Equipment management method and device, electronic equipment, storage medium and program product

Abstract

The invention provides an equipment management method and device, electronic equipment, a storage medium and a program product, and the method comprises the steps: monitoring a contact event of a first object, the first object being equipment or a user identification card corresponding to the equipment, and when the first contact event of the first object is monitored, carrying out life cycle management on the first object, and carrying out life cycle management on the second object based on the event mapping relationship between the equipment and the user identification card. According to the invention, the life cycle of the first object is managed by monitoring the first contact event of the first object, and the life cycle of the second object is managed according to the event mapping relation between the equipment and the user identification card. Through the mapping between the user identification card and the life cycle of the equipment, the life cycle of the equipment and the user identification card is managed, and the unification of the life cycles of the equipment and the user identification card is ensured.

Description

Technical Field

[0001] The present disclosure relates to the technical field of device management, and in particular to a device management method, apparatus, electronic device, storage medium, and program product. Background Art

[0002] Currently, vehicles on the market primarily manage their lifecycles through touchpoint events, but the lifecycle of the user identification card (UIC) cannot be linked back to the vehicle's lifecycle. When a UIC's lifecycle node changes, automakers are unable to detect and modify the vehicle's lifecycle node simultaneously. Manual management of the vehicle's lifecycle is required based on the UIC's lifecycle node. This cumbersome management method prevents timely alignment of the UIC and vehicle lifecycle nodes. Summary of the Invention

[0003] In view of the above problems, the present disclosure is proposed. The present disclosure provides a device management method, apparatus, electronic device, storage medium and program product.

[0004] In a first aspect, the present disclosure provides a device management method, including: monitoring contact events of a first object, where the first object is: a device, or a user identification card corresponding to the device; when a first contact event of the first object is monitored, performing lifecycle management on the first object; based on an event mapping relationship between the device and the user identification card, performing lifecycle management on a second object; wherein, when the first object is a device, the second object is a user identification card; when the first object is a user identification card, the second object is a device.

[0005] In an embodiment of the first aspect, when a first contact event of a first object is monitored, lifecycle management is performed on the first object, including: when a first contact event of the first object is monitored, based on a pre-configured first configuration rule, obtaining a first atomic action corresponding to the first contact event; based on the first atomic action, switching the life management state of the first object; wherein the first contact event includes at least one of the following: a change in the state of a user identification card, a change in the state of a device; and the first atomic action includes at least one of the following: communication management, service function management, and lifecycle switching.

[0006] In an embodiment of the first aspect, the method further includes: reading a first configuration rule stored in a database; and loading the first configuration rule into a memory.

[0007] In an embodiment of the first aspect, life cycle management of a second object is performed based on an event mapping relationship between a device and a user identification card, including: determining a second touch event corresponding to a first touch event based on an event mapping relationship between the device and the user identification card; obtaining a second atomic action corresponding to the second touch event based on a pre-configured second configuration rule; switching the life management state of the second object based on the second atomic action; wherein the second touch event includes at least one of the following: communication management, service function management, and life cycle switching; the second atomic action includes at least one of the following: communication management, service function management, and life cycle switching.

[0008] In an embodiment of the first aspect, one device corresponds to M user identification cards, where M is an integer greater than 0; the M user identification cards correspond one-to-one to the M event mapping relationships, and there is one event mapping relationship between the device and each of the M user identification cards.

[0009] In an embodiment of the first aspect, a device includes N life cycles, where N is an integer greater than 0, and a device uniquely corresponds to a life cycle at a point in time. The method also includes: switching the first life cycle corresponding to the device to a second life cycle according to a user operation.

[0010] In an embodiment of the first aspect, the device includes a vehicle, and the user identification card includes a vehicle user identification card.

[0011] In the second aspect, the present disclosure provides a device management device, including: an event acquisition module, configured to monitor the contact events of a first object, where the first object is: a device, or a user identification card corresponding to the device; a first object management module, configured to perform lifecycle management on the first object when a first contact event of the first object is monitored; a second object management module, configured to perform lifecycle management on the second object based on the event mapping relationship between the device and the user identification card; wherein, when the first object is a device, the second object is a user identification card; when the first object is a user identification card, the second object is a device.

[0012] In a third aspect, the present disclosure provides an electronic device, comprising: a memory for storing computer-readable instructions; and a processor for executing the computer-readable instructions so that the electronic device executes the method as described in any embodiment of the first aspect.

[0013] In a fourth aspect, the present disclosure provides a non-transitory computer-readable storage medium for storing computer-readable instructions, which, when executed by a processor, causes the processor to execute the method described in any embodiment of the first aspect.

[0014] In a fifth aspect, the present disclosure provides a computer program product, comprising a computer program, which, when executed by a processor, implements the method described in any embodiment of the first aspect.

[0015] This disclosure provides a device management method that manages the lifecycle of a first object by monitoring a first touch event of the first object, and manages the lifecycle of a second object based on an event mapping relationship between the device and a subscriber identity card. By mapping the lifecycles of the subscriber identity card and the device, the lifecycles of the device and the subscriber identity card are managed in a timely manner, ensuring the unification of their lifecycles.

[0016] It is to be understood that both the foregoing general description and the following detailed description are exemplary, and are intended to provide further explanation of the technology as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other purposes, features, and advantages of the present disclosure will become more apparent through a more detailed description of the embodiments of the present disclosure in conjunction with the accompanying drawings. The accompanying drawings are intended to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and are not intended to limit the present disclosure. In the drawings, the same reference numerals generally represent the same components or steps.

[0018] Figure 1 A schematic diagram of a device management method according to an embodiment of the present disclosure;

[0019] Figure 2 A schematic diagram of vehicle lifecycle management provided by an embodiment of the present disclosure;

[0020] Figure 3 A schematic diagram of vehicle life cycle management according to an embodiment of the present disclosure;

[0021] Figure 4 A schematic diagram of a vehicle life cycle switching path provided by an embodiment of the present disclosure;

[0022] Figure 5 A schematic diagram of multi-network convergence lifecycle switching provided by an embodiment of the present disclosure;

[0023] Figure 6 A schematic diagram of multi-brand vehicle life cycle switching provided by an embodiment of the present disclosure;

[0024] Figure 7 A structural block diagram of a device management apparatus provided in an embodiment of the present disclosure;

[0025] Figure 8 A hardware block diagram of an electronic device provided in an embodiment of the present disclosure;

[0026] Figure 9 A schematic diagram of a computer-readable storage medium provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solutions and advantages of the present disclosure more apparent, the following will describe in detail exemplary embodiments of the present disclosure with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited to the exemplary embodiments described herein.

[0028] To clarify the stage information of equipment or services and provide strong support for subsequent decision-making, customers can use the equipment lifecycle to understand the equipment status and perform operations such as repair and scrapping based on the equipment status. Enterprises can also use the lifecycle to measure equipment or services and make subsequent decisions. For example, when a vehicle is in use, customers can understand the vehicle status through the vehicle lifecycle, manage the vehicle scientifically, and maximize the vehicle's service life. In addition, vehicle brands can use the lifecycle management system to count the number of vehicles under their brand and view the details of specific vehicles and the brand packages purchased according to different categories, to facilitate the company's subsequent package development.

[0029] However, current enterprise lifecycle management may only be adaptable to the internal processes of a specific enterprise. Taking vehicle brands as an example, some vehicle brands hard-code the vehicle's lifecycle trigger events and execution rules into the lifecycle management platform. When the trigger event is met, the vehicle's lifecycle is switched according to the execution rules to achieve vehicle lifecycle management. However, this approach has poor scalability. When the trigger event or execution rule changes, the system may need to be rebuilt, resulting in a waste of resources. Furthermore, if there is a problem with vehicle information feedback, information such as vehicle usage, maintenance, and repairs may be lost and cannot be updated to the MNO in a timely manner, resulting in the inability to automatically correct the vehicle status. Customers and enterprises are also unable to promptly understand the specific status of the vehicle.

[0030] In order to solve the above problems, the present disclosure provides a device management method, which can synchronize the life cycle of the device to the user identification card. By triggering the contact event of the user identification card by the customer, the life cycle corresponding to the contact event of the user identification card is obtained, thereby realizing the mapping of the life cycle corresponding to the contact event between the user identification card and the device, and realizing the life cycle management of the device. Figure 1 A flow chart of a device management method provided by an embodiment of the present disclosure is shown as follows: Figure 1 As shown, the specific methods include:

[0031] S101, monitoring a touch event of a first object, where the first object is: a device, or a user identification card corresponding to the device.

[0032] S102: When a first touch event of a first object is monitored, lifecycle management is performed on the first object.

[0033] S103: Perform lifecycle management on the second object based on the event mapping relationship between the device and the subscriber identity card. When the first object is a device, the second object is the subscriber identity card; when the first object is a subscriber identity card, the second object is a device.

[0034] In this embodiment, the method can be applied to a lifecycle management system. As shown in step S101, the first object can be a device that can independently install a user identification card for network communication, including but not limited to at least one of the following: a vehicle, a mobile phone, a tablet computer, etc. The first object can also be a user identification card, including but not limited to at least one of the following: an Internet of Vehicles card, an Industrial Internet of Things card, an Agricultural Internet of Things card, etc. Among them, a user identification card can uniquely correspond to one device. When monitoring the first object, the monitoring method can be based on different event types, including but not limited to any one of an application program interface, a sensor, and a hardware interface.

[0035] When the lifecycle management system monitors that the first object triggers a first touch event, as shown in step S102, it can perform lifecycle management on the first object. The lifecycle management system can monitor the touch event of at least one first object, which can be a device or a user identification card.

[0036] In a possible embodiment, both the device and the user identification card may be monitored simultaneously. When it is monitored that either the device or the user identification card triggers a first touch event, lifecycle management is performed according to this solution.

[0037] A contact event can be understood as an event that is actively triggered by the first object. The first contact event here can be set with different corresponding events depending on the first object. The first contact event can be a change in the object state of the first object, including but not limited to at least one of the following: a change in the state of the user identification card, a change in the state of the device. For example, when the first object is a vehicle, the first contact event can include but is not limited to at least one of the following: a change in the vehicle package, a change in the user to whom the vehicle belongs, and the state of the Internet of Vehicles card. For another example, when the first object is an Internet of Vehicles card, the first contact event can include but is not limited to the transition from a test period to a formal period, separation of the machine and the card, and conversion from shutdown to account cancellation.

[0038] When the life cycle of the first object is changed due to the first object triggering the first contact event, as shown in step S103, the life cycle of the second object can be managed according to the event mapping relationship between the device and the subscriber identification card. When the first object is a device, the second object can be a subscriber identification card. When the first object is a subscriber identification card, the second object can be a device. For ease of understanding, when the subscriber identification card causes the node of its life cycle to change, since there is a mapping relationship between the life cycle nodes of the subscriber identification card and the device, the node of the device life cycle corresponding to the node of the life cycle of the subscriber identification card is obtained, thereby the device is carried out life cycle management. Wherein, the life cycle node name of the subscriber identification card can be identical with the name of the device life cycle node, or it can be different, and can be set by the enterprise according to actual conditions. Further, any life cycle node of the first object corresponds to the life cycle node of the second object at least. A device uniquely corresponds to a life cycle node at a time point, and a subscriber identification card uniquely corresponds to a life cycle node at a time point.

[0039] In an exemplary embodiment, for ease of understanding, the lifecycle management of a vehicle is taken as an example. In this case, the lifecycle management system may be a vehicle network lifecycle management system. Figure 2 A schematic diagram of vehicle life cycle management provided by an embodiment of the present disclosure, such as Figure 2As shown, the user identification card can be a vehicle user identification card, and the device can be a vehicle. A smart vehicle management platform (MNO) can receive first-touch events monitored by a vehicle terminal (e.g., an in-vehicle application) or a mobile application (e.g., a brand client). First-touch events may include, but are not limited to, changes in vehicle packages, changes in vehicle ownership, and changes in the status of the Internet of Vehicles (IoV) card. Vehicle packages may include, but are not limited to, at least one of the following: maintenance items for different vehicle parts and systems, insurance, etc. Because vehicle performance and reliability can be maintained through maintenance items included in the packages, the vehicle's service life is extended, thereby impacting the vehicle's lifecycle. Changes in IoV card status include, but are not limited to, at least one of the following: transitioning from a test period to a full-fledged period, separating the card from the vehicle, or deactivating the card from service. The MNO can also receive IoV card status information from the car manufacturer or its production line, including, but not limited to, at least one of the following: vehicle-card binding / unbinding, IoV card registration, etc. These first-touch events are then synchronized with the MNO, which transparently transmits this data to the IoV lifecycle management system. The IoV lifecycle management system manages the lifecycle. The management results are sent to the IoV card and the vehicle, and the IoV card status information is synchronized with the IoV network element. The IoV network element can interact with the vehicle terminal through the IoV and store the vehicle network card data. Furthermore, the IoV lifecycle management system can also send management results to the vehicle manufacturer, notifying them of the IoV card's current status or lifecycle milestones.

[0040] Furthermore, after obtaining the first touch event, the lifecycle management system can obtain the lifecycle node of the device or user identification card according to the first touch event, thereby determining subsequent operations. The specific method includes:

[0041] When a first touch event of a first object is monitored, a first atomic action corresponding to the first touch event is obtained based on a pre-configured first configuration rule.

[0042] Based on the first atomic action, the life management state of the first object is switched, wherein the first contact event includes at least one of the following: the state of the user identification card changes, the state of the device changes, and the first atomic action includes at least one of the following: communication management, service function management, and life cycle management.

[0043] In this embodiment, when the lifecycle management system monitors a first touch event of a first object, it can obtain a first atomic action corresponding to the first touch event based on a first configuration rule. The first configuration rule can be understood as the correspondence between the first touch event and the first atomic action. An atomic action can be understood as the smallest operation in lifecycle management, including but not limited to at least one of: opening / closing a communication channel, voice function management, SMS function management, and lifecycle switching. The first configuration rule can be stored in a database and loaded into memory. The first configuration rule can be independently developed by the enterprise or configured by the system. The first atomic action can include but is not limited to at least one of the following: communication management, service function management, and lifecycle switching. Communication management can be understood as changing the automatic linkage state of the user identification card based on changes in the user identification card status. Lifecycle management refers to switching the life management state of the user identification card and the device based on the first touch event. The life management state here can be understood as the lifecycle node of the first object at that time, and each lifecycle node corresponds to at least one touch event. Service function management refers to setting different service functions based on different first touch events. After the first object triggers the first touch event, the service function permissions of the user identification card or the device need to be switched.

[0044] Furthermore, the lifecycle management system also needs to manage the lifecycle of the second object based on the first touch event. The specific method may include: determining the second touch event corresponding to the first touch event based on the event mapping relationship between the device and the user identification card, obtaining the second atomic action corresponding to the second touch event based on the pre-configured second configuration rule, and switching the life management state of the second object based on the second atomic action. Among them, any second touch event corresponds to at least one first touch event, and any second touch event corresponds to at least one second atomic action. The second atomic action may include but is not limited to at least one of the following: communication management, service function management, and lifecycle switching. According to the event mapping relationship within the lifecycle management system, a correspondence can be established between the first touch event and the second touch event. The second configuration rule can be understood as a correspondence between the second touch event and the second atomic action. Therefore, the second touch event can be obtained based on the first touch event, and the corresponding second atomic action can be obtained based on the second touch event, and the lifecycle node of the second object is managed by the lifecycle management system.

[0045] For ease of understanding, let’s take the vehicle lifecycle management as an example. When the IoV lifecycle management system detects that the IoV card (i.e., user identification card) is activated (i.e., the first touch event), Figure 2As shown, when the life cycle node of the Internet of Vehicles card can be changed from testable to activated, the Internet of Vehicles life cycle management system can jointly manage the life cycle node of the vehicle (ie, the first atomic action) according to the first configuration rule. Figure 3 A schematic diagram of the vehicle life cycle corresponding management provided by the embodiment of the present disclosure, such as Figure 3 As shown, for ease of understanding, the vehicle lifecycle nodes can be set as: testing period, pending sale period, official period, and maintenance period. The IoV card lifecycle nodes can be set as: testable, activated, and shut down. The vehicle's testing period can correspond to the IoV card's testability, the vehicle's pending sale period and official period can correspond to the IoV card's activation, and the vehicle's maintenance period can correspond to the IoV card's shutdown. For example, some IoV cards have specific card status switching rules, such as automatically transitioning to the official period 180 days after activation. When the IoV card automatically transitions from testable to activated, the vehicle also transitions from the testing period to the pending sale period, and the communication channel is simultaneously closed (i.e., the first atomic action) for real-name management and control. For another example, when the vehicle's user unconventionally removes the IoV card's communication module (a first touch event), and the module contains an IoV card, resulting in a vehicle-card separation, the IoV lifecycle management system can, based on the event mapping relationship, obtain the IoV card's second touch event: vehicle-card separation. Therefore, the life cycle node of the vehicle is also changed from the formal period to the maintenance period (the first atomic action). At the same time, the Internet of Vehicles life cycle management system converts the life cycle node of the Internet of Vehicles card to shut down (the second atomic action).

[0046] It should be understood that the above lifecycle node settings are only for ease of understanding, and do not actually impose specific restrictions on the correspondence and settings of vehicle and vehicle network card lifecycle nodes, and can be adjusted according to actual conditions.

[0047] At present, considering that users may choose packages or services provided by multiple companies according to their needs, or due to the replacement of user identification cards, there may be multiple user identification cards under the user's name. If the network types of the user identification cards held by the user are different, it constitutes a multi-network fusion scenario. At this time, different types of user identification cards may result in different life cycle nodes, and the mapping relationship between them and the life cycle nodes of the device is also different. Therefore, in order to synchronize the life cycle management information between different types of user identification cards, it is necessary to establish an event mapping relationship between different types of user identification cards and devices. The specific method may include:

[0048] One device corresponds to M user identification cards, where M is an integer greater than 0, and the M user identification cards correspond to M event mapping relationships in a one-to-one correspondence.

[0049] There is an event mapping relationship between the device and each of the M user identification cards.

[0050] In a kind of exemplary embodiment, can set up the mapping relations between all Subscriber Identity Modules and the equipment, promptly there is mapping relation between the life cycle node of any Subscriber Identity Module all and the life cycle node of equipment.Life cycle management system can obtain the life cycle node of equipment by the life cycle node of the first Subscriber Identity Module, thereby according to the mapping relations between the life cycle node of equipment and the second Subscriber Identity Module, obtain the life cycle node of the second Subscriber Identity Module.In addition, life cycle management system also can directly obtain the life cycle node of the second Subscriber Identity Module according to the life cycle node of equipment.

[0051] In another embodiment, a mapping relationship between touch events of different types of user identification cards can be established. For example, user identification cards can be divided into 4G user identification cards and 5G user identification cards based on the different communication technologies used. That is, based on the mapping relationship between the touch events of the first user identification card and the touch events, the touch events of the second user identification card are obtained, and based on the touch events, the corresponding atomic actions are obtained, thereby managing the life cycle of the second user identification card.

[0052] In another embodiment, the mapping relation between the life cycle nodes of different subscriber identification cards can also be directly set up.For example, there is a corresponding relation between the life cycle node of equipment and the life cycle node of the first subscriber identification card, and there is a corresponding relation between the life cycle node of the first subscriber identification card and the life cycle node of the second subscriber identification card. The life cycle management system can obtain the life cycle node of the corresponding first subscriber identification card according to the life cycle node of equipment, thereby obtains the life cycle node of the second subscriber identification card corresponding to the life cycle node of the first subscriber identification card.

[0053] For ease of understanding, when the life cycle nodes of two user identification cards are the same, Figure 4 A schematic diagram of a vehicle life cycle switching path provided by an embodiment of the present disclosure, such as Figure 4As shown, the lifecycle nodes of two IoV cards (i.e., user identification cards) can include, but are not limited to, inventory, testable, pending activation, activated, shut down, pre-cancelled, and canceled. Inventory can be converted to pending activation and activated, corresponding to the vehicle display and vehicle sold scenarios, respectively. Testable can be converted to inventory, pending activation, activated, and shut down, corresponding to vehicle entry, vehicle display, vehicle sold, and vehicle / card separation, respectively. Pending activation can be converted to inventory and activated, corresponding to the vehicle entry and vehicle sold scenarios, respectively. An activated vehicle can be converted to shut down due to card separation, or it can be restored from shut down to activated. When a user cancels their account, an activated IoV card can be converted to pre-cancelled, and a pre-cancelled card can be converted to canceled. As noted above, some lifecycle nodes cannot be converted to other lifecycle nodes. Therefore, it is necessary to clearly define the switching paths for different IoV card types. First, the starting and target nodes for different IoV card types must be determined. If the starting and target nodes of two IoV cards match, no switching occurs. If the two are inconsistent, a switching path needs to be created. For example, if the first and second telematics cards have the same starting node (pending activation), the first card's target node is a pre-sold account, while the second card's target node is inventory. If a valid switching path cannot be formed between the two, the telematics lifecycle management system can issue a switching failure alert. If a switching path exists, it can be switched.

[0054] Furthermore, according to different communication requirements of users, Figure 5 A schematic diagram of multi-network fusion life cycle switching provided by an embodiment of the present disclosure, such as Figure 5As shown, a vehicle's card slot 1 can be bound to a 4G car networking card, and a vehicle's card slot 2 can be bound to a 5G car networking card. The lifecycle nodes of a 4G car networking card can include testable, activated, and shut down. Testable is mapped to the vehicle's testing period, activated is mapped to the vehicle's pending sale period and official period, and shut down is mapped to the vehicle's maintenance period. The lifecycle nodes of a 5G car networking card can include testable, pending activation, activated, and shut down. Testable is mapped to the vehicle's testing period, pending activation is mapped to the vehicle's pending sale period, activated is mapped to the vehicle's official period, and shut down is mapped to the vehicle's maintenance period. When the first trigger event is the vehicle owner's real-name registration, the car networking lifecycle management system automatically identifies the two card slots bound to the device, finds the lifecycle node corresponding to the trigger event, and performs APN operations on the cards in both slots based on the atomic actions corresponding to the lifecycle nodes. For 4G car networking cards, since both the pending sale period and the official period are mapped to activated, the car networking card lifecycle does not switch. For 5G vehicle networking cards, since there is a one-to-one relationship in the life cycle, the card life cycle (the second atomic action) is switched from pending activation to activated, and then the corresponding 5G-APN channel is opened and the corresponding trial package is given.

[0055] Furthermore, in addition to regular models, some brand companies have business scenarios where they manage multiple models, such as exhibition vehicles and special vehicles. Atomic actions also include, but are not limited to, free packages and package integration.

[0056] In an exemplary embodiment, for a company with multiple brands, there are two aspects: brand management and enterprise management. Enterprise management can be responsible for user identity card binding / unbinding and other user identity card status information. Brand management can be responsible for gift packages.

[0057] For ease of understanding, Figure 6 A schematic diagram of the life cycle switching of a multi-brand vehicle provided by an embodiment of the present disclosure is shown as follows: Figure 6 As shown, depending on the purpose of the vehicle, for example, when it is used as a display vehicle, the vehicle's waiting period can be switched to the display vehicle inventory period. When the first touch event is the real-name registration of the display vehicle company, the vehicle's life cycle can be switched to the official display vehicle period. After the display vehicle is untied, the vehicle's life cycle node is switched to the maintenance period. When the vehicle is sold as a sub-brand vehicle, in order to facilitate the sub-brand to give away packages within the brand, the vehicle's life cycle can be switched to the sub-brand waiting period. At this time, the vehicle's life cycle nodes include but are not limited to: sub-brand waiting period, sub-brand official period and sub-brand maintenance period, so that the brand can give away packages to users based on the life cycle nodes, facilitate management, and avoid brand overreach.

[0058] The above embodiments can all be applied to the same system, specifically including: monitoring a touch event of the first object.

[0059] The first configuration rule stored in the database is read.

[0060] Load the first configuration rule into memory.

[0061] When a first touch event of a first object is monitored, a first atomic action corresponding to the first touch event is obtained based on a pre-configured first configuration rule.

[0062] Based on the first atomic action, the life management state of the first object is switched.

[0063] Determining a second touch event corresponding to the first touch event based on an event mapping relationship between the device and the user identification card;

[0064] Based on a pre-configured second configuration rule, obtaining a second atomic action corresponding to the second touch event;

[0065] Based on the second atomic action, the life management state of the second object is switched.

[0066] The present disclosure also provides a device management apparatus. Figure 7 A structural block diagram of a device management device provided in an embodiment of the present disclosure, such as Figure 7 As shown, the device management apparatus 700 includes: an event acquisition module 701, which is configured to monitor a touch event of a first object, where the first object is: a device, or a user identification card corresponding to the device.

[0067] The first object management module 702 is configured to perform lifecycle management on the first object when a first touch event of the first object is monitored.

[0068] The second object management module 703 is configured to perform lifecycle management on the second object based on the event mapping relationship between the device and the subscriber identity card.

[0069] When the first object is a device, the second object is a user identification card.

[0070] When the first object is a subscriber identity card, the second object is a device.

[0071] In an exemplary embodiment, the first object management module 702 is configured to obtain a first atomic action corresponding to the first contact event based on a pre-configured first configuration rule when monitoring a first contact event of the first object, and switch the life management state of the first object based on the first atomic action, wherein the first contact event includes at least one of the following: a change in the state of the user identification card, a change in the state of the device, and the first atomic action includes at least one of the following: communication management, service function management, and life cycle switching.

[0072] In an exemplary embodiment, the device management apparatus 700 further includes reading a first configuration rule stored in a database and loading the first configuration rule into a memory.

[0073] In an exemplary embodiment, the second object management module 703 is configured to determine the second touch event corresponding to the first touch event based on the event mapping relationship between the device and the user identification card, obtain the second atomic action corresponding to the second touch event based on a pre-configured second configuration rule, and switch the life management state of the second object based on the second atomic action, wherein the second touch event includes at least one of the following: communication management, service function management, and life cycle switching, and the second atomic action includes at least one of the following: communication management, service function management, and life cycle switching.

[0074] In an exemplary embodiment, the device management apparatus 700 further includes one device corresponding to M user identification cards, where M is an integer greater than 0, the M user identification cards correspond one to one with M event mapping relationships, and there is one event mapping relationship between the device and each of the M user identification cards.

[0075] In an exemplary embodiment, the device management apparatus 700 further includes a device including N life cycles, where N is an integer greater than 0. A device uniquely corresponds to a life cycle at a point in time, and according to user operations, the first life cycle corresponding to the device is switched to the second life cycle.

[0076] In an exemplary embodiment, the device management apparatus 700 further includes a device including a vehicle, and the user identification card includes a vehicle user identification card.

[0077] Figure 8 This is a hardware block diagram of an electronic device provided in an embodiment of the present disclosure. The electronic device 800 according to an embodiment of the present disclosure includes at least a processor and a memory for storing computer-readable instructions. When the computer-readable instructions are loaded and executed by the processor, the processor executes the device management method of any of the preceding embodiments of the present disclosure.

[0078] Figure 8The electronic device 800 shown specifically includes: a central processing unit (CPU) 801, a graphics processing unit (GPU) 802, and a memory 803. These units are interconnected via a bus 804. The central processing unit (CPU) 801 and / or the graphics processing unit (GPU) 802 can be used as the above-mentioned processor, and the memory 803 can be used as the above-mentioned memory for storing computer-readable instructions. In addition, the electronic device 800 may also include a communication unit 805, a storage unit 806, an output unit 807, an input unit 808, and an external device 809, which are also connected to the bus 804.

[0079] Figure 9 A schematic diagram of a computer-readable storage medium provided in an embodiment of the present disclosure. Figure 9 As shown, a computer-readable storage medium 900 according to an embodiment of the present disclosure has computer-readable instructions 901 stored thereon. When the computer-readable instructions 901 are executed by a processor, the device management method described with reference to the above figures according to any of the above embodiments of the present disclosure is executed. The computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0080] The present disclosure further provides a computer program product, including a computer program, which implements the device method described in any of the above embodiments of the present disclosure when executed by a processor.

[0081] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0082] The basic principles of the present disclosure have been described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, and effects mentioned in this disclosure are merely illustrative and not restrictive, and should not be construed as necessarily possessed by each embodiment of the present disclosure. Furthermore, the specific details disclosed above are provided for illustrative purposes and to facilitate understanding, rather than as limitations. These details do not limit the present disclosure to necessarily being implemented using these specific details.

[0083] The block diagrams of the devices, devices, equipment, and systems involved in this disclosure are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, devices, equipment, and systems can be connected, arranged, or configured in any manner. Words such as "include," "comprise," "have," and the like are open-ended words, meaning "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and / or" and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.

[0084] Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

[0085] It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0086] Various changes, substitutions, and modifications may be made to the technology described herein without departing from the teachings defined by the appended claims. Moreover, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of things, means, methods, and actions described above. Currently existing or later developed processes, machines, manufactures, compositions of things, means, methods, or actions that perform substantially the same function or achieve substantially the same results as the corresponding aspects described herein may be utilized. Accordingly, the appended claims include within their scope such processes, machines, manufactures, compositions of things, means, methods, or actions.

[0087] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0088] The above description has been provided for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although a number of example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A device management method, characterized in that: The method comprises: Monitoring a touch event of a first object, where the first object is: a device, or a user identification card corresponding to the device; When a first touch event of the first object is monitored, performing lifecycle management on the first object; Performing lifecycle management on the second object based on the event mapping relationship between the device and the user identification card; Wherein, when the first object is a device, the second object is the user identification card; When the first object is the subscriber identification card, the second object is the device.

2. The method according to claim 1, characterized in that When the first touch event of the first object is monitored, performing lifecycle management on the first object includes: When a first touch event of the first object is monitored, obtaining a first atomic action corresponding to the first touch event based on a pre-configured first configuration rule; Switching the life management state of the first object based on the first atomic action; The first touch event includes at least one of the following: a change in the state of the user identification card, a change in the state of the device; The first atomic action includes at least one of the following: communication management, service function management, and life cycle switching.

3. The method according to claim 2, characterized in that The method further comprises: Reading the first configuration rule stored in the database; The first configuration rule is loaded into the memory.

4. The method according to claim 1, wherein The performing lifecycle management on the second object based on the event mapping relationship between the device and the user identification card includes: Determining a second touch event corresponding to the first touch event based on an event mapping relationship between the device and the user identification card; Based on a pre-configured second configuration rule, obtaining a second atomic action corresponding to the second touch event; Switching the life management state of the second object based on the second atomic action; Wherein, the second touch event includes at least one of the following: communication management, service function management, and life cycle switching; The second atomic action includes at least one of the following: communication management, service function management, and life cycle switching.

5. The method according to any one of claims 1 to 4, characterized in that One of the devices corresponds to M user identification cards, where M is an integer greater than 0; The M user identification cards correspond to the M event mapping relationships in a one-to-one manner; There is an event mapping relationship between the device and the M user identification cards respectively.

6. The method according to any one of claims 1 to 5, characterized in that One of the devices includes N life cycles, where N is an integer greater than 0, and one of the devices uniquely corresponds to one life cycle at a point in time. The method further includes: According to a user operation, the first life cycle corresponding to the device is switched to the second life cycle.

7. The method according to any one of claims 1 to 6, characterized in that The equipment includes: a vehicle; The user identification card includes: a vehicle user identification card.

8. A device management device, characterized in that: The device comprises: An event acquisition module is configured to monitor a touch event of a first object, where the first object is: a device, or a user identification card corresponding to the device; a first object management module, configured to perform lifecycle management on the first object when a first touch event of the first object is monitored; A second object management module is configured to perform lifecycle management on the second object based on the event mapping relationship between the device and the user identification card; Wherein, when the first object is a device, the second object is the user identification card; When the first object is the subscriber identification card, the second object is the device.

9. An electronic device, characterized in that: include: a memory for storing computer-readable instructions; as well as A processor is configured to execute the computer-readable instructions so that the electronic device performs the method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium for storing computer-readable instructions, characterized in that: When the computer-readable instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The method comprises a computer program, which implements the method according to any one of claims 1 to 7 when the computer program is executed by a processor.

Images