System and method for spectrum sharing
Claim Score by NHIP
Abstract
A method for spectrum coexistence includes determining interference from a primary network to a secondary network that is independent from the primary network, determining transmission parameters for a network element of the secondary network that mitigate interference from the secondary network to the primary network, and transmitting signals from the network element according to the determined transmission parameters. The network element could be a base station or user equipment. Accordingly, a secondary network can coexist with a primary network even when the networks do not communicate with each other.

Term
Projected expiry 15 April 2035.
- Priority
- Filed
- Published
- Today
- Projected expiry
20 claims: 2 independent, 18 dependent
- 1Broadest claimClaim Score 85, broad(NHIP)A spectrum coexistence method comprising:determining interference from a primary network to a secondary network that is independent from the primary network;determining transmission parameters for a network element of the secondary network that mitigate interference from the secondary network to the primary network;and transmitting signals from the network element according to the determined transmission parameters.
- 11A spectrum coexistence system comprising:a plurality of base stations;a performance assurance module that receives network performance data for a first network that includes the plurality of base stations;an interference detection and classification module that determines interference to the spectrum coexistence system from an independent network that is independent from the first network;and an interference mitigation module that determines transmission parameters for the plurality of base stations that mitigate interference from communications with the plurality of base stations to the independent network.
Independent claims2
93 paragraphs in 5 sections, as filed
CROSS-REFERENCES TO RELATED APPLICATIONS
The present invention claims priority to U.S. Provisional Application No. 61/979,680, filed Apr. 15, 2014, which is incorporated by reference herein for all purposes.
This invention was made with government support under contract number N0001413C0194 awarded by the Office of Naval Research. The government has certain rights in the invention.
BACKGROUND
Radio Frequency (RF) spectrum is a limited and extremely valuable resource. The amount of data transmitted wirelessly has been increasing exponentially in recent years. While technology has been evolving to make more efficient use of the limited RF spectrum available to certain technologies, the demand for spectrum resources has exceeded the improvements from those efficiencies.
The RF spectrum is typically constrained by local laws and regulations. The regulations generally allocate portions of the spectrum to certain technologies. For example, governments generally set aside particular portions of the spectrum for emergency and military services, television broadcasts, satellite transmissions, etc. Some of the services that occupy portions of the spectrum do not fully utilize those portions of the spectrum.
For example, a portion of the spectrum allocated for military purposes may be used extensively at a military site, but only have limited use in civilian areas. Similarly, while a portion of the spectrum allocated for television broadcasts may be sufficient to simultaneously handle up to 100 channels, only a few channels may be present in a particular location at a given time. Thus, while portions of the RF spectrum are highly loaded, other portions of the frequency spectrum are under-utilized.
BRIEF SUMMARY
Embodiments of the present disclosure relate to a system and method for radio frequency (RF) spectrum sharing between primary and secondary users. Aspects of the present disclosure may be implemented as a method, a system, or an apparatus.
In an embodiment, a spectrum coexistence method includes determining interference from a primary network to a secondary network that is independent from the primary network, determining transmission parameters for a network element of the secondary network that mitigate interference from the secondary network to the primary network, and transmitting signals from the network element according to the determined transmission parameters. Determining interference to the secondary network may include searching a database of external interference, and the database of external interference may include data for a plurality of predetermined interference sources that are known to transmit RF signals that interfere with the secondary network.
Determining interference to the secondary network may include measuring, by an element of the secondary network, signals that interfere with the secondary network, and classifying the measured signals by one or more characteristic of the signals. The classified signal can be used to determine the transmission parameters. The method may include adding the classified signal to the database of external interference.
In an embodiment, determining interference from the primary network includes localizing a source of the interference by a geolocation engine of the secondary network. Determining transmission parameters may include applying a spectrum policy from a spectrum policy database of the first network, and determining transmission parameters may include performing a simulation with an RF coverage prediction engine included in the secondary network.
Determining the interference and determining transmission parameters for the network element can be performed by a central network element using information from an Operation, Administration and Maintenance system, and the central network element is coupled to a plurality of base stations through low latency connections. In another embodiment, performing determining transmission parameters is distributed between a plurality of Self Organizing Network (SON) agents disposed at various network elements based on spectrum policy parameters stored at a central network element.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idref="DRAWINGS">FIG. 1</figref> illustrates an embodiment of a wireless communications network.
<figref idref="DRAWINGS">FIG. 2</figref> illustrates an embodiment of a network resource controller.
<figref idref="DRAWINGS">FIG. 3</figref> illustrates a secondary network in the presence of primary networks.
<figref idref="DRAWINGS">FIG. 4</figref> illustrates an embodiment of a Spectrum Coexistence Self Organizing Network (SC-SON) device.
<figref idref="DRAWINGS">FIG. 5</figref> illustrates an embodiment of an LTE communications system.
<figref idref="DRAWINGS">FIG. 6</figref> illustrates an embodiment of a centralized SC-SON system.
<figref idref="DRAWINGS">FIG. 7</figref> illustrates an embodiment of a hybrid SC-SON system.
<figref idref="DRAWINGS">FIG. 8</figref> illustrates an embodiment of a spectrum coexistence method.
DETAILED DESCRIPTION
Spectrum sharing is a promising technology to address the growing demand for mobile data in commercial wireless networks. Self Organizing Network (SON) systems, already widely adopted by operator and standards bodies to manage and optimize commercial wireless networks, are particularly well suited for implementing spectrum sharing techniques. Accordingly, embodiments of this disclosure relate to a SON system, referred to here as the Spectrum-Coexistence SON (SC-SON), that enables wireless networks to share spectrum with other users.
In an embodiment, an SC-SON enables a wireless cellular communications network to share spectrum with a network that may or may not be based on a cellular telecommunications technology, such as broadcast network, radar network, and wireless device communication network. The SC-SON may be flexible enough that the wireless telecommunications network could be either a primary or a secondary user of the spectrum.
In an embodiment, a primary network is an original occupant of a portion of frequency spectrum that is shared by a secondary network, however, embodiments are not limited thereto. A primary user may be given precedence over a secondary user when sharing spectrum. For example, a primary user may be an emergency broadcast system which is given priority over a cellular telecommunications network that is a secondary user. Various embodiments of a SC-SON system may be implemented as a centralized system or a hybrid system.
Embodiments of this disclosure can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
A detailed description of embodiments is provided below along with accompanying figures. The scope of this disclosure is limited only by the claims and encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding. These details are provided for the purpose of example and embodiments may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to this disclosure have not been described in detail so that this disclosure is not unnecessarily obscured.
<figref idref="DRAWINGS">FIG. 1</figref> illustrates a networked communications system <b>100</b> according to an embodiment of this disclosure. As depicted, system <b>100</b> includes a data communications network <b>102</b>, one or more base stations <b>106</b><i>a</i>-<i>e, </i>one or more network resource controller <b>110</b><i>a</i>-<i>c, </i>and one or more User Equipment (UE) <b>108</b><i>a</i>-<i>m. </i>As used herein, the term “base station” refers to a wireless communications station provided in a location and serves as a hub of a wireless network. The base stations may include macrocells, microcells, picocells, and femtocells.
In a network <b>100</b> according to an embodiment, the data communications network may include a backhaul portion that can facilitate distributed network communications between any of the network controller devices <b>110</b><i>a</i>-<i>c </i>and any of the base stations <b>106</b><i>a</i>-<i>e. </i>Any of the network controller devices <b>110</b><i>a</i>-<i>c </i>may be a dedicated Network Resource Controller (NRC) that is provided remotely from the base stations or provided at the base station. Any of the network controller devices <b>110</b><i>a</i>-<i>c </i>may be a non-dedicated device that provides NRC functionality among others. The one or more UE <b>108</b><i>a</i>-<i>m </i>may include cell phone devices <b>108</b><i>a</i>-<i>i, </i>laptop computers <b>108</b><i>j</i>-<i>k, </i>handheld gaming units <b>108</b><i>l, </i>electronic book devices or tablet PCs <b>108</b><i>m, </i>and any other type of common portable wireless computing device that may be provided with wireless communications service by any of the base stations <b>106</b><i>a</i>-<i>e. </i>
As would be understood by those skilled in the Art, in most digital communications networks, the backhaul portion <b>102</b> of a data communications network <b>100</b> may include intermediate links between a backbone of the network which are generally wire line, and sub networks or base stations <b>106</b><i>a</i>-<i>e </i>located at the periphery of the network. For example, cellular user equipment (e.g., any of UE <b>108</b><i>a</i>-<i>m</i>) communicating with one or more base stations <b>106</b><i>a</i>-<i>e </i>may constitute a local sub network. The network connection between any of the base stations <b>106</b><i>a</i>-<i>e </i>and the rest of the world may initiate with a link to the backhaul portion of an access provider's communications network (e.g., via a point of presence).
In an embodiment, an NRC has presence and functionality that may be defined by the processes it is capable of carrying out. Accordingly, the conceptual entity that is the NRC may be generally defined by its role in performing processes associated with embodiments of the present disclosure. Therefore, depending on the particular embodiment, the NRC entity may be considered to be either a hardware component, and/or a software component that is stored in computer readable media such as volatile or non-volatile memories of one or more communicating device(s) within the network <b>100</b>.
In an embodiment, any of the network controller devices <b>110</b><i>a</i>-<i>c </i>and/or base stations <b>106</b><i>a</i>-<i>e </i>may function independently or collaboratively to implement processes associated with various embodiments of the present disclosure.
In accordance with a standard GSM network, any of the network controller devices <b>110</b><i>a</i>-<i>c </i>(NRC devices or other devices optionally having NRC functionality) may be associated with a base station controller (BSC), a mobile switching center (MSC), a data scheduler, or any other common service provider control device known in the art, such as a radio resource manager (RRM). In accordance with a standard UMTS network, any of the network controller devices <b>110</b><i>a</i>-<i>c </i>(optionally having NRC functionality) may be associated with a NRC, a serving GPRS support node (SGSN), or any other common network controller device known in the art, such as an RRM. In accordance with a standard LTE network, any of the network controller devices <b>110</b><i>a</i>-<i>c </i>(optionally having NRC functionality) may be associated with an eNodeB base station, a mobility management entity (MME), or any other common network controller device known in the art, such as an RRM.
In an embodiment, any of the network controller devices <b>110</b><i>a</i>-<i>c, </i>the base stations <b>106</b><i>a</i>-<i>e, </i>as well as any of the UE <b>108</b><i>a</i>-<i>m </i>may be configured to run any well-known operating system, including, but not limited to: Microsoft® Windows®, Mac OS®, Google® Chrome®, Linux®, Unix®, or any mobile operating system, including Symbian®, Palm®, Windows Mobile®, Google® Android®, Mobile Linux®, etc. Any of the network controller devices <b>110</b><i>a</i>-<i>c, </i>or any of the base stations <b>106</b><i>a</i>-<i>e </i>may employ any number of common server, desktop, laptop, and personal computing devices.
In an embodiment, any of the UE <b>108</b><i>a</i>-<i>m </i>may be associated with any combination of common mobile computing devices (e.g., laptop computers, tablet computers, cellular phones, handheld gaming units, electronic book devices, personal music players, MiFi™ devices, video recorders, etc.), having wireless communications capabilities employing any common wireless data communications technology, including, but not limited to: GSM, UMTS, 3GPP LTE, LTE Advanced, WiMAX, etc.
In an embodiment, the backhaul portion <b>102</b> of the data communications network <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref> may employ any of the following common communications technologies: optical fiber, coaxial cable, twisted pair cable, Ethernet cable, and power-line cable, along with any other wireless communication technology known in the art. In context with various embodiments of the invention, it should be understood that wireless communications coverage associated with various data communication technologies (e.g., base stations <b>106</b><i>a</i>-<i>e</i>) typically vary between different service provider networks based on the type of network and the system infrastructure deployed within a particular region of a network (e.g., differences between GSM, UMTS, LTE, LTE Advanced, and WiMAX based networks and the technologies deployed in each network type).
<figref idref="DRAWINGS">FIG. 2</figref> illustrates a block diagram of an NRC <b>200</b> that may be representative of any of the network controller devices <b>110</b><i>a</i>-<i>c. </i>Accordingly, NRC <b>200</b> may be representative of a Network Manager (NM), an Element Manager (EM), a domain manager (DM), a SON server, etc., that is present in an embodiment of this disclosure. The NRC <b>200</b> has one or more processor devices including a CPU <b>204</b>.
The CPU <b>204</b> is responsible for executing computer programs stored on volatile (RAM) and nonvolatile (ROM) memories <b>202</b> and a storage device <b>212</b> (e.g., HDD or SSD). In some embodiments, storage device <b>212</b> may store program instructions as logic hardware such as an ASIC or FPGA. Storage device <b>212</b> may store, for example, an interference detection/classification module <b>214</b>, a performance assurance module <b>216</b>, and an interference mitigation module <b>218</b>.
The NRC <b>200</b> may also include a user interface <b>206</b> that allows an administrator to interact with the NRC's software and hardware resources and to display the performance and operation of the system <b>100</b>. In addition, the NRC <b>200</b> may include a network interface <b>206</b> for communicating with other components in the networked computer system, and a system bus <b>210</b> that facilitates data communications between the hardware resources of the NRC <b>200</b>.
In addition to the network controller devices <b>110</b><i>a</i>-<i>c, </i>the NRC <b>200</b> may be used to implement other types of computer devices, such as an antenna controller, an RF planning engine, a core network element, a database system, or the like. Based on the functionality provided by an NRC, the storage device of such a computer serves as a repository for software and database thereto.
<figref idref="DRAWINGS">FIG. 3</figref> shows an example of several primary networks <b>300</b> which share spectrum with a secondary network <b>350</b>. The primary networks <b>300</b> shown in <figref idref="DRAWINGS">FIG. 3</figref> are a television network <b>300</b><i>a, </i>a wireless microphone network <b>300</b><i>b, </i>and an emergency communications network <b>300</b><i>c. </i>A primary network may be a broadcast system that covers a relatively large area such as television network <b>300</b><i>a, </i>a one-way transmission system such as wireless microphone network <b>300</b><i>b, </i>or a bi-directional communications system such as emergency communications network <b>300</b><i>c. </i>However, embodiments are not limited to these examples. In other embodiments, other systems that transmit signals in the RF spectrum may be a primary network <b>300</b>.
The primary network <b>300</b> uses portions of the RF spectrum that interfere with secondary network <b>350</b>. Thus, a primary network <b>300</b> may use a portion of the RF spectrum that overlaps with or is near to a portion of the RF spectrum that is used by the secondary network <b>350</b>. A primary network <b>300</b> may be a civilian system or a government system.
The primary network <b>300</b> may be established as having primacy for the portion of spectrum that it uses by a government entity. For example, in the United States, television networks <b>300</b> are registered with the Federal Communications Commission to have primacy in certain frequency bands. In some jurisdictions, primary networks have exclusive rights to a portion of the RF spectrum. Embodiments of this disclosure facilitate the operation of other RF communication systems in an interfering portion of RF spectrum so that the primary networks maintain primacy in the allocated portion of spectrum. In other words, embodiments facilitate sharing a portion of frequency spectrum between a primary network <b>300</b> and a secondary network <b>350</b> in a way that minimizes impacts to the primary network <b>300</b>.
In an embodiment, each of the primary networks <b>300</b> are independent from the secondary network <b>350</b>. In other words, each primary network <b>300</b> is autonomous from the secondary network <b>350</b>. Accordingly, the primary networks <b>300</b> are operated and controlled separately from the secondary network <b>350</b>. Therefore, according to embodiments of this disclosure, a primary network <b>300</b> may operate normally without any accommodation for a secondary network <b>350</b>, while the secondary network adapts to minimize interference to and accept interference from the primary network <b>300</b>.
<figref idref="DRAWINGS">FIG. 4</figref> shows an embodiment of a Spectrum Coexistence Self-Organizing Network (SC-SON) system <b>400</b>. The primary network <b>400</b> includes three key modules: an interference and detection module <b>402</b>, a performance assurance module <b>404</b>, and an interference mitigation module <b>406</b>. Each of the modules may be disposed in a single physical location, or elements of one or more module may be distributed across multiple physical locations or entities.
In an embodiment, a module is a set of computer executable instructions that is stored on a computer readable medium. In another embodiment, one or more aspect of a given module is a hard-coded circuit such as an application-specific integrated circuit (ASIC) or field-programmable gate array (FPGA). In still another embodiment, a module includes both hard coded circuits and computer readable media.
The main control interfaces in the SC-SON system are shown using dotted arrows in <figref idref="DRAWINGS">FIG. 4</figref>. Accordingly, the user configuration module <b>408</b> may be used to initiate operation of the interference and detection module <b>402</b>, an interference mitigation module <b>404</b>, and performance assurance module <b>406</b>. Similarly, the performance assurance module <b>404</b> can be used to initiate the interference detection module <b>402</b> and the interference mitigation module <b>406</b>.
The SC-SON system <b>400</b> may include an interference database <b>410</b>. The interference database <b>410</b> may be internally maintained by the SC-SON system <b>400</b>. In an embodiment, the interference database <b>410</b> is populated by data from an external spectrum access managing entity, such as a spectrum access database, that provides information about the location and transmission characteristics of primary users of the spectrum.
For example, when a primary user to be managed by the SC-SON system <b>400</b> is a television network <b>300</b><i>a, </i>the SC-SON system <b>400</b> could query a white space database and store information about broadcast station locations, frequencies, transmission powers, and white spaces between channels as they exist in the vicinity of secondary network <b>350</b>. A non-exhaustive list of information that may be stored in the interference database <b>410</b> includes transmitter location, transmission power, transmission frequencies, transmission times, signal characteristics at various locations other than the source of the transmissions, pointing directions of antennas, and spatial signatures of one or more primary and secondary networks <b>300</b> and <b>350</b>.
Information in database <b>410</b> may come from a variety of sources. For example, an entity that manages RF spectrum may maintain lists of approved installations at various locations, which is one possible source. Other sources are manual entry and polling of various external databases. Examples of spectrum databases that may be polled in the United States include the FCC's TV White Space Database, and the Spectrum Database maintained by GOOGLE™.
Information in the interference database <b>410</b> may be augmented with information from the interference detection and classification module <b>402</b>. For example the SC-SON system <b>400</b> may detect the presence of a wireless microphone that does not appear in an external database. In such a case, interference database <b>410</b> may be updated to include information for the detected wireless microphone.
The SC-SON system <b>400</b> may include a spectrum policy database <b>412</b> which may include policy control and functional objectives for the operation of the interference detection, performance assurance, and interference mitigation modules <b>402</b>, <b>404</b> and <b>406</b>. For example, spectrum policy database <b>412</b> may include times and locations for which interference detection mechanisms are activated, performance thresholds for the primary network <b>300</b> and the secondary network <b>350</b>, and performance goals of the interference mitigation techniques. More specifically, the spectrum policy database <b>412</b> may include QoS targets for the primary network <b>300</b> that may be achieved by mitigation applied to the secondary network <b>350</b>.
The spectrum policy database <b>412</b> may receive inputs from an external spectrum access managing entity or be configured by an operator. For example, in the TV white space scenario, information in the spectrum policy database could be derived from certified TV white space databases and could include restrictions on the maximum allowable transmit power or coverage region of the transmission nodes of the secondary network <b>350</b>.
The interference detection/classification module <b>402</b> coordinates the transmission and RF measurement at network elements to isolate and detect interference caused by external sources from intra-system interference caused by network elements. For example, module <b>402</b> may schedule quiet times in a communications network and measure signals received during those quiet times.
In addition, interference detection/classification module <b>402</b> may collate measurements <b>424</b> from distributed network elements to build an interference fingerprint that can be used to classify the interferer. The interference fingerprint may be developed from a pattern of times, frequencies, and strengths of received signals. If available, the SC-SON system <b>400</b> may collect and collate external sensor data <b>420</b> from external sensor networks as well.
The interference detection/classification module <b>402</b> may interface with the interference database <b>410</b>. Information about interferers from the database <b>410</b> may be used in the interference classification process. For example, interference features may be compared to features of interferers that are known to exist in the vicinity of the SC-SON system <b>400</b> to identify the interferers. When an unknown interferer's fingerprint matches characteristics of a known interferer, module <b>402</b> may determine that the unknown interferer is the same type of entity as the known interferer.
Once new interferers are classified in the interference detection/classification module <b>402</b>, information about the interferers may be added to the interference database <b>410</b>. Therefore the module may use information from the interference database <b>410</b> as well as augment information in the interference database <b>410</b>.
Measurement data <b>424</b> collected by the interference detection/classification module <b>402</b> may be also be processed by a Geolocation module <b>414</b> in the SC-SON system <b>400</b> to localize the interferer source. When available, location information can be helpful in further characterizing and classifying an interferer. For example it may be known or otherwise assumed that wireless microphones are the only type of interferer present in a particular region. If geolocation information shows that an un-classified interferer is from this region, then the interferer can be assumed to be a wireless microphone.
When geolocation information for interferers is available, the geolocation information may be added to the interference database <b>410</b>. When interference is detected, the module <b>410</b> may interface with an alarm subsystem <b>408</b> to report the interferer.
The operation of the interference detection/classification module <b>402</b> may be initiated by a user from the user-configuration module <b>408</b>. The user may configure interference module <b>402</b> to be run once, periodically or continually. The operation of the module <b>402</b> may also be initiated by the performance assurance module <b>404</b> when it perceives irregularities in performance metrics <b>426</b>.
In an embodiment, the performance assurance module <b>404</b> subsystem retrieves performance data <b>426</b> from a secondary network <b>350</b> and builds and analyzes KPI trends to detect the presence of interference. In addition, module <b>404</b> may monitor the performance of implemented interference mitigation strategies.
If the presence of interference is indicated by anomalies in the KPI trends, the interference detection and classification module <b>402</b> may be triggered to detect and classify the source of the interference. KPI trends themselves may also be used by the interference detection and classification module in characterizing certain types of interferers. For example, performance degradations that periodically repeat may represent interference from a pulsed transmission source such as a Radar system.
The performance assurance module <b>404</b> may also interface with the alarm module <b>408</b> and external reporting modules to report any anomalies in expected KPI trends. The operation of performance assurance module <b>404</b> may be initiated by the user from the user-configuration module <b>408</b>. The user may configure the module <b>404</b> to be run once, periodically or continually.
The interference mitigation module <b>406</b> uses information about the detected and classified interference sources from the interference database <b>410</b> to dynamically optimize the configuration of a secondary network <b>350</b> to minimize the effect of interference from the secondary network <b>350</b> on a primary network <b>300</b>. The interference mitigation module <b>406</b> then pushes the optimized configuration parameters to the secondary network <b>350</b>. Interference mitigation module <b>406</b> may also interface with an RF coverage prediction tool <b>416</b> to analyze the impact of interference on the primary or secondary network <b>300</b> or the secondary network <b>350</b>, as well as to predict the impact of particular interference mitigation adaptations before pushing changes to network equipment.
Operations of the interference mitigation module <b>406</b> may be periodically logged and reported to a user via the user-configuration module <b>408</b>. The operation of interference mitigation module <b>406</b> may be initiated by the user from the user-configuration module <b>408</b>. The user may configure mitigation module <b>406</b> to be run once, periodically or continually. The user may also configure the interference mitigation module to run every time that a new interferer is added to the interference database <b>410</b>.
The Geolocation module <b>414</b> may allow other SC-SON modules to localize transmission nodes using measurements of their RF energy from distributed nodes within the network.
In an embodiment, the Geolocation module <b>414</b> is a server-based implementation with a well-defined API through which other SC-SON modules can dynamically initiate and receive location estimates based on RF measurements. In an embodiment, Geolocation module <b>414</b> is a generalized implementation that may be used for both geo-locating network nodes such as user equipment (UEs) and external interferers within a network. In another embodiment, Geolocation module <b>414</b> is a module that is used specifically for geo-locating external interferers. RF coverage prediction module <b>416</b> allows SC-SON modules to perform run-time RF predictions of specific scenarios, and the results of these predictions may be used within the decision logic of various modules. Various configuration parameters of base stations may be tested by the coverage prediction module <b>416</b> to evaluate the potential impact of changes to the configuration parameters.
In an embodiment, the RF coverage prediction module <b>416</b> is a server-based implementation that has a well-defined API through which other SC-SON modules can dynamically initiate and receive results for portions of the network. The RF prediction module <b>416</b> may incorporate 2D and 3D ray-tracing capability and outdoor to indoor coverage models. For refined accuracy, the propagation models may consider the attenuation and height of clutter databases at the receiver location or at each study point (point or pass-through clutter attenuation options) as well as 3D vector building databases for dense urban modeling.
With reference to the SC-SON system <b>400</b>, the Geolocation module <b>414</b> and the interference mitigation module <b>406</b> may leverage results from various sources such as the dynamic RF coverage prediction analysis performed by RF coverage prediction module <b>416</b>. As seen in <figref idref="DRAWINGS">FIG. 4</figref>, outputs from Geolocation module <b>414</b> may be incorporated into interference database <b>410</b>, and Geolocation module <b>414</b> may receive data from RF coverage prediction module <b>416</b>, interference database <b>410</b> and interference detection and classification module <b>402</b> to assist with determining Geolocations.
The alarm/log/user-configuration module <b>408</b> provides the external user interface for the SC-SON system <b>400</b>. The dotted arrows from module <b>408</b> to the interference detection and classification module <b>402</b>, performance assurance module <b>404</b> and interference mitigation module <b>406</b> indicate that module <b>408</b> may allow the operation of the these modules to be configured and initiated by a user. Module <b>408</b> may also maintain a log of data reported by the different SC-SON modules including alarms related to the identification of an external interferer. In addition, it may maintain a log of the decisions made by various SC-SON modules. Although <figref idref="DRAWINGS">FIG. 4</figref> shows the alarm, logging and user-configuration elements as being incorporated into a single module <b>408</b>, in other embodiments, these elements may be incorporated into discrete modules or combined with other modules.
<figref idref="DRAWINGS">FIG. 5</figref> shows elements of an LTE system <b>5</b> that may be involved in implementing an embodiment of the present disclosure. Specific implementations may be described as a centralized embodiment and a hybrid embodiment, which will be explained in more detail with respect to <figref idref="DRAWINGS">FIGS. 6 and 7</figref>. Although the embodiments are described with respect to an LTE system, it should be recognized that the technology in this disclosure applies to other wireless communication technologies as well.
As seen in <figref idref="DRAWINGS">FIG. 5</figref>, an LTE system <b>500</b> includes a plurality of base stations <b>502</b><i>a</i>-<i>d </i>which are in wireless communication with a plurality of UE. In the embodiment shown in <figref idref="DRAWINGS">FIG. 5</figref>, the base stations <b>502</b> are eNodeBs which are directly coupled to one another through a low-latency X2 interface.
In an LTE network, an Operation, Administration and Maintenance (OA&M) system includes of multiple management components such as a Network Manager (NM) <b>504</b>, a Domain Manager (DM) <b>506</b>, and Element Managers (EMs) <b>508</b><i>a</i>-<i>d. </i>The managers and other aspects of an OA&M system are described in the 3<sup>rd </sup>Generation Partnership Project (3GPP) Technical Specification (TS) 32.101, version 11.1.0, Release 11 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Principles and high level requirements) and 3GPP TS 32.342 version 11.0.0 Release 11 (Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS)).
EMs <b>508</b><i>a</i>-<i>d </i>manage a set of related types of network elements. For an LTE network, these network elements include eNodeBs <b>502</b>. EMs <b>508</b> for eNodeBs <b>502</b> are typically implemented by eNodeB vendors and may physically reside with each eNodeB <b>502</b>. However, EMs <b>508</b> can also be used to manage a sub-network of eNodeBs <b>502</b>. A DM <b>506</b> manages a sub-network and may provide multi-vendor and multi-technology management functions. A NM <b>504</b> manages a network and is typically supported by EMs <b>508</b> and DMs <b>506</b>. NMs <b>504</b> typically offer multi-vendor and multi-technology support for underlying EMs<b>508</b> and network elements.
3GPP defines a standard open interface, Itf-N (Northbound interface) between DMs <b>506</b> and an NM <b>504</b> and between EMs <b>508</b> and the NM <b>504</b>. A standardized file transfer protocol is also specified for the Itf-N interface to retrieve Configuration Management (CM), Performance Management (PM) and Fault Management (FM) metrics from the EMs <b>508</b> and DMs <b>506</b> at the NM <b>504</b>. However, some specific implementations of a northbound interface are vendor specific. The interface between EMs <b>508</b> and network elements is called the Itf-S (Southbound interface) and is vendor specific.
<figref idref="DRAWINGS">FIG. 6</figref> shows an LTE-based embodiment of an LTE-based central SC-SON system <b>600</b>. In a central SC-SON system <b>600</b>, the elements of the SC-SON system <b>400</b> explained with respect to <figref idref="DRAWINGS">FIG. 4</figref> are implemented at a central network element <b>610</b> of a wireless communications network, which is referred to here as an SC-SON Central Controller (SSCC). In the embodiment shown in <figref idref="DRAWINGS">FIG. 6</figref>, the centralized SC-SON node <b>610</b> is a standalone system that interfaces with the OA&M components of an LTE network. In another embodiment (not shown), the SSCC <b>610</b> is implemented within the NM <b>504</b> of the OA&M system.
In a central SC-SON system <b>600</b>, various SON interfaces <b>612</b>, shown as dashed lines in <figref idref="DRAWINGS">FIG. 6</figref>, may be used to directly access data from all network elements including management systems such as NM <b>504</b> and EMs <b>508</b> and base stations <b>502</b>. The interfaces <b>612</b> may be standardized low latency interfaces to access, for example, measurement data for interference detection and transmission schedule information from base stations <b>502</b>. In other words, interfaces <b>612</b> may be used to transmit data used to implement spectrum sharing from various components of a communications network to SSCC <b>610</b>.
Interference measurements and performance data from the entire network may be collated at the central node <b>610</b> to detect, characterize and localize external interference from a primary network <b>300</b>. Similarly, these metrics may also be used to identify interference mitigation strategies that are optimal from a global perspective for the LTE network.
The centralized SC-SON node <b>610</b> may access CM, PM, FM and event data at the NM <b>504</b>. If the SC-SON node <b>610</b> is implemented within the NM <b>504</b>, CM, PM, FM and event data may be directly accessed via the EMs <b>508</b> and DMs <b>506</b> using the Itf-N interface.
However, not all the information required for fast time-scale resource allocation decisions (including transmission schedule information as well as measurement data for interference detection support) is accessible via the CM, PM and FM metrics defined in 3GPP 32 series Technical Specifications. In addition, latency associated with the information flow from the higher-level network manager <b>504</b> to the eNodeBs <b>502</b> limits the possible time-resolution for network optimizations. Therefore, the SSCC <b>610</b> may implement standardized or proprietary low latency interfaces, shown as dashed lines <b>612</b> in <figref idref="DRAWINGS">FIG. 6</figref>, to the eNodeBs <b>502</b>, or to EMs <b>508</b> that are implemented within eNodeBs, such as EM <b>508</b><i>a </i>which is implemented within base station <b>502</b><i>a </i>in <figref idref="DRAWINGS">FIG. 6</figref>.
Access to real-time information from the low-latency interfaces <b>612</b> allows the SSCC <b>610</b> to perform fast time-scale optimization of parameters of base stations <b>502</b>. However, performing optimizations for an entire network or large portion of a network from a single central node <b>610</b> may place an excessive processing burden on certain central nodes <b>610</b>. In addition, high-resolution optimizations from a global perspective for an entire network may be prohibitively complex. Therefore, a hybrid implementation in which some SC-SON functionality is distributed across the network may be used.
<figref idref="DRAWINGS">FIG. 7</figref> shows an embodiment of an LTE based hybrid SC-SON system <b>700</b>, in which aspects of SC-SON system <b>400</b> are distributed across multiple physical entities. System <b>700</b> includes a centralized component <b>720</b> that coordinates the SC-SON functionality of the distributed SC-SON components. The centralized component is referred to here as the SC-SON Central Controller (SSCC) <b>720</b>.
With reference to <figref idref="DRAWINGS">FIG. 4</figref>, in an embodiment, some or all of the interference detection/classification module <b>402</b>, performance assurance module <b>404</b> and interference mitigation module <b>406</b> are distributed across multiple physical entities in the system. The SSCC <b>720</b> may implement at least a portion of the modules, and may implement some or all of the other components of SC-SON system <b>400</b> including external database <b>410</b>, spectrum policy database <b>412</b>, geolocation module <b>414</b> and RF coverage prediction engine <b>416</b>.
Distributed SON components, referred to here as SC-SON agents <b>716</b> and represented as black circles in <figref idref="DRAWINGS">FIG. 7</figref>, may reside in different network elements such as network manager <b>504</b>, domain manager <b>506</b>, element manager <b>508</b> and base station <b>502</b>. Each of the SC-SON agents may implement a portion of at least one of the interference detection/classification module <b>402</b>, performance assurance module <b>404</b> and interference mitigation module <b>406</b>.
In an embodiment, the SC-SON functionalities implemented in the SSCC <b>720</b> may use global intelligence about the network and attempt to create slower-time-scale parameter adaptation policies that are optimized with respect to global objectives such as maximizing the total capacity of a secondary network <b>350</b> in the presence of interference from a primary network <b>300</b>. Such global optimized adaptation policies may then be pushed down to the SC-SON agents <b>716</b> at the network elements.
Since the optimizations performed by the SSCC <b>720</b> may not have high resolution and may not operate on a fast time-scale, the SSCC need not necessarily have direct low-latency interfaces to network elements such as base stations <b>502</b>. Thus, in an embodiment of a hybrid SC-SON system <b>700</b>, aspects of SC-SON which benefit from rapid reporting and analysis of network data may be located at various network entities that are sources of or are close to sources of the network data, while less time-critical aspects of the SC-SON system may be located at SSCC <b>720</b>. In various embodiments, SSCC <b>720</b> may be incorporated into Network Manager <b>504</b>, or be a separate physical entity as shown in <figref idref="DRAWINGS">FIG. 7</figref>.
In an embodiment, the portions of the interference detection/classification module <b>402</b>, performance assurance module <b>404</b> and interference mitigation module <b>406</b> located at SON agents <b>716</b> may use local information and optimize local parameters with regards to the local environment and the policy pushed down by the SSCC <b>720</b>. Some portion of SC-SON agents <b>716</b> may have direct, possibly standardized, low-latency connections to the network elements such as base stations <b>502</b>. In some networks, base stations <b>502</b> may also have direct low-latency connections to each other, such as the X2 interface shown in the LTE network of <figref idref="DRAWINGS">FIG. 7</figref>. Such low-latency interfaces facilitate the availability and access of real-time information at SC-SON agents <b>716</b>, enabling SC-SON agents <b>716</b> to implement high-resolution optimization of network element parameters on a faster time-scale.
A hybrid system <b>700</b> reduces the complexity of optimizations by distributing the optimization process across the network. Distribution of the optimization process also reduces the information that needs to be exchanged across the network even for fast time-scale optimizations, since all the local information need not be sent to the SSCC <b>720</b>.
<figref idref="DRAWINGS">FIG. 8</figref> illustrates an embodiment of a spectrum coexistence process <b>800</b>. Elements of spectrum coexistence process will be explained with reference to an embodiment in which the primary network <b>300</b> is a broadcast television network, and the secondary network <b>350</b> is a LTE telecommunications network.
An SC-SON system determines interference at S<b>802</b>. In an embodiment, determining interference S<b>802</b> includes determining interference from the primary network <b>300</b> to the secondary network <b>350</b>. For example, the SC-SON system may search a database of users of a portion of spectrum that is the same as or near to a portion of spectrum used by a communications network coupled to the SC-SON system.
In more detail, the SC-SON system may search a database of registered spectrum users to determine which portions of spectrum are being used by primary networks <b>300</b> in various regions. For example, the SC-SON system may determine which channels are being broadcast in a given area, so that elements of the secondary network <b>350</b> in the given area can use portions of spectrum that do not interfere with the known broadcasts.
Interferers may be identified by determining frequencies and locations of RF signals from the primary network <b>300</b> that are sufficient to interfere with the secondary network <b>350</b>. For example, signal strength is greatest at the location of the transmitter, and diminishes with distance. Therefore, determining interference may include determining signal levels from the primary network at various geographic locations that are used by the secondary network <b>350</b>. In particular, the SC-SON may identify signal levels that are sufficient to cause interference to elements of the secondary network <b>35</b> at particular locations. Because signal strength varies according to location, the SC-SON system <b>400</b> may apply different levels of interference mitigation at different locations of the secondary network <b>350</b>.
In an embodiment, determining interference S<b>802</b> includes measuring signals at an element of the secondary network <b>350</b>. For example, a base station <b>502</b> may measure signals that are received at particular frequencies during times at which no transmissions are scheduled for the secondary network <b>350</b>. If no silent times of sufficient length are available in a transmission schedule, the SC-SON system may deliberately schedule silent times for the interference measurements as described in U.S. application Ser. No. 13/902,746. When interference is measured by the secondary network <b>350</b>, it may be classified according to various signal characteristics, such as a portion of spectrum, a signal strength value at a particular location, and patterns with respect to time and frequency. The signal characteristics may be matched to a known source of interference based on similarities in the patterns, and classified signal characteristics may be stored in interference database <b>410</b>.
Transmission parameters for the secondary network <b>350</b> are determined at S<b>804</b>. Determining transmission parameters may include applying a spectrum policy from spectrum policy database <b>412</b>. For example, a transmission policy may be for the secondary network <b>350</b> to cause no interference to the primary network <b>300</b>, in which case transmission parameters are determined to ensure that the secondary network does not transmit at frequencies and times that would interscafere with the primary network. In another embodiment, the transmission policy may include QoS parameters for one or both of the primary network <b>300</b> and the secondary network <b>350</b>. In the example of the television network, transmission parameters may be determined so that users can receive television broadcast signals free of interference from the secondary telecommunications network.
After transmission parameters are determined at S<b>804</b>, signals are transmitted by the secondary network <b>350</b> according to the transmission parameters at S<b>806</b>. The transmission parameters may be parameters for a network element of the secondary network, such as a base station or user equipment.
In an embodiment, process <b>800</b> is performed by central SC-SON system <b>600</b> illustrated in <figref idref="DRAWINGS">FIG. 6</figref>. In such an embodiment, determining interference S<b>802</b> and determining transmission parameters S<b>804</b> are performed by SSCC <b>610</b> at a central location of the secondary network <b>350</b>. In an embodiment with a SC-SON system <b>600</b>, signals may be measured by base stations <b>502</b> and transmitted to SSCC <b>610</b> for classification. Data such as measured signals and transmission parameters may be communicated between SSCC <b>610</b> and other network elements by low latency connections, such as a connection with a latency of one second or less.
In another embodiment, process <b>800</b> is performed by hybrid SC-SON system <b>700</b> illustrated in <figref idref="DRAWINGS">FIG. 7</figref>. In such an embodiment, aspects of process <b>800</b> are performed by SSCC <b>720</b> at a central location, while other aspects of process <b>800</b> are performed by SON agents <b>716</b> distributed through the secondary network <b>350</b>. For example, transmission parameters may be determined by SON agents <b>716</b> at base stations <b>502</b> or element managers <b>508</b> based on a spectrum policy parameters from a spectrum policy database in SSCC <b>720</b>. Thus, processes that benefit from low latency to transmitters and receivers may be distributed through the network, while processes that are less sensitive to delay may be performed at a central network location.
Contents5
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US12185115B2 | Cited by | United States of America | Applicant |
| US12127021B2 | Cited by | United States of America | Applicant |
| US11893893B1 | Cited by | United States of America | Applicant |
| US12192775B2 | Cited by | United States of America | Applicant |
| US12052577B1 | Cited by | United States of America | Applicant |
| US12120528B2 | Cited by | United States of America | Applicant |
| US12114170B2 | Cited by | United States of America | Applicant |
| US11956025B2 | Cited by | United States of America | Applicant |
| US12207097B2 | Cited by | United States of America | Applicant |
| US11930371B2 | Cited by | United States of America | Applicant |
| US12133084B2 | Cited by | United States of America | Applicant |
| US11997502B2 | Cited by | United States of America | Applicant |
| US11948446B1 | Cited by | United States of America | Applicant |
| US12096228B2 | Cited by | United States of America | Applicant |
| US12160763B2 | Cited by | United States of America | Applicant |
| US12137350B2 | Cited by | United States of America | Applicant |
| US12149946B2 | Cited by | United States of America | Applicant |
| US12167245B2 | Cited by | United States of America | Applicant |
| US12191925B2 | Cited by | United States of America | Applicant |
| US12225386B2 | Cited by | United States of America | Applicant |
| US10194438B2 | Cited by | United States of America | Applicant |
| US11838764B2 | Cited by | United States of America | Applicant |
| US12177679B2 | Cited by | United States of America | Applicant |
| US12096231B2 | Cited by | United States of America | Applicant |
| US11937092B2 | Cited by | United States of America | Applicant |
| US11869330B2 | Cited by | United States of America | Applicant |
| US2016360419A1 | Cited by | United States of America | Search report |
| US12028719B2 | Cited by | United States of America | Applicant |
| US12205477B2 | Cited by | United States of America | Applicant |
| US12101639B2 | Cited by | United States of America | Applicant |
| US12177682B2 | Cited by | United States of America | Applicant |
| US12167246B2 | Cited by | United States of America | Applicant |
| US12177680B2 | Cited by | United States of America | Applicant |
| US11924648B1 | Cited by | United States of America | Applicant |
| US11968539B2 | Cited by | United States of America | Applicant |
| US12192776B2 | Cited by | United States of America | Applicant |
| US11963013B1 | Cited by | United States of America | Applicant |
| US11943737B2 | Cited by | United States of America | Applicant |
| US12096227B2 | Cited by | United States of America | Applicant |
| US11991547B2 | Cited by | United States of America | Applicant |
| US12177701B2 | Cited by | United States of America | Applicant |
| US12022297B2 | Cited by | United States of America | Applicant |
| US12207119B1 | Cited by | United States of America | Applicant |
| US12052578B1 | Cited by | United States of America | Applicant |
| US12119966B2 | Cited by | United States of America | Applicant |
| US12167247B2 | Cited by | United States of America | Applicant |
| US11860209B2 | Cited by | United States of America | Applicant |
| US12035143B1 | Cited by | United States of America | Applicant |
| US12160751B1 | Cited by | United States of America | Applicant |
| US12127008B2 | Cited by | United States of America | Applicant |
| US12219365B2 | Cited by | United States of America | Applicant |
| US11974135B2 | Cited by | United States of America | Applicant |
| US12087147B2 | Cited by | United States of America | Applicant |
| US12198527B2 | Cited by | United States of America | Applicant |
| US11843953B1 | Cited by | United States of America | Applicant |
| US12096229B2 | Cited by | United States of America | Applicant |
| US12096232B2 | Cited by | United States of America | Applicant |
| WO2022269689A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11985509B2 | Cited by | United States of America | Applicant |
| US12096230B2 | Cited by | United States of America | Applicant |
| US12108258B2 | Cited by | United States of America | Applicant |
| US12101640B2 | Cited by | United States of America | Applicant |
| US12127007B2 | Cited by | United States of America | Applicant |
| US12052576B2 | Cited by | United States of America | Applicant |
| US12120529B1 | Cited by | United States of America | Applicant |
| US12133083B2 | Cited by | United States of America | Applicant |
| US12015928B2 | Cited by | United States of America | Applicant |
| US12075259B2 | Cited by | United States of America | Applicant |
| US12212973B2 | Cited by | United States of America | Applicant |
| US12108257B2 | Cited by | United States of America | Applicant |
| US11871103B2 | Cited by | United States of America | Applicant |
| US12063517B2 | Cited by | United States of America | Applicant |
| US9686360B2 | Cited by | United States of America | Search report |
| US11943627B2 | Cited by | United States of America | Applicant |
| US12047783B1 | Cited by | United States of America | Applicant |
| US11901963B1 | Cited by | United States of America | Applicant |
| US2018323579A1 | Cited by | United States of America | Search report |
| US10536858B2 | Cited by | United States of America | Search report |
| US12015927B2 | Cited by | United States of America | Applicant |
| US12185114B2 | Cited by | United States of America | Applicant |
| US12142127B1 | Cited by | United States of America | Applicant |
| US11985510B1 | Cited by | United States of America | Applicant |
| US11838780B2 | Cited by | United States of America | Applicant |
| US12137349B2 | Cited by | United States of America | Applicant |
| US11965922B2 | Cited by | United States of America | Applicant |
| US12177678B2 | Cited by | United States of America | Applicant |
| US12126392B2 | Cited by | United States of America | Applicant |
| US12212974B2 | Cited by | United States of America | Applicant |
| US11985013B2 | Cited by | United States of America | Applicant |
| US12143162B2 | Cited by | United States of America | Applicant |
| US12185143B2 | Cited by | United States of America | Applicant |
| US12160762B2 | Cited by | United States of America | Applicant |
| US12058529B2 | Cited by | United States of America | Applicant |
| US12114171B2 | Cited by | United States of America | Applicant |
| US12052575B2 | Cited by | United States of America | Applicant |
| EP3413596A1 | Cited by | European Patent Office (EPO) | Search report |
| US12200500B2 | Cited by | United States of America | Applicant |
| US12207118B1 | Cited by | United States of America | Applicant |
| US12156037B2 | Cited by | United States of America | Applicant |
| US12224888B2 | Cited by | United States of America | Applicant |
2 members in 2 offices
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 201461979680 | United States of America | P | |
| 201461979680 | United States of America | P | |
| 201514687872 | United States of America | A | |
| 61979680 | – | – | – |
| US201461979680P | – | – | – |
| US201514687872 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2015296386A1 | United States of America | A1 | |
| WO2015161005A1 | World Intellectual Property Organization (WIPO) | A1 |
53 transactions on the USPTO file
Abandoned after 2 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Mail Abandonment for Failure to Respond to Office ActionAbandonedMABN2 | MABN2 | |
| Aband. for Failure to Respond to O. A.AbandonedABN2 | ABN2 | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Applicant Initiated Interview SummaryMEXIA | MEXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Applicant Has Filed a Verified Statement of Small Entity Status in Compliance with 37 CFR 1.27SMAL | SMAL | |
| Cleared by L&R (LARS)L128 | L128 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
2 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTIONSTCB | STCB | |
| AssignmentAS | AS |
Numbers
- Publication
- 20150296386
- Publication, DOCDB
- 2015296386
- Publication, EPODOC
- US2015296386
- Application
- 14687872
- Application, DOCDB
- 201514687872
- Application, EPODOC
- US201514687872
Titles
- English
- SYSTEM AND METHOD FOR SPECTRUM SHARING
Classification
- CPC, 6
- H04W16/14
- H04W16/10
- H04W4/021
- H04J11/005
- H04W24/08
- H04W16/18
- IPC, 6
- H04W16 14
- H04W16 18
- H04W24 08
- H04W4 02
- H04J11 00
- H04W4 021
- USPC, 2
- 370241100
- 370329000