Active inter-cell coordination in telecommunication systems

By generating and sharing a local interrupt time database, identifying and coordinating the cell-interval delay priority, the problem of cell-interval delay management in mobile communication systems is solved, and equipment interrupt performance and system resource utilization efficiency are improved.

CN115004750BActive Publication Date: 2024-11-29NOKIA TECHNOLOGIES OY
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202080093791.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-17
Publication Date
2024-11-29
Estimated Expiration
2040-12-17

AI Technical Summary

Technical Problem

The inter-cell delay management in mobile communication systems is difficult to effectively coordinate, resulting in equipment interruption and delay budget mismatch, affecting system performance.

Method used

By generating and sharing a local interrupt time database, the highest priority cell is identified and inter-cell coordination is carried out based on this priority, such as unloading or muting proposals, ensuring the matching of delay budgets and the reasonable allocation of system resources.

Benefits of technology

The overall performance of device interrupts in mobile communication systems is improved, and the overall interrupt performance of the system is improved by optimizing inter-cell coordination, ensuring the matching of delay budgets and the effective utilization of system resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115004750B_ABST
    Figure CN115004750B_ABST
Patent Text Reader

Abstract

A device, method and computer program are described, including: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data includes data of a remaining time to outage for the corresponding device; sending a selected portion of the local outage time database to one or more other cells of the mobile communication network; receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data includes data of a remaining time to outage for one or more devices served by the other cells; and generating a multi-cell outage time database, which includes a portion or all of a shared selected portion of the local outage time database and a portion or all of the received second delay data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to active inter-cell coordination in a telecommunication system, such as active inter-cell coordination based on delay data. Background Art

[0002] Devices within a cell of a mobile communication system may have different delay budgets. Similarly, devices in adjacent cells may have different delay budgets. There is still a need to allocate resources in such a communication system. Summary of the invention

[0003] In a first aspect, the specification describes an apparatus comprising means for performing the following operations: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data of a remaining time to outage for the corresponding device; sending a selected portion of the local outage time database to one or more other cells of the mobile communication network (e.g., comprising adjacent or neighboring cells of the mobile communication network); receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data of a remaining time to outage for one or more devices served by the other cells; and generating a multi-cell outage time database comprising a portion or all of the local outage time database sharing the selected portion and a portion or all of the received second delay data. In this way, the multi-cell outage time database may store data of a time to outage for a plurality of devices served by a plurality of cells of the mobile communication system. For example, the multi-cell outage time database may be a modified version of the local outage time database (including some or all other updates from the other cells).

[0004] In some example embodiments, the apparatus is further configured to perform: sorting the multi-cell outage time database in the order of the data of the remaining time to the outage (e.g., in ascending order). Sorting the multi-cell outage time database in this manner may enable determination of cell delay priorities between multiple cells of the mobile communication system.

[0005] In some example embodiments, the apparatus is further configured to perform: identifying a cell serving a device having a shortest remaining time to interruption as a highest priority cell among the first cell and the other cells.

[0006] The apparatus may also be configured to perform providing inter-cell coordination based on the identified highest priority cell. For example, providing inter-cell coordination may include: determining whether the first cell is lightly loaded; and if the first cell is not the highest priority cell and is lightly loaded, sending an offloading proposal to the identified highest priority cell, proposing to offload one or more latency-critical devices from the highest priority cell to the first cell. The apparatus may also be configured to perform: initiating the offloading of the one or more latency-critical devices upon receiving an acceptance of the offloading proposal from the identified highest priority cell.

[0007] As described above, the apparatus may also be configured to perform providing inter-cell coordination (e.g., based on the identified highest priority cell). For example, providing inter-cell coordination may include: determining whether the first cell is highly loaded; and sending a muting proposal to the identified highest priority cell if the first cell is not the highest priority cell and is highly loaded. The apparatus may also be configured to perform: initiating muting of the first cell upon receiving an acceptance of the muting proposal from the highest priority cell.

[0008] In some example embodiments, providing inter-cell coordination includes: receiving, at a first cell (eg, a highest priority cell), an offload proposal or a muting proposal from one or more of the one or more other cells of the mobile communication system; and responding to the request according to a protocol.

[0009] In some example embodiments, the apparatus is further configured to perform: determining a selected portion of a local outage time database to send to one or more other cells of the mobile communications network (e.g., by determining local outage time database entries having a remaining time to outage below a threshold).

[0010] Sending the selected portion of the local outage time database to the one or more other cells of the mobile communications network may comprise sending an update message via an Xn interface of the communications system.

[0011] In some example embodiments, the apparatus is further configured to perform: identifying a cell of one or more other cells of the mobile communication system as an aggressor cell if a signal power from the other cells at the first cell is above a threshold compared to a signal power received at the first cell from the serving node.

[0012] A local outage time database for a first cell may store one or more of: a cell identifier for the first cell; an identifier for each of a plurality of devices served by the first cell; data on a remaining time to outage for each of the devices (e.g., each radio bearer of each device); a link direction for each device; and a cell identifier for any identified aggressor cell.

[0013] Each entry of the multi-cell outage time database may include: a cell identifier; a device identifier; a remaining time to outage for the corresponding device; and a link direction for each device.

[0014] The apparatus may include: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to together cause execution of the apparatus using the at least one processor.

[0015] In a second aspect, the present specification describes a method comprising: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data on a remaining time to outage for the corresponding device; sending a selected portion of the local outage time database to one or more other cells of the mobile communication network (e.g., including adjacent or neighboring cells of the mobile communication network); receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data on a remaining time to outage for one or more devices served by the other cells; and generating a multi-cell outage time database comprising a portion or all of a shared selected portion of the local outage time database and a portion or all of the received second delay data.

[0016] The method may include sorting the multi-cell outage time database in order of data of remaining time to outage (eg, in ascending order).

[0017] The method may include identifying a cell serving a device having a shortest remaining time to interruption as a highest priority cell among the first cell and the other cells.

[0018] The method may include providing inter-cell coordination based on the identified highest priority cell. For example, providing inter-cell coordination may include: determining whether the first cell is lightly loaded; and if the first cell is not the highest priority cell and is lightly loaded, sending an offload proposal to the identified highest priority cell, proposing to offload one or more latency critical devices from the highest priority cell to the first cell. The method may include: initiating offloading of the one or more latency critical devices upon receiving an acceptance of the offload proposal from the identified highest priority cell.

[0019] Alternatively or additionally, providing inter-cell coordination may include: determining whether the first cell is highly loaded; and if the first cell is not the highest priority cell and is highly loaded, sending a muting proposal to the identified highest priority cell. The method may include: initiating muting of the first cell upon receiving an acceptance of the muting proposal from the highest priority cell.

[0020] In some example embodiments, providing inter-cell coordination includes: receiving, at a first cell (eg, a highest priority cell), an offload proposal or a muting proposal from one or more of the one or more other cells of the mobile communication system; and responding to the request according to a protocol.

[0021] The method may comprise determining a selected portion of a local outage time database to send to one or more other cells of the mobile communications network (eg by determining local outage time database entries having a remaining time to outage below a threshold).

[0022] Sending the selected portion of the local outage time database to the one or more other cells of the mobile communications network may comprise sending an update message via an Xn interface of the communications system.

[0023] The method may comprise identifying a cell of one or more other cells of the mobile communication system as an aggressor cell if a signal power from said other cells at the first cell is above a threshold compared to a signal power received from the server node at the first cell.

[0024] In a third aspect, the present specification describes an apparatus configured to perform any method as described with reference to the second aspect.

[0025] In a fourth aspect, the present specification describes computer readable instructions which, when executed by a computing device, cause the computing device to perform any of the methods as described with reference to the second aspect.

[0026] In a fifth aspect, the present specification describes a computer program comprising instructions for causing a device to perform at least the following operations: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data on a remaining time to outage for the corresponding device; sending a selected portion of the local outage time database to one or more other cells of the mobile communication network (for example, including adjacent or neighboring cells of the mobile communication network); receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data on a remaining time to outage for one or more devices served by the other cells; and generating a multi-cell outage time database comprising a portion or all of a shared selected portion of the local outage time database and a portion or all of the received second delay data.

[0027] In a sixth aspect, the present specification describes a computer-readable medium (such as a non-transitory computer-readable medium) comprising program instructions stored thereon for performing at least the following operations: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data on a remaining time to outage for the corresponding device; sending a selected portion of the local outage time database to one or more other cells of the mobile communication network (for example, comprising adjacent or neighboring cells of the mobile communication network); receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data on a remaining time to outage for one or more devices served by the other cells; and generating a multi-cell outage time database comprising a portion or all of a shared selected portion of the local outage time database and a portion or all of the received second delay data.

[0028] In a seventh aspect, the present specification describes a device comprising: at least one processor; and at least one memory comprising computer program code, which, when executed by the at least one processor, causes the device to: generate a local interruption time database for a first cell of a mobile communication system, wherein the local interruption time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data on a remaining time to interruption for the corresponding device; send a selected portion of the local interruption time database to one or more other cells of the mobile communication network (for example, including adjacent or neighboring cells of the mobile communication network); receive second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data on a remaining time to interruption for one or more devices served by the other cells; and generate a multi-cell interruption time database, comprising a portion or all of a shared selected portion of the local interruption time database and a portion or all of the received second delay data.

[0029] In an eighth aspect, the present specification describes a device comprising: a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data on a remaining time to outage for the corresponding device; an output for providing a selected portion of the local outage time database to one or more other cells of the mobile communication network (e.g., including adjacent or neighboring cells of the mobile communication network); an input for receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data on a remaining time to outage for one or more devices served by the other cells; and a control module for generating a multi-cell outage time database comprising a partial or full shared selected portion of the local outage time database and a partial or full received second delay data.

[0030] In a ninth aspect, the present specification describes a device comprising: a device for generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data on a remaining time to outage for the corresponding device; a device for sending a selected portion of the local outage time database to one or more other cells of the mobile communication network (e.g., comprising adjacent or neighboring cells of the mobile communication network); a device for receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data on a remaining time to outage for one or more devices served by the other cells; and a device for generating a multi-cell outage time database comprising some or all of a shared selected portion of the local outage time database and some or all of the received second delay data. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Example embodiments will now be described, by way of example only, with reference to the following schematic diagrams, in which:

[0032] Figure 1 is a block diagram of a system according to an example embodiment;

[0033] Figure 2 is a table according to an example embodiment;

[0034] Figure 3 and 4 is a block diagram of a system according to an example embodiment;

[0035] Figure 5 is a flow chart showing an algorithm according to an example embodiment;

[0036] Figure 6 is a table according to an example embodiment;

[0037] Figure 7 is a sequence of messages according to an example embodiment;

[0038] Figure 8 is a flow chart illustrating an algorithm according to an example embodiment;

[0039] Fig. 9 is a sequence of messages according to an example embodiment;

[0040] Fig.10 is a flow chart showing an algorithm according to an example embodiment;

[0041] Fig.11 and 12 is a sequence of messages according to an example embodiment;

[0042] Fig.13 is a block diagram of components of a system according to an example embodiment; and

[0043] Fig.14A and 14B Tangible media are shown, which are respectively a removable nonvolatile memory unit and a compact disk (CD) storing computer readable codes, which when executed by a computer, perform operations according to example embodiments. DETAILED DESCRIPTION

[0044] The scope of protection sought by various embodiments of the present invention is defined by the independent claims. Embodiments and features described in the specification that do not belong to the scope of the independent claims, if any, are to be interpreted as examples useful for understanding various embodiments of the present invention.

[0045] In the description and drawings, like reference numerals refer to like elements throughout.

[0046] Figure 1 1 is a block diagram of a system according to an example embodiment, generally indicated by reference numeral 10. System 10 includes a plurality of devices (a first device 12, a second device 13, a third device 14, and a fourth device 15) in communication with a base station 16. Figure 1 10 forms part of a mobile communication system. Figure 1 , user devices are shown, but devices 12 to 15 may take a variety of forms, such as industrial equipment (e.g., robots, machinery, etc.), etc.

[0047] In an example embodiment, each of the plurality of devices 12 to 15 has a delay budget. The delay budget may be defined as the maximum supported duration from the moment a data packet arrives at a transmitter to the moment it is successfully received by an intended receiver. In the event that a device-specific delay budget is violated, such as due to packet loss caused by, for example, inter-cell interference, dynamic TDD cross-link interference, overload, etc., the device may exhibit an outage. For example, in the event that a delay budget of a robotic arm is violated, the robotic arm may be shut down.

[0048] Figure 2 is a table according to an example embodiment, generally indicated by reference numeral 20. Example table 20 shows a portion of a local outage time database (OTD) for system 10 (which may be referred to as a first cell).

[0049] Table 20 Storage:

[0050] • Cell Identifier (Cell ID) for the relevant cell. The Cell Identity is the globally unique Cell ID of the current serving cell.

[0051] · Device identifier (UE ID) for each of a plurality of devices (e.g., the first to fourth devices 12 to 15 above) served by a first cell.

[0052] Data on the remaining time to interruption for each of the devices (e.g., for each radio bearer of each device). The data on the remaining time to interruption is a value in milliseconds and is used to indicate how much time remains before the running radio bearer of an active device enters an interruption if uplink (UL) or downlink (DL) packets of the active device are not successfully processed within a relevant time period. This time can be captured at the packet data convergence protocol (PDCP) layer level. A simple decrementing timer can be used on the cell side to determine the data on the remaining time to interruption, which is initialized with the value of the "maximum latency budget" for each flow. Then, when an active radio bearer flow becomes available for transmission, the timer can be activated. For each transmission time interval (TTI) duration, such a timer can be updated locally because each timer is either reset if the corresponding packet of the flow has been successfully received, or continues to decrement if the corresponding packet is still pending, e.g., causing packet loss or multiple HARQ retransmissions.

[0053] · The link direction of each device, e.g., whether the expected link direction is uplink (UL) or downlink (DL).

[0054] · Cell identifier (cell ID) for any identified intruder cell. This entry includes the reported cell ID of the downlink intruder cell reported by the active device in the downlink direction. In an example embodiment, the serving cell of a mobile communication system first configures inter-cell interference measurement for its active devices. Through higher RRC signaling, the cell can configure its devices to identify downlink interference intruder cells by measuring the reference signal received power (RSRP) of adjacent cells. Thus, the device reports the serving cell using the physical cell ID (PCI) ID of adjacent cells with comparable RSRP coverage as follows: cells satisfying RSRP serving -RSRP neighbor < of P, where P is a predefined RSRP threshold sent via physical downlink control channel (PDCCH) signaling.

[0055] Example embodiments of the principles described herein include adjacent cells in an industrial or factory environment, which are associated with a strict radio latency budget for each connected device. Example applications include:

[0056] · Both frequency division duplex (FDD) and dynamic time division duplex (TDD) modes.

[0057] Ultra-reliable low-latency communication (URLLC) deployment with sporadic packet arrival and dynamic user scheduling.

[0058] Time-sensitive communication (TSC) deployment with deterministic packet arrival and semi-persistent scheduling.

[0059] Figure 3 is a block diagram of a system, generally indicated by the reference number 30 , according to an example embodiment.

[0060] System 30 includes a first cell 31 and a second cell 32, both communicating with a core network 33. First cell 31 includes a communication node 35 (such as a base station), a first device 36 and a second device 37. Second cell 32 includes a communication node 38 (such as a base station), a third device 39 and a fourth device 40.

[0061] The first to fourth devices of the system 30 all have a delay budget. For example, as shown in the system 30, the first device 36 has a first delay budget 41, the second device 37 has a second delay budget 42, the third device 39 has a third delay budget 43, and the fourth device 40 has a fourth delay budget 44.

[0062] Figure 4 is a block diagram of a system generally indicated by reference numeral 50 according to an example embodiment. System 50 is a mobile communication system including a first cell 51, a second cell 52, and a third cell 53. Each of cells 51 to 53 may be similar to cells 31 and 32 described above. A local outage time database (OTD) may be generated for each of cells 51 to 53, and at least some data of the OTD (such as the OTD) may be transmitted between the cells. Figure 4 ).

[0063] As described below, exchanging outage time database (OTD) data between neighboring cells enables these cells to work together to seek to achieve device-specific delay-aware coordinated transmission. For example, at any time, devices with low dynamically calculated delay tolerance before outage can be prioritized to improve the overall outage performance of the system 50.

[0064] Figure 5 is a flow chart showing an algorithm generally indicated by reference numeral 60 according to an example embodiment.

[0065] Algorithm 60 begins at operation 62, where a local outage time database (OTD) is generated for a first cell of a mobile communication system (such as one of cells 31 and 33 of system 30 or one of cells 51 to 53 of system 50). As described above, the local outage time database stores a delay time budget for each of a plurality of devices served by the first cell, wherein each delay budget includes data on a remaining time remaining until outage for the corresponding device.

[0066] At operation 64, some or all of the delay data of the first cell is shared by one or more other cells. For example, the delay data generated for the first cell 51 described above may be shared by the second and third cells 52 and 53 of the system 50. Sharing the delay data may include sending selected portions of the local outage time database to one or more other cells of the mobile communication network. These cells may be adjacent or neighboring cells of the relevant mobile communication network. Operation 64 may be implemented by generating a local outage time database (OTD) such as the above-mentioned OTD20 and sending some or all of the OTD to other cells.

[0067] For example, each cell may share latency data for all entries in the relevant local OTD where the remaining time to outage is below a predefined latency threshold.

[0068] The sharing of the delay data in operation 64 may be different for uplink and downlink transmissions.

[0069] For downlink transmissions, in the presence of a downlink (DL) aggressor cell reported by a device, the cell may exchange these corresponding entries as part of an OTD update message (e.g., an information object). The OTD update message may be sent only with those DL aggressor neighbor cells (e.g., over an Xn interface). The OTD update message may include the following data: cell ID, UE ID, remaining time to interruption for each DRB per UE, and link direction for each DRB per UE. In the absence of a DL aggressor cell reported for the corresponding device, the cell may skip these entries from the inter-cell exchange, because in this case, neither coordinated ICIC nor traffic offloading is applicable.

[0070] For uplink transmission, the cell may send these corresponding entries as OTD update messages to all layer 1 neighboring cells (e.g., via the Xn interface). As described above, the OTD update message may include: cell ID, UE ID, remaining time to interruption for each DRB per UE, and link direction for each DRB per UE.

[0071] At operation 66, latency data is received (at the first cell) from at least one of the one or more other cells of the mobile communication system, wherein the latency data includes data of a remaining time to interruption for one or more devices served by the other cells. For example, the first cell 51 may receive latency data (e.g., in the form of an OTD or a portion of an OTD) from the second cell 52 and / or the third cell 53 of the system 50.

[0072] At operation 68, a multi-cell outage time database is generated at the first cell (e.g., cell 51). The multi-cell OTD may be a modified version of the local OTD generated at the first cell. For example, the local OTD may be modified to include updates from other cells (i.e., some or all of the delay data received in operation 66) to generate the multi-cell OTD.

[0073] In the case of system 50, the first cell 51 may generate a multi-cell OTD by modifying the local OTD generated in the first cell using the delay data obtained from other cells in the system 50. Similarly, each of the second cell 52 and the third cell 53 may generate a multi-cell OTD by modifying the local OTD generated in the corresponding cell using the delay data obtained from other cells in the system 50.

[0074] Figure 6 is a table, generally indicated by reference numeral 70, according to an example embodiment. Table 70 shows an excerpt of an example multi-cell outage time database (OTD).

[0075] Table 70 stores:

[0076] • A cell identifier (cell ID) for the relevant cell. The cell identity is the globally unique cell ID of the current serving cell. In the example table 70, the first entry relates to data from a first cell and the second entry relates to data from a third cell.

[0077] Equipment Identifier (UE ID).

[0078] Data on the remaining time until interruption for the respective device.

[0079] The link direction for the corresponding device.

[0080] Thus, table 70 includes similar entries as table 20 described above. In the specific example table 70, the aggressor cell IDs are not reported (although they may be reported in some example embodiments). One reason for omitting the aggressor cell IDs is that a first cell receiving an OTD update from a neighboring cell may understand that the first cell is acting as an aggressor to the neighboring cell.

[0081] Figure 7is a message sequence generally indicated by reference numeral 80 according to an example embodiment. Message sequence 80 shows messages transmitted between cell 1 (such as first cell 51 described above), cell 2 (such as second cell 52 described above), and cell 3 (such as third cell 53 described above).

[0082] In operation 82, each cell establishes a separate outage time database (OTD). Operation 82 includes a plurality of steps.

[0083] Each cell first configures inter-cell interference measurements for its active devices.

[0084] Through higher RRC signaling, each cell configures its equipment to identify downlink interference aggressor cells by measuring the RSRP of neighboring cells. Therefore, the device reports the serving cell with the PCI ID of the neighboring cell with comparable RSRP coverage as: serving -RSRP neighbor < cell, where P is a predefined RSRP threshold signaled via PDCCH.

[0085] Therefore, the maximum interruption delay budget of each active device can be identified from the core entity processing the QoS PDCP flow.

[0086] Based on the information generated as described above, a local OTD may be generated in each cell (thereby implementing operation 62 of algorithm 60). As described above, each locally generated OTD includes the following data: cell ID; user ID; remaining time to interruption (ms) for each DRB for each UE; link direction for each DRB for each UE; and DL aggressor cell ID for each UE.

[0087] Load information is exchanged between the cells as part of the Xn interface specification at operation 84. In this way, each cell is aware of the load level of its surrounding cells.

[0088] At operation 86, the first cell determines that a connected device of the first cell is approaching an outage condition. This condition may be detected based on outage time data of a locally generated OTD.

[0089] In response to the detection of operation 86, an OTD update (information object) is sent to the second cell using message 88a, and an OTD update (information object) is also sent to the third cell using message 88b.

[0090] For the downlink direction, in case there are device reported DL aggressor cells, the OTD update can be shared with only those DL aggressor neighbor cells. In case there are no DL aggressor cells reported for the corresponding device, the OTD update message can be omitted, because in this case, neither coordinated ICIC nor traffic offloading is applicable.

[0091] For the uplink direction, as described above, the first cell sends an OTD update message to all first layer neighboring cells.

[0092] Figure 8 is a flow chart showing an algorithm generally indicated by reference numeral 90 according to an example embodiment.

[0093] Algorithm 90 assumes that the multi-cell OTD has been obtained or generated. For example, the multi-cell OTD may be generated using algorithm 60 described above.

[0094] The algorithm 90 begins at operation 92, where a multi-cell outage time database (OTD) obtained or generated is sorted in the order of the data of the remaining time to outage. For example, the multi-cell OTD can be sorted in ascending order of the remaining time to outage. This sorting can enable determination of cell delay priorities in multiple cells of a mobile communication system.

[0095] At operation 94, the highest priority cell is identified. For example, operation 94 may identify the cell serving the device having the shortest remaining time to interruption as the highest priority cell among cells of the communication system (such as cells 31 and 32 or cells 51 to 53 described above).

[0096] At operation 96, inter-cell coordination is provided based on the highest priority cell identified in operation 94. A number of example options for inter-cell coordination are described in detail below.

[0097] It should be noted that, assuming efficient link adaptation and user scheduling are in place, violations of PDCP (i.e., DRB), flow-specific delay bounds are typically attributable to capacity overload or strong inter-cell interference. Therefore, active inter-cell coordination with the aid of traffic offloading or interference coordination is an attractive option. The example embodiments herein describe device-specific delay-aware embodiments (rather than average cell delay awareness that may result in device-specific outage events).

[0098] Fig. 9 is a message sequence generally indicated by reference numeral 100 according to an example embodiment. The message sequence 100 is an example implementation of the algorithm 90 described above, for example using the system 50 described above, which includes a first cell 51, a second cell 52 and a third cell 53.

[0099] At operation 101, a first cell cell1 (e.g., a first cell) 51 ranks the multi-cell OTD generated or obtained by the first cell. Similarly, at operation 102, a second cell cell2 (e.g., a second cell 52) ranks the multi-cell OTD generated or obtained by the second cell, and at operation 103, a third cell cell3 (e.g., a third cell 53) ranks the multi-cell OTD generated or obtained by the third cell. Thus, operations 101 to 103 implement operation 92 of the algorithm 90 described above.

[0100] At operation 105, the second cell identifies the first cell as the highest priority cell (thereby implementing one instance of operation 94 of the above algorithm 90). Similarly, at operation 106, the third cell identifies the first cell as the highest priority cell (thereby implementing another instance of operation 94 of the above algorithm 90).

[0101] In response to identifying that the first cell has the highest priority, the second cell exchanges message 108 with the first cell and the third cell exchanges message 109 with the first cell. Messages 108 and 109 (examples of which are discussed further below) are example implementations of operation 96 described above.

[0102] Operation 96 (and messages 108 and 109) may take many different forms.

[0103] Fig.10 is a flow chart showing an algorithm generally indicated by reference numeral 110 in accordance with an example embodiment. Algorithm 110 is an example implementation of operation 96.

[0104] The algorithm 110 is implemented at a cell of a communication system having multiple cells, such as the system 50 described above, including a first cell that has been determined (in the example of operation 94 described above) to be not a highest priority cell.

[0105] At operation 112, the first cell determines that protective inter-cell coordination is required.

[0106] At operation 114 , it is determined whether the first cell is lightly loaded. If so (such that the first cell is not among the highest priority cells and is lightly loaded), the algorithm moves to operation 116 ; otherwise, the algorithm moves to operation 116 . Otherwise, the algorithm moves to operation 118 .

[0107] At operation 116, an offload proposal is sent (from the first cell) to the identified highest priority cell, proposing to offload one or more latency critical devices from the highest priority cell to the first cell. Algorithm 110 then terminates at operation 122. As discussed in detail below, offloading the one or more latency critical devices to the first cell may be implemented upon receiving an acceptance of the offload proposal from the identified highest priority cell.

[0108] At operation 118 , it is determined whether the first cell is highly loaded. If so (such that the first cell is not the highest priority cell and is highly loaded), the algorithm moves to operation 120 ; otherwise, the algorithm terminates at operation 122 .

[0109] At operation 120, a muting proposal is sent (from the first cell) to the identified highest priority cell, proposing that the first cell be muted. Algorithm 110 then terminates at operation 122. As discussed in detail below, muting of the first cell may be implemented upon receiving an acceptance of the muting proposal from the identified highest priority cell.

[0110] It should be noted that in algorithm 110 (and in the message sequences described in detail below), muting and offloading proposals are triggered by the cell providing active inter-cell assistance (rather than the cell requesting such assistance). Since the cell providing assistance knows its own conditions, it can provide inter-cell coordination (such as muting or offloading suggestions) that it can accept. If such a proposal is accepted, it can be executed immediately without any further message exchange. In contrast, some example systems in which a cell requests assistance (such as muting or offloading assistance) may require another round or more of additional inter-cell signaling to determine the parameters of the assistance to be given. In embodiments with tight latency budgets, it may be advantageous to reduce the number of rounds of inter-cell signaling.

[0111] Fig.11 is a message sequence generally indicated by reference numeral 130 according to an example embodiment. Message sequence 130 shows messages transmitted between cell 1 (such as first cell 51 described above), cell 2 (such as second cell 52 described above), and cell 3 (such as third cell 53 described above).

[0112] At operation 82, each cell establishes an individual / local outage time database (OTD). As discussed further above, operation 82 includes a number of steps.

[0113] Load information is exchanged between the cells as part of the Xn interface specification at operation 84. In this way, each cell is aware of the load level of its surrounding cells.

[0114] At operation 132a, it is determined that cell 1 is highly loaded. Similarly, at operation 132b, it is determined that cell 2 is highly loaded, and at operation 132c, it is determined that cell 3 is highly loaded.

[0115] At operation 134a, it is determined that the uplink device at cell 1 is approaching an outage condition (i.e., the time to outage of the uplink device is below a threshold level). In response to the determination at operation 134a, an OTD update message 136a is sent from cell 1 to cell 2 and an OTD update message 136b is sent from cell 1 to cell 3. As described above, the OTD update messages 136a and 136b cause multi-cell OTD to be generated at cells 2 and 3.

[0116] Similarly, at operation 134b, it is determined that the uplink device at cell 3 is approaching an outage condition (i.e., the time to outage of the uplink device is below a threshold level). In response to the determination at operation 134b, an OTD update message 138a is sent from cell 3 to cell 1 and an OTD update message 138b is sent from cell 3 to cell 2. As described above, the OTD update messages 138a and 138b cause multi-cell OTD to be generated at cells 1 and 2.

[0117] At this stage, multi-cell OTDs are generated at each cell and these can be sorted locally. This enables the relative priority of the cells to be determined (so that the cell with the shortest remaining time to outage can be identified).

[0118] In operation 140a, it is determined (in cell 1) that cell 1 has the highest priority and cell 3 has the second highest priority. Similar determinations are made in operation 140b (in cell 2) and operation 140c (in cell 3).

[0119] At cell 3, it is determined that cell 3 is highly loaded, but is not the highest priority cell. As a result, a muting proposal 142 is sent from cell 3 to the highest priority cell (cell 1 in this example). The muting proposal 142 proposes to cell 1 to mute cell 3 in order to provide proactive inter-cell coordination.

[0120] Similarly, at cell 2, it is determined that cell 2 is highly loaded, but not the highest priority cell. As a result, a muting proposal 143 is sent from cell 2 to the highest priority cell (cell 1). The muting proposal 143 proposes to cell 1 to mute cell 3 in order to provide active inter-cell coordination.

[0121] Therefore, the two lower priority cells (ie, cells with larger remaining time to outage) proactively propose inter-cell interference coordination (ICIC) assistance to the highest priority cell (cell 1) by exchanging muting proposal messages.

[0122] Cell 1 sends a first recommended muting message 144 to cell 3 and a second recommended muting message 145 to cell 2. The recommended muting messages 144 and 145 provide suggested muting configurations.

[0123] The first recommend-to-mute message 144 is accepted by cell 3 and an acceptance message 146 is sent to cell 1. Similarly, the second recommend-to-mute message 145 is accepted by cell 2 and an acceptance message 147 is sent to cell 1.

[0124] At operations 148a and 148b, corresponding muting proposals are implemented at cells 2 and 3, respectively, so that inter-cell interference-free uplink transmissions 150 can occur at cell 1. Operations 148a, 148b, and 150 collectively form inter-cell coordination (thereby implementing operation 96 of algorithm 90 described above).

[0125] Fig.12 is a message sequence generally indicated by reference numeral 160 according to an example embodiment. Message sequence 160 shows messages transmitted between cell 1 (such as first cell 51 described above), cell 2 (such as second cell 52 described above), and cell 3 (such as third cell 53 described above).

[0126] At operation 82, each cell establishes an individual / local outage time database (OTD). As discussed further above, operation 82 includes a number of steps.

[0127] Load information is exchanged between the cells as part of the Xn interface specification at operation 84. In this way, each cell is aware of the load level of its surrounding cells.

[0128] At operation 162a, it is determined that cell 1 is highly loaded. Similarly, at operation 162b, it is determined that cell 3 is highly loaded. However, at operation 163, it is determined that cell 2 is lightly loaded.

[0129] At operation 164, it is determined that the connected downlink device at cell 1 is approaching an outage condition (i.e., the time to outage of the downlink device is below a threshold level). In response to the determination at operation 164, an OTD update message 166a is sent from cell 1 to cell 2 and an OTD update message 166b is sent from cell 1 to cell 3. As described above, the OTD update messages 166a and 166b cause multi-cell OTD to be generated at cells 2 and 3.

[0130] At this stage, multi-cell OTDs are generated at each cell and can be locally ranked. This enables the relative priority of the cells to be determined (enabling the identification of the cell with the shortest remaining time to outage).

[0131] In operation 168a, it is determined (in cell 1) that cell 1 has the highest priority. Similar determinations are made in operation 168b (in cell 2) and operation 168c (in cell 3).

[0132] At cell 2, it is determined that cell 2 is lightly loaded and is not the highest priority cell. As a result, an offload proposal 170 is sent from cell 2 to the highest priority cell (cell 1 in this example). The offload proposal 170 recommends downlink offload assistance to cell 1.

[0133] At cell 3, it is determined that cell 3 is highly loaded, but not the highest priority cell. As a result, a muting proposal 172 is sent from cell 3 to the highest priority cell (cell 1 in this example). The muting proposal 142 proposes to cell 1 to mute cell 3 in order to provide proactive inter-cell coordination.

[0134] Therefore, both lower priority cells (ie, cells with longer remaining time to outage) proactively propose inter-cell interference coordination (ICIC) assistance to the highest priority cell (cell 1); however, the nature of the coordination assistance provided is different.

[0135] Cell 1 accepts the proposal to offload the latency degrading equipment to cell 2 (and therefore sends an acceptance message 174 to cell 2). Therefore, cell 1 rejects the assistance offered by cell 3 (and therefore sends a rejection message 175 to cell 3).

[0136] Upon receiving the rejection message 175, cell 3 discards the muting proposal and thus does not implement the proposed muting.

[0137] In operations 176 and 178, the offloading proposal is implemented by cell 1 and cell 2. Operations 176 and 178 together form inter-cell coordination (thereby implementing operation 96 of algorithm 90 described above).

[0138] Message sequences 130 and 160 thus describe an example protocol for generating offload and mute proposals and also describe an example protocol for responding to offload and mute proposals.

[0139] Based on the updated multi-cell OTD at each cell, the cells proactively coordinate to seek to ensure fast and interference-controlled conditions for the cells with the most critical flows.

[0140] The target cell updates its own OTD with the OTD entries received from the neighboring source cells. The target cell then identifies the most critical source cell with the shortest time-to-outage entry. Accordingly, the target cell becomes aware of the actual latency performance of its own connected devices and the critical surrounding source cells. Therefore, depending on its load and interference conditions, the cell can proactively send an offload proposal or a muting proposal to the critical, i.e., highest priority, source cell over the Xn interface.

[0141] The offload proposal indicates that the target cell proposes to offload critical devices with emergency DRB flows from the source cell to the target cell. The muting proposal may indicate that the target cell recommends muting of certain UL / DL resources in order to facilitate interference-free transmission of critical DRB payloads in the source cell.

[0142] Furthermore, if the target cell cannot mute certain resources or accept traffic offloading from the source cell, it sends neither offloading proposal nor muting proposal and should be excluded from the coordination.

[0143] At the source cell, after receiving an offload proposal and / or muting proposal from a neighboring cell, a cross-cell conflict may occur. Therefore, to resolve the potential conflict, the source cell sends back an "Accept", "Reject", "Recommend Offload" or "Recommend Muting" message as shown below:

[0144] Accept: The source cell accepts the corresponding proposal from the target cell (without any change to the proposal).

[0145] Rejection: The source cell rejects the corresponding proposal from the target cell and no further action is required, that is, no further coordination is required between the source cell and the target cell.

[0146] Recommended offloading: The source cell sends back the corresponding target cell with the recommended offloading configuration in response to the offloading proposal. This can be useful in cases where the state of the latency degraded device has changed quickly (payload has been transmitted / further retransmitted) before a new OTD update is sent from the source cell to the target cell.

[0147] Recommended muting: The source cell sends a recommended muting configuration back to the corresponding target cell in response to a muting proposal. This can be used to resolve potential conflicts. For example, two target cells may provide muting proposals for adjacent critical source cells, where various proposed timing and frequency resources are to be muted. Thus, the source cell can recommend a common muting configuration for all target cells and thus schedule latency-degraded devices on the agreed resources with interference-free conditions.

[0148] It should be noted that in message sequences 130 and 160, various muting and offloading suggestions are triggered by a cell providing muting or offloading support to another cell (e.g., from a target cell to a source cell), thereby providing proactive inter-cell assistance. This is different from a mechanism where a cell requiring support requests support from other nearby cells (e.g., by sending a request from a source cell to a target cell). In a system where a source cell (requiring support) sends a request to one or more target cells, each target cell may accept or reject the request, and therefore another round of coordination / signaling may be required to agree on a particular inter-cell coordination. In embodiments with very strict latency budgets, it may be advantageous to implement a system without such additional rounds of inter-cell signaling.

[0149] For the sake of completeness, Fig.13 is a schematic diagram of components of one or more of the example embodiments described previously, which are hereinafter collectively referred to as processing system 300. Processing system 300 may be, for example, an apparatus as referred to in the following claims.

[0150] The processing system 300 may include one or more of the following: a processor 302, a memory 304 tightly coupled to the processor and including a RAM 314 and a ROM 312, a user input 310 (such as a touch screen input, a hardware keyboard, and / or a voice input mechanism), and a display 318 (at least some of these components may be omitted in some example embodiments). The processing system 300 may include one or more network / device interfaces 308 for connecting to a network / device, such as a network / device that may be a wired or wireless modem. The interface 308 may also operate as a connection to other devices, such as devices / apparatus that are not network-side devices. Thus, direct connections between devices / apparatuses without network involvement are possible.

[0151] Processor 302 is connected to each of the other components to control their operation.

[0152] The memory 304 may include non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD). The ROM 312 of the memory 304 stores, among other things, an operating system 315 and may store software applications 316. The processor 302 uses the RAM 314 of the memory 304 to temporarily store data. The operating system 315 may include code that implements aspects of the algorithms 60, 90 and 110 or the message sequences 80, 100, 130 and 160 described above when executed by the processor. Please note that in the case of a small device / apparatus, the memory may be best suited for small size use, i.e., a hard disk drive (HDD) or a solid state drive (SSD) is not always used. The memory 304 may include computer program code, so that at least one memory 304 and a computer program may be configured to employ at least one processor 302 to induce the performance of the device.

[0153] Processor 302 may take any suitable form. For example, it may be a microcontroller, multiple microcontrollers, a processor, or multiple processors.

[0154] The processing system 300 may be a standalone computer, server, console or network thereof. The processing system 300 and the required structural components may all be inside a device / equipment such as an IoT device / equipment, i.e. embedded in a very small size.

[0155] In some example embodiments, the processing system 300 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partially or exclusively on the remote server device / apparatus. These applications may be referred to as cloud-hosted applications. The processing system 300 may communicate with the remote server device / apparatus in order to utilize the software applications stored there.

[0156] Fig.14A and 14B Tangible media are shown separately, namely a removable memory unit 365 and a compact disk (CD) 368, which store computer readable code that can execute the method according to the above-mentioned example embodiment when run by a computer. The removable storage unit 365 can be a memory stick, for example, a USB memory stick, which has an internal memory 366 storing computer readable code. The computer system can access the internal memory 366 via a connector 367. The CD 368 can be a CD-ROM or a DVD or the like. Other forms of tangible storage media can be used. The tangible medium can be any device / device capable of storing data / information that can be exchanged between devices / devices / networks.

[0157] Embodiments of the present invention may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside in memory or on any computer medium. In an example embodiment, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "memory" or "computer-readable medium" may be any non-transitory medium or device that can contain, store, communicate, propagate, or transmit instructions for use by or in conjunction with an instruction execution system, device, or apparatus, such as a computer.

[0158] Where relevant, references to "computer readable medium", "computer program product", "tangibly embodied computer program", etc. or "processor" or "processing circuitry", etc. should be understood to include not only computers with different architectures, such as single / multi-processor architectures and sequencer / parallel architectures, but also computers with special purpose circuits, such as field programmable gate arrays FPGAs, application specific circuits ASICs, signal processing devices / apparatuses and other devices / apparatuses. References to computer programs, instructions, codes, etc. should be understood to mean express software for programmable processor firmware, such as the programmable content of a hardware device / apparatus as instructions for a processor or configured settings or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc.

[0159] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. In addition, if desired, one or more of the above functions may be optional or may be combined. Similarly, it will also be understood that Figure 5 and 7 The flowcharts and message sequences of FIGS. 1 to 12 are merely examples and the various operations described therein may be omitted, reordered and / or combined.

[0160] It should be understood that the above exemplary embodiments are purely illustrative and do not limit the scope of the present invention.Other changes and modifications will be apparent to those skilled in the art after reading this specification.

[0161] Furthermore, the disclosure of the present application should be understood to include any novel feature or any novel combination of features disclosed herein explicitly or implicitly, or any generalization thereof, and during the prosecution of the present application or any application derived therefrom, new claims may be formulated to cover any such feature and / or combination of such features.

[0162] Although various aspects of the invention are set out in the independent claims, further aspects of the invention comprise other combinations of features from the described exemplary embodiments and / or the dependent claims with features of the independent claims and not just the combinations explicitly set out in the claims.

[0163] It should also be noted here that although various examples are described above, these descriptions should not be viewed in a limiting sense. On the contrary, several changes and modifications may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

1. A device for communication, comprising: means for generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data of a remaining time to outage for a corresponding device; means for transmitting selected portions of said local outage time database to one or more other cells of said mobile communications system; means for receiving second delay data from at least one of the one or more other cells of the mobile communication system, wherein the second delay data comprises data of a remaining time to interruption for one or more devices served by the other cell; and The device is used to generate a multi-cell outage time database, wherein the multi-cell outage time database includes part or all of the shared selected part of the local outage time database and part or all of the received second delay data.

2. The device of claim 1, further comprising: Means for sorting the multi-cell outage time database in order of data of remaining time to outage.

3. The device according to claim 1 or 2, further comprising: Means for identifying a cell serving a device having a shortest outage time as a highest priority cell among the first cell and other cells.

4. The apparatus of claim 3, further comprising: Means for providing inter-cell coordination based on the identified highest priority cell.

5. The device of claim 4, wherein: Providing inter-cell coordination includes: determining whether the first cell is lightly loaded; and In the case that the first cell is not the highest priority cell and is lightly loaded, an offloading proposal is sent to the identified highest priority cell, proposing to offload one or more delay critical devices from the highest priority cell to the first cell.

6. The device of claim 5, further comprising: Means for initiating offloading of the one or more latency critical devices upon receiving an acceptance of the offloading proposal from the identified highest priority cell.

7. The apparatus according to any one of claims 4 to 6, wherein: Providing inter-cell coordination includes: determining whether the first cell is highly loaded; and In case the first cell is not the highest priority cell and is highly loaded, a muting proposal is sent to the identified highest priority cell.

8. The apparatus of claim 7, further comprising: means for initiating muting of the first cell upon receiving an acceptance of the muting proposal from the highest priority cell.

9. The apparatus according to any one of claims 4 to 6, wherein: Providing inter-cell coordination includes: receiving, at the first cell, an offloading proposal or a muting proposal from one or more of the one or more other cells of the mobile communication system; and Respond to requests according to the protocol.

10. The device according to claim 1 or 2, further comprising: Means for determining a selected portion of the local outage time database for transmission to one or more other cells of the mobile communication system.

11. The device according to claim 1 or 2, wherein: Sending the selected portion of the local outage time database to the one or more other cells of the mobile communication system comprises sending an update message via an Xn interface of the communication system.

12. The device according to claim 1 or 2, further comprising: Means for identifying a cell of one or more other cells of the mobile communication system as an aggressor cell if a signal power at the first cell from said other cells is above a threshold compared to a signal power received at the first cell from a server node.

13. The device according to claim 1 or 2, wherein: The local outage time database of the first cell stores one or more of the following: a cell identifier for the first cell; an identifier for each of the plurality of devices served by the first cell; data of the time remaining to interruption for each of said devices; a link direction for each of said devices; as well as Cell identifiers for any identified aggressor cells.

14. The device according to claim 1 or 2, wherein: Each entry of the multi-cell outage time database comprises: cell identifier; Device identifier; The time to interruption for the corresponding device; and The link direction for each of said devices.

15. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the apparatus to perform at least the following steps using the at least one processor: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data of a remaining time to outage for a corresponding device; transmitting a selected portion of the local outage time database to one or more other cells of the mobile communication system; receiving second latency data from at least one of the one or more other cells of the mobile communication system, wherein the second latency data comprises data of a remaining time to interruption for one or more devices served by the other cell; and A multi-cell outage time database is generated, which includes part or all of the shared selected part of the local outage time database and part or all of the received second delay data.

16. The device of claim 15, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: The multi-cell outage time database is sorted in the order of data of the remaining time to the outage.

17. The apparatus of claim 15 or 16, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: The cell serving the device with the shortest interruption time is identified as the highest priority cell among the first cell and other cells.

18. The apparatus of claim 17, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: Inter-cell coordination is provided based on the identified highest priority cell.

19. The apparatus of claim 18, wherein: Providing inter-cell coordination includes: determining whether the first cell is lightly loaded; and In the case that the first cell is not the highest priority cell and is lightly loaded, an offloading proposal is sent to the identified highest priority cell, proposing to offload one or more delay critical devices from the highest priority cell to the first cell.

20. The apparatus of claim 19, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: Upon receiving an acceptance of the offloading proposal from the identified highest priority cell, offloading of the one or more latency critical devices is initiated.

21. The apparatus of any one of claims 18 to 20, wherein: Providing inter-cell coordination includes: determining whether the first cell is highly loaded; and In case the first cell is not the highest priority cell and is highly loaded, a muting proposal is sent to the identified highest priority cell.

22. The apparatus of claim 21, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: Muting of the first cell is initiated upon receiving an acceptance of the muting proposal from the highest priority cell.

23. The apparatus of any one of claims 18 to 20, wherein: Providing inter-cell coordination includes: receiving, at the first cell, an offloading proposal or a muting proposal from one or more of the one or more other cells of the mobile communication system; and Respond to requests according to the protocol.

24. The apparatus of claim 15 or 16, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: A selected portion of the local outage time database is determined for transmission to one or more other cells of the mobile communication system.

25. The apparatus of claim 15 or 16, wherein: Sending the selected portion of the local outage time database to the one or more other cells of the mobile communication system comprises sending an update message via an Xn interface of the communication system.

26. The apparatus of claim 15 or 16, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the device to at least perform the following steps: A cell of one or more other cells of the mobile communication system is identified as an aggressor cell if a signal power at the first cell from the other cells is above a threshold compared to a signal power received at the first cell from the server node.

27. The apparatus of claim 15 or 16, wherein: The local outage time database of the first cell stores one or more of the following: a cell identifier for the first cell; an identifier for each of the plurality of devices served by the first cell; data of the time remaining to interruption for each of said devices; a link direction for each of said devices; as well as Cell identifiers for any identified aggressor cells.

28. The apparatus of claim 15 or 16, wherein: Each entry of the multi-cell outage time database comprises: cell identifier; Device identifier; The time to interruption for the corresponding device; and The link direction for each of said devices.

29. A method for communication, comprising: generating a local outage time database for a first cell of a mobile communication system, wherein the local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data of a remaining time to outage for a corresponding device; transmitting a selected portion of the local outage time database to one or more other cells of the mobile communication system; receiving second latency data from at least one of the one or more other cells of the mobile communication system, wherein the second latency data comprises data of a remaining time to interruption for one or more devices served by the other cell; and A multi-cell outage time database is generated, which includes part or all of the shared selected part of the local outage time database and part or all of the received second delay data.

30. The method of claim 29, further comprising: The multi-cell outage time database is sorted in the order of data of the remaining time to the outage.

31. The method of claim 29 or 30, further comprising: The cell serving the device with the shortest interruption time is identified as a highest priority cell among the first cell and other cells.

32. The method of claim 31 , further comprising: Inter-cell coordination is provided based on the identified highest priority cell.

33. The method of claim 32, wherein: Providing inter-cell coordination includes: determining whether the first cell is lightly loaded; and In the case that the first cell is not the highest priority cell and is lightly loaded, an offloading proposal is sent to the identified highest priority cell, proposing to offload one or more delay-critical devices from the highest priority cell to the first cell.

34. The method of claim 32 or 33, wherein: Providing inter-cell coordination includes: determining whether the first cell is highly loaded; and In case the first cell is not the highest priority cell and is highly loaded, a muting proposal is sent to the identified highest priority cell.

35. The method of any one of claims 32 to 33, wherein: Providing inter-cell coordination includes: receiving, at the first cell, an offloading proposal or a muting proposal from one or more of the one or more other cells of the mobile communication system; and Respond to requests according to the protocol.

36. The method of any one of claims 29 to 30, further comprising: A selected portion of the local outage time database is determined for transmission to the one or more other cells of the mobile communication system.

37. The method of any one of claims 29 to 30, further comprising: In case a signal power at the first cell from the other cells is above a threshold compared to a signal power received at the first cell from a server node, a cell of the one or more other cells of the mobile communication system is identified as an aggressor cell.

38. A computer readable medium comprising program instructions stored thereon for causing a device to at least: A local outage time database is generated for a first cell of a mobile communication system, wherein: The local outage time database stores first delay data for each of a plurality of devices served by the first cell, wherein each first delay data comprises data of a remaining time to outage for a corresponding device; transmitting a selected portion of the local outage time database to one or more other cells of the mobile communication system; receiving second latency data from at least one of the one or more other cells of the mobile communication system, wherein the second latency data comprises data of a remaining time to interruption for one or more devices served by the other cell; as well as A multi-cell outage time database is generated, which includes part or all of the shared selected part of the local outage time database and part or all of the received second delay data.

Citation Information

Patent Citations

  • Method of detecting an outage of a radio cell

    EP2129175A1

  • System and Methods for Estimation and Improvement of User, Service and Network QOE Metrics

    US20140269269A1

  • Threshold for reduced latency mechanisms

    US20190007324A1

  • Methods and apparatuses to estimate and exchange latency and / or reliability information for dual or multi connectivity operation

    WO2019170209A1