Infrastructure sharing method and device using block chain and chip
Patent Information
- Application Number
- BR112025020282
- Authority / Receiving Office
- BR · BR
- Patent Type
- Applications
- Publication Date
- 2026-08-11
Smart Images

Figure 00000036_0000 
Figure 00000036_0001 
Figure 00000037_0000
Description
1 / 32 METHOD AND DEVICE FOR INFRASTRUCTURE SHARING USING BLOCKCHAIN AND CHIP BACKGROUND TO THE REVELATION 1. FIELD OF REVELATION
[001] The present disclosure relates to the field of communication systems and, more particularly, to a method of infrastructure sharing and to a device that can provide infrastructure sharing. 2. DESCRIPTION OF THE RELATED TECHNIQUE
[002] To cover a wide area, network operators need to deploy more base stations, which can be expensive due to the need for additional infrastructure and maintenance. As a result, network deployment can become a costly undertaking, and network operators need to carefully weigh the benefits of high-speed data rates against the costs of infrastructure deployment. Therefore, there is a need for infrastructure sharing so that future operators maintain good technology-based system coverage while anticipating affordable deployment expenses. SUMMARY
[003] One of the objectives of the present disclosure is to propose a method and apparatus for infrastructure sharing that can provide infrastructure sharing.
[004] In a first aspect of the present disclosure, a method of infrastructure sharing includes realizing infrastructure sharing between a first deployer and a second deployer using Petition 870250085849, dated 09 / 23 / 2025, page 8 / 98 2 / 32 a chain of blocks.
[005] In some embodiments of any of the above methods, infrastructure sharing includes a shared remote antenna and / or a shared fronthaul belonging to the second deployer being used for a user equipment (UE) belonging to the first deployer.
[006] In some embodiments of any of the above methods, the shared fronthaul is a link between a base station and the shared remote antenna.
[007] In some embodiments of any of the above methods, the blockchain includes a consortium chain, the first deployer and the second deployer belong to members of the consortium chain, or the first deployer and the second deployer are both approved by the consortium chain.
[008] In some embodiments of any of the above methods, infrastructure sharing between the first deployer and the second deployer is performed using a smart contract.
[009] In some forms of any of the above methods, the smart contract is created by the first implementer.
[0010] In some forms of any of the above methods, the smart contract contains an infrastructure that shares information.
[0011] In some embodiments of any of the above methods, infrastructure sharing information includes at least one of the following: a radio frequency (RF) performance of the antenna. Petition 870250085849, dated 09 / 23 / 2025, page 9 / 98 3 / 32 shared remote, a shared remote antenna location, a sharing duration, a geographic location, a base station switching location, a frequency band, a sharing type, sharing rate information, or a sharing negotiation.
[0012] In some embodiments of any of the above methods, the shared remote antenna and / or shared fronthaul belonging to the second deployer is agreed to be shared by the second deployer, the smart contract is called by the second deployer if a condition is verified, the smart contract is executed and a sharing permission is established.
[0013] In some embodiments of any of the above methods, the smart condition includes a license identifier (ID) that is approved when the shared remote antenna verifies a requirement.
[0014] In some embodiments of any of the above methods, the sharing type includes exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul.
[0015] In some embodiments of any of the above methods, the sharing type includes a non-exclusive share for the first deployer to use the shared remote antenna and / or the shared fronthaul.
[0016] In some embodiments of any of the above methods, a time pattern is defined in the smart contract to partition the usage periods for the first implementer and the second implementer, respectively. Petition 870250085849, dated 09 / 23 / 2025, page 10 / 98 4 / 32
[0017] In a second aspect of the present disclosure, an infrastructure sharing device includes an executor configured to perform infrastructure sharing between a first deployer and a second deployer using a blockchain.
[0018] In some embodiments of any of the above devices, infrastructure sharing includes a shared remote antenna and / or a shared fronthaul belonging to the second deployer being used for a first user equipment (UE) belonging to the first deployer.
[0019] In some embodiments of any of the above devices, the shared fronthaul is a link between a base station and the shared remote antenna.
[0020] In some embodiments of any of the above devices, the blockchain includes a consortium chain, the first deployer and the second deployer belong to the members of the consortium chain, or the first deployer and the second deployer are both approved by the consortium chain.
[0021] In some embodiments of any of the above devices, infrastructure sharing between the first deployer and the second deployer uses a smart contract.
[0022] In some forms of any of the above devices, the smart contract is created by the first implementer.
[0023] In some forms of any of the above devices, the smart contract contains a Petition 870250085849, dated 09 / 23 / 2025, page 11 / 98 5 / 32 infrastructure that shares information.
[0024] In some embodiments of any of the above devices, infrastructure sharing information includes at least one of the following: a radio frequency (RF) performance of the shared remote antenna, a location of the shared remote antenna, a sharing duration, a geographic location, a base station switching location, a frequency band, a sharing type, sharing rate information, or a sharing negotiation.
[0025] In some embodiments of any of the above devices, the shared remote antenna and / or shared fronthaul belonging to the second deployer is agreed to be shared by the second deployer, the smart contract is called by the second deployer if a condition is verified, the smart contract is executed and a sharing permission is established.
[0026] In some embodiments of any of the above devices, the smart condition includes a license identifier (ID) that is approved when the shared remote antenna verifies a requirement.
[0027] In some embodiments of any of the above devices, the sharing type includes exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul.
[0028] In some embodiments of any of the above devices, the sharing type includes non-exclusive sharing for the first deployer to use the shared remote antenna and / or fronthaul. Petition 870250085849, dated 09 / 23 / 2025, p. 12 / 98 6 / 32 shared.
[0029] In some versions of any of the above devices, a time pattern is defined in the smart contract to partition usage periods for the first deployer and the second deployer, respectively.
[0030] In a third aspect of the present disclosure, an infrastructure sharing device includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to execute any of the above methods.
[0031] In a fourth aspect of the present disclosure, a wireless communication device includes an adjuster configured to adjust a right of a spectrum block using a chain of blocks. Furthermore, the spectrum management device is configured to perform either of the above methods.
[0032] In a fifth aspect of the present disclosure, a wireless communication device includes an executor configured to perform any of the above methods.
[0033] In a sixth aspect of the present disclosure, a non-transient machine-readable storage medium has stored instructions that, when executed by a computer, cause the computer to execute any of the above methods.
[0034] In a seventh aspect of the present disclosure, a chip includes a processor, configured to call and execute a computer program stored in a memory, to cause a device in which the chip is installed to perform any of the above methods. Petition 870250085849, dated 09 / 23 / 2025, page 13 / 98 7 / 32
[0035] In an eighth aspect of the present disclosure, a computer-readable storage medium, on which a computer program is stored, causes a computer to execute any of the above methods.
[0036] In a ninth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to perform any of the above methods.
[0037] In a tenth aspect of the present disclosure, a computer program causes a computer to execute any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] To illustrate the modalities of the present revelation or related technique more clearly, the following Figures will be described in the modalities that are briefly introduced. It is obvious that the drawings are only some modalities of the present revelation; a person with ordinary skill in this field can obtain other Figures according to these Figures without paying the premise.
[0039] Figure 1 is a schematic diagram of a coverage comparison between mmW and the first frequency band (FR1) according to an embodiment of the present disclosure.
[0040] Figure 2 is a schematic diagram of a mass distributed multiple input and multiple output (MIMO) structure according to an embodiment of the present disclosure.
[0041] Figure 3 is a block diagram of an infrastructure sharing device in a communication network system according to an embodiment of Petition 870250085849, dated 09 / 23 / 2025, page 14 / 98 8 / 32 present revelation.
[0042] Figure 4 is a flowchart illustrating a method of infrastructure sharing according to an embodiment of the present disclosure.
[0043] Figure 5 is a schematic diagram of infrastructure sharing according to an embodiment of the present disclosure.
[0044] Figure 6 is a schematic diagram of infrastructure sharing according to an embodiment of the present disclosure.
[0045] Figure 7A is a schematic diagram of infrastructure sharing according to an embodiment of the present disclosure.
[0046] Figure 7B is a schematic diagram of infrastructure sharing according to an embodiment of the present disclosure.
[0047] Figure 8A is a schematic diagram of infrastructure sharing according to an embodiment of the present disclosure.
[0048] Figure 8B is a schematic diagram of infrastructure sharing according to an embodiment of the present disclosure.
[0049] Figure 9 is a block diagram of an infrastructure sharing device according to an embodiment of the present disclosure.
[0050] Figure 10 is a block diagram of a system for infrastructure sharing according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF MODALITIES
[0051] The modalities of the present disclosure are Petition 870250085849, dated 09 / 23 / 2025, page 15 / 98 9 / 32 described in detail with the technical issues, structural features, objectives achieved and effects with reference to the accompanying drawings below. Specifically, the terminology in the embodiments of the present disclosure is only to describe the purpose of a particular embodiment, but not to limit the disclosure. PROBLEM WITH THE TECHNIQUE
[0052] Millimeter wave (mmW) technology is being widely adopted for next-generation wireless networks due to its ability to offer high-speed data rates. However, one of the main disadvantages of mmW is its limited coverage range, which is significantly smaller than other frequency bands used for wireless communication. An example of coverage comparison is illustrated in Figure 1, where the mmW frequency band and the coverage difference of the first frequency band (FR1) is presented. This means that to cover a wide area, network operators need to deploy more base stations, which can be expensive due to the need for additional infrastructure and maintenance.As a result, mmW network deployment can become an expensive undertaking, and network operators need to carefully weigh the benefits of high-speed data rates against the infrastructure deployment costs. In the present disclosure, some embodiments present a method for future operators to maintain good system coverage based on mmW technology while anticipating affordable deployment expenses. BLOCK CHAIN Petition 870250085849, dated 09 / 23 / 2025, page 16 / 98 10 / 32
[0053] A blockchain is a type of distributed ledger technology (DLT) that includes growing lists of records, called blocks, that are securely linked using cryptography. Each block contains a cryptographic hash of the previous block, a timestamp, and transaction data (usually represented as a Merkle tree, where data nodes are represented by leaves). The timestamp proves that the transaction data existed when the block was created. Because each block contains information about the previous block, they effectively form a chain (compare to the linked list data structure), with each additional block linked to the previous ones. Consequently, blockchain transactions are irreversible, as once recorded, the data in any block cannot be retroactively altered without altering all subsequent blocks.
[0054] Blockchains can be managed by a peer-to-peer (P2P) computer network for use as a distributed public ledger, where nodes collectively adhere to a consensus algorithm protocol to add and validate new transaction blocks. Blockchain records are not immutable, since blockchain forks are possible; blockchains can be considered secure by design and exemplify a distributed computing system with high Byzantine fault tolerance. MMW
[0055] Millimeter wave (mmW) refers to a specific range of electromagnetic frequencies between 30 GHz and 300 GHz. This frequency range is considered a band. Petition 870250085849, dated 09 / 23 / 2025, p. 17 / 98 High-frequency 11 / 32 wavelength (mmW) is increasingly being explored for various wireless communication applications due to its ability to support high-speed, low-latency data transfer. mmW technology is particularly promising for the implementation of 5G networks and beyond, as it can provide data transfer rates of several gigabits per second, which are several times faster than current long-term evolving 4G (LTE) networks. The use of mmW technology can also enable the development of new applications and services, such as augmented reality and virtual reality, which require large amounts of data to be transferred in real time. However, the use of mmW technology also presents several challenges, such as signal attenuation and interference, which need to be addressed to fully realize its potential.Overall, mmW technology holds great promise for revolutionizing wireless communication and enabling a wide range of innovative applications. MIMO DISTRIBUTED IN MASS
[0056] Mass distributed multiple-input multiple-output (MIMO) is a cutting-edge technology that promises to revolutionize how wireless communication is performed. Figure 2 is a mass distributed multiple-input multiple-output (MIMO) structure according to an embodiment of the present disclosure. Figure 2 illustrates that, in some embodiments, the mass distributed MIMO structure involves the deployment of a large number of antennas over a wide area and the use of advanced signal processing algorithms to enable efficient, high-quality communication between devices. The technology has the potential to significantly increase the capacity and coverage of Petition 870250085849, dated 09 / 23 / 2025, page 18 / 98 12 / 32 wireless networks, reducing interference and power consumption.
[0057] Mass distributed MIMO is particularly well-suited for use in crowded and dense urban environments, where traditional cellular networks often struggle to provide adequate coverage and bandwidth. By utilizing multiple antennas and sophisticated beamforming techniques, mass distributed MIMO can provide high-speed, reliable connectivity to a large number of devices.
[0058] However, the implementation of massively distributed MIMO presents several challenges, such as the need for a large number of antennas and complex signal processing algorithms, which require significant computational power and energy. However, with continuous technological advancements, the potential benefits of massively distributed MIMO are expected to outweigh its challenges, paving the way for a new era of wireless communication.
[0059] Figure 3 illustrates that, in some embodiments, an infrastructure sharing device 10 in a communication network system 30 (e.g., non-terrestrial network (NTN) or terrestrial network), according to an embodiment of the present disclosure, is disclosed. The communication network system 30 includes the infrastructure sharing device 10. The infrastructure sharing device 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The processor 11 may be configured to implement proposed functions, procedures, and / or methods described in this description. Interface protocol layers Petition 870250085849, dated 09 / 23 / 2025, page 19 / 98 13 / 32 radio signals can be implemented in processor 11. Memory 12 is operationally coupled to processor 11 and stores a variety of information for operating processor 11. Transceiver 13 is operationally coupled to processor 11, and transceiver 13 transmits and / or receives a radio signal.
[0060] Processor 11 may include application-specific integrated circuit (ASIC), other chip assembly, logic circuit and / or data processing device. Memory 12 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage media and / or other storage device. Transceiver 13 may include baseband circuitry for processing radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so forth) that perform the functions described herein. The modules may be stored in memory 12 and executed by processor 11.Memory 12 can be implemented within processor 11 or external to processor 11, in which case it can be communicatively coupled to processor 11 by various means, as is known in the art.
[0061] In some embodiments, processor 11 is configured to perform infrastructure sharing between a first deployer (such as network operator A in Figure 6) and a second deployer (such as network operator B in Figure 6) using a blockchain. This can provide infrastructure sharing.
[0062] Figure 4 illustrates a method of Petition 870250085849, dated 09 / 23 / 2025, page 20 / 98 14 / 32 Infrastructure Sharing 200 according to an embodiment of the present disclosure. In some embodiments, the 200 method includes: a 202 block, performing infrastructure sharing between a first deployer and a second deployer using a blockchain. This can provide infrastructure sharing.
[0063] In some embodiments, infrastructure sharing includes a shared remote antenna and / or a shared fronthaul belonging to the second deployer being used for a user equipment (UE) belonging to the first deployer. In some embodiments, the shared fronthaul is a link between a base station and the shared remote antenna. In some embodiments, the blockchain includes a consortium chain, the first deployer and the second deployer belong to members of the consortium chain, or the first deployer and the second deployer are both approved by the consortium chain. In some embodiments, performing infrastructure sharing between the first deployer and the second deployer uses a smart contract. In some embodiments, the smart contract is created by the first deployer.
[0064] In some embodiments, the smart contract contains infrastructure sharing information. In some embodiments, the infrastructure sharing information includes at least one of the following: a radio frequency (RF) performance of the shared remote antenna, a location of the shared remote antenna, a sharing duration, a geographic location, a switching location of the Petition 870250085849, dated 09 / 23 / 2025, page 21 / 98 15 / 32 base station, a frequency band, a type of sharing, sharing rate information, or a sharing negotiation. In some embodiments, the shared remote antenna and / or the shared fronthaul belonging to the second deployer are agreed to be shared by the second deployer, the smart contract is called by the second deployer if a condition is verified, the smart contract is executed, and a sharing permission is established.
[0065] In some embodiments, the smart condition includes a license identifier (ID) that is approved when the shared remote antenna verifies a requirement. In some embodiments, the sharing type includes exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul. In some embodiments, the sharing type includes non-exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul. In some embodiments, a time pattern is defined in the smart contract to partition usage periods for the first deployer and the second deployer, respectively.
[0066] The examples given in this disclosure may be applied to IoT devices, NB-IoT devices, NR devices, LTE devices, but this disclosure is not limited to these. EXAMPLES
[0067] To solve the above technical problem, such as the issue of high costs associated with mmW network deployment, a possible solution is to share the deployment. Petition 870250085849, dated 09 / 23 / 2025, p. 22 / 98 16 / 32 infrastructure sharing among multiple network operators. By sharing the cost of infrastructure, operators can significantly reduce the cost of deploying mmW networks while still reaping the benefits of high-speed data rates. This approach can be particularly beneficial for smaller operators that may not have the resources to deploy mmW networks independently. Furthermore, infrastructure sharing can lead to more efficient use of resources, thus reducing the overall environmental impact of network deployment. However, for this approach to be successful, operators need to work together to ensure that infrastructure is deployed in a coordinated and efficient manner to avoid interference and other issues that could affect network performance.As illustrated in Figure 5, four operators share their infrastructure to provide full coverage, but in theory, they only pay 25% of the deployment cost.
[0068] As illustrated in Figure 6, the infrastructure sharing method for operators is as follows: assuming one operator (operator A) deploys the main network, which is connected to a base station. The base station can be considered a central processing unit (CPU) equipped with a switch, which is further connected to several remote antennas (APs). The link between the switch and the AP is called the fronthaul (FH). In some examples, assuming operator A deploys an AP (AP-A) and the FH that connects the switch and AP-A. While another operator (operator B) also deploys an AP (AP-B) connecting to the same switch. In this example, from a coverage perspective, coverage is extended by AP-A and AP-B, but the cost of Petition 870250085849, dated 09 / 23 / 2025, page 23 / 98 17 / 32 deployment for operator A is reduced due to the fact that the cost of the FH between the switch and AP-B is paid by operator B. Since AP-B is linked to the switch, operator A can use AP-B to serve a UE belonging to operator A. As for operator B, its infrastructure, in some examples AP-B and the corresponding FH, are shared by operator A. Thus, this is called infrastructure sharing between operators.
[0069] More specifically, when a UE belongs to operator A (UE-A), which is served by AP-A within the coverage of AP-A. When the UE leaves the coverage of AP-A and enters the coverage of AP-B, operator A can use AP-B to continue serving the UE. Thus, the coverage is extended. INFRASTRUCTURE SHARING METHOD
[0070] Infrastructure sharing can be accomplished through blockchain technology. For example, operator A and operator B belong to a consortium chain member, and operator A can create a smart contract containing the necessary AP information, such as RF performance, location, etc. Optionally, the information also includes the sharing duration, geographic location, switch location, frequency band, sharing type, etc. Furthermore, the smart contract also contains information about sharing fees. Figure 7A illustrates that, in some examples, when operator B agrees to share its AP and FH, operator B can request the smart contract. If the condition is met, the smart contract can be executed, and sharing permission is established. The condition could be a license ID for which the AP is approved. Petition 870250085849, dated 09 / 23 / 2025, page 24 / 98 18 / 32 shared check requirement. Sharing negotiation can also be recorded on the blockchain.
[0071] There can be different types of sharing. In one example, since an AP and an FH are shared by operator A, there is a long-term exclusive share, as illustrated in Figures 7A and 7B. This means that operator B cannot use the AP for its own use during the sharing period.
[0072] Figure 8A and Figure 8B illustrate that, in another example, the sharing period is not continuous and is swapped with the usage period of operator B. In this example, operator A and operator B can use AP-B to serve their own UEs. In this example, there may be a collision on AP-B for both operators A and B if they intend to use it at the same time. To solve this problem, a time pattern can be defined in the smart contract to partition the usage period for operators A and B, respectively.
[0073] In some modalities, infrastructure sharing negotiation is conducted via blockchain. First, the initial operator and another operator or supplier, etc., who wishes to be the new potential operator, must be a node in a blockchain dedicated to infrastructure sharing negotiation. An example is that this blockchain could be a consortium blockchain, and the consortium could be established by the governmental authority, operators, blockchain infrastructure builders, etc. To become a node on the blockchain, it is necessary to become a member of the consortium or be approved by the consortium. A node can have a node account with a Petition 870250085849, dated 09 / 23 / 2025, page 25 / 98 19 / 32 account address, which serves as a node identifier. The account may contain one or more pieces of information relevant to the transaction, such as the account balance used for transaction payment and information relevant to authentication, where authentication is used to prove that the user is authorized to participate in the transaction. This authentication may be issued by a government authority or another party. The user may be authenticated if certain conditions are met. For example, a condition may be certification to test whether the operator uses the infrastructure, its equipment meets regulations, is controlled by out-of-band interference requirements, or conforms to a standard of a target / requested technology, for example, new radio (NR), a 3GPP technology, or a Wi-Fi or IEEE technology. The transaction may take the form of an auction or a non-auction.For auction trading, an operator can set an initial price for the target spectrum segment and call for auction. Potential operators can bid for the right to use it. The auction process is described as follows: the operator (such as operator A in Figure 6) creates a smart contract for the auction and shares the smart contract address with all nodes interested in participating in the auction. In some modalities, the creation of the smart contract for the auction is based on a technological dimension. In some modalities, the technological dimension includes one or more technologies to be used in the spectrum block. In some modalities, one or more technologies include at least new radio (NR), a 3GPP technology, or a Wi-Fi or IEEE technology.
[0074] In a smart contract, he may need Petition 870250085849, dated 09 / 23 / 2025, page 26 / 98 20 / 32 all the granularity information presented above and the conditions for calling the smart contract are at least one of the following: 1) the consortium member; 2) the operator's account has sufficient funds in its balance account to trigger the bidding; 3) the operator has authentication to participate in the negotiation. In some modalities, money includes a coin or a token.
[0075] A smart contract can be a program stored in a blockchain that is executed when one or more predetermined conditions are met. A smart contract is used to automate the execution of an agreement so that all participants can be immediately certain of the outcome, without the involvement of any intermediary or loss of time. A smart contract can also automate a workflow, triggering a subsequent action when one or more conditions are met.
[0076] Coins refer to any cryptocurrency that has an autonomous and independent blockchain, such as Bitcoin. These cryptocurrencies are initialized from scratch, and the wider network is explicitly designed to achieve a specific goal. For example, Bitcoin exists as a censorship-resistant store of value and a medium of exchange that has a fixed and secure monetary policy. Bitcoin's native token, BTC (i.e., bitcoins), is the most liquid cryptocurrency on the market and has both the largest market capitalization and the largest realized market capitalization in the cryptocurrency sector. Coin projects often draw inspiration from past technologies or other cryptocurrencies and combine them into an innovative network geared towards a specific purpose. Another example of a coin, Ethereum's Ether (ETH) is the native coin. Petition 870250085849, dated 09 / 23 / 2025, page 27 / 98 Ethereum is a 21 / 32 smart contract platform for creating general-purpose computer programs that run on a decentralized blockchain. Instead of focusing on financial data, Ethereum focuses on arbitrary program data that can encompass anything from games to social networks. Ether is used to send / receive, manage assets, pay gas fees, and interact with decentralized applications on the network.
[0077] Tokens are a unique disbursement of broader smart contract platforms, such as Ethereum, that allow users to create, issue, and manage tokens that are derived from the primary blockchain. Tokens occupy a unique corner of the cryptocurrency market, where they function as utility tokens within an application's ecosystem to incentivize certain behaviors or pay fees. A token can refer to a digital unit of value that represents an asset or utility. Unlike coins, tokens do not have their own blockchain and are issued on top of existing networks. Unlike coins, tokens are not mined in the transaction validation process. Instead, they are minted.
[0078] In addition to these, the smart contract may contain other information, such as bid expiration time or remaining time; holder ID or holder signature; holder's smart contract account address; the bid amount each time the contract is called / triggered. After creating the smart contract, the smart contract can be published on the blockchain by the blockchain miner. In return, the holder can obtain a contract address, with which potential users can call the contract. Petition 870250085849, dated 09 / 23 / 2025, page 28 / 98 22 / 32 smart. Holders can share the address with potential users. As a potential user, they can use the smart contract address to trigger the smart contract to bid in the auction. Once the smart contract is triggered, it may first check if the expiration time has been reached; if so, the user can no longer trigger the smart contract. But if not, the smart contract may continue to check if the user's conditions are all met; the smart contract may automatically execute a fee transaction of a predefined bid amount from the user's account balance to the smart contract account and update the most recent user ID (or address) with the highest bid.When the auction expiration time ends, the smart contract can automatically transfer the final amount of money bid from the smart contract's account to the account holder's account, and simultaneously return the money to the accounts of all users who lost the auction. Then, the smart contract can record the data about the infrastructure sharing fee transaction in the ledger, and the smart contract can also update the infrastructure sharing data structure.
[0079] For non-auction, on the other hand, non-auction requires a fixed trading fee. This means that when the smart contract is called / triggered by a user (such as a trader), the transaction can be carried out and the right to use can be issued. Similarly, to call the smart contract, the user's conditions must be met, such as the user's money in the account balance must be equal to or greater than the requested trading fee; Petition 870250085849, dated 09 / 23 / 2025, page 29 / 98 23 / 32 The user needs to obtain authentication. In this case, it is important to note that when multiple users have successfully called the smart contract, the right to use it can be issued to multiple users. When there are multiple users who obtain infrastructure sharing within the same frequency block for the same time period and geographic location, the user needs to execute the access rule to avoid collisions, such as listen before speaking (LBT). The smart contract can be created to control the number of users so that the collision level is not high. For example, the holder (such as an operator) can set a maximum number of calls to the smart contract; every time the smart contract is successfully called by a user, the number can be reduced to zero.When the number reaches zero, the smart contract cannot be called / triggered again, achieving control over the number of users that are issued (granted) with infrastructure sharing.
[0080] In another example, when an operator obtains infrastructure sharing through the process described above, the user may be authorized to further trade their right in a second market.
[0081] Figure 9 illustrates an infrastructure sharing device 1700 according to an embodiment of the present disclosure. The infrastructure sharing device 1700 includes an executor 1701 configured to perform infrastructure sharing between a first deployer and a second deployer using a blockchain. This can provide infrastructure sharing.
[0082] In some modalities, sharing Petition 870250085849, dated 09 / 23 / 2025, page 30 / 98 24 / 32 infrastructure sharing includes a shared remote antenna and / or a shared fronthaul belonging to the second deployer being used for user equipment (UE) belonging to the first deployer. In some embodiments, the shared fronthaul is a link between a base station and the shared remote antenna. In some embodiments, the blockchain includes a consortium chain, the first deployer and the second deployer belong to the consortium chain, or the first deployer and the second deployer are both approved by the consortium chain. In some embodiments, performing infrastructure sharing between the first deployer and the second deployer uses a smart contract. In some embodiments, the smart contract is created by the first deployer.
[0083] In some embodiments, the smart contract contains infrastructure sharing information. In some embodiments, the infrastructure sharing information includes at least one of the following: a radio frequency (RF) performance of the shared remote antenna, a location of the shared remote antenna, a sharing duration, a geographic location, a base station switching location, a frequency band, a sharing type, sharing rate information, or a sharing negotiation. In some embodiments, the shared remote antenna and / or the shared fronthaul belonging to the second deployer are agreed to be shared by the second deployer; the smart contract is called by the second deployer if a condition Petition 870250085849, dated 09 / 23 / 2025, page 31 / 98 Once 25 / 32 is verified, the smart contract is executed and a sharing permission is established.
[0084] In some embodiments, the smart condition includes a license identifier (ID) that is approved when the shared remote antenna verifies a requirement. In some embodiments, the sharing type includes exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul. In some embodiments, the sharing type includes non-exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul. In some embodiments, a time pattern is defined in the smart contract to partition usage periods for the first deployer and the second deployer, respectively.
[0085] The commercial interests for some embodiments are as follows: 1. To improve spectrum utilization efficiency. 2. To provide flexible spectrum sharing. 3. Some embodiments of this disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, assemblers, including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc., drones (unmanned aerial vehicles), smartphone manufacturers, communication devices for use in public safety, AR / VR device manufacturers, for example, gaming, conferences / seminars, educational purposes. Some embodiments of this disclosure are a combination of techniques / processes that can be adopted in the 3GPP specification to create a final product. Petition 870250085849, dated 09 / 23 / 2025, page 32 / 98 26 / 32 embodiments of this disclosure may be adopted in licensed and unlicensed or shared 5G NR spectrum communications. Some embodiments of this disclosure propose technical mechanisms.
[0086] Figure 10 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. The embodiments described herein can be implemented in the system using any suitably configured hardware and / or software. Figure 10 illustrates the system 700, including a radio frequency (RF) circuit 710, a baseband circuit 720, an application circuit 730, a memory / storage 740, a screen 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, coupled together at least as illustrated. The application circuit 730 may include, but is not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors.Processors can be coupled to memory / storage and configured to execute instructions stored in memory / storage to enable various applications and / or operating systems running on the system.
[0087] The 720 baseband circuit may include, but is not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuit may handle various radio control functions that enable communication with one or more radio networks via the Petition 870250085849, dated 09 / 23 / 2025, page 33 / 98 27 / 32 RF circuit. Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency switching, etc. In some embodiments, the baseband circuitry may provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMANs), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be called a multimode baseband circuitry.
[0088] In several embodiments, the 720 baseband circuit suite may include circuits for operating with signals that are not strictly considered to be at a baseband frequency. For example, in some embodiments, the baseband circuits may include circuits for operating with signals at an intermediate frequency, which is between a baseband frequency and a radio frequency. The 710 RF circuit suite may enable communication with wireless networks using electromagnetic radiation modulated through a non-solid medium. In several embodiments, the RF circuit suite may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In several embodiments, the 710 RF circuit suite may include circuit suites for operating with signals that are not strictly considered to be at a radio frequency. For example, in some embodiments, Petition 870250085849, dated 09 / 23 / 2025, p. 34 / 98 28 / 32 RF circuit assemblies may include circuit assemblies for operating with signals at an intermediate frequency, which is between a baseband frequency and a radio frequency.
[0089] In various embodiments, the transmitter circuit assembly, the control circuit assembly, or the receiver circuit assembly discussed above in relation to the user equipment, eNB or gNB, may be incorporated in whole or in part into one or more RF circuit assemblies, baseband circuits, and / or application circuits. As used herein, circuit assembly may refer to, be part of, or include an Application-Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or grouped) and / or a memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality.In some embodiments, the electronic device circuitry may be implemented in, or the functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuit, application circuit, and / or memory / storage may be implemented together in a system-on-a-chip (SOC). The memory / storage may be used to load and store data and / or instructions, for example, for the system. The memory / storage of an embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM). Petition 870250085849, dated 09 / 23 / 2025, page 35 / 98 29 / 32 and / or non-volatile memory, such as flash memory.
[0090] In various embodiments, the 780 I / O interface may include one or more user interfaces designed to allow user interaction with the system and / or peripheral component interfaces designed to allow interaction of peripheral components with the system. User interfaces may include, but are not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB (Universal Serial Bus) port, an audio connector, and a power supply interface. In various embodiments, the 770 sensor may include one or more sensor devices to determine environmental conditions and / or system-related location information.In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuit and / or the RF circuit to communicate with components of a positioning network, for example, a Global Positioning System (GPS) satellite.
[0091] In various embodiments, the 750 screen may include a screen, such as a liquid crystal display and a touch screen. In various embodiments, the 700 system may be a mobile computing device, such as, but not limited to, a laptop-type computing device, a tablet-type computing device, a netbook-type computer, an ultrabook-type computer, a telephone. Petition 870250085849, dated 09 / 23 / 2025, page 36 / 98 30 / 32 smart, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. When appropriate, the methods described in this document can be implemented as a computer program. The computer program can be stored on a storage medium, such as a non-transient storage medium.
[0092] A person of ordinary skill in the art understands that each of the units, algorithms, and steps described and disclosed in the embodiments of the present disclosure are performed using electronic hardware or combinations of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the application condition and the design requirement for a technical plan. A person of ordinary skill in the art may use different ways of performing the function for each specific application, provided such embodiments do not exceed the scope of the present disclosure. It is understood by a person of ordinary skill in the art that they may refer to the working processes of the system, device, and unit in the aforementioned embodiment, since the working processes of the system, device, and unit mentioned above are basically the same. For ease of description and simplicity, these working processes will not be detailed.
[0093] It is understood that the system, device, and method revealed in the modalities of the present revelation can be realized in other ways. The aforementioned modalities are merely exemplary. The division of the units is based solely on logical functions, while other divisions exist in the realization. It is possible that a plurality of Petition 870250085849, dated 09 / 23 / 2025, page 37 / 98 31 / 32 units or components may be combined or integrated into another system. It is also possible that some characteristics may be omitted or ignored. On the other hand, the mutual coupling shown or discussed, direct coupling or communicative coupling operate through some ports, devices or units, indirectly or communicatively, by means of electrical, mechanical or other types of forms.
[0094] The units as separating components for explanation are either physically separate or not. The display units are either physical units, i.e., located in one place or distributed across a plurality of network units. Some or all of the units are used according to the purposes of the modalities. Furthermore, each of the functional units in each of the modalities may be integrated into a physically independent processing unit, or integrated into a processing unit with two or more than two units.
[0095] If the software function unit is implemented, used, and sold as a product, it may be stored on a computer-readable storage medium. Based on this understanding, the design of the technique proposed by the present disclosure may be implemented essentially or partially in the form of a software product. Or, a portion of the design of the technique beneficial to conventional technology may be implemented as the form of a software product. The software product on the computer is stored on a storage medium, including a plurality of commands for a computing device (such as a personal computer, a server, or a network device) to execute all or some of the steps disclosed by the embodiments. Petition 870250085849, dated 09 / 23 / 2025, page 38 / 98 32 / 32 of the present disclosure. Storage media includes a USB drive, a portable hard drive, read-only memory (ROM), random access memory (RAM), a floppy disk, or other types of media capable of storing program code.
[0096] Although the present disclosure has been described in connection with what are considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the embodiments disclosed, but is intended to cover various arrangements made without departing from the scope of the broader interpretation of the appended claims. Petition 870250085849, dated 09 / 23 / 2025, page 39 / 98
Claims
1 / 3 CLAIMS 1. INFRASTRUCTURE SHARING METHOD characterized by comprising: performing infrastructure sharing between a first deployer and a second deployer using a blockchain.
2. METHOD, according to claim 1, characterized by infrastructure sharing comprising that a shared remote antenna and / or a shared fronthaul belonging to the second deployer is used for a user equipment (UE) belonging to the first deployer.
3. METHOD, according to claim 2, characterized in that the shared fronthaul is a link between a base station and the shared remote antenna.
4. METHOD, according to any one of claims 1 to 3, characterized in that the blockchain comprises a consortium chain, in that the first implementer and the second implementer both belong to the consortium chain, or in that the first implementer and the second implementer are both approved by the consortium chain.
5. METHOD, according to any one of claims 1 to 4, characterized by performing infrastructure sharing between the first deployer and the second deployer using a smart contract.
6. METHOD, according to claim 5, characterized in that the smart contract is created by the first implementer. Petition 870250085849, dated 09 / 23 / 2025, page 40 / 98 2 / 3 7. METHOD, according to claim 5 or 6, characterized by the smart contract containing infrastructure sharing information.
8. METHOD, according to claim 7, characterized in that the infrastructure sharing information comprises at least one of the following: a radio frequency (RF) performance of the shared remote antenna, a location of the shared remote antenna, a sharing duration, a geographic location, a base station switching location, a frequency band, a sharing type, information on sharing rates, or a sharing negotiation.
9. METHOD, according to any one of claims 5 to 8, characterized in that the shared remote antenna and / or the shared fronthaul belonging to the second deployer is agreed to be shared by the second deployer, the smart contract is called by the second deployer if a condition is verified, the smart contract is executed, and a sharing permission is established.
10. METHOD, according to claim 9, characterized by the intelligent condition comprising a license identifier (ID) that is approved when the shared remote antenna verifies a requirement.
11. METHOD, according to any one of claims 8 to 10, characterized in that the type of sharing comprises exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul. Petition 870250085849, dated 09 / 23 / 2025, p. 41 / 98 3 / 3 12. METHOD, according to any one of claims 8 to 10, characterized in that the type of sharing comprises a non-exclusive sharing for the first deployer to use the shared remote antenna and / or the shared fronthaul.
13. METHOD, according to claim 12, characterized by a time pattern being defined in the smart contract to partition the usage periods for the first implementer and the second implementer, respectively.
14. INFRASTRUCTURE SHARING DEVICE characterized by being configured to implement the method as defined in any one of claims 1 to 13.
15. CHIP characterized by including: a processor, configured to call and execute a computer program stored in a memory, to cause a device in which the chip is installed to execute the method, as defined in any of claims 1 to 13. Petition 870250085849, dated 09 / 23 / 2025, p. 42 / 98