Systems and methods for supporting ad hoc group call for MCX services
US-12167494-B2 · Dec 10, 2024 · US
US11903041B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11903041-B2 |
| Application number | US-202117323714-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 18, 2021 |
| Priority date | Nov 19, 2018 |
| Publication date | Feb 13, 2024 |
| Grant date | Feb 13, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for processing an abnormality is provided. The method includes: loading and executing a driver of the Wi-Fi module in response to receiving an instruction for enabling a Wi-Fi function of the terminal device, initiating at least one request sub-process to a hardware layer of a Wi-Fi system of the terminal device through a framework layer of the Wi-Fi system, clearing the driver of the Wi-Fi module from a memory of the terminal device in response to failure of any request sub-process and re-loading and executing the driver of the Wi-Fi module after completely clearing the driver of the Wi-Fi module from the memory.
Opening claim text (preview).
What is claimed is: 1. A method for processing an abnormality, applicable in a terminal device comprising a Wi-Fi module, the method comprising: loading and executing a driver of the Wi-Fi module in response to receiving an instruction for enabling a Wi-Fi function of the terminal device, initiating at least one request sub-process to a hardware layer of a Wi-Fi system of the terminal device through a framework layer of the Wi-Fi system; clearing the driver of the Wi-Fi module from a memory of the terminal device in response to failure of any request sub-process; and re-loading and executing the driver of the Wi-Fi module after completely clearing the driver of the Wi-Fi module from the memory. 2. The method of claim 1 , wherein, the request sub-process comprises: a scanning request sub-process and a connecting request sub-process. 3. The method of claim 2 , wherein initiating the at least one request sub-process to the hardware layer of the Wi-Fi system of the terminal device through the framework layer of the Wi-Fi system comprises: initiating the scanning request sub-process to the hardware layer of the Wi-Fi system through the framework layer of the Wi-Fi system; and initiating the connecting request sub-process to the hardware layer of the Wi-Fi system through the framework layer of the Wi-Fi system in response to success of the scanning request sub-process. 4. The method of claim 2 , wherein clearing the driver of the Wi-Fi module from the memory of the terminal device in response to failure of any request sub-process comprises: determining that the scanning request sub-process fails and clearing the driver of the Wi-Fi module from the memory in response to not receiving any scanning response from the hardware layer within a first preset duration after the framework layer initiates a scanning request to the hardware layer. 5. The method of claim 4 , wherein clearing the driver of the Wi-Fi module from the memory of the terminal device in response to failure of any request sub-process comprises: determining that the scanning request sub-process fails and clearing the driver of the Wi-Fi module from the memory in response to receiving a scanning response from the hardware layer within the first preset duration after the framework layer initiates the scanning request to the hardware layer and no scanning result is received from the hardware layer within a second preset duration after the framework layer initiates the scanning request to the hardware layer. 6. The method of claim 4 , wherein clearing the driver of the Wi-Fi module from the memory of the terminal device in response to failure of any request sub-process comprises: determining that the scanning request sub-process fails and clearing the driver of the Wi-Fi module from the memory in response to receiving a scanning response from the hardware layer within the first preset duration after the framework layer initiates the scanning request to the hardware layer and no scanning result is received from the hardware layer within a third preset duration after the scanning response is received. 7. The method of claim 5 , further comprising: continuously initiating the scanning request sub-process to the hardware layer of the Wi-Fi system of the terminal device through the framework layer of the Wi-Fi system, until a preset number of continuous scanning request sub-processes all fail. 8. The method of claim 2 , wherein clearing the driver of the Wi-Fi module from the memory of the terminal device in response to failure of any request sub-process comprises: determining whether a present connecting request is the first connecting request after the framework layer initiates the present connecting request to the hardware layer; recording a current time as the time of initiating the present connecting request and monitoring a state of the hardware layer when the present connecting request is the first connecting request; and determining that the connecting request sub-process fails and clearing the driver of the Wi-Fi module from the memory in response to monitoring that the state of the hardware layer is a preset state. 9. The method of claim 8 , wherein determining whether the present connecting request is the first connecting request comprises: determining whether a time interval between the current time and a time of initiating a previous connecting request is less than a preset time interval when the present connecting request is not the first connecting request; recording the current time as the time of initiating the present connecting request and monitoring the state of the hardware layer when the time interval between the current time and the time of initiating the previous connecting request is less than the preset time interval; determining that the connecting request sub-process fails and clearing the driver of the Wi-Fi module from the memory in response to monitoring that the state of the hardware layer is the preset state. 10. The method of claim 9 , wherein determining whether the time interval between the current time and the time of initiating a previous connecting request is less than a preset time interval when the present connecting request is not the first connecting request comprises: disabling the Wi-Fi function when the time interval between the current time and the time of initiating the previous connecting request is greater than or equal to the preset time interval. 11. The method of claim 8 , wherein monitoring the state of the hardware layer comprises: waiting for a switching result when the state of the hardware layer is in switching; and determining the switching result as the state of the hardware layer in response to completing the switching of the state of the hardware layer. 12. The method of claim 1 , further comprising: setting a daemon process for the driver of the Wi-Fi module; and starting up the daemon process in response to monitoring that the driver of the Wi-Fi module is executed. 13. The method of claim 12 , wherein re-loading and executing the driver of the Wi-Fi module after completely clearing the driver of the Wi-Fi module from the memory comprises: triggering by the daemon process re-loading and executing the driver of the Wi-Fi module in response to monitoring that the driver of the Wi-Fi module is cleared completely from the memory. 14. The method of claim 1 , further comprising: opening a virtual running environment and executing the driver of the Wi-Fi module loaded currently in the virtual running environment; and clearing the driver of the Wi-Fi module from the memory in response to failure of the driver to execute in the virtual running environment. 15. The method of claim 14 , further comprising: re-executing the driver of the Wi-Fi module in response to the driver succeeding in executing in the virtual running environment; and initiating at least one request sub-process to the hardware layer of the Wi-Fi system through the framework layer of the Wi-Fi system of the terminal device. 16. The method of claim 14 , further comprising setting the virtual running environment comprising: setting a virtual Wi-Fi module in the virtual running environment based on a hardware parameter of the Wi-Fi module; and setting a response message for the virtual Wi-Fi module based on data interaction between the framework layer and the hardware layer. 17. The method of claim 1 , further comprising: disabling the Wi-Fi function in response to failure of the Wi-Fi module to connect to a wireless access point within a fourth preset duration after
Connection setup · CPC title
Discovering, processing access restriction or access information · CPC title
Selecting a network or a communication service · CPC title
between terminal device and access point, i.e. wireless air interface · CPC title
by checking the correct order of processing (G06F11/08 - G06F11/26 take precedence; monitoring patterns of pulse trains H03K5/19) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.