WO2016149372A1

WO2016149372A1 - Method and system for a flexible dynamic spectrum arbitrage system

Info

Publication number: WO2016149372A1
Application number: PCT/US2016/022647
Authority: WO
Inventors: Clint Smith
Original assignee: Rivada Networks Llc
Priority date: 2015-03-16
Filing date: 2016-03-16
Publication date: 2016-09-22

Abstract

A server computing device may be configured to perform dynamic spectrum arbitrage (DSA) operations that include broadcasting a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network, determining lease criteria parameters of a resource lease associated with the advertised telecommunication resource, determining network capability of the second telecommunication network, selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria, determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration, and sending the determined configuration parameters to components in each of the first and second networks.

Description

TITLE

Method and System for a Flexible Dynamic Spectrum Arbitrage System

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Non-Provisional Application No. 15/071,040, entitled "Method and System for a Flexible Dynamic Spectrum

Arbitrage System" filed March 15, 2016; which also claims the benefit of priority to U.S. Provisional Application No. 62/133,844, entitled "Method and System for a Flexible Dynamic Spectrum Arbitrage System" filed March 16, 2015. Also, this application is a continuation in part of U.S. Non-Provisional Application No. 14/948,903 titled

"Interfacing between a Dynamic Spectrum Policy Controller and a Dynamic Spectrum Controller" filed November 23, 2015, which is a continuation of U.S. Non-Provisional Application No. 14/287,090 titled "Interfacing Between a Dynamic Spectrum Policy Controller and a Dynamic Spectrum Controller" filed May 26, 2014, which claims the benefit of priority to U.S. Provisional Application No. 61/827,911 titled "Interfacing between a Dynamic Spectrum Policy Controller and a Dynamic Spectrum Controller" filed May 28, 2013, the entire contents of all of which are hereby incorporated by reference.

BACKGROUND

[0002] 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 frequency spectrum. Smart phone users complain about dropped calls, slow access to the Internet and similar problems which are due largely to too many devices trying to access finite RF bandwidth allocated to such services. Yet parts of the RF spectrum, such as the RF bands dedicated to emergency services (e.g., police, fire and rescue, etc.), go largely unused due to the non-continuous and episodic employment of such voice-radio communication bands. Therefore, improved methods and solutions for dynamically allocating underutilized telecommunication resources (e.g., RF spectrum, etc.) of a first telecommunication network for access and use by wireless devices that subscribe to other networks will be beneficial to the telecommunication networks, service providers, and to the consumers of telecommunication services.

SUMMARY

[0003] The various aspects include methods of performing DSAFlex operation in dynamic spectrum arbitrage (DSA) system, the DSAFlex operations including

broadcasting a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network, determining lease criteria parameters of a resource lease associated with the advertised telecommunication resource, determining network capability of the second

telecommunication network, selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria, determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration, and sending the determined configuration parameters to components in each of the first and second networks.

[0004] In an aspect, selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria includes selecting the DSAX network

configuration, and sending the determined configuration parameters to components in each of the first and second networks includes sending the determined configuration parameter directly to the components in the first and second networks. In a further aspect, sending the determined configuration parameter directly to the components in the first and second networks includes sending configuration parameters to an eNodeB via an Xe interface, and sending configuration parameters to an MME component via an Xm interface.

[0005] In a further aspect, selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria includes selecting the DSA Lite network configuration or the DSA9 network configuration, and sending the determined

configuration parameters to components in each of the first and second networks includes sending the determined configuration parameters to an O&M component in each of the first and second networks. In a further aspect, determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration includes determining configuration parameters that match a specific OEM format. In a further aspect, sending the determined configuration parameters to components in each of the first and second networks includes sending the parameters in the specific OEM format. In a further aspect, the method may include dynamically selecting an interface based on the determined network capability. In a further aspect, the method may include routing traffic to destination components based on the network configuration of the second network.

[0006] In a further aspect, the method may include receiving in a dynamic spectrum controller (DSC) processor a list of resources that are available for bidding via a communication link to a dynamic spectrum policy controller (DPC) that includes a DPC processor, generating a bid request message that includes information suitable for bidding on a resource identified in the received list of resources, and sending the generated bid request message to the DPC via the communication link.

[0007] In a further aspect, the method may include starting by the DPC processor a bid timer, receiving in the DPC processor the bid request message from the DSC via the communication link, determining whether the bid request message is valid, sending a bid accept message to the DSC via the communication link in response to determining that the bid is valid, determining whether the bid timer has expired, determining whether the DSC is a winner bidder that is to be allocated the resource based on information included in the bid request message in response to determining that the bid request message is valid and that the bid timer has expired, and sending a bid won message to the DSC via the communication link in response to determining that the DSC is the winner bidder.

[0008] Further aspects may include server computing device that includes a processor configured with processor executable instructions to perform operations including broadcasting a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network, determining lease criteria parameters of a resource lease associated with the advertised telecommunication resource, determining network capability of the second

[0009] In an aspect, the processor may be configured with processor executable instructions to perform operations such that selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria includes selecting the DSAX network configuration, and sending the determined configuration parameters to components in each of the first and second networks includes sending the determined configuration parameter directly to the components in the first and second networks. In a further aspect, the processor may be configured with processor executable instructions to perform operations such that sending the determined configuration parameter directly to the components in the first and second networks includes sending configuration parameters to an eNodeB via an Xe interface, and sending configuration parameters to an MME component via an Xm interface.

[0010] In a further aspect, the processor may be configured with processor executable instructions to perform operations such that selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria includes selecting the DSA Lite network configuration or the DSA9 network configuration, and sending the determined configuration parameters to components in each of the first and second networks includes sending the determined configuration parameters to an O&M component in each of the first and second networks. In a further aspect, the processor may be configured with processor executable instructions to perform operations such that determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration includes determining configuration parameters that match a specific OEM format.

[0011] In a further aspect, the processor may be configured with processor executable instructions to perform operations such that sending the determined configuration parameters to components in each of the first and second networks includes sending the parameters in the specific OEM format. In a further aspect, the processor may be configured with processor executable instructions to perform operations further including dynamically selecting an interface based on the determined network capability. In a further aspect, the processor may be configured with processor executable instructions to perform operations further including routing traffic to destination components based on the network configuration of the second network, In a further aspect, the processor may be configured with processor executable instructions to perform operations further including receiving a list of resources that are available for bidding via a communication link to a dynamic spectrum policy controller (DPC) that includes a DPC processor, generating a bid request message that includes information suitable for bidding on a resource identified in the received list of resources, and sending the generated bid request message to the DPC via the communication link.

[0012] In a further aspect, the processor may be configured with processor executable instructions to perform operations further including starting by the DPC processor a bid timer, receiving in the DPC processor the bid request message from a DSC via the communication link, determining whether the bid request message is valid, sending a bid accept message to the DSC via the communication link in response to determining that the bid is valid, determining whether the bid timer has expired, determining whether the DSC is a winner bidder that is to be allocated the resource based on information included in the bid request message in response to determining that the bid request message is valid and that the bid timer has expired, and sending a bid won message to the DSC via the communication link in response to determining that the DSC is the winner bidder.

[0013] Further aspects may include a non-transitory computer readable storage medium having stored thereon processor-executable software instructions configured to cause a processor to perform operations including broadcasting a communication message that includes information advertising that a telecommunication resource in a first

telecommunication network is available for allocation and use by wireless devices in a second telecommunication network, determining lease criteria parameters of a resource lease associated with the advertised telecommunication resource, determining network capability of the second telecommunication network, selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria, determining configuration parameters for one or more nodes in each of the first and second

telecommunication networks based on the selected network configuration, and sending the determined configuration parameters to components in each of the first and second networks. [0014] In an aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations such that selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria includes selecting the DSAX network configuration, and sending the determined configuration parameters to components in each of the first and second networks includes sending the determined configuration parameter directly to the components in the first and second networks. In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations sending the determined configuration parameter directly to the components in the first and second networks includes sending configuration parameters to an eNodeB via an Xe interface, and sending configuration parameters to an MME component via an Xm interface.

[0015] In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations such that selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria includes selecting the DSA Lite network configuration or the DSA9 network configuration, and sending the determined configuration parameters to components in each of the first and second networks includes sending the determined configuration parameters to an O&M component in each of the first and second networks. In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations such that determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration includes determining configuration parameters that match a specific OEM format.

[0016] In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations such that sending the determined configuration parameters to components in each of the first and second networks includes sending the parameters in the specific OEM format. In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations further including dynamically selecting an interface based on the determined network capability. In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations further including routing traffic to destination components based on the network configuration of the second network, In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations further including receiving a list of resources that are available for bidding via a communication link to a dynamic spectrum policy controller (DPC) that includes a DPC processor, generating a bid request message that includes information suitable for bidding on a resource identified in the received list of resources, and sending the generated bid request message to the DPC via the communication link.

[0017] In a further aspect, the stored processor-executable software instructions may be configured to cause the mobile device processor to perform operations further including starting by the DPC processor a bid timer, receiving in the DPC processor the bid request message from a DSC via the communication link, determining whether the bid request message is valid, sending a bid accept message to the DSC via the communication link in response to determining that the bid is valid, determining whether the bid timer has expired, determining whether the DSC is a winner bidder that is to be allocated the resource based on information included in the bid request message in response to determining that the bid request message is valid and that the bid timer has expired, and sending a bid won message to the DSC via the communication link in response to determining that the DSC is the winner bidder.

BRIEF DESCRIPTION OF THE DRAWINGS [0018] 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 features of the invention.

[0019] FIGs. 1 A through IE are system block diagrams illustrating various logical and functions components and communication links in communication systems that may be used to implement the various embodiments.

[0020] FIG. 2A is a process flow diagram illustrating a dynamic spectrum arbitrage (DSA) method of allocating resources from the perspective of a dynamic spectrum policy controller (DPC) in accordance with an embodiment.

[0021] FIG. 2B is a message flow diagram illustrating message communications between components of a DSA communication system when allocating resources in accordance with an embodiment.

[0022] FIGs. 3 through 7 are process flow diagrams illustrating an embodiment DSA method of allocating and accessing resources in a communication system that includes a DPC, two dynamic spectrum controllers (DSCs), and a wireless device.

[0023] FIGs. 8A through 8C are message flow diagrams illustrating an embodiment dynamic spectrum arbitrage application part (DSAAP) registration method.

[0024] FIGs. 9A and 9B are message flow diagrams illustrating an embodiment DSAAP advertizing method.

[0025] FIGs. 10A and 10B are message flow diagrams illustrating an embodiment DSAAP method for communicating a list of available resources.

[0026] FIGs. 11A and 11B are message flow diagrams illustrating an embodiment DSAAP bidding method. [0027] FIGs. 12A through 12D are message flow diagrams illustrating an embodiment DSAAP notification method for informing participating networks of the results of the bidding operations.

[0028] FIGs. 13A and 13B are message flow diagrams illustrating an embodiment DSAAP purchase method for immediately (or near immediately) purchasing a resource.

[0029] FIGs. 14A and 14B are message flow diagrams illustrating an embodiment DSAAP allocation method for allocating resources in a lessor network for access and use by components in a lessee network.

[0030] FIGs. 15A and 15B are message flow diagrams illustrating an embodiment DSAAP backoff method of selectively handing over a wireless device from a lessor network back to the lessee's network (i.e. its home PLMN).

[0031] FIG. 16A is a message flow diagram illustrating an embodiment DSC initiated DSAAP de-registration method for terminating DSA operations.

[0032] FIG. 16B is a message flow diagram illustrating an embodiment DPC initiated DSAAP de-registration method for terminating DSA operations.

[0033] FIG. 17A is a message flow diagram illustrating a DSC initiated DSAAP error indication method for reporting errors.

[0034] FIG. 17B is a message flow diagram illustrating a DPC initiated DSAAP error indication method for reporting errors.

[0035] FIG. 18 is an activity diagram illustrating the operations and information flows between various components in a communication system when performing a DSA resource update method.

[0036] FIG. 19 is a process flow diagram illustrating an embodiment DSA method of allocating and de-allocating resources between different networks. [0037] FIG. 20A is a process flow diagram illustrating a method of performing DSA operations in accordance with an embodiment.

[0038] FIG. 20B is a process flow diagram illustrating a method of performing DSA operations that include DSAFlex operations in accordance with an embodiment.

[0039] FIGs. 21 A through 21C are activity diagrams illustrating various operations and information flows in systems configured to perform DSAFlex operations in accordance with various embodiments.

[0040] FIG. 22 is a block diagram illustrating a system in which both the lessor and lessee networks are organized and/or configured to perform DS AX operations in accordance with the various embodiments.

[0041] FIG. 23 is a block diagram illustrating a system in which both the lessor and lessee networks are organized and/or configured to perform DS A9 operations in accordance with the various embodiments.

[0042] FIG. 24 is a block diagram illustrating a system in which the lessor network is organized/configured to perform DSAX operations and the lessee network is

organized/configured to perform DSA9 operations in accordance with an embodiment.

[0043] FIG. 25 is a block diagram illustrating a system in which both the lessor and lessee networks are organized/configured to perform DSA-Lite operations in accordance with an embodiment.

[0044] FIG. 26 is a block diagram illustrating a system in which the lessor network is organized/configured to perform DSAX operations and the lessee network is

organized/configured to perform DSA-Lite operations in accordance with an

embodiment. [0045] FIG. 27 is a component block diagram of an example wireless device suitable for use with the various embodiments.

[0046] FIG. 28 is a component block diagram of a server suitable for use with an embodiment.

DETAILED DESCRIPTION

[0047] The 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 made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims.

[0048] As used herein, the terms "wireless device," "wireless device" and "user equipment (UE)" may be used interchangeably and refer to any one of various cellular telephones, personal data assistants (PDA's), palm-top computers, laptop computers with wireless modems, wireless electronic mail receivers (e.g., the Blackberry® and Treo® devices), multimedia Internet enabled cellular telephones (e.g., the iPhone®), and similar personal electronic devices. A wireless device may include a programmable processor and memory. In a preferred embodiment, the wireless device is a cellular handheld device (e.g., a wireless device), which can communicate via a cellular telephone communications network.

[0049] 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, software, or software in execution, which are configured to perform particular operations or functions. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, a computer, a server, network hardware, etc. By way of illustration, both an application running on a computing device and the computing device may 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 may execute from various non- transitory computer readable media having various instructions and/or data structures stored thereon.

[0050] A number of different cellular and mobile communication services and standards are available or contemplated in the future, all of which may implement and benefit from the various embodiments. Such services and standards include, e.g., third generation partnership project (3GPP), long term evolution (LTE) systems, third generation wireless mobile communication technology (3G), fourth generation wireless mobile

communication technology (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 network (WLAN), public switched telephone network (PSTN), Wi-Fi Protected Access I & II (WPA, WPA2), Bluetooth®, integrated digital enhanced network (iden), land mobile radio (LMR), and evolved universal terrestrial radio access network (E-UTRAN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling and/or content messages. It should be understood that any references to terminology and/or technical details related to an individual telecommunication standard or technology are for illustrative purposes only, and are not intended to limit the scope of the claims to a particular communication system or technology unless specifically recited in the claim language. [0051] The various embodiments include a dynamic spectrum arbitrage (DSA) system configured to dynamically manage the availability, allocation, access, and use of telecommunication resources, such as radio frequency (RF) spectrum and RF spectrum resources. The DSA system may include various DSA components, such as a dynamic spectrum policy controller (DPC) component and a dynamic spectrum controller (DSC) component. The DPC component may be configured to manage the DSA operations and interactions between two or more networks (e.g., between a lessor network and a lessee network), which often requires communicating with a DSC component in each of the participating networks. As part of these DSA operations, the DSA components (e.g., DPC, DSC, etc.) may be required to communicate frequently and/or transmit a large amount of information. As such, the communications, interactions, and communication interfaces between these components may have a significant negative impact on the efficiency and speed of the DSA system and the participating telecommunication networks.

[0052] The various embodiments include a dynamic spectrum arbitrage application part (DSAAP) protocol and component configured to allow, facilitate, support, or augment communications between the DSA components (e.g., DPC, DSC, eNodeB, etc.) so as to improve the efficiency and speed of the DSA system. In addition, the DSAAP protocol/component may be configured to allow the DSA components to communicate specific information and perform operations that together provide various DSA functions that improve the efficiency and speed of the DSA system and participating networks.

[0053] In various embodiments, all or portions of the DSAAP component may be included in a DPC component, a DSC component, an eNodeB component, in an independent DSA component, or any combination thereof. The DSAAP component may be implemented in hardware, software, or a combination of hardware and software. In an embodiment, the DSAAP component may be configured to implement a DSAAP protocol, which may be defined over the Xe, Xd, and/or X2 reference points. In various embodiments, the Xe reference point between DSC and eNodeB may use the DSAAP protocol, TR-069 protocol, and/or TR-192 data model extensions to support listing available resources at the eNodeB and notifying the eNodeB of bid/buy confirmations. The Xd reference point between DSC and DPC may use the DSAAP protocol for dynamic spectrum and resource arbitrage operations. The X2 interface/reference point between the eNodeB s may also use the DSAAP protocol to communicate information.

[0054] In various embodiments, the DSAAP component may be configured to allow an eNodeB to communicate with a DSC component (e.g., via the Xe interface), with other eNodeBs (e.g., via an X2 interface), and with various other components (e.g., via the SI interface). By allowing the eNodeB to communicate efficiently with these components, the DSAAP component may further improves the efficiency and speed of the DSA system.

[0055] For example, in an embodiment, the DSA system may include an eNodeB that is equipped with a DSC application protocol and congestion monitoring (DAPCM) module. The DAPCM module may be configured to monitor various network conditions (e.g., network congestion, resource usage, resource availability, etc.), generate reports based on the monitoring, and send the generated reports to a DSC component via the DSAAP. The DSC may be configured to receive and use such information to make better or more informed resource requests and/or to better identify the resources that could be made available for allocation.

[0056] As another example, in an embodiment, the DSC may include an eNodeB geographic boundary management (EGBM) module configured to maintain records suitable for identifying geographical areas/boundaries associated with various resources. The EGBM may be configured to communicate (e.g., via the DSAAP) this information to the eNodeB, which may receive and use such information to make better and more efficient use of the allocated resources. For example, the eNodeB may use the

geographical information received from the DSC to better determine the geographic regions (e.g., zones, cell sites, etc.) in which a wireless device may use an allocated resource. Such communications also allow the DSA system to better allocate resources to a targeted geographic area, and to better allocate resources per user, per sector, per base station, per cell cluster, per license area, etc.

[0057] In various embodiments, the DSAAP component may be configured to allow, facilitate, support, or augment communications between the DSC component and the DPC component so as to improve the efficiency and speed of the DSA system and telecommunication network. Such communications may allow the DPC and/or DSC components to better pool resources across the different networks, better monitor traffic and resource usage in the various networks, to more efficiently communicate bids and bidding information, to quickly and efficiently register and deregister components, and better perform backoff operations. Such communications may also improve the DSA resource auctioning operations by improving the performance and efficiency of the procedures for bidding, generating invoices, advertizing resources, requesting resources, purchasing resources, validating bid credentials, etc.

[0058] In the various embodiments, the DSAAP component(s) may allow the various DSA components (e.g., DSC, DPC, eNodeB, etc.) to communicate using the DSAAP protocol and to perform various DSAAP methods. For example, the DSAAP methods may be performed in a DSA system that includes a first DSC server in a first

telecommunication network (e.g., a lessee network), a second DSC server in second telecommunication network (e.g., a lessor network), and a DPC server that is outside of the first and second telecommunication networks.

[0059] In various embodiments, the DSAAP component may be configured to facilitate, support, or improve the DSA operations for bidding, resources allocation, and billing. Such DSAAP/DSA operations may include receiving in a DSC processor a list of resources that are available for bidding (via a communication link to a DPC/DPC processor), generating bid request message (e.g., DSC Bid Request message) that includes information suitable for bidding on a resource identified in the received list of resources, and sending the generated bid request message to the DPC (via the communication link). The DSAAP/DSA operations may also include the DPC

processing starting a timer, receiving the bid request message (e.g., DSC Bid Request) from the DSC via the communication link, determining whether the bid request message is valid, and sending a bid accept message (DSC Bid Accept) to the DSC in response to determining that the bid is valid. The DPC processor may then determine whether the bid timer has expired, determine whether the DSC is a winning bidder that is to be allocated the resource (i.e., based on information included in the bid request message) in response to determining that the bid request message is valid and that bid timer has expired. The DPC processor may send a bid won message to the DSC via the communication link in response to determining that the DSC is the winning bidder. The DPC processor may then allocate the resource from a lessor network for access and use by a lessee network associated with the DSC.

[0060] In an embodiment, the DSAAP/DSA operations may include receiving in the DPC processor usage parameters and payment instructions from a component in the lessor network, generating an invoice for the access and use of the allocated resource by the lessee network, and sending the generated invoice to the DSC. The DPC processor may send the payment instructions and an invoice for to the use of the allocated resource by the lessee network to the DSC via the communication link, receive payment information from the DSC, and use the received payment information to settle the invoice.

[0061] In an embodiment, the DSAAP/DSA operations may include resource registrations operations. For example, the DPC processor may be configured to receive a resource register request message (e.g., DSC Resource Registration Request) from a second DSC in a lessor network, use the information included in the received resource register request message to make a plurality of resources available for bidding or buying via a financial brokerage platform, and generate the list of resources to include the plurality of resources. The bid request message may include a bid identifier information element (IE) that identifies a specific resource for which the DSC bids, a network identifier IE that identifies a specific network that includes the resource for which the DSC bids, and a bid amount IE that identifies a monetary amount offered for the access and use of the resource for which the DSC bids. In an embodiment, determining whether the bid request message is valid may include determining whether the monetary amount offered for the access and use of the resource (i.e., in the bid request message) is equal to an asking price for that resources received from its corresponding lessor network.

[0062] The various embodiments may be implemented within a variety of communication systems, examples of which are illustrated in FIGs. 1A-1E. With reference to FIG. 1A, wireless devices 102 may be configured to transmit and receive voice, data, and control signals to and from a base station 111, which may be a base transceiver station (BTS), NodeB, eNodeB, etc. The base station 111 may communicate with an access gateway 113, which may include one or more of a controller, a gateway, a serving gateway (S- GW), a packet data network gateway (PGW), an evolved packet data gateway (ePDG), a packet data serving node (PDSN), a serving GPRS support node (SGSN), or any similar component or combinations of the features/functions provided thereof. Since these structures are well known and/or discussed in detail further below, certain details have been omitted from FIG. 1 A in order to focus the descriptions on the most relevant features.

[0063] The access gateway 113 may be any logical and/or functional component that serves as the primary point of entry and exit of wireless device traffic and/or connects the wireless devices 102 to their immediate service provider and/or packet data networks (PDNs). The access gateway 113 may forward the voice, data, and control signals to other network components as user data packets, provide connectivity to external packet data networks, manage and store contexts (e.g. network internal routing information, etc.), and act as an anchor between different technologies (e.g., 3GPP and non-3GPP systems). The access gateway 113 may coordinate the transmission and reception of data to and from the Internet 105, as well as the transmission and reception of voice, data and control information to and from an external service network 104, the Internet 105, other base stations 111, and to wireless devices 102.

[0064] In various embodiments, the base stations 111 and/or access gateway 113 may be coupled (e.g., via wired or wireless communication links) to a dynamic spectrum arbitrage (DSA) system configured to dynamically manage the availability, allocation, access, and use of various network resources (e.g., RF spectrum, RF spectrum resources, etc.). The DSA system is discussed in detail further below.

[0065] FIG. IB illustrates that wireless devices 102 may be configured to send and receive voice, data and control signals to and from the service network 104 (and ultimately the Internet 105) using a variety of communication systems/technologies (e.g., GPRS, UMTS, LTE, cdmaOne, CDMA2000TM), any or all of which may be supported by, or used to implement, the various embodiments.

[0066] In the example illustrated in FIG. IB, long term evolution (LTE) and/or evolved universal terrestrial radio access network (E-UTRAN) data transmitted from a wireless device 102 is received by an eNodeB 116, and sent to a serving gateway (S-GW) 118 located within the core network 120. The eNodeB 116 may send signaling/control information (e.g., information pertaining to call setup, security, authentication, etc.) to a mobility management entity (MME) 130. The MME 130 may request user/subscription information from a home subscriber server (HSS) 132, communicate with other MME components, perform various administrative tasks (e.g., user authentication, enforcement of roaming restrictions, etc.), select a S-GW 118, and send authorization and

administrative information to the eNodeB 116 and/or S-GW 118. Upon receiving the authorization information from the MME 130 (e.g., an authentication complete indication, an identifier of a selected S-GW, etc.), the eNodeB 116 may send data received from the wireless device 102 to a selected S-GW 118. The S-GW 118 may store information about the received data (e.g., parameters of the IP bearer service, network internal routing information, etc.) and forward user data packets to a policy control enforcement function (PCEF) and/or packet data network gateway (PGW) 128.

[0067] FIG. IB further illustrates that general packet radio service (GPRS) data transmitted from the wireless devices 102 may be received by a base transceiver station (BTS) 106 and sent to a base station controller (BSC) and/or packet control unit (PCU) component (BSC/PCU) 108. Code division multiple access (CDMA) data transmitted from a wireless device 102 may be received by a base transceiver station 106 and sent to a base station controller (BSC) and/or packet control function (PCF) component

(BSC/PCF) 110. Universal mobile telecommunications system (UMTS) data transmitted from a wireless device 102 may be received by a NodeB 112 and sent to a radio network controller (RNC) 114.

[0068] The BSC/PCU 108, BSC/PCF 110, and RNC 114 components may process the GPRS, CDMA, and UMTS data, respectively, and send the processed data to a component within the core network 120. More specifically, the BSC/PCU 108 and RNC 114 units may send the processed data to a serving GPRS support node (SGSN) 122, and the BSC/PCF 110 may send the processed data to a packet data serving node (PDSN) and/or high rate packet data serving gateway (HS-GW) component (PDSN/HS-GW) 126. The PDSN/HS-GW 126 may act as a connection point between the radio access network and the IP based PCEF/PGW 128. The SGSN 122 may be responsible for routing the data within a particular geographical service area, and send signaling (control plane) information (e.g., information pertaining to call setup, security, authentication, etc.) to an MME 130. The MME 130 may request user and subscription information from a home subscriber server (HSS) 132, perform various administrative tasks (e.g., user

authentication, enforcement of roaming restrictions, etc.), select a S-GW 118, and send administrative and/or authorization information to the SGSN 122.

[0069] The SGSN 122 may send the GPRS/UMTS data to a selected S-GW 118 in response to receiving authorization information from the MME 130. The S-GW 118 may store information about the data (e.g., parameters of the IP bearer service, network internal routing information, etc.) and forward user data packets to the PCEF/PGW 128. The PCEF/PGW 128 may send signaling information (control plane) to a policy control rules function (PCRF) 134. The PCRF 134 may access subscriber databases, create a set of policy rules and performs other specialized functions (e.g., interacts with online/offline charging systems, application functions, etc.). The PCRF 134 may then send the policy rules to the PCEF/PGW 128 for enforcement. The PCEF/PGW 128 may implement the policy rules to control the bandwidth, the quality of service (QoS), the characteristics of the data, and the services being communicated between the service network 104 and the end users.

[0070] In the various embodiments, any or all of the components discussed above (e.g., components 102-134) may be coupled to, or included in, a DSA system configured to dynamically manage the availability, allocation, access, and use of telecommunication resources.

[0071] FIG. 1C illustrates various logical components and communication links in an embodiment system 100 that includes an DSA system 142 and a evolved universal terrestrial radio access network (E-UTRAN) 140. In the example illustrated in FIG. 1C, the DSA system 142 includes a dynamic spectrum controller (DSC) 144 component and a dynamic spectrum policy controller (DPC) 146 component. The E-UTRAN 140 includes a plurality of interconnected eNodeBs 116 coupled to the core network 120 (e.g., via a connection to an MME, S-GW, etc.).

[0072] In various embodiments, the DSC 144 may be included in or coupled to the E- UTRAN 140, either as part of its core network 120 or outside of the core network 120. In an embodiment, the DSC 144 may be coupled directly (e.g., via wired or wireless communication links) to one or more eNodeBs 116.

[0073] The eNodeBs 116 may be configured to communicate with the DSC 144 via the Xe interface/reference point. In various embodiments, the Xe reference point between DSC and eNodeB 116 may use the DSAAP protocol, TR-069 protocol, and/or TR-192 data model extensions to support listing available resources at the eNodeB 116 and notifying the eNodeB 116 of bid/buy confirmations. The DSC 144 may be configured to communicate with the DPC 146 via the Xd interface/reference point. The Xd reference point between DSC and DPC may use the DSAAP protocol for dynamic spectrum and resource arbitrage operations. The eNodeBs 116 may be interconnected, and configured to communicate via an X2 interface/reference point, which may also use the DSAAP protocol to communicate information. The eNodeBs 116 may be configured to communicate with components in the core network 120 via the SI interface. For example, the eNodeBs 116 may be connected to an MME 130 via the Sl-MME interface and to a S-GW 118 via the Sl-U interface. The SI interface may support a many-to- many relation between the MMEs 130, S-GWs 118, and eNodeBs 116. In embodiment, the DPC and/or DSC component may also be configured to communicate with a HSS 132 component.

[0074] The eNodeBs 116 may be configured to provide user plane (e.g., PDCP, RLC, MAC, PHY) and control plane (RRC) protocol terminations towards the wireless device 102. That is, the eNodeBs 116 may act as a bridge (e.g., layer 2 bridge) between the wireless devices 102 and the core network 120 by serving as the termination point of all radio protocols towards the wireless devices 102, and relaying voice (e.g., VoIP, etc.), data, and control signals to network components in the core network 120. The eNodeBs 116 may also be configured to perform various radio resource management operations, such as controlling the usage of radio interfaces, allocating resources based on requests, prioritizing and scheduling traffic according to various quality of service (QoS) requirements, monitoring the usage of network resources, etc. In addition, the eNodeBs 116 may be configured to collect radio signal level measurements, analyze the collected radio signal level measurements, and handover wireless devices 102 (or connections to the mobile devices) to another base station (e.g., a second eNodeB) based on the results of the analysis. [0075] The DSC 144 and DPC 146 may be functional components configured to manage the dynamic spectrum arbitrage process for sharing radio frequency and other network resources between different E-UTRANs 140. For example, the DPC 146 component may be configured to manage the DSA operations and interactions between multiple E- UTRAN networks by communicating with DSCs 144 in the E-UTRAN network.

[0076] FIG. ID illustrates various logical and functional components that may be included in a communication system 101 that suitable for use in performing DSA operations in accordance with various embodiments. In the example illustrated in FIG. ID, the communication system 101 includes an eNodeB 116, a DSC 144, a DPC 146, an MME 130, a S-GW 118, and a PGW 128.

[0077] The eNodeB 116 may include a DSC application protocol and congestion monitoring module 150, an inter-cell radio resource management (RRM) module 151, a radio bearer (RB) control module 152, a connection mobility control module 153, a radio admission control module 154, an eNodeB measurement configuration and provision module 155, and a dynamic resource allocation module 156. Each of these modules 150- 156 may be implemented in hardware, in software, or in a combination of hardware and software.

[0078] In addition, the eNodeB 116 may include various protocol layers, including a radio resource control (RRC) layer 157, a packet data convergence protocol (PDCP) layer 158, a radio link control (RLC) layer 159, a medium access control (MAC) layer 160, and a physical (PHY) layer 161. In each of these protocol layers, various hardware and/or software components may implement functionality that is commensurate with

responsibilities assigned to that layer. For example, data streams may be received in the physical layer 161, which may include a radio receiver, buffers, and processing components that perform the operations of demodulating, recognizing symbols within the radio frequency (RF) signal, and performing other operations for extracting raw data from the received RF signal. [0079] The DSC 144 may include an eNodeB geographic boundary management module 162, an eNodeB resource and congestion management module 163, a stream control transmission protocol (SCTP) module 164, a Layer-2 (L2) buffer module 165, and a Layer- 1 (LI) buffer module 166. The DPC 146 may include an eNodeB resource bid management module 167, an inter-DSC communication module 168, SCTP/DIAMETER module 169, an L2 buffer module 170, and a LI buffer module 171. The MME 130 may include a non-access stratum (NAS) security module 172, and idle state mobility handling module 173, and an evolved packet system (EPS) bearer control module 174. The S-GW 118 may include a mobility anchoring module 176. The PGW 128 may include a UE IP address allocation module 178 and a packet filtering module 179. Each of these modules 162-179 may be implemented in hardware, in software, or in a combination of hardware and software.

[0080] The eNodeB 116 may be configured to communicate with the S-GW 118 and/or MME 130 via the SI interface/protocol. The eNodeB 116 may also be configured to communicate with the DSC 144 via the Xe interface/protocol. The DSC 144 may be configured to communicate with the DPC 146 via the Xd interface/protocol.

[0081] The eNodeB 116 may be configured to perform various operations (e.g., via modules/layers 150-161) to provide various functions, including functions for radio resource management, such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to wireless devices 102 in both uplink and downlink (scheduling), etc. These functions may also include IP header compression and encryption of user data stream, selection of an MME at UE attachment when no routing to an MME 130 can be determined from the information provided by the UE, routing of user plane data towards S-GW 118, scheduling and transmission of paging messages (originated from the MME), scheduling and transmission of broadcast information (originated from the MME), measurement and measurement reporting configuration for mobility and scheduling, scheduling and transmission of public warning system (e.g., earthquake and tsunami warning system, commercial mobile alert service, etc.) messages (originated from the MME), closed subscriber group (CSG) handling, and transport level packet marking in the uplink. In an embodiment, the eNodeB 116 may be a donor eNodeB (DeNB) that is configured to perform various operations to provide additional functions, such as an S1/X2 proxy functionality, Sl l termination, and/or S- GW/PGW functionality for supporting relay nodes (RNs).

[0082] The MME 130 may be configured to perform various operations (e.g., via modules 172-175) to provide various functions, including non-access stratum (NAS) signaling, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reach-ability (including control and execution of paging retransmission), tracking area list management (e.g., for a wireless device in idle and active mode), PGW and S-GW selection, MME selection for handovers with MME change, SGSN selection for handovers to 2G or 3G 3GPP access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, support for public warning system (e.g., earthquake and tsunami warning system, commercial mobile alert service, etc.) message transmission, and performing paging optimization. The MME module may also communicate various device state and attach/detach status information to the DSC. In an embodiment, the MME 130 may be configured to not filter paging massages based on the CSG IDs towards macro eNodeB s.

[0083] The S-GW 118 may be configured to perform various operations (e.g., via module 176) to provide various functions, including mobility anchoring (e.g., for inter-3GPP mobility), serving as a local mobility anchor point for inter-eNodeB handovers, E- UTRAN idle mode downlink packet buffering, initiation of network triggered service request procedures, lawful interception, packet routing and forwarding, transport level packet marking in the uplink (UL) and the downlink (DL), accounting on user and QoS class identifier (QCI) granularity for inter- operator charging, uplink (UL) and the downlink (DL) charging (e.g., per device, PDN, and/or QCI), etc. [0084] The PGW 128 may be configured to perform various operations (e.g., via modules 178-179) to provide various functions, including per-user based packet filtering (by e.g. deep packet inspection), lawful interception, UE IP address allocation, transport level packet marking in the uplink and the downlink, UL and DL service level charging, gating and rate enforcement, DL rate enforcement based on APN-aggregate maximum bit rate (AMBR), etc.

[0085] The DSC 144 may be configured to perform various operations (e.g., via modules 162-166) to provide various functions, including managing resource arbitration operations within a network (e.g., Public Land Mobile Network (PLMN)), tracking network resource listings, tracking current bids in progress, tracking executed bids, and tracking bid specific closed subscriber group (CSG) identifiers (CSG-IDs) for mobility management of lessee wireless devices 102 in lessor networks. The DSC 144 may be configured to handover wireless devices 102 from lessee network to lessor network (i.e., perform handins), and handover wireless devices 102 from lessor network back to lessee network (i.e., perform backoff).

[0086] The DSC 144 may also be configured to track congestion states of eNodeBs, select target eNodeBs for handovers, and manage traffic on lessor eNodeBs. The DSC 144 may be configured to offload users based on configured policies (e.g. offload lower priority users, offload higher priority users, offload users with specific QoS, etc.) from lessee networks to other less loaded eNodeBs 116 within a lessor network. The DSC 144 may also perform backoff operations to handover a wireless device 102 from lessor network back to the lessee network. The DSC 144 may also be configured to monitor, manage, and/or maintain historic congestion information that is collected or received from one or more eNodeBs in the system.

[0087] The DPC 146 may be configured to perform various operations (e.g., via modules 167-171) to provide various functions, including functioning as a resource arbitrage broker between the DSCs 144 of lessor and lessee networks (e.g., PLMNs), listing resources from various lessor networks for auction, and managing the auction process. The DPC 146 may be configured to send notifications of outbid, bid win, bid cancel and bid withdrawal and bid expiry to DSCs 144, install bid specific charging rules in the online and/or offline charging systems of lessee and lessor networks, and coordinate resource usage between DSCs 144 by acting as gateway between lessee and lessor DSCs 144.

[0088] FIG. IE illustrates network components and information flows in an example communication system 103 that includes two E-UTRANs 140a, 140b interconnected by a DPC 146 configured to manage DSA operations and interactions. In the example illustrated in FIG. IE, each E-UTRAN 140a, 140b includes an eNodeB 116a, 116b that is outside of its core network 120a, 120b, and a DSC 144a, 144b that is inside of the core network 120a, 120b.

[0089] The DSCs 144a, 144b may be configured to communicate with the DPC 146 via Xd interface. The DSCs 144a, 144b may also be connected, directly or indirectly, to various network components in their respective core networks 120a, 120b, such as a PCRF 134, HSS 132 and a PCEF/PGW 128 (not illustrated in FIG. IE). In an

embodiment, one or more of the DSCs 144a, 144b may be connected directly to one or more of the eNodeBs 116a, 116b.

[0090] In addition to the above-mentioned connections and communication links, the system 103 may include additional connections/links to accommodate data flows and communications between components in different E-UTRANs (e.g., E-UTRANS 140a and 140b). For example, the system 103 may include a connection/communication link between an eNodeB 116b in the second E-UTRAN 140b to an S-GW 118 in the first E- UTRAN 140a. As another example, the system 103 may include a

connection/communication link between a S-GW 118 in the second E-UTRAN 140b to a PGW 128 in the first E-UTRAN 140a. To focus the discussion of the relevant embodiments, these additional components, connections, and communication links are not illustrated in FIG. IE.

[0091] As is discussed in detail further below, the DSCs 144a, 144b may be configured to send information regarding the availability of spectrum resources (e.g., information received from an eNodeB, PCRF, PCEF, PGW, etc.) to the DPC 146. This information may include data relating to current and expected future usage and/or capacity of each network or sub-network. The DPC 146 may be configured to receive and use such information to intelligently allocate, transfer, manage, coordinate, or lease the available resources of the first E-UTRAN 140a to the second E-UTRAN 140b, and vice versa.

[0092] For example, the DPC 146 may be configured to coordinate the allocation of spectrum resources to the second E-UTRAN 140b (i.e., lessee network) from the E- UTRAN 140a (i.e., lessor network) as part of the dynamic spectrum arbitrage operations. Such operations may allow a wireless device 102 that is wirelessly connected to the eNodeB 116b in the second E-UTRAN 140b via a communication link 143 to be handed off to an eNodeB 116a in the first E-UTRAN 140a so that it may use the allocated spectrum resources of the first E-UTRAN 140a. As part of this handoff procedure, the wireless device 102 may establish a new connection 141 to the eNodeB 116a in the first E-UTRAN 140a, terminate the wireless connection 143 to the original eNodeB 116b, and use the allocated resources of the first E-UTRAN 140a as if they are included in the second E-UTRAN 140b. The DSA operations may be performed so that the first DSC 144a is a lessor DSC for a first resource/period of time, and a lessee DSC for a second resource or another period of time.

[0093] In an embodiment, the DSA and/or handoff operations may be performed so that the wireless device 102 maintains a data connection to (or a data connection that is managed by) the original network after it is handed off. For example, DSA and/or handoff operations may be performed so that the wireless device 102 maintains a dataflow connection to a PGW 128 in the second E-UTRAN 140b after being handed off to the eNodeB 116a in the first E-UTRAN 140a.

[0094] FIG. 2A illustrates an example DSA method 200 of allocating resources in accordance with an embodiment. Method 200 may be performed by a processing core in a DPC 146 component (e.g., server computing device, etc.).

[0095] In block 202, the DPC 146 may establish a first communication link to a first DSC 144a in a first communication network (e.g., E-UTRAN, etc.). In block 204, the DPC 146 may establish a second communication link to a second DSC 144b in a second communication network. In block 206, the DPC 146 may determine whether radio frequency (RF) spectrum resources are available for allocation within the second communication network. This may be accomplished by using the DSAAP protocol to communicate with a DSC 144 in the second communication network via the second communication link, which may be a wired or wireless communication link. In block 208, the DPC 146 may determine the amount of RF spectrum resources that are available for allocation. In block 210, the DPC 146 may perform various operations to allocate all or a portion of the available RF resources of the second communication network for access and use by wireless devices 102 in the first communication network.

[0096] In block 212, the DPC 146 may send a communication message to the first DSC 144a (e.g., by using the DSAAP protocol) to inform the first communication network that the use of the allocated RF spectrum resources may begin. In block 214, the DPC 146 may record a transaction in a transaction database identifying an amount of RF spectrum resources allocated for use by the first communication network.

[0097] In block 216, the DPC 146 may receive a communication message from the second DSC 144b that includes information indicating that the allocated resources have been consumed and/or requesting that the allocated resources be released. In block 218, the DPC 146 may send a resource consumed/release message to the first DSC 144a to cause the first network to terminate its use of the allocated resources. [0098] FIG. 2B illustrates example information flows between a DPC 146 and a plurality of DSCs 144a-d when performing another embodiment DSA method 250 to allocate resources. In the description below, the DSA method 250 is discussed from the perspective of the DPC 146 component, and may be performed by a processing core in the DPC 146. However, it should be understood that the DSA method 250 may be performed by processing cores in a DPC 146 component, processing cores in DSC 144a- d components, or a combination thereof. In addition, it should be understood that all the interactions and communications between the DPC 146 and the other components may be accomplished by DSAAP components and/or using the DSAAP protocol. As such, all such interactions and communications may be included in the DSAAP protocol.

[0100] In operation 252, a processing core in a DPC 146 component may receive a "request for resources" communication message from a first DSC 144a component in a first network (e.g., E-UTRAN, etc.). It should be understood that the "request for resources" communication message and all other communication messages discussed in this application may be DSAAP messages.

[0101] The "request for resources" communication message may include information suitable for informing the DPC 146 that the first network is interested in purchasing, leasing, accessing, and/or using resources from other networks. The "request for resources" communication message may also include information suitable for identifying the types and/or amounts of resources (e.g., RF spectrum resources, etc.) that are requested by the first network, the types and capabilities of the wireless devices 102 to which the requested resources will be allocated, and other similar information.

[0102] In operations 254, 256, and 258 the DPC 146 may generate and send a "resource inquiry" communication message to each of a second DSC 144b component in a second network, a third DSC 144c component in a third network, and a fourth DSC 144d component in a fourth network, respectively. The DPC 146 may be configured to generate the "resource inquiry" communication messages to include various component, device, and resource requirements, criteria, and information. For example, the DPC 146 may generate a "resource inquiry" communication message to include information identifying the types, capabilities, and geographic criteria of user wireless devices 102 in the first network (and other networks) to which resources are to be allocated. The geographic criteria may include a geographic location, a geographic polygon, and/or license area for a user wireless device 102 to which resources will be allocated.

[0103] In operations 260 and 262, the DPC 146 may receive "resource inquiry response" communication messages from the second and third DSCs 144b, 144c. These "resource inquiry response" communication messages may include information identifying the availability of excess resources that comply with the requirements/criteria included in the resource inquiry messages. In operation 264, the DPC 146 may receive another

"resource inquiry response" communication message from the fourth DSC 144d. This "resource inquiry response" communication messages may include information indicating that the fourth network does not include resources that meet the requested requirements/criteria.

[0104] In an embodiment, as part of operations 260-264, the DPC 146 may update a database record to identify the second and third networks as having resources available for allocation and/or to identify the fourth network as not including such resources.

[0105] In operation 266, the DPC 146 may generate and send a "resource availability" communication message to a plurality of DSCs in a plurality of networks, including the first DSC 144a in the first network. The DPC 146 may be configured to generate the "resource availability" communication message to include information that is suitable for informing the networks that resources are available for allocation. In an embodiment, the DPC 146 may be configured to inform the networks that resources are available for allocation by broadcasting a communication signal that includes information suitable for informing the networks that resources are available for allocation via auction and/or an auction start time for the auction. [0106] In operation 268, the DPC 146 may receive a "resource reservation request" communication message from the first DSC 144a. The received "resource reservation request" communication message may include information suitable for informing the DPC 146 that the first network intends to participate in the auction and/or bid on at least a portion of the available resources.

[0107] In operations 270 and 272, the DPC 146 may send the "resource reservation request" communication message to the second and third DSCs 144b, 144c, respectively. The "resource reservation request" communication message may include information suitable for causing the second and third DSCs 144b, 144c to reserve all or a portion of their available resources for allocation and use by other networks.

[0108] In operations 274 and 276, the DPC 146 may receive a "resource reservation response" communication message from each of the second and third DSCs 144b, 144c. The "resource reservation response" messages may include information suitable for informing the DPC 146 that the requested resources that have been reserved and/or information suitable for identifying the reserved resources.

[0109] Optionally, in operation block 278, the DPC 146 may pool the reserved resources for allocation and use by wireless devices 102 in other networks (e.g., the first network). For example, the DPC 146 may combine a block of spectrum reserved in the second network with a block of spectrum reserved in the third network. As another example, the DPC 146 may pool the resources available in the first and fourth channels of a block of spectrum reserved in the second network.

[0110] In operation 280, the DPC 146 may receive "resource bid" communication messages from a plurality of networks, including from the first DSC 144a in the first network. Each "resource bid" communication message may include a bid or offer for accessing, using, leasing, and/or purchasing a resource, as well as other related bid information (e.g., price, requested allocation/access methods, etc.). As part of operation 280, the DPC 146 may determine whether the received resource bids comply with the policies and rules of the DSA system and/or with requirements set forth by the networks offering the resources for allocation (e.g., meet the minimum asking price, etc.).

[0111] In operation 282, the DPC 146 may accept the bid/offer from the first network in response to determining that the resource bid received from the first network complies with the policies/rules of the DSA system and with requirements set forth by the resource offering network (e.g., offers a monetary amount for the use of all or a portion of the resources in the pool of available resources that is greater than or equal to a minimum amount specified by the second network). Also in operation 282, the DPC 146 may generate and send a "bid acceptance" communication message to the first DSC 144a.

[0112] In operation 284, the DPC 146 may allocate the resources of the second network for access and used by wireless devices 102 in the first network by sending an "assign resources request" communication message to the second DSC 144b. That is, in operation 284, the DPC may determine that the portion of the resources (e.g., in the pool of available resources) won by the first DSC 144a are fully available via the second network, and in response, only send the assign resources request message to the second network.

[0113] In operation 286, the DPC 146 may receive a "resources allocated"

communication message from the second DSC 144b. In operation 288, the DPC 146 may send the "resources allocated" communication message to the first DSC 144a to inform the first network that the resources have been allocated for access and used by its wireless devices 102 and/or that the use of the allocated resources may begin. In operation block 290, the DPC 146 may record a transaction in a transaction database identifying these resources as being allocated for access and use by the first network.

[0114] In operation 292, the DPC 146 may receive a "release resources" communication message from the second DSC 144b that includes information indicating that the allocated resources have been consumed and/or information suitable for requesting that the allocated resources be released. In operation 294, the DPC 146 may send a resource consumed/release message to the first DSC 144a to cause the first network to terminate its use of the allocated resources.

[0115] FIGs. 3-7 illustrate an embodiment DSA method 300 for allocating and accessing resources in a communication system that includes a DPC 146 component, two DSC 144a, 144b components, and wireless devices 102. All or portions of DSA method 300 may be performed by processing cores in a DPC 146, DSCs 144a-b, and/or wireless device 102. In the various embodiments, any of all of the interactions and

communications between the components 146, 144a, 144b, and 102 may be

accomplished or facilitated by DSAAP components and/or using the DSAAP protocol. As such, all such interactions and communications may be included in the DSAAP protocol.

[0116] With reference to FIG. 3, in block 302, a first DSC 144a in a first network may monitor user traffic (e.g., call and data traffic, etc.) as compared to the total spectrum resources available to the first network. In block 304, the first DSC 144a may generate a resource status report based on a result of its monitoring, record/store the resource status report in memory, and send a resource status report to the DPC 146 via a resources status report communication message. In determination block 306, the first DSC 144a may determine, based on the received resource status reports, whether additional resources are required (and/or whether there is a high probability that additional resources will be required in the near future) to provide adequate service to the existing wireless devices 102 in the first network. In response to determining that additional resources are required (i.e., determination block 306 = "Yes"), in block 308, the first DSC 144a may send a "request for resources" communication message to the DPC 146. In response to determining that additional resources are not required (i.e., determination block 306 = "No"), the first DSC 144a may continue monitoring user traffic and/or perform other DSC operations in block 302. [0117] In block 310, a second DSC 144b in a second network may monitor user traffic as compared to the total spectrum resources available to the second network, generate resource status reports, and/or perform any or all of the DSC operations discussed in this application. In determination block 312, the second DSC 144b may determine whether there is an excess amount of resources available in the second network. In response to determining that there are no excess resources available in the second network (i.e., determination block 312 = "No"), in block 310, the second DSC 144b may continue monitoring user traffic and/or performing other DSC operations.

[0118] In response to determining that there is an excess amount of resources available in the second network (i.e., determination block 312 = "Yes"), in block 314, the second DSC 144b may mark, designate, or allocate all or portions of its excess resources for access and use by other networks (e.g., the first network, etc.). In block 316, the second DSC 144b may generate a resource allocation report, and send the generated resource allocation report to the DPC 146 (e.g., via a resource communication message). The DSC 144b may be configured to generate the resource allocation report to include information identifying the resources (or portions or amounts of resources) that are available for allocation and/or that have been marked, designated, or allocated by the second network.

[0119] In block 320, the DPC 146 may receive various resource status and allocation reports from DSCs 144 in many different networks, including the first and second DSCs 144a, 144b in the first and second networks. These reports may include information identifying various characteristics, criteria, requirements, and conditions of the networks and their components, such as the ratio of the detected user traffic to the total available spectrum resources, the amount of resources that are required by a network, the amount of resources that are available for allocation in a network, the types and capabilities of the wireless devices 102 that will use the allocated resources, system requirements that must be met before the wireless devices 102 access the allocated resources, network rules and policies with respect to access and use of resources, and other similar information. [0120] In block 322, the DPC 146 may store the received reports (e.g., resource status reports, resource allocation reports, etc.) in memory (e.g., a non-volatile memory). In block 324, the DPC 146 may receive a request for resources from DSCs 144 in different networks, including the first DSC 144a in the first network. In block 326, the DPC 146 may use the received/stored information (e.g., information received in requests for resources, resource allocation reports, resource status reports, etc.) to identify and select the most suitable/best available network from which the first network may lease or purchase additional resources. In the example illustrated in FIG. 3, the DPC 146 identifies and selects the second network as the most suitable network to provide resources to the first network.

[0121] In block 328, the DPC 146 may send a resource inquiry communication message to the second DSC 1144b. In block 330, the second DSC 1144b may receive the resource inquiry communication message. In block 332, the second DSC 1144b may determine the availability, amounts, and/or quantity of the excess resources that are marked, designated, or allocated by the second network. In block 334, the second DSC 1144b may generate and send a "resource inquiry response" communication message to the DPC 146. The second DSC 1144b may generate resource inquiry response to include information suitable for use in identifying the availability and quantity of the resources that are marked, designated, or allocated for access and use by other networks (e.g., the first network). In block 336, the DPC 146 may receive the "resources inquiry response" communication message from the second DSC 1144b, and in response, perform the operations of determination block 400 illustrated in FIG. 4.

[0122] With reference to FIG. 4, in determination block 400, the DPC 146 may determine whether resources are available based on the data (e.g., resources inquiry response message) received from the second DSC 144b in the second network. For example, the DPC 146 may determine that the identified resources are not available in response to determining that all or a portion of the resources were purchased or won by other bidders before they were reserved. [0123] In response to determining that the resources are not available (i.e., determination block 400 = "No"), in block 402, the DPC 146 may send a "no resources available" communication message to the first DSC 144a in the first network. In block 404, the first DSC 144a may receive the "no resources available" communication message. In block 406, the first DSC 144a may search (e.g., via the DPC 146) for other available resources, request resources from a different network, request different resources, terminate connections or communication sessions with users to free-up resources, or perform other similar operations to manage network traffic and congestion in the first network.

[0124] In response to determining that the resources are available (i.e., determination block 400 = "Yes"), in block 408, the DPC 146 may send a "resources available" communication message to the first DSC 144a. The resources available message may include information that may be used by the first DSC 144a to determine the quality and quantity of resources in the second network that may be used by wireless devices 102 in the first network.

[0125] In block 410, the first DSC 144a may receive the resources available

communication message sent from the DPC 146. In block 412, the first DSC 144a may determine the amount/quantity of resources that the first network requires and/or will attempt to acquire, and send this and other resource information to the DPC 146 in a "request resources" communication message.

[0126] In block 414, the DPC 146 may receive the "request resources" message from the first DSC 144a. In block 416, the DPC 146 may use information included in received message to generate and send a "reserve resources request" communication message to the second DSC 144b in the second network.

[0127] In block 418, the second DSC 144b may receive the "reserve resource request" message from the DPC 146. In block 420, the second DSC 144b may use the information included in the received "reserve resources request" message to reserve the requested quantity of allocated resources for access and use by components in other networks. In block 422, the second DSC 144b may send a "resource reserved" communication message to the DPC 146 to confirm that the requested quantity of resources has been reserved and/or to identify the reserved resources.

[0128] In block 424, the DPC 146 may receive the "resource reserved" communication message from the second DSC 144b. In block 426, the DPC 146 may offer the reserved resources for auction and/or begin accepting resource bids on the reserved resources.

[0129] FIG. 5 illustrates a bidding procedure of the DSA method 300 that may be performed after the DPC 146 offers the reserved resources for auction and/or begins accepting resource bids on the reserved resources (e.g., after performing the operations of block 426 illustrated in FIG. 4).

[0130] With reference to FIG. 5, in block 500, the first DSC 144a in the first network may negotiate access to the reserved resources of second network by sending a resource bid (e.g., via a communication message) to the DPC 146. In block 502, the DPC 146 may receive the resource bid from the first DSC 144a.

[0131] In determination block 504, the DPC 146 may determine whether the received resource bid is to be accepted, which may be accomplished by determining whether the resource bid complies with the policies and rules of the DSA system and the requirements of the second network (e.g., is greater than a minimum amount, etc.). In response to determining that the resource bid received from the first DSC 144a is to be accepted (i.e., determination block 504 = "Yes"), in block 506, the DPC 146 may send an "accept bid" communication message to the first DSC 144a. In block 508, the first DSC 144a may receive the "accept bid" message and wait to receive resource access instructions. In block 510, the DPC 146 may send an "assign resources" communication message to the second DSC 144b in the second network.

[0132] In block 512, the second DSC 144b may receive the "assign resources"

communication message from the DPC 146. In block 514, the second DSC 144b may use the information included in the received "assign resources" message to assign all or portions of its reserved resources for access and use by components in the first network. In block 516, the second DSC 144b may generate a "resources access" communication message that includes information (e.g., access parameters, etc.) that may be used by a wireless device 102 (i.e., in the first network) to access the assigned resources, and the send the "resources access" message to the DPC 146. In block 518, the second DSC 144b may perform various operations to prepare for establishing a communication session/link to wireless device 102 in the first network, such as by configuring or preparing to receive a voice or data call.

[0133] In block 522, the DPC 146 may receive the "resources access" communication message from the second DSC 144b, and relay the resources access message to the first DSC 144a. In block 524, the first DSC 144a may receive the "resources access" message from the DPC 146. The received "resource access" message may include access parameters that may be used by the wireless devices 102 to access the allocated resources of the second network. In block 526, the first DSC 144a may send access parameters to wireless devices 102 that have communication sessions with the first network and/or to the wireless devices 102 that the first network has designated/marked for migration to other networks.

[0134] In block 528, the wireless devices 102 may receive the access parameters of second network from the first DSC 144a. In blocks 530 and 520, the wireless devices 102 and/or second DSC 142b may perform various operations to establish a

communication session/link between the wireless devices 102 and the second network. The second DSC 144b may then perform the operations of block 700 illustrated in FIG. 7 and discussed further below.

[0135] As mentioned above, in determination block 504, the DPC 146 may determine whether the resource bid received from the first DSC 144a is to be accepted. In response to determining that the resource bid received from the first DSC 144a is not to be accepted (i.e., determination block 504 = "No"), the DPC 146 may perform the operations of block 600 illustrated in FIG. 6.

[0136] With reference to FIG. 6, in block 600, the DPC 146 may send a "rejected bid" communication message to the first DSC 144a. In block 602, the first DSC 144a may receive the "rejected bid" message from the DPC 146. In determination block 604, the first DSC 144a may determine whether the first network will/should rebid for the resources. In response to determining that the first network will/should rebid for the resources (i.e., determination block 604 = "Yes"), in block 606, the first DSC 144a may send a new resource bid (e.g., in a resource bid communication message) to the DPC 146.

[0137] In block 608, the DPC 146 may receive the new resource bid (or rebid) from the first DSC 144a. In determination block 610, the DPC 146 may determine whether to accept the new resource bid, such as by determining whether the new resource bid complies with the policies and rules of the DSA system and the requirements of the second network. In response to determining that the new resource bid is to be accepted (i.e., determination block 610 = "Yes"), the DPC 146 may perform the operations of block 506 illustrated in FIG. 5. In response to determining that the new resource bid is to not be accepted (i.e., determination block 610 = "No"), the DPC 146 may perform the operations of block 600.

[0138] In response to determining that the first network should rebid for the resources (i.e., determination block 604 = "No"), in block 612, the first DSC 144a may send a "cancel resource request" communication message to the DPC 146. In block 614, the DPC 146 may receive the "cancel resource request" message from the first DSC 144a. In block 616, the DPC 146 may send a "release of resources" communication message to the second DSC 144b.

[0139] In block 618, the second DSC 144b may receive the "release of resources" message from the DPC 146. In block 620, the second DSC 144b may release the reserved resources so that they may be used by other networks. The second DSC 144b may then report the status of the allocated resources to DPC 146, which may be accomplished by performing the operations of block 316, which is illustrated in FIG. 3 and discussed above.

[0140] FIG. 7 illustrates settlement procedure of the DS A method 300 that may be performed after second network provides access to the secondary user wireless devices 102 in the first network (i.e., after performing the operations of block 520 illustrated in FIG. 5).

[0141] In block 700, the second DSC 144b may send invoices and payment instructions relating to the use of allocated resources by the first network to the DPC 146. In block 704, the DPC 146 may relay the received invoice and payment instructions to the first DSC 144a. In block 706, the first DSC 144a may receive the invoices and payment instructions, and settle the charges with the second network in block 718.

[0142] Optionally or alternatively, in block 708, the second DSC 144b may send usage parameters and payment instructions to the DPC 146. In block 710, the DPC 146 may receive the usage parameters and payment instructions from the second DSC 144b. In block 712, the DPC 146 may create an invoice for the access and use of the resources. In block 714, the DPC 146 may send the invoice to the first DSC 144a in the first network. In block 716, the first DSC 144a may receive the invoice and payment instructions, and perform various operations to settle the charges with second network in block 718.

[0143] In the various embodiments, the DPC 146 and DSC 144 components may be configured to communicate via an interface, which may be implemented in, or provided via, a dynamic spectrum arbitrage application part (DSAAP) protocol/module/component that is defined over the Xe and/or Xd reference points. The DSAAP may allow, facilitate, support, or augment communications between the DPC 146 and DSC 144 so as to improve the efficiency and speed of the DSA system and telecommunication network. In various embodiments, all or portions of the DSAAP module/component may be included in a DPC 146 component, a DSC 144 component, in a component that is independent of the DPC 146 and DSC 144 components, or any combination thereof. The DSAAP module/component may allow these and other DSA components to communicate information using the DSAAP protocol.

[0144] For example, the DSAAP may allow the DPC 146 and DSC 144 components to communicate specific information and/or perform operations that together provide various functions, including a DSC registration function, resource availability

advertisement function, bidding and allocation of resources functions, handing off lessee users to lessor network function, backoff from lessor networks function, error handling function (e.g., reporting of general error situations for which function specific error messages are not defined, etc.), DSC de-registration function, error indication function, DSC bidding success and failure indication functions, and DSC resource allocation withdrawal function. In various embodiments, these functions may be provided, implemented, or accomplished by configuring the DPC 146 and/or DSC 144 components to perform one or a combination of the DSAAP methods discussed below with reference to FIGs. 8A-17B. Using the DSAAP protocol and performing the DSAAP methods may include communicating via one or more DSAAP messages.

[0145] In various embodiments, the DSAAP messages used to communicate information between the DSC 144 and DPC 146 may include a DSC REGISTER REQUEST message, DSC REGISTER ACCEPT message, DSC REGISTER REJECT message, DSC DE-REGISTER message, DSC RESOURCE REGISTER REQUEST message, DSC RESOURCE REGISTER ACCEPT message, DSC RESOURCE REGISTER REJECT message, AVAILABLE BIDS REQUEST message, AVAILABLE BIDS RESPONSE message, AVAILABLE BIDS REJECT message, DSC BID REQUEST message, DSC BID ACCEPT message, DSC BID REJECT message, DSC BID OUTBID message, DSC BID WON message, DSC BID LOST message, DSC BID CANCELLED message, DSC BUY REQUEST message, DSC BUY ACCEPT message, DSC BUY REJECT message, DSC RESOURCES ALLOCATED message, DSC RESOURCES WITHDRAWN message, and/or DSC BACKOFF COMMAND message. Each of these messages may include, or may be associated with, criticality information, presence information, range information, and assigned criticality information. These messages and their contents are discussed in detail further below.

[0146] In various embodiments, the DSAAP methods may be performed in a DSA system that includes a first DSC server in a first telecommunication network (e.g., a lessee network), a second DSC server in second telecommunication network (e.g., a lessor network), and a DPC server that is outside of the first and second telecommunication networks. The first DSC may include first DSC processor coupled to the DPC via a first communication link, and the second DSC may include a second DSC processor coupled to the DPC via a second communication link. The second DSC may be coupled to an eNodeB in the second telecommunication network via third communication link. The first and second communication links may be defined over the Xd interface, and the third communication link is defined over the Xe interface.

[0147] FIGs. 8 A through 8C illustrate an embodiment DSAAP registration method 800 for registering a DSC 144 component with a DPC 146 so as to allow the DPC 146 to provide various services to the DSC 144 (e.g., advertizing a lessor DSC's 144 resources for bidding, allowing a lessee DSC 144 to bid for resources provided by other networks, etc.). In the examples illustrated in FIGs. 8A through 8C, the DSAAP registration method 800 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component. The operations DSAAP registration method 800 may be performed after, or in response to the DSC 144 or DPC 146 detecting that, an XE signaling transport or communication link has been established.

[0148] In operation 802 illustrated in FIGs. 8 A through 8C, the DSC 144 may initiate DSAAP registration method 800 by generating and sending a DSC REGISTER

REQUEST message to the DPC 146. In an embodiment, the DSC 144 may be configured to generate and/or send the DSC REGISTER REQUEST message in response to determining that it requires services from the DPC 146. For example, the DSC 144 may be configured to generate the DSC REGISTER REQUEST message in response to determining that its corresponding network (i.e., the network represented by the DSC) includes excess resources that may be allocated to other networks. As another example, the DSC 144 may be configured to generate the DSC REGISTER REQUEST message in response to determining that its network requires additional resources to provide adequate service to its existing wireless devices 102 in view of the current or expected future user traffic, network congestion, etc.

[0149] In various embodiments, the DSC 144 may be configured to generate the DSC REGISTER REQUEST message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a DSC Internet protocol (IP) address IE, a DSC type IE, a DSC PLMN-ID IE, PLMN type IE, and DSC resource update timer IE. The DSC PLMN-ID IE may include a PLMN-ID that is suitable for use in

identifying the network (e.g., E-UTRAN) that is associated with, or represented by, the DSC 144. The PLMN type IE may include information that is suitable for use in determining the type of network (e.g., public safety, commercial, etc.) that is represented by the DSC 144. The DSC IP address IE may include the IP address of a DSC 144 that is responsible for managing, maintaining, or providing the XE interface of the DSAAP.

[0150] In operation block 804 illustrated in FIGs. 8A and 8B, the DPC 146 may perform various registration operations (i.e., authenticating the DSC, storing DSC identifier information in memory, etc.) to register the DSC 144 with the DPC 146. In an

embodiment, as part of these registration operations, the DPC 146 may

overwrite/override an existing registration with a new registration, such as in response to receiving a duplicate DSC REGISTER REQUEST message (i.e. for an already registered DSC identified by the same unique DSC identity).

[0151] In operation block 806 illustrated in FIG. 8 A, the DPC 146 may determine that the registration operations were successful. In operation 808, the DPC 146 may generate and send a DSC REGISTER ACCEPT message to the DSC 144 to indicate the acceptance and registration of the DSC 144. In various embodiments, the DPC 146 may generate the DSC REGISTER ACCEPT message to include any or all of a message type information element (IE), a message ID IE, a DPC ID IE, a XEh signaling transport network layer (TNL) address IE, and a tunneling information IE. The XEh signaling TNL address IE may include an address value that is suitable for use in establishing to transport layer session. The tunneling information IE may include information that may used to encapsulate a different payload protocol, establish a secured communication through an untrusted or unverified network, carry a payload over an incompatible delivery-network, and/or to perform other similar tunneling operations.

[0152] To support XEh connectivity via/to the DPC 146, in operation block 810, the DSC 144 may use the address value included in the XEh signaling TNL address IE of the DSC REGISTER ACCEPT message establish a transport layer session. In an embodiment, the DSC 144 may be configured to establish the transport layer session in response to determining that the DSC REGISTER ACCEPT message includes an address value in the XEh signaling TNL address information element. In an embodiment, the DSC 144 may be configured to determine that the XEh connectivity via/to the DPC 146 is not supported or not required in response to determining that the XEh signaling TNL address information element is not present, null, empty, or not valid.

[0153] With reference to FIG. 8B, in operation block 812, the DPC 146 may determine that the registration operations performed as part of operation 804 failed. The DPC 146 may determine that registration failed in response to detecting any of a variety of conditions/events, including the failure to authenticate or authorize the DSC, network or component overload, DSC parameter mismatch, etc. In operation 814, the DPC 146 may generate and send a DSC REGISTER REJECT message to the DSC 144 to inform the DSC 144 that the registration failed and/or that the DPC 146 cannot register the DSC 144. In various embodiments, the DPC 146 may generate the DSC REGISTER REJECT message to include any or all of a message type information element (IE), a message ID IE, a cause IE, a criticality diagnostics IE, and a backoff timer IE. The cause IE may include information suitable for identifying a specific reason for the failure (e.g., overloaded, etc.) or for indicating that the reason for the failure is not known or is unspecified.

[0154] In operation block 816, the DSC 144 may perform various registration failure- response operations based on the information included in the received REGISTER REJECT message. For example, the DSC 144 may wait for a duration indicated in the backoff timer IE of the received REGISTER REJECT message before reattempting registration with that same DPC 146 in response to determining that the value of the cause IE in the received REGISTER REJECT message is set to "overload."

[0155] With reference to FIG. 8C, in operation block 852, the DSC 144 may start a register response timer in response to sending a DSC REGISTER REQUEST message to the DPC 146 (e.g., as part of operation 802). In operation block 854, the DSC 144 may determine that the register response timer expired before the DSC 144 received a DSC REGISTER RESPONSE message. In operation 856, the DSC 144 may resend the DSC REGISTER REQUEST message to the DPC 146 in response to determining that the timer expired before it received a corresponding DSC REGISTER RESPONSE message. In operation block 858, the DSC 144 may restart or reset the register response timer. In operation 860, the DPC may send a DSC REGISTER RESPONSE message to the DSC 144. In operation block 862, the DSC 144 may stop the register response timer in response to receiving the DSC REGISTER RESPONSE message.

[0156] FIGs. 9 A and 9B illustrate a DSAAP advertizing method 900 for advertizing resources that are available for bidding/buying so as to allow the DPC 146 to store, organize, and/or make those resources available for bidding/allocation via a financial brokerage platform. In the examples illustrated in FIGs. 9A and 9B, the DSAAP advertizing method 900 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component.

[0157] In operation block 902 illustrated in FIGs. 9 A and 9B, the DSC 144 may determine that there are resources available for allocation within cells serviced by that DSC 144. In operation block 904, the DSC 144 may generate and send a DSC

RESOURCE REGISTER REQUEST message to the DPC 146. In various embodiments, the DSC 144 may generate the DSC RESOURCE REGISTER REQUEST message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a DSC type IE, a PLMN-ID list IE, resource availability IE, resource availability start time IE, a data bandwidth IE, a list of grids IE, a bid or buy IE, a minimum bid amount IE, resource availability end time IE, a time of the day IE, a time duration IE, megabits per second (MBPS) IE, and a cell identity IE.

[0158] The DSC identity IE may include information that may be used by the DPC 146 to determine the identity of DSC 144. For example, the DSC identity IE may include a DSC pool ID, DSC instance information, and a PLMN-ID of the network that the DSC is managing or representing. The DSC pool ID may be a unique identifier of a pool of available resources and/or may be the same as or similar to MME pool IDs and MME IDs in 3 GPP EPC architecture.

[0159] The message ID IE may include a message identifier for the specific DSC

RESOURCE REGISTER REQUEST message sent from the DSC 144. The DSC 144 and DPC 146 may be configured to use the message ID IE as a sequence number to identify and correlate DSC RESOURCE REGISTER REQUEST, DSC RESOURCE REGISTER ACCEPT and/or DSC RESOURCE REGISTER REJECT messages.

[0160] The resource availability IE may include information suitable for use by the DPC 146 in determining the PLMN-ID of the network that is advertising resources for allocation and use by other networks. The DPC 146 may be configured to receive, store, and/or maintain resource availability IEs for multiple DSCs and/or for multiple different networks (i.e. different PLMN-IDs). As such, each resource availability IE may include information suitable for identifying one or more of the networks that are advertising resources.

[0161] The time of the day IE may include information suitable for use by the DPC 146 in determining the time of the day that the DSC 144 transmitted the DSC RESOURCE REGISTER REQUEST message. The time duration IE may include information that is suitable for use in determining a time period during which the resources are to be made available for bidding or buying.

[0162] The data bandwidth IE may include information suitable for use in determining the available bandwidth (e.g., in MBPS) for the time duration specified in the optional time duration IE. The DPC 146 may determine that the bandwidth specified in the MBPS IE is to be made available until that bandwidth is consumed by the winning bidder or buyer in response to determining that the time duration IE is not included in the received DSC RESOURCE REGISTER REQUEST message (or in response to determining that the time duration IE does not include a valid value).

[0163] The list of grids IE may include information suitable for use in determining grid identifiers for the locations of the network bandwidth that is to be made available for bidding or buying. The cell identity IE may include information suitable for use in determining the individual cells within each grid (identified by grid ID and cell ID) that have available resources offered for bidding or buying as part of the offer in the DSC RESOURCE REGISTER REQUEST message. The minimum bid amount IE may include a monetary amount in a denomination or currency, such as in United States Dollars (USD).

[0164] In operation block 906 illustrated in FIG 9A, the DPC 146 may accept the DSC's 144 resources for bidding. In operation 908, the DPC 146 may generate and send a DSC RESOURCE REGISTER RESPONSE or DSC RESOURCE REGISTER ACCEPT message to the DSC 144 to acknowledge that the resources were accepted. In various embodiments, the DPC 146 may generate the DSC RESOURCE REGISTER message to include any or all of a message type information element (IE), a bid ID IE, and a message ID IE. The message ID IE may include the same message identifier value that is included in the received DSC RESOURCE REGISTER REQUEST message. The DPC 146 and/or DSC may be configured to use the value of the message ID IE to identify and correlate the DSC RESOURCE REGISTER REQUEST and DSC RESOURCE

REGISTER ACCEPT messages. In operation block 910, the DPC 146 may store, organize, and/or make the network resources available for bidding or buying via the financial brokerage platform.

[0165] In operation 912 illustrated in FIG. 9B, the DPC 146 may reject the DSC

RESOURCE REGISTER REQUEST message and/or reject for bidding the resources identified in the received DSC RESOURCE REGISTER REQUEST message. The DPC 146 may reject the message/resources for a variety of reasons and/or in response to detecting any of a variety of events or conditions. For example, the DPC 146 may reject the resources in response to determining that the DPC 146 is not accepting resources from any operator, is not accepting resources for the specific operator identified in the received message, is not accepting the resources identified in the message, that the DPC is overloaded, that there is insufficient memory to store and service the resources available for bidding, etc. The DPC 146 may also reject the resource available message in response to determining that an administrator of the DPC 146 has disabled further bidding from the specific PLMN-ID included in the DSC RESOURCE REGISTER REQUEST message, from all the networks (e.g., all the PLMN-IDs), etc.

[0166] In operation 914 illustrated in FIG. 9B, the DPC 146 may generate and send a DSC RESOURCE REGISTER REJECT message to the DSC 144. In various

embodiments, the DPC 146 may generate the DSC RESOURCE REGISTER REJECT message to include any or all of a message type information element (IE), a message ID IE, a cause IE, and a criticality diagnostics IE. The DPC 146 may also generate the DSC RESOURCE REGISTER REJECT message to include a message ID IE that includes a value that is the same as the message identifier included in the DSC RESOURCE

REGISTER REQUEST message received from DSC 144. The DPC 146 and/or DSC 144 may be configured to use the value of the message ID IE to identify and correlate the DSC RESOURCE REGISTER REQUEST and DSC RESOURCE REGISTER REJECT messages.

[0167] In operation block 916, the DSC 144 may perform various resource registration failure response operations based on information included in the received DSC

RESOURCE REGISTER REJECT message. For example, the DSC 144 may use the information included in the DSC RESOURCE REGISTER REJECT message to determine whether to reattempt resource registration with the DPC 146, attempt to register the resources with another DPC, reattempt the registration with different resources, or perform any of the other DSC operations discussed in this application.

[0168] FIGs. 10A and 10B illustrate a DSAAP method 1000 for communicating a list of available resources in accordance with an embodiment. DSAAP method 1000 may be performed to inform lessee networks of the resource bids or resources that are available for bidding/buying. In the examples illustrated in FIGs. 10A and 10B, the DSAAP method 1000 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component. In an embodiment, a lessee DSC 144 may be configured to perform DSAAP method 1000 to retrieve/receive a list of available resources prior to that DSC 144 bidding on, or requesting to lease or purchase, resources from the DPC 146.

[0169] In operation 1002 illustrated in FIGs. 10A and 10B, a lessee DSC 144 may generate and send an AVAILABLE BIDS REQUEST message to the DPC 146 to request information on the resource bids that are available for allocation from lessor network(s) for bidding or buying. In various embodiments, the lessee DSC 144 may generate the AVAILABLE BIDS REQUEST message to include any or all of a sequence number information element (IE), a message type IE, a PLMN list IE that includes one or more PLMN-ID IEs, a grid ID list IE that includes one or more Grid ID IEs.

[0170] In an embodiment, the lessee DSC 144 may be configured to request specific resources from a specific network by generating the AVAILABLE BIDS REQUEST message to include the PLMN-ID of the desired network, which may be included in the PLMN-ID IE of the PLMN list IE in the AVAILABLE BIDS REQUEST message.

[0171] In an embodiment, the lessee DSC 144 may be configured to request resources from any available network by not populating the PLMN list IE in the generated

AVAILABLE BIDS REQUEST message and/or by generating the AVAILABLE BIDS REQUEST message to not include a PLMN list IE and/or PLMN-ID value.

[0172] In an embodiment, the lessee DSC 144 may be configured to request resources from a specific grid within a lessor network by generating the AVAILABLE BIDS REQUEST message to include the grid IDs of the desired grids, which may be included in the grid ID IE of the grid ID list IE in the AVAILABLE BIDS REQUEST message.

[0173] In an embodiment, the lessee DSC 144 may be configured to request resources from any or all grids within a specified PLMN-ID in PLMN-ID IE grid by not populating the grid ID list IE in the generated AVAILABLE BIDS REQUEST message and/or by generating the AVAILABLE BIDS REQUEST message to not include a grid ID.

[0174] In operation block 1004 illustrated in FIGs. 10A and 10B, the DPC 146 may determine whether the PLMN-ID(s) and grid ID(s) included in the received

AVAILABLE BIDS REQUEST message are valid. If the PLMN-ID(s) and grid ID(s) are incorrect, in operation block 1005, the DPC 146 may determine a reason code for the error/incorrect values. In operation block 1006, the DPC 146 may determine whether there are resources/bids available for each grid identified in the received AVAILABLE BIDS REQUEST message or for all the available grids (e.g., when the grid ID list IE in the received AVAILABLE BIDS REQUEST message not include valid values). [0175] In operation 1008 illustrated in FIG. 10A, the DPC 146 may generate and send an AVAILABLE BIDS RESPONSE message to the DSC 144. The DPC 146 may be configured to generate the AVAILABLE BIDS RESPONSE message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a PLMN-ID grid cell bid info list IE, a sequence number IE, a PLMN list IE that includes one or more PLMN-ID IEs, and a grid list IE. In an embodiment, the PLMN list IE and grid list IE may be included in the PLMN-ID grid cell bid info list IE. In an embodiment, the grid list IE may include one or more cell ID list IEs that include one or more cell ID IEs.

[0176] In various embodiments, the DPC 146 may generate the AVAILABLE BIDS RESPONSE message to also include any or all of an absolute radio-frequency channel number (ARFCN) IE, a channel bandwidth IE, a megabit or megabyte IE for identifying total available bandwidth, a MBPS IE for identifying the peak data rate for the resource, a resource available time IE, a resource expiration time IE, a bid/buy IE, a bid/buy expiry time IE, a minimum bid amount IE, and a buy price IE. The DPC 146 may generate the AVAILABLE BIDS RESPONSE message to include such information for each PMLN, each resource, each grid, and/or each cell identified in the message.

[0177] In an embodiment, the DPC 146 may be configured to generate the AVAILABLE BIDS RESPONSE message to include the list of PLMN-ID, lists of grid ID(s) within each PLMN, and the available resources/bids within each grid in response to determining that there are bids for resources available for auction.

[0178] In an embodiment, the DPC 146 may be configured to generate the AVAILABLE BIDS RESPONSE message to include the message type and sequence number IEs (or valid values for these IEs) in response to determining that there no resources/bids for resources available for auction by that DPC 146 for the relevant networks/PLMN-IDs. In an embodiment, the DPC 146 may be configured to generate the AVAILABLE BIDS RESPONSE message to include a sequence number IE having the same value as in the sequence number IE included in the received AVAILABLE BIDS REQUEST message. In an embodiment, the DSC 144 may be configured to use the sequence number IEs in these request and response messages to correlate the messages.

[0179] In an embodiment, the DPC 146 may be configured to generate the AVAILABLE BIDS RESPONSE message to include a PLMN list IE that includes a PLMN-ID and grid ID list IE. The grid ID list IE may include a list of cells available for auction within the grid. The cell ID list IE may include a cell ID, and for each cell, the ARFCN, channel bandwidth, total available bandwidth, peak data rate allowed, the time of day (e.g., in UTC) when the resources are available and when they expire/end, whether it' s a bid or buy type auction, minimum bid amount or buy price, bid expiry time (e.g., in UTC), and other similar information.

[0180] In operation block 1010, the DSC 144 may use the information included in the AVAILABLE BIDS RESPONSE message to identify the resources that are available for bidding, determine whether the DSC 144 will submit a bid for the available resources, determine the resources for which the DSC 144 will submit bids, and/or perform other similar operations.

[0181] With reference to FIG. 10B, in operation 1012, the DPC 146 may reject the AVAILABLE BIDS REQUEST message received from lessee DSC 144 by generating and sending a AVAILABLE BIDS REJECT message to the DSC 144. The DPC 146 may be configured to reject the AVAILABLE BIDS REQUEST message in response to determining (e.g., as part of operation 1004 or 1006) that one or more of the PLMN-IDs supplied in the request message is not from any of the known networks, that one or more of the Grid IDs supplied in the request message is not valid with respect to the supplied PLMN-ID, and/or that there are no resources/bids available in the relevant grids.

[0182] In an embodiment, the DPC 146 may be configured to generate the AVAILABLE BIDS REJECT message to include a message type information element (IE), a message ID IE, a cause IE, a criticality diagnostics IE, and a sequence number IE. The cause IE may include a reason code (e.g., Invalid PLMN-ID, Invalid Grid ID, etc.) for the rejection of the available bids request, which may be determined in operation block 1005. The sequence number IE may include the same sequence number value that was included in the AVAILABLE BIDS REQUEST message received from lessee DSC 144. As such, the DPC 146 and/or DSC 144 may be configured to use sequence number IEs in the request and response messages to correlate those messages.

[0183] In operation block 1014, the DSC 144 may use the information included in the received AVAILABLE BIDS REJECT message to perform various failure-response operations. For example, the DSC 144 may determine whether to send another

AVAILABLE BIDS REQUEST message to the DPC 146, determine whether to send another AVAILABLE BIDS REQUEST message to a different DPC, etc.

[0184] FIGs. 11 A and 1 IB illustrate a DSAAP bidding method 1100 of bidding for DSC resources, which allows different lessee networks to bid for resources that are available from lessor networks. In the examples illustrated in FIGs. 11 A and 1 IB, the DSAAP method 1100 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component.

[0185] In an embodiment, the DSC 144 and/or DPC 146 may be configured to perform DSAAP method 1100 after the DSC 144 retrieves the list of resources that are available for bidding (e.g., after performing DSAAP method 1000). In various embodiments, the DSC 144 and/or DPC 146 may be configured to perform DSAAP method 1100 continuously or repeatedly until the expiration of a bidding time. In an embodiment, the DPC 146 may be configured to select a winning bid (i.e., bid highest bid value) at the expiry of a bidding time.

[0186] In operation 1102 of method 1100 illustrated in FIGs. 11A and 11B, the lessee DSC 144 may generate and send a DSC BID REQUEST message to the DPC 146 to bid for one or more of the resource that are determined to be available from a lessor network, (i.e., one or more of resources included the list of resources obtained via the performance of method 1000). The lessee DSC 144 may be configured to generate the DSC BID REQUEST message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a DSC type IE, bid ID IE, a PLMN-ID IE, and a bid amount IE. The bid ID IE may include information suitable for identifying a specific resource for which the lessee DSC 144 places a bid. The PLMN-ID IE may include information suitable for use in identifying the PLMN-ID of the network associated with the resources identified in the bid ID IE. The bid amount IE may include a monetary amount in a currency (e.g., USD), or the bid value.

[0187] In an embodiment, the lessee DSC 144 may be configured to generate the DSC BID REQUEST message to include a bid amount IE value that is greater than a minimum bid amount specified in a bid listing for the specific resource/bid ID. In an embodiment, the lessee DSC 144 may be configured to obtain the minimum bid amount and/or bid listing from the received AVAILABLE BIDS RESPONSE message (e.g., the message sent as part of operation 1008 illustrated in FIG. 10A).

[0188] In operation block 1104 illustrated in FIG. 11 A, the DPC 146 may use the information included in the received DSC BID REQUEST message to determine whether the bid (resource bid) is valid and is to be accepted, such as by determining whether the bid complies with the policies and rules of the DSA system and the requirements of the lessor network. In operation 1106, the DPC 146 may generate and send DSC BID ACCEPT message to the DSC in response to determining that the bid is valid and/or is to be accepted. The DPC 146 may be configured to generate the DSC BID ACCEPT message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, and other information suitable for informing the DSC 144 that the bid has been determined to be valid and/or has been accepted.

[0189] It should be noted that, in the example discussed above, the DSC BID ACCEPT message informs the DSC 144 that the bid is valid/accepted, not that lessee DSC 144 has won the bid. The winning lessee DSC may be informed via DSC BID WON message when the DPC 146 determines that the bid time has expired and that lessee DSC is the highest bidder at the time of bid expiry. Similarly, the DPC 146 may inform lessee DSC(s) who participated in the bidding process but submitted losing bids that they did not submit a winning bid via a DSC BID LOST message. The DSC BID WON message and DSC BID LOST message are discussed in more detail further below.

[0190] With reference to FIG. 1 IB, in operation block 1108, the DPC 146 may use the information included in the received DSC BID REQUEST message to determine that the bid is not valid and is not to be accepted. For example, the DPC 146 may use the received information to determine that the bid does not comply with the policies/rules of the DSA system and/or does not comply with the requirements of the lessor network (e.g., does not meet the minimum asking price, etc.). As further examples, the DPC 146 may be configured to determine that the bid is not valid or is not to be accepted in response to determining that the bid amount specific in bid amount IE in the BID

REQUEST message is not higher than the minimum bid, that the bid amount is not the highest among currently offered bids, that the bid id included in the bid ID IE is invalid, or that the bid/resource is no longer available for bidding (e.g., due to expiry, end of auction, bid withdrawn or invalid bid id).

[0191] In operation 1110, the DPC 146 may generate and send a DSC BID REJECT message to the DSC 144. The DPC 146 may be configured to generate the DSC BID REJECT message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, a cause IE, and a criticality diagnostics IE. The bid ID IE in the DSC BID REJECT message may include the same value as the bid identifier included in the received DSC BID REQUEST message. The cause IE may include a reason code identifying a reason for the rejection of the bid (e.g., minimum bid not met, outbid, bid not found, etc.). In operation block 1112, the DSC 144 may use information included in the received DSC BID REJECT message to perform various bid request failure-response operations, such as operations to determine whether to rebid for the resources, to generate a new DSC BID REQUEST message that includes a valid bid ID, etc. [0192] FIGs. 12 A through 12D illustrate a DSAAP notification method 1200 of informing participating networks of the results of the bidding operations. That is, DSAAP notification method 1200 may be performed to inform DSCs 144 of a result of an auction (e.g., that they submitted a winning bid, that they have been outbid, that they submitted a losing bid, that the auction was cancelled, etc.). In the examples illustrated in FIGs. 12A- 12D, the DSAAP notification method 1200 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component.

[0193] DSAAP notification method 1200 may be performed after the DPC 146 notifies the DSC 144 that the bid has been accepted (e.g., after operation 1106 illustrated in FIG. 11). The DSAAP notification method 1200 also may be performed after the expiry of a bidding time and/or in response to the DPC 146 detecting an event or condition (e.g., new bid received, outbid, etc.).

[0194] In operation block 1202 illustrated in FIG. 12A, the DPC 146 may determine that the bid amount specific in bid amount IE in the last, latest, or most current BID

REQUEST message accepted from the DSC 144 is not the highest among the current bids. In operation 1204, the DPC 146 may generate and send a DSC BID OUTBID message to the DSC 144 to inform the lessee DSC 144 that its earlier bid was outbid by a higher bid from another lessee DSC and/or that their earlier bid is no longer valid. In various embodiments, the DPC 146 may generate the DSC BID OUTBID message to include any or all of a message type information element (IE), a message ID IE, a cause IE, a bid info IE, a criticality diagnostics IE, a DSC ID IE and a BID ID IE.

[0195] The DSC ID IE may include information that is suitable for use in identifying the specific lessee DSC 144. The BID ID IE may include a bid ID suitable for use in identifying the submitted bid that has been outbid. In operation block 1206, the lessee DSC 144 may perform various bid-outbid failure-response operations, such as by determining whether to submit a higher bid for the resources to that DPC 146, to submit a bid to a different DPC 146, to drop existing calls to free bandwidth, etc.

[0196] With reference to FIG. 12B, in operation block 1210, the DPC 146 may determine that the bidding time has expired and that the bid amount specific in bid amount IE in the last, latest, or most current BID REQUEST message accepted from the DSC 144 is the highest among the current bids. In operation 1212, the DPC 146 may generate and send a DSC BID WON message to the DSC 144 to inform the lessee DSC 144 that their earlier bid is the winning bid. In various embodiments, the DPC 146 may generate the DSC BID WON message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, a bid info IE, a DSC ID IE, and original bid details such as bandwidth, MBPS, duration and the winning bid amount, etc. The DSC ID IE may include information that is suitable for use in identifying the specific lessee DSC 144. The bid ID IE may include a bid identifier suitable for identifying the bid that won the resource auction/bidding operations.

[0197] In operation block 1214, the winning lessee DSC 144 may wait to receive DSC RESOURCES ALLOCATED message from the DPC 146 before scheduling its network equipment and device (e.g., wireless devices) to start using the resources and/or for the resources to be made available for use (i.e. scheduling for the time of day when the resources will be ready for use by the winning lessee network). In operation block 1216, the DPC 146 may close the auction, such as by rejecting further bids from other networks for the resources won by the bid submitted by lessee DSC 144.

[0198] With reference to FIG. 12C, in operation block 1220, the DPC 146 may determine that the bidding time has expired and that the bid amount specific in bid amount IE in the last, latest, or most current BID REQUEST message accepted from the DSC 144 is not the highest among the current bids. In operation 1222, the DPC 146 may generate and send a DSC BID LOST message to the DSC 144 to inform the lessee DSC 144 that its earlier bid has not won the bid and the auction/bid is closed due to another lessee DSC winning the auction. In various embodiments, the DPC 146 may generate the DSC BID LOST message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, and a DSC ID IE. The DSC ID IE may include information that is suitable for use in identifying the specific lessee DSC 144 that submitted the losing bid and/or to which the DSC BID LOST message is sent. The bid ID IE may include a bid identifier suitable for use in identifying the submitted bid.

[0199] In operation block 1224, the lessee DSC 144 may perform various failure response operations, such as determining whether to submit a bid to for other available resources, whether to drop existing calls to free up resources, etc. In operation block 1226, the DPC 146 may close the auction and/or allow the losing lessee DSCs to bid for other available resources.

[0200] With reference to FIG. 12D, in operation block 1230, the DPC 146 may determine that the auction for a network resource that the DSC 144 previously submitted a bid has been cancelled. For example, the DPC 146 may determine that the auction has been withdrawn by lessor network operator or that the auction has been cancelled by DPC operator for administrative reasons. In operation 1232, the DPC 146 may generate and send a DSC BID CANCELLED message to the DSC 144 to inform the lessee DSC 144 that the auction has been cancelled. In various embodiments, the DPC 146 may generate the DSC BID CANCELLED message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, a DSC ID IE, and a cause IE. The DSC ID IE may include information that is suitable for use in identifying the specific lessee DSC 144. The bid ID IE may include a bid identifier suitable for use in identifying the resource/bid for which the auction has been cancelled. The cause IE may include a reason code for the bid's cancellation (e.g., auction withdrawn, auction cancelled, etc.). In operation block 1234, the lessee DSC 144 may perform various failure -response operations, such as by determining whether to submit a bid to a different DPC 146, to drop calls, etc. [0201] FIGs. 13 A and 13B illustrate a DSAAP purchase method 1300 of allowing a lessee network to make an immediate (or near immediate) purchase and/or claim of use for a resource that is made available for allocation by a lessor network. In the examples illustrated in FIGs. 13 A and 13B, the DSAAP purchasing method 1300 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component. In an embodiment, the DSC 144 and DPC 146 may be configured to perform DSAAP method 1300 after the DSC 144 retrieves/receives a list of resources that are available for purchase (e.g., after performing DSAAP method 1000 discussed above with reference to FIG. 10).

[0202] In operation block 1302 illustrated in FIGs. 13A and 13B, the lessee DSC 144 may identify and select a specific resource for immediate purchase from the list of resources (e.g., list of resources obtained from performing DSAAP method 1000 discussed above). In various the embodiments, the lessee DSC 144 may select a resource that is scheduled for bidding, that is currently being auctioned, that is only made available for immediate purchase, etc. In operation 1304, the DSC 144 may generate and send DSC BUY

REQUEST message to the DPC 146 to request to buy the identified/selected resources from a lessor network.

[0203] In various embodiments, the DSC 144 may generate the DSC BUY REQUEST message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a DSC type IE, a bid ID IE, a buy amount IE, and a PLMN-ID IE. The PLMN-ID IE may include information suitable for use in identifying the PLMN-ID of the network associated with the bid, which may identified via the bid ID IE. The buy amount IE may include the amount (e.g., in USD) of the bid (i.e., bid value) submitted by the lessee DSC 144.

[0204] In an embodiment, the DSC 144 may be configured to generate the DSC BUY REQUEST message to include a buy amount value that is equal to an amount identified via a buy amount IE in a listing for the bid ID included in a received AVAILABLE BIDS RESPONSE message (which is discussed above with reference to FIG. 10).

[0205] In operation block 1306 illustrated in FIG. 13 A, the DPC 146 may use the information included in the received DSC BUY REQUEST message to identify the requested resource, the network associated with the request resource, whether the requested resource is currently being auctioned, whether the requested resource has been made available for immediate purchase, a minimum purchase amount requested for the immediate purchase of that resource, and/or whether the buy amount included in the received DSC BUY REQUEST message is equal to (or greater than) the requested purchase amount. In the example illustrated in FIG. 13 A, as part of operation block 1306, the DPC 146 determines that the buy amount included in the received DSC BUY REQUEST message is greater than or equal to the requested purchase amount.

[0206] In operation 1308, the DPC 146 may generate and send a DSC BUY ACCEPT message to the DSC 144 to inform the lessee DSC 144 that it has successfully

purchased/leased the resource for use. In various embodiments, the DPC 146 may generate the DSC BUY ACCEPT message to include any or all of a message type information element (IE), a message ID IE, and a bid ID IE. In operation block 1310, the DPC 146 may terminate, stop, or close an active auction for that resource and/or perform similar operations so that the resource is no longer available for bidding or buying by other lessee DSCs.

[0207] With reference to FIG. 13B, in operation block 1312, the DPC 146 may use the information included in the received DSC BUY REQUEST message (e.g., as part of operation 1304) to determine that the bid (buy request) is to be rejected. For example, the DPC 146 may determine that the buy amount specific in buy amount IE in the received DSC BUY REQUEST message is less than the requested purchase amount. As another example, the DPC 146 may determine that the bid ID value included in the bid ID IE is invalid, or that the resource/bid is no longer available for bidding (due to expiry, end of auction, bid withdrawn, invalid bid ID, etc.).

[0208] In operation 1314, the DPC 146 may generate and send a DSC BUY REJECT message to the DSC 144. In various embodiments, the DPC 146 may generate the DSC BUY REJECT message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE and a cause IE. The value of the bid ID IE may be the same as the bid identifier included in the DSC BUY REQUEST message received as part of operation 1304. The cause IE may include a reason code for the rejection of the buy request (e.g., requested purchase price not met, bid not found, etc.). In operation block 1316, the DSC 1316 may perform various failure-response operations, such as determining whether to submit a new purchase request with a higher bid amount. In operation block 1318, the DPC 146 perform various operations so to make that resource available for bidding or buying by other lessee DSCs.

[0209] FIGs. 14A and 14B illustrate a DSAAP resource allocation method 1400 of allocating resources in a lessor network for access and use by components in a lessee network. In the examples illustrated in FIGs. 14 A and 14B, the DSAAP resource allocation method 1400 is performed by processing cores in a DPC 146 component, a lessee DSC 144a component, and a lessor DSC 144b component, each of which may include all or portions of a DSAAP module/component.

[0210] In operation block 1402 illustrated in FIGs. 14A and 14B, the DPC 146 may determine that the lessee DSC 144a has successfully purchased or won an auction for a resource in a lessor network represented by the lessor DSC 144b. In operation 1404 illustrated in FIG. 14A, the DPC 146 may generate and send a DSC BID SUCCESS message to the lessor DSC 144b to inform the lessor network that one or more of its allocated resources/bids has been won by the lessee DSC 144a.

[0211] In various embodiments, the DPC 146 may generate the DSC BID SUCCESS message to include any or all of a message type information element (IE), a message ID IE, a cause IE, and a criticality diagnostics IE. In a further embodiment, the DPC 146 may be configured to generate the DSC BID SUCCESS message to also include any or all of a bid ID IE, a DSC ID IE, and a bid value IE. These additional information elements may be used to communicate information regarding the winning bid. For example, the bid ID IE may include a bid ID that corresponds to the bid that successfully participated in and won the auction for the resources. The DSC ID IE may include the DSC ID of the auction winner (i.e., the lessee DSC 144a). The bid value IE may include the winning bid amount and/or the purchase price of the resources.

[0212] In operation 1404, the lessor DSC 144b may generate and send DSC

RESOURCES ALLOCATED message to the DPC 146 to allocate/commit the resources for access and use by components in the lessee network. The lessor DSC 144b may be configured to generate DSC RESOURCES ALLOCATED message to include any or all of a message type information element (IE), a message ID IE, a bid iD, a PLMN-ID Grid ID Cell ID list IE, a PLMN-ID IE, a grid ID IE, list of cell IDs IE, and various auction/resource details (e.g., bandwidth, MBPS, duration, etc.). In an embodiment, the PLMN-ID IE, a grid ID IE, and list of cell IDs IE may be included in the PLMN-ID Grid ID Cell ID list IE. The PLMN-ID IE may include the PLMN-ID of the lessor network allocating the resources, which may be the same PLMN-ID/network identified in the winning bid. The grid ID IE and list of cell IDs IE may include information suitable for identifying the grid/cells associated with the resources. These values may be the same as the grid/cell values included in the winning bid.

[0213] In operation 1406, the DPC 146 may forward the received DSC RESOURCES ALLOCATED message to the winning lessee DSC 144a to enable the lessee DSC 144a to start using the allocated resources of lessor network resources. In operation block 1408, the lessee DSC 144a may schedule its network equipment to start using lessor network resources from the time of day specified as part of the bid and/or included in the received DSC RESOURCES ALLOCATED message. [0214] With reference to FIG. 14B, in operation block 1410, the lessor DSC 144b may determine that the resources submitted for auction should be withdrawn and/or to forego allocating the submitted resources to a winner of the auction. The lessor DSC 144b may determine to withdraw the resources after the DPC 146 determines that lessee network purchased or won an auction for those resources and/or for any of a variety of reasons (e.g., unforeseen or administrative reasons, etc.).

[0215] In operation 1412, the lessor DSC 144b may generate and send a DSC

RESOURCES WITHDRAWN message to the DPC 146 to withdraw the resources. The lessor DSC 144b may generate the DSC RESOURCES WITHDRAWN message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, a cause IE, and a PLMN-ID Grid ID Cell ID list IE. The bid ID IE may include information that is suitable for use in identifying the bid. The cause IE may include a reason code that describes the reason for withdrawal of resource allocations (e.g., resources not available, resources withdrawn, administrative, etc.).

[0216] In operation 1414, the DPC 146 may forward the received DSC RESOURCES WITHDRAWN message to the lessee DSC 144a, which may have submitted a winning bid for the withdrawn resources. In operation block 1416, the lessee DSC 144a may perform various failure -response operations, such as determining whether to participate in another auction, whether to bid on a different resource, determining whether to drop calls to free up resources, etc.

[0217] FIGs. 15A and 15B illustrate an embodiment DSAAP backoff method 1500 of selectively handing over a wireless device from a lessor network back to the lessee's network to which the wireless device subscribes (i.e. its home PLMN). In the examples illustrated in FIGs. 15 A and 15B, the DSAAP backoff method 1500 is performed by processing cores in a DPC 146 component, a lessee DSC 144a component, and a lessor DSC 144b component, each of which may include all or portions of a DSAAP module/component. [0218] In operation block 1502 illustrated in FIGs. 15A and 15B, the lessor DSC 144b may determine that its network resources from the cells that are part of a prior auction are in congestion. That is, the lessor DSC 144b may determine that it requires access or use of its allocated resources. In operation 1504, the lessor DSC 144b may generate and send a DSC BACKOFF COMMAND message to the DPC 146 to selectively handover wireless device(s) that are using the allocated resources of the lessor network back to the lessee network (i.e. its home PLMN).

[0219] The lessor DSC 144b may be configured to generate the DSC BACKOFF

COMMAND message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, a UE identity IE, a measurement report IE, handoff cell information IE, a cause IE, and a DSC backoff response timer IE.

[0220] The UE identity IE may include information suitable for use in determining identity related information for the wireless device (or UE), such as the international mobile subscriber identity (IMSI) of the wireless device or its network.

[0221] The measurement report IE may include the latest, last, or most recent

measurement report E-UTRAN RRC message received by the lessor network for the identified wireless device (i.e., the wireless devices that are requested to backoff to lessee network).

[0222] The bid ID IE may include a bid ID value corresponding to the bid that successfully participated in and completed/won the auction. The bid ID may be used to identify the auction/contract associated with the backoff operations (i.e., the

auction/contract for which the resources were allocated).

[0223] In an embodiment, the lessor DSC 144b may be configured to determine whether there are multiple bid IDs that correspond to a congested cell. In an embodiment, the lessor DSC 144b may be configured to select the bid ID value from a plurality of bid IDs in response to determining that there are multiple bid IDs that correspond to a congested cell. In various embodiments, the lessor DSC 144b may be configured to select the bid ID value based on an operator policy provisioned at the lessor DSC 144b, based on a previous agreement, based on a policy/rule previously negotiated by lessor and lessee network operators, etc.

[0224] In operation 1506, the DPC 146 may forward the received DSC BACKOFF COMMAND message to the lessee DSC 144a. In operation block 1508, the lessee DSC 144a may use the information in the UE identity IE of the received DSC BACKOFF COMMAND message identify wireless device(s) that are to be subjected to the backoff operations (i.e., the wireless devices that are to be handed back).

[0225] In operation block 1510, the lessee DSC 144a may use the information included in the measurement report IE of the received DSC BACKOFF COMMAND message to determine, identify, and/or select a target cell (within lessee network) to which the identified wireless device(s) are to be handed over (the lessor network may have previously enabled measurement reporting from the wireless devices, such as when they attached, or were handed over, to the lessor network.)

[0226] In operation 1512, the lessee DSC 144a may generate and send a DSC BACKOFF RESPONSE message to the DPC 146. The lessee DSC 144a may be configured to generate the DSC BACKOFF RESPONSE message to include any or all of a message type information element (IE), a message ID IE, a bid ID IE, a UE identity IE, a handoff cell information IE, and a cause IE. In an embodiment, the lessee DSC 144a may be configured to generate the DSC BACKOFF RESPONSE message to include the cause IE (or a value for the cause IE) in response to determining that a suitable target cell (within lessee network) could not be identified or selected for the handed over. The value of the cause IE may identify a cause of the failure, such as network overload, no appropriate target cell found, or unknown wireless device/UE. In an embodiment, the lessee DSC 144a may be configured to generate the DSC BACKOFF RESPONSE message to include a value (e.g., target cell information) for the handoff cell information IE in response to successfully identifying a target cell (within lessee network) to which the wireless device may be handed over.

[0227] In operation 1514, the DPC 146 may identify the lessor DSC 144a based on the bid id IE included in the received DSC BACKOFF RESPONSE message, and forward the received DSC BACKOFF RESPONSE message to the lessor DSC 144b. In operation block 1516, the lessor DSC 144b may determine whether the received DSC BACKOFF RESPONSE message includes a handoff cell information IE (or a valid value for the handoff cell information IE). In response to determining that the received DSC

BACKOFF RESPONSE message includes a handoff cell information IE (or a valid value for the handoff cell information IE), in operation block 1518, the lessor DSC 144b may use the target cell information included in the handoff cell information IE to encode a HANDOVER REQUIRED message. In operation block 1520, the lessor DSC 144b may and initiate S 1 based handover procedure to handover the wireless device from lessor network to lessee network.

[0228] With reference to FIG. 15B, in operation block 1552, the lessor DSC 144b may determine that the DPC 146 has not responded to the DSC BACKOFF COMMAND message (sent as part of operation 1504) within a time period identified in the DSC backoff response timer IE included in the DSC BACKOFF COMMAND message.

Alternatively or additionally, in operation block 1554, the lessor DSC 144b may determine that there is significant or severe network congestion or administrative reasons that require withdraw of the allocation of all remaining network resources pertaining to the resources/bid id included or identified in the DSC BACKOFF COMMAND message.

[0229] In operation 1556, the lessor DSC 144b may generate and send a DSC

RESOURCES WITHDRAWN message to the DPC 146. In operation 1558, the DPC 146 may forward the received DSC RESOURCES WITHDRAWN message to the lessee DSC 144a to withdraw the allocation of the remaining network resources. In operation block 1560, the lessee DSC 144a may perform various resource withdrawn failure- response operations, such as dropping calls, determining whether to bid for new resources, etc.

[0230] FIG. 16A illustrates an embodiment DSC initiated DSAAP de-registration method 1600 for terminating operations. In the example illustrated in FIG. 16A, the DSC initiated DSAAP de-registration method 1600 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component.

[0231] In operation block 1602, the DSC 144 may determine that it needs to terminate DSA operations. In operation 1604, the DSC 144 may generate and send a DSC DE- REGISTER message to the DPC 146. The DSC 144 may be configured to generate the DSC DE-REGISTER message to include any or all of a message type information element (IE), a message ID IE, a backoff timer IE, and a cause IE that identifies a cause for the termination of operations. In operation block 1606, the DPC 146 may clear all the related resources associated with the DSC 144 and/or perform other similar operations to de-register the DSC 144 in response to receiving the DSC DE-REGISTER message.

[0232] FIG. 16B illustrates an embodiment DPC initiated DSAAP de-registration method 1650 for terminating operations. In the example illustrated in FIG. 16B, the DPC initiated DSAAP de-registration method 1650 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component.

[0233] In operation block 1652, the DPC 146 may determine that it needs to terminate DSA operations with the DSC 144. In operation 1654, the DPC 146 may generate and send a DSC DE-REGISTER message to the DSC 144. The DPC 146 may be configured to generate the DSC DE-REGISTER message to include any or all of a message type information element (IE), a message ID IE, a backoff timer IE, and a cause IE that identifies a cause for the termination of operations (e.g., overload, unspecified, etc.). In operation block 1656, the DPC 146 may clear all the related resources associated with the DSC 144 and/or perform other similar operations to de-register the DSC 144.

[0234] In operation block 1658, the DSC 144 may perform various de -registration failure response operations based on the information included in the received DSC DE- REGISTER message. For example, the DSC 144 may be configured to not retry registration to the same DPC 146 for at least the duration indicated in the backoff timer IE included in the received DSC DE-REGISTER message when the value of the cause IE in the DSC DE-REGISTER message is set to "overload."

[0235] FIG. 17A illustrates a DSC initiated DSAAP error indication method 1700 for reporting errors in accordance with an embodiment. In the example illustrated in FIG. 17A, method 1700 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP

module/component.

[0236] In operation block 1702, the DSC 144 may detect an error or error condition (e.g., a protocol error, etc.). In operation 1704, the DSC 144 may generate and send an

ERROR INDICATION message to the DPC 146. The DSC 144 may be configured to generate the ERROR INDICATION message to include any or all of a message type information element (IE), a message ID IE, cause IE, and a criticality diagnostics IE. The cause IE may include information suitable for use in identifying a cause or type of the error (e.g., transfer syntax error, abstract syntax error, logical error, etc.). The criticality diagnostics IE may include a procedure code IE, a triggering message IE, and a procedure criticality IE. In operation block 1706, the DSC 144 and/or DPC 146 may perform various error-response operations based on the detected error or information included in the received ERROR INDICATION message. The error detection and response operations are discussed in detail further below.

[0237] FIG. 17B illustrates an embodiment DPC initiated DSAAP error indication method 1750 for reporting errors in accordance with another embodiment. In the example illustrated in FIG. 17B, method 1750 is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or portions of a DSAAP module/component.

[0238] In operation block 1752, the DPC 146 may detect an error condition. In operation 1754, the DPC 146 may generate and send an ERROR INDICATION message to the DSC 144. The DPC 146 may be configured to generate the ERROR INDICATION message to include a cause information element (IE) that identifies a cause for the error. In operation block 1756, the DSC 144 and/or DPC 146 may perform various error- response operations based on the information included in the received ERROR

INDICATION message.

[0239] As mentioned above, the DSC 144 and DPC 146 may be configured perform various error-response or failure response operations in response to detecting an error or failure condition. As part of these operations, the DSC 144 and/or DPC 146 may identify the type or cause of the error/failure condition, and tailor their responses based on the identified type or cause. For example, the DSC 144 and/or DPC 146 may be configured to determine whether a detected error is a protocol error, and tailor their responses accordingly.

[0240] Protocol errors include transfer syntax errors, abstract syntax errors, and logical errors. A transfer syntax error may occur when the receiving functional DSAAP entity (e.g., DSC, DPC, etc.) is not able to decode the received physical message. For example, transfer syntax errors may be detected while decoding ASN.1 information in a received message. In an embodiment, the DSC 144 and DPC 146 components may be configured to retransmit or re-request a DSAAP message in response to determining that a detected error is a transfer syntax error (e.g., as part of the error-response operations).

[0241] An abstract syntax error may occur when the receiving functional DSAAP entity (e.g., DSC, DPC, etc.) receives information elements (IEs) or IE groups that cannot be comprehended or understood (i.e., an unknown IE id). An abstract syntax error may also occur when the entity receives an information element (IE) for which a logical range (e.g., allowed number of copies) is violated. The DSC 144 and DPC 146 components may be configured to detect or identify these types of abstract syntax errors (i.e., cannot comprehend abstract syntax error), and in response, perform error-response operations based on criticality information included in the corresponding DSAAP message.

Additional details regarding these operations and the criticality information are provided further below.

[0242] An abstract syntax error may also occur when the receiving functional DSAAP entity does not receive IEs or IE groups, but according to the specified presence of the object, the IEs or IE groups should have been present in the received message. The DSC 144 and DPC 146 components may be configured to detect or identify these particular types of abstract syntax errors (i.e., missing IE or IE group), and in response, perform error-response operations based on criticality information and presence information for the missing IE/IE group. Additional details regarding these operations, criticality information, and presence information are provided further below.

[0243] An abstract syntax error may also occur when the receiving entity receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group. In addition, an abstract syntax error may also occur when the receiving entity receives IEs or IE groups, but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. The DSC 144 and DPC 146 components may be configured to detect or identify such abstract syntax errors (i.e., wrong order, too many occurrences, erroneously present, etc.), and in response, reject or terminate a procedure or method associated with the error (e.g., the method that caused the error). The DSC 144 and DPC 146 components may reject or terminate the procedure/method as part of the error-response operations. [0244] In the various embodiments, the DSC 144 and DPC 146 components may be configured to continue to decode, read, or process a DSAAP message after detecting, identifying, or determining that an abstract syntax error occurred for that message. For example, the DSC 144 and DPC 146 components may skip a portion of the message that includes an error, and continue processing the other portions of the message. As part of this continued processing, the DSC 144 and DPC 146 components may detect or identify additional abstract syntax errors.

[0245] In an embodiment, the DSC 144 and DPC 146 components may be configured to perform error-response operations for each detected abstract syntax error and/or based on the criticality information and presence information for the IE/IE group associated with the abstract syntax error.

[0246] As mentioned above, each DSAAP message may include, or may be associated with, criticality information, presence information, range information, and assigned criticality information. In the various embodiments, a receiving functional DSAAP entity (e.g., DSC, DPC, etc.) may be configured to use any or all of such information (e.g., criticality information, presence information, etc.) when detecting an error, identifying the type of the error, or the specific error-response that are to be performed. That is, the entity may perform different operations depending on the values of the criticality information, presence information, range information, and/or assigned criticality information.

[0247] In an embodiment, the receiving functional DSAAP entity (e.g., DSC, DPC, etc.) may be configured to use the presence information included in a DSAAP message when identifying the type of error and the specific error-response operations that are to be performed for the identified error type. For example, the entity may use the presence information to determine whether the presence of an information element (IE) is optional, conditional, or mandatory (e.g., with respect to RNS application) for that message or communication. The entity may determine that an abstract syntax error has occurred when a received message is missing one or more information elements that are determined to be mandatory (or conditional when the condition is true).

[0248] In an embodiment, the receiving functional DSAAP entity (e.g., DSC, DPC, etc.) may be configured use the criticality information when identifying the specific error- response operations that are to be performed. That is, each DSAAP message may include criticality information for each individual information element (IE) or IE group included in that message. The values of criticality information for each IE or IE group may include "Reject IE," "Ignore IE and Notify Sender," and "Ignore IE." The receiving entity (e.g., DSC, DPC, etc.) may use this criticality information to determine that an IE, an IE group, or an EP is incomprehensible, identify the condition as an abstract syntax error (i.e., a cannot comprehend abstract syntax error), and/or to identify the error- response operations that are to be performed (e.g., reject, ignore, notify, etc.).

[0249] In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may be configured to reject a method/procedure and initiate a DSAAP error indication method (discussed above with reference to FIGs. 17A-B) in response to determining that an information element (IE) included in a message received during the performance of that

method/procedure is incomprehensible, and that value of the criticality information for that IE is set to "Reject IE."

[0250] For example, when a message that initiates a method/procedure (e.g., a DSC REGISTER REQUEST message, etc.) is received, determined to include one or more IEs/IE groups that are incomprehensible and marked as "Reject IE," the receiving entity may the reject the method/procedure by not executing any of the functional requests included in that message. The receiving entity may also report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. When the information in the received initiating message is insufficient and cannot be used to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving entity may terminate the procedure and initiate a DSAAP error indication method/procedure.

[0251] As a further example, when a message initiating a method/procedure that does not have a message to report unsuccessful outcome is received, and that message includes one or more IEs/IE groups marked with "Reject IE" which the receiving entity does not comprehend, the receiving entity may terminate the method/procedure and initiate a DSAAP error indication method/procedure.

[0252] As yet another example, when a response message (e.g., a DSC REGISTER RESPONSE message, etc.) is received that includes one or more IEs marked with "Reject IE" which the receiving entity does not comprehend, the receiving entity may consider the method/procedure as being unsuccessfully terminated, and initiate a local error handling method.

[0253] In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may be configured to ignore or skip a method/procedure and initiate an DSAAP error indication method (discussed above with reference to FIGs. 17A-B) in response to determining that an information element (IE) included in a message received during the performance of that method/procedure is incomprehensible, and that value of the criticality information for that IE is set to "Ignore IE and Notify Sender."

[0254] As an example, when a message initiating a method/procedure is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving entity does not comprehend, the receiving entity may ignore the content of the incomprehensible IEs/IE groups, continue with the method/procedure as if the incomprehensible IEs/IE groups were not received (except for the reporting) using the comprehended IEs/IE groups, and report in the response message of the

method/procedure that one or more IEs/IE groups have been ignored. When the information received in the initiating message is insufficient to determine a value for all IEs that are required to be present in the response message, the receiving entity may terminate the method/procedure and initiate a DSAAP error indication method/procedure.

[0255] As a further example, when a message initiating a method/procedure that does not have a message to report the outcome of the method/procedure is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving entity does not comprehend, the receiving entity may ignore the content of the not comprehended IEs/IE groups, continue with the method/procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate a DSAAP error indication method/procedure to report that one or more IEs/IE groups have been ignored.

[0256] As yet another example, when a response message is received containing one or more IEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving entity does not comprehend, the receiving entity may ignore the content of the not comprehended IE/IE groups, continue with the method/procedure as if the not

comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate a DSAAP error indication method/procedure.

[0257] In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may be configured to ignore or skip a method/procedure in response to determining that an information element (IE) included in a message received during the performance of that

method/procedure is incomprehensible, and that value of the criticality information for that IE is set to "Ignore IE."

[0258] As an example, when a message initiating a method/procedure is received containing one or more IEs/IE groups marked with "Ignore IE" which the receiving entity does not comprehend, the receiving entity may ignore the content of the not

comprehended IEs/IE groups and continue with the method/procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups. [0259] As a further example, when a response message is received that includes one or more IEs/IE groups marked with "Ignore IE" which the receiving entity does not comprehend, the receiving entity may ignore the content of the not comprehended IEs/IE groups and continue with the method/procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.

[0260] When reporting not comprehended IEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using a response message defined for the

method/procedure, the Information Element Criticality Diagnostics IE may be included in the Criticality Diagnostics IE for each reported IE/IE group.

[0261] In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may be configured to initiate a DSAAP error indication method (discussed above with reference to FIGs. 17A-B) in response to determining that it cannot decode a type of message IE in a received message. In an embodiment, the entity may be configured to only consider the IEs specified in the specification version used by the component when determining the correct order for the IE included in a message.

[0262] In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may be configured to treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of the present document used by the receiver.

[0263] As an example, the receiving entity (e.g., DSC, DPC, etc.) may be configured to not execute any of the functional requests of a received initiating message in response to determining that the received message is missing one or more IEs/IE groups with specified criticality "Reject IE." The receiving entity may reject the method/procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the method/procedure. When it is determined that the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the method/procedure, the receiving entity may terminate the

method/procedure and initiate a DSAAP error indication method/procedure.

[0264] As a further example, when a received message initiating a method/procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "Reject IE", the receiving entity may terminate the method/procedure and initiate a DSAAP error indication method/procedure.

[0265] As yet another example, when a received response message is missing one or more IEs/IE groups with specified criticality "Reject IE, the receiving entity may consider the method/procedure as unsuccessfully terminated and initiate a local error handling method/procedure .

[0266] As another example, when a received message initiating a method/procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving entity may ignore that those IEs are missing and continue with the method/procedure based on the other IEs/IE groups present in the message and report in the response message of the method/procedure that one or more IEs/IE groups were missing. When the information received in the initiating message is insufficient to determine a value for all IEs that are required to be present in the response message, the receiving entity may terminate the method/procedure and initiate a DSAAP error indication method/procedure.

[0267] As another example, when a received message initiating a method/procedure that does not have a message to report the outcome of the method/procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving entity may ignore that those IEs are missing and continue with the

method/procedure based on the other IEs/IE groups present in the message and initiate a DSAAP error indication method/procedure to report that one or more IEs/IE groups were missing. [0268] As another example, when a received message a received response message is missing one or more IEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving entity may ignore that those IEs are missing and continue with the method/procedure based on the other IEs/IE groups present in the message and initiate a DSAAP error indication method/procedure to report that one or more IEs/IE groups were missing.

[0269] As another example, when a received message initiating a method/procedure is missing one or more IEs/IE groups with specified criticality "Ignore IE", the receiving entity may ignore that those IEs are missing and continue with the method/procedure based on the other IEs/IE groups present in the message.

[0270] As another example, when a received response message is missing one or more IEs/IE groups with specified criticality "Ignore IE", the receiving entity may ignore that those IEs/IE groups are missing and continue with the method/procedure based on the other IEs/IE groups present in the message.

[0271] The receiving entity (e.g., DSC, DPC, etc.) may be configured to respond to messages that include IEs or IE groups that received in wrong order, include too many occurrences, or are erroneously present (i.e., are included and marked as "conditional" when the condition is not met) in various ways. For example, the receiving entity (e.g., DSC, DPC, etc.) may be configured to not execute any of the functional requests of a received initiating message in response to determining that the received message includes IEs or IE groups in wrong order, includes too many occurrences of an IE, or includes erroneously present IEs. The receiving entity may reject the method/procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the method/procedure. When the information received in the initiating message is insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the method/procedure, the receiving entity may terminate the

method/procedure and initiate a DSAAP error indication method/procedure.

[0272] As another example, when a message initiating a method/procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving entity may terminate the method/procedure, and initiate a DSAAP error indication

method/procedure using the cause value "Abstract Syntax Error (Falsely Constructed Message)".

[0273] As another example, when a response message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving entity may consider the method/procedure as unsuccessfully terminated and initiate local error handling.

[0274] As mentioned above, protocol errors include transfer syntax errors, abstract syntax errors, and logical errors. A logical error occurs when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a method/procedure which is not compatible with the state of the receiving entity.

[0275] In an embodiment, a receiving entity (e.g., DSC, DPC, etc.) may be configured to perform error response operations based on the class of the method/procedure and irrespective of the criticality information of the IE's/IE groups containing the erroneous values in response to determining/detecting an logical error.

[0276] For example, when a logical error is detected in a request message of a class 1 method/procedure, and the method/procedure has a message to report this unsuccessful outcome, this message may be sent with an appropriate cause value (i.e., in the clause IE), such as "semantic error" or "message not compatible with receiver state." When a logical error is detected in a request message of a class 1 method/procedure, and the method/procedure does not have a message to report this unsuccessful outcome, the method/procedure may be terminated and a DSAAP error indication method/procedure may be initiated with an appropriate cause value. Where the logical error exists in a response message of a class 1 procedure, the procedure may be considered as

unsuccessfully terminated and local error handling may be initiated.

[0277] When a logical error is detected in a message of a class 2 procedure, the procedure may be terminated and a DSAAP error indication procedure may be initiated with an appropriate cause value.

[0278] In the various embodiments, the receiving entity (e.g., DSC, DPC, etc.) may be configured to perform a local error handling method/procedure (as opposed to a DSAAP error indication method/procedure) when a protocol error is detected in the ERROR INDICATION message. In case a response message or error indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure may be considered as unsuccessfully terminated and local error handling may be initiated. When an error that terminates a procedure occurs, the returned cause value may reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure.

[0279] FIG. 18 illustrates the operations and information flows between various components when performing a DSA resource update method 1800 in accordance with an embodiment. In the example illustrated in FIG. 18, the operations of DSA resource update method 1800 are performed by various components, including a wireless device 102, a first eNodeB 116a, a first S-GW 118a, a first DSC 144a, a DPC 146, a second DSC 144b, a second S-GW 118b, and a second eNodeB 116b. The first eNodeB 116a, first S-GW 118a, and first DSC 144a are included in a first network (i.e., a lessee network). The second DSC 144b, second S-GW 118b, and second eNodeB 116b are included in a second network (i.e., a lessor network). [0280] In operation 1802, the wireless device 102 may attach to the lessee network. In operation 1804, the first eNodeB 116a may monitor and report resource usages and node level congestion levels to the first DSC 114a. This may be accomplished by the first eNodeB 116a generating and sending a resource update message to the first DSC 144a, either directly (e.g., via the Xe interface) or via the first S-GW 118a (e.g., via the Sl-U interface). In an embodiment, the first eNodeB 116a may generate the resource update message to include information suitable for reporting resource usage level for multiple cells, including the cell to which the wireless device 102 is attached. In various embodiments, the first eNodeB 116a may be configured to send such resource update messages periodically or in response to detecting a condition or event (e.g., new wireless device attached, etc.).

[0281] In operation 1806, the first S-GW 118a may use the information included in the received resource update message to update its resource usage records and/or forward the resource update message to the DSC 144a. In operation 1808, the first S-GW 118a may start a resource update acknowledgment timer. In operation 1810, the first DSC 144a, may generate and send a resource update acknowledgment message to the first eNodeB, either directly or via the first S-GW 118a. In operation 1812, the first S-GW 118a may forward the resource update acknowledgment message to the first eNodeB 116a and/or use the information included in the received acknowledgment message to update its resource usage records. In operation 1814, the first S-GW 118a may stop the resource update acknowledgment timer in response to receiving the acknowledgment message and/or in response to determining that the resource update acknowledgment message was received prior the expiration of the resource update acknowledgment timer.

[0282] In operations 1816-1822, the first eNodeB 116a may periodically report usage/congestion levels and the first DSC 114a and first S-GW 118a may update their resource usage records, which may be accomplished by performing the same or similar operations as those performed in operations 1804-1814. Similarly, in operations 1850- 1866, the second eNodeB 116b, second DSC 114b, and second S-GW 118b may perform the same or similar operations as those performed as part of operations 1804-1822.

[0283] In operations 1824 and 1826, the first DSC 114a may determine whether there are excess resources available in the first network for allocation to other networks, and send a resource availability message to the DPC 146. The resource availability message may include information suitable for informing the DPC 146 of the resources determined to be available for allocation. The DPC 146 may be configured to receive, store, or maintain resource availability information for multiple DSCs and/or for multiple different networks (i.e. different PLMN-IDs).

[0284] In operation 1828, the first DSC 114a may start a timer. In operations 1830 and 1832, the first DSC 114a may initiate or participate in an auction by monitoring its available/remaining resources and sending resource availability advertisements to DPC 1830. In operation 1834, the first DSC 114a may determine that the timer expired, and discontinue advertizing its resources. In operations 1870-1880, the second DSC 114b may perform the same or similar operations as those performed as part of operations 1824-1834.

[0285] FIG. 19 illustrates an embodiment DSA method 1900 of allocating resources in a first communication network for access and use by a second communication network. The operations of DSA method 1900 may be performed by a processing core of a DPC 146 component.

[0286] In operation 1902, a DPC 146 component may establish a communication link to a DSC 144a in first communication network. In operation 1904, the DPC 146 may determine whether a telecommunication resource of the first communication network is available for allocation based on information received via the communication link. In an embodiment, the DPC 146 may determine that the telecommunication resource is available for allocation at a future date and time. [0287] In operation 1906, the DPC 146 may broadcast a communication signal that includes information suitable for informing a plurality of communication networks that the telecommunication resource is available for allocation via an auction and including an auction start time for the auction. In operation 1908, the DPC 146 may receive bids from the plurality of communication networks for the telecommunication resource determined to be available for allocation in response to broadcasting the communication message and after the auction start time included in the broadcast communication signal. In an embodiment, receiving bids from the plurality of communication networks may include receiving bids for access and use of the telecommunication resource determined at the future date and time.

[0288] In operation 1910, the DPC 146 may accept only the bids received from

authorized networks determined to be eligible to participate in the auction. For example, the DPC 146 may determine whether the telecommunication resource is compatible with each of the plurality of communication networks, authorize networks in the plurality of communication networks as being eligible to participate in the auction based on their compatibility with the telecommunication resource, and accept bids from only the authorized networks.

[0289] In operation 1912, the DPC 146 may allocate the telecommunication resource of the first communication network for access and use by a second communication network in the plurality of communication networks based on accepted bids. In an embodiment, allocating the telecommunication resource may include allocating the telecommunication resource of the first communication network for access and use by the second

communication network at the future date and time. In operation 1914, the DPC 146 may send a communication message to the second communication network that includes information suitable for informing the second communication network that use of allocated telecommunication resource may begin. In operation 1916, the DPC 146 may record a transaction in a transaction database identifying the telecommunication resource as being allocated for use by the second communication network. [0290] In operation 1918, the DPC 146 may request return of the allocated telecommunication resource. In operation 1920, the DPC 146 may broadcast a second communication signal to inform the plurality of communication networks that the telecommunication resource is available for reallocation via a second auction.

[0291] FIG. 20A illustrates another embodiment DS A method 2000 of allocating resources in a first communication network for access and use by a second

communication network. The operations of DSA method 2000 may be performed by a processing core of a DPC 146 component.

[0292] In block 2002, the DPC 146 component may establish a communication link to a DSC 144a in first communication network. In block 2004, the DPC 146 component may determine that a resource in a first communication network is available for allocation. In block 2006, the DPC 146 component may broadcast a first communication signal informing a plurality of communication networks that the resource is available for allocation and of a geographical area associated with the resource. In block 2008, the DPC 146 component may allocate the resource of the first communication network for access and use by a second communication network in the plurality of communication networks. In block 2010, the DPC 146 component may broadcast a second

communication signal informing the second communication network that use of allocated telecommunication resource may begin in the geographical area. In block 2012, the DPC 146 component may record a transaction in a transaction database identifying the telecommunication resource as being allocated for use by the second communication network.

[0293] In operation 2014, the DPC 146 component may request return of the allocated telecommunication resource. In operation 2016, the DPC 146 may broadcast a second communication signal to inform the plurality of communication networks that the telecommunication resource is available for reallocation via a second auction. [0294] In an embodiment, the DSA method 2000 may further include the DPC 146 component receiving resource configuration information relating to a resource allocation scheme from a first DSC 144 in the first communication network and sending the resource configuration information to a second DSC 144 in the second communication network. In a further embodiment, the DSA method 2000 may include the DPC 146 component receiving coordination information relating to availability of the

telecommunication resource based on geographical areas from the first DSC 144 and sending the coordination configuration information to the second DSC 144.

[0295] In a further embodiment, the DPC 146 component may be configured to negotiate a resource leasing scheme between the first and second communication networks for a use of the resource, and coordinating a handover of a mobile device between the first and second communication networks based on geographic boundaries defined in the resource leasing scheme. The DPC 146 may be further configured to determine the validity of a subscriber device (e.g., wireless device 102) of the second communication network based on the proximity of the subscriber device to the geographical area, level of quality of service available to the subscriber device, and/or information included in the resource leasing scheme.

[0296] In various embodiments, the DPC 146 may be configured to instruct the subscriber device to change networks or to establish a communication link to a resource in the first communication network based on the proximity of the subscriber device to the

geographical area, level of quality of service available to the subscriber device, and/or terms of the resource leasing scheme. The DPC 146 may be configured to instruct a subscriber device that is actively connected to or using the telecommunication resource to change networks and/or to attach to another resource based on the proximity of the subscriber device to the geographical area.

[0297] In an embodiment, the DSA system may include a first DSC may include first DSC processor that is coupled to the DPC via a first communication link (i.e., a wired or wireless link), and the second DSC may include a second DSC processor coupled to the DPC via a second communication link. In addition, each of the first and second DSCs may be coupled to an eNodeB. For example, the second DSC may be coupled to an eNodeB in the second telecommunication network via third communication link. The first and second communication links may be defined over the Xd interface, and the third communication link may be defined over the Xe interface. That is, the DSCs may communicate with the DPC via the Xd interface by using the DSAAP protocol, and the DSCs may communicate with the eNodes in their respective networks via the Xe interface by using the DSAAP protrocol.

[0298] In an embodiment, the eNodeB processor may be configured monitor network conditions, generate reports based on a result of the monitoring, and send the generated reports to the second DSC via the third communication link. This may be accomplished by using the DSAAP protocol (i.e., by sending/receiving DSAAP communication messages and/or performing any of DSAAP methods discussed in this application). In an embodiment, monitoring network conditions may include monitoring one of network congestion, resource usage, and resource availability in the second telecommunication network.

[0299] In an embodiment, the second DSC processor may be configured to receive the generated reports from the eNodeB via the third communication link (using the DSAAP protocol), and use information included in the received reports to determine whether there are excess network resources in the second telecommunication network that are available for allocation and use by wireless devices in the first telecommunication network.

[0300] In an embodiment, the second DSC processor may be configured to determining a geographical boundary that is associated with a resource, and send information identifying the determined geographical boundary to the eNodeB via the third communication link (e.g., via a DSAAP component in the second DSC sending DSAAP messages and/or performing DSAAP methods).

[0301] In an embodiment, the DPC processor may be configured to communicate with the second DSC and at least one other DSC component using the DSAAP protocol. As part of these communications, the DPC may receive information suitable for identifying the resources that available for allocation in a plurality of different networks, including the second telecommunication network and at least one other telecommunication network. The DPC processor may use the received information to pool the resources available in the different networks, and communicate with the first DSC via the first communication link to allocate a portion of the pool of resources for access and use by wireless devices in the first telecommunication network.

[0302] In an embodiment, the DPC processor may be configured to receive user traffic and resource usage information from the second DSC via the second communication link (e.g., using the DSAAP protocol), use the received information to monitor traffic and resource usage in the second telecommunication network, and communicate with the first DSC via the first communication link to allocate resources of the second

telecommunication network to the first telecommunication network. The DPC may allocate the resources based on the results of the monitoring operations (i.e., based on detected user traffic and resource usage levels).

[0303] In an embodiment, the DPC processor may be configured to receive bid

information from the first DSC via the first communication link (using the DSAAP protocol), and send bid notification information to the first DSC via the first

communication link.

[0304] In an embodiment, the DPC processor may be configured to receive registration information from the first DSC via the first communication link, use the received registration information to authenticate the first DSC, store a DSC identifier in a registration memory of the DPC in response to authenticating the first DSC. The DPC processor may also generate a registration accept message that includes a plurality of information elements, and send the generated registration accept message to the first DSC via the first communication link by using the DSAAP protocol (e.g., via a DSAAP component in the DPC sending DSAAP message to the first DSC and/or the DPC and first DSC performing a DSAAP method). In an embodiment, the DPC processor may be configured to generate the registration accept message to include a XEh signaling transport network layer (TNL) address information element that includes an address value that is suitable for use in establishing to transport layer session. In an embodiment, the first DSC processor may be configured to receive the registration accept message from the DPC via the first communication link using the DSAAP protocol, and use the address value included in the XEh signaling TNL address information element of the received registration message to establish a transport layer session send an invoice to the first DSC via the first communication link using the DSAAP protocol.

[0305] In an embodiment, the second DSC processor may be configured to determine whether there are resources available for allocation within cells serviced by the second DSC, generate a resource register request message in response to determining that there are resources available for allocation within the cells serviced by the second DSC, and send the generated resource register request message to the DPC via the second communication link using the DSAAP protocol. The DPC processor may be configured to receive the resource register request message from the second DSC via the second communication link using the DSAAP protocol, rejecting the received resource register request message in response determining that there is insufficient memory to store and service resources identified in the received resource register request message, and send a resource register request reject message to the second DSC via the second

communication link using the DSAAP protocol in response to rejecting the received resource register request message.

[0306] In an embodiment, the first DSC processor may be configured to generate an available bids request message, send the generated available bids request message to DPC via the second communication link, and receive information on the resources that have been made available for allocation by the second telecommunication network from the DPC in response to sending the generated available bids request message. In a further embodiment, the first DSC processor may be configured to generate the available bids request message to include a public land mobile network identifier (PLMN-ID) of the second telecommunication network, and to request a specific resource (e.g., a specific RF frequency resource, an eNodeB in a specific cell, etc.) from the second

telecommunication network.

[0307] In an embodiment, the DPC processor may be configured to receive a bid request message from the first DSC via the first communication link. The bid request message may include including a bid. The DPC processor may determine whether the bid is valid by determining whether the bid complies with a requirement of the second

telecommunication network. The DPC processor may sending a bid accept message to the first DSC via the first communication link in response to determining that the bid is valid or send a bid reject message to the first DSC via the first communication link in response to determining that the bid is not valid.

[0308] In an embodiment, the second DSC processor may be configured to communicate with the DPC to allocate resources of a cell in the second telecommunication network for access and use by wireless devices of the first telecommunication network, monitor cell traffic to determine whether the cell is congested, and sending a backoff command message to the DPC via the second communication link using the DS AAP protocol in response to determining that the cell is congested. The backoff command message may include information that is suitable for causing the DPC to instruct the first DSC to selectively handover the wireless device subscribers of the first telecommunication network that using the allocated resources of the cell in the second telecommunication network. The DPC processor may be configured to receive the backoff command message from the second DSC, and communicate with the first DSC using the DSAAP protocol so as to cause the first DSC to select a target cell in the first telecommunication network to handoff the wireless devices using the allocated resources of the cell.

[0309] The various embodiments may include or use a dynamic spectrum arbitrage application part (DSAAP) protocol and/or component that is configured to allow, facilitate, support, or augment communications between two or more DSA components (e.g., DPC, DSC, eNodeB, MME, HSS, etc.) so as to improve the efficiency and speed of the DSA system. A DSA component may be any component discussed in this application and/or any component that participates in any of the DSA operations, communications, or methods discussed in this application. As such, the DSAAP component(s) may be configured to allow, facilitate, support, or augment communications between any of the components discussed in this application, including the communications between a DPC component and a DSC component, between the DSC component and an eNodeB component, between the DSC component and an MME component, between the DSC component and an HSS component, between the MME component and the HSS component, between the eNodeB component and a wireless device, etc.

[0310] To facilitate the communications between two or more DSA components, the DSAAP component(s) may publish application programming interfaces (API) and/or include client modules that facilitate communications between the DSA components. In addition, the DSAAP component(s) may be configured to allow the DSA components to communicate specific information, use specific communication messages, and/or perform specific operations that together provide various DSA functions that further improve the efficiency and speed of the DSA system and participating networks.

[0311] As an example, the DSAAP component(s) may be configured to allow an eNodeB to communicate with a DSC component (e.g., via Xe interface 2215 and 2217 illustrated in FIG. 22, Xe interface 2423 illustrated in FIG. 24, and Xe interface 2627 illustrated in FIG. 26), with other eNodeBs (e.g., via an X2 interface), and with various other components (e.g., via the SI interface). As a further example, the DSAAP component(s) may be configured to allow, facilitate, support, or augment communications between DSC component(s) and the DPC component so as to allow the DPC and/or DSC components to better pool resources across the different networks, better monitor traffic and resource usage in the various networks, to more efficiently communicate bids and bidding information, to quickly and efficiently register and deregister components, and better perform backoff operations (e.g., handover wireless devices 102 from lessor network back to lessee network) and/or handin (e.g., handover wireless devices 102 from lessee network to lessor network) operations. The DSAAP component(s) may also improve the DSA resource auctioning operations by improving the performance and efficiency of the procedures for bidding, generating invoices, advertizing resources, requesting resources, purchasing resources, validating bid credentials, etc.

[0312] In the various embodiments, all or portions of the DSAAP component may be included in one or more DSA components, such as a DPC component, a DSC component, an eNodeB component, an MME component, and an HSS component. The DSAAP component may be implemented in hardware, software, or a combination of hardware and software. In an embodiment, the DSAAP component may be configured to implement a DSAAP protocol, which may be defined over the Xe, Xd, and/or X2 reference points. In various embodiments, the Xe reference point between DSC and eNodeB may use the DSAAP protocol, TR-069 protocol, and/or TR-192 data model extensions to support listing available resources at the eNodeB and notifying the eNodeB of bid/buy confirmations. The Xd reference point between DSC and DPC may use the DSAAP protocol for dynamic spectrum and resource arbitrage operations. The X2 interface/reference point between the eNodeB s may also use the DSAAP protocol to communicate information.

[0313] In various embodiments, the DSAAP component(s) may be configured to allow the various DSA components (e.g., DSC, DPC, eNodeB, etc.) to communicate using the DSAAP protocol and/or to perform various DSAAP methods. DSAAP methods may be performed in any of the DSA systems discussed in this application, such as a system that includes a first DSC server in a first telecommunication network (e.g., a lessee network), a second DSC server in second telecommunication network (e.g., a lessor network), and a DPC server that is outside of the first and second telecommunication networks.

[0314] In further embodiments, the Dynamic Spectrum Arbitrage (DSA) system may be configured to enable the dynamic leasing of excess LTE network capacity through efficient mobility management via DSAFlex (e.g., via arranging or configuring the DSA components to perform one or more DSAFlex operations, etc.). For example, a dynamic spectrum arbitrage (DSA) system may be configured to perform DSAFlex, which may include a DSA component (e.g., a processor in a DCS component in the lessor network, etc.) broadcasting a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network, determining lease criteria parameters of a resource lease associated with the advertised telecommunication resource, determining network capability of the second

telecommunication network, selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria, determining configuration parameters (e.g., configuration parameters that match a specific OEM format, etc.) for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration, and sending the determined configuration parameters to directly or indirectly to components in each of the first and second networks (e.g., in their respective OEM formats, etc.).

[0315] The DSA component may select the DSAX network configuration (based on determined network capability and determined lease criteria), select a suitable

interface(s), and send the determined configuration parameter directly to the components in the first and second networks. For example, the DSA component may send the configuration parameters to an eNodeB via an Xe interface and to an MME component via an Xm interface. The DSA component may also select the DSA Lite network configuration or the DSA9 network configuration, in which case it may send the determined configuration parameters to an O&M component in each of the first and second networks (i.e., components in the lessee and lessor networks).

[0316] In some embodiments, the DSA component may be configured to dynamically select an interface (e.g., Xe, Xm, etc.) based on the determined network capabilities of the networks. In some embodiments, the DSA component may be configured to perform various operations for routing traffic to destination components that are selected based on the determined network configuration (e.g., configuration of the lessee network, etc.).

[0317] In some embodiments, the DSA component may be a dynamic spectrum controller (DSC) component that includes a DSC processor. The DSA component may be configured to receive a list of resources that are available for bidding (via a

communication link to a dynamic spectrum policy controller component that includes a DPC processor), generate a bid request message that includes information suitable for bidding on a resource identified in the received list of resources, and send the generated bid request message to the DPC via the communication link. The DPC may be configured to start a bid timer, receive a bid request message (from the DSC), determine whether the bid request message is valid, send a bid accept message to the DSC via the communication link in response to determining that the bid is valid, determine whether the bid timer has expired, determine whether the DSC is a winner bidder that is to be allocated the resource based on information included in the bid request message in response to determining that the bid request message is valid and that the bid timer has expired, and send a bid won message to the DSC via the communication link in response to determining that the DSC is the winner bidder.

[0318] FIG. 20B illustrates a method 2050 of performing dynamic spectrum arbitrage (DSA) that include DSAFlex operations in accordance with an embodiment. Method 2050 may be performed by a processor in a computing device that implements all or portions of a DSC component. In block 2052, the processor may broadcast a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network. In block 2054, the processor may determine lease criteria parameters of a resource lease associated with the advertised telecommunication resource. In block 2056, the processor may determine the network capabilities of the second telecommunication network. In block 2058, the processor may select one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria. In block 2060, the processor may determine configuration parameters (e.g., configuration parameters that match a specific OEM format, etc.) for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration. In block 2062, the processor may send the determined configuration parameters to components in each of the first and second networks (e.g., in their respective OEM formats, etc.).

[0319] FIG. 21A illustrates various example components, operations and information flows in a system 2100 that is organized/configured to perform DSAFlex operations in accordance with an embodiment. FIGs. 21B and 21C are expanded views of various phases illustrated in FIG. 21A. FIG. 21B illustrates the detailed DSAFlex operations and phases in the lessee network. FIG. 21C illustrates detailed DSAFlex operations and phases in a lessor network.

[0320] FIG. 21A illustrates that the system 2100 may include a lessee network grouping that includes a lessee DSC 2101 component, an eNodeB 2103 component, an MME 2105 component and a lessor HSS 2107 component, and a lessor network grouping that includes a lessor DSC 2151 component, an eNodeB 2153 component, an MME 2155 component, a lessee HSS 2157 component, and a S-GW 2159 component. The system 2100 and/or any of the above mentioned components may be configured to perform or provide DSAFlex operations. In some embodiments, these components may be configured to perform DSAFlex operations in phases (e.g., initialization phase, lease allocation phase, lease execution phase, etc.).

[0321] In the examples illustrated in FIGs. 21A through 21C, the components are configured to perform the DSAFlex operations in four phases, which include a DSC initialization phase 21001, a lease allocation phase 21002, lease execution phase 21003, and a lease termination phase 21004. In some embodiments, the DSAFlex operations within each phase may be performed in a chronologic order/sequence. In some embodiments, the phases themselves may be performed in a chronologic order/sequence. For example, the components may be configured so that the DSAFlex operations associated with the DSC initialization phase 21001 are performed before the operations in the lease allocation phase 21002, the operations associated with the lease allocation phase 21002 are performed before the operations in the lease execution phase 21003, etc.

[0322] In some embodiments, the components may be configured so that DSAFlex operations that are associated with same phase (e.g., lease allocation phase, etc.) are performed at different times in different participating networks. For example, in various embodiments, the components in the lessor network grouping may perform DSAFlex operations associated with the DSC Initialization phase 21001 before, concurrent with, or after the components in the lessor network perform similar or corresponding DSAFlex operations associated a corresponding DSC Initialization phase 21001. Thus, while the example illustrated in FIG. 21A generally follows a chronologic sequence for the operations, it should be understood that all or portions of the DSAFlex operations within each phase may be interchanged, repeated, returned to, executed concurrently, eliminated, added as needed for specific implementations and/or in different

embodiments. As such, the claims should not be interpreted as requiring a particular sequence or chronological order for the performance of the DSAFlex operations or phases unless expressly recited as such in the claims. [0323] With reference to FIG. 21B, in the DSC initialization phase 21001, the components (e.g., lessee DSC 2101 component, eNodeB 2103 component, etc.) may perform operation 2109. In operation 2109, the lessee DSC 2101 component (in the lessee network) may receive detailed eNodeB configuration information (e.g., eNodeB registration information, etc.) from one or more eNodeB 2103 components in the lessee network. The eNodeB configuration information may include information identifying the cells that are served or being serviced, cell types, cell areas, a neighbor list, and/or other similar information that may be collected by (or which is otherwise available to) the eNodeB s.

[0324] In the lease allocation phase 21002, the components (e.g., lessee DSC 2101 component, HSS 2107 component, MME 2105 component, etc.) may perform operations 2111 and 2113. In operation 2111, the lessee DSC 2101 component may perform any or all of the operations, methods or techniques discussed in this application to identify and select suitable eNodeB 2103 components (and/or UEs that are attached to select eNodeB 2103 components). For example, in operation 2111, the lessee DSC 2101 component may identify and select the suitable eNodeB 2103 component (and/or UEs that are attached to select eNodeB 2103 components) based on any combination of factors, such current congestions levels, a detected trigger, condition or event, an expected increase in usage, current usage rates, or any other factor or parameter discussed in this application. In addition, the lessee DSC 2101 may also identify a lessee MME 2105 component (MME in the lessee network) that is responsible for managing the identified/selected eNodeB 2103 components, generate a communication message that includes information identifying the eNodeB 2103 components that are in the grid (and/or a list of grids, lessor PLMN information, or other similar information), and send the generated communication message to the identified lessee MME 2105. In operation 2113, the MME 2105 component may receive the communication message (which identifies the selected eNodeB 2103 components) from the lessee DSC 2101, identify the UEs that are attached to the relevant eNodeB 2103 components, determine the identified UEs are suitable candidates for inter-PLMN handovers (e.g., for during or after the lease execution phase 21003, etc.), generate a inter-PLMN handover candidate list that identifies the UEs determined to be suitable candidates for inter-PLMN handovers, and send the generated inter-PLMN handover candidate list to the lessee DSC 2101 component.

[0325] In the lease execution phase 21003, the components may perform operations 2115, 2117 and 2119. In operation 2115, the lessee DSC 2101 may request and receive UE subscription information from a HSS 2107 component for the UEs in the inter-PLMN handover candidate list. In some embodiments, this may be accomplished via the lessee DSC 2101 component sending a notification message to the HSS 2107 component to indicate that a lease execution has commenced. In response, the HSS 2107 component may request and receive a list of UEs (e.g., UEs included in inter-PLMN handover candidate list, a list of UEs that will be involved in the DSAFlex operations, etc.) from the lessee DSC 2101, collect or retrieve subscription information for the UEs included in the list, and send UE subscription information for those UEs to the lessee DSC 2101 component.

[0326] In operation 2117, the lessee DSC 2101 component may generate and send communication messages to the relevant eNodeB 2103 components (e.g., eNodeBs to which the above-mentioned UEs are attached, etc.) to initiate handover operations and transfer attached devices from lessee network to lessor network. These communication messages may include information identifying the candidate UEs, subscriber or subscription information, HSS information, network information, and/or other

information for handing over the candidate devices. In response to receiving these communication messages, the eNodeB 2103 may perform any or all of the DSA/inter- PLMN handover operations discussed in this application (or any handover operation known in the art) to transfer one or more of the candidate devices from a first network (e.g., lessee network) to a second network (e.g., lessor network). As part of operation 2117, the various components may perform inter-PLMN handovers operations that include sending lessee PLMN information from the lessee network to the lessor network, initiating broadcast of the PLMN information on the lessor network, configuring measurement object(s) for the lessor frequency on the UEs selected for DSAFlex operations, etc.

[0327] In operation 2119, the MME 2105 component may generate and send status update messages to the lessee DSC 2101. In some embodiments, the MME 2105 component may be configured so that update messages are send for only the UEs that were selected for DSAFlex operations and/or for which updated information is relevant. These status update messages may also include status information for any or all of the relevant UEs, eNodeBs, grids (e.g., grids involved in the DSAFlex operations, etc.), or components that are participating in, or which are relevant to, the performance of DSAFlex operations. For example, the status update messages may include updated information regarding the number of UEs that are actively connected to the network within the grids identified for DSAFlex operations, information identifying the UEs that are camped on the network within the DSAFlex grids, information identifying the UEs that have entered or left the DSAFlex grids, etc.

[0328] In some embodiments, as part of operation 2119, the MME 2105 component may monitor various components, resources and conditions (e.g., UEs, eNodeBs, grids, network congestion, etc.) to collect information, and send the collected information to the relevant components. For example, the MME 2105 component provide information regarding idle-to-connected mode transitions (e.g., for UEs, etc.) or generate information suitable for causing transitions (e.g., idle-to-connected mode transitions, etc.) to occur in operation 2119. In the various embodiments, all or portions of operation 2119 may be performed continuously or repeatedly during or throughout the lease execution phase 21003 (e.g., for the entire period associated with the lease execution phase 21003, until the lease execution phase 21003 is complete, etc.). Alternatively or in addition, operation 2119 may be performed periodically, at set time intervals, or in response to various conditions, triggers or events (e.g., events triggered in response to exceeding a usage limit, dropping below a usage limit, a detected increase in usage that exceeds a threshold value, a usage decrease, a significant change in number of connected UEs, etc.).

[0329] During the lease termination phase 21004, the components may perform

operations 2121 and 2123. In operation 2121, the lessee DSC 2101 may perform various operations to cleanup lessor neighbor cells in the lessee. As part of these operations, the lessee DSC 2101 may execute an automatic neighbor relation (ANR) table/procedure (or perform other similar operations) to manage the provisioning of neighbor cells. For example, in some embodiments, the cleanup operations may include removing neighbor cells that were part of the lessor network during DSAFlex operations, adding neighbor cells that were removed or were not neighbors during DSAFlex operations (e.g., due to grid reconfiguration of cells, etc.). The performance of the cleanup operations may result in a release of resources on the lessee network and/or may include transfers of UEs (e.g., handins, etc.) between networks. These operations may also include rebalancing of resources in the effected eNodeBs, grids, etc. In operation 2123, the lessee MME 2105 may perform various operations to stop inter-PLMN handovers, stop updating UE information for the grids that were involved in DSAFlex operations, and/or other similar operations. In the various embodiments, all or portions of these operations may be performed after operation 2121 is complete, concurrent with or at the same time as operation 2121, and/or after operation 2121.

[0330] FIG. 21C illustrates interactions between the components in the lessor network group, which includes a lessor DSC 2151, eNodeBs 2153, MME 2155, lessee HSS 2157 and S-GW 2159. In the example illustrated in FIG. 21C, some of the operations and actions in the lessor network are grouped into categories and/or performed as groups. These groups include a first grouping 2191 for usage management, a second grouping 2193 in which UE subscriber(s) may exit grids covered by the DSAFlex lease, and a third grouping 2195 for congestion management of traffic on the lessor network. The first grouping 2191 includes operation 2191, the second grouping 2193 includes operation 2169, and the third grouping 2195 includes operations 2171 through 2181. [0331] FIG. 21C illustrates that the operations may also be associated with phases. For example, in the DSC initialization phase 21001, the components may perform operation 2161. The components may perform operations 2163 and 2165 in lease allocation phase 21002, operations 2167 through 2181 in the lease execution phase 21003, and operations 2183 through 2189 in the lease termination phase 21004. While these specific operations are illustrated as being associated with specific phases in FIG. 21C, it should be understood that, in various embodiments, any or all of the operations discussed below may be performed in any of the phases 21001 through 21004.

[0332] The groupings 2191, 2193, 2195 themselves may also be associated with one or more of phases 21001 through 21004. For example, FIG. 21C illustrates the first grouping 2191 as being associated with lease allocation phase 21002. However, it should be understood that, in various embodiments, the components may be configured to perform any or all of the operations in any of the groupings 2191, 2193, 2195 in any of the phases 21001-21004. It should also be understood that, in various embodiments, the operations in each of the groupings 2191, 2193, 2195 may be performed in different phases and/or across multiple phases. For example, in some embodiments, the operations in the first grouping 2191 may span into the lease execution phase 21003 and/or the lease termination phase 21004. As a further example, during any of phases 21002 through 21004, a UE subscriber may leave the grid that is covered by (or otherwise associated with) the performance of the DSAFlex operations, which may cause the components to perform the operations associated with the second grouping 2193. Therefore, it should be understood that the components may perform any or all of the operations associated with one or more of the groupings 2191, 2193, 2195 and/or cease performing operations associated with one or more of the groupings 2191, 2193, 2195 based on various triggers, events or conditions.

[0333] With reference to FIG. 21C, in operation 2161, the lessor DSC 2151 may receive eNodeB configuration details from one or more eNodeB 2153 components in the lessor network (e.g., via a eNodeB registration message). In operation 2163, the lessor DSC 2151 component may use the received eNodeB configuration details to identify and select eNodeB 2153 components (and their associated resources, etc.) for participation in DSAFlex operations. The lessor DSC 2151 component may also generate a resource allocation message, and send the generated message to the selected eNodeBs 2153. In some embodiments, the lessor DSC 2151 may be configured to generate the resource allocation message to include information regarding the lessee network eNobeB 2103 components and lessee UEs that are to participate in the DSAFlex operations. The resource allocation message may also be generated to include PLMN information and/or any of the information obtained by the lessee DSC 2101 (e.g., in operation 2109 discussed above, etc.). As part of operation 2163, the eNodeB 2153 component may receive the resource allocation message, perform various resource allocation operations, and broadcast information (e.g., lessee PLMN information, resource availably

information, etc.) so that it may be received by many participating networks.

[0334] In operation 2165, the lessor DSC 2151 component may generate send a resource allocation message to an MME 2155 component. The resource allocation message may include a list of the eNodeBs, lessee network PLMN information, and other similar information. The list of the eNodeBs (or eNodeB list) may identify all of the suitable eNodeB 2153 components that are in the grid of the lease (or lease grid). For example, the eNodeB list may include all of the eNodeBs identified in operation 2163. In addition, in operation 2165, the MME 2155 component may perform various operations to allow or support inter- PLMN handovers (i.e., to hand UEs off from the lessee network to the lessor network) in response to receiving the resource allocation message and/or in response to execution of the lease.

[0335] In some embodiments, before or during the execution of the lease, the components in the system may perform any or all of the operations in the first grouping 2191 (e.g., for usage management, management of resources, etc.), examples of which include operations for preparing handins from the lessee network, operations to obtain relevant information (e.g., PLMN information, Subscriber Profile ID (SPID) information, billing information, etc.), and operations to accomplish various network management tasks (e.g., allocate resources, properly bill for the allocation or usage of those resources, etc.).

[0336] In an embodiment, the components in the system may commence execution of the operations in the lease execution phase 21003 (i.e., operations 2167 through 2181) after the completion of operation 2165 and after the operations in the first grouping 2191 have been performed.

[0337] In some embodiments, any or all of operations in the lease execution phase 21003 may also be included as part of the third grouping 2195 (e.g., for congestion

management, etc.).

[0338] In operation 2067, the lessor DSC 2151 may send a resource allocation message to S-GW 2159, with instructions to begin providing accounting records for visiting UEs from the lessee network. The S-GW 2159 may send accounting records and details for billing to various components of the lessor network group (e.g., HSS 2157, MME 2155, DSC 2151, etc.) and/or to any component that is associated with usage or billing operations on the lessor network. For example, in response to each UE that joins the lessor network from the lessee network for DSAFlex operations, the S-GW 2159 may perform various operations (e.g., as part of operation 2168, etc.), collect billing or usage information, and send the billing/usage information to a charging system.

[0339] In operation 2169 (which may be included in the first group 2191, second group 2193 and/or third group 2195 in various embodiments), the MME 2155 component may generate and send status update message to the lessor DSC 2151. In an embodiment, the status update message may include updated status information for all lessee UEs that are connected/attached to the eNodeBs 2153. In an embodiment, the status update message may include updates for only those lessee UEs that are connected to eNodeBs 2153 that are within the grids involved in DSAFlex operations. In an embodiment, the update message may include updated information for each lessee and/or lessor UE that departed a grid involved in or associated with the DSAFlex operations. In an embodiment, the update message may include information identifying the occurrence of a transition (e.g., idle-to-connected mode transition, etc.). In some embodiments, the MME 2155 component may be configured to cause a transition (e.g., idle-to-connected mode transition, etc.), and report the occurrence or result of the transition to lessor DSC 2151 component via the update message.

[0340] In an embodiment, the MME 2155 component may be configured to generate and send the update message in response to determining that a lessee UE has exited a lessor grid that is part of the DSAFlex operations. Such an exit may be caused by various reasons that include, but are not limited to, UEs detaching from eNodeBs 2153 that are part of the grids covered by DSAFlex operations, moving beyond service coverage provided by lessor network involved in DSAFlex operations, UEs powering down, handout to networks other than lessor network, etc.

[0341] In an embodiment, the MME 2155 component may be configured to generate and send the update message based on various additional criteria or conditions, such as based on a time period, handin rate, handouts, usage levels, etc. For example, each time a UE depart a grid, the MME 2155 may generate and send an update message to lessor DSC 2151 to inform it of the updated status of the departing UEs.

[0342] In various embodiments, the MME 2155 component may be configured to perform operation 2169 before, during, and/or after the performance of the operations included in the second grouping 2195.

[0343] In operation 2171, the lessor DSC 2151 may communicate with the HSS 2157 component (e.g., via UE subscription information request and response messages) to receive, exchange or synchronize UE subscription information. For example, the lessor DSC 2151 may request UE subscription information from the HSS 2157 component, which in response, may generate and send lessee and/or lessor UE account, service, and subscription details to the lessor DSC 2151. In an embodiment, the HSS 2157 component may request or obtain the UE subscription information from the S-GW 2159. [0344] In an embodiment, the HSS 2157 component may request UE subscription information from the lessor DSC 2151 in operation 2171. For example, the HSS 2157 component may request updated account information from the lessor DSC 2151, which in response, may provide the HSS 2157 component with the information that it received in operation 2168 (if the lessee HSS did not obtain it directly from the S-GW 2159, etc.). In an embodiment, the HSS 2157 component may request the necessary information from the lessor DSC 2151, which in response, may contact the lessee network to obtain the UE subscription information.

[0345] Allowing the HSS 2157 and lessor DSC 2151 components to exchange UE subscription information enables the lessor network to prioritize the services that it provides for the lessee and/or lessor UEs involved in DSAFlex operations. The lessor network may also select and allocate appropriate resources based on the UE information (e.g., frequency capabilities, data rates, hardware settings, device requirements, etc.). This is especially useful if congestion management operations require rebalancing of resources and UEs connected to the network. The subscription and/or service

information may also be used to determine levels of service and quality of service indicators to be met. This information is also useful for prioritizing UEs during congestion management.

[0346] In operation 2173, one or more of the eNodeB 2153 components may generate and send one or more congestion triggers (congestion level update(s)) to the lessor DSC 2151. The congestion level updates may include information indicating to lessor DSC 2151 that the eNodeB 2153 has reached certain limits and information indicating that they may need to be rebalanced or can no longer take on additional resources. This may be caused by a number of reasons to include, but not limited to, excess DSAFlex handins for the eNodeB 2153 to handle, or normal lessor traffic aggregating at the eNodeB 2153, roaming of UEs that are not normally part of the lessor or lesse networks. The result being eNodeB 2153 has reached a set level that it notifies lessor DSC 2151 of the burden to eNodeB 2153. Upon receiving a notification from an eNodeB 2153 in operation 2173, a lessor DSC 2151 may execute any one, some or all of operations 2175-2181. The lessor DSC may conduct operations to decide which operations will best respond to the congestion level update to continue to provide services to lessor network UEs and lessee network UEs according to the terms of the DSAFlex lease.

[0347] In operation 2175, provide instructions to an eNodeB 2153 to stop broadcasting lessee PLMN. If the congestion level reduces this may solve the issue. Additionally, or alternatively, the lessor DSC 2151 may send the lessor MME 2155 instructions to rebalance the resources being handled by the eNodeB 2153 reporting a congestion level update. This may include the lessor MME 2153 sending instructions to the eNodeB 2153 to stop broadcasting the lessee network PLMN information or to initiation other actions, such as to initiate handovers to other networks for lessor UEs or lessee UEs, initiating handovers to neighboring eNodeB s of lessor UEs and other actions to reduce the load on the eNodeB while maintaining services agreed to according to the terms of the DSAFlex lease.

[0348] In response to receiving the notice in operation 2175, the lessor DSC 2151 may execute operation 2177. In operation 2177, eNodeBs 2153 may configure measurement object(s) for the lessee frequency on lessee UEs to determine actions in preparation for alleviating congestion. As part of operation 2177, the eNodeBs 2153 may initiate handover of lessee UEs from specific eNodeBs 2153 that have reached a set congestion level to other eNodeBs 2153 in the lessor network, or may initiate handover of lessee UEs back to the lessee network to alleviate the congestion.

[0349] In response to receiving the notice in operation 2175, the lessor DSC 2151 may execute operation 2179. In operation 2179 the lessor DSC 2151 may provide a message to MME 2155 to prevent further inter- PLMN handovers from the lessee network to specific eNodeBs 2153. This may include only the congested eNodeB 2153, prevention of inter- PLMN handovers may include other eNodeBs 2153 that are part the grid involved in DSAFlex operations on the lessor network or to prevent all additional inter- PLMN handovers from the lessee network.

[0350] In response to receiving the notice in operation 2175, the lessor DSC 2151 may execute operation 2181. In operation 2181, lessor DSC 2151 may send a message to eNodeB 2153 that sent the congestion level update message, or any eNodeBs 2153 involved in the DSAFlex operation, with instructions to release the lessee UE with redirection information to other eNodeBs 2153. Alternatively, the instructions may include redirection back to lessee network of the lessee UE(s).

[0351] As mentioned above, FIG. 21A and 21C illustrate operations 2175 through 2181 as being performed in a particular order. However, it should be understood that operations 2175-2181 may be perform in any order. Each operation 2175-2181 can be executed in response to any of the other operations 2175-2181. Any two or more of the operations 2175-2181 may be executed in any sequence or at the same time. In alternative embodiments, any one operation 2175-2181 may be executed to attempt to alleviate congestions and if it is not successful within a given period of time or does not remedy any quality of service issues, any one or more of the operations 2175-2181 may be executed to alleviate the congestion or improve service parameters.

[0352] Upon expiration of the DSAFlex lease, operation 2183 may be executed. In operation 2183, the lessor DSC 2151 sends a message to eNodeBs 2153 so the eNodeBs 2153 may configure measurement object(s) for the lessee frequency on the lessee UEs. Upon configuration of the measurement object(s) on the lessee UEs, the eNodeBs 2153 may initiate handovers of the lessee UEs to lessee network. Upon execution of operation 2123 on the lessee network, the lessee DSC 2101 may send a message to lessor DSC 2151 to initiate any one or more of operations 2185-2189. Alternatively, in response to the eNodeBs 2153 initiating handovers back to the lessee network, the lessor DSC 2151 in operation 2185 may send instructions to initiate a cleanup of the lessee neighbor cells in the lessor ANR tables. Alternatively, lessor DSC 2151 may execute operation 2185 immediately after initiating operation 2183. As ANR table clean up occurs, it may result in a release of resources on the lessor network.

[0353] The lessor DSC 2151 may execute operation 2187 anytime during lease

termination phase 21004 on the lessor network. In one embodiment, lessor DSC 2151 send a message to MME 2155 to initiate operation 2187, which includes the MME 2155 stopping inter-PLMN handovers to the lessor network from the lessee network.

Operation 2187 may also includes stopping the update of UE information for the grid involved in DSAFlex. Stopping inter-PLMN handovers involved with the DSAFlex in the grids involved will ensure no more UEs transfer from the lessee network to the lessor network. Additionally ceasing the update of UE information in the grid involved in DSAFlex operations will ensure that any lessee UEs that are on the lessor network do not receive lessor network information. This may include not providing lessor neighbor lists, or available eNodeBs that were available during DSAFlex operations or any other network information to the lessee UEs still on the network, lessee UEs may still be on the lessor network depending on the DSAFlex implementation, such as if there is an active session while using DSA-Lite implementation. Alternatively, upon beginning of the lease termination phase 21004 on the lessor network, the RAN sharing may be terminated and as such, any lessee UEs on the lessor network may have their sessions terminated. Having no lessor network connection information, should connect to any other network available in normal network connection preference as set by the UE, which generally is the lessee or UE' s home network.

[0354] The lessor DSC 2151 may also send a message to lessor S-GW 2159 in operation 2189 to signal the lessor S-GW 2159 it may stop sending accounting information for any lessee UEs at that time. In an alternative embodiment, as each lessee UE departs the lessor network, the S-GW 2159 can notify the lessor DSC 2151 of any billing

information it has for that UE and then stop supplying the information to lessor network components. [0355] Any operation that is executed by lessee DSC 2101 or lessor DSC 2151 may be communicated to the other directly, through network components or through a DPC. This may trigger operations in the same network or in the network receiving the communication. Examples may include, but are not limited to, the lessor DSC 2151 initiating operation 2183. lessor DSC 2151 may also communicate that this operation has begun to lessee DSC 2101 such that lessee DSC 2101 may initiate operation 2121, a cleanup of the lessor neighbor cells in the lessee ANR table may be executed, such that as operation 2185, to also conduct a cleanup of the lessee neighbor cells in the lessor ANR table, which in turn may be communicated to lessor DSC 2151 which may in turn initiate operation 2185. Alternatively, operations in lessee network may be triggered as actions are completed in the lessor network, and vice versa. In one embodiment, during congestion management 2195, as UEs depart the DSAFlex grid, operation 2119 may be executed on the lessee network to update UE statuses be triggered in the lessee network.

[0356] The network configurations illustrated in FIG. 22 is of an embodiment where the lessor and lessee networks both utilize a DSAX implementation. The network

configurations illustrated in FIG. 23 is a of an embodiment where both the lessor and lessee networks utilize a DSA9 implementation. The network configurations shown in FIG. 24 is of a heterogenous DSAFlex where a lessor network has a DSAX

implementation and the lessee network utilizes a DSA9 implementation. The network configurations illustrated in FIG. 25 is of an embodiment where the lessor and lessee networks both utilize a DSA-Lite implementation where the lessee has its own wireless network and infrastructure. However with DSA-Lite the lessee is not required to have its own infrastructure and can operate on a pure MVNO, mobile virtual network operator or the lessee can have a subset of infrastructure including possibly a HSS, IMS Ring, or P- GW or any combination. The network configurations illustrated in FIG. 26 is of an embodiment utilizing a heterogenous DSAFlex where a lessor network utilizes a DSAX implementation and a lessee network utilizes a DSA-Lite implementation. [0357] The DSA system may be configured to support a flexible implementation called DSAFlex. The components in a DSA system (i.e., DSA components) may be configured to perform DSAFlex operations that allow for several DSA configurations that support different Original Equipment Manufacturer (OEM) that have different infrastructure implementations .

[0358] A DSAFlex architecture may be used provide the DSA functionally provided by a DSC component, which may be locally connected to a LTE wireless network.

[0359] DSAX is a DSAFlex solution that is implemented via X-interfaces. A DSAFlex solution implemented using LTE Rel 9 with RAN sharing may be referred to in this application as DSA9. DSA-Lite is a DSAFlex solution that is implemented to use a pure roaming architecture.

[0360] With DSAFlex, a solution provider can enable DSA functionality where both networks involved with the DSA operations utilize one of DSAX, DS A9, DSA-Lite or the networks can utilize any combination of the three as illustrated in the table below. DSAFlex may be implemented with or without RAN Sharing (DSA9 uses RAN Sharing, whereas DSAX and DSA-Lite do not utilize RAN Sharing).

[0361] For example with DSAFlex, DSA functionally may be implemented using DSAX, using the DSAX interfaces and DSA9 configuration simultaneously between two wireless LTE networks utilizing different OEM infrastructure equipment.

[0362] DSA9 utilizing RAN sharing can be implemented between two LTE networks both using a DSA9 configuration.

[0363] DSA-Lite can be implemented as a standalone network or in conjunction with another wireless network using DSA-Lite, DSA9 or DSAX.

[0364] The table below shows the various combinations of DSA configurations possible with DSAFlex.

Sharing

DSAX DSAX No

DSAX DSA9 Yes

DSAX DSAL No

DSA9 DSA9 Yes

DSA9 DSAL No

DSAL DSAL No

[0365] The advantage of using DSA9 or DSA-Lite for an existing operator is that DSA may be implemented with functional integration of the DSC by communicating with just the O&M and Offline Charging System (OFCS) platforms of both the lessee and lessor networks. Additional platforms may be integrated or modified if desired that can act as front end or liasons between the DSC and the O&M and OFCS.

[0366] DSA9 and DSA-Lite utilize the OAM to make network changes for configuring the lease in both the lessee and lessor networks. However DSAX directly interfaces with the LTE nodes for both the lessee and lessor network utilizing a DSA Software Feature Pack (SP) enhancement to the LTE network for both Core and RAN. The SP can also be implemented using a distributed approach where the RAN has a localized server or subset of the core components enabling local control at the very edge of the network enabling elaborate policy control functions and features to be instilled allowing for current and future capabilities for lease management with DSA. [0367] In all configurations of DSAFlex the OEM vendor may provide assistance with specific features for implementation based on the software load. This includes the individual details of how the features are implemented within the specific network provider's infrastructure, commands, and any formatting needed to facilitate the implementation of DSA capability into the wireless network.

[0368] As referenced previously, DSAFlex can be used with and without RAN sharing. DSAX and DSA-Lite do not require RAN sharing. However, DS A9 typically uses a RAN sharing approach, however there are configurations possible by those in the craft where DS A9 does not require RAN sharing.

[0369] DSA-Lite may be used as an in-market roaming architecture. The in-marketing roaming architecture for DSA-Lite may include mobility utilizing the S10 link 2501 as illustrated in FIG. 25 and the option S10 link 2601 and optional S10 link 2603 as illustrated in FIG. 26. However DSA-Lite does not utilize RAN sharing or features for managed mobility of UEs between the lessee and lessor networks. The X interface, or through RAN sharing capabilities it is possible to conduct mobility management between a lessee and lessor networks for an active session. DSA-Lite provides connectivity to the lessee P-GW as is done currently in the wireless industry for Roaming.

[0370] DSA9 generally uses RAN Sharing (as compared to DSA-Lite, which generally does not). The RAN Sharing configuration that is used with DSA9 may be Multiple Operator Core Network (MOCN) architecture. DSA9 is different than DSAX. For example, DSAX uses a Gateway Core Network (GWCN) and a MOCN. However if DSAX is used with a DSA9 network, then the MOCN architecture may be used by itself for such a configuration.

[0371] Connectivity for transporting traffic between the lessee and lessor networks may be different if DS A9 is used (as compared to DSAX or DSA-Lite). With DSAX or DSA- Lite, the S-GW 2605 on the lessor network connects to the lessee networks P-GW 2607. In FIG. 26, this connection is illustrated by the S8 connection 2609. Components such as security gateways 2611a and 2611b may exist in the connection between the S-GW 2605 and P-GW 2607. For DSA9, as illustrated in FIG. 23, the lessee MME 2301 and S-GW 2303 may connect to each lessor eNodeB 2307 involved with the lease using the connection Sl-Flex As illustrated by connections Sl-M and Sl-U labeled 2305 in FIG. 23. Similarly illustrated in a heterogenous DSAFlex implementation using DSA9 and DSAX, the lessee MME 2415 and S-GW 2417 may be connected to each lessor eNodeB 2421 involved with the lease using the connection Sl-Flex illustrated as connections Sl- M and Sl-U labeled 2419 in FIG. 24.

[0372] Sl-Flex is currently used in LTE Rel 9 and later releases which can be used with a network using DSA to provide the RAN Sharing between networks.

[0373] The lessor network may need to have the lessee PLMN-ID transmitting on the lessor eNodeB using SIB2 regardless of which variant of DSA is being utilized during the lease preparation phase and duration of the lease PLMN-ID with DSAFlex.

[0374] Additionally the ability to support InterFreqHO by the UEs involved with the lease may be needed and is a standard feature with LTE currently.

[0375] The identification of which UE should be included in the DSA lease by the lessee is expected to be completed by the lessee network operator through a change in the subscriber profile in the lessee HSS 2157 as illustrated in FIGs. 21A and 21C, or HSS 2201 in FIG. 22, HSS 2309 in FIG. 23, HSS 2401 in FIG. 24, HSS 2503 in FIG. 25, or HSS 2613 in FIG. 26 as part of the lease parameters with DSAFlex.

[0376] The GIS Administrator Application (GAA), as currently implemented in DSA, may continue to craft a lease and be directly involved with analyzing a lease with

DSAFlex.

[0377] The DSCs may interface into the wireless operators Network Management System (NMS) platforms O&M with DSAFlex as illustrated by functional connections 2203 and 2205 in FIG. 22, functional connections 2309 and 2311 in FIG. 23, functional connections 2403 and 2405 in FIG. 24, functional connections 2505 and 2507 in FIG. 25, and functional connections 2615 and 2617 in FIG. 26. However the interaction with the O&M platforms may involve different provisioning commands based on the individual OEM vendor to enable the implementation of the lease for both the lessee and lessor networks. The different command structures and file formats needed to communicate with the lessee and lessor LTE networks via the DSC's may also be achieved with the use of API calls that can be implemented directly with the O&M or through a liaison platform that sits between the O&M and the DSC to facilitate this communication.

[0378] The Automatic Neighbor Relationships (ANR) feature on all the respective eNodeB's for the lease area in DSAFlex should be enabled. ANR is a standard feature implemented in LTE Rel 9. In addition to the ANR feature, inter frequency

measurements for selective eNodeB's should be enabled allowing on UEs to detect neighbor cells of the lessor or lessee network operating on different frequency bands. The ANR function may facilitate inter frequency handovers with less UE signaling being required and expediting the migration of UEs from one network to another.

[0379] Usage information used to determine how much of the lease volume has been consumed may be extracted in various ways from the lessor's OFCS platform 2209 in FIG. 22, 2315 in FIG. 23, 2409 in FIG. 24, 2511 in FIG. 25, and 2621 in FIG. 26, to include through an exposed API or a Gx interface used for Roaming extraction illustrated by interface 2207 in FIG. 22, interfaces 2313 or 2321 in FIG. 23, interface 2407 in FIG. 24, interface 2509 in FIG. 25, and interface 2619 in FIG. 26.

[0380] The Element Management System (EMS) platform that is associated with the DSC may be implemented as a shell for the existing NMS platforms used by the operators. The DSC EMS as illustrated by 2211 and 2213 in FIG. 22, 2317 and 2319 in FIG. 23, 2411 and 2413 in FIG. 24, 2513 and 2515 in FIG. 25, and 2623 and 2625 in FIG. 26 may be integrated into the various NMS platforms by providing the necessary MIBS when required. [0381] DSA9 may require the following to be available within the LTE network using DSA9: LTE Release 9 (Rel 9); Self Optimizing Networks (SON); Automatic Neighbor List (ANR); Carrier Priority (eNodeB) feature; Mobility Load Balancing (MLB) feature; Subscriber Profile ID (SPID) feature; DSC connectivity (LTE O&M, LTE OFCS); RAN Sharing enabled; Si-Flex with X2; and Roaming Restriction Support.

[0382] DSA-Lite may require the following to be available with the LTE network using DSA-Lite: LTE Rel 9; Roaming Allowed; Automatic Neighbor List (ANR); Carrier Priority (eNodeB) feature; Subscriber Profile ID (SPID) feature; DSC connectivity (LTE O&M, LTE OFCS); and optional S10 connectivity.

[0383] DSAX may require the following to be available on the LTE network using DSAX: LTE Rel 9; Self Optimizing Networks (SON); Subscriber Profile ID (SPID) feature; Automatic Neighbor List (ANR); Carrier Priority (eNodeB) feature; DSC connectivity (LTE O&M, LTE OFCS or S-GW (Xs)); MME (Xm); eNodeB (Xe); HSS (Xh).

[0384] From the above lists for DSAX, DSA9 and DSA-Lite, SON, ANR, MLD, SPID, Si-Flex, Carrier Priority, and RAN sharing may be features within LTE Rel 9. The selection of which UEs are allowed DSA capabilities may be defined through the HSS and/or provided by the lessor MME for visiting PLMNs.

[0385] In an embodiment, DSAX may be primary architecture for implementing DSA into a wireless LTE network.

[0386] Reference may be made to FIG. 22 for an illustration of an embodiment where both the lessee and Lesssor networks use a DSAX implementation.

[0387] The following provides some of the key details for the implementation of DSA9 and/or DSA-Lite in a DSAFlex environment. [0388] DSA9 is one of the primary configuration options for DSAFlex. The current LTE networks following 3GPP can successfully implement DSA using DS A9 with a reduced set of functionalities that are inherent to DSAX. With DSA9 the X interfaces used in DSAX are not required and generally not used.

[0389] Because the X interfaces for DSA9 are generally not utilized, the behavior and execution of the lease may not be as robust or dynamic as is the case with DSAX. lessee subscribers may handin and out of the lessor network using an the SI -flex connection.

[0390] DSA9 is implemented by having the DSC for the respective network interfacing with the O&M for the LTE network facilitating the network configuration to support the lease parameters. The OEMs associated with the LTE wireless carrier infrastructure may be needed to facilitate the correct commands and file formats are sent to the LTE wireless networks to enable DSA capability for the lease execution.

[0391] With DSA9, several Rel 9 features may be utilized to include Subscriber Profile ID (SPID), Carrier Priority, and Mobile Load Distribution (MLD) also referred to as Mobile Load Balancing (MLB), Si-Flex, and Automatic Neighbor Reporting (ANR).

[0392] Reference can be made to FIG. 23 for an illustration of an embodiment where both the lessee and Lessor networks use a DSA9 implementation.

[0393] Initiating a lease with DSA9 the eNodeB's on the lessor network may be connected to both the lessor and lessee networks through MOCN RAN sharing with Sl- Flex enabled. The use of the SI -Flex facilities the configuration via the O&M enabling VLANs from the lessor network to be dynamically configured at the inception of the lease through defining an IP address of the lessee MME 2301 and S-GW 2303 in FIG. 23 and MME 2415 and S-GW 2417 in FIG. 24.

[0394] Additionally with DSA9 the SPID for the lessee UE may be changed to reflect the channel on the lessor network that the UE will utilize. With DSA9 the support of active UE handovers can be augmented with Mobility Load Balancing (MLB). MLB is a common feature used in LTE Rel 9 and the network operators may utilize this feature to load balance their network. When the lease begins, lessee eNodeBs which are in the lease area may be provisioned to have the lessor RF capacity at its disposal.

[0395] The lessee eNodeBs in the lease area may be identified using the GAA and be configured to include in the frequency selection criteria for the RF channel on the lessor network. Therefore, all the lessee eNodeBs which are within the Grid Area of the lease itself as defined by the GAA may be used.

[0396] The Carrier Priority may be changed on all the lessee eNodeBs that are in the grid area defined by the GAA. Carrier Priority may be used as the primary method for steering lessee UEs from the lessee network to the shared RAN on the lessor Network which may operate on another carrier frequency. Carrier Priority may affect active traffic on the lessee eNodeB and might not affect the idle UEs attached to eNodeBs.

[0397] MLB/MLD may also be utilized to include the additional LTE channel on the lessor network for those sites in the lease area thereby facilitating active handins from the lessee network to lessor network. The volume of traffic for shedding from the lessee to lessor network may be reflective of the percentage (%) the lessee desires to move to the new network capacity or lessee can lease the value as previously defined and have the lessor channel be a priority or one of several channels to select from.

[0398] The X2 connection needed for MLB functionality between the lessee and lessor networks is facilitated by ANR capabilities for identifying eNodeBs which are handover candidate sites for entering and exiting the lease area. The X2 connection between the lessee eNodeBs and the lessor eNodeBs involved with the lease may be automatically configured based on ANR discovery.

[0399] Therefore, X2 connectivity using the inter frequency ANR feature may enable the source eNodeB to obtain the PCI and ECGI of a neighboring cell on a different frequency and can use these to setup a new X2 interface towards this eNodeB. Additionally TNL address discovery of the candidate eNodeB, the ID of which is known from the above ANR feature, via S 1 interface where a source eNodeB sends a configuration transfer message to request the MME for the address of the candidate eNodeB which in turn sends it to candidate eNodeB. The candidate eNodeB responds back with its address(es) for connectivity with the initiating/source eNodeB.

[0400] Utilizing geospatial coordination the GAA may initially provide the lessee eNodeBs with the lessor shared eNodeBs that could be considered valid neighbors. This may assist the ANR operations for mobility. In addition to the current neighbor list of the MOCN site, lessor side, may be replicated and utilized to populate the neighbor table of the lessee side of the MOCN site. Neighbor sites which are not in the lease area may be barred from the ANR table which may be modified by the DSC.

[0401] With DSA9 all the subscribers UEs on the lessee network may be eligible for DSA capability provided they have the hardware capabilities to utilize the radio channel frequency on the lessor system, unlike in DSAX.

[0402] The SPID may be used to designate which UEs may be selected for DSA during the lease period. The SPID for those designated UEs may be changed for the lease period where the radio channel frequency of the lessor may be added and put into the first choice selection which enables unique selection of specific UE' s for dynamic lease management.

[0403] With DSA9, selectivity of specific UEs is not guaranteed with SPID designation only since SON can override the SPID designation with a local SPID for all UEs using the eNodeB. Therefore, all the lessee UEs may become DSA eligible.

[0404] All the lessee eNodeBs which are within the Grid Area of the lease itself as defined by the GAA when the lease ends may have their Carrier Priority changed to remove the radio channel that is associated with the shared eNodeB on the lessor network. In addition the MLB for the lessee network for defined eNodeBs in the lease area may be modified to remove the LTE channel from the available selection criteria at the lessee network.

[0405] After a defined buffer time the SI -Flex connection may be removed between the lessee and lessor networks.

[0406] Once the lessee UE is on the lessor network, the UE may continue to remain on the lessor network since the lessor network eNodeBs may not have the lessee channels included as a selection of handover.

[0407] The border cell area may function differently with DSA9 as compared to DSAX and is really a buffer cell. Due to the shared eNodeB approach with DSA9 the border cells are not necessary. Instead, the eNodeBs on the lessor network which are in the lease area and border the lease boundary/grid, are called buffer cells. The ANR list for the lessee side of the eNodeB for those cells that are buffer cells may have their neighbor list populated at the lease inception and periodically checked on a regular basis to remove the exterior lessor cells from lessee use and the lessee cells may be removed from use by the lessor through barring in the ANR tables. This may be facilitated by the DSC.

[0408] Regarding buffer cells on the lessor network the eNodeB may have the lessee channel designed as valid choice. However at the conclusion of the lease, only the lessee Carrier may be included in the Carrier Priority list on the lessor network. The lessee may remove the lessor from the Carrier Priority list at the conclusion of the lease.

Additionally at the buffer cells the ANR table which may be modified to only include the lessee network eNodeBs.

[0409] Additionally the Emergency Blind Handover feature may be used on the border eNodeBs to direct the lessee UE back to its home network if it starts to lose coverage.

[0410] MLB can be also used to steer traffic from the lessor to the lessee network during at the conclusion of the lease for all lessor Interior cells. The MLB for the lessor border cells may also be adjusted to expedite the migration of lessee UEs back to the lessee network.

[0411] Additionally, on the lessor network MLB/MLD should not be configured to include the lessee network radio capacity at its disposal during the lease duration for the interior cell sites. At the end of the lease duration the lessee LTE channel may be configured in the MLB for selection with interior cell sites facilitating the lessee UEs to handover to the lessee system reflecting the preference for the lessee network channel.

[0412] If MLB is not available for use then static assignment for capacity on the shared eNodeB may be adjusted as a method for shedding traffic. Specifically the lessee may have 50%, then moved to 40%, and so on until it achieves 0% in sequential fashion with sufficient time to ensure the lessee user experience is maintained during and after the lease expiration.

[0413] The InterFreqHO message may be handled by the eNodeB of the lessor network and generally is not a network initiated InterFreqHO request as in DSAX through the Xe interface.

[0414] Therefore, with DSA9 the inclusion of SI -Flex with MOCN RAN Sharing, a path is available for the lessee UEs to handback to the lessee network when they are outside of the lease area.

[0415] During the lease period all the eNodeBs that are within the bid area may have their Carrier Priority listed as only that of the lessor networks carrier. At the conclusion of the lease all the interior cell sites for the bid area may have their Carrier Priority modified to only include the lessee Networks Carrier.

[0416] When the lease ends the SPID for all UEs involved with the lease may have their SPID changed at the lessee HSS and subsequently the lessee MME will be informed. However with SON capability, the SPID can be locally modified via SON. [0417] DSAX provides additional capabilities for graceful migration of UEs from a lessor network to the lessee network as compared to DSA9. Graceful migration may ensure that the lessee UEs are sent back in an orderly fashion. Graceful migration may involve selecting which UEs are handed back to the lessee network first based on their service class, QoS, or Bearer traffic that is being used. This can help avoid a situation in which there is a flood of UEs that are suddenly disconnected from a lessor network as they all attempt to reconnect to a lessee network at the end of a lease.

[0418] After the lease buffer time has expired, RAN sharing may be disabled on the lessor network for the particular lessee. The disabling of RAN sharing may force the connectivity via SI -Flex facilitating RAN sharing to be torn down. At that time all active lessees UEs on the lessor network may then have their session terminated in this scenario.

[0419] The removal of the Si-Flex connectivity may also inform the affected lessee eNodeBs that the radio channel capability of the lessor network being no longer available and will enable the lessee eNodeBs through SON. The MLB/MLD preferences depending on the OEM implementation may also need to be adjusted when removing the lessor channel preference.

[0420] All idle UEs that are camped on lessor eNodeB(s) may reselect the lessee network when the PLMN-ID of the lessee network is no longer transmitted by the lessor network.

[0421] Additionally the UEs that attempt to establish a session may no longer be able to choose the RF channel on the lessor network after the lease ends since the PLMN-ID of the lessee network will no longer be transmitted by the lessor network.

[0422] The ability to track the lease consumption based on data consumed, time expiration, or both is available for usage tracking of the lease with DSA9. The

consumption tracking method used for DSA9 may be different than that used in DSAX or DSA-Lite. [0423] Usage Tracking with DSA9 may be done by monitoring the consumed resources. For determining consumption levels it may be necessary to extract the consumption levels for the UEs using the lessor network. However since a MOCN RAN sharing approach can be used with DSA9, the S-GW of the lessor network not required to be involved. Therefore, the lessor network may not have any knowledge of the consumption taking place. As such with DSA9, the lessee network may report via the DSC to the DPC the consumption of usage. The DSC of the lessee Network may utilize the DPC to relay the traffic consumption details to the lessor DSC. The ending of the lease may still be initiated by the lessor DSC as in DSAX.

[0424] The time based approach for facilitating a lease by the lessor network may use a time component regardless of consumption levels. Therefore, when the lease time ends the lessor DSC may invoke the termination of the Lease as currently done in DSAX. This may eliminate the lessee DSCs involvement with tracking usage consumption.

[0425] FIG. 24 is a diagram illustrating an example embodiment where a lessor network uses a DSAX implementation and a lessee network uses a DSA9 implementation.

[0426] DSAFlex allows for another alternative configuration called DSA-Lite.

Specifically with DSA-Lite an intra-market roaming configuration following 3GPP's recommendation may be utilized. DSA-Lite however generally does not utilize the X- interface as with DSAX or RAN Sharing as with DSA9.

[0427] DSA-Lite has been an integral part of the DSA architecture from the inception of DSA and uses the least amount of interaction. However the respective DSCs still interact with LTE wireless networks O&M and OFCS platforms. Therefore, even with DSA- Lite, OEM vendor involvement may be needed to facilitate the execution of the lease parameters.

[0428] FIG. 25 is a diagram illustrating an example embodiment where both a lessor and lessee network use a DSA-Lite implementation. [0429] With DSA-Lite the lessee UEs utilize the lessor Network in a Roaming configuration where the lessee PLMN is transmitted on the SIB2 for the lessor eNodeB. The lessee user traffic is directed toward the lessee P-GW which may require a

connection that has sufficient bandwidth. The UEs may access the lessor Network if they are redirected based on carrier preference or may need to have the use of the lessor band included as a priority in the SPID.

[0430] Therefore, with DSA-Lite the lessee UE may be able to gain access to the lessor network upon detection of the PLMN-ID on the SIB 2.

[0431] Mobility management is generally not supported with DSA-Lite. Therefore, in DSA-Lite active lessee UEs generally can not handover from the lessee system to the lessor or from the lessor to the lessee network.

[0432] The grid area which designates the lease in the DSA-Lite configuration may not be as defined as with DSA9 or DSAX due to the lack of mobility between networks.

Specifically with DSA-Lite, during the lease period a lessee UE may be capable of handing off to cells outside of the grid area. The session in this case remains up. Once the session is completed, the normal reselection operations may take place where the lessee UE is outside of the lease area and may no longer be afforded service from that particular lease.

[0433] When the lease ends the PLMN-ID may cease to be transmitted on the SIB 2 of the lessor eNodeB. After a defined time the P-GW selection for the lessee UEs may no longer include the lessee P-GW.

[0434] For comparison, the following network architectures are presented which represent some of the possible configurations used with DSAFlex. In all the architecture diagrams, only one lessee and one lessor network are shown to facilitate the concept. It is possible to have more perturbations using more than two networks based on the various network implementations of DSAFlex. [0435] FIG. 26 is a diagram illustrating an example embodiment where a lessor network uses a DSA-Lite implementation and a lessee network uses a DSAX implementation, which is discussed in detail above.

[0436] The various embodiments may be implemented on a variety of mobile wireless computing devices, an example of which is illustrated in FIG. 27. Specifically, FIG. 27 is a system block diagram of a mobile transceiver device in the form of a smartphone/cell phone 2700 suitable for use with any of the embodiments. The cell phone 2700 may include a processor 2701 coupled to internal memory 2702, a display 2703, and to a speaker 2704. Additionally, the cell phone 2700 may include an antenna 2705 for sending and receiving electromagnetic radiation that may be connected to a wireless data link and/or cellular telephone transceiver 2706 coupled to the processor 2701. Cell phones 2700 typically also include menu selection buttons or rocker switches 2707 for receiving user inputs.

[0437] A typical cell phone 2700 also includes a sound encoding/decoding (CODEC) circuit 2708 which digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes received sound data packets to generate analog signals that are provided to the speaker 2704 to generate sound. Also, one or more of the processor 2701, wireless transceiver 2706 and CODEC 2708 may include a digital signal processor (DSP) circuit (not shown separately). The cell phone 2700 may further include a ZigBee transceiver (i.e., an IEEE 802.15.4 transceiver) for low-power short-range communications between wireless devices, or other similar communication circuitry (e.g., circuitry implementing the Bluetooth® or WiFi protocols, etc.).

[0438] The embodiments described above, including the spectrum arbitrage functions, may be implemented within a broadcast system on any of a variety of commercially available server devices, such as the server 2200 illustrated in FIG. 28. Such a server 2800 typically includes a processor 2801 coupled to volatile memory 2802 and a large capacity nonvolatile memory, such as a disk drive 2803. The server 2800 may also include a floppy disc drive, compact disc (CD) or DVD disc drive 2804 coupled to the processor 2801. The server 2800 may also include network access ports 2806 coupled to the processor 2801 for establishing data connections with a network 2807, such as a local area network coupled to other communication system computers and servers.

[0439] The processors 2701, 2801, may be any programmable microprocessor, microcomputer or multiple processor chip or chips that can be configured by software instructions (applications) to perform a variety of functions, including the functions of the various embodiments described below. In some wireless devices, multiple processors 2801 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 2702, 2802, before they are accessed and loaded into the processor 2701, 2801. The processor 2701, 2801 may include internal memory sufficient to store the application software instructions. In some servers, the processor 2801 may include internal memory sufficient to store the application software instructions. In some receiver devices, the secure memory may be in a separate memory chip coupled to the processor 2701. The internal memory 2702, 2802 may be a volatile or nonvolatile memory, such as flash memory, or a mixture of both. For the purposes of this description, a general reference to memory refers to all memory accessible by the processor 2701, 2801, including internal memory 2702, 2802, removable memory plugged into the device, and memory within the processor 2701, 2801 itself.

[0440] The foregoing method descriptions and the process flow diagrams are provided merely 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 will be appreciated by one of skill in the art the order of 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 simply used to guide the reader through the description of the methods. Further, any reference to claim elements in the singular, for example, using the articles "a," "an" or "the" is not to be construed as limiting the element to the singular.

[0441] 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.

[0442] 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, microcontroller, 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 specific to a given function.

[0443] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium or non-transitory processor-readable medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module which may reside on a non-transitory computer-readable or processor- readable storage medium. Non-transitory computer-readable or processor-readable storage media may be any storage media that may be accessed by a computer or a processor. By way of example but not limitation, such non-transitory computer-readable or processor-readable media may include RAM, ROM, EEPROM, FLASH memory, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may 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 are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

[0444] The preceding 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 spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. A dynamic spectrum arbitrage (DSA) method, comprising

broadcasting a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network;

determining lease criteria parameters of a resource lease associated with the advertised telecommunication resource;

determining network capability of the second telecommunication network;

selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria;

determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration; and

sending the determined configuration parameters to components in each of the first and second networks.

2. The DSA method of claim 1, wherein:

selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria comprises selecting the DSAX network configuration; and sending the determined configuration parameters to components in each of the first and second networks comprises sending the determined configuration parameter directly to the components in the first and second networks.

3. The DSA method of claim 1, wherein sending the determined configuration parameter directly to the components in the first and second networks comprises:

sending configuration parameters to an eNodeB via an Xe interface; and sending configuration parameters to an MME component via an Xm interface.

4. The DSA method of claim 1, wherein:

selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria comprises selecting the DSA Lite network configuration or the DSA9 network configuration; and

sending the determined configuration parameters to components in each of the first and second networks comprises sending the determined configuration parameters to an O&M component in each of the first and second networks.

5. The DSA method of claim 1, wherein determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration comprises:

determining configuration parameters that match a specific OEM format.

6. The DSA method of claim 4, wherein sending the determined configuration parameters to components in each of the first and second networks comprises sending the parameters in the specific OEM format.

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

dynamically selecting an interface based on the determined network capability.

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

routing traffic to destination components based on the network configuration of the second network;

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

receiving in a dynamic spectrum controller (DSC) processor a list of resources that are available for bidding via a communication link to a dynamic spectrum policy controller (DPC) that includes a DPC processor;

generating a bid request message that includes information suitable for bidding on a resource identified in the received list of resources; and

sending the generated bid request message to the DPC via the communication link.

10. The DSA method of claim 9, further comprising

starting by the DPC processor a bid timer;

receiving in the DPC processor the bid request message from the DSC via the communication link;

determining whether the bid request message is valid;

sending a bid accept message to the DSC via the communication link in response to determining that the bid is valid;

determining whether the bid timer has expired;

determining whether the DSC is a winner bidder that is to be allocated the resource based on information included in the bid request message in response to determining that the bid request message is valid and that the bid timer has expired; and sending a bid won message to the DSC via the communication link in response to determining that the DSC is the winner bidder.

11. A server computing device, comprising:

a processor configured with processor executable instructions to perform

operations comprising:

determining network capability of the second telecommunication network; selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria;

12. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations such that:

selecting one of a DSA Lite network configuration, DSA9 network configuration, and DSAX network configuration based on the determined network capability and determined lease criteria comprises selecting the DSAX network configuration; and

sending the determined configuration parameters to components in each of the first and second networks comprises sending the determined configuration parameter directly to the components in the first and second networks.

13. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations such that sending the determined configuration parameter directly to the components in the first and second networks comprises:

14. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations such that:

15. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations such that determining

configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration comprises: determining configuration parameters that match a specific OEM format.

16. The computing device of claim 14, wherein the processor is configured with processor executable instructions to perform operations such that sending the determined configuration parameters to components in each of the first and second networks comprises sending the parameters in the specific OEM format.

17. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations further comprising:

dynamically selecting an interface based on the determined network capability.

18. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations further comprising: routing traffic to destination components based on the network configuration of the second network;

19. The computing device of claim 11, wherein the processor is configured with processor executable instructions to perform operations further comprising:

receiving a list of resources that are available for bidding via a communication link to a dynamic spectrum policy controller (DPC) that includes a DPC processor;

20. The computing device of claim 19, wherein the processor is configured with processor executable instructions to perform operations further comprising:

starting by the DPC processor a bid timer;

receiving in the DPC processor the bid request message from a DSC via the communication link;

determining whether the bid request message is valid;

determining whether the bid timer has expired;

21. A non-transitory computer readable storage medium having stored thereon

processor-executable software instructions configured to cause a processor to perform operations comprising: broadcasting a communication message that includes information advertising that a telecommunication resource in a first telecommunication network is available for allocation and use by wireless devices in a second telecommunication network;

determining network capability of the second telecommunication network;

22. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations such that:

23. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations sending the determined configuration parameter directly to the components in the first and second networks comprises: sending configuration parameters to an eNodeB via an Xe interface; and sending configuration parameters to an MME component via an Xm interface.

24. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations such that:

25. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations such that determining configuration parameters for one or more nodes in each of the first and second telecommunication networks based on the selected network configuration comprises:

determining configuration parameters that match a specific OEM format.

26. The non-transitory computer readable storage medium of claim 24, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations such that sending the determined configuration parameters to components in each of the first and second networks comprises sending the parameters in the specific OEM format.

27. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations further comprising:

dynamically selecting an interface based on the determined network capability.

28. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations further comprising:

29. The non-transitory computer readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations further comprising:

30. The non-transitory computer readable storage medium of claim 29, wherein the stored processor-executable software instructions are configured to cause the mobile device processor to perform operations further comprising

starting by the DPC processor a bid timer;

determining whether the bid request message is valid;

sending a bid accept message to the DSC via the communication link in response to determining that the bid is valid; determining whether the bid timer has expired;