A method and apparatus for managing a terminal mobility mode

Abstract

A terminal mobility mode management method and device are provided, which are used for flexibly configuring and managing the mobility mode of a terminal according to the actual application scenario of the terminal, thereby optimizing network performance. The method comprises the following steps: a control plane function (CPF) entity acquires the mobility mode related information of a terminal; the CPF entity determines a first mobility mode of the terminal according to the mobility mode related information of the terminal; and the CPF entity sends the determined first mobility mode to a radio access network (RAN) node, and the first mobility mode is used by the RAN node to determine a second mobility mode of the terminal.

Description

[0001] This application is a divisional application of Chinese Patent Application No. 201680085471.4, filed on August 23, 2016, entitled "A Method and Apparatus for Managing Terminal Mobility Modes", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a method and apparatus for managing terminal mobility modes. Background Technology

[0003] In 5G communication systems, the connection status of a terminal can include signaling connection status and session connection status. Signaling connection status includes Non-Access Stratum (NAS) Connection Management (CM) status and Radio Resource Control (RRC) Signaling Connection Management (RRC) status. NAS signaling connection management status, represented by NCM, indicates the establishment status of a NAS signaling connection between the terminal and the core network, such as NCM_IDLE and NCM_CONNECTED. NCM_IDLE indicates that no signaling connection has been established between the terminal and the core network; NCM_CONNECTED indicates that a signaling connection has been established between the terminal and the core network through a RAN node. RRC signaling connection management status indicates the establishment status of an RRC signaling connection between the terminal and the radio access network, such as RRC_IDLE, RRC_CONNECTED, RRC_INACTIVE, and RRA_PCH. RRC_IDLE indicates that no RRC connection has been established between the terminal and the RAN node; RRC_CONNECTED indicates that an RRC connection has been established between the terminal and the RAN node; RRC_INACTIVE indicates that after the data packet is sent, the RAN node still saves the terminal's RRC context and bearer context information; RRA identifies the coverage area of ​​a RAN node, and RRA_PCH indicates that when the terminal is in an idle state, the network only pages the terminal within this RRA range.

[0004] Session connection management states indicate the activity state of a session context between the terminal and the network, including SESSION CONTEXT ACTIVE, SESSION CONTEXT INACTIVE, and SESSION CONTEXT SUSPEND. SESSION CONTEXT ACTIVE indicates that the session context is active, meaning it has been saved; SESSION CONTEXT INACTIVE indicates that the session context is deactivated, meaning it has been deleted; and SESSION CONTEXT SUSPEND indicates that the session context is saved, but no data is being sent or received.

[0005] For signaling connection states, different states represent the reachability level of the terminal's location, i.e., the accuracy with which the core network can determine the terminal's location. For example, when the terminal is in the NCM_IDLE state, it means that no signaling connection has been established between the terminal and the core network. The core network can determine the terminal's location with an accuracy of the location area pre-assigned to the terminal by the core network, which includes the coverage area of ​​multiple Radio Access Network (RAN) nodes. When the terminal is in the NCM_CONNECTED state, it means that a signaling connection has been established between the terminal and the core network through a RAN node. The core network can determine the terminal's location with an accuracy of the coverage area of ​​one RAN node. When downlink data is available, if the terminal is in the NCM_IDLE state, the core network needs to page the terminal on multiple RAN nodes within the terminal's location area to send data to the terminal, which incurs paging overhead. Of course, when the terminal is in the NCM_CONNECTED state, the core network can directly send data to the RAN node where the terminal is currently located without paging, which reduces paging overhead. However, if the terminal remains in the NCM_CONNECTED state, when the terminal moves to a new RAN node, it needs to update its location with the core network, which incurs location update overhead. Therefore, a balance needs to be struck between paging overhead and location update overhead to minimize the total overhead.

[0006] In existing technologies, the connection state and state transition conditions of a terminal are pre-configured in the terminal and network-side equipment. The pre-configured signaling connection state and state transition conditions of the terminal and core network are as follows: before sending or receiving data, the terminal needs to establish a signaling connection with the core network in the NCM_CONNECTED state; after data transmission and reception are completed, the signaling is released, that is, the signaling connection state is transitioned to NCM_IDLE. Under this fixed configuration, it is difficult to achieve a balance between the paging overhead and the location update overhead.

[0007] For session connection state, it represents the active state of a service's session context between the terminal and the network. In existing technologies, the terminal's connection state and state transition conditions are pre-configured in the terminal and network-side devices. The pre-configured session connection state and state transition conditions for the terminal in the terminal and RAN node are as follows: when the terminal is sending and receiving service data, the session connection state is SESSION CONTEXT ACTIVE; when the service data transmission ends, the session connection state transitions to SESSION CONTEXT INACTIVE, and the RAN node deletes the session context. Based on this fixed configuration, for terminals with frequent data services, such as sending and receiving data every minute, the session context needs to be re-established each time data is sent or received, resulting in significant signaling overhead. For terminals with infrequent data services, such as sending and receiving data every day, continuously storing the session context incurs additional storage and maintenance overhead.

[0008] In summary, in the prior art, the connection state and state transition conditions of the terminal are pre-configured in the terminal and network-side devices. This fixed configuration often cannot be flexibly changed according to the actual application scenario of the terminal, thereby reducing network performance. Summary of the Invention

[0009] This application provides a method and apparatus for managing terminal mobility modes. The mobility modes include mobility management configuration information, such as connection status, location area list, location update timer, paging area, and other configuration information, to flexibly configure and manage the terminal's mobility management configuration information, thereby optimizing network performance.

[0010] Firstly, a method for managing terminal mobility modes is provided. This method is implemented as follows: a Control Plane Function (CPF) entity obtains mobility mode-related information of the terminal and determines a first mobility mode of the terminal based on the mobility mode-related information. The CPF entity sends the first mobility mode to a Radio Access Network (RAN) node, so that the RAN node determines a second mobility mode of the terminal based on the first mobility mode. In this way, the CPF entity can select a suitable mobility mode for the terminal according to the actual application scenario of the terminal, and the RAN node determines the final mobility mode configured for the terminal and notifies the terminal. This breaks the fixed mobility mode configuration of the terminal, enabling flexible configuration and management of the terminal's mobility mode according to the actual application scenario, thereby optimizing network performance.

[0011] In one possible design, the CPF entity sends the terminal's first mobility mode directly to the terminal.

[0012] In one possible design, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical mobility event statistics. The mobility mode capability information includes the mobility modes supported by the terminal; the service characteristic information includes at least one of the terminal's periodic service indications, single service communication duration, and service cycle; the historical mobility event statistics include handovers or location updates occurring during a specific time period, or handovers or location updates occurring at a specific location, or movement speed types occurring during a specific time period or at a specific location. This allows for full utilization of the terminal's historical data to obtain the terminal's actual application scenario, enabling the CPF entity and RAN node to accurately determine the mobility mode suitable for the terminal's actual application scenario.

[0013] In one possible design, the CPF entity determines the first mobility mode of the terminal based on the terminal's mobility mode information, which is achieved in the following ways: the CPF entity determines the mobility modes that the terminal can support based on the terminal's mobility mode capability information; the CPF entity selects a mobility mode from the mobility modes that the terminal can support based on the terminal's historical mobility event statistics; or, the CPF entity selects a mobility mode from the mobility modes that the terminal can support based on the terminal's service characteristic information; or, the CPF entity selects a mobility mode from the mobility modes that the terminal can support based on both the terminal's service characteristic information and the historical mobility event statistics.

[0014] In one possible design, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0015] In one possible design, the connection state includes at least one of signaling connection state and session connection state; the signaling connection state includes non-access stratum (NAS) signaling connection state or radio resource control (RRC) signaling connection state.

[0016] In one possible design, the RAN node also sends the determined second mobility mode to the CPF entity. This enables the terminal, RAN node, and CPF entity to know the mobility mode used by the terminal, thus achieving network matching consistency.

[0017] Secondly, a method for managing terminal mobility modes is provided, comprising: a Radio Access Network (RAN) node receiving a first mobility mode of a terminal sent by a Control Plane Function (CPF) entity; the RAN node determining a second mobility mode of the terminal based on the first mobility mode; and the RAN node sending the determined second mobility mode to the terminal. In this way, the RAN node can configure a mobility mode for the terminal based on a mobility mode sent by the CPF entity that matches the actual application scenario of the terminal, and notify the terminal accordingly. This breaks the fixed mobility mode configuration of the terminal, enabling flexible configuration and management of the terminal's mobility mode according to the actual application scenario, thereby optimizing network performance.

[0018] In one possible design, the RAN node determines the second mobility mode of the terminal based on the first mobility mode, which can be achieved in the following way: the RAN node pre-obtains the mobility modes it can support; if the RAN node can support the mobility management configuration information included in the first mobility mode, then the RAN node determines the first mobility mode as the second mobility management configuration information; or, if the RAN node does not support the mobility management configuration information included in the first mobility mode, then the RAN node selects the default mobility mode as the second mobility mode. Based on the flexible configuration of the terminal's mobility mode, the RAN node's own configuration is fully considered to ensure normal operation between the RAN node and the terminal's mobility modes.

[0019] In one possible design, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0020] In one possible design, the connection state includes at least one of signaling connection state and session connection state; the signaling connection state includes non-access stratum (NAS) signaling connection state or radio resource control (RRC) signaling connection state.

[0021] In one possible design, the RAN node also sends the determined second mobility mode to the CPF entity. This enables the terminal, RAN node, and CPF entity to know the mobility mode used by the terminal, thus achieving network matching consistency.

[0022] Thirdly, a method for managing terminal mobility modes is provided, comprising: a Radio Access Network (RAN) node receiving mobility mode-related information of a terminal sent by a Control Plane Function (CPF) entity; the RAN node determining the terminal's mobility mode based on the mobility mode-related information; and the RAN node sending the mobility mode to the terminal. In this way, the RAN node can select a suitable mobility mode for the terminal based on its actual application scenario and notify the terminal, breaking the fixed mobility mode configuration of the terminal and enabling flexible configuration and management of the terminal's mobility mode according to its actual application scenario, thereby optimizing network performance.

[0023] In one possible design, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical mobility event statistics. The mobility mode capability information includes the mobility modes supported by the terminal; the service characteristic information includes at least one of the terminal's periodic service indications, single service communication duration, and service cycle; the historical mobility event statistics include handovers or location updates occurring during a specific time period, or handovers or location updates occurring at a specific location, or movement speed types occurring during a specific time period or at a specific location. This allows for full utilization of the terminal's historical data to obtain the terminal's actual application scenario, enabling the CPF entity and RAN node to accurately determine the mobility mode suitable for the terminal's actual application scenario.

[0024] In one possible design, the RAN node determines the mobility mode of the terminal based on the terminal's mobility mode information, which can be achieved in the following ways: the RAN node determines the mobility modes supported by the terminal based on the terminal's mobility mode capability information; the RAN node selects a mobility mode from the mobility modes supported by the terminal based on the terminal's historical mobility event statistics; or, the RAN node selects a mobility mode from the mobility modes supported by the terminal based on the terminal's service characteristic information; or, the RAN node selects a mobility mode from the mobility modes supported by the terminal based on both the terminal's service characteristic information and the historical mobility event statistics.

[0025] In one possible design, the mobility mode includes at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0026] In one possible design, the connection state includes at least one of signaling connection state and session connection state; the signaling connection state includes non-access stratum (NAS) signaling connection state or radio resource control (RRC) signaling connection state.

[0027] In one possible design, the RAN node also sends the determined mobility mode to the CPF entity. This enables the terminal, RAN node, and CPF entity to know the mobility mode used by the terminal, thus achieving network matching consistency.

[0028] Fourthly, a method for managing terminal mobility modes is provided, comprising: the terminal sending mobility mode-related information to a Control Plane Function (CPF) entity, wherein the mobility mode-related information is used to determine a first mobility mode of the terminal; the terminal receiving a second mobility mode sent by a RAN node; and the terminal determining a mobility management configuration information mobility mode to be adopted based on the second mobility mode. In this way, the terminal does not apply a fixed configuration of mobility modes it can support, but flexibly adopts a mobility mode according to the configuration of the network-side equipment, achieving the goal of matching the terminal's mobility mode with the actual application scenario of the terminal.

[0029] In one possible design, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical mobility event statistics; wherein, the mobility mode capability information includes the mobility modes that the terminal can support, the service characteristic information includes at least one of the terminal's periodic service indication, single service communication duration, and service cycle, and the historical mobility event statistics include the terminal switching or location updating during a specific time period, or the historical mobility event statistics include the switching or location updating during a specific location, or the historical mobility event statistics include the movement speed type occurring during a specific time period or at a specific location.

[0030] Fifthly, a terminal mobility mode management device is provided, which has the function of implementing the behavior of the CPF entity in the first aspect and any possible design of the first aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0031] Sixthly, a terminal mobility mode management device is provided, which has the function of implementing the RAN node behavior in any possible design of the second aspect and the above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0032] In a seventh aspect, a terminal mobility mode management device is provided, which has the function of implementing the RAN node behavior in any possible design of the third aspect described above. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0033] Eighthly, a terminal is provided that has the function of implementing the terminal behavior in any of the possible designs of the fourth aspect and the above-described fourth aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0034] A ninth aspect provides a CPF entity, comprising: a transceiver, a memory, and a processor, wherein the memory stores a set of programs, and the processor invokes the programs stored in the memory to perform the following operations: acquiring mobility mode information related to a terminal; determining a first mobility mode of the terminal based on the acquired mobility mode information; and transmitting the first mobility mode to a Radio Access Network (RAN) node via the transceiver, wherein the first mobility mode is used by the RAN node to determine a second mobility mode of the terminal. In this way, the CPF entity can select a suitable mobility mode for the terminal based on its actual application scenario, and determine the final mobility mode configured for the terminal through the RAN node and notify the terminal, breaking the fixed mobility mode configuration of the terminal and enabling flexible configuration and management of the terminal's mobility mode according to its actual application scenario, thereby optimizing network performance.

[0035] In one possible design, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical mobility event statistics. The mobility mode capability information includes the mobility modes supported by the terminal; the service characteristic information includes at least one of the terminal's periodic service indications, single service communication duration, and service cycle; the historical mobility event statistics include handovers or location updates occurring during a specific time period, or handovers or location updates occurring at a specific location, or movement speed types occurring during a specific time period or at a specific location. This allows for full utilization of the terminal's historical data to obtain the terminal's actual application scenario, enabling the CPF entity and RAN node to accurately determine the mobility mode suitable for the terminal's actual application scenario.

[0036] In one possible design, the processor is configured to: determine the mobility modes that the terminal can support based on the terminal's mobility mode capability information; select a mobility mode from the mobility modes that the terminal can support based on the terminal's historical mobility event statistics; or, select a mobility mode from the mobility modes that the terminal can support based on the terminal's service characteristic information; or, select a mobility mode from the mobility modes that the terminal can support based on both the terminal's service characteristic information and the historical mobility event statistics.

[0037] In one possible design, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0038] In one possible design, the connection state includes at least one of signaling connection state and session connection state; the signaling connection state includes non-access stratum (NAS) signaling connection state or radio resource control (RRC) signaling.

[0039] In a tenth aspect, a Radio Access Network (RAN) node is provided, comprising: a transceiver, a memory, and a processor, wherein the memory stores a set of programs, and the processor invokes the programs stored in the memory to perform the following operations: receiving a first mobility mode of a terminal sent by a Control Plane Function (CPF) entity via the transceiver; determining a second mobility mode of the terminal based on the first mobility mode; and sending the determined second mobility mode to the terminal. In this way, the RAN node can configure a mobility mode for the terminal based on a mobility mode sent by the CPF entity that matches the actual application scenario of the terminal, and notify the terminal, breaking the fixed mobility mode configuration of the terminal and enabling flexible configuration and management of the terminal's mobility mode according to the actual application scenario of the terminal, thereby optimizing network performance.

[0040] In one possible design, the processor is configured to: pre-obtain the mobility modes supported by the CPF entity; if the CPF entity supports the mobility management configuration information included in the first mobility mode, then determine the first mobility mode as the second mobility mode; or, if the CPF entity does not support the mobility management configuration information included in the first mobility mode, then select the default mobility mode as the second mobility mode. Based on the flexible configuration of the terminal's mobility mode, the processor fully considers the RAN node's own configuration to ensure normal operation between the RAN node and the terminal's mobility modes.

[0041] In one possible design, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0042] In one possible design, the connection state includes at least one of signaling connection state and session connection state; the signaling connection state includes non-access stratum (NAS) signaling connection state or radio resource control (RRC) signaling connection state.

[0043] Eleventhly, a Radio Access Network (RAN) node is provided, comprising: a transceiver, a memory, and a processor, wherein the memory stores a set of programs, and the processor invokes the programs stored in the memory to perform the following operations: receiving terminal mobility mode information transmitted by a Control Plane Function (CPF) entity via the transceiver; determining the terminal's mobility mode based on the mobility mode information received by the receiving unit; and transmitting the determined mobility mode to the terminal. In this way, the RAN node can select a suitable mobility mode for the terminal based on its actual application scenario and notify the terminal, breaking the fixed mobility mode configuration of the terminal and enabling flexible configuration and management of the terminal's mobility mode according to its actual application scenario, thereby optimizing network performance.

[0044] In one possible design, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical mobility event statistics. The mobility mode capability information includes the mobility modes supported by the terminal; the service characteristic information includes at least one of the terminal's periodic service indications, single service communication duration, and service cycle; the historical mobility event statistics include handovers or location updates occurring during a specific time period, or handovers or location updates occurring at a specific location, or movement speed types occurring during a specific time period or at a specific location. This allows for full utilization of the terminal's historical data to obtain the terminal's actual application scenario, enabling the CPF entity and RAN node to accurately determine the mobility mode suitable for the terminal's actual application scenario.

[0045] In one possible design, the processor is configured to: determine the mobility modes supported by the terminal based on the terminal's mobility mode capability information; select a mobility mode among the mobility modes supported by the terminal based on the terminal's historical mobility event statistics; or, select a mobility mode among the mobility modes supported by the terminal based on the terminal's service characteristic information; or, select a mobility mode among the mobility modes supported by the terminal based on both the terminal's service characteristic information and the historical mobility event statistics.

[0046] In one possible design, the mobility mode includes at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0047] In one possible design, the connection state includes at least one of signaling connection state and session connection state; the signaling connection state includes non-access stratum (NAS) signaling connection state or radio resource control (RRC) signaling connection state.

[0048] In a twelfth aspect, a terminal is provided, comprising: a transceiver, a memory, and a processor, wherein the memory stores a set of programs, and the processor invokes the programs stored in the memory to perform the following operations: sending mobility mode-related information of the terminal to a Control Plane Function (CPF) entity, the mobility mode-related information being used to determine a first mobility mode of the terminal; receiving a second mobility mode sent by a RAN node; and determining mobility management configuration information adopted by the terminal based on the second mobility mode. In this way, the terminal does not apply a fixed configuration based on the mobility modes it can support, but flexibly adopts mobility modes according to the configuration of network-side devices, achieving the goal of matching the terminal's mobility mode with the actual application scenario of the terminal.

[0049] In one possible design, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical statistics of mobility events;

[0050] The mobility mode capability information includes the mobility modes that the terminal can support; the service characteristic information includes at least one of the terminal's periodic service indication, single service communication duration, and service cycle; the mobility event historical statistics information includes the terminal switching or location updating during a specific time period; or the mobility event historical statistics information includes the switching or location updating during a specific location; or the mobility event historical statistics information includes the movement speed type occurring during a specific time period or at a specific location. Attached Figure Description

[0051] Figure 1 This is a diagram of the communication system architecture in an embodiment of this application;

[0052] Figure 2 This is one of the flowcharts for the terminal mobility mode management method in the embodiments of this application;

[0053] Figure 3 This is the second flowchart of the terminal mobility mode management method in the embodiments of this application;

[0054] Figure 4 This is the third flowchart of the terminal mobility mode management method in the embodiments of this application;

[0055] Figure 5 This is the fourth flowchart of the terminal mobility mode management method in the embodiments of this application;

[0056] Figure 6 This is one of the structural diagrams of the terminal mobility mode management device in the embodiments of this application;

[0057] Figure 7 This is the second structural diagram of the terminal mobility mode management device in the embodiments of this application;

[0058] Figure 8 This is the third structural diagram of the terminal mobility mode management device in the embodiments of this application;

[0059] Figure 9 This is one of the terminal structure diagrams in the embodiments of this application;

[0060] Figure 10 This is a schematic diagram of the CPF entity structure in the embodiments of this application;

[0061] Figure 11 This is one of the RAN node structure diagrams in the embodiments of this application;

[0062] Figure 12 This is the second terminal structure diagram in the embodiments of this application;

[0063] Figure 13 This is the second terminal structure diagram in the embodiments of this application. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0065] To address the problem in existing technologies where fixed mobility management configuration information for terminals cannot be flexibly changed according to the actual application scenarios of the terminals, thereby reducing network performance, this application provides a method and apparatus for managing terminal mobility modes. The Control Plane Function (CPF) entity selects a suitable mobility mode for the terminal based on the actual application scenarios of the terminal, determines the final mobility mode configured for the terminal through the RAN node, and notifies the terminal. This breaks the fixed mobility mode configuration of the terminal, enabling flexible configuration and management of the terminal's mobility mode according to the actual application scenarios of the terminal, thereby optimizing network performance.

[0066] The method provided in this application is applicable to various wireless access technology network systems, such as Long Term Evolution (LTE) systems, 5G communication systems, or more future communication systems. This application will use a 5G communication system as an example to illustrate the detailed solution.

[0067] 5G communication systems flexibly construct networks, which are further abstracted into network slices. Network slicing technology divides a physical network into multiple virtual end-to-end networks. Each virtual network, including its devices, access, transmission, and core network, is logically independent. Each network slice is instantiated from an independent network function or a combination of functions, possessing different functional characteristics and catering to different needs and services.

[0068] like Figure 1As shown in the embodiment of this application, the communication system architecture 100 includes: a terminal 101, a RAN node 102, and several network slices 103. Each network slice 103 includes a CPF entity 104 and a user plane function (UPF) entity 105. The CPF entity 104 mainly handles control plane-related signaling message processing, including: mobility management (MM) functions such as device access authentication, security encryption, and location registration; session management (SM) functions such as establishing, releasing, and modifying user plane transmission paths; and policy and charging (PC) control functions related to Quality of Service (QoS) and charging. In this embodiment, the CPF entity is an entity that simultaneously possesses MM and SM functions; or, the CPF entity includes an entity possessing either MM or SM functions. The UPF entity 105 mainly performs functions such as routing and forwarding user plane data. The terminal 101 can access one or more network slices 103 through the RAN node 102.

[0069] based on Figure 1 The communication system architecture shown below will be described in detail with reference to the accompanying drawings and preferred embodiments.

[0070] See Figure 2 As shown, the management method flow of terminal mobility mode in this application embodiment is as follows.

[0071] Step 201: The terminal sends its mobility mode information to the CPF entity.

[0072] The mobility mode information is used by the CPF entity to determine the terminal's first mobility mode, and the first mobility mode is used by the RAN node to determine the terminal's second mobility mode.

[0073] Optionally, mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical mobility event statistics. Specifically, mobility mode capability information includes the mobility modes supported by the terminal; service characteristic information includes at least one of the terminal's periodic service indications, duration of a single service communication, and service cycle; and historical mobility event statistics include handovers or location updates that occurred during a specific time period, or handovers or location updates that occurred at a specific location, or movement speed types that occurred during a specific time period or at a specific location.

[0074] Optionally, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: mobility mode, location area list, location update timer, and paging area.

[0075] Step 202: The CPF entity obtains information related to the terminal's mobility mode.

[0076] CPF entities can be obtained by receiving mobility mode information from the terminal, or by obtaining the terminal's subscription information.

[0077] Mobility mode-related information is determined based on the application scenario of the terminal, and generally includes information such as the terminal's capabilities, mobility characteristics, and service characteristics. Specifically, it may include one or any combination of the following information:

[0078] Mobility mode capability information, service characteristic information, and historical statistics of mobility events;

[0079] The mobility mode capability information includes the mobility modes that the terminal can support; the service characteristic information includes at least one of the terminal's periodic service indications, the duration of a single service communication, and the service cycle; and the historical statistics of mobility events include historical statistics of mobility events such as handovers and location updates that occurred during specific time periods and / or at specific locations.

[0080] Step 203: The CPF entity determines the terminal's first mobility mode based on the terminal's mobility mode information.

[0081] Optionally, the CPF entity determines the terminal's first mobility mode in the following way:

[0082] First, the CPF entity determines the mobility modes that the terminal can support based on the terminal's mobility mode capability information.

[0083] Then, the CPF entity selects at least one mobility mode from the mobility modes that the terminal can support based on the terminal's historical mobility event statistics; or, the CPF entity selects at least one mobility mode from the mobility modes that the terminal can support based on the terminal's service characteristic information; or, the CPF entity selects at least one mobility mode from the mobility modes that the terminal can support based on both the terminal's service characteristic information and historical mobility event statistics.

[0084] The CPF entity determines the terminal’s first mobility management configuration information based on at least one selected mobility mode.

[0085] Optionally, after selecting at least one mobility mode from the mobility modes supported by the terminal, the CPF entity determines the state parameters corresponding to the selected at least one mobility mode.

[0086] Step 204: The CPF entity sends the first mobility mode to the RAN node;

[0087] The first mobility mode is used by the RAN node to determine the second mobility mode of the terminal; the RAN node receives the first mobility mode of the terminal sent by the CPF entity;

[0088] Both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0089] Step 205: After receiving the first mobility mode of the terminal sent by the CPF entity, the RAN node determines the second mobility mode of the terminal based on the first mobility mode.

[0090] Step 206: The RAN node sends the determined second mobility mode to the terminal, and the terminal receives the second mobility mode sent by the RAN node.

[0091] Optionally, the RAN node may also send a second mobility mode to the CPF entity so that the CPF entity knows the mobility mode ultimately used by the terminal.

[0092] Step 207: The terminal determines the configuration information for terminal mobility management based on at least one mobility mode included in the second mobility mode.

[0093] The connection state described in this application embodiment includes at least one of signaling connection state and session connection state.

[0094] Specifically, in step 203, before the CPF entity determines the first mobility mode of the terminal, the CPF entity may pre-configure a set of mobility modes that the CPF entity can support. The set of mobility modes includes at least one mobility mode and a mode index value corresponding to each mobility mode. Optionally, the set of mobility modes also includes transition conditions between the various mobility modes. For ease of description, the set of mobility modes configured by the CPF entity may be referred to here as the first mobility mode set.

[0095] In this application embodiment, one possible implementation of the mobility mode set is in the form of one or more mobility mode lists, as shown in Tables 1-3. Each mobility mode list includes a mode index value such as: sub-mode 1, sub-mode 2, sub-mode 3, etc.

[0096] The mobility modes, such as the first mobility mode and the second mobility mode, described in the embodiments of this application include at least one sub-mode as shown in Tables 1, 2 and 3.

[0097] It should be noted that if the state parameters are not included in the state mode list, the CPF entity needs to further determine the state parameters corresponding to the first mobility mode and inform the RAN node.

[0098] Table 1

[0099]

[0100] Table 2

[0101]

[0102] Table 3

[0103]

[0104] Optionally, the CPF entity determines the terminal's first mobility mode in the following way:

[0105] First, the CPF entity determines at least one mobility mode that the terminal can support in the first mobility mode set based on the terminal's mobility mode capability information.

[0106] Then, the CPF entity selects a first mobility mode corresponding to the terminal's historical mobility event statistics from at least one mobility mode that the terminal can support, based on the terminal's historical mobility event statistics; or,

[0107] The CPF entity selects the first mobility mode corresponding to the service characteristic information of the terminal from at least one mobility mode supported by the terminal, based on the service characteristic information of the terminal; or

[0108] The CPF entity selects the first mobility mode corresponding to the service feature information and the historical mobility event statistics of the terminal from at least one mobility mode that the terminal can support, based on the service feature information and the historical mobility event statistics of the terminal.

[0109] The CPF entity will send the determined first mobility mode to the RAN node, which may be done, but is not limited to, through the following methods:

[0110] The CPF entity sends the mode index value corresponding to the first mobility mode to the RAN node; or, the CPF entity sends the configuration information of the connection status of the terminals included in the first mobility mode to the RAN node.

[0111] Before determining the second mobility mode of the terminal based on the first mobility mode, the RAN node pre-obtains the set of mobility modes that the RAN node can support. For ease of description, the set of mobility modes that the RAN node can support can be referred to as the second mobility mode set.

[0112] The RAN node determines whether the first mobility mode is included in the second mobility mode set; if so, the RAN node determines the first mobility mode as the second mobility mode; otherwise, the RAN node selects the default mobility mode from the mobility mode set according to the default configuration as the second mobility mode.

[0113] That is, the RAN node determines the terminal's second mobility mode based on the first mobility mode and the local configuration policy. For example, the first mobility mode includes states such as RRC_IDLE and RRC_INACTIVE, but the RAN node does not support the RRC_INACTIVE connected state, so the RAN node selects the default RRC_IDLE and RRC_CONNECTED states.

[0114] The following describes in more detail the above-mentioned solutions provided in the embodiments of this application, based on two application scenarios: a CPF entity is an entity with both MM and SM functions, and a CPF entity includes entities with both MM and SM functions.

[0115] Application Scenario 1: The CPF entity is a functional entity that has both MM and SM functions.

[0116] In this scenario, a CPF entity simultaneously possesses both MM and SM functionalities. The method steps are as follows: Figure 3 As shown.

[0117] Step 301: The terminal sends an attach request message to the CPF entity;

[0118] The attach request message carries information about the terminal's mobility mode capabilities, which indicates which mobility modes the terminal can support.

[0119] Step 302: The CPF entity retrieves the terminal's subscription information from the user subscription database.

[0120] Alternatively, the CPF entity can obtain the terminal's subscription information from other CPF entities previously attached to the terminal. This step is performed under the premise that the CPF entity is unaware of the terminal's subscription information. Of course, if the CPF entity is aware of the terminal's subscription information, step 302 can be omitted.

[0121] The terminal's subscription information includes some mobility mode-related information, namely, selection assistance information related to the terminal's mobility mode, including some service characteristic information of the terminal, such as service parameters such as periodic service indication, communication duration, communication cycle, fixed terminal indication, and connection status parameters such as periodic location update timer.

[0122] Step 303: The CPF entity obtains the historical statistics of the terminal's mobility events and determines the terminal's first mobility mode based on the historical statistics of the terminal's mobility events and the terminal's mobility mode capabilities.

[0123] The historical statistics of terminal mobility events include historical statistics of handovers, location updates, and other mobility events that occurred within a specific time period and / or location. For example, the number of handovers, location updates, and other events that occurred within a certain time period. By statistically analyzing these mobility events, the mobility characteristics of the terminal can be determined, such as whether it is a fixed terminal, a low-mobility terminal, or a high-mobility terminal. The CPF entity can set classification rules for the aforementioned mobility characteristics of the terminal, which are not limited in this application.

[0124] CPF entities pre-store a set of mobility patterns. One possible implementation of the mobility pattern set is as a list of one or more mobility patterns, as shown in Tables 1-3. The pattern index value in each mobility pattern list includes: sub-pattern 1, sub-pattern 2, sub-pattern 3, etc.

[0125] The CPF entity selects a subset of mobility modes that the terminal can support from the pre-stored mobility mode set in the CPF based on the terminal's mobility mode capabilities, and selects a first mobility mode suitable for the terminal from the subset based on the terminal's historical mobility event statistics.

[0126] For example, by statistically analyzing the number of location updates and handovers occurring on the terminal for each day and time period within a month, we can see that the terminal experiences very frequent location updates and handovers between 7:00 and 9:00 AM each day, indicating frequent location changes, possibly because the user is commuting to work during this period. Between 9:00 and 9:00 PM, fewer location updates and handovers occur, suggesting the user may be in the office area or surrounding region during this time. Between 9:00 and 7:00 AM, almost no location updates or handovers occur, indicating minimal location changes, possibly because the user is at home during this time. Therefore, the CPF entity can determine that the terminal's primary mobility mode between 7:00 and 9:00 AM is sub-mode 1 in Table 1 and sub-mode 1 in Table 2, meaning the terminal is in NCM_CONNECTED / RRC_CONNECTED mode when data transmission is active, and should switch to NCM_IDLE / RRC_IDLE mode upon completion of data transmission. Furthermore, the CPF entity can allocate a larger location area to the terminal, thereby avoiding the signaling overhead caused by the terminal frequently moving out of the location area to initiate location updates; the CPF entity can determine that the terminal's first mobility mode during the time period of 9:00-21:00 is mode 3 in Table 1 and mode 3 in Table 2, that is, the terminal's NAS signaling connection always remains in the NCM_CONNECTED state, the RRC signaling connection is RRC_CONNECTED when there is data transmission, and RRA_PCH when there is no data transmission, and can set the RAN Routing Area (RRA) parameter to multiple cells corresponding to the terminal's office area and surrounding area, that is, paging is only performed within the RRA range, avoiding the paging signaling overhead caused by an excessively large paging range;

[0127] The CPF entity can determine that the terminal's first mobility mode during the 21:00-7:00 time period is still mode 3 in Table 1 and mode 3 in Table 2, but sets the RRA parameter to the cell where the terminal is currently located, further narrowing the paging range to a specific cell, and can further set a longer periodic location update timer.

[0128] The specific time period in the above example can also be replaced with a specific location, that is, the mobility pattern can be determined based on the historical statistics of the terminal's mobility events in a specific location (such as home or office).

[0129] The connection state includes at least one of the signaling connection state and the service connection state. When selecting the first mobility mode for the terminal, only the signaling connection state suitable for the terminal can be considered. If the terminal needs a service connection later, the service characteristic parameters of the terminal will be considered to determine the session connection state mode.

[0130] Step 304: The CPF entity sends the selected first mobility mode suitable for the terminal to the RAN node.

[0131] Specifically, the mode index value corresponding to the terminal's first mobility mode is sent to the RAN node, or the parameters included in the terminal's first mobility mode are sent directly. Simultaneously, some mobility mode-related parameter configurations obtained from the terminal's subscription information are sent to the RAN node, such as the terminal's periodic location update timer.

[0132] Step 305: The RAN node determines the final second mobility mode to be used for the terminal based on the terminal's first mobility mode and its local configuration policy.

[0133] If the RAN node cannot support the first mobility mode, the RAN node will select the default mobility mode as the second mobility mode ultimately used by the terminal.

[0134] If the RAN node can support the first mobility mode, then the RAN node will determine the first mobility mode as the second mobility mode ultimately used by the terminal.

[0135] Step 306: The RAN node sends the second mobility mode to be used by the terminal to both the terminal and the CPF entity.

[0136] Step 307: The terminal sends a connection establishment request message to the CPF entity.

[0137] Step 308: The CPF entity determines the third mobility mode of the terminal based on the terminal's service characteristic information and mobility mode capability information obtained in step 302.

[0138] Specifically, similar to step 303, the CPF entity selects a subset of mobility modes that the terminal can support from the CPF's pre-stored mobility mode set based on the terminal's mobility mode capabilities, and selects a suitable third mobility mode for the terminal from the subset based on the terminal's service characteristic information.

[0139] For example, if the terminal's service characteristics are: periodic service, with a communication cycle of sending and receiving data every 30 minutes, then the CPF entity can determine the terminal's third mobility mode as Mode 3 in Table 3. The transition conditions are: after the session is established, the state is SESSION CONTEXT ACTIVE; after data transmission is complete, it transitions to SESSION CONTEXT SUSPEND; when data is sent, it transitions back to SESSION CONTEXT ACTIVE; and when the session is released, it transitions to SESSION CONTEXT INACTIVE. When the terminal's service characteristics change, for example, to: periodic service, with a communication cycle of sending and receiving data every day, then the CPF can determine the terminal's session mobility mode as Mode 1 in Table 3. The transition conditions are: after the session is established, the state is SESSION CONTEXT ACTIVE; after data transmission is complete, it transitions to SESSION CONTEXT INACTIVE; and when data is sent, the session connection is re-established, transitioning back to SESSION CONTEXT ACTIVE.

[0140] When selecting a third mobility mode for a terminal, you can only consider the service mobility mode that is suitable for the terminal.

[0141] Step 309: The CPF entity sends the selected third mobility mode suitable for the terminal to the RAN node.

[0142] Specifically, the mode index value corresponding to the terminal's third mobility mode is sent to the RAN node, or the parameters included in the terminal's third mobility mode are sent directly. Simultaneously, some mobility mode-related parameter configurations obtained from the terminal's subscription information are sent to the RAN node, such as the terminal's periodic location update timer.

[0143] Step 310: The RAN node determines the final fourth mobility mode to be used for the terminal based on the terminal's third mobility mode and its local configuration policy.

[0144] Step 311: The RAN node sends the fourth mobility mode to be used by the terminal to both the terminal and the CPF entity.

[0145] It should be noted that if the terminal only has the attach process and does not need the connection establishment process, then this solution only needs to execute steps 301 to 306. When the terminal needs to perform business later, steps 307 to 311 will be executed.

[0146] Application Scenario 2: CPF entities include entities with MM functionality or entities with SM functionality.

[0147] In this scenario, the functionality of the CPF entity is implemented by two separate functional entities: the entity with MM functionality is called the MM entity, and the entity with SM functionality is called the SM entity. The method steps are as follows: Figure 4 As shown.

[0148] Step 401: The terminal sends an attach request message to the MM entity.

[0149] The attach request message carries information about the terminal's mobility mode capabilities, which indicates which mobility modes the terminal can support.

[0150] Step 402: The MM entity retrieves the terminal's subscription information from the user subscription database.

[0151] The MM entity can also obtain the terminal's subscription information from other MM entities previously attached to the terminal. This step is performed on the premise that the MM entity is unaware of the terminal's subscription information. Of course, if the MM entity is aware of the terminal's subscription information, step 402 is omitted.

[0152] Step 403: The MM entity obtains the historical statistics of the terminal's mobility events, and determines the terminal's first mobility mode based on the historical statistics of the terminal's mobility events and the terminal's mobility mode capabilities.

[0153] Step 404: The MM entity sends the selected first mobility mode suitable for the terminal to the RAN node.

[0154] The steps 401 to 404 above are the same as the steps 301 to 304 above, except that the executing entity is changed from the CPF entity to the MM entity, and will not be repeated here.

[0155] Step 405: The RAN node determines the final second mobility mode to be used for the terminal based on the terminal's first mobility mode and its local configuration policy.

[0156] Step 406: The RAN node sends the second mobility mode to be used by the terminal to both the terminal and the MM entity.

[0157] Step 407: The terminal sends a connection establishment request message to the SM entity.

[0158] The connection establishment request message carries information about the terminal's mobility mode capabilities, which indicates which mobility modes the terminal can support.

[0159] Step 408: The SM entity retrieves the terminal's subscription information from the user subscription database.

[0160] Alternatively, the SM entity can obtain the terminal's subscription information from other SM entities previously attached to the terminal. This step is performed under the premise that the SM entity is unaware of the terminal's subscription information. Of course, if the SM entity is aware of the terminal's subscription information, step 408 is omitted. The terminal's subscription information includes some parameters related to the terminal's mobility mode, including some service characteristic information of the terminal, such as service parameters such as periodic service indication, communication duration, communication cycle, fixed terminal indication, and periodic location update timer, as well as mobility mode parameters such as periodic location update timer.

[0161] Step 409: The SM entity determines the third mobility mode of the terminal based on the acquired service characteristic information of the terminal and the mobility mode capability information of the terminal.

[0162] Step 410: The SM entity sends the selected third mobility mode suitable for the terminal to the RAN node.

[0163] Step 411: The RAN node determines the final fourth mobility mode to be used for the terminal based on the terminal's third mobility mode and its local configuration policy.

[0164] Step 412: The RAN node sends the fourth mobility mode to be used by the terminal to both the terminal and the SM entity.

[0165] It should be noted that if the terminal only has the attach process and does not need the connection establishment process, then this solution only needs to execute steps 401 to 406. When the terminal needs to perform business later, steps 407 to 412 will be executed.

[0166] This application also provides another implementation of the terminal mobility mode management method, in which the RAN node determines the terminal's mobility mode based on the terminal's application scenario. The specific process is as follows: Figure 5 As shown.

[0167] Step 501: The CPF entity sends the terminal's mobility mode information to the RAN node, and the RAN node receives the terminal's mobility mode information sent by the CPF entity.

[0168] Mobility pattern-related information includes one or any combination of the following: mobility pattern capability information, service characteristic information, and historical statistics of mobility events;

[0169] The mobility mode capability information includes the mobility modes that the terminal can support; the service characteristic information includes at least one of the terminal's periodic service indication, single service communication duration, and service cycle; the mobility event historical statistics information includes the terminal switching or location updating during a specific time period, or the mobility event historical statistics information includes the switching or location updating during a specific location, or the mobility event historical statistics information includes the movement speed type that occurred during a specific time period or at a specific location.

[0170] Step 502: The RAN node determines the terminal's mobility mode based on the received mobility mode information of the terminal.

[0171] Mobility mode includes at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area mobility management configuration information.

[0172] Specifically, the RAN node determines the mobility modes supported by the terminal based on the terminal's mobility mode capability information; then, the RAN node selects at least one mobility mode from the mobility modes supported by the terminal based on the terminal's historical mobility event statistics; or, the RAN node selects at least one mobility mode from the mobility modes supported by the terminal based on the terminal's service characteristic information; or, the RAN node selects at least one mobility mode from the mobility modes supported by the terminal based on both the terminal's service characteristic information and the historical mobility event statistics; the RAN node determines the terminal's mobility mode based on the selected at least one mobility mode.

[0173] Specifically, before determining the terminal's mobility mode based on the terminal's mobility mode information, the RAN node pre-configures a set of mobility modes that the RAN node can support. The set of mobility modes includes at least one mobility mode and the mode index value corresponding to each mobility mode.

[0174] The RAN node determines at least one mobility mode that the terminal can support from the mobility mode set based on the terminal's mobility mode capability information.

[0175] The RAN node selects a mobility mode corresponding to the terminal's historical mobility event statistics from at least one mobility mode that the terminal can support, based on the terminal's historical mobility event statistics; or, the RAN node selects a mobility mode corresponding to the terminal's service characteristics from at least one mobility mode that the terminal can support, based on the terminal's service characteristic information.

[0176] Step 503: The RAN node sends the determined mobility mode to the terminal.

[0177] Specifically, the RAN node sends the mode index value corresponding to the mobility mode to the terminal; or, the RAN node sends the configuration information of the terminal's mobility mode included in the mobility mode to the terminal.

[0178] Based on the same inventive concept, see [reference] Figure 6 As shown, this application embodiment also provides a terminal mobility mode management device 600 for performing... Figure 2 The terminal mobility mode management method shown is described. The terminal mobility mode management device 600 includes: an acquisition unit 601, a determination unit 602, and a transmission unit 603. Wherein:

[0179] The acquisition unit 601 is used to acquire information related to the terminal's mobility mode;

[0180] The determining unit 602 is used to determine the first mobility mode of the terminal based on the mobility mode-related information of the terminal acquired by the obtaining unit 601.

[0181] The transmitting unit 603 is used to transmit the first mobility mode determined by the determining unit 602 to the radio access network (RAN) node. The first mobility mode is used by the RAN node to determine the second mobility mode of the terminal.

[0182] Optionally, mobility pattern-related information includes at least one of the following: mobility pattern capability information, service characteristic information, and historical statistics of mobility events;

[0183] The mobility mode capability information includes the mobility modes that the terminal can support; the service characteristic information includes at least one of the terminal's periodic service indication, single service communication duration, and service cycle; the mobility event historical statistics information includes the terminal switching or location updating during a specific time period, or the mobility event historical statistics information includes the switching or location updating during a specific location, or the mobility event historical statistics information includes the movement speed type that occurred during a specific time period or at a specific location.

[0184] Optionally, the determining unit 602 is used for:

[0185] Based on the terminal's mobility mode capability information, determine the mobility modes that the terminal can support;

[0186] Based on the terminal's historical mobility event statistics, at least one mobility mode is selected from the mobility modes supported by the terminal; or, based on the terminal's service characteristic information, at least one mobility mode is selected from the mobility modes supported by the terminal; or, based on both the terminal's service characteristic information and historical mobility event statistics, at least one mobility mode is selected from the mobility modes supported by the terminal; and,

[0187] The first mobility mode of the terminal is determined based on at least one selected mobility mode.

[0188] Optionally, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0189] Optionally, the mobility mode includes at least one of signaling mobility mode and session mobility mode;

[0190] Signaling mobility modes include Non-Access Stratum (NAS) signaling mobility mode or Radio Resource Control (RRC) signaling mobility mode.

[0191] Based on the same inventive concept, see [reference] Figure 7 As shown in the illustration, this application also provides a terminal mobility mode management device 700 for performing... Figure 2 The terminal mobility mode management method shown is described. The terminal mobility mode management device 700 includes a receiving unit 701, a determining unit 702, and a sending unit 703. Wherein:

[0192] The receiving unit 701 is used to receive the first mobility mode of the terminal transmitted by the control plane function (CPF) entity;

[0193] The determining unit 702 is used to determine the second mobility mode of the terminal based on the first mobility mode received by the receiving unit 701.

[0194] The sending unit 703 is used to send the second mobility mode determined by the determining unit 702 to the terminal.

[0195] Optionally, the determining unit 702 is used for:

[0196] Pre-acquire the mobility modes that the device can support;

[0197] If the device can support the mobility management configuration information included in the first mobility mode, then the first mobility mode is determined as the second mobility mode; or, if the device does not support the mobility management configuration information included in the first mobility mode, then the default mobility mode is selected as the second mobility mode.

[0198] Optionally, both the first mobility mode and the second mobility mode include at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0199] Optionally, the connection state includes at least one of signaling connection state and session connection state;

[0200] Signaling connection status includes Non-Access Stratum (NAS) signaling connection status or Radio Resource Control (RRC) signaling connection status.

[0201] Based on the same inventive concept, see [reference] Figure 8 As shown, this application embodiment also provides another terminal mobility mode management device 800, used to perform... Figure 5 The terminal mobility mode management method shown is described. The terminal mobility mode management device 800 includes: a receiving unit 801, a determining unit 802, and a sending unit 803. Wherein:

[0202] The receiving unit 801 is used to receive terminal mobility mode related information sent by the control plane function (CPF) entity.

[0203] The determining unit 802 is used to determine the mobility mode of the terminal based on the mobility mode related information received by the receiving unit 801.

[0204] The sending unit 803 is used to send the mobility mode determined by the determining unit 802 to the terminal.

[0205] Optionally, mobility pattern-related information includes at least one of the following: mobility pattern capability information, service characteristic information, and historical statistics of mobility events;

[0206] The mobility mode capability information includes the mobility modes that the terminal can support; the service characteristic information includes at least one of the terminal's periodic service indication, single service communication duration, and service cycle; the mobility event historical statistics information includes the terminal switching or location updating during a specific time period, or the mobility event historical statistics information includes the switching or location updating during a specific location, or the mobility event historical statistics information includes the movement speed type that occurred during a specific time period or at a specific location.

[0207] Optionally, the determining unit 802 is used for:

[0208] Based on the terminal's mobility mode capability information, determine the mobility modes supported by the terminal.

[0209] Based on the terminal's historical mobility event statistics, select at least one mobility mode from the mobility modes that the terminal can support; or, based on the terminal's service characteristic information, select at least one mobility mode from the mobility modes that the terminal can support; or, based on the terminal's service characteristic information and historical mobility event statistics, select at least one mobility mode from the mobility modes that the terminal can support.

[0210] The mobility mode of the terminal is determined based on at least one selected mobility mode.

[0211] Optionally, the mobility mode includes at least one of the following mobility management configuration information: connection status, location area list, location update timer, and paging area.

[0212] Optionally, the connection state includes at least one of signaling connection state and session connection state;

[0213] Signaling connection status includes Non-Access Stratum (NAS) signaling connection status or Radio Resource Control (RRC) signaling connection status.

[0214] Based on the same inventive concept, see [reference] Figure 9 As shown in the embodiment of this application, a terminal 900 is also provided for executing... Figure 2 The terminal 900 is shown as a method for managing terminal mobility modes. The terminal 900 includes a transmitting unit 901, a receiving unit 902, and a determining unit 903.

[0215] The sending unit 901 is used to send mobility mode related information of the terminal to the control plane function CPF entity, wherein the mobility mode related information is used to determine the first mobility mode of the terminal.

[0216] The receiving unit 902 is used to receive the second mobility mode transmitted by the RAN node;

[0217] The determining unit 903 is configured to determine the mobility mode adopted by the terminal based on at least one mobility mode included in the second mobility mode.

[0218] Optionally, the mobility mode-related information includes at least one of the following: mobility mode capability information, service characteristic information, and historical statistics of mobility events;

[0219] The mobility mode capability information includes the mobility modes that the terminal can support; the service characteristic information includes at least one of the terminal's periodic service indication, single service communication duration, and service cycle; the mobility event historical statistics information includes the terminal switching or location updating during a specific time period; or the mobility event historical statistics information includes the switching or location updating during a specific location; or the mobility event historical statistics information includes the movement speed type occurring during a specific time period or at a specific location.

[0220] Based on the same inventive concept, see [reference] Figure 10 As shown in the illustration, this application also provides a CPF entity 1000, including a transceiver 1001, a processor 1002, and a memory 1003. The memory 1003 stores a set of programs, and the processor 1002 calls the programs stored in the memory 1003 to execute them. Figure 2 The terminal mobility mode management method shown.

[0221] The processor 1002 can be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.

[0222] The processor 1002 may further include a hardware chip. This hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0223] The memory 1003 may include volatile memory, such as random-access memory (RAM); the memory 1003 may also include non-volatile memory, such as flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 1003 may also include a combination of the above types of memory.

[0224] Based on the same inventive concept, see [reference] Figure 11 As shown in the illustration, this application also provides another RAN node 1100, including: a transceiver 1101, a processor 1102, and a memory 1103. The memory 1103 is used to store a set of programs, and the processor 1102 is used to call the programs stored in the memory 1103 to execute them. Figure 2 The terminal mobility mode management method shown.

[0225] The processor 1102 can be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.

[0226] The processor 1102 may further include a hardware chip. This hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0227] The memory 1103 may include volatile memory, such as random-access memory (RAM); the memory 1103 may also include non-volatile memory, such as flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 1103 may also include a combination of the above types of memory.

[0228] Based on the same inventive concept, see [reference] Figure 12 As shown in the illustration, this application also provides another RAN node 1200, including: a transceiver 1201, a processor 1202, and a memory 1203. The memory 1203 stores a set of programs, and the processor 1202 calls the programs stored in the memory 1203 for execution. Figure 5 The terminal mobility mode management method shown.

[0229] Processor 1202 can be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.

[0230] The processor 1202 may further include a hardware chip. This hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0231] The memory 1203 may include volatile memory, such as random-access memory (RAM); the memory 1203 may also include non-volatile memory, such as flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 1203 may also include a combination of the above types of memory.

[0232] Based on the same inventive concept, see [reference] Figure 13 As shown in the illustration, this application also provides another terminal 1300, including: a transceiver 1301, a processor 1302, and a memory 1303. The memory 1303 is used to store a set of programs, and the processor 1302 is used to call the programs stored in the memory 1303 to execute them. Figure 2 The terminal mobility mode management method shown.

[0233] The processor 1302 can be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.

[0234] The processor 1302 may further include hardware chips. These hardware chips may be application-specific integrated circuits (ASICs), programmable logic devices (PLDs), or combinations thereof. The PLDs may be complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), generic array logic (GALs), or any combination thereof.

[0235] The memory 1303 may include volatile memory, such as random-access memory (RAM); the memory 1303 may also include non-volatile memory, such as flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 1303 may also include a combination of the above types of memory.

[0236] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this 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.) containing computer-usable program code.

[0237] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0238] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0239] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0240] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0241] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A management system for terminal mobility modes, characterized in that, include: Control plane functional CPF entities and radio access network RAN ​​nodes; The CPF entity is used to send a first mobility mode of the terminal to the RAN node. The first mobility mode includes at least one of Radio Resource Control (RRC) signaling connection status, a first location area list, or a first location update timer. The RAN node is configured to receive the first mobility mode and determine the second mobility mode of the terminal based on the first mobility mode and a local configuration policy. The second mobility mode includes RRC-INACTIVE and further includes at least one of a second location area list and a second location update timer. The RAN node is also used to provide the second mobility mode to the terminal.

2. The system as described in claim 1, characterized in that, The second mobility mode also includes a paging area.

3. A terminal mobility mode management device, characterized in that, include: Memory and processor; The memory is used to store computer program instructions; The processor is configured to execute the computer program instructions to implement the following method: The terminal receives a first mobility mode from a control plane function (CPF) entity, the first mobility mode including at least one of Radio Resource Control (RRC) signaling connection status, a first location area list, or a first location update timer. Based on the first mobility mode and the local configuration policy, a second mobility mode of the terminal is determined. The second mobility mode includes RRC-INACTIVE and also includes at least one of a second location area list and a second location update timer. The second mobility mode is sent to the terminal.

4. The apparatus as described in claim 3, characterized in that, The second mobility mode also includes a paging area.

5. A computer-readable storage medium, characterized in that, Used to store computer program instructions, which, when executed, implement the following method: The terminal receives a first mobility mode from a control plane function (CPF) entity, the first mobility mode including at least one of Radio Resource Control (RRC) signaling connection status, a first location area list, or a first location update timer. Based on the first mobility mode and the local configuration policy, a second mobility mode of the terminal is determined. The second mobility mode includes RRC-INACTIVE and also includes at least one of a second location area list and a second location update timer. The second mobility mode is sent to the terminal.

6. A computer program product, characterized in that, Includes computer program instructions, which, when executed, implement the following method: The terminal receives a first mobility mode from a control plane function (CPF) entity, the first mobility mode including at least one of Radio Resource Control (RRC) signaling connection status, a first location area list, or a first location update timer. Based on the first mobility mode and the local configuration policy, a second mobility mode of the terminal is determined. The second mobility mode includes RRC-INACTIVE and also includes at least one of a second location area list and a second location update timer. The second mobility mode is sent to the terminal.

Images