Devices and methods for spectrum sharing in wireless networks

Abstract

A radio node (10) of a wireless network, comprising: a wireless transceiver (413); logic circuitry (410) configured to: transmit (810) a request message associated with resources within a pool of radio resources configured by a resource management node for spectrum sharing; receive (814), responsive to the request message, a message indicative of allocation of resources from the pool of radio resources, wherein the allocated resources are usable for scheduling in a subnetwork of user equipment, UE.

Description

[0001] DEVICES AND METHODS FOR SPECTRUM SHARING IN WIRELESS

[0002] NETWORKS

[0003] Technical field

[0004] This disclosure relates to the field of wireless communication, and specifically to the task of spectrum sharing. The proposed solution is associated with devices which interact to provide an agile mechanism for sharing resources in a wireless system, to obtain effective use of available spectrum.

[0005] Background

[0006] In wireless communication, a wireless channel is used to transfer information and data between different radio nodes acting as transmitter and receiver, using an electromagnetic wave signal. Wireless communication has been operative for several decades and involves a radio access network (RAN) which uses an air interface to communicate wirelessly with various devices, commonly referred to as User Equipment (UE) in the realm of the 3rdGeneration Partnership Project (3GPP). The RAN is connected to a backbone, referred to as core network (CN), which is connected to other networks, such as the Internet.

[0007] Spectrum is a scares resource in wireless communication. For this purpose, several attempts have been made to accomplish methods for reasonable sharing of the available spectrum. There are different approaches to share spectrum, such as geographic separation, time based (TDD), underlay, differences in powers and bandwidths, collaborative, e.g.

[0008] Legacy sharing on high level is that a number of operators in different countries purchase parts of the available and defined spectrum throughout the country and basically cover the area with its RAN, e.g., employing a frequency reuse pattern to avoid interference between cells.

[0009] In the United States, an entity referred to as CBRS (Citizens Broadband Radio Service) has defined a mechanism where, during times spectrum is not used, it can be indicated in a database and requested by other users originally not part of the licensed spectrum. CBRS thus provides a set of frequency bands for shared wireless use. It allows different types of users, including commercial entities and public safety organizations, to coexist and use the spectrum without causing interference to one another. This sharing is achieved through a three-tiered approach based on Incumbent Access, with Priority Access License (PAL) Holders, and General Authorized Access (GAA) Users, where the latter tier is open for unlicensed users, similar to how Wi-Fi operates. GAA users can access the spectrum as long as they do not cause harmful interference to incumbent or PAL users.

[0010] However, the spectrum sharing feature in CBRS, or as in TV White Spaces (TVWS), is a rather static system. There are thus challenges in accomplishing faster and more dynamic mechanisms to (re-)allocate spectrum, with timing down to below a second, not only within an operator or private network, but also between them.

[0011] Summary

[0012] A general object is to provide a mechanism for spectrum sharing in wireless communications. The proposed solution is defined by the terms of the independent claims, whereas various additional features are set out in the dependent claims.

[0013] The proposed solution involves the implementation of a resource management node configured to manage resource sharing, and optionally also for handling charging for reserved and utilized resources. The resource management node may be related to a geographical area where e.g., two base stations from different operators have overlapping coverage. Resource sharing operated by the resource management node may further be used for subnetworks, like roaming mobile vehicle subnetworks.

[0014] According to a first aspect, a radio node of a wireless network is provided, comprising a wireless transceiver and logic circuitry configured to receive a message indicative of allocation of resources from a pool of radio resources for spectrum sharing configured by a resource management node, wherein the allocated resources are usable for scheduling in a subnetwork of user equipment, UEs. In various examples, this mechanism may be set out in a UE acting as the radio node, in other examples in a base station acting as the radio node.

[0015] According to a second aspect, a resource management node is provided, which is connected to a wireless network and comprises logic circuitry configured to receive a request message associated with resources within a pool of radio resources configured for spectrum sharing; and to transmit, to a radio node of a wireless network, a message indicative of allocation of resources from the pool of radio resources, available for configuration of a UE with scheduling right as group head in a subnetwork.

[0016] By means of the proposed solution, a mechanism is obtained which is usable for temporarily allocating resources to a UE, which may subsequently schedule those resources for use in a subnetwork. This way, a dynamic way of sharing spectrum resources is accomplished.

[0017] Brief description of the drawings

[0018] Various examples will be described with reference to the drawings, in which:

[0019] Fig. 1 schematically illustrates a radio network with a connected resource management node according to an example of the proposed solution;

[0020] Fig. 2 schematically illustrates functional elements of a resource management node in accordance with various examples of the proposed solution;

[0021] Fig. 3 schematically illustrates functional elements of a radio node in the form of an access node, configured in accordance with various examples of the proposed solution;

[0022] Fig. 4 schematically illustrates functional elements of a radio node in the form of a UE, configured in accordance with various examples of the proposed solution;

[0023] Fig. 5A illustrates an example of timing of a reoccurring pool of radio resources, in which spectrum may be shared among users;

[0024] Fig. 5B schematically illustrates an example of a resource gris of a pool of radio resources, and allocation of various parts of that pool to different subnetworks;

[0025] Fig. 6 shows a flow chart of a method carried out in a radio node, in accordance with various examples of the proposed solution;

[0026] Fig. 7 shows a flow chart of a method carried out in a resource management node, in accordance with various examples of the proposed solution; and

[0027] Fig. 8 provides a signaling diagram showing various features and alternatives of the proposed solution. Detailed description

[0028] In the following description, for purposes of explanation and not limitation, details are set forth herein related to various examples. However, it will be apparent to those skilled in the art that the present disclosure may be practiced in other examples that depart from these specific details. In some instances, detailed descriptions of well- known devices, circuits, and methods are omitted so as not to obscure the description of the present disclosure with unnecessary detail. The functions of the various elements including functional blocks, including but not limited to those labeled or described as “computer”, “processor” or “controller”, may be provided through the use of hardware such as circuit hardware and / or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and / or computer-implemented and are thus machine-implemented. In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) (ASIC), and (where appropriate) state machines capable of performing such functions. In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term “processor” or “controller” shall also be construed to refer to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above.

[0029] The drawings provide performance plots and are otherwise to be regarded as being schematic, where representations and elements illustrated in the drawings are not necessarily shown to scale. Rather, the various elements are represented such that their function and general purpose become apparent to a person skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be implemented by an indirect connection or coupling. A coupling between components may also be established over a wireless connection. Functional blocks may be implemented in hardware, firmware, software, or a combination thereof.

[0030] Fig. 1 schematically illustrates a wireless communication scenario, providing an example of a scene in which the solutions provided herein may be incorporated. A wireless network 100A comprises an access network 120A, such as a 5G NR access network (Radio Access Network - RAN 120A). The access network 120A may comprise a plurality of access nodes or base stations, of which access node 121A is indicated, configured to provide a wireless interface for communication over an air interface with wireless stations (UEs). For an NR implementation, the access node may be referred to as a gNB. Each access node comprises a point of transmission and reception, referred to as a Transmission and Reception Point (TRP), which coincides with an antenna array of the respective access node. The wireless network 100A further includes a core network (CN) 110A, to which the access network 120A is connected. The core network 110A is in turn connected to other communication networks, such as the Internet.

[0031] In the context of the proposed solution, a second wireless network 100B may exist, with a RAN 120B comprising an access node 121B, and a CN HOB connected to the RAN 120B.

[0032] A UE 10 is shown, which may belong to one of the wireless networks 100A, 100B, or may be roaming. Further UEs, such as a second UE 20, are also indicated as part of a subnetwork 300, as will be further outlined below. Each UE may be any device operable to wirelessly communicate with the network 100A through the base stations 121 A, such as a mobile telephone, computer, tablet, a machine to machine (M2M) device, an loT (Internet of Things) device, a vehicle device, or other.

[0033] A resource management node 200 is further shown, which is connected to at least the first network 100A, optionally also the second network 100B. In various examples, the resource management node is an edge device, connected to the access node 121A, and optionally also to the access node 121B which substantially is co-located with access node 121 A such that they have overlapping coverage areas. Before proceeding to the details of the examples of the proposed solution, various entities which may be configured to carry out different aspects of the proposed solution will be briefly described.

[0034] Fig. 2 schematically shows a resource management node, RM node for short, 200. The RM node 200 comprises logic circuitry 210 configured to carry out or assist in positioning / locating UEs in the wireless network 200.

[0035] The logic circuitry 210 may include a processing device 211, including one or multiple processors, microprocessors, data processors, co-processors, and / or some other type of component that interprets and / or executes instructions and / or data. Processing device 211 may be implemented as hardware (e.g., a microprocessor, etc.) or a combination of hardware and software (e.g., a system-on-chip (SoC), an applicationspecific integrated circuit (ASIC), etc.). The processing device 211 may be configured to perform one or multiple operations based on an operating system and / or various applications or programs.

[0036] The logic circuitry 210 may further include memory storage 212, which may include one or multiple memories and / or one or multiple other types of storage mediums. For example, memory storage 212 may include a random access memory (RAM), a dynamic random access memory (DRAM), a cache, a read only memory (ROM), a programmable read only memory (PROM), flash memory, and / or some other type of memory. Memory storage 212 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.). The memory storage 212 is configured for holding computer program code, which may be executed by the processing device 211, wherein the logic 210 is configured to control the RM node 200 to carry out any of the method steps as provided herein. Software defined by said computer program code may include an application or a program that provides a function and / or a process. The software may include device firmware, an operating system (OS), or a variety of applications that may execute in the logic 210. In some examples, the RM node 200 may be at least partially realized by computer code residing in the cloud.

[0037] The RM node 200 further comprises network (NW for short) interfaces 213, for connection to wireless networks, such as networks 100A and 100B. In some examples, the RM node 120 may be long to, and form part of one wireless network 100A, and optionally be connected to network 100B by means of the interface 213. In other examples, the RM node 200 is an edge device with is not tied to any single network or operator. In such examples, the NW interfaces may be communicatively connectable to directly to access nodes (e.g., 121A and 121B) of one or more wireless networks, as exemplified in Fig. 1.

[0038] Fig. 3 schematically illustrates a radio node in the form of an access node 121, which may be any of access nodes 121 A or 121B as exemplified in Fig. 1. The radio node 121 may be configured to carry out various method steps as outlined herein. In various examples, the access node 121 is a radio base station for operation in the radio communication network 100A, to serve one or more radio UEs, such as the UE 10.

[0039] The access node 121 may comprise a wireless transceiver 313, such as a radio transceiver for communicating with other entities of the radio communication network 100, such as the UE 10. The transceiver 313 may thus include a radio receiver and transmitter for communicating through at least an air interface.

[0040] The access node 121 may further comprise, or be connected to, an antenna 314 which may comprise a plurality of antennas (antenna elements). The antenna 314 is connected to the transceiver 313.

[0041] The access node 121 further comprises logic circuitry 310 configured to control the access node 121 to communicate with wireless devices, such as the UE 10, via the radio transceiver 313 on a physical channel.

[0042] The logic circuitry 310 may include a processing device 311, including one or multiple processors, microprocessors, data processors, co-processors, and / or some other type of component that interprets and / or executes instructions and / or data. Processing device 311 may be implemented as hardware (e.g., a microprocessor, etc.) or a combination of hardware and software (e.g., a system-on-chip (SoC), an applicationspecific integrated circuit (ASIC), etc.). The processing device 311 may be configured to perform one or multiple operations based on an operating system and / or various applications or programs.

[0043] The logic circuitry 310 may further include memory storage 312, which may include one or multiple memories and / or one or multiple other types of storage mediums. For example, memory storage 312 may include a random access memory (RAM), a dynamic random access memory (DRAM), a cache, a read only memory (ROM), a programmable read only memory (PROM), flash memory, and / or some other type of memory. Memory storage 312 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.). The memory storage 312 is configured for holding computer program code, which may be executed by the processing device 311, wherein the logic 310 is configured to control the access node 121 to carry out any of the method steps as provided herein. Software defined by said computer program code may include an application or a program that provides a function and / or a process. The software may include device firmware, an operating system (OS), or a variety of applications that may execute in the logic 310.

[0044] The access node 121 may further comprise an interface 315, configured for communication with a core network.

[0045] Fig. 4 schematically illustrates a radio node in the form of a wireless device, referred to as UE 10. The UE 10 may be configured for carrying out various method steps as outlined.

[0046] The UE 10 may comprise a wireless transceiver 413, such as a radio transceiver for communicating with other entities of the radio communication network 100, such as access nodes of the RANs 120A and 120B, and with further UEs in a subnetwork. The transceiver 413 may thus include a radio receiver and transmitter for communicating through at least an air interface. The transceiver may comprise a radio modem.

[0047] The UE 10 may further comprise, or be connected to, an antenna 414 which may comprise a plurality of antennas (antenna elements). The antenna 414 is connected to the transceiver 413.

[0048] The UE 10 further comprises logic circuitry 410 configured to control the UE 10 to communicate with other devices via the radio transceiver 413 on a physical channel. The logic circuitry 410 may realize a scheduler for scheduling communication of data according to the solutions proposed herein, and for configuring one or more further UEs to communicate data according to the scheduling.

[0049] The logic circuitry 410 may include a processing device 411, including one or multiple processors, microprocessors, data processors, co-processors, and / or some other type of component that interprets and / or executes instructions and / or data. Processing device 411 may be implemented as hardware (e.g., a microprocessor, etc.) or a combination of hardware and software (e.g., a system-on-chip (SoC), an applicationspecific integrated circuit (ASIC), etc.). The processing device 411 may be configured to perform one or multiple operations based on an operating system and / or various applications or programs. The logic circuitry 410 may further include memory storage 412, which may include one or multiple memories and / or one or multiple other types of storage mediums. For example, memory storage 412 may include a random access memory (RAM), a dynamic random access memory (DRAM), a cache, a read only memory (ROM), a programmable read only memory (PROM), flash memory, and / or some other type of memory. Memory storage 412 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.). The memory storage 412 is configured for holding computer program code, which may be executed by the processing device 411, wherein the logic 410 is configured to control the UE 10 to carry out any of the method steps as provided herein. Software defined by said computer program code may include an application or a program that provides a function and / or a process. The software may include device firmware, an operating system (OS), or a variety of applications that may execute in the logic 410.

[0050] The solutions proposed herein are configured to provide a mechanism for defining resources that may be shared between subnetworks, such as resource sharing between different operators and private networks in the public domain. The RM node 200 provides a new entity and is preferably placed at the edge close to group of access nodes 121A, 12B. The RM node 200 is in various examples configured to serve access nodes and subnetworks belonging to different operators (wireless networks 100A, 100B) and may serve a specific area in which access nodes 121A, 12B of different wireless networks have overlapping coverage, e.g., cell coverage. The proposed solution is configured to operate across cell borders and to avoid interference between subnetworks not only handled by one operator, but also between different operators.

[0051] Fig. 5A illustrates, by way of example, semi static configuration of a pool 50 of radio resources, or resource pool 50 for short, which may be configured by the RM node 200. The resource pool 50 may be configured within a limited frequency portion of a system bandwidth of the wireless network. The resource pool 50 of radio resources may further be configured within a reoccurring time duration, such as a semi static or periodic. In an alternative example, the resource pool 50 occupies all time slots of a certain limited frequency. Radio nodes, or applications, may request and reserve resources in the resource pool 50 from the RM 200.

[0052] Fig. 5B further illustrates an example where resources 51 within the resource pool 50, shown in a time / frequency diagram according to a booking table configured by the RM 200, are allocated to different UEs 52 and 53 or to different group s / subnetworks managed by UE 52 and UE as group heads, respectively. In this context, a UE 52 may be allocated resources for use by one subnetwork, whereas UE 53 is allocated resources for use by another subnetwork.

[0053] Contrary to CBRS, resource allocation is not provided for a whole and specific BW of a frequency and during a longer time period as in DSS database case, but temporarily for a shorter period, such as x seconds or minutes, and in a dynamically shared spectrum of the resource pool 50. This provides greater flexibility to resource allocation and increases the opportunity to allocate resources to more UEs and subnetworks. Temporary allocation may be configured as a certain time frame, or as a number of occurrences of the resource pool 50. Depending on resource need, the resource pool 50 can either be fully occupied by one UE / subnetwork or be shared as shown in Fig. 5B.

[0054] According to the state of the art. the UE 10 typically belongs to, or is attached to, one network. In an area covered by that network e.g., 100A, which may be partly colocated with another network 100B, the UE 10 can only use resources of its own network (PLMN - Public Land Mobile Network) 100A. However, in the context of the proposed solution, a UE such as the UE 10 may be in its home PLMN 100A, but the resource management node 200 may configure the pool 50 and allocate resources 51 in that pool 50 to the UE 10, e.g., for use as by the UE 10 as group head in a subnetwork, where said resources may could belong to (be licensed to) any operator’ s network, such as 100B. The RM node thus provides a mechanism for conveniently sharing even licensed resources from different operator networks 100A, 100B for use in subnetworks.

[0055] The proposed solution may in some examples reuse mechanisms configured for SL operation, as outlined inter alia in 3GPP specifications 38.300, 38.331, and 38.212. For this purpose, sidelink (SL) will be briefly discussed going forward.

[0056] For SL, communication directly between UEs is specified, where a specific resource pool is defined, and where the resources within the pool are either allocated by the gNB (Mode 1) or can be handled autonomously by the UEs using sensing mechanism to avoid collision (Mode 2).

[0057] As an overview, NR (New Radio) SL communication is designed to support V2X services via UE-to-UE PC5 interface, but may be used to support other services than as well. Sidelink provides for three types of transmission modes: 1. Broadcast: o Transmission and reception of user traffic among UEs in SL

[0058] 2. Groupcast: o Transmission and reception of user traffic among UEs belonging to a group in SL; o Support of SL HARQ (Hybrid Automatic Repeat reQuest) feedback.

[0059] 3. Unicast: o Support of one PC5-RRC (Radio Resource Control) connection between peer UEs; o Transmission and reception of control information and user traffic between peer UEs; o Support of SL HARQ feedback; o Support of SL transmit power control; o Support of RLC AM (Radio Link Control Acknowledgment Mode); o Detection of radio link failure for the PC5-RRC connection.

[0060] As noted, there are two resource allocations modes in SL: Mode 1 and Mode 2.

[0061] In Mode 1 (Scheduled resource allocation) the UE needs to be RRC_CONNECTED to transmit data, and it gets the resource allocation from the gNB since it is the RAN that schedules the transmission resources.

[0062] In Mode 2, (UE autonomous resource selection), the UE can transmit data when inside or outside coverage. The UE autonomously selects transmission resources from resource pool(s). The resource pools can be preconfigured or configured by network.

[0063] Mode 2 is using principles from Unlicensed mode, including a LBT (Listening Before Talk) concept, where the Tx side performs sensing before transmission to detect if the channel is free. The Tx UE senses the resource pool for a period of time denoted sensing window. The sensing includes Sidelink Control Information (SCI) decoding in which the first-stage SCI on PSCCH (Physical Shared Control CHannel) can indicate future sub-channel(s) and slot(s) in which the UE will transmit, and Sidelink measurements where SL-RSRP (Reference Signal Received Power) corresponding to the SCI based on DMRS (Demodulation Reference Signal).

[0064] The sensing procedure is defined as decoding SCI from other UEs or measuring the power of SL transmissions from other UEs. By decoding SCI from other UEs, a UE is aware of the resource(s) planned to be used for SL transmissions by other UEs and can consider these resource(s) as non-available during the resource selection procedure. A selection window is a time interval from which a UE selects SL resources for transmission. It starts T1 > 0 after a resource (re-) selection trigger and ends at T2, bounded by at least a remaining PDB (Packet Delay Budget).

[0065] With respect to legacy SL procedures, briefly discussed above, various examples of the proposed solution may partly use resources configuration for SL, where both Mode 1 and Mode 2 resource allocation methods are feasible, or as a hybrid version of the two.

[0066] The proposed solution involves the RM node 200, the RAN 120A with an access node 121A, and a UE 10 which may be operated to set up a subnetwork 300. It shall be noted, though, that similarly the RAN 120B and its access node 121B, which is colocated with the access node 121A, may perform sensing and request resources from the RM node 200. In one aspect, operations according to the proposed solution may be executed by a radio node, such as the access node 121A or the UE 10. Some of those steps will now be described with reference to Fig. 6.

[0067] In step 600, a capability exchange may take place. This may follow legacy procedures, where UE capability is typically exchanged with the network 100A upon registration. Alternatively, or additionally, aspects of UE capability may be reported later in another UL message. In the context of the proposed solution, UE capability may provide subnetwork information, such one or more of subnetwork ID, maximum bitrate, maximum Tx power, frequency ban and bandwidth for subnetwork operation, etc. This capability information is conveyed to the RM node 200.

[0068] In step 602, the configuration of the resource pool 50 may be obtained. Where the resource pool 50 is configured according to specification, this obtainment may be preconfigured in program code in the radio node, i.e., in the UE 10 and / or the access node 121A. Where the RM node 200 configures the resource pool 50, the access node 121A may obtain this configuration by a message from the RM node 200, and the UE 10 may obtain this configuration by system information provided by its network 100A, or by a separate message. In some examples, the RM node 200 may configure plural different resource pools, and the UE 10 may be informed which resource pool is applicable for that UE.

[0069] In step 604, the radio node(s) may sense resources 51 of the resource pool 50. This may be carried out by the access node 121A, and particularly by the UE 10, by sensing radio activity in the resources 51. In some examples, the UE 10 may report results of the sensing, for receipt in the RM node 200, to indicate which resource are available within the resource pool 50. This reporting may take place in a scheduled fashion, or when the sensing indicates altered availability in the resource pool 50, or when resources are requested.

[0070] In step 606, a request message for resources 51 of the resource pool 50 is transmitted. The request message may originate from the UE 10, or from its serving access node 121 A, or from an application executed by the UE 10. As noted under step 604, the request message may comprise, or be combined with, a report indicative of resource availability based on sensing.

[0071] In some examples, step 608 comprises transmitting a request message associated with resources 51 of the resource pool 50, by the access node 121 A, which message comprises a request for an indication of available resources within the resource pool 50.

[0072] In step 608, a message may be received which is indicative of allocation of resources 51 within the resource pool 50. Specifically, those allocated resources are usable for scheduling by the UE 10 in a subnetwork of UEs. Where the UE 10 requests 606 and obtains 608 allocation of resources, the access nodes 121A, 121B having coverage in the area served by the RM node 200 may further receive a message indicative of these allocated resources.

[0073] In an example where the request message of step 606 comprises a request for an indication of available resources within the resource pool 50, the message indicative of allocation of resources 51 within the resource pool 50 may identify available resources. In this example, the mechanism may further include step 609 of the access node 121A allocating, and optionally scheduling, resources for the subnetwork based on the received indication of available resources. This step may further comprise transmitting, to the RM node 200, information of the allocated resources, for updating a booking table in the RM node 200.

[0074] In step 610, the allocated resources may be scheduled for a subnetwork 300.

[0075] In step 612, data may be exchanged between UEs of the subnetwork 300, using the resources scheduled by the UE 10.

[0076] Fig. 7 shows a flowchart corresponding to that of Fig. 6, but for steps carried out be the RM node 200. Various steps will therefore by described more briefly, as they are covered in with reference to Fig. 6. In step 700, a capability exchange may take place. This may comprise obtaining UE capability information for the UE 10 in the RM node 200.

[0077] In step 602, the resource pool 50 may be configured. Where the resource pool 50 is configured according to specification, this obtainment may be preconfigured. Alternatively, the RM node 200 may configure the resource pool 50, optionally based on further information, such as current number of UEs / subnetworks in the coverage are / serving area of the RM node 200, UE capability of UEs in the area, traffic load, etc.

[0078] In step 704, the RM node may transmit an indication of the configuration of the resource pool 50. This may be obtained by messaging to any connected access node 121 A, 12 IB, or by NAS (Non-Access Stratum) signaling to UEs in the area. In some examples, the RM node 200 may configure plural different resource pools, and the UE 10 may be informed which resource pool is applicable for that UE. In some examples, there is no separate indication of the configuration of the resource pool 50, wherein resources for use in a subnetwork may be requested without the requesting radio node 10, 121A knowing how the resource pool 50 is configured.

[0079] In step 706, the RM node sense obtain a message indicative of sensing of the resources 51 of the resource pool. This message may indicate which resource are available within the resource pool 50, in the vicinity of the sensing radio node 10, 121A. This reporting may take place in a scheduled fashion, or when the sensing indicates altered availability in the resource pool 50, or when resources are requested.

[0080] In step 708, a request message for resources 51 of the resource pool 50 is received. The request message may originate from the UE 10, or from its serving access node 121 A, or from an application executed by the UE 10. As noted under step 706, the request message may comprise, or be combined with, a report indicative of resource availability based on sensing. In some examples, the request message may be obtained from an access node 121A and may identify a request for indication of available resource. Such available resources may be determined in the RM node 200 based on a current booking table, and possibly in combination with reported sensing 706 on resources which are not booked. In this context, the indication of sensing 706 may be comprised in the request message. In some examples, step 708 comprises receiving a request message associated with resources 51 of the resource pool 50, received from the access node 121A, which message comprises a request for an indication of available resources within the resource pool 50. In step 710, the RM node may allocate resources based on the received request message 708, by booking available resources 51. In an example where step 708 comprises receiving a request message associated with resources 51 of the resource pool 50, step 710 may comprise updating a booking table with information, obtained from the access node 121A, or resources allocated (and optionally scheduled) by the access node 121A.

[0081] In step 712, the RM node 20 may transmit a message indicative of the allocation carried out in step 710. Specifically, those allocated resources are usable for scheduling by the UE 10 in a subnetwork of UEs. Where the UE 10 sends the message received in step 708, the access nodes 121A, 121B having coverage in the area served by the RM node 200 may further receive a message indicative of these allocated resources.

[0082] In examples where step 708 comprises receiving a request for an indication of available resources within the resource pool 50 from the access node 121 A, step 712 need not be used.

[0083] In one example, the proposed solution operates according to an adapted version of SL Mode 1, where the access node 121A (gNB) checks 708 resource availability with the RM 200, and allocates (and optionally schedules) the resources based on obtained availability. The resources 51 of the resource pool 50 may in various examples be same as or similar to time-fq SL resources defined in SL pool. In this context, the access node 121 A may act upon a request 606 from the UE 10 and obtain / receive information from the RM node 200 indicative of available resources in the resource pool 50. The access node 121 A may further allocate available resources 51 to the UE 10. A message indicative of the allocation of resources is then transmitted for receipt 608 in the UE 10, and a booking table in the RM node 200 is updated accordingly. Allocation of resources may be carried out based on obtained 600 UE capability.

[0084] In another example, the proposed solution operates according to an adapted version of SL Mode 2, where a radio node (UE 10 or its serving access node 121A) requests resources of a semi static resource pool 50 from the RM 200. Instead of doing sensing according to legacy LBT, a set of resources are allocated for the UE 10, and the UE 10 is free to schedule those allocated resources for communication in a subnetwork 300, possibly with certain restrictions in time and / or power. In this context, sensing 604 may rather be carried out prior to (and for the purpose of) allocation of resources 51 for a subnetwork to be set up by the UE 10. Step 610 may in such examples be carried out by the UE 10, acting as group head UE for a subnetwork 300, wherein the UE 10 schedules data communication within the subnetwork.

[0085] Fig. 8 visualizes various features and examples of the proposed solution in a signaling diagram. Herein, various actions are shown which are taken with respect to the UE 10 in the context of a group head of a subnetwork 300, which further includes at least UE 20. Moreover, actions taken with respect to the access node 121A and the RM 200 are shown. These actions are discussed below, where applicable with reference to the steps discussed in conjunction with Figs 6 and 7. Various aspects will be described as method steps. However, it shall be noted that with regard to the RM node 200, the logic circuitry 210 may be configured to carry out the related steps; with regard to the access node 121 A, the logic circuitry 310 may be configured to carry out the related steps; with regard to the UE 10, the logic circuitry 410 may be configured to carry out the related steps.

[0086] 800 indicates capability exchange, as described with reference to steps 600 and 700. A subnetwork group head such as UE 10 may in this context exchange capabilities and basic configuration with the core network 110A and / or with the RM 200, over the Ran 120A. This may be carried out at any time but may in various examples in conjunction with a request for resources 606 (810).

[0087] 802 indicates configuration, by the RM node 200, of a pool of radio resources 50 configured for spectrum sharing, for use in subnetworks of UEs, corresponding to 702.

[0088] 804 indicates a configuration message, wherein information indicative of the configuration of the pool 50 of radio resources is transmitted. This may serve to inform the RAN 120A (including access node 121A) of the resource pool configuration, and UEs in the area covered by the RM node 200. Informing UEs may be executed by system information transmitted by the RAN 120A.

[0089] 806 and 808 both indicate sensing of the resources 51 of the resource pool 50, in the UE 10 and the access node 121A, respectively, and reporting 807, 809 of obtained sensing. In some examples, sensing 806, 808 and reporting 807, 809 to the RM node 200 may e.g., be carried out on request by the RM node 200, or be pre-configuration according to some scheme, or upon requesting resources from the resource pool 50. In some examples, only the UE 10 which is to make use of the requested resources will sense 806 the resources of the resource pool 50, to identify and report 807 available resources. In some examples, reporting 807 of sensing from the UE 10 is carried out over the RAN 120A, even though this is not indicated in the drawing. The RM node 200 thus obtains a message indicative of available resources in the pool of radio resources based on sensing of the resources. In some examples, the RM node 200 may update a booking table associated with the resource pool 50 to indicate available resources for a certain access node 121A or a certain UE 10 (or its subnetwork), or for a certain geographical area related to the radio node 121 A or 10 which reports the sensing. The booking table may be stored in memory storage 212 of the RM node 200.

[0090] 810 indicates that the UE 10 transmits a request message to obtain allocation of resources from the RM node 200 within the resource pool 50, either transparently for the RAN 120A or non-transparently via the access node 121A as indicated by 811. Results of sensing 806 may be comprised in the request message, or be transmitted 807, 809 in conjunction with the request message. In some examples, the request 810 is transmitted to the access node 121A, which conveys it to the RM node 200.

[0091] 811 indicates that the access node 121 A may convey the request message with a query for available resources within the resource pool 50 to the RM node 200. Obtained results of sensing 806, 808 may be comprised, or transmitted 807, 809 in conjunction with conveying the request message.

[0092] 812 indicates resource availability check at the RM node 200 and configuration of resource allocation for the requesting UE 10. This corresponds to steps 708 and 710.

[0093] 813 indicates a request reply message, from the RM node 200 to the access node 121 A, which may indicate resources allocated to the UE 10, or indicate available resources in the resource pool 50, for the access node 121A to use for allocating resources to the UE 10.

[0094] 814 indicates transmission of an allocation message to the requesting UE 10, indicative of the allocation of resources. In some examples, the allocation of resources is carried out and booked by the RM node 200. In other examples, the resource availability check 812 comprises notifying 813 the access node 121 A of available resources, wherein the access node 121A makes the allocation of resources for the UE 10 based on inter alia the reported availability. In such an example, the access node may inform 815 the RM node 200 of the allocation made, wherein the RM node 200 may update the booking table associated with the resource pool 50. The allocation message may serve to configure the UE 10, as a group head UE of the subnetwork, with scheduling right of allocated resources in said subnetwork. At 816, the UEs of a subnetwork are configured, i.e., resources in time and frequency for use in data communication within the subnetwork are conveyed to the UEs of the subnetwork.

[0095] 818 indicates scheduling, by the requesting UE 10, of the allocated resources for communication in the subnetwork, such as between various UEs of a common vehicle. The scheduling includes communication with the subnetwork UEs according to the scheduling. This step may be seen as a modified version of SL Mode 1, where the scheduling is carried out by the UE 10, as group head UE of the subnetwork. In an alternative example, step 818 is absent, and an LBT mechanism is instead used within the subnetwork, which may be seen as a modified version of SL Mode 2.

[0096] At 820, data exchange within the subnetwork takes place according to the scheduling by the UE 10.

[0097] According to various aspects, the proposed solution provides mechanisms similar to a hybrid version of SL modes 1 and 2. Specifically, the UE 10 is assigned, temporarily, with resources from a resource pool 50 for spectrum sharing, whereas the UE 10 is granted the right to handle those resources that are reserved for it, such as for subnetwork communication.

[0098] The UE 10 and / or the access node 121A may sense 806, 808 the resource pool 50 to identify available resources, based on which allocation of resources to the UE 10 is carried out.

[0099] The RM node 200 may be set up in agreement with operators, to define specific resource pools to be used for subnetworks. The RM node 200 may thus be connected to serve a plurality of radio networks which may have at least partly overlapping coverage areas. The RM node may be configured for spectrum sharing both for national and international roaming, and for handling participants in subnetwork belonging to different operators.

[0100] According to some examples, the proposed solution involves a method carried out by the UE 10, comprising one or more of the following steps:

[0101] Receive 804, from the RM node 200, information indicative of configuration of the resource pool 50. The resource pool may be configured within a limited frequency portion of a system bandwidth of the wireless network and may be configured within a reoccurring time duration.

[0102] Sense 806 resources within the pool of radio resources. Transmit 807, 810, for receipt in the RM node 200, a message indicative of the sensing in the pool of radio resources, which may indicate available resources.

[0103] Transmit 810 a request message to obtain allocation of resources within the resource pool 50 from the RM node 200. The request may be sent to the RM node 200 via the access node 121A, or as a request to the access node 121A.

[0104] Receive 814, from the RM node 200 or the access node 121 A, a message indicative of allocation to the UE 10 of resources from the resource pool 50 configured for spectrum sharing. The message indicative of allocation may be indicative of temporary grant to schedule resources during a restricted time and / or a maximum transmit power within the allocated resources. The allocation of resources may be received from the access node 121A, which has configured the allocation based on a response 813 to an availability query 811 to the RM node 200.

[0105] Configure 816 further UEs in a subnetwork in accordance with the obtained allocation of resources.

[0106] Schedule 818 radio resources selected from the allocated resources to further UEs in a subnetwork.

[0107] According to some examples, the proposed solution involves a method carried out by the access node 121A, comprising one or more of the following steps:

[0108] Receive 804, from the RM node 200, information indicative of configuration of the resource pool 50. The resource pool may be configured within a limited frequency portion of a system bandwidth of the wireless network and may be configured within a reoccurring time duration.

[0109] Transmit 809, 811, for receipt in the RM node 200, a message indicative of sensing in the pool of radio resources, which may indicate available resources.

[0110] Transmit 811, to the RM node 200, a request message associated with resources within the pool of radio resources. The request message 811 may originate from or be based on a request message from the UE 10 and may include a query for available resources within the resource pool 50.

[0111] Receive 813 a request reply message from the RM node 200, which may indicate resources allocated to the UE 10, or indicate available resources in the resource pool 50, for the access node 121A to use for allocating resources to the UE 10.

[0112] Transmit 814, to the UE 10, a message indicative of allocation of resources from the resource pool 50 configured for spectrum sharing. The message indicative of allocation may be indicative of temporary grant to schedule resources during a restricted time.

[0113] The message indicative of allocation may further be indicative of a maximum transmit power within the allocated resources. Resource allocation may in this context be dependent on output power expected in the subnetwork, and possibly obtained location of the UE 10, wherein resources may be reused for group s / subnetworks that are not in close vicinity. For this purpose, a measure of location of the UE 10 may be obtained in the access node 121A and / or the RM node 200, from the UE 10 itself (e.g., in the request message 814) or by network positioning carried out in the RAN 120A, or other sources such as a Location Management Function (LMF) in the CN 110A. Since the output power is likely much lower for a subnetwork, e.g., close to 0 dBm with a coverage of 10th of meters, the interference from the subnetwork would be limited, and resources could be reused multiple times separated by location (spatial separation).

[0114] Transmit 815, to the RM node 200, a message informing the RM node 200 of configuration of resources allocated by the access node 121A to the UE 10, such as an indication of resources and duration of the allocation.

[0115] According to some examples, the proposed solution involves a method carried out by the RM node 200, comprising one or more of the following steps:

[0116] Configure 802 a resource pool 50 of radio resources configured for spectrum sharing.

[0117] Transmit 804 information indicative of the configuration of the resource pool 50. The resource pool may be configured within a limited frequency portion of a system bandwidth of the wireless network and may be configured within a reoccurring time portion.

[0118] Obtain 807, 809 a message indicative of sensing in the pool of radio resources, which may indicate available resources.

[0119] Receive 810, 811 a request message associated with resources within the pool of radio resources. The request message 811 may originate from the UE 10 or the access node 121A and may include a query for available resources within the resource pool 50.

[0120] Check availability 812 among the resources in the resource pool 50, which may involve accessing a look-up booking table.

[0121] Transmit 813 a request reply message to the access node 121 A, or by NAS to the UE 10. The reply message may indicate resources allocated to the UE 10, or indicate available resources in the resource pool 50 for the access node 121A to use for allocating resources to the UE 10.

[0122] Receive 815, from the access node 121 A, a message informing the RM node 200 of configuration of resources allocated by the access node 121A to the UE 10, such as an indication of resources and duration of the allocation. This information may be used for updating the booking table in the RM node 200.

[0123] Based on the proposed solution, after a subnetwork (or subgroup) has been allocated resources, the subgroup is free to use the resources under given configuration and time. The resources can be scheduled by the UE 10, or other UE of the subgroup, acting as group head in a similar way as the access node 121A (gNB) would do in case of SL Mode 1 operation, but contrary to Mode 1 operation it is the subgroup / subnetwork head that is granted the right to schedule the allocated resources.

[0124] The resources to be used by the subgroup could potentially also be based on SL Mode 2 mechanism, but instead of performing sensing and resource allocation, resources from the resource pool 50 (which may be a pool within legacy SL resource pool) is dedicated to the subgroup only.

[0125] In this context, the proposed solution provides a mechanism for “Rented Resources”, where allocated resources are temporarily rented. Actual usage of the allocated resources is up to the user (UE 10), but they are guaranteed to be available to the UE 10 (and its subgroup, where applicable) whenever needed during a temporary period of time. Like borrowing a book at the library, the UE 10 may transmit a message to the access node 121A, or the RM node 200 if the resources are not needed anymore, prior to expiry of the temporary period of the resource allocation.

[0126] Various aspects and features of the proposed solution have been outlined in the foregoing, with reference to the drawings. Additionally, the proposed solution may be configured according to any of the items listed below.

[0127] Item 1. A radio node (10) of a wireless network, comprising: a wireless transceiver (413); logic circuitry (410) configured to: receive (814) a message indicative of allocation of resources from a pool of radio resources configured by a resource management node for spectrum sharing, wherein the allocated resources are usable for scheduling in a subnetwork of user equipment, UE. Item 2. The radio node of item 1, wherein the logic circuitry is configured to: transmit (810) a request message associated with resources within the pool of radio resources, wherein the message indicative of allocation is received in response to the request message.

[0128] Item 3. The radio node of item 1 or 2, wherein the message indicative of allocation is indicative of temporary grant to schedule resources during a restricted time.

[0129] Item 4. The radio node of any preceding item, wherein the message indicative of allocation is indicative of a maximum transmit power within the allocated resources.

[0130] Item 5. The radio node of any preceding item, wherein the logic circuitry is configured to: receive (804), from the resource management node, information indicative of configuration of the pool of radio resources.

[0131] Item 6. The radio node of any preceding item, wherein the pool of radio resources is configured within a limited frequency portion of a system bandwidth of the wireless network.

[0132] Item 7. The radio node of any preceding item, wherein the pool of radio resources is configured within a reoccurring time duration.

[0133] Item 8. The radio node of any preceding item, wherein the logic circuitry is configured to control the radio transceiver to: obtain sensing (806) of resources within the pool of radio resources; and transmit (807, 810) a message indicative of the sensing for receipt in the resource management node.

[0134] Item 9. The radio node of any preceding item, wherein the radio node is a UE (10) configured to operate as a group head UE of a subnetwork of UEs.

[0135] Item 10. The radio node of item 9, wherein the logic circuitry comprises: a scheduler, configured to schedule (818) radio resources selected from the allocated resources to further UEs in said subnetwork.

[0136] Item 11. The radio node of any of items 1-8, wherein the radio node is a base station (121 A) of the radio network, wherein the logic circuitry is arranged to: configure (814) a group head UE of the subnetwork with scheduling right of the allocated resources in said subnetwork. Item 12. The radio node of item 11, wherein the message indicative of allocation comprises an indication of available resources within the pool of radio resources, and wherein the logic circuitry is further configured to: allocate (814) resources to a UE, selected from the indication of available resources.

[0137] Item 13. A resource management node (200) connected to a wireless network, comprising: logic circuitry configured to: receive (811) a request message associated with resources within a pool of radio resources configured for spectrum sharing; transmit (813), to a radio node of a wireless network, a message indicative of allocation of resources from the pool of radio resources, available for configuration of a group head UE with scheduling right in a subnetwork.

[0138] Item 14. The resource management node of item 13, wherein the logic circuitry is configured to: configure (802) the pool of radio resources configured for spectrum sharing.

[0139] Item 15. The resource management node of item 13 or 14, wherein the logic circuitry is configured to: transmit (804) information indicative of configuration of the pool of radio resources.

[0140] Item 16. The resource management node of any of items 13-15, wherein the request message comprises a request for resources.

[0141] Item 17. The resource management node of any of items 13-16, wherein the request is indicative of a query for available resources within the pool of radio resources.

[0142] Item 18. The resource management node of any of items 13-17, wherein the pool of radio resources is configured within a limited frequency portion of a system bandwidth of the wireless network.

[0143] Item 19. The resource management node of any of items 13-18, wherein the pool of radio resources is configured within a reoccurring time duration.

[0144] Item 20. The resource management node of any of items 13-19, wherein the message indicative of allocation is indicative of temporary grant to schedule resources during a restricted time. Item 21. The resource management node of any of items 13-20, wherein the message indicative of allocation is indicative of a maximum transmit power within the allocated resources.

[0145] Item 22. The resource management node of any of items 13-21, wherein the logic circuitry is configured to: obtain (807, 809, 811) a message indicative of available resources in the pool of radio resources based on sensing of the resources.

[0146] Item 23. The resource management node of any of items 13-22, further comprising: memory storage (212) configured to store a booking table indicative of resources allocated to UE subgroups.

[0147] Item 24. The resource management node of any of items 13-23, further comprising: a network interface (213) connected to serve a plurality of radio networks with overlapping coverage areas.

Claims

CLAIMS1. A radio node (10) of a wireless network, comprising: a wireless transceiver (413); logic circuitry (410) configured to: receive (814) a message indicative of allocation of resources from a pool of radio resources configured by a resource management node for spectrum sharing, wherein the allocated resources are usable for scheduling in a subnetwork of user equipment, UE.

2. The radio node of claim 1, wherein the logic circuitry is configured to: transmit (810) a request message associated with resources within the pool of radio resources, wherein the message indicative of allocation is received in response to the request message.

3. The radio node of claim 1 or 2, wherein the message indicative of allocation is indicative of temporary grant to schedule resources during a restricted time.

4. The radio node of any preceding claim, wherein the message indicative of allocation is indicative of a maximum transmit power within the allocated resources.

5. The radio node of any preceding claim, wherein the logic circuitry is configured to: receive (804), from the resource management node, information indicative of configuration of the pool of radio resources.

6. The radio node of any preceding claim, wherein the pool of radio resources is configured within a limited frequency portion of a system bandwidth of the wireless network.

7. The radio node of any preceding claim, wherein the pool of radio resources is configured within a reoccurring time duration.

8. The radio node of any preceding claim, wherein the logic circuitry is configured to control the radio transceiver to: obtain sensing (806) of resources within the pool of radio resources; and transmit (807, 810) a message indicative of the sensing for receipt in the resource management node.

9. The radio node of any preceding claim, wherein the radio node is a UE (10) configured to operate as a group head UE of a subnetwork of UEs.

10. The radio node of claim 9, wherein the logic circuitry comprises: a scheduler, configured to schedule (818) radio resources selected from the allocated resources to further UEs in said subnetwork.

11. The radio node of any of claims 1-8, wherein the radio node is a base station (121 A) of the radio network, wherein the logic circuitry is arranged to: configure (814) a group head UE of the subnetwork with scheduling right of the allocated resources in said subnetwork.

12. The radio node of claim 11, wherein the message indicative of allocation comprises an indication of available resources within the pool of radio resources, and wherein the logic circuitry is further configured to: allocate (814) resources to a UE, selected from the indication of available resources.

13. A resource management node (200) connected to a wireless network, comprising: logic circuitry configured to: receive (811) a request message associated with resources within a pool of radio resources configured for spectrum sharing; transmit (813), to a radio node of a wireless network, a message indicative of allocation of resources from the pool of radio resources, available for configuration of a group head UE with scheduling right in a subnetwork.

14. The resource management node of claim 13, wherein the logic circuitry is configured to: configure (802) the pool of radio resources configured for spectrum sharing.

15. The resource management node of claim 13 or 14, wherein the logic circuitry is configured to: transmit (804) information indicative of configuration of the pool of radio resources.

16. The resource management node of any of claims 13-15, wherein the request message comprises a request for resources.

17. The resource management node of any of claims 13-16, wherein the request is indicative of a query for available resources within the pool of radio resources.

18. The resource management node of any of claims 13-17, wherein the pool of radio resources is configured within a limited frequency portion of a system bandwidth of the wireless network.

19. The resource management node of any of claims 13-18, wherein the pool of radio resources is configured within a reoccurring time duration.

20. The resource management node of any of claims 13-19, wherein the message indicative of allocation is indicative of temporary grant to schedule resources during a restricted time.

21. The resource management node of any of claims 13-20, wherein the message indicative of allocation is indicative of a maximum transmit power within the allocated resources.

22. The resource management node of any of claims 13-21, wherein the logic circuitry is configured to:obtain (807, 809, 811) a message indicative of available resources in the pool of radio resources based on sensing of the resources.

23. The resource management node of any of claims 13-22, further comprising: memory storage (212) configured to store a booking table indicative of resources allocated to UE subgroups.

24. The resource management node of any of claims 13-23, further comprising: a network interface (213) connected to serve a plurality of radio networks with overlapping coverage areas.

Images