WO2017088520A1 - 一种上行业务识别切换方法及装置、基站 - Google Patents
一种上行业务识别切换方法及装置、基站 Download PDFInfo
- Publication number
- WO2017088520A1 WO2017088520A1 PCT/CN2016/093614 CN2016093614W WO2017088520A1 WO 2017088520 A1 WO2017088520 A1 WO 2017088520A1 CN 2016093614 W CN2016093614 W CN 2016093614W WO 2017088520 A1 WO2017088520 A1 WO 2017088520A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user terminal
- service
- switching
- time window
- threshold
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/0085—Hand-off measurements
- H04W36/0094—Definition of hand-off measurement parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/16—Performing reselection for specific purposes
- H04W36/22—Performing reselection for specific purposes for handling the traffic
Definitions
- This document relates to, but is not limited to, the field of wireless communications, and relates to an uplink service identification switching method and apparatus, and a base station.
- a resource channel for transmitting data by a user is referred to as an uplink wireless channel
- a channel for receiving data by a user is referred to as a downlink wireless channel.
- LTE Long Term Evolution
- FDD Frequency Division Duplexing
- TDD Time Division Duplexing
- the FDD system supports simultaneous transmission of uplink/downlink radio channel data, but TDD does not support simultaneous transmission of uplink/downlink radio channel data.
- the uplink radio channel and the downlink radio channel of the FDD system use different channels. Therefore, the uplink data transmission and the downlink data transmission of the FDD system do not affect each other.
- the TDD uses different time slots for the uplink wireless channel and the downlink wireless channel occupying the same frequency, and performs uplink/downlink wireless channel data transmission on different subframes according to different time slot ratios. Therefore, FDD is obviously more abundant than TDD in terms of frequency band resources, and the cell bandwidth resources in TDD mode are particularly tense.
- the ratio of the uplink and downlink resources is fixed.
- the common TDD time slot ratio 2 is taken as an example.
- the uplink is used.
- the frame occupies 2 subframes (2 milliseconds).
- Some user terminals (User Equipment, UE for short) cannot be scheduled in time.
- We hope that some users under the TDD cell can be cut into FDD cells with sufficient radio resources and light load.
- the embodiment of the invention provides a method and a device for switching uplink service identification, and a base station, which solves the technology that the user terminal does not receive timely scheduling when the uplink communication channel is resource-stressed and the load is aggravated, and affects the service transmission of the user terminal. problem.
- the embodiment of the invention provides a method for switching an uplink service identification, including:
- the method further includes: before detecting the number of times the user terminal reports the large-capacity service, setting a detection time window for detecting that the user terminal reports the large-capacity service;
- the number of times is the number of times the user terminal reports a large-capacity service within the detection time window.
- determining whether to switch the user terminal to another cell according to the detection result includes:
- the detecting the number of times the user terminal reports the large-capacity service includes: detecting the number of times the service of the same service type of the user terminal reports the large-capacity service.
- the method further includes: before determining whether to switch the user terminal to another cell according to the detection result, setting a handover number threshold according to the currently detected service type, where the handover number threshold is in the detecting The number of times of reporting the large-capacity service is preset in the time window; determining whether to switch the user terminal to another cell according to the detection result includes: comparing the detected number of times with the threshold number of switching times, if the detected If the number of times is greater than or equal to the threshold number of handovers, it is determined that the user terminal needs to be handed over to another cell;
- the method further includes: setting a percentage threshold according to the currently detected service type before determining whether to switch the user terminal to another cell according to the detection result; wherein the percentage threshold is in the detecting Determining, by the time window, a percentage of the number of times the large-capacity service is reported and the number of the theoretical uplink subframes; determining, according to the detection result, whether to switch the user terminal to another cell includes: calculating, detecting the user in the detection time window Number of times the terminal reports large-capacity services And a percentage of the theoretical uplink subframe number; comparing the calculated percentage with the percentage threshold value, and if greater than or equal to the percentage threshold value, determining that the user terminal needs to be handed over to another cell.
- the setting, for detecting, that the detection time window of the user terminal reporting the large-capacity service includes:
- the user terminal is a near-point user, setting the detection time window to a near-point detection time window, where the number of switching times threshold is a near-point switching number threshold, and the percentage threshold is a near-point percentage threshold value;
- the detection time window is set to be a remote detection time window that is greater than the near-point detection time window, where the number of handover times is a threshold value of the number of remote handovers, the percentage The threshold is the far point percentage threshold.
- the method further includes: when determining to switch the user terminal to another cell, switching the user terminal to another cell;
- the switching the user terminal to another cell includes: switching the user terminal to a frequency division duplex mode cell.
- the embodiment of the invention further provides an uplink service identification switching device, including:
- the detecting module is configured to detect the number of times the user terminal reports the large-capacity service
- the determining module is configured to determine whether to switch the user terminal to another cell according to the result of the detection by the detecting module.
- the device further includes:
- a setting module configured to set a detection time window for detecting that the user terminal reports a large-capacity service; wherein the number of times detected by the detecting module is that the user terminal reports a large-capacity service in the detecting time window frequency;
- the detecting module is configured to detect the number of times the service of the same service type of the user terminal reports the large-capacity service.
- the setting module is further configured to set a switching number threshold according to the currently detected service type, where the switching number threshold is a number of times that the large-capacity service is preset to be reported in the detection time window;
- the determining module includes a first determining submodule
- the first determining sub-module is configured to compare the number of times detected by the detecting module with the threshold of the number of switching times set by the setting module, and if the number of times detected by the detecting module is greater than or equal to the threshold of the number of switching times, Then it is determined that the user terminal needs to be switched to another cell.
- the setting module is further configured to set a percentage threshold according to the currently detected service type; wherein the percentage threshold is a number of times and a theory for pre-reporting the large-capacity service within the detection time window. The percentage of the number of uplink subframes;
- the determining module includes a second determining submodule
- the second determining sub-module is configured to calculate a percentage of detecting the number of times the user terminal reports the large-capacity service and the number of theoretical uplink subframes in the detecting time window; and performing the calculated percentage and the percentage threshold For comparison, if the calculated percentage is greater than or equal to the percentage threshold, it is determined that the user terminal needs to be handed over to another cell.
- the device further includes a switching module, where the switching module includes a frequency division duplex switching submodule;
- the frequency division duplex switching submodule is configured to switch the user terminal to a frequency division duplex mode cell.
- the embodiment of the invention further provides a base station, comprising: any uplink service identification switching device as described above.
- the base station detects the number of times the user terminal reports the large-capacity service, and then determines whether to switch the user terminal to another cell according to the detection result.
- the embodiment of the present invention determines the actual data amount required for the current transmission of the user terminal according to the large-capacity service reported by the user terminal, and implements real-time monitoring of the service transmission of the user terminal, ensuring fast and accurate performance.
- the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements an uplink service identification switching method.
- FIG. 1 is a flowchart of a method for switching an uplink service identification according to Embodiment 1 of the present invention
- FIG. 2 is a flowchart of starting a method for switching an uplink service identification of a large-capacity service user according to Embodiment 2 of the present invention
- FIG. 3 is a flowchart of detecting processing of a method for switching an uplink service identification of a large-capacity service user according to Embodiment 2 of the present invention
- FIG. 4 is a schematic diagram of a remote user detection time window according to Embodiment 2 of the present invention.
- FIG. 5 is a schematic diagram of a near-point user detection time window according to Embodiment 2 of the present invention.
- FIG. 6 is a schematic structural diagram of an uplink service identification switching apparatus according to Embodiment 3 of the present invention.
- Embodiment 1 is a diagrammatic representation of Embodiment 1:
- FIG. 1 is a flowchart of a method for switching an uplink service identification according to an embodiment of the present disclosure. Referring to FIG. 1, the method includes:
- Step S101 detecting the number of times the user terminal reports the large-capacity service
- Step S102 Determine, according to the detection result, whether to switch the user terminal to another cell.
- the number of times of detecting a large-capacity service may be detected by detecting a number of times of a Buffer Status Report (BSR) reported by the user terminal UE before performing a service.
- BSR Buffer Status Report
- the user equipment UE obtains the data of the BSR by the reported BSR. Therefore, by detecting the number of reported BSRs, it is known how much data of the user terminal UE is buffered in the uplink data buffer. How much data is actually needed by the terminal UE to complete the transmission.
- BSR Buffer Status Report
- the detecting the large-capacity service in step S101 may further include determining the size of the BSR reported by the user terminal, and determining whether the reported BSR is a BSR of the large-capacity service, and if the reported BSR is a BSR of the large-capacity service, Then, the number of times the user terminal reports the large-capacity service is detected to be increased by one.
- the threshold when determining whether the reported BSR is a BSR of a large-capacity service, the threshold may be determined by setting a threshold (T1), if the reported BSR is greater than or equal to a preset threshold (T1) If the reported BSR is a large-capacity service BSR, the number of times is increased by one; if the reported BSR is less than the preset threshold (T1), it is not a large-capacity service BSR, and the number of times does not increase.
- the threshold T1 for determining that the BSR is a large-capacity service BSR is set, and may be determined according to a related protocol.
- the size of the Layer 2 buffer (L2Buffer) of the user terminal in this embodiment is the table (Table) 4.1-3 of the protocol 36.306, and the capability level of the largest L2Buffer user terminal UE defined by the protocol is determined by
- the maximum BSR that can be reported by the UE MAC (Medium Access Control, MAC) layer is determined by the definition of the protocol.
- Type of user terminal The size of the second layer buffer (byte bytes) Type 1 150000 Type 2 700000 Type 3 1400000 Type 4 1900000 Type 5 35000000
- Table 2 is a table for dividing the size of a common buffer according to an embodiment of the present invention.
- Table 3 is a table for dividing the size of an extended buffer according to an embodiment of the present invention;
- the report has 64 index value definitions, and each index corresponds to an interval, which is determined by the protocol.
- Table 6.1.3.1-1 and Table 6.1.3.1-2 of 30.321 are defined.
- the maximum data block size of each TTI (Transmission Time Interval) is defined by Table 4.1-2 of 36.306.
- Table 4 is a user terminal according to an embodiment of the present invention transmitting at a transmission time interval. The largest data scale.
- the setting of the threshold value (T1) can be determined by the buffer division interval in Table 6.1.3.1-1, as shown in Table 2, for example:
- the user terminal UE capability level 3 is taken as an example. Assume that there is only one scheduling UE in the uplink, and the maximum buffer size that can be scheduled in each uplink subframe is 6378 bytes (Byte), then the corresponding BSR index in Table 2 is 42, the buffer.
- the BSR threshold T1 of the large-capacity service that should be set is 42 The lower limit in the index interval, or the value in the interval less than 42 index.
- the size of the extended buffer provided by Table 3 should be set as a standard.
- the method further includes: before step S101, setting a detection time window for detecting that the user terminal reports a large-capacity service; wherein the number of times is that the user terminal is in the The number of times the large-capacity service is reported in the detection time window.
- the number of times of detecting the large-capacity service is the number of times of the large-capacity service reported by the service in the same service type, and when it is detected that the number of times of reporting the large-capacity service is greater than or equal to a preset number of times, determining The user terminal needs to be handed over to another cell.
- switching the user terminal to another cell includes: switching the user terminal to a frequency division duplex cell.
- the method further includes: determining, according to the detection result, whether Before the user terminal switches to another cell, the switch number threshold is set according to the currently detected service type, where the switch number threshold is the number of times N of the large-capacity service is preset to be reported in the detection time window;
- determining whether to switch the user terminal to another cell includes: comparing the number of times of detecting with the threshold of the number of times of switching, and if it is greater than or equal to the threshold of the number of times of switching, determining that the user terminal needs to be handed over to another cell. ;
- the method further includes: before determining whether to switch the user terminal to another cell according to the detection result, setting a percentage threshold (T5) according to the currently detected service type; wherein the percentage threshold (T5) And determining, by the detection result, whether to switch the user terminal to another cell according to the detection result, where: calculating, at the detection time, the percentage of the number of times of reporting the large-capacity service and the number of theoretical uplink subframes in the detection time window; Detecting, in the window, a percentage of the number of times the user terminal reports the large-capacity service and the number of theoretical uplink subframes; comparing the calculated percentage with the percentage threshold (T5), if greater than or equal to the percentage threshold (T5), Then it is determined that the user terminal needs to be switched to another cell.
- the method further includes: determining whether the user terminal is a near-point user or a far-end user before determining whether to switch the user terminal to another cell according to the detection result.
- first setting is used to determine that the user terminal sets a path loss threshold (T2) for a near-point user or a far-end user; and if the current path loss value of the user terminal is compared with a preset path loss threshold, if If the current path loss value of the user terminal is greater than the preset path loss threshold (T2), it is determined that the user terminal is a far-end user, otherwise it is a near-point user.
- the path loss threshold (T2) is generally set to 120.
- the value is not fixed and unique, and can be appropriately adjusted for different network element environments.
- the adjustment of the path loss value (T2) in different network element environments may be calculated and adjusted according to the calculation formula provided in the protocol 36.213.
- the calculation may be performed according to the transmission power of the user terminal for the near point and the far point. .
- the detection time window includes a near-point detection time window and a far-point detection time window, wherein the near-point user and the far-end user respectively obtain the number of BSRs reported by the user terminal UE in the corresponding detection time window; If the user terminal is a near-point user, the setting is performed within the near-point detection time window; if the user terminal is a far-end user, the remote point detection is set. The detection is performed in a time window, and the far point detection time window is larger than the near point detection time window.
- the near-point handover threshold and the near-point percentage threshold are set for the near-point user and the far-end user in the corresponding detection time window. Value, far-point switching threshold and far-point percentage threshold.
- the setting of the detection time window for detecting the large-capacity service BSR is also determined according to the different service types specified by the protocol and the slot ratio of the system TDD.
- the user terminal is a near-point user, detecting the actual number of times the user terminal reports the BSR in the near-point detection time, when the detected actual number of times is greater than or equal to the near-point handover number threshold, The user terminal is a near-point large-capacity service user; or the percentage of the theoretical uplink subframe is calculated according to the detected actual secondary data, and compared with the near-point percentage threshold, if the ratio is greater than or equal to the near If the percentage threshold is used, the user terminal is a near-point large-capacity service user.
- the user terminal When the user terminal is a remote user, by detecting the number of times the user terminal reports the BSR in the remote detection time, when the actual number of detections is greater than or equal to the threshold value of the remote handover number, The user terminal is a far-end large-capacity service user; or the percentage of the theoretical uplink subframe is calculated according to the detected actual secondary data, and compared with the far-point percentage threshold, if the distance is greater than or equal to the far point For the percentage threshold, the user terminal is a remote large-capacity service user.
- the number of times of acquiring the large-capacity service BSR reported by the user terminal in the detection time window is detected, and may be counted by setting a BSR counter, and is detected in the detection time window.
- the BSR counter corresponding to the user terminal is incremented by 1 until the detection time window ends; when the detection time window ends, according to the value of the BSR counter and The percentage of the number of theoretical uplink subframes determines whether the user terminal needs to be handed over to other cells; after the judgment is completed, the BSR counter is cleared, waiting for the next detection time window to be re-counted; or directly determining the BSR counter Whether the count value reaches the preset number of times of reporting the BSR, if it is reached, it is determined that the user terminal needs to be switched to another cell, and the BSR counter is cleared, waiting for the next detection time window to recount.
- the detecting time window is performed according to the characteristics of the service model.
- the characteristic table of different service models provided in this embodiment provides the data size of different services, that is, the size of the BSR, by analyzing the characteristics of different service models.
- the capability level here refers to the transmission rate level that the UE can support; the L2 maximum buffer is 1.400000 bytes, each scheduling is 6378 bytes, and each TTI (transmission time interval, transmission time)
- the interval (TTI) is only one user terminal UE, and the theoretical completion time of different service models is analyzed.
- Table 6 is a theoretical completion schedule of different service models provided by the embodiments of the present invention.
- the BSR period 10 milliseconds (ms)
- 100 ms that is, the actual user experience duration of TDD configuration 2 is 500 ms
- the theoretical detection time window is obtained.
- the detection time window length of all data transmissions of each service model can be obtained, and the calculation is specifically to multiply the time recorded in Table 6 by 5 It is concluded that because the time in Table 6 is counted according to the number of TDD uplink subframes. For example, a service with a service number of 2 can complete the data transmission as a near-point user in only 0.5s. As a mid-point user, it can be transmitted in only 1.5s, as a far-end user within 4s. You can pass it all. Therefore, for the service with service number 2, the near-point detection time window T3 of the near-point user can be set to 0.5 seconds (s), and the far-point detection time window T4 of the far-end user can be set to 1.5 s.
- the far point detection time window of the far point user is an integer multiple of the near point detection time window of the near point user.
- Embodiment 2 is a diagrammatic representation of Embodiment 1:
- FIG. 2 is a flowchart of a method for starting a large-capacity service user uplink service identification switching method according to the embodiment.
- the specific steps of starting a large-capacity service BSR are included on the basis of setting all the parameters in the first embodiment. :
- Step S201 starting a detection switch of a large-capacity service
- the detection of large-capacity services will only be started if the detection switch is turned on, otherwise the detection of large-capacity services will not be performed;
- Step S202 waiting for the arrival of the detection time window
- the detection switch After the detection switch is turned on, the detection of the large-capacity service by the user terminal is not performed immediately, but the waiting time window is continuously waited for, that is, the detection of the large-capacity service is performed periodically;
- S203 Determine whether the detection time window is coming; if the detection time window arrives, perform detection processing for reporting the large-capacity service, otherwise the processing is not performed;
- step S203 if the detection time window arrives and is within the detection time window, the detection processing for reporting the large-capacity service is started, and the specific large-capacity service detection processing is as shown in FIG. 3.
- FIG. 3 is a flowchart of a detection process of a method for switching an uplink service identification of a large-capacity service user according to the embodiment, where specific steps include:
- Step S301 waiting for the arrival of the detection time window
- Step S302 determining that the detection time window arrives
- Step S303 detecting that the BSR reported by the user terminal UE is obtained
- the user terminal UE When the user terminal UE has uplink data transmission, the user terminal UE periodically reports the BSR.
- Step S304 determining whether the reported BSR is a large-capacity service BSR
- step S304 the obtained BSR is compared with the threshold T1 of the uplink service transmission of the user terminal UE, and if the obtained BSR is greater than the threshold T1, it is determined to be a large-capacity service.
- the BSR proceeds to step S305; otherwise, if the obtained BSR is less than or equal to the threshold value T1, the process returns to step S303 to wait for the next acquired BSR to perform the determination;
- Step S305 adding a BSR counter value of the corresponding calculated large-capacity service BSR by one;
- Step S306 determining whether the detection time window is over; if the detection time window is over, proceeding to step S307, determining whether the user terminal UE is a large-capacity service user; otherwise, if the detection time window is not over, proceeding to step S303, continuing to wait for the UE to report BSR;
- Step S307 determining whether the count value of the BSR counter is greater than or equal to the preset number of times N. If the count value of the BSR counter is greater than or equal to the preset number of times N, the final detection result of the user terminal UE is a large-capacity service user. Go to step S308; otherwise, if the count value of the BSR counter is less than the preset number of times N is not a large-capacity service user, then go to step S301;
- step S308 If the user terminal UE is not a large-capacity service user, if the user is less than the preset threshold (T5), the process proceeds to step S301;
- Step S308 determining that the detection result is a large-capacity service user and reporting information of the user terminal;
- Step S309 performing handover processing on the user terminal according to the information of the reported user terminal, and switching to another cell.
- the detection period and the detection time window of the far-point large-capacity service user are set as shown in FIG. 4, and the detection period and the detection time window of the near-point large-capacity service user are set as shown in FIG. 5,
- the configuration period t1 to t3 is a detection period.
- t1 to t2 are detection time windows of large-capacity service detection, when detecting t1.
- the detection of the large-capacity service is performed, and the count value of the BSR counter that reports the large-capacity service is counted until the time t2 arrives, and the detection stops.
- step S307 in FIG. 3 it is determined whether the user terminal UE is When it is determined as a large-capacity service user in step S307, the large-capacity service user performs step S308 and performs a report process.
- FIG. 5 is a schematic diagram of a near-point user detection time window according to the embodiment.
- the configuration period t1 to t3 is a detection period.
- t1 to t6 and t6 to t2 are respectively detection time windows of the large-capacity service. That is, the result of whether it is a large-capacity service is detected in the window from t1 to t6.
- the detection time window of the remote user has not ended yet, the detection result of the near-point user is not reported at this time, waiting for the next detection time.
- the detection result of the window t6 to t2 waits until the time t2 arrives to determine whether the user terminal is a large-capacity user and reports the processing.
- each cell has a remote user and a near-point user.
- the detection of the reported large-capacity service is performed on a cell basis, and all user terminals report the detection result at the same time.
- the data of the same size is transmitted, and the time required by the user is longer. Therefore, the reporting time point is the end time of the detection time window of the far-end user, which also requires the detection time window length of the far-end user to be set to the near-point user. Detects an integer multiple of the time window.
- Embodiment 3 is a diagrammatic representation of Embodiment 3
- the embodiment provides an uplink service identification switching device. As shown in FIG. 6 , in the embodiment, the device includes: a detection module 11 and a determination module 12;
- the detecting module 11 is configured to detect the number of times the user terminal reports a large-capacity service
- the determining module 12 is configured to determine, according to the result of the detection by the detecting module 11, whether to switch the user terminal to another cell.
- the uplink service identification switching device further includes: a setting module 13 configured to set a detection time window for detecting that the user terminal reports a large-capacity service; wherein the detecting module The number of detections is the number of times the user terminal reports a large-capacity service.
- the detecting module 11 is configured to detect the number of times that the service of the same service type of the user terminal reports the large-capacity service.
- the setting module 13 is further configured to set a threshold of the number of times of switching according to the currently detected service type, where the threshold of the number of times of switching is preset to report a large capacity in the detection time window. Number of times of business;
- the determining module 12 includes a first determining sub-module 121;
- the first determining sub-module 121 is configured to compare the number of times detected by the detecting module with the threshold number of switching times set by the setting module, if the number of times detected by the detecting module is greater than or equal to the threshold of the number of switching times Then, it is determined that the user terminal needs to be handed over to another cell.
- the setting module 13 is further configured to set a percentage threshold according to the currently detected service type, where the percentage threshold is preset to be reported in the detection time window.
- the determining module 12 includes a second determining sub-module 122;
- the second determining sub-module 122 is configured to calculate a percentage of detecting the number of times the user terminal reports the large-capacity service and the number of theoretical uplink subframes in the detection time window; and calculating the percentage and the percentage threshold For comparison, if the calculated percentage is greater than or equal to the percentage threshold, it is determined that the user terminal needs to be handed over to another cell.
- the apparatus further includes: a switching module 14, where the switching module 14 includes a frequency division duplex switching sub-module 141, configured to switch the user terminal from a time division duplex mode cell to a Frequency division duplex mode cell.
- the switching module 14 includes a frequency division duplex switching sub-module 141, configured to switch the user terminal from a time division duplex mode cell to a Frequency division duplex mode cell.
- the user terminal may further perform classification of the near-point user and the far-point, and set the path loss threshold to implement classification;
- the current path loss value of the user terminal is compared with the preset path loss threshold. If the current path loss value of the terminal user is greater than the preset path loss threshold, the user terminal is determined to be a far-end user, otherwise, the near-point user is .
- the detecting module 11 determines the number of BSRs reported by the user terminal in the set detection time window, and the determining module 12 determines, according to the result detected by the detecting module 11, whether the reported BSR is It is a large-capacity service BSR, and if so, the BSR counter is incremented by one; when the detection time window is over, the determination module 12 determines whether the count value of the BSR counter reaches the switching number threshold, and if so, determines The user terminal is a large-capacity service user, otherwise it is not a large-capacity service user; or the calculation sub-module calculates a percentage of the BSR counter count value and the theoretical uplink subframe number, and then calculates the percentage and percentage The size of the threshold value T5 is compared.
- the user terminal is determined to be a large-capacity service user, and the BSR counter is cleared, waiting for the next detection time window to be re-counted; and finally reporting the information of the user terminal.
- the switching module 14 switches the corresponding user terminal to another cell according to the reported information.
- a base station is further provided, where the base station includes any uplink service identification switching device in the foregoing embodiment, where the base station detects the number of times the user terminal reports a large-capacity service, and determines whether to The user terminal switches to another cell.
- the base station acquires the BSR reported by the user terminal in the set detection time window, and determines that the BSR is a large-capacity service BSR according to the BSR, and adds a BSR counter to the large-capacity service BSR; After the window ends, calculating a percentage of the count value of the BSR counter and the number of theoretical uplink subframes, and determining, according to the percentage, whether the user terminal is a large-capacity service user, and if yes, switching the user terminal to another cell. .
- the handover scheduling of the user terminals between the neighboring cells is implemented, and the cell is used in the case that the resources are insufficient or tight, and the load is large.
- the resources of each cell can be shared with each other, and the experience of the cell user terminal is further improved, and the resource utilization rate is improved.
- modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
- they may be implemented by program code executable by the computing device such that they may be stored in a storage medium (ROM/RAM, diskette, optical disk) by a computing device, and in some cases
- the steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Therefore, the invention is not limited to any particular combination of hardware and software.
- the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements an uplink service identification switching method.
- the above technical solution can reduce the load of the cell, improve the experience of the user terminal, and improve the resource utilization rate of the cell.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种上行业务识别切换方法及装置、基站,所述方法包括检测用户终端上报大容量业务的次数,根据检测的结果判断所述用户终端为大容量业务用户,并将所述用户终端切换到其他小区。本发明实施例是通过直接检测判断用户终端所上报的容量业务来确定是否为大容量业务用户,使得基站可以实时监控用户终端的业务传输量,在通信信道资源出现紧张或者负荷加重时,及时将业务传输量大的用户终端切换到期其他小区,从而减轻该小区的负荷,进一步的提高用户终端的体验度,同时也提高了小区的资源利用率。
Description
本文涉及但不限于无线通信领域,涉及一种上行业务识别切换方法及装置、基站。
在无线通信领域中,将用户发送数据的资源通道称之为上行无线信道,用户接收数据的通道称之为下行无线信道。
相关的LTE(长期演进,Long Term Evolution)系统都支持频分双工(Frequency Division Duplexing,简称FDD)和时分双工(Time Division Duplexing,简称TDD)两种信道工作模式。
FDD系统支持上行/下行无线信道数据的同时传输,但是TDD不支持上行/下行无线信道数据的同时传输。FDD系统的上行无线信道和下行无线信道所采用的是不同的信道,因此,FDD系统的上行数据传输与下行数据传输,两者不会互相影响。TDD对占用同一个频率的上行无线信道和下行无线信道使用不同的时隙,按照不同的时隙配比,在不同的子帧上进行上行/下行无线信道数据传输。所以,在频段资源方面FDD明显比TDD要充裕,TDD模式下的小区带宽资源就显得尤为紧张。
针对任一小区,如果TDD的时隙配比固定,则上下行的资源占比就是固定的,以常用的TDD时隙配比2为例,在一个系统帧(10毫秒时间)内,上行子帧就占用2个子帧(2毫秒时间),如果出现大量用户有上行数据发送,上行的信道资源就明显紧张,小区负荷加重,有些用户终端(User Equipment,简称UE)就得不到及时调度,严重影响用户业务。这时候我们就希望TDD小区下的某些用户能被切到无线资源充裕、负荷较轻的FDD小区下。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求
的保护范围。
本发明实施例提供一种上行业务识别切换方法及装置、基站,解决了相关技术中上行通信信道出现资源紧张、负荷加重时,用户终端得不到及时的调度,而影响用户终端业务传输的技术问题。
本发明实施例提供一种上行业务识别切换方法,包括:
检测用户终端上报大容量业务的次数;
根据检测结果判断是否将所述用户终端切换到其他小区。
可选地,所述方法还包括:在检测用户终端上报大容量业务的次数之前,设置用于检测所述用户终端上报大容量业务的检测时间窗;
其中,所述次数为所述用户终端在所述检测时间窗内上报大容量业务所发生的次数。
可选地,根据检测结果判断是否将所述用户终端切换到其他小区包括:
当所述上报大容量业务的次数大于或等于预设的次数时,则判定需要将所述用户终端切换到其他小区。
可选地,所述检测用户终端上报大容量业务的次数包括:检测用户终端同一业务类型下的业务上报大容量业务的次数。
可选地,所述方法还包括:在根据检测结果判断是否将所述用户终端切换到其他小区之前,根据当前检测的业务类型设置切换次数阈值,其中,所述切换次数阈值为在所述检测时间窗内预设上报大容量业务的次数;所述根据检测结果判断是否将所述用户终端切换到其他小区包括:将检测到的次数与所述切换次数阈值进行比较,若所述检测到的次数大于或等于所述切换次数阈值,则判定需要将所述用户终端切换到其他小区;
或者,所述方法还包括:在根据检测结果判断是否将所述用户终端切换到其他小区之前,根据当前检测的业务类型设置百分比门限值;其中,所述百分比门限值为在所述检测时间窗内预设上报大容量业务的次数与理论上行子帧数的百分比;所述根据检测结果判断是否将所述用户终端切换到其他小区包括:计算在所述检测时间窗内检测所述用户终端上报大容量业务的次数
与理论上行子帧数的百分比;将计算的百分比与所述百分比门限值进行比较,若大于或等于所述百分比门限值,则判定需要将所述用户终端切换到其他小区。
可选地,所述设置用于检测所述用户终端上报大容量业务的检测时间窗具体包括:
如果所述用户终端为近点用户,则设置所述检测时间窗为近点检测时间窗,其中,所述切换次数阈值为近点切换次数阈值,所述百分比门限值为近点百分比门限值;
如果所述用户终端为远点用户,则设置所述检测时间窗为大于所述近点检测时间窗的远点检测时间窗,其中,所述切换次数阈值为远点切换次数阈值,所述百分比门限值为远点百分比门限值。
可选地,所述方法还包括:在判断将所述用户终端切换到其他小区时,将所述用户终端切换到其他小区;
其中,所述将所述用户终端切换到其他小区包括:将所述用户终端切换到频分双工模式小区。
本发明实施例还提供一种上行业务识别切换装置,包括:
检测模块,设置为检测用户终端上报大容量业务的次数;
判断模块,设置为根据所述检测模块检测的结果判断是否将所述用户终端切换到其他小区。
可选地,装置还包括:
设置模块,设置为设置用于检测所述用户终端上报大容量业务的检测时间窗;其中,所述检测模块检测的次数为所述用户终端在所述检测时间窗内上报大容量业务所发生的次数;
所述检测模块,是设置为检测用户终端同一业务类型下的业务上报大容量业务的次数。可选地,
所述设置模块,还设置为根据当前检测的业务类型设置切换次数阈值,其中,所述切换次数阈值为在所述检测时间窗内预设上报大容量业务的次数;
所述判断模块包括第一判断子模块;
所述第一判断子模块,设置为将所述检测模块检测到的次数与所述设置模块设置的切换次数阈值进行比较,若所述检测模块检测到的次数大于或等于所述切换次数阈值,则判定需要将所述用户终端切换到其他小区。
可选地,所述设置模块,还设置为根据当前检测的业务类型设置百分比门限值;其中,所述百分比门限值为在所述检测时间窗内预设上报大容量业务的次数与理论上行子帧数的百分比;
所述判断模块包括第二判断子模块;
所述第二判断子模块,设置为计算在所述检测时间窗内检测所述用户终端上报大容量业务的次数与理论上行子帧数的百分比;将计算的百分比与所述百分比门限值进行比较,若计算的百分比大于或等于所述百分比门限值,则判定需要将所述用户终端切换到其他小区。
。
可选地,所述装置还包括切换模块,所述切换模块包括频分双工切换子模块;
所述频分双工切换子模块,设置为将所述用户终端切换到频分双工模式小区。
本发明实施例还提供了一种基站,包括:如上所述任一的上行业务识别切换装置。
本发明实施例的有益效果是:
本发明实施例提供的上行业务识别切换方法及装置、基站是通过检测用户终端上报大容量业务的次数,然后根据检测结果判断是否将所述用户终端切换到其他小区。本发明实施例是根据用户终端上报的大容量业务来判断所述用户终端当前传输业务所需的实际数据量,实现了对所述用户终端的业务传输的实时监控,保证了能快速、准确地从上报大容量业务中判断出大容量业务用户,并将该用户终端切换到其他小区,大大地提高了处理效率,实现
了每个相邻小区之间用户终端的调度以及对用户终端的准确定位调度,进一步的提高了整个网元通信信道的资源的利用率,解决了小区通信信道资源的紧张,减轻了各小区的负荷,从而提高了用户终端的体验度。本发明实施例还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机可执行指令,所述计算机可执行指令被执行时实现上行业务识别切换方法。
在阅读并理解了附图和详细描述后,可以明白其它方面。
图1为本发明实施例一提供的一种上行业务识别切换方法的流程图;
图2为本发明实施例二提供的大容量业务用户上行业务识别切换方法的启动流程图;
图3为本发明实施例二提供的大容量业务用户上行业务识别切换方法的检测处理流程图;
图4为本发明实施例二提供的远点用户检测时间窗示意图;
图5为本发明实施例二提供的近点用户检测时间窗示意图;
图6为本发明实施例三提供的一种上行业务识别切换装置结构示意图。
下面通过具体实施方式结合附图对本申请作进一步详细说明。
实施例一:
图1为本实施例提供的一种上行业务识别切换方法的流程图,请参考图1,所述方法包括:
步骤S101,检测用户终端上报大容量业务的次数;
步骤S102,根据检测结果判断是否将所述用户终端切换到其他小区。
在本实施例中,检测大容量业务的次数,可以通过检测所述用户终端UE在进行业务前上报的缓存状态报告(Buffer Status Report,简称BSR)的次数,
由于用户终端UE进行上行业务传输时所需要的资源是通过上报的BSR来获取的,因此,通过检测上报的BSR的次数来获知所述用户终端UE有多少数据缓存在上行数据缓冲区中,用户终端UE实际需要多少的数据量才能完成传输。
进一步的,在步骤S101检测大容量业务中,还可以包括判断检测到的用户终端上报的BSR的大小,确定上报的BSR是否为大容量业务的BSR,若上报的BSR是大容量业务的BSR,则将检测用户终端上报大容量业务的次数加1。可选的,在判断上报的BSR是否为大容量业务的BSR时,可以通过设置一个门限值(T1)来进行判断区分,如果所述上报的BSR大于或等于预设的门限值(T1),则该上报的BSR为大容量业务BSR,次数加1;否,如果所述上报的BSR小于预设的门限值(T1),则不是大容量业务BSR,次数不增加。
在本实施例中,设置用于判断所述BSR为大容量业务BSR的门限值T1,可以根据相关的协议规定来确定。如表1所示,为本实施例的用户终端的二层缓冲区(L2Buffer)的大小,即是协议36.306的表(Table)4.1-3,协议定义的最大L2Buffer用户终端UE的能力级别,由协议36.306Table 4.1-3定义,决定了UE MAC(介质访问控制,Medium Access Control,简称MAC)层能上报的最大BSR。
用户终端的类型 | 二层缓冲区的大小(字节bytes) |
类型1 | 150000 |
类型2 | 700000 |
类型3 | 1400000 |
类型4 | 1900000 |
类型5 | 35000000 |
表1
如表2和表3所示,表2为本发明实施例提供的普通缓冲区的大小划分情况表,表3为本发明实施例提供的扩展缓冲区的大小划分情况表;用户终端UE的BSR上报有64个索引值定义,每个索引对应一个区间,由协议的
30.321的Table 6.1.3.1-1和Table 6.1.3.1-2定义。每个TTI(Transmission Time Interval,传输时间间隔)调度的最大数据块大小由36.306的Table 4.1-2定义,如表4所示,表4为本发明实施例提供的用户终端在一个传输时间间隔传输的最大数据量表。
索引 | 缓冲区大小值 | 索引 | 缓冲区大小值 |
0 | BS=0 | 32 | 1132<BS<=1326 |
1 | 0<BS<=10 | 33 | 1326<BS<=1552 |
2 | 10<BS<=12 | 34 | 1552<BS<=1817 |
3 | 12<BS<=14 | 35 | 1817<BS<=2127 |
4 | 14<BS<=17 | 36 | 2127<BS<=2490 |
5 | 17<BS<=19 | 37 | 2490<BS<=2915 |
6 | 19<BS<=22 | 38 | 2915<BS<=3413 |
7 | 22<BS<=26 | 39 | 3413<BS<=3995 |
8 | 26<BS<=31 | 40 | 3995<BS<=4677 |
9 | 31<BS<=36 | 41 | 4677<BS<=5476 |
10 | 36<BS<=42 | 42 | 5476<BS<=6411 |
11 | 42<BS<=49 | 43 | 6411<BS<=7505 |
12 | 49<BS<=57 | 44 | 7505<BS<=8787 |
13 | 57<BS<=67 | 45 | 8787<BS<=10287 |
14 | 67<BS<=78 | 46 | 10287<BS<=12043 |
15 | 78<BS<=91 | 47 | 12043<BS<=14099 |
16 | 91<BS<=107 | 48 | 14099<BS<=16507 |
17 | 107<BS<=125 | 49 | 16507<BS<=19325 |
18 | 125<BS<=146 | 50 | 19325<BS<=22624 |
19 | 146<BS<=171 | 51 | 22624<BS<=26487 |
20 | 171<BS<=200 | 52 | 26487<BS<=31009 |
21 | 200<BS<=234 | 53 | 31009<BS<=36304 |
22 | 234<BS<=274 | 54 | 36304<BS<=42502 |
23 | 274<BS<=321 | 55 | 42502<BS<=49759 |
24 | 321<BS<=376 | 56 | 49759<BS<=58255 |
25 | 376<BS<=440 | 57 | 58255<BS<=68201 |
26 | 440<BS<=515 | 58 | 68201<BS<=79846 |
27 | 515<BS<=603 | 59 | 79846<BS<=93479 |
28 | 603<BS<=706 | 60 | 93479<BS<=109439 |
29 | 706<BS<=826 | 61 | 109439<BS<=128125 |
30 | 826<BS<=967 | 62 | 128125<BS<=150000 |
31 | 967<BS<=1132 | 63 | BS>150000 |
表2
索引 | 缓冲区大小值 | 索引 | 缓冲区大小值 |
0 | BS=0 | 32 | 4940<BS<=6074 |
1 | 0<BS<=10 | 33 | 6074<BS<=7469 |
2 | 10<BS<=13 | 34 | 7469<BS<=9185 |
3 | 13<BS<=16 | 35 | 9185<BS<=11294 |
4 | 16<BS<=19 | 36 | 11294<BS<=13888 |
5 | 19<BS<=23 | 37 | 13888<BS<=17077 |
6 | 23<BS<=29 | 38 | 17077<BS<=20999 |
7 | 29<BS<=35 | 39 | 20999<BS<=25822 |
8 | 35<BS<=43 | 40 | 25822<BS<=31752 |
9 | 43<BS<=53 | 41 | 31752<BS<=39045 |
10 | 53<BS<=65 | 42 | 39045<BS<=48012 |
11 | 65<BS<=80 | 43 | 48012<BS<=59039 |
12 | 80<BS<=98 | 44 | 59039<BS<=72598 |
13 | 98<BS<=120 | 45 | 72598<BS<=89272 |
14 | 120<BS<=147 | 46 | 89272<BS<=109774 |
15 | 147<BS<=181 | 47 | 109774<BS<=134986 |
16 | 181<BS<=223 | 48 | 134986<BS<=165989 |
17 | 223<BS<=274 | 49 | 165989<BS<=204111 |
18 | 274<BS<=337 | 50 | 204111<BS<=250990 |
19 | 337<BS<=414 | 51 | 250990<BS<=308634 |
20 | 414<BS<=509 | 52 | 308634<BS<=379519 |
21 | 509<BS<=625 | 53 | 379519<BS<=466683 |
22 | 625<BS<=769 | 54 | 466683<BS<=573866 |
23 | 769<BS<=945 | 55 | 573866<BS<=705666 |
24 | 945<BS<=1162 | 56 | 705666<BS<=867737 |
25 | 1162<BS<=1429 | 57 | 867737<BS<=1067031 |
26 | 1429<BS<=1757 | 58 | 1067031<BS<=1312097 |
27 | 1757<BS<=2161 | 59 | 1312097<BS<=1613447 |
28 | 2161<BS<=2657 | 60 | 1613447<BS<=1984009 |
29 | 2657<BS<=3267 | 61 | 1984009<BS<=2439678 |
30 | 3267<BS<=4017 | 62 | 2439678<BS<=3000000 |
31 | 4017<BS<=4940 | 63 | BS>3000000 |
表3
表4
在本实施例中,当用户终端UE不支持扩展缓冲区时,门限值(T1)的设置可以通过Table 6.1.3.1-1中的缓冲区划分区间确定,如表2所示,例如:以用户终端UE能力级3为例,假设上行只有一个调度UE,每个上行子帧能够调度的最大缓冲区大小为6378字节(Byte),那么在表2中对应的BSR索引为42,缓冲区的大小值区间为5476<BS<=6411,实际环境中上行调度的用户终端UE数不止一个,用户终端UE上报的BSR不能被及时调度,所以应当设置的大容量业务的BSR门限值T1为42索引区间里面的下限,或者在小于42索引的区间内的取值。同理,对于用户终端UE支持扩展缓冲区时,在设置门限值T1时,应该以表3提供的扩展缓冲区的大小划分情况表(即是Table 6.1.3.1-2)为标准进行设置。
可选地,在本实施例中,所述方法还包括:在步骤S101之前,设置用于检测所述用户终端上报大容量业务的检测时间窗;其中,所述次数为所述用户终端在所述检测时间窗内上报大容量业务所发生的次数。可选的,所述检测的大容量业务的次数为同一业务类型下的业务上报的大容量业务次数,当检测到所述上报大容量业务的次数为大于或等于预设的次数时,则判定需要将所述用户终端切换到其他小区,可选的,将所述用户终端切换到其他小区包括:将所述用户终端切换到频分双工小区。
可选地,在本实施例中,所述方法还包括:在根据检测结果判断是否将
所述用户终端切换到其他小区之前,根据当前检测的业务类型设置切换次数阈值,其中,所述切换次数阈值为在所述检测时间窗内预设上报大容量业务的次数N;步骤S102根据检测结果判断是否将所述用户终端切换到其他小区包括:将所述检测的次数与所述切换次数阈值进行比较,若大于等于所述切换次数阈值,则判定需要将所述用户终端切换到其他小区;
或者,所述方法还包括:在根据检测结果判断是否将所述用户终端切换到其他小区之前,根据当前检测的业务类型设置百分比门限值(T5);其中,所述百分比门限值(T5)为在所述检测时间窗内预设上报大容量业务的次数与理论上行子帧数的百分比;步骤S201根据检测结果判断是否将所述用户终端切换到其他小区包括:计算在所述检测时间窗内检测用户终端上报大容量业务的次数与理论上行子帧数的百分比;将计算的百分比与所述百分比门限值(T5)进行比较,若大于等于所述百分比门限值(T5),则判定需要将所述用户终端切换到其他小区。
可选地,在本实施例中,所述方法还包括:在根据检测结果判断是否将所述用户终端切换到其他小区之前,判断所述用户终端为近点用户还是远点用户。可选的,首先设置用于判断所述用户终端为近点用户或者远点用户设置路径损耗阈值(T2);根据所述用户终端当前的路径损耗值与预设的路径损耗阈值的比较,如果用户终端当前的路径损耗值大于预设的路径损耗阈值(T2),则为判定该用户终端为远点用户,否则为近点用户。在本实施例中,设置路径损耗阈值(T2)一般设置为120,该数值并不是固定唯一的,其于对不同的网元环境可进行适当的调整。可选地,在不同的网元环境下对路径损耗值(T2)的调整可以根据协议36.213中提供的计算公式进行计算调整,例如:可以根据用户终端对于近点和远点的发射功率进行计算。
在本实施中,由于近点用户和远点用户,在传输相同大小的数据量所使用的时间不同,近点用户传输的时间相对较短,因此在针对近点用户和远点用户分别设置不同的检测时间窗,所述检测时间窗包括近点检测时间窗和远点检测时间窗,所述近点用户和远点用户分别在对应的检测时间窗内获取用户终端UE上报的BSR次数;如果用户终端为近点用户,则设置在所述近点检测时间窗内进行检测;如果用户终端为远点用户,则设置在所述远点检测
时间窗内进行检测,所述远点检测时间窗大于近点检测时间窗。
在本实施例中,为了能更精准地判断所述用户终端为大容量业务用户,针对于近点用户和远点用户在对应的检测时间窗内设置近点切换次数阈值和近点百分比门限值,远点切换次数阈值和远点百分比门限值。
进一步的,对于检测大容量业务BSR的检测时间窗的设定,也是根据协议规定的不同业务类型和系统TDD的时隙配比共同决定。
如果所述用户终端为近点用户时,通过检测所述用户终端在所述近点检测时间内检测其上报BSR的实际次数,当检测到的实际次数大于等于所述近点切换次数阈值时,则该用户终端为近点大容量业务用户;或者根据检测到的实际次数据算其与理论上行子帧数的百分比,并与所述近点百分比门限值进行比较,若大于等于所述近点百分比门限值,则该用户终端为近点大容量业务用户。
当所述用户终端为远点用户时,通过检测所述用户终端在所述远点检测时间内用户终端上报BSR的次数,当检测到的实际次数大于等于所述远点切换次数阈值时,则该用户终端为远点大容量业务用户;或者根据检测到的实际次数据算其与理论上行子帧数的百分比,并与所述远点百分比门限值进行比较,若大于等于所述远点百分比门限值,则该用户终端为远点大容量业务用户。
在本实施例中,检测获取所述用户终端在所述检测时间窗内上报的大容量业务BSR的次数,可选地,可以通过设置BSR计数器来计数得到,当在所述检测时间窗内检测到所述用户终端有上报大容量业务BSR时,与所述用户终端对应的BSR计数器加1,直到所述检测时间窗结束;当所述检测时间窗结束后,根据所述BSR计数器的数值与理论上行子帧数的百分比判断是否需要将所述用户终端切换到其他小区;在判断完成后将所述BSR计数器清零,等待下一个检测时间窗的到来重新计数;或者直接判断所述BSR计数器的计数值是否达到预设的上报BSR的次数,若达到则判定需要将所述用户终端切换到其他小区,并将是BSR计数器清零,等待下一个检测时间窗的到来重新计数。
在本实施例中,可选地,所述检测时间窗的是根据业务模型的特性来进行设置表5。
如表5所示,为本实施例提供的不同业务模型的特性表,通过分析不同业务模型的特性,给出不同业务的数据量大小,即BSR的大小。以常见的能力级3的终端为例说明,这里的能力级指的是UE能够支持的传输速率的等级;L2最大缓冲区为1400000Byte,每次调度6378Byte,每个TTI(传输时间间隔,transmission time interval,简称TTI)只调度一个用户终端UE,分析得出不同业务模型的理论完成时间,如表6所示,表6为本发明实施例提供的不同业务模型的理论完成时间表。按照BSR周期10毫秒(ms)计算,每2个上行子帧有一个BSR上报,将100ms(也即是TDD配置2中实际用户体验的时长为500ms)作为一个统计周期,每个周期有50次BSR上报,则得出理论检测时间窗长。
表5
表6
根据表6中每个业务类型理论检测时间窗长的分析,可以得出每个业务模型的完成全部数据传输的检测时间窗长,其计算具体为将表6中记载的时间乘以5即可得出,因为表6中的时间是按照TDD上行子帧数计数的。例如:业务编号为2的业务,作为近点用户时只需要0.5s的时间即可全部完成数据的传输,作为中点用户时只需1.5s即可全部传完,作为远点用户在4s内即可全部传完。所以针对业务编号为2的业务,近点用户的近点检测时间窗T3可以设置为0.5秒(s),远点用户的远点检测时间窗T4可以设置为1.5s。
在本实施例中,可选地,在设置所述检测时间窗时,所述远点用户的远点检测时间窗为所述近点用户的近点检测时间窗的整数倍。
实施例二:
图2为本实施例提供的大容量业务用户上行业务识别切换方法的启动流程图,本实施例是在实施例一将所有的参数设置完成的基础上,启动对大容量业务BSR的具体步骤包括:
步骤S201,启动大容量业务的检测开关;
对大容量业务的检测只有在检测开关开启的情况下才会启动,否则不执行大容量业务的检测;
步骤S202,等待检测时间窗的到来;
当检测开关开启之后,并不是立即执行对用户终端上报大容量业务的检测,而是需要继续等待检测时间窗的到来,即大容量业务的检测是周期性进行的;
S203,判断检测时间窗是否到来;如果检测时间窗到来,则执行对上报大容量业务的检测处理,否则不执行处理;
S204,开始执行大容量业务的检测。
根据步骤S203的判断结果,如果检测时间窗到来,并在检测时间窗内,则开始执行对上报大容量业务的检测处理,具体的大容量业务检测处理,如图3所示。
图3为本实施例提供的大容量业务用户上行业务识别切换方法的检测处理流程图,其具体步骤包括:
步骤S301,等待检测时间窗的到来;
步骤S302,判断检测时间窗到来;
在判断检测时间窗到来时,启动对上报大容量业务用户的检测。
步骤S303,检测获取用户终端UE上报的BSR;
在用户终端UE有上行数据传输时,用户终端UE进行周期性的上报BSR。
步骤S304,判断获取到上报的BSR是否为大容量业务BSR;
在本步骤S304中,可以将获取到的上报的BSR与预先设置用户终端UE上行业务传输的门限值T1进行比较,如果获取到的上报的BSR大于门限值T1,则判定为大容量业务BSR,进入步骤S305;否则,如果获取到的上报的BSR小于或等于门限值T1,则返回步骤S303等待下一次获取到上报的BSR再进行判断;
步骤S305,将对应的计算大容量业务BSR的BSR计数器值加1;
步骤S306,判断检测时间窗是否结束;如果检测时间窗结束,则转步骤S307,判断用户终端UE是否为大容量业务用户;否则,如果检测时间窗未结束,则转步骤S303,继续等待UE上报BSR;
步骤S307,判断BSR计数器的计数值是否大于或等于预设的次数N,如果BSR计数器的计数值大于或等于预设的次数N,则对该用户终端UE的最终检测结果为大容量业务用户,转步骤S308;否则,如果BSR计数器的计数值小于预设的次数N就不是大容量业务用户,则转步骤S301;
或者,计算BSR计数器的计数值与理论上行子帧数的百分比,并判断该计算的百分比是否大于预设的门限值(T5);如果大于或等于预设的门限值(T5),则对该用户终端UE的最终检测结果为大容量业务用户,转步骤S308;否则,如果小于预设的门限值(T5),该用户终端UE就不是大容量业务用户,则转步骤S301;
步骤S308,判断检测结果为大容量业务用户并上报该用户终端的信息;
步骤S309,根据上报的用户终端的信息对该用户终端进行切换处理,切换到其他小区。
在本实施例中,对于远点大容量业务用户的检测周期和检测时间窗的设置如图4,对于近点大容量业务用户的检测周期和检测时间窗的设置如图5所示,
图4为本实施例提供的远点用户检测时间窗的示意图,根据配置周期t1~t3为一个检测周期,在这个检测周期内,t1~t2为大容量业务检测的检测时间窗,当检测t1时刻到来时,开始执行对上报大容量业务的检测,并调整计数上报大容量业务的BSR计数器的计数值,直到t2时刻到达,检测停止,根据上述图3中的步骤S307判断该用户终端UE是否为大容量业务用户,在步骤S307判断为大容量业务用户时,执行步骤S308,进行上报处理。
图5为本实施例提供的近点用户检测时间窗示意图,根据配置周期t1~t3为一个检测周期,在这个检测周期内,t1~t6,t6~t2分别为大容量业务的检测时间窗,即t1~t6窗内会检测出是否为大容量业务的结果,但这时候由于远点用户的检测时间窗还未结束,所以这时候不会上报近点用户的检测结果,等待下一个检测时间窗t6~t2的检测结果,等到t2时刻到来之后再进行判断该用户终端是否为大容量用户并上报处理。
在本实施例中,每个小区都会存在远点用户和近点用户,对于上报的大容量业务的检测以小区为单位进行处理,所有的用户终端都是在同一时间将检测结果进行上报处理。传输相同大小的数据,远点用户所需的时间要长一些,因此上报时间点就是远点用户的检测时间窗结束时间,这也要求远点用户的检测时间窗长度要设置为近点用户的检测时间窗的整数倍。
实施例三:
本实施例提供了一种上行业务识别切换装置,如图6所示,在本实施例中,所述装置包括:检测模块11、判断模块12;
所述检测模块11,设置为检测用户终端上报大容量业务的次数;
所述判断模块12,设置为根据所述检测模块11检测的结果判断是否将所述用户终端切换到其他小区。
可选地,在本实施例中,所述上行业务识别切换装置,还包括:设置模块13,设置为设置用于检测所述用户终端上报大容量业务的检测时间窗;其中,所述检测模块11检测的次数为所述用户终端上报大容量业务所发生的次数。可选地,所述检测模块11是设置为检测检测用户终端同一业务类型下的业务上报大容量业务的次数。
可选地,在本实施例中,所述设置模块13,还设置为根据当前检测的业务类型设置切换次数阈值,其中,所述切换次数阈值为在所述检测时间窗内预设上报大容量业务的次数;
所述判断模块12包括第一判断子模块121;
所述第一判断子模块121,设置为将所述检测模块检测到的次数与所述设置模块设置的切换次数阈值进行比较,若所述检测模块检测到的次数大于或等于所述切换次数阈值,则判定需要将所述用户终端切换到其他小区。
可选地,在本实施例中,所述设置模块13,还设置为根据当前检测的业务类型设置百分比门限值;其中,所述百分比门限值为在所述检测时间窗内预设上报大容量业务的次数与理论上行子帧数的百分比;
所述判断模块12包括第二判断子模块122;
所述第二判断子模块122,设置为计算在所述检测时间窗内检测所述用户终端上报大容量业务的次数与理论上行子帧数的百分比;将计算的百分比与所述百分比门限值进行比较,若计算的百分比大于或等于所述百分比门限值,则判定需要将所述用户终端切换到其他小区。
可选地,在本实施例中,所述装置还包括:切换模块14,所述切换模块14包括频分双工切换子模块141,设置为将所述用户终端从时分双工模式小区切换到频分双工模式小区。
可选地,在本实施例中,在切换模块14将用户终端切换到其他小区之前,还可以将用户终端进行近点用户和远点用的分类,通过设置路径损耗阈值来实现分类;根据所述用户终端当前的路径损耗值与预设的路径损耗阈值的比较,如果终端用户当前的路径损耗值大于预设的路径损耗阈值,则为判定该用户终端为远点用户,否则为近点用户。
采用本实施例的上行业务识别装置,可以实现每个小区在通信信道资源出现紧张时,对大容量业务用户的调度,减轻小区的负荷。可选地,所述检测模块11通过检测所述用户终端在设定的检测时间窗内上报的BSR的次数,所述判断模块12根据所述检测模块11检测的结果判断所述上报的BSR是否是大容量业务BSR,若是,则将所述BSR计数器加1;当检测时间窗结束后,由上所述判断模块12判断所述BSR计数器的计数值是否达到切换次数阈值,若达到,则判定所述用户终端为大容量业务用户,否则不是大容量业务用户;或者通过所述计算子模块计算所述BSR计数器的计数值与理论上行子帧数的百分比,再将所述计算的百分比与百分比门限值T5的大小进行比较,若大于或等于,则判定所述用户终端为大容量业务用户,并将BSR计数器清零,等待下一检测时间窗重新计数;最后上报所述用户终端的信息,所述切换模块14根据上报的信息将对应的用户终端切换到其他小区。
在本发明实施例中,还提供了一种基站,所述基站包括上述实施例的任一上行业务识别切换装置,所述基站检测用户终端上报大容量业务的次数,并根据结果判断是否将该用户终端切换到其他小区。可选地,所述基站在设定的检测时间窗内获取用户终端上报的BSR,根据所述BSR判断为大容量业务BSR,如果是大容量业务BSR,则将BSR计数器加1;当检测时间窗结束后,计算所述BSR计数器的计数值与理论上行子帧数的百分比,并根据该百分比判断所述用户终端是否为大容量业务用户,如果是,则将所述用户终端切换到其他小区。
通过采用本发明实施例提供的上行业务识别切换方法及装置、基站,实现了相邻小区之间的用户终端的切换调度,实现了小区在资源出现不够用或者紧张、负荷较大的情况下,每个小区的资源可以相互共享的,进一步的提高的小区用户终端的体验度,提高了资源的利用率。
显然,本领域的技术人员应该明白,上述本发明的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储介质(ROM/RAM、磁碟、光盘)中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。所以,本发明不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本申请所作的进一步详细说明,不能认定本申请的具体实施只局限于这些说明。对于本申请所属技术领域的普通技术人员来说,在不脱离本申请构思的前提下,还可以做出若干简单推演或替换,都应当视为属于本申请的保护范围。本发明实施例还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机可执行指令,所述计算机可执行指令被执行时实现上行业务识别切换方法。
上述技术方案可以减轻该小区的负荷,提高用户终端的体验度,同时也提高了小区的资源利用率。
Claims (13)
- 一种上行业务识别切换方法,包括:检测用户终端上报大容量业务的次数;根据检测结果判断是否将所述用户终端切换到其他小区。
- 如权利要求1所述的上行业务识别切换方法,所述方法还包括:在检测用户终端上报大容量业务的次数之前,设置用于检测所述用户终端上报大容量业务的检测时间窗;其中,所述次数为所述用户终端在所述检测时间窗内上报大容量业务所发生的次数。
- 如权利要求2所述的上行业务识别切换方法,其中:根据检测结果判断是否将所述用户终端切换到其他小区包括:当所述上报大容量业务的次数大于或等于预设的次数时,则判定需要将所述用户终端切换到其他小区。
- 如权利要求2所述的上行业务识别切换方法,其中:所述检测用户终端上报大容量业务的次数包括:检测用户终端同一业务类型下的业务上报大容量业务的次数。
- 如权利要求4所述的上行业务识别切换方法,所述方法还包括:在根据检测结果判断是否将所述用户终端切换到其他小区之前,根据当前检测的业务类型设置切换次数阈值,其中,所述切换次数阈值为在所述检测时间窗内预设上报大容量业务的次数;所述根据检测结果判断是否将所述用户终端切换到其他小区包括:将检测到的次数与所述切换次数阈值进行比较,若所述检测到的次数大于或等于所述切换次数阈值,则判定需要将所述用户终端切换到其他小区;或者,所述方法还包括:在根据检测结果判断是否将所述用户终端切换到其他小区之前,根据当前检测的业务类型设置百分比门限值;其中,所述百分比门限值为在所述检测时间窗内预设上报大容量业务的次数与理论上行子帧数的百分比;所述根据检测结果判断是否将所述用户终端切换到其他小 区包括:计算在所述检测时间窗内检测所述用户终端上报大容量业务的次数与理论上行子帧数的百分比;将计算的百分比与所述百分比门限值进行比较,若大于或等于所述百分比门限值,则判定需要将所述用户终端切换到其他小区。
- 如权利要求5所述的上行业务识别切换方法,其中:所述设置用于检测所述用户终端上报大容量业务的检测时间窗具体包括:如果所述用户终端为近点用户,则设置所述检测时间窗为近点检测时间窗,其中,所述切换次数阈值为近点切换次数阈值,所述百分比门限值为近点百分比门限值;如果所述用户终端为远点用户,则设置所述检测时间窗为大于所述近点检测时间窗的远点检测时间窗,其中,所述切换次数阈值为远点切换次数阈值,所述百分比门限值为远点百分比门限值。
- 如权利要求1-6任一项所述的上行业务识别切换方法,所述方法还包括:在判断将所述用户终端切换到其他小区时,将所述用户终端切换到其他小区;其中,所述将所述用户终端切换到其他小区包括:将所述用户终端切换到频分双工模式小区。
- 一种上行业务识别切换装置,包括:检测模块,设置为检测用户终端上报大容量业务的次数;判断模块,设置为根据所述检测模块检测的结果判断是否将所述用户终端切换到其他小区。
- 如权利要求8所述的上行业务识别切换装置,装置还包括:设置模块,设置为设置用于检测所述用户终端上报大容量业务的检测时间窗;其中,所述检测模块检测的次数为所述用户终端在所述检测时间窗内上报大容量业务所发生的次数;所述检测模块,是设置为检测用户终端同一业务类型下的业务上报大容量业务的次数。
- 如权利要求9所述的上行业务识别切换装置,其中:所述设置模块,还设置为根据当前检测的业务类型设置切换次数阈值,其中,所述切换次数阈值为在所述检测时间窗内预设上报大容量业务的次数;所述判断模块包括第一判断子模块;所述第一判断子模块,设置为将所述检测模块检测到的次数与所述设置模块设置的切换次数阈值进行比较,若所述检测模块检测到的次数大于或等于所述切换次数阈值,则判定需要将所述用户终端切换到其他小区。
- 如权利要求9所述的上行业务识别切换装置,其中:所述设置模块,还设置为根据当前检测的业务类型设置百分比门限值;其中,所述百分比门限值为在所述检测时间窗内预设上报大容量业务的次数与理论上行子帧数的百分比;所述判断模块包括第二判断子模块;所述第二判断子模块,设置为计算在所述检测时间窗内检测所述用户终端上报大容量业务的次数与理论上行子帧数的百分比;将计算的百分比与所述百分比门限值进行比较,若计算的百分比大于或等于所述百分比门限值,则判定需要将所述用户终端切换到其他小区。
- 如权利要求8-11任一项所述的上行业务识别切换装置,所述装置还包括切换模块,所述切换模块包括频分双工切换子模块;所述频分双工切换子模块,设置为将所述用户终端切换到频分双工模式小区。
- 一种基站,包括:如权利要求8-12任一项所述的上行业务识别切换装置。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510817568.7A CN106792927B (zh) | 2015-11-23 | 2015-11-23 | 一种上行业务识别切换方法及装置、基站 |
CN201510817568.7 | 2015-11-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017088520A1 true WO2017088520A1 (zh) | 2017-06-01 |
Family
ID=58762970
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/093614 WO2017088520A1 (zh) | 2015-11-23 | 2016-08-05 | 一种上行业务识别切换方法及装置、基站 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN106792927B (zh) |
WO (1) | WO2017088520A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113225765A (zh) * | 2020-01-21 | 2021-08-06 | 大唐移动通信设备有限公司 | 一种双连接主路径切换方法及装置 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109121165B (zh) * | 2017-06-23 | 2021-09-21 | 中国移动通信集团广东有限公司 | 基于上行大包业务的负载均衡处理方法及装置 |
CN111479288B (zh) * | 2019-01-23 | 2022-04-05 | 大唐移动通信设备有限公司 | 一种小区切换方法及系统 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1447535A (zh) * | 2002-03-26 | 2003-10-08 | 株式会社Ntt都科摩 | 复合无线通信系统控制装置 |
CN102905387A (zh) * | 2011-07-25 | 2013-01-30 | 中兴通讯股份有限公司 | 随机接入方法及用户设备 |
CN103517298A (zh) * | 2012-06-27 | 2014-01-15 | 中国电信股份有限公司 | 用于无线中继网络的切换测量方法、系统及中继节点 |
CN103974338A (zh) * | 2013-02-01 | 2014-08-06 | 华为技术有限公司 | 数据传输的方法、用户设备及基站 |
WO2015108714A1 (en) * | 2014-01-15 | 2015-07-23 | Qualcomm Incorporated | Intra and inter-frequency handover in lte with uplink and downlink weighted metrics |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101115287A (zh) * | 2006-07-26 | 2008-01-30 | 华为技术有限公司 | 通信方法及系统、数据传输方法及系统、以及通信方式结合方法及系统 |
CN101217775B (zh) * | 2007-01-04 | 2012-04-25 | 华为技术有限公司 | 上报上行业务量的方法、中间节点、信道切换方法与系统 |
GB0702169D0 (en) * | 2007-02-05 | 2007-03-14 | Nec Corp | Resource Allocation |
KR20110113484A (ko) * | 2010-04-09 | 2011-10-17 | 주식회사 팬택 | 다중 반송파 시스템에서 랜덤 액세스의 수행장치 및 방법 |
CN102264111A (zh) * | 2010-05-24 | 2011-11-30 | 华为技术有限公司 | 一种载波汇聚下的小区间切换方法及基站 |
US20150045029A1 (en) * | 2012-03-19 | 2015-02-12 | Nokia Corporation | Method and Apparatus Providing Data Offloading and Carrier Aggregation Associated Measurement Reporting |
CN103906160B (zh) * | 2012-12-25 | 2017-12-12 | 中国电信股份有限公司 | 接入网切换控制方法和系统 |
CN103916222A (zh) * | 2014-03-14 | 2014-07-09 | 电信科学技术研究院 | 一种上行业务发送方式调整方法及设备 |
-
2015
- 2015-11-23 CN CN201510817568.7A patent/CN106792927B/zh active Active
-
2016
- 2016-08-05 WO PCT/CN2016/093614 patent/WO2017088520A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1447535A (zh) * | 2002-03-26 | 2003-10-08 | 株式会社Ntt都科摩 | 复合无线通信系统控制装置 |
CN102905387A (zh) * | 2011-07-25 | 2013-01-30 | 中兴通讯股份有限公司 | 随机接入方法及用户设备 |
CN103517298A (zh) * | 2012-06-27 | 2014-01-15 | 中国电信股份有限公司 | 用于无线中继网络的切换测量方法、系统及中继节点 |
CN103974338A (zh) * | 2013-02-01 | 2014-08-06 | 华为技术有限公司 | 数据传输的方法、用户设备及基站 |
WO2015108714A1 (en) * | 2014-01-15 | 2015-07-23 | Qualcomm Incorporated | Intra and inter-frequency handover in lte with uplink and downlink weighted metrics |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113225765A (zh) * | 2020-01-21 | 2021-08-06 | 大唐移动通信设备有限公司 | 一种双连接主路径切换方法及装置 |
CN113225765B (zh) * | 2020-01-21 | 2022-04-01 | 大唐移动通信设备有限公司 | 一种双连接主路径切换方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
CN106792927B (zh) | 2021-06-25 |
CN106792927A (zh) | 2017-05-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10575320B2 (en) | Data transmission method and device | |
US20220116959A1 (en) | Method and apparatus for triggering a sidelink scheduling request and system | |
US20170064688A1 (en) | Method for Transmitting Control Information | |
EP3136805B1 (en) | Method and apparatus for retrieving transmit opportunity control in reverse direction grant | |
JP2019083577A (ja) | サイクリック・プレフィックスの長さを設定するためのシステムおよび方法 | |
US11736979B2 (en) | Data packet transmission method and apparatus to address a high-latency caused when data is to be transmitted using an unlicensed frequency band | |
CN109963308B (zh) | 无线通信系统中的资源调度方法及装置 | |
US10108457B2 (en) | Method and system for wireless communication baseband processing | |
Carrascosa et al. | An experimental study of latency for IEEE 802.11 be multi-link operation | |
US10560979B2 (en) | Measurement result reporting method, method for counting by timer, apparatus, and user equipment | |
US20200389910A1 (en) | Scheduling-free transmission method and apparatus | |
EP2712228A1 (en) | Method, equipment and system for coordinated multi-point transmission/reception | |
WO2017088520A1 (zh) | 一种上行业务识别切换方法及装置、基站 | |
US20160212794A1 (en) | Radio Base Station and Method Therein | |
US20200187234A1 (en) | Method and system for processing scheduling requests | |
KR20220006635A (ko) | 업링크 전송을 위한 방법, 단말 장치 및 네트워크 노드 | |
WO2012051878A1 (zh) | 一种协同传输的调度方法及系统 | |
Gachhadar et al. | Traffic Offloading in 5G Heterogeneous Networks using Rank based Network Selection. | |
Larroca et al. | An overview of WLAN performance, some important case-scenarios and their associated models | |
US8526307B2 (en) | Proportional-fair radio resource management | |
CN116783858A (zh) | 控制上行链路中的短控制信令(scs) | |
CN102006109B (zh) | 采用虚拟天线映射方式进行发射的方法及系统 | |
EP3211952B1 (en) | Joint interference rejection method and device, and method and device for realizing uplink comp | |
CN105264850B (zh) | 触发功率余量报告的方法、终端和系统 | |
CN111741452A (zh) | 一种NB-IoT基站剩余容量预测的方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16867747 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16867747 Country of ref document: EP Kind code of ref document: A1 |