ITU-T Q 85 6-1995 Stage 2 Description for Community of Interest Supplementary Services - Clause 6 - Global Virtual Network Service (GVNS) General Recommendations on Telephone Switcon F.pdf

《ITU-T Q 85 6-1995 Stage 2 Description for Community of Interest Supplementary Services - Clause 6 - Global Virtual Network Service (GVNS) General Recommendations on Telephone Switcon F.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 85 6-1995 Stage 2 Description for Community of Interest Supplementary Services - Clause 6 - Global Virtual Network Service (GVNS) General Recommendations on Telephone Switcon F.pdf（35页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 1 TELECOMMUNICATION (02/95)STANDARDIZATION SECTOROF ITU%.%2!,G0G02%#/-%.$!4)/.3G0G0/.G0G04%,%0(/.%37)4#().G0G0!.$G0G03).!,).telecommunications service: See clause 2.2/I.112 3, definition 201.6.3.12 terminating access indication: Information used to identi

2、fy the type of access that the GVNS TerminatingParticipating Service Provider actually used to complete the call.6.3.13 terminating network routing number: Information used by the terminating functional entity to route calls.This information is mandatory and is carried by either an ISDN number or a

3、network-specific number.6.3.14 terminating participating service provider identification: Information that uniquely identifies theparticipating service provider that provides customer access to GVNS to the called user/interface.6.3.15 transit indication: Information that indicates that the call is n

4、ot a terminating call and must be routed to theGVNS terminating service providers network.6.4 Symbols and abbreviationsFor the purposes of this Recommendation, the following abbreviations are used:CC Call ControlCCA Call Control Agentconf. confirmDB DataBaseGVNS Global Virtual Network Serviceind. in

5、dicationISDN Integrated Services Digital NetworkLE Local ExchangePSTN Public Switched Telephone Networkresp. responsereq. requestSDL Specification and Description LanguageSL customers may define a physical entity (station or user networkinterface) as multiple on-net locations during service provisio

6、ning. As a result, one physical entity may be registered toone or more GVNS User Groups. A GVNS customer is assigned a unique identifier which identifies the GVNS UserGroup. A GVNS customer may choose to group users into one or more subgroups in order to allow sub-group dependentservice interactions

7、 and operations.The GVNS customer can define call screening to determine what types of calls are allowed from on-net locations. Allcalls made from an on-net location may terminate to an on-net or off-net location (i.e., non-GVNS location). Ifterminating to an on-net location, it could be done via a

8、dedicated or a switched access. For either switched or directaccess, a user may need to dial a special code (e.g. prefix or access code) to identify GVNS calls and/or the desiredGVNS Participating Service Provider. The availability of Calling Line Identification (network-provided or network-verified

9、) is necessary to provide authorized access to the GVNS.A GVNS user may dial a private or a public number from an on-net location to reach off-net or other on-net locations.GVNS calls can also be made from non-GVNS locations. Such an access is called a remote access. At the customersrequest, appropr

10、iate verification of the calling party may be required. In this case, the caller makes a call to a RemoteAccess Number (e.g. public number or service code) and provides an authorization code, and waits for authorization.Either the Remote Access Number or the authorization code provides authorized ac

11、cess to the GVNS. Once a non-GVNS location receives authorized access to a particular GVNS user group, it functions as an on-net location. As aGVNS Service Providers option, the Calling Party could place additional calls without requiring re-entry of theauthorization code for remote access.GVNS allo

12、ws the customer to define a private numbering plan. The number of digits sent and received between thecustomers equipment and the GVNS service point will be, within a given range, specified by each GVNS ParticipatingService Provider. A customer should have the capability to define an on-net location

13、 with a customer-defined privatenumber or a public number. A customer may also define off-net locations as part of its customer-defined numberingplan. Such locations are termed virtual on-net locations.GVNS provides the customers with global services as a result of internetworking among the service

14、providers in variouscountries. Many service providers already provide the service between pairs of countries via bilateral agreements. Inview of the above, internetworking requirements become the primary focus of the ITU-T GVNS standardization effortto facilitate global deployment of GVNS among mult

15、iple countries.6.6 Derivation of a functional model6.6.1 Functional model descriptionThis subclause contains a description of the functional model of GVNS and is depicted in Figure 6-1 below. Thefunctional model contains five Functional Entities (FE1 to FE5) and four relationship types (ra, rb, rc,

16、and rd). Functionalentities are represented by circles and the relationship between two communicating functional entities is identified by aline joining them. Each functional entity is given a unique label (e.g., FE1, FE2) adjacent to the circle. The relationshipsare labelled (e.g. ra) for ease of r

17、eference. The functional entity type is contained within the circle._1)Dedicated network resources may be used to access GVNS or in conjunction with GVNS.4 Recommendation Q.85 (02/95)The five FEs are characterized into the following three functional entity types: Service Logic and Data Control (SL a

18、ndb) FEs of CC type to invoke, when appropriate, the necessary network resource functions (e.g., tonesand announcement, digit collection) to provide GVNS. Transit Control (TC) FEs of TC type modify necessary GVNS information for transit-type of calls.FE1 and FE3 are of the SS FE2 and FE4 are of the

19、SLb) remove prefix digits;c) interact with FE5 and the originating CCA functional entity of a basic service that is involved in a GVNScall, as required;d) establish and/or release a GVNS call (upon request of FE5 or the originating CCA functional entity of abasic service that is involved in a GVNS c

20、all);Recommendation Q.85 (02/95) 5e) establish, manipulate and release a GVNS call (upon request of FE2);f) associate and relate the originating and terminating CCA functional entities of a basic service that areinvolved in a particular GVNS call;g) manage the relationship between the originating an

21、d terminating CCA functional entities of a basicservice that are involved in a GVNS call (i.e. maintain the overall perspective of the call).6.6.2.2 Functional entity FE2FE2 is of the Service Logic and Data Control type. FE2 supports the functionality to:a) interface and interact with FE1;b) store a

22、nd process the service logic and data required to direct FE1 in handling a GVNS call;c) perform originating GVNS call screening and routing determination;d) interface and interact with FE4, if necessary, to process a GVNS call.6.6.2.3 Functional entity FE3FE3 is of the Service Switching and Resource

23、 Control type. FE3 supports the functionality to:a) interface and interact with FE5;b) recognize a GVNS service request from FE5 and interact with the terminating CCA functional entity of abasic service that is involved in a GVNS call;c) interact with FE4, when necessary;d) establish and/or release

24、a GVNS call (upon request of FE5 or the terminating CCA functional entity of abasic service that is involved in a GVNS call);e) establish, manipulate and/or release a GVNS call (upon request of FE4);f) associate and relate the originating and terminating CCA functional entities of a basic service th

25、at areinvolved in a particular GVNS call;g) manage the relationship between the originating and terminating CCA functional entities of a basicservice that are involved in a GVNS call (i.e. maintain the overall perspective of the call).6.6.2.4 Functional entity FE4FE4 is of the Service Logic and Data

26、 Control type. FE4 supports the functionality to:a) interface and interact with FE3, when requested by FE3;b) store and process the service logic and data that is required to direct FE3 to handle a GVNS call whenterminating GVNS call screening and routing determination is required;c) interface and i

27、nteract with FE2, when requested from FE2, to process a GVNS call.6.6.2.5 Functional entity FE5FE5 is of the Transit Control type. FE5 supports the functionality to:a) interface and interact with FE1 and FE3;b) modify, when necessary, the GVNS information received in order to deliver the call to the

28、 terminating CCfunctional entity of a basic service that is involved in a GVNS call (e.g. GVNS User GroupIdentification);c) pass through the call and/or GVNS information.6.6.3 Relation with a basic serviceThe relationship between the functional models of GVNS and a basic service is shown in Figure 6

29、-2.6 Recommendation Q.85 (02/95)T1160510-94/d02rbrc r1r2rdr3r2raraSLb) ENQUIRY 1 resp. conf.;c) ENQUIRY 2 req. ind.;d) ENQUIRY 2 resp. conf.;e) ENQUIRY 3 req. ind.;f) ENQUIRY 3 resp. conf.;g) REQ.INFO req. ind.;h) REQ.INFO resp. conf.;i) INFORM 1 req. ind.;j) INFORM 1 resp. conf.6.7.2.1 Definition o

30、f information flow ENQUIRY 1 req. ind. and resp. conf.ENQUIRY 1 req. ind. is used to request originating GVNS call screening and routing information translation. This is aconfirmed information flow and ENQUIRY 1 resp. conf. is used to carry back the information on rejecting the call or onhow to rout

31、e the call. This information flow is within the rcrelationship.The following items of information are or may be conveyed in the ENQUIRY 1 req. ind. and ENQUIRY 1 resp. conf.information flows:TABLE 6-1/Q.85Information items for ENQUIRY 1 req. ind. and resp. conf. information flows6.7.2.2 Definition o

32、f information flow ENQUIRY 2 req. ind. and resp. conf.ENQUIRY 2 req. ind. is used to request GVNS routing information translation. This is a confirmed information flowand ENQUIRY 2 resp. conf. that is used to carry back information on rejecting the call or on how to route the call. Thisinformation f

33、low is within the rbrelationship._2)The information flows defined in Recommendation Q.71 4 include CONNECTED req. ind., DISCONNECT req. ind.,PROCEEDING req. ind., RELEASE req. ind. and resp. conf., REPORT req. ind., SETUP req. ind. SETUP resp. conf., and SETUPREJECT req. ind.Item Relationship Req. i

34、nd. Resp. conf.Network-provided or Network-verified Calling Line Identification rcMandatory GVNS User Group Identification rc MandatoryDialed Number rcMandatory OptionalRouting Number rc MandatoryTerminating Network Routing Number rc MandatoryTerminating Participating Service Provider Identification

35、 rc MandatoryOn-net/Off-net Indicator rc MandatoryAlternate Terminating Network Routing Number rc OptionalTransit Indication rc MandatoryGVNS Service ID rcOptional 14 Recommendation Q.85 (02/95)The following items of information are conveyed in the ENQUIRY 2 req. ind. and ENQUIRY 2 resp. conf. infor

36、mationflows:TABLE 6-2/Q.85Information items for ENQUIRY 2 req. ind. and resp. conf. information flows6.7.2.3 Definition of information flow ENQUIRY 3 req. ind. and resp. conf.ENQUIRY 3 req. ind. is used to request remote GVNS call screening and routing information translation. This is aconfirmed inf

37、ormation flow and ENQUIRY 3 resp. conf. is used to carry back the information on rejecting the call or onhow to route the call. This information flow is within the rdrelationship.The following items of information are or may be conveyed in the ENQUIRY 3 req. ind. and ENQUIRY 3 resp. conf.information

38、 flows:TABLE 6-3/Q.85Information items for ENQUIRY 3 req. ind. and resp. conf. information flows6.7.2.4 Definition of information flow REQ.INFO req. ind. and resp. conf.REQ.INFO req. ind. is used to request collection of user provided information. This is a confirmed information flow andREQ.INFO res

39、p. conf. is used to carry back the information requested. This information flow is within the rcrelationship.Item Relationship Req. ind. Resp. conf.GVNS User Group Identification rbMandatory Dialed Number rbMandatory Routing Number rb MandatoryTerminating Network Routing Number rb MandatoryAlternate

40、 Terminating Network Routing Number rb OptionalOn-net/Off-net Indicator rb MandatoryAuthorization Code rbMandatory (Note) NOTE The authorization code information item is only applicable in the case of the remote access arrangement.Item Relationship Req. ind. Resp. conf.GVNS User Group Identification

41、 rdMandatory Dialed Number rdOptional Terminating Network Routing Number rdMandatory MandatoryAlternate Terminating Network Routing Number rdOptional OptionalGVNS Service ID rdOptional Recommendation Q.85 (02/95) 15The following items of information are or may be conveyed in the ENQUIRY 3 req. ind.

42、and ENQUIRY 3 resp. conf.information flows:TABLE 6-4/Q.85Information items for REQ. INFO req. ind. and resp. conf. information flows6.7.2.5 Definition of information flow INFORM 1 req. ind. and resp. conf.INFORM 1 req. ind. is used to carry GVNS information during the setup of the call. This is a co

43、nfirmed informationflow. This information flow is within the rarelationship.The following items of information are contained or may be conveyed in the INFORM 1 req. ind. and INFORM 1 resp.conf. information flows:TABLE 6-5/Q.85Information items for INFORM 1 req. ind. and resp. conf. information flows

44、Item Relationship Req. ind. Resp. conf.Request for Authorization Code Indication rcMandatory Authorization Code rcMandatoryItem Relationship Req. ind. Resp. conf.GVNS Service ID raMandatory Routing Number raMandatory Terminating Network Routing Number raMandatory GVNS User Group Identification raMan

45、datory Dialed Number raOptional Alternate Terminating Network Routing Number raOptional(Note 1)OptionalOriginating Participating Service Provider Identification raMandatory(Note 2)Terminating Participating Service Provider Identification raMandatory(Note 3)Transit Indication raMandatory(Note 4)Termi

46、nating Access Indication ra MandatoryNOTES1 The FE1 may send an Alternate Terminating Network Routing Number to the FE3 so that the FE3 may use this informationto route the call to an alternate termination. However, the FE3 may derive an alternate termination address directly withoutrelying on the F

47、E1 to provide this information. In the latter case, the FE1 does not need to send an Alternate Terminating NetworkRouting Number to the FE3; however, the FE3 may send back to the FE1 the Alternate Terminating Network Routing Numberthat it derives and uses to route the call. Such information is valua

48、ble when tracing customer trouble reports.2 This information is needed for the terminating network or an intermediate network (in the case of transit calls) to identify theoriginating participating service provider to support the settlement process.3 This information is needed for an intermediate ne

49、twork that supports GVNS to identify the terminating participating serviceprovider in the transit scenario. In its physical realization, this piece of information may be specified in the Routing Numberinformation element.4 This information is needed for the connecting network that supports GVNS to differentiate a transit call from a non-transitcall. In its physical realization, this piece of information can be deduced from the comparison of the connecting networksidentification with the information in either