CEPT T CD 08-02 E-1986 Interworking Aspects of Packet Switched Public Data《分组交换公共数据互通方面》.pdf

《CEPT T CD 08-02 E-1986 Interworking Aspects of Packet Switched Public Data《分组交换公共数据互通方面》.pdf》由会员分享，可在线阅读，更多相关《CEPT T CD 08-02 E-1986 Interworking Aspects of Packet Switched Public Data《分组交换公共数据互通方面》.pdf（5页珍藏版）》请在麦多课文档分享上搜索。

1、CEPT T/CD*08-02*E 86 2326414 0004303 4 W Page 1 TCD08-02 E Secornmendation T/CD 08-02 (Odense 1986) INTERWORKING ASPECTS OF PACKET SWITCHED PUBLIC DATA Recommendation proposed by Working Group T/WG 10 “Data communications” (CD) Text of the Recommendation adopted by the “Telecommunications” Commissio

2、n: “The Conference of European Post and Telecommunications Administrations, considering - that European public packet switched data networks are in service and that their interconnection has been carried out, - that experience shows that interconnection of these networks can pose practical problems,

3、 either because some of these problems have not been dealt with in CCIT or CEPT Recommendations, or because on some points it has emerged that these Recommendations give rise to differing interpretations, - that as far as possible, the differences in the implementation of national interfaces, networ

4、k user procedures and facilities offered to users should be kept to a minimum, - that CEPT Recommendation T/CSTD 2 provides already some guidelines on interworking aspects, recommends - that the optional user facilities and additional features for user classes 8-1 1 should be implemented in a harmon

5、ized o way according to this Recommendation, as given in following table.” O Edition of April 15, 1987 CEPT T/CD*O-OZ*E b 2326414 0004304 b T/CD 08-02 E Page 2 Harmonization of optional user facilities for user classes 8-11 in CEPT countries X.2 (Version 84) CCITT CEPT User classes of service Option

6、al user facility 8-1 1 8-1 1 vc PVC vc PVC 1 I 1.2 Nonstandard default window sizes A A EA EA 256 A A EA EA 1.4* Default throughput classes assignment A A EA EA Optional user facilities assigned for an agreed contractual period 1.1 Extended packet sequence numbering (module 128) A A N N 1,3 Nonstand

7、ard default sizes 16, 32, 64, 2048, 4096 A A N N 512, 1024 A A A A 1.5 Flow control parameter negotiation E E - 1.6* Throughput class negotiation E E - i .7 Packet retransmission A A N N 1.8 Incoming calls barred E E - 1.9 Outgoing calls barred E E - 1.10 One-way logical channel outgoing E E 1.1 1 O

8、ne-way logical channel incoming A - 1-12 Closed user group E E - 1.13* Closed user group with outgoing access A - 1.17 Bilateral closed user group A N - 1,18 Bilateral closed user group within outgoing access A N - 1.20 Fast select acceptance E - 1.21 Multilink procedure A A A A 1.22 Charging inform

9、ation A A - 1.23 Direct call FS N - 1.24* Hunt group A - EA - 1.25 On-line facility registration A A A A N N 1.26 D-bit modification 1.27 Local charging prevention A 1.28* Call redirection A - 1.29 Network user identification A A 1.30 Extended frame sequence numbering A A N N 1.31 RPOA selection A N

10、 - 2.1 Closed user group selection E - 2.2 Bilateral closed user group selection A N - 2.4 RPOA selection A - 2.5 Flow control parameter negotiation E - 2.6 Fast select E - 2.7* Throughput class negotiation E - 2.9 Charging information A - 2.10* Transit delay selection and indication E - 2,ll Call r

11、edirection notification (to alternate DTE) A - 2.12* Called line address modified notification A 2.13 Network user identification A - 2.14* 3. Additional features - - - - - - EA - EA A - EA A - EA - 1.14 1.15 Incoming calls barred within a closed user group A EA - 1.16 Closed user group with incomin

12、g access Outgoing calls barred within a closed user group - - 1.19 Reverse charging acceptance A EA - E - - - A - - EA - - - 2, Optional user facilities on a per-call basis E - 2.3 Reverse charging) A - EA - N E E E N 2.8 Abbreviated address calling FS - A E A EA A A - - - - - - - - - - - - - Closed

13、 user group with outgoing access selection A 3.1 Extended interrupt E E E E - - 1 3.2 CCITT-specified DTE facilities E E E = Essential, A = Additional. EA = A-facility essential in CEPT countries. I) For the time being, only for national use. * For facilities marked with an * details in the implemen

14、tation are found in the following pages. N = Presently not offered, unlikely to be available on many networks in the future. FS = Following study. Edition of April 15, 1987 -7 CEPT T/CD*O-OZ*E 6 2326414 0004305 1. 1.1. 1.2. 1.2.1. .2.2. .2.3. .2.4. 1.2.5. 1.2.6. 1.2.7. 1.2.8. 1.2.9. 1.2.10. 1.2.11.

15、1.2.12. T/CD 08-02 E Page 3 ADDITIONAL INFORMATION ON THROUGHPUT CLASS Definitions (provisional until final decision in CCLTT) The virtual circuit throughput is dened as the total number of user data bits in an individual transfer sample that are successfully transmitted in one direction of a partic

16、ular virtual circuit between a data source and a data sink divided by theinput/output time (in seconds) for that sample (dened in CCITT Recommen- dation X. 140). User data bits are the bits of the user data field in data packets of the X.25-rsp. X.75-Packet Level (protocol/data at Layer 4 and above)

17、. Framing, routing, bit stuffing, error control and other protocol fields introduced by all protocols at or below the network layer are excluded. The throughput class is a value, determined for each direction of transmission on a virtual call at the time of call establishment which is intended to re

18、present the largest value of actual throughput likely to be experienced during the existence of the call. Implementation details Throughput class negotiation should be as defined in CCITT Recommendation X.25. Throughput class has an end-to-end significance; in particular, once a vistual call is esta

19、blished, the values of throughput class for each disection of transmission are the same at both DTE/DCE interfaces, Networks do not guarantee that the throughput achieved will correspond to the throughput class 100% of the time. However, in the long term, networks should guarantee the achievable thr

20、oughput on the basis of a 95% probability value under specific conditions. The throughput achieved may exceed the throughput class. Network should not allow at the DTE/DCE interface a throughput class which exceeds the physical line speed of the access. If a higher value is requested then the networ

21、k should negotiate it down. For throughput class negotiation at the DTE/DCE interface, the network should consider each virtual circuit as independent. It is the responsibility of each network node (national or international) to reduce the requested throughput class if this throughput class correspo

22、nds to a thoughput that cannot be achieved on the virtual circuit, for example if the physical line speed of the link would be exceeded. The conditions upon which an international node reduces the throughput class requested on a X.75 link should be decided by bilateral agreement between Administrati

23、ons. In particular, specific link characteristics and operating conditions should be taken into account; for example, on a 9,600 bit/s X.75 link, the throughput class should not exceed 9, corresponding to 4,800 bit/s. It is the responsibility of each network whether or not to apply a relation betwee

24、n the requested throughput class and the flow control parameter values (window and packet size) on the national part of an international virtual circuit. In particular, networks negotiating the flow control parameters with end-to-end significance should consider that this end-to-end significance may

25、 only be valid on the national part of the international virtual circuit. The eventual relation to be applied on an international X.75 link between throughput class and flow control parameter values should be decided by bilateral agreement between Administrations. It should be a long term objective

26、that Administrations can decide this issue unilaterally. Determination of rules additional to those in X.25 concerning the throughput class negotiation to be used on a part of a virtual circuit should be based on measurements of throughput. These measurements should be made under strictly specified

27、conditions. Networks should, as much as possible, allocate resources to each virtual circuit in order to ensure that the throughput achievable will correspond to the throughput class requested by the DTE which originated the call. I Edition of April 15, 1987 CEPT T/CD*08-02*E 86 E 2326434 0004306 T

28、E T/CD 08-02 E Page 4 2. 2.1. 2.2. 2.3. 3. 3.1. 3.2. 3.3. 3,4. 4. ADDITIONAL INFORMATION ON TRANSIT DELAY SELECTION AND INDICATION (provisional until final decision in CCITT) The DTE may select a desired transit delay in the call request packet as defined in paragraph 6.28 of X.25. The network may t

29、ake this value for the selection of a specific route. The network (for international connections the originating network) will replace the value provided by the DTE with a network specific value dependent on its internal characteristics. Some networks may also use several specific values taking into

30、 account, e.g. different trunk speeds and the use of satellites or cables. For national calls, this value will be signalled to the called DTE. In case of an international call, the originating network will add to its specific value a value depending on the characteristics of the international links

31、as the transit delay selection utility. Each following network will add its network specific value and in case of transit an outgoing link specific value. The use of the transit delay for route selection in case of transit arrangements is for further study. If a network receives a call request with

32、the transit delay selection and indication facility to be sent to a called DTE of which the network knows that it cannot handle this facility the network will not clear the call: In this case the network may delete the facility in the incoming call packet. The network may only insert the transit del

33、ay selection and indication facility in the call connected packet if this facility was sent in the call request and in the corresponding incoming call packet. Values used for network specific and link specific transit delay The exact values are considered as a national matter and should be based on

34、measurement results under specific conditions. X. 135 is considered as a useful starting point in case where no measurement results are available. The values in it are consistent with figures of 400 ms for a national network and 150 ms for an international link, with an additional 150 ms if the link

35、 is at 9.6 kbit/s instead of 48 kbit/s or more and an additional 300 ms if it is over a satellite transmission channel. These are mean values, not 95% values. However, a value of 200 ms on national calls, with an additional 150 ms to 250 ms for international calls seems to be more appropriate in Eur

36、opean environment if no satellite is used. The coding of the X.75 utility should align with that in X.25, using a two octet presentation in units of milliseconds. If an X.75 link does not yet support the transit delay signalling, the call should be established that means no transit delay utility sho

37、uld be signalled to the other network and not transit delay indication facility should be signalled back to the calling DTE. ADDITIONAL INFORMATION ON HUNT GROUP Hunt groups may be limited to a single network node. Hunt group membership may preferably imply a common facility profile. If a calling DT

38、E in a hunt group uses its own specific address there should be a possibility of signalling a subaddress. This subaddress should be signalled to the called DTE independent whether the individual address or the hunt group address is signalled in the INCOMING CALL packed to the called DTE. The Hunt Gr

39、oup should allow for at least 10 members. ADDITIONAL INFORNIATION ON CALL REDIRECTION Call Redirection should also be available if the called DTE is busy. Edition of April 1 5. 1987 CEPT T/CD*O-OZ*E b I 2326414 O004307 1 I, - 5. 5.1. 5.2. 5.3. 6. 7. 7.1. I 7.2. 8. T/CD 08-02 E Page 5 ADDITIONAL INFO

40、RMATION ON CALLED LINE ADDRESS MODIFIED NOTIFICATION (CLAMN) CLAMN can only be passed to a DTE where explicitly known that this facility is accepted by this DTE. A DTE not recognizing CLAMN may be able to detect redirection/hunting by comparison of called address in the call connected packet. CLAMN

41、has to be signalled over an X.75 link. For an interim period, network must have the option not to signal CLAMN to other networks, because some networks may not yet have implemented this facility/ utility. In this case the call has to be established without CLAMN. If a DTE indicates invalid reason in

42、 the CLAMN in the CALL ACCEPTED/CLEAR REQUEST packet, this invalid reason should be overwritten by the network with the reason DTE originated. ADDITIONAL INFORMATION ON CUG Note 6 to Table 24m.25 warns that some international CUG cails may be cleared if the destination network does not support CUG w

43、ith OA selection, even though the called DTE should be accessible, This is understood to refer to the fact that the X.75 CUG utility is mandatory whereas the CUG + OA utility is optional. In order to solve this problem, all European networks should support the CUG + OA utility on X.75 links, ADDITIO

44、NAL INFORMATION ON EXTENDED INTERRUPT Ail networks wiil eventually support 32 octets interrupt packets. Networks supporting 32 octets interrupt packets earlier than others should not selectively prevent them being sent over X.75 links. The result of this will depend on the reaction of the receiving

45、network; it may, for example, be the resetting or clearing of the call. There are 2 solutions for the problem of existing 1980 DTEs in relation to 32 octets interrupt packets: (a) the 32 octets interrupt packet is sent to the DTE; (b) an X.25 port parameter indicates whether a DTE supports a single

46、or 32 octets interrupt packet (possibly as on facet of a more general 1980/84 parameter). If a DTE supports only an one octet interrupt packet and a longer interrupt packet was received from the remote DTE, the network should reset the virtual call. . Solution (b) should be the preferred one. ADDITI

47、ONAL INFORMATION ON CCITT-SPECIFIED DTE FACILIITIES All networks should check the presence of the OS1 marker and may also check the codes foilowing it, The presence of the OS1 marker could be used for charging purposes. If a network receives a call request with CCITT-specjed DTE facilities to be sen

48、t to a called DTE of which the network knows that it cannot handle these facilities, the network will not clear the call. In this case the network may delete these facilities in the incoming call packet. If a network receives a call accepted packet with CCITT-specified DTE facilities to be sent to cailing DTE of which the network knows that it cannot handle these facilities, the network will not clear the call. In this case the network may delete these facilities in the call connected packet. Edition of April 15, 1987 -7 t _