A networking method, readable medium, electronic device and program product

Abstract

This application relates to the field of communications and discloses a networking method, a readable medium, an electronic device, and a program product. In this method, the probability of a master device establishing a pre-connection and interacting with an extension device based on a certain connection type is obtained, and it is determined whether the usage probability is greater than or equal to a usage probability threshold. If the usage probability is greater than or equal to the threshold, the master device is controlled to establish a pre-connection with the corresponding extension device through the corresponding connection type; if the usage probability is less than the threshold, the master device is controlled not to establish a pre-connection with the corresponding extension device through the corresponding connection type. Thus, when the usage probability of a connection type does not meet the above conditions, the master device will not establish a pre-connection based on that connection type; if the connection type is a high-power connection type, the master device can avoid the pre-connection power consumption caused by maintaining a pre-connection state with the extension device without interacting with the extension device through that connection type.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular to a networking method, a readable medium, an electronic device, and a program product. Background Technology

[0002] With the development of Internet of Things (IoT) technology, users can interconnect with other extended devices through a master device and use the devices of the extended devices (such as displays) as virtual devices of the master device to enable the master device and extended devices to share device functions (such as display functions).

[0003] In some solutions, the master device can pre-establish connections with multiple expansion devices, so that when the master device determines to use the device function of a certain expansion device, it can directly use the device function of the corresponding expansion device without waiting to establish a connection, thus saving the time of waiting for the master device to establish a connection with the expansion device.

[0004] However, some connection types consume more power during connection, such as Wireless Local Area Network (WLAN) Direct, which is a communication technology that allows electronic devices to communicate directly through a WLAN network (such as Wireless Fidelity, Wi-Fi).

[0005] However, if the main device has pre-established connections with both extension devices a and b, and the connection type between the main device and extension device b is WLAN direct connection, and the main device does not use the device function of extension device b but uses the device function of extension device a, then the power consumption of the main device will be high due to the high power consumption of the WLAN direct connection established between the main device and extension device b. Summary of the Invention

[0006] To address the aforementioned issues, embodiments of this application provide a networking method, a readable medium, an electronic device, and a program product.

[0007] In a first aspect, this application provides a networking method applied to an electronic device. The method includes: determining a first usage probability based on historical data that the electronic device establishes a pre-connection and interacts with an extended device through a first connection type, wherein the historical data includes the interaction duration and number of interactions between the electronic device and the extended device through the first connection type within a historical time period; determining whether the first usage probability is greater than or equal to a first usage probability threshold; corresponding to the first usage probability being greater than or equal to the first usage probability threshold, controlling the electronic device and the extended device to establish a pre-connection through the first connection type; and corresponding to the first usage probability being less than the first usage probability threshold, controlling the electronic device and the extended device not to establish a pre-connection based on the first connection type.

[0008] In this application embodiment, "electronic device" can refer to the main device mentioned in this application embodiment, and "extended device" can refer to extended device a or extended device b mentioned in this application embodiment, etc., without specific limitations. Furthermore, "historical time period" can refer to the historical number of days N mentioned in this application embodiment, where N can be any positive integer, for example, without specific limitations.

[0009] In the embodiments of this application, the first usage probability may refer to the "intentProb" mentioned in the embodiments of this application, and the first usage probabilities corresponding to different connection types may be different or the same, without specific limitations.

[0010] In other embodiments of this application, if the first usage probability falls within a first usage probability range, the electronic device and the extended device can be controlled to establish a pre-connection through a first connection type. The first usage probability range may refer to "linkProb" mentioned in the embodiments of this application. Furthermore, the usage probability ranges corresponding to different configuration levels may differ, and no specific limitations are imposed here.

[0011] Using the above method, when determining whether the master device should establish a pre-connection with the expansion device based on a certain connection type, it needs to ensure that the usage probability of that connection type is greater than or equal to a usage probability threshold. Only then will the master device establish a pre-connection with the expansion device through the corresponding connection type. Thus, when the usage probability of a connection type does not meet the condition, the master device will not establish a pre-connection based on that connection type. If the connection type is a high-power connection type, the master device can avoid maintaining a pre-connection state with the expansion device without interacting with it, thus avoiding the pre-connection power consumption.

[0012] In one possible implementation of the first aspect above, corresponding to a first usage probability greater than or equal to a first usage probability threshold, controlling the electronic device and the extended device to establish a pre-connection through a first connection type further includes: determining whether the electronic device is in a screen-on state; corresponding to the electronic device being in a screen-on state, controlling the electronic device and the extended device to establish a pre-connection through the first connection type.

[0013] In this embodiment, when the electronic device is in a screen-on state, if the first usage probability is determined to be greater than or equal to the first usage probability threshold, the electronic device and the extended device can be controlled to establish a pre-connection through the first connection type, thereby avoiding the high power consumption caused by establishing a pre-connection when the electronic device is in a black-screen scenario.

[0014] It is understood that in some other embodiments, if the main device is detected to be in a black screen state, it may indicate that the main device is currently in an unused state, which is not limited here. Furthermore, the main device may not establish a pre-connection in the black screen display state, thus avoiding the connection power consumption caused by the main device establishing a pre-connection in the black screen display state.

[0015] In one possible implementation of the first aspect above, corresponding to a first usage probability greater than or equal to a first usage probability threshold, controlling the electronic device and the extended device to establish a pre-connection based on a first connection type further includes: obtaining a first application package name set based on first configuration information, and determining whether the electronic device starts a first application, wherein the first application is the application corresponding to a package name in the first application package name set, and the first configuration information is information used to guide the electronic device to establish a pre-connection; corresponding to the electronic device starting the first application and the first usage probability being greater than or equal to the first usage probability threshold, controlling the electronic device and the extended device to establish a pre-connection based on the first connection type.

[0016] In this embodiment, the first configuration information may refer to the information corresponding to different configuration levels in Table 1 mentioned in this embodiment. The first set of application package names may refer to the applist mentioned in this embodiment.

[0017] It is understandable that the application corresponding to the package name in the first set of application package names can refer to the application that the main device can establish a pre-connection with the extended device when using this type of application, and use the corresponding extended device's functions to improve device usage efficiency.

[0018] In this embodiment, when the electronic device enters a preset application, if the first usage probability is determined to be greater than or equal to a first usage probability threshold, the electronic device and the extended device can be controlled to establish a pre-connection through a first connection type. That is, when the electronic device launches the preset application, the electronic device is then controlled to establish a pre-connection based on the corresponding connection type. Thus, a pre-connection is only established when the main device enters the preset application. It can be understood that the preset application can refer to an application that can use the corresponding functions in the extended device. If the application launched by the main device is an application that does not require the use of the corresponding functions in the extended device, the main device will not be triggered to establish a pre-connection, i.e., no power consumption will occur due to the main device establishing a pre-connection.

[0019] In one possible implementation of the first aspect above, obtaining the first application package name set based on the first configuration information and determining whether the electronic device has started the first application further includes: corresponding to the electronic device not starting the first application, controlling the electronic device and the extended device not to establish a pre-connection based on the first connection type.

[0020] In this embodiment, if the electronic device does not enter a preset application, it can be directly controlled to prevent the electronic device from establishing a pre-connection with the extended device based on the first connection type. This avoids power consumption caused by the electronic device establishing a pre-connection and remaining in a pre-connection state even when using an application that does not require the corresponding functions of the extended device.

[0021] In one possible implementation of the first aspect above, corresponding to the electronic device launching the first application and the first usage probability being greater than or equal to the first usage probability threshold, controlling the electronic device and the extended device to establish a pre-connection based on the first connection type further includes: determining whether the electronic device exits the first application; corresponding to the electronic device exiting the first application, the electronic device disconnects the pre-connection established with the extended device based on the first connection type.

[0022] It's understandable that in some scenarios, if an electronic device exits an application that pre-requires the corresponding functions of the extended device, it indicates that the electronic device does not need to establish a pre-connection with the extended device. Based on this, the electronic device can disconnect from the extended device. This allows the electronic device to avoid establishing a pre-connection when using applications that do not require the extended device's functions, thus preventing power consumption caused by prolonged pre-connection.

[0023] In one possible implementation of the first aspect above, when the first usage probability is less than a first usage probability threshold, controlling the electronic device and the extended device not to establish a pre-connection based on the first connection type further includes: obtaining a first duration for which the electronic device and the extended device establish a pre-connection based on the first connection type, and determining whether the first duration is greater than a first pre-connection duration threshold; when the first duration is greater than the first pre-connection duration threshold, the electronic device disconnects the pre-connection established by the extended device based on the first connection type.

[0024] In this embodiment, the first pre-connection duration threshold can refer to "keepDur" or "totalDur" mentioned in this embodiment. By setting a connection duration threshold to disconnect the pre-connection, the power consumption of the main device in the pre-connection state for a long time can be effectively reduced.

[0025] In one possible implementation of the first aspect above, the determination of the first usage probability threshold includes: receiving a first networking strategy, wherein the first networking strategy includes a first pre-connection probability, the first pre-connection probability representing the probability that an electronic device establishes a pre-connection through a first connection type within a first time period; obtaining first configuration information, wherein the first configuration information includes first matching information, the first matching information being used to match information corresponding to the first networking strategy, and the first matching information including a first pre-connection probability threshold; the first configuration information includes first control information, the first control information including a first usage probability threshold, corresponding to the first pre-connection probability being greater than or equal to the first pre-connection probability threshold, and determining the first usage probability threshold based on the first control information.

[0026] In this embodiment, the first networking strategy may refer to the information in Table 2 mentioned in this embodiment, and is not specifically limited here. The first pre-connection probability may refer to "timeProb" in the networking strategy mentioned in this embodiment, the first matching information may refer to "scope" mentioned in this embodiment, and the first control information may refer to "ploy" mentioned in this embodiment.

[0027] In other embodiments of this application, the first matching information includes a first pre-connection probability range, which may refer to "timeProb" in the matching information "scope" mentioned in the embodiments of this application. If the first pre-connection probability belongs to the first pre-connection probability range, then the first usage probability range "linkProb" can be determined based on the first control information.

[0028] In one possible implementation of the first aspect above, the method for determining the first usage probability threshold further includes: obtaining the percentage of first network days, the first average number of network sessions, and the maximum percentage of first network days for a first historical period included in the first network strategy, wherein the first historical period includes historical days; the first matching information further includes the first network days percentage threshold, the first average number of network sessions threshold, and the maximum percentage of first network days threshold; and determining the first usage probability threshold based on the first configuration information for any one or more of the following: the percentage of first network days is greater than or equal to the first network days percentage threshold, the first average number of network sessions is greater than or equal to the first average number of network sessions threshold, and the maximum percentage of first network days is less than or equal to the maximum percentage of first network days threshold.

[0029] In this embodiment, the first network day percentage can refer to "validDaysPercent" mentioned in this embodiment. The first average number of network setups can refer to "validUseCnt" mentioned in this embodiment. The maximum percentage of network days in the first time period can refer to "maxSlotDaysPercent" mentioned in this embodiment.

[0030] In this embodiment of the application, the first matching information also includes the first network day ratio range "dayProb", the first average network number threshold can refer to "avgTimes" mentioned in this embodiment of the application, and the first time period network day ratio maximum threshold can refer to "maxProb" mentioned in this embodiment of the application.

[0031] In other embodiments of this application, a first usage probability range “linkProb” is determined based on the first configuration information, corresponding to any one or more of the following: the proportion of the first network days falls within the range of the first network days, the first average number of network sessions is greater than or equal to the threshold of the first average number of network sessions, and the maximum value of the proportion of the first time period network days is less than or equal to the threshold of the maximum value of the first time period network days.

[0032] Secondly, embodiments of this application provide an electronic device, including a memory for storing instructions and a processor for executing the instructions to implement the networking method provided by the first aspect and various possible implementations of the first aspect.

[0033] Thirdly, embodiments of this application provide a readable storage medium storing instructions that, when executed on an electronic device, cause the electronic device to perform the networking method provided in the first aspect and various possible implementations of the first aspect.

[0034] Fourthly, embodiments of this application also provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements the networking method provided by the first aspect and various possible implementations of the first aspect.

[0035] The beneficial effects of the second to fourth aspects mentioned above can be referred to the relevant descriptions in the first aspect and various possible implementations of the first aspect, which will not be repeated here. Attached Figure Description

[0036] Figure 1 A schematic diagram illustrating an application scenario of a networking method is shown based on the method provided in the embodiments of this application.

[0037] Figure 2 A flowchart illustrating a networking method is shown based on the method provided in the embodiments of this application.

[0038] Figure 3 According to the method provided in the embodiments of this application, a specific flowchart of a networking method is shown;

[0039] Figure 4 A schematic diagram of the software structure of an electronic device is shown according to the method provided in the embodiments of this application;

[0040] Figure 5 According to the method provided in the embodiments of this application, a schematic diagram of an interactive process is shown in which a master device determines how to pre-connect based on configuration information and networking strategy.

[0041] Figure 6 According to the method provided in the embodiments of this application, a flowchart of a master device acquiring and updating configuration information is shown;

[0042] Figure 7 A schematic diagram of the structure of an electronic device 100 is shown according to the method provided in the embodiments of this application. Detailed Implementation

[0043] The illustrative embodiments of this application include, but are not limited to, a networking method, a readable medium, an electronic device, and a program product.

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be described clearly and in detail below with reference to the accompanying drawings.

[0045] Multi-device networking refers to connecting multiple electronic devices together wirelessly or through other means to form a network system. In multi-device networking, devices can share resources, transmit data, and collaborate. Multiple electronic devices can network wirelessly; for example, multi-device networking can use wireless technologies such as Bluetooth (BT), Wi-Fi, or ZigBee to connect multiple electronic devices.

[0046] Figure 1 An embodiment of this application illustrates a schematic diagram of an application scenario for a networking method.

[0047] like Figure 1 As shown, mobile phone 10 can form a device group with electronic devices such as tablet computer 11, smart screen 12, TV 13, smart counting rope 14, smart electronic scale 15, smart blood pressure monitor 16, fax machine 17, printer 18, air conditioner 19, and refrigerator 20. The electronic devices within this device group can communicate with each other. For example, all electronic devices can be on the same local area network (LAN) and logged into the same account, in which case they can communicate with each other.

[0048] It is understandable that, in addition to local area networks, the aforementioned electronic devices can also establish communication through wireless communication technologies such as Bluetooth, Wi-Fi, Wi-Fi Direct, or ZigBee, and no restrictions are imposed here.

[0049] It is understood that the electronic devices in the embodiments of this application may include: mobile phones, smart screens, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0050] It is understood that the technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) mobile communication systems or new radio access technology (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS), etc. Furthermore, the technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems.

[0051] In some embodiments, provided that both the main device and the extended device have logged into user accounts and have successfully subscribed to the smart networking recommendation function in accordance with the privacy agreement of the smart interconnection function, the main device can receive a networking policy that indicates which extended device the main device can establish a pre-connection with and what connection type.

[0052] It is understood that the networking strategy can be determined based on the system time and location of the master device, as well as the historical interaction data between the master device and the extended devices. This historical interaction data may include the historical interaction time, historical interaction location, and historical connection type between the master device and the extended devices. The networking strategy may include information such as the device identifier and corresponding connection type of one or more extended devices. Furthermore, in some embodiments, the same extended device may include different connection types in the above networking strategy.

[0053] For example, if the current system time of the master device is t1, the location of the master device is A1, the historical interaction time intervals between the master device and extended devices a and b all include t1, and the historical interaction locations between the master device and extended devices a and b all include A1, then it can be determined that the current master device meets the pre-connection conditions. Furthermore, it is determined that the historical connection type between the master device and extended device a is Bluetooth, and the historical connection type between the master device and extended device b is WLAN direct connection. Based on this, a networking strategy can be determined, which includes the master device establishing a pre-connection with extended device a via Bluetooth, and the master device establishing a pre-connection with extended device b via WLAN direct connection.

[0054] As mentioned earlier, after the main device establishes pre-connections with extension devices a and b according to the networking strategy, if the main device chooses to use the device functions of extension device a instead of the device functions of control device b, the main device can directly use the device functions of control device a based on the pre-connection state with control device a. However, at the same time, the main device is also in a pre-connection state with extension device b, and the connection type is a high-power WLAN direct connection. Therefore, maintaining the pre-connection state between the main device and extension device b for a long time will result in high power consumption for the main device.

[0055] Therefore, to address the aforementioned issues, this application provides a networking method. This method obtains the probability of a master device establishing a pre-connection and interacting with an extension device based on a certain connection type, and determines whether the probability of use is greater than or equal to a probability threshold. If the probability of use is greater than or equal to the probability threshold, the master device is controlled to establish a pre-connection with the corresponding extension device using the corresponding connection type; if the probability of use is less than the probability threshold, the master device is controlled not to establish a pre-connection with the corresponding extension device using the corresponding connection type. The aforementioned probability of use can be determined by the interaction duration or number of interactions between the master device and the extension device using a certain connection type within a historical time period. A longer interaction duration or more interactions within a historical time period indicates a higher probability of use.

[0056] For example, the master device can obtain the first usage probability of establishing a pre-connection and interacting with the first extended device through a first connection type via a network strategy. This first usage probability can be determined by the duration or number of interactions between the master device and the first extended device after establishing the pre-connection through the first connection type within a historical time period. The longer the interaction duration or the more interactions within the historical time period, the higher the aforementioned first usage probability. Furthermore, the master device can determine whether the first usage probability is greater than or equal to a first usage probability threshold. If the first usage probability is greater than or equal to the first usage probability threshold, the master device is controlled to establish a pre-connection with the first extended device through the first connection type; if the first usage probability is less than the first usage probability threshold, the master device is controlled not to establish a pre-connection with the first extended device through the first connection type.

[0057] For example, the master device can obtain a second usage probability—the probability of establishing a pre-connection and interacting with the second extended device based on a second connection type—through a network strategy. This second usage probability can be determined by the duration or number of interactions between the master device and the second extended device after establishing a pre-connection using the second connection type within a historical time period. Furthermore, the master device can determine whether the second usage probability is greater than or equal to a first usage probability threshold. If the second usage probability is greater than or equal to the first usage probability threshold, the master device is controlled to establish a pre-connection with the second extended device using the second connection type; if the second usage probability is less than the first usage probability threshold, the master device is controlled not to establish a pre-connection with the second extended device using the second connection type.

[0058] In some embodiments of this application, assuming the first connection type is Bluetooth, the first usage probability of the master device establishing a pre-connection and interacting with the first extended device via Bluetooth is x1, and the first usage probability threshold is x2, where x1 can be greater than or equal to x2, then the master device can be controlled to establish a pre-connection with the first extended device via Bluetooth.

[0059] In some embodiments of this application, assuming the second connection type is WLAN direct connection, the second probability of the main device establishing a pre-connection and interacting with the second extended device through WLAN direct connection is x3, and the second probability threshold is x4, where x3 can be less than x4, then the main device can be controlled not to establish a pre-connection with the first extended device through WLAN direct connection.

[0060] As an example, Figure 2 A schematic flowchart of a networking method is shown according to an embodiment of this application.

[0061] Understandable. Figure 2 The execution entity of the process shown can be the main device, or as described above. Figure 1 The scene shown includes electronic devices such as mobile phone 10. For simplicity, the following description... Figure 2 The execution entity will not be described again when the process is shown.

[0062] like Figure 2 As shown, the process may include:

[0063] S201: Determine the first usage probability based on historical data that the master device interacts with the first extended device through the first connection type.

[0064] In some embodiments of this application, the aforementioned historical data may include first historical data corresponding to the first extended device. This first historical data may include: the total duration of interaction between the main device and the first extended device via the first connection type within a historical time period, the total number of interactions between the main device and the first extended device via the first connection type within the historical time period, and a first usage probability of the main device interacting with the first extended device via the first connection type within the historical time period based on the aforementioned total duration and / or total number of interactions.

[0065] It is understandable that the first usage probability can reflect the frequency with which the main device and the first extended device establish a pre-connection and interact within a historical time period.

[0066] It is understandable that if the total duration of interaction between the main device and the first extended device through the first connection type within a historical time period is longer, or if the total number of interactions between the main device and the first extended device through the first connection type within a historical time period is greater, then the probability of the main device and the first extended device establishing a pre-connection and interacting through the first connection type is greater.

[0067] It is understandable that the usage probability of the main device and different extended devices establishing pre-connections and interacting based on different connection types can be directly obtained based on a decision tree model. Specifically, historical interaction data between the main device and different extended devices within a historical time period can be obtained, and this historical interaction data can be used as sample data to input into the decision tree model for training. This allows us to obtain the usage probability corresponding to the main device and different extended devices establishing pre-connections and interacting based on different connection types. The decision tree model can include, but is not limited to, models such as ID3, C4.5, CART, random forest, GBDT, XGboost, LightGBM, and LambdaMART; this application does not impose any restrictions on this.

[0068] It is understandable that the historical time period can refer to the number of historical days N. N can be any positive integer, or any positive integer greater than or equal to 7. For example, N can be 30, 60, 90, etc., without any specific restrictions.

[0069] It is understood that the first connection type or the second connection type can include wireless communication types such as Wi-Fi connection, Wi-Fi P2P connection, Bluetooth connection, near field communication (NFC) connection, infrared (IR) connection, ultrawideband (UWB) connection, and ZigBee connection, without specific restrictions.

[0070] It is understood that the aforementioned historical data may also include historical interaction data corresponding to other extended devices that have established a pre-connection and interaction with the main device, and no specific restrictions are imposed here.

[0071] Correspondingly, the aforementioned first historical data may also include: at least one historical interaction time between the main device and the first extended device, at least one historical interaction location where the main device and the first extended device interact, the historical connection type of the main device and the first extended device at each historical interaction time and / or each historical interaction location, the device identifier of the first extended device, the name of the interaction event or the type of the interaction event, etc., without specific limitations.

[0072] It is understandable that within a certain historical interaction period, the main device and different extended devices can use one historical connection type or multiple historical connection types. At the same historical interaction point, the main device and different extended devices, or the same extended device, can use one historical connection type or multiple historical connection types, etc., without specific restrictions.

[0073] S202: Determine whether the first usage probability is greater than or equal to the first usage probability threshold.

[0074] If the judgment result is yes, then proceed to S203, and control the main device and the first extended device to establish a pre-connection through the first connection type;

[0075] If the judgment result is negative, proceed to S204 and control the main device and the first extended device not to establish a pre-connection through the first connection type.

[0076] In some embodiments of this application, after determining the first usage probability that the master device pre-connects and interacts with the first extended device through the first connection type, it can be further determined whether the first usage probability is greater than or equal to the first usage probability threshold.

[0077] In some other embodiments of this application, after determining the first probability of the main device pre-connecting and interacting with the first extended device through the first connection type, it can be further determined whether the first probability of use falls within the range of the first probability of use, without making specific restrictions here.

[0078] S203: Control the main device and the first expansion device to establish a pre-connection through the first connection type.

[0079] In some embodiments of this application, after determining that the first usage probability is greater than or equal to the first usage probability threshold, the master device can establish a pre-connection with the first extension device through the first connection type.

[0080] In other embodiments of this application, when the first usage probability is determined to be within the first usage probability range, the master device can establish a pre-connection with the first extension device through the first connection type.

[0081] S204: Control the master device and the first expansion device to not establish a pre-connection through the first connection type.

[0082] In some embodiments of this application, after determining that the first usage probability is less than the first usage probability threshold, the master device may establish a pre-connection with the first extension device without using the first connection type.

[0083] Using the above method, when determining whether the master device should establish a pre-connection with the expansion device based on a certain connection type, it needs to ensure that the usage probability of that connection type is greater than or equal to a usage probability threshold. Only then will the master device establish a pre-connection with the expansion device through the corresponding connection type. Thus, when the usage probability of a connection type does not meet the condition, the master device will not establish a pre-connection based on that connection type. If the connection type is a high-power connection type, the master device can avoid maintaining a pre-connection state with the corresponding expansion device without interacting with the expansion device, thus avoiding the pre-connection power consumption.

[0084] To better understand the technical solutions of the embodiments of this application, the following is combined with... Figure 3 The flowchart shown provides a detailed explanation of the process of establishing a communication connection between the master device and the expansion device in advance.

[0085] Figure 3 A specific flowchart of a networking method is shown according to an embodiment of this application. It can be understood that... Figure 3 The execution entity for all processes shown is the master device. For simplicity, the following description... Figure 3 The execution entity will not be described again when the process is shown.

[0086] like Figure 3 As shown, the process includes:

[0087] S301: Get configuration information.

[0088] In some embodiments of this application, the master device can obtain configuration information through cloud servers, local storage, or other means.

[0089] It is understandable that configuration information can be used to instruct the master device whether to establish a pre-connection according to the networking policy, and to instruct the master device how to establish the pre-connection.

[0090] It is understood that the above configuration information may include different configuration levels that can be matched with different networking strategies. The higher the configuration level, the lower the networking frequency. Each configuration level includes matching information and control information corresponding to that configuration level.

[0091] It can be understood that the matching information includes relevant parameters of the master device when establishing a pre-connection within a historical period. This matching information is used to match relevant information in the network topology policy that can be matched with it, in order to determine the configuration level corresponding to the network topology policy. The control information is used to specify the conditions that must be met when instructing the master device to establish a pre-connection with the corresponding extension device.

[0092] For example, Table 1 shows a configuration information that includes different matching information and different control information corresponding to different configuration levels.

[0093] Table 1

[0094]

[0095] Referring to Table 1, as an example, configuration information may include configuration levels such as "L0" and "L1". Each configuration level may include matching information "scope" and control information "ploy". The matching information "scope" may include configuration items "dayProb", "avgTimes", "maxProb", "timeProb" and the configuration values ​​set for each configuration item.

[0096] Specifically, "dayProb" can represent the percentage of days with network deployment within a historical period, "avgTimes" can represent the average number of network deployments within a historical period, "maxProb" can represent the maximum percentage of days with network deployment within the same time period within a historical period, and "timeProb" can represent the predicted probability of network deployment time periods. The control information "ploy" can include "screen," "power," "applist," "linkProb," and "keepDur." Specifically, "screen" can indicate that the main device needs to be in a screen-on state, "power:" can indicate whether to accumulate the pre-connection duration of the main device, "applist" can represent the application package name, "linkProb" can represent the probability range of use for pre-connection and interaction based on the corresponding connection type, and "keepDur" can represent the duration of a single pre-connection. It can be understood that in some embodiments, if the main device is detected to be in a black screen state, it can indicate that the main device is currently in an inactive state. Therefore, the main device can avoid establishing pre-connections in a black screen state, thus avoiding the connection power consumption caused by establishing pre-connections in a black screen state.

[0097] For example, in the matching information "scope" for configuration level "L0":

[0098] The configuration value of "dayProb" is [0.3, 1.0], which means that the percentage of days the main device has been in the network within the historical number of days needs to be within the range of [0.3, 1.0].

[0099] A configuration value of 1 for “avgTimes” indicates that the average number of times the main device forms a network within a historical number of days needs to be greater than or equal to 1.

[0100] The configuration value of "maxProb" is 0.9, which means that the maximum percentage of network days in the same period of the historical data of the main device needs to be less than 0.9.

[0101] The configuration value of "timeProb" is [0.60, 1], which means that the prediction probability of the network time period corresponding to the master device needs to be within the range of [0.60, 1].

[0102] In addition, in the control information "ploy" for configuration level "L0":

[0103] A “screen” configuration value of 1 indicates that the host device’s screen needs to be on when establishing a pre-connection.

[0104] The configuration value of "power" is 2, which can indicate that the pre-connection time can be unlimited after the master device establishes a pre-connection. For example, if the maximum pre-connection time is 360s, then the pre-connection time can exceed 360s.

[0105] The configuration value of "applist" is ["application package name"], which can instruct the host device to establish a pre-connection when entering the application corresponding to the package name in the application package name;

[0106] The configuration value of “linkProb” is [0.5, 1], which indicates that the probability of the master device establishing a pre-connection and interacting with the extension device through a certain connection type needs to be within the range of [0.5, 1], or the probability of use needs to be greater than or equal to 0.5;

[0107] The “keepDur” configuration value of 360s indicates the duration of a single pre-connection when the master device is in a pre-connection state.

[0108] For example, in the matching information "scope" for configuration level "L1":

[0109] The configuration value of "dayProb" is [0, 0.3], which means that the percentage of days the main device has been in the network within the historical number of days needs to be within the range of [0, 0.3].

[0110] A configuration value of 1 for “avgTimes” indicates that the average number of times the main device forms a network within a historical number of days needs to be greater than or equal to 1.

[0111] A configuration value of 0.9 for "maxProb" indicates that the maximum percentage of network days for the main device within the same historical period must be less than 0.9.

[0112] The configuration value of "timeProb" is [0, 0.6], which means that the prediction probability of the network time period corresponding to the master device needs to be within the range of [0, 0.6].

[0113] In addition, in the control information "ploy" for configuration level "L1":

[0114] A “screen” configuration value of 1 indicates that the host device’s screen needs to be on when establishing a pre-connection.

[0115] The configuration value of "power" is 1, which can indicate that the pre-connection time after the master device establishes a pre-connection cannot be greater than the maximum pre-connection time. For example, if the maximum pre-connection time is 360s, then the pre-connection time cannot exceed 360s.

[0116] The configuration value of "applist" is ["application package name"], which can instruct the host device to establish a pre-connection when entering the application corresponding to the application package name;

[0117] The configuration value of “linkProb” is [0, 0.5], which indicates that the probability of the master device establishing a pre-connection and interacting with the extension device through a certain connection type needs to be within the range of [0, 0.5].

[0118] The “keepDur” configuration value of 360s indicates the duration of a single pre-connection when the master device is in a pre-connection state.

[0119] It is understood that the values ​​or ranges of parameters in the matching and control information of the above configuration levels are merely illustrative. In other embodiments, the parameters corresponding to the matching and control information in different configuration levels may be other values ​​or ranges, which are not limited here.

[0120] It is understood that when defining configuration information, "userGrade" can be used to represent the configuration information; when defining the maximum pre-connection duration, "totalDur" can be used to represent the maximum pre-connection duration, that is, the longest time that the main device and the extended device maintain a pre-connection state. In addition, the naming or assignment of each parameter in the embodiments of this application is only an exemplary illustration. In other embodiments, the names or assignments of each parameter can be other values, and no specific restrictions are made here.

[0121] S302: Receive the networking policy and match the networking policy with the matching information of the same type in the matching information and the matching information in the configuration information.

[0122] In some embodiments of this application, the master device can receive a pre-networking notification, which may include a networking policy. When the master device receives the networking policy, it can match the networking policy with the matching information corresponding to different configuration levels in the configuration information in S301.

[0123] It is understood that the networking strategy may include: the percentage of days in which the main device and extended devices successfully networked within a historical period ("validDaysPercent"), the average number of times the main device and extended devices networked within a historical period ("validUseCnt"), the maximum percentage of days in which the main device and extended devices networked within the same time period within a historical period ("maxSlotDaysPercent"), the predicted probability of network formation time periods for the main device and extended devices ("timeProb"), and the probability of extended devices establishing pre-connections and interacting with the main device through different connection types ("intentProb"). It is understood that the networking strategy can be provided to the main device in the form of a pre-networking notification, without specific restrictions.

[0124] In some embodiments of this application, the process of matching the networking policy with the matching information in the configuration information may include one or more of the following dimensions: determining whether the value corresponding to “validDaysPercent” in the networking policy is within the range of “dayProb” in the matching information; determining whether the value corresponding to “validUseCnt” in the networking policy is greater than or equal to “avgTimes” in the matching information; determining whether the value corresponding to “maxSlotDaysPercent” in the networking policy is less than or equal to “maxProb” in the matching information; determining whether the value corresponding to “timeProb” in the networking policy is within the range of “timeProb” in the matching information, etc., without specific limitations.

[0125] For example, Table 2 shows a pre-networking notification, which may include a networking strategy.

[0126] Table 2

[0127]

[0128]

[0129] Referring to Table 2, as an example, the pre-networking notification may include, for example, the notification type "action", the corresponding business domain "business", and the notification version number "version". It also includes networking strategies for matching with the matching information in the configuration information: the percentage of days the main device and extended devices successfully networked within the historical period "validDaysPercent", the average number of times the main device and extended devices networked within the historical period "validUseCnt", the maximum percentage of days the main device and extended devices networked within the same time period within the historical period "maxSlotDaysPercent", the predicted probability of networking time periods for the main device and extended devices "timeProb", and the usage probability corresponding to the extended device establishing a pre-connection and interacting with the main device through different connection types "intentProb", etc.

[0130] In addition, network topology strategies may also include the duration of the service ("dura"), the start time of the service ("startTime"), the end time of the service ("endTime"), the intentProb object ("devType") for mobile devices ("devType"), the identifier of the extended device ("ID"), the duration of a single pre-connection of the service ("keepDura"), and the time to wait for the pre-connection service to execute ("waitDura").

[0131] For example, in the pre-network notification:

[0132] The field corresponding to "action" being AiRegularNetwork indicates that the notification is related to intelligent network services.

[0133] The field corresponding to "business" being AiNetworking indicates that the business area corresponding to this notification is intelligent network management;

[0134] The field corresponding to "version" being 1 indicates that the notification is a version number;

[0135] The field corresponding to “dura” being 10 indicates that the duration of the business in this notification is 10 seconds.

[0136] The field corresponding to “startTime” being 14:00:00 indicates that the business started at 14:00:00.

[0137] The field corresponding to "endTime" being 14:02:00 indicates that the business ended at 14:02:00.

[0138] The field corresponding to "ID" is 508B686875376D27, which can indicate that the identifier of the extended device is 508B686875376D27.

[0139] The field corresponding to “devType” being PHONE indicates that the intentProb object is for a mobile device (PHONE).

[0140] The value of 15 in the field corresponding to “keepDura” indicates that the duration of the business in this notification is 15 seconds.

[0141] The field value of 15 corresponding to “waitDura” indicates that the waiting time for the pre-connection service to be executed in this notification is 15 seconds.

[0142] The field corresponding to “validDaysPercent” is 0.5, which means that the percentage of days the network was formed within the historical number of days is 0.5.

[0143] The value of 100 for the field corresponding to “validUseCnt” indicates the average number of times the network was configured within the historical number of days. “validUseCnt” is 100 times.

[0144] The value of 0.6 for the field corresponding to “maxSlotDaysPercent” indicates that the maximum percentage of network days within the same time period in the historical data is 0.6.

[0145] The value of 0.5 in the "timeProb" field indicates that the predicted probability for this network time period is 0.5.

[0146] The field corresponding to “intentProb” is P2PINVALID: 0.0925, which means that the probability of failing to establish a pre-connection via P2P is 0.0922.

[0147] The field corresponding to “intentProb” is P2P2.4G: 0.0922, which means that the probability of establishing a pre-connection and interacting through P2P 2.4G is 0.0922.

[0148] The field corresponding to “intentProb” is WLAN 5G: 0.0918, which means that the probability of failing to establish a pre-connection via WLAN 5G is 0.0918.

[0149] The field corresponding to “intentProb” is Bluetooth Low Energy (BLE): 0.921 indicates that the probability of failing to establish a pre-connection via BLE is 0.921.

[0150] The field corresponding to “intentProb” is WLAN 5G: 0.0919, which means that the probability of failing to establish a pre-connection via WLAN 5G is 0.0919.

[0151] The field corresponding to “intentProb” is WLAN 2.4G: 0.0919, which means that the probability of failing to establish a pre-connection via WLAN 2.4G is 0.0919.

[0152] The field corresponding to “intentProb” is BR:0915, which means that the probability of failing to establish a pre-connection through BR is 0.0915.

[0153] It is understood that the aforementioned pre-networking notification includes part of the networking strategy, which also includes other extended devices that can establish pre-connections with the main device and their corresponding connection types, etc., without specific restrictions here.

[0154] S303: Determine whether the networking strategy matches the matching information in the configuration information.

[0155] If the judgment result is yes, proceed to S304 to determine whether to enter the target application;

[0156] If the result is negative, return to S302.

[0157] In some embodiments of this application, after obtaining the networking policy, it can be determined whether the networking policy matches the matching information in the configuration information.

[0158] For example, the judgment can be made based on one or more of the following dimensions: whether the value corresponding to "validDaysPercent" in the networking policy is within the range of "dayProb" in the matching information; or whether the value corresponding to "validUseCnt" in the networking policy is greater than or equal to "avgTimes" in the matching information; or whether the value corresponding to "maxSlotDaysPercent" in the networking policy is less than or equal to "maxProb" in the matching information; or whether the value corresponding to "timeProb" in the networking policy is within the range of "timeProb" in the matching information. No specific restrictions are imposed here.

[0159] S304: Determine whether to enter the target application.

[0160] If the judgment result is yes, proceed to S305, and determine whether to perform pre-connection service based on control information;

[0161] If the result is negative, the process ends.

[0162] In some embodiments of this application, before performing pre-connection services based on the control information in the configuration information, it is necessary to determine whether the master device is targeting the application. It can be understood that the target application is the application corresponding to the application package name in the "applist" of the control information in the configuration information. For example, the target application may include audio applications, document display applications, etc., without specific limitations here.

[0163] It is understandable that the applications corresponding to the application package names in "applist" can use the corresponding functions of the extended device based on the pre-connection established between the primary device and the extended device.

[0164] S305: Determine whether to perform pre-connection services based on control information.

[0165] If the judgment result is yes, proceed to S306 and establish a pre-connection based on the control information in the configuration information;

[0166] If the result is negative, the process ends.

[0167] In some embodiments of this application, the determination of whether to perform pre-connection services can be based on control information in the configuration information. For example, based on "screen": 1 in the control message, it indicates that it is necessary to determine whether the screen state of the main device is on; based on "linkProb": [0, 0.6] in the control message, it indicates that it is necessary to determine whether the usage probability of different connection types in the networking strategy is within the current range, or to determine a usage probability threshold and determine whether the usage probability of different connection types in the networking strategy is greater than or equal to the usage probability threshold.

[0168] S306: Pre-connect based on control information in configuration information.

[0169] In some embodiments of this application, if it is determined that the screen state of the main device is on, and the probability of using a connection type in the networking strategy is within the range of "linkProb" or greater than or equal to the probability threshold, then a pre-connection can be established between the main device and the corresponding extended device.

[0170] In some embodiments of this application, if it is determined that the networking strategy matches the matching information in the configuration information, for example, the "validDaysPercent": 0.5 in the networking strategy is within the range of "dayProb": [0.3, 1.0] in the matching information; the "validUseCnt": 100 in the networking strategy is greater than the "avgTimes": 1 in the matching information; the "maxSlotDaysPercent": 0.6 in the networking strategy is less than the "maxProb": 0.9 in the matching information; and the "timeProb": in the networking strategy is within the range of "timeProb": [0.60, 1] in the matching information, then it can be determined that the networking strategy matches the matching information in the configuration information, and the configuration level corresponding to the networking strategy is determined to be "L0".

[0171] Furthermore, the control information "ploy" in "L0" is obtained, and preparations can be made to perform pre-connection services based on the control information "ploy" corresponding to "L0". For example, preparations can be made to perform pre-connection services based on "screen": 1, "power": 2, "linkProb": [0,1], and "keepDur": 360 in the control information "ploy" in "L0". That is, when the main device is in a screen-on state, the main device and the corresponding extended device establish a pre-connection through a first connection type, where the first usage probability corresponding to the first connection type needs to be within "linkProb": [0,1]. In addition, after the main device and the corresponding extended device establish a pre-connection through the first connection type, the pre-connection duration can exceed the maximum pre-connection duration of 360 seconds.

[0172] For example, the networking strategy includes two extension devices, a and b, that can currently establish a pre-connection with the main device. Extension device a has a BLE connection type and a usage probability of 0.921, while extension device b has a WLAN direct connection (e.g., P2P 2.4G, P2P 5G) and a usage probability of 0.0921. If the BLE usage probability of 0.921 is within the range of "linkProb": [0.5, 1] ​​or greater than the probability threshold of 0.5, then the main device can be controlled to establish a pre-connection with extension device a based on the BLE connection type. Conversely, if the WLAN direct connection (e.g., P2P 2.4G, P2P 5G) usage probability of 0.0921 is not within the range of "linkProb": [0.5, 1] ​​or less than the probability threshold of 0.5, then the main device and extension device b will not establish a pre-connection based on the WLAN direct connection type (e.g., P2P 2.4G, P2P 5G).

[0173] S307: Determine whether the pre-connection duration is greater than the pre-connection duration threshold.

[0174] If the judgment result is yes, proceed to S308 to determine whether to exit the target application;

[0175] If the judgment result is negative, continue to execute S307.

[0176] In some embodiments of this application, timing begins after the master device and extension device a establish a pre-connection. If the pre-connection duration between the master device and extension device a exceeds the pre-connection duration threshold "keepDur", for example, 360 seconds, the timing is determined. In some embodiments, the pre-connection duration threshold can be determined based on the maximum pre-connection duration within a historical time period (i.e., the maximum pre-connection duration). Furthermore, in addition to determining whether the pre-connection duration is greater than the pre-connection duration threshold "keepDur", in other embodiments, it can also be determined whether the pre-connection duration is greater than the maximum pre-connection duration "totalDur".

[0177] S308: Determine whether to exit the target application.

[0178] If the judgment result is yes, proceed to S309 and disconnect the pre-connection;

[0179] If the judgment result is negative, continue to execute S308.

[0180] In some other embodiments of this application, after the main device and the extended device a establish a pre-connection, it is possible to detect in real time whether the main device exits the target application. If the main device exits the target application...

[0181] It is understandable that the order of judgments in S307 and S308 can be changed. For example, S308 can be executed before S307, or the judgment processes of S307 and S308 can be executed synchronously. No specific restrictions are imposed here.

[0182] S309: Disconnect pre-connection.

[0183] In some embodiments of this application, when it is determined that the pre-connection duration between the master device and the extension device is greater than the maximum pre-connection duration, and the master device and the corresponding extension device have not interacted, the pre-connection between the master device and the corresponding extension device can be disconnected to reduce the connection power consumption of the master device.

[0184] In some embodiments of this application, when it is determined that the main device has exited the target application, the main device can be controlled to disconnect from the pre-connection with the corresponding extended device in order to reduce the connection power consumption of the main device.

[0185] Based on this, the master device will only establish a pre-connection with the extension device based on the corresponding connection type if the probability of the master device and the extension device establishing a pre-connection and interacting with each other using the first connection type is greater than or equal to a probability threshold. When the probability of using a connection type does not meet the condition, the master device will not establish a pre-connection based on that connection type. If the connection type is a high-power connection type, the master device can avoid the pre-connection power consumption caused by maintaining a pre-connection state with the corresponding extension device through that connection type without interacting with the extension device.

[0186] It is understandable that if the main device exits the target application, or if the pre-connection duration between the main device and the corresponding extended device exceeds the maximum pre-connection duration and the main device and the corresponding extended device do not interact, the pre-connection between the main device and the extended device can be disconnected to reduce the connection power consumption of the main device.

[0187] The software architecture of the electronic device in the embodiments of this application is described below with reference to the accompanying drawings. It can be understood that the electronic device can be an electronic device within a device group, that is, it can be a main device or an extension device.

[0188] The software system of an electronic device can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to illustrate the software structure of an electronic device.

[0189] Figure 4 A schematic diagram of the software structure of an electronic device is shown according to an embodiment of this application. The electronic device may refer to the main device mobile phone 10 in the embodiment of this application, and no specific limitation is made here.

[0190] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, Android... TM The system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0191] like Figure 4 As shown, the application layer can include a series of application packages. These application packages can include applications such as camera, gallery, calendar, calling, map, conferencing, WLAN, Bluetooth, music, video, and instant messaging.

[0192] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0193] like Figure 4 As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, system settings 41, system Bluetooth 42, interconnect module 43, and smart module 44, etc.

[0194] System settings 41 can be used to monitor user operations and send system broadcasts to the smart module 44 and the interconnection module 43 to notify the smart module 44 and the interconnection module 43 to trigger events, such as entering a target application.

[0195] The system's Bluetooth 42 can be used to discover extended devices.

[0196] It is understandable that in the Android system, System Settings 41 and System Bluetooth 42 can be considered application-layer services, also known as system services. System Settings 41 and System Bluetooth 42 can be used to configure and adjust various options and parameters of the electronic device. That is to say, these services can refer to the interfaces provided by the framework layer to the application layer for accessing and operating lower-level system functions. In this embodiment, System Settings 41 and System Bluetooth 42 can be used to implement functions such as event listening and broadcasting.

[0197] The intelligent module 44 can be used to acquire historical interaction data and determine the network profile based on the historical interaction data. The intelligent module 44 can also be used to transmit the network strategy to the interconnection module 43 when the pre-connection conditions are met.

[0198] It can be understood that a networking strategy is a strategy used to instruct a master device to establish a pre-connection with a certain extension device based on a certain connection type.

[0199] The interconnection module 43 can be used to discover extended devices and complete device authentication, and establish pre-connections with extended devices based on networking policies. Furthermore, the interconnection module 43 can also be used to collect historical interaction data and transmit it to the smart module 44.

[0200] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0201] Content providers store and retrieve data, making that data accessible to applications. This data can include videos, images, audio, phone calls made and received, browsing history and bookmarks, phone books, etc.

[0202] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0203] A phone manager is used to provide communication functions for electronic devices. For example, it manages call status (including connection and disconnection).

[0204] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0205] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0206] The Android Runtime consists of the core libraries and the virtual machine. The Android Runtime is responsible for the scheduling and management of the Android system.

[0207] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0208] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0209] System libraries can include multiple functional modules. For example, a surface manager, media libraries, and 3D graphics processing libraries (such as OpenGL ES).

[0210] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0211] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0212] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, layer processing, etc.

[0213] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0214] Figure 5 An embodiment of this application illustrates an interactive process diagram of a master device determining how to pre-connect based on configuration information and networking policies.

[0215] like Figure 5 As shown, the process includes, but is not limited to, the following steps:

[0216] S501: The intelligent module 44 sends the networking strategy to the interconnection module 43 to determine the start of the prediction period.

[0217] In some embodiments of this application, after the smart module 44 detects that the master device meets the pre-connection conditions, it can send a networking strategy to the interconnection module 43. For example, the networking strategy can be the networking strategy in S302 above.

[0218] It is understandable that the predicted time period refers to the period during which the master device may establish a pre-connection. For example, in the networking policy, "startTime":"14:00:00" and "endTime":"14:02:00", this interval can represent the predicted time period.

[0219] S502: Interconnection module 43 matches the networking strategy and configuration information to determine the connection strategy for the master device to establish a pre-connection.

[0220] In some embodiments of this application, the process by which the interconnection module 43 matches the network strategy with the configuration information may include: obtaining "validDaysPercent", "validUseCnt", "maxSlotDaysPercent", and "timeProb" from the network strategy. Further, it determines whether the value corresponding to "validDaysPercent" in the network strategy is within the range of "dayProb" in the corresponding matching information in the configuration information; whether the value corresponding to "validUseCnt" in the network strategy is greater than or equal to "avgTimes" in the corresponding matching information in the configuration information; whether the value corresponding to "maxSlotDaysPercent" in the network strategy is less than or equal to "maxProb" in the matching information; and whether the value corresponding to "timeProb" in the network strategy is within the range of "timeProb" in the matching information. If one or more of these values ​​match, the corresponding configuration level in the configuration information is determined.

[0221] For example, the network policy's "validDaysPercent": 0.5 is within the range of "dayProb": [0.3, 1.0] in the matching information; the network policy's "validUseCnt": 100 is greater than the matching information's "avgTimes": 1; the network policy's "maxSlotDaysPercent": 0.6 is less than the matching information's "maxProb": 0.9; and the network policy's "timeProb" is within the range of the matching information's "timeProb": [0.60, 1]. Based on this, it can be determined that the network policy matches the matching information in the configuration information, and the configuration level corresponding to the network policy in the configuration information is determined to be "L0".

[0222] Furthermore, the process by which the interconnect module 43 determines the connection strategy for establishing a pre-connection of the main device may include: obtaining the control information "ploy" in the configuration level "L0" according to the configuration level "L0" corresponding to the networking strategy. Further, the connection strategy for establishing the pre-connection is determined based on the control information in the configuration information. For example, based on "screen": 1, "power": 2, "linkProb": [0,1], and "keepDur": 360 in the control information "ploy" in "L0", the connection strategy for establishing a pre-connection of the main device is determined as follows: the main device's display screen needs to be on; the pre-connection duration of the main device is not limited by the maximum pre-connection duration "totalDur" and can exceed the maximum pre-connection duration "totalDur", such as 360s; the probability of using the connection type for establishing a pre-connection of the main device needs to be within [0,1].

[0223] S503: Interconnect module 43 sends a notification to system settings 41 regarding the target application being monitored.

[0224] In some embodiments of this application, after the interconnection module 43 determines the connection strategy for establishing a pre-connection of the master device based on the network strategy and configuration information, the interconnection module 43 can further send a notification to the system settings 41 to monitor the target application. The target application may refer to the application corresponding to "applist": ["application package name"] in the configuration information. Monitoring the target application means monitoring the startup and exit of the target application, as well as monitoring the execution of business functions by the target application, etc., without specific limitations.

[0225] S504: System settings 41 returns a notification to interconnect module 43 that the target application has been started.

[0226] In some embodiments of this application, when system settings 41 detects that a target application has started, a notification that the target application has started can be sent to the interconnect module 43.

[0227] S505: Interconnect module 43 performs pre-connection based on the corresponding control information in the configuration information.

[0228] In some embodiments of this application, based on the notification that the target application has been started returned by the system settings 41 in S504, the interconnect module 43 can establish a pre-connection between the master device and the corresponding extension device based on the corresponding connection type according to the control information corresponding to the configuration level "L0" determined in S502.

[0229] S506: System settings 41 sends a notification to interconnect module 43 that the target application uses the service based on the P2P connection type.

[0230] In some embodiments of this application, after the main device establishes a pre-connection with the corresponding extended device based on the corresponding connection type, the system setting 41 detects that the target application uses services based on the P2P connection type.

[0231] For example, the target application in the main device starts, and the main device establishes a pre-connection with the extended device a via Bluetooth. Furthermore, the main device executes the service corresponding to the target application through the extended device a. Then, system setting 41 can detect that the main device has performed the corresponding service of the target application on the extended device a via Bluetooth. And system setting 41 can send a notification to the interconnect module 43 that the target application is using the service based on the P2P connection type.

[0232] S507: Interconnect module 43 establishes pre-connection count +1 based on P2P connection type.

[0233] In some embodiments of this application, if the main device and the extended device a are detected to establish a pre-connection based on Bluetooth and have business interaction based on the target application in S506, the interconnection module 43 can record the number of times the main device successfully establishes a pre-connection with the corresponding extended device based on the P2P connection type + 1.

[0234] S508: System settings 41 sends a notification to interconnect module 43 that the target application has exited.

[0235] In some embodiments of this application, when system settings 41 detects that the target application has exited in the main device, system settings 41 may send a notification to the interconnect module 43 that the target application has been closed.

[0236] S509: Interconnect module 43 disconnects pre-connection.

[0237] In some embodiments of this application, when the interconnect module 43 receives a notification from the system settings 41 that the target application in the main device has exited, the interconnect module 43 can control the disconnection of the pre-connection established between the main device and the extension device a via BLE.

[0238] Thus, since the target application in the main device has exited, it indicates that the main device's need to use the extended device a through pre-connection to complete the business corresponding to the target application has ended. Therefore, the pre-connection with the extended device a can be disconnected in a timely manner to reduce the connection power consumption caused by the pre-connection.

[0239] S510: Interconnect module 43 detects the end of the predicted period and increments the number of failed pre-connection attempts for the corresponding P2P connection type that failed to establish a pre-connection by 1.

[0240] In some embodiments of this application, if the interconnect module 43 detects the end of the prediction period, corresponding to the number of times the master device failed to establish a pre-connection with the corresponding extension device based on the corresponding P2P connection type during the prediction period, then the number of failed pre-connection establishments based on the corresponding P2P connection type is incremented by 1.

[0241] Figure 6 An embodiment of this application illustrates a flowchart of a master device acquiring and updating configuration information.

[0242] like Figure 6 As shown, this process may include, but is not limited to, the following steps:

[0243] S601: The intelligent module 44 sends configuration information and networking strategies to the interconnection module 43.

[0244] In some embodiments of this application, when the master device starts up, the smart module 44 can send networking strategies and configuration information to the interconnection module 43. The configuration information can be the configuration information in S301 above, and the networking strategy can be the networking strategy in S302 above, etc., without specific limitations.

[0245] It is understandable that the configuration information provided by the smart module 44 to the interconnection module 43 can be the maximum range of configuration information. The maximum range of configuration information means that the configuration information includes multiple configuration levels, and different networking strategies can be matched with the corresponding configuration level in this configuration information.

[0246] S602: Interconnection module 43 performs pre-connection based on networking strategy and configuration information, and determines the pre-connection result.

[0247] In some embodiments of this application, the process of pre-connecting according to the networking strategy and configuration information and determining the pre-connection result can refer to the above S301 to S309, and will not be repeated here.

[0248] For example, the pre-connection result could be: the master device matches the corresponding level "L0" in the configuration information through the networking strategy, and based on the control information corresponding to "L0", successfully establishes a pre-connection with the corresponding extended device a at time t1 and location A1 via Bluetooth.

[0249] For example, the pre-connection result could be: the main device matches the corresponding configuration level "L1" in the configuration information through the networking strategy, but based on the control information corresponding to the configuration level "L1", the pre-connection with the extended device b at time t1 and location A1 based on Wi-Fi direct connection fails.

[0250] It is understandable that the pre-connection result may include the configuration level matched by the master device through the networking policy, and whether the master device has successfully established a pre-connection with the corresponding extended device based on the control information corresponding to the matched configuration level.

[0251] It is understandable that the pre-connection result can include either a successful pre-connection or a failed pre-connection.

[0252] S603: The interconnection module 43 sends the pre-connection result to the smart module 44.

[0253] In some embodiments of this application, based on the pre-connection result obtained by the interconnection module 43 in S602, the interconnection module 43 can send the pre-connection result to the smart module 44.

[0254] S604: Smart module 44 adjusts configuration information based on pre-connection results.

[0255] In some embodiments of this application, after the smart module 44 receives the pre-connection result sent by the interconnection module 43, the smart module 44 can statistically analyze the current pre-connection success rate and the historical pre-connection success rate of the same connection type. For example, it can calculate the sum of the current successful pre-connection establishment via Bluetooth and the historical successful pre-connection establishment via Bluetooth, and divide it by the total number of pre-connection establishments via Bluetooth to obtain the success rate of pre-connection establishment via Bluetooth.

[0256] Furthermore, it can be determined whether the success rate of establishing a pre-connection based on Bluetooth reaches the expected success rate threshold (e.g., 90%). If not, the range of each configuration item in the matching information corresponding to the configuration level in the configuration information can be reduced. For example, the configuration value of the configuration item "dayProb" in the matching information of configuration level "L0" can be reduced from [0.3, 1.0] to [0.3, 0.6], or the configuration value of "maxProb" can be reduced from 0.9 to 0.5, or the configuration value of "timeProb" can be reduced from [0, 0.60] to [0, 0.5], etc., without specific restrictions here.

[0257] In some other embodiments of this application, after obtaining the pre-connection result, the smart module 44 can also determine the control information corresponding to the configuration level in the configuration information for different connection types, and whether the power consumption increment generated when establishing the pre-connection exceeds the preset power consumption increment threshold.

[0258] For example, if the main device establishes a pre-connection with the corresponding extended device via Bluetooth based on the control information corresponding to configuration level "L0", and the resulting power consumption increment exceeds a preset power consumption increment threshold, the range of each configuration item in the matching information corresponding to the configuration level can be reduced. For example, the configuration value of the configuration item "dayProb" in the matching information "scope" of configuration level "L0" can be reduced from [0.3, 1.0] to [0.3, 0.6], or the configuration value of "maxProb" can be reduced from 0.9 to 0.5, or the configuration value of "timeProb" can be reduced from [0, 0.60] to [0, 0.5], etc., without specific restrictions.

[0259] It is understood that the above example of adjusting the matching information corresponding to configuration level "L0" is merely an illustrative illustration. In other embodiments, where the pre-connection result corresponds to establishing a pre-connection with the control information corresponding to other configuration levels, the range of configuration items in the matching information of other configuration levels can be adjusted accordingly, without specific limitations here.

[0260] It's understandable that if there are significant differences in the pre-connection success rates for different connection types, the range of control items in the "ploy" control information of the corresponding configuration level can be modified. For example, if the success rate of establishing a pre-connection via Bluetooth based on the control information corresponding to configuration level "L0" is much higher than the success rate of establishing a pre-connection via Wi-Fi Direct based on the control information corresponding to configuration level "L0", then the range of control items in the "ploy" control information corresponding to "L0" can be reduced.

[0261] S605: The intelligent module 44 sends the adjusted configuration information to the interconnection module 43.

[0262] In some embodiments of this application, the intelligent module 44 can send the adjusted configuration information to the interconnection module 43. Thus, when the master device next determines the configuration level corresponding to the networking strategy in the configuration information based on the networking strategy, the interconnection module 43 can determine the configuration level corresponding to the networking strategy based on the adjusted configuration information, and then establish a pre-connection through the control information corresponding to the matched configuration level.

[0263] For example, Figure 7 A schematic diagram of the structure of an electronic device 100 is shown according to an embodiment of this application.

[0264] like Figure 7 As shown, the electronic device 100 may include a processor 110, a memory 120, an interface module 130, a power module 140, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, buttons 190, a camera 191, a display screen 192, etc.

[0265] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0266] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0267] In some embodiments, the processor 110 may be used to execute the networking method provided in the embodiments of this application.

[0268] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0269] Interface module 130 may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0270] The power module 140 is connected to the processor 110 and provides power to the processor 110, memory 120, camera 191, display screen 192, and mobile communication module 150.

[0271] The wireless communication function of electronic device 100 can be implemented through mobile communication module 150, wireless communication module 160, antenna, modem processor and baseband processor, etc.

[0272] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (such as Wi-Fi networks), Bluetooth, global navigation satellite system (GNSS), frequency modulation (FM), NFC, infrared technology, etc.

[0273] In some embodiments, wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TDSCDMA), LTE, NR, BT, GNSS, WLAN, NFC, FM, and / or IR technologies. GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0274] In some embodiments, the master device and the extension device can establish a communication connection through wireless communication technology.

[0275] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on the electronic device 100. In some embodiments, the main device and the extended device can also establish a communication connection through mobile communication technology.

[0276] Audio module 170 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. Audio module 170 can also be used for encoding and decoding audio signals.

[0277] The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0278] Electronic device 100 implements display functions through GPU, display screen 192, and application processor.

[0279] The display screen 192 is used to display images, videos, etc. The display screen 192 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini-LED, a Micro-LED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 192, where N is a positive integer greater than 1.

[0280] Electronic device 100 can perform shooting functions through ISP, camera 191, video codec, GPU, display 192 and application processor.

[0281] Camera 191 is used to capture still images or videos.

[0282] The memory 120 can be used to store computer executable program code, including instructions. The memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.). Furthermore, the memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the memory 120 and / or instructions stored in memory disposed in the processor.

[0283] Button 190 includes the power button, volume buttons, etc. Button 190 can be a mechanical button or a touch button.

[0284] In some embodiments, a computer-readable storage medium is also provided, which stores at least one instruction, at least one program, code set, or instruction set, which is loaded and executed by a processor to implement the networking method provided in the above-described method embodiments.

[0285] In some embodiments, a program product is also provided, which includes instructions that, when executed by an electronic device, enable the electronic device to implement the networking method provided in the embodiments of this application.

[0286] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0287] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0288] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0289] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable media include any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0290] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Furthermore, the inclusion of structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0291] It should be noted that all units / modules mentioned in the embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problem proposed in this application. Furthermore, to highlight the innovative aspects of this application, the embodiments of this application have not introduced units / modules that are not closely related to solving the technical problem proposed in this application. This does not mean that the above device embodiments do not contain other units / modules.

[0292] It should be noted that in the examples and description of this patent, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0293] Although this application has been illustrated and described with reference to certain preferred embodiments thereof, those skilled in the art should understand that various changes in form and detail may be made thereto without departing from the spirit and scope of this application.

Claims

1. A networking method, characterized in that, Applied to electronic devices, the method includes: The first probability of the electronic device establishing a pre-connection and interacting with the extended device through the first connection type is determined based on historical data, wherein the historical data includes the interaction duration and number of interactions between the electronic device and the extended device through the first connection type within a historical time period; A first package name set is obtained based on preset first configuration information, wherein each package name in the first package name set corresponds to an application that supports the extended device, and the application corresponding to each package name in the first package name set includes the first application. Determine whether the first usage probability is greater than or equal to a first usage probability threshold and whether the electronic device launches the first application; When the first usage probability is greater than or equal to the first usage probability threshold and the electronic device launches the first application, the electronic device is controlled to establish a pre-connection with the extended device through the first connection type. If the first usage probability is less than the first usage probability threshold, the electronic device and the extended device are controlled not to establish a pre-connection based on the first connection type.

2. The method according to claim 1, characterized in that, The step of controlling the electronic device and the extended device to establish a pre-connection via a first connection type corresponding to a first usage probability greater than or equal to a first usage probability threshold further includes: Determine whether the electronic device is in a screen-on state; When the electronic device is in a screen-on state, control the electronic device to establish a pre-connection with the extended device through a first connection type.

3. The method according to claim 1, characterized in that, The preset first configuration information is information used to guide the electronic device in establishing a pre-connection.

4. The method according to claim 3, characterized in that, The step of obtaining a first package name set based on preset first configuration information and determining whether the electronic device has launched the first application further includes: When the electronic device does not launch the first application, the electronic device is controlled not to establish a pre-connection with the extended device based on the first connection type.

5. The method according to claim 3, characterized in that, The step of controlling the electronic device to establish a pre-connection with the extended device based on the first connection type, corresponding to the electronic device launching the first application and the first usage probability being greater than or equal to the first usage probability threshold, further includes: Determine whether the electronic device has exited the first application; Corresponding to the electronic device exiting the first application, the electronic device disconnects from the pre-connection established by the extended device based on the first connection type.

6. The method according to claim 1, characterized in that, The step of controlling the electronic device and the extended device not to establish a pre-connection based on the first connection type when the first usage probability is less than the first usage probability threshold further includes: The first duration of the pre-connection established between the electronic device and the extended device based on the first connection type is obtained, and it is determined whether the first duration is greater than the first pre-connection duration threshold. When the first duration exceeds the first pre-connection duration threshold, the electronic device disconnects from the pre-connection established by the extended device based on the first connection type.

7. The method according to claim 1, characterized in that, The method for determining the first probability threshold includes: Receive a first networking strategy, wherein the first networking strategy includes a first pre-connection probability, the first pre-connection probability representing the probability that the electronic device establishes a pre-connection through the first connection type within a first time period; Obtain preset first configuration information, wherein the preset first configuration information includes first matching information, the first matching information is used to match with the information corresponding to the first networking strategy, and the first matching information includes a first pre-connection probability threshold. The preset first configuration information includes first control information, which includes a first usage probability threshold, corresponding to the first pre-connection probability being greater than or equal to the first pre-connection probability threshold. The first usage probability threshold is determined based on the first control information.

8. The method according to claim 7, characterized in that, The method for determining the first probability threshold further includes: Obtain the maximum value of the percentage of days in the first network formation for the first historical period, the first average number of network formations, and the percentage of days in the first period included in the first network formation strategy, wherein the first historical period includes the number of historical days; The first matching information also includes a first network day percentage threshold, a first average number of network sessions threshold, and a first time period network day percentage maximum threshold; The first usage probability threshold is determined based on the preset first configuration information, corresponding to any one or more of the following: the proportion of the first network days is greater than or equal to the threshold of the proportion of the first network days; the first average number of network formations is greater than or equal to the threshold of the first average number of network formations; and the maximum proportion of the first time period network days is less than or equal to the threshold of the maximum proportion of the first time period network days.

9. An electronic device, characterized in that, include: The processor and memory, the memory including physical memory and secondary memory, are used to store instructions executed by one or more processors of the electronic device; And a processor for executing the instructions to cause the electronic device to implement the networking method of any one of claims 1 to 8.

10. A readable storage medium, characterized in that, The readable storage medium stores a computer program, which, when executed by a terminal device, causes the terminal device to implement the networking method according to any one of claims 1 to 8.

11. A computer program product, characterized in that, Includes a computer program / instruction that, when the computer program product is run on an electronic device, causes the electronic device to implement the networking method according to any one of claims 1 to 8.

Images