TECHNIQUES FOR ROUTING REGISTRATION REQUEST OF ROAMING USER EQUIPMENT BY ROUTING ENTITY
FIG3 shows a block diagram of an exemplary bridge entity 260 according to the disclosure
FIG3 shows a block diagram of an exemplary bridge entity 260 according to the disclosure. The bridge entity 260 can be connected between a plurality of visited network slices 240 and a plurality of home network slices 210. The bridge entity 260 comprises a routing table 301 and a processor 302.
block diagram
210
network slice network slices
203
registration request message
301
routing table
302
processor
240
network slice network slices
260
entity
['1. A 5G communication system (200), comprising: at least one visited network slice (240) comprising a visited network access entity (251, 252); a home network slice (210) comprising a home Access and Mobility Management Function, AMF, entity (221); and a router entity (260) coupled between the visited network access entity (251) and the home AMF entity (221), wherein the router entity (260) is configured to route a registration request message (203) of a roaming user equipment, UE, (202) received from the visited network access entity (251) to the home AMF entity (221), wherein the router entity (260) is a central entity located at a central location of the 5G communication system (200) outside the at least one visited network slice (240) and the home network slice (210), wherein the visited network access entity (251, 252) comprises a routing table which comprises at least one internal route (253) for routing messages from non-roaming UEs (202) that are configured for the at least one visited network slice (240) and an external route (254) for routing messages (203) from roaming UEs (202) that are not configured for the at least one visited network slice (240).', '10. A visited network access entity of a visited network slice (240), the visited network access entity (300) comprising: a routing table comprising at least one internal route (253) which routes messages from non-roaming UEs (202), that are configured for the visited network slice, to a network entity (251) of the visited network slice (240) and an external route (254) for routing messages (203) from roaming UEs (202), that are not configured for the visited network slice, to a router entity (260) ; and a processor configured to forward an incoming registration request message (203) from the roaming and ef non-roaming UE (202) based on looking up the routing table with respect to an identity, UE ID, of the roaming and non-roaming UE (202) comprised in the registration request message (203) and/or a public land mobile network identity, PLMN ID, derived from the UE ID.']