Common Procedures for Processing r-csch Messages

2.6.14 Common Procedures for Processing r-csch Messages

2.6.14.1 Reporting Band Class – Band Subclass Capabilities

• 
  In the procedures below, the following assumptions apply:
  

– If the mobile station supports a candidate band class but it is not aware of any band subclass definition for that band class, the mobile station shall report its capabilities as if it supports band subclass 0 of that band class.

• 
  If the mobile station supports at least one band class and band subclass (if applicable) combination queried by the base station, the mobile station shall set BAND_SUB_REP_INCL to '1'; otherwise, the mobile station shall set this field to ‘0’ and shall not perform the remaining procedures.
  
• 
  The mobile station shall initialize NUM_BAND_SUBCLASS to ‘0000’.
  
• 
  If the mobile station supports all candidate band class and band subclass (if applicable) combinations queried by the base station, the mobile station shall not perform the remaining procedures; otherwise, for i = 1 to NUM_CAND_BAND_CLASS_s, the mobile station shall perform the following:
  

+ The mobile station shall include one instance of the BAND_SUBCLASS_SUP field and set it as follows. If the mobile station supports the candidate band class CAND_BAND_CLASS_REC[i].CAND_BAND_CLASS, the mobile station shall set this field to '1'; otherwise, it shall set it to '0'.

+ The mobile station shall increment NUM_BAND_SUBCLASS by 1.

– Otherwise, for j = 0 to CAND_BAND_CLASS_REC[i].SUBCLASS_REC_LEN, if CAND_BAND_CLASS_REC[i].BAND_SUBCLASS_IND_REC[j] is equal to '1', the mobile station shall perform the following:

+ The mobile station shall include one instance of the BAND_SUBCLASS_SUP field and set it as follows. If the mobile station supports the band subclass CAND_BAND_CLASS_REC[i].BAND_SUBCLASS_IND_REC[j], the mobile station shall set this field to '1'; otherwise, it shall set it to '0'.

+ The mobile station shall increment NUM_BAND_SUBCLASS by 1.

Figure 2.6.14.1-1 illustrates the relationship between the base station CAND_BAND_CLASS, BAND_SUBCLASS_IND fields and the mobile station BAND_SUBCLASS_SUP fields for one possible scenario.



Figure 2.6.14.1-1. Illustration of Band Class - Band Subclass Reporting

2.6.15 MEID procedures when communicating with P_REV 6, 7, 8, 10 Base Stations

2.6.16 Initialization of RC parameters

• The mobile station shall set FOR_FCH_ACK_MASK_RL_BLANKING_s to ‘0001 1001 1001 1000’ and set FOR_FCH_ACK_MASK_NO_RL_BLANKING_s to ‘0000 1010 1010 1010’.

• The mobile station shall set REV_FCH_ACK_MASK_s to ‘0000 1010 1010 1010’.

• The mobile station shall set FOR_SCH_ACK_MASK_RL_BLANKING_s to ‘0000 0000 0001 1000’ and set FOR_SCH_ACK_MASK_NO_RL_BLANKING_s to ‘0000 0000 0010 1000’.

• The mobile station shall set REV_SCH_ACK_MASK_s to ‘0000 0000 0010 1010’.

• The mobile station shall set FOR_N2M_IND_s to ‘001’ (4 bad frames).

• The mobile station shall set RPC_MODE_s to ‘00’ (200 to 400 bps).

• The mobile station shall set PWR_CNTL_STEP_ZERO_RATE_s to ‘000’ (1 dB).

• The mobile station shall set FOR_FCH_BLANKING_DUTYCYCLE_s to ‘001’ (N=4).

• The mobile station shall set REV_FCH_BLANKING_DUTYCYCLE_s to ‘001’ (N=4).

• The mobile station shall set _FCH_BLANKING_DUTYCYCLE_IN_USE to ‘001’ (N=4).

• The mobile station shall set REV_ACKCH_GAIN_ADJ_ACS1_s to ‘0000 000’.

• The mobile station shall set REV_ACKCH_GAIN_ADJ_ACS2PLUS_s to ‘0000 000’.

• The mobile station shall initialize RC_PARAMS_RECORD_s to have entry RC_PARAMS_RECORD_s[i] for each of the PILOT_PNs assigned to mobile and initialize corresponding fields of each of the RC_PARAMS_RECORD_s[i] record as follows:

• 
  Set RC_PARAMS_RECORD_s[i].QOF_SET_IN_USE set to ‘000’.
  
• 
  Set RC_PARAMS_RECORD_s[i].REV_SCH_ACK_CH_WALSH[00] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i].REV_SCH_ACK_BIT[00] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i].REV_SCH_ACK_CH_WALSH[01] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i].REV_SCH_ACK_BIT[01] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i].FOR_FCH_CCSH_INTERLEAVER_TYPE to ‘0’.
  

2.6.17 RC_PARAMS_RECORD update procedures

The mobile station shall update RC_PARAMS_RECORD in Traffic Channel Substate as follows:

• When a pilot is added to the active set for which there is no entry present in RC_PARAMS_RECORD_s, the mobile station shall update RC_PARAMS_RECORD_s to add an entry RC_PARAMS_RECORD_s[i] and perform the following:

• 
  Set RC_PARAMS_RECORD_s[i].PILOT_PN to the PILOT_PN of the added pilot.
  
• 
  Set RC_PARAMS_RECORD_s[i].QOF_SET_IN_USE to ‘000’.
  
• 
  Set RC_PARAMS_RECORD_s[i].REV_SCH_ACK_CH_WALSH[00] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i]. REV_SCH_ACK_BIT[00] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i]. REV_SCH_ACK_CH_WALSH[01] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i]. REV_SCH_ACK_BIT[01] to NULL.
  
• 
  Set RC_PARAMS_RECORD_s[i]. FOR_FCH_CCSH_INTERLEAVER_TYPE to ‘0’.
  

• When a pilot is removed from the active set for which there was an entry present in RC_PARAMS_RECORD_s, the mobile station shall update RC_PARAMS_RECORD_s to remove the entry.

• When an Radio Configuration Parameters Message is received, the mobile station shall update RC_PARAMS_RECORD_s as described in section 2.6.4.3.

2.6.18 Processing of General Extension Message

The base station may extend layer 3 messages with additional fields using the General Extension Message. The mobile station shall process this message at the action time:

• Explicitly specified in the message carried in the MESSAGE_REC field, or

• At the action time explicitly specified in the general extension record when the message carried in the MESSAGE_REC field does not carry action time explicitly, or

• implicity specified by the message carried in the MESSAGE_REC field when action time is not carried explicitly in the general extension record or the message carried in the MESSAGE_REC field

The mobile station shall process this message as follows:

• The mobile station shall store the ith occurrence of the GE_REC_TYPE_r in GE_REC_TYPE_s[i].

• The mobile station shall store the ith occurrence of the GE_REC_LEN_r in GE_REC_LEN_s[i].

• If any General Extension Record type is not supported, the mobile station shall send a Mobile Station Reject Order with ORDQ equal to 00011101.

• If any field value in any of the General Extension Records is outside its permissible range, the mobile station shall send a Mobile Station Reject Order with ORDQ equal to 00011110.

• If any field value in any of the General Extension Records is not supported, the mobile station shall send a Mobile Station Reject Order with ORDQ equal to 00011111.

• The mobile station shall store the ith occurrence of the GE_REC_r as follows.

• If GE_REC_TYPE_s[i] is equal to ‘00000000’ the mobile station shall store the BAND_CLASS_r field in the GE_REC_r as BAND_CLASS_s and REV_CHAN_r field in the GE_REC_r as REV_CHAN_s. The mobile station shall use the REV_CHAN_s channel number of BAND_CLASS_s as the associated reverse link for the channel carried in the message carried by the MESSAGE_REC field.

• If GE_REC_TYPE_s[i] is equal to ‘00000001’ the mobile station shall store and use the fields included in the Radio Configuration Parameters Record at the action time. If the USE_TIME field in the Radio Configuration Parameters Record is set to ‘0’, the mobile station shall process the message contained in the MESSAGE_REC and then update the RC_PARAMS_RECORDs by the values of the fields included in the Radio Configuration Parameters Record.

• The mobile station shall use the MESSAGE_TYPE field as specified in [4] and process the reception of layer 3 message carried in the MESSAGE_REC field.

1 Packet data service option refers to SO 60, SO 61 or any service option in Service Option Group 4 and 5 in [30]

2 REG_SECURITY_RESYNC was formerly called REG_ENCRYPT_RESYNC.

3 When SIGN_SLOT_CYCLE_INDEX is equal to ‘1’, the minimum length slot cycle consists of 16 slots of 80 ms each, hence 1.28 seconds. When SIGN_SLOT_CYCLE_INDEX is equal to ‘0’, the minimum length slot cycle consists of one slot of 80 ms, hence 80 ms. When operating in the reduced slot cycle mode, the minimum length slot cycle is also 80 ms.

4 Format of broadcast address for BCMC is defined in BCMC service document (see [30]).

5 One exception is if the mobile station is operating in the reduced slot cycle mode with a reduced slot cycle index of -3 or -4, and IGNORE_QPCH_s is equal to ‘1’.

6 A case for which the mobile station may not be able to detect that at least one of the paging indicators is set to “OFF” is for a mobile station that misses a part of or its entire Quick Paging Channel slot during overhead information update. In this case, the mobile station monitors its assigned Paging Channel slot.

7 The mobile station will not discard frequencies as long as they belong to a subclass that is both listed in the message and supported by the mobile station. If the base station does not list any subclass, the mobile station assumes that all subclasses are supported by the base station. The subclass to frequency mapping is not provided in the Extended CDMA Channel List Message; the mobile station needs to refer to [45] to find the mapping.

8 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

9 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

10 The mobile station will not discard frequencies as long as they belong to a subclass that is both listed in the message and supported by the mobile station. If the base station does not list any subclass, the mobile station assumes that all subclasses are supported by the base station. The subclass to frequency mapping is not provided in the Extended CDMA Channel List Message; the mobile station needs to refer to [45] to find the mapping.

11 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

12 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

13 The mobile station will not discard frequencies as long as they belong to a subclass that is both listed in the message and supported by the mobile station. If the base station does not list any subclass, the mobile station assumes that all subclasses are supported by the base station. The subclass to frequency mapping is not provided in the Extended CDMA Channel List Message; the mobile station needs to refer to [45] to find the mapping.

14 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

15 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

16 The mobile station will not discard frequencies as long as they belong to a subclass that is both listed in the message and supported by the mobile station. If the base station does not list any subclass, the mobile station assumes that all subclasses are supported by the base station. The subclass to frequency mapping is not provided in the Extended CDMA Channel List Message; the mobile station needs to refer to [45] to find the mapping.

17 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

18 This is primarily needed when hashing to a band with a different coverage footprint than the current band. The current neighbor list is to be used to search for pilots in the hashed-to band. The search priorities are to be adjusted to take into account the hashed-to frequency (e.g., the pilots in the hashed-to frequency should have the highest priority).

19 The mobile station processes the message as defined in section 2.6.3.3, but no requirements other than the Extended Channel Assignment Message processing requirements in section 2.6.3.3 are applicable.

20 Insufficiency of the Paging Channel and the Forward Common Control Channel is implementor-defined.

21 Insufficiency of the Paging Channel and the Forward Common Control Channel is implementor-defined.

22 The mobile station would be waiting for a response to the message transmitted in the access probe.

23 Insufficiency of the Paging Channel and the Forward Common Control Channel is implementor-defined.

24 The mobile station would be waiting for a response to the message transmitted in the access probe.

25 Requirements for processing the loss of Paging Channel are given separately for each substate of the System Access State, in the sections describing the substates.

26 A message is considered sent when the mobile station transmits the message at least once, no matter whether the L2 acknowledgment is received or not.

27 The current state may be Page Response Substate or Mobile Station Idle State. The mobile station remains in the state in which Extended Channel Assignment Message is received.

28 Periodic reporting and threshold reporting may be independently enabled or disabled by the base station.

29 Note that these procedures that take place at the action time may not occur for this message if a GHDM/UHDM with SCR_INCLUDED equal to ‘1’ is received before the action time of this message. In this case, these procedures take place for the new message. One exception is that the call assignments from this message take effect at the action time of this message regardless of the call assignments from the new message.

30 The stored service configuration is considered used when it is stored for the first time or when it is used again during a call using the SYNC_ID feature.

31 Packet data origination refers to origination with SO 60, SO 61 or any service option in Service Option Group 4 and 5 in [30]

32 For example, if the mobile station uses a 2.56 second slot cycle, then it may increment the counter by 32 every time it becomes active.

33 BASE_LAT and BASE_LONG are given in units of 1/4 seconds. BASE_LAT/14400 and BASE_LONG/14400 are in units of degrees.

34 ^ The mobile station need not maintain a separate identifier for Band Class 0, as the least significant bit of the SID identifies the serving system.

35 The indicator REG_ENABLED does not govern parameter-change registration.

36 For example, suppose a mobile station has the following SID, NID list: (2, 3), (2, 0), (3, 1). If the base station (SID, NID) pair is (2, 3), then the mobile station is not roaming because the (SID, NID) pair is in the list. If the base station (SID, NID) pair is (2, 7), then the mobile station is a foreign NID roamer, because the SID 2 is in the list, but the (SID, NID) pair (2, 7) is not in the list. If the base station (SID, NID) pair is (4, 0), then the mobile station is a foreign SID roamer, because SID 4 is not in the list.

37 The mobile station may send a Handoff Supplementary Information Notification message to the base station if a message that mobile station is sending includes a Pilot for which the base station may require supplementary information. For example, the mobile station may send this message along with PSMM or EPSMM message.

38 The table defines the entire search range. For example, SRCH_WIN_A_s = 6 corresponds to a 28 PN chip search window or 14 PN chips around the search window center.

39 If the mobile station searches the entire Candidate Frequency Search Set in a single visit to the Candidate Frequency, TOTAL_OFF_TIME_FWD will be equal to MAX_OFF_TIME_FWD, and TOTAL_OFF_TIME_REV will be equal to MAX_OFF_TIME_REV.

40 The CLEAR_RETRY_DELAY field received in General Handoff Direction Message does not affect the RETRY_DELAY_s[RETRY_TYPE] values.

41 This formula is adapted from Knuth, Donald N., The Art of Computer Programming, 2 volumes, (Reading, MA, Addison-Wesley, 1998).

42 This generator has full period, ranging over all integers from 1 to m-1; the values 0 and m are never produced. Several suitable implementations can be found in Park, Stephen K. and Miller, Keith W., “Random Number Generators: Good Ones are Hard to Find,” Communica­tions of the ACM, vol. 31, no. 10, October 1988, pp. 1192-1201.

43 If the mobile station is in the Mobile Station Origination Attempt Substate, the NEW_SSEQ_H field shall be the one included in the Origination Message. If the mobile station is in the Page Response Substate, the NEW_SSEQ_H field shall be the one included in the Page Response Message.

44 The mobile station should select a different value of NEW_SSEQ_H every time NEW_SSEQ_H is included in a message. This is to prevent the re-use of the same 24 most significant bits of the 32-bit crypto-sync.

45 Although the primitive is modeled to allow the Upper Layer to request for a single BCMC_FLOW_ID at a time, this procedure can be implemented such that multiple BCMC_FLOW_IDs can be requested simultaneously.

Directory: TSGC -> Working
Working -> 2. section (Continued) 6 Call Layer 3 Processing
Working -> 3gpp2 tsg-c wg 2 swg 3 meeting #40 Meeting Summary
Working -> C14-20050516-007 3gpp2 swg 4 title
Working -> Radiocommunication Study Groups

Download 3.74 Mb.

Share with your friends: