HK1215341B - Methods and systems for dynamic spectrum arbitrage - Google Patents

Description

Method and system for dynamic spectrum arbitration

Cross reference to related patent applications

This application claims the benefit of priority from U.S. patent application No. 13/830,839 filed on 3/14/2013, which is incorporated herein by reference in its entirety for all purposes.

Background

With the ever-increasing use of wireless communication devices for accessing networks and downloading large files (e.g., video files), there is an increasing demand for radio spectrum. Smart phone users complain of dropped calls, slow access to the internet, and similar problems, largely due to the excessive number of devices attempting to access the limited RF bandwidth allocated to such devices. However, due to the discontinuity of such voice radio communication bands and the use of episodics, certain portions of the RF spectrum, such as the RF bands dedicated to emergency services (e.g., police, fire and rescue, etc.), are largely idle.

SUMMARY

According to a first embodiment, a method for dynamically managing Radio Frequency (RF) spectrum resources in frequency, space, and time includes monitoring usage of RF spectrum resources at a first network and determining an amount of RF spectrum resources unused in the first network. The method includes allocating a portion of an amount of unused RF spectrum resources of the first network for use by secondary users and receiving a request for additional RF spectrum resources from a second network. The method includes providing the second network with access to unused RF spectrum resources of the first network. The method may include offloading secondary users from the first network.

According to another embodiment, a communication system including a server configured with server-executable instructions to perform operations includes dynamic spectrum arbitration (arbitrage) and management. Management enables the radio frequency spectrum to be made available to RF devices in frequency, space, and time as described herein. In another embodiment, a server configured with server-executable instructions to perform operations includes dynamic spectrum arbitration and management. Management enables the radio frequency spectrum to be made available to RF devices in frequency, space, and time.

In another embodiment, the radio frequency spectrum clearinghouse includes a server for monitoring usage of the RF spectrum resources. The determined amount of unused RF spectrum resources in the first communication system is cleared and a portion of the amount of unused RF spectrum resources is allocated for use by the secondary user. The server forms an allocated share of unused RF spectrum resources of the first communication system. The second communication system will utilize the allocated share. The server may communicate the availability of the allocated share to the second communication system.

Brief description of the drawings

The accompanying drawings, which are incorporated herein and constitute part of this specification, illustrate exemplary embodiments of the invention and, together with the general description given above and the detailed description given below, serve to explain the features of the invention.

Fig. 1 is a system block diagram showing call volume requests made to a cellular communication network under normal conditions.

Fig. 2 is a system block diagram showing call volume requests made to a cellular communication network in an emergency condition.

Fig. 3 is a system block diagram showing call volume requests made to a cellular communication network in an emergency condition when a first responder arrives on site.

Fig. 4 is a system block diagram showing call volume requests made to a cellular communication network as additional emergency response personnel arrive at the scene.

Figure 5 is a system block diagram showing call volume requests made to the cellular communication network after an emergency situation has been alleviated.

Fig. 6 is a process flow diagram of an embodiment method for managing a hierarchical priority access (TPA) operation on a network.

Fig. 7 is a process flow diagram of another embodiment method for managing TPA operations on a network.

Fig. 8 is an example hierarchical table of levels of users considering priority access to emergency communication resources.

Fig. 9 is a communication system block diagram of a Dynamic Spectrum Arbitrage (DSA) communication system according to one embodiment.

Fig. 10 is a communication system block diagram of a DSA communication system according to one embodiment.

Fig. 11 is a communication system block diagram of a DSA communication system according to one embodiment.

Figure 12 is a communication system block diagram showing a DSA communication system for one embodiment for providing master control for an arbitration process.

Fig. 13A is a diagram showing its allocated RF spectrum according to one embodiment.

Fig. 13B is a diagram showing one manner in which RF spectrum may be allocated for use, according to one embodiment.

Fig. 14 is a block diagram showing the manner in which the RF spectrum may be allocated for use with guard bands, according to one embodiment.

Fig. 15 is a diagram showing the manner in which the RF spectrum may be aggregated for use allocation, according to one embodiment.

Fig. 16A to 16C are block diagrams showing a manner of allocating spectrum for a Mobile Virtual Network Operator (MVNO).

Figure 17 is a communication system block diagram showing a DSA communication system for communication between components of a system for allocating resources, according to one embodiment.

Figure 18 is a communication system block diagram showing communication between components of two networks in a DSA communication system during resource reservation, according to one embodiment.

Fig. 19 is a communication system block diagram of a DSA communication system showing resource forking at a base station (eNodeB) according to one embodiment.

Fig. 20 is a communication system block diagram of a DSA communication system exhibiting Serving Gateway (SGW) and Packet Gateway (PGW) link bandwidth allocation and capacity control, according to one embodiment.

Fig. 21 is a communication system block diagram showing a DSA communication system combining x-forking of resources at an eNodeB and SGW and PGW link bandwidth allocation with capacity control, according to one embodiment.

Fig. 22 is a communication system block diagram of a DSA communication system showing spectrum allocation based on licensed region and local region methods according to one embodiment.

Fig. 23A is a diagram showing typical RF spectrum allocation in a licensed region, according to one embodiment.

Fig. 23B is a diagram showing RF spectrum allocation in a DSA communication system based on a licensed region, according to one embodiment.

Fig. 24 is a diagram showing spectrum allocation in a DSA communication system based on a local area according to one embodiment.

Fig. 25A is a communication system block diagram of a DSA communication system showing a case where a subscriber uses a first operator (operator a), according to one embodiment.

Fig. 25B is a communication system block diagram of a DSA communication system showing a case where a subscriber uses a second operator (operator B) in an actual type roaming setting for spectrum splitting according to one embodiment.

Fig. 26A is a communication system block diagram of a DSA communication system showing a case where a subscriber uses a first operator (operator a) for public safety and commercial DSA schemes according to one embodiment.

Figure 26B is a communication system block diagram showing a DSA communication system based on the service used, the geographic location, and the situation when a subscriber can use operator B in an actual short-term lease based on the DSA.

Figure 27A is a communication system block diagram of a DSA communication system showing a normal operating condition according to one embodiment.

Figure 27B is a communication system block diagram of a DSA communication system showing additional capacity and spectrum available to subscribers, according to one embodiment.

Fig. 28 is a process flow diagram showing an embodiment method for network selection and reselection in a DSA communication system.

Figure 29 is a communication block diagram of a DSA communication system showing a TAI routing area where a home non-DSA user equipment uses one TAI element (TAI) and a DSA user equipment uses another TAI.

Fig. 30 is a communication block diagram of a DSA communication system demonstrating advanced tracking and monitoring of RF spectrum resource allocation and usage, according to one embodiment.

Figure 31 is a communication block diagram showing the integrated DSA communication system required for full mobility between the visited and home networks.

Figure 32 is a communication block diagram of a DSA communication system showing a media independent handover of a user equipment from one network to another according to one embodiment.

Figure 33 is a communication block diagram showing a DSA communication system for initiating data flow for network handover, according to one embodiment.

Fig. 34 is a communication system block diagram showing a DSA communication system providing user equipment with access to several Radio Access Terminals (RATs), according to one embodiment.

Figure 35 is a message flow diagram that illustrates message communication between components of a DSA communication system, according to one embodiment.

Fig. 36-40 are process flow diagrams of an embodiment method for allocating and accessing resources using a DSA communication system.

Figure 41 is a message flow diagram that illustrates in more detail the communication of messages between components of a DSA communication system, according to one embodiment.

Fig. 42-44 are process flow diagrams of embodiment methods for offloading a communication session from a host network.

Figures 45-49 are process flow diagrams of an embodiment method for allocating and accessing resources in a public safety network using a DSA communication system.

Fig. 50-53 are process flow diagrams of an embodiment method for offloading a communication session from a public safety network.

Figures 54-56 are process flow diagrams of an embodiment method for enabling an authorized public safety authority to access a public safety network from another network using a wireless device.

Fig. 57 is a system block diagram illustrating network components in an example communication system suitable for use with the various embodiments.

Figure 58 is a system block diagram illustrating information flow and functional components in an embodiment DSA system including a DPC component configured for coordinating operation of two or more DSC components.

Figure 59 is a system block diagram illustrating functional components in an embodiment DSA system configured for partitioning a geographic region into a grid-like data structure.

Fig. 60 is an illustration of the locations of cell towers or cell sites in a lessee network and a lessor network.

Figure 61 is a process flow diagram showing an embodiment DSA method for allocating resources in a DSA system.

Fig. 62-64 are diagrams of network components and tenant User Equipment (UE) eligible for handoff to in a lessor network, in accordance with various embodiments.

Fig. 65A and 65B are illustrations of the order in which a UE that is utilizing a lessor network sends resources back to the lessee network, according to one embodiment.

Fig. 66A-66C are illustrations of the sequence in which a UE moves out of a geographic bidding area and switches to a tenant network.

Fig. 67 is a process flow diagram showing an embodiment DSA method for handing over a UE connected to a lessor network back to a lessee network in response to detecting network congestion.

Fig. 68 is a process flow diagram showing an embodiment DSA method for handing over resources back to a tenant network when a lease for the use of the allocated resources has been exhausted.

Fig. 69 is a process flow diagram showing an embodiment DSA method for switching resources back to a lessor network when a lessee UE using lessor network resources is no longer located within a geographic area defined in the bidding process.

Fig. 70 is a process flow diagram showing an embodiment DSA method for a tenant UE camping on a cell site and listening for instructions when the UE is located within a geographic region defined in a bidding process but has not requested to start a session.

Fig. 71A is a process flow diagram showing an embodiment DSA method for a tenant UE requesting to start a session with a lessor network when the UE is located in a geographic region defined in a bidding process but has not been instructed to camp on the lessor network.

Fig. 71B is a process flow diagram showing an embodiment DSA method for handing off a session when it is determined that a tenant UE has moved into a geographic region defined in a bidding process so that the tenant UE may continue an active session with a lessor network.

FIG. 72 is a component block diagram of an example mobile device suitable for use with the various aspects.

FIG. 73 is a component block diagram of a server suitable for use with one embodiment.

Detailed Description

Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References to specific examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims.

As used herein, the terms "mobile device," "wireless device," and "User Equipment (UE)" are used interchangeably and refer to various cellular telephones, Personal Data Assistants (PDAs), palm top computers, notebook computers with wireless modems, wireless email receivers (e.g., blueberries)Anddevice), multimedia internet enabled cellular telephone (e.g.) And similar personal electronic devices. The wireless device may include a programmable processor and memory. In a preferred embodiment, the wireless device is a cellular handset (e.g., mobile device) that can communicate via a cellular telephone communications network.

As used in this application, the terms "component," "module," "engine," "manager" are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, or software in execution, which is configured to perform a particular operation or function. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, a computer, a server, network hardware, and the like. By way of illustration, both an application running on a computing device and the computing device can be referred to as a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one processor or core and/or distributed between two or more processors or cores. In addition, these components can execute from various non-transitory computer readable media having various instructions and/or data structures stored thereon.

A number of different cellular and mobile communication services and standards are available or contemplated in the future, all of which may be implemented and benefit from various embodiments. Such services and standards include, for example, third generation partnership project (3GPP), Long Term Evolution (LTE) systems, third generation wireless mobile communication technologies (3G), fourth generation wireless mobile communication technologies (4G), Global System for Mobile communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) systems (e.g., cdmaOne, CDMA2000TM), enhanced data rates for GSM evolution (EDGE), Advanced Mobile Phone System (AMPS), digital AMPS (IS-136/TDMA), evolution data optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Networks (WLAN), Public Switched Telephone Networks (PSTN), and the like(PSTN), Wi-Fi protected Access I&II(WPA、WPA2)、Integrated digital enhanced network (iden), and Land Mobile Radio (LMR). Each of these techniques involves, for example, the transmission and reception of voice messages, data messages, signaling messages, and/or content messages. It should be understood that any reference to terminology and/or technical details relating to a separate telecommunications standard or technology is for illustrative purposes only and is not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language.

A high priority in response to any emergency or disaster situation is to establish effective communication. In a large-scale emergency or disaster (both man-made and natural) situation, it is important to maintain communication between all first responders and emergency personnel in order to effectively respond to, manage and control the emergency. In the absence of effective communication between the first responder and other emergency personnel, the resource may not be effectively moved to the area where it is most needed. Even in light emergency situations (e.g., traffic accidents and fires), the first responder must be able to call on support assets and coordinate with other services (e.g., public facilities, hospitals, etc.). Ownership and use of ubiquitous wireless devices, emergency communication via wireless devices using commercial cellular mobile communications networks is often the most efficient and effective means of mobilizing emergency response personnel and resources. Enabling wireless devices to provide effective emergency communication avoids the technical challenges and costs of coordinating radio frequencies among various first responder agencies (e.g., police, fire, ambulance, FEMA, public facilities, etc.). Further, a first responder (e.g., a doctor, nurse, retired police, or military personnel) that is not on duty or is not typically equipped with a radio will have a wireless device or can be promptly lent to a wireless device.

However, emergency communication over cellular communication networks is not without problems. As discussed above in the background, cellular communication networks ("networks") are designed to accommodate access requests from only a fraction of the total number of wireless devices in a particular cell. In an emergency or crisis, network resources can become overburdened when predictable human responses to the situation prompt a large number of wireless device users within a particular cell to access the network simultaneously. A wireless device user may be attempting to alert emergency personnel of an emergency situation (such as a 911 emergency call) or alert friends or family members that the user is safe while in the area of the emergency situation. Some users may be transmitting images of emergency situations (fire, accident, etc.) to news services or friends. In a large scale situation, emergency responders using wireless devices for emergency communication will increase the volume of calls. In any event, the predictable increase in call volume during an emergency situation can overwhelm commercial cellular communication networks, particularly in the cell areas surrounding the emergency situation, thus making the networks unreliable for emergency response personnel communication use.

To explain this problem, consider the case of a traffic accident occurring on a highway. Fig. 1 shows a cellular communication network in normal conditions. As shown, a plurality of wireless devices 101(a-g) are wirelessly connected to a cellular communication network via a base station 102 serving a particular cell 100. The base stations 102 are connected to a Mobile Switching Center (MSC)104 via a Base Station Controller (BSC)/Radio Network Controller (RNC) 103. The MSC104 contains a Public Switched Telephone Network (PSTN) interface and an internet interface. Calls made to or from any of the plurality of wireless devices 101(a-g) may be routed over the conventional landline PSTN105 or over the internet 106 using VOIP. Calls between a conventional fixed telephone station and any of the wireless devices 101(a-g) may be routed via the PSTN or the internet. Calls between wireless devices 101(a-g) may be routed over the PSTN or internet to a similar MSC104, BSC/RNC103, and base station 102 located proximate to the originating or intended wireless device 101 (a-g).

Fig. 1 shows a typical situation in which some of the wireless devices within a cell access the network simultaneously. For example, fig. 1 shows seven separate wireless devices 101(a-g) located within a cell, of which only three (101c, 101d, and 101e) are currently accessing the network. Thus, the network is operating well within its operating parameters and all requests from wireless devices 101(a-g) for the network are granted. Note that all wireless devices 101(a-g) that are turned on but not in use continue to communicate with base station 102 via a link management channel (not shown). The network uses these communications to keep track of the wireless devices 101(a-g) within each cell to support call routing. However, the amount of information communicated between all wireless devices 101(a-g) and the base station 102 for such tracking purposes is small (especially compared to the bandwidth required to make a normal telephone call), so the number of on-but-inactive wireless devices 101 that are turned on within a cell will generally not overwhelm the network.

This conventional functionality of cellular networks can be disrupted when, for example, an accident stops traffic causing delayed drivers to simultaneously use their wireless devices to alert emergency personnel of the traffic accident (emergency 911 calls) or to contact friends, family members, business associates, etc. to notify them of their late arrival. Fig. 2 shows a cellular communication network in such an emergency. In this illustration, a truck 107 in the vicinity of the base station 102 catches fire. Predictably, a truck 107 fire prompts most wireless device 101(a-g) users in the vicinity to access the cellular network at approximately the same time. This results in an overload situation in the cell due to exceeding the operator's bandwidth on the local base station 102. As a result, some wireless devices 101b, 101f will not be granted access to the network, and new network access requests may be denied until the communication channel is opened. This communication bottleneck can worsen emergency situations by delaying the response by emergency personnel and denying the first responder's effective network communication.

This problem is exacerbated in disaster situations involving many victims and large areas, such as wildfires, floods, hurricanes, tornadoes, and terrorist attacks. As witnessed during the 9-month 11-day attacks and the Katrina (Katrina) hurricane, the catastrophic disaster can destroy portions of the cellular and fixed telephone network infrastructure, making the remaining network more susceptible to overload conditions. Network overload during a catastrophic event is particularly troublesome as such situations naturally involve extensive confusion and require close coordination among a large number of emergency and relief personnel.

If a disaster situation will persist long enough (e.g., a flood or hurricane situation), additional cellular communication capacity may be added to an area by activating the deployable cellular communication system to provide emergency response teams and personnel with the ability to communicate. Such recently developed deployable units (also referred to herein as "switch on wheels") may include CDMA2000 base stations and switches for remote connection to the internet and PSTN, Land Mobile Radio (LMR) interoperability equipment, satellite Fixed Service Satellites (FSS), and optionally a generator driven by source or remote power such as gasoline or diesel. A more thorough description of an example deployable on-wheel exchanger is provided in U.S. patent application No. 12/249,143 filed 10/2008, the entire contents of which are hereby incorporated by reference in their entirety.

These on-the-turn switches are active mobile cellular base stations that can be deployed in disaster areas and operated as cellular antenna towers. The on-turn switch sends and receives communication signals from multiple wireless devices 101 and acts as a gateway portal to the remaining conventional communication infrastructure. Communications between the switch and the wireless device 101 on the turn are broken into packets for transmission as VOIP communications and may be transmitted via satellite to ground stations outside the disaster area where calls are forwarded to the recipient over the telephone network. Even with the increased bandwidth provided by deployable on-turn switches, network overload can still result in communication delays and frustration for emergency response personnel.

To overcome such problems in the event of a national emergency, WPA systems are deployed. Conventional WPA systems provide the selected emergency leader with preemptive access to the cellular communication network. However, conventional WPA systems do not allow calls to be made to registered WPA authorities' wireless devices. In other words, while wireless devices registered for WPA services may be given priority access to place calls on the network, there is no provision in the WPA system to enable those very same wireless devices to receive calls. Incoming calls to wireless devices in a command center may be as important as outgoing calls. Furthermore, conventional WPA systems assume that if an authorized user needs to make a call, the call will be made from their pre-registered wireless device. However, it may be the case that authorized personnel do not have their pre-registered wireless devices. Alternatively, the wireless device may be destroyed. Authorized personnel must be enabled access to the overloaded network. Moreover, emergency personnel who have not previously registered their wireless devices on the WPA system may not have "on the fly" access to an overloaded cellular communication network. Many times, primary volunteer emergency responders who are not on duty may be the first responders to an incident scene. Such personnel may not have the right to use conventional WPA designed to address the leadership needs. Thus, rather, personnel considering that they may quickly mitigate situations in the vicinity of the site may not be pre-registered and authorized for conventional WPA.

To overcome these limitations of conventional cellular communication networks and conventional WPAs, various embodiments provide a hierarchical priority access (TPA) capability to first responders to deliver quality of service (QoS)/grade of service (GOS) wireless device communications for both calls initiated and terminated at a mobile handset. Various embodiments are particularly directed to the needs of the first responder at the very beginning of an emergency event.

As its name implies, TPA is intended to provide a hierarchical response to network capacity requirements. As more responders are emerging to help solve the problem at hand, the layered response reflects typical communication requirements at the scene of the event. When an event occurs, the first responder either is on the scene of the event or begins to respond. The number of first responders to first arrive at a live reporting event is small and can grow in direct response to the magnitude and severity of the event.

To accommodate this predictable response, the TPA can implement call volume based escalation and downgrade procedures as the first responder arrives on-site and leaves as the situation is restored to normal.

In general, the various embodiments work as follows. During normal operation, the amount of cellular calls through a particular base station is monitored and a determination is made as to whether the network is approaching a capacity limit. The call volume may be monitored based on the current call, the attempt to access the network, the bandwidth in use, or other methods known to the cellular service provider. The call volume may be monitored at the base station 102, locally at the BSC/RNC103 or MSC104, or centrally in one embodiment, such as in a Network Operations Center (NOC). Such monitoring is at the cellular level, since normal emergency situations are most likely to affect one or two cell areas, although TPA will work in a similar fashion in a wide emergency. When the amount of calls in a cell exceeds a threshold preselected by the service provider and/or emergency response planner, the system assigns a channel in the affected cell tower to the TPA operation.

Fig. 2 shows a situation where the call volume has exceeded a threshold indicating that TPA should be implemented. As shown in fig. 2, more wireless devices 101 in a cell supported by a base station 102 are attempting to access the network than the network can connect to. As a result, only some of the wireless devices 101a, 101c, 101d, 101e, and 101g will be able to place or receive calls (as shown in black), while other wireless devices will be denied access to the network (as shown in white). In this case, the call volume in the cell served by the base station 102 has exceeded the threshold, so one of the communication channels on the antenna is assigned to the TPA operation. However, the channel remains available for general public use until a call to an authorized TPA is placed. Thus, no changes in the communication network are shown in fig. 2.

Various embodiments address this overload situation in order to allow emergency personnel to use the cellular communication network when they arrive at the scene, as shown in fig. 3. When the emergency responder 108 arrives at the scene, the individual may initiate a wireless telephone call. If the communication channel has been assigned to a TPA operation and the wireless device of the emergency responder is a wireless device pre-registered as an authorized TPA, the network may identify the pre-registered wireless device of the authorized TPA from the unique ID of the wireless device and identify the call as a TPA call. The base station 102, BSC/RNC103, or MSC104 may ensure that the TPA call is connected. If necessary, bandwidth allocated to the consumer wireless device user is reduced and one or more non-emergency calls may be dropped to enable the TPA call to be connected. This is shown in fig. 3 as having hung up the connection to wireless device 101c and denied further access to the network (shown as white lightning) and connected the TPA call made by emergency responder 108 (shown as virtual black lightning).

As shown in fig. 4, as additional emergency personnel 109 arrive at the emergency scene, additional TPA calls may need to be connected. To accommodate the increase in TPA calls, additional network resources may be automatically allocated to TPA operations to provide reliable cellular communications to emergency responders. This is illustrated in fig. 4, which shows a TPA call (shown as a ghost black lightning) connected to police 108 and fire 109 personnel, while wireless devices 101b, 101c, and 101f have been disconnected (shown as white lightning). Automatically allocating more resources to TPA use reduces the bandwidth available to the general public, which will limit general access to the network. However, as long as a large call volume persists, emergency personnel are provided with reliable access to the network.

Eventually the emergency will be resolved and emergency personnel will start to the scene. When the situation returns to normal, the amount of civil calls should return to normal level and the number of emergency responders requiring TPA access will also decrease. This is illustrated in fig. 5, which shows that the fire has been extinguished and the fire fighter has left the site. As traffic begins to return to normal flow, smaller, general population wireless devices 101a-101g simultaneously access the network. As cellular communications return to normal, cellular communications resources may be released from TPA operation, restoring the network to normal operation. As shown, the remaining emergency personnel 108 are connected to the cellular communication network in a normal fashion because the call volume has decreased to the point where the TPA operation has been terminated.

When TPA operation is implemented on one or more communication channels, the cellular system (e.g., in a local base station, BSC/RNC, or MSC, or in a central location such as a NOC) monitors incoming and outgoing calls to determine whether any calls are directed to or from emergency response personnel. This may be accomplished by identifying the originating or destination wireless device as a pre-registered TPA wireless device. Alternatively, the system may identify emergency response personnel when they complete a special dialing process, such as the 272 dialing process described below.

The wireless device may be pre-registered for use by the TPA through an authorized user. This may be accomplished by registering as a qualified emergency responder (e.g., according to standards established by governmental authorities) with the cellular network provider. As is well known in the field of telecommunications, all wireless devices 101 accessing cellular communications are assigned a unique identification number. During the pre-registration process, the cellular network provider stores the unique identification number of the wireless device in a database of authorized TPA personnel. As described more fully below, the cellular network provider may also issue a unique Personal Identification Number (PIN) for the individual for use in enabling TPA preemption from a non-TPA wireless device.

If the emergency responder's wireless device is not pre-registered (e.g., a borrowed phone) and the network is overloaded, the emergency responder may not be able to access network resources. In this case, the emergency responder may activate the embodiment TPA from the unregistered wireless device 101 by first dialing 272 and then dialing a Personal Identification Number (PIN) and a telephone number. The base station 102 closest to the unregistered wireless device 101 receives a transmission from the wireless device 101 indicating that the wireless device is initiating a call. The base station 102 (or the BSC/RNC103 connected to the receiving base station) recognizes 272 the special dialling prefix and starts routing the call to the appropriate destination. Alternatively, identification and routing of the #272 dialing prefix may be accomplished at MSC 104. This destination may be the PSAP or central location of the nearest database with the PIN. As the call progresses through the communication network system, the 272 call is similarly processed at the BSC/RNC103 and later at the MSC 104. The BSC/RNC103 or MSC104 controlling the base station antenna 102 and other associated antennas is programmed to identify the special dialing process using a pre-registered first responder PIN database. This PIN database may be stored at the MSC104 or at another central location such as the NOC. If the received PIN matches a record in the PIN database, MSC104 may immediately give the caller a preemptive access to the network as if the call was made from a wireless device registered with a TPA as described above. To support this capability, the channel assigned with the TPA reserves sufficient open capacity to receive and identify 272 the dial-up call during TPA operation. If the communication channel is at maximum capacity and the dialed number does not begin with x 272, the call is dropped quickly without attempting to complete the call. However, if the dialed number begins with x 272, the MSC104 completes the process of comparing the entered PIN with the PIN database and temporarily registers the call as a wireless device authorized for TPA. If necessary, non-TPA calls may be dropped to reserve sufficient capacity for receiving and identifying 272 calls.

Although reference is made throughout this application to MSC104 monitoring and providing this TPA capability, those of ordinary skill in the art will recognize that other elements of the communication system may implement various method steps. These elements may include, but are not limited to, equipment collocated with the base station antenna 102, BSC/RNC103, or NOC.

Once the wireless device is identified as a TPA phone by means of the 272 dialing procedure, MSC104 will keep track of the wireless device and continue to treat it as a TPA-registered wireless device as long as at least one communication channel is assigned to the TPA operation. Using the unique identification number assigned to the wireless device, MSC104 identifies the subsequent call from the wireless device as a TPA call without the user having to repeat the 272 dialing process. Similarly, MSC104 may identify an incoming call to the first responder that should receive the TPA preemption service. Thus, when implementing TPA for both incoming and outgoing calls by calling a number (such as dispatcher or "911") using the x 272 dialing process, a first responder 108 using a non-registered wireless device can register the wireless device "on the fly".

In one embodiment, the TPA-authorized user with a PIN may authenticate any number of wireless devices using the dialplan process of x 272 as described above. This embodiment would enable first responders such as police, firefighters or emergency medical technicians to "designate" as a proxy "the volunteer of military personnel, doctors or retired police as they find on site, thus creating a reliable temporary emergency communication network. Since the temporary TPA authorization of the wireless device established through the dialing process of x 272 is revoked (i.e., TPA operation is aborted) when all communication channels in the affected area return to normal operation, a limited consideration is that the TPA system can be compromised for subsequent emergency situations if the PIN of the authorized user is not revealed. Even if a PIN is disclosed, the PIN can be easily changed without significant impact since TPA implementations are expected to be a rare, random, sporadic event.

In yet another embodiment, a user of a TPA-registered wireless device without (or forgetting) a PIN may register another phone "on the fly," thereby "designating it as a proxy" for the duration of the TPA event by simply initiating a special dialing procedure on any wireless device. For example, the first responder may use a wireless device registered with the TPA to dial the number of the wireless device to be "designated as proxy" followed by a dial 272 (any dial prefix or suffix may be used). When MSC104 receives this call, it identifies the 272 prefix or suffix as a wireless device indicating that the dialed number is considered a temporary authorized TPA, allowing it to store the unique ID of the called wireless mobile device in a database for tracking such temporary authorized TPA. Using this capability, first responders can quickly designate one or more volunteers as agents by calling their numbers.

In yet another embodiment, emergency response personnel who have risen in status to a level that qualifies for pre-registered TPA services or PINs may still be the first emergency personnel in the emergency scene. The user may initiate 272 the special dialing process using his/her non-pre-registered wireless device. The call may be forwarded to a PSAP that may issue a temporary PIN and add the wireless device to a temporary TPA database.

Alternatively, if the user initiates 272 special dialing (or a similar dialing process as 911), the call may be forwarded to the PSAP. In large crisis situations, the answering PSAP may be disabled or unable to answer quickly due to the large volume of incoming calls. In such a case, the temporary TPA authorization may be automatically issued if the PSAP does not answer the 272 call within a predetermined time frame. Since the PSAP operator does not fully analyze the delivery environment surrounding the temporary TPA authorization, it is unclear whether the user receiving the temporary TPA authorization is properly authorized. Thus, the temporary TPA authorization may be flagged on the PSAP monitor for possible deactivation or investigation.

In yet another embodiment, when dialing into a residential (i.e., non-TPA-authorized) wireless device within a cell area that implements TPA operation, the cellular network is configured to prioritize calls from both TPA-registered wireless devices and (optionally) temporarily-authorized TPA wireless devices. When making such a call, the MSC104 is programmed to route the call through the wireless device assigned to the TPA-operated communication channel to dial. If the channel assigned with the TPA is at the highest capacity, when a call from a wireless device that is authorized for the TPA is received for the civilian wireless device, another civilian wireless device call is dropped to provide sufficient capacity to complete the call, using an associated preemption procedure to prevent another 911 call from being dropped. The present embodiment gives emergency personnel the ability to enter emergency dialing. For example, emergency personnel may use this capability to call back the public who originally called 911 to report an emergency in order to request updates from potential witnesses. As another example, a first responder may call a volunteer within the emergency scene to designate their phone as a proxy, ensuring that the volunteer is reachable even if the communication network is otherwise overwhelmed.

TPA operation can be achieved in at least two embodiments of the present disclosure. In a first embodiment, described below with reference to fig. 6, one or more cellular communication channels are dedicated to TPA calls, providing emergency personnel with dedicated communication capacity, while leaving the remaining channels to the general public. In a second embodiment, described below with reference to fig. 7, call preemption is only implemented for TPA calls when a traffic channel assigned TPA arrives at capacity. These embodiments are separately described below.

Fig. 6 illustrates an example process flow that may be used to implement the steps of the first embodiment of a TPA operable with a computing device having a processor. During normal operation, the cellular communication network call volume is monitored (block 201). In particular, the cellular communication network call volume (or the number of access requests or bandwidth in use) is compared to a predetermined threshold (e.g., 85% of maximum capacity) (block 202). If the call volume is below a predetermined threshold, assuming normal conditions exist, the monitoring process returns to block 201 to continue monitoring the call volume. However, if the volume of calls (or the number of access requests or bandwidth in use) exceeds a predetermined threshold, an abnormal condition exists, which may indicate that an emergency is developing. To prepare for an emergency, network resources (e.g., communication channels on a particular base station antenna) are partitioned and reserved for TPA use (block 203). By automatically assigning a communication channel to TPA use, the system allows TPA-authorized wireless devices to gain access to the network even when the network is otherwise overloaded. However, TPA preemption does not occur until a TPA-qualified caller attempts to access an overloaded network.

The communication channel assigned to the TPA continues to function normally as the increased call volume may or may not respond to an emergency, handling civil (i.e., non-TPA) calls in a normal fashion. In the case where the increased call volume is due solely to coincidental network requests and TPA-disqualified users are attempting to place calls, call preemption by TPA is not required. Thus, the TPA threshold can be exceeded and TPA is achieved even when there is no actual emergency. Delaying the actual implementation of TPA preemption until the first responder requests the service increases the reliability of the network under normal circumstances.

The system may be notified that an actual emergency is occurring, as indicated by emergency response personnel of an authorized TPA placing TPA calls within the affected cell area. When the communication channel is in TPA mode, the cellular system (whether at a base station, BSC/RNC/MSC, or at a central location such as NOC) monitors incoming and outgoing calls to determine if any emergency response personnel are using a pre-registered TPA wireless device or have completed a special dialing process that invokes TPA preemption (block 204). If no emergency response personnel have initiated a call using the wireless device or special dialing procedure of the authorized TPA, the system may continue to monitor the access request (in block 204) and the call volume (in block 201) to determine if the communication channel should be released from the TPA operation (block 202).

The TPA is initiated if a call is initiated by a wireless device that is authorized for the TPA, or if the call is generated from a non-pre-registered wireless device using a 272 dialing procedure (block 205). When initiating TPA, only previously registered or "on the fly" granted emergency personnel will be allowed access to the partitioned and reserved network resources, block 205. As noted above, TPA will typically be implemented first on a single communication channel, leaving the remaining channels available to the general public. Then, if the TPA usage exceeds the capacity of the network resource allocated with the TPA, another resource may be converted to TPA operation. By dedicating network resources of one channel or one resource at a time to emergency personnel use, the remaining network resources are reserved for unnecessary general public use. Further, by dedicating network resources to emergency personnel communications, emergency personnel can send and receive calls on their wireless devices.

In an alternative embodiment, when TPA is initiated (block 205), MSC104 may examine wireless devices 101 located in the affected cells or served by other base station antennas 102 within the same BSC/RNC103 to identify all registered or temporarily registered first responders. These first responders may be advised via SMS messages (or other methods) that they may utilize the TPA service by placing a call or using a special dialing process (block 206).

In another alternative embodiment, the base station 102, BSC/RNC103, or MSC104 may also send a message to all non-emergency wireless devices 101a-101g within the affected cell 100 suggesting that they avoid using their wireless devices 101a-101g, except for emergency 911 calls and indicating that emergency services have been notified (block 207). This messaging may be initiated by the PSAP responsible for the event zone, by a local event command and control authority, or by a network service provider. Such messages may be communicated via SMS messages or other communication means. The system may also notify callers connected to a channel assigned for TPA use that their call is being terminated before disconnecting the call.

As emergency situations continue to evolve and additional emergency response personnel are present on site, additional network resources may be required to support emergency personnel communications. Thus, the partitioned and dedicated network resources may be monitored to determine whether additional network resources should be partitioned and allocated to the TPA. This may be accomplished by comparing the amount of calls on the partitioned and dedicated network resources to a predefined maximum or minimum threshold (block 208). If the call volume exceeds a predefined maximum value (indicating an aggravating situation), e.g., 25% usage of the partitioned and dedicated network resources in the cell site/sector, additional dedicated network resources may be partitioned to the TPA operation (block 211) to allow emergency response personnel to communicate.

In one embodiment, before terminating a call to assign an additional channel to the TPA operation, an unnecessary (i.e., non-emergency personnel) wireless device 101 having an ongoing call or session with the assigned channel may be notified with a warning tone and/or a vocalized unless a defined code is entered (block 210) that their call is being terminated. This allows the first responder to maintain their call by quickly entering a code (e.g., their PIN). The definition code may be provided by the PSAP if the call in progress is an emergency 911 call.

In one embodiment, the system will continue to automatically acquire and reallocate network resources for emergency response personnel communications until all available network resources are dedicated for use by emergency response personnel. This embodiment will maximize the communication capacity of emergency response personnel. Other embodiments may reserve at least a minimum portion of network resources (e.g., one communication channel) to enable the general public to alert emergency response personnel of new or developing emergency situations, such as by placing a 911 call. Thus, other embodiments may impose a maximum limit on the amount of network resources that are taken away from the general population and dedicated to emergency response personnel communications. To accomplish this, in block 209, the MSC104 may determine whether the maximum amount of network resources have been partitioned and dedicated to emergency response personnel communications. If the maximum amount of network resources has been partitioned and dedicated, MSC104 may continue to monitor the utilization level of the partitioned and dedicated network resources in block 208. If the maximum amount of network resources that can be partitioned and dedicated has not been reached, the MSC104 can (optionally) inform the current caller that the call is being terminated (block 210) and reallocate network resources from general population use to emergency response personnel communications (block 211). Once the additional communication channel has been dedicated, MCS 104 will return to monitoring the utilization level of the partitioned and dedicated network resources to determine whether the emergency is being upgraded or downgraded (block 208).

As emergency response personnel work to mitigate the emergency and return the situation to normal, the need for network resources will decrease as emergency personnel evacuate the field. To enable the system to return to normal operation, MSC104 may continuously monitor the volume of calls on the partitioned and dedicated network resources for indications of upgrades or downgrades (block 208). When the usage level of the partitioned and dedicated network resources drops below a predefined minimum, MSC104 may begin to reallocate the network resources back to general public use (block 212). Network resources may be automatically reallocated channel by channel, gradually reducing the use of the allocated resources to emergency personnel, and returning to normal operation in a step-wise manner.

By dispatching network resources one channel or network resource at a time, the embodiment provides a flexible, situation-adaptive communication system. The embodiment system and method can meet the demand if the situation requires more or less network resources for emergency personnel communication, while also providing some network resources for general public use. The system may wait a period of time after each release of the TPA dedicated channel to accommodate the surge in emergency personnel use during the event grace-out phase, thereby avoiding having to unnecessarily repeat the process of hanging up the caller (block 210).

Once the cellular communication channel has been reallocated for general public use, the MSC104 determines whether there are any more network resources currently partitioned and dedicated for emergency personnel communication (block 213). If additional network resources are currently partitioned and dedicated to emergency personnel communications, the MSC104 returns to block 208 to determine if the emergency is being upgraded or downgraded. As the emergency situation degrades further and returns to normal, emergency response personnel require less and less network resources to support their communications. Accordingly, the MSC104 will continue to automatically reallocate network resources to general public use in response to call volume (block 212) until all network resources are in a normal operating configuration for general public use. MSC104 may return to block 201 and may monitor the volume of calls waiting for the next emergency.

In a second embodiment, illustrated in the process flow of fig. 7, network resources are incrementally allocated to TPA use at various call levels by call preemption to maximize public access to the network while meeting emergency personnel usage requirements. During normal operation, cellular communication network usage is monitored (block 302). The network access request, the amount of calls, or the bandwidth in use may be compared to a predetermined threshold (e.g., 85% of maximum capacity) (block 304). If the usage is below the predetermined threshold, assuming normal conditions exist, the monitoring process returns to block 302 to continue monitoring the call volume. However, if the usage exceeds a predetermined threshold, an abnormal condition exists, which may indicate that an emergency is developing. To prepare for an emergency, network resources such as communication channels on the affected base station antennas are partitioned and reserved for TPA use (block 306). By automatically assigning a communication channel to TPA use, the system allows TPA-authorized wireless devices to gain access to the network even when the network is otherwise overloaded. However, TPA preemption does not occur until a TPA-qualified caller attempts to access an overloaded network.

Because the increased call volume may or may not be responsive to an emergency situation, the communication channel assigned to the TPA continues to function properly by handling civilian (i.e., non-TPA) calls in a normal fashion. In the case where the increased call volume is simply due to coincidental call volume and a TPA-disqualified user is attempting to place a call, call preemption by the TPA is not required. Thus, the TPA threshold can be exceeded and TPA is implemented even when TPA call preemption is not required. Delaying the actual implementation of TPA preemption until the first responder requests preemption increases the reliability of the network under normal circumstances.

With the network resources allocated to the TPA operation, the cellular system (whether in the base station, BSC/RNC, or in a central location such as an MSC) monitors incoming and outgoing calls (block 308). The channel to which the TPA is assigned continues to operate as a normal cellular communication channel until (a) the channel is at its highest capacity (i.e., the current amount of calls through the channel equals its maximum capacity) and (b) the TPA-qualified wireless device attempts to access the network to place or receive calls. The amount of calls on the communication channel to which the TPA is assigned is monitored to determine if the call must be dropped in order to connect a call that qualifies as a TPA. Thus, when receiving a new call (incoming or outgoing) that will also be assigned to a channel assigned TPA, the system may first determine whether the channel is currently at the highest capacity (i.e., has as many call connections as the channel can reliably maintain) (block 310). If the channel is not at the highest capacity (i.e., there is excess capacity on the network), the call may be connected (block 315). This monitoring of the TPA channel can prevent disconnection of the residential call if there is sufficient capacity on the channel to enable connection of the incoming or outgoing TPA call.

As discussed above, the system may identify calls for an authorized TPA by determining whether the source or destination wireless device is a TPA-registered wireless device (block 312) and whether the call was made by a caller completing a particular dialing procedure. The dialing process may invoke TPA preemption (block 316). In block 315, the call may be connected. For example, if a caller is using (or placing a call to) a TPA-registered wireless device, the call may be connected. If at least one non-TPA call is connected on the channel to which the TPA is assigned, the call may be connected (block 314) and the capacity is released to be sufficient to connect the TPA call (block 315). This allows the TPA-qualified first responder to make calls without delay, even if the network is at maximum capacity. Similarly, if the incoming call is directed to a TPA-qualified wireless device, at least one non-TPA call is terminated on the TPA channel for connecting the incoming call to the TPA-qualified wireless device. The process of terminating a non-TPA call from an assigned channel may continue with more calls to the TPA-qualified wireless device accessing the network. If the caller is not using a phone registered with a TPA and is not entering a 272 type dialing sequence, the call may be blocked as a non-emergency call when the system is at maximum capacity (block 320). If the caller has entered a special dialing sequence (e.g., 272 plus a PIN), the entered PIN is compared to a PIN value stored in a database (e.g., at the base station 102, BSC/RNC103, or MSC 104) (block 318). If the PIN matches a registered emergency person, a non-TPA call is placed on the channel assigned the TPA (block 314) so that the release capacity is sufficient to place the TPA call (block 315).

The system may also monitor the amount of calls on the channel to which the TPA is assigned (block 322) to ensure that sufficient capacity remains to accommodate further emergency personnel requirements. The TPA call volume on the communication channel to which the TPA is assigned (i.e., the call volume to/from the TPA-qualified wireless device) may be compared to a threshold in block 322 to determine when another communication channel is assigned to TPA use. If the TPA call volume threshold is exceeded (i.e., test 322 yes), another channel will be assigned to the TPA function block 306, as discussed above.

The TPA call volume on each channel to which TPA is assigned may continue to be monitored (block 322), as well as the call volume on all channels (block 324). This may determine when the TPA call is no longer being made, such as would occur when the emergency is resolved and the first responder leaves the scene or when the total call volume returns to a level at which TPA operation is no longer required. If the call volume continues to exceed the TPA threshold, the system may continue to operate at least one channel in TPA mode, accept the call (block 308), check the TPA channel call volume (block 310), and place the call (block 315), if the call is from/to a wireless device that is authorized for TPA (block 312) or if the call volume is less than capacity. As the TPA call volume decreases, the number of channels allocated to the TPA operation may be reduced by releasing the TPA channels (block 326). Monitoring call volume and releasing channels from TPA assignment will continue until all communication channels are returned to normal operation. Furthermore, if the call volume on the non-TPA channels drops back to normal, the system may deactivate TPA operation on all assigned channels, since the normal capacity of the network may accommodate TPA-qualified callers without TPA preemption.

This second embodiment allows operating the channel allocated with the TPA in a manner that ensures that each caller authorized the TPA can access the network while providing the maximum possible bandwidth to the general public. Monitoring the TPA channel call volume allows the system to avoid hanging up a residential call if there is sufficient capacity on the channel to enable connection of a new incoming or outgoing TPA call. If no emergency response personnel initiate a call using the wireless device or special dialing process of the authorized TPA, the system may continue to monitor the access request (block 308), and the call volume (block 324) to determine if the communication channel should be released from the TPA operation (block 326).

Additional embodiments provide prioritized access to TPA-specific network resources to enable highest priority callers to use the cellular communication network. In the event that the number of emergency responders would exceed the capacity of the cellular network resources, this embodiment may enable high priority users, such as country leaders and field directors, to preempt other lower priority users in order to gain immediate access to the network. High priority users may use their pre-registered wireless devices to gain access to the network. The unique ID of their wireless device may be used to determine the user's priority from a database of unique IDs. Similarly, high priority users may identify themselves to the network using a special dialing process with a code or PIN that provides sufficient information for the network (e.g., MSC 104) to determine the user's priority from a PIN database. Using the priority value determined from the database, the network (e.g., MSC 104) may determine whether the current caller has a higher priority than any call already connected to the TPA-assigned network resource. Assuming that the wireless device 101 is properly authorized, the call may be given priority in queuing on the network resource to which the TPA is assigned so that emergency personnel members using pre-registered authorized wireless devices may be able to complete the call. If the network resources are at the highest capacity, calls from people with lower priority levels may be hung up in order to free up sufficient capacity to complete the call.

Fig. 8 shows an example hierarchy of emergency response personnel. Various other configurations are possible and may include other personnel, and the role or status of the personnel may change based on the event, e.g., military commander 302 may assume the role of administrative leader, etc. As shown in fig. 8, administrative leaders and policy makers 301 may be given the highest priority. Members of this level may pre-register their wireless device 101 to store the unique identifier of the wireless device 101 in the hierarchical database. If a call is placed from any pre-registered wireless device to a member of administrative leadership and policy maker level 301, the call is first placed in any queue of partitioned and dedicated network resources. Similarly, disaster response/military commands or control personnel 302 may be provided with a next highest priority level, followed by public health, security, and law enforcement commands 303, public services/utilities and public welfare 304, and disaster response teams 305. Lower levels of priority may be provided to front-line police and fire personnel 306 and emergency medical technicians 307. In all cases, the wireless devices may be pre-registered so that their unique identifiers and/or the user's PIN may be stored in a hierarchical database to support this embodiment.

The foregoing embodiments may also be implemented in a cellular system using a deployable "round robin switch" cellular communication system. Since such systems can be implemented in a large-scale emergency/disaster situation, limiting access to emergency responders and command authorities, network overload will occur from too many authorized (i.e., non-residential) users placing calls at the same time. To ensure reliable communication in such situations, a deployable on-turn switch may implement a caller priority embodiment such that callers with the highest priority (e.g., country and regional commanders) have guaranteed access to cellular communication, while the lowest priority authorized users may be disconnected, if desired. In this embodiment, a database of authorized users indicating various priority (tier) levels (e.g., as shown in FIG. 8) may be maintained in a server within a deployable on-turn switch.

The foregoing embodiments have been described as being implemented by the MSC 104. Those of ordinary skill in the art will recognize that the foregoing embodiments may be implemented within a plurality of computer switching system elements within a cellular communication network, including but not limited to a base station 102, a BSC/RNC103, or a NOC. Monitoring of call volume on the communication channel and within the cell has been performed automatically. Such a system may be reprogrammed to implement the foregoing embodiments so that the implementation of the TPA operation is performed automatically. Thus, the system may automatically identify when the call volume exceeds a threshold such that a communication channel should be assigned to the TPA operation. The system may further identify the call and dedicated network resources of the authorized TPA and automatically perform the call connection and disconnection. Similarly, the system may automatically return the network to a normal configuration as the call volume falls below the TPA threshold level. In this way, the cellular communication network may respond to an emergency situation, thereby enabling guaranteed communication for emergency personnel without requiring human action or intervention. For example, even if an event is not reported (e.g., no one is operating to dial 911), the system will still enable emergency responders to use the network in response to an excessive amount of calls. This capability also ensures that police, fire and EMT personnel (typically people who may be authorized to implement TPA) can use the cellular communication network during times of peak use, such as during periods of congestion on highways or after major sporting events have ended.

The hardware used to implement the foregoing embodiments may be a processing element and a memory element configured to execute a set of instructions for performing method steps corresponding to the above methods. Such processing and memory elements may take the form of computer-operated switches, servers, workstations, and other computer systems used in cellular communications centers as well as remote facilities (e.g., base station antenna locations). Some steps or methods may be performed by circuitry that is dedicated to a given function.

Wireless devices use portions of the Radio Frequency (RF) spectrum that are dedicated to cellular telephone communications. This RF spectrum is shrinking at a fast pace, primarily due to the increasing number of wireless devices using the already burdened RF bandwidth and the inefficient allocation of bandwidth in the marketplace. As the total RF spectrum is limited, as the number of users of the RF spectrum increases, more efficient RF spectrum management methods are required to ensure that the increasing demand for the RF spectrum is properly addressed.

The currently available RF spectrum is divided among cellular service providers based on static allocation models such as speculative models and classical licensing transactions. The static allocation model of current practice relies on a command and control scheme that allows the allocation of spectrum to providers in defined blocks of frequency and space. For example, one static method of leasing RF spectrum includes assigning entire blocks or sub-blocks of spectrum to one operator for their exclusive use based on a leasing protocol. Such bulk allocation of spectrum is inefficient because licensed providers are purchasing the spectrum based on speculations that the spectrum may be used in the future.

However, spectrum usage and traffic are dynamic and may depend on different variables including time information for using the spectrum and the geographic location of the wireless device using the spectrum. Traffic usage may be time dependent, as usage may vary during peak versus off-peak hours. Traffic may also be based on geography, as the location where the subscriber uses the network may also vary. For example, time and geographic based usage of spectrum on a network may vary during the day as subscribers travel to work, at work or return from work, or during off-hours.

Because spectrum usage and traffic is dynamic and unpredictable, a provider will inevitably waste spectrum resources by predicting future usage about it. Thus, current spectrum allocation schemes do not take into account real-time data about traffic patterns, encouraging further inefficiencies under utilization and subdivision of spectrum and through implementation of guard band and bandwidth throttling or bandwidth intensive features and services.

Various embodiment methods and systems provide a Dynamic Spectrum Arbitrage (DSA) system for dynamically managing the availability, allocation, access, and use of RF spectrum using real-time data. Currently, RF spectrum is licensed or purchased in frequency and space based on predictions of future use without taking real-time data into account. DSA communication systems make the RF spectrum available on a frequency, spatial (i.e., geographical area) and temporal basis, and thus provide a spectrum management method and system that is flexible and dynamic compared to current static command and control methods. Since RF spectrum resources are available on a time, frequency, and space basis, spectrum allocated by DSA communication systems is available for short-term lease and is not interfered with. Short term leases of spectrum may increase competition in a given market area and improve spectrum efficiency without negatively impacting the operator's ability to deliver services. DSA communication systems may actually increase the availability of RF spectrum by efficiently and dynamically managing spectrum availability, allocation, access, and usage.

In one embodiment, the DSA communication system may be a separate service affiliated with the participating providers. In such scenarios, the components of the DSA communication system may be integrated units participating in the network provider to allow the provider to monitor their resource vs. bandwidth traffic and determine whether they need or are able to provide additional resources. Non-integrated components of DSA communication systems may manage the overall exchange of resources between participating providers. Benefits of using DSA communication systems may include optimizing business revenue and providing wider and more efficient use of bandwidth on a physical (geographic) and temporal basis.

In one embodiment, DSA communication systems may enable allocation/access of RF spectrum resources by requiring participating providers to subscribe to the DSA communication system. For example, the subscription may be based on a pricing arrangement. As a participant in DSA communication systems, RF spectrum request providers may be enabled to use any available RF spectrum by sliding within and outside "swim lanes" of the spectrum depending on their demand for bandwidth and their preparation to pay for it. A "swim lane" of a spectrum will be the RF spectrum bandwidth that is possessed/controlled by a provider.

To participate in a DSA communication system, one or more operators may initially agree to allow secondary use of their spectrum in the market. DSA communication systems may enable each provider to purchase available spectrum or offers in the provider's network to sell additional spectrum to buyer providers.

In one embodiment, the DSA communication system may determine the compatibility of the subscriber wireless devices 101 using the secondary network and the cluster. If the subscriber device is capable, an incompatible Radio Access Network (RAN) may be used. Thus, if wireless devices 101 are able to access different RANs, DSA communication systems may facilitate these devices accessing spectrum from other RANs, even if the switch is between incompatible RANs. DSA communication systems are policy based and may provide unique implementations for spectrum and capacity management. DSA communication systems may be based on Long Term Evolution (LTE), evolution-data optimized or evolution-data only (EVDO), evolved High Speed Packet Access (HSPA), and any known wireless access platform.

Fig. 9 illustrates a communication component diagram 900 of an embodiment DSA communication system in a long term evolution, LTE, based wireless access platform. The DSA communication system may include a dynamic spectrum policy controller (DPC)902 connected to a Home Subscriber Server (HSS)904 that may communicate with network components of the provider network. The HSS904 may be a primary user database that supports the dynamic spectrum policy controller (DPC) 902. HSS904 may include subscription-related information (i.e., subscription profiles), perform authentication and authorize secondary users, and may optionally provide information about the location of subscribers and IP information. The HSS904 may contain the user's (SAE) subscription data, such as the EPS subscribe to QoS files or any access restrictions for roaming. It may also maintain, store, or retain information about PDNs to which users may connect. This may take the form of an Access Point Name (APN), which is a label according to the DNS naming convention describing access points to PDNs, or a PDN address, indicating one or more IP addresses for subscription. In addition, the HSS904 maintains dynamic information, such as the identity of the mobility management entity ("MME") to which the user is currently attached or registered. The HSS904 may also integrate an authentication center (AUC) that generates vectors for authentication and security keys.

The HSS904 may be connected to a signaling server 7(SS7) 906. Both the dynamic spectrum policy controller (DPC)902 and the HSS904 may be connected to the internet 106. The HSS904 may communicate with the intra-network components of the network independently via the SS7 network 906.

The DPC902 may also communicate with network components of a network provider through a commercial or private wireless carrier 903 and a Dynamic Spectrum Controller (DSC)910 or directly through the DSC910 without using a commercial or private carrier. The DSC910 component may be added to a network component for a network that participates in the DSA communication system and may communicate with the OMC/NMS 910. In various embodiments, the DSC910 components may include wired or wireless connections to policy control and charging rules function (PCRF)905 components/servers.

Availability of spectrum resources

In various embodiments, DSA communication systems may enable spectrum providers to monitor and evaluate its RF spectrum usage and availability, and make unused RF spectrum available to other providers or to unsubscribed users (i.e., secondary users). DSA communication systems may provide different methods to determine RF spectrum availability, such as location and database lookup, signal detectors, and spectrum usage beacons. DSA communication systems may enable one provider (host network) to identify spectrum resources available for use by another provider or provider subscribers (secondary users), such as payments on a per-use or per-minute basis.

In one exemplary embodiment, as shown in fig. 9, DSA communication system 900 may enable a network to determine the availability of RF resources. At each network or sub-network, the DSC910 may monitor call traffic through the OMC/NMS 912 to receive details of various network elements in real time without inserting another device into the network. The DSC910 may perform policy-based QoS decisions based on the state of existing traffic, projected traffic headroom, and system policies in order to determine whether a network or subnetwork has resources to allocate or demand resources from another provider for secondary use.

The DSC910 may be configured with software to communicate data regarding the availability of spectrum resources to the DPC902 using capacity policy criteria. The data communicated to the DPC902 may include data relating to the current excess capacity and the anticipated future capacity of the network or sub-network.

Resources available at a network provider may be dynamically allocated and deallocated. Resource polling information may be controlled by the DSC910 and forwarded to the DPC902 for central coordination. However, based on the rule set in the DSA communication system, the DSC910 may identify resources available for secondary use on a system level and cluster level, as traffic in the system fluctuates through increases and decreases, the pool of resources for secondary use may increase and decrease and may be reported to the DPC902 via the DSC 910.

Allocation of available resources

In various embodiments, a Dynamic Spectrum Arbitrage (DSA) system may further manage allocation or assignment of network provider's RF spectrum resources for specific uses, such as use by secondary users. DSA communication systems may manage RF spectrum allocation based on varying criteria of the provider, such as degree of priority (e.g., low priority or no priority), type of connection (e.g., "always on" and "surge" guaranteed access and bandwidth), and price.

In contrast to currently available spectrum allocation techniques, allocation of spectrum resources by DSA communication systems may be dependent on the real-time traffic status of the participating providers. DSA communication system resource allocation may further depend on different factors such as the availability of resources, the type of services being delivered, and policies associated with those services. Some key policy criteria that may be considered for allocating resources in DSA communication systems may include radio access selection, capacity increase, quality of service (QoS), bearer selection, congestion control, routing, security, and classification. DPC and DSC910 may perform policy definition and control.

Radio access selection: DSA communication systems may be configured for optimal available spectrum assignment from the available resource pool. Factors considered in the selection of a spectrum assignment may include spectrum bandwidth, location of spectrum in a frequency band, geographic area along the requested service, and QoS.

Capacity increase: DSA communication systems may be configured for best available capacity increase assignment from a pool of available resources. Factors considered in the decision may include spectrum bandwidth, location of spectrum in the band, geographic area along the requested service, and QoS.

Carrying and selecting: the DSA communication system may be configured for selecting resources required to support a requested QoS profile at a radio and transport bearer service.

Admission control: DSA communication systems may be configured for maintaining information of available/allocated resources in both radio and IP transport networks and performing resource reservation/allocation in response to new service requests.

And (3) congestion control: DSA communication systems may be configured as a method for monitoring traffic conditions on a primary network and finding alternatives for capacity offloading. Further, the DSA communication system may be configured to monitor the primary network and perform back-off of secondary users as traffic needs on the primary network increase.

Routing: DSA communication systems may be configured to ensure that optimal routing is used for services based on bearer traffic and available network resources.

Safety: DSA communication systems may be configured to provide security for traffic flows by splitting the traffic into multiple tunnels to ensure no cross-talk of information.

Grading: DSA communication systems may be configured to coordinate a hierarchical scheme including prioritization and operator royalties, as well as other metering processes.

DSA communication system resource allocation may be based on different methods, such as a stateless method and a stateful method. By employing different allocation methods, DSA communication systems may enable providers to customize spectrum allocation and utilization based on their respective spectrum traffic needs. A nationless approach may involve coordinating spectrum usage between networks on a real-time basis. A national approach may include storing and forwarding spectrum resources following a defined time interval. RF spectrum resources may be further allocated on an as needed basis, which may be based on committed and peak bandwidth/traffic requirements. The need-based allocation method may allow maximum flexibility and spectrum utilization. DSA communication systems may further employ just-in-time allocation methods to enable providers to allocate spectrum resources. By employing just-in-time allocation methods, DSA communication systems can improve overall spectrum utilization for a given market and provide a source of revenue for wireless operators.

In one embodiment, a DSA communication system may provide command and control functions to be implemented as an entire licensed region or as defined sub-licensed regions and lease spectrum for a certain term. For example, DSA communication systems may facilitate spectrum resource allocation using a sub-spectrum block approach, with the ability to increase or decrease dynamically consumed spectrum. For example, multiple different communication networks may allocate spectrum to the same user.

As shown in fig. 9, a component of a DSA communication system that is not part of a provider network, such as the DPC902, may manage spectrum allocation between different networks or subnetworks.

In one embodiment, a DSA communication system may enable a host network to provision a resource allocation currently assigned for use by a primary user for use by a secondary user. In this scenario, secondary users may be granted access to the spectrum capacity or resources of the host network, regardless of the existing available capacity of the host network.

Management and policy management

DSA communication systems may operate based on predetermined rules and parameters, which may be based on statistics of channel availability. For example, the operating rules may enable DSA communication systems to monitor the level of access to the RF spectrum at any given time to allow the system to determine whether capacity is available for allocation.

As described above, resource allocation may be performed by DSA communication system components (e.g., DPC902 and DSC 910) that follow rules defined by traffic arrangements, device compatibility, target system RAN and capacity, and requested services.

Figure 9 further shows a network architecture 900 for implementing an embodiment method of DSA policy management. DSA communication systems may require participants to comply with regulatory rules and policies.

In implementing DSA policies, a policy control and charging rules function (PCRF)905 participating in the network may provide policy and service control rules andthe policy control network (RPCN) may provide policy changes and corrections based on DSA rules and DPC902 requirements. The PCRF may be responsible for policy control decision making, as well as controlling the flow-based charging functionality in a Policy Control Enforcement Function (PCEF), which resides in the PGW. PCRF provides QoS authorization (QoS level identifier [ QCI ]]And bit rate) that decides how a certain data flow will be treated in the PCEF and ensures that the data flow and authorization are consistent and conform to the user's subscription profile. The RPCN may be part of each network DSC 910. The RPCN may further maintain hotlists (Hot lists) for public safety users who may also be linked to the business system.

For example, when the resources of the host network are exhausted, the network PCRF 905/RPCN may instruct the host network to take action to recover the additional resources for the preferred user of the home network. The instructions sent by PCRF 905/RPCN may be used to determine the procedures that need to be taken to release the action of resources for the use of the preferred user. For example, the PCRF 905/RPCN instructions may lower the QoS of the secondary user wireless device 101 or certain applications or shed the secondary user wireless device 101 from the network based on a set of conditions. The host network may implement the slot allocation when managing its level of resources by reducing traffic.

Some optional subcomponents of the EPC may include an MME914 (mobility management entity), which is a key control node for LTE access networks, and may be responsible for idle mode UE (user equipment) tracking and paging procedures, including retransmissions, and may participate in bearer activation/deactivation procedures and also be responsible for choosing an SGW for a UE at the time of initial attach and handover within LTE involving Core Network (CN) node migration. MME914 may be responsible for authenticating users (by interacting with HSS). Non-access stratum (NAS) signaling terminates at MME914 and may also be responsible for generating and assigning temporary identities to UEs. The MME914 may check the authorization of the UE to camp on the Public Land Mobile Network (PLMN) of the service provider and enforce UE roaming restrictions. The SGW 922 (serving gateway) may route and forward user packets while also acting as a mobility anchor for the user plane during inter-eNodeB handovers and between LTE and other 3GPP technologies. The PGW908 (PDN gateway) provides connectivity from the UE to external packet data networks by acting as a traffic exit and entry point for the UE. The UE may have simultaneous connections with more than one PGW908 for accessing multiple PDNs. HSS 926 may be a central database that contains subscriber-related information and subscription-related information. The functions of the HSS 926 include, for example, mobility management, call and session establishment support, user authentication, and access authorization. ANDSF 918 (access network discovery and selection function) provides information to the UE about connecting to 3GPP and non-3 GPP access networks (e.g., Wi-Fi). The purpose of ANDSF 918 is to facilitate UE discovery of access networks in its vicinity and to provide rules (policies) to prioritize and manage connections to these networks. The network 900 may also include an ePDG (evolved packet data gateway) to secure data transmissions with UEs connected to the EPC through untrusted non-3 GPP access networks.

DSA communication system policies and administration may have the same attributes as those found in a business network. However, in DSA communication systems, the combination of policy-driven QoS and dynamic spectrum arbitration/allocation can both improve primary and secondary (e.g., lessor and lessee) spectrum utilization and reduce overall cost.

In one embodiment DSA system, policies/administration may be set for a particular level of network resources per session, per "pipe", per user or group of users. The policy may also relate to priority, such as emergency calls taking the highest priority, or preferences, such as allowing degradation of the quality of ongoing calls or rejecting new calls when congestion is approaching. DSA policy and management may also invoke daily policies that may be used to facilitate optimal routing for particular types of communication sessions and service offerings.

Allocating resources for accessing another network

In one embodiment, a DSA communication system may manage access of users to the available RF spectrum resources of a network. For example, DSA communication systems may manage access of secondary users to spectrum resources allocated to a secondary used primary host network.

Secondary users may access spectrum resources of the primary host network using different methods, such as by acting as dynamic roamers or using a spectrum scheme coordinated with a compatible access technology. In allowing secondary users to access the primary host spectrum resources, DSA communication systems may enable wireless devices 101 of subscribers of one provider to change bandwidth from spectrum belonging to the home network provider of the wireless device 101 to spectrum belonging to the host network provider based on different parameters (such as price, reception quality, geographical area, and location).

DSA communication systems may provide access to secondary users based on different access conditions. DSA communication systems may provide access to the available spectrum either temporarily or by sharing traffic throughput for the radio access technology with primary users of a primary provider. Temporary access may involve accessing a defined spectrum allocated for use based on a policy of the DSA communication system. Sharing spectrum may involve allowing subscribers of one provider to access the radio spectrum at a host provider on a secondary basis.

The secondary user's home network provider may dynamically contract for the primary provider's allocated RF spectrum resources using different methods. For example, a primary provider may auction and a secondary provider may bid for available spectrum resources. Bidding may be a fee-based process; may involve managing reselling of unused spectrum on a temporary or permanent basis to efficiently manage excess resources that are otherwise unused at the time; or to manage the leasing of the remaining RF spectrum on a temporary or permanent basis.

Fig. 10 shows a network architecture 1000 of two wireless network providers that share spectrum resources using DSA communication systems. DSA communication systems may include two general components: an out-of-network component and an in-network component. The out-of-network components of the DSA communication system may include a DPC902 connected to a HSS 904. The DPC902 may enable the DSA communication system to dynamically manage access to the allocated spectrum resources of the network. For example, the DPC902 may manage access of secondary users of the network provider to allocated spectrum resources of the primary network provider.

The DPC902 may further coordinate DSA communication system policies and enforce the sharing of relevant information between network providers. DPC902 may further facilitate charging policies and resource requests that may be communicated with the network.

The DPC902 may be configured for communication with one or several networks (e.g., network 1 and network 2) by each DSA communication system participating in the provider's in-network DSC910 components. In one embodiment, each network 1 and 2 may include a DSC910a, 910b, which may be an add-on to a wireless carrier's online management center/network management system (OMC/NMS)912a, 912 b. At each network, the DSCs 910a, 910b may manage the traffic and capacity of each network and continuously monitor the nodes for capacity constraints based on commands received from the DPC902 or its policies and rule sets. The DSC910 may communicate its discovery to the DPC 910.

Each network may include an OMC/NMS 912a, 912b, which may communicate with the wireless networks 1002a, 1002 b. The wireless networks 1002a, 1002b may communicate with the wireless access nodes 102a, 102 b. The subscriber wireless device 101 may communicate with the wireless access nodes 102a, 102 b. The relationship and interconnection of these components of the network is known.

In one embodiment, the DSC910a of network 1 may determine that network 1 may require additional resources. The DSC910a of network 1 may be configured to send a request to the DPC902 for additional resources. DPC902 may receive information regarding the location and network of secondary user wireless device 101 a.

DPC902 may be configured to also receive data from other attached networks, such as DSC910b from network 2. The DSC910b of network 2 may be further configured to report to the DPC902 that a specified amount of resources are available in network 2.

DPC902 may be configured to process data received from a requesting network (i.e., network 1) and a provisioning network (i.e., network 2) and facilitate real-time access to resources of network 2 through requesting network 1. Once spectrum resources from network 2 are made available for access by users of network 1, DSC910a may instruct wireless device 101a to change networks and access spectrum resources provided by network 2. For example, when a wireless device 101a of network 1 requests communication resources, its rule set may be validated by the DSC910 of network 2. Network 2 may receive updated information for wireless device 101a in PCRF905 (shown in fig. 9). PCRF905 using other platforms may allow secondary user wireless device 101a to access the allocated resources of network 2.

In one embodiment, the accessibility of resources to secondary users through DSA communication systems may also depend on host network operator policies and usage criteria for those resources. The criteria may include both radio access and core network resources.

For example, some policy and resource criteria imposed by the host network operator may include: availability of spectrum (e.g., separate or co-existing); capacity/bandwidth availability (e.g., RF and core); overhead criteria (e.g., total available capacity vs. percentage of capacity used); the existence of backoff criteria (e.g., reselection, handover (intra-and inter-system), termination); treatment (how to treat/route a particular service/application); treatment is prohibited (e.g., use of services/applications is prohibited); rating (e.g., how to rate services, i.e., special discounts possible for off-peak usage); geographic boundaries (e.g., defining an area or cell to be encompassed); time (e.g., defining the time and date to include); duration (e.g., defining delta allocations based on time and geographic boundaries); the user equipment type.

DSA communication systems may enable secondary networks to request spectrum resources based on: time (e.g., when a resource is requested); required capacity/bandwidth; treatment (e.g., what services, including QoS, are desired); geographic boundaries (e.g., where to request service); and duration (e.g., how long to request resources).

In one embodiment, the communications performed by the DSCs 910a, 910b may be transparent to the secondary user. In another embodiment, the communication may not be transparent.

Fig. 11 shows a network component diagram 1100 of an embodiment DSA communication system in which processed spectrum usage and traffic data may be cleared by a third party or spectrum. The out-of-network components 1102 of the DSA communication system may include a number of subcomponents, such as the DPC902 (shown in figure 9). DPC902 may communicate with wireless networks 1 and 2 by communicating with subcomponents of the core networks 1104a, 1104 b. The out-of-network component 1102 may also communicate with one or both networks using the internet or private network 106. For example, the DSA communication system extranetwork component 1102 may communicate with the core network 1104b of network 2 via the internet 106 while communicating directly with the core network 1104a of network 1. The core network 1104a, 1104b may include a number of subcomponents such as DSC910, Long Term Evolution (LTE), (EVDO), (HSPA), and OMC/NMS 912 a.

When the network 1 becomes overburdened and requires additional spectrum resources, the core network 1104a may determine the requirements for spectrum and request additional spectrum resources from the DSA communication system out-of-network component 1102. Due to low call traffic, the network 2 may determine that it has an excess amount of spectrum resources available. The network 2 may also report the availability of excess resources to the out-of-network component 1102. Communication between the DSA out-of-network component 1102 and the network 2 may be through the internet 106. Alternatively, the out-of-network component 1102 and the network 2 may communicate directly as indicated by dashed line 1106. The DSA out-of-network component 1102 may facilitate allocation of spectrum resources from network 2 to network 1 as shown here by the dashed line 1108.

The wireless device 101b may access the allocated resources by different methods. Network 1 may instruct wireless device 101b to switch the network to network 2 to use the allocated resources as a secondary user on network 2. Alternatively, the allocated resources of network 2 may be made available through network 1, enabling wireless device 101b to use the resources of network 2 without having to change the communication session from network 1 to network 2. For example, networks 1, 2, and 3 may aggregate spectrum that may be allocated for use by multiple entities.

Figure 12 shows a communication system 1200 of a DSA network of one embodiment. When serving several different networks, the DPC902 may provide the primary control for the arbitration process. DPC902 may include policies for current allocations and time-dependent arbitration rules. The DSC910 may be configured to also have a local copy of the policy and time-dependent arbitration rules for the current assignment. Local copies of policies and time-dependent arbitration rules may ensure that local control of network resources may be maintained. Further, the DSCs 910a-910c may be separate platforms that interface with network operating systems that provide a demarcation point for future network operating issues.

In one embodiment, to ensure disaster recovery of the system upon the occurrence of an event, the DPC902 may be configured as a dual mirrored server site (e.g., DPC902a and DPC902 b) or include several servers in a geographically dispersed cluster. To protect the network, the DPC902a, 902b may have a secure link to defined and pre-approved network operators 1204a, 1204b, 1204c (e.g., spectrum resource providers) and system resource requesters 1206, 1208, 1210 (e.g., bidders).

In the event of a failure of communication between the DPC902a, 902b and the DSC910a, 910b, 910c, the DSC910a, 910b, 910c may be configured to use its locally-saved policies and rule content to maintain continuity in the arbitration process that has been initiated by the DPC902a, 902 b. However, due to lack of connection with the DSCs 902a, 902b, the DSCs 910a, 910b, 910c may not be able to facilitate additional new resource allocations or bids. To ensure that local control is always maintained, the DSCs 910a, 910b, 910c may be further configured to control and locally override a number of components and functions that enable the local operator to prematurely terminate or back off resources from secondary users.

For example, DSC910a may locally store policies and rules for any communicating DPCs 902a, 902 b. As such, if communication between DPC902a, 902b and DSC910a is compromised after a bid that has been processed by DPC902a, 902b, DSC910a may continue to provide resources to the secondary user of bidder 11206 without terminating the secondary user. Further, when network a 1204a requires more resources to provide service to its own primary user, DSC910a may locally control offloading of secondary users from network a to free up resources based on policies and rules of DPCs 902a, 902 b.

In one embodiment, the procedures involved in a DSA communication system may be similar for all cases of flows. As shown in fig. 13A, the resources of the spectrum block 1300A may be classified based on how they are used by the network. Resources for a given spectrum may be classified into occupied resources, uncertain resources, and available resources. The occupied resources may be those currently used by the operator and may not be allocated by the DSA communication system. The uncertain resources may provide a margin for the operator to manage peak loads. The uncertain resources can be used up during high peak loads and not used during low peak loads. The available resources may be a subset of resources that are not used at all by the network. The available resources may be made available for allocation to other secondary providers.

In one embodiment, the secondary users may be allocated spectrum resources by different methods. Fig. 13B shows allocation of spectrum resources of a spectrum block 1300 licensed by a host network according to one embodiment. The host network may license RF spectrum block 1300a that includes four channels. The host network may dedicate three of the four channels of the RF spectrum block for use by network 1 subscribers. Dedicated channels 1-2 are shaded in RF spectrum block 1300 b. As shown by RF spectrum 1300b, channel 4 may remain unassigned by the provider. Channel 3 may be partially allocated, partially transitioned, and partially unassigned, as shown by spectrum block 1300 c. A transition portion of the spectrum block 1300c may be reserved for use by subscribers of the provider during periods of high traffic. Unassigned portions of licensed spectrum 1300c may never be used.

In one embodiment, the host network may utilize a DSA communication system to subordinate license unassigned portions of the licensed spectrum to secondary users. In this scenario, the host operator may make both the unassigned portion of channel 3 and all of channel 4 available to secondary users.

Fig. 14 shows allocation of spectrum resources of a guard band channel comprising licensed spectrum 1400 according to one embodiment. Licensed spectrum 1400 may include guard bands 1404 that are either defined by the operator or set aside as part of spectrum deployment policies and procedures. Such guard bands may include useful resources that are not currently in use. The host network may use a DSA communication system to allow secondary users to use the resources available in the guard band. By using DSA, the host network may make available for using unused guard band resources by combining guard bands into a single useful channel 1402 for resource allocation.

Fig. 15 shows aggregation and allocation of spectrum resources for more than one host network using a DSA communication system, according to one embodiment. In one embodiment, a DSA communication system may be configured to investigate available spectrum from different networks and aggregate the available spectrum for allocation. In the exemplary embodiment illustrated by spectrum block (1), each of the host networks, network a and network B, may license a spectrum block that includes four channels each. For example, a spectrum block 1502A licensed by network a may include channels 1A, 2A, 3A, and 4A. The spectrum block 1502B licensed by network B may include channels 1B, 2B, 3B, and 4B.

In an exemplary embodiment as shown by spectrum block (2), spectrum block 1504A of network a may include available channel 4A and partially assigned channel 3A. Channel 3A may be assigned partially for use by the network, partially transitioned and partially available for use by other networks. Spectrum block 1504B for network B may include available channels 1B and 4B and partially assigned channel 3B. Channel 3B may be partially assigned for network use, partially transitioned, and partially available for allocation to other networks.

In one exemplary embodiment, as illustrated by spectrum block (3), each of the spectrum blocks 1506A, 1506B of network a and network B may have their resources available by using a DSA communication system. DSA communication systems may aggregate the available resources from each network and allocate them to secondary users. For example, DSA communication systems may aggregate the resources available in channels 1B and 4B and make them available to secondary users. The DSA communication system may pool the resources available in channel 4A and part of the resources available in channel 3A and make them available to the secondary users.

DSA communication systems may aggregate available resources from different networks for allocation to secondary users. In one exemplary embodiment, as shown in spectrum block (4), the DSA communication system may pool the available resources from channel 4A in network a, spectrum block 1508A, and channels 1B and 4B in network B, spectrum block 1508B and make them available to secondary users.

In one exemplary embodiment, as shown by the spectrum block (5), the DSA communication system may aggregate available resources from all channels in different networks, including channels having resources fully available to the network and channels including available resources. DSA communication systems may pool spectrum resources from channels 3A and 4A in network a (spectrum block 1510A) and channels 1B, 3B, and 4B of network B (spectrum block 1510B) and make them available to secondary users.

In one embodiment, a DSA communication system may enable a Mobile Virtual Network Operator (MVNO) to utilize unused spectrum capacity. For example, DPC902 may aggregate multiple MVNOs to utilize unused spectrum capacity in a prioritization scheme. This would enable an MVNO to sell its unused or unspent capacity to another MVNO, thereby ensuring efficient operation of the MVNO.

Fig. 16A-16C show MVNO spectral aggregation according to one embodiment. Fig. 16A shows allocation or capacity of spectrum for MVNO a1602A and MVNO B1602B, where both operators have unassigned spectrum capacity. Fig. 16B illustrates an example embodiment method by which a DSA communication system may enable MVNO B1604B to increase or augment its available spectrum capacity by receiving unassigned spectrum from MVNO a 1604A. Fig. 16C illustrates an example embodiment method by which a DSA communication system may enable one MVNO C1606C to receive additional spectrum capacity from two other MVNOs 1606A, 1606B. MVNO C1606C may be a new or additional MVNO and may obtain available unassigned spectral capacity for its potential use from MVNO a and MVNO B1606A, 1606B. In this scenario, MVNO a and MVNO B1606A, 1606B may or may not operate on the same host operator and may or may not have the same Radio Access Technology (RAT). In another embodiment, a transition may be provided to provide access between different RATs.

In one embodiment, to measure the amount of resources used by the secondary user, the host network may use a similar process as used for pre-paid users to facilitate the time/duration of secondary usage and usage metering, which may be on an individual or global billing basis.

Depending on the method used by the secondary users to access the available resources, several basic types of DSA allocation methods can be implemented, including: 1) a virtual best effort approach; 2) a virtual secondary user method; and 3) a spectrum allocation method that may include both licensed region and local region spectrum allocations. Each of these distribution methods may have several variations. For example, in a virtual best effort approach, DSA communication systems may be configured to make spectrum resources available for the entire licensed region or on a local, sub-licensed region basis. The rank of the user may also be defined in the user's wireless device 101 by their home network provider and may be assigned either a secondary user or best effort user status.

In one embodiment, the virtual best effort approach may be available to the MVNO through authorization of access to the involved networks. Prioritization may occur within the host network based on PCRF rules for the home network and the host network.

In a virtual best effort approach, the host network may enable the secondary consumer wireless device 101 to use the same network as the host network, but on a virtual basis, i.e., an MVNO type arrangement. Different variations of this arrangement may include a variety of situations when: 1) the secondary user uses the host network with the same permissions as the host network subscriber and 2) the secondary user uses the host network as a secondary user or on a secondary basis where the primary user (host subscriber) has higher priority and permissions than the secondary user subscriber. The access priority for the primary user may be established in a network where the primary user is a public safety user. During an emergency, the host network may hang up secondary users due to increased use of its spectrum by other users, such as public safety primary users.

Fig. 17 shows a communication system 1700 of a DSA communication system for allocating resources, according to one embodiment. As shown in fig. 17, in the virtual best effort approach, wireless device 101 may be considered as a valid rover.

During bidding, the DSA communication system may implement a set of rules that may be used to define the type of service, treatment, and duration of service for wireless devices authorized to access the host network. The rule set may include information such as: 1) requested capacity/boundary; 2) the treatment of services, such as when they are required and QoS; 3) a geographic boundary based on the requested service; 4) the time at which the resource was requested; and 5) the duration of the requested resource to be used by the secondary user. It is contemplated that all or a subset of these rules may be used depending on the arbitration scheme.

In a virtual best effort approach, DSA communication systems may follow an industry roaming procedure, as access to the spectrum may be granted to secondary users provided that the wireless device requesting service satisfies the required authentication procedure. Authentication/authorization of the secondary consumer wireless device 101 may be performed through the use of the master HSS 926 and AAA following standard MAP/IS-41 procedures.

Additional criteria that DSA communication systems may add to the roaming process may include different billing schemes. For example, the host network may manage access duration or total usage permissions for the secondary user's wireless device 101. Such management schemes enable the host network to control access by secondary users locally and on a real-time basis. In the virtual best effort approach, DSA communication systems may not reserve resources and only track the consumption of resources.

In the virtual best effort approach, the primary or host network provider may not authorize secondary user prioritization except through the differences provided by the host network provider's PCRF905 and PDN Gateway (PGW) 908. To utilize the resources of DSA communication systems using a virtual best effort approach, the secondary user may use either the PGW908 of the host network or the PGW of the secondary network, which may be connected either to an appropriate Serving Gateway (SGW)922 of the host network or to the PGW of the host through an intermediate PGW908 managed by the host network.

The PGW is responsible for IP address allocation, as well as QoS enforcement and flow-based charging for the wireless device 101 according to rules from the PCRF. It is responsible for filtering downlink user IP packets into different QoS-based bearers. This is performed based on a Traffic Flow Template (TFT). The PGW performs QoS enforcement for Guaranteed Bit Rate (GBR) bearers. It can also be used as a non-3 GPP technology such as CDMA2000 andand (4) mobile anchor points of network interworking.

All user IP packets may be transported through the SGW, which acts as a local mobility anchor for data bearers as the wireless device moves between enodebs. The local mobility anchor for inter-eNodeB handovers include downlink packet buffering and initiation of network triggered service requests, lawful interception, user charging and QCI granularity, and UL/DL charging per wireless device. The SGW also retains information about the bearers when the wireless device is in an IDLE state (called "EPS connection management-IDLE" [ ECM-IDLE ]) and temporarily buffers downlink data when the Mobility Management Entity (MME) initiates paging of the wireless device to re-establish the bearers. In addition, the SGW performs some management functions in the visited network such as collecting information for billing (e.g., the amount of data sent to/received from the user) and lawful interception. It also acts as a mobility anchor for interworking with other 3GPP technologies such as General Packet Radio Service (GPRS) and UMTS.

The MME is a control node that handles signaling between the wireless device and the CN. The protocols running between the wireless device and the CN are called non-access stratum (NAS) protocols (eMM, eSM) and security, AS security, tracking area list management, PDN GW and S-GW selection, handover (intra and inter LTE), authentication, bearer management. The MME also contains mechanisms for avoiding and handling overload situations.

The eNodeB performs radio resource management functions such as radio bearer control, radio admission control, radio mobility control, scheduling of resources in both uplink and downlink, and dynamic allocation to wireless devices. The eNodeB may perform header compression, which refers to compressing IP packet headers that may otherwise represent significant overhead, especially for small packets like VoIP to help ensure efficient use of the radio interface. The eNodeB may perform security functions by ensuring that all data sent over the radio interface is encrypted.

In one embodiment, the virtual best effort approach may enable DSA communication systems to manage resource allocation by using different approaches. For example, PCRF905 of the host network may control wireless device 101 of the secondary user who accesses the host network and tracks usage of resources. The secondary user may be charged using a charging system of the host network.

Alternatively, the charging system of the host network may control/track resource usage by the secondary user and the secondary user's home network PCRF905 may provide the preferred service. In such scenarios, PCRF905 of the host network may retain final control.

Alternatively, the host network may provide access and the PCRF905 of the secondary user's home network may define the preferred services. Further, as part of the allocation process using the virtual best effort approach, wireless devices of secondary users roaming on the host network may be assigned different TAIs. These TAIs may provide differentiated service areas or defined geographic areas for potential use. In one embodiment, the subscriber wireless device may be allowed access to the home network through the identification of a valid PLMN that it has in the USIM, either preprogrammed or provided through OTA provisioning. For different reasons, the home network may instruct the subscriber to use the host network as a secondary user. Further, if wireless device 101 is capable of accessing both networks simultaneously, wireless device 101 may potentially use the home network for one type of service and may be instructed to use the host network for other services.

In one embodiment, the available resources may be allocated to secondary users using a virtual secondary user approach, such as within the system (i.e., within a frequency lessor (Intra freq-lessor) or within a frequency primary lessee (Intra freq prime-lessee)). In the virtual secondary user approach, the primary host network may allow secondary users of the secondary network to operate using the system spectrum resources of the primary network with different usage rights, such as temporary leases but with different SIDs, than the primary user. This may be accomplished by allowing the secondary user to include spectrum allocations from the primary host network when there is technology compatibility between the primary network system and the secondary user wireless device 101. This allocation can be applied to mobile virtual network operators that provide mobile telephony services but do not have their own licensed spectrum allocation of radio spectrum, nor the infrastructure required to provide mobile telephony services.

In the virtual secondary user approach, the prioritization of secondary users may follow PCRF905 and PGW908 rules of the host network. The PGW908 usable by the secondary user wireless device 101 may be either controlled by the host network or made available through the secondary user's home network. If the PGW908 is available through the secondary user's home network, it may either be connected to the appropriate SGW 922 or provided, for example, through an intermediate PGW908 managed by the host network. In such a scenario, the secondary user may be considered as an effective rover in a DSA communication system using the virtual secondary user method, as shown in fig. 17.

In the virtual secondary user approach, the DSA communication system may use five basic bidding rule sets that are used to define the type, treatment and duration of service for the secondary user wireless device 101. These rule sets may include information such as: 1) requested capacity/boundary; 2) the treatment of services, how often they are required and QoS; 3) a geographic boundary based on the requested service; 4) the time at which the resource was requested; and 5) the duration that the secondary user will use the requested resource, and other rule sets that may be applied. It is contemplated that all or a subset of these rules may be used depending on the arbitration scheme.

In one embodiment, when employing the virtual secondary user approach, the host network may grant access to the secondary user wireless device 101 if it meets a predetermined required authentication procedure. The host network using the virtual secondary user method may use a different billing scheme where wireless device 101 access or usage is managed entirely by the rules and specifications of the host network, allowing local control of the secondary user device 101. As a secondary user in the system, access to the host network by the wireless device 101 may be limited, reduced, or prohibited depending on the conditions of the host network. Restrictions, reductions, or prohibitions may be imposed on calls on a local or system-wide basis depending on the conditions set forth by the host network in the bidding system. The limiting, reducing or prohibiting may be further performed on a dynamic basis by overriding the bidding conditions (e.g., in a public safety network).

Authentication or verification of the secondary user wireless device user may be performed in compliance with the MAP/IS-41 standard. Using MAP/IS-41, the secondary user wireless device may be authenticated by the host HSS 926 and AAA.

In one embodiment, when using the virtual secondary user approach, DSA communication systems may require different components of the host network and/or home network to be used for resource allocation. For example, the host network charging system and PCRF905 may control secondary user access to the network and track its usage. Alternatively, the host network charging system may control and/or track usage and the secondary user's home network PCRF905 may provide preferred services and the network PCRF905 may perform final control. Alternatively, the host network may provide access in the home network, and PCRF905 may define the preferred services.

When the resources allocated using the virtual secondary user method are close to exhaustion, either based on time, usage, or other criteria, the DPC902 may notify the home network operator in the host network that the resources may expire. If allowed, the home network operator may be enabled to end or replenish resources available to secondary users or otherwise provide additional RF spectrum resources by requesting an outbound bid on additional resources at the host network. To provide additional flexibility to the resource allocation process, wireless devices of secondary users that are roaming the host network may be assigned different TAIs. TAIs may provide differentiated service areas or different geographic areas for potential use.

In one embodiment, the secondary user's wireless device may be able to access the home network by identifying a valid public land mobile network or PLMN that it may already store in its universal subscriber identity module ("USIM"). The USIM may be provisioned either pre-programmed or through OTA provisioning. When the home network is used, the secondary user's wireless device 101 may be re-instructed to search for a host network from which it may receive service. Once the host network is identified, the secondary consumer wireless device 101 can use the host network for all services, or for one type of service. Alternatively, the use of the home network may be used for other services if the wireless device 101 has the capability to access both networks simultaneously. Various configurations are possible and within the scope of the present disclosure.

Figure 18 illustrates a communication system block diagram 1800 that illustrates communication between components of two networks in a DSA communication system during resource reservation, according to one embodiment. In one embodiment, the configuration of the host network (i.e., the lessor) may be controlled by the OMC 912. Further, home network (i.e., tenant) 1802 can be separate from host network 1804.

In one embodiment, a host network using a virtual secondary user method may reserve resources by using different methods, including: 1) an X bifurcation of the eNodeB; 2) SGW and PGW link bandwidths; 3) combined resource allocation (PGW and eNodeB); and 4) PCRF (host) control. These resource reservation methods may be used in combination or may be mutually exclusive, depending on host network requirements and bidding procedures.

By x-forking the eNodeB, resources can be reserved for secondary users. In one exemplary embodiment, as shown in fig. 19, eNodeB 916b may be forked to reserve resources for secondary users. eNodeB 916b may receive forking instructions from PCRF905, MME914, and SGW 922 to divide the percentages if its resources are available for another PLMN network. PGW908 may be located at a host network or may be located remotely. According to the received instructions, the eNodeB 916b may reserve X% of the resources for use by the primary users and Y% of the resources for use by the secondary users. eNodeB 916b may transmit an enhanced PLMN (eplmn), which may be identifiable to secondary user wireless device 101b and camped on a cell.

In one embodiment, resources may also be reserved by controlling the connection between the SGW 922 and PGW908 to which the secondary user wireless device is assigned.

Fig. 20 shows an embodiment method for controlling the SGW 922 and PGW908 a, 908b link bandwidth allocation scheme, according to one embodiment. Resource reservation may be controlled by controlling the connection of the host SGW 922 to the various PGWs 908a, 908 b. The connection of the SGW 922 to the PGWs 908a, 908b may be controlled by altering the available bandwidth between the SGW 922 and the PGWs 908a, 908b on a dynamic basis. The PGWs 908a, 908b may be local and/or remote with respect to the host network. The SGW 922 and PGW908 link bandwidths may be altered by the OMC/NMS 912 connectable to the DSC 910. PGW908 a may be located on a host network or remotely.

In one embodiment, shown in fig. 21, resources may be reserved by combining eNodeB x forking and SGW-PGW link bandwidth control methods for allocation purposes.

In one embodiment, host PCRF905 may control resource reservations for allocations to secondary users. The host PCRF905 can prioritize the secondary user wireless devices 101 based on the requested service using a combination of QCI/ARQ, which can be an automatic repeat request. In this scenario, PCRF905 may assign QCI/ARQ to primary user wireless device 101a and secondary user wireless device 101 b.

In one embodiment, the resources may be made available for allocation using an RF spectrum allocation method. In spectrum allocation methods, such as inter-system (inter-frequency renters, inter-frequency primary tenants), a primary network may assign spectrum resources for use by secondary users in a geographic area. Based on this, secondary network providers may make primary network resources available as channels/spectrum for their own normally operating networks (i.e., may be compatible or IRAT). This can also be applied to MVNOs. Thus, secondary users can access primary network resources on their home networks without having to roam on the primary networks.

The spectrum allocation method may be based on a) a licensed region; or b) a local area. In the licensed zone and localized zone approach to spectrum allocation, the spectrum available for use by the primary network provider operator (i.e., the lessor or network 1) may be programmed through the OMC/NMS 912. The spectrum allocation method may enable the host network to allocate spectrum based on a desired bandwidth, a geographic boundary of the secondary user, a time at which the secondary user requests resources, and a duration of time at which the secondary user requests resources.

In one embodiment, the spectrum allocation method may make spectrum resources available to secondary users on a dynamic basis. The charging procedure for the spectrum allocation method may not involve the host or the visited network charging platform. Rather, DPC902 may coordinate the charging for this effort.

In contrast to the virtual best effort or virtual secondary user approach, the spectrum allocation approach may enable the home network operator (network 2) to use the allocated resources for the secondary user wireless devices 101 and not share the allocated resources with the primary host network. Thus, the secondary users may use the allocated spectrum resources during the lease. The secondary user home network may also be enabled to control the allocated resources by using their radio access network node 102 for the duration of the lease.

Fig. 23A and 23B show an embodiment for allocating spectrum resources to the licensed region 2300 using a spectrum allocation method. When allocating spectrum resources to the license zone 2300, the primary host network may allocate a defined amount of spectrum resources for use by the secondary user home network. Each network operator of the secondary home network may be authorized to use the allocated spectrum over a geographically defined licensed region. As shown in fig. 23A, the spectrum license block 2300 may belong to a particular license region 2300.

The licensed region spectrum allocation method may involve partitioning blocks of spectrum 2302 that may be used over the entire licensed region. The partitioning may be done in a variety of different channels, either through a shared channel or through other methods. As shown in fig. 23B, spectrum chunk 2302 can be divided to provide three channels 2304a, 2304B, 2304c for primary users and channel 2304d for lease.

Fig. 24 shows an embodiment for allocating spectrum resources to a local area using a spectrum allocation method. Local zone spectrum allocation may involve allocating spectrum within a defined license zone 2300 of the host network. The primary host network may assign certain defined geographic regions. These regions surround secondary users that may use the allocated spectrum resources. Thus, the geographical region designated for use of the allocated resources may be a sub-region of the entire licensed region 2300 in which the operator has access to the spectrum. The host network (i.e., the lessor) may rent, sell, select, or otherwise transfer resources to other secondary operators on a temporal basis for use in their geographically defined sub-regions. This may allow the primary host operators to reserve the use of other geographical areas for their primary users or for renting to other secondary networks.

A single resource allocation may be defined in the operator's license area 2300 for possible use. For example, channel (4)2302d may be granted by the DSA communication system to a successful secondary user bidder for region a 2402. The same channel 4 may also be licensed to another secondary user bidder for region B2404. Outside of regions a2402 and B2404, the primary network may use the full spectrum (channel 1 through channel 4) 2302. In regions a2402 and B2404, the primary network operator may only use channels (1-3)2302a, 2302B, 2302 c. In regions a2402 and B2404, the primary user may not use channel (4)2302d licensed to the secondary network provider. For example, bidders of a resource may be engaged in many different spectrum contractual relationships, including leasing, purchasing, selecting, trading, aggregating, or otherwise transferring spectrum.

Once the available resources are allocated, they can be accessed based on different methods. The spectrum access method may depend on the method of allocation used by the network that is providing the resource. Generally, spectrum access methods can be divided into roaming and non-roaming methods. When accessing resources based on a roaming method, the secondary user wireless device 101 may be required to use the available resources through roaming onto the primary network. When accessing resources based on a non-roaming method, the secondary user wireless device 101 may be allowed to use the allocated resources while still on its home network.

Fig. 25A and 25B present two network diagrams illustrating the use of resources of another network by wireless device 101 to allow access to the resources using roaming arrangements according to one embodiment. As shown in fig. 25A, wireless device 101 may currently use the spectrum of network 1. Network 1 may communicate services that may require additional spectrum resources to continue for wireless device 101 to DPC 902. DPC902 may also receive information from network 2 to wireless devices 101 from other networks that may have additional or excess spectrum resources that may be allocated for use.

As shown in fig. 25B, once the DPC902 confirms that network 2 has spectrum for allocation, the wireless device 101 may be instructed to handover the operator from network 1 to network 2 based on the service used, the time, and/or the geographic location.

In one embodiment, the secondary user network provider may grant or lease rights to use the spectrum resources allocated by the primary network. In this scenario, the secondary user equipment 101 may not be required to roam onto the primary network to use the allocated spectrum resources. The secondary user equipment 101 may still be on the secondary home network where resources of the primary network may be made available through the secondary network access point based on the licensing terms.

Fig. 26A and 26B show yet another spectrum allocation method using short-term leasing of resources according to one embodiment. The available spectrum may be leased to other networks on a licensed region basis, a sub-licensed region basis, or through individual nodes, cell sites by employing a DSA communication system. DSA communication systems may make such leased spectrum available for secondary use through other networks determined by following geographic and spatial boundaries. In one embodiment, the secondary user may access the allocated spectrum of the host network through its own secondary network and need not switch to the host network.

Fig. 26A shows a wireless device 101 communicating with a wireless access node 102a of network 1. Network 1 may have a lease agreement with network 2 to use a specified chunk of spectrum for network 2. In this scenario, when the spectrum resources of network 1 are exhausted and additional resources are required, network 1 may use the licensed secondary spectrum resources to communicate with subscriber wireless device 101. Fig. 26B shows a wireless device 101 communicating with network 1 using licensed secondary spectrum resources of network 2.

The leasing of spectrum resources may enhance the capacity of the network, as shown in fig. 27B of fig. 27A. As shown in fig. 27A, network provider a may serve wireless device 101 through different wireless access points 102a, 102b, 102c depending on the geographic location of wireless device 101. The wireless access points 102a, 102b, 102c may use spectrum resources from the network provider a to serve the wireless device 101.

Due to the increased traffic, network provider a may require additional spectrum resources to properly serve its subscribers. Network provider a may license or lease spectrum resources from network provider B to enhance and increase its available spectrum resources. As shown in fig. 27B, the spectrum capacity enhancement of provider a may be achieved by sharing a radio access platform with provider B. In such a scenario, wireless access points 102a, 102B, 102c may broadcast spectrum signals received from providers a and B.

Initial cell selection

A cell or origination may involve a situation where the wireless device 101 of one network is directed to another network in order to access additional resources available on the new network. Currently, the wireless device 101 is programmed to establish a connection with the correct network for receiving a service. To find the correct network, once the wireless device 101 is powered up, it may search for a preferred Public Land Mobile Network (PLMN), a Preferred Roaming List (PRL), and the radio operator that the device is authorized to use. The listing of PLMNs/PRLs and radio operators may be provisioned on the wireless device. The PLMN/PRL list may include PLMN identities of authorized networks and ranked operators.

Since DSA communication systems may provide dynamic and real-time access to spectrum resources, when DSA systems are used, spectrum resources may be available at networks not listed on the PLMN/PRL of the wireless device.

As part of the DSA communication system process, the wireless device 101 may be previously programmed with an appropriate PLMN list. Also, the wireless device 101 may also be provisioned wirelessly on the secondary home network. The wireless provisioning may provide instructions to one or a group of wireless devices 101 to re-initiate the cell selection process using the updated PLMN list.

Alternatively, the wireless device 101 may be configured with a client application that, upon receipt of a WAP/SMS message, may enable the wireless device 101 to search for PLMNs that are already available during DSA.

Several methods may be used to allow a wireless device to access available resources on different networks. In DSA communication systems, there are at least two types of network or source systems: virtual networks or existing networks. The virtual network may comprise a network of Radio Access Networks (RANs) that utilize a primary network. Regulatory features and requirements for emergency calls (e.g., 911 calls) and other regulatory regulations may need to be addressed when the wireless device 101 is required to access a virtual network.

When connected to the virtual network, the DPC902 of the primary network may control access of the secondary user wireless device 101 and access RF spectrum resources and subscriber records of the primary system to allow the secondary user to appear as a roamer on the primary network. The secondary user wireless device 101 may use the list of preferred networks to access the virtual network.

Alternatively, when originating calls using an existing network, the secondary user wireless device 101 may make cell selection based on a priority list of networks participating in the DSA communication system. Once the secondary user wireless device 101 is authenticated, the DPC902 of the primary host network may authenticate the secondary user to access resources on the primary network. If the authentication or verification is unsuccessful, the DPC902 of the primary user may send a request to the secondary wireless device 101 via the client in the device to recall on the appropriate system.

The wireless device 101 may include a universal subscriber identity module or USIM. The USIM may be a single or dual USIM. Critical information (e.g., data) needed to select the correct network may be stored on the USIM. By using the USIM, the wireless device 101 can be made to no longer use the PLMN. The USIM may store information thereon such as the home international mobile subscriber identity or imsi (hplmn), a prioritized list of allowed VPLMNs, and a forbidden PLMN list.

If the wireless device 101 uses a dual USIM, it may be enabled to immediately access spectrum resources available in the alternative network. The dual USIM may further enable the multi-band, multi-mode wireless device 101 to access various networks in the DSA and use standard roaming arrangements.

Fig. 28 shows an embodiment method 2800 for network and cell initialization in a DSA communication system by wireless device 101. Initial network and cell selection may begin with the wireless device 101 when the wireless device either powers up or attempts to reestablish a connection (block 2802). The wireless device 101 may initially search the PLMN/PRL list stored on the device (block 2804) and select a cell by receiving, reading, and determining the strength of the nearby cell site broadcast channel (block 2806).

Wireless device 101 may read the cell site broadcast channel and determine whether the cell site provides the correct system (decision 2808). Wireless device 101 may select and establish a connection to the best available cell site. To identify the best available cell site, the wireless device 101 may measure neighboring cells based on the access technology to determine which cell is best utilized.

If a suitable cell is not initially available (i.e., determination 2808 — no), wireless device 101 may continue to search for a suitable cell site using any cell selection procedure/phase and by selecting the next PLMN/PRL list element until it finds a site that allows normal access following the access protocol in the appropriate PLMN list (block 2810).

If the correct system is available in the selected cell site (i.e., determination 2808 — yes), wireless device 101 may receive and read a System Information Block (SIB)/Master Information Block (MIB) transmitted by the selected cell site (block 2812). The SIB/MIB may include information about the network that the cell site is serving and the services available through that network.

In one embodiment, the SIB/MIB may include a lot of information such as PLMN ID, cell ID, Traffic Allocation Identifier (TAI) (routing area), LTE neighbor list, LTE non-system site, GSM cgell, UMTS cell, and CDMA cell. Wireless device 101 may use this information for different purposes. For example, when the wireless device 101 moves from eNodeB to eNodeB, it may use SIB/MIB information sent from the new eNodeB to determine that a change has occurred in the serving eNodeB. To detect a change in eNodeB, the wireless device 101 may identify a change in SIB/MIB information, which may include changes in PLMN availability and TAI parameters. The TAI definition may further serve to define a particular geographic region of the geographic area in which the wireless device 101 may use the available resources.

The SIB/MIB may be transmitted to the cell site through the network. The cell site may receive network information through the HSS 926 of the network. In addition to data communicated through the SIBs, the HSS 926 of the network may also provide information about which PGW(s) 908 the wireless device 101 may use to access resources on the network.

When reading the SIB/MIB, wireless device 101 may determine whether reselection is required at determination block 2814. If reselection is not required (i.e., it is determined at block 2814 to yes), wireless device 101 may camp on a cell channel at block 2816. If system reselection is required (i.e., determination block 2814 no), wireless device 101 may be instructed to reselect a new cell or system based on a cell selection/reselection procedure (block 2818).

The wireless device 101 may wirelessly receive additional information and instructions from a selected network, such as an updated list of public land mobile networks or PLMNs/PRLs, while camped on a selected cell site. Wireless device 101 may also continue to monitor the SIB/MIB for any changes or additional information.

In one embodiment, the SIB/MIB may provide a secondary access level that may enable the wireless device 101 to determine which channels it may use for access through a reselection procedure based on DSA procedures. The SIB/MIB may also include data that enables the camped wireless device 101 to reselect to another radio access technology (IRAT) and attempt to acquire a control channel on a new Radio Access Terminal (RAT). The information in the SIB/MIB may thus be used to instruct the wireless device 101 to reselect to another RAT associated with the same or another network, which may be on another frequency band.

Cell reselection, which may trigger PLMN selection, may be controlled via certain parameters. For example, DSA communication systems may employ forbidden PLMN-ids to prevent wireless device 101 from attempting to roam onto other networks using resources from one network. For example, the DSA communication system may prevent the secondary user wireless device 101 from using the resources of the primary host network to roam back to or establish a connection with the secondary home network. Similarly, DSA communication systems that use Over The Air (OTA), client activated, or dual USIM driven PLMN id prioritization schemes may also prevent the wireless device 101 from using the resources of the network to reestablish connections with other networks unless DSA communication system rules permit.

In one embodiment, a wireless device 101 camped on a cell site may be instructed to perform cell reselection when the capacity of the current cell reaches a predetermined level. In such a scenario, DSC910 using the currently camped-on network of OMC912 may change the SIB/MIB of the current network to include instructing the camped-on wireless device 101 to perform cell reselection and search for another TAI area or system. The instructions to perform cell reselection may also be forwarded to the wireless device 101 by a WAP/SMS message.

Fig. 29 shows an embodiment network diagram for cell reselection using a change in TAI. When using a network, different wireless devices 101 may be assigned different TAIs depending on their particular use and device type. For example, the network may assign one TAI to multiple DSA communication system users. The network may also assign another TAI to multiple devices that do not use the DSA communication system. The advantage of using multiple and tiered TAIs may enable a network that assigns TAIs to selectively customize usage traffic. Multiple and hierarchical TAIs may further enable the network assigned the TAI to block wireless devices 101 that may have the correct PLMN-id but should not use the selected region from selecting a cell but may be denied service or may be forced into cell reselection.

In one embodiment, a special client may be installed on the DSA communication system compatible wireless device 101 to enable the wireless device 101 to determine which system and RAT should be used on a secondary basis. The PLMN/PRL list of the client application may be updated by receiving a WAP or SMS transmitted to the handset via a text message or over a data (IP) session. The updated client application may instruct the wireless device 101 to the appropriate channel for accessing the allocated resources of the primary network.

The use of client applications may facilitate implementation of a DSA communication system in legacy networks and systems that may or may not possess the capability of having secondary access channels defined in SIBs (e.g., due to software loading).

In idle mode, the wireless device 101 may be instructed to perform intra-frequency and inter-frequency measurements during cell reselection. Using information in the SIB/MIB or from the client application, the wireless device 101 may perform intra-frequency search, inter-frequency or inter-radio access technology (iRAT). This process may be controlled by the UTRAN. The intra-frequency and inter-frequency measurement or inter-radio access techniques may be on a region or cell/sector basis, depending on the configuration of the wireless device 101.

Authentication of secondary user wireless devices:

the wireless device 101 may need authentication of the system it is camped on once it has selected the appropriate cell site and before it enters idle mode. The selected network requires verification and authentication of the wireless device 101 to ensure that the device possesses the required permissions to access the network.

The DSA communication system may authenticate the wireless device 101 using different methods. Authenticating wireless devices with DSA may depend on business arrangements between different providers and DSA systems. For example, authentication may be based on a general or prioritization level. The authentication procedure may be followed using the DPC902HSS 904 as an anchor and may be accessed through the AAA/AuC of the PCRF 9043G/2.5G network in LTE or similar platforms. The host network may authenticate the secondary user by using standard MAP/IS-41 signaling.

Once authenticated, each entrant may be assigned: (a) a defined usage level allowed on the host network; a duration of the license on the system; purchase type (e.g., range of sales or IMI); the HSS will allow redirection of incoming calls; applications will continue when they rely on servers accessible from the backend.

Monitoring and tracking of allocated resources:

DSA communication systems may ensure that a primary network provider always has sufficient resources to manage traffic on the primary provider network (e.g., network 2). Thus, depending on the traffic, DSA communication systems may dynamically alter the spectrum/capacity available to secondary users on a real-time and/or statistical basis.

For example, during peak hours, call traffic may increase in the primary network. As call traffic increases in the primary network, DSA communication systems may reduce the amount of spectrum available for allocation to secondary users to ensure that primary users have sufficient resources.

DSA communication systems may manage allocation and access to resources based on different factors including priority levels of users, time of using spectrum, and geographic location of users. In one embodiment, when secondary access to the primary network involves certain events, such as a disaster, an emergency, a first responder, or public safety, the DSA communication system may manage secondary usage of the primary system by using different prioritization. For example, when the secondary user is the first responder to use primary network resources, the DSA communication system may maintain or increase the resources allocated by the primary network provider to the secondary user to allow the emergency call to be successfully completed even if the primary network user is compromised.

In one embodiment, the use of spectrum resources of one network by secondary users may be managed and controlled by different components of the DSA communication system, such as the DPC 902. For example, the DPC902 of the primary network may monitor usage of the allocated spectrum resources to ensure that appropriate steps are taken when the allocated resources are exhausted or no longer available for secondary usage.

The DSC910 of the primary network on which the wireless device 101 may operate as a secondary user may be configured to monitor or receive data regarding the traffic class associated with the primary network. If the primary network capacity threshold is reached, the DSC910 may be configured to offload secondary users by downgrading resources, forcibly terminating (i.e., offloading) the secondary user's connection, or redirecting the secondary user to another operator or channel set.

The DSC910 of the primary network may also inform the DPC902 when offloading of secondary users may be required. For example, an undesirable surge in primary callers may cause DSC910 to request forking of secondary users to make resources available to the primary user. The technology access parameters may be sent to the (OTA) wireless device 101 when the offloading of the secondary user is initiated. Alternatively, the system may dynamically assign resources via LTE using an X2 link that instructs the defined wireless device 101 to switch to the new LTE network.

Offloading of the secondary user may include redirecting the secondary user's connection back to the secondary user's own network, to another provider network or channel, or disconnecting the secondary user from the primary provider network. For example, when the primary host network terminates the secondary user due to increased demand requirements on the primary network, the DPC may be configured to determine whether other networks are available to redirect the secondary user's connection rather than terminate. The DPC902 may query the DSCs 910 for resources from other networks. If the resource is available for use in other networks, DPC902 may use a rule set to determine the most cost-effective connection to another host network that satisfies the resource request requirements. Once DPC902 has identified another host network to which secondary user wireless device 101 may be redirected, DPC902 may instruct wireless device 101 to transition to the new host network for the communication session. The process of offloading of secondary users may include a handover or backoff process as explained in more detail below.

In yet another exemplary embodiment, the DPC902 of the host network may be further configured to instruct the primary host network to release the secondary user wireless device 101 back to the secondary home network after the host network resources are exhausted. DPC902 may be further configured to force termination of the secondary user's connection to the primary network if DPC902 determines that additional capacity is needed for use by the primary user.

If sufficient capacity is available, the DPC902 may force the secondary user to continue using the resources of the primary host network until the traffic on the primary host network requires additional actions based on the rule set.

In various embodiments, DSA may further manage the use of allocated and accessed spectrum. For example, DSA communication systems may manage the use of the RF spectrum of a host network by employing a back-off mechanism. When a high priority user accesses the host spectrum network, the spectrum may shed lower priority users to make the spectrum available to higher priority users.

Fig. 30 shows a network architecture diagram 3000 for monitoring and tracking of spectrum usage according to one embodiment. Tracking and monitoring of the use of spectrum resources may be performed using different methods. In a DSA communication system using a virtual best effort method of resource allocation, the DSC910 may monitor the usage of spectrum resources based on pre-arranged billing information and communication with a primary network billing platform.

The DSC910 may monitor the usage level for the group and also track the usage level with the PGW 908. Usage may be compared to anticipated or reasonably successful bids and monitored. Once the secondary user uses a predefined amount of allocated resources, the DSC910 of the primary network may be configured to generate and send a notification that the resources are approaching a very low tier to the secondary network provider through the DPC 902. The secondary user may receive this notification through its own DSC 910. Once the notification is received, the secondary user provider network may re-bid for additional resources or simply let the remaining resources exhausted.

In the case where the secondary user is actively using the primary network when the allocated resources are fully consumed, the primary network may instruct the secondary user wireless device 101 to reconnect to the home network (secondary user network provider), terminate the connection of the wireless device, or charge the secondary network for goods excess or replenishment based on a previously negotiated contract. Once the connection is terminated, the secondary user wireless device may no longer be able to access the primary network resources unless additional resources are allocated for the secondary user.

In a DSA communication system using a virtual secondary user method, the DSC910 may monitor usage of allocated resources and communication with a host primary network billing platform based on pre-arranged billing information. The process of monitoring usage of allocated resources based on a virtual secondary user approach may involve directing usage levels for the group and also tracking the usage levels along with the PGW 908.

Similar to DSA communication systems using the virtual best effort approach, DSA communication systems using the virtual secondary user approach may monitor usage by comparing usage with the amount of resources allocated to the secondary user network provider. Once the secondary user has used a predefined amount of the allocated resources, the DSC910 of the primary network may be configured to generate and send a notification through the DPC902 that the resources are approaching a very low level to the secondary network provider. The secondary user may receive this notification through its own DSC 910. Once the notification is received, the secondary user provider network may re-bid for additional resources or simply let the remaining resources exhausted.

In DSA communication systems using a virtual secondary user method, the secondary users may be terminated by a different method after the allocated resources are exhausted, such as by 1) non-prioritized back-off as discussed below; or 2) prioritized backoff.

In the non-prioritized back-off method, when a predetermined level of allocated spectrum resources is consumed, no further use is allowed. Once the allocated spectrum resources are exhausted, the primary network DSC910 may instruct the secondary user wireless device to connect to the secondary user home network, terminate the secondary user wireless device's connection with the primary network, or charge a commodity surcharge based on a previously negotiated contract. Once terminated from the primary network, the secondary user wireless device may no longer be able to access the primary network resources unless the secondary home network provider obtains additional resources.

In a prioritized back-off method, when the allocated spectrum resources are at a very low level and before the resources are completely exhausted, the primary network may begin a back-off process during which the primary network may dial the secondary user wireless device 101 on another suitable network. If not, other suitable networks are available to accept the secondary user wireless device 101, the primary network may switch the secondary user wireless device 101 back to the secondary user home network. The primary network may balance any allocated resources not used by the secondary user to the secondary network.

When using the resource allocation method, the primary host network may monitor the allocated resources differently depending on whether the resources are allocated based on the licensed region or the local region method.

If the allocation of resources is performed based on the licensed region approach, the primary network may monitor the use of resources by the secondary users. When the allocated resources are nearly exhausted, the DSC 910/DPC902 may notify the secondary user that the temporary lease of network resources is about to expire and provide the secondary network with an opportunity to bid and purchase additional resources.

If the secondary network fails or refuses to obtain additional resources, the primary network may use a different method to terminate or backoff the secondary user from the primary network, e.g., 1) no prioritized backoff; or 2) a prioritization method.

In the non-prioritized back-off method, when the lease of the resource expires, the spectrum resource may no longer be available to the secondary user. The primary network may instruct the secondary user wireless devices 101 to either switch to another radio access system in their network or terminate their use.

In a prioritized back-off method, the DSC 910/DPC902 of the primary network may coordinate resources with the DSC910 of the secondary network regarding the affected stations. The secondary network may attempt to handover the secondary user wireless network to another network, base station, radio access channel, or system for the affected area. The primary network may balance the unused allocated resources to the secondary network.

If the allocation of resources is performed based on a local area method, the primary network may monitor the use of resources by the secondary users. When the allocated resources are about to expire and approach a predetermined level of exhaustion, the DSC 910/DPC902 of the primary host network may notify the secondary home network to block the termination of the resources. The primary network may provide the secondary network with an opportunity to re-bid for additional resources.

If the secondary network fails or refuses to acquire additional resources, the primary network may use a different method to terminate or backoff the secondary user from the primary network, e.g., 1) no prioritized backoff; or 2) a prioritization method.

In the non-prioritized back-off method, when the lease period of the allocated resources expires, the secondary user may no longer be able to access the spectrum resources of the primary network. The primary network may either hand off the secondary user to another radio access system in their network, which may be the host network or another network, or terminate the secondary user's access to the primary network resources.

In the prioritized back-off method, the DSC910 and DPC902 of the primary network and the DSC910 of the secondary network may coordinate resources with affected stations and start a back-off process before the lease of the allocated resources expires. The secondary network may attempt to handover the secondary user wireless network to another network, base station, radio access channel, or system for the affected area. The primary network may balance the unused allocated resources to the secondary network.

Handover of secondary users during offloading:

in one embodiment, the DSA communication system may employ a handoff method to prevent interruption or maintenance of a communication session between the wireless device 101, the DSA communication system, and/or the network provider during the communication session. For example, the communication session may include wireless device 101 establishing a connection with a network. The handoff may occur when the wireless device 101 migrates from the home network to the host network and back to the home network during a period of a communication session. The network-generated SIB/MIB may include a list of cells and networks that may be used to switch communication sessions.

Outside of the DSA communication system, mobile-assisted handover may involve the wireless device 101 informing the serving network that a better server is available and changing the connection from the current server to the better server. Such mobile-assisted handovers may be performed while the wireless device is roaming on the host network. However, DSA communication systems may not allow such mobile-assisted handovers because the best server for roaming purposes may not be the best cell for capacity mitigation. The communication session with the DSA communication system may involve circuit switched or packet switched services.

FIG. 31 shows a network component diagram of one embodiment network capable of performing a handoff of a communication session. To effect handoff of the communication session, some connectivity between components of the host network and the home network (e.g., network a and network B) may exist. For example, the PGW908 of the host may be connected to the home network. The host's PGW908 and home network may communicate over the internet or a private data network. The host's PGW908 may also be connected to the home network's SGW 922. The host's ANDSF 918 and home network may also be connected to allow handover to legacy systems and to invoke the backoff procedure when the wireless device is required to migrate from the host to the home network.

An Access Network Discovery and Selection Function (ANDSF) is used to manage inter-system mobility policies and store access network discovery information in wireless devices that support the provision of such information from the ANDSF. ANDSF may initiate the provision of information from ANDSF to wireless devices as specified in 3GPP TS 24.302[3AA ].

Fig. 32 shows a network diagram of an embodiment method for media independent handover. ANDSF throughout the DSA procedure may initiate the handover by sending an SMS/WAP message to the wireless device 101 that instructs it to make a gap or non-gap handover. The handover procedure may be initiated in different circumstances and for different reasons. For example, the network may start the handover procedure based on contract specifications between the host network and the home network, based on the level of resources at the host network and whether the resources have reached a predetermined threshold, based on the exhaustion of resources leased by the home network, or based on whether a back-off procedure is initiated.

When host resources are no longer available to use or initiate a backoff procedure, the DSA communication system may take additional components or schemes to switch communication sessions. In this scenario, the eNodeB of the host network may perform the backoff procedure based on the QCI and ARP designations. eNodeB 916 backoff may involve handing off the current communication session from host eNodeB 916b to another eNodeB through the use of an X2 link between switching networks. This process may also be implemented by using the DSMPTA process with ANDSF.

To initiate and implement the handoff process, the host network may generate and send certain commands to the wireless device 101. For example, three different types of handovers include: 1) inter-frequency; 2) intra-frequency; and 3) IRAT.

In an inter-frequency handover, the network currently serving wireless device 101 (i.e., the current network) may initiate a handover of wireless device 101 from the current network to another network. In intra-frequency handover, the current network may initiate 101 handover of a wireless device from one cell in one network to another cell in the same network for capability offload. In IRAT handover, the current network may initiate handover of the wireless device 101 to another RAT.

An inter-frequency handover may be initiated when the current network sends an instruction to the secondary user wireless device 101 to begin using resources of another network. For example, wireless device 101 on the home network may be instructed to use the host network for uploading/downloading of larger files.

Inter-frequency handovers may be used to offload secondary users from the host network based on policy decisions that are in place. The inter-frequency handoff may further be used when the wireless device 101 no longer needs to use the services of the host network as a secondary user and can therefore be sent back to its home network. Inter-frequency handover may further be used when the wireless device 101 leaves the DSA communication system cluster or cell range and requires to continue its communication session. In such scenarios, the wireless device 101 may either be transferred to another network/cluster or sent back to the home network. Inter-frequency handovers may further be used to alleviate network capacity constraints by allowing some primary users to use the services of another network as secondary users.

Intra-frequency handovers may be used in current networks to alleviate cell congestion caused by shedding traffic from one cell to another. To avoid ping-pong effects that may prevent the capacity problem from being resolved, the intra-frequency handover command may prohibit the wireless device 101 from using neighboring cells/sectors that appear on the PLMN/PRL list for a defined period of time.

IRAT may be used to redirect the wireless device 101 to another RAT. During a handover from one IRAT to another, both the radio access technology and the frequency of operation may change. This type of handover may be used when a DSA communication system is available and the wireless device 101 is first active on a particular channel. The current network may instruct the wireless device 101 to change to another RAT through an IRAT handover procedure. In one embodiment, the handover command may be initiated from the current network, or alternatively may be initiated from a different network or entity. Thus, if the wireless device 101 communication session is hung up during the handover procedure, the wireless device 101 may be able to reestablish the communication session with the target RAT and not return to the previous network.

In one non-limiting embodiment, the session may be hung up during the INTERFREQ and/or INTRAFREQ handovers. In this embodiment, the device may reestablish the connection by returning to the previous network.

Figure 33 illustrates a network component diagram of one embodiment system required to initiate a network handover as part of a DSA procedure. The handover process may be initiated by the DSC910 based on its rule set established prior to bidding or during the bidding process. For maximum flexibility, the use of ANDSF 918 may enable intra-frequency, inter-frequency, and IRAT handovers to occur.

Backoff of secondary user from host network:

DPC902 may continuously monitor host network resources to ensure that a sufficient level of resources are available for use by primary users of the host network. When the capacity of the available resources at the host network approaches a predetermined threshold, the host network may instruct the wireless device 101 to begin a backoff process for the secondary user. A backoff procedure may be initiated to release resources at the host network.

When resources need to be made available to a primary user or subscriber of the network, the DSA may initiate backoff of secondary users to release the additional resources. The backoff procedure may involve different or combined methods depending on the DSA configuration. However, the commonality of the backoff policy is implemented using the wireless device 101 type and any special flags associated with the device, policy decisions for redirecting active and idle traffic, policy decisions of who to drop traffic to and in order, and re-provisioning or OTA or via an active client application.

In one embodiment, the DSA communication system may be configured to employ a hierarchical priority access (TPA) rule when initiating the backoff procedure (as described in detail above with reference to fig. 1-8). For example, the backoff procedure may be initiated when the resource level reaches a predetermined threshold level, which may be user defined. The threshold detection process may include traffic monitoring of Radio Access Network (RAN) and core network resources and determining whether a predetermined threshold level is reached that may trigger QoS or require dropping of secondary users to release resources.

The threshold level for RAN and core network resources may be determined based on traffic usage that may be generated by the secondary user. For example, when more than 85% of the RAN resources are used, a back-off procedure may be implemented to either reduce the throughput of the secondary user or drop the secondary user from the host network, or both. By initiating the backoff procedure, the host network ensures that the amount of available RAN or core network resources always remains above 15%.

In one embodiment, the backoff procedure that may allow the host network to maintain DSA where some amount of resources are always free may be proactive and independent of actual events. In the event of an event, such as a natural disaster, DSA communication systems may have the capacity to make free resources available to first responders and employ TPA procedures if additional resources are necessary.

In one embodiment, during the backoff procedure, the DSA communication system may monitor traffic and begin releasing RAN resources for secondary usage at user-defined intervals.

In one embodiment, each host network may employ certain backoff policies and resource criteria to decide whether to initiate a backoff process. These policy and resource criteria may include: spectrum availability (either separate or co-existing); capacity/bandwidth availability (RF and core); overhead criteria (total available capacity vs. percentage of capacity used); back-off conditions (reselection, handover-intra-system and inter-system) termination); treatment (how to treat/route a particular service/application); treatment is prohibited (e.g., use of services/applications is prohibited); rating (e.g., how to rate the service, i.e., special discounts possible for off-peak use); geographic boundaries (e.g., defining an area or cell to be encompassed); time (e.g., defining the time and date to include); duration (e.g., defining delta allocations based on time and geographic boundaries); the user equipment type.

The backoff procedure may be implemented differently for different resource allocation methods. In one embodiment, the PCRF905 policy rule set forth in the (EPC) may manage the back-off procedure for the virtual best effort (pure roaming) allocation method. The eNodeB may also be configured to initiate actions to reduce traffic by using the X2 link based on capacity loading. In this scenario, the eNodeB may enable the host network to shed secondary users by handing off traffic to neighboring cell sites. In one embodiment, the eNodeB may send instructions to one or more entities including the UE. In another embodiment, the eNodeB may initiate the procedure.

Furthermore, the backoff procedure for DSA may also involve one or more items that will be managed or enacted by the DSC following an agreed policy-based rule set and intended to guarantee session continuity or reassign the UE to another access method, in an attempt to guarantee user experience during the backoff procedure.

In one embodiment, the backoff procedure for virtual best effort (DSMPTA) may exceed and override typical rule sets that are part of the access and EPC. When the traffic reaches a predefined threshold, the DSA communication system may initiate a procedure or a combination of procedures to implement the DSMPTA backoff procedure. The PCRF905 can dynamically adjust the QCI/ARQ values for the secondary user wireless device 101. This may involve limiting bandwidth or placing usage to best effort or lower priority schemes. Cells experiencing capacity constraints may be placed on the forbidden cell list so that no additional secondary users may access the cells. Updates to the forbidden cell list can be communicated to the wireless device 101 by re-provisioning the broadcast message sent to the wireless device 101. The broadcast message may be updated with information about the barred cell and neighboring available cells.

To ensure that wireless devices 101 receive and read broadcast messages for barred cells and available neighbor cells, DSA communication systems may send WAP/SMS messages to configured wireless devices 101 to force their reselection. The wireless device 101 will have to read the broadcast message when they enter the reselection process.

In one embodiment, the DSA may initiate a closed service group to limit the use of a particular cell site to roaming wireless devices 101. The combination of CSG and TAI, which may involve capacity issues, may restrict access to the network by the secondary user wireless device 101. For example, CSG and TAI may hang up callers, degrade quality, expand networks, or provide other items that may handle capacity issues.

In one embodiment, during the backoff session, ANDSF 918 may facilitate the handover of the secondary user to another network or back to the secondary user home network. ADDSF 918 can initiate a network switch if a connection with another network is available. The wireless device 101 may be handed off to another network or another access network (RAT/IRAT).

In one embodiment, the PCRF905 policy rule set forth in the EPC and DPC902 may manage backoff procedures in DSA using a virtual secondary user method of resource allocation. The PCRF905 policy rules applied to the primary host network of the secondary user may take priority over those enforced by the DPC 902. However, the PCRF905 policy rules for the primary host network may be dynamically changed or modified based on the conditions set forth by the primary host network operational requirements. Alternatively, the back-off procedure in DSA communication systems may involve additional items. Implementation of these additional items may be controlled and managed by the DSC910 of the primary host network based on agreed policies and rule sets. DSC910 policies and rules are designed to ensure communication session continuity and good user experience during the backoff process.

In the event that existing policies and rule sets in the access EPC fail to apply to the backoff procedure, a DSA backoff procedure for the secondary user may be implemented. For example, when primary host network traffic reaches a predetermined threshold level, the host DSC910 may instruct the host eNodeB to use the X2 link and handover the secondary user to a neighboring cell site within the host network based on the secondary user wireless device 101QCI/ARQ rule set. Alternatively, when the host network and home network are connected for full mobility, the DSC910 may instruct the host eNodeB to handover the secondary user to the home network using the X2 link.

Based on instructions received from the host DSC910, the host PCRF905 may dynamically adjust QCI/ARQ values for the secondary user wireless device 101. For example, host PCRF905 may limit bandwidth, change resource allocation methods to virtual best effort, or change priority scheme to low priority.

The DSC910 may instruct the host network to update or generate a forbidden cell list and include cells that are currently experiencing traffic capacity that exceeds a predetermined traffic capacity threshold. The DSC910 may further instruct the host network to broadcast a message to re-provision the secondary user wireless device 101 with the updated forbidden cell list. The broadcast message may further include information about cells of a next ring or rings adjacent to the restricted cell or group of cells. The broadcast message may include the changed and valid PLMN-id, the changed TAI for one or more cells, and the changed neighbor list for use by the secondary user wireless device 101 to perform a handover procedure or network reselection. To ensure that the secondary user wireless device 101 checks for a re-provision broadcast message, the host network may send a WAP/SMS message to the configured wireless devices 101 to force them to perform a network reselection.

The host DSC910 may further instruct the host network to initiate a closed service group (CGS) to restrict the use of a particular cell site for a roaming secondary consumer wireless device 101. The combination of CGS and TAI, which relates to network capacity, may limit access of the roaming secondary consumer wireless device 101 to the host network. Access restrictions achieved by the combination of CGS and TAI may allow the host network to access only specified primary users.

In the event that there is a connection between the primary host network and another network (e.g., a secondary home network), the host DSC910 may instruct the host ANDSF 918 to initiate a network handover of the secondary user wireless device 101 to another connected network or access network (RAT/IRAT).

To reduce capacity overload when the eNodeB is x-forked for resource allocation and access, the host OMC912 (or other policy-based control configured to manage capacity) can instruct the eNodeB to shed resources accessible to the secondary user wireless device 101. Accordingly, resources designated for secondary users and associated with enodebs for affected zones may be reduced. Reducing the available resources of the eNodeB may be to force a handover or reselection to a neighboring cell with resources.

The host network initiated handover may balance the reallocation of eNodeB resources in order to force the secondary user wireless devices 101 to handover to another network where they may roam and be provided with sufficient resources. For example, the handover may be an inter-frequency RAT or IRAT handover.

The host PGW908 may also be used as part of the backoff process. The SG of secondary user wireless device 101 may be connected to the appropriate host PGW908 based on the policies and rules of host HSS904 and PCRF 905. The host DSC910 may control the bandwidth of the connection between the host PGW908 and the 101SG of the wireless device. During the back-off process, the host DSC910 may initiate the host network to reduce the bandwidth between the PGW908 and the SG of the secondary user wireless device 101 moved out of the host network. Predetermined policies and rules may govern the process by which the DSC910 may reduce the bandwidth between the PGW908 and the SG. The host DSC910 may continue to monitor host network cells that may be overburdened by high traffic and evaluate additional bandwidth reduction to the host PGW908 device SG connection to reduce traffic.

Not all procedures initiated by the DSC910 as part of the DSMPT backoff procedure are necessary and the implementation of these procedures and the order in which they may occur may depend on the agreement between the host and the home network.

In one embodiment, the backoff procedure may be implemented in a DSA communication system using a spectrum allocation method of resource allocation. The spectrum allocation method may include a licensed region and a local region method for resource allocation.

In one embodiment, the back-off procedure for DSA using the licensed region method may involve reallocation of spectrum resources from a secondary home network (i.e., tenant) to a primary hosting network (i.e., tenant). The host network using the licensed region approach may initiate a back-off procedure to switch all existing secondary user devices 101 from the lessor's spectrum to another network or back to the home network. The time frame for reallocation will be predetermined based on the rule set defined by the lessor and lessee agreement. Depending on the time frame defined in the rule set, it may not be possible to migrate all secondary users out of the host network in time, and as a result, some secondary users may hang up.

Based on pre-negotiated agreements between the lessor and lessee, the host network can determine whether to apply a backoff procedure to a portion or the entire licensed region. Spectrum reallocation may not be required for each cell of the entire licensed region based on the geographic area involved for capacity mitigation. Thus, the back-off procedure may be implemented in a sub-grant zone of the grant zone.

Upon implementing the back-off procedure for the entire licensed region, the host DSC910 may notify the DPC902 that the host network has reached a predetermined threshold of traffic capacity. The DPC902 may communicate the message to the home DSC 910. Home DSC910 may reduce the host resources available to the home eNodeB and switch secondary user traffic to the non-leased spectrum in a stepwise manner. The step of reducing the resources available to the eNodeB may be performed on a predetermined time interval basis. If traffic is not migrated in time, the home DPC902 may initiate a network switch to migrate the secondary user from the host network to another appropriate channel. Once the resources are released, the home eNodeB may remove the channel from its list of available channels.

When implementing the backoff procedure for the sub-licensed region (relative to the entire licensed region), the above procedure can be implemented except that the entire licensed region can be replaced with a defined cell or TAI.

Once the primary network has resolved the capacity restriction, the spectrum may be reallocated to the home network. To reallocate resources, the host DSC910 may notify the DPC902 that the spectrum resources are again available for use by the home network. The home DPC902 may notify the home DSC910 that resources are again available. Resources may be reallocated to the home network based on predetermined policies and rule sets.

For backoff procedures that are not managed by rules and policies in the access and EPC, the host may initiate a DSMPTA backoff procedure. This may be possible based on a set of rules.

In one embodiment, the back-off procedure for DSA communication systems using the local zone method may depend on policies and rule sets agreed upon by lessors and tenants.

The backoff procedure in DSA using the local region method of resource allocation may include switching all existing secondary user wireless equipment 101 using the host spectrum in the local region or sub-local region back to the home network or another network. The host DSC910 and DPC 902/DSC 910 rule sets may define whether the secondary user should be moved out of the entire or a subset of the local zone.

The time frame for reallocation of resources during the backoff process may be predetermined based on policies and rule sets agreed upon by the lessors and lessees. If the timeline set forth in the agreement is not met, it may not be possible to successfully migrate all traffic to the home network or another network during the back-off procedure. In this scenario, some connections may be hung up or lost as soon as a predetermined time frame expires.

When initiating the backoff procedure, tenant network resources associated with the home eNodeB may be reduced in a stepwise manner. The home OMC912 may initiate resource reduction by the eNodeB. Other policy-based components of the home network, such as DPC902, may also initiate resource reduction by the eNodeB. The home network may facilitate the secondary user to switch from the host network spectrum to the home network spectrum. If the home network does not have the capacity to handle traffic or does not perform the handover in a timely manner, it may either hand off the communication session to another network or channel or force the secondary user wireless device 101 to perform a reselection procedure. Once the eNodeB has switched all secondary users from the host spectrum, it may remove the spectrum channel from the available list of channels accessible to the secondary users.

Once the primary network has resolved the capacity restriction, the spectrum may be reallocated to the home network. To reallocate resources, the host DSC910 may notify the DPC902 that the spectrum resources are again available for use by the home network. The home DPC902 may notify the home DSC910 that resources are again available. Resources may be reallocated to the home network based on predetermined policies and rule sets.

Fig. 34 shows a smartphone 101a, laptop 101b, and cell phone 101c in communication with element 3402 connected to the primary 3404 and secondary 2306 and in communication with base stations 102a and 102b via the primary RAT and secondary RAT. Base station 102a is connected to a primary network and base station 102b is connected to a secondary network 102 b. In one embodiment, as shown in fig. 34, a DSA communication system may allow wireless devices 101a-101c to access several radio access technologies (i.e., primary and secondary RATs) simultaneously. For example, the DSA may enable a wireless device 101 using a primary RAT of a primary network to access a secondary RAT on a secondary network only for certain types of services. For example, when the wireless device 101 usage of the primary network causes high volume or bursty traffic, the DSA communication system may enable the primary network to offload and send the high volume and bursty traffic to the secondary network. For example, primary and secondary elements 2306 and 3404 may provide data to route traffic to primary and secondary wireless networks and base stations using data headers. Handover may occur using DSA to handover between networks. In another embodiment, switching can occur using element 3402, primary or secondary components 3404 or 3406. In yet another embodiment, the handover may be initiated by the primary or secondary DSA network, or by another entity observing the capacity of the network.

Figure 35 illustrates a message flow diagram 3500 of an arbitration procedure in a DSA communication system, according to one embodiment. In the present embodiment, one bidder (i.e., network 1) is used for simplicity, however, it is contemplated that multiple bidders may use this process. Network 13501 may send a request to DPC902 for resource message 3502. The DPC902 may receive the request message and send queries 3504, 3506 to the participating DSCs 910a, 910b of network 2 and network 3 based on predefined criteria, which may include the type and capabilities of the user wireless device 101 in addition to the geographic criteria of the requesting wireless device 101. The geographic criteria may include the geographic location, geographic polygon, or permissible region of the consumer wireless device 101. The geographic criteria request may include a number of parameters greater than those that the host network may allow. DPC902 may receive resource inquiry responses 3508, 3510 from each DSC910a, 910b contacted.

DPC902 may send resource availability message 3512 to notify network 1 that the requested resources are available through DSC910 a. The network 13501 may receive the resource availability message 3510 and in response send a resource request message 3514 to DPC902 to reserve available resources at DSC910 a. The DPC902 may send a resource reservation request 3516 to the DSC910 a. Upon receiving the resource reservation request 3516, the DSC910a may reserve the requested spectrum and send a resource reservation message 3518 back to the DPC 902. DPC902 may receive resource bid message 3520 from network 1, accept the bid (subject to the policies and rules of DPC902 if bidding) and send bid accept message 3522 to network 13501. Upon accepting bids from bidders, DPC902 may also send an assign resource request 3524 to DSC910a to allocate reserved resources to network 13501. DSC910a may receive an assign resource request 3524, allocate resources to be used by network 13501, and send a resource allocation message 3526 to DPC 902. The DPC902 may inform the network 13501 that the requested resource allocation is now available to the wireless device 101 for use by the subscriber network 13501 by sending a resource allocation message 3528 to the network 13501. Resources are available for use by the network 13501. Once these resources are used, DSC910a may send resource consumption/release message 3530 to DPC 902. DPC902 may receive resource consumption/release message 3530 and send resource consumption/release message 3532 to network 13501. Network 13501 may pay for the spectrum it uses.

Fig. 36-40 show a flow diagram of one embodiment method for allocating and accessing resources using a DSA communication system. As shown in fig. 36, network 1DSC 910a may monitor call traffic compared to the total spectrum resources available to network 1 (block 3602). DSC910a may record the resource status of network 1 and report it to DPC 902. DPC902 may receive the resource status report from network 1 (block 3702) and store it (block 3704). The DSC910a of network 1 may determine whether additional resources may be required to provide services to existing users of network 1 based on the resource status report (determination 3606). If no additional resources are required (i.e., determination 3606 — no), DSC910a may continue to monitor the available resources, vs. bandwidth traffic, by returning to block 3602. If additional resources are required (i.e., determination 3606 — yes), the DSC910a may send a request to the DPC902 for additional resources (block 3608).

The network 2DSC 910b may also monitor the available resources in network 2, vs. bandwidth traffic (block 3602), and report the resource status to the DPC902 (block 3804). DPC902 may receive a resource status report from DSC910b (block 3702) and store the received data (block 3704). The DSC910b may determine whether an excess amount of resources are available in the network 2 (determination 3804). If an excess amount of resources is not available in the network 2 (i.e., determination 3804 — no), the DSC910b may continue to monitor the available resources, vs. bandwidth traffic by returning to block 3602. If an excess amount of resources is available (i.e., determination 3804 — yes), DSC910b may allocate the excess resources or a sub-portion of the excess resources for secondary use (block 3806), and report the allocation of the resources for secondary user use to DPC902 (block 3808). DPC902 may receive a resource allocation report from DSC910b (block 3702), and store the received data (block 3704).

DPC902 may receive resource status reports from many different networks. However, in this embodiment, only the interaction of the DPC902 with the two networks is shown for ease of illustration. The status report received from the network may further include additional information such as network rules and policies regarding accessing and using the allocated resources. For example, the status report from network 2 may include system requirements for network 2 that must be met before wireless device 101 can successfully access the allocated resources on network 2 as a secondary user.

The DPC902 receives a request for additional resources from the DSC910a of network 1 (block 3706), and selects the best available network from which network 1 may purchase additional resources based on data received from other networks in block 3708. In this example, DPC902 may select network 2 as the most appropriate network to provide resources to network 1. The DPC902 may send a resource query to the network 2 (block 3710) to determine the availability and amount of the allocated excess resources of the network 2.

The DSC910b of network 2 may receive a resource query (block 3810) and determine resource availability (block 3812). DSC910b may send a resource query response to DPC 902. The resource query response may include information about the quality and quantity of resources available to the secondary user. DPC902 may receive a resource query response (block 3712).

As shown in fig. 37, the DPC902 may determine whether resources are available based on data received from the DSC910b of network 2 (block 3714). If the data is not available (i.e., determination block 3714 ═ no), DPC902 may send an unavailable resources message to network 1 (block 3722). Resources may not be available to the network for different reasons. For example, the resources may be purchased by other bidders before they are reserved by the network. The DSC910a of network 1 may receive the no available resources message (block 3614) and search for other available spectrum resources or terminate the connection session with the user to free up resources on network 1 (block 3618).

If data is available (i.e., determination 3714 ═ yes), DPC902 may send a resource available message to DSC910a to inform network 1 of the quality and quantity of resources available for secondary use at network 2 (block 3716). DSC910a may receive the resource available message and send a request resource message to reserve the allocated resources of network 2 for use by subscribers of network 1 (block 3612). The request resource message may include data as to the amount of resources that the network 1 may require in this transaction.

DPC902 may receive the resource request message (block 3718) and send a reserved resource request message to network 2 (block 3720). The DSC910b at network 2 may receive a reserve resource request (block 3816) and reserve the requested amount of allocated resources for use by network 1 subscribers (block 3818). The DSC910b of network 2 may confirm that the requested amount of allocated resources are reserved for use by network 1 by sending a resource reservation message (block 3820). DPC902 may receive resource reservation messages from network 2 and prepare for bidding procedures as described in fig. 38.

As shown in fig. 38, the DSC910a of network 1 may send a resource bid to negotiate access to reserved resources of network 2 (block 3620). DPC902 may receive the resource bid and process it (block 3726). In determination block 3728, DPC902 may determine whether to accept the bid received from network 1. The DPC902 may evaluate bids from network providers based on policies and rule sets of the DSA communication system in addition to requirements set forth by the resource providing network or by other methods, such as price and allocation or access methods. If bidding is accepted (i.e., determination 3728 ═ yes), DPC902 may send an accept bidding message to network 1 (block 3730). In block 3622, the DSC910a may receive an accept bid message and wait for a resource access instruction. Once the bid is accepted, the DPC902 may also send an assign resource message to the DSC910b of network 2 (block 3732). DSC910b may receive the assign resources message (block 3822) and assign reserved resources for use by network 1 (block 3824). DSC910b may transmit a resource access message to enable network 1 to access the assigned resources of network 2 (block 3826), and is configured to establish a communication session with wireless device 101 of network 1 (block 3828).

The DPC902 may forward the resource access message to the network 1 (block 3734). The DSC910a may receive a resource access message (block 3624). The resource access message may include data, such as access parameters, that secondary user wireless device 101 may use to access resources on network 2. DSC910a may send access parameters for network 2 to wireless device 101 having a communication session with network 1 and network 1 has designated a migration to network 2 (block 3626). The designated wireless device 101 may receive an access message for network 2 (block 3902) and establish a communication session with wireless device 101 of network 1, steps 3904 and 3830. The network 2 may begin the redemption process as described in more detail below with reference to fig. 40.

If bidding is denied (i.e., determination block 3728 ═ no), DPC902 may send a decline bid message to network 1 (block 3736) (as shown in fig. 39). As shown in fig. 39, the DSC910a may receive a decline bid message (block 3736) and determine whether to re-bid (determination 3640). If there is no re-bidding (i.e., determination 3640 no), DSC910a may send a cancel resource request message (block 3644). The DPC902 may receive a cancel resource request message (block 3742) and send a resource release message to the network 2 (block 3744). The DSC910b of network 2 may receive a resource release message (block 3832), release the reserved resources for use by other networks (block 3834), and report the allocated resource status to the DPC902 by returning to block 3808 and following the steps described above with respect to fig. 36, as shown in fig. 36.

If a re-bid is being re-bid (i.e., it is determined 3640 yes), the DSC910a may send a new bid for the same resource (block 3642). DPC902 may receive the new bid (block 3738) and determine whether to accept the new bid (determination 3740). If the new bid is rejected again (i.e., determination 3740 ═ no), DPC902 may send a decline bid message by returning to block 3736. If bidding is accepted (i.e., determination 3740 ═ yes), DPC902 sends an accept bid message by returning to block 3730, as shown in figure 38 and following the same steps as described above with reference to figure 38.

Fig. 40 shows the redemption process after network 2 provides access to the secondary user wireless device 101 of network 1. The DSC910b of network 2 may send invoices and payment instructions to the DPC902 related to the use of the allocated resources by network 1 (block 3836). DPC902 may forward the invoice and payment instructions from network 2 to network 1 (block 3746). DSC910a may receive invoices and payment instructions (block 3644) and pay fees for payment with network 2 (steps 3648 and 3840).

Alternatively, the DSC910b of network 2 may send the usage parameters and payment instructions to the DPC902 (block 3838). The DPC902 may receive usage parameters and payment instructions (block 3748), create an invoice (block 3750), and send the invoice to the network 2 (block 3752). DSC910a may receive invoices and payment instructions (block 3646) and pay fees for payment with network 2 (steps 3648 and 3840).

Fig. 41 shows a message flow diagram 4100 of message communication between components of a network provider that allocates available resources to other resources of a requesting network. The DSC910a at network 13501 may send a resource request (message 3502). DPC902 may receive the request for resource message and send a resource query to network 2 (message 3504). At network 2, a resource query may be received at DSC910 b. DSC910b may send a resource query to OMC912 in network 2 to determine whether resources are available for network 1 (message 4106). OMC912 may receive a resource query message from DSC910b and send a resource query message to access resource 4102 (message 4108). OMC912 may also send a resource query message (message 4110) to core resources 4204. Access resources 4102 and core resources 4204 each receive a resource query message from OMC912 and send a resource response (messages 4112, 4114), respectively, to OMC 912. Resources from access resources 4102 may include message parameters. The resource response from access resource 4102 may include other message parameters.

OMC912 may receive resource responses from access resources 4102 and core resources 4104 and send a resource response message to DSC910b indicating the status of resource availability in network 2 (message 4116). DSC910b may receive a resource response message from OMC912 and send a resource query response to DPC902 (message 3508). The DPC902 may receive the resource query response from DSC910b, determine whether the type of resource requested is available at network 2 and send a resource available message to DSC910a of network 1 (message 3512). DSC910a may receive the resource available message and send a resource request message to direct DPC902 to request available resources from network 2 (message 3514). The DPC902 may receive the resource request message and send a resource reservation request message to the DSC910b requesting reservation of available resources in network 2 for use by network 1 (message 3516). DSC910b may receive the resource reservation request message and send a resource reservation request to access resources 4102 via OMC912 (message 4118), and to core resources 4104 (message 4120).

Access resources 4102 may receive resource reservation requests from OMC912, reserve available resources and send resource reservation messages back to DSC910b via OMC912 (message 4122). Similarly, core resources 4104 may receive a resource reservation request from OMC912, reserve available resources and send a resource reservation message back to DSC910b via OMC912 (message 4124). DSC910b may receive resource reservation messages from access resources 4102 and core resources 4104 and send a resource reservation message to DPC902 to inform DPC902 and network 1 to reserve the requested resources for use by network 1 (message 3518). DPC902 may receive a resource bidding message from DSC910a of network 1 (message 3520). If the bids received by DPC902 meet the price and contract requirements of network 2, DPC902 may send a bid acceptance message to DSC910a (message 3522). If bidding is accepted, DPC902 may send an assign resource request to DSC910b (message 3524). DSC910b may receive an assigned resource request for access resources 4102 (message 4126) and an assigned resource request for core resources 4104 (message 4128). The DSC910b may further send a policy for resource assignment message to the policy controller 905, which may be the same or different with respect to PCFF (message 4130). The DSC910b may further send a metric for the assigned resources to the AAA/AuC 4106 (message 4132).

Fig. 42-44 show process flow diagrams of embodiment methods for back-off secondary users by switching them to their home network or terminating their communication session with the host network. The wireless device 101 from network 1 may establish a secondary user communication session with network 2 via the DSC910b (steps 3904, 3830). The DSC910b of network 2 may continuously monitor traffic on the network vs. available resources (block 3602) and send a report to the DPC902 (block 3604). The DPC902 may receive a resource status report from the DSC910 b. DSC910b may further determine whether the amount of network is greater than the capacity of the network based on the available resources of the network (determination 4404). If the amount of network is not greater than the capacity of the network (i.e., determination 4404 is no), DSC910b may continue to monitor network traffic vs. available resources by returning to block 3602. If the amount of networks is greater than the capacity of the networks (i.e., determination 4404-yes), DSC910b may identify the user on the networks (block 4406) and determine whether the user is a secondary user (determination 4408).

If the user is a secondary user (i.e., determination 4408-yes), DSC910b may send a disconnect session message at t, which is the amount of time remaining before network 2 will terminate the secondary user communication session (block 4410). As shown in fig. 43, the DPC902 may receive a disconnect session message at t (block 4306). Alternatively, instead of sending a disconnect session message at t, DSC910b may terminate the secondary user's communication session to immediately provide additional resources for the primary or other important user (block 4412). The alert regarding whether to terminate immediately or transmit prior to termination of the secondary user may be based on contract terms between the primary and secondary network providers and DSA communication system policies and rule sets.

If the user is not a secondary user (i.e., determination 4408-no), DSC910b may determine whether there are any other secondary users on the network (step 4414). If there are other secondary users still connected to the network 1 (i.e., determination 4414-yes), the DSC910b may first send an attempt to disconnect their session before the primary user by returning to steps 4410, 4412. If there are no other secondary users on the primary network (i.e., determination 4414 no), the DSC910b may hold or hang up the primary user communication session based on hierarchical priority access rules (block 4416). For example, high-end primary users (i.e., those users with more expensive subscription plans) may be hung up last. Alternatively, in one embodiment (not shown), instead of terminating the primary user communication session, the DSC910b may attempt to switch the user to another network as a secondary user, thus preserving the communication session connection while reducing the amount of network 1. DSC910b may determine whether additional callers need to be triaged by returning to monitoring network traffic vs. capacity by returning to block 4404.

As shown in fig. 43, the DPC902 may forward a disconnect session message at t to the DSC910a (block 4306). DSC910a may receive a disconnect session message at t (block 4206), set a timer to count down from t (block 4208), and monitor its available resources (block 4210) to determine if there are available resources on network 1 to receive a secondary user communication session from network 2 (decision 4212). If the resource is not available on the network 1 (i.e., determination 4212 — no), the DSC910a may send a request for the resource to the DPC902 (block 3808) to reserve and purchase the available resource from the network provider by returning to block 3706 of fig. 36 and following the resource allocation steps as described above with reference to fig. 36-40.

If resources are available on network 1 (i.e., it is determined 4212 — yes), DSC910a may allocate resources to a secondary user to be terminated from network 2 (block 4212) and send an instruction to DPC902 to disconnect from network 2 and connect to network 1 for wireless device 101, as shown in fig. 44 (block 4308). The DSC910a may also configure/prepare the network 1 system to connect to the secondary user wireless device 101 (block 4218).

As shown in fig. 44, DPC902 may forward instructions to DSC910b of network 2 for wireless device 101 to disconnect from network 2 and connect to network 1 (block 4308). The DSC910b may receive instructions (block 4418) and transmit them to the secondary user wireless device 101 that currently has a communication session with the network 2 (block 4420). Wireless device 101 may receive instructions to disconnect from network 2 and connect to network 1 (block 4220) and end the communication session with network 2 (block 4222) and establish the communication session with network 1 (steps 4224, 4226).

Public safety network:

in one embodiment, the primary network provider of the DSA communication system may be a public safety network. The public safety network may be a holder or owner of the public safety spectrum. The public safety spectrum is typically reserved for use by public safety authorities. The assigned public safety bandwidth typically includes more spectrum than the public safety authorities use based on average conditions. It is expected to be used during public safety emergencies such as disasters, assigning an excess amount of spectrum to public safety usage.

In one embodiment, a DSA communication system may allow public safety networks to lease spectrum resources to other networks when the public safety spectrum is available and not in use. During public safety emergencies, when all network resources may be needed for public safety authorities, DSA communication systems may allow a network to withdraw all of its allocated resources from other networks by offloading traffic from the public safety network to free the resources.

Furthermore, the DSA communication system may enable the public safety network to lease or employ resources from other networks participating in the DSA communication system if the assigned spectrum of the public safety network proves insufficient to handle the heavy usage of public safety authorities during an emergency. For example, DSA communication systems may require that all participating networks continuously keep a certain percentage (e.g., 10%) of their resources unassigned. Public safety networks may use unassigned resources of participating networks to increase their resources for public safety communications during an emergency. DSA communication systems may further offload primary and/or secondary users of the primary network to free up resources for use by public safety authorities.

In one embodiment, access to the public safety spectrum may be based on the hierarchical priority access method described above with reference to fig. 1-8. For example, a police dispatcher may always have access to the spectrum. However, access by other non-government users of public safety resources may be limited to certain time periods or dates, depending on the contract between the user and the public safety network provider.

In one embodiment, offloading non-public safety users from a public safety network or other network may be performed using the hierarchical priority access method described above with reference to fig. 1-8. For example, in public safety networks, when resources are needed for public safety use, DSA communication systems may enable public safety networks to offload users in a prioritized order, e.g., offload secondary non-public safety users first, offload primary non-public safety users second, offload low-level public safety users third, and so on. Similar hierarchical priority access methods may be used to offload users of another network, the resources of which may be used by public safety networks.

In one embodiment, during an emergency, the DSA communication system may restrict access to resources allocated to any public safety network for secondary use. For example, once the DSA communication system determines that a public safety emergency exists, the DSA communication system may no longer consider allocated resources from the public safety network involved in the emergency as resources available for use by other networks.

In one embodiment, DSA communication system policies and rule sets may require participating networks to allocate a percentage of their resources for public safety use and disaster response purposes. During an emergency, the DSA communication system may enable the public safety network to access additional resources, which each non-public safety network may allocate for public safety use. In this scenario, if the allocated resources are in use, a hierarchical priority access method may be used to offload users from the allocated resources. Other resources of the non-public safety network may not be used for public safety unless negotiated properly.

Fig. 45-49 show a flow diagram of an embodiment method for allocating and accessing resources of a public safety network using a DSA communication system. As shown in fig. 45, DSC910a may monitor resource vs. bandwidth traffic in network 1 (block 3602). DSC910a may record the resource status of network 1 and report it to DPC 902. DPC902 may receive the resource status report from network 1 (block 3702) and store it (block 3704). The DSC910a of network 1 may determine whether additional resources may be required to provide services to existing users of network 1 based on the resource status report (determination 3606). If no additional resources are required (i.e., determination 3606 — no), DSC910a may continue to monitor the available resources, vs. bandwidth traffic, by returning to block 3602. If additional resources are required (i.e., determination 3606 — yes), the DSC910a may send a request for additional resources to the DPC902 (block 3608).

In block 4502, the public safety network DSC910b may reserve a predetermined amount of unused resources as a backup for use only by public safety authorities. This may ensure that resource resources may be easily dedicated to public safety use if needed during an emergency such as a natural disaster until additional resources are released by offloading secondary users from the network. The public safety network DSC910b may also monitor the available resources vs. bandwidth traffic in the public safety network (block 3602) and report the resource status to the DPC902 (block 3804). DPC902 may receive a resource status report from DSC910b (block 3702) and store the received data (block 3704). The DSC910b may determine whether an excess amount of resources is available in the public safety network (decision 3804). If an excess amount of resources is not available in the public safety network (i.e., determination 3804 — no), the DSC910b may continue to monitor the available resources vs. bandwidth traffic by returning to block 3602. If an excess amount of resources is available (i.e., determination 3804 — yes), the DSC910b may allocate the excess resources or a sub-portion of the excess resources for secondary use (block 3806) and report to the DPC902 that the resources are allocated for secondary user use (block 3808). DPC902 may receive a resource allocation report from DSC910b (block 3702), and store the received data (block 3704).

The status report received from the network may further include information such as network rules and policies regarding access to and usage of the allocated resources. For example, the status report from the public safety network may include system requirements for the public safety network that must be met before the wireless device 101 can successfully access the allocated resources on the public safety network as a secondary user.

The DPC902 receives a request for additional resources from the DSC910a of network 1 (block 3706), and selects from the best available network from which network 1 may purchase additional resources based on data received from other networks (block 3708). In this embodiment, DPC902 may select the public safety network as the most appropriate network to provide resources to network 1. In block 3710, the DPC902 may send a resource query to the public safety network to determine the availability and amount of the allocated excess resources of the public safety network.

The DSC910b of the public safety network may receive a resource query (block 3810) and determine resource availability (block 3812). DSC910b may send a resource query response to DPC 902. The resource query response may include information about the amount and quality of resources available to the secondary user. DPC902 may receive a resource query response (block 3712).

As shown in fig. 46, the DPC902 may determine whether resources are available based on data received from the DSC910b of the public safety network (block 3714). If data is not available (i.e., determination 3714 ═ no), DPC902 may send an unavailable resource message to network 1 (block 3722). Resources may not be available to the network for different reasons. For example, resources may be sold to other bidders before being reserved by the requesting network. The DSC910a of network 1 may receive the no available resources message (block 3614) and search for other available spectrum resources or terminate the connection session with the user to free up resources on network 1 (block 3618).

If data is available (i.e., determination 3714 ═ yes), the DPC902 may send a resource available message to the DSC910a to inform the network 1 of the quality and quantity of resources available for secondary use at the public safety network (block 3716). DSC910a may receive the resource available message and transmit a request resource message to reserve allocated resources of the public safety network for use by subscribers of network 1 (block 3612). The request resource message may include data as to the amount of resources that the network 1 may require in this transaction. DPC902 may receive the resource request message (block 3718) and send a reserved resource request message to the public safety network (block 3720). DSC910b at the public safety network may receive a reserve resource request (block 3816) and reserve the requested amount of allocated resources for use by network 1 subscribers (block 3818). The DSC910b of the public safety network may confirm that the requested amount of allocated resources is reserved for use by the network 1 by sending a resource reservation message (block 3820). DPC902 may receive a resource reservation message from the public safety network and prepare for the bidding process, as described in figure 47.

As shown in fig. 47, the DSC910a of network 1 may send a resource bid to negotiate access to reserved resources of a public safety network (block 3620). DPC902 may receive the resource bid and process it (block 3726). In determination block 3728, DPC902 may determine whether the bid received from network 1 is acceptable. The DPC902 may evaluate bids from network providers based on policies and rule sets of the DSA communication system and requirements set forth by the resource providing network (e.g., price and allocation or access methods).

If bidding is accepted (i.e., determination 3728 ═ yes), DPC902 may send an accept bidding message to network 1 (block 3730). The DSC910a may receive an accept bid message and wait for a resource access instruction (block 3622). Upon accepting the bid, the DPC902 may also send an assign resource message to the public safety network DSC910b (block 3732). DSC910b may receive the assign resources message (block 3822) and assign reserved resources for use by network 1 (block 3824). DSC910b may transmit a resource access message to enable network 1 to access the assigned resources of the public safety network (block 3826), and configure to establish a communication session with wireless device 101 of network 1 (block 3828).

The DPC 902 may forward the resource access message to the network 1 (block 3734). The DSC910a may receive a resource access message (block 3624). The resource access message may include data such as access parameters that may be used by the secondary user wireless device 101 to access resources on the public safety network. It should be appreciated that other data may be included in the resource access message. The DSC910a may send access parameters for a public safety network to the wireless device 101 having a communication session with network 1 and the network 1 has designated a migration to the public safety network (block 3626). The designated wireless device 101 may receive access parameters for the public safety network (block 3902) and establish a communication session with the wireless device 101 of the network 1 (steps 3904 and 3830). The public safety network may begin a redemption process as described in more detail below with reference to figure 49.

If bidding is denied (i.e., determination 3728 ═ no), DPC 902 may send a decline bid message to network 1 (block 3736) (shown in fig. 48). As shown in fig. 48, the DSC910a may receive a decline bid message (block 3736) and determine whether to re-bid (determination 3640). If there is no re-bidding (i.e., determination 3640 no), DSC910a may send a cancel resource request message (block 3644). The DPC 902 may receive a cancel resource request message (block 3742) and send a resource release message to the public safety network (block 3744). The DSC910b of the public safety network may receive a resource release message (block 3832), release the reserved resources for use by other networks (block 3834), and report the allocated resource status to the DPC 902 by returning to block 3808 as shown in figure 45 and following the steps described above with reference to figure 45.

If a re-bid is being re-bid (i.e., it is determined 3640 yes), the DSC910a may send a new bid for the same resource (block 3642). DPC 902 may receive the new bid (block 3738) and determine whether to accept the new bid (determination 3740). If the new bid is rejected again (i.e., determination 3740 ═ no), DPC 902 may send a decline bid message by returning to block 3736. If bidding is accepted (i.e., determination 3740 ═ yes), DPC 902 sends an accept bid message by returning to block 3730, as shown in figure 47 and following the same steps as described above with reference to figure 47.

Figure 49 shows the redemption process after the secondary user wireless device 101 of the public safety network provider access network 1. The DSC910b of the public safety network may send invoices and payment instructions to the DPC 902 regarding the use of the allocated resources by the network 1 (block 3836). The DPC 902 may forward the invoice and payment instructions from the public safety network to the network 1 (block 3746). The DSC910a may receive invoices and payment instructions (block 3644) and reimburse the billing for the public safety network (steps 3648 and 3840).

Optionally, the DSC910b of the public safety network may send the usage parameters and payment instructions to the DPC 902 (block 3838). DPC 902 may receive usage parameters and payment instructions (block 3748), create an invoice (block 3750), and send the invoice to a public safety network (block 3752). The DSC910a may receive invoices and payment instructions (block 3646) and reimburse the billing for the public safety network (steps 3648 and 3840).

Fig. 50-53 show process flow diagrams of embodiment methods for back-off of secondary users by switching them to their home network or terminating their communication session with the host network. The wireless device 101 from the network 1 may establish a secondary user communication session with a public safety network via the DSC910b (steps 3904, 3830). The DSC910b of the public safety network may continue to monitor traffic on the network vs. available resources (block 3602) and send a report to the DPC 902 (block 3604). The DPC 902 may receive a resource status report from the DSC910 b. DSC910b may further determine whether the amount of network is greater than the capacity of the network based on the available resources of the network (determination 4404). If the amount of network is not greater than the capacity of the network (i.e., no to determine 4404), the DSC910b may continue to monitor network traffic vs. If the amount of networks is greater than the capacity of the networks (i.e., determination 4404-yes), DSC910b may identify the user on the networks (block 4406) and determine whether the user is a secondary user (determination 4408).

If the amount of network exceeds the allocated capacity threshold for the network (i.e., it is determined 4408-yes), there is an abnormal situation that may indicate that an emergency situation is developing. In this scenario, DSC910b may follow the process shown in the process flow diagram of fig. 50 to free resources for public safety use and fig. 54 to incrementally allocate network resources based on a hierarchical priority access regime.

As shown in fig. 50, to free resources for public safety use, the public safety network may send a disconnect session message at t, which is the amount of time left before the public safety network terminates the secondary user communication session (block 4110). As shown in fig. 43, the DPC 902 may receive a disconnect session message at t (block 4306). Alternatively, instead of sending the disconnect session message at t, DSC910b may terminate the secondary user's communication session to immediately provide additional resources for the primary or other important user (block 4412). The alert regarding whether to terminate immediately or transmit prior to termination of the secondary user may be based on contract terms between the primary and secondary network providers and DSA communication system policies and rule sets.

If the user is not a secondary user (i.e., determination 4408 — no), DSC910b may determine whether there are any other secondary users on the network (block 4414). If there are other secondary users still connected to the network 1 (i.e., determination 4414-yes), the DSC910b may first send an attempt to disconnect their session before the primary user by returning to steps 4410, 4412. If there are no other secondary users on the primary network (i.e., determination 4414 no), the DSC910b may hold or hang up the primary user communication session based on hierarchical priority access rules (block 4416). For example, high-end primary users (i.e., those users with more expensive subscription plans) may be hung up last. Alternatively, in one embodiment (not shown), instead of terminating the primary user communication session, DSC910b may attempt to switch the user to another network as a secondary user, thus, preserving the communication session connection while reducing the amount of network 1. DSC910b may determine whether additional callers need to be triaged by returning to monitoring network traffic vs. capacity by returning to block 4404.

As shown in fig. 51, the DPC 902 may forward a disconnect session message at t to the DSC910a (block 4306). DSC910a may receive a disconnect session message at t (block 4206), the device timer counts down from t (block 4208), and monitor its available resources (block 4210) to determine whether there are resources available on network 1 to receive a secondary user communication session from a public safety network (decision 4212). If the resource is not available on the network 1 (i.e., determination 4212 — no), the DSC910a may send a request for the resource to the DPC 902 (block 3808) to reserve and purchase the available resource from the network provider by returning to block 3706 of fig. 45 and following the resource allocation steps as described above with reference to fig. 45-49.

If resources are available on network 1 (i.e., determination 4212 is yes), DSC910a may allocate resources to a secondary user to be terminated from a public safety network (block 4212) and send an instruction to DPC 902 to disconnect wireless device 101 from the public safety network and connect to network 1 as shown in fig. 52 (block 4308). The DSC910a may also configure/prepare the network 1 system to connect to the secondary user wireless device 101 (block 4218).

As shown in fig. 52, the DPC 902 may forward an instruction for the wireless device 101 to disconnect from the public safety network and connect to network 1 to the DSC910b of the public safety network (block 4308). The DSC910b may receive instructions (block 4418) and transmit them to the secondary user wireless devices 101 that currently have a communication session with a public safety network (block 4420). Wireless device 101 may receive an instruction to disconnect from the public safety network and connect to network 1 (block 4220) and end the communication session with the public safety network (block 4222) and establish the communication session with network 1 (steps 4224, 4226).

In yet another embodiment, the public safety network may monitor all new reserved resource requests and queries received from the DPC 902 to ensure that resources are only provided to those requests initiated by the public safety authority on the basis of the TPA, at least until the resource capacity returns below a threshold level. The public safety network may receive the request to reserve resources at the DSC910b (block 3810) and determine whether the resource inquiry is from a device authorized for TPA (determination 312). If the resource request is from a device that is authorized a TPA (i.e., determination 312 is yes), DSC910b may disconnect a non-TPA communication session, such as a secondary user communication session (block 314), and connect the TPA call (block 315). DSC910b may again monitor resource v. If the resource reservation message is from wireless device 101 and not an authorized device (i.e., no at decision 312), the public safety network may block the call until the excess resources are again available to the secondary user (block 5302).

In one embodiment, for a person attempting an authorized TPA that establishes a communication session with a public safety network using a wireless device that subscribes to a network provider other than the public safety network provider, a prefix number and an access PIN may be provided to the public safety authority that may prompt the receiving network provider to request transfer of the communication session to the public safety network. By using the prefix number and PIN, the public safety user can access the public safety network using any device, even though the device is considered a secondary user wireless device 101 on the public safety network.

As shown in fig. 54-56, when an authorized public safety officer requires a connection to be established with a particular public safety network, he may use any unauthorized wireless device 101 of network 1 and dial a special prefix number, e.g., x 272, to place a call (block 5402). The DSC910a may receive and process the call (block 5404) and identify the prefix number as requesting transfer of the communication session to a public safety network (block 5406). The DSC910a may send a PIN request to the wireless device 101 (block 5408). The wireless device 101 may receive a PIN request (block 5410), display the PIN request to the user using a Graphical User Interface (GUI) and receive a PIN entry for the user (block 5412). Wireless device 101 may send the entered PIN to DSC910a for processing (block 5414). The DSC910a may receive the PIN (block 5416) and send a request for a network transfer along with the PIN to the DPC 902 (block 5418). DPC 902 may receive a request for a network transfer (block 5420) and determine whether the PIN matches the PIN database (decision 318). If the PIN does not match an entry in the PIN database (i.e., determination 318 no), DPC 902 may block the call (block 5302). If the PIN matches an entry in the PIN database (i.e., determination 318 no), the DPC 902 may identify the target public and secure network based on the received PIN (block 5422).

As shown in fig. 55, the DPC 902 may determine whether the wireless device 101 of the network 1 includes a technology compatible with the target public safety network (block 5424). If the device and the public safety network are technically incompatible (i.e., determination 5424 no), the DPC 902 may send a network incompatible message to the device via DSC910a (block 5426). The DSC910a may forward the network incompatible message (block 5428) and terminate the connection with the wireless device 101 (block 5432). The wireless device 101 may receive the network incompatible message (block 5430), display the message to the user (block 5434), and terminate the connection with the network 1 (block 5436). If the device is compatible with public safety network technology (i.e., determination 5424 is yes), the DPC 902 may send a resource reservation with PIN request to the public safety network DSC910b (block 5438). DSC910b may receive a reserve resource request with a PIN (block 5440).

In one embodiment, as shown in FIG. 56, access to the public safety network by authorized public safety authorities may be at a priority level. For example, a higher level official of a public safety organization may have priority access to the network over a lower level official from the same organization. At any given time, depending on the level of traffic and available resources, the public safety network may determine what level of authority may have access to the network. Alternatively, DSC910b may be configured to allow those with a required priority level and reject those with a lower priority level than required. DSC910b may continually reevaluate resource availability and change the officer's access level based on the availability of the resource. The DSC910b may determine a priority level for the user of the wireless device 101 based on the PIN (block 5442). DSC910b may determine whether the devices 101 of that level of priority are then allowed access to the public safety network (decision 5444). If the device 101 priority level is authorized (i.e., determination 5444 is yes), DSC910b may disconnect a non-TPA session or a lower priority TPA session to release resources for a new request for resources (block 5446), and connect the new TPA session (block 5448), and return to monitoring resources vs. bandwidth traffic of the network (block 3602 of fig. 45). If the request is from a TPA-authorized device that does not have a priority level of access to the network at the time (i.e., determination 5444 no), DSC910b may block the call (block 5302).

As discussed above, the methods and systems of various embodiments provide a Dynamic Spectrum Arbitrage (DSA) system for dynamically managing the availability, allocation, access, and use of RF spectrum and RF spectrum resources through the use of real-time data. Various embodiments may also include a dynamic spectrum policy controller (DPC) configured to manage DSA operations and interactions between two or more networks (e.g., between a lessor network and a tenant network). The DPC may communicate with various network components in a network provider network through one or more Dynamic Spectrum Controller (DSC) components, which may be included in or added to multiple networks participating in a DSA system. Efficient interaction between the DPC and multiple DSCs in a DSA system may improve the performance and efficiency of resource allocation operations of the DSA system.

Figure 57 illustrates a number of network components and information flow in an example communication system 5700, which includes two long term evolution (LTE or 4G LTE) systems interconnected by a DPC5720 and is suitable for implementing various embodiments. Each LTE communication system may include multiple eNodeB components 5704a, 5704b coupled to Mobility Management Entity (MME) components 5706a, 5706b and Serving Gateways (SGW)5708a, 5708 b. The MMEs 5706a, 5706b and SGWs 5708a, 5708b may be part of a core network 5730a, 5730b, such as a System Architecture Evolution (SAE) or Evolved Packet Core (EPC) network. The enodebs 5704a, 5704b may be outside of the core networks 5730a, 5730 b.

Each eNodeB5704a, 5704b may be configured for communicating voice signals, data signals, and control signals between mobile devices 5702 (e.g., cellular telephones) or to other network destinations. The enodebs 5704a, 5704b may act as a bridge (e.g., a layer 2 bridge) between the mobile device 5702 and the core networks 5730a, 5730b by serving as a termination point for all radio protocols toward the mobile device 5702 and forwarding voice signals (e.g., VoIP, etc.), data signals, and control signals to various network components in the core networks 5730a, 5730 b. The enodebs 5704a, 5704b may be configured to perform various radio resource management operations, such as controlling the use of the radio interface, allocating resources on a request basis, prioritizing and scheduling traffic according to various quality of service (QoS) requirements, monitoring the use of network resources, and so forth. The enodebs 5704a, 5704b may also be configured to acquire radio signal level measurements, analyze the acquired radio signal level measurements, and handover the mobile device 5702 (or a connection to the mobile device) to another base station (e.g., a second eNodeB) based on the results of the analysis.

In general, the mobile device 5702 transmits to and receives from enodebs 5704a, 5704b voice signals, data signals, and/or control signals over the wireless communication links 5722, 5724. The enodebs 5704a, 5704b may send signaling/control information (e.g., information related to call setup, security, authentication, etc.) to the MMEs 5706a, 5706b via the S1-AP protocol over the S1-MME interface. The MMEs 5706a, 5706b may request user/subscriber information from Home Subscriber Servers (HSS)5710a, 5710b over an S6-a interface, communicate with other MME components over an S10 interface, perform various management tasks (e.g., user authentication, enforcement of roaming restrictions, etc.), select SGWs 5708a, 5708b, and send authorization and management information to the enodebs 5704a, 5704b and/or SGWs 5708a, 5708b (e.g., over S1-MME and S11 interfaces).

Upon receiving authorization information (e.g., an authentication complete indication, an identifier of the selected SGW, etc.) from the MME5706a, 5706b, the eNodeB5704a, 5704b may send data received from the mobile device 5702 to the selected SGW 5708a, 5708b via GTP-U protocol over the S1-U interface. The SGWs 5708a, 5708b may store information about received data (e.g., a plurality of parameters of an IP bearer service, intra-network routing information, etc.) and forward a plurality of user packets to a packet data network gateway (PGW) and/or Policy Control Enforcement Function (PCEF)5714a, 5714b over an S11 interface.

In alternative embodiments, the PCEF/PGW components 5714a, 5714b may include a PCEF component coupled to a PGW component, a PCEF component included in a PGW component, or a PCEF component configured for performing a plurality of operations typically associated with a PGW component. Since these structures are well known, certain details have been omitted in order to focus on the description of the most relevant features. Information regarding Policy and Charging enforcement function operations may be found in the 3rd Generation Partnership Project Technical Specification Group services and systems aspect, Policy and Charging Control Architecture (3rd Generation Partnership Project Technical Specification Group services systems industries, Policy and Charging Control Architecture) TS 23.203(2011 update of 12/6), the entire contents of which are incorporated herein by reference.

The PCEF/PGW 5714a, 5714b may send signaling information (e.g., control plane information) to a Policy Control Rules Function (PCRF) component 5712a, 5712b (e.g., over the Gx interface). The PCRF components 5712a, 5712b can be responsible for identifying appropriate policy rules for a given communication session. The PCRF components 5712a, 5712b can communicate with an external PCRF component (not shown) over an S9 interface, access a subscriber database, create policy rules, and/or send policy rules to one or more PCEF/PGW components 5714a, 5714b for enforcement.

The PCEF/PGW 5714a, 5714b may receive policy rules from the PCRF component 5712a, 5712b and enforce the received policy rules to control bandwidth, quality of service (QoS), and/or other characteristics of data to be communicated between the serving network and the mobile device 5702. The PCEF/PGW 5714a, 5714b may also coordinate, allocate, add, remove, and/or adjust various resources (e.g., network resources, subscriber resources, etc.) based on the received policy rules.

The core networks 5730a, 5730b may be part of (or include) a dynamic service mediation communication system, such as any of the DSA systems described above. For example, fig. 57 illustrates that each core network 5730a, 5730b can include DSC components 5716a, 5716b suitable for performing DSA operations. The inclusion of DSC components 5716a, 5716b in the core network may enable one or more RAN state components (e.g., one of the components of eNodeB5704a, 5704b or core network 5730a, 5730 b) to send information related to one or more mobile devices and a plurality of associated RANs to the DSCs 5716a, 5716b, which the DSCs 5716a, 5716b may use to make a more situational spectrum arbitration determination (e.g., whether spectrum should be leased, how much spectrum should be shared, etc.).

In the example illustrated in fig. 57, the DSCs 5716a, 5716b are directly connected to the PCRFs 5712a, 5712 b. In various embodiments, the DSC 5722 may be directly or indirectly connected to PCEF/PGW 5714a, 5714b and/or various other components in the core network. In various embodiments, the DSCs 5716a, 5716b may be connected, either directly or indirectly, with one or more enodebs 5704, as shown by direct communication link 5732 in fig. 57.

In one embodiment, DSCs 5716a, 5716b may be connected to DPC5720 outside of core networks 5730a, 5730 b. DSCs 5716a, 5716b may be configured with software to communicate data regarding the availability of spectrum resources to DPC5720 using capacity policy criteria. The data communicated to DPC5720 may include data relating to the current excess capacity and the expected future capacity of the network or subnetwork, such as data received from one or more enodebs 5704a, 5704 b.

In various embodiments, spectrum and other resources may be allocated from a first network 5730a (i.e., a lessor network) to a second network 5730b (i.e., a tenant network) as part of a dynamic spectrum arbitration operation. The mobile device 5702 may be wirelessly connected to an eNodeB5704b corresponding to the second network 5730b through a connection 5724. The mobile device 5702 may be handed off to another eNodeB5704a associated with the second network 5730a in order to use the allocated spectrum resources or radio resources. As part of the handover procedure, a new RAN connection 5722 to another eNodeB5704a may be established and the RAN connection 5724 to the original eNodeB5704b may be terminated. Alternatively, in further embodiments, the RAN connection 5724 to the original eNodeB5704b may not be terminated and the mobile device 5702 may maintain multiple RAN connections.

In various embodiments, mobile device 5702, which has been handed off to another network, may maintain the data connection managed by the original anchor network. For example, the mobile device 5702 may maintain data flow to the PGW 5714b after being handed off to another eNodeB5704 a.

Various embodiments may include multiple additional connections to accommodate data flow between the mobile device 5702 and the first network, such as a connection 5728 from the second eNodeB5704a to the SGW 5708b in the first network, or a connection 5726 from the SGW 5708a of the second network to the PGW 5714b in the first network as shown in fig. 57.

Various embodiment DSA systems may be configured for using any of a number of different resource allocation schemes, algorithms and/or methods for accurate and efficient resource allocation. Such schemes, algorithms and/or methods may be performed by one or more servers or network components of any of the DSA systems described above (such as those discussed with reference to fig. 9 and 57). Each independent resource allocation scheme/method may support pure spectrum allocation, radio resource sharing or some other network resource sharing operation, or otherwise enable suitable and efficient resource allocation by DSA systems. DSA systems may be configured for using a single resource allocation scheme or a combination of multiple resource allocation schemes.

Generally, allocating resources in DSA systems requires some degree of coordination between the lessee wireless network (i.e., the network requests, purchases, or receives the allocated resources) and the lessor wireless network (i.e., the network provides, sells, or allocates resources). Further, allocating resources may also require coordinating the temporary allocation, reallocation, or sharing of resources among wireless networks to ensure that those resources that become available are properly managed. Furthermore, allocating resources may require some coordination between the lessor network operator and the lessee network operator, as well as additional coordination between the DPC components and the host network of the MVNO in the case of a Mobile Virtual Network Operator (MVNO).

To facilitate such coordinated operations, various embodiments include a DSC component/server configured to coordinate resource allocation and associated communications participating in each of a plurality of wireless networks in a DSA system, and a DPC component/server configured to coordinate operation of the DSCs and resource allocation among the wireless networks.

Various embodiments may include DSA systems configured for determining and managing the allocation, transfer, and/or use of resources over a wireless network based on licensed regions, local regions, cell/sector areas, and/or sub-sector cell areas. In one embodiment, allocation, transfer, and/or use of resources may be determined based on additional factors, such as RF bandwidth, traffic to be consumed (Mbit), geographic boundaries (e.g., where to request resources, etc.), time (e.g., when to request resources, etc.), duration (e.g., a period of time during which to request use of resources, etc.), and other similar parameters or characteristics. In various embodiments, the management, allocation, transfer, and/or use of resources over the wireless network based on the above factors may be accomplished in the DSC component, in the DSP component, or by a combination of the DSC component and the DSP component.

Various embodiments provide a number of benefits and advantages over existing solutions, including coordinating operations and interactions between different wireless networks to enable efficient allocation and transfer of resources. That is, the ability to efficiently allocate resources may not result in efficient use of resources by a tenant network without coordinating such operations/interactions. In addition, the subscriber experience may be diminished without coordinating the interaction between wireless networks, either because new resources that become available cannot be accessed or because their services/sessions are terminated due to congestion issues that cause the layered priority assignment process to be invoked, or resources being consumed. A hierarchical priority assignment process is discussed in detail in U.S. patent application No. 12/273,146 entitled "Method and System for Providing hierarchical priority Access to Communication Network Resources", filed on 18.11.2008, and U.S. patent application No. 13/664,819 entitled "Method and System for Providing hierarchical Access to Communication Network Resources", filed on 31.10.2012, both of which are incorporated herein by reference in their entirety.

Fig. 58 illustrates the information flow and functional components in an embodiment DSA system 5800 that includes a DPC component 5802 configured for coordinating the operation of two or more DSC components/servers 5804a, 5804 b.

Similar to the individual DSA systems discussed above with reference to fig. 9 and 57, DSA system 5800 may include a lessor wireless network 5806 and a tenant wireless network 5808. The lessor wireless network 5806 may be coupled to a first OMC/NMS component 5810a, which may be coupled to a first DSC component 5804 a. Similarly, a tenant wireless network 5808 may be coupled to a second OMC/NMS component 5810b, which may be coupled to a second DSC 5804 b.

The first DSC module 5804a may be coupled to the second DSC module 5804b either directly and/or through DPC module 5802. DPC component 5802 may be configured to coordinate operations of DSCs 5716a, 5716b and perform other coordination operations, such as sharing network configuration information at the DPC/DSC level to facilitate local or sub-local licensed region dynamic lease operations.

Fig. 59 illustrates functional components in an embodiment DSA system 5900 configured for partitioning a geographic region into a grid-like data structure. The DSA system 5900 may perform an auction/arbitration operation that results in successful bidders for a geographic area (which may include two entire networks, an area, multiple cell sites, multiple sectors, multiple sub-sectors, etc.) and divide the geographic area into a table (or grid) with allowed areas that include multiple cells, zones, rows, and/or columns so that resources may be allocated more quickly and efficiently.

In the example illustrated in fig. 59, the grid includes a permitted region 5902 having a first area (area 1)5904 and a second area (area 2) 5906. Each of the first area 5904 and the second area 5906 may be divided into one or more cell site classes 5910, each cell site class 5910 may include one or more sector or cell grid areas 5908, and each sector or cell grid area 5908 may include one or more sub-segment cell grid areas 5910. In the illustrated example, the first region 5904 includes a cell site level region 5912, and the second region 5906 includes a sector/cell grid region 5908 and a sub-segment cell grid region 5910.

The DSA system 5900 may perform an auction/arbitration operation that results in successful bidders for a geographic area. A successful bidder may want to take advantage of those resources won in the arbitration process and/or move a designated subscriber to a lessor network. Similarly, when allocated resources are consumed or a back-off procedure has been initiated, the DSA system 5900 may be required to hand off the subscriber to the tenant's network or to another wireless network for service/session continuity. In various embodiments, these and other operations may be accomplished by a DSA system 5900 that divides those relevant geographic regions into a grid-like data structure and uses the grid-like data structure to allocate, deallocate, and reallocate resources to various networks.

DSA systems may need information adapted to identify the current location of a tenant subscriber and which cell sites/sectors the subscriber is allowed to enter or leave in order to hand the subscriber in or out of the tenant's network. However, the location of such sites/sectors may not always be the same for both the lessee network and the lessor network. By dividing the geographic region into a grid and using the grid to allocate resources to various wireless networks, various embodiment DSA systems can hand subscribers into or out of a lessor network even when the locations of these cell sites/sectors are not the same in both the lessee network and the lessor network.

Fig. 60 demonstrates that the location of the cell towers or cell sites (i.e., site towers 6002a-c, 6006) in the tenant network can be different from the location of the cell sites/sectors (i.e., site towers 6004a-c, 6006) of the tenant network. When such sites/sectors are not collocated, the decision as to which sites/sectors a particular UE is handed over to is not determinable from the PLMN neighbor list generated by the subscriber unit. Further, even when such sites/sectors are collocated, their particular configuration may not result in the same coverage area or other performance criteria. Various embodiments overcome these and other limitations by generating and using a grid-like data structure to allocate, deallocate, reallocate resources to various networks. In one embodiment, a particular region may be won during bidding and used by the DSA system to interpret coverage and geographic area when transferring or transferring subscribers or resources to a different wireless network.

When the tenant component is a successful bidder in a DSA auction/bidding process, the corresponding lessor network can allocate available resources (such as RF bandwidth resources and traffic to be consumed (Mbit)) to the tenant. In one embodiment, these resources may be further defined in the lessor network by geographic boundaries (e.g., where they are requested), licensed regions, local regions, cell/sector regions, sub-sector cell regions, time (e.g., when these resources become available), and duration (e.g., how long the resources are available).

Figure 61 illustrates an embodiment DSA method 6100 for allocating resources in a DSA system. The operations of DSA method 6100 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example illustrated in fig. 61, the DSA method 6100 is performed in a DSA system that includes a tenant bidder network 6102, a Dynamic Policy Controller (DPC) component 6104, and a tenant Dynamic Spectrum Controller (DSC) component 6106. The tenant bidder network 6102 includes a tenant DSC component 6108 and a bidder component 6110.

In operation 6112 of the method 6100, the bidder component 6110 may send a resource request message to a Dynamic Policy Controller (DPC) component 6104 to determine if there are resources available in the lessor network that are compatible with the tenant network 6102. In operation 6114, a Dynamic Policy Controller (DPC) component 6104 may send a resource query message to the lessor DSC component 6106 to query the availability and/or compatibility of resources in the respective lessor network. In operation 6116, the lessor DSC component 6106 may send a resource query response to a Dynamic Policy Controller (DPC) component 6104 that includes information sufficient to identify resources in the lessor network that are compatible with the lessee network 6102 and available for use by the lessee network 6102. In operation 6118, a Dynamic Policy Controller (DPC) component 6104 may send a communication message to bidder component 6110 indicating that there are resources available for use by tenant network 6102.

In operation 6120, bidder component 6110 may send a resource request message to Dynamic Policy Controller (DPC) component 6104 requesting one or more of those resources identified as available for use by tenant network 6102. In operation 6122, a Dynamic Policy Controller (DPC) component 6104 may send a resource reservation request message to the lessor DSC component 6106. In operation 6124, the lessor DSC component 6106 may reserve those resources requested by the bidder component 6110 and send a communication message to the Dynamic Policy Controller (DPC)6104 indicating that these resources have been reserved.

In operation 6126, bidder component 6110 may send a resource bid to Dynamic Policy Controller (DPC) 6104. In operation 6128, a Dynamic Policy Controller (DPC) component 6104 may send a bid acceptance message.

In one embodiment, operations 6126 and 6128 may be performed as part of a resource auction performed in DSA system 6100. That is, as discussed above with reference to fig. 9 and 10, in one embodiment, the DSA system may automatically determine an amount of Radio Frequency (RF) spectrum resources available within the lessor network and auction for the available RF spectrum resources among multiple network operators/providers. DSA systems may select the tenant network 6102 to be able to receive available RF spectrum resources, which allows the lessor network to efficiently utilize excess RF spectrum resources (which might otherwise not be used for a significant period of time) by leasing the excess RF spectrum resources to the highest bidder (on a temporary or permanent basis), and allows the tenant network 6102 to lease RF spectrum resources on competitive market rates and/or when needed.

In operation 6130, a Dynamic Policy Controller (DPC) component 6104 may send a communication message to the lessor DSC component 6106 indicating that a bid from the bidder component 6110 has been accepted and instructing the lessor DSC 6106 to allocate reserved resources to the lessee network 6102. In operation 6132, the lessor DSC component 6106 may send a communication message to the Dynamic Policy Controller (DPC)6104 indicating that these resources have been allocated. In operation 6134, a Dynamic Policy Controller (DPC) component 6104 may send a communication message to bidder component 6110 indicating that the resources have been allocated. In operation 6136, a Dynamic Policy Controller (DPC) component 6104 may send a communication to the tenant DSC6108 indicating that these resources have been allocated and that the tenant DSC may begin using the allocated resources.

In operations 6112-6136, DSA information may be shared between the lessor DSC 6106 and DPC 6104, and between the lessee DSC6108 and DPC 6104, to facilitate implementing successful arbitrated bidding (e.g., in operations 6126-6128). In one embodiment, the lessee DSC 6106 and lessee DSC6108 may share information related to home network configuration and visited network configuration through DPC 6104. Such information may include the location of cell sites in the bidding area, knowledge of network congestion or reduced capacity of these networks, the existence of back-off procedures for potential target cell sites in the lessor network, and the like.

In block 6138, the requested resource has been allocated or otherwise made available for use by tenant network 6102. To utilize the allocated resources, the tenant network 6102 may initiate and handover individual devices (e.g., multiple UEs) into the tenant network. The tenant network 6102 may also perform additional operations to ensure proper traffic offload and maximum utilization of the lessor's radio resources, including network sharing operations.

Wherein DSA information is shared between the lessee DSC and DPC and between the lessee DSC and DPC to facilitate achieving a successful arbitrated bid. In particular, renters and lessees DSCs need to share information through the DPC relating to the home network and visited network configurations including the location of cell sites in the bidding area and knowledge of any congestion (reduced capacity) or the existence of back-off procedures for possible target cell sites in the renter's network.

In order for a lessee to utilize the resources of the lessor that have become available, a successful lessee needs to be able to call to and switch to the lessor network after a successful bid to ensure that the lessee makes optimal use of traffic offload and maximum utilization of the lessor's radio resources.

However, network sharing has limitations in terms of traffic control (handover in, handover out, and origination for non-primary users), access to UE devices, and the ability to utilize the primary wireless network. To successfully conduct the arbitration procedure and facilitate the lessee UEs to utilize lessor network specific functions for DSC/DPC in the DSA procedure to be defined.

The DSC may function to provide local command and control of the bidding and arbitration process. The role of the DPC may be to provide strategic guidance to the DSC as well as to facilitate coordination between individual DSCs. This may be accomplished by using a cross-mapping of network coverage areas or cell site locations to each other. In other words, the DSC of a lessee may be configured to obtain the location of the lessor's cell site involved in the bidding process so that it may originate calls or hand-off to the lessor's cell site. More specifically, the tenant network and DSCs in the tenant network may be configured to communicate with each other through the DPC to select the most appropriate cell site for the tenant UE to utilize when transitioning between these networks. This is important for a number of reasons, such as UEs are typically configured to stay on the primary network unless they are instructed to change networks.

In various embodiments, the DSC component may be configured to provide local command and control of bidding and arbitration processes, and the DPC component may be configured to provide policy guidance to the DSC and facilitate coordination among multiple DSCs of various wireless networks included in the DSA system. In one embodiment, this may be accomplished by mapping network coverage areas or cell site locations across from each other (e.g., by a grid-like structure) so that the DSC of the tenant network may obtain location information about the cell sites of the lessors involved in the bidding process so that the DSC may initiate or handover to the lessor's cell site.

In one embodiment, the tenant DSC6108 may communicate with the tenant DSC6108 through the DPC 6104 to select the most appropriate cell site for the tenant UE to utilize when transitioning between the two networks.

In one embodiment, a tenant DSC may be configured to provide the necessary communications through a tenant network, instructing a UE or a group of specific UEs from the tenant network to utilize the tenant network in a specific geographic region.

In one embodiment, the cross-mapping of network information may be controlled by DPC/DSC configuration, which may ensure that tenant UEs have been identified by tenants as being allowed to utilize those resources won in the DSA auction/arbitration process. With such geographical boundary regions, not all tenant UEs that are able to utilize these tenant resources may utilize resources in the correct geographical region. For example, a tenant UE may be located in a region that is not within the geographic boundaries of a bidding region. Thus, the location of the lessee UE along with knowledge of where the geographic boundaries of the bidding area in conjunction with the location of the lessor cell site may be needed.

In one embodiment, a tenant DSC may be configured for determining where a plurality of UEs of a tenant are located in a tenant network and determining whether the located UEs are valid candidates for utilizing the allocated resources. The reverse process may be performed when a tenant resource allocation has been exhausted, when a tenant UE utilizing a tenant network exits a geographic area where tenant resources are allocated, or when a back-off process has been initiated that requires a switch to a tenant network.

In one embodiment, the cross-mapping of network information may be controlled by the DPC/DSC configuration to ensure that tenant UEs have been identified by the tenant as being allowed to utilize those resources allocated.

Fig. 62-64 are illustrations of two lessee UEs 6202, 6204 eligible for handover to a lessor network, in accordance with various embodiments. In the example illustrated in fig. 62, a first UE6202 is connected to tenant cell 16206 and a second UE 6204 is connected to tenant cell 26208, all of which are outside of a bidding region 6220 won by bidder components associated with the tenant network.

In the example illustrated in fig. 63, the first UE6202 is inside the bidding region 6220 and still connected to tenant cell 16206. The second UE 6204 is connected to tenant cell 26208. Since the locations of the first UE6202 and the second UE 6204 are known relative to the winning bidding area and those renter network cell sites, the first UE6202 may be instructed to begin utilizing those resources won during the bidding process.

In the example shown in fig. 64, the first UE6202 is now connected to a lessor cell 26210, both of which are inside a bidding region 6220 won by a bidder component associated with the lessee network. That is, the first UE6202 is now using those resources of the lessor network won from a successful bid, while the second UE 6204 is not, as it has not yet entered the geographic boundary of the successful bidding region 6220.

When the lessee has consumed those resources purchased from the lessor network, the UE may be transferred back to the lessee network. Further, the system may be configured for handing over the UE back to the tenant network if the system determines that the UE needs to be handed over back to the tenant network during a back-off procedure for traffic shedding.

Fig. 65A and 65B illustrate the order in which the first UE6202 utilizes the lessor network (fig. 65A), and either because of exhaustion of secure resources or because of a back-off process, the UE6202 sends resources back to the lessee network by establishing a connection to the lessee cell 16206 while still inside the bidding area 6220 won by the bidder component associated with the lessee network.

Fig. 66A-66C illustrate the order in which the first UE6202 moves to a region outside of the geographic bidding region 6220, and it is desirable to handover UE6202 back to the tenant network to ensure that the user experience is maintained. Fig. 66A shows a first UE6202 within a geographic region 6220 of a bidding area. Fig. 66B shows that the first UE6202 has left the geographic bidding region 6220 and is about to be handed back to the tenant network. Fig. 66C shows that the first UE6202 has been successfully handed over back to the tenant network.

When a backoff condition is detected and/or a backoff operation is performed, the location of the lessee UE may be known and shared with the lessee DSC component. The lessor DSC component may determine alternative lessor cell sites to which the UE may handover as part of the backoff operation. The lessor DSC component may also predict traffic conditions for the enodebs experiencing problems and consider including or excluding eNodeB, traffic trends, and historical information in their decisions. The lessor DSC component may also determine whether those neighboring enodebs are about to enter congestion based on similar traffic trends.

When a tenant UE needs to be handed over to a tenant network, the processor of the UE and/or one or more servers in the DSA system perform one or more handover operations. The leaser DSC component may be configured for selecting which UEs are to be transferred when performing handover operations as part of backoff as backoff between networks experiencing congestion and/or when the network performs traffic drop operations. In one embodiment, the DSC may select multiple UEs for transfer by combining with a DPC component that can collect information for all networks in the system in advance. The DSC of the target system may also be notified of the request for a backoff handover and may determine which eNodeB is closest to selecting using the presence server.

In one embodiment, the UE may be configured to inform the DPC (e.g., via the eNodeB and MME) which station is the best alternative for backoff/handover, and this information may be communicated to the lessor DSC, DPC, and/or tenant DSC as additional information that may be used as part of the backoff/handover operation.

In one embodiment, a lessor and/or lessee DSC may be configured such that selecting an eNodeB for handover operations is based on a variety of factors, including bidding area conditions, traffic trends, and back-off conditions.

Fig. 67 illustrates an embodiment DSA method 6700 for handing over a User Equipment (UE) device connected to a lessor network back to a lessee network in the presence of network congestion or other similar situations. The operations of DSA method 6700 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example illustrated in fig. 67, the DSA method 6700 may be performed in a DSA system that includes a tenant wireless network component 6702, a tenant Dynamic Spectrum Controller (DSC) component 6704, a Dynamic Policy Controller (DPC) component 6706, a tenant DSC 6708, a tenant wireless network component 6710, and a tenant UE 6712.

In operation 6714, the lessor network may allocate resources for bidding through the lessor DSC component 6708 and/or the lessor wireless network component 6710. In operations 6716 through 6722, the DSA system may perform any DSA operations discussed in this application to determine whether a tenant UE6712 is allowed to access or use the allocated resources in the tenant network.

In operation 6724, the lessee UE6712 can attach to those resources (e.g., RF resources) allocated in the lessor network. In operation 6726, tenant UE6712 establishes an active session. In operation 6728, the lessor wireless network component 6710 may detect congestion.

In operation 6730, the lessor wireless network component 6710 may initiate a backoff process by sending a communication message to the lessor DSC component 6708 instructing the lessor DSC component to request a backoff for use of the allocated resource. In one embodiment, the communication message may include the location of tenant UE 6712. In operation 6732, the lessor DSC component 6708 may send a communication message to the DPC component 6706 instructing the DPC component to request a backoff for use of the allocated resource. In operation 6734, the DPC 6706 may send a communication message to the tenant DSC component 6704 instructing the tenant DSC component to request a back off for use of the allocated resource. In one embodiment, the communication message may include information identifying the location of tenant UE 6712.

In one embodiment, as part of operations 6732 and 6734, the tenant DSC component 6704 and/or the tenant DSC component 6708 may determine an alternative cell site to which the tenant UE6712 may switch as part of a backoff operation. The DSCs 6704, 6702 may also predict traffic conditions for the cell tower, base station, or eNodeB experiencing the problem and consider in its decision to include or exclude cell tower/base station/eNodeB, traffic trends, and historical information. In one embodiment, the DSC components 6704, 6708 may also determine whether a plurality of neighboring enodebs are congested or are about to experience observed congestion and detected traffic trends.

In operation 6736, the lessor wireless network component 6710 may send a UE handover request to the lessor DSC component 6708. In operation 6738, the lessor DSC component 6708 may forward the UE handover request to the DPC component 6706. In operation 6740, the DPC component 6706 may send a UE handover request to the tenant DSC component 6704.

In operation 6742, the tenant wireless network component 6702 and the tenant DSC component 6704 may communicate information suitable for determining optimal procedures for completing handover and/or backoff operations, including the transmission and reception of information regarding resource requests and being allocated.

In operation 6744, the tenant DSC component 6704 may send a UE handover response message to the DPC component 6706. In operation 6746, the DPC component 6706 may send a UE handover response message to the lessor DSC component 6708. In operation 6748, the lessor DSC component 6708 may identify and locate the telecommunication devices and resources needed to complete the handover and send the UE target handover information to the lessor wireless network component 6710. In operation 6750, the lessee wireless network component 6710 may send a UE handover command with target information to the lessee UE 6712.

In operation 6752, the tenant UE6712 may retune and reconnect to the telecommunication devices and those resources identified by the target information included in the target handover command. In operation 6754, tenant UE6712 may reestablish an active session to tenant network and/or tenant wireless network component 6702.

Fig. 68 illustrates an embodiment DSA method 6800 for handing over resources back to a tenant network when usage or lease of usage of allocated resources has been exhausted. The operations of the DSA method 6800 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example illustrated in fig. 68, the DSA method 6800 may be performed in a DSA system that includes a tenant wireless network component 6702, a tenant Dynamic Spectrum Controller (DSC) component 6704, a Dynamic Policy Controller (DPC) component 6706, a tenant DSC 6708, a tenant wireless network component 6710, and a tenant UE 6712.

Operations 6714 through 6724 of the DSA method 6800 are the same as those discussed above with reference to fig. 67. That is, the lessor network may allocate resources for bidding, the DSA system may perform any or all of those DSA operations discussed in this application to determine whether the lessee UE6712 is allowed to access or use resources in the lessor network, and the lessee UE6712 may attach to the allocated resources in response to the DSA system determining that the lessee UE6712 is to be allowed to access or use the allocated resources in the lessor network. In operation 6802, the tenant UE6712 may establish a secondary UE active session with a component in the tenant wireless network 6710.

In operation 6804, the lessor DSC component 6708 may determine those resources used by the lessee network that have been consumed or exhausted and are to be switched back for use or reallocation by the lessor network. In operation 6806, the lessee DSC component 6708 may send a communication message to the DPC component 6706 indicating that those resources in the lessee network have been consumed/depleted, that the lessee UE6712 is to be dropped, and/or that the lessee UE6712 is to be switched back to the lessee network. In operation 6808, the DPC component 6706 may notify the tenant DSC component 6704 that these resources have been consumed or exhausted and that the tenant UE6712 is about to be dropped by and/or switched back to the tenant network.

In operation 6810, the lessor DSC component 6708 may send a UE handover request message to the DPC component 6706. In operation 6812, the DPC component 6706 may send a UE handover request message to the tenant DSC component 6704. In operation 6814, the tenant wireless network component 6702 and the tenant DSC component 6704 may communicate information suitable for determining an optimal procedure for switching resources used by the tenant UE6712 back to the tenant wireless network 6710, which may include communicating information regarding resource requests and positive allocations.

In operation 6816, the tenant DSC component 6704 may send a UE handover response message to the DPC component 6706. In operation 6818, the DPC component 6706 may send a UE handover response message to the lessor DSC component 6708. In operation 6820, the lessor DSC component 6708 may identify and locate the telecommunication devices and resources needed to complete the handover and send the UE target handover information to the lessor wireless network component 6710. In operation 6822, the lessee wireless network component 6710 may send a UE handover command with target information to the lessee UE 6712.

In operation 6824, the tenant UE6712 may retune and reconnect to the telecommunication devices and those resources identified by the target information included in the target handover command. In operation 6826, the tenant UE6712 may reestablish an active session to a component in the tenant wireless network 6702.

Fig. 69 illustrates an embodiment DSA method 6900 for returning resources to a lessor network when a lessee UE using lessor network resources is no longer located within a geographic area defined during bidding. The operations of the DSA method 6900 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example illustrated in fig. 69, the DSA method 6900 may be performed in a DSA system that includes a tenant wireless network component 6702, a tenant Dynamic Spectrum Controller (DSC) component 6704, a Dynamic Policy Controller (DPC) component 6706, a tenant DSC 6708, a tenant wireless network component 6710, and a tenant UE 6712.

Operations 6714 through 6724 and 6802 of the DSA method 6900 are the same as those discussed above with reference to fig. 67 and 68. That is, the lessor network may allocate resources for bidding, the DSA system may perform any or all of those DSA operations discussed in this application to determine whether the lessee UE6712 is allowed to access or use resources in the lessor network, and the lessee UE6712 may attach to the allocated resources and establish a secondary active session in response to the DSA system determining that the lessee UE6712 is to be allowed to access or use resources in the lessor network.

In operation 6920, the lessee DSC component 6708 may determine that the lessee UE6712 has been moved to a location that is outside the geographic boundaries defined in the bidding process, such as a bidding area won by the lessee network during resource arbitration or bidding or auction operations performed by the DSA system.

In operation 6902, the lessor DSC component 6708 may send a UE handover request to the DPC component 6706. In operation 6904, the DPC component 6706 may send a UE handover request to the tenant DSC component 6704. In operation 6906, the tenant wireless network component 6702 and the tenant DSC component 6704 may communicate information suitable for determining an optimal procedure for switching the tenant UE6712, which may include communicating information regarding resource requests and being allocated.

In operation 6908, tenant DSC component 6704 may send a UE handover response message to DPC component 6706. In operation 6910, the DPC component 6706 may send a UE handover response message to the lessor DSC component 6708. In operation 6912, the lessor DSC component 6708 may identify and locate the telecommunication devices and resources needed to complete the handover and send the UE target handover information to the lessor wireless network component 6710. In operation 6914, the lessee wireless network component 6710 may send a UE handover command with target information to the lessee UE 6712.

In operation 6916, the tenant UE6712 may retune and reconnect to the telecommunication devices and those resources identified by the target information included within the target handover command. In operation 6918, the lessee UE6712 may reestablish an active session to a component in the lessor wireless network 6702.

Fig. 70 illustrates an embodiment DSA method 7000 for a tenant UE to camp on a cell site and listen for instructions when the UE is located within the geographic area won by a successful bid but has not yet requested to start a session. The operations of the DSA method 7000 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example illustrated in fig. 70, the DSA method 7000 may be performed in a DSA system that includes a tenant wireless network component 6702, a tenant Dynamic Spectrum Controller (DSC) component 6704, a Dynamic Policy Controller (DPC) component 6706, a tenant DSC 6708, a tenant wireless network component 6710, and a tenant UE 6712.

Operations 6714 through 6722 of the DSA method 7000 are the same as those discussed above with reference to fig. 67. That is, the lessor network may allocate resources for bidding, and the DSA system may perform any or all of those DSA operations discussed in this application to determine whether the lessee UE6712 is to be allowed to access or use resources in the lessor network.

The DSA method 7000 allows the UE to camp on a cell site while listening for instructions from the network, which may involve redirecting to another site during times of congestion, scanning for any number of functions instructed by other cells or networks. To further improve the effectiveness of DSA systems, DSA method 7000 also allows tenant UEs to camp on the tenant network.

In operation 7002 of the DSA method 7000, the tenant UE6712 may attach to the tenant wireless network 6702. In operation 7004, the lessee UE6712 may enter a lessor bidding geographic boundary, such as the bidding area 6220 discussed with reference to fig. 62-66C. In operation 7006, the tenant DSC component 6704 may send a communication message to the lessor network requesting that the tenant UE6712 be redirected to the lessor network. In operation 7008, the lessee wireless network component 6702 may send a lessee UE redirect command to the lessee UE 6712. In operation 7010, tenant UE6712 may retune and reconnect to the telecommunication devices and those resources identified in the tenant UE redirect command. In operation 7010, the lessee UE6712 may attach to the lessor wireless network 6710 and establish an active session.

In operation 7012, the lessor wireless network 6710 may send a communication message to the DPC component 6706 informing the DPC component that the lessee UE6712 has attached to the lessor wireless network 6710. In operation 7014, the DPC component 6706 may send a communication message to the tenant DSC component 6704 informing the tenant DSC component that the tenant UE6712 has attached to the tenant wireless network 6710. In operation 7020, the tenant DSC component 6704 may update HLR/HSS information for tenant UE6712 in the tenant wireless network 6702 and perform other similar operations.

Fig. 71A shows an embodiment DSA method 7100 for a tenant UE requesting to start a session with a lessor network when the UE is located in a geographic region won by a successful bid but has not been instructed to camp on the lessor network. DSA method 7100 allows UEs to initially attempt and initiate calls on a tenant network before instructing the tenant UE to be redirected to the tenant network to initiate a session. The operations of DSA method 7100 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example shown in fig. 71A, the DSA method 7100 may be performed in a DSA system that includes a tenant wireless network component 6702, a tenant Dynamic Spectrum Controller (DSC) component 6704, a Dynamic Policy Controller (DPC) component 6706, a tenant DSC 6708, a tenant wireless network component 6710, and a tenant UE 6712.

Operations 6714 through 6722 and operation 7002 of the DSA method 7100 are the same as those discussed above with reference to fig. 67 and 70. That is, the lessor network may allocate resources for bidding, the DSA system may perform any or all of those DSA operations discussed in this application to determine whether tenant UE6712 is to be allowed to access or use resources in the lessor network, and tenant UE6712 may attach to tenant wireless network 6702.

In operation 7102, the tenant DSC 6704 may determine that the tenant UE6712 has entered a lessor bidding geographic boundary, such as the bidding region 6220 discussed with reference to fig. 62-66C. In operation 7104, the tenant UE6712 may send a request message requesting establishment of an active session to the tenant wireless network. In operation 7106, the tenant wireless network 6702 may mark the tenant UE6712 for transfer to a tenant network. In operation 7108, the lessee wireless network 6702 may send a UE redirection request message to the lessee DSC 6704. In operation 7110, the tenant DSC 6704 may send a communication message to the tenant wireless network component 6702 authorizing the tenant UE to be redirected to the tenant wireless network 6710. In operation 7112, the lessee wireless network component 6702 may send a lessee UE redirect command to the lessee UE 6712.

In operation 7114, the tenant UE6712 may retune and reconnect to the telecommunication devices and those resources identified in the tenant UE redirect command. In operation 7116, a tenant UE6712 may attach to a tenant wireless network 6710. In operation 7118, the lessee UE6712 may reestablish an active session with the lessor wireless network 6710.

Fig. 71B illustrates an embodiment DSA method 7150 for handing over sessions such that a tenant UE may continue a session with a lessor network when it is determined that the tenant UE has an active session on the tenant network and has moved into a geographic region won by a successful bid. DSA method 7150 allows the UE to continue its session using the lessor network, thereby freeing up lessee resources. The operations of DSA method 7150 may be performed by one or more server processors in one or more network components included in any of the DSA systems discussed above. In the example shown in fig. 71B, DSA method 7150 may be performed in a DSA system that includes a tenant wireless network component 6702, a tenant Dynamic Spectrum Controller (DSC) component 6704, a Dynamic Policy Controller (DPC) component 6706, a tenant DSC 6708, a tenant wireless network component 6710, and a tenant UE 6712.

Operations 6714 through 6722 and operation 7002 of the DSA method 7150 are the same as those discussed above with reference to fig. 67 and 70. That is, the lessor network may allocate resources for bidding, the DSA system may perform any or all of those DSA operations discussed in this application to determine whether tenant UE6712 is to be allowed to access or use resources in the lessor network, and tenant UE6712 may attach to tenant wireless network 6702.

In operation 7151, the tenant DSC component 6704 may determine that the tenant UE6712 has been flagged and has entered a lessor bidding geographic boundary, such as the bidding region 6220 discussed with reference to fig. 62-66C.

In operation 7152, the tenant DSC component 6704 may send a UE Handover (HO) request message to the DPC component 6706. In operation 7154, the DPC component 6706 may send a UE handover request message to the lessor DSC component 6708. In operation 7156, the lessor DSC component 6708 may send a UE handover request message to a component in the lessor wireless network 6710.

In operation 7158, the lessor wireless network component 6710 may send a UE Handover (HO) request acknowledgement message to the lessor DSC component 6708. In operation 7160, the lessor DSC component 6708 may send a UE Handover (HO) request acknowledgement message to the DPC component 6706. In operation 7162, the DPC component 6706 may send a UE Handover (HO) request confirm message to the tenant DSC component 6704.

In operation 7164, the tenant DSC component 6704 may send a UE Handover (HO) command to the tenant wireless network component 6702. In operation 7166, the tenant wireless network component 6702 may send a UE HO command instructing the tenant UE6712 to handover to a cell site of the tenant network. In operation 7170, the tenant UE6712 may retune and reconnect to the telecommunication devices and those resources identified in the UE HO command. In operation 7170, the lessee UE6712 may attach to the lessor wireless network 6710 and/or establish an active session with the lessor wireless network 6710.

In operations 7172 through 7178, those components in the DSA system may communicate a UE HO complete message to the tenant wireless network 6702, which may update HLR and/or HSS information for the UE in the tenant wireless network in operation 7180.

Various embodiments may include Dynamic Spectrum Arbitrage (DSA) methods including determining, in a communication server, that telecommunications resources of a first communication network are available for allocation; broadcasting a first communication signal informing a plurality of communication networks that the telecommunications resource is available for allocation and a geographical area associated with the telecommunications resource; allocating the telecommunications resources of the first communication network for access and use by a second communication network of the plurality of communication networks; broadcasting a second communication signal informing the second communication network that use of the allocated telecommunication resource may start in the geographical area; and recording a transaction in a transaction database, the transaction database identifying the telecommunications resource as allocated for use by the second communications network.

In one embodiment, a DSA method may include receiving resource configuration information related to a resource allocation scheme from a first dynamic spectrum controller server in the first communication network; and sending the resource configuration information to a second dynamic spectrum controller server in the second communication network. In one embodiment, a DSA method may include receiving coordination information related to availability of the telecommunications resource from a first dynamic spectrum controller server in the first communication network based on a plurality of geographic regions; and sending the coordination configuration information to a second dynamic spectrum controller server in the second communication network.

In a further embodiment, the DSA method may comprise negotiating a resource lease scheme between the first communication network and the second communication network for the use of the telecommunication resource; and coordinating handover of the mobile device between the first communication network and the second communication network based on the plurality of geographic boundaries defined in the resource leasing scheme. In a further embodiment, the DSA method may comprise determining the validity of a subscriber device of the second communication network based on the proximity of the subscriber device to the geographical area and information included in the resource leasing scheme. In a further embodiment, the DSA method may include instructing a subscriber device of the second communication network to establish a communication link to a resource in the first communication network based on the proximity of the subscriber device to the geographic area and the terms of the resource leasing scheme.

In a further embodiment, the DSA method may include determining the validity of a subscriber device of the second communication network based on the proximity of the subscriber device to the geographic area and a level of quality of service available to the subscriber device. In a further embodiment, the DSA method may include instructing a subscriber device of the second communication network to establish a communication link to a resource in the first communication network based on the proximity of the subscriber to the geographic area and the level of quality of service available to the subscriber device. In a further embodiment, the DSA method may include instructing a subscriber device of the second communication network to modify a network based on a proximity of the subscriber device to the geographic area. In a further embodiment, the DSA method may comprise instructing subscriber devices of the second communication network that are actively connected to the telecommunications resource to change networks.

In a further embodiment, the DSA method may include instructing a subscriber device of the second communication network to actively attach to another resource in the first communication network based on a proximity of the subscriber device to the geographic area using the allocated telecommunications resource.

Various embodiments DSA methods may allow a first network and a second network to share configuration information related to a resource allocation scheme.

Various embodiments DSA methods may allow for the use of leased radio resources based on the physical location of the subscriber device.

Various embodiments DSA methods may allow for the use of leased radio resources based on the expected quality of service.

Various embodiment DSA methods may include coordinating network resources in which a DSC in a first network 1 informs a DSC of a second network of those available resources that it has in a geographic region or resource allocation scheme.

Various embodiment DSA methods may include coordinating network resources in which a DSC in a second network notifies a DSC of a first network of those available resources that it has in a geographic region or resource allocation scheme.

Various embodiment DSA methods may include coordinating handovers between networks based on geographic boundaries defined in a leasing scheme.

Various embodiment DSA methods may include determining the availability of a first network subscriber using resources available in a second network based on the location of the first network subscriber relative to the available resources of the second network and/or based on a resource allocation scheme.

Various embodiment DSA methods may include determining the effectiveness of a first network subscriber using resources available in a second network based on the location of the first network subscriber relative to the available resources of the second network and the available quality of service following a resource allocation scheme.

Various embodiment DSA methods may include instructing a subscriber device on a first network to change networks to a second network based on a location of the first network subscriber device relative to resources available on the second network and following a resource allocation scheme.

Various embodiment DSA methods may include instructing a subscriber device on a first network to change a network to a second network based on a location of the network subscriber device relative to available resources on the second network following a resource allocation scheme and available quality of service following the resource allocation scheme.

Various embodiment DSA methods may include instructing a subscriber device on a first network to change networks based on a geographic location of the subscriber device if resources become available in a second network.

Various embodiment DSA methods may include instructing a subscriber device from a first network that is currently using resources on a second network to change networks to the first network or another network based on the location of the first network subscriber device relative to resources available on the first network or another network.

Various embodiment DSA methods may include instructing a subscriber device from a first network that is currently using resources on a second network to change networks to the first network or another network based on a location of the network subscriber device relative to available resources on the first network or the other network that follow a resource allocation scheme, and an available quality of service that follows the resource allocation scheme.

Further embodiments may include a computing device that may include a processor configured with processor-executable instructions to perform operations corresponding to those methods discussed above.

Further embodiments may include computing devices including various means for performing functions corresponding to those of the method operations discussed above.

Further embodiments may include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor to perform operations corresponding to those method operations discussed above.

The various embodiments may be implemented on a variety of mobile computing devices, an example of which is illustrated in fig. 72. In particular, fig. 72 is a system block diagram of a mobile transceiver device in the form of a smart phone/cellular phone 7200 suitable for use with any of the aspects. The cellular telephone 7200 can include a processor 7201 coupled to internal memory 7202, a display 7203, and a speaker 7208. Additionally, the cellular telephone 7200 can include an antenna 7204 for transmitting and receiving electromagnetic radiation that can be connected to a wireless data link and/or cellular telephone transceiver 7205 coupled to the processor 7201. Cellular telephones 7200 also typically include menu selection buttons or toggle switches 7206 for receiving user inputs.

The exemplary cellular telephone 7200 also includes a voice coding/decoding (CODEC) circuit 7213 that digitizes voice received from the microphone into packets suitable for wireless communication and decodes the received voice packets to generate analog signals, which are provided to a speaker 7208 to generate sound. Also, one or more of the processor 7201, wireless transceiver 7205, and CODEC 7213 can include Digital Signal Processor (DSP) circuitry (not separately shown). The cellular telephone 7200 may further include a ZigBee receiver (i.e., an IEEE 802.15.4 receiver) or other similar communication circuitry (e.g., implementing) for low-power short-range communication between wireless devicesOr circuitry of WiFi protocol, etc.).

The above-described embodiments including the spectrum arbitration function can be implemented on a variety of commercially available server devices within a broadcast system, such as server 7300 shown in fig. 73. Such a server 7300 typically includes a processor 7301 connected to volatile memory 7302 and large capacity non-volatile memory (such as a disk drive 7303). The server 7300 may also include a floppy disk drive, Compact Disk (CD) or DVD disk drive 7311 coupled to the processor 7301. The server 7300 may also include a network access port 7306, such as a local area network coupled to other communication system computers and servers, coupled to the processor 7301 for establishing a data connection with the network 7305.

The processors 7201, 7301 may be any programmable microprocessor, or multiple processor chips that can be configured by software instructions (applications) to perform a variety of functions, including the functions of the various aspects described below. In some mobile devices, multiple processors 7301 may be provided, such as one processor dedicated to wireless communication functions and one processor dedicated to running other applications. Typically, software applications may be stored in the internal memory 7202, 7302 before they are accessed and loaded into the processor 7201, 7301. The processors 7201, 7301 may include internal memory sufficient to store the application software instructions. In some servers, processor 7301 may include internal memory sufficient to store the application software instructions. In some receiver devices, the secure memory may be a separate memory chip coupled to the processor 7301. The internal memory 7302 may be volatile or non-volatile memory (e.g., flash memory), or a mixture of both. For purposes of this description, a general reference to memory refers to all memory accessible to processor 7301, including internal memory 7302, removable memory plugged into the device, and memory within processor 7301 itself.

Embodiments include methods for managing, allocating, and arbitrating RF bandwidth as described above. Embodiments also include a communication system capable of implementing the DPC method. Embodiments also include non-transitory computer-readable storage media storing computer-executable instructions for performing the above-described methods.

The foregoing method descriptions and process flow diagrams are provided as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As one of ordinary skill in the art will appreciate, the order of the steps in the foregoing embodiments may be performed in any order. Words such as "thereafter," "then," "next," etc. are not intended to limit the order of the steps; these words are used only to guide the reader through the description of the method. Furthermore, any reference to an element in the singular (e.g., using the articles "a," "an," or "the") should not be construed as limiting the element to the singular.

The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The hardware used to implement the various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DPC), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microprocessor, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DPC and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DPC core, or any other such configuration. Alternatively, some steps or methods may be performed by circuitry that is dedicated to a given function.

In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The method steps or algorithms disclosed herein may be implemented in a processor-executable software module, which may reside on a tangible, non-transitory computer-readable storage medium. Tangible, non-transitory computer-readable storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, non-transitory computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of non-transitory computer-readable media. Furthermore, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a tangible, non-transitory machine-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles disclosed herein.

Claims (20)

1. A Dynamic Spectrum Arbitrage (DSA) method, comprising:

determining in a communications server that a telecommunications resource of a first communications network is available for allocation;

broadcasting a first communication signal informing a plurality of communication networks that the telecommunications resource is available for allocation and a geographical area associated with the telecommunications resource;

negotiating a resource lease scheme between the first and second ones of the plurality of communication networks for use of the telecommunications resource;

coordinating a handover of a mobile device between the first communication network and the second communication network based on geographic boundaries defined in the resource leasing scheme;

allocating the telecommunications resources of the first communication network for access and use by the second communication network;

broadcasting a second communication signal informing the second communication network that use of the allocated telecommunications resource may begin in the geographic area; and

a transaction is recorded in a transaction database that identifies the telecommunications resource as being allocated for use by the second communications network.

2. The DSA method of claim 1, further comprising:

receiving resource allocation information relating to a resource allocation scheme from a first dynamic spectrum controller server in the first communication network; and

sending the resource configuration information to a second dynamic spectrum controller server in the second communication network.

3. The DSA method of claim 1, further comprising:

receiving coordination information relating to availability of the telecommunications resource from a first dynamic spectrum controller server in the first communication network based on a plurality of geographic regions; and

sending the coordination information to a second dynamic spectrum controller server in the second communication network.

4. The DSA method of claim 1, further comprising:

determining the validity of a subscriber device of the second communication network based on the proximity of the subscriber device to the geographic area and information included in the resource leasing scheme.

5. The DSA method of claim 1, further comprising:

instructing a subscriber device of the second communication network to establish a communication link to a component in the first communication network based on the proximity of the subscriber device to the geographic area and the terms included in the resource leasing scheme.

6. The DSA method of claim 1, further comprising:

determining the validity of a subscriber device of the second communication network based on the proximity of the subscriber device to the geographic area and the level of quality of service available to the subscriber device.

7. The DSA method of claim 1, further comprising:

instructing a subscriber device of the second communication network to establish a communication link to a component in the first communication network based on the proximity of the subscriber device to the geographic area and the level of quality of service available to the subscriber device.

8. The DSA method of claim 1, further comprising:

instructing a subscriber device in the second communication network to change networks based on the proximity of the subscriber device to the geographic area.

9. The DSA method of claim 1, further comprising:

instructing a subscriber device of the second communications network that is actively connected to the telecommunications resource to change networks.

10. The DSA method of claim 1, further comprising:

using the allocated telecommunications resource, instructing a subscriber device of the second communication network to attach to another resource in the first communication network based on the proximity of the subscriber device to the geographic area.

11. A communication server for performing dynamic spectrum arbitration of a telecommunications resource, the communication server comprising:

a network communication circuit for communicating with a first communication network and a second communication network;

a memory; and

a processor coupled to the memory and the network communication circuitry, wherein the processor is configured with processor-executable instructions to perform operations comprising:

determining that a telecommunications resource of the first communications network is available for allocation;

broadcasting a first communication signal informing a plurality of communication networks that the telecommunications resource is available for allocation and a geographical area associated with the telecommunications resource;

negotiating a resource lease scheme between the first communication network and the second communication network for the use of the telecommunications resource;

coordinating a handover of a mobile device between the first communication network and the second communication network based on geographic boundaries defined in the resource leasing scheme;

allocating the telecommunications resources of the first communication network for access and use by the second communication network;

broadcasting a second communication signal informing the second communication network that use of the allocated telecommunications resource may begin in the geographic area; and

a transaction is recorded in a transaction database that identifies the telecommunications resource as being allocated for use by the second communications network.

12. The communication server of claim 11, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

receiving resource allocation information relating to a resource allocation scheme from a first dynamic spectrum controller server in the first communication network; and

sending the resource configuration information to a second dynamic spectrum controller server in the second communication network.

13. The communication server of claim 11, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

receiving coordination information relating to availability of the telecommunications resource from a first dynamic spectrum controller server in the first communication network based on a plurality of geographic regions; and

sending the coordination information to a second dynamic spectrum controller server in the second communication network.

14. The communication server of claim 11, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

determining the validity of a subscriber device of the second communication network based on the proximity of the subscriber device to the geographic area and information included in the resource leasing scheme.

15. The communication server of claim 11, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

instructing a subscriber device of the second communication network to establish a communication link to a component in the first communication network based on the proximity of the subscriber device to the geographic area and the terms included in the resource leasing scheme.

16. A Dynamic Spectrum Arbitrage (DSA) apparatus, comprising:

means for determining in the communications server that a telecommunications resource of a first communications network is available for allocation;

means for broadcasting a first communication signal informing a plurality of communication networks that the telecommunications resource is available for allocation and a geographical area associated with the telecommunications resource;

means for negotiating a resource lease scheme between the first communication network and a second communication network for use of the telecommunications resource;

means for coordinating a handover of a mobile device between the first communication network and the second communication network based on a plurality of geographic boundaries defined in the resource leasing scheme;

means for allocating the telecommunications resources of the first communication network for access and use by a second communication network of the plurality of communication networks;

means for broadcasting a second communication signal informing the second communication network that use of the allocated telecommunications resource may begin in the geographic area; and

for recording a transaction in a transaction database identifying the telecommunications resource as being allocated for use by the second communications network.

17. The DSA apparatus of claim 16, further comprising:

means for receiving resource configuration information relating to a resource allocation scheme from a first dynamic spectrum controller server in the first communication network; and

means for sending the resource configuration information to a second dynamic spectrum controller server in the second communication network.

18. The DSA apparatus of claim 16, further comprising:

means for receiving coordination information relating to availability of the telecommunications resource from a first dynamic spectrum controller server in the first communication network based on a plurality of geographic regions; and

means for sending the coordination information to a second dynamic spectrum controller server in the second communication network.

19. The DSA apparatus of claim 16, further comprising:

means for determining the validity of a subscriber device of the second communication network based on the proximity of the subscriber device to the geographic area and information included in the resource leasing scheme.

20. The DSA apparatus of claim 16, further comprising:

means for instructing a subscriber device of the second communication network to establish a communication link to a component in the first communication network based on the proximity of the subscriber device to the geographic area and the terms included in the resource leasing scheme.