Spectrum access restrictions and reallocation of transmission time resources

Abstract

The node transmits on the communication link (111, 112) using transmit time resources from a resource budget (700, 752) associated with spectrum access restrictions imposed on the second node (102).

Description

Technical Field

[0001] Various examples generally relate to communication using transmit time resources from a budget associated with spectrum access restrictions. Various examples specifically relate to fully or partially reallocating transmit time resources from a second node to a first node. Background Art

[0002] Wireless communication is ubiquitous. The number of wireless communication devices (sometimes also referred to as mobile devices or user equipment UE) is expected to increase further, for example as part of a trend known as the Internet of Things (IoT).

[0003] However, the resources on the electromagnetic spectrum are limited. Therefore, there may be scenarios where nodes accessing the spectrum compete for access to the spectrum. In order to alleviate this problem, it has been proposed to also allow access to open / unlicensed spectrum. When communicating on an open spectrum, no central scheduling service is employed that applies to all nodes accessing the spectrum; but each individual node is subject to certain regulations that impose restrictions on access to the spectrum. An example of such a spectrum access restriction is related to duty cycle (DC) restrictions, for example, in the case of a sliding window method (where the window size is, for example, one hour long), each individual node may not not transmit for more than, for example, 0.1% or 1% or 10% of the time.

[0004] In such a case where a DC restriction is imposed, the balance of the budget for the transmission time resource (TTR) associated with the DC restriction may be insufficient. Then, if additional data is queued for transmission, it may happen that the data transmission needs to be postponed until the balance of the budget has been restored. This increases the waiting time for data transmission. In certain use cases, such waiting time may be undesirable, for example, in view of time-sensitive data, etc. Summary of the invention

[0005] In view of spectrum access restrictions, advanced communication technologies are needed. In particular, advanced technologies are needed that overcome or mitigate at least some of the above-mentioned limitations and disadvantages.

[0006] The method of operating a first node includes transmitting on a communication link using transmit time resources from a resource budget associated with spectrum access restrictions imposed on a second node.

[0007] The computer program or computer program product or computer readable storage medium includes program code executable by at least one processor. Execution of the program code causes the at least one processor to perform a method of operating a first node, the method comprising transmitting on a communication link using transmission time resources from a resource budget associated with spectrum access restrictions imposed on a second node.

[0008] The first node includes control circuitry configured to transmit on the communication link using transmit time resources from a resource budget associated with spectrum access restrictions imposed on the second node.

[0009] A method includes a first node and a second node exchanging status signals indicating a balance of a resource budget associated with spectrum access restrictions imposed on the second node.

[0010] A computer program or a computer program product or a computer-readable storage medium includes a program code that can be executed by at least one processor. Execution of the program code causes the at least one processor to perform a method. The method includes: a first node and a second node exchanging a status signal, the status signal indicating a balance of a resource budget associated with a spectrum access restriction imposed on the second node.

[0011] The first node or the second node includes a control circuit configured to exchange status signals between the first node and the second node, the status signals indicating a balance of a resource budget associated with spectrum access restrictions imposed on the second node.

[0012] A method includes a first node and a second node exchanging signals indicating a partitioning of a resource budget associated with spectrum access restrictions imposed on the second node.

[0013] A computer program or a computer program product or a computer readable storage medium includes a program code that can be executed by at least one processor. Execution of the program code causes the at least one processor to perform a method. The method includes a first node and a second node exchanging signals indicating a partition of a resource budget associated with spectrum access restrictions imposed on the second node.

[0014] The first node or the second node includes a control circuit configured to exchange signals between the first node and the second node, the signals indicating a partitioning of a resource budget associated with spectrum access restrictions imposed on the second node.

[0015] It is to be understood that the features mentioned above and those yet to be explained below can be used not only in the respective combination specified but also in other combinations or alone, without departing from the scope of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 Schematically illustrates communication links between nodes according to various examples.

[0017] Figure 2 Nodes according to various examples are schematically illustrated.

[0018] Figure 3TTR and the associated DC-limited budget balance according to various examples are schematically illustrated.

[0019] Figure 4 is a flow chart of a method according to various examples.

[0020] Figure 5 is a flow chart of a method according to various examples.

[0021] Figure 6 is a signaling diagram of communication between an AP and a UE and reallocation of at least a portion of a resource budget according to various examples.

[0022] Figure 7 is a signaling diagram of communication between an AP and a UE and reallocation of at least a portion of a resource budget according to various examples.

[0023] Figure 8 is a signaling diagram of communication between an AP and a UE and reallocation of at least a portion of a resource budget according to various examples.

[0024] Fig. 9 is a signaling diagram of communication between an AP and a UE and reallocation of at least a portion of a resource budget according to various examples.

[0025] Fig.10 is a signaling diagram of communication between an AP and a UE and reallocation of at least a portion of a resource budget according to various examples.

[0026] Fig.11 is a signaling diagram of communication between an AP and a UE and reallocation of at least a portion of a resource budget according to various examples.

[0027] Fig.12 The balance of an updated resource budget according to various examples is schematically illustrated. DETAILED DESCRIPTION

[0028] Some examples of the present disclosure generally provide multiple circuits or other electrical devices. All references to circuits and other electrical devices and the functions they each provide are not intended to be limited to only the contents shown and described herein. Although specific labels can be assigned to the various circuits or other electrical devices disclosed, such labels are not intended to limit the operating range of circuits and other electrical devices. Such circuits and other electrical devices can be combined and / or separated from each other in any way based on the desired specific type of electrical implementation. It should be recognized that any circuit or other electrical device disclosed herein may include any number of microcontrollers, graphics processor units (GPUs), integrated circuits, storage devices (e.g., flash memory, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or other suitable variations thereof) and software that cooperates with each other to perform the operations disclosed herein. In addition, any one or more electrical devices may be configured to execute a program code that is embodied in a non-transitory computer-readable medium that is programmed to perform any number of functions disclosed.

[0029] Hereinafter, embodiments of the present invention will be described in more detail with reference to the accompanying drawings. It should be understood that the description of the following embodiments should not be considered as limiting. The scope of the present invention is not intended to be limited by the embodiments or drawings described below, which are exemplary only.

[0030] The drawings should be considered as schematic representations, and the elements shown in the drawings need not be shown to scale. Instead, the various elements are represented in a manner that is obvious to those skilled in the art in terms of their functions and general purposes. Any connection or coupling between the functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be achieved by indirect connections or couplings. Couplings between components may also be established by wireless connections. Functional blocks may be implemented by hardware, firmware, software, or a combination thereof.

[0031] In the following, techniques for facilitating communication between a first node and a second node in view of spectrum access restrictions are described. In general, spectrum access restrictions can be implemented based on TTR. Each node can have a budget for TTR determined based on the spectrum access restrictions. Then, when the node transmits using TTR, the balance of the budget is reduced. The balance must not fall below zero to avoid violating the spectrum access restrictions.

[0032] As a general rule, various kinds and types of spectrum access restrictions may be used in conjunction with the techniques described herein. For example, spectrum access restrictions may impose certain limits on the maximum continuous spectrum access time. Thus, for example, a given node may not be allowed to access the spectrum for longer than a certain duration without a break. Another example of a spectrum access restriction is a so-called DC restriction. For example, a typical DC restriction may specify a certain time portion per reference time interval that may be used by a node to transmit on the spectrum. For example, a typical duration of a reference time interval may be on the order of minutes or hours. For example, a typical time portion may be on the order of 0.1% to 10%.

[0033] Typically, each node is imposed with a corresponding spectrum access restriction. For example, a first spectrum access restriction may be imposed on a first node, and a second spectrum access restriction may be imposed on a second node. If the first node transmits a signal on the spectrum, the corresponding balance of the budget associated with the first spectrum access restriction is reduced, and the TTR from the budget is used. Over time, if the first node does not transmit, the balance may be restored.

[0034] A node to which spectrum access restrictions are imposed may refer to a scenario where a predetermined set of rules, etc., requires the node to communicate using a limited TTR budget. The budget may be initially allocated (pre-allocated) to the corresponding node.

[0035] For simplicity, in the following, reference is mainly made to implementing spectrum access restriction as DC restriction, but the technology described in the following is not limited thereto.

[0036] The examples described herein can be combined with communications over an open spectrum. Here, a central scheduling service may not be available. In some examples, each node attempting to access the spectrum may have to adopt a listen-before-talk (LBT) process. Here, channel sensing can be used to determine the average power on the spectrum; if the average power exceeds a threshold, the node attempting to access the spectrum can delay transmission for a backoff period. This is in contrast to a regulated spectrum, in which a central scheduling service is a central authority that actively allocates resources to the various participating nodes. As a general rule, the use of the LBT process is optional.

[0037] The various technologies described herein relate to a scenario where multiple nodes that access a spectrum form a network. In other words, multiple nodes can communicate with each other using predetermined rules. Multiple nodes can exchange data. For example, a network may include one or more access points (APs). A network may include one or more UEs. One or more APs may provide one or more UEs with access to one or more data networks (such as packet networks or even circuit-switched telecommunication networks).

[0038] For example, one or more communication links may be formed between nodes that access the spectrum. The communication link may include one or more frequency bands; carrier aggregation may be used. The communication link may implement one or more channels, such as a random access channel, a payload channel, and a control channel. The communication link may be characterized by one or more transmission attributes, such as transmission power, modulation scheme, coding scheme, coverage extension repetition level, data rate, etc. Different communication links may use the same or different protocols. It is generally not necessary for all communication links to operate according to the same protocol. For example, a first communication link may operate according to the third generation partnership project (3GPP) long term evolution (LTE) protocol, while a second communication link may operate according to the 3GPP new radio (NR) protocol. Other example protocols include: Bluetooth, Wi-Fi, etc. For example, the protocols of various communication links may differ in at least one of the carrier frequency, modulation scheme, and coding scheme. Device-to-device (D2D) communication (sometimes also referred to as sidelink communication) may be used. In addition, it is possible that one or more communication links are not associated with DC restrictions.

[0039] The various techniques described herein are based on the discovery that, in certain circumstances, one or more of the nodes accessing the spectrum may have an insufficient balance of the budget associated with the corresponding spectrum restriction. For example, there may be more data queued for transmission than the balance can accommodate: there is a risk that the budget is overdrawn. Such a situation may be particularly applicable to an AP. The reason for this is that an AP typically has to communicate with many UEs, so that the total amount of TTR required by the AP may be quite large. In one example, the AP may request the UE to send a large amount of downlink (DL) data to be received. Then, a so-called "greedy" situation may result: there may not be any penalties or restrictions configured in the DC restriction to avoid excessive DL traffic. This may cause spectrum congestion. The various examples described herein help to mitigate such insufficient balances associated with spectrum access restrictions. In addition, the various examples described herein avoid greedy behavior of the AP-UE communication system.

[0040] According to various examples, TTR from a budget associated with a spectrum access restriction (e.g., a DC restriction) imposed on a second node is partially or fully reallocated. Such a reallocation may be from the second node to the first node. In other words, according to various examples, it is possible to share TTR between the first node and the second node. For example, a corresponding protocol may be negotiated between the first node and the second node using corresponding control signaling. The first node may then send on the communication link using TTR from a resource budget associated with the spectrum access restriction imposed on the second node.

[0041] In this regard, a plurality of nodes having one or more communication links may be considered a system: a budgeted TTR associated with a spectrum access restriction imposed on one of the plurality of nodes may be used by the plurality of nodes.

[0042] For example, an AP with a first DC restriction may broadcast to one or more UEs that the AP may obtain at least one TTR from one or more resource budgets with a second DC restriction imposed on the one or more UEs. Thus, the AP may extend its own budget by at least a portion of the budget associated with the second DC restricted UE. Corresponding control signaling may be implemented between the AP and the one or more UEs.

[0043] As a general rule, a first node that uses TTRs from a resource budget associated with a DC restriction imposed on a second node may correspond to a first node that transmits on a communication link between the first node and the second node using these TTRs. For example, this may be a reciprocal communication link in which the radio parameters used to communicate from the first node to the second node are approximately equal to the radio parameters used to communicate from the second node to the first node. In another example, the first node uses TTRs from a resource budget associated with a DC restriction imposed on the second node on a communication link between the first node and a third node that is different from the second node.

[0044] In the examples described herein, management of resource budgets may be delegated between nodes. Management of resource budgets may be delegated specifically with reallocating TTRs. Management of resource budgets may include updating the balance of resource budgets. Here, the used TTRs may be counted.

[0045] In the examples described herein, it may be possible to apply non-proportional scaling when updating the balance of the resource budget. Thus, a penalty may be applied to the reallocated TTR.

[0046] Penalties may be specifically applied in scenarios when a resource budget is managed by more than a single node, for example, to avoid unintentional overdrafts of the budget. For example, penalties may be selectively applied depending on whether a single node manages the budget. For example, if only a single node manages the budget, then penalties may not be applied.

[0047] In some examples, a node may decrease or increase the TTR counting rate when updating the balance of a resource budget. A node may even completely delegate management of the resource budget and stop counting TTR. The node may later reactivate updating the balance.

[0048] The node may be instructed to stop transmitting using TTR from the reallocated resource budget to avoid overdrawing the budget.

[0049] Management of the reallocated budget may be facilitated by using a dedicated grant signal from one node to another of the TTR of the reallocated budget.

[0050] Management of the reallocated budget may be facilitated by a node monitoring another node's transmission of TTRs using the reallocated budget.

[0051] In the examples described herein, use of TTR can be limited, for example, to one or more selected communication links using one or more selected channels (e.g., random access, hybrid ARQ ack / nack transmissions, power control commands, etc.) and / or using one or more transmission attributes (e.g., coding scheme, coverage extension level, modulation scheme, etc.).

[0052] The reallocated TTR may be used on a communication link to another device that is different from the device to which the DC limit associated with the corresponding resource budget (from which the TTR was obtained) was imposed.

[0053] Figure 1 Schematically illustrated are aspects regarding a plurality of wireless communication links 111 - 116 formed between a plurality of nodes 101 - 104 .

[0054] exist Figure 1 In the example of FIG. 1 , nodes 101-104 form a network 100. There is an AP 101 and UEs 102-104. Since nodes 101-104 access an open spectrum, at least when communicating on the open spectrum, AP 101 does not provide a scheduling function to UEs 102-104. Figure 1 In the example of FIG. 1 , AP 101 provides access to packet network 109 via a backbone connection.

[0055] Figure 2 Node 400 is schematically shown. Figure 2 The node 400 shown in FIG. 4 can implement Figure 1 AP 101 or any one of UE 102-104.

[0056] Node 400 includes a processor 411, for example, a central processing unit or a graphics processing unit or a field programmable gate array or an application-specific integrated circuit. Node 400 also includes a memory 412. For example, the memory 412 may include a volatile part and a non-volatile part. For example, the memory 412 may include a random access memory and a flash memory, etc. The memory 412 may store program codes that may be loaded and executed by the processor 411. In this way, the processor 411 and the memory 412 may implement a control circuit. Node 400 also includes an interface 413. The interface 413 may be a wireless interface, and may include an analog front end and a digital front end. The interface 413 may include one or more antennas. Using the interface 413, it is possible to send and / or receive (transmit) on a wireless communication link.

[0057] When processor 411 executes program code stored in memory 412, processor 411 may perform one or more of the following functions: reallocating TTR; reallocating a budget associated with a DC restriction; sharing TTR from a single budget; sending using TTR from a budget associated with a DC restriction imposed on node 400 and / or using TTR from another budget associated with another DC restriction imposed on another node; exchanging status signals indicating the balance of the other budget; managing a budget and / or managing another budget; applying a scaling factor (e.g., defining a penalty) to update the balance of a budget, etc.

[0058] Figure 3 Schematically illustrates aspects of spectrum access for AP 101. Figure 3 Spectrum access by AP 101 is shown, but similar techniques may also be applied to spectrum access by any of UEs 102-104 or any other node communicating on a spectrum, such as an open spectrum.

[0059] Figure 3 The top portion of FIG. 1 shows transmission intervals 201-203 during which AP 101 accesses the spectrum. Figure 3 As shown, AP 101 does not have continuous access to the spectrum. This limitation in spectrum access is due to the DC limit imposed on AP 101.

[0060] Each time before accessing the spectrum, the AP 101 may need to perform the LBT process 250, for example, according to the access rules for the open spectrum. Performing the LBT process 250 is generally optional. The purpose of the LBT process 250 is to avoid conflicts between two nodes 101-104 trying to access the spectrum at the same time. For the transmission intervals 201-203, the corresponding LBT process 250 succeeds (otherwise the AP 101 will not send). For example, the corresponding spectrum power density can be kept below a predetermined threshold. Figure 32 shows a failed LBT process 250 between transmission intervals 201, 202. The failed LBT process 250 triggers a backoff period 251 after which a subsequent LBT process 250 is performed. The LBT process 250 is generally optional.

[0061] Figure 3 Also shown are aspects regarding a budget 700 associated with a DC limit. The AP 101 manages the budget 700. For example, this involves counting the usage of TTR during the transmission intervals 201-203 to update the balance 711 of the budget 700. This also includes monitoring that the balance 711 of the budget 700 does not reach zero or fall below zero.

[0062] exist Figure 3 In the example of , a pie chart is used to graphically illustrate the balance 711 of the budget 700. In the pie chart, the black portion is associated with the available, unused TTR - corresponding to the available balance 711; and the white portion is associated with the unavailable, already used TTR.

[0063] exist Figure 3 , four instances of a pie chart illustrating a budget 700 for four different points in time are shown. Initially, the balance 711 is high, i.e., there are many available TTRs. Then, for each transmission time interval 201-203, the balance 711 decreases, i.e., a certain portion 701 of the budget 700 is used to implement the corresponding transmission interval 201-203. The portion 701 is related to the number of used TTRs. This mapping of used and unused TTRs to the balance of the budget is an example implementation. There are various other available mappings, and the techniques described herein can be modified accordingly.

[0064] As a general rule, depending on the transmission attributes (eg, coding scheme, coverage extension repetition level, modulation scheme, frequency, forward error correction, and / or transmit power), the same amount of data may require more or less TTR.

[0065] like Figure 3 As shown, the balance 711 eventually drops below the threshold 705. Then, according to the reference embodiment, the AP 101 may not perform additional spectrum access for a certain period of time until the balance 711 is restored. In the following, techniques for overcoming or mitigating such transmission delays are described. Figure 4 and Figure 5 Example methods are described.

[0066] Figure 4 is a flow chart of a method according to various examples. Figure 2 Optional boxes are shown with dotted lines. Figure 4The method may be performed by a first node. The first node may be a sending node. For example, the first node may be configured as Figure 2 Node 400 in ; thus, Figure 4 The method can be Figure 2 The processor 411 and the memory 412 of the node 400 shown in the figure execute. Specifically, Figure 4 The method can be Figure 1 AP 101 of network 100 is shown performing.

[0067] The method starts at block 3001. In optional block 3001, a capability to partially or fully reallocate a resource budget associated with a DC constraint imposed on the second node from a second node to a first node is exchanged. The capability is exchanged between the first node and the second node.

[0068] Reallocating the resource budget may generally mean allowing one or more first nodes to transmit using TTR from the resource budget even if the resource budget is associated with a DC restriction imposed on the second node. If the resource budget is fully reallocated, the second node is no longer allowed to transmit using TTR from the resource budget.

[0069] Since the resource budget is associated with the DC restriction imposed on the second node, it is labeled as the second resource budget in the following.There may also be a first resource budget associated with the DC restriction imposed on the first node.

[0070] As a general rule, exchanging information and / or signals between a first node and a second node may include the first node sending one or more control signals to the second node, and / or the second node receiving one or more control signals from the first node, and / or the second node sending one or more control signals to the first node, and / or the first node receiving one or more control signals.

[0071] For example, the first node may send a capability request signal to the second node, and the second node may reply with a capability response signal indicating its ability to at least partially reallocate the second resource budget.

[0072] The reallocated one or more parameters may be identified in the capability request signal and / or the capability response signal.

[0073] Next, in optional block 3002, a partition of a second resource budget associated with a DC constraint imposed on the second node is exchanged between the first node and the second node. The partition may correspond to an a priori decomposition of the second resource budget into a first portion and a second portion, the first node may use a TTR from the first portion, and the second node may use a TTR from the second portion. When the second node delegates management of the first portion, the first node may then manage the first portion of the partition; while the second node manages the second portion of the partition. Here, each of the first node and the second node should be careful not to overdraw TTR from the corresponding portion of the partitioned second resource budget. For example, the first node may not send using a TTR from the first portion of the partition that overdraws the corresponding balance.

[0074] The advantage of this approach of using a split second resource budget is that status signals indicating the balance of the total budget do not have to be exchanged frequently - since each node manages its own portion of the split budget. On the other hand, the split may be somewhat (semi-)static, making flexible adjustments to the current needs of the TTR potentially less flexible.

[0075] In optional block 3003, the first node transmits using a TTR from the first resource budget. Thus, the first node can choose between using a TTR from the first resource budget or from the second resource budget. Thus, by at least partially reallocating the second resource budget from the second node to the first node, the first node can effectively expand its overall resource budget.

[0076] At optional block 3004, a status signal is exchanged between the first node and the second node, the status signal indicating the balance of the second resource budget. As explained in conjunction with block 3002, in the case of relying on a fixed split of the second resource budget, such exchange of status signals may not be required (although, for example, indicating the balance of the respective portions may be used in any case). On the other hand, in the case where the first node manages the entire second resource budget or in the case where the second node manages the entire second resource budget, the status signal may be useful to synchronize knowledge of the remaining balance of the second resource budget between the first node and the second node - thereby ensuring that the second resource budget is not overdrawn.

[0077] For example, in a scenario where the first node manages the second resource budget, the first node may send a status signal to the second node. The second node may then receive the status signal. The first node may repeatedly send the status signal according to a time schedule or upon request; thus, up-to-date information about the balance may be provided. In another example, the first node may send an event-driven status signal. For example, the status signal may indicate a transmission permission for an additional TTR. Thus, the transmission permission may be provided on demand, such as upon request. The transmission permission at least implicitly indicates that the balance is not too scarce to use an additional TTR.

[0078] For example, the transmission permission may indicate one or more channels (e.g., random access or side link, etc.) or transmission attributes, for which permission to use transmission type resources from the second resource budget is provided. For example, the transmission permission may indicate the amount of TTR. Through this technique, it can be ensured that the balance of the second resource budget is not overdrawn due to the use of too much TTR.

[0079] Alternatively or additionally, a more passive solution may also be adopted. Here, the first node managing the second resource budget may monitor the transmission of the second node using the additional TTR from the second resource budget. The first node may use the additional TTR to transmit until further notification - even if it has delegated management to the first node. Then, for example under certain conditions, the first node may again send a status signal indicating the balance of the resource budget. For example, once the balance of the second resource budget is insufficient, the first node will be able to send a status signal. The first node may then request the second node to suspend or stop or pause the use of the TTR from the second resource budget for transmission by means of the status signal. For example, the status signal may then indicate at least one of the suspension or backoff time periods of the transmission of the second node using the additional TTR from the second resource budget. In this way, the status signal may be marked as a stop signal.

[0080] As a general rule, in conjunction with such a technique in which the first node manages a second resource budget associated with a DC restriction imposed on the second node, the first node may send to the second node one or more transmission attributes for transmission by the second node using an additional TTR. By indicating the transmission attributes that are allowed or not allowed, it becomes possible to estimate the amount of TTR used by the second node to send data from the second resource budget. Specifically, as described above, the amount of TTR per data unit may vary according to one or more transmission attributes. This technique also applies in the case where the second node retains management of the second resource budget. Then, the second node may send to the first node one or more transmission attributes for transmission by the first node using the TTR from the second resource budget.

[0081] Above, it has been explained that exchanging a status signal indicating the balance of the second resource budget includes various situations in which the first node sends a status signal to the second node. This is usually associated with the first node managing the second resource budget on behalf of the second node. Other situations in which the second node does not delegate the management of the second resource budget to the first node can be imagined. Here, the second node may still be responsible for the management of the second resource budget. Specifically, in such a case, exchanging the status signal in box 3004 may include the first node receiving the status signal from the second node.

[0082] For example, the first node and the second node may have a synchronized timing of the communication of the status signal. The first node may then receive the status signal according to the timing. Thus, the first node may have up-to-date knowledge about the balance. The first node may take care not to overdraw the balance.

[0083] In another example, the first node may receive a transmission grant for a TTR from a second resource budget. This may be based on the second node managing the second resource budget. For example, the first node may initially send a request and then associate the transmission grant with the request. For example, the request may be sent after data arrives in a transmit buffer at the first node. For example, the request may be sent based on managing the first resource budget. For example, the first node identifies that there is more data to be sent queued in the transmit buffer than the available TTR in the first resource budget, and the first node may send the request.

[0084] Again, the transmission permission will be able to indicate one or more channels and / or one or more transmission attributes and / or the amount of TTR for which the second node is permitted to send to the first node using TTR. Alternatively or additionally, such information may also be included in the request.

[0085] The transmission permission may also indicate whether the transmission permission may be forwarded to a third node different from the second node. Thus, the transmission permission may indicate whether the first node is allowed to give or forward the TTR to the third node. The transmission permission may also indicate whether the TTR may be used for communication between the first node and the third node (or whether the TTR may only be used for communication between the first node and the second node).

[0086] Then, in any case, the first node may check whether the TTR is available at block 3005. In short, this may be based on the first node managing the corresponding portion of the split of the second resource budget (as explained above in conjunction with block 3002); or based on the first node managing the entire second resource budget (as explained above in conjunction with block 3004); or based on the first node receiving a status signal (e.g., a transmission permission) indicating the balance of the second resource budget from the second node managing the entire second resource budget (as explained above in conjunction with block 3004).

[0087] If it is determined in block 3005 that a TTR from the second resource budget is available, then in block 3006, the first node transmits on the communication link using the available TTR from the second resource budget.

[0088] As a general rule, the communication link may be between the second node and the first node. The communication link may also be between the first node and a third node.

[0089] As a more general rule, a communication link may be reciprocal or non-reciprocal. For example, a partial or full reallocation of TTR from the second node to the first node may be applicable, particularly in the case where the radio conditions under which the first node sends to the second node are comparable to the radio conditions under which the second node sends to the first node. This is based on the finding that in such a reciprocal communication link, under the assumption of reciprocity, it will be easy to evaluate the amount of TTR required for sending a data unit for a specific node that manages the resource budget. For example, the first node (and / or the second node) will be able to check the reciprocity of the communication link based on the transmission of one or more pilot signals. For example, the reception characteristics of the pilot signal sent from the first node to the second node can be compared with the reception characteristics of the pilot signal sent from the second node to the first node. Then, the reallocation of the second resource budget can be selectively activated based on reciprocity. In addition, since the radio propagation characteristics are generally dependent on the frequency, as an example, in the case where the wireless communication protocol operates in a time division duplex (TDD) mode, the node can consider the communication link to be reciprocal, which means that the same frequency range is used to transmit from the second node to the first node and from the first node to the second node. As another example, a node may consider a communication link to be non-reciprocal if the communication protocol operates in a frequency division duplex (FDD) manner, where the frequencies between two nodes in the two transmission directions are different.

[0090] Another option would be to use paired frequency bands for communication from the first node to the second node and vice versa.

[0091] Next, at optional block 3007, the balance of the first resource budget and / or the balance of the second resource budget is updated based on the TTR used for the transmission at block 3003 and / or for the transmission at block 3006. This may include counting the TTR used.

[0092] For example, if the first node (e.g., based on spectrum access rules) uses TTR from a first resource budget (associated with the first node itself - i.e., imposed on the first node), the first node may proportionally reduce the balance of TTR. For example, if the DC restriction imposed on the first node specifies that a TTR of 10 counts may be used in a reference time window of 1 minute, and at block 3003, the first node transmits using 3 TTRs from the first resource budget, the balance may be reduced by 3 increments (arbitrary units).

[0093] According to some examples, it will be possible to update the resource budget in the case of sending using the reallocated TTR. For example, a scaling factor may be applied. The scaling factor may be different from 1. For example, if the first node uses a TTR from the second resource budget (associated with the second node itself, i.e., applied to the second node), the nodes managing the second resource budget or the respective parts of the split of the second resource budget may reduce the balance of the second resource budget in a scaled manner. Specifically, when the first node uses a TTR from the second resource budget, the scaling may be applied to the balance of the second resource budget. For example, if the DC restriction imposed on the second node specifies that a TTR of 10 counts may be used in a reference time window of 1 minute, and in box 3006, the first node uses 3 TTRs from the second resource budget for sending, then the balance may be reduced by increments other than 3 (scaling factor equal to 1), for example, by 1 or 2 (scaling factor less than 1), or even by 4 or 5 (scaling factor greater than 1), etc. (arbitrary units). This corresponds to a penalty for the balance in the case of reducing the balance in a scaled manner, taking into account the TTR actually used.

[0094] For example, the scaling factor may depend on at least one of: a count of nodes using TTR from the second resource budget, e.g., how many nodes benefit from reallocating TTR from the second resource budget; a distance between the first node and the second node; and mobility of at least one of the first node and the second node.

[0095] Such scaling techniques are based on the finding that if the redistribution of TTR among nodes is widely adopted, equality of spectrum access will be experienced. For example, consider a scenario where a first node and a second node are arranged far apart: here, different spatial regions will be occupied based on one and the same DC limit imposed on a single node. In conventional techniques, TTR from a resource budget associated with a DC limit imposed on a single node may result in spectrum occupancy in different spatial regions. Similar considerations also apply to high / low mobility of individual nodes. By using scaling, spectrum access equality can be supported.

[0096] Figure 5 is a flow chart of a method according to various examples. Figure 5 Optional boxes are shown with dotted lines. Figure 5 The method may be performed by a second node. The second node may be a sending node. For example, the second node may be configured as Figure 2 Node 400 in ; thus, Figure 5 The method can be Figure 2 The processor 411 and the memory 412 of the node 400 shown in the figure execute. Specifically, Figure 5 The method can be Figure 1 UE 102 of network 100 is shown performing.

[0097] Figure 5 Methods and Figure 4 methods are interrelated.

[0098] As a general rule, the second node may retain or delegate management of the second resource budget associated with the DC limit imposed on the second node.Depending on where management of the second resource budget occurs, the second node may send or receive a status signal indicating the balance of the second resource budget.

[0099] Block 3011 is associated with block 3001 and exchanges the ability to partially or fully reallocate a resource budget associated with a DC constraint imposed on the second node from the second node to the first node.

[0100] Block 3012 is interrelated with block 3002; here, a partition of the resource budget associated with the DC restriction imposed on the second node is communicated.

[0101] Block 3014 is interrelated with block 3004; here, signals indicative of resource budgets are exchanged.

[0102] Box 3015 corresponds to box 3005. The second node checks whether the balance of the resource budget of the DC limit imposed on the second node is high enough. If yes, the method starts at box 3016.

[0103] Block 3016 corresponds to block 3006. At block 3016, the second node transmits using a TTR from its own resource budget.

[0104] Box 3017 corresponds to box 3007. For example, there may be a situation where the second node delegates management of the second resource budget to the first node. Here, as part of box 3014, the second node may receive a status signal from the first node indicating the balance of the second resource budget. The status signal may be based on the first node managing the second resource budget. For example, the status signal may indicate a transmission grant, as explained in conjunction with box 3004 above. Then, in box 3016, the second node may send using the TTR based on the transmission grant. Since the first node manages the second resource budget, the second node does not need to perform box 3017 in this case.

[0105] In an alternative case, the second node may not delegate management of the second resource budget to the first node. Here, as part of block 3014, the second node may send a status signal to the first node indicating a balance. For example, the status signal may indicate a transmission grant so that the first node may transmit using a TTR from the second resource budget. In this case, the second node may update the balance of the second resource budget in block 3007 based on the TTR subject to the transmission grant sent at block 3014 and optionally also based on the TTR used in block 3016. With respect to the TTR reallocated to the first node in block 3014, it will be possible to apply scaling again when updating the balance of the second resource budget in block 3017.

[0106] As an alternative to or in addition to using a transmission grant, a more passive approach may be employed in which the second node monitors transmissions by the first node using TTR from the second resource budget. The second node may manage the second resource budget based on the monitoring. Here, the second node may send a status signal indicating a balance based on the monitoring. For example, once the balance of the second resource budget is insufficient, the second node will likely send a status signal. The second node may then request the first node to abort or stop or pause transmissions using TTR from the second resource budget by means of the status signal. For example, the status signal may then indicate at least one of a pause or backoff period for transmissions by the first node using TTR from the second resource budget. In this way, the status signal may be marked as a stop signal.

[0107] generally, Figure 5 The order of the boxes in the scenario may not be fixed. For example, in the case where the second node sends a transmission permission to the first node, the check of box 3015 may be performed before executing box 3014.

[0108] Figure 6 is a signaling diagram of communication between AP 101 and UE 102. Figure 6 Aspects of reallocation of TTR with respect to a DC-constrained budget 752 imposed on a UE 102 are shown.

[0109] At 901, AP 101 sends a capability request signal 101. UE 102 receives capability request signal 101. For example, AP 101 may send capability request signal 101 in response to detecting an insufficient balance of a DC-limited budget 751 imposed on AP 101. At 902, UE 102 may respond with capability response signal 102. The capability response signal indicates a capability of UE 102 to reallocate its resource budget 752 at least partially to AP 101.

[0110] Despite Figure 6 In the example, the AP 101 sends the capability request signal 101 , but the UE 102 may also send the capability request signal 101 .

[0111] Next, at 903, AP 101 indicates the start of reallocation by sending a corresponding control signal 803. Figure 6 The optional confirmation signal is not shown. The UE 102 may also be given the possibility to reject the request of the AP 101.

[0112] Then, at 904, the reallocation of the resource budget 752 is implemented. At 904, the AP 101 indicates to stop the reallocation by sending a corresponding control signal 804.

[0113] There are a variety of options available to achieve partial or full reallocation of resource budget 752 from UE 102 to AP 101. Figures 7 to 11 Explain some examples.

[0114] Figure 7 is a signaling diagram for communication between AP 101 and UE 102. Figure 7 In the example of , UE 102 delegates the management of its resource budget 752 to AP 101. AP 101 manages the resource budget 752 of the DC limit imposed on UE 102. For example, this delegation can be negotiated or commanded as part of the control signaling in 901-903 (see Figure 6 ).

[0115] Since AP 101 manages resource budget 752, AP 101 does not need to request permission to transmit using a TTR from resource budget 752. Therefore, at 911, AP 101 transmits data 811 using a TTR from resource budget 752 associated with the DC restriction imposed on UE 102.

[0116] For example, the communication at 911 can be on communication link 111 or on communication link 112, i.e., it can be on communication link 111 between AP 101 and UE 102 that at least partially reallocates TTR from its budget to AP 101, or it can be on communication link 112 between AP 101 that obtains reallocation of TTR from resource budget 752 and a third-party UE 103.

[0117] At 912, UE 102 transmits a request signal 821 which is received by AP 101. At 913, AP 101 responds by transmitting a transmission permission signal 822. Transmission permission signal 822 is used to cause UE 100 to transmit data 812 at 914 using a TTR from resource budget 752. Based on transmission permission signal 122, AP 101 updates the balance of budget 752. Therefore, transmission permission signal 822 corresponds to a status signal indicating the balance of resource budget 752.

[0118] For example, the transmission permission signal 822 may indicate one or more channels or one or more transmission attributes for which transmission using TTR is permitted to the UE 102. Thus, the AP 101 may estimate the amount of TTR used by the UE 102. The transmission permission signal 822 may also explicitly indicate an upper threshold amount of TTR for the UE 102 to use.

[0119] At 915 , the AP 101 may optionally send the data 811 using a TTR from its own resource budget 751 .

[0120] Figure 8 is a signaling diagram for communication between AP 101 and UE 102. Figure 8 In the example of , UE 102 again delegates the management of its resource budget 752 to AP 101. AP 101 manages the resource budget 752 of the DC limit imposed on UE 102. For example, this delegation can be negotiated or commanded as part of the control signaling in 901-903 (see Figure 6 ).

[0121] Figure 8 The scenario generally corresponds to Figure 7 921 corresponds to 911, and 924 corresponds to 915.

[0122] At 921 , AP 101 sends data 811 using a TTR from the resource budget 752 associated with the DC restriction imposed on UE 102 .

[0123] However, in Figure 8In the scenario of , the UE 102 does not preemptively request permission to transmit using a TTR from the resource budget 752. Instead, the UE 102 transmits data 812 on the communication link 111 between the UE 102 and the AP 101 at 922. The AP 101 monitors such transmissions by the UE 102 using the TTR from the resource budget 752. Based on receiving the data 812 at 922, the AP 101 may update the balance of the resource budget 752 accordingly. For example, if the AP 101 then wants to prevent the UE 102 from continuing to transmit using the TTR from the resource budget 752, the AP 101 may send a corresponding stop signal 822 indicating at least one of a pause or backoff period for the UE 102 to transmit using the TTR from the resource budget 752, 923. The stop signal may indicate a low balance of the resource budget 752.

[0124] At 924 , the AP 101 may optionally send the data 811 using a TTR from its own resource budget 751 .

[0125] Although in Figure 8 In the scenario of FIG. 1 , AP 101 monitors the transmission of UE 101 on communication link 111, but AP 101 may also monitor the transmission of UE 102 on another communication link 116, 113 (see FIG. 1 ). Fig. 9 :932). Fig. 9 , 931 corresponds to 921, 933 corresponds to 923, and 934 corresponds to 924.

[0126] Fig.10 is a signaling diagram for communication between AP 101 and UE 102. Fig.10 In the example of , UE 102 does not delegate the management of its resource budget 752 to AP 101. UE 102 manages resource budget 752 of the DC constraints imposed on UE 102. AP 101 does not manage resource budget 751.

[0127] exist Fig.10 In the example of , at 941, AP 101 sends a request signal 841 to UE 102. At 942, based on the request signal 841, UE 102 sends a transmission permission signal 842. The request signal 841 is sent based on UE 102 managing resource budget 752. For example, if the balance of resource budget 752 is low, UE 102 may not transmit permission signal 821. Fig.10In the scenario of , there is sufficient available TTR in resource budget 752, and UE 102 sends a transmission grant signal 821, which gives AP 101 permission to send data 811 at 943 using the TTR from resource budget 752. UE 102 updates the balance of resource budget 752 accordingly.

[0128] For example, the transmission permission 821 may indicate one or more channels and / or one or more transmission attributes and / or the amount of TTR for which the AP 101 is permitted to transmit using the TTR. This may help estimate the amount of TTR required at the UE 102.

[0129] like Fig.10 As shown, UE 102 can use the TTR from resource budget 752 to send data 812 at 944 without seeking prior approval from AP 101. This is because Fig.10 In the scenario, UE 102 is always responsible for the management of resource budget 752.

[0130] At 945 , AP 101 may optionally send data 811 using a TTR from its own resource budget 751 , which corresponds to the actions / signaling at 934 , 924 , and 915 .

[0131] Although in Fig.10 In the scenario, AP 101 uses the transmission permission signal 821 to send data 811 at 943, but in some scenarios, AP 101 may even forward the transmission permission signal to, for example, UE 103 ( Fig.10 For example, the transmission permission signal 821 may indicate whether the transmission permission signal 821 may be forwarded to another node other than the AP 101. The transmission permission signal 821 may also indicate whether the AP 101 is allowed to transmit with another node such as the UE 103 using the TTR from the resource budget 752.

[0132] Although in Fig.10 In the scenario of , AP 101 preemptively requests permission to use TTR from resource budget 752, but it is also possible to implement such as combining Figure 8 and Fig. 9 Here, UE 102 may continue to be responsible for the management of resource budget 752, but may allow AP 101 to actively transmit using the TTR from resource budget 752, e.g., until UE 102 sends a status signal indicating at least one of: a pause or backoff period for AP 101 to transmit using the TTR from resource budget 752.

[0133] Fig.11 is a signaling diagram for communication between AP 101 and UE 102. Fig.11 In the example of , UE 102 sends a split signal 851 to AP 101 at 951. Split signal 851 indicates a split 759 of a resource budget 752 associated with a DC restriction imposed on UE 102.

[0134] Then, at 952, AP 101 may transmit on one of its communication links 111, 112 using the TTR from portion 761 of partition 759. AP 101 manages portion 761 of partition 759, while UE 102 manages portion 762 of partition 759. While AP 101 is not allowed to use the TTR from portion 762 managed by UE 102, vice versa, UE 102 is not allowed to use the TTR from portion 761 managed by AP 101. UE 102 transmits data 812 at 953 using the TTR from its portion 762. 954 corresponds to 945.

[0135] As can be appreciated from the above, there are various options available for managing at least a portion of the reallocated resource budget. For example, management can be at least partially retained on the node to which the corresponding associated DC limit is imposed. Management can also be at least partially delegated to the node to which the resource budget is at least partially reallocated. Regardless of the particular node that manages the resource budget, scaling can be applied when reallocating at least a portion of the resource budget. Fig.12 The corresponding scene is shown in FIG.

[0136] Fig.12 An aspect of updating a balance 771 of a resource budget 752 that is at least partially reallocated from a UE 102 to an AP 101 is shown. Fig.12 As shown, the balance 711 is reduced by a portion 701 of the total budget 752. Although the actual amount of TTR used only results in a small reduction in the value 703 of the balance 711, a scaling is also applied to the balance 711 when the AP 101 uses TTR from the resource budget 752. The scaling corresponds to a penalty applied to the balance 711 because the balance 711 is reduced by more than the amount that would be expected based on the TTR used. Scaling that provides incentives can also be applied when using reallocated TTR.

[0137] When managing a portion 761 of a partition 759 or when managing the entire resource budget 752 (see Figures 7 to 9 and Fig.11 ), AP 101 may apply such scaling.

[0138] When managing a portion 762 of a partition 759 or when managing the entire resource budget 752 (see Fig.10 and Fig.11 ), UE102 can apply scaling.

[0139] In summary, at least the following examples have been described above:

[0140] First example:

[0141] The TTR is implicitly shared when two nodes communicate over a reciprocal communication link or paired frequency bands: TTR is counted for any transmission, which means that even if the actual sending node is allowed not to count its TTR for transmissions, at least one node manages the balance of the TTR of the shared resource budget (see Figure 7 :914; Fig.10 :943, etc.).

[0142] This example may be based on capability signaling indicating that the node supports TTR sharing based on permission from the device communicating with the node, for example, a DC limited UE may be able to perform transmission without counting TTR.

[0143] When the AP allows this method, a dedicated transmission permission signal may be sent from the AP to the UE. The permission signal may indicate a specific signal type or channel that the UE is allowed to transmit using the TTR without counting the TTR (see Figure 7 , grant signal 822). An example may be to allow the UE to perform random access, or to send certain control signals or reference signals without counting its TTR.

[0144] In this example, a DC limited UE may be able to perform transmissions with a scaled TTR count based on permission from the nodes it is communicating with. A scaled TTR count means that only a small portion of the actual transmission time is taken into account. Since all TTRs still need to be considered throughout the system, it should be noted that scaling can be applied to two or more nodes in the system so that the sum of all scaling used is greater than or equal to 1. One reason for the sum of scaling to be greater than 1 is to avoid large amounts of resource sharing, so there may be overhead (penalty) applied. For example, if both the sending node and the receiving node of a communication link applied a scaling of 110%, the total would be greater than 1 and enable this feature when needed, but there is a certain penalty for using it.

[0145] Second example:

[0146] In this example, a transmission permission signal similar to that in the first example is assumed. In this example, the DC-limited node must be able to count the TTR when receiving based on dedicated signaling with the transmitting device. This means that the receiving node consumes TTR even if another node is actually transmitting on the communication link (see Figure 8 ). This can include signaling from the node managing the resource budget (the receiving node) to the sending node to communicate that all TTRs have been used and sending needs to stop (see Figure 8 , stop signal 821). A TTR status signal indicating the current balance may also be signaled prior to an insufficient balance situation (e.g., based on a request from the sending node or according to a schedule).

[0147] This example may include control signaling that requires a certain transmission attribute, such as a certain data rate. This helps enforce a certain TTR usage rate (e.g., TTR / hour) to meet a certain spectral efficiency target. For example, the transmission attribute may include a modulation scheme or a coding scheme, because, for example, for a given amount of data, higher modulation or less coding means less TTR.

[0148] Additionally, in this scenario, a scaling factor different from 1 may be used for the update.

[0149] Third example:

[0150] Here, explicit sharing on a reciprocal communication link is achieved. A DC-constrained node can explicitly give the TTR to another node (see Fig.10 , grant signal 842). These TTRs may be restricted in the sense that they are dedicated to the reciprocal communication link. In this scenario, based on optional capability signaling, the UE may communicate its TTRs to the AP. The signaling approach may be implemented in the following example steps: (i) the UE indicates its ability to partially or fully reallocate TTRs; (ii) the AP may send a query to the UE to obtain information about the UE's available TTRs, i.e., a query for a status signal indicating the current balance of the resource budget. The UE responds with a status signal. The AP may then send a TTR reallocation request to the UE. The request signal may include a certain amount of expected TTR resources to be reallocated. The UE responds with a TTR sharing acceptance to confirm the TTR reallocation. The UE alternatively responds with a rejection.

[0151] When reallocating resources, there may be a penalty factor used to reduce the effective available TTR at least partially upon reallocation. The reason for this penalty (reduction) when reallocating TTR from one node to another may be motivated by the fact that one node is effectively using more TTR than the normal DC limit and this may result in additional interference from that node. Another reason for the penalty is to avoid a lot of signaling (control signaling overhead) for resource reallocations, so a penalty is applied to each reallocation.

[0152] Fourth example:

[0153] Here, explicit sharing on a non-reciprocal communication link is achieved. A DC-constrained node must explicitly reallocate the TTR to another node where the TTR can be used for communication on a non-reciprocal communication link, or for communication with a third device or in paired frequency bands, i.e., two frequency bands for communication from a first node to a second node and from a second node to the first node. There may also be a penalty factor at each step when reallocating the TTR.

[0154] In the above description of the first to fourth examples, parameters such as scaling factors for combined management and penalty factors for redistributing TTR between nodes have been discussed. The values ​​of these parameters may be, for example, fixed values ​​defined in a standard or regulatory document for unlicensed spectrum use. Alternatively, a node may dynamically configure the values ​​of the parameters and broadcast them to other nodes.

[0155] Although the present invention has been shown and described with respect to certain preferred embodiments, equivalents and modifications will occur to those skilled in the art upon reading and understanding this specification. The present invention includes all such equivalents and modifications, and the present invention is limited only by the scope of the appended claims.

[0156] For illustration, various examples have been described above in which the resource budget associated with DC restriction is reallocated between a UE and an AP. Similar examples can be easily applied to other classes and types of nodes. For example, reallocation between two UEs or two APs would be possible.

[0157] For illustration, the various examples above have been described in connection with a first node managing a resource budget associated with spectrum access restrictions imposed on a second node. Similar examples may also be implemented for a scenario where the second node is always responsible for the management of the resource budget. For example, the second node will likely send a status signal to the first node indicating the balance of the resource budget. The second node may monitor the transmission of the first node using transmission time resources from the resource budget.

[0158] To further illustrate, it is even possible to implement a scenario where both the first node and the second node manage the resource budget at the same time (i.e., no splitting is applied). Here, the status signals exchanged between the first node and the second node may help align the balances. To avoid accidental overdrafts of the budget, a penalty scaling factor may be applied on each node managing the resource budget.

[0159] For further explanation, various examples employing the LBT process have been described. The LBT process is generally optional.

Claims

1. A method of operating a first node (101), the method comprising: - exchanging signals between said first node (101) and a second node (102) indicating an allocation of a resource budget (700, 752) associated with spectrum access restrictions imposed on said second node (102), wherein the first node (101) transmits on the communication link (111, 112) using transmission time resources from the corresponding portion (761) of the allocation; - reallocating at least partially the resource budget (700, 752) from the second node (102) to the first node (101); and - transmitting on said communication link (111, 112) using transmission time resources from said resource budget (700, 752), and Therein, the second node (102) delegates management of a portion of the resource budget (700, 752) to the first node (101).

2. The method according to claim 1, further comprising: - exchanging status signals (821, 822, 842) between the first node (101) and the second node (102), the status signals (821, 822, 842) indicating the balance (711) of the resource budget (700, 752).

3. The method according to claim 2, further comprising: - managing said resource budget (700, 752) at said first node (101).

4. The method according to claim 3, in, The exchange of the status signals comprises: - based on said management of said resource budget (700, 752), sending said status signal (822) indicating a balance (711) of said resource budget (700, 752) to said second node (102).

5. The method according to claim 4, in, The status signal indicates a transmission grant (822) for additional transmission time resources from the resource budget (700, 752).

6. The method according to claim 5, in, The transmission permission (822) indicates at least one of one or more channels, one or more transmission attributes, or the amount of the additional transmission time resources, for which transmission using the additional transmission time resources is permitted.

7. The method according to claim 3 or 4, in, The management of the resource budget (700, 752) includes: - monitoring transmissions by said second node (102) using additional transmission time resources from said resource budget (700, 752).

8. The method according to claim 7, in, The status signal (821) indicates at least one of a suspension or a backoff period of transmission by the second node (102) using the additional transmission time resource.

9. The method according to claim 3 or 4, further comprising: - based on the management, sending to the second node (102) transmission properties of transmissions by the second node (102) using additional transmission time resources from the resource budget (700, 752).

10. The method according to claim 1, further comprising: - managing said respective portion (761) of said allocation at said first node (101).

11. The method according to claim 1, further comprising: - exchanging signals (801, 802) between the first node (101) and the second node (102) indicating the ability to reallocate the resource budget (700, 752) from the second node (102) to the first node (101).

12. The method according to claim 1, further comprising: - When using said transmission time resources from said resource budget (700, 752), applying a scaling to the balance (711) of said resource budget (700, 752).

13. The method according to claim 12, in, The scaling depends on at least one of: a count of nodes using transmission time resources from the resource budget (700, 752); a distance between the first node (101) and the second node (102); and a mobility of at least one of the first node (101) and the second node (102).

14. The method according to claim 12 or 13, in, The scaling is associated with a penalty on the balance (711).

15. The method according to claim 1, in, The communication link (112) is between the first node (101) and the second node (102), or The communication link (111) is between the first node (101) and a third node, and the third node is different from the first node (101) and the second node (102).

16. The method according to claim 1, further comprising: - using other transmission time resources from another resource budget (700, 751) associated with another spectrum access restriction imposed on the first node (101) for transmitting on the communication link (111, 112).

17. A first node comprising a control circuit, the control circuit being configured to: - exchanging signals between said first node (101) and a second node (102) indicating an allocation of a resource budget (700, 752) associated with spectrum access restrictions imposed on said second node (102), in, The first node (101) transmits on the communication link (111, 112) using transmission time resources from the corresponding portion (761) of the allocation; - reallocating at least partially the resource budget (700, 752) from the second node (102) to the first node (101); and - transmitting on said communication link (111, 112) using transmission time resources from said resource budget (700, 752), and Therein, the second node (102) delegates management of a portion of the resource budget (700, 752) to the first node (101).

Images