WO2020077346A1 - Apparatus and methods for cell identification in wireless networks - Google Patents
Apparatus and methods for cell identification in wireless networks Download PDFInfo
- Publication number
- WO2020077346A1 WO2020077346A1 PCT/US2019/056150 US2019056150W WO2020077346A1 WO 2020077346 A1 WO2020077346 A1 WO 2020077346A1 US 2019056150 W US2019056150 W US 2019056150W WO 2020077346 A1 WO2020077346 A1 WO 2020077346A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user devices
- pci
- optional
- gnb
- mobility
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
- H04W8/265—Network addressing or numbering for mobility support for initial activation of new user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/14—Spectrum sharing arrangements between different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
Definitions
- 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.
- RANs Radio Area Networks
- RATs Radio Access Technologies
- 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).
- 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).
- 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: Table 1
- 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.
- non-ISM license-free communications applications
- wireless sensor networks in the 915 MHz and 2.450 GHz bands
- wireless LANs e.g., Wi-Fi
- cordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.
- 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
- networks e.g., the Internet, intranets, or extranets
- 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).
- WAP wireless access point
- 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.
- NR 5G New Radio
- 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).
- LTE entities 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).
- EPC Evolved Packet Core
- 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.
- FIG. 1 shows the 5G architecture 100 as defined in 3GPP TS 23.501 (Fig. 4.2.3-1 thereof).
- FIG. 2a shows the architecture 200 for interworking between 5GS and EPC/E-UTRAN as defined in TS 23.501 (Fig. 4.3.1-1 thereof), specifically the non-roaming architecture for interworking between the 5GS and the EPC/E-UTRAN.
- E- UTRAN (4G/4.5G) 202 Two different RAN technologies are supported; i.e., E- UTRAN (4G/4.5G) 202, and 5G (NG-RAN) 204.
- FIG. 2b shows a roaming architecture counterpart (i.e., with HPLMN and visited network (VPLMN).
- 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).
- PHY physical layer
- 5G NR Release 15 and beyond presently allows up to 1008 unique PCIs.
- a given PLMN (e.g., HPLMN or VPLMN, such as those described above with respect to FIGS. l-2b) has many cells.
- PCIs are rather limited in number, the notion of an ECGI (E-UTRAN Cell Global Identifier; LTE), and NCGI (NR Cell Global Identifier; 5G NR) was introduced, wherein a PLMN-ID is used in addition to the PCI to uniquely identify a given cell within a given PLMN (and also across it; i.e., inter-PLMN).
- the ECGI is constructed from the MCC (Mobile Country Code), MNC (Mobile Network Code) and the ECI (E-UTRAN Cell Identifier), while the NCGI is constructed from the PLMN identity to which the cell belongs and the NR Cell Identity (NCI) of the cell.
- MCC Mobile Country Code
- MNC Mobile Network Code
- ECI E-UTRAN Cell Identifier
- 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.
- PCI Confusion i.e., an ambiguity as to which PLMN a given PCI detected by a UE belongs.
- ANR Automatic Neighbor cell Relations
- 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.
- 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).
- NR- U Unlicensed spectrum
- CA Carrier Aggregation
- DC Dual Connectivity
- SA Standalone
- 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.
- 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.
- a method for cell identification within a wireless network 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.
- a set of candidate user devices e.g., UE(s)
- 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.
- 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.
- 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.
- 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.
- a wireless access 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.
- the node comprises a 3GPP-compliant gNB or eNB.
- a method for identifying a subset of user devices 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.
- 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 UECapabilitylnformation message (the latter sent in response to UECapability Inquiry message).
- 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.
- a mobile computerized device in another aspect of the disclosure, includes a 3GPP-compliant UE (user equipment) which is configured .
- 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.
- a system in yet another aspect, 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.
- a method for limiting a scope of a PCI search 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.
- a base station e.g., gNB
- a method of conducting Physical Cell ID (PCI) conflict resolution 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).
- PLMN ID Public Land Mobile Network ID
- IE measurement results reporting information element
- FIG. 1 is a functional block diagram of a prior art 5G system architecture and the various components thereof.
- FIG. 2a is a block diagram showing the extant architecture for interworking between 5GS and EPC/E-UTRAN as defined in 3 GPP TS 23.501 (Fig. 4.3.1-1 thereof), specifically the non-roaming architecture for interworking between the 5GS and the EPC/E-UTRAN.
- FIG. 2b shows a prior art roaming architecture counterpart to the architecture of FIG. 2a (i.e., with HPLMN and visited network (VPLMN)).
- HPLMN HPLMN and visited network (VPLMN)
- FIG. 2c shows a graphical representation of the PCI“confusion” problem between licensed and unlicensed spectrum networks within the exemplary 5G NR context.
- FIG. 3 is a logical flow diagram illustrating one embodiment of a generalized method of PCI conflict resolution according to the present disclosure.
- FIG. 3a is a logical flow diagram illustrating one embodiment of user device set identification within the generalized method of FIG. 3.
- FIG. 3b is a logical flow diagram illustrating one embodiment of user device measurement reporting within the generalized method of FIG. 3.
- FIG. 3c is a logical flow diagram illustrating a second embodiment of user device measurement reporting within the generalized method of FIG. 3.
- FIG. 3d is a logical flow diagram illustrating one embodiment of whitelist/blacklist updating based on measurement reporting, within the generalized method of FIG. 3.
- FIG. 4 is a functional block diagram of a first exemplary embodiment of an enhanced 5G NR network architecture according to the present disclosure.
- FIG. 4a is a functional block diagram of a first exemplary implementation of the architecture of FIG. 4 within a non-roaming E-UTRAN/5G network architecture according to the present disclosure.
- FIG. 4b is a functional block diagram of a second exemplary implementation of the architecture of FIG. 4 within a non-roaming E-UTRAN/5G network architecture according to the present disclosure.
- FIG. 4c is a functional block diagram of a first exemplary implementation of the architecture of FIG. 4 within a roaming E-UTRAN/5G network architecture according to the present disclosure.
- FIG. 5a is a functional block diagram of a first exemplary MSO/MNO network architecture useful in conjunction with various features described herein, wherein the MSO maintains the majority of 5G NR core infrastructure.
- FIG. 5b is a functional block diagram of a second exemplary MSO/MNO network architecture useful in conjunction with various features described herein, wherein the MNO maintains the majority of 5G NR core infrastructure.
- FIG. 6 is a functional block diagram illustrating a first exemplary embodiment of an HSS (Home Subscriber Service) and UDM (Unified Data Management), or HSS+UDM apparatus with PCI conflict resolution support, useful with various embodiments of the present disclosure.
- HSS Home Subscriber Service
- UDM Unified Data Management
- FIG. 7 is a functional block diagram illustrating a first exemplary embodiment of an enhanced 3GPP-compliant 5G NR gNB apparatus with PCI conflict resolution capability, useful with various embodiments of the present disclosure.
- the term“application” 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 XletTM that runs within the JavaTVTM environment.
- a CU refers without limitation to a centralized logical node within a wireless network infrastructure.
- 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 Fl interface connected with one or more DUs (e.g., gNB-DUs) defined below.
- gNB-CU 5G/NR gNB Central Unit
- 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.
- set-top boxes e.g., DSTBs
- gateways e.g., modems
- PCs personal computers
- minicomputers whether desktop, laptop, or otherwise
- mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablets,“phablets”, smartphones, and vehicle infotainment systems or portions thereof.
- “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), JavaTM (including J2ME, Java Beans, etc.) and the like.
- CORBA Common Object Request Broker Architecture
- JavaTM including J2ME, Java Beans, etc.
- a DU refers without limitation to a distributed logical node within a wireless network infrastructure.
- 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).
- gNB-DU 5G/NR gNB Distributed Unit
- One gNB-DU supports one or multiple cells, yet a given cell is supported by only one gNB-DU.
- the gNB-DU terminates the Fl interface connected with the gNB-CU.
- 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.
- 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.
- an operator e.g., an MSO
- MSO Mobility Management Entity
- 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.
- 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.
- LTE-U Long Term Evolution in unlicensed spectrum
- LTE-LAA Long Term Evolution, Licensed Assisted Access
- LTE-A Long Term Evolution Advanced
- 4G LTE Long Term Evolution
- WiMAX Worldwide Interoice over LTE
- VoLTE Voice over LTE
- 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.
- 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).
- DSPs digital signal processors
- RISC reduced instruction set computers
- CISC general-purpose processors
- microprocessors e.g., FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs).
- DSPs digital signal processors
- RISC reduced instruction set computers
- CISC general-purpose processors
- microprocessors gate arrays (e.g., FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processor
- MSO multiple systems operator
- 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.
- MNO mobile network operator
- WMAN e.g., 802.16
- MNO mobile network operator
- 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).
- HFC hybrid fiber coax
- 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.
- ATM 802.3, ATM, X.25, Frame Relay, 3 GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5GNR, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).
- 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.
- 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.
- 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.
- 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.
- 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).
- Wi-Fi Direct including inter alia , the“Wi-Fi Peer-to-Peer (P2P) Specification”, incorporated herein by reference in its entirety).
- 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.
- PLMNs mobile networks
- 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.
- the measurement reporting is configured to comply with 5G R-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.
- 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.
- each UE merely uses existing RF measurement reporting functions to provide the necessary data back to the serving gNB for PCI conflict resolution.
- wireless access networks e.g., 5GS and ECS
- a managed network of a service provider e.g., MSO and/or MNO networks
- RATs radio access technologies
- 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.
- FIGS. 3-3C various embodiments of the methods of, inter alia , cell identification and operating a wireless network, are shown and described in detail. It will be appreciated that while these methods are described primarily in the context of a 3GPP -based (i.e., E-UTRAN and 5G NR) architecture, the various methods are in no way so limited, and may be readily adapted and applied to other types or configurations of wireless network such as for instance MulteFireTM- based networks, such adaptation and application being within the skill level of the ordinary artisan given the present disclosure.
- 3GPP -based i.e., E-UTRAN and 5G NR
- FIG. 3 shows a first embodiment of the generalized method for cell identification according to the present disclosure.
- one or more candidate UE(s) for PCI confusion resolution are identified. As described in greater detail below, in one implementation, this identification is accomplished based on a mobility-related factor or determination.
- the cognizant gNB instructs the identified set of UEs from step 302 to perform Measurement Reports.
- the Measurement Reports are conducted taking the LBT (Listen Before Talk) protocol into account.
- 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.
- step 302 of the method 300 a mobility- related determination is performed.
- the gNB identifies at least some of the candidate set of UEs as requiring or not requiring application of the confusion resolution mechanism based on the presence or absence of a prescribed parameter (in one variant, the value‘Wo Mobility Require ’ or NMR is used, although other values and forms of parameter may be used with equal success.
- a prescribed parameter in one variant, the value‘Wo Mobility Require ’ or NMR is used, although other values and forms of parameter may be used with equal success.
- a prescribed parameter in one variant, the value‘Wo Mobility Require ’ or NMR is used, although other values and forms of parameter may be used with equal success.
- a prescribed parameter in one variant, the value‘Wo Mobility Require ’ or NMR is used, although other values and forms of parameter may be used with equal success.
- UE(s) such as those used for Fixed Wireless Access (FWA)
- FWA Fixed Wireless Access
- 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.
- the AMF Access and Mobility Management Function
- the procedure uses UE-associated signalling.
- the AMF accesses the UE/subscription data for the relevant UE (e.g., by accessing the global DB 402 at the HSS+UDM entity 401 discussed below), and inserts this accessed data into the relevant context message (e.g., CONTEXT SETUP REQUEST) transmitted to the cognizant gNB (step 314).
- the relevant context message e.g., CONTEXT SETUP REQUEST
- 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 Require ’ for that UE/user.
- UDM Unified Data Management
- 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.
- the term“mobility” refers more to intra-cell mobility, versus inter-cell mobility.
- 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.
- the device is immobile.
- 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.
- the gNB can apply different protocols to the different levels of mobility support needed; e.g., the method 300 above for NMR, another for l MR (e.g., a hybridization of the method of FIG. 3 and mobility-enabled approaches in scenarios where the UE or another gNB signals that it then requires mobility in that limited instance), and yet another for FMR scenarios.
- the parameter(s) of interest 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.
- the gNB upon receiving the context message from the AMF (step 316), analyzes the message and extracts the NMR value if present, and stores the NMR value for the duration of the UE’s session context (i.e., during RRC CONNECTED and RRC INAC IVE states) per step 318.
- the gNB may use the NMR data e.g., when deciding to request one or more UE(s) to perform Measurement Reporting, and correspondingly update white/black lists for Measurement Reporting if deemed necessary
- 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.
- step 304 of the method 300 of FIG. 3 is described.
- the cognizant gNB determines at least one“target” PCI, as well as a duration value specifying the duration for which the requested measurement is to be performed (i.e., in order to sufficiently collect required NCGI data from all PLMNs broadcasting the same PCI for a given frequency) per step 322.
- a gNB supports many UEs.
- the gNB Based on those UEs’ mobility state information already available the gNB (e.g., the NMR parameter), the gNB requests the identified sub-set of UEs to perform (or not perform, depending on the constitution of the sub-set as discussed supra) additional Measurement Reports to resolve PCI confusion. In one such approach, the gNB affirmatively instructs only those UE not having the NMR parameter associated to perform the Measurement Reports. In another approach, the gNB affirmatively instructs only those UE having the NMR parameter associated to not perform the Measurement Reports.
- the gNB affirmatively instructs only those UE having the NMR parameter associated to not perform the Measurement Reports.
- 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.
- LBT Listen Before Talk
- 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.
- step 324 of FIG. 3b includes the following ASN. l additions to the MeasObjectNR IE (information element which specifies information applicable for SS/PBCH block(s) intra/inter-frequency measurements or CSI-RS intra/inter-frequency measurements) to instruct the UE(s) on the requisite scan time (including flexibility to change as needed dynamically) - see Appendix I hereto: measReportLBTScanTime INTEGER
- OPTIONAL Time for which the TIE scans for all possible SSBs being broadcasted in the same PCI by different PLMNs
- 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 5ms, 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 5ms period, a TIE looking for the SSB should be able to read it.
- a physical medium e.g., an RF frequency
- NR requires tight time synchronization between the gNB and TIE
- an accurate timing source e.g., atomic clock
- the maximum COT (channel occupancy time) following a successful LBT procedure is lOms (see TS 37.213 vl5.l.O 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 lOms value, uses a l5ms total (5ms + lOms) time for the LIE to scan for all possible SSBs being broadcast in the same PCI, such as by different PLMNs. As such, the previously discussed ASN.
- the gNB then provides the identified LIE(s) from step 302 (FIG. 3) with the determined PCI and scan time values as above, which enables the LIE to scan the PCI(s) and return the generated data as part of the Measurement Report procedure.
- 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).
- the gNB further instructs the UE(s) to implement a second parameter relating to a prescribed maximum number of PLMNs to report on.
- the gNB assembles the extracted Measurement Report data from the directed UE(s) relating to all NCGI(s), in response to gNB’s PCI to NCGI resolution request. In one variant, this is performed on a per- PCI basis, although other schemes may be utilized consistent with the present disclosure.
- the gNB logic then evaluates the received data for each target PCI to determine whether conflicts are present.
- 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.
- 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.
- the parameter(s) of interest 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).
- the UE provides the parameter(s) (e.g., NMR ) within the UE-NR-Capability IE, which is included in UECapabilitylnformation message (the latter which is sent in response to UECapabilitylnquiry message).
- relevant portions of TS 38.331 may be modified as described below.
- the cognizant gNB 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.
- the UE-CapabilityRAT-ContainerList is used within the exemplary UECapability Information IE.
- the IE UE-CapabilityRAT-ContainerList contains a list of radio access technology specific capability containers.
- 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.
- the gNB may also utilize a second parameter to control the behavior of the UE conducting the measurement reporting.
- This second parameter as described in greater detail below, may be used in tandem with (or even in place of in somce circumstances) the previously described timing duration parameter(s).
- 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.
- OPTIONAL Maximum number of PLMNs for the same PCI for Measurement reports are to be generated by the EE
- Appendices III and IV hereto illustrate various embodiments of the use of the above value within the ASN.1 MeasObjectNR IE.
- the method proceeds similar to that of FIG. 3b described supra ; however, at step 323, the further gNB determines the maximum number of PLMNs (e.g., 5 as in the example above) for which measurement reporting is to be conducted by the EE.
- This determined value may be on a global basis (i.e., all EE), or individual to one or more EE within the broader population.
- the gNB instructs the relevant EE(s) with the target PCI value(s), duration(s), and also maximum PLMN number selected per step 323.
- 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 maxNrOfPI 1NsPerP( 7 ⁇ o Report 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).
- 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 PRC parameters are UE-specific, different UEs can be provided different values by the gNB given its knowledge of the topology, statistics, operationalconsiderations, 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.
- the present disclosure contemplates use of individual ones of the parmaters (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.
- a conjunction of both parameters may provide an optimal balance of UE power consumption obtaining the most accurate data regardingthe 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 maxNrOfPI NsPerPC 7 ⁇ o Re port.
- the PLMN- ID is reported when performing RSRQ/RSRP or other signal strength indicator (SSI) measurements, based on PCI reporting.
- SSI signal strength indicator
- 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.
- FIG. 4 shows one embodiment of a 5G NR-based architecture 400, including aspects as defined in 3GPP TS 23.501, according to the present disclosure.
- the architecture 400 includes a UDM-based data repository or database 402 of UE characterizing data (such as for instance the NMR and/or other parameters previously described) to be used consistent with the methods of FIGS. 3- 3C.
- the architecture also includes a PCI Conflict Resolution Entity (PCRE) 404, as well as a local characterizing database 406 for all or a subset of the gNBs (within the NG-RAN).
- PCRE PCI Conflict Resolution Entity
- all RAN include a PCRE 404 and database 406.
- gNBs supporting particular unlicensed spectrum functionality include the PCRE/database.
- gNBs expected to have significant PCI conflicts include the PCRE/database. It will be appreciated that any number of deployment configurations and scenarios may be utilized consistent with the present disclosure, the architecture 400 of FIG. 4 being merely exemplary.
- FIG. 4a is a functional block diagram of a first exemplary embodiment of an enhanced E-UTRAN/5G network architecture according to the present disclosure.
- the architecture 400 includes generally both a legacy or 4G/4.5G RAN 422 and a 5G-NR RAN (NG-RAN) 424, although it will be appreciated that configurations with different numbers of and/or other types of RANs may be utilized consistent with the present disclosure; e.g., a given PLMN may have multiple RANs including mixtures of legacy and next-generation technology, as well as unlicensed (e.g., ISM-band) and/or quasi-licensed (e.g., CBRS) apparatus and a capability associated therewith.
- the PLMN represented within the diagram is the home PLMN (HPLMN) of the 5G NR-U enabled UE.
- HPLMN home PLMN
- 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.
- 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.
- the global NMR database 402 here logically disposed within the HSS+LTDM functionality of the 5GC.
- the N8 interface as shown enables communication between the LTDM process (and hence the global DB 402) and the serving AMF 426 in support of the PCI confusion resolution functions described herein.
- the PCRE 404 and local NMR database 406 are disposed logically within the AMF function 446, and hence multiple CU/DU (gNBs) can be provided with the PCI conflict resolution function more centrally as opposed to the configuration of FIG. 4a.
- a client or local portion of the PCRE (PCRE ci ) 442 and server portion (PCRE s ) 444 are used, with the PCRE S performing the evaluation and determination logic of e.g., FIGS. 3-3c, and the PCRE d merely acting as an“implementation minion” process to in effect configure various UE with which it is in contact for Measurement Reporting (or no such reporting) as required.
- the PCRE S 444 is disposed within HSS+UDM of the UE’s home PLMN, while the client (PCRE ci ) 442 is disposed within the visited PLMN (i.e., within the CU/DU of the NG-RAN gNB(s)).
- the local NMR DB 406 is obviated in favor of a single global DB 402 at the HSS+UDM.
- an MSO e.g., cable or satellite network operator
- the MNO e.g., cellular service provider
- FIG. 5a illustrates a typical service provider network configuration useful with the features of the enhanced PCI conflict resolution apparatus and methods described herein, including the enhanced 3GPP architectures of FIGS. 4-4c.
- This service provider network 500 is used in one embodiment of the disclosure to provide backbone and backhaul from the service provider’s service nodes, such as HFC cable or FTTC/FTTH drops to different premises or venues/residences.
- service nodes such as HFC cable or FTTC/FTTH drops to different premises or venues/residences.
- NR 5G
- an MSO interface 532 to one or more MNO networks 511 such as those of an MVNO.
- the exemplary MNO/MVNO infrastructure or domain includes a number of 3GPP gNBs 544a-b and eNBs as shown, thereby providing 3GPP 4G/4.5G/5G coverage to authorized users of the MNO/MNVO network.
- 3GPP gNBs 544a-b and eNBs as shown, thereby providing 3GPP 4G/4.5G/5G coverage to authorized users of the MNO/MNVO network.
- this interface 532 supports the S5/S8/S6a 3GPP interfaces between the S-GW and P-GW (S8 is used when roaming between different operators, while S5 is network-internal).
- the TIE may include two radio transceivers (one for 3 GPP LTE, and one for 3 GPP 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.
- HSS+ETDM with global NMR DB 402 PGW, h-PCF/h-PCRF, AMF 426, v-PCF, v-SMF, and UPF entities of FIGS. 4-4c. While these entities are shown as part of the MSO“core” infrastructure portion in this embodiment, it will be appreciated as previously discussed that such entities each (i) may be distributed at two or more different/other locations within the MSO core or service domain(s); (ii) may be combined with each other or with other MSO infrastructure components (including those at the service domain), and (iii) may be virtualized as software/firmware processes within other components (such as MSO system servers, RAN infrastructure, etc.). Hence, the illustrated configuration of FIG. 5a is merely illustrative in this regard.
- FIG. 5a is characterized in the context of the embodiment of FIG. 4a (i.e., with the PCRE functionality logically and functionally contained within the gNBs of the MSO service domain, the architecture 500 may readily be adapted by those of ordinary skill given the present disclosure for other embodiments, including for example those of FIGS. 4b and 4c.
- 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.
- 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
- device-specific IDs e.g., gNB ID, Global gNB Identifier, NCGI, MAC address or the like
- 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.
- AMF ID Access and Mobility Management Function 426 shown in FIGS. 4-4c
- AMF ID Access and Mobility Management Function 426 shown in FIGS. 4-4c
- NCGI NR Cell Global Identifier
- NCI NR Cell Identity
- gNB ID gNB Identifier
- 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
- TAI Tracking Area identity
- S-NSSAI Single Network Slice Selection Assistance information
- the MSO network architecture 500 of FIG. 5a is particularly useful for the delivery of packetized content (e.g., encoded digital content carried within a packet or frame structure or protocol, such as video, audio, or voice data) consistent with the various aspects of the present disclosure.
- packetized content e.g., encoded digital content carried within a packet or frame structure or protocol, such as video, audio, or voice data
- the system of FIG. 5 may deliver Internet data and OTT (over-the-top) services to the end users (including those of the DU’s 506a-c) via the Internet protocol (IP) and TCP (i.e., over the 5G radio bearer), although other protocols and transport mechanisms of the type well known in the digital communication art may be substituted.
- IP Internet protocol
- TCP i.e., over the 5G radio bearer
- the network architecture 500 of FIG. 5 a generally includes one or more headends 507 in communication with at least one hub 517 via an optical ring 537.
- the distribution hub 517 is able to provide content to various“client” devices 509a, 506a- c, and gateway devices 560 as applicable, via an interposed network infrastructure 545.
- the various gNB components including the NR DU’s and CU’s and their constituent UE e ’s
- the CU 504 of a given gNB is physically disparate or removed from the locations of its constituent DU’s 506, and hence an interposed (e.g., wired, wireless, optical) PHY bearer is needed to communicate data between the DU’s and CU of a given gNB.
- the CU may be placed further toward the core of the MSO distribution network, while the various constituent DU’s are placed at the edge.
- both devices may be near the edge (and e.g., served by edge QAMs or RF carriers 540 as shown in FIG. 5a).
- the MSO infrastructure may be used to“backhaul” data from each device and communicate it to, via the MSO infrastructure, the other components, much as two geographically disparate customers of a given MSO might communicate data via their respective DOCSIS modems in their premises.
- Each component has an IP address within the network, and as such can be accessed (subject to the limitations of the architecture) by the other components.
- 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.”
- 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 FIG. 5a. This may also be “hybridized,” such as where one constituent DU is co-located (and potentially physically integrated) with the CU, while the remaining DU of that CU are geographically and physically distributed.
- various content sources 503, 503a are used to provide content to content servers 504, 505 and origin servers 521.
- content may be received from a local, regional, or network content library as discussed in co-owned U.S. Patent No. 8,997,136 entitled“APPARATUS AND METHODS FOR PACKETIZED CONTENT DELIVERY OVER A BANDWIDTH- EFFICIENT NETWORK”, which is incorporated herein by reference in its entirety.
- content may be received from linear analog or digital feeds, as well as third party content sources.
- Internet content sources 503a (such as e.g., a web server) provide Internet content to a packetized content origin server(s) 521.
- IP content may also be received at the origin server(s) 521, such as voice over IP (VoIP) and/or IPTV content.
- VoIP voice over IP
- IPTV content may also be received from subscriber and non-subscriber devices (e.g., a PC or smartphone-originated user made video).
- the network architecture 500 of FIG. 5a may further include a legacy multiplexer/encrypter/modulator (MEM; not shown).
- MEM multiplexer/encrypter/modulator
- the content server 504 and packetized content server 521 may be coupled via a LAN to a headend switching device 522 such as an 802.3z Gigabit Ethernet (or“10G”) device.
- a headend switching device 522 such as an 802.3z Gigabit Ethernet (or“10G”) device.
- the edge switch device 538 which may also comprise an 802.3z Gigabit Ethernet device
- the CMs 512 shown in FIG. 5a each service a premises or venue, such as a conference center or hospitality structure (e.g., hotel), which includes one or more DU nodes for provision of 5G NR services, and may also service WLAN (e.g., 802.11-2016 compliant Wi-Fi) nodes for WLAN access (e.g., within 2.4GHz ISM band), or even E-UTRAN femtocells, CBRS (Citizens Broadband Radio Service) nodes, or other such devices.
- WLAN e.g., 802.11-2016 compliant Wi-Fi
- E-UTRAN femtocells e.g., within 2.4GHz ISM band
- CBRS Cetizens Broadband Radio Service
- 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.
- so-called“OTT” content 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.
- 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
- user-plane data/traffic may also be routed and delivered apart from the CU.
- 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 El data interface, although other approaches may be used.
- 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).
- 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.
- different classes of DU 506 may be utilized.
- 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.
- 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.
- a unitary gNB-CU entity or device 504 as shown in FIG. 5 the present disclosure is in no way limited to such architectures.
- the techniques described herein may be implemented as part of a distributed or dis-aggregated or distributed CU entity (e.g., one wherein the user plane and control plane functions of the CU are dis- aggregated or distributed across two or more entities such as a CU-C (control) and CU-U (user)), and/or other functional divisions are employed.
- the individual DU’s 506 in FIGS. 5a and 5b communicate data and messaging with the CU 504 via interposed physical communication interfaces and logical interfaces which may include a user plane and control plane, and be embodied in prescribed protocols such as F1AP.
- one CU 504 is associated with one or more DU’s 506, yet a given DU is only associated with a single CU.
- the single CU 504 can be communicative with a single NG Core such as that operated by an MNO or MSO. Each NG Core may have multiple gNBs associated therewith.
- 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.
- 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.
- 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 FIGS. 4-5a.
- a given DU may act (i) solely as a DU (i.e., 5G NR-U PHY node) and operate outside of an E-UTRAN macrocell, or (ii) be physically co-located with an eNB or femtocell and provide NR coverage within a portion of the eNB macrocell coverage area, or (iii) be physically non-colocated with the eNB or femtocell, but still provide NR coverage within the macrocell coverage area.
- a DU i.e., 5G NR-U PHY node
- FIG. 5b is a functional block diagram of a second exemplary MSO/MNO network architecture 550, wherein the MNO maintains the majority of 5G NR core infrastructure, such as within the MNO core portion 552, which contains the 5G NR core components outside of the NG-RAN(s), the latter within the MSO service domain 554.
- FIG. 6 illustrates an exemplary configuration of an enhanced HSS+UDM 430 according to the present disclosure.
- the HSS+UDM 401 includes, inter alia , a processor apparatus or subsystem 602, a program memory module 604, mass storage 605 incorporating the parameter (e.g., NMR ) database 402 for served UE, HSS (Home Subscriber Server) and UDM (Unified Data Management) logic 606 including management of the foregoing database 402, one or more network interfaces 608.
- the parameter e.g., NMR
- HSS Home Subscriber Server
- UDM Unified Data Management
- 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 FIGS. 3-3c above), and other logical functions performed by the HSS+UDM as described elsewhere herein. Other embodiments may implement such functionality within dedicated hardware, logic, and/or specialized co- processors (not shown).
- memory 604 e.g., a non-transitory computer readable storage medium
- 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 FIGS. 3-3c above), and other logical functions performed by the HSS+UDM as described elsewhere
- the HSS+UDM DB controller logic 606 is a firmware or software module that, inter alia , communicates with a corresponding AMF (i.e., for setup for a given UE requesting access via a served NG-RAN with NR-U capability), and/or other upstream or backend entities such as those within the NG Core 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 FIG. 6 and the MSO backhaul (e.g., where the HSS+UDM is disposed within the MSO infrastructure).
- AAA authentication, authorization, and accounting
- the AAA servers whether locally maintained by the MSO or remotely by e.g., an MNO of the subscriber, are configured to provide services for, e.g., authorization and/or control of network subscribers (including roaming MNO“visitors” to the MSO RAN(s), and/or roaming MSO subscribers visiting an SPLMN of an MNO) for controlling access and enforcing policies, auditing usage, and providing the information necessary to bill for services.
- the AAA servers themselves may be used to supply NMR data or other similar context-related data necessary to support PCI conflict resolution according to the present disclosure.
- the HSS+UDM 401 is maintained by the MSO (see FIG. 5a) and is configured to utilize a non-public IP address within an IMS/Private Management Network“DMZ” of the MSO network.
- DMZs demilitarized zones
- so-called DMZs demilitarized zones
- DMZs demilitarized zones
- DMZs demilitarized zones
- FIG. 7 illustrates a block diagram of an exemplary embodiment of a NR-U enabled gNB apparatus, useful for operation in accordance with the present disclosure.
- the gNB (which may for instance take any of the forms shown in FIGS. 5a and 5b, including integrated CU 504 and DU 506, distributed CU/DU, etc.) includes, inter alia , a processor apparatus or subsystem 702, a program memory module 704, PCRE logic 706 (here implemented as software or firmware operative to execute on the processor 702), and wireless interfaces 710, 720 for communications with the relevant UE’s (e.g., 4G/4.5G E-UTRAN and 5G-NR RAN, respectively).
- the relevant UE’s e.g., 4G/4.5G E-UTRAN and 5G-NR RAN, respectively.
- 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.
- the antenna(s) 715, 725 of the radios of the gNB(s) may include multiple spatially diverse individual elements in e.g., a MIMO- or MISO-type configuration, such that spatial diversity of the received signals can be utilized.
- a phased array or similar arrangement can be used for spatial resolution within the environment, such as based on time delays associated with signals received by respective elements.
- 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.
- DMA direct memory access
- 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
- 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 FIGS. 3 -3c herein, in the form of software or firmware that implements the various functions).
- processors 704 e.g., the logic of the PCRE including enhanced functions of PCI conflict resolution and operation according to the methods of FIGS. 3 -3c herein, in the form of software or firmware that implements the various functions.
- Other embodiments may implement such functionality within dedicated hardware, logic, and/or specialized co-processors (not shown).
- 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).
- application program interfaces 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).
- ThresholdNR OPTIONAL 20 absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R absThreshCSI -RS -Consolidation ThresholdNR OPTIONAL, -- Need R nrofSS -BlocksToAverage INTEGER (2.. maxNrofSS -BlocksToAverage ) OPTIONAL, -- Need R nrofCSI-RS-ResourcesToAverage INTEGER (2.. maxNrofCSI -RS-ResourcesToAverage) OPTIONAL, -- Need R quantityConfigIndex INTEGER (1.. maxNrofQuantityConfig) ,
- blackCellsToRemoveList PCI -RangelndexList OPTIONAL -- Need N blackCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, -- Need N whiteCellsToRemoveList PCI -RangelndexList OPTIONAL Need N
- ThresholdNR : : SEQUENCE!
- thresholdRSRP RSRP-Range OPTIONAL Need R thresholdRSRQ RSRQ-Range OPTIONAL, Need R
- CellsToAddModList SEQUENCE (SIZE ( 1.. maxNrofCellMeas ) ) OF CellsToAddMod
- UE-NR-Capability-1530 SEQUENCE ⁇
- ThresholdNR OPTIONAL 20 absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R absThreshCSI -RS -Consolidation ThresholdNR OPTIONAL, -- Need R nrofSS -BlocksToAverage INTEGER (2.. maxNrofSS -BlocksToAverage ) OPTIONAL, -- Need R nrofCSI-RS-ResourcesToAverage INTEGER (2.. maxNrofCSI -RS-ResourcesToAverage OPTIONAL, -- Need R quantityConfigIndex INTEGER (1.. maxNrofQuantityConfig) ,
- freqBandIndicatorNR-vl530 FreqBandlndicatorNR OPTIONAL, -- Need R measCycleSCell -vl530 ENUMERATED ⁇ sf!60, sf256, sf320, sf512,sf640, sf!024, sfl280 ⁇ OPTIONAL Need R
- ThresholdNR : : SEQUENCE ⁇
- MeasResultListNR :: SEQUENCE (SIZE (1.. maxCellReport ) ) OF MeasResultNR
- MeasResultListEUTRA SEQUENCE (SIZE (1.. maxCellReport ) ) OF MeasResultEUTRA
- MeasResultEUTRA SEQUENCE ⁇
- cgi-info-5GC SEQUENCE (SIZE ( 1..maxPLMN) ) OF CellAccessRelatedInfo-EUTRA-5GC OPTIONAL, freqBandlndicator FreqBandlndicatorEUTRA,
- MultiBandlnfoListEUTRA SEQUENCE (SIZE (1.. maxMultiBands ) ) OF FreqBandlndicatorEUTRA
- ResultsPerSSB- IndexList SEQUENCE (SIZE (1.. maxNrofIndexesToReport2 ) ) OF ResultsPerSSB-Index
- ResultsPerCSI -RS - IndexList SEQUENCE (SIZE (1.. maxNrofIndexesToReport2 ) ) OF ResultsPerCSI -RS - Index
- measCycleSCell -vl530 ENUMERATED ⁇ sfl60, sf256, sf320, sf512, sf640, sfl024, sfl280 ⁇ OPTIONAL Need R
- ThresholdNR : : SEQUENCE!
- thresholdRSRP RSRP-Range OPTIONAL -- Need R thresholdRSRQ RSRQ-Range OPTIONAL, -- Need R
- CellsToAddModList SEQUENCE (SIZE ( 1.. maxNrofCellMeas ) ) OF CellsToAddMod
- BlockPCIOfCertainPLMNs : : SEQUENCE ⁇
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Apparatus and methods for physical cell identification within one or more wireless networks. In one embodiment, 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 (e.g., according to 3 GPP 5G NR-U technology) are resolved. 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 to detect any such PCI-based conflicts.
Description
APPARATUS AND METHODS FOR CELL IDENTIFICATION
IN WIRELESS NETWORKS
Priority
This application claims priority to U.S. Provisional Patent Application Serial Nos. 62/745,065 and 62/752,002 filed October 12, 2018 and October 29, 2018, respectively, each entitled “APPARATUS AND METHODS FOR CELL IDENTIFICATION IN WIRELESS NETWORKS,” each incorporated herein by reference in its entirety.
Background
Technological Field
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. Description of Related Technology
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:
Table 1
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:
Table 2
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:
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. FIG. 1 shows the 5G architecture 100 as defined in 3GPP TS 23.501 (Fig. 4.2.3-1 thereof).
An existing 3GPP LTE/LTE-A/EPC (i.e., 4G or 4.5G system) cannot be updated to support 5G; hence, 3 GPP has also defined interworking procedures between such 4G/4.5G and 5G systems. FIG. 2a shows the architecture 200 for interworking between 5GS and EPC/E-UTRAN as defined in TS 23.501 (Fig. 4.3.1-1 thereof), specifically the non-roaming architecture for interworking between the 5GS and the EPC/E-UTRAN. Two different RAN technologies are supported; i.e., E- UTRAN (4G/4.5G) 202, and 5G (NG-RAN) 204. FIG. 2b shows a roaming architecture counterpart (i.e., with HPLMN and visited network (VPLMN).
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 FIGS. l-2b) has many cells. But since the PCIs are rather limited in number, the notion of an ECGI (E-UTRAN Cell Global Identifier; LTE), and NCGI (NR Cell Global Identifier; 5G NR) was introduced, wherein a PLMN-ID is used in addition to the PCI to uniquely identify a given cell within a given PLMN (and also across it; i.e., inter-PLMN). The ECGI is constructed from the MCC (Mobile Country Code), MNC (Mobile Network Code) and the ECI (E-UTRAN Cell Identifier), while the NCGI is constructed from the PLMN identity to which the cell belongs and the NR Cell Identity (NCI) of the cell.
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 FIG. 2c, many different network operators (e.g., PLMN providers) could use same PCI at a given frequency within both the licensed and the unlicensed spectrum to identify their respective cells (i.e., PCIL and PCIu, respectively as shown in FIG. 2c). Given the nature of spectrum, coordination among such PLMN providers cannot be assumed, and in fact given the ad hoc nature of unlicensed spectrum, it is likely that coordination will not exist.
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.
Summary
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 UECapabilitylnformation message (the latter sent in response to UECapability Inquiry 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 ebodiment, 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.
Brief Description of the Drawings
FIG. 1 is a functional block diagram of a prior art 5G system architecture and the various components thereof.
FIG. 2a is a block diagram showing the extant architecture for interworking between 5GS and EPC/E-UTRAN as defined in 3 GPP TS 23.501 (Fig. 4.3.1-1 thereof), specifically the non-roaming architecture for interworking between the 5GS
and the EPC/E-UTRAN.
FIG. 2b shows a prior art roaming architecture counterpart to the architecture of FIG. 2a (i.e., with HPLMN and visited network (VPLMN)).
FIG. 2c shows a graphical representation of the PCI“confusion” problem between licensed and unlicensed spectrum networks within the exemplary 5G NR context.
FIG. 3 is a logical flow diagram illustrating one embodiment of a generalized method of PCI conflict resolution according to the present disclosure.
FIG. 3a is a logical flow diagram illustrating one embodiment of user device set identification within the generalized method of FIG. 3.
FIG. 3b is a logical flow diagram illustrating one embodiment of user device measurement reporting within the generalized method of FIG. 3.
FIG. 3c is a logical flow diagram illustrating a second embodiment of user device measurement reporting within the generalized method of FIG. 3.
FIG. 3d is a logical flow diagram illustrating one embodiment of whitelist/blacklist updating based on measurement reporting, within the generalized method of FIG. 3.
FIG. 4 is a functional block diagram of a first exemplary embodiment of an enhanced 5G NR network architecture according to the present disclosure.
FIG. 4a is a functional block diagram of a first exemplary implementation of the architecture of FIG. 4 within a non-roaming E-UTRAN/5G network architecture according to the present disclosure.
FIG. 4b is a functional block diagram of a second exemplary implementation of the architecture of FIG. 4 within a non-roaming E-UTRAN/5G network architecture according to the present disclosure.
FIG. 4c is a functional block diagram of a first exemplary implementation of the architecture of FIG. 4 within a roaming E-UTRAN/5G network architecture according to the present disclosure.
FIG. 5a is a functional block diagram of a first exemplary MSO/MNO network architecture useful in conjunction with various features described herein, wherein the MSO maintains the majority of 5G NR core infrastructure.
FIG. 5b is a functional block diagram of a second exemplary MSO/MNO network architecture useful in conjunction with various features described herein,
wherein the MNO maintains the majority of 5G NR core infrastructure.
FIG. 6 is a functional block diagram illustrating a first exemplary embodiment of an HSS (Home Subscriber Service) and UDM (Unified Data Management), or HSS+UDM apparatus with PCI conflict resolution support, useful with various embodiments of the present disclosure.
FIG. 7 is a functional block diagram illustrating a first exemplary embodiment of an enhanced 3GPP-compliant 5G NR gNB apparatus with PCI conflict resolution capability, useful with various embodiments of the present disclosure.
Figures 3-7 © Copyright 2018-2019 Charter Communications Operating, LLC. All rights reserved. Other Figures © Copyright of their respective copyright holders.
Detailed Description
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 Fl 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 Fl 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, 3 GPP, 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 R-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 LIE 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 FIGS. 3-3C, various embodiments of the methods of, inter alia , cell identification and operating a wireless network, are shown and described in detail. It will be appreciated that while these methods are described primarily in the context of a 3GPP -based (i.e., E-UTRAN and 5G NR) architecture, the various methods are in no way so limited, and may be readily adapted and applied to other types or configurations of wireless network such as for instance MulteFire™- based networks, such adaptation and application being within the skill level of the ordinary artisan given the present disclosure.
FIG. 3 shows a first embodiment of the generalized method for cell identification according to the present disclosure. Per step 302 of the method 300, one or more candidate UE(s) for PCI confusion resolution are identified. As described in greater detail below, in one implementation, this identification is accomplished based on a mobility-related factor or determination.
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 FIG. 3a, one particular implementation of step 302 of the method 300 is shown. Specifically, within step 302 of the method 300, a mobility- related determination is performed. Specifically, the gNB identifies at least some of the candidate set of UEs as requiring or not requiring application of the confusion resolution mechanism based on the presence or absence of a prescribed parameter (in one variant, the value‘Wo Mobility Require ’ or NMR is used, although other values and forms of parameter may be used with equal success. Specifically, for certain UE(s)
such as those used for Fixed Wireless Access (FWA), no mobility scenarios exist and hence such scenarios need not be supported. If a given gNB can identify such UE(s), then it can request the identified UE(s) to not perform Measurement Reports for certain PCI(s).
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 FIG. 3 a, the AMF accesses the UE/subscription data for the relevant UE (e.g., by accessing the global DB 402 at the HSS+UDM entity 401 discussed below), and inserts this accessed data into the relevant context message (e.g., CONTEXT SETUP REQUEST) transmitted to the cognizant gNB (step 314).
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 Require ’ 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 l MR (e.g., a hybridization of the method of FIG. 3 and mobility-enabled approaches in scenarios where the UE or another gNB signals that it then requires mobility in that limited instance), and yet another for FMR scenarios.
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 FIG. 3a, the gNB, upon receiving the context message from the AMF (step 316), analyzes the message and extracts the NMR value if present, and stores the NMR value for the duration of the UE’s session context (i.e., during RRC CONNECTED and RRC INAC IVE states) per step 318. As described in greater detail below, the gNB may use the NMR data e.g., when deciding to request one or more UE(s) to perform Measurement Reporting, and correspondingly update white/black lists for Measurement Reporting if deemed necessary
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 FIG. 3b, one implementation of step 304 of the method 300 of FIG. 3 is described. Specifically, per step 320, the cognizant gNB determines at least one“target” PCI, as well as a duration value specifying the duration for which the requested measurement is to be performed (i.e., in order to sufficiently collect required NCGI data from all PLMNs broadcasting the same PCI for a given frequency) per step 322. As noted, for a given cell, a gNB supports many UEs. Based on those UEs’ mobility state information already available the gNB (e.g., the NMR parameter), the gNB requests the identified sub-set of UEs to perform (or not perform, depending on the constitution of the sub-set as discussed supra) additional Measurement Reports to resolve PCI confusion. In one such approach, the gNB affirmatively instructs only those UE not having the NMR parameter associated to perform the Measurement Reports. In another approach, the gNB affirmatively instructs only those UE having the NMR parameter associated to not perform the Measurement Reports.
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 FIG. 3b includes the following ASN. l additions to the MeasObjectNR IE (information element which specifies information applicable for SS/PBCH block(s) intra/inter-frequency
measurements or CSI-RS intra/inter-frequency measurements) to instruct the UE(s) on the requisite scan time (including flexibility to change as needed dynamically) - see Appendix I hereto: measReportLBTScanTime INTEGER
(XX..maxMeasRepPCIScanTime) OPTIONAL— Time for which the TIE scans for all possible SSBs being broadcasted in the same PCI by different PLMNs
maxMeasRepPCIScanTime INTEGER : := YY
(where YY is the Maximum time (in ms) for which a given PCI is scanned)
As a brief aside, in 5GNR, 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 5ms, 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 5ms period, a TIE looking for the SSB should be able to read it.
In that NR requires tight time synchronization between the gNB and TIE, 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 lOms (see TS 37.213 vl5.l.O 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 lOms value, uses a l5ms total (5ms + lOms) time for the LIE to scan for all possible SSBs being broadcast in the same PCI, such as by different PLMNs. As such, the previously discussed ASN. l additions to th Q MeasObjectNR IE in such implementations can be configured with values of XX and YY of 5ms and 15 ms, respectively - that is: measReportLB TScan Time INTEGER
(5..maxMeasRepPCIScanTime) OPTIONAL— Need R maxMeasRepPCIScanTime INTEGER ::= 15
Hence, per step 324 of FIG. 3b, the gNB then provides the identified LIE(s) from step 302 (FIG. 3) with the determined PCI and scan time values as above, which enables the LIE to scan the PCI(s) and return the generated data as part of the Measurement Report procedure.
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 FIG. 3c), the gNB further instructs the UE(s) to implement a second parameter relating to a prescribed maximum number of PLMNs to report on.
Referring now to FIG. 3d, one implementation of the method step 306 of FIG. 3 is now described in detail. As shown, per step 330, the gNB assembles the extracted Measurement Report data from the directed UE(s) relating to all NCGI(s), in response to gNB’s PCI to NCGI resolution request. In one variant, this is performed on a per- PCI basis, although other schemes may be utilized consistent with the present disclosure.
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. l PCI-Range IE is provided per one embodiment of the present disclosure to support such additional specificity:
Modified PCI-Ranse Information Element
- ASN1 START
- TAG-PCI-RANGE-START
PCI-Range SEQUENCE {
start PhysCellld,
range ENUMERATED {n4, n8, nl2, nl6, n24, n32, n48, n64, n84,
n96, n!28, nl68, n252, n504, nl008,sparel} OPTIONAL -
Need S
nrCellld CellGloballdNR OPTIONAL— PCIs of specific PLMNs for which
Measurements Reports are to be disabled
}
CellGloballdNR ::= SEQUENCE {
plmn-Identity PLMN-Identity,
cellldentity Cellldentity
}
- TAG-PCI-RANGE-STOP
- ASN1STOP
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 UECapabilitylnformation message (the latter which is sent in response to UECapabilitylnquiry 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 FIG. 3c), the gNB may also utilize a second parameter to control the behavior of the UE conducting the measurement reporting. This second parameter, as described in greater detail below, may be used in tandem with (or even in place of in somce circumstances) the previously described timing duration parameter(s).
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 the PLMN search. Specifically, in one implementation, an addition to the ASN. l/TS 38.331 MeasObjectNR IE is used as shown below:
maxPEMNsPerPCIToReport INTEGER
( 1 ..maxNrOfPlMNsP rP JToReport.) OPTIONAL— Maximum number of PLMNs for the same PCI for Measurement reports are to be generated by the EE
In one implementation, the constant maxNrOfPlMNsP rPC 7 Ί o Re port is defined as follows: maxNrOfPlMNsPerPC 77 o Re port 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: blackCellsToAddModList
BlockPCIOfCertainPLMNs blackCellsToRemoveList
BlockPCIOfCertainPLMNs
Note also that in Appendix IV, several new elements have been added, including e.g., the following:
BlockPCI OfCertainPLMNs. SEQUENCE {
cellldentity Cellldentity plmn-Identity PEMN-Identity
Referring again to FIG. 3c, the method proceeds similar to that of FIG. 3b described supra ; however, at step 323, the further gNB determines the maximum number of PLMNs (e.g., 5 as in the example above) for which measurement reporting is to be conducted by the EE. This determined value may be on a global basis (i.e., all EE), or individual to one or more EE within the broader population.
Per step 325, the gNB instructs the relevant EE(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 maxNrOfPI 1NsPerP( 7 Ί o Report 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 PRC parameters are UE-specific, different UEs can be provided different values by the gNB given its knowledge of the topology, statistics, operationalconsiderations, 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 parmaters (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 regardingthe 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 maxNrOfPI NsPerPC 7 Ί o Re port.
In yet another embodiment of the disclosure, rather than use of CGI reporting - e.g., cgi-Info E 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 -
FIG. 4 shows one embodiment of a 5G NR-based architecture 400, including aspects as defined in 3GPP TS 23.501, according to the present disclosure. Specifically, as shown, the architecture 400 includes a UDM-based data repository or database 402 of UE characterizing data (such as for instance the NMR and/or other parameters previously described) to be used consistent with the methods of FIGS. 3- 3C. The architecture also includes a PCI Conflict Resolution Entity (PCRE) 404, as well as a local characterizing database 406 for all or a subset of the gNBs (within the NG-RAN). For example, in one scenario, all RAN (and their gNBs) include a PCRE 404 and database 406. In another scenario, only gNBs supporting particular
unlicensed spectrum functionality include the PCRE/database. In yet another scenario, gNBs expected to have significant PCI conflicts (e.g., by virtue of having a large unlicensed footprint or presence nearby or overlapping within the RAN coverage area) include the PCRE/database. It will be appreciated that any number of deployment configurations and scenarios may be utilized consistent with the present disclosure, the architecture 400 of FIG. 4 being merely exemplary.
FIG. 4a is a functional block diagram of a first exemplary embodiment of an enhanced E-UTRAN/5G network architecture according to the present disclosure. Specifically, as shown in FIG. 4a, the architecture 400 includes generally both a legacy or 4G/4.5G RAN 422 and a 5G-NR RAN (NG-RAN) 424, although it will be appreciated that configurations with different numbers of and/or other types of RANs may be utilized consistent with the present disclosure; e.g., a given PLMN may have multiple RANs including mixtures of legacy and next-generation technology, as well as unlicensed (e.g., ISM-band) and/or quasi-licensed (e.g., CBRS) apparatus and a capability associated therewith. In the illustrated embodiment, the PLMN represented within the diagram is the home PLMN (HPLMN) of the 5G NR-U enabled UE.
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+LTDM functionality of the 5GC. The N8 interface as shown enables communication between the LTDM 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 FIG. 4b, the PCRE 404 and local NMR database 406 are disposed logically within the AMF function 446, and hence multiple CU/DU (gNBs) can be provided with the PCI conflict resolution function more centrally as opposed to the configuration of FIG. 4a. In order for each gNB to receive and process the NMR data, a client or local portion of the PCRE (PCREci) 442 and server portion (PCREs) 444 are used, with the PCRES performing the evaluation and determination
logic of e.g., FIGS. 3-3c, and the PCREd merely acting as an“implementation minion” process to in effect configure various UE with which it is in contact for Measurement Reporting (or no such reporting) as required.
In the architecture 460 of FIG. 4c, the PCRES 444 is disposed within HSS+UDM of the UE’s home PLMN, while the client (PCREci) 442 is disposed within the visited PLMN (i.e., within the CU/DU of the NG-RAN gNB(s)). The local NMR DB 406 is obviated in favor of a single global DB 402 at the HSS+UDM.
As discussed with respect to FIGS. 5a and 5b below, depending on the division of ownership/operational responsibility between the NR (licensed) and NR-U (unlicensed) infrastructure, various combinations of component placement and configuration are possible in supporting the PCI conflict resolution functionality. For instance, in one variant, an MSO (e.g., cable or satellite network operator) may maintain NG-RAN functionality within their service domain (such as via their own deployed“standalone” or SA 5G NR-U enabled gNBs, as well as other unlicensed and/or quasi-licensed devices such as Wi-Fi APs, CBRS CBSDs, etc., with which the NR-U functionality must co-exist. Alternatively, in another variant, the MNO (e.g., cellular service provider) may maintain all infrastructure (including the PCI conflict resolution enabled gNBs and the various NMR databases), and merely lease or otherwise enable customers of the MSO to access the MNO infrastructure.
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 -
FIG. 5a illustrates a typical service provider network configuration useful with the features of the enhanced PCI conflict resolution apparatus and methods described herein, including the enhanced 3GPP architectures of FIGS. 4-4c. This service provider network 500 is used in one embodiment of the disclosure to provide backbone and backhaul from the service provider’s service nodes, such as HFC cable or FTTC/FTTH drops to different premises or venues/residences. For example, one or more stand-alone or embedded DOCSIS cable modems (CMs) 512 are in data
communication with the various NR (5G) architecture components (e.g., DU’s and CU’s) so as to provide two-way data communication to the served components.
Also provided within the architecture 500 of FIG. 5 is an MSO interface 532 to one or more MNO networks 511, such as those of an MVNO. The exemplary MNO/MVNO infrastructure or domain includes a number of 3GPP gNBs 544a-b and eNBs as shown, thereby providing 3GPP 4G/4.5G/5G coverage to authorized users of the MNO/MNVO network. These components (and others needed to support the E- UTRAN and 5G RAN in the architecture of e.g., FIG. 4a, such as the SGW and MME/MMEe - not shown in FIG. 5) interface with the MSO-domain (and ultimately the HSS+ETDM with global NMR DB) via e.g., a data interface 550 to the MSO backbone 531. In one embodiment, this interface 532 supports the S5/S8/S6a 3GPP interfaces between the S-GW and P-GW (S8 is used when roaming between different operators, while S5 is network-internal).
The TIE may include two radio transceivers (one for 3 GPP LTE, and one for 3 GPP 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 FIG. 5a are the HSS+ETDM with global NMR DB 402, PGW, h-PCF/h-PCRF, AMF 426, v-PCF, v-SMF, and UPF entities of FIGS. 4-4c. While these entities are shown as part of the MSO“core” infrastructure portion in this embodiment, it will be appreciated as previously discussed that such entities each (i) may be distributed at two or more different/other locations within the MSO core or service domain(s); (ii) may be combined with each other or with other MSO infrastructure components (including those at the service domain), and (iii) may be virtualized as software/firmware processes within other components (such as MSO system servers, RAN infrastructure, etc.). Hence, the illustrated configuration of FIG. 5a is merely illustrative in this regard.
Moreover, it will be recognized that while the architecture 500 of FIG. 5a is characterized in the context of the embodiment of FIG. 4a (i.e., with the PCRE functionality logically and functionally contained within the gNBs of the MSO service domain, the architecture 500 may readily be adapted by those of ordinary skill given the present disclosure for other embodiments, including for example those of FIGS. 4b and 4c.
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 FIGS. 4-4c);
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 FIG. 5a is particularly useful for the delivery of packetized content (e.g., encoded digital content carried within a packet or
frame structure or protocol, such as video, audio, or voice data) consistent with the various aspects of the present disclosure. In addition to on-demand and broadcast content (e.g., live video programming), the system of FIG. 5 may deliver Internet data and OTT (over-the-top) services to the end users (including those of the DU’s 506a-c) via the Internet protocol (IP) and TCP (i.e., over the 5G radio bearer), although other protocols and transport mechanisms of the type well known in the digital communication art may be substituted.
The network architecture 500 of FIG. 5 a generally includes one or more headends 507 in communication with at least one hub 517 via an optical ring 537. The distribution hub 517 is able to provide content to various“client” devices 509a, 506a- c, and gateway devices 560 as applicable, via an interposed network infrastructure 545. It will be appreciated from examination of FIG. 5a that the various gNB components (including the NR DU’s and CU’s and their constituent UEe’s) may each act as a“client” device of the network. For example, in many installations, the CU 504 of a given gNB is physically disparate or removed from the locations of its constituent DU’s 506, and hence an interposed (e.g., wired, wireless, optical) PHY bearer is needed to communicate data between the DU’s and CU of a given gNB. In one such architecture, the CU may be placed further toward the core of the MSO distribution network, while the various constituent DU’s are placed at the edge. Alternatively, both devices may be near the edge (and e.g., served by edge QAMs or RF carriers 540 as shown in FIG. 5a). In both cases, the MSO infrastructure may be used to“backhaul” data from each device and communicate it to, via the MSO infrastructure, the other components, much as two geographically disparate customers of a given MSO might communicate data via their respective DOCSIS modems in their premises. Each component has an IP address within the network, and as such can be accessed (subject to the limitations of the architecture) by the other components.
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 FIG. 5a. This may also be “hybridized,” such as where one constituent DU is co-located (and potentially physically integrated) with the CU, while the remaining DU of that CU are
geographically and physically distributed.
In the MSO network 500 of FIG. 5a, various content sources 503, 503a are used to provide content to content servers 504, 505 and origin servers 521. For example, content may be received from a local, regional, or network content library as discussed in co-owned U.S. Patent No. 8,997,136 entitled“APPARATUS AND METHODS FOR PACKETIZED CONTENT DELIVERY OVER A BANDWIDTH- EFFICIENT NETWORK”, which is incorporated herein by reference in its entirety. Alternatively, content may be received from linear analog or digital feeds, as well as third party content sources. Internet content sources 503a (such as e.g., a web server) provide Internet content to a packetized content origin server(s) 521. Other IP content may also be received at the origin server(s) 521, such as voice over IP (VoIP) and/or IPTV content. Content may also be received from subscriber and non-subscriber devices (e.g., a PC or smartphone-originated user made video).
The network architecture 500 of FIG. 5a may further include a legacy multiplexer/encrypter/modulator (MEM; not shown). In the present context, the content server 504 and packetized content server 521 may be coupled via a LAN to a headend switching device 522 such as an 802.3z Gigabit Ethernet (or“10G”) device. For downstream delivery via the MSO infrastructure (i.e., QAMs), video and audio content is multiplexed at the headend 507 and transmitted to the edge switch device 538 (which may also comprise an 802.3z Gigabit Ethernet device) via the optical ring 537.
In one implementation, the CMs 512 shown in FIG. 5a each service a premises or venue, such as a conference center or hospitality structure (e.g., hotel), which includes one or more DU nodes for provision of 5G NR services, and may also service WLAN (e.g., 802.11-2016 compliant Wi-Fi) nodes for WLAN access (e.g., within 2.4GHz ISM band), or even E-UTRAN femtocells, CBRS (Citizens Broadband Radio Service) nodes, or other such devices.
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 El 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 FIG. 5, the present disclosure is in no way limited to such architectures. For example, the techniques described herein
may be implemented as part of a distributed or dis-aggregated or distributed CU entity (e.g., one wherein the user plane and control plane functions of the CU are dis- aggregated or distributed across two or more entities such as a CU-C (control) and CU-U (user)), and/or other functional divisions are employed.
For instance, the individual DU’s 506 in FIGS. 5a and 5b communicate data and messaging with the CU 504 via interposed physical communication interfaces and logical interfaces which may include a user plane and control plane, and be embodied in prescribed protocols such as F1AP. In one embodiment, one CU 504 is associated with one or more DU’s 506, yet a given DU is only associated with a single CU. Likewise, the single CU 504 can be communicative with a single NG Core such as that operated by an MNO or MSO. Each NG Core may have multiple gNBs associated therewith.
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 FIGS. 4-5a. For instance, a given DU may act (i) solely as a DU (i.e., 5G NR-U PHY node) and operate outside of an E-UTRAN macrocell, or (ii) be physically co-located with an eNB or femtocell and provide NR coverage within a portion of the eNB macrocell coverage area, or (iii) be physically
non-colocated with the eNB or femtocell, but still provide NR coverage within the macrocell coverage area.
Moreover, the DU/CU architectures set forth in co-owned and co-pending U.S. Patent Application Serial No 15/945,657 filed April 4, 2018 and entitled “APPARATUS AND METHODS FOR CELL ACTIVATION IN WIRELESS NETWORKS,” incorporated herein by reference in its entirety, may be used consistent with the various aspects of the present disclosure.
FIG. 5b is a functional block diagram of a second exemplary MSO/MNO network architecture 550, wherein the MNO maintains the majority of 5G NR core infrastructure, such as within the MNO core portion 552, which contains the 5G NR core components outside of the NG-RAN(s), the latter within the MSO service domain 554.
HSS+UDM Apparatus -
FIG. 6 illustrates an exemplary configuration of an enhanced HSS+UDM 430 according to the present disclosure. As shown, the HSS+UDM 401 includes, inter alia , a processor apparatus or subsystem 602, a program memory module 604, mass storage 605 incorporating the parameter (e.g., NMR ) database 402 for served UE, HSS (Home Subscriber Server) and UDM (Unified Data Management) logic 606 including management of the foregoing database 402, one or more network interfaces 608.
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 FIGS. 3-3c above), and other logical functions performed by the HSS+UDM as described elsewhere herein. Other embodiments may implement such functionality within dedicated hardware, logic, and/or specialized co- processors (not shown). The HSS+UDM DB controller logic 606 is a firmware or software module that, inter alia , communicates with a corresponding AMF (i.e., for setup for a given UE requesting access via a served NG-RAN with NR-U capability), and/or other upstream or backend entities such as those within the NG Core in some embodiments.
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 FIG. 6 and the MSO backhaul (e.g., where the HSS+UDM is disposed within the MSO infrastructure). The AAA servers, whether locally maintained by the MSO or remotely by e.g., an MNO of the subscriber, are configured to provide services for, e.g., authorization and/or control of network subscribers (including roaming MNO“visitors” to the MSO RAN(s), and/or roaming MSO subscribers visiting an SPLMN of an MNO) for controlling access and enforcing policies, auditing usage, and providing the information necessary to bill for services. As such, the AAA servers themselves may be used to supply NMR data or other similar context-related data necessary to support PCI conflict resolution according to the present disclosure.
In one exemplary embodiment, the HSS+UDM 401 is maintained by the MSO (see FIG. 5a) and is configured to utilize a non-public IP address within an IMS/Private Management Network“DMZ” of the MSO network. As a brief aside, so- called DMZs (demilitarized zones) within a network are physical or logical sub- networks that separate an internal LAN, WAN, PAN, or other such network from other untrusted networks, usually the Internet. External-facing servers, resources and services are disposed within the DMZ so they are accessible from the Internet, but the rest of the internal MSO infrastructure remains unreachable or partitioned. This
provides an additional layer of security to the internal infrastructure, as it restricts the ability of surreptitious entities or processes to directly access internal MSO servers and data via the untrusted network, such as via a MME or AMF“spoof’ or MITM attack whereby an attacker might attempt to hijack one or more functional entities to obtain data from the corresponding HSS+UDM. gNB Apparatus -
FIG. 7 illustrates a block diagram of an exemplary embodiment of a NR-U enabled gNB apparatus, useful for operation in accordance with the present disclosure.
In one exemplary embodiment as shown, the gNB (which may for instance take any of the forms shown in FIGS. 5a and 5b, including integrated CU 504 and DU 506, distributed CU/DU, etc.) includes, inter alia , a processor apparatus or subsystem 702, a program memory module 704, PCRE logic 706 (here implemented as software or firmware operative to execute on the processor 702), and wireless interfaces 710, 720 for communications with the relevant UE’s (e.g., 4G/4.5G E-UTRAN and 5G-NR RAN, respectively).
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 FIG. 7, the antenna(s) 715, 725 of the radios of the gNB(s) may include multiple spatially diverse individual elements in e.g., a MIMO- or MISO-type configuration, such that spatial diversity of the received signals can be utilized. Moreover, a phased array or similar arrangement can be used for spatial resolution within the environment, such as based on time delays associated with signals received by respective elements.
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 FIGS. 3 -3c herein, in the form of software or firmware that implements the various functions). Other embodiments may implement such functionality within dedicated hardware, logic, and/or specialized co-processors (not shown).
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).
APPENDIX I - MODIFIED NR ASN.l (TS 38.331)
© Copyright 2018-2019 Charter Communications Operating, LLC.
MeasObjectNR information element
-- ASN1START
5 -- TAG-MEAS-OBJECT-NR-START
MeasObjectNR ::= SEQUENCE {
ssbFrequency ARFCN-ValueNR OPTIONAL, Cond
SSBorAssociatedSSB
10 ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, Cond
SSBorAssociatedSSB
smtcl SSB-MTC OPTIONAL, Cond
SSBorAssociatedSSB
smtc2 SSB-MTC2 OPTIONAL, Cond
15 IntraFreqConnected
refFreqCSI -RS ARFCN-ValueNR OPTIONAL
referenceSignalConfig ReferenceSignalConfig
20 absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R absThreshCSI -RS -Consolidation ThresholdNR OPTIONAL, -- Need R nrofSS -BlocksToAverage INTEGER (2.. maxNrofSS -BlocksToAverage ) OPTIONAL, -- Need R nrofCSI-RS-ResourcesToAverage INTEGER (2.. maxNrofCSI -RS-ResourcesToAverage) OPTIONAL, -- Need R quantityConfigIndex INTEGER (1.. maxNrofQuantityConfig) ,
offsetMO Q-OffsetRangeList ,
30 measReportLBTScanTime INTEGER (XX..maxMeasRepPCIScanTime)
maxMeasRepPCIScanTime INTEGER : : = YY
cellsToRemoveList PCI-List OPTIONAL, -- Need N
CellsToAddModList CellsToAddModList OPTIONAL, -- Need N
35
blackCellsToRemoveList PCI -RangelndexList OPTIONAL, -- Need N blackCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, -- Need N whiteCellsToRemoveList PCI -RangelndexList OPTIONAL Need N
40
whiteCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, -- Need N freqBandIndicatorNR-vl530 FreqBandlndicatorNR OPTIONAL, -- Need R
45 measCycleSCell -vl530 ENUMERATED {sf!60, sf256, sf320, sf512 , sf640 , sfl024, sfl280} OPTIONAL -- Need R
}
15
Q-OffsetRangeList ::= SEQUENCE {
rsrpOffsetSSB Q-OffsetRange DEFAULT dBO, rsrqOffsetSSB Q-OffsetRange DEFAULT dBO,
20 sinrOffsetSSB Q-OffsetRange DEFAULT dBO,
rsrpOffsetCSI -RS Q-OffsetRange DEFAULT dBO, rsrqOffsetCSI -RS Q-OffsetRange DEFAULT dBO, sinrOffsetCSI -RS Q-OffsetRange DEFAULT dBO
}
25
ThresholdNR : : = SEQUENCE!
thresholdRSRP RSRP-Range OPTIONAL, Need R thresholdRSRQ RSRQ-Range OPTIONAL, Need R
30 thresholdSINR SINR-Range OPTIONAL Need R
}
CellsToAddModList ::= SEQUENCE (SIZE ( 1.. maxNrofCellMeas ) ) OF CellsToAddMod
35 CellsToAddMod ::= SEQUENCE {
physCell Id PhysCellld,
celllndividualOffset Q-OffsetRangeList
}
40
-- TAG-MEAS-OBJECT-NR-STOP
-- ASN1STOP
APPENDIX CAPABILITY IE fTS 38.306)
© Copyright 2018-2019 Charter Communications Operating, LLC.
UE-NR-Capability information element
-- ASN1START
5 -- TAG-UE-NR-CAPABILITY-START
UE-NR-Capability ::= SEQUENCE {
accessStratumRelease AccessStratumRelease ,
pdcp-Parameters PDCP- Parameters ,
10 rlc -Parameters RLC-Parameters OPTIONAL,
mac -Parameters MAC-Parameters OPTIONAL,
phy-Parameters Phy-Parameters
rf- Parameters RF- Parameters ,
measAndMobParameters MeasAndMobParameters OPTIONAL,
15 fdd-Add-UE-NR-Capabilities UE-NR-Capabi1ityAddXDD-Mode OPTIONAL,
tdd-Add-UE-NR-Capabilities UE-NR-Capabi1ityAddXDD-Mode OPTIONAL,
frl -Add-UE-NR-Capabilities UE-NR-Capabi1ityAddFRX-Mode OPTIONAL,
fr2 -Add-UE-NR-Capabilities UE-NR-Capabi1ityAddFRX-Mode OPTIONAL,
featureSets FeatureSets OPTIONAL,
20 featureSetCombinations SEQUENCE (SIZE ( 1.. maxFeatureSetCombinations) ) OF FeatureSetCombination OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL,
nonCriticalExtension UE-NR-Capability-1530 OPTIONAL
UE-NR-Capability-1530 ::= SEQUENCE {
fdd-Add-UE-NR-Capabilities -1530 UE-NR-Capabi1ityAddXDD-Mode-1530 OPTIONAL
tdd-Add-UE-NR-Capabilities -1530 UE-NR-Capabi1ityAddXDD-Mode-1530 OPTIONAL
voiceOverMCG-Bearer ENUMERATED {supported} OPTIONAL
30 interRAT-Parameters InterRAT-Parameters OPTIONAL
inactiveState ENUMERATED {supported} OPTIONAL
delayBudgetReporting ENUMERATED {supported} OPTIONAL,
noMobii1tyRequired ENUMERATED (supported, not supported OPTIONAL
nonCriticalExtension SEQUENCE { } OPTIONAL
35 }
UE-NR-CapabilityAddXDD-Mode ::= SEQUENCE {
phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL,
mac -ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL,
40 measAndMobParametersXDD-Diff MeasAndMobParametersXDD-Diff OPTIONAL
}
UE-NR-Capabi1ityAddXDD-Mode -1530 SEQUENCE {
eutra- ParametersXDD-Diff EUTRA- ParametersXDD-Diff
45 }
UE-NR-CapabilityAddFRX-Mode ::= SEQUENCE {
phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, measAndMobParametersFRX-Diff MeasAndMobParametersFRX-Diff OPTIONAL
}
5 TAG-UE-NR-CAPABILITY-STOP
ASN1STOP
APPENDIX III - MODIFIED NR INCLUDING PLMN NUMBER LIMIT - ASN.l (TS 38.331)
© Copyright 2018-2019 Charter Communications Operating, LLC.
MeasObj ectNR information element
-- ASN1START
5 -- TAG-MEAS-OBJECT-NR-START
MeasObj ectNR ::= SEQUENCE {
ssbFrequency ARFCN-ValueNR OPTIONAL, - - Cond
SSBorAssociatedSSB
10 ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, - - Cond
SSBorAssociatedSSB
smtcl SSB-MTC OPTIONAL, - - Cond
SSBorAssociatedSSB
smtc2 SSB-MTC2 OPTIONAL, - - Cond
15 IntraFreqConnected
refFreqCSI -RS ARFCN-ValueNR OPTIONAL, referenceSignalConfig ReferenceSignalConfig
20 absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R absThreshCSI -RS -Consolidation ThresholdNR OPTIONAL, -- Need R nrofSS -BlocksToAverage INTEGER (2.. maxNrofSS -BlocksToAverage ) OPTIONAL, -- Need R nrofCSI-RS-ResourcesToAverage INTEGER (2.. maxNrofCSI -RS-ResourcesToAverage OPTIONAL, -- Need R quantityConfigIndex INTEGER (1.. maxNrofQuantityConfig) ,
offsetMO Q-OffsetRangeList ,
30 measReportLBTScanTime INTEGER (XX..maxMeasRepPCIScanTime)
maxMeasRepPCIScanTime INTEGER : : = YY
maxPLMNsPerPCIToReport INTEGER ::= (1..maxNrOfPLMNsPerPCIToReport) OPTIONAL -- maxNrOfPLMNsPerPCIToReport INTEGER ::= 20
35 cellsToRemoveList PCI-List OPTIONAL, -- Need N cellsToAddModList CellsToAddModList OPTIONAL, -- Need N blackCellsToRemoveList PCI -RangelndexList OPTIONAL -- Need N blackCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, Need N
40
whiteCellsToRemoveList PCI -RangelndexList OPTIONAL, -- Need N whiteCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, -- Need N
45
freqBandIndicatorNR-vl530 FreqBandlndicatorNR OPTIONAL, -- Need R measCycleSCell -vl530 ENUMERATED {sf!60, sf256, sf320, sf512,sf640, sf!024, sfl280} OPTIONAL Need R
}
ReferenceSignalConfig : : = SEQUENCE {
5 ssb-ConfigMobility SSB-ConfigMobility OPTIONAL, -- Need M csi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility } OPTIONAL -- Need M
}
SSB-ConfigMobility : := SEQUENCE {
10
ssb-ToMeasure SetupRelease { SSB-ToMeasure } OPTIONAL, -- Need M deriveSSB- IndexFromCell BOOLEAN,
ss-RSSI -Measurement SS -RSSI -Measurement OPTIONAL, Need M
15
}
Q-OffsetRangeList ::= SEQUENCE {
20 rsrpOffsetSSB Q-OffsetRange DEFAULT dBO ,
rsrqOffsetSSB Q-OffsetRange DEFAULT dBO,
sinrOffsetSSB Q-OffsetRange DEFAULT dBO,
rsrpOffsetCSI -RS Q-OffsetRange DEFAULT dBO,
rsrqOffsetCSI -RS Q-OffsetRange DEFAULT dBO,
25 sinrOffsetCSI -RS Q-OffsetRange DEFAULT dBO
}
ThresholdNR : : = SEQUENCE{
30 thresholdRSRP RSRP-Range OPTIONAL, -- Need R
thresholdRSRQ RSRQ-Range OPTIONAL, -- Need R
thresholdsINR SINR-Range OPTIONAL -- Need R
}
35 CellsToAddModList ::= SEQUENCE (SIZE ( 1.. maxNrofCellMeas ) ) OF CellsToAddMod
CellsToAddMod ::= SEQUENCE {
physCell Id PhysCellld,
celllndividualOffset Q-OffsetRangeList
40 }
-- TAG-MEAS-OBJECT-NR-STOP
45 -- ASN1STOP
-- ASN1START
-- TAG-PCI-RANGE-START
PCI -Range SEQUENCE {
start PhysCellld,
range ENUMERATED {n4, n8 , nl2 nl6 , n24 n32, n48, n64 n84, n96, nl28, nl68, n252 , n504 , nl 008 , sparel } OPTIONAL -- Need S
5 nrCellld CellGloballdNR OPTIONAL -- PCIs of specific PLMNs for which
Measurements Reports are to be disabled
}
CellGloballdNR ::= SEQUENCE {
10 plmn- Identity PLMN-Identity,
cellldentity Cellldentity
}
-- TAG-PCI-RANGE-STOP
15 -- ASN1STOP
MeasResults IE
-- ASNlSTART
20 -- TAG-MEAS-RESULTS-START
MeasResults : : = SEQUENCE {
measld Measld,
measResultServingMOList MeasResultServMOList ,
25 measResultNeighCells CHOICE {
measResultListNR MeasResultListNR,
measResultListEUTRA MeasResultListEUTRA
} OPTIONAL,
30
}
MeasResultServMOList ::= SEQUENCE (SIZE (1.. maxNrofServingCells) ) OF MeasResultServMO
35 MeasResultServMO : : = SEQUENCE {
servCell Id ServCe11 Index,
measResultServingCell MeasResultNR,
measResultBestNeighCell MeasResultNR OPTIONAL,
40 }
MeasResultListNR ::= SEQUENCE (SIZE (1.. maxCellReport ) ) OF MeasResultNR
MeasResultNR : := SEQUENCE {
physCell Id PhysCell Id OPTIONAL, plmn-Identity PLMN- Identity OPTIONAL measResult SEQUENCE {
5 cellResults SEQUENCE!
resultsSSB-Cell MeasQuantityResuits OPTIONAL, resuitSCSI -RS -Cell MeasQuantityResuits OPTIONAL
}.
rsIndexResults SEQUENCE!
10 resultsSSB- Indexes ResultsPerSSB- IndexList OPTIONAL, resuitSCSI -RS - Indexes ResultsPerCSI -RS - IndexList OPTIONAL
} OPTIONAL h
15
cgi - Info CGI - Info OPTIONAL
}
20 MeasResultListEUTRA ::= SEQUENCE (SIZE (1.. maxCellReport ) ) OF MeasResultEUTRA
MeasResultEUTRA ::= SEQUENCE {
physCell Id PhysCell Id,
measResult MeasQuantityResultsEUTRA,
25
cgi - Info SEQUENCE {
cgi-info-EPC SEQUENCE {
cgi - info-EPC- legacy CellAccessRelatedlnfo-EUTRA-EPC,
cgi - info-EPC- list SEQUENCE (SIZE ( 1..maxPLMN) ) OF CellAccessRelatedlnfo-EUTRA-EPC OPTIONAL
30 } OPTIONAL,
cgi-info-5GC SEQUENCE (SIZE ( 1..maxPLMN) ) OF CellAccessRelatedInfo-EUTRA-5GC OPTIONAL, freqBandlndicator FreqBandlndicatorEUTRA,
multiBandlnfoList MultiBandlnfoListEUTRA OPTIONAL,
35 freqBandlndicatorPriority ENUMERATED {true} OPTIONAL
} OPTIONAL,
}
40 MultiBandlnfoListEUTRA ::= SEQUENCE (SIZE (1.. maxMultiBands ) ) OF FreqBandlndicatorEUTRA
MeasQuantityResuits SEQUENCE {
rsrp RSRP-Range OPTIONAL, rsrq RSRQ-Range OPTIONAL,
45 sinr SINR-Range OPTIONAL
}
MeasQuantityResultsEUTRA SEQUENCE {
rsrp RSRP-RangeEUTRA OPTIONAL,
5 rsrq RSRQ-RangeEUTRA OPTIONAL, sinr SINR-RangeEUTRA OPTIONAL
}
10 ResultsPerSSB- IndexList SEQUENCE (SIZE (1.. maxNrofIndexesToReport2 ) ) OF ResultsPerSSB-Index
ResultsPerSSB- Index SEQUENCE {
ssb-Index SSB-Index,
ssb-Results MeasQuantityResults OPTIONAL
15 }
ResultsPerCSI -RS - IndexList SEQUENCE (SIZE (1.. maxNrofIndexesToReport2 ) ) OF ResultsPerCSI -RS - Index
ResultsPerCSI -RS - Index SEQUENCE {
20 csi -RS - Index CSI -RS- Index,
csi -RS -Results MeasQuantityResults OPTIONAL
}
TAG-MEAS-RESULTS -STOP
25 ASN1STOP
APPENDIX IV - MODIFIED NR - ALTERNATE EMBODIMENT- ASN.l (TS 38.331)
© Copyright 2018-2019 Charter Communications Operating, LLC.
5 MeasObj ectNR IE
-- ASNlSTART
-- TAG-MEASOBJECTNR-START
MeasObj ectNR : := SEQUENCE {
10 ssbFrequency ARFCN-ValueNR OPTIONAL, Cond SSBorAssociatedSSB ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, Cond SSBorAssociatedSSB smtcl SSB-MTC OPTIONAL, Cond SSBorAssociatedSSB smtc2 SSB-MTC2 OPTIONAL, Cond IntraFreqConnected refFreqCSI -RS ARFCN-ValueNR OPTIONAL, Cond CSI -RS
15 referenceSignalConfig ReferenceSignalConfig
absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, Need R absThreshCSI -RS -Consolidation ThresholdNR OPTIONAL, Need R nrofSS -BlocksToAverage INTEGER (2.. maxNrofSS -BlocksToAverage ) OPTIONAL, Need R nrofCSI -RS -ResourcesToAverage INTEGER (2.. maxNrofCSI -RS-ResourcesToAverage) OPTIONAL, Need R
20 quantityConfigIndex INTEGER (1.. maxNrofQuantityConfig) ,
offsetMO Q-OffsetRangeList ,
cellsToRemoveList PCI-List OPTIONAL, Need N cellsToAddModList CellsToAddModList OPTIONAL, Need N blackCellsToRemoveList PCI -RangelndexList OPTIONAL, Need N
25 blackCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, Need N
whiteCellsToRemoveList PCI -RangelndexList OPTIONAL, Need N whiteCellsToAddModList SEQUENCE (SIZE (1.. maxNrofPCI -Ranges) ) OF PCI -RangeElement OPTIONAL, Need N
30 freqBandIndicatorNR-vl530 FreqBandlndicatorNR OPTIONAL, Need R
measCycleSCell -vl530 ENUMERATED {sfl60, sf256, sf320, sf512, sf640, sfl024, sfl280} OPTIONAL Need R
[ [
measReportLBTScanTime INTEGER (XX..maxMeasRepPCIScanTime) OPTIONAL,
35 maxMeasRepPCIScanTime INTEGER : : = YY OPTIONAL,
maxPLMNsPerPCIToReport INTEGER : : = (1..maxNrOfPLMNsPerPCIToReport) OPTIONAL,
maxNrOfPLMNsPerPCIToReport INTEGER ::= 20 OPTIONAL,
blackCellsToAddModList BlockPCIOfCertainPLMNs OPTIONAL,
blackCellsToRemoveList BlockPCIOfCertainPLMNs OPTIONAL
40 ] ]
}
ReferenceSignalConfig :: = SEQUENCE {
ssb-ConfigMobility SSB-ConfigMobility OPTIONAL, Need M
45 csi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility } OPTIONAL Need M
}
SSB-ConfigMobility : := SEQUENCE {
5 ssb-ToMeasure SetupRelease { SSB-ToMeasure } OPTIONAL, -- Need M deriveSSB- IndexFromCell BOOLEAN,
ss-RSSI -Measurement SS -RSSI -Measurement OPTIONAL, -- Need M
}
10
Q-OffsetRangeList ::= SEQUENCE {
rsrpOffsetSSB Q-OffsetRange DEFAULT dBO ,
rsrqOffsetSSB Q-OffsetRange DEFAULT dBO,
15 sinrOffsetSSB Q-OffsetRange DEFAULT dBO,
rsrpOffsetCSI -RS Q-OffsetRange DEFAULT dBO,
rsrqOffsetCSI -RS Q-OffsetRange DEFAULT dBO,
sinrOffsetCSI -RS Q-OffsetRange DEFAULT dBO
}
20
ThresholdNR : : = SEQUENCE!
thresholdRSRP RSRP-Range OPTIONAL, -- Need R thresholdRSRQ RSRQ-Range OPTIONAL, -- Need R
25 thresholdSINR SINR-Range OPTIONAL -- Need R
}
CellsToAddModList ::= SEQUENCE (SIZE ( 1.. maxNrofCellMeas ) ) OF CellsToAddMod
30 CellsToAddMod ::= SEQUENCE {
physCell Id PhysCellld,
celllndividualOffset Q-OffsetRangeList
}
35
BlockPCIOfCertainPLMNs : := SEQUENCE {
cellldentity Cellldentity OPTIONAL,
plmn-Identity PLMN- Identity OPTIONAL
40
-- TAG-MEASOBJECTNR-STOP
-- ASN1STOP
Claims
1. A method for cell identification within a wireless network, the method comprising:
identifying a set of user devices for which to apply a cell identifier resolution mechanism;
instructing at least a portion of 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.
2. The method of Claim 1, wherein the user devices comprise 3GPP compliant user equipment (UEs), and the cell identifiers comprises PCI (Physical Cell ID) values.
3. The method of Claim 2, wherein the identifying a set of user devices for which to apply a cell identifier resolution mechanism comprises identifying the set of user devices based at least on a mobility-related parameter associated with each of the set of user devices.
4. The method of Claim 3, wherein the identifying the set of user devices based at least on a mobility-related parameter associated with each of the set of user devices comprises identifying the set of user devices based at least on accessing a database of mobility-related parameters associated with each of the set of user devices either (i) at time of initial user device account setup or registration, or (ii) based on a user input via the respective user device thereafter.
5. The method of Claim 1, wherein the identifying a set of user devices for which to apply a cell identifier resolution mechanism comprises identifying the set of user devices based at least on a mobility-related parameter associated with each of the set of user devices provided by at least each of the respective user devices of the set pursuant to registration with a 5GC (5th Generation Core) pursuant to 3 GPP TS 23.501 and TS 23.502.
6. The method of Claim 5, further comprising storing, via at least one gNB (gNodeB) wireless access node, the provided mobility-related parameter for each of the set of user devices for at least a duration of each respective user device’s session context.
7. The method of Claim 6, wherein the storing for at least a duration of each respective user device’s session context comprises storing at least during the respective user device’s RRC CONNECTED and RRC INACTIVE states.
8. The method of Claim 1, wherein the instructing at least a portion of the identified set of user devices to perform a measurement protocol comprises instructing only those user devices within the identified set not being used for Fixed Wireless Access (FWA) perform the measurement protocol.
9. The method of Claim 8, wherein the instructing only those user devices within the identified set not being used for Fixed Wireless Access (FWA) perform the measurement protocol comprises instructing only those user devices within the identified set not being used for Fixed Wireless Access (FWA) perform the measurement protocol only for certain selected one or more PCI (Physical Cell ID) values.
10. A method of operating a wireless network having a plurality of cells, the method comprising:
identifying a subset of a plurality of user devices for which a certain operational configuration or scenario applies;
applying a cell identifier resolution mechanism to only others of the plurality of user devices and not those of the subset;
instructing others of the plurality of user devices to perform a measurement protocol pursuant to the resolution mechanism; and
based on the results of the measurement protocol, configuring at least one listing of cell identifiers.
11. The method of Claim 10, where at least the identifying a subset of a plurality of user devices for which a certain operational configuration or scenario applies, the applying a cell identifier resolution mechanism to only others of the plurality of user devices and not those of the subset, the instructing others of the plurality of user devices to perform a measurement protocol pursuant to the resolution mechanism; and the configuring at least one listing of cell identifiers, are each performed by at least one of a 3 GPP compliant gNB (gNodeB) or a 3GPP compliant AMF (Access Management Function).
12. The method of Claim 11, further comprising 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).
13. A computerized user device, comprising:
a digital processor apparatus;
a wireless network interface apparatus in data communication with the digital processor apparatus; and
at least one storage device in data communication with the digital processor apparatus, the t least one storage device comprising at least one computer program having a plurality of instrictions configured to, when executed:
insert parametric data relating to a use scenario or context into a protocol message for transmission to a base station, the parametric data configured to be extracted by the base station to enable determination of whether measurement reporting should be performed for at least one other user device.
14. The computerized user device of Claim 13, wherein the at least one computer program is further configured to, when executed, provide mobility-related parametric data indicative that no mobility is required via a capabilities information element (IE), the mobility-related parametric data configured to enable a receiving base station to determine whether the user device can support a 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 (Physical Cell ID)-based conflict resolution protocol.
15. The computerized user device of Claim 13, wherein the user device comprises a 3GPP 5G NR (New Radio) compliant user equipment (UE).
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3115813A CA3115813A1 (en) | 2018-10-12 | 2019-10-14 | Apparatus and methods for cell identification in wireless networks |
EP19870881.0A EP3864917A4 (en) | 2018-10-12 | 2019-10-14 | Apparatus and methods for cell identification in wireless networks |
CN201980066552.3A CN112840728A (en) | 2018-10-12 | 2019-10-14 | Apparatus and method for cell identification in wireless networks |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862745065P | 2018-10-12 | 2018-10-12 | |
US62/745,065 | 2018-10-12 | ||
US201862752002P | 2018-10-29 | 2018-10-29 | |
US62/752,002 | 2018-10-29 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2020077346A1 true WO2020077346A1 (en) | 2020-04-16 |
WO2020077346A4 WO2020077346A4 (en) | 2020-06-04 |
Family
ID=70161837
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2019/056150 WO2020077346A1 (en) | 2018-10-12 | 2019-10-14 | Apparatus and methods for cell identification in wireless networks |
Country Status (5)
Country | Link |
---|---|
US (2) | US11129213B2 (en) |
EP (1) | EP3864917A4 (en) |
CN (1) | CN112840728A (en) |
CA (1) | CA3115813A1 (en) |
WO (1) | WO2020077346A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11405797B2 (en) | 2018-03-19 | 2022-08-02 | Charter Communications Operating, Llc | Apparatus and methods for cell activation in wireless networks |
US11477550B2 (en) | 2018-04-16 | 2022-10-18 | Charter Communications Operating, Llc | Apparatus and methods for enhancing quality of experience for data services over high-capacity wireless networks |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112840728A (en) | 2018-10-12 | 2021-05-25 | 特许通讯运营公司 | Apparatus and method for cell identification in wireless networks |
CN111432415B (en) * | 2019-01-09 | 2022-05-17 | 华为技术有限公司 | Communication method and device |
EP3909309A4 (en) * | 2019-02-15 | 2022-03-16 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling ue for cellular iot service in 5g mobile communication system |
US20220116794A1 (en) * | 2019-02-15 | 2022-04-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Automatic central unit user plane creation |
US11483762B2 (en) | 2019-02-22 | 2022-10-25 | Vmware, Inc. | Virtual service networks |
US11246087B2 (en) | 2019-02-22 | 2022-02-08 | Vmware, Inc. | Stateful network slice selection using slice selector as connection termination proxy |
US11146964B2 (en) * | 2019-02-22 | 2021-10-12 | Vmware, Inc. | Hierarchical network slice selection |
US10785705B1 (en) * | 2019-04-29 | 2020-09-22 | Movandi Corporation | Low-power and low-latency non-standalone initial access to new radio carrier |
CN114097265A (en) * | 2019-06-04 | 2022-02-25 | 苹果公司 | Centralized and distributed ad hoc network for physical cell identifier configuration and automatic neighbor relation |
US11178016B2 (en) | 2019-08-26 | 2021-11-16 | Vmware, Inc. | Performing slice based operations in a data plane circuit |
CN113938877B (en) * | 2020-07-13 | 2022-11-22 | 大唐移动通信设备有限公司 | Method, device and storage medium for configuring cell global identity |
WO2022072933A1 (en) * | 2020-10-02 | 2022-04-07 | Cable Television Laboratories, Inc. | Systems and methods to converge a mobile network operator (mno) with a multiple-system operator (mso) |
US11510024B2 (en) * | 2020-11-20 | 2022-11-22 | Verizon Patent And Licensing Inc. | System and method for geo-fencing of fixed wireless access |
US11973655B2 (en) | 2021-03-05 | 2024-04-30 | VMware LLC | SDL cache for O-RAN |
US11836551B2 (en) | 2021-03-05 | 2023-12-05 | Vmware, Inc. | Active and standby RICs |
US11793205B2 (en) * | 2021-11-18 | 2023-10-24 | S. C. Johnson & Son, Inc. | Oil-based insecticidal and insect repellent compositions |
CN116249083A (en) * | 2021-12-07 | 2023-06-09 | 中国电信国际有限公司 | Position area mapping method, device, equipment and medium for shared carrier of shared network |
US20230318794A1 (en) | 2022-03-23 | 2023-10-05 | Sterlite Technologies Limited | Optimizing physical cell id assignment in a wireless communication network |
WO2024031244A1 (en) * | 2022-08-08 | 2024-02-15 | Apple Inc. | Group handover and pci collision prevention in mobile iab scenario |
US20240205078A1 (en) | 2022-12-19 | 2024-06-20 | VMware LLC | Configuring different inter- and intra- communication protocols for components in a ran system |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0812119A2 (en) | 1996-05-23 | 1997-12-10 | Nokia Mobile Phones Ltd. | Mobile station having enhanced standby mode |
US20090176490A1 (en) * | 2008-01-07 | 2009-07-09 | Telefonaktiebolaget L M Ericsson (Publ) | Systems and Methods for Automatically Determining the Global Cell Identifier of a Neighboring Cell |
US20100178912A1 (en) | 2009-01-15 | 2010-07-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Automatic Detection and Correction of Physical Cell Identity Conflicts |
US20120275315A1 (en) * | 2011-04-27 | 2012-11-01 | Motorola Solutions, Inc. | Physical-layer cell identity (pci) conflict detection |
US20130079003A1 (en) * | 2011-03-25 | 2013-03-28 | Qualcomm Incorporated | Maintaining neighbor cell list |
US20130189990A1 (en) * | 2010-06-22 | 2013-07-25 | Samsung Electronics Co., Ltd. | Method and apparatus in which a terminal transmits a channel estimation result in a mobile communication system |
US8997136B2 (en) | 2010-07-22 | 2015-03-31 | Time Warner Cable Enterprises Llc | Apparatus and methods for packetized content delivery over a bandwidth-efficient network |
GB2548796A (en) | 2016-03-17 | 2017-10-04 | British Telecomm | Cellular telecommunications network |
Family Cites Families (413)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3999051A (en) | 1974-07-05 | 1976-12-21 | Sperry Rand Corporation | Error logging in semiconductor storage units |
US4339657A (en) | 1980-02-06 | 1982-07-13 | International Business Machines Corporation | Error logging for automatic apparatus |
US4574364A (en) | 1982-11-23 | 1986-03-04 | Hitachi, Ltd. | Method and apparatus for controlling image display |
JPS59116787A (en) | 1982-12-24 | 1984-07-05 | 株式会社日立製作所 | Display indication system |
US4604751A (en) | 1984-06-29 | 1986-08-05 | International Business Machines Corporation | Error logging memory system for avoiding miscorrection of triple errors |
US4710761A (en) | 1985-07-09 | 1987-12-01 | American Telephone And Telegraph Company, At&T Bell Laboratories | Window border generation in a bitmapped graphics workstation |
US5113517A (en) | 1986-04-28 | 1992-05-12 | Xerox Corporation | Concurrent display of data from two different processors each having different display font and user interface for controlling transfer of converted font data therebetween |
GB2191917A (en) | 1986-06-16 | 1987-12-23 | Ibm | A multiple window display system |
GB2191918B (en) | 1986-06-16 | 1990-09-05 | Ibm | Data display system |
JPH0814785B2 (en) | 1986-09-24 | 1996-02-14 | 株式会社日立製作所 | Display controller |
JPS63174122A (en) | 1987-01-05 | 1988-07-18 | コンピュータ・エツクス・インコーポレーテツド | Computer human interface |
US4890098A (en) | 1987-10-20 | 1989-12-26 | International Business Machines Corporation | Flexible window management on a computer display |
US5121475A (en) | 1988-04-08 | 1992-06-09 | International Business Machines Inc. | Methods of dynamically generating user messages utilizing error log data with a computer system |
JPH02297228A (en) | 1989-05-11 | 1990-12-07 | Fujitsu Ltd | Fault information storing system |
US5175813A (en) | 1989-08-14 | 1992-12-29 | International Business Machines Corporation | Window display system and method for creating multiple scrollable and non-scrollable display regions on a non-programmable computer terminal |
AU630567B2 (en) | 1990-07-31 | 1992-10-29 | Digital Equipment Corporation | System and method for emulating a window management environment having a uniform windowing interface |
US5245615A (en) | 1991-06-06 | 1993-09-14 | International Business Machines Corporation | Diagnostic system and interface for a personal computer |
JP2939021B2 (en) | 1991-09-30 | 1999-08-25 | 富士通株式会社 | Window management information input / output device |
US5434678A (en) | 1993-01-11 | 1995-07-18 | Abecassis; Max | Seamless transmission of non-sequential video segments |
US5276437A (en) | 1992-04-22 | 1994-01-04 | International Business Machines Corporation | Multi-media window manager |
US5673403A (en) | 1992-11-13 | 1997-09-30 | International Business Machines Corporation | Method and system for displaying applications of different operating systems on a single system using the user interface of the different operating systems |
EP0672277B1 (en) | 1992-12-01 | 1998-05-13 | Microsoft Corporation | A method and system for in-place interaction with embedded objects |
US5596702A (en) | 1993-04-16 | 1997-01-21 | International Business Machines Corporation | Method and system for dynamically sharing user interface displays among a plurality of application program |
FR2711819B1 (en) | 1993-10-21 | 1997-08-29 | Cegelec | Window manager especially for control / command post under multi-windowing. |
US5522025A (en) | 1993-10-25 | 1996-05-28 | Taligent, Inc. | Object-oriented window area display system |
US5465362A (en) | 1993-12-30 | 1995-11-07 | Taligent, Inc. | Object-oriented view-system for displaying information in a windowing environment |
US5463768A (en) | 1994-03-17 | 1995-10-31 | General Electric Company | Method and system for analyzing error logs for diagnostics |
US5487143A (en) | 1994-04-06 | 1996-01-23 | Altera Corporation | Computer user interface having tiled and overlapped window areas |
WO1995031771A1 (en) | 1994-05-13 | 1995-11-23 | Apple Computer, Inc. | Support for custom user-interaction elements in a graphical, event-driven computer system |
WO1995034170A1 (en) | 1994-06-08 | 1995-12-14 | Futurevision Of America Corp. | Interactive broadband multimedia system |
US5831609A (en) | 1994-06-17 | 1998-11-03 | Exodus Technologies, Inc. | Method and system for dynamic translation between different graphical user interface systems |
US5564002A (en) | 1994-08-01 | 1996-10-08 | International Business Machines Corporation | Method and apparatus for implementing a virtual desktop through window positioning |
US6397262B1 (en) | 1994-10-14 | 2002-05-28 | Qnx Software Systems, Ltd. | Window kernel |
US5742583A (en) | 1994-11-03 | 1998-04-21 | Omnipoint Corporation | Antenna diversity techniques |
US6219044B1 (en) | 1995-02-13 | 2001-04-17 | International Business Machines Corporation | Method for managing top-level windows within a conferencing network system |
US5790779A (en) | 1995-03-10 | 1998-08-04 | Microsoft Corporation | Method and system for consolidating related error reports in a computer system |
KR100243314B1 (en) | 1995-04-07 | 2000-02-01 | 윤종용 | Error log method using defect list |
US5850544A (en) | 1995-06-06 | 1998-12-15 | International Business Machines Corporation | System and method for efficient relational query generation and tuple-to-object translation in an object-relational gateway supporting class inheritance |
US5675755A (en) | 1995-06-07 | 1997-10-07 | Sony Corporation | Window system preventing overlap of multiple always-visible windows |
US5874960A (en) | 1995-07-05 | 1999-02-23 | Microsoft Corporation | Method and system for sharing applications between computer systems |
US5734652A (en) | 1995-09-27 | 1998-03-31 | Microsoft Corporation | ATM extended autoregistration and VPI/VCI assignment in a hybrid fiber-coax cable network |
US5856826A (en) | 1995-10-06 | 1999-01-05 | Apple Computer, Inc. | Method and apparatus for organizing window groups and windows in a table |
US6058307A (en) | 1995-11-30 | 2000-05-02 | Amsc Subsidiary Corporation | Priority and preemption service system for satellite related communication using central controller |
US6240555B1 (en) | 1996-03-29 | 2001-05-29 | Microsoft Corporation | Interactive entertainment system for presenting supplemental interactive content together with continuous video programs |
US5995103A (en) | 1996-05-10 | 1999-11-30 | Apple Computer, Inc. | Window grouping mechanism for creating, manipulating and displaying windows and window groups on a display screen of a computer system |
US5862316A (en) | 1996-07-01 | 1999-01-19 | Sun Microsystems, Inc. | Multiprocessing system having coherency-related error logging capabilities |
US5734380A (en) | 1996-09-27 | 1998-03-31 | Adams; James S. | Method for controlling the presentation of displays in a multi-window computer environment |
US6275857B1 (en) | 1996-10-30 | 2001-08-14 | Microsoft Corporation | System and method for freeing shared resources in a computer system |
US5867160A (en) | 1996-10-31 | 1999-02-02 | International Business Machines Corporation | System and method for task prioritization in computerized graphic interface environments |
US5895472A (en) | 1996-11-12 | 1999-04-20 | International Business Machines Corporation | Change and accounting log for object-oriented systems |
US6370571B1 (en) | 1997-03-05 | 2002-04-09 | At Home Corporation | System and method for delivering high-performance online multimedia services |
US6313880B1 (en) | 1997-04-03 | 2001-11-06 | Sony Corporation | Display with one or more display windows and placement dependent cursor and function control |
US6092107A (en) | 1997-04-07 | 2000-07-18 | At&T Corp | System and method for interfacing MPEG-coded audiovisual objects permitting adaptive control |
US6938254B1 (en) | 1997-05-06 | 2005-08-30 | Microsoft Corporation | Controlling memory usage in systems having limited physical memory |
US6108706A (en) | 1997-06-09 | 2000-08-22 | Microsoft Corporation | Transmission announcement system and method for announcing upcoming data transmissions over a broadcast network |
US6366876B1 (en) | 1997-09-29 | 2002-04-02 | Sun Microsystems, Inc. | Method and apparatus for assessing compatibility between platforms and applications |
US5954826A (en) | 1997-09-29 | 1999-09-21 | Sun Microsystems, Inc. | Method and apparatus for analyzing data |
US6181713B1 (en) | 1997-10-27 | 2001-01-30 | Sun Microsystems, Inc. | Selectable depacketizer architecture |
US6216152B1 (en) | 1997-10-27 | 2001-04-10 | Sun Microsystems, Inc. | Method and apparatus for providing plug in media decoders |
US6330010B1 (en) | 1997-11-21 | 2001-12-11 | Xsides Corporation | Secondary user interface |
US6337717B1 (en) | 1997-11-21 | 2002-01-08 | Xsides Corporation | Alternate display content controller |
US6192403B1 (en) | 1997-12-23 | 2001-02-20 | At&T Corp | Method and apparatus for adaptive monitor and support system |
US6359881B1 (en) | 1997-12-31 | 2002-03-19 | At&T Corp. | Hybrid fiber twisted pair local loop network service architecture |
US6510152B1 (en) | 1997-12-31 | 2003-01-21 | At&T Corp. | Coaxial cable/twisted pair fed, integrated residence gateway controlled, set-top box |
US6229810B1 (en) | 1997-12-31 | 2001-05-08 | At&T Corp | Network server platform for a hybrid fiber twisted pair local loop network service architecture |
EP1046259B1 (en) | 1998-01-06 | 2005-03-02 | Sony Electronics, Inc. | Method and system related to an audio/video network |
US6160872A (en) | 1998-01-15 | 2000-12-12 | Casio Communications, Inc. | Apparatus and method for preventing disconnection of consumer premises equipment |
JP4245670B2 (en) | 1998-04-22 | 2009-03-25 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Managing the functionality of consumer electronic systems |
JP3837290B2 (en) | 1998-05-07 | 2006-10-25 | サムスン エレクトロニクス カンパニー リミテッド | Method and apparatus for user and device command and control in a network |
US6233611B1 (en) | 1998-05-08 | 2001-05-15 | Sony Corporation | Media manager for controlling autonomous media devices within a network environment and managing the flow and format of data between the devices |
US6631403B1 (en) | 1998-05-11 | 2003-10-07 | At&T Corp. | Architecture and application programming interfaces for Java-enabled MPEG-4 (MPEG-J) systems |
JP3509060B2 (en) | 1998-05-28 | 2004-03-22 | 松下電器産業株式会社 | Display control device and method |
US6948183B1 (en) | 1998-06-18 | 2005-09-20 | General Instrument Corporation | Dynamic security for digital television receivers |
EP1088270B1 (en) | 1998-06-26 | 2002-10-02 | Deutsche Telekom AG | Method for checking java byte code programmes for security characteristics |
US6456892B1 (en) | 1998-07-01 | 2002-09-24 | Sony Electronics, Inc. | Data driven interaction for networked control of a DDI target device over a home entertainment network |
US6762796B1 (en) | 1998-08-10 | 2004-07-13 | Olympus Optical Co., Ltd. | Image pickup module having integrated lens and semiconductor chip |
US6381735B1 (en) | 1998-10-02 | 2002-04-30 | Microsoft Corporation | Dynamic classification of sections of software |
US6336122B1 (en) | 1998-10-15 | 2002-01-01 | International Business Machines Corporation | Object oriented class archive file maker and method |
KR20010080210A (en) | 1998-10-19 | 2001-08-22 | 매클린토크 샤운 엘 | Television set-top box with configurable functionality |
US6460141B1 (en) | 1998-10-28 | 2002-10-01 | Rsa Security Inc. | Security and access management system for web-enabled and non-web-enabled applications and content on a computer network |
US6169725B1 (en) | 1998-10-30 | 2001-01-02 | Sony Corporation Of Japan | Apparatus and method for restoration of internal connections in a home audio/video system |
US6317881B1 (en) | 1998-11-04 | 2001-11-13 | Intel Corporation | Method and apparatus for collecting and providing viewer feedback to a broadcast |
WO2000030346A1 (en) | 1998-11-12 | 2000-05-25 | General Instrument Corporation | Application programming interface (api) for accessing and managing resources in a digital television receiver |
GB9825102D0 (en) | 1998-11-16 | 1999-01-13 | Insignia Solutions Plc | Computer system |
US6910210B1 (en) | 1998-11-24 | 2005-06-21 | Microsoft Corp. | System and method for terminating applications |
US6487665B1 (en) | 1998-11-30 | 2002-11-26 | Microsoft Corporation | Object security boundaries |
US6581206B2 (en) | 1999-11-12 | 2003-06-17 | Sun Microsystems, Inc. | Computer program language subset validation |
US6873877B1 (en) | 1999-02-11 | 2005-03-29 | Loudeye Corp. | Distributed production system for digitally encoding information |
US6430570B1 (en) | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java application manager for embedded device |
US6469742B1 (en) | 1999-04-12 | 2002-10-22 | Koninklijke Philips Electronics N.V. | Consumer electronic devices with adaptable upgrade capability |
US6802056B1 (en) | 1999-06-30 | 2004-10-05 | Microsoft Corporation | Translation and transformation of heterogeneous programs |
US6762798B1 (en) | 1999-07-13 | 2004-07-13 | Sun Microsystems, Inc. | Methods and apparatus for providing video control for television applications |
US6532552B1 (en) | 1999-09-09 | 2003-03-11 | International Business Machines Corporation | Method and system for performing problem determination procedures in hierarchically organized computer systems |
US6630943B1 (en) | 1999-09-21 | 2003-10-07 | Xsides Corporation | Method and system for controlling a complementary user interface on a display surface |
US6625274B1 (en) | 1999-10-12 | 2003-09-23 | Broadsoft, Inc. | Computer system and method for providing services to users of communication systems using service entities, interface entities, and a service bus |
US6505298B1 (en) | 1999-10-25 | 2003-01-07 | International Business Machines Corporation | System using an OS inaccessible interrupt handler to reset the OS when a device driver failed to set a register bit indicating OS hang condition |
US6490580B1 (en) | 1999-10-29 | 2002-12-03 | Verizon Laboratories Inc. | Hypervideo information retrieval usingmultimedia |
US7158993B1 (en) | 1999-11-12 | 2007-01-02 | Sun Microsystems, Inc. | API representation enabling submerged hierarchy |
US6948175B1 (en) | 1999-11-16 | 2005-09-20 | Ricoh Company, Ltd. | Method and system of remote diagnostic, control and information collection using a dynamic linked library |
BR0015959A (en) | 1999-12-14 | 2002-08-06 | Scientific Atlanta | System and method for processing adaptive video with coordinated resource allocation |
US7016064B2 (en) | 1999-12-27 | 2006-03-21 | Fuji Photo Film Co., Ltd. | Method and system for remote management of processor, and method and system for remote diagnosis of image output apparatus |
US6996808B1 (en) | 2000-02-12 | 2006-02-07 | Microsoft Corporation | Function injector |
US6968364B1 (en) | 2000-03-30 | 2005-11-22 | Microsoft Corporation | System and method to facilitate selection and programming of an associated audio/visual system |
US20020032754A1 (en) | 2000-04-05 | 2002-03-14 | Gary Logston | Method and apparatus for profiling in a distributed application environment |
US6687735B1 (en) | 2000-05-30 | 2004-02-03 | Tranceive Technologies, Inc. | Method and apparatus for balancing distributed applications |
JP2001306581A (en) | 2000-04-18 | 2001-11-02 | Sony Corp | Middleware and media data audiovisual equipment using the middleware |
AU2001253702A1 (en) | 2000-04-19 | 2001-10-30 | Broadcom Corporation | Apparatus and method for persistent display interface |
US6529965B1 (en) | 2000-05-09 | 2003-03-04 | 3Com Corporation | Method of detecting TCP/IP bindings of installed network interface cards present in a computer system |
US6654722B1 (en) | 2000-06-19 | 2003-11-25 | International Business Machines Corporation | Voice over IP protocol based speech system |
US6856330B1 (en) | 2000-06-30 | 2005-02-15 | Microsoft Corporation | Method and system for user sessions on personal electronic devices |
EP1170658A1 (en) | 2000-07-07 | 2002-01-09 | Sun Microsystems, Inc. | Window management communications |
AU2001261267A1 (en) | 2000-08-07 | 2002-02-18 | Pni Corp. | Method and apparatus for a distributed home-automation-control (hac) window |
TW545059B (en) | 2000-08-08 | 2003-08-01 | Replaytv Inc | Method and system for remote television replay control |
US6829250B2 (en) | 2000-08-10 | 2004-12-07 | Verizon Communications Inc. | Automatic programming of customer premises equipment for vertical services integration |
US6631350B1 (en) | 2000-08-28 | 2003-10-07 | International Business Machines Corporation | Device-independent speech audio system for linking a speech driven application to specific audio input and output devices |
US7107606B2 (en) | 2000-08-30 | 2006-09-12 | The Chinese University Of Hong Kong | System and method for highly scalable video on demand |
US6651248B1 (en) | 2000-09-01 | 2003-11-18 | International Business Machines Corporation | Method and apparatus for efficient interface method dispatch |
US7581012B2 (en) | 2000-09-07 | 2009-08-25 | Fujitsu Limited | Virtual communication channel and virtual private community, and agent collaboration system and agent collaboration method for controlling the same |
US7111072B1 (en) | 2000-09-13 | 2006-09-19 | Cosine Communications, Inc. | Packet routing system and method |
US6952836B1 (en) | 2000-09-26 | 2005-10-04 | At&T Corp. | Method and apparatus for managing the provisioning of client devices connected to an interactive TV network |
US20050283816A1 (en) | 2004-06-16 | 2005-12-22 | Xtend Networks, Ltd. | Wideband node in a cable TV network |
US20020049978A1 (en) | 2000-10-20 | 2002-04-25 | Rodriguez Arturo A. | System and method for access and placement of media content information items on a screen display with a remote control device |
US7146305B2 (en) | 2000-10-24 | 2006-12-05 | Vcis, Inc. | Analytical virtual machine |
US6961945B2 (en) | 2000-10-30 | 2005-11-01 | Microsoft Corporation | Method and apparatus for adapting and hosting legacy user interface controls |
US7068597B1 (en) | 2000-11-27 | 2006-06-27 | 3Com Corporation | System and method for automatic load balancing in a data-over-cable network |
US7343427B2 (en) | 2000-12-13 | 2008-03-11 | Sony Corporation | Method and an apparatus for the integration of IP devices into a HAVi network |
US7127517B2 (en) | 2000-12-27 | 2006-10-24 | International Business Machines Corporation | Protocol adapter framework for integrating non-IIOP applications into an object server container |
US6750879B2 (en) | 2000-12-30 | 2004-06-15 | Intel Corporation | Method and apparatus for communicating cable modem problem demarcation through a graphical user interface |
US7051288B2 (en) | 2001-02-15 | 2006-05-23 | International Business Machines Corporation | Method, system, and product for a java-based desktop to provide window manager services on UNIX |
KR101035073B1 (en) | 2001-02-21 | 2011-05-19 | 유나이티드 비디오 프로퍼티즈, 인크. | Systems and methods for interactive program guides with personal video recording features |
US7055146B1 (en) | 2001-03-08 | 2006-05-30 | Microsoft Corporation | Method and system for dynamically inserting modifications for identified programs |
AU2002250559A1 (en) | 2001-03-22 | 2002-10-08 | United Video Properties, Inc. | Personal video recorder systems and methods |
CA2474887C (en) | 2001-03-26 | 2016-11-15 | Imagine Broadband Limited | Method and system of provisioning a desired communication service for a user across a network |
US6829729B2 (en) | 2001-03-29 | 2004-12-07 | International Business Machines Corporation | Method and system for fault isolation methodology for I/O unrecoverable, uncorrectable error |
US20040158829A1 (en) | 2001-03-30 | 2004-08-12 | Evgenij Beresin | Downloading application software to a mobile terminal |
US7370322B1 (en) | 2001-04-11 | 2008-05-06 | Sun Microsystems, Inc. | Method and apparatus for performing online application upgrades in a java platform |
US7243090B2 (en) | 2001-05-16 | 2007-07-10 | Sun Microsystems, Inc. | System and method for specification tracking in a Java compatibility testing environment |
EP1395904B1 (en) | 2001-05-22 | 2016-07-20 | Accenture Global Services Limited | Broadband communications |
US20020191028A1 (en) | 2001-06-19 | 2002-12-19 | Senechalle David A. | Window manager user interface |
US20030009765A1 (en) | 2001-06-22 | 2003-01-09 | Linden Thomas M. | Multiple program burst broadcast |
US20030009769A1 (en) | 2001-06-25 | 2003-01-09 | Debra Hensgen | Trusted application level resource advisor |
US7512964B2 (en) | 2001-06-29 | 2009-03-31 | Cisco Technology | System and method for archiving multiple downloaded recordable media content |
US7987228B2 (en) | 2001-07-03 | 2011-07-26 | Accenture Global Services Limited | Broadband communications |
US7546602B2 (en) | 2001-07-10 | 2009-06-09 | Microsoft Corporation | Application program interface for network software platform |
US7334228B2 (en) | 2001-07-27 | 2008-02-19 | International Business Machines Corporation | Runtime-resource management |
US6941135B2 (en) | 2001-08-13 | 2005-09-06 | Qualcomm Inc. | System and method for temporary application component deletion and reload on a wireless device |
US7225367B2 (en) | 2001-08-22 | 2007-05-29 | Genworth Financial, Inc. | Method and system for tracking errors |
US6847649B2 (en) | 2001-08-24 | 2005-01-25 | Ericsson Inc. | Methods, systems and computer program products for accessing an embedded web server on a broadband access terminal |
US7161978B2 (en) | 2001-08-29 | 2007-01-09 | Texas Instruments Incorporated | Transmit and receive window synchronization |
US8042132B2 (en) | 2002-03-15 | 2011-10-18 | Tvworks, Llc | System and method for construction, delivery and display of iTV content |
US8713623B2 (en) | 2001-09-20 | 2014-04-29 | Time Warner Cable Enterprises, LLC | Technique for effectively providing program material in a cable television system |
US6842870B2 (en) | 2001-09-20 | 2005-01-11 | International Business Machines Corporation | Method and apparatus for filtering error logs in a logically partitioned data processing system |
US7020669B2 (en) | 2001-09-27 | 2006-03-28 | Emc Corporation | Apparatus, method and system for writing data to network accessible file system while minimizing risk of cache data loss/ data corruption |
US7010796B1 (en) | 2001-09-28 | 2006-03-07 | Emc Corporation | Methods and apparatus providing remote operation of an application programming interface |
US7415539B2 (en) | 2001-09-28 | 2008-08-19 | Siebel Systems, Inc. | Method and apparatus for detecting insufficient memory for data extraction processes |
SE524262C2 (en) | 2001-10-24 | 2004-07-20 | Abb Ab | Method and system for automatic interaction between intelligent devices in a network |
US6895573B2 (en) | 2001-10-26 | 2005-05-17 | Resultmaker A/S | Method for generating a workflow on a computer, and a computer system adapted for performing the method |
US7000154B1 (en) | 2001-11-28 | 2006-02-14 | Intel Corporation | System and method for fault detection and recovery |
US6973597B2 (en) | 2001-12-05 | 2005-12-06 | Hewlett-Packard Development Company, L.P. | Method and apparatus for rebooting a printer |
JP2003196096A (en) | 2001-12-07 | 2003-07-11 | Internatl Business Mach Corp <Ibm> | Computer system, its starting control method and program |
US20030110511A1 (en) | 2001-12-11 | 2003-06-12 | Schutte Mark E. | Controlling personal video recording functions from interactive television |
US20030107604A1 (en) | 2001-12-12 | 2003-06-12 | Bas Ording | Method and system for automatic window resizing in a graphical user interface |
US6744967B2 (en) | 2001-12-20 | 2004-06-01 | Scientific-Atlanta, Inc. | Program position user interface for personal video recording time shift buffer |
US7366286B1 (en) | 2001-12-21 | 2008-04-29 | Symmetricom, Inc | Modified asymmetric digital subscriber line for use with long loops |
JP3938307B2 (en) | 2001-12-27 | 2007-06-27 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Display device, display method, display program, and recording medium |
US6912670B2 (en) | 2002-01-22 | 2005-06-28 | International Business Machines Corporation | Processor internal error handling in an SMP server |
US7690012B2 (en) | 2002-02-28 | 2010-03-30 | Scientific-Atlanta, Inc. | Positive parental control |
US7025678B2 (en) | 2002-03-21 | 2006-04-11 | Sony Corporation | System and method for effectively implementing remote display devices in a gaming network |
JP2004005321A (en) | 2002-03-26 | 2004-01-08 | Sony Corp | Program, recording medium, information processing device and method, and information processing system |
US20030188320A1 (en) | 2002-04-02 | 2003-10-02 | Intervideo, Inc. | Method and system for a distributed digital video recorder |
CN1332301C (en) | 2002-04-03 | 2007-08-15 | 株式会社Ntt都科摩 | Distribution method, distribution system, and terminal device |
US7369750B2 (en) | 2002-04-24 | 2008-05-06 | Microsoft Corporation | Managing record events |
US7810121B2 (en) | 2002-05-03 | 2010-10-05 | Time Warner Interactive Video Group, Inc. | Technique for delivering network personal video recorder service and broadcast programming service over a communications network |
US8832754B2 (en) | 2002-05-03 | 2014-09-09 | Tvworks, Llc | System and method for providing synchronized events to a television application |
US7899915B2 (en) | 2002-05-10 | 2011-03-01 | Richard Reisman | Method and apparatus for browsing using multiple coordinated device sets |
US7124328B2 (en) | 2002-05-14 | 2006-10-17 | Sun Microsystems, Inc. | Capturing system error messages |
US7228540B2 (en) | 2002-05-14 | 2007-06-05 | Microsoft Corporation | Preparation for software on demand system |
US7216170B2 (en) | 2002-05-22 | 2007-05-08 | Microsoft Corporation | Systems and methods to reference resources in a television-based entertainment system |
US7965693B2 (en) | 2002-05-28 | 2011-06-21 | Zte (Usa) Inc. | Interworking mechanism between wireless wide area network and wireless local area network |
US7289716B2 (en) | 2002-06-14 | 2007-10-30 | Microsoft Corporation | Scalable programmable video recorder |
US7305680B2 (en) | 2002-08-13 | 2007-12-04 | Sharp Laboratories Of America, Inc. | Listening module for asynchronous messages sent between electronic devices of a distributed network |
US7240104B2 (en) | 2002-08-21 | 2007-07-03 | Defywire, Inc. | Method and apparatus for managing resources stored on a communication device |
US20040040041A1 (en) | 2002-08-22 | 2004-02-26 | Microsoft Corporation | Interactive applications for stored video playback |
US7096459B2 (en) | 2002-09-11 | 2006-08-22 | International Business Machines Corporation | Methods and apparatus for root cause identification and problem determination in distributed systems |
US7080356B2 (en) | 2002-09-18 | 2006-07-18 | Sun Microsystems, Inc. | Certification test suite |
DE10393080T5 (en) | 2002-10-08 | 2005-09-29 | Invensys Systems, Inc., Foxboro | service portal |
US20040073944A1 (en) | 2002-10-15 | 2004-04-15 | General Instrument Corporation | Server-based software architecture for digital television terminal |
US7150008B2 (en) | 2002-10-25 | 2006-12-12 | Microsoft Corporation | Non-invasive rule-based binary analysis of software assemblies |
WO2004045125A2 (en) | 2002-11-07 | 2004-05-27 | Magis Networks, Inc. | Hybrid wired/wireless local area networking |
US7634779B2 (en) | 2002-11-20 | 2009-12-15 | Sun Microsystems, Inc. | Interpretation of DVD assembly language programs in Java TV-based interactive digital television environments |
US20040103434A1 (en) | 2002-11-25 | 2004-05-27 | United Video Properties, Inc. | Interactive television systems with conflict management capabilities |
US7058964B2 (en) | 2002-12-03 | 2006-06-06 | Matsushita Electric Industrial Co., Ltd. | Flexible digital cable network architecture |
US7316003B1 (en) | 2002-12-18 | 2008-01-01 | Oracle International Corp. | System and method for developing a dynamic web page |
US20040158649A1 (en) | 2002-12-20 | 2004-08-12 | Lior Ophir | System, method and apparatuses for hybrid coax-wireless multimedia networks using 802.11 technology |
US20050034159A1 (en) | 2002-12-20 | 2005-02-10 | Texas Instruments Incorporated | Implementing a hybrid wireless and coaxial cable network |
US20040187156A1 (en) | 2003-01-08 | 2004-09-23 | Stephen Palm | Transporting home networking frame-based communication signals over coaxial cables |
US8607280B2 (en) | 2003-01-08 | 2013-12-10 | Intel Corporation | Resource and capability borrowing |
US20040143836A1 (en) | 2003-01-21 | 2004-07-22 | Mccormack Jonathan Ian | System and method for sharing objects among two or more electronic devices |
US7194249B2 (en) | 2003-01-31 | 2007-03-20 | Qwest Communications International Inc. | Methods, systems and apparatus for providing urgent public information |
US20040181811A1 (en) | 2003-03-13 | 2004-09-16 | Rakib Selim Shlomo | Thin DOCSIS in-band management for interactive HFC service delivery |
JP4125169B2 (en) | 2003-04-02 | 2008-07-30 | キヤノン株式会社 | Log acquisition method |
TWI254565B (en) | 2003-04-11 | 2006-05-01 | Far Eastone Telecomm Co Ltd | A method applied to transmit multimedia message for services provider |
KR100526181B1 (en) | 2003-05-13 | 2005-11-03 | 삼성전자주식회사 | Test-Stream Generating Method And Apparatus Providing Various Standards And Testing Level |
US7574431B2 (en) | 2003-05-21 | 2009-08-11 | Digi International Inc. | Remote data collection and control using a custom SNMP MIB |
US7386836B2 (en) | 2003-06-09 | 2008-06-10 | International Business Machines Corporation | Maintaining multiple valid concurrent serialized object versions |
US20040261092A1 (en) | 2003-06-20 | 2004-12-23 | N2 Broadband, Inc. | Systems and methods for selling a consumer electronics host device and enhanced services associated with a cable system |
US7757261B2 (en) | 2003-06-20 | 2010-07-13 | N2 Broadband, Inc. | Systems and methods for providing flexible provisioning architectures for a host in a cable system |
US7194756B2 (en) | 2003-06-20 | 2007-03-20 | N2 Broadband, Inc. | Systems and methods for provisioning a host device for enhanced services in a cable system |
KR100506524B1 (en) | 2003-07-18 | 2005-08-03 | 삼성전자주식회사 | The Display Method of Out-Of-Band Channel Information on Open Cable |
US7401324B1 (en) | 2003-09-18 | 2008-07-15 | Sun Microsystems, Inc. | Method and apparatus for performing time measurements during instrumentation-based profiling |
US7552450B1 (en) | 2003-09-30 | 2009-06-23 | Microsoft Corporation | Systems and methods for enabling applications via an application programming interface (API) to interface with and configure digital media components |
US7519953B2 (en) | 2003-09-30 | 2009-04-14 | Microsoft Corporation | Method and system for automatically testing a software build |
US7290253B1 (en) | 2003-09-30 | 2007-10-30 | Vmware, Inc. | Prediction mechanism for subroutine returns in binary translation sub-systems of computers |
US7870352B2 (en) | 2003-11-13 | 2011-01-11 | Stalker Altan J | State-based memory unloading |
US8302111B2 (en) | 2003-11-24 | 2012-10-30 | Time Warner Cable Inc. | Methods and apparatus for hardware registration in a network device |
US7266726B1 (en) | 2003-11-24 | 2007-09-04 | Time Warner Cable Inc. | Methods and apparatus for event logging in an information network |
US7600219B2 (en) | 2003-12-10 | 2009-10-06 | Sap Ag | Method and system to monitor software interface updates and assess backward compatibility |
US7119675B2 (en) | 2004-01-27 | 2006-10-10 | Matsushita Electric Industrial Co., Ltd. | Emergency alert service |
US8078669B2 (en) | 2004-02-18 | 2011-12-13 | Time Warner Cable Inc. | Media extension apparatus and methods for use in an information network |
WO2005119435A2 (en) | 2004-06-02 | 2005-12-15 | Open Text Corporation | Systems and methods for dynamic menus |
US8201191B2 (en) | 2004-06-30 | 2012-06-12 | Time Warner Cable Inc. | Apparatus and methods for implementation of network software interfaces |
US8312267B2 (en) | 2004-07-20 | 2012-11-13 | Time Warner Cable Inc. | Technique for securely communicating programming content |
US7506320B2 (en) | 2004-09-09 | 2009-03-17 | International Business Machines Corporation | Generating sequence diagrams using call trees |
US7614045B2 (en) | 2004-09-24 | 2009-11-03 | Sap (Ag) | Sharing classes and class loaders |
US8458619B2 (en) | 2004-12-14 | 2013-06-04 | International Business Machines Corporation | Method, system and program product for screensaver breakthrough of prioritized messages |
US8522293B2 (en) | 2004-12-15 | 2013-08-27 | Time Warner Cable Enterprises Llc | Method and apparatus for high bandwidth data transmission in content-based networks |
US9723267B2 (en) | 2004-12-15 | 2017-08-01 | Time Warner Cable Enterprises Llc | Method and apparatus for wideband distribution of content |
US7711060B1 (en) | 2004-12-17 | 2010-05-04 | Marvell International Ltd. | Data stream interleaving with non-monotonically arranged data rotations for spatially diverse transmission |
KR100667789B1 (en) | 2005-01-04 | 2007-01-11 | 삼성전자주식회사 | An apparatus of receiving broadcast with Emergency Alert System packet and method of processing the Emergency Alert System packet |
US20130247027A1 (en) | 2005-02-16 | 2013-09-19 | Solidcore Systems, Inc. | Distribution and installation of solidified software on a computer |
KR20070114369A (en) | 2005-02-22 | 2007-12-03 | 다다시 아사히나 | Code type transmitting device, and code type receiving device |
KR100703779B1 (en) | 2005-05-19 | 2007-04-06 | 삼성전자주식회사 | System and method for transmitting wireline single-band orthogonal-frequency-division-multipleixing-based ultra wideband signal over the pipe-line carrying a CATV broadcasting signal |
US7945902B1 (en) | 2005-07-13 | 2011-05-17 | Oracle America, Inc. | Detection of non-standard application programming interface usage via analysis of executable code |
US7873344B2 (en) | 2005-10-03 | 2011-01-18 | Cisco Technology, Inc. | System and method to distribute emergency information |
DE102005050304A1 (en) | 2005-10-17 | 2007-04-19 | Netccm Gmbh | Method and program for the generation of automatically distributable clients of application servers |
US8027299B2 (en) | 2005-11-25 | 2011-09-27 | Gal Zuckerman | Hybrid system having multiple downlink channels and a single uplink channel |
US7606529B1 (en) | 2005-12-14 | 2009-10-20 | Sprint Communications Company L.P. | Wireless-signal distribution system via set-top box |
WO2007072670A1 (en) | 2005-12-22 | 2007-06-28 | Matsushita Electric Industrial Co., Ltd. | Broadcast receiving apparatus, video storing apparatus, and multimedia delivering system |
US8255891B2 (en) | 2005-12-30 | 2012-08-28 | Intel Corporation | Computer-implemented method and system for improved data flow analysis and optimization |
US8347341B2 (en) | 2006-03-16 | 2013-01-01 | Time Warner Cable Inc. | Methods and apparatus for centralized content and data delivery |
US20070261090A1 (en) | 2006-03-24 | 2007-11-08 | Miller Eric B | Interactive television application distribution, control, and communication system and methods |
US7739698B2 (en) | 2006-05-25 | 2010-06-15 | International Business Machines Corporation | Multiplatform API usage tool |
US7895579B2 (en) | 2006-06-16 | 2011-02-22 | Microsoft Corporation | Automated method and system for collecting and reporting API performance profiles |
WO2007144757A2 (en) | 2006-06-16 | 2007-12-21 | Nokia Corporation | An apparatus and method for transferring pdp context information for a terminal in the case of intersystem handover |
US7814544B1 (en) | 2006-06-22 | 2010-10-12 | Symantec Corporation | API-profile guided unpacking |
US8454231B2 (en) | 2006-08-09 | 2013-06-04 | Carrier Corporation | Mounting structure for a sensor |
CN101146071A (en) | 2006-09-12 | 2008-03-19 | Thomson宽带研发(北京)有限公司 | Bidirectional signal transmission device and method |
US8520850B2 (en) | 2006-10-20 | 2013-08-27 | Time Warner Cable Enterprises Llc | Downloadable security and protection methods and apparatus |
US8565744B2 (en) | 2006-10-31 | 2013-10-22 | Intel Corporation | Vertical handover composite quality measures |
JP4483921B2 (en) * | 2007-09-25 | 2010-06-16 | 株式会社カシオ日立モバイルコミュニケーションズ | Communications system |
US9008593B2 (en) | 2010-09-30 | 2015-04-14 | Broadcom Corporation | Method and system for 60 GHz distributed communication |
US8565692B2 (en) | 2007-10-30 | 2013-10-22 | Lantiq Deutschland Gmbh | System and method for providing a versatile RF and analog front-end for wireless and wired networks |
WO2009083912A2 (en) | 2007-12-28 | 2009-07-09 | Nokia Corporation | Multiple radio instances using software defined radio |
US8813143B2 (en) | 2008-02-26 | 2014-08-19 | Time Warner Enterprises LLC | Methods and apparatus for business-based network resource allocation |
US20100008235A1 (en) * | 2008-07-11 | 2010-01-14 | Qualcomm Incorporated | Reporting and resolving conflicting use of a node identifier |
US20100035610A1 (en) | 2008-08-08 | 2010-02-11 | Qualcomm Incorporated | Method and Apparatus for Selecting a Best Cell During Inter-Radio Access Technology Transition |
US8705440B2 (en) * | 2009-01-15 | 2014-04-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for cell searching |
CN102396275B (en) | 2009-02-17 | 2015-04-15 | 瑞典爱立信有限公司 | Method for controlling a communication network, servers, systems including servers |
CA2758863C (en) * | 2009-04-14 | 2015-08-18 | Interdigital Patent Holdings, Inc. | Method and apparatus of resolving pci confusion for providing inbound mobility to closed subscriber group |
US8265028B2 (en) * | 2009-08-13 | 2012-09-11 | Alcatel Lucent | Distributed allocation of physical cell identifiers |
US8639243B2 (en) * | 2009-08-21 | 2014-01-28 | Qualcomm Incorporated | Systems, methods and apparatus configured to manage neighbor cell lists |
GB2475094B (en) | 2009-11-06 | 2013-09-11 | Samsung Electronics Co Ltd | Selective enabling of user equipment capability |
EP2326122B1 (en) * | 2009-11-18 | 2017-02-15 | Mitsubishi Electric R&D Centre Europe B.V. | Method and a device for determining a wireless telecommunication device to which a hand-over of a mobile terminal has to be conducted |
US20110124335A1 (en) | 2009-11-25 | 2011-05-26 | Hans Martin | Enhanced plmn list |
CN102687553A (en) * | 2010-01-08 | 2012-09-19 | 交互数字专利控股公司 | Method and apparatus for adding CSG identities to a white list in connected mode |
KR101626989B1 (en) * | 2010-02-01 | 2016-06-13 | 삼성전자주식회사 | Method and appratus for allocation identifier of base station in a communicaiton system |
US9414269B2 (en) * | 2010-05-14 | 2016-08-09 | Blackberry Limited | Systems and methods of transmitting measurement reports |
US9300445B2 (en) | 2010-05-27 | 2016-03-29 | Time Warner Cable Enterprise LLC | Digital domain content processing and distribution apparatus and methods |
US9185341B2 (en) | 2010-09-03 | 2015-11-10 | Time Warner Cable Enterprises Llc | Digital domain content processing and distribution apparatus and methods |
US8385224B2 (en) | 2010-09-23 | 2013-02-26 | Verizon Patent And Licensing Inc. | Shared Wi-Fi / wireless broadband access |
US9807778B2 (en) | 2010-10-11 | 2017-10-31 | Interdigital Patent Holdings, Inc. | Dynamic spectrum management |
TWI569654B (en) | 2010-11-01 | 2017-02-01 | 內數位專利控股公司 | Wireless transmit/receive unit and method implemented in dynamic spectrum management engine |
JP5692234B2 (en) * | 2010-11-19 | 2015-04-01 | 富士通株式会社 | Radio base station apparatus, terminal apparatus, radio communication system, and radio communication method in radio base station apparatus |
US10009431B2 (en) | 2011-05-23 | 2018-06-26 | Nokia Technologies Oy | Methods and apparatuses for lawful interception through a subscription manager |
US8902815B2 (en) | 2011-07-10 | 2014-12-02 | Cisco Technology, Inc. | System and method for subscriber mobility in a cable network environment |
US8750710B1 (en) | 2011-07-15 | 2014-06-10 | Cisco Technology, Inc. | System and method for facilitating fiber access transport using pluggable radio frequency optics |
US8385305B1 (en) | 2012-04-16 | 2013-02-26 | CBF Networks, Inc | Hybrid band intelligent backhaul radio |
US8730919B2 (en) * | 2011-09-25 | 2014-05-20 | Lg Electronics Inc. | Method for performing mobility in wireless communication system and apparatus for the same |
US9271291B2 (en) | 2011-09-26 | 2016-02-23 | Interdigital Patent Holdings, Inc. | Common anchor based aggregation |
US8989162B2 (en) | 2011-09-27 | 2015-03-24 | Skyriver Communications, Inc. | Point-to-multipoint microwave communication |
US8724588B2 (en) | 2011-11-18 | 2014-05-13 | Verizon Patent And Licensing Inc. | Mobility management entity (MME) selection within a border region |
US20130143555A1 (en) * | 2011-12-02 | 2013-06-06 | Qualcomm Incorporated | Managing access terminal handover in view of access point physical layer identifier confusion |
US8792565B2 (en) | 2011-12-14 | 2014-07-29 | Entropic Communications, Inc. | 10 Gbps coaxial cable networking system |
GB2498924A (en) | 2012-01-05 | 2013-08-07 | Renesas Mobile Corp | Allocating resources between two wireless networks on an unlicensed band |
US20130201316A1 (en) | 2012-01-09 | 2013-08-08 | May Patents Ltd. | System and method for server based control |
US8983475B2 (en) | 2012-02-16 | 2015-03-17 | Futurewei Technologies, Inc. | System and method for partner network sharing architecture |
JP5822028B2 (en) * | 2012-02-17 | 2015-11-24 | 日本電気株式会社 | Communication system, identifier assigning device, base station, identifier assigning method, and program |
GB2500723A (en) | 2012-03-30 | 2013-10-02 | Nec Corp | Intersystem reselection between radio access networks of different types |
US9612816B2 (en) | 2012-04-12 | 2017-04-04 | Industry-University Cooperation Foundation Hanyang University | Method for operating software defined radio application |
US8849122B2 (en) | 2012-04-19 | 2014-09-30 | Time Warner Cable Enterprises, LLC | Apparatus and methods for dynamic delivery of optical and non-optical content in a network |
US8989221B2 (en) | 2012-06-04 | 2015-03-24 | Cisco Technology, Inc. | System and method for discovering and verifying a hybrid fiber-coaxial topology in a cable network environment |
WO2013190993A1 (en) * | 2012-06-18 | 2013-12-27 | Nec Corporation | Base station, communication system and method of controlling base station, and computer readable medium therefor |
US9578558B2 (en) | 2012-08-15 | 2017-02-21 | Lg Electronics Inc. | Method and apparatus for performing handover in wireless communication system |
US20140073304A1 (en) * | 2012-09-10 | 2014-03-13 | At&T Mobility Ii Llc | Distance-based modification of neighbor relations |
US9578531B2 (en) * | 2012-09-27 | 2017-02-21 | Blackberry Limited | Method and system for indicating frequency for reporting a GERAN CGI |
CN103716766A (en) | 2012-09-29 | 2014-04-09 | 华为技术有限公司 | Charging information processing method, device and system |
US9692459B2 (en) | 2012-11-28 | 2017-06-27 | Intel Corporation | Using multiple frequency bands with beamforming assistance in a wireless network |
US10375629B2 (en) | 2012-12-31 | 2019-08-06 | T-Mobile Usa, Inc. | Service preferences for multiple-carrier-enabled devices |
US9923621B2 (en) | 2013-02-16 | 2018-03-20 | Cable Television Laboratories, Inc. | Multiple-input multiple-output (MIMO) communication system |
GB2525532B (en) | 2013-02-16 | 2020-09-02 | Cable Television Laboratories Inc | Multiple-Input multiple-output (MMO) communication system |
CN105191197B (en) | 2013-03-07 | 2018-12-07 | 索尼公司 | MIMO receiving device and MIMO pre-processing device |
US8990851B2 (en) | 2013-03-14 | 2015-03-24 | Google Technology Holdings LLC | System and method for using emergency alert system messages |
US9032468B2 (en) | 2013-03-15 | 2015-05-12 | Arris Technology, Inc. | CATV video and data transmission system with automatic dispersion compensation |
CN103260268B (en) | 2013-04-15 | 2016-02-17 | 开曼群岛威睿电通股份有限公司 | Be applicable to mobile communications device and its integrated circuit of multi-mode communication |
KR102046159B1 (en) | 2013-04-15 | 2019-11-18 | 삼성전자주식회사 | Security and information supporting method and system for using policy control in re-subscription or adding subscription to mobile network operator in mobile telecommunication system environment |
US10044613B2 (en) | 2013-05-16 | 2018-08-07 | Intel IP Corporation | Multiple radio link control (RLC) groups |
US9378638B2 (en) | 2013-06-04 | 2016-06-28 | American Megatrends, Inc. | Emergency alert system using management controller in network |
US9107130B2 (en) * | 2013-06-18 | 2015-08-11 | Motorola Solutions, Inc. | Method and apparatus for traffic offloading procedure management in a public safety communication system |
US9554194B2 (en) | 2013-06-20 | 2017-01-24 | Antronix Inc. | System and method for providing data communication services through a CATV tap-off device |
EP3017643B1 (en) | 2013-07-03 | 2019-09-11 | Interdigital Patent Holdings, Inc. | Multi-band methods for interference limited wireless local area network systems |
US9635324B2 (en) | 2013-07-19 | 2017-04-25 | Antronix Inc. | Integrated coax/ethernet distribution system |
WO2015018448A1 (en) | 2013-08-08 | 2015-02-12 | Telefonaktiebolaget L M Ericsson (Publ) | Indication of packet based voice support in a mobile network with different radio access technologies |
US9462499B2 (en) * | 2013-09-04 | 2016-10-04 | Qualcomm Incorporated | Methods and apparatus for network entity collision detection |
US9794903B2 (en) | 2013-09-23 | 2017-10-17 | Ziva Corp. | Synchronization of distributed nodes |
US9510208B2 (en) * | 2013-10-04 | 2016-11-29 | Qualcomm Incorporated | Sequence generation for shared spectrum |
EP3075180B1 (en) | 2013-11-29 | 2018-04-11 | Telefonaktiebolaget LM Ericsson (publ) | Method and corresponding apparatus, computer program product to validate an euicc subscription change |
US10021572B2 (en) * | 2013-12-04 | 2018-07-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Resource sharing between radio access technologies |
US9832043B2 (en) | 2014-02-07 | 2017-11-28 | Verizon Patent And Licensing Inc. | Bandwidth boosting in shared local networks |
WO2015147707A1 (en) | 2014-03-24 | 2015-10-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method and network node for providing overlap information in a cellular network |
CN105228171B (en) * | 2014-05-30 | 2018-10-09 | 中国电信股份有限公司 | The self-configuration method and system of the small base station of dual link in heterogeneous network |
US10159019B2 (en) * | 2014-06-03 | 2018-12-18 | Deutsche Telekom Ag | Improving overall network performance and/or overall quality of service of user equipments in a mobile communication network |
US20150365178A1 (en) * | 2014-06-12 | 2015-12-17 | Broadcom Corporation | System, method, and apparatus for signaling intefering cell information |
JP6393398B2 (en) | 2014-07-07 | 2018-09-19 | コンヴィーダ ワイヤレス, エルエルシー | Coordinated grouping for machine type communication group based services |
EP3170334A4 (en) * | 2014-07-14 | 2017-12-27 | Nokia Solutions and Networks Oy | Cellular identifier optimizations |
US9674759B2 (en) | 2014-07-21 | 2017-06-06 | Ipcomm | Integrating mobile femto-cell access point into home appliance network |
US10560891B2 (en) | 2014-09-09 | 2020-02-11 | Blackberry Limited | Medium Access Control in LTE-U |
US10382294B2 (en) | 2014-09-25 | 2019-08-13 | Oracle International Corporation | Platform for capturing, processing, storing, and presentation of generic sensor data from remote arbitrary locations |
US9838169B2 (en) | 2014-10-29 | 2017-12-05 | Samsung Electronics Co., Ltd. | Methods and apparatus using interleaved guard OFDM in wireless communication systems |
US20160127434A1 (en) | 2014-11-03 | 2016-05-05 | Douglas Sup Yoon | Systems and methods for transmitting and receiving broadcast data |
US9674880B1 (en) | 2014-11-04 | 2017-06-06 | Dell Products, Lp | Method and apparatus for a smart vehicle gateway with connection context aware radio communication management and multi-radio technology |
US10225055B2 (en) * | 2014-11-26 | 2019-03-05 | Qualcomm Incorporated | Network identification based on discovery reference signals in wireless communications |
US9813148B2 (en) | 2014-12-18 | 2017-11-07 | Time Warner Cable Enterprises Llc | Wireless media usage, channel aggregation, and full-duplex communications |
US10887016B2 (en) | 2015-01-07 | 2021-01-05 | Mds Link, Inc. | Method and system for high bandwidth, multi-consumer data and video distribution equipment |
US20160212632A1 (en) * | 2015-01-16 | 2016-07-21 | Qualcomm Incorporated | Efficient physical cell identifier collision and confusion avoidance using lte-direct |
KR101683258B1 (en) | 2015-02-10 | 2016-12-07 | 주식회사 이센소프트 | System for failure analysis in HFC and method for operating the same |
US10055554B2 (en) | 2015-03-02 | 2018-08-21 | Parallel Wireless, Inc. | Software-enabled remote licensing and provisioning |
US11050503B2 (en) | 2015-03-31 | 2021-06-29 | Huawei Technologies Co., Ltd. | System and method of waveform design for operation bandwidth extension |
CN105071860B (en) | 2015-07-15 | 2017-08-25 | 武汉虹信通信技术有限责任公司 | A kind of multichannel ROF system based on WDM and OFDM technology |
US9564932B1 (en) | 2015-07-16 | 2017-02-07 | LGS Innovations LLC | Software defined radio front end |
US9948349B2 (en) | 2015-07-17 | 2018-04-17 | Corning Optical Communications Wireless Ltd | IOT automation and data collection system |
WO2017031384A1 (en) * | 2015-08-18 | 2017-02-23 | Parallel Wireless, Inc. | Cell id disambiguation |
US10177832B2 (en) | 2015-08-25 | 2019-01-08 | Cellium Technologies, Ltd. | Using a coaxial cable for distributing MIMO signals in-house |
WO2017058966A1 (en) | 2015-09-28 | 2017-04-06 | Department 13, LLC | Unmanned aerial vehicle intrusion detection and countermeasures |
US9872224B2 (en) | 2015-10-19 | 2018-01-16 | Sk Planet Co., Ltd. | Method for constructing beacon topology network |
US10848944B2 (en) | 2015-11-24 | 2020-11-24 | Verizon Patent And Licensing Inc. | Internet of things communication unification and verification |
US10715599B2 (en) | 2015-11-30 | 2020-07-14 | Verizon Patent And Licensing, Inc. | Internet of things (IoT) platform and application framework |
JP2017118483A (en) | 2015-12-18 | 2017-06-29 | 富士通株式会社 | Communication device and transmission method |
US10638282B2 (en) | 2015-12-31 | 2020-04-28 | Huawei Technologies Co., Ltd. | Charging system and method, and network device |
KR20170087054A (en) | 2016-01-19 | 2017-07-27 | 삼성전자주식회사 | Radio link failure processing method and device therefor |
WO2017126623A1 (en) | 2016-01-22 | 2017-07-27 | 京セラ株式会社 | Wireless terminal and processor |
EP3412045B1 (en) * | 2016-02-04 | 2021-09-15 | Reliance Jio Infocomm Limited | Systems and methods for resolving a physical cell identity confusion in a heterogeneous network |
US10492104B2 (en) | 2016-03-10 | 2019-11-26 | Cable Television Laboratories, Inc. | Latency reduction in wireless service |
WO2017157585A1 (en) * | 2016-03-17 | 2017-09-21 | British Telecommunications Public Limited Company | Cellular telecommunications network |
WO2017173612A1 (en) | 2016-04-07 | 2017-10-12 | 华为技术有限公司 | Data transmission method, user equipment and access network device |
WO2017186294A1 (en) | 2016-04-28 | 2017-11-02 | Nokia Solutions And Networks Oy | Method, system and apparatus for channel evacuation in a wireless network with spectrum sharing |
US10162990B2 (en) | 2016-04-29 | 2018-12-25 | Samsung Electronics Co., Ltd. | Analog heterogeneous connectivity tags and methods and systems to configure the tags |
US10164858B2 (en) | 2016-06-15 | 2018-12-25 | Time Warner Cable Enterprises Llc | Apparatus and methods for monitoring and diagnosing a wireless network |
US10764863B2 (en) | 2016-09-01 | 2020-09-01 | Parallel Wireless, Inc. | Multi-radio access technology paging |
US9894659B1 (en) * | 2016-09-29 | 2018-02-13 | Google Llc | Assigning physical-layer cell identities to base stations |
KR102503538B1 (en) | 2016-11-28 | 2023-02-24 | 삼성전자 주식회사 | Gateway and network allocation method of gateway, mobile management entity and network allocation method of mobile management entity and terminal and network connecting method of terminal in wireless communication system |
US10142886B2 (en) * | 2016-09-30 | 2018-11-27 | Cisco Technology, Inc. | System and method to facilitate group reporting of user equipment congestion information in a network environment |
CN108024314B (en) | 2016-11-03 | 2021-07-16 | 华为技术有限公司 | Method and device for selecting network |
US10716047B2 (en) | 2016-11-18 | 2020-07-14 | Qualcomm Incorporated | Techniques for selecting a radio access technology over an unlicensed radio frequency spectrum band for serving a class of traffic |
US10742321B2 (en) | 2016-12-19 | 2020-08-11 | Cable Television Laboratories, Inc. | Systems and methods for delta-sigma digitization |
US10805058B2 (en) | 2016-12-19 | 2020-10-13 | Cable Television Laboratories, Inc. | Systems and methods for mapping and demapping digitized signals for optical transmission |
CN118117305A (en) | 2016-12-21 | 2024-05-31 | 英特尔公司 | Wireless communication technology, device and method |
US10244435B2 (en) | 2016-12-22 | 2019-03-26 | Cisco Technology, Inc. | Cable cellular heterogeneous network |
US10680883B2 (en) | 2017-01-04 | 2020-06-09 | Hall Labs Llc | Devices and systems for consumer-installed hub-based intermediate-range packetized wireless networks utilizing assignable operational channels |
US10959235B2 (en) | 2017-01-05 | 2021-03-23 | Nokia Technologies Oy | Performance indicator for interworking radio access technologies |
KR102117098B1 (en) | 2017-01-12 | 2020-06-02 | 주식회사 케이티 | Methods for controlling handover for inter-Network and Apparatuses thereof |
WO2018131904A1 (en) | 2017-01-12 | 2018-07-19 | 주식회사 케이티 | Method for controlling heterogeneous network handover and apparatus therefor |
JP6928619B2 (en) | 2017-01-13 | 2021-09-01 | 大日精化工業株式会社 | Colorant and infrared reflective light-shielding film |
WO2018131956A1 (en) | 2017-01-16 | 2018-07-19 | Samsung Electronics Co., Ltd. | Method and apparatus for communication in wireless mobile communication system |
CN110249651A (en) | 2017-02-06 | 2019-09-17 | 瑞典爱立信有限公司 | It is used to indicate by the method and device of the auxiliary evolved node B of the WiFi access point data service carried on unlicensed spectrum |
CN110651532B (en) | 2017-03-24 | 2023-03-10 | 瑞典爱立信有限公司 | First Radio Network Node (RNN), second RNN and methods therein |
EP3471463B1 (en) | 2017-04-13 | 2021-01-13 | LG Electronics Inc. -1- | Method and apparatus for providing system information |
US10601664B2 (en) | 2017-04-28 | 2020-03-24 | Cisco Technology, Inc. | Dynamic network and security policy for IoT devices |
US11323976B2 (en) | 2017-05-08 | 2022-05-03 | Ntt Docomo, Inc. | Network device and radio communication method |
US10616090B2 (en) | 2017-05-10 | 2020-04-07 | Vivint, Inc. | Load balancing in multiple-input multiple-output systems using a mesh network |
US10674558B2 (en) | 2017-05-24 | 2020-06-02 | Vivint Wireless, Inc. | Mesh topology radio |
US10158532B1 (en) | 2017-05-31 | 2018-12-18 | At&T Intellectual Property I, L.P. | Bandwidth management in a customer premises equipment comprising multiple networks |
US10862911B2 (en) | 2017-06-27 | 2020-12-08 | Allot Ltd. | System, device, and method of adaptive network protection for managed internet-of-things services |
US10447341B2 (en) | 2017-07-20 | 2019-10-15 | Cable Television Laboratories, Inc. | Systems and methods for wireless coexistence in an unlicensed spectrum |
JP6901107B2 (en) | 2017-08-10 | 2021-07-14 | オフィノ, エルエルシー | Wireless resource configuration synchronization |
US11564271B2 (en) | 2017-08-11 | 2023-01-24 | Nokia Technologies Oy | User equipment category signaling in an LTE-5G configuration |
US10721752B2 (en) | 2017-09-10 | 2020-07-21 | Hewlett Packard Enterprise Development Lp | Channel plan determination |
US10693559B2 (en) | 2017-10-05 | 2020-06-23 | Cable Television Laboratories, Inc | System and methods for centralized network node digitization |
US11356840B2 (en) | 2017-10-17 | 2022-06-07 | Lenovo (Singapore) Pte. Ltd. | Suspending services in a core network |
US11057937B2 (en) | 2017-10-19 | 2021-07-06 | Qualcomm Incorporated | Relay node connection techniques in wireless backhaul systems |
US10855814B2 (en) | 2017-10-20 | 2020-12-01 | Comcast Cable Communications, Llc | Non-access stratum capability information |
US11368362B2 (en) | 2017-11-07 | 2022-06-21 | Apple Inc. | Transport network layer associations on the FI interface |
US10880792B2 (en) | 2017-11-07 | 2020-12-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Nodes and method for determining target PLMN ID and target cell ID |
US10966073B2 (en) | 2017-11-22 | 2021-03-30 | Charter Communications Operating, Llc | Apparatus and methods for premises device existence and capability determination |
US11736979B2 (en) | 2017-11-30 | 2023-08-22 | Huawei Technologies Co., Ltd. | Data packet transmission method and apparatus to address a high-latency caused when data is to be transmitted using an unlicensed frequency band |
US11201777B2 (en) | 2018-01-23 | 2021-12-14 | Cable Television Laboratories, ino. | Systems and methods for a universal data link |
US10644942B2 (en) | 2018-02-07 | 2020-05-05 | Mavenir Networks, Inc. | Management of radio units in cloud radio access networks |
EP3550886B1 (en) | 2018-02-09 | 2021-07-07 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Voice over ims incoming session |
US11405797B2 (en) | 2018-03-19 | 2022-08-02 | Charter Communications Operating, Llc | Apparatus and methods for cell activation in wireless networks |
US11716558B2 (en) | 2018-04-16 | 2023-08-01 | Charter Communications Operating, Llc | Apparatus and methods for integrated high-capacity data and wireless network services |
CN112369057B (en) | 2018-05-18 | 2024-06-18 | 联想(新加坡)私人有限公司 | UE radio capability update in 5G systems |
US11432284B2 (en) | 2018-05-22 | 2022-08-30 | Charter Communications Operating, Llc | Methods and apparatus for intra-cell and inter-frequency mobility optimization and mitigation of session disruption in a quasi-licensed wireless system |
CN112369077B (en) | 2018-06-25 | 2023-10-24 | 日本电气株式会社 | UE behavior for emergency services attachment device |
US11044597B2 (en) | 2018-08-07 | 2021-06-22 | Charter Communications Operating, Llc | Apparatus and methods for registration and operation in wireless networks |
US11284311B2 (en) | 2018-10-03 | 2022-03-22 | Cable Television Laboratories, Inc. | Systems and methods for radio access network small cell |
CN112840728A (en) | 2018-10-12 | 2021-05-25 | 特许通讯运营公司 | Apparatus and method for cell identification in wireless networks |
CN109792614B (en) | 2018-12-27 | 2021-11-02 | 北京小米移动软件有限公司 | Resource occupation method, device, terminal and storage medium of unauthorized frequency band |
CN113661755A (en) | 2019-03-18 | 2021-11-16 | 苹果公司 | System and method for balancing time resource allocation for cellular vehicle to all (C-V2X) and intelligent transportation system (ITS-G5) or Dedicated Short Range Communication (DSRC) depending on user configuration |
US10693687B1 (en) | 2019-03-28 | 2020-06-23 | Intel Corporation | Intermediate frequency on chip (IFoC) system |
US11357005B2 (en) | 2019-10-09 | 2022-06-07 | Cisco Technology, Inc. | Integration of a Wi-Fi access point with a cellular radio unit |
US11476894B2 (en) | 2019-12-10 | 2022-10-18 | AR & NS Investment, LLC | Edge communication system with cascaded repeater devices over wired medium |
US11843474B2 (en) | 2020-02-11 | 2023-12-12 | Charter Communications Operating, Llc | Apparatus and methods for providing high-capacity data services over a content delivery network |
US11570015B2 (en) | 2020-04-22 | 2023-01-31 | Charter Communications Operating, Llc | Premises apparatus and methods for aggregated high-capacity data services |
US11985641B2 (en) | 2020-04-22 | 2024-05-14 | Charter Communications Operating, Llc | Node apparatus and methods for providing high-capacity data services via a content delivery network architecture |
-
2019
- 2019-10-14 CN CN201980066552.3A patent/CN112840728A/en active Pending
- 2019-10-14 US US16/601,345 patent/US11129213B2/en active Active
- 2019-10-14 CA CA3115813A patent/CA3115813A1/en active Pending
- 2019-10-14 WO PCT/US2019/056150 patent/WO2020077346A1/en unknown
- 2019-10-14 EP EP19870881.0A patent/EP3864917A4/en active Pending
-
2021
- 2021-09-20 US US17/479,989 patent/US11903049B2/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0812119A2 (en) | 1996-05-23 | 1997-12-10 | Nokia Mobile Phones Ltd. | Mobile station having enhanced standby mode |
US20090176490A1 (en) * | 2008-01-07 | 2009-07-09 | Telefonaktiebolaget L M Ericsson (Publ) | Systems and Methods for Automatically Determining the Global Cell Identifier of a Neighboring Cell |
US20100178912A1 (en) | 2009-01-15 | 2010-07-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Automatic Detection and Correction of Physical Cell Identity Conflicts |
US20130189990A1 (en) * | 2010-06-22 | 2013-07-25 | Samsung Electronics Co., Ltd. | Method and apparatus in which a terminal transmits a channel estimation result in a mobile communication system |
US8997136B2 (en) | 2010-07-22 | 2015-03-31 | Time Warner Cable Enterprises Llc | Apparatus and methods for packetized content delivery over a bandwidth-efficient network |
US20130079003A1 (en) * | 2011-03-25 | 2013-03-28 | Qualcomm Incorporated | Maintaining neighbor cell list |
US20120275315A1 (en) * | 2011-04-27 | 2012-11-01 | Motorola Solutions, Inc. | Physical-layer cell identity (pci) conflict detection |
GB2548796A (en) | 2016-03-17 | 2017-10-04 | British Telecomm | Cellular telecommunications network |
Non-Patent Citations (4)
Title |
---|
3GPP TS 23.501 |
3GPP TS 36.300 |
3GPP TS 38.889 |
See also references of EP3864917A4 |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11405797B2 (en) | 2018-03-19 | 2022-08-02 | Charter Communications Operating, Llc | Apparatus and methods for cell activation in wireless networks |
US11477550B2 (en) | 2018-04-16 | 2022-10-18 | Charter Communications Operating, Llc | Apparatus and methods for enhancing quality of experience for data services over high-capacity wireless networks |
US11716558B2 (en) | 2018-04-16 | 2023-08-01 | Charter Communications Operating, Llc | Apparatus and methods for integrated high-capacity data and wireless network services |
US12041398B2 (en) | 2018-04-16 | 2024-07-16 | Charter Communications Operating, Llc | Apparatus and methods for enhancing quality of experience for data services over high-capacity wireless networks |
US12047719B2 (en) | 2018-04-16 | 2024-07-23 | Charter Communications Operating, Llc | Gateway apparatus and methods for wireless IoT (internet of things) services |
Also Published As
Publication number | Publication date |
---|---|
EP3864917A4 (en) | 2022-07-06 |
US20220007440A1 (en) | 2022-01-06 |
US11129213B2 (en) | 2021-09-21 |
US20200120724A1 (en) | 2020-04-16 |
CA3115813A1 (en) | 2020-04-16 |
EP3864917A1 (en) | 2021-08-18 |
CN112840728A (en) | 2021-05-25 |
US11903049B2 (en) | 2024-02-13 |
WO2020077346A4 (en) | 2020-06-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11903049B2 (en) | Apparatus and methods for cell identification in wireless networks | |
US20210314762A1 (en) | Apparatus and methods for registration and operation in wireless networks | |
US20220369119A1 (en) | Apparatus and methods for cell activation in wireless networks | |
JP7304365B2 (en) | Apparatus and method for enabling user device mobility in enhanced wireless networks | |
US11632677B2 (en) | Methods and apparatus for dynamic control and utilization of quasi-licensed wireless spectrum | |
US11863999B2 (en) | Apparatus and methods for interference detection and handling within unlicensed spectrum | |
US11601869B2 (en) | Non-public network discovery, selection, and access control in vertical domain | |
US20230199851A1 (en) | Apparatus and methods for multicarrier unlicensed heterogeneous channel access | |
US11432284B2 (en) | Methods and apparatus for intra-cell and inter-frequency mobility optimization and mitigation of session disruption in a quasi-licensed wireless system | |
US10932131B2 (en) | Service provisioning by local operator | |
US11019454B2 (en) | Apparatus and methods for device location determination | |
US11671905B2 (en) | Prioritized scanning for improved system acquisition |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19870881 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3115813 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019870881 Country of ref document: EP Effective date: 20210512 |