1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.2763 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Broadband ISDN - B-ISDN application protocols for the network signalling Signalling System No. 7 B-ISDN User Part (B-ISUP) - Formats and codes ITU-T Recomm
2、endation Q.2763 (Formerly CCITT Recommendation) ITU-T Q-SEMES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN CLAUSES APPLICABLE TO ITU-T STANDARD SYSTE
3、MS SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING
4、 SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INlbLLIGENT NETWORK SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 BROADBAND ISDN General aspects Signalling ATM adaptation layer (SAAL) Signalling network protocols Common aspects of B-ISDN application protocols
5、 for access signalling and network signalling and interworking Q. 1-4.3 4.4-4.59 4.60-4.99 Q. 100-Q. 1 19 Q. 120-4.249 4.250-4.309 4.3 10-4.399 Q.40CrQ.499 4.500-4.599 Q .60 b) message type code; c) message length; d) message compatibility information; e) message content. A description of the variou
6、s message parts is given in the following subclauses. Routing label Message type code Message length Message compatibility information Message content Figure UQ.2763 - B-ISDN User Part message format 5.1 Routing label The format and codes used for the routing label are described in 2.2Q.704. For eac
7、h ATM virtual connection the same routing label must be used for each message that is transmitted for that connection. The SLS value is allocated on a cyclic basis per signalling association, e.g. values of a cyclic 4-bit counter incremented for each new signalling association. A counter is required
8、 for each allocated OPC/DPC/NI combination. 5.2 Message compatibility information The message compatibility information consists of a one-octet field and is mandatory for all messages. The message compatibility information defines the behaviour of a switch if the message is not understood. 5.3 Messa
9、ge type code The message type code consists of a one-octet field and is mandatory for all messages. The message type code uniquely defines the function and format of each B-ISDN User Part message. The allocation with reference to the appropriate descriptive clause of this Recommendation is summarize
10、d in Table 1. Table 1/Q.2763 - Message type codes Message type Address complete Answer Application transport Blocking Blocking acknowledgement Call progress Call transfer Connection available (Note) Confusion Consistency check request Consistency check request acknowledgement Consistency check end C
11、onsistency check end acknowledgement Facility Forward transfer Identification request Identification response Initial address IAM acknowledgement IAM reject Loop prevention Modi acknowledgement Reference (Table) 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Code O000 o1 10 O000 1001 O10
12、0 O001 O001 O011 O001 O101 O010 1100 O011 1001 O011 1101 O010 1111 O000 O101 O001 O001 O001 o111 O001 1000 O01 1001 1 O000 1000 O011 O110 O011 o111 O000 O001 O000 1010 O000 1011 o 100 O000 O011 1010 Table 1/4-2763 - Message type codes (concluded) Message type Modifi reject Modify request Network res
13、ource management Pre-release information Release Release complete Reset Reset acknowledgement Resume Segmentation (national use) Subsequent address Suspend Unblocking Unblocking acknowledgement User Part available User Part test User-to-user information Reserved, used in N-ISUP Reserved, used in N-I
14、SUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Il II II Il Reserved, used in N-ISUP for future extensions Reserved for extension of name code Reference (Table) 25 26 27 36 28 29 6 7 32 30 31 32 6 7 33 34 35 Code O011 1
15、011 O011 1100 0011 O010 O100 O010 O000 1 100 O001 O000 O001 O010 O000 1111 O000 1110 O011 1000 O000 O010 O000 1101 O001 O100 O001 O110 O011 O101 O011 O100 O010 1101 O000 O01 1 O000 O100 O000 o1 11 O001 1001 to O010 1011 O010 11 10 O011 O000 O011 O001 O100 O01 1 1000 O000 1111 1111 NOTE - The former
16、name of the message was Modi% Confirm. Existing procedures are not influenced by this editorial change. However, this message may be used in additional procedure(s). 5.4 Message length The message length consists of a fixed length field and is mandatory for all messages. The message length uniquely
17、indicates the number of octets included in the B-ISDN User Part message content and the message compatibility information fields (see Figure 1). 5.5 Formatting principles The message content of each message contains a number of parameter listed and described in clause 6. Each parameter has a NAME wh
18、ich is coded as a single octet (see Table 2). The length of a parameter may be fixed or variable, and a length indicator of fixed length for each parameter is included. Every parameter contains parameter compatibility information (see Figure 2). Table 2/Q.2763 - Parameter name codes Parameter name A
19、AL parameters AAL prime parameters Access delivery information Additional ATM cell rate Additional calling party number Additional connected number AESA for additional calling party AESA for additional connected party AESA for called party AESA for calling party AESA for connected party Alternative
20、ATM cell rate Application generated identifier Application transport ATC setup parameters ATM cell rate Automatic congestion level Automatic re-routing (crankback) Backward GVNS Backward narrow-band interworking indicator Broadband bearer capability Broadband high layer information Broadband low lay
21、er information Call diversion information Call diversion may occur Call diversion treatment indicators Call history information Call offering treatment indicators Call transfer number Call transfer reference Called IN number Called party number Called party sub-address Called partys indicators Calli
22、ng party number Calling party sub-address Reference (subclause) 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.1 1 7.12 7.13 7.14 7.15 7.16 7.17 7.18 7.19 7.20 7.2 1 7.22 7.23 7.24 7.25 7.26 7.27 7.28 7.29 7.30 7.3 1 7.32 7.33 7.34 7.35 7.36 7.37 Code O100 o1 11 1001 0001 O010 1110 O101 1010 O001 O000 O001
23、O001 1001 O010 1001 O011 O101 1000 O101 1001 O110 1101 O101 o111 O110 1010 o111 1000 1001 o111 O000 1000 O010 o1 11 1001 O110 O100 1101 O001 O100 O101 O000 O100 o1 10 O100 1111 O011 O110 O010 o1 10 O110 1110 O010 1101 o111 O000 O100 O101 O100 O01 1 O110 1111 O000 0100 O001 0101 O001 o111 O000 1010 O
24、001 0110 Table 2lQ.2763 - Parameter name codes (continued) Parameter name Calling partys category Cause indicators CCSS CDVT Charge indicator Charged party identification (national use) Closed User Group information Collect call request Conference treatment indicators Connected line identity request
25、 Connected number Connected sub-address Connection element identifier Connection identifier Consistency check result information Correlation ID Destination connection link identifier Destination signalling identifier Display information Echo control information End-to-end transit delay network gener
26、ated indicator Exclusive connection element identifier Extended quality of service Forward GVNS Forward narrow-band intenvorking indicator Hop counter In-band information indicator Leaf party type Link layer core parameters Link layer protocol parameters Location number Loop prevention indicators Ma
27、ximum end-to-end transit delay MCID response indicators MCID request indicators Minimum ATM cell rate MLPP precedence MLPP user information Narrow-band bearer capability Narrow-band high layer compatibility Narrow-band low layer compatibility Nationallinternational call indicator Network call correl
28、ation identifier Reference (subclause) 7.38 7.39 7.40 7.41 7.42 7.43 7.44 7.45 7.46 7.47 7.48 7.49 7.50 7.5 1 7.52 7.53 7.54 7.55 7.56 7.57 7.58 7.59 7.60 7.61 7.62 7.63 7.64 7.65 7.66 7.67 7.68 7.69 7.70 7.71 7.72 7.73 7.74 7.75 7.76 7.77 7.78 7.79 7.80 Code O000 1001 O001 O010 O100 1011 o111 1110
29、0001 1001 o111 O001 O001 1010 o111 1001 o111 O010 O001 1011 O010 O001 O010 O100 O000 o1 10 O110 1001 O100 1010 o1 10 O101 0101 O100 O000 001 1 o111 O011 O011 o111 1001 1001 1001 O101 1001 O000 0100 1100 O001 1100 O011 1101 O001 1111 O101 O110 O110 1011 o1 10 1100 O011 1111 O100 O100 O000 o1 11 O011
30、1100 O011 1011 O101 O010 O011 1010 O100 1001 O001 1101 O011 O100 0010 O101 0010 1001 O110 1000 Table 2/Q.2763 - Parameter name codes (continued) Parameter name Network look ahead indicator Network management controls Notification OAM traffic descriptor original called number Origination connection l
31、ink identifier Ongination ISC point code Origination signalling identifier Priority Progress indicator Propagation delay counter Quality of Service Redirecting number Redirection information Redirection number Redirection number restriction Remote operations (national use) Report type Report type pr
32、ime Resource identifier SCF ID Segmentation indicator (national use) Service activation Soft PVC called endpoint Soft PVC calling endpoint Subsequent number SuspencUresume indicators Transit network selection (national use) UD action indicators UD capability indicators User-to-user indicators User-t
33、o-user information Reserved for FPH Reserved for look result Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reference (subclause) 7.81 7.82 7.83 7.84 7.85 7.86 7.87 7.88 7.
34、89 7.90 7.91 7.92 7.93 7.94 7.95 7.96 7.97 7.98 7.99 7.100 7.101 7.102 7.103 7.104 7.105 7.106 7.107 7.108 7.109 7.1 10 7.111 7.1 12 Code O101 1111 O101 1011 O010 1100 O100 1000 O010 1000 O101 O101 O010 1011 O000 O010 o1 10 o11 1 O011 O101 O011 O001 O101 O011 O000 1011 O001 O011 O000 1100 O100 O000
35、O011 O010 o1 10 O100 1001 O100 O011 1001 o1 10 o1 10 O011 1110 O011 O011 o111 O110 1001 1000 O000 O101 0010 O010 O010 O01 1 o111 O100 o111 O101 O010 1010 O010 O000 O101 O001 O101 1110 O000 O000 O000 O001 O000 1101 to O000 1111 O001 1000 O001 1110 O010 1111 O01 1 O000 Table 2/Q.2763 - Parameter name
36、codes (concluded) Parameter name Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved, used in N-ISUP Reserved used in N-ISUP Reserved used in N-ISUP Reserved used in N-ISUP Reserved used in N-ISUP Reserved, used in N-ISUP Reserved. used in N-ISUP Reserved for extensio
37、n of name code Reference (subclause) I I Parameter name Length indicator Parameter compatibility information Parameter content Code O011 1000 0100 O001 0100 O010 O100 1110 o111 o111 o111 1010 to o111 1101 o111 1111 to 1000 1110 1010 O000 to 1010 1111 1100 O000 1100 O001 1111 1111 Figure 2/Q.2763 - B
38、-ISDN User Part parameter format The detailed format of the length indicator and the parameter compatibility information is described in clause 6. The detailed format of the parameter content is uniquely defined for each parameter as described in clause 7. Between parameters there should be no unuse
39、d (i.e. dummy) octets. 5.6 Encoding principles for subfields The content of each parameter contains a number of subfields. Within each subfield, the least significant bit of the field is represented by the lowest-numbered bit and the most significant bit is represented by the highest-numbered bit. I
40、n case a subfield exceeds one octet, the significance of the bits, if applicable, is indicated in clause 7. 5.7 Order of transmission Since all the fields consist of an integral number of octets, the formats are presented as a stack of octets. The first octet transmitted to the underlying layedlevel
41、 is the one shown at the top of the stack and the last is the one at the bottom. Unless otherwise indicated, within each octet and subfield the bits are transmitted to the underlying layer/level with the least significant bit first. 5.8 Coding of spare bits Spare bits are coded “O“ unless indicated
42、otherwise. Any parameter values marked as %pare“, “reserved“, or “national use“ may be regarded as unrecognized. 5.9 If messages type codes and parameters are required for national uses not included in this Recommendation, the codes chosen should be from the highest code downwards, that is, starting
43、 at code 11 1 11 110. Message type codes in the range 1 1 11 1 110 to 1 1 100000 and parameter name codes in the range 1 1 1 1 1 1 1 O to 1 1 O00001 are reserved exclusively for this purpose. National message types and parameters 5.10 a) b) c) d) Rules for the allocation of message, parameter name,
44、and parameter subfield codes Existing N-ISUP message and parameter name codes used in B-ISUP should have the same name codes in B-ISUP. Existing N-ISUP message and parameter name codes not used in B-ISUP should be marked reserved in B-ISUP. B-ISUP message and parameter name codes not used in N-ISUP
45、should be marked reserved in N-ISUP. The code point 1 11 1 1 11 1 for both message and parameter name codes is reserved in B-ISUP to indicate extension of the name code: - a second parameter name octet shall appear as the first octet in the parameter content (see Figure 2); a second message name oct
46、et shall be encoded in a new parameter. - Allocation of codes for subfields of parameters used in both B-ISUP and N-ISUP must avoid overlapping and be coordinated. e) 5.11 The formats and codes of the parameters which are originated from the access protocol are the same as specified in Recommendatio
47、n ITU-T 4.2931. The coding standard subfield for such parameters shall be coded as specified in Recommendation ITU-T Q.293 1. Formats and codes of parameters originated from the access protocol 6 Parameter formats and codes 6.1 Message type codes The encoding of the message type is shown in Table 1.
48、 6.2 The format of the message length indicator field is shown in Figure 3. Coding of the message length indicator ext. 8 7 6 5 4 3 2 1 Octets 1 2 Length indicator Figure 3/Q.2763 - Message length indicator field Broadband/ I Pass on 1 Discard I Send I Release I Transit I 1 The message length indica
49、tor field is binary coded to indicate the number of octets in the message content field and the message compatibility information field (see Figure i). The length indicated does not include the routing label octets, the message type code octets or the message length indicator octets. The following codes are used in the message length indicator subfield: a) Length indicator A code expressing in pure binary representation the number of octets (see Note). Bit 8 of octet 1 is the most significant and bit 1 of octet 2 is the least significant respectively. NOTE
