Patent Grant
12200814
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The present disclosure relates generally to the field of wireless devices and networks thereof, and specifically in one exemplary aspect to activation or selection of one or more cells within one or more RANs (Radio Area Networks) of a radio network utilizing licensed and/or unlicensed spectrum.
A multitude of wireless networking technologies, also known as Radio Access Technologies (“RATs”), provide the underlying means of connection for radio-based communication networks to user devices. Such RATs often utilize licensed radio frequency spectrum (i.e., that allocated by the FCC per the Table of Frequency Allocations as codified at Section 2.106 of the Commission's Rules). Currently only frequency bands between 9 kHz and 275 GHz have been allocated (i.e., designated for use by one or more terrestrial or space radio communication services or the radio astronomy service under specified conditions). For example, a typical cellular service provider might utilize spectrum for so-called “3G” (third generation) and “4G” (fourth generation) wireless communications as shown in Table 1 below:
Alternatively, unlicensed spectrum may be utilized, such as that within the so-called ISM-bands. The ISM bands are defined by the ITU Radio Regulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of the Radio Regulations. In the United States, uses of the ISM bands are governed by Part 18 of the Federal Communications Commission (FCC) rules, while Part 15 contains the rules for unlicensed communication devices, even those that share ISM frequencies. Table 2 below shows typical ISM frequency allocations:
ISM bands are also been shared with (non-ISM) license-free communications applications such as wireless sensor networks in the 915 MHz and 2.450 GHz bands, as well as wireless LANs (e.g., Wi-Fi) and cordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.
Additionally, the 5 GHz band has been allocated for use by, e.g., WLAN equipment, as shown in Table 3:
User client devices (e.g., smartphone, tablet, phablet, laptop, smartwatch, or other wireless-enabled devices, mobile or otherwise) generally support multiple RATs that enable the devices to connect to one another, or to networks (e.g., the Internet, intranets, or extranets), often including RATs associated with both licensed and unlicensed spectrum. In particular, wireless access to other networks by client devices is made possible by wireless technologies that utilize networked hardware, such as a wireless access point (“WAP” or “AP”), small cells, femtocells, or cellular towers, serviced by a backend or backhaul portion of service provider network (e.g., a cable network). A user may generally access the network at a node or “hotspot,” a physical location at which the user may obtain access by connecting to modems, routers, APs, small cells, 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 has specified 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, also called “5GC”).
The NG-RAN (5G) System architecture is designed to support data connectivity and services offering with higher throughput and lower latency.
An existing 3GPP LTE/LTE-A/EPC (i.e., 4G or 4.5G system) cannot be updated to support 5G; hence, 3GPP has also defined interworking procedures between such 4G/4.5G and 5G systems.
In the local breakout scenario of
One service example of using the aforementioned interworking feature between the 5GS and the EPC/E-UTRAN is that a hypothetical voice call can be handled in the EPS (Evolved Packet System) or 4G/4.5G side by using redirection or handover features from the NG-RAN/5G side.
Notably, the extant 5GS and EPS interworking approach assumes that same PLMN operator operates on both sides of the architecture of
The 5G specifications (including TS 23.501) also define two types of UE registration modes: (i) single-registration mode, and (ii) dual-registration mode. As set forth in TS 23.501 (section 5.17.2.1), in single-registration mode, the UE has only one active MM (mobility management) state—either an RM state in 5GC (5G Core) or an EMM state in EPC- and it is either in 5GC NAS mode or in EPC NAS mode (when connected to 5GC or EPC, respectively). The UE maintains a single coordinated registration for both 5GC and EPC. Hence, the UE maps the EPS-GUTI (Globally Unique Temporary Identity) to 5G GUTI during mobility between EPC and 5GC, and vice versa (referencing Annex B).
As further set forth in TS 23.501 (section 5.17.2.1), the UE also keeps the native 5G-GUTI and the native 5G security context when moving from 5GC to EPC (so as to enable re-use of a previously established 5G security context when returning to 5GC).
Conversely, regarding dual-registration mode or “DRM,” TS 23.501 (section 5.17.2.1) states that the UE processes independent registrations for 5GC and EPC using separate RRC connections, and that the UE maintains both (i) a 5G-GUTI, and (ii) an EPS-GUTI, independent of one another. In this DRM mode, the UE provides its native 5G-GUTI, if previously allocated by 5GC, for registrations towards the 5GC, and it provides its native EPS-GUTI, if previously allocated by EPC (Evolved Packet Core), for Attach/TAU towards the EPC. In this DRM mode, the UE may be registered: (i) to the 5GC only, (ii) to the EPC only, or (iii) to both the 5GC and EPC.
However, as referenced above, extant 3GPP 5G standards, while providing compatibility between the heterogeneous 4G/4.5G and 5G technologies, do not permit association of a given UE with more than one PLMN at a time. Specifically, in the context of the aforementioned VPLMN and HPLMN (see
In reality, many situations may exist where the 5G RAN operation/coverage/configuration is specified by one network operator or entity, and the EPC/E-UTRAN operation/coverage/configuration specified by another. These entities may not have any mechanism for coordination or communication (other than those explicitly specified as required by 3GPP). Stated differently, extant 3GPP 5G RAN standards do not anticipate the situation where the EPC/E-UTRAN and 5G RAN are split across two or more operator's networks, but rather only contemplate the situation where (i) both RANs are of a common operator, and (ii) only prescribed communication between the two PLMNs is used. As such, a hypothetical UE that could be simultaneously connected to the two different PLMNs would require the support of dual-SIMs, in effect making the UE operate as two logical UEs “glued together.”
Similarly, on the network side, two HSS (Home Subscriber Service) entities would be required (i.e., one HSS per PLMN) and both PLMNs would be operated independently with each other. Since the UE practically could only be a subscriber to one operator, managing one subscription via two distinct PLMNs requires additional operational expenditure (OPEX); i.e., to maintain communication and coordination between the two networks, since specialized communication channels and infrastructure would necessarily need to be established for such purposes.
Accordingly, improved methods and apparatus are need to enable, inter alia, “splitting” of the RANs (e.g., 4G/4.5G and 5G) across respective different networks (and network operators), such as where one RAN is associated with a first PLMN, and the second RAN is associated with another, different PLMN.
The present disclosure addresses the foregoing needs by providing, inter alia, methods and apparatus for providing multi-network registration and operation (including service/application support) for wireless mobile devices.
In one aspect, a computerized mobile device configured for use within multiple mobile network environments is disclosed. In one embodiment, the computerized mobile device includes: digital processor apparatus; first wireless interface apparatus in data communication with the digital processor apparatus and configured for wireless communication with a first radio area network (RAN) utilizing a first wireless access technology; second wireless interface apparatus in data communication with the digital processor apparatus and configured for wireless communication with a second RAN utilizing a second wireless access technology; and storage apparatus in data communication with the digital processor apparatus and comprising a storage medium, the storage medium comprising at least one computer program.
In one variant, the at least one computer program is, configured to, when executed on the digital processor apparatus: establish data communication with a first network management entity associated with the first RAN, the first network management entity associated with a first network operator and a first mobile network; and establish data communication with a second network management entity associated with the second RAN, the second network management entity associated with a second network operator and a second mobile network.
In one implementation, the first wireless access technology comprises a 3GPP Long Term Evolution (LTE)-based technology, and the second wireless access technology comprises a 3GPP New Radio (5G-NR)-based technology. The first mobile network comprises for example a home public land mobile network (HPLMN) of the computerized mobile device, and the second mobile network comprises a public land mobile network (PLMN) which the computerized mobile device is visiting.
In another variant, the at least one computer program is configured to, when executed by the digital processor apparatus, perform the establishment of the data communication with the first network management entity associated with the first RAN and the establishment of the data communication with the second network management entity associated with the second RAN contemporaneously such that at least a portion of the data communication between the computerized mobile device and the first network management entity temporally overlaps with at least a portion of the data communication between the computerized mobile device and the second network management entity.
In one implementation, the contemporaneous establishment of the data communication with the first network management entity associated with the first RAN and the data communication with the second network management entity associated with the second RAN includes maintaining at least (i) a first RRC (Radio Resource Control) connection for the data communication with the first network management entity and (ii) a second RRC (Radio Resource Control) connection for the data communication with the second network management entity.
In another variant, the computerized mobile device further includes: the subscriber identity module logic in data communication with the data processor apparatus, the subscriber identity module configured to provide data enabling the establishment of the data communication with the first network management entity; and the same subscriber identity module configured to provide data enabling the establishment of the data communication with the second network management entity. In one implementation, the subscriber identity module logic are part of a common Universal Subscriber Identity Module (USIM).
In another variant, the data enabling the establishment of the data communication with the first network management entity includes data relating to a first land mobile network (LMN), and the data enabling the establishment of the data communication with the second network management entity includes data relating to a second land mobile network (LMN).
In a further variant, the computerized mobile device includes a user equipment (UE); the first land mobile network (LMN) includes a visited public land mobile network (VPLMN) for the UE; and the second land mobile network (LMN) includes a home public land mobile network (HIPLMN) for the UE.
In yet another variant, the first network management entity and the second network management entity are not affiliated or federated.
In still another variant, the first wireless access technology includes a 3GPP Long Term Evolution (LTE)-based technology; the second wireless access technology includes a 3GPP New Radio (5G-NR)-based technology; and the computerized mobile device is further configured to support DRM (Dual Registration Mode) operation.
In another aspect of the disclosure, an enhanced UE (user equipment) apparatus, or UEe, for use within a wireless network is disclosed. In one embodiment, the UEe includes both 4G/4.5G E-UTRAN-based and 5G NR-based wireless interfaces and associated protocol stacks so as to support both: (i) DRM (Dual Registration Mode) operation, and (ii) multi-network (e.g., multi-PLMN) operation.
In another aspect of the disclosure, network apparatus for use within a wireless network is disclosed. In one embodiment, the network apparatus includes an enhanced MME (Mobility Management Entity) or MMEe, and is configured to at least recognize prescribed 5G-related network migration or transition signals from the enhanced UE (UEe) so as to enable setup of a multi-network operation environment.
In one variant, the network apparatus includes an MME (Mobility Management Entity) process configured to at least recognize one or more prescribed 3GPP 5G NR (New Radio)-based network migration or transition signals generated from one or more 3GPP 5G NR compliant UE (user equipment) to enable simultaneous operation of the UE associated with first and second distinct land mobile networks (LMNs).
In one implementation, the network apparatus is configured to utilize the 3GPP 5G NR (New Radio)-based network migration or transition signals received from the UE to cause non-inclusion of indicator data in a transmission to a network management entity process associated with the first LMN. For example, the network apparatus may include a 3GPP Long Term Evolution (LTE) Mobility Management Entity (MME) process, and the network management process may include a 3GPP compliant HSS+UDM (Home Subscriber Service and User Data Management) entity.
In another variant, the non-inclusion of indicator data in a transmission to the network management entity process associated with the first LMN results in the network management entity process not cancelling an extant registration of the UE with another 5G NR entity. In one implementation of this variant, the network apparatus includes a 3GPP Long Term Evolution (LTE) Mobility Management Entity (MME) process, the network management process includes a 3GPP compliant HSS+UDM (Home Subscriber Service and User Data Management) entity, and the another 5G NR entity comprises an AMF (Access and Mobility Management Function).
In another aspect of the disclosure, network apparatus for use within a wireless network is disclosed. In one embodiment, the network apparatus includes an enhanced HSS+UDM (Home Subscriber Service and User Data Management) entity, or HSS+UDMe, and is configured to at least to be aware of a second PLMN (or SPLMN) registering the UEe, thereby allowing the HSS+UDMe to maintain registration within the 5GS (and thereby enable setup of a multi-network operation environment).
In one variant, the network apparatus includes a 3GPP HSS+UDM (Home Subscriber Service and User Data Management) entity configured to maintain registration of a UE (user equipment) within both a first mobile network and a second mobile network simultaneously, the first mobile network comprising a 3GPP Long Term Evolution (LTE) network operated by a first network operator, and the second mobile network comprising a 3GPP 5G NR network operated by a second network operator different from the first network operator.
In one implementation, the computerized network apparatus comprises computerized logic configured for data communication with both (i) an MME (Mobility Management entity) of the LTE network, and (ii) an AMF (Access and Mobility Management Function) of the 5G NR network; and the LTE network comprises a first PLMN ID (public land mobile network identifier), and the 5G NR network comprises a second PLMN ID.
In a further aspect, a wireless network architecture is disclosed. In one embodiment, the architecture includes an HSS+UDMe and a 4G/4.5 RAN. The architecture is configured to support multi-PLMN, DRM operation by a UE (e.g., UEe). In one variant, the architecture obviates use of the N26 interface during at least such multi-PLMN operation.
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 the aforementioned HSS+UDMe or MMEe.
In another embodiment, the computer readable apparatus comprises a USIM (Universal Subscriber Identity Module), which is configured to contain at least two PLMN identifiers (e.g., MCC+MNC #1, MCC+MNC #2) relevant to maintaining connection within two different PLMNs in e.g., 4G/4.5G and 5G networks.
In yet another aspect, a system is disclosed. In one embodiment, the system includes (i) an HSS+UDMe entity, and (ii) one or more MMEe entities.
In a further aspect, a method of operating a mobile device so as to maintain connection to two or more different PLMNs is disclosed.
In yet another aspect, a method of reducing operating expenditures (OPEX) within a mobile wireless network architecture is disclosed.
In another aspect, a method of operating a wireless network infrastructure is disclosed. In one embodiment, the method includes: identifying a first registration of a user device within the wireless network infrastructure, the wireless network infrastructure operated by a first network operator; receiving data relating to a second registration of the user device within a second wireless network infrastructure operated by a second network operator; evaluating the received data relating to the second registration for prescribed data; determining that the prescribed data is not present within the received data relating to the second registration; and based at least on the determining, enabling maintenance of both the first registration and the second registration simultaneously.
In one variant of the method, the identifying comprises data communication with an AMF (Access and Mobility Management Function) of 3GPP 5G NR (New Radio) network; the receiving data comprises receiving data from an MME (Mobility Management entity) of a 3GPP LTE (Long Term Evolution) network; the LTE network comprises a first PLMN ID (public land mobile network identifier); the 5G NR network comprises a second PLMN ID; and the enabling maintenance of both the first registration and the second registration simultaneously comprises operation of the user device using both the first PLMN ID and the second PLMN ID.
These and other aspects shall become apparent when considered in light of the disclosure provided herein.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
As used herein, the term “application” (or “app”) refers generally and without limitation to a unit of executable software that implements a certain functionality or theme. The themes of applications vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment; for example, the unit could include a downloadable Java Xlet™ that runs within the JavaTV™ environment.
As used herein, the term “central unit” or “CU” refers without limitation to a centralized logical node within a wireless network infrastructure. For example, a CU might be embodied as a 5G/NR gNB Central Unit (gNB-CU), which is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the gNB that controls the operation of one or more gNB-DUs.
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, 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.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0 and 3.1.
As used herein, the term “headend” or “backend” refers generally to a networked system controlled by an operator (e.g., an MSO) that distributes programming to MSO clientele using client devices, or provides other services such as high-speed data delivery and backhaul.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet. Other common examples include but are not limited to: a network of external servers, “cloud” entities (such as memory or storage not local to a device, storage generally accessible at any time via a network connection, and the like), service nodes, access points, controller devices, client devices, etc.
As used herein, the term “LTE” refers to, without limitation and as applicable, any of the variants or Releases of the Long-Term Evolution wireless communication standard, including LTE-U (Long Term Evolution in unlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed Assisted Access), LTE-A (LTE Advanced), 4G LTE, WiMAX, VoLTE (Voice over LTE), and other wireless data standards.
As used herein, the term “memory” includes any type of integrated circuit or other storage device adapted for storing digital data including, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3D memory, and PSRAM.
As used herein, the terms “microprocessor” and “processor” or “digital processor” are meant generally to include all types of digital processing devices including, without limitation, digital signal processors (DSPs), reduced instruction set computers (RISC), general-purpose (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components.
As used herein, the terms “MSO” or “multiple systems operator” refer to a cable, satellite, or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the terms “MNO” or “mobile network operator” refer to a cellular, satellite phone, WMAN (e.g., 802.16), or other network service provider having infrastructure required to deliver services including without limitation voice and data over those mediums. The term “MNO” as used herein is further intended to include MVNOs, MNVAs, and MVNEs.
As used herein, the terms “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications technologies or networking protocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5GNR, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).
As used herein, the 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).
In one exemplary aspect, the present disclosure provides improved methods and apparatus for providing enhanced wireless services which, inter alia, enable operation of a given mobile device (e.g., a 3GPP-compliant UE) within two or more mobile networks (e.g., PLMNs) of respective different operators.
In one implementation, this enhanced functionality is provided by using the UE in so-called dual-registration mode or DRM to allow different interworking between the two networks, and by taking advantage of independent registration capability of the UE to 5GC and EPC infrastructure (i.e., by enabling the UE to register with and connect to PLMNs associated with the 5G and EPC networks). With such enhancements, a DRM-enabled UE can operate in both PLMNs (e.g., a “visited” or secondary PLMN, and a Home PLMN) simultaneously, thereby effectively providing, inter alia, umbrella 4G/4.5G coverage over one or more small-cell 5G networks, with respective independent operators of each.
For instance, in one use case, an MSO or other entity may build a small cell, data-only network with 5G capability, and partner with a “macro” MNO or MVNO for provision of voice or other services to the MSO subscribers. As such, the two entities can split or divide into two logical networks; i.e., the MNO can assume the role of the visited or secondary PLMN, while the MSO assumes the role of the HPLMN. Enhanced DRM-UEe capability as described herein advantageously allows for such services (e.g., voice service) and interworking between the macro and small-cell layers of the system without complicated network configuration requirements between the two operating networks.
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 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. 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.
Multi-PLMN Network Architecture—
As shown, an enhanced UE (UEe) 402 of the type described subsequently herein in detail is disposed to operate “within” the two RANs 202, 204, whether individually or concurrently. In the exemplary use case or operational scenario, the UEe 402 is DRM-enabled (i.e., can operate in 5G DRM) and is configured such that it can form radio technology connections with the associated RANs (i.e., form an RRC connection with the legacy E-UTRAN 409, and a similar connection with the NG-RAN 410) via relevant portions of its protocol stack and wireless interfaces, including simultaneously.
Note that as illustrated by the dashed vertical line in
Also included within PLMN1 in
In the exemplary configuration, PLMN1 is equated to the previously described HPLMN (Home PLMN) of the UEe 402, and hence PLMN1 performs such home network functions for the UEe when the latter is associated with (connected to) the 5G RAN 204.
Further shown in
In the exemplary embodiment, the DRM-enabled UEe stores a primary SPLMN application list. For example, a voice application uses the SPLMN as its primary PLMN for servicing calls, and is configured to fall back to an HPLMN as its secondary network. The DRM-enabled UEe 402 uses its designated HPLMN for data services as a default, unless they are listed in the primary SPLMN application/services list (described elsewhere herein).
As described in greater detail below with respect to
It will be appreciated that while the architecture 400 of
Likewise,
Service Provider Network—
Also provided within the architecture 500 of
The enhanced UE (UEe 402), as discussed further with respect to
Also included in the infrastructure 500 of
Moreover, it will be recognized that while the architecture 500 of
In certain embodiments, the service provider network architecture 500 also advantageously permits the aggregation and/or analysis of subscriber- or account-specific data (including inter alia, particular CU or DU or E-UTRAN eNB/femtocell devices associated with such subscriber or accounts) as 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 so as to permit or at least facilitate, among other things, (i) user/device authentication to the MSO network; (ii) correlation of aspects of the area, premises or venue where service is provided to particular subscriber capabilities, demographics, or equipment locations, such as for delivery of location-specific or targeted content or advertising; and (iii) determination of subscription level, and hence subscriber privileges and access to certain services as applicable. Moreover, device profiles for particular devices can be maintained by the MSO, such that the MSO (or its automated proxy processes) can model the device for wireless or other capabilities.
As a brief aside, a number of different identifiers are used in the NG-RAN architecture, including those of UE's (including the UEe's described herein) and for other network entities. Specifically:
The MSO network architecture 500 of
The network architecture 500 of
Alternatively, the CU's (which in effect aggregate the traffic from the various constituent DU's towards the NG Core), may have a dedicated high bandwidth “drop.”
Moreover, a given CU and DU may be co-located as desired, as shown by the combined units 504b and 504c, and 506b and 506c in
In the MSO network 500 of
The network architecture 500 of
In one exemplary content delivery paradigm, MPEG-based video content (e.g., MPEG-2, H.264/AVC) may be delivered to user IP-based client devices over the relevant physical transport (e.g., DOCSIS channels and 5G NR bearer of the respective DU 506); that is as MPEG-over-IP-over-MPEG. Specifically, the higher layer MPEG or other encoded content may be encapsulated using an IP network-layer protocol, which then utilizes an MPEG packetization/container format of the type well known in the art for delivery over the RF channels or other transport, such as via a multiplexed transport stream (MPTS). Delivery in such packetized modes may be unicast, multicast, or broadcast. Likewise, audio/telephony content can be delivered using the illustrated transport, including via other protocols such as RTP/RTCP over the bearer.
Individual devices such as cable modems 512 and associated gNB devices 504, 506 of the implementation of
The edge switch forwards the packets receive from the CMTS to the QAM modulator, which transmits the packets on one or more physical (QAM-modulated RF) channels to the “client” gNB devices. The IP packets are typically transmitted on RF channels that are different than the “in band” RF channels used for the broadcast video and audio programming, although this is not a requirement.
In one implementation, the CMs 512 shown in
In parallel with (or in place of) the foregoing delivery mechanisms, the MSO backbone 531 and other network components can be used to deliver packetized content to the “client” gNB devices 504, 506 via non-MSO networks. For example, so-called “OTT” content (whether tightly coupled or otherwise) can be ingested, stored within the MSO's network infrastructure, and delivered to the gNB CU 504 via an interposed service provider network (which may include a public Internet) 511 (e.g., at a local coffee shop, via a DU connected to the coffee shop's service provider via a modem, with the user's IP-enabled end-user device utilizing an Internet browser or MSO/third-party app to stream content according to an HTTP-based approach over the MSO backbone 531 to the third party network to the service provider modem (or optical demodulator) to the DU, and to the user device via the DU NR wireless interface.
It will further be recognized that user-plane data/traffic may also be routed and delivered apart from the CU. In one implementation (described above), the CU hosts both the RRC (control-plane) and PDCP (user-plane); however, as but one alternate embodiment, a so-called “dis-aggregated” CU may be utilized, wherein a CU-CP entity (i.e., CU—control plane) hosts only the RRC related functions, and a CU-UP (CU—user plane) which is configured to host only PDCP/SDAP (user-plane) functions. The CU-CP and CU-UP entities can, in one variant, interface data and inter-process communications via an E1 data interface, although other approaches may be used.
In certain embodiments, each DU 506 is located within and/or services one or more areas within one or more venues or residences (e.g., a building, room, or plaza for commercial, corporate, academic purposes, and/or any other space suitable for wireless access). Each DU is configured to provide wireless network coverage within its coverage or connectivity range for its RAT (e.g., 5G NR). For example, a venue may have a wireless NR modem (DU) installed within the entrance thereof for prospective customers to connect to, including those in the parking lot via inter alia, their NR or LTE-enabled vehicles or personal devices of operators thereof. Notably, different classes of DU 506 may be utilized. In practical terms, some devices may have a working range on the order of hundreds of feet, while other devices may operate out to thousands of feet or more, the propagation and working range dictated by a number of factors, including the presence of RF or other interferers, physical topology of the venue/area, energy detection or sensitivity of the receiver, etc. Similarly, different types of NR-enabled DU 506 can be used depending on these factors, whether alone or with other wireless PHYs such as LTE, WLAN, etc.
It will also be appreciated that while described primarily with respect to a unitary gNB-CU entity or device 504 as shown in
It is also noted that heterogeneous architectures of eNBs, Home eNBs or femtocells (i.e., E-UTRAN LTE/LTE-A Node B's or base stations) and gNBs may be utilized consistent with the architectures of
Moreover, the enhanced DU/CU (i.e., DUe and CUe) architectures set forth in co-owned U.S. patent application Ser. No. 15/945,657 filed Apr. 4, 2018 entitled “APPARATUS AND METHODS FOR CELL ACTIVATION IN WIRELESS NETWORKS,” and issued as U.S. Pat. No. 11,405,797 on Aug. 2, 2022, incorporated herein by reference in its entirety, may be used consistent with the various aspects of the present disclosure.
Methodology
Referring now to
Moreover, while described primarily in the context of the architecture 400 of
Similarly, per step 602b, the HSS+UDMe 430 are configured with the PLMN2 network data. In the context of the architecture 400 of
At step 604, the UEe 402 sends a Registration Request message to the AMF 446 (via the 5G RAN DU/CU). In one variant, the 5G registration procedures as defined in 3GPP TS 23.502 (Section 4.2.2.2), incorporated herein by reference in its entirety, are utilized for this step.
Additionally, per step 606, the 5G AMF 446 communicates with the HSS+UDMe430 for registration of the UEe within the 5G network.
Per step 608, the AMF 446 (and supporting components) respond to the Registration Request and provide the 5G-GUTI to the UEe 402. The received 5G-GUTI is used by the UEe within PLMN1 (in this scenario, the HPLMN 422). The AMF also provides the EPLMN list, which is used by the UEe for HPLMN reselection.
At step 610, the UEe is registered to PLMN2 (SPLMN). In one embodiment, this registration is accomplished using the EPC “attach” procedure as defined in 3GPP TS 23.401, Section 5.3.2, incorporated herein by reference in its entirety. As shown, the MME/MMEe 452 of PLMN2 (SPLMN) treats this UEe Attach Request as being of a roaming subscriber. The S6a interface 532 (see
Specifically, per step 612, the MME/MMEe 452 transmits an Update Location Request message to the HSS+UDMe 430 without the “initial attach” indication, thereby resulting in the HSS+UDMe 430 not cancelling the registration of the UEe with the AMF 446. The HSS+UDMe 430 checks the SPLMN ID from MME/MMEe identity in the Update Location Request message; if the ID matches the SPLMN list (stored in step 602b discussed supra), the HSS+UDMe will not send a message canceling registration to the 5GS.
Conversely, in instances where the MME/MMEe 452 has not been upgraded (i.e., is merely a non-inventive MME), it will ignore the “moving from 5GC” indication (data) since it does not have the capability to interpret it, and assume that it is processing an initial attach for the UEe.
In step 614, the MME/MMEe 452 initiates a session request to the SGW 450, which then utilizes the S8 interface 532 to communicate the request to the PGW 434, 436 in the HPLMN of the UEe 402 (step 616).
In step 618, the MME/MMEe 452 transmits an Attach message to the UEe 402, including the 4G/4.5G-GUTI and the EPLMN list. The received EPLMN list is in the exemplary implementation used for SPLMN reselection only. The received 4G/4.5G-GUTI is used by the UEe within the SPLMN (PLMN2).
Note that after the completion of step 618, the UEe contains two EPLMN lists (one received per step 608, and one per step 618). The SPLMN 424 (EPS) treats the UEe as a roaming subscriber from the HPLMN 422, while the UEe is also operating within its HPLMN 422 on the 5GS. As such, the UEe can operate as a DRM device within two separate PLMNs (PLMN1 and PLMN2, e.g., the HPLMN and the SPLMN, respectively).
In those instances where a non-enhanced MME is being utilized for the EPC registration, as noted above, the MME will simply ignore the “moving from 5GC” data and presume that an initial attach is underway, thereby signaling the HSS+UDMe accordingly. Advantageously, in such cases, the HSS+UDMe is configured to be aware the SPLMN identity registering the UEe 402, thereby permitting the HSS+UDMe 430 to bypass transmission of the registration cancellation to the 5GS (and hence maintain any existing AMF registration and connection).
Per step 624, the UEe 402 sends an Registration Request message to the AMF 446 (via the 5G RAN DU/CU) as previously described (see
Per step 626, the UEe 402 then completes registration with the MME/MMEe 452 of PLMN2 (SPLMN) as previously described (see
Per step 628, the applicable service or application is initiated (in this scenarios, a voice service is triggered). Per the list data of step 622, the voice service is configured to use PLMN1 (HPLMN).
Per step 630, the UEe triggers “UE triggered Service Request” procedure (e.g., such as that set forth in 3GPP TS 23.401, Section 5.3.4) to establish an EPS (4G/4.5G) bearer required for the voice service. The UEe sends the triggering Service Request to the MME/MMEe 452, which then invokes the required bearer per step 632.
OPEX Benefits—
As discussed supra, under prior art approaches, a hypothetical UE that could simultaneously connect to both PLMNs would require the support of dual SIMs/USIMs. Such dual SIM/USIM UE would operates as two logical UEs, yet aggregated into a e.g., common form factor. On the network side, two HSS entities would be required (i.e., one HSS per PLMN) and both PLMNs would be operated independently of each other. Since the UE would only be a subscriber to one operator, managing one subscription via two PLMNs would require significant additional OPEX.
As one specific example of the foregoing, in order to allow IP address preservation when the hypothetical UE switched data connections from one PLMN to another, an additional middle-layer protocol (e.g., akin to a multi-path TCP for the transport layer) in the UE with the corresponding server in the network would be required. This requirement adds additional OPEX (and also CAPEX) to the system.
Conversely, using the methods and apparatus of the present disclosure in this context, the same data anchoring point (i.e., the SMF+PGW-C) can be assigned regardless of whether the UEe is connected via PLMN2 (e.g., the SPLMN) or PLMN1 (e.g., the HPLMN) of exemplary
In addition, the above hypothetical subscriber/UE with dual SIMs/USIMs has two subscription records to be managed (i.e., one HSS from each PLMN). Accordingly, any upgrade/downgrade to the subscription profiles (e.g., allowed data throughput or types of services or applications) would have to be managed in both HSS entities. This requirement creates another OPEX requirement for subscription data synchronization between the different HSS entities from both PLMNs. Conversely, the methods and apparatus described herein obviates this issue by only using the HSS (i.e., the HSS+UDMe 430) from the UEe's HPLMN 422.
MMEe Apparatus—
In the exemplary embodiment, the processor 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 702 may also comprise an internal cache memory, and is in communication with a memory subsystem 704, 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 702.
The network interfaces 808 are configured to comply with the relevant standards which the MMEe supports (e.g., 3GPP 4G/4.5G or others as applicable) in the service area of the E-UTRAN 409, including the S6a interface to the HSS+UDMe 430, S1-MME interface to the E-UTRAN, and the S11 interface to the SGW 450 of the EPC.
The processing apparatus 702 is configured to execute at least one computer program stored in memory 704 (e.g., a non-transitory computer readable storage medium); in the illustrated embodiment, such programs include MMEe controller logic 706, such as to recognize and decode the “moving from 5G” data as part of the EPC attach procedure message (thereby indicating to the MMEe that is should not include an “initial attach” indicator in its transmission to the HSS+UDMe 430 (see discussion of step 612 of
In some embodiments, the MMEe logic 706 utilizes memory 704 or other storage 705 configured to temporarily hold a number of data relating to the various UEs (including the inventive UEe's 402). In other embodiments, application program interfaces (APIs) such as those included in an MNO-provided application or those natively available on the MMEe may also reside in the internal cache or other memory 704.
In one implementation, the MSO subscriber or client database may also optionally include the provisioning status of the particular UEe that is associated with an MSO subscriber and which is also subscribed to the MNO network (which includes the MMEe452).
HSS+UDMe Apparatus—
In the exemplary embodiment, the processor 802 of the HSS+UDMe 430 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 802 may also comprise an internal cache memory, and is in communication with a memory subsystem 804, 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 802.
The processing apparatus 802 is configured to execute at least one computer program stored in memory 804 (e.g., a non-transitory computer readable storage medium); in the illustrated embodiment, such programs include HSS+UDMe controller logic 806, such as recognize the PLMN2 (e.g., SPLMN) identity registering the UEe 402, and accordingly obviate cancellation of the UEe's registration within the 5GS (see discussion of
In some embodiments, the HSS+UDMe logic 806 utilizes memory 804 or other storage 805 configured to temporarily hold a number of data relating to the various UEe's (including UDM registration data, SPLMN ID lists, etc.) for the various functions described herein including UEe authentication and registration, SPLMN ID verification, etc.). In other embodiments, application program interfaces (APIs) such as those included in an MSO-provided application or those natively available on the HSS+UDMe may also reside in the internal cache or other memory 804. Such APIs may include common network protocols or programming languages configured to enable communication with the HSS+UDMe 430 and other network entities (e.g., via API “calls” to the HSS+UDMe by MSO network processes tasked with gathering load, configuration, subscriber, SPLMN, or other data).
The HSS+UDMe 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 808 shown in
In one exemplary embodiment, the HSS+UDMe 430 is maintained by the MSO 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+UDMe (or even UEe's utilizing the HSS+UDMe).
UEe Apparatus—
In one exemplary embodiment as shown, the UEe 402 includes, inter alia, a processor apparatus or subsystem 902, a program memory module 904, UEe logic 906 (here implemented as software or firmware operative to execute on the processor 902), and wireless interfaces 910, 920 for communications with the relevant RANs (e.g., 4G/4.5G E-UTRAN and 5G-NR RAN, respectively). The RF interfaces 910, 920 are each configured to comply with the relevant PHY standards which it supports. The antenna(s) 915, 925 of the UEe radios 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 902 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 902 may also comprise an internal cache memory. The processing subsystem is in communication with a program memory module or subsystem 904, where the latter may include memory which may comprise, e.g., SRAM, flash and/or SDRAM components. The memory module 904 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 902. A mass storage device (e.g., HDD or SSD, or NAND/NOR flash or the like) is also provided as shown.
The processor apparatus 902 is configured to execute at least one computer program stored in memory 904 (e.g., the logic of the UEe including enhanced functions of DRM and multi-RAN (and PLMN) registration and operation, in the form of software or firmware that implements the various functions described herein). Other embodiments may implement such functionality within dedicated hardware, logic, and/or specialized co-processors (not shown).
Also included in the UEe 402 is a USIM apparatus 927, which is configured to securely store (and provide ancillary processing related to) both the legacy (4G/4.5G) GUTI and the 5G GUTI, which enables the UEe to register within the two separate networks (e.g., PLMN2 and PLMN1, respectively in
In some embodiments, the UEe logic 906 also utilizes memory 904 or other storage 905 configured to temporarily hold a number of data relating to the various EPLMN lists, PLMN associations for the various services/applications such as voice, etc.) for the various functions described herein. In other embodiments, application program interfaces (APIs) such as those included in an MSO-provided application or those natively available on the UEe may also reside in the internal cache or other memory 904. Such APIs may include common network protocols or programming languages configured to enable communication with the UEe 402 and other network entities (e.g., via API “calls” to the UEe by MSO network processes tasked with gathering load, configuration, usage of SPLMNs, or other data). As an aside, a downloadable application or “app” may be available to subscribers of an MSO or cable network (and/or the general public, including MSO “partner” MNO subscribers), where the app allows users to configure their UEe via the UI to implement enhanced functionality, including data collection and reporting back to the MSO core network so as to enable, inter alia, service/RAN availability when roaming, congestion, or other attributes which may be useful in implementing e.g., the methodologies of
It will be recognized that while certain aspects of the disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the disclosure, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the disclosure disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the disclosure as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the disclosure. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the disclosure. The scope of the disclosure should be determined with reference to the claims.
It will be further appreciated that while certain steps and aspects of the various methods and apparatus described herein may be performed by a human being, the disclosed aspects and individual methods and apparatus are generally computerized/computer-implemented. Computerized apparatus and methods are necessary to fully implement these aspects for any number of reasons including, without limitation, commercial viability, practicality, and even feasibility (i.e., certain steps/processes simply cannot be performed by a human being in any viable fashion).
This application claims priority to U.S. patent application Ser. No. 16/251,999 filed Jan. 18, 2019 and entitled “APPARATUS AND METHODS FOR REGISTRATION AND OPERATION IN WIRELESS NETWORKS,” which claims priority to U.S. Provisional Patent Application Ser. No. 62/715,562 filed Aug. 7, 2018 entitled “APPARATUS AND METHODS FOR REGISTRATION AND OPERATION IN WIRELESS NETWORKS,” each of the foregoing which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3999051 | Petschauer | Dec 1976 | A |
| 4339657 | Larson et al. | Jul 1982 | A |
| 4574364 | Tabata et al. | Mar 1986 | A |
| 4604751 | Aichelmann, Jr. et al. | Aug 1986 | A |
| 4692757 | Tsuhara et al. | Sep 1987 | A |
| 4710761 | Kapur et al. | Dec 1987 | A |
| 4845644 | Anthias et al. | Jul 1989 | A |
| 4890098 | Dawes et al. | Dec 1989 | A |
| 4890257 | Anthias et al. | Dec 1989 | A |
| 5113517 | Beard et al. | May 1992 | A |
| 5121475 | Child et al. | Jun 1992 | A |
| 5129055 | Yamazaki et al. | Jul 1992 | A |
| 5155731 | Yamaguchi | Oct 1992 | A |
| 5175813 | Golding et al. | Dec 1992 | A |
| 5245615 | Treu | Sep 1993 | A |
| 5276437 | Horvath et al. | Jan 1994 | A |
| 5408602 | Giokas et al. | Apr 1995 | A |
| 5463768 | Cuddihy et al. | Oct 1995 | A |
| 5487143 | Southgate | Jan 1996 | A |
| 5502839 | Kolnick | Mar 1996 | A |
| 5522025 | Rosenstein | May 1996 | A |
| 5564002 | Brown | Oct 1996 | A |
| 5581686 | Koppolu et al. | Dec 1996 | A |
| 5596702 | Stucka et al. | Jan 1997 | A |
| 5621879 | Kohda | Apr 1997 | A |
| 5664046 | Abecassis | Sep 1997 | A |
| 5673403 | Brown et al. | Sep 1997 | A |
| 5675755 | Trueblood | Oct 1997 | A |
| 5692142 | Craycroft et al. | Nov 1997 | A |
| 5734380 | Adams et al. | Mar 1998 | A |
| 5742583 | Scott | Apr 1998 | A |
| 5764230 | Baradel et al. | Jun 1998 | A |
| 5790779 | Ben-Natan et al. | Aug 1998 | A |
| 5831609 | London et al. | Nov 1998 | A |
| 5850544 | Parvathaneny et al. | Dec 1998 | A |
| 5856826 | Craycroft | Jan 1999 | A |
| 5862316 | Hagersten et al. | Jan 1999 | A |
| 5867160 | Kraft, IV et al. | Feb 1999 | A |
| 5874960 | Mairs et al. | Feb 1999 | A |
| 5877755 | Hellhake | Mar 1999 | A |
| 5895472 | Brodsky et al. | Apr 1999 | A |
| 5973702 | Orton et al. | Oct 1999 | A |
| 5995103 | Ashe | Nov 1999 | A |
| 6031530 | Trueblood | Feb 2000 | A |
| 6092107 | Eleftheriadis et al. | Jul 2000 | A |
| 6160872 | Karnowski et al. | Dec 2000 | A |
| 6169725 | Gibbs et al. | Jan 2001 | B1 |
| 6181713 | Patki et al. | Jan 2001 | B1 |
| 6192403 | Jong et al. | Feb 2001 | B1 |
| 6216152 | Wong et al. | Apr 2001 | B1 |
| 6219044 | Ansberry et al. | Apr 2001 | B1 |
| 6233611 | Ludtke et al. | May 2001 | B1 |
| 6240555 | Shoff et al. | May 2001 | B1 |
| 6252889 | Patki et al. | Jun 2001 | B1 |
| 6313880 | Smyers et al. | Nov 2001 | B1 |
| 6317881 | Shah-Nazaroff et al. | Nov 2001 | B1 |
| 6330010 | Nason et al. | Dec 2001 | B1 |
| 6336122 | Lee et al. | Jan 2002 | B1 |
| 6337717 | Nason et al. | Jan 2002 | B1 |
| 6366876 | Looney | Apr 2002 | B1 |
| 6381710 | Kim | Apr 2002 | B1 |
| 6381735 | Hunt | Apr 2002 | B1 |
| 6397262 | Hayden et al. | May 2002 | B1 |
| 6430570 | Judge et al. | Aug 2002 | B1 |
| 6456892 | Dara-Abrams et al. | Sep 2002 | B1 |
| 6460141 | Olden | Oct 2002 | B1 |
| 6469742 | Trovato et al. | Oct 2002 | B1 |
| 6496864 | McCartney | Dec 2002 | B1 |
| 6505298 | Cerbini et al. | Jan 2003 | B1 |
| 6510152 | Gerszberg et al. | Jan 2003 | B1 |
| 6529965 | Thomsen et al. | Mar 2003 | B1 |
| 6532552 | Benignus et al. | Mar 2003 | B1 |
| 6542500 | Gerszberg et al. | Apr 2003 | B1 |
| 6542739 | Garner | Apr 2003 | B1 |
| 6546016 | Gerszberg et al. | Apr 2003 | B1 |
| 6546419 | Humpleman et al. | Apr 2003 | B1 |
| 6600958 | Zondag | Jul 2003 | B1 |
| 6606711 | Andrews et al. | Aug 2003 | B2 |
| 6625274 | Hoffpauir et al. | Sep 2003 | B1 |
| 6630943 | Nason et al. | Oct 2003 | B1 |
| 6631350 | Celi, Jr. et al. | Oct 2003 | B1 |
| 6631403 | Deutsch et al. | Oct 2003 | B1 |
| 6651248 | Alpern | Nov 2003 | B1 |
| 6654722 | Aldous et al. | Nov 2003 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6714534 | Gerszberg et al. | Mar 2004 | B1 |
| 6750879 | Sandberg | Jun 2004 | B2 |
| 6762796 | Nakajoh et al. | Jul 2004 | B1 |
| 6762798 | Messer et al. | Jul 2004 | B1 |
| 6802056 | Chaiken et al. | Oct 2004 | B1 |
| 6847649 | Sutanto | Jan 2005 | B2 |
| 6850533 | Gerszberg et al. | Feb 2005 | B2 |
| 6856330 | Chew et al. | Feb 2005 | B1 |
| 6873877 | Tobias et al. | Mar 2005 | B1 |
| 6895573 | Norgaard et al. | May 2005 | B2 |
| 6938254 | Mathur et al. | Aug 2005 | B1 |
| 6941341 | Logston et al. | Sep 2005 | B2 |
| 6944185 | Patki et al. | Sep 2005 | B2 |
| 6948175 | Fong et al. | Sep 2005 | B1 |
| 6948183 | Peterka | Sep 2005 | B1 |
| 6952836 | Donlan et al. | Oct 2005 | B1 |
| 6968364 | Wong et al. | Nov 2005 | B1 |
| 6973050 | Birdwell et al. | Dec 2005 | B2 |
| 6996808 | Niewiadomski et al. | Feb 2006 | B1 |
| 7010796 | Strom et al. | Mar 2006 | B1 |
| 7039633 | Dey et al. | May 2006 | B1 |
| 7055146 | Durr et al. | May 2006 | B1 |
| 7058964 | Khandelwal et al. | Jun 2006 | B2 |
| 7068597 | Fijolek et al. | Jun 2006 | B1 |
| 7080356 | Atallah et al. | Jul 2006 | B2 |
| 7096459 | Keller et al. | Aug 2006 | B2 |
| 7111072 | Matthews et al. | Sep 2006 | B1 |
| 7137106 | Herman et al. | Nov 2006 | B2 |
| 7146305 | Made et al. | Dec 2006 | B2 |
| 7158993 | Schwabe | Jan 2007 | B1 |
| 7181725 | Posegga et al. | Feb 2007 | B1 |
| 7194249 | Phillips et al. | Mar 2007 | B2 |
| 7203869 | Gwak | Apr 2007 | B2 |
| 7213213 | Sekiguchi et al. | May 2007 | B2 |
| 7216170 | Ludvig et al. | May 2007 | B2 |
| 7240104 | Gautney | Jul 2007 | B2 |
| 7266726 | Ladd et al. | Sep 2007 | B1 |
| 7290253 | Agesen | Oct 2007 | B1 |
| 7316003 | Dulepet et al. | Jan 2008 | B1 |
| 7328333 | Kawano et al. | Feb 2008 | B2 |
| 7370322 | Matena et al. | May 2008 | B1 |
| 7394473 | Asai | Jul 2008 | B2 |
| 7401324 | Dmitriev | Jul 2008 | B1 |
| 7478341 | Dove | Jan 2009 | B2 |
| 7487534 | Peterka et al. | Feb 2009 | B1 |
| 7546602 | Hejlsberg et al. | Jun 2009 | B2 |
| 7552450 | Evans et al. | Jun 2009 | B1 |
| 7581012 | Shiouchi et al. | Aug 2009 | B2 |
| 7698606 | Ladd et al. | Apr 2010 | B2 |
| 7814544 | Wilhelm | Oct 2010 | B1 |
| 7945902 | Sahoo | May 2011 | B1 |
| 8024607 | Ladd et al. | Sep 2011 | B2 |
| 8042113 | Clohessy et al. | Oct 2011 | B2 |
| 8046636 | Ladd et al. | Oct 2011 | B2 |
| 8265028 | Davies et al. | Sep 2012 | B2 |
| 8302111 | Ladd et al. | Oct 2012 | B2 |
| 8321723 | Ladd et al. | Nov 2012 | B2 |
| 8599797 | Pelkonen | Dec 2013 | B2 |
| 8724588 | Li et al. | May 2014 | B2 |
| 8750710 | Hirt et al. | Jun 2014 | B1 |
| 8799723 | Ladd et al. | Aug 2014 | B2 |
| 8880071 | Taaghol et al. | Nov 2014 | B2 |
| 8989297 | Lou et al. | Mar 2015 | B1 |
| 8997136 | Brooks et al. | Mar 2015 | B2 |
| 9001789 | Hosobe | Apr 2015 | B2 |
| 9185341 | Hardin | Nov 2015 | B2 |
| 9204269 | Cham et al. | Dec 2015 | B1 |
| 9300445 | Hardin | Mar 2016 | B2 |
| 9564932 | Pack et al. | Feb 2017 | B1 |
| 9596593 | Li et al. | Mar 2017 | B2 |
| 9612816 | Choi et al. | Apr 2017 | B2 |
| 9654149 | Piipponen et al. | May 2017 | B2 |
| 9706512 | Suh | Jul 2017 | B2 |
| 9948349 | Malach | Apr 2018 | B2 |
| 10009431 | Holtmanns | Jun 2018 | B2 |
| 10164858 | Gunasekara et al. | Dec 2018 | B2 |
| 10375629 | Zhang | Aug 2019 | B2 |
| 10506499 | Keller et al. | Dec 2019 | B2 |
| 11044597 | Wong et al. | Jun 2021 | B2 |
| 11129213 | Vaidya et al. | Sep 2021 | B2 |
| 11405797 | Vaidya et al. | Aug 2022 | B2 |
| 11564155 | Wong et al. | Jan 2023 | B2 |
| 20010007138 | Iida et al. | Jul 2001 | A1 |
| 20010049691 | Asazu | Dec 2001 | A1 |
| 20020009149 | Rodriguez et al. | Jan 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020034193 | Patki et al. | Mar 2002 | A1 |
| 20020038358 | Sweatt, III et al. | Mar 2002 | A1 |
| 20020040470 | Guthrie et al. | Apr 2002 | A1 |
| 20020044567 | Voit et al. | Apr 2002 | A1 |
| 20020044569 | Kwok et al. | Apr 2002 | A1 |
| 20020049978 | Rodriguez et al. | Apr 2002 | A1 |
| 20020052977 | Stall | May 2002 | A1 |
| 20020073244 | Davies et al. | Jun 2002 | A1 |
| 20020083214 | Heisig et al. | Jun 2002 | A1 |
| 20020112090 | Bennett et al. | Aug 2002 | A1 |
| 20020126144 | Chenede | Sep 2002 | A1 |
| 20020144193 | Hicks et al. | Oct 2002 | A1 |
| 20020170033 | Chen | Nov 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020174433 | Baumgartner et al. | Nov 2002 | A1 |
| 20020191028 | Senechalle et al. | Dec 2002 | A1 |
| 20020198868 | Kinzhalin et al. | Dec 2002 | A1 |
| 20030005454 | Rodriguez et al. | Jan 2003 | A1 |
| 20030009765 | Linden et al. | Jan 2003 | A1 |
| 20030009769 | Hensgen et al. | Jan 2003 | A1 |
| 20030037331 | Lee | Feb 2003 | A1 |
| 20030041291 | Hashem et al. | Feb 2003 | A1 |
| 20030056155 | Austen et al. | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061240 | McCann et al. | Mar 2003 | A1 |
| 20030081664 | Lu et al. | May 2003 | A1 |
| 20030105995 | Schroath et al. | Jun 2003 | A1 |
| 20030107604 | Ording | Jun 2003 | A1 |
| 20030110331 | Kawano et al. | Jun 2003 | A1 |
| 20030110511 | Schutte et al. | Jun 2003 | A1 |
| 20030121055 | Kaminski et al. | Jun 2003 | A1 |
| 20030122879 | Inui et al. | Jul 2003 | A1 |
| 20030140285 | Wilkie | Jul 2003 | A1 |
| 20030163811 | Luehrs | Aug 2003 | A1 |
| 20030181241 | Oakes et al. | Sep 2003 | A1 |
| 20030188320 | Shing | Oct 2003 | A1 |
| 20030204848 | Cheng et al. | Oct 2003 | A1 |
| 20030217197 | Chan et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030229899 | Thompson et al. | Dec 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20030231855 | Gates et al. | Dec 2003 | A1 |
| 20040003400 | Carney et al. | Jan 2004 | A1 |
| 20040034697 | Fairhurst et al. | Feb 2004 | A1 |
| 20040040041 | Crawford | Feb 2004 | A1 |
| 20040073944 | Booth | Apr 2004 | A1 |
| 20040078695 | Bowers et al. | Apr 2004 | A1 |
| 20040078829 | Patel et al. | Apr 2004 | A1 |
| 20040083464 | Cwalina et al. | Apr 2004 | A1 |
| 20040098730 | Foote et al. | May 2004 | A1 |
| 20040103434 | Ellis | May 2004 | A1 |
| 20040107451 | Khandelwal et al. | Jun 2004 | A1 |
| 20040143836 | McCormack et al. | Jul 2004 | A1 |
| 20040158829 | Beresin et al. | Aug 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040186603 | Sanford et al. | Sep 2004 | A1 |
| 20040187152 | Francis et al. | Sep 2004 | A1 |
| 20040199903 | Iizuka | Oct 2004 | A1 |
| 20040205339 | Medin | Oct 2004 | A1 |
| 20040218736 | Fang et al. | Nov 2004 | A1 |
| 20040236759 | Young | Nov 2004 | A1 |
| 20040261092 | Addington et al. | Dec 2004 | A1 |
| 20040261114 | Addington et al. | Dec 2004 | A1 |
| 20040261116 | McKeown et al. | Dec 2004 | A1 |
| 20040261126 | Addington et al. | Dec 2004 | A1 |
| 20050015799 | Park | Jan 2005 | A1 |
| 20050021766 | McKeowen et al. | Jan 2005 | A1 |
| 20050027851 | McKeown et al. | Feb 2005 | A1 |
| 20050063317 | Risberg et al. | Mar 2005 | A1 |
| 20050071818 | Reissman et al. | Mar 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050120385 | Stalker | Jun 2005 | A1 |
| 20050132346 | Tsantilis | Jun 2005 | A1 |
| 20050160045 | Watanabe et al. | Jul 2005 | A1 |
| 20050162267 | Khandelwal et al. | Jul 2005 | A1 |
| 20050177832 | Chew | Aug 2005 | A1 |
| 20050273762 | Lesh | Dec 2005 | A1 |
| 20060005183 | Minear et al. | Jan 2006 | A1 |
| 20060020950 | Ladd et al. | Jan 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060070051 | Kuck et al. | Mar 2006 | A1 |
| 20060129947 | Hamzy et al. | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060143492 | Leduc et al. | Jun 2006 | A1 |
| 20060161946 | Shin | Jul 2006 | A1 |
| 20070094345 | Rabbers et al. | Apr 2007 | A1 |
| 20070207771 | Bowser et al. | Sep 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070261090 | Miller et al. | Nov 2007 | A1 |
| 20070288897 | Branda et al. | Dec 2007 | A1 |
| 20070294673 | Guerrera et al. | Dec 2007 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080101291 | Jiang et al. | May 2008 | A1 |
| 20080178153 | Fox et al. | Jul 2008 | A1 |
| 20080196011 | Bhandari et al. | Aug 2008 | A1 |
| 20080256510 | Auerbach | Oct 2008 | A1 |
| 20080288930 | Chen et al. | Nov 2008 | A1 |
| 20090176490 | Kazmi et al. | Jul 2009 | A1 |
| 20090222867 | Munetsugu | Sep 2009 | A1 |
| 20100008235 | Tinnakornsrisuphap et al. | Jan 2010 | A1 |
| 20100035610 | Narang et al. | Feb 2010 | A1 |
| 20100178912 | Gunnarsson et al. | Jul 2010 | A1 |
| 20110117917 | Gresset et al. | May 2011 | A1 |
| 20110124335 | Martin et al. | May 2011 | A1 |
| 20110207456 | Radulescu et al. | Aug 2011 | A1 |
| 20120076009 | Pasko | Mar 2012 | A1 |
| 20120224563 | Zisimopoulos et al. | Sep 2012 | A1 |
| 20120246255 | Walker et al. | Sep 2012 | A1 |
| 20120275315 | Schlangen et al. | Nov 2012 | A1 |
| 20130156115 | Petrovic | Jun 2013 | A1 |
| 20130178225 | Jul 2013 | A1 | |
| 20130201316 | Binder et al. | Aug 2013 | A1 |
| 20130247027 | Shah et al. | Sep 2013 | A1 |
| 20130252616 | Murakami | Sep 2013 | A1 |
| 20130267229 | Gopalakrishnan | Oct 2013 | A1 |
| 20130279914 | Brooks | Oct 2013 | A1 |
| 20130322504 | Asati et al. | Dec 2013 | A1 |
| 20140105028 | Bhaskaran et al. | Apr 2014 | A1 |
| 20140148107 | Maltsev et al. | May 2014 | A1 |
| 20140226606 | Nishigori et al. | Aug 2014 | A1 |
| 20140282704 | Tumuluru et al. | Sep 2014 | A1 |
| 20140282802 | Bowler et al. | Sep 2014 | A1 |
| 20140308986 | Yang et al. | Oct 2014 | A1 |
| 20140354442 | Maity et al. | Dec 2014 | A1 |
| 20140370895 | Pandey et al. | Dec 2014 | A1 |
| 20150085853 | Smith et al. | Mar 2015 | A1 |
| 20150156777 | Negus et al. | Jun 2015 | A1 |
| 20150195754 | Zhang et al. | Jul 2015 | A1 |
| 20150201088 | Wu et al. | Jul 2015 | A1 |
| 20150208290 | Seo et al. | Jul 2015 | A1 |
| 20150229584 | Okamoto et al. | Aug 2015 | A1 |
| 20150365178 | Maattanen et al. | Dec 2015 | A1 |
| 20160007138 | Palanisamy et al. | Jan 2016 | A1 |
| 20160013855 | Campos et al. | Jan 2016 | A1 |
| 20160020835 | Stadelmeier et al. | Jan 2016 | A1 |
| 20160021595 | Czaja et al. | Jan 2016 | A1 |
| 20160073344 | Vutukuri et al. | Mar 2016 | A1 |
| 20160094421 | Bali et al. | Mar 2016 | A1 |
| 20160128072 | Rajagopal et al. | May 2016 | A1 |
| 20160212632 | Katamreddy et al. | Jul 2016 | A1 |
| 20160259923 | Papa et al. | Sep 2016 | A1 |
| 20160373974 | Gomes et al. | Dec 2016 | A1 |
| 20170019144 | Malach | Jan 2017 | A1 |
| 20170094527 | Shattil et al. | Mar 2017 | A1 |
| 20170111846 | Kang | Apr 2017 | A1 |
| 20170149937 | Ren et al. | May 2017 | A1 |
| 20170155703 | Hao et al. | Jun 2017 | A1 |
| 20170164234 | Kalapatapu et al. | Jun 2017 | A1 |
| 20170201912 | Zingler et al. | Jul 2017 | A1 |
| 20170208488 | Hwang | Jul 2017 | A1 |
| 20170208540 | Egner et al. | Jul 2017 | A1 |
| 20170245281 | Zuckerman et al. | Aug 2017 | A1 |
| 20170265220 | Andreoli-Fang | Sep 2017 | A1 |
| 20170311247 | Qi et al. | Oct 2017 | A1 |
| 20170316233 | Kherani et al. | Nov 2017 | A1 |
| 20170359759 | Brown et al. | Dec 2017 | A1 |
| 20180063813 | Gupta | Mar 2018 | A1 |
| 20180092142 | Han et al. | Mar 2018 | A1 |
| 20180098245 | Livanos et al. | Apr 2018 | A1 |
| 20180146408 | Meylan et al. | May 2018 | A1 |
| 20180184337 | Jin et al. | Jun 2018 | A1 |
| 20180213452 | Kim et al. | Jul 2018 | A1 |
| 20180288657 | Stojanovski et al. | Oct 2018 | A1 |
| 20180316563 | Kumar et al. | Nov 2018 | A1 |
| 20180331935 | Ross et al. | Nov 2018 | A1 |
| 20180338277 | Byun et al. | Nov 2018 | A1 |
| 20180343685 | Hart et al. | Nov 2018 | A1 |
| 20180351665 | Fukuta et al. | Dec 2018 | A1 |
| 20180351809 | Meredith et al. | Dec 2018 | A1 |
| 20180375887 | Dezent et al. | Dec 2018 | A1 |
| 20190007870 | Gupta et al. | Jan 2019 | A1 |
| 20190053193 | Park et al. | Feb 2019 | A1 |
| 20190075023 | Sirotkin | Mar 2019 | A1 |
| 20190082501 | Vesely et al. | Mar 2019 | A1 |
| 20190109643 | Campos et al. | Apr 2019 | A1 |
| 20190124572 | Park et al. | Apr 2019 | A1 |
| 20190124696 | Islam et al. | Apr 2019 | A1 |
| 20190141586 | Olsson | May 2019 | A1 |
| 20190158975 | Petersen | May 2019 | A1 |
| 20190208380 | Shi et al. | Jul 2019 | A1 |
| 20190229974 | Campos et al. | Jul 2019 | A1 |
| 20190245740 | Kachhla | Aug 2019 | A1 |
| 20190253944 | Kim | Aug 2019 | A1 |
| 20190261264 | Lou | Aug 2019 | A1 |
| 20190289470 | Vaidya et al. | Sep 2019 | A1 |
| 20190313311 | Huang-Fu | Oct 2019 | A1 |
| 20190319814 | Das | Oct 2019 | A1 |
| 20190319858 | Das et al. | Oct 2019 | A1 |
| 20190320250 | Hoole et al. | Oct 2019 | A1 |
| 20190320322 | Jayawardene et al. | Oct 2019 | A1 |
| 20190320494 | Jayawardene et al. | Oct 2019 | A1 |
| 20190349848 | Bali | Nov 2019 | A1 |
| 20190356743 | Park et al. | Nov 2019 | A1 |
| 20190357037 | Velev | Nov 2019 | A1 |
| 20190357199 | Ali et al. | Nov 2019 | A1 |
| 20190379455 | Wang et al. | Dec 2019 | A1 |
| 20200068481 | Kim et al. | Feb 2020 | A1 |
| 20200091608 | Alpman et al. | Mar 2020 | A1 |
| 20200107213 | Park | Apr 2020 | A1 |
| 20200120724 | Vaidya et al. | Apr 2020 | A1 |
| 20200154388 | Koshimizu | May 2020 | A1 |
| 20200196199 | Sharma et al. | Jun 2020 | A1 |
| 20200214065 | Tomala et al. | Jul 2020 | A1 |
| 20200221464 | Nielsen et al. | Jul 2020 | A1 |
| 20200280836 | Velev | Sep 2020 | A1 |
| 20200342311 | Peroulas et al. | Oct 2020 | A1 |
| 20210029608 | Dodd-Noble et al. | Jan 2021 | A1 |
| 20210029759 | Tang | Jan 2021 | A1 |
| 20210176665 | Lan et al. | Jun 2021 | A1 |
| 20210281993 | Tiwari | Sep 2021 | A1 |
| 20210345161 | Zhu | Nov 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 105071860 | Nov 2015 | CN |
| 0812119 | Dec 1997 | EP |
| 2548796 | Oct 2017 | GB |
| 2006325206 | Nov 2006 | JP |
| 2011254495 | Dec 2011 | JP |
| 2017118483 | Jun 2017 | JP |
| 20160097917 | Aug 2016 | KR |
| WO-2004045125 | May 2004 | WO |
| WO-2015147707 | Oct 2015 | WO |
| WO-2017186294 | Nov 2017 | WO |
| WO-2018131488 | Jul 2018 | WO |
| Entry |
|---|
| 3GPP TS 38.473 V15.1.1 (Apr. 2018) “3rd Generation Partnership Project; Technical Specification Group Radio Access Network,” TS 38.473 (v15.0.0), Dec. 2017, NG-RAN, F1 application protocol (F1AP), Release 15, 90 pages. |
| 3GPP TS 23.502 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2; v. 16.0.0, (Mar. 2019) 420 pages. |
| IEEE 802.11 standard, 1997, URL: http://www.ieeexplore.ieee.org/documenU654779 , 459 pages. |
| Maamoun K. M. et al., “A Survey and a Novel Scheme for RoF-PON as FTTx Wireless Services,” 2009 6th InternationalSymposium on High Capacity Optical Networks and EnablingTechnologies(HONET), IEEE, 2009, pp. 246-253. |
| Wi-Fi Direct, “Wi-Fi Peer-to-Peer (P2P) Specification,” Wi-Fi Alliance, Version 1.5, 2014, 183 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210314762 A1 | Oct 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62715562 | Aug 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16251999 | Jan 2019 | US |
| Child | 17353605 | US |
