WO2017110003A1 - Inter-device connection method and object sharing device - Google Patents

Inter-device connection method and object sharing device Download PDF

Info

Publication number
WO2017110003A1
WO2017110003A1 PCT/JP2015/086439 JP2015086439W WO2017110003A1 WO 2017110003 A1 WO2017110003 A1 WO 2017110003A1 JP 2015086439 W JP2015086439 W JP 2015086439W WO 2017110003 A1 WO2017110003 A1 WO 2017110003A1
Authority
WO
WIPO (PCT)
Prior art keywords
key
group
machine
parent
same
Prior art date
Application number
PCT/JP2015/086439
Other languages
French (fr)
Japanese (ja)
Inventor
吉田　正樹
実 丹羽
泰伯 山崎
Original Assignee
株式会社アイ・エル・シー
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社アイ・エル・シー filed Critical 株式会社アイ・エル・シー
Priority to PCT/JP2015/086439 priority Critical patent/WO2017110003A1/en
Priority to JP2017557670A priority patent/JP6705836B2/en
Publication of WO2017110003A1 publication Critical patent/WO2017110003A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

  • the present invention relates to an inter-device connection method for performing object sharing between devices and an object sharing device.
  • an object of the present invention is to easily set whether or not to share according to the type of object.
  • the inter-device connection method of the present invention is the inter-device connection method between the own device and the other device, and when the own device accesses the object of the other device, Only when the object and the object of the other device have the same key of the same group, it is determined that the object of the own device can access the object of the other device.
  • the object of the other device when the own device generates a key including a parent-child relationship of the group of the own device and accesses an object of the other device, the object of the other device has a parent key of the same group as the own device. If it is, it is determined that the object of the other device is accessible.
  • the self device is characterized in that the object of the other device determined to be accessible is a shared object.
  • the object sharing device of the present invention is an object sharing device that shares an object of the own device and an object of the other device.
  • the object sharing device and the other device Only when the machine object has the same key of the same group, a control unit that judges that the object of the own machine can access the object of the other machine is provided.
  • the object of the other device when the own device generates a key including a parent-child relationship of the group of the own device and accesses an object of the other device, the object of the other device has a parent key of the same group as the own device. If it is, it is determined that the object of the other device is accessible.
  • the self-machine is characterized in that the object of the other machine determined to be accessible is a shared object.
  • the own object can be connected only to an object having the same key of the same group or an object having the parent key of the own group.
  • FIG. 1 is a diagram for explaining Shared and Isolated objects.
  • FIG. 2 is a diagram for explaining key generation for maintaining security of connection between devices.
  • FIG. 3 is a chart illustrating a key file generated by the key generation unit according to the embodiment.
  • FIG. 4 is a block diagram of a hardware configuration example of the device according to the embodiment.
  • FIG. 5 is a diagram illustrating group security based on a scope in the device according to the embodiment.
  • FIG. 6 is a table showing object cross-references in the device of the embodiment.
  • FIG. 7 is a flowchart illustrating an example of the inter-device connection process executed by the device according to the embodiment.
  • FIG. 1 is a diagram for explaining Shared and Isolated objects. First, Shared (shared) and Isolated (individual) objects will be described. Remote objects include a Shared object 101 that is shared between calling applications and an Isolated object 102 that is not shared between the applications and is separated from each other.
  • an object whose physical entity represents a device switch, LED 110, or the like represents what is physically specified as a single object, and all callers ( Calling Objects 1 to 3) Since it is necessary to indicate the same state among 131a to 131c, the Shared object 101 is desirable.
  • the shared object (Shared object) 101 can be physically specified as a single object such as a switch or LED 110, and the state must be shared among the callers 131a to 131c. It is.
  • FIG. 1A objects representing individual processes are not shared among the callers (Calling Objects 1 to 3) 131a to 131c, like the input / output class of the file 120, as shown in FIG. , It is desirable that the isolated objects 102 are separated from each other. This sharing / separation is set by configuration.
  • the separated object (Isolated object) 102 is an object that must have a unique state for each of the call sources 131a to 131c, such as the input / output of the file 120. Must be separated. For example, even if another caller (131b) performs a read operation after the caller 1 (131a) performs a read operation, the offset that the caller 1 (131a) reads next is the caller 2 (131b). The read operation must not change.
  • FIG. 2 is a diagram for explaining key generation for maintaining security of connection between devices.
  • devices and devices that are connected for communication via a network or the like are seamlessly connected. At this time, the devices are not connected unconditionally, but the security of the connected partner is defined. It is key generation that provides the security.
  • the key generator 200 shown in FIG. 2 generates a key file 202 by inputting a key element (file) 201 for generating an encryption key. Data required for input when generating a key (encryption key) is shown below.
  • the user ID 211 is captured as a key element (file) 201 into a key generator 200 for generating an encryption key.
  • a key generator 200 for generating an encryption key.
  • Group name When connecting devices, they must be in the same group, so a key K that can be used in the group is issued.
  • the group name 212 is used to identify a group and must be unique within the same user ID.
  • Parent group name A parent group name 213 that is a parent of the group G is designated.
  • the specified parent group can be connected.
  • a parent group is designated for the designated parent group itself, the parent above it can also be accessed.
  • This “accessible range” is defined as a scope.
  • the encryption method 214 designates an encryption method such as Advanced Encryption Standard (AES) or Blowfish, and the bit length of the key. When a plurality of encryption methods 214 are designated, encryption escalation (optimization) is performed.
  • AES Advanced Encryption Standard
  • Blowfish Blowfish
  • Effective number 215 designates the number of devices effective as an encryption key. When a key is issued, the effective number is reduced from the maximum number of keys issued set in the key element (file) 201. You cannot specify a valid number that exceeds the number of remaining keys.
  • each information of the key element 201 of the above 1) to 5) input to the key generation unit (Key Generator) 200 is displayed on the display unit 220 of the device, and the operation of the encryption key issue button 221 is performed.
  • the key file 202 is generated based on the information 1) to 5).
  • FIG. 3 is a chart showing a key file generated by the key generation unit of the embodiment.
  • the key file 202 generated by the key generation unit 200 includes a user ID 211, a group name 212, a parent group name 213, and an encryption key 215 for each encryption method 214.
  • the encryption key 1 (215a) of the encryption method 1 (214a) and the encryption key 2 (215b) of the encryption method 2 (214b) are included.
  • the generated key file 202 is stored in the secure area of the device, and the control unit of the device acquires the key file 202 from the secure area by the porting layer.
  • a single device can store and use a plurality of key files 202.
  • FIG. 4 is a block diagram of a hardware configuration example of the device according to the embodiment. This is a hardware configuration commonly used for each of the devices connected to each other.
  • the device 400 includes a control unit (CPU) 401, a Read-Only Memory (ROM) 402, and a Random Access Memory (RAM) 403. Also, a storage unit 404 such as a semiconductor memory or a disk drive, and a communication interface (I / F) 409 are included.
  • the device 400 may further include a display 408, a keyboard 410, a mouse 411, a scanner 412, and a printer 413 that can be connected. These CPU 401 to printer 413 are connected by a bus 414.
  • the CPU 401 is an arithmetic processing unit that controls the entire device 400.
  • the ROM 402 is a non-volatile memory that stores the program of the device 400.
  • the RAM 403 is a volatile memory that is used as a work area when the CPU 401 executes arithmetic processing.
  • the communication interface 409 controls an internal interface with the network 415 and controls input / output of data from an external device.
  • the communication interface 409 is connected to a local area network (LAN), a wide area network (WAN), or the Internet, which becomes the network 415 through a communication line, and is connected to the counterpart device 400 via the network 415.
  • LAN local area network
  • WAN wide area network
  • the Internet which becomes the network 415 through a communication line
  • the counterpart device 400 via the network 415.
  • a modem or a LAN adapter can be employed as the communication interface 409.
  • the display 408 is a device that displays data such as a cursor, an icon, or a tool box, as well as documents, images, function information, and the like.
  • a Thin Film Transistor (TFT) liquid crystal display for example, a Thin Film Transistor (TFT) liquid crystal display, a plasma display, an organic EL display, or the like can be employed.
  • TFT Thin Film Transistor
  • the key file 202 described above is stored in a secure area of the device 400, for example, a memory in the CPU 201, a ROM 402, or the like.
  • the key file 202 may be acquired from the outside of the device 400, or the CPU 201 has the function of the key generation unit 200, generates the key file 202 based on the key element (file) 201, and secures the device 400.
  • a configuration may be adopted in which data is stored and held in such areas.
  • These devices can be applied to various devices that perform information processing, such as embedded devices, personal computers, and smartphones.
  • FIG. 5 is a diagram illustrating group security based on a scope in the device according to the embodiment.
  • the “object scope” is determined by specifying a group name.
  • FIG. 5 it is assumed that, for example, four devices 400a to 400d are connected by communication or the like.
  • the parent-child relationship of the group (GROUP) is shown in the vertical direction of the figure. That is, as viewed from GROUP1, GROUP2 and 4 are children of the same hierarchy, and GROUP3 has GROUP2 as a child.
  • the object A of the device 400a has a GROUP1 key.
  • objects B, C, D, and E have GROUP1 as a parent key.
  • the object B and the object C device 400b, the object D device 400c, and the object E device 400d having GROUP1 as a parent key can be communicably connected.
  • the object B of the device 400b has a GROUP2 key. Assume that the object C has the same GROUP2 key, and the objects D and A have GROUP2 as the parent key. In this case, communication is possible with the device 400b of the object C having the same GROUP2 key (in the same device 400b). Further, the object B of the device 400b can communicate with the device 400c of the object D having the same GROUP2 key as a parent key. Furthermore, the object B of the device 400b can communicate with the device 400a of the object A having the parent key GROUP1.
  • the object C of the device 400b has a GROUP2 key, and can communicate with the device 400b of the object B having the same GROUP2 key (in the same device 400b). Further, the object C of the device 400c can communicate with the device 400c of the object D having the same GROUP2 key as a parent key. The object C of the device 400b can communicate with the device 400a of the object A having the parent key GROUP1.
  • the object D of the device 400c can communicate with the object B having the parent key GROUP2 and the device 400b of the object C (the same device 400b).
  • the object D has a parent key of GROUP2, which is a parent key, of GROUP1, and can communicate with the device 400a of the object A having GROUP1.
  • the object E can communicate only with the device 400a of the object A having the parent key GROUP1.
  • FIG. 6 is a chart showing object cross-references in the device of the embodiment. 6 is a list of whether or not each object in FIG. 5 can be connected.
  • communication can be performed only with an object having the same key of GROUP or a parent key of own GROUP. That is, communication is not possible with objects other than the same non-GROUP object and objects with the same GROUP parent key.
  • the object BC of GROUP 2 cannot be connected to the object E of GROUP 4. Further, the object D of GROUP 3 cannot be connected to the object E of GROUP 4.
  • FIG. 7 is a flowchart illustrating an example of the inter-device connection process executed by the device according to the embodiment. An example of processing based on an inter-device connection program executed by one CPU 401 of the devices 400 to be interconnected is shown.
  • the CPU 401 acquires a group of objects of the own device 400 and a parent key (step S701). Thereafter, the CPU 401 accesses the object of the other device 400 (step S702).
  • the CPU 401 determines whether the accessed object of the other device 400 belongs to the same GROUP (step S703). If the object of the other device 400 does not belong to the same GROUP (step S703: No), the CPU 401 proceeds to step S704. If the object of the other device 400 belongs to the same GROUP (step S703: Yes), the CPU 401 proceeds to step S705.
  • step S704 the CPU 401 determines whether this object is an object having its own GROUP as a parent key (step S704). If this object is an object having its own GROUP as a parent key (step S704: Yes), the process proceeds to step S705. If this object is not an object having its own GROUP as a parent key (step S704: No), the process proceeds to step S706.
  • step S705 the CPU 401 permits connection with the accessed object of the other device 400 (step S705).
  • step S706 the CPU 401 rejects connection with the accessed object of the other device 400 (step S706).
  • communication connection can be established only between an object belonging to the same GROUP or an object having the own GROUP as a parent key.
  • connection-permitted object is used as a Shared object shared between the devices 400
  • connection-rejected object is used as an Isolated object that is not shared between the devices 400.
  • the own object can be connected only to an object having the same key in the same group or an object having the parent key of the own group.
  • the objects (devices) to be connected to each other can be easily selected by using the attributes of the key and the parent key based on the hierarchical structure.
  • control processing burden of the control unit can be reduced, and an inexpensive embedded device It is suitable for use.
  • the device connection method described above can be realized by executing a device connection program prepared in advance on a computer mounted on a personal computer (PC), a smartphone, or the like.
  • the inter-device connection program is recorded on a computer-readable recording medium such as a magnetic disk, an optical disk, or a USB (Universal Serial Bus) flash memory, and is executed by being read from the recording medium by the computer.
  • the waveform data conversion program may be distributed via a network such as the Internet.
  • the present invention can be applied to various computer apparatuses that share objects, and is suitable for use in devices that determine mutual connection using a key.
  • Key generation unit 201 Key element (file) 202 Key file 400 Device 401 CPU 402 ROM 403 RAM 409 Communication interface

Abstract

At the time of inter-device connection between a device (400a) and another device (400b), when a control unit of the device (400a) accesses an object B of the other device (400b), the control unit determines that an object A of the device (400a) can access the object B of the other device (400b) only if the object A of the device (400a) and the object B of the other device (400b) have the same key of the same group. In addition, the control unit of the device (400a) generates a key including a parent-child relationship of the group of the device (400a), and , when the control unit accesses an object D of another device (400c), the control unit determines that it is possible to access the object D of the other device (400c) if the object D of the other device (400c) has a master key of the same group as the device (400a) .

Description

機器間接続方法およびオブジェクト共有機器Device connection method and object sharing device
　この発明は、機器間のオブジェクト共有を行う機器間接続方法およびオブジェクト共有機器に関する。 The present invention relates to an inter-device connection method for performing object sharing between devices and an object sharing device.
　従来、ネットワーク等を介してオブジェクトを共有するシステムがある（例えば、下記特許文献１参照。）。このシステムでは、機器間でデータを共有する。 Conventionally, there is a system for sharing an object via a network or the like (for example, see Patent Document 1 below). In this system, data is shared between devices.
特開２０１０－２６７０１号公報JP 2010-26701 A
　しかしながら、上記従来の技術では、データすなわち、オブジェクトの種別に応じた共有の可否を設定することができない。 However, according to the above-described conventional technology, it is not possible to set whether or not sharing is possible according to data, that is, the type of object.
　本発明は、上記課題に鑑み、オブジェクトの種別に応じた共有の可否を容易に設定できることを目的とする。 In view of the above problems, an object of the present invention is to easily set whether or not to share according to the type of object.
　上記目的を達成するため、本発明の機器間接続方法は、自機と他機との間の機器間接続方法において、前記自機は、前記他機のオブジェクトにアクセスしたとき、前記自機のオブジェクトと前記他機のオブジェクトとが同一グループの同一鍵を有している場合にのみ、前記自機のオブジェクトが前記他機のオブジェクトにアクセス可能と判断する、ことを特徴とする。 In order to achieve the above object, the inter-device connection method of the present invention is the inter-device connection method between the own device and the other device, and when the own device accesses the object of the other device, Only when the object and the object of the other device have the same key of the same group, it is determined that the object of the own device can access the object of the other device.
　また、前記自機は、当該自機のグループの親子関係を含めた鍵を生成し、前記他機のオブジェクトにアクセスしたとき、前記他機のオブジェクトが前記自機と同一グループの親鍵を有している場合には、前記他機のオブジェクトにアクセス可能と判断する、ことを特徴とする。 In addition, when the own device generates a key including a parent-child relationship of the group of the own device and accesses an object of the other device, the object of the other device has a parent key of the same group as the own device. If it is, it is determined that the object of the other device is accessible.
　前記自機は、前記アクセス可能と判断した前記他機のオブジェクトを共有オブジェクトとすることを特徴とする。 The self device is characterized in that the object of the other device determined to be accessible is a shared object.
　また、本発明のオブジェクト共有機器は、自機のオブジェクトと他機のオブジェクトを共有するオブジェクト共有機器において、前記自機は、前記他機のオブジェクトにアクセスしたとき、前記自機のオブジェクトと前記他機のオブジェクトとが同一グループの同一鍵を有している場合にのみ、前記自機のオブジェクトが前記他機のオブジェクトにアクセス可能と判断する制御部を備えた、ことを特徴とする。 The object sharing device of the present invention is an object sharing device that shares an object of the own device and an object of the other device. When the own device accesses the object of the other device, the object sharing device and the other device Only when the machine object has the same key of the same group, a control unit that judges that the object of the own machine can access the object of the other machine is provided.
　また、前記自機は、当該自機のグループの親子関係を含めた鍵を生成し、前記他機のオブジェクトにアクセスしたとき、前記他機のオブジェクトが前記自機と同一グループの親鍵を有している場合には、前記他機のオブジェクトにアクセス可能と判断する、ことを特徴とする。 In addition, when the own device generates a key including a parent-child relationship of the group of the own device and accesses an object of the other device, the object of the other device has a parent key of the same group as the own device. If it is, it is determined that the object of the other device is accessible.
　また、前記自機は、前記アクセス可能と判断した前記他機のオブジェクトを共有オブジェクトとすることを特徴とする。 Further, the self-machine is characterized in that the object of the other machine determined to be accessible is a shared object.
　上記構成によれば、自機のオブジェクトは、同一グループの同一鍵を持つオブジェクト、あるいは自グループの親鍵を持つオブジェクトとのみ接続することができるようになる。 According to the above configuration, the own object can be connected only to an object having the same key of the same group or an object having the parent key of the own group.
　本発明によれば、オブジェクトの種別に応じた共有の可否を容易に設定できるという効果を奏する。 According to the present invention, it is possible to easily set whether sharing is possible according to the type of object.
図１は、ＳｈａｒｅｄとＩｓｏｌａｔｅｄオブジェクトを説明する図である。FIG. 1 is a diagram for explaining Shared and Isolated objects. 図２は、機器間接続のセキュリティを維持する鍵生成を説明する図である。FIG. 2 is a diagram for explaining key generation for maintaining security of connection between devices. 図３は、実施の形態の鍵生成部により生成される鍵ファイルを示す図表である。FIG. 3 is a chart illustrating a key file generated by the key generation unit according to the embodiment. 図４は、実施の形態にかかる機器のハードウェア構成例を示すブロック図である。FIG. 4 is a block diagram of a hardware configuration example of the device according to the embodiment. 図５は、実施の形態の機器におけるスコープによるグループセキュリティを説明する図である。FIG. 5 is a diagram illustrating group security based on a scope in the device according to the embodiment. 図６は、実施の形態の機器におけるオブジェクトの相互参照を示す図表である。FIG. 6 is a table showing object cross-references in the device of the embodiment. 図７は、実施の形態にかかる機器が実行する機器間接続処理の一例を示すフローチャートである。FIG. 7 is a flowchart illustrating an example of the inter-device connection process executed by the device according to the embodiment.
（実施の形態）
　以下に添付図面を参照して、この発明にかかる機器間接続方法およびオブジェクト共有機器の好適な実施の形態を詳細に説明する。 (Embodiment)
Exemplary embodiments of an inter-device connection method and an object sharing device according to the present invention will be explained below in detail with reference to the accompanying drawings.
（ＳｈａｒｅｄとＩｓｏｌａｔｅｄオブジェクトについて）
　図１は、ＳｈａｒｅｄとＩｓｏｌａｔｅｄオブジェクトを説明する図である。はじめに、Ｓｈａｒｅｄ（共有）とＩｓｏｌａｔｅｄ（個別）オブジェクトについて説明しておく。リモートオブジェクトには、呼出し元のアプリケーション間で共有されるＳｈａｒｅｄオブジェクト１０１と、同アプリケーション間で共有されず、互いに分離されるＩｓｏｌａｔｅｄオブジェクト１０２がある。 (About Shared and Isolated objects)
FIG. 1 is a diagram for explaining Shared and Isolated objects. First, Shared (shared) and Isolated (individual) objects will be described. Remote objects include a Shared object 101 that is shared between calling applications and an Isolated object 102 that is not shared between the applications and is separated from each other.
　例えば、図１（ａ）に示すように、物理的な実体が装置のスイッチやＬＥＤ１１０などを表すオブジェクトは、物理的に単一の物として特定されるものを表しており、すべての呼出し元（Ｃａｌｌｉｎｇ　Ｏｂｊｅｃｔ１～３）１３１ａ～１３１ｃ間で同一の状態を示さなければならないものであるため、Ｓｈａｒｅｄオブジェクト１０１とすることが望ましい。 For example, as shown in FIG. 1A, an object whose physical entity represents a device switch, LED 110, or the like represents what is physically specified as a single object, and all callers ( Calling Objects 1 to 3) Since it is necessary to indicate the same state among 131a to 131c, the Shared object 101 is desirable.
　図１（ｂ）に示すように、共有オブジェクト（Ｓｈａｒｅｄオブジェクト）１０１は、スイッチやＬＥＤ１１０など、物理的に単一の物に特定でき、状態が呼出し元１３１ａ～１３１ｃ間で共有されなければならないオブジェクトである。 As shown in FIG. 1B, the shared object (Shared object) 101 can be physically specified as a single object such as a switch or LED 110, and the state must be shared among the callers 131a to 131c. It is.
　一方、図１（ａ）に示すように、物理的な実体がファイル１２０の入出力クラスのように、呼出し元（Ｃａｌｌｉｎｇ　Ｏｂｊｅｃｔ１～３）１３１ａ～１３１ｃ間で個別の処理を表すオブジェクトは共有されず、それぞれ分離されたＩｓｏｌａｔｅｄオブジェクト１０２とすることが望ましい。この共有・分離は、コンフィギュレーションで設定する。 On the other hand, as shown in FIG. 1A, objects representing individual processes are not shared among the callers (Calling Objects 1 to 3) 131a to 131c, like the input / output class of the file 120, as shown in FIG. , It is desirable that the isolated objects 102 are separated from each other. This sharing / separation is set by configuration.
　図１（ｂ）に示すように、分離オブジェクト（Ｉｓｏｌａｔｅｄオブジェクト）１０２は、ファイル１２０の入出力のように、呼出し元１３１ａ～１３１ｃ別に固有の状態を持っていなければならないオブジェクトは、他の呼出し元とは分離されたものである必要がある。例えば、呼出し元１（１３１ａ）がｒｅａｄ操作を行った後、別の呼出し元（１３１ｂ）がｒｅａｄ操作を行っても、呼出し元１（１３１ａ）が次に読み出すオフセットは、呼出し元２（１３１ｂ）のｒｅａｄ操作によって変わってはならない。 As shown in FIG. 1B, the separated object (Isolated object) 102 is an object that must have a unique state for each of the call sources 131a to 131c, such as the input / output of the file 120. Must be separated. For example, even if another caller (131b) performs a read operation after the caller 1 (131a) performs a read operation, the offset that the caller 1 (131a) reads next is the caller 2 (131b). The read operation must not change.
（機器間接続の鍵生成について）
　図２は、機器間接続のセキュリティを維持する鍵生成を説明する図である。実施の形態の機器間接続のシステムでは、互いにネットワーク等を介して通信接続する機器と機器をシームレスに繋げる。この際、機器間が無条件に繋がるのではなく、繋がる相手は厳密なセキュリティが規定されている。そのセキュリティを提供するのが、鍵生成である。 (About key generation for inter-device connection)
FIG. 2 is a diagram for explaining key generation for maintaining security of connection between devices. In the inter-device connection system of the embodiment, devices and devices that are connected for communication via a network or the like are seamlessly connected. At this time, the devices are not connected unconditionally, but the security of the connected partner is defined. It is key generation that provides the security.
　図２に示す鍵生成部（Ｋｅｙ　Ｇｅｎｅｒａｔｏｒ）２００は、暗号鍵を生成するための鍵の素（ファイル）２０１の入力により、鍵ファイル２０２を生成する。鍵（暗号鍵）を生成する際の入力に必要なデータを以下に示す。 The key generator 200 shown in FIG. 2 generates a key file 202 by inputting a key element (file) 201 for generating an encryption key. Data required for input when generating a key (encryption key) is shown below.
１）ユーザＩＤ
　ユーザＩＤ２１１は、鍵の素（ファイル）２０１として、暗号鍵を生成するための鍵生成部（Ｋｅｙ　Ｇｅｎｅｒａｔｏｒ）２００に取り込まれる。Ｋｅｙ　Ｇｅｎｅｒａｔｏｒ２００を使用する際には、ユーザＩＤ２１１に紐づくユーザ名を選択する。 1) User ID
The user ID 211 is captured as a key element (file) 201 into a key generator 200 for generating an encryption key. When using the Key Generator 200, the user name associated with the user ID 211 is selected.
２）グループ名
　機器同士を接続する際には、同一グループでなければならないため、グループで使える鍵Ｋを発行する。グループ名２１２は、グループを識別するために用いられ、同一ユーザＩＤ内ではユニークである必要がある。 2) Group name When connecting devices, they must be in the same group, so a key K that can be used in the group is issued. The group name 212 is used to identify a group and must be unique within the same user ID.
３）親グループ名
　グループＧの親となる親グループ名２１３を指定する。指定した親グループとも接続できるようになる。指定した親グループ自身に、親グループが指定されている場合には、さらにその上の親についても、アクセスが可能となる。この「アクセス可能な範囲」をスコープと規定する。 3) Parent group name A parent group name 213 that is a parent of the group G is designated. The specified parent group can be connected. When a parent group is designated for the designated parent group itself, the parent above it can also be accessed. This “accessible range” is defined as a scope.
４）暗号方式
　暗号方式２１４は、ＡＥＳ（Ａｄｖａｎｃｅｄ　Ｅｎｃｒｙｐｔｉｏｎ　Ｓｔａｎｄａｒｄ）や、Ｂｌｏｗｆｉｓｈ等の暗号化方式および鍵のビット長を指定する。暗号方式２１４を複数指定した場合には、暗号のエスカレーション（最適化）を実施する。 4) Encryption Method The encryption method 214 designates an encryption method such as Advanced Encryption Standard (AES) or Blowfish, and the bit length of the key. When a plurality of encryption methods 214 are designated, encryption escalation (optimization) is performed.
５）有効数
　有効数２１５は、暗号鍵として有効な機器の個数を指定する。鍵を発行すると鍵の素（ファイル）２０１に設定されている最大鍵発行数から有効数が減る。残っている鍵の個数を上回って有効数を指定することはできない。 5) Effective number The effective number 215 designates the number of devices effective as an encryption key. When a key is issued, the effective number is reduced from the maximum number of keys issued set in the key element (file) 201. You cannot specify a valid number that exceeds the number of remaining keys.
　例えば、機器の表示部２２０上には、鍵生成部（Ｋｅｙ　Ｇｅｎｅｒａｔｏｒ）２００に入力される上記１）～５）の鍵の素２０１の各情報が表示され、暗号鍵発行のボタン２２１の操作により、上記１）～５）の各情報に基づき、鍵ファイル２０２が生成される。 For example, each information of the key element 201 of the above 1) to 5) input to the key generation unit (Key Generator) 200 is displayed on the display unit 220 of the device, and the operation of the encryption key issue button 221 is performed. The key file 202 is generated based on the information 1) to 5).
　図３は、実施の形態の鍵生成部により生成される鍵ファイルを示す図表である。鍵生成部２００が生成する鍵ファイル２０２は、図２に示したように、ユーザＩＤ２１１、グループ名２１２、親グループ名２１３、暗号方式２１４別の暗号鍵２１５、からなる。図３の例では、暗号方式１（２１４ａ）の暗号鍵１（２１５ａ）と、暗号方式２（２１４ｂ）の暗号鍵２（２１５ｂ）を有している。 FIG. 3 is a chart showing a key file generated by the key generation unit of the embodiment. As shown in FIG. 2, the key file 202 generated by the key generation unit 200 includes a user ID 211, a group name 212, a parent group name 213, and an encryption key 215 for each encryption method 214. In the example of FIG. 3, the encryption key 1 (215a) of the encryption method 1 (214a) and the encryption key 2 (215b) of the encryption method 2 (214b) are included.
　生成された鍵ファイル２０２は、機器のセキュア領域に保存され、機器の制御部は、ポーティング層によってセキュアな領域から鍵ファイル２０２を取得する。１つの機器の中には、複数の鍵ファイル２０２を保存し、利用することができる。 The generated key file 202 is stored in the secure area of the device, and the control unit of the device acquires the key file 202 from the secure area by the porting layer. A single device can store and use a plurality of key files 202.
（ハードウェア構成例）
　図４は、実施の形態にかかる機器のハードウェア構成例を示すブロック図である。上述した互いに接続する各機器のそれぞれに共通して用いられるハードウェア構成である。 (Hardware configuration example)
FIG. 4 is a block diagram of a hardware configuration example of the device according to the embodiment. This is a hardware configuration commonly used for each of the devices connected to each other.
　機器４００は、制御部（ＣＰＵ）４０１と、Ｒｅａｄ‐Ｏｎｌｙ　Ｍｅｍｏｒｙ（ＲＯＭ）４０２と、Ｒａｎｄｏｍ　Ａｃｃｅｓｓ　Ｍｅｍｏｒｙ（ＲＡＭ）４０３と、を含む。また、半導体メモリやディスクドライブ等の記憶部４０４と、通信インターフェース（Ｉ／Ｆ）４０９とを含む。この機器４００は、さらに、ディスプレイ４０８と、キーボード４１０と、マウス４１１と、スキャナ４１２と、プリンタ４１３とを接続可能に備えてもよい。これらＣＰＵ４０１～プリンタ４１３はバス４１４によってそれぞれ接続されている。 The device 400 includes a control unit (CPU) 401, a Read-Only Memory (ROM) 402, and a Random Access Memory (RAM) 403. Also, a storage unit 404 such as a semiconductor memory or a disk drive, and a communication interface (I / F) 409 are included. The device 400 may further include a display 408, a keyboard 410, a mouse 411, a scanner 412, and a printer 413 that can be connected. These CPU 401 to printer 413 are connected by a bus 414.
　ＣＰＵ４０１は、機器４００の全体の制御を司る演算処理装置である。ＲＯＭ４０２は、機器４００のプログラムを記憶する不揮発性メモリである。ＲＡＭ４０３は、ＣＰＵ４０１による演算処理実行時のワークエリアとして使用される揮発性メモリである。 The CPU 401 is an arithmetic processing unit that controls the entire device 400. The ROM 402 is a non-volatile memory that stores the program of the device 400. The RAM 403 is a volatile memory that is used as a work area when the CPU 401 executes arithmetic processing.
　通信インターフェース４０９は、ネットワーク４１５と内部のインターフェースを司り、外部装置からのデータの入出力を制御する。具体的に、通信インターフェース４０９は、通信回線を通じてネットワーク４１５となるＬｏｃａｌ　Ａｒｅａ　Ｎｅｔｗｏｒｋ（ＬＡＮ）、Ｗｉｄｅ　Ａｒｅａ　Ｎｅｔｗｏｒｋ（ＷＡＮ）、インターネットなどに接続され、ネットワーク４１５を介して相手側の機器４００に接続される。通信インターフェース４０９には、例えば、モデムやＬＡＮアダプタなどを採用することができる。 The communication interface 409 controls an internal interface with the network 415 and controls input / output of data from an external device. Specifically, the communication interface 409 is connected to a local area network (LAN), a wide area network (WAN), or the Internet, which becomes the network 415 through a communication line, and is connected to the counterpart device 400 via the network 415. . As the communication interface 409, for example, a modem or a LAN adapter can be employed.
　ディスプレイ４０８は、カーソル、アイコンあるいはツールボックスをはじめ、文書、画像、機能情報などをデータ表示する装置である。ディスプレイ４０８には、例えば、Ｔｈｉｎ　Ｆｉｌｍ　Ｔｒａｎｓｉｓｔｏｒ（ＴＦＴ）液晶ディスプレイ、プラズマディスプレイ、有機ＥＬディスプレイなどを採用することができる。 The display 408 is a device that displays data such as a cursor, an icon, or a tool box, as well as documents, images, function information, and the like. As the display 408, for example, a Thin Film Transistor (TFT) liquid crystal display, a plasma display, an organic EL display, or the like can be employed.
　そして、上記説明した鍵ファイル２０２は、機器４００のセキュアな領域、例えば、ＣＰＵ２０１内のメモリやＲＯＭ４０２等に格納される。鍵ファイル２０２は、機器４００の外部から取得してもよいし、ＣＰＵ２０１が鍵生成部２００の機能を有し、鍵の素（ファイル）２０１に基づき、鍵ファイル２０２を生成し、機器４００のセキュアな領域に格納保持する構成としてもよい。 The key file 202 described above is stored in a secure area of the device 400, for example, a memory in the CPU 201, a ROM 402, or the like. The key file 202 may be acquired from the outside of the device 400, or the CPU 201 has the function of the key generation unit 200, generates the key file 202 based on the key element (file) 201, and secures the device 400. A configuration may be adopted in which data is stored and held in such areas.
　これら機器は、それぞれ組み込み機器や、パーソナル・コンピュータ、スマートフォンなど、情報処理を行う各種機器に適用可能である。 These devices can be applied to various devices that perform information processing, such as embedded devices, personal computers, and smartphones.
（スコープによるグループセキュリティについて）
　図５は、実施の形態の機器におけるスコープによるグループセキュリティを説明する図である。オブジェクト間でシームレスな通信を行うためには、グループ名を指定することで「オブジェクトのスコープ」を決定する。 (About group security by scope)
FIG. 5 is a diagram illustrating group security based on a scope in the device according to the embodiment. In order to perform seamless communication between objects, the “object scope” is determined by specifying a group name.
　図５を例に説明すると、例えば、４台の機器４００ａ～４００ｄが通信等により接続された構成であるとする。図５においてグループ（ＧＲＯＵＰ）の親子関係は図の上下方向で示している。すなわち、ＧＲＯＵＰ１からみて、ＧＲＯＵＰ２，４が同じ階層の子であり、ＧＲＯＵＰ３は、ＧＲＯＵＰ２を子とする。 Referring to FIG. 5 as an example, it is assumed that, for example, four devices 400a to 400d are connected by communication or the like. In FIG. 5, the parent-child relationship of the group (GROUP) is shown in the vertical direction of the figure. That is, as viewed from GROUP1, GROUP2 and 4 are children of the same hierarchy, and GROUP3 has GROUP2 as a child.
　そして、機器４００ａのオブジェクトＡは、ＧＲＯＵＰ１の鍵を持っている。そして、オブジェクトＢ，Ｃ，Ｄ，ＥがＧＲＯＵＰ１を親鍵として持つとする。この場合、ＧＲＯＵＰ１を親鍵として持つオブジェクトＢおよびオブジェクトＣの機器４００ｂ、オブジェクトＤの機器４００ｃ、オブジェクトＥの機器４００ｄと通信接続できる。 And the object A of the device 400a has a GROUP1 key. Assume that objects B, C, D, and E have GROUP1 as a parent key. In this case, the object B and the object C device 400b, the object D device 400c, and the object E device 400d having GROUP1 as a parent key can be communicably connected.
　機器４００ｂのオブジェクトＢは、ＧＲＯＵＰ２の鍵を持っている。そして、オブジェクトＣが同じＧＲＯＵＰ２の鍵を持ち、オブジェクトＤ，ＡがＧＲＯＵＰ２を親鍵として持つとする。この場合、同じＧＲＯＵＰ２の鍵を持つオブジェクトＣの機器４００ｂ（同一の機器４００ｂ内）と通信できる。また、機器４００ｂのオブジェクトＢは、同じＧＲＯＵＰ２の鍵を親鍵として持つオブジェクトＤの機器４００ｃと通信できる。さらに、機器４００ｂのオブジェクトＢは、親鍵であるＧＲＯＵＰ１を持つオブジェクトＡの機器４００ａと通信できる。 The object B of the device 400b has a GROUP2 key. Assume that the object C has the same GROUP2 key, and the objects D and A have GROUP2 as the parent key. In this case, communication is possible with the device 400b of the object C having the same GROUP2 key (in the same device 400b). Further, the object B of the device 400b can communicate with the device 400c of the object D having the same GROUP2 key as a parent key. Furthermore, the object B of the device 400b can communicate with the device 400a of the object A having the parent key GROUP1.
　機器４００ｂのオブジェクトＣは、ＧＲＯＵＰ２の鍵を持っており、同じＧＲＯＵＰ２の鍵を持つオブジェクトＢの機器４００ｂ（同一の機器４００ｂ内）と通信できる。また、機器４００ｃのオブジェクトＣは、同じＧＲＯＵＰ２の鍵を親鍵として持つオブジェクトＤの機器４００ｃと通信できる。機器４００ｂのオブジェクトＣは、親鍵であるＧＲＯＵＰ１を持つオブジェクトＡの機器４００ａと通信できる。 The object C of the device 400b has a GROUP2 key, and can communicate with the device 400b of the object B having the same GROUP2 key (in the same device 400b). Further, the object C of the device 400c can communicate with the device 400c of the object D having the same GROUP2 key as a parent key. The object C of the device 400b can communicate with the device 400a of the object A having the parent key GROUP1.
　機器４００ｃのオブジェクトＤは、親鍵であるＧＲＯＵＰ２を持つオブジェクトＢおよびオブジェクトＣの機器４００ｂ（同一の機器４００ｂ）と通信できる。また、オブジェクトＤは、親鍵であるＧＲＯＵＰ２の親鍵がＧＲＯＵＰ１であり、ＧＲＯＵＰ１を持つオブジェクトＡの機器４００ａと通信できる。 The object D of the device 400c can communicate with the object B having the parent key GROUP2 and the device 400b of the object C (the same device 400b). The object D has a parent key of GROUP2, which is a parent key, of GROUP1, and can communicate with the device 400a of the object A having GROUP1.
　オブジェクトＥは、親鍵であるＧＲＯＵＰ１を持つオブジェクトＡの機器４００ａとのみ通信できる。 The object E can communicate only with the device 400a of the object A having the parent key GROUP1.
　図６は、実施の形態の機器におけるオブジェクトの相互参照を示す図表である。図５の各オブジェクトの接続の可否を一覧化したものである。 FIG. 6 is a chart showing object cross-references in the device of the embodiment. 6 is a list of whether or not each object in FIG. 5 can be connected.
　上記例によれば、ＧＲＯＵＰの同一鍵、あるいは自ＧＲＯＵＰの親鍵を持つオブジェクトとの間でのみ通信が行える。すなわち、同一のＧＲＯＵＰでないオブジェクト、および同一のＧＲＯＵＰの親鍵を持つオブジェクト以外とは通信が行えない。ＧＲＯＵＰ２のオブジェクトＢＣは、ＧＲＯＵＰ４のオブジェクトＥと接続できない。また、ＧＲＯＵＰ３のオブジェクトＤは、ＧＲＯＵＰ４のオブジェクトＥと接続できない。 According to the above example, communication can be performed only with an object having the same key of GROUP or a parent key of own GROUP. That is, communication is not possible with objects other than the same non-GROUP object and objects with the same GROUP parent key. The object BC of GROUP 2 cannot be connected to the object E of GROUP 4. Further, the object D of GROUP 3 cannot be connected to the object E of GROUP 4.
　図７は、実施の形態にかかる機器が実行する機器間接続処理の一例を示すフローチャートである。相互接続する機器４００の一方のＣＰＵ４０１が実行する機器間接続プログラムに基づく処理の一例を示す。 FIG. 7 is a flowchart illustrating an example of the inter-device connection process executed by the device according to the embodiment. An example of processing based on an inter-device connection program executed by one CPU 401 of the devices 400 to be interconnected is shown.
　はじめに、ＣＰＵ４０１は、自機器４００のオブジェクトのグループと、親鍵を取得する（ステップＳ７０１）。この後、ＣＰＵ４０１は、他機４００のオブジェクトにアクセスする（ステップＳ７０２）。 First, the CPU 401 acquires a group of objects of the own device 400 and a parent key (step S701). Thereafter, the CPU 401 accesses the object of the other device 400 (step S702).
　この後、ＣＰＵ４０１は、アクセスした他機４００のオブジェクトが同一ＧＲＯＵＰに属するか判断する（ステップＳ７０３）。ＣＰＵ４０１は、他機４００のオブジェクトが同一ＧＲＯＵＰに属していなければ（ステップＳ７０３：Ｎｏ）、ステップＳ７０４に移行する。ＣＰＵ４０１は、他機４００のオブジェクトが同一ＧＲＯＵＰに属していれば（ステップＳ７０３：Ｙｅｓ）、ステップＳ７０５に移行する。 Thereafter, the CPU 401 determines whether the accessed object of the other device 400 belongs to the same GROUP (step S703). If the object of the other device 400 does not belong to the same GROUP (step S703: No), the CPU 401 proceeds to step S704. If the object of the other device 400 belongs to the same GROUP (step S703: Yes), the CPU 401 proceeds to step S705.
　ステップＳ７０４では、ＣＰＵ４０１は、このオブジェクトが自ＧＲＯＵＰを親鍵として持つオブジェクトであるか判断する（ステップＳ７０４）。このオブジェクトが自ＧＲＯＵＰを親鍵として持つオブジェクトであれば（ステップＳ７０４：Ｙｅｓ）、ステップＳ７０５に移行する。このオブジェクトが自ＧＲＯＵＰを親鍵として持つオブジェクトでなければ（ステップＳ７０４：Ｎｏ）、ステップＳ７０６に移行する。 In step S704, the CPU 401 determines whether this object is an object having its own GROUP as a parent key (step S704). If this object is an object having its own GROUP as a parent key (step S704: Yes), the process proceeds to step S705. If this object is not an object having its own GROUP as a parent key (step S704: No), the process proceeds to step S706.
　ステップＳ７０５では、ＣＰＵ４０１は、アクセスした他機４００のオブジェクトとの接続を許可する（ステップＳ７０５）。一方、ステップＳ７０６では、ＣＰＵ４０１は、アクセスした他機４００のオブジェクトとの接続を拒否する（ステップＳ７０６）。以上により、自機と他機との間について、オブジェクトが同一ＧＲＯＵＰに属するかあるいは自ＧＲＯＵＰを親鍵として持つオブジェクトとの間でのみ通信接続できるようになる。 In step S705, the CPU 401 permits connection with the accessed object of the other device 400 (step S705). On the other hand, in step S706, the CPU 401 rejects connection with the accessed object of the other device 400 (step S706). As described above, between the own device and the other device, communication connection can be established only between an object belonging to the same GROUP or an object having the own GROUP as a parent key.
　そして、接続許可されたオブジェクトは機器４００間で共有されるＳｈａｒｅｄオブジェクトとして用いられ、接続拒否されたオブジェクトは、機器４００間で共有されないＩｓｏｌａｔｅｄオブジェクトとして用いられる。このように、実施の形態によれば、オブジェクトの種別に応じた共有の可否を容易に設定し、この設定に基づき容易に運用できるようになる。 Then, the connection-permitted object is used as a Shared object shared between the devices 400, and the connection-rejected object is used as an Isolated object that is not shared between the devices 400. As described above, according to the embodiment, it is possible to easily set whether or not to share according to the type of object, and to easily operate based on this setting.
　以上説明したように、実施の形態によれば、自機のオブジェクトは、同一グループの同一鍵を持つオブジェクト、あるいは自グループの親鍵を持つオブジェクトとのみ接続することができるようになり、グループ間の階層構造に基づく、鍵、および親鍵の属性を用いて、相互に接続するオブジェクト（機器）を容易に選択できるようになる。 As described above, according to the embodiment, the own object can be connected only to an object having the same key in the same group or an object having the parent key of the own group. The objects (devices) to be connected to each other can be easily selected by using the attributes of the key and the parent key based on the hierarchical structure.
　特に、生成した鍵および親鍵を用いて同一グループあるいは同一の親グループに属するかを判断するだけでオブジェクトの共有の可否を判断できるため、制御部の制御処理負担を軽減でき、安価な組み込み機器等に用いて好適である。 In particular, since it is possible to determine whether objects can be shared simply by determining whether they belong to the same group or the same parent group using the generated key and the parent key, the control processing burden of the control unit can be reduced, and an inexpensive embedded device It is suitable for use.
　以上説明した、機器間接続方法は、予め用意された機器間接続プログラムをパーソナル・コンピュータ（ＰＣ）やスマートフォン等に搭載されたコンピュータで実行することにより実現することができる。本機器間接続プログラムは、磁気ディスク、光ディスク、ＵＳＢ（Ｕｎｉｖｅｒｓａｌ　Ｓｅｒｉａｌ　Ｂｕｓ）フラッシュメモリなどのコンピュータで読み取り可能な記録媒体に記録され、コンピュータによって記録媒体から読み出されることによって実行される。また、波形データ変換プログラムは、インターネット等のネットワークを介して配布してもよい。 The device connection method described above can be realized by executing a device connection program prepared in advance on a computer mounted on a personal computer (PC), a smartphone, or the like. The inter-device connection program is recorded on a computer-readable recording medium such as a magnetic disk, an optical disk, or a USB (Universal Serial Bus) flash memory, and is executed by being read from the recording medium by the computer. Further, the waveform data conversion program may be distributed via a network such as the Internet.
　以上のように、本発明は、オブジェクトを共有する各種コンピュータ装置に適用することができ、相互の接続を鍵を用いて判断する機器に用いて好適である。 As described above, the present invention can be applied to various computer apparatuses that share objects, and is suitable for use in devices that determine mutual connection using a key.
　２００　鍵生成部
　２０１　鍵の素（ファイル）
　２０２　鍵ファイル
　４００　機器
　４０１　ＣＰＵ
　４０２　ＲＯＭ
　４０３　ＲＡＭ
　４０９　通信インターフェース 200 Key generation unit 201 Key element (file)
202 Key file 400 Device 401 CPU
402 ROM
403 RAM
409 Communication interface

Claims (6)

  1. 　自機と他機との間の機器間接続方法において、
    　前記自機は、前記他機のオブジェクトにアクセスしたとき、前記自機のオブジェクトと前記他機のオブジェクトとが同一グループの同一鍵を有している場合にのみ、前記自機のオブジェクトが前記他機のオブジェクトにアクセス可能と判断する、
    　ことを特徴とする機器間接続方法。     In the inter-device connection method between your machine and other machines,
    When the own device accesses the object of the other device, the object of the own device and the other device have the same key in the same group only when the object of the own device and the object of the other device have the same key. Determine that the machine object is accessible,
    A connection method between devices.
  2. 　前記自機は、当該自機のグループの親子関係を含めた鍵を生成し、
    　前記他機のオブジェクトにアクセスしたとき、前記他機のオブジェクトが前記自機と同一グループの親鍵を有している場合には、前記他機のオブジェクトにアクセス可能と判断する、
    　ことを特徴とする請求項１に記載の機器間接続方法。     The own machine generates a key including the parent-child relationship of the group of the own machine,
    When accessing the object of the other machine, if the object of the other machine has a parent key of the same group as the own machine, it is determined that the object of the other machine is accessible.
    The inter-device connection method according to claim 1.
  3. 　前記自機は、前記アクセス可能と判断した前記他機のオブジェクトを共有オブジェクトとすることを特徴とする請求項１または２に記載の機器間接続方法。 3. The inter-device connection method according to claim 1 or 2, wherein the own device determines the object of the other device determined to be accessible as a shared object.
  4. 　自機のオブジェクトと他機のオブジェクトを共有するオブジェクト共有機器において、
    　前記自機は、前記他機のオブジェクトにアクセスしたとき、前記自機のオブジェクトと前記他機のオブジェクトとが同一グループの同一鍵を有している場合にのみ、前記自機のオブジェクトが前記他機のオブジェクトにアクセス可能と判断する制御部を備えた、
    　ことを特徴とするオブジェクト共有機器。     In the object sharing device that shares the object of own machine and the object of other machine,
    When the own device accesses the object of the other device, the object of the own device and the other device have the same key in the same group only when the object of the own device and the object of the other device have the same key. Equipped with a control unit that determines that the machine object is accessible,
    An object sharing device characterized by that.
  5. 　前記自機は、当該自機のグループの親子関係を含めた鍵を生成し、
    　前記他機のオブジェクトにアクセスしたとき、前記他機のオブジェクトが前記自機と同一グループの親鍵を有している場合には、前記他機のオブジェクトにアクセス可能と判断する、
    　ことを特徴とする請求項１に記載のオブジェクト共有機器。     The own machine generates a key including the parent-child relationship of the group of the own machine,
    When accessing the object of the other machine, if the object of the other machine has a parent key of the same group as the own machine, it is determined that the object of the other machine is accessible.
    The object sharing apparatus according to claim 1.
  6. 　前記自機は、前記アクセス可能と判断した前記他機のオブジェクトを共有オブジェクトとすることを特徴とする請求項４または５に記載のオブジェクト共有機器。 6. The object sharing device according to claim 4, wherein the own device sets the object of the other device determined to be accessible as a shared object.
PCT/JP2015/086439 2015-12-25 2015-12-25 Inter-device connection method and object sharing device WO2017110003A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2015/086439 WO2017110003A1 (en) 2015-12-25 2015-12-25 Inter-device connection method and object sharing device
JP2017557670A JP6705836B2 (en) 2015-12-25 2015-12-25 Device connection method and object sharing device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/086439 WO2017110003A1 (en) 2015-12-25 2015-12-25 Inter-device connection method and object sharing device

Publications (1)

Publication Number Publication Date
WO2017110003A1 true WO2017110003A1 (en) 2017-06-29

Family

ID=59089907

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/086439 WO2017110003A1 (en) 2015-12-25 2015-12-25 Inter-device connection method and object sharing device

Country Status (2)

Country Link
JP (1) JP6705836B2 (en)
WO (1) WO2017110003A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005106681A1 (en) * 2004-04-30 2005-11-10 Matsushita Electric Industrial Co., Ltd. Digital copyright management using secure device
JP2005539423A (en) * 2002-09-16 2005-12-22 サムスン エレクトロニクス カンパニー リミテッド Metadata encryption / decryption method, encrypted metadata management method and system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005539423A (en) * 2002-09-16 2005-12-22 サムスン エレクトロニクス カンパニー リミテッド Metadata encryption / decryption method, encrypted metadata management method and system
WO2005106681A1 (en) * 2004-04-30 2005-11-10 Matsushita Electric Industrial Co., Ltd. Digital copyright management using secure device

Also Published As

Publication number Publication date
JPWO2017110003A1 (en) 2018-07-26
JP6705836B2 (en) 2020-06-03

Similar Documents

Publication Publication Date Title
JP2013521587A (en) Information protection using zones
US20210073398A1 (en) Permission management of cloud-based documents
US20220335007A1 (en) Method and system for using dynamic content types
JP2017517773A (en) Securing directed acyclic graphs
JP2013257638A (en) Remote desktop system and control method
WO2014141802A1 (en) Information processing device, information processing system, information processing method, and program
US20190306270A1 (en) Methods And Systems Of Identifying A Device Using Strong Component Conflict Detection
JP2011154496A (en) Program and device for setting access right and access right management system
US10521168B2 (en) Encrypted document printing utilizing multiple networks
WO2017110003A1 (en) Inter-device connection method and object sharing device
JP6755539B2 (en) Methods and equipment for publishing copyrighted works on networks
JP6038828B2 (en) Electronic equipment and data management program
JP5984400B2 (en) Storage device, control method therefor, and program
AU2019208267A1 (en) Information processing system
JP6572679B2 (en) Information processing apparatus and program
JP6366457B2 (en) Information sharing apparatus and information sharing method
TW201926017A (en) Electronic device and web page management method thereof
JP2015162200A (en) File management device
JP5023295B2 (en) User environment restoration system and user environment restoration method
US20140320905A1 (en) Data managing system, image processing apparatus, image restoring apparatus, storage medium, and data managing method
US20200272601A1 (en) Information processing apparatus and non-transitory computer readable medium
JP2012238113A (en) File management device, file management method, and file management program
JP2010205020A (en) Device, method and program for password management
LIU Distributed data mining of Inner Mongolia tourism geographic information based on GIS.
JP2016126506A (en) Information processing device, program and information processing method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15911435

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017557670

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15911435

Country of ref document: EP

Kind code of ref document: A1