BS EN IEC 62919:2018 pdf download – Content management – Monitoring and management of personal digital content.
1 Scope This document specifies requirements, the protocol and the data format to visualize personal content saved on the various devices, such as mobile phones, music players, personal computers, hard disk recorders and e-book devices. This document also specifies methods for gathering information of digital content saved on personal devices and shared within a group, and to extract the gathered information by uniform application interface. 2 Normative references There are no normative references in this document. 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply. ISO and IEC maintain terminological databases for use in standardization at the following addresses: • IEC Electropedia: available at http://www.electropedia.org/ • ISO Online browsing platform: available at http://www.iso.org/obp 3.1.1 content preservation information information on content that is preserved in a user’s device 3.1.2 content information server server which receives and stores content preservation information 3.1.3 personal content digital content stored on user devices Note 1 to entry: Personal content includes content that users purchase or create by themselves. 3.1.4 content device user device where content is stored 3.1.5 device ID identifier to specify a device
6 General measures for visualizing personal content 6.1 Protocol In this document, it is expected that a web browser can be the application of my library for visualizing personal content. The HTTP or HTTPS protocol is used to communicate from content devices to the content information server as shown in Figure A.1 . Since the HTTP or HTTPS protocol is used for internet browsing, users do not need to change the port setting on their broadband routers or their gateway routers in their home and domains. 6.2 Application layer 6.2.1 General requirement Users would like to sort or rearrange content icons on my library by drag and drop operations, such as operations on actual bookshelves. Addition, modification and deletion of content saved on the devices should be notified to the client (visualization application) in asynchronous communication. In addition, the client devices to visualize personal content should display the content preservation information, even if it is offline. Figure 5 shows an example of the personal content view of my library.
7 Sending content information to servers or cloud 7.1 General 7.1.1 Content meta and base information Content preservation information, which each device sends to the content information server, includes the items listed in 7.1 .2 and 7.1 .3. 7.1.2 Content meta information Content meta information <content_metainfo> includes the items listed as follows: • method, • device ID/device name, • user ID, • family ID, • content ID, and • sub-content ID (global ID identified in content distribution market). After the content preservation information is stored in the content information server, family ID can be settled on the server system. For instance, users access a website on the server system, they select a family ID from the candidates to confirm a group for content sharing. Family ID is an identifier that can be applied to not only a family, but also friends, colleagues and other groups. When a device is registered in the system, the user can add its device name to the system. A name-resolving server runs in the cloud system and manages the table between the device ID and the device name. The correspondence between the device ID and the device name helps name resolving in the system, as needed.
Content IDs may consist of two IDs that are a content ID and a sub-content ID. The sub-content ID is the identifier allocated globally in the content distribution market. The server in the cloud system can derive the content metadata from the sub-content ID. The derivation or reference operations between the sub-content ID and the content metadata will be conducted only on the server side. 7.1.3 Content base information Content base information <content_baseinfo> includes the items listed as follows: • filename, • filepath, • application type, • create time, • size, and • title. An application type that is registered in RFC6838 as a media type can be used to launch the correct program to consume digital content. Application types are regarded as classification of application programs that work on devices. When the content information server receives the content preservation information including the application type, the server saves the data as shown in Table 1 .