User device determines whether to create a new session based on session type information
A session processing method related to the field of wireless communications technologies is provided. The method discloses: obtaining, by user equipment (UE), session type information, where the session type information is used to indicate a type of a first session; and when a first application triggers a first service, determining, by the UE based on the session type information, whether a create session request needs to be initiated for the first service. According to the solutions provided in embodiments, before the create session request is initiated, the UE may determine whether to reuse a created session or create a new session. In this way, for a service that can reuse a created session, no new session needs to be created, thereby reducing signaling exchange between the UE and a network side.
1. A session processing method comprising:
obtaining, by user equipment (UE), session type information, wherein the session type information indicates a type of a first session, the session type information comprises a data network name (DNN), supported by the first session, and the session type information further comprises at least one of a type of a service supported by the first session and a type of a slice supporting the first session; and
in response to a first application triggering a first service, determining, by the UE based on the session type information, whether a create session request needs to be initiated for the first service.
2. The method according to claim 1 , wherein the determining, by the UE based on the session type information, whether the create session request needs to be initiated for the first service comprises:
determining, by the UE based on the session type information and a preconfigured correspondence among (a) the first application, (b) a DNN accessed by the first application, and (c) a type of the first service or a type of a slice required for supporting the first service, whether there is a created session that supports the DNN accessed by the first application, and supports at least one of the type of the first service or the type of the slice supporting the first session.
3. The method according to claim 2 , wherein in response to there being the created session that can support the DNN accessed by the first application and at least one of the type of the first service or the type of the slice supporting the first session, the UE reuses the created session for the first application to access the DNN.
4. The method according to claim 2 , wherein in response to there being no created session that can support the DNN accessed by the first application and at least one of the type of the first service or the type of the slice supporting the first session, the UE determines to initiate the create session request for the first service.
5. The method according to claim 1 , wherein the obtaining, by the UE, the session type information comprises: obtaining, by the UE, the session type information in a create session procedure; or obtaining, by the UE, the session type information in an initial attach procedure; or obtaining, by the UE, the session type information in a tracking area update procedure.
6. The method according to claim 1 , wherein the obtaining, by the UE, the session type information comprises:
receiving, by the UE, a create session response message from a session management function (SMF) device, wherein the create session response message carries the session type information.
7. The method according to claim 1 , wherein the obtaining, by the UE, the session type information comprises:
obtaining, by the UE, the session type information in an initial attach procedure.
8. The method according to claim 1 , wherein the obtaining, by the UE, the session type information comprises:
obtaining, by the UE, the session type information in a tracking area update procedure.
9. A communication device comprising:
a receiver, configured to cooperate with a processor to obtain session type information, wherein the session type information indicates a type of a first session, the session type information comprises a data network name (DNN), supported by the first session, and the session type information further comprises at least one of a type of a service supported by the first session and a type of a slice supporting the first session; and
the processor, configured to: in response to a first application triggering a first service, determine, based on the session type information, whether a create session request needs to be initiated for the first service.
10. The communication device according to claim 9 , wherein the processor is configured to: determine, based on the session type information and a preconfigured correspondence among (a) the first application, (b) a DNN accessed by the first application and (c) a type of the first service or a type of a slice required for supporting the first service, whether there is a created session that supports the DNN accessed by the first application, and at least one of the type of the first service or the type of the slice supporting the first session.
11. The communication device according to claim 10 , wherein the processor is configured to: in response to there being the created session that can support the DNN accessed by the first application and at least one of the type of the first service or the type of the slice supporting the first session, the communication device reuses the created session for the first application to access the DNN.
12. The communication device according to claim 10 , wherein the processor is configured to: in response to there being no created session that can support the DNN accessed by the first application and at least one of the type of the first service or the type of the slice supporting the first session, the communication device determines to initiate the create session request for the first service.
13. The communication device according to claim 9 , wherein the receiver is configured to cooperate with the processor to obtain the session type information in a create session procedure.
14. The communication device according to claim 13 , wherein the receiver is configured to cooperate with the processor to receive a create session response message from a session management function (SMF) device, wherein the create session response message carries the session type information.
15. A session processing system comprising: a user equipment (UE) and a session management function (SMF) device, wherein
the SMF device, is configured to send a create session response message to the UE, wherein the create session response message carries a session type information, the session type information indicates a type of a first session, the session type information comprises a data network name (DNN) supported by the first session, and the session type information further comprises at least one of a type of a service supported by the first session and a type of a slice supporting the first session;
the UE is configured to receive the create session response message, and in response to a first application triggering a first service, determine based on the session type information, whether a create session request needs to be initiated for the first service.
16. The system according to claim 15 , wherein when determining whether the create session request needs to be initiated for the first service, the UE is configured to:
determine based on the session type information and a preconfigured correspondence among (a) the first application, (b) a DNN accessed by the first application and (c) a type of the first service or a type of a slice required for supporting the first service, whether there is a created session that supports the DNN accessed by the first application, and supports at least one of the type of the first service or the type of the slice supporting the first session.
17. The system according to claim 16 , wherein the UE is configured to: reuse the created session for the first application to access the DNN in response to there being a created session that can support the DNN accessed by the first application and at least one of the type of the first service or the type of a slice supporting the first session.
18. The system according to claim 16 , wherein the UE is configured to: determine to initiate the create session request for the first service in response to there being no created session that can support the DNN accessed by the first application and at least one of the type of the first service or the type of the slice supporting the first session.
19. The system according to claim 15 , wherein the UE is configured to: receive a create session response message from a session management function (SMF) device, wherein the create session response message carries the session type information.