Patent Publication Number: US-2021176132-A9

Title: Smallcell Network Deployment, Optimization and Management based on Blockchain Technology

Description:
FIELD OF THE INVENTION 
     A method and apparatus for deploying, optimizing and managing smallcell network with blockchain technology is disclosed. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG. 1  is a schematic diagram showing an architecture of a smallcell network 
         FIG. 2  is another flowchart showing the connection and communication between the smallcell network and the core network. 
         FIG. 3  is another flowchart diagram showing the internal components of the operator&#39;s core network. 
         FIG. 4  is a flow-chart showing a method to deploy, optimize and manage the smallcell network. 
         FIG. 5  is a chart showing the description of the Smallcell ID, Spectrum Amount, Location and Rent Duration 
         FIG. 6  is a flowchart showing the overall data exchange between user terminal and the smallcell. 
         FIG. 7  is a graph showing the relationship between the USER TRAFFIC AMOUNT over TIME and the active state of a smallcell 
         FIG. 8  is another graph showing the relationship between the Frequency Spectrum over time. 
         FIG. 9  is a schematic diagram showing the architecture of smallcell network 
         FIG. 10  is a flowchart showing how the user terminal sends a request to connect to smallcell 
         FIG. 11  is another flowchart showing that any payment, transaction, user and smallcell information, user and smallcell data, between user terminal and smallcell; and between smallcell and user terminal is recorded in smallcell blockchain; and 
         FIG. 12  is another flowchart showing that any payment, transaction, smallcell information, smallcell data between smallcells in the network is recorded in the smallcell blockchain. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     While the present invention is described herein with reference to the illustrative embodiments for particular applications, it should be understood that the invention is not limited thereto. Those skilled in the art with access to the teachings provided herein will recognize additional modifications, applications, and embodiments within the scope thereof and additional fields in which the invention would be of significant utility. 
     In the detailed description of embodiments that follows, references to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. 
     Turning now to  FIG. 1  an architecture  10  a smallcell network is shown. Smallcell communication devices  12 ,  14 ,  16 .  36 ,  38 ,  40  are deployed at various locations randomly and/or at predetermined locations. A few smallcells can create a cluster  18 . A cluster can be of any size, that is, a cluster of smallcells can contain any number of smallcells. 
     There may be smallcells in the network which are not inside and/or pan of any cluster  18 . Any smallcell can have a wired  30 ,  32 ,  50 ,  54  and/or wireless connection  20 ,  52  to another smallcell in the same cluster and/or also with another smallcell in another cluster. 
     These inter-smallcell connections carry any kind of data between smallcells. Smallcell can have directional  22 ,  24 ,  26 ,  28 ,  42 ,  44 ,  46 ,  48  antennas and/or omnidirectional antennas  34 ,  56  to communicate with user terminals  58 ,  62 . User terminals are wireless communication devices which communicate with smallcells devices&#39; antennas  22 ,  24 ,  26 ,  28 ,  42 ,  44 ,  46 ,  48  using its own antennas  60 ,  64 . 
     A user terminal can be any type of device which is authorized by the service operator and/or smallcell network. A user terminal carry an identification module called Subscriber Identity Module (SIM) card. 
       FIG. 2  shows  68 , the connection and communication between the smallcell network and the core network  72 . Communication link  72 , between the smallcell network cluster  70  and the operator&#39;s core network  74 , is capable of carrying any type of information in any format using any kind of communication protocol to core network  74  from smallcell network  70  and from core network  74  to smallcell network  70 . Operator&#39;s core network  74  is connected to internet using a separate link  76 . Link  76  carries any type of traffic in any format using any communication protocol. 
       FIG. 3  shows the internal components of the operators core network. Smallcell Database  82 , saves and stores all information about all smallcells in smallcell network. User Terminal Database saves and stores all information about user terminals which are connected to any smallcell in operator&#39;s network. Smallcell Coin Miner  84 , mines smallcell coins, stores smallcell coins, shares smallcell coins with other smallcells in the smallcell network. Smallcell Coin Miner  84 , also saves and stores all smallcell coin mining, and transaction history. This history consists of which smallcell(s) mined how many smallcell coins, at which time, and how many of these coins are spent and the reason for spending. For example, if a particular smallcell mined  100  smallcell coins on Oct. 7 between 4:00-5:00 AM (EST) at Fairfax country location and spent 25 of these 100 smallcell coins to rent a spectrum at the location or any other location, this record is saved in that format. Smallcell Database, User Terminal Database, Smallcell Coin Miner, Data and Session Management components (servers) are connected to each other  89 . 
       FIG. 4  shows a method to deploy, optimize and manage the smallcell network. 
       FIG. 4  shows a method  90  of creating small cell network, and authorizing transactions. The method  90  may be implemented as a set of executable logic instructions stored in at least one machine- or computer-readable storage medium such as random access memory (RAM), read only memory (ROM), programmable ROM (PROM), flash memory, firmware, microcode, etc. in configurable logic such as, for example, programmable logic arrays (PLAs), field programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), in fixed functionality hardware using circuit technology such as, for example, application specific integrated circuit (ASIC), complementary metal oxide semiconductor (CMOS) or transistor logic (TTL) technology, or any combination thereof. For example, computer program code to carry out operations shown in the method  90  may be written in any combination of one or more programming languages, including an object-oriented programming languages such as “C” programming language or similar programming languages. Moreover, various aspects of the method  90  could be implemented as embedded logic of a processor using any of the aforementioned circuit technologies. 
     Illustrated processing block  94  defines the initial cluster size of smallcell network. Initial cluster size shows the number of smallcells in the same network of a cluster which communicates with each other through wireless and/or wireline links. 
     Processing block  96  shows that any smallcell which becomes part of the network creates communication links with other smallcells in the network. This communication link can be any wireless and/or wireline link. 
     Processing blocks  98 ,  100  and  102  show the process of requesting the spectrum. Each smallcell requests a particular amount of spectrum far a particular amount of duration. This request is shared with other smallcells over communication interface  30 ,  32 ,  20 ,  50 ,  54 ,  52 . Each smallcell inside the same network cluster votes for that request and sends the vote back to original smallcell requesting the spectrum resources. If at least half of the smallcells vote for YES (8 out of 15), spectrum resource is rented out to the requesting smallcell. Each smallcell holds a table that shows the spectrum in use, and spectrum not in use, and smallcell requests spectrum based on this real-time spectrum information in the table.  FIG. 5, 200  shows an example of a spectrum lookup table held by each smallcell in smallcell network. Spectrum rent record is created if a particular smallcell is approved to use a frequency spectrum and/or range of frequency spectrum. Each record consists of duration of the rent of the spectrum  208 , amount of the spectrum rented out to smallcell  204 , location of the rent of the spectrum  206 , smallcell identification  202  of the smallcell which owns and uses the spectrum. Each row of the table  200  shows data about the same smallcell, and different rows of the table show information regarding different smallcells. 
     Processing block  104  shows the procedure that when a smallcell is rejected to rent and utilize the spectrum, smallcell will wait for a random amount of time to make a request to rent the spectrum again,  98 . 
     If a smallcell has been rejected N times already, this smallcell is not able to make a request to rent any amount of spectrum in the network of which smallcell wants to be part of. Therefore, smallcell will be removed from the smallcell network cluster and network cluster size will be reduced by  1 ,  92 . 
     Processing block  106  shows that the spectrum will be rented to the smallcell who made the request to rent the spectrum  98  if other smallcells in the cluster give YES votes to the request to rent the spectrum. In other words, smallcell which is requesting the spectrum should receive majority of positive votes (YES) from other smallcells in the network cluster. Once smallcell owns right to transmit power in the spectrum rented, smallcell starts transmitting data to and from user terminals in its network coverage. 
     Processing block  114  shows that once smallcell&#39;s request to rent the frequency spectrum is approved, UEs which are in the radio frequency (RF) coverage of the smallcell recognize that this smallcell is a live and signal transmitting smallcell, and UEs make request to connect to this smallcell. User terminals recognize the smallcell as live and transmitting smallcell it user terminal can scan and read the physical cell identity (PCI) of the smallcell. Once user terminal completes all data transmission to smallcell, and also when smallcell completes all data transmission to the user terminal, user terminal will disconnect from the smallcell,  116 . 
     Processing block  118  identifies the amount of all kind of network and smallcell resources used by user terminal, determines the payment method, and performs transaction to make the payment to smallcell for the amount of resources used during the data transmission from and to user terminal.  FIG. 6  shows the overall data exchange between user terminal and the smallcell to perform the payment transaction and resource usage determination  300  shows signaling flow between user terminal and smallcell. User terminal  302  exchanges messages with smallcell  304  to determine the amount of resources consumed by user terminal. After user terminal completes the data transmission to and from the smallcell user terminal sends ‘Calculate Resource Consumption’ message  306  to smallcell. Smallcell confirms ‘Calculate Resource Consumption’ message by sending ‘Resource Calculation Started’ message  308  back to user terminal. As a next step, smallcell calculates amount of resources consumed by user terminal and sends message  310  with Smallcell Coin Units (SCC) information. After receiving Smallcell Coin Unit information from the smallcell, user terminal performs its own calculations  312  to calculate the amount of resources that user terminal has used during the connection and communication with smallcell. If the difference between the resource consumption calculations is less than some number, user terminal confirms the consumed amount  314 . If the difference between the resource consumption calculations is more than some number, user terminal rejects the usage, and requests smallcell to recalculate the resource consumption  316 . After smallcell resource consumption recalculations, if the difference between calculated number is still higher than some percentage, smallcell will ask for more information from user terminals. For example, smallcell asks for the time duration during which user terminal has been connected to the smallcell, and the moment of time that user terminal was disconnected from the smallcell. Smallcell investigates if there was any moment that user terminal lost data or voice connection with smallcell, this was not captured by smallcell. All the information that smallcell uses for further verification of the resource consumption amount, smallcell will ask user terminal to send its own log information. After resource consumption is confirmed by user terminal and as a next step, smallcell will send  318  the list of supported cryptocurrencies by this cluster of smallcell network. User terminal selects one and/or more cryptocurrencies and initiates the transaction towards smallcell  320 . This transaction is recorded in smallcell blockchain  320 . In order to record this transaction in blockchain, for user terminal, user terminal&#39;s International Mobile Subscriber Identifier (IMSI) number is used as private key in the block, and user terminal&#39;s phone number is used as public key in the block. For smallcell, combination of Medium Access Control (MAC) number is used as private key, and smallcell product serial number is used as public key in the blockchain. After payment is sent from user terminal to smallcell using blockchain technology, smallcell confirms the payment  322 . After transaction is successfully completed, user terminal sends disconnection request  324  to smallcell. Smallcell confirms the disconnection request  326  and user terminal disconnects from smallcell and smallcell network. 
     Processing block  108  shows process that checks if smallcell has active traffic going to any user terminal and/or coming from any user terminal. If any user terminal traffic goes through the smallcell, smallcell is in ACTIVE state.  FIG. 7  shows the active state  408  of a smallcell. Similarly, if there is no user terminal related traffic going through the smallcell, smallcell is in IDLE stale  402 ,  406 . There is also a third state which is Mining In the Background (MIB) state  404 . In MIB state  404 , smallcell has an active user terminal traffic, however this user terminal traffic is small and smallcell has hardware and software resources to mine Smallcell coin simultaneously while transmitting data to user terminal and receiving data from user terminal. 
     Processing block  110  shows the procedure that if smallcell is in IDLE state  402 ,  406 , smallcell uses its hardware and software resources to mine the Smallcell Coin (SCC).  FIG. 8  shows the number of Smallcell Coins that smallcell mines based on IDLE time and frequency available. For example, when smallcell is IDLE for 1 MHz and for 1 second, smallcell mines 1 smallcell coin (SCC)  502 . If smallcell is IDLE for 10 MHz and 1 second, smallcell mines  10  smallcell coins (SCCs),  504 . Similarly, if smallcell is IDLE for 15 MHz and 10 seconds, smallcell mines  150  Smallcell Coins (SCCs)  506 . 
     For IDLE 1 hour (3600 seconds) of 10 MHz spectrum, each smallcell mines 36000 CC. Smallcell produces smallcell coin to use it for at least one of the payment to other smallcells, and payment for all services smallcell receives from other smallcells, from individuals, from people, from software centers, from hardware centers, from cloud centers, from data centers, from service providers, and from any party providing direct and indirect service to smallcells. 
       FIG. 9  shows the architecture of smallcell network  600  where two smallcells request the same amount of spectrum resources at the same time, where at that location there is only one set of spectrum resource available which is the spectrum resource two smallcells request to rent at the same time. Each smallcell requesting the spectrum to rent sends the request to all other smallcells in the network. Smallcell  602  requests to rent the spectrum and sends this request using link  608  to smallcell  604  and smallcell  606 . Smallcell  604  request to rent spectrum and sends its request to smallcell  602  using the link  610  and sending the same request to smallcell  606  using the link  610 . 
     Links between smallcells  602 ,  604 ,  606  are two-way links which means that each smallcell send information with other smallcell simultaneously. Each link is separate from the other link physically and/or logically. During the operation there might be some tie cases. One example tie case might be defined as, if there are 3 small cells in a particular cluster  600  and two of these small cells  602 ,  604  ask for exactly the same amount of spectrum resource for exactly the same amount of duration. When small cells send resource request to each other  608 ,  610 , they will also create a random number and send this number as pan of their message. Each smallcell will check the resource request and if the resource request matches in terms of bandwidth and the time duration of the rent, smallcell which has the high random number will have access to the resources, if a smallcell has an access to resources in this tie breaking scenario, the smallcell who wins (has right to own the spectrum requested) at this time, will divide the generated random number by a pre-defined number in the next tie scenario. If smallcell does not win (no right to own the spectrum requested) at this time, in the next tie scenario smallcell will multiply the generated random number by a pre-defined number. And these divisions and multiplications will be increased and decreased by a pre-defined number at each time. This method creates fairness in owning the spectrum resources in smallcell network. 
     In  FIG. 10 , when user terminal  702  sends a request to connect to smallcell  704 , smallcell  704  accepts the connection based on availability of its hardware and software resources, and at the same time, smallcell makes a resource request  710  to core network to carry user terminal&#39;s traffic. If smallcell&#39;s resource request is accepted  712 ,  714 , user terminal will sign a smart contact  716  with the smallcell by using user terminal&#39;s International Mobile Subscriber Identification (IMSI) and user terminal&#39;s phone number. Smart contract is recorded as a block in a smallcell blockchain. IMSI is used as private key in recording smart contract in smallcell blockchain. User terminal&#39;s mobile phone number is used as public key in recording smart contract in smallcell blockchain. Smart contract between user terminal and smallcell will stay open as long as user terminal transmits and receives data. When user terminal finishes the data traffic, smart contract will be closed and payment will be made to the smallcell in terms of Smallcell Coin (SCC) using the procedures depicted in  FIG. 6 . 
       FIG. 11  shows diagram that any payment  808 , transaction  812 , user and smallcell information  812 , user and smallcell data  812 ,  808  between user terminal  802  and smallcell  804 ; and between smallcell  804  and user terminal is recorded  810 ,  814  in smallcell blockchain  806 . 
       FIG. 12  shows diagram that any payment  908 ,  912 , transaction  908 ,  912 , smallcell  902  information  908 ,  912 , smallcell data between smallcells  902 ,  904  in the network is recorded  910 ,  914  in the smallcell blockchain  906 . 
       FIG. 13  shows process flow to update the software of the smallcells in the network. When new software release  1002  is available in software development center, the feature list  1004  of this new software release is shared with smallcells in the network. Each smallcell in the network votes  1006  for each feature of this new software release. Each vote  1008  from each smallcell is recorded in smallcell blockchain. Smallcells voting positive for a particular feature  1010  pay 1 smallcell coin for each positive vote. If the total amount of smallcell coins is larger or equal price of the new software release  1012 , each smallcell in the network saves old performance routers and key performance indicators  1016  which are recorded in smallcell blockchain. Each smallcell installs the new software  1018 . Each smallcell creates new counters and key performance indicators based on the new installed software release and records all of the information in smallcell blockchain  1020 . If the performance of the smallcell has improved, this new software release is kept in that smallcell  1022 . If the performance of the smallcell has degraded after installing the new software release, smallcells reinstall the previous version of the software which was installed in the smallcell before the new software release  1024 . 
       FIG. 14  shows software center  2002  and the part of a smallcell network  2000 . Smallcells  2006 ,  2010 ,  2014 ,  2020 ,  2028 ,  2032  are connected to each other with a backhaul connection  2004 ,  2008 ,  2012 ,  2016 ,  2018 ,  2022 ,  2024 ,  2026 ,  2030 . When a new release and/or updated release of software is available in the software center, this information pushed to a smallcell and/or a few smallcells in the network. When a new release and/or updated release of software is available in the software center, this information is pulled by a smallcell or a few of smallcells in the network. That is, the availability of new software release can be pulled from software center by smallcells and also can be pushed by software center to smallcells. When one smallcell knows that a new software release is available in the software center, this information is shared with other smallcells in the network through backhaul connection  2004 ,  2008 ,  2012 ,  2016 ,  2018 ,  2022 ,  2024 ,  2026 ,  2030  between smallcells. This backhaul connection can be wired, wireless, or any other type of communication medium.  2040  shows software feature score table which has ratings, votes for each software feature by each smallcell in the network. Each smallcell in the network has this table. 
       FIG. 15, 3000  shows charging ledger in smallcell blockchain.  3002  shows the time of recording the ledger in smallcell blockchain,  3004  shows phone number of subscriber (user terminal) which has been connected to a smallcell,  3006  shows IMSI number of subscriber (user terminal) which has been connected to a smallcell.  3008  shows unique identification number of smallcell.  3010  shows geographical location of smallcell in terms of latitude and longitude.  3012  shows if the service subscriber has received is normal service or emergency service or both.  3014  shows amount of consumed data, and amount of consumed voice minutes.  3016  is reserved for terminal type and quality of service (QoS) class. 
       FIG. 16, 4000  shows performance ledger used in smallcell blockchain.  4002  shows the time recording for the ledger.  4004  shows telephone number for subscriber (user terminal).  4006  shows IMSI of subscriber (user terminal).  4008  shows smallcell identification number which can be serial number of a smallcell and/or any other unique number that identifies smallcell.  4010  shows geographical location of smallcell in terms of latitude and longitude.  4012  shows quality index. Each subscriber (user terminal) connected to smallcell will send performance metrics at the end of the call. This is used to report performance to smallcell. Quality Index consists of counter and key performance indicators such as Amount of throughput per RRC Connected Instance (in kbps)/Average Channel Quality Indicator. Standard Deviation of throughput Per RRC Connected Instance (in kbps), Access Success Rate, Handover Success Rate.  4014  shows amount of consumed data and total number of voice minutes by subscriber user terminal),  4016  shows terminal type and quality of service (QoS) class. 
     The value of smallcell coin will be different based on at least one of the network operators owning and running the smallcell network, and based on the different vendors/manufacturers of smallcell. The value of smallcell coin will depend on Coverage, Capacity, Service Experience, Service Quality.