2section (Continued) 6 Layer 3 Processing
Download 3.74 Mb.
|
2.6.4.1.2.2 Service SubfunctionsAs illustrated in Figure 2.6.4.1.2.2-1, the mobile station supports service configuration and negotiation by performing the following set of service subfunctions: • Normal Service Subfunction - While this subfunction is active, the mobile station processes service configuration requests from the user and from the base station. • Waiting for Service Request Message Subfunction - While this subfunction is active, the mobile station waits to receive a Service Request Message. • Waiting for Service Response Message Subfunction - While this subfunction is active, the mobile station waits to receive a Service Response Message. • Waiting for Service Connect Message Subfunction - While this subfunction is active, the mobile station waits to receive a Service Connect Message, a General Handoff Direction Message, or a Universal Handoff Direction Message containing a service configuration record. • Waiting for Service Action Time Subfunction - While this subfunction is active, the mobile station waits for the action time associated with a new service configuration and then sends a Service Connect Completion Message, a Handoff Completion Message, or an Extended Handoff Completion Message. • SO Negotiation Subfunction - While this subfunction is active, the mobile station supports service option negotiation with the base station. This subfunction is only used while operating in Band Class 0. The SO Negotiation Subfunction supports service option negotiation. All of the other service subfunctions support service negotiation. At any given time during Traffic Channel operation, only one of the service subfunctions is active. For example, when the mobile station first enters the Traffic Channel Initialization Substate of the Mobile Station Control on the Traffic Channel State, the Normal Service Subfunction, the Waiting for Service Connect Message Subfunction or the SO Negotiation Subfunction is active. Each of the other service subfunctions may become active in response to various events which occur during the Traffic Channel substates. Typically, the mobile station processes events pertaining to service configuration and negotiation in accordance with the requirements for the active service subfunction, however, some Traffic Channel substates do not allow for the processing of certain events pertaining to service configuration and negotiation, or specify requirements for processing such events which supersede the requirements of the active service subfunction.
2.6.4.1.2.2.1 Normal Service Subfunction While this subfunction is active, the mobile station processes service configuration requests from the user and from the base station. While the Normal Service Subfunction is active, the mobile station shall perform the following: • The mobile station shall process Forward and Reverse Traffic Channel frames in accordance with the current service configuration. The mobile station shall discard any Forward Traffic Channel frame which has a format that is not supported by the mobile station. The mobile station may discard any type of Forward Traffic Channel traffic that is not signaling traffic and is not part of the current service configuration. • To initiate service negotiation for a new service configuration, the mobile station shall send a Service Request Message to propose the new service configuration. The mobile station shall activate the Waiting for Service Response Message Subfunction. • For any service option connection that is part of the current service configuration, the mobile station may send a Service Option Control Message to invoke a service option specific function in accordance with the requirements for the associated service option. • If SERV_NEGs changes from enabled to disabled (see 2.6.6.2.5.1), the mobile station shall activate the SO Negotiation Subfunction. • If the mobile station receives one of the following service negotiation messages, the mobile station shall process the message according to the specified requirements: 1. Service Connect Message: The mobile station shall perform the following: • If USE_OLD_SERV_CONFIGr equals ‘01’ or ‘10’, and if the mobile station entered the Mobile Station Control on the Traffic Channel State due to receiving an Extended Channel Assignment Message with GRANTED_MODE set to ‘11’, the mobile station shall send a Mobile Station Reject Order with the ORDQ field set to ‘00010100’ (stored configuration already restored at channel assignment) within T56m seconds and shall not perform the rest of the procedures below. • If USE_OLD_SERV_CONFIGr equals ‘00’, the mobile station shall perform the following: If the mobile station accepts the service configuration specified in the message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds. • If USE_OLD_SERV_CONFIGr equals ‘01’, the mobile station shall perform the following: If the mobile station accepts the service configuration currently stored at the mobile station, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds. • If USE_OLD_SERV_CONFIGr equals ‘10’, the mobile station shall perform the following: If the mobile station accepts the service configuration resulting from updating the stored service configuration with the service configuration received in this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds. • If USE_OLD_SERV_CONFIGr equals ‘11’, the mobile station shall perform the following: if the mobile station accepts the service configuration resulting from restoring the indicated service option connection records from the stored service configuration and releasing the indicated service option connection records from the current service configuration, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds. 2. Service Option Control Message: If the service option connection specified by the message is part of the current service configuration, and the service option specified by the message is the same as the service option associated with the service option connection, the mobile station shall interpret the action time of the message as specified in 2.6.4.1.5, and shall process the message in accordance with the requirements for the service option; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds. 3. Service Request Message: The mobile station shall process the message as follows: – If the purpose of the message is to reject a proposed service configuration, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds. – If the purpose of the message is to propose a service configuration, the mobile station shall process the message as follows: + If the mobile station accepts the proposed service configuration, the mobile station shall send a Service Response Message to accept the proposed service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Connect Message Subfunction. + If the mobile station does not accept the proposed service configuration and does not have an alternative service configuration to propose, the mobile station shall send a Service Response Message to reject the proposed service configuration within T59m seconds. + If the mobile station does not accept the proposed service configuration and has an alternative service configuration to propose, the mobile station shall send a Service Response Message to propose the alternative service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Request Message Subfunction. 4. Service Response Message: The mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds. 5. General Handoff Direction Message: If the SCR_INCLUDED field is included in this message and is set to ‘1’: If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction. 6. Universal Handoff Direction Message: If the SCR_INCLUDED field is included in this message and is set to ‘1’: If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction. • If the mobile station receives one of the following service option negotiation messages, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds: 1. Service Option Request Order 2. Service Option Response Order 3. Service Option Control Order 2.6.4.1.2.2.2 Waiting for Service Request Message Subfunction While this subfunction is active, the mobile station waits to receive a Service Request Message. Upon activation of the Waiting for Service Request Message Subfunction, the mobile station shall set the subfunction timer for T68m seconds. While the Waiting for Service Request Message Subfunction is active, the mobile station shall perform the following: • If the subfunction timer expires, the mobile station shall activate the Normal Service Subfunction. • The mobile station shall process Forward and Reverse Traffic Channel frames in accordance with the current service configuration. The mobile station shall discard any Forward Traffic Channel frame which has a format that is not supported by the mobile station. The mobile station may discard any type of Forward Traffic Channel traffic that is not signaling traffic and is not part of the current service configuration. • The mobile station shall not initiate service negotiation for a new service configuration. • For any service option connection that is part of the current service configuration, the mobile station may send a Service Option Control Message to invoke a service option specific function in accordance with the requirements for the associated service option. • If SERV_NEGs changes from enabled to disabled (see 2.6.6.2.5.1), the mobile station shall activate the SO Negotiation Subfunction. • If the mobile station receives one of the following service negotiation messages, the mobile station shall process the message according to the specified requirements: 1. Service Connect Message: The mobile station shall perform the following: • If USE_OLD_SERV_CONFIGr equals ‘01’ or ‘10’, and if the mobile station entered the Mobile Station Control on the Traffic Channel State due to receiving an Extended Channel Assignment Message with GRANTED_MODE set to ‘11’, the mobile station shall send a Mobile Station Reject Order with the ORDQ field set to ‘00010100’ (stored configuration already restored at channel assignment) within T56m seconds, and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘00’, the mobile station shall perform the following: If the mobile station accepts the service configuration specified in the message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘01’, the mobile station shall perform the following: If the mobile station accepts the service configuration currently stored at the mobile station, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘10’, the mobile station shall perform the following: If the mobile station accepts the service configuration resulting from updating the stored service configuration with the service configuration received in this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘11’, the mobile station shall perform the following: if the mobile station accepts the service configuration resulting from restoring the indicated service option connection records from the stored service configuration and releasing the indicated service option connection records from the current service configuration, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. 2. Service Option Control Message: If the service option connection specified by the message is part of the current service configuration, and the service option specified by the message is the same as the service option associated with the service option connection, the mobile station shall interpret the action time of the message as specified in 2.6.4.1.5, and shall process the message in accordance with the requirements for the service option; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds. 3. Service Request Message: The mobile station shall process the message as follows:
+ If the mobile station accepts the proposed service configuration, the mobile station shall send a Service Response Message to accept the proposed service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Connect Message Subfunction. + If the mobile station does not accept the proposed service configuration and does not have an alternative service configuration to propose, the mobile station shall send a Service Response Message to reject the proposed service configuration within T59m seconds. The mobile station shall activate the Normal Service Subfunction. + If the mobile station does not accept the proposed service configuration and has an alternative service configuration to propose, the mobile station shall send a Service Response Message to propose the alternative service configuration within T59m seconds. The mobile station shall reset the subfunction timer for T68m seconds. 4. Service Response Message: The mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds. 5. General Handoff Direction Message: If the SCR_INCLUDED field is included in this message and is set to ‘1’: If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall activate the Normal Service Subfunction. 6. Universal Handoff Direction Message: If the SCR_INCLUDED field is included in this message and is set to ‘1’: If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall activate the Normal Service Subfunction. • If the mobile station receives one of the following service option negotiation messages, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds: 1. Service Option Request Order 2. Service Option Response Order 3. Service Option Control Order 2.6.4.1.2.2.3 Waiting for Service Response Message Subfunction While this subfunction is active, the mobile station waits to receive a Service Response Message. Upon activation of the Waiting for Service Response Message Subfunction, the mobile station shall set the subfunction timer for T68m seconds. While the Waiting for Service Response Message Subfunction is active, the mobile station shall perform the following: • If the subfunction timer expires, the mobile station shall activate the Normal Service Subfunction. • The mobile station shall process Forward and Reverse Traffic Channel frames in accordance with the current service configuration. The mobile station shall discard any Forward Traffic Channel frame which has a format that is not supported by the mobile station. The mobile station may discard any type of Forward Traffic Channel traffic that is not signaling traffic and is not part of the current service configuration. • The mobile station shall not initiate service negotiation for a new service configuration. • For any service option connection that is part of the current service configuration, the mobile station may send a Service Option Control Message to invoke a service option specific function in accordance with the requirements for the associated service option. • If SERV_NEGs changes from enabled to disabled (see 2.6.6.2.5.1), the mobile station shall activate the SO Negotiation Subfunction. • If the mobile station receives one of the following service negotiation messages, the mobile station shall process the message according to the specified requirements:
• If USE_OLD_SERV_CONFIGr equals ‘01’ or ‘10’, and if the mobile station entered the Mobile Station Control on the Traffic Channel State due to receiving an Extended Channel Assignment Message with GRANTED_MODE set to ‘11’, the mobile station shall send a Mobile Station Reject Order with the ORDQ field set to ‘00010100’ (stored configuration already restored at channel assignment) within T56m seconds, and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘00’, the mobile station shall perform the following: If the mobile station accepts the service configuration specified in the message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘01’, the mobile station shall perform the following: If the mobile station accepts the service configuration currently stored at the mobile station, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘10’, the mobile station shall perform the following: If the mobile station accepts the service configuration resulting from updating the stored service configuration with the service configuration received in this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘11’, the mobile station shall perform the following: if the mobile station accepts the service configuration resulting from restoring the indicated service option connection records from the stored service configuration and releasing the indicated service option connection records from the current service configuration, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction.
– If the purpose of the message is to reject a proposed service configuration, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds.
+ If the mobile station accepts the proposed service configuration, the mobile station shall send a Service Response Message to accept the proposed service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Connect Message Subfunction. + If the mobile station does not accept the proposed service configuration and does not have an alternative service configuration to propose, the mobile station shall send a Service Response Message to reject the proposed service configuration within T59m seconds. The mobile station shall activate the Normal Service Subfunction. + If the mobile station does not accept the proposed service configuration and has an alternative service configuration to propose, the mobile station shall send a Service Response Message to propose the alternative service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Request Message Subfunction. 4. Service Response Message: The mobile station shall process the message as follows: – If the service request sequence number (SERV_REQ_SEQr) from the message does not match the sequence number of the Service Request Message for which the mobile station is expecting a response, the mobile station shall not process the other Layer 3 fields of the message. – If the purpose of the message is to reject the service configuration proposed in the corresponding Service Request Message, the mobile station shall activate the Normal Service Subfunction. The mobile station may indicate to the user that the requested service configuration has been rejected.
+ If the mobile station accepts the proposed service configuration, the mobile station shall send a Service Request Message to accept the proposed service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Connect Message Subfunction. + If the mobile station does not accept the proposed service configuration and does not have an alternative service configuration to propose, the mobile station shall send a Service Request Message to reject the proposed service configuration within T59m seconds. The mobile station shall activate the Normal Service Subfunction. + If the mobile station does not accept the proposed service configuration and has an alternative service configuration to propose, the mobile station shall send a Service Request Message to propose the alternative service configuration within T59m seconds. The mobile station shall reset the subfunction timer for T68m seconds.
If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall activate the Normal Service Subfunction.
If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall activate the Normal Service Subfunction. • If the mobile station receives one of the following service option negotiation messages, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds: 1. Service Option Request Order 2. Service Option Response Order 3. Service Option Control Order 2.6.4.1.2.2.4 Waiting for Service Connect Message Subfunction While this subfunction is active, the mobile station waits to receive a Service Connect Message, a General Handoff Direction Message, or a Universal Handoff Direction Message containing a service configuration record. Upon activation of the Waiting for Service Connect Message Subfunction, the mobile station shall set the subfunction timer for T65m seconds. While the Waiting for Service Connect Message Subfunction is active, the mobile station shall perform the following: • If the subfunction timer expires, the mobile station shall activate the Normal Service Subfunction. • The mobile station shall process Forward and Reverse Traffic Channel frames in accordance with the current service configuration. The mobile station shall discard any Forward Traffic Channel frame which has a format that is not supported by the mobile station. The mobile station may discard any type of Forward Traffic Channel traffic that is not signaling traffic and is not part of the current service configuration. • The mobile station shall not initiate service negotiation for a new service configuration. • For any service option connection that is part of the current service configuration, the mobile station may send a Service Option Control Message to invoke a service option specific function in accordance with the requirements for the associated service option. • If SERV_NEGs changes from enabled to disabled (see 2.6.6.2.5.1), the mobile station shall activate the SO Negotiation Subfunction. • If the mobile station receives one of the following service negotiation messages, the mobile station shall process the message according to the specified requirements:
• If USE_OLD_SERV_CONFIGr equals ‘01’ or ‘10’, and if the mobile station entered the Mobile Station Control on the Traffic Channel State due to receiving an Extended Channel Assignment Message with GRANTED_MODE set to ‘11’, the mobile station shall send a Mobile Station Reject Order with the ORDQ field set to ‘00010100’ (stored configuration already restored at channel assignment) within T56m seconds, and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘00’, the mobile station shall perform the following: If the mobile station accepts the service configuration specified in the message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘01’, the mobile station shall perform the following: If the mobile station accepts the service configuration currently stored at the mobile station, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds, and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘10’, the mobile station shall perform the following: If the mobile station accepts the service configuration resulting from updating the stored service configuration with the service configuration received in this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds, and shall activate the Normal Service Subfunction. • If USE_OLD_SERV_CONFIGr equals ‘11’, the mobile station shall perform the following: if the mobile station accepts the service configuration resulting from restoring the indicated service option connection records from the stored service configuration and releasing the indicated service option connection records from the current service configuration, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds, and shall activate the Normal Service Subfunction.
3. Service Request Message: The mobile station shall process the message as follows: – If the purpose of the message is to reject a proposed service configuration, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds.
+ If the mobile station accepts the proposed service configuration, the mobile station shall send a Service Response Message to accept the proposed service configuration within T59m seconds. The mobile station shall reset the subfunction timer for T65m seconds. + If the mobile station does not accept the proposed service configuration and does not have an alternative service configuration to propose, the mobile station shall send a Service Response Message to reject the proposed service configuration within T59m seconds. The mobile station shall activate the Normal Service Subfunction. + If the mobile station does not accept the proposed service configuration and has an alternative service configuration to propose, the mobile station shall send a Service Response Message to propose the alternative service configuration within T59m seconds. The mobile station shall activate the Waiting for Service Request Message Subfunction.
If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall activate the Normal Service Subfunction.
If the mobile station has not rejected this message, the mobile station shall activate the Waiting for Service Action Time Subfunction; otherwise, the mobile station shall activate the Normal Service Subfunction. • If the mobile station receives one of the following service option negotiation messages, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds: 1. Service Option Request Order 2. Service Option Response Order 3. Service Option Control Order 2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction While this subfunction is active, the mobile station waits for the action time associated with a new service configuration. If the action time was specified by a Service Connect Message, the mobile station shall send the Service Connect Completion Message at the action time. While the Waiting for Service Action Time Subfunction is active, the mobile station shall perform the following: • Prior to the action time associated with the Service Connect Message, General Handoff Direction Message (containing a service configuration record), or Universal Handoff Direction Message (containing a service configuration record), the mobile station shall process Forward and Reverse Traffic Channel frames in accordance with the current service configuration. The mobile station shall discard any Forward Traffic Channel frame which has a format that is not supported by the mobile station. The mobile station may discard any type of Forward Traffic Channel traffic that is not signaling traffic and is not part of the current service configuration. • At the action time associated with the Service Connect Message, General Handoff Direction Message (containing a service configuration record) or Universal Handoff Direction Message (containing a service configuration record), the mobile station shall perform the following29: – If this is a Service Connect Message and USE_TYPE0_PLCMr equals ‘1’, the mobile station shall perform the following:
– If this is a Service Connect Message with USE_OLD_SERV_CONFIGr equals ‘01’, the mobile station shall perform the following: + If SYNC_ID_INCLr is included and set to ‘1’, the SYNC_IDr indicates the stored service configuration to be restored; otherwise, the SYNC_ID conveyed by the mobile station indicates the stored service configuration to be restored. + The Call Control instance identified by NULL shall also be identified by the connection reference assigned to the first service option connection in the stored Service Configuration information record. + For each service option connection (with corresponding connection reference CON_REFi) in the stored service configuration record, if any, except for the first one, Layer 3 shall instantiate a Call Control instance (as specified in 2.6.10) with a ‘restore indication’. The mobile station shall identify each of these Call Control instances by the corresponding CON_REFi. + The mobile station shall begin to use the stored service configuration corresponding to this SYNC_ID as the current service configuration as specified in 2.6.4.1.2.2.5.2 and shall begin to process Forward and Reverse Traffic Channel frames accordingly. The mobile station shall send a Service Connect Completion Message within T56m seconds after the action time. + The mobile station shall store the synchronization identifier corresponding to the stored service configuration as SYNC_IDs. + The mobile station shall exit this subfunction and activate the Normal Service Subfunction. – If this is a Service Connect Message with USE_OLD_SERV_CONFIGr equals ‘10’, the mobile station shall perform the following: + If SYNC_ID_INCLr is included and set to ‘1’ and SYNC_ID_BS_INITIATED_INDr is set to ‘1’, the SYNC_IDr indicates the stored service configuration to be restored; otherwise, the SYNC_ID conveyed by the mobile station indicates the stored service configuration to be restored. + The mobile station shall update the stored service configuration with the received service configuration as follows: The mobile station shall restore the stored service configuration as specified in 2.6.4.1.2.2.5.2. The mobile station shall process the received Service Configuration Record as specified in 2.6.4.1.12. The mobile station shall process the received Non-negotiable Service Configuration Record as specified in 2.6.4.1.13.
+ For each service option connection (with corresponding connection reference CON_REFi) in the stored service configuration record, if any, except for the first one, Layer 3 shall instantiate a Call Control instance (as specified in 2.6.10) with a ‘restore indication’. The mobile station shall identify each of these Call Control instances by the corresponding CON_REFi. + The mobile station shall begin to use the updated service configuration as the current service configuration and shall begin to process Forward and Reverse Traffic Channel frames accordingly. The mobile station shall send a Service Connect Completion Message within T56m seconds after the action time. + If SYNC_ID_INCLr is set to ‘1’ and SYNC_ID_BS_INITIATED_INDr is set to ‘0’, the mobile station shall perform the following:: The mobile station shall store the synchronization identifier received from the base station (SYNC_IDs = SYNC_IDr). The mobile station shall store the new service configuration corresponding to SYNC_IDs as specified in 2.6.4.1.2.2.5.1.
Otherwise, the mobile station shall set SYNC_IDs to NULL. + The mobile station shall exit this subfunction and activate the Normal Service Subfunction. – If this is a Service Connect Message with USE_OLD_SERV_CONFIGr equals ‘11’, the mobile station shall perform the following: + If the SYNC_ID_INCL field is included in this message and set to ‘1’, the SYNC_ID included in this message indicates the stored service configuration to be restored; otherwise, the SYNC_ID conveyed by the mobile station indicates the stored service configuration to be restored. o Prior to this message, if an Extended Channel Assignment Message with GRANTED_MODE set to ‘11’ was not received and a Service Connect Message, General Handoff Direction Message (with service configuration), or Universal Handoff Direction Message (with service configuration) was not successfully received or accepted by the mobile station since entering the Traffic Channel Substate, the mobile station shall perform the following:
o Otherwise, the mobile station shall perform the following at the action time of this message:
If SR_IDr equals ‘111’, the mobile station shall restore all remaining service option connection records. Otherwise, if SR_IDr equals ‘000’, the mobile station shall restore service option connection records corresponding to SR_IDs indicated by SR_ID_RESTORE_BITMAPr received in this message; otherwise the mobile station shall restore the service option connection record corresponding to the SR_IDr received in this message.
– Otherwise, the mobile station shall perform the following: + Prior to this message, if a Service Connect Message, General Handoff Direction Message (with service configuration), or Universal Handoff Direction Message (with service configuration) was not successfully received or accepted by the mobile station since entering the Traffic Channel Substate, the mobile station shall perform the following: he mobile station shall set the service configuration parameters (i.e. those signaled via the Service Configuration information record and the Non-Negotiable Service Configuration information record) to their default values as specified in 2.6.4.2. + The mobile station shall process the received Service Configuration Record as specified in 2.6.4.1.12, shall process the received Non-negotiable Service Configuration Record as specified in 2.6.4.1.13 (if included), and shall begin to use the service configuration specified by the Service Connect Message, General Handoff Direction Message or Universal Handoff Direction Message containing a service configuration record as the current service configuration and shall begin to process Forward and Reverse Traffic Channel frames accordingly. If the action time was specified by a Service Connect Message, the mobile station shall send a Service Connect Completion Message within T56m seconds after the action time. + If SYNC_ID_INCLr is set to ‘1’, the mobile station shall perform the following: The mobile station shall store the synchronization identifier received from the base station (SYNC_IDs = SYNC_IDr). The mobile station shall store the new service configuration corresponding to SYNC_IDs as specified in 2.6.4.1.2.2.5.1. Otherwise, the mobile station shall set SYNC_IDs to NULL. + If P_REV_IN_USEs is greater than six, the Non-Negotiable Service Configuration information record is not included in this message, and the value of SR_ID corresponding to the logical resource of ‘0000’ in the LOGICAL_TO_PHYSICAL_MAPPING_TABLE is NULL, the mobile station shall set this SR_ID field to the value specified in the Service Configuration information record. + If CC_INFO_INCLr equals ‘1’, then for each of the NUM_CALLS_ASSIGNr occurrences of the call control parameters included in the message, the mobile station shall perform the following: If RESPONSE_INDr equals ‘1’, and TAGr matches any of the TAG values contained in the list TAG_OUTSTANDING_LIST, the Layer 3 shall instantiate a Call Control instance (as specified in 2.6.10). The mobile station shall identify this Call Control instance by CON_REFr. The mobile station shall disable the enhanced origination timer associated with TAGr and remove the TAG value specified by TAGr from the list TAG_OUTSTANDING_LIST. If RESPONSE_INDr equals ‘0’, the mobile station shall store the bypass indicator (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr) and the Layer 3 shall instantiate a Call Control instance (as specified in 2.6.10). The mobile station shall identify this Call Control instance by CON_REFr. + The mobile station shall exit this subfunction and activate the Normal Service Subfunction. • The mobile station shall not initiate service negotiation for a new service configuration. • For any service option connection that is part of the current or pending service configuration, the mobile station may send a Service Option Control Message to invoke a service option specific function in accordance with the requirements for the associated service option. • If SERV_NEGs changes from enabled to disabled (see 2.6.6.2.5.1), the mobile station shall activate the SO Negotiation Subfunction. • If the mobile station receives one of the following service negotiation messages, the mobile station shall process the message according to the specified requirements:
If the mobile station has not rejected this message, the mobile station shall remain in this subfunction until the action time specified in the message, and shall perform the following: The mobile station shall not perform the above procedures for the previous message. But the call assignments from the previous message (if any) shall take effect at the action time of the previous message. The mobile station shall perform the above procedures for this message (that is, begin to use the service configuration specified by the General Handoff Direction Message) at the action time of this message.
If the mobile station has not rejected this message, the mobile station shall remain in this subfunction until the action time specified in the message, and shall perform the following: The mobile station shall not perform the above procedures for the previous message. But the call assignments from the previous message (if any) shall take effect at the action time of the previous message. The mobile station shall perform the above procedures for this message (that is, begin to use the service configuration and call assignments (if any) specified by the Universal Handoff Direction Message) at the action time of this message. • If the mobile station receives one of the following service option negotiation messages, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds: 1. Service Option Request Order 2. Service Option Response Order 3. Service Option Control Order 2.6.4.1.2.2.5.1 Storing a Service Configuration with SYNC_ID The mobile station shall set NUM_SYNC_ID_SUPPORTED as follows: • If the mobile station has not reported the Capability Information information record with the ADD_NUM_SYNC_ID field, the mobile station shall set NUM_SYNC_ID_SUPPORTED to four. • If the mobile station has reported the Capability Information information record with the ADD_NUM_SYNC_ID field, the mobile station shall set NUM_SYNC_ID_SUPPORTED to five plus the value of the ADD_NUM_SYNC_ID field included in the Capability Information information record. The mobile station shall be capable of storing a minimum of NUM_SYNC_ID_SUPPORTED service configurations along with their corresponding SYNC_ID, SID and NID. Two SYNC_IDs are considered to be equal if and only if both the length and value of the SYNC_IDs is equal. The mobile station shall use the following procedure in the order listed below to store the current service configuration when it is associated with a SYNC_ID: • If the mobile station has a stored service configuration associated with SIDs, NIDs and SYNC_IDs, then the mobile station shall delete the stored service configuration. • If the number of stored service configurations is NUM_SYNC_ID_SUPPORTED or more, the mobile station shall not delete the (NUM_SYNC_ID_SUPPORTED - 1) most recently used30 service configuration(s) and corresponding synchronization identifier(s), SID(s), NID(s). • he mobile station shall store the current service configuration (that is, parameters conveyed by both the Service Configuration information record and the Non-negotiable Service Configuration information record) and the SYNC_IDs corresponding to the current service configuration along with SIDs and NIDs. 2.6.4.1.2.2.5.2 Restoring a stored Service Configuration based on SYNC_ID When restoring a stored service configuration based on SYNC_ID, the mobile station shall restore only those parameters defined in the current P_REV_IN_USEs. 2.6.4.1.2.2.6 SO Negotiation Subfunction The SO Negotiation Subfunction is only supported for mobile stations operating in Band Class 0. Service option negotiation is not supported for P_REV_IN_USEs greater than six. Upon activation of the SO Negotiation Subfunction, the mobile station shall delete from the current service configuration any service option connection which does not use primary traffic on both the Forward and Reverse Traffic Channels and the Layer 3 shall terminate the corresponding Call Control instances. The Call Control instance corresponding to the service option connection which uses primary traffic, if any, shall be identified by NULL. While the SO Negotiation Subfunction is active, the mobile station shall perform the following: • If the current service configuration includes a service option connection, the mobile station shall process the received primary traffic bits in accordance with the requirements for the service option associated with the service option connection; otherwise, the mobile station shall discard the received primary traffic bits. • If the current service configuration includes a service option connection, the mobile station shall transmit primary traffic bits in accordance with the requirements for the service option associated with the service option connection; otherwise, the mobile station shall transmit null traffic on the Reverse Fundamental Channel, if the Fundamental Channel is present or transmit power control bits on the Reverse Pilot Channel, if only the Dedicated Control Channel is present. • If the current service configuration includes a service option connection, the mobile station may send a Service Option Control Order to invoke a service option specific function in accordance with the requirements for the service option associated with the service option connection. • To initiate service option negotiation, the mobile station shall set SO_REQs to the number of the requested service option and shall send a Service Option Request Order containing the requested service option number. • If SERV_NEGs changes from disabled to enabled (see 2.6.6.2.5.1), the mobile station shall set SO_REQs to NULL and shall activate the Normal Service Subfunction. • If the mobile station receives a Service Option Request Order, it shall process the order as follows: – If the mobile station accepts the requested service option, the mobile station shall set SO_REQs to NULL and shall send a Service Option Response Order accepting the requested service option within T58m seconds. The mobile station shall interpret the message action time of the Service Option Request Order in accordance with the requirements for the requested service option and the mobile station shall begin using the service configuration implied by the requested service option in accordance with those requirements. The implied service configuration shall include the default Forward and Reverse multiplex options and radio configurations associated with the requested service option, and shall include one service option connection for which the service option connection reference is 1, the service option is the requested service option, and the Forward and Reverse Traffic Channel types are both primary traffic. If a Call Control instance currently exists, the Layer 3 shall use this Call Control instance for a new service option connection; otherwise, the Layer 3 shall instantiate a Call Control instance (as specified in 2.6.10) and this Call Control instance shall be identified by both a connection reference with a value of 1 and a default identifier with a value of NULL. – If the mobile station does not accept the requested service option and has an alternative service option to request, the mobile station shall set SO_REQs to the alternative service option number and shall send a Service Option Request Order requesting the alternative service option within T58m seconds. – If the mobile station does not accept the requested service option and does not have an alternative service option to request, the mobile station shall set SO_REQs to NULL and shall send a Service Option Response Order to reject the request within T58m seconds. The mobile station shall continue to use the current service configuration. • If the mobile station receives a Service Option Response Order, it shall process the order as follows: – If the service option number specified in the order is equal to SO_REQs, the mobile station shall set SO_REQs to NULL. The mobile station shall interpret the message action time of the Service Option Response Order in accordance with the requirements for the specified service option, and the mobile station shall begin using the service configuration implied by the specified service option in accordance with those requirements. The implied service configuration shall include the default Forward and Reverse multiplex options and radio configurations associated with the specified service option, and shall include one service option connection for which the service option connection reference is 1, the service option is the specified service option, and the Forward and Reverse Traffic Channel types are both primary traffic. If a Call Control instance currently exists, the Layer 3 shall use this Call Control instance for a new service option connection; otherwise, the Layer 3 shall instantiate a Call Control instance (as specified in 2.6.10) and this Call Control instance shall be identified by both a connection reference with a value of 1 and a default identifier with a value of NULL. – If the order indicates a service option rejection, the mobile station shall set SO_REQs to NULL. The mobile station shall continue to use the current service configuration. – If the order does not indicate a service option rejection and the service option specified in the order is not equal to SO_REQs, the mobile station shall set SO_REQs to NULL and shall send a Mobile Station Reject Order (ORDQ = ‘00000100’) within T58m seconds. The mobile station shall continue to use the current service configuration. • If the mobile station receives a Service Option Control Order, it shall process the order as follows: – If the current service configuration includes a service option connection, the mobile station shall interpret the message action time of the Service Option Control Order in accordance with the requirements for the service option associated with the service option connection and the mobile station shall process the Service Option Control Order in accordance with those requirements; – otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000001’) within T56m seconds. • If the mobile station receives one of the following service negotiation messages, the mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within T56m seconds: 1. Service Connect Message 2. Service Option Control Message 3. Service Request Message 4. Service Response Message
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:
|
