Patent Description:
For example, one parameter in providing good performance and capacity for a given communications protocol in a communications network is resource scheduling.

Resource handling is commonly handled by the scheduler located in the radio access network node on the network side. The scheduler is configured to apply certain principles to divide radio resources (bandwidth, time slots, etc.) between terminal devices in a cell served by the radio access network node. The scheduler might further be configured to apply multi-cell scheduling policies to balance and mitigate interference and load variations over larger areas than a single cell and in situation where terminal devices not only in its own cell benefit from a jointly optimized resource dispatching approach.

One scheduling principle is Round Robin where the served terminal devices are scheduled according a given queue order, with the constraint of scheduling equal time and resources for each individual terminal device in the queue. Other scheduling mechanisms might consider weight factors and/or different priority levels as assigned to the individual terminal devices as well as the amount of data in transmit buffers and/or radio conditions for each individual terminal device when allocating the resources among the terminal devices.

Despite this, there are few means for an individual terminal device to impact to what extent the scheduler assigns resources to it.

<CIT> discloses a resource allocation method, a resource contention method, and a related apparatus. The disclosure teaches sending, by a first terminal, declaration information used to indicate an available resource; receiving, by the first terminal, resource request information sent by at least one second terminal according to the declaration information; and sending, by the first terminal, response information, where the response information includes an identification of at least one third terminal, so as to instruct the at least one third terminal to use the available resource, and the at least one third terminal is selected from the at least one second terminal.

<CIT> discloses a device comprising a first and a second communication band and a control module. According to the disclosure, the control module is configured to request communication resources in the second band from another device using a first type of request, allocate said resources in the second band for communication upon receipt of a resource allocation confirmation from said another device, and to communicate using at least a part of the allocated resources in the second band.

Hence, there is still a need for an improved scheduling of terminal devices in a communications network.

An object of embodiments herein is to provide mechanisms enabling efficient scheduling of terminal devices in a communications network.

According to a first aspect there is presented a method for requesting radio resources from a second terminal device. The method is performed by a first terminal device. The method comprises identifying an increasing need for use of radio resources. The method comprises transmitting, via a sidelink to the second terminal device, a request for using radio resources allocated to the second terminal device. The method comprises receiving, via the sidelink, a response from the second terminal device. The response pertains to whether the second terminal device has granted the first terminal device to use at least some of the requested radio resources or not. The method comprises providing, towards a network node serving the first terminal device, a notification of that the first terminal device has requested the radio resources from the second terminal device and of that the second terminal device has granted the first terminal device to use at least some of the requested radio resources. The method comprises receiving, from the network node, a decision pertaining to whether the network node has accepted the at least some of the requested radio resources to be granted to the first terminal device or not. The method comprises consuming, the at least some of the requested radio resources according to the decision.

According to a second aspect there is presented a first terminal device for requesting radio resources from a second terminal device. The first terminal device comprises processing circuitry. The processing circuitry is configured to cause the first terminal device to identify an increasing need for use of radio resources. The processing circuitry is configured to cause the first terminal device to transmit, via a sidelink to the second terminal device, a request for using radio resources allocated to the second terminal device. The processing circuitry is configured to cause the first terminal device to receive, via the sidelink, a response from the second terminal device. The response pertains to whether the second terminal device has granted the first terminal device to use at least some of the requested radio resources or not. The processing circuitry is configured to cause the first terminal device to provide, towards a network node serving the first terminal device, a notification of that the first terminal device has requested the radio resources from the second terminal device and/or of that the second terminal device has granted the first terminal device to use at least some of the requested radio resources. The processing circuitry is configured to cause the first terminal device to receive, from the network node, a decision pertaining to whether the network node has accepted the at least some of the requested radio resources to be granted to the first terminal device or not. The processing circuitry is configured to cause the first terminal device to consume, the at least some of the requested radio resources according to the decision.

According to a third aspect there is presented a method for granting radio resources to a first terminal device. The method is performed by a second terminal device. The method comprises receiving, via a sidelink to the first terminal device, a request for the first terminal device to use radio resources allocated to the second terminal device. The method comprises transmitting, via the sidelink, a response to the first terminal device. The response pertains to whether the second terminal device has granted the first terminal device to use at least some of the requested radio resources or not. The method comprises providing, towards a network node serving the second terminal device, a notification of that the first terminal device has requested the radio resources from the second terminal device and of that the second terminal device has granted the first terminal device to use at least some of the requested radio resources. The method comprises receiving, from the network node, a decision pertaining to whether the network node has accepted the at least some of the requested radio resources to be granted to the first terminal device or not. The method comprises refraining from consuming the at least some of the requested radio resources according to the decision.

According to a fourth aspect there is presented a second terminal device for granting radio resources to a first terminal device. The second terminal device comprises processing circuitry. The processing circuitry is configured to cause the second terminal device to receive, via a sidelink to the first terminal device, a request for the first terminal device to use radio resources allocated to the second terminal device.

The processing circuitry is configured to cause the second terminal device to transmit, via the sidelink, a response to the first terminal device. The response pertains to whether the second terminal device has granted the first terminal device to use at least some of the requested radio resources or not. The processing circuitry is configured to cause the second terminal device to provide, towards a network node serving the second terminal device, a notification of that the first terminal device has requested the radio resources from the second terminal device and of that the second terminal device has granted the first terminal device to use at least some of the requested radio resources. The processing circuitry is configured to cause the second terminal device to receive, from the network node, a decision pertaining to whether the network node has accepted the at least some of the requested radio resources to be granted to the first terminal device or not. The processing circuitry is configured to cause the second terminal device to refrain from consuming the at least some of the requested radio resources according to the decision.

According to a fifth aspect there is presented a method for handling radio resources between a first terminal device and a second terminal device. The method is performed by a network node. The method comprises obtaining, from a least one of the first terminal device served by the network node and the second terminal device served by the network node, a notification of that the first terminal device has transmitted a request for radio resources from the second terminal device where the radio resources have been allocated to the second terminal device, and of that the second terminal device has granted the first terminal device to use at least some of the requested radio resources. The method comprises transmitting, to at least one of the first terminal device and the second terminal device, a decision pertaining to whether the network node has accepted the at least some of the requested radio resources to be granted the first terminal device or not.

According to a sixth aspect there is presented a network node for handling radio resources between a first terminal and a second terminal device. The network node comprises processing circuitry. The processing circuitry is configured to cause the network node to obtain, from a least one of the first terminal device served by the network node and the second terminal device served by the network node, a notification of that the first terminal device has transmitted a request for radio resources from the second terminal device where the radio resources have been allocated to the second terminal device, and of that the second terminal device has granted the first terminal device to use at least some of the requested radio resources. The processing circuitry is configured to cause the network node to transmit, to at least one of the first terminal device and the second terminal device, a decision pertaining to whether
the network node has accepted the at least some of the requested radio resources to be granted the first terminal device or not.

Advantageously these methods, these first terminal devices, these second terminal devices, and these network nodes enable efficient scheduling of terminal devices in a communications network.

Advantageously these methods, these first terminal devices, these second terminal devices, and these network nodes product enable cell capacity, as given by the radio resources, to be traded between different terminal devices in a communications network.

In turn, this enables efficient utilization of available radio resource in the communications network.

In turn, this enables a terminal device to obtain more radio resources than given by the scheduling policy followed by the network node.

Advantageously these methods, these first terminal devices, these second terminal devices, and these network nodes enable the scheduling of radio resources to a terminal device to be adapter faster than if the scheduling were to be updated by means of a quality of service (QoS) policy update and/or change of subscription policy.

As disclosed above, there is a need for an improved scheduling of terminal devices in a communications network.

In more detail, there are currently no means for terminal devices to initiate trade, or redistribution, of their already scheduled radio resources. In a scenario where a terminal device has a need for extra radio resource within certain hours, etc., and another terminal device in the same cell has scheduled radio resources to spare for the same certain hours, there is currently no means for the radio resources to be traded, or redistributed, among these two terminal devices (optionally exchanging some sort of payment/remuneration).

Although QoS schemes seemingly are designed for such scenarios and thus how this matter should be addressed, i.e. where there are QoS models that assign different scheduling weights and priorities to different terminal devices depending on their current buffer status and radio environment, given a certain subscription, scheduling in the above scenario is not easily executed.

<FIG> is a schematic diagram illustrating a communications network 100a where embodiments presented herein can be applied. The communications networks 100a, could be a third generation (<NUM>) telecommunications network, a fourth generation (<NUM>) telecommunications network, or a fifth (<NUM>) telecommunications network, or any combination thereof, and support any 3GPP telecommunications standard, where applicable.

The communications network 100a comprises a radio access network <NUM>, a core network <NUM>, and a service network <NUM>, which are interconnected with each other. In turn, the radio access network <NUM> comprises a radio access network node <NUM> configured to provides network access to terminal devices 200a, 200b within the cell served by the radio access network node <NUM>, thus enabling the terminal device 200a, 200b to communicate with over a wireless link 150a, 150b. The terminal devices 200a, 200b are thereby enabled to, via the radio access network node <NUM>, access services of, and exchange data with, the service network <NUM>.

Operation of the radio access network node <NUM> is controlled by a network node <NUM>. The network node <NUM> could be part of, integrated with, collocated with, or physically separated from, the radio access network node <NUM>. The terminal devices 200a, 200b are further configured to communicate directly with each other over a wireless sidelink <NUM>. As will be further disclosed below, the wireless sidelink <NUM> is facilitated by a proximity-based services (ProSe) as provided by a ProSe server <NUM>.

Examples of radio access network nodes <NUM> are radio base stations, base transceiver stations, Node Bs (NBs), evolved Node Bs (eNBs), gNBs, access points, and access nodes, and backhaul nodes. Examples of terminal devices 200a, 200b are wireless devices, mobile stations, mobile phones, handsets, wireless local loop phones, user equipment (UE), smartphones, laptop computers, tablet computers, network equipped sensors, network equipped vehicles, machine type communication (MTC) devices, and so-called Internet of Things (IoT) devices. As the skilled person the communications network 100a might comprise a plurality of radio access network nodes <NUM> providing network access to a plurality of terminal devices 200a, 200b.

Hereinafter, terminal device 200a is denoted a first terminal device and terminal device 200b is denoted a second terminal device. However, this notation is for simplifying the description and does not necessarily impose a hierarchical relation between these terminal devices 200a, 200b.

<FIG> is a schematic diagram illustrating a communications network 100b showing the communications interfaces between the entities of the communications network 100a of <FIG>. The first terminal device 200a and the second terminal device 200b communicate with each other over communication interface PC5, the first terminal device 200a and the second terminal device 200b communicate with the radio access network (including the radio access network node <NUM> and possibly the network node <NUM>) over communication interface Uu, and the first terminal device 200a and the second terminal device 200b communicate with the ProSe server <NUM> over communication interface PC3. That is, the sidelink <NUM> is established over the PC5 interface, and the wireless links 150a, 150b are established over the Uu interface. For 3GPP Release <NUM> and onwards, the PC5 interface is a one-to-many communication interface, i.e. it is specified for group communication. From a higher protocol layer perspective (e.g., higher layer than protocol layer <NUM>; the physical layer), this is reflected in the assignment of destination identities (IDs), which according to the ProSe functionality are always group IDs. The Internet Protocol (IP) address of the ProSe server <NUM> might be preconfigured (hard-coded) in the terminal device 200a, 200b. Alternatively, the terminal device 200a, 200b identify the IP address of the ProSe server <NUM> via a domain name server (DNS) look-up. To contact the ProSe server <NUM> the terminal device 200a, 200b have to establish a radio resource control (RRC) connection with the network node over the Uu interface. The radio access network (including the radio access network node <NUM> and possibly the network node <NUM>) communicates with the core network <NUM> (possibly including the network node <NUM>) over communication interface S1, and the core network <NUM> (possibly including the network node <NUM>) communicates with the ProSe server <NUM> over communication interface PC4. As the skilled person understands, these are just examples of communication interfaces and the entities of <FIG> might be configured to communicate with each other using other communication interfaces, depending on the actual implementation of the communications network 100a, 100b, for example with regards to which telecommunications standard is to be supported (e.g., Long Term Evolution (LTE), New Radio (NR), etc.).

Among a group of terminal devices 200a, 200b served by the network node <NUM>, although the network node <NUM> does not consider the need of the individual terminal devices 200a, 200b other than fulfilling a configured scheduling policy, there might be a need for some of the served terminal devices 200a, 200b that requires the terminal device to use more than its scheduled radio resources.

To make this feasible among the group of terminal devices 200a, 200b, it is according to the present disclosure proposed that at least two terminal devices 200a, 200b perform a negotiation of radio resources over a sidelink <NUM>.

The communication over the sidelink <NUM> is an example of device to device (D2D) communication. D2D communication can be used to support ProSe. Typical applications range from public safety, traffic control/safety and commercial services like proximity based social networking, gaming, and advertisements for by-passers. The network node <NUM> indicates support of sidelink communication with the presence of system information block <NUM> (SIB18).

ProSe can be provided when terminal devices supporting such services are within direct communication capabilities range of each other. Examples of ProSe services are ProSe Direct Discovery (according to which terminal devices 200a, 200b in proximity of each other are identified; for two terminal devices 200a, 200b within cellular coverage it may also be used for other commercial purposes), and ProSe Direct Communication between two terminal devices. Radio resources from cellular traffic are reserved and used for this type of communication or enables communication in areas without cellular coverage.

In this context the sidelink <NUM> is used for ProSe Direct Discovery and Prose Direct communication between terminal devices 200a, 200b and the sidelink <NUM> corresponds to the communication between two ProSe enabled terminal devices 200a, 200b. The sidelink communication describes the channel structure consisting of Logical, Transport and physical channels over the air interface to realize a ProSe application (see, interface PC5 in <FIG>).

The embodiments disclosed herein relate to mechanisms for handling radio resources between a first terminal device 200a and a second terminal device 200b. In order to obtain such mechanisms there is provided a first terminal device 200a, a method performed by the first terminal device 200a, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the first terminal device 200a, causes the first terminal device 200a to perform the method. In order to obtain such mechanisms there is further provided a second terminal device 200b, a method performed by the second terminal device 200b, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the second terminal device 200b, causes the second terminal device 200b to perform the method. In order to obtain such mechanisms there is further provided a network node <NUM>, a method performed by the network node <NUM>, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the network node <NUM>, causes the network node <NUM> to perform the method.

Reference is now made to <FIG> illustrating a method for requesting radio resources from a second terminal device 200b as performed by the first terminal device 200a according to an embodiment.

S102: The first terminal device 200a identifies an increasing need for use of radio resources.

In this respect, although a terminal device, such as the first terminal device 200a, itself might identify an increasing need for use of radio resources, the actual allocation, or scheduling, of radio resources for each terminal device 200a, 200b is handled by the scheduler of the network node <NUM> serving the terminal devices 200a, 200b. Examples of causes for the increasing need for use of radio resources will be given below. The first terminal device 200a then requests extra radio resource from a peer terminal device, exemplified by the second terminal device 200b.

S110: The first terminal device 200a transmits, via a sidelink <NUM> to the second terminal device 200b, a request for using radio resources allocated to the second terminal device 200b.

It is assumed that the second terminal device 200b responds to the first terminal device 200a.

S112: The first terminal device 200a receives, via the sidelink <NUM>, a response from the second terminal device 200b, the response pertaining to whether the second terminal device 200b has granted the first terminal device 200a to use at least some of the requested radio resources or not.

A notification is then provided towards the network node <NUM> serving the first terminal device 200a.

S116: The first terminal device 200a provides, towards a network node <NUM> serving the first terminal device 200a, a notification of that the first terminal device 200a has requested the radio resources from the second terminal device 200b and/or of that the second terminal device 200b has granted the first terminal device 200a to use at least some of the requested radio resources.

Different examples of how the notification might be provided towards the network node <NUM> will be provided below.

Embodiments relating to further details of requesting radio resources from a second terminal device 200b as performed by the first terminal device 200a will now be disclosed.

In some examples the sidelink <NUM> is established over interface PC5.

In some examples the radio resources are to be consumed by the first terminal device 200a for enabling cellular communication with the network node <NUM> serving the first terminal device 200a.

There could be different causes for the increasing need for use of radio resources. In some examples the increasing need is caused by a comparatively large amount of uplink data to be transmitted by the first terminal device 200a towards the network node <NUM>. In some examples the increasing need is caused by a comparatively large amount of downlink data to be transmitted to the first terminal device 200a from the network node <NUM>. In some examples the increasing need is caused by a need for a comparatively high level of quality of service required by a certain network service which the first terminal device 200a is to use. There could be different network services where the large amount of data (uplink or downlink) and high level of quality of service is needed. One example of such a network service is mission critical (MC) services or other types of emergency, rescue, or investigation, services.

In some examples the increasing need for use of radio resources pertains to a certain amount of radio resources and/or a certain amount of time when the radio resources are needed for consumption by the first terminal device 200a. For example, the need could be specified in terms of a certain amount of physical resource blocks, symbols, bits, bandwidth, etc..

In some aspects the sidelink <NUM> is not already established when the first terminal device 200a identifies the increasing need for use of radio resources. The sidelink <NUM> then needs to be established before the request in S110 is transmitted. According to an embodiment the first terminal device 200a is therefore configured to perform (optional) step S104:
S104: The first terminal device 200a transmits, to the network node <NUM>, a request to establish the sidelink <NUM>.

The first terminal device 200a would then receive a response from the network node <NUM> to establish the sidelink <NUM>.

In some aspects the request to establish the sidelink <NUM> includes information of the network service for which the radio resource are to be used by the terminal device <NUM>. Particularly, according to an embodiment, the request in S104 to establish the sidelink <NUM> comprises an indication of which network service the increasing need for use of radio resources results from.

In some aspects the first terminal device 200a stores information of its previous sessions (e.g. considered sufficiently successful) so that reliable and fair second terminal devices 200b could be addressed first when seeking to establish the sidelink <NUM>.

The first terminal device 200a could then in its request to the serving network node <NUM> for a sidelink transmission include a request for the network node <NUM> to contact a list of preferred second terminal devices 200b for establishment of the sidelink <NUM>. In particular, according to an embodiment the first terminal device 200a is configured to perform (optional) step S106:
S106: The first terminal device 200a receives, from the network node <NUM>, an identifier of a set of candidate terminal devices to which the sidelink <NUM> can be established. The second terminal device 200b is then selected from the set of candidate terminal devices.

The identifier of the set of candidate terminal devices might be stored for future use, for example when a need for further radio resources is identified. In particular, according to an embodiment the first terminal device 200a is configured to perform (optional) step S108:
S108: The first terminal device 200a stores the identifier of the set of candidate terminal devices.

In other aspects the request includes a list of non-preferred second terminal devices 200b with which establishment of the sidelink is to, if possible, be avoided. The first terminal device 200a might store also this list such that when a need for further radio resources is identified it is avoided to establish a sidelink <NUM> to any of these non-preferred second terminal devices 200b.

In some aspects the response in S112 from the second terminal device 200b includes information of the amount of offered radio resources and/or of the time duration during which the offered radio resources might be used by the first terminal device 200a. In particular, according to an embodiment, the response from the second terminal device 200b comprises information of amount of the radio resources granted to the first terminal device 200a and/or for how long time the radio resources are granted to the first terminal device 200a.

The notification in S116 to the network node <NUM> might then include information of the amount of offered radio resources and/or of the time duration during which the offered radio resources might be used by the first terminal device 200a. In particular, according to an embodiment, the notification in S116 provided towards the network node <NUM> comprises this information.

In some aspects the offer comprises details of payment/remuneration between the first terminal device 200a and the second terminal device 200b. The terminal devices 200a, 200b could then reach an agreement on payment/renumeration with regards to an over-the-top application, or a peer-to-peer application for payment/renumeration, for the radio resources to be transferred from the second terminal device 200b to the first terminal device 200a. In particular, according to an embodiment, the request in S110 comprises an offer for using radio resources allocated to the second terminal device 200b and the first terminal device 200a is configured to perform (optional) step S114:
S114: The first terminal device 200a transmits, via the sidelink <NUM>, a response to the second terminal device 200b. The response comprises at least a partial acceptance of the offer.

The notification in S116 to the network node <NUM> might then include information of acceptance of the offer. In particular, according to an embodiment, the notification in S116 provided towards the network node <NUM> comprises the at least partial acceptance of the offer.

In some aspects, payment/remuneration between the first terminal device 200a and the second terminal device 200b is additionally or alternatively handled via, or supervised by, the network node <NUM> and/or an Operational Support System (OSS) or Business Support System (BSS) in the communications network 100a, 100b.

There could be different ways for the first terminal device 200a to provide the notification in S116. Different aspects relating thereto will now be disclosed in detail.

According to a first aspect the notification is in S116 provided by being transmitted directly to the network node <NUM>, without being transmitted via the second terminal device 200b. That is, according to an embodiment, the notification is in S116 provided towards the network node <NUM> by being transmitted directly to the network node <NUM> from the first terminal device 200a.

In this case the notification might comprise an encrypted, or otherwise protected, secret, such as a key, that is shared by the network node <NUM> and the second terminal device 200b but not known by the first terminal device 200a that will ensure the network node <NUM> that the second terminal device 200b has agreed to offer the requested radio resources to the first terminal device 200a. That is, according to an embodiment, the response from the second terminal device 200b comprises a protected secret shared by the network node <NUM> and the second terminal device 200b but not known by the first terminal device 200a, and the notification in S116 comprises the protected secret.

According to a second aspect the notification is in S116 provided by being transmitted to the network node <NUM> via the second terminal device 200b. That is, according to an embodiment the notification is in S116 provided towards the network node <NUM> by being transmitted to the second terminal device 200b for forwarding therefrom to the network node <NUM>.

In this case the notification might comprise an encrypted, or otherwise protected, secret, such as a key, that is shared by the network node <NUM> and the first terminal device 200a but not known by the second terminal device 200b that will ensure the network node <NUM> that the first terminal device 200a has agreed to the offer of the requested radio resources as given by the second terminal device 200b. That is, according to an embodiment, the notification in S116 comprises a protected secret shared by the network node <NUM> and the first terminal device 200a but not known by the second terminal device 200b.

As will be further disclosed below, the network node <NUM> determines whether to accept or reject the at least some of the requested radio resources to be granted to the first terminal device 200a. Particularly, according to an embodiment the first terminal device 200a is configured to perform (optional) step S118:
S118: The first terminal device 200a receives, from the network node <NUM>, a decision pertaining to whether the network node <NUM> has accepted the at least some of the requested radio resources to be granted the first terminal device 200a or not.

The first terminal device 200a is then configured to act accordingly. Particularly, according to an embodiment the first terminal device 200a is configured to perform (optional) step S120:
S120: The first terminal device 200a consumes the at least some of the requested radio resources according to the decision.

Reference is now made to <FIG> illustrating a method for granting radio resources to a first terminal device 200a as performed by the second terminal device 200b according to an embodiment.

As disclosed above, the first terminal device 200a requests extra radio resource from a peer terminal device, exemplified by the second terminal device 200b.

S204: The second terminal device 200b receives, via a sidelink <NUM> to the first terminal device 200a, a request for the first terminal device 200a to use radio resources allocated to the second terminal device 200b.

S206: The second terminal device 200b transmits, via the sidelink <NUM>, a response to the first terminal device 200a. The response pertains to whether the second terminal device 200b has granted the first terminal device 200a to use at least some of the requested radio resources or not.

A notification is then provided towards the network node <NUM> serving the second terminal device 200b.

S210: The second terminal device 200b provides, towards a network node <NUM> serving the second terminal device 200b, a notification of that the first terminal device 200a has requested the radio resources from the second terminal device 200b and/or of that the second terminal device 200b has granted the first terminal device 200a to use at least some of the requested radio resources.

Embodiments relating to further details of granting radio resources to a first terminal device 200a as performed by the second terminal device 200b will now be disclosed.

As disclosed above, in some aspects the sidelink <NUM> is not already established when the first terminal device 200a identifies the increasing need for use of radio resources. The sidelink <NUM> then needs to be established before the request in S204 is received. According to an embodiment the second terminal device 200b is therefore configured to perform (optional) step S202:
S202: The second terminal device 200b receives, from the network node <NUM>, a request to establish the sidelink <NUM>.

As disclosed above, in some aspects the response in S206 from the second terminal device 200b includes information of the amount of offered radio resources and/or of the time duration during which the offered radio resources might be used by the first terminal device 200a. In particular, according the response to the first terminal device 200a comprises information of amount of the radio resources granted to the first terminal device 200a and/or for how long time the radio resources are granted to the first terminal device 200a.

Further, the information of the amount of offered radio resources and/or of the time duration during which the offered radio resources might be used by the first terminal device 200a might be included in the notification in S210 provided towards the network node <NUM>. That is, according to an embodiment, the notification in S210 provided towards the network node <NUM> comprises this information.

As disclosed above, in some aspects the offer comprises details of payment/remuneration between the first terminal device 200a and the second terminal device 200b. Particularly, according to an embodiment, the request in S204 comprises an offer for using radio resources allocated to the second terminal device 200b and the second terminal device 200b is configured to perform (optional) step S208:
S208: The second terminal device 200b receives, via the sidelink <NUM>, a response from the first terminal device 200a. The response comprises at least a partial acceptance of the offer.

The notification in S210 to the network node <NUM> might then include information of acceptance of the offer. In particular, according to an embodiment, the notification in S210 provided towards the network node <NUM> comprises the at least partial acceptance of the offer.

There could be different ways for the second terminal device 200a to provide the notification in S210. Different aspects relating thereto will now be disclosed in detail.

According to a first aspect the notification is in S210 provided by being transmitted directly to the network node <NUM>, without being transmitted via the first terminal device 200a. That is, according to an embodiment, the notification is in S210 provided towards the network node <NUM> by being transmitted directly to the network node <NUM> from the second terminal device 200b.

In this case the notification might comprise an encrypted, or otherwise protected, secret, such as a key, that is shared by the network node <NUM> and the first terminal device 200a but not known by the second terminal device 200b that will ensure the network node <NUM> that the first terminal device 200b has agreed to the offer of the requested radio resources as given by the second terminal device 200b. That is, according to an embodiment, the response in S206 from the first terminal device 200a comprises a protected secret shared by the network node <NUM> and the first terminal device 200a but not known by the second terminal device 200b, and the notification in S210 comprises the protected secret.

According to a second aspect the notification is in S210 provided by being transmitted to the network node <NUM> via the first terminal device 200a. That is, according to an embodiment the notification is in S210 provided towards the network node <NUM> by being transmitted to the first terminal device 200a for forwarding therefrom to the network node <NUM>.

In this case the notification might comprise an encrypted, or otherwise protected, secret, such as a key, that is shared by the network node <NUM> and the second terminal device 200b but not known by the first terminal device 200a that will ensure the network node <NUM> that the second terminal device 200b has agreed to offer the requested radio resources to the first terminal device 200a. That is, according to an embodiment, the notification in S210 comprises a protected secret shared by the network node <NUM> and the second terminal device 200b but not known by the first terminal device 200a.

As will be further disclosed below, the network node <NUM> determines whether to accept or reject the at least some of the requested radio resources to be granted to the first terminal device 200a. Particularly, according to an embodiment the second terminal device 200b is configured to perform (optional) step S212:
S212: The second terminal device 200b receives, from the network node <NUM>, a decision pertaining to whether the network node <NUM> has accepted the at least some of the requested radio resources to be granted the first terminal device 200a or not.

The second terminal device 200b is then configured to act accordingly. Particularly, according to an embodiment the second terminal device 200b is configured to perform (optional) step S214:
S214: The second terminal device 200b refrains from consuming the at least some of the requested radio resources according to the decision.

Reference is now made to <FIG> illustrating a method for handling radio resources between a first terminal device 200a and a second terminal device 200b as performed by the network node <NUM> according to an embodiment.

As disclosed above, a notification pertaining to whether the second terminal device 200b has granted the first terminal device 200a to use at least some of the requested radio resources or not is provided towards the network node <NUM>.

S308: The network node <NUM> obtains, from a least one of the first terminal device 200a served by the network node <NUM> and the second terminal device 200b served by the network node <NUM>, a notification of that the first terminal device 200a has requested radio resources from the second terminal device 200b where the radio resources have been allocated to the second terminal device 200b, and/or of that the second terminal device 200b has granted the first terminal device 200a to use at least some of the requested radio resources.

The network node <NUM> then responds with a decision regarding whether to accept or reject the at least some of the requested radio resources to be granted the first terminal device 200a.

S314: The network node <NUM> transmits, to at least one of the first terminal device 200a and the second terminal device 200b, a decision pertaining to whether the network node <NUM> has accepted the at least some of the requested radio resources to be granted the first terminal device 200a or not.

Embodiments relating to further details of handling radio resources between a first terminal device 200a and a second terminal device 200b as performed by the network node <NUM> will now be disclosed.

As disclosed above, in some aspects the notification in S308 might include information of acceptance of an offer. In particular, according to an embodiment the notification in S308 comprises at least a partial acceptance of an offer of the first terminal device 200a for using radio resources allocated to the second terminal device 200b.

As further disclosed above, in some aspects the notification in S308 might include information of the amount of offered radio resources and/or of the time duration during which the offered radio resources might be used by the first terminal device 200a. In particular, according to an embodiment the notification in S308 comprises information of amount of the radio resources granted to the first terminal device 200a and/or for how long time the radio resources are granted to the first terminal device 200a.

As further disclosed above, in some aspects the sidelink <NUM> is not already established when the first terminal device 200a identifies the increasing need for use of radio resources. Particularly, according to an embodiment the network node <NUM> is configured to perform (optional) steps S302, S304:
S302: The network node <NUM> receives, from the first terminal device 200a, a request to establish the sidelink <NUM>; and in response thereto:
S304: The network node <NUM> transmits, at least to the second terminal device 200b, a request to establish the sidelink <NUM>.

It is thus assumed that both the first terminal device 200a and the second terminal device 200b are requested, or even instructed or ordered, to establish the sidelink <NUM>. The request might further comprise instructions for the first terminal device 200a and the second terminal device 200b to not use uplink resources when transmission over the sidelink <NUM> is expected to be received.

As further disclosed above, in some aspects the request in S302 to establish the sidelink <NUM> includes information of the network service for which the radio resource are to be used by the terminal device <NUM>. Particularly, according to an embodiment, the request to establish the sidelink <NUM> comprises an indication of which network service the increasing need for use of radio resources results from.

In some aspects the request in S304 to establish the sidelink <NUM> is transmitted to more than one potential second terminal device. In particular, according to an embodiment, the request to establish the sidelink <NUM> is transmitted to a set of candidate terminal devices, and the network node <NUM> is configured to perform (optional) step S306:
S306: The network node <NUM> transmits, to the first terminal device 200a, an identifier of the set of candidate terminal devices.

There could be different ways for the network node <NUM> to determine which terminal devices to include in the set of candidate terminal devices. As will be further disclosed next, in some aspects the set of candidate terminal devices is based on their radio conditions, capabilities, and which network service the first terminal device 200a is to use, etc. Particularly, according to an embodiment, the set of candidate terminal devices is selected based on at least one of: their radio conditions, their capabilities, and which network service the requested radio resources are to be used by the first terminal device 200a. Further examples thereof will now be disclosed.

In some aspects the network node <NUM> considers which second terminal devices 200b to inform of an incoming sidelink transmission over the PC5 interface by considering their corresponding weights in the scheduling process.

For example, the network node <NUM> could indicate the resource allocations of radio resources for the considered announcing and monitoring terminal devices by creating a list of potential second terminal devices 200b with respect to radio measures relevant for scheduling bandwidth prioritization, such as measurements of reference signal received power (RSRP), signal plus interference and noise ratio (SINR), modulation and coding scheme (MCS), channel quality indicator (CQI), transmission rank, etc. The network node <NUM> could then select a set of potential second terminal devices 200b among the terminal devices 200b present in the scheduling evaluations of the network node <NUM> such that the potential second terminal devices 200b will have an opportunity to provide radio resources to the first terminal device 200a. This could reduce the risk of a second terminal devices 200b beings selected that has little or no priority in the ongoing scheduling evaluations.

In some aspects the network node <NUM> considers which device category (such as UE category) the potential second terminal devices 200b belong to. For example, the network node <NUM> could consider their respective capabilities in terms of number of transmit/receive antennas, MCS, multiple input multiple output (MIMO) and transmission rank capability, QoS capabilities, maximum uplink/downlink throughput, etc. As an example, if the first terminal device 200a is of lower device category and/or has lower capabilities than the second terminal device 200b, only requested radio resources corresponding to the category and/or capabilities of the first terminal device 200a might be granted to the first terminal device 200a, which might enable surplus radio resources to be granted from the second terminal device 200b to a yet further terminal device, if needed.

In some aspects the request from the first terminal device 200a to establish the sidelink <NUM> comprises information about whether the requested radio resource are to be used for uplink communication or downlink communication. In some aspects the network node <NUM> thus considers what link direction (i.e., uplink or downlink) the requested radio resource are to be used for by the first terminal device 200a. The network node <NUM> could then select a set of potential second terminal devices 200b by considering those potential second terminal devices 200b present in the scheduling evaluations of the network node <NUM> such that the potential second terminal devices 200b will have an opportunity to provide radio resources to the first terminal device 200a in the link direction requested by the first terminal device 200a. This could reduce the risk of a second terminal devices 200b beings selected that has little or no radio resource available in the link direction requested by the first terminal device 200a.

In some aspects the request from the first terminal device 200a to establish the sidelink <NUM> comprises an indication of which network service (such as mobile broadband, voice, streaming, etc.) the increasing need for use of radio resources results from. In some aspects the network node <NUM> thus considers what type of network service the requested radio resource are to be used for by the first terminal device 200a. The network node <NUM> could then select a set of potential second terminal devices 200b by considering those potential second terminal devices 200b present in the scheduling evaluations of the network node <NUM> such that the potential second terminal devices 200b will have an opportunity to provide radio resources to the first terminal device 200a capable of supporting the requested network service. This could reduce the risk of a second terminal devices 200b beings selected that has not enough amount of radio resource available for the network service to be used by the first terminal device 200a.

As the skilled person understands the request from the first terminal device 200a might comprise an indication of two or more network services the increasing need for use of radio resources results from, and where the set of potential second terminal devices 200b is selected accordingly.

As the skilled person further understands, the above examples for selecting a set of potential second terminal devices 200b could be combined by the network node <NUM> considering two or more pieces of information (such as weights, category, link direction, network services).

In some aspects, the network node <NUM> determines whether to accept or reject the radio resources to be granted to the first terminal device 200a. In particular, according to a first embodiment the network node <NUM> is configured to perform (optional) step S310:.

The decision is then transmitted as in above S314.

There could be different ways for the network node <NUM> to determine whether to accept (as in S310) or reject (as in S312) the at least some of the requested radio resources to be granted the first terminal device 200a.

When the notification in S308 is received (only) from the first terminal device 200a, the at least some of the requested radio resources are rejected to be granted to the first terminal device 200a when the notification fails to comprise a protected secret shared by the network node <NUM> and the second terminal device 200b but not known by the first terminal device 200a. The request might be granted, or at least be considered for further evaluation, when the notification comprises the protected secret.

When the notification in S308 is received (only) from the second terminal device 200b, the at least some of the requested radio resources are rejected to be granted to the first terminal device 200a when the notification fails to comprise a protected secret shared by the network node <NUM> and the first terminal device 200a but not known by the second terminal device 200b. The request might be granted, or at least be considered for further evaluation, when the notification comprises the protected secret.

When a separate instance of the notification in S308 is received from each of the first terminal device 200a and from the second terminal device 200b, the at least some of the requested radio resources are rejected to be granted the first terminal device 200a when the instances of the notification fail to match each other. The request might be granted, or at least be considered for further evaluation, when the instances of the notification match each other.

The further evaluation might relate to a policy decision for the first terminal device 200a and/or the second terminal device 200b, properties of a network subscription for the first terminal device 200a and/or the second terminal device 200b, etc. that might allow or not allow radio resources to be accepted from, or shared to, another terminal device.

One particular embodiment for handling radio resources between a first terminal device 200a and a second terminal device 200b based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of <FIG>. According to this embodiment, the first terminal device 200a sends via a D2D application a request to other D2D-capable terminal devices (as symbolized by the second terminal device 200b) in its vicinity (via the PC5 interface) to use a part of the radio resources (specified in term of duration, bandwidth, throughput, etc.) of these other terminal devices. The other part either accepts or rejects the request and information of this is sent to the first terminal device 200a and their serving network node <NUM>.

S401: First terminal device 200a considers its current cellular performance non-adequate (considering adequate radio quality but still poor throughput, i.e. due to high cell load) and decides to request potential other terminal devices in its vicinity to request a specified share of their radio resources, for example described in terms of a specified duration in time, bandwidth, application throughput, number of delivered bits, etc..

S402: First terminal device 200a requests its serving network node <NUM> for a sidelink transmission to contact other terminal devices 200b to request extra radio resources from them.

S403a, S403b: first terminal device 200a indicates resource allocations for the considered announcing and monitoring terminal devices.

S404: First terminal device 200a requests, via the sidelink, resources from the listening terminal devices (implicitly selected by the serving network node <NUM>). For example, first terminal device 200a might provide a request with an offer for radio resource corresponding to specified duration in time, bandwidth, application throughput, number of delivered bits, etc. and optionally a renumeration offer for the radio resource.

S405a, S405b: First terminal device 200a responds to first terminal device 200a with either an acknowledgement (ACK) or a negative acknowledgement (NACK) to the request whereby first terminal device 200a in turn is prompted with an ACK/NACK, potentially including a partial agreement of the offer (in terms of offered radio resources, demand for renumeration, etc.), potentially including an alternative to the offer (in terms of offered radio resources, demand for renumeration, etc.).

S406: First terminal device 200a selects one offer and replies to second terminal device 200b with an agreement.

S407: First terminal device 200a sends a Requester Payment Agreed Message (R-PAM), including information of second terminal device 200b and terms, e.g. duration, of contract, etc. to the serving network node <NUM>.

S408: Second terminal device 200b sends a Provider Payment Agreed Message (P-PAM), including information of second terminal device 200b and duration of the contract, etc. to the serving network node <NUM>.

S409: Network node <NUM> checks presence and validity of both R-PAM and P-PAM. If both are found valid the network node <NUM> re-allocates scheduled radio resources of second terminal device 200b to first terminal device 200a for the time period agreed in the contract. If at least one is found invalid the network node <NUM> dismisses the request. With frequent mismatches between observed R-PAM and P-PAM, either first terminal device 200a or second terminal device 200b could be blocked/listed/black-listed/put-on-monitor for further considerations.

S410: Network node <NUM> releases second terminal device 200b from the contract after duration of contract time has passed (possibly in combination with some utilized measure of used radio resources).

S411a, S411b: Network node <NUM> informs first terminal device 200a and second terminal device 200b of the termination of the contract.

<FIG> schematically illustrates, in terms of a number of functional units, the components of a terminal device 200a, 200b according to an embodiment. Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1110a (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the terminal device 200a, 200b to perform a set of operations, or steps, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the terminal device 200a, 200b to perform the set of operations. Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed.

The terminal device 200a, 200b may further comprise a communications interface <NUM> for communications with network node <NUM>, ProSe server <NUM>, other terminal devices 200a, 200b, etc. in the communication network 100a, 100b. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry <NUM> controls the general operation of the terminal device 200a, 200b e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the terminal device 200a, 200b are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of a terminal device 200a, 200b according to an embodiment.

When acting as a first terminal device 200a, the terminal device 200a comprises an identity module 210a configured to perform step S102, a transmit module 210e configured to perform step S110, a receive module 310f configured to perform step S112, and a provide module <NUM> configured to perform step S116. When acting as a first terminal device 200a, the terminal device 200a may further comprise a number of optional functional modules, such as any of a transmit module 210b configured to perform step S104, a receive module 210c configured to perform step S106, a store module 210d configured to perform step S108, a transmit module <NUM> configured to perform step S114, a receive module 210i configured to perform step S118, and a consume module 210j configured to perform step S120.

When acting as a second terminal device 200b the terminal device 200b comprises a receive module <NUM> configured to perform step S204, a transmit module <NUM> configured to perform step S206, and a provide module 210o configured to perform step S210. When acting as a second terminal device 200b the terminal device 200b may further comprise a number of optional functional modules, such as any of a receive module <NUM> configured to perform step S202, a receive module 210n configured to perform step S208, a receive module 210p configured to perform step S212, and a refrain module 210q configured to perform step S214.

In general terms, each functional module 210a-210q may be implemented in hardware or in software. Preferably, one or more or all functional modules 210a-210q may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and the storage medium <NUM>. The processing circuitry <NUM> may thus be arranged to from the storage medium <NUM> fetch instructions as provided by a functional module 210a-210q and to execute these instructions, thereby performing any steps of the terminal device 200a, 200b as disclosed herein.

<FIG> schematically illustrates, in terms of a number of functional units, the components of a network node <NUM> according to an embodiment. Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1110c (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the network node <NUM> to perform a set of operations, or steps, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the network node <NUM> to perform the set of operations. Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed.

The network node <NUM> may further comprise a communications interface <NUM> for communications with other entities, functions, nodes, servers, and devices of the communication networks 100a, 100b. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry <NUM> controls the general operation of the network node <NUM> e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the network node <NUM> are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of a network node <NUM> according to an embodiment. The network node <NUM> of <FIG> comprises a number of functional modules; an obtain module 310d configured to perform step S308, and a transmit module <NUM> configured to perform step S314. The network node <NUM> of <FIG> may further comprise a number of optional functional modules, such as any of a receive module 310a configured to perform step S302, a transmit module 310b configured to perform step S304, a transmit module 310c configured to perform step S306, an accept module 310e configured to perform step S310, and a reject module 310f configured to perform step S312.

In general terms, each functional module 310a-<NUM> may be implemented in hardware or in software. Preferably, one or more or all functional modules 310a-<NUM> may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and the storage medium <NUM>. The processing circuitry <NUM> may thus be arranged to from the storage medium <NUM> fetch instructions as provided by a functional module 310a-<NUM> and to execute these instructions, thereby performing any steps of the network node <NUM> as disclosed herein.

The network node <NUM> may be provided as a standalone device or as a part of at least one further device. For example, the network node <NUM> may be provided in a node of the radio access network or in a node of the core network. Alternatively, functionality of the first terminal device 200a may be distributed between at least two devices, or nodes. These at least two nodes, or devices, may either be part of the same network part (such as the radio access network or the core network) or may be spread between at least two such network parts. In general terms, instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the cell than instructions that are not required to be performed in real time. In this respect, at least part of the network node <NUM> may reside in the radio access network, such as in the radio access network node.

Thus, a first portion of the instructions performed by the network node <NUM> may be executed in a first device, and a second portion of the of the instructions performed by the network node <NUM> may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the network node <NUM> may be executed. Hence, the methods according to the herein disclosed embodiments are suitable to be performed by a network node <NUM> residing in a cloud computational environment. Therefore, although a single processing circuitry <NUM> is illustrated in Fig. x9 the processing circuitry <NUM> may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 310a-<NUM> of Fig. <NUM> and the computer programs 1120c of <FIG>.

<FIG> shows one example of a computer program product 1110a, 1110b, 1110c comprising computer readable means <NUM>. On this computer readable means <NUM>, a computer program 1120a can be stored, which computer program 1120a can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1120a and/or computer program product 1110a may thus provide means for performing any steps of the first terminal device 200a as herein disclosed. On this computer readable means <NUM>, a computer program 1120b can be stored, which computer program 1120b can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1120b and/or computer program product 1110b may thus provide means for performing any steps of the second terminal device 200b as herein disclosed. On this computer readable means <NUM>, a computer program 1120c can be stored, which computer program 1120c can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1120c and/or computer program product 1110c may thus provide means for performing any steps of the network node <NUM> as herein disclosed.

In the example of <FIG>, the computer program product 1110a, 1110b, 1110c is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 1110a, 1110b, 1110c could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 1120a, 1120b, 1120c is here schematically shown as a track on the depicted optical disk, the computer program 1120a, 1120b, 1120c can be stored in any way which is suitable for the computer program product 1110a, 1110b, 1110c.

Claim 1:
A method for requesting radio resources from a second terminal device (200b), the method being performed by a first terminal device (200a), the method comprising:
identifying (S102) an increasing need for use of radio resources;
transmitting (S110), via a sidelink (<NUM>) to the second terminal device (200b), a request for using radio resources allocated to the second terminal device (200b);
receiving (S112), via the sidelink (<NUM>), a response from the second terminal device (200b), the response pertaining to whether the second terminal device (200b) has granted the first terminal device (200a) to use at least some of the requested radio resources or not,
the method characterized by further comprising:
providing (S116), towards a network node (<NUM>) serving the first terminal device (200a), a notification of that the first terminal device (200a) has requested the radio resources from the second terminal device (200b) and of that the second terminal device (200b) has granted the first terminal device (200a) to use at least some of the requested radio resources;
receiving (S118), from the network node (<NUM>), a decision pertaining to whether the network node (<NUM>) has accepted the at least some of the requested radio resources to be granted to the first terminal device (200a) or not; and
consuming (S120) the at least some of the requested radio resources according to the decision.