WO2018121382A1 - Connected state control method, device and system for terminal - Google Patents

Abstract

Provided are a connected state control method, device and system for a terminal, to at least solve the problem in the art that after introducing a lightly connected state or an inactively connected state, the entire network cannot perform actively necessary control over a terminal being in a connected state for a long time without user-plane data transmission. The method comprises: a first network device receiving indication information from a second network device, wherein the indication information is used for indicating that user-plane data transmission of a terminal in a connected state has already finished; and the first network device initiating, according to the indication information, a connection release flow, wherein the connection release flow is used for turning the terminal from a connected state to an idle state.

Description

Terminal connection state control method, device and system

The present application claims priority to Chinese Patent Application No. 201611262499.9, entitled "Connected State Control Method, Apparatus and System for Terminals" on December 30, 2016, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a connection state control method, device, and system for a terminal.

Background technique

In the existing terminal connection management mechanism, when a terminal does not have user plane data transmission within a certain period of time, the network side releases the signaling connection of the terminal to change the terminal to an idle state, thereby saving air interface bearer resources. However, because of the diversity of applications running on the terminal, the network side cannot predict the specific time when the next uplink or downlink data transmission occurs in the idle state terminal, so that the terminal performs state switching between the idle state and the connected state more frequently. However, the state switching from the idle state to the connected state requires more signaling overhead due to the need to establish an air interface signaling connection and a network side signaling connection at the same time.

In order to reduce the signaling overhead of the state switching between the idle state and the connected state of the terminal, the lightly connected state and the inactive connected state are respectively in the fourth generation (4rd generation, 4G) mobile communication network. Introduced in the fifth generation (5rd generation, 5G) mobile communication network, the core idea is to introduce a lightweight connection state in the air interface of the 4G mobile communication network; or introduce an inactive connection state in the air interface of the 5G mobile communication network. . Taking the 4G mobile communication network as an example, after the terminal enters the connected state, if there is no user plane data transmission within a certain period of time, the terminal still remains in the connected state on the network side, and enters the lightweight connected state in the air interface terminal. When the subsequent terminal has uplink data and signaling needs to be sent or the downlink data and signaling to the terminal need to be sent, the terminal recovers from the lightweight connection state to the connected state in the air interface, thereby greatly reducing the air interface and the network side. Signaling overhead.

However, after introducing a lightweight connected state or an inactive connected state, the terminal is always in a connected state on the network side. Even if the terminal has not transmitted user plane data for a long time, the network side cannot sense the active state of the terminal user plane, and thus the entire network cannot actively perform the necessary operation on the terminal that is in the connected state for a long time but has no user plane data transmission. control.

Summary of the invention

The embodiment of the present application provides a connection state control method, device, and system for a terminal, so as to at least solve the problem that the entire network cannot actively connect to a long time after the introduction of a lightweight connection state or an inactive connection state in the prior art. The terminal of data transmission carries out the necessary control problems.

To achieve the above objective, the embodiment of the present application provides the following technical solutions:

In a first aspect, the embodiment of the present application provides a method for controlling a connection state of a terminal, where the method includes: receiving, by the first network device, indication information from the second network device, where the indication information is used to indicate a user plane of the terminal in the connected state. The data transmission has ended; the first network device initiates a connection release procedure according to the indication information, and the connection release procedure is used to change the terminal from the connected state to the idle state. Based on the connection state control method of the terminal provided by the embodiment of the present application, after the lightweight connection state or the inactive connection state is introduced, the first network device may detect, after the second network device detects that the terminal in the connected state has no user plane data transmission. Receiving the indication information of the initiated connection release process from the second network device, and changing the terminal from the connected state to the idle state according to the indication information, thereby solving the problem that the network side cannot only perceive the user plane data transmission state of the terminal The technical limitation of passively maintaining the terminal in the connected state allows the operator to perform on-demand control on the terminal in the connected state, for example, the terminal that is in the connected state for a long time but has no user plane data transmission changes from the connected state to the idle state. Thereby, unnecessary network and air interface resources are saved, and the running performance and efficiency of the network are improved.

In a possible design, the first network device initiates a connection release process according to the indication information, including: determining, by the first network device, whether the terminal is based on the local policy or the subscription data of the terminal according to the indication information. From the connected state to the idle state; if the first network device determines to change the terminal from the connected state to the idle state, the first network device initiates the connection release procedure. That is, in the embodiment of the present application, the first network device may not directly initiate the connection release process after receiving the indication information, but determine that the terminal is changed from the connected state to the idle state based on the local policy or the subscription data of the terminal. After that, the connection release process is initiated, so that the operator can further perform on-demand control on the connected terminal. For the specific implementation of determining whether to change the terminal from the connected state to the idle state based on the local information or the subscription data of the terminal, the first network device may refer to the specific implementation manner, and details are not described herein again.

In a possible design, before the first network device receives the indication information from the second network device, the method further includes: the first network device sending a request message to the second network device, the request message is used to request the The second network device reports the user plane data transmission status of the terminal. That is, in the embodiment of the present application, the first network device may receive the indication information from the second network device after requesting the second network device to report the user plane data transmission status of the terminal. The second network device may be requested to report the user plane data transmission status of the terminal by introducing an end user plane activity status query mechanism on the first network device of the terminal, or by using the first network device and the second network device. A user plane activity state change reporting mechanism is introduced for the terminal to request the second network device to report the user plane data transmission status of the terminal. For details, refer to the specific implementation part, and details are not described herein again.

In a possible design, the first network device sends a request message to the second network device, including: the first network device starts a second inactivity timer; if the second inactivity timer expires, The first network device does not receive uplink or downlink signaling or data of the terminal, and the first network device sends the request message to the second network device. The solution requests the second network device to report the user plane data transmission status of the terminal by introducing an end user plane activity status query mechanism on the first network device of the terminal.

In a possible design, after the first network device starts the second inactivity timer, the method further includes: if the second inactivity timer expires, the first network device receives the uplink of the terminal or Downlink signaling or data, the first network device stops the second inactivity timer.

In a possible design, the first network device sends a request message to the second network device, including: determining, by the first network device, whether the second network device is requested to report the local network policy based on the local policy or the subscription data of the terminal The user plane data transmission status of the terminal; if the first network device determines to request the second network device to report the user plane data transmission status of the terminal, the first network device sends a request message to the second network device. That is, in the embodiment of the present application, the first network device may not directly send the request message to the second network device, but determine, according to the local policy or the subscription data of the terminal, that the second network device is requested to report the user plane data of the terminal. The request message is sent after the transmission state, so that the operator can further perform on-demand control on the terminal in the connected state. For a specific implementation of determining whether to request the second network device to report the user plane data transmission status of the terminal based on the local policy or the subscription data of the terminal, reference may be made to the specific implementation manner, and details are not described herein.

In a possible design, after the first network device receives the indication information from the second network device, before the first network device initiates the connection release process according to the indication information, the first network device may further include: The second network device sends an acknowledgement message, where the acknowledgement information is used to indicate that the first network device confirms that the indication information from the second network device is received. That is, the first network device may send the confirmation information confirming that the indication information from the second network device is received to the second network device immediately after the second network device sends the indication information to the first network device. Of course, the first network device can also be confirmed by the connection release process. For details, refer to the specific implementation part, and details are not described herein again.

In a possible design, the local policy includes: a usage type of the terminal, a service type of the terminal, a device type of the terminal, an access priority of the terminal, a mobile mode of the terminal, a wireless access type of the terminal, and a dedicated terminal. At least one of a core network type, a data type of the terminal, and statistical movement information of the terminal.

In one possible design, the subscription data includes information on whether the terminal is allowed to be in the connected state for a long time.

For a detailed description of the local policy and the subscription data, reference may be made to the specific implementation manner, and details are not described herein again.

In one possible design, the first network device comprises a mobility management entity MME or an access and mobility management function AMF entity.

In a second aspect, the embodiment of the present application provides a method for controlling a connection state of a terminal, where the method includes: determining, by the second network device, whether the terminal in the connected state has user plane data transmission; if the second network device determines that the terminal has no user The second network device sends the indication information to the first network device, where the indication information is used to indicate that the user plane data transmission of the terminal in the connected state has ended. Based on the connection state control method of the terminal provided by the embodiment of the present application, after the lightweight connection state or the inactive connection state is introduced, the second network device can sense whether the terminal in the connected state has user plane data transmission, and is determined to be in the After the user in the connected state has no user plane data transmission, the first network device is instructed to initiate a connection release process, and the connection release process is used to change the terminal from the connected state to the idle state, thereby solving the network side because the user plane data of the terminal cannot be perceived. The transmission state can only passively limit the technical state of the terminal to the connected state, so that the operator can perform on-demand control on the terminal in the connected state, for example, the terminal that is in the connected state for a long time but has no user plane data transmission from the connected state. It becomes idle, which saves unnecessary network and air interface resources and improves the running performance and efficiency of the network.

In a possible design, the second network device determines whether the terminal in the connected state has user plane data transmission, including: the second network device starts a first inactivity timer; if the first inactivity timer is in the first inactivity timer When the timeout occurs, the second network device does not receive uplink or downlink signaling or data of the terminal, and the second network device determines that the terminal has no user plane data transmission. That is, in the embodiment of the present application, whether the terminal in the connected state has user plane data transmission can be determined by starting the first inactivity timer.

In a possible design, after the second network device starts the first inactivity timer, the method further includes: if the first inactivity timer expires, the second network device receives the uplink of the terminal or Downlink signaling or data, the second network device stops the first inactivity timer.

In a possible design, the second network device determines whether the terminal in the connected state has user plane data transmission, including: if the user plane data transmission status of the terminal changes from an active state to an inactive state, the second The network device determines that the terminal has no user plane data transmission. That is, in the embodiment of the present application, the first network device may save the user plane data transmission status of the terminal, and if the user plane data transmission status of the terminal changes from the active state to the inactive state, the first network device may determine that the terminal has no user plane. data transmission.

Of course, in addition to the specific implementation of the above-mentioned two types of first network devices to determine whether the terminal in the connected state has a user plane data transmission, there may be other possible implementation manners. For details, refer to the specific implementation manners, and details are not described herein again.

In a possible design, before the second network device determines whether the terminal in the connected state has user plane data transmission, the method further includes: the second network device receiving the request message sent by the first network device, the request message And configured to request the second network device to report a user plane data transmission status of the terminal. The second network device may be requested to report the user plane data transmission status of the terminal by introducing an end user plane activity status query mechanism on the first network device of the terminal, or by using the first network device and the second network device. A user plane activity state change reporting mechanism is introduced for the terminal to request the second network device to report the user plane data transmission status of the terminal. For details, refer to the specific implementation part, and details are not described herein again.

In a possible design, after the second network device sends the indication information to the first network device, the method may further include: receiving, by the first network device, confirmation information, where the confirmation information is used to indicate that the first network device acknowledges receipt Indication information from the second network device. That is, the first network device may send the confirmation information confirming that the indication information from the second network device is received to the second network device immediately after the second network device sends the indication information to the first network device. Of course, the first network device can also be confirmed by the connection release process. For details, refer to the specific implementation part, and details are not described herein again.

In one possible design, the second network device includes a serving gateway SGW or a user plane function UPF entity.

In a third aspect, the embodiment of the present application provides a first network device, where the first network device has a function of implementing behavior of the first network device in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, an embodiment of the present application provides a first network device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when When the first network device is in operation, the processor executes the computer-executed instruction stored in the memory to cause the first network device to perform the connection state control method of the terminal according to any one of the foregoing first aspects.

In a fifth aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the first network device, which includes a program designed to execute the foregoing aspect for the first network device.

In a sixth aspect, the embodiment of the present application provides a computer program, where the computer program includes instructions, when the computer program is executed by a computer, to enable the computer to perform the connection state control method of the terminal according to any one of the foregoing first aspects. Process.

In addition, the technical effects brought by any one of the third aspect to the sixth aspect can be referred to the technical effects brought by different design modes in the first aspect, and details are not described herein again.

In a seventh aspect, the embodiment of the present application provides a second network device, where the second network device has a function of implementing behavior of the second network device in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighth aspect, the embodiment of the present application provides a second network device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when When the second network device is in operation, the processor executes the computer-executed instruction stored in the memory to cause the second network device to perform the connection state control method of the terminal according to any one of the foregoing second aspects.

In a ninth aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the second network device, which includes a program designed to execute the foregoing aspect for the second network device.

In a tenth aspect, the embodiment of the present application provides a computer program, where the computer program includes instructions, when the computer program is executed by a computer, to enable the computer to perform the connection state control method of the terminal according to any one of the foregoing second aspects. Process.

In addition, the technical effects brought by the design mode of any one of the seventh aspect to the tenth aspect can be referred to the technical effects brought by different design modes in the second aspect, and details are not described herein again.

In an eleventh aspect, the embodiment of the present application provides a connection state control system for a terminal, where the connection state control system of the terminal includes the first network device of the foregoing third aspect, and the second network device of the foregoing seventh aspect. Or the connection state control system of the terminal includes the first network device according to the fourth aspect and the second network device of the foregoing eighth aspect; or the connection state control system of the terminal includes the foregoing fifth aspect The computer storage medium according to the above aspect, wherein the connection state control system of the terminal comprises the computer program according to the sixth aspect and the computer program according to the tenth aspect. Based on the connection state control system of the terminal provided by the embodiment of the present application, after the lightweight connection state or the inactive connection state is introduced, the second network device can sense whether the terminal in the connected state has user plane data transmission, and is determined to be in the After the user in the connected state has no user plane data transmission, the first network device is instructed to initiate a connection release process, and the connection release process is used to change the terminal from the connected state to the idle state, thereby solving the network side because the user plane data of the terminal cannot be perceived. The transmission state can only passively limit the technical state of the terminal to the connected state, so that the operator can perform on-demand control on the terminal in the connected state, for example, the terminal that is in the connected state for a long time but has no user plane data transmission from the connected state. It becomes idle, which saves unnecessary network and air interface resources and improves the running performance and efficiency of the network.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

1 is a schematic structural diagram of a connection state control system of a terminal according to an embodiment of the present application;

2 is a schematic structural diagram of a connection state control system of a terminal in a 4G network architecture according to an embodiment of the present disclosure;

3 is a schematic structural diagram of a connection state control system of a terminal in a 5G network architecture according to an embodiment of the present disclosure;

4 is a schematic structural diagram of a computer device according to an embodiment of the present application;

FIG. 5 is a schematic diagram 1 of a connection state control method of a terminal according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram 2 of a connection state control method of a terminal according to an embodiment of the present disclosure;

FIG. 7 is a third schematic diagram of interaction of a connection state control method of a terminal according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram 4 of interaction of a connection state control method of a terminal according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram 5 of a connection state control method of a terminal according to an embodiment of the present disclosure;

10 is a schematic diagram 6 of interaction of a connection state control method of a terminal according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram 1 of a first network device according to an embodiment of the present application;

FIG. 12 is a schematic structural diagram 2 of a first network device according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram 1 of a second network device according to an embodiment of the present application;

FIG. 14 is a schematic structural diagram 2 of a second network device according to an embodiment of the present disclosure.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the present application, the meaning of "a plurality" is two or more unless otherwise stated. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish the same or similar items whose functions and functions are substantially the same. Those skilled in the art will understand that the words "first", "second", etc. do not limit the quantity and order of execution. For example, the “first” of the first network device and the “second” of the second network device in the embodiment of the present application are only used to distinguish different network devices.

The network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

FIG. 1 is a schematic structural diagram of a connection state control system of a terminal provided by an embodiment of the present application. The connected state control system 10 of the terminal includes a first network device 101 and a second network device 102. The second network device 102 is configured to determine whether the terminal in the connected state has user plane data transmission; if the second network device 102 determines that the terminal in the connected state has no user plane data transmission, the second network device 102 sends the user plane data to the first network device. The indication information is sent to indicate that the user plane data transmission of the terminal in the connected state has ended. The first network device 101 is configured to receive indication information from the second network device, where the indication information is used to indicate that the user plane data transmission of the terminal in the connected state has ended, and initiate a connection release process according to the indication information, and the connection release process Used to change the terminal from the connected state to the idle state.

It should be noted that, in FIG. 1 , the first network device 101 and the second network device 102 may directly communicate, and may also perform communication through forwarding of other network devices, which is not specifically limited in this embodiment of the present application.

Specifically, the connection state control system 10 of the foregoing terminal can be applied to the current 4G Long Term Evolution (LTE)/Evolved Packet Core (EPC) network, and can also be applied to future 5G networks and other futures. The network of the present application does not specifically limit this.

If the connection state control system 10 of the terminal is applied to the current 4G LTE/EPC network, as shown in FIG. 2, the first network device 101 is specifically a mobility management entity (Mobility Management Entity) in the 4G LTE/EPC network. MME); the second network device 102 is specifically a Serving Gateway (SGW) in the 4G LTE/EPC network. For the main functions of the MME and the SGW, reference may be made to the descriptions of the first network device 101 and the second network device 102, and details are not described herein.

In addition, as shown in FIG. 2, the 4G LTE/EPC network may further include a terminal and a base station. The terminal communicates with the base station through the LTE-Uu interface, the base station communicates with the SGW through the S1-U interface, the base station communicates with the MME through the S1-MME interface, and the MME communicates with the SGW through the S11 interface.

The terminal is configured to send uplink signaling or data from the idle state to the connected state; and, in the idle state, receive the paging initiated by the network side to send downlink signaling or data, and change from the idle state to the connected state. The base station participates in the establishment of the air interface signaling connection of the terminal from the idle state to the connected state, the paging initiated by the participating network side for transmitting the downlink signaling or the data to the terminal in the idle state, and the uplink or downlink information of the terminal participating in the connected state. Order and data transmission, etc.

Although not shown, the above-mentioned 4G LTE/EPC network may further include a Home Subscriber Server (HSS), which is a primary user database in the 4G LTE/EPC network. It saves the subscription data and user profile configured by the operator for the terminal, performs user authentication, access restrictions, PDN context parameter configuration and authorization, etc., similar to those in the Global System for Mobile Communication (GSM). Home Location Register (HLR). The HSS can provide the HLR functions necessary for the 4G LTE/EPC Packet Switched (PS) domain and the Internet Protocol (IP) Multimedia Multimedia Subsystem (IMS). In the embodiment of the present application, the HSS is used to provide the subscription data of the terminal, and is used by the MME to determine whether to change the terminal from the connected state to the idle state according to the subscription data of the terminal, or to request the SGW to request the SGW according to the subscription data of the terminal. Report the user plane data transmission status of the terminal.

Of course, the above 4G LTE/EPC network may also include other modules or network entities, such as Packet Data Network (PDN), General Packet Radio Service (GPRS) service support node (Serving GPRS). The support node (SGSN) or the Policy and Charging Rules Function (PCRF), etc., is not specifically limited in this embodiment of the present application.

If the connection state control system 10 of the terminal is applied to a future 5G network and other future networks, as shown in FIG. 3, the first network device 101 is specifically a 5G network and access and movement in other networks in the future. An Access and Mobility Management Function (AMF) entity; the second network device 102 is specifically a future 5G network and a User Plane Function (UPF) entity in other networks in the future. For the main functions of the AMF entity and the UPF entity, reference may be made to the descriptions of the first network device 101 and the second network device 102, and details are not described herein.

In addition, as shown in FIG. 3, the future 5G network and other future networks may further include a terminal, a Radio Access Network (RAN) access point, and a Session Management Function (SMF) entity. The terminal communicates with the AMF entity through the Next Generation (NG) interface 1, the RAN access point communicates with the AMF entity through the NG interface 2, the RAN access point communicates with the UPF entity through the NG interface 3, and the UPF entity passes the NG interface 4 In communication with the SMF entity, the AMF entity communicates with the SMF entity via the NG interface 11.

The terminal is configured to send uplink signaling or data from the idle state to the connected state; and, in the idle state, receive the paging initiated by the network side to send downlink signaling or data, and change from the idle state to the connected state. The RAN access point participates in the establishment of the air interface signaling connection of the terminal from the idle state to the connected state, the paging initiated by the participating network side for transmitting the downlink signaling or the data to the terminal in the idle state, and the uplink of the terminal participating in the connected state. Or downlink signaling and data transmission, etc. The SMF entity participates in the session management related functions of the terminal and implements communication between the AMF entity and the UPF entity.

Although not shown, the foregoing 5G network and the other networks in the future may further include a database entity, and the function of the database entity is similar to the function of the HSS described above, and details are not described herein again. In the embodiment of the present application, the database entity is mainly used to provide the subscription data of the terminal, and is used by the AMF entity to determine whether to change the terminal from the connected state to the idle state according to the subscription data of the terminal; or, for the AMF entity to sign the terminal according to the terminal. The data request UPF entity reports the user plane data transmission status of the terminal.

Of course, the above-mentioned future 5G network and other future networks may also include other modules or network entities, such as an Authentication Server Function (AUSF) entity, a Policy Control Function (PCF) entity, and the like. The embodiment of the present application does not specifically limit this.

It should be noted that the foregoing 5G network and other terminals in the future, the RAN access point, the UPF entity, the AMF entity, the SMF entity, and the database entity are only one name, and the name does not limit the device itself. In the future 5G network and other networks in the future, the network element or the entity corresponding to the terminal, the RAN access point, the UPF entity, the AMF entity, the SMF entity, and the database entity may also be other names. No specific limitation. For example, the database entity may also be replaced by a Home Subscriber Server (HSS) or a User Subscription Database (USD) or Unified Data Management (UDM); the UPF entity may also be replaced. It is replaced with UP, etc., and is uniformly explained here, and will not be described below.

It should be noted that the terminal involved in the present application may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of terminals. Mobile station (MS), user equipment (User Equipment, UE), terminal equipment (Terminal Equipment), soft terminal, and the like. For convenience of description, in the present application, the above mentioned devices are collectively referred to as terminals.

In addition, the first network device 101 or the second network device 102 in the embodiment of the present application may be implemented by one physical device, or may be implemented by multiple physical devices. The first network device 101 in this embodiment of the present application. And the second network device 102 may be implemented by different physical devices, or may be implemented by the same physical device, which is not specifically limited in this embodiment of the present application. That is, it can be understood that the first network device 101 and the second network device 102 in the embodiment of the present application may be a logical function module in the physical device, or may be a logical function composed of multiple physical devices. The module is not specifically limited in this embodiment.

For example, as shown in FIG. 4, the first network device 101 and the second network device 102 of FIG. 1 may be implemented by the computer device (or system) of FIG.

FIG. 4 is a schematic diagram of a computer device according to an embodiment of the present application. Computer device 400 includes at least one processor 401, a communication bus 402, a memory 403, and at least one communication interface 404.

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

Communication bus 402 can include a path for communicating information between the components described above.

The communication interface 404 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. .

The memory 403 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (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 Any other media accessed, but not limited to this. The memory can exist independently and be connected to the processor via a bus. The memory can also be integrated with the processor.

The memory 403 is used to store application code for executing the solution of the present application, and is controlled by the processor 401 for execution. The processor 401 is configured to execute application code stored in the memory 403 to implement connection state control of the terminal.

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

In a particular implementation, as an embodiment, computer device 400 can include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

In a particular implementation, as an embodiment, computer device 400 may also include an output device 405 and an input device 406. Output device 405 is in communication with processor 401 and can display information in a variety of ways. For example, the output device 405 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 406 is in communication with processor 401 and can accept user input in a variety of ways. For example, input device 406 can be a mouse, keyboard, touch screen device, or sensing device, and the like.

The computer device 400 described above can be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device 400 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet, a wireless terminal device, a communication device, an embedded device, or have the following FIG. A device of similar structure. The embodiment of the present application does not limit the type of computer device 400.

The method for controlling the connection state of the terminal provided by the embodiment of the present application will be specifically described below with reference to the system shown in FIG. 1 to FIG. 3 and the device shown in FIG. 4 .

First, in conjunction with the connection state control system 10 of the terminal shown in FIG. 1, the connection state control method of the terminal provided by the embodiment of the present application includes: determining, by the second network device, whether the terminal in the connected state has user plane data transmission; The network device determines that the terminal in the connected state has no user plane data transmission, and the second network device sends the indication information to the first network device, where the indication information is used to indicate that the user plane data transmission of the terminal in the connected state has ended. In this way, the first network device receives the indication information from the second network device, and according to the indication information, initiates a connection release procedure, where the connection release procedure is used to change the terminal from the connected state to the idle state. That is, in the connection state control method of the terminal provided by the embodiment of the present application, after the lightweight connection state or the inactive connection state is introduced, the second network device may perceive whether the terminal in the connected state has user plane data transmission, and After the terminal in the connected state is determined to have no user plane data transmission, the first network device is instructed to initiate a connection release process, where the connection release process is used to change the terminal from the connected state to the idle state, thereby solving the problem that the network side cannot sense the terminal. The data transmission state can only passively limit the technical state of the terminal to the connected state, so that the operator can perform on-demand control on the terminal in the connected state, for example, the terminal that is in the connected state for a long time but has no user plane data transmission. The connected state becomes idle, which saves unnecessary network and air interface resources and improves the running performance and efficiency of the network.

Next, the connection state control system 10 of the terminal shown in FIG. 1 is applied to the 4G LTE/EPC network shown in FIG. 2 as an example, and the connection state control method of the above terminal is expanded.

As shown in FIG. 5, a schematic flowchart of a method for controlling connection state of a terminal according to an embodiment of the present application is shown in FIG. The connection state control method of the terminal involves the interaction between the terminal, the base station, the serving MME of the terminal, and the SGW of the terminal, and includes the following steps:

S501. The terminal enters a connected state from an idle state.

Specifically, the transmission of the user plane data requires the terminal to enter the connected state from the idle state.

For uplink user plane data transmission: Typically, the terminal initiates a Service Request procedure, which is used to change the terminal from an idle state to a connected state.

For the downlink user plane data transmission, the SGW of the terminal sends a Downlink Data Notification (DDN) message to the MME, and triggers the MME to initiate paging to the terminal. Further, as a paging response, the terminal initiates a service request procedure for changing the terminal from an idle state to a connected state.

It should be noted that, unlike the prior art solution in the 4G network, after the lightweight connection state or the inactive connection state is introduced, after the user plane data transmission of the terminal in the connected state is completed, in order to keep the terminal on the network side. In the connected state, the base station of the 4G mobile communication network does not start the user inactivity timer, so that the MME does not perceive the user plane data transmission status of the terminal, and thus keeps the terminal in the connected state.

S502. The SGW starts a first inactivity timer.

Specifically, the first inactivity timer is used by the SGW to detect whether the user plane data transmission status of the terminal currently in the connected state is in an inactive state, so the timer may also be referred to as a user plane inactivity timer. ). The timing of the first inactivity may be set and changed by the operator, and a default value, such as 30s, may be pre-configured on the SGW, which is not specifically limited in this embodiment of the present application.

It should be noted that, in the embodiment of the present application, the SGW usually starts the first inactivity timer when the terminal is in the connected state and there is no user plane data transmission on the terminal. Of course, the SGW can also start the first inactivity timer when the terminal is in the connected state and the uplink or downlink data is transmitted on the terminal, which is not specifically limited in this embodiment of the present application.

S503. If the SGW does not receive uplink or downlink signaling or data of the terminal when the first inactivity timer expires, the SGW determines that the terminal does not have user plane data transmission.

Optionally, if the SGW receives the uplink or downlink signaling or data of the terminal before the first inactivity timer expires, the SGW stops the first inactivity timer.

Exemplarily, it is assumed that the timing duration of the first inactivity timer is set to 30s, and the SGW is the first inactivity timer that is started when the terminal is in the connected state and there is no user plane data transmission on the terminal, and then the SGW is started. After an inactivity timer:

If the uplink or downlink signaling or data of the terminal is not received within 30s, the SGW determines that the terminal has no user plane data transmission.

If the uplink or downlink signaling or data of the terminal is received within 30 s, the SGW stops the first inactivity timer. After the uplink or downlink signaling or data transmission ends, the SGW may restart the first inactivity timer. If the uplink or downlink signaling or data of the terminal is not received within 30s, the SGW determines that the terminal has no user plane data transmission. . On the other hand, if the uplink or downlink signaling or data of the terminal is still received within 30s, the SGW stops the first inactivity timer, and continues to perform the process according to the foregoing process, and details are not described herein again.

Or, by way of example, assuming that the timing duration of the first inactivity timer is set to 30 s, the SGW is the first inactivity timer that is started when the terminal is in the connected state and there is uplink or downlink data transmission on the terminal, and then the SGW is in the SGW. After starting the first inactivity timer:

If the uplink or downlink signaling or data of the terminal is received within 30 s, the SGW stops the first inactivity timer. If the SGW still receives the uplink or downlink signaling or data of the terminal within 30s after the SGW restarts the first inactivity timer, the SGW still stops the first inactivity timer. After the SGW restarts the first inactivity timer and does not receive uplink or downlink signaling or data of the terminal within 30s, the SGW determines that the terminal has no user plane data transmission.

It should be noted that, in steps S502 and S503, only a specific implementation of whether the SGW determines whether the terminal in the connected state has user plane data transmission is provided. Of course, the SGW determines whether the terminal in the connected state has user plane data transmission. There may be other implementation manners. For example, the SGW may save the user plane data transmission status of the terminal. If the user plane data transmission status of the terminal changes from the active state to the inactive state, the SGW may determine that the terminal has no user plane data transmission. Alternatively, a time dimension may be introduced, but when the time dimension is implemented, the timer may not be started, for example, by querying the system time twice, if the system queries the terminal without the user plane data transmission time. The interval between the two is equal to or exceeds the preset time interval, and the SGW can determine that the terminal has no user plane data transmission. The embodiment of the present application does not specifically limit whether the SGW determines whether the terminal in the connected state has user plane data transmission.

S504. The SGW sends the indication information to the MME, so that the MME receives the indication information. The indication information is used to indicate that the user plane data transmission of the terminal has ended, that is, the user plane activity status of the terminal changes from active to inactive.

Specifically, the SGW may send the indication information to the MME by using a newly defined message, for example, the newly defined message may be a UP Inactivity Notification message, where the user plane inactivity notification message carries the indication information. . Of course, the SGW can also send the indication information to the MME through the existing message, for example, the DDN message is modified, and the indication information is carried in the DDN message, which is not specifically limited in this embodiment of the present application.

S505. The MME determines, according to the indication information, whether to change the terminal from the connected state to the idle state based on the local policy or the subscription data of the terminal.

The local policy may be a policy that is pre-configured by the operator on the MME, which is also called an operator policy, or a policy that the MME obtains and saves from other network elements in advance, for example, in the initial registration process of the terminal. The MME obtains a local policy from an application server (AS) or an application function (AF) entity through the network capability open function entity and saves it.

Specifically, in the embodiment of the present application, the local policy information may include a usage type of the terminal, a service type of the terminal, a device type of the terminal, and an access priority of the terminal. ), the mobility pattern of the terminal, the radio access type of the terminal, the Dedicated Core Network type (DCN type) of the terminal, the data type of the terminal, and the terminal At least one of statistic mobility information.

The type of use of the terminal may be, for example, frequent large data packet transmission, infrequent small data packet transmission, high reliability data transmission, or low latency data transmission.

The service type of the terminal may be, for example, a short message service, a voice service, a video service, a data service, an emergency service, or an abnormal service.

The device type of the terminal can be, for example, a smart phone, a machine type device, a cellular Internet of things device, a wearable device, or an in-vehicle device.

The access priority of the terminal may be, for example, a high priority, a normal priority, or a low priority.

The mobile mode of the terminal may be, for example, no mobility, low mobility, high mobility, or random mobility. Among them, no mobility means stationary.

The mobility mode of the terminal may be, for example, cell range mobility, location area range mobility, registration area range mobility, access technology range mobility, and cross-radio access. Inter-Radio Access Technology (inter-RAT) mobility, network range mobility and cross-network mobility. The location area range mobility may be, for example, a Tracking Area (TA) range mobility. The registration area range mobility may be, for example, a tracking list list (TA list) range mobility. Access technology range mobility may be, for example, 4G intra mobility. The network range mobility may be, for example, intra-Public Land Mobile Network (intra-PLMN) mobility. Cross-network mobility may be, for example, trans-public land mobile network (inter-PLMN) mobility.

The wireless access type of the terminal may be, for example, LTE access, Narrowband Internet of Things (NB-IoT) access, or 5G air interface access.

The dedicated core network type of the terminal may be, for example, a Machine Type Communication (MTC) private network, a Cellular Internet of Things (CIoT) private network, and a Vehicle to Everything (V2X) private network. Wait.

The data type of the terminal may be, for example, IP data, non-IP (non-IP) data, or the like. Among them, IP includes IPv4 or IPv6.

The statistical movement information of the terminal may be, for example, a historical movement trajectory of the terminal, a foreseeable movement trajectory of the terminal, and the like.

Specifically, the subscription data of the terminal may be information about whether the terminal is allowed to be in the connected state for a long time. Or more specifically, the subscription data may be information about whether the terminal is allowed to enter a lightly connected state, which is not specifically limited in this embodiment of the present application. The subscription data of the terminal is obtained in the initial attachment process or the location update process of the terminal, and the MME obtains the subscription data information for the terminal in the HSS. For details, refer to the method for obtaining the existing subscription data, and details are not described herein again. In addition, other information may be included in the subscription data, which is not specifically limited in this embodiment of the present application.

In combination with the foregoing local policy or the subscription data of the terminal, the MME determines, according to the indication information, whether to change the terminal from the connected state to the idle state based on the local policy or the subscription data of the terminal, for example, may be:

If the local policy is: for a terminal whose type is non-frequent small packet transmission and whose service type is data service, or for a terminal whose device type is a cellular IoT device and whose access priority is low, or for the mobile mode is random mobile And the mobility range is a terminal moving across the access technology and moving across the network range, and the MME determines to change the terminal from the connected state to the idle state;

Alternatively, if the subscription data of the terminal does not allow the terminal to be in the connected state for a long time, the MME determines that the terminal is changed from the connected state to the idle state, and vice versa, the terminal is not changed from the connected state to the idle state;

Alternatively, if the subscription data is that the terminal is not allowed to enter the lightweight connection state, the MME determines that the terminal is changed from the connected state to the idle state, and vice versa, the terminal is not changed from the connected state to the idle state.

S506. If the MME determines to change the terminal from the connected state to the idle state, the MME initiates a connection release procedure, where the connection release procedure is used to change the terminal from the connected state to the idle state.

Specifically, the connection release process in the embodiment of the present application completely reuses the S1 connection release process in the existing 4G LTE/EPC network, and specifically refers to the 3rd Generation Partnership Project (3GPP).

The standard TS 23.401 part is not described here.

It should be noted that the step S505 is an optional step. After receiving the indication information, the MME may directly initiate a connection release process according to the indication information, where the connection release process is used to change the terminal from the connected state to the idle state. The embodiment does not specifically limit this.

Optionally, in the embodiment of the present application, after step S504, the method may further include:

The MME sends an acknowledgement message to the SGW, where the acknowledgement information is used to instruct the MME to confirm that the indication information sent by the SGW is received. That is, after the SGW transmits the indication information to the MME, the MME may immediately send confirmation information confirming that the indication information transmitted by the SGW has been received to the SGW. If the SGW sends the indication information to the MME through the user plane inactivity notification message in step S504, the MME may send the acknowledgement information to the SGW through the account inactivity notification acknowledgement message; if the SGW passes the DDN message in step S504. The MME may send the indication information to the MME, and the MME may send the acknowledgment information to the SGW through the DDN acknowledgment message, which is not specifically limited in this embodiment of the present application.

Certainly, the MME may also perform the acknowledgment by the Release Access Bearers Request message in the connection release process in step S506, which is not specifically limited in this embodiment of the present application.

In the connection state control method of the terminal provided by the embodiment of the present application, the user plane inactivity detection mechanism of the terminal is introduced on the SGW of the terminal, and the terminal is in the inactive state of the user plane, that is, the user plane data transmission of the terminal is performed. At the end, the SGW actively informs the serving MME of the terminal that the terminal is in a user-side inactive state. After obtaining the notification information, the MME initiates an S1 connection release process according to the local policy or the subscription data of the terminal, and changes the terminal from the connected state. The idle state solves the technical limitation that the MME can only passively keep the terminal in the connected state because the MME cannot sense the user plane data transmission state of the terminal in the prior art, so that the operator can perform on-demand control on the terminal in the connected state. For example, a terminal that is in a connected state for a long time but has no user plane data transmission changes from a connected state to an idle state, thereby saving unnecessary network and air interface resources, and improving network running performance and efficiency.

The operations of the SGWs in the foregoing S501, S502, S503, S504, and S506 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not used in this embodiment of the present application. Any restrictions.

The action of the MME in the above-mentioned S501, S505, and S506 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not limited in this embodiment.

A possible implementation manner is shown in FIG. 6 , which is a schematic flowchart of a connection state control method of a terminal according to an embodiment of the present application. The connection state control method of the terminal involves the interaction between the terminal, the base station, the serving MME of the terminal, and the SGW of the terminal, and includes the following steps:

S601, the same as S501.

S602. The MME starts a second inactivity timer.

Specifically, the second inactivity timer is used by the MME to periodically query the S-GW of the terminal whether the user plane data transmission status of the terminal currently in the connected state is in an inactive state, so the timer may also be referred to as a user plane. Inactivity timer. The timing of the second inactivity timer may be set and changed by the operator, and a default value, such as 30s, may be pre-configured on the MME, which is not specifically limited in this embodiment of the present application.

It should be noted that, in this embodiment of the present application, the MME usually starts the second inactivity timer when the terminal is in the connected state and there is no signaling or data transmission on the terminal. Of course, the MME may also start the second inactivity timer when the terminal is in the connected state and the uplink or downlink signaling or data transmission is performed on the terminal, which is not specifically limited in this embodiment of the present application.

S603. If the MME does not receive the uplink or downlink signaling or data of the terminal when the second inactivity timer expires, the MME determines whether to request the SGW to report the user plane data transmission status of the terminal, based on the local policy or the subscription data of the terminal. .

Optionally, if the MME receives the uplink or downlink signaling or data of the terminal before the second inactivity timer expires, the SGW stops the second inactivity timer.

Exemplarily, assuming that the timing duration of the second inactivity timer is set to 30 s, the MME is a second inactivity timer that is started when the terminal is in the connected state and there is no signaling or data transmission on the terminal, and is started at the MME. After the second inactivity timer:

If the uplink or downlink signaling or data of the terminal is not received within 30s, the MME determines whether to request the SGW to report the user plane data transmission status of the terminal based on the local policy or the subscription data of the terminal.

If the uplink or downlink signaling or data of the terminal is received within 30 s, the MME stops the first inactivity timer. After the uplink or downlink signaling or data transmission ends, the MME may restart the second inactivity timer. If the uplink or downlink signaling or data of the terminal is not received within 30s, the MME is based on the local policy or the subscription of the terminal. Data, determining whether to request the SGW to report the user plane data transmission status of the terminal. On the other hand, if the uplink or downlink signaling or data of the terminal is still received within 30s, the MME stops the second inactivity timer, and continues to perform the process according to the foregoing process, and details are not described herein again.

Or, by way of example, assuming that the timing duration of the second inactivity timer is set to 30 s, the MME is a second inactivity timer that is started when the terminal is in the connected state and there is uplink or downlink signaling or data transmission on the terminal. Then after the MME starts the second inactivity timer:

If the uplink or downlink signaling or data of the terminal is received within 30 s, the MME stops the second inactivity timer. If the MME still receives the uplink or downlink signaling or data of the terminal within 30s after the MME restarts the second inactivity timer, the MME still stops the second inactivity timer. After the MME restarts the second inactivity timer and does not receive the uplink or downlink signaling or data of the terminal within 30s, the MME determines whether to request the SGW to report the user plane data of the terminal based on the local policy or the subscription data of the terminal. Transmission status.

Specifically, the local policy or the subscription data of the terminal in the embodiment of the present application, and the MME determining whether to request the SGW to report the user plane data transmission status of the terminal based on the local policy or the subscription data of the terminal may refer to the implementation shown in FIG. 5 . The related description in the example will not be described here.

S604. If the MME determines that the SGW is requested to report the user plane data transmission status of the terminal, the MME sends a request message to the SGW, so that the SGW receives the request message, where the request message is used to request the SGW to report the user plane data transmission status of the terminal.

Specifically, in the embodiment of the present application, the user plane data transmission status of the terminal includes two types: active or inactive. The active corresponding terminal has user plane data transmission; the inactive corresponding terminal has no user plane data transmission. A unified explanation is given here, and will not be described below.

Specifically, the request message may be a newly defined message, for example, an end user activity request (UP Activity Request) message. Certainly, the request message may also be an existing message, such as a Modify Access Bearers Request or a Change Notification Request, and add an end user in modifying the access bearer request or changing the notification request. The indication information of the face activity status query is not specifically limited in this embodiment of the present application.

Specifically, in the embodiment of the present application, the MME may periodically perform the steps S602-S604, that is, the terminal in the connected state periodically queries the user plane data transmission state of the terminal, which is not specifically limited in this embodiment of the present application. .

It should be noted that, in the steps S602-S604, only a specific implementation of the MME sending a request message to the SGW is provided. Of course, the MME may send the request message to the SGW, and may have other implementation manners, for example, the terminal is idle. After the state enters the connected state, the MME may directly send a request message to the SGW, where the request message is used to request the SGW to report the user plane data transmission status of the terminal. Alternatively, after the terminal enters the connected state from the idle state, the MME may first determine whether to request the SGW to report the user plane data transmission status of the terminal based on the foregoing local policy or the subscription data of the terminal; and determine, at the MME, requesting the SGW to report the user plane data of the terminal. After the transmission state, the MME starts a second inactivity timer; if the MME does not receive the uplink or downlink signaling or data of the terminal when the second inactivity timer expires, the MME sends a request message to the SGW, where the request message is used. The SGW is requested to report the user plane data transmission status of the terminal. The implementation manner of the MME sending a request message to the SGW is not specifically limited.

It should be noted that, in addition to determining whether to request the SGW to report the user plane data transmission status of the terminal by using the second inactivity timer, the MME may also save the control plane signaling of the terminal or the transmission status of the user plane data, if the terminal The control plane signaling or the transmission status of the user plane data changes from the active state to the inactive state, and the MME may request the SGW to report the user plane data transmission status of the terminal. Alternatively, a time dimension may be introduced, but when the time dimension is implemented, the timer may not be started, for example, by querying the system time twice, and querying the control plane signaling or user plane of the terminal twice. When the interval between the system times in which the data transmission state is inactive is equal to or exceeds the preset time interval, the MME requests the SGW to report the user plane data transmission status of the terminal. The embodiment of the present application does not specifically limit how the MME determines the implementation manner of requesting the SGW to report the user plane data transmission status of the terminal.

S605. The SGW determines, according to the request message, whether the terminal has user plane data transmission.

Specifically, the specific implementation of the SGW to determine whether the terminal has the user plane data transmission may refer to the related description in the embodiment shown in FIG. 5, and details are not described herein again.

S606. If the SGW determines that the terminal does not have user plane data transmission, the SGW sends the indication information to the MME, so that the MME receives the indication information. The indication information is used to indicate that the user plane data transmission of the terminal has ended, that is, the user plane activity status of the terminal changes from active to inactive.

Specifically, if the request message in step S604 is an end user plane activity request message, in step S606, the SGW may send the indication information to the MME through a user activity response (UP Activity Response) message; if the request message in step S604 In order to modify the access bearer request, in step S606, the SGW may send the indication information to the MME by modifying the modify bearer response (Modify Access Bearers Response); if the request message in step S604 is a change notification request, then in step S606, The SGW may send the indication information to the MME by changing a Change Notification Response.

S607. The MME initiates a connection release process according to the indication information, where the connection release procedure is used to change the terminal from the connected state to the idle state.

Specifically, in the embodiment of the present application, the MME may directly initiate a connection release process according to the indication information, where the connection release process is used to change the terminal from the connected state to the idle state; the MME may also be based on the local policy or the subscription data of the terminal. After determining to change the terminal from the connected state to the idle state, a connection release process is initiated, and the connection release process is used to change the terminal from the connected state to the idle state. This embodiment of the present application does not specifically limit this. For related implementations, reference may be made to the embodiment shown in FIG. 5, and details are not described herein again.

Optionally, in step S605, if the SGW determines that the terminal has user plane data transmission, the SGW may send, to the MME, indication information indicating that the user plane data transmission of the terminal is not completed. In this way, after receiving the indication information, the MME may restart the foregoing second inactivity timer to continue to query the SGW for the user plane data transmission status of the terminal. The embodiment of the present application does not specifically limit the situation.

In the connection state control method of the terminal provided by the embodiment of the present application, the terminal user plane activity status query mechanism is introduced on the serving MME of the terminal, and the user plane data transmission status of the terminal is queried according to the local policy or the subscription data of the terminal. And perform different processing according to the feedback of the SGW. The technical limitation that the MME can only passively keep the terminal connected to the terminal state because the MME cannot be aware of the user plane data transmission state of the terminal in the prior art, so that the operator can perform on-demand control on the terminal in the connected state, for example, if The SGW feeds back the user plane data transmission status of the terminal to an inactive state, that is, the user plane data transmission of the terminal ends, and the MME initiates the S1 connection release process to change the terminal from the connected state to the idle state, thereby saving unnecessary network and air interface. Resources improve the performance and efficiency of the network.

The operation of the SGW in the foregoing S601, S605, S606, and S607 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, and the embodiment of the present application does not impose any limitation on this. .

The action of the MME in the foregoing S601, S602, S603, S604, and S607 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not used in this embodiment of the present application. Any restrictions.

In a possible implementation manner, as shown in FIG. 7, a schematic flowchart of a connection state control method of a terminal according to an embodiment of the present application is provided. The connection state control method of the terminal involves the interaction between the terminal, the base station, the serving MME of the terminal, and the SGW of the terminal, and includes the following steps:

S701. The MME sends a request message to the SGW, so that the SGW receives the request message, where the request message is used to request the SGW to report the user plane data transmission status of the terminal.

Specifically, the terminal may initiate an initial attach or location update (such as a Tracking Area Update (TAU)) process, or a packet data network (PDN) connection establishment process initiated by the terminal. The MME sends a request message to the SGW, where the request message is used to request the SGW to report the user plane data transmission status of the terminal, which is not specifically limited in this embodiment.

Specifically, the terminal initiates an initial attach or location update process, or the terminal initiates a PDN connection establishment process, or the specific process of the terminal initiating the bearer resource allocation or modification process may refer to the existing process in the 4G LTE/EPC network, and details are not described herein again. .

Specifically, the request message may be a newly defined message, such as an end user plane activity request message. Of course, the request message may also modify the existing messages in the foregoing process, for example, modify a Create Session Request or a Modify Bearer Request, and add an end user plane in creating a session request or modifying a bearer request. The indication information of the activity status change report is not specifically limited in this embodiment of the present application. Optionally, the SGW sends a response message of the request message to the MME, for example, the response message of the user plane activity request message may be a user plane activity response, or the response message for creating the session request may be a Create Session Response, or The response message for modifying the bearer request may be a Modify Bearer Response, and the SGW accepts the indication information of the execution end user plane activity status change report in the response message of the request message.

Specifically, in the foregoing process, the MME may directly send the request message to the SGW, or the MME may determine to send the request to the SGW after requesting the SGW to report the user plane data transmission status of the terminal based on the local policy or the subscription data of the terminal. The information in this embodiment of the present application is not specifically limited. For related content, refer to the embodiment shown in FIG. 6, and details are not described herein again.

S702-S704, the same as S501-S503.

S705. The SGW sends the indication information to the MME, so that the MME receives the indication information. The indication information is used to indicate that the user plane data transmission of the terminal has ended, that is, the user plane activity status of the terminal changes from active to inactive.

Specifically, the SGW may send the indication information to the MME by using a newly defined message, for example, the newly defined message may be a user activity change notification (UP Activity Change Notification) message, where the user plane activity status change notification carries the Instructions. Of course, the SGW can also send the indication information to the MME through the existing message, for example, the DDN message is modified, and the indication information is carried in the DDN message, which is not specifically limited in this embodiment of the present application.

S706-S707, same as S505-S506.

It should be noted that the step S706 is an optional step. After receiving the indication information, the MME may directly initiate a connection release process according to the indication information, where the connection release process is used to change the terminal from the connected state to the idle state. The embodiment does not specifically limit this.

Optionally, in the embodiment of the present application, after step S705, the method may further include:

The MME sends an acknowledgement message to the SGW, where the acknowledgement information is used to instruct the MME to confirm that the indication information sent by the SGW is received. That is, the MME may, after the SGW transmits the indication information to the MME, immediately send an acknowledgment to the SGW confirming that the indication information transmitted by the SGW has been received. If the SGW sends the indication information to the MME by using the user plane activity status change notification in step S705, the MME may send the confirmation information to the SGW by using the user plane activity status change notification confirmation message; if the SGW sends the DDN message to the MME in step S705. The MME may send the acknowledgment information to the SGW through the DDN acknowledgment message, which is not specifically limited in this embodiment of the present application.

Of course, the MME may also perform the acknowledgment by issuing the release access bearer request message in the connection release process in step S707, which is not specifically limited in this embodiment of the present application.

In the connection state control method of the terminal provided by the embodiment of the present application, a user plane activity state change reporting mechanism is introduced between the MME and the SGW, and if the SGW determines that the terminal is in a user plane inactive state, that is, the user plane data of the terminal. At the end of the transmission, the SGW informs the MME that the terminal is in the inactive state of the user plane, and after obtaining the notification information, the MME initiates the S1 connection release process according to the local policy or the subscription data of the terminal, and changes the terminal from the connected state to the idle state. The technical limitation of the MME in the prior art that the MME can only passively maintain the connected state of the terminal because the MME cannot be aware of the user plane data transmission status of the terminal, so that the operator can perform on-demand control on the terminal in the connected state, for example, The terminal whose time is in the connected state but has no user plane data transmission changes from the connected state to the idle state, thereby saving unnecessary network and air interface resources, and improving the running performance and efficiency of the network.

The operation of the SGW in the foregoing S702, S703, S704, S705, and S707 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not used in this embodiment of the present application. Any restrictions.

The action of the MME in the foregoing S701, S702, S706, and S707 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not limited in this embodiment. .

In the following, the connection state control system 10 of the terminal shown in FIG. 1 is applied to the future 5G network shown in FIG. 3 and other future networks as an example, and the connection control method of the above terminal is explained.

In a possible implementation manner, as shown in FIG. 8 , a schematic flowchart of a connection state control method of a terminal according to an embodiment of the present application is provided. The connection state control method of the terminal involves the interaction between the terminal, the RAN access point, the serving AMF entity of the terminal, the serving SMF entity of the terminal, and the serving UPF entity of the terminal, including the following steps:

S801-S806 is similar to S501-S506.

The only difference is: replacing the base station in the 4G LTE/EPC network with the future 5G network and the RAN access point in other future networks; replacing the MME in the 4G LTE/EPC network with the future 5G network and other future AMF entity in the network; replace the SGW in the 4G LTE/EPC network with the future 5G network and the UPF entity in other networks in the future. In addition, the SMF entity added in the embodiment of the present application is used to forward the information or the message between the UPF entity and the AMF entity. The subscription data in the embodiment of the present application may be more specifically whether the terminal is allowed to enter the inactive connection state (inactive). The connection release process in the embodiment of the present application is an NG1 connection release process. For details, refer to the description in the embodiment shown in FIG. 5, and details are not described herein again.

In the connection state control method of the terminal provided by the embodiment of the present application, the user plane inactivity detection mechanism of the terminal is introduced on the service UPF entity of the terminal, and the terminal is in the inactive state of the user plane, that is, the user plane data transmission of the terminal ends. The UPF entity actively informs the service AMF entity of the terminal that the terminal is in a user-side inactive state. After the AMF entity learns the notification information, the AMF entity initiates an NG1 connection release process to connect the terminal from the connected state according to the local policy or the subscription data of the terminal. The invention is in an idle state, which solves the technical limitation that the AMF entity in the prior art can only passively maintain the terminal in a connected state because the user plane data transmission status of the terminal cannot be perceived, so that the operator can press the terminal in the connected state. Need to control, for example, a terminal that is in a connected state for a long time but has no user plane data transmission changes from a connected state to an idle state, thereby saving unnecessary network and air interface resources, and improving the running performance and efficiency of the network.

The action of the UPF entity in the foregoing S801, S802, S803, S804, and S806 can be performed by the processor 401 in the computer device 400 shown in FIG. 4 calling the application code stored in the memory 403. No restrictions are imposed.

The action of the AMF entity in the above-mentioned S801, S805, and S806 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, which is not limited in this embodiment.

In a possible implementation manner, as shown in FIG. 9 , a schematic flowchart of a connection state control method of a terminal according to an embodiment of the present application is provided. The connection state control method of the terminal involves the interaction between the terminal, the RAN access point, the serving AMF entity of the terminal, the serving SMF entity of the terminal, and the serving UPF entity of the terminal, including the following steps:

S901-S907 is similar to S601-S607.

For the difference, refer to the differences between steps S801-S806 and steps S501-S506 in the embodiment shown in FIG. 8, and details are not described herein again.

In the connection state control method of the terminal provided by the embodiment of the present application, the terminal user plane activity status query mechanism is introduced on the service AMF entity of the terminal, and the user plane data of the terminal is queried according to the local policy or the subscription data of the terminal. The status is transmitted and processed differently according to the feedback of the UPF entity. The technical limitation that the AMF entity in the prior art can only passively maintain the terminal connected state because the user plane data transmission status of the terminal cannot be perceived is allowed, so that the operator can perform on-demand control on the terminal in the connected state, for example, If the UPF entity feeds back the user plane data transmission status of the terminal to be inactive, that is, the user plane data transmission of the terminal ends, the AMF entity initiates the NG1 connection release process to change the terminal from the connected state to the idle state, thereby saving unnecessary Network and air interface resources improve the performance and efficiency of the network.

The action of the UPF entity in the foregoing S901, S905, S906, and S907 can be performed by the processor 401 in the computer device 400 shown in FIG. 4, and the application code stored in the memory 403 is called, and the embodiment of the present application does not do anything. limit.

The actions of the AMF entities in the foregoing S901, S902, S903, S904, and S907 can be performed by the processor 401 in the computer device 400 shown in FIG. 4 calling the application code stored in the memory 403. No restrictions are imposed.

As shown in FIG. 10, a schematic flowchart of a method for controlling connection state of a terminal according to an embodiment of the present application is shown in FIG. The connection state control method of the terminal involves the interaction between the terminal, the RAN access point, the serving AMF entity of the terminal, the serving SMF entity of the terminal, and the serving UPF entity of the terminal, including the following steps:

S1001-S1007, similar to S701-S707.

For the difference, refer to the differences between steps S801-S806 and steps S501-S506 in the embodiment shown in FIG. 8, and details are not described herein again.

In the connection state control method of the terminal provided by the embodiment of the present application, a user plane activity state change reporting mechanism is introduced between the AMF entity and the UPF entity for the terminal, and if the UPF entity determines that the terminal is in the inactive state of the user plane, That is, when the user plane data transmission of the terminal ends, the UPF entity notifies the AMF entity that the terminal is in the inactive state of the user plane, and after the AMF entity learns the notification information, initiates the NG1 connection release according to the local policy or the subscription data of the terminal. The process changes the terminal from the connected state to the idle state, which solves the technical limitation that the AMF entity in the prior art can only passively maintain the terminal in the connected state because it cannot sense the user plane data transmission state of the terminal, so that the operator can The terminal in the connected state performs on-demand control, for example, the terminal that is in the connected state for a long time but has no user plane data transmission changes from the connected state to the idle state, thereby saving unnecessary network and air interface resources and improving the running performance of the network. With efficiency.

The action of the UPF entity in the foregoing S1002, S1003, S1004, S1005, and S1007 may be performed by the processor 401 in the computer device 400 shown in FIG. 4 calling the application code stored in the memory 403, which is used by the embodiment of the present application. No restrictions are imposed.

The actions of the AMF entities in the foregoing S1001, S1002, S1006, and S1007 may be performed by the processor 401 in the computer device 400 shown in FIG. 4, by calling the application code stored in the memory 403, and the embodiment of the present application does not do any limit.

Optionally, in the embodiment shown in FIG. 8 to FIG. 10, the AMF entity may also release the NG1 connection between the terminal and the AMF entity by initiating an NG2 connection release procedure. It should be noted that, unlike the 4G LTE/EPC network, the NG1 connection between the terminal and the AMF entity is separately introduced in the 5G network in the embodiment shown in FIG. 8 to FIG. 10 or other future networks. The connection depends on the NG2 connection between the RAN access point and the AMF. The NG1 connection can be established only after the NG2 connection is established successfully. Otherwise, if the NG2 connection is released, the NG1 connection is also forcibly released. Specifically, the AMF entity initiates the NG1 connection release process, and initiates the NG2 connection release process, which is not specifically limited in this embodiment of the present application.

The solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that each network element, such as the first network device or the second network device, in order to implement the above functions, includes corresponding hardware structures and/or software modules for performing the respective functions. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application may divide the function modules of the first network device and the second network device according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one. Processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

For example, in the case of dividing each functional module by using the corresponding function, FIG. 11 is a schematic diagram showing a possible structure of the first network device involved in the foregoing embodiment. The first network device 1100 includes: a receiving module 1101. And sending module 1102.

The receiving module 1101 is configured to receive indication information from the second network device, where the indication information is used to indicate that the user plane data transmission of the terminal in the connected state has ended.

The sending module 1102 is configured to initiate a connection release process according to the indication information, where the connection release process is used to change the terminal from the connected state to the idle state.

For example, as described above, the first network device 1100 may be an MME or an AMF entity, which is not specifically limited in this embodiment of the present application.

Optionally, the sending module 1102 initiates a connection release process according to the indication information, including: determining, according to the local policy or the subscription data of the terminal, whether to change the terminal from the connected state to the idle state according to the indication information; It becomes idle and initiates a connection release process.

Further, the sending module 1102 is further configured to: before the receiving module 1101 receives the indication information from the second network device, send a request message to the second network device, where the request message is used to request the second network device to report the user plane data of the terminal. Transmission status.

Optionally, the sending, by the sending module 1102, the request message to the second network device, includes: starting a second inactivity timer; if the second inactivity timer expires, the receiving module 1101 does not receive uplink or downlink signaling of the terminal. Or data, the sending module 1102 sends a request message to the second network device.

Optionally, the sending module 1102 is further configured to: after the second inactivity timer is started, if the receiving module 1101 receives uplink or downlink signaling or data of the terminal before the second inactivity timer expires, stopping the Two inactivity timers.

Optionally, the sending module 1102 sends the request message to the second network device, including: determining, according to the local policy or the subscription data of the terminal, whether the second network device is requested to report the user plane data transmission status of the terminal; if it is determined to request the second network device Reporting the user plane data transmission status of the terminal, and sending a request message to the second network device.

Specifically, the local policy includes: a usage type of the terminal, a service type of the terminal, a device type of the terminal, an access priority of the terminal, a mobile mode of the terminal, a wireless access type of the terminal, a dedicated core network type of the terminal, and a terminal. At least one of a data type and a statistical movement information of the terminal.

The subscription data includes: whether to allow the terminal to be in the connected state for a long time.

The specific description of the local policy and the subscription data, and the sending module 1102, according to the indication information, determine whether to change the terminal from the connected state to the idle state based on the local policy or the subscription data of the terminal, and the sending module 1102 is based on the local policy or the terminal. For the specific implementation of the data, the method for determining whether to request the second network device to report the user plane data transmission status of the terminal may be referred to the foregoing method embodiment, and details are not described herein again.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

FIG. 12 is a schematic diagram showing a possible structure of the first network device involved in the foregoing embodiment, where the first network device 1200 includes a communication module 1202. The communication module 1202 can be used to perform the operations that can be performed by the receiving module 1101 and the sending module 1102 in FIG. 11. For details, refer to the embodiment shown in FIG.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In this embodiment, the first network device is presented in a form that divides each functional module corresponding to each function, or the first network device is presented in a form that divides each functional module in an integrated manner. A "module" herein may refer to an Application-Specific Integrated Circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device. In a simple embodiment, those skilled in the art will appreciate that the first network device 1100 or the first network device 1200 may take the form shown in FIG. For example, the receiving module 1101 and the transmitting module 1102 in FIG. 11 can be implemented by the processor 401 and the memory 403 of FIG. Specifically, the receiving module 1101 and the sending module 1102 can be executed by calling the application code stored in the memory 403 by the processor 401, which is not limited in this embodiment. Alternatively, for example, the communication module 1202 in FIG. 12 can be implemented by the processor 401 and the memory 403 of FIG. 4. Specifically, the communication module 1202 can be executed by calling the application code stored in the memory 403 by the processor 401. The embodiment of the present application does not impose any limitation on this.

The embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the first network device, which includes a program designed to execute the foregoing method embodiments. The connection state control of the terminal can be realized by executing the stored program.

The embodiment of the present application further provides a computer program, which includes instructions, when the computer program is executed by a computer, to enable the computer to execute the flow executed by the first network device in the foregoing method embodiment.

After the first network device provided by the embodiment of the present application, after the lightweight connection state or the inactive connection state is introduced, the first network device may receive after the second network device senses that the terminal in the connected state has no user plane data transmission. Initiating a connection release process indication information from the second network device, and changing the terminal from the connected state to the idle state according to the indication information, thereby solving that the network side can only passively because the user plane data transmission state of the terminal cannot be perceived. The technical limitation of keeping the terminal connected state allows the operator to perform on-demand control on the terminal in the connected state, for example, the terminal that is in the connected state for a long time but has no user plane data transmission changes from the connected state to the idle state, thereby saving Unnecessary network and air interface resources improve the performance and efficiency of the network.

For example, in the case of dividing each functional module by using corresponding functions, FIG. 13 is a schematic structural diagram of a second network device involved in the foregoing embodiment. The second network device 1300 includes: a determining module 1301. And sending module 1302.

The determining module 1301 is configured to determine whether the terminal in the connected state has user plane data transmission.

The sending module 1302 is configured to: if the determining module 1301 determines that the terminal has no user plane data transmission, send the indication information to the first network device, where the indication information is used to indicate that the user plane data transmission of the terminal in the connected state has ended.

For example, as described above, the second network device 1300 may be an SGW or an UPF entity, which is not specifically limited in this embodiment of the present application.

Optionally, as shown in FIG. 13, the second network device 1300 further includes a receiving module 1303.

The determining module 1301 determines whether the terminal in the connected state has user plane data transmission, including starting the first inactivity timer; if the first inactivity timer expires, the receiving module 1303 does not receive the uplink or downlink signaling of the terminal or The data determines that the terminal has no user plane data transmission.

Optionally, the determining module 1301 is further configured to: after the first inactivity timer is started, if the receiving module 1303 receives the uplink or downlink signaling or data of the terminal before the first inactivity timer expires, stopping the An inactivity timer.

Further, the determining module 1301 determines whether the terminal in the connected state has user plane data transmission, including: if the user plane data transmission status of the terminal changes from the active state to the inactive state, the determining module 1301 determines that the terminal has no user plane data transmission.

Optionally, as shown in FIG. 13, the second network device 1300 further includes a receiving module 1303.

The receiving module 1303 is configured to: before the determining module 1301 determines whether the terminal in the connected state has user plane data transmission, receive a request message sent by the first network device, where the request message is used to request the second network device 1300 to report the user plane data of the terminal. Transmission status.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

FIG. 14 is a schematic diagram showing a possible structure of a second network device involved in the foregoing embodiment, where the second network device 1400 includes: a processing module 1401 and a communication. Module 1402. The processing module 1401 can be used to perform the operations that can be performed by the determining module 1301 in FIG. 13, and the communications module 1402 can be used to perform operations performed by the receiving module 1303 and the sending module 1302 in FIG. The embodiments of the present application are not described herein again.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In this embodiment, the second network device is presented in a form that divides each functional module corresponding to each function, or the second network device is presented in a form that divides each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above. In a simple embodiment, those skilled in the art will appreciate that the second network device 1300 or the second network device 1400 may take the form shown in FIG. For example, the receiving module 1303, the transmitting module 1302, and the determining module 1301 in FIG. 13 can be implemented by the processor 401 and the memory 403 of FIG. Specifically, the receiving module 1303, the sending module 1302, and the determining module 1301 may be executed by calling the application code stored in the memory 403 by the processor 401, which is not limited in this embodiment. Alternatively, for example, the processing module 1401 and the communication module 1402 in FIG. 14 may be implemented by the processor 401 and the memory 403 of FIG. 4. Specifically, the processing module 1401 and the communication module 1402 may be called by the processor 401 in the memory 403. The stored application code is executed, and the embodiment of the present application does not impose any limitation on this.

The embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the second network device, which includes a program designed to execute the foregoing method embodiments. The connection state control of the terminal can be realized by executing the stored program.

The embodiment of the present application further provides a computer program, the computer program comprising instructions, when the computer program is executed by the computer, to enable the computer to execute the flow executed by the second network device in the foregoing method embodiment.

After the second network device provided by the embodiment of the present application, after the lightweight connection state or the inactive connection state is introduced, the second network device can detect whether the terminal in the connected state has user plane data transmission, and determines that it is in the connected state. After the terminal has no user plane data transmission, the first network device is instructed to initiate a connection release process, and the connection release process is used to change the terminal from the connected state to the idle state, thereby solving the problem that the network side cannot sense the user plane data transmission state of the terminal. The technology can only passively maintain the connection state of the terminal, so that the operator can perform on-demand control on the terminal in the connected state. For example, the terminal that is in the connected state for a long time but has no user plane data transmission changes from the connection state. The idle state saves unnecessary network and air interface resources and improves the running performance and efficiency of the network.

Although the present application has been described herein in connection with the various embodiments, those skilled in the art can Other variations of the disclosed embodiments are achieved. 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 several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, apparatus (device), or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code. The computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.

The present application is described with reference to flowchart illustrations and/or block diagrams of the methods, apparatus, and computer program products of the embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the present invention has been described in connection with the specific embodiments and embodiments thereof, various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the description and drawings are to be regarded as It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims (33)

A method for controlling a connection state of a terminal, the method comprising: The first network device receives the indication information from the second network device, where the indication information is used to indicate that the user plane data transmission of the terminal in the connected state has ended; And the first network device initiates a connection release procedure according to the indication information, where the connection release procedure is used to change the terminal from the connected state to an idle state. The method according to claim 1, wherein the first network device initiates a connection release process according to the indication information, including: Determining, according to the indication information, whether the terminal is changed from the connected state to the idle state according to the local policy or the subscription data of the terminal, according to the indication information; And if the first network device determines to change the terminal from the connected state to an idle state, the first network device initiates the connection release procedure. The method according to claim 1 or 2, further comprising: before the receiving, by the first network device, the indication information from the second network device, The first network device sends a request message to the second network device, where the request message is used to request the second network device to report a user plane data transmission status of the terminal. The method according to claim 3, wherein the sending, by the first network device, the request message to the second network device comprises: The first network device starts a second inactivity timer; If the first network device does not receive uplink or downlink signaling or data of the terminal when the second inactivity timer expires, the first network device sends the Request message. The method of claim 4, after the first network device starts the second inactivity timer, further comprising: If the first network device receives uplink or downlink signaling or data of the terminal before the second inactivity timer expires, the first network device stops the second inactivity timer. The method according to any one of claims 3-5, wherein the first network device sends a request message to the second network device, including: Determining, by the first network device, the second network device, according to the local policy or the subscription data of the terminal, whether the second network device is requested to report the user plane data transmission status of the terminal; And if the first network device determines that the second network device is requested to report the user plane data transmission status of the terminal, the first network device sends a request message to the second network device. The method according to claim 2 or 6, wherein the local policy comprises: a usage type of the terminal, a service type of the terminal, a device type of the terminal, an access priority of the terminal, a mobile mode of the terminal, and a terminal At least one of a wireless access type, a dedicated core network type of the terminal, a data type of the terminal, and statistical mobile information of the terminal. The method according to claim 2 or 6, wherein the subscription data comprises: information on whether the terminal is allowed to be in the connected state for a long time. The method according to any of claims 1-8, wherein the first network device comprises a mobility management entity MME or an access and mobility management function AMF entity. A method for controlling a connection state of a terminal, the method comprising: The second network device determines whether the terminal in the connected state has user plane data transmission; If the second network device determines that the terminal has no user plane data transmission, the second network device sends indication information to the first network device, where the indication information is used to indicate user plane data of the terminal in the connected state. The transfer has ended. The method according to claim 10, wherein the second network device determines whether the terminal in the connected state has user plane data transmission, including: The second network device starts a first inactivity timer; If the second network device does not receive uplink or downlink signaling or data of the terminal when the first inactivity timer expires, the second network device determines that the terminal has no user plane data transmission. . The method according to claim 11, wherein after the second network device starts the first inactivity timer, the method further includes: If the second network device receives uplink or downlink signaling or data of the terminal before the first inactivity timer expires, the second network device stops the first inactivity timer. The method according to claim 10, wherein the second network device determines whether the terminal in the connected state has user plane data transmission, including: If the user plane data transmission status of the terminal changes from an active state to an inactive state, the second network device determines that the terminal has no user plane data transmission. The method according to any one of claims 10 to 13, wherein before the second network device determines whether the terminal in the connected state has user plane data transmission, the method further includes: The second network device receives a request message sent by the first network device, where the request message is used to request the second network device to report a user plane data transmission status of the terminal. The method according to any of claims 10-14, wherein the second network device comprises a serving gateway SGW or a user plane function UPF entity. A first network device, where the first network device includes: a receiving module and a sending module; The receiving module is configured to receive indication information from the second network device, where the indication information is used to indicate that user plane data transmission of the terminal in the connected state has ended; The sending module is configured to initiate a connection release process according to the indication information, where the connection release process is used to change the terminal from the connected state to an idle state. The first network device according to claim 16, wherein the sending module is specifically configured to: Determining, according to the local information or the subscription data of the terminal, whether to change the terminal from the connected state to an idle state according to the indication information; if it is determined to change the terminal from the connected state to an idle state, initiate The connection release process. A first network device according to claim 16 or 17, wherein The sending module is further configured to: before the receiving module receives the indication information from the second network device, send a request message to the second network device, where the request message is used to request the second network device to report the location The user plane data transmission status of the terminal. The first network device according to claim 18, wherein the sending module sends a request message to the second network device, including: And a second inactivity timer is started; if the receiving module does not receive uplink or downlink signaling or data of the terminal when the second inactivity timer expires, sending the Request message. The first network device according to claim 19, wherein the sending module is further configured to: after the starting the second inactivity timer, before the second inactivity timer expires, The receiving module receives the uplink or downlink signaling or data of the terminal, and stops the second inactivity timer. The first network device according to any one of claims 18 to 20, wherein the sending module sends a request message to the second network device, including: Determining, according to the local policy or the subscription data of the terminal, whether the second network device is requested to report the user plane data transmission status of the terminal; if it is determined that the second network device is requested to report the user plane data transmission status of the terminal Sending a request message to the second network device. The first network device according to claim 17 or 21, wherein the local policy comprises: a usage type of the terminal, a service type of the terminal, a device type of the terminal, an access priority of the terminal, and a mobile mode of the terminal. At least one of a wireless access type of the terminal, a dedicated core network type of the terminal, a data type of the terminal, and statistical mobile information of the terminal. The first network device according to claim 17 or 21, wherein the subscription data comprises: information on whether the terminal is allowed to be in the connected state for a long time. The first network device according to any one of claims 16 to 23, wherein the first network device comprises a mobility management entity MME or an access and mobility management function AMF entity. A second network device, the second network device includes: a determining module and a sending module; The determining module is configured to determine whether the terminal in the connected state has user plane data transmission; The sending module is configured to: if the determining module determines that the terminal has no user plane data transmission, send the indication information to the first network device, where the indication information is used to indicate user plane data transmission of the terminal in the connected state It is over. The second network device according to claim 25, wherein the second network device further comprises a receiving module; The determining module is specifically configured to: Deactivating a first inactivity timer; if the receiving module does not receive uplink or downlink signaling or data of the terminal when the first inactivity timer expires, determining that the terminal has no user plane data transmission . The second network device according to claim 26, wherein the determining module is further configured to: after the first inactivity timer is started, before the first inactivity timer expires, The receiving module receives the uplink or downlink signaling or data of the terminal, and stops the first inactivity timer. The second network device according to claim 25, wherein the determining module is specifically configured to: If the user plane data transmission status of the terminal changes from an active state to an inactive state, it is determined that the terminal has no user plane data transmission. The second network device according to any one of claims 25 to 28, wherein the second network device further comprises a receiving module; The receiving module is configured to: before the determining module determines whether the terminal in the connected state has user plane data transmission, receive a request message sent by the first network device, where the request message is used to request the second network The device reports the user plane data transmission status of the terminal. The second network device according to any one of claims 25-29, wherein the second network device comprises a serving gateway SGW or a user plane function UPF entity. A first network device, comprising: a processor, a memory, a bus, and a communication interface; The memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the first network device is in operation, the processor executes the computer execution instruction stored in the memory, The first network device is configured to perform the connection state control method of the terminal according to any one of claims 1-9. A second network device, comprising: a processor, a memory, a bus, and a communication interface; The memory is configured to store a computer execution instruction, the processor is coupled to the memory via the bus, and when the second network device is in operation, the processor executes the computer execution instruction stored in the memory, The second network device is configured to perform the connection state control method of the terminal according to any one of claims 10-15. A connection state control system for a terminal, characterized in that the connection state control system of the terminal comprises the first network device according to any one of claims 16-24 and the method of any one of claims 25-30 Second network device; Alternatively, the connection state control system of the terminal comprises the first network device according to claim 31 and the second network device according to claim 32.

Images