CN110768839B - Third-party software authorization system based on intelligent equipment monitoring and user identity binding - Google Patents

Third-party software authorization system based on intelligent equipment monitoring and user identity binding Download PDF

Info

Publication number
CN110768839B
CN110768839B CN201911042019.1A CN201911042019A CN110768839B CN 110768839 B CN110768839 B CN 110768839B CN 201911042019 A CN201911042019 A CN 201911042019A CN 110768839 B CN110768839 B CN 110768839B
Authority
CN
China
Prior art keywords
party software
client
user
cloud server
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201911042019.1A
Other languages
Chinese (zh)
Other versions
CN110768839A (en
Inventor
李晓宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nanning Zhisou Information Technology Co ltd
Original Assignee
Nanning Zhisou Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nanning Zhisou Information Technology Co ltd filed Critical Nanning Zhisou Information Technology Co ltd
Priority to CN201911042019.1A priority Critical patent/CN110768839B/en
Publication of CN110768839A publication Critical patent/CN110768839A/en
Application granted granted Critical
Publication of CN110768839B publication Critical patent/CN110768839B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0246Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0273Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
    • H04L41/0293Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP] for accessing web services by means of a binding identification of the management service or element
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/40Security arrangements using identity modules
    • H04W12/48Security arrangements using identity modules using secure binding, e.g. securely binding identity modules to devices, services or applications

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention provides a third-party software authorization system based on intelligent device monitoring and user identity binding. The system comprises a cloud server and clients, wherein the clients comprise a user client, a maintenance client, a production client and a third-party software testing client. The invention relates to an integrated system of user identity identification, binding of hardware characteristics of intelligent equipment and user identity identification and third-party software authorization, which can track hardware characteristics of the intelligent equipment, each stage of the full life cycle of the intelligent hardware, ownership of the intelligent equipment by a user, login and inquiry states of the user on a cloud server through the equipment, use of third-party software and the like.

Description

Third-party software authorization system based on intelligent device monitoring and user identity binding
Technical Field
The invention relates to the technical field of cloud computing, in particular to a third-party software authorization system based on intelligent device monitoring and user identity binding.
Background
In the prior art, whether the intelligent device is an original factory certified product or not is verified based on a single or combined mode of an electronic certificate, an intelligent device hardware characteristic, a serial number, a user identity characteristic and the like, only after the intelligent device arrives at the user, the user provides the currently purchased intelligent device serial number, and submits and verifies the intelligent device serial number to a system provided by a producer, and the inquiry result taken by the user is only to verify the original factory certified product of the serial number of the intelligent device, but not to simultaneously verify whether the serial number and the hardware characteristic code of the corresponding intelligent device are the original factory certified product or not, and further, whether the information changes or not and whether the information is the original factory certified product or not can not be monitored through the whole life cycle of the intelligent device. Therefore, the technical list is too simple and static in terms of the authentication mode of the certified products of the intelligent equipment, the certified products are verified only by the equipment serial number under most conditions, the hardware feature codes of the related intelligent equipment corresponding to the serial number are not extracted in real time and are transmitted to the cloud server to serve as the basis of the certified products verification, then the hardware feature code extracting client is installed in the intelligent equipment in the hand of the user, and the current hardware feature codes are transmitted to the cloud server to be compared with the certified product data of the cloud server for identification. The current scheme is easy to cause the problems that the serial number is genuine, and the intelligent hardware feature code is not produced by the original factory; moreover, the system can not completely cover all links of production, inventory, sale and maintenance of the intelligent equipment, and has a lot of loopholes, so that the loopholes need to be solved in a more timely and dynamic mode.
In addition, many single-machine edition legal software installed in the intelligent equipment at present are easy to crack due to the fact that the software is not supported by the cloud.
Disclosure of Invention
The invention provides a third-party software authorization system for monitoring query and user identity recognition of the full life cycle of intelligent equipment based on cloud computing, which aims to solve the problems in the links, provide a new solution for certified inspection of the intelligent equipment, and establish a set of real-time binding of the hardware feature code of the intelligent equipment and a user account on the solution so as to bind and monitor the real-time certified state of the exclusive intelligent equipment hardware for a user.
The system comprises a cloud server and clients, wherein the clients comprise a user client, a maintenance client, a production client and a third-party software testing client; the third-party software test client side realizes the whole-course authorization on the access, verification, starting, continuous use and closing states of the third-party software through a software interface authorization mode, a memory authorization mode, a file authorization mode or a dynamic link library interface authorization mode;
the cloud server is configured to: generating a serial number of the intelligent equipment, binding and storing the hardware feature code uploaded by the client and the serial number, and realizing the management of the full life cycle of the intelligent equipment hardware based on the serial number; carrying out account registration and client authority configuration on related personnel; judging and storing the related data uploaded by the client and the information of the third-party software; the system is provided with a factory management system, a sales management system, a logistics management system, a user access system and a product repair system, and the management of production, sales, purchase and maintenance links in the whole life cycle is respectively realized; the intelligent device is also provided with a third-party software information record management system for realizing the management of third-party software running on the intelligent device;
the plant management system is configured to: interacting with the production client, receiving the hardware feature codes and serial numbers of the intelligent equipment uploaded by the production client, binding and storing the serial numbers and the corresponding hardware feature codes, and providing an equipment inquiry function based on the serial numbers for the sales management system;
the sales management system is configured to: when the intelligent equipment sales state corresponding to the serial number is changed into sales, the serial number and the hardware feature code of the intelligent equipment are marked for sales in the database and a sales order number is generated and shared to the logistics management system;
the logistics management system is configured to: a logistics worker logs in the system and selects a shared sales order number or a repair order shared by the product repair system, so that the shipment logistics tracking and the user signing management of the intelligent equipment in two states of sales and repair are realized;
the user access system is configured to: interacting with the user client, and inquiring whether the intelligent equipment is an original product or not by the user of the intelligent equipment through the user client and submitting repair data during repair; storing personal information of a user name and a password, binding the information with each serial number, hardware feature codes of the intelligent equipment corresponding to the serial numbers and maintenance information, and providing whole-process supervision of starting, continuous use and closing states for third-party software;
the product rework system is configured to: interacting with a maintenance client, and confirming whether the maintenance work of the intelligent equipment is finished by a maintainer; receiving the hardware feature code and the serial number extracted by the maintenance client, judging whether the serial number is correct, if so, binding and storing the updated hardware feature code of the intelligent equipment and the serial number, and updating the hardware feature code of the intelligent equipment in the user access system database to be consistent with the hardware feature code after maintenance; sharing the repair order number to a logistics management system;
the third party software information docketing management system is configured to: storing and managing third-party software related information, judging the third-party software information uploaded by the user client, and monitoring the running state of the third-party software;
the service client is configured to: the system is used for a maintainer to log in the product repair system, automatically scan various hardware feature codes of the intelligent equipment after the maintenance is finished after logging in, and upload corresponding serial numbers to the maintenance management system;
the user client is configured to: the system is used for autonomously registering an account number and newly purchasing equipment by a user, inquiring whether the intelligent equipment is original factory certified products or not, and providing butt joint and interaction service of third-party software and a cloud server;
the third party software testing client is configured to: the system is used for testing third-party software, simulating a use scene of a user client and checking whether pop-up information of the third-party software meets an agreed design specification;
the third-party software testing client interacts with the cloud server to realize the starting authorization interaction operation of the third-party software, and the method comprises the following steps:
the method comprises the following steps: the user starts the third-party software, and the third-party software feeds back the third-party software record information of the third-party software through the third-party software testing client interface;
step two: after receiving the third-party software filing information, the third-party software testing client uploads the information to a third-party software information filing management system;
step three: the third-party software information filing management system judges whether the third-party software filing information is consistent with that stored in the cloud server or not, if not, an error result is returned to the third-party software testing client, the third-party software testing client sends out a parameter for refusing the start of the third-party software through an authorization interface, the third-party software is refused to start, a prompt box for preventing the third-party software from starting is popped up, and the third-party software cannot be started and does not perform subsequent steps; if the two are consistent, the next step is carried out;
step four: the correct result is returned to the third-party software testing client, the third-party software testing client sends out parameters allowing the third-party software to be started, the version number and the software name information of the third-party software are displayed in a third-party software browser of the third-party software testing client, and a continuous use monitoring interface of the third-party software is initialized;
step five: and the third-party software testing client and the third-party software start a continuous use monitoring interface at the same time, and a user access system monitors whether a user account and an intelligent equipment hardware information feature code sent to the third-party software testing client by the third-party software testing client are in an appointed time stamp period according to a protocol so as to confirm the online state of the third-party software testing client, feeds a judgment result back to the third-party software testing client in the appointed period, and feeds the online state back to the third-party software by the third-party software testing client.
Further, the cloud server further comprises a verification code generation and verification system, which is used for generating and sending an email or a mobile phone verification code when a user registers, and verifying the verification code after the user client uploads the verification code.
Further, in the production link, the interaction process between the production client and the cloud server is as follows:
the method comprises the following steps: the cloud server carries out account opening operation and authority distribution on a storage administrator in advance, and the storage administrator applies for a serial number to the cloud server;
step two: the cloud server responds to the application and sends the serial numbers with corresponding quantity to the storage administrator in the cloud;
step three: a stock manager logs in a factory management system through a production client, and the production client extracts a hardware feature code of the intelligent equipment;
step four: the method comprises the steps that a storage administrator uploads a serial number and a hardware feature code of the intelligent device to a factory management system, and a cloud server binds and stores the hardware feature code and the corresponding serial number.
Further, in the sales link, the workflow of the sales management system is as follows:
the method comprises the following steps: the cloud server carries out account opening operation and authority distribution on a salesman in advance, and the factory management system shares the serial number of the intelligent equipment which can be sold in the stock;
step two: a salesman logs in a sales management system to carry out sales operation, and marks a sales state corresponding to the serial number of the sold intelligent equipment as sold; the sales management system generates a corresponding sales order number according to the serial number and the hardware feature code;
step three: and the sales management system shares the sales order number in the step two to the logistics management system.
Further, when the user registers, the interactive workflow of the user client and the cloud server is as follows:
the method comprises the following steps: a user fills registration information in a registration interface of a user client;
step two: a user sends a verification code request to a cloud server, and a user client scans and records a hardware feature code of the intelligent device and sends the hardware feature code and registration information to the cloud server;
step three: the cloud server verifies the hardware feature codes, if the hardware feature codes can be matched with the hardware feature codes stored in the cloud server, the fourth step is carried out, otherwise, the verification codes are refused to be sent, and the subsequent steps are not carried out;
step four: the verification code generating and verifying system generates a verification code and sends the verification code to a user;
step five: the user fills the verification code in a registration interface and clicks registration;
step six: the user client scans and records the hardware feature code of the intelligent device again, and sends the hardware feature code and the registration information to the cloud server;
step seven: the cloud server verifies the hardware feature codes, if the hardware feature codes can be matched with the hardware feature codes stored in the cloud server, the step eight is carried out, and if not, registration is refused;
step eight: and the verification code generation and verification system carries out verification of the verification code, if the verification is successful, the registration is successful, otherwise, the registration is refused.
Furthermore, the third-party software testing client interacts with the user access system to realize the starting of the third-party software authorization interface, which comprises the following steps,
the method comprises the following steps: a third-party software test client logs in a cloud server;
step two: the third-party software testing client and the user access system establish communication through respective real-time online monitoring interfaces;
step three: the third-party software testing client periodically sends a user account and an intelligent equipment hardware information feature code to the user access system so that the cloud user access system can periodically confirm the identity and real-time online state of the user and the intelligent equipment;
step four: the user access system judges whether the relevant data is received within the appointed time, if so, the user access system sends on-line confirmation information to the third-party software testing client, and after the third-party software testing client receives the information, the third-party software authorization interface is started, and normal authorization data interaction work is started; otherwise, the monitoring interface is closed, and the third-party software testing client needs to log in the cloud again.
Further, the method for periodically monitoring the third-party software by the third-party software testing client comprises the following steps: the third-party software testing client actively pushes the connection state parameters through the monitoring interface, and the third-party software judges the on-off state of the third-party software testing client when receiving or not receiving the relevant state parameters in a specified period; or the third-party software requests the current-stage connection state parameters from the third-party software testing client through the interface, and the third-party software testing client replies according to the current state.
Furthermore, the user access system is provided with a web page, and the web page is provided with a function key for the user to prohibit starting and closing operations on the third-party software.
The beneficial effects of the invention are as follows:
according to the invention, hardware characteristics, serial numbers, market circulation states and user identities of intelligent equipment are organically bound through a cloud server comprehensive service program system and three client software, on the basis of the user client software, the state of each link in a production, storage and marketing maintenance process of the equipment, the login state of a user and data acquired in advance by the hardware characteristics of the intelligent equipment and the cloud server are judged and interacted with an intelligent equipment full-life cycle monitoring system of the cloud server, and relevant results are obtained to serve as the basis for logging in a user access system and inquiring whether the intelligent equipment hardware is an original factory certified product, so that the intelligent equipment comprehensive service system has the advantages of safe binding login and original factory certified product judgment which take software and hardware and cloud computing as the core.
Compared with the existing serial number verification method, the verification method creatively using the serial number plus hardware feature code has the advantage of monitoring the full life cycle of the intelligent equipment, provides authentication for the upper-layer application of the user through the monitoring of the full life cycle, and can provide guarantee with pertinence, safety and privacy for the hardware bound by the user.
Because the technical scheme of the combined operation of cloud computing and the client is adopted and the cloud server adopts the WEB technology, the operation can be carried out on the relevant business at several levels of the cloud server, the browser and the client, and the single C/S or B/S architecture is broken through, so that the whole business process completely reaches the real-time level, in particular to real-time monitoring of the whole life cycle of the intelligent equipment, real-time operation of the hardware copyright verification of the intelligent equipment and the like, the real-time services all benefit from the design of the whole system architecture, break through a single C/S or B/S architecture, and enable the services related to the whole invention to meet the requirements of an intelligent device owner on real-time query of hardware copyright and the requirement that a user identity can be bound and safely log in a user access system in real time after the intelligent device hardware is confirmed to be original factory copyright.
The system provided by the invention is a system which is matched with a cloud computing and software client side and keeps continuous mutual perception with the cloud side, and the system is used for verifying the identity of a user, hardware characteristics of intelligent equipment, setting a legal circulation channel in the processes of sale and maintenance from the cloud side, so that the system provides authentication services such as starting, continuous starting and closing for legal software. Only after the hardware characteristics and the user identity are screened by the system layer by layer can the system activate the actions of starting, continuously using, closing and the like of the third-party original software, thereby reducing the probability that the single-machine original software can run on any machine without limit only by cracking.
Aiming at the problem that privacy data generated by a plurality of software installed in the intelligent equipment is easy to peep, when the situation that all intelligent equipment is opened by an unauthorized third party and starts a sensitive application program but cannot control the privacy data to be peeped occurs in the state that an owner of the intelligent equipment does not authorize the third party to view the privacy data, the invention can obtain a new solution. The invention binds the owner information of the intelligent device with the hardware characteristics of the intelligent device, and after the information is jointly detected by the user client and the cloud, the user can be authorized to log in at the cloud end, and in the login state, the mutual inductance state is continuously kept between the client end and the cloud end, therefore, the intelligent device can provide the starting authorization of the sensitive application program, only the owner of the intelligent device can activate the starting of the sensitive application program, the client side can communicate with the cloud side in a real-time mutual sensing manner to ensure that the owner of the intelligent device keeps the continuous login state with the cloud side so as to ensure that the sensitive application program keeps the continuous starting state after being started, after the intelligent device owner logs out of the login cloud end by using the user client side, the third-party software is started and the continuous use authorization is closed, and at the moment, the sensitive software can prompt the user to close or directly close. When the user client is in a closed or off-line state, even if an unauthorized third party uses the intelligent device, any unauthorized third party cannot start the sensitive application program, and further cannot peek the user sensitive data.
Detailed Description
The present invention will be described in further detail with reference to specific examples. It should be understood that the scope of the above-described subject matter is not limited to the following examples, and any techniques implemented based on the disclosure of the present invention are within the scope of the present invention.
The design concept of the invention is as follows: the cloud computing-based intelligent device full-life cycle monitoring, user identity recognition and intelligent device hardware feature and user identity recognition binding integrated system is provided, and multiple links such as the hardware feature of the intelligent device, each stage of the full-life cycle of the intelligent hardware, ownership of the intelligent device by a user, and login and query states of the user on a cloud server through the device are tracked.
The following description is made of terms commonly used in the present application.
The intelligent device: the intelligent device in the application refers to a device set which comprises but is not limited to various computers, intelligent mobile phones and the like, is provided with a CPU computing chip and data network transmission chips such as wired, cellular and wireless WiFi and the like, is provided with an operating system and can run application programs, and is characterized by being capable of performing interconnection and intercommunication operation with a cloud server through a programming means.
Hardware characteristics of the intelligent device: the intelligent device is a chip set which has computing and network communication functions and highlights the characteristics of the intelligent device, such as a CPU, a display chip, a memory chip, a wired network chip, a wireless network chip and the like of the intelligent device.
Hardware feature code of intelligent device: the intelligent device identity code is a relevant chip of intelligent device hardware features, and a code which can identify the identity uniqueness of the intelligent device hardware feature is carried by the intelligent device hardware feature chip when the intelligent device is shipped from a factory, such as serial numbers of a CPU (central processing unit), a display chip and a memory chip, or physical addresses (also called MAC (media access control) addresses) of a wired network chip and a wireless network chip, and a device unique identification code (UUID) calculated by a special algorithm of an operating system, or an IEMI (intelligent electronic equipment interface) code of a smart phone, and the intelligent hardware feature codes are used for identifying the uniqueness of the intelligent device identity and are a basis for identifying the uniqueness of the device identity and binding with the owner identity.
Production, storage and marketing: the production, inventory, sale, maintenance and the like of the intelligent equipment enter the inventory from the production line of the intelligent equipment to the offline, are sold to users through markets, and finally reach the whole process of maintenance caused by problems in use, and are short for each stage of the whole life cycle of the intelligent equipment in the production and circulation link.
A cloud server: the system comprises Internet cloud server hardware, a cloud technology-based intelligent device 'production, storage, marketing and maintenance' tracking system and a cloud server software system which is matched with the intelligent device to perform functions of hardware feature recognition, intelligent device serial number generation and recognition, user identity registration and recognition, mutual inductance connection with the intelligent device and the like.
The user: refers to a consumer who purchases the smart device (the "owner" of the smart device), or an unauthorized (unauthorized) user of the smart device (a third party who is not authorized by the "owner" to use the smart device).
The intelligent device owner: the method comprises the steps of using the intelligent device, registering an identity account number of the intelligent device in a cloud server through a related client, and binding a hardware feature code of the intelligent device and the identity account number of the intelligent device for use. The invention considers that a user who successfully registers an account number and binds an intelligent hardware feature code in a cloud server is an intelligent device owner.
The technical solution of the present invention is explained below. The system comprises a cloud server and three clients. Which are described separately below.
Cloud server
The cloud server is used as a management center and is provided with a plurality of subsystems, wherein the subsystems comprise a factory management system, a sales management system, a logistics management system, a user access system and a product repair system, so that the functions of product overall management, intelligent equipment serial number generation, account opening and client authority management of related personnel in different links in the processes of production, sales, use and maintenance states can be realized, and functions of data aggregation, data mining and analysis and the like of the subsystems are performed.
The account opening of each service system manager is specifically as follows: the management center administrator performs account opening operation (distributing account names and passwords, filling real names, identification numbers (real name systems), contact ways, affiliated departments/units and the like of different types of personnel) on a stock administrator (corresponding to the factory management system), a salesman (corresponding to the sales management system), a logistics worker (corresponding to the logistics management system) and a maintainer (corresponding to the product repair system).
The client side authority allocation method specifically comprises the following steps: and allocating operation authorities of various personnel on user names, passwords, login, exit, data writing, modification, deletion and the like of corresponding subsystems. When a distribution library administrator, an intelligent device owner and a maintenance person respectively operate a production client, a user client and a maintenance client to upload cloud server data, the related clients log in and write operation permission of the cloud server corresponding to the system.
The operation of generating the unique serial number of the intelligent device is specifically as follows: the method comprises the steps of generating unique serial numbers corresponding to different quantities of batches of produced intelligent equipment, binding the hardware feature codes of the intelligent equipment, providing unique identification for the intelligent equipment through the hardware feature codes and the serial numbers of the intelligent equipment, and preparing for association with hardware features of the intelligent equipment and a user account in a subsequent operation process.
The following describes each subsystem.
1. A factory management system: the intelligent equipment management system is configured to interact with a production client, receive the hardware feature codes and serial numbers of the intelligent equipment uploaded by the production client, bind and store the serial numbers and the corresponding hardware feature codes, and provide an equipment query function based on the serial numbers for the sales management system.
More specifically, the method mainly comprises the steps of receiving the intelligent equipment hardware feature codes uploaded by the production client and the serial numbers corresponding to the feature codes, binding and storing the intelligent equipment hardware feature codes uploaded by the client and the serial numbers corresponding to the feature codes in a database of a factory management system, forming an inventory database based on the binding information, and providing an equipment query function based on the intelligent hardware serial numbers for a sales management system.
2. The sale management system comprises: the intelligent equipment management system is configured to be used for multiple management functions of account opening, sales order opening, sales statistics and the like of self-owned sales personnel and sales personnel of peripheral agents of intelligent equipment manufacturers. The serial number of the intelligent device is shared in the whole system, when the sales state of the intelligent device corresponding to the serial number is changed into a sold state, the serial number and the hardware characteristic of the intelligent device are marked as sold in the database, and a sales order number is generated and shared to the logistics management system.
The serial numbers of the intelligent devices are shared by the factory management system to the salesperson within the system.
When the intelligent device owner performs intelligent device registration operation through the user client, the sold mark judges the serial number fed back by the user client, and confirms whether the serial number is the serial number in the producer database, and whether the serial number is sold through a registered salesman, wherein one of the serial number and the serial number cannot be met, so that the operation of anyone registering the intelligent device through the user client fails; if the serial number is not the serial number in the factory management system database, the user client prompts the user that the equipment is not an original factory product; if the serial number is the serial number in the database of the factory management system, but the registered salesman does not perform the sales operation, when anyone registers the intelligent device through the user client, the user client prompts the intelligent device to be a 'non-formal channel product'. By the method, the situation that a factory puts the intelligent equipment into market circulation without passing through a regular sale way after producing the intelligent equipment and inputting the intelligent equipment into a factory management system can be avoided, so that a user cannot distinguish whether to obtain the intelligent equipment through a regular channel after purchasing the intelligent equipment, various unforeseen results are caused, and the vital interests of the user are actually guaranteed.
3. The logistics management system comprises: the system is configured to be used for logistics workers to log in the system, select a shared sales order number or a product repair order shared by a product repair system, and realize shipment logistics tracking and user sign-in management of the intelligent equipment under two states of sales and repair.
The working method of the logistics management system comprises the following steps:
the method comprises the following steps: the management center carries out account opening operation on the logistics worker, at the moment, the management center creates information such as an account number, a password, a real name and a job number of the logistics worker, operation permissions such as information reading, writing, modification and deletion on the logistics management system are distributed, and meanwhile, the sales management system shares a sales order number and a repair order number with the product repair system in the system to the logistics worker for browsing and selecting respectively.
Step two: after receiving a sales order number shared by the sales management system and a repair order shared by the product repair system, the logistics worker selects a specific order number independently, puts out a real object of the intelligent equipment from a warehouse and then carries out warehouse operation in the logistics management system; the order that completed the ex-warehouse operation will not be able to be selected by other logistics personnel.
Step three: and the logistics worker packs the intelligent equipment according to the name, the contact way and the receiving address of the intelligent equipment purchasing person in the sales order or the name, the contact way and the receiving address of the intelligent equipment reworking person in the rework list and sends the intelligent equipment out through the logistics company.
4. The user access system comprises: the system is configured to interact with a user client, and is used for inquiring whether the intelligent equipment is an original factory good or not and submitting repair data during repair by an intelligent equipment user through the user client; and storing the user name, each serial number, the hardware feature code of the corresponding intelligent equipment and maintenance information.
5. The third-party software information record management system comprises: the method comprises the steps of inputting, storing, classifying, summarizing and managing information such as account numbers of software information interface personnel of third-party software providers, names, categories, full names of manufacturers, version numbers and update time of third-party software provided by the third-party software providers.
The management center performs account opening operation on a third-party software provider (external partner personnel) and a third-party software information auditor (intelligent equipment manufacturer internal personnel), and at the moment, the management center creates related information such as an account number, a supplier number, a password and a real name of the third-party software provider and creates an account number, a password and a job number of the third-party software information auditor. The intelligent equipment manufacturer provides the related registered account information to the software submitting service interface person of the third party software provider, and the software submitting service interface person inputs own software filing information, wherein the filing information comprises but is not limited to the following contents: name, category, manufacturer, version number, update time, etc. of the third party software. After the logging is finished, a third-party software provider interface person clicks a 'submitting and auditing' button in the system, the information is synchronously added into the software of a corresponding version, and the related version software is sent to a third-party software information auditor for auditing, the third-party software information auditor starts a test client to be in butt joint with the third-party software for auditing, whether the information reported by the test client is consistent with the cloud storage or not and whether a popup prompt meets the design specification requirement or not are confirmed, the popup prompt is mainly that the test client is subjected to abnormal logout (logout in a mode of closing a process by a command line or mouse operation under an operating system task manager), normal logout and disconnection conditions, the third-party software is allowed to obtain the related state condition, and then a corresponding standardized prompt window is popped; if the verification is not passed, returning to the input step, and enabling the third-party software provider to resubmit the qualified information and the software version; and after the verification is passed, a third-party software auditor clicks a 'pass verification' button in the system, the system marks the verification pass on the software filing information which passes the verification, and when the third-party software installed in the intelligent equipment is started by the intelligent hardware owner, the user client feeds back the third-party software information to the cloud end and a bottom version for filing comparison with the third-party software filing system, so that the cloud end server provides whole-course authorization of states such as access, verification, starting, continuous use, closing and the like for the third-party software, and the software of the version is put in a software store of an intelligent equipment manufacturer for being downloaded by the intelligent equipment user.
6. Product system of reprocessing: configured to interact with a service client for a serviceman to confirm whether a service of the intelligent device is completed; receiving the hardware feature code and the serial number extracted by the maintenance client, judging whether the serial number is correct, and binding and storing the updated hardware feature code of the intelligent equipment and the serial number if the serial number is correct; and sharing the repair order number to a logistics management system, and recording the maintenance number.
7. Verification code generation and verification system: configured to generate, send an email or a cell phone verification code upon user registration, and verify after uploading the verification code at the user client.
The following describes each client and an interaction method between the client and the cloud server.
1. Production client
The method is used for logging in the factory management system by a manager, automatically extracting the hardware feature code of the intelligent device after logging in, and uploading the corresponding serial numbers to the factory management system. The interaction process with the factory management system is as follows:
the method comprises the following steps: the management center carries out account opening operation on the custodian, at the moment, the management center creates information such as an account number, a password, a real name and a work number of the custodian, distributes operation permissions such as information reading, writing, modification and deletion of a factory management system, and distributes login and write operation permissions of the custodian on a cloud server when the custodian operates a production client to upload cloud server data.
Step two: the method comprises the steps that a library manager applies for serial numbers to a management center in a factory management system, wherein the serial numbers are consistent with the number of intelligent equipment needing to be bound by hardware feature codes and the serial numbers and correspond to the intelligent equipment one by one.
After an intelligent device manufacturer produces intelligent device hardware and passes product quality inspection, hardware feature codes of intelligent devices produced by the intelligent device manufacturer are extracted (due to the particularity of intelligent device production, chips with different functions are adopted in the intelligent device to complete tasks with different functions, the chips are respectively provided with uniquely identified feature codes, and therefore the uniqueness of the intelligent device can be locked through combination and extraction of the feature codes), the intelligent device serial number generated by a management center is bound, and the intelligent device serial number is returned to a production inventory database of a cloud server and stored by the cloud server, so that a judgment basis is provided for the circulation state of the intelligent device in the market circulation link of the cloud server.
Step three: and the management center responds to the application, sends the serial numbers with corresponding quantity to the storage administrator in the cloud server, and displays a corresponding serial number list to the storage administrator in the cloud server.
Step four: a storage administrator logs in the cloud server factory management system through the production client and extracts the hardware feature codes related to the intelligent equipment through the production client.
The hardware feature code includes, but is not limited to, the following information: smart device UUID, IMEI (if any), CPU model, CPU serial number, graphics card manufacturer, graphics card model, graphics card memory size, graphics card chip serial number (if any), motherboard manufacturer, motherboard model, motherboard serial number, motherboard chipset manufacturer, motherboard chipset model, motherboard chipset serial number, display screen manufacturer, display screen model, display screen serial number, hard disk manufacturer, hard disk model, hard disk capacity, hard disk serial number (if any), wired network card model, wired network card MAC address, wireless network card model, wireless network card MAC address, and the like.
Step five: after the production client extracts the intelligent hardware feature code, the serial number label is photographed by a librarian and is guided into the production client, the serial number label is uploaded to a factory management system through the production client, the hardware feature code and the corresponding serial number are bound (associated) and stored by the factory management system of the cloud server, and at the moment, the serial number represents the intelligent equipment feature code and is used for subsequent sales process operation.
Second, user's customer end
The user client interacts with the user access system, is used for the user to autonomously register an account number, autonomously register new equipment, log in the cloud server and modify a password, and can also return the user access system to inquire whether the hardware of the intelligent equipment is an original product or not through the serial number and the intelligent hardware characteristic code, and the core operation data and judgment data are stored in the user access system of the cloud server.
The user client can also be in butt joint with the third-party software information filing management system after logging in is completed, and whole-process monitoring is provided for the third-party software in the states of butt joint, verification, starting, continuous use, closing and the like of the third-party software information filing management system.
A. An autonomous registration function:
the user client provides the intelligent device owner with the function that the user autonomously registers an account number in the cloud server, clicks a 'register new account number' button of a main window in the registration process, and selects a mode of filling in a mobile phone number, an e-mail address, characters and the like to register a user name in the 'register new account number' window.
a. Using character mode as user name registration
When the user selects a character mode to register the user name, the registration interface can also require the user to fill in the mobile phone number or the email address, the mobile phone number or the email address is uploaded to the cloud server together, verification code comparison is carried out between the mobile phone verification code generation and the verification system or between the email verification code generation and the verification system, the mobile phone number or the email address is bound, and the mobile phone number or the email address is used for facilitating the cloud server to send a mobile phone short message or an email verification code to verify the identity of the user when the password is forgotten, and resetting the password.
The intelligent device owner finishes filling in related information, clicks a verification code sending button, at the moment, a user client scans and records a hardware feature code of the intelligent device, and sends the hardware feature code to the cloud server together with a user name, a password, a mobile phone number or an e-mail address, after the cloud server receives the data, the cloud server firstly judges the hardware feature information, and if the hardware feature code is consistent with features stored by the cloud server, the cloud server generates a short message or an e-mail verification code sent by a verification system through the mobile phone verification code; and if the hardware feature code is inconsistent with the feature stored by the cloud server, the cloud server refuses to send the short message or the e-mail verification code, and returns the result refused to send to the client, and at the moment, the client pops up a prompt window to prompt the original manufacturer certified products of the non-equipment manufacturer of the intelligent equipment and refuse to send the verification code.
After receiving and filling in the verification code, the intelligent device owner clicks a button of 'registering a new user', and at the moment, the user client scans and records the hardware feature code of the intelligent device again, and the data is sent to the cloud server together with the user name, the password, the mobile phone number or the email address, and after the cloud server receives the data, firstly, judging hardware characteristic information, if the hardware characteristic code is consistent with that stored in the cloud server, then verifying whether the short message verification code is consistent by a mobile phone verification code generation and verification system so as to ensure that the registered mobile phone number is consistent with the mobile phone number receiving the verification code, if the two are consistent, the cloud server allows account opening, the account number and the password data of the user are written and stored in the cloud server, the result of successful registration is returned to the user client, and the user client prompts the user that the account registration is successful; if the hardware feature code is inconsistent with the hardware feature code stored in the cloud server, the cloud server refuses to open an account, and returns a result of refusing to register to the user client, and at the moment, the user client pops up a prompt window to prompt the original manufacturer certified products of the non-equipment manufacturer of the intelligent equipment and refuse to register an account; if the hardware feature code is consistent with that stored by the cloud server but the short message verification code is inconsistent, the cloud server refuses to open an account and returns a result of refusing to register to the user client, and the user client pops up a prompt window to prompt that the short message verification code is wrong and refuses to register an account.
B. Registration by using mobile phone number and e-mail address as user name
The operation logic when the intelligent device owner adopts the mobile phone number and the e-mail address as the user name to register the account number is as follows: the intelligent device owner inputs a mobile phone number or an electronic mail address as a user name at the user client, inputs a password and clicks a button of sending a verification code, at the moment, the user client scans and sends hardware characteristics of the intelligent device to the cloud server, and the cloud server judges the hardware characteristics. If the hardware characteristics are consistent with the information stored in the cloud server, the mobile phone verification code generation and verification system of the cloud server or the electronic mail box verification code generation and verification system sends verification codes to filled mobile phone numbers or electronic mail addresses, and an intelligent device owner fills the verification codes which are sent to relevant mobile phones or electronic mails by the cloud server in a verification code input box; if the hardware characteristics are inconsistent with the information stored in the cloud server, the cloud server returns a result that the hardware characteristics are wrong and the verification code cannot be sent to the user client, and the user client prompts a user that the original factory intelligent hardware is not used for registration and the registration fails.
Judging that the hardware characteristics are correct at the cloud server, sending a verification code to a mobile phone number or an email address filled by an intelligent device owner, filling the verification code by the intelligent device owner, clicking a button for registering a new user, scanning the hardware characteristics of the intelligent device again by the user client, sending a user account number, a password and the verification code to the cloud server, judging whether the hardware characteristics and the verification code are consistent with those of the cloud server again by the cloud server, judging whether the verification code is consistent again if the hardware characteristics and the cloud server are consistent, returning a verification code inconsistency result to the user client by the cloud server if the verification code is inconsistent, and popping a prompt window by the user client to prompt that the verification code is wrong; if the verification codes are consistent, the user is successfully registered, the user access system stores each associated data successfully registered in the cloud server database, meanwhile, a successful registration result of the user client is returned, and after the user client receives the successful registration result, a prompt window pops up to confirm that the user is successfully registered. If the cloud server judges that the hardware characteristics are inconsistent with the storage of the cloud server again, a hardware characteristic error result is returned to the user client, and a prompt window is popped up by the user client to prompt a user that the original factory intelligent hardware is not used for registration and the registration fails.
Preferably, user identification biological characteristic identification data including fingerprints, irises, faces and the like can be added after the user account registration is completed, the mode that an owner of the intelligent device logs in the cloud server is enriched, the login operation is simplified, and the data including the fingerprints, the irises, the faces and the like can be input only when the user can normally register a new user and register new equipment, so that the login mode does not relate to a new equipment registration process, and the login process is as follows:
the intelligent device owner successfully logs in the cloud server user access system in a user name plus password mode by using the user client, and the intelligent device owner is allowed to log in modes of fingerprints, irises, faces and the like. And starting the user client again, and selecting the corresponding login modes for login, wherein the modes can only select one item in the login process without all selections. After selection, the owner of the intelligent device cooperates with relevant parts of the device to acquire data of items such as fingerprints/irises/faces, the acquired data is compared with the data of the items such as the fingerprints/irises/faces of a local database, if the comparison is inconsistent, the user inputs the data again, if the comparison is repeated for three times and errors occur all the time, a window is popped up at the client side to prompt that the items such as the fingerprints/irises/faces cannot be used for logging in, an account password login frame is popped up, the items are logged in an account password mode instead of the account password mode, and the account password login mode is not repeated; if the comparison is consistent, the data in the modes are bound with the user name and the password, the user client starts an account login program at the moment, the user name, the password and the hardware characteristic code of the intelligent device are sent to the cloud server, and the user logs in the user access system smoothly after the cloud server detects no error; and if the cloud server detects that the hardware feature code of the intelligent equipment is wrong, the intelligent equipment refuses to log in and returns error information that the hardware feature code of the intelligent equipment is wrong, and at the moment, after the client of the user receives the relevant information, a prompt for prompting that the hardware of the intelligent equipment is a non-original factory certified product is popped up, and the intelligent equipment refuses to log in.
B. Login and registration of newly purchased intelligent hardware functions:
the user client provides a login function and a function of registering newly purchased intelligent hardware, and binds the newly purchased hardware with a user account, and the method is completed at one time, and the specific flow is as follows:
the intelligent device owner opens a user client, fills account numbers (the account numbers can be characters, mobile phone numbers and electronic mailbox numbers) and passwords in the user client, clicks a login button to log in a cloud server, the user client scans hardware feature codes of the intelligent device and uploads the hardware feature codes, the user name and the passwords to the cloud server at the moment, the cloud server judges whether the hardware features are consistent with data in a database after receiving information such as the user account numbers, the passwords and the hardware feature codes, if the hardware feature codes are not consistent, the cloud server returns a result of the inconsistency of the hardware features to the user client, and the user client pops up a prompt window of 'non-original genuine products of the intelligent device' after receiving the result; if the result is consistent with the sales mark, the cloud server does not return the result to the client, whether the sales mark exists in the database or not is continuously judged, if the sales mark does not exist, the result without the sales mark is returned to the user client, and the user client pops up a prompt window of 'intelligent equipment informal sales channel products' after receiving the result; if the sales mark is carried, a result is not returned to the user client, whether the user account number and the password are correct or not is continuously judged, if the result is incorrect, different results of the user name or the password error are returned to the user client, and after the user client receives the result, different windows are respectively popped up to prompt the user that the user name or the password are incorrect; if the login success result is received, popping up a login success prompt window by the user client to inform the user that the process of logging in the cloud server is completed; if the serial number is not bound, allowing the user to log in the cloud server, returning the result that the user logs in successfully but does not bind the serial number to the user client, popping up a bound serial number window after the user client receives the returned result, filling the serial number by the user, and clicking a button of 'registering new equipment', at the moment, the user client encrypts and uploads a user name, a password, a hardware feature code and a serial number to the cloud server together, after the cloud server receives the information, judging whether the user name, the password, the hardware feature code and the serial number are consistent with the data of the cloud server database or not, if so, the user name, the hardware feature code and the serial number are bound and stored in a user access system database, and returning a binding success result to the user client, and popping up a prompt window by the user client to prompt the user that the registration of the new equipment is completed; if the data is inconsistent with the data, the cloud server returns a message comparison abnormal result to the client, and the client pops up a prompt window of 'abnormal data reception and failure in registering new equipment' after receiving the result.
C. The genuine product inquiry function:
the intelligent equipment owner successfully logs in the user access system through the user client, the main interface of the user client displays a 'genuine product query' button, the intelligent equipment owner clicks the 'genuine product query' button, the user client scans the hardware feature code of the intelligent equipment and sends the hardware feature code and the user account number to the user access system, the user access system receives related information, the user information and the equipment information are matched, the matched correct result is returned to the user client after the matching is finished, and a prompt window is popped up to display that the intelligent equipment under the user name is genuine.
The whole process embodies the characteristic of binding the user account and the hardware characteristics, and only in the state of binding the two parties, the user access system allows the correct result to be fed back to the genuine product query operation of the intelligent device.
D. Password modification function:
when the intelligent device owner forgets the login password of the cloud server, the user client pops up a password retrieving window by clicking a password forgetting button on a user client interface, and the window is provided with a user name, a mobile phone number, an e-mail address, a verification code filling, a new password inputting prompt and corresponding input boxes, and a verification code sending button and a password modifying button. The user can select one from the mobile phone number and the e-mail address to fill in, the cloud server can return the verification code to the corresponding position according to different requests uploaded by the client, when the user fills in the relevant information of the user name, the mobile phone number/the e-mail address, and clicks a button of sending a verification code, the user client scans the hardware characteristic code of the intelligent device, the hardware characteristic code is uploaded to the cloud server together with the user name, the mobile phone number/the e-mail address, after the cloud server receives the relevant information, the cloud server judges whether the hardware characteristic code of the intelligent device is consistent with the information in the database of the cloud server, if not, the result of the inconsistency and refusal of sending the verification code is returned to the user client, and after the user client receives the result, popping up a prompt window to prompt a user that the intelligent equipment is not genuine and the verification code is refused to be sent; if the result is consistent, the cloud server does not return any result, whether the hardware feature code has a sales mark in the database is continuously judged, if the result does not have the sales mark, an error result which does not have the sales mark and refuses to send the verification code is returned to the user client, and after the user client receives the error result, a prompt window is popped up to prompt the user that the intelligent equipment is a product which is not a normal channel of an original factory and refuses to send the verification code; if the user name, the mobile phone number or the e-mail address is incorrect, an error result is returned to the user client, and the user client pops up a prompt window to prompt that the user name, the mobile phone number or the e-mail address are incorrect and needs to be input again by a user; if the user name, the mobile phone number/the e-mail address are correct, the cloud server sends a verification code to the mobile phone number/the e-mail address filled by the user, the user continues to fill the verification code sent by the cloud server in a verification code input box after receiving the verification code, fills a new password, clicks a 'password modification' button, the user client uploads the user name, the new password and the verification code to the cloud server, the cloud server judges whether the user name and the verification code are consistent with or inconsistent with the cloud server, error information is returned to the user client, and the user client pops up an error prompt window to prompt the user that the verification code is wrong; and the cloud server changes the original password under the user name into a new password, stores the new password in a database of the user access system, returns a successful modification result to the user client, and pops up a password modification success prompt window after the user client receives the result.
Thirdly, the method comprises the following steps: third-party software testing client
The method is used for testing the software provided by the third-party software provider, and comprises the steps of testing whether the information such as the name, the category, the full manufacturer name, the version number, the updating time and the like of the third-party software returned by the third-party software provider is consistent with the information submitted in the third-party software information record management system, simulating the use scene of a user client, and checking whether the pop-up information of the third-party software meets the agreed design specifications. The client simulates the working mode of the user client and provides the client for a third-party software manufacturer to carry out internal docking test, so that the architecture of the whole system is not influenced. The respective test functions thereof will be explained below.
a. Third party software authorization functionality
The functions of the third-party software testing client for performing whole-process authorization on states of the third-party software such as access, verification, starting, continuous use and closing are as follows:
the third-party software testing client provides a docking mechanism for accessing, auditing, starting, continuously using and closing states for the third-party software (hereinafter referred to as "third-party software authorization docking mechanism"), and the mechanism can be implemented by several ways including but not limited to:
1. the third-party software testing client directly provides an authorization interface (software interface authorization mode).
2. The third-party software testing client opens up two areas in the memory of the intelligent device, one area is written by the third-party software testing client and the third-party software is read only, and the other area is written by the third-party software testing client and the third-party software only (a memory authorization mode).
3. The third-party software testing client establishes two encrypted files in the intelligent device memory, one is written by the third-party software testing client and the third-party software is read only, and the other is read only and the third-party software is written (file authorization mode).
4. The third-party software testing client adopts a mode that a dynamic link library provides an interface (dynamic link library interface authorization mode).
The third-party software testing client side is provided with a third-party software authorization browsing window, and displays the third-party software record information and the number of the third-party software currently authorized to be started by the third-party software testing client side to a tester in real time, so that the tester can browse and manage conveniently.
When the third-party software testing client is not started, the network connection is interrupted, the testing personnel does not log in the cloud end, or the cloud end logging fails, the state belongs to a state that the testing personnel does not access the cloud end, at the moment, a third-party software authorization interface of the third-party software testing client is not activated, the third-party software cannot acquire software starting authorization information through the authorization interface, meanwhile, third-party software filing information cannot be interacted with the third-party software testing client, namely, no authorization is acquired, and at the moment, the third-party software cannot be started.
In the process that a tester logs in the cloud, the cloud server verifies the binding relationship between the hardware characteristics of the intelligent device and the account of the tester and whether the uploaded encrypted data are consistent with the existing data of the cloud server, so that the tester can open the third-party software in a third-party software authorization mode of testing the client by the third-party software with the identity of the tester through the third-party software after the tester successfully logs in the cloud by using the intelligent device and the account belonging to the tester, but not open the third-party software authorized by others.
And after the third-party software testing client successfully logs in the cloud, the third-party software testing client is in butt joint with the user access system, and the third-party software testing client and the cloud user access system start respective real-time online monitoring interfaces and are in butt joint.
b. The authorization interface is initiated. The method comprises the following steps:
the method comprises the following steps: a third-party software test client logs in a cloud server;
step two: and the third-party software testing client and the user access system establish a communication maintaining mechanism through respective real-time online monitoring interfaces. This mechanism periodically checks (for example, with 30 seconds as one check period) the connection states of both parties.
Step three: the third-party software testing client and the user access system periodically send the account number of the tester and the hardware information feature code of the intelligent device, so that the cloud user access system can periodically confirm the identity and real-time online state of the tester and the intelligent device.
Step four: the user access system judges whether the relevant data is received within the appointed time, if so, the confirmation online information is sent to the third-party software testing client, and after the third-party software testing client receives the confirmation of the online information, the third-party software authorization interface is started, and the normal authorization data interactive work is started; otherwise, the monitoring interface is closed, the user is set to be in an exit state, and the third-party software testing client side logs in the cloud again.
c. And starting and authorizing interactive operation of third-party software:
the method comprises the following steps: the testing personnel starts the third-party software, and the third-party software feeds back the third-party software record information of the third-party software through the third-party software testing client interface;
step two: after receiving the third-party software filing information, the third-party software testing client uploads the information to a third-party software information filing management system;
step three: the third-party software information filing management system judges whether the third-party software filing information is consistent with that stored in the cloud server or not, if not, an error result is returned to the third-party software testing client, the third-party software testing client sends out a parameter for refusing the start of the third-party software through an authorization interface, the third-party software is refused to start, a prompt box for preventing the third-party software from starting is popped up, and the third-party software cannot be started and does not perform subsequent steps; if the two are consistent, the next step is carried out;
step four: returning a correct result to the third-party software testing client, sending out parameters allowing the third-party software to be started by the third-party software testing client, displaying information such as the version number and the software name of the third-party software in a third-party software browser of the third-party software testing client, and initializing a continuous use monitoring interface with the third-party software;
step five: the third-party software is started successfully, the third-party software testing client and the third-party software start a continuous use monitoring interface at the same time, a user access system monitors whether a user account and an intelligent equipment hardware information feature code sent to the third-party software testing client by the third-party software testing client are in an appointed timestamp period according to a protocol so as to confirm the online state of the third-party software testing client, the online state is fed back to the third-party software testing client in the appointed period, and the online state is fed back to the third-party software by the third-party software testing client so as to ensure the real-time continuous use state of the third-party software to be stable.
d. Continuous use monitoring interface
There are two modes of operation for the continuous use monitoring interface. One mode is that a third-party software test client actively pushes connection state parameters through a monitoring interface, and the third-party software judges the on-off state of the third-party software test client by receiving or not receiving related state parameters in a specified period; the other mode is that the third-party software requests the current-stage connection state parameters from the third-party software testing client through the interface, the third-party software testing client responds according to the current state, and returns or does not return the related state as a judgment basis for continuous use.
The above two periodic detection mechanisms of the working state are that the third-party software test client generates an instant time stamp at the moment of the outgoing state and sends the instant time stamp to the third-party software, so that the comparison of whether the interaction period of the two parties is in the appointed time period is facilitated. The third-party software testing client side can return the plurality of connection state detection parameters by continuously using the monitoring interface, and after the third-party software receives the parameters, the third-party software adds the timestamp corresponding to the received parameters finally, so that the work of comparing whether the interaction periods of the two parties are in the appointed time period can be completed.
Preferably, in consideration of convenience of the tester in use, the third-party software testing client may design a pop-up window for prompting the tester of interruption of communication with the cloud (i.e., a "network disconnection" state, which is hereinafter referred to as a "network disconnection window"), and in addition, the third-party software testing client may also send or respond to the current connection state with the cloud to the third-party software.
The third-party software testing client and the continuous use monitoring interface of the third-party software are used for receiving state parameters (namely online state identification parameters) of the third-party software authorization interface of the third-party software testing client and the cloud server in continuous connection or disconnection and whether state parameters of a connection interruption prompt window popping up with the cloud server exist or not so as to judge whether the third-party software needs to be closed or not.
In a mode that a third-party software testing client actively pushes connection state parameters through the interface and the third-party software judges the on-off state of the third-party software when receiving or not receiving related state parameters in a specified period, the specific working process is as follows:
when the third-party software testing client is normally connected with the cloud server, the third-party software testing client feeds back a connection state parameter with the cloud to the third-party software as true when continuously using the monitoring interface, the state parameter of the pop-up broken window is false, and the third-party software is in a working state of normal opening; when the third-party software testing client is disconnected with the cloud server, a prompt window which is disconnected with the cloud server can be popped up by the third-party software testing client, at the moment, the state parameter of the third-party software testing client connected with the cloud server is false, the state parameter of the prompt window which is popped up and disconnected with the cloud server is true, and the new parameter value is informed to the third-party software through the continuous use monitoring interface of the third-party software testing client. In this state, the third-party software pops up a prompt window to prompt a tester, the third-party software tests whether the connection between the client and the cloud end is interrupted and whether the third-party software needs to be closed or not, or a mechanism for directly storing a working result and quitting the software is established through the third-party software to forcibly store the current work and directly quit the software. It should be noted that, in this embodiment, the case that the third-party software testing client is disconnected from the cloud end is understood that the third-party software testing client cannot determine whether the identity of the tester is the same as the user, because a result of successful login returned by the cloud end in real time and continuous connection monitoring with the third-party software testing client is started cannot be obtained at this time, the result must be obtained only by logging in again after networking, so that the third-party software must be informed of the actual connection state of the current third-party software testing client and the cloud end server, so that the third-party software developer has to choose to prompt the user to turn off the software, or establish a mechanism of directly storing a working result and quitting the software, so that the software is forcibly quitted.
The monitoring interface for the third-party software testing client side to be continuously connected with the third-party software not only feeds back the connection state with the cloud to the third-party software, but also provides a prompting closing judgment method for the third-party software when the third-party software testing client side accidentally exits or artificially exits, namely, after the interface exceeds a preset protocol monitoring period (for example, 10 seconds), the third-party software fails to acquire a new cloud connection state updating parameter or the connection state updating parameter interval exceeds the protocol period through the interface, and the third-party software testing client side does not update the prompting window parameter of the interruption of the connection with the cloud, so that the connection failure with the third-party software testing client side is automatically judged, and the state is considered to be that the third-party software cannot judge whether the identity of a user is the user in the embodiment, the third-party software developer can choose to forcibly save the current working state, quit the operating mechanism of the software and forcibly quit the software.
The third-party software requests the working state of the current connection state parameter from the third-party software testing client through the interface, and the mechanism is similar to the mechanism that the third-party software testing client actively pushes the relevant parameter, and the difference is that the third-party software is an active state requesting party and the third-party software testing client is a state returning party. After receiving the state application of the third-party software, the third-party software testing client performs response reply according to the current state in a specified period, and when the return is completed or the return related state parameters are not completed, the third-party software testing client can be used as a judgment basis for judging whether the third-party software testing client can be continuously used or not.
Preferably, after the function of logging in the website of the user access system by the tester is added, after the third-party software test client successfully logs in, the operation of forbidding starting and closing of the third-party software on the cloud server is provided for the tester on the web page of the user access system, and the specific steps are as follows:
the method comprises the following steps: and the tester starts a third-party software testing client on the intelligent equipment.
Step two: the tester starts the certified third party software.
Step three: and the third-party software is normally started through the authentication mechanism of the third-party software test client.
Step four: the third-party software regularly returns the relevant information of the software through the third-party software test client. The method comprises the following steps of (1) working states of software name, software ID, starting and closing of the software and the like;
step five: and displaying software related information including a software name, a software ID and a related state, which is returned by the third-party software through the third-party software testing client, on a web page of the user access system.
Prior to this step, the tester has also logged in to the user's web page of the access system at this point in a number of ways as previously described. A user access system web page is preset with a 'closing authorization' button at a position corresponding to a third-party software name;
step six: the tester clicks a closing authorization button corresponding to third-party software needing to be closed;
step seven: the user access system transmits the related software name, software ID and closing operation to the third-party software testing client;
step eight: the third-party software testing client receives the software name, the software ID and the closing operation instruction;
step nine: the third-party software testing client stops updating the connection state parameters with the cloud server to the third-party software, and pops up a prompt window interrupted in connection with the cloud;
step ten: the third-party software judges the connection state to be an abnormal exit state;
step eleven: and the third-party software developer takes mandatory measures, saves the current working state and forcibly quits the software.
Third, maintenance client
The intelligent hardware feature code is re-extracted after the intelligent equipment hardware is maintained and related parts are replaced, the new hardware feature code and an original serial number are uploaded to a cloud server maintenance database together for storage, the cloud server is enabled to perform data updating operation after the intelligent equipment is maintained, the intelligent equipment hardware feature code after maintenance is bound to the original serial number in an associated mode, maintenance state records of the intelligent equipment are added, subsequent hardware feature recognition operation of a user logging in a cloud platform is facilitated, and it is guaranteed that the intelligent hardware of the user is original factory certification.
The maintenance client and the cloud server are required to perform the following interaction to realize the functions:
the management center carries out account opening operation on a maintainer, the management center generates information such as an account number, a password, a real name and a job number of the maintainer at the moment, the account number of the maintainer is classified into a maintainer group and put into a product repair system, the operation permission of the maintainer is distributed by the product repair system, and the login and writing operation permission of the cloud server are distributed when the data of the cloud server is uploaded by a maintainer operation and maintenance client.
When the hardware of the intelligent equipment of an intelligent equipment owner breaks down and needs to be maintained, logging in the user access system through an after-sales maintenance special login channel of the cloud server user access system, submitting information such as names, contact ways, delivery addresses, intelligent equipment serial numbers needing to be maintained, fault phenomena and the like in the system, and checking out the permission of an intelligent equipment manufacturer to replace equipment parts (if the option is not checked out, a maintainer of the intelligent equipment manufacturer cannot replace the fault parts, obtain the authority of re-extracting the hardware features of new equipment and storing the hardware features in the cloud server product maintenance system); the user access system generates a repair order number, and after receiving the repair order number, the user returns the equipment to a maintenance address specified by the intelligent equipment manufacturer according to the prompt of the user access system.
After receiving the fault equipment, the maintenance personnel maintain according to the actual condition, if the parts of the equipment do not need to be replaced, after the maintenance is finished, the maintenance personnel confirm that the maintenance work is finished in the product repair system, the product repair system adds the repair order number to the account number of the maintenance personnel and stores the number in the product repair system, after the storage is finished, the information of the relevant order number is pushed to the logistics management system, and the logistics personnel perform subsequent operation; when meeting the situation that the parts need to be replaced, after the parts are replaced, a maintenance person runs a maintenance client on the intelligent device, logs in the cloud server product repair system through the maintenance client, after the parts are logged in, the maintenance client automatically scans various hardware characteristics of the intelligent device after the parts are repaired and displays the hardware characteristics to the maintenance person, after the hardware characteristics of the intelligent device are displayed on the maintenance client, the maintenance person manually fills a serial number of the intelligent device for repair (the serial number is not changed after the whole intelligent device is repaired and repaired, only hardware characteristic information of the device is changed, so that the design does not disturb the one-to-one corresponding relation between the user identity and the intelligent device), photographs label paper of the serial number, sends the label paper to the intelligent device of the current running maintenance client, is extracted by the maintenance client, and after the work is completed, the maintenance person clicks an equipment hardware information updating button of the maintenance client, encrypting and uploading a new hardware feature code and a new serial number of the intelligent equipment to a cloud server product repair system, comparing whether the serial number is consistent with the serial number stored by a cloud server or not by the cloud server product repair system, if not, returning error information to a maintenance client, popping up a serial number error after the maintenance client receives the error information, prompting a maintenance worker to re-enter an error prompt window of the serial number, and re-inputting the accurate original serial number of the intelligent equipment by the maintenance worker; if the serial number of the intelligent equipment is consistent with the hardware feature code of the intelligent equipment, the product repair system binds and stores the updated serial number of the intelligent equipment and the hardware feature code of the intelligent equipment, updates the hardware feature code of the intelligent equipment accessed into a system database by a user, and binds and stores the serial number and the new hardware feature code (because the serial number of the intelligent equipment is not changed at the moment, the binding relation between the serial number and the user is not changed, and only the incidence relation between the serial number and the hardware feature code after maintenance is changed); after the binding work is finished, a user access system adds a maintenance mark to the hardware feature bound by the serial number (at this time, a user name, the serial number and a maintained hardware feature code in the user access system are bound), so that when the user access system and the product repair system check whether the intelligent equipment corresponding to the related serial number has an official maintenance record, a judgment result is obtained by comparing whether the same hardware feature exists under the same serial number in databases of the user access system and the product repair system (the step is used for preventing a user from taking a maintenance center authorized by a non-intelligent equipment original factory/original factory on the market to maintain after the hardware of the intelligent equipment fails, and after equipment parts are replaced, the user logs in a cloud server again and generates unpredictable results through a third-party software authorization mode provided by the cloud server and the user client); after the maintenance personnel finish the steps, the maintenance work completion is confirmed in the product repair system, the product repair system adds the repair order number to the account number of the maintenance personnel and stores the repair order number in the product repair system, after the storage is completed, the related order number information is pushed to the logistics management system, and the logistics management personnel perform subsequent operation.

Claims (8)

1. The third-party software authorization system based on intelligent equipment monitoring and user identity binding is characterized by comprising a cloud server and clients, wherein the clients comprise a user client, a maintenance client, a production client and a third-party software testing client; the third-party software testing client side realizes the whole-course authorization of the access, the verification, the starting, the continuous use and the closing state of the third-party software through a software interface authorization mode, a memory authorization mode, a file authorization mode or a dynamic link library interface authorization mode;
the cloud server is configured to: generating a serial number of the intelligent equipment, binding and storing the hardware feature code uploaded by the client with the serial number, and realizing the management of the full life cycle of the intelligent equipment hardware based on the serial number; carrying out account registration and client authority configuration on related personnel; judging and storing the related data uploaded by the client and the information of the third-party software; the system is provided with a factory management system, a sales management system, a logistics management system, a user access system and a product repair system, and the management of production, sales, purchase and maintenance links in the whole life cycle is respectively realized; the intelligent device is also provided with a third-party software information record management system for realizing the management of third-party software running on the intelligent device;
the plant management system is configured to: interacting with the production client, receiving the hardware feature codes and serial numbers of the intelligent equipment uploaded by the production client, binding and storing the serial numbers and the corresponding hardware feature codes, and providing an equipment inquiry function based on the serial numbers for the sales management system;
the sales management system is configured to: when the sales state of the intelligent equipment corresponding to the serial number is changed into sales, the serial number and the hardware feature code of the intelligent equipment are marked for sales in the database and a sales order number is generated, and the sales order number is shared to the logistics management system;
the logistics management system is configured to: a logistics worker logs in the system and selects a shared sales order number or a repair order shared by the product repair system, so that the shipment logistics tracking and the user signing management of the intelligent equipment in two states of sales and repair are realized;
the user access system is configured to: interacting with the user client, and inquiring whether the intelligent equipment is an original product or not by the user of the intelligent equipment through the user client and submitting repair data during repair; storing personal information of a user name and a password, binding the information with each serial number, hardware feature codes of the intelligent equipment corresponding to the serial numbers and maintenance information, and providing whole-process supervision of starting, continuous use and closing states for third-party software;
the product rework system is configured to: the system is interacted with a maintenance client and used for a maintainer to confirm whether the maintenance work of the intelligent equipment is finished; receiving the hardware feature code and the serial number extracted by the maintenance client, judging whether the serial number is correct, if so, binding and storing the updated hardware feature code of the intelligent equipment and the serial number, and updating the hardware feature code of the intelligent equipment in a user access system database to be consistent with the hardware feature code after maintenance; sharing the repair order number to a logistics management system;
the third party software information docketing management system is configured to: storing and managing third-party software related information, judging the third-party software information uploaded by the user client, and monitoring the running state of the third-party software;
the service client is configured to: the system is used for logging in the product repair system by a maintainer, automatically scanning various hardware feature codes of the intelligent equipment after the maintenance is finished after logging in, and uploading corresponding serial numbers to the maintenance management system;
the user client is configured to: the system is used for autonomously registering an account number of a user, autonomously registering new purchased equipment, inquiring whether the intelligent equipment is an original factory certified product or not, and providing butt joint and interaction service of third-party software and a cloud server;
the third party software testing client is configured to: the system is used for testing the third-party software, simulating the use scene of the user client, and checking whether the pop-up information of the third-party software meets the appointed design specification;
the third-party software testing client interacts with the cloud server to realize the starting authorization interactive operation of the third-party software, and the steps are as follows:
the method comprises the following steps: the user starts third-party software, and the third-party software feeds back the third-party software filing information of the third-party software through a third-party software testing client interface;
step two: after receiving the third-party software filing information, the third-party software testing client uploads the information to a third-party software information filing management system;
step three: the third-party software information filing management system judges whether the third-party software filing information is consistent with that stored in the cloud server or not, if not, an error result is returned to the third-party software testing client, the third-party software testing client sends out a parameter for refusing the start of the third-party software through an authorization interface, the third-party software is refused to start, a prompt box for preventing the third-party software from starting is popped up, and the third-party software cannot be started and does not perform subsequent steps; if the two are consistent, the next step is carried out;
step four: the correct result is returned to the third-party software testing client, the third-party software testing client sends out parameters allowing the third-party software to be started, the version number and the software name information of the third-party software are displayed in a third-party software browser of the third-party software testing client, and a continuous use monitoring interface of the third-party software is initialized;
step five: and the third-party software testing client and the third-party software start a continuous use monitoring interface at the same time, and a user access system monitors whether a user account and an intelligent equipment hardware information feature code sent to the third-party software testing client by the third-party software testing client are in an appointed time stamp period according to a protocol so as to confirm the online state of the third-party software testing client, feeds a judgment result back to the third-party software testing client in the appointed period, and feeds the online state back to the third-party software by the third-party software testing client.
2. The third-party software authorization system based on intelligent device monitoring and user identity binding according to claim 1, wherein the cloud server further comprises a verification code generation and verification system for generating and sending an email or a mobile phone verification code when a user registers, and performing verification after the user client uploads the verification code.
3. The third-party software authorization system based on smart device monitoring and user identity binding according to claim 1 or 2, wherein in a production link, an interaction process between the production client and the cloud server is as follows:
the method comprises the following steps: the cloud server carries out account opening operation and authority distribution on a storage administrator in advance, and the storage administrator applies for a serial number to the cloud server;
step two: the cloud server responds to the application and sends the serial numbers with corresponding number to the storage administrator in the cloud;
step three: a custodian logs in a factory management system through a production client, and the production client extracts a hardware feature code of the intelligent equipment;
step four: the method comprises the steps that a storage administrator uploads a serial number and a hardware feature code of the intelligent device to a factory management system, and a cloud server binds and stores the hardware feature code and the corresponding serial number.
4. The third-party software authorization system based on intelligent device monitoring and user identity binding according to claim 1, wherein in the sales link, the workflow of the sales management system is as follows:
the method comprises the following steps: the cloud server carries out account opening operation and authority distribution on a salesman in advance, and the factory management system shares the serial number of the intelligent equipment which can be sold in the stock;
step two: a salesman logs in a sales management system to carry out sales operation, and marks a sales state corresponding to the serial number of the sold intelligent equipment as sold; the sales management system generates a corresponding sales order number according to the serial number and the hardware feature code;
step three: and the sales management system shares the sales order number in the step two to the logistics management system.
5. The third-party software authorization system based on smart device monitoring and user identity binding according to claim 2, wherein when the user registers, the interactive workflow between the user client and the cloud server is as follows:
the method comprises the following steps: a user fills in registration information on a registration interface of a user client;
step two: a user sends a verification code request to a cloud server, and a user client scans and records a hardware feature code of the intelligent device and sends the hardware feature code and registration information to the cloud server;
step three: the cloud server verifies the hardware feature codes, if the hardware feature codes can be matched with the hardware feature codes stored in the cloud server, the fourth step is carried out, otherwise, the verification codes are refused to be sent, and the subsequent steps are not carried out;
step four: the verification code generation and verification system generates a verification code and sends the verification code to a user;
step five: the user fills the verification code in a registration interface and clicks registration;
step six: the user client scans and records the hardware feature code of the intelligent device again, and sends the hardware feature code and the registration information to the cloud server;
step seven: the cloud server verifies the hardware feature codes, if the hardware feature codes can be matched with the hardware feature codes stored in the cloud server, the step eight is carried out, and if not, registration is refused;
step eight: and the verification code generation and verification system carries out verification of the verification code, if the verification is successful, the registration is successful, otherwise, the registration is refused.
6. The intelligent device monitoring and user identity binding-based third-party software authorization system of claim 1, wherein the third-party software test client interacts with the user access system to enable activation of a third-party software authorization interface, comprising,
the method comprises the following steps: a third-party software test client logs in a cloud server;
step two: the third-party software testing client and the user access system establish communication through respective real-time online monitoring interfaces;
step three: the third-party software testing client periodically sends a user account and an intelligent equipment hardware information feature code to the user access system so that the cloud user access system can periodically confirm the identity and real-time online state of the user and the intelligent equipment;
step four: the user access system judges whether the relevant data is received within the appointed time, if so, the user access system sends the on-line confirmation information to the third-party software testing client, and after the third-party software testing client receives the information, the third-party software authorization interface is started, and normal authorization data interaction work is started; otherwise, the monitoring interface is closed, and the third-party software testing client needs to log in the cloud again.
7. The third-party software authorization system based on intelligent device monitoring and user identity binding of claim 1, wherein the method for the third-party software testing client to periodically monitor the third-party software comprises: the third-party software test client actively pushes the connection state parameters through the monitoring interface, and the third-party software judges the on-off state of the third-party software when receiving or not receiving the relevant state parameters in a specified period; or the third-party software requests the current-stage connection state parameters from the third-party software testing client through the interface, and the third-party software testing client replies a response according to the current state.
8. The third-party software authorization system based on intelligent device monitoring and user identity binding according to any one of claims 1-2 and 4-7, characterized in that the user access system is provided with a web page, and a function key for a user to prohibit the starting and closing operation of the third-party software is arranged on the web page.
CN201911042019.1A 2019-10-30 2019-10-30 Third-party software authorization system based on intelligent equipment monitoring and user identity binding Active CN110768839B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911042019.1A CN110768839B (en) 2019-10-30 2019-10-30 Third-party software authorization system based on intelligent equipment monitoring and user identity binding

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911042019.1A CN110768839B (en) 2019-10-30 2019-10-30 Third-party software authorization system based on intelligent equipment monitoring and user identity binding

Publications (2)

Publication Number Publication Date
CN110768839A CN110768839A (en) 2020-02-07
CN110768839B true CN110768839B (en) 2022-07-22

Family

ID=69334759

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911042019.1A Active CN110768839B (en) 2019-10-30 2019-10-30 Third-party software authorization system based on intelligent equipment monitoring and user identity binding

Country Status (1)

Country Link
CN (1) CN110768839B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112835635A (en) * 2021-01-25 2021-05-25 广州视源电子科技股份有限公司 Equipment replacement method, device, system, server and storage medium
CN113761479B (en) * 2021-09-15 2024-03-12 厦门熵基科技有限公司 Software authorization method, system, equipment and computer storage medium
CN113553629A (en) * 2021-09-18 2021-10-26 新大陆数字技术股份有限公司 Hardware authorization method and system

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060230433A1 (en) * 2005-03-29 2006-10-12 Invented Corporation Client device reservation system and method
CN104065621B (en) * 2013-03-21 2018-10-30 腾讯科技(深圳)有限公司 A kind of auth method of third party's service, client and system
CN103428699A (en) * 2013-07-16 2013-12-04 李锦风 Registration binding and identity authentication method based on mobile phone hardware feature information
CN104836814B (en) * 2015-05-29 2018-09-18 北京奇虎科技有限公司 Intelligent hardware high in the clouds connection control method and its corresponding device
CN105389263B (en) * 2015-12-24 2017-12-19 北京奇虎科技有限公司 Application software authority monitoring method, system and equipment
CN109150828B (en) * 2018-07-10 2021-04-13 珠海腾飞科技有限公司 Verification registration method and system
CN109101839B (en) * 2018-08-13 2021-03-23 浙江大学 Product maintenance support system based on block chain

Also Published As

Publication number Publication date
CN110768839A (en) 2020-02-07

Similar Documents

Publication Publication Date Title
CN110611685B (en) Internet site login system based on intelligent equipment monitoring and user identity recognition
CN110765149B (en) Intelligent device full life cycle monitoring query and user identity recognition binding system
CN110768839B (en) Third-party software authorization system based on intelligent equipment monitoring and user identity binding
US6954736B2 (en) System, method and computer program product for order confirmation in a supply chain management framework
CN110751303B (en) Intelligent device full life cycle monitoring query system based on cloud computing
CN107770191B (en) Enterprise financial management system with safety protection
US20030046121A1 (en) System, method and computer program product for normalizing data in a supply chain management framework
US20030069778A1 (en) System, method and computer program product for error checking in a supply chain management framework
US20030088449A1 (en) System, method and computer program product for an analysis creation interface in a supply chain management framework
CN104050401A (en) User permission management method and system
US20040193482A1 (en) System, method and computer program product for user-specific advertising in a supply chain management framework
US20030074239A1 (en) System, method and computer program product for a network-based restaurant supply chain management framework
CA2847012A1 (en) Applicant screening
US20030046089A1 (en) System, method and computer program product for an access-based revenue model involving a supply chain management framework
US20030078845A1 (en) System, method and computer program product for a distributor interface in a supply chain management framework
US20030050859A1 (en) System, method and computer program product for a catalog feature in a supply chain management framework
US20030074264A1 (en) System, method and computer program product for low-cost fulfillment in a supply chain management framework
US20030078787A1 (en) System, method and computer program product for generating revenue in a supply chain management framework
US20030088474A1 (en) System, method and computer program product for an electronics and appliances supply chain management framework
US20030074281A1 (en) System, method and computer program product for a centralized a supply chain management framework
US20030069818A1 (en) System, method and computer program product for creating contracts using a graphical user interface in a supply chain management framework
US20030078818A1 (en) System, method and computer program product for a communication framework in a supply management architecture
US20030055704A1 (en) System, method and computer program product for defining roles/responsibilities in a supply chain management framework
US20030074263A1 (en) System, method and computer program product for an office products supply chain management framework
US20030074262A1 (en) System, method and computer program product for a convenience store supply chain management framework

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant