C)F<:aI'rI
`
`Kncm ledp.<- (‘t*I1|r+'
`
`R um ILH.\I\H'.\iL \ I It ‘\~
`-‘sh! \t\
`
`
`
` :_ ____
`
`.
`
`'
`
`fh
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 1
`'
`e Radlotammunuzauons Agency -5 an Eaecutwe Agency of the Department at Trade and Industry
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 1
`
`

`
`System Interface Specification for
`radio units to be used with co1iiI1'A1t_fif_c.|_:;ilV-4 -'
`_ trunked networks operating in Bafi"%diI]_IIL-.
`sub-bands 1 and 2 - W
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 2
`
`

`
`Crown Copyright 1988
`
`First Published 1988
`
`Revised and reprinted September 1991
`
`
`
`
`
`ISBN 1-870837-41-X
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 3
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 3
`
`

`
`
`
`.
`
`FOREWORD
`
`This specification contains the minimum performance requirements additional to MPT I323
`to be met by radio units used with commercial tnrnked networks operating in Band 111, sub-
`bands 1 and 2. A companion specification, MPT 1347, contains the additional minimum
`performance requirements to be met by network fixed equipment. Together these common
`specifications are intended to allow a user to migrate from one trunked radio network to
`another without having to change radio equipment.
`
`It should be noted that some aspects of the specification remain relatively unproven
`operationally. All reasonable efforts have been made to ensure accuracy, but it may prove
`necessary to amend some sections in the light of practical experience. An example is the
`way that the radio unit caters for time-shared and discontinuous control channels.
`
`In§gllg;t1_rgl Property Rights
`
`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.
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 4
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 4
`
`

`
`Page
`
`1-]
`
`2-1
`
`3-1
`
`3-9
`
`3-9
`
`4-1
`4-2
`4-3
`
`5 1
`
`5 2
`5-3
`5 3
`
`6- 1
`
`6-1
`6-2
`
`7-1
`
`8-1
`8-10
`8-39
`
`9-1
`9-2
`9-5
`9-34
`9-38
`
`10-1
`10-1
`10-8
`
`CONTENTS
`
`1.
`
`2.
`
`3.
`
`SCOPE
`
`ASSOCIATED DOCUMENTS
`
`GENERAL
`
`3.1
`
`3.2
`
`3.3
`
`Definitions
`
`Test Conditions
`
`General Requirements
`
`4.
`
`TRANSMITTER PARAMETERS
`
`4.1
`4.2
`4.3
`
`Frequency Parameters
`Modulation Characteristics
`Performance Parameters
`
`5.
`
`RECEIVER PARAMETERS
`
`6.
`
`7.
`
`8.
`
`9.
`
`5. 1
`Frequency Parameters
`5.2
`Demodulation Characteristics
`5.3 Muting
`5.4
`Performance Parameters
`
`STORAGE REQUIREMENTS
`6. 1
`Introduction
`
`6.2
`6.3
`
`Types of Memory
`Summary of Storage Requirements
`
`SECURITY
`
`MAN-MACHINE INTERFACE
`
`8. I
`8.2
`8.3
`
`Confidence Indications
`Call Number Convention
`Ready for Communication Control
`
`CONTROL CHANNEL ACQUISITION AND RETENTION
`9. I
`Introduction
`9.2
`Radio Unit Storage Requirements
`9.3
`Control Channel Acquisition Procedures
`9.4
`Leaving a Control channel
`9.5
`Multiple Control Channels
`
`10.
`
`REGISTRATION
`
`10.1 General
`10.2
`Single Registration
`10.3 Multiple Registration
`
`iii
`
` E
`
`ii»
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 5
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 5
`
`

`
`
`
`-
`
`‘
`
`1 1.
`
`CALL PROCESSING
`
`Introduction
`11. 1
`1 1.2 Definitions
`
`Signalling Fonnats
`11.3
`11.4 Addressing
`11.5 Codeword Structure
`
`11.6 Channel Discipline
`11.7 Random Access Protocol
`
`11.8 Registration Procedures
`11.9 Basic Call Procedures
`
`11.10 Emergency C311 Procedures
`11.11 Include Call Procedures
`
`11.12 Call Diversion Procedures
`
`11.13 Status Message Procedures
`11.14 Short Data Message Procedures
`11.15 Data Interrogation Procedures
`11.16 Not Used
`
`11.17 Standard Data procedures
`
`12.
`
`NON-STANDARD DATA INTERFACE PROVISION
`
`12.1 Muting
`12.2 Maladjustment
`12.3
`Facilities
`
`12.4 Data Ca11 Handling
`12.5
`Facilities
`
`13.
`
`FALL-BACK MODE
`
`13. 1
`
`13.2
`13.3
`13.4
`
`Introduction
`
`Storage Requirements
`Entering Fall-back Mode
`Procedures in Fall-back Mode
`
`Leaving Fall-back Mode
`13.5
`13.6 User lnitiated Change of Network
`
`14.
`
`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
`Procedure for Radio units
`
`14-5 An Example of the Procedures for Extended Data Messages
`
`iii"
`
`ERROR PERFORMANCE REQUIREMENTS
`APPENDIX A
`Definition
`A. 1
`A.2 Method of Measurement
`A.3
`Limits
`
`1 1-1
`1 1-4
`
`11-4
`11-5
`1 1-6
`
`11-18
`11-20
`
`11-21
`11-23
`
`11-31
`11-31
`
`11-32
`
`11-32
`11-32
`11-32
`11-33
`
`11.33
`
`12-1
`12-1
`12-1
`
`12-1
`12-2
`
`13-1
`
`13-1
`13-1
`13-2
`
`13-3
`13-4
`
`14-1
`
`14-2
`14-9
`14-10
`
`14-17
`
`A-1
`A-1
`A-3
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 6
`
`iv
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 6
`
`

`
` B.l
`
`APPENDIX B
`
`B.2
`
`TIMING AND DEFAULT PARAMETERS
`
`Default Parameters
`
`Timing Parameters
`
`B-1
`
`B-2
`
`AN-1
`
`ANNEX
`
`AN] Clarification of Radio Unit Operation on Time Shared
`Control Channels
`
`-
`
`Comprehansive Hunt Sequence has been entered
`
`AN—2
`
`AN2 Recommendation for Radio Unit Behaviour once the
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 7
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 7
`
`

`
`SCOPE 1.1
`
`1 .
`
`This specification covers the minimum performance requirements for radio
`units used with commercial trunked networks operating in Band 111. sub-bands I and 2.
`It
`covers:
`
`==.-,r‘~“':‘= “
`
`It
`
`—
`
`—
`
`-
`
`-
`
`1.2
`
`signalling requirements based upon the standard MPT 1327.
`
`MPT 1343 is designed to be read in association with MP1" 1327.
`
`radio frequency requirements, where they are additional
`MPT 1323.
`
`to those in
`
`interface requirements, where advantages are to be gained from
`user
`standardisation.
`
`The specification includes two types of requirement:
`
`those that are mandatory in all radio units.
`
`those that are optional in a radio unit, but shall be implemented in a standard
`manner.
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 8
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 8
`
`

`
`
`
`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 band
`174-225 MHz.
`
`MPT 1327 (1988)
`
`A signalling standard for trunked private land mobile radio systems.
`
`MPT 1331 (1987)
`
`Code of practice for radio site engineering.
`
`tie-it-,
`
`MPT 1347 (1988)
`
`specification for commercial
`Radio interface
`operating in Band III sub-bands l and 2.
`
`trunked networks
`
`MPT 1352 (1991)
`
`the approval of radio units to be used with
`schedule for
`Test
`commercial trunked networks operating in Band Ill sub-bands I and 2.
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 9
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 9
`
`

`
`
`
`(I
`
`_
`
`'
`
`-
`
`’-"
`
`'“
`
`3.
`
`3-1
`
`GENERAL
`
`D_0l";fltioL§
`
`Section numbers appearing between !!
`numbers within MPT 1327.
`
`!! delimiters in this specification refer to section
`
`Words appearing between asterisks in this section are defined terms.
`
`The condition obtained by the successful completion of the *control channel
`acquisition prooedure* for a control channel which allows a radio unit to transmit on that
`channel.
`
`‘Network personalisation‘ data which enables the ‘radio
`;;\_9gujsitiQn Authorisation Data:
`unit* to determine by examination of the relevant sub-fields within a ‘system identity code*
`received on a *cont.rol channel‘ whether the *radio unit* is authorised to access on that
`*control channel''‘.
`
`Active on a Channel: A *radio unit* is *active on a channel* when, on that channel, it is
`enabled to respond to *messages* addressed to it, or is transmitting, or is in transition
`between the two states.
`
`Note: a *radio unit* becomes active on an assigned *traffic channel* as soon as it can
`receive on that channel, whereas, on a ‘control channel* it shall not become active
`until it has received a codeword containing an appropriate ‘system identity code"‘.
`
`Adgrgsz A 20-bit number by which a unit or group of units is known within a *system“‘.
`The *address* comprises two *fields*; a 7-bit *prefix* and a 13-bit "'ident*.
`
`Adgmss Qggeword: A 64-bit codeword, conforming to the requirements of MPT 1327,
`where the first bit is set to '1‘. An *address codeword‘ is always the first codeword in any
`*message*, and defines the nature of the *message*.
`
`If the *trunking system controller‘ implements such a
`Available fior Custgmigtignz
`customised function, then if the ‘radio unit* implements the function it shall respond in the
`manner specified by the network operator of that ‘trunking system controller‘.
`Such
`functions will not modify existing standardised functions.
`If the radio unit does not
`understand the customised function in the context of a *system* it is currently using, then
`it shall ingnore that function. The ‘radio unit* shall not infringe any of the requirements of
`section 5 of MP1‘ 132?.
`
` : The entirety of transmitters and receivers operated by a flrunldng system
`controller‘ at any one site.
`
`gall: A complete information exchange between two or more "‘parties* which includes one
`or more *t:ransactions"‘ and may include direct user-to-user communication on a '‘‘traffic
`channel‘.
`
`31
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 10
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 10
`
`

`
`
`
`
`
`
`
`
`
` : The unit, or group of units, which a ‘calling unit* identifies as the
`desired recipient(s) of a *call"'. The ‘called unit (or group)* retains this designation for the
`duration of the *call* and this convention is used in messages relating to that particular “'cal1*
`irrespective of the origin of such ‘messages’.
`
`ggalling glnit: A *radio unit* or *line unit* which requests a "‘call*. The *calling unit‘
`retains this designation for the duration of a "‘call* and this convention is used in *messages*
`relating to that particular *call“' irrespective of the origins of such "messages*.
`
`: A *call‘." where the values of the ‘prefixes’ in the calling and called
`fix
`mon
`*addresses"' are the same. *Comrnon prefix calls* use ‘short addressing‘ procedures.
`
` : A procedure employed by the ‘radio unit‘ to facilitate the selection of an
`appropriate ‘control channel‘ to‘ allow a ‘session’ with a "system" to be initiated or
`continued. The *confirmation"‘ process consists of applying prescribed tests to the signal
`content of the received “‘forward channe1*.
`
` : A designation given to the *radio unit* during *network personalisation"‘
`which governs that unit's right of access to *control channels“ radiated by that *network*.
`A "'radio unit‘ shall only access a *control channel* when the value of the LAB field in the
`*system identity code* indicates that the unit's *control category* is permitted to use that
`channel.
`
`Qgntrol Channel: A *forward channel* and *return channel* being used for the transmission
`of *messages* conforming to MP1‘ 1327 with the primary purpose of enabling the *trunking
`system controller‘ to control ‘radio units*.
`
`gggggl g;har_inel Amuisitigg mute: A procedure employed by the ‘radio unit* to select
`an appropriate *control channel* to allow a *session* with a *system* to be initiated or
`continued. The procedure consists of "‘hunting* for candidate ‘control channels* which are
`submitted to *confin'nation* tests to determine if *acquisition* is permitted.
`*Hunting*
`continues until such time as a successful *acquisition* is confirmed.
`
` : A 64-bit codeword, conforming to the requirements of MP1‘ 1327, where
`the first bit is set to '0'. *Data codewords* are concatenated to an ‘address codeword* and
`
`supplement the information in the *address codeword*.
`
` : A transmitted codeword shall be considered “decodable“‘ if, after receipt, and
`after error correction (see Section 11.3.2.3) has been applied, a valid codeword from the
`(64,48) code defined in section 3.2.3 of MPT 1327 is formed.
`
` : A procedure whereby a *party* may request that future "'calls"' to a particular
`called *address* be directed to an alternative destination.
`
`Explicit Registration: A *registration"‘ achieved by means of an RQR message.
`
`Extended Addressing: A method which allows called “‘party“' details to be conveyed to the
`"‘trunking system controller’ when the "call* details cannot be accommodated in a single
`
`3-2
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 11
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 11
`
`

`
`
`
`
`
`These called-party details may be an ‘address’ or addressing
`*address oodeword*.
`information in a different font: (eg PSTN dialling digits).
`
`Fg;1—back Mode: A customised form of operation which may be used by a *network“‘
`suffering equipment malfunction,
`
`F_iel;1: A number of contiguous bits in a codeword which is specified in terms of the position
`within the codeword and the number of bits.
`
`Fixgj mm Llnit: A *radio unit‘ used with its antenna at a fixed location.
`
`Forward Qhgnnglz A radio bearer where the direction of transmission is from the *trunl<ing
`system controller‘ to the ‘radio units*.
`
`Ffi Fgrmgt Dag: Data within a codeword which, in this specification, is constrained only
`by its position and length.
`
`ident* which is used to identify a *message* relating to a *call or
`gateway: A *special
`transaction* to or from a communications service outside the *system* (eg the PSTN). For
`the purpose of this specification the interprefix *ident"‘, IPFIXI,
`is also regarded as a
`*gateway*.
`
` : An *address* which is common to more than one unit and which, when
`nominated as the called *address"‘, signifies a *group caIl*. Units may be assigned any
`practicable number of *group addresses*.
`
` : A "‘call* in which a ‘group address’ is specified as the called “‘party* and,
`accordingly, provides a means of communication between more than two units. The calling
`*party* in a ‘group call‘ may opt for a conversational mode. where all “‘parties* are able
`to speak, or for an announcement mode where only the caller may speak.
`
`Hgd Message: Single transmission of an MPT 1327 HEAD *address codeword* and its
`appended *data codewords*.
`
`Hunting: A procedure employed by the *radio unit* to facilitate the selection of an
`appropriate *control channel"‘ to allow a *session* with a *system* to be initiated or
`continued. The "‘hunting* process consists of systematic sampling of the *forward channel*
`frequencies by the ‘radio unit* until it selects and ‘'‘confirms* one of the ‘forward channels*.
`which together with its paired "‘retum channel‘ is an appropriate ‘control channel*.
`
` : A procedure employed by the *radio unit‘ during *hunting* which
`consists of one or more *hunting stages*. There are five described ‘hunting sequences‘:
`
`"Resurning a control channel sequence"
`(a)
`(b) "Single channel hunt sequence"
`(c)
`"Preferential hunt sequence”
`(d) “Nomial hunt sequence"
`(e) “Comprehensive hunt sequence"
`
`3-3
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 12
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 12
`
`

`
`
`
`A *hunting sequence* iscompleted when all *hunting stages* appropriate to that *hunting
`sequence"‘ have been completed or, prior to this,
`if a successful *control channel*
`*confirmation* is achieved.
`
`Hunting Stage: A procedure employed by the "‘radio unit* during *hunting* which consists
`of sampling all channel numbers applicable to the type of *hunting sequence* in progress at
`a particular acquisition threshold level. A *hunting stage"' is completed when all channel
`numbers applicable have been sampled and *confirmation* attempted on any candidate .
`''‘control channels* located or may be completed prior to this if a successful *control
`channel* *confirrnation* is achieved.
`
`'
`
`Ldemt: A 13-bit number used for identification purposes. Values of *ident* between 1 and
`8100 inclusive are assigned to individual units or groups (see section 8.2), in which case they
`are associated with a *prefix* to form a 20-bit address. Values of *ident* above 8100 are
`designated *specia1 idents* and these are not associated with any particular *prefix*, nor is
`the *ident* value 0 (DUMMYI).
`
`Idle State: A *radio unit* is in the *idle state* on a *system* when it is "‘active on a
`channel*,
`is receiving on an appropriate *control channel* from the *system*,
`is not
`currently within a *message* exchange and has no current *message* transfer requirement.
`
`Implicit Registration: A *registration* achieved by means other than an RQR message and
`associated Acknowledgement message from the *network*.
`
`Ingludez A procedure whereby *parties* may be introduced into a *call* in progress at the
`request of an existing *party* to the *call*.
`
`Individual Addres§:- An *address* by which a single unit is known within a *system*,
`allowing that unit to be uniquely addressed by that *system*. Units may be assigned any
`practicable number of *individual addresses‘ provided that at least one is assigned to each
`unit.
`
`Indivi ual
`
`all: A *call* between a calling *party* and a single called *party*.
`
`Interprefix gall: A *call* where the values of the *prefixes* in the calling and called
`*addresses* are different. *Interprefix cal1s* require *extended addressing* procedures.
`
`Item: A complete user transmission on a traffic channel by one *party"‘ within a *call* at the
`conclusion of which that *party"' rests from transmission.
`It is possible for a "‘call* to .
`contain only one *item*.
`
`Line unit (LU): A user station which is allocated an *individual address"‘ and is directly
`connected to a *trunlcing system controller* via a medium other than that part of the radio
`spectrum to which this specification applies.
`
`Mggtoryz The *radio unit* shall implement the function or facility.
`
`Mesgge: A single contiguous data transmission which consists of
`
`a. codeword
`
`3-4
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 13
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 13
`
`

`
`
`
`synchronisation sequence, an ‘address codeword‘ and (optionally) one or more ‘data
`codewords‘ conforming to MP1‘ 1327.
`
`Ngmorkz Interconnected "‘systems"‘.
`
` : A procedure undertaken when a subscription to "‘network* is taken
`out by a user whereby that user's ‘radio units‘ are implanted with data to enable it to
`function correctly on that *network"'. *Radio units‘ which are required to access more than
`one *network"' shall be personalised for each *network* to be accessed.
`
` : A procedure which may be adopted by a ‘trunking system controller*
`whereby channels used by the *system"‘ may be flexibly allocated as ‘control channels‘ or
`*traffic channels‘ depending on the traffic load on the ‘system’. When this procedure is
`employed, the current *control channel"‘ would nonnally be allocated as a "'uaffic channel*
`when all other channels are in use for traffic and the ‘control channel‘ facility restored when
`possible, eg by allocating the next *traffic channei* to become free as a new ‘control
`channel*.
`
`_
`
`.;
`
`;
`
`
`
`Ngrhprescrihg data: Any data traffic which does not conform to the data protocols defined
`in MP1‘ 1327.
`
` : The operation mode of a ‘radio unit* or *control channel* which
`is not in the *fall-back mode*.
`
`Norma Rggisgatign Mode: A *control channel* mode in which the *network"' will accept
`and maintain *registration* requests.
`
`record which has an indication that
`Nogial Registration Rgordz A *registration"‘
`*network* is maintaining the *registration“' record.
`
`the
`
`' n R
`Null Re i
`with the AREA code.
`
`rd: A *registration* record which includes a NULL indicator together
`
`Party: A source and/or recipient of information within a *call"‘. The term includes the
`totality of equipment at the user station and, where the context permits, the equipment user.
`A *party* may be an individual or a group.
`
`Pgrsgnalityz The totality of *network personalisation‘ data entered into the *radio unit*.
`
` : A portable radio unit is distinguished from any other radio unit by the
`following cn'ten'a:-
`
`-
`
`—
`-
`
`the equipment covered is intended to be used only with an integral antenna, which
`may be detachable. When this equipment is used with a non-integral antenna it ceases
`to be defined as a portable radio unit for the purpose of this specification;
`
`the maximum effective radiated power shall not exceed 5 watts;
`the equipment shall be powered by a self contained battery unit.
`
`3-5
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 14
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 14
`
`

`
`
`
`
`
`
`
`mm: The 7 most significant bits of an *address*. Normally units within a fleet will be
`allocated the same "‘prefix“‘ since ‘calls’ between units and groups with the same "'prefix"'
`can be made without the use of ‘extended addressing‘ procedures. A *prefix* is only
`relevant to ‘individual addresses* and *group addresses‘.
`
`Prime Regjsfltjgn Rfird: The most recently created *registration* record held by the -
`*radio unit‘. Note that the ‘prime registration record‘ does not include timing information.
`
`&_g'g unit (RU): A mobile or other user station contacting a "system* by normal land
`mobile radio in accordance with the specification.
`
` : The method by which a "‘radio unit* transmits an unsolicited
`"‘message* to the *I:runlcing system controller‘ on a *control channel*. The method requires
`that a *radio unit* repeats a random access "message* if a response *message* is not
`received within a designated waiting time. Further repeats are required, in the absence of
`an appropriate acknowledgement, until a
`In this specification a ‘random access attempt“
`designated number of repeats is reached.
`covers the period from initiation of the "‘transaction* to the receipt of an appropriate
`acknowledgement or the expiry of a timeout.
`
`Rgidggnly Memory: A storage facility within the *radio unit* which contains *network
`personalisation* data. The contents of the *read-only memory"' cannot be modified or added
`to by the action of the *radio unit* or its user.
`It is intended that the contents of *read-only
`memory* are placed there only during *network personalisation* by a suitably authorised
`agent (normally a service provider).
`
`Read/Write Memggyz a storage facility within the *radio unit* the contents of which may be
`modified by the ‘radio unit*.
`
`Ray for Communication Qgntrgl (RFCC): A device or system to inform a unit of the user's
`readiness to communicate (see section 8.3).
`
`Registration: A procedure which confirms that a ‘radio unit* is in a *session* on a
`*system*. The *registration* procedures may be initiated by a demand from the *trunking
`system controller‘, or at the initiative of the ‘radio unit‘, depending on the circumstances
`of the registration.
`
`Ragga unit (or Qmup): A unit, or group of units, which takes part in a *transaction*
`initiated by the ‘trunking system controller‘ or another "‘party*.
`
`Rmggg-5_1;’ng unit: A *radio unit‘ or ‘line unit‘ which initiates a *transaction* with the
`“Trunking system controller‘ or another "party*, via the *trunldng system controller’.
`
`gesgriql: Codewords and '''fields* which are designated as *reserved* in MPT 1327 are
`intended for future phases of standardisation and shall not be used in the interim for the
`conveyance of information.
`"‘Reserved fields‘ must be set to the default value specified in
`MP1‘ 1327.
`
`3-6
`
`-'E: .5.
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 15
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 15
`
`

`
`
`
` : A radio bearer where the direction of transmission is from ‘radio units‘ to
`the ‘trunking system controller‘.
`
`Segment: For a known ‘transaction’, the portion of the "1'-message‘ contained in a ‘HEAD
`message‘.
`
`gglecteg Network: The ‘network‘ which the user of the ‘radio unit‘ has selected for the
`time being and which is the only *network* that the ‘radio unit‘ may attempt to access until
`such time as the user designates a new *selectcd network‘. Where the ‘radio unit‘ does not
`allow the user to select from a choice of ‘networlts* then only one ‘network* shall be
`available to that ‘radio unit‘ for access and this "network" shall be. per se, the ‘selected
`network‘.
`
`gig: A ‘session* is a period of operation associated with one ‘system‘. A ‘session‘ on
`a ‘system* starts when a ‘radio unit‘ becomes ‘active on a control channel‘ of that
`‘system‘, either after switch on or after being ‘active on a control channel‘ of a different
`‘system‘. A *session* ends either when the ‘radio unit‘ is switched off or when it starts
`its next ‘session"‘.
`
`Shog Addressing: The method used when the *parties‘ to a "‘call"‘ can be completely
`specified by a single *prefix* and two *idents*. This form of addressing minimises the
`signalling required.
`
`Shgrt Dag,: A procedure which allows a data *message‘ to be exchanged between *parties*
`or between ‘parties* and the ‘trunking system controller‘. This procedure does not support
`‘messages‘ which include more than four ‘data codewords‘.
`
`Short-Form P§TN Destinajgn: A called PSTN ‘party‘ previously agreed between the system
`operator and the user of the ‘caning unit‘ which can be specified by a ‘special idem‘ rather
`than the full stream of dialling digits representing the directory number.
`
`§ingle gggmegt Trangction (§§f1f): Short data ‘transaction‘ requiring only one *segment‘.
`
`figs: Codewords and *fields‘ which are designated *spare* are available for free use by
`“‘systems* (ie "‘system* customisation) provided that the conditions of MP1‘ 1327 are not
`infringed. The use of *spare"‘ codewords and ‘fields* may vary from ‘system* to ‘system*.
`
` : An *ident* with a value greater than 8100. These *idents* are used for a
`variety of special purposes.
`Some of these are specified in MPT 132?, others may be
`nominated by system operators.
`‘Special idents‘ are not associated with a ‘prefix* to form
`an "address‘.
`
` : A ‘ca.ll* as a result of the receipt of a GTC *message’'‘ with the ‘D‘ *field* set
`to '0‘. The audio is not muted.
`
` : The procedure by which information exchange takes place using the data
`protocol defined in section 17 of MP1‘ 1327.
`_
`
`3-7
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 16
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 16
`
`

`
`
`
` : Any optional feature for which the implementation has been standardised
`in MP1‘ 1327. Any unit implementing such an option shall implement it at least in the
`specified standardised manner.
`Units and *systems"‘ shall not
`infringe any of the
`standardised formats in MPT 1327 when implementing customised features.
`
`System: The totality of equipment required to provide the communication facilities at one .
`location, associated with one or more "‘system identity codes*. "‘Systems* may be combined
`to form larger communications facilities.
`
` : A 15-bit number which identifies a *system*. This code is radiated
`on each *forward control channel* within the “‘system* (in the SYS *field*).
`
` : totality of “‘free—format data* which is intended to be conveyed in a ‘short data*
`*transaction*.
`
` : A *control channel* mode in which the *network* will accept
`but may not maintain *registration* requests. The *radio unit* may be required to re-
`register when the *normal registration mode"' is resumed.
`
`Temporary Registgtjon Record: A "‘registration* record which has an indication that the
`"‘networl<* may not be maintaining the *registration* record.
`
`: A *registration"' record held by the *radio unit*, that has been
`R
`R ' trati
`Ti
`displaced from the ’'‘prime registration record‘. The record has a timer TD associated with
`it.
`
`Traffig Qhgnel: A *forward channel* and *retum channel* being used primarily for user
`communications.
`
`
`
`Tgaggtignz A complete information exchange consisting of one or more *messages*
`between a “‘party* and the "'trunking system controller*, or another *party*, via the
`‘trunking system controller*.
`
`Tginldng Sysgm Qgntrgller (TSC): The central control intelligence necessary to enable the
`trunking system to function according to MPT 1327. The "‘trun1dng system controller* may
`control one or more "'base stations*.
`
` : A *registration* record which has no indication that the
`"‘network"‘ may or may not be maintaining the *registration“ record.
`
` : The AREA subfield of the received *system identity code* (SYS) used
`to verify a *control channel*.
`
`Vgrifigj §IL fie: The SIL field of the *system identity code‘ (SYS) received and verified
`by a ‘radio unit* from the ‘control channel* on which that *radio unit* was most recently
`*active*.
`
`3-8
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 17
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 17
`
`

`
`3.2
`
`T3 Congi;iQn_s_
`
`Unless otherwise specified, the *radio unit‘ shall meet the requirements of this specification
`under extreme test conditions, as defined in MPT 1323 section 2.4
`
`3.3
`
`General Rguigments
`
`The ‘radio unit"' shall not operate duplex.
`
`The facility to switch from one “‘network" to another is a "‘standard option*.
`
`it is *mandatory* that *network* switching shall be under control of the
`If implemented,
`user. Autonomous switching between *networks* by the *radio unit* shall not be permitted.
`
`It shall be possible to transfer, between *network(s)* in a *radio unit* by changing the
`*personality* (see section 6).
`
`3-9
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 18
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 18
`
`

`
`5.13
`
`_F_res1uen9xlolerana;
`
`The centre frequency of the response of the radio receiver shall be within 1.5 kHz of the
`nominal receive frequency except during channel switching.
`
`This tolerance includes crystal ageing and shall be maintained under both nonnal and extreme
`temperature conditions, as defined in MPT 1323 sections 2 and 3, for a period of at least one
`year, without re-adjustment.
`
`5-2
`
`5-2-1 S
`
`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. The radio unit shall be deemed to have passed
`this requirement if it meets the permitted departure either at the electrical connections to the
`loudspeaker (with a suitable resistive load if the loudspeaker is disconnected), or acoustically.
`
`I
`I
`I
`I
`/I////////////////I//H
`
`/ /
`
`/////////////////////H
`
`Amplitude relative
`to optimum phase
`demodulator response
`
`1‘
`6 dB
`1
`
`100
`
`300
`
`1000
`
`2550
`
`10000
`
`Input Frequency Hz
`
`Figure 5.1
`
`5.2.2
`
`D
`
`Si n
`
`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‘.
`Units shall meet the error performance requirements of Appendix A of this specification.
`
`Note: The received peak deviation of standard data does not exceed i2.0 kHz and is not
`less than ;|-_1.0 kHz. For non-prescribed data, the peak frequency deviation does not
`exceed _-t;2.5 Id-lz.
`
` 3
`
`_:_.‘
`159 3* -“ 5
`
`ewfimfi
`
`én———__..
`
`-a-24»
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 19
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 19
`
`

`
` 5. RECEIVER PARAMETERS
`
`The requirements of this section shall be met under normal
`MPT 1323 section 2.3, unless othenvise specified.
`
`test conditions, as defined in
`
`5.1
`
`Frmuengy Parameters
`
`This section contains the frequency parameters for radio units operating in Band 111 sub-bands
`1 and 2.
`
`All radio units shall operate on any of the channels in the frequency range to which they are
`directed by network messages and shall examine and if necessary; operate on that channel,
`in that range,
`in accordance with the procedures specified in Section 9. If directed by
`network messages to any channel outside this range, radio units shall not comply with the
`messages and shall remain on the channel from which the message was sent-.
`
`5.1.1
`
`Channel Spacing and Designations for Sub-band 1
`
`The channel spacing shall be 12.5 kHz. The channel designations shall be as follows:
`
`Channel Number
`
`CHAN field binary
`representation of
`channel number
`
`Radio Unit
`Receive Frequency
`
`176.5000 MHz
`
`1000000001
`
`177.2125 MHz
`
`.
`
`1
`
`58
`
`560
`
`1111110111
`
`183.4875 MHz
`
`
`
`The radio equipment shall receive over channels 58 to 560 ( 177.2125 MHz to 183.4875
`MI-Iz) inclusively.
`
`5.1.2
`
`Channel spacing and designations 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
`
`Radio Unit
`Receive Frequency
`
`200.5000 MHz
`
`0000000001
`
`201.2125 MHz
`
`1
`
`58
`
`560
`
`0111110111
`
`207.4875 MHz
`
`The radio equipment shall receive over channels 58 to 560 (201.2125 MHz to 207.4875
`MI-lz) inclusively.
`.
`
`5-1
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 20
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 20
`
`

`
`4.2.3.2
`
`Dgta Peak Deviagign
`
`For standard data modulation.
`
`Angle modulation:
`
`