Apparatus and method 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 a resource within a pool of radio resources configured for spectrum sharing by a resource management node; in response to the request message, a message is received (814) indicating an allocation of resources from a pool of radio resources, where the allocated resources are available for scheduling in a sub-network of a user equipment (UE).

Description

Technical Field

[0001] This disclosure relates to the field of wireless communications, and more specifically to the task of spectrum sharing. The proposed solutions are associated with devices that interact to provide a flexible mechanism for sharing resources in a wireless system to achieve efficient use of available spectrum. Background Technology

[0002] In wireless communication, wireless channels are used to transmit information and data between different radio nodes that act as transmitters and receivers using electromagnetic wave signals. Wireless communication has been in operation for decades and involves radio access networks (RANs), which use an air interface to communicate wirelessly with various devices (often referred to as user equipment (UEs) in the 3GPP framework). The RAN connects to a backbone network called the core network (CN), which connects to other networks such as the Internet.

[0003] Spectrum is a scarce resource in wireless communications. To this end, several attempts have been made to achieve the rational sharing of available spectrum. Different methods exist for spectrum sharing, such as geographical separation, time-based (TDD) sharing, underlying layer differentiation, power and bandwidth differences, and cooperation.

[0004] Traditional high-level sharing involves multiple operators from different countries purchasing a portion of available and defined spectrum across the country and essentially covering the area with their RAN, for example, using frequency reuse patterns to avoid interference between cells.

[0005] In the United States, an entity known as CBRS (Citizens Broadband Radio Service) defines a mechanism in which spectrum, when not in use, can be indicated in a database and requested by other users who are not originally part of the licensed spectrum.

[0006] CBRS therefore 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 interfering with each other. This sharing is achieved through a three-tiered approach based on existing users accessing Priority Access License (PAL) holders and General Authorized Access (GAA) users, with the last tier open to unlicensed users, similar to how Wi-Fi operates. GAA users can access the spectrum as long as they do not cause harmful interference to existing users or PAL users.

[0007] However, the spectrum sharing features in CBRS, or in systems like TV whitespace (TVWS), are rather static. Therefore, there are challenges in implementing faster and more dynamic spectrum (re)allocation mechanisms, where timing times drop to less than one second not only within carrier or private networks, but also between them. Summary of the Invention

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

[0009] The proposed solution relates to the implementation of a resource management node configured to manage resource sharing and optionally also handle billing for reserved and used resources. The resource management node can be associated with a geographic region where two base stations from different operators have overlapping coverage. The resource sharing operated by the resource management node can also be used for subnetworks, such as roaming mobile vehicle subnetworks.

[0010] According to a first aspect, a radio node for a wireless network is provided, including a radio transceiver and logic circuitry configured to receive a message indicating the allocation of resources from a radio resource pool configured for spectrum sharing by a resource management node, wherein the allocated resources can be used for scheduling within a subnetwork of a user equipment (UE). In various examples, this mechanism may be illustrated in a UE acting as a radio node, and in other examples in a base station acting as a radio node.

[0011] According to a second aspect, a resource management node is provided, connected to a wireless network, and including logic circuitry configured to receive a request message associated with resources within a radio resource pool configured for spectrum sharing; and to send a message to a radio node of the wireless network instructing the allocation of resources from the radio resource pool, the resources of which can be used to configure scheduling rights for a group head UE in a sub-network.

[0012] The proposed solution provides a mechanism for temporarily allocating resources to a UE, which can then schedule these resources for use in a sub-network. This enables a dynamic approach to sharing spectrum resources. Attached Figure Description

[0013] Various examples will be described with reference to the accompanying drawings, in which: Figure 1 A radio network with resource management nodes is schematically illustrated as an example of the proposed solution. Figure 2The functional elements of a resource management node are schematically illustrated according to various examples of the proposed solution; Figure 3 The functional elements of a radio node in the form of an access node, configured according to various examples of the proposed solution, are schematically shown. Figure 4 The functional elements of a radio node in the form of a UE, configured according to various examples of the proposed solution, are schematically illustrated. Figure 5A An example of the timing of a recurring pool of radio resources is shown, where spectrum can be shared among users; Figure 5B schematically illustrates the resource gradient of a radio resource pool and an example of the allocation of different parts of the pool to different sub-networks. Figure 6 A flowchart illustrating methods executed in a radio node according to various examples of the proposed solution is shown; Figure 7 Flowcharts illustrating methods executed in a resource management node according to various examples of the proposed solution are shown; and Figure 8 Signaling diagrams are provided to illustrate the various features of the proposed solution and alternatives. Detailed Implementation

[0014] In the following description, details relating to various examples are set forth herein for purposes of explanation and not limitation. However, it will be apparent to those skilled in the art that this disclosure may be practiced in other examples departing from these specific details. In some instances, detailed descriptions of well-known apparatuses, circuits, and methods have been omitted so as not to obscure the description of this disclosure with unnecessary detail. The functionality of various elements comprising functional blocks (including, but not limited to, those marked or described as “computer,” “processor,” or “controller”) may be provided using hardware such as circuit hardware and / or hardware capable of executing software stored on a computer-readable medium in the form of coded instructions. Thus, such functionality and illustrated functional blocks will be understood as hardware-implemented and / or computer-implemented, and therefore machine-implemented. In terms of hardware implementation, functional blocks may include or comprise, but are not limited to, digital signal processor (DSP) hardware, reduced instruction set processors, hardware (e.g., digital or analog) circuitry (including, but not limited to, application-specific integrated circuits (ASICs)), and (where appropriate) state machines capable of performing such functionality. In terms of computer implementation, a computer is generally understood to include one or more processors or one or more controllers, and the terms computer, processor, and controller may be used interchangeably herein. When provided by a computer, processor, or controller, the functionality may be provided by a single dedicated computer, processor, or controller, by a single shared computer, processor, or controller, or by multiple separate computers, processors, or controllers (some of which may be shared or distributed). Furthermore, the use of the terms "processor" or "controller" should also be interpreted to refer to other hardware capable of performing such functionality and / or executing software, such as the example hardware described above.

[0015] The accompanying figures provide performance graphs and are also considered schematic, wherein the representations and elements shown in the figures are not necessarily shown to scale. Rather, various elements are shown such that their function and general purpose will be apparent to those skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the figures or described herein may also be achieved through indirect connections or couplings. Coupling between components may also be established via wireless connections. Functional blocks may be implemented in hardware, firmware, software, or a combination thereof.

[0016] Figure 1A wireless communication scenario is schematically illustrated, providing an example of a scenario in which the solution presented herein can be incorporated. Wireless network 100A includes access network 120A, such as a 5G NR access network (Radio Access Network - RAN 120A). Access network 120A may include multiple access nodes or base stations, with access node 121A indicated, configured to provide a radio interface for communication with a radio station (UE) via an air interface. For NR implementations, the access node may be referred to as a gNB. Each access node includes a transmit and receive point (TRP), which corresponds to the antenna array of the respective access node. Wireless network 100A also includes a core network (CN) 110A to which access network 120A is connected. Core network 110A is further connected to other communication networks, such as the Internet.

[0017] In the context of the proposed solution, there may be a second wireless network 100B having a RAN 120B including an access node 121B and a CN 110B connected to the RAN 120B.

[0018] UE 10 is shown, which may belong to one of wireless networks 100A and 100B, or may be in a roaming state. Other UEs, such as the second UE 20, are also indicated as part of subnetwork 300, as will be further outlined below. Each UE can be any device operable to wirelessly communicate with network 100A via base station 121A, such as a mobile phone, computer, tablet, machine-to-machine (M2M) device, IoT (Internet of Things) device, vehicle device, or other device.

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

[0020] Figure 2 The resource management node, abbreviated as RM node 200, is schematically shown. RM node 200 includes logic circuitry 210, which is configured to perform or assist in the placement / location of UEs in the wireless network 200.

[0021] Logic circuitry 210 may include processing device 211, which includes one or more processors, microprocessors, data processors, coprocessors, 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) or a combination of hardware and software (e.g., a system-on-a-chip (SoC), an application-specific integrated circuit (ASIC), etc.). Processing device 211 may be configured to perform one or more operations based on an operating system and / or various applications or programs.

[0022] Logic circuit 210 may also include storage device 212, which may include one or more memories and / or one or more other types of storage media. For example, storage device 212 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or some other type of memory. Storage device 212 may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.). Storage device 212 is configured to store computer program code executable by processing device 211, wherein logic circuit 210 is configured to control RM node 200 to perform any method steps as provided herein. Software defined by the computer program code may include applications or programs that provide functionality and / or procedures. Software may include device firmware, operating system (OS), or various applications executable in logic circuit 210. In some examples, RM node 200 may be implemented at least partially by computer code residing in the cloud.

[0023] RM node 200 also includes a network (NW) interface 213 for connecting to wireless networks such as networks 100A and 100B. In some examples, RM node 120 may belong to and form part of wireless network 100A, and optionally connect to network 100B via interface 213. In other examples, RM node 200 is an edge device not bound to any single network or operator. In such examples, the NW interface may be communicatively directly connected to access nodes (e.g., 121A and 121B) of one or more wireless networks, such as... Figure 1 exemplified in .

[0024] Figure 3 A radio node in the form of access node 121 is schematically shown, which can be as follows: Figure 1Either access node 121A or 121B is illustrated herein. Radio node 121 can be configured to perform various method steps as outlined herein. In various examples, access node 121 is a radio base station for operating in a radio communication network 100A to serve one or more radio UEs (such as UE 10).

[0025] Access node 121 may include a wireless transceiver 313, such as a wireless transceiver for communicating with other entities (such as UE 10) of the radio communication network 100. Therefore, transceiver 313 may include a radio receiver and a transmitter for communicating via at least an air interface.

[0026] Access node 121 may also include or be connected to antenna 314, which may include multiple antennas (antenna elements). Antenna 314 is connected to transceiver 313.

[0027] Access node 121 also includes logic circuitry 310 configured to control access node 121 to communicate with wireless devices such as UE 10 over a physical channel via wireless transceiver 313.

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

[0029] Logic circuitry 310 may also include storage device 312, which may include one or more memories and / or one or more other types of storage media. For example, storage device 312 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or some other type of memory. Storage device 312 may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.). Storage device 312 is configured to store computer program code executable by processing device 311, wherein logic circuitry 310 is configured to control access node 121 to perform any method steps as provided herein. Software defined by the computer program code may include applications or programs that provide functionality and / or procedures. Software may include device firmware, operating system (OS), or various applications executable in logic circuitry 310.

[0030] Access node 121 may also include interface 315 configured to communicate with the core network.

[0031] Figure 4 A radio node in the form of a wireless device, referred to as UE 10, is schematically shown. UE 10 can be configured to perform various methodological steps as outlined.

[0032] UE 10 may include a wireless transceiver 413, such as a wireless transceiver for communicating with other entities in the radio communication network 100 (such as access nodes of RAN 120A and 120B) and with other UEs in the subnetwork. Therefore, transceiver 413 may include a radio receiver and transmitter for communicating via at least an air interface. The transceiver may include a radio modem.

[0033] UE 10 may also include or be connected to antenna 414, which may include multiple antennas (antenna elements). Antenna 414 is connected to transceiver 413.

[0034] UE 10 also includes logic circuitry 410 configured to control UE 10 to communicate with other devices over a physical channel via radio transceiver 413. Logic circuitry 410 may implement a scheduler for scheduling data communication according to the solution proposed herein, and for configuring one or more other UEs to perform data communication according to the schedule.

[0035] The logic circuit 410 may include a processing device 411, which includes one or more processors, microprocessors, data processors, coprocessors, and / or some other type of component that interprets and / or executes instructions and / or data. The processing device 411 may be implemented as hardware (e.g., a microprocessor) or a combination of hardware and software (e.g., a system-on-a-chip (SoC), an application-specific integrated circuit (ASIC), etc.). The processing device 411 may be configured to perform one or more operations based on an operating system and / or various applications or programs.

[0036] Logic circuitry 410 may also include a storage device 412, which may include one or more memories and / or one or more other types of storage media. For example, storage device 412 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or some other type of memory. Storage device 412 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.). Storage device 412 is configured to store computer program code executable by processing device 411, wherein logic circuitry 410 is configured to control UE 10 to perform any method steps as provided herein. Software defined by the computer program code may include applications or programs that provide functionality and / or procedures. Software may include device firmware, an operating system (OS), or various applications executable in logic 410.

[0037] The proposed solution is configured to provide a mechanism for defining resources that can be shared between subnetworks, such as resource sharing between different operators and private networks in a public domain. RM node 200 provides a new entity and is preferably placed near the edge of the group of access nodes 121A and 121B. In various examples, RM node 200 is configured to serve access nodes and subnetworks belonging to different operators (wireless networks 100A and 100B), and can serve specific areas where access nodes 121A and 121B of different wireless networks have overlapping coverage (e.g., cell coverage). The proposed solution is configured to operate across cell boundaries and avoids interference between subnetworks not only handled by one operator, but also between different operators.

[0038] Figure 5A A semi-static configuration of radio resource pool 50, or simply resource pool 50, is illustrated by way of example. This resource pool can be configured by RM node 200. Resource pool 50 can be configured within a limited frequency portion of the system bandwidth of the wireless network. Resource pool 50 of radio resources can also be configured for durations such as semi-static or periodically recurring. In an alternative example, resource pool 50 occupies all time slots of a limited frequency. Radio nodes or applications can request and reserve resources in resource pool 50 from RM 200.

[0039] Figure 5B further illustrates an example where resources 51 within resource pool 50, as shown in the time / frequency diagram of the reservation table configured by RM 200, are allocated to different UEs 52 and 53, or to different groups / sub-networks managed by UE 52 and the UE acting as the group head, respectively. In this context, UE 52 may be allocated resources for use by one sub-network, while UE 53 may be allocated resources for use by another sub-network.

[0040] Unlike CBRS, resource allocation is not provided for the entire frequency and a specific BW and over a longer time period as in the DSS database scenario. Instead, it is provided temporarily for shorter time periods (such as x seconds or minutes) and within the dynamically shared spectrum of resource pool 50. This provides greater flexibility in resource allocation and increases the opportunity to allocate resources to more UEs and subnetworks. Temporary allocations can be configured for a specific time frame or for the number of times resource pool 50 appears. Depending on resource requirements, resource pool 50 can be fully occupied by a single UE / subnetwork or as... Figure 5B The data shown is shared.

[0041] According to existing technology, UE 10 typically belongs to or is attached to a network. In the area covered by this network (e.g., 100A, which may partially co-locate with another network 100B), UE 10 can only use the resources of its own network (PLMN - Public Land Mobile Network) 100A. However, in the context of the proposed solution, a UE such as UE 10 can reside in its home PLMN 100A, but the resource management node 200 can configure a pool 50 and allocate resources 51 from that pool 50 to UE 10, for example, for UE 10 to use as a group head in a subnetwork, where the resources can belong to (be licensed to) any operator's network, such as 100B. Therefore, the RM node provides a mechanism for conveniently sharing licensed resources, even from different operator networks 100A and 100B, for use in a subnetwork.

[0042] In some examples, the proposed solution can reuse mechanisms configured for SL operation, as outlined in particular in 3GPP specifications 38.300, 38.331, and 38.212. Therefore, sidelinks (SLs) will be briefly discussed below.

[0043] For SL, direct communication between UEs is specified, in which a specific resource pool is defined, and the resources in the pool are allocated by the gNB (Mode 1) or can be handled autonomously by the UE using a sensing mechanism to avoid conflicts (Mode 2).

[0044] In summary, NR (New Radio) SL communication is designed to support V2X services via the UE-to-UE PC5 interface, but can also be used to support other services. The sidelink provides three types of transmission modes: 1. Broadcast: ○ Sending and receiving user traffic between UEs in SL.

[0045] 2. Multicast: ○ Sending and receiving user traffic between UEs belonging to groups in SL; ○ Supports SL HARQ (Hybrid Automatic Repeat Request) feedback.

[0046] 3. Unicast: ○ Supports one PC5-RRC (Radio Resource Control) connection between peer UEs; ○ Sending and receiving control information and user traffic between peer UEs; ○Supports SL HARQ feedback; ○Supports SL transmit power control; ○ Supports RLC AM (Radio Link Control Acknowledgment Mode); ○ Detect radio link faults in the PC5-RRC connection.

[0047] As mentioned above, there are two resource allocation modes in SL: Mode 1 and Mode 2.

[0048] In Mode 1 (Scheduled Resource Allocation), the UE needs to be in the RRC_CONNECTED state to send data, and it obtains resource allocation from the gNB because the RAN is responsible for scheduling transmission resources.

[0049] In Mode 2 (UE Autonomous Resource Selection), the UE can transmit data both within and outside coverage area. The UE autonomously selects transmission resources from a resource pool. The resource pool can be pre-configured or configured by the network.

[0050] Mode 2 uses the principles of unlicensed mode, including the LBT (Listen Before Talk) concept, where the Tx side performs sensing before transmission to detect if the channel is idle. The Tx UE senses the resource pool within a time period represented as the sensing window. Sensing includes Sidelink Control Information (SCI) decoding, where the first-phase SCI on the PSCCH (Physical Shared Control Channel) indicates the sub-channels and time slots the UE will use for future transmissions, and sidelink measurements, where the SL-RSRP (Reference Signal Received Power) is based on the DMRS (Demodulation Reference Signal) and corresponds to the SCI.

[0051] The sensing process is defined as decoding the SCI from other UEs or measuring the power of SL transmissions from other UEs. By decoding the SCIs from other UEs, the UE knows the resources planned for SL transmissions by other UEs and can treat these resources as unavailable during the resource selection process. The selection window is the time interval from which the UE selects SL resources for transmission. It begins after resource (re)selection is triggered (T1≥0) and ends at T2, bounded at least by the remaining PDB (Packet Delay Budget).

[0052] Regarding the traditional SL process briefly discussed above, various examples of the proposed solutions can partially utilize resource configuration for SL, where both Mode 1 and Mode 2 resource allocation methods are feasible, or as a hybrid version of both.

[0053] The proposed solution involves RM node 200, RAN 120A with access node 121A, and UE 10, which can be operated to establish subnetwork 300. However, it should be noted that, similarly, RAN 120B and its co-located access node 121B with access node 121A can perform sensing and request resources from RM node 200. In one aspect, operation according to the proposed solution can be performed by radio nodes such as access node 121A or UE 10. Reference will now be made to... Figure 6 Describe some of these steps.

[0054] In step 600, capability exchange can be performed. This can follow a conventional process, where UE capabilities are typically exchanged with network 100A during registration. Alternatively or additionally, aspects of the UE capabilities can be reported later in another UL message. In the context of the proposed solution, UE capabilities can provide one or more of subnet information, such as subnet ID, maximum bit rate, maximum Tx power, frequency band and bandwidth used for subnet operation, etc. This capability information is transmitted to RM node 200.

[0055] In step 602, the configuration of resource pool 50 can be obtained. If resource pool 50 is configured according to a specification, this acquisition can be pre-configured in the program code of the radio node (i.e., in UE 10 and / or access node 121A). If resource pool 50 is configured on RM node 200, access node 121A can obtain the configuration via a message from RM node 200, and UE 10 can obtain the configuration via system information provided by its network 100A or via a separate message. In some examples, RM node 200 can configure multiple different resource pools and can notify UE 10 which resource pool is suitable for the UE.

[0056] In step 604, the radio node can sense resource 51 of resource pool 50. This can be performed by access node 121A, and specifically by UE 10, by sensing radio activity in resource 51. In some examples, UE 10 can report the results of the sensing for reception in RM node 200, indicating which resources within resource pool 50 are available. This reporting can be done in a scheduled manner, or when sensing indicates a change in availability in resource pool 50, or when resources are requested.

[0057] In step 606, a request message for resource 51 in resource pool 50 is sent. The request message may originate from UE 10, or from the serving access node 121A of the UE, or from an application executed by UE 10. As described below in step 604, the request message may include a report based on sensing indications of resource availability, or a combination thereof.

[0058] In some examples, step 608 includes the access node 121A sending a request message associated with resource 51 of resource pool 50, the message including a request for indication of available resources within resource pool 50.

[0059] In step 608, a message indicating the allocation of resources 51 within resource pool 50 may be received. Specifically, those allocated resources can be used by UE 10 for scheduling within the UE's subnetwork. If UE 10 requests 606 and receives the allocation of resources in 608, access nodes 121A and 121B, which have coverage in the area served by RM node 200, may also receive messages indicating these allocated resources.

[0060] In an example where the request message in step 606 includes a request for indication of available resources within resource pool 50, the message indicating the allocation of resource 51 within resource pool 50 may identify the available resources. In this example, the mechanism may further include step 609, where access node 121A allocates resources to the sub-network and optionally schedules resources based on the received indication of available resources. This step may also include sending information about the allocated resources to RM node 200 for updating the reservation table in RM node 200.

[0061] In step 610, the resources allocated to subnetwork 300 can be scheduled.

[0062] In step 612, resources scheduled by UE 10 can be used to exchange data between UEs in subnetwork 300.

[0063] Figure 7 It shows the relationship with Figure 6This is the flowchart corresponding to the previous one, but specifically for the steps performed by RM node 200. Therefore, the individual steps will be described more briefly, as they are referenced from... Figure 6 It is covered.

[0064] In step 700, capability exchange can be performed. This may include obtaining UE capability information of UE 10 in RM node 200.

[0065] In step 702, resource pool 50 can be configured. This acquisition can be pre-configured if resource pool 50 is configured according to specifications. Alternatively, RM node 200 can optionally configure resource pool 50 based on further information such as the current number of UEs / subnetworks in the coverage / service area of ​​RM node 200, the UE capabilities of the UEs in the area, traffic load, etc.

[0066] In step 704, the RM node may send an indication of the configuration of resource pool 50. This can be obtained by sending a message to any connected access nodes 121A, 121B or by sending NAS (Non-Access Stratum) signaling to the UE in the area. In some examples, RM node 200 may configure multiple different resource pools and may notify UE 10 which resource pool is suitable for that UE. In some examples, there is no separate indication of the configuration of resource pool 50, in which case resources for the subnetwork may be requested even if the requesting radio nodes 10, 121A do not know how resource pool 50 is configured.

[0067] In step 706, the RM node senses a message indicating resource 51 in the sensing resource pool. This message may indicate which resources are available in the vicinity of sensing radio nodes 10 and 121A within resource pool 50. This report may be sent in a scheduled manner, or when the sensing indicates a change in availability in resource pool 50, or when a resource is requested.

[0068] In step 708, a request message for resource 51 of resource pool 50 is received. The request message may originate from UE 10, or from the serving access node 121A of the UE, or from an application executed by UE 10. As described below in step 706, the request message may include a report based on sensing indications of resource availability, or a combination thereof. In some examples, the request message may be obtained from access node 121A and may identify a request for indications of available resources. Such available resources may be determined in RM node 200 based on the current reservation table and possibly in conjunction with reported sensing 706 regarding unreserved resources. In this context, the indication of sensing 706 may be included in the request message. In some examples, step 708 includes receiving a request message associated with resource 51 of resource pool 50 received from access node 121A, the message including a request for indications of available resources within resource pool 50.

[0069] In step 710, the RM node may allocate resources by reserving available resources 51 based on the received request message 708. In an example where step 708 includes receiving a request message associated with resource 51 of resource pool 50, step 710 may include updating the reservation table using information obtained from access node 121A or information about resources allocated (and optionally scheduled) by access node 121A.

[0070] In step 712, RM node 20 may send a message indicating the allocation performed in step 710. Specifically, those allocated resources can be used by UE 10 for scheduling within the UE's subnetwork. If UE 10 sends the message received in step 708, access nodes 121A and 121B, which are covered in the area served by RM node 200, may also receive messages indicating these allocated resources.

[0071] In the example where step 708 includes receiving a request from access node 121A for an indication of available resources within resource pool 50, step 712 is not required.

[0072] In one example, the proposed solution operates according to an adapted version of SL mode 1, where access node 121A (gNB) checks resource availability (708) with RM 200 and allocates (and optionally schedules) resources based on the obtained availability. In various examples, resource 51 of resource pool 50 may be the same as or similar to the time-frequency SL resources defined in the SL pool. In this context, access node 121A may respond to request (606) from UE 10 and obtain / receive information from RM node 200 indicating available resources in resource pool 50. Access node 121A may also allocate available resource 51 to UE 10. A message indicating the allocation of this resource is then sent to UE 10 for reception (608), and the reservation table in RM node 200 is updated accordingly. Resource allocation may be performed based on the obtained UE capability (600).

[0073] In another example, the proposed solution operates according to an adapted version of SL Mode 2, where the radio node (UE 10 or its serving access node 121A) requests resources from the semi-static resource pool 50 from RM 200. Instead of sensing according to conventional LBT, a set of resources is allocated to UE 10, and UE 10 is free to schedule those allocated resources for communication within subnetwork 300, possibly with some time and / or power limitations. In this context, sensing 604 can be performed before (and for the purpose of allocating) resources 51 to the subnetwork to be established by UE 10. In such an example, step 610 can be performed by UE 10, which acts as the group head UE of subnetwork 300, where UE 10 schedules data communication within the subnetwork.

[0074] Figure 8 Various features and examples of the proposed solution are visualized in the signaling diagram. Here, various actions taken by UE 10 in the context of the group header of subnetwork 300, which also includes at least UE 20, are shown. Furthermore, actions taken with regard to access nodes 121A and RM 200 are shown. These actions are discussed below, with reference to relevant diagrams where applicable. Figure 6 and Figure 7 The steps discussed will be described in terms of method steps. However, it should be noted that, with respect to RM node 200, logic circuit 210 can be configured to perform the relevant steps; with respect to access node 121A, logic circuit 310 can be configured to perform the relevant steps; and with respect to UE 10, logic circuit 410 can be configured to perform the relevant steps.

[0075] 800 indicates capability exchange, as described with reference to steps 600 and 700. In this context, a subnetwork group head such as UE 10 can exchange capabilities and basic configurations with the core network 110A and / or with the RM 200 via RAN 120A. This can be performed at any time, but in various examples it can be performed in conjunction with resource request 606 (810).

[0076] 802 indicates the configuration by RM node 200 of radio resource pool 50 for spectrum sharing for use in the UE's sub-network, corresponding to 702.

[0077] Message 804 indicates a configuration, in which information indicating the configuration of radio resource pool 50 is sent. This can be used to notify RAN 120A (including access node 121A) of the resource pool configuration and the UEs in the area covered by RM node 200. Notification to the UE can be performed via system information sent by RAN 120A.

[0078] 806 and 808 respectively indicate sensing of resource 51 in resource pool 50 in UE 10 and access node 121A, and reporting of the sensed resources obtained in 807 and 809. In some examples, sensing 806 and 808 and reporting 807 and 809 to RM node 200 may be performed, for example, in response to a request from RM node 200, or pre-configured according to some scheme, or performed when resources are requested from resource pool 50. In some examples, only UE 10, which will utilize the requested resources, senses the resources of resource pool 50 in 806 to identify and report 807 available resources. In some examples, reporting 807 of the sensed resources from UE 10 is performed via RAN 120A, even though this is not shown in the figures. RM node 200 thus obtains a message indicating available resources in the radio resource pool based on the sensing of resources. In some examples, RM node 200 may update a reservation table associated with resource pool 50 to indicate available resources for a particular access node 121A or a particular UE 10 (or its subnetwork) or for a particular geographic area associated with a reported sensing radio node 121A or 10. The reservation table may be stored in storage device 212 of RM node 200.

[0079] 810 instructs UE 10 to send a request message to obtain the allocation of resources within resource pool 50 from RM node 200, either transparently to RAN 120A or non-transparently via access node 121A as indicated in 811. The result of sensing 806 may be included in the request message or sent together with the request message in 807, 809. In some examples, request 810 is sent to access node 121A, which then forwards the request to RM node 200.

[0080] 811 instructs access node 121A to transmit a request message to RM node 200 containing a query for available resources within resource pool 50. The results of the sensing 806, 808 can be included or sent along with the request message 807, 809.

[0081] 812 instructs the RM node 200 to perform a resource availability check and configure the resource allocation for requesting UE 10. This corresponds to steps 708 and 710.

[0082] 813 indicates a request-response message from RM node 200 to access node 121A, which may indicate resources allocated to UE 10 or available resources in resource pool 50 for access node 121A to allocate resources to UE 10.

[0083] 814 instructs the sending of an allocation message to requesting UE 10, which indicates the allocation of resources. In some examples, resource allocation is performed and reserved by RM node 200. In other examples, resource availability check 812 includes notifying access node 121A of available resources 813, where access node 121A allocates resources to UE 10, particularly based on reported availability. In such an example, access node may notify RM node 200 of the allocation performed 815, where RM node 200 may update the reservation table associated with resource pool 50. The allocation message can be used to configure UE 10 as a group head UE of a subnetwork, which has scheduling rights over allocated resources in that subnetwork.

[0084] At point 816, the UE of the sub-network is configured, that is, the time and frequency resources used for data communication within the sub-network are transmitted to the UE of the sub-network.

[0085] Step 818 indicates the allocation of resources by requesting UE 10 for communication within the subnetwork (such as between various UEs in a public vehicle). Scheduling includes communicating with the subnetwork UEs according to this schedule. This step can be considered a modified version of SL Mode 1, where scheduling is performed by UE 10, which is the group head UE of the subnetwork. In an alternative example, step 818 is omitted, and instead, an LBT mechanism is used within the subnetwork, which can be considered a modified version of SL Mode 2.

[0086] At 820, data exchange within the subnetwork is performed according to the scheduling of UE 10.

[0087] Depending on the aspects, the proposed solution provides a mechanism similar to a hybrid version of SL modes 1 and 2. Specifically, UE 10 is temporarily allocated resources from resource pool 50 for spectrum sharing, while UE 10 is granted the right to process those resources reserved for it (such as those used for sub-network communications).

[0088] UE 10 and / or access node 121A can sense resource pools 50 806 and 808 to identify available resources and perform resource allocation to UE 10 based on these available resources.

[0089] RM node 200 can be established through agreements with operators to define specific resource pools to be used for subnetworks. Therefore, RM node 200 can be connected to serve multiple radio networks that may have at least partially overlapping coverage areas. RM nodes can be configured for spectrum sharing for domestic and international roaming, as well as for handling participants in subnetworks belonging to different operators.

[0090] Based on some examples, the proposed solution involves a method performed by UE 10, including one or more of the following steps: Receive 804 information from RM node 200 indicating the configuration of resource pool 50. The resource pool can be configured within a limited frequency portion of the system bandwidth of the wireless network and can be configured for a recurring duration.

[0091] Sensing resources within the 806 radio resource pool.

[0092] Send messages 807 and 810 indicating the sensing in the radio resource pool for reception in RM node 200; these messages can indicate available resources.

[0093] Send an 810 request message to obtain the allocation of resources within resource pool 50 from RM node 200. This request can be sent to RM node 200 via access node 121A, or it can be sent as a request to access node 121A.

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

[0095] Configure other UEs in the 816 subnetwork based on the allocation of the acquired resources.

[0096] Radio resources selected from the allocated resources will be dispatched to other UEs in the subnetwork.

[0097] Based on some examples, the proposed solution involves a method performed by access node 121A, including one or more of the following steps: Receive information from RM node 200 regarding the configuration of resource pool 50, indicated by 804. The resource pool can be configured within a limited frequency portion of the system bandwidth of the wireless network and can be configured for a recurring duration.

[0098] Send messages 809 and 811 indicating sensing in the radio resource pool for reception in RM node 200; these messages can indicate available resources.

[0099] Send a request message 811 to RM node 200, which associates resources within the radio resource pool. The request message 811 may originate from or be based on a request message from UE 10, and may include a query for available resources within resource pool 50.

[0100] Receive Request Response Message 813 from RM Node 200. This Request Response Message may indicate the resources allocated to UE 10 or the available resources in resource pool 50 for access node 121A to allocate resources to UE 10.

[0101] The UE 10 sends an 814 message indicating the allocation of resources from resource pool 50, which is configured for spectrum sharing. The allocation message may indicate a temporary authorization to schedule resources during a limited time period.

[0102] The allocation message can also indicate the maximum transmit power within the allocated resources. In this context, resource allocation can depend on the expected output power in the subnetwork and the possible location of UE 10, where resources can be reused for groups / subnetworks that are not closely adjacent. For this purpose, the location of UE 10 can be measured in the access node 121A and / or RM node 200 from UE 10 itself (e.g., in request message 814) or by network location performed in RAN 120A, or by other sources such as the location management function (LMF) in CN 110A. Since the output power may be much lower for the subnetwork, e.g., close to 0 dBm, with a coverage range of tens of meters, interference from the subnetwork will be limited, and resources can be reused multiple times by location (spatial separation).

[0103] Send Message 815 to RM Node 200, which informs RM Node 200 of the configuration of resources allocated to UE 10 by Access Node 121A, such as the resources and an indication of the duration of the allocation.

[0104] Based on some examples, the proposed solution involves a method executed by RM node 200, including one or more of the following steps: Configure resource pool 50 for radio resources configured for spectrum sharing 802.

[0105] Send 804 information indicating the configuration of resource pool 50. The resource pool can be configured within a limited frequency portion of the system bandwidth of the wireless network, and can also be configured within a recurring time portion.

[0106] Obtain messages 807 and 809 indicating the sensing in the radio resource pool, which can indicate available resources.

[0107] Receive request messages 810 and 811 associated with resources in the radio resource pool. Request message 811 may originate from UE 10 or access node 121A and may include a query for available resources in resource pool 50.

[0108] Check the availability of resources in resource pool 50 (812), which may involve accessing and looking up the reservation table.

[0109] Send an 813 request response message to access node 121A or to UE 10 via NAS. The response message may indicate the resources allocated to UE 10, or indicate the available resources in resource pool 50 for access node 121A to allocate resources to UE 10.

[0110] Message 815 is received from Access Node 121A, which informs RM Node 200 of the configuration of resources allocated to UE10 by Access Node 121A, such as the resources and the duration of the allocation. This information can be used to update the reservation table in RM Node 200.

[0111] Based on the proposed solution, after resources have been allocated to a sub-network (or subgroup), the subgroup is free to use the resources under a given configuration and time. Resources can be scheduled by UE 10 or other UEs in the subgroup, which acts as the group head in a similar manner to what Access Node 121A (gNB) would do in SL Mode 1 operation, but instead of being the subgroup / sub-network head granted the right to schedule the allocated resources.

[0112] Resources to be used by a subgroup could potentially be based on the SL Mode 2 mechanism, but instead of performing sensing and resource allocation, resources from resource pool 50 (which could be a pool within a traditional SL resource pool) would be dedicated solely to that subgroup.

[0113] In this context, the proposed solution provides a "resource rental" mechanism in which allocated resources are temporarily rented. The actual use of the allocated resources depends on the user (UE 10), but it is guaranteed that these resources are available to UE 10 (and its subgroups, where applicable) whenever needed during the temporary period. Similar to borrowing books from a library, if the resources are no longer needed, UE 10 can send a message to access node 121A or RM node 200 before the expiration of the temporary resource allocation period.

[0114] The various aspects and features of the proposed solution have been outlined above with reference to the accompanying drawings. Furthermore, the proposed solution can be configured according to any of the items listed below.

[0115] Project 1. A radio node (10) for a wireless network, comprising: Wireless transceiver (413); The logic circuit (410) is configured as follows: Receive (814) a message indicating that resources are allocated from a radio resource pool configured for spectrum sharing by a resource management node, wherein the allocated resources can be used for scheduling in a sub-network of a user equipment (UE).

[0116] Project 2. Based on the radio node of Project 1, the logic circuit is configured as follows: Send (810) a request message associated with a resource in the radio resource pool, wherein a message indicating allocation is received in response to the request message.

[0117] Project 3. Based on the radio nodes of Project 1 or 2, wherein the message indicating allocation indicates a temporary authorization to schedule resources during a limited time period.

[0118] Project 4. According to any of the preceding projects, the radio node, wherein the message indicating allocation indicates the maximum transmit power within the allocated resources.

[0119] Project 5. Based on any of the aforementioned projects' radio nodes, wherein the logic circuitry is configured as follows: Receive (804) information from the resource management node indicating the configuration of the radio resource pool.

[0120] Project 6. A radio node according to any of the preceding projects, wherein the radio resource pool is configured within a limited frequency portion of the system bandwidth of the wireless network.

[0121] Project 7. According to any of the aforementioned projects, the radio resource pool is configured for a recurring duration.

[0122] Project 8. According to any of the preceding projects, a radio node wherein logic circuitry is configured to control the radio transceiver to: Acquire sensing of resources within the radio resource pool (806); and Send (807, 810) a sensing message for reception in the resource management node.

[0123] Item 9. A radio node according to any of the preceding items, wherein the radio node is a UE configured to operate as a group head UE of a sub-network of the UE (10).

[0124] Project 10. Based on the radio node of Project 9, the logic circuit includes: The scheduler is configured to schedule (818) radio resources selected from the allocated resources to another UE in the subnetwork.

[0125] Project 11. A radio node according to any one of Projects 1 to 8, wherein the radio node is a base station (121A) of a radio network, wherein the logic circuit is arranged as follows: Configure (814) the scheduling rights of the resources allocated in the subnetwork for the group head UE of the subnetwork.

[0126] Project 12. The radio node according to Project 11, wherein the message indicating allocation includes an indication of available resources within the radio resource pool, and wherein the logic circuitry is further configured to: The resource allocation (814) selected from the indication of available resources is given to the UE.

[0127] Item 13. A resource management node (200) connected to a wireless network, comprising: The logic circuit is configured as follows: Receive (811) a request message associated with resources within a radio resource pool configured for spectrum sharing; Send (813) a message to the radio node of the wireless network instructing the allocation of resources from a radio resource pool, the resources of which can be used to configure scheduling rights for the group head UE in the sub-network.

[0128] Project 14. Based on the resource management node of Project 13, the logic circuit is configured as follows: Configure the radio resource pool configured for spectrum sharing (802).

[0129] Project 15. Based on the resource management node of Project 13 or 14, the logic circuit is configured as follows: Send (804) information indicating the configuration of the radio resource pool.

[0130] Project 16. Based on any one of Projects 13 to 15, the resource management node, wherein the request message includes a request for resources.

[0131] Item 17. Based on any one of Items 13 to 16, the resource management node requests instructions for querying available resources within the radio resource pool.

[0132] Project 18. A resource management node according to any one of Projects 13 to 17, wherein the radio resource pool is configured within a limited frequency portion of the system bandwidth of the wireless network.

[0133] Project 19. Based on any of Projects 13 to 18, the resource management node, wherein the radio resource pool is configured for a recurring duration.

[0134] Item 20. Based on any one of Items 13 to 19, the resource management node, wherein the message indicating allocation indicates a temporary authorization to schedule resources during a limited time period.

[0135] Project 21. According to any one of Projects 13 to 20, the resource management node, wherein the message indicating allocation indicates the maximum transmission power within the allocated resource.

[0136] Project 22. Based on the resource management node of any one of Projects 13 to 21, the logic circuit is configured as follows: The information (807, 809, 811) is obtained based on the sensing of resources to indicate the available resources in the radio resource pool.

[0137] Project 23. Based on any one of the resource management nodes in Projects 13 to 22, further including: The storage device (212) is configured to store a reservation table indicating the resources allocated to the UE subgroup.

[0138] Project 24. Based on any one of the resource management nodes in Projects 13 to 23, further include: Network interface (213) connects to serve multiple radio networks with overlapping coverage areas.

Claims

1. A radio node (10) for a wireless network, comprising: Wireless transceiver (413); The logic circuit (410) is configured as follows: Receive (814) a message indicating that resources are allocated from a radio resource pool configured for spectrum sharing by a resource management node, wherein the allocated resources can be used for scheduling in a sub-network of a user equipment (UE).

2. The radio node according to claim 1, wherein, The logic circuit is configured as follows: Send (810) a request message associated with a resource in the radio resource pool, wherein the message indicating allocation is received in response to the request message.

3. The radio node according to claim 1 or 2, wherein, The message indicating the allocation indicates a temporary authorization to schedule resources during a limited time period.

4. The radio node according to any one of the preceding claims, wherein, The message indicating the allocation specifies the maximum transmission power within the allocated resources.

5. The radio node according to any one of the preceding claims, wherein, The logic circuit is configured as follows: Receive (804) information from the resource management node indicating the configuration of the radio resource pool.

6. The radio node according to any one of the preceding claims, wherein, The radio resource pool is configured within a limited frequency portion of the system bandwidth of the wireless network.

7. The radio node according to any one of the preceding claims, wherein, The radio resource pool is configured to recur for a duration.

8. The radio node according to any one of the preceding claims, wherein, The logic circuit is configured to control the wireless transceiver to: Acquire sensing of resources within the radio resource pool (806); and Send (807, 810) a message indicating the sensing to be received in the resource management node.

9. The radio node according to any one of the preceding claims, wherein, The radio node is a UE (10) configured to operate as a group head UE in a sub-network of the UE.

10. The radio node according to claim 9, wherein, The logic circuit includes: The scheduler is configured to schedule (818) radio resources selected from the allocated resources to another UE in the subnetwork.

11. The radio node according to any one of claims 1 to 8, wherein, The radio node is a base station (121A) of the radio network, wherein the logic circuit is arranged as follows: Configure (814) the scheduling rights of the resources allocated in the sub-network for the group head UE of the sub-network.

12. The radio node according to claim 11, wherein, The message indicating allocation includes an indication of available resources within the radio resource pool, and wherein the logic circuitry is further configured to: The resource allocation (814) selected from the indication of the available resources is given to the UE.

13. A resource management node (200) connected to a wireless network, comprising: The logic circuit is configured as follows: Receive (811) a request message associated with resources within a radio resource pool configured for spectrum sharing; Send (813) a message to the radio node of the wireless network instructing the allocation of resources from the radio resource pool, the resources of which can be used to configure scheduling rights for the group head UE in the sub-network.

14. The resource management node according to claim 13, wherein, The logic circuit is configured as follows: Configure the radio resource pool configured for spectrum sharing (802).

15. The resource management node according to claim 13 or 14, wherein, The logic circuit is configured as follows: Send (804) information indicating the configuration of the radio resource pool.

16. The resource management node according to any one of claims 13 to 15, wherein, The request message includes a request for resources.

17. The resource management node according to any one of claims 13 to 16, wherein, The request indicates a query for available resources within the radio resource pool.

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

19. The resource management node according to any one of claims 13 to 18, wherein, The radio resource pool is configured to recur for a duration.

20. The resource management node according to any one of claims 13 to 19, wherein, The message indicating the allocation indicates a temporary authorization to schedule resources during a limited time period.

21. The resource management node according to any one of claims 13 to 20, wherein, The message indicating the allocation specifies the maximum transmission power within the allocated resources.

22. The resource management node according to any one of claims 13 to 21, wherein, The logic circuit is configured as follows: Based on sensing of the resources, messages indicating available resources in the radio resource pool are acquired (807, 809, 811).

23. The resource management node according to any one of claims 13 to 22, further comprising: The storage device (212) is configured to store a reservation table indicating the resources allocated to the UE subgroup.

24. The resource management node according to any one of claims 13 to 23, further comprising: Network interface (213) connects to serve multiple radio networks with overlapping coverage areas.

Images