Network node, wireless device, resource allocation server, and resource allocation method

Abstract

A network node, a wireless device, a resource allocation server, and a resource allocation method are disclosed. The network node includes a memory circuit, a processor circuit, and an interface. The network node is configured to send a first resource allocation request to a first resource allocation server and send a second resource allocation request to a second resource allocation server. The network node is configured to receive a first resource allocation response from the first resource allocation server and receive a second resource allocation response from the second resource allocation server. The first resource allocation response indicates first resource authorization parameters. The second resource allocation response indicates second resource authorization parameters. The network node is configured to operate using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters.

Description

Technical Field

[0001] The present disclosure relates to a network node, a wireless device, a resource allocation server, and a resource allocation method. Background Art

[0002] In a mobile communication network, resources need to be processed and allocated. As long as resources can be shared, they need to be processed and allocated. For example, shared resources such as radio resources allow the allocation of radio spectrum to be used.

[0003] Traditionally, for example, in a carrier-controlled cellular network, there is a central and static allocation of a common radio frequency to be used. For example, there is also a local distribution and dynamic allocation of how the allocated spectrum is used in terms of, for example, time slot allocation, modulation format selection, coding, and / or transmission power.

[0004] In such a scenario, the static allocation of frequencies is typically caused by the long-term lease of radio resource spectra, where the spectrum administrator can authorize local or national band licenses for a single company to use for several years.

[0005] An evolution towards a more semi-static processing of resources in mobile communication networks is emerging. As an example, edge computing can be used to distribute computer processing resources among devices in the network. Another example is radio spectrum allocation, which can be shared semi-statically by using a spectrum management database. Using the spectrum sharing database, a node requesting access to the spectrum managed by the spectrum sharing database can request access to the spectrum via the spectrum sharing database. Access to the node can be authorized based on access rules and licensing methods applied by regulations managed by the spectrum sharing database. This allows control of usage based on, for example, time and location, and is used, for example, by a Citizens Broadband Radio Service (CBRS) system to manage a portion of the 3.5 GHz spectrum.

[0006] This general concept has drawbacks due to a centralized approach to processing and managing requests in a single resource sharing database. Summary of the Invention

[0007] There is a need for a flexible and dynamic method for sharing and allocating resources, including spectrum resources, computing resources, software resources, and / or hardware resources. Accordingly, there is a need for an apparatus and method for resource allocation that alleviates, mitigates, or solves existing drawbacks and provides flexible and dynamic resource allocation.

[0008] A network node is disclosed. The network node includes a memory circuit, a processor circuit, and an interface. The network node is configured to send a first resource allocation request to a first resource allocation server and send a second resource allocation request to a second resource allocation server. The network node is configured to receive a first resource allocation response from the first resource allocation server and receive a second resource allocation response from the second resource allocation server. The first resource allocation response indicates first resource authorization parameters. The second resource allocation response indicates second resource authorization parameters. The network node is configured to operate using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters.

[0009] A resource allocation method performed by an example network node is disclosed. The method includes the steps of: sending a first resource allocation request to a first resource allocation server and sending a second resource allocation request to a second resource allocation server. The method includes the steps of: receiving a first resource allocation response from the first resource allocation server and receiving a second resource allocation response from the second resource allocation server. The first resource allocation response indicates first resource authorization parameters. The second resource allocation response indicates second resource authorization parameters. The method includes the steps of: operating using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters.

[0010] The disclosed network node and related methods provide flexible and dynamic resource allocation, where resource allocation authorization can be obtained by the network node from multiple resource allocation servers. In other words, the network node can combine resources from multiple resource allocation servers into a combined resource pool for use in operations (such as for communicating with a wireless device, for computing of a wireless device, such as for concurrent use).

[0011] A wireless device is disclosed. The wireless device includes a memory circuit, a processor circuit, and a wireless interface. The wireless device is configured to send a resource request to a network node. The wireless device is configured to receive a resource response indicating resource authorization parameters from the network node, where the resource authorization parameters are associated with a combined resource pool. The wireless device is configured to utilize the combined resource pool according to the resource authorization parameters.

[0012] A method for obtaining resource allocation performed by a wireless device is disclosed. The method includes the steps of: sending a resource request to a network node. The method includes the steps of: receiving a resource response indicating resource authorization parameters from the network node. The resource authorization parameters are associated with a combined resource pool. The method includes the steps of: utilizing the combined resource pool according to the resource authorization parameters.

[0013] The disclosed wireless devices and related methods can benefit from a combined resource pool, which can allow a wireless device to receive an authorization for resources as needed, or can, for example, provide the wireless device with the possibility of expanding the resource pool of the wireless device in certain situations. This results in highly dynamic and resource-efficient behavior. The disclosed wireless devices and related methods can benefit from accessing various types of resources. For example, this can enable the wireless device to benefit from high-performance artificial intelligence capabilities and / or gaming capabilities without any added cost of hardware devices.

[0014] A resource allocation server is disclosed. The resource allocation server includes a memory circuit, a processor circuit, and an interface. The resource allocation server is configured to communicate with a plurality of resource allocation servers including a first resource allocation server of a first network. The resource allocation server is configured to receive a first resource allocation request indicating a resource type from a requester. The resource allocation server is configured to negotiate resource allocation with the first resource allocation server based on the resource type indicated in the first resource allocation request. The resource allocation server is part of a network different from the first network.

[0015] A resource allocation method performed by a resource allocation server is disclosed. The method includes the steps of receiving a first resource allocation request indicating a resource type from a requester. The method includes the steps of negotiating resource allocation with the first resource allocation server based on the resource type indicated in the first resource allocation request. The resource allocation server is part of a network different from the first network.

[0016] The disclosed resource allocation server and related methods handle dynamic resource allocation requests by negotiating with one or more other resource allocation servers of other corresponding networks and thereby enabling access to other sets of resources managed by the other resource allocation servers. Brief Description of the Drawings

[0017] The above and other features and advantages of the present disclosure will become apparent to those skilled in the art from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings, wherein:

[0018] Figure 1 is a view illustrating traditional spectrum management via a central spectrum sharing database,

[0019] Figure 2 is a view illustrating an exemplary wireless communication system and an exemplary resource allocation server according to the present disclosure,

[0020] Figure 3 is an exemplary signaling diagram between an exemplary wireless device, an exemplary network node, and an exemplary resource allocation server according to one or more examples of the present disclosure,

[0021] Figure 4 is a block diagram illustrating an example network node according to the present disclosure,

[0022] Figure 5 is a flowchart illustrating an example method for resource allocation performed by a network node according to the present disclosure,

[0023] Figure 6 is a block diagram illustrating an example wireless device according to the present disclosure,

[0024] Figure 7 is a flowchart illustrating an example method for obtaining resource allocation performed by a wireless device according to the present disclosure,

[0025] Figure 8 is a schematic diagram illustrating an example system according to the present disclosure including an example resource allocation server,

[0026] Figure 9 shows a schematic diagram illustrating example functions and communications in an example network of five example resource allocation servers with co-located distributed ledger technology according to the present disclosure,

[0027] Figure 10 is a block diagram illustrating an example resource allocation server according to the present disclosure, and

[0028] Figure 11 is a flowchart illustrating an example method for resource allocation performed by a resource allocation server according to the present disclosure. DETAILED DESCRIPTION

[0029] In the following, various examples and details are described with reference to the relevant drawings. It should be noted that the drawings may be drawn to scale or not to scale, and elements of similar structure or function are denoted by the same reference numerals throughout the drawings. It should also be noted that the drawings are only intended to facilitate the description of the examples. They are not intended as an exhaustive description of the present disclosure or as a limitation on the scope of the present disclosure. Additionally, the illustrated examples need not have all aspects or advantages shown. Aspects or advantages described in connection with a particular example need not be limited to that example and may be practiced in any other example even if not so shown or not so explicitly described.

[0030] For clarity, these figures are schematic and simplified, and they only show the details helpful for understanding the present disclosure while omitting other details. The same reference numerals are used for the same or corresponding parts throughout the text.

[0031] Figure 1 is a view illustrating traditional spectrum management via a central spectrum sharing database 8.

[0032] Using a central spectrum sharing database 8, network nodes requesting access to the spectrum managed by the central spectrum sharing database 8 can request access to the spectrum via the central spectrum sharing database 8. For example, network nodes 2, 3, 4 of network A that process wireless device 9 can request access to the spectrum via the central spectrum sharing database 8. For example, network nodes 5, 6, 7 of network B can request access to the spectrum via the central spectrum sharing database 8.

[0033] For example, a network node can check whether the network node is permitted to use, for example, a spectrum range through the central spectrum sharing database 8 by sending a query to the central spectrum sharing database 8. The query can include network node geographical location, antenna configuration, radio parameters, and / or other network node specific information.

[0034] Their requests can be authorized to network nodes based on access rules and permission methods applied by regulations administered by the spectrum sharing database 8. This allows control of usage based on, for example, time and location, and is used, for example, by a Citizen Broadband Radio Service (CBRS) system to manage portions of the 3.5 GHz spectrum.

[0035] This general concept has drawbacks due to a centralized approach of processing requests and management in a single resource sharing database such as database 8. A flexible and dynamic method is needed to share and allocate resources, including spectrum resources and hardware resources. The present disclosure provides a network node such as a base station in a wireless network that sends resource requests for allocating resources to a plurality of resource allocation servers, wherein the network node can combine resources authorized from the plurality of servers into a resource pool for operation and / or wireless communication.

[0036] The present disclosure allows network nodes to access a plurality of available resource allocation servers and combine the allocations from them. The present disclosure provides several resource allocation methods.

[0037] Figure 2 is a view illustrating an example wireless communication system 1 and an example resource allocation server in accordance with one or more examples of the present disclosure.

[0038] The resource allocation servers disclosed herein can be regarded as logical entities that manage resources, such as managing different types of resource allocations and possibly owning these resources. The resource allocation server can include database functionality (e.g., lookup table type functionality) where a network node can check whether it has access rights. Alternatively or additionally, the resource allocation server can have resource leasing and / or renting functionality where a network node can request resources from a leasing transaction and access the resources via the leasing transaction.

[0039] An example wireless communication system includes a first network 30 (such as a first radio access network 30) and a second network 40 (such as a second radio access network 40). The example wireless communication system includes a wireless device 300.

[0040] The first network 30 (such as a first radio access network 30) includes a plurality of network nodes (such as radio access network nodes), such as network nodes 400, 400A, 400B.

[0041] The second network 40 (such as a second radio access network 40) includes a plurality of network nodes (such as radio access network nodes), such as network nodes 440, 441, 442.

[0042] The network nodes disclosed herein may be regarded as radio access network nodes operating in a radio access network, such as a base station, evolved Node B, eNB, gNB in NR. In one or more examples, the RAN node is a functional unit that may be distributed in multiple physical units.

[0043] As discussed in detail herein, the present disclosure relates to a wireless communication system 1 including a cellular system (e.g., a 3GPP wireless communication system). The wireless communication system 1 includes a wireless device 300 and / or a network node 400.

[0044] The wireless communication system 1 described herein may include one or more wireless devices 300 and / or one or more network nodes 400, such as one or more of the following: base stations, eNBs, gNBs, and access points.

[0045] The wireless device may refer to a mobile device and / or a user equipment UE.

[0046] The wireless device 300 may be configured to communicate with the network node 400 via a wireless link (or radio access link).

[0047] In Figure 2 , the network nodes in the network are wirelessly connected to one or more mobile or wireless devices, such as the wireless device 300 (such as a user device UE), and one or more resource allocation servers 500, 500A, 500B.

[0048] For example, the network node 440 may check multiple resource allocation servers 500A and 500B, and may obtain resource allocation from 500A and / or 500B. The network node 440 may use a combined resource pool from 500A and 500B.

[0049] Connect network node 440 to two or more resource allocation servers 500A, 500B. The resource allocation server 500A can be regarded as a resource allocation server independent of the network.

[0050] The exemplary wireless communication system optionally includes a central resource allocation server 500C.

[0051] In one or more examples, the present disclosure provides a distributed resource management, in which resources can be allocated to network nodes in a mobile network from multiple servers. For example, the disclosed network nodes send resource allocation requests to multiple corresponding resource allocation servers to allocate resources, such as communication resources and / or computing resources. For example, the disclosed network nodes can combine multiple resource authorizations into a combined resource pool according to corresponding resource authorization parameters for the operation of the network node and the wireless device. For example, the disclosed network nodes can obtain authorization for resources from one resource allocation server, and the authorization can be used by the network node in its operation.

[0052] The present disclosure can be particularly suitable when resource allocation is performed according to resource leasing (e.g., as a time allocation and / or location-specific allocation and / or service-specific allocation of resources from a resource allocation server). In this case, spectrum leasing can be regarded as a transaction. For example, in the transaction, parameters defining the protocol can be stored via a resource allocation distributed ledger function.

[0053] Resources can include one or more of the following: spectrum resources, computing resources (e.g., edge computing), hardware accelerators (such as those used for graphics or machine learning inference), neural network accelerators, or other physically limited resources. The use of the term "resource allocation" can be contemplated, and in some examples, spectrum is used as an example resource.

[0054] Figure 3 is an example signaling diagram between one or more example wireless devices 300, 300A, an example network node 400, and one or more example resource allocation servers 500, 500A according to one or more examples of the present disclosure.

[0055] In an initial step, the resource allocation servers 500, 500A register 702, 704 with the network node 400, where in some examples, each resource allocation server is used to handle different defined services, so that the network node 400 knows where to send resource requests.

[0056] The one or more example wireless devices 300, 300A may send resource requests 706, 708 to the network node 400 based on their upcoming expected resource needs. This signaling is partly optional, and if used, it may provide guidance to the network node for estimating upcoming resource needs.

[0057] When resource requests 706, 708 have been received from 300, 300A, the network node 400 may determine that one or more resources need to be acquired to satisfy the resource requests 706, 708. The network node may identify the need to send a resource allocation request to obtain resources of one or more resource types. In some embodiments, the network node 400 may perform a resource allocation request, such as for enabling a cell (initiating cell discovery) and / or for requesting a general resource pool.

[0058] The network node 400 sends one or more resource allocation requests 710, 712 to one or more resource allocation servers 500, 500A. The resource allocation requests 710, 712 may include service description parameters that identify the expected traffic type and quantify the need for resources.

[0059] The resource allocation servers 500, 500A process the resource allocation requests 710, 712 to verify availability (e.g., via database lookups, leasing via a resource allocation distributed ledger).

[0060] The resource allocation servers 500, 500A send resource allocation responses 714, 716 indicating resource authorization parameters to the network node 400.

[0061] The network node 400 combines the resource allocation responses 714, 716 from multiple resource allocation servers 500, 500A and may then use the allocated resources for communication between the network node and the wireless devices 300, 300A. In certain embodiments, the network node 400 may forward individual resource information to the wireless devices 300, 300A in resource responses 718, 720 and use the confirmed resources for its own upcoming communication and / or operations.

[0062] The resource allocation servers 500, 500A may be service-specific and may manage resource pools (e.g., resource pools for ultra-reliable low-latency communication URLLC (possibly related to specific spectrum / mmW) and resource pools for wide-area coverage Internet of Things IoT).

[0063] Resources can be regarded as devices to be accessed and / or used for operations. For example, resources include one or more of the following: radio spectrum resources and / or computing resources (such as hardware resources). For example, radio spectrum resources include: radio resources, frequency resources (such as frequency bands with bandwidth), time resources (such as time slots, time windows). Hardware resources include, for example, computing resources (such as edge computing resources), such as computer processing unit CPU and / or graphics processing unit GPU.

[0064] In some examples, the first resource can be frequency and time resources.

[0065] Resource allocation can be regarded as the allocation of resources that may result in authorization (such as partial authorization of the requested resources, or full or complete authorization of the requested resources), or the rejection of authorization to access the requested resources.

[0066] Figure 4 A block diagram of an example network node 400 according to the present disclosure is shown. The network node 400 includes: a memory circuit 401, a processor circuit 402, and a wireless interface 403. The network node 400 can be configured to execute Figure 5 any of the disclosed methods 200.

[0067] Configure the wireless interface 403 to perform wireless communication via a wireless communication system (such as a 3GPP system (such as, for example, a 3GPP system supporting one or more of the following: New Radio NR, Narrowband IoT, NB-IoT, and Long-Term Evolution - Machine-Type Communication Enhanced LTE-M)), a wireless LAN system (such as Wi-Fi IEEE 802.11), and a low-power network (such as based on IEEE802.15.4).

[0068] The network node 400 is configured to (such as via the wireless interface 403) send a first resource allocation request to a first resource allocation server and send a second resource allocation request to a second resource allocation server.

[0069] A resource allocation request (such as a first resource allocation request and / or a second resource allocation request) can be regarded as a request from a requester to access and / or utilize resources (which can be shared among various entities) to access and / or utilize a resource type. In some embodiments, the present disclosure allows a network node to indicate its expected service or its expected service type as part of the resource allocation request.

[0070] The resource allocation request can be responded to by the resource allocation server with a resource allocation response. The resource allocation request can include service description parameters that identify the expected service type and quantify the need for resources. The resource allocation request can include resource parameters that indicate (such as identify) the resource type.

[0071] The network node 400 is configured to receive a first resource allocation response from a first resource allocation server and a second resource allocation response from a second resource allocation server (such as via a wireless interface 403). The first resource allocation response indicates first resource authorization parameters, where the second resource allocation response indicates second resource authorization parameters. Resource authorization parameters can be regarded as parameters indicating permission to access and / or use resources, such as positive permission (such as permitted access, such as authorization, such as partial authorization of the requested resources, such as full or complete authorization of the requested resources) or negative permission (such as denied access). In one or more example network nodes, the first resource authorization parameters include information indicating a first resource associated with a first service of a first service type. In one or more example network nodes, the second resource authorization parameters include information indicating a second resource associated with a second service of a second service type. The resource allocation response or the resource authorization parameters can indicate the expected service.

[0072] The network node 400 is configured to operate using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters. The combined resource pool can be used by wireless devices simultaneously. The combined resource pool can be dedicated to a resource type and / or a service type (e.g., a resource pool for ultra-reliable low-latency communication URLLC (possibly related to a specific spectrum / mmW) and a resource pool for wide-area coverage Internet of Things IoT).

[0073] In one or more example network nodes, the first resource authorization parameters are associated with a first resource of a first type. In one or more example network nodes, the first resource includes one or more of the following: spectrum resources (such as a first spectrum resource), time resources (such as a first time resource), and hardware resources (such as a first hardware resource, such as computing resources (such as Tx output power authorization)). For example, the first type includes one or more of the following: spectrum type, time type, data processing resource type, and hardware type. In one or more example network nodes, the first resource includes spectrum resources (such as a first spectrum resource). In one or more example network nodes, the first resource includes time resources (such as a first time resource). In one or more example network nodes, the first resource includes hardware resources (such as a first hardware resource, such as computing resources (such as Tx output power authorization)).

[0074] In one or more example network nodes, a second resource authorization parameter is associated with a second resource of a second type. In one or more example network nodes, the second resource includes one or more of the following: a spectrum resource (such as a second spectrum resource), a time resource (such as a second time resource), and a hardware resource (such as a second hardware resource, such as Tx output power authorization). For example, the second type includes one or more of the following: a spectrum type, a time type, a data processing resource type, and a hardware type. In one or more example network nodes, the second resource includes a spectrum resource (such as a second spectrum resource). In one or more example network nodes, the second resource includes a time resource (such as a second time resource). In one or more example network nodes, the second resource includes a hardware resource (such as a second hardware resource, such as computing resources (such as Tx output power authorization)).

[0075] In one or more example network nodes, a combined resource pool combines a first resource and a second resource based on a first resource authorization parameter and a second resource authorization parameter. For example, when the first resource authorization parameter indicates a partial authorization of the requested resource and the second resource authorization parameter indicates a partial authorization of the requested resource, the combined resource includes the resource indicated by the partial authorization of the first authorization parameter and the resource indicated by the partial authorization of the second authorization parameter. For example, when the first resource authorization parameter indicates a negative permission for a resource (such as a denial of access) and the second resource authorization parameter indicates a full or partial authorization of the requested resource, the combined resource pool includes the full or partial authorization of the requested resource of the second resource authorization parameter.

[0076] In one or more example network nodes, the first resource at least partially overlaps with the second resource. For example, when the first resource is a first spectrum resource and the second resource is a second spectrum resource, and when both the first authorization parameter and the second authorization parameter indicate that the overlap (such as a frequency band) of the first spectrum resource and the second spectrum resource is acceptable, the network node can operate using the overlap of the first spectrum resource and the second spectrum resource.

[0077] In one or more example network nodes, the second type is different from the first type. For example, if the first type is a spectrum resource type, the second type is not a spectrum type, such as a hardware resource.

[0078] In one or more example network nodes, a second resource allocation request depends on a first resource allocation request and / or a first resource allocation response. In one or more examples, the second resource allocation request is sent after the first resource allocation response in time. For example, a first resource allocation request for a first amount of a first type of resource may be sent, and a first resource allocation response may be received, where the first resource authorization parameter indicates authorization for an amount of resource different from the amount of resource requested in the first resource allocation request. A second resource allocation request may be sent, where the resource requested in the second resource allocation request is selected based on the information received in the first resource allocation response. In one or more examples, a second resource type is selected based on the first resource allocation authorization. In one or more examples, the amount of resource requested in the second resource allocation request is selected based on the first resource allocation response. For example, a network node may have a resource requirement for transmitting data using resources consisting of time and frequency resources. In one or more examples, the first resource allocation request may include a resource allocation request for an amount of spectrum, where the first resource allocation response may include a first resource authorization parameter indicating an amount of spectrum different from the requested amount. Since the time required to transmit an amount of data over a wireless channel may depend on the allocated spectrum, a second resource allocation request may be sent, where the second resource allocation request may include, for example, a time allocation request, where the amount of time resource is selected based on the amount of frequency authorized in the first resource allocation authorization. In one or more examples, the second allocation request may include another spectrum allocation request, where the amount of spectrum resource is selected based on the amount of frequency authorized in the first resource allocation response.

[0079] In one or more example network nodes, the first resource allocation request indicates a first service of a first service type selected from one or more service types. The second resource allocation request indicates a second service of a second service type selected from the one or more service types. The one or more service types may include the first service type and / or the second service type.

[0080] The service type may indicate the expected service requested by the network node. The service may provide access to resources such as hardware resources, processing resources, and / or spectrum resources. For example, the service type may be based on the expected traffic type and on the quantified need for resources. For example, the service may include one or more of the following: a resource rental service, a resource lending service, and a resource provider service.

[0081] In one or more example network nodes, the first resource authorization parameter indicates a service corresponding to the first service of the first service type. In one or more example network nodes, the second resource authorization parameter indicates a service corresponding to the second service of the second service type.

[0082] In one or more example network nodes, the operation of using a combined resource pool based on a first resource authorization parameter and a second resource authorization parameter is based on combining a first resource and a second resource into the combined resource pool according to the first resource authorization parameter and the second resource authorization parameter. For example, the combination can depend on the resource types indicated in the first resource authorization parameter and the second resource authorization parameter. For example, when the first resource type and the second resource type are the same, the combination can include aggregating the first resource indicated by the first resource authorization parameter and the second resource indicated by the second resource authorization parameter. For example, in Figure 5 different radio resources such as time slots can be combined in S210A of Figure 5 In S210A of

[0083]

[0084] In one or more example network nodes, the operation of using a combined resource pool based on a first resource authorization parameter and a second resource authorization parameter includes: transmitting to the first wireless device an authorization of the first resource indicated in the first resource authorization parameter and / or the second resource indicated in the second resource authorization parameter. For example, the network node can transmit an authorization (such as a partial authorization or a full authorization, or a rejection) to the first wireless device according to the corresponding resource authorization parameter. For example, when the resource is of a spectrum resource type, the transmission of the authorization can include using the first resource according to the first resource authorization parameter and / or the second resource indicated in the second resource authorization parameter to communicate with the first wireless device. For example, when the first resource authorization parameter or the second resource authorization parameter indicates a rejection of the authorization of one or more corresponding resources, the network node being prevented from using the requested corresponding resources to communicate with the first wireless device (such as for a certain period of time) can be regarded as transmitting to the first wireless device an authorization of the first resource indicated in the first resource authorization parameter and / or the second resource indicated in the second resource authorization parameter.

[0085] In one or more example network nodes, when the resource is of a hardware resource type, the operation of using a combined resource pool based on a first resource authorization parameter and a second resource authorization parameter includes: operating using a combined hardware resource pool based on the first resource authorization parameter and the second resource authorization parameter. For example, the network node may indicate to a wireless device to utilize one or more resources in the combined resource pool based on the first resource authorization parameter and the second resource authorization parameter.

[0086] In one or more example network nodes, the first resource authorization parameter includes a parameter indicating a time-limited allocation of a first resource. The second resource authorization parameter includes a parameter indicating a time-limited allocation of a second resource. The time-limited allocation may be regarded as a temporary allocation. For example, the first resource authorization parameter includes a parameter indicating a lease of the first resource or a lending of the first resource. For example, the second resource authorization parameter includes a parameter indicating a lease of the second resource or a lending of the second resource.

[0087] In one or more example network nodes, the network node is configured to separate a first resource request and a second resource request based on a first service type indicated in the first resource request and a second service type indicated in the second resource request. For example, the network node separates the first resource request and the second resource request based on the first service type indicated in the first resource request and the second service type indicated in the second resource request so as to be able to issue a first resource allocation request and a second allocation request to a relevant resource allocation server based on the requested resource types.

[0088] In one or more example network nodes, the first resource authorization parameter includes a parameter indicating a time-limited allocation of a first resource, and wherein the second resource authorization parameter includes a parameter indicating a time-limited allocation of a second resource.

[0089] In one or more example network nodes, the time-limited allocation of the first resource includes a first transaction related to the first resource on a first distributed ledger.

[0090] In one or more example network nodes, the time-limited allocation of the second resource includes a second transaction related to the second resource on a second distributed ledger.

[0091] Optionally configure the processor circuit 402 to perform Figure 5 any of the operations disclosed in

[0092] Moreover, the operations of network node 400 can be considered as methods that network node 400 is configured to perform. Moreover, although the described functions and operations can be implemented in software, such functions can also be performed via dedicated hardware or firmware, or some combination of hardware, firmware, and / or software.

[0093] Memory circuit 401 can be one or more of the following: a buffer, flash memory, a hard disk drive, removable media, volatile memory, non-volatile memory, random access memory (RAM), or other suitable devices. In a typical arrangement, memory circuit 401 can include non-volatile memory for long-term data storage and volatile memory that serves as the system memory for processor circuit 402. Memory circuit 401 can exchange data with processor circuit 402 via a data bus. There can also be control lines and an address bus ( Figure 4 not shown in the figure) between memory circuit 401 and processor circuit 402. Memory circuit 401 is regarded as a non-transitory computer-readable medium.

[0094] Memory circuit 401 can be configured to store information (such as resource allocation requests, requested resource types, resource allocation responses, resource authorization parameters, transactions related to a distributed ledger) in a portion of the memory.

[0095] Figure 5 is an illustration of an example method 200 for resource allocation performed by an example network node (such as the network node 400 disclosed herein, such as Figure 2 , Figure 3 and Figure 4 ). The method 200 can be executed to enable resource allocation from a resource allocation server, such as for supporting resource allocation to a wireless device for resources controlled or managed by the resource allocation server.

[0096] Method 200 includes the steps of sending S206 a first resource allocation request to a first resource allocation server and sending S206 a second resource allocation request to a second resource allocation server.

[0097] Method 200 includes the steps of receiving S208 a first resource allocation response from the first resource allocation server and receiving S208 a second resource allocation response from the second resource allocation server (e.g., where the second resource allocation server is from a second network independent of the first network of the first resource allocation server). The first resource allocation response indicates first resource authorization parameters. The second resource allocation response indicates second resource authorization parameters. In one or more example methods, the first resource authorization parameters include information indicating a first resource associated with a first service of a first service type.

[0098] In one or more example methods, the second resource authorization parameter includes information indicating a second resource associated with a second service of a second service type.

[0099] Method 200 includes the following steps: operating S210 (such as for simultaneous use) using a combined resource pool based on a first resource authorization parameter and a second resource authorization parameter. The combined resource pool can be dedicated to a resource type and / or a service type (for example, a resource pool for ultra-reliable low-latency communication URLLC (possibly related to specific spectrum / mmW) and a resource pool for wide-area coverage Internet of Things IoT).

[0100] In one or more example methods, the first resource authorization parameter is associated with a first resource of a first type. In one or more example methods, the first resource includes one or more of the following: spectrum resources (such as a first spectrum resource), time resources (such as a first time resource), and hardware resources (such as a first hardware resource, such as computing resources (such as Tx output power authorization)). For example, the first type includes one or more of the following: spectrum type, time type, and hardware type.

[0101] In one or more example methods, the second resource authorization parameter is associated with a second resource of a second type. In one or more example methods, the second resource includes one or more of the following: spectrum resources (such as a second spectrum resource), time resources (such as a second time resource), and hardware resources (such as a second hardware resource, such as Tx output power authorization). For example, the second type includes one or more of the following: spectrum type, time type, and hardware type.

[0102] In one or more example methods, the combined resource pool combines the first resource and the second resource based on the first resource authorization parameter and the second resource authorization parameter. For example, when the first resource authorization parameter indicates a partial authorization of the requested resource and the second resource authorization parameter indicates a partial authorization of the requested resource, the combined resource includes the resource indicated by the partial authorization of the first authorization parameter and the resource indicated by the partial authorization of the second authorization parameter. For example, when the first resource authorization parameter indicates a negative permission for the resource (such as a denial of access) and the second resource authorization parameter indicates a full or partial authorization of the requested resource, the combined resource pool includes the full or partial authorization of the requested resource of the second resource authorization parameter.

[0103] In one or more example methods, the first resource at least partially overlaps with the second resource.

[0104] In one or more example methods, the second type is different from the first type. For example, when the first type is a spectrum resource type, the second type is not a spectrum type, such as a hardware resource.

[0105] In one or more example methods, the second resource allocation request depends on the first resource allocation request and / or the first resource allocation response.

[0106] In one or more example methods, the first resource allocation request indicates a first service of a first service type selected from one or more service types. The second resource allocation request indicates a second service of a second service type selected from the one or more service types. The one or more service types may include the first service type and / or the second service type.

[0107] In one or more example methods, the first resource authorization parameter indicates a service corresponding to the first service of the first service type. In one or more example methods, the second resource authorization parameter indicates a service corresponding to the second service of the second service type.

[0108] In one or more example methods, the operation S210 of using a combined resource pool based on the first resource authorization parameter and the second resource authorization parameter includes: merging the first resource and the second resource into a combined resource pool S210A based on the first resource authorization parameter and the second resource authorization parameter. For example, the merging S210A may depend on the resource types indicated in the first resource authorization parameter and the second resource authorization parameter. For example, when the first resource type and the second resource type are the same, the merging S210A may include aggregating the first resource indicated by the first resource authorization parameter and the second resource indicated by the second resource authorization parameter. For example, different radio resources, such as time slots, may be merged in S210A. For example, in S210A, different computing resources (such as hardware resources) may be merged using the resources given by the first resource allocation server and the second resource allocation server for the requested service type to form a combined resource pool. For example, a network node may aggregate resources from the first resource allocation server and resources from the second resource allocation server.

[0109] In one or more example methods, method 200 includes the following steps: receiving S202 a first resource request from a first wireless device. The first resource request may indicate the first resource type requested by the first wireless device. The first resource request may indicate a first service of a first type selected from the one or more service types.

[0110] In one or more example methods, the operation S210 of using a combined resource pool based on a first resource authorization parameter and a second resource authorization parameter includes: transmitting to a first wireless device an authorization for a first resource indicated in the first resource authorization parameter and / or a second resource indicated in the second resource authorization parameter.

[0111] In one or more example methods, the first resource authorization parameter includes a parameter indicating a time-limited allocation of the first resource. The second resource authorization parameter includes a parameter indicating a time-limited allocation of the second resource. The time-limited allocation can be regarded as a temporary allocation. For example, the first resource authorization parameter includes a parameter indicating a lease of the first resource or a lending of the first resource. For example, the second resource authorization parameter includes a parameter indicating a lease of the second resource or a lending of the second resource.

[0112] In one or more example methods, method 200 includes the following steps: separating S204 the first resource request and the second resource request based on a first service type indicated in the first resource request and a second service type indicated in the second resource request. For example, a network node separates the first resource request and the second resource request based on the first service type indicated in the first resource request and the second service type indicated in the second resource request so as to be able to issue a first resource allocation request and a second allocation request to a relevant resource allocation server based on the requested resource types.

[0113] In one or more example methods, the first resource authorization parameter includes a parameter indicating a time-limited allocation of the first resource, and wherein the second resource authorization parameter includes a parameter indicating a time-limited allocation of the second resource.

[0114] In one or more example methods, the time-limited allocation of the first resource includes a first transaction related to the first resource on a first distributed ledger.

[0115] In one or more example methods, the time-limited allocation of the second resource includes a second transaction related to the second resource on a second distributed ledger.

[0116] Figure 6 is a block diagram of an example wireless device 300 in accordance with the present disclosure. The wireless device 300 includes a memory circuit 301, a processor circuit 302, and a wireless interface 303. The wireless device 300 can be configured to execute Figure 7 any of the methods disclosed in

[0117] The wireless interface 303 is configured to perform wireless communication via a wireless communication system (such as a 3GPP system, such as a 3GPP system supporting one or more of the following: New Radio NR, Narrowband IoT, NB-IoT, and Long Term Evolution-Machine Type Communication Enhanced LTE-M), a wireless LAN system (such as Wi-Fi IEEE 802.11), and a low power network (such as based on IEEE 802.15.4).

[0118] The wireless device 300 is configured to send a resource request to a network node (such as via the wireless interface 303).

[0119] The wireless device 300 is configured to receive, from a network node (such as via the wireless interface 303), a resource response indicating resource authorization parameters. The resource authorization parameters are associated with a combined resource pool. In one or more examples, the resource authorization parameters may correspond to Figure 4 and Figure 5 a first (or second) resource authorization parameter of

[0120] In one or more examples, the resource response may be based on a resource allocation response, such as Figure 4 and Figure 5 a first (or second) resource allocation response of Figure 4 and Figure 5 In some examples, the first (or second) resource allocation response of

[0121] The network node 300 is configured to utilize the combined resource pool according to the resource authorization parameters. The combined resource pool may combine one or more resources according to the resource authorization parameters obtained from a resource allocation server. When the resource authorization parameters indicate a rejection of the requested resources, the combined resource pool excludes the rejected requested resources.

[0122] The network node 300 is optionally configured to utilize the combined resource pool according to the resource authorization parameters, simultaneously with another wireless device.

[0123] The operations of the wireless device 300 may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) stored on a non-transitory computer-readable medium (e.g., the memory circuit 301) and executed by the processor circuit 302.

[0124] Moreover, the operation of the wireless device 300 can be considered as a method that the wireless device 300 is configured to perform. Moreover, although the described functions and operations can be implemented in software, such functions can also be performed via dedicated hardware or firmware, or some combination of hardware, firmware, and / or software.

[0125] The memory circuit 301 can be one or more of the following: a buffer, flash memory, a hard disk drive, removable media, volatile memory, non-volatile memory, random access memory (RAM), or other suitable devices. In a typical arrangement, the memory circuit 301 can include non-volatile memory for long-term data storage and volatile memory that serves as the system memory for the processor circuit 302. The memory circuit 301 can exchange data with the processor circuit 302 via a data bus. There can also be control lines and an address bus ( Figure 6 not shown in the figure) between the memory circuit 301 and the processor circuit 302. The memory circuit 301 is regarded as a non-transitory computer-readable medium.

[0126] The memory circuit 301 can be configured to store information (such as requested resources, resource authorization parameters) in a portion of the memory.

[0127] Figure 7 is an illustration of a flowchart of an example method 600 for obtaining resource allocation performed by an example wireless device (such as the wireless device disclosed herein, such as Figure 2 , Figure 3 , Figure 6 the wireless device 300) according to the present disclosure.

[0128] The method 600 includes the following steps: sending an S602 resource request to a network node.

[0129] The method 600 includes the following steps: receiving an S604 resource response indicating resource authorization parameters from the network node. The resource authorization parameters are associated with a combined resource pool.

[0130] The method 600 includes utilizing the S606 combined resource pool according to the resource authorization parameters, for example, for simultaneous use with another wireless device.

[0131] Figure 8 is a schematic diagram illustrating an example system according to the present disclosure including an example resource allocation server. Figure 8 Shows a first network 30 including an example first resource allocation server 500. Figure 8 Shows a second network 40 including an example second resource allocation server 500A. Figure 8Shows a network - independent resource allocation server 500C, which is configured to communicate with a first resource allocation server 500 and / or a second resource allocation server 500A.

[0132] The present disclosure provides resource allocation (such as spectrum usage and / or computing resource usage) among multiple resource allocation servers that do not belong to the same network. In some embodiments, the present disclosure provides the allocation of the agreements reached that can be made via a resource allocation distributed ledger.

[0133] The present disclosure provides a resource allocation server for resource allocation negotiation and registration. For example, network nodes and / or wireless devices within a network can request specific resources, such as an amount of spectrum at a specific time, from the disclosed resource allocation server. The resource allocation server disclosed herein has a method for negotiating resource allocation with other resource allocation servers in other networks or systems. For example, other resource allocation servers may have resources that overlap with the negotiating resource allocation server.

[0134] Once the negotiation is completed among the involved resource allocation servers, there is a function for registering and storing the resource allocation of the agreements reached. These agreements are stored robustly, redundantly, and / or securely, and are traceable and / or transparent to all the involved resource allocation servers, without uncertainty in timing or content.

[0135] In some examples, the present disclosure proposes adding data specifying a protocol such as a transaction to a resource allocation distributed ledger using distributed ledger technology (DLT). This can inherently make the protocol visible simultaneously at all resource allocation servers and can be integrated into the negotiation process.

[0136] In Figure 8 , the resource allocation servers 500, 500A, 500C signal resource allocation requests and resource allocation responses to negotiate and possibly reach an agreement on authorizing a requester (such as the network nodes and / or wireless devices disclosed herein) to access certain resources. The resource allocation server 500 can be part of a first network 30. The resource allocation server 500A can be part of a second network 40. The resource allocation server 500C can be regarded as a network - independent resource allocation server.

[0137] A resource allocation request from one resource allocation server to another can include one or more parameters specifying a resource request description (for example, in the case of spectrum, parameters indicating a channel, parameters indicating bandwidth, parameters indicating time, parameters indicating duration, parameters indicating periodicity, parameters indicating geographical location). The resource allocation request can, for example, include predictions of future requests, service types, and priorities.

[0138] The resource allocation server can reach a consensus in a distributed manner, for example, through common priority rules and / or fairness rules and / or priority fairness rules. A resource allocation request can be responded to with a resource authorization parameter indicating the authorization of some or all of the requested resources, or with a negative response (such as a refusal to allocate resources).

[0139] In some embodiments, the negotiation can also include economic agreement parameters in terms of reaching an agreement on the cost of leased resources.

[0140] It can be noted that the resource allocation server can negotiate with and request resources from multiple other resource allocation servers. Different resource allocation servers can be used to access different types of resources. Once there is an agreement on the requested resource allocation, it can trigger a transaction in a dedicated distributed ledger as Figure 9 illustrated.

[0141] Figure 9 A schematic diagram showing example functions and communications in an example network of five example resource allocation servers 500, 800, 802, 804, 805 illustrating a co-located resource allocation distributed ledger based on distributed ledger technology according to the present disclosure is shown. The resource allocation server 500 can operate based on one or more negotiation protocols and / or one or more policies.

[0142] For example, the resource allocation server 500 receives a resource allocation request 722 indicating a resource type from a requester. The resource allocation server 500 negotiates resource allocation with the first resource allocation server 800 and optionally with the second resource allocation server 802 based on the resource type indicated in the first resource allocation request. The resource allocation server 500 can negotiate with one or more additional resource allocation servers 802, 804, 805.

[0143] Upon reaching an agreement, or as part of the negotiation protocol, the resource allocation server 500 node creates a transaction in the resource allocation distributed ledger in a joint consensus with one or more of 800, 802, 804, 805. When the transaction is confirmed, the resource allocation server 500 transmits the resulting resource allocation response 724 to the requester.

[0144] When resource allocation servers 500, 800, 802, 804, 805 are processing the same transaction, the resource allocation distributed ledger contains the same final agreement across all resource allocation servers and can deliver a resource allocation response from resource allocation server 500 to the requester. In some embodiments, the resource allocation distributed ledger functionality can be co-located with the resource allocation server. In other embodiments, the resource allocation distributed ledger functionality is not co-located with resource allocation servers 800, 802, 804, 805.

[0145] The resource allocation distributed ledger can operate according to a federated consensus mechanism. The resource allocation distributed ledger can include an additional hash tree.

[0146] The term "federated consensus mechanism" as used herein can be regarded as a mechanism that can ensure, with a defined level of certainty, that the additional hash trees created by the respective resource allocation distributed servers are the same, comply with the predetermined rules of the resource allocation distributed ledger or hash tree, and store the additional hash trees in the resource allocation distributed ledger.

[0147] Example federated consensus mechanisms can include one or more of the following: Proof-of-Work, Proof-of-State, Proof-of-Elapsed Time, Practical Byzantine Fault Tolerance, Cross-Fault Tolerance (XFT), and federated Byzantine protocols (such as the Ripple Consensus Protocol algorithm and the Stellar Consensus Protocol).

[0148] The term "resource allocation distributed ledger" can be regarded as a resource allocation distributed ledger data hash tree that is shared, replicated, and synchronized among resource allocation distributed ledgers or servers. The resource allocation distributed ledger records resource authorization transactions between resource allocation servers. For example, the records in the resource allocation data hash tree can have timestamps and unique cryptographic signatures. For example, all records in the resource allocation data hash tree can have timestamps and unique cryptographic signatures, providing a transparent and auditable history of each transaction of the resources. For example, the resource allocation distributed ledger can be based on the Hyperledger Fabric blockchain.

[0149] Figure 10 is a block diagram illustrating an example resource allocation server 500 according to the present disclosure. The resource allocation server 500 includes: a memory circuit 501, a processor circuit 502, and an interface 503. The resource allocation server 500 can be configured to execute Figure 11Any of the methods disclosed in. In other words, the resource allocation server 500 can be configured for resource allocation.

[0150] The interface 503 is configured to perform wired and / or wireless communication via a communication system such as a 3GPP system.

[0151] The resource allocation server 500 is configured to communicate with a plurality of resource allocation servers (such as via the interface 503).

[0152] The plurality of resource allocation servers includes a first resource allocation server of a first network.

[0153] The resource allocation server 500 is configured to receive a first resource allocation request indicating a resource type from a requester (such as via the interface 503). The requester can be a wireless device and / or network node as Figure 3 disclosed.

[0154] A resource allocation request from one resource allocation server to another resource allocation server can include one or more parameters specifying a resource request description (for example, in the case of a spectrum, parameters indicating a channel, parameters indicating a bandwidth, parameters indicating a time, parameters indicating a duration, parameters indicating a periodicity, parameters indicating a geographical location). The resource allocation request can, for example, include a prediction of a future request, a service type, and a priority.

[0155] The resource allocation server 500 is configured to negotiate a resource allocation based on the resource type indicated in the first resource allocation request with the first resource allocation server (such as using the processor circuit 502 and / or the interface 503). In other words, the negotiation is linked to the first resource allocation request. The resource allocation can indicate a lease of a first resource and / or a second resource.

[0156] The resource allocation server 500 is part of a network different from the first network. The network of the resource allocation server 500 can be represented as a second network different from the first network.

[0157] The resource allocation server 500 can be configured to negotiate an allocation of resources based on the resource type indicated in the first resource allocation request with a plurality of resource allocation servers (such as using the processor circuit 502 and / or the interface 503). The plurality of resource allocation servers do not belong to the network of the resource allocation server 500. The plurality of resource allocation servers can all belong to one or more networks different from the network of the resource allocation server 500. In some embodiments, the plurality of resource allocation servers can all belong to their own network. In some embodiments, one or more of the plurality of resource allocation servers can belong to the same network but different from the network of the resource allocation server 500.

[0158] In one or more examples, the negotiation with the resource allocation server may include transmitting (such as sending and / or receiving) one or more signaling messages between the resource allocation server and one or more other resource allocation servers (such as a first resource allocation server). The negotiation may include, for example, a sequence of messages sent as one or more queries and one or more responses to the queries. The negotiation may end by transmitting an acknowledgement signaling.

[0159] In one or more examples, the negotiation may include transmitting results from distributed computing, which means that two or more nodes may perform the same or different computations and may signal the results from the computations to the resource allocation server. Such computations may be performing verification computations to ensure that two or more resource allocation servers share the same understanding of the expected resource allocation as part of the negotiation.

[0160] In one or more example resource allocation servers, the resource allocation server 500 is configured to negotiate resource allocation with a first resource allocation server based on the resource type indicated in a second allocation request. The resource allocation server may be configured to receive a second allocation request from a requester.

[0161] In one or more example resource allocation servers, the negotiation of the resource allocation includes: determining whether an agreement is reached between the resource allocation server and the first resource allocation server.

[0162] In one or more example resource allocation servers, the resource allocation server 500 is configured to generate a transaction in the resource allocation distributed ledger when an agreement on the authorized resource allocation is reached between the resource allocation server and the first resource allocation server (such as when the agreement is reached). For example, when the agreement is reached, the resource allocation server may obtain such a protocol indicator that indicates the protocol when the agreement is reached between the resource allocation server and the first resource allocation server. For example, when no agreement is reached, the resource allocation server may obtain such a protocol indicator that indicates the protocol when no agreement is reached between the resource allocation server and the first resource allocation server.

[0163] In one or more example resource allocation servers, the resource allocation server 500 is configured to send a first resource allocation response indicating authorization of the resource to the requester when the transaction on the resource allocation distributed ledger is verified. In other words, when the transaction is confirmed (such as based on proof-of-work), a first resource allocation response indicating authorization of the resource is sent to the requester.

[0164] In one or more example resource allocation servers, the protocol is based on a set of protocol item parameters including a first protocol item parameter, where the first protocol item parameter indicates the criteria to be met for reaching an agreement. For example, the agreement can be indicated by the transmission of an acknowledgment ACK message. For example, initiation includes a resource allocation request, and the resource allocation response to the resource allocation request includes resource authorization parameters. For example, an agreement can be reached when the requester responds to the resource allocation response with an ACK message. Additionally, the resource allocation request and the resource allocation response can be sent by the requester until the final ACK message is sent by the requester. In other words, the criteria to be met is the transmission of the ACK message at the resource allocation server.

[0165] It is conceivable that the resource allocation server has criteria or limitations on the relationship between the cost and the benefits of different levels of resource allocation, so as to respectively determine what is a sufficiently acceptable agreement and then send a resource allocation response, which can lead to further transmissions to reach a conclusion. Examples can be, for example, pass / fail limits for the allocation. For example, when the resource allocation request is 100 units and 80 units are authorized in the resource allocation response, according to this criterion, this can be acceptable. It can also be cost-related, with a certain total cost or cost per unit.

[0166] In one or more example resource allocation servers, the protocol is based on a joint consensus mechanism. The joint consensus mechanism can be common among the following parties involved: the resource allocation server and at least one resource allocation server among the multiple resource allocation servers.

[0167] In one or more example resource allocation servers, the joint consensus mechanism includes reaching a consensus in a distributed mode (e.g., in a distributed manner) between the resource allocation server and the first resource allocation server (and possibly also with other resource allocation servers).

[0168] In one or more example resource allocation servers, the joint consensus mechanism is based on a rule set and a service type (such as the service type indicated in the first resource allocation request). In one or more example resource allocation servers, the rule set includes a first rule, where the first rule includes one or more of the following items: a priority rule, and a fairness rule. For example, the rule set can be based on the service type and priority (such as a common priority fairness rule). For example, the prioritization can be based on the traffic type, internal priority, fairness (e.g., any request is weighted in the same way).

[0169] In one or more example resource allocation servers, the resource allocation server 500 is configured not to generate a transaction on the resource allocation distributed ledger when no agreement on an authorized allocation is reached between the resource allocation server and a first resource allocation server.

[0170] In one or more example resource allocation servers, resource authorization is an authorization for a part of a resource.

[0171] In one or more example resource allocation servers, the federated consensus mechanism is established between the resource allocation server and at least one of the plurality of resource allocation servers before receiving the first resource allocation request.

[0172] In one or more example resource allocation servers, the resource allocation distributed ledger is associated with the resource allocation server and the plurality of resource allocation servers. For example, the resource allocation distributed ledger is common between the resource allocation server and the plurality of resource allocation servers, such as distributed between the resource allocation server and the plurality of resource allocation servers.

[0173] In one or more example resource allocation servers, the resource allocation distributed ledger is a resource allocation distributed ledger of a resource allocation server dedicated to a network (e.g., a network only for the resource allocation server 500).

[0174] In one or more example resource allocation servers, the resource allocation distributed ledger is a resource allocation distributed ledger collocated with the resource allocation server.

[0175] In one or more example resource allocation servers, resources include one or more of the following: spectrum resources, time resources, and hardware resources.

[0176] In one or more example resource allocation servers, the resource allocation server 500 is configured to receive a confirmation indicator from the resource allocation distributed ledger (such as via interface 503) when verifying a transaction on the resource allocation distributed ledger. When the resource allocation distributed ledger is collocated with the resource allocation server, the confirmation indicator can be an internal indicator.

[0177] In one or more example resource allocation servers, negotiation includes: sending a second resource allocation request to the first resource allocation server. The second resource allocation request can be the same as or different from the first resource allocation request. In one or more example resource allocation servers, negotiation includes: receiving a second resource allocation response from the first resource allocation server. The second resource allocation response indicates a protocol indicator regarding the resource allocation indicated in the second allocation request.

[0178] The processor circuit 502 is optionally configured to perform Figure 11 any of the operations disclosed in Figure 11 (such as any one or more of S104, S106A, S107, S108, S109, S110, S112, S112A, S112B). The operations of the resource allocation server 500 may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) that are stored on a non-transitory computer-readable medium (e.g., the memory circuit 501) and are executed by the processor circuit 502.

[0179] Moreover, the operations of the resource allocation server 500 can be considered as a method that the resource allocation server 500 is configured to perform. Moreover, although the described functions and operations can be implemented in software, such functions can also be performed via dedicated hardware or firmware, or some combination of hardware, firmware, and / or software.

[0180] The memory circuit 501 can be one or more of the following: a buffer, flash memory, a hard disk drive, a removable medium, volatile memory, non-volatile memory, random access memory (RAM), or other suitable devices. In a typical arrangement, the memory circuit 501 can include non-volatile memory for long-term data storage and volatile memory that serves as the system memory of the processor circuit 502. The memory circuit 501 can exchange data with the processor circuit 502 via a data bus. There may also be control lines and an address bus ( Figure 10 not shown in Figure 10 ) between the memory circuit 501 and the processor circuit 502. The memory circuit 501 is regarded as a non-transitory computer-readable medium.

[0181] The memory circuit 501 can be configured to store information (such as requested resources, resource authorization parameters) in a portion of the memory.

[0182] Figure 11 is an example flowchart of a method 100 for resource allocation performed by a resource allocation server (such as Figure 2 , Figure 3 , Figure 10 the resource allocation servers 500, 500A, 500B, 500C in any of the figures in Figure 10 ) according to the present disclosure.

[0183] Method 100 includes the following steps: receiving S104 a first resource allocation request indicating a resource type from a requester.

[0184] Method 100 includes the following steps: negotiate S106 resource allocation with a first resource allocation server based on the resource type indicated in a first resource allocation request. The resource allocation server is part of a network different from the first network.

[0185] In one or more example methods, negotiating S106 includes: determining S106A whether an agreement is reached between the resource allocation server and the first resource allocation server.

[0186] In one or more example methods, method 100 includes the following steps: when an agreement for authorizing resource allocation is reached between the resource allocation server and the first resource allocation server, generate S108 a transaction in the resource allocation distributed ledger.

[0187] In one or more example methods, method 100 includes the following steps: when a transaction on the resource allocation distributed ledger is verified, send S110 a first resource allocation response indicating authorization of the resource to the requester.

[0188] In one or more example methods, the agreement is based on a set of protocol item parameters including a first protocol item parameter, where the first protocol item parameter indicates the criteria to be met for reaching the agreement.

[0189] In one or more example methods, the agreement is based on a federated consensus mechanism.

[0190] In one or more example methods, the federated consensus mechanism includes: reaching a consensus in a distributed mode between the resource allocation server and the first resource allocation server.

[0191] In one or more example methods, the federated consensus mechanism is based on a rule set and a service type. In one or more example methods, the rule set includes a first rule, where the first rule includes one or more of the following items: a priority rule, and a fairness rule. For example, the rule set can be based on the service type and priority (such as a common priority fairness rule). For example, prioritization can be based on the business type, internal priority, fairness (e.g., any request is weighted in the same way).

[0192] In one or more example methods, method 100 includes the following steps: receiving, from a requester, a second resource allocation request indicating a resource type (indicating a second resource type). The second resource may be the same or different resource type as the first resource allocation request. In some embodiments, the second resource may be different from the resource type of the first resource allocation request. In one or more example methods, method 100 includes the following steps: negotiating S112 resource allocation with a first resource allocation server based on the resource type indicated in the second allocation request. In one or more example methods, negotiating S112 includes: sending S112A the second resource allocation request to the first resource allocation server.

[0193] In one or more example methods, negotiating S112 includes: receiving S112B a second resource allocation response from the first resource allocation server. The second resource allocation response indicates a protocol indicator regarding the resource allocation indicated in the second allocation request.

[0194] In one or more example methods, method 100 includes the following steps: when no agreement on an authorized allocation is reached between the resource allocation server and the first resource allocation server, inhibiting S107 generating a transaction on the resource allocation distributed ledger.

[0195] In one or more example methods, resource authorization is an authorization for a part of a resource.

[0196] In one or more example methods, a joint consensus mechanism is established between the resource allocation server and at least one of the plurality of resource allocation servers before receiving the first resource allocation request.

[0197] In one or more example methods, the resource allocation distributed ledger is associated with the resource allocation server and the plurality of resource allocation servers.

[0198] In one or more example methods, the resource allocation distributed ledger is a resource allocation distributed ledger dedicated to the resource allocation server of the network.

[0199] In one or more example methods, the resource allocation distributed ledger is a resource allocation distributed ledger paired with the resource allocation server.

[0200] In one or more example methods, resources include one or more of the following items: spectrum resources, time resources, and hardware resources.

[0201] In one or more example methods, method 100 includes the following steps: when verifying a transaction on the resource allocation distributed ledger, receiving S109 a verification indicator from the resource allocation distributed ledger.

[0202] Examples of the methods and products (network nodes, wireless devices, and resource allocation servers) according to the present disclosure are set forth in the following items:

[0203] Item 1. A network node, the network node including a memory circuit, a processor circuit, and an interface, wherein the network node is configured to:

[0204] - Send a first resource allocation request to a first resource allocation server and send a second resource allocation request to a second resource allocation server;

[0205] - Receive a first resource allocation response from the first resource allocation server and receive a second resource allocation response from the second resource allocation server, wherein the first resource allocation response indicates first resource authorization parameters, and wherein the second resource allocation response indicates second resource authorization parameters; and

[0206] - Operate using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters.

[0207] Item 2. The network node according to Item 1, wherein the first resource authorization parameters are associated with a first type of first resource.

[0208] Item 3. The network node according to Item 2, wherein the first resource includes one or more of the following: spectrum resources, time resources, and hardware resources.

[0209] Item 4. The network node according to any one of Items 2 to 3, wherein the second resource authorization parameters are associated with a second type of second resource.

[0210] Item 5. The network node according to Item 4, wherein the second resource includes one or more of the following: spectrum resources, time resources, and hardware resources.

[0211] Item 6. The network node according to any one of Items 4 to 5, wherein the combined resource pool combines the first resource and the second resource based on the first resource authorization parameters and the second resource authorization parameters.

[0212] Item 7. The network node according to any one of the foregoing items depending on Items 2 and 4, wherein the first resource at least partially overlaps with the second resource.

[0213] Item 8. The network node according to any one of Items 4 to 6, wherein the second type is different from the first type.

[0214] Item 9. The network node according to any one of Items 4 to 7, wherein the second resource allocation request depends on the first resource allocation request and / or the first resource allocation response.

[0215] Item 10. The network node according to any one of the preceding items, wherein the first resource allocation request indicates a first service of a first service type selected from one or more service types; and wherein the second resource allocation request indicates a second service of a second service type selected from the one or more service types.

[0216] Item 11. The network node according to Item 10, wherein the first resource allocation response includes information indicating a service corresponding to the first service of the first service type.

[0217] Item 12. The network node according to any one of Items 10 to 11, wherein the second resource allocation response includes information indicating a service corresponding to the second service of the second service type.

[0218] Item 13. The network node according to any one of Items 10 to 12, wherein the first resource authorization parameter includes information indicating the first resource associated with the first service of the first service type.

[0219] Item 14. The network node according to any one of Items 10 to 13, wherein the second resource authorization parameter includes information indicating the second resource associated with the second service of the second service type.

[0220] Item 15. The network node according to any one of Items 4 to 14, wherein the operation of using the combined resource pool based on the first resource authorization parameter and the second resource authorization parameter is based on combining the first resource and the second resource into the combined resource pool according to the first resource authorization parameter and the second resource authorization parameter.

[0221] Item 16. The network node according to any one of Items 10 to 15, wherein the first resource authorization parameter indicates a service corresponding to the first service of the first service type, and the second resource authorization parameter indicates a service corresponding to the second service of the second service type.

[0222] Item 17. The network node according to any one of the preceding items, wherein the network node is configured to receive a first resource request from a first wireless device.

[0223] Item 18. The network node according to any one of Items 4 to 17, wherein the operation of using the combined resource pool based on the first resource authorization parameter and the second resource authorization parameter includes: transmitting an authorization for the first resource indicated in the first resource authorization parameter and / or the second resource indicated in the second resource authorization parameter to the first wireless device.

[0224] Item 19. The network node according to any one of the preceding items, wherein the network node is configured to receive a second resource request from a second wireless device.

[0225] Item 20. The network node according to Item 19, wherein the network node is configured to separate the first resource request and the second resource request based on a first service type indicated in the first resource request and a second service type indicated in the second resource request.

[0226] Item 21. The network node according to any one of the preceding items, wherein the first resource authorization parameter includes a parameter indicating a time-limited allocation of the first resource, and wherein the second resource authorization parameter includes a parameter indicating a time-limited allocation of the second resource.

[0227] Item 22. The network node according to Item 21, wherein the time-limited allocation of the first resource includes a first transaction related to the first resource on a first distributed ledger.

[0228] Item 23. The network node according to any one of Items 21 to 22, wherein the time-limited allocation of the second resource includes a second transaction related to the second resource on a second distributed ledger.

[0229] Item 24. A wireless device, the wireless device including a memory circuit, a processor circuit, and a wireless interface, wherein the wireless device is configured to:

[0230] - send a resource request to a network node;

[0231] - receive a resource response indicating a resource authorization parameter from the network node, wherein the resource authorization parameter is associated with a combined resource pool; and

[0232] - utilize the combined resource pool according to the resource authorization parameter.

[0233] Item 25. A method performed by a network node (400), the method (200) including the following steps:

[0234] - Send (S206) a first resource allocation request to a first resource allocation server and send (S206) a second resource allocation request to a second resource allocation server;

[0235] - Receive (S208) a first resource allocation response from the first resource allocation server and receive (S208) a second resource allocation response from the second resource allocation server, wherein the first resource allocation response indicates first resource authorization parameters, and wherein the second resource allocation response indicates second resource authorization parameters; and

[0236] - Operate (S210) using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters.

[0237] Item 26. The method according to item 25, wherein the first resource authorization parameters are associated with a first resource of a first type.

[0238] Item 27. The method according to item 26, wherein the first resource includes one or more of the following: spectrum resources, time resources, and hardware resources.

[0239] Item 28. The method according to any one of items 26 to 27, wherein the second resource authorization parameters are associated with a second resource of a second type.

[0240] Item 29. The method according to item 28, wherein the second resource includes one or more of the following: spectrum resources, time resources, and hardware resources.

[0241] Item 30. The method according to any one of items 28 to 29, wherein the combined resource pool combines the first resource and the second resource based on the first resource authorization parameters and the second resource authorization parameters.

[0242] Item 31. The method according to any one of the foregoing items depending on items 26 and 27, wherein the first resource at least partially overlaps with the second resource.

[0243] Item 32. The method according to any one of items 28 to 30, wherein the second type is different from the first type.

[0244] Item 33. The method according to any one of items 28 to 31, wherein the second resource request depends on the first resource allocation request and / or the first resource allocation response.

[0245] Item 34. The method according to any one of Items 25 to 33 above, wherein the first resource allocation request indicates a first service of a first service type selected from one or more service types; and wherein the second resource allocation request indicates a second service of a second service type selected from the one or more service types.

[0246] Item 35. The method according to Item 34, wherein the first resource allocation response includes information indicating a service corresponding to the first service of the first service type.

[0247] Item 36. The method according to any one of Items 34 to 35, wherein the second resource allocation response includes information indicating a service corresponding to the second service of the second service type.

[0248] Item 37. The method according to any one of Items 34 to 36, wherein the first resource authorization parameter includes information indicating the first resource associated with the first service of the first service type.

[0249] Item 38. The method according to any one of Items 34 to 37, wherein the second resource authorization parameter includes information indicating the second resource associated with the second service of the second service type.

[0250] Item 39. The method according to any one of Items 28 to 38, wherein the operation (S210) of using the combined resource pool based on the first resource authorization parameter and the second resource authorization parameter includes: combining (S210A) the first resource and the second resource into the combined resource pool based on the first resource authorization parameter and the second resource authorization parameter.

[0251] Item 40. The method according to any one of Items 34 to 39, wherein the first resource authorization parameter indicates a service corresponding to the first service of the first service type, and the second resource authorization parameter indicates a service corresponding to the second service of the second service type.

[0252] Item 41. The method according to any one of Items 25 to 40 above, the method comprising the steps of:

[0253] - Receiving (S202) a first resource request from a first wireless device.

[0254] Item 42. The method according to any one of Items 28 to 41, wherein the operation (S210) of using the combined resource pool based on the first resource authorization parameter and the second resource authorization parameter includes: transmitting (S210B) to the first wireless device an authorization for the first resource indicated in the first resource authorization parameter and / or the second resource indicated in the second resource authorization parameter.

[0255] Item 43. The method according to any one of the preceding Items 25 to 42, wherein the first resource authorization parameter includes a parameter indicating a time-limited allocation of the first resource, and wherein the second resource authorization parameter includes a parameter indicating a time-limited allocation of the second resource.

[0256] Item 44. The method according to Item 43, the method comprising the steps of:

[0257] - Separating (S204) the first resource request and the second resource request based on a first service type indicated in the first resource request and a second service type indicated in the second resource request.

[0258] Item 45. The method according to any one of the preceding Items 25 to 44, wherein the first resource authorization parameter includes a parameter indicating a time-limited allocation of the first resource, and wherein the second resource authorization parameter includes a parameter indicating a time-limited allocation of the second resource.

[0259] Item 46. The method according to Item 45, wherein the time-limited allocation of the first resource includes a first transaction related to the first resource on a first distributed ledger.

[0260] Item 47. The method according to any one of Items 45 to 46, wherein the time-limited allocation of the second resource includes a second transaction related to the second resource on a second distributed ledger.

[0261] Item 48. A method performed by a wireless device 300, the method 600 comprising the steps of:

[0262] - Sending (S602) a resource request to a network node;

[0263] - Receiving (S604) from the network node a resource response indicating a resource authorization parameter, wherein the resource authorization parameter is associated with a combined resource pool; and

[0264] - Utilizing (S606) the combined resource pool according to the resource authorization parameter.

[0265] Item 49. A resource allocation server, the resource allocation server including a memory circuit, a processor circuit, and an interface, wherein the resource allocation server is configured to communicate with a plurality of resource allocation servers including a first resource allocation server of a first network, wherein the resource allocation server is configured to:

[0266] - Receive a first resource allocation request indicating a resource type from a requester; and

[0267] - Negotiate resource allocation with the first resource allocation server based on the resource type indicated in the first resource allocation request;

[0268] - wherein the resource allocation server is part of a network different from the first network.

[0269] Item 50. The resource allocation server according to any one of the preceding items 49, wherein the resource allocation server is configured to negotiate resource allocation with the first resource allocation server based on the resource type indicated in a second allocation request.

[0270] Item 51. The resource allocation server according to any one of the preceding items 49 to 50, wherein the negotiation of the resource allocation includes: determining whether an agreement is reached between the resource allocation server and the first resource allocation.

[0271] Item 52. The resource allocation server according to item 51, wherein the resource allocation server is configured to:

[0272] - When an agreement authorizing the resource allocation is reached between the resource allocation server and the first resource allocation server, generate a transaction in a resource allocation distributed ledger; and

[0273] - When the transaction on the resource allocation distributed ledger is verified, send a first resource allocation response indicating authorization of the resource to the requester.

[0274] Item 53. The resource allocation server according to any one of the preceding items 51 to 52, wherein the agreement is according to a set of protocol item parameters including a first protocol item parameter, wherein the first protocol item parameter indicates a criterion to be met for reaching the agreement.

[0275] Item 54. The resource allocation server according to any one of the preceding items 51 to 53, wherein the agreement is based on a joint consensus mechanism.

[0276] Item 55. The resource allocation server according to Item 54, wherein the joint consensus mechanism includes reaching a consensus in a distributed mode between the resource allocation server and the first resource allocation server.

[0277] Item 56. The resource allocation server according to any one of the preceding Items 54 to 55, wherein the joint consensus mechanism is based on a rule set and a service type.

[0278] Item 57. The resource allocation server according to Item 56, wherein the rule set includes a first rule, and the first rule includes one or more of the following items: a priority rule, and a fairness rule.

[0279] Item 58. The resource allocation server according to any one of the preceding Items 49 to 57, wherein the negotiation includes sending a second resource allocation request to the first resource allocation server.

[0280] Item 59. The resource allocation server according to Item 58, wherein the negotiation includes receiving a second resource allocation response from the first resource allocation server, and the second resource allocation response indicates a protocol indicator regarding the resource allocation indicated in the second allocation request.

[0281] Item 60. The resource allocation server according to any one of the preceding Items 51 to 59, wherein the resource allocation server is configured to:

[0282] - When no agreement authorizing the allocation is reached between the resource allocation server and the first resource allocation server, do not generate the transaction on the resource allocation distributed ledger.

[0283] Item 61. The resource allocation server according to any one of the preceding Items 52 to 60, wherein the resource authorization is an authorization for a part of the resource.

[0284] Item 62. The resource allocation server according to any one of the preceding Items 54 to 61, wherein the joint consensus mechanism is established between the resource allocation server and at least one resource allocation server among the multiple resource allocation servers before receiving the first resource allocation request.

[0285] Item 63. The resource allocation server according to any one of the preceding Items 52 to 62, wherein the resource allocation distributed ledger is associated with the resource allocation server and the multiple resource allocation servers.

[0286] Item 64. The resource allocation server according to any one of the preceding Items 52 to 62, wherein the resource allocation distributed ledger is a resource allocation distributed ledger dedicated to the resource allocation server of the network.

[0287] Item 65. The resource allocation server according to any one of the preceding Items 52 to 64, wherein the resource allocation distributed ledger is a resource allocation distributed ledger paired with the resource allocation server.

[0288] Item 66. The resource allocation server according to any one of the preceding Items 49 to 65, wherein the resources include one or more of the following: spectrum resources, time resources, and hardware resources.

[0289] Item 67. The resource allocation server according to any one of the preceding Items 52 to 66, the resource allocation server being configured to receive a confirmation indicator from the resource allocation distributed ledger when confirming the transaction on the resource allocation distributed ledger.

[0290] Item 68. A method performed by a resource allocation server, the method comprising the steps of:

[0291] - receiving (S104) a first resource allocation request indicating a resource type from a requester; and

[0292] - negotiating (S106) resource allocation with the first resource allocation server based on the resource type indicated in the first resource allocation request;

[0293] - wherein the resource allocation server is part of a network different from the first network.

[0294] Item 69. The method according to Item 68, wherein the method comprises the step of: negotiating (S112) resource allocation with the first resource allocation server based on the resource type indicated in a second allocation request.

[0295] Item 70. The method according to any one of the preceding Items 68 to 69, wherein the negotiation (S112) comprises: sending (S112A) the second resource allocation request to the first resource allocation server.

[0296] Item 71. The method according to any one of the preceding Items 68 to 70, wherein the negotiation (S106) comprises: determining (S106A) whether an agreement is reached between the resource allocation server and the first resource allocation.

[0297] Item 72. The method according to Item 71, the method comprising the steps of:

[0298] - When an agreement authorizing the resource allocation is reached between the resource allocation server and the first resource allocation server, a transaction is generated (S108) in the resource allocation distributed ledger;

[0299] - When the transaction on the resource allocation distributed ledger is verified, a first resource allocation response indicating authorization of the resource is sent (S110) to the requester.

[0300] Item 73. The method according to any one of Items 71 to 72, wherein the agreement is based on a set of protocol item parameters including a first protocol item parameter, and the first protocol item parameter indicates a criterion to be satisfied for reaching the agreement.

[0301] Item 74. The method according to any one of Items 71 to 73, wherein the agreement is based on a joint consensus mechanism.

[0302] Item 75. The method according to Item 74, wherein the joint consensus mechanism includes reaching a consensus in a distributed mode between the resource allocation server and the first resource allocation server.

[0303] Item 76. The method according to any one of Items 74 to 75, wherein the joint consensus mechanism is based on a rule set and a service type.

[0304] Item 77. The method according to Item 76, wherein the rule set includes a first rule, and the first rule includes one or more of the following items: a priority rule, and a fairness rule.

[0305] Item 78. The method according to any one of Items 70 to 77, wherein the negotiation (S112) includes receiving (S112B) a second resource allocation response from the first resource allocation server, and the second resource allocation response indicates a protocol indicator regarding the resource allocation indicated in the second allocation request.

[0306] Item 79. The method according to any one of Items 69 to 76, the method includes the following steps:

[0307] - When an agreement authorizing the allocation is not reached between the resource allocation server and the first resource allocation server, generating the transaction on the resource allocation distributed ledger is stopped (S109).

[0308] Item 80. The method according to any one of Items 72 to 79, wherein the resource authorization is an authorization of a part of the resource.

[0309] Item 81. The method according to any one of Items 72 to 80, wherein the joint consensus mechanism is established between the resource allocation server and at least one of the plurality of resource allocation servers before receiving the first resource allocation request.

[0310] Item 82. The method according to any one of Items 72 to 81, wherein the resource allocation distributed ledger is associated with the resource allocation server and the plurality of resource allocation servers.

[0311] Item 83. The method according to any one of Items 72 to 81, wherein the resource allocation distributed ledger is a resource allocation distributed ledger dedicated to the resource allocation servers of the network.

[0312] Item 84. The method according to any one of Items 72 to 81, wherein the resource allocation distributed ledger is a resource allocation distributed ledger paired with the resource allocation server.

[0313] Item 85. The method according to any one of the foregoing Items 68 to 84, wherein the resources include one or more of the following: spectrum resources, time resources, and hardware resources.

[0314] Item 86. The method according to any one of Items 75 to 84, the method comprising the steps of:

[0315] - When verifying the transaction on the resource allocation distributed ledger, receiving (S109) a verification indicator from the resource allocation distributed ledger.

[0316] The use of the terms "first", "second", "third" and "fourth", "firstly", "secondly", "thirdly", etc. does not imply any particular order, but is included to identify separate elements. Further, the use of the terms "first", "second", "third" and "fourth", "firstly", "secondly", "thirdly", etc. does not denote any order or importance, and on the contrary, "first", "second", "third" and "fourth", "firstly", "secondly", "thirdly", etc. are used to distinguish one element from another. It should be noted that the words "first", "second", "third" and "fourth", "firstly", "secondly", "thirdly", etc. are used here and elsewhere only for labeling purposes and do not refer to any particular spatial or temporal ordering. Moreover, the labeling of a first element does not imply the existence of a second element, and vice versa.

[0317] It can be realized that Figures 1 to 11Some circuits or operations are illustrated by solid lines and some circuits or operations are illustrated by dashed lines. The circuits or operations included by solid lines are those included in the broadest examples. The circuits or operations included by dashed lines are examples of circuits or operations that can be included in the circuits or operations of the solid-line examples, or as part of the circuits or operations of the solid-line examples, or as further circuits or operations that can be taken in addition to the circuits or operations of the solid-line examples. It should be appreciated that these operations need not be performed in the order presented. Also, it should be appreciated that not all operations need to be performed. The example operations can be performed in any order and in any combination.

[0318] Note that the word "comprising" does not necessarily exclude the presence of other elements or steps in addition to the listed elements or steps.

[0319] Note that the word "a" before an element does not exclude the presence of a plurality of such elements.

[0320] It should also be noted that any reference signs do not limit the scope of the claims, that the examples can be implemented at least in part by means of both hardware and software, and that several "means", "units" or "devices" can be represented by the same item of hardware.

[0321] The various example methods, apparatuses, nodes, and systems described herein are described in the general context of method steps or processes, which can be implemented in one aspect by a computer program product embodied in a computer-readable medium that includes computer-executable instructions (such as program code) executed by a computer in a networked environment. The computer-readable medium can include removable and non-removable storage devices including, but not limited to, read-only memory (ROM), random access memory (RAM), compact discs (CDs), digital versatile discs (DVDs), etc. In general, program circuitry can include routines, programs, objects, components, data structures, etc. that perform specified tasks or implement particular abstract data types. The computer-executable instructions, associated data structures, and program circuitry represent examples of program code for performing the steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents an example of the corresponding actions for implementing the functions described in such steps or processes.

[0322] Although the features have been shown and described, it should be understood that they are not intended to limit the claimed disclosure, and it will be apparent to those skilled in the art that various changes and modifications can be made without departing from the scope of the claimed disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The claimed disclosure is intended to cover all alternatives, modifications, and equivalents.

Claims

1. A network node, the network node comprising a memory circuit, a processor circuit, and an interface, wherein, The network node is configured to: Send a first resource allocation request to a first resource allocation server and send a second resource allocation request to a second resource allocation server; Receive a first resource allocation response from the first resource allocation server and receive a second resource allocation response from the second resource allocation server, wherein the first resource allocation response indicates first resource authorization parameters, and wherein the second resource allocation response indicates second resource authorization parameters; and Operate using a combined resource pool based on the first resource authorization parameters and the second resource authorization parameters, Wherein the first resource allocation request indicates a first service of a first service type selected from one or more service types; and wherein the second resource allocation request indicates a second service of a second service type selected from the one or more service types.

2. The network node according to claim 1, wherein, The first resource authorization parameters are associated with a first resource of a first type, wherein the first resource includes one or more of the following: spectrum resources, time resources, and hardware resources.

3. The network node according to claim 1, wherein, The second resource authorization parameters are associated with a second resource of a second type; wherein the second resource includes one or more of the following: spectrum resources, time resources, and hardware resources.

4. The network node according to claim 3, wherein, The combined resource pool combines the first resource and the second resource based on the first resource authorization parameters and the second resource authorization parameters.

5. The network node according to claim 3, wherein, The first resource and the second resource at least partially overlap.

6. The network node according to claim 1, wherein, The second resource allocation request depends on the first resource allocation request and / or the first resource allocation response.

7. The network node according to claim 1, wherein, The first resource allocation response includes information indicating a service corresponding to the first service of the first service type, and wherein the second resource allocation response includes information indicating a service corresponding to the second service of the second service type.

8. The network node according to claim 1, wherein, The first resource authorization parameters include information indicating the first resource associated with the first service of the first service type; wherein the second resource authorization parameters include information indicating the second resource associated with the second service of the second service type.

9. The network node according to any one of claims 3 to 8, wherein, The operation of using the combined resource pool based on the first resource authorization parameters and the second resource authorization parameters is based on combining the first resource and the second resource into the combined resource pool according to the first resource authorization parameters and the second resource authorization parameters.

10. The network node according to claim 7 or 8, wherein, The first resource authorization parameters indicate a service corresponding to the first service of the first service type, and the second resource authorization parameters indicate a service corresponding to the second service of the second service type.

11. The network node according to any one of claims 1 to 8, wherein, The network node is configured to receive a first resource request from a first wireless device.

12. The network node according to claim 11, wherein, The operation of using the combined resource pool based on the first resource authorization parameters and the second resource authorization parameters includes: transmitting to the first wireless device an authorization of the first resource indicated in the first resource authorization parameters and / or the second resource indicated in the second resource authorization parameters.

13. The network node according to any one of claims 3 to 8, wherein, The first resource authorization parameter includes a parameter indicating time-limited allocation of the first resource, and wherein the second resource authorization parameter includes a parameter indicating time-limited allocation of the second resource.

14. A wireless device, the wireless device comprising a memory circuit, a processor circuit, and a wireless interface, wherein, The wireless device is configured to: Send a resource request to a network node; Receive a resource response indicating resource authorization parameters from the network node, wherein the resource authorization parameters are associated with a combined resource pool; and Utilize the combined resource pool according to the resource authorization parameters, wherein the resource request indicates a service of a service type selected from one or more service types.

Images