2section (Continued) 6 Layer 3 Processing
Download 3.74 Mb.
|
- Navigate this page:
- 2.6.4.1.6 Long Code Transition Request Processing
- 2.6.4.1.7 Power Up Function (PUF)
- 2.6.4.1.7.1 Processing the Power Up Function Message
2.6.4.1.5 Message Action TimesA Forward Traffic Channel message without a USE_TIME field or with a USE_TIME field set to ‘0’ has an implicit action time. A message that has its USE_TIME field set to ‘1’ has an explicit action time that is specified in the ACTION_TIME field of the message. A message with an explicit action time is called a pending message. Unless otherwise specified, a message having an implicit action time shall take effect no later than the first 80 ms boundary (relative to System Time plus FRAME_OFFSETs 1.25 ms) occurring at least 80 ms after the end of the frame containing the last bit of the message. A message with an explicit action time, except for a Power Up Function Message, shall take effect when System Time minus FRAME_OFFSETs 1.25 ms (in 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME field. A Power Up Function Message shall take effect ACTION_TIME_FRAME frames after the time when System Time minus FRAME_OFFSETs 1.25 ms (in 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME field. The difference in time between ACTION_TIME and the end of the frame containing the last bit of the message shall be at least 80 ms. The mobile station shall support two pending messages at any given time, not including pending Service Option Control Orders or Service Option Control Messages. The number of pending Service Option Control Orders or Service Option Control Messages that the mobile station is required to support is specific to the service option (see the relevant service option description). In addition, the mobile station shall support one pending Power Up Function Message. 2.6.4.1.6 Long Code Transition Request ProcessingThe mobile station performs these procedures upon receiving a Long Code Transition Request Order. If the Long Code Transition Request Order requests a transition to the private long code, and the mobile station is able to generate the private long code (see 2.3.12.3), and the mobile station accepts the request, the mobile station shall send a Long Code Transition Response Order (ORDQ = ‘00000011’) within T56m seconds. The mobile station shall use the private long code on both the Forward Traffic Channel and the Reverse Traffic Channel. The mobile station shall store the public long code mask and PLCM_TYPEs currently in use and begin using the private long code at the explicit action time (see 2.6.4.1.5) specified in the message. At the action time of the message, the mobile station should indicate to the user that the voice privacy mode is active. If the Long Code Transition Request Order requests a private long code transition, and the mobile station is not able to generate the private long code or the mobile station does not accept the request, the mobile station shall send a Long Code Transition Response Order (ORDQ = ‘00000010’) within T56m seconds. If the Long Code Transition Request Order requests a transition to the public long code and the mobile station accepts the request, the mobile station shall send a Long Code Transition Response Order (ORDQ = ‘00000010’) within T56m seconds. The mobile station shall use the public long code on both the Forward Traffic Channel and the Reverse Traffic Channel. The mobile station shall begin using the public long code that is stored previously, derived from PLCM_TYPEs as specified in 2.3.6, at the explicit action time (see 2.6.4.1.5) specified in the message. At the action time of the message, the mobile station should indicate to the user that the voice privacy mode is inactive. If the Long Code Transition Request Order requests a public long code transition, and the mobile station does not accept the request, the mobile station shall send a Long Code Transition Response Order (ORDQ = ‘00000011’) within T56m seconds.
A PUF probe is one or more consecutive Traffic Channel frames. A PUF probe consists of three parts: PUF setup, PUF pulse, and PUF recovery. PUF_SETUP_SIZE is the duration of the PUF setup part, in power control groups. PUF_PULSE_SIZE is the duration of the PUF pulse, in power control groups. The PUF recovery period occupies the remainder of the last frame of the PUF probe. A PUF attempt is a sequence of PUF probes sent by the mobile station in response to a Power Up Function Message. A PUF attempt begins at an offset frame boundary within 80 ms of the ACTION_TIME specified in the Power Up Function Message. A PUF attempt can be terminated in one of four ways: • The mobile station receives a Power Up Function Completion Message. • The mobile station has transmitted the maximum number of PUF probes specified in the Power Up Function Message. • The mobile station has transmitted the maximum number of probes allowed at its maximum output power. • The mobile station receives a new Power Up Function Message.
• PUF_FREQ_INCLr is set to ‘1’ and PUF_BAND_CLASSr is not supported by the mobile station. • PUF_FREQ_INCLr is set to ‘1’ and the mobile station is unable to re-tune to the PUF Target Frequency during (PUF_SETUP_SIZEr + 1) power control groups. • MOB_P_REVp is not equal to five and the mobile station does not support the Power Up Function. The mobile station shall send a Mobile Station Reject Order with the ORDQ field set to ‘00001100’ (invalid Frequency Assignment), if the Frequency Assignment specified in the message is the same as the Serving Frequency (PUF_FREQ_INCLr is equal to ‘1’, PUF_BAND_CLASSr is equal to CDMABANDs and PUF_CDMA_FREQr is equal to CDMACHs). If the mobile station is processing a PUF probe, the mobile station shall wait for the PUF probe to complete. It shall then terminate the current PUF attempt. The mobile station shall store the following parameters: • Maximum number of PUF probes transmitted at full power level (MAX_PWR_PUFs = MAX_PWR_PUFr + 1) • Total number of PUF probes (TOTAL_PUF_PROBESs = TOTAL_PUF_PROBESr + 1) • PUF interval (PUF_INTERVALs = PUF_INTERVALr) • Number of PUF setup power control groups (PUF_SETUP_SIZEs = PUF_SETUP_SIZEr + 1) • Number of PUF pulse power control groups (PUF_PULSE_SIZEs = PUF_PULSE_SIZEr +1) • Power increase of initial PUF pulse (PUF_INIT_PWRs = PUF_INIT_PWRr) • Power increase for each successive PUF pulse (PUF_PWR_STEPs = PUF_PWR_STEPr) • Frequency included indicator (PUF_FREQ_INCLs = PUF_FREQ_INCLr) If PUF_FREQ_INCLs equals ‘1’, the mobile station shall store the following: • PUF probe Target Frequency CDMA Channel number (PUF_TF_CDMACHs = PUF_CDMA_FREQr) • PUF probe Target Frequency CDMA band class (PUF_TF_CDMABANDs = PUF_BAND_CLASSr) The mobile station shall set CURRENT_PUF_PROBEs equal to 0. The mobile station shall then begin the PUF attempt at the time specified in 2.6.4.1.7.2.
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:
|
