Bandwidth detection method, device, equipment, and storage medium

Abstract

Embodiments of the present application disclose a bandwidth detection method, apparatus, device, and storage medium; wherein the method includes: obtaining the device name of an electronic device accessing a gateway; determining whether the device name satisfies a naming rule; if so, using the electronic device as a target device; determining whether the bandwidth supported by the target device matches the processed bandwidth; wherein the processed bandwidth is the bandwidth processed by a user of a terminal device accessing the gateway through the target device.

Description

Technical Field

[0001] The embodiments of the present application relate to communication technology, and relate to but are not limited to a bandwidth detection method and apparatus, device, and storage medium. Background Art

[0002] With the development of network technology, people's frequency of terminal usage in daily life has further increased. Correspondingly, users' expectations for network quality have also increased, and operators are receiving an increasing number of network quality complaints. The reasons for this, in addition to issues with network quality itself, are also often due to a mismatch between the network broadband subscribed by users and the speed of the router they use. Therefore, how to determine whether the speed of the network broadband subscribed by users matches the speed of the router they use is a pressing issue facing operators. Summary of the Invention

[0003] In view of this, the bandwidth detection method, apparatus, device, and storage medium provided in the embodiments of the present application can improve the ability and range of identifying the target device, thereby improving the ability to identify whether the network bandwidth handled by the user matches the speed of the target device used. The bandwidth detection method, apparatus, device, and storage medium provided in the embodiments of the present application are implemented as follows:

[0004] The bandwidth detection method provided in an embodiment of the present application includes: obtaining a device name of an electronic device accessing a gateway; determining whether the device name satisfies a naming rule; if so, using the electronic device as a target device; and determining whether the bandwidth supported by the target device matches the processed bandwidth; wherein the processed bandwidth is the bandwidth processed by a user of a terminal device accessing the gateway through the target device.

[0005] The bandwidth detection device provided in an embodiment of the present application includes: an acquisition module, which is used to obtain the device name of an electronic device accessing a gateway; a determination module, which is used to determine whether the device name satisfies a naming rule; if so, the electronic device is used as a target device; the determination module is further used to determine whether the bandwidth supported by the target device matches the processed bandwidth; wherein the processed bandwidth is the bandwidth processed by a user of a terminal device accessing the gateway through the target device.

[0006] An electronic device provided in an embodiment of the present application includes a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the method described in the embodiment of the present application is implemented.

[0007] The computer-readable storage medium provided in the embodiment of the present application stores a computer program thereon, and when the computer program is executed by a processor, the method provided in the embodiment of the present application is implemented.

[0008] In an embodiment of the present application, the device name of the electronic device accessing the gateway is obtained, and then the electronic device whose device name meets the naming rules is determined to be the target device. In the related art, whether the electronic device is the target device is determined by determining whether the local area network address (Media Access Control Address, MAC) of the electronic device is the same as the MAC address of the target device. For the MAC address, it is difficult to obtain and the coverage is small; while the device name of the target device is enumerable, and for the target device, it is relatively easy to obtain its corresponding device name and store it. In this way, the naming rule library is determined in advance according to the device name of the target device. Compared with determining the MAC address library in advance according to the MAC address of the target device, the determination method is simpler, the coverage is wider, and the recognition ability is stronger. It can be seen that this method of determining whether the electronic device is the target device according to the device name can improve the recognition ability and recognition range of the target device, and thus improve the recognition ability of whether the network bandwidth handled by the user matches the rate of the target device used. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and, together with the specification, are used to illustrate the technical solutions of the present application.

[0010] Figure 1 A schematic diagram of an implementation flow of a bandwidth detection method provided in an embodiment of the present application;

[0011] Figure 2 A schematic diagram of an implementation flow of a bandwidth detection method provided in an embodiment of the present application;

[0012] Figure 3 A schematic diagram of an implementation flow of a method for determining a naming rule provided in an embodiment of the present application;

[0013] Figure 4 A schematic diagram of an implementation flow of a bandwidth detection method provided in an embodiment of the present application;

[0014] Figure 5 This is a schematic structural diagram of a bandwidth detection device according to an embodiment of the present application;

[0015] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] To make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the specific technical solutions of the present application will be further described in detail below in conjunction with the drawings in the embodiments of the present application. The following embodiments are used to illustrate the present application but are not intended to limit the scope of the present application.

[0017] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing the embodiments of this application only and are not intended to limit this application.

[0018] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0019] It should be pointed out that the terms "first\second\third" involved in the embodiments of the present application are used to distinguish similar or different objects, and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0020] An embodiment of the present application provides a bandwidth detection method, which is applied to an electronic device. During implementation, the electronic device can be various types of computer devices with information processing capabilities, such as personal computers (such as desktop computers, laptops, small laptops, tablet computers, and ultrabooks), mobile phones, personal digital assistants (PDAs), servers, etc. The functions implemented by the method can be implemented by a processor in the electronic device calling program code. Of course, the program code can be stored in a computer storage medium. Therefore, the electronic device includes at least a processor and a storage medium.

[0021] Figure 1 A schematic diagram of the implementation flow of the bandwidth detection method provided in the embodiment of the present application is shown as follows: Figure 1 As shown, the method may include the following steps 101 to 104:

[0022] Step 101: Obtain the device name of the electronic device connected to the gateway.

[0023] In an embodiment of the present application, the categories of electronic devices accessing the gateway may be diverse, and accordingly, the ways in which electronic devices of different categories access the gateway may also be different. For example, the access method may be a wireless connection, or the access method may be a wired connection.

[0024] In some embodiments, the target device accesses the gateway via a wired connection. Therefore, after obtaining the device name of the electronic device accessing the gateway, the device names of the multiple electronic devices can be cleaned. Specifically, the device names of electronic devices that access the gateway wirelessly are filtered out, and the device names of electronic devices with empty device name fields are filtered out. This allows the target device to be subsequently determined from the device names of the electronic devices obtained after filtering, reducing the amount of data to be identified and thereby speeding up the identification of the electronic device.

[0025] In some embodiments, while obtaining the device names of electronic devices accessing the gateway, a collection period for the electronic devices accessing the gateway is also obtained. The collection period can be varied, for example, the device names of electronic devices accessing the gateway daily, the device names of electronic devices accessing the gateway within a week, or the device names of electronic devices accessing the gateway within a month. There is no restriction on the collection period and it can be set arbitrarily according to specific needs.

[0026] Step 102 , determining whether the device name satisfies the naming rules; if so, executing step 103 ; otherwise, returning to step 102 , continuing to detect whether the device name of the next electronic device satisfies the naming rules.

[0027] In some embodiments, the device name includes a source identifier and a model identifier. Further, in some embodiments, the source identifier is the name of the manufacturer that produced the device.

[0028] In some embodiments, the naming rule may be determined through steps 301 to 302 in the following embodiments.

[0029] In some embodiments, after determining the naming rule for the target device, the device name of the electronic device can be compared with the naming rule to determine whether the device name of the electronic device matches the naming rule. If the match is successful, step 103 is executed to determine that the electronic device is the target device, and subsequent steps are continued for the target device. If the match is unsuccessful, it is determined that the electronic device is not the target device, and the process returns to step 102, i.e., the device name of the next electronic device is checked to see if it meets the naming rule.

[0030] Step 103, using the electronic device as the target device;

[0031] Step 104 , determining whether the bandwidth supported by the target device matches the managed bandwidth; wherein the managed bandwidth is the bandwidth managed by the user of the terminal device accessing the gateway through the target device.

[0032] In some embodiments, the situation in which the bandwidth supported by the target device is determined to be mismatched with the processing bandwidth may be: whether the bandwidth supported by the target device is greater than or less than the processing bandwidth, the two are determined to be mismatched; or, only when the bandwidth supported by the target device is less than the processing bandwidth, the two are determined to be mismatched, and when the bandwidth supported by the target device is greater than or equal to the processing bandwidth, the two are determined to be matched.

[0033] For example, if it is determined that the bandwidth supported by the target device is 400M, and the bandwidth applied by the user is 500M, then it is considered that the bandwidth supported by the target device is less than the applied bandwidth; if it is determined that the bandwidth supported by the target device is 500M, and the bandwidth applied by the user is 400M, then it is considered that the bandwidth supported by the target device is greater than the applied bandwidth.

[0034] In some embodiments, when the bandwidth supported by the target device is greater than or less than the processed bandwidth, and both are determined to be mismatched, if the bandwidth supported by the target device is less than the processed bandwidth, a first prompt message is sent to the terminal device, and the first prompt message is used to remind the user of the terminal device to replace the target device; if the bandwidth supported by the target device is greater than the processed bandwidth, a second prompt message is sent to the terminal device, and the second prompt message is used to remind the user of the terminal device to upgrade the processed bandwidth.

[0035] In some embodiments, the target device is a router device.

[0036] It is understandable that if the MAC address of the electronic device is determined to be the same as the MAC address of the target device to determine whether it is the target device, there will be the following problems: on the one hand, each target device corresponds to a MAC address, and the MAC address field is long and irregular. Therefore, both the matching process and the process of establishing a contact table based on the MAC address and the name of the target device in advance are difficult; on the other hand, the chips used by some target devices are purchased from other manufacturers, which makes it difficult to trace the MAC addresses of such target devices, and therefore it is also difficult to obtain the MAC address information corresponding to each target device.

[0037] Different target devices may correspond to the same device name. Therefore, the device name of the target device is enumerable, and for the target device, it is relatively easy to obtain its corresponding device name and store it. Obviously, compared with obtaining the MAC address of the target device, the total number of target device device names is significantly smaller than the total number of target device MAC addresses, and the coverage of the target device device name is much larger than the coverage of the target device MAC address. In this way, determining the naming rule library based on the device name of the target device in advance is simpler, has a wider coverage, and has a stronger recognition ability than determining the MAC address library based on the MAC address of the target device in advance.

[0038] Therefore, in the embodiment of the present application, the device name of the electronic device connected to the gateway is obtained, and then the electronic device whose device name meets the naming rules is determined to be the target device. Compared with matching the MAC address of the electronic device with a pre-established MAC address library, this identification method can improve the target device identification capability and identification range, and further improve the ability to identify whether the network bandwidth used by the user matches the speed of the target device used.

[0039] Figure 2 A schematic diagram of the implementation flow of the bandwidth detection method provided in the embodiment of the present application is shown as follows: Figure 2 As shown, the method may include the following steps 201 to 206:

[0040] Step 201: Obtain the device name of the electronic device connected to the gateway;

[0041] Step 202, determining whether the device name satisfies the naming rules; if so, executing step 203; otherwise, returning to step 202, continuing to determine whether the device name of the next electronic device satisfies the naming rules;

[0042] Step 203: Determine that the electronic device is a target device.

[0043] After determining the target device, the bandwidth supported by the target device needs to be compared with the bandwidth applied for by the user of the terminal device that accesses the gateway through the target device to determine whether the bandwidth supported by the target device matches the bandwidth applied for by the user. In some embodiments, determining the bandwidth supported by the target device based on the device name of the target device can be achieved by executing the following steps 204 to 205.

[0044] Step 204 : According to the device name of the target device, obtain the frequency band supported by the target device and the transmission rate corresponding to the frequency band from the first mapping table.

[0045] In some embodiments, the first mapping table includes hardware parameter information corresponding to the target device, wherein the hardware parameter information includes at least one of the following: a device name of the target device, frequency band information corresponding to the device name, and a transmission rate corresponding to the frequency band information.

[0046] Furthermore, in some embodiments, the frequency band information includes single-frequency information supported by the target device and / or dual-frequency information supported by the target device.

[0047] In some embodiments, the first mapping table corresponding to the target device may be obtained by pre-acquiring and storing hardware parameter information corresponding to a device identical to the current target device.

[0048] Step 205: Determine the bandwidth supported by the target device based on the frequency band supported by the target device and the transmission rate corresponding to the frequency band.

[0049] Step 206: Determine whether the bandwidth supported by the target device matches the processing bandwidth.

[0050] In some embodiments, the method for determining the bandwidth can be: determining the user information of the target device and the broadband account opened by the user according to the user information table; and obtaining the bandwidth handled by the user from the second mapping table according to the broadband account opened by the user.

[0051] It is understandable that an operator generally stores a user information table internally, and the user information table includes broadband accounts corresponding to existing gateways within the operator.

[0052] In some embodiments, the second mapping table includes parameters such as the broadband account activated by the user and the bandwidth corresponding to the broadband account. After obtaining the broadband account activated by the user from the user information table, the bandwidth activated by the user can be obtained from the second mapping table. Then, the hardware parameter information (i.e., supported bandwidth) of the target device used by the user is compared with the bandwidth activated by the user to determine whether the bandwidth supported by the target device matches the activated bandwidth.

[0053] In some embodiments, the naming rule may be determined through the following steps 301 to 302:

[0054] Step 301: Acquire a first sample set; wherein the first sample set includes a device name of at least one target device.

[0055] In some embodiments, step 301 is implemented by executing steps 3011 to 3015 as follows:

[0056] Step 3011: Collect device names of multiple electronic devices connected to the gateway during a historical period to obtain a second sample set.

[0057] In some embodiments, the device names of electronic devices connected to the gateway in the past year or the past two years may be collected. There is no restriction on the collection period and it can be freely set according to specific needs.

[0058] Furthermore, in some embodiments, after collecting the device names of multiple electronic devices within a historical period, these device names can be sorted by their frequency of occurrence, and the device names of electronic devices with a frequency of occurrence greater than a threshold can be extracted to obtain a second sample set. This can reduce the amount of data in the second sample set and ensure that the device names of the electronic devices in the second sample set are those that deserve special attention.

[0059] In some embodiments, the device name consists of a source identification and a model identification.

[0060] After obtaining the second sample set, the following steps 3012 to 3015 may be executed to select the device name belonging to the target device from the second sample set to obtain the first sample set.

[0061] Step 3012: Select the device name belonging to the target device from the second sample set according to the reference source identifier to obtain a third sample set.

[0062] In some embodiments, the reference source identifier is a source identifier corresponding to a target device that is commonly used by users on the market. After obtaining the reference source identifier, the device names of electronic devices in the second sample set whose source identifiers are identical to the reference source identifier are selected and used as the device names of the target devices, thereby obtaining a third sample set.

[0063] Step 3013: extract the model identifier from the device name of the third sample set.

[0064] It is understandable that the reference source identifier is generally the source identifier corresponding to the target device that is used more frequently by users, and its coverage is not comprehensive, which may lead to the situation in the second sample set that some electronic devices are actually target devices, but the source identifier in their device name is different from the reference source identifier.

[0065] In some embodiments, to avoid missed identification, the model identifier in the device name of the selected target device can also be extracted for further identification. This is because, in actual applications, there may be a situation where the model identifier of a certain type of electronic device is the same as the model identifier of the target device, while the source identifier of the electronic device of this type is different from the source identifier of the target device, but the electronic device of this type is also a target device.

[0066] Step 3014: Determine the device name of the target device from the remaining sample sets according to the model identifier to obtain a fourth sample set; wherein the remaining sample set includes the remaining device names in the second sample set except the device names of the third sample set.

[0067] After extracting the model identifiers from the device names in the third sample set, the model identifiers in the device names of the remaining electronic devices in the second sample set that are not identified as target devices (i.e., the remaining device names in the second sample set excluding the device names of the third sample set) are matched with the model identifiers of the target devices in the third sample set. If a match occurs, the device name of the electronic device in the remaining sample set is determined to be different from the device name of the target device in the third sample set (i.e., the model identifiers are the same, but the source identifiers are different), thereby obtaining a fourth sample set.

[0068] Step 3015: Aggregate the third sample set and the fourth sample set into a first sample set.

[0069] In some embodiments, step 301 may also be implemented as follows: searching for a device name of a target device corresponding to a source identifier on a platform to which at least one source identifier belongs, obtaining device names of target devices belonging to different source identifiers, and aggregating these device names into a first sample set.

[0070] It should be noted that the platforms on which the source identifier belongs vary. For example, it can be the official website of the manufacturer that produces the target device with the source identifier, or it can be an e-commerce platform that stores the device name of the target device with the source identifier. There is no limitation on the platform from which the source identifier is obtained; it is sufficient to know that the device names of multiple target devices can be obtained from these platforms.

[0071] Step 302 : According to the source identifiers recorded in the device names in the first sample set, the device names belonging to the same source identifier are analyzed to obtain corresponding naming rules.

[0072] In some embodiments, after obtaining the naming rules corresponding to the device names belonging to different source identifiers, these naming rules can be summarized into a naming rule table. Obviously, the naming rule table contains at least one naming rule. In this way, when determining whether the device name of the electronic device connected to the gateway meets the naming rules in step 101, the device name of the electronic device can be matched one by one with the naming rules in the naming rule table. If a match is found, the electronic device is determined to be the target device.

[0073] Of course, in some embodiments, after obtaining the naming rules corresponding to the device names belonging to different source identifiers, these naming rules can also be connected using an OR relationship to obtain a longer naming rule. In this way, when determining whether the device name of the electronic device connected to the gateway meets the naming rule in step 101, the device name of the electronic device can be input into the longer naming rule, and the output result can be used to determine whether the electronic device is the target device.

[0074] In an embodiment of the present application, a first sample set is obtained, and then the device names belonging to the same source identifier are analyzed according to the source identifier recorded in the device name in the first sample set to obtain a corresponding naming rule. This method of determining whether the electronic device connected to the gateway is the target device according to the naming rule has a smaller traversal range than comparing the device name of the electronic device connected to the gateway with the device names of all target devices available on the market one by one, and can make the target device identification faster.

[0075] With the development of network technology, the frequency of people's use of terminals in daily life has further increased. Correspondingly, the requirements for network quality are increasing, and operators are receiving more and more network quality complaints. A closer look at the reasons behind the complaints, excluding the problems of network quality itself, there are also many reasons due to the mismatch between the network broadband subscribed by the user and the router speed used by the user, that is, the router used by the user is not sufficient to support the network broadband speed subscribed by the user. Therefore, how can operators accurately identify the detailed information of the router used by broadband users to match the user's broadband application situation, remind and urge users with mismatched speeds to replace appropriate routers to resolve or avoid such complaints in advance? This is an urgent problem currently faced by operators. In related technologies, the MAC information of the device collected by the intelligent gateway is usually first used, and a router device information database (which stores detailed information tables such as router MAC and manufacturer model technical parameters) is maintained to identify the detailed information of the router used by the user through MAC matching. The speed-related hardware parameters of the router are then compared with the bandwidth of the broadband service subscribed to identify users with mismatched speeds.

[0076] In related technologies, router MAC addresses and manufacturer models are manually collected to form a router device information database. This is then matched with the MAC information of downstream devices collected and reported by smart gateways to identify the detailed information of the routers used by users. However, this technical approach has a serious problem: maintaining a database that consistently matches router MAC addresses with detailed information such as manufacturer models is extremely difficult. There are several reasons for this: On the one hand, if data is collected from router manufacturers, due to the large number of router brands, it is extremely difficult to collect router MAC and other detailed information from all brands. In addition, some router brands use chips purchased from other manufacturers, making it difficult to trace router MAC information. On the other hand, if data is collected from public online channels, there are problems such as unknown data accuracy and limited data sources, resulting in low coverage of identifiable routers. Given that the device information collected and reported by smart gateways includes a device name field, the router's device name is usually a combination of the router's manufacturer and model information by default, and the default naming rules for routers from the same manufacturer are basically the same.

[0077] Based on this, the following describes an exemplary application of the embodiment of the present application in a practical application scenario.

[0078] In an embodiment of the present application, a method, device and system for identifying users whose broadband and router speeds do not match are proposed. The method does not rely on MAC address information. Instead, the method uses an intelligent gateway to collect and report device name information, designs corresponding regular expressions for precise matching, extracts router manufacturer and model information, and then completes other information parameters of the router by matching the manufacturer model with the hardware parameter information library, thereby obtaining comprehensive user router-related information.

[0079] The present invention provides a method, device and system for automatically identifying router information. Figure 4 As shown, the specific steps are as follows: 401 to 406:

[0080] Step 401: Clean the online and offline log information of the gateway-attached devices (i.e., electronic devices) collected and reported by the smart gateway every day. Since the connection between the router and the gateway is wired, the online and offline logs of devices with wireless connection and the logs with empty device name fields are filtered. The main collection is the gateway MAC address of the day, the device name of the attached device, and the collection time field, and input them into the device name regular expression (i.e., naming rule) recognition module.

[0081] Step 402, device name regular expression recognition module: uses regular expressions to recognize the device name field of the collected downstream devices. It includes the following steps a to e:

[0082] In step a, in order to understand the device name naming rules of the router, the gateway downstream device logs collected in step 401 within a relatively long period of time (i.e., historical period) (usually within the past one or two years) are summarized according to the device name to obtain the device name appearance frequency ranking. In the ranking, the device names whose total appearance frequency exceeds a certain threshold (according to the actual coverage requirement, for example, 1000 times) are taken as analysis samples (i.e., the second sample set) to summarize the regular expressions extracted from the device names of each manufacturer.

[0083] In step b, according to data observation, the default name of a router device is generally composed of the manufacturer and model according to certain rules (for example, H3C_Magic_R100, TL-WDR5620). Most of them contain the manufacturer name (i.e., source identifier), so rules can be extracted starting from the manufacturer name.

[0084] In step c, through basic online knowledge of router manufacturers, the Chinese pinyin and English names of current mainstream router manufacturers are identified (i.e., reference source identifiers) (including more than 20 brands such as TP-LINK, Mercury Communications, Tenda, Xunjie, Xiaomi, etc.), and the analysis samples obtained in step a are manually checked and compared to determine the correspondence between the identifiable device names and router manufacturers (for example, devices starting with "H3C_" are all manufactured by H3C) (i.e., a third sample set is obtained).

[0085] In step d, for each manufacturer, the device names that have appeared are summarized and analyzed, the regular expressions of the router device names of each manufacturer are summarized, and the model information (i.e., model identification) of the routers of each manufacturer is extracted.

[0086] In step e, based on the model obtained in step d, the device names whose manufacturer information was not identified in step c (i.e., the remaining sample set) are compared again. If there is a device name containing router model information, the device model is extracted and supplemented with the corresponding manufacturer information (i.e., the fourth sample set).

[0087] Through the above steps, the router device name identification rules of each manufacturer are formed and solidified into regular expressions, which are used to identify the router manufacturer and model of the devices connected to the gateway.

[0088] In step 403, the regular expression generated in step 402 is used to identify routers that meet the extraction criteria. These routers are then stored or updated in the smart gateway's currently connected router vendor and model table. This table primarily includes four fields: smart gateway MAC address, router model, router vendor, and update time. Since most home broadband networks use a single router, by default, each smart gateway MAC address corresponds to one router.

[0089] In step 404, statistics are collected from the manufacturer and model table of the routers currently connected to the smart gateway to obtain all currently identified router models. Data is then retrieved from the corresponding official website or e-commerce platform through manual online search or crawling to obtain router hardware parameter information (i.e., the first mapping table). This is stored in the database to obtain a detailed table of router hardware parameters, which includes fields such as router manufacturer, model, wired rate (i.e., the transmission rate corresponding to the frequency band), wireless rate, and single and dual band (i.e., the frequency bands supported by the target device).

[0090] Step 405: The smart gateway user information table is a table of user information related to broadband accounts activated by existing gateways within the operator. By associating the manufacturer and model table of the router currently connected to the smart gateway with the smart gateway user information table and the router hardware parameter detailed information table, detailed information on the router currently used by each broadband account can be obtained.

[0091] In step 406, the user broadband package information table is an existing broadband service table within the operator, storing detailed service parameters such as the user and bandwidth for each broadband account. Generally, a province has a fixed number of broadband package bandwidth options, with no more than 10. The bandwidth and router matching module, based on expert experience, compiles a set of router hardware parameter rules for different bandwidths. Using this set of rules, it identifies broadband users whose bandwidth and router speed do not match, outputs the results, and generates the final result.

[0092] In this embodiment, based on the hardware device name field collected by the gateway, the router device name rules of different router manufacturers are analyzed to summarize and extract regular expressions, thereby identifying the router manufacturer and model information in the hardware device. Then, after identifying the user's router device attributes, based on the user's broadband package, expert experience is used to sort out a set of router hardware parameter rules suitable for different bandwidths. This rule-based matching is used to identify users whose routers are insufficient to support their broadband speeds.

[0093] The embodiment of the present application uses device name data collected by the intelligent gateway to match routers of mainstream manufacturers and models on the market by refining regular expressions. Compared with the method of building a dictionary matching based on the device MAC, which is usually used in related technologies to identify the specific manufacturer and model of smart hardware devices in the network, it does not require the difficult-to-obtain relationship table provided by the manufacturer and the public MAC-device pairing relationship of the network with uncertain quality. At the same time, it has stronger recognition capabilities for routers of some non-chip manufacturers whose MAC information is difficult to accurately grasp.

[0094] The embodiment of the present application identifies the router model and device of the user in the operator network through gateway data, then matches the user's broadband service data, compares and formulates broadband and router rate mismatch rules to identify the corresponding users, so that business operators can provide corresponding operation promotion activities.

[0095] By adopting the method in the embodiment of the present application, in the actual test of the online and offline log data of the smart gateway, nearly 3 million router devices and corresponding device parameter attributes were identified. Based on the identified router parameters and user broadband package data, nearly 140,000 broadband and speed mismatch user groups were matched, which were used by relevant departments to promote related special operation activities.

[0096] Based on the aforementioned embodiments, an embodiment of the present application provides a bandwidth detection device, which includes the modules included and the units included in each module, and can be implemented by a processor; of course, it can also be implemented by a specific logic circuit; during implementation, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA), etc.

[0097] Figure 5 This is a schematic diagram of the structure of the bandwidth detection device according to an embodiment of the present application. Figure 5 As shown, the device 500 includes an acquisition module 501 and a determination module 502, wherein: the acquisition module 501 is used to obtain the device name of the electronic device accessing the gateway; the determination module 502 is used to determine whether the device name meets the naming rules; if so, the electronic device is used as the target device; the determination module 502 is also used to determine whether the bandwidth supported by the target device matches the processed bandwidth; wherein the processed bandwidth is the bandwidth processed by the user of the terminal device accessing the gateway through the target device.

[0098] In some embodiments, the determination module 502 is further configured to determine the bandwidth supported by the target device according to the device name of the target device; and determine whether the bandwidth supported by the target device matches the processing bandwidth.

[0099] In some embodiments, the acquisition module 501 is used to obtain the frequency band supported by the target device and the transmission rate corresponding to the frequency band from the first mapping table according to the device name of the target device; the determination module 502 is used to determine the bandwidth supported by the target device according to the frequency band supported by the target device and the transmission rate corresponding to the frequency band.

[0100] In some embodiments, the apparatus 500 further includes an analysis module, an acquisition module 501, for acquiring a first sample set, wherein the first sample set includes the device name of at least one target device; and an analysis module for analyzing device names belonging to the same source identifier according to the source identifier recorded in the device name in the first sample set to obtain a corresponding naming rule.

[0101] In some embodiments, the device 500 further includes a collection module and a selection module. The collection module is used to collect the device names of multiple electronic devices connected to the gateway during a historical period to obtain a second sample set; the selection module is used to select the device name belonging to the target device from the second sample set to obtain a first sample set.

[0102] In some embodiments, the apparatus 500 further includes an extraction module and a aggregation module, wherein the selection module is configured to select, based on a reference source identifier, a device name belonging to a target device from the second sample set to obtain a third sample set; the extraction module is configured to extract a model identifier from the device name in the third sample set; the determination module 502 is configured to determine, based on the model identifier, the device name of the target device from the remaining sample set to obtain a fourth sample set; the remaining sample set includes the remaining device names in the second sample set excluding the device names in the third sample set; and the aggregation module is configured to aggregate the third sample set and the fourth sample set into the first sample set.

[0103] In some embodiments, the device 500 also includes a reminder module, which is used to send a first reminder message to the terminal device if the bandwidth supported by the target device does not match the processing bandwidth, if the bandwidth supported by the target device is less than the processing bandwidth; wherein the first reminder message is used to remind the user of the terminal device to replace the target device; and if the bandwidth supported by the target device is greater than the processing bandwidth, send a second reminder message to the terminal device; wherein the second reminder message is used to remind the user of the terminal device to upgrade the processed bandwidth.

[0104] The description of the above device embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of this application, please refer to the description of the method embodiment of this application for understanding.

[0105] It should be noted that in the embodiments of this application Figure 5The module division of the bandwidth detection device shown is schematic and represents only one logical functional division. Actual implementations may employ different division methods. Furthermore, the functional units in the various embodiments of this application may be integrated into a single processing unit, physically exist separately, or two or more units may be integrated into a single unit. These integrated units may be implemented in hardware or software functional units. Alternatively, they may be implemented using a combination of software and hardware.

[0106] It should be noted that, in the embodiment of the present application, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling an electronic device to execute all or part of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific combination of hardware and software.

[0107] An embodiment of the present application provides an electronic device, Figure 6 This is a schematic diagram of the hardware entity of the electronic device according to the embodiment of the present application, such as Figure 6 As shown, the electronic device 600 includes a memory 601 and a processor 602. The memory 601 stores a computer program that can be run on the processor 602. When the processor 602 executes the program, the steps in the method provided in the above embodiment are implemented.

[0108] It should be noted that the memory 601 is configured to store instructions and applications executable by the processor 602, and can also cache data to be processed or processed by the processor 602 and various modules in the electronic device 600 (for example, image data, audio data, voice communication data and video communication data), which can be implemented through flash memory (FLASH) or random access memory (Random Access Memory, RAM).

[0109] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method provided in the above embodiment are implemented.

[0110] An embodiment of the present application provides a computer program product containing instructions, which, when executed on a computer, enables the computer to execute the steps of the method provided in the above method embodiment.

[0111] It should be noted that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium, storage medium, and device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

[0112] It should be understood that "one embodiment" or "an embodiment" or "some embodiments" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments. The above description of the various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other. For the sake of brevity, they will not be repeated here.

[0113] The term "and / or" in this article is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, object A and / or object B can mean: object A exists alone, object A and object B exist at the same time, and object B exists alone.

[0114] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0115] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of the modules is merely a logical function division. In actual implementation, there may be other division methods, such as: multiple modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or modules can be electrical, mechanical or other forms.

[0116] The modules described above as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules; they may be located in one place or distributed across multiple network units; some or all of the modules may be selected according to actual needs to achieve the purpose of this embodiment.

[0117] In addition, all functional modules in the embodiments of the present application can be integrated into one processing unit, or each module can be a separate unit, or two or more modules can be integrated into one unit; the above-mentioned integrated modules can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0118] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, and other media that can store program codes.

[0119] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling an electronic device to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks or optical disks.

[0120] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0121] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0122] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0123] The above is merely an embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A bandwidth detection method, characterized in that: The method comprises: Obtain the device name of the electronic device connected to the gateway; determining whether the device name satisfies a naming rule; if so, taking the electronic device as a target device; According to the device name of the target device, obtaining the frequency band supported by the target device and the transmission rate corresponding to the frequency band from a first mapping table; the first mapping table at least includes hardware parameter information corresponding to the target device; Determining a bandwidth supported by the target device based on a frequency band supported by the target device and a transmission rate corresponding to the frequency band; Determine whether the bandwidth supported by the target device matches the processed bandwidth; wherein the processed bandwidth is the bandwidth processed by the user of the terminal device accessing the gateway through the target device.

2. The method according to claim 1, characterized in that The process of determining the naming rule includes: Acquire a first sample set; the first sample set includes a device name of at least one target device; According to the source identifiers recorded in the device names in the first sample set, the device names belonging to the same source identifier are analyzed to obtain corresponding naming rules.

3. The method according to claim 2, characterized in that The obtaining of the first sample set includes: Collecting device names of multiple electronic devices connected to the gateway within a historical period to obtain a second sample set; A device name belonging to the target device is selected from the second sample set to obtain a first sample set.

4. The method according to claim 3, characterized in that The selecting a device name belonging to the target device from the second sample set to obtain a first sample set includes: Selecting a device name belonging to the target device from the second sample set according to the reference source identifier to obtain a third sample set; extracting a model identifier from the device name of the third sample set; determining, according to the model identifier, a device name of the target device from the remaining sample sets to obtain a fourth sample set; the remaining sample set includes the remaining device names in the second sample set excluding the device names in the third sample set; The third sample set and the fourth sample set are aggregated into the first sample set.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: In the case where the bandwidth supported by the target device does not match the processed bandwidth, if the bandwidth supported by the target device is less than the processed bandwidth, sending a first prompt message to the terminal device; wherein the first prompt message is used to remind the user of the terminal device to replace the target device; If the bandwidth supported by the target device is greater than the processed bandwidth, a second prompt message is sent to the terminal device; wherein the second prompt message is used to remind the user of the terminal device to upgrade the processed bandwidth.

6. A bandwidth detection device, characterized in that: include: An acquisition module, used to acquire the device name of the electronic device connected to the gateway; further configured to obtain, according to the device name of the target device, a frequency band supported by the target device and a transmission rate corresponding to the frequency band from a first mapping table; the first mapping table at least including hardware parameter information corresponding to the target device; A determination module, configured to determine whether the device name satisfies a naming rule; If yes, taking the electronic device as the target device; The determination module is further configured to determine the bandwidth supported by the target device based on the frequency band supported by the target device and the transmission rate corresponding to the frequency band; Determine whether the bandwidth supported by the target device matches the processed bandwidth; wherein the processed bandwidth is the bandwidth processed by the user of the terminal device accessing the gateway through the target device.

7. An electronic device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images