1、 Reference numberECMA TR/102:2010Ecma International 2010ECMA TR/102 1stEdition / December 2010 Personal Networks Overview and Standardization Needs COPYRIGHT PROTECTED DOCUMENT Ecma International 2010 Ecma International 2010 i Contents Page 1 Scope 1 2 References . 1 3 Terms and definitions . 2 4 Ba
2、ckground and General Concepts 4 4.1 Service Level 8 4.2 PN Level . 8 4.3 Connectivity Level . 9 5 PN Configurations . 9 5.1 PN with 1 User . 9 5.2 PNs with multiple Users 9 5.3 PN owned by a Legal Entity . 10 5.4 EPN using Offered Services . 11 5.5 EPN using Non-PN Services 11 5.6 User to User Telec
3、ommunication 2 PN configuration 12 6 Requirements . 12 6.1 Connectivity and Mobility Support 13 6.2 Security and Privacy . 13 6.3 Auto Configuration and Self-organisation 13 6.4 Quality. 13 6.5 Management . 13 6.6 Scalability . 14 7 PN Networking . 14 7.1 PN Creation and Dissolution 15 7.2 Device Im
4、printing, Node Initialisation and Configuration . 15 7.3 Node Addressing . 15 7.4 Network Cluster Formation 15 7.5 Intra-cluster Routing . 15 7.6 Gateway Node 16 7.7 Inter-cluster communication, tunnelling and Routing . 16 7.8 External communication . 17 7.8.1 Via proxies . 17 7.8.2 Direct L2 commun
5、ication and tunnelling on behalf of proxies 17 7.9 Mobility in PNs . 18 7.9.1 Device (terminal) Mobility . 18 7.9.2 Personal Mobility . 18 7.9.3 Session Mobility 18 7.9.4 Service Mobility . 18 7.10 Support for Non-IP IP or Resource Constrained Devices . 18 7.11 Other Technical Considerations 18 8 St
6、andardisation Needs 18 8.1 Quality. 19 8.2 Credential Management and imprinting 19 8.3 Node initialisation and configuration 19 8.4 Uniform network interfacing 19 8.5 Network Cluster formation and maintenance . 19 8.6 Network Cluster routing 19 8.7 Inter-Network Cluster routing and tunnelling . 19 8
7、.8 External communication . 20 ii Ecma International 20108.9 Resource and service discovery and management .20 Ecma International 2010 iii Introduction This Ecma Technical Report explores Personal Networks (PNs) and their extensions. PNs provide secure and ubiquitous communication between (personal)
8、 devices over multiple network technologies. PNs provide automatic configuration of networking, security, and offers users access to their Services across their PNs. This Technical Report introduces the PN architecture and identifies various communication scenarios as well as standardization needs o
9、f PNs. This work is based on - and Ecma acknowledges - the valuable results from EU FP6-IST projects Magnet and Magnet Beyond (see 33 and Dutch Freeband PNP2008 (see 32). A comprehensive PN overview may be found in 34. This Ecma Technical Report has been adopted by the General Assembly of December 2
10、010. iv Ecma International 2010“DISCLAIMER This document and possible translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, witho
11、ut restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to Ecma International, except as needed f
12、or the purpose of developing any document or deliverable produced by Ecma International (in which case the rules applied to copyrights must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by Ec
13、ma International or its successors or assigns. This document and the information contained herein is provided on an “AS IS“ basis and ECMA INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE AN
14、Y OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.“ Ecma International 2010 1Personal Networks Overview and Standardization Needs 1 Scope This Technical Report introduces and defines architectural concepts, and standardization needs concerning person
15、al networks (PN) and PNs that are extended with Services using various scenarios. This report does not specify the standards or the technologies to be used. 2 References For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (inclu
16、ding any amendments) applies. 1 ECMA TR/92, Corporate Telecommunication Networks - Mobility for Enterprise Communications 2 ECMA TR/96, Next Generation Corporate Networks (NGCN) - Identification and Routing 3 ECMA TR/101, Next Generation Corporate Networks (NGCN) - Emergency Calls 4 ISO/IEC 29341-1:
17、2008, Information technology - UPnP Device Architecture - Part 1: UPnP Device Architecture Version 1.0 5 ISO/IEC 7498-1:1994, Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model 6 ITU-T Rec. X.509, Information technology - Open Systems Interconnection - The
18、 Directory: Public-key and attribute certificate frameworks 7 ITU-T Rec X.200, Information technology - Open Systems Interconnection - Basic Reference Model: The basic model 8 ITU-T Rec. Y.1542, Framework for achieving end-to-end IP performance objectives 9 ITU-T Rec. Y.1542 Amd1, Framework for achi
19、eving end-to-end IP performance objectives 10 ITU, Performance, QoS and QoE, ITU-T Study Group 12 (Study Period 2009-2012) 11 IETF RFC 3261, SIP: Session Initiation Protocol 12 IETF RFC 4306, Internet Key Exchange (IKEv2) Protocol 13 IETF RFC 2205, Resource ReSerVation Protocol (RSVP) 14 IETF, The O
20、ptimized Link State Routing Protocol, V2, draft-ietf-manet-olsrv2-11 15 IETF, Dynamic MANET On-demand (DYMO) Routing, draft-ietf-manet-dymo-19 16 IETF, Simplified Multicast Forwarding (SMF), draft-ietf-manet-smf-10 17 IETF, Network Mobility Work Group, online: http:/tools.ietf.org/wg/nemo 18 IETF, M
21、obile Ad Hoc Network (MANET) Neighbourhood Discovery Protocol (NHDP), draft-ietf-manet-nhdp-12 19 IETF RFC 5201 Host Identity Protocol 20 IETF, Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN), draft-ietf-behave-turn-16 21 IETF, Service Locatio
22、n Protocol (SLP, srvloc), Version 2, RFC2608 22 IETF, Link-Local Multicast Name Resolution (LLMNR), RFC4795 2 Ecma International 201023 IETF RFC 2407 defined The Internet IP Security Domain of Interpretation for ISAKMP 24 IETF RFC 2408 Internet Security Association and Key Management Protocol (ISAKM
23、P) 25 IETF RFC 2409 defined The Internet Key Exchange (IKE) 26 IETF, REsource LOcation And Discovery (RELOAD), draft-ietf-p2psip-reload-00 27 OMA-TP-CPNS-2008-0002-INP_CPNS: “Personal network concepts: Standardization needs in Personal Networks” 28 Digital Living Network Alliance (DLNA), online: htt
24、p:/www.dlna.org/ 29 Peer to Peer Universal Computing Consortium, online; http:/www.pucc.jp/ 30 Apache River, Jini, online: http:/www.jini.org/ 31 Universal Plug and Play (UPnP), online: http:/www.upnp.org/ 32 Freeband PNP2008, http:/pnp2008.freeband.nl/ 33 IST MAGNET Project, http:/magnet.aau.dk 34
25、Martin Jacobsson, Ignas Niemegeers, Sonia Heemstra de Groot, “Personal Networks: Wireless Networking for Personal Devices“, ISBN 978-0-470-68173-2, John Wiley o Offered Services; and o Non-PN Services. Functionality for sharing Services, including access control and the management thereof. Giving ac
26、cess to Non-PN Services and Offered Services using Proxies. Offering PNs (OPNs) make a subset of their Services available to other PNs that may (subject to a set of rules) then become Extended PNs (EPNs). Notice that only a subset of the Services in each participating PN is made available to the oth
27、ers. 4.2 PN Level The PN level provides an efficient networking platform for the PN Services. A PN can be seen as an autonomous overlay network that runs transparently on top of existing infrastructure. The PN level addresses how the Nodes are organized and how they communicate with each other. PN p
28、rotocols are based on IP because IP offers abstraction across heterogeneous connectivity technologies and the network level has to be as independent as possible from the connectivity level so that current and future connectivity technologies can be supported, compatibility with the already developed
29、 protocols based on the IP is maintained, existing technologies based on IP can be reused within the PN. The PN level detaches communication among its Nodes from communication with Foreign Nodes. The PN has its own PN level address space for its Nodes. Nodes must have an address that is unique withi
30、n its PN and may receive it during the imprinting process. Applications and services can use these addresses to communicate with each other regardless of the location and topology. A PN has at least one - or more - Network Clusters. Network Clusters do not have an address or identity. Nodes organise
31、 themselves into Network Clusters, using a method that is to-be-standardised. Network Clusters facilitate local communication and efficient routing. Communication among the Nodes in different Network Clusters may be realized using IP routing, forwarding and/or tunnelling over the Interconnecting Str
32、ucture. Network Clusters use their Gateways to communicate with other Network Clusters, using the Gateway PoA(s) retrieved from a (common) Registry. Gateways keep the globally addressable registry up to date when their PoAs change. The Gateways use the Registry to learn each others PoAs initially an
33、d when they change. Ecma International 2010 9Higher layer protocols, such as SIP 11, IKEv2 12. RSVP 13, may be required for e.g. mobility, security or QoS support. 4.3 Connectivity Level In the connectivity level, Devices are organised in L2 Domains with communication links among them. The connectiv
34、ity level covers the basic wired and wireless networks and protocols. Concerns addressed at this level include issues at data link layer, physical layer, and their interrelationships. Solutions for this abstraction level use existing wired and wireless technologies. A Personal Network will partly be
35、 formed on top of these L2 domains by simply using the connectivity offered by this L2 domain. Some important issues that are influential on the performance of PNs are Auto-configuration of interfaces: if different Nodes want to communicate with each other in a L2 domain, they may need to use the sa
36、me configuration. For example, for networks based on the IEEE 802.11 standard, this means they have to connect to the same access point (in infrastructure mode) or the same ad-hoc network (in ad-hoc mode). Manual intervention to achieve this would seriously impact user-friendliness. Efficient utilis
37、ation of resources: For example, several wireless technologies operate in the same frequency bands (e.g., ISM bands). These technologies should share these radio resources in an efficient and fair way to improve connectivity, scalability and co-existence. Standardized access to L2 link properties su
38、ch as bandwidth and delay to make the PN networking more efficient. Standardized feedback about L2 events such as the detection of other devices, the breakage of links or loss in connectivity to make the PN establishment and maintenance more efficient. 5 PN Configurations This Clause introduces some
39、 configurations for Personal Networks and their extensions. 5.1 PN with 1 User People make use of a wide range of devices. At home, they have a variety of devices such as digital TV, stereo, PC, printer, digital camera, hard disk recorder, media server, smart phone, intercom, HVAC system, surveillan
40、ce camera. Furthermore, users also carry around some devices such as smart phones, PDAs or laptops. Such devices are not easily connected to each other and access to services is difficult. PNs facilitate interconnection of these devices, access to information that is stored on them and usage of serv
41、ices offered whether the user is inside, around or away from home. Examples of such services are: automated file replication, remotely watching the surveillance camera, accessing digital photos stored at home, programming your hard disk recorder, controlling the heating system while driving back hom
42、e. The Owner will authorise or himself imprint these Devices. The Nodes at home will self-organize them into a Network Cluster. When the User leaves his house, carrying some Devices with him, the Nodes on these Devices will form another Network Cluster. The PN technology will automatically interconn
43、ect the different Network Clusters via Gateways and make all their Services available to each other. It is possible that a Device, e.g. a printer, is being used by other Users at the same time. In that case, this Device will host different Nodes at the same time, each Node belonging to another PN. 5
44、.2 PNs with multiple Users People residing in a home for the elderly become often socially isolated. Their family members often do not have time to visit them due to time and distance restrictions. However, these elderly people really care about 10 Ecma International 2010how their children and grand
45、children are doing. They like to watch pictures of them, listen to music, communicate with each other, or to be kept up-to-date about interesting things that happened. Within the home for the elderly, the caregivers want to keep these people informed about things happening inside the home (meals, ac
46、tivities, pictures of events), but also in the outside world. Traditional technology is often too complex for these elderly people, but PN technology reduces complexity and can enrich the life of these elderly people. Figure 5 2 PNs, both having multiple users Within the home for the elderly, Device
47、s can be installed in the rooms of the people. On the Device of a person living in the home for the elderly and on the Devices of their family members, Nodes can be created, forming a Family PN that has multiple Users. The PN transparently makes the Services offered by the Nodes of the family member
48、s available to the Node created on the Device in the room. Then, with an easy, remote-controlled user interface, these Services can be used by the elderly people in a very simple and intuitive way. In the same way, all Devices in the home for the elderly can host an additional Node that is part of t
49、he “Home for the Elderly” PN. The TranseCare project implemented a prototype of this use-case, see 36. 5.3 PN owned by a Legal Entity Within a company employees are often on the road or they have to be stand-by in case of an emergency. Therefore, they frequently require access to data stored in remote databases or services located at different premises. For example, a sales person requires access to the customer database at the main office when visiting its cus
