Content delivery using 5g multicast services with satellite connectivity

Abstract

In view of the foregoing, delivery of content is ensured across a satellite communications system. At a satellite gateway content is received from a core data network. A translation network of the satellite gateway maintains functionality between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and the core data network coupled to the satellite gateway at a translation layer of the translation network.

Description

Docket: GMU-24-037CONTENT DELIVERY USING 5G AND FUTURE-GENERATION MULTICAST SERVICES WITH NON-3GPP ACCESS AND SATELLITE CONNECTIVITYRELATED APPLICATIONS

[0001] This application claims the benefit of provisional application serial number 63 / 727,486 filed December 3, 2024, titled “Content Delivery Using 5G Multicast Services with Non-3GPP Access and Satellite Connectivity,” the entire content of which is hereby incorporated by reference.BACKGROUND

[0002] For 5G Non-Terrestrial Networks (NTNs), it is clear that the current 3rdGeneration Partnership Project (3GPP)-specified approach, relying on cellular-derived NTN bands and Device-to-Device (D2D) techniques, significantly degrades the link budget and drives high deployment costs for new hardware both on the ground and in space. This current approach imposes severe bandwidth limitations and prevents the delivery of true high-bandwidth services to residential customers.

[0003] To close this critical gap, there is a need for a low-cost solution that allows satellite and internet service providers to provide scalable, high-performance connectivity in a highly cost-effective manner.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The accompanying drawings provide visual representations which will be used to describe various representative embodiments more fully and can be used by those skilled in the art to understand better the representative embodiments disclosed and their inherent advantages. In these drawings, like reference numerals identify corresponding or analogous elements.

[0005] FIG.1 illustrates a 5G Non-Terrestrial Network (NTN) implementation in which New Radio 5G Satellite Access is shown, in accordance with embodiments of the present disclosure.

[0006] FIG. 2 illustrates network architecture for Multicast and Broadcast Services (MBS) user services delivery and control, in accordance with embodiments of the present disclosure.Docket: GMU-24-037

[0007] FIG. 3 illustrates Trusted non-3GPP architecture, in accordance with embodiments of the present disclosure.

[0008] FIG. 4 illustrates Untrusted non-3GPP architecture, in accordance with embodiments of the present disclosure.

[0009] FIG. 5 illustrates data and content delivery using legacy satellite ground station equipment, in accordance with embodiments of the present disclosure.

[0010] FIG. 6 illustrates a block diagram of a satellite network system with a 5G or a Future-G core, in accordance with embodiments of the present disclosure.

[0011] FIG. 7 illustrates a block diagram of an example satellite network system with a 5G core, in accordance with embodiments of the present disclosure.

[0012] FIG. 8 depicts protocol stacks of a user plane for a TNAN, in accordance with embodiments of the present disclosure.

[0013] FIG. 9 illustrates protocol stacks of a control plan for the TNAN, in accordance with embodiments of the present disclosure.

[0014] FIG. 10 illustrates the User plane N3IWF protocol stack after security association establishment in accordance with embodiments of the present disclosure.

[0015] FIG. 11 illustrates the Control plane N3IWF protocol stack after security association establishment, in accordance with embodiments of the present disclosure.

[0016] FIG. 12 illustrates an example TNAN message flow 1200 that may be used in accordance with embodiments of the present disclosure.

[0017] FIG. 13 illustrates an example workflow diagram of an example simulation, employing a Wi-Fi access technology as a proxy for the satellite ground station, in accordance with embodiments of the present disclosure.

[0018] FIG. 14 provides an overview of a method for ensuring delivery of content across a satellite communications system, in accordance with embodiments of the present disclosure.DETAILED DESCRIPTION

[0019] In accordance with the various embodiments presented in the disclosure, various features of a novel satellite gateway, system and method ensure deliver of media content to actual users, not bots, in a satellite based communications network such as the Internet.

[0020] During research on 5G Non-Terrestrial Networks (NTN), it became clear that the current 3GPP-specified approach, relying on cellular-derived NTN bands (e.g., n254, n255, n256, n510, n511, n512) and Device-to-Device (D2D) techniques, significantly degrades the link budget and drives high deployment costs for new hardware both on the ground and inDocket: GMU-24-037 space. This path imposes severe bandwidth limitations and prevents the delivery of true high- bandwidth services to residential customers.

[0021] To close this critical gap, presented herein is a low-cost, innovative solution that fully unlocks the flexibility of a cloud-based 5G and / or Future-G core network. The innovative approach effectively future-proofs satellite and internet service providers, enabling scalable, high-performance connectivity in a highly cost-effective manner.

[0022] Therefore, in accordance with various embodiments of the disclosure, a satellite gateway includes a ground station, also referred to as a satellite ground station, that is operable to connect to a satellite and a translation network coupled to the ground station. The translation network is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway that is operable to transmit content to the satellite via the satellite gateway, the translation layer operable to maintain functionality across an interface between the core data network and a residential gateway via the satellite.

[0023] In accordance with various embodiments of the disclosure, a satellite communications system includes a residential gateway and a satellite gateway coupled to a satellite. The satellite gateway includes a ground station that is operable to connect to the satellite and a translation network coupled to the ground station that is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway that is operable to transmit content to the satellite via the satellite gateway. The translation layer is operable to maintain functionality across an interface between the core data network and the residential gateway via the satellite. The residential gateway is coupled to and in communication with the satellite gateway and having one or more end-user devices each having a receiver, the receivers of the one or more end-user devices operable to receive from the satellite gateway content transmitted by the content provider over the core data network to the satellite gateway.

[0024] Further, in accordance with various embodiments of the disclosure a method of ensuring delivery of content across a satellite communications system is provided. The method includes at a satellite gateway: receiving content from a core data network and a translation network of the satellite gateway maintaining functionality between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway at a translation layer of the translation network.Docket: GMU-24-037

[0025] An objective of the embodiments of the disclosure is to enable existing satellite television and internet service providers to leverage the 5G and future-generation telecommunications (Future-G) network for service delivery while utilizing existing satellite infrastructure. This approach offers a highly cost-effective and efficient means to future-proof their services with minimal capital expenditure and the potential to reduce operational costs. These embodiments allow for data rates that are high enough to provide streaming TV services to an end device and may also provide cost savings to satellite TV providers while employing the security and flexibility of the 5G and Future-G networks. The growing proliferation of the standalone 5G and future-G Service-Based Architecture provides a ready - to-commercialize platform that enables satellite and Internet service providers to leverage its flexible architecture, reduced deployment costs, and expanded use cases.

[0026] The 5G standards provide different possibilities for an access network to connect to the 5G core network. Before discussing a use case for providing programing services to a user using a traditional satellite infrastructure and 5G or Future-G multicast and Broadcast services, different non-3GPP access types and the non-terrestrial satellite services within 3 GPP are reviewed.

[0027] When 5G non-terrestrial access is discussed, many consider a use case for nonterrestrial networks that are used to extend the cellular network - essentially a bent pipe in the sky. This network can also place the RAN DU (Radio Access Network Distributed Unit) in the satellite. Significantly, this uses 5G New Radio. Reference is made to FIG. 1 that illustrates an example conventional 5G Non-Terrestrial Network (NTN) implementation, in which New Radio 5G Satellite Access is shown.

[0028] New Radio and the spectrum that is used introduces bandwidth limitations due to the link budget from a grounds station to a satellite. 3GPP TR 38.821 section 6.1.3 has an analysis of the link budget and how it is calculated.

[0029] Regardless of the link budget, data rates, etc. from a ground station to a satellite, the detailed description in the specs anticipate that the connectivity is a full 3GPP compliant connection through what is essentially an 0-RAN (Open Radio Access Network) Distributive Unit (DU), basically an extension of the cellular network.

[0030] As with a terrestrial cellular use case for 5G New Radio, the N1 interface is fully encrypted and therefore should be viewed in the same light as a terrestrial connection.

[0031] The NTN implementation enables Direct-to-Device (D2D) communication via satellite from a ground gateway or station to the handset or other User Equipment (UE) using the 5G New Radio (NR) physical layer in Frequency Range 1 (FR1) bands n254, n255, andDocket: GMU-24-037 n256 (all sub-6 GHz). These bands are deliberately chosen for their favorable propagation characteristics, but the extreme path loss inherent in satellite-to-handset links still restricts initial services to low-data-rate applications such as SMS / MMS text messaging and, in some cases, narrowband voice calls. A primary objective is to simply extend cellular coverage to remote or rural areas where deploying traditional terrestrial infrastructure is not economically viable. The ground station or gateway communications with the satellite via a 5G NR Link and the satellite in turn communications also via a 5G NR links with handsets or other UE. The ground station also communications with the 5G Radio Access Network (RAN) Distributed Unit (DU) and Central Unit (CU), which is turn is in communication with the 5G Core Network (CN) and Data Network (DN) as shown.

[0032] The deployment of the option 2 standalone 5G Service Based Architecture introduces great flexibility in architecture and potential use cases. One of the significant advantages is that 5G can now accept access technologies that are both 3GPP and non-3GPP compliant. The non-3GPP compliant access technologies are further split into untrusted and trusted access.

[0033] 3GPP and network providers are also looking very closely at non-terrestrial access networks. The current discussions are based around 3GPP Technical Reports (TR’s) and may feature extensions of the 5G cellular footprint. However, the scope of Non-Terrestrial Networks in 5G can be greatly expanded if non-3GPP access technologies are included. Accordingly, the embodiments herein describe an architecture(s) that may provide broadband satellite connectivity and TV services to the home using Multicast-Broadcast 5G and Future- G services and a non-3GPP satellite access network.

[0034] Using building blocks from 3GPP suggests an architecture that will provide broadband satellite connectivity and TV services to the home or residents using Multicast- Broadcast 5G services and a non-3GPP satellite access network.

[0035] The 5G Service Based Architecture is extremely flexible and can be constructed into whatever is required to fulfill a particular use case. One particular use case is that of Broadcast / Multicast Services (BMS) delivery of services such as TV broadcasting to either a large base of users as is the case with Broadcast, or a select number of users as is the case with multicast. Discussions for MBMS may center around the use of New Radio for the connection for network from the network. The 3 GPP Specifications allow for Multicast and Broadcast Services (MBS) to be delivered to an end point device or User Equipment (UE). As discussed above, these services are sent over the Air Interface via a Next Generation (NG) Radio such as 5G New Radio. See the network architecture for MBS user services deliveryDocket: GMU-24-037 and control (3GPP TS 23.247 4 / 2 / 1) in FIG. 2 in which multicast / broadcast support in 3GPP is illustrated.

[0036] 3 GPP specifications support both trusted and untrusted non-3GPP access architectures. 3GPP 23.501 section 4 reviews non-3GPP Access to the 5G core network in greater detail, but for high-level reference consider the following. There are two fundamental variants for accessing the 5G core network. These are Untrusted non-3GPP access and Trusted non-3GPP access. A use case for Multicast-Broadcast Services (MBS) over legacy satellite networks may use a Trusted non-3GPP access. This will allow for control plane procedures to be performed over the N1 interface.

[0037] FIG. 3 shows the trusted non-3GPP access architecture, in which the Trusted Non- 3 GPP Access Network (TNAN) includes a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF), analogous to the Wireline 5G Access Network (W-5GAN) and Wireline Access Gateway Function (W-AGF) defined in Broadband Forum TR-470, for example. For more details refer to 3GPP TS 23.501 Section 4.

[0038] The untrusted non-3GPP access technology is connected to the 5G Core via a Non- 3GPP Interworking Function (N3IWF). The N3IWF is a part of the 5G Service based architecture and supports connectivity over the N2 interface for the control plane Access and Mobility Function (AMF) and to the user plane, i.e. User Plane Function (UPC) over the N3 interface as shown in FIG. 4. The UPF and the AMF are in communication with the Session Management Function (SMF), as also shown in FIG. 7. Non-3GPP untrusted access is further discussed in 3GPP TS 23.501 Section 4.2.8.

[0039] The architecture described in FIG. 2 shows content delivery using the 5G RAN. This use case works well for delivery to a hand-held device. However, it is not sufficient if a legacy satellite TV provider wishes to use a 5G Core Network with Multimedia Broadcast Multicast Service (MBMS) capability to deliver content to a residence using a legacy satellite network, for example.

[0040] FIG. 5 illustrates a novel method and system of data and content delivery using legacy satellite ground station equipment. In the block and flow diagram 500, the satellite gateway 520 has a ground station such as a satellite ground station that connects to a satellite and a translation network 530 coupled to the ground station. The translation network 530 is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network 540 coupled to the satellite gateway 520 that is operable to transmit content to the satellite via the satellite gateway 520. The core data network 540 may be 5G or Future-G, as described herein. TheDocket: GMU-24-037 translation layer 530 is operable to maintain functionality across an interface between the core data network 540 and a residential gateway 510 via the satellite. As described above, the translation network has a translation layer between the legacy satellite lower layers and the core network 540. In certain embodiments, the TNAN acts as the translation layer and includes the TNAP and the TNGF.

[0041] In accordance with the various embodiments presented herein, the block diagram 600 of a satellite network system in FIG. 6 illustrates the utilization of a 5G / Future-G core network 650 to facilitate the delivery of high data-rate services from an Application Function (AF) 660 such as a media content provider or Internet Service Provider (ISP) to end users of the residential gateway 610 through a legacy satellite distribution system via satellite gateway 640. Examples of such satellite services include DStv (Africa), Tata Play (South Asia), CCTV / ChinaSat (China), and Free-to-Air (FTA) platforms.

[0042] This approach enables data rates sufficient to support streaming television services to end-user devices 615, such as a 5G Residential Gateway (5G-RG) 610 or a satellite television receiver 615 connected to the user’s television set. By leveraging the security and flexibility of 5G / Future-G networks, the methods and structure presented herein provide substantial cost efficiencies for satellite television service providers, while facilitating seamless onboarding of new applications and content delivery entities. This same approach can be used to deliver Broadband Data from an Internet Service Provider. Further, existing satellite and supporting infrastructure that includes the satellite and the satellite Radio Access Network (Ground Station) are used. This significantly reduces cost and ease of deployment.

[0043] Accordingly, the embodiments of the disclosure introduce a novel TNAN implementation integrated within a satellite gateway that retains the legacy satellite uplink / downlink physical and lower-layer protocols while exposing a TNGF toward the 5G or Future-G core. This enables the 5G / Future-G core network to perform standard Nl- interface NAS-layer authentication, security, and session management procedures, thereby allowing legacy satellite terminals to deliver broadcast TV, multicast streaming, or residential broadband services under full 5G or Future-G core control without requiring IPSec tunneling or replacement of existing satellite infrastructure.

[0044] This combination of 5G MBMS architecture with 5G Trusted Non-3GPP Access technology (TNAN) is illustrated in block diagram 700 of a satellite communication system having a 5G core in FIG. 7, which shows an example configuration for 5G Broadcast services using satellite connectivity. A residential gateway 710 having a 5G-RG with an End Point Device(s) (UEs) 715 and a domestic (residential) satellite receiver 720 is illustrated.Docket: GMU-24-037Both the residential gateway 710 and the satellite gateway 740 are in communication with satellite 730 as shown. The translation network 745 provides a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite 730 and a 5G core data network 770 coupled to the satellite gateway 740 that is operable to transmit content to the satellite 730 via the satellite gateway 740. The translation layer of 745 is operable to maintain functionality across an interface between the core data network 770 and the residential gateway 710 via the satellite 730 to deliver broadcast TV, multicast streaming, or residential broadband services (content from content provider 780) under full 5G or Future-G core control.

[0045] It can be seen that it is possible to use a high data rate Satellite connection Physical and Radio Recourse Layer with a 5G N1 Interface (TNAP). This allows the 5G MBMS network to provide all of the features, including 5G and Future-G network features and security procedures, while using a legacy satellite to deliver the service and content from content provider 780. This architecture also allows considerable cost savings, for both the satellite TV provider (780) and for the consumer (at 710). Software updates on the satellite 730 transponder and on the consumer equipment of the residential gateway 710 are performed as needed to enable the support of the 5GN1 Interfaces and to enable Multi cast / B roadcast Service (MBS) for efficient content deliver and ISP services. Such software updates may include updates for MBS within the 3GPP specification.

[0046] The Ta interface between TNAP and TNGF may not be specified as per 3 GPP Technical Specification (TS) 23.501, release 18 section 4.2.8.3.2. Some requirements may be drawn with reference to 3GPP TS 23.502 section 4.12a.2.2, Figure 4.12a.2.2-l : Registration via trusted non-3GPP access. With regard to the description below of the Ta interface, actions described may make reference to the numbered steps or actions illustrated in the Ta interface between TNAP and TNGF as per 3GPP Technical Specification (TS) 23.501, release 18 section 4.2.8.3.2. As described herein, L2 denotes a message may be encapsulated in the L2 message, not that it may be an L2 message.

[0047] Requirements on the Ta interface between the TNAN 750 and TNGF 760

[0048] The Ta interface may be able to carry extensible authentication protocol 5G (EAP- 5G) traffic and user location information before the NWt connection may be established between the user equipment (UE) 715 and the TNGF 760. The Ta interface allows the UE and the TNGF 760 to exchange IP traffic.

[0049] In deployments where the TNAP 750 does not allocate the local IP addresses to UE(s) 715, the Ta interface may be able to allow the UE 715 to request and receive IPDocket: GMU-24-037 configuration from the TNAN 740 (including a local IP address), e.g. with Dynamic Host Configuration Protocol (DHCP). This may allow the UE 715 to use an IP stack to establish a NWt connection between the UE 715 and the TNGF 760.

[0050] The "local IP address" may be the IP address that allows the UE 715 to contact the TNGF 760; the entity providing this local IP address may be part of TNAN 740 and out of 3 GPP scope.

[0051] Procedures Related to the TNAP-TNGF

[0052] Although the procedures for the Ta interface have not yet been specified, some of the NAS messages that transit that interface are observed to ascertain what kind of information may be carried.

[0053] An EAP procedure may be initiated. EAP messages may be encapsulated into layer-2 packets, e.g. to be compliant with wireless standards developed by the Institute of Electrical and Electronics Engineers (IEEE) IEEE 802.3 / 802. lx packets, intoIEEE 802.11 / 802. lx packets, into Point-to-Point Protocol (PPP) packets, etc. The Network Access Identifier (NAI) provided by the UE not operating in Stand-Alone Non-Public Network (SNPN) access mode for Yt interface indicates that the UE requests "5G connectivity" to a specific Public Land Mobile Network (PLMN). In the case of Wireless Local Area Network (WLAN) access, if the UE has a MBMS subscription, the UE may also include an indication of its MPS subscription in the username part of the NAI as per TS 23.003. The NAI provided by the UE operating in SNPN access mode for Yt interface indicates that the UE request "5G connectivity" to a specific SNPN. If the Wireless Local Area Network Selection Policy (WLANSP) rule contains information including TNGF ID to use for specific slices and the UE supports such information, the UE builds the realm of NAI taking the TNGF ID into account. This NAI triggers the TNAP 750 to send an Authentication, Authorization, and Accounting (AAA) request to a TNGF 760, which operates as an AAA proxy. Between the TNAP 750 and TNGF 760 the EAP packets are encapsulated into AAA messages. The AAA request may also include the TNAP identifier, which may be treated as the User Location Information defined in clause 5.6.2 of Technical Specification (TS) Document from the 3rdGeneration Partnership Project, TS 23.501. In order to support usage of the TNAP identifier defined in TS 23.316, when a 5G Residential Gateway (5G-RG) acts as a TNAP, the W-5GAN may, as defined in clause 5.6.2 of TS 23.501, provide the 5G RG civic address information in the TNAP identifier.

[0054] An EAP-5G procedure may be executed as the one for the untrusted non-3GPP access with the following modifications. The registration request may contain an indicationDocket: GMU-24-037 that the UE supports TNGF selection based on the slices the UE wishes to use over trusted non-3GPP access (i.e., that the UE supports Extended WLANSP rule).

[0055] A TNGF key, instead of a Non-3GPP Interworking Function (N3IWF) key, may be created in the UE and in the Access and Mobility Management Function (AMF) of core network 770 after the successful authentication. The TNGF key may be transferred from the AMF of core network 770 to TNGF 760 within the N2 Initial Context Setup Request. The TNGF 760 derives a TNAP key, which may be provided to the TNAP 750. The TNAP key depends on the non-3GPP access technology (e.g. it may be a Pairwise Master Key in the case of IEEE Std 802.11). How these security keys are created may be specified in TS 33.501.

[0056] The UE may include the requested Network Slice selection Assistance Information (NSSAI) identifier in the Access Network (AN) parameters if allowed, according to the conditions defined in clause 5.15.9 of TS 23.501, for the trusted non-3GPP access. The UE may also include a UE ID in the AN parameter, e.g. a 5G-Globally Unique Temporary Identity (5G-GUTI) if available from a prior registration to the same PLMN or SNPN. If the UE in SNPN access mode for Yt interface performs the Registration procedure for UE onboarding, the UE may include an indication in the AN parameter that the connection request may be for onboarding.

[0057] In the N2 message, the TNGF 760 may include a UE Location Information (ULI) including the TNAP ID and the UE IP address based on information received. If the ULI includes the IP address, this may be set to a "null" IP address (e.g. 0.0.0.0) because the UE may not yet be assigned an IP address. If the TNGF 760 has received the TNAP ID over the Ta interface, the TNGF includes the TNAP ID within UE Location ULI sent to AMF. After the UE may be assigned an IP address, the TNGF includes this address in subsequent N2 messages. This N2 message also includes the Selected PLMN ID and optionally the Selected Network Interface Device (NID) and the Establishment cause. The Selected NID may be present when the UE connects to an SNPN via Trusted non-3GPP access.

[0058] If the UE in SNPN access mode for Yt interface performs the registration procedure for UE onboarding, the interaction between Access Mobility Function (AMF) and Authentication Server Function (AUSF), as per 3GPP TS 23.502 action 8a and action 8c in Figure 4.12a.2.2-l, may be replaced, depending on the 5GC architecture that may be used for UE onboarding.

[0059] After receiving the TNGF key from AMF, the TNGF 760 may send to UE an EAP- Request / 5G-Notification packet containing the "TNGF Contact Info", which includes the IPDocket: GMU-24-037 address of TNGF. After receiving an EAP-Response / 5G-Notification packet from the UE, the TNGF 760 may send a message containing the EAP-Success packet.

[0060] The UE may receive IP configuration from the TNAN, e.g. with DHCP. The UE may have successfully connected to the TNAN and have obtained an IP configuration. The UE may set-up a secure NWt connection with the TNGF 760 as follows. The UE initiates an Internet Key Exchange Initialization (IKE INIT) exchange using the Internet Protocol (IP) address of TNGF 760 received during the EAP-5G signaling. Subsequently, the UE initiates an IKE AUTH exchange and provides its identity. The identity provided by the UE in the IKEv2 signaling may be the same as the UE ID included in the AN parameter. This enables the TNGF 760 to locate the TNGF key that was created before for this UE, during the authentication. The TNGF key may be used for mutual authentication. NULL encryption may be negotiated between the UE 715 and the TNGF 760.

[0061] The TNGF 760 provides to UE (a) an "inner" IP address, (b) a NAS IP ADDRESS and a TCP port number and (c) a DSCP value. After this action, an Internet Protocol Security (IPsec) Security Association (SA) may be established between the UE 715 and TNGF 760. This may be referred to as the "signaling IPsec SA" and operates in Tunnel mode. Operation in Tunnel mode enables the use of Mobile Internet Key Exchange (MOB IKE) for reestablishing the IPsec SAs when the IP address of the UE changes during mobility events. All IP packets exchanged between the UE 715 and TNGF 760 via the "signaling IPsec SA" may be marked with the above DSCP value. The UE 715 and the TNAP 750 may map the DSCP value to a Quality of Service (QoS) level (e.g. to an Enhanced Distributed Channel Access (EDCA) Class) supported by the underlying non-3GPP Access Network. The mapping of a DSCP value to a QoS level of the non-3GPP Access Network may be outside the scope of 3 GPP.

[0062] Right after the establishment of the "signaling IPsec SA", the UE may setup a TCP connection with the TNGF 760 by using the NAS IP ADDRESS and the TCP port number received. The UE may send NAS messages within TCP / IP packets with source address the "inner" IP address of the UE and destination address the NAS IP ADDRESS. The TNGF 760 may send NAS messages within TCP / IP packets with source address the NAS IP ADDRESS and destination address the "inner" IP address of the UE.

[0063] This concludes the setup of the NWt connection between the UE and the TNGF 760. Subsequent NAS messages between UE and TNGF are carried over this NWt connection (i.e. encapsulated in TCP / IP / ESP).Docket: GMU-24-037

[0064] The NAS Registration Accept message may be sent by the AMF and may be forwarded to UE via the established NWt connection. Now the UE can use the TNAN (a) to transfer non-seamless offload traffic and (b) to establish one or more Protocol Data Unit (PDU) Sessions.

[0065] The AMF sends via the TNGF 760 a UE Registration Reject indicating that the selected TNGF was not appropriate for the requested slices that the UE may be allowed to access to. The AMF may provide target TNAN information (SSID, TNGF ID) to the UE within the Registration Reject message indicating the UE to build the NAI based on the TNGF ID.

[0066] The AMF may determine a target TNGF that supports the subset of the requested Network Slice Selection Assistance Information (NSSAI) that may be allowed by the subscribed single NSSAIs (S-NSSAIs) based on the list of supported TAs and the corresponding list of supported slices for the TA obtained in N2 interface management procedures as specified in TS 38.413 and considering UE location.

[0067] The user domain model may give an indication of the functionality for the end point device to enable this functionality. This end point device may be anything including a home satellite receiver 720, a vehicle, or any end point device 715 that has the antenna capable of connecting to the satellite 730.

[0068] As previously mentioned, it is also possible to use untrusted Non-3GPP functionality by using a Non-3GPP Interworking Function (N3IWF). However, this may be less desirable because it then requires IP SEC tunneling at the upper layers for security purposes, hence the latency will increase considerably.

[0069] From an Open Systems Interconnection (OSI) stack perspective this can be seen as retaining the legacy lower layers, such as the Layer 1 (LI) Physical Layer and the Layer 2 (L2) Data Link Layer (DLL), from the ground station to the satellite. LI of the stack is the Physical Layer that provides physical connection between devices and transmits individual bits from one node (device) to the next node and controls bit synchronization, bit rate control, arrangement of devices / nodes in a network (physical topology), and transmission modes between two connected devices. Examples of LI devices include modems, cables, hubs, and repeaters. L2 is the DLL that ensures node-to-node error-free data transfer in delivery of messages across the LI Physical Layer. These lower layers are very likely to be proprietary in nature as well as using the existing Radio Frequency (RF) Physical Layer. This results in no or very little change to the satellite which significantly reduces implementation costs. From the upper layers of the OSI stack the 5G / Future-GNAS and application layerDocket: GMU-24-037 messaging such as Authentication and Security remain as standard 3 GPP procedures as described in the 3 GPP specifications. The uplink and downlink protocol stacks are described in the 3 GPP specifications.

[0070] FIGs. 8 and 9 illustrate the TNAN protocol stack for the trusted Non-3GPP functionality and architecture while FIGs. 10 and 11 illustrate the N3IWF protocol stacks for the untrusted Non-3GPP functionality and architecture. More specifically, FIG. 8 illustrates the protocol stacks of the User plane for the TNAN (satellite access network) and FIG. 9 illustrates the protocol stacks of the Control plane for the TNAN (satellite access network). FIG. 10 illustrates the User plane N3IWF protocol stack after security association establishment while FIG. 11 illustrates the Control plane N3IWF protocol stack after security association establishment.

[0071] As described above, the translation network has a translation layer between the legacy satellite lower layers (L2, LI) and the core network 540. In certain embodiments, the TNAN acts as the translation layer and includes the TNAP and the TNGF. Use of the TNAN may be preferred over the N3IWF because it eliminates the need for IPSec tunneling, thereby considerably reducing latency while preserving full 5G / Future-G functionality across the N1 interface.

[0072] Referring now to FIG. 12, an example TNAN message flow 1200 that may be used in the satellite gateway, system and method embodiments described herein. It is noted that the Layer 2 (L2) messages depicted in the drawing are TNAN message flows derived from (TNAN) scenarios defined in the 3 GPP specifications. These illustrative examples do not necessarily reflect or limit an exact L2 protocol implementation of this disclosure. Accordingly, the disclosures herein are accordingly designed to be flexible and agnostic to the specific L2 and Physical layer protocols employed on the potentially proprietary air interface between the ground station of the satellite gateway and the satellite. This approach enables a variety of L2 and Physical layer implementations, whether standardized, vendorspecific, or fully proprietary, while maintaining interoperability at the N 1 NAS and higher layers ensuring compliance with 3GPP and 5G / Future-G.

[0073] FIG. 13 illustrates a MATLAB workflow diagram illustrating an example simulation successfully conducted, in which a Wi-Fi access technology was employed as a proxy for the satellite ground station. This approach enabled the validation of key system parameters and performance metrics in a controlled, cost-effective environment. The simulation architecture, signal processing chain, and performance evaluation methodology.Docket: GMU-24-037

[0074] More particularly, in an example simulation of 5G multicast services, testing included an iperf server running in a 5G core and with N3IWUE requesting 5G running multicast service. For simplicity of development, N3IW and UE are in the same virtual instance and the 5G core is another virtual instance. It was seen that it is possible to use a high data rate satellite connection physical and radio recourse layer with a 5G N1 interface (TNAP). This allows the 5G MBMS network to provide features while using a legacy satellite to deliver the service. The command iperf -s -B 239.10.20.30 -u -T 4 -i 1 is used to set up an iperf server in 5G core server, with the breakdown of this command including, for example:• iperf: The command-line tool for network performance measurement.• -s: This -s option tells iperf to run in server mode, listening for incoming connections.• -B 239.10.20.30: The -B option binds the server to the specified IP address, in this case, 239.10.20.30, which is a multicast address. By binding to this address, the server can receive multicast traffic sent to this IP.• -u: This option tells iperf to use UDP (User Datagram Protocol) instead of the default TCP. Multicast traffic is typically used with UDP, as TCP does not support multicast.• -T 4: The -T option sets a “title” for the connection. This is helpful for distinguishing between multiple iperf sessions in the output.• -i 1 : This option sets the interval for reporting statistics to 1 second, meaning the server will display network performance statistics every second.In brief, this command sets up an iperf server on the multicast address 239.10.20.30, listening for UDP traffic, with a reporting interval of 1 second.

[0075] Similarly, the snap of the N3IWUE is next considered. The route to the multicast server (239.10.20.30) is through the gretune-id-2 and also the default gateway is through the same interface. The command iperf -c 239.10.20.30 -u -T 4 -t 200 -i 1 is used to run an iperf client with specific options to test network performance, including, for example:• iperf: The command-line tool for measuring network bandwidth.• -c 239.10.20.30: This option specifies that iperf should run in client mode, sending data to the IP address 239.10.20.30, which is a multicast address.• -u: This option tells iperf to use UDP instead of the default TCP, which is necessary for multicast traffic.Docket: GMU-24-037• -T 4: The -T option sets a title or "tag" for this session, with the identifier 4, which can help distinguish it from other sessions in the output.• -t 200: This option sets the test duration to 200 seconds, meaning the client will continue sending data to the multicast address for 200 seconds.• -i 1 : This sets the reporting interval to 1 second, so iperf will report performance statistics every second.In summary, this command starts an iperf client that sends UDP traffic to the multicast address 239.10.20.30 for 200 seconds, with a reporting interval of 1 second.

[0076] Referring now to FIG. 14, flowchart 1400 provides an overview of a method for ensuring delivery of content across a satellite communications system. At block 1410, content from a core data network is received at a satellite gateway, described above. At block 1420, a translation network of the satellite gateway maintains functionality between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway at a translation layer of the translation network.

[0077] While this present disclosure is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail specific embodiments, with the understanding that the embodiments shown and described herein should be considered as providing examples of the principles of the present disclosure and are not intended to limit the present disclosure to the specific embodiments shown and described. In the description below, like reference numerals are used to describe the same, similar or corresponding parts in the several views of the drawings. For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

[0078] As recited in this disclosure, various embodiments described herein provide a novel satellite gateway, system and method to ensure deliver of media content to actual users, not bots, in a communications network such as the Internet.

[0079] The following embodiments are combinable.

[0080] Therefore, in one embodiment of the disclosure, a satellite gateway includes a ground station, also referred to as a satellite ground station, that is operable to connect to a satellite and a translation network coupled to the ground station. The translation network is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway that is operable to transmit content to the satellite via the satellite gateway, theDocket: GMU-24-037 translation layer operable to maintain functionality across an interface between the core data network and a residential gateway via the satellite.

[0081] In another embodiment of the satellite gateway, the translation layer retains uplink and downlink protocols of the one or more lower layers of the OSI stack of the satellite and provides compatibility with the core data network coupled to the satellite gateway.

[0082] In another embodiment of the satellite gateway, the one or more lower layers of the OSI stack are at least one or more Layer 2 (L2) data link layers (DLL) of the OSI stack.

[0083] In another embodiment of the satellite gateway, the translation network of the satellite gateway is a trusted access network including a trusted access point and a trusted gateway function.

[0084] In another embodiment of the satellite gateway, the translation network is a Trusted Non-3GPP Access Network (TNAN) including a Trusted Non-3PP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF) and where the translation network is operable to maintain 5G / FutureG functionality across a Nl interface between a 5G / FutureG core data network and user equipment of the residential gateway via the satellite.

[0085] In another embodiment of the satellite gateway, the translation network of the satellite gateway is a non-trusted access network including an untrusted access point and a Non-3GPP Interworking Function (N3IWF).

[0086] In another embodiment of the satellite gateway, the ground station includes the translation network.

[0087] In another embodiment of the satellite gateway, the translation layer operable to maintain functionality across the interface between the core data network and user equipment of the residential gateway via the satellite.

[0088] In another embodiment of the satellite gateway, the content transmitted from the core data network to the satellite via the satellite gateway is Multicast / Broadcast Services (MBS).

[0089] In another embodiment of the satellite gateway, the MBS includes one or more of satellite television including broadcast TV, multicast streaming, residential broadband, internet service, cellular services, texting services, and voice calls from an Application Function (AF).

[0090] In another embodiment of the satellite gateway, the AF is one or more of a media content provider, an Internet Service Provider (ISP), and a satellite service.

[0091] Therefore, in one embodiment of the disclosure, a satellite communications system includes a residential gateway and a satellite gateway coupled to a satellite, the satelliteDocket: GMU-24-037 gateway includes a ground station that is operable to connect to the satellite and a translation network coupled to the ground station that is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway that is operable to transmit content to the satellite via the satellite gateway, with the translation layer operable to maintain functionality across an interface between the core data network and the residential gateway via the satellite and the residential gateway coupled to and in communication with the satellite gateway and having one or more end-user devices each having a receiver, the receivers of the one or more end-user devices operable to receive from the satellite gateway content transmitted by the content provider over the core data network to the satellite gateway.

[0092] In another embodiment of the system, an end-user device of the one or more enduser devices may be one or more of a hand-held device, a handset, television receiver.

[0093] In another embodiment of the system, further including the core data network coupled to and in communication with the satellite gateway.

[0094] In another embodiment of the system, further including the content provider coupled to and in communication with the core data network and having a transmitter operable to transmit content over the core data network and the satellite gateway to the residential gateway.

[0095] In another embodiment of the system, the content transmitted from the core data network to the satellite via the satellite gateway is Multi cast / B roadcast Services (MBS).

[0096] In another embodiment of the system, the MBS includes one or more of satellite television including broadcast TV, multicast streaming, residential broadband, internet service, cellular services, texting services, and voice calls from an Application Function (AF). In another embodiment of the system, the AF is one or more of a media content provider, an Internet Service Provider (ISP), and a satellite service.

[0097] In one embodiment of the disclosure, a method of ensuring delivery of content across a satellite communications system is provided. The method includes at a satellite gateway: receiving content from a core data network and a translation network of the satellite gateway maintaining functionality between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway at a translation layer of the translation network.

[0098] In another embodiment of the method, the translation layer maintaining functionality across an interface between the core data network and a residential gateway via the satellite.Docket: GMU-24-037

[0099] In another embodiment of the method, further including the translation layer retaining uplink and downlink protocols of the one or more lower layers of the OSI stack of the satellite and providing compatibility with the core data network coupled to the satellite gateway.

[0100] In another embodiment of the method, the one or more lower layers of the OSI stack are at least one or more Layer 2 (L2) data link layers (DLL) of the OSI stack.

[0101] In another embodiment of the method, the translation network is a Trusted Non- 3GPP Access Network (TNAN) including a Trusted Non-3PP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF), the method further including the translation network maintaining 5G / FutureG functionality across a Nl interface between a 5G / FutureG core data network and user equipment of a residential gateway via the satellite.

[0102] In another embodiment of the method, the translation network of the satellite gateway is a non-trusted access network including an untrusted access point and a Non-3GPP Interworking Function (N3IWF).

[0103] In another embodiment of the method, further including the translation layer maintaining functionality across the interface between the core data network and user equipment of the residential gateway via the satellite.

[0104] In another embodiment of the method, further including the core data network transmitting Multicast / Broadcast Services (MBS) to the satellite via the satellite gateway.

[0105] In another embodiment of the method, the MBS include one or more of satellite television including broadcast TV, multicast streaming, residential broadband, internet service, cellular services, texting services, and voice calls from an Application Function (AF).

[0106] In another embodiment of the method, the AF is one or more of a media content provider, an Internet Service Provider (ISP), and a satellite service.

[0107] Embodiments are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations that may be suitable for use with various embodiments include, but are not limited to, embedded computing systems, personal computers, server computers, mobile devices, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, medical device, network PCs, minicomputers, mainframe computers, cloud services, telephonic systems, distributed computing environments that include any of the above systems or devices, and the like.Docket: GMU-24-037

[0108] Embodiments may be described in the general context of computer executable instructions, such as program modules, being executed by computing capable devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Some embodiments may be designed to be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local

[0109] While implementations of the disclosure are susceptible to embodiment in many different forms, there is shown in the drawings and will herein be described in detail specific embodiments, with the understanding that the present disclosure is to be considered as an example of the principles of the disclosure and not intended to limit the disclosure to the specific embodiments shown and described. In the description above, like reference numerals may be used to describe the same, similar or corresponding parts in the several views of the drawings.[001 10] In this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by “comprises . . .a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.[001 1 1 ] Reference throughout this document to “one embodiment,” “certain embodiments,” “an embodiment,” “implementation(s),” “aspect(s),” or similar terms means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of such phrases or in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments without limitation.[001 12] The term “or” as used herein is to be interpreted as an inclusive or meaning any one or any combination. Therefore, “A, B or C” means “any of the following: A; B; C; ADocket: GMU-24-037 and B; A and C; B and C; A, B and C ” An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive. Also, grammatical conjunctions are intended to express any and all disjunctive and conjunctive combinations of conjoined clauses, sentences, words, and the like, unless otherwise stated or clear from the context. Thus, the term “or” should generally be understood to mean “and / or” and so forth. References to items in the singular should be understood to include items in the plural, and vice versa, unless explicitly stated otherwise or clear from the text.[001 13] Recitation of ranges of values herein are not intended to be limiting, referring instead individually to any and all values falling within the range, unless otherwise indicated, and each separate value within such a range is incorporated into the specification as if it were individually recited herein. The words “about,” “approximately,” or the like, when accompanying a numerical value, are to be construed as indicating a deviation as would be appreciated by one of ordinary skill in the art to operate satisfactorily for an intended purpose. Ranges of values and / or numeric values are provided herein as examples only, and do not constitute a limitation on the scope of the described embodiments. The use of any and all examples, or exemplary language (“e.g.,” “such as,” “for example,” or the like) provided herein, is intended merely to better illuminate the embodiments and does not pose a limitation on the scope of the embodiments. No language in the specification should be construed as indicating any unclaimed element as essential to the practice of the embodiments.[001 14] For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the embodiments described herein. The embodiments may be practiced without these details. In other instances, well-known methods, procedures, and components have not been described in detail to avoid obscuring the embodiments described. The description is not to be considered as limited to the scope of the embodiments described herein.[001 15] In the following description, it is understood that terms such as “first,” “second,” “top,” “bottom,” “up,” “down,” “above,” “below,” and the like, are words of convenience and are not to be construed as limiting terms. Also, the terms apparatus, device, system, etc. may be used interchangeably in this text.[001 16] The many features and advantages of the disclosure are apparent from the detailed specification, and, thus, it is intended by the appended claims to cover all such features and advantages of the disclosure which fall within the scope of the disclosure. Further, sinceDocket: GMU-24-037 numerous modifications and variations will readily occur to those skilled in the art, it is not desired to limit the disclosure to the exact construction and operation illustrated and described, and, accordingly, all suitable modifications and equivalents may be resorted to that fall within the scope of the disclosure.

Claims

Docket: GMU-24-037WHAT IS CLAIMED IS:

1. A satellite gateway, comprising: a ground station that is operable to connect to a satellite; and a translation network coupled to the ground station that is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway that is operable to transmit content to the satellite via the satellite gateway, the translation layer operable to maintain functionality across an interface between the core data network and a residential gateway via the satellite.

2. The satellite gateway of claim 1, where the translation layer retains uplink and downlink protocols of the one or more lower layers of the OSI stack of the satellite and provides compatibility with the core data network coupled to the satellite gateway.

3. The satellite gateway of claim 1, where the one or more lower layers of the OSI stack are at least one or more Layer 2 (L2) data link layers (DLL) of the OSI stack.

4. The satellite gateway of claim 1, where the translation network of the satellite gateway is a trusted access network including a trusted access point and a trusted gateway function.

5. The satellite gateway of claim 4, where the translation network is a Trusted Non- 3GPP Access Network (TNAN) including a Trusted Non-3PP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF) and where the translation network is operable to maintain 5G / FutureG functionality across a N1 interface between a 5G / FutureG core data network and user equipment of the residential gateway via the satellite.Docket: GMU-24-0376. The satellite gateway of claim 1, where the translation network of the satellite gateway is a non-trusted access network including an untrusted access point and a Non-3GPP Interworking Function (N3IWF).

7. The satellite gateway of claim 1, where the ground station includes the translation network.

8. The satellite gateway of claim 1, the translation layer operable to maintain functionality across the interface between the core data network and user equipment of the residential gateway via the satellite.

9. The satellite gateway of claim 1, where the content transmitted from the core data network to the satellite via the satellite gateway is Multi cast / B roadcast Services (MBS).

10. The satellite gateway of claim 9, where the MBS includes one or more of satellite television including broadcast TV, multicast streaming, residential broadband, internet service, cellular services, texting services, and voice calls from an Application Function (AF).

11. The satellite gateway of claim 10, where the AF is one or more of a media content provider, an Internet Service Provider (ISP), and a satellite service.

12. A satellite communications system, comprising: a residential gateway; and a satellite gateway coupled to a satellite, the satellite gateway including: a ground station (also a satellite ground station) that is operable to connect to the satellite; and a translation network coupled to the ground station that is operable as a translation layer between one or more lower layers of an open systems interconnection (OSI) stack of theDocket: GMU-24-037 satellite and a core data network coupled to the satellite gateway that is operable to transmit content to the satellite via the satellite gateway, the translation layer operable to maintain functionality across an interface between the core data network and the residential gateway via the satellite, the residential gateway coupled to and in communication with the satellite gateway and having one or more end-user devices each having a receiver, the receivers of the one or more end-user devices operable to receive from the satellite gateway content transmitted by the content provider over the core data network to the satellite gateway.

13. The system of claim 12, where an end-user device of the one or more end-user devices may be one or more of a hand-held device, a handset, television receiver.

14. The system of claim 12, further comprising the core data network (5G, FutureG) coupled to and in communication with the satellite gateway.

15. The system of claim 12, further comprising the content provider coupled to and in communication with the core data network and having a transmitter operable to transmit content over the core data network and the satellite gateway to the residential gateway.

16. The system of claim 12, where the content transmitted from the core data network to the satellite via the satellite gateway is Multi cast / B roadcast Services (MBS).

17. The satellite gateway of claim 16, where the MBS includes one or more of satellite television including broadcast TV, multicast streaming, residential broadband, internet service, cellular services, texting services, and voice calls from an Application Function (AF).

18. The system of claim 17, where the AF is one or more of a media content provider, an Internet Service Provider (ISP), and a satellite service.Docket: GMU-24-03719. A method of ensuring delivery of content across a satellite communications system, comprising: at a satellite gateway: receiving content from a core data network; and a translation network of the satellite gateway maintaining functionality between one or more lower layers of an open systems interconnection (OSI) stack of the satellite and a core data network coupled to the satellite gateway at a translation layer of the translation network.

20. The method of claim 19, further comprising the translation layer maintaining functionality across an interface between the core data network and a residential gateway via the satellite.

21. The method of claim 19, further comprising the translation layer retaining uplink and downlink protocols of the one or more lower layers of the OSI stack of the satellite and providing compatibility with the core data network coupled to the satellite gateway.

22. The method of claim 19, where the one or more lower layers of the OSI stack are at least one or more Layer 2 (L2) data link layers (DLL) of the OSI stack.

23. The method of claim 19, where the translation network is a Trusted Non-3GPP Access Network (TNAN) including a Trusted Non-3PP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF), the method further comprising: the translation network maintaining 5G / FutureG functionality across a N1 interface between a 5G / FutureG core data network and user equipment of a residential gateway via the satellite.Docket: GMU-24-03724. The method of claim 19, where the translation network of the satellite gateway is a non-trusted access network including an untrusted access point and a Non-3GPP Interworking Function (N3IWF).

25. The method of claim 19, further comprising the translation layer maintaining functionality across the interface between the core data network and user equipment of the residential gateway via the satellite.

26. The method of claim 19, further comprising the core data network transmitting Multi cast / B roadcast Services (MBS) to the satellite via the satellite gateway.

27. The method of claim 26, where the MBS include one or more of satellite television including broadcast TV, multicast streaming, residential broadband, internet service, cellular services, texting services, and voice calls from an Application Function (AF).

28. The method of claim 27, where the AF is one or more of a media content provider, an Internet Service Provider (ISP), and a satellite service.

Images