throbber
----1
`
`i I
`
`
`
`
`
`i
`
`1
`I
`
`MPT 1347
`
`Radio interface specification
`For commercial trunked Iietworks
`
`ioperating in Band III, sub-bands 1 and 2
`
`1
`
`August 1988
`Revised and reprinted September 1991
`
`EXHIBIT
`
`Ex.1007
`
` Ex. 1007
`
`Page 1 of 86
`Page 1 0f 86
`
`iocommunacanons Agency :5 an EXEEUUVE Agency ol the
`
`PETITIONER'S EXHIBIT 1007
`D PETI'I‘IGONER'S EXHIBIT 1007
`
`

`

`
`
`L-----------
`
`Page 2 of 86
`Page 2 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`Crown Copyright 1988
`
`First published 1988
`
`Revised and reprinted September 199]
`
`
`
`ISBN 1 870837 26 6
`
`Page 3 of 86
`I Page 3 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`l-----------
`
`Page 4 of 86
`Page 4 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`FOREWORD
`
`This specification contains the radio interface requirements to be met by trunking system
`controllers and the associated base stations to be used in commercial
`trunked networks
`
`operating in Band III. sub-bands l and 2.
`
`A companion Specification, MPT 1343, contains the requirement to be met by radio units to
`be used with these networks.
`
`These complementary specifications are intended to enable a user to migrate from one
`commercial trunked network to another without having to change mobile radio unit.
`
`Intellgtual Property fights
`
`Firms intending to manufacture equipment which complies with the specification should be
`aware that certain features of the specification are subject to IPR claims.
`
`All firms are therefore advised that they should make appropriate enquiries through
`their Patent Agents before proceeding.
`
`Page 5 of 86
`' Page 5 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`|-‘-------_---
`
`Page 6 of 86
`Page 6 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`CONTENTS
`
`1
`
`2
`
`3
`
`4
`
`SCOPE
`
`ASSOCIATED DOCUMENTS
`
`GENERAL
`3.]
`
`Definitions
`
`3.2
`
`Environmental Requirements
`
`TRANSMITTER PARAMETERS
`
`4. 1
`4.2
`4.3
`
`Frequency Parameters
`Modulation Characteristics
`Performance Parameters
`
`5
`
`RECEIVER PARAMETERS
`
`5.1
`5.2
`5.3
`
`Frequency Parameters
`Demodulation Characteristics
`Performance Parameters
`
`Page
`
`1‘1
`
`2‘1
`
`3
`
`3—
`
`4-1
`4-2
`4-2
`
`S 1
`5-2
`5 2
`
`6
`
`7
`
`8
`
`NETWORK PARAMETERS
`6 1.
`
`Introduction
`
`6.2
`
`6.3
`
`6.4
`
`Network Dependent Data
`
`User Address Data
`
`Fixed Parameters
`
`6.5
`
`Network Customisation
`
`SECURITY
`
`NUMBERING CONVENTION
`8. 1
`Introduction
`
`8.2
`8.3
`
`8.4
`
`Network Options
`Call Diversion
`
`Storage Requirements
`
`9
`
`CONTROL CHANNEL OPERATION
`
`9.1
`9.2
`9.3
`9.4
`9.5
`
`Control Channel Availability
`Control Channel Frequencies
`Forward Control Channel Structure
`Control Channel Parameters
`Broadcast Information
`
`10
`
`REGISTRATION (Standard Option)
`10.1
`Registration in the network operating in the normal mode
`10.2 Registration Procedures
`
`ii
`
`-1
`
`-1
`a
`
`6
`2—
`2
`
`-4
`
`at
`
`7-1
`
`8-1
`
`8—1
`8-3
`
`8—4
`
`9-1
`9—1
`9-2
`9-7
`9-8
`
`10‘!
`10-]
`
`Page 7 of 86
`Page 7 Of 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`I I I I I I I I I I
`
`I
`
`I I I I I I I I I I
`
`

`

`
`
`‘-----------
`
`Page 8 of 86
`Page 8 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`ll
`
`GENERAL CONTROL PROCEDURES
`11. 1
`Introduction
`11.2 Definitions
`
`Signalling Formats
`11.3
`11.4 Addressing
`11.5 Codeword Structures
`11.6 Channel Discipline
`11.7 Random Access Protocol
`11.8 Registration Procedures
`11.9 Basic Call Procedures
`11.10 Emergency Call Procedures
`11.1]
`Include Call Procedures
`11.12 Call Diversion Procedures
`11.13 Status Message Procedures
`11.14 Short Data Messages
`11.15 Data Interrogation Procedures
`11.16 Not used
`11.17 Standard Data Procedures
`
`12
`
`13
`
`14
`
`NON STANDARD DATA
`
`FALL-BACK MODE (Standard Option)
`13.1
`Introduction
`13.2 Entering Fallback Mode
`13.3
`Procedures in Fall-back Mode
`13.4 Resuming normal control channel operation
`
`SHORT DATA ON THE CONTROL CHANNEL USING RQC
`14.1
`Introduction
`14.2 Message Format
`14—3 The Use of Control Fields for STF = '1'
`14—4 TSC Procedures
`14-5 An Example of the Procedures for Extended Data Message
`
`APPENDIX A
`
`APPENDIX B
`
`A.1
`A.2
`A.3
`
`3.1
`
`13.2
`
`Approval Arrangements
`Design changes
`Address for Approval Applications
`
`Declaration to be completed when applying
`for an MPT 1347 Approval Certificate
`Application for MPT 1347 Approval Certificate
`
`APPENDIX C
`
`SCHEDULE OF TSC FACILITIES TO BE TESTED
`C.1 Mandatory Facilities
`Standard Optional Features and Facilities
`
`iii
`
`11-1
`11-1
`
`11-1
`1 1-2
`11-2
`ll~8
`11-8
`11—9
`”-9
`11-11
`“-11
`“-11
`11—11
`“-12
`11-12
`11~12
`11-12
`
`12-1
`
`13-1
`13-1
`13-1
`13-1
`
`14-1
`14—2
`14-9
`14-10
`14-13
`
`A-l
`A-l
`A-2
`
`B-l
`B-Z
`
`01
`02
`
`Page 9 of 86
`' Page 9 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`Page 10 of 86
`Page 10 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`1
`
`SCOPE
`
`This specification is designed to be read in conjunction with MPT specifications 1323. 1327
`and l343, and contains the radio interface requirements to be met by trunked system
`controllers and associated base stations to be used in commercial trunked networks operating
`in Band III sub-bands 1 and 2.
`
`It covers the requirements for the following:
`
`- Signalling, based on MPT 1327;
`
`- Radio frequency parameters, where they are different from MPT 1323;
`
`- Technical interfaces for operation with radio units meeting MPT 1343:
`
`- Network operation;
`
`There are two main types of requirement:
`
`- Mandatory, applicable to all networks;
`
`- Optional, but implemented in a standard manner in networks where the options are
`implemented.
`
`l—l
`
`Page 11 of 86
`Page 11 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`Page 12 of 86
`Page 12 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`2
`
`ASSOCIATED DOCUMENTS
`
`MPT 1317 (1981)
`
`Code of practice for the transmission of digital information over land
`mobile radio systems.
`
`MPT 1318 (1986)
`
`Engineering memorandum: Trunked systems in the land mobile
`service.
`
`MPT 1323 (1987)
`
`Angle modulated radio equipment for use at base and mobile stations
`in the private mobile radio service operating in the frequency had 174-
`225 MHZ.
`
`MPT 1327 (1987)
`
`A signalling standard for trunked private land mobile radio systems.
`
`MPT 1331 (1987)
`
`Code of practice for radio site engineering.
`
`MPT 1343 (1988)
`
`to be used with
`radio units
`System interface specification for
`commercial trunked networks operating in Band III sub-bands l and 2.
`
`MPT 1352 (1991)
`
`the approval of radio units to be used with
`Test schedule for
`commercial trunked networks operating in Band III sub—bands 1 and 2.
`
`Page 13 of 86
`lPage 13 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`Page 14 of 86
`Page 14 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`3
`
`3. I
`
`GENERAL
`
`Definitions
`
`The definitions of terms used in this specification are given in MPT 1343. Two further
`definitions are given here:
`
`Network op_erator: The licensed operator of the network(s}.
`
`§yst§m standard data: This refers only to data messages originated or regenerated by the
`system using the data modulation specified in section 4.2.3 and with the form specified in
`MPT 1327, section 3. This definition excludes standard data signals originated by a unit but
`passing through the system without the system taking any responsibility for their form.
`
`!! delimiters in this specification refer to section
`Section numbers appearing between i!
`numbers within MPT 1327. Section numbers appearing between 95% %% deiimiters refer
`to section numbers within MPT 1343.
`
`'
`I
`
`3.2
`
`Environmental Rgiuirements
`
`Unless otherwise specified, base stations shall meet the requirements of this specification
`under extreme test conditions, as defined in MP’I‘ 1323, section 2.4. Other equipment shall
`be designed so as to take into account the environment in which it shall operate. Specified
`limits or requirements shall not be exceeded due to environmental conditions.
`
`3-1
`
`Page 15 of 86
`I Page 15 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`l---------------—-----
`
`Page 16 of 86
`Page 16 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`
`
`-"-'--'-'-‘-’-'-‘-'-"-'--'-"-‘-'-‘-‘--
`
`
`
`
`
`4
`
`4.1
`
`TRANSMITTER PARAMETERS
`
`Freguency Parameters
`
`4.1.1
`
`Channel Spacing and Designation for Sub-band l
`
`The channel spacing shall be 12.5 kHz.
`
`the channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`Base station
`transmitter
`frequency
`
`1
`
`58
`
`176.5000 MHz
`
`1000000001
`
`177.2125 MHz
`
`560
`
`1111110111
`
`183.4875 MHz
`
`The equipment shall be capable of operating on at least any one selected channel within the
`range 58 to 560 (177.2125 MHz to 183.4865 MHz). Transmission outside this frequency
`range is not permitted.
`
`4.1.2
`
`Channel Spacing and Designation for Sub-band 2
`
`The channel spacing shall be 12.5 kHz. The channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`Base station
`transmitter
`frequency
`
`1
`
`58
`
`200.5000 MHz
`
`0000000001
`
`201.2125 MHz
`
`560
`
`0111110111
`
`207.4875 MHz
`
`The equipment shall be capable of operating on at least any one selected channel within the
`range 58 to 560 (201.2125 MHz — 207.4875 Mp2). Transmission outside this frequency
`range is not permitted.
`
`4. 1.3
`
`Frauency Tolerance
`
`The carrier frequency transmitted shall be within 1.0 kHzof the nominal transmit frequency.
`
`4-!
`
`Page 17 of 86
`Page 17 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`4.2
`
`Modulation Characteristics
`
`4.2. 1
`
`general
`
`The peak frequency deviation shall not exceed :2.5 kHz.
`
`4.2.2
`
`Smh Modulation
`
`Speech transmissions shall employ a phase modulation characteristic.
`
`4.2.3
`
`5" ‘tem §tandard Dag Modulation
`
`System standard data modulation shall be by audio subcanier modulation employing phase
`continuous fast frequency shift keying (FFSK) to a frequency modulation characteristic at the
`RF carrier. During transmission of system standard data all audio other than this data signal
`shall be muted by at least 35 dB. The parameters of the modulation shall be as follows:
`
`Bit rate
`Modulation rate
`Binary '0'
`Binary '1‘
`Amplitude difference
`Data element boundaries
`Peak deviation
`Normal conditions
`Extreme conditions
`
`1200 Bit/s
`1200 Baud
`1800 Hz
`1200 Hz
`< 1.5 dB
`Phase 0" or 180°
`
`1.5 kHz 1 250 Hz
`1.5 kHz -_|- 500 Hz
`
`The method for modulating any other data is not prescribed in this specification.
`
`4.3
`
`Performance Parameters
`
`Transmitters shall meet the requirements of MPT 1323.
`
`Intermodulation attenuation shall be at least 40 dB for any intermodulation component. This
`may be achieved by the use of isolating devices external to the transmitter.
`
`
`
`4-2
`
`Page 18 of 86
`Page 18 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`l-----------
`
`

`

`-----'-'-"*---'-'-'-'-
`
`5
`
`RECEIVER PARAMETERS
`
`The requirements of this section shall be met under normal test conditions, as defined in
`MPT 1323 section 2.3, unless otherwise specified.
`
`5.1
`
`Frguency Parameters
`
`5.1.2
`
`Channel Spacing and Designation for Sub—band 1
`
`The channel spacing shall be 12.5 kl-lz. The channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`Base station
`receiver
`frequency
`
`184.5000 MHz
`
`1000000001
`
`185.2125 MHz
`
`1
`
`58
`
`560
`
`1111110111
`
`191.4875 MHz
`
`The equipment shall be capable of operating on at least any one selected channel within the
`range 185.2125 MHz to 191.4875 MHz. Opeation outside this range is not permitted.
`
`5.1.2
`
`EQhannel Spacing and Designation for Sub-band 2
`
`The channel spacing shall be 12.5 kHz.
`
`the channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`Base station
`receiver
`frequency
`
`192.5000 MHz
`
`0000000001
`
`193.2125 MHz
`
`1
`
`58
`
`560
`
`0111110111
`
`199.4875 MHz
`
`The equipment shall be capable of operating on at least any one selected channel within the
`range 193.2125 MHz - 199.4875 MHz. Operation outside this frequency range is not
`permitted.
`
`5.1.3
`
`Frequency Tolerance
`
`The centre frequency of the response of the receiver shall be within 1.0 kHz of the nominal
`receive frequency.
`
`S-l
`
`Page 19 of 86
`' Page 19 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`5.2
`
`Demodulatign gharacteristics
`
`5.2.1
`
`Spgzgh §ignals
`
`The speech demodulator shall have a phase demodulation response characteristic. The
`permitted departure from the phase demodulation response amplitude characteristic over the
`audio frequency range 300 Hz to 2.55 ld-Iz shall be i3 dB, ie the total audio output power
`shall fit totally within the mask of figure 5.1.
`
` /
`
`HUN/IN///////////////H
`
`/ /
`
`MPIitude
`relative to
`
`—
`
`optimum phase
`demodulator
`response
`
`T
`6 dBI
`J.
`
`/
`/
`l
`HI/l/HH/ll/l/l/H/l/l/H/
`
`100
`
`300
`
`1000
`
`2550
`
`10000
`
`5.2.2
`
`Data Signals
`
`Fi ure
`
`.1
`
`Received standard data signals have a fast frequency shift keying (FFSK) characteristic.
`Standard data modulation follows the requirements of MP1“ 1323, that is phase continuous
`1200 baud FFSK, with 1800 Hz representing binary ‘0‘ and 1200 Hz representing binary '1’.
`
`Note: The received peak deviation of standard data does not exceed $2.0 kHz and is not less
`than $1.0 kHz. For non-prescribed data, the peak frequency deviation does not exceed
`$2.5 kHz.
`
`5.3
`
`Eerformflce Pmmeters
`
`Base station receivers shall meet the requirements of MPT 1323.
`
`Page 20 of 86
`Page 20 of 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`
`
`

`

`6
`
`NETWORK PARAMETERS
`
`6. 1 mm
`
`This section details both the fixed and variable parameters which allow a radio unit to be
`customised and personalised to take service from a network.
`
`The data is divided into two categories: network dependent data (which defines how the radio
`unit operates), and user address data (which contains address and call information).
`
`6.2
`
`Network Degndent Data
`
`The network operator shall pr0vide the following information to allow radio units to be
`customised for the particular network.
`
`Parameter
`
`Item SizefRange
`of values
`
`Number of
`Entries
`
`1 Zone sub-field length
`2 Area sub-field length
`3
`Identity code of selected network
`4 Normal Hunt Channel Numbers!
`Size of Hunt
`5 Lowest Channel No in Network
`
`6 Highest Channel No in Network
`7
`Suppress Comprehensive Hunt
`8 Value of INFO to be used in RQR
`9 LMl Level margin (see 9.3.5)
`10 LM2 Level margin (see 9.3.5)
`ll LM3 Level margin (see 9.3.5)
`12 NC]- Size of Error Check Sample prior
`to confirmation
`13 NC2’ Size of Error Check Sample after
`confirmation
`14 NDD preference data
`15 NS- No. of samples in background sampling
`activity
`16 NV- No. of consecutive CCSCs during
`verification
`l7 NXl- Error codeword limit prior to
`canfirmation
`18 NX2- Error codeword limit after
`
`confirmation
`19 NZl- No of samples for error checking
`prior to confirmation
`20 N22- No of samples for error checking
`after confirmation
`21 NPON Number of Pressel 0n Messages
`
`6-l
`
`0 to 9 bits
`0 to 9 bits
`2 or 7 bits
`10 bits + TS flag
`Range 1 to 32
`10 bits
`
`1
`1
`1
`32
`1
`1
`
`1
`10 bits
`1
`Flag
`1
`15 bits
`0 to 40 dB in steps of 6 dB 1
`0 to 40 dB in steps of 6 dB 1
`0 to 40 dB in steps of 6 dB 1
`
`0 to 255 step 1
`
`2
`
`0 to 255 step 1
`Max. 9 bits
`
`2
`4 min.
`
`1 to 10 in steps of 1
`
`1 to 16 step 1
`
`0 to 255 step 1
`
`0 to 255 step 1
`
`1 to 255 step 1
`
`to 255 step 1
`1
`1 lo 5
`
`l
`
`2
`
`2
`
`2
`
`l
`
`l
`l "
`
`Page 21 of 86
`' Page 21 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`22
`
`23
`24
`25
`26
`27
`
`NPOFF Number of Pressel Off "Messages
`PREFERRED NDD priority indicator
`PREFERRED NDD sub-field length
`TC» Random Access Timeout
`TD- Registration Record Timeout
`TGI- Short Data Message
`Individual time out observed when radio
`
`to 5
`1
`to 10 in steps of 1
`1
`Range 0 to 9 bits
`0 to 120 secs step 10
`0 to 70 min step 5
`1
`to 15 seconds in 1 second
`steps
`
`unit responds to HEAD with
`ACK (QUAL = 0) or ACKB (QUAL = 1)
`28 TGG- Short Data Message Group timeout
`observed when radio unit receives a group
`HEAD message
`29 TH— Sampling activity duration
`30 TL— Sampling activity interval
`
`31 TJ- Further Signalling Timeout
`32 TN- Traffic Channel Timeout
`33 TS— Delay before leaving a
`Control Channel
`34 TD Maximum Item Duration
`35 Home Zone
`36 Non-applicable Channel Nos
`37 NT- Max TSC Response Delay to
`Unsolicited Traffic Channel Message
`38 TU- Data Call Duration Timer
`39 Suppress Data Call Duration Timer
`40 TA- Timeout for called radio
`unit after receiving AHY
`41 TW- Timeout for radio unit
`waiting for call
`
`l to 30 seconds in 1 second
`steps
`
`0 to 100 slots in steps of 1.
`0 to 3000 slots in
`steps of 100, or
`0 to 310 seconds in
`
`steps of 10
`0 to 60 secs step 10
`0 to 10 secs step 1
`
`0 to 10 secs step 1
`0 to 60 secs step 10
`0 to 9 bits
`10 bits
`103 to 1236 hits step
`103 bits
`30 to 180 secs Step 30 secs
`Flag
`10 to 120 second steps OR
`fixed at 60 seconds
`60 seconds
`
`1
`4 min.
`4 min.
`1
`1
`
`1
`
`1
`
`l
`
`l
`1
`l
`
`l
`1
`1
`Unspecified
`
`1
`1
`1
`
`1
`1
`
`6.3
`
`6.3.1
`
`user Address Data
`
`Data Programmfl lnto all Radio Units
`
`The following data has to be programmed into all radio units. The source of this data is not
`specified.
`
`Parameter
`
`Item Size/Range
`of values
`
`Number of
`Entries
`
`1 Own Prefix
`2 Own Individual Indent
`3 Access Authorisation Data
`4 Radio Unit Control Category
`
`7 bits
`13 bits
`Max 9 bits
`1 of 4
`
`1
`1
`8 min
`1
`
`6-2
`
`Page 22 of 86
`Page 22 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`
`
`---.------.o-v---v---v---*-'---
`
`
`
`
`
`Number of
`Entries
`
`min
`
`1
`
`10 max
`Unspecified
`112
`
`1/2
`1
`
`20 bits
`13 bits
`
`13 bits
`
`Flag
`Flag
`[3 bits
`
`13 bits
`
`Unspecified
`Unspecified
`13 bits
`
`13 bits
`13 bits
`
`Flag
`10 bits
`
`4/9 bits
`
`\DMQONMh-LQNi—I
`D—lr-Ilh-‘b—‘HH
`
`Ut-P'aJNF-‘O
`
`16
`
`17
`18
`19
`
`20
`
`Own Group Address
`Individual Base Ident
`
`Group Base Ident
`Two or Three Digit Individual Calls
`Two or Three Digit Group Calls
`Highest Permitted Own Fleet Individual Idem
`Highest Permitted Own Fleet Group Ident
`Single Digit Number Destination
`Look-up Table for 5-digit Inter-fleet Calls
`*0% and *Onn# Immediate Address
`*9# Immediate Address
`*2 Immediate Access
`
`Inter Fleet Group Calls Barred
`Channel No for Fall-back
`
`Value of NDD in SYS code for
`Fall-back Service
`
`SIL System Indicator Locator
`sub-field length
`*" Abbreviated Dialling Maximum Limit
`Disable FOACSU
`
`CLIM- Network personalisation data;
`maximum call duration for a
`
`non-emergency call
`
`CLIME- network personalisation data;
`maximum call duration for an
`
`emergency call
`
`6.3.2
`
`Data Programmed Into Some Radio Units
`
`The following data may require to be programmed into certain radio units, dependent upon
`the facilities offered by the radio unit manufacturer. The source ofthis data is not specified.
`
`Parameter
`
`Item SizeIRange
`of values
`
`Range 3 to 9 bits in
`steps or” 1
`8 bits
`
`Flag
`10 secs to 4 mins 14 secs
`
`in 1 sec steps, or 5 mins to
`13 mins in l min steps,
`or inhibited
`10 secs to 4 mins 14 secs
`
`1
`
`in 1 sec steps, or 5 mins to
`13 mins in l min steps.
`or inhibited
`
`6-3
`
`Page 23 of 86
`Page 23 0f 86
`
`PETITIONER'S EXHIBIT 1007
`
`PETITIONER'S EXHIBIT 1007
`
`

`

`
`
`
`
`6.4
`
`Fixed Parameters
`
`The following radio unit parameters are fixed and networks must take these into account.
`
`1
`2
`3
`4
`5
`
`6
`7
`
`8
`9
`10
`
`11
`12
`
`6.5
`
`NDl
`ND'Z
`NE
`N1
`NR
`
`- No of disconnect messages sent by called radio unit
`- No of disconnect messages sent by calling radio unit
`- Max no of random access transmissions of RQE
`- Max no of include request access attempts
`- Max no of random access transmissions
`
`of RQS, RQD, RQX, RQT, RQR or RQQ
`NW - Response delay (in frames)
`TB
`- Time barred from calling same ident after
`ACK/ACKX/ACKV or any idea: after ACKT/ACKB
`— Value of TS in fall-back mode
`- Include timer
`- Max interval between periodic messages to be assumed
`at switch-on or equivalent
`- Value of TC in fall-back mode
`- Call set-up - Data Keyline delay
`
`TF
`TI
`TP
`
`TX
`TR
`
`Network Customisation
`
`Value
`
`3
`5
`16
`4
`
`8
`5
`
`2 s
`180 s
`2 s
`
`5 s
`180 s
`500 ms
`
`The previous sections have detailed the requirements and limits for the variables specified
`in MPT 1343. A network operator is free to design his network with particular functions (eg
`time shared control channels, fall-back, full-off—air—call-set-up etc) provided that the above
`requirements are complied with.
`
`Page 24 of 86
`Page 24 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`6-4
`
`

`

`7
`
`SECURITY
`
`Each radio unit stores a unique 38 bit security number which is programmed by the radio
`unit manufacturer and which can be accessed by the system. Various restrictions are
`irnistet:I on radio unit manufacturers towards safeguarding the integrity of this number (see
`MPT 1343 sectiOn 7).
`
`There is no requirement on the system to read or check the security number ofa mobile, but
`performing the check on security number will reduce or discourage abuse and fraud in the
`following areas:
`
`LA-FthMH
`
`Theft of radio units;
`
`Cloning of radio units;
`Use of unapproved equipment;
`Fraud by modification of identity;
`Denial of responsibility to pay a bill for use of the system.
`
`There are a number of steps that may be taken by a system once a security number has been
`read from a radio unit:
`
`1
`
`Ix.)
`
`3
`
`Check the security number against a whitelist of numbers permitted to use the system,
`checking that the individual user identity matches that expected.
`(In practice, the
`security number would be stored in a location determined by the individual user
`identity, along with billing information if applicable.)
`
`Check the security number against as blacklist of known "rogue" radio units (alone,
`this is less useful than (1) above). A blacklist may be useful to help locate stolen
`mobiles.
`
`The system may check the integrity of the 8 check bits (see below) within the security
`number. This does not need storage of lists, and may be useful initially and on
`systems with limited processing or storage capability.
`
`The format of the security number is as follows:
`
`Manufacturer's
`Code
`
`Model
`
`Serial number
`for: this model
`
`Check Bit-.5
`
`3 bits
`
`4 bits
`
`18 bits
`
`8 bits
`
`The system may request a radio unit to transmit its security number using an AHYC message
`(see MPT 1327 Sections 5.5.3.2.8, 9.1.1 and 15). The radio unit responds with the security
`number in a SAMIS message (see MPT 1327 Section 5.6.1.22). The parameter fields of
`the SAMIS message are constructed as follows:
`
`7-]
`
`-----------
`
`Page 25 of 86
`Page 25 of 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`
`
`

`

`PARAMETERS 1
`
`(20 bits)
`
`PARAMETERS 2 (19 bits)
`
`Manufacturer's
`Code
`
`Model
`
`Check bits
`
`Serial number
`for this model
`
`8 bits
`
`4 bits
`
`8 bits
`
`18 bits
`
`Manufacturer's code:
`
`An 8 bit number (0 to 255), one or more of which is issued to
`each radio unit manufacturer by the licensing body (ie the
`Radiocommunications Agency in the UK).
`
`Model:
`
`Serial number (for
`this model):
`
`Check bits:
`
`A 4 bit number (0 to 15) which is unique to a radio unit type
`for a given manufacturer‘s code.
`The model number is
`allocated by the manufacturer as and when new radio unit
`models are to be type approved.
`In the event of a radio unit
`manufacturer producing more than 16 type approved models,
`the manufacturer may apply for an additional manufacturer's
`code.
`
`The serial number of the radio unit of a given model.This model
`number is allocated by the manufacturer, and would normally
`run from 1 up towards 262143. Where this capacity is
`exceeded,
`the radio unit manufacturer may allocate an
`additional model number to radio units of the same type
`
`approval type.
`
`The algorithm for calculating the check bits is based on the
`data contained in the other fields above. The algorithm used
`in the UK is available from the DTI to manufacturers and
`network operators.
`If the check bits are incorrect in a radio
`unit, a network may refuse access to that radio unit. The
`algorithm will not be present in the radio unit.
`
`I
`
`|
`
`I
`
`Manufacturer‘s codes and the security algorithm can be obtained by writing to the following
`address:
`
`Mobile Technology Section
`Radiocommunications Agency
`Room 514
`
`Waterloo Bridge House
`London
`SE1 SUA
`
`Page 26 of 86
`Page 26 0f 86
`
`
`7—2
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`O
`
`
`
`

`

`8
`
`8.1
`
`NUMBERING CONVENTION
`
`Introduction
`
`The primary objective of the numbering convention is to provide a means of dialling short
`number strings on radio units for in-fleet calls by reference to common base identities and
`group identities to fleets therefore each need blocks of contiguous identities. The lowest
`identity in each block (the base ident) has an even value.
`the blocks of individual and group
`identities for one fleet both operate within a common prefix. Networks shall conform to this
`convention.
`
`Radio units numbers which are dialled by the radio unit user are translated, in the radio unit,
`into unit addresses by means of algorithms which use the dialled number and the base ident
`or the Iatter’s allegory, the fleet number (%%8.2.3.1%%).
`
`The network may restrict the calls that the unit is permitted to make to identities within the
`fleet allocation or,
`in addition,
`to other parts of the addressing range. Conversely no
`restrictions need to be made to any unit which is allowed full access to all other units on the
`network or to units which have internal limitations on the number of identities which the unit
`
`can call. The network may also be connected to other communications networks and
`facilities such as:
`
`'
`
`- PABX networks
`
`— PSTN networks
`
`- Operator services
`
`traffic between radio units and these networks to meet user
`The network may restrict
`requirements in a similar manner to restrictions applied to inter-unit calls.
`
`The options described in this specification are not an exhaustive list. Other options may be
`incorporated into the system design as may be required by the network operator.
`
`8.2
`
`Network Options
`
`This network may maintain records of each fleet starting address and finishing address for
`both individual and group address blocks. This information may be made available to service
`providers for inclusion in the network personalisation data installed in each radio unit.
`
`8.2.1
`
`all t
`
`i.
`
`Inter-unit calls
`
`A unit address or a group address consists of a combination of any prefix (PFIX) with
`an identity (IDENT) in the range 1 to 8100. The use of other aduresses is specified
`in MPT 1327, Section 4 and in sub-sections iv and v below.
`
`The network may restrict the acceptance of call set-up requests from any unit to pre-
`arranged parts of the addressing range.
`
`8—1
`
`Page 27 of 86
`| Page 27 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`Outgoing PABX calls
`ii.
`Random access requests (RQn) with EXT = ‘ 1‘ may be accepted from radio units for
`calls to a PABX.
`Such call requests will contain an offset telephone extension
`number in IDENTI with additional routing in FLAGI and FLA02 (!!5.5.3.l.1!!).
`
`For received IDENT] = O to 7999 the network shall recover the original dialled
`number by adding 1000 (base 10)
`to the received lDENTl, and shall offer the
`recovered number to the selected PABX (% %8.2.5 % %). Leading digits in the dialled
`string may be discarded by the network if the connected PABX has less than four
`digits in its numbering scheme.
`
`The candidate PABX (one of four maximum) shall be selected by reference to the
`calling party identity and the setting of FLAGl and FLAGZ. PABXs are selected
`according to the table:
`
`Candidate
`
`PABX
`l
`2
`
`3
`4
`
`FLAGl
`0
`0
`
`1
`1
`
`FLAG2
`0
`1
`
`0
`1
`
`If the radio unit sends IDENT] = 8000 the network may select the PABX defined
`by FLAGl and FLAGZ, as defined above, and set up a call to the PABX Operator
`(%%8.2.5.1, 8.2.5.2%%). 1Values of IDENTI = 8001 to 8191 are available for
`customisation.
`
`The network may also accept random access requests (RQn) to PABXI (IDENT 8102)
`with EXT = '0’ from radio units for extended addressing calls to larger PABX
`networks. Such calls send all dialling information (including exchange routing digits)
`in a SAMIS on demand from the network (% %8.2.5.6% %). Connection shall be to
`the PABX network specified by the unit user.
`
`Outgoing PSTN calls
`iii.
`The network may accept random access requests (RQn except RQQ) from radio units
`for extended addressing calls via IDENT 8101 (PSTNGI). Such calls send full
`national or international numbers (less the leading zero) in a SAMIS plus optional
`data codewords on demand from the network.
`(%%8.2.6.2%%).
`
`The network may also accept random access requests (RQn) from radio units for short
`addressing calls via IDENTs 8121 to 8135 (PSTNSIj). Each IDENT for such calls
`is translated into a full national or international number by the network using data
`held by the network for each radio unit or fleet. Connection may be to any UK
`PSTN by arrangement with the relevant PSTN operator.
`(96968.18. 1 %%).
`
`The digit string sent to the PSTN for each call and the method of connection will be
`agreed with the chosen PSTN operator who may require the restoration of the leading
`zero of the dialled string.
`
`8-2
`
`Page 28 of 86
`Page 28 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`Special IDENTs 8136 to 8169
`iv.
`Special IDENTs 8136 to 8169 are spare for customisation.
`
`Operator Services
`v.
`The network may offer operator services to callers on receipt of special IDENTs 8170
`to 8180.
`It is recommended that 8170 is used for calls to a call assistance operator
`and 8180 to an emergency operator. With the exception of 8170, which is originated
`in the radio unit by the dialled string 100, and 8180, which is originated by the
`dialled string 999, the IDENTs 817x correspond to dialled strings 1x1 and the service
`which is offered is at the discretion of the network operator. eg:
`
`Radio Unit
`Dialled String
`
`Special
`[dent
`
`100
`111
`121
`
`131
`141
`151
`161
`171
`181
`
`191
`999
`
`8170
`8171
`8172
`
`8173
`8174
`8175
`8176
`8177
`8178
`
`8179
`8180
`
`8.3
`
`Call Diversion
`
`Numerical or addressing information which is received from the divertor as part of a
`diversion request for the divertor (RQT, DIV = ‘0', FLAG 2 = '0‘), ie the contents of
`IDENTI, or the accompanying numerical or addressing data received in response to an
`AHYfiC sent by the system if IDENTl = [PFIXL PABXI, or PSTNGI, may be stored against
`the divertor‘s address and sent as a response to any call request to that address.
`If the
`diversion address is a PSTN number or PSTNSIj and the caller has the number, or equivalent
`number, in store as a short form address, the appropriate PSTNSIj may be sent to the caller,
`otherwise the full PSTN number may be sent to the caller as the diverted call destination.
`
`8.3.1
`
`Third party diversions
`
`Numerical or addressing information which is received from the divertor as part of a
`diversion request on behalf of a third party (RQT, DIV = '0', FLAG 2 = '1'), ie the
`contents of IDENTI, or the accompanying numerical or addressing data received in response
`to an AHYC sent by the system if IDENTl = IPFIXI, PABXI, or PSTNGIj, may be stored
`against the address of the unit which is indicated by the calling unit upon the system sending
`an AHYC, IDENTI = DIVERTI, and sent as a response to any call request to that address.
`If the diversion address is a PSTN number or PSTNSI and the caller has the number, or
`equivalent number, in store as a short form address, the appropriate PSTNSIj may be sent
`to the caller, otherwise the full PSTN number may be sent to the caller as the diverted call
`
`8-3
`
`Page 29 of 86
`I Page 29 0f 86
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`destination.
`
`Call diversion requests from either self-interested parties or third parties may displace earlier
`requests set up by either method.
`
`8.3.2
`
`Qancel Diversion
`
`A cancel diversion request (RQT, DIV = ‘1‘, FLAG 2 = '0‘) cancels the diversion state for
`the unit whose address is PFIX/IDENTI, or the address data received in response to an
`AHYC sent by the system if IDENTI = IPFIXI.
`
`8.4
`
`§torage Rguirements
`
`The network may store the following data for each radio unit or fleet:
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`Fleet base identity for individual calls (%%8.2.3.1%% I81);
`
`Fleet base identity for group calls (%%8.2.3.1%% GBI);
`
`Highest used identity for individual calls (or block size);
`
`Highest used identity for group calls (or block size);
`
`15 PSTN numbers
`Up to
`(%%8.2.8.l.1%%);
`
`for
`
`translation from PSTNSIj
`
`(8121
`
`to
`
`8135)
`
`Up to 34 network defined numbers or facilities for translation from spare IDENTs
`8136 to 8169 (%%8.2.8.l.1%%);
`
`Up to 11 sets of routing data for network operator services for translation from spare
`IDENTs 8170 to 8180 (%%8.2.7%%);
`
`The following storage requirements are requested for each call diversion interception:
`
`a.
`
`b.
`
`0.
`
`Diverted party address;
`
`Diversion destination;
`
`Divert SpeechIDivert Data flags.
`
`
`
`_————--————--——-———4
`
`8—4
`
`Page 30 of 86
`Page 30 Of 86
`
`
`PETITIONER'S EXHIBIT 1007
`PETITIONER'S EXHIBIT 1007
`
`

`

`9
`
`CONTROL CHANNEL OPERATION
`
`9.1
`
`‘
`
`gontrol Qhannel Availability
`
`The control channel is the medium which allows the population of radio units to communicate
`with the network control elements (the TSC of MPT 1327). when they are not assigned to
`traffic chann

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