A wireless base station receives a radio resource control (rrc) message having a Vehicle-to-X (V2X) service indicator from a user equipment (ue) and transfers a ue message to a network core that serves the ue with the V2X service. The wireless base station receives another rrc message having a text/multimedia messaging service indicator from another ue and transfers a ue message to a different network core that serves the other ue with the text/multimedia messaging service. The wireless base station receives another rrc message having a video conferencing service indicator from a ue and transfers a ue message to yet another network core that serves the ue with the video conferencing service.
|
11. A wireless base station in a multi-core data communication network, the wireless base station comprising:
transceiver circuitry configured to wirelessly receive a first radio resource control (rrc) message having a Vehicle-to-X (V2X) service indicator from a first user equipment (ue), wirelessly receive a second rrc message having a text/multimedia messaging service indicator from a second ue, and wirelessly receive a third rrc message having a video conferencing service indicator from a third ue; and
processing circuitry configured to transfer a first ue message for the first ue to a first network core that serves the first ue with the V2X service responsive to the first ue message, transfer a second ue message for the second ue to a second network core that serves the second ue with the text/multimedia messaging service responsive to the second ue message, and transfer a third ue message for the third ue to a third network core that serves the third ue with the video conferencing service responsive to the third ue message.
1. A method of operating a wireless base station in a multi-core data communication network, the method comprising:
the wireless base station wirelessly receiving a first radio resource control (rrc) message having a Vehicle-to-X (V2X) service indicator from a first user equipment (ue) and responsively transferring a first ue message for the first ue to a first network core that serves the first ue with the V2X service responsive to the first ue message;
the wireless base station wirelessly receiving a second rrc message having a text/multimedia messaging service indicator from a second ue and responsively transferring a second ue message for the second ue to a second network core that serves the second ue with the text/multimedia messaging service responsive to the second ue message; and
the wireless base station wirelessly receiving a third rrc message having a video conferencing service indicator from a third ue and responsively transferring a third ue message for the third ue to a third network core that serves the third ue with the video conferencing service responsive to the third ue message.
3. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
10. The method of
13. The wireless base station of
15. The wireless base station of
16. The wireless base station of
17. The wireless base station of
18. The wireless base station of
19. The wireless base station of
20. The wireless base station of
|
|||||||||||||||||||||||||||
This United States Patent Application is a continuation of U.S. patent application Ser. No. 15/198,265 that was filed on Jun. 30, 2016 and is entitled, DATA COMMUNICATIONS OVER A DISTRIBUTED MULTI-CORE LONG TERM EVOLUTION (LTE) NETWORK.” U.S. patent application Ser. No. 15/198,265 is hereby incorporated by reference into this United States Patent Application.
Data communication systems exchange user data with User Equipment (UEs) to provide various data communication services. The UEs may be phones, computers, media players, and the like. The data communication services may be Internet access, voice/video calling, messaging, evolved Multimedia Broadcast Multicast Service (eMBMS), location-based services, local bulletin (news/traffic/weather), vehicle services (V2X), group communications, enterprise access, or some other computerized information services.
A popular wireless communication technology is Long Term Evolution (LTE). LTE networks use wireless base stations called evolved Node Bs (eNodeBs) to connect the UEs to LTE network cores. The LTE network cores comprise network elements like mobility managers, gateways, controllers, routers, databases, and servers. The LTE network cores exchange user data with the user devices over the eNodeBs to serve out the various data services.
The UEs are typically attached to the proximate LTE network core. The UEs typically switch from one LTE network core to another when they transit large distances. In some examples, a special UE ID may be used to identify and attach a special UE to a special LTE network core that provides a special data service. These special LTE network cores are not readily scalable in an open system. Unfortunately, wireless base stations do not yet efficiently and effectively attach UEs to LTE network cores in a complex multi-service, multi-core LTE environment.
A wireless base station receives a Radio Resource Control (RRC) message having a Vehicle-to-X (V2X) service indicator from a User Equipment (UE) and transfers a UE message to a network core that serves the UE with the V2X service. The wireless base station receives another RRC message having a text/multimedia messaging service indicator from another UE and transfers a UE message to a different network core that serves the other UE with the text/multimedia messaging service. The wireless base station receives another RRC message having a video conferencing service indicator from a UE and transfers a UE message to yet another network core that serves the UE with the video conferencing service.
UEs 101-102 could be computers, phones, media players, or some other intelligent machines. Wireless base station 110 could be an evolved Node B (eNodeB), Wireless Fidelity (WIFI) hotspot, LTE relay, 5G base station, or some other wireless access point. LTE network cores 121-123 comprise communication network elements like gateways, controllers, routers, databases, and servers. The elements of data communication system 100 (101-102, 110, 121-123) each comprise data processing circuitry, data memory, data communication transceivers, and operating software.
In operation, LTE core networks 121-123 transfer core service data to wireless base station 110 to identify the data services for each network core. The core service data may be organized into bit strings (CORE121:110010101 . . . ) to efficiently identify the status of data services at the core by the one or zero and its placement in the string. The core service data may also indicate a class or type of core, such as enterprise, V2X, full service, and the like.
Wireless base station 110 aggregates and correlates the received data into core service data structure 111 that individually associates representative data services A-I with LTE network cores 121-123. LTE core 121 is associated with individual data services A, B, and C, D, and E. LTE core 122 is associated with individual data services A, F, and G. LTE core 122 is associated with individual data services A, H, and I.
Upon attachment or UE request, wireless base station 110 transfers UE service data to UEs 101-102 indicating available data services A-I that are indicated in data structure 111. The transfer may occur over Access Stratum (AS) information blocks or Non-Access Stratum (NAS) data files. For example, upon initial attachment to a default core, wireless base station 110 may transfer the UE service data to UE 101 for subsequent service requests. The UE service data may also use bit strings to efficiently identify the UE data services that are available over wireless base station 110.
Some UEs may not be authorized for all data services. UEs 101-102 are typically subscribed to individual data services, so LTE network cores 121-123 should have the appropriate UE context for UE service authorizations. Consider an example where wireless base station 110 receives a UE service request for data service B from UE 101. The UE service request may be Radio Resource Connect (RRC) message with a Service Feature Indicator (SFI) that indicates the data service B. The UE service request may have an indicator bit that identifies the presence of SFI in the request and may also use a bit strings to efficiently identify the requested data service. Note that the RRC Connect message also includes the standard Establishment Cause in addition to the SFI.
Wireless base station 110 enters core service data structure 111 with data service B which yields LTE network cores 121, 131, and 141. Wireless base station 110 selects LTE network core 121 over cores 131 and 141 based on factors like proximity, loading, UE ID, quality-of-service, or some other metric. In response to the selection of LTE network core 121, wireless base station 110 transfers a UE message that indicates UE 101 and data service B to selected LTE network core 121. The UE message may be an S1-MME Initial UE message, and wireless base station 110 could transfer the S1-MME Initial UE message to an LTE Mobility Management Entity (MME) in LTE network core 121.
Consider another example where wireless base station 110 receives a UE service request for data service H from UE 102. The UE service request may be an RRC message with the standard Establishment Cause plus an SFI bit string that indicates data service H. Wireless base station 110 enters core service data structure 111 with data service H which yields LTE network cores 123, 133, and 143. Wireless base station 110 selects LTE network core 123 over cores 133 and 143 based on factors like proximity, loading, UE ID, quality-of-service, or some other attribute. In response to the selection of LTE network core 123, wireless base station 110 transfers a UE message that indicates UE 101 and data service H to selected LTE network core 123. The UE message may be an S1-MME Initial UE message to an MME in LTE network core 123.
LTE network cores vary. Some LTE cores may have multiple MMEs that share a Serving Gateway (S-GW) and a Packet Data Network Gateway (P-GW). Other cores may have multiple MMEs and S-GWs share a P-GW. Some LTE cores have direct access to a Home Subscriber System (HSS) and/or Policy Charging Rules Function (PCRF) while other cores have indirect access through another core. Most cores have direct Internet access although some cores have indirect Internet access through another core. LTE network cores 121-123 may include various combinations of V2X servers, eMBMS servers, group communication servers, enterprise servers, and the like.
In some examples, LTE network cores 121-123 comprise Network Function Virtualization Infrastructures (NFVIs) that execute Network Function Virtualization (NFV) Virtual Network Functions (VNFs). These NFV VNFs may comprise Software-Defined Network (SDN) applications and controllers. In turn, the NFV VNFs and SDN applications may comprise base station controllers, MMEs, S-GWs, P-GWs, HSS, PCRF, V2X servers, eMBMS servers, group communication servers, local bulletin servers, and enterprise servers. In these examples, data structure 111 can be expanded to individually associate the data services with NFVIs, NFV Network Service Descriptors (NSDs), VNF Forwarding Graphs (VNFFGs), and/or SDN applications that are also individually associated with one or more LTE network cores.
Wireless base station 110 then receives a UE service request for a data service from a UE (204). If an RRC Connect message is used, the message will also include the standard Establishment Cause in addition to the SFI. Wireless base station 110 enters the core service data structure with the data service identified by the UE to yield one or more selected LTE network cores for the data service (205). If multiple cores are available, wireless base station 110 selects one of the cores based on factors like proximity, loading, quality, or UE ID. In response to the LTE core selection (206), wireless base station 110 transfers a UE message that indicates the UE and the data service to the selected LTE network core (207-209). If LTE network core 121 is selected (206), then network core 121 implements the identified data service responsive to the UE message from wireless base station 110 (207). If LTE network core 122 is selected (206), then network core 122 implements the identified data service responsive to the UE message from wireless base station 110 (208). If network core 123 is selected (206), then core 123 implements the identified data service responsive to the UE message from wireless base station 110 (209).
Upon attachment, wireless base station 110 transfers UE service data to UE 101 indicating the available data services. The transfer may use bit strings and occur over AS or NAS information blocks. For example, upon initial attachment to wireless base station 110 and a default core, wireless base station 110 may transfer a bit sequence comprising the UE service data for UE 101.
Wireless base station 110 subsequently receives a UE service request for data service E from UE 101. The UE service request may be an RRC message with the standard Establishment Cause in addition to an SFI that indicates the data service. The UE service request may have an indicator bit that identifies the presence of SFI in the request and may also use a bit string to efficiently identify the requested data service.
In this example, UE 101 requests data service E. Wireless base station 110 enters core service data structure 111 with data service E and to yield LTE network core 121. In response to the core selection, wireless base station 110 transfers a UE message that indicates UE 101 and data service E to LTE network core 121. The UE message may be an S1-MME Initial UE message to an LTE MME in LTE network core 121. If UE 101 is subscribed to data service E, selected LTE network core 121 should have the appropriate UE 101 context for UE service authorization. If UE 101 is authorized for service E, LTE network core 121 provides data service E to UE 101 per the UE message from wireless base station 110.
After UE 102 attaches, wireless base station 110 transfers UE service data indicating the available data services. Wireless base station 110 receives a UE service request for data service F from UE 102. The UE service request may be an RRC message with an SFI that indicates the data service F. Wireless base station 110 enters core service data structure 111 with data service F which yields LTE network core 122. In response to the core selection, wireless base station 110 transfers a UE message that indicates UE 101 and data service F to LTE network core 122. If UE 102 is authorized for service F, LTE network core 122 provides data service F to UE 102 per the UE message from wireless base station 110.
The core layer has edge cores, mid cores, and central cores. The edge cores are usually smaller and may be deployed along roads or in special purpose locations. The edge cores manage services like internet access (INET), V2X, local bulletin, and group communications. The mid cores are larger than edge cores and are typically near suburbs, campuses, and large enterprises. The mid cores manage services like INET, Short Messaging Service (SMS), Multimedia Messaging Service (MMS), evolved Multimedia Broadcast Multicast Service (eMBMS), Location-Based Services (LBS). The central cores are larger than mid cores and are typically in dense urban areas. The central cores manage all services including INET, voice/video conferencing, enterprise services, V2X, local bulletin, group communications, SMS/MMS, eMBMS, and LBS.
In operation, the core layer transfers core service data to the eNodeB layer. The core service data associates each LTE core with the individual data services that are served from that core. The eNodeB layer aggregates and correlates the core service data into a data structure that associates the specific data services with the individual network cores as indicated above. Upon UE attachment and/or UE request, the eNodeB layer transfers UE service data to the UE layer. The UE service data indicates the available data services like V2X, eMBMS, voice calling, and the like.
The UE service applications (APPS) in the UE layer transfer UE service requests to the eNodeB layer. For example, an eMBMS smartphone APP may direct the phone to transfer an eMBMS service request to the eNodeB layer. The service requests from the UE layer comprise RRC messages with standard Establishment Causes and also with the SFIs to indicate the requested data services.
The eNodeB layer enters its core service data structures with the requested data services to yield the available LTE network cores for the requested data services. The eNodeB layer selects network cores from those available and directs the UE service requests to the selected LTE network cores. Final network core selection is based on proximity, loading, and UE quality-of-service. The UE service requests from the eNodeB layer to the core layer are S1-MME Initial UE messages to MMEs in the selected LTE network cores. The MMEs direct the implementation of the requested data services responsive to the S1-MME Initial UE messages.
Many LTE network cores comprise NFVIs that execute NFV VNFs. These NFV VNFs comprise SDN applications and controllers. In turn, the SDN application VNFs comprise base-band units, base station controllers, MMEs, S-GWs, P-GWs, HSS, PCRF, V2X servers, eMBMS servers, group communication servers, local bulletin servers, enterprise servers, and the like. The available NFVIs, NFV NSDs, VNF Forwarding Graphs VNFFGs, and/or SDN applications may be individually associated with specific data services in the core services data structures at the eNodeB layer. Thus, the eNodeB layer may process a UE service request to select an available network core based on a specific VNGFG that is operating in the selected network core. The eNodeB layer may process the UE service request to select an available network core based on a specific SDN application VNF that is executing in the selected network core.
The NFVIs execute virtual layer software to provide a virtualized processing environment. Under the control of the MANO system, the virtual layers execute various SDN VNFs. In the edge, mid, and core NFVIs, the virtual layers execute UE SDN virtual switch (vSW) VNFs, UE SDN controller (CNT) VNFs, and UE SDN application (APP) VNFs. In the MANO NFVI, the virtual layer executes MANO SDN vSW VNFs, MANO SDN CNT VNFs, MANO SDN APP VNFs. The MANO VNFs transfer networking data to the edge, mid, and core NFVI virtual layers to drive the execution of the UE SDN VNFs. The UE SDN APP VNFs in the edge NFVIs include a multitude of base station controller VNFs.
The UE SDN APP VNFs for LTE core networks 501-530 transfer core service data to the UE SDN APP base station controller VNFs in the edge NFVIs. The core service data identifies the individual data services for each LTE core, NFVI, NFV NS SD, VNFFG, and SDN APP VNF. UE SDN APP base station controller VNFs in the edge NFVIs aggregate and correlate the received data into core service data structures that individually associate LTE network cores 501-530 with individual data services and other NFV/SDN data.
Upon UE attachment, an SDN APP base station controller VNF transfers UE service data to the UE indicating the available data services at that base station. The SDN APP base station controller VNF receives a UE service request from the attached UE for one of the data services. In this example, the UE requests a video conferencing data service. The SDN APP base station controller VNF enters its core service data structure with a video conferencing service ID to yield LTE network cores 512-513, 517-518, and 531-532. The SDN APP base station controller VNF selects LTE network core 513 based on loading and proximity data for the video conferencing data service. In response to the LTE core 513 selection, the SDN APP base station controller VNF transfers a UE message that identifies the UE and the video conferencing data service to a UE SDN APP MME VNF in LTE network core 513. If the UE is authorized, the VNFs for LTE network core 513 serve the video conferencing data service to the UE according to the UE message from the base station controller VNF.
The UE SDN APP VNFs for LTE core 513 exchange signaling (typically with other cores) to establish the video conference between the UEs. Some of the UE SDN video conference APP VNFs transfer SDN controller API calls for the video conference to their associated UE SDN controller VNFs. The UE SDN controller VNFs transfer SDN data machine API calls to the SDN switches. The SDN switches and wireless base stations transfer the user video data between the UEs. If needed, an SDN video conference application VNF may direct an SDN controller VNF to drive an SDN data machine to deliver user video data to an NFVI for heavier processing like transcoding, decryption, or the like.
In another example, the SDN APP base station controller VNF receives a UE service request from the attached UE for a V2X data service. The SDN APP base station controller VNF enters its core service data structure with a V2X service ID to yield LTE network cores 504, 509, 514, 519, and 529-530. The SDN APP base station controller VNF selects LTE network core 504 based on its proximity (in the same NFVI) for the V2X data service. In response to the LTE core 504 selection, the SDN APP base station controller VNF transfers a UE message that identifies the UE and the V2X service to a UE SDN APP MME VNF in LTE network core 504. If the UE 101 is authorized, the UE SDN V2X APP VNF for LTE core 504 exchanges signaling (possibly with other cores) to establish the V2X service for the UE.
In particular, the UE SDN V2X APP VNF transfers SDN controller API calls for the V2X service to their associated UE SDN controller VNF. The UE SDN controller VNF transfers SDN data machine API calls to the edge SDN switch with the base station. The SDN switch and base station exchanges user V2X data with the UE. The UE SDN V2X APP VNF in LTE core 504 handles the V2X user data.
Data machine transceivers 621-624 comprise communication components, such as ports, bus interfaces, signal processors, memory, software, and the like. Processing circuitry 603 comprises server blades, circuit boards, bus interfaces, integrated circuitry, and associated electronics. Storage system 604 comprises non-transitory, machine-readable, data storage media, such as flash drives, disc drives, memory circuitry, servers, and the like. Software 605 comprises machine-readable instructions that control the operation of processing circuitry 603 when executed. Software 605 includes software modules 606-611. NFV/SDN server 600 may be centralized or distributed. All or portions of software 606-611 may be externally stored on one or more storage media, such as circuitry, discs, and the like. Some conventional aspects of SDN server 600 are omitted for clarity, such as power supplies, enclosures, and the like.
When executed by processing circuitry 603, software modules 606-611 direct circuitry 603 to perform the following operations. eNodeB SDN application VNF modules 606 drive base station operations including the correlation of core service data, transfer of service data to UEs, and translation of user-requested data services to LTE network cores. LTE core SDN application VNF modules 607 drive core network operations like mobility management and gateway security—including the transfer of core service data to eNodeB SDN application VNF modules 606. SDN vSW modules 608 provide SDN north and west interfaces to VNF modules 606-607. SDN vSW modules 608 provide SDN south and east interfaces to SDN CNT VNF modules 609. SDN CNT VNF modules 609 expose an SDN Application Programming Interface (API) to SDN modules 606-608 to control SDN data machines in the field. NFVI control modules 610 include hypervisors and virtual machines to create the virtualized networking environment. NFVI MANO modules 611 include orchestrators, VNF Managers (VNFMs) and Virtual Infrastructure Managers (VIMs) to control the operation of the NFVIs and VNFs.
The above description and associated figures teach the best mode of the invention. The following claims specify the scope of the invention. Note that some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Those skilled in the art will appreciate that the features described above can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific embodiments described above, but only by the following claims and their equivalents.
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 6876649, | Sep 27 1999 | CIENA LUXEMBOURG S A R L ; Ciena Corporation | High-capacity WDM-TDM packet switch |
| 9001682, | Jul 21 2011 | RIBBON COMMUNICATIONS OPERATING COMPANY, INC | Content and RAN aware network selection in multiple wireless access and small-cell overlay wireless access networks |
| 9326229, | Mar 31 2011 | Fujitsu Limited | Gateway device and gateway selection method |
| 20060190605, | |||
| 20110176530, | |||
| 20130051298, | |||
| 20130225123, | |||
| 20150063296, | |||
| 20160007331, | |||
| 20160262045, | |||
| 20160285935, | |||
| 20170251357, | |||
| 20180077668, | |||
| WO2017043940, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Jun 29 2016 | PARK, SUNYONG | SPRINT COMMUNICATIONS COMPANY L P | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047261 | /0046 | |
| Oct 22 2018 | Sprint Communications Company L.P. | (assignment on the face of the patent) | / | |||
| Apr 01 2020 | ISBV LLC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | ASSURANCE WIRELESS USA, L P | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | SPRINT SPECTRUM L P | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | SPRINT INTERNATIONAL INCORPORATED | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | SPRINT COMMUNICATIONS COMPANY L P | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | Clearwire Legacy LLC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | Clearwire IP Holdings LLC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | CLEARWIRE COMMUNICATIONS LLC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | BOOST WORLDWIDE, LLC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | PUSHSPRING, INC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | LAYER3 TV, INC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | T-MOBILE CENTRAL LLC | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Apr 01 2020 | T-Mobile USA, Inc | DEUTSCHE BANK TRUST COMPANY AMERICAS | SECURITY AGREEMENT | 053182 | /0001 | |
| Mar 03 2021 | SPRINT COMMUNICATIONS COMPANY L P | T-MOBILE INNOVATIONS LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 055604 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | LAYER3 TV, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | Sprint Spectrum LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | SPRINT INTERNATIONAL INCORPORATED | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | SPRINT COMMUNICATIONS COMPANY L P | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | SPRINTCOM LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | Clearwire IP Holdings LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | CLEARWIRE COMMUNICATIONS LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | BOOST WORLDWIDE, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | ASSURANCE WIRELESS USA, L P | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | T-Mobile USA, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | T-MOBILE CENTRAL LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | PUSHSPRING, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 | |
| Aug 22 2022 | DEUTSCHE BANK TRUST COMPANY AMERICAS | IBSV LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 062595 | /0001 |
| Date | Maintenance Fee Events |
| Oct 22 2018 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| May 30 2023 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Date | Maintenance Schedule |
| Dec 17 2022 | 4 years fee payment window open |
| Jun 17 2023 | 6 months grace period start (w surcharge) |
| Dec 17 2023 | patent expiry (for year 4) |
| Dec 17 2025 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Dec 17 2026 | 8 years fee payment window open |
| Jun 17 2027 | 6 months grace period start (w surcharge) |
| Dec 17 2027 | patent expiry (for year 8) |
| Dec 17 2029 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Dec 17 2030 | 12 years fee payment window open |
| Jun 17 2031 | 6 months grace period start (w surcharge) |
| Dec 17 2031 | patent expiry (for year 12) |
| Dec 17 2033 | 2 years to revive unintentionally abandoned end. (for year 12) |