# US 12,604,190 B2 · Techniques for enabling communication between a plurality of disparate networks and devices utiilzing various connection technologies

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,604,190 B2
- Document ID: US12604190B2
- Status: Granted
- Kind: B2
- Application number: 17/872,906
- Filed: 2022-07-25
- Published: 2024-01-25
- Granted: 2026-04-14
- Earliest claimed: 2022-07-25
- Assignees: Meta Platforms, Inc.
- Applicants: Meta Platforms, Inc.
- Inventors: Behzad Barjasteh Mohebbi
- Web page: https://patentgrep.com/patent/US12604190B2

## CPC

- H04W 12/088: using filters or firewalls
- H04W 12/72: Subscriber identity
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

According to examples, a system for enabling communication between one or more disparate networks and network devices utilizing various connection technologies. The system may include a processor and a memory storing instructions. The processor, when executing the instructions, may cause the system to modify a security gateway to provide a metaverse security gateway by implementing a protocol associated with a 3rd Generation Partnership Project (3GPP) standard, modify a server to provide a metaverse server by implementing a protocol associated with the 3rd Generation Partnership Project (3GPP) standard, and utilize the metaverse security gateway and the metaverse server to facilitate a metaverse communication for a client device.

## Claims

### Claim 1

A system, comprising:
a security gateway;
a processor; and
a memory storing instructions, which when executed by the processor, cause the processor to:
modify the security gateway to provide a metaverse security gateway by implementing a first protocol and a second protocol in a protocol stack of the security gateway, wherein modifying the security gateway includes implementation of an internet protocol security (IPsec) tunnel utilizing a dynamic key and a universal subscriber identity module (USIM), wherein the first protocol is associated with a 3rd Generation Partnership Project (3GPP) standard, and wherein the second protocol is different than the first protocol; and
utilize the metaverse security gateway to facilitate a metaverse communication for a first client device using the first protocol and a second client device using the second protocol.

### Claim 2 (depends on 1)

The system of claim 1, wherein the second protocol is associated with Fast Identity Online (FIDO) authentication.

### Claim 3 (depends on 2)

The system of claim 2, wherein modifying the security gateway further comprises assigning, via implementation of a security gateway (SecGW), a proxy subscriber identity module (SIM) to the first client device or the second client device.

### Claim 4 (depends on 1)

The system of claim 1, wherein the instructions, when executed by the processor, further cause the processor to:
facilitate a modification of an aspect of the second client device to utilize a Fast IDentity Online (FIDO) standard in association with the security gateway.

### Claim 5 (depends on 4)

The system of claim 4, wherein the instructions, when executed by the processor, further cause the processor to:
modify a server to provide a metaverse server by implementing the first protocol associated with the 3rd Generation Partnership Project (3GPP) standard.

### Claim 6 (depends on 5)

The system of claim 5, wherein modifying the server comprises implementing at least one functional block associated with the 3rd Generation Partnership Project (3GPP) standard.

### Claim 7 (depends on 5)

The system of claim 5, wherein modifying the server comprises implementing a Fast IDentity Online (FIDO) server within a 5G core (5GC) network.

### Claim 8 (depends on 7)

The system of claim 7, wherein modifying the server further comprises assigning a proxy subscriber identity module (SIM), via the 5G core (5GC) network, to a client device.

### Claim 9

A method, comprising:
modifying a security gateway to provide a metaverse security gateway by implementing a first protocol and a second protocol in a protocol stack of the security gateway, wherein modifying the security gateway includes implementation of an internet protocol security (IPsec) tunnel utilizing a dynamic key and a universal subscriber identity module (USIM), wherein the first protocol is associated with a 3rd Generation Partnership Project (3GPP) standard, and wherein the second protocol is different than the first protocol;
modifying a server to provide a metaverse server by implementing a third protocol associated with the 3rd Generation Partnership Project (3GPP) standard; and
utilizing the metaverse security gateway and the metaverse server to facilitate a metaverse communication with a first device using the first protocol and a second device using the second protocol.

### Claim 10 (depends on 9)

The method of claim 9, wherein modifying the server comprises implementing at least one functional block associated with the 3rd Generation Partnership Project (3GPP) standard.

### Claim 11 (depends on 9)

The method of claim 9, wherein modifying the server comprises implementing a Fast IDentity Online (FIDO) server within a 5G core (5GC) network.

### Claim 12 (depends on 11)

The method of claim 11, wherein modifying the server further comprises assigning a proxy subscriber identity module (SIM), via the 5G core (5GC) network, to a client device.

### Claim 13 (depends on 9)

The method of claim 9, wherein modifying the security gateway comprises implementing a non-access stratum (NAS) layer in the protocol stack of the security gateway.

### Claim 14 (depends on 9)

The method of claim 9, wherein the security gateway is to support 5G-capable devices and non-5G-capable devices.

### Claim 15

A non-transitory computer-readable storage medium having an executable stored thereon, which when executed instructs a processor to:
modify a security gateway to provide a metaverse security gateway by implementing a first protocol and a second protocol in a protocol stack of the security gateway, wherein modifying the security gateway includes implementation of an internet protocol security (IPsec) tunnel utilizing a dynamic key and a universal subscriber identity module (USIM), wherein the first protocol is associated with a 3rd Generation Partnership Project (3GPP) standard, and wherein the second protocol is different than the first protocol;
modify a server to provide a metaverse server by implementing the first protocol associated with the 3rd Generation Partnership Project (3GPP) standard, wherein modifying the server comprises implementing at least one functional block associated with the 3rd Generation Partnership Project (3GPP) standard, the at least one functional block comprising Access Management function (AMF), Security Anchor function (SEAF), Authentication Server Function (AUSF), Authentication Credential Repository and Processing Function (ARPF) Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), a User Plane Function (UPF) or a Session Management Function (SMF); and
utilize the metaverse security gateway and the metaverse server to facilitate a metaverse communication for a first client device using the first protocol and a second client device using the second protocol.

### Claim 16 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein modifying the server further comprises implementing a Fast IDentity Online (FIDO) standard on a dedicated server.

### Claim 17 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein modifying the server further comprises assigning a proxy subscriber identity module (SIM), via implementation of the dedicated server, to the first client device.

### Claim 18 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein modifying the security gateway comprises implementing a non-access stratum (NAS) layer in the protocol stack of the security gateway.
