SYSTEM AND METHOD FOR PROCESSING NETWORK TRAFFIC BASED ON FEDERATED SERVICES AND USER GROUPS - Patent application
By segregating network traffic using VRF instances and separate RF channels, the system addresses security and revenue loss issues in cellular networks by ensuring distinct processing for different user groups and services, enhancing security and optimizing bandwidth.
Patent Information
- Application Number
- JP2020097385
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-06-04
- Filing Date
- 2020-06-04
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2040-06-04
AI Technical Summary
Cellular network providers face security risks due to the inability to separate and manage network traffic effectively for different Tier 2 operators, leading to potential data breaches and loss of revenue from stranded bandwidth.
Implementing a system with multiple modem pools and network devices that utilize virtual routing forwarding (VRF) instances to segregate network traffic on a per-user group and per-service basis, ensuring separate routing and processing for different user groups and services, using separate RF channels and modems to enhance security and flexibility.
The solution provides enhanced data security and flexibility by ensuring that traffic for different user groups and services is processed separately, reducing the risk of data breaches and optimizing bandwidth utilization.
Smart Images

Figure 0007582796000001 
Figure 0007582796000002 
Figure 0007582796000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates generally to handling network traffic based on federated services and user groups. [Background technology]
[0002] A cellular network provider (also referred to as a Tier 1 Mobile Network Operator (MNO)) may use a cellular system to provide telephone, data, and other services to subscribers via wireless devices (e.g., cell phones, tablet computers, etc.). The cellular network provider has a certain frequency spectrum (e.g., a frequency range) from which the network bandwidth (measured in Hertz (Hz)) and capacity (measured in bits per second (bps)) used to provide cellular services to the subscribers are obtained. This bandwidth and capacity may be greater than that required to provide the services offered by the cellular network provider. To increase revenue, the cellular network provider may sell a portion of the bandwidth, capacity, and services to a Tier 2 operator (also known as a Mobile Virtual Network Operator (MVNO) or Virtual Network Operator (VNO)). In this model, the Tier 1 operator is referred to as a Value Added Reseller (VAR) that resells the bandwidth, capacity, and services. If such bandwidth, capacity, and services are not resold, they are "stranded" (i.e., not used to generate revenue for the VAR). The cellular system is then used to provide access to a given cellular or network service to subscribers of the tier 2 operators. Although the cellular system may process traffic for various tier 2 operators, in some systems traffic associated with a first tier 2 operator and a first service is not separated from traffic associated with a second tier 2 operator and a second service, which may create a security risk for these tier 2 operators (e.g., traffic associated with a particular tier 2 operator or a particular service being processed by and provided to devices associated with another tier 2 operator or another service). Summary of the Invention
[0003] In a particular implementation, a system for service and user group based communications includes a plurality of modems corresponding to a plurality of modem pools. The plurality of modems includes a first modem corresponding to a first modem pool and a second modem corresponding to a second modem pool. The first modem is configured to generate a first data packet based on a first radio frequency (RF) signal. The first data packet includes first data and a first virtual routing and forwarding (VRF) instance identifier. The second modem is configured to generate a second data packet based on a second RF signal. The second data packet includes second data and a second VRF instance identifier. The system also includes a network device in communication with the plurality of modems. The network device is configured to receive the first data packet and transmit the first packet over a network to the first device. The first packet includes the first data and a first header including a first indicator. The first indicator is associated with a first VRF instance corresponding to the first VRF instance identifier. The first VRF instance identifier is associated with a first service, a first user group, or both. The network device is further configured to receive a second data packet and transmit the second packet over the network to the second device, the second packet including the second data and a second header including a second indicator, the second indicator being associated with a second VRF instance corresponding to a second VRF instance identifier, the second VRF instance identifier being associated with a second service, a second user group, or both.
[0004] In another particular implementation, a satellite includes a payload including one or more antennas. The satellite includes a memory configured to store channel mapping data indicating a mapping of at least one radio frequency (RF) channel to another RF channel. The satellite further includes a processor configured to initiate transmission of a second RF signal from the one or more antennas to a first device (e.g., a subscriber device) based on the channel mapping data, a first service associated with the first device, and a first user group associated with the first device. The second RF signal is based on a first RF signal received at the one or more antennas from a radio frequency equipment (RFE). The first RF signal corresponds to a first RF channel and the second RF signal corresponds to a second RF channel different from the first RF channel.
[0005] In another particular implementation, a method includes receiving, at a network device, a first data packet from a first modem of a first modem pool, transmitting the first packet from the network device over a network to the first device, receiving, at the network device, a second data packet from a second modem of a second modem pool, and transmitting the second packet from the network device over a network to the second device. The first data packet includes first data and a first VRF instance identifier. The first packet includes the first data and a first header including a first indicator associated with the first VRF instance. The first VRF instance is associated with a first service and a first user group. The second data packet includes second data and a second VRF instance identifier. The second packet includes the second data and a second header including a second indicator associated with the second VRF instance. The second VRF instance identifier is associated with a second service and a second user group. [Brief description of the drawings]
[0006] [Figure 1]1 is a block diagram illustrating a first example of one implementation of a system for processing network traffic associated with different virtual routing and forwarding (VRF) instances corresponding to different user group and service pairs. [Diagram 2] FIG. 2 illustrates a second example of one implementation of a system for processing network traffic associated with different VRF instances corresponding to different pairs of user groups and services. [Diagram 3] FIG. 13 illustrates a third example of one implementation of a system for processing network traffic associated with different VRF instances corresponding to different pairs of user groups and services. [Figure 4] FIG. 4 is a ladder diagram illustrating a first example of network traffic communicated through the systems of FIGS. 1-3. [Diagram 5] FIG. 4 is a ladder diagram illustrating a second example of network traffic communicated through the systems of FIGS. 1-3. [Figure 6] 1 is a flow diagram of an example method for processing network traffic received from a device based on user groups and services associated with the device. [Figure 7] FIG. 1 is a flow diagram of an example method for processing network traffic to be sent to a device based on user groups and services associated with the device. [Figure 8] 1 is a flow diagram of an example method for processing network traffic associated with different virtual routing and forwarding (VRF) instances corresponding to different user group and service pairs. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0007] Particular implementations are described with reference to the drawings. In this description, common features are given common reference numbers throughout the drawings. As used herein, various terms are used only to describe particular implementations and are not intended to be limiting. For example, the singular forms "a / an" and "the" are intended to include the plural (unless the context clearly indicates otherwise). Furthermore, it will be understood that the words "comprise / comprises / comprising" may be used interchangeably with "include / includes / including." Additionally, it will be understood that the word "wherein" may be used interchangeably with "where." As used herein, "exemplary" may indicate examples, implementations, and / or aspects and should not be construed as limiting or indicating a preferred or preferred implementation. As used herein, ordinal numbers (e.g., "first," "second," "third," etc.) used to modify elements such as structures, components, acts, etc., do not in themselves indicate any priority or order of the element relative to other elements, but merely distinguish the element from other elements of the same name (apart from its use as an ordinal number). As used herein, the term "set" refers to a group of one or more elements, and the term "plurality" refers to a plurality of elements.
[0008] In this disclosure, terms such as "determining," "calculating," "shifting," "adjusting," and the like may be used to describe how one or more operations are performed. It should be noted that such terms should not be construed as limiting, and other techniques may be utilized to perform similar operations. Additionally, as referred to herein, "generating," "calculating," "using," "selecting," "accessing," and "determining" may be used interchangeably. For example, "generating," "calculating," or "determining" a parameter (or signal) may refer to actively generating, calculating, or determining a parameter (or signal), or may refer to using, selecting, or accessing a parameter (or signal) that has already been generated, for example, by another component or device. As used herein, "coupled" may include "communicatively coupled," "electrically coupled," or "physically coupled," and / or may further (or alternatively) include any combination thereof. Two devices (or components) may be coupled (communicatively coupled, electrically coupled, or physically coupled) directly or indirectly via one or more other devices, components, wires, buses, networks (e.g., wired networks, wireless networks, or combinations thereof), etc. Two devices (or components) that are electrically coupled may be included in the same device or in separate devices, and may be connected via electronics, one or more connectors, or inductive coupling, as illustrative and non-limiting examples. In some implementations, two devices (or components) that are communicatively coupled (e.g., in electrical communication) may send and receive electrical signals (digital or analog signals), directly or indirectly, for example, via one or more wires, buses, networks, etc.As used herein, a "directly coupled" may include two devices that are coupled (e.g., communicatively coupled, electrically coupled, or physically coupled) with no intervening components.
[0009] Implementations disclosed herein are directed to systems and methods for providing segregation of network traffic on a per-user group and per-service basis in a cellular system. In some implementations, the systems and methods described herein are described in connection with a federated network. In other implementations, the systems and methods described herein are applied to other types of networks. A cellular system includes multiple components, such as network devices (e.g., "core network" devices), base stations, beam forming networks, radio frequency (RF) equipment (RFE), switching circuitry, or other components. An operator of a cellular system (e.g., a Tier 1 operator) may sell access to the cellular system to separate Closed User Groups (CUGs) for providing various network services. As used herein, "CUG" refers to a Tier 2 operator (e.g., a service provider) that pays for access to equipment associated with the Tier 1 operator. For convenience, members of a CUG are referred to as "users." Tier 2 operators include, by way of non-limiting examples, Mobile Virtual Network Operators (MVNOs) and Virtual Network Operators (VNOs). In certain aspects, an MVNO includes multiple CUGs. An individual who subscribes to a service provided by a Tier 2 operator is referred to herein as a "subscriber." In certain aspects, multiple CUGs provide the same type of service. The described systems and methods improve the security of data processed by the cellular system by isolating network traffic associated with each user group (e.g., an MVNO, a CUG within an MVNO, or a CUG associated with a certain service) and each service. In addition, the adaptability of the cellular system is increased because data associated with different user groups and different services can be processed according to different rules or criteria, instead of a global set of rules or criteria being applied to all user groups and all services.
[0010] In certain aspects, the service may be a first generation (1G) cellular communication, a second generation (2G) cellular communication, a third generation (3G) cellular communication, a fourth generation (4G) cellular communication, a fifth generation (5G) cellular communication, high speed packet access (HSPA), high speed downlink packet access (HSDPA), high speed uplink packet access (HSUPA), short message service (SMS), multimedia message service (MMS), Internet of Things (IoT) communication, Worldwide Interoperability for Microwave The communications include at least one of WiMAX communications, Institute of Electrical and Electronics Engineers (IEEE) 802.11x communications, Wi-Fi communications, Digital Video Broadcasting-Satellite (DVB-S) communications, Digital Video Broadcasting-Satellite-Second Generation (DVB-S2) communications, DVB-S2 Extended (DVB-S2X) communications, Digital Video Broadcasting-Return Channel via Satellite (DVB-RCS) communications, DVB Two-Way Satellite System Second Generation (DVB-RCS2) communications, or proprietary government system communications.
[0011] To implement network traffic isolation per user group and per service, traffic associated with different user group and service pairs is encapsulated separately and routed and forwarded through the cellular system using different routing information. In a particular implementation, base stations and network devices (e.g., mobile management entities, packet gateways such as packet data network gateways (PGWs) and serving gateways (SGWs)) are configured to encapsulate traffic associated with different user group (e.g., different MVNOs) and service pairs using different identifiers. Illustratively, in a particular implementation, the network devices maintain different virtual routing and forwarding (VRF) instances for each user group and service pair. This includes maintaining different routing information base (RIB) data for each user group and service pair. Due to the different RIB data, traffic associated with a first user group and a first service may take a different path through an external network than traffic associated with a second user group and a second service.
[0012] In certain implementations, traffic associated with different pairs of user groups and services are processed by different devices (or different components) in the cellular system. Illustratively, a base station includes multiple modem pools (e.g., physical modem pools, virtual modem pools, or logical modem pools) including one or more modems, where the modems in each modem pool are configured to process data packets associated with a corresponding user group and a corresponding service. As a particular example, one or more modems in a first modem pool process data packets associated with a first user group and a first service (indicated by a VRF instance identifier in the data packets), and one or more modems in a second modem pool process data packets associated with a second user group and a second service. In certain aspects, one or more modems in the first modem pool are different from one or more modems in the second modem pool. In some examples, the first user group and the first service are different from the second user group and the second service, respectively. In some examples, the first user group is different from the second user group, but the first service is the same as the second service (e.g., are homogenous). In some examples, the first user group is the same as the second user group, but the first service is different from the second service.
[0013] In addition to isolating network traffic through the network and the cellular system for each user group and service pair, the cellular system may allow separate user group and service pairs to access the cellular system via separate portions of the RF spectrum (e.g., separate RF channels or separate portions of RF channels). In a particular implementation, switching circuitry onboard the satellite is configured to receive RF signals from RF circuitry coupled to the base station and perform "beam-to-beam" switching (e.g., RF signal switching). Thereby, an RF signal received from the RF circuitry corresponding to traffic associated with a first user group and a first service is used to generate a second RF signal corresponding to a first portion of the RF spectrum associated with the first user group and the first service. Similarly, a third RF signal corresponding to traffic associated with a second user group and a second service is used to generate a fourth RF signal corresponding to a second portion of the RF spectrum associated with the second user group and the second service. The second RF signal is provided to user devices associated with the first user group and subscribed to the first service. The fourth RF signal is provided to user devices associated with the second user group and subscribed to the second service. In a particular implementation, RF signals are deployed in an overlapping pattern at the same location such that multiple devices at the same location can access the cellular system over separate portions of the RF spectrum (e.g., separate RF channels or separate portions of RF channels). The RF signals are mapped to corresponding VRF instances (e.g., to corresponding user groups and services) and converted into data packets. The processing of these data packets is separated for each VRF instance as described herein.
[0014] The system described herein improves data security compared to other systems by isolating network traffic associated with different pairs of user groups (e.g., different service providers, government customers, or enterprise customers) and services. For example, data associated with different pairs of user groups and services is encapsulated and processed using different VRF instance identifiers, thereby distinguishing (e.g., isolating) data associated with a particular pair of user groups and services from data associated with other pairs of user groups and services. In addition, communications between the cellular system and subscriber devices are conducted using separate RF channels (or other frequency bands), further isolating communications associated with a particular pair of user groups and services from communications associated with other pairs of user groups and services. Such network traffic isolation improves data security in cellular systems associated with different user groups (e.g., different service providers) and different services. In addition, it increases the adaptability of the cellular system, since traffic associated with a particular pair of user groups and services can be processed using different rules or policies than data associated with other pairs of user groups and services.
[0015] Segregation of network traffic on a per-user group and per-service basis is described as an example implementation. In some implementations, segregation of network traffic is provided based on various criteria (e.g., quality of service, user group, service, user, or combinations thereof). In such implementations, different portions of the RF spectrum are allocated based on the criteria. For example, a first portion of the RF spectrum corresponds to a first quality of service, a first user group, a first service, a first user, or combinations thereof, and a second portion of the RF spectrum corresponds to a second quality of service, a second user group, a second service, a second user, or combinations thereof. Traffic meeting different criteria is processed by different devices (or different components). For example, one or more first modems are configured to process data packets associated with the first quality of service, the first user group, the first service, the first user, or combinations thereof, and one or more second modems are configured to process data packets associated with the second quality of service, the second user group, the second service, the second user, or combinations thereof.
[0016] 1 illustrates an example of a system 100 configured to process network traffic associated with different virtual routing and forwarding (VRF) instances corresponding to different pairs of user groups and services. System 100 includes satellite 102 including switching circuitry 104 and beam forming network 108, RFE 106, base station 118, and core network 130 including network device 142, subscriber data server 136, and Internet Protocol (IP) multimedia subsystem server 134. Although components 102, 104, 106, 108, 118, 134, 136, and 142 are illustrated as being included in system 100, in other implementations, one or more of components 102, 104, 106, 108, 118, 134, 136, and 142 are not included (corresponding functionality is performed by one or more of the remaining components). In other implementations, system 100 includes additional components not illustrated.
[0017] The satellite 102 is configured to communicate with one or more devices (e.g., one or more subscriber devices). The one or more devices may include a mobile device (such as, but not limited to, a mobile phone, a tablet computer, a laptop computer, a smart watch, a media playback device, a navigation system, a personal digital assistant (PDA), a satellite phone, a vehicle (or components thereof), or a combination thereof). In some implementations, the one or more devices may also include a stationary computerized device. The satellite 102 includes a processor 180, a memory 182, a switching circuit 104, a beam forming network 108, and a payload 184. The payload 184 includes one or more antennas configured to communicate with the one or more devices. In certain implementations, the system 100 includes or corresponds to a satellite-based cellular system. In other specific implementations, the system 100 includes or corresponds to a hybrid cellular system (e.g., a satellite-terrestrial hybrid cellular system). For example, satellite 102 may communicate with one or more devices via one or more components of a ground-based cellular system (e.g., antenna(s), satellite(s), tower(s), etc.) In an alternative implementation, system 100 includes or corresponds to a ground-based cellular system, as further described in connection with FIG.
[0018] The switching circuitry 104 is configured to divide a frequency spectrum (e.g., an RF spectrum) into multiple smaller frequency "slices" (e.g., sub-bands, channels, sub-channels, etc.). As an example, the switching circuitry 104 is configured to divide an incoming ultra-wideband signal into multiple channels or sub-channels for transmission to another device or component. Although RF signals are described herein, other frequency signals may be used in other implementations. In certain implementations, the switching circuitry 104 is configured to divide the RF signal into narrower bandwidths than other filtering devices. As a specific example, other filtering devices may divide the RF signal into sizes referred to as "transponders" or "transponder-size" having a range of approximately 30 to 70 megahertz (MHz). Meanwhile, the switching circuitry 104 is configured to divide the RF spectrum (or another frequency spectrum) into multiple bands or slices of approximately 31 kilohertz (kHz). Signals may be referred to as portions of a frequency band, or as frequency channels (e.g., RF channels), or may be divided into multiple time-based channels or sub-channels (e.g., for time division multiple access (TDMA) signals) or code-based channels or sub-channels (e.g., for code division multiple access (CDMA) signals).
[0019] The beamforming network 108 is configured to enable beamforming to one or more devices. In a particular implementation, the beamforming network 108 is configured to apply beamforming weights to RF signals (e.g., "beams") to modify the directionality and spatial selectivity of the RF signals to or from one or more devices. In a particular implementation, the beamforming weights are stored as beamforming data 110 in the memory 182, and each set of beamforming weights is associated with a corresponding user group and a corresponding service (e.g., beamforming weights are assigned on a per-user group and per-service basis), as described below.
[0020] In the implementation shown in FIG. 1, beam forming network (BFN) 108 includes a first BFN 112, a second BFN 114, and an Nth BFN 116. Although three BFNs are shown in BFN 108, in other implementations, N may be any integer greater than two. In certain implementations, the first BFN 112 is assigned to perform operations on RF signals associated with a first service, a first group of users, or both. For example, the first BFN 112 is associated with a first beamforming weight associated with the first service, the first group of users, or both. In certain aspects, the second BFN 114 is assigned to perform operations on RF signals associated with a second service, a second group of users, or both. In a particular aspect, each of the BFNs 112, 114, and 116 is assigned to perform operations on the RF signals for a unique pair of service and user group.
[0021] As used herein, a "user" includes a Tier 2 operator or other service provider that provides services by using network resources of a Tier 1 operator (e.g., the Tier 1 operator that owns and operates the system 100). A CUG includes a Mobile Virtual Network Operator (MVNO), a Virtual Network Operator (VNO), and other service providers that use the system 100 to provide services to subscribers. In certain aspects, a "user group" includes multiple users, multiple MVNOs, a CUG within an MVNO, a CUG associated with a particular type of service, or a combination thereof. A subscriber includes people who subscribe to a service provided by a service provider (e.g., a CUG) and who access the system 100 using a device (e.g., a mobile phone or other equipment). In a particular implementation shown in FIG. 1, the switching circuitry 104 and the beam forming network 108 are integrated within the satellite 102. In another particular implementation, the switching circuitry 104 and the beam forming network 108 are coupled between the RFE 106 and the base station 118, as described in connection with FIG. 2. In certain aspects, the base stations 118, the core network 130, or both, include terrestrial components.
[0022] In certain implementations, the switching circuitry 104 is configured to generate multiple sets of RF signals associated with corresponding portions of the RF spectrum. For example, each set of RF signals includes one or more RF signals corresponding to a particular portion of the RF spectrum (e.g., a particular RF channel or particular RF channels). The multiple sets of RF signals include at least one RF signal associated with a particular portion of the RF spectrum associated with a unique pair including a user group and a service. By way of example, the multiple RF signals include a first RF signal corresponding to a particular portion of the RF spectrum (e.g., a particular RF channel) designated for communications associated with a first user group (e.g., a first MVNO) and a first service. By way of further example, the multiple RF signals include a second RF signal corresponding to a particular portion of the RF spectrum (e.g., a second particular RF channel) designated for communications associated with a second user group (e.g., a second MVNO) and a second service.
[0023] In a particular implementation, the beam forming network 108 is configured to adjust the phase, amplitude, or both of the RF signal based on beam forming data indicating a first set of beam forming weights associated with a first user group and a first service and a second set of beam forming weights associated with a second user group and a second service. For example, the first BFN 112 is configured to adjust the phase, amplitude, or both of the RF signal based on the first set of beam forming weights and the second BFN 114 is configured to adjust the phase, amplitude, or both of the RF signal based on the second set of beam forming weights. The RF signal is transmitted (e.g., deployed) to one or more locations to enable wireless communication with devices associated with the two user groups and two services over separate portions of the RF spectrum, as described below. Although the switching circuitry 104 and the beam forming network 108 are illustrated as two components, in a particular implementation, they are integrated into or correspond to a single component. Alternatively, the operations of the switching circuitry 104 and the beam forming network 108 are performed by the processor 180.
[0024] The RFE 106 is configured to process RF signals received from one or more devices or to be sent (e.g., transmitted) to one or more devices via the satellite 102. As an example, the RFE 106 includes one or more filters, one or more amplifiers, one or more mixers, one or more other components, or a combination thereof, that process the RF signals received from one or more user equipment (UE) devices or to be sent to one or more UE devices via the satellite 102.
[0025] Base station 118 includes a processor 120 and a memory 122 and is configured to receive RF signals from one or more devices (e.g., via components 102-108, 112-116) and process the RF signals. In particular implementations, processor 120 is configured to execute instructions stored in memory 122 to perform operations described herein. In alternative implementations, base station 118 includes hardware (e.g., an application specific integrated circuit (ASIC) or field programmable gate array (FPGA)) or a controller that performs the operations described herein.
[0026] Illustratively, the base station 118 is configured to convert RF signals to the digital domain to generate data packets that are routed through the core network 130. To generate the data packets, the base station 118 includes multiple modem pools that include multiple modems. In certain implementations, each modem pool is assigned to a particular user group (e.g., a particular MVNO) and a particular service, and one or more modems of a particular modem pool are assigned to process data packets associated with the corresponding user group and corresponding service. Although described as individual modems, in some implementations the base station 118 includes a single modem that is virtualized to provide virtual modem pools and virtual modems that perform the modem operations described herein. In other implementations, the modems can be physical modems, logical modems, virtual modems, or a combination thereof.
[0027] In the implementation shown in FIG. 1, the base station 118 includes a first modem 124, a second modem 126, and an Nth modem 128. For example, each of the first modem 124, the second modem 126, and the Nth modem 128 is instantiated in the base station 118. Although three modems are shown, in other implementations, N can be any integer greater than two. Each modem is part of a modem pool. As an example, the first modem pool 125 includes the first modem 124, the second modem pool 127 includes the second modem 126, and the Nth modem pool 129 includes the Nth modem 128. Although one modem per modem pool is shown, this example is not limiting. A modem pool may include any number of modems. In the implementation shown in FIG. 1, each of the first modem pool 125, the second modem pool 127, and the Nth modem pool 129 is instantiated in the base station 118. In a particular implementation, the modems in the first modem pool 125 are assigned to perform operations on traffic associated with a first service, and the modems in the second modem pool 127 are assigned to perform operations on traffic associated with a second service. In a particular aspect, a first modem in the first modem pool 125 and a second modem in the first modem pool 125 are assigned to perform operations on traffic associated with a first user group and a second user group, respectively, that provide the first service.
[0028] In a particular implementation, the modem is configured to generate data packets based on RF signals from multiple devices associated with separate pairs of user groups and services. The data packets include an identifier that associates each data packet with a particular user group and a particular service. For example, the data packets include an identifier of a virtual routing and forwarding (VRF) instance. The VRF instance corresponds to a user group (e.g., a tier 2 operator or other service provider) and a service, and is used to implement routing in the network device 142, as described below. In a particular example, the VRF instance is instantiated in the network device 142. In a particular implementation, the RF signals are assigned to the modem for processing based on configuration data 123 stored in memory 122. In a particular implementation, the configuration data 123 indicates an association between a VRF identifier and a pair of user group identifiers and service identifiers. Illustratively, the configuration data 123 indicates that a particular pair (including a particular user group identifier and a particular service identifier) is associated with a VRF instance (corresponding to a particular user group identified by the user group identifier and corresponding to a particular service identified by the service identifier). The data packet, including the VRF instance identifier, is sent from the base station 118 to the network device 142 .
[0029] Network device 142 includes a processor 144 and memory 146 and is configured to route traffic between one or more devices and a network 156 (e.g., the Internet, an external network, such as a network maintained by another Tier 1 provider). In certain implementations, processor 144 is configured to execute instructions stored in memory 146 to perform operations described herein. In alternative implementations, network device 142 includes hardware (e.g., an ASIC or FPGA) or a controller that performs operations described herein. Network device 142 may include or correspond to a signaling gateway, a packet gateway, a mobility management entity (MME), or a combination thereof. In certain implementations, network device 142 is a single device that performs the functions of a signaling gateway, a packet gateway, and an MME. Alternatively, more than one communicatively coupled device may perform the operations of network device 142.
[0030] In a particular implementation, the network device 142 is configured to receive data packets from the modem of the base station 118 and generate packets to be sent through the core network 130 (e.g., the subscriber data server 136 and the IP multimedia subsystem server 134) to other devices of the network 156, as described below. The subscriber data server 136 (e.g., a Customer Billing Subsystem (CCBS)) is configured to monitor network usage for billing and provisioning. In a particular implementation, the subscriber data server 136 is configured to track network usage and perform billing on a per-user group and per-service basis. As a non-limiting example, information regarding subscriber usage is maintained and stored for each user group and each service. The IP multimedia subsystem is configured to perform operations such as initiating and maintaining a voice session, initiating and maintaining a data session, initiating telephone ringtones, and other operations that enable telephone, data, and other services on one or more devices. In some implementations, core network 130 also includes one or more security or cybersecurity systems configured to provide secure logical separation between system 100 and external networks (e.g., network 156).
[0031] During operation, the system 100 enables multiple user groups (e.g., tier 2 operators or service providers) to provide multiple services via the system 100, such as a first service 160 (e.g., an IP core network service), a second service 164 (e.g., a circuit-based core network service), and an N service 168 (e.g., a proprietary core network service). Although three services are illustrated, in other implementations, N may be any integer greater than two. To support multiple user groups (e.g., CUGs) and multiple services, beammaps and beamforming weights may be created and stored as beamforming data 110. In a particular implementation, the beammap specifies a frequency reuse pattern of beams directed to multiple cells (e.g., earth cells) such that a particular frequency band (e.g., channel, subchannel, etc.) may be reused in different non-adjacent cells. In another particular implementation, the beamforming data 110 indicates a carrier map that specifies an initial capacity and carrier configuration for each beam generated by the switching circuitry 104. In another particular implementation, each user group and service pair is associated with a corresponding cell size, beam weight, pattern, capacity, and carrier allocation, and the beamforming data 110 indicates multiple sets of beamforming weights (and other information, such as cell sizes, patterns, capacity, and carrier allocation) associated with multiple user group and service pairs. In some implementations, the beamforming data 110 (or portions thereof) is adjusted over time, for example, based on changing subscriber distribution, changing traffic load patterns, user group policies, or service policies.
[0032] In a particular implementation, the satellite 102 transmits multiple RF signals (e.g., beams) in one or more patterns in one or more regions. Each pattern of RF signals corresponds to a pair of a user group (e.g., a first MVNO) and a service and enables wireless communication between the system 100 and devices associated with the pair of the user group and the service. Illustratively, the switching circuitry 104 receives data (e.g., from the network device 142 after performing one or more association operations) indicating that a unique pair of a user group and a service (e.g., a first service 160) is associated with a particular portion of the frequency spectrum, and generates at least one beam associated with the particular portion. In a particular implementation, the beam forming network 108 adjusts the multiple RF signals based on the beam forming data 110, with each RF signal being transmitted over a portion of the frequency spectrum associated with a corresponding pair (e.g., including one user group and one service). For example, the first BFN 112 adjusts a first RF signal based on a first set of beamforming weights corresponding to a first user group and a first service 160, and the second BFN 114 adjusts a second RF signal based on a second set of beamforming weights corresponding to a second user group and a second service 164. The first RF signal is transmitted over a first portion of the frequency spectrum corresponding to the first user group and the first service 160. The second RF signal is transmitted over a second portion of the frequency spectrum corresponding to the second user group and the second service 164. In a particular implementation, the satellite 102 stores data indicative of an association between each unique pair (e.g., each user group and service pair) and a corresponding portion of the frequency spectrum (e.g., channel mapping data 186 is stored in memory 182).
[0033] Satellite 102 may transmit (e.g., deploy) multiple RF signals in one or more patterns in one or more regions. In a particular implementation, satellite 102 deploys one or more RF signals in a first pattern 162, a second pattern 166, and an Nth pattern 170. Each of patterns 162, 166, and 170 is associated with a different pairing of a user group and a service. In a particular implementation, first pattern 162 is associated with a first service 160 and a first user group, second pattern 166 is associated with a second service 164 and a second user group, and Nth pattern 170 is associated with an Nth service 168 and an Nth user group. One or more of patterns 162, 166, and 170 may overlap in the same region. Illustratively, patterns 162, 166, and 170 overlap in a particular region to provide wireless communication services to subscribers in the particular region over separate RF channels (or other frequency bands) associated with separate pairs of user groups (e.g., CUGs) and services. Alternatively, one or more of patterns 162, 166, and 170 may be deployed in separate regions. Illustratively, subscribers in a first region access system 100 over a first RF channel, and a second subscriber in a second region accesses system 100 over a second RF channel.
[0034] A specific example is provided to illustrate the operation of the system 100. In this example, the first pattern 162, the second pattern 166, and the Nth pattern 170 overlap each other within the first region. A first device 172 (e.g., a first subscriber device) entering the first region synchronizes with an available operator frequency and receives data (e.g., master information block data and system information block data) indicative of available user groups (e.g., CUGs) that are served via the system 100. If the first device 172 is associated with the first service 160 and the first user group (e.g., if the subscriber associated with the first device 172 has subscribed to the first service 160 provided by the first user group), the first device 172 performs one or more association operations and performs supported wireless communications over the portions of the frequency spectrum associated with the first service 160 and the first user group. At the same location, a second device 174 (e.g., a second subscriber device) associated with a second service 164 and a second user group performs one or more association operations and performs supported wireless communications over the portion of the frequency spectrum associated with the second service 164 and the second user group.
[0035] In this manner, the portion of the frequency spectrum associated with the first service 160 and the first user group is accessible by devices (e.g., subscriber devices) located at the first location that are associated with (subscribe to) the first service 160 provided by the first user group. This portion of the frequency spectrum is inaccessible by devices (e.g., subscriber devices) located at the first location that are not associated with the first service 160 and the first user group. However, devices may be associated with other user groups, other services, or both, and may access different portions of the frequency spectrum at the same location. Thus, different devices associated with different pairs of user groups and services may access the system 100 using different frequencies at the same location.
[0036] In another particular implementation, the particular pattern of RF signals includes a first set of RF signals corresponding to RF channel(s) associated with a first service 160 and a first user group, a second set of RF signals corresponding to RF channel(s) associated with a second service 164 and a second user group, and a third set of RF signals corresponding to RF channel(s) associated with an Nth service 168 and an Nth user group. This particular pattern is deployed at multiple different locations. As a particular example, this particular pattern is deployed in Chicago, Washington DC, and New York. Subscribers are allowed to access communication services associated with each of the user group-channel pairs at each location using the same corresponding RF channel as part of a frequency reuse initiative. By way of example, subscribers in each of the three cities are allowed to access the first service 160 provided by the first user group via a first RF channel, the second service 164 provided by the second user group via a second RF channel, and the Nth service 168 provided by the Nth user group via a third RF channel. Alternatively, different patterns may be deployed at different locations. As a specific example, a first pattern is deployed in Chicago including a first service 160 and an RF channel associated with a first user group, and a second service 164 and a second RF channel associated with a second user group, and a second pattern is deployed in New York including a third RF channel associated with the first service 160 and the first user group, and a fourth RF channel associated with an N service 168 and the N user group. Subscribers associated with the first user group access the first service 160 via the first RF channel in Chicago and via the third RF channel in New York. Subscribers associated with the second user group access the second service 164 via the second RF channel in Chicago (but cannot access the second service 164 in New York).Subscribers associated with the Nth user group access the Nth service 168 over the fourth RF channel in New York (and cannot access the Nth service 168 in Chicago).
[0037] Performing one or more association operations may include performing a radio link attachment operation, a network registration operation, an IP Multimedia Subsystem (IMS) operation, other association operations, or a combination thereof. In a particular implementation, the one or more association operations are performed by the base station 118, the network device 142, other devices, or a combination thereof. In this implementation, the base station 118 and the network device 142 store data in memories 122, 146, respectively. This data associates the device with a user group (e.g., CUG) and service pair, and is updated during the performance of the one or more association operations. Further details regarding the one or more association operations are described in connection with FIG. 2.
[0038] Once a device is associated with a selected user group and service pair, it may send an RF signal to (or receive an RF signal from) system 100 over a corresponding portion of the frequency spectrum. In a particular implementation, a first device 172 sends a first RF signal over a first portion of the frequency spectrum (e.g., a first RF channel) corresponding to a first service 160 and a first user group, and a second device 174 sends a second RF signal over a second portion of the frequency spectrum (e.g., a second RF channel) corresponding to a second service 164 and a second user group. The RF signals are received by satellite 102 and provided to RFE 106 for processing. In a particular implementation, RFE 106 is configured to perform one or more processing operations (e.g., amplification, noise reduction, etc.) on the first RF signal and the second RF signal.
[0039] The base station 118 receives the first and second RF signals and designates a particular modem to process these RF signals (and resulting data packets) or incoming data packets, as described below. In a particular implementation, the first modem 124 is configured to generate a first data packet based on the first RF signal, and the second modem 126 is configured to generate a second data packet based on the second RF signal. The designation of a particular modem of a particular modem pool to process an RF signal (or data packet) is based on a user group and service pair associated with the RF signal (or data packet) and the configuration data 123. As a particular example, the configuration data 123 indicates (e.g., based on an indicator of a device ID associated with the first device 172) that the first device 172 is associated with a first pair (e.g., including a first service 160 and a first user group) corresponding to a first VRF instance identifier, and that the second device 174 is associated with a second pair (e.g., including a second service 164 and a second user group) corresponding to a second VRF instance identifier. The base station 118 (e.g., processor 120) is configured to designate the first modem 124 to process the first RF signal (e.g., RF signals or data packets associated with the first service 160 and the first user group) and the second modem 126 to process the second RF signal (e.g., RF signals or data packets associated with the second service 164 and the second user group) based on the configuration data 123 and the device ID indicator. In particular implementations, the indicator includes a phone number associated with the device, a subscription identifier (e.g., a mobile subscriber integrated services digital network number (MSISDN)), or any other type of device identity indicator.
[0040] In a particular implementation, each modem of the plurality of modems of the base station 118 is configured to process traffic (e.g., RF signals, data packets, etc.) associated with a corresponding VRF instance identifier. Illustratively, the first modem 124 and other modems of the first modem pool 125 are configured to process RF signals and data packets associated with a first VRF instance identifier corresponding to a first VRF instance associated with a first service 160 and a first user group. In a particular implementation, the first modem 124 is further configured to not process RF signals and data packets associated with other VRF instance identifiers (e.g., a second VRF instance identifier corresponding to a VRF instance associated with a second service 164 and a second user group). Similarly, the second modem 126 and other modems of the second modem pool 127 are configured to process data packets associated with the second VRF instance identifier and not process RF signals and data packets associated with the first VRF instance identifier.
[0041] Processing the RF signals in the modems 124-128 includes generating a data packet including the data and corresponding to the VRF instance identifier. By way of example, the base station 118, based on a determination that the first device 172 is associated with the first service 160 and the first user group, designates the first modem 124 to generate a first data packet based on the first RF signal, and the base station 118, based on a determination that the second device 174 is associated with the second service 164 and the second user group, designates the second modem 126 to generate a second data packet based on the second RF signal, the first data packet including the first data and the first VRF instance identifier, and the second data packet including the second data and the second VRF instance identifier.
[0042] In a particular implementation, the modems 124-128 are configured to encrypt data packets on a per VRF (or per user group and service) basis. Illustratively, the first modem 124 is further configured to encrypt the first data packets based on a first encryption associated with the first VRF instance, and the second modem 126 is configured to encrypt the second data packets based on a second encryption associated with the second VRF instance. In a particular implementation, the first and second encryptions are the same type of encryption, but different keys or other values are used to perform the corresponding encryptions. In an alternative implementation, the first and second encryptions are performed using different types of encryption. Encrypting data associated with one user group and service pair differently from encrypting data associated with another user group and service pair can improve security and differentiation of data corresponding to different user group and service pairs. Illustratively, encrypted data inadvertently provided to a device associated with a different user group and a different service will not be decrypted using the same encryption as other data received by the device.
[0043] The first and second data packets are sent to the network device 142. In a particular implementation, the data packets (including the first and second data packets) are sent over an Institute of Electrical and Electronics Engineers (IEEE) 802.11Q compliant connector or trunk. In a particular implementation, the connector includes a 10 gigabit (gB) fiber tube. In a particular implementation, the base station 118 manages modulation and coding (MOCOD), time slot allocation, and queues of data packets (e.g., Evolved Packet System (EPS) bearers) via the modems 124-128 based on one or more network quality criteria. Further details regarding the data packets are described in conjunction with FIG. 2.
[0044] Network device 142 receives data packets and generates packets to be transmitted over core network 130 and network 156 to one or more other devices. For example, network device 142 is configured to receive a first data packet and transmit the first packet over network 156 to the first device. Network device 142 is further configured to receive a second data packet and transmit the second packet over network 156 to the second device. In a particular implementation, the first device and the second device are the same device. In an alternative implementation, the first device and the second device are separate devices. The first packet includes the first data and a first header including a first indicator associated with the first VRF instance, and the second packet includes the second data and a second header including a second indicator associated with the second VRF instance.
[0045] In a particular implementation, multiple VRF instances are maintained in the network device 142. Maintaining multiple VRF instances includes maintaining multiple routing information bases (RIBs) (e.g., routing forwarding data) in the network device 142 to be used to route packets. As a particular example, the network device 142 stores first VRF instance RIB data 150, second VRF instance RIB data 152, and Nth VRF instance RIB data 154 in the memory 146. Although three instance RIB data are shown in FIG. 1, in other implementations, N is any other integer greater than two. The VRF instance RIB data 150-154 may include or indicate routing information, forwarding information, or a combination thereof.
[0046] In a particular implementation, each of the VRF instance RIB data 150-154 is associated with a user group and service pair. As an example, the first VRF instance RIB data 150 is associated with a first service 160 and a first user group, the second VRF instance RIB data 152 is associated with a second service 164 and a second user group, and the Nth VRF instance RIB data 154 is associated with an Nth service 168 and an Nth user group. The VRF instance RIB data 150-154 allow different routing paths to be established for traffic associated with different user group and service pairs. For example, a routing path from a first device 172 to a first device in the network 156 may travel through the system 100, the core network 130, and the network 156 through different devices or portions of devices (e.g., different modems in the base station 118) than a routing path from a second device 174 to a second device in the network 156. Alternatively, the routing path from the first device 172 to the first device in the network may be the same as the routing path from the second device 174 to the second device in the network.
[0047] By maintaining separate RIBs for separate VRF instances and designating separate resources (e.g., modems) of the base station 118 for the separate VRF instances, logical separation of traffic is provided on a per-user group and per-service basis. To illustrate, traffic to and from the first device 172 (e.g., a subscriber device associated with the first service 160 and the first user group) travels through the system 100 on different time slots or with different modulation coding than traffic to and from the second device 174 (e.g., a subscriber device associated with the second service 164 and the second user group). In addition, due to differences between the first VRF instance RIB data 150 and the second VRF instance RIB data 152, the route that the traffic to and from the first device 172 takes through the core network 130 and the network 156 may be different from the route that the traffic to and from the second device 174 takes. By logically isolating traffic on a per-user group and per-service basis, security of user traffic is increased compared to systems that do not maintain separate VRF instances for separate user group and service pairs.
[0048] In a particular implementation, the network device 142 stores the composite RIB data 148 in the memory 146 for use in routing packets through the core network 130 and the network 156. The composite RIB data 148 is based on the VRF instance RIB data 150-154 and on any additional routing information generated by the network device 142 (e.g., routing associated with packets that do not correspond to one of the VRF instances). When a data packet is received at the network device 142, the corresponding VRF instance RIB data is updated. Illustratively, the network device 142 updates the first VRF instance RIB data 150 based on a first data packet and updates the second VRF instance RIB data 152 based on a second data packet.
[0049] In a particular implementation, the network device 142 generates a packet (including a header including an indicator of the corresponding VRF instance) based on the received data packet and the composite RIB data 148. As an example, the network device 142 generates a first packet including the first data and a first header including a first indicator associated with the first VRF instance, and generates a second packet including the second data and a second header including a second indicator associated with the second VRF instance. The first indicator and the second indicator include or correspond to an identifier (such as a source IP address or a source port address), as a non-limiting example. In a particular implementation, the indicator encapsulates the first data associated with the first VRF instance using a different header than the second data associated with the second VRF instance corresponding to a label or "5-tuples" (e.g., a tuple including a source address, a source port, a destination address, a destination port, and a protocol associated with the packet), thereby logically separating the first data from the second data during processing by the devices of the core network 130 and the network 156.
[0050] After being transmitted by the network device 142, the packet travels through the core network 130 and the network 156 on its way to the final destination device(s). In some implementations, at least some components of the core network 130 process the packet on a per-VRF basis. In a particular implementation, the subscriber data server 136 generates (or updates) the first subscriber data 138 based on the first packet and generates (or updates) the second subscriber data 140 based on the second packet. The first subscriber data 138 indicates provisioning information, billing information, usage information, or a combination thereof associated with a subscriber of the first service 160 provided by the first user group, and the second subscriber data 140 indicates provisioning information, billing information, usage information, or a combination thereof associated with a subscriber of the second service 164 provided by the second user group. In a particular implementation, other components of the core network 130 process the traffic on a per-VRF basis. As an example, the IP multimedia subsystem server 134 performs one or more actions on the first packet based on a policy or rule corresponding to the first service 160 and the first user group, and performs one or more actions on the second packet based on a policy or rule corresponding to the second service 164 and the second user group. In another particular implementation, one or more security or cybersecurity devices or systems (also referred to as a "demilitarized zone (DMZ)") process the traffic based on the rules and policies associated with the corresponding VRF instance. The VRF instance-based rules and policies allow traffic associated with a particular user group and service pair to be handled differently by devices in the core network 130 than traffic associated with other user group and service pairs.
[0051] Packets sent from devices in the network 156 to subscriber devices are processed in a similar manner. The packets proceed through the core network 130 and the rest of the system 100 on a per VRF instance basis or on a per user group and per service basis until they reach the destination subscriber device. As an example, the network device 142 is configured to receive a third packet from the first device via the network 156 and a fourth packet from the second device via the network 156. The third packet includes third data and a third header including an indicator associated with the first VRF instance, and the fourth packet includes fourth data and a fourth indicator associated with the second VRF instance. In a particular implementation, the third and fourth packets are routed to the subscriber data server 136 before arriving at the network device 142, and the subscriber data server 136 updates the corresponding subscriber data based on the third and fourth packets as described above.
[0052] In a particular implementation, the network device 142 updates the composite RIB data 148 based on the third and fourth packets, if any new routing information is associated with the third and fourth packets. For example, the network device 142 updates the first VRF instance RIB data 150 based on the third indicator being associated with the first VRF instance and updates the second VRF instance RIB data 152 based on the fourth indicator being associated with the second VRF instance. The network device 142 may further generate a data packet based on the received packets and transmit the data packet to a particular modem of the base station 118. As an example, the network device 142 generates a third data packet including the third data and the first VRF instance identifier and generates a fourth data packet including the fourth data and the second VRF instance identifier.
[0053] After generating the third and fourth packets, the network device 142 sends the third data packet to the first modem 124 (e.g., based on the third indicator being associated with the first VRF instance) and the fourth data packet to the second modem 126 (e.g., based on the fourth indicator being associated with the second VRF instance). The base station 118 converts the third and fourth data packets into third and fourth RF signals, respectively, that are transmitted to corresponding subscriber devices. In a particular implementation, the RF signals are processed by the components 102-108, 112-116 before being transmitted to the devices. Illustratively, the RFE 106 is configured to process the third and fourth RF signals, for example, by performing filtering, amplification, etc.
[0054] The base station 118 indicates to the RFE 106 and the satellite 102 that the different RF signals are associated with different VRF instances and therefore different pairs of user groups and services. In a particular implementation, the base station 118 associates RF signals corresponding to different VRF instances with different logical interfaces. For example, the base station 118 associates a first RF signal corresponding to a first VRF instance (and a first user group and a first service) with a first logical interface between the base station 118 and the RFE 106 (or between the base station 118 and the satellite 102), and also associates a second RF signal corresponding to a second VRF instance (and a second user group and a second service). In an alternative implementation, the base station 118 routes RF signals corresponding to different VRF instances to different ports (e.g., physical ports, logical ports, virtualized ports, etc.) of the RFE 106. As a particular example, the first modem 124 sends a first RF signal associated with a first VRF instance (and a first user group and a first service) to a first port, and the second modem 126 sends a second RF signal associated with a second VRF instance (and a second user group and a second service) to a second port.
[0055] In a particular implementation, RF signals associated with different logical interfaces (or routed to different ports) are transmitted over different portions of the RF spectrum (e.g., different RF channels) to the satellite 102. As a particular example, RF signals associated with a first logical interface (and thus associated with a first VRF, a first service 160, and a first user group) are transmitted over a first RF channel, and RF signals associated with a second logical interface (and thus associated with a second VRF, a second service 164, and a second user group) are transmitted over a different RF channel. In this manner, the satellite 102 receives an indication of an association between an RF signal and a VRF instance (corresponding to a particular service provided by a particular Tier 2 operator or service provider).
[0056] In a particular implementation, the satellite 102 is configured to receive RF signals from the RFE 106 and perform beam-to-beam switching to generate RF signals to be transmitted to one or more devices based on the channel mapping data 186. As a particular example, the processor 180 (or the switching circuitry 104) is configured to initiate transmission of a second RF signal from one or more antennas of the payload 184 to the first device 172 based on the channel mapping data 186 and based on the first user group and the first service 160 associated with the first device 172. The second RF signal is based on a first RF signal from the RFE 106 (and associated with the first VRF instance) received at the one or more antennas of the payload 184. The first RF signal and the second RF signal may correspond to different RF channels. For example, the first RF signal corresponds to a first RF channel and the second RF signal corresponds to a second RF channel that is different from the first RF channel.
[0057] In a particular implementation, the channel mapping data 186 indicates a mapping of RF channels (or other portions of the frequency spectrum) for communication with one or more devices or RFEs 106 to user group (e.g., CUG) and service pairs. As a particular example, the channel mapping data 186 indicates that a first service 160 and a first user group are mapped to at least a first RF channel for communication between the satellite 102 and the RFE 106, and to at least a second RF channel for communication between the satellite 102 and a first device 172 that subscribes to the first service 160 provided by the first user group. The channel mapping data 186 may be generated (or updated) by an operator of the satellite control system as a service provider (e.g., MVNO) purchases capacity and access to the system 100. For example, when a first user group purchases capacity and access to the system 100 to provide a first service 160, the satellite control system transmits data to the satellite 102 indicating that the first user group and first service 160 are associated with a first RF channel for communication between the satellite 102 and the RFE 106, and a second RF channel for communication between the subscriber device (associated with the first user group and first service 160) and the satellite 102. In some implementations, the channel mapping data 186 indicates groups of RF channels associated with each user group-service pairing, with at least some channels in each group of RF channels associated with separate locations. As additional user groups (e.g., CUGs) purchase capacity and access to the system 100 to provide services, data indicating the mapping of additional user group-service pairs to RF channels may be sent to the satellite 102 to update the channel mapping data 186.
[0058] In a particular implementation, the processor 180 is configured to initiate transmission of a fourth RF signal from one or more antennas of the payload 184 to the second device 174 based on the channel mapping data 186 and based on the second service 164 and the second user group associated with the second device 174. In this example, the fourth RF signal is based on a third RF signal from the RFE 106 received at the one or more antennas of the payload 184. The third RF signal and the fourth RF signal correspond to different RF channels, where the third RF channel and the fourth RF channel correspond to an RF channel different from the first RF channel and the second RF channel, respectively. As a particular example, the third RF signal corresponds to a third RF channel different from the first RF channel, and the fourth RF signal corresponds to a fourth RF channel different from the third RF channel and the second RF channel. In this manner, different pairs of user groups and services are associated with different RF channel mappings, and traffic associated with different pairs of user groups and services are communicated by transmission of RF signals over different RF channels. As a particular example, the RF signal transmitted to the first device 172 corresponds to a second RF channel (e.g., an RF channel associated with the first service 160 and the first user group) and the RF signal transmitted to the second device 174 corresponds to a fourth RF channel (e.g., an RF channel associated with the second service 164 and the second user group). In another particular implementation, one or more antennas of the payload 184 are configured to overlap transmission of the second and fourth RF signals at the same location.
[0059] Additional RF signals associated with the same pair of user group and service may be transmitted and received over the same RF channel. As a particular example, processor 180 is configured to initiate transmission of a sixth RF signal from one or more antennas of payload 184 to first device 172 based on the channel mapping data and based on first service 160 and first user group. In this example, the sixth RF signal is based on a fifth RF signal from RFE 106 received at one or more antennas of payload 184. Because the fifth RF signal and the sixth RF signal are associated with first service 160 and first user group, the fifth RF signal corresponds to the first RF channel and the sixth RF signal corresponds to the second RF channel.
[0060] In a particular implementation, the satellite 102 (e.g., the processor 180, the switching circuitry 104, or both) sends an RF signal to the RFE 106 based on the RF signals received from one or more subscriber devices and the channel mapping data 186. As a particular example, one or more antennas of the payload 184 receive an RF signal from the first device 172 over the second RF channel, and the processor 180 initiates transmission of the RF signal over the first RF channel to the RFE 106. The RFE 106 receives the RF signal over the first RF channel and processes the RF signal before providing it to the base station 118. In a particular implementation, the base station 118 assigns the RF signal to a modem (e.g., the first modem 124) in the first modem pool 125 for processing based on the RF signal being received over the first RF channel (e.g., an RF channel associated with the first service 160 and the first user group). Traffic received at the satellite 102 from subscriber devices associated with other user group and service pairs is similarly processed and provided to the base station 118 via the RFE 106. In this manner, traffic sent to (or received from) subscriber devices associated with different user group and service pairs is separated by communicating over separate RF channels (or other portions of the frequency spectrum). Conducting communications associated with different user group and service pairs over separate RF channels (or other portions of the frequency spectrum) may improve security and prevent data associated with a particular user group and service pair from being processed together with data associated with a different user group and service pair.
[0061] In a particular implementation, the beamforming network 108 adjusts the RF signal based on beamforming information associated with separate pairs of user groups and services. As an example, the beamforming network 108 is configured to adjust the second RF signal (e.g., an RF signal transmitted to the first device 172) based on the beamforming data 110 stored in the memory 182 and based on the first RF signal (e.g., based on the RF channel through which the first RF signal is received). In a particular implementation, the beamforming data 110 indicates a set of beamforming weights corresponding to pairs of user groups that have purchased capacity and access to the system 100 to provide the service. As a particular example, the beamforming data 110 indicates a first set of beamforming weights associated with the first service 160 and the first user group, and a second set of beamforming weights associated with the second service 164 and the second user group.
[0062] In a particular implementation, the first BFN 112 adjusts RF signals corresponding to the first service 160 and the first group of users based on a first set of beamforming weights, and the second BFN 114 adjusts RF signals corresponding to the second service 164 and the second group of users based on a second set of beamforming weights. Adjusting the RF signals may include modifying the amplitude, phase, other characteristics, or a combination thereof, of the RF signals. Adjusting the RF signals based on the beamforming weights may also be referred to as "applying beamforming weights to the RF signals."
[0063] In a particular implementation, the first BFN 112 is configured to adjust the RF signal by applying one or more first beamforming weights of the beamforming data 110 (e.g., based on the RF signal being associated with a first service 160 and a first user group), and the BFN 114 is configured to adjust another RF signal by applying one or more second beamforming weights of the beamforming data 110 (e.g., based on the other RF signal being associated with a second service 164 and a second user group). Applying the beamforming weights adjusts the phase, amplitude, other characteristics, or a combination thereof, of the RF signal based on the specific beamforming weights for each user. This may increase the directionality and spatial selectivity of the RF signal toward the device. The beamforming data 110 or a portion of the beamforming data 110 (e.g., the portion corresponding to a particular user group and a particular service) may be updated according to changes in traffic load patterns, user group policies, or service policies.
[0064] In a particular implementation, the switching circuitry 104 generates multiple beams based on the first RF signal and the third RF signal. Illustratively, the RF signal is received at an analog front end of the switching circuitry 104, converted to the digital domain, switched through a multi-stage interconnect network, and converted back to the analog domain by the analog back end of the switching circuitry 104. The RF signals are deployed by the satellite 102 over various portions of the frequency spectrum (e.g., based on the channel mapping data 186). For example, the first RF signal may be converted to a particular portion of the frequency spectrum associated with a first service 160 and a first user group, and the second RF signal may be converted to another particular portion of the frequency spectrum associated with a second service 164 and a second user group. Satellite 102 transmits a second RF signal (e.g., deploys one or more beams associated with the second RF signal in first pattern 162) and a fourth RF signal (e.g., deploys one or more beams associated with the fourth RF signal in second pattern 166) to first device 172 and second device 174, respectively, over corresponding portions of the frequency spectrum.
[0065] The system 100 may provide "end-to-end" logical separation of traffic on a per-user-group and per-service basis by maintaining separate VRF instances for separate pairs of user groups and services and communicating traffic associated with the separate pairs of user groups and services over separate RF channels (or other portions of the frequency spectrum). As an example, traffic associated with the first service 160 and the first user group is encapsulated and differentiated based on a first VRF instance as compared to traffic associated with the second service 164 and the second user group. The traffic associated with the first service 160 and the first user group is routed through components of the system 100 (e.g., the core network 130 and the network 156) over one or more paths that may be different from the one or more paths over which the traffic associated with the second service 164 and the second user group is routed. By way of further example, the traffic associated with the first service 160 and the first user group is sent to (or received from) the first device 172 over a different RF channel than the traffic associated with the second service 164 and the second user group. Providing logical separation of traffic on a per-user group and per-service basis increases security for each user group and service compared to processing the traffic of all user groups and services together. Separating traffic on a per-user group and per-service basis increases security of system 100. The adaptability of system 100 may also be increased compared to systems that do not separate traffic by user group and service. For example, system 100 may be configured to process traffic associated with a particular user group and service pairing according to different rules and policies than other user group and service pairs.
[0066] In the above description, various functions performed by the system 100 of FIG. 1 are described as being performed by components 102-108, 112-118, 134, 136, and 142. This is for illustrative purposes only. In other implementations, one or more of the components 102-108, 112-118, 134, 136, and 142 may be integrated into a single component that performs the functions associated with the multiple components. In addition, various functions are described as being performed by the processor 120 based on execution of instructions stored in the memory 122 or by the processor 144 based on execution of instructions stored in the memory 146. This is for illustrative purposes only. In alternative implementations, one or more functions performed by the processor 120 or the processor 144 may instead be performed by one or more hardware components. For example, the first component may generate a packet based on the composite RIB data 148 and the first VRF instance RIB data 150. Each component may be implemented using hardware (e.g., a field programmable gate array (FPGA) device, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a controller, etc.), software (e.g., instructions executable by a processor), or a combination thereof.
[0067] 2 illustrates an example of a system 200 configured to process network traffic associated with different VRF instances corresponding to different pairs of user groups and services. System 200 includes RFE 106, base station 118, network device 142, subscriber data server 136, and IP multimedia subsystem server 134 of FIG. 1. In addition, system 200 includes cellular system 202, switching circuitry 204, and beam forming network 206. Although components 202, 204, 206, 106, 118, 134, 136, and 142 are illustrated as being included in system 200, in other implementations, one or more of components 202, 204, 206, 106, 118, 134, 136, and 142 are not included (with corresponding functionality being performed by one or more of the remaining components).
[0068] The components 106, 118, 134, 136, and 142 are configured to perform the operations described in conjunction with Figure 1. The switching circuitry 204 and the beam forming network 206 are configured to perform the operations described in conjunction with the switching circuitry 104 and the beam forming network 108 of Figure 1. As one example, the switching circuitry 204 generates RF signals to be transmitted to one or more devices over various RF channels (or other portions of the frequency spectrum) based on the channel mapping data 210, as described in conjunction with Figure 1. As another example, the beam forming network 206 adjusts one or more RF signals based on beam forming weights associated with a particular user group and service pair, as indicated by the beam forming data 208, to adjust the amplitude, phase, etc., of the one or more RF signals, as described in conjunction with Figure 1. However, in the implementation shown in Figure 2, the switching circuitry 204 and the beam forming network 206 are communicatively coupled between the RFE 106 and the base station 118 (instead of being integrated within the satellite).
[0069] In a particular implementation, the RF signal generated by the switching circuitry 204 (and processed by the RFE 106) is transmitted (e.g., deployed) by the cellular system 202 to one or more subscriber devices. The cellular system 202 includes one or more components (e.g., antenna(s), satellite(s), tower(s), etc.) configured to provide RF signals from one location to another. In a particular implementation, the cellular system 202 includes or corresponds to a terrestrial cellular system. In another particular implementation, the cellular system 202 includes or corresponds to a hybrid system (e.g., a system including terrestrial components, such as one or more towers, and one or more satellites).
[0070] In operation, system 200 provides end-to-end network traffic isolation for separate pairs of user groups and services, as described in connection with system 100 of Figure 1. However, in contrast to system 100 of Figure 1, channel mapping and beamforming operations are performed by terrestrial components. Illustratively, channel mapping and beamforming operations are performed by switching circuitry 204 and beamforming network 206, respectively, which are terrestrial components and communicatively coupled between RFE 106 and base station 118. Reducing the number of components integrated within the satellite may reduce costs and improve ease of repair of system 200.
[0071] 3 illustrates an example of a system 300 configured to process network traffic associated with separate VRF instances corresponding to separate pairs of user groups and services. System 300 includes switching circuitry 104, RFE 106, beam forming network 108, network device 142, subscriber data server 136, and IP multimedia subsystem server 134 of FIG. 1. In addition, system 300 includes satellite 302 and operations center 330. Although components 104, 106, 108, 134, 136, 142, 302, and 330 are illustrated as being included in system 300, in other implementations, one or more of components 104, 106, 108, 134, 136, 142, 302, and 330 are not included (with corresponding functionality being performed by one or more of the remaining components).
[0072] The components 104, 106, 108, 134, 136, and 142 are configured to perform the operations described in conjunction with Figure 1. As an example, the switching circuitry 104 generates RF signals to be transmitted to one or more devices over various RF channels (or other portions of the frequency spectrum) based on the channel mapping data 186, as described in conjunction with Figure 1. As another example, the beam forming network 108 adjusts one or more RF signals based on beam forming weights associated with a particular user group and service pair, as indicated by the beam forming data 110, to adjust the amplitude, phase, etc. of the one or more RF signals, as described in conjunction with Figure 1. The RFE 106 is configured to process RF signals received by the satellite 302 from one or more devices, or RF signals to be sent (transmitted) from the satellite 302 to one or more devices. The network device 142 is configured to receive data packets from the modem and generate packets to be sent to other devices in the network 156. However, in the particular implementation shown in Figure 3, the RFE 106 and the network device 142 are integrated within the satellite 302. For example, the payload 384 of the satellite 302 includes the network device 142, the first modem pool 125, the second modem pool 127, and the Nth modem pool 129. Illustratively, each of the first modem pool 125, the second modem pool 127, and the Nth modem pool 129 are instantiated in the payload 384. In some aspects, the implementation shown in Figure 1 is referred to as a "transparent architecture" and the implementation shown in Figure 3 is referred to as a "regenerative architecture." For example, the satellite 102 is configured to process analog RF signals, while the satellite 302 is configured to regenerate RF energy into digital modem frames that encapsulate network packets. The IP multimedia subsystem server 134 and the subscriber data server 136 are integrated within the operations center 330 (e.g., outside the satellite 302).In particular implementations, one or more of the operations described with respect to the components of the satellite 302 are performed by a processor 380 of the satellite 302 .
[0073] In operation, system 300 provides end-to-end network traffic isolation for separate pairs of user groups and services, as described in connection with system 100 of Figure 1. However, in contrast to system 100 of Figure 1, modem operations and packet conversion operations (e.g., between data packets corresponding to RF signals and network packets communicated over network 156) are performed by satellite components. Illustratively, modem operations and packet conversion operations are performed by one or more of first modem pool 125, second modem pool 127, and Nth modem pool 129 of payload 384 of satellite 302 and network device 142, respectively.
[0074] FIG. 4 depicts a ladder diagram 400 illustrating a first example of network traffic communicated through the system 100 of FIG. 1. In a particular implementation, the operations illustrated in FIG. 4 are performed by the first device 172, the second device 174, the system front end 402, the first modem 124, the second modem 126, the network device 142, and one or more devices 404. In a particular implementation (e.g., as illustrated in FIG. 1), the system front end 402 refers to the satellite 102, the switching circuitry 104, the RFE 106, the beam forming network 108, or a combination thereof. In a particular implementation (e.g., as illustrated in FIG. 2), the system front end 402 refers to the cellular system 202, the RFE 106, the switching circuitry 204, the beam forming network 206, or a combination thereof. In a particular implementation (e.g., as illustrated in FIG. 3), the system front end 402 refers to the switching circuitry 104, the RFE 106, the beam forming network 108, or a combination thereof.
[0075] As depicted in Figure 4, the first device 172 performs a first association operation(s) 410 with a base station 118 (or satellite 302) and a network device 142 to associate with the system 100 of Figure 1, the system 200 of Figure 2, or the system 300 of Figure 3. The first association operation(s) 410 may include a radio link binding operation, a network registration operation, an IMS registration operation, or a combination thereof.
[0076] In a particular implementation, the first device 172 is associated with the first service 160 (e.g., the first device 172 subscribes to the first service 160 for the first user group) and performs one or more radio link binding operations according to one or more wireless communication standards (e.g., the Third Generation Partnership Project (3GPP) standard). Illustratively, the first device 172 synchronizes with available operator frequencies and receives Master Information Block (MIB) data and System Information Block (SIB) data. The MIB data and SIB data indicate available operators associated with the system 100 (or system 200) and information used to connect to the system 100 (or 200 associated therewith). The first device 172 initiates a random access channel (RACH) procedure to join the network. As part of the RACH procedure, the first device 172 and the base station 118 (or satellite 302) perform a handshake procedure that results in the establishment of a MAC layer connection between the first device 172 and the first modem 124.
[0077] In certain implementations, the first device 172 performs one or more network registration operations after one or more radio link coupling operations. In some implementations, the one or more network registration operations follow one or more wireless standards (e.g., 3GPP standards). By way of example, the first device 172 initiates a handshake procedure with an MME (e.g., network device 142) to verify and authenticate the identity of the first device 172 and the network, respectively. In the handshake procedure, the MME cooperates with an Equipment Identity Registration (EIR) to verify that the first device 172 is authorized to access the network. The MME and EIR store and maintain data regarding each user group and each service for performing the handshake procedure. The MMR manages a second handshake procedure with the SGW, PGW, and base station 118 (or satellite 302) that will allocate a session (e.g., with a core network 130, such as an Evolved Packet Core (EPC) network) and establish an Early Evolved Packet System (EPS) bearer with the first device 172. The network devices 142 (e.g., MME, SGW, PGW) and base station 118 (or satellite 302) are configured to store data associated with each user group and each service and to support multi-VRF RIB data and queue structures. The network devices 142 (e.g., MME, SGW, PGW) may create additional EPS bearers in response to a first service 160 being requested by the first device 172. The first device 172 is enabled to transmit and receive data via the system 100 (or system 200) once one or more radio binding operations and one or more network registration operations have been completed.
[0078] In a particular implementation, the first device 172 performs one or more IMS registration operations after completing one or more network registration operations. Illustratively, the first device 172 initiates an IMS registration procedure by sending a Session Initiation Protocol (SIP) registration message to the IP multimedia subsystem server 134 of FIG. 1, FIG. 2, or FIG. 3. A Proxy Call Setup Control Function (P-CSCF) of the IP multimedia subsystem server 134 receives the SIP registration message and initiates a handshake procedure between the P-CSCF, an Interrogating CSCF (I-CSCF) of the IP multimedia subsystem server 134, and a Serving CSCF (S-CSCF) of the IP multimedia subsystem server 134 to verify the authorization of the first device 172 to access IMS-based services. The S-CSCF also performs a handshake procedure with a Telephony Application Server (TAS) to enable the TAS to search a home subscriber server database for Voice over Long Term Evolution (VoLTE) data associated with the first device 172. The first device 172, the P-CSCF, and the TAS then participate in a handshake procedure and subscribe to a registration event package in order to be aware of future changes in the registration status associated with the first device 172. The second device 174 performs second association operation(s) 412 with the base station 118 (or satellite 302) and the network device 142 similar to the first association operation(s) 410, except that the second device 174 is associated with a second service 164 and a second user group. The above-described association operations are exemplary and not limiting. In other implementations, one or more other association operations are performed, one or more of the above-described association operations are not performed, or both.
[0079] The first device 172 sends a first RF signal 414 to the system front end after the first association operation(s) 410 are performed. The system front end receives the first RF signal 414 and performs initial processing (e.g., amplification, filtering, noise reduction, etc.) before sending the first RF signal 414 to the base station 118 (or the payload 384 of the satellite 302). The first modem 124 receives the first RF signal 414 and generates a first data packet 416. The first data packet includes first data 420 (e.g., data represented by the first RF signal 414) and a first identifier 422. In a particular implementation, the first identifier 422 includes or corresponds to a label. The label includes a switching tag (also referred to as a virtual local area network (VLAN) tag or 802.1Q tag), a VRF instance identifier, and an open shortest path first (OSPF) process identifier (PID).
[0080] The first data packet 416 is sent from the first modem 124 to the network device 142. The network device 142 receives the first data packet 416 and generates a first packet 418 based on the first data packet 416. The first packet 418 includes the first data 420 and a first indicator 424. In a particular implementation, the network device 142 is configured to replicate any changes made to the per-VRF instance RIB data in the composite RIB data 148 (e.g., also referred to as a backbone RIB or a global VRF instance RIB). Illustratively, the composite RIB data 148 is updated based on updates to the first VRF instance RIB data 150. Additionally, the first identifier 422 is separated from the first data 420, and the first packet 418 includes a first indicator 424. The first indicator 424 (e.g., a “per-VRF identifier”) indicates a VRF instance associated with the first service 160 and the first user group. In certain implementations, the first indicator 424 is included in a header of the first packet 418. In some implementations, the first indicator 424 is indicated by a source address or source port number in the header of the first packet 418. After the first packet 418 is generated, it is sent to one or more devices 404 via the core network 130 and network 156 of FIG. 1 or 2, or via network 156 of FIG. 3.
[0081] The second device 174 sends a second RF signal 430 to the system front end after the second association operation(s) 412 are performed. The system front end receives the second RF signal 430 and performs initial processing (e.g., amplification, filtering, noise reduction, etc.) before sending the second RF signal 430 to the base station 118 (or the payload 384 of the satellite 302). The second modem 126 receives the second RF signal 430 and generates a second data packet 432. The second data packet includes second data 440 (e.g., data represented by the second RF signal 430) and a second identifier 442. In a particular implementation, the second identifier 442 includes or corresponds to a label. The label includes a switch tag, a VRF instance identifier, and an OSPF PID.
[0082] The second data packet 432 is sent from the second modem 126 to the network device 142. The network device 142 receives the second data packet 432 and generates a second packet 434 based on the second data packet 432. The second packet 434 includes the second data 440 and a second indicator 444. In a particular implementation, the network device 142 is configured to recreate any changes made to the per-VRF instance RIB data in the composite RIB data 148. Illustratively, the composite RIB data 148 is updated based on updates to the second VRF instance RIB data 152. Additionally, the second identifier 442 is separated from the second data 440, and the second packet 434 includes the second indicator 444. The second indicator 444 indicates a VRF instance associated with the second service 164 and the second user group. In a particular implementation, the second indicator 444 is included in a header of the second packet 434. In some implementations, the second indicator 444 is indicated by a source address or source port number in a header of the second packet 434. After the second packet 434 is generated, it is sent to one or more devices 404 via the core network 130 and network 156 of Figure 1 or 2, or via network 156 of Figure 3.
[0083] Figure 5 illustrates a ladder diagram 500 showing a second example of network traffic communicated via the system 100 of Figure 1, the system 200 of Figure 2, or the system 300 of Figure 3. In a particular implementation, the operations illustrated in Figure 5 are performed by the first device 172, the second device 174, the system front end 402, the first modem 124, the second modem 126, the network device 142, and one or more devices 404.
[0084] As depicted in FIG. 5 , the network device 142 receives a third packet 502 from one or more devices 404. The third packet includes third data 510 and a first indicator 424. The first indicator 424 indicates a VRF instance associated with the first service 160 and the first user group. In certain implementations, the first indicator 424 is included in a header of the third packet 502. In some implementations, the first indicator 424 is indicated by a source address or a source port number in the header of the third packet 502. In certain implementations, the network device 142 is configured to update the composite RIB data 148 based on the third packet 502 and replicate any changes made to the composite RIB data 148 in the corresponding per-VRF instance RIB data. Illustratively, the first VRF instance RIB data 150 is updated based on the update of the composite RIB data 148.
[0085] The network device 142 receives the third packet 502 and generates a third data packet 504 based on the third packet 502. The third data packet 504 includes the third data 510 and the first identifier 422. In a particular implementation, the first identifier 422 includes or corresponds to a label. The label includes a switching tag (also referred to as a VLAN tag or 802.1Q tag), a VRF instance identifier, and an OSPF PID. Illustratively, the first indicator 424 is separated from the third packet 502 and the third data 510 is encapsulated in the third data packet 504 along with the first identifier 422.
[0086] The first modem 124 receives the third data packet 504 and modulates the third data 510 to generate a third RF signal 506. For example, the third data packet 504 is received and processed at the first modem 124 (e.g., a modem in the first modem pool 125 associated with the first service 160 and the first user group) based on a first identifier 422 that identifies the first VRF instance (corresponding to the first service 160 and the first user group). The third RF signal 506 represents the third data 510 and is provided by the system front end 402 for further processing (e.g., by the RFE 106) and transmission to the first device 172. In a particular implementation, the third RF signal 506 corresponds to an RF channel (or other portion of the frequency spectrum) associated with the first service 160 and the first user group.
[0087] The network device 142 also receives a fourth packet 520 from one or more devices 404. The fourth packet includes fourth data 540 and a second indicator 444. The second indicator 444 indicates a VRF instance associated with the second service 164 and the second user group. In certain implementations, the second indicator 444 is included in a header of the fourth packet 520. In some implementations, the second indicator 444 is indicated by a source address or source port number in the header of the fourth packet 520. In certain implementations, the network device 142 is configured to update the composite RIB data 148 based on the fourth packet 520 and replicate any changes made to the composite RIB data 148 in the corresponding per-VRF instance RIB data. Illustratively, the second VRF instance RIB data 152 is updated based on the update of the composite RIB data 148.
[0088] The network device 142 receives the fourth packet 520 and generates a fourth data packet 522 based on the fourth packet 520. The fourth data packet 522 includes the fourth data 540 and the second identifier 442. In a particular implementation, the second identifier 442 includes or corresponds to a label. The label includes a switching tag (also referred to as a VLAN tag or 802.1Q tag), a VRF instance identifier, and an OSPF PID. Illustratively, the second indicator 444 is separated from the fourth packet 520 and the fourth data 540 is encapsulated within the fourth data packet 522 along with the second identifier 442.
[0089] The second modem 126 receives the fourth data packet 522 and modulates the fourth data 540 to generate a fourth RF signal 524. For example, the fourth data packet 522 is received and processed at the second modem 126 (e.g., a modem in the second modem pool 127 associated with the second service 164 and the second user group) based on a second identifier 442 that identifies a second VRF instance (corresponding to the second service 164 and the second user group). The fourth RF signal 524 represents the fourth data 540 and is provided by the system front end 402 for further processing (e.g., by the RFE 106) and transmission to the second device 174. In a particular implementation, the fourth RF signal 524 corresponds to an RF channel (or other portion of the frequency spectrum) associated with the second service 164 and the second user group.
[0090] Figure 6 illustrates a method 600 for processing network traffic received from a device based on a user group and service associated with the device. In a particular implementation, method 600 is performed by, as non-limiting examples, system 100 of Figure 1, system 200 of Figure 2, or system 300 of Figure 3. Method 600 is conveniently described with reference to a particular service (e.g., first service 160) and a particular user group (e.g., first user group), although such description is intended to be non-limiting.
[0091] The method 600 includes receiving 602 an RF signal from a subscriber device (e.g., a UE or wireless communication terminal) associated with a user group and service over a particular RF channel accessible to the subscriber device associated with the user group and service after the subscriber device associates with a network device to establish a session with the network. As a particular example, after a first device 172 associates with a network device 142, a satellite 102 (or satellite 302) receives an RF signal from the first device 172 over an RF channel associated with a first service 160 and a first user group (e.g., a first MVNO).
[0092] Method 600 includes performing front-end processing on the RF signal at the RFE, at 604. As a particular example, the RF signal is used to generate a second RF signal (e.g., an RF signal corresponding to a second RF channel associated with the first service 160 and the first user group), which is transmitted to the RFE 106. The RFE 106 performs front-end processing (e.g., amplification, noise reduction, etc.) on the second RF signal.
[0093] The method 600 includes, at 606, allocating a first modem of a first modem pool to process the RF signal to generate a data packet including the data and an identifier of the first VRF instance associated with the user group and service based on the association of the subscriber device with such user group and service. As a particular example, the base station 118 (or satellite 302) allocates a first modem 124 of the first modem pool 125 to process a second RF signal based on the association of the second RF signal with the first service 160 and the first user group (indicated by the second RF signal corresponding to a second RF channel associated with the first service 160 and the first user group). After being assigned to the second RF signal, the first modem 124 generates a first VRF instance that identifies a first data packet instance including the first data and the first VRF identifier associated with the first service 160 and the first user group.
[0094] The method 600 includes generating a packet at the network device, at 608. The packet includes data and a header including an indicator of a VRF instance based on the composite RIB data. As a particular example, the network device 142 generates a first packet including the first data and an indicator (e.g., a label or 5-tuple, as a non-limiting example) of a first VRF instance associated with the first service 160 and the first user group based on the composite RIB data 148. The method 600 includes updating, at 610, the RIB data associated with the VRF instance based on the data packet, and updating, at 612, the composite RIB data based on the RIB data associated with the VRF instance. As a particular example, the network device 142 updates the first VRF instance RIB data 150 based on the first data packet before generating the packet, and updates the composite RIB data 148 based on the update of the first VRF instance RIB data 150 (or any update of the RIB data specific for each other VRF).
[0095] The method 600 includes updating subscriber information associated with the first VRF instance based on the packet, at 614. As a particular example, the subscriber data server 136 updates the first subscriber data 138 (e.g., subscriber data associated with the VRF instance corresponding to the first service 160 and the first user group) based on the first packet.
[0096] Method 600 further includes transmitting the packet over the network to the device, at 616. As a particular example, the first packet travels through core network 130, network 156, or both, via a first route to the destination device. The first route is indicated by first VRF instance RIB data 150 and may be different from routes traveled by packets associated with other VRF instances (and other pairs of user groups and services).
[0097] Method 600 provides end-to-end network traffic isolation for separate pairs of user groups and services by communicating RF signals for the separate pairs of user groups and services over separate RF channels (e.g., separate portions of a frequency spectrum) and by maintaining separate VRF instances for the separate pairs of user groups and services. Providing end-to-end network traffic isolation reduces the likelihood that data associated with a particular pair of user groups and services will be accessible to subscribers of different pairs of user groups and services.
[0098] FIG 7 illustrates a method 700 for processing traffic to be sent to a device based on a user group and a service associated with the device. In certain implementations, method 700 is performed by system 100 of FIG 1, system 200 of FIG 2, or system 300 of FIG 3, as non-limiting examples. In some implementations, method 700 is performed after method 600 of FIG 6 is performed or before method 600 of FIG 6 is performed. Method 700 is described for convenience with respect to a particular service (e.g., second service 164) and a particular user group (e.g., second user group), although such description is non-limiting.
[0099] The method 700 includes, at 702, receiving a packet at a network device from another device over a network. The packet includes data and a header that includes an indicator of a VRF instance associated with a user group and a service. As a particular example, the network device 142 receives a second packet from the device over the network 156, the core network 130, or both. The second packet includes second data and a second header that indicates a second indicator of a second VRF instance associated with a second service 164 and a second user group (e.g., a second MVNO).
[0100] The method 700 includes updating subscriber information associated with the VRF instance based on the packet, at 704. As a particular example, the subscriber data server 136 receives the second packet and updates the second subscriber data 140 based on the second packet before the network device 142 receives the second packet.
[0101] The method 700 includes generating, at 706, a data packet including the data and an identifier of the VRF instance based on the RIB data associated with the VRF instance. As a particular example, the network device 142 generates a second data packet including the second data and the second VRF identifier based on the second VRF instance RIB data 152. The method 700 includes updating, at 708, the composite RIB data based on the packet, and updating, at 710, the RIB data associated with the VRF instance based on the composite RIB data. As a particular example, the network device 142 updates the composite RIB data 148 based on the second packet and updates the second VRF instance RIB data 152 based on the update of the composite RIB data 148 before generating the second data packet.
[0102] The method 700 includes, at 712, transmitting a data packet from the network device to a modem of the first modem pool based on the VRF instance identifier. The data packet includes data and the VRF instance identifier. Illustratively, the base station 118 (or satellite 302) assigns a second modem 126 (of a second modem pool 127 associated with the second service 164 and the second user group) to process the second data packet based on the second data packet including a second VRF instance identifier corresponding to a second VRF instance (e.g., a VRF instance associated with the second service 164 and the second user group).
[0103] The method 700 includes generating, at 714, an RF signal based on the data packet at the modem. As a particular example, the second modem 126 generates a second RF signal based on the second data packet and provides the second RF signal to the RFE 106 for front-end processing (e.g., amplification, filtering, etc.). In a particular implementation, the second modem 126 associates the second RF signal with a particular logical interface associated with the second service 164 and the second user group (or routes the RF signal to a particular port associated with the second service 164 and the second user group).
[0104] The method 700 further includes, at 716, transmitting an RF signal over a particular RF channel to the subscriber device associated with the user group and service. As a particular example, the satellite 102 (or the payload 384 of the satellite 302) receives the second RF signal from the RFE 106 over a particular RF channel associated with the second service 164 and the second user group. The satellite 102 (or the satellite 302) generates a third RF signal corresponding to the second RF channel associated with the second service 164 and the second user group and designated for communication between the device and the satellite 102 (or the satellite 302) based on the second RF signal being associated with the second service 164 and the second user group. In a particular implementation, the satellite 102 (or the satellite 302) transmits the third RF signal to the second device 174 over the second RF channel.
[0105] Method 700 provides end-to-end network traffic isolation for separate pairs of user groups and services by communicating RF signals for the separate pairs of services and user groups over separate RF channels (e.g., separate portions of a frequency spectrum) and by maintaining separate VRF instances for the separate pairs of user groups and services. Providing end-to-end network traffic isolation reduces the likelihood that data associated with a particular pair of user groups and services will be accessible to subscribers of a different pair of user groups and services.
[0106] 8 illustrates a method 800 for processing network traffic associated with different VRF instances corresponding to different pairs of user groups and services. In a particular implementation, method 800 is performed by (e.g., by network device 142) system 100 of FIG. 1, system 200 of FIG. 2, or system 300 of FIG. 3, as non-limiting examples.
[0107] The method 800 includes receiving 802, at a network device, a first data packet from a first modem of a first modem pool. For example, the network device 142 receives a first data packet 416 from a first modem 124 of the first modem pool 125, as described in connection with FIGURE 4. The first data packet 416 includes first data 420 and a first identifier 422 (e.g., a first VRF instance identifier).
[0108] The method 800 includes, at 804, transmitting a first packet from the network device to the first device over the network. For example, the network device 142 transmits a first packet 418 to the first device 172 over the core network 130, the network 156, or both, as described in connection with FIG. 4. The first packet 418 includes first data 420 and a first header including a first indicator 424 associated with a first VRF instance. The first identifier 422 (e.g., a first VRF instance identifier) is associated with the first service 160 and the first user group. The first identifier 422 (e.g., a first VRF instance identifier) corresponds to (e.g., identifies) the first VRF instance associated with the first service 160 and the first user group.
[0109] The method 800 includes receiving, at the network device, a second data packet from a second modem of a second modem pool, at 806. For example, the network device 142 receives a second data packet 432 from a second modem 126 of the second modem pool 127, as described in connection with FIGURE 4. The second data packet 432 includes second data 440 and a second identifier 442 (e.g., a second VRF instance identifier).
[0110] The method 800 further includes, at 808, transmitting a second packet from the network device to the second device over the network. For example, the network device 142 transmits the second packet 434 over the core network 130, the network 156, or both, as described in connection with FIG. 4. The second packet 434 includes the second data 440 and a second header including a second indicator 444 associated with a second VRF instance. The second identifier 442 (e.g., a second VRF instance identifier) is associated with the second service 164 and the second user group. The second identifier 442 (e.g., a second VRF instance identifier) corresponds to (e.g., identifies) a second VRF instance associated with the second service 164 and the second user group.
[0111] In certain implementations, the method 800 further includes generating first RIB data associated with the first VRF instance (e.g., first VRF instance RIB data 150) based on the first data packet 416 and generating second RIB data associated with the second VRF instance (e.g., second VRF instance RIB data 152) based on the second data packet 432. In some implementations, the method 800 further includes generating composite RIB data 148 (e.g., backbone RIB data) based on the first VRF instance RIB data 150 and the second VRF instance RIB data 152. In some implementations, the first header and the second header are generated based on the composite RIB data.
[0112] In another particular implementation, the method 800 further includes logically separating data associated with the second VRF instance from data associated with the first VRF instance by encapsulating the data associated with the first VRF instance using a different header than the data associated with the second VRF instance. As a particular example, data packets associated with different VRF instances generated by the base station 118 (or satellite 302) include different VRF instance identifiers (e.g., the first identifier 422 and the second identifier 442 of FIG. 4), and packets associated with different VRF instances generated by the network device 142 include headers that include different indicators (e.g., the first indicator 424 and the second indicator 444 of FIG. 4).
[0113] In another particular implementation, the method 800 further includes updating first subscriber information (e.g., first subscriber data 138) associated with the first VRF instance based on the first packet 418, and updating second subscriber information (e.g., second subscriber data 140) associated with the second VRF instance based on the second packet 434.
[0114] One or more of Figures 1-8 may illustrate systems, devices, and / or methods according to the teachings of the present disclosure, but the present disclosure is not limited to these illustrated systems, devices, and / or methods. One or more features or components of any of Figures 1-8 illustrated or described herein may be combined with one or more other portions of another of Figures 1-8. For example, one or more of the elements of method 600 of Figure 6, one or more of the elements of method 700 of Figure 7, one or more of the elements of method 800 of Figure 8, or combinations thereof may be performed in combination with other steps described herein. Thus, any single implementation described herein should not be construed as limiting, and implementations of the present disclosure may be suitably combined without departing from the teachings of the present disclosure. As an example, one or more operations described in connection with Figures 6-8 may be optional, may be performed at least partially simultaneously, and / or may be performed in a different order than illustrated or described.
[0115] Additionally, the present disclosure includes embodiments according to the following clauses:
[0116] Clause 1. A system for service and user group based communications, comprising: a plurality of modems corresponding to a plurality of modem pools, the plurality of modems configured to generate a first data packet based on a first radio frequency (RF) signal, the first data packet including a first data and a first virtual routing and forwarding (VRF) instance identifier, and a second modem corresponding to a second modem pool configured to generate a second data packet based on a second RF signal, the second data packet including a second data and a second VRF instance identifier, the system further comprising a network device in communication with the plurality of modems, the network device configured to receive the first data packet and transmit the first data packet over a network. the network device is further configured to receive a second data packet and transmit the second packet over the network to the second device, the second packet including the second data and a second header including the second indicator, the second indicator being associated with a second VRF instance corresponding to the second VRF instance identifier, the second VRF instance identifier being associated with a second service, a second user group, or both; system.
[0117] Clause 2. The first service includes first generation (1G) cellular communication, second generation (2G) cellular communication, third generation (3G) cellular communication, fourth generation (4G) cellular communication, fifth generation (5G) cellular communication, high speed packet access (HSPA), high speed downlink packet access (HSDPA), high speed uplink packet access (HSUPA), short message service (SMS), multimedia message service (MMS), Internet of Things (IoT) communication, Worldwide Interoperability for Microwave Access ( 13. The system of claim 1, comprising at least one of the following: WiMax communications, Institute of Electrical and Electronics Engineers (IEEE) 802.11x communications, Wi-Fi communications, Digital Video Broadcasting-Satellite (DVB-S) communications, Digital Video Broadcasting-Satellite-Second Generation (DVB-S2) communications, DVB-S2 Extended (DVB-S2X) communications, Digital Video Broadcasting-Return Channel via Satellite (DVB-RCS) communications, DVB Two-Way Satellite System Second Generation (DVB-RCS2) communications, or proprietary government system communications.
[0118] Clause 3. The system of clause 1, wherein the network device is further configured to receive a third packet from the first device over the network, the third packet including third data and a third header including a third indicator, the third indicator being associated with the first VRF instance, and to transmit a third data packet to the first modem, the third data packet including the third data and the first VRF instance identifier.
[0119] Clause 4. The system of clause 3, further comprising a beamforming network configured to adjust a third RF signal based on a first set of beamforming weights associated with a first user group and a first service, the first user group and the first service corresponding to a first VRF instance, and the third RF signal being generated based on a third data packet.
[0120] Clause 5. The system of clause 1, further comprising a radio frequency equipment (RFE) configured to transmit a third RF signal, the third RF signal being based on a third data packet received from the network device at the first modem, the third data packet including the first VRF instance identifier.
[0121] Clause 6. The system of clause 5, further comprising switching circuitry configured to generate a plurality of sets of RF signals, each set of RF signals associated with a corresponding portion of the RF spectrum, the plurality of sets of RF signals including at least one RF signal associated with a particular portion of the RF spectrum associated with a user group and service.
[0122] Clause 7. The system of clause 6, further comprising a cellular system configured to deploy multiple sets of RF signals in an overlapping pattern at a first location, wherein a particular portion of the RF spectrum is accessible by devices associated with a user group and service at the first location and is inaccessible by devices not associated with the user group and service.
[0123] Clause 8. The system of clause 7, wherein the cellular system comprises a satellite-based cellular system or a terrestrial-based cellular system.
[0124] Clause 9. The system of clause 6, wherein the user group includes a first mobile virtual network operator (MVNO), and the plurality of modems and network devices are configured to logically separate traffic associated with the first MVNO and service from traffic associated with a second MVNO and another service.
[0125] Clause 10. The system of clause 1, wherein a plurality of modem pools are associated with a plurality of VRF instance identifiers, and each modem of the plurality of modem pools is configured to process traffic associated with a corresponding VRF instance identifier, and the corresponding VRF instance identifier is associated with a service, a user group, or both.
[0126] Clause 11. The system of clause 1, wherein the first modem is further configured to encrypt the first data packet based on a first encryption associated with the first VRF instance, and the second modem is further configured to encrypt the second data packet based on a second encryption associated with the second VRF instance.
[0127] Clause 12. A satellite comprising: a payload having one or more antennas; a memory configured to store channel mapping data indicating a mapping of at least one radio frequency (RF) channel to another RF channel; and a processor configured to initiate transmission of a second RF signal from the one or more antennas to a first device based on the channel mapping data, a first service associated with the first device, and a first user group associated with the first device, the second RF signal being based on a first RF signal received at the one or more antennas from a radio frequency equipment (RFE), the first RF signal corresponding to the first RF channel, and the second RF signal corresponding to a second RF channel different from the first RF channel. satellite.
[0128] Clause 13. The satellite of clause 12, wherein the processor is further configured to initiate transmission of a fourth RF signal from one or more antennas to the second device based on the channel mapping data, a second service associated with the second device, and a second user group associated with the second device, the fourth RF signal being based on a third RF signal received from the RFE at the one or more antennas, the third RF signal corresponding to a third RF channel different from the first RF channel, and the fourth RF signal corresponding to a fourth RF channel different from the third RF channel and the second RF channel.
[0129] Clause 14. The satellite of clause 13, wherein the one or more antennas are configured to overlap transmission of the second RF signal and the fourth RF signal at the same location.
[0130] Clause 15. The satellite of clause 12, further comprising a beamforming network configured to adjust the second RF signal based on beamforming data stored in the memory and the first RF signal, the beamforming data indicating one or more sets of beamforming weights associated with one or more user groups and one or more services.
[0131] Clause 16. The satellite of clause 12, wherein the processor is further configured to initiate transmission of a sixth RF signal from one or more antennas to the first device based on the channel mapping data, the first service, and the first user group, the sixth RF channel being based on a fifth RF signal received from the RFE at the one or more antennas, the fifth RF signal corresponding to the first RF channel and the sixth RF signal corresponding to the second RF channel.
[0132] Clause 17. Receiving, in a network device, a first data packet from a first modem of a first modem pool, the first data packet including first data and a first virtual routing and forwarding (VRF) instance identifier; and transmitting the first packet from the network device over a network to the first device, the first packet including the first data and a first header including a first indicator, the first indicator being associated with the first VRF instance, the first VRF instance identifier being associated with a first service and a first user group. receiving, at the network device, a second data packet from a second modem of a second modem pool, the second data packet including the second data and a second VRF instance identifier; and transmitting, from the network device over the network to the second device, the second packet including the second data and a second header including a second indicator, the second indicator being associated with the second VRF instance, the second VRF instance identifier being associated with a second service and a second user group. method.
[0133] Clause 18. The method of clause 17, wherein each of the first modem pool, the second modem pool, the first VRF instance, and the second VRF instance is instantiated in a payload of a satellite.
[0134] Clause 19. The method of clause 17, wherein each of the first modem pool, the second modem pool, the first VRF instance, and the second VRF instance is instantiated in one or more terrestrial components.
[0135] Clause 20. The method of clause 17, further comprising: generating first Routing Information Base (RIB) data associated with the first VRF instance based on the first data packet; and generating second RIB data associated with the second VRF instance based on the second data packet.
[0136] Clause 21. The method of clause 20, further comprising generating composite RIB data based on the first RIB data and the second RIB data, wherein the first header and the second header are generated based on the composite RIB data.
[0137] Clause 22. The method of clause 17, further comprising: logically separating data associated with the second VRF instance from data associated with the first VRF instance by encapsulating the data associated with the first VRF instance using a different header than the data associated with the second VRF instance.
[0138] Clause 23. The method of clause 17, further comprising updating first subscriber information associated with the first VRF instance based on the first packet, and updating second subscriber information associated with the second VRF instance based on the second packet.
[0139] The illustrations described herein are intended to provide a general understanding of the structure of various implementations. These illustrations are not intended to serve as an exhaustive description of all elements and features of apparatus and systems that utilize the structures or methods described herein. Many other implementations may become apparent to those of ordinary skill in the art upon review of this disclosure. Other implementations may be utilized and derived from this disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. For example, method steps may be performed in an order different from that shown in the figures, or one or more method steps may be omitted. Accordingly, the disclosure and drawings are to be considered illustrative rather than restrictive.
[0140] Moreover, although specific examples have been illustrated and described herein, it should be recognized that subsequent configurations designed to achieve the same or similar results may be substituted for the specific implementations shown. This disclosure is intended to cover all subsequent adaptations and variations of the various implementations. Combinations of the above implementations, as well as other implementations not specifically described herein, will be apparent to one of ordinary skill in the art upon review of this specification.
[0141] The "Abstract" of the disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above "Description of the Preferred Embodiments," various features may be grouped together or described in a single implementation for the purpose of making the disclosure easier to understand. The above examples illustrate the disclosure, but do not limit it. It should also be understood that numerous modifications and variations are possible in accordance with the principles of the disclosure. As reflected in the following claims, the claimed subject matter may not be directed to all features of any of the disclosed examples. The scope of the disclosure is therefore defined by the following claims and their equivalents.
Claims
1. 1. A system for service and user group based communications, comprising: A plurality of modems corresponding to a plurality of modem pools, the plurality of modems comprising: a first modem corresponding to a first modem pool configured to generate a first data packet based on a first radio frequency (RF) signal, the first data packet including first data and a first virtual routing and forwarding (VRF) instance identifier; and a second modem corresponding to a second modem pool configured to generate a second data packet based on a second RF signal, the second data packet including second data and a second VRF instance identifier; and the system further comprises: a network device in communication with the plurality of modems, the network device comprising: a first data packet configured to receive the first data packet and transmit the first packet over a network to a first device, the first packet including the first data and a first header including a first indicator, the first indicator being associated with a first VRF instance corresponding to the first VRF instance identifier, the first VRF instance identifier being associated with a first service, a first user group, or both, the network device further configured to: configured to receive the second data packet and transmit the second packet via the network to a second device, the second packet including the second data and a second header including a second indicator, the second indicator being associated with a second VRF instance corresponding to the second VRF instance identifier, the second VRF instance identifier being associated with a second service, a second user group, or both; each of the first modem pool, the second modem pool, the first VRF instance, and the second VRF instance is instantiated in a payload of a satellite; system.
2. The first service is a first generation (1G) cellular communication, a second generation (2G) cellular communication, a third generation (3G) cellular communication, a fourth generation (4G) cellular communication, a fifth generation (5G) cellular communication, a high speed packet access (HSPA), a high speed downlink packet access (HSDPA), a high speed uplink packet access (HSUPA), a short message service (SMS), a multimedia message service (MMS), an Internet of Things (IoT) communication, a Worldwide Interoperability for Microwave Access (W 13. The system of claim 1, further comprising at least one of: an IEEE 802.11x (IEEE) ...
3. The network device comprises: receiving a third packet from the first device over the network, the third packet including third data and a third header including a third indicator, the third indicator associated with the first VRF instance; 3. The system of claim 1, further configured to: transmit a third data packet to the first modem, the third data packet including the third data and the first VRF instance identifier.
4. 4. The system of claim 3, further comprising: a beamforming network configured to adjust a third RF signal based on a first set of beamforming weights associated with the first user group and the first service, the first user group and the first service corresponding to the first VRF instance, and the third RF signal being generated based on the third data packet.
5. 5. The system of claim 1, further comprising: a radio frequency equipment (RFE) configured to transmit a third RF signal, the third RF signal being based on a third data packet received at the first modem from the network device, the third data packet including the first VRF instance identifier.
6. 6. The system of claim 5, further comprising: switching circuitry configured to generate a plurality of sets of RF signals, each set of RF signals associated with a corresponding portion of an RF spectrum, the plurality of sets of RF signals including at least one RF signal associated with a particular portion of the RF spectrum associated with a user group and service.
7. 7. The system of claim 6, further comprising a cellular system configured to deploy multiple sets of the RF signals in an overlapping pattern at a first location, the particular portion of the RF spectrum being accessible by devices at the first location associated with the user group and the service and inaccessible by devices not associated with the user group and the service.
8. The system of claim 7 , wherein the cellular system comprises a satellite-based cellular system or a terrestrial-based cellular system.
9. 7. The system of claim 6, wherein the user group includes a first mobile virtual network operator (MVNO), and the plurality of modems and the network device are configured to logically separate traffic associated with the first MVNO and the service from traffic associated with a second MVNO and another service.
10. 10. The system of claim 1, wherein the plurality of modem pools are associated with a plurality of VRF instance identifiers, each modem of the plurality of modem pools being configured to process traffic associated with a corresponding VRF instance identifier, the corresponding VRF instance identifier being associated with a service, a user group, or both.
11. 11. The system of claim 1, wherein the first modem is further configured to encrypt the first data packets based on a first encryption associated with the first VRF instance, and the second modem is further configured to encrypt the second data packets based on a second encryption associated with the second VRF instance.
12. A method implemented by a system according to any one of claims 1 to 11, comprising the steps of: receiving a first data packet from a first modem in a first modem pool at a network device, the first data packet including first data and a first virtual routing and forwarding (VRF) instance identifier; transmitting a first packet from the network device to a first device over a network, the first packet including the first data and a first header including a first indicator, the first indicator being associated with a first VRF instance, the first VRF instance identifier being associated with a first service and a first user group; receiving, at the network device, a second data packet from a second modem of a second modem pool, the second data packet including second data and a second VRF instance identifier; transmitting a second packet from the network device to a second device over the network, the second packet including the second data and a second header including a second indicator, the second indicator being associated with a second VRF instance, the second VRF instance identifier being associated with a second service and a second user group. method.
13. generating first routing information base (RIB) data associated with the first VRF instance based on the first data packet; 13. The method of claim 12, further comprising: generating second RIB data associated with the second VRF instance based on the second data packet.
14. 13. The method of claim 12, further comprising: logically separating the data associated with the second VRF instance from the data associated with the first VRF instance by encapsulating the data associated with the first VRF instance using a different header than the data associated with the second VRF instance.
15. updating first subscriber information associated with the first VRF instance based on the first packet; 13. The method of claim 12, further comprising: updating second subscriber information associated with the second VRF instance based on the second packet.
Citation Information
Patent Citations
Network communication system
JP2014146950A
System and method for federated network traffic processing
JP2018201192A
Satellite Diversity
US20170215190A1
Interference mitigation for a satellite network
US20170353871A1
System and method for configuring a switch matrix on-board a vehicle based on network information
US20190058672A1
