WO2015154690A1

WO2015154690A1 - Charging socket and mobile terminal processing method based on charging socket

Info

Publication number: WO2015154690A1
Application number: PCT/CN2015/076153
Authority: WO
Inventors: Lunyao CHEN; Yijun Li; Dongxiong SHEN
Original assignee: Tencent Technology (Shenzhen) Company Limited
Priority date: 2014-04-09
Filing date: 2015-04-09
Publication date: 2015-10-15
Also published as: CN104980564A

Abstract

The present disclosure provides a charging socket and a mobile terminal processing method based on the charging socket. The mobile terminal processing method includes: detecting whether a charging socket is connected to a mobile terminal; detecting a system type of the mobile terminal if the charging socket is connected to the mobile terminal; performing a processing operation on the mobile terminal according to the system type of the mobile terminal and a preset to-be-processed item, where the processing operation includes a data operation and a charging operation on the mobile terminal. According to the charging socket and the mobile terminal processing method based on the charging socket in the present disclosure, a charging socket of a mobile terminal performs a processing operation on the mobile terminal, which solves a technical problem that an existing charging socket cannot automatically manage a mobile terminal, and thus affects operation efficiency of a user.

Description

CHARGING SOCKET AND MOBILE TERMINAL PROCESSING METHOD BASED ON CHARGING SOCKET

FIELD OF THE TECHNOLOGY

The present disclosure relates to the field of mobile terminal processing, and in particular, to a charging socket and a mobile terminal processing method based on the charging socket.

BACKGROUND OF THE DISCLOSURE

With the astounding advancement of mobile Internet technologies and the rapid development of services based on the mobile Internet, the number of netizens using mobile terminals increases sharply. Users use mobile terminals for entertainment and communication, which bring great convenience to life. In this way, a mobile terminal has become an essential device of a user.

However, when a user installs an application or updates an application, the user needs to install or update a corresponding application by using a mobile terminal, or the user installs or updates an application in a mobile terminal by using a computer. In this way, for installation or update of an application, a user needs to perform an operation on a mobile terminal or perform an operation on a mobile terminal by using a computer, which affects operation efficiency of the user； moreover, if the user forgets to update the application in time, the user cannot use the application in time because a version of the application is excessively low.

SUMMARY

Embodiments of the present invention provide a charging socket that can automatically perform a processing operation on a mobile terminal, so as to solve a technical problem that an existing mobile terminal processing method cannot be used to automatically manage a mobile terminal, and thus affects operation efficiency of a user.

Embodiments of the present invention further provide a mobile terminal processing method that can be used to automatically perform a processing operation on a mobile terminal, so as to solve a technical problem that an existing mobile terminal processing apparatus cannot automatically manage a mobile terminal, and thus affects operation efficiency of a user.

In order to solve the foregoing problems, the present disclosure provides the following technical solutions:

An embodiment of the present invention provides a charging socket, including:

at least one data interface, configured to connect to a mobile terminal；

a development board, including a general purpose input/output (GIPO) , configured to perform a processing operation on the mobile terminal connected to the data interface； and

a power supply module, configured to supply power to the development board and the data interface,

the at least one data interface being connected to the development board, and the power supply module being separately connected to the at least one data interface and the development board.

An embodiment of the present invention further provides a mobile terminal processing method based on the charging socket, including:

detecting, by the charging socket, whether the charging socket is connected to a mobile terminal；

detecting, by the charging socket, a system type of the mobile terminal if the charging socket is connected to the mobile terminal； and

performing, by the charging socket, a processing operation on the mobile terminal according to the system type of the mobile terminal and a preset to-be-processed item,

the processing operation including a data operation and a charging operation on the mobile terminal.

Compared with a mobile terminal processing method of an existing technology, according to the charging socket and the mobile terminal processing method based on the charging socket in the present disclosure, a charging socket of a mobile terminal performs an automatic processing operation on the mobile terminal, which solves a technical problem that an existing charging socket cannot automatically manage a mobile terminal, and thus affects operation efficiency of a user.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic structural diagram of a first preferred embodiment of a mobile terminal processing apparatus according to the present disclosure；

FIG. 2 is a flowchart of a first preferred embodiment of a mobile terminal processing method according to the present disclosure；

FIG. 3 is a schematic structural diagram of a second preferred embodiment of a mobile terminal processing apparatus according to the present disclosure；

FIG. 4 is a flowchart of a second preferred embodiment of a mobile terminal processing method according to the present disclosure；

FIG. 5 is a schematic structural diagram of a preferred embodiment of a charging socket in a mobile terminal processing method according to the present disclosure； and

FIG. 6 is a flowchart of use of a specific embodiment of a charging socket in a mobile terminal processing method according to the present disclosure.

DESCRIPTION OF EMBODIMENTS

Referring to the drawings, same component symbols represent same components. A principle of the present disclosure is described by using examples in which the present disclosure is implemented in proper computing environments. The following descriptions are specific embodiments of the present disclosure based on the examples, and should not be construed as a limitation to other specific embodiments of the present invention that are not described herein in detail.

In the description that follows, the specific embodiments of the present disclosure will be described with reference to steps and symbolic representations of operations that are performed by one or more computers, unless indicated otherwise. As such, it will be understood that such steps and operations, which are at times referred to as being computer-executed, include the manipulation by the processing unit of the computer of electrical signals representing data in a structured form. This manipulation transforms the data or maintains it at locations in the memory system of the computer, which reconfigures or otherwise alters the operation of the computer in a manner well understood by those skilled in the art. The data structures where data is maintained are physical locations of the memory that have particular properties defined by the format of the data. However, while the principle of the present disclosure is being described in the foregoing context, it is not meant to be limiting as those of skill in the art will appreciate that various of the steps and operation described hereinafter may also be implemented in hardware.

The terms "component" , "module" , "system" , "interface" , "process" and the like used in this application are generally intended to refer to computer-related entities: hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running in a processor, a processor, an object, an executable application, an executed thread, a program and/or a computer. According to the drawings, both an application running on a controller and the controller may be components. One or more components may exist in an executed process and/or thread, and the component may be located in a computer and/or distributed between two or more computers.

Moreover, a subject required to be protected may be implemented by using standard programming and/or an engineering technology to produce software, firmware, hardware, or any other combination thereof, to control a computer to implement a method, an apparatus, or an article of manufacture of the disclosed subject. The term "article of manufacture" used in the specification is intended to encompass a computer program accessible from any computer-readable device, carrier, or medium. Certainly, a person skilled in the art may be aware that modifications may be performed on the configuration without departing from the scope and spirit of the subject required to be protected.

The specification provides various operations of the embodiments. In one embodiment, the one or more operations may constitute one or more computer-readable instructions stored in the computer-readable media, and when the computer-readable instruction is executed by an electronic device, a calculation device is enabled to perform the operation. Description of an order of some or all operations shall not be construed as implying that these operations must be order-related. A person skilled in the art understands a replaceable order having benefits of the specification. In addition, it should be understood that, not all operations must exist in each embodiment provided in the specification.

Moreover, the word "preferred" used in the specification means serving as an instance, an example, or an illustration. Any aspect or design described as "preferred" in the specification is not necessarily be construed as advantageous over other aspects or designs. Rather, the word "preferred" is used to put forward a concept in a specific manner. For example, the term "or" used in this application is intended to mean an inclusive "or" rather than an exclusive "or" . That is, unless specified otherwise or clear from the context, "X uses A or B" refers to any of natural inclusive permutations. That is, if X uses A, X uses B, or X uses both A and B, "X uses A or B" is satisfied in any one of the foregoing examples.

Moreover, although the present disclosure is shown and described by using one or more implementation manners, a person skilled in the art may conceive equivalent variations and modifications based on reading and understanding of the specification and the accompany drawings. The present disclosure includes all such variations and modifications, which is only limited by the scope of the appended claims. In particular regard to the various functions performed by the foregoing components (such as elements and resources) , terms used to describe such components are intended to correspond to any component (unless indicated otherwise) performing specified functions of the components (for example, the components are equivalent in functions) , even though structures of the functions are not equivalent to the disclosed structures of functions in the exemplary implementation manners in the present disclosure shown in the specification. In addition, although specific features of the present disclosure are disclosed with respect to only one of several implementation manners, the features may be combined with one or more other features of other implementation manners that are desirable for and advantageous to a given or specific application. Moreover, for the terms "include" , "have" , "contain" or variations thereof being used in specific implementation manners or claims, the terms are intended to be inclusive in a similar manner to that of the term "comprise" .

Referring to FIG. 1, FIG. 1 is a schematic structural diagram of a first preferred embodiment of a mobile terminal processing apparatus according to the present disclosure. The mobile terminal processing apparatus 10 in this preferred embodiment may be disposed in another electronic device, for example, disposed in an electronic charging socket, and can automatically perform a processing operation on a mobile terminal 14 while charging the mobile terminal 14.

The mobile terminal processing apparatus 10 in this preferred embodiment includes a connection detection module 11, a system type detection module 12, and an automatic management module 13. The connection detection module 11 is configured to detect whether the mobile terminal processing apparatus 10 is connected to the mobile terminal 14. The system type detection module 12 is configured to detect a system type of the mobile terminal 14 if the connection detection module 11 detects that the mobile terminal processing apparatus 10 is connected to the mobile terminal 14. The automatic management module 13 is configured to perform an automatic processing operation on the mobile terminal 14 according to the system type of the mobile terminal 14 and a preset to-be-processed item 15. The automatic processing operation includes a data operation (such as a data backup operation, a file cleaning operation, an application update operation, and a virus scanning and removal operation) and a charging operation on the mobile terminal.

The system type of the mobile terminal 14 refers to an operating system installed in the mobile terminal 14. In this preferred embodiment, the operating system includes an Android system and an Apple system, but actually the operating system includes, but is not limited to, the Android system and the Apple system.

The preset to-be-processed item 15 refers to advance setting by a user on an item and a parameter of the processing operation, for example, setting of content (a contact, a short messaging service message, and the like) of data backup, a type of a cleaned file in the file cleaning operation, a virus scanning and removal time, and a antivirus database. In this way, the automatic management module 13 may perform the automatic processing operation on the mobile terminal 14 according to the preset to-be-processed item.

When the mobile terminal processing apparatus 10 in this preferred embodiment is used, the user connects the mobile terminal 14 and the mobile terminal processing apparatus 10 by using a connection cable. For different interfaces of mobile terminals 14, connection between the mobile terminal 14 and the mobile terminal processing apparatus 10 can be implemented by using different connection cables. The connection detection module 11 of the mobile terminal processing apparatus 10 detects the connection to the mobile terminal 14.

Then, the system type detection module 12 detects a system type of the mobile terminal 14, such as an Android system of the mobile terminal 14 or an Apple system of the mobile terminal 14.

Finally, the automatic management module 13 selects a corresponding preset to-be-processed item 15 according to the system type, which is detected by the system type detection module 12, of the mobile terminal 14, and performs a data backup operation, a file cleaning operation, an application update operation, a virus scanning and removal operation, a charging operation, or the like on the mobile terminal 14.

In this way, the process of the processing operation by the mobile terminal processing apparatus 10 in this preferred embodiment is completed.

The mobile terminal processing apparatus in this preferred embodiment is disposed in a corresponding electronic device (such as a charging socket) , and an automatic processing operation is performed on a mobile terminal by using the electronic device, which improves efficiency of a processing operation on the mobile terminal by a user.

Referring to FIG. 1 and FIG. 2, FIG. 2 is a flowchart of a first preferred embodiment of a mobile terminal processing method according to the present disclosure. The mobile terminal processing method in this preferred embodiment can be performed by using the first preferred embodiment of the mobile terminal processing apparatus, and includes:

Step S201: A charging socket detects a connection to a mobile terminal.

Step S202: The charging socket determines whether the charging socket is connected to the mobile terminal. If the charging socket is connected to the mobile terminal, perform step S203； if the charging socket is not connected to the mobile terminal, go back to step S201 to continue to detect a connection to the mobile terminal.

Step S203: The charging socket detects a system type of the mobile terminal.

Step S204: The charging socket performs an automatic processing operation on the mobile terminal according to the system type of the mobile terminal and a preset to-be-processed item.

The mobile terminal processing method in this preferred embodiment is ended by step S204.

A specific process of the steps in the mobile terminal processing method in this preferred embodiment is described below in detail.

In step S201, a user connects a mobile terminal 14 and a mobile terminal processing apparatus 10 (the charging socket) by using a connection cable. For different interfaces of mobile terminals 14, connection between the mobile terminals 14 and the mobile terminal processing apparatus 10 can be implemented by using different connection cables. A connection detection module 11 of the mobile terminal processing apparatus 10 detects whether the mobile terminal processing apparatus 10 is connected to the mobile terminal 14. Then, step S202 is performed.

In step S202, if the connection detection module 11 detects that the mobile terminal processing apparatus 10 is connected to the mobile terminal 14, step S203 is performed. If the connection detection module 11 does not detect that the mobile terminal processing apparatus 10 is connected to the mobile terminal 14, go back to step S201, so that the connection detection module 11 continues to detect a connection between the mobile terminal processing apparatus 10 and the mobile terminal 14.

In step S203, a system type detection module 12 detects a system type of the mobile terminal 14, such as an Android system of the mobile terminal 14 or an Apple system of the mobile terminal 14. Then, step S204 is performed.

In step S204, an automatic management module 13 selects a corresponding preset to-be-processed item 15 according to the system type, which is detected by the system type detection module 12, of the mobile terminal 14, and performs a data backup operation, a file cleaning operation, an application update operation, a virus scanning and removal operation, a charging operation, or the like on the mobile terminal 14.

In this way, the process of the processing operation in the mobile terminal processing method in this preferred embodiment is completed.

According to the mobile terminal processing method in this preferred embodiment, an automatic processing operation is performed on a mobile terminal by using an electronic device (such as a charging socket) , which improves efficiency of a processing operation on the mobile terminal by a user.

Referring to FIG. 3, FIG. 3 is a schematic structural diagram of a second preferred embodiment of a mobile terminal processing apparatus according to the present disclosure. The mobile terminal processing apparatus 30 in this preferred embodiment may be disposed in another electronic device, for example, disposed in an electronic charging socket, and can automatically perform a processing operation on a mobile terminal 34 while charging the mobile terminal 34.

The mobile terminal processing apparatus 30 in this preferred embodiment includes a connection detection module 31, a system type detection module 32, and an automatic management module 33. Based on the first preferred embodiment of the mobile terminal processing apparatus 10, the system type detection module 32 includes a vender ID acquiring unit 321 and a system type determining unit 322, where the vender ID acquiring unit 321 is configured to acquire a vender ID of the mobile terminal 34, and the system type determining unit 322 is configured to determine a system type of the mobile terminal 34 according to the vender ID of the mobile terminal 34.

When the mobile terminal processing apparatus 30 in this preferred embodiment is used, a user connects the mobile terminal 34 and the mobile terminal processing apparatus 30 by using a connection cable. For different interfaces of mobile terminals 34, connection between the mobile terminals 34 and the mobile terminal processing apparatus 30 can be implemented by using different connection cables. The connection detection module 31 of the mobile terminal processing apparatus 30 detects the connection to the mobile terminal 34.

Then, the vender ID acquiring unit 321 of the system type detection module 32 acquires the vender ID of the mobile terminal 34, the system type determining unit 322 of the system type detection module 32 determines the system type of the mobile terminal 34 according to the vender ID, which is acquired by the vender ID acquiring unit 321, of the mobile terminal 34, for example, a vender ID of an Apple system is 0x05c, and then may further acquire a specific manufacturer of the mobile terminal 34 according to a product ID.

Finally, the automatic management module 33 selects a corresponding preset to-be-processed item 35 according to the system type, which is detected by the system type detection module 32, of the mobile terminal 34, and performs an automatic processing operation on the mobile terminal.

If the system type detection module 32 detects that the system type of the mobile terminal 34 is an Android system, the automatic management module 33 detects a system state of the mobile terminal 34. If the system state of the mobile terminal 34 is a storage state, the automatic management module 33 performs the automatic processing operation on the mobile terminal 34 according to the preset to-be-processed item 35. If the system state of the mobile terminal 34 is a non-storage state, the automatic management module 33 only performs a charging operation on the mobile terminal 34. Herein, the automatic management module 33 preferably performs the automatic processing operation on the mobile terminal 34 by using an Android debug bridge (adb) .

Because the Android system of the mobile terminal 34 has a storage state in which a system file can be accessed and a non-storage state in which a system file cannot be accessed, if the Android system is in a storage state, the automatic management module 33 may perform processing operations, such as data backup, file cleaning, application update, virus scanning and removal, and charging, on the mobile terminal 34； if the Android system is in a non-storage state, the automatic management module 33 cannot access a system file of the Android system, the automatic management module 33 can only perform the charging operation on the mobile terminal 34.

If the system type detection module 32 detects that the system type of the mobile terminal 34 is the Apple system, the automatic management module 33 preferably performs the automatic processing operation on the mobile terminal 34 by using an Apple communications protocol (universal serial bus (USB) multiplex daemon (usbmuxd) , which provides a USB-Transmission Control Protocol (TCP) conversion service, and is a communications protocol between iTunes and Apple (iOS) devices) .

Because the Apple system of the mobile terminal 34 does not have a non-storage state in which a system file cannot be accessed, the automatic management module 33 may perform automatic processing operations, such as data backup, file cleaning, application update, virus scanning and removal, and charging, on the mobile terminal 34 by using the Apple communications protocol.

In this way, the process of the processing operation by the mobile terminal processing apparatus 30 in this preferred embodiment is completed.

Based on the first preferred embodiment, the mobile terminal processing apparatus in this preferred embodiment can respectively perform targeted automatic processing operations on an Apple system and an Android system, further improving efficiency of a processing operation on a mobile terminal by a user.

Referring to FIG. 3 and FIG. 4, FIG. 4 is a flowchart of a second preferred embodiment of a mobile terminal processing method according to the present disclosure. The mobile terminal processing method in this preferred embodiment can be performed by using the second preferred embodiment of the mobile terminal processing apparatus, and includes:

Step S401: A charging socket detects a connection to a mobile terminal.

Step S402: The charging socket determines whether the charging socket is connected to the mobile terminal. If the charging socket is connected to the mobile terminal, perform step S403； if the charging socket is not connected to the mobile terminal, go back to step S401 to continue to detect a connection to the mobile terminal.

Step S403: The charging socket acquires a vender ID of the mobile terminal.

Step S404: The charging socket determines a system type of the mobile terminal according to the vender ID of the mobile terminal.

Step S405: The charging socket determines whether the system type of the mobile terminal is an Android system. If the system type is an Android system, perform step S406； if the system type is not an Android system, perform step S410.

Step S406: The charging socket detects a system state of the mobile terminal.

Step S407: The charging socket determines whether a system state of the Android mobile terminal is a storage state, if the system state of the Android mobile terminal is a storage state, perform step S408； if the system state of the Android mobile terminal is a non-storage state, perform step S409.

Step S408: The charging socket performs an automatic processing operation on the mobile terminal according to a preset to-be-processed item by using an adb.

Step S409: The charging socket performs a charging operation on the mobile terminal.

Step S410: The charging socket performs an automatic processing operation on the mobile terminal according to a preset to-be-processed item by using an Apple communications protocol.

The mobile terminal processing method in this preferred embodiment is ended by step S408, step S409, and step S410.

In step S401, a user connects a mobile terminal 34 and a mobile terminal processing apparatus 30 (the charging socket) by using a connection cable. For different interfaces of different mobile terminals 34, connection between the mobile terminals 34 and the mobile terminal processing apparatus 30 can be implemented by using different connection cables. A connection detection module 31 of the mobile terminal processing apparatus 30 detects whether the mobile terminal processing apparatus 30 is connected to the mobile terminal 34. Then, step S402 is performed.

In step S402, if the connection detection module 31 detects that the mobile terminal processing apparatus 30 is connected to the mobile terminal 34, step S403 is performed. If the connection detection module 31 does not detect that the mobile terminal processing apparatus 30 is connected to the mobile terminal 34, go back to step S401, so that the connection detection module 31 continues to detect a connection to the mobile terminal 34.

In step S403, a vender ID acquiring unit 321 of a system type detection module 32 acquires a vender ID of the mobile terminal 34. Then, step S404 is performed.

In step S404, a system type determining unit 322 of the system type detection module 32 determines a system type of the mobile terminal 34 according to the vender ID, which is acquired by the vender ID acquiring unit 321, of the mobile terminal 34, for example, a vender ID of an Apple system is 0x05c, and then may further acquire a specific manufacture of the mobile terminal 34 according to a product ID. Then, step S405 is performed.

In step S405, the system type determining unit 322 determines whether the system type of the mobile terminal 34 is an Android system. If the system type is an Android system, step S406 is performed. If the system type is not an Android system, step S410 is performed.

In step S406, if the system type determining unit 322 determines that the system type of the mobile terminal 34 is an Android system, the automatic management module 33 detects a system state of the mobile terminal 34. Then, step S407 is performed.

In step S407, an automatic management module 33 determines whether the system state of the mobile terminal 34 is a storage state. If the system state of the mobile terminal 34 is a storage state, step S408 is performed. If the system state of the mobile terminal 34 is a non-storage state, step S409 is performed.

In step S408, if the automatic management module 33 determines that the system state of the mobile terminal 34 is a storage state, the automatic management module 33 performs an automatic processing operation on the mobile terminal 34 according to a preset to-be-processed item 35.Herein, the automatic management module 33 preferably performs the automatic processing operation on the mobile terminal 34 by using an adb.

In step S409, if the automatic management module 33 determines that the system state of the mobile terminal 34 is a non-storage state, the automatic management module 33 only performs a charging operation on the mobile terminal 34.

In step S410, if the system type determining module 322 determines that the system type of the mobile terminal 34 is an Apple system, the automatic management module 33 preferably performs an automatic processing operation on the mobile terminal 34 by using an Apple communications protocol (usbmuxd, which provides a USB-TCP conversion service, and is a communications protocol between iTunes and Apple (iOS) devices) .

Because the Apple system of the mobile terminal 34 does not have a non-storage state in which a system file cannot be accessed, the automatic management module 33 may perform processing operations, such as data backup, file cleaning, application update, virus scanning and removal, and charging, on the mobile terminal 34 by using the Apple communications protocol.

Based on the first preferred embodiment, in the mobile terminal processing method in this preferred embodiment, targeted automatic processing operations can be respectively performed on an Apple system and an Android system, further improving efficiency of a processing operation on a mobile terminal by a user.

The present disclosure further provides a charging socket. Referring to FIG. 5, FIG. 5 is a schematic structural diagram of a preferred embodiment of a charging socket according to the present disclosure. The charging socket 50 in this preferred embodiment includes at least one data interface 51, a development board 52, a power supply 53, and a loudspeaker 54. The development board 52 of the charging socket 50 in this preferred embodiment can manage a mobile terminal 55 by using the foregoing mobile terminal processing apparatus.

The data interface 51 of the charging socket 50 is configured to connect to the mobile terminal 55. The development board 52 of the charging socket 50 is configured to perform an automatic processing operation on the mobile terminal 55 connected to the charging socket 50, and includes a GPIO, where the GPIO can support a micro USB port, a lightning interface, an Apple 30-pin interface, and the like of the mobile terminal 55, and the GPIO is connected to the data interface 51 of the charging socket 50. The power supply 53 of the charging socket 50 is configured to supply power to the development board 52 and the data interface 51. The loudspeaker 54 of the charging socket 50 is configured to make a corresponding sound prompt, alarm prompt, or the like according to an operation result of automatic management.

If a system type of the mobile terminal 55 is an Android system, the development board 52 of the charging socket 50 performs the automatic processing operation on the mobile terminal 55 by using an adb. If the system type of the mobile terminal 55 is an Apple system, the development board 52 of the charging socket 50 performs the automatic processing operation on the mobile terminal 55 by using an Apple communications protocol. Herein, the automatic processing operation includes, but is not limited to, a data backup operation, a file cleaning operation, an application update operation, a virus scanning and removal operation, and a charging operation.

The charging socket in this preferred embodiment may further include a wireless connection module (not shown in the figure) . In this way, the charging socket may further be wirelessly connected to a corresponding mobile terminal by using the wireless connection module, to manage the mobile terminal.

A specific use principle of the charging socket 50 in this preferred embodiment is the same as that of the processing operation performed on the mobile terminal according to the mobile terminal processing apparatus and the mobile terminal processing method. For details, reference may be made to descriptions in the preferred embodiments of the mobile terminal processing apparatus and the mobile terminal processing method.

In this preferred embodiment, a development board which processes a mobile terminal is disposed in a charging socket of a corresponding mobile terminal, so that the charging socket can respectively perform targeted automatic processing operations on mobile terminals with an Apple system and an Android system, further improving efficiency of a processing operation on the mobile terminal by a user.

A process of using a charging socket in the present disclosure is described below in detail with reference to FIG. 5 and FIG. 6. FIG. 6 is a flowchart of use of a specific embodiment of the charging socket according to the present disclosure.

Step S601: A data interface 51 of a charging socket 50 is connected to a mobile terminal 55, where the data interface 51 may be connected to the mobile terminal 55 by using a corresponding data line (such as a data line supporting a micro USB port, a lightning interface, or an Apple 30-pin interface) . Then, step S602 is performed.

Step S602: A development board 52 of the charging socket 50 acquires a vender ID of the mobile terminal 55. Then, step S603 is performed.

Step S603: The development board 52 determines whether the vender ID is 0x05ac. If the vender ID is 0x05ac, perform step S604； if the vender ID is not 0x05ac, perform step S605.

Step S604: If the development board 52 determines that the vender ID is 0x05ac, the development board determines that a system type of the mobile terminal 50 is an Apple system, and the development board 52 interacts with the Apple mobile terminal by using usbmuxd. Then, S607 is performed.

Step S605: If the development board 52 determines that the vender ID is not 0x05ac, the development board determines that a system type of the mobile terminal 55 is an Android system, and the development board 52 determines whether a system state of the Android system is a storage state. If the system state of the Android system is a storage state, perform step S606； if the system state of the Android system is not a storage state, perform step S610.

Step S606: The development board 52 interacts with the Android mobile terminal by using an adb. Then, step S607 is performed.

Step S607: The development board 52 performs an application installation operation and an application update operation on the mobile terminal 55, and the loudspeaker 54 of the charging socket 50 may make a sound prompt or alarm prompt for an operation result. Then, step S608 is performed.

Step S608: The development board 52 performs a data backup operation on the mobile terminal 55, and the loudspeaker 54 of the charging socket 50 may make a sound prompt or alarm prompt for an operation result. Then, step S609 is performed.

Step S609: The development board 52 performs a file cleaning operation on the mobile terminal 55, and the loudspeaker 54 of the charging socket 50 may make a sound prompt or alarm prompt for an operation result. Then, step S610 is performed.

Step S610: The development board 52 performs a charging operation on the mobile terminal 55, and the loudspeaker 54 of the charging socket 50 can make a sound prompt or alarm prompt for an operation result.

In this way, the processing operation on the mobile terminal 55 by the charging socket 50 is completed. An execution order of step S607, step S608, and step S609 may be adjusted according to settings of a user, for example, step S609 is first performed for file cleaning, and step S608 is then performed for the data backup operation, which also belongs to the protection scope of the present disclosure.

According to the mobile terminal processing method, the mobile terminal processing apparatus and the charging socket in the present disclosure, a charging socket of a mobile terminal performs an automatic processing operation on the mobile terminal, which solves a technical problem that an existing charging socket cannot automatically manage the mobile terminal, and thus affects operation efficiency of a user.

The functional units in the embodiments of the present invention may be integrated into one processing module, or each of the units may exist alone physically, or two or more units may be integrated into one module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. When the integrated module is implemented in a form of a software functional module and sold or used as an independent product, the integrated module may be stored in a computer-readable storage medium. The foregoing storage medium may be a read-only memory, a magnetic disk, or an optical disc. The apparatuses or systems can perform methods in corresponding method embodiments.

To sum up, although the present disclosure is described above by using preferred embodiments, the preferred embodiments are not intended to limit the present disclosure. Various variations and modifications can be made by persons of ordinary skill in the art without departing from the spirit and scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the scope defined by the claims.

Claims

A charging socket, comprising:

at least one data interface, configured to connect to a mobile terminal；

a development board, comprising a general purpose input/output (GPIO) , configured to perform a processing operation on the mobile terminal connected to the data interface； and

a power supply module, configured to supply power to the development board and the data interface,

the at least one data interface being connected to the development board, and the power supply module being separately connected to the at least one data interface and the development board.
The charging socket according to claim 1, wherein the GIPO supports a micro universal serial bus (USB) port, a lightning interface, and an Apple 30-pin interface.
The charging socket according to claim 1, wherein the charging socket further comprises:

a loudspeaker, configured to make a corresponding sound prompt according to an operationresult of automatic management, wherein the loudspeaker is separately connected to the development board and the power supply module.
The charging socket according to claim 1, wherein the performing a processing operation on the mobile terminal connected to the data interface comprises:

detecting, by the development board, whether the data interface is connected to the mobile terminal；

detecting, by the development board, a system type of the mobile terminal if the data interface is connected to the mobile terminal； and

performing, by the development board, the processing operation on the mobile terminal according to the system type of the mobile terminal and a preset to-be-processed item, wherein

the processing operation comprises a data operation and a charging operation on the mobile terminal.
The charging socket according to claim 4, wherein the step of detecting a system type of the mobile terminal comprises:

acquiring, by the development board, a vender ID of the mobile terminal； and

determining, by the development board, the system type of the mobile terminal according to the vender ID of the mobile terminal.
The charging socket according to claim 4, wherein if the system type of the mobile terminal is an Android system, the performing, by the development board, a processing operation on the mobile terminal further comprises:

detecting, by the development board, a system state of the mobile terminal； and

performing, by the development board, the processing operation on the mobile terminal according to the system type of the mobile terminal, the system state of the mobile terminal, and the preset to-be-processed item.
The charging socket according to claim 6, wherein

if the system type of the mobile terminal is the Android system, the system state of the mobile terminal comprises a storage state in which a system file can be accessed and a non-storage state in which a system file cannot be accessed；

if the system state of the mobile terminal is a storage state, the development board performs the processing operation on the mobile terminal according to the preset to-be-processed item； and

if the system state of the mobile terminal is a non-storage state, the development board performs the charging operation on the mobile terminal.
The charging socket according to claim 4, wherein the step of performing, by the development board, a processing operation on the mobile terminal comprises:

performing, by the development board if the system type of the mobile terminal is an Android system, the processing operation on the mobile terminal according to the preset to-be-processed item by using an Android debug bridge (adb) ； and

performing, by the development board if the system type of the mobile terminal is an Apple system, the processing operation on the mobile terminal according to the preset to-be-processed item by using an Apple communications protocol.
A mobile terminal processing method based on the charging socket according to claim 1, comprising:

detecting, by the charging socket, whether the charging socket is connected to a mobile terminal；

detecting, by the charging socket, a system type of the mobile terminal if the charging socket is connected to the mobile terminal； and

performing, by the charging socket, a processing operation on the mobile terminal according to the system type of the mobile terminal and a preset to-be-processed item,

the processing operation comprising a data operation and a charging operation on the mobile terminal.
The mobile terminal processing method based on the charging socket according to claim 9, wherein the step of detecting a system type of the mobile terminal comprises:

acquiring, by the charging socket, a vender ID of the mobile terminal； and

determining, by the charging socket, the system type of the mobile terminal according to the vender ID of the mobile terminal.
The mobile terminal processing method based on the charging socket according to claim 9, wherein if the system type of the mobile terminal is an Android system, the mobile terminal processing method further comprises:

detecting, by the charging socket, a system state of the mobile terminal； and

performing, by the charging socket, the processing operation on the mobile terminal according to the system type of the mobile terminal, the system state of the mobile terminal, and the preset to-be-processed item.
The mobile terminal processing method based on the charging socket according to claim 11, wherein

if the system type of the mobile terminal is the Android system, the system state of the mobile terminal comprises a storage state in which a system file can be accessed and a non-storage state in which a system file cannot be accessed；

if the system state of the mobile terminal is a storage state, the charging socket performs the processing operation on the mobile terminal according to the preset to-be-processed item； and

if the system state of the mobile terminal is a non-storage state, the charging socket performs the charging operation on the mobile terminal.
The mobile terminal processing method based on the charging socket according to claim 9, wherein the step of performing a processing operation on the mobile terminal comprises:

performing, by the charging socket if the system type of the mobile terminal is an Android system, the processing operation on the mobile terminal according to the preset to-be-processed item by using an Android debug bridge (adb) ； and

performing, by the charging socket if the system type of the mobile terminal is an Apple system, the processing operation on the mobile terminal according to the preset to-be-processed item by using an Apple communications protocol.