CN115509619A - Operating system event processing method, operating system, electronic device and storage medium - Google Patents

Operating system event processing method, operating system, electronic device and storage medium Download PDF

Info

Publication number
CN115509619A
CN115509619A CN202211178771.0A CN202211178771A CN115509619A CN 115509619 A CN115509619 A CN 115509619A CN 202211178771 A CN202211178771 A CN 202211178771A CN 115509619 A CN115509619 A CN 115509619A
Authority
CN
China
Prior art keywords
operating system
event
target operating
module
system event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211178771.0A
Other languages
Chinese (zh)
Inventor
张磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fibocom Wireless Inc
Original Assignee
Fibocom Wireless Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fibocom Wireless Inc filed Critical Fibocom Wireless Inc
Priority to CN202211178771.0A priority Critical patent/CN115509619A/en
Publication of CN115509619A publication Critical patent/CN115509619A/en
Priority to PCT/CN2023/111687 priority patent/WO2024066748A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The application relates to an operating system event processing method, an operating system, an apparatus, an electronic device, a storage medium and a computer program product. The method comprises the following steps: acquiring a target event identifier corresponding to a target operating system event; identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event. According to the method, the kernel-mode filtering driver module of the operating system is used for processing the operating system events, and the kernel-mode filtering driver can be realized by utilizing the open interface and the drive model of the operating system, so that the operating system events are processed, and the open dependence on module codes can be effectively avoided.

Description

Operating system event processing method, operating system, electronic device and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to an operating system event processing method, an operating system, an apparatus, an electronic device, a storage medium, and a computer program product.
Background
In recent years, with the advent of new services for PCs (Personal computers), such as services for PC security tracking, PC rental, PC remote maintenance, and PC billing service, new technical requirements have been placed on communication modules directed to the PC industry. Firstly, a communication module is required to meet the requirement of instant networking of a terminal user and realize real-time online tracking management of a PC full application scene; secondly, the network flow required by the equipment management function of the communication module is required to be settled based on an independent tariff packet, so that a terminal user can open or terminate corresponding services at any time; and thirdly, the equipment management service of the communication module can not interfere the normal use of the terminal user for the PC, namely, the terminal user can not sense the equipment management service.
In order to meet the above requirements, the communication Module is usually integrated with a device management service, a dual card single standby Module, and a built-in embedded SIM (Subscriber Identity Module) card. When a terminal User needs to use the module to perform networking service, the extrapolated SIM card is used for data dialing, otherwise, the terminal User is switched to the embedded SIM card for equipment management service, and the influence on a system UI (User Interface) is avoided by switching the extrapolated SIM card and the embedded SIM card and shielding related events. Most of the traditional methods are code integration in the external module, which has too large open dependency on the external module code.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an operating system event processing method, an operating system, an apparatus, an electronic device, a computer-readable storage medium, and a computer program product, which are capable of opening without depending on an external module code.
In a first aspect, the present application provides a method for processing an event of an operating system, where the operating system includes a configuration module and a filter driver module running in a kernel state, and the filter driver module is in communication connection with the configuration module, and the method is applied to the filter driver module. The method comprises the following steps:
acquiring a target event identifier corresponding to a target operating system event;
identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier;
determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event;
and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
In one embodiment, the operating system further comprises an application module running in a user mode, and the application module is connected with the filter driver module in a communication manner; the determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of the configuration module related to the target operating system event comprises the following steps:
when the working mode of the configuration module related to the target operating system event is a non-equipment management mode, uploading the target operating system event to the application module; the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identity identification card;
and when the working mode of the configuration module related to the target operating system event is an equipment management mode, determining the processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the module is the operation related to the embedded SIM card.
In one embodiment, the event types comprise a type of event and a type of event; when the working mode of the configuration module related to the target operating system event is the device management mode, determining the processing strategy of the operating system event according to the event type of the target operating system event, including:
when the event type is a type of event, shielding the target operating system event; the event of the same type is an event reported to the application module by the configuration module;
when the event type is a second-class event, issuing a working mode switching instruction to enable the working mode of the configuration module to be switched from the equipment management mode to a non-equipment management mode, then issuing an execution request for the target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; the second type of event is an event issued by the application module to the configuration module.
In one embodiment, the obtaining a target event identifier corresponding to a target operating system event includes:
when first event identifiers corresponding to a plurality of operating system events are acquired at the same time, determining a target operating system event from the operating system events according to the priority of the first event identifiers, and acquiring a target event identifier corresponding to the target operating system event.
In a second aspect, the present application further provides an operating system, where the operating system includes a configuration module and a filter driver module running in a kernel state, and the configuration module is communicatively connected to the filter driver module; wherein the content of the first and second substances,
the configuration module is used for managing operating system events and the working mode of the configuration module;
the filtering driving module is used for acquiring a target event identifier corresponding to a target operating system event; identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; according to the processing strategy of the target operating system event, correspondingly processing the target operating system event; the target operating system event is any one of the operating system events.
In one embodiment, the operating system further comprises an application module running in a user mode, and the application module is in communication connection with the filter driver module;
the filtering driving module is further configured to upload the target operating system event to the application module when a working mode of a configuration module related to the target operating system event is a non-device management mode; the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identity identification card; when the working mode of the configuration module related to the target operating system event is an equipment management mode, determining a processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the module is the operation related to the embedded SIM card;
and the application module is used for executing the target operating system event uploaded by the filter driving module.
In one embodiment, the event types include a type of event and a type of event;
the filtering driving module is further configured to shield the target operating system event when the event type is a type of event; the event of the same type is an event reported to the application module by the configuration module; when the event type is a second-class event, issuing a working mode switching instruction to enable the working mode of the configuration module to be switched from the equipment management mode to a non-equipment management mode, then issuing an execution request for the target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; the second type of event is an event issued by the application module to the configuration module.
In one embodiment, the operating system further comprises a class extension module running in a kernel mode, and the class extension module is in communication connection with the configuration module and the filter driver module respectively;
the class extension module is used for converting the format of the operating system event managed by the configuration module from a first format to a second format;
the filtering driving module is further configured to obtain a target event identifier corresponding to a target operating system event in a second format from the class extension module, and identify an event type of the target operating system event and a working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
In a third aspect, the present application further provides an operating system event processing apparatus, where an operating system includes a configuration module and a filter driver module running in a kernel state, the filter driver module is communicatively connected to the configuration module, and the apparatus is applied to the filter driver module. The device comprises:
the identifier acquisition module is used for acquiring a target event identifier corresponding to a target operating system event;
the identifier identification module is used for identifying the event type of the target operating system event and the working mode of the configuration module related to the target operating system event according to the target event identifier;
the event policy module is used for determining a processing policy of the target operating system event according to the event type of the target operating system event and the working mode of the configuration module related to the target operating system event;
and the event processing module is used for correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
In a fourth aspect, the present application further provides an electronic device. The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor realizes the following steps when executing the computer program:
acquiring a target event identifier corresponding to a target operating system event;
identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier;
determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event;
and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
In a fifth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring a target event identifier corresponding to a target operating system event;
identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier;
determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event;
and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
In a sixth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
acquiring a target event identifier corresponding to a target operating system event;
identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier;
determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event;
and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
According to the operating system event processing method, the operating system, the operating device, the electronic equipment, the storage medium and the computer program product, the target event identifier corresponding to the target operating system event is obtained; identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event. According to the method and the device, the kernel-state filtering driver module of the operating system is used for processing the operating system events, the kernel-state filtering driver module can be used for processing the operating system events by utilizing an open interface and a drive model of the operating system, and open dependence on configuration module codes can be effectively avoided; in addition, according to the event type of the operating system event and the working mode of the configuration module related to the operating system event, the processing strategy of the operating system event can be accurately determined, and effective management of the operating system event is realized.
Drawings
FIG. 1 is a diagram of an application environment for a method of handling operating system events, according to an embodiment;
FIG. 2 is a flowchart illustrating a method for handling operating system events according to one embodiment;
FIG. 3 is a flowchart of step 206 in one embodiment;
FIG. 4 is a flowchart illustrating step 304 in one embodiment;
FIG. 5 is a diagram of an application environment of a method for handling operating system events in another embodiment;
FIG. 6 is a flowchart illustrating a method for handling operating system events in accordance with another embodiment;
FIG. 7 is a flowchart illustrating a method for handling operating system events in accordance with another embodiment;
FIG. 8 is a flowchart illustrating a method for handling operating system events in accordance with another embodiment;
FIG. 9 is a block diagram of an operating system in one embodiment;
FIG. 10 is a block diagram showing the structure of an operating system event processing device according to one embodiment;
FIG. 11 is a diagram illustrating the internal architecture of an electronic device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad application.
The operating system event processing method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The operating system may be configured with various configuration modules 102, such as a communication module; the configuration module 102 and the operating system may be connected to each other through a PCI-E (peripheral component interconnect express) bus or a USB (universal serial bus) bus, and may implement communication. The operating system comprises a filter driver module 104 and an application module 106, wherein the filter driver module 104 runs in an operating system kernel mode, and the filter driver module 104 communicates with the application module 106 in a user mode. The kernel mode filtering driver module 104 of the operating system acquires a target event identifier corresponding to a target operating system event, and identifies the event type of the target operating system event and the working mode of the configuration module 102 related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of the configuration module 102 related to the target operating system event; and according to the processing strategy of the target operating system event, performing corresponding processing on the target operating system event to determine whether to upload the target operating system event to the user mode application module 106. The operating system may be a Windows operating system, a Unix operating system, a Linux operating system, a MacOS operating system, or the like.
In one embodiment, as shown in fig. 2, an operating system event processing method is provided, which is described by taking the method as an example applied to the kernel-mode filter driver module in fig. 1, and includes the following steps 202 to 208.
Step 202, a target event identifier corresponding to a target operating system event is obtained.
The kernel-state filter driver module may obtain a target event identifier corresponding to the target system event from the configuration module or the application module. The drivers in the operating system can be divided into a user mode driver and a kernel mode driver, the user mode driver is executed in a user mode, the kernel mode driver is executed in a kernel mode, and the kernel mode driver can be divided into a high-level driver, a middle-level driver and a bottom-level driver. The high-level Driver comprises various File System Drivers (FSD), and depends on the middle-level Driver and the bottom-level Driver; the middle layer driver, such as a virtual disk, a mirror image or a device type specific class driver, depends on the support provided by the bottom layer driver, and can be further divided into a function driver and a filter driver, wherein the function driver is used for controlling a specific peripheral on one I/O bus. The kernel-state filter driver module in this embodiment belongs to an intermediate layer driver, and may be disposed above the function driver. The operating system in this embodiment includes an application module in which the configuration module operates in a user mode and a filter driver module in which the filter driver module operates in a kernel mode, where the filter driver module is in communication connection with the configuration module and the application module, respectively.
The operating system event refers to an event of mutual interaction between the configuration module and the user mode application module, and includes an event reported by the configuration module to the user mode application module, an event for the user mode application module to issue an instruction to the configuration module, and the like. The target operating system event may refer to any one of the operating system events. In this embodiment, the corresponding operating system event is characterized by an event identifier, and different operating system events correspond to different event identifiers, for example, the corresponding event identifier may be characterized by an NDIS (Network Driver Interface Specification) OID (Object identifier).
Step 204, identifying the event type of the target operating system event and the working mode of the configuration module related to the target operating system event according to the target event identifier.
In this embodiment, the target event identifier includes event type information of the target operating system event and working mode information of the configuration module corresponding to the target operating system event, for example, the event type of the corresponding target operating system event and the working mode of the corresponding configuration module may be identified according to a certain target event identifier. The event type information of the target operating system event and the working mode information of the configuration module corresponding to the target operating system event may respectively correspond to different positions in the target event identifier, that is, the event type and the working mode of the corresponding configuration module may be identified from the identifier at the corresponding position in the target event identifier.
Step 206, determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of the configuration module related to the target operating system event.
And the filtering driving module determines the processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of the configuration module related to the target operating system event. The processing policy of the target operating system event may be a first policy for directly uploading the target operating system event to the user mode application module, or a second policy for shielding the target operating system event, or a third policy for suspending the target operating system event and uploading the target operating system event to the user mode application module after a preset uploading condition is met, and the like. It should be noted that, in an actual application, the processing policy of the target operating system event is not limited to the above-mentioned cases, and may be set according to an actual application scenario.
In an alternative embodiment, the processing policy of the target operating system event may be determined according to the event type of the target operating system event in different working modes of the configuration module involved in the target operating system event. Or determining the processing strategy of the target operating system event according to the working mode of the configuration module related to the target operating system event when the target operating system event is in different event types.
And step 208, correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
And the filtering driving module carries out corresponding processing on the target operating system according to the processing strategy of the target operating system event. Specifically, the filter driver module may upload a target operating system event to the application module according to a first policy of directly uploading the target operating system event to the application module; according to a second strategy for shielding the target operating system event, shielding the target operating system event without processing; according to a third strategy that a target operating system event is suspended firstly and then uploaded to an application module after a preset uploading condition is met, the target operating system event is suspended, and then the target operating system event is uploaded to the application module after the preset uploading condition is judged to be met.
The operating system event processing method comprises the steps of obtaining a target event identifier corresponding to a target operating system event; identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event. According to the method and the device, the kernel-state filtering driver module of the operating system is used for processing the operating system events, the kernel-state filtering driver module can be used for processing the operating system events by utilizing the open interface and the open driver model of the operating system, and the open dependence on configuration module codes can be effectively avoided; in addition, according to the event type of the operating system event and the working mode of the configuration module related to the operating system event, the processing strategy of the operating system event can be accurately determined, the operating system event can be effectively managed, and therefore the terminal user cannot sense the equipment management service.
In one embodiment, the operating system further includes an application module running in a user mode, the application module is communicatively connected to the filter driver module, and as shown in fig. 3, the step 206 of determining the processing policy of the target operating system event includes steps 302 to 304 according to the event type of the target operating system event and the operating mode of the configuration module related to the target operating system event.
Step 302, when the working mode of the configuration module related to the target operating system event is a non-device management mode, uploading the target operating system event to an application module; the non-device management mode refers to that the operation executed by the configuration module is the operation related to the user identification card.
And when the working mode of the configuration module related to the target operating system event is a non-equipment management mode, the filter driving module directly uploads the target operating system event to the application module, wherein the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identity identification card. When the operation executed by the configuration module is an operation related to the user identity identification card, it indicates that the operation corresponding to the target operating system event corresponds to the application of the user mode application module at this time and needs to be uploaded to the user mode application module for processing, and therefore, the kernel mode filter driver module uploads the target operating system event to the user mode application module. It is understood that the subscriber identity module card in this embodiment may refer to an extrapolated SIM card, and the subscriber identity module card may enable the terminal device to enjoy services provided by a network operator, such as performing communication networking.
In this embodiment, when the working mode of the configuration module related to the target operating system event is the non-device management mode, the target operating system event may be directly uploaded to the user mode application module without considering the event type of the target operating system event, or the target operating system event may be directly executed, and the execution result of executing the target operating system event may be uploaded to the user mode application module.
Step 304, when the working mode of the configuration module related to the target operating system event is the device management mode, determining the processing policy of the target operating system event according to the event type of the target operating system event, wherein the device management mode refers to that the operation executed by the configuration module is an operation related to the embedded SIM card.
And when the working mode of the configuration module related to the target operating system event is an equipment management mode, the filter driving module determines the processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the configuration module is the operation related to the embedded SIM card. There are various event types of the target operating system event, and when the working mode of the configuration module related to the target operating system event is the device management mode, different event types correspond to different processing strategies.
Embedded SIM cards, also known as electronic SIM cards, i.e., eSIM cards, embed traditional SIM cards directly onto a device chip, rather than being added to the device as a separate removable component, and the user does not need to insert a physical SIM card. This will allow the user more flexibility in choosing a package of operators or changing operators at any time without having to unlock the equipment or purchase new equipment. In this embodiment, the embedded SIM card is used for device management services.
In one embodiment, as shown in FIG. 4, the event types include a type of event and a type of event; when the working mode of the configuration module involved in the target operating system event is the device management mode, the step 304 of determining the processing policy of the operating system event according to the event type of the target operating system event includes the following steps 402 to 404.
Step 402, when the event type is a type of event, shielding the target operating system event; one type of event is an event reported to the application module by the configuration module.
In this embodiment, when the event type of the target operating system event is a type of event, the filter driver module shields the target operating system event, where the type of event refers to an event reported by the configuration module to the user side. And shielding the target operating system event means that the data corresponding to the target operating system event is removed and is not continuously reported to the user mode application module.
Step 404, when the event type is a type two event, issuing a working mode switching instruction to switch the working mode of the configuration module from the device management mode to the non-device management mode, then issuing an execution request for the target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; wherein, the second kind of events are events issued by the application module to the configuration module.
In this embodiment, when the event type is a type two event, the kernel-mode filter driver module issues a working mode switching instruction to switch the working mode of the configuration module from the device management mode to the non-device management mode, after it is determined that the working mode of the configuration module is switched from the device management mode to the non-device management mode, the kernel-mode filter driver module issues an execution request of the target operating system event, and after receiving an execution result corresponding to the execution request of the target operating system event, uploads the corresponding execution result to the user-mode application module; the second type of events are events issued by the user mode application module to the configuration module.
In an optional embodiment, when the event type is a type two event, the kernel-state filter driver module issues a working mode switching instruction to the device mode management unit in the configuration module, the device mode management unit switches the working mode of the configuration module from the device management mode to the non-device management mode according to the working mode switching instruction, after the switching is completed, the device mode management unit returns a mode switching success instruction to the user-state filter driver module, after the kernel-state filter driver module receives the mode switching success instruction returned by the device mode management unit, the kernel-state filter driver module issues an execution request of the target operating system event to the configuration module, and after receiving an execution result corresponding to the execution request of the target operating system event, the corresponding execution result is uploaded to the user-state application module.
In the operating system event processing method in the embodiment, when the working mode of the configuration module related to the target operating system event is the device management mode, the processing policy of the event of the corresponding type is determined according to whether the event type of the target operating system event is a first type event or a second type event, and the corresponding processing policy can be accurately obtained for different types of events, so that whether the execution result corresponding to the target operating system event is reported to the user mode application module or not is accurately determined, and therefore it is ensured that a terminal user does not perceive the device management service.
In some embodiments, the operating system event processing method further includes: and when the second-class event is a system query event, obtaining the latest query result of the stored second-class event, and returning the latest query result to the application module.
Optionally, when the event type is a system query type event in the second type of events and the working mode of the corresponding configuration module is the non-device management mode, the kernel-state filter driver module directly issues an execution instruction corresponding to the operating system event, returns a received execution result corresponding to the execution instruction to the application module, and stores the execution result for use by a subsequent event.
When the event type is a system query type event in the second type of events and the working mode of the corresponding configuration module is an equipment management mode, directly obtaining the latest query result of the stored second type of events and reporting the latest query result to the application module, so that a terminal user cannot perceive the change of the working mode of the configuration module from the state of the corresponding interface of the application module.
In some embodiments, the target event identifier corresponding to the target operating system event is characterized by a network driver interface specification NDIS identifier.
NDIS, which spans the transmission layer, the network layer and the data link layer, defines the communication interface specification between the network card or the network card driver and the upper protocol driver, and shields the difference of the bottom layer physical hardware, so that the upper protocol driver can communicate with the network card of any type at the bottom layer. The NDIS creates a complete development environment for the network driver, only the NDIS function needs to be called, and the problems of a kernel of an operating system and interfaces with other drivers do not need to be considered, so that the network driver can be separated from complex communication with the operating system, and the network driver is greatly convenient to write.
In this embodiment, the target event identifier corresponding to the target operating system event is characterized by an NDIS OID, different target operating system events correspond to different target event identifiers, different target event identifiers correspond to different NDIS OIDs, and meanwhile, the NDIS OID includes event type information of the target operating system event and working mode information of a configuration module related to the target operating system event.
In one embodiment, the step 202 of obtaining a target event identifier corresponding to a target operating system event includes: when the first event identifiers corresponding to the multiple operating system events are acquired at the same time, the target operating system event is determined from the multiple operating system events according to the priority of the first event identifiers, and the target event identifier corresponding to the target operating system event is acquired.
When the first event identifiers corresponding to the multiple operating system events are acquired at the same time, the target operating system event is determined from the multiple operating system events according to the priority of the first event identifiers, and the target event identifier corresponding to the target operating system event is acquired.
Optionally, when the first event identifiers corresponding to the multiple operating system events are acquired simultaneously, the priorities of the multiple first event identifiers are sorted, the multiple operating system events are sequentially used as target operating system events according to the sequence from high to low of the priorities of the multiple first event identifiers, and the target event identifiers corresponding to the target operating system events are acquired.
In the above embodiment, when the first event identifiers corresponding to the multiple operating system events are acquired simultaneously, the target operating system event is determined from the multiple operating system events according to the priority of the first event identifier, and the kernel-mode filter driver can quickly and efficiently process the operating system event, so that the user terminal is more favorably unaware of the device management service.
In a specific example, the operating system event processing method is applied to an application environment shown in fig. 5, where the configuration module is a communication module, the class extension module is an MBB CX driver module, and the application module is a WWANSvc application module. The communication module comprises an equipment mode management unit and an MBIM (Mobile Broadband Interface Model) management unit, wherein the equipment mode management unit is connected with the MBIM management unit through an Interface to realize communication, and the equipment mode management unit is responsible for managing the working mode of the communication module, such as switching the working mode; an MBIM management unit, configured to manage the MBIM events in the communication module, for example, generate a corresponding MBIM command identifier (MBIM CID), where the MBIM CID is used to characterize the corresponding event in the communication module. The filtering driving module is connected with an MBB CX (Mobile broadband Band CX, mobile broadband WDF type extension) driving module, and is in a kernel state of an operating system, the MBB CX driving module is used for realizing the mutual conversion between an MBIM CID and an NDIS OID, the filtering driving module uploads operating system events corresponding to the NDIS OID to be uploaded to a WWANSVc (Wireless Wide Area Network service) application module, and the WWANSVc application module carries out corresponding processing according to the received operating system events.
The filtering driving module acquires a target event identifier NDIS OID corresponding to a target operating system event, and identifies the event type of the target operating system event and the working mode of the corresponding communication module according to the NDIS OID; and determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of the corresponding communication module, and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
Fig. 6 shows a processing flow of the filtering driver module to the operating system event when the event type is an event reported by the communication module to the WWANSvc application module, that is, the event type is a type of event. The communication module further comprises a protocol stack driving unit, which is used for detecting the change condition of the communication related parameters, for example, detecting the events such as the state change of an SIM card or the state change of a network, and uploading the corresponding events to the MBIM management unit, the MBIM management unit generates corresponding MBIM CID events, the MBIM management unit uploads the generated MBIM CID events to the MBB CX driving module, the MBB CX driving module generates corresponding NDIS OID events, and uploads the NDIS OID events to the kernel state filtering driving module, the kernel state filtering driving module identifies the event types of the NDIS OID events and the working modes of the corresponding communication modules, if the working mode of the communication module related to the NDIS OID events is the device management mode, the NDIS OID events are shielded and are not reported to the WWvc application module, and if the working mode of the communication module related to the NDIS OID events is the non-device management mode, the NDIS OID events are reported to the WWANSVc application module.
When the event type is an event issued by the application module to the communication module, that is, the event type is a second-class event, specifically, if the operating system event is an end-user-class operating event, a processing flow of the filtering driver module to the operating system event is as shown in fig. 7. The WWANSVc application module generates an NDIS OID event and sends the NDIS OID event to the kernel-mode filtering driver module, the kernel-mode filtering driver module blocks the current NDIS OID event and issues a working mode switching instruction to indicate a device mode management unit in the communication module to switch the working mode of the communication module from a device management mode to a non-device management mode, and the filtering driver module indicates to execute the NDIS OID event and uploads an execution result corresponding to the NDIS OID event to the WWANSVc application module when receiving the switching success instruction. It can be understood that the private OID and the private MBIM CID are different representation forms corresponding to the same event, the MBIM CID is correspondingly used in the configuration module, and the private OID is correspondingly used in the filter driver module, and the two may be converted to each other through the MBBCX driver module.
If the os event is a system request query type event, the processing flow of the filter driver for the os event is shown in fig. 8. The WWANSVc application module generates an NDIS OID event and sends the NDIS OID event to the kernel-mode filtering driver module, and if the kernel-mode filtering driver module identifies that the NDIS OID event is a system request query type event and the working mode of the current communication module is an equipment management mode, the latest saved execution result corresponding to the NDIS OID event is directly obtained and reported to the WWANSVc application module; when the kernel mode filter driver module identifies that the NDIS OID event is a system request query type event and the working mode of the current communication module is a non-equipment management mode, an NDIS OID event execution instruction is issued, an NDIS OID event execution result returned by the communication module is returned to the WWANSVc application module, and meanwhile, the NDIS OID event execution result is stored for use in next query.
In the operating system event processing method in the embodiment, the kernel-state filtering driver module is used for processing the operating system event, and the corresponding event can be processed by using the open interface and the open driver model of the operating system, so that the open dependence on the module code can be effectively avoided; compared with the corresponding event processing in the configuration module, the interface dependence between different units in the configuration module can be avoided; in addition, the main framework of the scheme is arranged on the MBB CX drive, does not depend on the MBIM system framework of the configuration module, and can better realize the compatibility between different system frameworks; according to the scheme, the terminal user can accurately realize the non-perception of the equipment management service.
It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides an operating system for implementing the above-mentioned operating system event processing method. The implementation scheme for solving the problem provided by the operating system is similar to the implementation scheme described in the above method, so specific limitations in one or more operating system embodiments provided below may refer to the above limitations on the operating system event processing method, and details are not described here.
In one embodiment, an operating system is provided, and comprises a configuration module and a filter driver module running in a kernel state, wherein the configuration module is connected with the filter driver module in a communication manner; wherein the content of the first and second substances,
the configuration module is used for managing operating system events and configuring the working mode of the module;
the filtering driving module is used for acquiring a target event identifier corresponding to a target operating system event; identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; according to the processing strategy of the target operating system event, correspondingly processing the target operating system event; wherein the target operating system event is any operating system event.
Alternatively, the configuration module may be configured to manage operating system events related to the configuration module, for example, the configuration module generates corresponding operating system events, classifies, identifies and transmits the operating system events, such as characterizing the operating system events generated by the configuration module using the MBIM CID, and sends the operating system events meeting the preset condition to the filter driver module. The configuration module comprises a plurality of working modes, such as a device management mode and a non-device management mode, and can manage the working modes of the configuration module, and when a mode switching instruction of the filter driving module is received or a preset condition of the corresponding mode is met, the working modes of the configuration module are managed.
In the operating system, the managed operating system event is sent to a filter driving module through a configuration module, the filter driving module receives a target event identifier corresponding to a target operating system event sent by the configuration module, and the event type of the target operating system event and the working mode of the configuration module related to the target operating system event are identified according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event. The kernel-state filtering driver module of the operating system is used for processing the operating system events, the kernel-state filtering driver module can process the operating system events by utilizing an open interface and a drive model of the operating system, and open dependence on configuration module codes can be effectively avoided; in addition, according to the event type of the operating system event and the working mode of the configuration module related to the operating system event, the processing strategy of the operating system event can be accurately determined, and effective management of the operating system event is realized.
In one embodiment, the operating system further comprises an application module running in the user mode, which may be referred to in fig. 1, the application module is communicatively connected to the filter driver module,
the filtering driving module is also used for uploading the target operating system event to the application module when the working mode of the configuration module related to the target operating system event is a non-equipment management mode; the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identification card; when the working mode of the configuration module related to the target operating system event is an equipment management mode, determining the processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the module is the operation related to the embedded SIM card;
and the application module is used for executing the target operating system event uploaded by the filter driving module.
In one embodiment, the event types include a type of event and a type of event;
the filtering driving module is also used for shielding the target operating system event when the event type is one type of event; one type of event is an event reported to the application module by the configuration module; when the event type is a second-class event, issuing a working mode switching instruction to enable the working mode of the configuration module to be switched from the equipment management mode to the non-equipment management mode, issuing an execution request for a target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; the second kind of events are the events sent by the application module to the configuration module.
In one embodiment, as shown in fig. 9, the operating system further includes a class extension module running in a kernel mode, and the class extension module is communicatively connected to the configuration module and the filter driver module respectively;
the class extension module is used for converting the format of the operating system event managed by the configuration module from a first format to a second format;
the filtering driving module is further used for acquiring a target event identifier corresponding to the target operating system event in the second format from the class extension module, and identifying the event type of the target operating system event and the working mode of the configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
Optionally, the class extension module is communicatively connected to the configuration module and the filter driver module, respectively, and after receiving the operating system event sent by the configuration module, the class extension module converts the operating system event in the first format sent by the configuration module into the operating system event in the second format, for example, converts the operating system event in the MBIM CID format sent by the configuration module into the operating system event in the NDIS OID format.
Based on the same inventive concept, the embodiment of the present application further provides an operating system event processing apparatus for implementing the above-mentioned operating system event processing method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the method, so specific limitations in one or more embodiments of the operating system event processing device provided below can be referred to the limitations of the operating system event processing method in the foregoing, and details are not described here.
In one embodiment, as shown in fig. 10, an operating system event processing apparatus is provided, where an operating system includes a configuration module and a filter driver module running in a kernel state, the filter driver module is communicatively connected to the configuration module, and the apparatus is applied to the filter driver module, and the apparatus includes: an identifier acquisition module 1002, an identifier identification module 1004, an event policy module 1006, and an event processing module 1008, wherein:
an identifier obtaining module 1002, configured to obtain a target event identifier corresponding to a target operating system event;
an identifier identifying module 1004, configured to identify, according to the target event identifier, an event type of the target operating system event and a working mode of a configuration module related to the target operating system event;
an event policy module 1006, configured to determine a processing policy of the target operating system event according to an event type of the target operating system event and a working mode of a configuration module related to the target operating system event;
the event processing module 1008 performs corresponding processing on the target operating system event according to the processing policy of the target operating system event.
In one embodiment, the operating system further comprises an application module running in a user mode, and the application module is in communication connection with the filter driver module; the event policy module 1006 is further configured to:
when the working mode of the configuration module related to the target operating system event is a non-equipment management mode, uploading the target operating system event to an application module; the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identity identification card;
and when the working mode of the configuration module related to the target operating system event is an equipment management mode, determining the processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the module is the operation related to the embedded SIM card.
In one embodiment, the event types include a type of event and a type of event, and the event policy module 1006 is further configured to:
when the event type is a type of event, shielding the target operating system event; the event of the same type is an event reported to the application module by the configuration module;
when the event type is a second-class event, issuing a working mode switching instruction to enable the working mode of the configuration module to be switched from the equipment management mode to a non-equipment management mode, then issuing an execution request for the target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; the second type of event is an event issued by the application module to the configuration module.
In one embodiment, the operating system event processing apparatus further comprises a system query module for:
and when the second-class event is a system query event, obtaining the latest saved query result of the second-class event, and returning the latest query result to the application module.
In one embodiment, the identifier obtaining module 1002 is further configured to: when a first event identifier corresponding to a plurality of operating system events is acquired at the same time, determining a target operating system event from the operating system events according to the priority of the first event identifier, and acquiring a target event identifier corresponding to the target operating system event.
The various modules in the operating system event processing apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent of a processor in the electronic device, or can be stored in a memory in the electronic device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, an electronic device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 11. The electronic device comprises a processor, a memory, a communication interface, a display screen and an input device which are connected through a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The communication interface of the electronic device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement an operating system event handling method. The display screen of the electronic equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the electronic equipment, an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 11 is a block diagram of only a portion of the structure associated with the present application, and does not constitute a limitation on the electronic devices to which the present application may be applied, and a particular electronic device may include more or fewer components than those shown in the drawings, or may combine certain components, or have a different arrangement of components.
Those skilled in the art will understand that the electronic device can be a wireless communication module, or a smart device (such as a smart car, a smart cabinet, a smart meter, etc.) including the wireless communication module, or a communication device such as a mobile phone, a computer, a tablet, etc.
In one embodiment, an electronic device is provided, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the operating system event processing method in the foregoing embodiments when executing the computer program.
In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the steps of the operating system event processing method in the above embodiments.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the operating system event processing method of the above embodiments.
It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), magnetic Random Access Memory (MRAM), ferroelectric Random Access Memory (FRAM), phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims (10)

1. An operating system event processing method, wherein an operating system includes a configuration module and a filter driver module running in a kernel state, the filter driver module is communicatively connected to the configuration module, and the method is applied to the filter driver module, and the method includes:
acquiring a target event identifier corresponding to a target operating system event;
identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier;
determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event;
and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
2. The method of claim 1, wherein the operating system further comprises an application module running in a user state, the application module communicatively coupled to the filter driver module; the determining the processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of the configuration module related to the target operating system event comprises the following steps:
when the working mode of the configuration module related to the target operating system event is a non-equipment management mode, uploading the target operating system event to the application module; the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identity identification card;
and when the working mode of the configuration module related to the target operating system event is an equipment management mode, determining the processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the module is the operation related to the embedded SIM card.
3. The method of claim 2, wherein the event types include a class one event and a class two event; when the working mode of the configuration module related to the target operating system event is the device management mode, determining the processing strategy of the operating system event according to the event type of the target operating system event, including:
when the event type is a type of event, shielding the target operating system event; the event of the same type is an event reported to the application module by the configuration module;
when the event type is a second-class event, issuing a working mode switching instruction to enable the working mode of the configuration module to be switched from the equipment management mode to a non-equipment management mode, then issuing an execution request for the target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; the second type of event is an event issued by the application module to the configuration module.
4. The method of claim 1, wherein obtaining a target event identifier corresponding to a target operating system event comprises:
when first event identifiers corresponding to a plurality of operating system events are acquired at the same time, determining a target operating system event from the operating system events according to the priority of the first event identifiers, and acquiring a target event identifier corresponding to the target operating system event.
5. An operating system, wherein the operating system comprises a configuration module and a filter driver module running in a kernel state, and the configuration module is connected with the filter driver module in a communication manner; wherein, the first and the second end of the pipe are connected with each other,
the configuration module is used for managing operating system events and the working mode of the configuration module;
the filtering driving module is used for acquiring a target event identifier corresponding to a target operating system event; identifying the event type of the target operating system event and the working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; according to the processing strategy of the target operating system event, correspondingly processing the target operating system event; the target operating system event is any one of the operating system events.
6. The operating system of claim 5, further comprising an application module running in a user state, the application module communicatively coupled to the filter driver module;
the filtering driving module is further configured to upload the target operating system event to the application module when a working mode of a configuration module related to the target operating system event is a non-device management mode; the non-equipment management mode refers to that the operation executed by the configuration module is the operation related to the user identity identification card; when the working mode of the configuration module related to the target operating system event is an equipment management mode, determining a processing strategy of the target operating system event according to the event type of the target operating system event, wherein the equipment management mode refers to that the operation executed by the module is the operation related to the embedded SIM card;
and the application module is used for executing the target operating system event uploaded by the filter driving module.
7. The operating system of claim 6, wherein the event types include a class one event and a class two event;
the filtering driving module is further configured to shield the target operating system event when the event type is a type of event; the event of the same type is an event reported to the application module by the configuration module; when the event type is a second-class event, issuing a working mode switching instruction to enable the working mode of the configuration module to be switched from the equipment management mode to a non-equipment management mode, then issuing an execution request for the target operating system event to the configuration module, receiving and uploading an execution result corresponding to the target operating system event execution request to the application module; the second type of event is an event issued by the application module to the configuration module.
8. The operating system according to claim 5, wherein the operating system further comprises a class extension module running in a kernel state, and the class extension module is communicatively connected to the configuration module and the filter driver module respectively;
the class extension module is used for converting the format of the operating system event managed by the configuration module from a first format to a second format;
the filtering driving module is further configured to obtain a target event identifier corresponding to a target operating system event in a second format from the class extension module, and identify an event type of the target operating system event and a working mode of a configuration module related to the target operating system event according to the target event identifier; determining a processing strategy of the target operating system event according to the event type of the target operating system event and the working mode of a configuration module related to the target operating system event; and correspondingly processing the target operating system event according to the processing strategy of the target operating system event.
9. An electronic device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method of any of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4.
CN202211178771.0A 2022-09-27 2022-09-27 Operating system event processing method, operating system, electronic device and storage medium Pending CN115509619A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202211178771.0A CN115509619A (en) 2022-09-27 2022-09-27 Operating system event processing method, operating system, electronic device and storage medium
PCT/CN2023/111687 WO2024066748A1 (en) 2022-09-27 2023-08-08 Operating system event processing method, operating system, electronic device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211178771.0A CN115509619A (en) 2022-09-27 2022-09-27 Operating system event processing method, operating system, electronic device and storage medium

Publications (1)

Publication Number Publication Date
CN115509619A true CN115509619A (en) 2022-12-23

Family

ID=84505799

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211178771.0A Pending CN115509619A (en) 2022-09-27 2022-09-27 Operating system event processing method, operating system, electronic device and storage medium

Country Status (2)

Country Link
CN (1) CN115509619A (en)
WO (1) WO2024066748A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066748A1 (en) * 2022-09-27 2024-04-04 深圳市广和通无线股份有限公司 Operating system event processing method, operating system, electronic device and storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108037999A (en) * 2017-12-06 2018-05-15 广东欧珀移动通信有限公司 Resource allocation method and Related product
CN108965413B (en) * 2018-07-03 2021-08-03 北京小米移动软件有限公司 Information interaction method and device and storage medium
CN109784041B (en) * 2018-12-29 2020-10-16 360企业安全技术(珠海)有限公司 Event processing method and device, storage medium and electronic device
CN110881051B (en) * 2019-12-24 2022-04-29 深信服科技股份有限公司 Security risk event processing method, device, equipment and storage medium
CN115509619A (en) * 2022-09-27 2022-12-23 深圳市广和通无线股份有限公司 Operating system event processing method, operating system, electronic device and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066748A1 (en) * 2022-09-27 2024-04-04 深圳市广和通无线股份有限公司 Operating system event processing method, operating system, electronic device and storage medium

Also Published As

Publication number Publication date
WO2024066748A1 (en) 2024-04-04

Similar Documents

Publication Publication Date Title
US20200112851A1 (en) Apparatuses, methods and systems for implementing a system-on-chip with integrated reprogrammable cellular network connectivity
CN111600952B (en) Scene pushing method, scene pushing execution device, terminal, server and scene pushing system
US20140355519A1 (en) Sharing wireless traffic
US20160210632A1 (en) Secured payment method and relevant device and system
CN108345462B (en) Method and device for upgrading components
CN111800462A (en) Micro-service instance processing method and device, computer equipment and storage medium
CN106407757A (en) Access right processing method, apparatus and system for database
WO2021223672A1 (en) Near field communication (nfc) method and apparatus, and electronic device
US20190246266A1 (en) Apparatuses, methods and systems for implementing a system-on-chip with integrated reprogrammable cellular network connectivity
US20150242076A1 (en) Method of editing one or more objects and apparatus for same
CN110213092A (en) Resource access method, platform management equipment, storage medium and the device of mixed cloud
CN112631780A (en) Resource scheduling method and device, storage medium and electronic equipment
CN112215025A (en) Radio frequency card function calling method and device
WO2024066748A1 (en) Operating system event processing method, operating system, electronic device and storage medium
KR102045662B1 (en) System and method for managing logical channels for accessing several virtual profiles within a secure element
CN110928681A (en) Data processing method and device, storage medium and electronic device
CN108520401B (en) User list management method, device, platform and storage medium
CN109343944A (en) Data processing method, device, terminal and the storage medium of eSIM card
CN104349506A (en) Association management method, wireless access device and system
CN106528199A (en) Method and terminal for updating automobile instrument panel system
CN112787828B (en) Application flow statistical method and device and mobile electronic device
CN115098020A (en) Storage management method, device and storage medium
US9642010B2 (en) Management server, data processing method, and program
CN112769688B (en) Method and device for protocol stack adaptation, electronic equipment and storage medium
CN110351703A (en) One kind opening chucking method, device, relevant device and storage medium

Legal Events

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