DIV
`
`FLAG1
`
`FLAG2
`
`for a request for call diversion.
`'0'
`'1' for a request for cancellation of call diversion.
`
`For IDENT1 = PSTNGI,
`up to 9 dialling digits
`'0' - number has
`'1' - number has 10 to 31 dialling digits.
`For IDENT1 / PSTNGI, FLAGI is reserved; default value='O'.
`
`Specifies whether or not three addresses must be supplied:
`For DIV='O',
`'0'
`for self-initiated diversion
`'1'
`for third—party diversion.
`For DIV='1', FLAG2 shall be set to '0‘.
`
`Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 61
`
`Page 5-27
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 61
`
`

`
`5.5.3.l.5 Reggest Emergency Call Message, RQE
`
`This message is transmitted to the TSC by a radio unit requesting an
`emergency call.
`The RQE codeword contains all the information necessary to
`request a call to a unit or group of units with the same prefix,
`to all
`units in the system,
`to a prearranged PSTN destination or to a PABX
`extension that can be accommodated in the range 0-8191.
`In addition, RQE
`may be used to request entry into the extended addressing mode for an
`interprefix call, a general call to the PSTN or a call to a PABX extension
`with a "long" number.
`See section 10 for the emergency call procedures.
`
`RQE may also be used to request a special mode of service previously
`arranged with the system.
`
`Usually emergency calls will take precedence over all other calls.
`Emergency calls may be pre-emptive,
`that is, another call may be terminated
`prematurely to free a channel for an emergency call.
`
` IDENT1
`CAT
`TYPE
`FUNC
`FLAGI FLAG2
`
`1
`
`7
`
`13
`
`l
`
`3
`
`2
`
`3
`
`13
`
`1
`
`1
`
`l
`
`l
`
`1
`
`16
`
`PFIX - Prefix of the requesting radio unit.
`
`IDENT1
`
`— _Called party or gateway:
`Ident
`— for a common-prefix call
`IPFIXI
`— for an interprefix call
`ALLI
`- for a system-wide call
`number
`- for a short addressing call to a PABK extension
`(EXT='1')
`- for a call to a "long" PABX extension number
`PABXI
`PSTNSIj — for a call to a prearranged PSTN destination
`PSTNGI
`- for a call to a general PSTN destination.
`
`Note: If ExT='0'/FLAG2='1',
`redefined.
`
`the meaning of IDENT1 may be
`
`CAT
`
`TYPE
`
`FUNC
`
`IDENT2
`
`D
`
`—
`
`—
`
`-
`
`~
`
`-
`
`‘O00’.
`
`'10’.
`
`'100'.
`
`Ident of the requesting radio unit.
`
`'0'
`'1'
`
`if the caller is requesting speech communication.
`if the caller is requesting data communication.
`
`Note: If EXT=‘0‘/FLAG2=‘1',
`redefined.
`
`the meaning of bit D may be
`
`contd.
`
`Page 5-28
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 62
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 62
`
`

`
`
`
`RSVD
`
`- Reserved for future definition. Default value=‘0'.
`
`EXT
`
`—
`
`'0' if IDENT1 is not a short addressing PABX extension
`number.
`
`'1'
`
`if IDENT1 is a short addressing PABX extension number.
`
`FLAG1
`
`- For a group call (common-prefix or interprefix):
`'0' - enable called users to reply
`'1' — disable called users from replying.
`For a short addressing call to a PABX extension,
`FLAG1/FLAG2 indicates the appropriate PABX exchange.
`For a general call to the PSTN:
`'0' — number has
`up to 9 dialling digits
`'1' - number has 10 to 31 dialling digits.
`For all other types of call, FLAG1 is reserved for future
`definition. Default value='0'.
`
`Note: If EXT='O'/FLAG2='l',
`redefined.
`
`the meaning of FLAG1 may be
`
`FLAG2
`
`~ For a short addressing call to a PABX extension,
`FLAG1/FLAG2 indicates the appropriate PABX exchange.
`For all other types of call (i.e.
`if ExT='0'):
`'0' — caller is not requesting a special mode of
`service.
`
`'1' — caller is requesting a special mode of service
`previously arranged with the system.
`In this
`case,
`the meanings of fields IDENT1, D and FLAGI
`may be redefined.
`See also section 10.
`
`P
`
`- Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 63
`
`Page 5-29
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 63
`
`

`
`O O O O O O O O O
`
`.
`
`0
`
`.
`
`. O O O O O O O O O O
`
`5.5.3.l.6 Reguest to Register Message. RQR
`
`This message is transmitted to the TSC on a control channel by a radio
`unit requesting to register.
`See section 8 for the registration
`procedures.
`
`Registration may be required for the tracking of roamers, for wide-
`area systems with multiple control channels and for polling systems.
`
`
`
`PFIX — Prefix of the requesting radio unit.
`
`IDENT1
`
`CAT
`
`TYPE
`
`FUNC
`
`-
`
`-
`
`-
`
`—
`
`Ident of the requesting radio unit.
`
`'O0O'.
`
`'10’.
`
`'l01'.
`
`INFO ~ Available for customisation by systems,
`to convey additional
`information to the TSC. Null value = all 'O's.
`
`RSVD
`
`- Reserved for future definition. Default value = ‘O00’.
`
`P
`
`- Parity check bits.
`
`Page 5-30
`Petitioner Cisco Systems - Exhibit 1005 - Page 64
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 64
`
`

`
`
`
`5 . 5 . 3 . 1 . 7 Reggest Status Transaction, RE
`
`This message is transmitted to the TSC on a control channel by a radio
`
`unit:
`
`-
`
`to request that status information be relayed to the
`addressed line unit or radio unit, or
`
`-
`
`to send tatus information to the '1'5C.
`
`The status field in an RQQ message consists of 5 bits, allowing 32
`different status values.
`Two of these values have been predefined (see
`below).
`
`the RQQ message contains all the
`For a common—prefix status message,
`information necessary for the transaction.
`For an interprefix status
`message,
`the RQQ message is used to request entry into the extended
`addressing mode.
`See section 13 for the status procedures.
`
`IDENT1
`
`1
`
`CAT
`
`110
`
`TYPE
`10
`
`FUNC
`
`IDENT2
`
`STATUS
`
`1
`
`7
`
`13
`
`1
`
`3
`
`2
`
`3
`
`13
`
`5
`
`16
`
`PFIX - Prefix of the requesting radio unit.
`
`IDENT1
`
`— Called party or gateway:
`Ident
`— for a common—prefix transaction
`IPFIXI — for an interprefix transaction
`TSCI
`- for a transaction with the TSC.
`
`CAT
`
`TYPE
`
`FUNC
`
`IDBNT2
`
`—
`
`-
`
`—
`
`—
`
`‘O00’.
`
`'10‘.
`
`'l10'.
`
`Ident of the requesting radio unit.
`
`STATUS
`
`- For a transaction with a line unit or radio unit:
`
`‘C0000’
`
`'OOOOl'
`
`'111l1'
`
`requests that the addressed unit
`call back with a speech call
`(no other status information
`indicated).
`to '111l0‘ are user-defined status values.
`
`cancels a previous speech call request
`(no other status information
`indicated).
`
`For a transaction with the TSC:
`
`'00O0O‘
`'O0O01'
`'11l11'
`
`indicates "off—hook" or equivalent.
`to '111l0‘ are system-defined status values.
`indicates
`"on-hook" or equivalent.
`
`P
`
`- Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 65
`
`Page 5-31
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 65
`
`

`
`
`
`5.5.3.l.8 Re est to Transmit Short Data Hessa e R
`
`This message is sent by a radio unit to request permission to transmit
`a short data message {comprising the HEAD address codeword and up to four
`data codewords). After receiving the request,
`the Tsc uses the AHYC
`message to instruct the requesting unit to transmit the data message on the
`control Channel.
`See section 14 for the short data message procedures.
`
`FLAG1 FLAG2
`
`1
`
`CAT
`
`TYPE
`
`FUNC
`
`IDENT2
`
`EXT
`
`PFIX - Prefix of the requesting radio unit.
`
`IDENT1
`
`CAT
`TYPE
`FUNC
`
`IDENT2
`
`SLOTS
`
`- Called party or gateway:
`Ident
`-
`for a common-prefix call
`IPFIXI
`—
`for an interprefix call
`ALLI
`-
`for a system-wide call
`number
`-
`for a short addressing call to a PABX extension
`(EXT='1')
`for a call to a "long" PABX extension number
`for a Call to a prearranged PSTN destination
`for a call to a general PSTN destination
`for a transaction with the TSC.
`
`—
`PABXI
`PSTNSIj -
`PSTNGI
`-
`TSCI
`-
`
`-
`-
`-
`
`-
`
`‘O00’.
`'10’.
`‘Ill’.
`
`Ident of the requesting radio unit.
`
`- The number of timeslots required for the data message:
`'00’
`reserved
`'01‘
`reserved
`
`'10‘
`'11‘
`
`(address codeword + 1 or 2 data codewords)
`two slots
`three slots (address codeword + 3 or 4 data codewords)
`
`EXT
`
`-
`
`'0'
`'1'
`
`if IDENT1 is not a short addressing PABX extension number.
`if IDENTl is a short addressing PABX extension number.
`
`FLAG1
`
`- For a short addressing call to a PABX extension.
`FLAG1/FLAG2 indicates the appropriate PABX exchange.
`For a general call to the PSTN:
`'0' — number has
`up to 9 dialling digits
`'1' — number has 10 to 31 dialling digits.
`For all other types of call, FLAG1 is reserved for future
`definition. Default value='0'.
`
`FLAG2
`
`- For a short addressing call to a PABX extension,
`FLAGI/FLAG2 indicates the appropriate PABX exchange.
`For all other types of call, FLAG2 is reserved for future
`definition. Default value='O'.
`
`P
`
`- Parity check bits.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 66
`
`Page 5-32
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 66
`
`

`
`5.5.3.2 Aho Hesse es
`
`T
`
`'10’
`
`These messages are transmitted by a TSC;
`an addressed radio unit.
`
`they demand a response from
`
`The basic structure is illustrated below but, for clarity of
`
`the message for each function is detailed separately in
`definition,
`sections 5.5.3.2.1 to 5.5.3.2.B.
`
`(Note that the request messages sent by radio units have the same
`Category and Type as the Ahoy messages sent by the TSC.)
`
`
`
`IDENTI
`
`1
`
`7
`
`13
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`10
`
`FUNC
`
`PARAMETERS
`
`3
`
`2
`
`3
`
`18
`
`
`
`16
`
`PFIX — Prefix.
`
`IDENT1
`
`CAT
`
`TYPE
`
`FUNC
`
`—
`
`-
`
`-
`
`Ident of the called party or gateway.
`
`‘O00’.
`
`'10‘.
`
`— Specifies the function of the Ahoy:
`‘O00’
`AHY
`General availability check
`‘O01’
`Free for customisation
`'D10'
`AHYX
`Cancel alert/waiting state
`‘O11’ Reserved for future use
`'l00' Reserved for future use
`'lO1' Reserved for future use
`'1lO'
`AHYQ
`Status message
`'ll1'
`AHYC
`Short data invitation.
`
`PARAMETERS
`
`—
`
`See following pages.
`
`P
`
`- Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 67
`
`Page 5-33
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 67
`
`

`
`5.S.3.2.1 General Availability Check Message, AHY
`
`This message is transmitted on a control channel by the TSC as
`follows.
`
`a.
`
`b.
`
`c.
`
`It may be transmitted to a called radio unit to establish the
`availability of the called unit/user prior to allocating a traffic
`channel for a call
`(see 9.1.1.5), or prior to including a unit in an
`existing call (see 11.1.5).
`
`It may be sent to check the availability of a called radio unit before
`the TSC transmits a short data message (HEAD); see 14.1.6.
`
`It may be sent to a requesting radio unit to check that it is still in
`radio Contact and to restart its waiting timer (see, for example,
`sections 8.2.1.3, 9.1.1.7 and 9.1.1.10).
`
`AHY may also be sent by the TSC to a radio unit on a traffic channel,
`for example to check that the unit has reached, or is still on,
`the channel
`(see 6.1.2.1 and 9.1.2.2), or to restart the waiting timer of a radio unit
`which has requested an Include call
`(see 11.1.7).
`
`to
`one data codeword may be appended to the AHY address codeword,
`convey additional information, depending on the value of bit AD.
`(In this
`issue of the standard, this facility is used only when the AHY is sent on a
`control channel to a called radio unit).
`
`AHY demands an acknowledgement
`
`from the addressed unit:
`
`i)
`
`For AD
`
`'0'
`
`the addressed unit responds in
`- On a control channel,
`the slot following the AHY.
`On a traffic channel,
`the unit times its response
`from the end of the AHY address codeword.
`
`ii)
`
`For AD
`
`II
`
`|-'-
`
`I
`
`the addressed unit responds in
`On a control channel,
`the slot following the data codeword (i.e.
`in the
`slot following the slot that contains the data
`codeword].
`On a traffic channel,
`the unit times its
`response from the end of the data codeword.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 68
`
`contd.
`
`Page 5-34
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 68
`
`

`
`1
`
`1
`
`PFIX IDENT1
`
`7
`
`13
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`10
`
`FUNC
`000
`
`IDENT2
`
`3
`
`2
`
`3
`
`13
`
`1
`
`1
`
`1
`
`1
`
`1
`
`16
`
`PFIX - Prefix of the radio unit.
`
`IDENT1
`
`- Called party or gateway:
`
`
`
`
`
`a)
`
`For POINT='O' (i.e. availability check on called unit).
`IDENTl is the ident of the called radio unit.
`
`
`
`
`
`
`
`
`
`
`
`
`h)
`
`For POINT='l' (i.e. availability check on calling unit),
`IDENT1 is the called party or gateway as follows:
`Ident
`- for a common-prefix call
`IPFIXI
`- for an interprefix call
`ALLI
`- for a system-wide call
`PABXI
`- for a call to a PABX extension
`
`PSTNSIj - for a call to a prearranged PSTN destination
`PSTNGI
`— for a call to a general PSTN destination
`TSCI
`— for an RQQ or RQC transaction with the TSC
`DIVERTI — for general cancellation by a recipient of
`diversions.
`
`For restarting the waiting timer of a radio unit that has
`requested registration,
`IDENTI = REGI.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`CAT
`TYPE
`FUNC
`
`-
`-
`-
`
`‘O00’.
`'10‘.
`‘O00’.
`
`
`
`IDENT2
`
`— Calling party or gateway:
`
`a)
`
`
`
`
`
`
`
`
`
`
`
`For POINT='0' (i.e. availability check on called unit),
`IDENT2 is the calling party or gateway as follows:
`INCI
`-
`for an Include call availability check
`SDMI
`-
`for a short data message availability check
`DUMMYI
`-
`for a "no—call" test availability check
`For all other types of call,
`Ident
`—
`for a common-prefix call
`IPFIXI
`—
`for an intarprefix call
`PABXI
`—
`for a call from a PABX extension
`PSTNGI
`-
`for a call from the PSTN.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`the address of the calling unit
`If IDENT2 = IPFIXI or IHCI,
`may be provided in an appended data codeword (see below).
`
`b)
`
`For POINT='l' (i.e. availability check on calling unit),
`IDENT2 is the ident of the calling radio unit.
`
`contd.
`
`Page 5-35
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 69
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 69
`
`

`
`D
`
`POINT
`
`If the calling party requested speech communication
`{i.e. RQS(DT=G) or RQE(D=0)).
`then D='0'.
`Otherwise, D='l'.
`
`(For an AHY sent to restart the waiting timer of a radio unit
`sending "offshook" or "on-hook" signalling, ='l').
`
`'0' demands an acknowledgement from the unit whose
`individual address is PFIX/IDENTl.
`'1' demands an acknowledgement
`from the unit whose
`individual address is PFIX/IDENT2.
`See sections 9.2.2.2, 9.2.2.3 and 9.2.3.2 for the appropriate
`acknowledgement.
`
`CHECK
`
`AHY message on a control channel:
`
`a)
`
`'1'
`
`(i.e. availability check on called unit),
`For POINT='O'
`'0'
`indicates that the TSC is checking only that the unit
`is in radio contact
`(and can accept this call).
`indicates that the TSC is also checking:
`—
`for D='O', whether the unit‘s user is ready
`for a speech call
`for D='l'. whether the unit's data equipment
`is ready.
`
`-
`
`b)
`
`For POINT='l' (i.e. availability check on calling unit),
`CHECK is reserved for future definition. Default
`value='0'.
`
`AHY message on a traffic channel:
`CHECK is reserved for future definition. Default
`value='0'.
`
`'0'
`
`if the calling party requested a non—emergency call or
`transaction.
`
`'1'
`
`if the Calling party requested an emergency call.
`
`to restart the waiting timer of a radio unit
`(For an AHY sent
`requesting registration or an Include call, or sending
`"off—hook" or ”on—hook" signalling, E='O').
`
`'0' if there is no appended data codeword.
`'1'
`if there is a data codeword appended to the AHY.
`
`Parity check bits.
`
`AD
`
`P
`
`
`
`Petitioner Cisco Systems - Exhibit 10(Y5’“-‘Page 70
`
`, _ ii____i_
`
`Page 5-36
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 70
`
`

`
`Data codeword followin AH’! address codeword:
`
`For a (control channel) availability check on the called unit, if bit
`AD in the AHY address codeword is set to '1', then a single data codeword
`with the following structure is appended to the AH! codeword.
`
`1
`
`3
`
`44
`
`16
`
`FORM — Defines the format of the PARAMETERS field (see below).
`‘O00’
`- value used to convey the address of the calling
`unit in an interprefix or Include call.
`to '100' are reserved for future use.
`
`'0D1‘
`
`'10l'
`
`to 'll1' are spare for customisation.
`
`PARAMETERS
`
`—
`
`See parameter formats below.
`
`P
`
`- Parity check bite.
`
`Parameter formats
`
`FORM = ‘O00’
`
`PARAMETERS
`
`24
`
`7
`
`13
`
`RSVD
`
`- Reserved for future use.
`Default value = all
`'O's.
`
`PFIX2
`
`- Prefix of the calling unit.
`
`IDENT2
`
`-
`
`Ident of the calling unit.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 71
`
`Page 5—37
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 71
`
`

`
`5.5.3.2.2 This section is free for customisation.
`
`5.5.3.2.3 Cancel Alert Waitin State Messa e
`
`AHYX
`
`to inform
`This message is transmitted on a control channel by the TSC,
`a called radio unit of cancellation of an incoming traffic channel call
`e.g. if the calling unit no longer wants the call.
`It demands a response
`ACK(QUAL=1)
`in the next slot from the called unit i.e.
`the unit whose
`individual address is PFIX/IDENT1 - see 9.2.2.4.
`(Note that this message
`is used only for cancelled individual calls to radio units.)
`
`IDENT2
`
`PFIX — Prefix of the called radio unit.
`
`IDENT1
`
`CAT
`
`TYPE
`
`FUNC
`
`IDENT2
`
`-
`
`-
`
`—
`
`-
`
`Ident of the called radio unit.
`
`‘O00’.
`
`'10’.
`
`‘O10’.
`
`— Calling party or gateway:
`Ident
`-
`for a common-prefix call
`IPFIXI
`-
`for an interprefix call
`PABXI
`-
`for a call from a PABX extension
`PSTNGI
`-
`for a call from the PSTN
`INCI
`-
`for an Include call.
`
`RSVD
`
`‘ Reserved for future definition. Default value = 'OO0O0'.
`
`P
`
`— Parity check bits.
`
`Page 5—38
`Petitioner Cisco Systems - Exhibit 1005 - Page 72
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 72
`
`

`
`5.5.3.2.4 This section is reserved for future use.
`
`5.5.3.2.5 This section is reserved for future use.
`
`5.5.3.2.6 This section is reserved for future use.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 73
`
`Page 5-39
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 73
`
`

`
`5.5.3.2.? Status Aho Messa e
`
`AHY
`
`This message is transmitted on a control channel by a TSC to inform a
`called radio unit of status information sent by a radio or line unit.
`For
`an interprefix status message,
`IDENT2 in the AHYQ address codeword is set
`to IPFIXI and a data codeword is appended containing the calling unit's
`address.
`AHYQ is also used to send a S—bit status message to a radio unit
`from the TSC.
`
`AHYQ demands an response ACK, ACKX, ACKV or ACKB from the called unit
`(i.e. the unit whose individual address is PFIX/IDENT1):
`
`-
`
`-
`
`in the slot following the AHYQ address codeword, for a
`common-prefix status message (IDENT2 = ident) or a message
`from the TSC (IDENT2 = TSCI);
`in the slot following the appended data codeword, for an
`interprefix status message (IDENT2 = IPFIXI).
`
`See 13.2.1.5 and 13.2.3.1 for the Status Ahoy procedures.
`
`AHYQ address codeword:
`
`
`
`IDENT2
`
`STATUS
`
`CAT
`
`TYPE
`10
`
`FUNC
`110
`
`1
`
`7
`
`13
`
`1
`
`3
`
`2
`
`3
`
`13
`
`5
`
`16
`
`PFIX — Prefix of the called radio unit.
`
`IDENT1
`
`CAT
`TYPE
`FUNC
`
`IDENT2
`
`—
`
`-
`~
`—
`
`Ident of the called radio unit.
`
`'OO0'.
`'10‘.
`'1l0'.
`
`- Calling unit or gateway:
`Ident
`— for a common-prefix transaction
`IPFIXI
`— for an interprefix transaction
`TSCI
`- for a message from the TSC.
`
`the address of the calling unit
`If IDENT2 = IPFIXI,
`provided in an appended data codeword (see below).
`
`is
`
`STATUS
`
`this field
`— For a status message from a radio or line unit,
`contains the status information sent by the calling unit:
`‘O00OO'
`requests a speech call
`‘O0O01'
`to '1lllO' are user~defined status values
`
`‘1l11l‘
`
`cancels a previous speech call request.
`
`For a status message from the TSC,
`field is system—dependent.
`
`the meaning of the STATUS
`
`P
`
`— Parity check bits.
`
`contd.
`
`Page 5-40
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 74
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 74
`
`

`
`
`
`Data codeword followin AHY address codeword:
`
`IDENT2 in the AHYQ address
`For an interprefix status transaction,
`codeword is set to IPFIXI and a data codeword is appended containing the
`calling unit's address.
`
`a Rsvo mxz mm: '
`
`1
`
`27
`
`7
`
`13
`
`16
`
`RSVD
`
`- Reserved for future use. Default value = all
`
`'0's.
`
`PFIX2
`
`- Prefix of the calling unit.
`
`IDENT2
`
`-
`
`Ident of the calling unit.
`
`P
`
`— Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 75
`
`Page 5-41
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 75
`
`

`
`5.S.3.2.8 Short Data Invitation Message, AHYC
`
`This message is used by the TSC to instruct a radio unit to send a
`short data transmission (see sections 9.2.2.1, 11.3.1 and 15.2).
`
`AHYC is used in two Modes:
`
`-
`
`-
`
`In Mode 1, AHYC instructs a calling radio unit to send addressing
`information (see SAMIS, section S.6.l.2.2) or RQC data (see HERD,
`section 5.6.2), when a preceding request message from the radio
`unit has indicated the requirement.
`Mode 1 is distinguished by
`setting PFIX/IDENT2 to a radio unit's individual address.
`
`In Mode 2, AHYC demands that a radio unit transmits a data message
`of a prescribed type (see section 15);
`for example,
`the TSC may
`demand the serial number of a radio unit.
`It is an interrogation
`mode, not part of a call requested by the radio unit. Mode 2 is
`distinguished by setting PFIX/IDENT1 to a radio unit's individual
`address (with IDENT2 as a non-radio-unit ident).
`
`The type of data to be transmitted by the radio unit is indicated by
`the DESC field and the non—radio-unit ident: the meaning of DESC can be
`different for the two modes.
`
`AHYC may be sent on either a control channel or a traffic channel.
`
`1
`
`1
`
`PFIX IDENTI
`
`7
`
`13
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`10
`
`FUNC
`
`IDENT2
`
`
`
`3
`
`2
`
`PFIX - Prefix of the radio unit.
`
`IDENT1
`
`— Called unit, gateway or special
`
`ident:
`
`a. Mode 1 (instructing the unit with address PFIX/IDENT2
`to send data):
`IPFIXI - for inviting extended addressing information for
`an interprefix call
`PSTNGI — for inviting dialled digits for a call to the
`PSTN
`
`PABXI
`
`— for inviting address information for a call to a
`PABX extension
`
`DIVERTI — for inviting the blocked address for third—party
`call diversion
`
`SDMI — for inviting RQC data.
`
`b. Mode 2 (interrogation):
`
`Ident of the radio unit.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 76
`
`contd.
`
`Page 5-42
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 76
`
`

`
`CAT
`
`TYPE
`
`FUNC
`
`-coo’.
`
`-10'.
`
`'11l'.
`
`IDENT2
`
`Calling party:
`
`a. Mode 1:
`
`Ident of the calling radio unit.
`
`b. Mode 2
`
`(instructing the unit with address PFIX/IDENTI
`to send data): Ident of the interrogator:
`
`For DESC='OO0' (serial number check),
`
`IDENT2 = TSCI.
`
`SLOTS
`
`The number of slots reserved for the data message:
`
`SLOTS
`
`No. of slots
`
`No. of codewords
`
`'00‘
`
`'01‘
`'10‘
`'11‘
`
`reserved
`
`1
`2
`3
`
`address codeword only
`address codeword + 1 or 2 data codewords
`address codeword + 3 or 4 data codewords
`
`3LOTS shall correspond to the request message from
`For Mode 1.
`the radio unit as follows:
`
`IDENTI
`
`in AHYC
`
`SLOTS
`
`IPFIXI
`
`PSTNGI
`
`PABXI
`DIVERTI
`
`SDHI
`
`'01‘
`
`'01’ for up to 9 digits, or
`'10’ for 10 to 31 digits
`'01‘
`'01‘
`
`equal to SLOTS from the RQC
`
`For Mode 2, SLOTS shall correspond to the data required from the
`radio unit as follows:
`
`contd.
`
`Page 5-43
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 77
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 77
`
`

`
`DESC
`
`Data message codeword descriptor. This field indicates the type
`of data message with which the radio unit shall respond:
`
`i) when the first codeword of the radio unit's data message
`is required to be SAMIS, DESC is set to the value of the
`DESC field to be used in the SAMIS as follows;
`(note that
`the meaning of the SAHIS message may be different for
`Modes 1 and 2):
`
`a. Node 1:
`
`'OOO'
`
`— for inviting extended addressing information for
`an interprefix call, or the blocked address for
`third—party diversion
`'O01' — for inviting dialled digits for a call to the
`PSTN
`
`'0lO'
`
`— for inviting address information for a call to a
`PABX extension
`‘011' - Reserved
`
`'1OO to 111' are spare
`
`b. Mode 2:
`
`- for demanding the serial number of a radio unit.
`‘O00’
`‘O01 to 011' are reserved
`
`'l0O to 111' are spare
`
`ii) When the first codeword of the radio unit's data message
`is required to be HEAD (i.e.
`IDENTl=SDMI). DESC = ‘O00’.
`DESC = '00l'
`to ‘011' are reserved.
`
`DESC = '100'
`
`to ‘111' are spare
`
`Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 78
`
`Page 5—44
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 78
`
`

`
` T
`
`e '11’
`5.5.4 Miscellaneous Control Messa es
`
`
`
`The basic
`These are various messages required for system control.
`structure is illustrated below, but the detailed structure for each message
`is defined separately on the following pages.
`
`
`
`1
`
`1
`
`PARAHS
`
`20
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`ll
`
`FUNC
`
`PARAMETERS
`
`
`
`3
`
`2
`
`3
`
`18
`
`16
`
`PARAMS
`
`-
`
`Dependent on FUNC.
`Where applicable, PARAMS is an address (PFIX/IDENT1);
`otherwise bits 2-21 are used for other purposes.
`See following pages.
`
`CAT
`
`TYPE
`
`-
`
`-
`
`‘O00’.
`
`'11‘.
`
`FUNC
`
`- Specifies the function of the message:
`‘O00’
`MARK
`Control channel marker
`
`‘OOl' MAINT
`‘O10’
`CLEAR
`
`Call maintenance message
`Clear down from allocated channel
`
`Move to specified control channel
`MOVE
`'0ll'
`Broadcast message for system parameters
`BCAST
`‘lOO'
`'101' Reserved for future use
`'llO' Reserved for future use
`'l11' Reserved for future use
`
`PARAMETERS
`
`—
`
`See following pages.
`
`P
`
`- Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 79
`
`Page 5-45
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 79
`
`

`
`5.5.4.1 Control Channel Marker, MARK
`
`This message may be transmitted on a control channel by a TSC. For
`example, it may be sent as the first address codeword(s) on a newly
`designated control channel
`in order to accelerate control channel
`acquisition by radio units (see 3.3.3.1).
`It does not need an address
`PFIX/IDENTl, so bits 2-21 are reused.
`
`The message fields A and B are chosen so that:
`
`i)
`
`the parity check bits always form the control channel codeword
`synchronisation sequence, SYNC (see section 3.2.1.1), and
`
`ii)
`
`the number of bit transitions included between bits 33 and 49 is the
`maximum achievable,
`taking into account condition i) above.
`The bit
`values of these fields will depend on CHAN4 and the system identity
`code.
`An algorithm for generating these fields is given in
`Appendix 4.
`
`1
`
`l
`
`CHAN4
`
`SYS
`
`4
`
`1
`
`15
`
`l
`
`1
`
`CAT
`000
`
`TYPE
`11
`
`FUNC
`000
`
`P
`11000lO0llO10lll
`
`
`
`3
`
`2
`
`3
`
`18
`
`16
`
`CHAN4
`
`— Least significant four bits of the channel number
`of the control channel on which the message is sent
`
`A
`
`SYS
`
`CAT
`
`TYPE
`
`FUNC
`
`B
`
`P
`
`—
`
`-
`
`—
`
`-
`
`-
`
`—
`
`see i) and ii) above and Appendix 4.
`
`System identity code of the transmitting system.
`
`‘O00’.
`
`‘ll’.
`
`‘O00’.
`
`see i) and ii) above and Appendix 4.
`
`— Parity check bits.
`These complete the codeword and also form the control
`channel codeword synchronisation sequence.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 80
`
`Page S~46
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 80
`
`

`
`5.5.4.2 Call Maintenance Message, MAINT
`
`These messages are transmitted on an allocated traffic channel during
`a call.
`
`'O11')
`‘O10’,
`'001‘,
`A radio unit sends MAINT messages (OPER = 'OO0',
`during a call; see 9.2.3.
`The TSC may send MAINT (OPER = 'l10'} to clear
`down from the channel any radio units that should not be there, and may
`send HAINT (OPER = '111') to disable radio units from user transmission.
`
`1
`
`PFIX IDENTI
`
`
`
`1
`
`7
`
`13
`
`PFIX — Prefix.
`
`1
`
`1
`
`CAT
`D00
`
`TYPE
`11
`
`FUNC
`001
`
`CHAN
`
`
`
`3
`
`2
`
`3
`
`10
`
`3
`
`5
`
`16
`
`IDENTI
`
`- Transmitted by radio unit:
`PFIX/IDENTl is the unit's individual address if it was
`individually addressed by the GTC message; otherwise
`PFIX/IDENT1 is either its individual address or the group
`address (PFIX/IDENTI)
`from the GTC, as specified by the
`system — see 5.5.4.Sc, 9.2.2.6 and 9.2.3.
`
`Transmitted by TSC:
`OPER = 'l10'
`PFIX/IDENTl is the "call-labelling“ address:
`either address from the GTC message.
`Individual or group ident, or ALLI;
`see below.
`
`OPER = '111‘
`
`CAT
`TYPE
`FUNC
`
`-
`-
`-
`
`'000'.
`'11‘.
`‘O01’.
`
`CHAN
`
`- Channel number of the channel on which the message is sent.
`
`OPER
`
`—
`
`‘O00’ Pressel on
`'OO1' Pressel Off
`
`‘O10’ Periodic message within an item
`‘O11’ Disconnect message, end of channel use
`'100'
`Spare for customisation (eg radio transmitter
`power control)
`'101' Reserved for future use
`
`'l10' Clear down radio units for which PFIX/IDENT1 is
`not a valid call-labelling address
`'11l' Disable user transmission, as follows:
`a)
`an individual radio unit,
`if PFIX/IDENT1 is an
`individual address
`
`b)
`
`c)
`
`called radio units in a group,
`the group address
`all radio units on the channel,
`
`if PFIX/IDENTI is
`
`if IDENTl is ALLI.
`
`RSVD
`
`'100' when these
`- Reserved for future use. Except for OPER =
`bits are available for synchronisation when reserved,
`default value = '0OO00'.
`
`P
`
`— Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 81
`
`Page 5-4?
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 81
`
`

`
`5.5.4.3 Clear-Down Message, CLEAR
`
`This message is transmitted by a TSC; it directs all radio units to
`clear down from a traffic channel.
`It does not need an address
`
`PFIX/IDENTI, so bits 2-21 are reused.
`
`1
`
`1
`
`CHAN
`
`CONT
`
`10
`
`10
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`11
`
`FUNC
`010
`
`RSVD
`
`SPARE
`
`REVS
`101010101010
`
`3
`
`2
`
`3
`
`4
`
`2
`
`12
`
`P
`
`16
`
`CHAN
`
`- Channel number of the traffic channel on which the
`
`message is sent.
`
`CONT
`
`- Channel number of the Control channel to which radio
`
`units should move (unless CONT = ‘OO00OOOO0O',
`case the channel movement is system-dependent).
`
`in which
`
`CAT
`
`TYPE
`
`FUNC
`
`—
`
`-
`
`—
`
`‘O0O'.
`
`‘ll’.
`
`'010'.
`
`RSVD
`
`— Reserved for future use. Default value =
`
`‘D000’.
`
`SPARE
`
`— These bits are available for customisation.
`
`REVS
`
`— Bit reversals, ending with a '0'.
`
`P
`
`— Parity check bits.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 82
`
`Page S—48
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 82
`
`

`
`5.5.4.4 Move to Control Channel, MOVE
`
`This message is transmitted on a control channel by a TSC; it directs
`selected radio units to a different control channel.
`(See sections 6.1.1
`and 7.4.2).
`
`
`
`IDENT1
`
`13
`
`1
`
`l
`
`CAT
`000
`
`TYPE
`11
`
`FUNC
`011
`
`CONT
`
`(M)
`
`RSVD
`
`SPARE
`
`3
`
`2
`
`3
`
`10
`
`5
`
`2
`
`1
`
`16
`
`
`
`PFIX
`
`Prefix.
`
`IDENTI
`
`PFIX/IDENT1 specifies the radio units that should move.
`Only the (M)
`least significant bits of the 20-bit address
`are used;
`the remaining address bits may be set
`arbitrarily.
`
`CRT
`
`'OOO'.
`
`TYPE
`
`'11‘.
`
`FUNC
`
`CONT
`
`(M)
`
`RSVD
`
`'O1l'.
`
`Channel number of the control channel to which
`
`the addressed radio units should move (unless
`CONT = 'OOO0OO0OOO‘,
`in which case the channel
`movement is system-dependent).
`
`Address qualifier.
`
`Reserved for future use. Default value = '00‘.
`
`SPARE
`
`This bit is available for customisation.
`
`Parity check bits.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 83
`
`Page 5-49
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 83
`
`

`
`5.5.4.5 Broadcast Message, BCAST
`
`This message is transmitted on a control channel by a TSC; it contains
`information about system parameters for either this system or another
`system.
`It does not need an address PFIX/IDENTI, so bits 2-21 are reused.
`
`32 different types of information can be broadcast using BCAST
`messages, by setting the SYSDEF and parameter fields appropriately. The
`parameter fields for each SYSDEF are detailed on the following pages.
`
`1
`
`l
`
`SYSDEF
`
`SYS
`
`S
`
`15
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`11
`
`FUNC
`100
`
`PARAMETERS
`
`
`
`3
`
`2
`
`3
`
`18
`
`16
`
`SYSDEF
`
`- Specifies which system parameters are being broadcast:
`
`'OO0O0'
`‘0O0O1'
`
`'OOOl0'
`‘D0011’
`'OO100'
`
`'OOlOl'
`
`'o011o'
`:
`‘D1111’
`
`‘l0OOO'
`:
`'1llll'
`
`)
`)
`)
`
`)
`)
`)
`
`Announce control channel
`withdraw control channel
`
`Specify call maintenance parameters
`Specify registration parameters
`Broadcast adjacent site control channel
`number
`Vote now advice
`
`Reserved for future use
`
`Spare for customisation of services
`
`SYS
`
`-
`
`system identity code of the system to which the broadcast
`message refers.
`
`CAT
`
`TYPE
`
`FUNC
`
`—
`
`-
`
`-
`
`‘O00’.
`
`'11‘.
`
`'l0O'.
`
`PARAMETERS
`
`— Parameter fields — see following pages.
`
`P
`
`— Parity check bits.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 84
`
`Page 5-50
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 84
`
`

`
`
`
`Parameter fields in BCAST messages
`
`a)
`
`
`
`
`
`SYSDEF =Announce control channel ‘D0000’
`
`This message announces a channel that may be used for control by the
`named system; radio units may then include it in their list of channels to
`scan.
`
`
`
`1
`
`1
`
`SYSDEF
`OOCOO
`
`SYS
`
`5
`
`1 5
`
`1
`
`1
`
`CAT
`000
`
`TYPE
`11
`
`FUNC
`100
`
`CHAN
`
`
`
`3
`
`2
`
`3
`
`10
`
`2
`
`6
`
`16
`
`CHAN
`
`— Channel number of the control channel being announced.
`
`SPARE
`
`— These bits are available for customisation.
`
`RSVD
`
`- Reserved for future definition. Default = all 'O's.
`
`
`
`
`
`SYSDEF =b) Withdraw control channel '0O001'
`
`This message withdraws a channel that could previously be used for
`control by the named system; radio units may then delete it from their list
`of channels to scan.
`
`1
`
`SYSDEF
`00001
`
`SYS
`
`1
`
`CAI‘
`000
`
`TYPE
`11
`
`FUNC
`100
`
`
`
`CHAN
`
`RSVD
`
`P
`
`1
`
`5
`
`15
`
`1
`
`3
`
`2
`
`3
`
`10
`
`2
`
`6
`
`16
`
`CHAN
`
`— Channel number of the control channel being withdrawn.
`
`SPARE
`
`- These bits are available for customisation.
`
`RSVD
`
`- Reserved for future definition. Default = all
`
`'O's.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 85
`
`Page 5-51
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 85
`
`

`
`
`
`c)
`
`Specify call maintenance parameters [SYSDEF = 'O0O10'}
`
`This message specifies:
`
`(i)
`
`(ii)
`
`(iii)
`
`whether this system requires radio units to send call
`maintenance messages on traffic channels periodically within
`speech items;
`if so, it specifies the maximum interval between
`the periodic messages;
`
`whether this system requires radio units on traffic channels to
`send NPON Pressel on messages at the start of speech items;
`
`whether this system requires that a called unit in a group
`shall set PFIX/IDENT1 in MAINT messages it sends to its
`individual address or to the group address from the GTC
`message.
`
`This message shall be sent only by the system to which the broadcast
`refer