Network initiated UPF sessions transfer

Patent metadata

Field	Value
Publication number	US-11224093-B2
Application number	US-201916538187-A
Country	US
Kind code	B2
Filing date	Aug 12, 2019
Priority date	Aug 13, 2018
Publication date	Jan 11, 2022
Grant date	Jan 11, 2022

Abstract

A SMF receives from a first UPF, first message(s) indicating a status of the first UPF. The SMF determines, based on the status, to transfer sessions for a group of wireless devices from the first UPF to a second UPF. The SMF sends to the second UPF, a second message indicating an establishment request of sessions for the group of wireless devices. The second message comprises session identifiers of the sessions. The SMF receives from the second UPF, a third message indicating a result of the establishment request. The SMF sends to the first UPF, based on the result, a fourth message indicating release of session(s) of the sessions. The fourth message comprises session identifier(s) of the session(s).

First claim

What is claimed is:

1. A method comprising:
receiving, by a session management function (SMF) from a first user plane function (UPF), at least one first message indicating a status of the first UPF;
determining, by the SMF and based on the status, to transfer a plurality of sessions for a plurality of wireless devices from the first UPF to a second UPF;
sending, by the SMF to the second UPF, a second message indicating an establishment request of the plurality of sessions for the plurality of wireless devices, wherein the second message comprises session identifiers of the plurality of sessions;
receiving, by the SMF from the second UPF, a third message indicating a result of the establishment request; and
sending, by the SMF to the first UPF and based on the result, a fourth message indicating release of at least one session of the plurality of sessions, wherein the fourth message comprises at least one session identifier of the at least one session.

2. The method of claim 1 , further comprising receiving, by the SMF from the first UPF, a fifth message indicating a response to the fourth message.

3. The method of claim 1 , further comprising receiving, by the SMF from a first network function, the at least one first message indicating a status of the first UPF, wherein the first network function comprises at least one of:
an operation and maintenance function; or
a policy control function.

4. The method of claim 1 , wherein the first message further comprises a first parameter indicating a request for transferring sessions of one or more UPFs, wherein the first parameter comprises at least one of:
a UPF identifier of the first UPF;
the session identifiers of the plurality of sessions;
location information of the first UPF;
a data network name of the first UPF;
a packet data unit session type of the plurality of sessions;
a quality of service;
a fully qualified connection set identifier;
a single network slice selection assistance information of the plurality of sessions; or
a data network access identifier of the first UPF.

5. The method of claim 1 , wherein the first message further comprises a second parameter comprising traffic load information of one or more sessions of the first UPF, wherein the traffic load information comprises at least one of:
a session identifier;
a fully qualified connection set identifier;
a usage report;
an error indication report;
load control information;
overload control information; or
an additional usage reports information.

6. The method of claim 1 , wherein the first message further comprises a third parameter comprising node information of the first UPF, wherein the node information comprises at least one of:
a node identifier;
a fully qualified connection set identifier;
a node report type;
a user plane path failure report;
a usage report for sessions; or
an overload report.

7. The method of claim 1 , wherein the third message comprises at least one of:
uplink fully qualified tunnel endpoint identifiers for the plurality of sessions; or
downlink fully qualified tunnel endpoint identifiers for the plurality of sessions.

8. The method of claim 1 , further comprising sending, by the SMF to a second network function, a fifth message comprising downlink fully qualified tunnel endpoint identifiers of the second UPF for the plurality of sessions.

9. The method of claim 8 , further comprising receiving, by the SMF from the second network function and in response to the fifth message, a sixth message comprising uplink fully qualified tunnel endpoint identifiers of the second network function for the plurality of sessions.

10. The method of claim 8 , wherein the second network function comprises at least one of:
a packet data unit session anchor user plan function; or
an egress network function, wherein the egress network function is an intermediate UPF and/or PDU session anchor UPF.

11. The method of claim 1 , further comprising:
sending, by the SMF to a third network function, a fifth message comprising uplink fully qualified tunnel endpoint identifiers of the second UPF for the plurality of sessions; and
receiving, by the SMF from the third network function and in response to the fifth message, a sixth message comprising downlink fully qualified tunnel endpoint identifiers of the third network function for the plurality of sessions.

12. The method of claim 11 , wherein the third network function comprises at least one of an ingress network function, and the ingress network function being an intermediate UPF.

13. The method of claim 1 , wherein the plurality of sessions comprises:
at least one first session of a first wireless device; and
at least one second session of a second wireless device.

14. The method of claim 1 , further comprising:
sending, by the SMF to the second UPF, a fifth message comprising:
an uplink fully qualified tunnel endpoint identifier of a second network function for the plurality of sessions; and
a downlink fully qualified tunnel endpoint identifier of a third network function for the plurality of sessions; and

receiving, by the SMF from the second UPF and in response to the fifth message, a sixth message for the plurality of sessions.

15. The method of claim 1 , wherein the result indicates that establishment of one or more sessions of the plurality of sessions failed.

16. The method of claim 1 , further comprising:
sending, by the SMF to a fourth network function, a fifth message comprising uplink fully qualified tunnel endpoint identifiers of the second UPF for the plurality of sessions; and
receiving, by the SMF from the fourth network function and in response to the fifth message, a sixth message comprising a downlink fully qualified tunnel endpoint identifier of a fifth network function for the plurality of sessions.

17. The method of claim 16 , further comprising:
sending, by the fourth network function to the fifth network function, a seventh message comprising uplink fully qualified tunnel endpoint identifiers of the second UPF for the plurality of sessions; and
receiving, by the fourth network function from the fifth network function and in response to the seventh message, a eight message comprising downlink fully qualified tunnel endpoint identifiers of the fifth network function for the plurality of sessions.

18. The method of claim 17 , wherein the fourth network function comprises an access and mobility management function.

19. The method of claim 18 , wherein the fifth network function comprises at least one access network.

20. The method of claim 1 , further comprising:
receiving, by the SMF from a unified data management and/or a policy control function, a fifth message comprising transfer priority information; and
employing, by the SMF, the transfer priority information to transfer the plurality of sessions from the first UPF to a second UPF.

Assignees

• Bharatia Jayshree
• Dinan Esmael
• Park Kyungmin
• Talebi Fard Peyman
• Qiao Weihua
• Ofinno Llc

Inventors

• Bharatia Jayshree
• Dinan Esmael
• Park Kyungmin
• Talebi Fard Peyman
• Qiao Weihua

Classifications

• H04W80/10 Primary

  adapted for {application} session management, e.g. SIP [Session Initiation Protocol] {(connection management H04W76/00; arrangements for session management H04L67/14)} · CPC title

• H04W76/30

  Connection release · CPC title

• H04W76/11

  Allocation or use of connection identifiers · CPC title

• H04W80/12

  Application layer protocols, e.g. WAP [Wireless Application Protocol] · CPC title

• H04W92/24

  between backbone network devices · CPC title