WO2020034802A1

WO2020034802A1 - Method and device for activating pdu session

Info

Publication number: WO2020034802A1
Application number: PCT/CN2019/096278
Authority: WO
Inventors: 王胡成
Original assignee: 电信科学技术研究院有限公司
Priority date: 2018-08-13
Filing date: 2019-07-17
Publication date: 2020-02-20
Also published as: CN110831091A; CN110831091B

Abstract

The present application relates to the technical field of wireless communication, relating in particular to a method and device for activating a PDU session so as to solve the problem wherein there is still no definite solution for how to activate a PDU session of a service time delay-sensitive service. An embodiment of the present application comprises: an AMF entity receiving a request message sent by a UE; determining a permanently online PDU session corresponding to the UE according to the request message and/or context information of the UE that is maintained by the AMF entity; and informing an SMF entity to resume the establishment of a user plane connection of the permanently online PDU session. Since the SMF entity is informed to resume the user plane connection of the permanently online PDU session in the embodiment of the present application, it is not necessary to request the establishment of the user plane connection of the PDU session when the UE needs to transmit uplink and downlink data on the permanently online PDU session, thereby reducing a time delay and further improving system performance.

Description

Method and equipment for activating PDU session

Cross-reference to related applications

This application claims the priority of a Chinese patent application filed on August 13, 2018 with the Chinese Patent Office, application number 201810917342.8, and application name "A method and device for activating a PDU session", the entire contents of which are incorporated herein by reference. Applying.

Technical field

The present application relates to the field of wireless communication technologies, and in particular, to a method and device for activating a PDU session.

Background technique

A packet data unit (PDU) session is a session between a terminal and a data network (DN) to provide PDU connectivity services. PDU connectivity service refers to a service that provides PDU exchange between a terminal and a DN determined by a Data Network Name (DNN).

In the current 5G system, selective activation of PDU sessions is supported, that is, when multiple PDU sessions are established for User Equipment (UE), a portion of the PDU sessions can be activated. For UEs that support low-latency high-reliability services or IP Multimedia Multimedia Subsystem (IMS) services, since low-latency high-reliability services and IMS services are delay-sensitive services, in order to reduce delay-sensitivity The delay of service recovery. When the UE enters the connected state from the idle state, even if there is no uplink or downlink data transmission on the PDU session serving the delay-sensitive service, the PDU session can be activated. However, in the prior art, there is no clear solution for activating a PDU session of a service delay-sensitive service when there is no uplink or downlink data transmission on the PDU session of the service delay-sensitive service.

In summary, at present, there is no clear solution on how to activate the PDU session of the service delay-sensitive business.

Summary of the Invention

The present application provides a method and a device for activating a PDU session, which are used to solve the problem in the prior art that there is currently no clear solution for how to activate a service delay sensitive service PDU session.

Based on the above problems, in a first aspect, an embodiment of the present application provides a method for activating a PDU session, including:

An Access and Mobility Management Function (AMF) entity receives a request message sent by a UE; wherein the request message is used to request activation of a PDU session of the UE;

Determining, by the AMF entity, an always on PDU session corresponding to the UE according to the request message and / or context information of the UE maintained by the AMF entity;

The AMF entity notifies a Session Management Function (SMF) entity to resume establishing a user plane connection of the always-on PDU session.

Optionally, the request message includes instruction information used to indicate activation of a PDU session; or

The request message includes a list of PDU sessions that need to be activated.

Optionally, the AMF entity determines the always-on PDU session corresponding to the UE according to the following manner:

If the request message is not only used to indicate activation of a control plane signaling connection, or the request message includes the indication information, the AMF entity uses the always-on PDU session recorded in the context information of the UE as An always-on PDU session corresponding to the UE;

If the activation request message includes the list of PDU sessions that need to be activated, the AMF entity adds the always-on PDU sessions in the list of always-on PDU sessions and recorded in the context information of the UE, As an always-on PDU session corresponding to the UE.

Optionally, the method further includes:

The AMF entity refuses to activate the always-on PDU session in the list of PDU sessions that need to be activated, which is not recorded in the context information of the UE, and notifies the UE of the refused to-activate always-on PDU session.

Optionally, before the AMF entity receives the request message sent by the UE, the method further includes:

During the establishment of the PDU session of the UE, the AMF entity determines that the PDU session established for the UE is an always-on PDU session;

The AMF entity records the determined always-on PDU session in the context information of the UE.

Optionally, the AMF entity determines that the PDU session established for the UE is an always-on PDU session according to the following manner:

The AMF entity determines that the PDU session established for the UE is an always-on PDU session according to the subscription information of the UE and the PDU session establishment request message sent by the UE during the PDU session establishment process; or

After receiving the indication sent by the SMF entity, the AMF entity determines that the PDU session established for the UE is an always-on PDU session.

Optionally, the indication sent by the SMF entity is at least one of a session management policy sent by the SMF entity according to a locally configured network policy, a Policy Control Function (PCF) entity, and subscription information of the UE, And the PDU session establishment request message, it is determined that the PDU session established for the UE is sent after the always-on PDU session.

In a second aspect, an embodiment of the present application provides a method for activating an always-on PDU session. The method includes:

The SMF entity receives a notification from the AMF entity, where the notification is that the AMF entity determines that the UE is always online according to a request message sent by the UE and / or context information of the UE maintained by the AMF entity Sent after a PDU session;

The SMF entity resumes establishing a user plane connection of the always-on PDU session.

Optionally, before the SMF entity receives the notification from the AMF entity, the method further includes:

During the PDU session establishment process of the UE, the SMF entity determines that the PDU session established for the UE is an always-on PDU session;

The SMF entity records the always-on PDU session in the context information of the UE, and sends an indication to the AMF entity that the PDU session established for the UE is always-on PDU session.

Optionally, the SMF entity determines that the PDU session established for the UE is an always-on PDU session according to the following manner:

The SMF entity is based on at least one of a locally configured network policy, a session management policy sent by a PCF entity, the UE's subscription information, and a PDU session establishment request message sent by the UE during the PDU session establishment process, It is determined that the PDU session established for the UE is an always-on PDU session.

In a third aspect, an embodiment of the present application provides a method for activating an always-on PDU session. The method includes:

The UE determines that a PDU session needs to be activated;

Sending, by the UE, a request message for requesting activation of a PDU session to the AMF entity, so that the AMF entity determines an always-on PDU session corresponding to the UE after receiving the request message, and notifies an SMF entity to resume establishment A user plane connection of the always-on PDU session.

The request message includes a list of PDU sessions that need to be activated.

Optionally, the sending, by the UE, a request message for requesting activation of a PDU session to the AMF entity includes:

During the service request process, the UE sends a request message to the AMF entity for requesting activation of a PDU session; or

During the registration update process, the UE sends a request message for requesting activation of a PDU session to the AMF entity.

In a fourth aspect, an embodiment of the present application provides an access and mobility management AMF entity, including: a processor and a memory;

The processor is configured to read a program in the memory and execute:

Receiving a request message sent by a UE; wherein the request message is used to request activation of a PDU session of the UE;

Determining, according to the request message and / or the context information of the UE maintained by the AMF entity, an always-on PDU session corresponding to the UE;

The SMF entity is notified to resume the establishment of the user plane connection of the always-on PDU session.

The request message includes a list of PDU sessions that need to be activated.

Optionally, the processor is specifically configured to:

If the request message is not only used to indicate activation of a control plane signaling connection, or the request message includes the indication information, the always-on PDU session recorded in the context information of the UE is used as the UE corresponding Always-on PDU session;

If the activation request message includes the list of PDU sessions that need to be activated, the always-on PDU session in the list of always-on PDU sessions and recorded in the context information of the UE is used as the UE The corresponding always-on PDU session.

Optionally, the processor is further configured to:

Refusing to activate the always-on PDU session in the list of PDU sessions that need to be activated, which is not recorded in the context information of the UE, and notifying the UE of the refused to activate always-on PDU session.

Optionally, the processor is further configured to:

Before receiving the request message sent by the UE, during the PDU session establishment process of the UE, determining that the PDU session established for the UE is an always-on PDU session;

Record the determined always-on PDU session in the context information of the UE.

Optionally, the processor is specifically configured to:

The PDU session established for the UE is determined to be an always-on PDU session according to the following manner:

Determining, according to the subscription information of the UE and the PDU session establishment request message sent by the UE during the PDU session establishment process, that the PDU session established for the UE is an always-on PDU session; or

After receiving the indication sent by the SMF entity, it is determined that the PDU session established for the UE is an always-on PDU session.

Optionally, the indication sent by the SMF entity is at least one of an SMF entity's locally configured network policy, a session management policy sent by the PCF entity, the UE's subscription information, and the PDU session establishment request message, It is determined that the PDU session established for the UE is sent after the always-on PDU session.

In a fifth aspect, an embodiment of the present application provides a session management function SMF entity, including a processor and a memory;

The processor is configured to read a program in the memory and execute:

Receiving a notification from an AMF entity; wherein the notification is that the AMF entity determines an always-on PDU session corresponding to the UE according to a request message sent by the UE and / or context information of the UE maintained by the AMF entity Sent later

Resume the user plane connection establishing the always-on PDU session.

Optionally, the processor is further configured to:

Before receiving the notification from the AMF entity, during the PDU session establishment process of the UE, determining that the PDU session established for the UE is an always-on PDU session;

Record the always-on PDU session in the context information of the UE, and send an indication to the AMF entity that the PDU session established for the UE is always-on PDU session.

Optionally, the processor is specifically configured to:

And determining, according to at least one of a locally configured network policy, a session management policy sent by a PCF entity, the UE's subscription information, and a PDU session establishment request message sent by the UE during the PDU session establishment process, The PDU session established by the UE is an always-on PDU session.

In a sixth aspect, an embodiment of the present application provides a user equipment UE, including: a processor and a memory;

The processor is configured to read a program in the memory and execute:

Determine that a PDU session needs to be activated;

Sending a request message to the AMF entity for requesting activation of a PDU session, so that the AMF entity determines the always-on PDU session corresponding to the UE after receiving the request message, and notifies the SMF entity to resume establishing the User plane connection for online PDU session.

The request message includes a list of PDU sessions that need to be activated.

Optionally, the processor is specifically configured to:

Sending a request message for requesting activation of a PDU session to the AMF entity during the service request process; or

During the registration update process, a request message for requesting activation of a PDU session is sent to the AMF entity.

In a seventh aspect, an embodiment of the present application provides an access and mobility management AMF entity, including:

A first receiving module, configured to receive a request message sent by a UE; wherein the request message is used to request activation of a PDU session of the UE;

A first determining module, configured to determine an always-on PDU session corresponding to the UE according to the request message and / or context information of the UE maintained by the AMF entity;

A notification module, configured to notify an SMF entity to resume the establishment of the user plane connection of the always-on PDU session.

In an eighth aspect, an embodiment of the present application provides a session management function SMF entity, including:

A second receiving module, configured to receive a notification from an AMF entity; wherein the notification is to determine, in the AMF entity, the request message sent by the UE and / or the context information of the UE maintained by the AMF entity; Sent after the corresponding always-on PDU session of the UE;

A processing module, configured to restore a user plane connection for establishing the always-on PDU session.

In a ninth aspect, an embodiment of the present application provides a user equipment UE, including:

A second determining module, configured to determine that a PDU session needs to be activated;

A sending module, configured to send a request message for requesting activation of a PDU session to the AMF entity, so that the AMF entity determines the always-on PDU session corresponding to the UE after receiving the request message, and notifies the SMF entity Resume the user plane connection establishing the always-on PDU session.

According to a tenth aspect, an embodiment of the present application provides a computer-storable medium having stored thereon a computer program that, when executed by a processor, implements the steps of the method according to any one of the first aspects, or any one of the second aspects. The steps of the method, or the steps of the method of any of the third aspects.

In the embodiment of the present application, after receiving the request message, the AMF entity determines the always-on PDU session corresponding to the UE according to the request message and / or the context information of the UE, and notifies the SMF entity to resume the user plane connection of the always-on PDU session; When the UE needs to transmit uplink and downlink data on the always-on PDU session, it does not need to re-request to establish a user plane connection of the PDU session, so it can reduce the delay and further improve system performance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;

2 is a schematic structural diagram of an active PDU session system according to an embodiment of the present application;

3 is a flowchart of determining whether a PDU session is an always-on PDU session by a first SMF entity according to an embodiment of the present application;

4 is a flowchart of determining whether a PDU session is an always-on PDU session by a second SMF entity according to an embodiment of the present application;

5 is a flowchart of activating a PDU session according to a first embodiment of the present application;

FIG. 6 is a flowchart of activating a PDU session according to a second embodiment of the present application; FIG.

7 is a schematic structural diagram of a first AMF entity according to an embodiment of the present application;

8 is a schematic structural diagram of a first SMF entity according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a first UE according to an embodiment of the present application; FIG.

10 is a schematic structural diagram of a second AMF entity according to an embodiment of the present application;

11 is a schematic structural diagram of a second SMF entity according to an embodiment of the present application;

12 is a schematic structural diagram of a second UE according to an embodiment of the present application;

13 is a flowchart of a first method for activating a PDU session according to an embodiment of the present application;

14 is a flowchart of a second method for activating a PDU session according to an embodiment of the present application;

FIG. 15 is a flowchart of a third method for activating a PDU session according to an embodiment of the present application.

detailed description

In order to make the purpose, technical solution, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The present application will be further described in detail below with reference to the accompanying drawings.

FIG. 1 exemplarily illustrates a system architecture diagram applicable to an embodiment of the present application. As shown in FIG. 1, in a future 5G system architecture, a terminal 101 may communicate with a core network via an access network entity 102, and the terminal It may refer to UE, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing (PDA), and wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in future 5G networks, etc. In FIG. 1, for convenience of description, only one terminal is exemplified. In an actual network, multiple terminals may coexist, and details are not described herein again.

Access network (AN) entity 102, the access network entity may also be referred to as a radio access network ((Radio) Access network (R) AN) entity, hereinafter collectively referred to as the access network entity or (R) The AN entity is mainly responsible for providing a wireless connection for the terminal 101 and ensuring reliable transmission of uplink and downlink data of the terminal 101. The access network entity 102 may be a base station (generation NodeB, gNB) in a 5G system, and may be a Global System for Mobile Communication (GSM) system or a Code Division Multiple Access (CDMA) system. The base station (Base Transceiver Station, BTS) can also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or a Long Term Evolution (LTE) system. Evolution base station (Evolutionary NodeB, eNB or eNodeB), etc.

A Session Management Function (SMF) entity 103, which can be used to perform some functions of a Mobility Management Entity (MME) in the LTE system, and is mainly responsible for establishing a session for the terminal 101 and managing the session. A suitable User Plane Function (UPF) entity may be selected for the terminal 101 according to the location information of the terminal 101.

The user plane functional entity 104 is a functional network element of the user plane of the terminal 101, and its main functions include packet routing and forwarding, and quality of service (QoS) processing of user plane data.

Access and Mobility Management Function (AMF) entity 105, whose main functions include the termination point of the radio access network control plane, the termination point of non-access signaling, mobility management, legal monitoring, access Authorization or authentication, etc.

The Policy Control Function (Funion, PCF) entity 106 is mainly responsible for the functions of establishing, releasing, and changing user plane transmission paths.

Authentication Server Function (AUSF) entity 107, whose main functions include user authentication and the like.

The User Data Management (UDM) entity 108 is mainly responsible for managing the user's subscription data and the like.

The data network (Data Network, DN) 109 may refer to a network that provides services to the terminal 101. For example, some DNs may provide the terminal 101 with Internet access functions, and some DNs may provide the terminal 101 with MMS functions.

It should be noted that the system architecture described above is only an example of a system architecture applicable to the embodiment of the present application. The system architecture applicable to the embodiment of the present application may add other entities or reduce some entities compared to the system architecture shown in FIG. 1.

A PDU session is a connection between a terminal and a DN and provides PDU connectivity services. The terminal can establish multiple PDU sessions to connect to the same DN or different DNs. Terminals can also establish PDU sessions served by different UPFs to connect to the same DN.

The states of a PDU session include at least an active state (inactive or de-activated).

Among them, the active state refers to the state in which the user plane resources of the PDU session have been established. An end-to-end connection is established between the terminal and the DN, and data can be transmitted through the PDU session. The inactive state means that only part of the user plane resources are reserved in the PDU session, but the user plane air interface resources between the terminal and the (R) AN entity, and the connection between the (R) AN entity and the UPF entity are not established. The terminal and Data cannot be transmitted between DNs, but some information of the PDU session is still retained in the SMF entity and the UPF entity.

When the UE is in an idle state, the state of the PDU session established for the UE is inactive; when the UE has uplink or downlink data transmission, the PDU session of the UE is activated. However, for delay-sensitive services, if each time a delay-sensitive service data needs to be transmitted, reactivating a PDU session serving the service will increase the delay; therefore, the embodiment of the present application proposes The PDU session of the service is set to always PDU session, that is, the PDU session is activated regardless of whether there is uplink or downlink data to be transmitted on the PDU session, so that when data of delay-sensitive services needs to be transmitted, it can be The time delay is greatly reduced. Specifically, the UE sends a request to the network side to request the network side to activate the always-on PDU session.

In the embodiment of the present application, an always-on PDU session is a PDU session in which a UE that enters a connected state always maintains a user plane connection during a life cycle of the PDU session.

For always-on PDU sessions, SMF entities and UPF entities can implement independent charging policies.

With reference to the foregoing description, as shown in FIG. 2, a system for activating a PDU session according to an embodiment of the present application includes a UE 20, an AMF entity 21, and an SMF entity 22;

The UE 20 is used to determine that a PDU session needs to be activated. A request message for requesting activation of a PDU session is sent to the AMF entity, so that the AMF entity determines the permanent corresponding to the UE after receiving the request message. An online PDU session, and notifying the SMF entity to resume the user plane connection establishing the always-on PDU session.

AMF entity 21 is configured to receive a request message sent by UE 20; wherein the request message is used to request activation of a PDU session of the UE; and according to the request message and / or the context of the UE maintained by the AMF entity Information to determine the always-on PDU session corresponding to the UE; and notify the SMF entity to resume the establishment of the user-plane connection of the always-on PDU session.

The SMF entity 22 is configured to receive a notification from the AMF entity, where the notification is to determine the UE according to a request message sent by the UE and / or context information of the UE maintained by the AMF entity. Sent after the corresponding always-on PDU session; resuming the user plane connection establishing the always-on PDU session.

In implementation, the UE may send a request message to the AMF entity at the following timings:

1. During the service request process, the UE sends a request message to the AMF entity for requesting activation of a PDU session.

It should be noted that when there is uplink data to be sent on one or more PDU sessions of the UE, the UE will initiate a Service Request process;

The request message sent by the UE to the AMF entity during the service request process is a service request message.

2. During the registration update process, the UE sends a request message to the AMF entity for requesting activation of a PDU session.

The request message sent by the UE to the AMF entity during the registration update process is a registration update request message.

What needs to be explained here is that the timing of the UE sending the request message to the AMF entity is not limited to the above two. In this embodiment, after determining that the PDU session needs to be activated, the UE may also send the AMF entity to request the activation of the PDU session in other ways. Request message.

The request message includes instruction information for instructing activation of a PDU session; or

The request message includes a list of PDU sessions that need to be activated.

In an optional manner, when the UE sending request message includes a list of PDU sessions that need to be activated, the PDU session list only includes PDU sessions without uplink data transmission;

When the UE sends a request message to the AMF entity during the service request process, it also needs to request the AMF to activate a PDU session with uplink data transmission. At this time, the UE also needs to send a list of PDU sessions with uplink data transmission to the AMF entity.

After receiving the request message sent by the UE, the AMF entity determines the always-on PDU session corresponding to the UE according to the indication information in the request message or the list of PDU sessions that need to be activated;

In implementation, the AMF entity determines the always-on PDU session corresponding to the UE according to the request message and / or the context information of the UE maintained by the AMF entity;

Specifically, if the request message sent by the UE includes indication information used to indicate activation of a PDU session, the AMF entity determines the always-on PDU session corresponding to the UE according to the context information of the UE maintained;

If the request message sent by the UE includes a list of PDU sessions that need to be activated, the AMF entity determines the always-on PDU session corresponding to the UE according to the list of PDU sessions that need to be activated and the context information of the UE maintained by the AMF entity.

When the AMF entity determines the always-on PDU session corresponding to the UE according to the context information of the UE, it determines the always-on PDU session corresponding to the UE according to the always-on PDU session recorded in the context of the UE.

In the embodiment of the present application, after determining the always-on PDU session corresponding to the UE, the AMF entity notifies the SMF entity to resume the establishment of the user-plane connection corresponding to the always-on PDU session of the UE;

It should be noted here that the always-on PDU session corresponding to the UE determined by the AMF entity is the always-on PDU session determined by the AMF entity to be allowed to be activated; when the AMF entity determines the always-on PDU session that is allowed to be activated, it needs to be based on the mobility restriction information To determine whether the UE's PDU session is an always-on PDU session that is allowed to be activated; for example, the mobility restriction information is whether the UE has entered a non-allowed area. When the UE enters a non-allowed area, the UE's PDU session cannot be activated.

In the embodiment of the present application, the AMF entity maintains the context information of the UE; and, during the process of establishing the PDU session, the AMF entity determines whether the PDU session is an always-on PDU session, and if so, records the always-on PDU session in the UE. Context information.

The method for determining the always-on PDU session recorded in the UE context information by the AMF entity in the embodiment of the present application is described in detail below.

Optionally, in the process of establishing the PDU session of the UE, the AMF entity determines that the PDU session established for the UE is an always-on PDU session; the AMF entity records the determined always-on PDU session in The context information of the UE.

For any PDU session established for the UE, during the establishment of the PDU session, the AMF entity determines whether the PDU session is an always-on PDU session. If so, the AMF entity marks the PDU session as permanent in the context information of the UE. Online PDU session.

Specifically, the embodiments of the present application provide several ways for the AMF entity to determine whether a PDU session established for the UE is an always-on PDU session, which will be described separately below.

Method 1: The AMF entity determines that the PDU session established for the UE is an always-on PDU session according to the subscription information of the UE and the PDU session establishment request message sent by the UE during the PDU session establishment process.

The subscription information of the UE includes single network slice selection information (Single Network Selection Assistant Information (S-NSSAI)) and / or DNN information;

In the process of establishing a PDU session for the UE, the S-NSSAI and / or DNN information in the subscription information needs to be used to establish the PDU session;

In addition, for any PDU session established for the UE, whether or not the PDU session is an always-on PDU session is displayed or indicated in the S-NSSAI and / or DNN information used to establish the PDU session.

During the process of the UE registering with the network, the AMF entity obtains the subscription information of the UE, where the obtained subscription information includes S-NSSAI and / or DNN information;

During the PDU session establishment process, the S-NSSAI and / or DNN information included in the UE's subscription information is used to establish a PDU session for the UE.

When the AMF entity determines whether the PDU session established for the UE is an always-on PDU session, the AMF entity determines whether the PDU session is an always-on PDU session according to the S-NSSAI and / or DNN information used to establish the PDU session;

If the AMF entity determines that the PDU session established for the UE is an always-on PDU session, the AMF entity records the PDU session as an always-on PDU session in the context information of the UE maintained by itself.

Manner 2: The AMF entity receives the instruction sent by the SMF entity, and determines that the PDU session established for the UE is an always-on PDU session.

In the second method, the indication sent by the SMF entity to the AMF entity is sent to the AMF entity after the SMF entity determines that the PDU session established for the UE is an always-on PDU session.

It should be noted that in the second method, the SMF entity determines whether the PDU session established for the UE is an always-on PDU session.

Optionally, the indication sent by the SMF entity is determined by the SMF entity according to at least one of a locally configured network policy, a session management policy sent by the PCF entity, the UE's subscription information, and the PDU session establishment request message, as The PDU session established by the UE is sent after the always-on PDU session.

In the embodiment of the present application, the SMF entity may determine whether the PDU session established for the UE is an always-on PDU session in the following ways:

Method 1: The SMF entity determines whether the PDU session established for the UE is an always-on PDU session according to the subscription information of the UE and the PDU session establishment request message.

The UE subscription information includes S-NSSAI and / or DNN information;

During the PDU session establishment process, the S-NSSAI and / or DNN information included in the UE's subscription information is used to establish a PDU session for the UE; and, when the SMF entity performs a session management subscription check, the UE's subscription information can be obtained from the UDM entity , Wherein the obtained contract information includes S-NSSAI and / or DNN information;

The SMF entity determines whether the PDU session is an always-on PDU session according to the UE's subscription information and a PDU session establishment request message;

If the SMF entity determines that the PDU session established for the UE is an always-on PDU session, the SMF entity records the PDU session as an always-on PDU session in the context information of the UE maintained by the SMF entity.

After determining that the PDU session is an always-on PDU session, the SMF entity sends an instruction to the AMF entity to notify the AMF entity that the PDU session is an always-on PDU session.

As shown in FIG. 3, a flowchart of a first SMF entity determining whether a PDU session established for a UE is an always-on PDU session in the embodiment of the present application.

Step 301: The UE sends a PDU session establishment request message to the AMF entity.

Step 302: The AMF entity forwards the PDU session establishment request message sent by the UE to the SMF entity.

Step 303: The SMF entity obtains the subscription information of the UE from the UDM entity.

The UE subscription information includes S-NSSAI and / or DNN information;

Step 304: The SMF entity determines whether the PDU session established for the UE is an always-on PDU session according to the PDU session establishment request message and the subscription information of the UE.

Step 305: The SMF entity sends an indication to the AMF entity that the PDU session established for the UE is an always-on PDU session.

It should be noted here that in step 305, the SMF entity sends an indication to the AMF entity to indicate that the PDU session established for the UE is an always-on PDU session. In addition, the SMF entity may also determine When the PDU session established for the UE is not an always-on PDU session, an indication is also sent to the AMF entity to notify that the PDU session established for the UE is not an always-on PDU session;

Step 306: In the context information of the UE, the AMF entity records that the PDU session established for the UE is an always-on PDU session.

Method 2: The SMF entity determines whether the PDU session established for the UE is an always-on PDU session according to the session management policy and the PDU session establishment request message sent by the PCF entity.

During the PDU session establishment process, an association is established between the SMF entity and the PCF entity; the PCF entity determines whether the PDU session established for the UE is an always-on PDU session; the PCF entity determines that the PDU session established for the UE is an always-on PDU session Then, a session management policy is sent to the SMF entity, and the session management policy is used to indicate that the PDU session established for the UE is an always-on PDU session.

Specifically, the PCF entity determines that the PDU session established for the UE is an always-on PDU session according to some or all of the following information:

Operator policy, UE subscription information, UE auxiliary information;

The auxiliary information of the UE includes, but is not limited to, UE preferences and UE setting information.

After the SMF entity determines that the PDU session is an always-on PDU session according to the session management policy and the PDU session establishment request message sent by the PCF entity, it sends an indication to the AMF entity to notify the AMF entity that the PDU session is always-on PDU session.

As shown in FIG. 4, a flowchart of determining whether the PDU session established for the UE by the second SMF entity in the embodiment of the present application is an always-on PDU session.

Step 401: The UE sends a PDU session establishment request message to the AMF entity.

Step 402: The AMF entity forwards the PDU session establishment request message sent by the UE to the SMF entity.

Step 403: Establish an association between the SMF entity and the PCF entity;

Step 404: The PCF entity determines that the PDU session established for the UE is an always-on PDU session.

Step 405: The PCF entity sends a session management policy to the SMF entity according to the judgment result.

The session management policy is used to indicate whether the PDU session established for the UE is an always-on PDU session;

Step 406: The SMF entity determines whether the PDU session established for the UE is an always-on PDU session according to the session management policy and the PDU session establishment request message sent by the PCF entity.

It should be noted that, when the PCF entity determines that the PDU session established for the UE is an always-on PDU session, the PCF entity sends a session management policy indicating that the PDU session established for the UE is always-on PDU session to the SMF entity so that After receiving the session management policy sent by the PCF entity, the SMF entity determines whether the PDU session established for the UE is an always-on PDU session according to the session management policy and the PDU session establishment request message;

Step 407: The SMF entity sends an indication to the AMF entity that the PDU session established for the UE is an always-on PDU session.

It should be noted here that in step 407, the SMF entity sends an indication to the AMF entity to indicate that the PDU session established for the UE is an always-on PDU session. In addition, the SMF entity may also determine When the PDU session established for the UE is not an always-on PDU session, an indication is also sent to the AMF entity to notify that the PDU session established for the UE is not an always-on PDU session;

Step 408: In the context information of the UE, the AMF entity records that the PDU session established for the UE is an always-on PDU session.

Method 3: The SMF entity determines whether the PDU session established for the UE is an always-on PDU session according to a locally configured network policy.

If the SMF entity determines that the PDU session established for the UE is an always-on PDU session according to the locally configured network policy, the SMF entity records the PDU session as an always-on PDU session in the context information of the UE maintained by itself.

It should be noted here that the manner in which the above-mentioned AMF entity determines that the PDU session established for the UE is an always-on PDU session is only an optional manner in the embodiment of the present application. In the embodiment of the present application, the AMF entity may also determine as The PDU session established by the UE is an always-on PDU session.

In addition, during the process of establishing a PDU session for the UE, the AMF entity determines the always-on PDU session corresponding to the UE, and records the PDU session established for the UE in the context information of the UE.

After the AMF receives the request message of the UE, according to the request message of the UE and / or the context information of the UE, when determining the always-on PDU session corresponding to the UE, different methods are used to determine the always-on PDU corresponding to the UE for different request messages. Conversation. Each is described below.

Case 1: If the request message is not only used to indicate activation of the control plane signaling connection.

In this case, the AMF determines the always-on PDU session corresponding to the UE according to the following methods:

The AMF entity uses the always-on PDU session recorded in the context information of the UE as the always-on PDU session corresponding to the UE.

For example, suppose that the always-on PDU sessions recorded in the context information of the UE maintained by the AMF entity are: PDU session 1, PDU session 3, and PDU session 4. After the AMF entity receives the request message from the UE, if it is determined that the request message is not only Used to indicate activation of a control plane signaling connection, the AMF entity uses the always-on PDU session recorded in the UE's context information: PDU session 1, PDU session 3, and PDU session 4 as the always-on PDU session corresponding to the UE.

In the second case, the request message includes instruction information for instructing activation of a PDU session.

It should be noted that, in this case, the request message sent by the UE to the AMF entity does not specify the PDU session to be activated; after the AMF entity receives the request message containing only the indication information, the AMF entity maintains the UE maintained by itself. All the always-on PDU sessions recorded in the context information of the UE are always the always-on PDU sessions corresponding to the UE.

For example, it is assumed that the always-on PDU session recorded in the context information of the UE maintained by the AMF entity is: PDU session 1, PDU session 2, PDU session 4; after the AMF entity receives the request message of the UE, if it is determined that the request message contains The indication information used to indicate activation of the always-on PDU session, the AMF entity uses the always-on PDU session recorded in the context information of the UE: PDU session 1, PDU session 2, and PDU session 4 as the always-on PDU session corresponding to the UE.

Scenario 3: The request message contains a list of PDU sessions that need to be activated.

The AMF entity uses the always-on PDU session in the list of PDU sessions that need to be activated and recorded in the context information of the UE as the always-on PDU session corresponding to the UE.

In this case, the AMF entity includes a list of PDU sessions that the UE requests to activate in the request message sent by the UE. The AMF entity selects the PDU sessions included in the PDU session list and the PDU sessions included in the context information of the UE. The intersection is used as the always-on PDU session corresponding to the UE.

For example, it is assumed that the always-on PDU sessions recorded in the context information of the UE maintained by the AMF entity are: PDU session 1, PDU session 2; the list of PDU sessions that need to be included in the request message received by the AMF entity from the UE is: PDU session 2. For PDU session 3 and PDU session 4, the always-on PDU session recorded in the UE's context information and the intersection of PDU session 2 and the PDU session in the list of PDU sessions that need to be activated are used as the always-on PDU session corresponding to the UE.

In addition, the AMF entity refuses to activate the always-on PDU session in the list of PDU sessions that needs to be activated, which is not recorded in the context information of the UE, and notifies the UE of the refused to-activate always-on PDU session.

For example, it is assumed that the always-on PDU sessions recorded in the context information of the UE maintained by the AMF entity are: PDU session 1, PDU session 2; the list of PDU sessions that need to be included in the request message received by the AMF entity from the UE is: PDU session 2. PDU session 3 and PDU session 4. Because the PDU session 3 and PDU session 4 included in the list of PDU sessions to be activated are not recorded in the context information of the UE, the AMF entity refuses to activate PDU session 3 and PDU session 4; The UE is notified of the PDU session 3 and the PDU session 4 that are not activated.

Alternatively, the AMF entity only determines the always-on PDU session corresponding to the UE according to the context information of the UE; specifically, after receiving the request message sent by the UE, the AMF entity uses the always-on PDU session recorded in the context information of the UE as the corresponding UE Always online PDU session.

The following describes a method for activating a PDU session in a specific embodiment.

As shown in FIG. 5, a first flowchart of activating a PDU session according to an embodiment of the present application; the description is made by taking an example in which a request message includes instruction information for instructing activation of a PDU session.

Step 501: The UE sends a request message to the AMF entity.

Step 502: The AMF entity uses the always-on PDU session recorded in the context information of the UE as the always-on PDU session corresponding to the UE.

Step 503: The AMF entity notifies the SMF entity to resume the establishment of the user plane connection corresponding to the UE's always-on PDU session.

As shown in FIG. 6, a second flowchart of activating a PDU session according to an embodiment of the present application; it is described by using a request message including a list of PDU sessions that need to be activated as an example.

Step 601: The UE sends a request message to the AMF entity.

Step 602: The AMF entity uses the always-on PDU session in the list of always-on PDU sessions and recorded in the context information of the UE as the always-on PDU session corresponding to the UE;

Step 603: The AMF entity notifies the SMF entity to resume the establishment of the user plane connection of the always-on PDU session corresponding to the UE.

As shown in FIG. 7, the first type of access and mobility management AMF entity in this embodiment of the present application includes a processor 700, a memory 701, and a bus interface.

The processor 700 is responsible for managing the bus architecture and general processing, and the memory 701 may store data used by the processor 700 when performing operations. The bus architecture may include any number of interconnected buses and bridges, and is specifically linked by various circuits of one or more processors 700 and one or more memories 701. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein. The bus interface provides an interface. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 701 may store data used by the processor 700 when performing operations.

The processes disclosed in the embodiments of the present application may be applied to the processor 700, or implemented by the processor 700. In the implementation process, each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 700 or an instruction in the form of software. The processor 700 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the embodiments in this application. The disclosed methods, steps and logical block diagrams. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in the memory 701, and the processor 700 reads the information in the memory 701 and completes the steps of the signal processing flow in combination with its hardware.

Specifically, the processor 700 is configured to read a program in the memory 701 and execute:

The request message includes a list of PDU sessions that need to be activated.

Optionally, the processor 700 is specifically configured to:

If the request message is not only used to indicate activation of a control plane signaling connection, or the request message includes the indication information, the always-on PDU session recorded in the context information of the UE is used as the always-on PDU session corresponding to the UE Online PDU session;

If the activation request message includes the list of PDU sessions that need to be activated, the always-on PDU session in the list of always-on PDU sessions and recorded in the context information of the UE is taken as the corresponding UE Always online PDU session.

Optionally, the processor 700 is further configured to:

Optionally, the processor 700 is specifically configured to:

As shown in FIG. 8, the first session management function SMF entity in this embodiment of the present application includes a processor 800, a memory 801, and a bus interface.

The processor 800 is responsible for managing the bus architecture and general processing, and the memory 801 may store data used by the processor 800 when performing operations. The bus architecture may include any number of interconnected buses and bridges, and is specifically linked by various circuits of one or more processors 800 and one or more memories 801. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein. The bus interface provides an interface. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 801 may store data used by the processor 800 when performing operations.

The processes disclosed in the embodiments of the present application may be applied to the processor 800 or implemented by the processor 800. In the implementation process, each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 800 or an instruction in the form of software. The processor 800 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the embodiments in this application. The disclosed methods, steps and logical block diagrams. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in the memory 801, and the processor 800 reads the information in the memory 801 and completes the steps of the signal processing flow in combination with its hardware.

Specifically, the processor 800 is configured to read a program in the memory 801 and execute:

Resume the user plane connection establishing the always-on PDU session.

Optionally, the processor 800 is further configured to:

Optionally, the processor 800 is specifically configured to:

As shown in FIG. 9, the first type of user equipment UE in this embodiment of the present application includes a processor 900, a memory 901, a transceiver 902, and a bus interface.

The processor 900 is responsible for managing the bus architecture and general processing, and the memory 901 may store data used by the processor 900 when performing operations. The transceiver 902 is configured to receive and transmit data under the control of the processor 900.

The bus architecture may include any number of interconnected buses and bridges, and one or more processors specifically represented by the processor 900 and various circuits of the memory represented by the memory 901 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein. The bus interface provides an interface. The processor 900 is responsible for managing the bus architecture and general processing, and the memory 901 may store data used by the processor 900 when performing operations.

The processes disclosed in the embodiments of the present application may be applied to the processor 900 or implemented by the processor 900. In the implementation process, each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 900 or an instruction in the form of software. The processor 900 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the embodiments in this application. The disclosed methods, steps and logical block diagrams. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in the memory 901, and the processor 900 reads the information in the memory 901 and completes the steps of the signal processing flow in combination with its hardware.

Specifically, the processor 900 is configured to read a program in the memory 901 and execute:

Determine that a PDU session needs to be activated;

The request message includes a list of PDU sessions that need to be activated.

Optionally, the processor 900 is specifically configured to:

As shown in FIG. 10, the second AMF entity in this embodiment of the present application includes:

A first receiving module 1001, configured to receive a request message sent by a UE; wherein the request message is used to request activation of a PDU session of the UE;

A first determining module 1002, configured to determine an always-on PDU session corresponding to the UE according to the request message and / or the context information of the UE maintained by the AMF entity;

A notification module 1003 is configured to notify an SMF entity to resume the user plane connection establishing the always-on PDU session.

The request message includes a list of PDU sessions that need to be activated.

Optionally, the first determining module 1002 is specifically configured to:

The always-on PDU session corresponding to the UE is determined according to the following manner:

Optionally, the first determining module 1002 is further configured to:

Optionally, the first receiving module 1001 is further configured to:

Before receiving the request message sent by the UE, during the PDU session establishment process of the UE, it is determined that the PDU session established for the UE is an always-on PDU session; and the determined always-on PDU session is recorded in the UE Context information.

Optionally, the first determining module 1002 is specifically configured to:

As shown in FIG. 11, the second SMF entity in this embodiment of the present application includes:

The second receiving module 1101 is configured to receive a notification from an AMF entity, where the notification is to determine the address of the UE according to a request message sent by the UE and / or context information of the UE maintained by the AMF entity. The following description is sent after the always-on PDU session corresponding to the UE;

The processing module 1102 is configured to recover a user plane connection for establishing the always-on PDU session.

Optionally, the second receiving module 1101 is further configured to:

Before receiving the notification from the AMF entity, during the PDU session establishment process of the UE, determining that the PDU session established for the UE is an always-on PDU session; recording the always-on PDU session in context information of the UE, And sending an indication to the AMF entity that the PDU session established for the UE is an always-on PDU session.

Optionally, the second receiving module 1101 is specifically configured to:

As shown in FIG. 12, the second UE in this embodiment of the present application includes:

A second determining module 1201, configured to determine that a PDU session needs to be activated;

A sending module 1202 is configured to send a request message for requesting activation of a PDU session to the AMF entity, so that the AMF entity determines the always-on PDU session corresponding to the UE after receiving the request message, and notifies the SMF The entity resumes establishing a user plane connection of the always-on PDU session.

The request message includes a list of PDU sessions that need to be activated.

Optionally, the sending module 1202 is specifically configured to:

An embodiment of the present application further provides a computer-storable medium on which a computer program is stored. When the program is executed by a processor, the steps of the foregoing AMF entity in the embodiment of the present application, or the steps of the SMF entity in the embodiment of the present application, Or the steps of the UE described in the embodiments of this application.

Based on the same inventive concept, an embodiment of the present application also provides a first method for activating a PDU session, because a device corresponding to the method is an AMF entity in a system for activating a PDU session according to the embodiment of the present application, and the principle of the method to solve the problem Similar to this device, the implementation of this method can refer to the implementation of the device.

As shown in FIG. 13, the first method for activating a PDU session in the embodiment of the present application includes:

Step 1301: The AMF entity receives a request message sent by the UE; wherein the request message is used to request activation of a PDU session of the UE;

Step 1302: The AMF entity determines an always-on PDU session corresponding to the UE according to the request message and / or the context information of the UE maintained by the AMF entity.

Step 1303: The AMF entity notifies the SMF entity to resume establishing a user plane connection of the always-on PDU session.

The request message includes a list of PDU sessions that need to be activated.

If the request message is not only used to indicate activation of a control plane signaling connection, or the request message includes the indication information, the AMF entity uses the always-on PDU session recorded in the context information of the UE as Always-on PDU session corresponding to UE;

Optionally, the method further includes:

Based on the same inventive concept, the embodiment of the present application also provides a second method for activating a PDU session, because the device corresponding to the method is an SMF entity in the system for activating a PDU session according to the embodiment of the present application, and the principle of the method to solve the problem Similar to this device, the implementation of this method can refer to the implementation of the device.

As shown in FIG. 14, a second method for activating a PDU session in this embodiment of the present application includes:

Step 1401: The SMF entity receives a notification from the AMF entity, where the notification is that the AMF entity determines that the UE corresponds to the request message sent by the UE and / or the context information of the UE maintained by the AMF entity. Sent after an always-on PDU session;

Step 1402: The SMF entity resumes establishing a user plane connection of the always-on PDU session.

Based on the same inventive concept, a third method for activating a PDU session is also provided in the embodiment of the present application, because the device corresponding to the method is a UE in the system for activating a PDU session in the embodiment of the present application, and the principle and method of solving the problem This device is similar, so the implementation of this method can refer to the implementation of the device, and the duplicates will not be repeated.

As shown in FIG. 15, a third method for activating a PDU session in the embodiment of the present application includes:

Step 1501: The UE determines that a PDU session needs to be activated.

Step 1502: The UE sends a request message for requesting activation of a PDU session to the AMF entity, so that the AMF entity determines the always-on PDU session corresponding to the UE after receiving the request message, and notifies the SMF. The entity resumes establishing a user plane connection of the always-on PDU session.

The request message includes a list of PDU sessions that need to be activated.

The above describes the present application with reference to block diagrams and / or flowcharts showing methods, devices (systems) and / or computer program products according to embodiments of the present application. It should be understood that one block of the block diagrams and / or flowchart illustrations, and a combination of blocks of the block diagrams and / or flowchart illustrations can be implemented by computer program instructions. These computer program instructions may be provided to a general purpose computer, a processor of a special purpose computer, and / or other programmable data processing device to produce a machine such that the instructions executed via the computer processor and / or other programmable data processing device create A method for implementing the functions / actions specified in the block diagrams and / or flowchart blocks.

Accordingly, the application can also be implemented in hardware and / or software (including firmware, resident software, microcode, etc.). Still further, the present application may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code implemented in the medium for use by an instruction execution system or Used in conjunction with the instruction execution system. In the context of this application, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, transmit, or transfer a program for use by or in connection with an instruction execution system, apparatus, or device, Device or equipment.

Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application also intends to include these changes and variations.

Claims

A method for activating a packet data unit PDU session, wherein the method includes:

The access and mobility management function AMF entity receives a request message sent by a user equipment UE; wherein the request message is used to request activation of a PDU session of the UE;

Determining, by the AMF entity, the always-on PDU session corresponding to the UE according to the request message and / or context information of the UE maintained by the AMF entity;

The AMF entity notifies the session management function SMF entity to resume the establishment of the user plane connection of the always-on PDU session.
The method according to claim 1, wherein the request message includes instruction information for instructing activation of a PDU session; or

The request message includes a list of PDU sessions that need to be activated.
The method according to claim 1 or 2, wherein the AMF entity determines the always-on PDU session corresponding to the UE according to the following manner:

If the request message is not only used to indicate activation of a control plane signaling connection, or the request message includes the indication information, the AMF entity uses the always-on PDU session recorded in the context information of the UE as An always-on PDU session corresponding to the UE;

If the activation request message includes the list of PDU sessions that need to be activated, the AMF entity adds the always-on PDU sessions in the list of always-on PDU sessions and recorded in the context information of the UE, As an always-on PDU session corresponding to the UE.
The method of claim 3, further comprising:

The AMF entity refuses to activate the always-on PDU session in the list of PDU sessions that need to be activated, which is not recorded in the context information of the UE, and notifies the UE of the refused to-activate always-on PDU session.
The method according to claim 1, before the AMF entity receives the request message sent by the UE, further comprising:

During the establishment of the PDU session of the UE, the AMF entity determines that the PDU session established for the UE is an always-on PDU session;

The AMF entity records the determined always-on PDU session in the context information of the UE.
The method according to claim 5, wherein the AMF entity determines that a PDU session established for the UE is an always-on PDU session according to the following manner:

The AMF entity determines that the PDU session established for the UE is an always-on PDU session according to the subscription information of the UE and the PDU session establishment request message sent by the UE during the PDU session establishment process; or

The AMF entity receives the indication sent by the SMF entity, and determines that the PDU session established for the UE is an always-on PDU session.
The method according to claim 6, wherein the indication sent by the SMF entity is at least one of an SMF entity's locally configured network policy, a session management policy sent by a policy control function PCF entity, and the UE's subscription information. One type, and the PDU session establishment request message, determines that the PDU session established for the UE is sent after an always-on PDU session.
A method for activating an always-on PDU session, characterized in that the method includes:

The SMF entity receives a notification from the AMF entity, where the notification is that the AMF entity determines that the UE is always online according to a request message sent by the UE and / or context information of the UE maintained by the AMF entity Sent after a PDU session;

The SMF entity resumes establishing a user plane connection of the always-on PDU session.
The method according to claim 8, wherein before the SMF entity receives the notification from the AMF entity, further comprising:

During the PDU session establishment process of the UE, the SMF entity determines that the PDU session established for the UE is an always-on PDU session;

The SMF entity records the always-on PDU session in the context information of the UE, and sends an indication to the AMF entity that the PDU session established for the UE is always-on PDU session.
The method according to claim 9, wherein the SMF entity determines that the PDU session established for the UE is an always-on PDU session according to the following manner:

The SMF entity is based on at least one of a locally configured network policy, a session management policy sent by a PCF entity, the UE's subscription information, and a PDU session establishment request message sent by the UE during the PDU session establishment process, It is determined that the PDU session established for the UE is an always-on PDU session.
A method for activating an always-on PDU session, characterized in that the method includes:

The UE determines that a PDU session needs to be activated;

Sending, by the UE, a request message for requesting activation of a PDU session to the AMF entity, so that the AMF entity determines an always-on PDU session corresponding to the UE after receiving the request message, and notifies an SMF entity to resume establishment A user plane connection of the always-on PDU session.
The method according to claim 11, wherein the request message includes indication information for instructing activation of a PDU session; or

The request message includes a list of PDU sessions that need to be activated.
The method according to claim 11, wherein the sending, by the UE, a request message for requesting activation of a PDU session to the AMF entity comprises:

During the service request process, the UE sends a request message to the AMF entity for requesting activation of a PDU session; or

During the registration update process, the UE sends a request message for requesting activation of a PDU session to the AMF entity.
An access and mobility management AMF entity, comprising: a processor and a memory;

The processor is configured to read a program in the memory and execute:

Receiving a request message sent by a UE; wherein the request message is used to request activation of a PDU session of the UE;

Determining, according to the request message and / or the context information of the UE maintained by the AMF entity, an always-on PDU session corresponding to the UE;

The SMF entity is notified to resume the establishment of the user plane connection of the always-on PDU session.
The AMF entity according to claim 14, wherein the request message includes instruction information for instructing activation of a PDU session; or

The request message includes a list of PDU sessions that need to be activated.
The AMF entity according to claim 14 or 15, wherein the processor is specifically configured to:

If the request message is not only used to indicate activation of a control plane signaling connection, or the request message includes the indication information, the always-on PDU session recorded in the context information of the UE is used as the UE corresponding Always-on PDU session;

If the activation request message includes the list of PDU sessions that need to be activated, the always-on PDU session in the list of always-on PDU sessions and recorded in the context information of the UE is used as the UE The corresponding always-on PDU session.
The AMF entity according to claim 16, wherein the processor is further configured to:

Refusing to activate the always-on PDU session in the list of PDU sessions that need to be activated, which is not recorded in the context information of the UE, and notifying the UE of the refused to activate always-on PDU session.
The AMF entity according to claim 14, wherein the processor is further configured to:

Before receiving the request message sent by the UE, during the PDU session establishment process of the UE, determining that the PDU session established for the UE is an always-on PDU session;

Record the determined always-on PDU session in the context information of the UE.
The AMF entity according to claim 18, wherein the processor is specifically configured to:

The PDU session established for the UE is determined to be an always-on PDU session according to the following manner:

Determining, according to the subscription information of the UE and the PDU session establishment request message sent by the UE during the PDU session establishment process, that the PDU session established for the UE is an always-on PDU session; or

After receiving the indication sent by the SMF entity, it is determined that the PDU session established for the UE is an always-on PDU session.
The AMF entity according to claim 19, wherein the indication sent by the SMF entity is at least one of an SMF entity's locally configured network policy, a session management policy sent by the PCF entity, and the UE's subscription information And the PDU session establishment request message, determining that the PDU session established for the UE is sent after an always-on PDU session.
A session management function SMF entity, including: a processor and a memory;

The processor is configured to read a program in the memory and execute:

Receiving a notification from an AMF entity; wherein the notification is that the AMF entity determines an always-on PDU session corresponding to the UE according to a request message sent by the UE and / or context information of the UE maintained by the AMF entity Sent later

Resume the user plane connection establishing the always-on PDU session.
The SMF entity according to claim 21, wherein the processor is further configured to:

Before receiving the notification from the AMF entity, during the PDU session establishment process of the UE, determining that the PDU session established for the UE is an always-on PDU session;

Record the always-on PDU session in the context information of the UE, and send an indication to the AMF entity that the PDU session established for the UE is always-on PDU session.
The SMF entity according to claim 22, wherein the processor is specifically configured to:

The PDU session established for the UE is determined to be an always-on PDU session according to the following manner:

And determining, according to at least one of a locally configured network policy, a session management policy sent by a PCF entity, the UE's subscription information, and a PDU session establishment request message sent by the UE during the PDU session establishment process, The PDU session established by the UE is an always-on PDU session.
A user equipment UE, comprising: a processor and a memory;

The processor is configured to read a program in the memory and execute:

Determine that a PDU session needs to be activated;

Sending a request message to the AMF entity for requesting activation of a PDU session, so that the AMF entity determines the always-on PDU session corresponding to the UE after receiving the request message, and notifies the SMF entity to resume establishing the User plane connection for online PDU session.
The UE according to claim 24, wherein the request message includes indication information for instructing activation of a PDU session; or

The request message includes a list of PDU sessions that need to be activated.
The UE according to claim 24, wherein the processor is specifically configured to:

Sending a request message for requesting activation of a PDU session to the AMF entity during the service request process; or

During the registration update process, a request message for requesting activation of a PDU session is sent to the AMF entity.
An access and mobility management AMF entity is characterized in that it includes:

A first receiving module, configured to receive a request message sent by a UE; wherein the request message is used to request activation of a PDU session of the UE;

A first determining module, configured to determine an always-on PDU session corresponding to the UE according to the request message and / or context information of the UE maintained by the AMF entity;

A notification module, configured to notify an SMF entity to resume the establishment of the user plane connection of the always-on PDU session.
A session management function SMF entity includes:

A second receiving module, configured to receive a notification from an AMF entity; wherein the notification is to determine, in the AMF entity, the request message sent by the UE and / or the context information of the UE maintained by the AMF entity; Sent after the corresponding always-on PDU session of the UE;

A processing module, configured to restore a user plane connection for establishing the always-on PDU session.
A user equipment UE, comprising:

A second determining module, configured to determine that a PDU session needs to be activated;

A sending module, configured to send a request message for requesting activation of a PDU session to the AMF entity, so that the AMF entity determines the always-on PDU session corresponding to the UE after receiving the request message, and notifies the SMF entity Resume the user plane connection establishing the always-on PDU session.
A computer-storable medium having stored thereon a computer program, characterized in that when the program is executed by a processor, the steps of the method according to any one of claims 1 to 7 or the claims 8 to 10 are implemented Steps of the method, or steps of the method according to any one of claims 11 to 13.