Component management method and device and mobile terminal

[0061] The exemplary embodiments will be described in detail here, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present invention. Rather, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0062] figure 1 It is a flowchart of a component management method according to an exemplary embodiment, such as figure 1 As shown, the method includes the following steps.

[0063] In step 101, when a component management request is received, the first component name is extracted from the component management request, and the component management request carries the component to be managed and the first component name of the component to be managed.

[0064] In step 102, based on the first component name, it is searched whether there is a first pit name corresponding to the first component name.

[0065] In step 103, if it is determined that there is a first pit name corresponding to the first component name, the component to be managed is managed based on the pit indicated by the first pit name.

[0066] In the method provided by the embodiment of the present invention, when a component management request is received, the first component name is extracted from the component management request, and based on the first component name, it is found whether there is a first hole name corresponding to the first component name, if If it is determined that there is a first pit name corresponding to the first component name, the component to be managed is managed based on the pit indicated by the first pit name, so that the corresponding relationship between the component and the pit is fixed, which can be directly based on the The corresponding pit position management component does not need to perform pit position allocation every time the component is managed, which avoids pit position allocation errors and has better intelligence.

[0067] In another embodiment, the method further includes:

[0068] If it is determined that there is no first pit name corresponding to the first component name, determine the pit to be allocated;

[0069] When it is determined that the pit to be allocated is successful, the second pit name of the pit to be allocated is correspondingly stored with the name of the first component;

[0070] Manage the components to be managed based on the pits to be allocated.

[0071] In another embodiment, if it is determined that there is no first pit name corresponding to the first component name, determining that the pit to be allocated includes:

[0072] If it is determined that there is no first pit name corresponding to the first component name, determine at least one unallocated pit;

[0073] Extract any unallocated pit from the at least one unallocated pit, and use the unallocated pit as the to-be-allocated pit.

[0074] In another embodiment, the method further includes:

[0075] When it is determined that the pit to be allocated fails, obtain at least one recyclable pit that has not been recovered, and the component corresponding to the reclaimable pit has been removed;

[0076] If obtaining the at least one recyclable pit is successful, set the at least one recyclable pit as an unallocated pit;

[0077] If the acquisition of the at least one recoverable pit fails, a recovery failure instruction is generated and displayed.

[0078] In another embodiment, the method further includes:

[0079] When a component removal request is received, extract the second component name from the component removal request, and the component removal request carries the second component name of the component to be removed;

[0080] Searching for the name of the pit to be removed corresponding to the name of the second component based on the name of the second component;

[0081] The pit to be removed indicated by the name of the pit to be removed is released, and the pit to be removed is set as an unallocated pit.

[0082] All the above-mentioned optional technical solutions can be combined in any way to form an optional embodiment of the present invention, which will not be repeated here.

[0083] Figure 2A It is a flowchart of a component management method according to an exemplary embodiment, such as Figure 2A As shown, the method includes the following steps.

[0084] In step 201, when a component management request is received, the first component name is extracted from the component management request, and the component management request carries the component to be managed and the first component name of the component to be managed.

[0085] In the embodiment of the present invention, the component to be managed may be a component in the terminal operating system, for example, an Activity (interaction) component, a Service (service) component, a Content Provide (data sharing) component, and a Receiver (receiver) component. The terminal operating system may be an Android (semi-open source operation) system, and the embodiment of the present invention does not specifically limit the types of management components and terminal operating systems. The inventor realizes that when the sandbox receives a component management request, it usually randomly allocates pits for the components to be managed carried in the component management request, and manages the components to be managed based on the assigned pits. Since the components running in the sandbox may be malware, the structure and function of the malware may be imperfect, which may cause the malware to crash during the running process, and then exit the sandbox, and the sandbox will keep receiving during the running process. A large number of component management requests result in a large amount of startup events and exit events that are generated in parallel during the process of managing components in the sandbox. This makes the sandbox's recording of startup events and exit events may cause errors. It cannot be completely synchronized with the exit event. The sandbox may still record the pit that has been assigned a management component as an unallocated pit. For example, pit A has been assigned to the component to be managed 1, but an error in the sandbox causes the record Pit A has not been allocated. In this way, when the current component to be managed is allocated next time, it is very likely that the pit that has been allocated to other components will be allocated to the current component to be managed again, resulting in the current component to be managed Unable to manage normally. Therefore, in the embodiment of the present invention, a fixed pit position is allocated to each component to be managed, so that when each component to be managed enters the sandbox, it can enter the fixed pit position for management, and avoid randomizing the components to be managed. An error occurs when allocating pits, and the intelligence is better.

[0086] Since the corresponding relationship between the component to be managed and the pit is fixed, when the component to be managed needs to be managed, the first component name of the component to be managed can be carried in the component management request, so that the sandbox can receive the component During the management request, the pit position corresponding to the component to be managed is determined based on the first component name in the component management request, and then the component to be managed is managed based on the pit position. Among them, the sandbox may provide a component management entry on the terminal with which it has a connection relationship, and when it is detected that the user triggers the component management entry, the component upload page is displayed. The component upload page can provide component upload box, component name input box and confirm button. When the terminal detects the component to be managed uploaded in the component upload box, it can directly read the first component name of the component to be managed and directly The first component name is displayed in the component name input box, and the first component name manually input by the user in the component name input box can also be received. When the user triggers the confirmation button, the terminal determines that the current user has finished uploading the components to be managed and filling in the names of the first components of the components to be managed, and obtains the components to be managed and the names of the first components, based on the components to be managed and the first component names. A component name generates a component management request, and sends the component management request to the sandbox, so that after receiving the component management request, the sandbox determines the pit location corresponding to the component to be managed, and manages the component to be managed based on the pit location.

[0087] In step 202, based on the first component name, it is searched whether there is a first pit name corresponding to the first component name, and if it is determined that there is a first pit name corresponding to the first component name, the following step 203 is executed; If it is determined that there is no first pit location name corresponding to the first component name, the following step 204 is performed.

[0088] In the embodiment of the present invention, after the first component name of the component to be managed is determined, it can be searched based on the first component name to find out whether there is a first pit name corresponding to the first component name. The name of the first pit location corresponding to the name of the first component determines that the component to be managed is not the first time to enter the sandbox management. A fixed pit location has been assigned to the component to be managed in the sandbox, and the component to be managed can directly enter the sandbox Perform management, that is, perform the following step 203; if it is determined that there is no first hole name corresponding to the first component name, determine that the component to be managed enters the sandbox management for the first time. In this way, it is necessary to assign a fixed component to the component to be managed , And manage the components to be managed based on the pit position, that is, perform the following step 204.

[0089] In step 203, if it is determined that there is a first pit name corresponding to the first component name, the component to be managed is managed based on the pit indicated by the first pit name.

[0090] In the embodiment of the present invention, if it is determined that there is a first pit name corresponding to the first component name, it means that there is already a pit corresponding to the component to be managed in the current bunker, which can be directly based on the first pit name. The pit position manages the component to be managed.

[0091] In step 204, if it is determined that there is no first pit name corresponding to the first component name, the pit to be allocated is determined. When it is determined that the pit to be allocated is successful, the following step 205 is executed; when the pit to be allocated is determined In case of failure, perform the following step 206.

[0092] In the embodiment of the present invention, if it is determined that there is no first pit name corresponding to the first component name, it is determined that the component to be managed enters the sandbox management for the first time. In this way, it is necessary to determine the pits to be allocated in the sandbox that have not yet been allocated. Bits, the pits to be allocated are allocated to the components to be managed for management. Since there may be at least one unallocated pit in the sandbox, the sandbox can extract any of the at least one unallocated pit as the pit to be allocated, and subsequently allocate the pit to be allocated to the management The components are managed, that is, the following step 205 is executed.

[0093] In the actual application process, because the start event and exit event generated by the sandbox in the process of managing components cannot be completely synchronized, so that when a component in the sandbox has been tested, it is no longer necessary to enter the sandbox management At the time, the sandbox may not recover the pit of the component, and still record that the pit is allocated to the component; however, the pit in the sandbox is limited, and there may be some completed tests and The pits corresponding to the management components that exit the sandbox. These pits may be allocated pits in the current record of the sandbox. Therefore, the sandbox fails to determine the pits to be allocated. In this way, it is necessary to check the sandbox. The idle pits (that is, the pits where the corresponding component has been tested) are recovered, and the unallocated pits are re-obtained, and the unallocated pits are allocated to the components to be managed, that is, the following step 206 is executed.

[0094] In step 205, when it is determined that the pit to be allocated is successful, the second pit name of the pit to be allocated is stored corresponding to the name of the first component, and the component to be managed is managed based on the pit to be allocated.

[0095] In the embodiment of the present invention, when it is determined that the pit to be allocated is successful, the second pit name of the pit to be allocated can be stored correspondingly to the first component name of the component to be managed to indicate that the current pit to be allocated has been Assigned to the component to be managed, the next time the component to be managed enters the sandbox management, it can directly enter the pit indicated by the second pit name, and the sandbox does not need to allocate the pit to the component to be managed. Wherein, when the sandbox stores the second pit location name and the first component name, it can generate the component-pit location relationship list shown in Table 1. The embodiment of the present invention has a corresponding relationship between the sandbox storage component name and the pit location name The method is not specifically limited.

[0096] Table 1

[0097] Component name

[0098] In step 206, when it is determined that the pit to be allocated fails, at least one recyclable pit that has not been recovered is obtained, and the component corresponding to the recyclable pit has been removed. If the acquisition of at least one recyclable pit succeeds, the following is performed Step 207: If the acquisition of at least one recoverable pit fails, perform the following step 208.

[0099] In the embodiment of the present invention, when it is determined that the pit to be allocated fails, at least one recoverable pit may be determined in the sandbox. Among them, when at least one recyclable pit is determined, the operation status of all pits in the sandbox can be detected, the pits that are not managed components are regarded as idle pits, and the idle time of the idle pits is counted. Time determines the location of the recyclable pit. A timeout period can be set in the sandbox. When it is determined that the idle time of a pit is greater than the timeout period, the pit is determined to be a recyclable pit; a preset number can also be set in the sandbox. After determining the display time of each pit, The idle time is sorted according to the length of the idle time, and the preset number of pits with the longest idle time is regarded as the recyclable pits. Among them, in order to record the idle time of each pit position, the sandbox can set a timer for each pit position. When a component in a certain pit position exits, the timer of the pit position is automatically started to start timing. In the actual application process, you can also determine whether the pit is a recyclable pit according to the component status of the running component in the pit. The sandbox can record the running status of its corresponding component. When it is detected that the component has completed the test When the entire process is exited, the component status corresponding to the pit location is set to when the test is completed, so that the pit location can be determined as a recyclable pit location in the subsequent. The embodiment of the present invention does not specifically limit the manner in which the sandbox determines the location of the recyclable pit.

[0100] Since there may not be any recyclable pits in the sandbox, the acquisition of at least one recyclable pit may fail. In this way, if the sandbox succeeds in obtaining at least one recyclable pit, at least one recyclable pit will be recovered. At least one reclaimable pit is set as an unallocated pit, so as to extract any pit from the unallocated pit as a pit to be allocated, and then manage the components to be managed based on the pit to be allocated, that is, perform the following steps 207; If the sandbox fails to obtain at least one recyclable pit, it means that there is no available pit in the current sandbox, and the developer needs to add pits to the sandbox. At this time, a recovery failure instruction needs to be generated to correct The developer makes a reminder, that is, executes the following step 208.

[0101] In step 207, if the acquisition of at least one recyclable pit is successful, at least one recyclable pit is set as an unallocated pit, and step 205 is performed.

[0102] In the embodiment of the present invention, if the acquisition of at least one recyclable pit is successful, at least one recyclable pit can be set as an unallocated pit, and then any pit from the unallocated pit can be extracted as a pit to be allocated In order to allocate the pit to be allocated to the component to be managed, the component to be managed is managed based on the pit to be allocated, that is, the following step 207 is executed.

[0103] In step 208, if obtaining at least one recoverable pit fails, a recovery failure instruction is generated and displayed.

[0104] In the embodiment of the present invention, if the acquisition of at least one recyclable pit fails, it means that there is no idle pit in the current sandbox, and there are management components in all the pits. In this way, the developer needs to increase the sand. Therefore, the sandbox will generate a recovery failure instruction and display the recovery failure instruction so that developers can know that the current sandbox is insufficient. In the actual application process, the sandbox can be connected to the terminal, and when the recovery failure instruction is generated, the recovery failure instruction is transmitted to the terminal, and the terminal displays the recovery failure instruction. The embodiment of the present invention does not specifically limit the manner in which the sandbox displays the recovery failure instruction.

[0105] It should be noted that during the operation of the sandbox, there will be components that have been tested in the sandbox. These components can be removed in their corresponding pits after the testing is completed, and will not be entered in the subsequent The corresponding pit location management, in this way, the component needs to be removed from the pit location. See Figure 2B , You can execute Figure 2B Steps 209 to 211 in Figure 1 implement the removal of the component from the pit.

[0106] In step 209, when the component removal request is received, the second component name is extracted from the component removal request, and the component removal request carries the second component name of the component to be removed.

[0107] In the embodiment of the present invention, since the correspondence between components and pits is fixed, when a component needs to be removed, the component removal request needs to carry the second component name of the component to be removed , So that when the sandbox receives the component removal request, it determines the pit corresponding to the component to be removed based on the second component name in the component removal request, and then removes the component in the pit, and The pit is for recycling. Among them, the sandbox may provide a component removal portal on the terminal with which it is connected, and when it is detected that the user triggers the component removal portal, the component removal page is displayed. The component removal page can provide a removal component name input box and a confirm button. The terminal receives the second component name manually entered by the user in the removed component name input box. When the user triggers the confirm button, the terminal confirms The current user has completed filling in the second component name of the component to be removed, obtains the second component name of the component to be removed, generates a component removal request based on the second component name, and sends the component removal request to the sandbox to After receiving the component removal request, the sandbox determines the pit location corresponding to the component to be removed, removes the component in the pit location, and reclaims the pit location.

[0108] When the sandbox receives a component removal request, it will directly extract the second component name of the component to be removed in the component removal request, so that it can search based on the second component name in the future to determine the corresponding component to be removed Pit, remove the components in the pit, and recycle the pit.

[0109] In step 210, based on the second component name, search for the name of the pit to be removed corresponding to the second component name.

[0110] In the embodiment of the present invention, after the second component name of the component to be removed is determined, it can be searched based on the second component name, determine the pit name to be removed of the pit corresponding to the second component name, and then The pit indicated by the pit to be removed is released, and the pit to be removed is set as an unallocated pit.

[0111] In the actual application process, if the relationship between the component name and the pit name is stored in the sandbox based on Table 1 shown in step 205, after the second component name is determined, the component- Query in the pit relationship list to determine the name of the pit to be removed.

[0112] In step 211, the pit to be removed indicated by the name of the pit to be removed is released, and the pit to be removed is set as an unallocated pit.

[0113] In the embodiment of the present invention, when the name of the pit to be removed is determined, the components running in the pit to be removed can be removed, the pit to be removed is recovered, and the pit to be removed is released, and The pit to be removed is set as an unallocated pit, so that a new component to be managed is subsequently allocated to the unallocated pit.

[0114] It should be noted that the content in the above steps 209 to 211 can be executed only when pit removal is required. If all pits in the current sandbox are operating normally and there are no pits that have been tested, they may not Perform steps 209 to 211 above.

[0115] In the actual application process, in order to manage the pits in the sandbox more stably, a pit manager can be set in the sandbox, see Figure 2C , The pit position manager executes the pit position allocation, pit position query, pit position recovery, and pit position release operations involved in the above steps 201 to 211. The embodiment of the present invention does not specifically limit the objects for performing operations such as pit location allocation, pit location query, pit location recovery, and pit location release. in Figure 2C When the sandbox receives the component management request, the sandbox asks the pit manager to check whether there is a first pit name corresponding to the first component name carried in the component management request. If the pit manager returns information The first pit name corresponding to the first component name in the display sandbox is directly based on the component to be managed carried in the pit management component management request indicated by the first pit name; if the information returned by the pit manager is displayed There is no first hole name corresponding to the first component name in the sandbox, and the sandbox requests the hole manager to allocate a new hole for the component to be managed. When the pit position manager receives the sandbox request to allocate a new pit position to the component to be managed, it extracts any unallocated pit position from at least one unallocated pit position as the pit position to be allocated, and returns the pit position to be allocated Give the sandbox so that the sandbox manages the components to be managed based on the pits to be allocated. If there is no unallocated pit in the pit location manager, the pit location manager manages the pit location recovery function, recovers the recyclable pit location in the sandbox, and sets at least one reclaimable pit location recovered as Unallocated pits in order to allocate unallocated pits to new components to be managed. Wherein, when the sandbox receives a component removal request, it can transmit the component removal request to the pit manager, and the pit manager determines based on the second component name of the component to be removed carried in the component removal request The pit position is to release the pit position to realize the removal of the components to be removed and the recovery of the pit position.

[0116] In the method provided by the embodiment of the present invention, when a component management request is received, the first component name is extracted from the component management request, and based on the first component name, it is found whether there is a first hole name corresponding to the first component name, if If it is determined that there is a first pit name corresponding to the first component name, the component to be managed is managed based on the pit indicated by the first pit name, so that the correspondence between the component and the pit is fixed, which can be directly based on the The corresponding pit position management component does not need to perform pit position allocation every time the component is managed, which avoids pit position allocation errors and has better intelligence.

[0117] Figure 3A It is a block diagram showing a component management device according to an exemplary embodiment. Reference Figure 3A , The device includes an extraction module 301, a search module 302, and a management module 303.

[0118] The extraction module 301 is configured to extract a first component name from the component management request when a component management request is received, and the component management request carries the component to be managed and the first component name of the component to be managed;

[0119] The searching module 302 is configured to search for whether there is a first pit name corresponding to the first component name based on the first component name;

[0120] The management module 303 is configured to, if it is determined that there is a first pit name corresponding to the first component name, manage the component to be managed based on the pit indicated by the first pit name.

[0121] In the device provided by the embodiment of the present invention, when a component management request is received, the first component name is extracted from the component management request, and based on the first component name, it searches whether there is a first hole name corresponding to the first component name, if If it is determined that there is a first pit name corresponding to the first component name, the component to be managed is managed based on the pit indicated by the first pit name, so that the corresponding relationship between the component and the pit is fixed, which can be directly based on the The corresponding pit position management component does not need to perform pit position allocation every time the component is managed, which avoids pit position allocation errors and has better intelligence.

[0122] In another embodiment, see Figure 3B , The device also includes a determining module 304 and a storage module 305.

[0123] The determining module 304 is configured to determine the pit to be allocated if it is determined that there is no first pit name corresponding to the first component name;

[0124] The storage module 305 is configured to store the second pit name of the pit to be allocated and the name of the first component correspondingly when it is determined that the pit to be allocated is successful;

[0125] The management module 303 is also used to manage the components to be managed based on the pits to be allocated.

[0126] In another embodiment, see Figure 3C , The determination module 304 includes a determination sub-module 3041 and an extraction sub-module 3042.

[0127] The determining sub-module 3041 is configured to determine at least one unallocated pit if it is determined that there is no first pit name corresponding to the first component name;

[0128] The extraction sub-module 3042 is used to extract any unallocated pit from at least one unallocated pit, and use the unallocated pit as a to-be-allocated pit.

[0129] In another embodiment, see Figure 3D , The device also includes an obtaining module 306, a setting module 307, and a generating module 308.

[0130] The obtaining module 306 is configured to obtain at least one recyclable pit that has not yet been recovered when it is determined that the pit to be allocated fails, and the component corresponding to the recyclable pit has been removed;

[0131] The setting module 307 is configured to set the at least one recyclable pit as an unallocated pit if the acquisition of at least one recyclable pit is successful;

[0132] The generating module 308 is configured to generate and display a recovery failure instruction if the acquisition of at least one recoverable pit fails.

[0133] In another embodiment, see Figure 3E , The device also includes a release module 309.

[0134] The extraction module 301 is further configured to extract the second component name from the component removal request when the component removal request is received, and the component removal request carries the second component name of the component to be removed;

[0135] The search module 302 is also used to search for the name of the pit to be removed corresponding to the name of the second component based on the name of the second component;

[0136] The release module 309 is used to release the pit to be removed indicated by the name of the pit to be removed, and set the pit to be removed as an unallocated pit.

[0137] Regarding the device in the foregoing embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and detailed description will not be given here.

[0138] Figure 4 It is a block diagram showing a component management device 400 according to an exemplary embodiment. For example, the apparatus 400 may be a mobile phone, a computer, a digital broadcasting terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0139] Reference Figure 4 , The device 400 may include one or more of the following components: a processing component 402, a memory 404, a power supply component 406, a multimedia component 408, an audio component 410, an I/O (Input/Output) interface 412, and a sensor component 414 , And communication component 416.

[0140] The processing component 402 generally controls the overall operations of the device 400, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 402 may include one or more processors 420 to execute instructions to complete all or part of the steps of the foregoing method. In addition, the processing component 402 may include one or more modules to facilitate the interaction between the processing component 402 and other components. For example, the processing component 402 may include a multimedia module to facilitate the interaction between the multimedia component 408 and the processing component 402.

[0141] The memory 404 is configured to store various types of data to support the operation of the device 400. Examples of these data include instructions for any application or method operating on the device 400, contact data, phone book data, messages, pictures, videos, etc. The memory 404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as SRAM (Static Random Access Memory, static random access memory), EEPROM (Electrically-Erasable Programmable Read-Only Memory, electrical Erasable Programmable Read Only Memory), EPROM (Erasable Programmable Read Only Memory), PROM (Programmable Read-Only Memory, Programmable Read-Only Memory), ROM (Read-Only Memory, Read-only memory), magnetic memory, flash memory, magnetic or optical disk.

[0142] The power supply component 406 provides power to various components of the device 400. The power supply component 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 400.

[0143] The multimedia component 408 includes a screen that provides an output interface between the device 400 and the user. In some embodiments, the screen may include LCD (Liquid Crystal Display, liquid crystal display) and TP (TouchPanel, touch panel). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, sliding, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure related to the touch or slide operation. In some embodiments, the multimedia component 408 includes a front camera and/or a rear camera. When the device 400 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

[0144] The audio component 410 is configured to output and/or input audio signals. For example, the audio component 410 includes a MIC (Microphone). When the device 400 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 404 or sent via the communication component 416. In some embodiments, the audio component 410 further includes a speaker for outputting audio signals.

[0145] The I/O interface 412 provides an interface between the processing component 402 and a peripheral interface module. The peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0146] The sensor component 414 includes one or more sensors for providing the device 400 with various aspects of status assessment. For example, the sensor component 414 can detect the on/off status of the device 400 and the relative positioning of components, such as the display and keypad of the device 400. The sensor component 414 can also detect the position change of the device 400 or a component of the device 400. The presence or absence of contact with the device 400, the orientation or acceleration/deceleration of the device 400, and the temperature change of the device 400. The sensor component 414 may include a proximity sensor configured to detect the presence of nearby objects when there is no physical contact. The sensor component 414 may also include a light sensor, such as a CMOS (Complementary Metal Oxide Semiconductor) or CCD (Charge-coupled Device) image sensor for use in imaging applications. In some embodiments, the sensor component 414 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

[0147] The communication component 416 is configured to facilitate wired or wireless communication between the apparatus 400 and other devices. The device 400 can access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 416 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 416 further includes an NFC (Near Field Communication) module to facilitate short-range communication. For example, the NFC module can be based on RFID (Radio Frequency Identification) technology, IrDA (Infra-red Data Association, infrared data association) technology, UWB (Ultra Wideband, ultra-wideband) technology, BT (Bluetooth, Bluetooth) technology and other Technology to achieve.

[0148] In an exemplary embodiment, the apparatus 400 may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors, digital signal processors), DSPDs (Digital Signal Processor Devices, digital signal processing devices). ), PLD (Programmable Logic Device, Programmable Logic Device), FPGA) (Field Programmable Gate Array, Field Programmable Gate Array), controller, microcontroller, microprocessor or other electronic components to implement the above component management method.

[0149] In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 404 including instructions, which may be executed by the processor 420 of the device 400 to complete the foregoing method. For example, the non-transitory computer-readable storage medium may be ROM, RAM (Random Access Memory, random access memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk, and optical data Storage equipment, etc.

[0150] A non-transitory computer-readable storage medium. When the instructions in the storage medium are executed by the processor of the component management device, the component activation device can execute the above component management method.

[0151] A1. A component management method, characterized in that the method includes:

[0152] When a component management request is received, extract the first component name from the component management request, and the component management request carries the component to be managed and the first component name of the component to be managed;

[0153] Based on the first component name, searching whether there is a first pit name corresponding to the first component name;

[0154] If it is determined that there is a first pit name corresponding to the first component name, the component to be managed is managed based on the pit indicated by the first pit name.

[0155] A2. The method of claim 1, wherein the method further comprises:

[0156] If it is determined that there is no first pit name corresponding to the first component name, determine the pit to be allocated;

[0157] When it is determined that the pit to be allocated is successful, the second pit name of the pit to be allocated is stored corresponding to the name of the first component;

[0158] Manage the components to be managed based on the pits to be allocated.

[0159] A3. The method according to claim 2, wherein if it is determined that there is no first pit name corresponding to the first component name, then determining the pit to be allocated comprises:

[0160] If it is determined that there is no first pit name corresponding to the first component name, determine at least one unallocated pit;

[0161] Extract any unallocated pit from the at least one unallocated pit, and use the unallocated pit as the to-be-allocated pit.

[0162] A4. The method according to claim 2, wherein the method further comprises:

[0163] When it is determined that the pit to be allocated fails, obtain at least one recyclable pit that has not been recovered, and the component corresponding to the reclaimable pit has been removed;

[0164] If obtaining the at least one recyclable pit is successful, set the at least one recyclable pit as an unallocated pit;

[0165] If the acquisition of the at least one recoverable pit fails, a recovery failure instruction is generated and displayed.

[0166] A5. The method according to claim 1, wherein the method further comprises:

[0167] When a component removal request is received, extract the second component name from the component removal request, and the component removal request carries the second component name of the component to be removed;

[0168] Searching for the name of the pit to be removed corresponding to the name of the second component based on the name of the second component;

[0169] The pit to be removed indicated by the name of the pit to be removed is released, and the pit to be removed is set as an unallocated pit.

[0170] A6. A component management device, characterized in that the device includes:

[0171] An extraction module, configured to extract a first component name from the component management request when a component management request is received, the component management request carrying the component to be managed and the first component name of the component to be managed;

[0172] A searching module, configured to search for whether there is a first pit name corresponding to the first component name based on the first component name;

[0173] The management module is configured to, if it is determined that there is a first pit name corresponding to the first component name, manage the component to be managed based on the pit indicated by the first pit name.

[0174] A7. The device according to claim 6, wherein the device further comprises:

[0175] A determining module, configured to determine the pit to be allocated if it is determined that there is no first pit name corresponding to the first component name;

[0176] A storage module, configured to store the second pit name of the pit to be allocated corresponding to the first component name when it is determined that the pit to be allocated is successful;

[0177] The management module is further configured to manage the components to be managed based on the pits to be allocated.

[0178] A8. The device according to claim 7, wherein the determining module comprises:

[0179] A determining sub-module is configured to determine at least one unallocated pit if it is determined that there is no first pit name corresponding to the first component name;

[0180] The extraction sub-module is configured to extract any unallocated pit from the at least one unallocated pit, and use the unallocated pit as the to-be-allocated pit.

[0181] A9. The device according to claim 7, wherein the device further comprises:

[0182] An obtaining module, configured to obtain at least one recyclable pit that has not been reclaimed when it is determined that the pit to be allocated fails, and the component corresponding to the reclaimable pit has been removed;

[0183] A setting module, configured to set the at least one recyclable pit as an unallocated pit if the acquisition of the at least one recyclable pit is successful;

[0184] The generating module is configured to generate and display a recovery failure instruction if the acquisition of the at least one recoverable pit fails.

[0185] A10. The device according to claim 6, wherein the device further comprises:

[0186] The extraction module is further configured to extract a second component name from the component removal request when a component removal request is received, and the component removal request carries the second component name of the component to be removed;

[0187] The search module is further configured to search for the name of the pit to be removed corresponding to the name of the second component based on the name of the second component;

[0188] The release module is used to release the pit to be removed indicated by the name of the pit to be removed, and set the pit to be removed as an unallocated pit.

[0189] A11. A mobile terminal, characterized by comprising the component management device of claims 6-10.

[0190] A12. A mobile terminal, comprising: a memory for storing executable instructions;

[0191] And a processor, configured to communicate with the memory to execute the executable instructions to complete the operation of the component management method of claims 1-5.

[0192] Those skilled in the art will easily think of other embodiments of the present invention after considering the description and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptive changes of the present invention. These variations, uses or adaptive changes follow the general principles of the present invention and include common knowledge or conventional technical means in the technical field not disclosed in this disclosure. . The description and the embodiments are to be regarded as exemplary only, and the true scope and spirit of the present invention are pointed out by the following claims.

[0193] It should be understood that the present invention is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present invention is only limited by the appended claims.