60 likes | 204 Views
DO-1X Paging Notification Proposal. Lei Yu (lei.yu@nokia.com). DO->1X Paging Notification Requirement. The mechanism should work well with IS2000 Rev 0 (P_REV 6) compliance mobile.
E N D
DO-1X Paging Notification Proposal Lei Yu (lei.yu@nokia.com)
DO->1X Paging Notification Requirement • The mechanism should work well with IS2000 Rev 0 (P_REV 6) compliance mobile. • The mechanism should allow mobile receiving the DO page notification in 1X system to go to DO system as soon as possible (e.g., skipping page response and so on). • The mechanism should work well for mobile in idle state or traffic state. • The notification should give mobile terminal as much information as possible to support: • Allow mobile terminal forwarding notification to end-user and choose to switch to DO or not. • Provide as much DO network information as possible allowing fast transition.
Proposal Details • Using Data Burst Message to deliver DO page notification to mobile terminal in idle state or traffic state. • New burst type “000111” is defined as DO page notification. • Mechanism is the same for mobile in idle state or traffic state. • New DBM could carry extra following information (not limited to this list) • DO network information enabling fast transition to DO system: DO frequency information, DO overhead information, DO TrafficAssignment and etc. • Specific DO service availability information: Knowing specifically what service is ready in DO network help end-user decide whether to switch to DO system or not. This is especially useful when mobile terminal is in traffic state.
Proposal Details (cont.) • ACK_REQ field in DBM can specify whether or not mobile needs to send back response on r-csch in 1X system before going to DO system. This allows two possible implementations: • Fast Repeat: In this mode, 1X network sends DBM multiple times without ACK required. This will allow AT transition to DO faster and still provide good delivery successful rate. • Assured Delivery: In this mode, 1X network sends DBM with ACK required. This will guarantee the delivery of the notification at the expense of slower transition to DO.
Proposal Details (cont.) • Use RESERVED field in GPM as indication for hybrid terminal to keep monitoring f-csch. • RESERVED field in GPM is set to ‘0001’ if there is DBM (BustType = ‘000111’) in hybrid terminal’s assigned slot or the slot after. • For non-hybrid terminal, it will ignore the RESERVED field and stop monitoring f-csch as per IS2000 standard. • For hybrid terminal, if it receives GPM with RESERVED field set to ‘0001’ in its assigned slot, it should keep monitoring f-csch until one of the following conditions is true: • GPM with RESERVED field set to ‘0000’ is received in its assigned slot and mobile terminal declares address mismatch for the GPM. • GPM is received in the slot after its assigned slot and mobile terminal declares address mismatch for the GPM • Mobile terminal finishes monitoring the slot after its assigned slot on f-csch.
Scenarios • Scenario 1: mobile terminal is in idle state • Network sends DBM with BurstType set to ‘000111’ to mobile terminal. • Mobile terminal does not send back response and switch to DO system if ACK_REQ field in DBM is set to 0. • Scenario 2: mobile terminal is in 1X traffic state • Network sends DBM with BurstType set to ‘000111’ to mobile terminal. • Mobile terminal forwards the notification to end-user and let end-user decide to switch to DO system or not. • If end-user chooses to switch to DO system, mobile terminal will end 1X traffic normally and start transitioning to DO network.