Roaming method based on fttr, fttr gateway and program product

Abstract

This application discloses a roaming method, FTTR gateway, and application product based on FTTR, belonging to the field of communication technology. The method includes: in response to a terminal roaming from a first fiber-to-room FTTR gateway to at least one second FTTR gateway within a target time period, acquiring roaming data of the terminal within the target time period; determining the network scenario of the first FTTR gateway and each of the second FTTR gateways based on the terminal's roaming data within the target time period; and in response to the existence of at least one network scenario being a coverage-limited scenario, updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario. This method can meet the roaming requirements of coverage-limited scenarios, avoid terminal roaming failures or timeouts, and improve user experience.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a roaming method, FTTR gateway, and software product based on FTTR. Background Technology

[0002] Fiber to the Room (FTTR) whole-house fiber optic networking is a wireless network composed of multiple wireless access points (APs). User terminals can move freely within the coverage area and connect to the nearest wireless access point at any time. However, related roaming technologies primarily rely on fixed roaming strategies for guidance and triggering. This makes it difficult to meet the roaming needs of various coverage-limited scenarios, such as obstacle obstruction or roaming from edge APs, leading to terminal roaming failures or timeouts and impacting user experience. Summary of the Invention

[0003] This application provides a roaming method, FTTR gateway, and program product based on FTTR, to at least solve the problem that related roaming technologies are unable to meet the roaming needs of various coverage-limited scenarios.

[0004] To solve the above-mentioned technical problems, this application is implemented as follows: In a first aspect, embodiments of this application provide a roaming method based on FTTR, comprising: in response to a terminal roaming from a first fiber-to-room FTTR gateway to at least one second FTTR gateway within a target time period, acquiring roaming data of the terminal within the target time period; determining the networking scenario of the first FTTR gateway and each of the second FTTR gateways based on the roaming data of the terminal within the target time period; and in response to the existence of at least one networking scenario being a coverage-limited scenario, updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario.

[0005] Secondly, embodiments of this application provide an FTTR gateway, the FTTR gateway including a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the method described in the first aspect above.

[0006] Thirdly, embodiments of this application provide a computer-readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect above.

[0007] Fourthly, embodiments of this application provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the steps of the method described in the first aspect above.

[0008] In this embodiment, in response to a terminal roaming from a first fiber-to-the-room FTTR gateway to at least one second FTTR gateway within a target time period, roaming data of the terminal within the target time period is obtained. Based on the terminal's roaming data within the target time period, the networking scenario of the first FTTR gateway and each second FTTR gateway is determined. In response to the existence of at least one networking scenario being a coverage-limited scenario, the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario are updated based on the roaming policy corresponding to the coverage-limited scenario. Thus, when a terminal roams from the first FTTR gateway to at least one second FTTR gateway, the networking scenario of the first FTTR gateway and each second FTTR gateway is determined based on the terminal's roaming data, and the roaming control parameters of the corresponding second FTTR gateway are updated for coverage-limited scenarios. This can meet the roaming requirements of coverage-limited scenarios, avoid terminal roaming failures or timeouts, and improve user experience.

[0009] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0010] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0011] Figure 1 This application provides schematic diagrams illustrating terminal roaming in FTTR all-optical networking according to some embodiments. Figure 2 The flowchart of a roaming method based on FTTR provided in some embodiments of this application is shown; Figure 3 This application provides a schematic diagram illustrating the interaction between MFU, SFU, and STA according to some embodiments. Figure 4 The illustration shows a terminal roaming scenario in an obstacle-prone environment, as provided in some embodiments of this application. Figure 5 A flowchart illustrating a method for determining networking scenarios provided in some embodiments of this application is shown; Figure 6 This paper illustrates the signal strength of the STA between AP1 and AP2 in an obstacle-free scenario according to some embodiments of this application. Figure 7This application provides schematic diagrams illustrating the signal strength of the STA between AP1 and AP2 in obstacle-prone scenarios according to some embodiments of the present application. Figure 8 This illustration shows a terminal roaming scenario where the SFU3 provided in some embodiments of this application is a roaming edge access gateway; Figure 9 A flowchart illustrating a method for determining networking scenarios provided in other embodiments of this application is shown; Figure 10 This paper shows a schematic diagram of the FTTR network structure provided in an embodiment of this application; Figure 11 A schematic diagram of the hardware structure of the FTTR gateway provided in an embodiment of this application is shown. Detailed Implementation

[0012] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0013] In existing roaming technologies, roaming is primarily based on fixed roaming strategies for guidance and triggering, which struggles to meet the roaming needs of various coverage-limited scenarios, such as those with obstructed access or APs at the roaming edge. For example, in obstructed scenarios, wireless signals attenuate rapidly, making timely signal measurement impossible and resulting in delayed roaming guidance triggering, hindering timely handover. Furthermore, the limited number of target APs available for handover at the roaming edge can easily lead to repeated triggering of the roaming measurement process. These issues ultimately cause terminal roaming failures or timeouts, impacting user experience.

[0014] To address the aforementioned problems in the roaming process, this application provides a roaming method based on FTTR. When a terminal roams from a first FTTR gateway to at least one second FTTR gateway, the method determines the networking scenario of the first FTTR gateway and each second FTTR gateway based on the terminal's roaming data. For scenarios with limited coverage, the method updates the roaming control parameters of the corresponding second FTTR gateway to meet the roaming requirements of scenarios with limited coverage, avoid terminal roaming failure or timeout, and improve user experience.

[0015] Please see Figure 1 , Figure 1 This document illustrates terminal roaming diagrams for FTTR all-optical networking provided in some embodiments of this application. For example... Figure 1As shown, the all-optical FTTR network includes a main FTTR unit (MFU) 110 and several sub-FTTR units (SFUs) 120. This all-optical FTTR network contains at least two MFUs or SFUs with WiFi capabilities. The main FTTR unit can be a WiFi-enabled MFU, and the sub-FTTR units can be WiFi-enabled SFUs. The MFUs and SFUs in the network have basic management communication channels, such as an EasyMesh networking channel, a Wi-Fi Management and Control Interface (WMCI) channel, or a Control and Provisioning of Wireless Access Points Protocol (CapWap) channel. The terminal 130 can move freely within the coverage area of ​​this network and connect to the corresponding MFU or SFU at any time.

[0016] Figure 2 The diagram illustrates a flowchart of an FTTR-based roaming method provided in some embodiments of this application. This method can be executed by an FTTR gateway; exemplary, this method can be applied to the above-described... Figure 1 The MFU device or any SFU device in the system. For example... Figure 2 As shown, the method 200 may include the following steps: Step 210: In response to the terminal roaming from the first fiber to room FTTR gateway to at least one second FTTR gateway within the target time period, obtain the roaming data of the terminal within the target time period.

[0017] In one exemplary embodiment, such as Figure 3 As shown, the MFU can pre-configure network information, including but not limited to network topology information and WiFi-related configuration information. For example, the configuration can be set as: SFU_i: (WiFix / x band / x power / ...)(SFU_j: -xdbm), meaning that from FTTR device i, using WiFi x radio frequency mode, binding to the specified x band and x power, this device detects a wireless signal strength of -xdbm from FTTR device j.

[0018] The SFU passively or periodically reports the terminal status information of the associated station (STA). For example, the terminal status information of the terminal STA_i includes: information of the currently associated SFU or MFU, frequency band, current signal strength, etc.

[0019] After a STA associates with a SFU, the SFU reports its own information, frequency band, and current signal strength of the STA to the MFU. Alternatively, a STA can directly associate with an MFU, which then obtains its own information, frequency band, and current signal strength. The SFU autonomously guides the STA's roaming according to common scenarios. After multiple roaming trips by the STA within a target time period, the MFU obtains the roaming data of the terminal within that time period.

[0020] For example, the SFU currently associated with the STA monitors the STA's signal strength. When the signal drops to a preset roaming threshold, the SFU reports its own information and the STA's information to the MFU. The MFU acquires its own and all SFUs' signal data, determines the optimal roaming target gateway, and generates a roaming command. The MFU sends a "disconnect guidance" command to the STA's currently associated gateway and a "prepare for access" command to the target gateway, thereby guiding the STA to roam from its currently associated gateway to the target gateway. The MFU can acquire all roaming data of the terminal within the target time period, and the SFU currently associated with the STA can obtain the roaming data corresponding to the STA's current roaming event through the MFU.

[0021] For example, the MFU currently associated with the STA monitors the STA's signal strength. When the signal drops to a preset roaming threshold, the MFU acquires its own and all SFUs' signal data, determines the optimal roaming target gateway, and generates a roaming command. The MFU disconnects the boot process and simultaneously sends an "access ready" command to the target gateway, thereby guiding the STA to roam from the MFU to the target gateway. The MFU currently associated with the STA can obtain the roaming data corresponding to this roaming event for that STA.

[0022] Step 220: Based on the roaming data of the terminal within the target time period, determine the networking scenario of the first FTTR gateway and each of the second FTTR gateways.

[0023] Continuing with the above embodiments, the MFU or SFU identifies the networking scenario based on the roaming data of the terminal within the target time period through AI learning or a preset scene recognition strategy, thereby obtaining the networking scenario of the first FTTR gateway and each of the second FTTR gateways.

[0024] Step 230: In response to the existence of at least one network scenario being a coverage-limited scenario, update the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario.

[0025] Continuing with the above embodiments, it is determined whether there is a coverage-limited scenario in the networking scenario of the first FTTR gateway and each of the second FTTR gateways. The coverage-limited scenario refers to a scenario in which the wireless signal coverage is limited by environmental factors, equipment deployment, etc., resulting in a decrease in signal quality and insufficient coverage. For example, the coverage-limited scenario includes obstacle obstruction scenario, corner scenario, FTTR gateway as a roaming edge access gateway, etc.

[0026] The aforementioned coverage-limited scenarios are prone to roaming failures or timeouts. This application addresses this issue by updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming strategy for that scenario. For example, if there are obstacles such as walls or furniture between the first and second FTTR gateways, the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario are updated to trigger roaming in advance. If the first FTTR gateway is a roaming edge access gateway, the limited number of second FTTR gateways are configured as the destination gateway to avoid triggering repeated roaming measurements and improve roaming handover efficiency.

[0027] In specific applications, such as Figure 3 As shown, the MFU can distribute the identified networking scenario to the SFU, which then guides the STA to roam based on the networking scenario.

[0028] In this embodiment of the application, when a terminal roams from a first FTTR gateway to at least one second FTTR gateway, the networking scenario of the first FTTR gateway and each second FTTR gateway is determined based on the roaming data of the terminal. For coverage-limited scenarios, the roaming control parameters of the corresponding second FTTR gateway are updated, which can meet the roaming requirements of coverage-limited scenarios, avoid terminal roaming failure or timeout, and improve user experience.

[0029] In some embodiments, step 220 above, determining the networking scenario of the first FTTR gateway and each of the second FTTR gateways based on the roaming data of the terminal within the target time period, includes: Step 220-1: Based on the roaming data of the terminal within the target time period, determine the terminal status information corresponding to the roaming events of the terminal from the first FTTR gateway to each second FTTR gateway.

[0030] For example, terminal status information includes Received Signal Strength Indicator (RSSI), negotiation rate, traffic changes, and service lag information.

[0031] Step 220-2: Based on the terminal status information corresponding to the roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways, determine the networking scenario of the first FTTR gateway and each of the second FTTR gateways.

[0032] In an exemplary embodiment, when the terminal status information includes the negotiation rate, the negotiation rate jump amplitude can be calculated and compared with a preset threshold to determine whether there is an obstacle between the first FTTR gateway and the second FTTR gateway, i.e. whether the networking scenario is an obstacle occlusion scenario.

[0033] In another exemplary embodiment, when the terminal status information includes traffic changes, the magnitude of the traffic jump can be calculated and compared with a preset threshold to determine whether there is an obstacle between the first FTTR gateway and the second FTTR gateway, i.e. whether the networking scenario is an obstacle occlusion scenario.

[0034] In another exemplary embodiment, when the terminal status information includes service lag information, the number of service lags within a certain period of time can be counted, and the number of service lags can be compared with a preset threshold to determine whether there is an obstacle between the first FTTR gateway and the second FTTR gateway, i.e. whether the networking scenario is an obstacle occlusion scenario.

[0035] Using the above methods, the terminal's status information during roaming can be accurately obtained. Based on the terminal status information, various networking scenarios such as normal scenarios, obstacle-obstructed scenarios, and external signal interference can be accurately identified, providing data support for subsequent adjustments to roaming control parameters.

[0036] In some embodiments, the coverage-limited scenario described above includes an obstacle scenario, where there is an obstacle between the first FTTR gateway and the second FTTR gateway; in step 220-1 above, determining the networking scenario of the first FTTR gateway and each of the second FTTR gateways based on the terminal status information corresponding to the roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways includes: For each second FTTR gateway, an obstacle determination index is determined based on the terminal status information corresponding to the roaming event of the terminal from the first FTTR gateway to the second FTTR gateway. The obstacle determination index is used to indicate the degree of change in terminal signal quality between the first FTTR gateway and the second FTTR gateway. In response to the obstacle determination index being greater than the obstacle determination threshold, the networking scenario of the first FTTR gateway and the second FTTR gateway is determined to be an obstacle scenario.

[0037] In one exemplary embodiment, for each second FTTR gateway, an obstacle determination index is determined based on the terminal state information corresponding to the roaming event of the terminal from the first FTTR gateway to the second FTTR gateway. The obstacle determination index quantifies the degree of signal quality jump between the first FTTR gateway and the second FTTR gateway. The greater the degree of signal quality jump during roaming, the more obvious the signal is affected by obstruction, and the higher the obstacle determination index.

[0038] When the obstacle detection index is greater than the obstacle detection threshold, the networking scenario of the first FTTR gateway and the second FTTR gateway is an obstacle scenario; when the obstacle detection index is less than or equal to the obstacle detection threshold, the networking scenario of the first FTTR gateway and the second FTTR gateway is a normal scenario.

[0039] In this embodiment of the application, the degree of change in terminal signal quality between the first FTTR gateway and the second FTTR gateway is quantified by the obstacle determination index. By comparing the obstacle determination index with the obstacle determination threshold, obstacle scenarios in the networking scenario can be quickly identified.

[0040] In some embodiments, the terminal status information mentioned above includes received signal strength information; in step 220-1 above, determining the obstacle determination index based on the terminal status information corresponding to the roaming event of the terminal from the first FTTR gateway to the second FTTR gateway includes: Based on the received signal strength information corresponding to the roaming events of the terminal from the first FTTR gateway to the second FTTR gateway within the target time period, the average signal jump amplitude of the terminal roaming from the first FTTR gateway to the second FTTR gateway is determined; based on the average signal jump amplitude of the roaming events of the terminal from the first FTTR gateway to the second FTTR gateway within the target time period, the obstacle detection index is determined.

[0041] In an exemplary embodiment, the received signal strength information corresponding to the roaming event of the terminal from the first FTTR gateway AP1 to the second FTTR gateway AP2 within the target time period is obtained: RSSI(T_i, AP1), RSSI(T_i+1, AP1), ..., RSSI(T_i+(m-1), AP2). For example, when the terminal triggers a roaming event, received signal strength information can be collected before and after the trigger time of the roaming event, thereby obtaining the received signal strength information during the terminal's roaming switch from AP1 to AP2. The number of sampling points and the sampling interval for the received signal strength information before and after the trigger time of the roaming event can be set according to actual conditions and are not specifically limited here.

[0042] The average signal hop amplitude of the terminal roaming from the first FTTR gateway AP1 to the second FTTR gateway AP2 is calculated based on the received signal strength information, as shown in the following formula.

[0043] Average signal transition amplitude = |(RSSI(T_i, AP1) + RSSI(T_i+1, AP1) + ... + RSSI(T_i+(m-1), AP2))| / m Where m is the number of samples.

[0044] The average signal jump amplitude of multiple roaming events from the first FTTR gateway to the second FTTR gateway within the target time period is determined as the obstacle detection index, as shown in the following formula.

[0045] Obstacle detection index = ∑n(average signal jump amplitude) / n Where n is the number of roaming events of the terminal from the first FTTR gateway to the second FTTR gateway within the target time period.

[0046] In this embodiment of the application, the obstacle determination index is determined based on the average signal jump amplitude of the roaming events of the terminal from the first FTTR gateway to the second FTTR gateway within the target time period. The obstacle determination index can improve the reliability of obstacle determination.

[0047] In some embodiments, the method for determining the obstacle detection threshold described above includes: The obstacle detection threshold is determined based on the theoretical signal strength information between the first FTTR gateway and the second FTTR gateway. This theoretical signal strength information is the signal strength information calculated based on the distance between the first FTTR gateway and the second FTTR gateway, the transmission power, and the path loss model, assuming there are no obstacles between them.

[0048] In an exemplary embodiment, when there are no obstacles between the first FTTR gateway AP1 and the second FTTR gateway AP2, theoretical signal strength information RSSI(AP1, AP2) is calculated using a model of distance between AP1 and AP2, transmit power, and path loss. An obstacle determination threshold is then determined based on the theoretical signal strength information RSSI(AP1, AP2), for example, by multiplying the theoretical signal strength information by a preset signal attenuation coefficient.

[0049] In this embodiment of the application, the obstacle determination threshold is determined based on the theoretical signal strength information between the first FTTR gateway and the second FTTR gateway, which can improve the accuracy of obstacle scene recognition.

[0050] In some embodiments, determining the obstacle detection threshold based on the theoretical signal strength information between the first FTTR gateway and the second FTTR gateway includes: The theoretical signal strength information and the preset signal attenuation coefficient are multiplied to obtain the attenuation correction signal strength; the sum of the attenuation correction signal strength and the preset obstacle determination threshold offset is determined as the obstacle determination threshold.

[0051] In an exemplary embodiment, the theoretical signal strength information RSSI(AP1, AP2) and the preset signal attenuation coefficient α are multiplied to obtain the attenuation correction signal strength; the sum of the attenuation correction signal strength and the preset obstacle determination threshold offset β is determined as the obstacle determination threshold.

[0052] It is understood that the obstacle scene determination condition in the embodiments of this application is: obstacle determination index > α × RSSI(AP1, AP2) + β.

[0053] In practical applications, the value ranges and related explanations of the above parameters are shown in Table 1 below.

[0054] Table 1. Value ranges and related explanations for each parameter.

[0055] In this embodiment, the spatial loss of the signal during propagation can be corrected by the signal attenuation coefficient. Combined with the obstacle determination threshold offset, an obstacle determination threshold that is adapted to the current signal propagation scenario can be generated. Based on this obstacle determination threshold, the obstacle scenario in the network scenario can be accurately identified.

[0056] In some embodiments, step 220 above, determining the networking scenario of the first FTTR gateway and each of the second FTTR gateways based on the roaming data of the terminal within the target time period, includes: Step 220-3: Based on the roaming data of the terminal within the target time period, determine the roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways.

[0057] In an exemplary embodiment, since the roaming edge access gateway is located at the coverage edge of the network and the number of its target APs is limited, in order to avoid triggering repeated roaming measurements, this embodiment of the application counts roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways based on the roaming data of the terminal within the target time period.

[0058] Step 220-4: Based on the number of roaming events from the terminal from the first FTTR gateway to each of the second FTTR gateways, determine the networking scenario of the first FTTR gateway and each of the second FTTR gateways.

[0059] Continuing with the above embodiments, the networking scenario of the first FTTR gateway and each of the second FTTR gateways is determined based on the number of roaming events from the terminal to each of the second FTTR gateways. For example, when the proportion of roaming events to all roaming events is greater than a preset threshold, the first FTTR gateway is determined to be a roaming edge access gateway.

[0060] The above methods can effectively identify roaming edge access gateways, providing data support for subsequent adjustments to roaming strategies.

[0061] In some embodiments, the coverage-limited scenarios described above include the first FTTR gateway being a roaming edge access gateway; in step 220-4 above, determining the networking scenario of the first FTTR gateway and each of the second FTTR gateways based on the number of roaming events from the terminal from the first FTTR gateway to each of the second FTTR gateways includes: For each second FTTR gateway, a roaming transfer probability is determined based on the number of roaming events corresponding to the second FTTR gateway. This roaming transfer probability is used to indicate the possibility of a terminal roaming from the first FTTR gateway to the second FTTR gateway. In response to a roaming transfer probability greater than a transfer probability threshold, the first FTTR gateway is determined to be a roaming edge access gateway.

[0062] In one exemplary embodiment, for each second FTTR gateway, the more roaming events it corresponds to, the greater the roaming transfer probability. When there is a roaming transfer probability among the roaming transfer probabilities corresponding to each second FTTR gateway that is greater than the transfer probability threshold, the first FTTR gateway is determined to be a roaming edge access gateway.

[0063] In this embodiment, the roaming transfer probability is determined by counting the number of roaming events corresponding to each second FTTR gateway. Based on this roaming transfer probability, the roaming edge access gateway in the network can be quickly identified, and the coverage-limited area can be accurately located, which is conducive to optimizing roaming scheduling in the coverage-limited area and improving the user experience.

[0064] In some embodiments, after determining the first FTTR gateway as a roaming edge access gateway as described above, the method further includes: Configure the second FTTR gateway as the destination gateway of the first FTTR gateway. This destination gateway is the gateway for the terminal to perform roaming handover.

[0065] In this embodiment of the application, by configuring the second FTTR gateway with a roaming transfer probability greater than the transfer probability threshold as the destination gateway of the first FTTR gateway, the terminal can be directly guided to roam to the destination gateway when the terminal triggers a roaming event, avoiding repeated roaming measurements and improving roaming guidance efficiency.

[0066] In some embodiments, in step 220-4 above, determining the roaming transfer probability based on the number of roaming events corresponding to the second FTTR gateway includes: The ratio of the number of roaming events corresponding to the second FTTR gateway to the total number of roaming events in the roaming data is determined as the roaming transition probability.

[0067] In one exemplary embodiment, the roaming transfer probability can be calculated using the following formula: P(AP_i → AP_j) = Count(AP_i → AP_j) / Total_Roam_From_AP_i Where P(AP_i → AP_j) is the roaming transition probability of the terminal roaming from AP_i to AP_j, Count(AP_i→ AP_j) is the number of roaming events of the terminal from AP_i to AP_j, Total_Roam_From_AP_i is the total number of roaming events corresponding to AP_i, and j ∈ {all possible roaming target AP}.

[0068] When the roaming transfer probability is greater than the transfer probability threshold P_threshold, the first FTTR gateway is determined to be the roaming edge access gateway. It can be understood that the determination condition for the roaming edge access gateway is: max(P(AP_i → AP_j))>P_threshold.

[0069] In practical applications, the value ranges and related explanations of the above parameters are shown in Table 2 below.

[0070] Table 2 shows the value range and related explanations for each parameter.

[0071] In this embodiment of the application, by determining the ratio of the number of roaming events corresponding to the second FTTR gateway to the total number of roaming events as the roaming transfer probability, the frequency of terminal switching to the corresponding gateway can be accurately quantified, which is beneficial for quickly locating the roaming edge access gateway in the network.

[0072] In some embodiments, step 230 above, updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario, includes: Step 230-1: Send the scene information of the coverage-limited scene and the corresponding gateway information of the second FTTR gateway to the first FTTR gateway, so as to instruct the first FTTR gateway to update the roaming control parameters of the corresponding second FTTR gateway based on the roaming policy corresponding to the coverage-limited scene.

[0073] In an exemplary embodiment, the MFU can pre-configure network scenario information, which includes a first field and a second field. The first field indicates a coverage-limited scenario, and the second field indicates the gateway information of the peer in the network scenario. This network scenario information is then sent to the SFU. For example, if an obstacle exists between the first FTTR gateway and the second FTTR gateway, the MFU sends the scenario information of the coverage-limited scenario (i.e., the obstacle scenario) and the corresponding gateway information of the second FTTR gateway to the first FTTR gateway using the network scenario information. Based on the roaming policy corresponding to the obstacle scenario, the first FTTR gateway updates the roaming control parameters of the second FTTR gateway corresponding to the obstacle scenario, which are maintained in the first FTTR gateway.

[0074] In this embodiment, the roaming control parameters of the first FTTR gateway can be adaptively adjusted according to the scenario information of the coverage-limited scenario to avoid terminal roaming failure or timeout and improve user experience.

[0075] In some possible implementations, after updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy described above, the following additional steps are included: Step 230-2: Send the scene information of the coverage-limited scene and the corresponding gateway information of the first FTTR gateway to the second FTTR gateway, so as to instruct the second FTTR gateway to update the roaming control parameters of the corresponding first FTTR gateway based on the roaming policy corresponding to the coverage-limited scene.

[0076] In another exemplary embodiment, if there is an obstacle between the first FTTR gateway and the second FTTR gateway, the MFU can also send the scene information of the coverage-limited scene (i.e. the obstacle scene) and the corresponding gateway information of the first FTTR gateway to the second FTTR gateway through the network scene information. The second FTTR gateway updates the roaming control parameters of the first FTTR gateway corresponding to the obstacle scene maintained in the second FTTR gateway based on the roaming policy corresponding to the obstacle scene.

[0077] In this embodiment, the roaming control parameters of the second FTTR gateway can also be adaptively adjusted according to the scenario information of the coverage-limited scenario to avoid terminal roaming failure or timeout and improve user experience.

[0078] In some embodiments, the roaming control parameters described above include a roaming threshold, which triggers the terminal to roam from the first FTTR gateway to the second FTTR gateway when a first condition is met. The first condition includes at least one of the following: (1) The first FTTR gateway detected that the signal strength of the terminal decreased to the roaming threshold.

[0079] (2) The second FTTR gateway detected that the signal strength of the terminal reached the roaming threshold.

[0080] In one exemplary embodiment, the MFU can update the roaming threshold of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario. When the first FTTR gateway detects that the terminal's signal strength has decreased to the roaming threshold, and / or the second FTTR gateway detects that the terminal's signal strength has reached the roaming threshold, the terminal is triggered to roam from the first FTTR gateway to the second FTTR gateway.

[0081] In this embodiment, based on the roaming policy corresponding to the coverage-limited scenario, the roaming threshold of the second FTTR gateway corresponding to the coverage-limited scenario is updated. The timing of roaming triggering can be adjusted according to the coverage-limited scenario to avoid terminal roaming failure or timeout.

[0082] In some embodiments, step 230 above, updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario, includes: Based on the coverage-limited scenario, determine the roaming trigger adjustment value; based on the roaming trigger adjustment value and the initial roaming threshold of the second FTTR gateway, determine the target roaming threshold corresponding to the coverage-limited scenario; update the roaming threshold of the second FTTR gateway corresponding to the coverage-limited scenario to the target roaming threshold.

[0083] In some embodiments, the MFU can determine a roaming trigger adjustment value based on coverage-limited scenarios. This roaming trigger adjustment value can be configured according to actual needs, and the selection of the roaming trigger adjustment value is not limited here. Based on the roaming trigger adjustment value and the initial roaming threshold of the second FTTR gateway, a target roaming threshold corresponding to the coverage-limited scenario is determined. For example, the roaming trigger adjustment value for an obstacle scenario is configured to 10 dB, the initial roaming threshold of the second FTTR gateway is RSSI_roam_threshold = -70 dB, and the target roaming threshold for the coverage-limited scenario is RSSI_roam_threshold += 10 dB, i.e., the target roaming threshold is -60 dB. The roaming threshold of the second FTTR gateway corresponding to the coverage-limited scenario is updated to the target roaming threshold. It can be understood that in an obstacle scenario, when the first FTTR gateway detects that the terminal's signal strength has decreased to -60 dB, and / or the second FTTR gateway detects that the terminal's signal strength has reached -60 dB, the terminal is triggered to roam from the first FTTR gateway to the second FTTR gateway, thereby achieving early triggering of roaming guidance.

[0084] In this embodiment, the roaming threshold of the second FTTR gateway in a coverage-limited scenario is adaptively adjusted by the roaming trigger adjustment value to adapt to the roaming requirements of the coverage-limited scenario, avoid terminal roaming failure or timeout, and improve user experience.

[0085] In some embodiments, after updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario in step 230 above, the method further includes: Step 240: In response to the existence of multiple second FTTR gateways, determine the comprehensive evaluation value of each second FTTR gateway based on the terminal's signal quality evaluation value and / or the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario.

[0086] In an exemplary embodiment, when multiple second FTTR gateways exist, if the networking scenario of the first FTTR gateway and each of the second FTTR gateways is a normal scenario, the comprehensive evaluation value of the second FTTR gateway is determined based on the terminal's signal quality evaluation value (Signal_Score). If the networking scenario of the first FTTR gateway and each of the second FTTR gateways is a coverage-limited scenario, the comprehensive evaluation value of each second FTTR gateway is determined based on the terminal's signal quality evaluation value (Signal_Score) and the scene adaptation evaluation value (Scene_Score) of the second FTTR gateway corresponding to the coverage-limited scenario. For example, the roaming decision adopts a multi-factor weighted scoring mechanism, comprehensively considering multiple dimensions such as signal quality and networking scenario, and its formula is shown below.

[0087] Total_Score = w1 × Signal_Score + w2 × Scene_Score + ... Among them, Signal_Score is the signal quality evaluation value, which can range from 0 to 100; Scene_Score is the scene adaptation evaluation value, which can range from 0 to 100; w1 and w2 are the weight coefficients of each item, and their sum is 1.0.

[0088] Step 250: Select the target gateway from multiple second FTTR gateways based on the comprehensive evaluation value of each second FTTR gateway.

[0089] Continuing with the above embodiments, the second FTTR gateway with the highest comprehensive evaluation value among the comprehensive evaluation values ​​of each second FTTR gateway is selected as the target gateway.

[0090] Step 260: In response to the terminal's received signal strength information decreasing to the roaming control parameters corresponding to the target gateway, the terminal is guided to roam to the target gateway.

[0091] Continuing with the above embodiments, when the received signal strength of the terminal decreases to the roaming control parameters corresponding to the target gateway, the terminal is guided to roam to the target gateway.

[0092] In some embodiments, in response to a coverage-limited scenario being an obstacle scenario, the method for determining the scenario adaptation evaluation value of the second FTTR gateway corresponding to the aforementioned coverage-limited scenario includes: Based on the signal hopping amplitude of the terminal from the first FTTR gateway to the second FTTR gateway, determine the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario.

[0093] In an exemplary embodiment, when the coverage-limited scenario is an obstacle scenario, the MFU can determine the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario based on the signal hop amplitude of the terminal roaming from the first FTTR gateway to the second FTTR gateway. For example, the scenario adaptation evaluation value in the obstacle scenario is determined in the following manner: Scene_Score_obstacle = 100 - Signal_Jump_Penalty Signal_Jump_Penalty = (ΔRSSI_actual / ΔRSSI_expected) × 50 Among them, Scene_Score_obstacle is the scene adaptation evaluation value in the obstacle scene, Signal_Jump_Penalty is the signal jump amplitude, ΔRSSI_actual is the actual signal jump amplitude, and ΔRSSI_expected is the theoretical signal jump amplitude, which is determined based on the distance and power between the first FTTR gateway and the second FTTR gateway.

[0094] In this embodiment, the scene adaptation evaluation value is determined based on the signal transition amplitude, which can adaptively adapt to various types of obstacle scenes and provide reliable data support for the optimization of roaming control parameters.

[0095] In some embodiments, in response to the coverage-limited scenario where the first FTTR gateway is a roaming edge access gateway, the method for determining the scenario adaptation evaluation value of the second FTTR gateway corresponding to the aforementioned coverage-limited scenario includes: Based on the roaming transfer probability of the terminal roaming from the first FTTR gateway to the second FTTR gateway, determine the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario.

[0096] In an exemplary embodiment, when the coverage-limited scenario is where the first FTTR gateway is a roaming edge access gateway, the MFU can determine the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming transfer probability of the terminal roaming from the first FTTR gateway to the second FTTR gateway. For example, the scenario adaptation evaluation value in the scenario where the first FTTR gateway is a roaming edge access gateway is determined in the following manner: Scene_Score_edge_ap = Transition_Probability × 100 Where Scene_Score_edge_ap is the scene adaptation evaluation value in the scenario where the first FTTR gateway is a roaming edge access gateway, and Transition_Probability is the roaming transition probability.

[0097] In some possible implementations, if the second FTTR gateway is the primary target AP, Scene_Score += 20; if the second FTTR gateway is the backup target AP, Scene_Score += 10.

[0098] In one exemplary embodiment, such as Figure 4 As shown, suppose there is an obstacle between the first FTTR gateway SFU1 and the second FTTR gateway SFU2.

[0099] The MFU pre-configures network information, including but not limited to network topology information and WiFi-related configuration information. For example, the configuration for SFU_1 includes: (WiFi 6 / 2 bands / 100% power / ...) (SFU_2: -70dBm, MFU: -70dBm), and the configuration for SFU_2 includes: (WiFi 7 / 2 bands / 100% power / ...) (SFU_1: -70dBm, MFU: -70dBm). Each SFU passively or periodically reports the STA's status information. For example, the STA status information reported by SFU_1 includes: STA_1, T_1, SFU1, 5G, current signal strength -45dBm (this can be understood as: at time T_1, terminal STA_1, associated with SFU1's 5GHz WiFi band, currently has a signal strength of -45dBm). The fields of the STA status information are shown in Table 3 below: Table 3 Fields in STA Status Information

[0100] When a roaming event occurs, each SFU autonomously guides the STA roaming process according to the general scenario mode. For example, STA_1, T_i, SFU1, 5G, current signal strength -50dBm; STA_1, T_i+1, SFU1, 5G, current signal strength -70dBm; STA_1, T_i+2, SFU2, 5G, current signal strength -30dBm (roaming occurred)...

[0101] Based on the roaming data of STAs within the target time period, MFU determines the networking scenario between AP1 and each AP2, such as... Figure 5 As shown, it includes the following steps: Step 510: Based on the roaming data of the STA within the target time period, determine and obtain the terminal status information corresponding to the roaming events of the STA from AP1 to each AP2.

[0102] Step 520: Based on the received signal strength information corresponding to the roaming events of the terminal from AP1 to AP2 within the target time period, determine the average signal hopping amplitude ΔRSSI of the terminal roaming from AP1 to AP2.

[0103] Step 530: Determine the obstacle detection index (obstacle detection index calculation) based on the average signal jump amplitude ΔRSSI of the roaming events of the terminal from AP1 to AP2 within the target time period.

[0104] Step 540: Determine the obstacle detection threshold based on the theoretical signal strength information between AP1 and AP2.

[0105] Step 550: Determine whether the obstacle detection index is greater than the obstacle detection threshold.

[0106] Step 560: If the obstacle determination index is greater than the obstacle determination threshold, the networking scenario of AP1 and AP2 is determined to be an obstacle scenario.

[0107] Step 570: If the obstacle determination index is less than or equal to the obstacle determination threshold, the networking scenario of AP1 and AP2 is determined to be a normal scenario.

[0108] Step 580: Output the network scene recognition results.

[0109] For example, if in this network scenario, the theoretical signal strength RSSI(AP1, AP2) from AP1 to AP2 is 85, the attenuation coefficient α is 1.3, and the obstacle determination threshold offset β is 15, then the obstacle determination condition is 1.3 × 85 + 15 = 125.

[0110] (1) such as Figure 6 As shown, in an obstacle-free scenario, the STA experiences a smooth jump in signal strength between AP1 and AP2: During the first roaming, RSSI was sampled 5 times: RSSI(T_1, AP1)=-50, RSSI(T_2, AP1)=-55, RSSI(T_3, AP1)=-60, RSSI(T_4, AP1)=-65, RSSI(T_5, AP1)=-70, RSSI(T_1, AP2)=-70, RSSI(T_2, AP2)=-65, RSSI(T_3, AP2)=-60, RSSI(T_4, AP2)=-55, RSSI(T_5, AP2)=-50, and the average signal transition amplitude F1=120.

[0111] The second roaming sampled RSSI 5 times: RSSI(T_1, AP1)=-50, RSSI(T_2, AP1)=-56, RSSI(T_3, AP1)=-61, RSSI(T_4, AP1)=-66, RSSI(T_5, AP1)=-70, RSSI(T_1, AP2)=-70, RSSI(T_2, AP2)=-66, RSSI(T_3, AP2)=-60, RSSI(T_4, AP2)=-56, RSSI(T_5, AP2)=-50, with an average signal transition amplitude F2=121.

[0112] F3=122, F4=119, F5=117, F6=121, F7=120, F8=122, F9=123... The tenth roaming session sampled RSSI 5 times: RSSI(T_1, AP1)=-50, RSSI(T_2, AP1)=-55, RSSI(T_3, AP1)=-60, RSSI(T_4, AP1)=-64, RSSI(T_5, AP1)=-68, RSSI(T_1, AP2)=-67, RSSI(T_2, AP2)=-64, RSSI(T_3, AP2)=-59, RSSI(T_4, AP2)=-54, RSSI(T_5, AP2)=-50, with an average signal transition amplitude F10=118.

[0113] Obstacle detection index = (120+121+......+118) / 10 = 120<125, indicating a scene without obstacles.

[0114] (2) For example Figure 7 As shown, in a scenario with obstacles, the signal strength drops sharply when the STA passes through the obstacle between AP1 and AP2: During the first roaming, RSSI was sampled 5 times: RSSI(T_1, AP1)=-50, RSSI(T_2, AP1)=-55, RSSI(T_3, AP1)=-70, RSSI(T_4, AP1)=-75, RSSI(T_5, AP1)=-80, RSSI(T_1, AP2)=-80, RSSI(T_2, AP2)=-75, RSSI(T_3, AP2)=-60, RSSI(T_4, AP2)=-55, RSSI(T_5, AP2)=-50, and the average signal transition amplitude F1=130.

[0115] F2=131, F3=132, F4=129, F5=127, F6=131, F7=130, F8=132, F9=133, F10=128... Obstacle detection index = (130+131+......+128) / 10 = 130>125, therefore the scene is considered an obstacle scene.

[0116] The MFU sends network scenario information to SFU1 and / or SFU2, as shown in Table 4 below.

[0117] Table 4. One of the typical information encapsulation scenarios in networking.

[0118] Each SFU adjusts the decision coefficient of the corresponding AP based on the location of the obstacle to perform roaming management.

[0119] (1) Roaming threshold adjustment On SFU1: Adjust the decision threshold of SFU2 by one level, for example, from -70dBm to -60dBm, so that STA can enter roaming state earlier.

[0120] On SFU2: Adjust the decision threshold of SFU1 by one level, for example, from -70 to -60, so that STA can enter the roaming state earlier.

[0121] (2) Making roaming decisions The STA is associated with SFU1. The signal quality evaluation value from the STA to SFU2 and SFU3 is 70. The weight of the signal quality evaluation value is w1=0.5, and the weight of the scene adaptation evaluation value is w2=0.5. There is an obstacle between SFU1 and SFU2. The scene adaptation evaluation value for the obstacle scene is 100-(130 / 85)×50=24. The overall evaluation value for SFU2 is 0.5×70+0.5×24=47. There is no obstacle between SFU1 and SFU3. The total score for SFU2 and SFU3 is 1×70=70. SFU1 will decide that the STA will roam to SFU3.

[0122] (3) Send roaming guidance SFU1 uses 11v messages to send SFU3 as the destination gateway to the STA, guiding the STA to associate with SFU3.

[0123] In another exemplary embodiment, such as Figure 8 As shown, the MFU pre-configures network information, including but not limited to network topology information and WiFi-related configuration information. For example, The configuration for SFU_1 includes: (WiFi5 / 2 bands / 100% power / ...) (SFU_2: -70dBm, MFU: -70dBm). The configuration for SFU_2 includes: (WiFi6 / 2 bands / 100% power / ...) (SFU_1: -70dBm, SFU3: -70dBm). The configuration for SFU_3 includes: (WiFi7 / 2 bands / 100% power / ...) (SFU_2: -70dBm, MFU: -90dBm).

[0124] When a roaming event occurs, each SFU autonomously guides the STA roaming process according to the general scenario mode. For example, STA_1, T_i, SFU3, 5G, current signal strength -50dBm; STA_1, T_i+1, SFU2, 5G, current signal strength -50dBm (roaming occurred)...

[0125] Based on the roaming data of the STA within the target time period, the MFU determines the networking scenario between the first FTTR gateway and each of the second FTTR gateways, such as... Figure 9 As shown, it includes the following steps: Step 910: Based on the roaming data of the terminal within the target time period, determine the roaming events of the terminal from SFU3 to SFU1 and SFU2.

[0126] Step 920, optionally, can also check the validity of the roaming data obtained above.

[0127] Step 930: Determine whether the total number of roaming events is greater than or equal to the minimum number of roaming events.

[0128] Step 940: If the total number of roaming events is less than the minimum number of roaming events, then there is insufficient data, and the network scenario will not be determined at this time.

[0129] Step 950: If the total number of roaming events is greater than or equal to the minimum number of roaming events, calculate the roaming transition probability of SFU1 and SFU2.

[0130] Step 960: Determine whether the roaming transfer probability is greater than the transfer probability threshold.

[0131] Step 970: If the roaming transfer probability is not greater than the transfer probability threshold, then SFU3 is not a roaming edge access gateway.

[0132] Step 980: If the roaming transfer probability is greater than the transfer probability threshold, then SFU3 is a roaming edge access gateway.

[0133] Step 990: Output the network scenario recognition results.

[0134] For example, the transfer probability threshold is set to 90%, and the maximum number of destination gateways is 1. Assuming that there are 20 roaming records on SFU3 within 72 hours, and 19 STAs roam to SFU2, the transfer probability P = 19 / 20 = 95% > 90%, SFU3 can be considered as the roaming edge access gateway.

[0135] The MFU sends network scenario information to the SFU3, as shown in Table 5 below.

[0136] Table 5. Typical Networking Scenarios - Part Two

[0137] SFU3 adjusts its unique roaming destination gateway to SFU2 based on the network scenario information to perform roaming management.

[0138] (1) Making roaming decisions If the STA is associated with SFU3, and the signal quality assessment value from the STA to both SFU1 and SFU2 is 70, with a weight w1 of 0.5 for the signal quality assessment value and a weight w2 of 0.5 for the scene adaptation assessment value, then the overall assessment value for SFU2 is 0.5 × 70 + 0.5 × (95% × 100) = 82.5, and the overall assessment value for SFU1 is 1 × 70 = 70. SFU3 will then decide whether the STA will roam to SFU2. Alternatively, the scoring calculation can be skipped, and the decision to roam to SFU2 can be made directly.

[0139] (2) Send roaming guidance SFU3 uses 11v messages to send SFU2 as the destination gateway to the STA, guiding the STA to associate with SFU2.

[0140] The FTTR-based roaming method described above can be executed by the intelligent roaming engine module in the FTTR network, such as... Figure 10 As shown, the FTTR network has at least one intelligent roaming engine module. This intelligent roaming engine module can be deployed on the MFU or on each SFU, and is used to execute the FTTR-based roaming method provided in the above embodiments.

[0141] Both MFU and SFU include a status monitoring module and a roaming guidance module. The status monitoring module is used to acquire the roaming data of the terminal, and the roaming guidance module is used to guide the terminal to roam to the target gateway based on the roaming decision of the intelligent roaming engine module.

[0142] Figure 11 The diagram illustrates the hardware structure of the FTTR gateway provided in this application embodiment. Referring to the diagram, at the hardware level, the FTTR gateway 1100 includes a processor 1110, and optionally includes an internal bus 1120, a network interface 1130, and a memory. The memory may include RAM 1141, such as high-speed random-access memory (RAM), and may also include non-volatile memory 1142, such as at least one disk storage device. Of course, the FTTR gateway 1100 may also include other hardware required for other services.

[0143] The processor 1110, network interface 1130, and memory can be interconnected via an internal bus 1120. This internal bus 1120 can be an Advanced Microcontroller Bus Architecture (AMIC) bus, a Wishbone bus, an Open Core Protocol (OCP) bus, an Avalon bus, etc. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in this diagram, but this does not imply that there is only one bus or one type of bus.

[0144] The memory stores programs. Specifically, the program may include program code, which includes computer operation instructions. The memory may include main memory 1141 and non-volatile memory 1142, and provides instructions and data to the processor 1110.

[0145] Processor 1110 reads the corresponding computer program from non-volatile memory 1142 into memory and then runs it, forming a device for locating the target user at the logical level. Processor 1110 executes the program stored in memory and specifically performs the following: Figure 2 or Figure 5 or Figure 9 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0146] The above is as stated in this application. Figure 2 or Figure 5 or Figure 9 The methods disclosed in the illustrated embodiments can be applied to or implemented by processor 1110. Processor 1110 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware of processor 1110 or by instructions in software form. The processor 1110 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0147] The FTTR gateway can also execute the methods described in the preceding method embodiments and achieve the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0148] Of course, in addition to the software implementation, the FTTR gateway 1100 of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0149] This application also proposes a computer-readable storage medium that stores one or more programs, which, when executed by an FTTR gateway comprising multiple applications, cause the FTTR gateway to perform... Figure 2 or Figure 5 or Figure 9 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0150] The computer-readable storage medium mentioned above includes read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc.

[0151] Furthermore, embodiments of this application also provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, implement the following process: Figure 2 or Figure 5 or Figure 9 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0152] This application's embodiments can be applied to various FTTR gateway collaboration or interconnection scenarios, including: collaboration and interconnection between mobile phones and laptops / tablets; collaboration and interconnection between mobile terminals and smart TVs / monitors; collaboration and interconnection between mobile phones or tablets and in-vehicle entertainment systems; collaboration and interconnection between mobile terminals and smart conferencing systems, etc. This meets users' diverse needs in smart home, smart office, and smart travel scenarios.

[0153] In summary, the above description is merely a preferred embodiment of this application and does not limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0154] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0155] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0156] It should also be noted that 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 limitation, 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.

[0157] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A roaming method based on FTTR, characterized in that, include: In response to a terminal roaming from a first fiber to a room FTTR gateway to at least one second FTTR gateway within a target time period, the roaming data of the terminal within the target time period is obtained. Based on the roaming data of the terminal within the target time period, the networking scenario of the first FTTR gateway and each second FTTR gateway is determined. In response to the existence of at least one network scenario being a coverage-limited scenario, the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario are updated based on the roaming policy corresponding to the coverage-limited scenario; wherein, the roaming control parameters include a roaming threshold, which triggers the terminal to roam from the first FTTR gateway to the second FTTR gateway when a first condition is met, the first condition including at least one of the following: The first FTTR gateway detected that the terminal's signal strength had decreased to the roaming threshold; The second FTTR gateway detected that the terminal's signal strength reached the roaming threshold.

2. The method according to claim 1, characterized in that, The determination of the networking scenario between the first FTTR gateway and each of the second FTTR gateways based on the roaming data of the terminal within the target time period includes: Based on the roaming data of the terminal within the target time period, determine the terminal status information corresponding to the roaming events of the terminal from the first FTTR gateway to each second FTTR gateway; Based on the terminal status information corresponding to the roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways, the networking scenario of the first FTTR gateway and each of the second FTTR gateways is determined.

3. The method according to claim 2, characterized in that, The coverage-limited scenario includes an obstacle scenario, where an obstacle exists between the first FTTR gateway and the second FTTR gateway; determining the networking scenario of the first FTTR gateway and each of the second FTTR gateways based on the terminal status information corresponding to the roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways includes: For each second FTTR gateway, an obstacle determination index is determined based on the terminal state information corresponding to the roaming event of the terminal from the first FTTR gateway to the second FTTR gateway; the obstacle determination index is used to indicate the degree of jump in terminal signal quality between the first FTTR gateway and the second FTTR gateway. In response to the obstacle determination index being greater than the obstacle determination threshold, the networking scenario of the first FTTR gateway and the second FTTR gateway is determined to be an obstacle scenario.

4. The method according to claim 3, characterized in that, The terminal status information includes received signal strength information; the step of determining the obstacle detection index based on the terminal status information corresponding to the roaming event of the terminal from the first FTTR gateway to the second FTTR gateway includes: Based on the received signal strength information corresponding to the roaming events of the terminal from the first FTTR gateway to the second FTTR gateway within the target time period, the average signal hop amplitude of the terminal roaming from the first FTTR gateway to the second FTTR gateway is determined; The obstacle detection index is determined based on the average signal jump amplitude of the roaming events of the terminal from the first FTTR gateway to the second FTTR gateway during the target time period.

5. The method according to claim 3, characterized in that, The method for determining the obstacle detection threshold includes: The obstacle determination threshold is determined based on the theoretical signal strength information between the first FTTR gateway and the second FTTR gateway; the theoretical signal strength information is the signal strength information calculated based on the distance, transmission power and path loss model between the first FTTR gateway and the second FTTR gateway when there are no obstacles between them.

6. The method according to claim 5, characterized in that, The step of determining the obstacle detection threshold based on the theoretical signal strength information between the first FTTR gateway and the second FTTR gateway includes: The attenuation-corrected signal strength is obtained by multiplying the theoretical signal strength information with the preset signal attenuation coefficient. The sum of the attenuation correction signal strength and the preset obstacle determination threshold offset is determined as the obstacle determination threshold.

7. The method according to claim 1, characterized in that, The step of determining the networking scenario between the first FTTR gateway and each of the second FTTR gateways based on the roaming data of the terminal within the target time period includes: Based on the roaming data of the terminal within the target time period, determine the roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways; Based on the number of roaming events of the terminal from the first FTTR gateway to each of the second FTTR gateways, the networking scenario of the first FTTR gateway and each of the second FTTR gateways is determined.

8. The method according to claim 7, characterized in that, The coverage-limited scenario includes situations where the first FTTR gateway is a roaming edge access gateway; the scenario of determining the networking of the first FTTR gateway and each second FTTR gateway based on the number of roaming events of the terminal from the first FTTR gateway to each second FTTR gateway includes: For each second FTTR gateway, the roaming transfer probability is determined based on the number of roaming events corresponding to the second FTTR gateway; the roaming transfer probability is used to indicate the possibility that the terminal roams from the first FTTR gateway to the second FTTR gateway. In response to the roaming transfer probability being greater than the transfer probability threshold, the first FTTR gateway is determined to be a roaming edge access gateway.

9. The method according to claim 8, characterized in that, After determining that the first FTTR gateway is a roaming edge access gateway, the method further includes: Configure the second FTTR gateway as the destination gateway of the first FTTR gateway, whereby the destination gateway is the gateway for the terminal to perform roaming switching.

10. The method according to claim 8, characterized in that, The step of determining the roaming transfer probability based on the number of roaming events corresponding to the second FTTR gateway includes: The ratio of the number of roaming events corresponding to the second FTTR gateway to the total number of roaming events in the roaming data is determined as the roaming transition probability.

11. The method according to claim 1, characterized in that, The step of updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario includes: The scene information of the coverage-limited scene and the corresponding gateway information of the second FTTR gateway are sent to the first FTTR gateway to instruct the first FTTR gateway to update the roaming control parameters of the corresponding second FTTR gateway based on the roaming policy corresponding to the coverage-limited scene.

12. The method according to claim 1, characterized in that, After updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario, the method further includes: The scene information of the coverage-limited scene and the corresponding gateway information of the first FTTR gateway are sent to the second FTTR gateway to instruct the second FTTR gateway to update the roaming control parameters of the corresponding first FTTR gateway based on the roaming policy corresponding to the coverage-limited scene.

13. The method according to claim 1, characterized in that, The step of updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario includes: Based on the aforementioned coverage-limited scenarios, determine the roaming trigger adjustment value; Based on the roaming trigger adjustment value and the initial roaming threshold of the second FTTR gateway, the target roaming threshold corresponding to the coverage-limited scenario is determined; Update the roaming threshold of the second FTTR gateway corresponding to the coverage-limited scenario to the target roaming threshold.

14. The method according to claim 1, characterized in that, After updating the roaming control parameters of the second FTTR gateway corresponding to the coverage-limited scenario based on the roaming policy corresponding to the coverage-limited scenario, the method further includes: In response to the existence of multiple second FTTR gateways, the comprehensive evaluation value of each second FTTR gateway is determined based on the signal quality evaluation value of the terminal and / or the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario. Based on the comprehensive evaluation values ​​of each second FTTR gateway, the target gateway is selected from multiple second FTTR gateways; In response to the terminal's received signal strength information decreasing to the roaming control parameters corresponding to the target gateway, the terminal is guided to roam to the target gateway.

15. The method according to claim 14, characterized in that, In response to the coverage-limited scenario being an obstacle scenario, the method for determining the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario includes: Based on the signal hopping amplitude of the terminal roaming from the first FTTR gateway to the second FTTR gateway, the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario is determined.

16. The method according to claim 14, characterized in that, In response to the coverage-limited scenario where the first FTTR gateway is a roaming edge access gateway, the method for determining the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario includes: Based on the roaming transfer probability of the terminal roaming from the first FTTR gateway to the second FTTR gateway, the scenario adaptation evaluation value of the second FTTR gateway corresponding to the coverage-limited scenario is determined.

17. An FTTR gateway, characterized in that, The FTTR gateway includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 16.

18. A computer program product, characterized in that, The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer, cause the computer to perform the steps of the method as described in any one of claims 1 to 16.

Images