throbber

`
`“Ff-31;
`.-
`.
`'-.
`_
`:4wr1im134 r.
`p-
`,1_.
`Lv‘ii
`ultra 1n
`.4 ‘ -- -' Performance Specification
`
`-
`
`.
`
`1
`
`System Interface Specification for
`radio units to be used with commercial
`
`trunked networks operating in Band III
`-
`sub-bands 1 and 2
`
`January 1988
`
`Revised and reprinted September 1991
`
`EXHIBIT
`
`
`
`ARRIS GROUP, mc.
`IPR201 5-00635 , p. 1
`Hip H...rlu1cr_lmmnnu.r1lu'ur-' Asp-an: .
`
`.... F -t-- u'lr: {any-I141 ul FII.-.jln-=._..-lrn.xnl
`
`' Twill,
`
`.' -'.llll_||,|,|:y
`
`

`

`MPT 1343
`
`System Interface Specification for
`radio units to be used with commercial-f".--'.
`trunked networks operating in Band III
`sub-bands 1 and 2
`"
`
`Revised and reprinted September1991
`
`January 1988
`
`_r-~..
`
`

`

`Crown Copyright 1988
`
`First Published 1988
`
`Revised and reprinted September 199}
`
`ISBN 1—870837—4 l-X
`
`ARRIS GROUP, INC.
`IPR2015-00635 , p. 3
`
`
`

`

`
`
`t
`
`FOREWORD
`
`This specification contains the minimum performance requirements additional to MVP 1323
`to he met by radio units used with cumrnerctal Lrurtked networks operating in Band LII. sub—
`bands I 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 specitiaiu'on 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 Lhe
`way that the radio unit caters for time-shared and discontinuous control channels.
`
`Intellectual 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.
`
`All firms are therefore advised that they should make appropriate enquiries through
`their Patent Agents before proceeding.
`
`ii
`
`ARRIS GROUP, INC.
`IPR2015-00635 , p. 4
`
`
`

`

`
`
`CONTENTS
`
`l.
`
`SCDPE
`
`ASSOCIATED DOCUMENTS
`
`GENERAL
`
`3. 1
`
`3.2
`
`3.3
`
`Definitions
`
`Test Conditions
`
`General Requirements
`
`TRANSMITTER PARAMETERS
`
`4.1
`4.2
`4.3
`
`Frequency Parameters
`Modulation Characteristics
`Performance Parameters
`
`RECEIVER PARAMETERS
`
`5.1
`5.2
`
`5.3
`5.4
`
`Frequency Parameters
`Demodulation Characteristics
`
`Muting
`Performance Parameters
`
`STORAGE REQUIREMENTS
`6. 1
`Introduction
`
`6.2
`6.3
`
`Types of Memory
`Summary of Storage Requirements
`
`SECURITY
`
`MAN—MACHINE INTERFACE
`
`8.1
`8.2
`
`8.3
`
`Confidence Indications
`Call Number Convention
`
`Ready for Communication Control
`
`CONTROL CHANNEL ACQUISITION AND RETENTION
`9. l
`IntIoducLion
`
`9.2
`9.3
`9.4
`9.5
`
`Radio Unit Storage Requirements
`Control Channel Acquisition Procedures
`Leaving a Control channel
`Multiple Control Channels
`
`10.
`
`REGISTRATION
`10.1 General
`
`Single Registration
`10.2
`10.3 Multiple Registration
`
`ARRIS GROUP, INC.
`IPR2015-00635 , p. 5
`
`Page
`
`E
`
`-
`
`|
`
`2-1
`
`3-1
`
`3-9
`
`3—9
`
`4-1
`4-2
`4-3
`
`5-1
`5-2
`
`53
`5-3
`
`6-1
`
`6-1
`(3-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
`
`

`

` 11.
`
`-
`
`1“
`
`m
`rag-$5;
`
`'
`
`CALL PROCESSlNG
`
`11.1
`
`Introduction
`
`11.2 Definitions
`
`Signalling {Tanners
`11.3
`11.4 Addressing
`11.5
`Codeword Structure
`
`Channel Discipline
`11.6
`11.7 Random Access Protocol
`
`1 1.3 Registration Procedures
`| 1.9
`Basic Cal! 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 Message Procedures
`1 1.15 Data Interrogation Procedures
`11.16 Not Used
`
`11.17 Standard Data procedures
`
`12.
`
`NON—STANDARD DATA LNTERFACE PROWSION
`
`12. 1 Muting
`12.2 MaJadjustment
`12.3
`Facilities
`
`12.4 Data Call Handling
`12.5
`Facilities
`
`13.
`
`FALL—BACK MODE
`13.1
`Introduction
`
`Storage Requirements
`13.2
`Entering Fall-back Mode
`13.3
`Procedures in Fallback Mode
`13.4
`Leaving Fall-back Mode
`13.5
`13.6 User Initiated 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 Field-s For STF = '1'
`[44
`Procedure for Radio units
`
`11 .
`
`t
`
`“-4
`
`11-4
`11—5
`11—6
`
`11—18
`11—21]
`
`11-21
`1 1Q}?
`
`11-31
`“-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
`[3-1
`13-2
`[3-3
`13-4
`
`14-1
`
`142
`14-9
`14-10
`
`14—5
`
`An Example of the Procedures for Extended Data Messages
`
`14—17
`
`ERROR PERFORMANCE REQUIREMENTS
`APPENDIX A
`Definition
`A. 1
`A.2 Method of l‘vleasurement
`A.3
`Limits
`
`A- 1
`A-l
`A—3
`
`ARRIS GROUP, mc.
`IPR2015-00635 , p. 6
`
`
`

`

`
`
`APPENDIX B
`B.1
`
`TIMING AND DEFAULT PARAMETERS
`Default Parameters
`
`3.2
`
`Timing Parameters
`
`ANNEX
`
`ANi
`
`Clarification of Radio Unit Open-innit t1” 'I‘irnc- Shared
`Control (“name-IS.
`
`B-I
`
`B-2
`
`AN-I
`
`AN2 Recommendation for Radio Unit Behaviour once the
`
`Comprehansive Hunt Sequence has been entered
`
`:‘tN-E
`
`ARRIS GROUP, INC.
`IPR2015-00635 , p. 7
`
`
`

`

`
`
`1.
`
`SCOPE
`
`This specification covers the minimum performance requirements for radio
`1.]
`units used with commercial trunked networks imperating in Band III. Huh—hands l and 2.
`It
`cox-era:
`
`signalling requirements based upon tin: standard ,MPT 133?.
`
`MPT 1343 is designed to be read in association with MPT 132?.
`
`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.
`
`1.2
`
`-
`
`-
`
`IPR2015-00635 , p. 3
`
`ARRIS GROUP, INC.
`
`

`

`2.
`
`ASSOCIATED DOCUNI'ENTS
`
`MI’l‘ 1:117 (1981)
`
`Code of practice for the transmissmn of digital information over land
`mobile radio systems.
`
`MP'I‘ 1318 (1986l
`
`Engmeering memorandum: Trunked systems in the land mobile
`service.
`
`MP’I'
`
`i323 (1987)
`
`Angle modulated radio equipment for use at base and mobile slatlnns
`in Lhe private mobile radio service operating in the t'reqtienugi band
`174—225 MHz.
`
`MPT 1327 (1988)
`
`A signalling standard for trunked private land mobile radio systems.
`
`MP1." 1331 (1937)
`
`Code of practice for radio site engineering.
`
`MPT 1347 (1938)
`
`specification for commercial
`Radio interface
`operating in Band Ill sub—bands l and 2.
`
`trunked networks
`
`MPT 1352 (1991)
`
`the approval of radio units to be used with
`Test schedule for
`commercial trunked networks operating in Band III sub-bands l and 2.
`
`
`
`
`
`1
`
`To
`
`ARRIS GROUP, INc.
`IPR201 5-00635 , p. 9
`
`

`

`
`
`3.
`
`3.1
`
`GENERAL
`
`Definitions
`
`Section numbers. appearing between H
`numbers within IVIPT 1327.
`
`ll delimiters in this sputlication refer to section
`
`Words appearing between asterisks in this section are defined terms.
`
`Acquisition: The condition obtained by the successful completion of the *control channel
`acquisition procedure* for a control channel which allows a radio unit to transmit on that
`channel.
`
`Aguisition Authorisation Data: *Network personalisation“ data which enables the *radio
`unit“ to determine by examination of the relevant sub—fields within a *system identity code*
`received on a *control channel* whether the *radio unit* is authorised to access on that
`*control channel“.
`
`it is
`Active on a Channel: A *radio unit“ is *active on a channel“ when, on that channel,
`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“.
`
`Address: 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“.
`
`Address Cgmeword: A 64-bit codeword, conforming to the requirements of MP1“ 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 for Customisation:
`customised function, then if the ”radio unitm implements the function it shall respond in the
`manner specified by the network operator of that *trunl-ring 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 M'PT 1327.
`
`Base Station: The entirety of transmitters and receivers operated by a *trunlo'ng system
`controller“ at any one site.
`
`Call: A complete information exchange between two or more *parties" which includes one
`or more *transactions“ and may include direct user-to—user communication on a *traffic
`channel“.
`
`3-1
`
`fir? -.
`
`ARRIS GROUP, mc.
`IPR2015-00635 , p. 10
`
`
`

`

`
`
`Called. Unit (or Group}: 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 “call“
`irrespective of the origin of such “messages“.
`
`Calling Unit: A “radio unit“ or “line unit“ which requests a “call“. The “calling unit“
`retains this designation for the duration of a “call" and this conventi0n is used in “messages“
`relating to that particular “call“ irrespective of the origins of such “messages“.
`
`Common Prefix Call: A “call“ where the values of the “prefixes“ in the calling and called
`“addresses“ are the same.
`“Common prefix calls“ use “short addressing“ procedures.
`
`Confirmation: 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 channel“.
`
`3.?
`
`
`
`I
`-
`
`IMP“
`
`Control Category: 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.
`
`l“d
`h
`lbgdfh
`1Ch1A“f
`dh
`C
`ontro
`an “returnc anne “ ein use ort etransmission
`orwar c anne
`I anne:
`of “messages“ conforming to MP1" 1327 with the primary purpose of enabling the *U‘Ul’lklng
`system controller“ to control “radio units“.
`
`Control Channel Acquisition Procedure: 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 “continuation“ tests to determine if “acquisition“ is permitted.
`“Hunting“
`continues until such time as a successful “acquisition“ is confirmed.
`
`Data Codeword: A 64—bit codeword, conforming to the requirements of MPT 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“.
`
`Decodable: 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.
`
`-
`
`Diversion: 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
`
`ARRIS GROUP, INC.
`
`IPR2015-00635 , p. 11
`
`
`

`

`
`
`These called-party details may be an *address“ or addressing
`*address codeword‘.
`information in a different form (eg PSTN dialling digits].
`
`Fall—back Mode: A customised form of operation which may be used by a *network“
`suffering equipment malfunction.
`
`Field: A number of contiguous bits in a codeword which is specified in terms of the position
`within the codeword and the number of bits.
`
`Fixed Radio ilnit: A *radio unit" used with its antenna at a fixed location.
`
`Forward Channel: A radio bearer where the direction of transmission is from the "trunking
`system controller" to the *radio units".
`
`Free Format Data: Data within a codeword which. in this specification, is constrained only
`by its position and length.
`
`ident“ which is used to identify a “"message‘lr 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*.
`
`Group Address: An *address* which is common to more than one unit and which, when
`nominated as the called *address“. signifies a *group call“. Units may be assigned any
`practicable number of *group addresses".
`
`Group Call: 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 callng
`*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.
`
`--
`.
`-.'.-'-..-ch..;..
`
`
`Head Messaue: Single transmission of an MWUE? 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 ”commits“ one of the *forward channels“,
`which together with its paired *retum channel“ is an apprOpriate *control charmel“.
`
`HuntingI Se_quence: A procedure employed by the *radio unit“ during “hunting“ which
`consists of one or more *hunting stages“. There are five described *hunting sequences“:
`
`"Resuming a control channel sequence"
`(a)
`"Single channel hunt sequence"
`(b)
`(c) "Preferential hunt sequence"
`(d)
`"Normal hunt sequence"
`(e)
`"Comprehensive hunt sequence"
`
`|
`
`r);
`
`1;)
`
`ARRIS GROUP, INC.
`IPR2015-00635 , p. 12
`i
`
`
`

`

`
`
`A *hunting sequenee* is’oompleted when all *hunting stages“ appropriate to that *hunt'mg
`sequence* have been completed or, prior to this,
`if a successful *oonb'ol 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 chan.nels* located or may be completed prior to this if a successful *control
`channel'“ *confirmation* is achieved.
`
`'
`
`Ident: A 13-bit number used for identification purposes. Values of *ident’“ between I 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 *special idents* and these are not associated with any particular *prefix*, nor is
`the *ident* value 0 (DUMMYI).
`
`is *active on a
`Idle State: A *radio unit* is in the *idle state“ on a *system* when it
`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*.
`
`m
`|
`
`|
`|
`
`Include: A procedure whereby *parties’“ may be introduced into a *call* in progress at the
`request of an existing *party* to the *call*.
`
`.
`
`is knOWn within a *system*,
`Individual Address:- An *address* by which a single unit
`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.
`
`saga-gal
`
`Individual Call: A *call* between a calling *party* and a single called *party*.
`
`Integprefix Call: A *call“ where the values of the *prefixes* in the calling and called
`*addresses* are different. *Interprefix cal.ls* 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 *trunldng system controller“ via a medium other than that part of the radio
`spectrum to which this specification applies.
`
`Mandatory: The *radio unit* shall implement the function or facility.
`
`Message: A single
`
`contiguous data
`
`transmission which
`
`consists of
`
`a
`
`codeword
`
`3-4
`
`ARRIS GROUP, INC.
`
`IPR2015-00635 , p. 13
`
`
`

`

`
`
`synchronisation sequence. an *address codeword“ and (optionally) one or more *data
`codewords“ conforming to MP? 1327'.
`
`Network: Interconnected *5ystems'.
`
`Network Personalisation: 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.
`
`Non—dedicated: 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
`*n'affic channels“ depending on the traffic load on the *system“. When this procedure is
`employed, the current *conu-ol channel“ would normally be allocated as a *traffic channel“
`when all other channels are in use for traffic and the *control channel“ facility restored when
`possible, eg by allocating the next *uaffic channel“ to become free as a new *control
`channel“.
`
`Non-prescribed data: Any data traffic which dot-s not conform to the data protocols defined
`in MPT 1327.
`
`Normal Opegtion Mode: The operation mode of a *radio unit“ or *control channel* which
`is not in the *fall-back mode“.
`
`“ Normal Registration Mode: A *control channel* mode in which the *netw-ork‘“ will accept
`and maintain *regisrration* requests.
`
`Normal Registration Record: A *regisb’ation’“ record which has an indication that
`*network“ is maintaining the *registration“ record.
`
`the
`
`”5“”?
`
`Null Registration Record: A *registration* record which includes a NULL indicator together
`with the AREA code.
`
`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.
`
`Personality: The totality of *network personalisation“ data entered into the *radio unit‘“.
`
`Portable radio unit: A portable radio unit is distinguished from any other radio unit by the
`following criteria:—
`
`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
`
`ARRIS GROUP, mc.
`IPR2015-00635 , p. 14
`
`
`

`

`
`
`Erefix: The '7 most significant bits of an “address“. Normally units within a fleet will be
`allocated the same I“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 Registration Record: The most recently created *registration“ record held by the I
`*radio unit*. Note that the *prime registration record“ does not include timing information.
`
`Radio Unit (RU): A mobile or other user station contacting a *system* by normal land
`mobile radio in accordance with the specification.
`
`Random Access Attempt: The method by which a *radio unit* transmits an unsolicited
`*message* to the *trunking 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 *‘transacti0n* to the receipt of an appropriate
`acknowledgement or the expiry of a timeout.
`
`Read—only 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 Memog: a storage facility within the *radio unit* the contents of which may be
`modified by the *radio unit*.
`
`Ready for Communication Control (RF CC): 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 he initiated by a demand from the *trunking
`system controller*, or at the initiative of the *radio unit*. depending on the circumstances
`of the registration.
`
`jouested Unit (or Group): A unit, or group of units, which takes part in a *‘transaction*
`initiated by the *trunking system controller“ or another *party“.
`
`Reguesting Unit: A *radio unit* or *line unit* which initiates a *transaction* with the
`*trunlcing system controlled“ or another *party‘“, via the *trunlcing system controller“.
`
`Reserved: 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
`MPT 1327.
`
`ARRIS GROUP, INC.
`
`IPR2015-00635 , p. 15
`
`3—6
`
`

`

`Return Channel: A radio bearer where the direction of transmission is from _*radio units“ to
`
`the *trunlting system controller’“.
`
`Segment: For a known *transaction“, the portion of the *T~rnessage* contained in 3 *HEAD
`message“.
`
`Selected 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 *selected network“. Where the *radio unit* does not
`allow the user to select from a choice of *networks" then only one *network“ shall be
`available to that *radio unit’“ for access and this *networl-t“ shall be. per se, the *selected
`network*.
`
`Session: 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 *acrive on a control channel“ of a different
`*syst.em*. A *session" ends either when the *radio unit“ is switched off or when it starts
`its next *session*.
`
`Short 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.
`
`Short Data: A procedure which allows a data *message“ to be exchanged between *panies“
`. or between *parties“ and the *trunking system centroller". This procedure does not support
`*messages* which include more than four *data codewords".
`
`Short-Form PSTN Destination: A called PSTN *party“ previously agreed between the system
`operator and the user of the *calling unit“ which can be specified by a *special ident“ rather
`than the full stream of dialling digits representing the directory number.
`
`Single Segment Transaction {SST}: Short data *transaction* requiring only one *segment*.
`
`Spare: Codewords and *fields“ which are designated *spare“ are available for free use by
`*systems* (ie *system* customisation) provided that the conditions of MPT 1327 are not
`infringed. The use of *spare* codewords and *fields“ may vary from *system“ to *system'“.
`
`ngial Ident: 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 l32’r‘. others may be
`nominated by system operators.
`“Special idents* are nor associated with a *prefix“ to form
`an *address*.
`
`IPR2015-00635 , p. 16
`
`Smech gjall: A *cail* as a result of the receipt ot‘a GTC ‘message'
`to '0‘. The audio is not muted.
`
`'leiil the ‘D' *tield’“ set
`
`Standard Data: The procedure by which information exchange takes place using the data
`protocol defined in section 17 of MPT 1327.
`
`ARRIS GROUP, INC.
`
`

`

`
`
`Standard uptign: Any optional feature for which the implementation has been standardised
`in MPT 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.
`
`System Identity Code: A 15-bit number which identifies a “system“. This code is radiated
`on each “forward control channel“ within the “system“ (in the SYS “field“).
`
`
`T-messaoe: totality of “free-format data“ which is intended to be conveyed in a “short data“
`“transaction“.
`
`Temp_o_rar_y Registration ngjg: 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.
`
`Temp_or_ary Registration Record: A “registration“ record which has an indication that the
`“network“ may not be maintaining the “registration“ record.
`
`Timed Registration Record: A “registration“ record held by the “radio unit“, that has been
`displaced from the “prime registration record“. The record has a timer TD associated with
`it.
`
`Traffic Channel: A “forward channel“ and “return channel“ being used primarily for user
`communications.
`
`Transaction: 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“.
`
`Trunking System Controller (TSC): The central control intelligence necessary to enable the
`trunking system to function according to MPT 1327. The “trunking system controller“ may
`control one or more “base stations“.
`
`Undefined Registration Record: A “registration“ record which has no indication that the
`“network“ may or may not be maintaining the “registration“ record.
`
`Verififi AREA code: The AREA subfield of the received “system identity code“ (SYS) used
`to verify a “control channel“.
`
`Verified 51]., code: The SEL 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“.
`
`ARRIS GROUP, INC.
`
`IPR2015-00635 , p. 17
`
`3-8
`
`

`

`
`
`3.2
`
`Test Conditions
`
`Unless otherwise specified, the ‘radio unit’ shall meet the requirements at :hts incantation
`under extrEme test conditions. as defined in MPT 1.12.1 senior: 2-.-l
`
`3.3
`
`General Reguirements
`
`The "radio unit“ shall not operate duplex.
`
`The Facility to switch from one *network“ to another is a ‘standard option‘.
`
`'network“ switching shall be under control of the
`it is *mandatory“ that
`If implemented,
`user. Autonomous switching between *networks* by the *radio unit' shall not be permitted.
`
`g; -A‘
`
`It shall be possible to transfer, between *network(s)* in a *radio un.it* by changing the
`*personality* (see section 6).
`
`
`
`IPR2015-00635 , p. 18
`
`ARRIS GROUP, INC.
`
`

`

`5. l .3
`
`Frequency Tolerance
`
`The centre frequency of the response of the radio receiver shall be Within l5 kHz of the
`nominal receive frequency except during channel switching.
`
`This tolerance includes crystal ageing and shall be maintained under both normal and extreme
`temperature conditions, as defined in MPT 1323 sections 2 and 3, fora period of at least one
`year, without re—adjustment.
`
`5.2
`
`Demodulation Qharacteristics
`
`5.2.1
`
`SM“.ch Sianals
`
`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 -_l-3 dB. ie the total audio output power
`shall fit totally within the mask of figure 5. l. The radio unit shall be deemed to have passed
`this requirement if it meets the permitted departure either at the electrical connections to the
`loud speaker (with a suitable resistive load if the loudspeaker is disconnected), or acoustically.
`
`
`
`l/
`i
`y
`g
`iii/iii//////////////ii
`l.___—_
`
`1
`
`
`
`T
`6 dB
`
`L
`
`Amplitude relative
`to optimum phase
`demodulator response
`
`Eh;
`
`I!ffff//lf/lll£//////fff
`/
`.I’I
`l/
`/
`
`300
`2550
`
`1000
`
`100
`
`10000
`
`Input Frequency Hz
`
`Figure 5.1
`
`5.2.2
`
`Data Sinrials
`
`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
`11100 baud FFSK. with lSOO Hz representing binary ‘0' and IEllfl Hz representing hinary ’1’.
`Units shall meet the error performance requirements of Appendix A of this specification.
`
`Nore: The received peak deviation of standard data does not exceed 12.0 kHz. and is not
`less than ill) kHz. For non—prescribed data, the peak frequency deviation does not
`exceed i2.5 kHz.
`
`5-2
`
`
`
`ARRIS GROUP, INC.
`IPR2015-00635 , p. 19
`
`

`

`RECEIVER PARANIETERS
`
`The requirements of this section shall be met under normal
`MPT 1323 section 2.3, unless otherwise specified.
`
`test conditions, as defined in
`
`5. 1
`
`F rguency 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 SpacingI and Designations 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
`
`Radio Unit
`Receive Frequency
`
`176.5000 MHz.
`
`1000000001
`
`177.2125 MHz
`
`.
`
`1
`
`58
`
`560
`
`1111110111
`
`183.4875 MHz
`
` 5.
`
`The radio equipment shall receive over channels 58 to 560 (177.2125 MHz to 183.4875
`MHz) 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 f0110ws:
`
`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
`MHz) inclusively.
`
`ARRIS GROUP, INC.
`
`IPR2015-00635 , p. 20
`
`5—1
`
`

`

`
`
`
`4.2.3.2
`
`Data Peak DeviatiQn
`
`For standard data modulation.
`
`Angle modulation:
`
`Nominal
`Extreme
`
`1.5 kHz i250 Hz
`1.5 kHz i500 Hz
`
`4.3
`
`Performance Parameters
`
`Radio units shall meet the requirements of MPT 1323.
`
`ARRIS GROUP, mc.
`
`IPR201 5-00635 , p. 21
`
`4-3
`
`

`

`4.1 .3
`
`Frguency Tolerance
`
`The carrier frequency of a signal transmitted by a radio unit shall be within 1.5 [(1—12 of the
`nominal transmit frequency.
`
`This tolerance includes crystal ageing and shall be maintained under both normal and extreme
`temperature conditions. as defined in MPT 1323 sections 2 and 3,

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