1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000672.2000(R2015) Bearer Independent Call Control (BICC) As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATI
2、S committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from desig
3、n and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generati
4、on Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit . AMERICAN NA
5、TIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substant
6、ial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The
7、 use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American Nat
8、ional Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards
9、 Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute requi
10、re that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer Forward bearer set-up 4-76 Figure F.11
11、/T1.672.4 - Forward call and bearer release; Backward bearer set-up 4-77 Figure F.12/T1.672.4 - Forward call release; Bearers not released. 4-77 Figure F.13/T1.672.4 - Forward call and bearer release; Gateway interworking between forward and backward bearer set-up . 4-78 Figure H.1/T1.672.4 CMN Func
12、tional model. 4-81 Chapter 7 (T1.672.7-2000) Figure 1/T1.672.7 - BICC Network Topology . 7-3 Figure 2/T1.672.7 BICC specification model. 7-5 Figure 3/T1.672.7 . 7-7 Figure 4/T1.672.7 . 7-7 Figure 5/T1.672.7 . 7-8 Figure 6/T1.672.7 . 7-8 Figure 7/T1.672.7 - Encapsulated Application Information field.
13、 7-13 Figure 8/T1.672.7 - Length indicator 7-14 Figure 9/T1.672.7 - Compatibility Information 7-14 Figure 10/T1.672.7 Action Indicator 7-16 Figure 11/T1.672.7 Backbone Network Connection Identifier. 7-17 Figure 12/T1.672.7 Interworking Function Address 7-18 Figure 13/T1.672.7 Codec List 7-18 Figure
14、14/T1.672.7 - Single Codec 7-19 Figure 15/T1.672.7 - Codec Information subfield . 7-19 Figure 16/T1.672.7 Coding for the 1 octet long configuration field 7-21 Figure 17/T1.672.7 BAT Compatibility Report. 7-23 Figure 18/T1.672.7 Diagnostics 7-24 Figure 19/T1.672.7 Bearer Network Connection Characteri
15、stics 7-24 Table of Tables Chapter 4 (T1.672.4-2000) Table 1/T1.672.4 BAT primitive interface 4-3 Table 2/T1.672.4 BAT primitive interface 4-8 Table B.1/T1.672.4 Primitives and parameters of the BICC Signalling Transport Sublayer . 4-46 Table C.1/T1.672.4 Message Transfer Part service primitives . 4
16、-50 Table C.2/T1.672.4 Primitives and parameters between the STC and layer management 4-51 Table C.3/T1.672.4 Parameters in the MTP-TRANSFER.request primitive 4-53 Table C.4/T1.672.4 Cause parameter mapping 4-54 Table D.1/T1.672.4 SSCOP primitives and parameters 4-59 Table D.2/T1.672.4 State transit
17、ion table 4-62 viii T1.672-2000 Chapter 7 (T1.672.7-2000) Table 1/T1.672.7 Primitives between AP and BICC SACF . 7-9 Table 2/T1.672.7 Contents of the BICC_Data Ind/Req primitive. 7-9 Table 3/T1.672.7 Contents of the BICC_Error Ind primitive 7-10 Table 4/T1.672.7 Mapping between BAT ASE and APM ASE p
18、rimitives . 7-10 Table 5/T1.672.7 Mapping between AP and BAT ASE primitives. 7-10 Table 6/T1.672.7 Mapping between BAT ASE and AP primitive 7-11 Table 7/T1.672.7 Mapping between APM ASE and BAT ASE primitives . 7-11 Table 8/T1.672.7 Mapping between EH ASE and BAT ASE primitives 7-11 Table 9/T1.672.7
19、 Primitives between BICC SACF and BAT ASE. 7-11 Table 10/T1.672.7 Contents of the APM_U_Data Ind/Req primitive. 7-13 Table 11/T1.672.7 Contents of the APM_U_Error Ind primitive 7-13 Table 12/T1.672.7 List of Identifiers 7-16 Table 13/T1.672.7 Coding of configuration fields 7-22 ix AMERICAN NATIONAL
20、STANDARD T1.672.1-2000American National Standard for Telecommunications Chapter 1 Functional Description of the Bearer Independent Call Control (BICC) Protocol 1 Scope This standard describes the adaptation of the narrowband ISDN User Part (ISUP) for the support of narrowband ISDN services independe
21、nt of the bearer technology and signalling message transport technology used. This standard is written as a set of exceptions to T1.113-2000. In some cases these exceptions are displayed by quoting the original text of T1.113-2000 with revision marks. (Deleted text is shown using strikeouts, and add
22、ed text is shown underlined.) The protocol defined by this standard is the call control protocol to be used between “Serving Nodes”. This protocol is called the “Bearer Independent Call Control” (BICC) protocol. Between Serving Nodes the control of bearers is provided by other protocols not specifie
23、d by this standard. Three types of Serving Node (SN) are defined: Interface Serving Node (ISN) Provides an interface to circuit switched networks. Transit Serving Node (TSN) Provides transit functionality, for call and bearer, within one network using the BICC protocol. Gateway Serving Node (GSN) Pr
24、ovides inter-network gateway functionality, for call and bearer, using the BICC protocol. The main body of this document defines the protocol at Transit Serving Nodes and Gateway Serving Nodes. The scope is thus as shown in Figure 1/T1.672.1. 1-1 T1.672.1-2000 Call Service Function (CSF) Bearer Cont
25、rol Function (BCF) Serving Node (SN) Call Control Signalling (BICC protocol) Call Control Signalling (BICC protocol) Bearer Control Signalling Bearer Control Signalling Bearer SCOPE OF THE MAIN BODY OF THIS STANDARD Figure 1/T1.672.1 - Scope of this Standard In defining the procedures for BICC at an
26、 Interface Serving Node, this standard also defines how BICC interworks with other protocols. These descriptions are contained in Annex E/T1.672.4 to this standard. This standard also contains Annex H/T1.672.4, of relevance to a Call Mediation Node, where call control functions may reside without an
27、y bearer control capability. 2 Normative References The following standards, and other references contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards and other references are su
28、bject to revision; all users of this standard are therefore encouraged to investigate the possibility of applying the most recent edition of the standards and other references listed below. T1.113-2000, American National Standard for Telecommunications Signaling System Number 7 (SS7) Integrated Serv
29、ices Digital Network (ISDN) User Part.1ITU-T Recommendation Q.115 (1997) Logic for the Control of Echo Control Devices.2T1.111-2000, American National Standard for Telecommunications Signaling System Number 7 (SS7) Message Transfer Part (MTP).1T1.637-1999, American National Standard for Telecommunic
30、ations B-ISDN ATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP).11T1 standards are available from the Alliance for Telecommunications Industry Solutions . 2ITU-T recommendations are available from the ITU Telecommunication Standardization Sector . 1-2 T1.672.1-2000 ITU-T R
31、ecommendation Q.2111 (12/99) Service Specific Connection Oriented Protocol in a Multi-link and Connectionless Environment (SSCOPMCE).2ITU-T Recommendation Q.1400 (1993) Architecture framework for the development of signaling and OA BCF-N, BCF-T, BCF-G and BCF-R. The BCF-N, BCF-T and BCF-G provide th
32、e control of the bearer switching function, the communication capability with its associated Call Service Function (CSF), and the signalling capability necessary for the establishment and release of the bearer to its peer. The BCF-R provides the control of the bearer switching function and relays th
33、e bearer control signalling requests to next BCF in order to complete the end-to-end bearer control signalling action. The BCF is not within the scope of this standard. 3.2 Bearer Inter-Working Function (BIWF): A functional entity which provides bearer control functions (BCF) and media mapping/switc
34、hing functions within the scope of a Serving Node (SN). A BIWF contains one BCF. 3.3 Call Mediation Node (CMN): A functional entity which provides CSF functionality without an associated BCF entity. 3.4 Call Service Function (CSF): Four types of CSF are defined: The Call Service Nodal Function (CSF-
35、N) provides the service control nodal actions associated with the narrow-band service by inter-working with narrowband and bearer independent signalling, signalling to its peer CSF the characteristics of the call, and invoking the Bearer Control Nodal Functions (BCF-N) necessary to transport the nar
36、row-band bearer service across the backbone network. The Call Service Transit Function (CSF-T) provides the service transit actions necessary to establish and maintain a backbone network call (see Figure 2/T1.672.1), and its associated bearer by relaying signalling between CSF peers and invoking the
37、 Bearer Control Transit Functions (BCF-T) necessary to transport the narrow-band bearer service across the backbone network. The Call Service Gateway Function (CSF-G) provides the service gateway actions necessary to establish and maintain a backbone network call and its associated bearer by relayin
38、g signalling between CSF peers and invoking the Bearer Control Gateway Functions (BCF-G) necessary to transport the narrow-band bearer service between backbone networks. The Call Service Co-ordination Function (CSF-C) provides the call co-ordination and mediation actions necessary to establish and m
39、aintain a backbone network call by relaying signalling between CSF peers. The CSF-C has no association with any BCF. It is only a call control function. 1-3 T1.672.1-2000 3.5 Constructor: An information element type, the contents of which consists of other information elements, as described in T1.67
40、2.7. 3.6 Gateway Serving Node (GSN): A functional entity which provides gateway functionality between two network domains. This functional entity contains the call service function (CSF-G), and one or more bearer inter-working functions (BIWF). GSNs interact with other GSNs, in other backbone networ
41、k domains and other ISNs and TSNs within its own backbone network domain. 3.7 Interface Serving Node (ISN): A functional entity which provides the interface with SCNs. This functional entity contains the call service nodal function (CSF-N), and one or more bearer inter-working functions (BIWF) which
42、 interact with the Switched Circuit Network (SCN) and its peers within the backbone network. 3.8 List of Supported Codecs: List of codecs conveyed between two SNs. It includes all the codecs that are supported from the SN initiating codec negotiation procedures up to the SN sending the message inclu
43、ding the list of codecs. 3.9 List of Available Codecs: This list contains all the codecs that can be used for the call set-up and in the active phase of the call. 3.10 Signalling Transport Layers (STL): Any suite of protocol layers currently specified to provide Transport and/or Network Layer servic
44、es to the BICC. Their functions, protocol and service primitives are outside the scope of this standard. 3.11 Serving Node (SN): A functional entity that is either an ISN, a GSN, or a TSN. 3.12 Signalling Transport Converter (STC): A protocol layer between the STL and BICC. This layer enables the BI
45、CC protocol to be independent of the STL being used. 3.13 Simple: An information element type, as described in T1.672.7. 3.14 Switching Node (SWN): A functional entity which provides the switching functions within the backbone core network. This functional entity contains a BCF-R. SWNs interact with
46、 other SWNs and BIWFs, within their own backbone network domain. 3.15 Switched Circuit Network (SCN): generic term for any network that uses circuit switching technology, i.e., ISDN, PSTN, PLMN. 3.16 Transit Serving Node (TSN): A functional entity which provides transit functionality between two ISN
47、s. This functional entity contains the call service function (CSF-T), and supports one or more bearer inter-working functions (BIWF). TSNs interact with other TSNs, GSNs and ISNs within their own backbone network domain. 1-4 T1.672.1-2000 4 Abbreviations Parameters; Identifiers; Information elements
48、; Messages; and 1-7 T1.672.1-2000 Methods/functions. Examples: Called Party Number parameter, Initial Address message, Backbone Network Connection Identifier information element. 2. The definition of a parameter value is written in italics and is put between quotation marks. Example: Nature of Addre
49、ss value 0000011 “national (significant) number.” 3. All message names are BICC messages unless explicitly stated otherwise. Example: The “IAM message” is the IAM message in BICC, whereas an IAM message in ISUP is referred to as an “ISUP IAM message.” 4. For the name and the type of a service primitive, the following applies: The name is capitalized; and The type is separated from the name by “.“ Example: BICC_Data.request primitive. NOTE - Where the text has been imported f
