TIA EIA-136-730-A-2002 TDMA Third Generation Wireless - Over-the-Air Programming Teleservice (OPTS) (ANSI APPROVED WITHDRAWN JUNE 12 2015)《TDMA第3代无线电通信 广播编程电信业务(OPTS)》.pdf

《TIA EIA-136-730-A-2002 TDMA Third Generation Wireless - Over-the-Air Programming Teleservice (OPTS) (ANSI APPROVED WITHDRAWN JUNE 12 2015)《TDMA第3代无线电通信 广播编程电信业务(OPTS)》.pdf》由会员分享，可在线阅读，更多相关《TIA EIA-136-730-A-2002 TDMA Third Generation Wireless - Over-the-Air Programming Teleservice (OPTS) (ANSI APPROVED WITHDRAWN JUNE 12 2015)《TDMA第3代无线电通信 广播编程电信业务(OPTS)》.pdf（42页珍藏版）》请在麦多课文档分享上搜索。

1、 ANSI/TIA/EIA-136-730-A-2002 APPROVED: APRIL 15, 2002 APPROVED: SEPTEMBER 17, 2013 WITHDRAWN: JUNE 12, 2015 TIA/EIA-136-730-A (Revision of TIA/EIA-136-730) April 2002TDMA Third Generation Wireless- Over-the-Air Programming Teleservice (OPTS) NOTICE TIA Engineering Standards and Publications are desi

2、gned 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 exist

3、ence 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-TIA m

4、embers, 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 partie

5、s 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 app

6、licability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. ANSI/TIA-PN-136.730-A-WD, formulated under the cognizan

7、ce 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 be amended, modified or changed in the standards development or any editing process. The use or practice of content

8、s 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 investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and cal

9、led 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 investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of

10、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-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have

11、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”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, r

12、ecommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assur

13、ance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the r

14、ecords 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 Document. TIA does not certify, inspect, test or otherwise investigate pr

15、oducts, 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 CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE,

16、 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 REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGUL

17、ATION, 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 INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN,

18、 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 OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE,

19、 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/EIA-136-730-A-2013 i Contents 1. Overview.2 1.1 Simplified Reference Model

20、 .2 1.2 Protocol Hierarchy3 2. Basic Operations 4 2.1 IRDB Download .4 2.2 Alpha Tag Download5 2.3 Sub-Band Priority Order Download .5 2.4 Additional IRDB Data Download.5 2.5 Security and Integrity of OPTS Downloads .5 2.6 Broadcast Management of OPTS6 2.7 Mobile Station OPTS Acknowledgments (Point-

21、to-Point)7 2.8 Mobile Station Default IRDB Data.8 3. OPTS Message Set .11 3.1 IRDB Download .12 3.2 Extended IRDB Download .13 3.3 Alpha Tag Download14 4. Information Element Description.15 4.1 Additional IRDB Data 15 4.2 Alpha Tag Data.16 4.3 Extended Remaining Length.18 4.4 Intelligent Roaming Dat

22、abase.18 4.4.1 Band Order Band 119 4.4.2 Band Order Band 220 4.4.3 Band Order Band 320 4.4.4 Band Order Band 420 4.4.5 Band Order Band 520 4.4.6 Band Order Band 620 4.4.7 Band Order Band 721 4.4.8 Band Order Band 821 4.4.9 Favored SID List21 4.4.10 Forbidden SID List.21 4.4.11 Favored SOC List.21 4.

23、4.12 Forbidden SOC List .21 4.4.13 IR Control Data Word22 4.4.14 NUM_CELLULAR Number of Cellular Probability Blocks24 4.4.15 NUM_FAVORED_SID Number of Favored SIDs.24 4.4.16 NUM_FAVORED_SOC Number of Favored SOCs 24 4.4.17 NUM_FORBIDDEN_SID Number of Forbidden SIDs .24 4.4.18 NUM_FORBIDDEN_SOC Numbe

24、r of Forbidden SOCs.24 4.4.19 NUM_PARTNER_SID Number of Partner SIDs.25 4.4.20 NUM_PARTNER_SOC Number of Partner SOCs 25 TIA/EIA-136-730-A-2013 ii 4.4.21 NUM_PCS Number of PCS Sub-bands 25 4.4.22 Partner SID List25 4.4.23 Partner SOC List.25 4.4.24 RESCAN_COUNT - Rescan Count.25 4.4.25 RESCAN_LOOP -

25、 Rescan Loop25 4.4.26 IRDB Version Data 26 4.5 Sub-band Priority Order26 4.6 Message Type28 4.7 Remaining Length.29 5. Change History for TIA/EIA-136-73030 TIA/EIA-136-730-A-2013 iii List of Figures Figure 1 Simplified OPTS Reference Model .2 Figure 2 OPTS Protocol Hierarchy 3 TIA/EIA-136-730-A-2013

26、 iv THIS PAGE INTENTIONALLY LEFT BLANK TIA/EIA-136-730-A-2013 1 Purpose and Scope 1 This section describes a teleservice that is designed to support downloading of non-NAM 2 programming information to an MS; an example of non-NAM programming information 3 is that information to support Intelligent R

27、oaming (IR). The Over-the-Air Programming 4 Teleservice (OPTS) provides a sequence of messages exchanged between the Over-the-5 Air Service Provisioning Function (OTAF) and the MS for the delivery of information. 6 OPTS is a Teleservice that can be performed either on a DTC or a DCCH. 7 Network supp

28、ort for OPTS is beyond the scope of this document and references to the 8 Over-the-Air Service Provisioning Function (OTAF) are only provided to aid in 9 describing the support of OPTS over the air interface. 10 TIA/EIA-136-730-A-2013 2 1. Overview 1 1.1 Simplified Reference Model 2 Figure 1 shows a

29、 simplified reference model used for a description of OPTS. 3 Figure 1 Simplified OPTS Reference Model 4 SmMS UmBMI OTAF*where: 5 MS: Mobile Station: A station used by the cellular subscriber to access 6 network services over an air interface. Mobile stations include portable 7 units, units installe

30、d in vehicles and fixed subscriber stations. 8 BMI: Base Station/Mobile Switching Center/Interworking Function: A 9 base station provides the means for mobile stations to access network 10 services using radio. An MSC is connected to at least one base station, 11 and may use inter-working functions

31、to connect to other networks. 12 OTAF: Over-the-Air Service Provisioning Function: Description of this 13 network entity is beyond the scope of this document, but is provided to 14 assist implementers. It may include a single network entity, or a 15 collection of network entities that facilitates th

32、e IR feature. The OTAF 16 provides the service provider with a means of controlling the over-the-air 17 programming information sent to mobile stations. 18 Note: For some of the operations, the OTAF will require connection to 19 other network entities, such as Home Location Registers, but these 20 e

33、ntities, and their inter-connections are beyond the scope of this 21 document. 22 Sm:Reference point Smis a vendor specific interface between the mobile 23 station and the user. 24 TIA/EIA-136-730-A-2013 3 Um: Reference point Umis the traffic and signaling interface between the BS 1 and MS, which co

34、rresponds to the air interface. This reference point is 2 defined in TIA/EIA-136. 3 : Reference points identified as * are beyond the scope of this document, 4 and may be vendor specific. 5 1.2 Protocol Hierarchy 6 OPTS transports messages between the MS and the BMI using the R-DATA message 7 where

35、the Higher Layer Protocol Identifier indicates OPTS (See TIA/EIA-136-123). 8 OPTS messages may be delivered via point-to-point or broadcast mechanisms. 9 The OPTS protocol hierarchy is depicted in Figure 2. 10 Figure 2 OPTS Protocol Hierarchy 11 OPTS OPTSOPTS MessagesR-DATA R-DATAIWFMSBMI OTAFReceiv

36、eSendTIA/EIA-136 Air Interface*TSARTSARSegmentation and Reassembly, if required*beyond the scope of this document. 12 TIA/EIA-136-730-A-2013 4 2. Basic Operations 1 2.1 IRDB Download 2 An IRDB Download or an Extended IRDB Download message is sent to the mobile 3 station whenever the Intelligent Roam

37、ing Database (IRDB) is to be updated in the mobile 4 station. The information contained within the IRDB Download or Extended IRDB 5 Download is used by the mobile station for selecting a suitable control channel during 6 DCCH Scanning and Locking procedures. There are no application layer 7 acknowle

38、dgments defined in OPTS. Such acknowledgements have not been defined due 8 to traffic considerations on both the TIA/EIA-136 air link and TIA/EIA-41 transport 9 network. A Layer 3 acknowledgment (R-DATA ACCEPT or R-DATA REJECT) is 10 sufficient to serve as an application layer response, i.e., the mo

39、bile station will verify that 11 the IRDB is received and stored correctly prior to sending the R-DATA ACCEPT (see 12 Section 3.6). 13 The mobile station will reply to an IRDB Download or an Extended IRDB Download 14 message via a Layer 3 R-DATA ACCEPT or R-DATA REJECT. Multiple R-DATAs 15 may be us

40、ed to accommodate all the information that is to be downloaded, with 16 segmentation via Teleservice Segmentation and Reassembly (TSAR) applied by the 17 OTAF. 18 The IRDB Download or Extended IRDB Download message includes the entire 19 information element as defined in Section 5. The entire IRDB i

41、s downloaded to a mobile. 20 There is no support for partial downloads, or changes to fields within a table. If a 21 modification to the table occurs (for example, a change in the status of a SID), then the 22 entire IRDB is downloaded to the mobile, and the mobile overwrites the existing IRDB 23 wi

42、th the new data. The reasons and frequency for changing the IRDB are carrier specific 24 and not subject to standardization. 25 The IRDB version may be provided when an IRDB is delivered via point-to-point 26 transport mechanisms, and shall be provided when an IRDB is delivered via the 27 broadcast

43、transport mechanism. A mobile station that has a currently stored IRDB that 28 includes version information shall overwrite its current IRDB if a newer version is 29 detected and the security rules defined in Section 2.5 are met. A newer version is 30 identified by either of the following occurrence

44、s: (1) The IRDB Version provided via 31 OPTS is greater than the currently stored IRDB Version in the mobile station. (2) The 32 IRDB Version provided via OPTS is less than the currently stored IRDB Version in the 33 mobile station by 215or more. A mobile station that has a currently stored IRDB tha

45、t 34 does not include version information shall always overwrite the current IRDB with a new 35 versioned or unversioned IRDB if the security rules of Section 2.5 are met. A mobile 36 station that has a currently stored IRDB that includes version information shall always 37 overwrite the current IRD

46、B with an unversioned IRDB if the security rules of Section 2.5 38 are met. 39 TIA/EIA-136-730-A-2013 5 2.2 Alpha Tag Download 1 An Alpha Tag Download is sent to the mobile station whenever the alpha tags are to be 2 updated in the mobile station. An alpha tag is displayed by the mobile station when

47、 3 obtaining service on a control channel of a Home, Partner, Favored, or Neutral service 4 provider. 5 The mobile station will reply to an Alpha Tag Download via a Layer 3 R-DATA 6 ACCEPT or R-DATA REJECT. The downloading of Alpha Tags are supported by an 7 OPTS Alpha Tag Download message. 8 An Alp

48、ha Tag Download includes the entire information element as defined in Section 5. 9 There is no support for partial download of select fields within this element. The reasons 10 and frequency for changing the alpha tags are carrier specific and not subject to 11 standardization. 12 2.3 Sub-Band Prior

49、ity Order Download 13 Sub-Band Priority Order is an optional information element in the IRDB Download and 14 Extended IRDB Download messages, and is sent to the mobile station whenever the Sub-15 Band Priority Order is to be updated in the mobile station. 16 A Sub-Band Priority Order includes the entire information element as defined in 17 Section 5. There is no support for partial download of select fields within this element. 18 The reasons and frequency for changing the Sub-Band Priority Order are carrier specific 19 and not subject to s