TIA TSB105-1999 Clarification of Audit Order with Forced Re-Registration in Pre-TIA EIA-136-A Implementation《在TIA EIA-136-A执行前的带强行再注册的审计顺序的澄清》.pdf

《TIA TSB105-1999 Clarification of Audit Order with Forced Re-Registration in Pre-TIA EIA-136-A Implementation《在TIA EIA-136-A执行前的带强行再注册的审计顺序的澄清》.pdf》由会员分享，可在线阅读，更多相关《TIA TSB105-1999 Clarification of Audit Order with Forced Re-Registration in Pre-TIA EIA-136-A Implementation《在TIA EIA-136-A执行前的带强行再注册的审计顺序的澄清》.pdf（5页珍藏版）》请在麦多课文档分享上搜索。

1、- R 3234bO0 0610508 b42 TIA/EIA TELECOMMUNICATIONS SYSTEMS BULLETIN Clarification of Audit Order with Forced Re-Regis t ration in Pr e-TI A/EH A-1 3 64 Implement at ion TSBIOS MARCH 1999 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Elrctronic Industri- Alliance NOTICE WEIA Engineering Standards and Publi

2、cations are 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 his particular n

3、eed. Existence of such Standards and miblications shall not in any respect preclude any member or nonmember of WEIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by tho

4、se other than TIA/= members, whether the standard is to be used either domestically or internationally. Standards, miblications and Bulletins are adopted by EU in accordance with the American National Standards Institute (ANSI) patent policy. By such action, WEIA does not assume any liability to any

5、 patent owner, nor does it assume any obligation whatever to parties adopting the Standard, Publication, or Bulletin. Technical Bulletins are distinguished from TAEA Standards or Interim Standards, in that they contain a compilation of engineering data or infomation useful to the technical community

6、, and represent approaches to good engineering practices that are suggested by the formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly represent good engineehg practice, or that may be acceptable to, or have been accepted by, appropriate bod

7、ies. Parties who wish to bring other approaches to the attention of the formulating committee to be considered for inclusion in future revisions of this Bulletin are encouraged to do so. It is the intention of the formulating committee to revise and update this Bulletin from time to time as may be o

8、ccasioned by changes in technology, industry practice, or government regulations, or for other appropriate reasons. (From Project No. 440, formulated under the cognizance of the TLA “R-45.3 Subcommittee on Time Division Digital Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 1999 S

9、tandards and Technology Department 250 Wilson Boulevard Arlington, VA 22201 PRICE: Please refer to the current Catalog of EM, JEDEC and TIA STANDARDS and ENGINEERING PUBLICATIONS International (303-397-7956) or call Global Engineering Documents, USA and Canada (1-800-854-7179) All rights reserved Pr

10、inted in U.S.A. 3234bOO Ob10510 ZTT I TSB-105 Clarification of Audit Order with Forced Re-Registration in Pre-TINEIA-136-A Implementations o Table of Contents i 1. STATEMENT OF PROBLEM 1 2 2. PROPOSED SOLUTION . 2 3 4 I 3234b00 ObLOSLL L3b O 1. Statement of 9 10 11 12 13 14 15 16 17 18 19 P 21 P 23

11、24 25 26 n 28 29 3) 31 32 33 34 35 36 37 38 39 40 47 48 49 TSB-105 Clarification of Audit Order with Forced Re-Registration in Pre-TINEIA-136-A Implementations Problem A mobile station in the DCCH Camping state receives a PCH message and invokes the Termination procedure (see TIA/EIA-136-123 Section

12、 3.3 and Section 4.4). The mobile station determines that the PCH message is an Audit Order addressed to it and issues an RDCCH Request primitive containing an Audit Confirmation message along with any other coincidental messages required. According to TIA/EIA- 136-123 Section 8, the only message th

13、at can be concatenated with the Audit Confirmation is the MACA Report. Still executing the Termination procedure, the mobile station checks the Forced Re-Registration flag of the Audit Order. If the Forced Re- Registration Flag is enabled, then the mobile station invokes the Registration procedure (

14、see TIAEIA-136 Section 4.7). Within the Registration procedure, the mobile station (1) formulates a Registration message with a Forced indication, (2) issues an RDCCH Request primitive containing this message, an Audit Conf-mtion message, and any other coincidental messages required, and (3) enters

15、the Registration Proceeding state. According to TINEIA-136-123 Section 8, the Audit Confirmation message cannot be concatenated with the Registration message. As described in TIA/EIA-136-123, the receipt of an Audit Order with the Forced Re-Registration flag set should result in the mobile station i

16、ssuing three separate RDCCH Request primitives, and therefore three RACH bursts. The first RDCCH Request primitive, issued from within the Termination procedure, contains an Audit Confirmation message with any other Coincidental messages that are allowed to be concatenated with the primary message.

17、The second RDCCH Request primitive, issued from within the Registration procedure, contains a Registration message with any other coincidental messages that are allowed to be concatenated with the primary message. The third RDCCH Request primitive, also issued from within the Registration procedure,

18、 contains a second Audit Confirniation message with any other coincidental messages that are allowed to be concatenated with the primary message. The first and third RDCCH Request primitives contain redundant information. Changes made to the mobile station procedures in TIAEIA-136-123-A remove the n

19、eed for the issuance of the third RDCCH Request primitive. The redundancy described in MIA-136-123 resulted in multiple interpretations of the procedures associated with the receipt of an Audit Order with the Forced Re-Registration flag set. Three mobile station implementations are known to exist: 1

20、. Issue one RDCCH Request primitive, with the Audit Confirmation as the primary message and the Registration as a secondary message, along with any other coincidental messages required. This interpretation results in one RACH burst, but violates the message concatenation rules of TIAEIA-136-123 Sect

21、ion 8. 2. Issue one RDCCH Request primitive, with the Registration as the primary message and the Audit Confnnation as a secondary message, along with any other coincidental messages required. 1 O 1 9 10 11 12 13 14 15 16 17 18 19 P 21 P P 24 2s 26 27 s TSB-105 Clarification of Audit Order with Forc

22、ed Re-Registration in Pre-TIAEIA-136-A Implementations 2. Proposed This interpretation also results in one RACH burst, and also violates the message concatenation rules. 3. Issue two RDCCH Request primitive, the first with the Audit Confiition as the primary message and the second with the Registrat

23、ion as the primary message. This interpretation results in two RACH bursts, but does not smctly follow TIAEIA-136- 123 because the third RACH burst is not sent. However, this is the correct interpretation for mobile stations following TIMIA-136- 123-A. The BMI must support all three pre-TIA/EIA-136-

24、A mobile station implementations, in addition to an implementation based on the strict interpretation of TIMIA-136-123 that requires the mobile station to send three RACH bursts. Solution When a BMI issues an Audit Order with the Forced Re-Registration flag set, it shall accept any of the following

25、responses from pre- TIMIA-136-A compiiant mobile stations: 1. One RACH burst, with the Audit Confirmation as the primary message and the Registration as a secondary message, along with any other coincidental messages required. 2. One RACH burst, with the Registration as the primary message and the A

26、udit Confinnation as a secondary message, along with any other coincidental messages required. 3. Two RACH bursts, the first with the Audit Confirmation as the primary message and the second with the Registration as the primary message. 4. Three RACH bursts, the first and third with the Audit Confirmation as the primary message and the second with the Registration as the primary message.