1、 ETSI GS MTC 008 V1.1.1 (2010-05)Group Specification Mobile Thin Client (MTC);Use Cases and RequirementsETSI ETSI GS MTC 008 V1.1.1 (2010-05)2Reference DGS/MTC-0001 Rqmts Keywords ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret
2、 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 available in more than one electronic version or
3、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 a specific network drive within ETSI Secretari
4、at. 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 errors in the present document, please send yo
5、ur 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 in all media. European Telecommunications Stand
6、ards 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 and of the 3GPP Organizational Partners. LTE
7、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 008 V1.1.1 (2010-05)3Contents Intellectual Property Rights 5g3Foreword . 5g3In
8、troduction 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 System overview 9g34 Requirements 11g34.1 Thin client device requirements . 11g34.1.1 High level requirements 11g34.1.
9、1.1 Device capabilities 11g34.1.1.2 User Input Interfaces . 11g34.1.1.3 Display 11g34.1.1.4 Power consumption . 11g34.1.2 Hardware Requirements . 11g34.1.2.1 Display 11g34.1.2.2 Battery performance 11g34.1.2.3 Wireless Communication Network . 12g34.1.3 Software Requirements . 12g34.1.3.1 System OS .
10、 12g34.1.3.2 Mobile Communication Stack . 12g34.1.3.3 Resident applications 12g34.2 Protocol Suite . 12g34.2.1 End-to-end requirements . 12g34.2.2 Delay and jitter . 12g34.2.3 Guaranteed delivery 13g34.3 Server System / technology 13g34.3.1 Application Image Server . 13g34.3.2 Data Storage Server 13
11、g34.4 Service Management Framework . 13g34.4.1 User Management . 13g34.4.1.1 Categories of Users . 13g34.4.1.2 User authentication 14g34.4.1.3 Logging Users activities 14g34.4.2 Infrastructure . 14g34.4.2.1 Infrastructure management 15g34.4.2.1.1 Topology of infrastructure . 15g34.4.2.1.2 Status of
12、infrastructure 15g34.4.2.1.3 Software Level - Configuration on each server . 17g34.4.2.1.4 Software Level - Installed applications on each server . 17g34.4.2.1.5 Session Management . 17g34.4.3 Business Support 18g34.4.3.1 Billing . 18g34.4.3.2 Reporting . 18g3Annex A (informative): Examples of mobil
13、e thin client scenarios . 19g3A.1 Scenario 1: Bringing the hospital to the patients home . 19g3A.2 Scenario 2: Getting in touch with Paris 19g3ETSI ETSI GS MTC 008 V1.1.1 (2010-05)4A.3 Scenario 3: Keep scoring at school 20g3A.4 Scenario 4: Mobile thin office 20g3Annex B (informative): General aspect
14、s 21g3B.1 Social aspects . 21g3B.2 Application aspects. 21g3B.3 Technical aspects 22g3Annex C (informative): Information on parameters used in the present document 23g3C.1 Delay: . 23g3C.2 Bandwidth 23g3C.3 Jitter 25g3Annex D (informative): Bibliography . 26g3History 28g3ETSI ETSI GS MTC 008 V1.1.1
15、(2010-05)5Intellectual 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: “Intellectua
16、l 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 investigatio
17、n, 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 Specification (GS
18、) has been produced by ETSI Industry Specification Group (ISG) Mobile Thin client Computing (MTC). Introduction The present document defines a set of consistent and complete requirements for a future mobile thin client system. An important consideration is that the mobile thin client system should w
19、ork with the current available Internet and wireless communication network infrastructure (including the access network, the aggregation network and the core network). Requirements with respect to this network partitions are defined. Besides the network itself, additional infrastructural components
20、are important for the mobile thin client system. Their function and the rationale for constructing the system out of these building blocks are described in the deliverable and requirements of the components themselves are defined. Namely those basic building blocks are the thin client server, the ap
21、plication image server, the data storage server, the thin client mobile device and the service management framework. The defined requirements are categorised into mandatory and optional. The present document is a requirement document only, and does not describe technical solutions. Motivated by the
22、fact that the issues of security, detailed AAA implementation, seamless handover and the optimization of external resources (like application image server or data storage server) are amply addressed in other standardisation effort; the present document does not address these issues. ETSI ETSI GS MTC
23、 008 V1.1.1 (2010-05)61 Scope The present document is intended to define a set of consistent and complete requirements. Nevertheless, during the ongoing discussion, new requirements can come up. Hence, from the start on, the requirements (as well as the initial architecture) are intended to be relev
24、ant and adequate for future mobile thin client systems, while exhibiting the necessary flexibility to cope with new requirements. The basic idea considered in mobile thin client system concerns nomadic users and addresses remote application access. User terminals considered range from laptops to sma
25、rt phones, and applications should be delivered transparently (i.e. without changing the application code itself). This basic setting is further developed in the present document into more specific scenarios. The following issues are excluded from the present document: Security; detailed implementat
26、ions of AAA including billing mechanism; seamless handover; optimization of external resources, like application image server or data storage server. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific
27、references, only the cited version applies. For non-specific 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. NOT
28、E: While any hyperlinks included in this clause were valid 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 DGS MTC 009: “Mobile Thin Client (MTC); Archi
29、tecture“. 2.2 Informative references The 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. i.1 Niraj Tolia, David G. Andersen, M. Satyanarayanan “Quantifying Interactive User Experience on T
30、hin Clients“, IEEE Computer, Volume 39 - 3, pages 46-52, March 2006. i.2 Niraj Tolia, David G. Andersen, M. Satyanarayanan: “The Seductive Appeal of Thin Clients“, February 2005. i.3 Pantel, L.: “On The Impact of Delay on Real-Time Multiplayer Games. International Workshop on Network and Operating S
31、ystem Support for Digital Audio and Video“, 2002. i.4 Dick, M.: “Analysis of Factors Affecting Players“ Performance and Perception in Multiplayer Games“, Proceedings of 4th ACM SIGCOMM workshop on Network and system support for games, 2005. ETSI ETSI GS MTC 008 V1.1.1 (2010-05)7i.5 Deboosere, L., De
32、 Wachter, J., Simoens, P., De Turck, F., Dhoedt, B., and Demeester, P.: “Thin Client Computing Solutions in Low- and High-Motion Scenarios“, in Proceedings of the Third international Conference on Networking and Services (June 19 - 25, 2007). ICNS. IEEE Computer Society, Washington, DC, 38. i.6 ITU
33、Recommendation Y.1541 (February 2006): “Network performance objectives for IP-based services“. i.7 “VirtualGL - Background“ online. i.8 A.F. Wattimena, et al.: “Predicting the perceived quality of a First Person Shooter: the Quake IV-model“, 5th Workshop on Network - leave the old session and start
34、a new one with the new settings (this is not desired since too many sessions per user might be left on servers, without real necessity); - keep the old session and disconnect the ongoing connection. The exact definition of the attributes and behaviour of the previous different sessions will be speci
35、fied in the architectural design and technical details. ETSI ETSI GS MTC 008 V1.1.1 (2010-05)18No Requirements 37 User login session SHALL be stateful (such that the same log-in can be used for different applications in the same session) 38 SMF SHALL support session persistence as defined above 39 S
36、MF SHOULD support server session migration 40 SMF SHOULD support server session mobility 41 SMF SHOULD support terminal mobility 42 USER SHOULD be able to have more than one session active at a time 43 Session migration service SHALL allow control from the user 44 An authorized administrator SHOULD
37、be able to allocate specific resources users or groups of users 45 An authorized administrator SHOULD be able to define user profiles (e.g. desktop appearance, ) 4.4.3 Business Support 4.4.3.1 Billing No Requirements 46 SMF charging and invoicing services SHALL be able to export charging and invoici
38、ng data in standard charging / invoicing formats 47 SMF SHOULD Support more than one billing system * NOTE: There is more than one billing system available, e.g. http:/ (commercial), http:/ (open source), http:/ (software directory). It has to be decided and document in D2.2. 4.4.3.2 Reporting No Re
39、quirements 48 SMF reporting services SHALL be able to export data in standard format for Business Information tools 49 SMF reporting SHOULD Support more than one Business Information system ETSI ETSI GS MTC 008 V1.1.1 (2010-05)19Annex A (informative): Examples of mobile thin client scenarios A.1 Sce
40、nario 1: Bringing the hospital to the patients home Conveniently installed in his seat, Mr. GEPRACTI (general practitioner) was watching a theatre performance given by his sons school when his PA (personal assistant) rang: one of his patients had some troubles and need to be examined at once! When a
41、rriving to patients house, Mr. GEPRACTI wanted, as usual, to access all his records (notes, digitised X-rays, multi-dimensional scans, etc.) by simply connecting his PA to his office server. As the house was in a quite isolated place and as the mobile services were not provided there, Mr. GEPRACTI o
42、btained the connection through the patients wireless/fixed Internet connection. The images and short video footages were transmitted in lower resolution, adapted to his device characteristics and the available bandwidth. For clearer views (compulsory in some diagnosis issues) higher resolution image
43、s could be displayed by connecting the PA to the patients TV-or HDTV-set. During the examination, some patients external symptoms determined him to get a second opinion from a medical specialist. Therefore he turned his PA in the high resolution camera mode and dialled the number of the specialist.
44、The video was then stored on the office server of Mr. GEPRACTI for future recapitulation and transmitted to the specialist. As the examination showed nothing serious in the opinion of the specialist, they closed the call and Mr. GEPRACTI wrote down the prescription. He was back to the sons performan
45、ce just before the end if only his son did not notice his absence! A.2 Scenario 2: Getting in touch with Paris For five years already, Mrs. and Mr. JATUBE (Just some American Tourists Uninformed but with Big Expectations) have wanted to visit Paris. Today their dream starts to become true: during hi
46、s lunch break, Mr. JATUBE connected his mobile phone to the Internet and won an auction for a very low cost holiday, hotels and plane tickets from MiddleOfNoWhere to Paris included. Of course, they are very happy but some concerns also arise. As the departure will be in about one week, they will hav
47、e no time either for informing themselves about Paris main sights or for buying a good guide book. Moreover, they are perfectly aware that French is spoken down there! Once in Paris, they understand that their concerns were unfounded. What a chance the city council exploits the virtual city applicat
48、ion “Virtual Paris“! On the first morning, they decided to visit Notre Dame and the Latin Quarter. On the streets, they immediately noticed some access points, where some decent people (just like them, with caps and sport shoes) queued-up. It was explained that these access points are a kind of ligh
49、t terminal, connected to the servers of the city hall and providing tourists with information about the neighbourhood: historical, architectural, shopping, etc. Moreover, it is free! An explicative notice also let them know that this service, with even more options, can be accessed by a simple cell phone. Mr. JATUBE took out his phone and connected it to the servers of the city hall. It was a pleasant surprise: his cell phone
