1、 TIA-1041-A-1 April 2011Broadcast and Multicast Service in cdma2000 Wireless IP Network Addendum 1 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability a
2、nd 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 product
3、s 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 Standard
4、s 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 applicable
5、 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 Project No. 3-0161-RV1-AD1, formulated under the cognizance of the TIA TR-45 Mobile
6、(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 Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may invo
7、lve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a st
8、atement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to 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 cond
9、itions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respe
10、cts the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise)
11、, whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims 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 Ref
12、erence; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identi
13、fication to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the co
14、ntents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS IN
15、TELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODU
16、CT 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 OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDE
17、NTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING
18、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 LIMITATIONS. 3GPP2 X.S0022-A v2.0 i Broadcast and Multicast Service in cdma2000 Wireless IP Network 1 CONTENTS 2 1 Introduction 1 3 2 Glossary and Definitions
19、 2 4 2.1 Acronyms 2 5 2.2 Definitions 3 6 3 References 4 7 3.1 Normative References 4 8 3.2 Informative References 5 9 4 Protocol Reference Model 7 10 4.1 Network Reference Model 7 11 4.2 Protocol Stack 9 12 4.3 BCMCS Flow ID Structure 11 13 5 BCMCS Service Description 13 14 5.1 Service Discovery/An
20、nouncement 13 15 5.2 Content Subscriptions 13 16 5.3 BCMCS Information Acquisition 13 17 5.4 Content Availability Determination 13 18 5.5 BCMCS Registration 13 19 5.6 BCMCS Content Delivery 14 20 5.7 BCMCS De-registration 14 21 6 BCMCS Controller Discovery 15 22 6.1 Static BCMCS Controller Discovery
21、 15 23 6.2 Dynamic BCMCS Controller Discovery 15 24 6.2.1 BCMCS Controller DHCP Option .15 25 6.2.1.1 MS Requirements15 26 6.2.1.2 PDSN Requirements .15 27 6.2.1.3 DHCP Server Requirements15 28 6.2.2 BCMCS Controller DHCPv6 Option16 29 6.2.2.1 MS Requirements16 30 6.2.2.2 PDSN Requirements .16 31 6.
22、2.2.3 DHCPv6 Server Requirements16 32 7 BCMCS Information Acquisition 17 33 7.1 MS Requirements 18 34 7.2 BCMCS Controller Requirements 19 35 7.3 Home RADIUS Server Requirements 20 36 3GPP2 X.S0022-A v2.0 ii7.4 Protocol and Message Format 21 1 7.5 Message-body Tag Definitions 21 2 7.6 MIME Type 21 3
23、 7.6.1 HTTP Information Acquisition Request.21 4 7.6.2 HTTP Information Acquisition Response.22 5 7.6.3 HTTP Information Acquisition Reject22 6 7.6.4 XML Elements22 7 7.6.4.1 .23 8 7.6.4.1.1 23 9 7.6.4.1.2 29 10 7.6.4.1.3 .36 11 7.7 XML Schema 38 12 8 BCMCS Controller and Content Server Interface 46
24、 13 8.1 BCMCS Flow Life Cycle 46 14 8.1.1 Inactive State 47 15 8.1.2 Active, Idle State.47 16 8.1.3 Active, Busy State.48 17 8.2 CS-BCMCS Control Protocol 48 18 8.3 CS-BCMCS Control Protocol Messages 48 19 8.3.1 CS-BCMCS Control Protocol Message Procedures .49 20 8.3.1.1 Add BCMCS Flow49 21 8.3.1.1.
25、1 CS Functional Requirements .49 22 8.3.1.1.2 BCMCS Controller Functional Requirements .49 23 8.3.1.2 Modify BCMCS Flow.50 24 8.3.1.2.1 CS Functional Requirements .50 25 8.3.1.2.2 BCMCS Controller Functional Requirements .50 26 8.3.1.3 Remove BCMCS Flow51 27 8.3.1.3.1 CS Functional Requirements .51
26、28 8.3.1.3.2 BCMCS Controller Functional Requirements .51 29 8.3.1.4 State Synchronization51 30 8.3.1.5 Refresh Keys .52 31 8.3.1.5.1 CS Functional Requirements .52 32 8.3.1.5.2 BCMCS Controller Functional Requirements .52 33 8.3.1.6 FlowInformation52 34 8.3.1.6.1 CS Functional Requirements .53 35 8
27、.3.1.6.2 BCMCS Controller Functional Requirements .53 36 8.3.2 Message Format53 37 8.3.2.1 AddFlowRequest.54 38 8.3.2.2 AddFlowResponse 55 39 8.3.2.3 ModifyFlowRequest55 40 8.3.2.4 ModifyFlowResponse .56 41 8.3.2.5 RemoveFlowRequest 56 42 8.3.2.6 RemoveFlowResponse 57 43 8.3.2.7 RefreshKeyRequest.57
28、 44 8.3.2.8 RefreshKeyResponse 57 45 3GPP2 X.S0022-A v2.0 iii 8.3.2.9 FlowInformation58 1 8.3.2.10 FlowInformationResponse 58 2 8.3.2.11 ResetRequest .58 3 8.3.2.12 ResetResponse.58 4 8.3.3 Information Elements .59 5 8.3.3.1 AuthenticationExtension .59 6 8.3.3.2 BAKParameter 60 7 8.3.3.3 BCMCSFlowHa
29、ndle .61 8 8.3.3.4 ContentProviderID 62 9 8.3.3.5 ContentTunnelProtocolOption 63 10 8.3.3.6 DelayOffset .63 11 8.3.3.7 EndTime64 12 8.3.3.8 FailedParameter.64 13 8.3.3.9 QoSParameters65 14 8.3.3.10 L3TunnelDestinationAddress66 15 8.3.3.11 L3TunnelSourceAddress.66 16 8.3.3.12 MulticastFlowAddress_BCM
30、CSFlowHandle .67 17 8.3.3.13 ResultCode 68 18 8.3.3.14 SDPParameters70 19 8.3.3.15 StartTime.71 20 9 BCMCS Bearer Path Setup 72 21 9.1 Bearer Path Setup between MS and BSN 72 22 9.2 Join Multicast Group from BSN 72 23 9.2.1 IGMP Support.73 24 9.2.2 MLD Support73 25 9.3 BSN-Content Server Unicast Tun
31、nel 74 26 10 BSN Session Management 75 27 10.1 Session Discovery Triggered by the BSN 75 28 10.1.1 BSN Requirement.75 29 10.1.2 SAAA/BCMCS Controller Requirement76 30 10.2 Session Information Triggered by the BCMCS Controller 76 31 10.2.1 SAAA/BCMCS Controller Requirement76 32 10.2.2 BSN Requirement
32、.77 33 10.3 Session Termination Triggered by the BCMCS Controller 77 34 10.3.1 SAAA/BCMCS Controller Requirements 77 35 10.3.2 BSN Requirements .78 36 11 BCMCS Security 79 37 11.1 Authentication, Authorization and Integrity Check 79 38 11.1.1 Information Acquisition79 39 11.1.1.1 BCMCS Controller Re
33、quirement 79 40 11.1.1.2 Home RADIUS Server Requirement 80 41 11.1.1.3 MS Requirement .81 42 11.1.2 Registration.81 43 3GPP2 X.S0022-A v2.0 iv11.1.2.1 BSN Requirements81 1 11.1.2.2 SAAA/BCMCS Controller Requirements.81 2 11.2 Key Management 82 3 11.3 Encryption 82 4 11.3.1 Link Layer Encryption82 5
34、11.3.2 Higher Layer Encryption 82 6 11.3.2.1 Authentication Tag83 7 12 Header Compression 85 8 12.1 MS Requirements 85 9 12.2 BCMCS Controller Requirements 85 10 12.3 BSN Requirements 86 11 13 Accounting 87 12 13.1 General 87 13 13.1.1 BAK Based Accounting88 14 13.1.1.1 BCMCS Controller Usage Data R
35、ecord (UDR)88 15 13.1.1.2 Accounting Formats 89 16 13.1.1.3 BCMCS Controller Procedure.91 17 13.1.1.4 RADIUS Server Procedure .91 18 13.1.2 Octet Count Based Accounting.91 19 13.1.2.1 BCMCS Airlink Records.91 20 13.1.2.1.1 BCMCS A10 Connection Setup Airlink Record .92 21 13.1.2.1.2 BCMCS Active Star
36、t Airlink Record.92 22 13.1.2.1.3 BCMCS Active Stop Airlink Record.92 23 13.1.2.2 BSN Usage Data Record (UDR) .93 24 13.1.2.3 Accounting Formats 94 25 13.1.2.4 BSN Procedures 96 26 13.1.2.4.1 A10 Connection Setup Airlink Record Arrives .97 27 13.1.2.4.2 Arrival of Forward Link Direction BCMCS Flow.9
37、7 28 13.1.2.4.3 Active Start Airlink Record Arrives 97 29 13.1.2.4.4 Active Stop Airlink Record Arrives.97 30 13.1.2.4.5 Interim-Update Record Trigger .97 31 13.1.2.4.6 Stop Record Trigger.97 32 13.1.2.4.7 Time of Day Timer Expires .98 33 13.1.2.5 RADIUS Server Procedure .98 34 14 BCMCS RADIUS Vendo
38、r Specific Attribute 99 35 15 A List of 3GPP2 VSAs between the BSN and SAAA/BCMCS Controller 110 36 16 A List of 3GPP2 VSAs between the BCMCS Controller and HAAA 112 37 Annex A: Call Flows (Informative) 113 38 Annex B: Sample XML Output (Informative) 122 39 B.1 BCMCS Information Acquisition Request
39、122 40 3GPP2 X.S0022-A v2.0 v B.2 BCMCS Information Acquisition Response 122 1 B.3 BCMCS Information Acquisition Reject 123 2 Annex C: XML Data Structure (Normative) 124 3 Annex D: The Example of The usage of Reserved Program ID (Informative) 128 4 5 3GPP2 X.S0022-A v2.0 vi LIST OF FIGURES 1 Figure
40、4-1 Network Reference Model .7 2 Figure 4-2 Protocol Reference Model for BCMC Bearer Path (when Segment-based framing is 3 applied).10 4 Figure 4-3 Protocol Reference Model for BCMC Bearer Path (when HDLC-Like Framing is 5 applied).10 6 Figure 4-4 An Example of the BCMCS Flow ID Structure.12 7 Figur
41、e 8-1 BCMCS Flow Handle States47 8 Figure 8-2 Common Header Format and Body Format .53 9 Figure 8-3 AuthenticationExtension 60 10 Figure 8-4 BAKParameter .60 11 Figure 8-5 Field format for Port number and IP address .61 12 Figure 8-6 BCMCSFlowHandle 62 13 Figure 8-7 ContentProviderAddress 62 14 Figu
42、re 8-8 ContentTunnelProtocolOption .63 15 Figure 8-9 DelayOffset 63 16 Figure 8-10 EndTime.64 17 Figure 8-11 FailedParameter64 18 Figure 8-12 QoSParameters.65 19 Figure 8-13 L3TunnelDestinationAddress.66 20 Figure 8-14 L3TunnelSourceAddress67 21 Figure 8-15 MulticastFlowAddress_BCMCSFlowHandle 68 22
43、 Figure 8-16 ResultCode .69 23 Figure 8-17 SDPParameters.71 24 Figure 8-18 StartTime71 25 Figure 11-1 SRTP Key Derivation.83 26 Figure 11-2 MKI Format .83 27 Figure 11-3 BCMCS SRTP Authentication Tag format 84 28 Figure 13-1 Octet Count Based Accounting Architecture .87 29 Figure 13-2 Per BAK based
44、Accounting Architecture.88 30 Figure 14-1 3GPP2 BCMCS RADIUS Attribute Format 99 31 Figure 14-2 Authorization Parameters VSA Format99 32 Figure 14-3 BCMCS Capability VSA Format .100 33 Figure 14-4 Common Session Info VSA Format.101 34 Figure 14-5 BSN Session Info VSA Format103 35 Figure 14-6 RAN Ses
45、sion Info VSA Format .104 36 Figure 14-7 Subnet VSA Format .106 37 Figure 14-8 TK Info VSA Format .107 38 Figure 14-9 BAK_ID VSA Format107 39 Figure 14-10 Content Provider ID format109 40 41 3GPP2 X.S0022-A v2.0 vii Figure A - 1 Registration Authorization, Bearer.113 1 Figure A - 2 HTTP Authenticati
46、on and Integrity Protection 116 2 Figure A - 3 Network Initiated Flow 118 3 Figure A - 4 Success Add Flow Scenario .119 4 Figure A - 5 Successful Modify Flow Scenario120 5 Figure A - 6 Successful Remove Flow Scenario 121 6 7 Figure C- 1 XML Overall Structure 124 8 Figure C- 2 XML Data Structure: Req
47、uest124 9 Figure C- 3 XML Data Structure: PgmInfo under Request .125 10 Figure C- 4 XML Data Structure: ReqSysInfo under Request 125 11 Figure C- 5 XML Data Structure: Response126 12 Figure C- 6 XML Data Structure: GenInfo under Response and BCMCSInfo .126 13 Figure C- 7 XML Data Structure: PgmInfo
48、under Response and BCMCSInfo.127 14 Figure C- 8 XML Data Structure: Reject.127 15 16 Figure D- 1 Static Mapping Reserved Group IDs in IPv4 Multicast Address Space 128 17 Figure D- 2 Static Mapping Reserved Flow IDs in 16 bit BCMCS Flow ID129 18 Figure D- 3 Static Mapping Reserved Flows IDs in 24 bit
49、 BCMCS Flow ID 130 19 Figure D- 4 Static Mapping Reserved Flows IDs in 32 bit BCMCS Flow ID 130 20 3GPP2 X.S0022-A v2.0 viii LIST OF Tables 1 Table 8-1 CS-BCMCS Control Protocol Message .48 2 Table 8-2 Message Type Values.54 3 Table 8-3 Definition of Mandatory, Conditional, Optional 54 4 Table 8-4 AddFlowRequest55 5 Table 8-5 AddFlowResponse .55 6 Table 8-6 ModifyFlowRequest.56 7 Table 8-7 ModifyFlowResponse 56 8 Table 8-8 RemoveFlowRequest .56 9 Table 8-9 RemoveFlowResponse .57 10 Table 8-10 RefreshKeyRequest57 11 Table 8-11 RefreshKeyResponse .57 12 Table 8-12 FlowInforma
