WO2019232785A1 - 一种设备管理方法、设备管理装置及移动终端 - Google Patents

一种设备管理方法、设备管理装置及移动终端 Download PDF

Info

Publication number
WO2019232785A1
WO2019232785A1 PCT/CN2018/090439 CN2018090439W WO2019232785A1 WO 2019232785 A1 WO2019232785 A1 WO 2019232785A1 CN 2018090439 W CN2018090439 W CN 2018090439W WO 2019232785 A1 WO2019232785 A1 WO 2019232785A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared charging
charging device
operator
shared
registration information
Prior art date
Application number
PCT/CN2018/090439
Other languages
English (en)
French (fr)
Inventor
吴志勇
Original Assignee
深圳市奥星澳科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市奥星澳科技有限公司 filed Critical 深圳市奥星澳科技有限公司
Priority to CN201880000614.6A priority Critical patent/CN109076109B/zh
Priority to PCT/CN2018/090439 priority patent/WO2019232785A1/zh
Publication of WO2019232785A1 publication Critical patent/WO2019232785A1/zh

Links

Classifications

    • 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
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F15/00Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
    • G07F15/003Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity
    • G07F15/006Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity dispensed for the electrical charging of other devices than vehicles
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F17/00Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/0042Coin-freed apparatus for hiring articles; Coin-freed facilities or services for hiring of objects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/141Setup of application sessions

Definitions

  • the present application belongs to the technical field of the Internet of Things, and particularly relates to a device management method, a device management device, a mobile terminal, and a computer-readable storage medium.
  • the current shared charging concept has been popularized.
  • Shared charging devices can not only charge mobile terminals, but also electronic products such as electric vehicles.
  • manufacturers of shared charging equipment can rent or sell their shared charging equipment to individuals, and individuals as operators of shared charging equipment can earn profits through the shared charging equipment.
  • this application provides a device management method, a device management device, a mobile terminal, and a computer-readable storage medium, which can realize remote management of the shared charging device operated by an operator, simplify the management process, and improve management efficiency.
  • a first aspect of the present application provides a device management method, including:
  • the usage status sent by the shared charging device is received.
  • a second aspect of the present application provides a device management apparatus, including:
  • An obtaining unit configured to obtain a device ID of a shared charging device managed by an operator
  • a positioning unit configured to locate a device network address of the shared charging device based on the device ID
  • a connecting unit configured to establish a network connection with the shared charging device according to the network address of the device
  • the receiving unit is configured to receive a usage status sent by the shared charging device after establishing a network connection with the shared charging device.
  • a third aspect of the present application provides a mobile terminal.
  • the mobile terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor.
  • the processor executes the computer program, the processor is implemented as described above. Step by step method.
  • a fourth aspect of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the steps of the method of the first aspect above.
  • a fifth aspect of the present application provides a computer program product.
  • the computer program product includes a computer program.
  • the steps of the method of the first aspect are implemented.
  • the device ID of the shared charging device managed by the operator is first obtained, and then the device network address of the shared charging device is located based on the device ID, and then the sharing with the device is established based on the device network address. After the network connection of the charging device is established, after the network connection with the shared charging device is established, the usage status sent by the shared charging device is received.
  • the user can remotely receive and view the usage status of the shared charging device, which can realize the remote management of the shared charging device operated by the operator, simplify the management process, and improve management efficiency.
  • FIG. 1 is a schematic flowchart of an implementation of a device management method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of another implementation of a device management method according to an embodiment of the present application.
  • FIG. 3 is a structural block diagram of a device management apparatus according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a mobile terminal according to an embodiment of the present application.
  • the device management method in the embodiment of the present application includes:
  • step 101 a device ID of a shared charging device managed by an operator is acquired
  • the device ID of each shared charging device that is put into use is unique, that is, there is a one-to-one correspondence between the shared charging device and the device ID.
  • a database may be set in advance, and each time the device ID of the shared charging device is obtained, the acquired Whether the device ID has been stored in the above database, and if a device ID obtained this time has not been stored in the above database, then the device ID is stored in the above database first, and then step 102 and subsequent steps are performed; If a device ID obtained this time has been stored in the above database, it is considered that the mobile terminal has established a connection with the shared charging device corresponding to the device ID, that is, the mobile terminal can already obtain the usage status of the shared charging device, without having to Repeat step 102 and subsequent steps.
  • step 102 the device network address of the shared charging device is located based on the device ID
  • the device ID of each shared charging device that is put into use is unique, the device ID can be used to identify the shared charging device to uniquely identify a shared charging device; therefore, it can be based on The above device ID obtains various device information of the shared charging device corresponding to the device ID, including but not limited to a device network address, a device physical address, a device model, and the like.
  • the network address of the device may be an Internet Protocol address (Internet Protocol Address (IP Address) can also be a Media Access Control (Media Access Control) address, of course, it can also be another address that can uniquely express the above shared charging device, which is not limited here.
  • IP Address Internet Protocol Address
  • Media Access Control Media Access Control
  • the geographic address of the device may be the latitude and longitude of the shared charging device, or a detailed address of the shared charging device expressed in text, which is not limited herein.
  • step 103 a network connection with the shared charging device is established according to the device network address
  • the mobile terminal may establish a network connection with the shared charging device according to the device network address.
  • the network connection may be a direct network connection established between the mobile terminal and the shared charging device, or an indirect network connection established by the mobile terminal with the shared charging device through a preset server, which is not limited herein.
  • the mobile terminal may send a connection establishment request to the shared charging device. After receiving the connection establishment request, the shared charging device returns a first confirmation message to the mobile terminal. After receiving the first After the confirmation information is returned, the second confirmation information is returned to the shared charging device again. At this time, the network connection is completed.
  • a prompt message may also be output through text, ringtone, voice broadcast or vibration to remind the user that the user has currently established a new shared charging device that needs to be managed. Good connection.
  • step 104 after establishing a network connection with the shared charging device, the usage status sent by the shared charging device is received.
  • the shared charging device after the shared charging device starts a power source and establishes a network connection with the shared charging device, it can monitor and record its own usage status, and send the shared charging device to the shared charging device at a preset time. Usage of new records. For example, during the time period from time point A to time point B, the usage status during this period is recorded and recorded as usage status AB. When time point B is reached, only the usage status AB is sent to the mobile terminal without The use conditions before time point A need to be sent, because these use conditions have been sent to the mobile terminal, and there is no need to repeat sending.
  • the mobile terminal after sending the recorded usage status to the mobile terminal, the sent usage status can be deleted to avoid the storage space being occupied in large quantities.
  • the mobile terminal After receiving the above-mentioned usage status, the mobile terminal can perform analysis and recording on its own, and can also display the received usage status output to the user for viewing, which is not limited here.
  • the mobile terminal directly establishes a network connection with the shared charging device, in order to save system resources of the mobile terminal, after the mobile terminal analyzes the above usage status, if the analysis result is non-negative, the shared charging device is considered to be In normal operations, the above-mentioned usage status and corresponding analysis results can be uploaded to a preset server, and the above-mentioned usage status and corresponding analysis results can be deleted locally on the mobile terminal. If the analysis results are negative, the above sharing is considered There may be problems with the charging device. The above usage status and corresponding analysis results will be stored in the mobile terminal, and will be checked when the operator goes to the shared charging device to handle the problem.
  • the mobile terminal can obtain the device network address of the shared charging device through the device ID positioning, establish a network connection with the shared charging device, and the user can remotely receive and view the usage status of the shared charging device, which can
  • the remote management of the shared charging equipment operated by the operator is realized, the management process is simplified, and the management efficiency is improved.
  • the device management method in the embodiment of the present application includes:
  • step 201 receiving equipment operation registration information input by an operator
  • the above-mentioned device registration and operation information includes, but is not limited to, account name, account password, operator ID information, operator collection account information, and business place photos.
  • the account name may be set by the user, or may be a mobile phone number or email entered by the user, or may be associated with the user ’s Alipay, WeChat, or QQ account, which is not limited here.
  • the above-mentioned operator identity information in order to ensure that the above-mentioned user is a legitimate user, the user is also required to upload an identity card; at the same time, for the above-mentioned operator's collection account information, it should be noted that the account holder of the collection account should be the operator himself.
  • step 202 the above-mentioned equipment operation registration information is verified
  • the mobile terminal may send the device operation registration information to the server for manual verification to determine that the operator is a legitimate operator.
  • step 203 after the above-mentioned device operation registration information is verified, the device ID of the shared charging device managed by the operator is obtained.
  • step 204 locate the device network address of the shared charging device based on the device ID
  • step 205 establish a network connection with the shared charging device according to the device network address
  • step 206 after the network connection with the shared charging device is established, the usage status sent by the shared charging device is received.
  • the above steps 203, 204, 205, and 206 are the same as or similar to the above steps 101, 102, 103, and 104.
  • the above steps 101, 102, 103, and 104 refer to the related descriptions of the above steps 101, 102, 103, and 104, and are not described here To repeat.
  • a user may first register an operator account through a mobile terminal, obtain a device ID after successful registration, and obtain a device network address of the shared charging device through the device ID positioning, and establish and share the charging device.
  • users can remotely receive and view the usage status of shared charging equipment, which can realize the remote management of shared charging equipment operated by operators, simplify the management process and improve management efficiency.
  • the device management methods provided in the foregoing Embodiment 1 and Embodiment 2 may further include:
  • the shared charging device has a loaned charging device, real-time location of each of the loaned charging devices is obtained separately;
  • a hotspot map is established for the aforementioned operators to consult.
  • each of the lending charging devices can periodically or irregularly obtain the current real-time position of itself and send its real-time position.
  • the mobile terminal establishes a hot map based on the real-time location of each of the above-mentioned loaned charging devices, and can accurately know which regions of the user have a greater demand for the charging device. Based on the hot map, the operator can share for subsequent releases Make better plans for the location of your charging equipment.
  • the use status includes power consumption of the shared charging device
  • the device management method may further include:
  • a reminder message is output to remind the user to check the location of the shared charging device.
  • a power consumption threshold corresponding to each shared charging device is set, and the mobile terminal performs power consumption in the received usage status. It is detected that if the power consumption of the shared charging device is greater than the power consumption threshold, it indicates that there may be a problem in the operation of the shared charging device, and the mobile terminal may output a reminder message at this time to remind the user to check the location of the shared charging device.
  • the above reminder message may be in the form of text, ringtone, voice broadcast or vibration, which is not limited here.
  • Embodiment 3 of the present application provides a device management apparatus.
  • the above device management apparatus may be integrated in a mobile terminal.
  • the device management apparatus 300 in the embodiment of the present application includes:
  • An obtaining unit 301 configured to obtain a device ID of a shared charging device managed by an operator
  • a positioning unit 302 configured to locate a device network address of the shared charging device based on the device ID;
  • a connecting unit 303 configured to establish a network connection with the shared charging device according to the network address of the device
  • the receiving unit 304 is configured to receive a usage status sent by the shared charging device after establishing a network connection with the shared charging device.
  • the device management apparatus 300 further includes:
  • a registration information receiving unit for receiving equipment operation registration information input by an operator
  • Registration information verification unit to verify the above-mentioned equipment operation registration information
  • the obtaining unit is specifically configured to obtain the device ID of the shared charging device managed by the operator after the verification of the device operation registration information is passed.
  • the above device operation registration information includes: account name, account password, operator ID information, operator collection account information, and business place photos.
  • the device management apparatus 300 further includes:
  • a real-time location acquiring unit configured to obtain the real-time location of each of the above-mentioned lent charging devices if the shared charging device has a lent charging device;
  • a hotspot map establishing unit is configured to establish a hotspot map for the above-mentioned operators to consult based on the real-time location of each of the above-mentioned loaned charging devices.
  • the usage status includes power consumption of the shared charging device
  • the device management apparatus 300 further includes:
  • a power consumption detecting unit configured to detect whether the power consumption of the shared charging device is greater than a preset power consumption threshold
  • the reminder output unit is configured to output a reminder message if it is detected that the power consumption of the shared charging device is greater than the power consumption threshold, to remind the user to check the location of the shared charging device.
  • the device management device can obtain the device network address of the shared charging device through device ID positioning, establish a network connection with the shared charging device, and the user can remotely receive and view the usage status of the shared charging device. It can realize the remote management of the shared charging equipment operated by the operator, simplify the management process and improve the management efficiency.
  • the fourth embodiment of the present application provides a mobile terminal. Please refer to FIG. 4.
  • the mobile terminal in the embodiment of the present application includes a memory 401, one or more processors 402 (only one is shown in FIG. 4), and stored in the memory.
  • a computer program on a 401 that can run on a processor.
  • the memory 401 is used to store software programs and modules, and the processor 402 executes various functional applications and data processing by running the software programs and units stored in the memory 401 to obtain resources corresponding to the preset events.
  • the processor 402 implements the following steps by running the computer program stored in the memory 401:
  • the usage status sent by the shared charging device is received.
  • the processor 402 before obtaining the device ID of the shared charging device managed by the operator, the processor 402 also implements the following steps when running the computer program stored in the memory 401:
  • the device ID of the shared charging device managed by the acquisition operator includes:
  • the device ID of the shared charging device managed by the operator is obtained.
  • the foregoing device operation registration information includes: account name, account password, operator ID information, operator collection account information, and management Place photos.
  • the processor 402 The following steps are also implemented by running the above computer program stored in the memory 401:
  • the shared charging device has a loaned charging device, real-time location of each of the loaned charging devices is obtained separately;
  • a hotspot map is established for the aforementioned operators to consult.
  • the processor 402 also implements the following steps when running the computer program stored in the memory 401:
  • a reminder message is output to remind the user to check the location of the shared charging device.
  • the above mobile terminal may further include one or more input devices 403 (only one is shown in FIG. 4) and one or more output devices 404 (only one is shown in FIG. 4).
  • the memory 401, the processor 402, the input device 403, and the output device 404 are connected through a bus 405.
  • the processor 402 may be a central processing unit (Central Processing Unit (CPU), the processor can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (Applications) Specific Integrated Circuit (ASIC), off-the-shelf Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • CPU Central Processing Unit
  • DSPs digital signal processors
  • ASIC application-specific integrated circuits
  • FPGA off-the-shelf Programmable Gate Array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the input device 403 may include a keyboard, a touch pad, a fingerprint sensor (for collecting user's fingerprint information and fingerprint orientation information), a microphone, and the like, and the output device 404 may include a display, a speaker, and the like.
  • the memory 401 may include a read-only memory and a random access memory, and provide instructions and data to the processor 402. A part or all of the memory 401 may further include a non-volatile random access memory. For example, the memory 401 may also store information of a device type.
  • the mobile terminal can obtain the device network address of the shared charging device through the device ID positioning, establish a network connection with the shared charging device, and the user can remotely receive and view the usage status of the shared charging device, which
  • the remote management of the shared charging equipment operated by the operator is realized, the management process is simplified, and the management efficiency is improved.
  • the disclosed apparatus and method may be implemented in other ways.
  • the system embodiments described above are only schematic.
  • the division of the above modules or units is only a logical function division.
  • multiple units or components may be combined.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • the above integrated unit When the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, this application implements all or part of the processes in the method of the above embodiment, and can also be completed by a computer program instructing related hardware.
  • the above computer program can be stored in a computer-readable storage medium.
  • the computer program When executed by a processor, the steps of the foregoing method embodiments may be implemented.
  • the computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file, or some intermediate form.
  • the computer-readable storage medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a mobile hard disk, a magnetic disk, an optical disk, a computer-readable memory, and a read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signals, telecommunication signals, and software distribution media.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • electric carrier signals telecommunication signals
  • software distribution media any entity or device capable of carrying the computer program code
  • a recording medium a U disk, a mobile hard disk, a magnetic disk, an optical disk, a computer-readable memory, and a read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signals, telecommunication signals, and software distribution media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种设备管理方法、设备管理装置、移动终端及计算机可读存储介质,其中,该设备管理方法包括:获取经营者所管理的共享充电设备的设备ID;基于设备ID,定位共享充电设备的设备网络地址;根据设备网络地址,建立与共享充电设备的网络连接;在建立与共享充电设备的网络连接后,接收共享充电设备发送的使用状况。通过本申请方案,可实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。

Description

一种设备管理方法、设备管理装置及移动终端 技术领域
本申请属于物联网技术领域,尤其涉及一种设备管理方法、设备管理装置、移动终端及计算机可读存储介质。
背景技术
当前共享充电概念已经得到普及,共享充电设备不仅可以为移动终端充电,也可以为电动车等电子产品充电。为了进一步推广共享充电设备,共享充电设备的厂商可将其共享充电设备出租或出售给个人,由个人作为共享充电设备的经营者,通过该共享充电设备获取利润。
技术问题
但当前,共享充电设备的经营者在需要查看共享充电设备的使用状况时,还需要前往共享充电设备的所在地进行考察,因而,当前还无法实现经营者对所运营的共享充电设备的远程管理。
技术解决方案
有鉴于此,本申请提供了一种设备管理方法、设备管理装置、移动终端及计算机可读存储介质,可实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。
本申请的第一方面提供了一种设备管理方法,包括:
获取经营者所管理的共享充电设备的设备ID;
基于上述设备ID,定位上述共享充电设备的设备网络地址;
根据上述设备网络地址,建立与上述共享充电设备的网络连接;
在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。
本申请的第二方面提供了一种设备管理装置,包括:
获取单元,用于获取经营者所管理的共享充电设备的设备ID;
定位单元,用于基于上述设备ID,定位上述共享充电设备的设备网络地址;
连接单元,用于根据上述设备网络地址,建立与上述共享充电设备的网络连接;
接收单元,用于在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。
本申请的第三方面提供了一种移动终端,上述移动终端包括存储器、处理器以及存储在上述存储器中并可在上述处理器上运行的计算机程序,上述处理器执行上述计算机程序时实现如上第一方面的方法的步骤。
本申请的第四方面提供了一种计算机可读存储介质,上述计算机可读存储介质存储有计算机程序,上述计算机程序被处理器执行时实现如上第一方面的方法的步骤。
本申请的第五方面提供了一种计算机程序产品,上述计算机程序产品包括计算机程序,上述计算机程序被一个或多个处理器执行时实现如上述第一方面的方法的步骤。
有益效果
由上可见,通过本申请方案,首先获取经营者所管理的共享充电设备的设备ID,然后基于上述设备ID,定位上述共享充电设备的设备网络地址,接着根据上述设备网络地址,建立与上述共享充电设备的网络连接,并在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。通过本申请方案,用户可以远程接收并查看共享充电设备的使用状况,可实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。
附图说明
为了更清楚地说明本申请实施例中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的设备管理方法的一种实现流程示意图;
图2是本申请实施例提供的设备管理方法的另一种实现流程示意图;
图3是本申请实施例提供的设备管理装置的结构框图;
图4是本申请实施例提供的移动终端的示意图。
本发明的实施方式
以下描述中,为了说明而不是为了限定,提出了诸如特定系统结构、技术之类的具体细节,以便透彻理解本申请实施例。然而,本领域的技术人员应当清楚,在没有这些具体细节的其它实施例中也可以实现本申请。在其它情况中,省略对众所周知的系统、装置、电路以及方法的详细说明,以免不必要的细节妨碍本申请的描述。
为了说明本申请上述的技术方案,下面通过具体实施例来进行说明。
实施例1
下面对本申请实施例提供的一种设备管理方法进行描述,请参阅图1,本申请实施例中的设备管理方法包括:
在步骤101中,获取经营者所管理的共享充电设备的设备ID;
在本申请实施例中,每个投入使用的共享充电设备的设备ID都是唯一的,也即是说,共享充电设备与设备ID之间呈现一一对应的关系。可选地,由于可能出现一个经营者投资经营多个共享充电设备的情况,因而在本步骤中,可以预先设置一个数据库,每当获取到共享充电设备的设备ID时,分别检测本次获取到的设备ID是否已存入了上述数据库中,若本次获取到的某一设备ID还未存入上述数据库中,则将该设备ID先存入上述数据库中,再执行步骤102及后续步骤;若本次获取到的某一设备ID已存入上述数据库中,则认为移动终端已经与上述设备ID对应的共享充电设备建立连接,也即移动终端已经可以获取该共享充电设备的使用状况,无需再重复执行步骤102及后续步骤。
在步骤102中,基于上述设备ID,定位上述共享充电设备的设备网络地址;
在本申请实施例中,由于每个投入使用的共享充电设备的设备ID都是唯一的,通过该设备ID,可以对共享充电设备进行识别,用以唯一确定一共享充电设备;因而,可以基于上述设备ID,获取与该设备ID对应的共享充电设备的各项设备信息,包括但不限于设备网络地址、设备物理地址、设备型号等。其中,上述设备网络地址可以是互联网协议地址(Internet Protocol Address,IP Address),也可以是媒体访问控制(Media Access Control)地址,当然,也可以是其它能够唯一表达上述共享充电设备的地址,此处不作限定。上述设备地理地址,可以是上述共享充电设备的经纬度,也可以是用文字表达的上述共享充电设备的详细地址,此处不作限定。
在步骤103中,根据上述设备网络地址,建立与上述共享充电设备的网络连接;
在本申请实施例中,移动终端可以根据上述设备网络地址,建立与上述共享充电设备的网络连接。上述网络连接可以是移动终端与上述共享充电设备建立直接的网络连接,也可以是上述移动终端通过一预设的服务器与上述共享充电设备建立间接的网络连接,此处不作限定。具体地,可以由上述移动终端发送建立连接请求至上述共享充电设备处,上述共享充电设备接收到上述建立连接请求后,返回第一确认信息至上述移动终端处,上述移动终端在接收到上述第一确认信息后再次返回第二确认信息至上述共享充电设备处,此时,上述网络连接才建立完成。可选地,在建立与上述共享充电设备的网络连接后,还可以通过文字、铃声、语音播报或者震动的方式输出一提示信息,以提醒用户当前已与所需要管理的新的共享充电设备建立好连接。
在步骤104中,在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。
在本申请实施例中,上述共享充电设备在启动电源并与上述共享充电设备建立网络连接后,可以对自身的使用状况进行监测及记录,并每隔预设的时间向上述共享充电设备发送所新记录的使用状况。例如,在时间点A至时间点B的时间段内,记录了这一期间内的使用状况,记作使用状况AB,则在到达时间点B时,仅向移动终端发送使用状况AB,而不需要发送在时间点A之前的使用状况,因为这些使用状况已经发送至移动终端处了,不再需要重复发送。可选地,由于共享充电设备的存储空间有限,每次将记录的使用状况发送至移动终端后,可将已发送的使用状况删除,避免存储空间被大量占用。而移动终端在接收到上述使用状况后,可以自主进行分析与记录,也可以同时将接收到的使用状况输出显示给用户查看,此处不作限定。可选地,若移动终端直接与上述共享充电设备建立网络连接,则为了节约移动终端的系统资源,可以在移动终端分析完上述使用状况后,若分析结果是非负面的,则认为上述共享充电设备在正常运营中,可以将上述使用状况及对应的分析结果上传至一预设的服务器中,在移动终端的本地删除上述使用状况及对应的分析结果,若分析结果是负面的,则认为上述共享充电设备可能存在问题,上述使用状况及对应的分析结果将保存在移动终端中,待经营者前往共享充电设备处处理问题时进行查阅。
由上可见,通过本申请实施例,移动终端可以通过设备ID定位得到共享充电设备的设备网络地址,建立与共享充电设备的网络连接,用户即可远程接收并查看共享充电设备的使用状况,能够实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。
应理解,上述实施例中各步骤的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
实施例2
在上述实施例一的基础上,下面对本申请实施例提供的另一种设备管理方法进行描述,请参阅图2,本申请实施例中的设备管理方法包括:
在步骤201中,接收经营者输入的设备经营注册信息;
在本申请实施例中,上述设备注册经营信息包括但不限于账号名称、账号密码、经营者身份证信息、经营者收款帐户信息、经营场所照片等。其中, 上述账号名称可以是用户自行设置的,也可以是用户所输入的手机号或者邮箱,或者,还可以是与用户的支付宝、微信、QQ账号关联的,此处不作限定。对于上述经营者身份信息,为了保证上述用户是合法用户,还需要用户上传身份证;同时,对于上述经营者收款账户信息,需注意该收款账户的开户人应该是经营者本人。
在步骤202中,对上述设备经营注册信息进行验证;
在本申请实施例中,移动终端可以将上述设备经营注册信息发送至上述服务器进行人工验证,以确定该经营者为合法经营者。
在步骤203中,在上述上述设备经营注册信息验证通过后,获取经营者所管理的共享充电设备的设备ID。
在步骤204中,基于上述设备ID,定位上述共享充电设备的设备网络地址;
在步骤205中,根据上述设备网络地址,建立与上述共享充电设备的网络连接;
在步骤206中,在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。
在本申请实施例中,上述步骤203、204、205、206与上述步骤101、102、103、104相同或相似,具体可参见上述步骤101、102、103、104的相关描述,在此不再赘述。
由上可见,通过本申请实施例,用户可先通过移动终端注册经营者账号,并在注册成功后获取设备ID,并通过设备ID定位得到共享充电设备的设备网络地址,建立与共享充电设备的网络连接,用户即可远程接收并查看共享充电设备的使用状况,能够实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。
可选地,在上述实施例一及上述实施例二所提供的设备管理方法中,还可以包括:
若上述共享充电设备存在已出借的充电设备,则分别获取各个上述已出借的充电设备的实时位置;
基于各个上述已出借的充电设备的实时位置,建立热点地图供上述经营者查阅。
其中,若上述共享充电设备是通过出借充电设备的方式运营,例如,出借充电宝,则每个出借的充电设备都可以周期性或不定时获取当前自身的实时位置,并将自身的实时位置发送至移动终端中;移动终端基于各个上述已出借的充电设备的实时位置,建立热点地图,可以准确获知哪些区域的用户对充电设备的需求较大,经营者基于该热点地图,可以为后续投放共享充电设备的地点作出更好的规划。
可选地,在上述实施例一及上述实施例二所提供的设备管理方法中,上述使用状况包括上述共享充电设备的功耗,上述设备管理方法还可以包括:
检测上述共享充电设备的功耗是否大于预设的功耗阈值;
若检测到上述共享充电设备的功耗大于上述功耗阈值,则输出提醒消息,以提醒用户前往上述共享充电设备位置处查看。
其中,不同型号的共享充电设备有其功耗上限值,基于该功耗上限值,设置每台共享充电设备所对应的功耗阈值,移动终端对接收到的使用状况中的功耗进行检测,若检测到上述共享充电设备的功耗大于上述功耗阈值,则表明该共享充电设备的运行可能出现问题,移动终端此时可以输出提醒消息,以提醒用户前往上述共享充电设备位置处查看。上述提醒消息可以是文字、铃声、语音播报或震动等形式,此处不作限定。
应理解,上述实施例中各步骤的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
实施例3
本申请实施例三提供了一种设备管理装置,上述设备管理装置可集成于移动终端中,如图3所示,本申请实施例中的设备管理装置300包括:
获取单元301,用于获取经营者所管理的共享充电设备的设备ID;
定位单元302,用于基于上述设备ID,定位上述共享充电设备的设备网络地址;
连接单元303,用于根据上述设备网络地址,建立与上述共享充电设备的网络连接;
接收单元304,用于在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。
可选地,上述设备管理装置300还包括:
注册信息接收单元,用于接收经营者输入的设备经营注册信息;
注册信息验证单元,对上述设备经营注册信息进行验证;
上述获取单元,具体用于在上述上述设备经营注册信息验证通过后,获取经营者所管理的共享充电设备的设备ID。
可选地,上述设备经营注册信息包括:账号名称、账号密码、经营者身份证信息、经营者收款帐户信息、经营场所照片。
可选地,上述设备管理装置300还包括:
实时位置获取单元,用于若上述共享充电设备存在已出借的充电设备,则分别获取各个上述已出借的充电设备的实时位置;
热点地图建立单元,用于基于各个上述已出借的充电设备的实时位置,建立热点地图供上述经营者查阅。
可选地,上述使用状况包括上述共享充电设备的功耗,上述设备管理装置300还包括:
功耗检测单元,用于检测上述共享充电设备的功耗是否大于预设的功耗阈值;
提醒输出单元,用于若检测到上述共享充电设备的功耗大于上述功耗阈值,则输出提醒消息,以提醒用户前往上述共享充电设备位置处查看。
由上可见,通过本申请实施例,设备管理装置可以通过设备ID定位得到共享充电设备的设备网络地址,建立与共享充电设备的网络连接,用户即可远程接收并查看共享充电设备的使用状况,能够实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。
实施例4
本申请实施例四提供了一种移动终端,请参阅图4,本申请实施例中的移动终端包括:存储器401,一个或多个处理器402(图4中仅示出一个)及存储在存储器401上并可在处理器上运行的计算机程序。其中:存储器401用于存储软件程序以及模块,处理器402通过运行存储在存储器401的软件程序以及单元,从而执行各种功能应用以及数据处理,以获取上述预设事件对应的资源。具体地,处理器402通过运行存储在存储器401的上述计算机程序时实现以下步骤:
获取经营者所管理的共享充电设备的设备ID;
基于上述设备ID,定位上述共享充电设备的设备网络地址;
根据上述设备网络地址,建立与上述共享充电设备的网络连接;
在建立与上述共享充电设备的网络连接后,接收上述共享充电设备发送的使用状况。
假设上述为第一种可能的实施方式,则在第一种可能的实施方式作为基础而提供的第二种可能的实施方式中,在上述获取经营者所管理的共享充电设备的设备ID之前,处理器402通过运行存储在存储器401的上述计算机程序时还实现以下步骤:
接收经营者输入的设备经营注册信息;
对上述设备经营注册信息进行验证;
上述获取经营者所管理的共享充电设备的设备ID,包括:
在上述上述设备经营注册信息验证通过后,获取经营者所管理的共享充电设备的设备ID。
在上述第二种可能的实施方式作为基础而提供的第三种可能的实施方式中,上述设备经营注册信息包括:账号名称、账号密码、经营者身份证信息、经营者收款帐户信息、经营场所照片。
在上述第一种可能的实施方式作为基础,或者上述第二种可能的实施方式作为基础,或者上述第三种可能的实施方式作为基础而提供的第四种可能的实施方式中,处理器402通过运行存储在存储器401的上述计算机程序时还实现以下步骤:
若上述共享充电设备存在已出借的充电设备,则分别获取各个上述已出借的充电设备的实时位置;
基于各个上述已出借的充电设备的实时位置,建立热点地图供上述经营者查阅。
在上述第一种可能的实施方式作为基础,或者上述第二种可能的实施方式作为基础,或者上述第三种可能的实施方式作为基础而提供的第五种可能的实施方式中,上述使用状况包括上述共享充电设备的功耗,则处理器402通过运行存储在存储器401的上述计算机程序时还实现以下步骤:
检测上述共享充电设备的功耗是否大于预设的功耗阈值;
若检测到上述共享充电设备的功耗大于上述功耗阈值,则输出提醒消息,以提醒用户前往上述共享充电设备位置处查看。
进一步,如图4所示,上述移动终端还可包括:一个或多个输入设备403(图4中仅示出一个)和一个或多个输出设备404(图4中仅示出一个)。存储器401、处理器402、输入设备403和输出设备404通过总线405连接。
应当理解,在本申请实施例中,所称处理器402可以是中央处理单元(Central Processing Unit,CPU),该处理器还可以是其他通用处理器、数字信号处理器 (Digital Signal Processor,DSP)、专用集成电路 (Application Specific Integrated Circuit,ASIC)、现成可编程门阵列 (Field-Programmable Gate Array,FPGA) 或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
输入设备403可以包括键盘、触控板、指纹采传感器(用于采集用户的指纹信息和指纹的方向信息)、麦克风等,输出设备404可以包括显示器、扬声器等。
存储器401可以包括只读存储器和随机存取存储器,并向处理器402 提供指令和数据。存储器 401的一部分或全部还可以包括非易失性随机存取存储器。例如,存储器401还可以存储设备类型的信息。
由上可见,通过本申请实施例,移动终端可以通过设备ID定位得到共享充电设备的设备网络地址,建立与共享充电设备的网络连接,用户即可远程接收并查看共享充电设备的使用状况,能够实现经营者对所运营的共享充电设备的远程管理,简化管理过程,提升管理效率。
所属领域的技术人员可以清楚地了解到,为了描述的方便和简洁,仅以上述各功能单元、模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能单元、模块完成,即将上述装置的内部结构划分成不同的功能单元或模块,以完成以上描述的全部或者部分功能。实施例中的各功能单元、模块可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中,上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。另外,各功能单元、模块的具体名称也只是为了便于相互区分,并不用于限制本申请的保护范围。上述系统中单元、模块的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在上述实施例中,对各个实施例的描述都各有侧重,某个实施例中没有详述或记载的部分,可以参见其它实施例的相关描述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者外部设备软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
在本申请所提供的实施例中,应该理解到,所揭露的装置和方法,可以通过其它的方式实现。例如,以上所描述的系统实施例仅仅是示意性的,例如,上述模块或单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通讯连接可以是通过一些接口,装置或单元的间接耦合或通讯连接,可以是电性,机械或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
上述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读存储介质中。基于这样的理解,本申请实现上述实施例方法中的全部或部分流程,也可以通过计算机程序来指令相关的硬件来完成,上述的计算机程序可存储于一计算机可读存储介质中,该计算机程序在被处理器执行时,可实现上述各个方法实施例的步骤。其中,上述计算机程序包括计算机程序代码,上述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。上述计算机可读存储介质可以包括:能够携带上述计算机程序代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机可读存储器、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是,上述计算机可读存储介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减,例如在某些司法管辖区,根据立法和专利实践,计算机可读存储介质不包括是电载波信号和电信信号。
以上上述实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围,均应包含在本申请的保护范围之内。

Claims (10)

  1. 一种设备管理方法,其特征在于,包括:
    获取经营者所管理的共享充电设备的设备ID;
    基于所述设备ID,定位所述共享充电设备的设备网络地址;
    根据所述设备网络地址,建立与所述共享充电设备的网络连接;
    在建立与所述共享充电设备的网络连接后,接收所述共享充电设备发送的使用状况。
  2. 如权利要求1所述的设备管理方法,其特征在于,在所述获取经营者所管理的共享充电设备的设备ID之前,还包括:
    接收经营者输入的设备经营注册信息;
    对所述设备经营注册信息进行验证;
    所述获取经营者所管理的共享充电设备的设备ID,包括:
    在所述所述设备经营注册信息验证通过后,获取经营者所管理的共享充电设备的设备ID。
  3. 如权利要求2所述的设备管理方法,其特征在于,所述设备经营注册信息包括:账号名称、账号密码、经营者身份证信息、经营者收款帐户信息、经营场所照片。
  4. 如权利要求1至3任一项所述的设备管理方法,其特征在于,所述设备管理方法还包括:
    若所述共享充电设备存在已出借的充电设备,则分别获取各个所述已出借的充电设备的实时位置;
    基于各个所述已出借的充电设备的实时位置,建立热点地图供所述经营者查阅。
  5. 如权利要求1至3任一项所述的设备管理方法,其特征在于,所述使用状况包括所述共享充电设备的功耗,则所述设备管理方法还包括:
    检测所述共享充电设备的功耗是否大于预设的功耗阈值;
    若检测到所述共享充电设备的功耗大于所述功耗阈值,则输出提醒消息,以提醒用户前往所述共享充电设备位置处查看。
  6. 一种设备管理装置,其特征在于,包括:
    获取单元,用于获取经营者所管理的共享充电设备的设备ID;
    定位单元,用于基于所述设备ID,定位所述共享充电设备的设备网络地址;
    连接单元,用于根据所述设备网络地址,建立与所述共享充电设备的网络连接;
    接收单元,用于在建立与所述共享充电设备的网络连接后,接收所述共享充电设备发送的使用状况。
  7. 如权利要求6所述的设备管理装置,其特征在于,所述设备管理装置还包括:
    注册信息接收单元,用于接收经营者输入的设备经营注册信息;
    注册信息验证单元,对所述设备经营注册信息进行验证;
    所述获取单元,具体用于在所述所述设备经营注册信息验证通过后,获取经营者所管理的共享充电设备的设备ID。
  8. 如权利要求6或7所述的设备管理装置,其特征在于,所述设备管理装置还包括:
    实时位置获取单元,用于若所述共享充电设备存在已出借的充电设备,则分别获取各个所述已出借的充电设备的实时位置;
    热点地图建立单元,用于基于各个所述已出借的充电设备的实时位置,建立热点地图供所述经营者查阅。
  9. 一种移动终端,包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序,其特征在于,所述处理器执行所述计算机程序时实现如权利要求1至5任一项所述方法的步骤。
  10. 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求1至5任一项所述方法的步骤。
PCT/CN2018/090439 2018-06-08 2018-06-08 一种设备管理方法、设备管理装置及移动终端 WO2019232785A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880000614.6A CN109076109B (zh) 2018-06-08 2018-06-08 一种设备管理方法、设备管理装置及移动终端
PCT/CN2018/090439 WO2019232785A1 (zh) 2018-06-08 2018-06-08 一种设备管理方法、设备管理装置及移动终端

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/090439 WO2019232785A1 (zh) 2018-06-08 2018-06-08 一种设备管理方法、设备管理装置及移动终端

Publications (1)

Publication Number Publication Date
WO2019232785A1 true WO2019232785A1 (zh) 2019-12-12

Family

ID=64789417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090439 WO2019232785A1 (zh) 2018-06-08 2018-06-08 一种设备管理方法、设备管理装置及移动终端

Country Status (2)

Country Link
CN (1) CN109076109B (zh)
WO (1) WO2019232785A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106910284A (zh) * 2017-02-24 2017-06-30 武汉浩宏科技有限公司 一种基于saas云平台的充电桩管理系统
CN107370824A (zh) * 2017-08-16 2017-11-21 扈传平 共享充电宝及共享充电宝信息交互方法
CN107393178A (zh) * 2017-07-21 2017-11-24 深圳市威泰能源有限公司 移动电源、移动电源系统、共享请求方法、智能终端和存储介质
CN107680280A (zh) * 2017-10-10 2018-02-09 左立杰 一种共享充电宝方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106910284A (zh) * 2017-02-24 2017-06-30 武汉浩宏科技有限公司 一种基于saas云平台的充电桩管理系统
CN107393178A (zh) * 2017-07-21 2017-11-24 深圳市威泰能源有限公司 移动电源、移动电源系统、共享请求方法、智能终端和存储介质
CN107370824A (zh) * 2017-08-16 2017-11-21 扈传平 共享充电宝及共享充电宝信息交互方法
CN107680280A (zh) * 2017-10-10 2018-02-09 左立杰 一种共享充电宝方法

Also Published As

Publication number Publication date
CN109076109A (zh) 2018-12-21
CN109076109B (zh) 2020-05-15

Similar Documents

Publication Publication Date Title
US10637668B2 (en) Authentication method, system and equipment
CN111008839B (zh) 资源转移数据管理方法、装置及存储介质
TWI770146B (zh) 管理裝置、管理系統、車輛以及記錄介質
TWI757495B (zh) 線下資訊推送方法和裝置
CN104468463B (zh) 验证方法、装置和系统
US9117191B2 (en) Automatic device inventory management for different types of devices
WO2017020654A1 (zh) 无线网络接入方法和装置
WO2019033979A1 (zh) 智能播报方法和装置
CN104168269B (zh) 安全连接建立方法、装置及系统
CN108156268A (zh) 设备标识的获取方法及服务器、终端设备
JP2018532301A (ja) 本人認証方法及び装置
TW201516914A (zh) 一種安全支付方法及相關設備、系統
US20160335675A1 (en) Binding social account interactions to a master agnostic identity
EP3332371A1 (en) Method and apparatus for risk management based on aggregated information from multiple payment networks while maintaining anonymity of user
CN105516258A (zh) 信息交互系统、方法及装置
CN108234124B (zh) 身份验证方法、装置与系统
US9467841B2 (en) Information processing apparatus, wireless communication apparatus, and communication system
CN105337974A (zh) 账号授权方法、账号登录方法、账号授权装置及客户端
US20140164258A1 (en) Mobile station apparatus and communication method thereof
CN107423099B (zh) 键码烧写方法、服务器、终端、键码烧写系统及存储介质
KR20190087206A (ko) 약전계 환경에서 콜 연속성을 제공하는 전자 장치 및 제어 방법
KR20130064217A (ko) 장치 대 장치서비스를 제공하기 위한 제어모듈시스템 및 방법
CN111598162A (zh) 一种黄牛风险监测方法、终端设备和存储介质
US10884470B2 (en) Method and server for managing power supply devices
US20180176781A1 (en) Method and device for managing wireless access point

Legal Events

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

Ref document number: 18921973

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18921973

Country of ref document: EP

Kind code of ref document: A1