CN115665811A

CN115665811A - Method and apparatus for performing connection mobility adjustment

Info

Publication number: CN115665811A
Application number: CN202211276567.2A
Authority: CN
Inventors: 汪巍崴; 许丽香; 王弘; 柯小婉
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2017-05-05
Filing date: 2017-05-05
Publication date: 2023-01-31
Also published as: CN108810968B; CN108810968A

Abstract

The present disclosure provides a concentration unit and a distribution unit of a base station and a method of performing connection mobility parameter adjustment through their cooperation. The method comprises the following steps: sending a resource state request message to a distribution unit of a base station; a resource status response message is received from a distribution unit of the base station. The method can improve the accuracy of the connection mobility parameter setting.

Description

Method and apparatus for performing connection mobility adjustment

Technical Field

The present application relates generally to wireless communication technology, and more particularly, to a method and apparatus for performing connection mobility adjustment.

Background

Modern mobile communications are increasingly tending to provide higher mobile bandwidth, less latency, support for a large number of terminal services, which generally requires more efficient resource management and scheduling in support of virtualization of network functions. For this purpose, the base station (gNB) of a next generation mobile communication system, such as a 5G mobile communication system, is divided into a centralized unit (gNB-CU) and a distributed unit (gNB-DU), rather than being considered as a single functional entity as the base station (eNB) in a conventional LTE network. Connection mobility adjustment performed by the base station is no longer applicable to the mechanisms in the eNB, since the separation between the gNB-DU and the gNB-CU is no longer an internal implementation of a single functional entity. Currently there is no provision for how to implement the connection mobility adjustment in the gNB.

Therefore, a new mechanism for performing connection mobility adjustment in the gbb is needed.

Disclosure of Invention

The present disclosure is directed to a mechanism for performing connection mobility parameter adjustment through cooperation of a centralized unit and a distributed unit of a base station.

According to a first aspect of the invention, a method is provided which is performed in a concentration unit of a base station. The method comprises the following steps: sending a connection mobility adjustment request message to a distribution unit of a base station; a connection mobility adjustment acknowledgement message from a distribution unit of a base station is received.

According to a second aspect of the invention, a concentration unit of a base station is provided. The concentration unit includes: a transmit module configured to: sending a connection mobility adjustment request message to a distribution unit of a base station; a receiving module configured to: a connection mobility adjustment acknowledgement message from a distribution unit of a base station is received.

According to a third aspect of the present invention, there is provided a method performed in a distribution unit of a base station, comprising: receiving a connection mobility adjustment request message from a central unit of a base station; in response to the received connection mobility adjustment request message, a connection mobility adjustment confirm message is transmitted to the central unit of the base station.

According to a fourth aspect of the present invention, a distribution unit of a base station is provided. The distribution unit includes: a receiving module configured to: receiving a connection mobility adjustment request message from a central unit of a base station; and a transmitting module configured to: in response to the received connection mobility adjustment request message, a connection mobility adjustment confirmation message is sent to the central unit of the base station.

Drawings

The above and other features of the present disclosure will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:

fig. 1 schematically shows a system architecture diagram of an example of a next generation mobile communication system;

fig. 2 schematically shows a structural diagram of an example of a base station of a next generation mobile communication system;

fig. 3A and 3B schematically show a schematic diagram of a method of performing connection mobility adjustment according to a first embodiment of the present disclosure;

fig. 4A and 4B schematically show a schematic diagram of a method of performing connection mobility adjustment according to a second embodiment of the present disclosure;

fig. 5A and 5B schematically show a schematic diagram of a method of performing connection mobility adjustment according to a third embodiment of the present disclosure;

fig. 6A and 6B schematically show a schematic diagram of a method of performing connection mobility adjustment according to a fourth embodiment of the present disclosure;

fig. 7A and 7B schematically illustrate a method of performing connection mobility adjustment according to a fifth embodiment of the present disclosure;

fig. 8 schematically shows a schematic diagram of a method of performing connection mobility adjustment according to a sixth embodiment of the present disclosure;

fig. 9 schematically shows a schematic diagram of a method of performing connection mobility adjustment according to a second embodiment of the present disclosure;

fig. 10 is a block diagram schematically showing a structural example of a concentration unit of a base station according to an embodiment of the present disclosure;

fig. 11 schematically shows a block diagram of a structural example of a distribution unit of a base station according to an embodiment of the present disclosure.

In the drawings, like reference numerals designate identical or similar elements.

Detailed Description

The present disclosure is described in detail below with reference to the figures and specific embodiments. It should be noted that the present disclosure should not be limited to the particular embodiments described below. In addition, for the sake of brevity, detailed descriptions of well-known technologies not directly related to the present disclosure are omitted to prevent confusion of understanding of the present disclosure.

Fig. 1 schematically shows a system architecture diagram of an example of a next generation mobile communication system, such as a fifth generation 5G mobile communication system. As shown in the figure, the system mainly includes a User Equipment (UE) 11, a next generation radio Access Network (NG-RAN) 12, an Access control and Mobility Management Function (AMF) 13, a User Plane Function (UPF) 14, a Session Management Function (SMF) 15, and a Data Network (DN) 16. Among them, the access control and mobility management function entity (AMF) 13, the user plane function entity (UPF) 14, and the session management function entity (SMF) 15 can be considered to be located in the next generation core network (e.g. 5 GC). It should be understood that the devices in the figures are for illustrative purposes only and that the system may include a number of UEs, one or more radio access networks, one or more data networks, and other devices, etc.

The User Equipment (UE) 11 is a terminal device for receiving data. As used herein, the terms "user equipment" and "UE" may refer in some cases to mobile devices such as mobile phones, personal digital assistants, handheld or laptop computers, and similar devices having communication capabilities. In other cases, the terms "user equipment" and "UE" may also refer to devices that have similar capabilities but are not portable, such as desktop computers, set-top boxes, or network devices.

The next generation radio access network (NG-RAN) 12 is a radio access network. The NG-RAN12 includes a base station that provides access to the radio network interface for the UE. The base station may be a next generation base station (gbb) or an eNB connected to a next generation core network (e.g., 5 GC).

An access control and mobility management function (AMF) 13 is responsible for managing mobility context and security information of the UE, etc.

A user plane function entity (UPF) 14 mainly provides functions of the user plane.

The Session Management Function (SMF) 15 is responsible for session management.

The Data Network (DN) 16 contains services like the operator, access to the internet and a third party service NG1 is the interface between the UE and the AMF.

NG-C is the control plane interface between the AMF and the NG-RAN. NG-U is the user plane interface between NG-RAN and UPF. NG6 is the interface between the UPF and DN. NG4 is the interface between the UPF and SMF.

Fig. 2 schematically shows a structural diagram illustrating an example of a base station (e.g., a gNB) of a next generation mobile communication system (e.g., a 5G mobile communication system). As shown, in some embodiments, to support virtualization of network functions, more efficient resource management and scheduling, the gNB may be divided into a centralized unit (gNB-CU) 30 and a distributed unit (gNB-DU) 40, with a standardized public interface F1 supported between the centralized unit and the distributed unit. It should be understood that although 2 gNB-DUs are shown in the figure, a gNB may include more or fewer gNB-DUs. For simplicity, hereinafter, the centralized unit (gNB-CU) and the distributed unit (gNB-DU) of the gNB are also referred to simply as CU and DU, respectively. CUs provide Service Data Adaptation Protocol (SDAP), packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC). The DU provides functions of a radio link control protocol (RLC), medium Access Control (MAC), and a physical layer, etc.

As can be seen from fig. 2, the base station (gNB) in the 5G mobile communication system can not be considered as a single functional entity like the base station (eNB) in the conventional LTE, but is divided into two functional entities, CU and DU, which implement different functions. In a conventional LTE network, a base station is generally regarded as a functional entity, and the interaction between all functions of the entity can be regarded as internal implementation. However, in a 5G mobile communication system, a base station in the conventional sense is divided into different functional entities CU and DU, and functions contained in the CU and DU need to interact with each other through an F1 interface if necessary. The CU provides a Connection Mobility Control (CMC) function. Connection mobility control relates to management of radio resources in idle and mobile states, such as setting and/or adjusting of connection mobility parameters. Examples of the connection mobility parameters are cell selection/reselection related parameters, cell handover related parameters, etc. To enable the setting and/or adjustment of the connection mobility parameters, the RRC function in the CU needs to generate the set and/or adjusted values of these connection mobility parameters and deliver them to other protocol layers below it (e.g., PDCP, RLC, MAC and physical layers) to inform the UE. To accomplish the setting and/or adjustment of these connection mobility parameters, reference is made to the following information, including but not limited to: the measurement information of the downlink channel of the user, the measurement information of the uplink channel, the load information of the neighboring cell, the distribution information of the data flow, the resource information of the transmission network (i.e. the link connecting different functional entities, including but not limited to the link connecting CU and DU, the link connecting two CUs, the link connecting CU and other gnbs, etc.) and hardware, the policy of the operator, etc. Details of the information may refer to, for example, an initialization process of resource status reporting and an update process of resource status (Section 8.3.6 and Section 8.3.7) in ts36.423v14.2.0 (2017-03). Some of the above information, such as uplink channel measurement information, to which the setting and/or adjustment of the connection mobility parameters needs to be referred, is only known to the DUs. The uplink channel measurement information may include, for example, one or more of the following signal measurements: measurement of uplink reference signals, measurement of uplink data signals, measurement of uplink random access signals, and the like. Therefore, a mechanism is needed to allow these DU-only aware information to help CUs to set and/or adjust the connection line mobility parameters.

It should be understood that the terms "CMC-related parameter" and "connection mobility parameter" may be used interchangeably herein. The setting of a parameter may be regarded as a special case of an adjustment of a parameter, so for the sake of brevity, the term "setting and/or adjustment of a parameter" is also referred to simply as "adjustment of a parameter" in the following, unless otherwise indicated.

The following describes in detail various embodiments according to the present disclosure, taking a 5G mobile communication system as an example application environment. Hereinafter, unless otherwise explicitly indicated, a base station refers to a base station gNB of a 5G mobile communication system that includes different functional entities CU and DU. However, those skilled in the art will appreciate that the present disclosure is not limited to the gNB and may also be applied to other base stations comprising different functional entities. The present disclosure is not limited to the following embodiments, but is applicable to more other wireless communication systems, for example, mobile communication systems after 5G.

As previously mentioned, the connection mobility parameters in the present disclosure are mobility related parameters, such as cell selection/reselection related parameters, cell handover related parameters, and the like. Cell selection/reselection related parameters such as cell selection or reselection threshold values, etc. Cell handover related parameters such as threshold values for triggering handover preparation procedures for a particular neighbor cell, etc.

As mentioned previously, the uplink channel measurement information in the present disclosure may include, for example, one or more of the following signal measurements: measurement of uplink reference signals, measurement of uplink data signals, measurement of uplink random access signals, and the like.

In addition, in the present invention, the message name is only an example and not a limitation, and it may be replaced with other names as long as the message can transfer the specified information.

Fig. 10 schematically shows a block diagram of a concentration unit of a base station, gNB-CU 30, according to an embodiment of the present disclosure.

As shown, CU 30 may include a sending module 31, a receiving module 32, and a processing module 33.

The sending module 31 may be configured to: a message is sent to the distribution unit.

The receiving module 32 may be configured to: a message is received from a distribution unit.

The processing module 33 may be configured for overall control of the central unit gNB-CU 30. In particular, the processing module 33 may be configured to generate messages to be sent, parse received messages, perform connection mobility adjustments, and the like.

Fig. 11 schematically shows a block diagram of a distribution unit gbb-DU 40 of a base station according to an embodiment of the present disclosure.

As shown, the DU 40 may include a transmitting module 41, a receiving module 42, and a processing module 43.

The sending module 41 may be configured to: a message is sent to the central unit.

The receiving module 42 may be configured to: a message is received from a central unit.

The processing module 43 may be configured for overall control of the distribution unit gNB-DU 40. In particular, the processing module 43 may be configured to generate messages to be sent, parse received messages, and the like.

It should be understood that the above illustrated configurations of the concentration unit and the distribution unit of the base station are only illustrative and not restrictive. The sending module and the receiving module in the centralized unit or the distributed unit may be separate modules, or may be integrated together to be a transceiver module. Furthermore, the concentration unit and/or the distribution unit may comprise further modules, for example modules that may be developed or that may be developed in the future, which may be used for the base station concentration unit or the distribution unit, etc.

The concentration unit 30 and the distribution unit 40 in fig. 10 and 11 may cooperate to perform connection mobility adjustments. The specific operation of the gNB-CU and gNB-DU will be described in detail below with reference to various embodiments.

Example 1

Fig. 3A and 3B schematically illustrate a first method of performing connection mobility adjustment according to a first embodiment of the present disclosure. In this embodiment, the gNB-CU initiates a request for resource status to the gNB-DU. Fig. 3A shows a situation where the request is successful or at least partially successful. Fig. 3B shows a case where the request fails.

As shown in fig. 3A, the method begins at step 301.

In step 301, the gNB-CU sends a gNB-DU resource status request Message (gNB-DUresource status request Message) to the gNB-DU. The gbb-DU resource status request message may contain one or a combination of the following information:

-identity information of the gNB-DU.

-requiring the gNB-DU to report indication information of uplink channel measurement information to the gNB-CU.

-a list of cells to which said information to be reported belongs. The information of this list indicates that the gNB-CU requests the gNB-DU to report the above information of the cells in the list.

-reporting periodic or triggering information of said information.

■ If the information of the requested report needs to be reported periodically by the gNB-DU, the request message contains periodic information. In some implementations, the period for reporting the above information may be different for different cells, and thus the request message may give different reporting period information for different cells. In other implementations, the information of each cell may be reported according to the same periodicity, and the request message may provide a common report period information.

■ If the above-mentioned information of requested report needs to be triggered by the gNB-DU according to the occurrence of a specific event, the event information triggering the gNB-DU to report will be included in the request message. Examples of such triggering events are: the average value of the uplink channel measurement results is smaller than a first threshold; the minimum value of the uplink channel measurement result is less than a second threshold; the uplink channel measurement result shows that the UE smaller than the third threshold is larger than the fourth threshold; cell load changes, etc. The setting of the trigger event may be different for each cell or may be the same. Thus, in some implementations, the same trigger event may be set. In other implementations, different trigger thresholds for the same trigger event may be set for different cells. In still other implementations, different trigger events may be set for different cells.

■ If some cells report periodically and some cells report event-triggered for the information of the requested report, the request message may include a reporting period set for the periodically reported cells and a trigger event set for the cell that reports event-triggered. The reporting period and the trigger event may be set according to the corresponding manners described above.

-measurement identity information related to the uplink channel measurement. As assigned by the gNB-CU, corresponding to the report of the uplink channel measurements.

Indication information related to controlling the reporting of the uplink channel measurement information, such as start of measurement, stop of measurement, etc.

If the gNB-DU is capable of performing the measurements or at least part of the measurements requested by the gNB-CU, the method proceeds to step 302.

In step 302, the gNB-DU sends a gNB-DU resource status response Message (gNB-DU resource status response Message) to the gNB-CU. The gbb-DU resource status response message may contain one or a combination of the following information:

-measurement identity information contained in the received gNB-DU resource status request message.

-measurement identity information allocated by the gNB-DU relating to the uplink channel measurements. This identification information, in combination with the measurement identification information contained in the gNB-DU resource status request message, can uniquely characterize the uplink channel measurement report.

-some cells may be able to perform and some cells may not be able to perform for measurements requested in the gNB-DU resource status request message. Thus, the gNB-DU may indicate in the gNB-DU resource status response messageCan carry out Requested measurement and reporting cell list, and/or requested measurement and reporting cell list not available. Preferably, in case that a cell list for which the requested measurement and report cannot be performed is indicated in the gNB-DU resource status response message, a reason for the inability may also be indicated.

In step 303, the gNB-DU sends a resource status update Message (gNB-DU resource status update Message) to the gNB-CU. And if the gNB-DU is indicated in the gNB-DU resource state request message to report periodically, reporting by the gNB-DU according to the period in the request message. And if the gNB-DU is indicated in the gNB-DU resource state request message to carry out event trigger reporting, reporting the gNB-DU after the trigger event is met. The resource status update message may include one or more of the following information:

cell ID, identity of the Cell to which the measured uplink signal belongs.

-user ID, identity of UE to which the measured uplink signal belongs.

-measured signal strength of uplink signals from the UE indicated by the user ID, such as Reference Signal Received Power (RSRP), received Signal Strength Indication (RSSI), signal energy. The signal strength information may be actual measurement results or quantized results (e.g., 0 to 100,0 for minimum signal strength and 100 for maximum signal strength)

-measured signal quality of uplink signals from the UE indicated by the user ID, such as Reference Signal Received Quality (RSRQ). Similarly, the signal quality information may be actual measurement results or quantized results (e.g., 0 to 100,0 indicating the worst signal quality and 100 indicating the best signal quality).

Measured levels (e.g. intensity level or quality level) of uplink signals from the UE indicated by the user ID, e.g. low (low), medium (medium), high (high). The above-mentioned level decision may be determined by the concrete implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the level is low; above the fifth threshold, the level is high; between the fourth and fifth thresholds, the rank is medium.

-a measurement result representing the signal strength/signal quality of the uplink signals of all UEs in the Cell indicated by the Cell ID, such as the average of the measurement results of all UEs. The measurement result may be an actual measurement result or a quantized result (e.g., 0 to 100, where 0 indicates minimum signal strength/worst signal quality and 100 indicates maximum signal strength/best signal quality).

It is easily understood that when the resource status update message includes the measured signal strength, signal quality and/or level of the uplink signal from the UE indicated by the user ID, the resource status update message needs to include the user ID. When the resource status update message includes the above-described measurement results indicating the signal strength/signal quality of the uplink signals of all UEs in the Cell indicated by the Cell ID, the user ID may not be included.

In step 304, the gNB-CU performs connection mobility parameter adjustment according to the obtained measurement result of the uplink signal and other information. This step 304 may be performed by a processing module. Such other information includes, but is not limited to: measuring information of a downlink channel of a user; load information of neighboring cells; distribution information of the data stream; transport network (i.e., links connecting different functional entities, including but not limited to links connecting CUs and DUs, links connecting two CUs, links connecting one CU and another gNB, etc.) and hardware resource information; operator policy, etc. to make connection mobility parameter adjustments.

Fig. 3B shows the situation when the gbb-DU is not capable of making measurements requested by the gbb-CU, which may feed back a failure message.

As shown, step 301 in fig. 3B is the same as 301 in fig. 3A.

In step 301, the gNB-CU sends a gNB-DU resource status request Message (gNB-DU resource status request Message) to the gNB-DU.

When the gNB-DU is not capable of performing the measurements requested by the gNB-CU, it proceeds to step 302a.

In step 302a, the gNB-DU sends a gNB-DU resource status failure Message (gNB-DU resource status failure Message) to the gNB-CU.

In some implementations, the gNB-DU resource status failure message may simply indicate that the gNB-DU resource status request cannot be responded to.

In other embodiments, the gNB-DU resource status failure message may indicate more information, for example, may include one or more of the following information:

-measurement identity information allocated by the gNB-DU in relation to the uplink channel measurement information. This identification information, in combination with the measurement identification information contained in the gNB-DU resource status request message, can uniquely characterize the uplink channel measurement report.

For measurements requested in the gNB-DU resource status request message, the gNB-DU may indicate in the gNB-DU resource status failure message the list of cells for which the requested measurements and reports cannot be made, and the reason for the inability to be made.

Example 2

Fig. 4A and 4B schematically illustrate a second method of performing connection mobility adjustment according to a second embodiment of the present disclosure. In this embodiment, the connection mobility adjustment request is initiated by the gNB-CU. Fig. 4A illustrates a situation where the adjustment request is accepted or at least partially accepted. Fig. 4B shows a case where the adjustment request fails.

As shown in fig. 4A, the method begins at step 401.

In step 401, the gNB-CU sends a gNB connection mobility adjustment request Message (gNB connection mobility adjustment Message) to the gNB-DU. The gNB connection mobility adjustment request message may contain one or a combination of the following information:

-cell identity information

The cell identification information identifies the cell for which the connection mobility parameters need to be adjusted.

■ In some implementations, the cell identification information for the cell for which the connection mobility parameter needs to be adjusted includes an identification of a cell. The cell may belong to the gNB-DU which received the message, or may belong to other gNB-DUs.

■ In other implementations, the cell identification information for the cell for which the connection mobility parameter needs to be adjusted may include the identification of two or more cells. The two or more cells may belong to the same gNB-DU, or may belong to different gNB-DUs under the same gNB-CU, or may belong to different gnbs.

-adjustment recommendation information for connection mobility parameters

The adjustment suggestion information of the connection mobility parameter may be suggestion that the gNB-CU provides for adjusting the connection mobility parameter for the cell corresponding to the above-mentioned each cell identification information.

The adjustment recommendation information of the connection mobility parameters may include at least one of the following information:

■ Information of delayed or advanced cell selection/reselection/handover suggested by the gNB-CU. It may be an indication message, e.g. suggested by the gNB-CU to delay or advance the handover by adjusting mobility parameters. For example, if the information is a first value (e.g., 0) indicating that the gNB-CU may delay the user handover of the cell by adjusting the mobility parameter. Otherwise, if the value is the second value (e.g. 1), it indicates that the gNB-CU advances the user handover of the cell by adjusting the mobility parameter.

■ Reference value for parameter adjustment for mobility of connections suggested by gNB-CU

■ Reference value range for parameter adjustment for mobility of connection suggested by gNB-CU (which can be expressed by the maximum and minimum values of the range)

In some implementations, the adjustment recommendation information may be different for each cell. In other implementations, the adjustment recommendation information for each cell may be the same. In still other implementations, the cells to be adjusted may be divided into multiple groups. The principle of dividing groups may be, for example: the reason for adjusting the connection mobility parameters of the cells in the same group is the same; the cells in the same group will affect each other when adjusting the mobility parameters; and so on. In the implementation of cell grouping, a pin may be used

Corresponding advice information is given for each cell in each group, as shown in table 1 below.

TABLE 1

-reason for connection mobility parameter adjustment.

The reason for the connection mobility parameter adjustment indicates a specific reason why the gNB-CU suggests the connection mobility parameter adjustment, such as load balancing, handover optimization, and the like. For example, if there are multiple cells or groups of cells to be adjusted, the cause may be given separately for each cell or may be given for each cell group.

In step 402, the gNB-DU replies to the gNB-CU with a gNB connection mobility adjustment acknowledgement Message (gNB connection mobility adjustment Message). The gNB connection mobility adjustment confirm message is an acknowledgement to the gNB connection mobility adjustment request message. The gNB-DU determines whether the adjustment proposal information of the connection mobility parameters proposed by the gNB-CU is available according to the obtained information (such as the uplink channel quality information, the downlink channel quality information and the like), and informs the gNB-CU of the confirmation result. The gNB connection mobility adjustment confirm message may contain one or more of the following information:

-cell identities corresponding to feasible proposal information;

-cell identity corresponding to the unfeasible proposal information.

Optionally, in some implementations, the gNB connection mobility adjustment confirm message may further include additional information for the cell to which the feasible suggested information corresponds; and/or additional information for cells to which the proposed information is not feasible.

The additional information for the cell to which the feasible proposal information corresponds may for example comprise further adjustment proposal information given by the gNB-DU.

■ For example, if the adjustment recommendation information for the connection mobility parameter of the cell given by the gNB-CU in step 401 is a reference value range for parameter adjustment of connection mobility, the confirmation message may include a reference value for parameter adjustment of connection mobility corresponding to the recommended connection mobility of the cell (the reference value is within the recommended reference value range).

The additional information for the cell to which the infeasible advice information corresponds may include, for example, at least one of the following information given by the gNB-CU:

new adjustment recommendation information for connection mobility parameters of cells corresponding to the impracticable recommendation information;

uplink for cell to be adjusted included in connection mobility adjustment request messageChannel measurement information; and/or

Suggesting an unacceptable reason.

In particular, there may be several ways for the new adjustment recommendation information given by the gNB-CU for the connection mobility parameters of the cell corresponding to the infeasible recommendation information.

■ For example, if the suggested adjustment information for the connection mobility parameters of the cell given by the gNB-CU in step 401 is information of delaying or advancing cell selection/reselection/handover, the suggested information for the cell given by the gNB-DU may be included in the confirmation message, such as a suggested information or parameter invariance about delaying or advancing cell selection/reselection/handover, or a suggested reference value for parameter adjustment of connection mobility, or a suggested reference value range for parameter adjustment of connection mobility.

■ If the adjustment recommendation information for the connection mobility parameter of the cell given by the gNB-CU in step 401 is a reference value for parameter adjustment of connection mobility, the range of reference values for parameter adjustment recommended by the gNB-DU for the cell may be included in the confirmation message.

■ If the adjustment recommendation information for the connection mobility parameter for the cell given by the gNB-CU in step 401 is the reference value range for parameter adjustment of connection mobility, a new reference value range for parameter adjustment recommended by the gNB-DU for the cell or a recommended reference value for parameter adjustment may be included in the confirmation message.

Specifically, in some implementations, the gNB connection mobility adjustment confirm message includes uplink channel measurement information of the cell served by the gNB-DU and appearing in the request message in step 401, which may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

■ The measured signal strength of the uplink signal from the UE indicated by the user ID, such as RSRP, RSSI, signal energy. The intensity information may be actual measurements or quantized results (e.g., 0 to 100,0 indicating minimum signal intensity and 100 indicating maximum signal intensity).

■ The measured signal quality of the uplink signal from the UE indicated by the user ID, e.g., RSRQ. The signal quality information may be actual measurement results or quantized results (e.g., 0 to 100,0 indicating the worst signal quality and 100 indicating the best signal quality).

■ The measured level (e.g., strength level or quality level) of the uplink signal from the UE indicated by the user ID is low (low), medium (medium), and high (high). The above-mentioned level decision may be determined by the concrete implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the level is low; if the grade is higher than the fifth threshold, the grade is high; between the fourth and fifth thresholds, the rank is medium.

■ The Cell ID indicates a measurement result of the signal strength/signal quality of uplink signals of all UEs in the Cell, such as an average value of the measurement results of all UEs. The measurement result may be an actual measurement result or a quantized result (e.g., 0 to 100, where 0 indicates minimum signal strength/worst signal quality and 100 indicates maximum signal strength/best signal quality).

In particular, in some implementations, the gNB connection mobility adjustment confirm message may include a reason why the adjustment recommendation for the connection mobility parameters for the cell given by the gNB-CU in step 401 is not accepted.

Then, in step 403, the gNB-CU performs connection mobility parameter adjustment according to the received gNB connection mobility adjustment acknowledgement. This step may be performed by a processing module.

Fig. 4B shows a case where the adjustment fails. Step 401 in fig. 4B is the same as in fig. 4A.

In step 401, the gNB-CU sends a gNB connection mobility adjustment request Message (gNB connection mobility adjustment Message) to the gNB-DU.

If the gNB-DU does not agree with the proposed information of all cells given by the gNB-CU, it proceeds to step 402a.

In step 402a, the gNB-DU may reply to the gNB-CU with a gNB connection mobility adaptation failure Message (gNB connection mobility adaptation Message).

In some implementations, the gNB connection mobility adjustment failure message may simply indicate that the gNB-DU connection mobility adjustment request cannot be responded to.

In other embodiments, the gNB connection mobility adjustment failure message may indicate more information, which may include, for example: cell identity corresponding to the not-feasible advice information. Optionally, in some implementations, the gNB connection mobility adjustment failure message may further include additional information for a cell corresponding to the infeasible suggested information, for example, at least one of the following information may be included:

uplink channel measurement information for a cell to be adjusted included in the connection mobility adjustment request message; and/or

Reason why the parameter adjustment is unsuccessful.

In particular, there may be a plurality of ways for the new adjustment recommendation information given by the gNB-CU for the connection mobility parameters of the cell corresponding to the infeasible recommendation information.

■ If the adjustment recommendation information for the connection mobility parameter for the cell given by the gNB-CU in step 401 is the reference value range for parameter adjustment of connection mobility, a new reference value range or a recommended reference value for parameter adjustment proposed by the gNB-DU for the cell may be included in the confirmation message.

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

■ The measured signal strength of the uplink signal from the UE indicated by the user ID, such as RSRP, RSSI, signal energy. The intensity information may be actual measurement results or quantized results (e.g., 0 to 100,0 indicating minimum signal intensity and 100 indicating maximum signal intensity).

■ The measured signal quality of the uplink signal from the UE indicated by the user ID, such as RSRQ. The signal quality information may be actual measurement results or quantized results (e.g., 0 to 100,0 indicating the worst signal quality and 100 indicating the best signal quality).

■ The measured level (e.g., intensity level or quality level) of the uplink signal from the UE indicated by the user ID, e.g., low (low), medium (medium), high (high). The above-mentioned level decision can be determined by the particular implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the level is low; above the fifth threshold, the level is high; between the fourth and fifth thresholds, the rank is medium.

■ And a measurement result representing the signal strength/signal quality of uplink signals of all UEs in the Cell indicated by the Cell ID, such as an average value of the measurement results of all UEs. The measurement result may be an actual measurement result or a quantized result (e.g., 0 to 100, where 0 indicates minimum signal strength/worst signal quality and 100 indicates maximum signal strength/best signal quality).

Example 3

Fig. 5A and 5B schematically show a third schematic diagram of a method of performing connection mobility adjustment according to a third embodiment of the present disclosure. The method of embodiment 3 is similar to the method of embodiment 2, except that the connection mobility adjustment is initiated by the gNB-DU, and the gNB-DU first sends the gNB connection mobility adjustment requirement to the gNB-CU, and then the operation is similar to the method of embodiment 2. Fig. 5A illustrates a situation where the adjustment request is accepted or at least partially accepted. Fig. 5B shows a case where the adjustment request fails.

As shown in fig. 5A, the method begins at step 501.

In step 501, the gNB-DU sends a gNB connection mobility adjustment required Message (gNB connection mobility adjustment request Message) to the gNB-CU. The gNB connection mobility adjustment required message may contain one or more of the following information:

cell identity information of cells requiring adjustment of connection mobility parameters

■ The cell identification information may be an identification of one cell, an identification of two cells, or an identification of more than two cells.

Alternatively, the cell identification information may be divided into a plurality of groups, each group may contain the identities of one or two or more cells. The principle of dividing groups may be, for example: the reason for adjusting the connection mobility parameters of the cells in the same group is the same; the cells in the same group will affect each other when adjusting the mobility parameters; and so on.

-uplink channel measurement information of the cell served by the gNB-DU and appearing in the demand message

The information may include one or more of the following:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identification of the user to which the measured uplink signal belongs

■ The measured signal strength of the uplink signal from the UE indicated by the user ID, such as RSRP, RSSI, signal energy. The intensity information may be the actual measurement result or the quantized result (e.g., 0 to 100,0 indicates the minimum signal intensity and 100 indicates the maximum signal intensity).

■ The measured signal quality of the uplink signal from the UE indicated by the user ID, such as RSRQ. The signal quality information may be an actual measurement result or a quantized result (for example, 0 to 100,0 indicates the worst signal quality, and 100 indicates the best signal quality).

■ The measured level (e.g., intensity level or quality level) of the uplink signal from the UE indicated by the user ID, e.g., low (low), medium (medium), high (high). The above-mentioned level decision may be determined by the concrete implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the level is low; above the fifth threshold, the level is high; between the fourth and fifth thresholds, the rank is medium.

Reasons for adjusting the mobility parameters of the connection, such as load balancing, handover optimization, etc. The reason information may be given separately for each cell, or for each cell group if the cells are grouped.

The method then proceeds to step 502.

In step 502, the gNB-CU sends a gNB connection mobility adjustment Message (gNB connection mobility adjustment Message) to the gNB-DU. The gNB connection mobility adjustment Message (gNB connection mobility adjustment Message) may be regarded as a specific type of the gNB connection mobility adjustment request Message in embodiment 2. The adjustment message may contain, for each cell represented by the cell identity in step 501, one or more of the following information:

-cell identity information

In particular, the cell identification information herein may include a part or all of the cell identification information of the cell for which the connection mobility parameter needs to be adjusted, which is included in the demand message of step 501.

-adjustment recommendation information for connection mobility parameters

This is the proposed information of mobility parameter adjustment given by the gNB-CU for the cell corresponding to the above cell identification information.

The adjustment recommendation information of the connection mobility parameter may include at least one of the following information:

■ Information of delayed or advanced cell selection/reselection/handover suggested by the gNB-CU. It may be an indication message, e.g. suggested by the gNB-CU to delay or advance the handover by adjusting mobility parameters. For example, if the information is a first value (e.g., 0) indicating that the gNB-CU may delay the user handover of the cell by adjusting the mobility parameter. Otherwise, if the value is a second value (e.g. 1), it indicates that the gNB-CU will advance the user handover of the cell by adjusting the mobility parameter.

Similar to embodiment 2, in some implementations, the adjustment recommendation information may be different for each cell. In other implementations, the adjustment recommendation information for each cell may be the same. In still other implementations, the cells to be adjusted may be divided into multiple groups. In the implementation of cell grouping, corresponding recommendation information may be given for each cell in each group.

In addition, for the cell without changing the connection mobility parameter, the method may be implemented by only including the cell identifier without the adjustment suggestion information in step 502, or may be implemented by not including the corresponding cell identifier.

In step 503, the gNB-DU transmits a gNB connection mobility adjustment acknowledgement Message (gNB connection mobility adjustment Message) to the gNB-CU. The acknowledgement message is similar to the acknowledgement message in step 402 in embodiment 2. In this embodiment, the confirmation message may contain one or more of the following information:

cell identity corresponding to the proposed information available in step 502

Optionally, if the recommendation information is a reference range for parameter adjustment of connection mobility, a recommended reference value may be included. In one embodiment, the reference value is within a reference value range of a proposed parameter adjustment, and in another embodiment, the reference value may not be within a reference value range of a proposed parameter adjustment.

If the recommendation information of only part of the cells is feasible, the message will include the above information in the manner described above for the cells where the recommendation information is feasible, and at least one of the following messages for the cells where the recommendation information is not feasible:

-identification of non-feasible cells

-advice information on infeasible cells

■ If the recommendation information for the cell in step 502 is information of delayed or advanced cell selection/reselection/handover, the recommendation information for the cell given by the gNB-DU may be included in the confirmation message, such as a recommendation that the parameters or information about delayed or advanced cell selection/reselection/handover are not changed, or a recommendation that the parameters of the connection mobility are adjusted.

■ If the proposed information for the cell in step 502 is a reference value for parameter adjustment, the message may contain a range of parameter adjustment reference values proposed for the cell

■ If the proposed information for the cell in step 502 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for parameter adjustment proposed for the cell may be included in the message

The uplink channel measurement information of the cell served by the gNB-DU and not feasible with the recommendation of step 502 may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identification of user to which measured uplink signal belongs

■ The measured level (e.g., intensity level or quality level) of the uplink signal from the UE indicated by the user ID, e.g., low (low), medium (medium), high (high). The above-mentioned level decision may be determined by the concrete implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the rank is low; if the grade is higher than the fifth threshold, the grade is high; between the fourth and fifth thresholds, the rank is medium.

■ And a measurement result representing the signal strength/signal quality of uplink signals of all UEs in the Cell indicated by the Cell ID, such as an average value of the measurement results of all UEs. The measurement result may be an actual measurement result or a quantized result (for example, 0 to 100, where 0 indicates minimum signal strength/worst signal quality and 100 indicates maximum signal strength/best signal quality).

-suggesting reasons for not being accepted.

Then, in step 504, the gNB-CU performs connection mobility parameter adjustment according to the received gNB connection mobility adjustment acknowledgement. This step may be performed by a processing module.

Fig. 5B shows a case where the adjustment fails. Steps 501 and 502 in fig. 5B are the same as in fig. 5A.

In step 501, the gNB-DU sends a gNB connection mobility adjustment required message to the gNB-CU.

In step 502, the gNB-CU sends a gNB connection mobility adjustment message to the gNB-DU.

If the gNB-DU does not agree with all the recommendation information given by the gNB-CU, the method proceeds to step 503a. In step 503a, the gNB-DU replies to the gNB connection mobility adjustment failure Message (gNB connection mobility adjustment failure Message).

For each cell for which the suggested information is not feasible, the adjustment failure message may contain one or more of the following information:

-identification of non-feasible cells

-advice information on infeasible cells

■ If the proposed information for the cell in step 502 is a reference value for parameter adjustment, the message may contain a range of parameter adjustment reference values proposed for the cell.

■ If the proposed information for the cell in step 502 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for parameter adjustment proposed for the cell may be included in the message.

The uplink channel measurement information of the cell served by the gNB-DU and appearing in the demand message may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ The measured signal strength of the uplink signal from the user indicated by the user ID, such as RSRP, RSSI, signal energy, may be the actual measurement result or the quantized result (e.g. 0-100, 0 means minimum signal strength, 100 means maximum signal strength)

■ The measured signal quality of the uplink signal from the user indicated by the user ID, such as RSRQ, can be the actual measurement result or the quantized result (e.g., 0-100, 0 represents the worst signal quality, 100 represents the best signal quality)

■ The measured level (e.g., intensity level or quality level) of the uplink signal from the UE indicated by the user ID, e.g., low (low), medium (medium), high (high). The above-mentioned level decision may be determined by the concrete implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the rank is low; above the fifth threshold, the level is high; between the fourth and fifth thresholds, the rank is medium.

■ The measurement result of the signal strength/signal quality of the uplink signal of all users in the cell identifier, such as the average value of the measurement results of all users, may be the actual measurement result or the quantized result (e.g. 0-100, 0 means minimum signal strength and 100 means maximum signal strength)

-reason for unsuccessful parameter adjustment.

Example 4

Fig. 6A and 6B schematically show a fourth schematic diagram of a method of performing connection mobility adjustment according to a fourth embodiment of the present disclosure. In this embodiment, the connection mobility adjustment is initiated by the gNB-DU. Fig. 6A illustrates a situation where the adjustment request is accepted or at least partially accepted. Fig. 6B shows a case where the adjustment request fails.

As shown in fig. 6A, the method begins at step 601.

In step 601, the gNB-DU sends a gNB connection mobility adjustment request Message (gNB connection mobility adjustment request Message) to the gNB-CU, which may contain one or a combination of the following information

-cell identity information

■ The identity information may be an identity of a cell, which may belong to the gNB-DU that sent the message, or may belong to other gNB-DUs.

■ The identity information may also include identity information of two or more cells, where each cell may belong to the same gNB-DU, may belong to different gNB-DUs under the same gNB-CU, or may belong to different gnbs.

-the gNB-DU gives a recommendation for adjusting mobility parameters for the cell to which each cell identity information corresponds, which may be one of the following three recommendation information:

■ Information of cell selection/reselection/handover suggested by the gNB-DU. It may be for example an indication message that the handover is delayed or advanced by adjusting mobility parameters as suggested by the gNB-DU. For example, if the information is a first value (e.g., 0) indicating that the gNB-CU is recommended to delay the user handover of the cell by adjusting the mobility parameters. Otherwise, if the value is a second value (such as 1), it indicates that the gNB-CU is suggested to advance the user handover of the cell by adjusting the mobility parameter.

■ Reference value for parameter adjustment for mobility of connections proposed by gNB-DU

■ Reference value range for parameter adjustment for mobility of connection suggested by gNB-DU (which can be expressed by the maximum and minimum values of the range)

In some implementations, the adjustment recommendation information may be different for each cell. In other implementations, the adjustment recommendation information for each cell may be the same. In still other implementations, the cells to be adjusted may be divided into multiple groups. The principle of dividing groups may be, for example: the reason for adjusting the connection mobility parameters of the cells in the same group is the same; the cells in the same group will affect each other when adjusting the mobility parameters; and so on. In the implementation of cell grouping, corresponding recommendation information may be given for each cell in each group, as shown in table 2 below.

TABLE 2

-uplink channel measurement information for the cell served by the gNB-DU and appearing in the request message, which may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

The gNB-DU suggests reasons for adjusting the mobility parameters of the connection, such as load balancing, handover optimization, etc., and if the proposal of multiple cells or the proposals of multiple groups of cells is included, each cell or each group of cells may be given the corresponding reasons.

In step 602, the gNB-CU replies to the gNB-DU with a gNB connection mobility adjustment acknowledgement Message (gNB connection mobility adjustment Message). The gNB-CU replies to each cell of the gNB-DU whether it is feasible to reply with the recommendation information according to the information (e.g., uplink channel quality information, downlink channel quality information, etc.) it may include one or more of the following information:

cell identity corresponding to feasible proposal information

Optionally, if the proposed information is a reference value range for parameter adjustment, the acknowledgement message may also include a proposed reference value for the cell. In one embodiment, the reference value is within a reference value range of a proposed parameter adjustment, and in another embodiment, the reference value may not be within a reference value range of a proposed parameter adjustment.

If the proposed information for multiple cells is included in step 601 and only the proposed information for some cells is feasible, the message includes the above information for feasible cells, and includes at least one of the following messages for infeasible cells:

-cell identity corresponding to infeasible advice information

-proposed information for infeasible cells:

■ If the recommendation information for the cell in step 601 is an indication message about delayed or advanced handover, the message may contain recommendation information for the cell, such as a recommendation about delayed handover or advanced handover or no change of handover parameters, a recommendation about a reference value range for parameter adjustment, or a recommendation about a reference value for parameter adjustment

■ If the proposed information for the cell in step 601 is a reference value for parameter adjustment, the message may include a range of parameter adjustment reference values proposed for the cell

■ If the proposed information for the cell in step 601 is a reference value range for parameter adjustment, the message may contain an identification for the cell and a new reference value range or a proposed reference value for the proposed parameter adjustment

-suggesting reasons for not being accepted.

Then, in step 603, the gNB-CU performs connection mobility parameter adjustment.

It should be understood that the execution order of step 603 and step 602 may be arbitrary and is not limited to that shown in fig. 6A. Step 603 may be performed before or after step 602, or may be performed in parallel.

Furthermore, step 602 is optional. In some implementations, step 602 may be omitted.

Fig. 6B shows a case where the adjustment fails. Step 601 in fig. 6B is the same as in fig. 6A.

In step 601, the gNB-DU transmits a gNB connection mobility adjustment request Message (gNB connection mobility adjustment request Message) to the gNB-CU.

If the gNB-CU does not agree with all the proposed information given by the gNB-DU, the method proceeds to step 602a.

In step 602a, the gNB-CU may reply to a gNB connection mobility adjustment failure Message (gNB connection mobility adjustment failure Message).

In other embodiments, the gNB connection mobility adjustment failure message may indicate more information. The adjustment failure message may include, for each cell, at least one of the following information:

-cell identity corresponding to infeasible advice information

-proposed information for infeasible cells:

■ If the proposed information for the cell in step 601 is an indication message about delayed or advanced handover, the proposed information for the cell may be included in the message, such as a proposal about delayed handover or advanced handover or unchanged handover parameters, a proposal about a reference value range for parameter adjustment, or a proposal about a reference value for parameter adjustment

■ If the proposed information for the cell in step 601 is a reference value range for parameter adjustment, the identity for the cell and a new reference value range or a proposed reference value for the proposed parameter adjustment may be included in the message

-reason for unsuccessful parameter adjustment.

Example 5

Fig. 7A and 7B schematically illustrate a fifth method of performing connection mobility adjustment according to a fifth embodiment of the present disclosure. The method of embodiment 5 is similar to the method of embodiment 4, except that the connectivity mobility adjustment is initiated by the gNB-CU, the gNB-CU first sends the gNB connectivity mobility adjustment requirement to the gNB-DU, and then the operation is similar to the method of embodiment 4.

Fig. 7A shows a situation where the adjustment is successful or at least partly successful. Fig. 7B shows a case where the adjustment fails.

As shown in fig. 7A, the method begins at step 701.

In step 701, the gNB-CU sends a gNB connection mobility adjustment requirement Message (gNB connection mobility adjustment request Message) to the gNB-DU, which may include one or more of the following information in combination

■ The identification information may be an identification of one cell, an identification of two cells, or an identification of more than two cells

Reasons for adjusting connection mobility parameters, such as load balancing, handover optimization, etc. The reason information may be given separately for each cell. Alternatively, if the cells are grouped, the cause information may be given separately for each cell group.

In step 702, the gNB-DU transmits a gNB connection mobility adjustment Message (gNB connectivity mobility adjustment Message) to the gNB-CU. The gNB connection mobility adjustment Message (gNB connection mobility adjustment Message) may be regarded as a specific type of the gNB connection mobility adjustment request Message in embodiment 4. For each cell represented by the cell identity contained in step 701, the message may contain one or more of the following information:

-cell identity information

Specifically, the cell identification information herein may include a part or all of the cell identification information of the cell for which the connection mobility parameter needs to be adjusted, which is included in the demand message of step 701.

The proposed information for mobility parameter adjustment given by the gNB-DU may be one of the following information:

■ The indication message proposed by the gNB-DU to delay handover or advance handover by adjusting mobility parameters or not change handover parameters, e.g., if the message is 0, it indicates that the gNB-DU proposes to delay user handover of the cell indicated by the cell identification information by adjusting mobility parameters, if 1, user handover of the cell is advanced, and if 2, parameters for not changing cell handover.

■ Reference range for parameter adjustment for mobility of connections proposed by gNB-DU

Similar to embodiment 4, in some implementations, the adjustment recommendation information may be different for each cell. In other implementations, the adjustment recommendation information for each cell may be the same. In still other implementations, the cells to be adjusted may be divided into multiple groups. In the implementation of cell grouping, corresponding recommendation information may be given for each cell in each group.

In addition, for the cell that does not change the connection mobility parameter, the method may be implemented by only including the cell identifier without the adjustment suggestion information in step 702, or may be implemented by not including the corresponding cell identifier.

The uplink channel measurement information of the cell served by the gNB-DU and appearing in the demand message in step 701 may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

In step 703, the gNB-CU sends a gNB connection mobility adjustment acknowledgement Message (gNB connection mobility adjustment Message) to the gNB-DU. The confirmation message may contain one or more of the following information:

cell identity corresponding to the proposed information available in step 702

If the recommendation information of only part of cells is feasible, aiming at the cells with feasible recommendation information, the information is also contained in the message according to the mode; for the infeasible cell, the message further includes at least one of the following messages:

-identification of non-feasible cells

-advice information on infeasible cells

■ If the proposed information for the cell in step 702 is an indication message about delayed or advanced handover, the message may contain proposed information for the cell, such as a proposal about delayed or advanced handover or no change in handover parameters, or a proposal about a reference value range for parameter adjustment, or a proposal about a reference value for parameter adjustment

■ If the proposed information for the cell in step 702 is a reference value for parameter adjustment, the message may contain a range of parameter adjustment reference values proposed for the cell

■ If the proposed information for the cell in step 702 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for parameter adjustment proposed for the cell may be included in the message

-suggesting reasons for not being accepted.

Then, in step 704, the gNB-CU makes connection mobility parameter adjustments. This step may be performed by a processing module.

It should be understood that the execution order of step 704 and step 703 may be arbitrary and is not limited to that shown in fig. 7A. Step 704 may be performed before or after step 703, or may be performed in parallel.

Furthermore, step 703 is optional. In some implementations, step 703 may be omitted.

Fig. 7B shows a case where the adjustment fails. Steps 701 and 702 in fig. 7B are the same as in fig. 7A.

In step 701, the gNB-CU sends a gNB connection mobility adjustment requirement Message (gNB connection mobility adjustment request Message) to the gNB-DU.

In step 702, the gNB-DU transmits a gNB connection mobility adjustment Message (gNB connectivity mobility adjustment Message) to the gNB-CU.

If the gNB-CU does not agree with the proposed information for all cells given by the gNB-DU, the method proceeds to step 703a. In step 703a, the gNB-CU may reply to a gNB connection mobility adjustment failure Message (gNB connection mobility adjustment failure Message). For each cell, the adjustment failure message may include one or more of the following information:

-identification of non-feasible cells

-advice information on infeasible cells

■ If the proposed information for the cell in step 702 is a reference value for parameter adjustment, the proposed information for the cell may include a range of reference values for parameter adjustment proposed for the cell

-reason for unsuccessful parameter adjustment.

Example 6

Fig. 8 schematically shows a sixth schematic diagram of a method for performing connection mobility adjustment according to a sixth embodiment of the present disclosure. In this embodiment, the connection mobility adjustment is initiated by the gNB-CU.

As shown in fig. 8, the method begins at step 801.

In step 801, the gNB-CU sends a gNB connection mobility adjustment request Message (gNB connection mobility adjustment request Message) to the gNB-DU. The message may contain one or a combination of the following information:

-cell identity of the offered proposal

The cell represented by the proposed cell identity will have associated proposed information

■ The identification information may be an identification of a cell. The cell may belong to the gNB-DU which receives the message, or may belong to other gNB-DUs.

■ The identification information may also include identification information of two or more cells. The two or more cells may belong to the same gNB-DU, may belong to different gNB-DUs under the same gNB-CU, and may belong to different gNBs.

-the gNB-CU gives a recommendation to adjust the connection mobility parameters for each of the above proposed cells, which may be one of the following three recommendation information:

■ Information of delayed or advanced cell selection/reselection/handover suggested by the gNB-CU. It may be an indication message, e.g. suggested by the gNB-CU to delay or advance the handover by adjusting mobility parameters. For example, if the information is a first value (e.g., 0) indicates that the gNB-CU may delay the user handover of the cell by adjusting the mobility parameter. Otherwise, if the value is a second value (e.g. 1), it indicates that the gNB-CU will advance the user handover of the cell by adjusting the mobility parameter.

In some implementations, the adjustment recommendation information may be different for each cell. In other implementations, the adjustment recommendation information for each cell may be the same. In still other implementations, the cells to be adjusted may be divided into multiple groups. The principle of dividing groups may be, for example: the reason for adjusting the connection mobility parameters of the cells in the same group is the same; the cells in the same group will affect each other when adjusting mobility parameters; and so on. In the implementation of cell grouping, corresponding recommendation information may be given for each cell in each group, as shown in table 3 below.

TABLE 3

-it is desired to obtain a suggested cell identity:

for the cell represented by the above-mentioned cell identity for which a recommendation is desired, the gNB-CU expects the gNB-DU to provide a recommendation regarding the adjustment of the mobility parameters of the connection.

For each cell mentioned above, the gNB-CU recommends the reasons for connection mobility parameter adjustment, such as load balancing, handover optimization, etc. If multiple cells or groups of cells are involved, each cell or group of cells may be given a corresponding cause.

In step 802, the gNB-DU replies a gNB connection mobility adjustment response Message (gNB connection mobility adjustment Message) to the gNB-CU. The gNB-DU replies to the gNB-CU whether the proposed information provided in step 801 is available, based on the information it obtained (e.g., uplink channel quality information, downlink channel quality information, etc.), which includes one or more of:

cell identity corresponding to feasible proposal information

Optionally, if the recommendation information given for the cell in step 801 is a reference value range for parameter adjustment, the confirmation message may further include a recommended reference value corresponding to the cell. In one embodiment, the reference value is within a reference value range of a proposed parameter adjustment, and in another embodiment, the reference value may not be within a reference value range of a proposed parameter adjustment.

If step 801 includes the proposed information for multiple cells and only some of the proposed information for cells is available, the message may include the above information for the available cells and one or more of the following information for the unavailable cells:

-cell identity corresponding to infeasible advice information

-optionally, recommendation information for infeasible cells:

■ If the recommendation information for the cell in step 801 is an indication message about delayed or advanced handover, the message may contain recommendation information for the cell, such as a recommendation about delayed handover or advanced handover or no change in handover parameters, a recommendation about a reference value range for parameter adjustment, or a recommendation about a reference value for parameter adjustment

■ If the proposed information for the cell in step 801 is a reference value for parameter adjustment, the range of the parameter adjustment reference value proposed for the cell may be included in the message

■ If the proposed information for the cell in step 801 is a reference value range for parameter adjustment, the message may contain an identification for the cell and a new reference value range or a proposed reference value for the proposed parameter adjustment

Optionally, uplink channel measurement information of the cell served by the gNB-DU and appearing in the request message in step 801, which may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

■ The measured level (e.g., intensity level or quality level) of the uplink signal from the UE indicated by the user ID, e.g., low (low), medium (medium), high (high). The above-mentioned level decision may be determined by the concrete implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the level is low; if the grade is higher than the fifth threshold, the grade is high; between the fourth and fifth thresholds, the rank is medium.

-suggesting reasons for not being accepted.

If the gNB-DU does not agree with all the proposed information given by the gNB-CU, the message may contain one or more of the following information for each cell for which a proposal has been given in step 801:

-cell identity corresponding to infeasible advice information

-optionally, recommendation information for infeasible cells:

■ If the proposed information for the cell in step 801 is a reference value for parameter adjustment, the message may contain a range of proposed parameter adjustment reference values

■ If the proposed information for the cell in step 801 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for the proposed parameter adjustment may be included in the message

The uplink channel measurement information of the cell served by the gNB-DU and appearing in the request message in step 801 may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

-reason for unsuccessful parameter adjustment.

If in step 801 the cell identity for which a recommendation is desired is included, the gNB-DU may give a recommendation to adjust the connection mobility parameters for each such cell and/or may report uplink channel measurement information. The message may then contain, for each cell for which a recommendation is desired, one or more of the following:

-recommendation information to adjust connection mobility parameters, which may include one or more of the following information:

■ Cell identification information

■ One of the following three suggested information:

gNB-DU-proposed indication message to delay or advance handover by adjusting mobility parameters, e.g. if the message is 0, it indicates that gNB-DU may delay user handover of cell by adjusting mobility parameters, whereas if 1, it advances user handover of cell

Reference values for parameter adjustment of mobility of connections proposed by gNB-DU

gNB-DU-proposed reference value range for parameter adjustment of connection mobility (which can be represented by the maximum minimum of the range)

-uplink channel measurement information, which may comprise one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

■ The measured signal strength of the uplink signal from the UE indicated by the user ID, such as RSRP, RSSI, signal energy. The intensity information may be the actual measurement result or the quantized result (e.g., 0 to 100, where 0 indicates the minimum signal intensity and 100 indicates the maximum signal intensity).

In optional step 803, if the recommendation information about the cell for which recommendation is desired in step 801 is given in step 802, the gNB-CU replies a gNB connection mobility adjustment acknowledgement Message (gNB connection mobility adjustment Message) to the gNB-DU. For each cell provided in step 801 for which a recommendation is desired to be obtained and the corresponding recommendation information provided in step 802, the following information may be included:

cell identification where the proposed information provided in step 802 is feasible in the cell where the proposal is desired to be obtained

If the proposed information of only some cells is feasible, the adjustment confirmation message will also include the above information for the cells where the proposed information is feasible, and for the cells where the proposed information is not feasible, the adjustment confirmation message will also include at least one of the following messages

-identification of non-feasible cells

-advice information on infeasible cells

■ If the proposed information for the cell in step 802 is an indication message about delayed or advanced handover, the message may contain proposed information for the cell, such as a proposal about delayed or advanced handover or no change in handover parameters, or a proposal about a reference value range for parameter adjustment, or a proposal about a reference value for parameter adjustment

■ If the proposed information for the cell in step 802 is a reference value for parameter adjustment, the message may contain a range of parameter adjustment reference values proposed for the cell

■ If the proposed information for the cell in step 802 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for parameter adjustment proposed for the cell may be included in the message

-suggesting reasons for not being accepted.

Furthermore, if the gbb-CU does not agree with the recommendation information of all cells given by the gbb-DU, the adjustment confirmation message may contain one or more of the following information for each cell:

-identification of non-feasible cells

-advice information on infeasible cells

■ If the proposed information for the cell in step 802 is a reference value for parameter adjustment, the proposed information for the cell may include a range of reference values for parameter adjustment proposed for the cell

-reason for unsuccessful parameter adjustment.

Then, in step 804, the gNB-CU makes connection mobility parameter adjustments. This step may be performed by a processing module.

It should be understood that the execution order of steps 804 and 803 may be arbitrary and is not limited to that shown in fig. 8. Step 804 may be performed before or after step 803, or may be performed in parallel.

Further, step 803 is optional. In some implementations, step 803 may be omitted.

Example 7

Fig. 9 schematically shows a seventh schematic diagram of a method for performing connection mobility adjustment according to a seventh embodiment of the present disclosure. In this embodiment, the connection mobility adjustment is initiated by the gNB-DU.

As shown in fig. 9, the method begins at step 901.

In step 901, the gNB-DU sends a gNB connection mobility adjustment request Message (gNB connection mobility adjustment request Message) to the gNB-CU. The adjustment request message may contain one or a combination of the following information:

-proposed cell identity

■ The identity information may be an identity of a cell that may belong to the gNB-DU that received the message, or may belong to other gNB-DUs

■ The identification information may also include identification information of two or more cells, and the two or more cells may belong to the same gNB-DU, may belong to different gNB-DUs under the same gNB-CU, or belong to different gnbs

-the gNB-DU gives a proposal for adjusting the mobility parameters of the connection for each proposed cell, which may be one of the following three types of proposal information:

■ The indication message proposed by the gNB-DU to delay or advance the handover by adjusting the mobility parameters, e.g. if the message is 0, it indicates that the gNB-CU will delay the handover of the cell by adjusting the mobility parameters, otherwise if 1, it advances the handover of the cell

In some implementations, the adjustment recommendation information may be different for each cell. In other implementations, the adjustment recommendation information for each cell may be the same. In still other implementations, the cells to be adjusted may be divided into multiple groups. The principle of dividing groups may be, for example: the reason for adjusting the connection mobility parameters of the cells in the same group is the same; the cells in the same group will affect each other when adjusting mobility parameters; and so on. In the implementation of cell grouping, corresponding recommendation information may be given for each cell in each group, as shown in table 4 below.

TABLE 4

-cell identity desired to obtain a recommendation

For the cell represented by the above-mentioned cell identity for which a recommendation is desired to be obtained, the gNB-DU expects the gNB-CU to provide a recommendation on the adjustment of the mobility parameters of the connection.

Optionally, the uplink channel measurement information of the cell served by the gNB-DU and appearing in the request message in step 901, which may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

■ The measured level (e.g., strength level or quality level) of the uplink signal from the UE indicated by the user ID is low (low), medium (medium), and high (high). The above-mentioned level decision can be determined by the particular implementation of the gNB-DU. If the signal strength or quality of the uplink signal is below a fourth threshold, the level is low; above the fifth threshold, the level is high; between the fourth and fifth thresholds, the rank is medium.

For each cell, the gNB-DU suggests reasons for adjusting the mobility parameters of the connection, such as load balancing, handover optimization, etc., and if multiple cells or groups of cells are involved, each cell or group of cells may give the corresponding reasons.

In step 902, the gNB-CU replies to the gNB-DU with a gNB connection mobility adjustment response Message (gNB connection mobility adjustment Message). The gNB-CU replies to the gNB-DU about whether the proposed information provided in step 901 is available, based on the information it obtained (e.g., uplink channel quality information, downlink channel quality information, etc.), which includes one or more of:

cell identity corresponding to feasible proposal information

Optionally, if the proposed information given for the cell in step 901 is a reference value range for parameter adjustment, the confirmation message may further include a proposed reference value corresponding to the cell, and in one embodiment, the reference value is within the reference value range for proposed parameter adjustment, and in another embodiment, the reference value may not be within the reference value range for proposed parameter adjustment.

If the proposed information for multiple cells is included in step 901 and the proposed information for only some cells is feasible, the message may include the above information for feasible cells, and one or more information for infeasible cells:

-cell identity corresponding to infeasible advice information

-optionally, recommendation information for infeasible cells:

■ If the recommendation information for the cell in step 901 is an indication message about delayed or advanced handover, the message may contain recommendation information for the cell, such as a recommendation about delayed handover or advanced handover or no change of handover parameters, a recommendation about a reference value range for parameter adjustment, or a recommendation about a reference value for parameter adjustment

■ If the suggested information for the cell in step 901 is a reference value for parameter adjustment, the message may contain a range of parameter adjustment reference values suggested for the cell

■ If the proposed information for the cell in step 901 is a reference value range for parameter adjustment, the message may contain an identification for the cell and a new reference value range or a proposed reference value for the proposed parameter adjustment

-suggesting reasons for not being accepted.

If the gNB-CU does not agree with all the proposed information given by the gNB-DU, this message may contain one or more of the following information for each cell for which a proposal has been given in step 901:

-cell identity corresponding to infeasible advice information

-optionally, recommendation information for infeasible cells:

■ If the proposed information for the cell in step 901 is an indication message about delayed handover or advanced handover, the proposed information for the cell may be included in the message, such as a proposal about delayed handover or advanced handover or unchanged handover parameter, a proposal about a reference value range for parameter adjustment, or a proposal about a reference value for parameter adjustment

■ If the proposed information for the cell in step 901 is a reference value for parameter adjustment, the message may contain a range of the proposed reference value for parameter adjustment

■ If the proposed information for the cell in step 901 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for proposed parameter adjustment may be included in the message

-reason for unsuccessful parameter adjustment.

If in step 901 a cell identity is included for which a recommendation is desired, for each such cell the gNB-CU may give a recommendation to adjust the connection mobility parameters, which may contain the following information:

■ Cell identification information

■ One of the following three suggested information:

gNB-CU proposed indication message to delay or advance handover by adjusting mobility parameters, e.g. if the message is 0, it indicates that gNB-CU will delay user handover of cell by adjusting mobility parameters, whereas if 1, it advances user handover of cell

Reference values for parameter adjustment of connection mobility suggested by gNB-CU

The range of reference values for parameter adjustment of the mobility of the connection suggested by the gNB-CU (which can be represented by the maximum minimum of this range).

In an optional step 903, if the recommendation information gNB-DU about the cell for which the recommendation is desired to be obtained in step 901 is given in step 902, a gNB connection mobility adaptation confirmation Message (gNB connection mobility adaptation Message) is replied to the gNB-CU. For each cell provided in step 901 for which a recommendation is desired to be obtained and the corresponding recommendation information provided in step 902, the following information is included:

cell identification where the proposed information provided in step 902 is feasible in the cell where the proposal is desired to be obtained

Optionally, if the recommendation information is a reference range for parameter adjustment of connection mobility, it may further contain a recommended reference value, which in one embodiment is within the reference range for parameter adjustment of recommendation, and in another embodiment may not be within the reference range for parameter adjustment of recommendation.

If the proposed information of only some cells is feasible, the message also contains the information in the manner described above for the cells where the proposed information is feasible, and for the cells where the proposed information is not feasible, the message also contains at least one of the following messages:

-identification of non-feasible cells

-advice information on infeasible cells

■ If the proposed information for the cell in step 902 is an indication message about delayed or advanced handover, the message may contain proposed information for the cell, such as a proposal about delayed or advanced handover or no change in handover parameters, or a proposal about a reference value range for parameter adjustment, or a proposal about a reference value for parameter adjustment

■ If the proposed information for the cell in step 902 is a reference value for parameter adjustment, the message may contain a range of parameter adjustment reference values proposed for the cell

■ If the proposed information for the cell in step 902 is a reference value range for parameter adjustment, a new reference value range or a proposed reference value for parameter adjustment proposed for the cell may be included in the message

Optionally, the uplink channel measurement information of the cell served by the gNB-DU and desired to be proposed in step 901 may include one or more of the following information:

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

-suggesting reasons for not being accepted.

Furthermore, if the gbb-DU does not agree with the proposed information of all cells given by the gbb-CU, the message may contain one or more of the following information for each cell:

-identification of non-feasible cells

-advice information on infeasible cells

■ Cell ID, identification of Cell to which measured uplink signal belongs

■ User ID, identity of UE to which measured uplink signal belongs

-reason for unsuccessful parameter adjustment.

Then, in step 904, the gNB-CU performs connection mobility parameter adjustment according to the received gNB connection mobility adjustment acknowledgement. This step may be performed by a processing module.

Examples of reference to the exemplary embodiments will be described below as supplementary notes. The above-described exemplary embodiments and modifications made thereto may also be described in whole or in part as the following supplementary notes. However, the invention and modifications made thereto illustrated in the foregoing exemplary embodiments are not limited to the following.

(supplementary notes 1)

A method performed in a centralized unit of a base station, comprising:

sending a resource state request message to a distribution unit of a base station;

receiving a resource state response message and a resource state updating message from a base station; and

and performing connection mobility adjustment according to the received resource state response message and the resource state updating message.

(supplementary notes 2)

A concentration unit for a base station, comprising:

a transmission module configured to transmit a resource status request message to a distribution unit of a base station;

a receiving module configured to receive a resource status response message and a resource status update message from a distribution unit of a base station; and

a processing module configured to perform connection mobility adjustment according to the received resource status update message and the resource status update message.

(supplementary notes 3)

A method performed in a distribution unit of a base station, comprising:

receiving a resource status request message from a central unit of a base station;

and sending the resource state response message and the resource state updating message to the centralized unit of the base station.

(supplementary notes 4)

A distribution unit of a base station, comprising:

a receiving module configured to: receiving a resource status request message from a central unit of a base station; and

a sending module configured to: and sending the resource state response message and the resource state updating message to the centralized unit of the base station.

(supplementary notes 5)

The method or unit of any of supplementary notes 1 to 4, wherein the resource status request message comprises at least one of the following information:

identification information of the distribution unit;

indication information of uplink channel measurement information needs to be reported;

a list of cells to which uplink channel measurement information to be reported belongs;

periodic information or trigger information of the report;

the centralized unit distributes measurement identification information related to the uplink channel measurement; and

indication information related to controlling reporting of the uplink channel measurement information.

(supplementary notes 6)

The method or unit of any of supplementary notes 1 to 4, wherein the resource status response message includes at least one of the following information:

measurement identification information distributed by the centralized unit;

measurement identification information distributed by the distribution unit;

a list of cells for which measurements and reports can be made;

a list of cells that cannot be measured and reported;

the reason why it cannot be done.

(supplementary notes 7)

The method or unit of any of supplementary notes 1 to 4, wherein the resource status update message includes at least one of the following information:

an identity of a cell to which the reported measurement corresponds;

a user identity corresponding to the reported measurement;

measured signal strength;

a measured signal quality;

the measured signal level; and

the overall signal strength/signal quality of the cell.

(supplementary notes 8)

A method performed in a central unit of a base station, comprising:

sending a connection mobility adjustment request message to a distribution unit of a base station;

receiving a connection mobility adjustment acknowledgement message from a distribution unit of a base station; and

performing connection mobility adjustment according to the received connection mobility adjustment confirm message.

(supplementary note 9)

The method according to supplementary note 8, further comprising:

receiving a connection mobility adjustment required message from a distribution unit of a base station,

wherein the transmission of the connection mobility adjustment request message to the distribution unit of the base station is made in response to the received connection mobility adjustment required message.

(supplementary notes 10)

The method according to supplementary note 8, wherein the connection mobility adjustment request message includes at least one of the following information:

cell identification information of a cell to which a mobility parameter needs to be adjusted;

adjustment recommendation information of connection mobility parameters;

reason for the adjustment of the connection mobility parameters.

(supplementary notes 11)

The method according to supplementary note 10, wherein the adjustment recommendation information of the connection mobility parameter includes at least one of the following information:

information to delay or advance cell selection/reselection/handover;

reference values for parameter adjustments for connection mobility;

reference value range for parameter adjustment of connection mobility.

(supplementary notes 12)

The method according to supplementary note 8, wherein the connection mobility adjustment acknowledgment message includes at least one of the following information:

information of a cell corresponding to the feasible adjustment suggestion information; and/or

And the information of the cell corresponding to the impracticable adjustment suggestion information.

(supplementary notes 13)

A concentration unit for a base station, comprising:

a sending module configured to: sending a connection mobility adjustment request message to a distribution unit of a base station;

a receiving module configured to: receiving a connection mobility adjustment acknowledgement message from a distribution unit of a base station; and

a processing module configured to: and executing connection mobility adjustment according to the connection mobility adjustment confirmation message.

(supplementary notes 14)

The concentration unit according to supplementary note 13, wherein,

the receiving module is further configured to: receiving a connection mobility adjustment requirement message from a distribution unit of the base station, and

the sending module is further configured to: transmitting the connection mobility adjustment request message to a distribution unit of a base station in response to the connection mobility adjustment demand message.

(supplementary notes 15)

The concentration unit according to supplementary note 13, wherein the connection mobility adjustment request message includes at least one of the following information:

adjustment recommendation information of connection mobility parameters;

reason for the adjustment of the connection mobility parameters.

(supplementary notes 16)

The centralized unit according to supplementary note 15, wherein the adjustment recommendation information of the connection mobility parameter includes at least one of the following information:

information to delay or advance cell selection/reselection/handover;

reference values for parameter adjustments for connection mobility; and/or

Reference value range for parameter adjustment of connection mobility.

(supplementary notes 17)

The method according to supplementary note 13, wherein the connection mobility adjustment acknowledgement message includes at least one of the following information:

information of cells corresponding to feasible adjustment suggestion information; and/or

Information of a cell to which the adjustment advice information is not feasible.

(supplementary notes 18)

A method performed in a distribution unit of a base station, comprising:

receiving a connection mobility adjustment request message from a central unit of a base station;

in response to the received connection mobility adjustment request message, a connection mobility adjustment confirm message is transmitted to the central unit of the base station.

(supplementary note 19)

The method according to supplementary note 18, further comprising:

sending a connection mobility adjustment required message to the concentration unit of the base station,

wherein the connection mobility adjustment request message is a response message to the connection mobility adjustment required message.

(supplementary notes 20)

The method according to supplementary note 18, wherein the connection mobility adjustment request message includes at least one of the following information:

adjustment recommendation information of connection mobility parameters;

reason for the adjustment of the connection mobility parameters.

(supplementary note 21)

The method according to supplementary note 20, wherein the adjustment suggestion information of the connection mobility parameter includes at least one of the following information:

information to delay or advance cell selection/reselection/handover;

reference values for parameter adjustments for connection mobility; and/or

Reference value range for parameter adjustment of connection mobility.

(supplementary note 22)

The method according to supplementary note 18, wherein the connection mobility adjustment acknowledgement message includes at least one of the following information:

(supplementary note 23)

A distribution unit of a base station, comprising:

a receiving module configured to: receiving a connection mobility adjustment request message from a central unit of a base station; and

a sending module configured to: in response to the received connection mobility adjustment request message, a connection mobility adjustment confirm message is transmitted to the central unit of the base station.

(supplementary notes 24)

The distribution unit according to supplementary note 23, wherein,

the sending module is further configured to: transmitting a connection mobility adjustment required message to the central unit of the base station,

(supplementary note 25)

The distribution unit according to supplementary note 23, wherein the connection mobility adjustment request message includes at least one of the following information:

adjustment recommendation information of connection mobility parameters;

reason for the adjustment of the connection mobility parameters.

(supplementary notes 26)

The distribution unit according to supplementary note 25, wherein the adjustment recommendation information of the connection mobility parameter includes at least one of the following information:

information to delay or advance cell selection/reselection/handover;

reference values for parameter adjustments for connection mobility; and/or

Reference value range for parameter adjustment of connection mobility.

(supplementary note 27)

The distribution unit according to supplementary note 23, wherein the connection mobility adjustment confirm message includes at least one of the following information:

(supplementary notes 28)

A method performed in a central unit of a base station, comprising:

receiving a connection mobility adjustment request message from a distribution unit of a base station; and

performing connection mobility adjustment according to the received connection mobility adjustment request message.

(supplementary note 29)

The method according to supplementary note 28, further comprising:

a connection mobility adjustment acknowledgement message is sent to a distribution unit of the base station.

(supplementary notes 30)

The method according to supplementary note 28, further comprising:

sending a connection mobility adjustment required message to a distribution unit of the base station,

wherein the connection mobility adjustment request message is a response to the connection mobility adjustment required message.

(supplementary notes 31)

A concentration unit for a base station, comprising:

a receiving module configured to: receiving a connection mobility adjustment request message from a distribution unit of a base station; and

a processing module configured to: performing connection mobility adjustment according to the received connection mobility adjustment request message.

(supplementary notes 32)

The concentration unit according to supplementary note 31, wherein,

the sending module is further configured to: sending a connection mobility adjustment acknowledgement message to a distribution unit of the base station.

(supplementary note 33)

The concentration unit according to supplementary note 31, wherein,

the sending module is further configured to send a connection mobility adjustment required message to a distribution unit of the base station,

(supplementary notes 34)

A method performed in a distribution unit of a base station, comprising:

transmitting a connection mobility adjustment request message to a central unit of a base station; and

a connection mobility adjustment acknowledgement message is received from the central unit of the base station.

(supplementary notes 35)

The method of supplementary note 34, further comprising:

receiving a connection mobility adjustment requirement message from the central unit of the base station,

wherein the transmission of the connection mobility adjustment request message to the central unit of the base station is made in response to the received connection mobility adjustment required message.

(supplementary notes 36)

A distribution unit of a base station, comprising:

a transmission module configured to transmit a connection mobility adjustment request message to a concentration unit from a base station; and

a receiving module configured to receive a connection mobility adjustment acknowledgement message from the central unit of base stations.

(supplementary note 37)

The distribution unit according to supplementary note 36, wherein:

the receiving module is further configured to: receiving a connection mobility adjustment requirement message from the central unit of the base station,

(supplementary notes 38)

A method performed in a central unit of a base station, comprising:

receiving a connection mobility adjustment response message from a distribution unit of a base station; and

performing connection mobility adjustment according to the received connection mobility adjustment response message.

(supplementary note 39)

The method according to supplementary note 38, further comprising:

sending a connection mobility adjustment acknowledgement message to a distribution unit of the base station.

(supplementary notes 40)

The method according to supplementary note 38 or 39, wherein the connection mobility adjustment request message includes at least one of the following information:

the proposed cell identification and the adjustment proposal information of the corresponding connection mobility parameter are provided;

cell identification for which it is desirable to obtain a recommendation

The reason for the adjustment.

(supplementary note 41)

The method according to supplementary note 38 or 39, wherein the connection mobility adjustment response message includes at least one of the following information:

information of a cell corresponding to the feasible advice information;

information of a cell corresponding to the infeasible advice information.

(supplementary notes 42)

A concentration unit of a base station configured to perform the method of any one of supplementary notes 38 to 41.

(supplementary notes 43)

A method performed in a distribution unit of a base station, comprising:

receiving a connection mobility adjustment request message of a central unit of a base station;

a connection mobility adjustment response message is sent to the central unit of the base station.

(supplementary note 44)

The method according to supplementary note 43, further comprising:

a connection mobility adjustment acknowledgment message is received from the central unit of base stations.

(supplementary notes 45)

The method according to supplementary note 43 or 44, wherein the connection mobility adjustment request message includes at least one of the following information:

desiring to obtain a proposed cell identity;

the reason for the adjustment.

(supplementary notes 46)

The method according to supplementary note 43 or 44, wherein the connection mobility adjustment response message includes at least one of the following information:

information of a cell corresponding to the feasible advice information;

information of a cell corresponding to the infeasible advice information.

(supplementary notes 47)

A distribution unit of a base station configured to perform the method of any of the supplementary notes 43 to 46.

(supplementary notes 48)

A method performed in a central unit of a base station, comprising:

receiving a connection mobility adjustment request message from a distribution unit of a base station;

transmitting a connection mobility adjustment response message to a centralized unit of the base station;

(supplementary note 49)

The method according to supplementary note 48, wherein the connection mobility adjustment request message includes at least one of the following information:

the proposed cell identity and its corresponding adjustment proposal information of the connection mobility parameters are provided;

desiring to obtain a proposed cell identity;

the reason for the adjustment.

(supplementary notes 50)

The method according to supplementary note 48, wherein the connection mobility adjustment response message includes at least one of the following information:

information of a cell corresponding to the feasible advice information;

information of a cell corresponding to the infeasible advice information.

(supplementary notes 51)

A concentration unit of a base station configured to perform the method of any one of supplementary notes 48 to 50.

(supplementary notes 52)

A method performed in a distribution unit of a base station, comprising:

transmitting a connection mobility adjustment request message to a central unit of a base station;

receiving a connection mobility adjustment response message from a central unit of the base station; and

a connection mobility adjustment acknowledgement message is sent to the central unit of the base station.

(supplementary note 53)

The method according to supplementary note 52, wherein the connection mobility adjustment request message includes at least one of the following information:

cell identification for which it is desirable to obtain a recommendation

The reason for the adjustment.

(supplementary notes 54)

The method according to supplementary note 52, wherein the connection mobility adjustment response message includes at least one of the following information:

information of a cell corresponding to the feasible advice information;

information of a cell corresponding to the infeasible advice information.

(supplementary notes 55)

A distribution unit of a base station configured to perform the method of any of the supplementary notes 52 to 55.

The method of the present application and the apparatus involved have been described above in connection with preferred embodiments. According to the method for controlling connection mobility performed through the F1 interface of the present disclosure, it is possible to improve the accuracy of, for example, cell selection/reselection and/or handover-related parameter settings, and reduce problems such as user handover failure, handover ping-pong, and inter-cell load imbalance caused by inappropriate settings of these parameters.

Those skilled in the art will appreciate that the methods illustrated above are exemplary only. The methods of the present application are not limited to the steps or sequences shown above. The concentration unit and the distribution unit shown above may comprise further modules, e.g. also available modules, which may be developed or developed in the future, etc. The various identifiers shown above are merely exemplary and not limiting, and the application is not limited to the specific information elements that are examples of such identifiers. Many variations and modifications may be made by those skilled in the art in light of the teachings of the illustrative embodiments.

The foregoing detailed description has set forth numerous embodiments of a method of performing mobility adjustments, a corresponding centralized unit, and a distributed unit, using schematics, flowcharts, and/or examples. Where such diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of structures, hardware, software, firmware, or virtually any combination thereof. In one embodiment, portions of the subject matter described in embodiments of the present disclosure may be implemented by Application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs), digital Signal Processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described in this disclosure are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described in this disclosure applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of signal bearing media include, but are not limited to: recordable type media such as floppy disks, hard disk drives, compact Disks (CDs), digital Versatile Disks (DVDs), digital tape, computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.)

Although the present disclosure has been shown in connection with the preferred embodiments of the present disclosure, those skilled in the art will appreciate that various modifications, substitutions and alterations can be made to the present disclosure without departing from the spirit and scope of the present disclosure. Accordingly, the present disclosure should not be limited by the above-described embodiments, but should be defined by the appended claims and their equivalents.

Claims

1. A method performed in a central unit of a base station, comprising:

sending a resource state request message to a distribution unit of a base station; and

a resource status response message is received from the distribution unit of the base station.

2. The method of claim 1, further comprising:

a resource status update message is received from a distribution unit of a base station.

3. The method of claim 1, wherein the resource status request message comprises at least one of:

the distribution unit reports the indication information of the uplink channel measurement information to the central unit;

a list of cells to which the information to be reported belongs;

reporting cycle information or trigger information of the indication information;

measurement identification information related to uplink channel measurement;

indication information related to controlling the reporting of the uplink channel measurement information.

4. The method of claim 3, wherein the reporting of the periodic information or the trigger information of the indication information comprises at least one of:

different reporting period information for different cells;

one report period information;

event information triggering the distribution unit to report;

a reporting period set for the periodically reported cells;

and triggering an event set by the cell for triggering the report of the event.

5. The method of claim 1, wherein the resource status response message comprises at least one of:

measurement identification information contained in the received resource status request message;

the distribution unit distributes measurement identification information related to the uplink channel measurement information;

a list of cells capable of requested measurements and reporting;

a list of cells that cannot make the requested measurements and reports;

the reason why it cannot be performed.

6. A concentration unit of a base station, comprising:

a transceiver;

a processor coupled with the transceiver and configured to perform the method of any of claims 1-5.

7. A method performed in a distribution unit of a base station, comprising:

receiving a resource status request message from a centralized unit of a base station;

in response to the received resource status request message, a resource status response message is sent to the centralized unit of the base station.

8. The method of claim 7, further comprising:

a resource status update message is sent to the centralized unit of the base station.

9. The method of claim 7, wherein the resource status request message comprises at least one of:

the distribution unit is required to report the indication information of the uplink channel measurement information to the central unit;

a list of cells to which the information to be reported belongs;

measurement identification information related to uplink channel measurement;

10. The method of claim 9, wherein the

The period information or the trigger information for reporting the indication information includes at least one of the following information:

different reporting period information for different cells;

one report period information;

event information triggering the distribution unit to report;

a reporting period set for the periodically reported cells;

and triggering the reported triggering event aiming at the cell triggered by the event.

11. The method of claim 7, wherein the resource status response message includes at least one of:

a list of cells capable of requested measurements and reporting;

a list of cells that cannot make the requested measurements and reports;

the reason why it cannot be done.

12. A distribution unit of a base station, comprising:

a transceiver;

a processor coupled with the transceiver and configured to perform the method of any of claims 7-11.