ETSI GS MTC 009-2010 Mobile Thin Client (MTC) Architecture《移动精简型计算机(MTC) 架构(版本1 1 1)》.pdf

《ETSI GS MTC 009-2010 Mobile Thin Client (MTC) Architecture《移动精简型计算机(MTC) 架构(版本1 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI GS MTC 009-2010 Mobile Thin Client (MTC) Architecture《移动精简型计算机(MTC) 架构(版本1 1 1)》.pdf（23页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GS MTC 009 V1.1.1 (2010-05)Group Specification Mobile Thin Client (MTC);ArchitectureETSI ETSI GS MTC 009 V1.1.1 (2010-05)2Reference DGS/MTC-0002 Arch Keywords access, adaptation, architecture, mobile, multimedia, remote ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:

2、+33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made ava

3、ilable in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on

4、a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find

5、errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction i

6、n all media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members

7、 and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MTC 009 V1.1.1 (2010-05)3Contents In

8、tellectual Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 High-level architecture . 6g34.1 Overview 6g34.2 Basic Building Blocks 7

9、g34.3 Philosophy of the architecture 8g35 Functional Architecture 9g35.1 General Overview. 9g35.2 Elaboration of the architecture . 9g35.2.1 Introduction to the Architecture 9g35.2.2 Top level architecture description (level 0) 10g35.2.2.1 Network considerations . 10g35.2.2.2 End point consideration

10、s . 11g35.2.2.3 Self Management 12g35.2.2.4 Self Data 12g35.2.2.5 Top level view of the architecture . 12g35.2.2.6 Top level architecture 13g35.2.3 Level one architecture description 14g35.2.3.1 End-to-end communications . 14g35.2.3.2 Mobile Thin Server and its hosting environment 15g35.2.3.3 System

11、 architecture: level one. 16g35.2.3.4 Level one architecture . 17g35.2.4 Level two architecture description 17g35.2.4.1 Introduction to level two . 17g35.2.4.2 Architecture of TCSC . 18g35.2.4.3 Level two architecture . 18g3Annex A (informative): Scenario mapping 20g3History 23g3ETSI ETSI GS MTC 009

12、 V1.1.1 (2010-05)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Int

13、ellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no inve

14、stigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Group Specifica

15、tion (GS) has been produced by ETSI Industry Specification Group (ISG) Mobile Thin client Computing (MTC). Introduction The present document is intended to define a technical framework of the mobile thin client system architecture. This includes basic building blocks, components detailed at differen

16、t levels and appropriate interfaces between them. ETSI ETSI GS MTC 009 V1.1.1 (2010-05)51 Scope The present document presents the architecture for a mobile thin client system, consistent with the requirements articulated in the work item “Mobile thin client system requirements“ of the MTC ISG. The d

17、eliverable first describes a high-level architecture, in order to position the approach taken, and subsequently details the functional architecture at three different levels. Components and their interactions are identified, together with their interfaces. Non-normative scenarios indicating a possib

18、le implementation of the required functionality, are included as annex to the present document. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-sp

19、ecific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were v

20、alid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. 1 ETSI MTC 008: “ Mobile Thin Client (MTC); Use Cases and Requirements“. 2.2 Informative references T

21、he following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definit

22、ions apply: Service Management Framework (SMF): to manage the thin client service, a whole range of management components are required (such as authentication and authorization, network management, business management, session management, server management, monitoring, etc.). The collection of these

23、 management components is called the Service Management Framework (SMF). It should be noted that for scalability and efficiency reasons, the components of the SMF will be distributed. Some of the management components will run on the client, some on the server hosting the thin client session and som

24、e on dedicated management servers thin client protocol: is responsible for delivering user input (such as keystrokes, mouse events but also data from for example webcams, etc.) to the server and sending audiovisual output from the server to the client ETSI ETSI GS MTC 009 V1.1.1 (2010-05)6thin clien

25、t service: is a service offering remote execution of applications. While the application logic is actually running on a remote server, output is transmitted to the terminal the user interacts with. Likewise, the user input is captured at the terminal, and transmitted to the remote server for proper

26、handling. This basic service can be supplemented with additional functionalities, such as authentication, remote data storage and management, automatic application installation, etc. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ADS Application Delive

27、ry Service DSS Data Storage Service E2E End to End E2EAUTHN End to End authentication E2EAUTHZ End to End authorization E2ECONN End to End connection E2ELOGISTICS End to End logistics ENV ENVironment ESS Entity Subscription Service I Interface MTC Mobile Thin Client (implementing the client part of

28、the service) MTH Mobile client Hosting environment MTS Mobile Thin Server (implementing the server part of the service) NET NETwork NETC NETwork Control QOS Quality of Service SDM Self Data Manager SLM Self Logistics Manager SMF Service Management Framework TCS Thin Client Service TCSC Thin client s

29、ervice core TCSCC Thin client service core core (i.e. the core of the TCSC) 4 High-level architecture 4.1 Overview In Figure 1, the high-level software architecture is illustrated. Six basic building blocks can be distinguished: the Mobile Thin Client, the Mobile Thin Server, the Service Management

30、Framework, the Network Control, the Data Storage Service and the Application Delivery Service. Figure 1: High-level software architecture ETSI ETSI GS MTC 009 V1.1.1 (2010-05)7In Figure 1, only one client (i.e. Mobile Thin Client) and one server (i.e. Mobile Thin Server) are visualized. The multi-us

31、er aspect of the architecture is shown in Figure 2. Multiple clients can be connected to the same physical Thin Client Server running a separate User Session for each connected user. To monitor and manage the Thin Client Server, a part of the Service Management Framework (i.e. the Thin Client Server

32、 Management component) is installed at every Thin Client Server. The Mobile Thin Server runs on top of the Thin Client Server Operating System. Figure 2: Multi-user aspect of the system Architecture 4.2 Basic Building Blocks From a high-level perspective, the functionality of the 6 basic blocks is s

33、ummarized Table 1. In clause 5, an exhaustive description of the functionality of all basic blocks will be discussed. ETSI ETSI GS MTC 009 V1.1.1 (2010-05)8Table 1: Basic building blocks of architecture Basic Building Block Description Mobile Thin Client This is the software running on the mobile cl

34、ient device. When a user wants to start the thin client service, he starts this client on his thin client device. Service Management Framework (SMF) When a user logs in, he has to identify himself to the SMF, which is responsible for managing the complete thin client service and guaranteeing the des

35、ired QoS to the users. The components of the SMF are distributed over the different building blocks. Mobile Thin Server This is the software running on the Thin Client Server selected by the SMF. All applications of the users are executed in their Mobile Thin Server. Audiovisual output from a users

36、applications is transported over the network to the users device. Input from the user is transported in the opposite direction. Network Control This is the service of the network operator. The SMF will interact with the Network Control block to set the appropriate QoS classes for the traffic between

37、 the Mobile Thin Client and the Mobile Thin Server. Data Storage Service This service maintains the personal data of the users. Application Delivery Service For scalability reasons (not every application should be installed in every Mobile Thin Server), applications are delivered by an application d

38、elivery service to the Mobile Thin Server. 4.3 Philosophy of the architecture A first introduction of the system architecture is shown in Figure 3. Details on the functional aspects of the system architecture will be given in clause 5. Two major components can be distinguished: the Mobile Thin Clien

39、t (MTC) and the Mobile Thin Server (MTS). Both entities communicate with each other over the network and exchange thin client protocol messages and management data. The architecture is quite symmetric, with some additional components on the MTS side to support specific services (e.g. data storage se

40、rvice). Figure 3: Overview of the System Architecture A short description of the components of Figure 3 is given in Table 2. Note that the functionality or implementation might differ between the MTC and MTS side. This rather high-level description can help the reader to understand the composition o

41、f the overall system architecture. ETSI ETSI GS MTC 009 V1.1.1 (2010-05)9Table 2: Components of the System Architecture TCSC_E2ECONN Starts a connection between MTC and MTS, and thus acts as a portal to the system. TCSC_E2EAUTHN Authentication of MTS and MTC. TCSC_E2EAUTHZ Authorization of MTS and M

42、TC. TCSC_E2ELOGISTICS Negotiates session settings, reserves resources, MTS_MON Monitors the state of the MTS. MTS_ADM Handles administration tasks. MTS_NET (De)packetizes data, sends and receives network packets (general network functionality), including network control functionality. MTS_SDM Contai

43、ns data about the system, and provides a means for interacting with it. MTS_SLM Handles self management tasks such as resilience. MTS_DSS Endpoint to deal with data storage service. MTS_ADS Handles application delivery from application delivery service. MTS_ESS Handles access to the entity subscript

44、ion service. MTS_BUS Provides required information for external business systems. TCSCC Handles the core communication between MTC and MTS. This basically means the thin client protocol communication, functionally equivalent to e.g. VNC. RDP, NX, 5 Functional Architecture 5.1 General Overview As alr

45、eady stated in the requirement document 1, the mobile thin client service as an entity would operate within the following three main environments: The Terminal Device environment is composed of the terminal hardware and software. This is the environment where the Mobile Thin Client will operate. The

46、 Hosting environment is the environment, where the Mobile Thin Server will operate. This environment is supposed to provide components that are not included in the system scope but that are necessary for the Mobile Thin Server to communicate with the external world. For instance, components needed f

47、or configuring routers are not in the scope of the system. Another example is that the service should provide billing data to external billing systems but should not include a billing system. So if a billing system is needed it should be considered as part of the environment of the system. Network e

48、nvironment is the pipe that links the two previous environments. This environment is composed of one or many networks. This environment is taken into account because the Mobile Thin Client and Server will need to interact with it, for instance to ask for specific network QoS support. A goal of the s

49、ervice is to allow end-to-end network adaptation in order to provide the best possible end user experience combined with the best possible energy economy. 5.2 Elaboration of the architecture 5.2.1 Introduction to the Architecture To elaborate on the architecture, we proceed using an approach that will consist of: Elaborating the top level (level 0) architecture layer. Recursively building detailed layers (level 1 up to level 3): to achieve this, each functional block in a previous layer will be split into deeper sub-blocks, according to the sub-functionality the