1、 TIA-2006-A March 2010Interoperability Specification (IOS) for Broadcast Multicast Services (BCMCS) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability
2、and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling produc
3、ts not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standar
4、ds Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicabl
5、e regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Standards Proposal No. 3-0361, formulated under the cognizance of the TIA TR-45.4 -
6、Radio and Switching Technology - Mobile and Personal Communications Standards) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATI
7、ON STANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these
8、documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request pe
9、rmission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright OR Telecommunications Industry Association Standards (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Documen
10、t may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no sear
11、ch or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation t
12、o investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non
13、-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”
14、) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA discl
15、aims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending pa
16、tent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents
17、 of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY
18、 OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRAN
19、TIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT O
20、R INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT,
21、 BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATION
22、S. TIA-2006-A i Table of Contents 1 Foreword. ix 2 1. Introduction.1-1 3 1.1 Purpose1-1 4 1.2 Scope.1-1 5 1.3 Document Convention 1-1 6 1.4 References.1-1 7 1.4.1 Normative References.1-1 8 1.5 Terminology1-3 9 1.5.1 Acronyms1-3 10 1.5.2 Definitions.1-4 11 1.6 BCMCS IOS Assumptions .1-5 12 2. Archit
23、ecture and Protocols2-1 13 2.1 Architectural Model 2-1 14 2.1.1 cdma2000 1x System 2-1 15 2.1.2 cdma2000 HRPD System with SC/MM in the AN.2-1 16 2.1.3 cdma2000 HRPD System with SC/MM in the PCF .2-1 17 2.2 Bearer Path Architecture.2-2 18 3. Feature Description.3-1 19 3.1 Basic Concepts3-1 20 3.1.1 S
24、ervice Announcement and Discovery .3-1 21 3.1.2 Content Subscriptions .3-1 22 3.1.3 Content Information Acquisition 3-1 23 3.1.4 Content Availability Determination3-1 24 3.1.5 RAN Session Discovery3-1 25 3.1.6 BCMCS Registration 3-2 26 3.1.7 BCMCS Deregistration.3-2 27 3.1.8 Bearer Path Establishmen
25、t 3-2 28 3.1.9 Bearer Path Release 3-2 29 3.2 Static Broadcast and Dynamic Broadcast .3-2 30 3.3 Accounting3-2 31 3.4 Encryption.3-3 32 3.5 Security .3-3 33 3.6 Page Set Maintenance .3-3 34 3.7 BSN Selection Algorithm .3-3 35 4. Feature Call Flows 4-1 36 4.1 MS Initiated BCMCS Registration and RAN S
26、ession Discovery.4-1 37 4.1.1 BCMCS Registration and RSD (1x System) 4-1 38 4.1.2 BCMCS Registration and RSD (HRPD System with SC/MM in the AN).4-2 39 4.1.3 BCMCS Registration and RSD (HRPD System with SC/MM in the PCF)4-3 40 4.2 BSN Session Information Update.4-4 41 4.2.1 BSN Session Information Up
27、date (1x and HRPD Systems).4-4 42 TIA-2006-A ii 4.3 Bearer Path Establishment 4-4 1 4.3.1 BS/AN Initiated Bearer Establishment - No A10 Established4-5 2 4.3.2 BS/AN Initiated Bearer Establishment - A10 Established4-5 3 4.4 Bearer Path Release 4-6 4 4.4.1 BS/AN Initiated Bearer Release - Last A8 Conn
28、ection4-6 5 4.4.2 BS/AN Initiated Bearer Release - Not Last A8 Connection .4-6 6 4.4.3 PCF Initiated Bearer Release A8 Connection4-7 7 4.4.4 PCF Initiated Bearer Release A10 Connection4-8 8 4.4.5 BSN Initiated Bearer Release .4-8 9 4.5 Page Set Maintenance .4-9 10 4.5.1 1x System4-9 11 4.5.2 HRPD Sy
29、stem with SC/MM in AN 4-10 12 4.5.3 HRPD System with SC/MM in the PCF.4-10 13 5. Control Plane and Bearer Plane Considerations .5-1 14 5.1 Bearer Plane Considerations for the A8 and A10 Interfaces 5-1 15 5.1.1 Protocol Stacks and Protocols.5-1 16 5.1.2 BCMCS Framing 5-1 17 5.2 Control Plane Consider
30、ations for A9 and A11 Interfaces.5-1 18 6. Broadcast A9 Signaling Messages6-1 19 6.1 General Considerations.6-1 20 6.2 A9 Message Procedures6-1 21 6.2.1 MS initiated Registration and RAN Session Discovery .6-1 22 6.2.1.1 A9-BC Service Request 6-1 23 6.2.1.1.1 Successful Operation 6-1 24 6.2.1.1.2 Fa
31、ilure Operation 6-2 25 6.2.1.2 A9-BC Service Response6-2 26 6.2.1.2.1 Successful Operation 6-2 27 6.2.1.2.2 Failure Operation 6-2 28 6.2.2 BSN Session Information Update.6-2 29 6.2.2.1 A9-BC Service Initiate Request6-2 30 6.2.2.1.1 Successful Operation 6-2 31 6.2.2.1.2 Failure Operation 6-2 32 6.2.2
32、.2 A9-BC Service Initiate Response .6-3 33 6.2.2.2.1 Successful Operation 6-3 34 6.2.2.2.2 Failure Operation 6-3 35 6.2.3 BCMCS Bearer Path Establishment .6-3 36 6.2.3.1 A9-BC Setup-A8.6-3 37 6.2.3.1.1 Successful Operation 6-3 38 6.2.3.1.2 Failure Operation 6-3 39 6.2.3.2 A9-BC Connect-A8 6-3 40 6.2
33、.3.2.1 Successful Operation 6-3 41 6.2.3.2.2 Failure Operation 6-4 42 6.2.4 BCMCS Bearer Path Release6-4 43 6.2.4.1 A9-BC Disconnect-A86-4 44 TIA-2006-A iii 6.2.4.1.1 Successful Operation 6-4 1 6.2.4.1.2 Failure Operation 6-4 2 6.2.4.2 A9-BC Release-A8 .6-4 3 6.2.4.2.1 Successful Operation 6-4 4 6.2
34、.4.2.2 Failure Operation 6-4 5 6.2.4.3 A9-BC Release-A8 Complete.6-4 6 6.2.4.3.1 Successful Operation 6-4 7 6.2.4.3.2 Failure Operation 6-5 8 6.3 A9 Message Formats.6-5 9 6.3.1 A9-BC Service Request 6-5 10 6.3.2 A9-BC Service Response6-7 11 6.3.3 A9-BC Setup-A8.6-11 12 6.3.4 A9-BC Connect-A8 6-12 13
35、 6.3.5 A9-BC Disconnect-A86-13 14 6.3.6 A9-BC Release-A8 .6-14 15 6.3.7 A9-BC Release-A8 Complete.6-16 16 6.3.8 A9-BC Service Initiate Request6-17 17 6.3.9 A9-BC Service Initiate Response .6-18 18 6.4 A9 Information Element Definitions 6-19 19 6.4.1 Generic Information Element Encoding .6-19 20 6.4.
36、1.1 A9 Information Element Identifiers6-19 21 6.4.1.2 Cross Reference of Information Elements with Messages6-20 22 6.4.2 Information Elements6-21 23 6.4.2.1 A9 Message Type .6-21 24 6.4.2.2 A8 BC Traffic ID 6-22 25 6.4.2.3 BCMCS Information List6-23 26 6.4.2.4 BCMCS Flow and Registration Information
37、 6-25 27 6.4.2.5 BCMCS Registration Result .6-28 28 6.4.2.6 BCMCS Flow ID 6-30 29 6.4.2.7 Cause.6-30 30 6.4.2.8 Correlation ID .6-32 31 6.4.2.9 Mobile Identity (IMSI/ATI)6-32 32 6.4.2.10 HRPD Subnet6-32 33 6.4.2.11 A9 Indicators.6-32 34 6.4.2.12 BSID .6-33 35 6.4.2.13 Enhanced BCMCS Information List
38、.6-33 36 6.5 Timer Definitions6-35 37 6.5.1 Timer Values.6-35 38 6.5.2 Timer Definitions6-35 39 6.5.2.1 Tbcsreq96-35 40 6.5.2.2 Tbcsetup96-35 41 6.5.2.3 Tbcrel96-35 42 6.5.2.4 Tbcdiscon96-35 43 TIA-2006-A iv 6.5.2.5 Tbcsireq9.6-35 1 7. Broadcast A11 Signaling Messages7-1 2 7.1 General Considerations
39、.7-1 3 7.2 A11 Message Procedures7-1 4 7.2.1 MS initiated Registration and RAN Session Discovery .7-1 5 7.2.1.1 A11-BC Service Request 7-1 6 7.2.1.1.1 Successful Operation 7-1 7 7.2.1.1.2 Failure Operation 7-1 8 7.2.1.2 A11-BC Service Response7-1 9 7.2.1.2.1 Successful Operation 7-1 10 7.2.1.2.2 Fai
40、lure Operation 7-2 11 7.2.2 BSN Session Information Update.7-2 12 7.2.2.1 A11-BC Service Initiate Request7-2 13 7.2.2.1.1 Successful Operation 7-2 14 7.2.2.1.2 Failure Operation 7-2 15 7.2.2.2 A11-BC Service Initiate Response .7-2 16 7.2.2.2.1 Successful Operation 7-2 17 7.2.2.2.2 Failure Operation
41、7-3 18 7.2.3 BCMCS Bearer Path Establishment and Release .7-3 19 7.2.3.1 A11-BC Registration Request.7-3 20 7.2.3.1.1 Successful Establishment Operation.7-3 21 7.2.3.1.2 Successful Release Operation.7-3 22 7.2.3.1.3 Failure Operation 7-3 23 7.2.3.2 A11-BC Registration Reply7-3 24 7.2.3.2.1 Successfu
42、l Operation 7-3 25 7.2.3.2.2 Failure Operation 7-3 26 7.2.3.3 A11-BC Registration Update7-4 27 7.2.3.3.1 Successful Operation 7-4 28 7.2.3.3.2 Failure Operation 7-4 29 7.2.3.4 A11-BC Registration Acknowledge .7-4 30 7.2.3.4.1 Successful Operation 7-4 31 7.2.3.4.2 Failure Operation 7-4 32 7.3 A11 Mes
43、sage Formats.7-4 33 7.3.1 A11-BC Service Request 7-4 34 7.3.2 A11-BC Service Response7-7 35 7.3.3 A11-BC Registration Request.7-10 36 7.3.4 A11-BC Registration Reply7-13 37 7.3.5 A11-BC Registration Update7-16 38 7.3.6 A11-BC Registration Acknowledge .7-17 39 7.3.7 A11-BC Service Initiate Request7-1
44、9 40 7.3.8 A11-BC Service Initiate Response .7-22 41 7.4 A11 Information Element Definitions 7-23 42 7.4.1 Generic Information Element Encoding .7-23 43 7.4.1.1 A11 Information Element Identifiers7-24 44 TIA-2006-A v 7.4.1.2 Cross Reference of Information Elements with Messages7-24 1 7.4.2 Informati
45、on Element .7-26 2 7.4.2.1 A11 Message Type .7-26 3 7.4.2.2 Flags7-27 4 7.4.2.3 Lifetime.7-27 5 7.4.2.4 Home Address.7-27 6 7.4.2.5 Home Agent7-27 7 7.4.2.6 Care-of-Address7-27 8 7.4.2.7 Identification.7-27 9 7.4.2.8 Code 7-27 10 7.4.2.9 Status.7-28 11 7.4.2.10 Mobile-Home Authentication Extension 7
46、-28 12 7.4.2.11 Registration Update Authentication Extension.7-28 13 7.4.2.12 Session Specific Extension .7-28 14 7.4.2.13 BCMCS Session Extension.7-30 15 7.4.2.14 Reason.7-38 16 7.4.2.15 Critical Vendor/Organization Specific Extension (CVSE).7-39 17 7.4.2.16 Normal Vendor/Organization Specific Exte
47、nsion (NVSE) 7-42 18 7.5 Timer Definitions7-44 19 7.5.1 Timer Values.7-44 20 7.5.2 Timer Definitions7-44 21 7.5.2.1 Tbcsreq117-44 22 7.5.2.2 Tbcreq11.7-44 23 7.5.2.3 Tbcupd117-44 24 7.5.2.4 Tbcsireq11.7-45 25 8. Transport.8-1 26 8.1 GRE Attributes8-1 27 8.1.1 Segmentation Indication: 8-1 28 9. A1 Si
48、gnaling Messages.9-1 29 9.1 General Considerations.9-1 30 9.2 A1 Message Procedures9-1 31 9.2.1 Page Set Maintenance .9-1 32 9.2.1.1 Location Updating Request.9-1 33 9.2.1.1.1 Successful Operation 9-1 34 9.2.1.1.2 Failure Operation 9-1 35 9.2.1.2 Location Updating Accept 9-1 36 9.2.1.3 Other Message
49、s Directed to the MS .9-1 37 9.2.1.3.1 Successful Operation 9-1 38 9.2.1.3.2 Failure Operation 9-1 39 9.3 A1 Message Formats.9-2 40 9.3.1 Location Updating Request.9-2 41 9.3.2 Location Updating Accept 9-2 42 9.3.3 Other Messages Directed to the MS .9-2 43 TIA-2006-A vi Table of Figures 1 Figure 2.2-1 Bearer path architecture 2-2 2 Figure 4.1.1-1: BCMCS Registration and RSD (1x System).4-1 3 Figure 4.1.2-1: BCMCS Registration and RSD (HRPD System with SC/MM in the AN) .4-2 4 Figure 4.1.3-1: BCMCS Registration and RSD (HRPD System with SC/MM in the PCF)4-3 5 Figure 4.2.1-1 BSN Sessio
