`:\<..E:'\C\
`
`MPf 1347
`
`Radio interface specification
`
`For commercial trunked networks
`operating in Band rn, sub-bands 1 and 2
`
`August 1988
`Revised and reprinted September 1991
`
`I I I••I I••
`
`•••I
`••I
`
`I.
`
`The Radiocommunications Av_nC)' is an Executl..... Agency of the Deplllrtment of T~de and Industry
`
`I••I
`
`Petitioner Cox Communications - Exhibit 1007 Page 1
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 2
`
`
`
`Crown Copyright 1988
`
`First published 1988
`
`Revised and reprinted September 1991
`
`ISBN I 870837 26 6
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 3
`
`
`
`I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 4
`
`
`
`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 I and 2.
`
`A companion specification, MPT 1343, contains the requirement to be met by radio units 10
`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.
`
`IntelIectual Property Rights
`
`Firms intending to manufacture equipment which complies with the specification should be
`aware that certain features of the specification are subject to [PR claims.
`
`AII fU"lllS are therefore advised that they should make appropriate enquiries through
`their Patent Agents before proceeding.
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 5
`
`
`
`I I I I I I I I I I I I I I I I I I
`
`'I
`
`I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 6
`
`
`
`I I
`
`I
`I
`I
`I
`I
`I
`I
`I.
`I
`I
`
`I
`
`I
`I
`I
`I
`
`I•
`
`• 8
`• 9
`
`CONTENTS
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`SCOPE
`
`ASSOCIATED DOCUMENTS
`
`GENERAL
`3.1
`3.2
`
`Definitions
`Environmental Requirements
`
`TRANSMITTER PARAMETERS
`4.1
`Frequency Parameters
`4.2
`Modulation Characteristics
`4.3
`Performance Parameters
`
`RECEIVER PARAMETERS
`5.1
`Frequency Parameters
`5.2
`Demodulation Characteristics
`5.3
`Performance Parameters
`
`NETWORK PARAMETERS
`6.1
`Introduction
`6.2
`Network Dependent Data
`6.3
`User Address Data
`6.4
`Fixed Parameters
`6.5
`Network Customisation
`
`SECURITY
`
`NUMBERING CONVENTION
`8.1
`Introduction
`8.2
`Network Options
`8.3
`Call Diversion
`8.4
`Storage Requirements
`
`CONTROL CHANNEL OPERATION
`9.1
`Control Channel Availability
`9.2
`Control Channel Frequencies
`9.3
`Forward Control Channel Structure
`9.4
`Control Channel Parameters
`9.5
`Broadcast Information
`
`Page
`
`I-I
`
`2-1
`
`3-1
`3-1
`
`4-1
`4-2
`4-2
`
`5-1
`5-2
`5-2
`
`6-1
`6-1
`6-2
`6-4
`6-4
`
`7-1
`
`8-1
`8-1
`8-3
`8--+
`
`9-1
`9-1
`9-2
`9-7
`9-8
`
`10
`
`REGISTRATION (Standard Option)
`10.1
`Registration in the network operating in the normal mode
`10.2 Registration Procedures
`
`10-1
`10-1
`
`11
`
`Petitioner Cox Communications - Exhibit 1007 Page 7
`
`
`
`- - - - - - - - - - - - - - -
`
`I I I I I I I I I I I I I I I I I I I I
`
`-
`
`Petitioner Cox Communications - Exhibit 1007 Page 8
`
`
`
`11
`
`12
`
`13
`
`14
`
`GENERAL CONTROL PROCEDURES
`11. I
`Introduction
`11.2 Definitions
`11. 3
`Signalling Formats
`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.11 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
`
`NON STANDARD DATA
`
`FALL-BACK MODE (Standard Option)
`13.1
`Introduction
`13.2
`Entering Fall-back Mode
`13.3
`Procedures in Fall-back Mode
`13.4 Resuming normal contro! 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 = '!'
`14-4
`TSC Procedures
`14-5 An Example of the Procedures for Extended Data Message
`
`APPENDIX A
`A.l
`A.2
`A.3
`
`APPENDIX B
`
`Approval Arrangements
`Design changes
`Address for Approval Applications
`
`B.I
`
`B.2
`
`C.I
`C.2
`
`Declaration to be completed when applying
`for an MPT 1347 Approval Certificate
`Application for MPT 1347 Approval Certificate
`
`SCHEDULE OF TSC FACILITIES TO BE TESTED
`Mandatory Facilities
`Standard Optional Features and Facilities
`
`APPENDIX C
`
`III
`
`11-1
`11-1
`11-1
`11-2
`11-2
`11-8
`11-8
`11-9
`11-9
`11-11
`11-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-I
`A-I
`A-2
`
`B-1
`B-2
`
`C-I
`C-2
`
`I II I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 9
`
`
`
`I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 10
`
`
`
`1
`
`SCOPE
`
`This specification is designed to be read in conjunction with MPT specifications 1323. 1327
`and 1343, 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.
`
`1-1
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 11
`
`
`
`I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 12
`
`
`
`2
`
`ASSOClATED 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 bad 174(cid:173)
`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)
`
`radio units to be used with
`System interface specification for
`commercial tronked networks operating in Band III sub-bands I and 2.
`
`MPT 1352 (1991)
`
`the approval of radio units to be used with
`Test schedule for
`commercial tronked networks operating in Band III sub-bands I and 2.
`
`2-1
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 13
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 14
`
`
`
`3
`
`3.1
`
`GENERAL
`
`Definitions
`
`The definitions of terms used in this specificalion are given in MPT 1343. Two further
`definitions are given here:
`
`Network operator: The licensed operator of the network(s).
`
`System standard data: This refers only 10 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 !!
`numbers within MPT 1327. Section numbers appearing between %% %% delimiters refer
`to section numbers within MPT 1343.
`
`3.2
`
`Environmental Requirements
`
`Unless otherwise specified, base stations shall meet the requirements of this specification
`under extreme test conditions, as defined in MPT 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
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 15
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 16
`
`
`
`4
`
`4.1
`
`TRANSMITTER PARAMETERS
`
`FreQuency Parameters
`
`4.1.1
`
`Channel Spacing and Designation for Sub-band 1
`
`The channel spacing shall be 12.5 k.Hz. the channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`1
`
`58
`
`560
`
`1()()()(J()()()Q 1
`
`1111110111
`
`Base station
`transmitter
`frequency
`
`176.5000 MHz
`
`177.2125 MHz
`
`183.4875 MHz
`
`The equipment shall be capable of operating on at least anyone 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
`
`1
`
`58
`
`560
`
`OOOOOOOOO1
`
`0111110111
`
`Base station
`transmitter
`frequency
`
`200.5000 MHz
`
`201.2125 MHz
`
`207.4875 MHz
`
`The equipment shall be capable of operating on at least anyone selected channel within the
`range 58 to 560 (201.2125 MHz - 207.4875 Ml-Iz). Transmission outside this frequency
`range is not permitted.
`
`4.1.3
`
`FreQuency Tolerance
`
`The carrier frequency transmitted shall be within 1.0 kHz of the nominal transmit frequency.
`
`4-1
`
`I(cid:173)IIIiIIIII,ItI,ItI *IIIIIIIII
`
`Petitioner Cox Communications - Exhibit 1007 Page 17
`
`
`
`I I I I I I I I I I I I I I
`
`I I I I I I
`
`4.2
`
`4.2.1
`
`Modulation Characteristics
`
`General
`
`The peak frequency deviation shall not exceed ±2.5 kHz.
`
`4.2.2
`
`Speech Modulation
`
`Speech transmissions shall employ a phase modulation characteristic.
`
`4.2.3
`
`~. -tem Standard Data Modulation
`
`System standard data modulation shall be by audio subcarrier 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 0 or 180 0
`
`1.5 kHz ± 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
`
`Petitioner Cox Communications - Exhibit 1007 Page 18
`
`
`
`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. I
`
`5. 1.2
`
`Frequency Parameters
`
`Channel Spacing and Designation for Sub-band I
`
`The channel spacing shall be 12.5 kJ:lz. The channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`58
`
`560
`
`10ס0ooooo1
`
`1111110111
`
`Base s!ation
`receiver
`frequency
`
`184.5000 MHz
`
`185.2125 MHz
`
`191.4875 MHz
`
`The equipment shall be capable of operating on at least anyone selected channel within the
`range 185.2125 MHz to 191.4875 MHz. Opeation outside this range is not permitted.
`
`5.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
`
`I
`
`58
`
`560
`
`סס0oooooo1
`
`0111110111
`
`Base station
`receiver
`frequency
`
`192.5000 MHz
`
`193.2125 MHz
`
`199.4875 MHz
`
`The equipment shall be capable of operating on at least anyone 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.
`
`5-1
`
`I,
`
`I~I,I•I *I,I *III,I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 19
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`5.2
`
`5.2.1
`
`Demodulation Characteristics
`
`Speech Signals
`
`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 kHz shall be +3 dB, ie the total audio output power
`shall fit totally within the mask of figure 5.1.
`
`Amplitude
`relative to
`optimum phase
`demodulator
`response
`
`t
`6 dBI
`~
`
`I
`I
`I
`I
`IIIIIIIIIIIIIIIIIIIIIIIIIIII
`
`IIIIIIIIIIIIIIIIIIIIIIIIIII
`I
`I
`I
`I
`
`100
`
`300
`
`1000
`
`2550
`
`10000
`
`5.2.2
`
`Data Signals
`
`Figure 5.1
`
`Received standard data signals have a fast frequency shift keying (FFSK) characteristic.
`Standard data modulation follows the requirements of MPT 1323, that is phase continuous
`1200 baud FFSK, with 1800 Hz representing binary '0' and 1200 Hz representing binary 'I'.
`
`Note: The r~ived 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
`
`Performance Parameters
`
`Base station receivers shall meet the requirements of MPT 1323.
`
`5-2
`
`Petitioner Cox Communications - Exhibit 1007 Page 20
`
`
`
`Parameter
`
`Zone sub-field length
`I
`2 Area sub-field length
`Identity code of selected network
`3
`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)
`11 LM3 Level margin (see 9.3.5)
`12 NCI- 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 consec-utive CCSCs during
`veri fication
`17 NX 1- Error codeword limit prior to
`confirmation
`18 NX2- Error codeword limit after
`confirmation
`19 NZI- No of samples for error checking
`prior to confirmation
`20 NZ2- No of samples for error checking
`after confirmation
`21 NPON Number of Pressel On Messages
`
`6-[
`
`I I I I I I I I I I I I I I I I I I I I I
`
`6
`
`6.1
`
`NETWORK PARAMETERS
`
`Introduction
`
`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 Dependent Data
`
`The network operator shall provide the following information to allow radio units to be
`customised for the particular network.
`
`Number of
`Entries
`
`Item Size!Range
`of values
`oto 9 bits
`I
`oto 9 bits
`I
`1
`2 or 7 bits
`10 bits + TS flag
`32
`I
`Range I to 32
`1
`10 bits
`1
`10 bits
`1
`Flag
`I
`15 bits
`oto 40 dB in steps of 6 dB 1
`oto 40 dB in steps of 6 dB 1
`oto 40 dB in steps of 6 dB 1
`oto 255 step I
`oto 255 step 1
`Max. 9 bits
`
`2
`
`2
`4 min.
`
`I to 10 in steps of I
`
`I to 16 step 1
`oto 255 step 1
`oto 255 step 1
`
`I to 255 step 1
`
`I to 255 step I
`I to 5
`
`I
`
`2
`
`2
`
`2
`
`I
`I _.
`
`Petitioner Cox Communications - Exhibit 1007 Page 21
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`22 NPOFF Number of Pressel Off-Messages
`23 PREFERRED NDD priority indicator
`24 PREFERRED NDD sub-field length
`25 TC- Random Access Timeout
`26 TD- Registration Record Timeout
`27 TGI- Short Data Message
`Individual time out observed when radio
`unit responds to HEAD with
`ACK (QUAL = 0) or ACKB (QUAL = I)
`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 TT- 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
`
`I to 5
`I to 10 in steps of I
`Range 0 to 9 bits
`o to 120 secs step 10
`o to 70 min step 5
`I to 15 seconds in I second
`steps
`
`I
`4 min.
`4 min.
`I
`I
`
`I
`
`I
`
`I to 30 seconds in I second
`steps
`o to 100 slots in steps of I,
`o to 3000 slots in
`steps of 100, or
`o to 310 seconds in
`steps of 10
`o to 60 secs step 10
`o to 10 secs step 1
`o to 10 secs step 1
`o to 60 secs step 10
`o to 9 bits
`10 bits
`103 to 1236 bits step
`1
`103 bits
`30 to 180 secs Step 30 secs 1
`1
`Flag
`10 to 120 second steps OR
`fixed at 60 seconds
`60 seconds
`
`I
`1
`1
`
`1
`1
`1
`Unspecified
`
`1
`I
`
`6.3
`
`6.3.1
`
`User Address Data
`
`Data Programmed Into all Radio Units
`
`The following data has to be programmed into all radio units. The source of this data is not
`specified.
`
`Item Size/Range
`of values
`
`Number of
`Entries
`
`mill
`
`I 18
`
`I
`
`7 bits
`13 bits
`Max 9 bits
`1 of 4
`
`Parameter
`
`I Own Prefix
`2 Own Individual Indent
`3 Access Authorisation Data
`4 Radio Unit Control Category
`
`6-2
`
`Petitioner Cox Communications - Exhibit 1007 Page 22
`
`
`
`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 of this data is not specified.
`
`Parameter
`
`Item Size/Range
`of values
`
`Number of
`Entries
`
`4 min
`
`I 1IIII1
`
`0 max
`Unspecified
`1/2
`1/2
`
`III
`
`IIII
`
`20 bits
`I Own Group Address
`13 bits
`Individual Base Ident
`2
`13 bits
`3 Group Base Ident
`Flag
`4 Two or Three Digit Individual Calls
`Flag
`5 Two or Three Digit Group Calls
`6 Highest Permitted Own Fleet Individualldent 13 bits
`7 Highest Permitted Own Fleet Group Ident
`13 bits
`Single Digit Number Destination
`Unspecified
`8
`Look-up Table for 5-digit Inter-fleet Calls
`Unspecified
`9
`10 "0% and "Onn# Immediate Address
`13 bits
`11 "9# Immediate Address
`13 bits
`13 bits
`12 "2 Immediate Access
`13 In ter Fleet Group Calls Barred
`Flag
`14 Channel No for Fall-back
`10 bits
`15 Value of NDD in SYS code for
`Fall-back Service
`16 SIL System Indicator Locator
`sub-field length
`17 .... Abbreviated Dialling Maximum Limit
`18 Disable FOACSU
`19 CLIM- Network perspnalisation data;
`maximum call duration for a
`non-emergency call
`
`20 CLIME- network personalisation data;
`maximum call duration for an
`emergency call
`
`6-3
`
`4/9 bits
`Range 3 to 9 bits in
`steps of I
`8 bits
`Flag
`10 secs to 4 mins 14 secs
`in I sec steps, or 5 mins to
`13 mins in I min steps,
`or inhibited
`10 secs to 4 mins 14 secs
`in I sec steps, or 5 mins to
`13 mins in I min steps,
`or inhibited
`
`IIIII *,I~I *ItI *ItIj ItItI(cid:173)I\I
`
`Petitioner Cox Communications - Exhibit 1007 Page 23
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`6.4
`
`Fixed Parameters
`
`The following radio unit parameters are fixed and networks must take these into account.
`
`NDl
`ND2
`NE
`NI
`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
`ofRQS,RQD,RQX,RQT,RQRorRQQ
`NW - Response delay (in frames)
`- Time barred from calling same ident after
`TB
`ACKlACKX/ACKV or any ident 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
`
`Value
`
`3
`5
`16
`4
`
`8
`5
`
`2 s
`180 s
`2 s
`
`5 s
`180 s
`500 ms
`
`I
`2
`3
`4
`5
`
`6
`7
`
`8
`9
`10
`
`11
`12
`
`6.5
`
`Network Customisation
`
`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-eall-set-up etc) provided that the above
`requirements are complied with.
`
`6-4
`
`Petitioner Cox Communications - Exhibit 1007 Page 24
`
`
`
`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
`imposed 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 of a mobile, but
`performing the check on security number will reduce or discourage abuse and fraud in the
`following areas:
`
`1
`2
`3
`4
`5
`
`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
`r~ad from a radio unit:
`
`1
`
`2
`
`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 a· 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
`
`Se:::-ial number
`for this model
`
`Check Bits
`
`8 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.2.2). The parameter fields of
`the SAMIS message are constructed as follows:
`
`7-1
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 25
`
`
`
`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:
`
`Model:
`
`Serial number (for
`this model):
`
`Check bits:
`
`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).
`
`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 thi$ 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
`If the check bits are incorrect in a radio
`network operators.
`unit, a network may refuse access to that radio unit. The
`algorithm will not be present in .he radio unit.
`
`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 SEl 8UA
`
`7-2
`
`••••••••••••••
`
`••
`••
`
`'•
`••'.,
`'•
`•~
`
`Petitioner Cox Communications - Exhibit 1007 Page 26
`
`
`
`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
`the blocks of individual and group
`identity in each block (the base ident) has an even value.
`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 latter'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
`in addition,
`to other parts of the addressing range. Conversely no
`fleet allocation or,
`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:
`
`- P ABX 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 ir. the network personalisation data installed in each radio unit.
`
`8.2.1
`
`Call types:
`
`Inter-unit calls
`i.
`A unit address or a group address consists of a combination of any prefix (PFIX) with
`an identity (IDENT) in the range I 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(cid:173)
`arranged parts of the addressing range.
`
`8-1
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 27
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`ii.
`Outgoing PABX calls
`Random access requests (RQn) with EXT = 'I' 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 FLAGl and FLAG2 (!!5.5.3.1.1!!).
`
`For received IDENTI = 0 to 7999 the network shall recover the original dialled
`number by adding 1000 (base 10) to the received IDENT I , 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 FLAG I and FLAG2. PABXs are selected
`according to the table:
`
`FLAG2
`
`oIo1
`
`FLAG I
`
`ooI1
`
`Candidate
`PABX
`
`I234
`
`If the radio unit sends IDENTl = 8000 the network may select the PABX defined
`by FLAG! and FLAG2, as defined above, and set up a call to the PABX Operator
`(%%8.2.5.1, 8.2.5.2%%). Values of IDENTl = 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
`lll.
`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
`(%%8.2.6.2%%).
`data codewords on demand from the network.
`
`The network may also accept random access requests (RQn) from radio units for short
`addressing calls via IDENTs 8121 to 8135 (PSTNSlj). 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.
`(% %8.2.8.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
`
`Petitioner Cox Communications - Exhibit 1007 Page 28
`
`
`
`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 !DENTs 8170
`It is recommended that 8170 is used for calls to a call assistance operator
`to 8180.
`and 8180 to an emergency operator. With the exception of8170, 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 1xI and the service
`which is offered is at the discretion of the network operator. eg:
`
`Radio Unit
`Dialled String
`
`Special
`Ident
`
`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, DIY = '0', FLAG 2 = '0'), ie the contents of
`IDENTl, or the accompanying numerical or addressing data received in response to an
`AHXC sent by the system ifIDENTl = IPFIXI, PABXI. or PSTNGI, may be stored against
`If the
`the divertor's address and sent as a response to any call request to that address.
`diversion address is a PSTN number or PSTNSlj and the caller has the number, or equivalent
`number, in store as a short form address, the appropriate PSTNSlj 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 = 'I '), ie the
`contents of IDENTl, or the accompanying numerical or addressing data received in response
`to an AHYC sent by the system iflDENTI = 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, IDENTl = 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 PSTNSlj m~;' be sent
`to the caller, otherwise the full PSTN number may be sent to the caller as the diverted call
`
`8-3
`
`I I I I I I I I I I I I I I I I I I I I I
`
`Petitioner Cox Communications - Exhibit 1007 Page 29
`
`
`
`I I I I I I I I I I I I I I I I I I I I I
`
`destination.
`
`Call diversion requests from either self·interested panies or third panies may displace earlier
`requests set up by either method.
`
`8.3.2
`
`Cancel Diversion
`
`A cancel diversion request (RQT, DIY = '1', FLAG 2 = '0') cancels the diversion state for
`the unit whose address is PFIX/IDENT1, or the address data received in response to an
`AHYC sent by the system if IDENTI = IPFIXI.
`
`8.4
`
`Storage Requirements
`
`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 %% rEI);
`
`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.1.1 %%);
`
`for
`
`translation from PSTNSlj
`
`(8121 to 8135)
`
`Up to 34 network defined numbers or facilities for translation from spare !DENTs
`8136 to 8169 (%%8.2.8.1.1%%);
`
`Up to 11 sets of routing data for network operator services for translation from spare
`!DENTs 8170 to 8180 (%%8.2.7%%);
`
`The following storage reqvirements are requested for each call diversion interception:
`
`a.
`
`b.
`
`c.
`
`Diverted party address;
`
`Diversion destination;
`
`Divert Speech/Divert Data flags.
`
`8-4
`
`Petitioner Cox Communications - Exhibit 1007 Page 30
`
`
`
`CONTROL CHANNEL OPERATION
`
`Control Channel Availability
`
`.1
`
`9 9
`
`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