the Office of Communications
`1, Julia Fraser, am Head of Knowledge Management at
`(“Ofcom”), an independent regulator for the communications sector in the United Kingdom
`located in London.
`I was previously responsible for maintaining publications at
`the
`Radiocommunications Agency starting in the Spring of 1990.
`The Radiocommunications
`Agency, a public agency of the United Kingdom, was formerly an Executive Agency of the
`Department of Trade and Industry and merged with several other regulatory bodies in the United
`Kingdom to form Ofcom in 2003.
`
`I am the custodian for the attached document:
`
`MPT 1327: A Signalling Standardfor Trunked Private Land Mobile Radio Systems
`
`I certify that the attached is a true and correct copy from the records of Ofcom and has been in
`Ofcom’s possession (and previously that of the RA) since its original release in 1991.
`
`§5lA0\Q-sage
`
`Julia Fraser
`
`Head of Knowledge Management
`Office of Communications
`
`25? Ave? 2m§
`
`EXHIBIT
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p.
`
`1 of 295
`
`

`
`MPT 1327
`
`A Signalling Standard
`
`for Trunked Private Land Mobile
`
`Radio Systems
`
`January 1988
`
`Revrsed and reprinted November 1991
`
`-*PaI‘t‘1-
`
`(cid:36)(cid:53)(cid:53)(cid:44)(cid:54)(cid:3)(cid:42)(cid:53)(cid:50)(cid:56)(cid:51)(cid:15)(cid:3)(cid:44)(cid:49)(cid:38)(cid:17)(cid:15)(cid:3)(cid:44)(cid:51)(cid:53)(cid:21)(cid:19)(cid:20)(cid:24)(cid:16)(cid:19)(cid:19)(cid:25)(cid:22)(cid:24)(cid:15)(cid:3)(cid:40)(cid:91)(cid:17)(cid:3)(cid:20)(cid:19)(cid:22)(cid:24)(cid:15)(cid:3)(cid:83)(cid:17)(cid:3)(cid:3)(cid:21)(cid:3)(cid:82)(cid:73)(cid:3)(cid:21)(cid:28)(cid:24)
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 2 of 295
`
`

`
`MPT 1327
`
`mg; mg? 1.988
`
`A SIGNALLING STANDARD FOR
`
`TRUNKED P-LRIV-ATE LAND MQBILE RADIO SYSTEMS
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 3 of 295
`
`

`
`Crown Copyright 1988-
`First; published January 1988
`Reprinted and revised October 1990
`Reprinted and revised November 1991
`
`Amendments issued since publication
`
`Amendment
`Number
`
`Date of issue
`
`Text affected
`
`October: 1990
`
`Incorporated in the -version
`reprinted in October 1990.
`Amended text was highlighted
`by a bar in the margin.
`
`ARRIS GROUP, INC., lPR2015-00635, Ex. 1035, p. 4 of 295
`
`3 9 0 0 0 0 0 c 0 0 0 0 o o 0 0 0 0 0 0 0 0 0
`
`

`
`FOREWORD
`
`This standard defi'nes- the rules for comniunication between radio units-and trunking
`system controllers operating in trunked private land mobile radio systems.
`
`Applications and test conditions for this standard,.app1icabie to Band III, are contained in
`the following specifications" prepared by the Department of Trade and Industry,
`Radioqommunications Agency-..
`
`MPT 1343
`
`System interface spezzification for radio equipment to be used with
`commerdial trunked networks operating in Band III, sub-bands 1
`‘and 2.
`
`Radio interface“ specification for commercial trunked networks-
`operating in Band III, su'_b~bands 1 and 2.
`
`Test schedule for the approval of radio units to be used with
`commercial -trunked networks operating in Band III, sub—bands 1 and
`2.
`
`Intgllecgggl P'rgp_@'1*ty Rightg
`
`Firms intending to manufacture equipment which complies with the standard should be
`aware that certain features of the standard are subject to [PR claims.
`
`All firms are therefore -advised that they should make appropriate enquiries through
`their Patent Agents before proceeding.
`
`ARRIS GROUP, INC., IPRZO15-00635,'Ex. 1035, p. 5 of 295
`
`

`
`INTRODUCTION
`
`DEFINITIONS
`
`SIGNALLING FORMATS
`
`ADDRESSING
`
`conrwoap s-mucruars
`
`CHANNEL DISCIPLINE
`
`RANDOM Acc'Ess PROTOCOL
`
`REGISTRATIOH PROCEDURES
`
`BASIC CALL PROCEDURES
`
`EMERGENC¥'CALL PROCEDURES
`
`INCLUDE CALL PROCEDURES
`
`CALL DIVERSION PROCEDURES
`
`STATUS MESSAGE PROCEDURES
`
`SHORT DATA MESSAGE PROCEDURES
`
`DATA INTERROGATION PROCEDURES
`
`section reserved for additional short data procedures
`e.g. SAKS.
`
`STANDARD DATA PROCEDURES
`
`APPENDIX
`
`3..
`
`APPENDIX
`
`2.
`
`APPENDIX
`
`3.
`
`APPENDIX
`
`APPENDIX
`
`APPENDIX
`
`APPENDIX
`
`Suggested values for parameters.
`
`The error control properties of the codewords.
`
`An algorithm for determining the codeword completion
`sequence of a control channel system codeword.
`
`An algorithm for generating fields A and B of
`the MARK codeword.
`
`BCD coding .
`
`Reserved for Timing of responses for standard data at a
`customised rate.
`
`other ideas considered during the drafting of section 17
`(standard data).
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 6 of 295
`
`

`
`Ml>'£l327 is a signalling standard for trunked private land mobile radio
`systems.
`It defines the protocol rules for connmmlcation between a
`trunking system controller (Tsc) and users‘ radio units.
`
`from
`The standard can be used to implement a wide variety of systems,
`small systems with only a few radio channels (even single-channel systems),
`through to large networks which may be formed by the interconnection of
`Tsce.
`
`The protocol offers a broad range of user: facilities and system
`options. However, it is not necessary to implement all of the facilities
`available; an appropriate subset of the protocol could be implemented,
`according to the user requirements. Also,
`there is scope for customisation
`for special requirements, and Qrovieion has been made for further
`standardised facilities to be added to the protocol in the future.
`
`The standard defines only the over-aiz: signalling and imposes only
`minimum constraints on eyetem design. Additional specifications will be
`required for specific implementations, for example, to define:
`
`the facilities that must be implemented
`--
`— garemeter values
`--
`a channel plan
`-
`for a network, criteria for when a radio unit: should register.
`
`Section 1.1 of this introduction describes the user facilities which
`
`{It does not describe additional
`are explicitly provided by the protocol.
`facilities which may be offered in a radio unit but which do not require
`any specific protocol.)
`
`Section 1.2 describes some protocol features,
`available to system designers.
`
`indicating the options
`
`Section 1.3 provides an introduction to the operation of the protocol.
`
`subsequent sections of this document contain the protocol definition.
`In most of these sections,
`the protocol rules for the T50 and for radio
`units are specified separately, but with crosewreferencing where
`convenient.
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 7 of 295
`
`0 o 0 0 0 0 0 0 0 0 0 0 0 0 0 9 Q 0 o o o 0 o
`
`

`
`1.1
`
`User Facilities
`
`The facilities available to users are outlined below. For a full
`definition of the facilities, see the sections indicated.
`
`1-1.1 Tyggs.of call
`
`The standard protocol enables radio units to make the following types
`of call.
`
`a.
`
`Speech call.
`
`(See section 9.}
`
`For group
`speech calls may be requested with normal or high priority.
`calls,
`the calling party may opt for a conversational mode, where all
`parties are able to speak, or for an announcement mode where only the
`caller may speak.
`
`Data call, for the transmission of non—prescribed signalling.
`(see section 9.)
`
`Parameters are available to specify either normal or high priority
`and, for a group call, whether the called group members can reply.
`(Provision has been made for specifying a standard method of data
`communication in the future).
`
`Emergency call.
`
`(See section 10.)
`
`Parameters are available to specify either a speech or a data call
`and, for a group cell, whether the called group members can reply.
`Also, a radio unit may request a special mode of emergency service
`previously arranged with the system;
`the TSC determines the required
`action by reference to the calling unit‘s address.
`
`Include call.
`
`(See section 1;.)
`
`During a call, a unit may request that another party joins the call.
`This facility may be used to implement a Conference Call or Call
`Transfer.
`
`status message.
`
`(see section 13.)
`
`Thirty-two different status messages may be conveyed between units.
`The meanings of two of these messages are prescribed as a "call-me~
`back request" and "cancel previous ca11—me—back request". The
`remaining thirty messages have user~defined meanings.
`{Status
`messages can also be sent between radio units and the TSC.}
`
`Short Data Message.
`
`(See section 14.)
`
`Messages of up to 184 bits of free format data can be sent between
`units, or between units and the TSC.
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 8 of 295
`
`coooooooooooooooooooooo.
`
`

`
`1.1.2 flaking calls
`
`A radio unit may request a cal}. to any of the following called parties
`{except for status messages, which cannot be addressed to PABX or Psm
`destinations or to groups):
`
`-—
`-
`--
`-
`
`an individual radio unit or line-connected unit
`a group, or all units in the system
`a PABX number, up to nine digits
`a PSTN number, up to 31 digits.
`
`In addition, status messages and short data messages may be sent to the
`TSC.
`
`the mac may pass a wide variety of information to
`During call set-up,
`the caller, to indicate the progress of the call. For example, it may
`indicate the reason for any delays in call set-up or the reason for a call
`failure.
`
`A call request may be cancelled at any time.
`
`1. 1 .3 geceiving calls
`
`A radio unit may receive calls from a radio unit or line unit, or
`(except for status messages) from a PABX extension or the PSTN.
`In
`addition, status messages and short data messages may be received from the
`’1‘5C.
`For a call from a radio unit, a line unit or the Tsc,
`the calling
`address may be supplied to the called unit. For a call from a PABX
`exteneion or from the PSTN,
`the calling gateway is indicated as the source
`of the call but the caller’s number is not conveyed to the called unit.
`
`Incoming calls may be addressed to the unit individually or to a group
`to which it belongs.
`A radio unit may he a member of an arbitrary number
`of groups ; its group addresses can be chosen independently of its
`individual address.
`
`A radio unit may refuse to accept all incoming calls, for example by
`means of a "busy" or "out-of—vehicle" control, or incoming calls could be
`refused selectively, depending on the source of the call.
`If a user does
`not wish to plroceed with an incoming call immediately, be can indicate that
`he will call back later.
`
`Systems may be configured to alert .3 called individual and require him
`to indicate that he is ready, before a traffic channel is allocated for a
`call.
`
`1 . 1. 4 Diverting Calls
`
`If a radio unit does not wish to receive calla, it may request that
`future calls addressed to it be redirected to a specified alternative
`destination.
`A radio unit may also request redirection on behalf of a
`third party,
`for example, for a unit which is not equipped for call
`diversion. A radio unit calling a diverted party will be informed of the
`alternative destination to try; it may then re-make the call automatically,
`or it may give the user the option of deciding whether to call the
`alternative destination.
`see section 12 for the full diversion facilities.
`
`ARRIS GROUP, INC., IPR2015-00635, Ex. 1035, p. 9 of 295
`
`Page 1-3
`
`0 0 0 O 0 0 0 0 0 0 0 0 o 0 0 0 o
`
`co
`,0
`90
`
`0 0 0
`
`

`
`1.2
`
`System Features and Facilities
`
`1.2.1 System dimensions
`
`The numbering range of the protocol accommodates:
`
`*
`-
`-
`
`1,036,800 addresses per system
`1024 channel numbers
`32768 system identity codes.
`
`1.2.2 system control
`
`The protocol uses signalling at 1200 bit/s with Fast Frequency shift
`Keying (FFSK) subcarrier modulation.
`It is designed for use by two-
`frequency half-duplex radio units and a duplex TSC.
`
`The signalling for setting up calls is transmitted on a "control"
`channel.
`A TSC can be operated-using either of two control channel
`strategies: dedicated or non—dedicated.
`A dedicated system has a control
`channel permanently available for signalling, whereas a non—dedicatsd
`system may assign the control channel for traffic {speech or data
`communication) if all the other channels are in use.
`The use of a
`dedicated control channel is appropriate for a TSC with many channels,
`whereas a non-dedicated control channel may be more appropriate for a TSC
`with only a few channels.
`The protocol allows the use of either strategy.
`
`Broadcast messages are available to inform radio units of system
`information, such as the channels which the system may use for control
`signalling.
`
`one of the problems of mobile radio signalling systems is the clashing
`of messages from different radio units transmitting at the same time.
`The
`problems of clashing are controlled by an access protocol which offers high
`efficiency, stability and flexibility.
`(see section 1.3.3 and section 7.)
`
`Protection against interference is provided by labelling the
`signalling with a system identity code and,
`in some messages,
`the channel
`number.
`If heavy interference is encountered, control can be changed to a
`different channel.
`
`To cope with system malfunction, a customised fall-back mode of
`operation may be defined.by the system designer.
`
`1.2.3 Call handling
`
`The protocol is designed for use by systems which queue calls that
`cannot be set up immediately, for example, if no channel is currently
`available for traffic.
`
`Before a traffic channel is assigned for a call to an individual radio
`the TSC checks that the called unit is in radio contact,
`in order to
`unit,
`avoid wasted channel assignments.
`It may also check that the radio unit's
`operator is ready for the call,
`to avoid a traffic channel being assigned
`to an unmanned unit.
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 10 of 295
`
`Page l—4
`
`CCUOOOUOOOOOIOOOOOUOOII1
`
`

`
`call maintenance signalling in defined for prompt: release of ttaific
`channels at the and of a conversation, or" in _caa_.e communication is lost
`during a call.
`(see section 1.3.5 and section 9.)
`
`as a precaution against fraudulent use of a system by an unauthorised
`rad-io unit,
`the Tsc may at any time instruct a radio unit to transmit its
`unique serial number; comparison of the xzeceived serial number with the
`expected value will assist in the detection of fraudulent nears.
`(see
`section 15.)
`
`1.2.4 Kulti-site systems
`
`The standard leaves scope for various multi-site wide-area coverage
`techniques to be used, for example:
`
`-
`—
`—
`
`synchronous[quash-synchronous operation
`a separate control channel at each site
`a single control channel shared by time division.
`
`The protocol includes a registration facility to assist the
`implementation of multi:-mite systems and networks of Tscaz a radio unit can
`inform the TSC of its location as it roams between sites or systems.
`{The
`system identity code distinguishes the signalling from different sites and
`systems) .
`The standard defines signalling procedures for registration
`(section 8), but the criteria for registration will be sy3tem—dependent.
`
`A TSC can broadcast information to assist radio units hunting for a
`control channel when they roam; for example, it can announce the channels
`which may be used for control by itself 02: by ‘£503 on adjacent sites.
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035; p. 11 of 295
`
`5 0 0 0 0 0 0 o 0 0 0 0 0 o 0 0 0 0 0 0 o o 0
`
`

`
`1.3
`
`Guide to some Egg Protocol aspgggs
`
`This section provides an introduction to the operation of the protocol
`which, because of its scope and_f1exibi1ity, is necessarily complex. The
`section outlines the control channel structure, the random access_pretocol
`and some message exchange procedures for call set-up.
`
`This section is intended only as a guide: it should not be regarded as
`a protocol-specification. Readers should refer to the main body of the
`standard for the complete and precise definition.
`
`1.3.1
`
`Control channel signalling structure
`
`The signalling for setting up calls is transmitted on a "control"
`channel. Time on the control channel is divided into slots of duration
`106.7 ms
`(128 bits), and one signalling message-can be sent in each slot.
`The basic control channel-signalling structure is illustrated in Figure
`lei.
`
`signalling on the forward channel (base station transmit frequency) is
`nominally continuous, with each slot comprising two 64-bit codewords,
`usually:
`
`i)
`
`A Control Channe1.System codeword (CCSC).
`The CCSC identifies the system to radio units and provides
`synchronisation for the following “address” codeword.
`
`An "address" codeword.
`afl
`'
`'
`Ar =Hdre9e cofleudrd is the fire? vndeworfi of an" meeeeoe
`
`0000000000001
`
`ARRIS GROUP, INC., IPR2015-00635, Ex. 1035, p. 12 of 295
`
`

`
`1.3.2
`
`control channel signalling messages
`
`The messages sent on a control channel may be classified as .follows:-
`
`Aloha messages
`
`Requests
`
`"Ahoy" messages
`
`sent by the mass to invite and control
`random access.
`
`Sent by radio units -to request
`calls/transactions,
`Sent by the T80 to demand a response from an
`addressed radio unit.
`
`-Acknowledgements
`Go To channel.messages
`single address messages
`Short data messages
`Miscellaneous messages
`
`sent by the 1'80 and by radio units.
`Sent by the rsc to allocate traffic channels.
`currently sent only by radio units.
`sent by the TSC -and. by radio units.
`Sent by the TSC for system control.
`
`some uses of these messages are illustrated in the following sections.
`
`1 . 3 . 3
`
`Random access grotocol
`
`1.3.3.1 Pm’.-ncigle of operation
`
`one of the problems of mobile radio signalling schemes is the clash of
`messages from different radio units transmitting at the same time.
`In this
`standard, the problems" of clashing are controlled. by a random access
`protocol which is based on slotted Aloha, with a superimposed framing
`structure.
`The access protocol can be used to minimise access delays,
`ensure stability and maintain peak throughput under heavy traffic loads.
`
`The basic principle of the access. protocol is described with reference
`to Figure 1-2, which illustrates signalling on a control channel.
`The TSC
`transmits a synchronisation message (indicated by ALE in Figure 1-2)
`to
`invite radio units to send random access messages.
`The ALE message
`contains a parameter (N) which indicates the number of following timeslots,
`constituting a frame, that are available for access.
`If a frame is already
`in progress when a user initiates a call, the radio unit may send its
`random access message in the next slot.
`otherwise the unit waits for a
`frame to be started and then chooses a random slot from the frame for its
`
`message. A unit wishing to send a repeat transmission after an unsuccessful
`message (corrupted by fading or clashing) chooses again from a new frame.
`
`1 slot
`<———>
`
`ALH
`(4)
`
`ALH
`(3)
`
`TSC to
`radio units
`
`Radio units
`to TSC
`
`Two random access frames
`
`each marked 1)
`
`an ALI-I messa e
`
`Page 1-7
`
`ARRIS GROUP, INC., IPR2015-00635, Ex. 1035, p. 13 of 295
`
`0 0 O 0 0 0 0 0 0 . 0
`
`0 0 . 0 o 0 0 0 o 0 0
`
`

`
`1.3.3.2 Features of-the random access protocol
`
`The.main features of the access protocol are as follows:
`
`The TSC can monitor activity on the control channel and can optimise
`the system performance by varying the framelength to.prevent excessive
`clashing and to minimise access delays. Figure 1-3 illustrates an
`example of random access control.
`
`The signalling overhead for random access control is kept small by
`allowing Acknowledgements and Go To Channel messages to contain the
`framelength parameter (N), so that frames can be marked without
`requiring an explicit Aloha message.
`For example, see Figure 1-3.
`
`During a frame, the T50 may transmit messages that demand a
`response from a specified radio unit. These outbound messages
`inhibit random access in the following slot, and so reserve the
`slot for the unit's reply.
`
`The TSC may reserve frames for:
`
`-
`
`specific types of call request, by means of specific Aloha messages
`(for instance,
`the Aloha message ALHE invites emergency calls
`only):
`
`—
`
`subsets of the radio unit population (subdivision by address).
`
`TSC to
`radio units
`
`Radio units
`to TSC
`
`ALH
`(1)
`
`ALB
`(2)
`
`ALB Acxo Acxo
`(0)
`(1)
`(1)
`
`RQSl RQS2
`
`\___f \___l \
`frame frame
`
`frame
`
`\___/
`I \___l
`frame frame
`
`The TSC detects the clashing of requests RQS1 and RQS2, and
`marks a longer frame (with message ALH(2)). The radio units
`repeat their requests and.
`in this example, choose different
`slots. Each request is acknowledged in the following slot.
`
`RLH(O) does not mark a frame.
`
`ACKQ(1) acknowledges a request and also marks a new frame.
`
`In the absence of clashing, the framelength may be reduced.
`
`Fig. 1-3
`
`Examgle of random access control
`
`ARRIS GROUP, INC., IPR2015-00635, Ex. 1035, p. 14 of 295
`
`

`
`1.3.4
`
`Addressing
`
`A unit address is a. 20-tilt "number compr~is_ing- two fields: a 7-bit
`prefix and 'a 13-bit ident.
`(Normally; all members of a fleet will be
`allocated,the same prefix.) The division into prefix -and idem: allows" most
`messages to accommodate two addresses, the calling and called party, by
`including the prefix only once. For instance, call requests and Go '20
`channel messages contain two idents ‘and only one prefix.
`
`For a call to a unit with the same prefix, a request message contains
`all the information necessary to make the call. However, for a. call to a
`unit with a different prefix, the call details cannot be accommodated in a
`single address codeword; this type of call requires the use of “extended
`addressing" procedures (as do some PABX and most PSTN calls).
`
`1.3.5
`
`Examples of signalling seggences
`
`The precise signalling required for a call depends on the type of call
`and on the design of the Tsc;
`(the standard does not prescribe the arse
`algorithms) . This section contains some examples of message exchange
`sequences. Note that, although not shown in the examples, messages will be
`retransmitted in the case of corruption by propagation errors or collision.
`
`Examples of message exchange sequences for call set-up are presented
`in sections 1.3.5.1 to 1.3.5.3. These examples show control channel
`signalling, for:
`
`.
`
`call requests
`instruction to send extended address information
`
`checking availability of radio units
`tra.f..fic channel allocation.
`
`‘
`
`signalling is also sent on an allocated traffic channel, for call
`maintenance and call clea.r—down.
`For instance:
`
`a)
`
`To assist call maintenance, a radio unit sends a "P2.-essel Off"
`message at the end of each speech transmission.
`The system may
`also require the unit to start each speech transmission with a
`"Pressel On” message and to send call maintenance messages
`periodically within the transmission.
`
`The calling unit in a group call, or both units in an individual
`call, send “Disconnect” messages to indicate end-of-channel-use
`when the user goes on-hook or equivalent.
`
`c)
`
`The TSC sends CLEAR messages to clear down a call (after receiving
`a valid Disconnect message or if a time—out has expired).
`
`However,
`
`the examples do not cover traffic charmel signalling.
`
`The final example (section 1.3.5.4) illustrates the transmission of a
`short: data message. This type of transaction does not use a traffic
`channel: it requires control channel signalling only.
`
`ARRIS GROUP, INC., lPR2015-00635, Ex. 1035, p. 15 of 295
`
`4 xE
`
`i» ;
`
`

`
`1.3.5.1
`
`Exam le: radio unit-calla a
`
`rou
`
`Figure 1-4 illustrates a message sequence on a control channel to set
`up a group cell between radio unite with the same prefix.
`
`The-sequence includes call reguést and channel allocation signalling.
`(For group calls. an availability check on the called units is-not
`performed.)
`In this example, all traffic channels are in use when.the call
`is requested and so the call is queued.
`
`TSC to RUS
`
`RU5 t0 TSC
`
`RQS
`
`\,__/ \__/
`frame frame
`
`\___/ \_/
`frame frame
`
`General Aloha invitation (one-slot frame).
`
`The calling-radio-unit transmits its request, complying
`with the random access protocol.
`
`informing the
`The TSC acknowledges the RQS message,
`calling unit that the call has been queued.
`
`the Tsc sends the
`when a traffic channel is available,
`Go To Channel command, addressed to the calling unit and
`called group; this message instructs the units to switch
`to the traffic channel for their conversation,
`In this
`example the GTC is repeated, for added reliability.
`
`Fig. 1-4
`
`Common-prefix group call
`
`-Alternative acknowledgements from the TSC are available if, for
`instance,
`the call request is invalid or the system is overloaded.
`
`If a traffic channel is available when a group call is requested then
`the TSC may omit the ACKQ and send the GTC command immediately.
`
`In this example the GTC message is repeated immediately. However,
`repeat messages may be delayed for other signalling.
`
`ARRIS GROUP,-lNC., lPR2015-00635, Ex. 1035, p. 16 of 295
`
`O000000000Or.OOOCUOiO“DCUCI1
`
`

`
`.
`
`5.2
`
`Ba:
`
`1e:
`
`ad can ‘t: calls a unit wit
`
`the same
`
`refix
`
`Figure 1-5 illustrates a message sequence on a control channel. to set
`up a call between two radio units with the same 15re£5.x'. The sequence
`includes call request, availability check and channel allocation
`signalling.
`
`TSC to RUB
`
`RUB to TSC
`
`frame
`
`frame
`
`I \___/
`frame
`
`General Aloha invitation {three-slot frame).
`
`Random access can request.
`
`Availability check message
`-
`acknowledges the R95 message
`--
`demands a response from the called radio unit
`(thereby checking whether the called unit
`is in radio contact)
`inhibits random access in the next slot.
`
`-
`
`Acknowledgement from the called radio unit,
`sent in the reserved slot.
`
`Go To Channel message instructing both radio units to
`switch to the specified traffic channel for their call.
`In this example the Give is repeated, for added reliability.
`
`I-‘lg-
`
`1»-5
`
`Common—Qref.Lx individual call
`
`the called unit is in radio contact and therefore
`In this example,
`If the called unit cannot be contacted, the use may
`responds to the AHY.
`lndicate the failure to the calling unit py sending acknowledgement ACKV.
`
`In both this and the following example, the arse checks only that the
`called unit is in radio contact before allocating a traffic channel. The
`TSC may also check whether the called user is ready; if he is not,
`the unit:
`responds with acknowledgement ACKI and takes action to alert him. Then,
`when the user is ready to receive the call, the unit may send a status
`message (RQQ) to inform the Tsc.
`
`in
`The ALHU3) message in these examples is used as a "dummy" message,
`slate carrying no signalling relevant to the example.
`In practice, these
`alota may be used for signalling for another call, or for broadcast
`messages (which contain information about system parameters).
`
`ARRIS GROUP, INC., lPR2015-00635, Ex. 1035, p. 17 of 295
`
`

`
`1.3.5.3
`
`Exam_le: radio unit calls a unit
`
`ith a different
`
`_
`
`,Figure l~6 illustrates a message sequence on a control channel to set
`up a call between two radio units with different prefixes.
`
`The sequence includes call request, availability check and channel
`allocation signalling {as in the previous example). However, this sequence
`has an extra phase: after receiving the RQS message,
`the TSC sends AHYC to
`invite the calling unit to transmit the full-called address. Also,
`separate GTC messages instruct the two units, because GIG-contains only one
`prefix.
`
`TSC to RUs
`
`RUB to TSC
`
`frame
`
`frame
`
`General Aloha invitation (four-slot frame).
`
`Random access request for an interprefix call.
`(The request contains the calling unit's address
`(prefix/ident), but the called ident is set to a
`special "gateway" ident to indicate that extended
`addressing procedures are needed.)
`
`Short data invitation message
`—
`acknowledges the RQS message
`—
`instructs the calling unit to send the called address
`inhibits random access in the next slot.
`
`-
`
`Single Address Message from.the calling radio unit,
`containing the address (prefix/ident) of the called unit.
`
`Availability check message demanding a response from
`the called radio unit.
`in this example,
`the availability check is a
`single—codeword message i.e. the address of the
`calling unit is not supplied.
`
`: Acknowledgement from the called radio unit.
`
`Go To Channel message instructing the called radio unit
`to switch to the specified traffic channel for the call.
`
`Go To Channel message instructing the calling radio unit
`to switch to the specified channel for the call.
`
`Fig. 1-6
`
`Intergrefix individual cell
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 18 of 295
`
`

`
`1.3.5.4
`
`Examjgle: radio unit sends a short data message
`
`Figure 1-'—‘-'! illustrates a message sequence on a central channel for
`sending a short data. message from one radio unit to .another radio unit. In
`this example,
`the data ‘message cornpriaes an address codeword and two
`appended data codewords;
`(each of the data codewords contains 46 bits of
`free format data) .
`
`the radio unit sends its request; the Tsc instructs
`In the sequence,
`the unit to send the data message, forwards the data message to the called
`unit and then indicates the success of the transaction to the calling unit.
`
`TSC to RUG
`
`RUB to TSC
`
`frame frame
`
`frame frame
`
`: General Aloha invitation (one-slot frame).
`
`: Random access request to transmit a short data message.
`(The request indicates the number of timeslote required
`for the data message:
`in this case,
`two slots.)
`
`:
`
`short data invitation message
`-
`acknowledges the RQC message
`—
`instructs the calling unit to send the data
`message in the next
`two slots.
`
`The calling radio unit sends its short data
`message to the TSC.
`In this example the
`message comprises an address codeword (_HEAD)
`and two appended data codeword-5.
`
`HEAD + data
`
`:
`
`The TSC forwards the short data message to
`the called radio unit.
`
`: Acknowledgement from the called unit - message accepted.
`
`: Acknowledgement sent to the calling unit to indicate
`that the called unit has accepted the data message.
`In this example the TSC immediately repeats the
`ACK message,
`for added reliability.
`
`Fig. 1-7
`
`Short data message
`
`ARRIS GROUP, INC., IPR2015-00635, Ex. 1035, p. 19 of 295
`
`

`
`DEFINITIONS-
`
`_Igg3:_§_ -— words‘ appearing within asterisks within these definitions are
`defined terms.
`(eg. fidefined term!)
`
`Active on a channel: A *z.-adio nnitt 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 these
`two states,
`
`Note — a. *radio un'it* becomes active on an assigned *tra‘ffic
`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 *s.ystem 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 codeword: A 64-bit codeword, conforming to the requirements of
`this standard, 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*.
`
`Base Station: The entirety of transmitters and receivers operated by a
`*trunking 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 channelh
`
`Called Unit {or Group]: The unit, or group of units, which a *calli.ng
`unit* identifies as the desired recipienus) of a *call*.
`The
`*cslled unit
`(or group}* retains this designation for the
`duration of a *call* and this convention is used in *messages*
`relating to that particular *call*,
`irrespective of the origin
`of such *meesages*.
`
`Calling Unit: A *radio unit* or *line unit‘! which request a *call*.
`The acalling 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
`*meseages*.
`
`Common Prefix Call: A *call* where the values of the *prefixes* in the
`calling and called *addresses* are the same.
`*common prefix
`calls* use the *shoz:t addressing* procedures.
`
`control channel: A *forward channel} and *return channel* being used
`for the transmission of *messages* conforming to this standard
`with the primary purpose of enabling the *trunking system
`control.le2:* to control radio units.
`
`Data codeword: A 64-bit codeword, conforming to the requirements of
`this standard, where the first bit is set to '0‘.
`*Data
`codewords* are concatenated to an *address codeword* and
`
`supplement the information in the *address* codewordh
`
`ARRIS GROUP, INC., |PR2015-00635, Ex. 1035, p. 20 of 295
`
`Page 2-1
`
`

`
`'Qgtaitgm: The whole, or a part of, a *Tmessage#. A dataitem may not
`include-more than 62 data codewqrds.
`
`.Decodeah1e: A.transmitted codeword shall be considered *decodeable*
`“if, after receipt, and after any error correction (if used) has
`been applied,-a valid codeword from the code defined in
`section 3.2;3 of this standard is formed.
`
`request that future
`Diversion: A procedure whereby a *party* may
`*calls* to a particular called address be redirected to an
`alternative destination.
`
`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 *address codeword*.
`These ca1led—party details may be an *address* or addr