1、 TIA-41.730-E (Revision of TIA-41.D) October 2010 Part 730: Wireless Radiotelecommunications Intersystem Operations WIN DistributedPlane and Model ANSI/TIA-41.730-E-2004 APPROVED: APRIL 20, 2004 REAFFIRMATION: SEPTEMBER 1, 2010 NOTICE TIA Engineering Standards and Publications are designed to serve
2、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 such S
3、tandards 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, either
4、 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 adopting the
5、 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 applicability of
6、regulatory limitations before its use. (From Standards Proposal No. 3-3590.730-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
7、 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.org/stan
8、dards/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 agreement. Fo
9、r 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 one or
10、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 expected t
11、o 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 preparation in a
12、ccordance 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, OWNED
13、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 REFERENCE T
14、O, 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 PARTICULA
15、R 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 APPLICABLE STAT
16、UTE, 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 BUSINESS,
17、 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 CONTENT
18、S HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-41-730-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960730-1 WIN DISTRIBUTED FUNCTIONAL MODELPART 7301 WIN DISTRIBUTED FUNCTIONAL MODELFigure 1 sho
19、ws the DFP model for WIN. This diagram depicts the functional entities andrelationships applicable to WIN. This diagram is based on the generic IN DFP model described inITU-T recommendation Q.1224. A general explanation of functional entities, relationships, and theITU IN DFP model are contained in
20、Q.1224.TIA-41-730-EWIN DISTRIBUTED FUNCTIONAL MODEL123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960730-2Figure 1 WIN Distributed Functional ModelFunctional modeling facilitates the development of information flows between the FEs in mode
21、lingnetwork functionality and services. This model has been developed to be non-service specific. It isa functional model and does not imply any limitations regarding physical implementations ordistribution of functions to physical platforms. Annex C provides an example mapping of these FEsto NEs. S
22、uch mapping facilitates the development of protocols between NEs.to any FESMAF SMF SCEFSDF SCF SRFSSFCCFCCFSCFRACFACFACFRACFRCFRTFLegendAuthentication Control Function Call Control Function Functional Entity Location Registration Function - HLR Location Registration Function - VLR Mobile Station Acc
23、ess Control Function Radio Access Control Function Radio Control Function Radio Terminal Function Service Creation Environment Function Service Control Function Service Data Function Service Management Access Function Service Management Function Specialized Resource Function Service Switching Functi
24、onACF CCF FE LRF LRF MACF RACF RCF RTF SCEF SCF SDF SMAF SMF SRF SSFHVLRFVLRFHMACFTIA-41-730-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960730-3 WIN Functional Model1.1 WIN Functional ModelThe WIN DFP is based on the DFP for IN CS-2.
25、The Authentication Control Function (ACF),Location Registration Function (LRF), Mobile Station Access Control Function (MACF), RadioAccess Control Function (RACF), Radio Control Function (RCF) and Radio Terminal Function(RTF) functional entities provide functionality specifically related to wireless
26、 access and mobility.Requirements for the Service Management Function (SMF), Service Creation EnvironmentFunction (SCEF) and Service Management Access Function (SMAF) functional entities and relatedinterfaces are for further study.1.2 WIN Functional EntitiesThe WIN functional entities provide the fo
27、llowing functionality:1.2.1 Authentication Control Function (ACF)The Authentication Control Function (ACF) provides the service logic and service data function toprovide authentication, voice privacy and signaling message encryption functions. The ACF:a. interacts with the SCF, LRFH, LRFV,RACF and o
28、ther ACF functional entities for theauthentication of mobile stationsb. maintains the authentication parameters for the MSc. authenticates the MS accessd. computes the voice privacy mask and signaling message encryption key for MS originationand page response accessese. updates the MSs authenticatio
29、n parametersf. provides trigger mechanisms to access WIN service logic (for further study)1.2.2 Call Control Function (CCF)The Call Control Function (CCF) provides call and service processing and control. The CCF:a. establishes, manipulates and releases call and connection as requested by the MACF,R
30、ACF, RCF and by other CCF functional entitiesb. provides the capability to associate and relate RCF functional entities, and other CCFfunctional entities that are involved in a particular call and/or connection instance (that maybe due to SSF requests)c. manages the relationship between RCF function
31、al entities and between other CCFfunctional entities involved in a call (e.g. supervises the overall perspective of the call andconnection)d. interacts with the MACF and RACF to establish an information exchange path (e.g., calldelivery, short message delivery) to an MSe. provides trigger mechanisms
32、 to access WIN functionality (e.g., passes events to the SSF)TIA-41-730-EWIN Functional Entities123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960730-41.2.3 Location Registration Functions (LRFH, LRFV)The Location Registration Function (LR
33、F) provides the service logic and service data function tomanage the mobility aspects for wireless users. There are two complementary LRF FEs: LRFHandLRFV.The LRFH:a. interacts with the LRFVand MACF1functional entities to maintain the location andactive/inactive status for mobile stationsb. maintain
34、s the subscriber profile (e.g., switch-based features, triggers) and interacts with theLRFVfunctional entity to transfer and update the subscriber profilec. interacts with the LRFVfunctional entity to provide a routing address for establishment ofan information exchange path (e.g., call delivery, sh
35、ort message delivery)d. interacts with the ACF functional entity to provide authentication, voice privacy andsignaling message encryption for mobile stations.e. maintains mobile station access information (e.g., SMS pending flag)f. provides trigger mechanisms to access WIN service logic at an SCF (f
36、or further study)The LRFV:a. interacts with the LRFHand MACF functional entities to maintain the location andactive/inactive status for mobile stationsb. stores the subscriber profile (e.g., switch-based features, triggers) and interacts with theLRFHand the MACF functional entities to transfer and u
37、pdate the subscriber profilec. interacts with the LRFHand the MACF functional entities to provide a routing address forestablishment of an information exchange path (e.g., call delivery, short message delivery)d. interacts with the ACF functional entity to provide authentication, voice privacy andsi
38、gnaling message encryption for mobile stationse. at the request of the LRFHfunctional entity, interacts with the MACFfunctional entity toprovide mobile station notification informationf. provides trigger mechanisms to access WIN service logic at an SCF (for further study)1.2.4 Mobile Station Access
39、Control Function (MACF)The Mobile Station Access Control Function (MACF) stores subscriber data and dynamicallyassociates system resources with a particular set of call instance data. The MACF:a. interacts with the LRFH2,LRFVand RACF functional entities to maintain the location andactive/inactive st
40、atus for mobile stations1This is for cases when the mobile station is in the home system.2This is for cases when the mobile station is in the home system.TIA-41-730-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960730-5 WIN Functional En
41、titiesb. stores the subscriber profile (e.g., switch-based features, triggers) and interacts with theSSF/CCF and with the LRFVfunctional entities to transfer and update the subscriber profilec. provides subscriber profile information (e.g., switch-based services, triggers) andauthorization informati
42、on to the CCF and RACF functional entitiesd. maintains the mobile station access information (e.g., SMS pending flag)e. interacts with the RACF and LRFVfunctional entities to provide a routing address forestablishment of an information exchange path (e.g., call delivery, short message delivery)to an
43、 MSf. interacts with the RACF functional entity to establish an information exchange path(e.g., call delivery, short message delivery) to an MSg. interacts with the RACF functional entity to verify the presence of the mobile stationh. at the request of the LRFVfunctional entity, interacts with the R
44、ACFfunctional entity toprovide mobile station notification informationi. interacts with the LRFVfunctional entity to provide the paging strategy to the RACFfunctional entity to verify the presence of the mobile stationj. provides trigger mechanisms to access WIN service logic (for further study)1.2.
45、5 Radio Access Control Function (RACF)The Radio Access Control Function (RACF) provides the service logic and service datafunctionality specifically related to the radio link. The RACF:a. interacts with the CCF, ACF, MACF, RCF and with other RACF functional entities in theprocessing of call, non-cal
46、l, or service related functionsb. interacts with the CCF and MACF to establish an information exchange path (e.g., calldelivery, short message delivery) to an MSc. interacts with the ACF to authenticate the MS accessd. interacts with the MACF to provide a routing address for establishment of an info
47、rmationexchange path (e.g., call delivery, short message delivery)e. manages the RCF functions for associated RCFsf. provides radio access control functions such as assignment of radio resourcesg. interacts with the associated RCF and with other RACF functional entities to coordinatehandoff activiti
48、es, including the determination of target RCFs, handoff decision andhandoff completionh. interacts with other RACF functional entities to process border cell operationsi. contains service logic functionality to handle service requests that are specific to radiobearer requirementsj. executes mobile s
49、tation pagingTIA-41-730-EWIN Functional Entities123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960730-61.2.6 Radio Control Function (RCF)The Radio Control Function (RCF) provides the radio port and radio port control. The RCF:a. establishes, manipulates and releases call/connection as “requested” by the RACF, CCF,and RTFb. provides radio functions including carrier generation, signal amplification, selectivefiltering, modulation and demodulation, radio channel assignment and supervisionc. provides interconnection between t
