BWP switching method, device, equipment and medium

Abstract

The embodiment of the invention provides a BWP switching method and device, equipment and a medium, and belongs to the technical field of communication. The method comprises the following steps: determining a priority switching parameter of each BWP according to one or more operation performance data of each BWP, the priority switching parameter representing the performance of the BWP; and under the condition that the performance represented by the priority switching parameter of the current BWP is lower than the performance represented by the priority switching parameter of the target BWP, switching the RedCap user set in the current BWP to the target BWP, the target BWP being one of the plurality of BWPs. According to the embodiment of the invention, the performance of the RedCap user service can be improved.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a BWP switching method, apparatus, device, and medium. Background Art

[0002] With the continuous evolution of 5G technology, the communication requirements of the Internet of Things (IoT) for low cost, low power consumption, and high efficiency are increasing day by day. To meet the communication requirements of the IoT, RedCap technology has emerged. RedCap technology can meet the requirements of the IoT by reducing the terminal bandwidth, reducing the number of transceiver antennas, reducing the modulation order, etc. Further, to meet the throughput requirements of RedCap terminals, multiple Bandwidth Parts (BWPs) can be configured, and BWPs can be randomly allocated to RedCap users to enable RedCap users to access evenly on each BWP. However, this allocation method will cause some RedCap users to switch to an unsuitable BWP, thereby reducing the performance of RedCap user services. Summary of the Invention

[0003] Embodiments of this application provide a BWP switching method, apparatus, device, and medium, which can improve the performance of RedCap user services.

[0004] In a first aspect, embodiments of this application provide a BWP switching method based on RedCap users, including: determining a priority switching parameter for each BWP according to one or more running performance data of each BWP, where the priority switching parameter characterizes the performance level of the BWP; and in a case where the performance characterized by the priority switching parameter of the current BWP is lower than the performance characterized by the priority switching parameter of a target BWP, switching the RedCap user set on the current BWP to the target BWP, where the target BWP is one of multiple BWPs.

[0005] In some possible implementation manners, determining a priority switching parameter for each BWP according to one or more running performance data of each BWP includes: if the BWP corresponding to the RedCap user is a BWP associated with a non-cell-defined synchronization signal block (NCD-SSB), determining the priority switching parameter for each BWP associated with the NCD-SSB according to multiple running performance data of each BWP associated with the NCD-SSB; if the BWP corresponding to the RedCap user is a BWP associated with a cell-defined synchronization signal block (CD-SSB), determining the priority switching parameter for each BWP associated with the NCD-SSB according to the number of RedCap users of each BWP associated with the NCD-SSB, where the performance characterized by the priority switching parameter has a negative correlation with the number of RedCap users.

[0006] In some possible embodiments, according to various operating performance data of each BWP associated with NCD-SSB, determining the priority handover parameters of each BWP associated with NCD-SSB includes: performing normalization processing on each type of operating performance data; obtaining the extreme values of each type of operating performance data after normalization processing; and obtaining the priority handover parameters of each BWP associated with NCD-SSB according to the operating performance data after normalization processing and the extreme values of each type of operating performance data after normalization processing.

[0007] In some possible embodiments, the extreme values include maximum values and minimum values; obtaining the priority handover parameters of each BWP associated with NCD-SSB according to the operating performance data after normalization processing and the extreme values of each type of operating performance data after normalization processing includes: for each BWP associated with NCD-SSB, calculating a first distance parameter and a second distance parameter according to the operating performance data after normalization processing and the extreme values of the operating performance data, where the first distance parameter represents the distance between the various operating performance data after normalization processing and the maximum value of the operating performance data, and the second distance parameter represents the distance between the various operating performance data after normalization processing and the minimum value of the operating performance data; and obtaining the priority handover parameters according to the first distance parameter and the second distance parameter.

[0008] In some possible embodiments, the priority handover parameter includes the ratio of the first distance parameter to the first sum, or the priority handover parameter includes the ratio of the second distance parameter to the first sum; the first sum is the sum of the first distance parameter and the second distance parameter.

[0009] In some possible embodiments, the operating performance data includes first forward performance data and reverse performance data; performing normalization processing on each type of operating performance data includes: performing forward conversion on the reverse performance data to obtain second forward performance data; and performing normalization processing on the first forward performance data and the second forward performance data to obtain the operating performance data after normalization processing.

[0010] In some possible embodiments, switching a RedCap user set in the current BWP to the target BWP includes: obtaining the service traffic data of the RedCap user set in the current BWP; and among the RedCap users set in the current BWP, switching the RedCap users whose service traffic data meets the traffic performance condition to the target BWP.

[0011] In some possible embodiments, when the BWP corresponding to the RedCap user is the BWP associated with CD-SSB, the target BWP includes the BWP associated with NCD-SSB with the fewest RedCap users.

[0012] In some possible embodiments, the operating performance data includes one or more of the following: the number of RedCap users, the RedCap user level, the RedCap user channel quality indicator (CQI), uplink interference, the perceived speed of RedCap users, the connection rate of RedCap users, service delay, handover delay, network jitter, and communication packet loss rate.

[0013] In a second aspect, an embodiment of the present application provides a BWP switching device, including: a performance determination module, configured to determine, according to one or more operating performance data of each BWP, a priority switching parameter for each BWP, where the priority switching parameter characterizes the performance level of the BWP; a switching module, configured to switch the RedCap users set in the current BWP to the target BWP when the performance characterized by the priority switching parameter of the current BWP is lower than the performance characterized by the priority switching parameter of the target BWP, and the target BWP is one of the multiple BWPs.

[0014] In a third aspect, an embodiment of the present application provides a base station device, including: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the BWP switching method in the first aspect.

[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the BWP switching method in the first aspect is implemented.

[0016] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, the BWP switching method in the first aspect is implemented.

[0017] An embodiment of the present application provides a BWP switching method, device, equipment, and medium. According to one or more operating performance data of each BWP, a priority switching parameter capable of characterizing the comprehensive performance of the BWP is obtained. If the performance characterized by the priority switching parameter of the current BWP is lower than the performance characterized by the priority switching parameter of the target BWP, the RedCap users are switched to the target BWP. The performance of the target BWP is better than that of the current BWP. Switching the RedCap users set in the current BWP to the target BWP can enable the RedCap users to be configured to a BWP with better and more suitable performance, thereby improving the performance of the RedCap user service. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required to be used in the embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

[0019] Figure 1 Schematic diagram of an example of the BWP provided by an embodiment of the present application;

[0020] Figure 2 Flowchart of the BWP switching method provided by an embodiment of the present application;

[0021] Figure 3 Flowchart of the BWP switching method provided by another embodiment of the present application;

[0022] Figure 4 Flowchart of the BWP switching method provided by yet another embodiment of the present application;

[0023] Figure 5 Flowchart of an example of the BWP switching process provided by an embodiment of the present application;

[0024] Figure 6 Schematic structural diagram of the BWP switching device provided by an embodiment of the present application;

[0025] Figure 7 Schematic structural diagram of the base station device provided by an embodiment of the present application. Detailed implementation manners

[0026] The features and exemplary embodiments of various aspects of the present application will be described in detail below. To make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without some of these specific details. The following description of the embodiments is only intended to provide a better understanding of the present application by showing examples of the present application.

[0027] It should be noted that in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, elements defined by the statement "including..." do not exclude the existence of additional identical elements in the process, method, article or device including the said elements.

[0028] With the continuous evolution of 5G technology, the communication requirements of the Internet of Things (IoT) for low cost, low power consumption, and high efficiency are increasing day by day. To meet the communication requirements of the IoT, RedCap technology has emerged. RedCap technology can meet the requirements of the IoT by reducing the terminal bandwidth, reducing the number of transceiver antennas, and reducing the modulation order, etc. The terminal supporting RedCap technology is a RedCap terminal, and the RedCap terminal may include modules, industrial gateways, industrial routers, etc. When the number of RedCap terminals in the network is large or the traffic volume is large, configuring a single Bandwidth Part (BWP) cannot meet the throughput requirements of RedCap terminals. To meet the throughput requirements of RedCap terminals, multiple BWPs can be configured, and the RedCap users are randomly assigned BWPs with reference to the number of RedCap users in the BWPs, so that RedCap users can access evenly on each BWP. However, this allocation method will cause some RedCap users to switch to an unsuitable BWP, thus reducing the performance of RedCap user services.

[0029] For the sake of easy understanding, here, the content of the base station enabling the multi-RedCap function and supporting the multi-BWP function will be briefly described first. The cell accessed by RedCap users has a certain bandwidth, and this bandwidth can be divided into multiple BWPs. For example, Figure 1 This is a schematic diagram of an example of the BWP provided by the embodiment of the present application. As Figure 1 shown, the cell bandwidth is 100 MHz, and the 100 MHz can be divided into five BWPs, namely BWP1-1, BWP1-2, BWP1-3, BWP1-4, and BWP1-5. Among them, BWP1-1 is associated with the Cell Defining Synchronization Signal Block (CD-SSB), and BWP1-2, BWP1-3, BWP1-4, and BWP1-5 are associated with the Non-Cell Defining Synchronization Signal Block (NCD-SSB). After the RedCap user accesses the cell through BWP1-1 associated with the CD-SSB, it will then switch to other BWPs associated with the NCD-SSB, that is, switch to any one of BWP1-2, BWP1-3, BWP1-4, and BWP1-5.

[0030] The present application provides a BWP switching method, apparatus, device, and medium, which can obtain one or more operating performance parameters of a BWP, determine the performance levels of multiple BWPs based on the operating performance parameters, and switch at least some of the RedCap users configured in the BWP with relatively poor performance to the BWP with relatively better performance, so that the RedCap users are configured with a better and more suitable BWP, improving the performance of the RedCap user services.

[0031] The BWP switching method, apparatus, device, medium, and program product provided by the present application will be described separately below.

[0032] The present application provides a BWP switching method, which can be applied to the scenario of configuring corresponding BWPs for RedCap users. This BWP switching method can be executed by a BWP switching apparatus, a base station device, etc. The BWP switching apparatus and the base station device both belong to the base station, and are not limited herein. Figure 2 It is a flowchart of the BWP switching method provided by an embodiment of the present application. As Figure 2 shown, this BWP switching method may include step S101 and step S102.

[0033] In step S101, according to one or more operating performance data of each BWP, determine the priority switching parameter of each BWP.

[0034] To meet the throughput requirements of RedCap users, multiple BWPs are set. The operating performance data of the BWP can be periodically obtained according to the monitoring period to determine the priority switching parameter of each BWP. The monitoring period can be regarded as the period for RedCap users to switch BWPs, and the monitoring period can be set according to scenarios, requirements, experience, etc. For example, the monitoring period can be 15 minutes, 30 minutes, 1 hour, etc., and is not limited herein. The base station can obtain one or more operating performance data of the BWP within the monitoring period, and different types of operating performance data characterize the operating performance of the BWP in different aspects.

[0035] In some examples, the operating performance data may include, but is not limited to, more than one of the following: the number of RedCap users, the RedCap user level, the RedCap user channel quality indicator CQI, the uplink interference, the RedCap user perceived speed, the RedCap user connection rate, the service delay, the handover delay, the network jitter, and the communication packet loss rate. Other operating performance data that can characterize the performance of the BWP is also within the protection scope of the embodiments of the present application.

[0036] The number of RedCap users is the number of RedCap users with data scheduling on the BWP. The larger the number of RedCap users, the fewer available resources of the BWP, the relatively lower the performance of the BWP, and the lower the priority. The smaller the number of RedCap users, the more available resources of the BWP, the relatively higher the performance of the BWP, and the higher the priority. The RedCap users in the embodiments of this application can be regarded as RedCap terminals. During the process of the base station receiving various messages associated with users, the base station can identify whether a user is a RedCap user based on various messages, and distinguish different RedCap users according to the session identifier, device identifier, etc. associated with the RedCap users.

[0037] The RedCap user level can be obtained based on the levels of RedCap users on the BWP measured and reported during the monitoring period. Specifically, the RedCap user level can be implemented as the average level of RedCap users, that is, the RedCap user level can be the average of the levels of RedCap users on the BWP associated with the NCD-SSB measured and reported during the monitoring period. For example, the BWP associated with the NCD-SSB includes BWP1-2, and the number of RedCap users on BWP1-2 is 3, then the RedCap user level on BWP1-2 can be the average of the levels of the 3 RedCap users on BWP1-2. It should be noted that in other examples, the RedCap user level can also be implemented as the maximum value, minimum value or other processed values of the levels of RedCap users, which is not limited here.

[0038] The RedCap user Channel Quality Indicator (CQI) can be obtained based on the CQIs of RedCap users on the BWP measured and reported during the monitoring period. Specifically, the RedCap user CQI can be implemented as the average of the CQIs of RedCap users, that is, the RedCap user CQI can be the average of the CQIs of RedCap users on the BWP measured and reported during the monitoring period. For example, the BWP associated with the NCD-SSB includes BWP1-2, and the number of RedCap users on BWP1-2 is 2, then the RedCap user CQI on BWP1-2 can be the average of the CQIs of the 2 RedCap users on BWP1-2. It should be noted that in other examples, the RedCap user CQI can also be implemented as the maximum value, minimum value or other processed values of the CQIs of RedCap users, which is not limited here.

[0039] The uplink interference can be obtained based on the interference value of resource blocks (RBs) within a BWP. Specifically, the uplink interference can be implemented as the average of the interference values of the RBs within the BWP during the monitoring period. It should be noted that in other examples, the uplink interference can also be implemented as the maximum value, minimum value, or other processed values of the interference value of the RB, which is not limited herein.

[0040] The perceived speed of RedCap users can be obtained based on the data transmission rate of RedCap users. Specifically, the perceived speed of RedCap users can be implemented as the average of the data transmission rates of RedCap users in the BWP measured and reported during the monitoring period. It should be noted that in other examples, the perceived speed of RedCap users can also be implemented as the maximum value, minimum value, or other processed values of the data transmission rate of RedCap users, which is not limited herein.

[0041] The connection success rate of RedCap users can be obtained based on the success rate of successful configuration of RedCap users with the BWP. Specifically, the connection success rate of RedCap users can be implemented as the average of the success rates of successful configuration of RedCap users with the BWP obtained during the monitoring period. It should be noted that in other examples, the connection success rate of RedCap users can also be implemented as the maximum value, minimum value, or other processed values of the success rate of successful configuration of RedCap users with the BWP, which is not limited herein.

[0042] The service delay can be obtained based on the delay when RedCap users execute services. Specifically, the service delay can be implemented as the average of the delays when RedCap users in the BWP associated with NCD-SSB execute services obtained during the monitoring period. It should be noted that in other examples, the service delay can also be implemented as the maximum value, minimum value, or other processed values of the delay when RedCap users in the BWP execute services, which is not limited herein.

[0043] The handover delay can be obtained based on the delay of RedCap users when they hand over the BWP. Specifically, the handover delay can be implemented as the average of the delays when RedCap users hand over to this BWP during the monitoring period. It should be noted that in other examples, the handover delay can also be implemented as the maximum value, minimum value, or other processed values of the delays when RedCap users hand over to this BWP, which is not limited herein.

[0044] The network jitter can be obtained based on the network jitter of the service executed by the BWP configured by the RedCap user. Specifically, the network jitter can be implemented as the average value of the network jitter of the service executed by the BWP configured by the RedCap user within the monitoring period. It should be noted that in other examples, the network jitter can also be implemented as the maximum value, minimum value or other processed values of the network jitter of the service executed by the BWP configured by the RedCap user, which is not limited here.

[0045] The communication packet loss rate can be obtained based on the packet loss rate when the BWP configured by the RedCap user executes the service. Specifically, the communication packet loss rate can be implemented as the average value of the packet loss rate of the service executed by the BWP configured by the RedCap user within the monitoring period. It should be noted that in other examples, the communication packet loss rate can also be implemented as the maximum value, minimum value or other processed values of the packet loss rate of the service executed by the BWP configured by the RedCap user, which is not limited here.

[0046] For each BWP, the performance of the BWP is evaluated according to the operation performance data of the BWP. The performance of the BWP can be evaluated by the priority handover parameter. The priority handover parameter can characterize the performance level of the BWP. In some examples, the magnitude of the priority handover parameter may be positively correlated with the performance level of the BWP, that is, the larger the value of the priority handover parameter, the higher the performance of the BWP. In other examples, the magnitude of the priority handover parameter may be negatively correlated with the performance level of the BWP, that is, the smaller the value of the priority handover parameter, the higher the performance of the BWP.

[0047] In step S102, when the performance characterized by the priority handover parameter of the current BWP is lower than the performance characterized by the priority handover parameter of the target BWP, the RedCap user set on the current BWP is switched to the target BWP.

[0048] The current BWP is any one of multiple BWPs. Multiple BWPs can be polled, and the performance of each of the multiple BWPs is compared, and the BWP handover of RedCap users set in the BWP is performed. The target BWP can be one of the multiple BWPs. Further, the target BWP is the BWP among the multiple BWPs whose performance characterized by the priority handover parameter is higher than the performance of the current BWP characterized by the priority handover parameter. The target BWPs corresponding to different current BWPs can be different or the same, which is not limited here. If the performance of the current BWP characterized by the priority handover parameter is lower than the performance of the target BWP characterized by the priority handover parameter, then the current BWP is a BWP with relatively poor performance, and the service performance of RedCap users set in the current BWP may decrease. In order to improve the service performance of RedCap users, the RedCap users set in the current BWP are switched to the target BWP, and the RedCap users can be switched to a BWP with relatively better performance, thereby improving the service performance of RedCap users.

[0049] In some examples, the target BWP may include the BWP with the highest performance characterized by the priority handover parameter. The BWPs can be sorted according to the performance characterized by the priority handover parameter from high to low, and the BWP ranked first is determined as the target BWP. Switching the RedCap users set in the current BWP to the target BWP with the highest performance can greatly improve the service performance of RedCap users and also improve the user experience. The BWP handover method in the above embodiment can be executed in each monitoring period. After the BWP handover in the current monitoring period is completed, the BWP handover in the next monitoring period is performed.

[0050] In the embodiment of the present application, according to one or more running performance data of each BWP, a priority handover parameter capable of characterizing the comprehensive performance of the BWP is obtained. If the performance of the current BWP characterized by the priority handover parameter is lower than the performance of the target BWP characterized by the priority handover parameter, then the RedCap users are switched to the target BWP. The performance of the target BWP is better than the performance of the current BWP. Switching the RedCap users set in the current BWP to the target BWP can enable the RedCap users to be configured with a BWP with better and more suitable performance, thereby improving the performance of the RedCap user service.

[0051] In some embodiments, the BWP may include the BWP associated with NCD-SSB and the BWP associated with CD-SSB. Figure 3 The flowchart of the BWP handover method provided by another embodiment of the present application Figure 3 is different from Figure 2 in that Figure 2 step S101 in Figure 3Steps S1011 and S1012 therein.

[0052] In step S1011, if the current BWP is the BWP associated with NCD-SSB, determine the priority handover parameters of each BWP associated with NCD-SSB according to various operating performance data of each BWP associated with NCD-SSB.

[0053] When the current BWP is the BWP associated with NCD-SSB, the various operating performance data of the BWP associated with NCD-SSB can be comprehensively considered to determine the priority handover parameters of the BWP associated with NCD-SSB, and the comprehensive performance of the BWP associated with NCD-SSB can be determined through the performance of the BWP associated with NCD-SSB in multiple aspects.

[0054] When the current BWP is the BWP associated with NCD-SSB, the BWP handover of the RedCap user of the current BWP is that the RedCap user switches from one BWP associated with NCD-SSB to another BWP associated with NCD-SSB. That is to say, the embodiments of the present application can achieve the direct handover of the RedCap user between the BWPs associated with NCD-SSB, without the RedCap user first switching from one BWP associated with NCD-SSB to the BWP associated with CD-SSB, and then switching from the BWP associated with CD-SSB to another BWP associated with NCD-SSB. Using the BWP handover method for RedCap users provided by the embodiments of the present application can also improve the BWP handover efficiency of RedCap users.

[0055] In step S1012, if the current BWP is the BWP associated with the cell-defined synchronization signal block CD-SSB, determine the priority handover parameters of each BWP associated with NCD-SSB according to the number of RedCap users of each BWP associated with NCD-SSB.

[0056] The number of RedCap users of the BWP associated with NCD-SSB is the number of RedCap users with data scheduling on the BWP associated with NCD-SSB. The performance characterized by the priority handover parameter may have a negative correlation with the number of RedCap users. The larger the number of RedCap users of the BWP associated with NCD-SSB, the less available resources of the BWP associated with NCD-SSB, the relatively lower performance of the BWP associated with NCD-SSB, and the lower the priority; the smaller the number of RedCap users of the BWP associated with NCD-SSB, the more available resources of the BWP associated with NCD-SSB, the relatively higher performance of the BWP associated with NCD-SSB, and the higher the priority.

[0057] In some examples, when the current BWP is the BWP associated with CD-SSB, the target BWP includes the NCD-SSB-associated BWP with the least number of RedCap users. When a RedCap user initially accesses, the BWP configured for the RedCap user is the BWP associated with CD-SSB. For RedCap users configured in the BWP associated with CD-SSB, they can be sorted according to the number of RedCap users in the NCD-SSB-associated BWP from low to high, and the RedCap users configured in the BWP associated with CD-SSB can be switched to the NCD-SSB-associated BWP with the least number of RedCap users, that is, the target BWP.

[0058] By performing traffic splitting on RedCap users in the BWP associated with CD-SSB and RedCap users in the BWP associated with NCD-SSB, it is possible to avoid BWP congestion caused by RedCap users in the BWP associated with CD-SSB. Moreover, for RedCap users switched from the BWP associated with CD-SSB to the target BWP, in the next monitoring period, they can also be switched according to the switching method of RedCap users between NCD-SSB-associated BWPs, switching the RedCap users to a better NCD-SSB-associated BWP, improving the service performance of RedCap users, and making the BWP switching method of RedCap users more flexible and diverse.

[0059] In some embodiments, when the current BWP is the BWP associated with NCD-SSB, in order to improve the accuracy of the performance of the BWP characterized by the priority switching parameter and reduce the difficulty of calculating the priority switching parameter, unified standardization processing can be performed on various operation performance data, and comprehensive calculation is performed using the standardized operation performance data to obtain the priority switching parameter. Figure 4 The flowchart of the BWP switching method provided by another embodiment of this application Figure 4 is different from Figure 3 in that Figure 3 step S1011 in Figure 4 can be specifically refined into

[0060] In step S10111, standardization processing is performed on each type of operation performance data.

[0061] Standardization processing can unify and standardize different types of operation performance data, so that different types of operation performance data can participate in the operation together.

[0062] In some examples, the running performance data may include first forward performance data and reverse performance data. The first forward performance data is the forward performance data in the running performance data. The forward performance data includes data that is positively correlated with performance. The larger the value of the forward performance data, the higher the performance characterized by the forward performance data. The reverse performance data includes data that is negatively correlated with performance. The smaller the value of the reverse performance data, the higher the performance characterized by the reverse performance data. The normalization process may include a unified direction process and a normalization process. The unified direction process can be implemented as a forward process or a reverse process to unify the directions of various running performance data. The normalization process can unify the metrics of various running performance data.

[0063] Taking the unified direction process as the forward process as an example for illustration below, the reverse performance data can be forward-processed to obtain second forward performance data; the first forward performance data and the second forward performance data are normalized to obtain the running performance data after the normalization process. The second forward performance data is the reverse performance data after the forward process. The second forward performance data is forward performance data. The forward process processes the reverse performance data into forward performance data with the same direction as the first forward performance data, so that the first forward performance data can participate in subsequent processing together with the second forward performance data.

[0064] For example, the BWPs associated with NCD-SSB include BWP1-2, BWP1-3, BWP1-4, and BWP1-5. The running performance data includes the number of RedCap users, the RedCap user level, the RedCap user CQI, and the uplink interference. The running performance data of the four BWPs associated with the above NCD-SSB can be as shown in Table 1 below:

[0065] Table 1

[0066] BWP Number of RedCap Users RedCap User Level RedCap User CQI Uplink Interference BWP1-2 5 -63 11 -94 BWP1-3 4 -72 8 -97 BWP1-4 8 -77 10 -114 BWP1-5 6 -68 14 -120

[0067] As can be seen from Table 1, the number of RedCap users and the uplink interference are reverse performance data, and the RedCap user level and the RedCap user CQI are forward performance data. It is necessary to forward-process the number of RedCap users and the uplink interference. After the forward process, the running performance data can be as shown in Table 2 below:

[0068] Table 2

[0069] BWP Number of RedCap Users RedCap User Level RedCap User CQI Uplink Interference BWP1-2 0.20 0.016 11 94 BWP1-3 0.25 0.014 8 97 BWP1-4 0.13 0.013 10 114 BWP1-5 0.17 0.015 14 120

[0070] As can be seen from Table II, after the positive normalization process, the number of RedCap users and the uplink interference are consistent with the RedCap user level and the RedCap user CQI, and all become positive performance data. The larger the values of the number of RedCap users, the RedCap user level, the RedCap user CQI, and the uplink interference in Table II, the higher the performance and the higher the priority.

[0071] The normalization process can process the first positive performance data and the second positive performance data into data with values within a predetermined range. For example, the first positive performance data and the second positive performance data can be processed into data with values between 0 and 1. The specific algorithm of the normalization process is not limited here. For example, the algorithm of the normalization process can be shown as the following formula (1):

[0072]

[0073] where Z ij is the running performance data after the j-th normalization process of the i-th BWP; x ij is the j-th positive performance data of the i-th BWP, and this positive performance data can be the first positive performance data or the second positive performance data; n is the number of BWPs associated with NCD-SSB. The running performance data in the above Table II can be normalized as shown in the following Table III: Table III

[0074] BWP Number of RedCap Users RedCap User Level RedCap User CQI Uplink Interference BWP1-2 0.52 0.55 0.50 0.44 BWP1-3 0.65 0.48 0.36 0.45 BWP1-4 0.33 0.45 0.46 0.53 BWP1-5 0.44 0.51 0.64 0.56

[0075] The values of the number of RedCap users, the RedCap user level, the RedCap user CQI, and the uplink interference in Table III are all within the range of 0 to 1.

[0076] Through the standardization process including the positive normalization process and the normalization process, the directions and metrics of the running performance data are made consistent, which is more convenient for calculation and can further improve the accuracy of the priority handover parameters obtained based on the running performance data.

[0077] In step S1022, obtain the extreme values of each type of running performance data after the standardization process.

[0078] The extreme values include the maximum value and the minimum value, that is, the maximum value and the minimum value of each type of running performance data can be obtained from each type of running performance data. For example, if the running performance data after the standardization process is as shown in the above Table III, the maximum value and the minimum value of each type of running performance data obtained can be as shown in Table IV:

[0079] Table IV

[0080] Number of RedCap Users RedCap User Level RedCap User CQI Uplink Interference Maximum Value 0.65 0.55 0.64 0.56 Minimum Value 0.33 0.45 0.36 0.44

[0081] In step S1023, according to the standardized operation performance data and the extreme values of each type of standardized operation performance data, the priority handover parameters for each BWP associated with NCD-SSB are obtained.

[0082] Based on the standardized operation performance data and the extreme values of each type of standardized operation performance data, the distance between the standardized operation performance data of each BWP and the extreme values can be obtained. Based on the distances between the standardized operation performance data of all BWPs and the extreme values, the priority handover parameters for each BWP can be calculated.

[0083] In some examples, for each BWP associated with NCD-SSB, a first distance parameter and a second distance parameter are calculated according to the standardized operation performance data and the extreme values of the operation performance data; the priority handover parameter is obtained according to the first distance parameter and the second distance parameter. The first distance parameter represents the distance between the multiple standardized operation performance data and the maximum value of the operation performance data. The first distance parameter of a BWP can be calculated according to the sum of the squares of the differences between the maximum value of each type of operation performance data and the corresponding operation performance data of this BWP. The second distance parameter represents the distance between the multiple standardized operation performance data and the minimum value of the operation performance data. The second distance parameter of a BWP can be calculated according to the sum of the squares of the differences between the minimum value of each type of operation performance data and the corresponding operation performance data of this BWP. For example, the first distance parameter and the second distance parameter can be calculated according to the following formulas (2) and (3):

[0084]

[0085] where is the first distance parameter of the i-th BWP; is the maximum value of the j-th type of standardized operation performance data; z ij is the j-th type of standardized operation performance data of the i-th BWP; is the second distance parameter of the i-th BWP; is the minimum value of the j-th type of standardized operation performance data; m is the number of types of operation performance data.

[0086] For example, if the standardized operation performance data of the BWPs associated with NCD-SSB are as shown in Table III above, and the extreme values of the standardized operation performance data are as shown in Table IV above, then the first distance parameters and the second distance parameters of BWP1-2, BWP1-3, BWP1-4, and BWP1-5 are as shown in Table V below:

[0087] Table V

[0088] BWP First Distance Parameter Second Distance Parameter BWP1-2 0.23 0.26 BWP1-3 0.30 0.33 BWP1-4 0.39 0.13 BWP1-5 0.22 0.32

[0089] The first distance parameter of a BWP represents the difference between the normalized operating performance data of the BWP and the maximum value of the normalized operating performance data. The second distance parameter of a BWP represents the difference between the normalized operating performance data of the BWP and the minimum value of the normalized operating performance data. The larger the first distance parameter, the greater the difference between the normalized operating performance data of the BWP and the maximum value of the normalized operating performance data. The larger the second distance parameter, the greater the difference between the normalized operating performance data of the BWP and the minimum value of the normalized operating performance data. Based on the first distance parameter and the second distance parameter, the relative level of the normalized operating performance data of each BWP among multiple normalized operating performance data can be obtained. For example, if the normalized operating performance data are all positive performance data, that is, the larger the value of the normalized operating performance data, the higher the represented performance. The maximum value of the normalized operating performance data represents the highest performance represented by the operating performance data among the current multiple NCD-SSB-associated BWPs, and the minimum value of the normalized operating performance data represents the lowest performance represented by the operating performance data among the current multiple NCD-SSB-associated BWPs. Correspondingly, the larger the first distance parameter, the greater the difference between the performance represented by the normalized operating performance data and the highest performance represented by the operating performance data among the current multiple NCD-SSB-associated BWPs; the larger the second distance parameter, the greater the difference between the performance represented by the normalized operating performance data and the lowest performance represented by the operating performance data among the current multiple NCD-SSB-associated BWPs. The performance of the NCD-SSB-associated BWP can be comprehensively evaluated based on the first distance parameter and the second distance parameter, that is, the priority handover parameter is obtained according to the first distance parameter and the second distance parameter.

[0090] In some examples, the priority handover parameter includes the ratio of the second distance parameter to the first sum, or the priority handover parameter includes the ratio of the first distance parameter to the first sum; the first sum is the sum of the first distance parameter and the second distance parameter. For example, the priority handover parameter can be obtained according to Equation (4) or Equation (5) below:

[0091]

[0092] where S iis the priority handover parameter for the i-th BWP; for the descriptions of other parameters, refer to the relevant content in the above embodiments, which will not be elaborated here. The priority handover parameter obtained by using formula (4) is positively correlated with the performance of the BWP, that is, the larger the value of the priority handover parameter, the higher the performance of the BWP. The BWP with the largest priority handover parameter can be determined as the first target BWP. The priority handover parameter obtained by using formula (5) is negatively correlated with the performance of the BWP, that is, the larger the value of the priority handover parameter, the lower the performance of the BWP. The BWP with the smallest priority handover parameter can be determined as the first target BWP.

[0093] For example, if the priority handover parameter is calculated by using formula (4), and the first distance parameter and the second distance parameter of the BWP are as shown in Table Five above, then the priority handover parameters and performance rankings of each BWP are as shown in Table Six below:

[0094] Table Six

[0095] BWP Priority Handover Parameter Performance Ranking BWP1-2 0.54 2 BWP1-3 0.52 3 BWP1-4 0.25 4 BWP1-5 0.59 1

[0096] As shown in Table Six, BWP1-5 are determined as the first target BWP, and at least some of the RedCap users associated with the NCD-SSB of the BWP are handed over to BWP1-5.

[0097] The priority handover parameter obtained by the above method can be comprehensively obtained based on both the difference from the highest performance and the difference from the lowest performance, and the evaluated priority handover parameter representing the performance of the BWP associated with the NCD-SSB is more accurate.

[0098] In some embodiments, since RedCap users with large traffic volumes are more sensitive to the performance of the BWP, the RedCap users with large traffic volumes can be preferentially handed over to the target BWP. Specifically, the base station can obtain the traffic data of the RedCap users set in the current BWP; among the RedCap users set in the current BWP, the RedCap users whose traffic data meets the traffic performance condition are handed over to the target BWP. The traffic performance condition can be used to determine whether a RedCap user is a RedCap user with a large traffic volume. In some examples, the traffic performance condition can include that the traffic data is greater than a preset traffic data threshold value, and the RedCap users of the BWP whose traffic data is greater than the traffic data threshold value are handed over to the target BWP. The traffic data threshold value can be set according to scenarios, requirements, experience, etc., and is not limited here. The RedCap users configured in the BWP whose traffic data does not meet the traffic performance condition can be determined as non-large-traffic RedCap users. For the RedCap users configured in the BWP whose traffic data does not meet the traffic performance condition, these RedCap users can be handed over to the BWP associated with the NCD-SSB with the fewest RedCap users.

[0099] User diversion between RedCap users with large service traffic and those without large service traffic can be achieved through traffic performance conditions, and different RedCap users can be switched to more suitable BWPs associated with NCD-SSBs.

[0100] In some other embodiments, without distinguishing between RedCap users with large service traffic and those without large service traffic, the operation of switching all RedCap users of all BWPs to the target BWP is performed.

[0101] For the sake of easy understanding, the overall process of the BWP switching method for RedCap users is described below with an example. Figure 5 It is a flowchart of an example of the BWP switching process provided by the embodiment of the present application. As Figure 5 shown, this BWP switching process may include steps a1 to a8.

[0102] In step a1, the base station enables the multi-BWP function and the BWP switching function.

[0103] In step a2, the base station obtains various operation performance data of multiple BWPs associated with NCD-SSBs in the current detection period.

[0104] In step a3, the base station obtains the priority switching parameters according to the various operation performance data of multiple BWPs associated with NCD-SSBs.

[0105] In step a4, multiple BWPs associated with NCD-SSBs are sorted according to the priority switching parameters to determine the first target BWP.

[0106] In step a5, the BWP switching is performed on the eligible RedCap users.

[0107] In step a6, the RedCap users with large service traffic configured in the BWP associated with NCD-SSB are switched to the first target BWP.

[0108] In step a7, the RedCap users configured in the BWP associated with CD-SSB are switched to the second target BWP.

[0109] In step a8, the next monitoring period is entered, and the process returns to step a2.

[0110] For the specific content of the above steps a1 to a8, reference can be made to the relevant descriptions in the above embodiments, which will not be elaborated here.

[0111] The present application provides a BWP switching device. Figure 6 It is a schematic structural diagram of the BWP switching device provided by an embodiment of the present application. AsFigure 6 As shown, the BWP switching device 200 may include a performance determination module 201 and a switching module 202.

[0112] The performance determination module 201 may be configured to determine the priority switching parameter of each BWP according to one or more operating performance data of each BWP, and the priority switching parameter characterizes the performance level of the BWP.

[0113] The switching module 202 may be configured to switch the RedCap user set in the current BWP to the target BWP when the performance characterized by the priority switching parameter of the current BWP is lower than the performance characterized by the priority switching parameter of the target BWP, and the target BWP is one of the multiple BWPs.

[0114] In some embodiments, the performance determination module 201 may be configured to: if the current BWP is a BWP associated with a non-cell-defined synchronization signal block (NCD-SSB), determine the priority switching parameter of each BWP associated with the NCD-SSB according to various operating performance data of each BWP associated with the NCD-SSB; if the current BWP is a BWP associated with a cell-defined synchronization signal block (CD-SSB), determine the priority switching parameter of each BWP associated with the NCD-SSB according to the number of RedCap users of each BWP associated with the NCD-SSB, and the performance characterized by the priority switching parameter has a negative correlation with the number of RedCap users.

[0115] In some embodiments, the performance determination module 201 may specifically be configured to: perform normalization processing on each operating performance data; obtain the extreme values of each normalized operating performance data; and obtain the priority switching parameter of each BWP associated with the NCD-SSB according to the normalized operating performance data and the extreme values of each normalized operating performance data.

[0116] In some examples, the extreme values include a maximum value and a minimum value. The performance determination module 201 may specifically be configured to: for each BWP associated with the NCD-SSB, calculate a first distance parameter and a second distance parameter according to the normalized operating performance data and the extreme values of the operating performance data, where the first distance parameter characterizes the distance between the normalized various operating performance data and the maximum value of the operating performance data, and the second distance parameter characterizes the distance between the normalized operating performance data and the minimum value of the various operating performance data; and obtain the priority switching parameter according to the first distance parameter and the second distance parameter.

[0117] In some examples, the priority switching parameter includes the ratio of the first distance parameter to the first sum, or the priority switching parameter includes the ratio of the second distance parameter to the first sum; the first sum is the sum of the first distance parameter and the second distance parameter.

[0118] In some examples, the running performance data includes first forward performance data and reverse performance data. The performance determination module 201 may specifically be configured to: perform forward processing on the reverse performance data to obtain second forward performance data; perform normalization processing on the first forward performance data and the second forward performance data to obtain the running performance data after the normalization processing.

[0119] In some embodiments, the switching module 202 may be configured to: obtain the service traffic data of the RedCap users of the currently set BWP; among the RedCap users of the currently set BWP, switch the RedCap users whose service traffic data meets the traffic performance condition to the target BWP.

[0120] In some embodiments, when the currently set BWP is the BWP associated with CD-SSB, the target BWP includes the BWP associated with NCD-SSB with the smallest number of RedCap users.

[0121] In some examples, the running performance data includes one or more of the following: the number of RedCap users, the level of RedCap users, the channel quality indicator (CQI) of RedCap users, uplink interference, the perceived speed of RedCap users, the connection rate of RedCap users, service delay, handover delay, network jitter, and communication packet loss rate.

[0122] It should be noted that the BWP switching device 200 is a device corresponding to the above-mentioned BWP switching method based on RedCap users. All the implementation manners in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effects.

[0123] This application also provides a base station device. Figure 7 It is a schematic structural diagram of the base station device provided by an embodiment of this application, as Figure 7 shown, the base station device 300 includes a memory 301, a processor 302, and a computer program stored on the memory 301 and executable on the processor 302.

[0124] In some examples, the above-mentioned processor 302 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0125] The memory 301 may include a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the BWP switching method according to embodiments of the present application.

[0126] The processor 302 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 301, so as to implement the BWP switching method in the above embodiments.

[0127] In some examples, the base station device 300 may further include a communication interface 303 and a bus 304. Among them, as Figure 7 shown, the memory 301, the processor 302, and the communication interface 303 are connected through the bus 304 and complete communication with each other.

[0128] The communication interface 303 is mainly used to implement communication between various modules, devices, units, and / or devices in embodiments of the present application. The input device and / or output device may also be accessed through the communication interface 303.

[0129] Bus 304 includes hardware, software, or both, and couples components of base station device 300 to each other. By way of example and not limitation, bus 304 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable bus or a combination of two or more of these. Where appropriate, bus 304 may include one or more buses. Although embodiments of the present application describe and illustrate specific buses, the present application contemplates any suitable bus or interconnect.

[0130] The present application also provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the BWP switching method in the above embodiments can be implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again. Among them, the above computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disc, etc., which are not limited herein.

[0131] The present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the BWP switching method in the above embodiments is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again.

[0132] It should be clear that each embodiment in this specification is described in a progressive manner. For the parts that are the same or similar among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. For the device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments, reference can be made to the description part of the method embodiments for the relevant parts. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of this application. And, for the sake of brevity, the detailed description of known method technologies is omitted here.

[0133] The above has described various aspects of this application with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this application. It should be understood that each block in the flowcharts and / or block diagrams, as well as the combinations of the blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing devices to generate a machine, such that these instructions executed by the processor of the computer or other programmable data processing devices enable the implementation of the functions / actions specified in one or more blocks of the flowcharts and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It can also be understood that each block in the block diagrams and / or flowcharts, as well as the combinations of the blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware that performs the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0134] Those skilled in the art should be able to understand that the above embodiments are all exemplary rather than restrictive. Different technical features that appear in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other variant embodiments of the disclosed embodiments based on the study of the drawings, the specification, and the claims. In the claims, the term "comprising" does not exclude other devices or steps; the quantifier "one" does not exclude a plurality; the terms "first" and "second" are used to label names rather than to indicate any specific order. Any reference signs in the claims should not be construed as limiting the scope of protection. The functions of multiple parts in the claims can be implemented by a single hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A method for bandwidth part (BWP) switching, characterized in that, Including: Determine the priority handover parameter of each BWP according to one or more running performance data of each BWP, where the priority handover parameter characterizes the performance level of the BWP; In the case that the performance characterized by the priority handover parameter of the current BWP is lower than the performance characterized by the priority handover parameter of the target BWP, switch the RedCap user set in the current BWP to the target BWP, where the target BWP is one of multiple BWPs.

2. The method according to claim 1, wherein The determining the priority handover parameter of each BWP according to one or more running performance data of each BWP includes: If the current BWP is a BWP associated with a non-cell-defined synchronization signal block (NCD-SSB), determine the priority handover parameter of each BWP associated with the NCD-SSB according to multiple pieces of the running performance data of each BWP associated with the NCD-SSB; If the current BWP is a BWP associated with a cell-defined synchronization signal block (CD-SSB), determine the priority handover parameter of each BWP associated with the NCD-SSB according to the number of RedCap users of each BWP associated with the NCD-SSB, and the performance characterized by the priority handover parameter has a negative correlation with the number of RedCap users.

3. The method according to claim 2, wherein The determining the priority handover parameter of each BWP associated with the NCD-SSB according to multiple pieces of the running performance data of each BWP associated with the NCD-SSB includes: Perform normalization processing on each piece of the running performance data; Obtain the extreme values of each piece of the running performance data after normalization processing; According to the running performance data after normalization processing and the extreme values of each piece of the running performance data after normalization processing, obtain the priority handover parameter of each BWP associated with the NCD-SSB.

4. The method according to claim 3, wherein The extreme values include maximum values and minimum values; The obtaining the priority handover parameter of each BWP associated with the NCD-SSB according to the running performance data after normalization processing and the extreme values of each piece of the running performance data after normalization processing includes: For each BWP associated with the NCD-SSB, calculate a first distance parameter and a second distance parameter according to the running performance data after normalization processing and the extreme values of the running performance data. The first distance parameter characterizes the distance between multiple pieces of the running performance data after normalization processing and the maximum value of the running performance data, and the second distance parameter characterizes the distance between multiple pieces of the running performance data after normalization processing and the minimum value of the running performance data; Obtain the priority handover parameter according to the first distance parameter and the second distance parameter.

5. The method according to claim 4, wherein The priority handover parameter includes the ratio of the first distance parameter to a first sum, or the priority handover parameter includes the ratio of the second distance parameter to the first sum; The first sum is the sum of the first distance parameter and the second distance parameter.

6. The method according to claim 3, characterized in that The running performance data includes first forward performance data and reverse performance data; The performing normalization processing on each piece of the running performance data includes: Perform a forward transformation on the reverse performance data to obtain second forward performance data; Perform a normalization process on the first forward performance data and the second forward performance data to obtain the running performance data after the normalization process.

7. The method according to claim 1, characterized in that, The switching of the RedCap user set in the current BWP to the target BWP includes: Obtain the traffic data of the RedCap user set in the current BWP; Among the RedCap users set in the current BWP, switch the RedCap users whose traffic data meets the traffic performance conditions to the target BWP.

8. The method according to claim 2, wherein When the current BWP is the BWP associated with CD-SSB, the target BWP includes the BWP associated with NCD-SSB with the fewest RedCap users.

9. The method according to claim 1, wherein The target BWP includes the BWP with the highest performance characterized by the priority switching parameter.

10. The method according to any one of claims 1 to 9, characterized in that The running performance data includes one or more of the following: The number of RedCap users, the level of RedCap users, the channel quality indicator CQI of RedCap users, uplink interference, the perceived speed of RedCap users, the connection rate of RedCap users, service delay, handover delay, network jitter, and communication packet loss rate.

11. A bandwidth part BWP switching device, characterized in that, Includes: A performance determination module, configured to determine the priority switching parameter of each BWP according to one or more running performance data of each BWP, where the priority switching parameter characterizes the performance level of the BWP; A handover module, configured to switch the RedCap users set in the current BWP to the target BWP when the performance characterized by the priority switching parameter of the current BWP is lower than the performance characterized by the priority switching parameter of the target BWP, and the target BWP is one of multiple BWPs.

12. A base station device, characterized in that, Includes: a processor and a memory storing computer program instructions; The processor reads and executes the computer program instructions to implement the bandwidth part BWP switching method according to any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that, Computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by the processor, the bandwidth part BWP switching method according to any one of claims 1 to 10 is implemented.

14. A computer program product, characterized in that, Includes a computer program, and when the computer program is executed by the processor, the bandwidth part BWP switching method according to any one of claims 1 to 10 is implemented.

Images