TECHNICAL FIELD

[001] This disclosure relates to resource status reporting.

BACKGROUND

[002] A resource status reporting procedure is used by a first network entity to request a second network entity (e.g., a neighboring network node) (a.k.a., the “reporting entity”) to report the result of one or more measurements. For example, this procedure can be used by a fist Next Generation (NG) Radio Access Network (RAN) (NG-RAN) node to request a second NG-RAN node to report load measurements (e.g., the average number of active user equipments (UEs)) within a sampling period).

[003] The first network entity can initiate the procedure by sending a resource status start message to the reporting entity requesting that the reporting entity periodically provide to the first network entity requested resource status information (i.e., one more measurement values). If, the second network entity is capable to provide the requested resource status information, the second network entity shall initiate the measurements as requested and respond with a response message. To periodically provide the requested information to the first network entity (a.k.a., the “requesting entity”), the reporting entity transmits periodically to the requesting entity a status update message comprising the requested information.

SUMMARY

[004] Certain challenges presently exist. For instance, a requesting entity may request many reporting entities to periodically provide requested information, which means that the number of status update message transmitted to the requesting entity within a given window of time may be quite large. Additionally, the measurement values included in a status update message may be of little value to the requesting entity if the measurement values have not changed significantly since the last status update message was sent.

[005] This disclosure aims at avoiding or at least mitigating the above problems. Accordingly, in one aspect there is provided a method performed by a reporting entity for reporting one or more measurement values to a requesting entity. In one embodiment the method includes obtaining a first measurement value, VI, for a first measurement object. The method also includes obtaining a second measurement value, V2, for the first measurement object. The method also includes determining that a reporting condition is satisfied. The method further includes, as a result of determining that the reporting condition is satisfied, reporting V2 to the requesting entity. The step of determining that the reporting condition is satisfied comprises comparing AV to a first reporting threshold, Tl, wherein AV is a function of a difference between V2 and VI.

[006] In another aspect there is provided a computer program comprising instructions which when executed by processing circuitry of a reporting entity causes the reporting entity to perform any of the methods disclosed herein. In one embodiment, there is provided a carrier containing the computer program wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

[007] In another aspect there is provided a reporting entity. The reporting is operative to obtain a first measurement value, VI, for a first measurement object and to obtain a second measurement value, V2, for the first measurement object. The reporting is further operative to determine whether a reporting condition is satisfied; and, as a result of determining that the reporting condition is satisfied, report V2 to the requesting entity. The reporting entity is operative to determine whether the reporting condition is satisfied by performing a process that comprises comparing AV to a first reporting threshold, Tl, wherein AV is a function of a difference between V2 and VI.

[008] In yet another aspect there is provided a reporting entity. The reporting entity comprises processing circuitry and a memory (642). The memory contains instructions executable by the processing circuitry, wherein the reporting entity is operative to obtain a first measurement value, VI, for a first measurement object and to obtain a second measurement value, V2, for the first measurement object. The reporting entity is further operative to determine whether a reporting condition is satisfied and, as a result of determining that the reporting condition is satisfied, report V2 to the requesting entity. The reporting entity is operative to determine whether the reporting condition is satisfied by performing a process that comprises comparing AV to a first reporting threshold, Tl, wherein AV is a function of a difference between V2 and VI.

[009] An advantage of the embodiments disclosed herein is that they provide a mechanism that gives needed precision and frequency of updates while using less resources to do so. It is adaptive and configurable to the specific need of precision for the user. This means that without sacrificing the precision or quality of measurements, updates can be sent less frequently when the measurement has not changed enough. This gives lower the network utilization for distributing resource utilization information between the nodes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0011] FIG. 1 illustrates a requesting entity communicating with a reporting entity.

[0012] FIG. 2 illustrates a system comprising a plurality of nodes where each node can be a reporting entity and/or a requesting entity.

[0013] FIG. 3 illustrates a system comprising a central unit communicating with a number of distributed units.

[0014] FIG. 4 is a flowchart illustrating a process according to some embodiments.

[0015] FIG. 5 is a flowchart illustrating a process according to some embodiments.

[0016] FIG. 6 is a block diagram of a reporting entity according to some embodiments.

DETAILED DESCRIPTION

[0017] FIG. 1 illustrates a requesting entity 102 communicating with a reporting entity 104. Both the requesting entity and the reporting entity may be a network node of an access network (e.g., a radio access network (RAN), such as a Next Generation (NG) RAN specified by the Third Generation Partnership Project (3GPP)). For instance, in some embodiments, the requesting entity is a first base station and the reporting entity is a second base station. FIG. 2 illustrates a system 200 comprising a plurality of nodes (e.g., RAN nodes), where each node can be a reporting entity and/or a requesting entity. Accordingly, if each node is a reporting entity, it is possible that a large number of status update messages are transmitted within a certain window of time, which could overload or create congestion in the network 202 connecting the nodes together. As another example, in some embodiments, the requesting entity is a central unit (CU) of a base station and the reporting entity is distributed unit (DU) of the base station. This example is illustrated in FIG. 3, which shows a CU 302 communicating with many DUs. If each DU is a reporting entity, it is possible that a large number of status update messages are transmitted to CU 302 within a certain window of time, which could overload the network 302 connecting the DUs to CU 302.

[0018] Referring back to FIG. 1, FIG. 1 shows requesting entity 102 transmitting to reporting entity 104 a resource status request message 191 (or simply message 191 for short). For example, requesting entity 102 may transmit message 191 directly to reporting entity 104 (e.g., the entities may be connected to the same Local Area Network (LAN) segment) or requesting entity 102 may transmit message 191 indirectly to reporting entity 104 (i.e., one or more relay nodes may by employed to relay the message from requesting entity 102 to reporting entity 104). In response to message 191, reporting entity 104 transmits to requesting entity 102 a response message 192. Assuming that reporting entity 104 is capable of providing the requested information to requesting entity 102, then, at some point after receiving request message 191, reporting entity 104 obtains the requested measurement value(s) (step si 99) and then transmits to requesting entity 102 a status update message 193 containing the obtained measurement value(s). These last two steps may be repeated on a periodic basis (e.g., between 500 milliseconds (ms) and 10 seconds (s)).

[0019] A problem with having the reporting entity perform the obtaining step and the status update message transmitting step on a periodic basis is that the resulting status update message may be of marginal value to the requesting entity.

[0020] For example, if measurement value included in the status update message is a value specifying the current total number of users of a resource, the available resources (AR) for an additional user of the same resource, assuming fair allocation would be: AR = (1/(1 + N)), where N is the current total number of users of the resource. The total resources are known, so multiplying that by AR (i.e., the available resource for the another user) gives an estimated number for the resources available for a new user. [0021] Because the resource utilization is used in this way, an absolute change in the current total number of users will have a different impact depending on the size of the current number of users before the change. As an example, if the current total number of users = 50 and one user is added, then the new current total number of users = 51. Assuming a total capacity of 1000, then AR will change from 19.6 (Current number of users = 50) to 19.23 (Current number of users = 51). When the absolute numbers are lower, but the absolute change is the same, for example when going from 333 (Current number of users = 2) to 250 (Current number of users = 3). In the first case, it is not necessary to distribute an updated value very frequently, since the impact for a decision will be very small. In the second case, a change is more important to distribute, because it will more like have an impact on a decision to which resource to use.

[0022] Advantageously, to reduce the number of status update messages that may be of marginal value to requesting entity 102, requesting entity 102 may include in the resource status request message 191 first threshold information that specifies a first reporting threshold (Tl) or enables reporting entity 104 to calculate Tl, wherein reporting entity 104 should use Tl, the previously reported measurement value (denoted VI), and the newly obtained measurement value (V2) to determine whether or not the newly obtained measurement value (V2) should be reported to requesting entity 102.

[0023] For instance, if abs(V2-Vl) is less than Tl (or (abs(V2-Vl)/Vl) < Tl), then reporting entity 104 refrains from sending a status update message that includes V2, where abs(N) is a function that returns the absolute value of N. On the other hand, if (abs(V2-Vl)) is greater than Tl (or (abs(V2-Vl)/Vl)) > Tl) and zero or more other conditions are satisfied (e.g., the amount of time that has elapsed since reporting entity 104 transmitted the status update message containing VI is greater than a second reporting threshold (T2), which may be indicated in the request message 191), then reporting entity 104 will send to requesting entity 102 a status update message that includes V2. In some embodiments, if abs(V2-Vl) is equal to Tl (or (abs(V2-Vl)/Vl) = Tl), then reporting entity 104 refrains from sending a status update message that includes V2. In this manner, by introducing such a reporting threshold, reporting entity 104 will refrain some sending to requesting entity 102 a status update message that has little or no value to requesting entity 102.

[0024] FIG. 4 is a flowchart illustrating a process 400 according to some embodiments. Process 400 is performed by reporting entity 104 and may begin with step [0025] Step s402 comprises the reporting entity obtaining a measurement value, for a first measurement object. Step s404 (optional) comprises the reporting entity reporting the obtained measurement value to requesting entity 102 (this reported measurement value is named VI). Step s406 comprises the reporting entity obtaining a new measurement value (named V2) for the first measurement object. Step s408 comprises the reporting entity determining whether a reporting condition is satisfied. If the reporting condition is not satisfied, then process 400 may return to step s406 where a new measurement value is obtained, otherwise process 400 proceeds to step s410. Step s410 comprises the reporting entity, as a result of determining that the reporting condition is satisfied, reporting the new measurement value (i.e., the most recently obtained measurement value, which we denote asV2) to the requesting entity. The step of determining that the reporting condition is satisfied comprises comparing AV to a first reporting threshold (Tl), wherein AV is a function of a difference between the most recently obtained measurement value (i.e., V2) and the most recently reported measurement value (i.e., VI). After step s410, process 400 may go back to step 406, where a new measurement value is obtained.

[0026] In some embodiments, the process further includes the reporting entity reporting VI to the requesting entity, wherein VI is reported to the requesting entity at a first point in time, tl, and determining that the reporting condition is satisfied further comprises comparing At to a second reporting threshold (T2), wherein At represents the amount of time between tl and t2, wherein t2 is the time at which V2 was obtained or a time after the time at which V2 was obtained, and the reporting condition is satisfied if At is greater than T2 and AV is greater than Tl .

[0027] In some embodiments, the process further includes receiving a status request or update message transmitted by the requesting entity, wherein the status request or update message indicates the first reporting threshold (Tl). In some embodiments, the status request or update message further indicates the second reporting threshold (T2). In some embodiments, the status request or update message further indicates the measurement object.

[0028] In some embodiments, obtaining the new measurement value comprises obtaining a plurality of measurement values and averaging the plurality of measurement values to produce an average measurement value (Av), wherein the new measurement value (i.e., V2) is the average measurement value (V2 = Av) or a function of the average measurement value (e.g., V2 = floor(Av x 10)/l 0). [0029] In some embodiments, the requesting entity is a first radio access network, RAN, node; and the reporting entity is a second RAN node.

[0030] In some embodiments, the requesting entity is a Central Unit, CU, of a radio access network, RAN, node; and the reporting entity is a Distributed Unit, DU, of the RAN node.

[0031] In some embodiments, the reporting condition is satisfied if AV is greater than Tl.

[0032] In some embodiments, AV is equal to one of: (V2 - VI), (V1-V2), abs(V2- VI), or abs(V2-Vl)/Vl.

[0033] FIG. 5 is a flowchart illustrating a process 500 according to some embodiments. Process 500 is performed by reporting entity 104 and may begin with step s502.

[0034] Step s502 comprises reporting entity 104 receiving resource status request message 191 transmitted by requesting entity 102. In this example, message 191 includes at least Tl and may also include T2 (or it may include information enabling reporting entity 104 to determine Tl and T2) and it includes information identifying a measurement object.

[0035] Step s504 comprises reporting entity 104 initializing a first variable (i.e. , R = 0).

[0036] Step s506 comprises reporting entity 104 obtaining N measurement values (nl, n2, ..., nN) (e.g., N=5) within a certain window of time (e.g., a 500 ms window) for the identified measurement object. In one embodiment, each measurement value is the number of UEs for a certain data radio bearer (DRB) and a certain cell for which there is downlink (DL) data available for transmission. In another embodiment, each measurement value is the number of UEs for the DRB and the cell for which there is uplink (UL) data available for transmission.

[0037] Step s508 comprises reporting entity 104 obtaining an average measurement value (Av). In one embodiment obtaining Av comprises calculating: Av = (nl + n2 + ... + nN)/N. In another embodiment obtaining Av comprises calculating: Av = floor( (nl + n2 + ... + nN)/N) x 10 )/10.

[0038] Step s510 comprises reporting entity 104 determining whether a reporting condition is satisfied. For example, in one embodiment, determining whether the reporting condition is satisfied comprises the reporting entity 104 determining whether (abs(Av - R))/R > Tl or (abs(Av - R))/R > Tl. In one embodiment, if it is determined that (abs(Av - R))/R > T1 or (abs(Av - R))/R > Tl, then the reporting entity determines that the reporting condition is satisfied and process 500 goes to step s512, otherwise, if the reporting condition is not satisfied (e.g., abs(Av - R))/R < Tl), then process 500 goes back to step s506. In some embodiments, determining whether the reporting condition is satisfied further comprises the reporting entity 104 determining whether more than a threshold amount of time (T2) has elapsed since the last time that step s512 was performed. In some embodiments, the reporting condition is satisfied if more than the threshold amount of time (T2) has elapsed since the last time that step s512 was performed.

[0039] Step s512 comprises reporting entity 104 sending to requesting entity 102 a status update message containing Av.

[0040] Step s514 comprises setting R = Av. After step s514, process 500 goes back to step s506.

[0041] As mentioned above with respect to step s502, message 191 may include the threshold values Tl and T2 (or it may include information enabling reporting entity 104 to determine Tl and T2) and information identifying one or more measurement objects. In some embodiments, message 191 may also include additional information. For example, in one embodiment message 191 may include any one of the information elements shown below in table 1 :

[0042] In some embodiments, requesting entity 102 is a CU (e.g., CU 302) and reporting entity 104 is a DU.

[0043] In another embodiments, requesting entity 102 is a first network node (e.g., a first base station) and reporting entity 104 is a second network node (e.g., a second base station) that comprises CU 302 and multiple DUs. In such an embodiment, the resource status request message transmitted in step s502 may contain a request for measurements on many different cells, and the cells can belong to different DUs controlled by CU 302. In such a scenario, CU 302 must set up subscriptions to the DUs containing the cells that are to be measured (e.g., CU 302 sends a resource status request message to each DU that serves one of the cells that are to be measured). Thus, CU 302 functions a requesting entity 102 with respect to the DUs and functions as a reporting entity with respect to the first network node.

[0044] In some embodiments, CU 302 may receive such a request from multiple requesting entities 102, and must set up subscriptions to the DUs containing the cells that are to be measured (e.g., CU 302 sends a resource status request message to each DU that serves one of the cells that are to be measured). These different requests received by CU 302 may contain different thresholds (e.g., each request may have a different T1 threshold). In this scenario, the CU keeps track of the different thresholds from all incoming requests. The one with the lowest threshold determines the threshold that CU 302 provides to the DUs. For example, assume that CU 302 receives a first request from a first requesting entity with threshold Tla and a second request from a different requesting entity with threshold Tib, where Tla > Tib. In this scenario, CU 302 will send to each DU serving a cell to be measured a request that contains the threshold Tib. Accordingly, when CU 302 receives from a DU a status update message containing the requested measurement value, CU 302 will send at least to the first requesting entity a status update message containing the measurement value received from the DU because the reporting condition will necessarily be satisfied for the first requesting entity, and CU 302 will send to the second requesting entity a status update message containing the measurement value only after CU 302 determines, based on the current measurement value and the measurement value most recently reported to the second requesting entity, that the second requesting entity’s reporting condition is satisfied. That is, when a DU sends an updated measurement CU must keep track of all receivers that wants this information, and apply the appropriate threshold condition and see what neighbor that should get the updated value. Additionally, CU may get one resource status update per DU and CU will aggregate these into a common resource status update to send to the requesting entity that requested the resource status update of cells from many DUs.

[0045] FIG. 6 is a block diagram of reporting entity 104, according to some embodiments. As shown in FIG. 6, reporting entity 104 may comprise: processing circuitry (PC) 602, which may include one or more processors (P) 655 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., reporting entity 104 may be a distributed computing apparatus); at least one network interface 648 comprising a transmitter (Tx) 645 and a receiver (Rx) 647 for enabling reporting entity 104 to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface 648 is connected (directly or indirectly) (e.g., network interface 648 may be wirelessly connected to the network 110, in which case network interface 648 is connected to an antenna arrangement); and a storage unit (a.k.a., “data storage system”) 608, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. In an alternative embodiment the network interface 648 may be connected to the network 110 over a wired connection, for example over an optical fiber or a copper cable. In embodiments where PC 602 includes a programmable processor, a computer program product (CPP) 641 may be provided. CPP 641 includes a computer readable medium (CRM) 642 storing a computer program (CP) 643 comprising computer readable instructions (CRI) 644. CRM 642 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 644 of computer program 643 is configured such that when executed by PC 602, the CRI causes reporting entity 104 to perform steps of the methods described herein (e.g., steps described herein with reference to one or more of the flow charts). In other embodiments, reporting entity 104 may be operative to perform steps of the methods described herein without the need for code. That is, for example, PC 602 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

[0046] In the embodiment illustrated in FIG. 6 the data storage system 608, the processing circuitry 602 and the network interface 648 are connected in series. However, in an alternative embodiment, elements 608, 602 and 648 may be connected to a bus.

[0047] Accordingly, in one aspect the reporting entity 104 is operative to obtain a first measurement value (VI) for a first measurement object. Reporting entity 104 is further operative to obtain a second measurement value (V2) for the first measurement object.

Reporting entity 104 is further operative to determine whether a reporting condition is satisfied. Reporting entity 104 is further operative such that as a result of determining that the reporting condition is satisfied, reporting entity 104 reports V2 to the requesting entity. The reporting entity 104 is operative to determine whether the reporting condition is satisfied by performing a process that comprises comparing AV to a first reporting threshold (Tl), wherein AV is a function of a difference between V2 and VI.

[0048] While various embodiments are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of this disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[0049] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.