Presentation is loading. Please wait.

Presentation is loading. Please wait.

TSG-C SWG2.3 Source: Lucent Technologies Contact: Krishna Balachandran Kenneth Budka Joseph Kang

Similar presentations


Presentation on theme: "TSG-C SWG2.3 Source: Lucent Technologies Contact: Krishna Balachandran Kenneth Budka Joseph Kang"— Presentation transcript:

1 TSG-C SWG2.3 Source: Lucent Technologies Contact: Krishna Balachandran [krishnab@lucent.com] Kenneth Budka [kbudka@lucent.com] Joseph Kang [jhkang@lucent.com] TITLE: QPCH Operation for BCMCS: Lucent thoughts on QC-TC-74 ABSTRACT: RECOMMENDATION: ©2003 Lucent Technologies, Inc. The contributors grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. The contributors. is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The contributors. specifically reserves the right to amend or modify the material contained herein and to any intellectual property of the contributors. other than provided in the copyright statement above. Discuss and adopt for IS-2000 Rev. D This contribution discusses QPCH operational scenarios for BCMCS, and enhancements to improve BCMCS mobile station battery life. C23-20040112-010

2 2 QPCH Operation for Type 1 Flows Type 1 denotes static streaming flows (e.g. “TV Channel” like programs)Type 1 denotes static streaming flows (e.g. “TV Channel” like programs) Operational Model: MS Originated BCMCSOperational Model: MS Originated BCMCS –When users want to watch BCMCS flow X, MSs will look for BSPM parameters related to BCMCS flow X –If flow is not transmitted on account of resource availability, then MSs that have done a BCMCS registration and have either timed out or been notified of unavailability may do the following: Alternative 1: If MSs are not monitoring QPCH BCMCS indicators, they can u Stop trying to acquire BSPM parameters for the flow, or u Blindly retry to acquire BSPM over common channels without any knowledge of when radio resources are allocated to the flow Alternative 2: If MSs are monitoring QPCH BCMCS indicators, they can be notified when radio resources (codes/power) are allocated to the flow u Differential BSPM can be used to provide flow parameters u QPCH BCMCS indicator monitoring can be relatively infrequent (i.e., of the order of acceptable wait times) for notifications in this case

3 3 QPCH Operation for Type 2 Flows Type 2 denotes dynamic BCMCS flows (e.g. PTT, stock updates)Type 2 denotes dynamic BCMCS flows (e.g. PTT, stock updates) Operational Model: MS Terminated BCMCSOperational Model: MS Terminated BCMCS –When BCMCS flow X is activated, MSs need to be notified within short period of time –If MS is monitoring BCMCS indicators on the QPCH, it can be notified of flow activation and changes to flow parameters Differential BSPM on the PCH or PBCCH can provide flow parameters QPCH monitoring needs to be quite frequent for these flows (i.e., to satisfy latency requirements for potentially “real time” services) –Users interested in monitoring such dynamic flows consciously trade off battery life for the support of the service

4 4 QPCH Operation for BCMCS Requirements (already satisfied in current procedures)Requirements (already satisfied in current procedures) –Latency requirements for Type 1 or Type 2 flow activation –Minimal impact to battery life of legacy mobile stations (current procedures result in no impact) Current QPCH procedures employ common BCMC slot cycle and broadcast indicator bits for both Type 1 and Type 2 flowsCurrent QPCH procedures employ common BCMC slot cycle and broadcast indicator bits for both Type 1 and Type 2 flows Desirable to enhance QPCH operationDesirable to enhance QPCH operation –Mobiles interested in monitoring a certain Type 1 flow should be minimally impacted by monitoring requirements for other Type 1 flows or Type 2 flows –Mobiles interested in monitoring a certain Type 2 flow should be minimally impacted by monitoring requirements for other Type 1 flows or Type 2 flows

5 5 QPCH Enhancements Multiple BCMC slot cycles that minimize impact to MSs with infrequent QPCH monitoring requirements while enabling dynamic servicesMultiple BCMC slot cycles that minimize impact to MSs with infrequent QPCH monitoring requirements while enabling dynamic services –Fast for real-time Type 2 flows, slow for Type 1 flows –Slot cycles are configurable BCMCS Indicator OptionsBCMCS Indicator Options –Non-flow specific BI bits only (currently supported) –Flow ID hashed PI bits only –Flow ID hashed PI and BI bits (previously proposed and deferred) Mobiles interested in monitoring multiple flows may choose to only monitor BI bits


Download ppt "TSG-C SWG2.3 Source: Lucent Technologies Contact: Krishna Balachandran Kenneth Budka Joseph Kang"

Similar presentations


Ads by Google