WO2020098730A1 - 用户设备迁移方法、集中单元、分布单元及*** - Google Patents

用户设备迁移方法、集中单元、分布单元及*** Download PDF

Info

Publication number
WO2020098730A1
WO2020098730A1 PCT/CN2019/118325 CN2019118325W WO2020098730A1 WO 2020098730 A1 WO2020098730 A1 WO 2020098730A1 CN 2019118325 W CN2019118325 W CN 2019118325W WO 2020098730 A1 WO2020098730 A1 WO 2020098730A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
load
migration
list
migrated
Prior art date
Application number
PCT/CN2019/118325
Other languages
English (en)
French (fr)
Inventor
田路晓
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020098730A1 publication Critical patent/WO2020098730A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • 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

Definitions

  • This application relates to the communication field, for example, to a user equipment migration method, centralized unit, distributed unit, and system.
  • the 5rd Generation mobile communication system (the 5rd Generation mobile communication system, 5G) has come into people's eyes.
  • 5G Radio Access Network (RAN) architecture the 3rd Generation Partnership Project (3GPP) passed the Central Unit / Distributed Unit (CU / DU) architecture solution .
  • CU mainly deals with non-real-time wireless high-level protocol stack functions
  • DU mainly deals with physical layer functions and layer 2 functions required for real-time performance.
  • CU and DU complete signaling and data transmission through the F1 interface.
  • CU and DU are separated, the realization of some conventional business functions becomes complicated.
  • load balancing function Take the load balancing function as an example.
  • UE User Equipment
  • PRB physical resource block
  • Modulation modulation coding order
  • MCS Coding Scheme
  • UE air separation information are generally important reference indicators.
  • the DU because of functional division, only the DU knows the PRB, MCS, and space division information of each UE. Only the CU knows the load of the neighboring cell, and the UE's migration process is also controlled by the CU.
  • the DU needs to report the PRB occupancy, MCS, and space division information of each UE to the CU through the F1 interface. Because there are a large number of DUs under the CU, there are multiple cells under each DU, and there are thousands of users under each cell. If the DU reports this information to the CU, the amount of messages is large. In particular, the number of PRBs occupied by users, MCS, and air separation status will change from time to time, so it is possible that the DU may report this information to the CU multiple times. Because the amount of reported information is too large, it puts extra pressure on the F1 interface, which may affect normal services.
  • Embodiments of the present application provide a user equipment migration method, centralized unit, distribution unit, and system, so as to at least solve the problem of UE migration in the related art.
  • An embodiment of the present application provides a user equipment migration method, which includes: a CU receives a migrated UE list sent by a DU; and the CU performs neighbor cell migration on a UE in the migrated UE list.
  • the CU receiving the migrated UE list sent by the DU includes: the CU receives the migrated UE list indication message sent by the DU, wherein the migrated UE list indication message carries the migrated UE list and the migration reason value.
  • the CU performing neighbor cell migration on the UE in the migrated UE list includes: the CU acquiring the low-load neighbor cell or high priority of the first cell to which the UE in the migrated UE list belongs Neighboring cell, wherein the low-load neighboring cell is a neighboring cell with a load lower than a preset threshold or a neighboring cell with a load ratio lower than a preset threshold, and the high-priority neighboring cell has a priority higher than a preset priority Neighboring cell; the CU migrates the UE in the migrated UE list to the low-load neighboring cell or the high-priority neighboring cell according to the configured migration switching strategy.
  • the CU migrates the UEs in the migrated UE list to the low-load neighbor cell or the high-priority neighbor cell according to the configured migration handover strategy, including one of the following:
  • the migration handover strategy is In the case of blind handover, the CU issues a handover instruction to a UE in the migrated UE list to switch the UE to the low-load neighbor cell or the high-priority neighbor cell, where the handover command Carries low-load neighbor information or high-priority neighbor information; when the migration switching strategy is redirection, the CU issues a redirection instruction to the UE in the migrated UE list to reset the UE Directed to the low-load neighboring zone or the high-priority neighboring zone, wherein the redirection instruction carries the frequency information of the low-load neighboring zone or the high-priority neighboring zone; In the case of measurement-based handover, the CU issues a measurement instruction for neighboring cells to the UE in the migrated UE list, and switches the
  • the method before the CU receives the migrated UE list sent by the DU, the method further includes: the CU collects the load of all neighboring cells of the first cell, and according to the load of all neighboring cells, A low-load neighbor cell of the first cell is selected from the cell; wherein, the first cell is a cell to be migrated by the UE notified by the DU, and the low-load neighbor cell is a neighbor whose load is lower than a preset threshold The CU notifies the DU of the frequency information of the low-load neighboring cell.
  • the CU collects the load of all neighboring cells of the first cell, including at least one of the following: the CU sends a resource collection request to the neighboring cell of the first cell, and receives the cell load reported by the neighboring cell Report; the CU sends a resource collection request to the DU and receives the cell load report reported by the DU; the CU sends a resource collection request to other CUs and receives the cell load report reported by the other CU.
  • the resource collection request includes at least one of the following: the identifier of the neighboring area where the load needs to be collected, the type of load that needs to be collected, the load reporting method, and the load reporting period.
  • An embodiment of the present application further provides a user equipment migration method, including: a DU monitoring the status of a UE in a first cell, and adding a UE in the first cell that meets the migration policy to the list of migrated UEs; The CU sends the migrated UE list.
  • the eviction strategy includes at least one of the following: UEs whose physical resource block PRB occupancy rate exceeds a set threshold; UEs whose packet error rate exceeds a set threshold; UEs that do not include a specified service; resources cannot satisfy the service UE with required quality of service QoS; UE with lower priority than the set priority.
  • the method before the DU monitors the status of the UE in the first cell and adds the UE in the first cell that meets the migration policy to the list of migrated UEs, the method further includes: the DU monitoring the DU The load situation of multiple cells notifies the CU of the first cell to be migrated by the UE, where the first cell is a cell whose load is higher than a first preset threshold.
  • notifying the CU of the first cell to be migrated by the UE includes: when the DU satisfies the trigger condition, the DU sends a load indication message to the CU to migrate the pending UE
  • the first cell notifies the CU, wherein the trigger condition includes at least one of the following: a newly added high-load cell is found, and a load change that has been reported to the high-load cell has reached a second preset threshold.
  • the load indication message includes at least one of the following: a cell identification ID, a cell load status, a cell uplink residual load, and a cell downlink residual load.
  • adding the UE that conforms to the migration policy in the first cell to the migrated UE list includes the DU adding the migration that conforms to the migration policy in the first cell and supporting migration to a low-load neighbor cell
  • the UE of at least one frequency point is added to the list of migrated UEs, wherein the low-load neighbor cell is a neighbor cell of all the neighbor cells of the first cell indicated by the CU whose load is lower than a third preset threshold .
  • An embodiment of the present application further provides a centralized unit CU, including: a receiving module configured to receive a migration UE list sent by a distribution unit DU; a migration module configured to perform neighbor cell migration on the UEs in the migrated UE list.
  • the receiving module is configured to receive a migration UE list indication message sent by a DU, where the migration UE list indication message carries a migration UE list and a migration reason value.
  • the migration module includes: an acquisition unit configured to acquire a low-load neighbor cell or a high-priority neighbor cell of the first cell to which the UE in the migrated UE list belongs, wherein the low-load neighbor cell Is a neighboring cell with a load lower than a preset threshold or a neighboring cell with a load ratio lower than a preset threshold, the high-priority neighboring cell is a neighboring cell with a priority higher than the preset priority; the migration unit is set to The migration switching strategy migrates the UEs in the migrated UE list to the low-load neighbor cell or the high priority neighbor cell.
  • the migration unit is configured to migrate UEs in the migrated UE list to the low-load neighboring zone or high-priority neighboring zone according to the configured migration switching strategy in one of the following ways: during migration switching When the strategy is blind handover, a handover instruction is issued to the UE in the migrated UE list to switch the UE to the low-load neighbor cell or the high-priority neighbor cell, wherein, in the handover command Carries low-load neighbor information or high-priority neighbor information; when the migration switching strategy is redirection, a redirection instruction is issued to the UE in the migrated UE list to redirect the UE to the A low-load neighboring cell or the high-priority neighboring cell, wherein the redirection instruction carries the frequency information of the low-load neighboring cell or the high-priority neighboring cell; the migration switching strategy is based on measurement In the case of handover, a measurement instruction for a neighbor cell is issued to the UE in the migrated UE list, and according to the
  • the migration module further includes: a collection unit configured to collect the loads of all neighboring cells of the first cell, and filter out the first neighboring cells according to the loads of all neighboring cells A low-load neighboring cell of a cell, notifying the DU of frequency information of the low-load neighboring cell, wherein the first cell is a cell to be relocated by the UE notified by the DU, and the low-load neighboring cell It is the neighboring area where the load is lower than the preset threshold.
  • a collection unit configured to collect the loads of all neighboring cells of the first cell, and filter out the first neighboring cells according to the loads of all neighboring cells A low-load neighboring cell of a cell, notifying the DU of frequency information of the low-load neighboring cell, wherein the first cell is a cell to be relocated by the UE notified by the DU, and the low-load neighboring cell It is the neighboring area where the load is lower than the preset threshold.
  • An embodiment of the present application further provides a distribution unit DU, including: a monitoring module configured to monitor the status of the UE in the first cell, and add the UE in the first cell that meets the migration policy to the list of migrated UEs; send The module is configured to send the migrated UE list to the centralized unit CU.
  • a monitoring module configured to monitor the status of the UE in the first cell, and add the UE in the first cell that meets the migration policy to the list of migrated UEs; send The module is configured to send the migrated UE list to the centralized unit CU.
  • the eviction strategy includes at least one of the following: UEs with PRB occupancy rate exceeding the set threshold; UEs with packet error rate exceeding the set threshold; UEs without specified service; resources that cannot meet the QoS requirements of the service UE; the priority is lower than the set priority UE.
  • the monitoring module is further configured to monitor the load of multiple cells under the DU and notify the CU of the first cell to be migrated by the UE, where the first cell is the load Cells above the first preset threshold.
  • the monitoring module is configured to notify the CU of the first cell to be migrated by the UE in the following manner: when a trigger condition is met, a load indication message is sent to the CU to notify The first cell notifies the CU, wherein the trigger condition includes at least one of the following: a newly added high-load cell is found, and a load change that has been reported to the high-load cell has reached a second preset threshold.
  • the load indication message includes at least one of the following: cell ID, cell load status, cell uplink residual load, and cell downlink residual load.
  • the monitoring module is configured to add UEs in the first cell that comply with the migration policy to the list of migrated UEs by adding the UEs in the first cell that conform to the migration policy and supporting migration to low A UE with at least one frequency point of a load neighboring cell is added to the list of migrated UEs, wherein the low load neighboring cell is the load indicated by the CU in all neighboring cells of the first cell that is lower than a third preset threshold Neighborhood.
  • a user equipment migration system including a centralized unit CU and a distributed unit DU in any embodiment of the present application.
  • FIG. 1 is a schematic diagram of a CU / DU architecture of a 5G base station provided by an embodiment of the present application;
  • FIG. 2 is a flowchart of a user equipment migration method provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a DU-triggered UE migration method provided by an embodiment of the present application.
  • FIG. 4 is a flowchart of a UE migration method for CU indicating low-load frequency information provided by an embodiment of the present application
  • FIG. 5 is a flowchart of another UE migration method provided by an embodiment of the present application.
  • FIG. 6 is a flowchart of another UE migration method provided by an embodiment of the present application.
  • FIG. 7 is a flowchart of another UE migration method provided by an embodiment of the present application.
  • FIG. 8 is a flowchart of another UE migration method provided by an embodiment of the present application.
  • FIG. 9 is a flowchart of a cell load collection method provided by an embodiment of the present application.
  • FIG. 10 is a structural block diagram of a centralized unit CU provided by an embodiment of the present application.
  • FIG. 11 is a structural block diagram of a distribution unit DU provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of the CU / DU architecture of a 5G base station.
  • the 5G base station may include one or more CUs (only CU1 and CU2 are shown in FIG. 1), and the CUs are connected through an Xn interface.
  • Each CU is connected to one or more DUs (for example, DU1 to DUn) to which it belongs through an F1 interface.
  • the structure shown in FIG. 1 is only an illustration, which does not limit the CU / DU architecture of the 5G base station described above.
  • FIG. 2 is a flowchart of a user equipment migration method according to an embodiment of the present application. As shown in FIG. 2, the process includes the following steps:
  • step S202 the CU receives the migrated UE list sent by the DU.
  • Step S204 the CU performs neighbor cell migration on the UE in the migrated UE list.
  • the DU may set the UE migration policy, and the migration policy may be set according to actual needs.
  • the migration policy may include but not limited to the following strategies and combinations of strategies:
  • the DU receives a message from the CU that the selected UE should support migration to at least one frequency specified by the CU.
  • the DU is responsible for selecting the migrated UE list according to the strategy, and the CU is responsible for migrating the UE selected by the DU to a suitable neighboring cell.
  • the DU can independently select the UE to migrate according to the scheduling strategy, which can satisfy multiple scheduling strategies Reason for UE migration.
  • the number of migrated UEs selected by the DU is relatively small.
  • the DU only reports these UEs that meet the conditions to the CU, and the CU controls the migration process. Avoiding the DU reporting a large amount of UE scheduling related information to the CU can greatly reduce the amount of information exchanged through F1, greatly reduce the load on the F1 port, and achieve load balancing without increasing the pressure on the F1 interface.
  • An embodiment of the present application also provides a DU-triggered UE migration method. As shown in FIG. 3, the method includes the following steps:
  • step S3010 after learning the migration policy or principle, the DU monitors the status of all UEs in the cell in real time, and identifies UEs that meet the migration policy as a UE list.
  • step S3020 the DU sends the UE list composed of UEs to be migrated to the CU through the F1 message "DU migration UE list indication" message, and the message includes the migrated UE list.
  • step S3030 after receiving the message, the CU will process according to the pre-set strategy according to the migrated UE list in the message, including but not limited to blind handover, measurement-based handover, and redirection.
  • the operation of each UE in the UE migration list carried in the "DU migration UE list indication" message is as follows:
  • the configured strategy is blind handover, a handover command is directly issued to the UE (the handover command has low-load neighbor information or high-priority neighbor information). If the configured strategy is redirection, a redirection instruction is directly issued to the UE (the instruction has information such as the frequency of a low-load neighbor or the frequency of a high-priority neighbor). If the configured strategy is based on measurement handover, then for each UE's measurement instruction for the neighboring cell, when the UE reports the measurement report, indicating that the signal of the neighboring cell is strong enough, the UE may be sent to the neighboring cell indicated by the measurement report instruction.
  • the CU migrates the UE in the migrated UE list indicated by the "DU migrated UE list indication" message to a low-load neighbor cell or a high priority neighbor cell according to the configured strategy.
  • the migration is completed through the redirection or switching process specified in the standard agreement.
  • An embodiment of the present application also provides a UE migration method in which the CU indicates low-load frequency information.
  • UE migration in a specific scenario of load balancing is used as an example.
  • the CU in order to ensure that the UE selected by the DU can migrate to a suitable neighbor cell as much as possible, the CU can notify the DU of the frequency information of the neighbor cell through the F1 interface.
  • the frequency information of the neighbor cell is used as a reference for the DU to select the UE to migrate to One of the factors is to ensure that the selected UE list supports migration to these frequencies.
  • the CU may not always collect neighbor load information. When the DU needs to actively migrate services, it can notify the CU to collect neighbor load through the F1 interface in advance.
  • the UE migration method provided in this implementation includes the following steps:
  • Step S4010 the DU sends a "DU load indication" message to the CU. If the message is initiated by the DU, it indicates to the CU that the load status of the cell under the DU has changed (for example, the load changes from low to high or the load changes from high to low) to facilitate the CU to trigger Reasonable load balancing behavior. For example, when the load changes from low to high, the CU can collect the neighbor cell load of the cell, find the low load neighbor cell, and migrate some of the services under the high load cell to the low load neighbor cell; if the load changes from high to low, the CU can stop Collect the load of the neighboring area.
  • the message is initiated by the DU, it indicates to the CU that the load status of the cell under the DU has changed (for example, the load changes from low to high or the load changes from high to low) to facilitate the CU to trigger Reasonable load balancing behavior. For example, when the load changes from low to high, the CU can collect the neighbor cell load of the cell, find the low
  • the content of the message may include a cell identifier (ID), cell load status (high, medium, and low), cell uplink residual load, cell downlink residual load, and so on.
  • ID cell identifier
  • cell load status high, medium, and low
  • cell uplink residual load cell downlink residual load
  • the DU monitors the load of multiple cells under its own name in real time, and determines whether it is a high-load cell in time according to a preset threshold obtained from the background.
  • the DU finds that there are one or more high-load cells, it notifies the CU through the "DU Load Indication" message.
  • This message is only triggered (including but not limited to): Discover new high-load cells (according to the preset threshold) Judgment); the high-load cell that has been reported becomes a low-load cell (judgment according to a preset threshold); the high-load cell that has been reported becomes a higher-load cell (judgment according to a preset threshold).
  • Step S4020 after receiving the "DU load indication" message, the CU will perform load balancing preparation work, including: 1) recording the high-load cells reported by the DU; 2) for each high-load cell, the CU obtains the load of all its neighboring cells , And can filter out low-load neighbors according to the preset threshold.
  • step S4030 the CU sends the acquired information such as the frequency point of the low-load neighboring cell of the high-load cell to the corresponding DU through the "CU low-load neighboring cell frequency information indication" message to assist the DU in choosing to migrate the UE.
  • Step S4040 after acquiring the "CU low-load neighbor frequency information indication" message, the DU selects to migrate the UE according to the set strategy and low-load frequency information.
  • step S4050 the DU sends the UE list to be migrated to the CU through the F1 message "DU migration UE list indication" message, and the message includes the migrated UE list.
  • This step may be the same as step S302 in the embodiment of FIG. 3, and details are not described here.
  • step S4060 after receiving the message, the CU will migrate the UEs in the migrated UE list using a preset strategy according to the migrated UE list in the message, including but not limited to blind handover, measurement-based handover, and redirection.
  • This step may be the same as step S303 in the embodiment of FIG. 3, and details are not described here.
  • Embodiment 1 of the present application provides a UE migration method.
  • CU1-> DU1-> Cell_1 represents the Cell_1 cell of DU1 under CU1, and the relationship between other cells and DUs and CUs can be deduced by analogy, which is not enumerated here.
  • the following conditions are preset:
  • the cell Cell_1 is configured with a high load threshold such that the PRB occupancy rate reaches 80% of the available resources of the cell.
  • the cell Cell_1 configures a UE migration out selection strategy to select a UE whose PRB occupancy rate exceeds 5%.
  • the cell Cell_1 has two neighboring cells, which are:
  • the UE migration method in this embodiment includes the following steps:
  • step S5010 DU1 detects that the PRB occupancy rate of the cell Cell_1 exceeds 80%.
  • Step S5020 DU1 starts to screen UEs to be migrated in the cell Cell_1.
  • the set condition 2) only UE0 and UE1 meet the migration conditions, so DU1 selects UE0 and UE1 to send to CU1, and requests CU1 to migrate UE0 and UE1. High load.
  • Step S5030 after receiving the relocation request, CU1 finds that the reason for the relocation is high cell load, and the cell Cell_1 has a low-load neighbor Cell_M, then CU1 initiates a migration process to the neighbor cell Cell_M for UE0 and UE1 respectively. Direct switching, measurement switching, redirection, etc.
  • Step S5040 after receiving the relocation instruction, UE0 and UE1 relocate to the cell CU1-> DUn-> Cell_M indicated by the relocation instruction.
  • the DU triggers the migration of the UE.
  • the following conditions are preset:
  • CU1-> DU1-> Cell_1 configures a scheduling strategy to migrate UEs: within 1000 transmission time intervals (Transmission Time Interval, TTI), the number of UE scheduling exceeds 100, and the number of scheduling failures exceeds 80. If such a UE exists, it moves out.
  • TTI Transmission Time Interval
  • CU1-> Cell_1 configures the UE migration strategy. If the migration reason is R, the UE is switched to the neighboring cell.
  • CU1-> DU1-> Cell_1 has neighboring cells CU1-> DUn-> Cell_M.
  • the UE migration method in this embodiment includes the following steps:
  • Step 6010 During the CU1-> DU1-> Cell_1 scheduling process, it is detected that UE0 satisfies assumption 1), then UE0 is selected as the migrated UE, and the migration reason value is R.
  • Step 6020 DU1 informs CU1 through the "DU Migration UE List Indication" message that UE0 under CU1-> DU1-> Cell_1 needs to be migrated due to the occurrence cause value being R.
  • Step 6030 CU1 receives the "DU migration UE list indication" message from DU1 and finds that the reason for migration is R, and initiates the process of switching UE0 to CU1-> DUn-> Cell_M.
  • Step 6040 UE0 receives the handover instruction and switches to CU1-> DUn-> Cell_M cell.
  • Embodiment 3 of the present application also provides a UE migration method.
  • the difference between this embodiment and the foregoing embodiments 1 and 2 is that, in this embodiment, the CU sends a low-load neighbor cell indication to assist the DU in choosing to migrate the UE.
  • the following conditions may be preset:
  • CU1-> DU1-> Cell_1 configures a high load threshold so that the PRB occupancy rate reaches 80% of the available resources of the cell.
  • CU1-> DU1-> Cell_1 configures the UE migration out selection strategy to select UEs whose PRB occupancy rate exceeds 5%.
  • the cell Cell_1 has two neighboring cells, which are:
  • UE0 supports migration to the neighbor cell Cell_M
  • UE1 does not support migration to the neighbor cell Cell_M.
  • this embodiment 4 may include the following steps:
  • step S7010 CU1 finds that the load of the two neighboring cells Cell_M and Cell_T of the cell Cell_1 is 20% and 70%, respectively. According to the set low-load judgment criterion, it is considered that the neighboring cell Cell_M is a low-load neighboring cell.
  • Step S7020 CU1 notifies DU1 of the low-load neighbor cell_M frequency and other information through the F1 interface "CU low-load neighbor cell frequency information indication" message.
  • step S7030 DU1 receives the low load frequency indication information, and after a period of time, it is found that the PRB occupancy rate of the cell Cell_1 exceeds 80%.
  • Step S7040 DU1 starts to screen the UE for migration.
  • the setting condition 2 only UE0 and UE1 satisfy the condition; according to the setting condition 5), since UE1 does not support the migration to the neighboring cell Cell_M, UE1 is excluded, and only UE0 satisfies the migration condition. Therefore, DU1 selects UE0 to send to CU1, and requests CU1 to migrate to UE0. The reason for the migration is high load.
  • step S7050 after receiving the relocation request, CU1 finds that the cause of the relocation is the high load of the cell, and the cell Cell_1 has a low-load neighbor Cell_M, then CU1 initiates a migration process to the neighbor cell Cell_M for UE0. Measurement switching, redirection, etc.
  • Step S7060 after receiving the relocation instruction, UE0 relocates to the CU1-> DUn-> Cell_M cell indicated by the relocation instruction.
  • CU1 does not actively collect the load of the neighboring cell of the cell Cell_1, but the DU first indicates the load change to the CU, and then the CU takes reasonable load balancing measures.
  • the threshold for sending the high load indication message configured by the cell Cell_1 is that the PRB occupancy rate exceeds 75%.
  • the high load threshold of the cell Cell_1 is configured so that the PRB occupancy rate reaches 80% of the available resources of the cell.
  • the cell Cell_1 configures the UE migration out selection strategy to select the UE whose PRB occupancy rate exceeds 5%.
  • UE0 supports migration to the neighbor cell Cell_M
  • UE1 does not support migration to the neighbor cell Cell_M.
  • this embodiment may include the following steps:
  • Step S8010 it is detected that the PRB occupancy rate of the cell Cell_1 exceeds 75% but does not exceed 80%, then the DU1 sends a "DU load indication" message to the CU1.
  • Cell_1 load status (medium or high), CU1-> DU1-> Cell_1 uplink and downlink remaining capacity (indicating remaining service acceptance capacity).
  • Step S8020 after receiving the load instruction, CU1 finds that the load of Cell_1 is too high, and CU1 starts the load collection process of the neighboring cell of Cell_1.
  • This embodiment describes load collection in the neighboring area.
  • the neighbor cell of the 5G RAN system cell is configured on the CU side. Therefore, the CU is responsible for load collection in the neighbor cell.
  • Neighbor cells may be deployed across DUs or across CUs (there may also be neighboring cells of different systems, such as Long Term Evolution (LTE) neighbor cells), as shown in Figures 1 and 9:
  • LTE Long Term Evolution
  • CU and LTE are connected via X2 interface.
  • the load collection is also divided into the following three types.
  • the first type load interaction between CU and LTE cell
  • This load interaction can be carried out through the existing X2 standard protocol messages, mainly involving the following three messages:
  • Resource status request (RESOURCE STATUS REQUEST): Specify the load of the resource that needs to be collected and the period of the load report.
  • the second kind load interaction between CU and DU
  • This load interaction can be modeled on the X2 load interaction mode, and three messages need to be added on the F1 interface:
  • CU RESOURCE STATUS REQUEST (the message name is only for display, not limited to this): CU sends it to DU, requesting DU to report the load of the designated cell.
  • Message content cell identification, resource type to be collected, load reporting method and period, etc.
  • CU RESOURCE STATUS RESPONSE (message name is not limited to this): DU is sent to CU, DU cell responds to CU request for resource collection.
  • DU RESOURCE STATUS UPDATE (the message name is not limited to this): DU reports the cell load according to the CU RESOURCE STATUS REQUEST request method.
  • the content of the message may include cell identification, hardware, transmission load status (high, medium, low), remaining resources (indicating service acceptance capability), etc.
  • the third kind load interaction between CU and CU
  • This load interaction can be modeled on the X2 load interaction mode, and three messages need to be added to the Xn interface:
  • XN RESOURCE STATUS REQUEST A cell of CU1 requests the load of some cells under CU2, and then CU1 sends it to CU2 through the Xn port.
  • the content of the message may include the identity of the neighboring cell that needs to collect the load, the type of load that needs to be collected (hardware load, transmission load, physical resource load, etc.), load reporting method and period, etc.
  • CU2 responds to the cell load requested by CU1 as requested by CU1.
  • the content of the message may include CU2 load, for example, hardware load or transmission load status, etc., and the cell ID under CU2 that needs to report load, hardware, transmission load status (high, medium, low), remaining resources (indicating service acceptance capability), etc.
  • the load interaction between the CU and CU may be forwarded by the CU to the DU for processing. And call the interface of CU and DU load interaction.
  • CU1-> DU1-> Cell_1 has two neighboring cells, one inter-DU neighboring cell CU1-> DUn-> Cell_M, and one cross-CU The neighboring cell CU2-> DU2-> Cell_CU2_T.
  • the load collection of this implementation includes the following steps:
  • Step S9010 CU1 receives the "DU load indication" of CU1-> DU1-> Cell_1 and finds that CU1-> DU1-> Cell_1 is highly loaded, or CU1's own strategy (such as CU1 hardware load reaching the set threshold, CU1's self Optimization function) and other reasons, start to collect the load of CU1-> DU1-> Cell_1 neighboring area.
  • Step S9020 CU1 sends a load collection request CU RESOURCE STATUS REQUEST to CU1-> DUn-> Cell_M through the F1 interface.
  • the main content of the message is: CU1-> DUn-> Cell_M cell identification, collected load type (including but not limited to transmission load , Physical resource load, hardware load, etc.), load reporting cycle.
  • Step S9030 CU1 sends a load collection request XN RESOURCE STATUS REQUEST to CU2 through the Xn interface, the main content of the message: the cell ID of CU2-> DU2-> Cell_CU2_T, the type of load collected (including but not limited to transmission load, physical resource load, hardware Load, etc.), load reporting period.
  • Step S9040 CU1-> DUn-> Cell_M receives the load collection request CURESRESCESTATUSREQUEST of CU1, and sends CURESRESCESTATUSRESPONSE to CU1 as a response, indicating that CU1-> DUn-> Cell_M has accepted the request and will report according to the request load.
  • Step S9050 CU2 receives the load collection request XN RESOURCE STATUS REQUEST of CU1 and finds that it needs to collect the load of CU2-> DU2-> Cell_CU2_T, then CU2 sends CU RESOURCE STATUS REQUEST to DU2 through the F1 interface, the main content of the message: CU2-> DU2 -> Cell_CU2_T's cell ID, collected load type (including but not limited to transmission load, physical resource load, hardware load, etc.), load reporting period.
  • CU2-> DU2 -> Cell_CU2_T's cell ID, collected load type including but not limited to transmission load, physical resource load, hardware load, etc.
  • Step S9060 CU2-> DU2-> Cell_CU2_T receives the CU2 load collection request CU RESOURCE STATUS REQUEST and sends CU RESOURCE STATUS RESPONSE to CU2 as a response, indicating that CU2-> DU2-> Cell_CU2_T has accepted the request and will report it as requested load.
  • Step S9070 After CU2 receives the resource collection response CU2-> DU2-> Cell_CU2_T CU RESOURCE STATUS RESPONSE, it responds to CU1 through the Xn interface to XN RESOURCE STATUS RESPONSE, indicating that DU2 has accepted the request and will report the load as requested.
  • Step S9080 CU1-> DUn-> Cell_M collects the load and sends DURESOURCESTATUSUPDATE to report the load to the CU1 through the F1 interface, the message content: CU1-> DUn-> Cell_M cell identification, hardware, transmission load status (high, medium, Low), remaining resources (indicating business acceptance capacity), etc.
  • Step S9090 CU2-> DU2-> Cell_CU2_T collects load, sends DURESOURCESTATUSUPDATE to report load through F1 interface, message content: CU2-> DU2-> Cell_CU2_T cell ID, hardware, transmission load status (high, medium, Low), remaining resources (indicating business acceptance capacity), etc.
  • Step S9100 CU2 sends the received CU2-> DU2-> Cell_CU2_T load to CU1 through the Xn interface message XN RESOURCE STATUS UPDATE, the message content: CU2-> DU2-> Cell_CU2_T cell ID, hardware, transmission load status (high, Medium and low), remaining resources (indicating business acceptance capacity), etc.
  • CU1 parses the received DU RESOURCE STATUS UPDATE to obtain the load across the DU neighborhood CU1-> DUn-> Cell_M, and CU1 parses the received XN RESOURCE STATUS UPDATE to obtain the cross-CU neighbor CU2-> DU2- > Load of Cell_CU2_T.
  • module and “unit” may implement a combination of software and / or hardware that performs a predetermined function.
  • the devices described in the following embodiments are implemented in software, implementation of hardware or a combination of software and hardware is also possible and conceived.
  • FIG. 10 is a structural block diagram of a centralized unit CU according to an embodiment of the present application.
  • the centralized unit 100 includes a receiving module 110 and a migration module 120.
  • the receiving module 110 is configured to receive the migrated UE list sent by the distribution unit DU.
  • the migration module 120 is configured to perform neighbor cell migration on the UE in the migrated UE list.
  • FIG. 11 is a structural block diagram of a distribution unit according to an embodiment of the present application. As shown in FIG. 11, the distribution unit 200 includes a monitoring module 210 and a sending module 220.
  • the monitoring module 210 is configured to monitor the status of the UE in the first cell, and add the UE in the first cell that conforms to the migration policy to the list of migrated UEs.
  • the sending module 220 is configured to send the migrated UE list to the centralized unit CU, so that the CU performs neighbor cell migration on the UEs in the migrated UE list.
  • the above-mentioned multiple modules can be implemented by software or hardware. For the latter, they can be implemented by the following methods, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned multiple modules are respectively combined in any combination Located in different processors.
  • the above-mentioned multiple modules or multiple steps of the present application may be implemented by a general-purpose computing device, and they may be concentrated on a single computing device or distributed on a network composed of multiple computing devices.
  • they can be implemented with program code executable by the computing device, so that they can be stored in the storage device to be executed by the computing device, and in some cases, the programs can be executed in an order different from here
  • the steps shown or described are implemented by making them into multiple integrated circuit modules, respectively, or by making multiple modules or steps among them into a single integrated circuit module. In this way, this application is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文提供了一种用户设备迁移方法、集中单元、分布单元及***，该方法包括：集中单元CU接收分布单元DU发送的迁移UE列表；所述CU对迁移UE列表中的UE进行邻区迁移。

Description

用户设备迁移方法、集中单元、分布单元及***
本申请要求在2018年11月15日提交中国专利局、申请号为201811362801.7的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，例如，涉及一种用户设备迁移方法、集中单元、分布单元及***。
背景技术
随着移动通信技术的发展，第五代移动通信***(the 5rd Generation mobile communication system，5G)已经进入人们的视眼。在5G无线接入网络(Radio Access Network，RAN)架构方面，第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)通过了集中单元/分布单元(Central Unit/Distributed Unit，CU/DU)架构方案。CU主要处理非实时的无线高层协议栈功能，而DU主要处理物理层功能和实时性需求的层2功能。CU与DU通过F1接口完成信令和数据传输。
因为CU与DU分离，一些常规业务功能实现上变得复杂起来。以负荷均衡功能为例。当负荷较高时，运营商一般会有比较灵活的策略来选择迁移用户设备(User Equipment，UE)，其中，UE的物理资源块(Physical Resource Block，PRB)占用率、调制编码阶数(Modulation and Coding Scheme，MCS)和UE的空分信息等等一般来说是重要的参考指标。这些参数在***移动通信***(the4rd Generation mobile communication system，4G)基站中可直接从本站内部媒体接入控制(Medium Access Control，MAC)层获取。
而在5G中因为功能划分的缘故，只有DU才知道每个UE的PRB、MCS、空分信息。只有CU才知道邻区的负荷，UE的迁移过程也由CU控制。
如果负荷均衡功能完全由CU实现，那么需要DU通过F1接口向CU上报每个UE的PRB占用量、MCS和空分信息。因CU下有大量DU，每个DU下有多个小区，每个小区下最大有上千用户。如果DU向CU报告这些信息，消息量很大。特别是用户占用的PRB数量、MCS和空分状态时刻会变化，因此DU有可能多次向CU报告这些信息。因为上报量信息量过大，给F1接口带来了额外的压力，有可能影响正常的业务。
发明内容
本申请实施例提供了一种用户设备迁移方法、集中单元、分布单元及***，以至少解决相关技术中UE的迁移的问题。
本申请实施例提供了一种用户设备迁移方法，包括：CU接收DU发送的迁移UE列表；所述CU对所述迁移UE列表中的UE进行邻区迁移。
一实施例中，所述CU接收DU发送的迁移UE列表，包括：CU接收DU发送的迁移UE列表指示消息，其中，所述迁移UE列表指示消息中携带有迁移UE列表以及迁移的原因值。
一实施例中，所述CU对所述迁移UE列表中的UE进行邻区迁移，包括：所述CU获取所述迁移UE列表中的UE所属的第一小区的低负荷邻区或高优先级邻区，其中，所述低负荷邻区为负荷低于预设门限的邻区或负荷比低于预设门限的邻区，所述高优先级邻区为优先级高于预设优先级的邻区；所述CU根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或所述高优先级邻区。
一实施例中，所述CU根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或所述高优先级邻区，包括以下之一：在迁移切换策略为盲切换的情况下，所述CU向所述迁移UE列表中的UE下发切换指令以将所述UE切换至所述低负荷邻区或所述高优先级邻区，其中，所述切换指令中携带有低负荷邻区信息或高优先级邻区信息；在迁移切换策略为重定向的情况下，所述CU向所述迁移UE列表中的UE下发重定向指令以将所述UE重定向至所述低负荷邻区或所述高优先级邻区，其中，所述重定向指令中携带有低负荷邻区的频点信息或高优先级邻区的频点信息；在迁移切换策略为基于测量的切换的情况下，所述CU向所述迁移UE列表中的UE下发对邻区的测量指令，并根据所述UE上报的测量报告，将所述UE切换到所述测量报告指示的邻区。
一实施例中，在所述CU接收DU发送的迁移UE列表之前，还包括：所述CU采集第一小区的所有邻区的负荷，并根据所述所有邻区的负荷，从所述所有邻区中筛选出所述第一小区的低负荷邻区；其中，所述第一小区为所述DU通知的待进行UE迁移的小区，所述低负荷邻区为负荷低于预设门限的邻区；所述CU将所述低负荷邻区的频点信息通知所述DU。
一实施例中，所述CU采集第一小区的所有邻区的负荷，包括以下至少之一：所述CU向第一小区的邻区发送资源采集请求，并接收所述邻区上报的小区负荷报告；所述CU向DU发送资源采集请求，并接收所述DU上报的小区负荷报告；所述CU向其它CU发送资源采集请求，并接收所述其它CU上报的小区负荷报告。
一实施例中，所述资源采集请求中至少包括以下之一：需要采集负荷的邻区标识、需要采集的负荷类型、负荷报告方式、负荷报告周期。本申请实施例还提供了一种用户设备迁移方法，包括：DU监控第一小区中UE的状况，并将所述第一小区中符合迁出策略的UE加入迁移UE列表中；所述DU向CU发送所述迁移UE列表。
一实施例中，所述迁出策略包括以下至少之一：物理资源块PRB占用率超过设定门限的UE；误包率超过设定门限的UE；不含指定业务的UE；资源不能满足业务的服务质量QoS要求的UE；优先级低于设定优先级的UE。
一实施例中，在所述DU监控第一小区中UE的状况，并将所述第一小区中符合迁出策略的UE加入迁移UE列表中之前，还包括：所述DU监控所述DU下多个小区的负荷情况，将待进行UE迁移的所述第一小区通知所述CU，其中，所述第一小区为负荷高于第一预设门限的小区。
一实施例中，所述将待进行UE迁移的所述第一小区通知所述CU，包括：所述DU在满足触发条件的情况下，向所述CU发送负荷指示消息以将待进行UE迁移的所述第一小区通知所述CU，其中，所述触发条件包括以下至少之一：发现新增的高负荷小区、已经上报过的高负荷小区发生负荷变化达到第二预设门限。
一实施例中，所述负荷指示消息中包括以下至少之一：小区标识ID、小区负荷状态、小区上行剩余负荷、小区下行剩余负荷。
一实施例中，所述将所述第一小区中符合迁出策略的UE加入迁移UE列表中，包括：所述DU将所述第一小区中符合迁出策略并支持迁移到低负荷邻区的至少一个频点的UE加入所述迁移UE列表中，其中，所述低负荷邻区为所述CU指示的所述第一小区的所有邻区中负荷低于第三预设阈值的邻区。
本申请实施例还提供了一种集中单元CU，包括：接收模块，设置为接收分布单元DU发送的迁移UE列表；迁移模块，设置为对所述迁移UE列表中的UE进行邻区迁移。
一实施例中，所述接收模块是设置为接收DU发送的迁移UE列表指示消息，其中，所述迁移UE列表指示消息中携带有迁移UE列表以及迁移的原因值。
一实施例中，所述迁移模块包括：获取单元，设置为获取所述迁移UE列表中的UE所属的第一小区的低负荷邻区或高优先级邻区，其中，所述低负荷邻区为负荷低于预设门限的邻区或负荷比低于预设门限的邻区，所述高优先级邻区为优先级高于预设优先级的邻区；迁移单元，设置为根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或所述高优先级邻区。
一实施例中，所述迁移单元是设置为通过以下方式之一根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或高优先级邻区：在迁移切换策略为盲切换的情况下，向所述迁移UE列表中的UE下发切换指令以将所述UE切换至所述低负荷邻区或所述高优先级邻区，其中，所述切换指令中携带有低负荷邻区信息或高优先级邻区信息；在迁移切换策略为重定向的情况下，向所述迁移UE列表中的UE下发重定向指令以将所述UE重定向至所述低负荷邻区或所述高优先级邻区，其中，所述重定向指令中携带有低负荷邻区的频点信息或高优先级邻区的频点信息；在迁移切换策略为基于测量的切换的情况下，向所述迁移UE列表中的UE下发对邻区的测量指令，并根据所述UE上报的测量报告，将所述UE切换到所述测量报告指示的邻区。
一实施例中，所述迁移模块还包括：采集单元，设置为采集第一小区的所有邻区的负荷，并根据所述所有邻区的负荷，从所述所有邻区中筛选出所述第一小区的低负荷邻区，将所述低负荷邻区的频点信息通知所述DU，其中，所述第一小区为所述DU通知的待进行UE迁移的小区，所述低负荷邻区为负荷低于预设门限的邻区。本申请实施例还提供了一种分布单元DU，包括：监控模块，设置为监控第一小区中UE的状况，并将所述第一小区中符合迁出策略的UE加入迁移UE列表中；发送模块，设置为向集中单元CU发送所述迁移UE列表。
一实施例中，所述迁出策略包括以下至少之一：PRB占用率超过设定门限的UE；误包率超过设定门限的UE；不含指定业务的UE；资源不能满足业务的QoS要求的UE；优先级低于设定优先级的UE。
一实施例中，所述监控模块，还设置为监控所述DU下多个小区的负荷情况，将待进行UE迁移的所述第一小区通知所述CU，其中，所述第一小区为负荷高于第一预设门限的小区。
一实施例中，所述监控模块是设置为通过如下方式将待进行UE迁移的所述第一小区通知所述CU：在满足触发条件的情况下，向所述CU发送负荷指示消息以将所述第一小区通知所述CU，其中，所述触发条件包括以下至少之一：发现新增的高负荷小区、已经上报过的高负荷小区发生负荷变化达到第二预设门限。
一实施例中，所述负荷指示消息中包括以下至少之一：小区ID、小区负荷状态、小区上行剩余负荷、小区下行剩余负荷。
一实施例中，所述监控模块是设置为通过如下方式将所述第一小区中符合迁出策略的UE加入迁移UE列表中：将所述第一小区中符合迁出策略并支持迁移到低负荷邻区的至少一个频点的UE加入所述迁移UE列表中，其中，所述低负荷邻区为所述CU指示的所述第一小区的所有邻区中负荷低于第三预设阈值 的邻区。
根据本申请实施例还提供了一种用户设备迁移***，包括本申请任意实施例中的集中单元CU和分布单元DU。
附图说明
图1是本申请实施例提供的一种5G基站的CU/DU架构示意图；
图2是本申请实施例提供的一种用户设备迁移方法的流程图；
图3是本申请实施例提供的一种DU触发的UE迁移方法的流程图；
图4是本申请实施例提供的一种CU指示低负荷频点信息的UE迁移方法流程图；
图5是本申请实施例提供的另一种UE迁移方法的流程图；
图6是本申请实施例提供的另一种UE迁移方法的流程图；
图7是本申请实施例提供的另一种UE迁移方法的流程图；
图8是本申请实施例提供的另一种UE迁移方法的流程图；
图9是本申请实施例提供的一种小区负荷采集方法流程图；
图10是本申请实施例提供的一种集中单元CU的结构框图；
图11是本申请实施例提供的一种分布单元DU的结构框图。
具体实施方式
下文中将参考附图并结合实施例来说明本申请。本文中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请所提供的方法实施例可以在5G基站的CU/DU架构上执行。图1是5G基站的CU/DU架构示意图。如图1所示，该5G基站可以包括一个或多个CU(图1中仅示出CU1和CU2)，CU之间通过Xn接口连接。每个CU与其所属的一个或多个DU(例如，DU1至DUn)通过F1接口连接。每个DU下又具有多个小区。图1所示的结构仅为示意，其并不对上述的5G基站的CU/DU架构造成限定。
本实施例提供的用户设备迁移方法可以运行于图1所示的CU/DU架构上，以实现用户设备在小区内的迁移。图2是根据本申请实施例的用户设备迁移方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，CU接收DU发送的迁移UE列表。
步骤S204，CU对迁移UE列表中的UE进行邻区迁移。
在本实施例中，DU可以设置UE迁出策略，该迁出策略可以根据实际需要来进行设置。例如，可以包括但不限于以下策略及策略的组合：
1)选择PRB占用率超过设定门限的UE。
2)选择一定时间内误包率超过设定门限的UE。
3)选择不含一些业务(比如语音业务)的UE。
4)资源不足，不能满足服务质量(Quality of Service，QoS)要求，优先级相对低的UE等等。
5)负荷均衡原因，DU收到CU的消息，选择的UE应该支持迁移到至少CU指定的一个频点。
在本实施例，DU负责根据策略选择迁移出的UE列表，CU负责把DU选出来的UE迁移到合适的邻区，这样的话DU可根据调度策略自主选择UE进行迁移，可满足多种调度策略原因的UE迁移。另外，DU选出的迁移UE相对来说数量比较少，DU只把这些满足条件的UE报给CU，由CU控制迁移流程。避免DU向CU大量报告UE调度相关信息，可以很大程度减少通过F1交互的信息量，大大减少F1口的负荷，在不增加F1接口压力的情况下达到负荷均衡的目的。
本申请实施例还提供了一种DU触发的UE迁移方法，如图3所示，包括如下步骤：
步骤S3010，DU获知迁出策略或原则后，实时监控小区所有UE状况，识别符合迁出策略的UE汇总为UE列表。
步骤S3020，DU把需要迁移的UE组成的UE列表通过F1消息“DU迁移UE列表指示”消息发给CU，消息中包含迁移UE列表。
步骤S3030，CU收到该消息后，将根据消息中的迁移UE列表，用预设置的策略进行处理，包括且不限于盲切换，基于测量的切换，重定向等。对“DU迁移UE列表指示”消息携带的UE迁移列表中的每个UE按如下操作：
1)获取UE所属小区的低负荷邻区或高优先级邻区。
2)如果配置的策略是盲切换，则直接对UE下切换指令(切换指令有低负荷邻区信息或高优先级邻区信息)。如果配置的策略是重定向，直接对UE下重定向指令(指令有低负荷邻区的频点或高优先级邻区的频点等信息)。如果配置的策略是基于测量的切换，则对每个UE下对邻区的测量指令，当UE上报测量报告，说明邻区的信号足够强，则可以对UE发出切换到测量报告指示的邻区 指令。
3)CU把“DU迁移UE列表指示”消息指示的迁移UE列表中的UE根据配置的策略迁移到低负荷邻区或高优先级邻区。通过标准协议中规定的重定向或切换流程完成迁移。
本申请实施例还提供了一种CU指示低负荷频点信息的UE迁移方法。本实施例以负荷均衡这一特定场景下的UE迁移为例。
在本实施例中，为了保证DU选出的UE尽量能迁移到合适的邻区，CU可以把邻区的频点信息通过F1接口通知DU，这些邻区频点信息作为DU选择迁移UE的参考因素之一，保证选出来的UE列表支持向这些频点迁移。CU可能不会时刻采集邻区负荷信息，当DU需要主动迁移业务时可提前通过F1接口通知CU采集邻区负荷。
如图4所示，本实施提供的UE迁移方法包括如下步骤：
步骤S4010，DU向CU发送“DU负荷指示”消息，该消息如果是DU主动发起，向CU指示DU下的小区负荷状态变化(如负荷由低变高或负荷由高变低)，便于CU触发合理的负载均衡行为。比如负荷由低变高时CU可以采集该小区的邻区负荷，找到低负荷的邻区，把高负荷小区下的部分业务迁移到低负荷的邻区；如负荷由高变低时CU可以停止采集邻区负荷。
消息内容可以包括小区标识(Identifier，ID)，小区负荷状态(高、中、低)，小区上行剩余负荷、小区下行剩余负荷等。
一实施例中，DU实时监控自己名下多个小区的负荷情况，并根据从后台获取的预设门限，及时判断是否是高负荷小区。当DU发现存在一个或多个高负荷小区时，通过“DU负荷指示”消息通知所属CU，该消息只在以下情况下触发(包括且不限于)：发现新增高负荷小区(根据预设门限判断)；已经上报过的高负荷小区，变为低负荷小区(根据预设门限判断)；已经上报过的高负荷小区，变为更高负荷小区(根据预设门限判断)。
步骤S4020，CU收到“DU负荷指示”消息后，将进行负荷均衡准备工作，包括：1)记录DU上报的高负荷小区；2)对于每一个高负荷小区，CU获取其所有邻区的负荷，并可根据预设的门限值筛选出低负荷邻区。
步骤S4030，CU通过“CU低负荷邻区频点信息指示”消息，将获取的高负荷小区的低负荷邻区的频点等信息下发给对应DU，以辅助DU选择迁移UE。
步骤S4040，DU获取“CU低负荷邻区频点信息指示”消息后，根据设定的策略和低负荷频点信息选择迁移UE。
步骤S4050，DU把需要迁移的UE列表通过F1消息“DU迁移UE列表指示”消息发给CU，消息中包含迁移UE列表。该步骤可与图3实施例中的步骤S302相同，在此不赘述。
步骤S4060，CU收到该消息后，将根据消息中的迁移UE列表，用预设置的策略对迁移UE列表中的UE进行迁移，包括且不限于盲切换，基于测量的切换，重定向等。该步骤可与图3实施例中的步骤S303相同，在此不赘述。
实施例1
本申请实施例1提供了一种UE迁移方法。为了描述方便，在本实施实例中，CU1->DU1->Cell_1表示CU1下DU1的Cell_1小区，其它小区与DU以及CU之间的关系可以以此类推，在此不一一列举。另外，在本实施例中，预先设定如下条件：
1)小区Cell_1配置高负荷门限为PRB占用率达到小区可用资源的80％。
2)小区Cell_1配置UE迁出选择策略为选择PRB占用率超过5％的UE。
3)小区Cell_1下有100个UE，编号分别为UE0～UE99，其中UE0和UE1占用的PRB分别为小区整个资源的6％，8％。其它UE占用的PRB资源都没有超过5％。
4)小区Cell_1有两个邻区，分别为：
CU1->DUn->Cell_M，CU2->DU2->Cell_CU2_T。
通过常规的负荷交互方式发现邻区Cell_M的负荷为20％，邻区Cell_CU2_T的负荷为70％。
如图5所示，本实施例的UE迁移方法包括如下步骤：
步骤S5010，DU1检测到小区Cell_1的PRB占用率超过80％。
步骤S5020，DU1开始在小区Cell_1中筛选需迁移的UE，根据设定条件2)，只有UE0和UE1满足迁移条件，因此DU1选择UE0和UE1发给CU1，要求CU1迁移UE0和UE1，迁移原因是高负荷。
步骤S5030，CU1收到迁移请求后，发现迁移原因是小区高负荷，且小区Cell_1有一个低负荷邻区Cell_M，则CU1对UE0和UE1分别发起向邻区Cell_M的迁移流程，该迁移流程可以是直接切换、测量切换、重定向等。
步骤S5040，UE0和UE1收到迁移指令后，迁移到迁移指令指示的CU1->DUn->Cell_M小区下。
实施例2
在本实施例由DU触发迁移UE，在本实施例中，预先设定如下条件：
1)CU1->DU1->Cell_1配置调度策略迁移UE：1000个传输时间间隔(Transmission Time Interval，TTI)内，UE调度的次数超过100次，调度失败的次数超过80次。如果存在这样的UE，则迁出。
2)CU1->Cell_1配置UE迁移策略，如迁移原因为R，则把UE切换到邻区。
3)CU1->DU1->Cell_1下有100个UE，编号分别为UE0～UE99。
4)CU1->DU1->Cell_1有邻区CU1->DUn->Cell_M。
如图6所示，本实施例的UE迁移方法包括如下步骤：
步骤6010：CU1->DU1->Cell_1调度过程中检测到UE0满足假设条件1)，则挑选UE0作为迁移UE，迁移原因值为R。
步骤6020：DU1通过“DU迁移UE列表指示”消息告知CU1，CU1->DU1->Cell_1下的UE0因发生原因值为R的情况需要迁移。
步骤6030：CU1收到DU1的“DU迁移UE列表指示”消息，发现迁移原因为R，则发起将UE0切换到CU1->DUn->Cell_M的流程。
步骤6040：UE0收到切换指令，切换到CU1->DUn->Cell_M小区。
实施例3
本申请实施例3还提供了一种UE迁移方法。本实施例与上述实施例1和2的不同之处在于，在本实施实例中，由CU发送低负荷邻区指示，辅助DU选择迁移UE。同样，在本实施例中，可预先设定如下条件：
1)CU1->DU1->Cell_1配置高负荷门限为PRB占用率达到小区可用资源的80％。
2)CU1->DU1->Cell_1配置UE迁出选择策略为选择PRB占用率超过5％的UE。
3)CU1->DU1->Cell_1下有100个UE，编号分别为UE0～UE99，其中UE0和UE1占用的PRB分别为小区整个资源的6％，8％。其它UE占用的PRB资源都没有超过5％。
4)小区Cell_1有两个邻区，分别为：
CU1->DUn->Cell_M，CU2->DU2->Cell_CU2_T。
通过常规的负荷交互方式发现邻区Cell_M的负荷为20％，邻区Cell_T的负荷为70％。
5)UE0支持向邻区Cell_M迁移，UE1不支持向邻区Cell_M迁移。
如图7所示，本实施例4可包括如下步骤：
步骤S7010，CU1发现小区Cell_1的两个邻区Cell_M和Cell_T负荷分别为20％和70％。根据设定的低负荷判断准则，认为邻区Cell_M为低负荷邻区。
步骤S7020，CU1通过F1接口“CU低负荷邻区频点信息指示”消息通知DU1低负荷邻区Cell_M的频点等信息。
步骤S7030，DU1收到低负荷频点指示信息，一段时间后发现小区Cell_1的PRB占用率超过80％。
步骤S7040，DU1开始筛选UE进行迁移。根据设定条件2)，只有UE0和UE1满足条件；根据设定条件5)，由于UE1不支持向邻区Cell_M迁移，因此排除UE1，只有UE0满足迁移条件。因此DU1选择UE0发给CU1，要求CU1迁移UE0，迁移原因是高负荷。
步骤S7050，CU1收到迁移请求后，发现迁移原因是小区高负荷，且小区Cell_1有一个低负荷邻区Cell_M，则CU1对UE0发起向邻区Cell_M的迁移流程，该迁移流程可以是直接切换、测量切换、重定向等。
步骤S7060，UE0收到迁移指令后，迁移到迁移指令指示的CU1->DUn->Cell_M小区。
实施例4
本实施例与上述的实施例的不同之处在于，在本实施实例中，CU1没有主动采集小区Cell_1的邻区负荷，而是DU先向CU指示负荷变化，然后CU才采取合理负荷均衡措施。
同样，在本实施例中，可预先设定如下条件：
1)小区Cell_1配置的高负荷指示消息发送门限为PRB占用率超过75％。
2)小区Cell_1配置高负荷门限为PRB占用率达到小区可用资源的80％。
3)小区Cell_1配置UE迁出选择策略为选择PRB占用率超过5％的UE。
4)小区Cell_1下有100个UE，编号分别为UE0～UE99，其中UE0和UE1占用的PRB分别为小区整个资源的6％，8％。其它UE占用的PRB资源都没有超过5％。
5)UE0支持向邻区Cell_M迁移，UE1不支持向邻区Cell_M迁移。
如图8所示，本实施例可包括如下步骤：
步骤S8010，检测到小区Cell_1的PRB占用率超过75％但是没有超过80％， 则DU1向CU1发送“DU负荷指示”消息，消息内容包含CU1->DU1->Cell_1标识、CU1->DU1->Cell_1负荷状态(中或高)、CU1->DU1->Cell_1上下行剩余容量(表明剩余业务接纳能力)。
步骤S8020，CU1收到负荷指示后发现小区Cell_1负荷偏高，则CU1启动Cell_1的邻区的负荷采集流程。
本实施的后续步骤与实施例3的相同，可参考实施例3的步骤S7010至步骤S7050，在此不累述。
实施例5
本实施例描述了邻区负荷采集。以5G RAN***为例，5G RAN***小区的邻区在CU侧配置，因此，由CU负责邻区负荷采集。邻区可能跨DU部署，也可能跨CU部署(也可能存在异***邻区，如长期演进(Long Term Evolution，LTE)邻区)，如图1和9所示：
1)CU和LTE通过X2接口连接。
2)CU和DU通过F1接口连接。
3)CU之间通过Xn接口连接。
依据上述连接方式的不同，将负荷采集也分如下三种类型。
第一种：CU与LTE小区之间的负荷交互
该负荷交互可以通过已有的X2标准协议消息来进行，主要涉及以下3条消息：
1)资源状态请求(RESOURCE STATUS REQUEST)：指明需要采集那种资源的负荷，及负荷报告的周期。
2)资源状态响应(RESOURCE STATUS RESPONSE)：目标小区响应资源采集请求。
3)资源状态更新(RESOURCE STATUS UPDATE)：目标小区按RESOURCE STATUS REQUEST请求方式报告小区负荷。
第二种：CU与DU之间负荷交互
该负荷交互可以仿照X2负荷交互方式，需要在F1接口增加3条消息：
1)CU RESOURCE STATUS REQUEST(消息名称仅为示列，并不限于此)：CU发给DU，要求DU报告指定小区的负荷。消息内容：小区标识、需要采集的资源类型、及负荷报告方式和周期等。
2)CU RESOURCE STATUS RESPONSE(消息名称不限于此)：DU发给 CU，DU小区响应CU对资源采集请求。
3)DU RESOURCE STATUS UPDATE(消息名称不限于此)：DU按CU RESOURCE STATUS REQUEST请求方式报告小区负荷。消息内容可包括小区标识，硬件、传输负荷状态(高、中、低)、剩余资源(表明业务接纳能力)等。
第三种：CU与CU之间的负荷交互
该负荷交互可仿照X2负荷交互方式，需要在Xn接口增加3条消息：
1)XN RESOURCE STATUS REQUEST：CU1的一小区请求CU2下一些小区的负荷，则由CU1通过Xn口发给CU2。消息内容可包括需要采集负荷的邻区小区标识，需要采集的负荷类型(硬件负荷、传输负荷、物理资源负荷等等)，负荷报告方式及周期等。
2)XN RESOURCE STATUS RESPONSE：CU2响应CU1的负荷请求。
3)XN RESOURCE STATUS UPDATE：CU2按CU1的请求方式响应CU1所请求的小区负荷。消息内容可包括CU2负荷，例如，硬件负荷或传输负荷状态等，以及CU2下需报告负荷的小区标识，硬件、传输负荷状态(高、中、低)、剩余资源(表明业务接纳能力)等。
因5G RAN物理资源在DU侧，CU和CU的负荷交互，可能会由CU转发给DU处理。及调用CU和DU负荷交互的接口。
下面本实施例描述了CU的负荷采集流程流程，如图9所示，CU1->DU1->Cell_1有2个邻区，一个跨DU的邻区CU1->DUn->Cell_M，一个跨CU的邻区CU2->DU2->Cell_CU2_T。
本实施的负荷采集包括如下步骤：
步骤S9010：CU1收到CU1->DU1->Cell_1的“DU负荷指示”，发现CU1->DU1->Cell_1高负荷，或者CU1本身的策略(如CU1硬件负荷达到设定的门限、CU1的自优化功能)等原因，开始采集CU1->DU1->Cell_1邻区的负荷。
步骤S9020：CU1通过F1接口向CU1->DUn->Cell_M发负荷采集请求CU RESOURCE STATUS REQUEST，消息主要内容：CU1->DUn->Cell_M的小区标识、采集的负荷类型(包含但不限于传输负荷，物理资源负荷，硬件负荷等)、负荷报告周期。
步骤S9030：CU1通过Xn接口向CU2发负荷采集请求XN RESOURCE STATUS REQUEST，消息主要内容：CU2->DU2->Cell_CU2_T的小区标识、采 集的负荷类型(包含但不限于传输负荷，物理资源负荷，硬件负荷等)、负荷报告周期。
步骤S9040：CU1->DUn->Cell_M收到CU1的负荷采集请求CU RESOURCE STATUS REQUEST，向CU1发送CU RESOURCE STATUS RESPONSE作为响应，表明CU1->DUn->Cell_M已经接受请求并会按请求的方式报告负荷。
步骤S9050：CU2收到CU1的负荷采集请求XN RESOURCE STATUS REQUEST，发现需要采集CU2->DU2->Cell_CU2_T的负荷，则CU2通过F1接口向DU2发送CU RESOURCE STATUS REQUEST，消息主要内容：CU2->DU2->Cell_CU2_T的小区标识、采集的负荷类型(包含但不限于传输负荷，物理资源负荷，硬件负荷等)、负荷报告周期。
步骤S9060：CU2->DU2->Cell_CU2_T收到CU2的负荷采集请求CU RESOURCE STATUS REQUEST，向CU2发送CU RESOURCE STATUS RESPONSE作为响应，表明CU2->DU2->Cell_CU2_T已经接受请求并会按请求的方式报告负荷。
步骤S9070：CU2接收到CU2->DU2->Cell_CU2_T的资源采集响应CU RESOURCE STATUS RESPONSE后，通过Xn接口向CU1响应XN RESOURCE STATUS RESPONSE，表明DU2已经接受请求并会按请求的方式报告负荷。
步骤S9080：CU1->DUn->Cell_M收集负荷，通过F1接口向CU1发送DU RESOURCE STATUS UPDATE报告负荷，消息内容：CU1->DUn->Cell_M的小区标识，硬件、传输负荷状态(高、中、低)、剩余资源(表明业务接纳能力)等。
步骤S9090：CU2->DU2->Cell_CU2_T收集负荷，通过F1接口向CU2发送DU RESOURCE STATUS UPDATE报告负荷，消息内容：CU2->DU2->Cell_CU2_T的小区标识，硬件、传输负荷状态(高、中、低)、剩余资源(表明业务接纳能力)等。
步骤S9100：CU2把收到的CU2->DU2->Cell_CU2_T负荷通过Xn接口消息XN RESOURCE STATUS UPDATE发给CU1，消息内容：CU2->DU2->Cell_CU2_T的小区标识，硬件、传输负荷状态(高、中、低)、剩余资源(表明业务接纳能力)等。
通过上述的步骤，CU1解析收到的DU RESOURCE STATUS UPDATE获取到跨DU邻区CU1->DUn->Cell_M的负荷，CU1解析收到的XN RESOURCE STATUS UPDATE获取到跨CU邻区CU2->DU2->Cell_CU2_T的负荷。
在本实施例中还提供了一种装置，该装置设置为实现上述实施例，已经进 行过说明的不再赘述。如以下所使用的，术语“模块”、“单元”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图10是根据本申请实施例的集中单元CU的结构框图，如图10所示，该集中单元100包括接收模块110和迁移模块120。
接收模块110设置为接收分布单元DU发送的迁移UE列表。迁移模块120，设置为对迁移UE列表中的UE进行邻区迁移。
图11是根据本申请实施例的分布单元的结构框图，如图11所示，该分布单元200包括监控模块210和发送模块220。
监控模块210设置为监控第一小区中UE的状况，并将第一小区中符合迁出策略的UE加入迁移UE列表中。
发送模块220设置为向集中单元CU发送所述迁移UE列表，以便所述CU将迁移UE列表中的UE进行邻区迁移。
上述多个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述多个模块以任意组合的形式分别位于不同的处理器中。
上述的本申请的多个模块或多个步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上。一实施例中，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在一些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成多个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。

Claims (25)

  1. 一种用户设备UE迁移方法，包括：
    集中单元CU接收分布单元DU发送的迁移UE列表；
    所述CU对所述迁移UE列表中的UE进行邻区迁移。
  2. 根据权利要求1所述的方法，其中，所述CU接收DU发送的迁移UE列表，包括：
    CU接收DU发送的迁移UE列表指示消息，其中，所述迁移UE列表指示消息中携带有迁移UE列表以及迁移的原因值。
  3. 根据权利要求1或2所述的方法，其中，所述CU对所述迁移UE列表中的UE进行邻区迁移，包括：
    所述CU获取所述迁移UE列表中的UE所属的第一小区的低负荷邻区或高优先级邻区，其中，所述低负荷邻区为负荷低于预设门限的邻区或负荷比低于预设门限的邻区，所述高优先级邻区为优先级高于预设优先级的邻区；
    所述CU根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或所述高优先级邻区。
  4. 根据权利要求3所述的方法，其中，所述CU根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或所述高优先级邻区，包括以下之一：
    在迁移切换策略为盲切换的情况下，所述CU向所述迁移UE列表中的UE下发切换指令以将所述UE切换至所述低负荷邻区或所述高优先级邻区，其中，所述切换指令中携带有低负荷邻区信息或高优先级邻区信息；
    在迁移切换策略为重定向的情况下，所述CU向所述迁移UE列表中的UE下发重定向指令以将所述UE重定向至所述低负荷邻区或所述高优先级邻区，其中，所述重定向指令中携带有低负荷邻区的频点信息或高优先级邻区的频点信息；
    在迁移切换策略为基于测量的切换的情况下，所述CU向所述迁移UE列表中的UE下发对邻区的测量指令，并根据所述UE上报的测量报告，将所述UE切换到所述测量报告指示的邻区。
  5. 根据权利要求1或2所述的方法，在所述CU接收DU发送的迁移UE列表之前，还包括：
    所述CU采集第一小区的所有邻区的负荷，并根据所述所有邻区的负荷，从所述所有邻区中筛选出所述第一小区的低负荷邻区；其中，所述第一小区为所述DU通知的待进行UE迁移的小区，所述低负荷邻区为负荷低于预设门限的邻 区；
    所述CU将所述低负荷邻区的频点信息通知所述DU。
  6. 根据权利要求5所述的方法，其中，所述CU采集第一小区的所有邻区的负荷，包括以下至少之一：
    所述CU向第一小区的邻区发送资源采集请求，并接收所述邻区上报的小区负荷报告；
    所述CU向DU发送资源采集请求，并接收所述DU上报的小区负荷报告；
    所述CU向其它CU发送资源采集请求，并接收所述其它CU上报的小区负荷报告。
  7. 根据权利要求6所述的方法，其中，所述资源采集请求中至少包括以下之一：
    需要采集负荷的邻区标识、需要采集的负荷类型、负荷报告方式、负荷报告周期。
  8. 一种用户设备UE迁移方法，包括：
    分布单元DU监控第一小区中UE的状况，并将所述第一小区中符合迁出策略的UE加入迁移UE列表中；
    所述DU向集中单元CU发送所述迁移UE列表。
  9. 根据权利要求8所述的方法，其中，所述迁出策略包括以下至少之一：
    物理资源块PRB占用率超过设定门限的UE；
    误包率超过设定门限的UE；
    不含指定业务的UE；
    资源不能满足业务的服务质量QoS要求的UE；
    优先级低于设定优先级的UE。
  10. 根据权利要求8或9所述的方法，在所述DU监控第一小区中UE的状况，并将所述第一小区中符合迁出策略的UE加入迁移UE列表中之前，还包括：
    所述DU监控所述DU下多个小区的负荷情况，将待进行UE迁移的所述第一小区通知所述CU，其中，所述第一小区为负荷高于第一预设门限的小区。
  11. 根据权利要求10所述的方法，其中，所述将待进行UE迁移的所述第一小区通知所述CU，包括：
    所述DU在满足触发条件的情况下，向所述CU发送负荷指示消息以将待进 行UE迁移的所述第一小区通知所述CU，其中，所述触发条件包括以下至少之一：发现新增的高负荷小区、已经上报过的高负荷小区发生负荷变化达到第二预设门限。
  12. 根据权利要求11所述的方法，其中，所述负荷指示消息中包括以下至少之一：
    小区标识ID、小区负荷状态、小区上行剩余负荷、小区下行剩余负荷。
  13. 根据权利要求11所述的方法，其中，所述将所述第一小区中符合迁出策略的UE加入迁移UE列表中，包括：
    所述DU将所述第一小区中符合迁出策略并支持迁移到低负荷邻区的至少一个频点的UE加入所述迁移UE列表中，其中，所述低负荷邻区为所述CU指示的所述第一小区的所有邻区中负荷低于第三预设阈值的邻区。
  14. 一种集中单元CU，包括：
    接收模块，设置为接收分布单元DU发送的迁移用户设备UE列表；
    迁移模块，设置为对所述迁移UE列表中的UE进行邻区迁移。
  15. 根据权利要求14所述的CU，其中，
    所述接收模块，是设置为接收DU发送的迁移UE列表指示消息，其中，所述迁移UE列表指示消息中携带有迁移UE列表以及迁移的原因值。
  16. 根据权利要求14或15所述的CU，其中，所述迁移模块包括：
    获取单元，设置为获取所述迁移UE列表中的UE所属的第一小区的低负荷邻区或高优先级邻区，其中，所述低负荷邻区为负荷低于预设门限的邻区或负荷比低于预设门限的邻区，所述高优先级邻区为优先级高于预设优先级的邻区；
    迁移单元，设置为根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或所述高优先级邻区。
  17. 根据权利要求16所述的CU，其中，所述迁移单元是设置为通过以下方式之一根据配置的迁移切换策略将所述迁移UE列表中的UE迁移至所述低负荷邻区或高优先级邻区：
    在迁移切换策略为盲切换的情况下，向所述迁移UE列表中的UE下发切换指令以将所述UE切换至所述低负荷邻区或所述高优先级邻区，其中，所述切换指令中携带有低负荷邻区信息或高优先级邻区信息；
    在迁移切换策略为重定向的情况下，向所述迁移UE列表中的UE下发重定向指令以将所述UE重定向至所述低负荷邻区或所述高优先级邻区，其中，所述 重定向指令中携带有低负荷邻区的频点信息或高优先级邻区的频点信息；
    在迁移切换策略为基于测量的切换的情况下，向所述迁移UE列表中的UE下发对邻区的测量指令，并根据所述UE上报的测量报告，将所述UE切换到所述测量报告指示的邻区。
  18. 根据权利要求14或15所述的CU，其中，所述迁移模块还包括：
    采集单元，设置为采集第一小区的所有邻区的负荷，并根据所述所有邻区的负荷，从所述所有邻区中筛选出所述第一小区的低负荷邻区，将所述低负荷邻区的频点信息通知所述DU，其中，所述第一小区为所述DU通知的待进行UE迁移的小区，所述低负荷邻区为负荷低于预设门限的邻区。
  19. 一种分布单元DU，包括：
    监控模块，设置为监控第一小区中用户设备UE的状况，并将所述第一小区中符合迁出策略的UE加入迁移UE列表中；
    发送模块，设置为向集中单元CU发送所述迁移UE列表。
  20. 根据权利要求19所述的DU，其中，所述迁出策略包括以下至少之一：
    物理资源块PRB占用率超过设定门限的UE；
    误包率超过设定门限的UE；
    不含指定业务的UE；
    资源不能满足业务的服务质量QoS要求的UE；
    优先级低于设定优先级的UE。
  21. 根据权利要求19或20所述的DU，其中
    所述监控模块，还设置为监控所述DU下多个小区的负荷情况，将待进行UE迁移的所述第一小区通知所述CU，其中，所述第一小区为负荷高于第一预设门限的小区。
  22. 根据权利要求21所述的DU，其中，
    所述监控模块是设置为通过如下方式将待进行UE迁移的所述第一小区通知所述CU：在满足触发条件的情况下，向所述CU发送负荷指示消息以将所述第一小区通知所述CU，其中，所述触发条件包括以下至少之一：发现新增的高负荷小区、已经上报过的高负荷小区发生负荷变化达到第二预设门限。
  23. 根据权利要求22所述的DU，其中，所述负荷指示消息中包括以下至少之一：
    小区标识ID、小区负荷状态、小区上行剩余负荷、小区下行剩余负荷。
  24. 根据权利要求22所述的DU，其中，
    所述监控模块是设置为通过如下方式将所述第一小区中符合迁出策略的UE加入迁移UE列表中：将所述第一小区中符合迁出策略并支持迁移到低负荷邻区的至少一个频点的UE加入所述迁移UE列表中，其中，所述低负荷邻区为所述CU指示的所述第一小区的所有邻区中负荷低于第三预设阈值的邻区。
  25. 一种用户设备迁移***，包括权利要求14至18中任一项所述的集中单元CU，以及权利要求19至24中任一项所述的分布单元DU。
PCT/CN2019/118325 2018-11-15 2019-11-14 用户设备迁移方法、集中单元、分布单元及*** WO2020098730A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811362801.7 2018-11-15
CN201811362801.7A CN111194054B (zh) 2018-11-15 2018-11-15 用户设备迁移方法、集中单元、分布单元及***

Publications (1)

Publication Number Publication Date
WO2020098730A1 true WO2020098730A1 (zh) 2020-05-22

Family

ID=70710635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/118325 WO2020098730A1 (zh) 2018-11-15 2019-11-14 用户设备迁移方法、集中单元、分布单元及***

Country Status (2)

Country Link
CN (1) CN111194054B (zh)
WO (1) WO2020098730A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115022932A (zh) * 2022-06-02 2022-09-06 成都中科微信息技术研究院有限公司 一种提高nr***小区节能关闭时终端业务可靠性的方法及nr***
WO2024032328A1 (zh) * 2022-08-12 2024-02-15 大唐移动通信设备有限公司 配置信息处理方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114024833B (zh) * 2022-01-06 2022-04-01 深圳市聚能优电科技有限公司 Ems的后端服务器切换方法、***、设备及存储介质
CN117998481A (zh) * 2022-11-03 2024-05-07 华为技术有限公司 一种通信方法和通信装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150031360A1 (en) * 2013-07-26 2015-01-29 Samsung Electronics Co., Ltd. Method and device for load balancing in wireless communication system
CN104581827A (zh) * 2013-10-29 2015-04-29 ***通信集团公司 一种负载均衡方法和设备
CN108307425A (zh) * 2016-08-11 2018-07-20 财团法人资讯工业策进会 支持多连接性的通信***及其连接方法
CN108616933A (zh) * 2017-01-24 2018-10-02 电信科学技术研究院 一种中央单元-分布式单元架构下的通信处理方法及装置
CN108810968A (zh) * 2017-05-05 2018-11-13 北京三星通信技术研究有限公司 执行连接移动性调整的方法和设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11051259B2 (en) * 2015-11-02 2021-06-29 Qualcomm Incorporated Methods and apparatuses for an access procedure
CN107343299B (zh) * 2016-05-03 2021-01-05 株式会社Kt 用于改变ue的连接状态的方法和装置
CN108668312B (zh) * 2017-03-29 2021-10-26 华为技术有限公司 一种测量参数发送方法及其装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150031360A1 (en) * 2013-07-26 2015-01-29 Samsung Electronics Co., Ltd. Method and device for load balancing in wireless communication system
CN104581827A (zh) * 2013-10-29 2015-04-29 ***通信集团公司 一种负载均衡方法和设备
CN108307425A (zh) * 2016-08-11 2018-07-20 财团法人资讯工业策进会 支持多连接性的通信***及其连接方法
CN108616933A (zh) * 2017-01-24 2018-10-02 电信科学技术研究院 一种中央单元-分布式单元架构下的通信处理方法及装置
CN108810968A (zh) * 2017-05-05 2018-11-13 北京三星通信技术研究有限公司 执行连接移动性调整的方法和设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115022932A (zh) * 2022-06-02 2022-09-06 成都中科微信息技术研究院有限公司 一种提高nr***小区节能关闭时终端业务可靠性的方法及nr***
WO2024032328A1 (zh) * 2022-08-12 2024-02-15 大唐移动通信设备有限公司 配置信息处理方法及装置

Also Published As

Publication number Publication date
CN111194054A (zh) 2020-05-22
CN111194054B (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
WO2020098730A1 (zh) 用户设备迁移方法、集中单元、分布单元及***
CN111182601B (zh) 用于小区测量和特殊功能小小区选择的装置和方法
CN104917600B (zh) 载波聚合场景下的成员载波配置方法、设备及***
EP2800414B1 (en) Load balancing method and related device
EP2563065B1 (en) Method and device for updating coordinated multi-point transmission set
CN104581810B (zh) 一种基于载波聚合的切换方法、板间聚合切换方法和装置
US20200163144A1 (en) Method and apparatus for transmitting and receiving signals in wireless communication system
US20130183970A1 (en) Method of notifying switching information and base station
CN108243505B (zh) 一种资源调度方法及装置
JP2013518486A (ja) 付加的な測定結果の報告方法及びシステム
CN104902569A (zh) 由wtru实现的用于执行无线电链路监控的方法及wtru
JP2012516086A (ja) アップリンク・キャリア周波数を管理する方法、装置及びシステム
CN104782205A (zh) 在无线通信***中支持载波聚合组的方法和设备
CN101273556A (zh) 移动通信小区改变过程
CN105917700A (zh) 控制在小区边缘附近操作的高优先级的用户设备的切换
WO2016011752A1 (zh) 负荷均衡方法及装置
CN105554818A (zh) 一种负荷均衡方法和装置
EP2727397A1 (en) Method and apparatus for terminal measurement configuration in multi-radio access technology environment
WO2012152335A1 (en) Saving energy in muliti - rat communication network
CN104854940A (zh) 用户装置以及发送控制方法
WO2015096088A1 (zh) 信道测量配置方法、信道测量方法、装置和通信***
CN107172635B (zh) 数据传输的方法及***
CN113766643A (zh) 波束失败恢复方法、装置及设备
CN109257773B (zh) 一种负载均衡的方法和装置
CN112770339B (zh) 一种协作小区确定方法及装置

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: 19884461

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: 19884461

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 15/09/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19884461

Country of ref document: EP

Kind code of ref document: A1