CN110519809A - Manage the methods, devices and systems of PDU session - Google Patents

Abstract

The embodiment of the present application discloses the methods, devices and systems of management PDU session, is related to field of communication technology, facilitates saving PDU session and enters the time required for activated state.This method comprises: session management network element initiates to determine that at least one PDU session, at least one PDU session are in activated state in the PDU session established from terminal；Session management network element sends the first information to access network equipment；The first information includes the identification information of at least one PDU session, the first information is used to indicate the user face interface-free resources that access network equipment discharges at least one PDU session, retains the configuration information of the user face interface-free resources of at least one PDU session and the context of at least one PDU session.

Description

Method, device and system for managing PDU sessions

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a method, device, and system for managing a protocol data unit (protocol data unit, PDU) session.

Background technique

A PDU session is a connection between a terminal and a data network (DN), and the terminal can initiate and establish multiple PDU sessions to connect to the same DN or different DNs. In the fifth generation (5rd generation, 5G) network architecture, the PDU session can be set to be activated or deactivated. When the PDU session is in the active state, the user plane air interface resource and the control plane resource of the PDU session have been established, and data can be transmitted between the terminal and the DN through the PDU session. When the PDU session is in the deactivated state, the user plane air interface resources and control plane resources of the PDU session retain some information, and the terminal and the DN cannot transmit data through the PDU session.

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

Contents of the invention

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

In a first aspect, a method for managing PDU sessions is provided. The method may include: the session management network element determines at least one PDU session from the PDU session initiated and established by the terminal; the at least one PDU session is in an active state; the session management network element sends first information to the 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 the user plane air interface resources of the at least one PDU session, and retain the configuration information of the user plane air interface resources and the context of the at least one PDU session.

Wherein, the at least one PDU session is a PDU session that needs to enter a dormant state among the active PDU sessions initiated and established by the terminal. How to determine that a PDU session needs to enter the dormant state is not limited in this application, and for specific examples, please refer to the specific implementation part 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 and established by the terminal.

It can be seen that in this technical solution, when the PDU session is in the active state, the session management network element can instruct the access network device 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 PDU session 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 resource of the PDU session according to the reserved configuration information of the user plane air interface resource of the PDU session, and there is no need to restart Get the context of the PDU session, thus helping to save the time required for the PDU session to enter the active state. In addition, the technical solution helps to select any one or more PDU sessions from the active state to the dormant state according to requirements, which increases the flexibility of managing PDU sessions.

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

In a possible design, the session management network element determines at least one PDU session from the PDU sessions initiated and established 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 In at least one of the local configurations, at least one PDU session is determined from the PDU sessions initiated and established by the terminal.

In a possible design, the session management network element determines at least one PDU session from the PDU session initiated and established by the terminal, which may include: the session management network element receives the second information sent by the terminal, and the session management network element receives the second information sent by the terminal, and the session management network element initiates and establishes 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 dormant state.

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

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

In a possible design, the at least one PDU session can enter a dormant state. The method may further include: the session management network element determines the at least one PDU session as a PDU session capable of entering a dormant state 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.

In a possible design, the at least one PDU session can enter a dormant 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 PDU session as a PDU session capable of entering a dormant state according to the second information; wherein the second information includes the identifier of the at least one PDU session information and information indicating that the at least one PDU session can enter a dormant state.

In a possible design, the at least one PDU session can enter a dormant 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 information 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 second information. The PDU session is a PDU session capable of entering a dormant 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 dormant state.

In a possible design, the method may further include: after the session management network element receives the response information of the first information sent by the access network device, modifying 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; where the third information includes identification information of one or more PDU sessions, and 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 user plane air interface resources of the one or more PDU sessions. In other words, the third information is used to indicate that the access network device has recovered the user plane air interface resources of the one or more PDU sessions. This possible design provides the steps performed by the session management network element during the restoration of the PDU session from the dormant state to the active state.

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

In the second aspect, a method for managing PDU sessions is provided. The method may include: the access network device receives 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 and established by the session management network element from the terminal Determined in the session, the at least one PDU session is in an active state; the access network 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 and the at least one PDU session context.

It can be seen that in this technical solution, when the PDU session is in the active state, the access network device can 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. In this way, when 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 resource of the PDU session, and does not need to reacquire the context of the PDU session , thus helping to save the time required for the PDU session to enter the active state. In addition, the technical solution helps to select any one or more PDU sessions from the active state to the dormant state according to requirements, which increases the flexibility of managing PDU sessions.

In a possible design, 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 instruct the terminal to release the at least one PDU session. The user plane air interface resource of the PDU session retains the configuration information of the user plane air interface resource 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 the active state, the access network device can 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, so that , 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 access network device receiving 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 The terminal determines from the at least one PDU session; the access network device establishes the user plane air interface resources 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. This possible design provides the steps performed by the access network device during the recovery process of the PDU session from the dormant state to the active state.

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

In a possible design, in the handover process, the above-mentioned 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 this possible design, optionally, the above access network device receives the fifth information sent by the terminal, specifically: the target access network device receives the fifth information sent by the terminal.

In a third aspect, a method for managing PDU sessions is provided. The method may include: the terminal receives 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 determined by the session management network element from the PDU session established by the terminal , the at least one PDU session is in an active state; 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 the active state, the access network device can 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, so that , 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 dormant 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 and established by the terminal. Optionally, this possible design may occur in the process of establishing a PDU session at the terminal, but of course it is not limited thereto. It can be seen that the embodiment of the present application supports the technical solution that the terminal reports to the session management network element that the PDU session can enter the dormant state.

In a possible design, the method may further include: the terminal establishes user plane air interface resources of the one or more PDU sessions according to configuration information of the user plane air interface resources of the one or more PDU sessions; wherein, the one or multiple PDU sessions are determined by the terminal from at least one PDU session; the terminal sends fifth information to the access network device; where 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 of the one or more PDU sessions. This possible design provides the steps performed by the terminal in the process of restoring the PDU session from the dormant 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 above. Specifically, the session management network element may be the session management network element described in the above first aspect.

In a possible design, the session management network element can be divided into functional modules according to the method provided in the first aspect above. For example, each functional module can be divided corresponding to each function, or two or more functions can be divided into integrated in one 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 in the first aspect is executed.

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

In a possible design, the functional modules of the access network device can be divided according to the method provided in the second aspect above, for example, each functional module can be divided corresponding to each function, or two or more functional modules can be divided into integrated in one 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 in the second aspect is executed.

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

In a possible design, the functional modules of the terminal device can be divided according to the method provided in the third aspect above, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one 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 the seventh aspect, the embodiment of the present application provides a system for managing PDU sessions, the system may include any session management network element provided in the fourth aspect above, any access network device provided in the fifth aspect above, And any terminal device provided in the sixth aspect above.

The embodiment of the present application also provides a processing device, which is used to implement the functions of the above-mentioned device (such as 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, the processor can be implemented by hardware or software, when implemented by hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor , implemented by reading software codes stored in a memory, which may be integrated in the processor or located outside the processor and exist independently.

The embodiment of the present application also provides a computer-readable storage medium, where computer instructions are stored on the computer-readable storage medium, and when the computer instructions are run on the computer, the computer is made to perform any of the above first to third aspects. One possible way.

The embodiment of the present application also provides a computer program product, which enables any one of the methods provided in the first aspect to the third aspect to be executed when the computer program product is run on a computer.

The present application also provides a chip system, which may include a processor, used for the communication device to implement the functions involved in the above aspects, for example, generate, receive, send, or process the data and and/or information. In a possible design, the chip system further includes a memory, and the memory is configured to store necessary program instructions and data of the communication device. The system-on-a-chip may consist of chips, or may include chips and other discrete devices. The system-on-a-chip can also be a device.

It can be understood that any device or system or computer storage medium or computer program product provided above is used to execute the corresponding method provided above. Therefore, the beneficial effects that it can achieve can refer to the corresponding method. 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, etc., all have non-transitory .

Description of drawings

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

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

FIG. 3 is an interactive schematic diagram 1 of a method for managing a PDU session provided by an embodiment of the present application;

FIG. 4 is a second interactive schematic diagram of a method for managing a PDU session provided by an embodiment of the present application;

FIG. 5A is a schematic diagram of a process of a terminal entering a suspended state from a connected state, that is, a ConnectionSuspend process provided by an embodiment of the present application;

FIG. 5B is a schematic diagram of a process of a terminal entering a connection state from a suspended state, that is, a ConnectionResume process provided by an embodiment of the present application;

FIG. 6A is a schematic diagram of a flow of a PDU session from an active state to a dormant state provided by an embodiment of the present application;

FIG. 6B is a schematic diagram of a PDU session transition from a dormant state to an active state according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a process for establishing a PDU session provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a session management network element provided by an embodiment of the present application;

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

FIG. 10 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a communication device to which the technical solution provided by the embodiment of the present application is applied.

Detailed ways

The technical solutions provided by 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 future communication systems. Of course, it may also be a long term evolution (long term evolution, LTE) system, an LTE evolution (LTE-Advanced, LTE-A) system, and the like. Taking the wireless communication system as an example of a 5G system, as shown in FIG. 1 , it is a schematic structural diagram of a communication system to which the technical solution provided by the embodiment of the present application is applicable.

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

The UE 10 communicates with the AMF network element 301 through a next generation network (next generation, 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 (N11 for short), and communicates with the PCF network element 303 through the N15 interface (N15 for short). The SMF network element 302 communicates with the PCF network element 303 through the N7 interface (N7 for short), communicates with the UPF network element 304 through the N4 interface (N4 for short), and communicates with the UDM network element 305 through the N10 interface (N10 for short). The UPF network element 304 communicates with the DN40 through the 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 various network elements, solid lines are used in FIG. 1 for illustration.

Terminal 10 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions; 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 (handheld), laptop computer (laptop computer), cordless phone (cordless phone) or wireless local loop (wireless local loop, WLL) station, machine type communication (machine type communication, MTC) terminal, user equipment (user equipment, UE), mobile station (mobile station, MS), terminal equipment (terminaldevice) or relay user equipment, etc. Wherein, the relay user equipment may be, for example, a 5G residential gateway (residential gateway, RG). For convenience of description, in this application, these devices are collectively referred to as terminals (terminal).

The RAN device 20 can be used to provide wireless connection, and is located between the terminal 10 and the core network 30 . The RAN device 20 may include, but is not limited to, a base station, an evolved base station (evolved node base station, eNB), a next generation base station (next generation node base station, gNB), a new radio base station (new radio eNB), a macro base station, a micro base station, a high Frequency base station or transmission and reception point (transmission and reception point, TRP), non-3GPP access network (such as WiFi) and/or non-3GPP interworking function (non-3GPP interworking function, N3IWF) and other equipment. It should be noted that the RAN device 20 hereinafter may be understood as a network element in the RAN, which will be described in a unified manner here, 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, selection of the SMF network element 302, and the like. The SMF network element 302 can be used for session management such as session establishment, modification and release, selection and control of the UPF network element 304, service and session continuity (service and session continuity) mode selection, and roaming services. The PCF network element 303 may be used to provide policy control services and acquire subscription information for policy decisions. The UPF network element 304 can be used to process events on the user plane, such as transmitting or routing data packets, detecting data packets, reporting traffic, processing quality of service (QoS), lawful interception, and storing downlink data packets. The UDM network element 305 can be used to store user subscription data and the like.

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

It can be understood that although not shown, the above-mentioned 5G network may also include other network elements, such as network slice selection function (network slice selection function, NSSF) network elements, network storage function (network repository function, NRF) network elements, authentication service Function (authentication server function, AUSF) network elements, application function (application function, AF) network elements, and capability exposure function network elements (network exposure function, NEF) network elements, etc., are not specifically limited in this application.

It should be noted that the name of the interface between network elements in FIG. 1 is just an example, and the name of the interface may be another name in a specific implementation, which is not limited in this embodiment of the present application.

It should be noted that each network element in Figure 1, such as terminal, RAN device, AMF network element, SMF network element, PCF network element, UPF network element, and UDM network element, is just a name, and the name does not constitute a 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 this embodiment of the present application. For example, an AMF network element may be replaced by an AMF or an AMF entity, and an SMF network element may also be replaced by an SMF or an SMF entity, etc., which are described in a unified manner here and will not be described in detail below.

In order to facilitate the 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 (connected) state and an idle (idle) state. Among them, a suspend state is proposed in the user plane transmission enhancement technology in the 4G network architecture. The pause state is a kind of idle state. Specifically, in the connection suspend (Connection Suspend) process, the context of the terminal and the context of the bearer are reserved, so that the terminal enters a suspended state. When the terminal has data to send, the bearer can be resumed through the Connection Resume process, so that the terminal enters the connected state without initiating a service request (Service Request) process, so that the bearer can be quickly resumed.

A PDU session is a connection between a terminal and a DN (ie, DN40 in FIG. 1 ), and is used to provide a PDU connection service. Wherein, the connection type may be an internet protocol (internet protocol, IP) connection, an Ethernet connection, or an unstructured data connection between networks. The PDU connection service supported by the 5G core network refers to the service that provides PDU exchange between the terminal and the DN determined by the 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 can initiate the establishment of a PDU session based on a group of core network elements (such as SMF network elements, PCF network elements, and UPF network elements, etc.).

As shown in FIG. 2 , it is a schematic diagram of a PDU session provided by the 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 the PDU session include active state, dormant state and deactivated state. Wherein, the dormant state is a state proposed by the embodiment of the present application that can be applied to, but not limited to, a PDU session in a 5G communication system. The name of the state of the PDU session does not define the state of the PDU session itself. The name of the dormant state of the PDU session is just an example. In a specific implementation, the dormant state of the PDU session may also have other names, for example, it may be the suspend state of the PDU session (Suspend State or Suspend Status or Pause Status).

When the PDU session is in the active state, the user plane resources (also called user plane connection) and control plane resources of the PDU session have been established, and the terminal and DN can transmit data through the PDU session. Wherein, the user plane resource may include a user plane air interface resource such as a data radio bearer (data radio bearer, DRB). The control plane resource may include a control plane air interface resource 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 tunnel information of the RAN device that the PDU session passes through and tunnel information of the UPF network element that the PDU session passes through, and the RAN device that the PDU session passes through Refer to Figure 2 for equipment and UPF network elements. Usually, 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 opposite end through the saved tunnel information of the opposite end.

When the PDU session is in the 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, the terminal and the DN cannot transmit data through the PDU session, and the RAN device and the terminal The configuration information of the user plane air interface resource and the context of the PDU session are reserved. Wherein, the configuration information of the user plane air interface resource refers to the configuration information used to establish the user plane air interface resource, and may include, for example, the configuration information of the DRB. The context of the PDU session retained in the RAN device may include, but is not limited to, at least one of the following: QoS information, identification information of the PDU session, tunnel information of the UPF network element, single network slice selection assistance information (single network slice selection assistance information, S- NSSAI), session aggregate maximum bit rate (aggregate maximum bitrate, AMBR), type of PDU session, etc. The context of the PDU session retained 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 (internet protocol version 4, IPv4) address or IPv6 prefix, session and service continuity Sex (wession and wervicecontinuity, SSC) mode, type of PDU session, etc. When the PDU session is in the dormant state, the context of the PDU session saved in the SMF network element and the UPF network element can be the same as that 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 the deactivated state, the user plane resources and control plane resources of the PDU session retain some information, and the terminal and DN cannot transmit 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, which may include but not limited to at least one of the following: QoS information, S-NSSA, DNN, type of PDU session, and the like. When the PDU session is in the deactivated state, the RAN device generally does not retain the context of the PDU session.

It can be seen from the above description that when the PDU session is in different states, the contexts of the PDU session reserved in different network elements may be different. It is described here in a unified manner, and will not be described in detail below. 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, etc.) retains certain information, which can be understood as: the network element itself stores the information, and does not release (or delete) the information. Or, it can be understood that the network element does not perform any operation on the information.

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

Table 1

It should be noted that Table 1 is only an example, which 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 the 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 it means that the above information 1-5 are not managed. For example, when the PDU session is in any of the above states, it does not mean that other information of the PDU session is not managed in the terminal, RAN device and UPF network element, for example, the identification information and status of the PDU session can also be managed. For example, when the PDU session is in any of the above 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 state of the PDU session.

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

Table 2

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

As shown in FIG. 3 , it is an interactive schematic diagram of a method for managing a PDU session provided by the embodiment of the present application. The method shown in FIG. 3 specifically provides a method for making the PDU session enter the dormant state from the active state. The method may include the steps of:

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

The technical solution provided in this embodiment can be applied to a scenario where the terminal is in a connected state. For example, it may be applied to a scenario where the terminal is always in the connected state (specifically, the terminal is always in the connected state during the execution of this embodiment), and may also 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 and established 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 and established by the terminal, in a possible implementation, when the SMF network element determines that the PDU session needs to enter the dormant state, the PDU session can be used as the PDU session in the at least one PDU session. of a PDU session. In this implementation manner, it may be considered (or defaulted): each PDU session initiated and established by the terminal (or each PDU session in an active state) can enter a dormant state. Wherein, the embodiment of the present application does not limit how to determine whether a PDU session needs to enter the sleep state. Here are a few possible examples:

As an example, when the PDU session has no data to be transmitted within a preset period of time (or within a certain period of time), it may be considered that the PDU session needs to enter a dormant state. For example, the UPF network element detects that the PDU session has no data transmission within a specified inactivity period (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 (QoS flow) of a PDU session are rejected by the target RAN device, such as the target next generation RAN (next generation RAN, NG-RAN) device, then the PDU session needs to enter dormancy state.

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

As an example, during the process in which the terminal enters the suspend state (that is, the connection suspend procedure (ConnectionSuspend procedure)), the PDU session initiated and established by the terminal needs to enter the dormant 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 PDU session in the active state initiated by the terminal needs to enter the dormant state . Wherein, 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 and established by the terminal needs to enter the dormant state, wherein the AMF network element can notify the SMF network element that the terminal has moved out of the allowed area.

For any PDU session in the active state initiated and established by the terminal, in another possible implementation, when the SMF network element determines that the PDU session needs to enter the dormant state and can enter the dormant state (that is, it has the ability to enter the dormant state attribute/function), the PDU session can be used as a PDU session in the at least one PDU session. In other words, each PDU session in the at least one PDU session is a PDU session capable of entering a dormant state. In this implementation manner, it can be considered that each PDU session (or each active PDU session) can enter the dormant state, which needs to be set before executing S101.

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

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

For example, the SMF network element determines that a PDU session can enter a dormant state according to the SM subscription data of the terminal. For example, the SMF network element determines that a PDU session can enter a dormant state according to the policy of the terminal. For example, the SMF network element determines that a PDU session can enter the dormant 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 dormant state according to the SM subscription data of the terminal and the policy of the terminal. For example, the SMF network element determines that a PDU session can enter a dormant state according to the SM subscription data 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 dormant 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 a dormant state according to the terminal's SM subscription data, the terminal's policy, and the local configuration of the SMF network element.

The SM subscription data of the terminal may include the SM subscription data stored locally by the SMF network element, and the SM subscription data of the terminal obtained by the SMF network element through information interaction with the UDM network element. The policy of the terminal may include the local policy of the SMF network element (for example, the policy configured by the operator on the SMF network element), and the policy configured by the PCF network element to the SMF network element. 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 through information exchange with the PCF network element. The local configuration of the SMF network element may include the locally stored policy of the SMF network element (that is, the local policy of the SMF network element), the locally stored subscription data of 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 dormant state, the SMF network element can consider that The PDU session can enter a dormant state. That is to say, the present application supports adding in any one or more of the SMF subscription 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 to indicate whether the PDU session able to enter the dormant state) information.

It should be noted that the information indicating that the PDU session can enter the dormant 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 dormant state is based on the granularity of the terminal, it means that the terminal initiated All established PDU sessions can enter the dormant state (for example, if the terminal has the ability to enhance user plane transmission, all PDU sessions initiated by the terminal can enter the dormant state); if the information indicating that the PDU session can enter the dormant state is based on If the PDU session granularity is set, it means that the PDU session can enter the dormant state.

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

The present application does not limit the specific process in which the mode 2 occurs, nor the specific signaling (or message) in which the second information is carried in the process. For example, manner 2 may occur during the process of establishing the PDU session, and in this case, the second information may be carried in a PDU session establishment (PDU Session Establishment) message.

The information indicating that the PDU session can enter the dormant state can be understood as indication information for indicating that the PDU session can enter the dormant state. Wherein, the present application does not limit the specific implementation manner of the information indicating that the PDU session can enter the dormant state. For example, the binary number "1" can be used to indicate that the PDU session can enter the dormant state, or the binary number "0" can be used to indicate that the PDU session can enter the dormant state. For another example, it may indicate that the PDU session can enter the dormant state by indicating that the PDU session has a user plane enhancement feature. Of course, the present application is not limited thereto.

It should be noted that, it is described here by taking an example in which the second information includes identification information of a PDU session and indication information indicating that the PDU session can enter a dormant state. During specific implementation, the second information may include identification information of multiple PDU sessions, and information indicating that the multiple PDU sessions can enter a dormant state. Wherein, the information indicating that multiple PDU sessions can enter the dormant state may be a collection of multiple information indicating that a single PDU session may enter the dormant state, or may be 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 the information indicating that PDU sessions 1, 2, and 3 can all enter The information of the dormant state may be a binary number "111". For another example, the second information may include: identification information of PDU sessions 1, 2, and 3, and a binary number "1", wherein the binary number "1" is information indicating that PDU sessions 1, 2, and 3 can all enter a dormant 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 dormant 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. Wherein, 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 relevant content in method 3, refer to the above, and will not repeat them here.

It can be understood that the SMF network element can save the information that the PDU session can enter the dormant state after determining that the PDU session can enter the dormant state, for example but not limited to, through any of the above methods 1 to 3, so that the PDU session needs to be determined later. When the session can enter the dormant state, directly query the stored information. For example, the SMF network element can add a flag bit for each PDU session managed to mark whether the PDU session can enter the dormant state. Based on this, when executing S101, the SMF network element queries the flag bit of the PDU session, It can be learned whether the PDU session can enter the dormant state.

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

S102: The SMF network element sends first information to the RAN device. Wherein, the first information may include identification information of the at least one PDU session, and the first information is used to instruct the RAN device to release the user plane air interface resource of the at least one PDU session, and reserve the configuration of the user plane air interface resource of the at least one PDU session information and 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 by the AMF network element.

S103: The RAN device receives 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 reserves 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 modify the state of the at least one PDU session from the active state to the dormant state.

S105: The RAN device sends fourth information to the terminal according to the first information. Wherein, the fourth information may include identification information of the at least one PDU session, and the fourth information is used to instruct the terminal to release the user plane air interface resources of the at least one PDU session, and to reserve 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.

S106: The terminal receives fourth information.

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

Optionally, after performing S107, the terminal may modify the state of the at least one PDU session from the active state to the dormant state.

The above S101-S107 describe the steps performed by the SMF network element, RAN device and terminal in the process of the PDU session changing from the active state to the dormant 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 changing from the active state to the deactivated state.

This embodiment provides a process for a PDU session to enter a dormant state from an active state. When a PDU session enters a dormant state, the configuration information of the user plane air interface resources of the PDU session and the context of the PDU session are retained in the terminal and/or RAN device , so that when data needs to be transmitted through the PDU session, the user plane air interface resource of the PDU session can be quickly restored according to the reserved configuration information of the user plane air interface resource of the PDU session, and the context of the PDU session does not need to be acquired again , thus helping 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 among the PDU sessions initiated and established by the terminal, and then triggers the at least one PDU session to enter the dormant state. That is to say, the PDU session can be changed from the active state to the dormant state based on the granularity of the PDU session. In this way, it is helpful to select any one or more PDU sessions from the active state to the dormant state according to requirements, which increases the flexibility of managing PDU sessions.

As shown in FIG. 4 , it is an interactive schematic diagram of a method for managing a PDU session provided by the embodiment of the present application. The method shown in FIG. 4 specifically provides a method for making the PDU session enter the active state from the dormant state. The method may include the steps of:

S201: The terminal establishes (or recovers) the user plane air interface resource of the PDU session according to configuration information of the user plane air interface resource of the PDU session. Wherein, the PDU session is a PDU session initiated and established by the terminal and is in a dormant state, for example, it 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 user plane air interface resources of the PDU session reserved in the terminal when the PDU session enters a dormant state.

Optionally, the terminal may determine that the PDU session needs to enter the active state when determining that it needs to transmit data through the PDU session in the dormant state, for example, when the terminal needs to send data to the DN or receive data sent by the DN through the PDU session in the dormant state, Thus triggering the execution of S201.

In this embodiment, one PDU session is changed from the dormant state to the active state as an example for illustration. Of course, multiple PDU sessions can also be changed from the dormant 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 dormant state to the active state.

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

S203: The RAN device receives fifth information.

S204: The RAN device establishes the user plane air interface resource of the PDU session according to the fifth information and the configuration information of the user plane air interface resource of the PDU session. Wherein, the configuration information is the configuration information of the user plane air interface resource of the PDU session reserved in the RAN device when the PDU session enters the dormant state.

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

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

S206: The SMF network element receives the third information. Optionally, after performing S206, the SMF network element may modify the state of the PDU session from the dormant state to the active state.

The above S201-S206 describe the steps performed by the SMF network element, the RAN device and the terminal in the process of the PDU session changing from the dormant 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 process of the PDU session changing from the deactivated state to the activated state.

This embodiment provides a process for a PDU session to enter an active state from a dormant state. When data needs to be transmitted through a PDU session in a dormant state, the network can quickly restore the PDU session according to the reserved 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 reacquire 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 a PDU session can be changed from a dormant state to an 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 session 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.

It can be understood that when the terminal is in the connected state, it may be necessary to perform a switching process, that is, the process triggered by the source RAN device needs to switch from "connecting the terminal to the source RAN device" to "connecting the terminal to the target RAN device". In this case, The RAN device storing the context of the PDU session in the dormant state is specifically the source RAN device. Optionally, when performing the handover process, the source RAN device may first determine that the terminal initiates the established PDU session that is in a dormant state, 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 changed from the dormant state to the active state, the terminal may send information (such as the fifth information above) used to indicate the user plane air interface resource for establishing the PDU session to the target RAN device. 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 will be described below through a specific example.

As shown in FIG. 5A , it is a schematic diagram of a flow of a terminal entering a suspended state from a connection state, that is, a Connection Suspend flow, provided by an embodiment of the present application. The process may include a process of changing at least one PDU session initiated by the terminal from an active state to a dormant state, and/or a process of changing other PDU sessions initiated by the terminal from an active state to a deactivated state. The following is an example of a process including: changing at least one PDU session initiated by the terminal from the active state to the dormant state, and changing other PDU sessions initiated by the terminal from the active state to the deactivated state. The method shown in Figure 5A may include the following steps:

S301: The RAN device sends a UE Context Suspend Request (UE Context SuspendRequest) message to the AMF network element. Wherein, the terminal context suspend request message is used to request to change the state of the terminal from the activated state to the suspended state. The terminal context suspend request message may carry a PDU session identification (identity, ID) list, and may also carry a cause value (Cause), etc. The cause value may be that the terminal needs to enter the suspend 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 regarded as a specific realization of the identification information of the PDU session.

S302: The AMF network element reserves the context of the terminal according to the terminal context suspension request message. The AMF network element sends an update session management context (Nsmf_PDUSession_UpdateSMContext) message to the SMF(s) network element (ie, one or more SMF network elements). The update session management context message can carry the ID of one or more PDU sessions, and the ID of the one or more PDU sessions belongs to the PDU session ID list described in S301; in addition, it can also carry a reason value, etc., and the reason value can be required by the terminal. into a pause state.

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

For example, in combination with the example shown in FIG. 3 , in the above S101, it can be considered that "at least one PDU session ID" in S101 is specifically the "PDU session ID list" in this embodiment, that is, it is considered that each session initiated by the terminal is in an active state. All PDU sessions need to enter the dormant state. However, optionally, not every PDU session can enter a PDU session, therefore, it is necessary to determine which PDU session can enter a dormant 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 a dormant state.

Specifically, for any PDU session, the SMF network element can determine whether the PDU session can into sleep mode. For example, based on the example in S302, SMF network element 1 can query the target flags of PDU sessions 1-3 to determine whether PDU sessions 1-3 can enter the dormant state; SMF network element 2 can query the target flags of PDU session 4 , so as to determine whether the PDU session 4 can enter the dormant state.

S304: The SMF(s) network element sends an N4 session modification request (N4Session ModificationRequest) 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 equipment tunnel information passed by one or more PDU sessions. 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 identifiers of PDU sessions 1-3, and the N4 session modification request message carries the RAN Tunnel information of the device; the SMF network element 2 can send an N4 session modification request message to the UPF network element managing the tunnel identifier of the PDU session 4, and the N4 session modification request message carries the tunnel information of the RAN device through which the PDU session 4 passes. Wherein, the UPF network element managing the tunnel ID of PDU sessions 1-3 and the UPF network element managing the tunnel ID of PDU session 4 may be the same or different. The RAN device managing PDU sessions 1-4 is the RAN device in S301 above.

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 (N4Session Modification Response) message to the SMF(s) network element.

No matter whether the PDU session enters the deactivated state from the active state or enters the dormant state from the active state, for the UPF network element that manages the PDU session, it is necessary 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-S305 and S303. For example, S304-S305 may be executed first, and then S303 may be executed, or S304-S305 may be executed first, and then S303 may be executed, or S303 may be executed during the execution of S304-S305.

S306: The SMF(s) network element sends an update session management context response (Nsmf_PDUSession_UpdateSMContext Response) message to the AMF network element. Wherein, the update session management context response message carries the ID of the PDU session that needs to enter the dormant state, and the ID of the PDU session that needs to enter the deactivated state. Wherein, 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 the "indication information" is the same, and the two can be used interchangeably, or the message name can also be used to indicate that the PDU session needs to enter a certain state, which is not limited in this application. In any embodiment of the present application, "the message carries the ID of the PDU session that needs to enter another state from one state" and "the message carries the ID of the PDU session and indicates that the PDU session needs to enter from the one state The indication information of the PDU session in another state has the same meaning, and the two can be used interchangeably, or the message name can also be used to indicate that the PDU session needs to enter a certain state from a certain state, which is not limited by the present application. Wherein, The message here may be, for example but not limited to, an update session management context response message, a terminal context suspension response message, etc., and the state here may be an active 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 dormant state, and PDU session 3 cannot enter the dormant state, then in S306, the update session management context response sent by SMF network element 1 to the AMF network element The message carries the following information: the PDU sessions that can enter the sleep state are PDU sessions 1 and 2, and the 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 dormant state, then 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 that can enter the dormant state is the PDU session 4 .

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

For example, in combination with the example shown in Figure 3, it can be considered that S306-S307 are the specific implementation of the above S102. Specifically, it can be considered that the first information is carried in the update session management context response message and sent by the SMF network element to the AMF network element, and then It is carried in the terminal context suspension response message and sent by the AMF network element to the RAN device.

S308: According to the context suspension response message, the RAN device releases the user plane air interface resources of the PDU session for each PDU session that needs to enter the dormant state (such as the above PDU session 1, 2, 4), and retains the configuration of the user plane air interface resources information and the context of the PDU session, and optionally, modify the state of the PDU session from the active state to the dormant state. And, for each PDU session that needs to enter the deactivated state (such as the above-mentioned PDU session 3), release the user plane air interface resource of the PDU session, the configuration information of the user plane air interface resource and the context of the PDU session, optionally, Change the state of the PDU session from the activated state to the deactivated state.

During specific implementation, the RAN device may retain the context of the terminal according to the context suspension response message, and generate a Resume ID for the terminal, wherein 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 executing the ConnectionResume process subsequently, 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 when executing the Connection Resume process, the new RAN device usually needs to send the terminal's Resume ID 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 suspend (Connection Suspend) message to the terminal. Wherein, the RRC connection suspension message may carry the ID of the PDU session that needs to enter the dormant state, and the ID of the PDU session that needs to enter the deactivated state.

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

S310: According to the RRC connection suspend message, for each PDU session that needs to enter the dormant state, the terminal 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. Optionally, Change the state of the PDU session from the active state to the dormant state. And, for each PDU session that needs to enter the deactivated state, release the user plane air interface resource of the PDU session, the configuration information of the user plane air interface resource and the context of the PDU session, optionally, the state of the PDU session is changed by The activated state is changed to the deactivated state.

In this embodiment, any one or more PDU sessions initiated and established by the terminal can be changed from the active state to the dormant state during the process of the terminal entering the suspended state from the connected state. For the description about the beneficial effect of this embodiment, reference may be made to the above.

Optionally, in another embodiment provided by this application, the PDU session ID list in S301 above includes IDs of PDU sessions that can enter a dormant state. In this embodiment, the SMF network element can notify the RAN device in advance of whether the PDU session can enter the dormant state. In this way, when the RAN device executes S301, the PDU session ID list can be set to include the PDU session that can enter the dormant state. ID. In this case, the above S303 does not need to be executed. Optionally, since the SMF network element can notify the RAN device in advance of whether the PDU session can enter the dormant state, after the RAN device confirms that the terminal needs to enter the suspended state and determines the PDU session ID list, release the list. Indicate the 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, and do not need to release the PDU session after receiving the context suspension 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 , it is a schematic diagram of a flow of a terminal entering a connection state from a suspend state, that is, a Connection Resume flow, provided by the embodiment of the present application. The process may include a process of changing at least one PDU session initiated by the terminal from a dormant state to an active state, and/or a process of changing other PDU sessions initiated by the terminal from a deactivated state to an active state. In the following, the process includes: changing at least one PDU session initiated and established by the terminal from the dormant state to the active state as an example for illustration. The method shown in Figure 5B may include the following steps:

S401: The terminal determines that it needs to enter the connection state from the pause state. For example, when there is data to be transmitted, such as sending data to the DN or receiving data sent by the DN, it is determined that it needs to enter the connection state from the pause state.

S402: The terminal determines whether one or more PDU sessions that need to transmit data are currently in a dormant state or a deactivated state. Wherein, the one or more PDU sessions may be part or all of the PDU sessions initiated and established by the terminal. The PDU session currently in the dormant state is a PDU session that needs to enter the active state from the dormant state.

It can be understood that the process for the terminal to enter the connection state from the suspended state may also include entering the PDU session that needs to transmit data and is in the deactivated state into the active state. The specific implementation method can refer to the existing technology, and will not be repeated here.

S403: The terminal sends an RRC connection resume request (Connection Resume Request) message to the RAN device. Wherein, the RRC connection 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 the dormant state to the active state. The RRC connection recovery request message is used to request recovery of the control plane air interface resources between the terminal and the RAN device and the 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 exchange information, respectively establish (or restore) the PDU session according to the configuration information of the user plane air interface resources of the PDU session reserved by itself The air interface resources of the user plane, the terminal and the RAN device establish the air interface resources of the control plane by exchanging information. Optionally, the terminal and the RAN device may respectively change the state of each PDU session that needs to change from the dormant state to the active state from the dormant state to the active state.

For example, with reference to the embodiment shown in FIG. 4 , it can be considered that information exchange is performed between the terminal and the RAN device, including that the terminal in FIG. 4 sends 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 (Connection Response Response) message to the terminal.

After S405 is executed, uplink data transmission can be performed between the terminal and the DN 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 Resume Request (UE Context ResumeRequest) message to the AMF network element. Wherein, 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 the dormant state to the active state. The terminal context recovery request message is used to indicate that the user plane air interface resources of the one or more PDU sessions have been recovered. 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. Wherein, the update session management context message may carry the ID of the PDU session that needs to enter the active state from the dormant 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 the SMF(s) network element receives the update session management context message, it can 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. Wherein, 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 update session management context message.

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 S409 is executed, downlink data transmission can be performed between the terminal and the DN 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 modifies the state of the one or more PDU sessions from a dormant state to an active state.

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

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

In this embodiment, any one or more PDU sessions initiated and established by the terminal can be changed from the dormant state to the active state during the process of the terminal entering the connected state from the suspended state. For the description about the beneficial effect of this embodiment, reference may be made to the above.

As shown in FIG. 6A , it is a schematic diagram of a flow of a PDU session from an active state to a dormant state according to an embodiment of the present application. During this process, the terminal is always in the connected state. The method shown in Figure 6A may include the following steps:

S501: The SMF network element determines that one or more PDU sessions need and can enter a dormant state. Wherein, the one or more PDU sessions are part or all of the active PDU sessions initiated and established by the terminal.

For how the SMF network element determines that a PDU session needs to enter the dormant state from the connected state, and the specific implementation method that can enter the dormant state from the connected state can refer to the above, and will not be repeated here. It can be understood that, in the case of no obvious conflict, any of the specific implementation manners 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 to be deleted 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 transfer (Namf_Communication_N1N2MessageTransfer) signaling to the AMF network element. Wherein, 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 dormant state.

S505: The AMF network element sends an N2 session request (N2Session Request) message to the RAN device. Wherein, the N2 session request message may carry IDs of the one or more PDU sessions, and indication information for the one or more PDU sessions to enter a dormant state.

For example, in combination with the embodiment shown in FIG. 3 , it can be considered that S504-S505 are the specific implementations 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, and then 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 resource of the PDU session, and retains the configuration information of the user plane air interface resource and the context of the PDU session. The RAN device modifies the state of the PDU session from the active state to the dormant state.

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

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

S508: For each PDU session in the one or more PDU sessions, the terminal releases the user plane air interface resource of the PDU session, and retains the configuration information of the user plane air interface resource 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 (N2Session 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 can be changed from the active state to the dormant state. For the description about the beneficial effect of this embodiment, reference may be made to the above.

As shown in FIG. 6B , it is a schematic diagram of a flow of a PDU session from a dormant state to an active state according to an embodiment of the present application. During this process, the terminal is always in the connected state. The method shown in Figure 6B may include the following steps:

S601: The terminal determines that one or more PDU sessions need to be changed 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 From dormant state to active state.

S602: The terminal sends a PDU session recovery 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 the dormant state to the active state. The PDU session recovery request message is used to request recovery of the user plane air interface resources of the one or more PDU sessions.

S603: For each PDU session in the recovery of the one or more PDUs, the terminal and the RAN device respectively establish the user plane air interface of the PDU session according to the configuration information of the user plane air interface resources of the PDU session retained by the terminal through information exchange resource. In addition, the terminal and the RAN device can respectively change the state of each PDU session that needs to change from the dormant state to the active state from the dormant state to the active state.

For example, with reference to the embodiment shown in FIG. 4 , it can be considered that information exchange is performed between the terminal and the RAN device, including that the terminal in FIG. 4 sends 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 recovery response message to the terminal.

After S604 is executed, uplink data transmission can be performed between the terminal and the DN 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 recovery request message to the AMF network element. Wherein, the PDU session 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 the dormant state to the active state. The PDU session context restore request message is used to request to restore 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. Wherein, the update session management context 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 dormant 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 the SMF(s) network element receives the update session management context message, it can 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. Wherein, 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 the PDU session carried by the update session management context message is carried.

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 S608 is executed, uplink data transmission can be performed between the terminal and the DN 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 modifies the state of each PDU session in the one or more PDU sessions from the dormant state to the 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 can be changed from the dormant state to the active state. For the description about the beneficial effect of this embodiment, reference may be made to the above.

As shown in FIG. 7 , it is a process of establishing a PDU session provided by the embodiment of this application. The method may include the steps of:

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

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

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

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

Any one of the steps above S703 and S704 is optional.

S705: The SMF network element determines whether the PDU session can enter a dormant state according to at least one of the terminal's SM subscription data, the terminal's policy, the local configuration of the SMF network element, and the user plane transmission enhancement instruction. Wherein, the specific implementation manner of this step and 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 a dormant state. How the SMF network element records whether the PDU session can enter the dormant 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 can send an indication that the PDU session can enter the sleep state (or an indication that the PDU session cannot enter the sleep state) to the SMF network element during the process of initiating the establishment of the PDU session. , so that when the SMF network element needs to determine whether the PDU session can enter the dormant state, it can directly query the recorded information. Directly querying the recorded information may, but is not limited to, be applied to any of the above-mentioned related embodiments.

It should be noted that the above describes the process of changing the PDU session from the active state to the dormant state, and the process of restoring (or entering) the PDU session from the dormant state to the active state. It can be understood that in a 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 subscription data of the terminal is changed and other reasons make one or some PDU sessions change from being able to enter the dormant state to being unable to enter the dormant state, if the PDU session is currently in the dormant state, then optionally, the The PDU session enters the deactivated state from the dormant state. For example, but not limited to, when one or some PDU sessions are changed from being unable to enter the dormant state to being able to enter the dormant state due to reasons such as changes in the subscription data of the terminal, if the PDU session is currently in the deactivated state, the The PDU session enters the dormant state from the deactivated state. Other examples are not listed one by one. In addition, the embodiment of the present application does not limit the process of the PDU session entering the deactivated state from the dormant state, and the process of entering the dormant state from the deactivated state.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of methods. In order to realize the above functions, it includes corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art should easily realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The embodiment of the present application can divide the functional modules of the device for managing PDU sessions (including session management network elements such as SMF network elements, access network equipment such as RAN equipment, and terminal devices such as terminals) according to the above-mentioned method examples. For example, it can correspond to Each function is divided into each function module, and two or more functions can also be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.

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

The processing unit 801 is configured to determine at least one PDU session from the PDU sessions initiated and established by the terminal; where at least one PDU session is in an active 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 the user plane air interface resources of at least one PDU session, and reserve Configuration information of user plane air interface resources and context of at least one PDU session.

For example, with reference to 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 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 with no data to be transmitted within a preset time period; The PDU session rejected by the target access network device; the LADN PDU session when the terminal moves out of LADN; the PDU session in the active state when the terminal needs to enter the suspended state from the connected state; the PDU in the active state when the terminal moves out of the allowed range session.

Optionally, the processing unit 801 may be specifically configured to: determine at least one PDU from the PDU session initiated and established 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 session.

Optionally, the transceiving unit 802 may also be configured to receive second information sent by the terminal. In this case, the processing unit 801 can be specifically configured to: determine at least one PDU session from the PDU sessions 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 at least one PDU session can Information about entering the dormant state.

Optionally, the transceiving unit 802 may also be configured to receive second information sent by the terminal. In this case, the processing unit 801 can be specifically configured to: initiate and establish the PDU session from the terminal according to at least one of the terminal's session management subscription data, the terminal's policy, the local configuration of the session management network element 8, and the second information. Determine at least one PDU session; wherein, the second information includes identification information of at least one PDU session and information indicating that at least one PDU session can enter a dormant state.

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

Optionally, the at least one PDU session can enter a dormant state. The transceiver unit 802 may also be configured to receive second information sent by the terminal, and the processing unit 801 may specifically be configured to determine the at least one PDU session as a PDU session capable of entering a dormant state according to the second information; 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 dormant state;

Optionally, the at least one PDU session can enter a dormant state. The transceiver unit 802 may also be configured to receive the second information sent by the terminal, and the processing unit 801 may specifically be 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, and the first The second information determines that the at least one PDU session is a PDU session capable of entering a dormant 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 dormant state.

Optionally, the transceiver unit 802 may also be 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 information from the terminal at least one Determined in the PDU session; the third information is used to indicate that the access network device has established one or more user plane air interface resources of the PDU session. For example, referring to FIG. 4 , the transceiver unit 802 may be used to execute S206.

For the explanation of the relevant content in the session management network element provided in the embodiment of the present application and the technical effects that can be obtained, reference may be made to the above method embodiment, and details are not repeated here.

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

The transceiver unit 901 is configured to receive the first information sent by the session management network element; wherein, the first information includes identification information of at least one PDU session, and at least one PDU session is determined by the session management network element from the PDU session established 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 user plane air interface resources and context of at least one PDU session.

For example, referring to 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 also be configured to send fourth information to the terminal according to the first information; wherein, 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 resource, retains the configuration information of the user plane air interface resource and the context of at least one PDU session. For example, referring to FIG. 3 , the transceiver unit 901 may be used to execute S105.

Optionally, the transceiver unit 901 may also be 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 information obtained by the terminal from at least one PDU session definite. In this case, the processing unit 902 may be further configured to, according to the fifth information and the configuration information of the user plane air interface resources of the one or more PDU sessions, establish the user plane air interface resources of the one or more PDU sessions. For example, referring to FIG. 4 , the transceiver unit 901 may be used to perform S203, and the processing unit 902 may be used to perform S204.

Optionally, the transceiving unit 901 may also be 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 user plane air interface resources of the one or more PDU sessions. For example, referring to FIG. 4 , the transceiver unit 901 may also be used to execute S205.

Optionally, in the handover process, the access network device 9 is the source access network device. In this case, the transceiving 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 transceiving unit 901 may also be configured to receive fifth information sent by the terminal, specifically: the target access network device receives the fifth information sent by the terminal. The transceiving unit 901 may also be 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 the relevant content in the access network device provided in the embodiment of the present application and the technical effects that can be obtained, reference may be made to the foregoing method embodiment, and details are not repeated here.

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

The transceiver unit 1001 is configured to receive the fourth information sent by the access network device; wherein the fourth information includes identification information of at least one PDU session, and at least one PDU session is a PDU session initiated and established 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 user plane air interface resources of at least one PDU session according to the fourth information, and retain configuration information of user plane air interface resources and context of at least one PDU session.

For example, referring to FIG. 3 or FIG. 4 , the terminal device 10 may be the terminal in FIG. 3 or 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 also be 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 at least one PDU session can enter a dormant state, and the second information uses At least one PDU session is determined from the PDU sessions established by the session management network element from the terminal device 10 .

Optionally, the processing unit 1002 may also be configured to, according to configuration information of user plane air interface resources of one or more PDU sessions, establish user plane air interface resources of one or more PDU sessions; wherein, 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 can also be configured to send fifth information to the access network device; wherein, 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 a or user plane air interface resources for multiple PDU sessions. For example, referring to 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 relevant content in the terminal device provided in the embodiment of the present application and the technical effects that can be obtained, reference may be made to the foregoing method embodiment, and details are not repeated here.

As shown in FIG. 11 , it is a schematic structural diagram of a communication device to which the technical solution provided in the embodiment of the present application is 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 session management network element 8 , access network device 9 or terminal device 10 provided above. For example, referring to any one of FIGS. 8 to 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 (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more devices used to control the program execution of the application program integrated circuit.

Communications link 1102 may include a pathway for communicating information between the components described above.

The memory 1103 may be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or other types that can store information and instructions The dynamic storage device can also be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a read-only disc (compactdisc 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.), magnetic 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 stored by a computer Any other medium, but not limited to.

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 (wireless local area networks, WLAN) and so on.

Wherein, the memory 1103 is used to store computer-executed instructions for implementing the solutions of the present application, and the execution is controlled by the processor 1101 . The processor 1101 is configured to execute computer-executed instructions stored in the memory 1103, so as to implement the methods provided in the following embodiments of the present application.

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

Optionally, the memory 1103 may exist independently and be connected to the processor 1101 through the 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, for example, CPU0 and CPU1 in FIG. 11 .

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

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

The aforementioned communication device 11 may be a general-purpose device or a special-purpose device. In a specific implementation, the communication device 11 can be a desktop computer, a portable computer, a network server, a palm computer (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 . The embodiment of the present application does not limit the type of the communication device 11 .

For the relevant steps executed by the processor in the communication device provided in the embodiment of the present application, as well as explanations and technical effects that can be obtained, reference may be made to the foregoing method embodiments, and details are not repeated here.

The embodiment of the present application also provides a system for managing PDU sessions. 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 session initiated and established by the terminal; the at least one PDU session is in an active state; and, send the 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, 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 determining at least one PDU session from the PDU sessions initiated and established by the terminal, which may include: the session management network element determines the session according to the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element. The at least one PDU session is determined from the PDU session initiated and established by the terminal.

Optionally, the terminal may also be 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 dormant state. The session management network element can 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 and established by the terminal may include: the session management network element determines the at least one PDU session from the PDU sessions initiated and established by the terminal according to the second information.

Optionally, the terminal may also be 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 dormant state. The session management network element can also be used to receive the second information sent by the terminal. In this case, the session management network element executes determining at least one PDU session from the PDU sessions initiated and established by the terminal, which may include: the session management network element determines the session according to the terminal's session management subscription data, the terminal's policy, and the local configuration of the session management network element. At least one of the 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 also be 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, release user plane air interface resources of the at least one PDU session according to the fourth information, and retain configuration information of 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 dormant state.

Optionally, the terminal may also be 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 obtained by the terminal from the determined in at least one PDU session; and, sending fifth information to the access network device; where the fifth information includes identification information of the one or more PDU sessions. The access network device may also be configured to receive 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 resource.

Optionally, the access network device may also be used 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 can also be used to receive the third information sent by the access network device.

For the explanation of the relevant content in the PDU session management system provided by the embodiment of the present application and the technical effects that can be obtained, refer to the above method embodiment, and details are not repeated here.

In the description of this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this article is just a description of the relationship between associated objects, Indicates that there may be three relationships, for example, A and/or B, may indicate: A exists alone, A and B exist simultaneously, and B exists alone.

In the description of the present application, unless otherwise specified, "plurality" means two or more than two.

In addition, in order to clearly describe 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 with basically the same function and effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not necessarily limit the difference.

In addition, in the description of the present application, unless otherwise specified, "at least one" means any one or any combination of multiples, and "at least one" means any one or any combination of multiples. For example, at least one of A, B and C may include the following situations: ①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 for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application. With the evolution and emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

In the above embodiments, all or part of them may be implemented 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 computer-executed instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server, or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or may be a data storage device including one or more servers, data centers, etc. that can be integrated with the medium. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.

Although the present application has been described in conjunction with various embodiments here, however, in the process of implementing the claimed application, those skilled in the art can understand and 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. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that these measures cannot be combined to advantage.

Although the application has been described in conjunction with specific features and embodiments thereof, it will be 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 illustrative of the application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of this application. Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (26)

1. a kind of method of management agreement data cell PDU session, which is characterized in that the described method includes:

Session management network element initiates to determine at least one PDU session in the PDU session established from terminal；Wherein, described at least one A PDU session is in activated state；

The session management network element sends the first information to access network equipment；The first information includes at least one described PDU The identification information of session, the first information are used to indicate the use that the access network equipment discharges at least one PDU session Family face interface-free resources retain the configuration information of user face interface-free resources and the context of at least one PDU session.

2. the method according to claim 1, wherein the session management network element initiates the PDU established from terminal At least one PDU session is determined in session, comprising:

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

The PDU session for needing to transmit without data in preset time period；

In switching flow, all service quality streams are all by the PDU session of target access network equipment refusal；

LADN PDU session when the terminal is out of local data network coverage LADN；

When the terminal needs to be entered by connected state pause state, the PDU session in activated state；

The terminal out of permission range when, the PDU session in activated state.

3. method according to claim 1 or 2, which is characterized in that at least one described PDU session is to be able to enter suspend mode The PDU session of state, the method also includes:

The session management network element is according to the session management subscription data of the terminal, the tactful and described session pipe of the terminal At least one of being locally configured for network element is managed, determines that at least one described PDU session is to be able to enter the PDU meeting of dormant state Words；

Alternatively, the session management network element receives the second information that the terminal is sent, according to second information determination At least one PDU session is to be able to enter the PDU session of dormant state；Wherein, second information includes at least one described PDU The identification information of session and at least one described PDU session of expression are able to enter the information of dormant state；

Alternatively, the session management network element receives the second information that the terminal is sent, according to the session management label of the terminal About the tactful and described session management network element of data, the terminal at least one of be locally configured and second information Determine that at least one described PDU session is to be able to enter the PDU session of dormant state；Wherein, second information include it is described extremely The identification information of a few PDU session and at least one described PDU session of expression are able to enter the information of dormant state.

4. method according to any one of claims 1 to 3, which is characterized in that the method also includes:

The session management network element receives the third information that the access network equipment is sent；Wherein, the third information includes one The identification information of a or multiple PDU sessions, one or more of PDU sessions are the terminals from least one described PDU meeting It is determined in words；The third information is used to indicate the use that one or more of PDU sessions have been established in the access network equipment Family face interface-free resources.

5. a kind of method of management agreement data cell PDU session, which is characterized in that the described method includes:

Access network equipment receives the first information that session management network element is sent；Wherein, the first information includes at least one PDU The identification information of session, at least one described PDU session are that the session management network element is initiated in the PDU session established from terminal Determining, at least one described PDU session is in activated state；

The access network equipment discharges the user face interface-free resources of at least one PDU session, protects according to the first information Stay the configuration information of user face interface-free resources and the context of at least one PDU session.

6. according to the method described in claim 5, it is characterized in that, the method also includes:

The access network equipment sends the 4th information according to the first information, Xiang Suoshu terminal；Wherein, the 4th packet The identification information of at least one PDU session is included, the 4th information is used to indicate at least one described in the terminal release The user face interface-free resources of PDU session, retain user face interface-free resources configuration information and at least one described PDU session Context.

7. method according to claim 5 or 6, which is characterized in that the method also includes:

The access network equipment receives the 5th information that the terminal is sent；Wherein, the 5th information includes one or more The identification information of PDU session, one or more of PDU sessions are that the terminal is determined from least one described PDU session 's；

The access network equipment is matched according to the 5th information and the user face interface-free resources of one or more of PDU sessions Confidence breath, establishes the user face interface-free resources of one or more of PDU sessions.

8. the method according to the description of claim 7 is characterized in that the method also includes:

The access network equipment sends third information to the session management network element；Wherein, the third information includes described one The identification information of a or multiple PDU sessions；The third information be used to indicate the access network equipment have been established it is one or The user face interface-free resources of multiple PDU sessions.

9. according to the described in any item methods of claim 5 to 8, which is characterized in that in switching flow, the access network equipment It is source access network equipment；The method also includes:

The source access network equipment sends the context of one or more of PDU sessions to target access network equipment.

10. a kind of method of management agreement data cell PDU session, which is characterized in that the described method includes:

Terminal receives the 4th information that access network equipment is sent；Wherein, the 4th information includes the mark of at least one PDU session Know information, at least one described PDU session is that session management network element initiates to determine in the PDU session established from terminal, described At least one PDU session is in activated state；

The terminal discharges the user face interface-free resources of at least one PDU session according to the 4th information, described in reservation The context of the configuration information of user face interface-free resources and at least one PDU session.

11. according to the method described in claim 10, it is characterized in that, the method also includes:

The terminal sends the second information to the session management network element；Wherein, second information include it is described at least one The identification information of PDU session and at least one described PDU session of expression are able to enter the information of dormant state, and second information is used It initiates to determine at least one described PDU session in the PDU session established from the terminal in the session management network element.

12. method described in 0 or 11 according to claim 1, which is characterized in that the method also includes:

The terminal is established one or more according to the configuration information of the user face interface-free resources of one or more PDU sessions The user face interface-free resources of a PDU session；Wherein, one or more of PDU sessions be the terminal from it is described at least one It is determined in PDU session；

The terminal sends the 5th information to the access network equipment；Wherein, the 5th information includes one or more of The identification information of PDU session, the 5th information are used to indicate the access network equipment and establish one or more of PDU sessions User face interface-free resources.

13. a kind of session management network element, which is characterized in that the session management network element includes:

Processing unit determines at least one PDU session for initiating from terminal in the PDU session established；Wherein, described at least one A PDU session is in activated state；

Transmit-Receive Unit, for sending the first information to access network equipment；The first information includes at least one described PDU session Identification information, the first information is used to indicate the user face that the access network equipment discharges at least one PDU session Interface-free resources retain the configuration information of user face interface-free resources and the context of at least one PDU session.

14. session management network element according to claim 13, which is characterized in that

The processing unit is specifically used for: determine that at least one described PDU session belongs to following any PDU session:

The PDU session for needing to transmit without data in preset time period；

In switching flow, all service quality streams are all by the PDU session of target access network equipment refusal；

LADN PDU session when the terminal is out of local data network coverage LADN；

When the terminal needs to be entered by connected state pause state, the PDU session in activated state；

The terminal out of permission range when, the PDU session in activated state.

15. session management network element described in 3 or 14 according to claim 1, which is characterized in that at least one described PDU session is It is able to enter the PDU session of dormant state；

The processing unit is specifically used for: according to the session management subscription data of the terminal, the strategy of the terminal and described Session management network element at least one of is locally configured, and determines that at least one described PDU session is to be able to enter dormant state PDU session；

Alternatively, the Transmit-Receive Unit is also used to, the second information that the terminal is sent is received, the processing unit is specifically used for, Determine that at least one described PDU session is to be able to enter the PDU session of dormant state according to second information；Wherein, described Two information include the identification information of at least one PDU session and indicate that at least one described PDU session is able to enter suspend mode The information of state；

Alternatively, the Transmit-Receive Unit is also used to, the second information that the terminal is sent is received, the processing unit is specifically used for, According to the session management subscription data of the terminal, the terminal being locally configured of tactful and described session management network element in At least one and described second information determines that at least one described PDU session is to be able to enter the PDU session of dormant state；Its In, second information includes the identification information of at least one PDU session and indicates that at least one described PDU session can Into the information of dormant state.

16. 3 to 15 described in any item session management network elements according to claim 1, which is characterized in that

The Transmit-Receive Unit is also used to, and receives the third information that the access network equipment is sent；Wherein, the third information includes The identification information of one or more PDU sessions, one or more of PDU sessions are the terminals from least one described PDU It is determined in session；The third information is used to indicate the access network equipment and one or more of PDU sessions has been established User face interface-free resources.

17. a kind of access network equipment, which is characterized in that the access network equipment includes:

Transmit-Receive Unit, for receiving the first information of session management network element transmission；Wherein, the first information includes at least one The identification information of PDU session, at least one described PDU session are that the session management network element initiates the PDU meeting established from terminal It is determined in words, at least one described PDU session is in activated state；

Processing unit, for discharging the user face interface-free resources of at least one PDU session, protecting according to the first information Stay the configuration information of user face interface-free resources and the context of at least one PDU session.

18. access network equipment according to claim 17, which is characterized in that

The Transmit-Receive Unit is also used to, and according to the first information, Xiang Suoshu terminal sends the 4th information；Wherein, the described 4th Information includes the identification information of at least one PDU session, and it is described extremely that the 4th information is used to indicate the terminal release The user face interface-free resources of a few PDU session, retain user face interface-free resources configuration information and it is described at least one The context of PDU session.

19. access network equipment described in 7 or 18 according to claim 1, which is characterized in that

The Transmit-Receive Unit is also used to, and receives the 5th information that the terminal is sent；Wherein, the 5th information include one or The identification information of multiple PDU sessions, one or more of PDU sessions are the terminals from least one described PDU session Determining；

The processing unit is also used to, and eats dishes without rice or wine to provide according to the user face of the 5th information and one or more of PDU sessions The configuration information in source establishes the user face interface-free resources of one or more of PDU sessions.

20. access network equipment according to claim 19, which is characterized in that

The Transmit-Receive Unit is also used to, and Xiang Suoshu session management network element sends third information；Wherein, the third information includes institute State the identification information of one or more PDU sessions；The third information is used to indicate the access network equipment and has been established described one The user face interface-free resources of a or multiple PDU sessions.

21. 7 to 20 described in any item access network equipments according to claim 1, which is characterized in that described in switching flow Access network equipment is source access network equipment；The Transmit-Receive Unit is also used to, and is sent to target access network equipment one or more The context of a PDU session.

22. a kind of terminal installation, which is characterized in that the terminal installation includes:

Transmit-Receive Unit, for receiving the 4th information of access network equipment transmission；Wherein, the 4th information includes at least one The identification information of PDU session, at least one described PDU session are that session management network element is initiated in the PDU session established from terminal Determining, at least one described PDU session is in activated state；

Processing unit retains for discharging the user face interface-free resources of at least one PDU session according to the 4th information The context of the configuration information of user face interface-free resources and at least one PDU session.

23. terminal installation according to claim 22, which is characterized in that

The Transmit-Receive Unit is also used to, and Xiang Suoshu session management network element sends the second information；Second information include it is described extremely The identification information of a few PDU session and indicate that at least one described PDU session is able to enter the information of dormant state, described second Information is initiated to determine at least one described PDU session in the PDU session established from the terminal for the session management network element.

24. the terminal installation according to claim 22 or 23, which is characterized in that

The processing unit is also used to, and according to the configuration information of the user face interface-free resources of one or more PDU sessions, establishes institute State the user face interface-free resources of one or more PDU sessions；Wherein, one or more of PDU sessions are the terminals from institute State determination at least one PDU session；

The Transmit-Receive Unit is also used to, and Xiang Suoshu access network equipment sends the 5th information；Wherein, the 5th information includes described The identification information of one or more PDU sessions, the 5th information be used to indicate the access network equipment establish it is one or The user face interface-free resources of multiple PDU sessions.

25. a kind of system of management agreement data cell PDU session, which is characterized in that any including such as claim 13 to 16 Session management network element described in, such as the described in any item access network equipments of claim 17 to 21, and such as claim 22 To 24 described in any item terminal installations.

26. a kind of computer readable storage medium, which is characterized in that including computer instruction, when the computer instruction is being counted When being run on calculation machine, so that as the described in any item methods of claim 1 to 12 are performed.