1 / 17

BCMCS Framework TSG-X BCMCS Adhoc August 20, 2003

BCMCS Framework TSG-X BCMCS Adhoc August 20, 2003. Current Status. Stage 1 Document (S.P 0030-A, v. 0.4.3): Ad hoc and TSG-S WG1 jointly reviewed the document Under other TSGs review now Security Framework Document (S.P 0083, v.0.6): Adhoc and TSG-S WG4 jointly reviewed the document

giona
Download Presentation

BCMCS Framework TSG-X BCMCS Adhoc August 20, 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BCMCS FrameworkTSG-X BCMCS AdhocAugust 20, 2003

  2. Current Status • Stage 1 Document (S.P 0030-A, v. 0.4.3): • Ad hoc and TSG-S WG1 jointly reviewed the document • Under other TSGs review now • Security Framework Document (S.P 0083, v.0.6): • Adhoc and TSG-S WG4 jointly reviewed the document • Under other TSGs review • BCMCS Framework Document (X.P 0019, v.0.1.3): • Draft baseline text are under other TSGs review • One open issue: Framing • TSG-X: • Stage 2 and 3 work started, will be in a separate document from X.P0011 (TIA-835) • TSG-A: • Stage 2 and 3 will be in a separate document from IOS 5.0? • TSG-C: • 1X EVDV: Plans to be in C.S0001-C.S0005 (TIA-2000-D)? • 1X EVDO: Baseline in July and V&V is compete (C.S0054)

  3. BCMCS Concepts

  4. Overview • Optimize use of the cdma2000 radio interface over the air • BCMCS provides delivery of the IP flows that comprise BCMCS Programs (content) to one or more terminals in one or more regions of the 3GPP2 network. • The 3GPP2 operator has control of: • Transmission Areas of BCMCS IP flows • Billing of the user and/or content provider • Encryption of the IP flows • Examples: weather, stock, news, pay per view movies, sport events etc.

  5. Architecture

  6. Architecture • BCMCS Controller: • Communicates with the mobile to provide detailed information necessary to choose and receive a BCMCS program. May also provide lists of available programs. • Communicates with the BCMCS Content Provider to control the ability of a Content Provider to send BCMCS programs to a BCMCS Content Server. • May generate BCMCS Access Keys (BAKs) to encrypt BCMCS program content. • Distributes BAK to the MS • Communicates via the S-AAA with the PDSN to provide IP multicast addressing and flow treatment information to the PDSN. • BCMCS Content Provider: • Is the source of BCMCS programs sent to users. • Communicates with the BCMCS Controller to arrange the delivery of a program to a BCMCS Content Server.

  7. Architecture • BCMCS Content Server: • Is the last application that manipulates the BCMCS IP flows before they are sent to the PDSNs. • May combine several input programs from BCMCS Content Providers, e.g., traffic + weather + advertising combining. • Provides upper layer encryption of BCMCS programs when so chosen by the operator. • BCMCS Client on the mobile: • Communicates with the BCMCS Controller via normal IP methods in a client-server relationship to obtain detailed information necessary to receive desired BCMCS programs. • Decrypts and displays BCMCS program.

  8. Basic Procedures • Service Discovery/Announcement • Used to find out available BCMCS service • Distribute information about the service, parameters required for information acquisition and program schedule • Via out of band mechanisms • Content Subscriptions • Subscribes to BCMCS • RK (Registration Key) is provisioned • Via out of band mechanisms • Information Acquisitions • Obtain BCMCS Session related info from Controller (BCMCS_FLOW_ID, header compression etc) • Obtain Security Parameters (BAK etc) • Content Availability Determination • Determines whether a Multicast IP flow is available in a particular sector and the BCMCS radio configuration information • Via the overhead messages from a BS • BCMCS Registration • Request for delivering the IP flows in a particular sector • The first user may trigger the Bearer Path establishment • Notify where to page the MS • Reception of the Content • BCMCS Deregistration

  9. Key Hierarchy for CS-MS Security SK (Session Key) • Used to decrypt content. • Changes frequently to discourage session theft • Generated by the UIM card and sent to the ME BAK (BCMCS Access Key) • Used to generate SK • Provides access to program/multicast IP flow • Decrypted and stored in the UIM TK (Temporary Key) • Used to encrypt/decrypt the BCMCS Access Key (BAK) for transmission to the MS • Generated from RK RK (Registration Key) • Used to generate TK • RK is obtained when user subscribes to broadcast services • Stored in the UIM

  10. Security Architecture

  11. Protocol Stack

  12. BCMCS Parameters (Non-security related) • Content Name • Content Name represents the name given to the BCMCS Content Stream by the service provider. • Content Names are likely to be human-friendly. • Content Name is discovered by the user via SMS, WAP, HTML, etc. • Multicast IP Address and Transport Layer Port Number • A {Multicast IP Address and Transport Layer Port Number} tuple identifies the destination multicast IP address and the destination transport layer (e.g., UDP) port number for an IP flow within a BCMCS Content Stream. • BCMCS_FLOW_ID • BCMCS_FLOW_ID is an alias for the {Multicast IP Address and Transport Layer Port Number}. Used to efficiently transport over the air. • Radio Parameters • Examples of these parameters are physical channel identification and characteristics, logical channel identification, logical channel to physical channel mapping, soft handoff group and registration parameters.

  13. Operational Scenarios- Service Discovery, Information Acquisition, and Content Availability Determination

  14. Operational Scenarios- Bearer Path Setup (PPP Required)

  15. Operational Scenarios - Bearer Path Setup (w/o PPP Required)

  16. Accounting • Collected accounting data should be able to help service provider: • Billing on BCMCS Originators/Content Provider • Billing on BCMCS viewers/subscribers • Accounting type: • Flat fee (e.g., monthly payment) • Pay per view • Usage Based • Accounting data may be collected by: • RAN • PDSN • BCMCS Controller • Accounting data should send to HAAA.

  17. Example for Accounting by BCMCS Controller • The BCMCS client application on the MS communicates with the BCMCS Controller to acquire BCMCS information. • The BCMCS Controller responds with the BCMCS information. This information may include BAK values that will allow the user to receive and properly decode BCMCS content streams. • The BCMCS Controller sends accounting information to the AAA. • The AAA responds to acknowledge the accounting information. • The BCMCS Controller may include the following accounting information for each subscribed user: • - User Identity (NAI) - BCMCS Controller Identity • - BCMCS_FLOW_ID - Content name • - BAK_ID - BAK lifetime • - Multicast IP address(es)/port number(s) of the content stream

More Related