ITU-T Y 130-2000 Information Communication Architecture Series Y Global Information Infrastructure and Internet Protocols Aspects Global Information Infrastructure - General《信息通信结构.pdf

《ITU-T Y 130-2000 Information Communication Architecture Series Y Global Information Infrastructure and Internet Protocols Aspects Global Information Infrastructure - General《信息通信结构.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 130-2000 Information Communication Architecture Series Y Global Information Infrastructure and Internet Protocols Aspects Global Information Infrastructure - General《信息通信结构.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、I NTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOM M U N I CATI ON STANDARDIZATION SECTOR OF ITU YA30 (03/2000) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE AND INTERNET PROTOCOL ASPECTS Global information infrastructure - General Information communication architecture ITU-T Recommendation Y.130 (F

2、ormerly CCITT Recommendation) ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE AND INTERNET PROTOCOL ASPECTS _ GLOBAL INFORMATION INFRASTRUCTURE General Services, applications and middleware Network aspects Interfaces and protocols Numbering, addressing and naming Operation, administ

3、ration and maintenance Security Performances General Services and applications Architecture, access, network capabilities and resource management Transport Interworking Quality of service and network performance Signalling Operation, administration and maintenance Charging INTERNET PROTOCOL ASPECTS

4、Y.100-Y.199 Y.200-Y.299 Y.300-Y.399 Y .40O-Y .499 Y SOO-Y .599 Y.600-Y .699 Y .70 provide easy access to new services. ensure effective use of network assets; simplify deployment of network technologies; enable evolution to new services and network technologies; provide smooth transition to the GI1

5、(Global Information Infrastructure). identi the functions and behaviours between the user and network facilities in terms of ensure adequate decoupling between end user and network technologies; define functions and behaviour of middleware components; identify points at which open interfaces might b

6、e defined. e For network operators the purpose of the architecture is to: O e e e To meet the above, the ICA is designed to: e middleware services; e e e 3 The scope of the architecture defined in this ITU-T Recommendation covers the following aspects of communication: a) user-to-user communication;

7、 b) c) machine-to-machine communication. Scope and field of application user-to-machine communication (and vice versa); In this context “user“ covers both “end-user“ as well as “user“ as a client in any client server situation. In addition, content providers and service providers may also be conside

8、red to be users. Thus, the scope is not restricted to a narrow interpretation, i.e. limited to traditional telecommunications products and services. Rather, the scope covers any combination of products and service suppliers involved in provision of the above communications. For example, local area n

9、etworks, cable networks, IP-based networks, and their related services are included within the scope of ICA, as well as ITU-T defined networks and their related services. Such services may involve the transfer of data, voice, or video, or some combination thereof. Similarly, service providers may in

10、clude, among others, local area network operators, cable network operators, Internet Service Providers, entertainment service providers, etc. In short, the scope involves any of the parties and technologies involved in the moving of, andor, the related processing of such information. This is not to

11、say that the ITU-T will define all the component elements of the architecture. It may be expected that the particular specialisms of other standards organizations internal to, and external to, the ITU-T will be taken into account. In this regard, the architecture is expected to draw on outside exper

12、tise of internal and external organizations, and will benefit from the appropriate inter- organizational collaboration. Accordingly, the ICA will take account of a number of existing architectures from other organizations such as TINA2, OMG3, GSM-Mou4, ODP-RM5, etc. with an initial focus on function

13、s, reference points, and roles. 3.1 General positioning The scope of ICA middleware is wide and functionality can be combined in many different ways. Middleware service components can, in general, be presented in terms of three functional aspects: a b) c functionality which represents the vertical a

14、spects; functionality which represents the horizontal aspects; functionality which represents infrastructure aspects. 3.2 Vertical aspects The vertical aspects are shown separately in Figure 1, which illustrates that ICA is positioned to provide functionality to intelligently bridge the gap between

15、user applications and raw transport facilities. In accordance with the GI1 framework, as defined in ITU-T Recommendation Y.110, the primary “area of concern“ of the ICA in relation to the GI1 is shown in Figure 1. Telecommunications Intelligent Network Architecture. 3 Object Management Group. Global

16、 Systems for Mobile Communications - Memorandum of Understanding Association. 5 Open Distributed Processing - Reference Model. Application Functions I -( Application Programming Interface )- Baseware Programming Interface Baseware Functions GI1 : TI 315820-99 II Area of concern Figure 1N.130 - Verti

17、cal scope and relationship between the ICA and the GI1 ICA middleware functions will, in general, use both GI1 transport and processingstorage classes of baseware service components. This ITU-T Recommendation addresses middleware interoperating with transport service components. It is envisioned tha

18、t the ICA model will be expanded to interoperate with processingstorage service components. 3.3 Horizontal aspects Figure 2, taken from ITU-T Recommendation Y.110 shows the horizontal aspects, in the sense that ICA functionality will be distributed at appropriate points throughout the network, to fo

19、rm a set of geographically distributed cooperating entities. The figure is intended to show that the scope of ICA embraces the distribution of intelligence at various points in the “path“ between the end points. This figure is for explanatory purposes only, and is not intended to indicate any specif

20、ic components or specific distribution thereof. Information f r appliance Customer Network IT enabling access from existing legacy systems to services deployed in future systems in the ICA; i i) enabling access fi-om future systems of the ICA to existing services. NOTE - Accessibility from future sy

21、stems in the ICA to existing services is required under the condition that such interworking does not give undue strong constraint to the development of future systems. The ICA should enable the operators (service providers) to control: policy aspects of service provision; contractual aspects of ser

22、vice provision; service availability and advertising aspects of service provision. 6 The ICA guides the design of advanced information communications services and the systems supporting their provision. The principle of separating physical-connection-oriented call processing from service-oriented ca

23、ll processing is advanced by ICA middleware service components. The notion of calls is replaced by the notion of service instances and communication sessions. For example, this would be the case for connectionless services and cases where multiple calls and multiple streams are involved in a given s

24、ession. The ICA will be defined in a way that encompasses many different service architectures. In this regard, many different service architectures may be deployed to implement the ICA. The basis of the ICA framework is that it provides for the clear separation of concerns. For example, service con

25、trol from connectivity control and Signalling from transport network. Service control components provide the means to access, control, and manage services and connectivity. Interaction between these components and the infrastructure and Signalling network is provided through Middleware Programming I

26、nterfaces (MPIs) and Baseware Programming Interfaces (BPIs). The remainder of this clause outlines some of the basic concepts, assumptions and principles underlying the design of the ICA. Basic concepts, assumptions and principles for ICA 6.1 Middleware services ICA is the intermediary layer where i

27、ndependent middleware services intelligently bridge the gap between content applications and network transport services. This is illustrated in Figure 1. This intermediary layer will enable the transformation from a voice-dominated network to a data- dominated network. The ICA architecture has been

28、designed to meet the challenge of enabling multimedia communication across a diverse landscape of content providers, service providers and network providers. Multimedia was chosen because it is a ubiquitous element in the way people work, play, and conduct business. It also places high demands on ne

29、twork infrastructures to deliver quality-of- service guarantees. The value of any architecture is best realized when capabilities are expressed in terms of functions that solve real needs or challenges. Challenges that are persistent over time are ideal candidates. The network challenge is to provid

30、e infrastructure services that seamlessly deliver multimedia information in a way that preserves natural human interactions across diverse set of data networking technologies and applications. In the context of this work, the definition of multimedia entails the technical aspects of using one or mor

31、e media types (text, images, graphics, speech, audio, video, and data files) for the purpose of communicating across transmission, storage, access and content creation applications. Seamless delivery of multimedia information between communicating parties (i.e. human-to-human and human-to-machine) e

32、ncompass the following: e user interface and information presentations; organization, storing and retrieving of multimedia information; searching, browsing of multimedia documents and libraries; formatting, compression and coding of various media types; e multiplexing and control coordination; end-t

33、o-end QoS and QoS Intenvorking; e processing of multimedia information; e e e e .e interactive voice and video communication. all aspects of multimedia processing are part of the network. Some persistent capabilities, such raphical User Interface (GUI) presentation and processing of information, nat

34、urally reside in the of end user applications. Since ICA is positioned as network-based middleware, the . to be supported directly reflect the location and movement of information across technologies. ICA capabilities encompass the transport or movement of information een end users and servers. At t

35、he most basic level these capabilities evolve around formatting d movement of information bits, and any necessary transformations thereof. the ICA middleware represents the service-processing layer. Service processing is carried out in an open aistributed way: e by structuring services into object#;

36、 by relying on a distributed processing platform for open interaction and cooperation among by having a technology-independent view of the network resources, by way of a BPI which e objects; encapsulates implementation details and allows them to be seen by the Middleware as object interfaces; e In t

37、his ITU-T Recommendation the word “object“ is used in the sense of an abstract specification technique, and not in the sense of an implementation technique. e by having a technology-independent support of applications, by way of an API which encapsulates deployment details and allows them to be seen

38、 by the Middleware as objects. Within the context of the GII, the ICA: should focus upon a limited number of standardized generic APIs, MPIs, and BPIs allowing services built on these interfaces to be standardized, in an open-ended way that allows providers to compete with differentiated services; e

39、 should be modular design framework with standardized interfaces between the modules providing the flexibility to satisfy a wide range of “enterprise role“9 requirements, and a flexibility to allow service providers to adjust their interfaces as their requirements change but in a cost effective and

40、efficient manner; e should position the intelligence of the system at the highest level so that open interfaces are should separate areas of concern, i.e. applications from infrastructure by way of middleware; should support evolution from IP-based networks, ISDNIN, GSM, CTM, etc.; should allow for

41、the provision of high-level APIs to service providers so that they have a should dictate concepts, rules, guidelines, prescriptive models for service creation; should give focus to the vertical interfaces (APIs, MPIs and BPIs) for the Middleware, should ensure decoupling of Transport technology from

42、 specific services. provided for service and network control; e e e high level of network control in order to build differentiated services; 0 e which is an abstract execution environment for services; e The conceptual aspects of the ICA include generic design concepts like middleware components, se

43、rvice instances and communication sessions. Conceptual support is meant to enable service and system designers to follow the key design principles. Conformance to these principles should result in good and flexible design of open-ended systems offering a multiplicity of (customized) quality services

44、. Such systems also exhibit service flexibility allowing public and proprietary services to be integrated and combined in a modular and flexible way. Other key design principles of the ICA include: e Coherent design of management and control. Customization and personalization of services. Nested ser

45、vices for defining and providing new services. Separation of application and session as well as resource and communication-oriented Separation of media services from their control and management. Separation of service access from service core. Reference Points at which it may be desirable to have op

46、en interfaces. e e e problems. e e e System-independent modelling of services. e The application of this collection of design principles and concepts is expected to be adequate to support modelling of services, because of their intrinsic generality. 9 Business roles as perceived by applying the ODP-

47、RM include: Content Provider, Service Provider (Brokerage), Customer (User), and Transport Network Provider, etc. A role is a set of activities carried out by a stakeholder. A stakeholder can play different roles. A stakeholder is an individual or organization that partakes in some activity related

48、to a business. 6.2 The ICAS focus on middleware is as defined in ITU-T Recommendation Y.110, “Global Information Infiastructure principles and framework architecture“. The primary area of concern of ICA is the Middleware functions as shown in Figure 3. Relationship to GI1 Recommendation Y.11 O Appli

49、cation Programming Interface Baseware Programming Interface Structural Communication role and networking Distributed service provision Generic communications Control functions Transport functions T1315830-99 Figure 3N.130 - Area of concern (extracted from ITU-T Recommendation Y.110) ITU-T Recommendation Y.110 should be consulted for further information on this subject and the related general issues of players, role, domains, etc. NOTE - In some cases, ITU-T Recommendation Y. 1 10 for example, the Baseware Programming Interface shown above has been termed the Basic Programming Inte