SIS bit no.
`
`1
`
`2-3
`
`4-12
`
`13-15
`
`h
`
`Network operator identity
`
`1
`'00’ National network no.
`'01‘ National network no. 2
`’ 10’ Reserved
`‘ 1 1' Reserved
`
`Network dependent data
`(see below)
`
`Label for multiple control channels
`(see 9.5.3)
`
`NDD-
`
`LAB-
`
`Frmtfthn ork ntta
`
`The network operator is free to utilise the network dependent data sub-field in any way which
`conforms to the following general structure and requirements:
`
`Bit no.
`
`9
`
`12 SYS bit no.
`
`1 = '0'
`
`
`
` —
`
`
`
`ERERERRER NDD -
`
`bit no.
`
`4
`
`ZONE
`
`AREA
`
`FREE
`
`-
`
`-
`
`-
`
`12 SYS bit no.
`
`1
`
`:1:
`
`A sub-field with length set by the network operator, starting at bit 9
`(SYS bit no.
`1 = '0') or bit 4 (SYS bit no. 1 = '1‘) which indicates
`the subscription zone to which the system identity code belongs.
`
`A sub~field with length set by the network operator, starting at bit 9
`(SYS bit no.
`1 = '0') or bit 4 (SYS bit no.
`1 = '1') which indicates
`the registration area to which the system identity code belongs.
`
`A sub-field with length set by the network operator ending at bit 12 of
`the SYS field which may be used for any control channel identification
`purpose which the network operator specifies.
`i
`
`9—29
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 107
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 107
`
`

`
`
`
`SIL
`
`PREFERRED
`
`NDD
`
`-
`
`-
`
`A sub—field with length set by the network operator (minimum 3),
`starting at bit 9 (SYS bit no.
`1 = '0’) or hit 4 (SYS bit no.
`1 = ‘l‘)
`which indicates the sub-field to be used when checking the source of
`MAINT or CLEAR messages
`(see 1l.9.2.3.3, 11.9.2.3.7 and_
`1l.9.2.3.8).
`
`A sub—field with length set by the network operator starting at bit 9
`(SYS bit no. 1 = '0') or bit 4 (SYS bit no.
`I = '1’) which indicates
`the sub-field of the network dependent data which is to be preferred
`during hunting.
`
`.
`
`Zero bits is a valid length of any sub-field, in which case that sub-field has no relevance to
`acquisition authorisation or hunting procedures.
`
`9.3.4.2.3
`
`Amuisitign AuthQri§a_ttion Data and NDD Prefereng Data
`
`The radio unit shall provide facilities for acquisition authorisation data to be implanted during
`network personalisation to enable the radio unit to carry out the verification process specified
`in 9.3.42.1 for each possible selected network (see 9.2). This acquisition authorisation data
`shall consist of the following information for each possible selected network:
`
`-
`
`-
`
`the length of the ZONE sub-field (LZ),
`
`the length of the AREA sub-field (LA).
`
`In addition, the acquisition authorisation storage shall provide for any combination of the
`following three classes of acquisition data for at least eight total entries:
`
`—
`
`-
`
`-
`
`to L2, which authorises
`zone identity: a binary number of length equal
`acquisition of control channels conveying system identity codes bearing that
`zone value;
`
`to LA, which authorises
`area identity: a binary number of length equal
`acquisition of control channels conveying system identity codes bearing that .
`area value;
`
`1 = '0’) or 9 bits ’
`full identity: a binary number of length 4 bits (SYS bit no.
`(SYS bit no.
`I = *1‘) which authorises acquisition of control channels
`conveying the single identity code in the network which bears that value in
`bits 9 to 12 (SYS bit no.
`1 = ’0’) or bits 4 to 12 (SYS bit no. 1 = ‘l’).
`
`Each zone, area or full identity entry in memory shall include an identifier to distinguish the
`three classes of data (the form to be taken by this identifier is not specified).
`
`The radio unit may provide facilities for NDD preference data to be implanted during
`network personalisation to enable the radio unit to carry out the verification process specified
`
`9-30
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 108
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 108
`
`

`
`
`
`in 9.3.4.2.? for each possible selected network (see 9.2). This NDD preference data shall
`consist of the following information for each possible selected network:
`
`-
`
`—
`
`-
`
`At least four values of PREFERRED NDD sub-field. each value referred to
`as a preferred NDD sub-set, which identify preferred system identity codes
`as ones bearing these values in the PREFERRED NDD sub-field.
`
`For each preferred NDD sub-set a number from 0-9 indicating the length of
`the PREFERRED NDD sub—field in bits to which the value refers.
`
`For each preferred NDD sub-set, a number from 1 to 10, inclusive, indicating
`the order of priority (I is highest priority, 10 lowest) in a ‘preferential NDD
`sub-set hunt stage“, "preferential sampled hunt stage" or ‘background search
`sequence". The same priority may apply to more than one preferred NDD
`sub—set.
`
`93.4-2.4
`
`fA i "
`
`A
`
`The radio unit shall apply the following procedures when checking a system identity code
`selected for verification against its acquisition authorisation data for the selected network.
`
`
`
`
`
`
`
`1 of the selected SYS is ‘l‘, the mobile shall check that the selected network is a
`If bit
`national network and that a match exists between the NET field in the selected SYS and that
`authorised for the selected network.
`
`1 of the received SYS is '0', the mobile shall check that the selected network is a
`if bit
`regional network and that a match exists between the OPID field in the selected SYS and that
`authorised for the selected network.
`
`
`
`~
`
`-
`
`If the radio unit holds no data for zone, area or full identity acquisition
`authorisation for the selected network,
`then it may
`acquire any control
`channel belonging to that network.
`
`If the radio holds data for zone, area or full identity acquisition authorisation
`for the selected network,
`then the following precedence shall apply:
`
`
`
`
`
`
`
`
`
`
`
`
`The radio unit shall first check for a match between any zone identity
`(a)
`acquisition authorisation data and the selected system identity code.
`If a
`match is found then acquisition is authorised.
`
`Failing acquisition authorisation at the zone identity level, the radio
`(b)
`unit shall check for a match between any area identity acquisition authorisation
`data and the selected system identity code.
`If a match is
`found then
`acquisition is authorised.
`
`Failing acquisition authorisation at the zone or area identity level, the
`(c)
`radio unit shall check for a match between any full
`identity acquisition
`authorisation data and the selected system identity code.
`If a match is found
`
`9-31
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 109
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 109
`
`

`
`then acquisition is authorised.
`
`If acquisition authorisation testing fails at all three levels, then the radio unit shall assume
`that it is not authorised to acquire the control channel under test.
`
`9.3.4.2.5
`
`Checking the LAB Sub-field
`
`If the radio unit has successfully verified the system identity code against its acquisition -
`authorisation data for the selected network it shall examine the LAB sub-field in the light of
`its control category held in read-only memory (see 9.2).
`
`If the control category of the radio unit is not one of the categories permitted access by the
`LAB sub-field value (see 9.5.3), then the radio unit shall assume that it is not authorised to
`acquire the control channel under test.
`
`9.3.42.6
`
`Qhgking the AREA §ub—fi§ld
`
`If the radio unit has successfully verified the system identity code against its acquisition
`authorisation data for the selected network and has verified that it is permitted to acquire by
`the value of the LAB field,
`then it shall examine the AREA sub-field in the light of
`currently-valid records of successful and denied registrations applicable to the selected
`network held in its read/write memory (see 9.2).
`
`If the value of the AREA sub-field under examination is a value held in a currently-valid
`record of denied registrations applicable to the selected network,
`then a radio unit shall
`assume that it is not authorised to acquire the control channel under test.
`
`In addition, if the control channel confirmation is being carried out during a "preferential
`area hunt stage“ and if the value of the AREA sub~field under examination is not held in a
`currently-valid successful registration record for the selected network in the radio unit's
`read/write memory, then the radio unit shall assume that it is not authorised to acquire the
`control channel under test.
`
`9.3.4.2.?
`
`Chgking the PREFERRED NDD Sub-field
`
`If control channel confinnation is being carried out during a "preferential NDD sub-set hunt .
`stage", or, where specified, during a "preferential sampled hunt stage" (see 9.3.3.3.2), the
`radio unit shall examine the PREFERRED NDD sub-field of the system identity code being
`verified against the NDD preference data for the selected network held in the radio units ’
`read-only memory. If no match can be found between any item of NDD preference data and
`the selected system identity code then the radio unit shall assume that it is not authorised to
`acquire the control channel under test on this basis.
`
`9.3.4.3
`
`Err r
`
`h
`
`kin
`
`n C ntr l
`
`hannel
`
`Whilst receiving a control channel a radio unit shall monitor the codeword error rate and
`count the codewords received with errors (after the application of any error corrections
`procedures which may be adopted) in successive samples of NC] or NC2 codewords (values
`
`9-32
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 110
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 110
`
`

`
`
`
`
`
`are network dependent). Samples of length NC1 codewords shall be taken when monitoring
`the channel for the purpose of final checking prior to confirmation (9.3.4.4) and of length
`NC2 after confirmation.
`
`In this context a "codeword" shall be considered as the contents of the first or second half
`
`.~‘.~=s:s:.=:i:=i
`..,.s_ ——
`
`of a slot on the fonvard control channel (see !!3.3.3.l!!) irrespective of the contents of that
`slot. Any codeword which is not decodable shall be regarded as a codeword with errors.
`
`The radio unit shall also count as codewords with errors all codewords received between the
`
`first control channel system codeword with a value of SYS field different to that selected for
`verification and the first control channel system codeword with the value of SYS field the
`same as that selected for verification. including the initial control channel system codeword
`with the different value of SYS field.
`
`If, in any sample of NC1 codewords, the count of codewords received with errors exceeds
`NXI (network dependent), or in any sample of NC2 codewords, the count of codewords
`received with errors exceeds NX2 (network dependent), then a codeword sample error event
`shall be recorded by the radio unit. The radio unit shall hold two alternative values of
`NC1/NXI and NC2/NX2 as follows:
`
`-.-::<-r;:»"»‘.--
`
`-
`
`—
`
`-
`
`-
`
`one set of values of NC1 and NX1 shall be utilised when monitoring a channel
`for the purpose of final checking prior to confinnation when the channel
`number is identified as one on which time-shared control channels may be
`expected in the store of channel numbers held in the radio unit's read-only
`memory as applicable to a "nonnal hunting sequence“ (see 9.2.1) or in the
`store of data received from BCAST messages held in readlwrite memory (see
`9.2.2) or in the TS! field of a received MOVE or CLEAR message;
`
`the other set of values of NC1 and NXI shall be utilised when monitoring a
`channel for the purpose of final checking prior to confirmation when the
`channel number is not identified in the data stores or fields specified above as
`one on which time-shared control channels may be expected;
`
`one set of values of NC2 and NX2 shall be utilised when monitoring a channel
`after confirmation when the channel number is identified as one on which
`
`time-shared control channels may be expected in the store of channel numbers
`held in the radio unit's read-only memory as applicable to a "normal hunting
`sequence" (see 9.2.1) or in the store of data received from BCAST messages
`held in readfwrite memory (see 9.2.2), or in the TSI field of a received
`MOVE or CLEAR message;
`
`the other set of values of NC2 and NX2 shall be utilised when monitoring a
`channel after confirmation when the channel number is not identified in the
`
`data stores or fields specified above as one on which time-shared control
`channels may be expected.
`
`Whilst waiting for signalling on a control channel (eg, after transmitting a random access
`message) a radio unit shall suspend the count of codewords received with errors. Any count
`
`9-33
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 111
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 111
`
`

`
`
`
`
`
`in progress at the time that a radio unit enters this waiting state shall be aborted and the
`result discarded.
`
`When a radio unit leaves the control channel as a result of the circumstances specified in
`9.4.1 parts (b), (c), (d), (t), (g), or (m), or (b) when due to a demanded registration, it shall
`resume error checking. When it acquires and verifies a new charmel it shall confirm the ‘
`channel (9.3.4.4) and shall then suspend error checking until it is no longer waiting for
`signalling.
`
`9.3.4.4
`
`Final Qhmking Prior to A3;
`
`If a control channel, which satisfies the procedures of 9.3.4.1 and 9.3.4.2, was sampled
`during a hunt at a level less than L.2., then it shall not be finally confirmed until the error
`checking procedure specified in 9.3.4.3 has produced Nzl samples of NCI codewords.
`Further if any of the N21 samples of NC] codewords has produced a codeword sample error
`event then the radio unit shall reject the channel and resume hunting.
`
`When a sampled control channel has passed all the appropriate tests in 9.3.4.1, 9.3.4.2 and
`9.3.4.3 then the radio unit shall regard the current hunting sequence as complete and shall
`consider the control channel as confirmed.
`
`9.4
`
`vin
`
`ontrol
`
`1
`
`9.4.1
`
`R
`
`vi,
`
`lhnl
`
`i Ntw"
`
`frinlin
`
`Whilst active on a control channel, either prior to acquisition being confirmed or during
`activity subsequent to control channel confirmation, the radio unit shall monitor conditions
`on that channel and be prepared to leave the control channel and return to the control channel
`hunting procedures. This monitoring shall continue when the radio unit is waiting for
`signalling from the TSC, but the circumstances which result in the radio unit leaving the
`control channel are reduced and are prescribed in 9.4.2 below.
`
`When not in the state of waiting for signalling from the TSC the radio unit shall leave the
`current control channel and enter the control channel hunting stage prescribed when:
`
`After confirmation, a codeword sample error event has been recorded in a _
`(a)
`sample of NC2 codewords (see 9.3.4.3) and codeword sample error events are
`recorded in each of N22 further successive samples of NC2 codewords.
`In this case
`the radio unit shall enter the "preferential hunt sequence“.
`
`The value of bits I to 12 of the SYS recovered from decodable control channel
`(b)
`system codewords received differs from the value of the bits verified during
`acquisition authorisation (see 93.4.2.1) for a continuous period TS and the next
`decodable control channel system codeword received after the expiry of TS also
`yields a value of SYS different to the verified value (see !!6.2.1.2!!). The radio unit
`shall remain active on the channel after the first mismatch but shall not transmit any
`random access message until a valid SYS value has been received, in which case it
`may resume normal operation (see !!6.2.1.2!!). After leaving a control channel in
`
`9-34
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 112
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 112
`
`

`
`
`
`I
`i
`!
`1
`
`
`these circumstances, the radio unit shall enter the "preferential hunt sequence" , unless
`it is prior to confirmation when it shall resume hunting procedures.
`
`system codewords are received over a
`No decodable control channel
`(c)
`continuous period in excess of TS (see l!6.2.l.2!!).
`In this case the radio unit shall
`enter the "preferential hunt sequence". unless it is prior to confirmation when it shall
`resume hunting procedures.
`
`in the case of radio units which are equipped to employ the
`An Aloha or,
`(d)
`MARK message, a MARK message is received in which the value of CHAN4 does
`not match the least significant four bits of the channel number of the control channel
`and there is also no match in the next decodable Aloha or MARK message. The
`radio unit shall remain active on the channel after the first mismatch but shall not
`
`transmit any random access message and shall leave the channel immediately after the
`second mismatch, unless a valid Cl-IAN4 value has been received in the interim in
`
`which case it may resume normal operation (see ll6.2. l.2!!). After leaving a control
`channel
`in these circumstances the radio unit shall enter the "preferential hunt
`sequence“, unless it is prior to confirmation when it shall resume hunting procedures.
`
`In this case the radio unit
`The user initiates a change of selected network.
`(:2)
`shall assume control channel acquisition procedures on the new selected network with
`the "single channel hunt sequence“, the "preferential hunt sequence”, or the “normal
`hunt sequence" depending on what valid information of previous activity on the new
`selected network is held in the radio unit's read/write memory.
`
`In
`A MOVE message applicable to the radio unit is received (see !l7.4.2.!!).
`(D
`this case the radio unit shall note the value of the TS] field and enter either the
`"single channel hunt sequence" or the “preferential hunt sequence" depending on the
`value of the CONT field in the MOVE message, unless it is prior to confirmation
`when it shall resume hunting procedures.
`
`A control channel system codeword is received in which the value of the LAB
`(g)
`sub-field in the system identity code indicates that the control category of the radio
`unit for the selected network is not permitted access on the current control channel
`and the LAB value in the next decodable control channel system codeword also
`indicates that the radio units control category is not acceptable. The radio unit shall
`remain active on the channel after the first failure but shall not uansmit any random
`access message and shall
`leave the channel
`immediately after the second failure,
`unless a value of LAB sub-field is received in the interim which does permit access
`by the unit, in which case it may resume normal operation (see 9.5.3). After leaving
`a control channel in these circumstances the radio unit shall enter the "preferential
`hunt sequence", unless it
`is prior to confirmation when it shall resume hunting
`procedures.
`
`The radio unit receives ACKX(QUAL='0‘) as a result of sending a random
`(h)
`access registration (RQR) message (see !!8.2.2.3l!), or as a response to an RQR sent
`in reply to a registration demand by the TSC (see !l8.3.2.2!!).
`In the caseof a
`random access registration request
`(not permitted prior to confirmation) or a
`
`9-35
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 113
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 113
`
`

`
` registration demand received whilst the radio unit is seeking to make a random access
`
`registration request, the radio unit shall assume the hunt stage that it was last engaged
`in prior to the registration attempt. It may either resume the hunt stage at the channel
`number it would have sampled next or commence the hunt stage anew.
`In the case
`where a registration demand was received at any other time, the radio unit shall enter
`the "preferential hunt stage", unless it is prior to confirmation when it shall resume
`hunting procedures.
`
`After confirmation, the radio unit receives ACKX(QUAL='1’) as a result of
`(j)
`sending a random access registration request (RQR) message (see !!8.2.2.3!!). In this
`case the radio unit shall assume the hunt stage that it was last engaged in prior to the
`registration attempt.
`It may either resume the hunt stage at the channel number it
`would have sampled next or commence the hunt stage anew.
`
`the radio unit has timed out after a random access
`After confirmation,
`(it)
`registration (RQR) attempt due to NR being reached or TC being exceeded (see
`!!7.3.8!!).
`In this case if the registration attempt is being carried out prior to a
`successful re-registration being achieved on a newly-confirmed control channel the
`radio unit shall assume the hunt stage that
`it was last engaged in prior to the
`registration attempt.
`It may either resume the hunt stage at the channel number it
`would have sampled next or commence the hunt stage anew.
`If the registration
`attempt
`is being carried out at any other
`time the radio unit shall enter the
`"preferential hunt sequence”.
`
`When the radio unit receives an ALI-IF message or equivalent (see 13.6) and
`(1)
`the radio unit is not in the fall—back mode (see 13.3).
`In this case the radio unit shall
`enter the "preferential hunt sequence". If the radio unit is equipped with the fall-back
`option it shall obey the procedures of section 13.
`
`(in) When the radio unit receives a GTC message which it has not obeyed in which
`the designated traffic channel
`is the control channel on which the message was
`received and the radio unit is not in the fallback mode (see !!9.2.2.5!!).
`In this case
`the radio unit shall enter the "preferential hunt sequence".
`
`In addition to these mandatory conditions a radio unit may leave the cunent control channel
`and enter the control acquisition procedures when:
`
`After confirmation, the radio unit receives ACI(X(QUAL=‘l') as a result of
`(n)
`sending a random access request message. except RQR.
`If the radio unit leaves the
`control channel as a result of exercising this option it shall enter the "preferential hunt
`sequence".
`
`After confirmation, the radio unit has timed-out after a random access attempt,
`(p)
`except RQR, due to NR or NE being reached or TC being exceeded (see !!7.3.8!!).
`If the radio unit leaves the control channel as a result of exercising this option it shall
`enter the "preferential hunt sequence".
`
`(q)
`
`After confirmation,
`
`the radio unit has identified one or more prospective
`
`9-36
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 114
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 114
`
`

`
`
`
`‘?“*F?‘3‘§=“?§
`
`control channels as a result of carrying out a "background search. sequence" (see
`9.3.3.7). If the radio leaves the control channel as a result of exercising this option
`it shall enter the “preferential hunt sequence".
`
`In addition a radio unit may leave the current control channel, temporarily, when:
`
`In this case the
`It has received a BCAST (SYSDEF ='00l0l’) message.
`(r)
`radio unit shall switch to the return channel indicated by the CHAN field in the
`message and shall return to the confirmed control channel in sufficient time to be able
`to decode any address codeword which may be transmitted in the forward direction
`in the second slot following the slot containing the BCAST (SYSDEF =‘00l0l‘)
`message.
`
`In the course of implementing a “background search sequence" it initiates a
`(s)
`sampling activity in accordance with the requirements of section 9.3.3.7.
`
`9.4.2
`
`vin
`
`ntrol
`
`hannel Whilst Waitin
`
`f r
`
`i nallin
`
`A radio unit waiting for signalling shall leave the control channel on which it is currently
`active when any of the following events as listed in 9.4.1 above occur:
`(b), (c), (d), (f), (g).
`(h) due to a demanded registration, and (m).
`In such circumstances the radio unit shall retain
`its state of waiting for signalling during any hunting procedures and subsequent control
`channel confirmation tests. Any timers relevant to the waiting state shall be maintained.
`
`1‘
`
`In addition, a radio unit which times-out on the expiry of timer TJ whilst waiting for
`signalling relevant to the transmission of an RQR message shall:
`
`
`
`
`
`re-
`is being carried out prior to a successful
`If the registration attempt
`i.
`registration being achieved on a newly-confirmed control channel, assume the hunt
`stage that it was last engaged in prior to the registration attempt.
`it may either
`resume the hunt stage at
`the channel number it would have sampled next or
`commence the hunt stage anew.
`
`*
`
`
`
`
`
`
`
`ii.
`
`If the registration attempt is being carried out at any other time, enter the
`
`"preferential hunt sequence".
` A radio unit which enters the control channel acquisition procedures whilst in the waiting
`
`
`
`
`
`-
`
`.
`
`1
`
`state shall obey the hunting procedures specified in 9.3.3 and the control channel
`confirmation procedures specified in 9.3.4.
`In addition, whilst in the waiting state, the radio
`unit shall only confirm a control channel in which the value of bits 1-12 of the system
`identity code (SYS) being examined under the procedure specified in 9.3.4.2 matches bits
`1-12 of the system identity code which was examined to authorise acquisition of the control
`channel on which the radio unit was last confirmed. A radio unit which, having entered the
`control channel acquisition procedure whilst in the waiting state. times out on any of the
`timers TA, TC, T1 or TW as appropriate to its condition, shall continue to search for a
`control channel but shall resume the control channel acquisition procedures, but without the
`application of the additional SYS code check specified above.
`
`
`
`
`
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 115
`
`9-37
`
`
`
`
`
`
`
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 115
`
`

`
`
`
`A radio unit waiting for signalling which leaves the control channel on which it is currently
`active due to events (e) or (1) listed in the foregoing 9.4.1 shall cancel its waiting for
`signalling state upon entering the control channel acquisition prmdures.
`
`It should be noted that events (a), (h) for a random access registration request, (1), (k), (n),
`(p), (q), (r) and (s) are not applicable to a radio unit in the state of waiting for signalling.
`
`_
`
`9.5
`
`Mul‘ l
`
`I
`
`it
`
`til
`
`9.5 . l
`
`Ingmfiugtign
`
`Commercial networks in Band III sub-bands l and 2 may operate with multiple control
`channels at a single site and may require the subdivision of the radio unit population to allow
`load sharing between control channels. This facility is provided by the LAB sub-field in the
`system identity code (see 9.5.3) and by control categorisation of radio units (see 9.5.2).
`
`9.5.2
`
`ntrol
`
`ri
`
`'n f
`
`i
`
`ni
`
`At the time of network personalisation the radio unit shall be allocated a control category
`(CCAT) and this category shall be stored in the radio unit's read-only memory. Four control
`categories are available, which are designated A, B, C and D for convenience.
`
`The control category governs acquisition and retention of a control channel, since the LAB
`sub—fie1d in the system identity code indicates which radio unit control categories are allowed
`to use a control channel (see 9.3.4.3 and 9.4).
`
`9.5.3
`
`The LAB Sgt;-field
`
`The LAB sub-field occupies bits 13 to 15 of the system identity code (see 9.3.4.22). The
`meanings assigned to the eight possible values of LAB shall be:
`
`‘O00’
`‘O01’
`‘010’
`'01 1'
`' 100'
`‘l0l‘
`‘I10’
`'1 1 l‘
`
`Reserved (future definition in MP1‘ 1343)
`All categories permitted
`Categories A and B only pemiitted
`Categories C and D only permitted
`Category A only permitted
`Category B only permitted
`Category C only permitted
`Category D only permitted
`
`9-38
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 116
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 116
`
`

`
`
`
`10
`
`10.1
`
`REGISTRATION
`
`Qenegl
`
`10.1.1
`
`lntrqiimtion
`
`.
`
`Registration is a method of recording the area or group of areas where a radio unit is likely
`to be located within a network. This information avoids searching for radio units throughout
`the whole network, consequently reducing call set-up time and control channel loading.
`
`A secondary feature is that it provides a means of restricting the service of individual radio
`units by allowing the network to deny registration requests.
`
`It is
`The registration strategy enables networks to operate single or multiple registration.
`mandatory for radio units to support single registration, and multiple registration is a
`standard option. On networks which employ multiple registration. single registration radio
`units may make more registration requests than multiple registration radio units. Since the
`single registration radio unit is registered in only one area however,
`it is likely that fewer
`AHOY messages from the network would be required to locate it. Registration strategy is
`determined by the network and may be broadcast to radio units to allow them to take
`appropriate actions.
`
`‘
`
`The registration strategy describes two types of registration. The first of these is explicit
`registration, where registration is achieved by means of an RQR message (either random
`- access or demanded). The second is implicit registration, appropriate to multiple registration
`type radio units, where registration is achieved by means of messages exchanged during call
`set-up. Only messages that terminate control channel signalling are used for implicit
`registration.
`
`_N _
`
`g
`
`_
`
`i
`
`-
`
`It is possible that due to a failure the network may not be able to maintain registrations. but
`will want radio units to use the network as if they are registered. The network may
`broadcast a message to indicate that a temporary registration mode is in operation. Radio
`units which receive this message will recognise the temporary registration mode, and may
`be required to re- register on receipt of a further broadcast message indicating that the
`network is in a normal registration mode.
`
`10.2
`
`ginglg Registration
`
`10.2.]
`
`P
`
`re
`
`The single registration procedure specified in this section enables a network to record the
`likely area in which a radio unit is located.
`
`10.2.1.1
`
`The Principle
`
`The principle of registration requires that the radio unit shall only retain a valid registration
`record where it has received confirmation that it is the same record as that currently. held
`within the network.
`If there is any doubt that the record is correct, then a NULL indicator
`
`I0-1
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 117
`
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 117
`
`

`
`must be written against the record. If a radio unit fails to receive a response to a registration
`request, this could be due to:
`
`-
`
`—
`
`-
`
`the request not being received by the network, in which case the network will
`regard the previous successful registration by the unit as the current1y—valid _
`registration record‘,
`
`the request being accepted by the network but the acknowledgement not being
`received by the radio unit,
`in which case the network will regard the
`unsuccessful registration by the unit as the currently-valid registration record;
`
`'
`
`the request being denied or failed by the network but the acknowledgement not
`being received by the radio unit, in which case the network may either regard
`the previous successful
`registration by the unit as
`the currently-valid
`registration record or record a NULL registration for the calling unit.
`
`Accordingly, in such cases the radio unit is not able to confirm whether the network holds
`a valid record for the unit and if it does, whether it is the previous registration or the present
`registration.
`It shall
`therefore, when making a registration attempt, write the registration
`record into its memory at the time of making the registration attempt but, at the same time,
`write a NULL indicator against the record. When the successful registration is confirmed by
`a suitable acknowledgement from the system the radio unit shall
`then cancel
`the NULL
`indicator.
`
`10.2.2
`
`Storage and Timing rgiuirements
`
`10.2.2.1
`
`Requirements
`
`In order to follow the procedures specified in this section the radio unit shall provide the
`following storage requirements appropriate to the selected network:
`
`a)
`
`In Type ‘B’ read/write memory lg; fltion 6.2):
`
`The registration record applicable to the selected network. The registration record shall
`include the value of the verified AREA code and may include the channel number of the
`control channel on which that explicit or implicit registration attempt was carried out. The
`registration record shall also include a flag to indicate whether the registration record is
`normal or temporary. Until the radio unit is switched off, or equivalent, the flag shall also
`be capable of indicating an undefined state prior to being set.
`
`The radio unit shall discard any data held in protected read/write memory unless its validity
`is reasonably assured. Also it should be noted that the values described in 10.2.2. 1(a) may
`be held in unprotected RAM while operational and transferred to protected RAM on switch
`off or equivalent.
`
`The registration records used by a single registration radio unit are indicated in Table 6.1 as
`"Prime registration" records.
`*
`
`10~2
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 118
`
`Petitioner Cisco Systems - Exhibit 1006 - Page 118
`
`

`
`
`
`b)
`
`I
`
`' mem
`
`At l