if a PDN entry point is to be reached via an intermediate network
`then the appropriate intermediate gateway is set in IDBNT1 and
`further addressing is accomplished on the data channel in the format
`appropriate to that gateway.
`
`b.
`
`c.
`
`d.
`
`e.
`
`:5.
`
`g.
`
`the
`unless
`field shall be set to '0'
`FAD
`The
`destination address contains more than 9 digits.
`
`PABX/PSTN
`
`Field PORT indicates the required called port.
`
`if the calling party requires interactive
`Bit INTER is set to '1'
`contact with the called party.
`
`Bit LEVEL indicates whether the calling party is requesting high
`priority for resources.
`For INTER = '1', this requests high priority
`for the complete path to the called party; for INTER = '0' , it
`requests high priority only for the calling unit's link to the TSC.
`
`Bit MODEM indicates whether the unit is able to operate at the
`customised transmission rate.
`
`if high accuracy data transfer is
`Bit HADT shall be set to '1'
`thought to be supported by the TSC and is required.
`
`The radio unit shall attempt access until:
`
`i)
`
`ii)
`
`iii)
`
`it receives a valid response (see 17.l.2.1.2/3), or
`
`its user cancels the call (see 17.l.2.1.B), or
`
`the unit has sent the maximum
`the access attempt fails (i.e.
`number of transmissions NR/NDR and received no response, or its
`access time-out TC/TDC has expired (see 7.3.8 or 17.2.1.2.7)).
`
`In this case:
`
`-
`
`If the unit has not sent a request, it shall return to the
`state previous to the access attempt
`(and may indicate the
`failure to the service user).
`
`the unit shall wait for further call set—up
`- otherwise,
`signalling for the call; see 1'I.l.2.l.4 to l7.1.2.l.7.
`
`17.1.2.l.2 Valid responses to short addressing RQD(E=0)
`
`the calling unit shall accept the
`For a short addressing call,
`following messages as a valid response to its RQD and send no more
`requests:
`
`a.
`
`b.
`
`An acknowledgement ACKI(QUAL=l), ACKQ, ACKX or ACKV, with the same
`prefix and idents as the RQD.
`
`An acknowledgement ACK'I'(QUAL=0) with PFIX/IDENT2 as its individual
`address.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 241
`
`Page 17-23
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 241
`
`

`
`c.
`
`A Go To Transaction message GTT with PFIX/IDENT as its individual
`address, bit 0/R set to '1', an acceptable RATE and, for a request on
`a data channel, CHAN set to the number of that data channel.
`
`For other actions on receiving these messages, see sections
`l7.l.2.1.4 and l7.l.2.l.6, and l7.1.2.3.4 or l7.l.2.4.5.
`
`l7.l.2.l.3 Valid responses to extended addressing RQD(E=O)
`
`the calling unit shall accept the
`For an extended addressing call,
`following messages (with the same prefix and idents as the RQD) as a valid
`response to its RQD and send no more requests:
`
`a.
`
`b.
`
`An acknowledgement ACKI(QUAL=1), ACKv(QUAL=0) or ACKX.
`
`AHYC (i.e. an instruction to send the full called address
`information).
`
`For other actions on receiving these messages, see sections
`17.l.2.l.4 and l7-l.2.l.5.
`
`17.1.2.l.4 Acknowledgement received
`
`If a radio unit attempting access or waiting for further call set-up
`signalling for a standard data call receives an appropriate acknowledgement
`then it shall take action as indicated below.
`(For extended addressing
`calls, only ACKI(QUAL=l), ACKV(QUAL=0) and ACKX are appropriate until the
`full address information has been sent.)
`For idents, see 5.5.2.1.
`
`ACKI
`
`(QUAL=l)
`
`-
`
`Intermediate acknowledgement; more signalling to
`follow.
`
`ACKQ (QUAL=O)
`
`ACKQ (QUAL=l]
`
`ACKX (QUAL=0)
`
`ACKX (QUAL=1]
`
`-
`
`—
`
`-
`
`-
`
`All data channels are busy. wait for further
`signalling.
`
`Called party engaged. Wait for further signalling.
`
`Call adjudged to be invalid by TSC or called party;
`request rejected.
`
`the called party
`System overload, or for INTER='l‘
`is engaged or will not interact at this time, and
`the TSC has not queued the call; request rejected.
`
`ACKV (QUAL=0)
`
`~
`
`Called unit not
`abandoned.
`
`in radio contact or call set-up
`
`ACKV (QUAL=l)
`
`—
`
`Call not queued because the called party is unable
`to receive a call with the required facilities,
`e.g.
`the radio unit does not support HADT or
`interaction or cannot accept the requested PORT.
`
`ACKT (QUAL=0)
`
`*
`
`Called party's calls have been diverted.
`
`the unit shall wait for further
`If ACKI(QUAL=l) or ACKQ is received,
`signalling and may indicate to the service user the progress of the call.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 242
`
`Page 17-24
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 242
`
`

`
`
`
`If ACKX or ACKV is received, the unit shall return to the state
`previous to the call request and may indicate to the service user the
`reason for the failure of the call; it is recommended that receipt of
`ACKV(QUAL=O), ACKV(QUAL=l), BCKX(QUBL=0), and ACKX(QUAL=1) each be
`indicated in its own distinct manner.
`
`If a complete ACI(T(QU1\L=0) message is received,
`
`the unit shall either:
`
`a.
`
`b.
`
`-
`
`-
`
`(and may
`return to the state previous to the call request
`to the service user that the called party's calls have been
`diverted), or
`
`indicate
`
`wait for a time (T3 on the control channel, TDB on the data channel)
`(see below), and then attempt a new call to the diversion address
`given in the ACKT message:
`
`if IDENT1 does not equal IPFIXI or PSTNGI or PABXI, try on
`IDENT1;
`
`if IDENTI = IPFIXI or PSTNGI or PABXI, try the alternative
`called party given in the appended data codewor-3(3).
`
`IPFIXI and an appended data
`Note that ACK'1‘(QUnL=0), with IDENT1
`codeword,
`indicates either an interprefix diversion address or that the
`diversion address is of a different type from the original called address.
`Flag GF in the appended data codeword specifies whether the diversion
`address is an individual or group address; see 5.5.2.1.
`
`If an incomplete AcKT(QUAL=0) message is received (i.e.
`appended data codewords are decodeable),
`then:
`
`if not all the
`
`i)
`
`If the unit does not require the diversion address; it Shall return
`to the previous state (and may give an indication to the service
`user).
`
`ii)
`
`If the unit does require the diversion address then:
`
`-
`
`-
`
`if still attempting access for the call, it shall
`message and continue to attempt access;
`
`ignore the
`
`otherwise it shall wait for a repeat ACKT, returning to the
`previous state if a time TB/TDB elapses (in which case,
`it may
`indicate the failure to the service user).
`
`the unit shall not request
`After receiving ACKX or ACKV for the call,
`another non—emergency call of any type to the same called ident {or
`the
`gateway)
`for at least a time TB/TDB. After receiving ACKT for the call,
`unit shall not request another non-emergency call of any type for at least
`a time TB/TDB.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 243
`
`Page 17-25
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 243
`
`

`
`l7.1.2.1.5 Instruction to send address information
`
`A radio unit that is requesting an extended addressing standard data
`call on a control channel shall follow the procedure in 9.2.2.1 for sending
`the full address information, but with a revised check on the SLOTS field
`from the AHYC.
`The check that "SLOTS corresponds to the request",
`for an
`extended addressing data call, shall be taken as:
`
`If IDENT1 = PSTNGI and unit's call requires > 9 PSTN digits
`then SLOTS = '10‘.
`
`If IDENT1 = PSTNGI and unit's call requires < 10 PSTN digits
`then SLOTS = '01‘ or '10’.
`
`If IDENT1 not equal to PSTNGI
`then SLOTS = '01‘.
`
`The procedure for sending extended addressing information for a data
`call requested on a data channel is specified in section 17.l.2.4.1.
`
`l7.l.2.1.6 Availability check and channel command for own call
`
`A calling radio unit attempting access or waiting for further call
`set-up signalling for a standard data call shall obey the appropriate
`availability check and channel command procedures (see 9.2.2.2 to 9.2.2.5
`and 17.l.2.3.1 to l7.l.2.3.4, or 17.l.2.4.2 to 17.1.2.4.6).
`
`It shall assume that a GTT message it receives is for its requested
`standard data call if PFIX/IDENT is its individual address, bit O/R is set
`to '1‘, RATE is acceptable and,
`for a GTT on a data channel, CHAN is set to
`the number of that data channel. If also TRANS > ‘O000O0OO0O'
`then the unit
`
`shall regard the call link as established and may give an indication to the
`service user.
`
`17.l.2.l.7 Time—out after waiting
`
`A calling radio unit waiting for further call set—up signalling on the
`channel on which it attempted access for a standard data call shall return
`to the previous state if a time TW/TDW has elapsed since the last message
`it sent for the call, viz.
`
`RQD,
`
`requesting the standard data call
`
`(see l7.1.2.1.l)
`
`SAHIS, providing extended address information for the call (see
`or
`l7.1.2.l.S)
`
`in response to an AHY message with bit POINT = 1 and
`or ACK(QUAL=O), sent
`IDENTI as the called ident or gateway (see 9.2.2.3 or l7.l.2.4.2).
`
`It may also indicate the failure to the service user.
`
`OOOOOOOOOOOOOOOOOOOOOOO(
`
`
`
`Page 17-26
`Petitioner Cisco Systems - Exhibit 1005 - Page 244
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 244
`
`

`
`
`
`.
`
`17. 1.g.1.B call cancellation
`
`If the service user wishes to cancel the call, and the unit has not
`yet sent an RQD,
`then it shall return immediately to the previous state.
`otherwise, if the unit has sent an RQD, it shall attempt to send a call
`cancellation request RQX (see 5.5.3.1.3), complying with the appropriate
`random access protocol. It shall attempt access until one of the following
`OCCUEB:
`
`a.
`
`b.
`
`c.
`
`d.
`
`It receives AcK(QUAL=1), with the same prefix and idents as
`confirming cancellation of the call.
`
`the RQX,
`
`It receives Acxx, BCKV or 1\CK'1'(QUm'..=O) for the call it is
`to cancel.
`see also 17.l.2.1.4.
`
`attempting
`
`It receives a GTT message for the call it is attempting to cancel;
`this case, it shall obey the GT? procedure (see 17.1.2.3.4 or
`17.l.2.4.6),
`though it may then terminate the transaction.
`
`in
`
`It has sent the maximum number of transmissions NR/NDR and received
`no response, or it's access time-out Tc/TDC has expired.
`In this
`case, it shall return to waiting for signalling for the standard data
`call (see 17.1.2.1.4 to l7.l.2.1.'I).
`
`In cases a. and b., the unit shall return to the previous state.
`
`17.1.2.2 Procedures for Radio Units Reggesting Emergency Standard Data
`Calls
`
`A radio unit shall make only one emergency call set—up attempt at a
`time. While attempting access or waiting for further call set-up
`signalling for an emergency request,
`the unit shall not request another
`call of any type (unless the user first cancels the original call).
`It may
`make an emergency call at any other time.
`For example, it may interrupt a
`non-emergency call set-up attempt to request an emergency call;
`in this
`case it shall abandon the previous call attempt
`(without sending RQX).
`
`11'. 1. 2 .2 . 1 Regpest for an emergency standard data call
`
`A radio unit requests an emergency standard data call by sending an
`RQD(E=1) message on a control channel or data channel. The fields in the
`RQD message shall be set appropriately (see 5.7.1).
`Some TSCE may permit
`more than one emergency random access transmission in a frame; however.
`unless the radio unit knows the retry rate permitted by the TSC, it shall
`comply with the appropriate normal
`random access protocol - see 7.3 or
`17.2.1.2.
`
`The unit shall attempt access until it receives a valid response (see
`17.l.2.2.2). or until its user cancels the call
`(see 17.l.2.2.'l), or until
`the access attempt fails (i.e.
`the unit has sent the maximum number of
`transmissions (NE for the control channel. NDE for the data channel) and
`received no response, or its access time-out TC/TDC has expired).
`In the
`case of access failure, if the unit has not sent a request, it shall return
`to the previous state (and may indicate the failure to the service user);
`otherwise, it shall wait for further call set—up signalling for the call -
`see 17.l.2.2.3 to l7.l.2.2.6.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 245
`
`Page 17-27
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 245
`
`

`
`17.1.2.2.2 Respgnses to 3Qp{E=ll
`
`The calling unit shall accept the following messages (with the same
`prefix and idents as the RQD) as a valid response to its emergency RQD and
`send no more requests:
`
`a.
`
`b.
`
`An acknowledgement ACKE(QUAL=O).
`
`An AHYD message with bits POINT and E set to '1'.
`
`It shall then wait for further signalling for the call. See also
`section 9.2.2.3 or 17.l.2.4.2.
`
`l7.1.2.2.3 Sending extended address information
`
`For an extended addressing emergency standard data call, after
`receiving ACKE(QUAL=0) or AHY(POINT=1,E=l) for its call,
`the calling unit
`shall send the full called address information on receipt of an appropriate
`AHYC; see section 17.1.2.1.5.
`
`Until it receives ACKE(QUAL=O) or AHY(POINT=l,E=1), the unit shall
`respond to Mode 1 AHYC messages with ACKX(QUAL=0).
`
`l7.l.2.2.4 Acknowledgements indicating progress of call
`
`After receiving ACKE(QUAL=0) or AHY(POINT=1,E=1) for its emergency
`standard data call,
`the waiting calling unit shall take appropriate action
`on receiving further acknowledgements —ACKI(QUAL=1), ACKQ, ACKX, ACKV or
`ACKT(QUAL=0) - as detailed in section 17.l.2.1.4.
`
`Until it receives ACKE(QUAL=0) or AHY(POINT=1,E=l),
`ignore other acknowledgements.
`
`the unit shall
`
`If it receives ACKE(QUAL=O) for the call then the unit shall wait for
`further signalling.
`
`17.1.2.2.5 Availability check and channel command for own call
`
`A calling radio unit attempting access or waiting for further call
`set—up signalling for an emergency standard data call shall obey the
`availability check procedures (see 9.2.2.2 to 9.2.2.4, 17.1.2.3.l and
`17.1.2.3.2, or 17.1.2.4.2 to 17.l.2.4.4).
`
`The unit shall also obey the channel allocation procedures (see
`9.2.2.5 and 17.1.2.3.4 or l7.l.2.4.6). Note particularly that:
`
`i)
`
`On a control channel:
`
`a.
`
`h.
`
`If the unit has not received ACKE(QUAL=O) or AHY(POINT=1,E=1)
`for its emergency call, it shall ignore all GTT and GTC
`messages.
`
`After receiving ACKE(QUAL=D) or AHY(POINT=1,E=l) for its
`emergency call,
`the unit shall obey a GTT or GTC message only
`if it is individually addressed by the GTT or GTC.
`
`
`
`Page 17-28
`Petitioner Cisco Systems - Exhibit 1005 - Page 246
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 246
`
`

`
`ii)
`
`on a data channel:
`
`If the unit has not received ACKE(QUaL=0) or AHY(POIN'l‘=1,E=l) for its
`emergency call, it shall ignore individually addressed GTT messages
`with bit 0/?! set to '1'.
`
`See rule 1 of sections 9.2.2.5 and 1'I.l.2.3.4, or section l7.l.2.4.6b.
`
`After receiving AcKE(QUnL=O) or AH'f(POIN'1‘=l,E=1) for a short
`addressing call or after sending the full addres information for an
`extended addressing call, the unit shall assume that a GT1‘ message it
`receives is for its requested call if PFIX/IDENT is its individual address,
`bit 0/}! is set to '1', RATE is acceptable and, for a GT1‘ on a data channel,
`CHAN is set to the number of that data channel.
`If also TRANS >
`
`then the unit shall regard the call link as established and
`‘000O000000'
`may give an indication to the service user.
`
`17.1.2.2.6 Time-out after waiting
`
`A calling radio unit waiting for further call set-up signalling on the
`channel on which it attempted access for an emergency standard data call
`shall return to the previous state if a time TW/TDW has elapsed since the
`last message it sent for the call, viz.
`
`RQD(E=1), requesting the emergency call (see 1'I.1.2.2.1)
`SAMIS, providing extended address information for the call
`or
`or ACK(QUAL=0) , sent in response to an AH! message with POINT = 1, E = 1
`and IDENTI as the called ident or gateway. It may also indicate the failure
`to the service user.
`
`l7.1.2.2.7 other procedures
`
`a.
`
`A calling radio unit waiting for an emergency standard data call may
`attempt to cancel the call by sending a call cancellation request
`RQX.
`The procedures are as defined in 1':‘.l.2.1.8 for cancelling
`non—emergency data cal ls .
`
`b.
`
`The procedures on the data channel are as defined in 17.2.
`
`17.1.2.3
`
`Related Procedures for All Radio Units on a
`Control Channel
`
`These procedures shall be obeyed by all radio units that are equipped
`to send or receive standard data.
`
`A radio unit attempting access or waiting for further signalling for a
`call may he sent a data availability check message AHYD or Go To
`Transaction message GTT for an incoming call
`(see l7.1.2.3.lA and
`l7.l.2.3.4). Note that:
`
`i) The unit can reject an incoming individual standard data call by
`sending ACKV(QUAL=1)
`in response to the Al-IYD message.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 247
`
`Page 17-29
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 247
`
`

`
`ii) A radio unit is required to obey individually addressed GTT messages
`and system—wide calls (except
`in emergency),
`though it may ignore group
`call GTTs. However,
`if making a call of its own,
`the unit is required to
`ignore GTT messages for incoming group calls; see 17.l.2.3.4. This rule
`applies also to a unit that has received an AHY or AHYD message for an
`incoming individual traffic channel or data call and responded with
`ACE (QUAL=0) or ACKI (QUA.L=0) .
`
`iii} If a unit receives and obeys a GTT message not for its own call, it
`returns to its previous state at the end of the incoming call. unless the
`time—out (e.g. TW or TDW) on the previous state has expired.
`
`17.l.2.3.1 Data availabilit
`called radio unit
`
`rate check on individuall
`
`If a radio unit on a control channel receives an AHYD message with
`PFIX/IDENT1 matching its individual address then it shall respond with the
`appropriate acknowledgement (see below), with the same prefix and idents as
`the AHYD.
`If bit AD = O in the AHYD message,
`the unit shall respond in the
`slot following the AHYD address codeword; if bit AD = 1, a data codeword is
`appended (containing the calling address) and the unit shall respond in the
`slot following the data codeword.
`For timing. see 6.2.1.3.
`
`A}
`
`Incoming standard data call :
`
`IDENT2 not equal to DUMMYI
`
`The unit shall send one of the following acknowledgements:
`
`if it is not equipped to accept standard data calls at
`ACKX (QUAL=0)
`least from this calling party.
`
`ACKX (QUAL=l) if it cannot accept this standard data call at this
`time (e.g. its data store is full or interaction
`has been requested
`but is not
`immediately possible).
`
`ACKV (QUAL=1) if it does not support one or more of the requested
`facilities, i.e. does not support HADT or interaction or cannot
`accept the wanted PORT.
`
`in the AHYD message but the appended data
`if AB = l
`ACKB (QUAL=l)
`codeword was not decodeable and the unit requires the message to be
`retransmitted.
`
`if it is available for a standard data call of this
`(QUAL=O)
`ACK
`in this case,
`the unit shall set bit MODEM to indicate whether
`type;
`it is able to operate at the customised transmission rate; see
`5.5.2.2.
`
`The unit may indicate to its user the caller (by reference to
`PFIX/IDENT2 from the AHYD message or PFIX2/IDENT2 from the data codeword)
`and whether interaction is required, and whether the incoming call
`is an
`emergency call
`(by reference to bit E from the AHYD).
`
`there is no option
`Note that, unlike RHY for traffic channel calls,
`for the radio unit to respond to AHYD with an intermediate acknowledgement
`ACKI(QUAL=0),
`followed by use of a called party answer mechanism;
`the unit
`must either accept or reject the data call.
`(If the data equipment is not
`ready immediately,
`the radio unit could receive and buffer the first data
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 248
`
`Page 17-30
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 248
`
`

`
`transmiss:Lon(s) , and then introduce a pause using the Flow Control
`mechanisms on the data channel.)
`
`After receiving an AI-{YD message for an incoming individual standard
`data call and responding with ACl<(QUAL-=0),
`the unit shall ignore:
`
`-
`
`group call GTC messages as specified in section 9.2.2.5
`
`rule 2 or
`
`3.
`
`4.
`
`-
`
`group call GTT messages as specified in section 17.l.2.3.4 rule 2 or
`
`unti 1 either:
`
`a.
`
`(i.e. a GTT
`it receives a channel command for the incoming data call
`message with PFIX/IDENT as its individual address, bit O/R set to '0‘
`and an acceptable RATE),
`or
`
`b.
`
`it assumes that the call will not take place; see l7.l.2.3.2.
`
`If, while waiting for an incoming individual standard data call, a
`radio unit receives a repeat AHYD then it shall send the appropriate
`acknowledgement;
`also,
`for ACK(QUAL=0), it
`shall
`restart its timer
`TA/TDA (see l7.l.2.3.2).
`
`(having sent
`If, while waiting for an incoming traffic channel call
`ACK(QUAL=0) or ACKI(QUAL=O)
`in response to an AH! message), a radio unit
`receives an AHYD for an incoming individual standard data call,
`the unit
`shall abandon the old call and obey the AHYD; also.
`if currently attempting
`an "off-hook" or "on-hook" RQQ transaction for the original call, it shall
`abandon the RQQ transaction - see 13.1.2.
`
`3)
`
`"No-call" test availability check :
`
`IDENT2 = DUMKYI
`
`The unit may indicate that it is not suitably equipped by sending
`ACKX(QUAL=D). Otherwise it shall send ACK(QUAL=D).
`
`ACKX (QUP.L=0)
`
`- The unit could not at any time accept a standard
`data call with all the specified facilities.
`
`ACK
`
`(QUAL=0)
`
`- Unit is in radio contact and is suitably equipped
`to support the particular parameter settings in the
`AHYD. Bit MODEM indicates whether it is able to
`
`operate at the customised transmission rate.
`
`17.1.2.3.2 Cancelling waiting state of individually called
`radio unit
`
`A radio unit that has received an AHYD message for an incoming
`individual standard data call {see 1'I.1.2.3.1A), and responded with
`ACK(QUi\L=O), shall assume that the call will not take place if one of the
`following occurs:
`
`a.
`
`It has not received a GTT message for the call at a time TA/TDA after
`the last ACK(QUAL=0) it sent in response to an AI-IYD for the call.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 249
`
`Page 17-31
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 249
`
`

`
`
`
`
`
`b.
`
`c.
`
`d.
`
`It receives an AHYX message with the same prefix and idents as the
`AHYD.
`(The unit shall respond in the next slot with ACK(QUAL=1). as
`required by section 9.2.2.4.)
`
`It receives an AHYD message checking its availability for a different
`incoming individual standard data call (i.e. bit E and/or the calling
`address and/or the PORT is different from the original AHYD).
`
`It receives an AHY message checking its availability for an incoming
`traffic channel call.
`
`The unit may indicate to the service user that the expected data call
`will not take place.
`In cases a. and b.,
`the unit shall note that:
`
`—
`
`-
`
`rule 2 or 3 of section 9.2.2.5,
`
`and
`
`rule 2 or 4 of section 17.1.2.3.4
`
`(requiring the unit to ignore GTC/GTT messages for incoming group calls) no
`longer apply.
`In case c.,
`the unit shall obey the procedures in l7.1.2.3.1A
`for the new call.
`In case d.,
`the unit shall obey the procedures in
`9.2.2.23 for the new call.
`
`l7.l.2.3.3 Receiving AHYD message addressed to a group or
`ALLI
`
`If a radio unit on a control channel receives an AHYD message with
`
`PFIX/IDENT1 matching any of its group addresses for this system or
`
`IDENTl set to the system-wide all-call ident ALLI
`
`then it may accept the call information contained in the AHYD codeword, but
`shall transmit no response.
`The unit may then assume that the next
`GTT(0/R=0) message for this respective group or ALLI address received on
`this channel within the following time TA/TDA corresponds to the:
`
`i)
`
`calling address
`(PFIX/IDENT2 or PFIXZ/IDENT2 from an appended data codeword)
`
`ii)
`
`E bit
`
`iii) pour
`
`announced by the AHYD message.
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 250
`
`Page 17-32
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 250
`
`

`
`If the unit has not received a G'I‘T(0/R=O) message at a time TA/TDA
`after the last received AHYD for the call, or if it receives an M-{YD
`message for different call to this address,
`then it may assume that the
`expected call will not take place.
`
`17.1.2.3.4 Data channel assignment
`
`A radio unit on a control channel shall check all GTT messages it
`receives to see whether the message is addressed to it, that is, whether:
`
`PFIX/IDENT from the GTT message matches its individual address or
`
`PFIX/IDENT matches any of its group addresses for this system or
`
`IDENT is the ystem-wide all-call ident ALLI.
`
`If the GTT message is addressed to it, and it is able to receive
`standard data at the transmission rate specified by field RATE,
`the unit
`shall use the appropriate rule below to decide whether to obey the command:
`
`1.
`
`If the unit is making an emergency call (RQE or RQD(E=l)) and has not
`received ACKE(QUAL=0) or AHY(I:‘.=1) for its call, it shall ignore the
`GTT message.
`
`If the unit is waiting for further signalling for its emergency call,
`after receiving ACKE(QUAL=O) or M-1Y(E=1) for the call, it shall obey
`the GTT message if and only if it is individually addressed by the
`GTT (i.e. its individual address is PFIX/IDENT).
`
`2.
`
`otherwise:
`
`If the unit is waiting for an incoming individual emergency call (see
`9.2.2.2}; and 17.1.2.3.lA), it shall obey the GTT message if and only
`if it is individually addressed by the GTI‘.
`
`3.
`
`Otherwise:
`
`If the unit is attempting access or waiting for further signalling
`for a non-emergency call or transaction, it shall obey the GTT
`message if and only if:
`
`it is individually addressed by the GTT,
`
`or
`
`IDENT is set to ALLI and the unit knows that it is not the
`
`calling unit (i.e. it is not making a system—wide standard data
`call or has received an AHYD message indicating another caller
`— see l7.l.2.3.3).
`
`4.
`
`Otherwise:
`
`If the unit is waiting for an incoming non—emergency individual
`traffic channel or data call
`(see 9.2.2.213 and l'J.l.2.3.lA), it shall
`obey the GTT message if and only if:
`
`it is individually addressed by the GTT,
`
`or
`
`(unless the unit has received an AHYD
`[DENT is set to ALLI
`message indicating that it was the calling party in the call).
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 251
`
`Page 17-33
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 251
`
`

`
`5.
`
`Otherwise (i.e. if not waiting for any call or transaction):
`
`The unit shall obey the GTT message, unless:
`
`IDENT is set to ALLI and the unit has received an AHYD message
`indicating that it was the calling party in the call
`
`or
`
`PFIX/IDENT is one of the unit's group addresses and the unit
`cannot or does not wish to accept this call, for example:
`
`-
`
`—
`
`—
`
`-
`
`the service user does not wish to receive group calls, or
`
`the unit has received an AHYD message for this group
`address indicating that it was the calling party in the
`call, or
`
`the unit has received an AHYD message for this group
`address indicating an unacceptable calling party or PORT,
`or
`
`the unit has not received an AHYD message for this group
`address and it needs the AHYD information for reliable
`
`some calls to this address are of normal
`operation (e.g.
`accuracy whilst others employ HADT).
`
`If the unit is required to obey the GTT command, it shall perform the
`following actions:
`
`a.
`
`The unit shall tune to the designated forward channel and shall be
`able to receive on the data channel within 35 ms after the end of the
`
`GTT message.
`
`It shall be prepared to receive signalling at the transmission rate
`specified by field RATE in the GTT message.
`
`b.
`
`If bit 0/R from the GTT message is set to '1', the unit shall note
`that it is the calling party. Otherwise it is a called party.
`
`Note that, if the unit is a called party and is waiting for an
`incoming standard data call for this address (see l7.1.2.3.l and
`17.l.2.3.3),
`then it may take the PORT and the calling address (if
`fully supplied)
`from the AHYD message-
`
`c.
`
`The unit shall note PFIX,
`
`IDENT and TRANS from the GTT message.
`
`i)
`
`ii)
`
`the unit shall expect to receive
`For TRANS > 'O00OOO0COD‘,
`signalling on the data channel for this transaction number.
`
`the unit shall expect to receive a
`For TRANS = 'OOOO0OO0OO‘,
`further GTT message on the data channel to assign a transaction
`number for the link.
`The unit shall assume that the next GTT
`
`message, containing this address, bit 0/R and bit RATE, and
`with CHAN equal
`to the number of the data channel, received
`within the following time TDG, corresponds to this call - see
`l7.1.2.4.6a.
`
`
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 252
`
`Page 17-34
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 252
`
`

`
`
`
`If a calling unit has not received the expected G'r‘1‘(O/R=l)
`message on the data channel at a time TDG after the control
`channel GTT,
`then it shall return to the idle state on the
`control channel and may indicate the call failure to the
`service user.
`
`If a called unit has not received the expected GTT(0/R=0)
`message on the data channel at a time TDG after the control
`channel GTT, or if it receives an individually addressed A!-{ID
`message for a different call to this address,
`then it shall
`assume that the expected call will not be received and may give
`an indication to the service user.
`
`d.
`
`The unit shall note the channel number of the control channel.
`
`It may also give an indication of the event to the service user.
`
`If the unit does not obey a GTT message, and the designated data channel is
`the control channel on which the message was received,
`then the unit shall
`enter the control channel acquisition procedures.
`
`17.1.2.4
`
`Related Procedures for All Radio Units on a Data
`Channel
`
`These procedures shall be obeyed Py all radio units which are equipped
`to request or receive calls on a data channel.
`(other procedures for radio
`units on a data channel are included in sections 17.2.)
`
`17 . l . 2 . 4 . 1
`
`Instruction to send extended address information
`
`This procedure shall be obeyed by all radio units that are equipped to
`request extended addressing standard data calls.
`
`If a radio unit on a data channel receives an M-PIC message with
`PFIX/IDENT2 matching its individual address then it shall either send
`address information or transmit ACKx(QUAL=O), as indicated below. For
`
`timing on a 1200 bit/s data channel, see section_6.2.l.3.
`
`If the unit has sent an extended addressing RQD(E=O) request, or has
`received ACKE or A1-lY(E=l) for an extended addressing RQD(E=l)
`
`and
`
`IDENTl matches IDENTI
`
`from the request
`
`and DESC
`
`is appropriate to IDEN'l‘l (see S.S.3.2.8)
`
`and
`
`SLOTS
`
`corresponds to the request
`
`{i.e.
`
`if IDENTI = PSTNGI and unit's call requires > 9 PSTN digits
`SLOTS = '10‘
`
`then
`
`if IDENT1 = PSTNGI and unit's call requires < 10 PSTN digits
`then SLOTS = '01‘ or
`'10‘
`
`.“-
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 253
`
`Page 17-35
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 253
`
`

`
`
`
`
`
`if IDENTl is not equal to PSTNGI
`
`then SLOTS = '01‘)
`
`then it shall transmit the full called address information,
`conforming to the codeword formats defined in section 5.6.1.2.2
`(SAHIS, Mode 1).
`
`Otherwise
`
`the unit shall transmit ACKX(QUAL=0), with the same prefix and idents
`as the AHYC.
`
`17.l.2.4.2 Data availabilitggrate check on individually
`called radio unit
`
`If a radio unit on a data channel receives an AHYD message with
`PFIX/IDENTI matching its individual address then it shall respond with the
`appropriate acknowledgement (see below), with the same prefix and idents as
`the AHYD.
`If bit AD = 0 in the BHYD message,
`the unit shall respond in the
`slot following the AHYD address codeword; if bit AB = 1, a data codeword is
`appended (containing the calling address) and the unit shall respond in the
`slot following the data codeword. For timing on a 1200 bit/s data channel,
`see 6.2.1.3.
`
`A)
`
`Incoming standard data call :
`
`IDENT2 not equal to DUMMYI
`
`The unit shall send one of the following acknowledgements:
`
`if it is not equipped to accept standard data calls
`ACKX (QUAL=O)
`from this calling party.
`
`if it cannot accept this standard data call at this
`ACKX (QUAL=l)
`time (e.g. it cannot process concurrent calls or its data store is
`full or interaction has been requested but is not
`immediately
`possible).
`
`if it does not support one or more of the requested
`ACKV (QUAL=1)
`facilities, i.e. does not support HADT or interaction or cannot
`accept the wanted PORT.
`
`in the AHYD message but the appended data
`if AD = l
`ACKB (QUAL=l)
`codeword was not decodeable and the unit requires the message to be
`retransmitted.
`
`if it is available for a standard data call of this
`(QUAL=O)
`ACK
`i.e. it can support
`the particular parameter settings of the
`type;
`In this case,
`the unit shall set bit MODEM to the value
`AHYD.
`appropriate for that channel; see 5.5.2.2.
`
`The unit may indicate to its user the caller (by reference to
`PFIX/IDENT2 from the AHYD message or PFIx2/IDENT2 from the data codeword)
`and whether interaction is required, and whether the incoming call
`is an
`emergency call
`(by reference to bit E from the AHYD).
`
`After receiving an AHYD message for an incoming individual standard data
`call and responding with ACK(QUAL=O),
`the unit shall wait for a GTT message
`for the call (i.e. a GTT message with PFIX/IDENT as its individual address,
`
`Petitioner Cisco Systems - Exhibit 1005 - Page 254
`
`Page