KR20190123680A - System and Method for Transaction in Internet of Media Things and Method therefor - Google Patents

Abstract

The present invention relates to Internet of Things. More specifically, provided is a transaction based on a block chain or the like applied to Internet of media things (MThing), which is media-oriented Internet of Things. A computer readable medium may include a command code for implementing the API when executed by a processor of the MThing.

Description

System and Method for Transaction in Internet of Media Things and Method therefor}

The present invention relates to the Internet of Things. More specifically, the present invention relates to a transaction based on a blockchain applied to the Internet of Media Things, which is a media-oriented Internet of Things.

The contents described in this section merely provide background information on the present invention and do not constitute a prior art.

The Moving Picture Experts Group (MPEG), an international standardization organization for multimedia, has standardized on the Internet of Things (MThing) -oriented media thing Internet (IoMT) through the MPEG-IoMT (Internet of Media Things (ISO / IEC JTC1 23093) project. Is in progress. MPEG-IoMT discusses the application program interface (API) for data exchange between media objects and standardization of data formats exchanged between media objects. In particular, in recent years, attempts have been made to apply a blockchain to the media thing internet for the purpose of establishing a decentralized media thing internet system environment and for autonomous and secure transactions between the media things constituting it.

The present invention proposes a blockchain-based transaction between media objects and an API of media objects for supporting the same. 'Transaction' in the media thing internet includes not only simple transactions such as currency exchange, but also the meaning of all information exchanges that occur between media objects.

According to an aspect of the present invention, there is provided a computer-readable recording medium including instruction code for implementing an API when executed by a processor of Media Thing (MThing). The API may include a function having a token type and a token name as parameters, and returning a cost to be paid to receive a predetermined media service if the input token type and token name are supported; A function that has the token type and the token name as parameters and returns a wallet address according to the token type and the token name; And a function having as a parameter a transaction identifier (tid) assigned to the payment for the wallet address by an external payment system, and providing the predetermined service.

The API may further include a function having the transaction identifier as a parameter and checking the external payment system to determine whether a transaction corresponding to the transaction identifier is completed.

The API includes a function that takes a token type and a token name as parameters and returns a list of required token types and media objects supporting the token name; And a function of returning a list of media objects that support the type and capabilities of the media thing and having the type and capability of the media thing as parameters.

The API has parameters of the wallet address and token amount of another media thing providing another predetermined service, and the amount of the token specified by the parameter is determined through the external payment system. It may further include a function that sends to the address, and returns the associated transaction ID (transaction ID).

According to another aspect of the invention, the first media thing is a method for performing a transaction with the second media thing, the cost to be paid in order to receive a token type (tokenType) and token name (tokenName) to receive a predetermined media service Calling a function supported by the API of the second media thing to return; Acquiring the function, supported by the API of the second media thing, which receives the token type and the token name and returns a wallet address according to the token type and the token name; Paying a predetermined amount of tokens to a wallet address of the second media thing through an external payment system, and obtaining a transaction identifier assigned to the payment for the wallet address; And invoking a function supported by the API of the second media thing, which receives the transaction identifier and provides a predetermined service.

According to another aspect of the invention, a Media Thing (MThing) device, comprising: a first processing module for creating, storing, or processing media; And a second processing module for executing an API for processing an instruction received from another media thing, wherein the API has a token type and a token name as parameters, and an input token type and a token. A function for returning a cost to be paid in order to receive a given media service, if the name is supported; A function that has the token type and the token name as parameters and returns a wallet address according to the token type and the token name; And a function having as a parameter a transaction identifier (tid) assigned to the payment for the wallet address by an external payment system, and providing the predetermined service.

According to the present invention, the process of exchanging information between all media things in the IoMT transaction process is performed through a blockchain smart contract. Therefore, no separate server or administrator intervention is required, and thus a decentralized IoMT network can be operated.

Users who want to use the functions of media things can also freely exchange information and use various services with media things through the Web, decentralized application (DApp) or distributed app platform.

1 illustrates an IoMT architecture to which a transaction method according to the present invention may be applied.
2 shows an example process for discovering MThings on a network with the required capability.
3 shows a process for associating MThings with the required capabilities with a function.
4 shows an example process for disconnecting (ie releasing capabilities) MThing.
5 shows an example process that MThing notifies other MThings that some or all of all capabilities are not available.
6 shows a flow diagram illustrating an example transaction process between a user and MThing.
7 shows a flow diagram illustrating an example transaction process between MThings.

Hereinafter, some embodiments of the present invention will be described in detail through exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are only for distinguishing the components from other components, and the nature, order or order of the components are not limited by the terms. Throughout the specification, when a part is said to include, 'include' a certain component, which means that it may further include other components, except to exclude other components unless otherwise stated. . In addition, as described in the specification. The term 'module' refers to a unit that processes at least one function or operation, which may be implemented by hardware or software or a combination of hardware and software.

Terms referred to in this disclosure, in general, can be understood as follows.

"Media" means data that can be rendered, including audio, video, text, graphics, images, haptic and tactile information.

"Media Thing" (MThing) refers to a thing capable of sensing, collecting, actuating or processing media or metadata. The media object may include a media sensor (MSensor), a media actuator (MAcuator), a media aggregator (MAggregator), a media analyzer (MAnalyzer), and the like. Media actuators are components that carry digital information to change some attributes of a physical entity.

The "Internet of Media Things (IoMT)" is a special subset of the IoT whose main functions are related to media processing.

"Media IoT Device (IoMT Device)" refers to an IoT device having at least one media thing (MThing).

A "media token" is a virtual token for accessing the functions, resources and data of the media thing.

The present disclosure generally relates to an API for supporting a transaction on the Internet of Things using a blockchain-based cryptocurrency or a fiat currency and a transaction method thereof.

1 illustrates an IoMT architecture to which a transaction method according to the present invention may be applied.

Each MThing may include sensors, submodules such as actuators, media processing modules, command & communication processing modules. The sensor may collect media data about an entity in a real or virtual world. Actuators can affect the state of an entity. The media processing module may analyze the media data collected by the sensor and extract meaningful information to determine a task to be performed. The command & communication processing module can interpret commands or communication messages from other media objects.

As shown in FIG. 1, an interface for IoMT includes an interface between a user and an MThing (hereinafter referred to as a 'first interface') and an interface between a sensor, a controller, and a processor included in the MThing (hereinafter, ' A second interface ”and an MThing interface (hereinafter referred to as a“ third interface ”).

The 'first interface' is a user interface between the user and the MThing, and may include setup information for controlling the MThing. Here, the 'user' may include a 'designer', an 'Internet' service or a content designer of the product, and the 'setup information' may include a feature parameter setup of MThing or a command performed when MThing meets a certain condition.

The 'first' interface is an interface for transmitting and receiving user setup information defined in the first interface between MThings.

The second interface is an interface for processing sensor data and actuation data generated from sensors or actuators included in MThing. Here, the 'sensor data' refers to not only data (eg, video data) detected from the sensor, but also high-level sensor data (eg, face descriptor, fingerprint descriptor, medical diagnosis name, etc.) obtained by processing the data. It may include. Actuation data is information about an object of interest (e.g., Binary Format for Scene: BIFS) that is used when the entity of interest detected in one MThing is utilized as content in another MThing (e.g., display monitor). ) May be included.

The "second 'interface" is an interface in which data of the second interface is converted into a format for transfer between MThings and transmitted.

The 'third interface' is an interface for defining discovery, performance, characteristics, and the like of MThing, and may include the first and second interfaces.

MThings and entities can use the MPEG-IoMT standard application programming interface (API) to discover, connect, and exchange data in a standardized format. A working draft of MPEG-IoMT Part 1 (ISO / IEC 23093-1) is available from https://www.iso.org/standard/57796.html. A working draft of MPEG-IoMT Part 2 (ISO / IEC 23093-2) is available from https://www.iso.org/standard/74332.html. A working draft of MPEG-IoMT Part 3 (ISO / IEC 23093-3) is available from https://www.iso.org/standard/74333.html.

The following describes APIs of Mthings for supporting a transaction process on Media Internet of Things (IoMT), while manipulating MThings and exchanging structured data between MThings, and using blockchain-based cryptocurrency. The following APIs are described based on JAVA programming, but it is obvious that they may be implemented in other programming languages such as C ++ and C.

1.class MThing

Class MThing is the base class for all kinds of MThings. This class contains the essential fields and methods of MThing.

Class MThing can have multiple constructors, depending on the presence of parameters and the types of parameters they use. The following table defines three constructors, including a default constructor that takes no parameters. The constructor parameter may include a string unique identifier (id) of MThing, an IP address of a string type (ipAddress), and a port of an int type.

Class MThing, as its member, has a field representing an attribute and a method representing a function. A method is a set of statements or a function for performing a particular task. That is, the API of all kinds of MThings supports the methods of class MThing. In the following description, a method and a function may be used interchangeably.

Table 1 below defines several methods of class MThing.

For example, the method discoverMThingByToken (int tokenType, String tokenName) takes a token type (tokenType) and a token name (tokenName) as its parameters when called, and returns a list of MThings that support that token type and token name. . The method isCapabilityAvailable (String MThingType, String capability), upon invocation, takes as its parameters the MediaTypeType (MThingType) and capability, and assigns the specified capability to the MediaObject of the specified MediaTypeType (MThingType). Ask for availability. The above method returns 1 if the capability is available and 0 otherwise.

The method getWalletAddress (int tokenType, String tokenName) takes a token type (tokenType) and a token name (tokenName) as its parameters when called, and the wallet address according to the requested token type and the requested token name. ) The method returns the wallet address if the operation succeeds, or null if there is no wallet address for the specified tokenType (tokenType) and token name (tokenName).

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MThing () Default constructor. MThing (String id) MThing (String id, String ipAddress, Integer port) Fields Modifier and Type Field and Description String Id Unique identifier. String ipAddress int port Methods Modifier and Type Method and Description Type get () void set (Type) List <MThingInfoType> discoverMThingByCapability (String MThingType, String capability) This function returns a list of MThings that support the required capabilities. MThingType and capability may be represented by a string (eg, term ID or binary representation) of MThingTypeCS and capabilityCS specified in the Appendix of the draft of ISO / IEC 23093-3, respectively. List <MThingInfoType> discoverMThingByToken (int tokenType, String tokenName) This function takes a tokenType and tokenName as its parameters and returns a list of MThings that support that tokentype and token name. A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 .
Yes) dicoverMThingByToken (0, "BTC") or dicoverMThingByToken (0, "00000001")
Ex) dicoverMThingByToken (1, "USD") or dicoverMThingByToken (1, "10010100") int isCapabilityAvailable (String MThingType, String capability) This function takes as its parameters the MThingType and capability, and queries the availability of the specified capabilities for the media object of the specified MThingType. MThingType and capability may be represented by a string (eg, term ID or binary representation) of MThingTypeCS and capabilityCS specified in the Appendix of the draft of ISO / IEC 23093-3, respectively.
This function returns 1 if the capability is available and 0 otherwise.
Ex) isCapabilityAvailable ("MSensor", "SENSOR_CAPTURE_AUDIO"); Or isCapabilityAvailable ("0000000", "00000001"); String getWalletAddress (int tokenType, String tokenName) This function takes a tokenType and a tokenName as its parameters and returns a wallet address according to the requested token type and token name. A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 .
Yes) getWalletAddress (0, "BTC") or getWalletAddress (0, "00000001")
Ex) getWalletAddress (1, "USD") or getWalletAddress (1, "10010100") String sendTokens (String walletAddress, float amount) This function passes the token to the receiver MThing using the wallet address of the receiver MThing. The amount of tokens specified by the parameter amount is sent to the walletAddress. This function returns the transaction ID if the operation succeeds or null if it fails. float checkTransactionCompletion (String tid) This function checks for transaction completion using the transaction ID tid . Which MThing (e.g., the token sender) and the corresponding MThing (e.g., token receiver) may check with the external payment system whether the (token) transaction was completed with the transaction ID tid . If the transaction is complete, the token amount is returned; otherwise, -1 is returned. int connectMThing (MThingInfoType myMThingInfo) This function sends (requester) MThing information, myMThingInfo, to reserve all available capabilities of the target MThing. Returns 1 if the operation is successful, 0 if the operation fails, or -1 if the target MThing does not respond. int connectMThing (MThingInfoType myMThingInfo, String targetMThingType, String targetCapability) This function reserves the specified capability of the target MThing by sending myMThingInfo (requester) MThing information. The targetMThingType and targetCapability may be expressed as a string (eg, a term ID or binary representation) of MThingTypeCS and capabilityCS, which will be defined in the Appendix of the draft of ISO / IEC 23093-3, respectively. Returns 1 if the operation is successful, 0 if the operation fails, or -1 if the target MThing does not respond.
Ex) connectMThing (myMThingInfo, "MSensor", "SENSOR_CAPTURE_AUDIO"); or
connectMThing (myMThingInfo, "0000000", "00000001"); int disconnectMThing (MThingInfoType myMThingInfo) This function sends (requester) MThing information myMThingInfo to release all reserved functions of the target MThing. If the operation succeeds, it returns 1; if it fails, it returns 1; if the target MThing does not respond, it returns -1. int disconnectMThing (MThingInfoType myMThingInfo, String targetMThingType, String targetCapability) This function sends the (requester) MThing information myMThingInfo to release the specified function of the target MThing. The targetMThingType and targetCapability may be represented by a string (eg, a term ID or binary representation) of MThingTypeCS and capabilityCS, which will be defined in the Appendix of the draft of ISO / IEC 23093-3, respectively. This function returns 1 if the operation succeeds, 0 if it fails, and -1 if the target MThing does not respond.
Ex) disconnectMThing (myMThingInfo, "MSensor", "SENSOR_CAPTURE_AUDIO"); or
disconnectMThing (myMThingInfo, "0000000", "00000001"); int alertDisconnection (MThingInfoType myMThingInfo) This function sends the (requester) MThing information myMThingInfo to alert the target MThing to disconnect all reserved capabilities of the requester MThing. This function returns 1 if the operation succeeds, 0 if it fails, and -1 if the target MThing does not respond. int alertDisconnection (MThingInfoType myMThingInfo, String myMThingType, String myCapability) This function sends a (requester) MThing information, myMThingInfo, to warn the target MThing of disconnecting the specified capability of the requester MThing. myMThingType and myCapability may be represented as strings (eg, term ID or binary representation) of MThingTypeCS and capabilityCS, respectively, to be defined in the Appendix of the draft ISO / IEC 23093-3. Returns 1 if the operation is successful, 0 if the operation fails, or -1 if the target MThing does not respond.
Ex) alertDisconnectCapability (myMThingInfo, "MSensor", "SENSOR_CAPTURE_AUDIO"); or
alertDisconnectCapability (myMThingInfo, "00000000", "00000001"); MPEG21TerminalCapabilityType getMPEG21TerminalCapabilityList () This function creates TerminalCapabilityType, a hardware description that conforms to the MPEG-21 specification. "MPEG21TerminalCapabilityType", which is a type of returned data, will be described later.

2. Return type class

Now, the return type classes, MThingInfoType and MPEG21 Terminal CapabilityType, are described.

2-1. MThingInfoType

The following table defines the return type class MThingInfoType that conveys MThing information. That is, the MThing information may be provided in the class defined in the table below. Therefore, another MThing can obtain MThing information by using various methods included in the class MThingInfoType.

Constructor Constructor and Description MThingInfoType () Default constructor. MThingInfoType (int type, String MThingInfo) Fields Modifier and Type Field and Description int type Return type of MThing information: 0 = None, 1 = XML, 2 = Binary, 3 = JSON String MThingInfo MThing Information The data format described by MThingInfo's data format specified in the draft of ISO / IEC 23093-3 may contain MThing metadata, (absolute) time information of the metadata, and a list of tokens supported by MThing. have. Methods Modifier and Type Method and Description int getType () void setType (int type) String getMThingInfo () void setMThingInfo (String MThingInfo)

2-2. MPEG21TerminalCapabilityType

The table below defines a return type class MPEG21TerminalCapabilityType that conveys the hardware capabilities of MThing, described by the terminal capabilities specified in MPEG-21 DIA (ISO / IEC 23000-7). That is, hardware capabilities can be provided in the classes defined in the table below. Thus, other MThings can obtain hardware capabilities using various methods included in the class MPEG21TermCapabilityType.

Constructor Constructor and Description MPEG21TerminalCapabilityType () Default constructor. MPEG21TerminalCapabilityType (int type, String mpeg21Data) Fields Modifier and Type Field and Description int type Return type of hardware capability: 0 = None, 1 = XML, 2 = Binary, 3 = JSON String mpeg21Data Terminal (eg, hardware) capability information according to the specification of terminal capabilities of MPEG-21 Methods Modifier and Type Method and Description int getType () void setType (int type) String getMPEG21Data () void setMPEG21Data (String mpeg21Data)

3. API for IoMT sensors

The API of IoMT sensors supports the following MSensor class. The MSensor class inherits the features of the aforementioned MThing class. The MSensor class contains several methods (that is, functions) that return a class (that is, Java or C ++) or a structure (that is, C).

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MSensor () Default constructor. MSensor (String id) MSensor (String id, String ipAddress, integer port) Fields Modifier and Type Field and Description Methods Modifier and Type Method and Description MPEGVCapabilityType getMPEGVCapability () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include sensor capabilities of return types (eg XML, Binary) and ISO / IEC 23005-2 (MPEG-V Part 2). MPEGVSensedDataType getMPEGVSendsedData () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include actuator capabilities of return type (eg XML, Binary) and ISO / IEC 23005-5 (MPEG-V Part 5). CapabilityListType getSensorCapabilityList (); This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include a list of return types (eg XML, Binary) and capabilities as defined herein. CapabilityListType getAvailableSensorCapabilityList () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include the return types (e.g., XML, Binary) and the list of available capabilities as defined herein. CapabilityListType getAppliedSensorCapabilityList () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include the return types (e.g., XML, Binary) defined in this specification, and the list of applied capabilities. SensedDataType getCapturedTime () This function returns the captured time of the sensed data. SensedDataType getCapturedTime (String tid) This function returns the captured time of the sensed data. tid is the token transaction ID of the corresponding service. float getCapturedTime_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use getCapturedTime () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) getCapturedTime_Cost (0, "BTC") or getCapturedTime_Cost (0, "00000001")
Ex) getCapturedTime_Cost (1, "USD") or getCapturedTime_Cost (1, "10010100")

3-1. API for IoMT microphone

The API of an IoMT sensor (ie IoMT microphone) with microphone capability supports the following MMicrophone classes. The MMicrophone class inherits the features of the MSensor class described above.

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MMicrophone () Default constructor. MMicrophone (String id) MMicrophone (String id, String ipAddress, integer port) Fields Modifier and Type Field and Description Methods Modifier and Type Method and Description String getAudioURL () This function returns the URL of the audio source. String getAudioURL (String tid) This function returns the URL of the audio source. tid is the transaction ID of the payment to use this function. float getAudioURL_CostPerMinute (int tokenType, String tokenName) This function returns the amount of tokens to use getAudioURL () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Ex) getAudioURL_CostPerMinute (0, "BTC") or getAudioURL_CostPerMinute (0, "00000001")
Ex) getAudioURL_CostPerMinute (1, “USD”) or getAudioURL_CostPerMinute (1, "10010100")

3-2. API for IoMT cameras

The API of an IoMT sensor (ie IoMT camera) with camera capability supports the following MMicrophone classes. The MMicrophone class inherits the features of the MSensor class described above.

As shown in the table below, the fields (ie attributes) of the MCamera class include the MCamera's unique identifier (id), IP address (ipAddress), and port. The data types of the unique identifier (id), the IP address (ipAddress), and the port are a string, a string, and an integer, respectively.

Methods (that is, functions) of the MCamera class include getVideoURL (), getVideoURL (String tid), getVideoURL_CostPerMinute (int tokenType, String tokenName), getImageURL (), getImageURL (String tid), getImageURL_Cost (int tokenType, String tokenName) . For example, the method getVideoURL_CostPerMinute (int tokenType, String tokenName), upon its invocation, takes a tokenType (tokenType) and a token name (tokenName), and returns the amount of tokens per minute for using getVideoURL ().

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MCamera () Default constructor. MCamera (String id) MCamera (String id, String ipAddress, integer port) Fields Modifier and Type Field and Description Methods Modifier and Type Method and Description String getVideoURL () This function returns the URL of the video source. String getVideoURL (String tid) This function returns the URL of the video source. tid is the transaction ID of the payment to use this function. float getVideoURL_CostPerMinute (int tokenType, String tokenName) This function returns the amount of tokens to use getVideoURL () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) getVideoURL_CostPerMinute (0, "BTC") or getVideoURL_CostPerMinute (0, "00000001")
Ex) getVideoURL_CostPerMinute (1, "USD") or getVideoURL_CostPerMinute (1, "10010100") String getImageURL () This function returns the URL of the image source. String getImageURL (String tid) This function returns the URL of the image source. tid is the transaction ID of the payment to use this function. float getImageURL_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use getImageURL () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) getImageURL_Cost (0, "BTC") or getImageURL_Cost (0, "00000001")
Ex) getImageURL_Cost (1, "USD") or getImageURL_Cost (1, "10010100")

4. API for IoMT Actuators

The API of the IoMT actuators supports the following MActuator classes. The MActuator class inherits the features of the aforementioned MThing class. The MActuator class contains several methods (that is, functions) that return a class (that is, Java or C ++) or a structure (that is, C).

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MActuator () Default constructor. MActuator (String id) MActuator (String id, String ipAddress, integer port) Fields Modifier and Type Field and Description Methods Modifier and Type Method and Description MPEGVCapabilityType getMPEGVCapability () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include actuator types of return type (eg XML, Binary) and ISO / IEC 23005-2 (MPEG-V Part 2). int setMPEGVCommand (MPEGVCommandType mpegvCommand) This function sets the command to the actuator according to the specifications of the actuator commands in ISO / IEC 23005-5 (MPEG-V Part 5). This function returns 1 if the operation is successful and 0 otherwise. CapabilityListType getCapabilityList () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures contain a list of capabilities using the return types (eg XML, Binary) and data formats defined herein. CapabilityListType getAvailableActuatorCapabilityList () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures contain a list of available capabilities expressed using the return types (eg, XML, Binary) and data formats defined herein. CapabilityListType getAppliedActuatorCapabilityList () This function returns a class (ie Java or C ++) or a structure (ie C). These classes or structures include a return type (eg, XML, Binary) and a list of applied capabilities, expressed using the data format defined herein.

4-1. API for IoMT speaker

The API of an IoMT actuator (ie IoMT speaker) with speaker capabilities supports the following MSpeaker classes: The MSpeaker class inherits the features of the aforementioned MActuator class.

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MSpeaker () Default constructor. MSpeaker (String id) MSpeaker (String id, String ipAddress, integer port) Fields Modifier and Type Field and Description Methods Modifier and Type Method and Description int setAudioURL (String url) This function takes the URL of an audio source sent by another MThings. This function returns 1 if the operation is successful and 0 otherwise. int setAudioURL (String tid, String url) This function takes the URL of an audio source sent by another MThings. This function returns 1 if the operation is successful and 0 otherwise. tid is the transaction ID of the payment to use this function. float setAudioURL_CostPerMinute (int tokenType, String tokenName) This function returns the amount of tokens per minute to use setAudioURL () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) setAudioURL_CostPerMinute (0, "BTC") or setAudioURL_CostPerMinute (0, "00000001")
Ex) setAudioURL_CostPerMinute (1, "USD") or setAudioURL_CostPerMinute (1, "10010100") int setPlay (ActuationDataType play) This function controls the type of playback (for example, stop, play, pause). This function returns 1 if the operation is successful and 0 otherwise. int setPlay (String tid, ActuationDataType play) This function controls the type of playback (for example, stop, play, pause). This function returns 1 if the operation is successful and 0 otherwise. tid is the transaction ID of the payment to use this function. float setPlay_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use setPlay () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) setPlay_Cost (0, "BTC") or setPlay_Cost (0, "00000001")
Ex) setPlay_Cost (1, "USD") or setPlay_Cost (1, "10010100") int setVolume (ActuationDataType volume) This function adjusts the volume of the sound. This function returns 1 if the operation is successful and 0 otherwise. int setVolume (String tid, ActuationDataType volume) This function adjusts the volume of the sound. This function returns 1 if the operation is successful and 0 otherwise. tid is the transaction ID of the payment to use this function. float setVolume_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use setVolume () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) setVolume_Cost (0, "BTC") or setVolume_Cost (0, "00000001")
Ex) setVolume_Cost (1, "USD") or setVolume_Cost (1, "10010100")

4-2. API for IoMT display

The API of an IoMT actuator with display capabilities (ie, IoMT display) supports the following MDisplay class: The MDisplay class inherits the features of the above-described MActuator class.

The MDisplay class has its members, a field representing attributes and a method representing functionality.

As shown in Table 9 below, the fields (ie attributes) of the MDisplay class include MCamera's unique identifier (id), IP address (ipAddress), and port. The data types of the unique identifier (id), the IP address (ipAddress), and the port are a string, a string, and an integer, respectively.

Nested classes Modifier and Type Method and Description Constructor Constructor and Description MDisplay () Default constructor. MDisplay (String id) MDisplay (String id, String ipAddress, integer port) Fields Modifier and Type Field and Description Methods Modifier and Type Method and Description int setVideoURL (String url) This function gets the URL of the video source from another MThing. This function returns 1 if the operation is successful and 0 otherwise. int setVideoURL (String tid, String url) This function gets the URL of the video source from another MThing. This function returns 1 if the operation is successful and 0 otherwise.
tid is the transaction ID of the payment to use this function. int setVideoURL_CostPerMinute (int tokenType, String tokenName) This function returns the amount of tokens per minute to use setVideoURL () .
A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender".
tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) setVideoURL_CostPerMinute (0, "BTC") or setVideoURL_CostPerMinute (0, "00000001")
Ex) setVideoURL_CostPerMinute (1, "USD") or setVideoURL_CostPerMinute (1, "10010100") int setPlay (ActuationDataType play) This function controls the type of playback (eg, stop, play, pause). This function returns 1 if the operation is successful and 0 otherwise. int setPlay (String tid, ActuationDataType play) This function controls the type of playback (eg, stop, play, pause). This function returns 1 if the operation is successful and 0 otherwise. Where tid is the transaction ID of the payment to use this feature. int setPlay_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use setPlay () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender".
tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Ex) setPlay_Cost (0, "BTC") or setPlay_Cost (0, "00000001")
Ex) setPlay_Cost (1, "USD") or setPlay_Cost (1, "10010100") int setDisplayResolution (ActuationDataType resolution) This function controls the resolution of the video display. This function returns 1 if the operation is successful, 0 otherwise, and 1 otherwise. int setDisplayResolution (String tid, ActuationDataType resolution) This function controls the resolution of the video display. This function returns 1 if the operation is successful and 0 otherwise. tid is the transaction ID of the payment to use this function. int setDisplayResolution_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use setDisplayResolution () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) setDisplayResolution_Cost (0, "BTC") or setDisplayResolution_Cost (0, "00000001")
Ex) setDisplayResolution_Cost (1, "USD") or setDisplayResolution_Cost (1, "10010100") int setBrightness (ActuationDataType brightness) This function controls the brightness of the display. This function returns 1 if the operation is successful and 0 otherwise. int setBrightness (String tid, ActuationDataType brightness) This function controls the brightness of the display. This function returns 1 if the operation is successful and 0 otherwise. tid is the transaction ID of the payment to use this function. int setBrightness_Cost (int tokenType, String tokenName) This function returns the amount of tokens to use setBrightness () . A tokenType of 0 indicates "Crypto Currency" and a tokenType of 1 indicates "Legal Tender". tokenName is represented as a string (eg, term ID or binary representation) of TokenCS to be specified in the Appendix of the draft of ISO / IEC 23093-3 . If the requested token is not supported, -1 is returned.
Yes) setBrightness_Cost (0, "BTC") or setBrightness_Cost (0, "00000001")
Ex) setBrightness_Cost (1, "USD") or setBrightness_Cost (1, "10010100")

Now, some example scenarios using the above-described APIs will be described.

2 shows an example process for discovering MThings on a network with the required capability. In addition to its capabilities, MThing can also be found as a supported media token type, using the method discoverMThingByToken (int tokenType, String tokenName) illustrated in Table 1. Each MThing that supports the required capability or media token type can return its own information.

In FIG. 2, MThing (i.e. requester) broadcasts a message looking for other MSensors capable of capturing audio using discoverMThingByCapability () (1) in FIG. 2). Each MSensor (eg, MMicrophone1, MMicrophone2, MCamera1) sends its own information using sendBackMThingInfo () which returns the data format MThingInfo defined in ISO / IEC 23093-3 (2 in FIG. 2).

3 shows a process for associating MThings with the required capabilities with a function. MThing (ie, "ReqMThing" in FIG. 3) may query the availability of a specific capability (eg, SENSOR_CAPTURE_AUDIO) with the function isCapabilityAvailable () for another MThing (1 in FIG. 3). If the "SENSOR_CAPTURE_AUDIO" capability is not currently available, MThing (e.g., MMicrophone1 in Figure 3) announces "unavailable" (2 in Figure 3). ReqMThing may use the binary representations of "MSensor" and "SENSOR_CAPTURE_AUDIO" to query other MThings (eg, ③ in FIG. 3) again for the availability of this particular capability. When MCamera1 informs ReqMThing that the "SENSOR_CAPTURE_AUDIO" capability is available (④ in FIG. 3), ReqMThing may connect to MCamera1 and reserve the "SENSOR_CAPTURE_AUDIO" function of MCamera1 (⑤ in FIG. 3). As long as the function "SENSOR_CAPTURE_AUDIO" of MCamera1 is used by ReqMThing, other MThings cannot access the function.

4 shows an example process for disconnecting (ie releasing capabilities) MThing. ReqMThing may release all reserved capacities of the MCamera using disconnectMThing () (see ① and ② of FIG. 4) or release a designated function (eg, SENSOR_CAPTURE_AUDIO) (see ③ and ④ of FIG. 4).

5 shows an example process that MThing notifies other MThings that some or all of all capabilities are not available. The MCamera may use alertDisconnection () to inform MThing_01 that all capabilities reserved by MThing_01 are not available (see ①, ② in FIG. 5), or the specified capabilities (eg SENSOR_CAPTURE_AUDIO) are no longer available to MThing_01. It may inform MThing_01 that it is not possible.

Referring now to FIGS. 6 and 7, a transaction process between a user and an MThing and between MThings will be described. Before performing the process of FIGS. 6 and 7, it may be understood that the discovery process of FIG. 2 and the connection process of FIG. 3 are first performed between these entities.

6 shows a flow diagram illustrating an example transaction process between a user and MThing. Suppose a user wants to see a video captured from a nearby camera (ie MCamera).

The user can use the getVideoURL_CostPerMinute () to obtain a video captured by the MCamera through a user interface such as a dedicated application, a decentralized application (DApp), or a web application. Cost per minute (S601 in FIG. 6) to view by cryptocurrency or fiat currency) and token name (e.g., Bitcoin or US dollars). The MCamera returns a cost per minute so that the user can use the getVideoURL () function (S602 in FIG. 6). If the user wants to watch the video at the price replied, the user inquires the wallet address (S603 in FIG. 6). The MCamera responds with an appropriate wallet address (S604 in FIG. 6).

The user sends a certain amount of tokens to the wallet address through a payment system, such as a blockchain or banking system (S605 in FIG. 6), and the payment system returns a transaction ID (i.e. tid) (S606 in FIG. 6). The user can use checkTransactionCompletion (tid) to check whether the token transaction has been successfully completed at the designated wallet address (S607 to S608 in Fig. 6). If the transaction is confirmed, the user may request a video stream service from the MCamera using getVideoURL (tid) (S609 in FIG. 6).

MCamera uses checkTransactionCompletion (tid) (S610 in FIG. 6) to confirm the completion of the token transaction and the amount of token received (S611 in FIG. 6). The MCamera returns a video URL and streams the video as the user paid (S612 in FIG. 6).

The transaction process illustrated in FIG. 6 includes other scenarios (e.g., a scenario in which the user outputs the desired audio to a nearby microphone (i.e., MMicrophone), and the user streams and plays the desired video to a nearby display (i.e., MDisplay). Scenarios).

7 shows a flow diagram illustrating an example transaction process between MThings. Suppose a camera (i.e., MCamera) wants to stream captured video to a nearby display (i.e., MDisplay) for playback.

MCamera uses setVideoURL_CostPerMinute () to query the cost per minute for playing video on the MDisplay by tokenType (e.g., cryptocurrency or fiat currency) and token name (e.g., Bitcoin or US dollars). (S701 in FIG. 7). MDisplay returns cost per minute so that MCamera can use the setVideoURL () function (S702 in FIG. 7). If the user wants to play the video at the price answered, Mcamera asks MDisplay for the wallet address (S703 in FIG. 7). MDisplay responds with the appropriate wallet address (S704 in FIG. 7).

The MCamera sends a certain amount of tokens to the wallet address through a payment system such as a blockchain or banking system (S705 in FIG. 7), and the payment system returns a transaction ID (ie tid) (S706 in FIG. 7). The MCamera may use checkTransactionCompletion (tid) to check whether the token transaction was successfully completed at the designated wallet address (S707 to S708 in FIG. 7). If the transaction is confirmed, the MCamera may request a video stream service from the MDisplay using setVideoURL (tid, url) (S709 of FIG. 7).

The MDisplay uses checkTransactionCompletion (tid) (S710 in FIG. 7) to confirm the completion of the token transaction and the amount of tokens received (S711 in FIG. 7). The MDisplay uses the received video URL to play the video as much as MCamera pays (S712 in FIG. 7), and notifies the completion of the video playback service (S713 in FIG. 7).

It should be understood that the example embodiments described above may be implemented in many different ways. In some examples, the various methods, devices, apparatuses, systems described herein have a processor, memory, disk or other mass storage, communication interface, input / output (I / O) devices, and other peripheral devices. It may be implemented by a computing device.

It is to be understood that the functional components described herein are labeled as units or modules in order to further emphasize their implementation independence. For example, the module may be implemented as a custom very-large-scale integration (VLSI) circuit or hardware circuitry including semiconductors such as gate arrays, logic chips, and transistors. The module may also be implemented as programmable hardware devices such as field programmable gate arrays (FPGAs), programmable array logic, programmable logic devices, and the like.

Meanwhile, the various methods described herein may be implemented with instructions stored on a non-transitory recording medium that can be read and executed by one or more processors. Non-transitory recording media includes all types of recording devices, for example, in which data is stored in a form readable by a computer system. For example, non-transitory recording media include storage media such as erasable programmable read only memory (EPROM), flash drives, optical drives, magnetic hard drives, solid state drives (SSD).

The above description is merely illustrative of the technical idea of the present embodiment, and those skilled in the art to which the present embodiment belongs may make various modifications and changes without departing from the essential characteristics of the present embodiment. Accordingly, the present embodiments are not intended to limit the technical spirit of the invention to be protected, but are intended to describe the scope of the technical spirit of the invention to be protected by the embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present embodiment.

Claims (7)

A computer readable recording medium containing instruction code for implementing an API when executed by a processor of a media thing (MThing), the API comprising:
A function that has a tokenType and a tokenName as parameters, and returns a cost to be paid to receive a predetermined media service if the input token type and the token name are supported;
A function that has the token type and the token name as parameters and returns a wallet address according to the token type and the token name; And
A function having as a parameter a transaction identifier (tid) assigned to payment for the wallet address by an external payment system, and providing the predetermined service.
Computer-readable recording medium comprising a. The method of claim 1,
The API is
And having a transaction identifier as a parameter and checking a function of the external payment system to determine whether a transaction corresponding to the transaction identifier is completed. The method of claim 1,
The API is
A function having a token type and a token name as parameters, and returning a list of required token types and media objects supporting the token name; And
A function that takes a media object's type and capability as a parameter and returns a list of media objects that support the type and capability of the media object.
The computer readable recording medium further comprising. The method of claim 1,
The API is
It has the parameters of the wallet address and the amount of tokens of other media things that provide other predetermined services, and sends the amount of tokens specified by the parameters to the wallet address of the other media things through the external payment system, And a function for returning an associated transaction ID. In a method in which a first media thing performs a transaction with a second media thing,
Invoking a function, supported by the API of the second media thing, that takes a tokenType and a tokenName and returns a cost to be paid for providing a predetermined media service;
Acquiring the function, supported by the API of the second media thing, which receives the token type and the token name and returns a wallet address according to the token type and the token name;
Paying a predetermined amount of tokens to a wallet address of the second media thing through an external payment system, and obtaining a transaction identifier assigned to the payment for the wallet address; And
Invoking a function supported by the API of the second media thing, which receives the transaction identifier and provides a predetermined service;
How to include. The method of claim 5,
Checking whether the transaction corresponding to the transaction identifier is completed to the external payment system;
How to include more. As a Media Thing (MThing) device,
A first processing module for creating, storing, or processing media; And
A second processing module for executing an API for processing an instruction received from another media object, wherein the API includes:
A function that has a tokenType and a tokenName as parameters, and returns a cost to be paid to receive a predetermined media service if the input token type and the token name are supported;
A function that has the token type and the token name as parameters and returns a wallet address according to the token type and the token name; And
A function having as a parameter a transaction identifier (tid) assigned to payment for the wallet address by an external payment system, and providing the predetermined service.
Including, the media thing device.

Images