Patent Grant
11903049
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The present disclosure relates generally to the field of wireless devices and networks thereof, and specifically in one exemplary aspect to identification of one or more cells within one or more RANs (Radio Area Networks) of a radio network utilizing licensed and/or unlicensed spectrum.
A multitude of wireless networking technologies, also known as Radio Access Technologies (“RATs”), provide the underlying means of connection for radio-based communication networks to user devices. Such RATs often utilize licensed radio frequency spectrum (i.e., that allocated by the FCC per the Table of Frequency Allocations as codified at Section 2.106 of the Commission's Rules). Currently only frequency bands between 9 kHz and 275 GHz have been allocated (i.e., designated for use by one or more terrestrial or space radio communication services or the radio astronomy service under specified conditions). For example, a typical cellular service provider might utilize spectrum for so-called “3G” (third generation) and “4G” (fourth generation) wireless communications as shown in Table 1 below:
Alternatively, unlicensed spectrum may be utilized, such as that within the so-called ISM-bands. The ISM bands are defined by the ITU Radio Regulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of the Radio Regulations. In the United States, uses of the ISM bands are governed by Part 18 of the Federal Communications Commission (FCC) rules, while Part 15 contains the rules for unlicensed communication devices, even those that share ISM frequencies. Table 2 below shows typical ISM frequency allocations:
ISM bands are also been shared with (non-ISM) license-free communications applications such as wireless sensor networks in the 915 MHz and 2.450 GHz bands, as well as wireless LANs (e.g., Wi-Fi) and cordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.
Additionally, the 5 GHz band has been allocated for use by, e.g., WLAN equipment, as shown in Table 3:
User client devices (e.g., smartphone, tablet, phablet, laptop, smartwatch, or other wireless-enabled devices, mobile or otherwise) generally support multiple RATs that enable the devices to connect to one another, or to networks (e.g., the Internet, intranets, or extranets), often including RATs associated with both licensed and unlicensed spectrum. In particular, wireless access to other networks by client devices is made possible by wireless technologies that utilize networked hardware, such as a wireless access point (“WAP” or “AP”), small cells, femtocells, or cellular towers, serviced by a backend or backhaul portion of service provider network (e.g., a cable network). A user may generally access the network at a node or “hotspot,” a physical location at which the user may obtain access by connecting to modems, routers, APs, etc. that are within wireless range.
5G New Radio (NR) and NG-RAN (Next Generation Radio Area Network)
NG-RAN or “NextGen RAN (Radio Area Network)” is part of the 3GPP “5G” next generation radio system. 3GPP is currently specifying Release 15 NG-RAN, its components, and interactions among the involved nodes including so-called “gNBs” (next generation Node B's or eNBs). NG-RAN will provide high-bandwidth, low-latency wireless communication and efficiently utilize, depending on application, both licensed and unlicensed spectrum of the type described supra in a wide variety of deployment scenarios, including indoor “spot” use, urban “macro” (large cell) coverage, rural coverage, use in vehicles, and “smart” grids and structures. NG-RAN will also integrate with 4G/4.5G systems and infrastructure, and moreover new LTE entities are used (e.g., an “evolved” LTE eNB or “eLTE eNB” which supports connectivity to both the EPC (Evolved Packet Core) and the NR “NGC” (Next Generation Core).
The NG-RAN (5G) System architecture is designed to support data connectivity and services offering with higher throughput and lower latency.
An existing 3GPP LTE/LTE-A/EPC (i.e., 4G or 4.5G system) cannot be updated to support 5G; hence, 3GPP has also defined interworking procedures between such 4G/4.5G and 5G systems.
In LTE and 5G NR, for a given cell, the cognizant eNB/gNB broadcasts a Physical Cell ID (PCI). The Physical Cell ID is the identification of a cell at the physical layer (PHY). Under LTE (pre Release 15), up to 504 unique PCIs can be specified. 5G NR (Release 15 and beyond) presently allows up to 1008 unique PCIs.
However, a given PLMN (e.g., HPLMN or VPLMN, such as those described above with respect to
Typically, the UE 222 performs Measurement Reporting, under network directive, based on detected PCIs for a given EARFCN (E-UTRA Absolute Radio Frequency Channel Number) or frequency/set of frequencies. There may exist scenarios where in a given geographic area, two or more PLMNs broadcast the same PCI as seen by a UE. This situation leads to what is referred to as “PCI Confusion;” i.e., an ambiguity as to which PLMN a given PCI detected by a UE belongs.
Automatic Neighbor cell Relations (ANR) (see e.g., 3GPP TS 36.300) was developed to solve the foregoing issue. In ANR, an eNB/gNB—upon receiving Measurement Reports containing the PCI from the UE—instructs the RRC_CONNECTED mode UE to read all broadcast ECGI(s)/NCGI(s), TAC(s), RANAC(s), PLMN ID(s) and LTE/NR frequency band(s) of the cell identified via the reported PCI. Using this information, the eNB/gNB formulates a neighbor cell relationship, and can use this information to update the “whitelist” or “blacklist” and forward to the UE 222. Using this updated information, the UE can adjust its future Measurement Reports. This update information can also be used across PLMN operators to coordinate PCIs of cells, so that the aforementioned ambiguity or confusion is avoided (i.e., two PLMNs with common coverage where a UE might be located will not utilize the same PCI).
3GPP TS 23.501 and TS 23.502 also support a mode known as MICO (Mobile Initiated Connection Only) which allows the network to control Registration Areas, Paging and other related features for certain devices which are expected to operate only in MO-only mode. However, MICO mode was designed for UEs which mostly have UL-heavy transmissions; e.g., IoT sensors. Although such devices could be limited in terms of mobility, it is not a strict requirement, and there is no mechanism determination of mobility (or lack thereof).
The Unlicensed Problem
As of the date of this disclosure, design of NR for Unlicensed spectrum (NR-U) is underway in 3GPP for Releases 15 and 16. NR-U is being defined for three (3) use-cases: (i) Carrier Aggregation (CA), (ii) Dual Connectivity (DC), and (iii) Standalone (SA). (Licensed) NR's design is used as the baseline for NR-U and as such, every NR-U cell will broadcast a PCI, as well as every licensed cell. Unlike licensed spectrum where a single operator owns a frequency range, unlicensed spectrum is open to all for use.
Accordingly, as shown in
Moreover, the foregoing issue is exacerbated due to the NR-U requirements to: a) perform LBT (Listen Before Talk) protocols to gain access to physical medium for transmission; see, e.g., 3GPP TS 38.889 (or TS 37.213 for LTE-LAA), and/or b) account for transmission failures, and implement resulting exponential back-off mechanisms.
Based on the foregoing, no viable mechanism for cell identifier/identity management within unlicensed environments (including for instance the 5G NR-U environment) currently exists.
The present disclosure addresses the foregoing needs by providing, inter alia, methods and apparatus for providing optimized identification of cells, such as for example those supported by a 5G NR-U enabled gNB or its broader PLMN.
In a first aspect of the disclosure, a method for cell identification within a wireless network is described. In one embodiment, the method includes: identifying a set of candidate user devices (e.g., UE(s)) for which to apply the cell identifier resolution mechanism; instructing the identified set of user devices to perform a measurement protocol; and based on the results of the measurement protocol, configure at least one listing of cell identifiers.
In another embodiment, the method includes using at least one gNB to identify a set of candidate UE(s) for which to apply PCI confusion resolution mechanism; instructing, via the at least one gNB, the identified set of UEs to perform Measurement Reports taking LBT into account; and using Measurement Reports provided by UE to update the white/black lists to include/exclude unrelated PCIs.
In an additional aspect of the disclosure, computer readable apparatus is described. In one embodiment, the apparatus includes a storage medium configured to store one or more computer programs, and includes a program memory or HDD or SSD on a computerized device such as a CU of a 5G NR gNB. In one variant, the one or more computer programs are configured to evaluate whether a conflict between two PLMNs (e.g., a 5G NR licensed PLMN and a 5G NR-U unlicensed PLMN) exists, and invoke one or more resolution mechanisms as required.
In a further aspect, a wireless access node is disclosed. In one embodiment, the node comprises a computer program operative to execute on a digital processor apparatus, and configured to, when executed, obtain data from a control or network entity with which the node is associated, and based on the data, cause selective implementation of conflict resolution protocols within the population of user devices served by the access node.
In another embodiment, the node comprises a 3GPP-compliant gNB or eNB.
In another aspect of the disclosure, a method for identifying a subset of user devices (e.g., UEs) is disclosed. In one embodiment, the method includes inserting parametric data relating to a use scenario or context into a protocol message delivered to a base station or RAN (e.g., 5G gNB). The parametric data is extracted by the gNB and used to determine whether subsequent operations, such as Measurement Reporting, should be performed for each UE based thereon.
In another embodiment, a UE provides data (e.g., a “noMobilityRequired” parameter or field) to indicate that no mobility is required, via the UE-NR-Capability IE which is included in UECapabilityInformation message (the latter sent in response to UECapabilityInquiry message). Upon reception of the provided data, the cognizant gNB can determine whether the UE can support the PCI conflict resolution mechanism or not and hence when combined information received e.g., from the AMF (e.g., over N2-AP INITIAL CONTEXT SETUP REQUEST), the gNB can accurately decide whether or not and how to apply PCI conflict resolution mechanism for the UE.
In another aspect of the disclosure, a mobile computerized device is disclosed. In one embodiment, the device includes a 3GPP-compliant UE (user equipment) which is configured.
In an additional aspect of the disclosure, computer readable apparatus is described. In one embodiment, the apparatus includes a storage medium configured to store one or more computer programs, and includes a program memory or HDD or SSD on a computerized device such as a 5G NR gNB or AMF.
In yet another aspect, a system is disclosed. In one embodiment, the system includes (i) an HSS+UDM entity with NMR database, and (ii) one or more PCRE-enabled RAN or AMF entities which cooperate with the HSS+UDM entity to enable PCI conflict resolution in, inter alia, unlicensed 5G spectrum usage scenarios.
In another aspect of the disclosure, a method for limiting a scope of a PCI search is disclosed. In one embodiment, the method includes determining a number to which to limit the search by one or more UE(s), and transmitting an IE from a base station (e.g., gNB) to the one or more UE(s) to restrict the subsequent search and reporting by the UE to the specified number.
In a further aspect, a method of conducting Physical Cell ID (PCI) conflict resolution is disclosed. In one embodiment, the method includes obtaining one or more Public Land Mobile Network ID (PLMN ID) values via a PLMN-ID value within a measurement results reporting information element (IE).
These and other aspects shall become apparent when considered in light of the disclosure provided herein.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
As used herein, the term “application” (or “app”) refers generally and without limitation to a unit of executable software that implements a certain functionality or theme. The themes of applications vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment; for example, the unit could include a downloadable Java Xlet™ that runs within the JavaTV™ environment.
As used herein, the term “central unit” or “CU” refers without limitation to a centralized logical node within a wireless network infrastructure. For example, a CU might be embodied as a 5G/NR gNB Central Unit (gNB-CU), which is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs, and which terminates the F1 interface connected with one or more DUs (e.g., gNB-DUs) defined below.
As used herein, the terms “client device” or “user device” or “UE” include, but are not limited to, set-top boxes (e.g., DSTBs), gateways, modems, personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones, and vehicle infotainment systems or portions thereof.
As used herein, the term “computer program” or “software” is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML, VoXML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), Java™ (including J2ME, Java Beans, etc.) and the like.
As used herein, the term “distributed unit” or “DU” refers without limitation to a distributed logical node within a wireless network infrastructure. For example, a DU might be embodied as a 5G/NR gNB Distributed Unit (gNB-DU), which is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU (referenced above). One gNB-DU supports one or multiple cells, yet a given cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0 and 3.1.
As used herein, the term “headend” or “backend” refers generally to a networked system controlled by an operator (e.g., an MSO) that distributes programming to MSO clientele using client devices, or provides other services such as high-speed data delivery and backhaul.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet. Other common examples include but are not limited to: a network of external servers, “cloud” entities (such as memory or storage not local to a device, storage generally accessible at any time via a network connection, and the like), service nodes, access points, controller devices, client devices, etc.
As used herein, the term “LTE” refers to, without limitation and as applicable, any of the variants or Releases of the Long-Term Evolution wireless communication standard, including LTE-U (Long Term Evolution in unlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed Assisted Access), LTE-A (LTE Advanced), 4G LTE, WiMAX, VoLTE (Voice over LTE), and other wireless data standards.
As used herein, the term “memory” includes any type of integrated circuit or other storage device adapted for storing digital data including, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3D memory, and PSRAM.
As used herein, the terms “microprocessor” and “processor” or “digital processor” are meant generally to include all types of digital processing devices including, without limitation, digital signal processors (DSPs), reduced instruction set computers (RISC), general-purpose (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components.
As used herein, the terms “MSO” or “multiple systems operator” refer to a cable, satellite, or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the terms “MNO” or “mobile network operator” refer to a cellular, satellite phone, WMAN (e.g., 802.16), or other network service provider having infrastructure required to deliver services including without limitation voice and data over those mediums. The term “MNO” as used herein is further intended to include MVNOs, MNVAs, and MVNEs.
As used herein, the terms “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications technologies or networking protocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5GNR, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).
As used herein the terms “5G” and “New Radio (NR)” refer without limitation to apparatus, methods or systems compliant with 3GPP Release 15, and any modifications, subsequent Releases, or amendments or supplements thereto which are directed to New Radio technology, whether licensed or unlicensed.
As used herein, the term “QAM” refers to modulation schemes used for sending signals over e.g., cable or other networks. Such modulation scheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.) depending on details of a network. A QAM may also refer to a physical channel modulated according to the schemes.
As used herein, the term “server” refers to any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer network.
As used herein, the term “storage” refers to without limitation computer hard drives, DVR device, memory, RAID devices or arrays, optical media (e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices or media capable of storing content or other information.
As used herein, the term “Wi-Fi” refers to, without limitation and as applicable, any of the variants of IEEE Std. 802.11 or related standards including 802.11 a/b/g/n/s/v/ac/ax, 802.11-2012/2013 or 802.11-2016, as well as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer (P2P) Specification”, incorporated herein by reference in its entirety).
Overview
In one exemplary aspect, the present disclosure provides methods and apparatus for, inter alia, effectively resolving conflicts in PCI values which may exist within two or more mobile networks (e.g., PLMNs) of respective different operators when unlicensed spectrum is utilized.
In one implementation, this functionality is provided by specifying one or more mobility-related parameters associated with various UE, such that serving gNBs can determine whether a given UE requires a mobility context, and as such whether it should conduct subsequent RF measurement reporting to report back potential conflicts in PCI it may encounter to the gNB. In one variant, the measurement reporting is configured to comply with 5G NR-U required “listen-before-talk” or LBT protocols; i.e., to measure parameters consistent with the LBT protocols as part of the detection of any such PCI-based conflicts.
In another variant, a maximum number of PLMNs common to a given PCI is specified, such that instructed UE(s) will limit themselves to measurement reporting on that number of detected PLMNs.
Enhanced PCI confusion resolution capability as described herein advantageously allows for UE to utilize unlicensed spectrum (e.g., under the NR-U model) without complicated network communication and configuration requirements between two or more operating networks as typically found in licensed spectrum scenarios.
Moreover, the various aspects of the present disclosure can be implemented within the existing base of UE with no modification; i.e., each UE merely uses existing RF measurement reporting functions to provide the necessary data back to the serving gNB for PCI conflict resolution.
Similarly, only minor modifications to extant network-side architectures (e.g., 3GPP) are needed to support this enhanced functionality.
Detailed Description of Exemplary Embodiments
Exemplary embodiments of the apparatus and methods of the present disclosure are now described in detail. While these exemplary embodiments are described in the context of the previously mentioned wireless access networks (e.g., 5GS and ECS) associated with or supported at least in part by a managed network of a service provider (e.g., MSO and/or MNO networks), other types of radio access technologies (“RATs”), other types of networks and architectures that are configured to deliver digital data (e.g., text, images, games, software applications, video and/or audio) may be used consistent with the present disclosure. Such other networks or architectures may be broadband, narrowband, or otherwise, the following therefore being merely exemplary in nature.
It will also be appreciated that while described generally in the context of a network providing unlicensed spectrum service to a customer or consumer or end user or subscriber (i.e., within a prescribed service area, venue, or other type of premises), the present disclosure may be readily adapted to other types of environments including, e.g., outdoors, commercial/retail, or enterprise domain (e.g., businesses), or even governmental uses (including e.g., quasi-licensed spectrum such as CBRS). Yet other applications are possible.
Other features and advantages of the present disclosure will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below.
Methods
Referring now to
Next, per step 304, the cognizant gNB instructs the identified set of UEs from step 302 to perform Measurement Reports. As discussed below, in one implementation, the Measurement Reports are conducted taking the LBT (Listen Before Talk) protocol into account.
Lastly, per step 306, the gNB uses data from the Measurement Reports provided by the UE(s) to update the current white and/or black lists to include/exclude unrelated or improper PCI values.
Referring now to
In one approach, the presence or absence of this NMR or similar parameter is conducted when such UE(s)/users perform registration with the 5GC (see 3GPP TS 23.501, and 23.502); i.e., the “No Mobility Required” value is present in the N2-AP INITIAL CONTEXT SETUP REQUEST (which carries Registration Accept per TS 23.502 Section 4.2.2.2.2, step 21); see also TS 38.413 Section 8.3.1.2, step 2, each of the foregoing incorporated herein by reference in its entirety. Specifically, the AMF (Access and Mobility Management Function) may initiate the Initial Context Setup procedure if (i) a UE-associated logical NG-connection exists for the UE, or (ii) if the AMF has received the RAN UE NGAP ID IE in an INITIAL UE MESSAGE message, or (iii) if the NG-RAN node has already initiated a UE-associated logical NG-connection by sending an INITIAL UE MESSAGE message via another NG interface instance. The procedure uses UE-associated signalling.
Hence, per step 312 of the method of
To support the presence or absence of this NMR parameter within the above registration process, in one variant, each UE is characterized at time of generation of the UE(s) and/or users' subscription profile within the UDM (Unified Data Management) process or entity, the profile denoting “No Mobility Required” for that UE/user. For instance, an end-user may be utilizing a fixed 5G-enabled wireless device such as a smart TV, DSTB, gateway, router, IoT-enabled device, etc. which has no mobility capability.
As a brief aside, it will be recognized that as used herein, the term “mobility” refers more to intra-cell mobility, versus inter-cell mobility. Specially, any device is mobile to some degree; i.e., one can set up their smart TV or IoT device within their premises, and then later move it to another location within the same premises. However, under such scenarios, from a PCI perspective, the device is immobile. Notwithstanding, the present disclosure also contemplates use of two or more “grades” or levels of mobility characterization in one alternate embodiment; e.g., (i) No Mobility Required, (ii) Limited Mobility Required, and (iii) Full Mobility Required. Under such model, the gNB can apply different protocols to the different levels of mobility support needed; e.g., the method 300 above for NMR, another for LMR (e.g., a hybridization of the method of
It will also be appreciated that while the foregoing approach of accessing the UDM (e.g., via the AMF) as part of the Attach procedure (and generating the INITIAL CONTEXT SETUP REQUEST sent to the gNB with mobility-related data) is used to determine UE mobility status for purposes of PCI management, other approaches may be used consistent with the present disclosure. For example, in another variant, the UE itself supplies the NMR or other parameter, such as via another Attach procedure or setup message.
As yet another variant, the parameter(s) of interest (e.g., NMR) may be provided in RRC signaling between the UE and gNB, including in some cases coupling with a subscription-based solution (the latter which is advantageously reliable and operator-controllable) as described in greater detail below with respect to Appendix II. Referring again to
It will also be recognized that in other variants, the NMR or other mobility-related data may be used as a basis for inclusion as well as exclusion of UEs within the gNB identification logic. For example, if it is desired to identify UE(s) with no mobility requirements, then those carrying the NMR parameter (e.g., via the CONTEXT REQUEST from the AMF as described above) are included, and all else are excluded. Conversely, if it is desired to identify only UE(s) having mobility requirements, those carrying the NMR parameter are excluded, and all else included. It will be recognized that the “negative” of this approach can be used as well consistent with the present disclosure; i.e., all UE(s) not within a FWA or no-mobility context can have for instance an “MR” (Mobility Required) parameter, while all others have no such value. Likewise, in another variant, those UE(s) requiring mobility may carry the MR parameter, while those under FWA carry the NMR parameter. Since the number of FWA-context devices is expected to be much less than the mobility-required devices, it is more efficient to merely label the FWA-context devices with NMR or the like in such scenarios. In one implementation, UEs not supporting NMR functionality by definition will be considered normal UEs, although it will be recognized that they may also be affirmatively identified or labeled as not supporting parameter (e.g., NMR) functionality.
Referring now to
As a brief aside, unlicensed spectrum coexistence is a key principle in both LAA (LTE) and NR-U (5G). This coexistence is accomplished by dynamically selecting available channels within the unlicensed band to avoid e.g., Wi-Fi users. If no available or clear channel is present, channels are shared “fairly” among the users using the Listen Before Talk (LBT) protocol. As in LTE-LAA and other technologies, the LBT protocol in NR-U is a mechanism by which measurements of a given carrier are obtained, and use or “backoff” determined based on the measurements.
Accordingly, in one implementation, step 324 of
As a brief aside, in 5G NR, the SSB (the Synchronization Signal/PBCH Block) consists of synchronization signal (i.e., PSS and SSS) and PBCH channels. The SSB burst set is re-transmitted every 5 ms, and within every SSB burst set the SSB is transmitted at a certain periodicity. Since SSB is unique to a gNB on a per-cell, per-beam basis, it is safe to assume that when the SSB is transmitted continuously over a physical medium (e.g., an RF frequency), within a 5 ms period, a UE looking for the SSB should be able to read it.
In that NR requires tight time synchronization between the gNB and UE, it is also safe to assume that multiple gNBs both within the same PLMN and across different PLMNs are coordinated to an accurate timing source (e.g., atomic clock). Hence, time deviation among the gNBs of different PLMNs is negligible.
In LTE-LAA, the maximum COT (channel occupancy time) following a successful LBT procedure is 10 ms (see TS 37.213 v15.1.0 clause 4.1.1, incorporated herein by reference in its entirety). One implementation of the methodology described herein, based on the assumption that an NR system uses the same 10 ms value, uses a 15 ms total (5 ms+10 ms) time for the UE to scan for all possible SSBs being broadcast in the same PCI, such as by different PLMNs. As such, the previously discussed ASN.1 additions to the MeasObjectNR IE in such implementations can be configured with values of XX and YY of 5 ms and 15 ms, respectively—that is:
Hence, per step 324 of
Per step 326, the gNB extracts the relevant reporting data for the target PCI values from the Measurement Reports of the “instructed” UE after such Reports have been received (e.g., signal strength data for the prescribed frequencies).
In another implementation (discussed below with respect to
Referring now to
Per step 332, the gNB logic then evaluates the received data for each target PCI to determine whether conflicts are present. Per steps 334 and 336 the gNB can, based on various criteria including the results of the evaluation of step 332, decide to update the current white list and/or black list; i.e., specifying those PCI on which it wishes to subsequently obtain Measurement Reports.
Notably, extant white list/black list approaches only allow for the inclusion of PCI values (i.e., in the PCI-Range IE). The PCI-Range IE is defined in TS 38.331 and is used to encode either a single or a range of physical cell identities. Per TS 38.331, the range is encoded by using a start value and by indicating the number of consecutive physical cell identities (including start) in the range. For fields comprising multiple occurrences of PCI-Range, the Network may configure overlapping ranges of physical cell identities. The “range” field in the PCI-Range IE indicates the number of physical cell identities in the range (including start). For example, the value n4 corresponds with 4, n8 corresponds with 8. The UE applies a value of 1 in the case the field is absent, in which case only the physical cell identity value indicated by the “start” field applies. The “start” field indicates the lowest physical cell identity in the range.
In the particular case of PCI confusion, however, the extant structure is not sufficient. Specifically, what is required is the ability to either enable or disable Measurement Reports from PCI(s) of a specific PLMN. Therefore, the following modified ASN.1 PCI-Range IE is provided per one embodiment of the present disclosure to support such additional specificity:
As referenced above, in another variant, the parameter(s) of interest (e.g., NMR) may be provided in RRC signaling between the UE and gNB, including in some cases coupling with a subscription-based solution (the latter which is advantageously reliable and operator-controllable). For example, in one implementation, the UE provides the parameter(s) (e.g., NMR) within the UE NR-Capability IE, which is included in UECapabilityInformation message (the latter which is sent in response to UECapabilityInquiry message). As such, relevant portions of TS 38.331 may be modified as described below.
Specifically, upon reception of the foregoing data, the cognizant gNB has an understanding of whether a given UE can support the parametric determination (e.g., NMR) or not. Combined with the information received over the N2-AP INITIAL CONTEXT SETUP REQUEST as described elsewhere herein, the gNB can accurately decide whether or not to apply NMR for this UE. In one implementation, within the exemplary UECapability Information IE, the UE-CapabilityRAT-ContainerList is used. The IE UE-CapabilityRAT-ContainerList contains a list of radio access technology specific capability containers. For NR, the IE UE NR-Capability IE is used to convey the NR UE Radio Access Capability Parameters, see TS 38.306. Appendix II hereto illustrates an exemplary implementation of the UE NR-Capability IE including added NMR parameters according to the present disclosure.
In another embodiment of the methodology (see
Specifically, it is recognized by the inventors hereof that there is no reliable mechanism for knowing a priori how many PLMN operators will be operating within a given cell's area at any given point in time. During the initial deployment phase of NR technology, it is expected that the number of PLMN operators will be comparatively small and contained; however, as deployment continues over time, this assumption may no longer hold true. As discussed above, the ability of the gNB to utilize scan time limit(s) which may be applied to the PCI search and reporting is already provided herein. However, it may be the case e.g., that the use of the time-bounded limit may not be sufficient to adequately restrict the measurement reporting conducted by the UE; i.e., if a larger number of PLMNs are present (e.g., more than 5), they may all be within the prescribed scan window, including in some cases being “densely packed” within a smaller portion of the scan window due to e.g., statistical variation, and hence the UE would still be conducting a higher number of scans/reports than desired, even with the scan window limit imposed.
As such, an additional mechanism by which the number of PLMNs corresponding to the PCI (and hence reports corresponding thereto generated by the UE(s)) may be limited is proposed herein; i.e., a “report-bound” in addition to the previously described “time-bound” on the PLMN search. Specifically, in one implementation, an addition to the ASN.1/TS 38.331 MeasObjectNR IE is used as shown below:
maxPLMNsPerPCIToReport INTEGER::=(1..maxNrOfPLMNsPerPCIToReport) OPTIONAL—Maximum number of PLMNs for the same PCI for Measurement reports are to be generated by the UE
In one implementation, the constant maxNrOfPLMNsPerPCIToReport is defined as follows:
maxNrOfPLMNsPerPCIToReport INTEGER::=20
Appendices III and IV hereto illustrate various embodiments of the use of the above value within the ASN.1 MeasObjectNR IE.
Note also that in Appendix IV, the following elements have been added in place of the CellGlobalNR IE of the alternate embodiment:
Note also that in Appendix IV, several new elements have been added, including e.g., the following:
Referring again to
Per step 325, the gNB instructs the relevant UE(s) with the target PCI value(s), duration(s), and also maximum PLMN number selected per step 323.
It will be appreciated that the exemplary specified constant value above (5) may be varied as needed, based on operational or other considerations. This variation may even be dynamic in nature, such as e.g., by logic having insight into the number of active PLMNs as a function of time (which may be correlated for example to status of operational deployment, planned maintenance outages, etc.). The value of the constant may also be related to the above-described scan time value(s), such as where it is desired to use the maxNrOfPLMNsPerPCIToReport parameter to limit the measurement reporting when a longer scan time window is used (i.e., when the window is so long as to effectively provide no limitation).
It will also be appreciated that the scan time parameter(s) and the maximum number of PLMN parameter may be used heterogeneously across different UE being served by a common gNB. For instance, it may be desirable in some cases to have one subset of the UE population implement the scan time parameter(s) alone, while others utilize the combination of scan time and maximum PLMN number parameters. Since RRC parameters are UE-specific, different UEs can be provided different values by the gNB given its knowledge of the topology, statistics, operational considerations, etc. These heterogeneous uses may also be combined with the conjunctive/selective use of the scan time and maximum PLMN numbers described herein to optimize the network on a per-UE/per-gNB basis. For example, even two UE's within the same subset may have differing combinations/constant values, such as in the case where Combination A (scan time parameter=R, maximum PLMN number=S) is applied to a portion of the second subset mentioned above (combination subset), while Combination B (scan time parameter=T, maximum PLMN number=U) is applied to another portion of that same second subset.
Further, as referenced above, the present disclosure contemplates use of individual ones of the parameters (e.g., scan time/maximum number of PLMNs) either individually or in combination, depending on factors such as operational circumstance. It will be appreciated that such different parameters may have respective different benefits/optimizations, thereby making their use non-identical. For instance, one risk or potential detriment of using the scan time parameter alone is that the cognizant gNB may not get an accurate representation of all possible combinations of PLMNs which a given UE is experiencing. This disability can be resolved by, for instance, the gNB performing cell scans itself, or performing ANR, but, neither of these “work arounds” is optimal.
Conversely, one risk or potential detriment in using the maximum PLMN number parameter alone is that as the number of PLMNs for a given PCI increases, the affected UE(s) will spend progressively longer times (and resources) scanning for all possible PLMNs (i.e., until the maximum specified number is reached).
Accordingly, in one exemplary implementation of the disclosure, a conjunction of both parameters may provide an optimal balance of UE power consumption obtaining the most accurate data regarding the UE's environment. It will be recognized, however, that such uses may be selectively invoked or adjusted; for instance, where UE electrical power consumption is low (e.g., where the battery charge is significantly depleted or below a prescribed threshold), this information may be used to “rebalance” the optimization, such as by e.g., reducing the maximin number of PLMNs specified in the constant maxNrOfPLMNsPerPCIToReport.
In yet another embodiment of the disclosure, rather than use of CGI reporting—e.g., cgi-Info IE in MeasResultNR (which may or may not be active based on circumstance; i.e., is optional, and CGI reporting may not be turned on), the PLMN-ID is reported when performing RSRQ/RSRP or other signal strength indicator (SSI) measurements, based on PCI reporting.
Specifically, as shown in the embodiment of Appendix III, the PLMN-ID may be added to MeasResultNR, so that the PLMN-ID can be obtained in cases where CGI reporting is not invoked. Alternatively, it can be obtained from the CGI-nfo IE where utilized.
Network Architecture
As shown, the 5G RAN 424 of the type described subsequently herein in detail is configured to include both a local parameter (e.g., NMR in this example) database 406, and PCRE 404. In this embodiment, the PCRE/NMR database are located within the 5G NR CU (central unit) of the relevant gNBs (not shown), although it will be appreciated that these components may be located in different locations, whether individually or collectively.
Also shown is the global NMR database 402, here logically disposed within the HSS+UDM functionality of the 5GC. The N8 interface as shown enables communication between the UDM process (and hence the global DB 402) and the serving AMF 426 in support of the PCI confusion resolution functions described herein.
In the architecture 440 of
In the architecture 460 of
As discussed with respect to
As such, the placement and configuration of the various PCI conflict resolution processes (i.e., PCREs, NMR databases, etc.) is envisioned to vary accordingly. Advantageously, since standardized 5G NR protocols and interfaces are utilized, communication between the various entities is straightforward (i.e., as opposed to proprietary protocols utilized in each domain).
Service Provider Network
Also provided within the architecture 500 of
The UE may include two radio transceivers (one for 3GPP LTE, and one for 3GPP NR including NR-U), or alternatively a common unified dual-mode transceiver, as well as protocol stacks serving the respective transceivers for functions including support of higher layer processes such as authentication.
Also included in the infrastructure 500 of
Moreover, it will be recognized that while the architecture 500 of
In certain embodiments, the service provider network architecture 500 also advantageously permits the aggregation and/or analysis of subscriber- or account-specific data (including inter alia, particular CU or DU or E-UTRAN eNB/femtocell devices associated with such subscriber or accounts, as well as their mobility or FWA status as previously discussed) as part of the provision of services to users under the exemplary delivery models described herein. As but one example, device-specific IDs (e.g., gNB ID, Global gNB Identifier, NCGI, MAC address or the like) can be cross-correlated to MSO subscriber data maintained at e.g., the network head end(s) 507, or within the HSS+UDM (and associated global NMR database 402) where maintained by the MNO, so as to permit or at least facilitate, among other things, PCI conflict resolution and Measurement Report configuration.
As a brief aside, a number of additional identifiers over and above the PCI discussed supra are used in the NG-RAN architecture, including those of UE's and for other network entities. Specifically:
the AMF Identifier (AMF ID) is used to identify an AMF (Access and Mobility Management Function 426 shown in
the NR Cell Global Identifier (NCGI), is used to identify NR cells globally, and is constructed from the PLMN identity to which the cell belongs, and the NR Cell Identity (NCI) of the cell;
the gNB Identifier (gNB ID) is used to identify gNBs within a PLMN, and is contained within the NCI of its cells;
the Global gNB ID, which is used to identify gNBs globally, and is constructed from the PLMN identity to which the gNB belongs, and the gNB ID;
the Tracking Area identity (TAI), which is used to identify tracking areas, and is constructed from the PLMN identity to which the tracking area belongs, and the TAC (Tracking Area Code) of the Tracking Area; and
the Single Network Slice Selection Assistance information (S-NSSAI), which is used to identify a network slice.
Hence, depending on what data is useful to the MSO or its customers, various portions of the foregoing can be associated and stored to particular gNB “clients” or their components being backhauled by the MSO network.
The MSO network architecture 500 of
The network architecture 500 of
Alternatively, the CU's (which in effect aggregate the traffic from the various constituent DU's towards the NG Core), may have a dedicated high bandwidth “drop.”
Moreover, a given CU and DU may be co-located as desired, as shown by the combined units 504b and 504c, and 506b and 506c in
In the MSO network 500 of
The network architecture 500 of
In one implementation, the CMs 512 shown in
In parallel with (or in place of) the foregoing delivery mechanisms, the MSO backbone 531 and other network components can be used to deliver packetized content to the “client” gNB devices 504, 506 via non-MSO networks. For example, so-called “OTT” content (whether tightly coupled or otherwise) can be ingested, stored within the MSO's network infrastructure, and delivered to the gNB CU 504 via an interposed service provider network (which may include a public Internet) 511 (e.g., at a local coffee shop, via a DU connected to the coffee shop's service provider via a modem, with the user's IP-enabled end-user device utilizing an Internet browser or MSO/third-party app to stream content according to an HTTP-based approach over the MSO backbone 531 to the third party network to the service provider modem (or optical demodulator) to the DU, and to the user device via the DU NR wireless interface.
It will further be recognized that user-plane data/traffic may also be routed and delivered apart from the CU. In one implementation (described above), the CU hosts both the RRC (control-plane) and PDCP (user-plane); however, as but one alternate embodiment, a so-called “dis-aggregated” CU may be utilized, wherein a CU-CP entity (i.e., CU-control plane) hosts only the RRC related functions, and a CU-UP (CU-user plane) which is configured to host only PDCP/SDAP (user-plane) functions. The CU-CP and CU-UP entities can, in one variant, interface data and inter-process communications via an E1 data interface, although other approaches may be used.
In certain embodiments, each DU 506 is located within and/or services one or more areas within one or more venues or residences (e.g., a building, room, or plaza for commercial, corporate, academic purposes, and/or any other space suitable for wireless access). Each DU is configured to provide wireless network coverage within its coverage or connectivity range for its RAT (e.g., 5G NR). For example, a venue may have a wireless NR modem (DU) installed within the entrance thereof for prospective customers to connect to, including those in the parking lot via inter alia, their NR or LTE-enabled vehicles or personal devices of operators thereof. Notably, different classes of DU 506 may be utilized. In practical terms, some devices may have a working range on the order of hundreds of feet, while other devices may operate out to thousands of feet or more, the propagation and working range dictated by a number of factors, including the presence of RF or other interferers, physical topology of the venue/area, energy detection or sensitivity of the receiver, etc. Similarly, different types of NR-enabled DU 506 can be used depending on these factors, whether alone or with other wireless PHYs such as LTE, WLAN, etc.
It will also be appreciated that while described primarily with respect to a unitary gNB-CU entity or device 504 as shown in
For instance, the individual DU's 506 in
Two or more gNBs may also be communicative with one another via e.g., an Xn interface, and accordingly can conduct at least CU to CU data transfer and communication. Separate NG Cores may be used for control and user plane (and other) functions of the network. Alternatively, the separate NG Cores may be logically “cross-connected” to the gNBs of one or more other NG Cores, such that one core can utilize/control the infrastructure of another, and vice versa. This may be in “daisy chain” fashion (i.e., one gNB is communicative one other NG Core other than its own, and that NG Core is communicate with yet one additional gNB other than its own, and so forth), or the gNBs and NG Cores may form a “mesh” topology where multiple Cores are in communication with multiple gNBs or multiple different entities (e.g., service providers). Yet other topologies will be recognized by those of ordinary skill given the present disclosure. This cross-connection approach advantageously allows for, inter alia, sharing of infrastructure between two MNOs/MSOs, which is especially useful in e.g., dense deployment environments which may not be able to support multiple sets of RAN infrastructure.
It is also noted that heterogeneous architectures of eNBs, Home eNBs or femtocells (i.e., E-UTRAN LTE/LTE-A Node B′s or base stations) and gNBs may be utilized consistent with the architectures of
Moreover, the DU/CU architectures set forth in co-owned U.S. patent application Ser. No. 15/945,657 filed Apr. 4, 2018 and entitled “APPARATUS AND METHODS FOR CELL ACTIVATION IN WIRELESS NETWORKS,” and issued on Aug. 2, 2022 as U.S. Pat. No. 11,405,797, incorporated herein by reference in its entirety, may be used consistent with the various aspects of the present disclosure.
HSS+UDM Apparatus
In the exemplary embodiment, the processor 602 of the HSS+UDM 401 may include one or more of a digital signal processor, microprocessor, field-programmable gate array, or plurality of processing components mounted on one or more substrates. The processor 602 may also comprise an internal cache memory, and is in communication with a memory subsystem 604, which can comprise, e.g., SRAM, flash and/or SDRAM components. The memory subsystem may implement one or more of DMA type hardware, so as to facilitate data accesses as is well known in the art. The memory subsystem of the exemplary embodiment contains computer-executable instructions which are executable by the processor 602.
The processing apparatus 602 is configured to execute at least one computer program stored in memory 604 (e.g., a non-transitory computer readable storage medium); in the illustrated embodiment, such programs include HSS+UDM-based NMR DB controller logic 606, such as to serve data from requesting AMF or other entities relating to individual UE or subscriber accounts relating to characterizing data such as NMR data (see discussion of
In some embodiments, the HSS+UDM logic 606 utilizes memory 604 or other storage 605 configured to temporarily hold a number of data relating to the various UE's (including UDM registration data, NMR data, etc.) for the various functions described herein including UE authentication and registration, PCI conflict resolution, etc.).
The HSS+UDM 401 may further be configured to directly or indirectly communicate with one or more authentication, authorization, and accounting (AAA) servers of the network, such as via the interface 608 shown in
In one exemplary embodiment, the HSS+UDM 401 is maintained by the MSO (see
gNB Apparatus
In one exemplary embodiment as shown, the gNB (which may for instance take any of the forms shown in
The 5G RF interface 720 may be configured to comply with the relevant PHY and CU DU functional “splits” (e.g., Options 1 through 8) according to the relevant 3GPP NR standards which it supports. Returning again to
In one embodiment, the processor apparatus 702 may include one or more of a digital signal processor, microprocessor, field-programmable gate array, or plurality of processing components mounted on one or more substrates. The processor apparatus 702 may also comprise an internal cache memory. The processing subsystem is in communication with a program memory module or subsystem 704, where the latter may include memory which may comprise, e.g., SRAM, flash and/or SDRAM components. The memory module 704 may implement one or more of direct memory access (DMA) type hardware, so as to facilitate data accesses as is well known in the art. The memory module of the exemplary embodiment contains one or more computer-executable instructions that are executable by the processor apparatus 702. A mass storage device (e.g., HDD or SSD, or NAND/NOR flash or the like) is also provided as shown.
The processor apparatus 702 is configured to execute at least one computer program stored in memory 704 (e.g., the logic of the PCRE including enhanced functions of PCI conflict resolution and operation according to the methods of
In some embodiments, the PCRE logic 706 also utilizes memory 704 or other storage 705 configured to temporarily and/or locally hold a number of data relating to the various NMR data and associations for the various UE which it services under the NR-U standard(s). In other embodiments, application program interfaces (APIs) may also reside in the internal cache or other memory 704. Such APIs may include common network protocols or programming languages configured to enable communication between the PCRE and other network entities (e.g., via API “calls” to or from the HSS+UDM 401 or AMF 426).
It will be recognized that while certain aspects of the disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the disclosure, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the disclosure disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the disclosure as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the disclosure. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the disclosure. The scope of the disclosure should be determined with reference to the claims.
It will be further appreciated that while certain steps and aspects of the various methods and apparatus described herein may be performed by a human being, the disclosed aspects and individual methods and apparatus are generally computerized/computer-implemented. Computerized apparatus and methods are necessary to fully implement these aspects for any number of reasons including, without limitation, commercial viability, practicality, and even feasibility (i.e., certain steps/processes simply cannot be performed by a human being in any viable fashion).
This application is a continuation of, and claims priority to, co-owned U.S. patent application Ser. No. 16/601,345 of the same title filed on Oct. 14, 2019, and issuing as U.S. Pat. No. 11,129,213 on Sep. 21, 2021, which claims priority to U.S. Provisional Patent Application Ser. Nos. 62/745,065 and 62/752,002 filed Oct. 12, 2018 and Oct. 29, 2018, respectively, each entitled “APPARATUS AND METHODS FOR CELL IDENTIFICATION IN WIRELESS NETWORKS,” each incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3999051 | Petschauer | Dec 1976 | A |
| 4339657 | Larson et al. | Jul 1982 | A |
| 4574364 | Tabata et al. | Mar 1986 | A |
| 4604751 | Aichelmann, Jr. et al. | Aug 1986 | A |
| 4692757 | Tsuhara et al. | Sep 1987 | A |
| 4710761 | Kapur et al. | Dec 1987 | A |
| 4845644 | Anthias et al. | Jul 1989 | A |
| 4890098 | Dawes et al. | Dec 1989 | A |
| 4890257 | Anthias et al. | Dec 1989 | A |
| 5113517 | Beard et al. | May 1992 | A |
| 5121475 | Child et al. | Jun 1992 | A |
| 5129055 | Yamazaki et al. | Jul 1992 | A |
| 5155731 | Yamaguchi | Oct 1992 | A |
| 5175813 | Golding et al. | Dec 1992 | A |
| 5245615 | Treu | Sep 1993 | A |
| 5276437 | Horvath et al. | Jan 1994 | A |
| 5408602 | Giokas et al. | Apr 1995 | A |
| 5463768 | Cuddihy et al. | Oct 1995 | A |
| 5487143 | Southgate | Jan 1996 | A |
| 5502839 | Kolnick | Mar 1996 | A |
| 5522025 | Rosenstein | May 1996 | A |
| 5564002 | Brown | Oct 1996 | A |
| 5581686 | Koppolu et al. | Dec 1996 | A |
| 5596702 | Stucka et al. | Jan 1997 | A |
| 5621879 | Kohda | Apr 1997 | A |
| 5664046 | Abecassis | Sep 1997 | A |
| 5673403 | Brown et al. | Sep 1997 | A |
| 5675755 | Trueblood | Oct 1997 | A |
| 5692142 | Craycroft et al. | Nov 1997 | A |
| 5734380 | Adams et al. | Mar 1998 | A |
| 5742583 | Scott | Apr 1998 | A |
| 5764230 | Baradel et al. | Jun 1998 | A |
| 5790779 | Ben-Natan et al. | Aug 1998 | A |
| 5831609 | London et al. | Nov 1998 | A |
| 5850544 | Parvathaneny et al. | Dec 1998 | A |
| 5856826 | Craycroft | Jan 1999 | A |
| 5862316 | Hagersten et al. | Jan 1999 | A |
| 5867160 | Kraft, IV et al. | Feb 1999 | A |
| 5874960 | Mairs et al. | Feb 1999 | A |
| 5877755 | Hellhake | Mar 1999 | A |
| 5895472 | Brodsky et al. | Apr 1999 | A |
| 5973702 | Orton et al. | Oct 1999 | A |
| 5995103 | Ashe | Nov 1999 | A |
| 6031530 | Trueblood | Feb 2000 | A |
| 6092107 | Eleftheriadis et al. | Jul 2000 | A |
| 6160872 | Karnowski et al. | Dec 2000 | A |
| 6169725 | Gibbs et al. | Jan 2001 | B1 |
| 6181713 | Patki et al. | Jan 2001 | B1 |
| 6192403 | Jong et al. | Feb 2001 | B1 |
| 6216152 | Wong et al. | Apr 2001 | B1 |
| 6219044 | Ansberry et al. | Apr 2001 | B1 |
| 6233611 | Ludtke et al. | May 2001 | B1 |
| 6240555 | Shoff et al. | May 2001 | B1 |
| 6252889 | Patki et al. | Jun 2001 | B1 |
| 6313880 | Smyers et al. | Nov 2001 | B1 |
| 6317881 | Shah-Nazaroff et al. | Nov 2001 | B1 |
| 6330010 | Nason et al. | Dec 2001 | B1 |
| 6336122 | Lee et al. | Jan 2002 | B1 |
| 6337717 | Nason et al. | Jan 2002 | B1 |
| 6366876 | Looney | Apr 2002 | B1 |
| 6381710 | Kim | Apr 2002 | B1 |
| 6381735 | Hunt | Apr 2002 | B1 |
| 6397262 | Hayden et al. | May 2002 | B1 |
| 6430570 | Judge et al. | Aug 2002 | B1 |
| 6456892 | Dara-Abrams et al. | Sep 2002 | B1 |
| 6460141 | Olden | Oct 2002 | B1 |
| 6469742 | Trovato et al. | Oct 2002 | B1 |
| 6496864 | Mccartney | Dec 2002 | B1 |
| 6505298 | Cerbini et al. | Jan 2003 | B1 |
| 6510152 | Gerszberg et al. | Jan 2003 | B1 |
| 6529965 | Thomsen et al. | Mar 2003 | B1 |
| 6532552 | Benignus et al. | Mar 2003 | B1 |
| 6542500 | Gerszberg et al. | Apr 2003 | B1 |
| 6542739 | Garner | Apr 2003 | B1 |
| 6546016 | Gerszberg et al. | Apr 2003 | B1 |
| 6546419 | Humpleman et al. | Apr 2003 | B1 |
| 6600958 | Zondag | Jul 2003 | B1 |
| 6606711 | Andrews et al. | Aug 2003 | B2 |
| 6625274 | Hoffpauir et al. | Sep 2003 | B1 |
| 6630943 | Nason et al. | Oct 2003 | B1 |
| 6631350 | Celi, Jr. et al. | Oct 2003 | B1 |
| 6631403 | Deutsch et al. | Oct 2003 | B1 |
| 6651248 | Alpern | Nov 2003 | B1 |
| 6654722 | Aldous et al. | Nov 2003 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6714534 | Gerszberg et al. | Mar 2004 | B1 |
| 6750879 | Sandberg | Jun 2004 | B2 |
| 6762796 | Nakajoh et al. | Jul 2004 | B1 |
| 6762798 | Messer et al. | Jul 2004 | B1 |
| 6802056 | Chaiken et al. | Oct 2004 | B1 |
| 6847649 | Sutanto | Jan 2005 | B2 |
| 6850533 | Gerszberg et al. | Feb 2005 | B2 |
| 6856330 | Chew et al. | Feb 2005 | B1 |
| 6873877 | Tobias et al. | Mar 2005 | B1 |
| 6895573 | Norgaard et al. | May 2005 | B2 |
| 6938254 | Mathur et al. | Aug 2005 | B1 |
| 6941341 | Logston et al. | Sep 2005 | B2 |
| 6944185 | Patki et al. | Sep 2005 | B2 |
| 6948175 | Fong et al. | Sep 2005 | B1 |
| 6948183 | Peterka | Sep 2005 | B1 |
| 6952836 | Donlan et al. | Oct 2005 | B1 |
| 6968364 | Wong et al. | Nov 2005 | B1 |
| 6973050 | Birdwell et al. | Dec 2005 | B2 |
| 6996808 | Niewiadomski et al. | Feb 2006 | B1 |
| 7010796 | Strom et al. | Mar 2006 | B1 |
| 7039633 | Dey et al. | May 2006 | B1 |
| 7055146 | Durr et al. | May 2006 | B1 |
| 7058964 | Khandelwal et al. | Jun 2006 | B2 |
| 7068597 | Fijolek et al. | Jun 2006 | B1 |
| 7080356 | Atallah et al. | Jul 2006 | B2 |
| 7096459 | Keller et al. | Aug 2006 | B2 |
| 7111072 | Matthews et al. | Sep 2006 | B1 |
| 7137106 | Herman et al. | Nov 2006 | B2 |
| 7146305 | Made et al. | Dec 2006 | B2 |
| 7158993 | Schwabe | Jan 2007 | B1 |
| 7181725 | Posegga et al. | Feb 2007 | B1 |
| 7194249 | Phillips et al. | Mar 2007 | B2 |
| 7203869 | Gwak | Apr 2007 | B2 |
| 7213213 | Sekiguchi et al. | May 2007 | B2 |
| 7216170 | Ludvig et al. | May 2007 | B2 |
| 7240104 | Gautney | Jul 2007 | B2 |
| 7266726 | Ladd et al. | Sep 2007 | B1 |
| 7290253 | Agesen | Oct 2007 | B1 |
| 7316003 | Dulepet et al. | Jan 2008 | B1 |
| 7328333 | Kawano et al. | Feb 2008 | B2 |
| 7366286 | Shenoi | Apr 2008 | B1 |
| 7370322 | Matena et al. | May 2008 | B1 |
| 7394473 | Asai | Jul 2008 | B2 |
| 7401324 | Dmitriev | Jul 2008 | B1 |
| 7478341 | Dove | Jan 2009 | B2 |
| 7487534 | Peterka et al. | Feb 2009 | B1 |
| 7546602 | Hejlsberg et al. | Jun 2009 | B2 |
| 7552450 | Evans et al. | Jun 2009 | B1 |
| 7581012 | Shiouchi et al. | Aug 2009 | B2 |
| 7606529 | Swan et al. | Oct 2009 | B1 |
| 7698606 | Ladd et al. | Apr 2010 | B2 |
| 7814544 | Wilhelm | Oct 2010 | B1 |
| 7945902 | Sahoo | May 2011 | B1 |
| 8024607 | Ladd et al. | Sep 2011 | B2 |
| 8042113 | Clohessy et al. | Oct 2011 | B2 |
| 8046636 | Ladd et al. | Oct 2011 | B2 |
| 8265028 | Davies et al. | Sep 2012 | B2 |
| 8302111 | Ladd et al. | Oct 2012 | B2 |
| 8321723 | Ladd et al. | Nov 2012 | B2 |
| 8599797 | Pelkonen | Dec 2013 | B2 |
| 8724588 | Li et al. | May 2014 | B2 |
| 8750710 | Hirt et al. | Jun 2014 | B1 |
| 8799723 | Ladd et al. | Aug 2014 | B2 |
| 8880071 | Taaghol et al. | Nov 2014 | B2 |
| 8989297 | Lou et al. | Mar 2015 | B1 |
| 8997136 | Brooks et al. | Mar 2015 | B2 |
| 9001789 | Hosobe | Apr 2015 | B2 |
| 9185341 | Hardin | Nov 2015 | B2 |
| 9300445 | Hardin | Mar 2016 | B2 |
| 9564932 | Pack et al. | Feb 2017 | B1 |
| 9596593 | Li et al. | Mar 2017 | B2 |
| 9612816 | Choi et al. | Apr 2017 | B2 |
| 9654149 | Piipponen et al. | May 2017 | B2 |
| 9706512 | Suh | Jul 2017 | B2 |
| 9769692 | Freda et al. | Sep 2017 | B2 |
| 9807778 | Ma et al. | Oct 2017 | B2 |
| 9813148 | Syed et al. | Nov 2017 | B2 |
| 9894659 | Wang et al. | Feb 2018 | B1 |
| 9918260 | Marinier et al. | Mar 2018 | B2 |
| 9948349 | Malach | Apr 2018 | B2 |
| 10009431 | Holtmanns | Jun 2018 | B2 |
| 10135730 | Chou | Nov 2018 | B2 |
| 10164858 | Gunasekara et al. | Dec 2018 | B2 |
| 10375629 | Zhang | Aug 2019 | B2 |
| 10506456 | Lou et al. | Dec 2019 | B2 |
| 10506499 | Keller et al. | Dec 2019 | B2 |
| 10680883 | Hall et al. | Jun 2020 | B2 |
| 10693687 | Kushnir | Jun 2020 | B1 |
| 10924825 | Das et al. | Feb 2021 | B2 |
| 11026004 | Das | Jun 2021 | B2 |
| 11044597 | Wong et al. | Jun 2021 | B2 |
| 11102560 | Hoole et al. | Aug 2021 | B2 |
| 11129213 | Vaidya et al. | Sep 2021 | B2 |
| 11405797 | Vaidya et al. | Aug 2022 | B2 |
| 11432284 | Hmimy et al. | Aug 2022 | B2 |
| 20010007138 | Iida et al. | Jul 2001 | A1 |
| 20010049691 | Asazu | Dec 2001 | A1 |
| 20020009149 | Rodriguez et al. | Jan 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020034193 | Patki et al. | Mar 2002 | A1 |
| 20020038358 | Sweatt, III et al. | Mar 2002 | A1 |
| 20020040470 | Guthrie et al. | Apr 2002 | A1 |
| 20020044567 | Voit et al. | Apr 2002 | A1 |
| 20020044569 | Kwok et al. | Apr 2002 | A1 |
| 20020049978 | Rodriguez et al. | Apr 2002 | A1 |
| 20020052977 | Stall | May 2002 | A1 |
| 20020073244 | Davies et al. | Jun 2002 | A1 |
| 20020083214 | Heisig et al. | Jun 2002 | A1 |
| 20020112090 | Bennett et al. | Aug 2002 | A1 |
| 20020126144 | Chenede | Sep 2002 | A1 |
| 20020144193 | Hicks et al. | Oct 2002 | A1 |
| 20020170033 | Chen | Nov 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020174433 | Baumgartner et al. | Nov 2002 | A1 |
| 20020191028 | Senechalle et al. | Dec 2002 | A1 |
| 20020198868 | Kinzhalin et al. | Dec 2002 | A1 |
| 20030005454 | Rodriguez et al. | Jan 2003 | A1 |
| 20030009765 | Linden et al. | Jan 2003 | A1 |
| 20030009769 | Hensgen et al. | Jan 2003 | A1 |
| 20030037331 | Lee | Feb 2003 | A1 |
| 20030041291 | Hashem et al. | Feb 2003 | A1 |
| 20030056155 | Austen et al. | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061240 | Mccann et al. | Mar 2003 | A1 |
| 20030081664 | Lu et al. | May 2003 | A1 |
| 20030105995 | Schroath et al. | Jun 2003 | A1 |
| 20030107604 | Ording | Jun 2003 | A1 |
| 20030110331 | Kawano et al. | Jun 2003 | A1 |
| 20030110511 | Schutte et al. | Jun 2003 | A1 |
| 20030121055 | Kaminski et al. | Jun 2003 | A1 |
| 20030122879 | Inui et al. | Jul 2003 | A1 |
| 20030140285 | Wilkie | Jul 2003 | A1 |
| 20030163811 | Luehrs | Aug 2003 | A1 |
| 20030181241 | Oakes et al. | Sep 2003 | A1 |
| 20030188320 | Shing | Oct 2003 | A1 |
| 20030204848 | Cheng et al. | Oct 2003 | A1 |
| 20030217197 | Chan et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030229899 | Thompson et al. | Dec 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20030231855 | Gates et al. | Dec 2003 | A1 |
| 20040003400 | Carney et al. | Jan 2004 | A1 |
| 20040034697 | Fairhurst et al. | Feb 2004 | A1 |
| 20040040041 | Crawford | Feb 2004 | A1 |
| 20040073944 | Booth | Apr 2004 | A1 |
| 20040078695 | Bowers et al. | Apr 2004 | A1 |
| 20040078829 | Patel et al. | Apr 2004 | A1 |
| 20040083464 | Cwalina et al. | Apr 2004 | A1 |
| 20040098730 | Foote et al. | May 2004 | A1 |
| 20040103434 | Ellis | May 2004 | A1 |
| 20040107451 | Khandelwal et al. | Jun 2004 | A1 |
| 20040143836 | McCormack et al. | Jul 2004 | A1 |
| 20040158649 | Ophir et al. | Aug 2004 | A1 |
| 20040158829 | Beresin et al. | Aug 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040186603 | Sanford et al. | Sep 2004 | A1 |
| 20040187152 | Francis et al. | Sep 2004 | A1 |
| 20040187156 | Palm et al. | Sep 2004 | A1 |
| 20040199903 | Iizuka | Oct 2004 | A1 |
| 20040205339 | Medin | Oct 2004 | A1 |
| 20040218736 | Fang et al. | Nov 2004 | A1 |
| 20040236759 | Young | Nov 2004 | A1 |
| 20040261092 | Addington et al. | Dec 2004 | A1 |
| 20040261114 | Addington et al. | Dec 2004 | A1 |
| 20040261116 | Mckeown et al. | Dec 2004 | A1 |
| 20040261126 | Addington et al. | Dec 2004 | A1 |
| 20050015799 | Park | Jan 2005 | A1 |
| 20050021766 | Mckeowen et al. | Jan 2005 | A1 |
| 20050027851 | Mckeown et al. | Feb 2005 | A1 |
| 20050034159 | Ophir et al. | Feb 2005 | A1 |
| 20050063317 | Risberg et al. | Mar 2005 | A1 |
| 20050071818 | Reissman et al. | Mar 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050120385 | Stalker | Jun 2005 | A1 |
| 20050132346 | Tsantilis | Jun 2005 | A1 |
| 20050160045 | Watanabe et al. | Jul 2005 | A1 |
| 20050162267 | Khandelwal et al. | Jul 2005 | A1 |
| 20050177832 | Chew | Aug 2005 | A1 |
| 20050273762 | Lesh | Dec 2005 | A1 |
| 20060005183 | Minear et al. | Jan 2006 | A1 |
| 20060020950 | Ladd et al. | Jan 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060070051 | Kuck et al. | Mar 2006 | A1 |
| 20060129947 | Hamzy et al. | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060143492 | Leduc et al. | Jun 2006 | A1 |
| 20060161946 | Shin | Jul 2006 | A1 |
| 20070094345 | Rabbers et al. | Apr 2007 | A1 |
| 20070207771 | Bowser et al. | Sep 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070261090 | Miller et al. | Nov 2007 | A1 |
| 20070288897 | Branda et al. | Dec 2007 | A1 |
| 20070294673 | Guerrera et al. | Dec 2007 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080101291 | Jiang et al. | May 2008 | A1 |
| 20080178153 | Fox et al. | Jul 2008 | A1 |
| 20080196011 | Bhandari et al. | Aug 2008 | A1 |
| 20080256510 | Auerbach | Oct 2008 | A1 |
| 20080279287 | Asahina | Nov 2008 | A1 |
| 20080288930 | Chen et al. | Nov 2008 | A1 |
| 20090082060 | Namatame | Mar 2009 | A1 |
| 20090110088 | Di Giandomenico et al. | Apr 2009 | A1 |
| 20090119735 | Dounaevski et al. | May 2009 | A1 |
| 20090176490 | Kazmi et al. | Jul 2009 | A1 |
| 20090217326 | Hasek | Aug 2009 | A1 |
| 20090222867 | Munetsugu | Sep 2009 | A1 |
| 20100008235 | Tinnakornsrisuphap et al. | Jan 2010 | A1 |
| 20100035610 | Narang et al. | Feb 2010 | A1 |
| 20100064330 | Yu et al. | Mar 2010 | A1 |
| 20100176912 | Sears et al. | Jul 2010 | A1 |
| 20100178912 | Gunnarsson et al. | Jul 2010 | A1 |
| 20110117917 | Gresset et al. | May 2011 | A1 |
| 20110124335 | Martin et al. | May 2011 | A1 |
| 20110190000 | Kwun | Aug 2011 | A1 |
| 20110207456 | Radulescu et al. | Aug 2011 | A1 |
| 20110281583 | Hole | Nov 2011 | A1 |
| 20120076009 | Pasko | Mar 2012 | A1 |
| 20120083207 | Rofougaran et al. | Apr 2012 | A1 |
| 20120224563 | Zisimopoulos et al. | Sep 2012 | A1 |
| 20120246255 | Walker et al. | Sep 2012 | A1 |
| 20120275315 | Schlangen et al. | Nov 2012 | A1 |
| 20130010686 | Shatzkamer et al. | Jan 2013 | A1 |
| 20130077515 | Jung et al. | Mar 2013 | A1 |
| 20130077554 | Gauvreau et al. | Mar 2013 | A1 |
| 20130079003 | Nagaraja et al. | Mar 2013 | A1 |
| 20130143555 | Singh et al. | Jun 2013 | A1 |
| 20130156115 | Petrovic | Jun 2013 | A1 |
| 20130178225 | Jul 2013 | A1 | |
| 20130189990 | Kim et al. | Jul 2013 | A1 |
| 20130201316 | Binder et al. | Aug 2013 | A1 |
| 20130215870 | Hosobe | Aug 2013 | A1 |
| 20130247027 | Shah et al. | Sep 2013 | A1 |
| 20130252616 | Murakami | Sep 2013 | A1 |
| 20130267229 | Gopalakrishnan | Oct 2013 | A1 |
| 20130279914 | Brooks | Oct 2013 | A1 |
| 20130322504 | Asati et al. | Dec 2013 | A1 |
| 20130337794 | Kojima | Dec 2013 | A1 |
| 20140073304 | Brisebois et al. | Mar 2014 | A1 |
| 20140087715 | Suzuki et al. | Mar 2014 | A1 |
| 20140148107 | Maltsev et al. | May 2014 | A1 |
| 20140282704 | Tumuluru et al. | Sep 2014 | A1 |
| 20140282802 | Bowler et al. | Sep 2014 | A1 |
| 20140308986 | Yang et al. | Oct 2014 | A1 |
| 20140354442 | Maity et al. | Dec 2014 | A1 |
| 20140370895 | Pandey et al. | Dec 2014 | A1 |
| 20150063137 | Shen et al. | Mar 2015 | A1 |
| 20150085853 | Smith et al. | Mar 2015 | A1 |
| 20150087354 | Ianev et al. | Mar 2015 | A1 |
| 20150098349 | Wei et al. | Apr 2015 | A1 |
| 20150156777 | Negus et al. | Jun 2015 | A1 |
| 20150181363 | Khorami | Jun 2015 | A1 |
| 20150201088 | Wu et al. | Jul 2015 | A1 |
| 20150208290 | Seo et al. | Jul 2015 | A1 |
| 20150229584 | Okamoto et al. | Aug 2015 | A1 |
| 20150365178 | Maattanen et al. | Dec 2015 | A1 |
| 20160007138 | Palanisamy et al. | Jan 2016 | A1 |
| 20160013855 | Campos et al. | Jan 2016 | A1 |
| 20160014651 | Wellington | Jan 2016 | A1 |
| 20160020835 | Stadelmeier et al. | Jan 2016 | A1 |
| 20160021595 | Czaja et al. | Jan 2016 | A1 |
| 20160073344 | Vutukuri et al. | Mar 2016 | A1 |
| 20160094421 | Bali et al. | Mar 2016 | A1 |
| 20160127434 | Yoon et al. | May 2016 | A1 |
| 20160128072 | Rajagopal et al. | May 2016 | A1 |
| 20160212632 | Katamreddy et al. | Jul 2016 | A1 |
| 20160259923 | Papa et al. | Sep 2016 | A1 |
| 20160373974 | Gomes et al. | Dec 2016 | A1 |
| 20170019144 | Malach | Jan 2017 | A1 |
| 20170055186 | Donepudi et al. | Feb 2017 | A1 |
| 20170094527 | Shattil et al. | Mar 2017 | A1 |
| 20170111846 | Kang | Apr 2017 | A1 |
| 20170118527 | Wachob et al. | Apr 2017 | A1 |
| 20170149937 | Ren et al. | May 2017 | A1 |
| 20170155703 | Hao et al. | Jun 2017 | A1 |
| 20170164068 | Wachob et al. | Jun 2017 | A1 |
| 20170201912 | Zingler et al. | Jul 2017 | A1 |
| 20170208488 | Hwang et al. | Jul 2017 | A1 |
| 20170208540 | Egner et al. | Jul 2017 | A1 |
| 20170245281 | Zuckerman et al. | Aug 2017 | A1 |
| 20170265220 | Andreoli-Fang et al. | Sep 2017 | A1 |
| 20170316233 | Kherani et al. | Nov 2017 | A1 |
| 20180063813 | Gupta et al. | Mar 2018 | A1 |
| 20180092142 | Han et al. | Mar 2018 | A1 |
| 20180098245 | Livanos et al. | Apr 2018 | A1 |
| 20180146408 | Meylan et al. | May 2018 | A1 |
| 20180167128 | Kinamon et al. | Jun 2018 | A1 |
| 20180184337 | Jin et al. | Jun 2018 | A1 |
| 20180213452 | Kim et al. | Jul 2018 | A1 |
| 20180269974 | Luciano | Sep 2018 | A1 |
| 20180316563 | Kumar et al. | Nov 2018 | A1 |
| 20180331935 | Ross et al. | Nov 2018 | A1 |
| 20180338277 | Byun et al. | Nov 2018 | A1 |
| 20180343685 | Hart et al. | Nov 2018 | A1 |
| 20180351665 | Fukuta et al. | Dec 2018 | A1 |
| 20180351809 | Meredith et al. | Dec 2018 | A1 |
| 20180375887 | Dezent et al. | Dec 2018 | A1 |
| 20190007870 | Gupta et al. | Jan 2019 | A1 |
| 20190028141 | Padden et al. | Jan 2019 | A1 |
| 20190037630 | Zhang et al. | Jan 2019 | A1 |
| 20190053193 | Park et al. | Feb 2019 | A1 |
| 20190075023 | Sirotkin | Mar 2019 | A1 |
| 20190082447 | Harsha et al. | Mar 2019 | A1 |
| 20190082501 | Vesely et al. | Mar 2019 | A1 |
| 20190098582 | Mackenzie et al. | Mar 2019 | A1 |
| 20190109643 | Campos et al. | Apr 2019 | A1 |
| 20190124572 | Park et al. | Apr 2019 | A1 |
| 20190124696 | Islam et al. | Apr 2019 | A1 |
| 20190141586 | Olsson et al. | May 2019 | A1 |
| 20190158975 | Petersen | May 2019 | A1 |
| 20190208380 | Shi et al. | Jul 2019 | A1 |
| 20190229974 | Campos et al. | Jul 2019 | A1 |
| 20190245740 | Kachhla | Aug 2019 | A1 |
| 20190253944 | Kim | Aug 2019 | A1 |
| 20190261264 | Lou et al. | Aug 2019 | A1 |
| 20190289470 | Vaidya et al. | Sep 2019 | A1 |
| 20190319814 | Das | Oct 2019 | A1 |
| 20190319858 | Das et al. | Oct 2019 | A1 |
| 20190320250 | Hoole et al. | Oct 2019 | A1 |
| 20190320322 | Jayawardene et al. | Oct 2019 | A1 |
| 20190320494 | Jayawardene et al. | Oct 2019 | A1 |
| 20190349848 | Bali | Nov 2019 | A1 |
| 20190357037 | Velev et al. | Nov 2019 | A1 |
| 20190357199 | Ali et al. | Nov 2019 | A1 |
| 20190379455 | Wang et al. | Dec 2019 | A1 |
| 20200021689 | Sultana et al. | Jan 2020 | A1 |
| 20200053545 | Wong et al. | Feb 2020 | A1 |
| 20200091608 | Alpman et al. | Mar 2020 | A1 |
| 20200112888 | Glennon et al. | Apr 2020 | A1 |
| 20200120724 | Vaidya et al. | Apr 2020 | A1 |
| 20200154388 | Koshimizu et al. | May 2020 | A1 |
| 20200214065 | Tomala et al. | Jul 2020 | A1 |
| 20200280836 | Velev et al. | Sep 2020 | A1 |
| 20210028915 | Jia et al. | Jan 2021 | A1 |
| 20210029759 | Tang | Jan 2021 | A1 |
| 20210112551 | Anderson et al. | Apr 2021 | A1 |
| 20210175925 | Tarighat Mehrabani | Jun 2021 | A1 |
| 20210176665 | Lan et al. | Jun 2021 | A1 |
| 20210250196 | Das et al. | Aug 2021 | A1 |
| 20210281993 | Tiwari et al. | Sep 2021 | A1 |
| 20210336815 | Das et al. | Oct 2021 | A1 |
| 20210337543 | Das et al. | Oct 2021 | A1 |
| 20220078624 | Hong | Mar 2022 | A1 |
| 20220132524 | Mueck et al. | Apr 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 105071860 | Nov 2015 | CN |
| 0812119 | Dec 1997 | EP |
| 1046259 | Oct 2000 | EP |
| 2548796 | Oct 2017 | GB |
| 2006325206 | Nov 2006 | JP |
| 2011254495 | Dec 2011 | JP |
| 2016511998 | Apr 2016 | JP |
| 2017118483 | Jun 2017 | JP |
| 2018510589 | Apr 2018 | JP |
| 20160097917 | Aug 2016 | KR |
| WO-0024192 | Apr 2000 | WO |
| WO-0213039 | Feb 2002 | WO |
| WO-2004045125 | May 2004 | WO |
| WO-2015147707 | Oct 2015 | WO |
| WO-2017186294 | Nov 2017 | WO |
| WO-2018131488 | Jul 2018 | WO |
| WO-2018131904 | Jul 2018 | WO |
| Entry |
|---|
| Methods and Arrangements for Proximity Detection; WO 2013051988 A1 (Year: 2013). |
| Method and Apparatus for Controlling Collision of Physical Cell Identifier; KR 20160107419 A (Year: 2016). |
| Method And Apparatus For Automatically Allocating Physical Cell Identity In Wireless Communication System; KR 101890156 B1 (Year: 2018). |
| Method and Apparatus for Controlling Physical Cell Identifier; KR 20160123469 A (Year: 2016). |
| Channel Evacuation Procedures for Wireless Networks Deployed in Dynamic Shared Spectrum; WO 2014078676 A2 (Year: 2014). |
| Marinier et al. (WO 2010120837 A1): Resolving Physical Layer Cell Identity Confusion For Providing Inbound Mobility To Closed Subscriber Group (CSG) By Identifying Cell Global Identity (CGI) Of Neighbor CSG Cell If First And Second Sets Of System Information Are Similar. (Year: 2010). |
| Wang et al. (WO 2014029107 A1): PCI Confusion Detection Method, User Equipment, and Base Station. (Year: 2014). |
| Feng, Wenbin (WO 2016095461 A1); Handling Method and Detection Base Station for Physical Cell Identity Confusion. (Year: 2016). |
| Hwang Hyun et al. (KR 20160107419 A): Method and Apparatus for Controlling Collision of Physical Cell Identifier. (Year: 2016). |
| 3GPP., “Evolved Universal Terrestrial Radio Access (E-UTRA), Carrier Aggregation, Base Station (BS) radio transmission and reception (Release 10)”, Technical Specification Group Radio Access Network, Technical Report (TR 36.808 V10.1.0), 2013, 31 pages. |
| 3GPP., “Radio Resource Control (RRC) protocol specification (Release 16)”, Technical Specification Group Radio Access Network, TS 38.331 (V16.0.0), Mar. 2020, 832 pages. |
| 3GPP., “RAN Adjusts Schedule for 2nd Wave of 5G Specifications (Release 16)”, 2 pages, Retrieved from the internet [URL: https://www.3gpp.org/news-events/3gpp-news/2005-ran_r16_schedule]. |
| 3GPP TR 38.801 v.14.0.0 (Mar. 2017) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology: Radio Access Architecture and Interfaces (Release 14), 91 pages. |
| 3GPP TS 23.234 v13.1.0, “3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 13)” 2017, 18 pages. |
| 3GPP TS 23.501 v.15.4.0 (Dec. 2018) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2; Release 15, 236 pages. |
| 3GPP TS 23.502 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2; v. 16.0.0, (Mar. 2019) 420 pages. |
| 3GPP TS 32.300 V15.0.0 (Jun. 2018), Technical Specification—3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Name convention for managed objects, (Release 15) Jun. 2018, 27 pages. |
| 3GPP TS 36.300 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network, (Dec. 2017) 338 pages. |
| 3GPP TS 36.413 V14.4. entitled “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 14)” dated Sep. 2017. |
| 3GPP TS 36.413, V14.4.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 14)”, 2018. |
| 3GPP TS 37.213 LTE; Physical Layer Procedures For Shared Spectrum Channel Access, version 15.0.0 Release 15, (Jul. 2018) 22 pages. |
| 3GPP TS 38.306 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) radio access capabilities (Release 15), (Dec. 2020) 60 pages. |
| 3GPP TS 38.413 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 16), (Dec. 2019) 335 pages. |
| 3GPP TS 38.473 V15.1.1 (Apr. 2018) “3rd Generation Partnership Project; Technical Specification Group Radio Access Network,” TS 38.473 (v15.0.0), Dec. 2017, NG-RAN, F1 application protocol (F1AP), Release 15, 90 pages. |
| 3GPP TS 38.473 V15.A.A (Apr. 2018) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15), 106 pages. |
| 3GPP TS 38.889 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on NR-based Access to Unlicensed Spectrum; Release 16, (Nov. 2018), 120 pages. |
| 3GPP., “Study on New Radio Access Technology, Radio Interface Protocol Aspects (Release 14)”, Technical Specification Group Radio Access Network, Technical Report (TR 38.804), V14.0.0 (Mar. 2017), 57 pages. |
| Allen, et al., The Case for Run-Time Types in Generic Java, Rice University 2002 pp. 1-6. |
| Article 5 of the Radio Regulations (edition 2001), Introduction to International Radio Regulations, 161 pages. |
| Bertenyi B., 3GPP TSG RAN, RAN Adjusts Schedule for2nd Wave of 5G Specifications, The Mobile Broadband Standard, A Global Initiative, Dec. 14, 2018, retrieved from the Internet: (https://www.3gpp.org/news-events/3gpp-news/2005-ran_r16_schedule), 2 pages. |
| Bluetooth Core Specification, Jun. 30, 2010, Version 4.0, 2302 pages. |
| Chapter 4—Window Manager for Mac ©. Apple Computer. Inc., Jul. 11, 1996, 4 pages. |
| Chapter 7—Window Management, SOL library Documentation vU.3-rev 1, Sep. 2001, 2 pages. |
| Chou, et al., Open CPE Architecture: A Solution to the Delivery of Integrated Services over Broadband, Intel Communication Group, Corp. pp. 1-10, 2001. |
| Curran K., et al., “The Use of Dynamically Reconfigurable Protocol Stacks for Streaming Multimedia to Mobile Devices,” 8th IEEE International Conference on Communication Systems Singapore, Nov. 25-28, 2002, pp. 947-951. URL: http://www.infm.ulst.ac.uk/.about.kevin/pubs.htm. |
| Day, “Java Media Framework Player API”, Apr. 1997, XP-002093309, www.javaworld.com. |
| Eldering, Charles, Customer Permises Epuipment Residential Broadband Networks, Jun. 1997, IEEE, p. 114-212. |
| Ellis, “Getting to Know the OpenCable Application Platform,” Sun microsystems, Jun. 2006. |
| ETSI TS 123 502 v15.2.0 (Jun. 2018) Technical Specification; 5G; Procedures for the 5G System; 311 pages. |
| Evain, “The Multimedia Home Platform” EBU Review—Technical, European Broadcasting Union. Brussels, BE, No. 275, Mar. 21, 1998, pp. 4-10, XP000767493. |
| GSMA Road to 5G: Introduction and Migration, Apr. 2018, 54 pages. |
| Han R., et al., Websplitter, 2000, pp. 13. |
| Hentschel et al., Video Quality Of Service For Consumer Terminal A Novel System For Programmable Componets, 2002, IEEE, pp. 28-29. |
| Hutchings D. R., et al., New Operation for Display Space Management and Window Management, Technical Report GIT-GVU-02-18, Aug. 2002, 20 pages. |
| IEEE 802.11 standard, 1997, URL: http://www.ieeexplore.ieee.org/documenU654779, 459 pages. |
| IEEE Standards 802.3, 2008, 27 pages. |
| IEEE Std. 802.15.4-2015; IEEE Standard for Low-Rate Wireless Networks, approved Dec. 5, 2015, 708 pages. |
| Interworking Wi-Fi and Mobile Networks, The Choice of Mobility Solutions, White Paper, 2013, 13 pages. |
| Java Media Players, V.1.0.5, May 5, 1998, X940410443, Sun Microsystems, Inc. |
| “JMFRegistry User's Guide”, Sun Microsystems, XP-002573305, Mar. 8, 2010. |
| Kar, et al., Cable's Home Digital Network Interface Of Choice, 1999, Cable Television Lab. IEEE, pp. 34-35. |
| Luu J, “MainWin and Window Managers,” Mainsoft, 2000, 5 pages. |
| Mayer, “Analyzing the Use of Interfaces in Large OO Projects,” ACM, Oct. 2003. |
| Motorola, Control Management Module (CMM 2000) information sheets: 4 pages; C Motorola, Inc. 2001; https://www.motorola.com/broadband. |
| Motorola, HFC Manager, Integrated Element Management System information sheets; 4 pages; .COPYRGT. Motorola, Inc. 2003; https://www.motorola.com/broadband. |
| Motorola Product Detail, HFC Manager HFC Element Management System; 1 page: © Motorola, Inc. 2004; https://www.motorola.com/lbroadband. |
| Nokia 5G New Radio (NR): Physical Layer Overview and Performance, IEEE Communication Theory Workshop, 2018 by A. Ghosh, May 15, 2018, 38 pages. |
| OCAP Applications in Detail (pp. 1-8), www.tvwithoutborders.com, Feb. 13, 2010. |
| OpenCable Application Platform Specification (“OpenCable” copyright 2001-2003 pp. 1-398). |
| OpenCable Host Device, Core Functional Requirements, Issued Specification (OC-SP-HOST-CFR-I14-030905), Sep. 5, 2003, 81 pages. |
| Scientific Atlanta, ROSA Network Management System and Element Management web pages, 10 pages, © Scientific Atlanta 2006, www.scientificatlanta.com. |
| Scientific Atlanta, Subscriber Networks; Explorer.RTM. 3100HD High Definition DHCT information pages; Oct. 2001; 2 pgs. |
| Scientific Atlanta, Subscriber Networks; Explorer.RTM. 4200 Home Gateway information pages; Sep. 2003; 3 pgs. |
| Scientific Atlanta, Subscriber Products; Explorer.RTM. 8000. TM. Home Entertainment Server information pages; Nov. 2003; 4 pgs. |
| Wi-Fi Agile Multiband Specification Version 1.2 dated Dec. 31, 2018. |
| Wi-Fi Certified Agile MultibandTM Technology Overview, Dec. 2017, 9 pages. |
| Wi-Fi Direct, “Wi-Fi Peer-to-Peer (P2P) Specification,” Wi-Fi Alliance, Version 1.5, 2014, 183 pages. |
| Xie, et al., “MAPO: Mining API Usages from Open Source Repositories,” ACM, May 2006. |
| Maamoun K. M. et al., “A Survey and a Novel Scheme for RoF-PON as FTTx Wireless Services,” 2009 6th InternationalSymposium on High Capacity Optical Networks and Enabling Technologies(HONET), IEEE, 2009, pp. 246-253. |
| Number | Date | Country | |
|---|---|---|---|
| 20220007440 A1 | Jan 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62745065 | Oct 2018 | US | |
| 62752002 | Oct 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16601345 | Oct 2019 | US |
| Child | 17479989 | US |
