1、 TIA-41.700-E (Revision of TIA-41.D) October 2010 Part 700: Wireless Radiotelecommunications Intersystem Operations Introduction to WIN Functional Plane ANSI/TIA-41.700-E-2004 APPROVED: APRIL 20, 2004 REAFFIRMATION: SEPTEMBER 1, 2010 NOTICE TIA Engineering Standards and Publications are designed to
2、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 existence of
3、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 members,
4、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 parties adopti
5、ng 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 applicabili
6、ty of regulatory limitations before its use. (From Standards Proposal No. 3-3590.700-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 Bou
7、levard Arlington, VA 22201 U.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.or
8、g/standards/search_n_order.cfm 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 agreeme
9、nt. For information, contact: 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 o
10、ne or more Engineering Committees 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 expe
11、cted to conduct their affairs 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 preparatio
12、n in accordance with the Manual 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,
13、OWNED BY ONE OR MORE PARTIES. 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 REFER
14、ENCE TO, AND DISCLAIMS ANY OBLIGATION 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 PAR
15、TICULAR PURPOSE OR USE, ITS MERCHANTABILITY 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 APPLICABL
16、E STATUTE, RULE OR REGULATION. 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 BUS
17、INESS, LOSS OF PROFITS, LITIGATION, 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 C
18、ONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-41-700-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960700-1 INTRODUCTIONPART 7001 INTRODUCTIONThe Wireless Intelligent Network (WIN) is a ne
19、twork which supports the use of intelligent networkcapabilities to provide seamless terminal services, personal mobility services, and advanced networkservices in the mobile environment. 700 Intelligent network capabilities are all those functionalcapabilities which support creation and execution of
20、 service logic programs which reside outside ofswitching equipment, but work in collaboration with the switching equipment based upon a commondefinition of call models and protocols. These service logic programs may utilize data resources andphysical resources which also reside outside of the switch
21、ing equipment.Terminal mobility services are services created using intelligent network capabilities to servecustomers with mobile terminals. A set of these services will be associated with each mobileterminal based on the capabilities of the terminal and subscription selections. Some prerequisites
22、ofproviding these services are the abilities to identify and authenticate the terminal and to provideseamless operations capabilities between wireless and wireline networks.Personal mobility services are services created using intelligent network capabilities to servecustomers who are mobile. A set
23、of these services will be associated with each customer based onpersonal subscription selections. The customer may utilize a variety of mobile and fixed terminalsat different locations. Some prerequisites of providing these services are the abilities to: identify and authenticate the person (subscri
24、ber) who has been provisioned for the service provide seamless operations capabilities among the wireless, fixed and other networks(e.g., broadband, internet, data networks) provide a unique set of services to the subscriber based on the subscribers access point to theWIN serviceAdvanced network ser
25、vice has the functionality to identify the capability of the serving network, toprovide service based on the network and terminal capability, and to provide seamless servicemobility between wireless and wireline networks.The basic difference between terminal mobility service, personal mobility servi
26、ce, and advancednetwork service is as follows: Terminal mobility services: services based on the terminal capability irrespective of theterminal user. Personal mobility services: services based on personal needs or business entity needsirrespective of terminals or networks. Advanced network services
27、: customized services which can be provided ubiquitously in homeor roaming networks (wireless or wireline).Service management functionality is used to provision and manage the service control functionality,the service data functionality, and the specialized resource functionality in the network. Ser
28、vicecreation functionality is used to create services. Service management and service creationfunctionality may use standardized interfaces. However, the ability of a service subscriber to interactdirectly with subscriber-specific service management information will not be excluded orconstrained for
29、 WIN.TIA-41-700-EOBJECTIVE123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960700-2Initial WIN standards describe a distributed functional plane (DFP) architecture, call models, andadvanced network services such as calling name presentation
30、capabilities, voice controlled services,and incoming call screening services. Future WIN standards will add additional WIN capabilitiesand functionality.1.1 OBJECTIVEThe DFP defines the WIN architecture in terms of functional entities (FEs), each of which performsdistinct actions in the network. A g
31、rouping of actions across one or more FEs, when coordinated bycommunication flows, provides the required WIN service execution.The WIN DFP provides a different view of the network than is provided by the wireless networkreference model (NRM). The NRM defines network entities and the associated inter
32、face referencepoints that may logically comprise a wireless network. The WIN DFP identifies FEs that performdistinct actions in the network. Multiple FEs can be included in a single network entity.1.2 SCOPEThis part of TIA-41 defines the distributed functional plane (DFP) for the Wireless Intelligen
33、tNetwork (WIN).Specifically, the scope of this part of the Standard is:1. To define the WIN functional entities and the relationships applicable to WIN.2. To specify a high level model description of call control function (CCF) activities requiredto establish and maintain communication paths for use
34、rs.3. To specify a high level model description of service switching function (SSF) activitiesrequired for interaction between the CCF and a service control function (SCF).4. To specify WIN triggers and provide a high level model description of detection pointprocessing.5. To describe mobility manag
35、ement and radio access control functions in the context ofWIN.6. To illustrate how the WIN basic call state models interact with TIA-41 signaling.TIA-41-700-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960700-3 WIN DISTRIBUTED FUNCTIONA
36、L PLANE2 WIN DISTRIBUTED FUNCTIONAL PLANEThe distributed functional plane (DFP) for the Wireless Intelligent Network (WIN) is based on theITU-T Q.1224 recommendation for IN CS-2. The DFP defines the WIN architecture in terms offunctional entities (FEs), each of which performs distinct actions in the
37、 network. A grouping ofactions across one or more FEs, when coordinated by communication flows, provides the requiredWIN service execution.The WIN DFP provides a different view of the network than is provided by the wireless networkreference model (NRM). The NRM defines network entities and the asso
38、ciated interface referencepoints that may logically comprise a wireless network. The WIN DFP identifies FEs that performdistinct actions in the network. Multiple FEs can be included in a single network entity.2.1 Scope of WIN Distributed Functional PlaneThe scope of the DFP architecture for WIN is d
39、riven by the requirements of desired wireless servicesand is constrained by the capabilities of the embedded base of evolvable network technology.The functions required to support the desired wireless services include: end user access to call and service processing service invocation and control end
40、 user interaction with service control service managementThe scope of each of these functions is described below.2.1.1 End User AccessEnd user access to call and service processing will be provided via the following accessarrangements: line interfaces that are provided by radio access systems tradit
41、ional trunk and SS7 interfaces other types of network access arrangements such as roamer ports2.1.2 Service Invocation and ControlCall and service processing for WIN builds upon the call processing infrastructure of existing MSCs.It does so by using a generic model of existing call control functiona
42、lity to process basic two-partycalls, then adding service switching functionality to invoke and manage WIN service logic. Onceinvoked, WIN service logic is executed under the control of service control functionality inconjunction with service data functionality. With this distributed approach to cal
43、l and serviceprocessing, the existing call control functionality retains ultimate responsibility for the integrity ofcalls, as well as for the control of call processing resources.The following call and service processing constraints apply for WIN:TIA-41-700-EScope of WIN Distributed Functional Plan
44、e123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960700-4a. Call control and service switching functionality are tightly coupled in the MSC, thus therelationship between SSF and CCF is not standardized.b. A call is either between two or mor
45、e end users that are external to the network andaddressable via a directory number or combination of directory number and bearercapability, or a call is between one or more end users and the network itself.c. A call may be initiated by an end user, or by an SCF within the network on behalf of an end
46、user. To supplement a call, WIN service logic may either be invoked by an end user servedby a WIN MSC, or by the network on behalf of an end user.d. A call may span multiple MSCs. As such, each MSC only controls the portion of the callin that MSC. Call processing is functionally separated between MS
47、Cs. WIN service logicinvoked on WIN MSCs in such an inter-MSC call are managed independently by each WINMSC.e. MSCs can be viewed as having two functionally separate sets of call processing logic thatcoordinate call processing activities to create and maintain a basic two-party call. Thisfunctional
48、separation is provided between the originating portion of the call and theterminating portion of the call. This functional separation should be maintained in a WINMSC to allow WIN service logic invoked on the originating portion of the call (i.e. onbehalf of the calling party) to be managed independ
49、ently of WIN service logic invoked onthe terminating portion of the call (i.e. on behalf of the called party).f. It is desirable to allow multiple WIN-supported service logic instances to besimultaneously active for a given end user. It is also recognized that non-WIN service logicwill continue to exist in the network. As such, service feature logic instances mechanismsfor WIN should: determine which service logic to invoke for a given service request. This mechanismshould select the appropriate WIN-supported service logic or non-WIN-supportedservice logic, and block t
