1、 TIA-1112-2008 APPROVED: OCTOBER 1, 2008 REAFFIRMED: SEPTEMBER 19, 2013 TIA-1112 October 2008X.S0050-0 v1.0 Session Initiation Protocol (SIP) to ISDN User Part (ISUP) Interworking NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunder
2、standings 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 in any respe
3、ct 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. Standards and
4、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 Standard does not
5、 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 use. (From Pro
6、ject No. PN-3-0254-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 standards development o
7、r 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 of patents and publ
8、ished 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 validity of any claims o
9、f 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 that procedures o
10、r 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 publication of standard
11、s (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 investigate the records of
12、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) Information as to claims of
13、 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, test or otherwise i
14、nvestigate 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 FOR A PARTICULAR PU
15、RPOSE 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 APPLICABLE STATUTE,
16、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 THE CONTENTS CONT
17、AINED 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), PRODUCT LIABILITY
18、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. X.S0050-0 v1.0 i Session Initiation Protocol (SIP) to ISDN User P
19、art (ISUP) Interworking 1 Contents 2 List of Figures.vi 3 List of Tablesviii 4 Forewordx 5 1 Scope1 6 2 References1 7 3 Definitions and Abbreviations4 8 3.1 Definitions 4 9 3.2 Abbreviations4 10 4 General .5 11 4.1 General Interworking Overview .5 12 5 Network Characteristics .6 13 5.1 Key Character
20、istics of ISUP-based CS Networks 6 14 5.2 Key Characteristics of IM CN Subsystem 6 15 6 Interworking with CS Networks.6 16 6.1 Interworking Reference Model.6 17 6.1.1 Interworking Reference Points and Interfaces 6 18 6.1.2 Interworking Functional Entities 7 19 6.1.2.1 Void.7 20 6.1.2.2 Media Gateway
21、 Control Function (MGCF) 7 21 6.1.2.3 IP Multimedia - Media Gateway Function (IM-MGW) 7 22 6.2 Control Plane Interworking Model .7 23 6.3 User Plane Interworking Model7 24 7 Control Plane Interworking7 25 7.1 General .8 26 7.2 Interworking between CS Networks Supporting ISUP and the IM CN Subsystem8
22、 27 7.2.1 Services Performed by Network Entities in the Control Plane .8 28 7.2.1.1 Services Performed by the SS7 Signalling Function.8 29 7.2.1.2 Void.9 30 7.2.1.3 Services of the MGCF.9 31 7.2.1.4 Services of the SIP Signalling Function 9 32 7.2.2 Signalling Between Network Entities in the Control
23、 Plane 9 33 7.2.2.1 Signalling Between the SS7 Signalling Function and the MGCF .9 34 7.2.2.2 Signalling Between the MGCF and SIP Signalling Function9 35 7.2.3 SIP-ISUP protocol interworking.9 36 7.2.3.1 Incoming Call Interworking from SIP to ISUP at I-MGCF 9 37 X.S0050-0 v1.0 ii 7.2.3.1.1 Sending o
24、f IAM 9 1 7.2.3.1.2 Coding of the IAM10 2 7.2.3.1.2.1 Called Party Number 10 3 7.2.3.1.2.2 Nature of Connection Indicators.11 4 7.2.3.1.2.3 Forward Call Indicators11 5 7.2.3.1.2.4 Calling Partys Category.12 6 7.2.3.1.2.5 User Service Information12 7 7.2.3.1.2.6 Calling Party Number.14 8 7.2.3.1.2.7
25、Generic Address .16 9 7.2.3.1.2.8 Void17 10 7.2.3.1.2.9 Original Called Number .17 11 7.2.3.1.2.10 Redirecting Number .18 12 7.2.3.1.2.11 Redirection Information .18 13 7.2.3.1.2.11a Jurisdiction Information .19 14 7.2.3.1.2.12 Hop Counter (National Option)19 15 7.2.3.1.2.12a Transit Network Selecti
26、on19 16 7.2.3.1.3 Sending of COT 20 17 7.2.3.1.4 Receipt of ACM20 18 7.2.3.1.5 Receipt of CPG .21 19 7.2.3.1.5a Receipt of ANM21 20 7.2.3.1.6 Sending of the Release message (REL) 21 21 7.2.3.1.7 Coding of the REL 22 22 7.2.3.1.8 Receipt of the Release Message23 23 7.2.3.1.9 Receipt of RSC, GRS or CG
27、B (H/W Oriented) 25 24 7.2.3.1.10 Autonomous Release at I-MGCF25 25 7.2.3.1.11 Internal Through Connection of the Bearer Path 25 26 7.2.3.2 Outgoing Call Interworking from ISUP to SIP at O-MGCF .25 27 7.2.3.2.1 Sending of INVITE.25 28 7.2.3.2.2 Coding of the INVITE 26 29 7.2.3.2.2.1 REQUEST URI Head
28、er26 30 7.2.3.2.2.2 SDP Media Description27 31 7.2.3.2.2.3 P-Asserted-Identity From and Privacy Header Fields .30 32 7.2.3.2.2.4 History-Info Header33 33 7.2.3.2.2.5 Max Forwards Header 35 34 7.2.3.2.3 Receipt of CONTINUITY.35 35 7.2.3.2.4 Sending of ACM and Awaiting Answer Indication 36 36 7.2.3.2.
29、5 Coding of the ACM.37 37 7.2.3.2.5.1 Backward call indicators 37 38 7.2.3.2.6 Sending of the Call Progress Message (CPG).38 39 7.2.3.2.7 Coding of the CPG38 40 7.2.3.2.7.1 Event Information.38 41 7.2.3.2.7a Receipt of 200 OK (INVITE) .38 42 7.2.3.2.8 Sending of the Answer Message (ANM) 38 43 7.2.3.
30、2.9 Coding of the ANM 39 44 7.2.3.2.9.1 Backwards Call Indicators39 45 7.2.3.2.10 Void 39 46 7.2.3.2.11 Void 39 47 7.2.3.2.12 Receipt of Status Codes 4xx, 5xx or 6xx 39 48 7.2.3.2.12.1 Void41 49 7.2.3 2.13 Receipt of a BYE 41 50 7.2.3.2.14 Receipt of the Release Message41 51 7.2.3.2.15 Receipt of RS
31、C, GRS or CGB (H/W Oriented) 41 52 7.2.3.2.16 Autonomous Release at O-MGCF 41 53 7.2.3.2.17 Special Handling of 580 Precondition Failure Received in Response to 54 Either an INVITE or UPDATE.42 55 X.S0050-0 v1.0 iii 7.2.3.2.17.1 580 Precondition Failure Response to an INVITE .42 1 7.2.3.2.17.2 580 P
32、recondition Failure Response to an UPDATE within an 2 Early Dialog42 3 7.2.3.2.18 Sending of CANCEL 42 4 7.2.3.2.19 Receipt of SIP Redirect (3xx) Response.42 5 7.2.3.3 Timers43 6 7.3 Void 43 7 7.4 Supplementary Services43 8 7.4.1 Calling Line Identification Presentation/Restriction (CLIP/CLIR) 43 9
33、7.4.2 COLP/COLR 43 10 7.4.3 Void 44 11 7.4.4 Void 44 12 7.4.5 Void 44 13 7.4.6 Call Forwarding Busy (CFB)/ Call Forwarding No Reply (CFNR) / Call Forwarding Unconditional 14 (CFU)44 15 7.4.7 Call Deflection (CD).44 16 7.4.8 Explicit Call Transfer (ECT) 44 17 7.4.9 Call Waiting44 18 7.4.10 Call Hold.
34、44 19 7.4.10.1 Session Hold Initiated from the IM CN Subsystem Side 44 20 7.4.10.2 Session Hold Initiated from the CS Network Side 45 21 7.4.11 Void 46 22 7.4.12 Void 46 23 7.4.13 Void 46 24 7.4.14 Conference Calling (CONF) / Three-Party Service (3PTY).46 25 7.4.15 Void 47 26 7.4.16 Void 47 27 7.4.1
35、7 Multi-Level Precedence and Pre-emption (MLPP).47 28 7.4.18 Void 47 29 7.4.19 Void 47 30 7.4.20 Void 47 31 7.4.21 User-to-User Signalling (UUS).47 32 7.4.22 Void 47 33 7.4.23 Void 47 34 7.5 Void 47 35 8 User Plane Interworking.47 36 8.1 Void 47 37 8.2 Interworking between IM CN Subsystem and TDM-ba
36、sed CS Network.47 38 8.3 Transcoding Requirements .48 39 9 MGCF IM-MGW Interaction48 40 9.1 Overview 48 41 9.2 Mn Signalling Interactions .48 42 9.2.1 Network Model.49 43 9.2.2 Basic IM CN Subsystem Originated Session49 44 9.2.2.1 Void.49 45 9.2.2.2 Void.49 46 9.2.2.3 ISUP 49 47 X.S0050-0 v1.0 iv 9.
37、2.2.3.1 IM-MGW Selection 49 1 9.2.2.3.2 IM CN Subsystem Side Termination Reservation 49 2 9.2.2.3.3 IM CN Subsystem Side Session Establishment 50 3 9.2.2.3.4 CS Network Side Circuit Reservation.50 4 9.2.2.3.5 Through-Connection .50 5 9.2.2.3.6 Continuity Check 50 6 9.2.2.3.7 Codec Handling.50 7 9.2.
38、2.3.8 Voice Processing Function50 8 9.2.2.3.9 Failure Handling in MGCF .51 9 9.2.2.3.10 Message Sequence Chart.51 10 9.2.3 Basic CS Network Originated Session53 11 9.2.3.1 Void.53 12 9.2.3.2 Void.53 13 9.2.3.3 ISUP 53 14 9.2.3.3.1 IM-MGW Selection 53 15 9.2.3.3.2 CS Network Side Circuit Reservation.
39、53 16 9.2.3.3.3 IM CN Subsystem Side Termination Reservation 53 17 9.2.3.3.4 IM CN Subsystem Side Session Establishment 53 18 9.2.3.3.5 Called Party Alerting 53 19 9.2.3.3.6 Called Party Answer .54 20 9.2.3.3.7 Through-Connection .54 21 9.2.3.3.8 Continuity Check 54 22 9.2.3.3.9 Codec Handling.54 23
40、 9.2.3.3.10 Voice Processing Function54 24 9.2.3.3.11 Failure Handling in MGCF .54 25 9.2.3.3.12 Message Sequence Chart.54 26 9.2.3.4 Handling of Forking 56 27 9.2.3.4.1 Detection of Forking .56 28 9.2.3.4.2 IM CN Subsystem Side Session Establishment 56 29 9.2.3.4.3 IM CN Subsystem Side Session Esta
41、blishment Completion.57 30 9.2.3.4.4 Message Sequence Chart.57 31 9.2.4 Session Release Initiated from IM CN Subsystem Side .60 32 9.2.4.1 Void.60 33 9.2.4.2 ISUP 60 34 9.2.4.2.1 Session Release in the IM CN Subsystem Side 60 35 9.2.4.2.2 Session Release in the CS Network Side 60 36 9.2.4.2.3 Messag
42、e Sequence Chart.60 37 9.2.5 Session Release Initiated from CS Network Side.61 38 9.2.5.1 Void.61 39 9.2.5.2 ISUP 61 40 9.2.5.2.1 Session Release in the CS Network Side 61 41 9.2.5.2.2 Session Release in the IM CN Subsystem Side 61 42 9.2.5.2.3 Message Sequence Chart.61 43 9.2.6 Session Release Init
43、iated by MGCF .62 44 9.2.6.1 Void.62 45 9.2.6.2 ISUP 62 46 9.2.6.2.1 Session Release in the CS Network Side 62 47 9.2.6.2.2 Session Release in the IM CN Subsystem Side 62 48 9.2.6.2.3 Message Sequence Chart.62 49 9.2.7 Session Release Initiated by IM-MGW 62 50 9.2.7.1 Void.62 51 X.S0050-0 v1.0 v 9.2
44、.7.2 ISUP 62 1 9.2.7.2.1 Session Release in the CS Network Side 62 2 9.2.7.2.2 Session Release in the IM CN Subsystem Side 63 3 9.2.7.2.3 Message Sequence Chart.63 4 9.2.8 Handling of RTP Telephone Events .64 5 9.2.8.1 Void.64 6 9.2.8.2 Sending and Receiving DTMF Digits Inband to/from CS CN (ISUP)64
45、 7 9.2.9 Session Hold Initiated from IM CN Subsystem65 8 9.2.9.1 Hold Request.65 9 9.2.9.2 Resume Request 65 10 9.2.9.3 Message Sequence Chart.65 11 9.2.10 Session Hold Initiated from CS Network .66 12 9.2.10.1 Message Sequence Chart.67 13 X.S0050-0 v1.0 vi List of Figures 1 Figure 1 IM CN subsystem
46、 to CS network logical interworking reference model6 2 Figure 2 Control plane Interworking between CS Networks Supporting ISUP and the IM CN Subsystem .8 3 Figure 3 Receipt of an Invite Request (Continuity Procedure Supported in the ISUP Network)10 4 Figure 4 Receipt of an Invite request (continuity
47、 procedure not supported in the ISUP network)10 5 Figure 5 Sending of COT 20 6 Figure 6 The Receipt of ACM (“Subscriber Free”).20 7 Figure 7 The Receipt of ACM (BCI other than “Subscriber Free”) 21 8 Figure 8 Receipt of CPG (Alerting).21 9 Figure 9 Receipt of ANM21 10 Figure 10 Receipt of the Bye me
48、thod22 11 Figure 11 Receipt of Cancel method .22 12 Figure 12 Receipt of an IAM (En Bloc Signalling in CS network).26 13 Figure 13 Receipt of COT (Success).36 14 Figure 14 Sending of ACM (Receipt of first 180 ringing) 36 15 Figure 15 Sending of ACM (Ti/w2elapses) 36 16 Figure 16 Sending of ACM (Rece
49、ipt of 183 Session Progress) 37 17 Figure 17 Sending of CPG (Alerting)38 18 Figure 18 Sending of ANM.38 19 Figure 19 Receipt of Status Codes 4xx, 5xx or 6xx 39 20 Figure 20 Receipt of BYE Method41 21 Figure 21 Receipt of COT (Failure). .42 22 Figure 22 Receipt of SIP Response Code 3xx.42 23 Figure 23 Session hold/resume initiated from the IM CN subsystem side45 24 Figure 24 Session Hold/Resume Initiated from the CS Network Side46 25 Figure 25 IM CN Subsystem to TDM-based CS network User Plane Protocol Stack 48 26 Figure 26 Network model49 27 Figure 27 Basic IM CN Subsystem Originating
