Session handling method and apparatus

Patent metadata

Field	Value
Publication number	US-11540337-B2
Application number	US-202016791775-A
Country	US
Kind code	B2
Filing date	Feb 14, 2020
Priority date	Aug 15, 2017
Publication date	Dec 27, 2022
Grant date	Dec 27, 2022

Abstract

A session handling method and apparatus, where the method includes: initiating, by a terminal, an application (APP); determining a session type of a packet data unit (PDU) session based on the APP; and sending a first message to an access and mobility management function (AMF) entity, where the first message includes the session type, and the first message is used to request to establish the PDU session of the session type. In the method, a network side can establish the PDU session of the corresponding type based on the session type of the PDU session that is sent by the terminal, in order to establish the PDU session of the correct type for the terminal.

First claim

What is claimed is:

1. A session handling method comprising:
receiving, by a terminal, a user equipment (UE) route selection policy (URSP) from a network, wherein the URSP comprises: a traffic filter, direct offload information, slice information, continuity types, a data network (DN) identifier, an access type, and a first session type, wherein the traffic filter includes a first application (APP), and wherein the first session type is an Ethernet type;
initiating, by the terminal, the first APP;
determining, by the terminal, the Ethernet type associated with the first APP based on the URSP;
sending, by the terminal, a first message to an access and mobility management function entity, wherein the first message comprises the Ethernet type, and wherein the first message requests to establish a first session of the Ethernet type;
receiving, by the terminal, a session reject message from a session management function entity, wherein the session reject message comprises a second session type determined by the session management function entity, and wherein the second session type is different from the Ethernet type; and
sending, by the terminal, a third message to the access and mobility management function entity, wherein the third message comprises the second session type, and wherein the third message requests to establish a second session of the second session type.

2. The session handling method according to claim 1 , wherein at least one the first session or the second session is a packet data unit (PDU) session.

3. The session handling method according to claim 1 , further comprising:
determining, by the terminal based on a second correspondence, that the DN identifier corresponds to the first APP;
determining, by the terminal, a DN type corresponding to the DN identifier; and
determining, by the terminal based on a third correspondence, the Ethernet type corresponding to the DN type, wherein the second correspondence is between an APP and the DN identifier, and wherein the third correspondence is between the DN type and the first session type.

4. The session handling method according to claim 3 , further comprising:
sending, by the terminal, a request message to the access and mobility management function entity; and
receiving, by the terminal, the DN identifier and the DN type from the access and mobility management function entity based on the request message.

5. The session handling method according to claim 3 , further comprising:
sending, by the terminal, a request message to the access and mobility management function entity; and
receiving, by the terminal, the DN identifier and the DN type that are broadcast by a radio access network (RAN) device.

6. The session handling method according to claim 1 , further comprising sending, by the terminal, first DN information to the access and mobility management function entity, wherein the first DN information comprises either the DN identifier or the DN identifier and a DN type, and wherein the first DN information is for the access and mobility management function entity to determine the session management function entity based on the DN identifier.

7. The session handling method according to claim 1 , wherein the first APP is one of a video application, a text application, or a picture application.

8. The session handling method according to claim 1 , wherein sending the first message to the access and mobility management function entity comprises sending, by the terminal, the first message to the access and mobility management function entity via a non-access stratum (NAS) message, wherein the NAS message comprises first DN information for the access and mobility management function entity to determine the session management function entity, and wherein the first DN information comprises at least one of the DN identifier or a DN type.

9. An apparatus comprising:
a memory storage configured to store instructions; and
one or more processors in communication with the memory storage and configured to execute the instructions to:
receive a user equipment (UE) route selection policy (URSP) from a network, wherein the URSP comprises: a traffic filter, direct offload information, slice information, continuity types, a data network (DN) identifier, an access type, and a first session type, wherein the traffic filter includes a first application (APP), and wherein the first session type is an Ethernet type;
initiate the first APP;
determine the Ethernet type associated with the first APP based on the URSP;
send a first message to an access and mobility management function entity, wherein the first message comprises the Ethernet type, and wherein the first message requests to establish a first session of the Ethernet type;
receive a session reject message from a session management function entity, wherein the session reject message comprises a second session type determined by the session management function entity, and wherein the second session type is different from the first session type; and
send a third message to the access and mobility management function entity, wherein the third message comprises the second session type, and wherein the third message requests to establish a second session of the second session type.

10. The apparatus according to claim 9 , wherein at least one of the first session or the second session is a packet data unit (PDU) session.

11. The apparatus according to claim 10 , wherein the apparatus comprises a terminal, and wherein the terminal is configured to obtain a first correspondence between the first APP and the session type from the access and mobility management function entity.

12. The apparatus according to claim 11 , wherein the first APP is a video application.

13. The apparatus according to claim 11 , wherein the first APP is a text application.

14. The apparatus according to claim 11 , wherein the first APP is a picture application.

15. The apparatus according to claim 9 , wherein the one or more processors execute the instructions to:
determine, based on a second correspondence, that the DN identifier corresponds to the first APP;
determine a DN type corresponding to the DN identifier; and
determine, based on a third correspondence, the Ethernet type corresponding to the DN type, wherein the second correspondence is between an APP and the DN identifier, and wherein the third correspondence is between the DN type and the first session type.

16. The apparatus according to claim 15 , wherein the one or more processors execute the instructions to:
send a request message to the access and mobility management function entity; and
receive the DN identifier and the DN type from the access and mobility management function entity based on the request message.

17. The apparatus according to claim 15 , wherein the one or more processors execute the instructions to:
send a request message to the access and mobility management function entity; and
receive the DN identifier and the DN type that are broadcast by a radio access network (RAN) device.

18. The apparatus according to claim 9 , wherein the one or more processors execute the instructions to send first DN information to the access and mobility management function entity, and wherein the first DN information comprises the DN identifier or the DN identifier and a DN type.

19. The apparatus according to claim 18 , wherein the first DN information is for the access and mobility management function entity to determine a session management function entity based on the DN

Assignees

• Huawei Tech Co Ltd

Inventors

• Wang Yuan
• Chen Zhongping
• Xu Changchun

Classifications

• H04W36/0027

  for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections · CPC title

• H04L67/146

  Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title

• H04W76/12 Primary

  Setup of transport tunnels · CPC title

• H04W8/08

  Mobility data transfer · CPC title

• H04W40/02

  Communication route or path selection, e.g. power-based or shortest path routing · CPC title