ANSI TIA-41.290-E-2007 Mobile Application Part (MAP) C Intersystem Handoff Annex A《移动应用部分(MAP).系统内转接.附录A》.pdf

1、 TIA-41.290-E (Revision of TIA-41.290-D) February 2007Mobile Application Part (MAP) - Intersystem Handoff Annex A ANSI/TIA-41.290-E-2007 APPROVED: FEBRUARY 2, 2007 REAFFIRMED: JANUARY 10, 2013 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through elimina

2、ting 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 existence of such Standards and Publications shall not

3、 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 members, either domestically or internationally. S

4、tandards 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 parties adopting the Standard or Publication. This Stan

5、dard 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 applicability of regulatory limitations before its u

6、se. (From Project No. 3-3590.290-RV5-RF1, 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 be amended, modified or changed in the stand

7、ards 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 investigation for IPR. When IPR consisting o

8、f 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 investigate or inquire into, the scope or validi

9、ty 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-discriminatory. TIA does not warrant or represent

10、 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”) engaged in the formulation, development or publi

11、cation 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 any duty or obligation to search or investiga

12、te 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 applications shall apply; and (iii) Informati

13、on 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 Document. TIA does not certify, inspect, t

14、est 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 CONTENTS, ITS FITNESS OR APPROPRIATENESS F

15、OR 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 REGARDING THE CONTENTS COMPLIANCE WITH ANY AP

16、PLICABLE 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 INDIRECT, ARISING FROM OR RELATING TO ANY USE OF

17、 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 OF WARRANTY, TORT (INCLUDING NEGLIGENCE),

18、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-41.290-ERevision HistoryCopyright Telecommu

19、nications Industry Association 2006. All rights reserved.This document is subject to change.Revision Date RemarksTIA-41.290-E May 2006 Initial publication.TIA-41.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-1PART 290Annex A:

20、Additional DMH Support for Intersystem Handoff in MAP (normative)This Annex is normative and is considered part of this Specification.The Data Message Handler standard has some impact upon MAP. The changes which impact MAPIntersystem Operations are:1. Change segment numbering to include the tandem s

21、egments as well as the air timesegments.2. DMH requires the number of segments in a call be saved in the audit record. This infor-mation must be passed from the serving system to the anchor system upon call disconnect.These changes are detailed in the following stage 2 diagrams. Only the scenario st

22、eps which involveDMH related changes are described.d. If the Serving MSC (Anchor) opens a tandem segment, it increments the current segmentcounter and then passes that value in the FACDIR.Figure 1 Handoff-Forward (A to B)abcdefgMSC MSCConversationMSONCHHANDMREQhandmreqFACDIR (Seg=n+1)Open Tandem Seg

23、ment n+1Open Air Segment n+2facdirConversationClose Air Segment nA Anchor Serving BTarget TIA-41.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-2g. If the Anchor MSC had a tandem segment open, it should now close that segment.F

24、igure 2 Handoff-Back (B to A)abcdeghfAAnchor TargetBServingMSC MSCHANDMREQ handmreq handbackFACRELfacrel ConversationHANDBACK (Seg=n) Open Tandem Segment A-BClose Air Segment nClose Air Segment n+1ConversationTIA-41.290-E1234567891011121314151617181920212223242526272829303132333435363738394041424344

25、45464748495051525354555657585960290-3d. If the Serving MSC opens a tandem segment, it increments the current segment counter andthen passes that value in the FACDIR.Figure 3 Handoff-Forward (B to C)abcdegfAAnchor BServing CTarget Conversation HANDMREQ handmreq FACDIR (Seg=n+1) facdir MSONCH Conversa

26、tion MSC MSC MSC Open Tandem Segment n+1Open Air Segment n+2Close Air Segment nTIA-41.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-4g. If the Serving MSC opened a tandem segment, it should close it now. Figure 4 Handoff-Back

27、(C to B)abcdeghfAAnchor BTarget and Tandem CServing MSC MSC MSC ConversationHANDMREQ handmreq HANDBACK (Seg=n) handbackFACREL facrel Conversation Close Tandem Segment B-COpen Air Segment n+1Open Air Segment nTIA-41.290-E12345678910111213141516171819202122232425262728293031323334353637383940414243444

28、5464748495051525354555657585960290-5d. If the Anchor MSC opens a tandem segment, it increments the current segment counter andthen passes that value in the FACDIR.j. If the Serving MSC opened a tandem segment, it should close it now.Figure 5 Path Minimization (A-B to A-C)abcdegkfhijAAnchor CTarget B

29、Serving MSCMSCMSCConversation HANDMREQ handmreq HANDTHIRD (Seg=n)FACDIR (Seg=n+1) facdir handthird MSONCH FACREL facrel Conversation Open Tandem Segment n+1Open Air Segment n+2Close Air Segment n Close Tandem Segment A-B TIA-41.290-E1234567891011121314151617181920212223242526272829303132333435363738

30、39404142434445464748495051525354555657585960290-6b. When the Serving MSC detects that the MS has disconnected or has lost radio contact, itsignals the release of the facilities with a FACREL including the number of segmentscurrently allocated.d. When a Tandem MSC processes a FACREL containing the nu

31、mber of segments in aBillingID, it should relay that parameter toward the Anchor MSC.Figure 6 Release by the MS (C-B-A)abcdeMSCAAnchor BTarget CServing MSC MSC Conversation FACREL (Seg=n) facrel FACREL (Seg=n) facrel Open Tandem Segment A-B Close Tandem Segment B-C Close Audit Record (Seg=n+1) TIA-4

32、1.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-7b. When the Anchor MSC receives a disconnect request from the other party for a handed offMS, it should launch a FACREL and start a timer to wait for the response. If the timere

33、xpires, an indicator for an unknown number of segments can be used.c. When a Tandem MSC receives a FACREL from the Anchor MSC for a handed off MS, itshould launch a FACREL toward the Serving MSC and start a timer to wait for the response.If the timer expires, an indicator for an unknown number of se

34、gments can be used.Upon receipt of the FACREL the Serving MSC can release any facilities that it is using andclose out the current air segment DMH record. It confirms the release by sending a facrelto the Tandem MSC including the BillingID to convey the number of segments.d. When a Tandem MSC receiv

35、es a facrel from the Serving MSC for a handed off MS, itcan release any facilities that it is using and close out the current tandem segment DMHrecord. It confirms the release by sending a facrel to the Tandem MSC including theBillingID to convey the number of segments.e. When the Anchor MSC receive

36、s a facrel from the Tandem or Serving MSC for a handedoff MS, it can release any facilities that it is using and close out the current tandem segmentDMH record and the audit record for the call with the number of segments.Figure 7 Release by the other party (A-B-C)abcdeMSCAAnchor BTandem CServing MS

37、C MSC Conversation FACREL facrel (Seg=n) Close Tandem Segment A-B Close Audit Record (Seg=n+1) facrel (Seg=n) FACREL Close Tandem Segment B-C Close Air Segment C TIA-41.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-8a. This sc

38、enario occurs when an active call is disconnected by both the originating party andterminating party at about the same time.b. When the Anchor MSC receives a disconnect request from the other party for a handed offMS, it should launch a FACREL and start a timer to wait for the response. If the timer

39、expires, an indicator for an unknown number of segments can be used.When a Tandem MSC receives a FACREL from the Anchor MSC for a handed off MS, it should launch a FACREL toward the Serving MSC and start a timer to wait for the response.Upon receipt of the FACREL the Serving MSC can release any faci

40、lities that it is using andclose out the current air segment DMH record.The Serving MSC detects a disconnect request from the MS at about the same time andsends a FACREL toward the Anchor MSC with the number of segments. The Serving MSCis unaware that the other end is releasing simultaneously.c. Bot

41、h the Tandem and Serving MSCs will receive the FACREL before they receive afacrel.d. The Tandem MSC will send a facrel to the Serving MSC.Figure 8 Release GlareabcdgefAAnchor BTandem CServing MSC MSC MSCPSTN Conversation FACREL (Seg=n) facrel facrel (Seg=n)FACREL facrel (Seg=n) Close Tandem Segment

42、A-B Close Audit Record (Seg=n+1) FACRELClose Air Segment CClose Tandem Segment B-CTIA-41.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-9e. The Serving MSC will send a facrel to the Tandem MSC including the number ofsegments.f. The Tandem MSC sends the facrel to the Anchor MSC including the number ofsegments.TIA-41.290-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960290-10