1、 TIA-41.790-E (Revision of TIA-41.D) October 2010 Part 790: Wireless Radiotelecommunications Intersystem Operations Annexes ANSI/TIA-41.790-E-2004 APPROVED: APRIL 20, 2004 REAFFIRMATION: SEPTEMBER 1, 2010 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest thr
2、ough 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 existence of such Standards and Publicatio
3、ns 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 members, either domestically or intern
4、ationally. 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 parties adopting the Standard or Publicatio
5、n. 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 applicability of regulatory limitations
6、before its use. (From Standards Proposal No. 3-3590.790-RV5, formulated under the cognizance of the TIA TR-45.2 Subcommittee on Wireless Intersystem Technology.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2002 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.
7、S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org/standards/search_n_order.cf
8、m All rights reserved Printed in U.S.A. PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the TIA and may not be reproduced without permission. Organizations may obtain permission to reproduce a limited number of copies through entering into a license agreement. For information, contact:
9、 Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 U.S.A. or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 NOTICE OF DISCLAIMER AND LIMITATION OF LIABILITY The document to which this Notice is affixed has been prepared by one or more Engineering Commit
10、tees of the Telecommunications Industry Association (“TIA”). TIA is not the author of the document contents, but publishes and claims copyright to the document pursuant to licenses and permission granted by the authors of the contents. TIA Engineering Committees are expected to conduct their affairs
11、 in accordance with the TIA Engineering Manual (“Manual”), the current and predecessor versions of which are available at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm. TIAs function is to administer the process, but not the content, of document preparation in accordance with the Manu
12、al and, when appropriate, the policies and procedures of the American National Standards Institute (“ANSI”). 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.
13、 TIA MAKES NO SEARCH OR INVESTIGATION FOR IPR. WHEN IPR CONSISTING OF PATENTS AND PUBLISHED 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 OB
14、LIGATION TO INVESTIGATE OR INQUIRE INTO, THE SCOPE OR VALIDITY OF ANY CLAIMS OF IPR. 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 M
15、ERCHANTABILITY AND ITS NON-INFRINGEMENT 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 REGULATION
16、. 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, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIG
17、ATION, 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 NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CON
18、TENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-41-790-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960790-1 IntroductionPART 790Annex A: Call Delivery Using the BCSMNote: The content of this annex has be790n changed f
19、orm IS-771 annex B.This annex is informative and is not considered part of this standard.This annex describes how MS-to-MS call delivery can be modeled using the WIN Basic Call StateModels (BCSMs). The message sequences shown in this annex are as in TIA-41. A.1 IntroductionThis annex illustrates how
20、 the BCSMs interact with TIA-41 signaling to complete an MS-to-MS callinvolving two WIN subscribers. Not all of the information exchanges that take place between half-call segments in the same WIN MSC are shown. Details of trunk signaling have been minimized.This annex uses extended signaling messag
21、e flow diagrams to illustrate how TIA-41 messages mayinteract with the BCSMs. The following conventions are used in the BCSM and TIA-41 interactiondiagrams:Mapping TIA-41 signaling to a BCSM should not be viewed as a specific requirement forimplementation.A.2 ScopeThis Annex describes the following
22、call delivery scenarios:a. normal MS - MS call delivery, with both MSs served by the same MSC (see Figure 4 )b. normal MS - MS call delivery, with MSs served by different Serving MSCs (see Figure 5)These scenarios provide guidance on the intended functioning of the call model with respect toTIA/EIA-
23、41 intersystem operations.A.3 TIA-41 Signaling for MS-MS CallFigures 1 and 2 below illustrate the basic TIA-41 information flows to support an MS-to-MS call.Both the calling and called parties are WIN subscribers whose trigger profile information is sent totheir respective serving systems upon regis
24、tration confirmation. This is shown for the calling partyin Figure 1. The subscriber profile will cause a trigger to be armed in the O-BCSM that causes theMSC/SSF to launch a WIN query (ORREQ) during call setup. Associated with the armed trigger isthe address to which the ORREQ is to be sent. (The O
25、RREQ is typically sent to an SCP, but theORREQ may also be sent to the subscribers HLR.) The SCP performs service logic processing andANS-41Intersystem OperationInternal Network Entity IndicationTrunk SignalingTIA-41-790-ETIA-41 Signaling for MS-MS Call12345678910111213141516171819202122232425262728
26、2930313233343536373839404142434445464748495051525354555657585960790-2returns information in the orreq instructing the MSC to proceed with the call. Note that servicelogic processing may involve the exchange of additional messages, such as SRFDIR, between theORREQ and the orreq; these are not illustr
27、ated.Figure 1 TIA-41 Registration and “Call From” SignalingCall setup continues, and the call is delivered to the Originating MSC. The message sequence inFigure 2 illustrates the subsequent message exchange that may occur for a WIN subscriber, withoptional messages shown in the shaded boxes.On deter
28、mining the call is to a mobile subscriber, the MSC/SSF sends a LOCREQ to the HLR, withthe TRANSCAP and WINCAP parameters set to indicate the capabilities of the MSC/SSF, such aswhether the MSC/SSF is capable of handling WIN triggers and if it is capable of sending asubsequent LOCREQ message. If a se
29、rvice is to be executed in an SCP, the HLR may send aSERVREQ message requesting the SCP to execute a service. Upon receipt of the servreq, theHLR may send a ROUTREQ to obtain a TLDN. A second SERVREQ may then be sent to the SCPfor further service processing after the routreq is received. The locreq
30、is then returned to theMSC/SSF. Note that this locreq may contain destination information, trigger profile information,or both. In the case where the locreq has returned trigger profile information only, this is used to armdetection points in the BCSM at the O-MSC. Upon encountering an armed detecti
31、on point andsatisfying associated criteria, the MSC/SSF sends an ANLYZD to the Network Entity (NE)address associated with the trigger, typically an SCP, to invoke a service. In this example,instructions returned in the anlyzd provide information to proceed with call processing. Uponencountering the
32、Location trigger and satisfying the conditions, a second LOCREQ is sent toMS HLR SCPServing SystemMSC VLRorreq RoutingInfocall setupREGNOTregnot Profile, TRIGADDRLISTregnot Profile, TRIGADDRLISTORREQ MIN, TRIGTYPE, TRANSCAP, WINCAP, DGTSDIALMS originationRNT RNTabcdefghREGNOTORTTIA-41-790-E123456789
33、101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960790-3 TIA-41 Signaling for MS-MS Callthe HLR with the TRIGTYPE parameter set to indicate the Location trigger was encounteredand thereby requesting routing information. The HLR proceeds to obtain de
34、stinationinformation and to pass this information back to the MSC/SSF in the second locreq. In the case where locreq has returned both trigger profile information and destinationinformation together, both pieces of information are used by the MSC/SSF. The triggerinformation is used to arm detection
35、points in the BCSM at the O-MSC later in the call; thedestination information is used to deliver the call.After call setup, call processing continues, and further calls to service logic are performed whenarmed detection points are encountered and appropriate criteria are satisfied.TIA-41-790-ENormal
36、 Intrasystem Call Delivery123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960790-4Figure 2 TIA-41 “Call To” SignalingA.4 Normal Intrasystem Call DeliveryFor this scenario, the calling and called MSs are in the same MSC. The Originating MSC
37、determinesthat the destination is an MS and proceeds with normal TIA-41 call delivery.MSC SCP VLRServing SystemOriginating SystemMSCHLRLOCREQ DGTSDIAL, TRIGTYPESERVREQ SRVIDservreq ACTCODElocreq TRIGADDRLISTROUTREQ MINroutreq TLDNRRTroutreq TLDNRRTROUTREQ MINANLYZD TRIGTYPEcall setupROUTREQ MINroutr
38、eq TLDNlocreq TERMLISTroutreq TLDNROUTREQ MINRRT RRTLOCREQ DGTSDIAL, TRIGTYPEANZTLRTLRTijklbcdefghnopqrstcall originationTLDNATSVRTSVRTSERVREQ SRVIDservreq ACTCODETLDNATmaanlyzd ACTCODETIA-41-790-E1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
39、57585960790-5 Normal Intrasystem Call DeliveryA.4.1 TIA-41 Signaling for Normal Intrasystem Call DeliveryCD Invocation to an idle, Local MS in Chapter 3 of TIA-41-E describes call delivery invocation toan idle MS that is served by the MSC where the call originates.A.4.2 Call SegmentsThe following fi
40、gure illustrates the call segments for this intrasystem call delivery scenario.Figure 3 Call Segments for Intrasystem MS to MS Call A.4.3 BCSM and TIA-41 InteractionsFigure 4 illustrates the BCSM and TIA-41 interactions for normal call delivery invocation to an idleMS that is served by the MSC where
41、 the call originates.Originating MSCCallingMS(MS1)Called MS(MS2)T-BCSM1O-BCSM1TIA-41-790-ENormal Intrasystem Call Delivery123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960790-6Figure 4 BCSMs for Normal Intrasystem Call Delivery (1 of 2)Or
42、iginating / Serving SystemHLRabcdhMSCAuth_Call_LOCREQ DGTSDIAL ecalloriginatiMS 1 MS 2Send_CallPagePagegfT_AlertingO_AlertingT_ActiveO_Activealertingansweransweranswercall setuplocreq TERMLIST LRTTIA-41-790-E12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505
43、1525354555657585960790-7 Normal Intersystem Call DeliveryFigure 4 BCSMs for Normal Intrasystem Call Delivery (2 of 2)Notes:a. MS 1 sends an indication that it wishes to originate a call. (Dialed digits are included in thecall origination indication.) The MSC assigns a radio channel to MS 1. The MSC
44、authorizesthe call origination and arms originating triggers for the subscriber. MSC call processing(via O-BCSM1) progresses through the Collect_Information PIC and the dialed digits areanalyzed.b. The MSC determines that this call is to a MS served by this MSC and selects an internalroute (internal
45、 to the MSC) for the call. The originating MSC initiates terminating callprocessing (via instantiation of T-BCSM1) on behalf of that MS (MS 2).c. The Mobile_Termination trigger is detected at the Termination_Attempt DP. The MSCsends a LOCREQ to the HLR.d. The HLR determines that the subscriber is cu
46、rrently served by the Originating MSC, andsends a locreq to the Originating MSC. The TERMLIST parameter is set to indicateLocal Termination.e. The Originating MSC, recognizing itself as the Serving MSC and that the call is a localtermination, initiates procedures to set up the call to the MS. It det
47、ermines that the MStermination is authorized.f. The MSC pages MS 2. MS 2 responds and is assigned to a voice channel.g. MS 2 is alerted. T-BCSM1transits to the T_Alerting PIC and notifies O-BCSM1.O BCSM1transits to the O_Alerting PIC.h. MS 2 answers the call. T-BCSM1transits to the T_Active PIC and
48、notifies O-BCSM1.O BCSM1transits to the O_Active PIC.i. MS 1 disconnects. O-BCSM1transits to the O_Null PIC and notifies T-BCSM1. T-BCSM1transits to the T_Null PIC.A.5 Normal Intersystem Call DeliveryFor this scenario, the calling and called MSs are in different MSCs. The Originating MSCdetermines t
49、hat the destination is an MS and proceeds with normal TIA-41 call delivery.ireleasereleasereleaseOriginating / Serving SystemMSCMS 1 MS 2T_ActiveO_ActiveTIA-41-790-ENormal Intersystem Call Delivery123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960790-8A.5.4 TIA-41 Signaling for Normal Intersystem Call DeliveryCD Invocation to an Idle MS or Another MSC in Chapter 3 of TIA-41 describes call deliveryinvocation to an idle MS that is outside the serving area of the MSC where
