WO2019223702A1

WO2019223702A1 - Pdu session management method, apparatus and system

Info

Publication number: WO2019223702A1
Application number: PCT/CN2019/087861
Authority: WO
Inventors: 刘睿智; 周铮; 吴义壮; 熊春山
Original assignee: 华为技术有限公司
Priority date: 2018-05-21
Filing date: 2019-05-21
Publication date: 2019-11-28
Also published as: CN110519809A; CN110519809B

Abstract

Embodimetns of the present application relates to the technical field of communications. Disclosed are a PDU session management method, apparatus and system, which save time required by a PDU session to enter an activated state. The method comprises: a session management network element determines at least one PDU session from PDU sessions initiated and set up by a terminal, the at least one PDU session being in an activated state; the session management network element sends first information to an access network device, the first information comprising identifier information of the at least one PDU session and being used for instructing the access network device to release a user plane air interface resource of the at least one PDU session and retain configuration information of the user plane air interface resource of the at least one PDU session and context of the at least one PDU session.

Description

Method, device and system for managing PDU session

This application claims priority from Chinese patent applications filed on May 21, 2018 with the State Intellectual Property Office, application number 201810493181.4, and application name "Method, Device, and System for Managing PDU Sessions", the entire contents of which are incorporated herein by reference. In this application.

Technical field

Embodiments of the present application relate to the field of communications technologies, and in particular, to a method, an apparatus, and a system for managing a protocol data unit (PDU) session.

Background technique

A PDU session is a connection between a terminal and a data network (DN). The terminal can initiate the establishment of multiple PDU sessions to connect to the same DN or different DNs. In a 5th generation (5G) network architecture, a PDU session can be set to an active state or a deactivated state. When the PDU session is in the active state, both the user plane air interface resource and the control plane resource of the PDU session have been established, and the terminal and the DN can pass data through the PDU session. When the PDU session is in a deactivated state, both the user plane air interface resource and the control plane resource of the PDU session retain some information, and the terminal and the DN cannot transfer data through the PDU session.

When a PDU session is in a deactivated state, if data needs to be transmitted through the PDU session, functional network elements in the network, such as radio access network (RAN) equipment, and session management function (SMF) ) Network element and user plane function (UPF) network element, etc., need to restore user plane resources and control plane resources of the PDU session based on some information of the PDU session retained in the network, so that the PDU session is active state. However, the process of entering a PDU session from a deactivated state to an activated state requires more interactive signaling, so it takes longer.

Summary of the Invention

The embodiments of the present application provide a method, a device, and a system for managing a PDU session, which help save time required for the PDU session to enter an active state.

In a first aspect, a method for managing a PDU session is provided. The method may include: the session management network element determines at least one PDU session from a PDU session initiated by the terminal; the at least one PDU session is in an active state; the session management network element sends first information to an access network device; the first information includes The identification information of the at least one PDU session. The first information is used to instruct the access network device to release user plane air interface resources of the at least one PDU session, and retain configuration information of the user plane air interface resources and the context of the at least one PDU session.

The at least one PDU session is a PDU session that needs to enter the dormant state among the active PDU sessions initiated by the terminal. Regarding how to determine that a PDU session needs to enter the dormant state, this application is not limited, and specific examples can refer to the specific implementation section below. Optionally, the number of the at least one PDU session is less than the number of PDU sessions initiated and established by the terminal. Optionally, the number of the at least one PDU session is equal to the number of PDU sessions initiated by the terminal.

It can be seen that in this technical solution, when the PDU session is in an active state, the session management network element may instruct the access network device to release the user plane air interface resources of the PDU session, and retain the configuration information of the user plane air interface resources and the PDU session Context, in this way, when data needs to be transmitted through the PDU session, the access network device can quickly restore the user plane air interface resources of the PDU session according to the reserved configuration information of the user plane air interface resources of the PDU session, and does not need to be restarted. Obtaining the context of a PDU session therefore helps to save the time required for the PDU session to enter the active state. In addition, this technical solution helps to realize that any one or more PDU sessions can be selected from the active state to the dormant state according to the requirements, which increases the flexibility of managing the PDU sessions.

In a possible design, the session management network element determining at least one PDU session from the PDU sessions initiated by the terminal may include: the session management network element determines that the at least one PDU session belongs to any one of the following PDU sessions: a preset time There are no PDU sessions for which data needs to be transmitted in the segment; during the handover process, all QoS flows that were rejected by the target access network device (such as the target next-generation access network device); the terminal moved out of the local data network data network (LADN) PDU session; when the terminal needs to enter the suspended state from the connected state, the active PDU session; when the terminal moves out of the allowed range, the active PDU session.

In a possible design, the session management network element determines at least one PDU session from the PDU sessions initiated by the terminal, which may include: the session management network element according to the terminal's session management subscription data, the terminal's policy, and the session management network element's At least one of local configurations determines at least one PDU session from the PDU sessions initiated by the terminal.

In a possible design, the session management network element determining at least one PDU session from the PDU sessions initiated by the terminal may include: the session management network element receives the second information sent by the terminal, and initiates the establishment of the PDU session from the terminal according to the second information. At least one PDU session is determined in the PDU session; wherein the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state.

In a possible design, the session management network element determining at least one PDU session from the PDU sessions initiated by the terminal may include: the session management network element receives second information sent by the terminal, and according to the terminal's session management subscription data, the terminal At least one of the local configuration of the policy and the session management network element and the second information, determine at least one PDU session from the PDU sessions initiated by the terminal; wherein the second information includes identification information and a representation of the at least one PDU session Information that the at least one PDU session can enter a sleep state.

In one possible design, the at least one PDU session can enter a sleep state. Based on the possible design, it can be considered that the at least one PDU session is a PDU session that is required in the PDU session initiated by the terminal and can enter the dormant state.

In one possible design, the at least one PDU session can enter a sleep state. The method may further include: determining, by the session management network element, the at least one PDU session as a PDU session capable of entering a sleep state, according to at least one of a session management contract data of the terminal, a policy of the terminal, and a local configuration of the session management network element.

In one possible design, the at least one PDU session can enter a sleep state. The method may further include: the session management network element receives second information sent by the terminal, and determines that the at least one PDU session is a PDU session capable of entering a sleep state according to the second information; wherein the second information includes an identifier of the at least one PDU session Information and information indicating that the at least one PDU session can enter a sleep state.

In one possible design, the at least one PDU session can enter a sleep state. The method may further include: the session management network element receives the second information sent by the terminal, and determines the at least one according to at least one of the terminal's session management subscription data, the policy of the terminal, and the local configuration of the session management network element, and the second information. The PDU session is a PDU session capable of entering a sleep state; wherein the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state.

In a possible design, the method may further include: after receiving the response information of the first information sent by the access network device, the session management network element changes the state of the at least one PDU session from the active state to the dormant state .

In a possible design, the method may further include: the session management network element receives third information sent by the access network device; wherein the third information includes identification information of one or more PDU sessions, the one or more The PDU session is determined by the terminal from the at least one PDU session; the third information is used to indicate that the access network device has established a user plane air interface resource for the one or more PDU sessions. In other words, the third information is used to indicate that the access network device has resumed user plane air interface resources for the one or more PDU sessions. This possible design gives the steps performed by the session management network element in the process of resuming the PDU session from the dormant state to the active state.

In a possible design, the method may further include: after the session management network element receives the third information, the one or more PDUs marked by the identification information of the one or more PDU sessions included in the third information The state of the session is changed from hibernation to active.

In a second aspect, a method for managing a PDU session is provided. The method may include: the access network device receives first information sent by a session management network element; wherein the first information includes identification information of at least one PDU session, where the at least one PDU session is a PDU initiated by the session management network element from the terminal; It is determined in the session that the at least one PDU session is in an active state; the access network device releases user plane air interface resources of the at least one PDU session, and retains configuration information of the user plane air interface resources and the at least one PDU session according to the first information. Context.

It can be seen that in this technical solution, when a PDU session is in an active state, the access network device can release the user plane air interface resources of the PDU session, and retain the configuration information of the user plane air interface resources and the context of the PDU session. When data needs to be transmitted through the PDU session, the access network device can quickly recover the user plane air interface resources of the PDU session according to the reserved configuration information of the user plane air interface resources of the PDU session, and does not need to re-acquire the context of the PDU session. Therefore, it helps to save the time required for the PDU session to enter the active state. In addition, this technical solution helps to realize that any one or more PDU sessions can be selected from the active state to the dormant state according to the requirements, which increases the flexibility of managing the PDU sessions.

In a possible design, the access network device sends fourth information to the terminal according to the first information, where the fourth information includes identification information of the at least one PDU session, and the fourth information is used to instruct the terminal to release the at least one The user plane air interface resources of the PDU session retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.

It can be seen that, in this technical solution, when the PDU session is in an active state, the access network device may instruct the terminal to release the user plane air interface resource of the PDU session, and retain the configuration information of the user plane air interface resource and the context of the PDU session. When data needs to be transmitted through the PDU session, the terminal can quickly recover the user plane air interface resources of the PDU session according to the reserved configuration information of the user plane air interface resources of the PDU session, and does not need to re-acquire the context of the PDU session. Therefore, it helps to save the time required for the PDU session to enter the active state.

In a possible design, the method may further include: the access network device receives fifth information sent by the terminal; wherein the fifth information includes identification information of one or more PDU sessions, and the one or more PDU sessions are The terminal determines from the at least one PDU session; the access network device establishes user plane air interface resources of the one or more PDU sessions according to the fifth information and configuration information of user plane air interface resources of the one or more PDU sessions. This possible design gives the steps performed by the access network device during the process of resuming the PDU session from the dormant state to the active state.

In a possible design, the method may further include: the access network device sends third information to the session management network element; wherein the third information includes identification information of the one or more PDU sessions; the third information is used for Indicates that the access network device has established user plane air interface resources for the one or more PDU sessions. This possible design shows the steps performed by the access network device during the process of resuming the PDU session from the dormant state to the active state.

In a possible design, in the handover process, the access network device is a source access network device; the method may further include: the source access network device sends the one or more PDU sessions to the target access network device Context. Based on the possible design, optionally, the access network device receiving the fifth information sent by the terminal is specifically: the target access network device receives the fifth information sent by the terminal.

In a third aspect, a method for managing a PDU session is provided. The method may include: receiving, by a terminal, fourth information sent by an access network device; wherein the fourth information includes identification information of at least one PDU session, the at least one PDU session being determined by a session management network element from a PDU session initiated by the terminal The terminal releases the user plane air interface resources of the at least one PDU session according to the fourth information, and retains the configuration information of the user plane air interface resources and the context of the at least one PDU session.

It can be seen that, in this technical solution, when the PDU session is in an active state, the access network device may instruct the terminal to release the user plane air interface resource of the PDU session, and retain the configuration information of the user plane air interface resource and the context of the PDU session. When data needs to be transmitted through the PDU session, the terminal can quickly recover the user plane air interface resources of the PDU session according to the reserved configuration information of the user plane air interface resources of the PDU session, and does not need to reacquire the context of the PDU session Therefore, it helps to save the time required for the PDU session to enter the active state.

In a possible design, the method may further include: the terminal sends second information to the session management network element; wherein the second information includes identification information of the at least one PDU session and indicates that the at least one PDU session can enter a sleep state The second information is used by the session management network element to determine the at least one PDU session from the PDU sessions initiated by the terminal. Optionally, the possible design may occur in a process of establishing a PDU session by the terminal, and is not limited to this, of course. It can be seen that the embodiment of the present application supports a technical solution in which a terminal reports a PDU session to a sleep state to a session management network element.

In a possible design, the method may further include: the terminal establishing the user plane air interface resources of the one or more PDU sessions according to the configuration information of the user plane air interface resources of the one or more PDU sessions; wherein the one Or the PDU sessions are determined by the terminal from at least one PDU session; the terminal sends fifth information to the access network device; wherein the fifth information includes identification information of the one or more PDU sessions, and the fifth information is used to indicate The access network device establishes user plane air interface resources for the one or more PDU sessions. This possible design gives the steps performed by the terminal during the process of resuming the PDU session from the sleep state to the active state.

In a fourth aspect, a session management network element, such as an SMF network element, is provided. The session management network element may be used to execute any one of the methods provided in the first aspect. The session management network element may specifically be the session management network element described in the first aspect.

In a possible design, the functional modules of the session management network element may be divided according to the method provided in the first aspect, for example, each functional module may be divided corresponding to each function, or two or more functions may be divided. Integrated in a processing module.

In another possible design, the session management network element may include a memory and a processor. The memory is used to store a computer program, and when the computer program is executed by the processor, any method provided by the first aspect is executed.

In a fifth aspect, an embodiment of the present application provides an access network device, such as a RAN device. The access network device may be configured to execute any one of the methods provided in the second aspect. The access network device may specifically be the access network device described in the second aspect.

In a possible design, the function modules of the access network device may be divided according to the method provided in the second aspect above. For example, each function module may be divided corresponding to each function, or two or more functions may be divided. Integrated in a processing module.

In another possible design, the access network device may include a memory and a processor. The memory is used to store a computer program, and when the computer program is executed by the processor, any method provided by the second aspect is executed.

In a sixth aspect, an embodiment of the present application provides a terminal device. The terminal device may be configured to execute any one of the methods provided in the third aspect. The terminal device may be specifically the terminal described in the third aspect, or the terminal device may be a chip.

In a possible design, the terminal device may be divided into functional modules according to the method provided in the third aspect, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated in In a processing module.

In another possible design, the terminal device may include a memory and a processor. The memory is used to store a computer program, and when the computer program is executed by the processor, any method provided by the third aspect is executed.

In a seventh aspect, an embodiment of the present application provides a system for managing a PDU session. The system may include any one of the session management network elements provided in the fourth aspect, and any one of the access network devices provided in the fifth aspect. And any terminal device provided by the sixth aspect.

An embodiment of the present application further provides a processing device for implementing the functions of the foregoing device (for example, a session management network element, an access network device, or a terminal device). The processing device may include a processor and an interface. The processing device may be a Chip, processor can be implemented by hardware or software, when implemented by hardware, the processor can be logic circuits, integrated circuits, etc .; when implemented by software, the processor can be a general-purpose processor It is realized by reading the software code stored in the memory, which can be integrated in the processor, can be located outside the processor, and exists independently.

An embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions, and when the computer instructions are run on the computer, the computer executes any of the first to third aspects. One possible method.

The embodiment of the present application further provides a computer program product, and when the computer program product runs on a computer, any method provided in the first aspect to the third aspect is executed.

This application also provides a chip system. The chip system may include a processor for a communication device to implement the functions involved in the foregoing aspects, for example, generating, receiving, sending, or processing data and methods involved in the foregoing methods. / Or information. In a possible design, the chip system further includes a memory, and the memory is configured to store program instructions and data necessary for the communication device. The chip system may be composed of chips, and may also include chips and other discrete devices. The chip system may also be a device.

It can be understood that any of the devices or systems or computer storage media or computer program products provided above are used to execute the corresponding methods provided above. Therefore, for the beneficial effects that can be achieved, refer to the corresponding methods. The beneficial effects are not repeated here.

It should be noted that the above-mentioned devices for storing computer instructions or computer programs provided in the embodiments of the present application, such as, but not limited to, the above-mentioned memory, computer-readable storage medium, and communication chip are all non-transitory. .

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic structural diagram of a communication system to which a technical solution provided in an embodiment of the present application is applied; FIG.

FIG. 2 is a schematic diagram of a PDU session according to an embodiment of the present application; FIG.

FIG. 3 is a first schematic diagram of interaction of a method for managing a PDU session according to an embodiment of the present application; FIG.

4 is a second schematic diagram of interaction of a method for managing a PDU session according to an embodiment of the present application;

5A is a schematic diagram of a process in which a terminal enters a suspended state from a connected state, that is, a Connection Suspend process according to an embodiment of the present application;

5B is a schematic diagram of a process in which a terminal enters a connected state from a suspended state, that is, a Connection and Resume process according to an embodiment of the present application;

6A is a schematic diagram of a PDU session from an active state to a sleep state according to an embodiment of the present application;

FIG. 6B is a schematic diagram of a process for a PDU session from a sleep state to an active state in accordance with an embodiment of the present application; FIG.

7 is a schematic diagram of a process for establishing a PDU session according to an embodiment of the present application;

8 is a schematic structural diagram of a session management network element according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of an access network device according to an embodiment of the present application;

10 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a communication device to which the technical solutions provided in the embodiments of the present application are applied.

Detailed ways

The technical solutions provided in the embodiments of the present application may be applied to a wireless communication system, and the wireless communication system may be a 5G system or other communication systems in the future. Of course, it can also be a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, and so on. Taking the wireless communication system as a 5G system as an example, as shown in FIG. 1, it is a schematic architecture diagram of a communication system to which the technical solutions provided in the embodiments of the present application are applicable.

In FIG. 1, the communication system may include a terminal 10, a RAN device 20, a core network element 30, and a data network (DN) 40. The RAN device may also be called an access network (AN) device. The core network element 30 (also referred to as a core network function network element) may include: an access and mobility management function (AMF) network element 301, an SMF network element 302, and a policy control function (PCF) network element 303, UPF network element 304, and unified data management (unified data management (UDM) network element 305).

The UE 10 communicates with the AMF network element 301 through a next generation network (n) interface 1 (N1 for short). The RAN device communicates with the AMF network element 301 through the N2 interface (N2 for short), and communicates with the UPF network element 304 through the N3 interface (N3 for short). The AMF network element 301 communicates with the SMF network element 302 through the N11 interface (referred to as N11), and communicates with the PCF network element 303 through the N15 interface (referred to as N15). The SMF network element 302 communicates with the PCF network element 303 through the N7 interface (referred to as N7), communicates with the UPF network element 304 through the N4 interface (referred to as N4), and communicates with the UDM network element 305 through the N10 interface (referred to as N10). The UPF network element 304 communicates with the DN40 through an N6 interface (N6 for short). The connection between the foregoing network elements may be a wireless connection or a wired connection. In order to conveniently and intuitively represent the connection relationship between the various network elements, a solid line is used for illustration.

The terminal 10 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem; it may also include subscriber units, cellular phones, Smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device (laptop computer), cordless phone (cordless phone) or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (UE), mobile station (MS), terminal equipment (terminal device) or relay user equipment. The relay user equipment may be, for example, a 5G residential gateway (RG). For convenience of description, these devices are collectively referred to as a terminal in this application.

The RAN device 20 may be used to provide a wireless connection and is located between the terminal 10 and the core network element 30. The RAN device 20 may include, but is not limited to, a base station, an evolved base station (eNB), a next generation base station (gNB), a new radio base station (new radio base station), a macro base station, a micro base station, High-frequency base stations or transmission and reception points (TRP), non-3GPP access networks (such as WiFi), and / or non-3GPP interworking functions (N3IWF) and other equipment. It should be noted that the RAN device 20 in the following can be understood as a network element in the RAN, which is described here in a unified manner and will not be described in detail below.

The AMF network element 301 can be used for connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, and selection of the SMF network element 302. The SMF network element 302 can be used for session management such as establishment, modification, and release of a session, selection and control of a UPF network element 304, selection of service and session continuity modes, and roaming services. The PCF network element 303 may be used to provide a policy control service and obtain contract information such as a policy decision. The UPF network element 304 can be used to process events with the user plane, such as transmitting or routing data packets, detecting data packets, reporting traffic, processing quality of service (QoS), legal monitoring, and storing downlink data packets. The UDM network element 305 may be used to store subscription data of a user and the like.

DN40 can be, for example, operator services, Internet access, or third-party services.

Understandably, although not shown, the above 5G network may also include other network elements, such as network slice selection function (NSSF) network elements, network storage function (NRF) network elements, and authentication The service function (authentication server function (AUSF) network element, application function (AF) network element, and capability open function network element (network exposure function (NEF) network element) are not specifically limited in this application.

It should be noted that the interface names between the various network elements in FIG. 1 are only examples, and the interface names may be other names in the specific implementation, which is not limited in the embodiment of the present application.

It should be noted that each network element in FIG. 1, such as a terminal, a RAN device, an AMF network element, an SMF network element, a PCF network element, a UPF network element, and a UDM network element, is only a name, and the name does not constitute the device itself limited. In the 5G network and other networks in the future, these network elements may also have other names, which are not specifically limited in the embodiments of the present application. For example, AMF network elements may also be replaced with AMF or AMF entities, etc., and SMF network elements may also be replaced with SMF or SMF entities, etc., which are described collectively here and will not be described in detail below.

In order to facilitate understanding of the technical solutions provided in this application, the technologies and terms involved in this application are introduced below.

The state of the terminal includes a connected state and an idle state. Among them, the user plane transmission enhancement technology in the 4G network architecture proposes a suspend state. The suspended state is a type of idle state. Specifically, in the connection suspension process, the context of the terminal and the context of the bearer are retained, so that the terminal enters a suspended state. When the terminal needs to send data, the bearer can be restored through the Connection Resume process, so that the terminal enters the connected state without initiating a Service Request process, so that the bearer can be quickly restored.

A PDU session is a connection between a terminal and a DN (that is, DN40 in FIG. 1), and is used to provide a PDU connection service. The connection type may be an internet protocol connection (IP) connection, an Ethernet connection, or an unstructured data connection. The PDU connection service supported by the 5G core network refers to a service that provides PDU exchange between a terminal and a DN determined by a data network name (DNN). The terminal can initiate the establishment of one or more PDU sessions to connect to the same DN or different DNs. The terminal may initiate the establishment of a PDU session based on a group of core network network elements (such as an SMF network element, a PCF network element, and a UPF network element, etc.).

As shown in FIG. 2, it is a schematic diagram of a PDU session provided by an embodiment of the present application. In FIG. 2, the terminal initiates the establishment of PDU session 1, PDU session 2, and PDU session 3. Among them, PDU session 1 and PDU session 2 are connected to DN1 through different UPF network elements, and PDU session 3 is connected to DN2. The PDU session initiated by the terminal described in this application can be understood as a PDU session triggered by the terminal.

The states of a PDU session include an active state, a dormant state, and a deactivated state. The dormant state is a state proposed by the embodiments of the present application that can be, but is not limited to, a PDU session applied to a 5G communication system. The name of the state of the PDU session does not limit the state of the PDU session itself. The name of the dormant state of the PDU session is just an example. In specific implementation, the dormant state of the PDU session may also be other names, for example, it may be the suspended state of the PDU session (Suspend State, Suspend Status, Pause, Status, etc.).

When the PDU session is in the active state, both the user plane resources (also called user plane connections) and control plane resources of the PDU session have been established, and the terminal and the DN can pass data through the PDU session. The user plane resources may include user plane air interface resources such as data radio bearer (DRB). The control plane resources may include control plane air interface resources such as a signaling radio bearer (signaling radio bearer, SRB). The user plane resources of a PDU session may include a tunnel identifier, and the tunnel identifier of the PDU session may include the tunnel information of the RAN device that the PDU session passes and the tunnel information of the UPF network element that the PDU session passes, and the RAN that the PDU session passes. For equipment and UPF network elements, refer to Figure 2. Generally, the RAN device stores the tunnel information of the UPF network element, and the UPF network element stores the tunnel information of the RAN device. In this way, the RAN device and the UPF network element can send data to the peer end through the saved tunnel information of the peer end.

When the PDU session is in a dormant state, the user plane air interface resources of the PDU session are released, the tunnel information of the RAN device stored in the UPF network element is released, and the terminal and the DN cannot pass data through the PDU session. The configuration information of the user plane air interface resources and the context of the PDU session are retained. The configuration information of the user plane air interface resources refers to the configuration information used to establish the user plane air interface resources, and may include, for example, DRB configuration information. The context of the PDU session reserved in the RAN device may include, but is not limited to, at least one of the following: QoS information, PDU session identification information, UPF network element tunnel information, single network slice selection assistance information (single network slice selection assistance information, S -NSSAI), aggregate maximum bit rate (AMBR), type of PDU session, etc. The context of the PDU session reserved in the terminal may include, but is not limited to, at least one of the following: QoS information, identification information of the PDU session, assigned Internet Protocol version 4 (IPv4) address or IPv6 prefix, session and service Continuity (wession and maintenance) (SSC) mode, PDU session type, and so on. The context of the PDU session stored in the SMF network element and the UPF network element when the PDU session is in the dormant state may correspond to the context of the PDU session stored in the SMF network element and the UPF network element when the PDU session is in the deactivated state. For details, please refer to the following.

When the PDU session is in a deactivated state, both the user plane resources and the control plane resources of the PDU session retain some information, and the terminal and the DN cannot transfer data through the PDU session. For example, the context of the PDU session is reserved in the SMF network element and the UPF network element, and may include, but is not limited to, at least one of the following: QoS information, S-NSSA, DNN, and type of PDU session. When a PDU session is in a deactivated state, the RAN device usually does not retain the context of the PDU session.

It can be known from the above description that when the PDU session is in different states, the context of the PDU session reserved in different network elements may be different. The description is unified here and will not be repeated here. Generally, the context of the PDU session described below is the context of the PDU session stored in the RAN device and the terminal. It should be noted that in this application, a network element (such as a RAN device or a terminal) retains certain information, which can be understood as: the network element itself holds the information and does not release (or delete) the information. Or, it can be understood that the network element has not performed any operation on the information.

In order to clearly compare the different states of the PDU session, Table 1 uses the information managed by the network element including information 1 to 5 as an example to illustrate that some network elements (such as terminals, RAN devices, and UPF network elements) in the network are in different states. ) Management information. Among them, the information 2 to 4 managed by the network element can be specifically considered as the information 2 to 4 stored by the network element. Information 1 indicates the user plane air interface resource of the PDU session. Information 2 indicates the configuration information of the user plane air interface resources of the PDU session. Information 3 indicates the context of the PDU session reserved by the RAN device or terminal. Information 4 indicates the tunnel information of the UPF network element. Information 5 indicates the tunnel information of the RAN device.

Table 1

It should be noted that Table 1 is only an example, and it does not constitute a limitation of the information managed in the network in the state of the PDU session involved in this application. For example, when the PDU session is in a deactivated state, it does not mean that the terminal, the RAN device, and the UPF network element do not manage any information of the PDU session, but rather it does not manage the foregoing information 1 to 5. For example, when a PDU session is in any of the foregoing states, it does not mean that other information of the PDU session is not managed in the terminal, the RAN device, and the UPF network element, for example, the identification information and status of the PDU session can also be managed. For example, when a PDU session is in any of the foregoing states, it does not mean that other network elements in the terminal do not manage the information of the PDU session, for example, the SMF network element can also manage the status of the PDU session.

When the terminal is in the connected state, there is a signaling connection between the terminal and the core network. Any PDU session initiated by the terminal may be in the activated state, the dormant state, or the deactivated state. When the terminal is idle, any PDU session initiated by the terminal can be in a sleep state or a deactivated state. The relationship between the status of the terminal and the status of the PDU session can be shown in Table 2.

Table 2

终端的状态Terminal status	终端发起建立的任一PDU会话的状态Status of any PDU session initiated by the terminal
连接态Connected state	激活态、休眠态、去激活态Active state, dormant state, deactivated state
空闲态(包括暂停态)Idle state (including suspended state)	休眠态、去激活态Dormant state, deactivated state

Hereinafter, a method for managing a PDU session provided by an embodiment of the present application will be described with reference to the foregoing description and accompanying drawings. Specifically, in the following description, the embodiments of the present application are applied to the system architecture shown in FIG. 1 as an example for description. Based on this, the session management network element described in this application may specifically be an SMF network element in FIG. 1, and the access network device described in this application may specifically be a RAN device in FIG. 1.

As shown in FIG. 3, it is a schematic interaction diagram of a method for managing a PDU session according to an embodiment of the present application. The method shown in FIG. 3 specifically provides a method for making a PDU session from an active state to a sleep state. The method may include the following steps:

S101: The SMF network element determines at least one (that is, one or more) PDU sessions from the PDU sessions initiated by the terminal. The at least one PDU session is in an active state. The at least one PDU session may be a part or all of the PDU sessions initiated and established by the terminal. The at least one PDU session can be understood as: at least one PDU session to enter a sleep state.

The technical solution provided in this embodiment may be applied to a scenario in which a terminal is in a connected state. For example, it can be applied to a scenario where the terminal is always in the connected state (specifically, the terminal has been in the connected state during the execution of this embodiment), or it can be applied to a scenario where the terminal enters the suspended state from the connected state.

The SMF network element manages the status of each PDU session initiated by the terminal. Therefore, the SMF network element can determine whether each PDU session initiated by the terminal is an active PDU session.

For any active PDU session initiated by the terminal, in a possible implementation manner, when the SMF network element determines that the PDU session needs to enter the dormant state, the PDU session may be used as the at least one PDU session. A PDU session. In this implementation manner, it can be considered (or defaulted) that each PDU session (or each active PDU session) initiated by the terminal can enter the sleep state. The embodiment of the present application does not limit how to determine whether a PDU session needs to enter the sleep state. Here are some possible examples:

As an example, when the PDU session has no data to be transmitted within a preset time period (or a certain period of time), it can be considered that the PDU session needs to enter a sleep state. For example, the UPF network element detects that the PDU session has no data transmission within a specified inactivity period / inactivity timer, and then notifies the SMF network element of the detection result.

As an example, in the handover process, if all QoS flows of a PDU session are rejected by a target RAN device, such as a target next generation RAN (NG-RAN) device, the PDU session needs to go to sleep. state.

As an example, for a LADNPDU session, if the terminal moves out of the LADN service area, the PDU session needs to enter the dormant state, where the AMF network element can notify the SMF network element that the terminal has moved out of the LADA service area. Understandably, a LADN PDU session is a type of PDU session.

As an example, in a process in which the terminal enters a suspended state (ie, a connection suspension process (Connection Suspend procedure)), an active PDU session initiated by the terminal needs to enter a sleep state. This is because when the terminal is in the suspended state, each PDU session initiated by the terminal is not in the active state. Therefore, in this case, it can be considered that each active PDU session initiated by the terminal needs to enter the dormant state. . Among them, the RAN device initiates a connection suspension process to the AMF network element, indicating that the RRC connection of the terminal will be suspended. The AMF network element sends this message to the SMF network element.

As an example, if the terminal moves out of the allowed area, each active PDU session initiated by the terminal needs to enter the dormant state, where the AMF network element can notify the SMF network element that the terminal has moved out of the allowed area.

For any active PDU session initiated by the terminal, in another possible implementation manner, when the SMF network element determines that the PDU session needs to enter the sleep state, and can enter the sleep state (that is, it has to enter the sleep state) Attribute / function), the PDU session may be regarded as a PDU session among the at least one PDU session. In other words, each of the at least one PDU session is a PDU session capable of entering a sleep state. In this implementation manner, it can be considered that each PDU session (or each PDU session in an active state) can be put into a sleep state that needs to be set before executing S101.

The embodiment of the present application does not limit the specific implementation of how to set the PDU session to enter the sleep state. Here are a few possible implementations:

Manner 1: The SMF network element determines that a PDU session can enter a sleep state according to at least one of session terminal management (SM) contract data, terminal policy, and local configuration of the SMF network element.

For example, the SMF network element determines that a PDU session can enter the sleep state according to the SM subscription data of the terminal. For example, the SMF network element determines that a PDU session can enter the sleep state according to the policy of the terminal. For example, the SMF network element determines that a PDU session can enter the sleep state according to the local configuration of the SMF network element. For example, the SMF network element determines that a PDU session can enter a sleep state according to the terminal's SM subscription data and the terminal's policy. For example, the SMF network element determines that a PDU session can enter the sleep state according to the terminal's SM subscription data and the local configuration of the SMF network element. For example, the SMF network element determines that a PDU session can enter the sleep state according to the policy of the terminal and the local configuration of the SMF network element. For example, the SMF network element determines that a PDU session can enter the sleep state according to the SM subscription data of the terminal, the policy of the terminal, and the local configuration of the SMF network element.

The SM contract data of the terminal may include the SM contract data stored locally by the SMF network element, and the SM contract data of the terminal obtained through the information interaction between the SMF network element and the UDM network element. The policy of the terminal may include a local policy of the SMF network element (for example, a policy configured by the operator in the SMF network element), and a policy configured by the PCF network element to the SMF network element, and the like. If the policy of the terminal is a policy configured by the PCF network element to the SMF network element, the SMF network element can obtain the policy by exchanging information with the PCF network element. The local configuration of the SMF network element may include a policy stored locally on the SMF network element (that is, a local policy of the SMF network element), and contract data stored locally on the SMF network element, and the like.

Optionally, if at least one of the terminal's SM subscription data, the terminal's policy, and the local configuration of the SMF network element contains information indicating that a certain PDU session of the terminal can enter the sleep state, the SMF network element may consider that The PDU session can go to sleep. That is, this application supports adding to any one or more of the SMF contract data of the terminal, the policy of the terminal, and the local configuration of the SMF network element to indicate that the PDU session can enter the dormant state (or whether it indicates whether the PDU session is in a sleep state or not). To enter the sleep state).

It should be noted that the information indicating that the PDU session can enter the sleep state can be based on the granularity of the terminal or the granularity of the PDU session. If the information indicating that the PDU session can enter the sleep state is based on the terminal granularity, it indicates that the terminal initiated All established PDU sessions can go to sleep (for example, if the terminal has enhanced user plane transmission capabilities, all PDU sessions initiated by the terminal can go to sleep); if the information indicating that the PDU session can go to sleep is based on The granularity of the PDU session indicates that the PDU session can enter the sleep state.

Method 2: The SMF network element receives the second information sent by the terminal, and determines that a PDU session can enter the sleep state according to the second information. The second information includes identification information of the PDU session and information indicating that the PDU session can enter a sleep state.

This application does not limit in which process the method 2 specifically occurs, and in which signaling (or message) the second information is specifically carried. For example, Mode 2 may occur in the process of establishing the PDU session. In this case, the second information may be carried in a PDU Session Establishment message.

The information indicating that the PDU session can enter the sleep state can be understood as instruction information used to indicate that the PDU session can enter the sleep state. The specific implementation of the information indicating that the PDU session can enter the sleep state is not limited in this application. For example, a binary number "1" can be used to indicate that the PDU session can enter the sleep state, or a binary number "0" can be used to indicate that the PDU session can enter the sleep state. As another example, the PDU session can be indicated to have a user plane enhancement feature to indicate that the PDU session can enter the sleep state. Of course, this application is not limited to this.

It should be noted that the second information includes identification information of a PDU session and indication information indicating that the PDU session can enter a sleep state, for example. In specific implementation, the second information may include identification information of multiple PDU sessions and information indicating that the multiple PDU sessions can enter a sleep state. The information indicating that multiple PDU sessions can enter the sleep state may be a collection of multiple information indicating that a single PDU session can enter the sleep state, or other information. For example, assuming that the binary number "1" is used to indicate that a single PDU session can enter the dormant state, the second information may include identification information of PDU sessions 1, 2, and 3, and indicate that PDU sessions 1, 2, and 3 can enter The information of the sleep state may be a binary number "111". As another example, the second information may include identification information of the PDU sessions 1, 2, and 3, and a binary number "1", where the binary number "1" is information indicating that the PDU sessions 1, 2, and 3 can enter the sleep state. . Other examples are not listed one by one.

Method 3: The SMF network element receives the second information sent by the terminal, and determines that a PDU session can enter a sleep state according to at least one of the terminal's SMF subscription data, the terminal's policy, and the local configuration of the SMF network element, and the second information. The second information includes identification information of the PDU session and information indicating that the PDU session can enter a sleep state. For the explanation of the related content in Mode 3, refer to the foregoing, and will not be repeated here.

Understandably, after determining that the PDU session can enter the dormant state through, for example, but not limited to, any of the above methods 1 to 3, the SMF network element saves the information that the PDU session can enter the dormant state, so that the PDU needs to be determined later When the session can enter the sleep state, directly query the saved information. For example, the SMF network element may add a flag bit to each managed PDU session to mark whether the PDU session can enter the sleep state. Based on this, when S101 is performed, the SMF network element queries the flag bit of the PDU session. That is to know whether the PDU session can enter the sleep state.

Based on the above description, optionally, S101 may include: the SMF network element initiates a PDU established from the terminal according to at least one of the terminal's SMF contract data, the terminal's policy, the local configuration of the SMF network element, and the second information. At least one PDU session is determined in the session.

S102: The SMF network element sends the first information to the RAN device. The first information may include identification information of the at least one PDU session. The first information is used to instruct the RAN device to release a user plane air interface resource of the at least one PDU session, and to reserve a configuration of the user plane air interface resource of the at least one PDU session. Information and the context of the at least one PDU session.

It can be understood that the information exchange between the SMF network element and the RAN device usually needs to be forwarded through the AMF network element.

S103: The RAN device receives the first information.

S104: The RAN device releases the user plane air interface resources of the at least one PDU session according to the first information, and retains the configuration information of the user plane air interface resources of the at least one PDU session and the context of the at least one PDU session.

Optionally, after performing S104, the RAN device may change the state of the at least one PDU session from an active state to a dormant state.

S105: The RAN device sends fourth information to the terminal according to the first information. The fourth information may include identification information of the at least one PDU session. The fourth information is used to instruct the terminal to release user plane air interface resources of the at least one PDU session, and to retain configuration information of user plane air interface resources of the at least one PDU session and The context of the at least one PDU session.

S106: The terminal receives the fourth information.

S107: The terminal releases the user plane air interface resources of the at least one PDU session according to the fourth information, and retains the configuration information of the user plane air interface resources and the context of the at least one PDU session.

Optionally, after executing S107, the terminal may change the state of the at least one PDU session from an active state to a dormant state.

The above S101 to S107 describe the steps performed by the SMF network element, the RAN device, and the terminal in the process of the PDU session from the active state to the sleep state. In addition, the process may also include steps performed by the SMF network element and the UPF network element. This process may refer to the steps performed by the SMF network element and the UPF network element in the process of the PDU session from the active state to the deactivated state.

This embodiment provides a process for a PDU session to enter a dormant state from the active state. When the PDU session enters the dormant state, the terminal and / or the RAN device retains the configuration information of the user plane air interface resources of the PDU session and the context of the PDU session. In this way, when data needs to be transmitted through the PDU session, the user plane air interface resources of the PDU session can be quickly restored according to the configuration information of the user plane air interface resources retained in the PDU session, and the context of the PDU session does not need to be obtained again. Therefore, it helps to save the time required for the PDU session to enter the active state. Further, in this embodiment, the SMF network element determines at least one active PDU session from the PDU sessions initiated by the terminal, and then triggers the at least one PDU session to enter a sleep state. That is, the PDU session can be realized from the active state to the dormant state based on the PDU session granularity. In this way, it is helpful to realize that any one or more PDU sessions are switched from the active state to the dormant state according to the requirements, and the flexibility of managing the PDU sessions is increased.

As shown in FIG. 4, it is a schematic interaction diagram of a method for managing a PDU session according to an embodiment of the present application. The method shown in FIG. 4 specifically provides a method for making a PDU session from a sleep state to an active state. The method may include the following steps:

S201: The terminal establishes (or restores) the user plane air interface resources of the PDU session according to the configuration information of the user plane air interface resources of the PDU session. The PDU session is a PDU session that is initiated and established by the terminal and is in a sleep state. For example, the PDU session may be any one of the at least one PDU session in the embodiment shown in FIG. 3. The configuration information is configuration information of a user plane air interface resource of the PDU session retained in the terminal when the PDU session enters a sleep state.

Optionally, the terminal may determine that the PDU session needs to enter the active state when it is determined that data needs to be transmitted through the PDU session in the dormant state, for example, when the terminal needs to send data to or receive data from the DN through the dormant PDU session, Thereby, execution of S201 is triggered.

In this embodiment, the description is made by taking one PDU session from the sleep state to the active state as an example. Of course, multiple PDU sessions can also be changed from the sleep state to the active state at the same time.

Optionally, after performing S201, the terminal may change the state of the PDU session from the sleep state to the active state.

S202: The terminal sends fifth information to the RAN device. The fifth information includes identification information of the PDU session, and the fifth information is used to instruct the RAN device to establish a user plane air interface resource of the PDU session.

S203: The RAN device receives the fifth information.

S204: The RAN device establishes user plane air interface resources of the PDU session according to the fifth information and configuration information of user plane air interface resources of the PDU session. The configuration information is configuration information of a user plane air interface resource of the PDU session retained in the RAN device when the PDU session enters a sleep state.

Optionally, after executing S204, the RAN device may change the state of the PDU session from the sleep state to the active state.

S205: The RAN device sends third information to the SMF network element, and the third information includes identification information of the PDU session. The third information is used to indicate that the access network device has established a user plane air interface resource of the PDU session.

S206: The SMF network element receives the third information. Optionally, after executing S206, the SMF network element may change the state of the PDU session from the sleep state to the active state.

The above S201 to S206 describe the steps performed by the SMF network element, the RAN device, and the terminal in the process of the PDU session from the sleep state to the active state. In addition, the process may also include steps performed by the SMF network element and the UPF network element. This process may refer to the steps performed by the SMF network element and the UPF network element in the flow of the PDU session from the deactivated state to the activated state.

This embodiment provides a process in which a PDU session enters an active state from a dormant state. When data needs to be transmitted through the dormant PDU session, the network can quickly recover the configuration information of the user plane air interface resources of the PDU session. The user plane air interface resource of the PDU session does not need to re-acquire the context of the PDU session, so it helps to save the time required for the PDU session to enter the active state. This embodiment provides that the PDU session can be switched from the dormant state to the active state based on the PDU session granularity. In this way, it is helpful to select any one or more PDU sessions from the dormant state to the active state according to the requirements. Compared with the technical solution of changing the PDU sessions from the dormant state to the active state based on the terminal granularity, it can save resource overhead and increase Flexibility in managing PDU sessions.

Understandably, when the terminal is in the connected state, it may be necessary to perform a handover process, that is, a process triggered by the source RAN device that needs to switch from "terminal to source RAN device" to "terminal to target RAN device connection". In this case, The RAN device storing the context of the PDU session in the sleep state is specifically the source RAN device. Optionally, when the handover process is performed, the source RAN device may first determine that the terminal initiates an established and dormant PDU session, and then sends the determined context of the PDU session to the target RAN device. It can be understood that when the PDU session needs to be switched from the dormant state to the active state, the terminal may send information (such as the foregoing fifth information) to the target RAN device to indicate the user plane air interface resources for establishing the PDU session. If there is no obvious conflict, this optional implementation manner can be applied to any embodiment provided in this application.

The method for managing the PDU session provided above is described below through a specific example.

As shown in FIG. 5A, it is a schematic diagram of a process in which a terminal enters a suspended state from a connected state, that is, a Connection Suspend process according to an embodiment of the present application. The process may include a process in which at least one PDU session initiated and established by the terminal enters a dormant state from an active state, and / or a process in which other PDU sessions initiated and established by the terminal are activated and deactivated. The following description is based on an example in which the process includes: a process in which at least one PDU session initiated and established by a terminal enters a dormant state from an activated state, and other PDU sessions initiated and established by a terminal are activated into a deactivated state. The method shown in FIG. 5A may include the following steps:

S301: The RAN device sends a UE Context Suspend Request message to the AMF network element. The terminal context pause request message is used to request that the state of the terminal be changed from the active state to the suspended state. The terminal context pause request message may carry a list of PDU session identifiers (identities, IDs), and may also carry a cause value (Cause), which may be that the terminal needs to enter a suspended state. The PDU session ID list includes IDs of active PDU sessions initiated and established by the terminal. The ID of the PDU session can be considered as a specific implementation of the identification information of the PDU session.

S302: The AMF network element suspends the request message according to the terminal context, and retains the context of the terminal. The AMF network element sends an update session management context (Nsmf_PDUSession_UpdateSMContext) message to the SMF (s) network element (that is, one or more SMF network elements). The update session management context message may carry one or more PDU session IDs, and the one or more PDU session IDs belong to the PDU session ID list described in S301; in addition, it may also carry a cause value, etc., which may be required by the terminal Enter the pause state.

Specifically, the AMF network element sends an update session management context message to each SMF network element that manages the PDU session indicated by the PDU session ID list. For example, if the PDU session ID list includes the IDs of PDU sessions 1 to 4, and PDU sessions 1 and 2 are managed by SMF network element 1, and PDU session 3 is managed by SMF network element 2, the AMF network element sends the SMF to SMF. Network element 1 sends an update session management context message, which contains the IDs and cause values of PDU sessions 1 to 3 (for example, the terminal needs to enter the suspended state), and sends an update session management context message to SMF network element 2, which contains ID and reason value of PDU session 4 (for example, the terminal needs to enter the suspended state).

For example, in conjunction with the example shown in FIG. 3, the above S101 may be considered that the "at least one PDU session" in S101 is specifically the "PDU session ID list" in this embodiment, that is, each of the terminals initiated by the terminal is considered to be in an active state. All PDU sessions need to go to sleep. However, optionally, not every PDU session can enter the PDU session. Therefore, it is necessary to determine which PDU session can enter the sleep state by performing S303.

S303: The SMF (s) network element determines whether the PDU session carried in the update session management context message can enter the sleep state.

Specifically, for any PDU session, the SMF network element may determine whether the PDU session is able to query the flag bit (hereinafter referred to as a target flag bit) of the PDU session for marking whether the PDU session can enter the sleep state. Go to sleep. For example, based on the example in S302, SMF network element 1 can query the target flag bits of PDU sessions 1 to 3 to determine whether PDU sessions 1 to 3 can enter the sleep state; SMF network element 2 can query the target flag bits of PDU session 4. To determine whether PDU session 4 can enter the sleep state.

S304: The SMF (s) network element sends an N4 Session Modification Request message to the UPF network element. The N4 session modification request message may instruct the UPF network element to delete the tunnel identifier, specifically the RAN device tunnel information that one or more PDU sessions pass through. The IDs of the one or more PDU sessions belong to the PDU session ID list in S301.

For example, based on the example in S302, SMF network element 1 may send an N4 session modification request message to the UPF network element that manages the tunnel identities of PDU sessions 1 to 3. The N4 session modification request message carries the RANs through which PDU sessions 1 to 3 pass Device tunnel information; SMF network element 2 may send an N4 session modification request message to the UPF network element that manages the tunnel identity of PDU session 4. The N4 session modification request message carries the tunnel information of the RAN device through which PDU session 4 passes. The UPF network element that manages the tunnel identifier of PDU sessions 1 to 3 and the UPF network element that manages the tunnel identifier of PDU session 4 may be the same or different. The RAN device managing the PDU sessions 1 to 4 is the RAN device in the above S301.

S305: The UPF network element deletes the tunnel identifier requested to be deleted by the N4 session modification request, and then sends an N4 Session Modification Response message to the SMF (s) network element.

Since the PDU session enters the deactivated state from the activated state or enters the dormant state from the activated state, the UPF network element managing the PDU session needs to delete the tunnel identifier of the PDU session (that is, the RAN that the PDU session passes through Tunnel information of the device), therefore, this application does not limit the sequence of S304 to S305 and S303. For example, S304 to S305 may be executed before S303, S304 to S305 may be executed before S303, and S303 and the like may be executed during S304 to S305.

S306: The SMF (s) network element sends an update session management context response (Nsmf_PDUSession_UpdateSMContextResponse) message to the AMF network element. The update session management context response message carries the ID of the PDU session that needs to enter the sleep state, and the ID of the PDU session that needs to enter the deactivated state. The IDs of these PDU sessions belong to the PDU session ID list described in S301.

It should be noted that in any embodiment of the present application, the "message carries the ID of the PDU session that needs to enter a certain state" and "the message carries the ID of the PDU session and indicates that the PDU session needs to enter the state The meaning of "instruction information" is the same, and the two can be used interchangeably, or the message name can be used to indicate that the PDU session needs to enter a certain state, which is not limited in this application. In any of the embodiments of the present application, the "message carries the ID of a PDU session that needs to be entered from one state to another state" and "the message carries the ID of the PDU session and indicates that the PDU session needs to be entered from that one state The indication information of the PDU session in the other state has the same meaning, and the two can be used interchangeably, or the message name can be used to indicate that the PDU session needs to enter a certain state from a certain state, which is not limited in this application. Among them, The message here may be, for example, but not limited to, an update session management context response message, a terminal context pause response message, and the like, and the state here may be an activated state, a dormant state, or a deactivated state.

Based on the example in S303, if SMF network element 1 determines that PDU sessions 1 and 2 can enter the sleep state, and PDU session 3 cannot enter the sleep state, then in S306, SMF network element 1 sends an update session management context response to the AMF network element. The message carries the following information: PDU sessions that can enter the sleep state are PDU sessions 1 and 2, and PDU sessions that cannot enter the sleep state are PDU sessions. If the SMF network element 2 determines that the PDU session 4 can enter the sleep state, in S306, the update session management context response message sent by the SMF network element 1 to the AMF network element carries the following information: The PDU session capable of entering the sleep state is the PDU session 4 .

S307: The AMF network element sends a UE context suspension response (UE Context Suspend Response) message to the RAN device. The terminal context pause response message carries the ID of the PDU session that needs to enter the sleep state, and the ID of the PDU session that needs to enter the deactivated state.

For example, in conjunction with the example shown in FIG. 3, S306 to S307 can be considered as the specific implementation of the above S102. Specifically, the first information can be considered to be sent in the update session management context response message and sent by the SMF network element to the AMF network element. It is carried in the terminal context pause response message and sent by the AMF network element to the RAN device.

S308: The RAN device suspends the response message according to the context. For each PDU session (for example, the above PDU sessions 1, 2, and 4) that needs to enter the dormant state, the user plane air interface resources of the PDU session are released, and the configuration of the user plane air interface resources is retained. The information and the context of the PDU session. Optionally, the state of the PDU session is changed from an active state to a dormant state. And, for each PDU session that needs to enter the deactivated state (for example, the above-mentioned PDU session 3), the user plane air interface resources of the PDU session, the configuration information of the user plane air interface resources, and the context of the PDU session are optional. The state of the PDU session is changed from an active state to a deactivated state.

In specific implementation, the RAN device may also pause the response message according to the context, and may also retain the context of the terminal and generate a Resume ID for the terminal, where the Resume ID for the terminal is used to identify the context of the terminal. Subsequently, the RAN device may send the Resume ID for the terminal to the terminal. In this way, when the Connection Resume process is subsequently performed, the terminal can send the Resume ID for the terminal to the RAN device, so that the RAN device can obtain the context of the terminal according to the Resume ID for the terminal. Optionally, if the new RAN device is different from the old RAN device during the execution of the Connection Resume process, the new RAN device usually needs to send the Resume ID of the terminal to the old RAN device to obtain the context of the terminal on the old RAN.

S309: The RAN device sends a radio resource control (radio resource control, RRC) connection suspension (Connection Suspend) message to the terminal. The RRC connection suspension message may carry the ID of the PDU session that needs to enter the sleep state, and the ID of the PDU session that needs to enter the deactivated state.

For example, with reference to the example shown in FIG. 3, S309 can be considered as a specific implementation of S105. Specifically, it can be considered that the fourth information is carried in the RRC connection suspension message and sent by the RAN device to the terminal.

S310: The terminal releases the user plane air interface resource of the PDU session for each PDU session that needs to enter the dormant state according to the RRC connection suspension message, and retains the configuration information of the user plane air interface resource and the context of the PDU session. Optional, The state of the PDU session is changed from an active state to a dormant state. And, for each PDU session that needs to enter the deactivated state, release the user plane air interface resources of the PDU session, the configuration information of the user plane air interface resources, and the context of the PDU session. Optionally, the status of the PDU session is determined by The active state is changed to the deactivated state.

In this embodiment, in a process in which a terminal enters a suspended state from a connected state, any one or more PDU sessions initiated and established by the terminal are switched from an activated state to a dormant state. For a description of the beneficial effects of this embodiment, refer to the foregoing.

Optionally, in another embodiment provided in the present application, the PDU session ID list in the above S301 includes an ID of a PDU session capable of entering a sleep state. In this embodiment, the SMF network element may notify the RAN device of the result of whether the PDU session can enter the sleep state in advance. In this way, when the RAN device executes S301, the PDU session ID list may be set to include a PDU session that can enter the sleep state. ID. In this case, it is not necessary to execute the above S303. Alternatively, since the SMF network element can notify the RAN device of whether the PDU session can enter the dormant state in advance, after the RAN device confirms that the terminal needs to enter the suspended state and determines the PDU session ID list, the list is released. The indicated user plane air interface resources of each PDU session retain the configuration information of the user plane air interface resources and the context of the PDU session, without the need to release the PDU session after receiving the context pause response message as shown in S308. The user plane air interface resource retains the configuration information of the user plane air interface resource and the context of the PDU session.

As shown in FIG. 5B, a schematic diagram of a process in which a terminal enters a connected state from a suspended state, that is, a Connection and Resume process, according to an embodiment of the present application. The process may include a process in which at least one PDU session initiated and established by the terminal enters an active state from a dormant state, and / or a process in which other PDU sessions initiated and established by the terminal enter an activated state from a deactivated state. The following description uses the process to include at least one PDU session initiated and established by the terminal from a sleep state to an active state as an example for description. The method shown in FIG. 5B may include the following steps:

S401: The terminal determines that it needs to enter the connected state from the suspended state. For example, when there is data to be transmitted, such as when data needs to be sent to the DN or when data sent by the DN needs to be received, it is determined that the suspended state needs to be entered into the connected state.

S402: The terminal determines whether one or more PDU sessions that need to transmit data are currently in a sleep state or a deactivated state. The one or more PDU sessions may be some or all of the PDU sessions initiated by the terminal. A PDU session that is currently in a dormant state is a PDU session that needs to be changed from the dormant state to the active state.

It can be understood that the process of the terminal entering the connected state from the suspended state may further include entering the activated state of the PDU session that needs to transmit data and is in the deactivated state. For a specific implementation manner, refer to the existing technology, and details are not described herein again.

S403: The terminal sends an RRC Connection Resume Request message to the RAN device. The RRC connection restoration request message may carry the ID of the one or more PDU sessions and the indication information of the one or more PDU sessions from the sleep state to the active state. The RRC connection restoration request message is used to request restoration of control plane air interface resources between the terminal and the RAN device and user plane air interface resources of the one or more PDU sessions.

S404: For each PDU session in the one or more PDU sessions, the terminal and the RAN device respectively establish (or restore) the PDU session according to the configuration information of the user plane air interface resources of the PDU session by performing information interaction. User plane air interface resources, the terminal and the RAN device establish control plane air interface resources through information interaction. Optionally, the terminal and the RAN device may also change the state of each PDU session that needs to be changed from the sleep state to the active state from the sleep state to the active state.

For example, in conjunction with the embodiment shown in FIG. 4, it can be considered that information exchange between the terminal and the RAN device includes the terminal in FIG. 4 sending fifth information to the RAN device. For example, S404 and S403 may be executed simultaneously or sequentially. This application does not limit this.

S405: The RAN device sends an RRC connection resume response (ConnectionResumeResponse) message to the terminal.

After performing S405, the terminal and the DN can perform uplink data transmission through the one or more PDU sessions, that is, the terminal can send data to the DN through the one or more PDU sessions.

S406: The RAN device sends a UE context recovery request (UE Context Resume Request) message to the AMF network element. The terminal context recovery request message may carry the ID of the one or more PDU sessions and the indication information of the one or more PDU sessions from a sleep state to an active state. The terminal context restoration request message is used to indicate that the user plane air interface resource of the one or more PDU sessions has been restored. The message may also carry tunnel information of the RAN device through which the one or more PDU sessions pass.

S407: The AMF network element sends an update session management context (Nsmf_PDUSession_UpdateSMContext) message to the SMF (s) network element. The update session management context message may carry the ID of the PDU session that needs to be changed from the sleep state to the active state. The update session management context message is used to indicate that the user plane air interface resources of the one or more PDU sessions have been restored. After receiving the update session management context message, the SMF (s) network element may send the tunnel information of the RAN device through which the one or more PDU sessions pass to the UPF network element.

S408: The SMF (s) network element sends an N4 session modification request message to the UPF network element. The N4 session modification request message may carry the identifier of the tunnel to be restored, specifically, the tunnel information of the RAN device through which one or more PDU sessions carried by the session management context message is updated.

S409: The UPF network element restores (or saves) the identifier of the tunnel to be restored requested by the N4 session modification request message, and sends an N4 session modification response message to the SMF (s) network element.

After performing S409, the terminal and the DN can perform downlink data transmission through the one or more PDU sessions, that is, the DN can send data to the terminal through the one or more PDU sessions.

S410: The SMF (s) network element changes the state of the one or more PDU sessions from a sleep state to an active state.

S411: The SMF (s) network element sends an Update Session Management Context Response (Nsmf_PDUSession_UpdateSMContextResponse) message to the AMF network element.

S412: The AMF network element sends a UE Context Resume Response message to the RAN device.

In this embodiment, in a process in which a terminal enters a connected state from a suspended state, any one or more PDU sessions initiated and established by the terminal are switched from a sleep state to an activated state. For a description of the beneficial effects of this embodiment, refer to the foregoing.

As shown in FIG. 6A, a flow chart of a PDU session from an active state to a sleep state provided by an embodiment of the present application is shown. The terminal is always connected in this process. The method shown in FIG. 6A may include the following steps:

S501: The SMF network element determines that one or more PDU sessions are required and can enter the sleep state. The one or more PDU sessions are some or all of the PDU sessions initiated and established by the terminal in an active state.

Regarding how the SMF network element determines that a PDU session needs to enter the dormant state from the connected state and the specific implementation manner capable of entering the dormant state from the connected state, reference may be made to the above, which is not repeated here. It can be understood that, in the case where there is no obvious conflict, a specific implementation manner provided above may be applicable to this embodiment.

S502: The SMF network element sends an N4 session modification request message to the UPF network element. The N4 session modification request message may instruct the UPF network element to delete the tunnel identifier, specifically the tunnel information of the RAN device through which the one or more PDU sessions pass.

S503: The UPF network element deletes the tunnel identifier requested by the N4 session modification request message, and then sends an N4 session modification response message to the SMF network element.

S504: The SMF network element sends N1N2 message transmission (Namf_Communication_N1N2MessageTransfer) signaling to the AMF network element. The N1N2 message transmission signaling may carry IDs of the one or more PDU sessions, and indication information that the one or more PDU sessions need to enter a sleep state.

S505: The AMF network element sends an N2 Session Request (N2 Session Request) message to the RAN device. The N2 session request message may carry the ID of the one or more PDU sessions, and the indication information for entering the one or more PDU sessions into a sleep state.

For example, in conjunction with the embodiment shown in FIG. 3, S504 to S505 can be considered as the specific implementation of the above S102. Specifically, it can be considered that the first information is carried in the N1N2 message transmission signaling and sent by the SMF network element to the AMF network element. It is carried in the N2 session request message and sent by the AMF network element to the RAN device.

S506: For each PDU session in the one or more PDU sessions, the RAN device releases the user plane air interface resources of the PDU session, and retains the configuration information of the user plane air interface resources and the context of the PDU session. The RAN device changes the state of the PDU session from the active state to the dormant state.

S507: The RAN device sends an RRC Connection Reconfiguration message to the terminal. The RRC connection reconfiguration message may carry IDs of the one or more PDU sessions, and indication information of the one or more PDU sessions entering a sleep state.

For example, in conjunction with the example shown in FIG. 3, S507 can be considered as a specific implementation of S105. Specifically, it can be considered that the fourth information is carried in the RRC connection reconfiguration message and sent by the RAN device to the terminal.

S508: For each PDU session in the one or more PDU sessions, the terminal releases user plane air interface resources of the PDU session, and retains configuration information of the user plane air interface resources and the context of the PDU session. The terminal changes the state of the PDU session from the active state to the dormant state.

S509: The terminal sends an RRC connection reconfiguration response message to the RAN device.

S510: The RAN device sends an N2 Session Response (N2 Session Response) message to the AMF network element.

S511: The AMF network element sends an update session management context response (Nsmf_PDUSession_UpdateSMContext) message to the SMF network element.

S512: The SMF network element reserves the context of the PDU session. The SMF network element changes the state of the PDU session from the active state to the dormant state.

In this embodiment, when the terminal is in the connected state, any one or more PDU sessions initiated and established by the terminal are switched from the active state to the sleep state. For a description of the beneficial effects of this embodiment, refer to the foregoing.

As shown in FIG. 6B, a flowchart of a PDU session from a sleep state to an active state is provided according to an embodiment of the present application. The terminal is always connected in this process. The method shown in FIG. 6B may include the following steps:

S601: The terminal determines that one or more PDU sessions need to be switched from the dormant state to the active state. For example, when data needs to be transmitted through the one or more PDU sessions in the dormant state, it is determined that the one or more PDU sessions need to be transmitted. Enter the active state from the sleep state.

S602: The terminal sends a PDU session restoration request message to the RAN device. The PDU session recovery request message may carry the ID of the one or more PDU sessions and indication information for the one or more PDU sessions from a sleep state to an active state. The PDU session recovery request message is used to request to recover the user plane air interface resources of the one or more PDU sessions.

S603: For each PDU session in the restoration of the one or more PDUs, the terminal and the RAN device, through information exchange, respectively establish a user-plane air interface of the PDU session according to the configuration information of the user-plane air interface resources of the PDU session that they retain. Resources. In addition, the terminal and the RAN device can also change the state of each PDU session that needs to enter the active state from the dormant state to the active state.

For example, in conjunction with the embodiment shown in FIG. 4, it can be considered that information exchange between the terminal and the RAN device includes the terminal in FIG. 4 sending fifth information to the RAN device. The above S603 and S602 may be executed simultaneously or sequentially. This application does not limit this.

S604: The RAN device sends a PDU session restoration response message to the terminal.

After performing S604, the terminal and the DN can perform uplink data transmission through the one or more PDU sessions, that is, the terminal can send data to the DN through the one or more PDU sessions.

S605: The RAN device sends a PDU session context restoration request message to the AMF network element. The PDU session context recovery request message may carry IDs of the one or more PDU sessions and indication information of the one or more PDU sessions from a sleep state to an active state. The PDU session context recovery request message is used to request to recover the context of the one or more PDU sessions.

S606: The AMF network element sends an update session management context message to the SMF (s) network element. The update session management context message may carry IDs of the one or more PDU sessions, and indication information of the one or more PDU sessions from a sleep state to an active state. The update session management context message is used to indicate that the user plane air interface resource of the one or more PDU sessions has been restored. After receiving the update session management context message, the SMF (s) network element may update the one or more PDU sessions. The tunnel information of the RAN device is sent to the UPF network element.

S607: The SMF (s) network element sends an N4 session modification request message to the UPF network element. The N4 session modification request message may carry a tunnel identifier to be restored, specifically, the tunnel information of the RAN device through which the PDU session carried by the update session management context message is updated.

S608: The UPF network element restores (or saves) the tunnel identifier to be restored requested by the N4 session modification request message, and sends an N4 session modification response message to the SMF (s) network element.

After performing S608, the terminal and the DN can perform uplink data transmission through the one or more PDU sessions, that is, the terminal can send data to the DN through the one or more PDU sessions.

S609: The SMF (s) network element changes the state of each PDU session in the one or more PDU sessions from a sleep state to an active state.

S610: The SMF (s) network element sends an update session management context response message to the AMF network element.

S611: The AMF network element sends a PDU session context recovery response message to the RAN device.

In this embodiment, when the terminal is in the connected state, any one or more PDU sessions initiated and established by the terminal are switched from the sleep state to the active state. For a description of the beneficial effects of this embodiment, refer to the foregoing.

As shown in FIG. 7, this embodiment provides a process for establishing a PDU session. The method may include the following steps:

S701: The terminal sends a PDU session establishment message to the AMF network element. The PDU session establishment message may carry the ID of the PDU session and an enhanced indication of user plane transmission. The enhanced indication of user plane transmission is used to indicate that the PDU session can enter the sleep state or cannot enter the sleep state.

S702: The AMF network element sends a message for establishing a session management context (Nsmf_PDUSession_CreateSMContext) to the SMF network element. The message establishing the session management context carries the ID of the PDU session and the user plane transmission enhancement indication.

S703: The SMF network element obtains the session management contract data of the terminal from the UDM network element. The subscription data may include an indication of whether the PDU session can enter the sleep state.

S704: The SMF network element obtains the policy of the terminal from the PCF network element. The policy of the terminal may include a policy related to whether the PDU session can enter a sleep state.

Any of the above steps S703 and S704 is optional.

S705: The SMF network element determines whether the PDU session can enter the dormant state according to at least one of the terminal's SM subscription data, the terminal's policy, and the local configuration of the SMF network element and the user plane transmission enhancement instruction. The specific implementation of this step, as well as information such as the SM subscription data, can be referred to above, and will not be repeated here.

S706: The SMF network element records whether the PDU session can enter the sleep state. How the SMF network element records whether the PDU session can enter the sleep state can refer to the above, and will not be repeated here.

This embodiment provides a method for establishing a PDU session. In this method, the terminal may send an indication to the SMF network element that the PDU session can enter the sleep state (or an indication that it cannot enter the sleep state) during the process of initiating the establishment of the PDU session. In this way, when the SMF network element needs to determine whether the PDU session can enter the sleep state, it can directly query the recorded information. The directly recorded information may be applied to, but not limited to, any of the above related embodiments.

It should be noted that the above describes the process of changing the PDU session from the active state to the sleep state, and the process of restoring (or entering) the PDU session from the sleep state to the active state. It can be understood that during the specific implementation process, the PDU session can also enter the deactivated state from the dormant state, and can also enter the dormant state from the deactivated state. For example, but not limited to, when the contract data of the terminal is changed and other reasons make a PDU session or some PDU sessions change from being able to enter the dormant state to not being able to enter the dormant state. If the PDU session is currently in the dormant state, optionally, you can change the The PDU session enters the deactivated state from the sleep state. For example, but not limited to, when the contract data of the terminal is changed and other reasons make a certain PDU session change from being unable to enter the dormant state to being able to enter the dormant state, if the PDU session is currently in a deactivated state, the optional can be changed The PDU session goes from a deactivated state to a dormant state. Other examples are not listed one by one. In addition, the embodiment of the present application does not limit the flow of the PDU session from the sleep state to the deactivated state, and the flow of the PDU session from the deactivated state to the sleep state.

The above mainly introduces the solutions provided by the embodiments of the present application from a method perspective. In order to realize the above functions, it includes a hardware structure and / or a software module corresponding to each function. Those skilled in the art should easily realize that, with reference to the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

In the embodiment of the present application, function modules can be divided according to the foregoing method example (including a session management network element such as an SMF network element, an access network device such as a RAN device, and a terminal device such as a terminal). For example, it can correspond to Each function is divided into various function modules, and two or more functions can also be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.

As shown in FIG. 8, it is a schematic structural diagram of a session management network element according to an embodiment of the present application. The session management network element 8 shown in FIG. 8 may be used to perform the steps performed by the SMF network element in any one of the methods provided above. The session management network element 8 may include a processing unit 801 and a transceiver unit 802. among them:

The processing unit 801 is configured to determine at least one PDU session from the PDU sessions initiated by the terminal, where at least one PDU session is in an activated state.

The transceiver unit 802 is configured to send first information to the access network device; the first information includes identification information of at least one PDU session, and the first information is used to instruct the access network device to release user plane air interface resources of the at least one PDU session, and reserve the User plane air interface resource configuration information and the context of at least one PDU session.

For example, in conjunction with FIG. 3 or FIG. 4, the session management network element 8 may be the SMF network element in FIG. 3 or FIG. 4, the processing unit 801 may be used to execute S101 in FIG. 3, and the transceiver unit 802 may be used to execute in FIG. S102.

Optionally, the processing unit 801 may be specifically configured to: determine that the at least one PDU session belongs to any of the following PDU sessions: a PDU session in which no data needs to be transmitted within a preset time period; in the handover process, all quality of service flows are PDU sessions rejected by the target access network device; LADN PDU sessions when the terminal has moved out of LADN; PDU sessions that need to be active when the terminal enters the suspended state from the connected state; active PDUs when the terminal moves out of the allowed range Conversation.

Optionally, the processing unit 801 may be specifically configured to determine at least one PDU from a PDU session initiated by the terminal according to at least one of the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element 8. Conversation.

Optionally, the transceiver unit 802 may be further configured to receive the second information sent by the terminal. In this case, the processing unit 801 may be specifically configured to determine at least one PDU session from a PDU session initiated and established by the terminal according to the second information; wherein the second information includes identification information of at least one PDU session and indicates that the at least one PDU session is capable of Information about entering hibernation.

Optionally, the transceiver unit 802 may be further configured to receive the second information sent by the terminal. In this case, the processing unit 801 may be specifically configured to: according to at least one of the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element 8 and the second information, in the PDU session initiated and established by the terminal Determining at least one PDU session; wherein the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state.

Optionally, the at least one PDU session can enter a sleep state. The processing unit 801 may be specifically configured to determine that the at least one PDU session is a PDU session capable of entering a sleep state according to at least one of session management subscription data of the terminal, a policy of the terminal, and a local configuration of the session management network element.

Optionally, the at least one PDU session can enter a sleep state. The transceiver unit 802 may be further configured to receive the second information sent by the terminal, and the processing unit 801 may be specifically configured to determine, according to the second information, that the at least one PDU session is a PDU session capable of entering a sleep state, where the second information includes the PDU session. Identification information of at least one PDU session and information indicating that the at least one PDU session can enter a sleep state;

Optionally, the at least one PDU session can enter a sleep state. The transceiver unit 802 may be further configured to receive the second information sent by the terminal, and the processing unit 801 may be specifically configured to perform at least one of the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element and the first The second information determines that the at least one PDU session is a PDU session capable of entering a sleep state; wherein the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state.

Optionally, the transceiver unit 802 may be further configured to receive third information sent by the access network device, where the third information includes identification information of one or more PDU sessions, and the one or more PDU sessions are sent by the terminal from at least one Determined in the PDU session; the third information is used to indicate that the access network device has established a user plane air interface resource for one or more PDU sessions. For example, in conjunction with FIG. 4, the transceiver unit 802 may be configured to perform S206.

For the explanation of related content in the session management network element provided in the embodiments of the present application and the technical effects that can be obtained, refer to the foregoing method embodiments, and details are not described herein again.

As shown in FIG. 9, it is a schematic structural diagram of an access network device according to an embodiment of the present application. The access network device 9 shown in FIG. 9 may be configured to perform the steps performed by the RAN device in any one of the methods provided above. The access network device 9 may include a transceiver unit 901 and a processing unit 902. among them:

The transceiver unit 901 is configured to receive first information sent by the session management network element. The first information includes identification information of at least one PDU session. The at least one PDU session is determined by the session management network element from a PDU session initiated by the terminal. , At least one PDU session is active.

The processing unit 902 is configured to release user plane air interface resources of at least one PDU session according to the first information, and retain configuration information of the user plane air interface resources and the context of the at least one PDU session.

For example, in conjunction with FIG. 3 or FIG. 4, the access network device 9 may be the RAN device in FIG. 3 or FIG. 4, the transceiver unit 901 may be used to execute S103 in FIG. 3, and the processing unit 902 may be used to execute the S104.

Optionally, the transceiver unit 901 may be further configured to send fourth information to the terminal according to the first information, where the fourth information includes identification information of at least one PDU session, and the fourth information is used to instruct the terminal to release at least one PDU session. The user plane air interface resources retain the configuration information of the user plane air interface resources and the context of at least one PDU session. For example, in conjunction with FIG. 3, the transceiver unit 901 may be configured to execute S105.

Optionally, the transceiver unit 901 may be further configured to receive fifth information sent by the terminal, where the fifth information includes identification information of one or more PDU sessions, and the one or more PDU sessions are from the at least one PDU session of the terminal. definite. In this case, the processing unit 902 may be further configured to establish user plane air interface resources of one or more PDU sessions according to the fifth information and configuration information of user plane air interface resources of one or more PDU sessions. For example, in conjunction with FIG. 4, the transceiver unit 901 may be used to execute S203, and the processing unit 902 may be used to execute S204.

Optionally, the transceiver unit 901 may be further configured to send the third information to the session management network element. The third information includes identification information of the one or more PDU sessions; the third information is used to indicate that the access network device 9 has established a user plane air interface resource of the one or more PDU sessions. For example, in conjunction with FIG. 4, the transceiver unit 901 may also be used to execute S205.

Optionally, in the handover process, the access network device 9 is a source access network device. In this case, the transceiver unit 901 is further configured to send the context of the one or more PDU sessions to the target access network device. Based on this optional implementation manner, the transceiver unit 901 may be further configured to receive the fifth information sent by the terminal, specifically: the target access network device receives the fifth information sent by the terminal. The transceiver unit 901 may be further configured to send the third information to the session management network element. Specifically, the target access network device sends the third information to the session management network element.

For the explanation of related content in the access network device provided in the embodiments of the present application and the technical effects that can be obtained, refer to the foregoing method embodiments, and details are not described herein again.

As shown in FIG. 10, it is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device 10 shown in FIG. 10 may be configured to execute the steps performed by the terminal in any of the methods provided above. The terminal device 10 may include a transceiving unit 1001 and a processing unit 1002. among them:

The transceiver unit 1001 is configured to receive fourth information sent by the access network device. The fourth information includes identification information of at least one PDU session. The at least one PDU session is a PDU session initiated by the session management network element from the terminal device 10. It is determined that at least one PDU session is active.

The processing unit 1002 is configured to release the user plane air interface resources of the at least one PDU session according to the fourth information, and retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.

For example, in conjunction with FIG. 3 or FIG. 4, the terminal device 10 may be the terminal in FIG. 3 or FIG. 4. The transceiver unit 1001 may be used to execute S106 in FIG. 3, and the processing unit 1002 may be used to execute S107.

Optionally, the transceiver unit 1001 may be further configured to send second information to the session management network element; the second information includes identification information of at least one PDU session and information indicating that the at least one PDU session can enter a sleep state, and the second information is used for At least one PDU session is determined in the session management network element from the PDU sessions initiated by the terminal device 10.

Optionally, the processing unit 1002 may be further configured to establish user plane air interface resources of one or more PDU sessions according to the configuration information of the user plane air interface resources of one or more PDU sessions; wherein the one or more PDU sessions are The terminal device 10 is determined from at least one PDU session. In this case, the transceiver unit 1001 may be further configured to send fifth information to the access network device, where the fifth information includes identification information of one or more PDU sessions, and the fifth information is used to instruct the access network device to establish one User plane air interface resources for one or more PDU sessions. For example, in conjunction with FIG. 4, the processing unit 1002 may be used to execute S201, and the transceiver unit 1001 may be used to execute S202.

For the explanation of the related content in the terminal device provided in the embodiments of the present application and the technical effects that can be obtained, refer to the foregoing method embodiments, and details are not described herein again.

As shown in FIG. 11, it is a schematic structural diagram of a communication device to which the technical solutions provided in the embodiments of the present application are applicable. The communication device 11 may include: at least one processor 1101, a communication line 1102, a memory 1103, and at least one communication interface 1104. The communication device 11 may specifically be any one of the session management network element 8, the access network device 9, or the terminal device 10 provided above. For example, in conjunction with any of FIG. 8 to FIG. 10, the transceiver unit may be the communication interface 1104 in FIG. 11, and the processing unit may correspond to the processor 1101 or the processor 1107 in FIG. 11.

The processor 1101 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program program of the present application. integrated circuit.

The communication line 1102 may include a path for transmitting information between the aforementioned components.

The memory 1103 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM), or other types that can store information and instructions Dynamic storage device, can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory (EEPROM)), read-only compact disc (compact disc-read-only memory (CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.

The communication interface 1104 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), and the like.

The memory 1103 is configured to store a computer execution instruction for executing the solution of the present application, and the processor 1101 controls the execution. The processor 1101 is configured to execute computer execution instructions stored in the memory 1103, thereby implementing the method provided in the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

Optionally, the memory 1103 may exist independently, and is connected to the processor 1101 through a communication line 1102. The memory 1103 may also be integrated with the processor 1101.

In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 11.

In a specific implementation, as an embodiment, the communication device 11 may include multiple processors, such as the processor 1101 and the processor 1107 in FIG. 11. Each of these processors can be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

In specific implementation, as an embodiment, the communication device 11 may further include an output device 1105 and an input device 1106. The output device 1105 communicates with the processor 1101 and can display information in a variety of ways. For example, the output device 1105 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. The input device 1106 is in communication with the processor 1101 and can receive user input in a variety of ways. For example, the input device 1106 may be a mouse, a keyboard, a touch screen device, or a sensing device.

The above-mentioned communication device 11 may be a general-purpose device or a special-purpose device. In a specific implementation, the communication device 11 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device having a similar structure in FIG. 11 device. The embodiment of the present application does not limit the type of the communication device 11.

For the related steps and explanations performed by the processor and the technical effects that can be obtained in the communication device provided in the embodiments of the present application, reference may be made to the foregoing method embodiments, and details are not described herein again.

An embodiment of the present application further provides a system for managing a PDU session. The system may include: a session management network element, an access network device, and a terminal.

Optionally, the session management network element is used to determine at least one PDU session from the PDU sessions initiated by the terminal; the at least one PDU session is in an active state; and sending first information to the access network device; the first information includes the Identification information of at least one PDU session. The access network device is configured to receive the first information, and release the user plane air interface resources of the at least one PDU session according to the first information, and retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.

Optionally, the session management network element executes to determine at least one PDU session from the PDU sessions initiated by the terminal, which may include: the session management network element according to the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element Determining at least one PDU session from the established PDU sessions initiated by the terminal.

Optionally, the terminal may be further configured to send second information to the session management network element, where the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state. The session management network element may also be used to receive the second information sent by the terminal. In this case, the execution of the session management network element to determine at least one PDU session from the PDU sessions initiated by the terminal may include: the session management network element determines the at least one PDU session from the PDU sessions initiated by the terminal according to the second information.

Optionally, the terminal may be further configured to send second information to the session management network element; the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state. The session management network element may also be used to receive the second information sent by the terminal. In this case, the session management network element determining at least one PDU session from the PDU sessions initiated by the terminal may include: the session management network element according to the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element And at least one of the second information and the second information, the at least one PDU session is determined from the PDU session initiated and established by the terminal.

Optionally, the access network device may be further configured to send fourth information to the terminal according to the first information; the fourth information includes identification information of the at least one PDU session. The terminal is further configured to receive fourth information sent by the access network device, and release the user plane air interface resources of the at least one PDU session according to the fourth information, and retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.

Optionally, the at least one PDU session can enter a sleep state.

Optionally, the terminal may be further configured to establish the user plane air interface resources of the one or more PDU sessions according to the configuration information of the user plane air interface resources of the one or more PDU sessions; the one or more PDU sessions are Determined in at least one PDU session; and sending fifth information to the access network device; wherein the fifth information includes identification information of the one or more PDU sessions. The access network device may be further configured to receive the fifth information sent by the terminal, and establish the user plane air interface of the one or more PDU sessions according to the fifth information and the configuration information of the user plane air interface resources of the one or more PDU sessions. Resources.

Optionally, the access network device may be further configured to send third information to the session management network element; the third information includes identification information of the one or more PDU sessions; the third information is used to indicate that the access network device has established the User plane air interface resources for one or more PDU sessions. The session management network element may also be used to receive third information sent by the access network device.

For the explanation of related content in the PDU session management system provided in the embodiments of the present application and the technical effects that can be obtained, refer to the foregoing method embodiments, and details are not described herein again.

In the description of this application, unless otherwise stated, "/" represents or means, for example, A / B may represent A or B; "and / or" herein is merely an association relationship describing an associated object, It means that there can be three kinds of relationships, for example, A and / or B, it can mean: there are three cases of A alone, A and B, and B alone.

In the description of this application, unless stated otherwise, "plurality" means two or more.

In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as “first” and “second” are used to distinguish the same or similar items having substantially the same functions and functions. Those skilled in the art can understand that the words "first", "second" and the like do not limit the number and execution order, and the words "first" and "second" are not necessarily different.

In addition, in the description of the present application, unless otherwise stated, "at least one" means any one or any combination, and "at least one" means any one or any combination. For example, at least one of A, B, and C may include the following cases: ①A; ②B; ③C; ④A and B; ⑤A and C; ⑥B and C; ⑦A, B, and C.

The network architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will know that with the With the evolution and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer executes instructions loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be from a website site, a computer, a server, or a data center. Transmission by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or includes one or more data storage devices such as servers, data centers, and the like that can be integrated with the medium. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and understand by looking at the drawings, the disclosure, and the appended claims. Other variations of the disclosed embodiments are implemented. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

Although the present application has been described in connection with specific features and embodiments thereof, it is apparent that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are deemed to have covered any and all modifications, changes, combinations, or equivalents that fall within the scope of the application. 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, this application also intends to include these modifications and variations.

Claims

A method for managing a protocol data unit PDU session, wherein the method includes:

The session management network element determines at least one PDU session from the PDU sessions initiated by the terminal; wherein the at least one PDU session is in an activated state;

The session management network element sends first information to an access network device; the first information includes identification information of the at least one PDU session, and the first information is used to instruct the access network device to release the at least one The user plane air interface resources of a PDU session retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.
The method according to claim 1, wherein the session management network element determining at least one PDU session from a PDU session initiated by the terminal comprises:

The session management network element determines that the at least one PDU session belongs to any one of the following PDU sessions:

No data PDU session to be transmitted within a preset time period;

During the handover process, all QoS flows are rejected by the target access network device.

LADN PDU session when the terminal moves out of the local data network service area LADN;

When the terminal needs to enter the suspended state from the connected state, the PDU session is in an active state;

When the terminal moves out of the allowed range, it is in an active PDU session.
The method according to claim 1 or 2, wherein the at least one PDU session is a PDU session capable of entering a sleep state, and the method further comprises:

The session management network element determines that the at least one PDU session is capable of entering a sleep state according to at least one of session management subscription data of the terminal, a policy of the terminal, and a local configuration of the session management network element. PDU session;

Alternatively, the session management network element receives second information sent by the terminal, and determines, according to the second information, that the at least one PDU session is a PDU session capable of entering a sleep state; wherein the second information includes the Identification information of at least one PDU session and information indicating that the at least one PDU session can enter a sleep state;

Alternatively, the session management network element receives the second information sent by the terminal, and according to at least one of the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element and the The second information determines that the at least one PDU session is a PDU session capable of entering a sleep state; wherein the second information includes identification information of the at least one PDU session and a message indicating that the at least one PDU session is capable of entering a sleep state. information.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The session management network element receives third information sent by the access network device; wherein the third information includes identification information of one or more PDU sessions, and the one or more PDU sessions are Determined in the at least one PDU session; the third information is used to indicate that the access network device has established a user plane air interface resource for the one or more PDU sessions.
A method for managing a protocol data unit PDU session, wherein the method includes:

The access network device receives the first information sent by the session management network element, wherein the first information includes identification information of at least one PDU session, and the at least one PDU session is a PDU initiated by the session management network element from a terminal. It is determined in the session that the at least one PDU session is in an activated state;

The access network device releases user plane air interface resources of the at least one PDU session according to the first information, and retains configuration information of the user plane air interface resources and a context of the at least one PDU session.
The method according to claim 5, further comprising:

The access network device sends fourth information to the terminal according to the first information; wherein the fourth information includes identification information of the at least one PDU session, and the fourth information is used to indicate the The terminal releases user plane air interface resources of the at least one PDU session, and retains configuration information of the user plane air interface resources and a context of the at least one PDU session.
The method according to claim 5 or 6, further comprising:

The access network device receives fifth information sent by the terminal; wherein the fifth information includes identification information of one or more PDU sessions, and the one or more PDU sessions are Determined in a PDU session;

The access network device establishes user plane air interface resources of the one or more PDU sessions according to the fifth information and configuration information of user plane air interface resources of the one or more PDU sessions.
The method according to claim 7, further comprising:

The access network device sends third information to the session management network element; wherein the third information includes identification information of the one or more PDU sessions; the third information is used to indicate the access The network device has established user plane air interface resources for the one or more PDU sessions.
The method according to any one of claims 5 to 8, wherein in the handover process, the access network device is a source access network device; the method further comprises:

The source access network device sends a context of the one or more PDU sessions to a target access network device.
A method for managing a protocol data unit PDU session, wherein the method includes:

Receiving, by a terminal, fourth information sent by an access network device; wherein the fourth information includes identification information of at least one PDU session determined by the session management network element from a PDU session initiated by the terminal, The at least one PDU session is in an active state;

The terminal releases user plane air interface resources of the at least one PDU session according to the fourth information, and retains configuration information of the user plane air interface resources and a context of the at least one PDU session.
The method according to claim 10, further comprising:

The terminal sends second information to the session management network element; wherein the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state, and the first The two pieces of information are used by the session management network element to determine the at least one PDU session from a PDU session initiated by the terminal.
The method according to claim 10 or 11, further comprising:

The terminal establishes user plane air interface resources of the one or more PDU sessions according to configuration information of user plane air interface resources of the one or more PDU sessions; wherein the one or more PDU sessions are Described in at least one PDU session;

The terminal sends fifth information to the access network device; wherein the fifth information includes identification information of the one or more PDU sessions, and the fifth information is used to instruct the access network device to establish User plane air interface resources for the one or more PDU sessions.
A session management network element, characterized in that the session management network element includes:

A processing unit, configured to determine at least one PDU session from the PDU sessions initiated by the terminal; wherein the at least one PDU session is in an activated state;

The transceiver unit is configured to send first information to the access network device; the first information includes identification information of the at least one PDU session, and the first information is used to instruct the access network device to release the at least one The user plane air interface resources of the PDU session retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.
The session management network element according to claim 13, wherein:

The processing unit is specifically configured to determine that the at least one PDU session belongs to any one of the following PDU sessions:

No data PDU session to be transmitted within a preset time period;

During the handover process, all QoS flows are rejected by the target access network device.

LADN PDU session when the terminal moves out of the local data network service area LADN;

When the terminal needs to enter the suspended state from the connected state, the PDU session is in an active state;

When the terminal moves out of the allowed range, it is in an active PDU session.
The session management network element according to claim 13 or 14, wherein the at least one PDU session is a PDU session capable of entering a sleep state;

The processing unit is specifically configured to determine that the at least one PDU session is capable of entering hibernation according to at least one of session management subscription data of the terminal, a policy of the terminal, and a local configuration of the session management network element. Stateful PDU session;

Alternatively, the transceiver unit is further configured to receive second information sent by the terminal, and the processing unit is specifically configured to determine, according to the second information, that the at least one PDU session is a PDU session capable of entering a sleep state; The second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state;

Alternatively, the transceiver unit is further configured to receive the second information sent by the terminal, and the processing unit is specifically configured to manage the subscription data of the terminal, the policy of the terminal, and the session management network element according to the terminal At least one of a local configuration and the second information determine that the at least one PDU session is a PDU session capable of entering a dormant state; wherein the second information includes identification information and a representation of the at least one PDU session. It describes the information that at least one PDU session can enter the sleep state.
The session management network element according to any one of claims 13 to 15, wherein

The transceiver unit is further configured to receive third information sent by the access network device; wherein the third information includes identification information of one or more PDU sessions, and the one or more PDU sessions are the Determined by the terminal from the at least one PDU session; the third information is used to indicate that the access network device has established a user plane air interface resource of the one or more PDU sessions.
An access network device, characterized in that the access network device includes:

The transceiver unit is configured to receive first information sent by the session management network element; wherein the first information includes identification information of at least one PDU session, and the at least one PDU session is initiated by the session management network element from a terminal. It is determined in the PDU session that the at least one PDU session is in an activated state;

A processing unit, configured to release user plane air interface resources of the at least one PDU session according to the first information, and retain configuration information of the user plane air interface resources and a context of the at least one PDU session.
The access network device according to claim 17, wherein:

The transceiver unit is further configured to send fourth information to the terminal according to the first information; wherein the fourth information includes identification information of the at least one PDU session, and the fourth information is used to indicate The terminal releases user plane air interface resources of the at least one PDU session, and retains configuration information of the user plane air interface resources and a context of the at least one PDU session.
The access network device according to claim 17 or 18, wherein:

The transceiver unit is further configured to receive fifth information sent by the terminal; wherein the fifth information includes identification information of one or more PDU sessions, and the one or more PDU sessions are sent by the terminal from Described in at least one PDU session;

The processing unit is further configured to establish user plane air interface resources of the one or more PDU sessions according to the fifth information and configuration information of user plane air interface resources of the one or more PDU sessions.
The access network device according to claim 19, wherein:

The transceiver unit is further configured to send third information to the session management network element; wherein the third information includes identification information of the one or more PDU sessions; and the third information is used to indicate the The access network device has established user plane air interface resources for the one or more PDU sessions.
The access network device according to any one of claims 17 to 20, wherein in the handover process, the access network device is a source access network device; and the transceiver unit is further configured to connect to a target. The network access device sends the context of the one or more PDU sessions.
A terminal device, characterized in that the terminal device includes:

The transceiver unit is configured to receive fourth information sent by the access network device; wherein the fourth information includes identification information of at least one PDU session, and the at least one PDU session is a PDU session initiated by the session management network element from the terminal It is determined that the at least one PDU session is in an activated state;

A processing unit, configured to release user plane air interface resources of the at least one PDU session according to the fourth information, and retain configuration information of the user plane air interface resources and a context of the at least one PDU session.
The terminal device according to claim 22, wherein

The transceiver unit is further configured to send second information to the session management network element; the second information includes identification information of the at least one PDU session and information indicating that the at least one PDU session can enter a sleep state, The second information is used by the session management network element to determine the at least one PDU session from a PDU session initiated by the terminal.
The terminal device according to claim 22 or 23, wherein

The processing unit is further configured to establish user plane air interface resources of the one or more PDU sessions according to configuration information of user plane air interface resources of the one or more PDU sessions; wherein the one or more PDU sessions are Determined by the terminal from the at least one PDU session;

The transceiver unit is further configured to send fifth information to the access network device; wherein the fifth information includes identification information of the one or more PDU sessions, and the fifth information is used to indicate the The access network device establishes user plane air interface resources of the one or more PDU sessions.
A system for managing a protocol data unit PDU session, comprising a session management network element according to any one of claims 13 to 16, and an access network device according to any one of claims 17 to 21, And a terminal device according to any one of claims 22 to 24.
A computer-readable storage medium, comprising computer instructions, which, when the computer instructions run on a computer, cause the method according to any one of claims 1 to 12 to be performed.