1、 TIA STANDARD Circuit Services Notification Application Specification for cdma2000TIA-1110 September 2007 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance NOTICE TIA Engineering Standards and Publications are
2、designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The e
3、xistence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-T
4、IA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards 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 pa
5、rties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the
6、 applicability of regulatory limitations before its use. (From Project No. 3-0252-1, formulated under the cognizance of the TIA TR-45 Mobile (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 b
7、e 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 search or i
8、nvestigation 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 to inves
9、tigate 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-discri
10、minatory. 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”) engag
11、ed 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 disclaims an
12、y 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 patent ap
13、plications 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 of the
14、 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 OF THE
15、 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 WARRANTIES RE
16、GARDING 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 OR INDIR
17、ECT, 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, BREACH
18、 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 LIMITATIONS. TIA-
19、1110 CONTENTS i FOREWORD. vi 1 NOTES vii 2 REFERENCES. vii 3 1 Overview .1-1 4 1.1 Scope of This Document.1-1 5 1.2 Requirements Language .1-1 6 1.3 Architecture Reference Model.1-1 7 1.4 Protocols .1-2 8 1.4.1 Interfaces 1-2 9 1.4.2 States1-3 10 1.5 Terms1-3 11 1.6 Notation 1-4 12 2 3G1X Circuit Se
20、rvices Notification Application 2-1 13 2.1 Introduction2-1 14 2.1.1 General Overview2-1 15 2.1.2 Public Data .2-1 16 2.2 Data Encapsulation for the InUse Instance of the Application.2-1 17 2.3 Protocol Initialization2-1 18 2.3.1 Protocol Initialization for the InConfiguration Application Instance.2-
21、1 19 2.4 Procedures and Messages for the InConfiguration Instance of the 3G1X 20 Circuit Services Notification Application.2-2 21 2.4.1 Procedures2-2 22 2.4.2 Commit Procedures.2-2 23 2.4.3 Message Formats 2-3 24 2.4.3.1 ConfigurationRequest .2-3 25 2.4.3.2 ConfigurationResponse.2-3 26 2.5 3G1X Circ
22、uit Services Notification Protocol2-4 27 2.5.1 Overview .2-4 28 2.5.2 Primitives2-4 29 2.5.2.1 Commands2-4 30 2.5.2.2 Return Indications2-4 31 2.5.3 Protocol Data Unit 2-4 32 TIA-1110 CONTENTS ii 2.5.4 Procedures and Messages for the InUse Instance of the Protocol 2-4 1 2.5.4.1 Procedures 2-4 2 2.5.
23、4.1.1 General Requirements 2-4 3 2.5.4.1.2 Access Terminal Requirements. 2-5 4 2.5.4.1.2.1 Transmission and Reception of LAC Encapsulated PDUs. 2-5 5 2.5.4.1.2.2 Processing a 3G1XParameters Message 2-6 6 2.5.4.1.2.3 Processing a 3G1XParametersReset Message. 2-6 7 2.5.4.1.3 Access Network Requirement
24、s 2-6 8 2.5.4.1.3.1 State Independent Requirements . 2-7 9 2.5.4.1.3.2 Inactive State Requirements. 2-8 10 2.5.4.1.3.3 Idle Tunnel State Requirements . 2-8 11 2.5.4.1.3.4 Connected State Requirements 2-9 12 2.5.4.1.3.4.1 Processing of a 1x Service Redirection Message . 2-10 13 2.5.4.1.3.4.2 Processi
25、ng of a 1x (MEID) Universal Handoff Direction 14 Message 2-10 15 2.5.4.1.3.4.3 Transmission of a 1x Service Redirection Message 2-11 16 2.5.4.1.3.4.4 Transmission of a 1x (MEID) Universal Handoff Direction 17 Message 2-11 18 2.5.4.2 Message Formats 2-11 19 2.5.4.2.1 3G1XServices 2-11 20 2.5.4.2.2 3G
26、1XServicesAck 2-12 21 2.5.4.2.3 3G1XParameters. 2-13 22 2.5.4.2.4 3G1XParametersAck. 2-28 23 2.5.4.2.5 3G1XParametersReset 2-28 24 2.5.4.2.6 3G1XParametersResetAck 2-29 25 2.5.4.2.7 AttributeUpdateRequest . 2-29 26 2.5.4.2.8 AttributeUpdateAccept . 2-30 27 2.5.4.2.9 AttributeUpdateReject 2-30 28 2.5
27、.5 Interface to Other Protocols 2-30 29 2.5.5.1 Commands 2-30 30 2.5.5.2 Indications 2-31 31 2.6 Configuration Attributes of the 3G1X Circuit Services Notification Application 2-31 32 TIA-1110 CONTENTS iii 2.6.1 Simple Attributes2-31 1 2.6.2 Complex Attributes.2-32 2 2.6.2.1 AllowedReverseLinkMessag
28、es Attribute .2-32 3 2.6.2.2 AllowedForwardLinkMessages Attribute.2-34 4 2.6.2.3 ServiceOptionIdle attribute.2-35 5 2.6.2.4 ServiceOptionConnected Attribute .2-36 6 2.6.2.5 BurstTypeIdle Attribute 2-37 7 2.6.2.6 BurstTypeConnected Attribute .2-38 8 2.6.2.7 OrderCodeReverse Attribute .2-39 9 2.6.2.8
29、OrderCodeForward Attribute 2-40 10 2.7 Session State Information 2-41 11 2.7.1 3G1XParameters.2-41 12 2.7.2 ProtocolState Parameter .2-42 13 TIA-1110 FIGURES iv Figure 1.3-1. Architecture Reference Model 1-2 1 Figure 2.5.4.1.3-1. 3G1X Circuit Services Notification Protocol State Diagram 2 (Access Ne
30、twork) 2-7 3 TIA-1110 TABLES v Table 2.6.1-1. Configurable Values2-32 1 Table 2.7.1-1. The Format of the Parameter Record for the 3G1XParameters 2 Parameter.2-41 3 Table 2.7.2-1. The Format of the Parameter Record for the ProtocolState Parameter2-42 4 TIA-1110 FOREWORD vi (This foreword is not part
31、of this Standard) 1 This standard was prepared by Technical Specification Group C of the Third Generation 2 Partnership Project 2 (3GPP2). This standard is evolved from and is a companion to the 3 cdma20001standards. This air interface standard provides 3G1X Circuit Services 4 Notification services.
32、 5 6 1“cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in th
33、e United States.” TIA-1110 REFERENCES vii The following documents contain provisions, which, through reference in this text, 1 constitute provisions of this document. References are either specific (identified by date of 2 publication, edition number, version number, etc.) or non-specific. For a spe
34、cific 3 reference, subsequent revisions do not apply. For a non-specific reference, the latest 4 version applies. In the case of a reference to a 3GPP2 document, a non-specific reference 5 implicitly refers to the latest version of that document in the same Release as the present 6 document. 7 8 1 T
35、IA-2000.2, Physical Layer Standard for cdma2000 Spread Spectrum Systems. 9 2 TIA-2000.5, Upper Layer (Layer 3) Signaling Specification for cdma2000 Spread 10 Spectrum Systems. 11 3 TSB-58, Administration of Parameter Value Assignments for cdma2000 Spread 12 Spectrum Standards. (informative reference
36、) 13 4 TIA-2000.4, Signaling Link Access Control (LAC) standard for cdma2000 Spread 14 Spectrum Systems. 15 5 TIA-1082, Mobile Station Equipment Identifier (MEID) Support for cdma2000 16 Spread Spectrum Systems. 17 6 TIA-856, cdma2000 High Rate Packet Data Air Interface Specification. 18 TIA-1110 RE
37、FERENCES viii No text. 1 2 Overview TIA-1110 1-1 1 OVERVIEW 1 1.1 Scope of This Document 2 These technical requirements form a compatibility standard for 3G1X Circuit Services 3 Notification services on cdma2000 high rate packet data systems. These requirements 4 ensure that a compliant access termi
38、nal can obtain service through any access network 5 conforming to this standard. These requirements do not address the quality or reliability 6 of that service, nor do they cover equipment performance or measurement procedures. 7 This specification is primarily oriented toward requirements necessary
39、 for the design and 8 implementation of access terminals. As a result, detailed procedures are specified for 9 access terminals to ensure a uniform response to all access networks. Access network 10 procedures, however, are specified only to the extent necessary for compatibility with 11 those speci
40、fied for the access terminal. 12 This specification includes provisions for future service additions and expansion of system 13 capabilities. The architecture defined by this specification permits such expansion without 14 the loss of backward compatibility to older access terminals. 15 1.2 Requirem
41、ents Language 16 Compatibility, as used in connection with this standard, is understood to mean: Any 17 access terminal can obtain service through any access network conforming to this 18 standard. Conversely, all access networks conforming to this standard can service access 19 terminals. 20 “Shall
42、” and “shall not” identify requirements to be followed strictly to conform to the 21 standard and from which no deviation is permitted. “Should” and “should not” indicate 22 that one of several possibilities is recommended as particularly suitable, without 23 mentioning or excluding others, that a c
43、ertain course of action is preferred but not 24 necessarily required, or that (in the negative form) a certain possibility or course of action 25 is discouraged but not prohibited. “May” and “need not” indicate a course of action 26 permissible within the limits of the standard. “Can” and “cannot” a
44、re used for statements 27 of possibility and capability, whether material, physical, or causal. 28 1.3 Architecture Reference Model 29 The architecture reference model is presented in Figure 1.3-1. The reference model 30 consists of the following functional units: 31 TIA-1110 Overview 1-2 UmAccess T
45、erminalSectorAccess Network1 Figure 1.3-1. Architecture Reference Model 2 The access terminal, the access network, and the sector are formally defined in Section 3 1.5. 4 The reference model includes the air interface between the access terminal and the access 5 network. The protocols used over the
46、air interface are defined in this document. 6 1.4 Protocols 7 1.4.1 Interfaces 8 This standard defines a set of interfaces for communications between protocols in the 9 same entity and between a protocol executing in one entity and the same protocol 10 executing in the other entity. 11 In the follow
47、ing the generic term “entity” is used to refer to the access terminal and the 12 access network. 13 Protocols in this specification have four types of interfaces: 14 Headers and messages are used for communications between a protocol executing in 15 one entity and the same protocol executing in the
48、other entity. 16 Commands are used by a protocol to obtain a service from another protocol within the 17 same access network or access terminal. 18 Indications are used by a protocol to convey information regarding the occurrence of 19 an event to another protocol within the same access network or a
49、ccess terminal. Any 20 protocol can register to receive these indications. 21 Public Data is used to share information in a controlled way between 22 protocols/applications. Public data is shared between protocols/applications in the 23 same layer, as well as between protocols/applications in different layers. The public 24 data of the InUse protocol/application is created when an InUse instance of a 25 protocol/application is created. All configurable attributes of the InConfiguration 26 instance of a protocol or application are also public data of that protocol o
