System and method for securely creating a listing of a device on an online device marketplace platform

Abstract

The present invention is entitled "System and method for securely creating a list of devices on an online device market platform". The present invention discloses a method for securely enabling a user to create a list of devices on an online device market platform. The method may include: receiving a request from a user to create a list of devices on an online device market platform; prompting the user to upload one or more images or documents of the device; receiving one or more images or documents of the device from the user, the one or more images or documents containing information of the device; determining whether to verify the identity of the device based on the information of the device in the one or more images or documents; and if the identity of the device is verified, enabling the user to create a list of devices on the online device market platform.

Description

Technical Field

[0001] Various embodiments of the present disclosure relate generally to an online device marketplace platform for trading devices, and more particularly to systems and methods for securely enabling users to create listings of devices on an online device marketplace platform. Background Art

[0002] Traditionally, equipment such as aerospace parts are bought and sold in primary and secondary safety-critical markets. Such markets typically include manual lookups that often rely on intermediaries that require multiple conversations between the buyer and seller to assess the correctness of the information / attributes associated with the equipment before closing a deal to sell the equipment. Today, approximately $4 billion in aerospace parts are traded worldwide each year. However, less than 2% of aerospace parts trade is conducted through online marketplaces such as e-commerce websites. In the aerospace industry, it is difficult to establish online marketplace platforms for such equipment because of the lack of trust between buyers and sellers in online marketplaces.

[0003] Buyers may lack trust in sellers in an online device marketplace for a variety of reasons. First, buyers of devices may lack trust in the seller's identity on the online device marketplace. Second, buyers may lack trust in listings posted by sellers. For example, ghost listings may be a problem where a seller posts device information without actually owning the device / does not have the device in inventory. Third, buyers may also lack trust in the information / attributes of a posted listing that map to a physical device.

[0004] Likewise, sellers may lack trust in buyers in the device online marketplace for a variety of reasons. First, the seller of the device may lack trust in the buyer's identity in the device online marketplace. Second, the seller may lack trust in the way the buyer pays for the device.

[0005] In addition, equipment trade, such as aviation parts trade, can be conducted between several high-asset entities, such as airlines, airports, aircraft, and / or original equipment manufacturers (OEMs). For example, demanding, time-constrained services, such as gates and runways, can be traded. However, there is currently no integrated equipment online marketplace that integrates these resources between various participants (e.g., airlines, airports, aircraft, and OEMs).

[0006] The present disclosure is directed to overcoming one or more of the challenges described above. Summary of the invention

[0007] In one aspect, a computer-implemented method for securely enabling a user to create a list of devices on an online device market platform is disclosed. The method may include: receiving, by a server executing the online device market platform, a request from a user to create a list of devices on the online device market platform through a network; prompting, by the server, the user to upload one or more images or documents of the device through the online device market platform; receiving, by the server, one or more images or documents of the device from the user, the one or more images or documents containing information of the device; determining, by the server, whether to verify the identity of the device based on the information of the device in the one or more images or documents; and enabling, by the server, the user to create a list of devices on the online device market platform if the identity of the device is verified.

[0008] On the other hand, a system for securely enabling a user to create a list of devices on an online device market platform is disclosed. The system may include: a memory having processor-readable instructions therein; and at least one processor configured to access the memory and execute processor-readable instructions, which, when executed by the processor, configure the processor to perform multiple functions, including the following functions: receiving a request from a user to generate a list of devices on the online device market platform via a network by a server executing the online device market platform; prompting the user to upload one or more images or documents of the device via the online device market platform by the server; receiving one or more images or documents of the device from the user by the server, the one or more images or documents containing information of the device; determining by the server whether to verify the identity of the device based on the information of the device in the one or more images or documents; and enabling the user to create a list of devices on the online device market platform by the server if the identity of the device is verified.

[0009] In another aspect, a non-transitory computer-readable medium containing instructions for securely enabling a user to create a list of devices on an online device market platform is disclosed. The instructions may include instructions for the following operations: receiving a request from a user to create a list of devices on the online device market platform through a network by a server executing the online device market platform; prompting the user to upload one or more images or documents of the device through the online device market platform by the server; receiving one or more images or documents of the device from the user by the server, the one or more images or documents containing information of the device; determining by the server whether to verify the identity of the device based on the information of the device in the one or more images or documents; and enabling the user to create a list of devices on the online device market platform by the server if the identity of the device is verified.

[0010] Additional objects and advantages of the disclosed embodiments will be set forth in part in the following description, and in part will become apparent from the description, or may be learned by practicing the disclosed embodiments. The objects and advantages of the disclosed embodiments will be realized and obtained by means of the elements and combinations particularly pointed out in the appended claims.

[0011] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosed embodiments, as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary embodiments and, together with the description, serve to explain the principles of the disclosed embodiments.

[0013] Figure 1 A block diagram of a system for an online marketplace for devices in accordance with aspects of the present disclosure is depicted.

[0014] Figure 2 A block diagram depicting a blockchain-based online marketplace for devices.

[0015] Figure 3 Describes the use of Figure 2 Block diagram of a system for generating digital identities for devices on an online blockchain-based device marketplace.

[0016] Figure 4 Describes a method for securely enabling users to Figure 1 A flow chart of an exemplary embodiment of a process for creating a listing for a device in an online marketplace for a device.

[0017] Figure 5 Depicted are high-level functional block diagrams of exemplary computer devices or systems in which embodiments of the present disclosure, or portions thereof, may be implemented. DETAILED DESCRIPTION

[0018] The following embodiments describe systems and methods for automatically generating a list of equipment on an equipment online market platform. The following embodiments further describe systems and methods for verifying equipment identity information on an equipment online market platform. As used herein, "equipment" may include products or services traded between organizations in primary and secondary markets. Therefore, "equipment" may include, for example, aircraft, aviation parts and components, time-constrained equipment / services such as gates and runways, or any other aviation-related products or services traded between airlines, airports, aircraft or aviation OEMs. Although the exemplary equipment online market platform disclosed herein relates to aviation equipment, "equipment" may also include any type of vehicle (e.g., automobiles, ships, spacecraft, etc.), vehicle parts and components, vehicle services, heavy equipment, heavy equipment parts and components, heavy equipment services, computing devices, computing device parts and components, computing device services, or any other product or service traded between organizations in primary and secondary markets.

[0019] As described above, it is difficult to establish trust between buyers and sellers in an online market for equipment, such as an online market for aviation parts. The embodiments of the present disclosure provide solutions to these obstacles by providing a new workflow that is implemented using blockchain and other auxiliary technologies to help enhance trust in trade in an online market platform for equipment, such as trust in trade in safety-critical systems, such as aviation parts. The online market platform for equipment of the present disclosure is distinguished by establishing trust. For example, the embodiments of the present disclosure may enable buyers to trust a trusted list of sellers. The trusted list may be collaboratively established using smart contracts and auxiliary technologies.

[0020] Embodiments of the present disclosure also use a set of step-by-step methods that make the operation transparent and can automate the above process while coordinating transactions on the device online market platform. Embodiments of the present disclosure may also include an initial trusted identity represented by an organization node. The task of establishing a trusted list is simplified by a set of steps as described below.

[0021] The subject matter of the present disclosure will now be described more fully below with reference to the accompanying drawings, which form a part of the present disclosure and show specific exemplary embodiments by way of example. An embodiment or specific implementation described herein as "exemplary" should not be interpreted as, for example, being more preferred or advantageous than other embodiments or specific implementations. On the contrary, it is intended to reflect or indicate that the one or more embodiments are one or more "example" embodiments. The subject matter can be embodied in a variety of different forms, so the subject matter covered or claimed is intended to be interpreted as not being limited to any exemplary embodiment set forth herein; the exemplary embodiments are provided only for illustration. Similarly, the subject matter intended to be claimed or covered has a suitably broad scope. Among other things, for example, the subject matter may be embodied as a method, device, component or system. Therefore, the implementation may, for example, take the form of hardware, software, firmware, or any combination thereof (except the software itself). Therefore, the following specific embodiments are not intended to be considered as having a limiting meaning.

[0022] Throughout the specification and claims, in addition to the meanings explicitly stated, terms may have slightly different meanings suggested or implied by the context. Likewise, the phrase "in one embodiment" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment" as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include, in whole or in part, a combination of the exemplary embodiments.

[0023] The terms used below are to be interpreted in their broadest reasonable manner, even when used in conjunction with the detailed description of certain specific examples of the present disclosure. Indeed, certain terms may even be emphasized below; however, any term intended to be interpreted in any limited manner will be explicitly and specifically defined in this detailed description. Both the foregoing general description and the following detailed description are exemplary and illustrative only and are not intended to limit the features protected by the claims.

[0024] Now referring to the accompanying drawings, Figure 1 1 depicts a block diagram of a system 100 for an online market for devices according to aspects of the present disclosure. Figure 1 As shown, a system 100 for an online market for equipment may include an online market platform 102 for equipment, such as an online market platform for aviation parts, which includes a server system 104 and a shared database 106. The server system 104 may store and execute the online market platform 102 for use over a network 108, such as the Internet. The online market platform 102 for equipment may be implemented by one or more server systems 104, such as an application program interface (API) server, a web server, an image server, a list server, a processing server, a search server, or any other type of front-end server or back-end server.

[0025] The user can access the appliance online market platform 102 through the network 108 via a user device 110. The user device 110 enables the user to display a web browser for accessing the appliance online market platform 102 from the server system 104 through the network 108. The user device 110 can be any type of device for accessing web pages, such as a personal computing device, a mobile computing device, etc. The user device 110 can be a seller device 112 or a buyer device 114. Therefore, the user can be a seller and / or a buyer who trades through the appliance online market platform 102. As shown in Figure 1 As further shown in FIG. 1 , the user device 110 can be both a seller device 112 and a buyer device 114. Therefore, the user can access the device online market platform 102 as both a seller and a buyer.

[0026] In addition, the device online market platform 102 may provide a seller interface and a buyer interface. The seller interface may be displayed to a user who accesses the device online market platform 102 as a seller on the user device 110. The seller interface may include features that enable the seller to enter information about devices that the seller wishes to sell through the device online market platform 102. For example, the seller interface may enable the seller to create, edit, or delete a device list based on the information of the corresponding device. The buyer interface may be displayed to a user who accesses the device online market as a buyer on the user device 110. The buyer interface may include features that enable the buyer to search, select, and purchase devices from a device list created by a seller.

[0027] As discussed above, the device online market platform for conducting device trade can provide features for establishing trust between users of the device online market platform. For example, the tasks of device registration, device provenance tracking, ownership change authentication, and listing authentication can include a shared database 106 such as a blockchain shared ledger.

[0028] Figure 2 A block diagram of a blockchain-based device online marketplace 200 is depicted. Figure 2 As shown, the blockchain-based device online market 200 may include an organization node 202 connected to a device online market network 204. The organization node 202 may include an organization that sells and / or purchases equipment such as aviation parts. For example, the organization node 202 may include an OEM 202a, an airport (AX) 202b, an airline 202c, or other sellers and / or buyers 202n of aviation parts or any other equipment, such as maintenance, repair and operation (MRO) suppliers. The organization node 202 may also include an organization that maintains and implements the device online market platform 102 implemented on the server system 104.

[0029] In the blockchain-enabled device online marketplace 200, the organization node 202 can act as a node in a blockchain network such as network 204. Thus, the nodes can be distributed in a widely distributed network and can perform a variety of tasks. As described above, the node can include a user device 110 connected to the network 108. The node can support the online marketplace network 204 by maintaining a copy of the blockchain shared ledger 106. As further described below, the organization node 202 can contribute to the task of verifying the digital identity of the devices in the list.

[0030] The device online market network 204 may include tasks and / or other services provided by the device online market 200. The organization node 202 may perform multiple tasks of the device online market 200 of the present disclosure. For example, the device online market network 204 may include tasks of device registration 205, device source tracking 206, ownership change authentication 207, and listing authentication 208, where the organization node 202 contributes to these tasks, as described in detail below.

[0031] The first task of device registration 205 may include a device registration method. The device registration method may enable a user 210 authorized by an organization to upload information about a device. For example, the current owner 210a (e.g., a seller) of a device may upload information about a physical device via the device online market platform 102. Therefore, the properties of a physical device may be used to represent the physical device in the digital world on the device online market platform 102. A unique identity is created for the device, and the unique identity is stored as a blockchain entry for the device in a shared ledger 106, from which the unique identity of the device may be referenced for future use, as further described below. The device registration method may include verifying the authenticity of device ownership so that the identity of the device and records attached to the device may be trusted by other users 210. For example, the unique identity of an aviation part may include a part number, a serial number, an image of the part, an FAA form 8130-3 of the part, and other information about the part or device.

[0032] The second task of device source tracking 206 may include a traceable device source method. The traceable device source method may enable other users 210b (e.g., shippers, maintenance technicians, etc.) who currently own the device to upload information about any actions performed on the device. For example, the traceable device source method may include storing all actions (such as maintenance functions) performed by multiple organizations on the device as blockchain entries for the device in the shared ledger 106, as further described below. The maintenance functions performed on the device may be verified by a smart contract. As used herein, a "smart contract" is a computer code stored in a blockchain shared ledger that contains a set of predefined rules according to which the parties to the contract agree to interact with each other. When the predefined rules are met, the contract or agreement may be automatically implemented. For example, a smart contract for a device may include a clause (or rule) for performing maintenance on the device before a set date. The server 104 may receive information related to the maintenance functions performed on the device, and the smart contract may verify the information and determine that the maintenance occurred before the set date. Therefore, the server 104 may verify the maintenance function through a smart contract.

[0033] In one embodiment, the history of maintenance functions performed on the equipment stored in the shared ledger can be queried or accessed by the user 210 through the equipment online market platform 102 to track the history of the equipment. Equipment provenance tracking for aviation parts can include, for example, information such as: part number, serial number, image of the part, FAA form 8130-3 for the part, the current owner of the part, maintenance steps performed on the part, or any other information relevant to tracking the history of a part or equipment.

[0034] In one embodiment, actions or events on a device may originate from multiple organizations 202a-202n, including users 210 of the device online marketplace network 204 from a historical or real-time record. For example, a shipper may be authorized by the network 204 to submit a shipment event transaction and information to the network 204. The transaction and / or information may be recognized by other organizations 202a-202n, and the shipment status and information may be recorded in the shared ledger 106 as a blockchain entry for the device.

[0035] The third task of the ownership change authentication method 207 may include recording and using a smart contract to authenticate a reference to the device ownership change in a consensus manner. The current owner 210c of the device may upload information about the device ownership change. For example, the device ownership may be stored as a blockchain entry for the device in the shared ledger 106. In one embodiment, when the sale is recorded on the device online market platform 102, the ownership change authentication method 207 may include submitting a sales transaction between the user 210 (seller and buyer) to the network 204. The transaction may be approved, and the new ownership information (e.g., the buyer becomes the new owner of the device) may be recorded in the blockchain entry for the device in the shared ledger 106.

[0036] The fourth task of list authentication 208 can include verifying that the seller owns the physical device before enabling the seller to create a listing on the device online market platform 102. For example, a seller 210d can create a listing to publish a device for sale on the device online market platform 102. A list of aviation parts may include, for example, a part number, a part serial number, an image of the part, an FAA form 8130-3 for the part, current owner information, or any other information about the part or device. The listing can be verified by an automatic list authentication method, as further described below. The automatic list authentication method can reduce shadow listings. Therefore, the automatic list authentication method can include a smart contract supported by a verification process. The smart contract can be supported by a verification process implemented by the device registration method 205 and the verification process.

[0037] Figure 3 A block diagram of a system 300 for securely enabling a user 210 to create a listing of a device on a blockchain-based device online marketplace platform 102 is depicted. Figure 3 As shown, the system 300 may include a blockchain shared ledger, such as an immutable distributed device registry 302. The task of listing certification 208 may utilize the tasks of device registration 205, device provenance tracking 206, and ownership change certification 207 to ensure that a secure listing is generated on the device online market platform 102. For example, to register a device on the device online market platform 102 (e.g., initially generate a digital identity for the device), a user 210 may upload one or more images 306 and / or documents 308 containing information about the device to the server 104 via the network 108. The user 210 may be the current owner 210a (e.g., a seller) of the device or another user 210b (e.g., a shipper or maintenance technician) who currently owns the device.

[0038] In one embodiment, one or more images 306 and / or documents 308 may include a recently certified release form. For example, for an aviation part, the server may receive a recently certified release form, such as FAA form 8130. The certified release form may be certified by a government entity such as the Federal Aviation Administration (FAA) and may authorize the device to be used on, for example, a vehicle. For example, for a vehicle part or an aviation part, the certified release form may contain information about the part, such as a description, part number, serial number, status of the part, manufacturing information, safety status information, and other information about the part that may be certified by a government entity. The server may also receive an image 306 of a device from a user 210. For example, for a vehicle part or an aviation part, the image 306 may be a panel and the panel may contain information about the part, such as a part number, serial number, manufacturer, or other relevant information about the part.

[0039] The one or more images 306 and / or documents 308 may be digitally signed by the user 210 with the user's identification number (e.g., DUN number and / or organization name). The server 104 may include a device image server 310 for receiving and processing the one or more images 306. The server 104 may also include a document server 312 for receiving and processing the one or more documents 308. Thus, the server 104 may receive, process, and store the one or more images 306 and / or documents 308 containing information of the device to generate a blockchain entry for the device on the shared ledger 302.

[0040] The server 104 can parse one or more images 306 and / or documents 308 and extract attribute information 314 of the device from each image 306 and / or document 308. The attribute information 314 can be stored in the blockchain entry of the device on the shared ledger 302. The attribute information 314 for identifying the device may include an origin record 314a, which includes a device number (e.g., part number), a serial number, a manufacturer, a manufacturing location, and a manufacturing date. The attribute information 314 may also include an attribute record 314b, which includes one or more images 306 and / or documents 308 uploaded. In one embodiment, the origin record 314a and the attribute record 314b may be the minimum device information required for identifying the device and for registering the device on the device online market platform 102. The server can create and assign a unique device identification number corresponding to the device information received for the corresponding device. Therefore, each unique device registered on the device online market platform 102 can include a unique device identification number for identifying the device.

[0041] Each device may also include optional device information 316, which may be stored in the blockchain entry of the device (via device source tracking 206 and ownership change authentication 207) for further identification and tracking of the device. For example, another user 210b (e.g., a shipper or maintenance technician) who currently owns the device may upload additional information of the device to the blockchain entry of the device in the shared ledger 302, as further described below. Optional device information 316 may include, for example, ownership records 316a, shipping records 316b, service records 316c, and records 316d on the vehicle. Ownership records 316a may include the ownership date and current owner of the device. Shipping records 316b may include the device migration date and current device location. Service records 316c may include, for example, service date, sub-device identification number, service center, service type, repair / audit / inspection / c-inspection / oil change, etc., and service life. For vehicle parts or aviation parts, the record 316d on the vehicle may include the vehicle update date, vehicle identification information (eg, aircraft tail number and serial number), and the date the part was installed and / or the date the part was removed from the vehicle.

[0042] When the information of the device is modified and / or updated and the new information is processed by the traceable device source method or the ownership change authentication method detailed above, the optional device information 316 can be updated in the blockchain entry. Therefore, the optional device information 316 can be used to track the history of the device. For example, when the device is shipped, another user 210b who currently owns the device can upload one or more images 306 and / or documents 308 of the shipping information to the shipping record 316b to provide updated information of the shipping record 316b. In one embodiment, another user 210b can also manually enter the shipping information on the device online market platform 102. The updated information can be stored in the blockchain entry of the corresponding device in the shared ledger 302. Another user 210 (e.g., a buyer) of the device online market platform 102 can then query and / or view the shipping information to view the history of the corresponding device.

[0043] In one embodiment, a user 210, such as a seller 210d of a device, may want to create a sales listing for the device on the device online marketplace platform 102. The seller 210d may include the current owner 210a of the device. In one embodiment, the seller 210d may be different from the user 210 who generated the initial digital identity of the device in the process detailed above. For example, the seller 210d may be a previous buyer who purchased the device through the device online marketplace platform 102. Therefore, after the digital identity has been generated as a blockchain entry for the device in the shared ledger 302, the seller 210 may be the current owner of the device.

[0044] The listing authentication task 208 of the device online market network 204 can securely enable the user 210 to create a listing of the device on the device online market platform 102 while ensuring that the user 210 owns the physical device. For example, in order to create a listing of the device, the user 210 may be required to upload one or more images 306 and / or documents 308 containing information of the device to the server 104 through the device online market platform 102. The server 104 can verify the identity of the device based on the information of the device in the one or more images 306 or documents 308 uploaded by the user 210, as described in further detail below. If the identity of the device is verified, the server 104 can enable the user 210 to create a listing of the device on the device online market 102.

[0045] Figure 4 A flow chart of a method 400 for securely enabling a user 210 to create a listing of a device on a device online marketplace platform 102 is depicted. In an initial step 405, the server 104 may receive a request from a user 210 over a network 108 to create a listing of a device on a device online marketplace platform 102.

[0046] In step 410 , the server 104 may prompt the user 210 via the device online marketplace platform 102 to upload one or more images 306 or documents 308 of the device through the device online marketplace platform 102 .

[0047] In step 415, the server 104 may receive one or more images 306 or documents 308 of a device from the user 210, the one or more images 306 or documents 308 containing information of the device. For example, the information of the device may include a device number (e.g., a part number), a serial number, geographic location information, and / or identity information of the user 210 who uploaded the one or more images 306 or documents 308. In one embodiment, the server 104 may receive the one or more images 306 or documents 308 of the device from the user 210 via a mobile application.

[0048] In one embodiment, the server 104 may parse the received one or more images 306 or documents 308 of the device and extract information identifying the device from the received one or more images 306 or documents 308. For example, the server 104 may use character recognition codes such as optical character recognition (OCR) to extract the information of the device from the received one or more images 306 or documents 308. In one embodiment, the information identifying the device may be included in a metadata file associated with the received one or more images 306 or documents 308.

[0049] In step 420, the server 104 may determine whether to verify the identity of the device based on the information of the device in the one or more images 306 or documents 308. In one embodiment, to determine whether the identity of the device is verified, the server 104 may broadcast a message to other users 210 of the device online market platform 102 to approve the identity of the device. The server 104 may then receive approval of the identity of the device from the other users 210 through the device online market platform 102. If the identity of the device is approved by a threshold number of other users 210, the server 104 may determine that the identity of the device is verified. In one embodiment, the threshold number may include at least 51% of the other users 210.

[0050] In one embodiment, before the user 210 initiates the process of creating a listing on the device online market platform 102, the identity of the device may be stored in the blockchain entry of the device in the shared ledger 302 (according to the system 300 detailed above). Therefore, the server 104 can access the shared ledger 302 to determine whether the identity of the device is verified. The server 104 can compare the information of the device from the one or more images 306 or documents 308 with the information of the device in the blockchain entry of the device stored in the shared ledger 302. For example, the server 104 can compare the identity information of the user 210 with the current ownership information of the device in the blockchain entry. If the information of the device from the one or more images 306 or documents 308 matches the information of the device stored in the blockchain entry of the device, the server 104 can determine that the identity of the device is verified. For example, if the identity information of the user 210 matches the current ownership information stored in the blockchain entry, the server 104 can determine that the user 210 owns the device and can verify the identity of the device.

[0051] In one embodiment, the identity of the device may not be stored in a blockchain entry in the shared ledger 302 before the user 210 initiates the process of creating a listing on the device online market platform 102. If there is no identity information stored in the shared ledger 302, the server 104 may determine that the identity of the device is verified if the identity information of the user 210 matches the identity information of a founding member of the device online market network 204. For example, the device online market network 204 may include a user 210 belonging to an organization 202 that is a founding member of the device online market network 204. The founding member may be a selected organization 202 invited to the device online market network 204 by the organization that maintains and implements the device online market platform 102. For example, a founding member may be a user 210 that has initial access to the device online market platform 102 before other users join the network 204. Therefore, the founding member role may be associated with the identity information of the user 210 who is a founding member of the device online market network 204.

[0052] In step 425 , if the identity of the device is not verified (step 420 : No), the server 104 may deny the user 210 from creating a listing for the device on the device online marketplace platform 102 .

[0053] In step 430, if the identity of the device is verified, the server 104 may enable the user 210 to create a listing of the device on the device online marketplace platform 102. In one embodiment, the server 104 may require the user 210 to include one or more images 306 or documents 308 uploaded to the device online marketplace platform 102 in the listing of the device. The server 104 may also require the user 210 to include price information for the device in the listing of the device.

[0054] In one embodiment, user 210 may need to have a specific role on the device online market platform 102 in order to be able to create a list of devices. For example, server 104 may receive identity information (e.g., email address) of user 210 through device online market platform 102. Identity information of user 210 may include the role of user 210 associated with the email address. The role of user 210 may include, for example, seller, buyer, consignor, supplier, etc. If the role of user 210 matches a predetermined role for determining whether user 210 is authorized to create a list on device online market platform 102, server 104 may enable user 210 to create a list of devices on device online market platform 102. For example, the predetermined role may include a seller role. Therefore, if the identity information of user 210 includes a seller role, server 104 may enable user 210 to create a list of devices on device online market platform 102.

[0055] Thus, the server 104 may securely enable the user 210 to create a listing of a device on the device online marketplace platform 102 .

[0056] Figure 5 A high-level functional block diagram of an exemplary computer device or system is shown, in which embodiments of the present disclosure or portions thereof may be implemented, for example, as computer-readable code. Figures 1 to 4 Each of the exemplary systems, user interfaces, and methods described may be implemented in the apparatus 500 using hardware, software, firmware, a tangible computer-readable medium having instructions stored thereon, or a combination thereof, and may be implemented in one or more computer systems or other processing systems. Hardware, software, or any combination thereof may implement the above with respect to Figures 1 to 4 Each of the exemplary systems, user interfaces, and methods described.

[0057] If programmable logic is used, such logic can be executed on a commercially available processing platform or a dedicated device. Those skilled in the art will appreciate that embodiments of the disclosed subject matter can be implemented using a variety of computer system configurations, including multi-core multi-processor systems, minicomputers, mainframe computers, computers linked or clustered together with distributed functionality, and ubiquitous or microcomputers that can be embedded in almost any device.

[0058] For example, at least one processor device and memory may be used to implement the above embodiments. The processor device may be a single processor, multiple processors, or a combination thereof. The processor device may have one or more processor "cores".

[0059] As mentioned above Figures 1 to 4 The various embodiments of the present disclosure described in the examples of can be implemented using device 500. After reading this specification, it will become apparent to those skilled in the relevant art how to implement the embodiments of the present disclosure using other computer systems and / or computer architectures. Although operations can be described as sequential processes, some operations can actually be performed in parallel, concurrently, and / or in a distributed environment, and where program code is stored locally and / or remotely for access by single-processor or multi-processor machines. In addition, in some embodiments, the order of operations can be rearranged without departing from the essence of the disclosed subject matter.

[0060] like Figure 5 As shown, the device 500 may include a central processing unit (CPU) 520. The CPU 520 may be any type of processor device, including, for example, any type of dedicated or general purpose microprocessor device. It should be understood by those skilled in the relevant art that the CPU 520 may also be a single processor in a multi-core / multi-processor system (such a system operates alone) or in a cluster of computing devices operating in a cluster or server farm. The CPU 520 may be connected to a data communication infrastructure 510, such as a bus, a message queue, a network, or a multi-core message passing scheme.

[0061] The device 500 may also include a main memory 540, such as a random access memory (RAM), and may also include an auxiliary memory 530. The auxiliary memory 530, such as a read-only memory (ROM), may be, for example, a hard disk drive or a removable storage drive. Such removable storage drives may include, for example, a floppy disk drive, a tape drive, an optical disk drive, a flash memory, etc. The removable storage drive reads from and / or writes to the removable storage unit in a well-known manner in this example. The removable storage unit may include a floppy disk, a tape, an optical disk, etc. that is read by and written to the removable storage drive. It should be understood by those skilled in the relevant art that such a removable storage unit generally includes a computer-usable storage medium having computer software and / or data stored therein.

[0062] In alternative implementations, secondary memory 530 may include other similar components that enable computer programs or other instructions to be loaded into device 500. Examples of such components may include program cartridges and cartridge interfaces (such as found in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, and other removable storage units and interfaces that enable software and data to be transferred from the removable storage unit to device 500.

[0063] The device 500 may also include a communication interface ("COM") 560. The communication interface 560 allows software and data to be transferred between the device 500 and external devices. The communication interface 560 may include a modem, a network interface (such as an Ethernet card), a communication port, a PCMCIA slot and card, etc. The software and data transferred via the communication interface 560 may be in the form of signals, which may be electronic, electromagnetic, optical or other signals capable of being received by the communication interface 560. These signals may be provided to the communication interface 560 via a communication path of the device 500, which may be implemented using, for example, wires or cables, optical fibers, a telephone line, a cellular phone link, an RF link, or other communication channels.

[0064] The hardware elements, operating systems, and programming languages ​​of such devices are conventional in nature, and it is therefore assumed that those skilled in the art are sufficiently familiar with this. The device 500 may also include input and output ports 550 to connect to input and output devices (such as keyboards, mice, touch screens, monitors, displays, etc.). Of course, various server functions can be implemented in a distributed manner on multiple similar platforms to distribute the processing load. Alternatively, these servers can be implemented by appropriate programming of a computer hardware platform.

[0065] The systems, devices, apparatuses and methods disclosed herein are described in detail by way of example with reference to the accompanying drawings. The examples discussed herein are merely examples, and the purpose of providing is to help explain the devices, devices, systems and methods described herein. Any features or components shown in the accompanying drawings or discussed below should not be considered as mandatory for any specific implementation of any of these devices, devices, systems or methods, unless explicitly stated as mandatory. For ease of reading and clarity, certain components, modules or methods may be described only in conjunction with specific drawings. In the present disclosure, any indication of specific techniques, arrangements, etc. is either related to the specific examples proposed, or is merely a general description of such techniques, arrangements, etc. The indication of specific details or examples is not intended to be or should not be interpreted as mandatory or restrictive, unless explicitly stated as such. Any situation in which a combination or sub-combination of components is not explicitly described should not be understood as an indication that any combination or sub-combination is impossible. It should be understood that the disclosed and described examples, arrangements, configurations, components, elements, equipment, devices, systems, methods, etc. may be modified, and this may be required for specific applications. In addition, for any method described, whether or not the method is described in conjunction with a flowchart, it should be understood that, unless otherwise indicated or required by the context, any explicit or implied ordering of the steps performed during the method execution does not mean that these steps must be performed in the order presented, but may be performed in a different order or in parallel.

[0066] Throughout this disclosure, the components or modules mentioned generally refer to objects that can be logically combined to perform a function or a group of related functions. Similar reference numerals are generally intended to refer to the same or similar components. Components and modules can be implemented in software, hardware, or a combination of software and hardware. The term "software" is used broadly to include not only executable code such as machine executable or machine interpretable instructions, but also data structures, data storage, and computing instructions stored in any suitable electronic format (including firmware and embedded software). The terms "information" and "data" are widely used and include a variety of electronic information, including executable code; content such as text, video data, and audio data; and various codes or marks. The terms "information", "data", and "content" are sometimes used interchangeably when the context allows.

[0067] It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A computer-implemented method for securely enabling a user to create a listing of a device on an online marketplace platform for devices, the method comprising: A server executing the device online market platform receives a request from a user to create a list of the device on the device online market platform through a network; Prompting the user to upload one or more images or documents of the device through the device online market platform by the server; receiving, by the server, the one or more images or documents from the device of the user, the one or more images or documents containing information of the device; determining, by the server, whether to verify the identity of the device based on the information of the device in the one or more images or documents; as well as If the identity of the device is verified, the user is enabled by the server to create a listing of the device on the device online marketplace platform.

2. The method of claim 1, wherein the receiving, by the server, the one or more images or documents from the device of the user comprises receiving, by the server, the one or more images or documents of the device via a mobile application.

3. The method of claim 1, wherein the determining, by the server, whether to verify the identity of the device based on the information of the device in the one or more images or documents comprises: Broadcasting a message by the server to other users of the device online market platform to confirm the identity of the device; receiving, by the server through the device online market platform, an approval of the identity of the device from the other user; as well as The server determines that the identity of the device is verified if the identity of the device is recognized by a threshold number of other users.

Images