Search

KR-102964517-B1 - Access Gateway Relocation

KR102964517B1KR 102964517 B1KR102964517 B1KR 102964517B1KR-102964517-B1

Abstract

Devices, methods, and systems for relocating an access gateway during UE registration are disclosed. One device (600) includes an interface (640) that communicates with a remote unit and a plurality of network functions in a mobile communication network. The device (600) includes a processor (605) that initiates the registration of a remote unit into a mobile communication network (705) and receives a relocation command (710) from an AMF while the registration is in progress, wherein the relocation command includes the address of a first TNGF and a first security key. If connection with the first TNGF is supported, the processor (605) transmits a first request to the first TNGF (720), the first request including a remote unit identity and an AMF identity. However, if connection with the first TNGF is not supported, the processor (605) transmits a relocation refusal message to the AMF (725).

Inventors

  • 살킨치스, 아포스톨리스
  • 벨레브, 제나디

Assignees

  • 레노보 (싱가포르) 피티이. 엘티디.

Dates

Publication Date
20260513
Application Date
20200403

Claims (20)

  1. As a device, An interface that communicates with a remote unit via a non-3GPP access network and communicates with multiple network functions within a mobile communication network; and processor Includes, and the processor is: Initiating the registration of a remote unit to the above mobile communication network; While the above registration is in progress, a relocation command is received from an access and mobility management function ("AMF") within the mobile communication network, and —the relocation command includes the address of the first TNGF and the first security key—; Determine whether connection with the above-mentioned first TNGF is supported; In response to the support of connection with the first TNGF, a first request including a remote unit identity and an AMF identity is transmitted to the first TNGF; In response to the fact that connection with the above-mentioned first TNGF is not supported, a relocation refusal message is sent to the AMF, and A device in which the relocation command including the address of the first TNGF indicates that the first TNGF is selected to resume the registration of the remote unit to the mobile communication network.
  2. A device according to claim 1, wherein the processor initiates the registration of the remote unit to the mobile communication network by transmitting an extensible authentication protocol 5G (EAP-5G) packet including a start indication to the remote unit, and the processor also relays at least one non-access layer ("NAS") message between the remote unit and the AMF.
  3. A device according to claim 1, wherein the processor forwards the address of the first TNGF to the remote unit before transmitting the first request to the first TNGF or transmitting the relocation refusal message to the AMF.
  4. A device according to paragraph 3, wherein the relocation command includes a Security Mode Control ("SMC") request, and the processor forwards the address of the SMC request and the first TNGF to the remote unit before transmitting the first request to the first TNGF or transmitting a relocation refusal message to the AMF, and the processor receives a message from the remote unit in response to forwarding the SMC request, and the message from the remote unit includes an SMC response.
  5. A device according to paragraph 4, wherein the first request includes the SMC response, the processor receives the first response from the first TNGF, the processor generates a second security key using the first security key, and forwards the second security key to an access point serving a remote unit in the non-3GPP access network.
  6. In paragraph 4, the device, wherein the relocation refusal message includes an SMC response.
  7. delete
  8. In claim 1, the first TNGF is selected to resume the registration of the remote unit to the mobile communication network in response to the determination of the AMF that the device does not support the set of network slices allowed for the remote unit, and the first TNGF supports the set of network slices allowed, the device.
  9. A device according to claim 1, wherein the relocation command includes the AMF identity, and the AMF identity is a globally unique AMF identity ("GUAMI"; Globally Unique AMF Identity).
  10. As a method, A step of initiating the registration of a remote unit to a mobile communication network; The step of receiving a relocation command from an access and mobility management function ("AMF") within the mobile communication network while the above registration is in progress, ―the relocation command includes the address of the first TNGF and the first security key―; A step of determining whether connection with the first TNGF is supported; A step of transmitting a first request to the first TNGF, including a remote unit identity and an AMF identity, in response to the support of connection with the first TNGF; and A step of sending a relocation refusal message to the AMF in response to the fact that connection with the first TNGF is not supported. Includes, A method in which the relocation command including the address of the first TNGF indicates that the first TNGF is selected to resume the registration of the remote unit to the mobile communication network.
  11. delete
  12. delete
  13. delete
  14. delete
  15. delete
  16. delete
  17. delete
  18. delete
  19. delete
  20. delete

Description

Access Gateway Relocation The subject matter disclosed in this specification generally relates to, for example, relocating an access gateway while UE registration is in progress. The following abbreviations and acronyms are defined herein, at least some of which are mentioned in the description below. 3G Partnership Project ("3GPP"), 5G Core ("5GC"), Access and Mobility Management Function ("AMF"), Access Point Name ("APN"), Access Layer ("AS"), Access Network Information ("ANI"), Application Programming Interface ("API"), Data Network Name ("DNN"), Downlink ("DL"), Enhanced Mobile Broadband ("eMBB"), Evolved Node-B ("eNB"), Evolved Packet Core ("EPC"), Evolved UMTS Terrestrial Radio Access Network ("E-UTRAN"), Home Subscriber Server ("HSS"), IP Multimedia Subsystem ("IMS"), also known as the "IP Multimedia Core Network Subsystem"), Internet Protocol (“IP”), Long Term Evolution (“LTE”), LTE Advanced (“LTE-A”), Media Access Control (“MAC”), Mobile Network Operator (“MNO”), Mobility Management Entity ("MME"), Non-Access Layer ("NAS"), Narrowband ("NB"), Network Function ("NF"), Network Access Identifier ("NAI"), Next Generation (e.g., 5G) Node-B ("gNB"), Next Generation Radio Access Network ("NG-RAN"), New Radio ("NR"), Policy Control Function ("PCF"), Packet Data Network ("PDN"), Packet Data Unit ("PDU"), PDN Gateway ("PGW"), Public Land Mobile Network ("PLMN"), Quality of Service ("QoS"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Radio Resource Control ("RRC"), Reception ("Rx"), Single Network Slice Selection Auxiliary Information ("S-NSSAI"), Serving Gateway ("SGW"), Session Management Function ("SMF"), Transmission Control Protocol ("TCP"), Transport ("Tx"), Unified Data Management ("UDM"), Network Function in 5GC), User Entity/Equipment (Mobile Terminal) ("UE"), Uplink ("UL"), User Plane ("UP"), Universal Mobile Communications System ("UMTS"), User Datagram Protocol (“UDP”), User Location Information (“ULI”), Wireless Local Area Network (“WLAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”). In certain embodiments, the UE can access the 5G core of the PLMN through various types of non-3GPP access networks, all of which provide IP access between the UE and the 5G core ("5GC") through an access gateway. A more specific description of the embodiments briefly described above will be made with reference to specific embodiments illustrated in the accompanying drawings. With the understanding that these drawings illustrate only some embodiments and should not be construed as limiting the scope accordingly, the present disclosure will be described and explained with additional specificity and detail through the use of the accompanying drawings: FIG. 1 is a drawing illustrating an embodiment of a wireless communication system for relocating an access gateway during UE registration; FIG. 2a is a signal flowchart illustrating an example of a procedure for N3IWF relocation during UE registration; FIG. 2b is a continuation of the procedure illustrated in FIG. 2a; FIG. 2c is a continuation of the procedure illustrated in FIG. 2b; FIG. 3a is a signal flow diagram illustrating an example of a procedure for TNGF relocation during UE relocation; FIG. 3b is a continuation of the procedure illustrated in FIG. 3a; FIG. 3c is a continuation of the procedure illustrated in FIG. 3b; FIG. 4a is a signal flowchart illustrating another embodiment of a procedure for TNGF relocation during UE relocation and is a continuation of the procedure illustrated in FIG. 3a; FIG. 4b is a continuation of the procedure illustrated in FIG. 4a; FIG. 5 is a block diagram illustrating one embodiment of a user equipment device for relocating an access gateway during UE registration; FIG. 6 is a block diagram illustrating one embodiment of a network equipment device for relocating an access gateway during UE registration; FIG. 7 is a flowchart illustrating one embodiment of a first method for relocating an access gateway during UE registration; FIG. 8 is a flowchart illustrating one embodiment of a second method for relocating an access gateway during UE registration; FIG. 9 is a flowchart illustrating one embodiment of a third method for relocating an access gateway during UE registration; and FIG. 10 is a flowchart illustrating one embodiment of a fourth method for relocating an access gateway during UE registration. As will be understood by a person skilled in the art, embodiments of the embodiments may be embodied as a system, device, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware embodiments. For example, the disclosed embodiments may be implemented as off-the-shelf semiconductors, such as hardware circuits including custom very-large-scale integration ("VLSI") circuits or gate arrays, logic chips, transistor