Top Half of Document

 

 

3.50 Signalling point code (national use)

The format of the signalling point code parameter field is shown in Figure 50.

 

8

7

6

5

4

3

2

1

1

Signalling lsb

2

spare

 msb point code

Figure 50/Q.763 – Signalling point code parameter field

3.51 Subsequent number

The format of the subsequent number parameter field is shown in Figure 51.

 

8

7

6

5

4

3

2

1

1

O/E

spare

2

2nd address signal

1st address signal

:

:

    

m

Filler (if necessary)

nth address signal

Figure 51/Q.763 – Subsequent number parameter field

The following codes are used in the subfields of the subsequent number parameter field:

a) Odd/even indicator (O/E): as Subclause 3.9 a).

b) Address signal: as Subclause 3.9 e).

c) Filler: as Subclause 3.9 f).

3.52 Suspend/resume indicators

The format of the suspend/resume indicators parameter field is shown in Figure 52.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 52/Q.763 – Suspend/resume indicators parameter field

The following codes are used in the suspend/resume indicators parameter field:

bit A: Suspend/resume indicator

0 ISDN subscriber initiated

1 network initiated

bits H-B: spare

3.53 Transit network selection (national use)

The format of the transit network selection parameter field is shown in Figure 53.

 

8

7

6

5

4

3

2

1

1

O/E

Type of network identification

Network identification plan

2

  

:

Network identification

n

  

Figure 53/Q.763 – Transit network selection parameter field

The following codes are used in the subfields of the transit network selection parameter field:

a) Odd/even indicator(O/E): as Subclause 3.9 a).

b) Type of network identification

0 0 0 CCITT/ITU-T-standardized identification

0 0 1 spare

0 1 0 national network identification

0 1 1 ü

to ý spare

1 1 1 þ

c) Network identification plan

i) For CCITT/ITU-T-standardized identification

0 0 0 0 unknown

0 0 0 1 spare

0 0 1 0 spare

0 0 1 1 public data network identification code (DNIC), Recommendation X.121

0 1 0 0 spare

0 1 0 1 spare

0 1 1 0 public land Mobile Network Identification Code (MNIC), Recommendation E.212

0 1 1 1 ü

to ý spare

1 1 1 1 þ

ii) For national network identification

This information is coded according to national specifications.

d) Network identification

This information is organized according to the network identification plan and the coding principle given in Subclause 3.9 e) and, if applicable, in Subclause 3.9 f).

3.54 Transmission medium requirement

The format of the transmission medium requirement parameter field is shown in Figure 54.

8

7

6

5

4

3

2

1

Transmission medium requirement (TMR)

Figure 54/Q.763 – Transmission medium requirement parameter field

The following codes are used in the transmission medium requirement parameter field:
0 0 0 0 0 0 0 0 speech
0 0 0 0 0 0 0 1 spare
0 0 0 0 0 0 1 0 64 kbit/s unrestricted
0 0 0 0 0 0 1 1 3.1 kHz audio
0 0 0 0 0 1 0 0 reserved for alternate speech (service 2)/64 kbit/s unrestricted (service 1)
0 0 0 0 0 1 0 1 reserved for alternate 64 kbit/s unrestricted (service 1)/speech (service 2)
0 0 0 0 0 1 1 0 64 kbit/s preferred
0 0 0 0 0 1 1 1 2 × 64 kbit/s unrestricted
0 0 0 0 1 0 0 0 384 kbit/s unrestricted
0 0 0 0 1 0 0 1 1536 kbit/s unrestricted
0 0 0 0 1 0 1 0 1920 kbit/s unrestricted
spare
0 0 0 1 0 0 0 0 3 × 64 kbit/s unrestricted
0 0 0 1 0 0 0 1 4 × 64 kbit/s unrestricted
0 0 0 1 0 0 1 0 5 × 64 kbit/s unrestricted
0 0 0 1 0 0 1 1 spare
0 0 0 1 0 1 0 0 7 × 64 kbit/s unrestricted
0 0 0 1 0 1 0 1 8 × 64 kbit/s unrestricted
0 0 0 1 0 1 1 0 9 × 64 kbit/s unrestricted
0 0 0 1 0 1 1 1 10 × 64 kbit/s unrestricted
0 0 0 1 1 0 0 0 11 × 64 kbit/s unrestricted
0 0 0 1 1 0 0 1 12 × 64 kbit/s unrestricted
0 0 0 1 1 0 1 0 13 × 64 kbit/s unrestricted
0 0 0 1 1 0 1 1 14 × 64 kbit/s unrestricted
0 0 0 1 1 1 0 0 15 × 64 kbit/s unrestricted
0 0 0 1 1 1 0 1 16 × 64 kbit/s unrestricted
0 0 0 1 1 1 1 0 17 × 64 kbit/s unrestricted
0 0 0 1 1 1 1 1 18 × 64 kbit/s unrestricted
0 0 1 0 0 0 0 0 19 × 64 kbit/s unrestricted
0 0 1 0 0 0 0 1 20 × 64 kbit/s unrestricted
0 0 1 0 0 0 1 0 21 × 64 kbit/s unrestricted
0 0 1 0 0 0 1 1 22 × 64 kbit/s unrestricted
0 0 1 0 0 1 0 0 23 × 64 kbit/s unrestricted
0 0 1 0 0 1 0 1 spare
0 0 1 0 0 1 1 0 25 × 64 kbit/s unrestricted
0 0 1 0 0 1 1 1 26 × 64 kbit/s unrestricted
0 0 1 0 1 0 0 0 27 × 64 kbit/s unrestricted
0 0 1 0 1 0 0 1 28 × 64 kbit/s unrestricted
0 0 1 0 1 0 1 0 29 × 64 kbit/s unrestricted
spare

3.55 Transmission medium requirement prime

The format of the transmission medium requirement prime parameter field is shown in Figure 54, except that the coding rules for optional parameter are applied.

The following codes are used in the transmission medium requirement prime parameter field:
0 0 0 0 0 0 0 0 speech
0 0 0 0 0 0 0 1 spare
0 0 0 0 0 0 1 0 reserved for 64 kbit/s unrestricted
0 0 0 0 0 0 1 1 3.1 kHz audio
0 0 0 0 0 1 0 0 reserved for alternate speech (service 2)/64 kbit/s unrestricted (service 1)
0 0 0 0 0 1 0 1 reserved for alternate 64 kbit/s unrestricted (service 1)/speech (service 2)
0 0 0 0 0 1 1 0 reserved for 64 kbit/s preferred
0 0 0 0 0 1 1 1 reserved for 2 × 64 kbit/s unrestricted
0 0 0 0 1 0 0 0 reserved for 384 kbit/s unrestricted
0 0 0 0 1 0 0 1 reserved for 1536 kbit/s unrestricted
0 0 0 0 1 0 1 0 reserved for 1920 kbit/s unrestricted
spare
reserved
0 0 0 1 0 0 1 1 spare
reserved
0 0 1 0 0 1 0 1 spare
reserved
spare

3.56 Transmission medium used

The format of the transmission medium used parameter field is shown in Figure 54, except that the coding rules for optional parameter are applied.

The codings are identical to codings in Subclause 3.55.

3.57 User service information

The format of the user service information parameter field is shown in Figure 55. This format is the same as the Bearer capability information element from Recommendation Q.931 and not all capabilities coded here are supported at this time.

 

8

7

6

5

4

3

2

1

1

ext.

Coding standard

Information transfer capability

2

ext.

Transfer mode

Information transfer rate

2a

Rate multiplier

3

ext.

Layer ident.

User information Layer 1 protocol

4

ext.

Layer ident.

User information Layer 2 protocol

5

ext.

Layer ident.

User information Layer 3 protocol
  NOTE 1 – Octet 2a is required if octet 2 indicates multirate (64 kbit/s base rate); otherwise, it shall not be present.

NOTE 2 – Octets 3, 4, 5 or any combination of these octets may be omitted. Octet 3 may be extended as described in Recommendation Q.931.

Figure 55/Q.763 – User service information parameter field

The codes to be used in the subfields of the user service information parameter field is defined in the Bearer capability information element in Recommendation Q.931.

3.58 User service information prime

The format of the user service information prime parameter field is shown in Figure 55.

The codes to be used in the subfield of the user service information prime parameter field are defined in the Bearer capability information element in Recommendation Q.931.

3.59 User teleservice information

The format of the user teleservice information parameter field is shown in Figure 56. This format is the same as the High Layer Compatibility information element from Recommendation Q.931 and not all capabilities coded here are supported at this time.

 

 

8

7

6

5

4

3

2

1

1

ext.

Coding standard

Interpretation

Presentation

2

ext.

High layer characteristics identification

3

ext.

Extended layer characteristics identification

Figure 56/Q.763 – User teleservice information parameter field

The codes to be used in the user teleservice information parameter field are defined in the High layer compatibility information element in Recommendation Q.931.

3.60 User-to-user indicators

The format of the user-to-user indicators parameter field is shown in Figure 57.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 57/Q.763 – User-to-user indicators parameter field

The following codes are used in the user-to-user indicators parameter field:

bit A: Type

0 request

1 response

If bit A equals 0 (request):

bits C B: Service 1

0 0 no information

0 1 spare

1 0 request, not essential

1 1 request, essential

bits E D: Service 2

0 0 no information

0 1 spare

1 0 request, not essential

1 1 request, essential

bits G F: Service 3

0 0 no information

0 1 spare

1 0 request, not essential

1 1 request, essential

bit H: spare

If bit A equals 1 (response):

bits C B: Service 1

0 0 no information

0 1 not provided

1 0 provided

1 1 spare

bits E D: Service 2

0 0 no information

0 1 not provided

1 0 provided

1 1 spare

bits G F: Service 3

0 0 no information

0 1 not provided

1 0 provided

1 1 spare

bit H: Network discard indicator

0 no information

1 user-to-user information discarded by the network

3.61 User-to-user information

The format of the user-to-user information parameter is shown in Figure 58.

 

8

7

6

5

4

3

2

1

1

:

:

:

n

 

 

User-to-user information

Figure 58/Q.763 – User-to-user information parameter field

The format of the user-to-user information parameter field is coded identically to the protocol discriminator plus user information field described in Recommendation Q.931.

3.62 Backward GVNS

The format of the backward GVNS parameter field is shown in Figure 59.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 59/Q.763 – Backward GVNS parameter field

The following codes are used in the backward GVNS parameter field:

bits B A: Terminating access indicator

0 0 no information

0 1 dedicated terminating access

1 0 switched terminating access

1 1 spare

bits G-C: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.63 CCSS

The format of the CCSS parameter field is shown in Figure 60.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 60/Q.763 – CCSS parameter field

The following codes are used in the CCSS parameter field:

bit A: CCSS call indicator

0 no indication

1 CCSS call

bits H-B: spare

3.64 Call transfer number

The format of the call transfer number parameter field is shown in Figure 61.
 

8

7

6

5

4

3

2

1

1

O/E

Nature of address indicator

2

spare

Numbering plan indicator

Address presentation restricted indicator

Screening indicator

3

2nd address signal

1st address signal

:

:

 

 

  

m

Filler (if necessary)

nth address signal

Figure 61/Q.763 – Call transfer number parameter field

The following codes are used in the subfields of the call transfer number parameter field:

a) Odd/even indicator (O/E): as Subclause 3.9 a).

b) Nature of address indicator

0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number (national use)
0 0 0 0 1 0 0 international number
spare
reserved for national use
1 1 1 1 1 1 1 spare

c) Numbering plan indicator
0 0 0 spare
0 0 1 ISDN (Telephony) numbering plan (Recommendation E.164)
0 1 0 spare
0 1 1 Data numbering plan (Recommendation X.121) (national use)
1 0 0 Telex numbering plan (Recommendation F.69) (national use)
1 0 1 Private numbering plan (national use)
1 1 0 reserved for national use
1 1 1 spare

d) Address presentation restricted indicator

0 0 presentation allowed
0 1 presentation restricted
1 0 spare
1 1 spare

e) Screening indicator

0 0 user provided, not verified
0 1 user provided, verified and passed
1 0 user provided, verified and failed
1 1 network provided

f) Address signal

0 0 0 0 digit 0
0 0 0 1 digit 1
0 0 1 0 digit 2
0 0 1 1 digit 3
0 1 0 0 digit 4
0 1 0 1 digit 5
0 1 1 0 digit 6
0 1 1 1 digit 7
1 0 0 0 digit 8
1 0 0 1 digit 9
1 0 1 0 spare
1 0 1 1 code 11
1 1 0 0 code 12
spare

The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit fields.

g) Filler: as Subclause 3.9 f).

3.65 Call transfer reference

The format of the call transfer reference parameter is shown in Figure 62.

8

7

6

5

4

3

2

1

Call transfer identity

Figure 62/Q.763 – Call transfer reference parameter field

The call transfer identity is a pure binary representation of the integer (0 to 255) assigned unambiguously to the particular ECT supplementary service invocation (see Clause 7/Q.732).

3.66 Forward GVNS

The format of the forward GVNS parameter field is shown in Figure 63.1.

 

8

7

6

5

4

3

2

1

1

Originating participating service provider (OPSP)

2

GVNS user group (GUG)

3

Terminating network routeing number (TNRN)

Figure 63.1/Q.735 – Forward GVNS parameter field

The following codes are used in the subfields of the forward GVNS parameter:

a) Originating participating service provider
 

8

7

6

5

4

3

2

1

1

O/E

spare

OPSP length indicator

1a

2nd digit

1st digit

:

:

:

1m

Filler (if necessary)

nth digit

Figure 63.2/Q.735 – Originating participating service provider subfield

1) Odd/even indicator (O/E): as Subclause 3.9 a).

2) OPSP length indicator

Number of octets to follow. The maximum number of octets is 4, allowing for a maximum number of digits to 7.

3) Digit

Digit string in BCD encoding of flexible length representing the Originating Participating Service Provider (OPSP) identification.

4) Filler

In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal.

b) GVNS user group
 

8

7

6

5

4

3

2

1

2

O/E

spare

GUG length indicator

2a

2nd digit

1st digit

:

:

:

2m

Filler (if necessary)

nth digit

Figure 63.3/Q.735 – GVNS user group subfield

1) Odd/even indicator (O/E): as Subclause 3.9 a).

2) GUG length indicator

Number of octets to follow. The maximum number of octets is 8, allowing for a maximum number of digits to 16.

3) Digit

Digit string in BCD encoding of flexible length representing the GVNS user group identification (GUG).

4) Filler

In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal.

c) Terminating network routeing number
 

8

7

6

5

4

3

2

1

3

O/E

Numbering plan indicator

TNRN length indicator

3a

spare

Nature of address indicator

3b

2nd digit

1st digit

:

:

:

3m

Filler (if necessary)

nth digit

Figure 63.4/Q.735 – Terminating network routeing number subfield

1) Odd/even indicator (O/E): as Subclause 3.9 a).

2) Numbering plan indicator: as Subclause 3.9 d).

3) TNRN length indicator

Number of octets to follow. The maximum number of octets is 9 allowing for a maximum number of digits to 15.

4) Nature of address indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number
0 0 0 0 1 0 0 international number
0 0 0 0 1 0 1 network specific number
spare
reserved for national use
1 1 1 1 1 1 1 spare

5) Digit: as Subclause 3.9 e).

6) Filler: as Subclause 3.9 f).

3.67 Loop prevention indicators

The format of the loop prevention indicators parameter field is shown in Figure 64.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 64/Q.763 – Loop prevention indicators parameter field

The following codes are used in the loop prevention indicators parameter field:

bit A: Type

0 request

1 response

If bit A equals to 0 (request):

bits H-B: spare

If bit A equals to 1 (response):

bits C B: Response indicator

0 0 insufficient information (note)

0 1 no loop exists

1 0 simultaneous transfer

1 1 spare

bits H-D: spare

NOTE – The value "insufficient information" may be received due to interworking.

3.68 Network management controls

The format of the network management controls parameter field is shown in Figure 65.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 65/Q.763 – Network management controls parameter field

The following codes are used in the network management controls parameter field:

bit A: Temporary Alternative Routeing (TAR) indicator

0 no indication

1 TAR controlled call

bits G-B: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.69 Circuit assignment map

The format of the circuit assignment map parameter field is shown in Figure 66.

 

8

7

6

5

4

3

2

1

 

 

1

spare

Map type

 

 

2

8

7

6

5

4

3

2

1

3

16

15

14

13

12

11

10

9

4

24

23

22

21

20

19

18

17

5

spare

31

30

29

28

27

26

25
                 

Figure 66/Q.763 – Circuit assignment map parameter field

The following codes are used in the circuit assignment map parameter field:

a-1) Map type:
0 0 0 0 0 0 spare
0 0 0 0 0 1 1544 kbit/s digital path map format (64 kbit/s base rate)
0 0 0 0 1 0 2048 kbit/s digital path map format (64 kbit/s base rate)
spare

a-2) bits 8,7, octet 1: spare

b-1) Map format (octets 2 to 5):

Each bit position on the map (octets 2 to 5) indicates whether the corresponding 64 kbit/s circuit is used in the N ´ 64 connection. The bits are coded as follows:
0 64 kbit/s circuit is not used
1 64 kbit/s circuit is used

Octet 5 is not used for 1544 kbit/s digital path map.

b-2) bit 8, octet 5: spare

3.70 Correlation id

The format of the correlation id parameter field is shown in Figure 67.

 

8

7

6

5

4

3

2

1

 

1

  

:

Correlation id

n

  

Figure 67/Q.763 – Correlation id parameter field

The correlation id is coded as described in Recommendation Q.1218 [11].

3.71 SCF id

The format of the SCF id parameter field is shown in Figure 68.

 

8

7

6

5

4

3

2

1

 

1

  

:

SCF id

n

  

Figure 68/Q.763 – SCF id parameter field

The SCF id is coded as described in Recommendation Q.1218 [11].

3.72 Call diversion treatment indicators

The format of the call diversion treatment indicators parameter field is shown in Figure 69.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 69/Q.763 – Call diversion treatment indicators parameter field

The following codes are used in the call diversion treatment parameter field:

bits BA: Call to be diverted indicator

0 0 no indication

0 1 call diversion allowed

1 0 call diversion not allowed

1 1 spare

bits G-C: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.73 Called IN number

The format of the called IN number parameter corresponds to the original called number parameter (see Subclause 3.39).

3.74 Call offering treatment indicators

The format of the call offering treatment indicators parameter field is shown in Figure 70:

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 70/Q.763 – Call offering treatment indicators parameter field

The following codes are used in the call offering treatment parameter field:

bits BA: Call to be offered indicator

0 0 no indication

0 1 call offering not allowed

1 0 call offering allowed

1 1 spare

bits G-C: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.75 Charged party identification (national use)

The format of the charged party identification parameter is national network specific. The format is similar to the format of the corresponding INAP parameter in the "FurnishChargingInformation" operation (see Recommendations Q.1218 [11] and Q.1228 [12]).

3.76 Conference treatment indicators

The format of the conference treatment indicators parameter field is shown in Figure 71.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 71/Q.763 – Conference treatment indicators parameter field

The following codes are used in the conference treatment parameter field:

bits BA: Conference acceptance indicator (Note)

0 0 no indication

0 1 accept conference request

1 0 reject conference request

1 1 spare

NOTE – Applicable to the conference and three-party supplementary services.

bits G-C: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.77 Display information

The format of the display information parameter field is shown in Figure 72.

 

8

7

6

5

4

3

2

1

 

1

  

:

Display information

n

  

Figure 72/Q.763 – Display information parameter field

The display information is coded as described in Recommendation Q.931.

3.78 UID action indicators

The format of the UID action indicators parameter field is shown in Figure 73.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 73/Q.763 – UID action indicators parameter field

The following codes are used in the UID action indicators parameter field:

bit A: Through-connection instruction indicator

0 no indication

1 through-connect in both directions

bit B: T9 timer instruction indicator

0 no indication

1 stop or do not start T9 timer

bits G-C: spare

bit H: Extension indicator: as Subclause 3.25 a).


3.79 UID capability indicators

The format of the UID capability indicators parameter field is shown in Figure 74:

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 74/Q.763 – UID capability indicators parameter field

The following codes are used in the UID capability indicators parameter field:

bit A: Through-connection indicator

0 no indication

1 through-connection modification possible

bit B: T9 timer indicator

0 no indication

1 stopping of T9 timer possible

bits G-C: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.80 Hop counter

The format of the hop counter parameter field is shown in Figure 75.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 75/Q.763 – Hop counter parameter field

The following codes are used in the hop counter parameter field:

bits E D C B A: Hop counter

The hop counter contains the binary value of the number of contiguous SS 7 interexchange circuits that are allowed to complete the call.

bits H G F: spare

3.81 Collect call request

The format of the collect call request parameter field is shown in Figure 76.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 76/Q.763 – Collect call request parameter field

The following codes are used in the collect call request parameter field:

bit A: Collect call request indicator

0 no indication

1 collect call requested

bits H-B: spare

3.82 Application transport parameter (APP)

The format of the application transport parameter field is shown in Figure 77.

 

8

7

6

5

4

3

2

1

1

ext.

Application context identifier

2

ext.

spare

SNI

RCI

3

ext.

SI

APM segmentation indicator

4

ext.

Segmentation local reference

5a

  

:

Encapsulated application information

5n

  

Figure 77/Q.763 - Application transport parameter field

The following codes are used in the application transport parameter field:

a) Extension indicator (ext.): as Subclause 3.25 a).

b) Application context identifier (ACI)
0 0 0 0 0 0 0 Unidentified Context and Error Handling (UCEH) ASE
0 0 0 0 0 0 1 PSS1 ASE (VPN)
0 0 0 0 0 1 0 spare
0 0 0 0 0 1 1 Charging ASE
0 0 0 0 1 0 0 GAT
0 0 0 0 1 0 1 ü
        to ý
0 1 1 1 1 1 1 þ
spare
1 0 0 0 0 0 0 ü
        to ý
1 1 1 1 1 1 1 þ
reserved for non-standardized applications

NOTE - The compatibility mechanism as defined in Q.764 is not applicable to this field.

c) Application transport instruction indicators
bit 1 Release call indicator (RCI)

0

 do not release call

1

 release call
bit 2 Send notification indicator (SNI)

0

 do not send notification

1

 send notification

d) APM segmentation indicator

0 0 0 0 0 0 final segment
0 0 0 0 0 1 ü
      to ý
0 0 1 0 0 1 þ
indicates the number of following segments
0 0 1 0 1 0 ü
      to ý
1 1 1 1 1 1 þ
spare

NOTE - The compatibility mechanism as defined in Q.764 is not applicable to this field.

e) Sequence indicator (SI)

0

 subsequent segment to first segment

1

 new sequence

f) Segmentation local reference (SLR)

g) Encapsulated application information:

Contains the application specific information.

The format and coding of this field is dependent upon the APM-user application and defined in the appropriate recommendation. For APM-user applications that wish to provide a service of transparent transport of information (e.g. the case where existing information elements are defined for the transport of certain information) as well as having the ability of passing additional network related information within the public network, then the following guideline is provided:

It is suggested that this field be structured such that the first octet (i.e. first octet of first segment for long APM-user information) is a pointer to information to be transported transparently. The pointer value (in binary) gives the number of octets between the pointer itself (included) and the first octet (not included) of transparent data. The pointer value all zeros is used to indicate that no transparent data is present. The range of octets between the pointer octet and the first octet of transparent data (to which the pointer octet points) contains the network related information to be passed between the applications residing within the public network. The format and coding of both the transparent information and the network related information is application specific and defined in the appropriate recommendation.

3.83 CCNR possible indicator

The format of the CCNR possible indicator parameter field is shown in Figure 78.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 78/Q.763 - CCNR possible indicator parameter field

The following codes are used in the CCNR possible indicator parameter field:

bit A: CCNR possible indicator

0 CCNR not possible

1 CCNR possible

bits H-B: spare

3.84 Pivot capability

The format of the pivot capability parameter field is shown in Figure 79.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 79/Q.763 - Pivot capability parameter field

The following codes are used in the pivot capability parameter field:

bits CBA: Pivot possible indicator

000 no indication

001 pivot routeing possible before ACM

010 pivot routeing possible before ANM

011 pivot routeing possible any time during the call

100 ü

to ý spare

111 þ

bits FED: spare

bit G: Interworking to redirection indicator (national use)

0 allowed (forward)

1 not allowed (forward)

bit H: Extension indicator: as Subclause 3.25 a).

3.85 Pivot routeing indicators

The format of the pivot routeing indicators parameter field is shown in Figure 80.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 80/Q.763 - Pivot routeing indicators parameter field

The following codes are used in the pivot routeing indicators parameter field:

bit GFEDCBA: Pivot routeing indicators

0000000 no indication

0000001 pivot request

0000010 cancel pivot request

0000011 pivot request failure

0000100 interworking to redirection prohibited (backward) (national use)

0000101 ü

to ý spare

1111111 þ

bit H: Extension indicator: as Subclause 3.25 a).

3.86 Called directory number (national use)

The format of the called directory number parameter field is shown in Figure 81.

 

8

7

6

5

4

3

2

1

1

O/E

Nature of address indicator

2

INN

Numbering plan indicator

spare

3

2nd address signal

1st address signal

:

:

    

m

Filler (if necessary)

nth address signal

Figure 81/Q.763 - Called directory number parameter field

The following codes are used in the subfields of the called directory number parameter field:

a) Odd/even indicator (O/E): as Subclause 3.9 a).

b) Nature of address indicator

0000000 spare

0000001 subscriber number (national use)

0000010 unknown (national use)

0000011 national (significant) number (national use)

0000100 reserved

0000101 network-specific number (national use)

0000110 reserved

0000111 reserved

0001000 reserved

0001001 ü

to ý spare

1101111 þ

1110000 ü

to ý reserved for national use

1111110 þ

1111111 spare

c) Numbering plan indicator

000 reserved

001 ISDN (Telephony) numbering plan (Recommendation E.164)

010 spare

011 reserved (national use)

100 reserved (national use)

101 reserved for national use

110 reserved for national use

111 reserved

d) Internal network number indicator (INN)

0 reserved

1 routeing to internal network number not allowed

e) Address signal

0000 digit 0

0001 digit 1

0010 digit 2

0011 digit 3

0100 digit 4

0101 digit 5

0110 digit 6

0111 digit 7

1000 digit 8

1001 digit 9

1010 spare

1011 reserved

1100 reserved

1101 spare

1110 spare

1111 ST

The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit fields.

f) Filler: as Subclause 3.9 f).

3.87 Original Called IN number

The format of the original called IN number parameter corresponds to the original called number parameter (see Subclause 3.39).

3.88 Calling geodetic location

The format of the calling geodetic location parameter field is shown in Figure 82.1. The format and coding of the elements in the shape description are described in the following subclauses.

 

8

7

6

5

4

3

2

1

1

spare

LPRI

Screening

2

ext.

Type of shape

3

  

:

Shape description

n

  

Figure 82.1 - Geodetic location parameter

The following codes are used in the subfields of the geodetic location parameter:

a) Location presentation restricted indicator

00 presentation allowed
01 presentation restricted
10 location not available (Note)
11 spare

NOTE - If the Geodetic Location parameter is included and the LPRI indicates location not available, octets 3 to n are omitted, the subfield (c) is coded with 0000000 and the subfield (b) is coded 11.

b) Screening indicator

00 user provided, not verified
01 user provided, verified and passed
10 user provided, verified and failed
11 network provided

c) Type of shape

0000000 ellipsoid point
0000001 ellipsoid point with uncertainty
0000010 point with altitude and uncertainty
0000011 ellipse on the ellipsoid
0000100 ellipsoid circle sector
0000101 polygon
0000110 ü
     to ý spare
0111111 þ

1000000 ü

     to ý reserved for national use

1111110 þ

1111111 reserved for future expansion

d) Extension indicator (ext.): as Subclause 3.25 a).

e) Shape description

The coding of the shape description consists of different elements dependent on the type of shape as detailed in the following subclauses:

3.88.1 Ellipsoid point shape description

The format of the ellipsoid point shape description is shown in Figure 82.2.
 

8

7

6

5

4

3

2

1

1

Lat. Sign

 msb

2

  

Degrees of latitude

  

3

lsb

4

 msb

5

  

Degrees of longitude

  

6

lsb

Figure 82.2/Q.763 - Ellipsoid point shape description

a) Latitude Sign

0 North
1 South

b) Degrees of latitude

The relation between the binary coded number N and the range of latitudes X (0 = X = 90, where X is in degrees but not necessarily an integral number of degrees) it encodes is described by the following equation;

except for N = 223-1, for which the range is extended to include N+1

c) Degrees of longitude

The longitude, expressed in the range -180° , +180° , is coded as a number between -223 and 223 –1, coded in 2s complement binary. The relation between the binary coded number N and the range of longitudes X (-180 = X = +180, where X is in degrees but not necessarily an integral number of degrees) it encodes is described by the following equation:

3.88.2 Ellipsoid point with uncertainty shape description

The format of the ellipsoid point with uncertainty shape description is shown in Figure 82.3.

 

8

7

6

5

4

3

2

1

1

Lat. Sign

 msb

2

  

Degrees of latitude

  

3

lsb
  msb

5

  

Degrees of longitude

  

6

lsb

7

spare

Uncertainty code

8

spare

Confidence

Figure 82.3/Q.763- Shape description of an ellipsoid point with uncertainty

a) Latitude Sign

As Subclause 3.88.1a).

b) Degrees of latitude

As Subclause 3.88.1b).

c) Degrees of longitude

As Subclause 3.88.1c).

d) Uncertainty code

The uncertainty r, expressed in metres (in the range 1m to 1 800 km), is mapped from the binary number K, with the following formula:

with C = 10 and x = 0.1.

e) Confidence

The confidence by which the location is known to be within the shape description, C (expressed as a percentage) is directly mapped from the binary number K, except for K = 0 which is used to indicate "no information", and 100 < K = 127 which are not used.

3.88.3 Point with altitude and uncertainty shape description

The format of the point with altitude and uncertainty circle shape description is shown in Figure 82.4.

 

8

7

6

5

4

3

2

1

1

Lat. Sign

 msb

2

  

Degrees of latitude

  

3

lsb

4

  

msb

5

  

Degrees of longitude

  

6

lsb

7

spare

Uncertainty code

8

Alt. sign

 msb Altitude  

9

  

lsb

10

spare

Altitude uncertainty code

11

spare

Confidence

Figure 82.4/Q.763 - Shape description of a point with altitude and uncertainty

a) Latitude sign

As Subclause 3.88.1 a).

b) Degrees of latitude

As Subclause 3.88.1 b).

c) Degrees of longitude

As Subclause 3.88.1 c).

d) Uncertainty code

As Subclause 3.88.2 d).

e) Altitude Sign

0 above the ellipsoid
1 below the ellipsoid

f) Altitude

The relation between the binary coded number N and the range of altitudes a (in metres) it encodes is described by the following equation;

except for N = 215 -1 for which the range is extended to include all greater values of a.

g) Altitude uncertainty code

The altitude uncertainty h, expressed in metres (in the range 0 m to ˜1 000 m), is mapped from the binary number K, with the following formula:

with C = 45 and x = 0.025.

h) Confidence

As Subclause 3.88.2 e).

3.88.4 Ellipse on the ellipsoid shape description

The format of the ellipse on the ellipsoid shape description is shown in Figure 82.5.

 

8

7

6

5

4

3

2

1

1

Lat. Sign

 msb

2

  

Degrees of latitude

  

3

lsb

4

  

msb

5

  

Degrees of longitude

  

6

lsb

7

spare

Major radius

8

spare

Minor radius

9

Orientation

10

spare

Confidence

Figure 82.5/Q.763 - Shape description of an ellipse on the ellipsoid

a) Latitude sign

As Subclause 3.88.1 a).

b) Degrees of latitude

As Subclause 3.88.1 b).

c) Degrees of longitude

As Subclause 3.88.1 c).

d) Major radius

The major axis of the ellipse rmajor, expressed in metres (in the range 1 m to 1 800 km), is mapped from the binary number K, with the following formula:

with C = 10 and x = 0.1.

e) Minor radius

The minor axis of the ellipse rminor, expressed in metres (in the range 1 m to 1 800 km), is mapped from the binary number K, with the following formula:

with C = 10 and x = 0.1.

f) Orientation

The orientation of the major axis of the ellipse, q , expressed in degrees (0° being North, 90° being East, etc. with 1° granularity), is mapped from the binary number K, with the following formula:

q = K

except for 180 < K = 255 which are not used.

g) Confidence

As Subclause 3.88.2 e).

3.88.5 Ellipsoid circle sector shape description

The format of the ellipsoid circle sector shape description is shown in Figure 82.6.

 

8

7

6

5

4

3

2

1

1

Lat. Sign

 msb

2

  

Degrees of latitude

  

3

lsb

4

  

msb

5

  

Degrees of longitude

  

6

lsb

7

spare

Radius

8

Offset

9

Included angle

10

spare

Confidence

Figure 82.6/Q.763 - Shape description of an ellipsoid circle sector

a) Latitude sign

As Subclause 3.88.1 a).

b) Degrees of latitude

As Subclause 3.88.1 b).

c) Degrees of longitude

As Subclause 3.88.1 c).

d) Radius

The radius of the circle sector r, expressed in metres (in the range 1 m to 1 800 km), is mapped from the binary number K, with the following formula:

with C = 10 and x = 0.1.

e) Offset

The orientation of the offset of the circle sector, ?, expressed in degrees (0° being North, 90° being East, etc. with 2° granularity), is mapped from the binary number K, with the following formula:

? = 2K

except for 180 < K = 255 which are not used.

f) Included angle

The included angle of the circle sector, b expressed in degrees (0° being North, 90° being East, etc. with 2° granularity), is mapped from the binary number K, with the following formula:

b = 2K

except for 180 < K = 255 which are not used.

g) Confidence

As Subclause 3.88.2 e).

3.88.6 Polygon shape description

The format of the polygon shape description is shown in 82.7.

 

8

7

6

5

4

3

2

1

1

spare

Number of points

2

Lat. Sign 1

 msb

3

  

Degrees of latitude 1

  

4

lsb

5

  

msb

6

  

Degrees of longitude 1

  

7

lsb

:

|

6n-4

Lat. Sign n

 msb

6n-3

  

Degrees of latitude n

  

6n-2

lsb

6n-1

  

msb

6n

  

Degrees of longitude n

  

6n+1

lsb

6n+2

spare

Confidence

Figure 82.7/Q.763 - Shape description of a polygon

a) Number of points

0000 not used
0001 not used
0010 not used
0011 ü
to ý binary value of the number of points (3-15)
1111 þ

b) Latitude Sign 1

As Subclause 3.88.1 a).

c) Degrees of latitude 1

As Subclause 3.88.1 b).

 

d) Degrees of longitude 1

As Subclause 3.88.1 c).

e) Latitude Sign n

As Subclause 3.88.1 a).

f) Degrees of latitude n

As Subclause 3.88.1 b).

g) Degrees of longitude n

As Subclause 3.88.1 c).

h) Confidence

As Subclause 3.88.2 e).

3.89 HTR information

The format of the HTR information parameter field corresponds to the format is shown in Figure 83.

 

8

7

6

5

4

3

2

1

1

O/E

Nature of address indicator

2

spare

Numbering plan indicator

spare

3

2nd address signal

1st address signal

:

:

    

m

Filler (if necessary)

nth address signal

Figure 83/Q.763 - HTR information parameter field

The following codes are used in the subfields of the HTR information parameter field:

a) Odd/even indicator (O/E): as Subclause 3.9 a)

b) Nature of address indicator: as Subclause 3.9 b)

c) Numbering plan indicator: as Subclause 3.9 d)

d) Address signal: as Subclause 3.9 e)

e) Filler: as Subclause 3.9 f).

3.90 Network routeing number (national use)

The format of the network routeing number parameter field is shown in Figure 84.

 

8

7

6

5

4

3

2

1

1

O/E

Numbering plan indicator

Nature of address indicator

2

2nd address signal

1st address signal

:

:

    

m

Filler (if necessary)

nth address signal

Figure 84/Q.763 - Network routeing number parameter field

The following codes are used in the subfields of the network routeing number parameter:

a) Odd/even indicator (O/E): as Subclause 3.9 a).

b) Numbering plan indicator

000 spare

001 ISDN (Telephony) numbering plan (Recommendation E.164)

010 spare

011 spare

100 spare

101 spare

110 reserved for national use

111 reserved for national use

c) Nature of address indicator

0000 spare

0001 network routeing number in national (significant) number format (national use)

0010 network routeing number in network specific number format (national use)

0011 ü

to ý spare

1010 þ

1011 ü

to ý reserved for national use

1111 þ

d) Address signal

0000 digit 0

0001 digit 1

0010 digit 2

0011 digit 3

0100 digit 4

0101 digit 5

0110 digit 6

0111 digit 7

1000 digit 8

1001 digit 9

1010 spare

1011 spare

1100 spare

1101 spare

1110 spare

1111 spare

e) Filler: as Subclause 3.9 f).

3.91 Query on release capability (network option)

The format of the query on release capability parameter field is shown in Figure 85.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 85/Q.763 - QoR capability parameter field

The following codes are used in the QoR capability parameter field:

bit A: QoR capability indicator

0 no indication

1 QoR support

bits G-B: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.92 Pivot status (national use)

The format of the pivot status parameter field is shown in Figure 86.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 86/Q.763 - Pivot status indicator parameter field

bits BA: Pivot status indicator

00 not used
01 acknowledgment of pivot routeing
10 pivot routeing will not be invoked
11 spare

bits GFEDC: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.93 Pivot Counter

The format of the pivot counter parameter field is shown in Figure 87.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 87/Q.763 - Pivot counter parameter field

The following codes are used in the pivot counter parameter field:

bits EDCBA Pivot counter

binary value of the number of redirections

bits HGF spare

3.94 Pivot routeing forward information

The pivot routeing forward information parameter is a constructor with format as shown in Figure 88.1.

 

8

7

6

5

4

3

2

1

1

information type tag

2

information type length

3

information type value

:

  

:

  

n+1

information type tag

n+2

information type length

n+3

information type value

Figure 88.1/Q.763 - Pivot routeing forward information parameter field

The values of the information type tag are:

0000 0000 not used
0000 0001 return to invoking exchange possible (national use)
0000 0010 return to invoking exchange call identifier (national use)
0000 0011 performing pivot indicator
0000 0100 invoking pivot reason
0000 0101
to
1111 1111		 ü

ý

þ

spare

3.94.1 Return to invoking exchange possible (national use)

Return to invoking exchange possible has length zero and has no information type value.

3.94.2 Return to invoking exchange call identifier (national use)

The format of the return to invoking exchange call identifier is shown in Figure 9, and the encoding is identical with that of the Call Reference parameter as shown in Subclause 3.8.

3.94.3 Performing pivot indicator

The format of the performing pivot indicator is shown in Figure 88.2.

8

7

6

5

4

3

2

1

1

ext.

Performing pivot reason
Reason 1

2

spare

Pivot possible indicator at performing exchange

:

:

2n-1

ext.

Performing pivot reason
Reason n

2n

spare

Pivot possible indicator at performing exchange

Figure 88.2/Q.763 - Performing pivot indicator

The following codes are used in the performing pivot indicator:

a) Extension indicator (ext.): as Subclause 3.25 a).

b) Performing Pivot Reason (octet 2n-1)

0 0 0 0 0 0 0 unknown/ not available

0 0 0 0 0 0 1 service provider portability (national use)

0 0 0 0 0 1 0 reserved for location portability

0 0 0 0 0 1 1 reserved for service portability

0 0 0 0 1 0 0 ü

to ý spare

0 1 1 1 1 1 1 þ

1 0 0 0 0 0 0 ü

to ý reserved for national use

1 1 1 1 1 1 1 þ

c) Pivot Possible Indicator at Performing Exchange (octet 2n)

0 0 0 no indication

0 0 1 pivot routeing possible before ACM

0 1 0 pivot routeing possible before ANM

0 1 1 pivot routeing possible any time during the call

1 0 0 ü

to ý spare

1 1 1 þ

3.94.4 Invoking pivot reason

The format of the invoking pivot reason is shown in Figure 88.3.

8

7

6

5

4

3

2

1

1

ext.

Invoking Pivot Reason

Figure 88.3/Q.763 - Invoking pivot reason

The coding of the invoking pivot reason is identical to that of the performing pivot indicator as shown in Subclauses 3.94.3 a) and b).

3.95 Pivot routeing backward information

The pivot routeing backward information parameter is a constructor with format as shown in Figure 88.1.

The values of the information type tag are:

0000 0000 not used

0000 0001 return to invoking exchange duration

0000 0010 return to invoking exchange call identifier

0000 0011 invoking pivot reason

0000 0100 ü
to ý spare
1111 1111 þ

3.95.1 Return to invoking exchange duration (national use)

Return to invoking exchange duration is encoded in units of seconds as a variable length (of length 1-2 octets) integer with the least significant bit in the first octet.

3.95.2 Return to invoking exchange call identifier (national use)

The format of the return to invoking exchange call identifier is shown in Figure 9, and the encoding is identical to that of the call reference parameter as shown in Subclause 3.8.

3.95.3 Invoking pivot reason

The format and coding of the invoking pivot reason are given in Subclause 3.94.4.

3.96 Redirect capability (national use)

The format of the redirect capability parameter field is shown in Figure 89.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 89/Q.763 - Redirect capability parameter field

The following codes are used in the redirect capability parameter field:

bits CBA Redirect possible indicator

000 not used

001 redirect possible before ACM

010 redirect possible before ANM

011 redirect possible at any time during the call

100 ü

to ý spare

111 þ

bits GFED spare

bit H Extension indicator: as Subclause 3.25 a).

3.97 Redirect counter (national use)

The format of the redirect counter parameter field is shown in Figure 90.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 90/Q.763 - Redirect counter parameter field

The following codes are used in the redirect counter parameter field:

bits EDCBA Redirect counter

binary value of the number of redirections

bits HGF spare

3.98 Redirect status (national use)

The format of the redirect status parameter field is shown in Figure 91.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 91/Q.763 - Redirect status parameter field

bits BA: Redirect status indicator

00 not used
01 acknowledgment of redirection
10 redirection will not be invoked
11 spare

bits GFEDC: spare

bit H: Extension indicator: as Subclause 3.25 a).

3.99 Redirect forward information (national use)

The redirect forward information parameter is a constructor with format as shown in Figure 88.1.

The values of the information type tag are:

0000 0000 not used

0000 0001 return to invoking exchange possible

0000 0010 return to invoking exchange call identifier

0000 0011 performing redirect indicator

0000 0100 invoking redirect reason

0000 0101 ü
to ý spare
1111 1111 þ

3.99.1 Return to invoking exchange possible

Return to invoking exchange possible has length zero and has no information type value.

3.99.2 Return to invoking exchange call identifier

The format of the return to invoking exchange call identifier is shown in Figure 9, and the encoding is identical with that of the Call Reference parameter as shown in Subclause 3.8.

3.99.3 Performing redirect indicator

The format of the performing redirect indicator is shown in Figure 92.

8

7

6

5

4

3

2

1

1

ext.

Performing redirect reason
Reason 1

2

spare

Redirect possible indicator at performing exchange

:

:

2n-1

ext.

Performing redirect reason
Reason n

2n

spare

Redirect possible indicator at performing exchange

Figure 92/Q.763 - Performing redirect indicator

The following codes are used in the performing redirect indicator:

a) Extension indicator (ext.): as Subclause 3.25 a)

b) Performing redirect reason (octet 2n-1)

0 0 0 0 0 0 0 unknown/ not available

0 0 0 0 0 0 1 service provider portability (national use)

0 0 0 0 0 1 0 reserved for location portability

0 0 0 0 0 1 1 reserved for service portability

0 0 0 0 1 0 0 ü

to ý spare

0 1 1 1 1 1 1 þ

1 0 0 0 0 0 0 ü

to ý reserved for national use

1 1 1 1 1 1 1 þ

c) Redirect possible indicator at performing exchange (octet 2n)

0 0 0 no indication

0 0 1 redirect possible before ACM

0 1 0 redirect possible before ANM

0 1 1 redirect possible any time during the call

1 0 0 ü

to ý spare

1 1 1 þ

3.99.4 Invoking redirect reason

The format of the invoking redirect reason is shown in Figure 93.

 

8

7

6

5

4

3

2

1

1

ext.

Invoking redirect reason

Figure 93/Q.763 - Invoking redirect reason

The coding of the invoking redirect reason is identical to that of the performing redirect indicator as shown in Subclauses 3.99.3 a) and b).

3.100 Redirect backward information (national use)

The redirect backward information parameter is a constructor with format as shown in Figure 88.1.

The values of the information type tag are:

0000 0000 not used

0000 0001 return to invoking exchange duration

0000 0010 return to invoking exchange call identifier

0000 0011 invoking redirect reason

0000 0100 ü
to ý spare
1111 1111 þ

3.100.1 Return to invoking exchange duration

Return to invoking exchange duration is encoded in units of seconds as a variable length (of length 1-2 octets) integer with the least significant bit in the first octet.

3.100.2 Return to invoking exchange call identifier

The format of the return to invoking exchange call identifier is shown in Figure 9, and the encoding is identical with that of the Call Reference parameter as shown in Subclause 3.8.

3.100.3 Invoking redirect reason

The format and coding of the invoking redirect reason are given in Subclause 3.99.4.

3.101 Number portability forward information (network option)

The format of the number portability forward information parameter field is shown in Figure 94.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

Figure 94/Q.763 - Number portability forward information parameter field

The following codes are used in the number portability forward information parameter field:

a) bits DCBA: Number portability status indicator

0000 no indication

0001 number portability query not done for called number

0010 number portability query done for called number, non-ported called subscriber

0011 number portability query done for called number, ported called subscriber

0100 ü

to ý spare

1111 þ

b) bits GFE: spare

c) bit H: Extension indicator: as Subclause 3.25 a).