US 12,452,816 B2
Relocating an access gateway
Apostolis Salkintzis, Athens (GR); and Genadi Velev, Darmstadt (DE)
Assigned to Lenovo (Singapore) Pte. Ltd., Singapore (SG)
Appl. No. 17/916,757
Filed by Lenovo (Singapore) PTE. LTD., New Tech Park (SG)
PCT Filed Apr. 3, 2020, PCT No. PCT/EP2020/059652
§ 371(c)(1), (2) Date Oct. 3, 2022,
PCT Pub. No. WO2021/197630, PCT Pub. Date Oct. 7, 2021.
Prior Publication US 2023/0146052 A1, May 11, 2023
Int. Cl. H04W 60/00 (2009.01); H04W 12/069 (2021.01); H04W 48/18 (2009.01)
CPC H04W 60/00 (2013.01) [H04W 12/069 (2021.01); H04W 48/18 (2013.01)] 17 Claims
OG exemplary drawing
 
1. An first trusted non-3GPP gateway function (“TNGF”) comprising:
a processor; and
a memory coupled to the processor, the processor configured to cause the first TNGF to:
initiate registration of a user equipment (“UE”) with a mobile communication network;
receive a relocation command from an access and mobility management function (“AMF”) in the mobile communication network while the registration is ongoing, wherein the relocation command comprises containing an address of a second TNGF and a first security key;
determine whether connectivity with the second TNGF is supported;
transmit a first request to the second TNGF containing a UE identity and an AMF identity in response to connectivity with the second TNGF being supported; and
transmit a relocation reject message to AMF in response to connectivity with the second TNGF not being supported.