WO2018035726A1 - 一种终端移动性模式的管理方法及装置 - Google Patents

一种终端移动性模式的管理方法及装置 Download PDF

Info

Publication number
WO2018035726A1
WO2018035726A1 PCT/CN2016/096443 CN2016096443W WO2018035726A1 WO 2018035726 A1 WO2018035726 A1 WO 2018035726A1 CN 2016096443 W CN2016096443 W CN 2016096443W WO 2018035726 A1 WO2018035726 A1 WO 2018035726A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
mobility
mobility mode
mode
information
Prior art date
Application number
PCT/CN2016/096443
Other languages
English (en)
French (fr)
Inventor
黄正磊
杨艳梅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202110446352.XA priority Critical patent/CN113225754A/zh
Priority to JP2019510771A priority patent/JP7026675B2/ja
Priority to BR112019002990A priority patent/BR112019002990A2/pt
Priority to CN201680085471.4A priority patent/CN109076362B/zh
Priority to EP16913750.2A priority patent/EP3496445B1/en
Priority to KR1020197007523A priority patent/KR102290689B1/ko
Priority to PCT/CN2016/096443 priority patent/WO2018035726A1/zh
Publication of WO2018035726A1 publication Critical patent/WO2018035726A1/zh
Priority to US16/283,324 priority patent/US11533606B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method and an apparatus for managing a terminal mobility mode.
  • the connection status of the terminal may include a signaling connection status and a session connection status.
  • the signaling connection status includes: Non-Access Stratum (NAS) signaling connection management (English: Connection Management, abbreviation: CM) status, and radio resource control (English: Radio Resource Control, abbreviation: RRC) signaling Connection management status.
  • NAS Non-Access Stratum
  • CM Connection Management
  • RRC Radio Resource Control
  • the NAS signaling connection management status may be represented by NCM, and is used to indicate the establishment status of the NAS signaling connection between the terminal and the core network, for example, NCM_IDLE, NCM_CONNECTED, and the like.
  • NCM_IDLE indicates that the terminal and the core network have not established a signaling connection
  • NCM_CONNECTED indicates that the terminal and the core network have established a signaling connection through one RAN node.
  • the RRC signaling connection management state is used to indicate the establishment state of the RRC signaling connection between the terminal and the radio access network. For example, states such as RRC_IDLE, RRC_CONNECTED, RRC_INACTIVE, and RRA_PCH.
  • RRC_IDLE indicates that no RRC connection is 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 the RAN node still stores information such as the RRC context and bearer context of the terminal after the data packet is transmitted;
  • the session connection management state is used to indicate the activation state of the session context between the terminal and the network, including states such as SESSION CONTEXT ACTIVE, SESSION CONTEXT INACTIVE, and SESSION CONTEXT SUSPEND.
  • SESSION CONTEXT ACTIVE indicates that the session context is active, that is, the session context has been saved
  • SESSION CONTEXT INACTIVE indicates that the session context is deactivated, that is, the session context has been deleted
  • SESSION CONTEXT SUSPEND indicates that the session context is saved, but no data is sent or received.
  • different signaling connection states indicate the reachability level of the terminal location, that is, the core network can determine the accuracy of the terminal location.
  • the core network can determine the accuracy of the terminal location as a range of location areas that the core network pre-allocates to the terminal, and the location area includes multiple radio access networks.
  • RAN Radio Access Network
  • the core network needs to page terminals with multiple RAN nodes in the location area of the terminal to send data to the terminal, which will generate paging overhead.
  • the core network can directly send data to the RAN node where the terminal is currently located, without paging, which can reduce the paging overhead.
  • the terminal keeps NCM_CONNECTED, the terminal is connected due to the location.
  • it is necessary to update the location of the terminal to the core network, and this will result in location update overhead. Therefore, it is necessary to achieve a balanced state between the above paging overhead and the location update overhead in order to minimize the total overhead.
  • connection state and the state transition condition of the terminal are pre-configured in the terminal and the network side device, and the signaling connection state and the state transition condition of the terminal pre-configured in the terminal and the core network are: the terminal is transmitting or receiving data.
  • the signaling connection status with the core network needs to be NCM_CONNECTED; when the data is sent and received, the signaling is released, and the signaling connection status is changed to NCM_IDLE.
  • NCM_CONNECTED NCM_CONNECTED
  • the activation state of the session context of a certain service between the terminal and the network For the session connection state, the activation state of the session context of a certain service between the terminal and the network.
  • the connection state and the state transition condition of the terminal are pre-configured in the terminal and the network side device, and the session connection state and the state transition condition of the terminal preconfigured by the terminal and the RAN node are: when the terminal has service data.
  • the session connection status is SESSION CONTEXT ACTIVE.
  • the session connection status is changed to SESSION. CONTEXT INACTIVE, and the RAN node deletes the session context.
  • connection state and the state transition condition of the terminal are pre-configured in the terminal and the network side device, and the fixed configuration cannot be flexibly changed according to the actual application scenario of the terminal, thereby reducing Network performance.
  • the present application provides a method and an apparatus for managing a mobility mode of a terminal, where the mobility mode includes mobility management configuration information, such as a connection status, a location area list, a location update timer, a paging area, and the like, for flexibility. Optimize network performance by configuring and managing terminal mobility management configuration information.
  • mobility management configuration information such as a connection status, a location area list, a location update timer, a paging area, and the like.
  • a method for managing a terminal mobility mode is provided.
  • the method is implemented by: a control plane function CPF entity acquiring mobility mode related information of a terminal, and determining, according to the mobility mode related information of the terminal, a first mobility mode of the terminal, the CPF entity transmitting the first mobility mode to a radio access network RAN node, so that the RAN node determines a second mobility of the terminal according to the first mobility mode Sexual mode.
  • the CPF entity can select a mobility mode suitable for the terminal according to the actual application scenario of the terminal, and determine the mobility mode finally configured for the terminal through the RAN node, and notify the terminal, breaking the fixed mobility mode configuration of the terminal, and implementing The mobility mode of the terminal is flexibly configured and managed according to the actual application scenario of the terminal, thereby optimizing network performance.
  • the CPF entity sends the first mobility mode of the terminal directly to the terminal.
  • the mobility mode related information includes at least one of the following: mobility mode capability information, service feature information, and mobility event history statistics;
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service cycle of the terminal, where the mobility
  • the event history statistical information includes that the terminal performs switching or location update in a specific time period, or the mobility event history statistical information includes switching or location update at a specific location, or the mobility event historical statistical information is included in a specific time period. Or the type of movement speed that occurs at a particular location.
  • the actual application scenario of the terminal can be fully utilized by the historical data of the terminal, so that the CPF entity and the RAN node can accurately determine the mobility mode suitable for the actual application scenario of the terminal.
  • the CPF entity determines the first mobility mode of the terminal according to the mobility mode related information of the terminal, where the CPF entity is configured according to the mobility of the terminal. a mode of capability information, determining a mobility mode that the terminal can support; the CPF entity selecting a mobility mode in a mobility mode that the terminal can support according to the mobility event history statistics information of the terminal; or The CPF entity selects a mobility mode in a mobility mode that the terminal can support according to the service feature information of the terminal; or the CPF entity according to the service feature information of the terminal and the The mobility event history statistical information selects a mobility mode in a mobility mode that the terminal can support.
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a connection state, a location area list, a location update timer, and a paging region.
  • the connection state includes at least one of a signaling connection state and a session connection state;
  • the signaling connection state includes a non-access stratum NAS signaling connection state or a radio resource control RRC signaling connection. status.
  • the RAN node also sends the determined second mobility mode to the CPF entity. This enables the terminal, the RAN node, and the CPF entity to learn the mobility mode used by the terminal, so that the network matching is consistent.
  • a second aspect provides a method for managing a terminal mobility mode, including: a radio access network RAN node receiving a first mobility mode of a terminal sent by a control plane function CPF entity; The node determines a second mobility mode of the terminal according to the first mobility mode; the RAN node sends the determined second mobility mode to the terminal.
  • the RAN node can configure the mobility mode for the terminal according to the mobility mode that is matched by the CPF entity to the actual application scenario of the terminal, and notify the terminal, and break the fixed mobility mode configuration of the terminal, thereby realizing flexible according to the actual application scenario of the terminal. Optimize network performance by configuring and managing the mobility mode of the endpoint.
  • the determining, by the RAN node, the second mobility mode of the terminal according to the first mobility mode may be implemented by: the RAN node acquiring, in advance, a mobile that the RAN node can support a mode of determining; if the RAN node is capable of supporting mobility management configuration information included in the first mobility mode, 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, the RAN node selects a default mobility mode as the second mobility mode.
  • the self-configuration of the RAN node is fully considered to ensure normal operation between the mobility mode of the RAN node and the terminal.
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a connection state, a location area list, a location update timer, and a paging region.
  • the connection state includes at least one of a signaling connection state and a session connection state;
  • the signaling connection state includes a non-access stratum NAS signaling connection state or a radio resource control RRC signaling connection. status.
  • the RAN node also sends the determined second mobility mode to the CPF entity. This enables the terminal, the RAN node, and the CPF entity to learn the mobility mode used by the terminal, so that the network matching is consistent.
  • a method for managing a mobility mode of a terminal comprising: receiving, by a radio access network, a RAN node, mobility mode related information of a terminal sent by a CPF entity, where the RAN node is related according to the mobility mode Information determining a mobility mode of the terminal; the RAN node transmitting the mobility mode to the terminal.
  • the RAN node can be based on the terminal
  • the actual application scenario is to select a mobility mode suitable for the terminal, and notify the terminal, which breaks the fixed mobility mode configuration of the terminal, and implements flexible configuration and management of the mobility mode of the terminal according to the actual application scenario of the terminal, thereby optimizing network performance.
  • the mobility mode related information includes at least one of the following: mobility mode capability information, service feature information, and mobility event history statistics information; wherein the mobility mode capability information includes a mobility mode that the terminal can support, where the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service period of the terminal, where the mobility event history statistics information includes the terminal at a specific time period.
  • a handover or location update occurs, or the mobility event history statistics includes a handover or location update at a particular location, or the mobility event history statistics includes a type of mobile speed that occurs at a particular time period or location.
  • the RAN node determines the mobility mode of the terminal according to the mobility mode related information of the terminal, which may be implemented by: the RAN node according to the mobility mode capability of the terminal. Determining a mobility mode supported by the terminal; the RAN node selects a mobility mode in a mobility mode that the terminal can support according to the mobility event history statistics information of the terminal; or the RAN node Selecting, according to the service feature information of the terminal, a mobility mode in a mobility mode that the terminal can support; or the RAN node according to the service feature information of the terminal and the mobility event history The statistical information selects a mobility mode in a mobility mode that the terminal can support.
  • the mobility mode includes at least one of the following mobility management configuration information: a connection status, a location area list, a location update timer, and a paging area.
  • the connection state includes at least one of a signaling connection state and a session connection state;
  • the signaling connection state includes a non-access stratum NAS signaling connection state or a radio resource control RRC signaling connection. status.
  • the RAN node also sends the determined mobility mode to the CPF entity. This enables the terminal, the RAN node, and the CPF entity to learn the mobility mode used by the terminal, so that the network matching is consistent.
  • a fourth aspect a method for managing a mobility mode of a terminal, comprising: transmitting, by a terminal, mobility mode related information of the terminal to a control plane function CPF entity, where the mobility mode related information is used to determine the terminal a mobility mode; the terminal receives a second mobility mode sent by the RAN node; and the terminal determines a mobility management configuration information mobility mode adopted by the terminal according to the second mobility mode.
  • the terminal does not apply according to the fixed configuration of the mobility mode that can be supported by the terminal, but uses the mobility mode flexibly according to the configuration of the network side device to achieve the purpose of matching the mobility mode of the terminal with the actual application scenario of the terminal.
  • the mobility mode related information includes at least one of the following: mobility mode capability information, service feature information, and mobility event history statistics information; wherein the mobility mode capability information includes a mobility mode that the terminal can support, where the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service period of the terminal, where the mobility event history statistics information includes the terminal at a specific time period.
  • a handover or location update occurs, or the mobility event history statistics includes a handover or location update at a particular location, or the mobility event history statistics includes a type of mobile speed that occurs at a particular time period or location.
  • a management apparatus for a terminal mobility mode having a function of implementing the CPF entity behavior in any of the possible aspects of the first aspect and the first aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a terminal mobility mode management apparatus having a function of implementing RAN node behavior in any of the possible aspects of the second aspect and the second aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a terminal mobility mode management apparatus having a function of implementing RAN node behavior in any of the possible aspects of the third aspect and the third aspect described above. Said function It can be implemented by hardware or by software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a terminal having a function of implementing terminal behavior in any of the possible aspects of the fourth aspect and the fourth aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a CPF entity comprising: a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the program stored by the memory to perform the following operations: acquiring a mobility mode related information of the terminal, determining a first mobility mode of the terminal according to the obtained mobility mode related information of the terminal; and sending, by the transceiver, the first mobility mode to the RAN node of the radio access network, where The first mobility mode is used by the RAN node to determine a second mobility mode of the terminal.
  • the CPF entity can select a mobility mode suitable for the terminal according to the actual application scenario of the terminal, and determine the mobility mode finally configured for the terminal through the RAN node, and notify the terminal, breaking the fixed mobility mode configuration of the terminal, and implementing The mobility mode of the terminal is flexibly configured and managed according to the actual application scenario of the terminal, thereby optimizing network performance.
  • the mobility mode related information includes at least one of the following: mobility mode capability information, service feature information, and mobility event history statistics information; wherein the mobility mode capability information includes a mobility mode that the terminal can support, where the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service period of the terminal, where the mobility event history statistics information includes the terminal at a specific time period.
  • a handover or location update occurs, or the mobility event history statistics includes a handover or location update at a particular location, or the mobility event history statistics includes a type of mobile speed that occurs at a particular time period or location.
  • the processor is configured to: according to the mobility mode of the terminal a mobility information, determining a mobility mode that the terminal can support; selecting a mobility mode in a mobility mode that the terminal can support according to the mobility event history statistics information of the terminal; or, according to the terminal
  • the service feature information is selected in a mobility mode that the terminal can support; or, according to the service feature information of the terminal and the mobility event history statistics, the terminal can support Select mobility mode in mobility mode.
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a connection state, a location area list, a location update timer, and a paging region.
  • connection state includes at least one of a signaling connection state and a session connection state;
  • the signaling connection state includes a non-access stratum NAS signaling connection state or radio resource control RRC signaling.
  • a tenth aspect provides a radio access network RAN node, including: a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke the program stored by the memory to execute The following operation: receiving, by the transceiver, a first mobility mode of the terminal sent by the control plane function CPF entity; determining, according to the first mobility mode, a second mobility mode of the terminal; determining the second mobility The sexual mode is sent to the terminal.
  • the RAN node can configure the mobility mode for the terminal according to the mobility mode that is matched by the CPF entity to the actual application scenario of the terminal, and notify the terminal, and break the fixed mobility mode configuration of the terminal, thereby realizing flexible according to the actual application scenario of the terminal. Optimize network performance by configuring and managing the mobility mode of the endpoint.
  • the processor is configured to: acquire a mobility mode that the CPF entity can support in advance; and if the CPF entity can support the mobility management configuration information included in the first mobility mode, Determining the first mobility mode as the second mobility mode; or, if the CPF entity does not support mobility management configuration information included in the first mobility mode, selecting a default mobility mode As the second mobility mode.
  • the self-configuration of the RAN node is fully considered to ensure normal operation between the mobility mode of the RAN node and the terminal.
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a connection state, a location area list, a location update timer, and a paging region.
  • the connection state includes at least one of a signaling connection state and a session connection state;
  • the signaling connection state includes a non-access stratum NAS signaling connection state or a radio resource control RRC signaling connection. status.
  • a wireless access network RAN node including: a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke a program stored by the memory to Performing the following operations: receiving, by the transceiver, mobility mode related information of the terminal sent by the control plane function CPF entity; determining, according to the mobility mode related information received by the receiving unit, the mobility mode of the terminal; The mobility mode determined by the determining unit is sent to the terminal.
  • the RAN node can select the mobility mode suitable for the terminal according to the actual application scenario of the terminal, and notify the terminal, breaking the fixed mobility mode configuration of the terminal, and flexibly configuring and managing the mobility of the terminal according to the actual application scenario of the terminal. Mode to optimize network performance.
  • the mobility mode related information includes at least one of the following: mobility mode capability information, service feature information, and mobility event history statistics information; wherein the mobility mode capability information includes a mobility mode that the terminal can support, where the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service period of the terminal, where the mobility event history statistics information includes the terminal at a specific time period.
  • a handover or location update occurs, or the mobility event history statistics includes a handover or location update at a particular location, or the mobility event history statistics includes a type of mobile speed that occurs at a particular time period or location.
  • the processor is configured to: determine, according to the mobility mode capability information of the terminal, a mobility mode supported by the terminal; according to a mobility event history of the terminal And selecting a mobility mode in a mobility mode that the terminal can support; or selecting a mobility mode in a mobility mode that the terminal can support according to the service feature information of the terminal; or And selecting, according to the service characteristic information of the terminal and the mobility event history statistical information, a mobility mode in a mobility mode that the terminal can support.
  • the mobility mode includes at least one of the following mobility management configuration information: a connection status, a location area list, a location update timer, and a paging area.
  • the connection state includes at least one of a signaling connection state and a session connection state;
  • the signaling connection state includes a non-access stratum NAS signaling connection state or a radio resource control RRC signaling connection. status.
  • a terminal comprising: a transceiver, a memory, and a processor, wherein the memory is configured to store a set of programs, and the processor is configured to invoke a program stored by the memory to perform the following operations: a control plane function CPF entity sends mobility mode related information of the terminal, the mobility mode related information is used to determine a first mobility mode of the terminal; and receives a second mobility mode sent by the RAN node; The second mobility mode determines mobility management configuration information used by the terminal.
  • a control plane function CPF entity sends mobility mode related information of the terminal, the mobility mode related information is used to determine a first mobility mode of the terminal; and receives a second mobility mode sent by the RAN node;
  • the second mobility mode determines mobility management configuration information used by the terminal.
  • the terminal does not apply according to the fixed configuration of the mobility mode that can be supported by the terminal, but uses the mobility mode flexibly according to the configuration of the network side device to achieve the purpose of matching the mobility mode of the terminal with the actual application scenario of the terminal.
  • the mobility mode related information includes at least one of the following information: mobility mode capability information, service feature information, and mobility event history statistics;
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service cycle of the terminal, where the mobility
  • the event history statistical information includes that the terminal performs switching or location update in a specific time period, or the mobility event history statistical information includes switching or location update at a specific location, or the mobility event historical statistical information is included in a specific time period. Or the type of movement speed that occurs at a particular location.
  • FIG. 1 is a structural diagram of a communication system in an embodiment of the present application.
  • FIG. 2 is a flowchart of a method for managing a mobility mode of a terminal in an embodiment of the present application
  • FIG. 3 is a second flowchart of a method for managing a mobility mode of a terminal in an embodiment of the present application
  • FIG. 4 is a third flowchart of a method for managing a mobility mode of a terminal in an embodiment of the present application
  • FIG. 5 is a fourth flowchart of a method for managing a mobility mode of a terminal according to an embodiment of the present application
  • FIG. 6 is a structural diagram of a device for managing a mobility mode of a terminal in an embodiment of the present application.
  • FIG. 7 is a second structural diagram of a terminal mobility mode management apparatus according to an embodiment of the present application.
  • FIG. 8 is a third structural diagram of a terminal mobility mode management apparatus according to an embodiment of the present application.
  • FIG. 9 is a structural diagram of a terminal in an embodiment of the present application.
  • FIG. 10 is a structural diagram of a CPF entity in an embodiment of the present application.
  • FIG. 11 is a structural diagram of a RAN node in an embodiment of the present application.
  • FIG. 12 is a second structural diagram of a RAN node in an embodiment of the present application.
  • FIG. 13 is a second structural diagram of a terminal in an embodiment of the present application.
  • the embodiment of the present application provides a terminal mobility mode management method and apparatus.
  • the control plane function (English: Control Plane Function, CPF) entity selects the mobility mode suitable for the terminal according to the actual application scenario of the terminal, and determines the mobility mode finally configured for the terminal through the RAN node, and notifies the terminal, and breaks the terminal.
  • CPF Control Plane Function
  • the method provided in this embodiment of the present application is applicable to various wireless access technology network systems, for example, Long Term Evolution (LTE) system, 5G communication system, or more communication systems.
  • LTE Long Term Evolution
  • 5G communication system or more communication systems.
  • This application will take a 5G communication system as an example for a detailed description of the solution.
  • the 5G communication system builds the network in a flexible manner, and the network is further abstracted into a network slice (ie, Network Slice).
  • Network slicing technology is to cut a physical network into multiple virtual end-to-end networks.
  • Each virtual network, including devices, access, transmission and core networks within the network, is logically independent.
  • Each network slice is instantiated by a separate network function or combination of functions with different functional characteristics for different needs and services.
  • the communication system architecture 100 in the embodiment of the present application includes: a terminal 101, a RAN node 102, and a plurality of network slices 103.
  • the network slice 103 includes a CPF entity 104 and a user plane function (UPF).
  • the entity 105, the CPF entity 104 mainly completes the control plane related signaling message processing, including: device access authentication, security encryption, location registration and other mobility management (English: Mobility Management, abbreviation: MM) function; user plane transmission path Session management (English: Session Management, abbreviation: SM) functions; quality of service (QoS), billing, etc. related policies and billing (English: Policy and Charging, abbreviation: PC) )control function.
  • the CPF entity is an entity that has both the MM function and the SM function; or the CPF entity includes an MM-enabled entity or an SM-enabled entity.
  • the UPF entity 105 mainly performs functions such as routing and forwarding of user plane data.
  • Terminal 101 may access one or more network slices 103 through RAN node 102.
  • the method for managing the mobility mode of the terminal in this embodiment of the present application is as follows.
  • Step 201 The terminal sends the mobility mode related information of the terminal to the CPF entity.
  • the mobility mode related information is used by the CPF entity to determine a first mobility mode of the terminal, and the first mobility mode is used by the RAN node to determine a second mobility mode of the terminal.
  • the mobility mode related information includes at least one of the following information: mobility mode Capability information, business feature information, and mobility event history statistics.
  • the mobility mode capability information includes a mobility mode that the terminal can support
  • the service feature information includes at least one of a periodic service indication of the terminal, a single service communication duration, and a service period, where the mobility event history statistics information includes the terminal.
  • a handover or location update occurs during a particular time period
  • the mobility event history statistics include a handover or location update at a particular location
  • the mobility event history statistics include a type of mobile speed that occurs at a particular time period or location.
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a mobility mode, a location area list, a location update timer, and a paging area.
  • Step 202 The CPF entity acquires mobility mode related information of the terminal.
  • the CPF entity may be obtained by receiving mobility mode related information sent by the terminal, or by acquiring subscription information of the terminal.
  • the mobility mode related information is determined according to the application scenario of the terminal, and includes information about the capability, the mobility feature, and the service feature of the terminal, and may specifically include one or any combination of the following information:
  • Mobility mode capability information for service feature information, and mobility event history statistics
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature information includes at least one of a periodic service indication of the terminal, a single service communication duration, and a service period, where the mobility event history statistics information includes the terminal. Historical statistics of mobility events such as handovers, location updates, etc. occur at specific time periods and/or at specific locations.
  • Step 203 The CPF entity determines the first mobility mode of the terminal according to the mobility mode related information of the terminal.
  • the manner in which the CPF entity determines the first mobility mode of the terminal is:
  • the CPF entity determines, according to the mobility mode capability information of the terminal, a mobility mode that the terminal can support;
  • the CPF entity selects at least one mobility mode in the mobility mode that the terminal can support according to the mobility event history statistics information of the terminal; or, the CPF entity, according to the service feature information of the terminal, in the mobility mode that the terminal can support Select at least one mobility mode; or, The CPF entity selects at least one mobility mode in the mobility mode that the terminal can support according to the service characteristic information of the terminal and the historical event information of the mobility event;
  • the CPF entity determines the first mobility management configuration information of the terminal according to the selected at least one mobility mode.
  • the CPF entity determines the state parameter corresponding to the selected at least one mobility mode.
  • Step 204 The CPF entity sends the first mobility mode to the RAN node.
  • the first mobility mode is used by the RAN node to determine a second mobility mode of the terminal; the RAN node receives a first mobility mode of the terminal sent by the CPF entity;
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a connection state, a location zone list, a location update timer, and a paging zone.
  • 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 according to the first mobility mode.
  • Step 206 The RAN node sends the determined second mobility mode to the terminal, where the terminal receives the second mobility mode sent by the RAN node.
  • the RAN node further sends the second mobility mode to the CPF entity, so that the CPF entity learns the mobility mode that the terminal finally uses.
  • Step 207 The terminal determines configuration information of the terminal mobility management according to at least one mobility mode included in the second mobility mode.
  • connection state described in the embodiment of the present application includes at least one of a signaling connection state and a session connection state.
  • the CPF entity may pre-configure a mobility mode set that the CPF entity can support, where the mobility mode set includes at least one mobility mode and each mobile The mode index value corresponding to the sex mode.
  • the mobility mode set also includes transition conditions between the various mobility modes.
  • the set of mobility patterns configured by the CPF entity herein may be referred to as a first mobility mode set.
  • One possible implementation of the mobility mode set in the embodiment of the present application is one or more mobiles.
  • the form of the sexual mode list is shown in Table 1 - Table 3.
  • the mode index values in each mobility mode list include: sub mode 1, sub mode 2, sub mode 3, and the like;
  • the mobility modes of the first mobility mode, the second mobility mode, and the like described in the embodiments of the present application include at least one sub-mode as shown in Table 1, Table 2, and Table 3.
  • the CPF entity needs to further determine the state parameter corresponding to the first mobility mode and notify the RAN node.
  • the manner in which the CPF entity determines the first mobility mode of the terminal is:
  • the CPF entity determines, according to the mobility mode capability information of the terminal, at least one mobility mode that the terminal can support in the first mobility mode set;
  • the CPF entity selects a first mobility mode corresponding to the mobility event history statistics information of the terminal in the at least one mobility mode that the terminal can support according to the mobility event history statistics information of the terminal;
  • the CPF entity selects the first mobility mode corresponding to the service feature information of the terminal in at least one mobility mode that the terminal can support according to the service feature information of the terminal;
  • the CPF entity selecting, by the CPF entity, the service feature information and the location of the terminal in the at least one mobility mode that the terminal can support, according to the service feature information of the terminal and the mobility event history statistics information.
  • the first mobility mode corresponding to the mobility event history statistics information.
  • the CPF entity sends the determined first mobility mode to the RAN node, which may be, but is not limited to, the following:
  • 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 state of the terminal included in the first mobility mode to the RAN node.
  • the RAN node Before the RAN node determines the second mobility mode of the terminal according to the first mobility mode, the RAN node acquires a mobility mode set that the RAN node can support in advance.
  • the mobility mode that the RAN node can support is supported by the RAN node.
  • a collection can be referred to as a second set of mobility patterns.
  • 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 follows the default from the mobility mode set
  • the configuration selects the default mobility mode as the second mobility mode.
  • the RAN node determines the second mobility mode of the terminal according to the first mobility mode and the local configuration policy.
  • the first mobility mode includes states such as RRC_IDLE and RRC_INACTIVE, but the RAN node does not support the connection state of RRC_INACTIVE, and the RAN node selects the default RRC_IDLE and RRC_CONNECTED states.
  • the CPF entity is an entity that has the MM function and the SM function
  • the CPF entity includes the MM function entity and the SM function entity.
  • the CPF entity is a functional entity with both MM and SM functions.
  • a CPF entity has both MM and SM functions.
  • the method steps are shown in Figure 3.
  • Step 301 The terminal sends an attach request message to the CPF entity.
  • the attach request message carries information about the mobility mode capability of the terminal, and is used to identify which mobility modes the terminal can support.
  • Step 302 The CPF entity obtains the subscription information of the terminal from the user subscription database.
  • the CPF entity may also obtain subscription information of the terminal from other CPF entities attached to the terminal. This step is performed on the premise that the CPF entity does not know the subscription information of the terminal. Of course, if the CPF entity knows the subscription information of the terminal, step 302 is omitted.
  • the subscription information of the terminal includes information about the mobility mode of the terminal, that is, the selection assistance information related to the mobility mode of the terminal, including some service feature information of the terminal, for example, periodic service indication, communication duration, and communication cycle.
  • Service parameters such as fixed terminal indications, and connection status parameters such as periodic location update timers.
  • Step 303 The CPF entity acquires the mobility event history statistics information of the terminal, and determines the first mobility mode of the terminal according to the mobility event history statistics information of the terminal and the mobility mode capability of the terminal. formula.
  • the mobility event history statistics information of the terminal includes mobility event history statistics information such as handover of the terminal at a specific time period and/or a specific location, location update, and the like. For example, the number of times the terminal has changed events such as handover and location update within a certain period of time, and the statistics of the mobility events can determine whether the terminal is a mobility feature of the terminal, such as a fixed terminal, a low mobility terminal, or a high mobility.
  • the terminal and the CPF entity may set a dividing rule for the mobility feature of the terminal, which is not limited in this application.
  • the CPF entity pre-stores a set of mobility patterns.
  • One possible implementation of the mobility pattern set is in the form of one or more mobility mode lists, as shown in Table 1 - Table 3.
  • the mode index values in each mobility mode list include: sub mode 1, sub mode 2, sub mode 3, and the like.
  • the CPF entity selects a subset of the mobility modes that the terminal can support in the CPF pre-stored mobility mode set according to the mobility mode capability of the terminal, and selects a first suitable terminal in the subset according to the mobility event history statistics information of the terminal. Mobility mode.
  • the terminal can be updated in the time range of 7:00-9:00 every day.
  • the switching is very frequent, that is, the location of the terminal changes frequently. It is possible that the user is on the way to work during this time period; a small number of location updates and handovers are sent within the time period of 9:00-21:00, and the user may be in this time period.
  • the CPF entity can determine that the first mobility mode of the terminal in the 7:00-9:00 time period is the submode 1 in Table 1 and the submode 1 in Table 2, that is, the terminal is NCM_CONNECTED when there is data transmission and reception. /RRC_CONNECTED, the data should be transferred to NCM_IDLE/RRC_IDLE when it is sent and received.
  • the CPF entity may allocate a location area with a larger range to the terminal, thereby avoiding the signaling overhead caused by the terminal frequently moving out of the location area to initiate location update; the CPF entity may determine that the terminal is within the time range of 9:00-21:00.
  • a mobility mode is mode 3 in Table 1 and mode 3 in Table 2, that is, the terminal NAS signaling connection always maintains the NCM_CONNECTED state, and the RRC signaling connection has RRC_CONNECTED when data is transmitted, and when there is no data transmission, RRA_PCH, and can set the RAN routing area (English: RAN Routing Areas, abbreviation: RRA) parameter to be a plurality of cells corresponding to the terminal office area and the surrounding area, that is, paging only in the RRA range, to avoid excessive paging range Paging signaling overhead;
  • RRA RAN Routing Areas
  • the CPF entity may determine that the first mobility mode of the terminal in the 21:00-7:00 time period is still mode 3 in Table 1 and mode 3 in Table 2, but the RRA parameter is set to the cell where the terminal is currently located, and further The paging range is reduced to a specific cell, and a longer periodic location update timer can be further set.
  • the specific time period of the above example may also be replaced with a specific location, that is, the mobility mode is determined according to the mobility event history statistics of the terminal at a specific location (such as a home, office area).
  • the connection state includes at least one of a signaling connection state and a service connection state.
  • a signaling connection state when the terminal selects the first mobility mode, only the signaling connection state suitable for the terminal may be considered, and if the terminal needs a service connection, the terminal is considered.
  • the business feature parameters are used to determine the session connection state mode.
  • Step 304 The CPF entity sends the selected first mobility mode of the suitable terminal to the RAN node.
  • the mode index value corresponding to the first mobility mode of the terminal is sent to the RAN node, or the parameter included in the first mobility mode of the terminal is directly transmitted.
  • some parameter configurations related to the mobility mode obtained from the subscription information of the terminal are sent to the RAN node, for example, a periodic location update timer of the terminal.
  • Step 305 The RAN node determines, according to the first mobility mode of the terminal, the second mobility mode that is finally used according to the local configuration policy.
  • the RAN node If the RAN node cannot support the first mobility mode, the RAN node selects the default mobility mode to determine the second mobility mode that is ultimately used by the terminal.
  • the RAN node determines the first mobility mode as the second mobility mode that the terminal eventually uses.
  • Step 306 The RAN node separately sends the second mobility mode determined for the final use determined by the terminal to the terminal and the CPF entity.
  • Step 307 The terminal sends a connection establishment request message to the CPF entity.
  • Step 308 The CPF entity determines the third mobility mode of the terminal according to the service feature information of the terminal acquired in step 302 and the mobility mode capability information of the terminal.
  • the CPF entity selects a subset of the mobility modes that the terminal can support in the CPF pre-stored mobility mode set according to the mobility mode capability of the terminal, and selects the subset according to the service characteristic information of the terminal.
  • the service characteristic information of the terminal is: a periodic service, and the communication cycle is to send and receive data every 30 minutes.
  • the CPF entity may determine that the third mobility mode of the terminal is mode 3 in Table 3.
  • the transition condition is: when the session is established, the state is SESSION CONTEXT ACTIVE, and after the data is sent and received, it is changed to SESSION CONTEXT SUSPEND, when data is sent, Switch to SESSION CONTEXT ACTIVE and change to SESSION CONTEXT INACTIVE when the session is released.
  • the service characteristic information of the terminal changes, for example, it is changed to: periodic service, and the communication cycle is to send and receive data once every day.
  • the CPF can determine that the session mobility mode of the terminal is mode 1 in Table 3.
  • the transition condition is: when the session is established, the state is SESSION CONTEXT ACTIVE, and after the data is sent and received, it is changed to SESSION CONTEXT INACTIVE, and the session is re-established when data is sent. The connection is changed to SESSION CONTEXT ACTIVE.
  • the third mobility mode when the third mobility mode is selected for the terminal, only the service mobility mode suitable for the terminal can be considered.
  • Step 309 The CPF entity sends the selected third mobility mode suitable for the terminal to the RAN node.
  • the mode index value corresponding to the third mobility mode of the terminal is sent to the RAN node, or the parameter included in the third mobility mode of the terminal is directly transmitted.
  • some parameter configurations related to the mobility mode obtained from the subscription information of the terminal are sent to the RAN node, for example, a periodic location update timer of the terminal.
  • Step 310 The RAN node determines, according to the third mobility mode of the terminal, the fourth mobility mode that is finally used according to the local configuration policy.
  • Step 311 The RAN node separately sends a fourth mobility mode for final use determined by the terminal to the terminal and the CPF entity.
  • step 307 to step 311 are performed.
  • the CPF entity includes an MM-capable entity or an SM-capable entity.
  • the function of the CPF entity is implemented by two functional entities.
  • the entity with the MM function can be called an MM entity, and the entity with the SM function can be called an SM entity.
  • the method steps are shown in Figure 4.
  • Step 401 The terminal sends an attach request message to the MM entity.
  • the attach request message carries information about the mobility mode capability of the terminal, and is used to identify which mobility modes the terminal can support.
  • Step 402 The MM entity obtains the subscription information of the terminal from the user subscription database.
  • the MM entity may also obtain subscription information of the terminal from other MM entities attached to the terminal. This step is performed on the premise that the MM entity does not know the subscription information of the terminal. Of course, if the MM entity knows the subscription information of the terminal, step 402 is omitted.
  • Step 403 The MM entity acquires the mobility event history statistics information of the terminal, and determines the first mobility mode of the terminal according to the mobility event history statistics information of the terminal and the mobility mode capability of the terminal.
  • Step 404 The MM entity sends the selected first mobility mode of the suitable terminal to the RAN node.
  • Step 405 The RAN node determines, according to the first mobility mode of the terminal, the second mobility mode that is finally used according to the local configuration policy.
  • Step 406 The RAN node separately sends the second mobility mode determined for the final use determined by the terminal to the terminal and the MM entity.
  • Step 407 The terminal sends a connection establishment request message to the SM entity.
  • connection establishment request message carries information about the mobility mode capability of the terminal, and is used to Characterize which mobility modes the terminal can support.
  • Step 408 The SM entity obtains the subscription information of the terminal from the user subscription database.
  • the SM entity may also obtain subscription information of the terminal from other SM entities attached to the terminal. This step is performed on the premise that the SM entity does not know the subscription information of the terminal. Of course, if the SM entity knows the subscription information of the terminal, step 408 is omitted.
  • the subscription information of the terminal includes some parameters related to the mobility mode of the terminal, including some service characteristic information of the terminal, for example, periodic service indication, communication duration, communication period, fixed terminal indication and other service parameters, and a period. Mobility mode parameters such as the location update timer.
  • Step 409 The SM entity determines the third mobility mode of the terminal according to the obtained service characteristic information of the terminal and the mobility mode capability information of the terminal.
  • Step 410 The SM entity sends the selected third mobility mode suitable for the terminal to the RAN node.
  • Step 411 The RAN node determines, according to the third mobility mode of the terminal, the fourth mobility mode that is finally used for the terminal according to the local configuration policy.
  • Step 412 The RAN node sends the terminal and the SM entity respectively the fourth mobility mode for final use determined by the terminal.
  • step 407 to step 412 are performed.
  • the RAN node determines the mobility mode of the terminal according to the application scenario of the terminal, and the specific process is shown in FIG. 5 .
  • Step 501 The CPF entity sends the mobility mode related information of the terminal to the RAN node, and the RAN node receives the mobility mode related information of the terminal sent by the CPF entity.
  • the mobility mode related information includes one or any combination of the following information: mobility mode capability information, service feature information, and mobility event history statistics;
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature
  • the information includes at least one of a periodic service indication, a single service communication duration, and a service period of the terminal, where the mobility event history statistics information includes a handover or location update of the terminal in a specific time period, or a history information of the mobility event. This includes switching or location updates at specific locations, or mobility event history statistics including the type of mobile speed that occurs at a particular time period or at a particular location.
  • Step 502 The RAN node determines the mobility mode of the terminal according to the received mobility mode related information of the terminal.
  • the mobility mode includes at least one of the following mobility management configuration information: a connection status, a location area list, a location update timer, and paging area mobility management configuration information.
  • the RAN node determines the mobility mode supported by the terminal according to the mobility mode capability information of the terminal; then, the RAN node selects at least one mobility in the mobility mode that the terminal can support according to the mobility event history statistics information of the terminal. Or the RAN node selects at least one mobility mode in the mobility mode that the terminal can support according to the service feature information of the terminal; or the RAN node performs the traffic feature information according to the terminal and the mobility event history statistics. Selecting at least one mobility mode in a mobility mode supported by the terminal; the RAN node determining a mobility mode of the terminal according to the selected at least one mobility mode.
  • the RAN node pre-configures the mobility mode set that the RAN node can support, where the mobility mode set includes at least one mobility mode and each mobility mode respectively corresponds to The mode index value.
  • the RAN node determines, according to the mobility mode capability information of the terminal, at least one mobility mode that the terminal can support in the mobility mode set;
  • the RAN node selects a mobility mode corresponding to the mobility event history statistics information of the terminal in the at least one mobility mode that the terminal can support according to the mobility event history statistics information of the terminal; or the RAN node is configured according to the service feature information of the terminal, A mobility mode corresponding to the service feature information of the terminal is selected in at least one mobility mode that the terminal can support.
  • Step 503 The RAN node sends the determined mobility mode to the terminal.
  • the RAN node sends the mode index value corresponding to the mobility mode to the terminal; or, The RAN node transmits configuration information of the mobility mode of the terminal included in the mobility mode to the terminal.
  • the embodiment of the present application further provides a terminal mobility mode management apparatus 600 for performing the terminal mobility mode management method shown in FIG. 2.
  • the terminal mobility mode management apparatus 600 includes an acquisition unit 601, a determination unit 602, and a transmission unit 603. among them:
  • the obtaining unit 601 is configured to acquire mobility mode related information of the terminal.
  • a determining unit 602 configured to determine, according to the mobility mode related information of the terminal acquired by the obtaining unit 601, a first mobility mode of the terminal;
  • the sending unit 603 is configured to send the first mobility mode determined by the determining unit 602 to the radio access network RAN node, where the first mobility mode is used by the RAN node to determine the second mobility mode of the terminal.
  • the mobility mode related information includes at least one of the following information: mobility mode capability information, service feature information, and mobility event history statistics information;
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature information includes at least one of a periodic service indication of the terminal, a single service communication duration, and a service period, where the mobility event history statistics information includes the terminal.
  • a handover or location update occurs during a particular time period, or the mobility event history statistics include a handover or location update at a particular location, or the mobility event history statistics include a type of mobile speed that occurs at a particular time period or location.
  • the determining unit 602 is configured to:
  • a first mobility mode of the terminal is determined based on the selected at least one mobility mode.
  • the first mobility mode and the second mobility mode both include the following mobility management At least one of the configuration information: a connection status, a location area list, a location update timer, and a paging area.
  • the mobility mode includes at least one of a signaling mobility mode and a session mobility mode;
  • the signaling mobility mode includes a non-access stratum NAS signaling mobility mode or a radio resource control RRC signaling mobility mode.
  • the embodiment of the present application further provides a terminal mobility mode management apparatus 700 for performing the terminal mobility mode management method shown in FIG. 2.
  • the terminal mobility mode management apparatus 700 includes a receiving unit 701, a determining unit 702, and a transmitting unit 703. among them:
  • the receiving unit 701 is configured to receive a first mobility mode of the terminal sent by the control plane function CPF entity.
  • a determining unit 702 configured to determine, according to the first mobility mode received by the receiving unit 701, a second mobility mode of the terminal;
  • the sending unit 703 is configured to send the second mobility mode determined by the determining unit 702 to the terminal.
  • the determining unit 702 is configured to:
  • the device is capable of supporting the mobility management configuration information included in the first mobility mode, determining the first mobility mode as the second mobility mode;
  • the default mobility mode is selected as the second mobility mode.
  • the first mobility mode and the second mobility mode each include at least one of the following mobility management configuration information: a connection state, a location zone list, a location update timer, and a paging zone.
  • connection status includes at least one of a signaling connection state and a session connection state
  • the signaling connection status includes a non-access stratum NAS signaling connection status or a radio resource control RRC signaling connection status.
  • the embodiment of the present application further provides another terminal mobility mode management apparatus 800 for performing the terminal mobility mode management method shown in FIG. 5.
  • the terminal mobility mode management apparatus 800 includes a receiving unit 801, a determining unit 802, and a transmitting unit 803. among them:
  • the receiving unit 801 is configured to receive mobility mode related information of the terminal sent by the control plane function CPF entity;
  • a determining unit 802 configured to determine, according to the mobility mode related information received by the receiving unit 801, a mobility mode of the terminal;
  • the sending unit 803 is configured to send the mobility mode determined by the determining unit 802 to the terminal.
  • the mobility mode related information includes at least one of the following information: mobility mode capability information, service feature information, and mobility event history statistics information;
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature information includes at least one of a periodic service indication of the terminal, a single service communication duration, and a service period, where the mobility event history statistics information includes the terminal.
  • a handover or location update occurs during a particular time period, or the mobility event history statistics include a handover or location update at a particular location, or the mobility event history statistics include a type of mobile speed that occurs at a particular time period or location.
  • the determining unit 802 is configured to:
  • the mobility mode of the terminal is determined according to the selected at least one mobility mode.
  • the mobility mode includes at least one of the following mobility management configuration information: a connection status, a location area list, a location update timer, and a paging area.
  • connection status includes at least one of a signaling connection state and a session connection state
  • the signaling connection status includes a non-access stratum NAS signaling connection status or a radio resource control RRC signaling connection status.
  • the embodiment of the present application further provides a terminal 900 for performing the terminal mobility mode management method shown in FIG. 2.
  • the terminal 900 includes a transmitting unit 901, a receiving unit 902, and a determining unit 903.
  • the sending unit 901 is configured to send mobility mode related information of the terminal to a control plane function CPF entity, where the mobility mode related information is used to determine a first mobility mode of the terminal;
  • the receiving unit 902 is configured to receive a second mobility mode sent by the RAN node.
  • the determining unit 903 is configured to determine, according to the at least one mobility mode included in the second mobility mode, a mobility mode adopted by the terminal.
  • the mobility mode related information includes at least one of the following information: mobility mode capability information, service feature information, and mobility event history statistics.
  • the mobility mode capability information includes a mobility mode that the terminal can support, and the service feature information includes at least one of a periodic service indication, a single service communication duration, and a service cycle of the terminal, where the mobility
  • the event history statistical information includes that the terminal performs switching or location update in a specific time period, or the mobility event history statistical information includes switching or location update at a specific location, or the mobility event historical statistical information is included in a specific time period. Or the type of movement speed that occurs at a particular location.
  • the embodiment of the present application further provides a CPF entity 1000, including: a transceiver 1001, a processor 1002, and a memory 1003.
  • the memory 1003 is used to store a set of programs, and the processor 1002 is configured to call a program stored in the memory 1003 to execute the management method of the terminal mobility mode shown in FIG. 2.
  • the processor 1002 may be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of a CPU and an NP.
  • CPU central processing unit
  • NP network processor
  • the processor 1002 may further include a hardware chip.
  • the above hardware chip may be an application-specific integrated circuit (ASIC: ASIC), programmable logic Device (English: programmable logic device, abbreviation: PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic Device
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory 1003 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 1003 may also include a non-volatile memory (English: non-volatile memory) For example, flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory 1003 may also include the above types of memory The combination.
  • a volatile memory English: volatile memory
  • RAM random access memory
  • non-volatile memory English: non-volatile memory
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviated: HDD
  • SSD solid state drive
  • the RAN node 1100 further includes 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 configured to call a program stored in the memory 1103 to execute a management method of executing the terminal mobility mode shown in FIG. 2.
  • the processor 1102 can be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of a CPU and an NP.
  • CPU central processing unit
  • NP network processor
  • the processor 1102 can also further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory 1103 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 1103 may also include a non-volatile memory (English: non-volatile memory) ), such as flash memory (English) Text: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory 1103 may also include a combination of the above types of memory.
  • a volatile memory English: volatile memory
  • RAM random access memory
  • non-volatile memory English: non-volatile memory
  • flash memory English
  • HDD hard disk drive
  • SSD solid state drive
  • an embodiment of the present application further provides another RAN node 1200, including: a transceiver 1201, a processor 1202, and a memory 1203.
  • the memory 1203 is configured to store a set of programs
  • the processor 1202 is configured to invoke a program stored in the memory 1203 to execute the management method of the terminal mobility mode shown in FIG. 5.
  • the processor 1202 may be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviation: NP) or a combination of a CPU and an NP.
  • CPU central processing unit
  • NP network processor
  • the processor 1202 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory 1203 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 1203 may also include a non-volatile memory (English: non-volatile memory) For example, flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory 1203 may also include the above types of memory The combination.
  • a volatile memory English: volatile memory
  • RAM random access memory
  • non-volatile memory English: non-volatile memory
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviated: HDD
  • SSD solid state drive
  • the embodiment of the present application further provides another terminal 1300, including: a transceiver 1301, a processor 1302, and a memory 1303.
  • the memory 1303 is configured to store a set of programs
  • the processor 1302 is configured to call a program stored in the memory 1303 to execute a management method for executing the terminal mobility mode shown in FIG. 2.
  • the processor 1302 may be a central processing unit (English: central processing unit, abbreviation: CPU).
  • Network processor English: network processor, abbreviation: NP
  • CPU central processing unit
  • NP network processor
  • the processor 1302 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory 1303 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 1303 may also include a non-volatile memory (English: non-volatile memory) For example, flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory 1303 may also include the above types of memory The combination.
  • a volatile memory English: volatile memory
  • RAM random access memory
  • non-volatile memory English: non-volatile memory
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviated: HDD
  • SSD solid state drive
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • 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.
  • 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 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种终端移动性模式的管理方法及装置，用于实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。该方法为：控制面功能CPF实体获取终端的移动性模式相关信息；所述CPF实体根据所述终端的移动性模式相关信息确定所述终端的第一移动性模式；所述CPF实体将确定的所述第一移动性模式发送至无线接入网络RAN节点，所述第一移动性模式用于所述RAN节点确定所述终端的第二移动性模式。

Description

一种终端移动性模式的管理方法及装置 技术领域
本申请涉及通信技术领域，特别涉及一种终端移动性模式的管理方法及装置。
背景技术
在第五代(5th Generation，5G)通信系统中，终端的连接状态可包括信令连接状态和会话连接状态。信令连接状态包括：非接入层(Non Access stratum,NAS)信令连接管理(英文：Connection Management，缩写：CM)状态，和无线资源控制(英文：Radio Resource Control，缩写：RRC)信令连接管理状态。其中，NAS信令连接管理状态可用NCM表示，用于表示终端和核心网之间的NAS信令连接的建立状态，例如NCM_IDLE、NCM_CONNECTED等状态。NCM_IDLE表示终端和核心网没有建立信令连接；NCM_CONNECTED表示终端和核心网已经通过一个RAN节点建立了信令连接。RRC信令连接管理状态用于表示终端和无线接入网之间的RRC信令连接的建立状态。例如RRC_IDLE、RRC_CONNECTED、RRC_INACTIVE和RRA_PCH等状态。RRC_IDLE表示终端和RAN节点之间没有建立RRC连接；RRC_CONNECTED表示终端和RAN节点之间已经建立RRC连接；RRC_INACTIVE表示数据包发送完成之后，RAN节点仍然保存终端的RRC上下文和承载上下文等信息；RRA标识一个RAN节点覆盖的范围，RRA_PCH表示终端处于空闲态时，网络只在这个RRA范围内寻呼终端。
会话连接管理状态用于表示会话上下文在终端和网络之间的激活状态，包括SESSION CONTEXT ACTIVE、SESSION CONTEXT INACTIVE和SESSION CONTEXT SUSPEND等状态。其中SESSION CONTEXT ACTIVE表示会话上下文处于激活状态，即会话上下文已被保存；SESSION CONTEXT INACTIVE表示会话上下文处于去激活状态，即会话上下文已被删除； SESSION CONTEXT SUSPEND表示会话上下文保存，但没有数据收发。
对于信令连接状态来说，不同的信令连接状态表示了终端位置的可达性等级，即核心网能够确定终端位置的精度。例如，终端处于NCM_IDLE状态时，表示终端和核心网没有建立信令连接，核心网能够确定终端位置的精度为核心网预先分配给终端的位置区域范围，该位置区域范围包含多个无线接入网络(英文：Radio Access Network，缩写：RAN)节点的覆盖范围；而终端处于NCM_CONNECTED状态时，表示终端和核心网已经通过一个RAN节点建立了信令连接，核心网能够确定终端位置的精度是一个RAN节点的覆盖范围。当有下行数据时，如果终端处于NCM_IDLE状态，核心网需要在终端所在位置区域范围内的多个RAN节点寻呼终端，以便向终端发送数据，这样会产生寻呼开销。当然终端在处于NCM_CONNECTED状态时，核心网可直接将数据发送给终端当前所在的RAN节点，不需要做寻呼，能够降低寻呼开销，但是，如果终端一直保持NCM_CONNECTED，则当终端由于位置移动接入新的RAN节点时，就需要向核心网更新终端所在位置，而这样会产生位置更新开销。因此，上述寻呼开销和位置更新开销之间需要达到一个平衡状态，才能使总开销最低。
现有技术中，终端的连接状态和状态转移条件是预先配置在终端和网络侧设备中的，在终端和核心网预先配置终端的信令连接状态及状态转移条件为：终端在发送或接收数据之前，需要先和核心网建立信令连接状态为NCM_CONNECTED；当数据收发结束之后释放信令，即将信令连接状态转为NCM_IDLE。在这种固定的配置下，很难使得上述寻呼开销和位置更新开销之间需要达到一个平衡状态。
对于会话连接状态来说，表示某个业务的会话上下文在终端和网络之间的激活状态。现有技术中，终端的连接状态和状态转移条件是预先配置在终端和网络侧设备中的，在终端和RAN节点预先配置的终端的会话连接状态及状态转移条件为：当终端存在业务数据正在收发时，会话连接状态为SESSION CONTEXT ACTIVE，当业务数据收发结束时，会话连接状态转为SESSION  CONTEXT INACTIVE，且RAN节点删除会话上下文。基于这种固定的配置，对于数据业务频繁的终端，例如每隔1分钟收发一次数据，则每次收发数据都需要重新建立会话上下文，信令开销较大。而对于数据业务不频繁的终端，例如每隔1天收发一次数据，则一直保存会话上下文会带来额外的存储和维护开销。
综上所述，现有技术中，终端的连接状态及状态转移条件是预先配置在终端和网络侧设备中的，而这种固定的配置往往不能根据终端的实际应用场景而灵活更改，从而降低网络性能。
发明内容
本申请提供一种终端移动性模式的管理方法及装置，所述移动性模式包括移动性管理配置信息，例如连接状态，位置区列表，位置更新定时器，寻呼区域等配置信息，用以灵活配置和管理终端的移动性管理配置信息，从而优化网络性能。
第一方面，提供一种终端移动性模式的管理方法，该方法通过以下方式实现，控制面功能CPF实体获取终端的移动性模式相关信息，并根据所述终端的移动性模式相关信息确定所述终端的第一移动性模式，所述CPF实体发送所述第一移动性模式给无线接入网络RAN节点，以使得所述RAN节点根据所述第一移动性模式确定所述终端的第二移动性模式。这样，CPF实体能够根据终端的实际应用场景来选择适合终端的移动性模式，并通过RAN节点确定最终为终端配置的移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。
在一个可能的设计中，所述CPF实体将所述终端的第一移动性模式直接发送给所述终端。
在一个可能的设计中，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；其 中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。这样，能够充分利用终端的历史数据获取终端的实际应用场景，使得CPF实体和RAN节点能够准确确定适合终端实际应用场景的移动性模式。
在一个可能的设计中，所述CPF实体根据所述终端的移动性模式相关信息，确定所述终端的所述第一移动性模式，通过以下方式实现：所述CPF实体根据所述终端的移动性模式能力信息，确定所述终端能够支持的移动性模式；所述CPF实体根据所述终端的移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，所述CPF实体根据所述终端的所述业务特征信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，所述CPF实体根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式。
在一个可能的设计中，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
在一个可能的设计中，所述连接状态包括信令连接状态和会话连接状态中的至少一种；所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
在一个可能的设计中，所述RAN节点还将确定的所述第二移动性模式发送给所述CPF实体。这样能够使终端、RAN节点和CPF实体获知终端使用的移动性模式，使得网络匹配达到一致。
第二方面，提供一种终端移动性模式的管理方法，包括：无线接入网络RAN节点接收控制面功能CPF实体发送的终端的第一移动性模式；所述RAN 节点根据所述第一移动性模式，确定所述终端的第二移动性模式；所述RAN节点将确定的所述第二移动性模式发送给所述终端。这样，RAN节点能够根据CPF实体发送与终端的实际应用场景匹配的移动性模式为终端配置移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。
在一个可能的设计中，所述RAN节点根据所述第一移动性模式确定所述终端的第二移动性模式，可以通过以下方式实现：所述RAN节点预先获取所述RAN节点能够支持的移动性模式；若所述RAN节点能够支持所述第一移动性模式中包括的移动性管理配置信息，则所述RAN节点将所述第一移动性模式确定为所述第二移动性管理配置信息；或者，若所述RAN节点不支持所述第一移动性模式中包括的移动性管理配置信息，则所述RAN节点选择默认的移动性模式作为所述第二移动性模式。在对终端的移动性模式灵活配置的基础上，充分考虑RAN节点的自身配置，保证RAN节点与终端的移动性模式之间工作正常。
在一个可能的设计中，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
在一个可能的设计中，所述连接状态包括信令连接状态和会话连接状态中的至少一种；所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
在一个可能的设计中，所述RAN节点还将确定的所述第二移动性模式发送给所述CPF实体。这样能够使终端、RAN节点和CPF实体获知终端使用的移动性模式，使得网络匹配达到一致。
第三方面，提供一种终端移动性模式的管理方法，包括：无线接入网络RAN节点接收控制面功能CPF实体发送的终端的移动性模式相关信息，所述RAN节点根据所述移动性模式相关信息，确定所述终端的移动性模式；所述RAN节点将所述移动性模式发送给所述终端。这样，RAN节点能够根据终端 的实际应用场景来选择适合终端的移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。
在一个可能的设计中，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；其中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。这样，能够充分利用终端的历史数据获取终端的实际应用场景，使得CPF实体和RAN节点能够准确确定适合终端实际应用场景的移动性模式。
在一个可能的设计中，所述RAN节点根据所述终端的移动性模式相关信息，确定所述终端的移动性模式，可以通过以下方式实现：所述RAN节点根据所述终端的移动性模式能力信息，确定所述终端支持的移动性模式；所述RAN节点根据所述终端的移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，所述RAN节点根据所述终端的所述业务特征信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，所述RAN节点根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式。
在一个可能的设计中，所述移动性模式包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
在一个可能的设计中，所述连接状态包括信令连接状态和会话连接状态中的至少一种；所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
在一个可能的设计中，所述RAN节点还将确定的移动性模式发送给所述 CPF实体。这样能够使终端、RAN节点和CPF实体获知终端使用的移动性模式，使得网络匹配达到一致。
第四方面，提供一种终端移动性模式的管理方法，包括：终端向控制面功能CPF实体发送所述终端的移动性模式相关信息，所述移动性模式相关信息用于确定所述终端的第一移动性模式；所述终端接收RAN节点发送的第二移动性模式；所述终端根据所述第二移动性模式确定所述终端采用的移动性管理配置信息移动性模式。这样，终端并不是根据自身能够支持的移动性模式的固定配置来应用，而是根据网络侧设备的配置灵活采用移动性模式，达到终端的移动性模式与终端的实际应用场景匹配的目的。
在一个可能的设计中，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；其中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
第五方面，提供一种终端移动性模式的管理装置，该装置具有实现上述第一方面和第一方面的任一种可能的设计中CPF实体行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，提供一种终端移动性模式的管理装置，该装置具有实现上述第二方面和第二方面的任一种可能的设计中RAN节点行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，提供一种终端移动性模式的管理装置，该装置具有实现上述第三方面和第三方面的任一种可能的设计中RAN节点行为的功能。所述功能 可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供一种终端，该终端具有实现上述第四方面和第四方面的任一种可能的设计中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，提供一种CPF实体，包括：收发器、存储器和处理器，其中，所述存储器用于存储一组程序，所述处理器用于调用所述存储器存储的程序以执行以下操作：获取终端的移动性模式相关信息，根据获取的终端的移动性模式相关信息，确定所述终端的第一移动性模式；通过收发器发送所述第一移动性模式给无线接入网络RAN节点，所述第一移动性模式用于所述RAN节点确定所述终端的第二移动性模式。这样，CPF实体能够根据终端的实际应用场景来选择适合终端的移动性模式，并通过RAN节点确定最终为终端配置的移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。
在一个可能的设计中，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；其中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。这样，能够充分利用终端的历史数据获取终端的实际应用场景，使得CPF实体和RAN节点能够准确确定适合终端实际应用场景的移动性模式。
在一个可能的设计中，所述处理器用于：根据所述终端的移动性模式能 力信息，确定所述终端能够支持的移动性模式；根据所述终端的移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式。
在一个可能的设计中，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
在一个可能的设计中，所述连接状态包括信令连接状态和会话连接状态中的至少一种；所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令。
第十方面，提供一种无线接入网络RAN节点，包括：收发器、存储器和处理器，其中，所述存储器用于存储一组程序，所述处理器用于调用所述存储器存储的程序以执行以下操作：通过收发器接收控制面功能CPF实体发送的终端的第一移动性模式；根据所述第一移动性模式，确定所述终端的第二移动性模式；将确定的所述第二移动性模式发送给所述终端。这样，RAN节点能够根据CPF实体发送与终端的实际应用场景匹配的移动性模式为终端配置移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。
在一个可能的设计中，所述处理器用于：预先获取所述CPF实体能够支持的移动性模式；若所述CPF实体能够支持所述第一移动性模式中包括的移动性管理配置信息，则将所述第一移动性模式确定为所述第二移动性模式；或者，若所述CPF实体不支持所述第一移动性模式中包括的移动性管理配置信息，则选择默认的移动性模式作为所述第二移动性模式。在对终端的移动性模式灵活配置的基础上，充分考虑RAN节点的自身配置，保证RAN节点与终端的移动性模式之间工作正常。
在一个可能的设计中，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
在一个可能的设计中，所述连接状态包括信令连接状态和会话连接状态中的至少一种；所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
第十一方面，提供一种无线接入网络RAN节点，包括：收发器、存储器和处理器，其中，所述存储器用于存储一组程序，所述处理器用于调用所述存储器存储的程序以执行以下操作：通过收发器接收控制面功能CPF实体发送的终端的移动性模式相关信息；根据所述接收单元接收的所述移动性模式相关信息，确定所述终端的移动性模式；将所述确定单元确定的所述移动性模式发送给所述终端。这样，RAN节点能够根据终端的实际应用场景来选择适合终端的移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的移动性模式，从而优化网络性能。
在一个可能的设计中，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；其中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。这样，能够充分利用终端的历史数据获取终端的实际应用场景，使得CPF实体和RAN节点能够准确确定适合终端实际应用场景的移动性模式。
在一个可能的设计中，所述处理器用于：根据所述终端的移动性模式能力信息，确定所述终端支持的移动性模式；根据所述终端的移动性事件历史 统计信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息，在所述终端能够支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端能够支持的移动性模式中选择移动性模式。
在一个可能的设计中，所述移动性模式包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
在一个可能的设计中，所述连接状态包括信令连接状态和会话连接状态中的至少一种；所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
第十二方面，提供一种终端，包括：收发器、存储器和处理器，其中，所述存储器用于存储一组程序，所述处理器用于调用所述存储器存储的程序以执行以下操作：向控制面功能CPF实体发送所述终端的移动性模式相关信息，所述移动性模式相关信息用于确定所述终端的第一移动性模式；接收RAN节点发送的第二移动性模式；根据所述第二移动性模式确定所述终端采用的移动性管理配置信息。这样，终端并不是根据自身能够支持的移动性模式的固定配置来应用，而是根据网络侧设备的配置灵活采用移动性模式，达到终端的移动性模式与终端的实际应用场景匹配的目的。
在一个可能的设计中，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
其中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
附图说明
图1为本申请实施例中通信系统架构图；
图2为本申请实施例中终端移动性模式的管理方法流程图之一；
图3为本申请实施例中终端移动性模式的管理方法流程图之二；
图4为本申请实施例中终端移动性模式的管理方法流程图之三；
图5为本申请实施例中终端移动性模式的管理方法流程图之四；
图6为本申请实施例中终端移动性模式的管理装置结构图之一；
图7为本申请实施例中终端移动性模式的管理装置结构图之二；
图8为本申请实施例中终端移动性模式的管理装置结构图之三；
图9为本申请实施例中终端结构图之一；
图10为本申请实施例中CPF实体结构图；
图11为本申请实施例中RAN节点结构图之一；
图12为本申请实施例中RAN节点结构图之二；
图13为本申请实施例中终端结构图之二。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
针对现有技术中，终端固定的移动性管理配置信息不能根据终端的实际应用场景而灵活更改，从而降低网络性能的问题，本申请实施例提供了一种终端移动性模式的管理方法及装置，控制面功能(英文：Control Plane Function，CPF)实体根据终端的实际应用场景来选择适合终端的移动性模式，并通过RAN节点确定最终为终端配置的移动性模式，并通知给终端，打破了终端固定的移动性模式配置，实现根据终端的实际应用场景灵活配置和管理终端的 移动性模式，从而优化网络性能。
本申请实施例提供的方法可适用于各种无线接入技术网络系统，例如，长期演进(英文：Long Term Evolution，缩写：LTE)系统、5G通信系统或者以后更多的通信系统。本申请将以5G通信系统为例作详细方案的说明。
5G通信系统以灵活的方式构建网络，网络将被进一步抽象为网络切片(即Network Slice)。网络切片技术是将一个物理网络切割成多个虚拟的端到端的网络，每个虚拟网络之间，包括网络内的设备、接入、传输和核心网，是逻辑独立的。每个网络切片由一个独立的网络功能或功能组合实例化构成，具备不同的功能特点，面向不同的需求和服务。
如图1所示，本申请实施例中通信系统架构100包括：终端101、RAN节点102和若干个网络切片103，一个网络切片103中包括CPF实体104和用户面功能(user plane function，UPF)实体105，CPF实体104主要完成控制面相关的信令消息处理，包括：设备接入鉴权、安全加密、位置注册等移动性管理(英文：Mobility Management，缩写：MM)功能；用户面传输路径的建立、释放和更改等会话管理(英文：Session Management，缩写：SM)功能；服务质量(Quality of Service，QoS)、计费等相关的策略和计费(英文：Policy and Charging，缩写：PC)控制功能。本申请实施例中，CPF实体为同时具备MM功能和SM功能的一个实体；或者，CPF实体包括具备MM功能的实体或具备SM功能的实体。UPF实体105主要完成用户面数据的路由转发等功能。终端101可通过RAN节点102接入一个或多个网络切片103。
基于图1所示的通信系统架构，下面将结合附图及优选的实施例对本申请提供的方案作详细说明。
参阅图2所示，本申请实施例终端移动性模式的管理方法流程如下。
步骤201：终端向CPF实体发送终端的移动性模式相关信息。
该移动性模式相关信息用于CPF实体确定终端的第一移动性模式，第一移动性模式用于RAN节点确定终端的第二移动性模式。
可选的，移动性模式相关信息包括以下信息中的至少一种：移动性模式 能力信息、业务特征信息和移动性事件历史统计信息。其中，移动性模式能力信息包括终端能够支持的移动性模式，业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
可选的，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：移动性模式，位置区列表，位置更新定时器，寻呼区域。
步骤202：CPF实体获取终端的移动性模式相关信息。
CPF实体可以通过接收终端发送的移动性模式相关信息来获取，或者，通过终端的签约信息来获取。
移动性模式相关信息根据终端的应用场景确定，大致包括终端的能力、移动性特征和业务特征等信息，具体可包括以下信息中的一种或任意组合：
移动性模式能力信息、业务特征信息、移动性事件历史统计信息；
其中，移动性模式能力信息包括终端能够支持的移动性模式，业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，移动性事件历史统计信息包括终端在特定时间段和/或特定位置发生切换、位置更新等移动性事件的历史统计信息。
步骤203：CPF实体根据终端的移动性模式相关信息确定终端的第一移动性模式。
可选的，CPF实体确定终端的第一移动性模式的方式为：
首先，CPF实体根据终端的移动性模式能力信息，确定终端能够支持的移动性模式；
然后，CPF实体根据终端的移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，CPF实体根据终端的业务特征信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者， CPF实体根据终端的业务特征信息和移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；
CPF实体根据选择的至少一个移动性模式确定终端的第一移动性管理配置信息。
可选的，CPF实体在终端能够支持的移动性模式中选择至少一个移动性模式之后，确定所选择的至少一个移动性模式对应的状态参数。
步骤204：CPF实体发送第一移动性模式给RAN节点；
该第一移动性模式用于RAN节点确定终端的第二移动性模式；RAN节点接收CPF实体发送的终端的第一移动性模式；
第一移动性模式和第二移动性模式中均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
步骤205：RAN节点在接收到CPF实体发送的终端的第一移动性模式后，根据第一移动性模式确定终端的第二移动性模式。
步骤206：RAN节点将确定的第二移动性模式发送给终端，终端接收RAN节点发送的第二移动性模式。
可选地，RAN节点还将第二移动性模式发送给CPF实体，以使CPF实体获知终端最终使用的移动性模式。
步骤207：终端根据第二移动性模式中包含的至少一个移动模式，确定所述终端移动性管理的配置信息。
本申请实施例中所述的连接状态包括信令连接状态和会话连接状态中的至少一种。
具体地，在步骤203中，在CPF实体在确定终端的第一移动性模式之前，CPF实体可以预先配置CPF实体能够支持的移动性模式集合，移动性模式集合包括至少一个移动性模式以及各个移动性模式分别对应的模式索引值。可选的，移动性模式集合中还包括各个移动性模式之间的转移条件。为了方便描述，这里将CPF实体配置的移动性模式集合可称为第一移动性模式集合。
本申请实施例中移动性模式集合一种可能的实现方式是一个或多个移动 性模式列表的形式，如表1-表3所示。每一个移动性模式列表中的模式索引值包括：子模式1、子模式2、子模式3等等；
本申请实施例中所述的第一移动性模式、第二移动性模式等移动性模式包括如表1、表2和表3所示的至少一个子模式。
需要说明的是，如果状态模式列表中未包括状态参数，CPF实体需要进一步确定第一移动性模式对应的状态参数，并告知RAN节点。
表1
Figure PCTCN2016096443-appb-000001
表2
Figure PCTCN2016096443-appb-000002
表3
Figure PCTCN2016096443-appb-000003
Figure PCTCN2016096443-appb-000004
可选的，CPF实体确定终端的第一移动性模式的方式为：
首先，CPF实体根据终端的移动性模式能力信息，确定第一移动性模式集合中终端能够支持的至少一个移动性模式；
然后，CPF实体根据终端的移动性事件历史统计信息，在终端能够支持的至少一个移动性模式中选择与终端的移动性事件历史统计信息对应的第一移动性模式；或者，
所述CPF实体根据所述终端的所述业务特征信息，在所述终端能够支持的至少一个移动性模式中选择与所述终端的所述业务特征信息对应的所述第一移动性模式；或者
所述CPF实体根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端能够支持的至少一个移动性模式中选择与所述终端的所述业务特征信息和所述移动性事件历史统计信息对应的所述第一移动性模式。
CPF实体将确定的第一移动性模式发送至RAN节点，可以但不限于通过以下方式：
CPF实体将第一移动性模式对应的模式索引值发送给RAN节点；或者，CPF实体将第一移动性模式中包括的终端的连接状态的配置信息发送给RAN节点。
RAN节点在根据第一移动性模式确定终端的第二移动性模式之前，RAN节点预先获取RAN节点能够支持的移动性模式集合，为方便描述，这里RAN节点获取的RAN节点能够支持的移动性模式集合可称为第二移动性模式集合。
RAN节点确定第一移动性模式是否包含在第二移动性模式集合中；若是，则RAN节点将第一移动性模式确定为第二移动性模式；否则，RAN节点从移动性模式集合中按照默认配置选择默认的移动性模式作为第二移动性模式。
即，RAN节点根据第一移动性模式和本地配置策略确定终端的第二移动性模式。例如，第一移动性模式中包含RRC_IDLE和RRC_INACTIVE等状态，但是RAN节点不支持RRC_INACTIVE这种连接状态，则RAN节点则选择默认的RRC_IDLE和RRC_CONNECTED状态。
下面根据CPF实体为具备MM功能和SM功能的一个实体，和CPF实体包括具备MM功能的实体和具备SM功能的实体这两种应用场景，对本申请实施例提供的上述方案作进一步详细的介绍。
应用场景一：CPF实体为一个功能实体，同时具备MM功能和SM功能。
这种场景下，一个CPF实体同时具备MM功能和SM功能。方法步骤如图3所示。
步骤301：终端向CPF实体发送附着请求消息；
其中，附着请求消息中携带了终端的移动性模式能力的信息，用于表征终端能够支持哪些移动性模式。
步骤302：CPF实体从用户签约数据库中获取终端的签约信息。
或者，CPF实体也可以从终端之前附着的其他CPF实体获取终端的签约信息。本步骤是在CPF实体不知终端的签约信息的前提下进行的，当然，如果CPF实体已知终端的签约信息，则省略步骤302。
终端的签约信息中包括了一些终端的移动性模式相关信息，即与终端的移动性模式相关的选择辅助信息，包括终端的一些业务特征信息，例如，周期性业务指示、通信持续时间、通信周期、固定终端指示等业务参数，还有周期性位置更新定时器等连接状态参数。
步骤303：CPF实体获取终端的移动性事件历史统计信息，并根据终端的移动性事件历史统计信息和终端的移动性模式能力确定终端的第一移动性模 式。
终端的移动性事件历史统计信息包括终端在特定时间段和/或特定位置的切换、位置更新等移动性事件历史统计信息。例如，终端在一定时间段内发生切换、位置更新等事件的次数，通过这些移动性事件的统计能够确定终端是终端的移动性特征，例如是固定终端、还是低移动性终端、或者高移动性终端，CPF实体可以对终端的上述移动性特征设定划分规则，本申请不作限制。
CPF实体预先存储一个移动性模式集合，移动性模式集合一种可能的实现方式是一个或多个移动性模式列表的形式，如表1-表3所示。每一个移动性模式列表中的模式索引值包括：子模式1、子模式2、子模式3等等。
CPF实体根据终端的移动性模式能力在CPF预存的移动性模式集合中选择终端能够支持的移动性模式的子集，并根据终端的移动性事件历史统计信息在子集中选择一个适合终端的第一移动性模式。
例如：根据终端在一个月内的每一天每一时间段发生位置更新、切换等移动性事件的数量进行统计，可得到终端在每一天的7:00-9:00时间段内发生位置更新、切换非常频繁，即终端的位置变化比较频繁，可能这一时间段用户在上班途中；在9:00-21:00时间段内发送较少数量的位置更新、切换，可能这一时间段用户在办公区及周边区域；而在21:00-7:00时间段内几乎不发生位置更新、切换，即终端的位置几乎不变化，可能这一时间段用户在家中。因此，CPF实体可确定终端在7:00-9:00时间段内的第一移动性模式为表1中的子模式1以及表2中的子模式1，即终端在有数据收发时为NCM_CONNECTED/RRC_CONNECTED，数据收发完成时应转为NCM_IDLE/RRC_IDLE。并且，CPF实体可为终端分配范围较大的位置区，从而避免终端频繁移出位置区发起位置更新带来的信令开销；CPF实体可确定终端在9:00-21:00时间段内的第一移动性模式为表1中的模式3以及表2中的模式3，即终端NAS信令连接始终保持NCM_CONNECTED状态，RRC信令连接有数据发送时为RRC_CONNECTED，没有数据发送时为 RRA_PCH，并且可设置RAN路由区(英文：RAN Routing Areas，缩写：RRA)参数为终端办公区及周边区域对应的多个小区，即仅在RRA范围进行寻呼，避免寻呼范围过大带来的寻呼信令开销；
CPF实体可确定终端在21:00-7:00时间段内的第一移动性模式仍然为表1中的模式3以及表2中的模式3，但是设置RRA参数为终端当前所在的小区，进一步缩小寻呼范围为一个特定小区，还可进一步设置较长的周期性位置更新定时器。
上述例子的特定时间段也可以替换成特定位置，即根据终端在特定位置(如家中、办公区)的移动性事件历史统计信息来确定移动性模式。
连接状态至少包括信令连接状态和业务连接状态中的一种，这里为终端选择第一移动性模式时，可以仅考虑适合终端的信令连接状态，后续若终端需要业务连接时，再考虑终端的业务特征参数来确定会话连接状态模式。
步骤304：CPF实体将选择的适合终端的第一移动性模式发送给RAN节点。
具体地，将终端的第一移动性模式对应的模式索引值发送给RAN节点，或者，直接发送终端的第一移动性模式中包括的参数。同时，将从终端的签约信息中获取的与移动性模式相关的一些参数配置发送给RAN节点，例如终端的周期性位置更新定时器。
步骤305：RAN节点根据终端的第一移动性模式，以及根据本地的配置策略为终端确定最终使用的第二移动性模式。
若RAN节点不能支持第一移动性模式，则RAN节点会选择默认的移动性模式确定为终端最终使用的第二移动性模式。
若RAN节点能支持第一移动性模式，则RAN节点将第一移动性模式确定为终端最终使用的第二移动性模式。
步骤306：RAN节点分别向终端和CPF实体发送为终端确定的最终使用的第二移动性模式。
步骤307：终端向CPF实体发送连接建立请求消息。
步骤308：CPF实体根据步骤302中获取的终端的业务特征信息，以及终端的移动性模式能力信息，确定终端的第三移动性模式。
具体地，与步骤303中类似，CPF实体根据终端的移动性模式能力在CPF预存的移动性模式集合中选择终端能够支持的移动性模式的子集，并根据终端的业务特征信息在子集中选择一个适合终端的第三移动性模式。
例如，终端的业务特征信息为：周期性业务，通信周期为每30分钟收发一次数据。则CPF实体可确定终端的第三移动性模式为表3中的模式3，转移条件为：当会话建立后状态为SESSION CONTEXT ACTIVE，数据收发完毕之后转为SESSION CONTEXT SUSPEND，当有数据发送时又转为SESSION CONTEXT ACTIVE，当会话释放后转为SESSION CONTEXT INACTIVE。当终端的业务特征信息发生变化时，例如改变为：周期性业务，通信周期为每1天收发一次数据。则CPF可确定终端的会话移动性模式为表3中的模式1，转移条件为：当会话建立后状态为SESSION CONTEXT ACTIVE，数据收发完毕之后转为SESSION CONTEXT INACTIVE，当有数据发送时重新建立会话连接转为SESSION CONTEXT ACTIVE。
这里为终端选择第三移动性模式时，可以只考虑适合终端的业务移动性模式。
步骤309：CPF实体将选择的适合终端的第三移动性模式发送给RAN节点。
具体地，将终端的第三移动性模式对应的模式索引值发送给RAN节点，或者，直接发送终端的第三移动性模式中包括的参数。同时，将从终端的签约信息中获取的与移动性模式相关的一些参数配置发送给RAN节点，例如终端的周期性位置更新定时器。
步骤310：RAN节点根据终端的第三移动性模式，以及根据本地的配置策略为终端确定最终使用的第四移动性模式。
步骤311：RAN节点分别向终端和CPF实体发送为终端确定的最终使用的第四移动性模式。
需要说明的是，若终端只有附着过程，不需要连接建立的过程，则本方案只需要执行步骤301至步骤306，在后续终端需要做业务的时候，再执行步骤307到步骤311。
应用场景二：CPF实体包括具备MM功能的实体或具备SM功能的实体。
这种场景下，CPF实体的功能分为两个功能实体分别来实现，具备MM功能的实体可称为MM实体，具备SM功能的实体可称为SM实体。方法步骤如图4所示。
步骤401：终端向MM实体发送附着请求消息。
其中，附着请求消息中携带了终端的移动性模式能力的信息，用于表征终端能够支持哪些移动性模式。
步骤402：MM实体从用户签约数据库中获取终端的签约信息。
MM实体也可以从终端之前附着的其他MM实体获取终端的签约信息。本步骤是在MM实体不知终端的签约信息的前提下进行的，当然，如果MM实体已知终端的签约信息，则省略步骤402。
步骤403：MM实体获取终端的移动性事件历史统计信息，并根据终端的移动性事件历史统计信息和终端的移动性模式能力确定终端的第一移动性模式。
步骤404：MM实体将选择的适合终端的第一移动性模式发送给RAN节点。
上述步骤401至步骤404与上述步骤301至步骤304除了执行主体由CPF实体改为MM实体之外，其他内容相同，在此不再赘述。
步骤405：RAN节点根据终端的第一移动性模式，以及根据本地的配置策略为终端确定最终使用的第二移动性模式。
步骤406：RAN节点分别向终端和MM实体发送为终端确定的最终使用的第二移动性模式。
步骤407：终端向SM实体发送连接建立请求消息。
其中，连接建立请求消息中携带了终端的移动性模式能力的信息，用于 表征终端能够支持哪些移动性模式。
步骤408：SM实体从用户签约数据库中获取终端的签约信息。
或者，SM实体也可以从终端之前附着的其他SM实体获取终端的签约信息。本步骤是在SM实体不知终端的签约信息的前提下进行的，当然，如果SM实体已知终端的签约信息，则省略步骤408。终端的签约信息中包括了一些与终端的移动性模式相关的参数，包括终端的一些业务特征信息，例如，周期性业务指示、通信持续时间、通信周期、固定终端指示等业务参数，还有周期性位置更新定时器等移动性模式参数。
步骤409：SM实体是根据获取的终端的业务特征信息，以及终端的移动性模式能力信息，确定终端的第三移动性模式。
步骤410：SM实体将选择的适合终端的第三移动性模式发送给RAN节点。
步骤411：RAN节点根据终端的第三移动性模式，以及根据本地的配置策略为终端确定最终使用的第四移动性模式。
步骤412：RAN节点分别向终端和SM实体发送为终端确定的最终使用的第四移动性模式。
需要说明的是，若终端只有附着过程，不需要连接建立的过程，则本方案只需要执行步骤401至步骤406，在后续终端需要做业务的时候，再执行步骤407到步骤412。
本申请实施例还有另一种终端移动性模式的管理方法的实现方式，由RAN节点根据终端的应用场景来决定终端的移动性模式，具体流程如图5所示。
步骤501：CPF实体向RAN节点发送终端的移动性模式相关信息，RAN节点接收CPF实体发送的终端的移动性模式相关信息。
移动性模式相关信息包括以下信息中的一种或任意组合：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
其中，移动性模式能力信息包括终端能够支持的移动性模式，业务特征 信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
步骤502：RAN节点根据接收到的终端的移动性模式相关信息确定终端的移动性模式。
移动性模式包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域移动性管理配置信息。
具体地，RAN节点根据终端的移动性模式能力信息，确定终端支持的移动性模式；然后，RAN节点根据终端的移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，RAN节点根据终端的业务特征信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，RAN节点根据终端的所述业务特征信息和所述移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；RAN节点根据选择的至少一个移动性模式确定所述终端的移动性模式。
具体地，RAN节点根据终端的移动性模式相关信息确定终端的移动性模式之前，预先配置RAN节点能够支持的移动性模式集合，移动性模式集合包括至少一个移动性模式以及各个移动性模式分别对应的模式索引值。
RAN节点根据终端的移动性模式能力信息，确定移动性模式集合中终端能够支持的至少一个移动性模式；
RAN节点根据终端的移动性事件历史统计信息，在终端能够支持的至少一个移动性模式中选择与终端的移动性事件历史统计信息对应的移动性模式；或者，RAN节点根据终端的业务特征信息，在终端能够支持的至少一个移动性模式中选择与终端的业务特征信息对应的移动性模式。
步骤503：RAN节点将确定的移动性模式发送给终端。
具体地，RAN节点将移动性模式对应的模式索引值发送给终端；或者， RAN节点将移动性模式中包括的终端的移动性模式的配置信息发送给终端。
基于同一发明构思，参阅图6所示，本申请实施例中还提供了一种终端移动性模式的管理装置600，用以执行图2所示的终端移动性模式的管理方法。该终端移动性模式的管理装置600包括：获取单元601、确定单元602和发送单元603。其中：
获取单元601，用于获取终端的移动性模式相关信息；
确定单元602，用于根据获取单元601获取的终端的移动性模式相关信息，确定终端的第一移动性模式；
发送单元603，用于发送确定单元602确定的第一移动性模式给无线接入网络RAN节点，第一移动性模式用于RAN节点确定终端的第二移动性模式。
可选的，移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
其中，移动性模式能力信息包括终端能够支持的移动性模式，业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
可选的，确定单元602用于：
根据终端的移动性模式能力信息，确定终端能够支持的移动性模式；
根据终端的移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，根据终端的业务特征信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，根据终端的业务特征信息和移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；以及，
根据选择的至少一个移动性模式确定终端的第一移动性模式。
可选的，第一移动性模式和所述第二移动性模式均包括以下移动性管理 配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
可选的，移动性模式包括信令移动性模式和会话移动性模式中的至少一种；
信令移动性模式包括非接入层NAS信令移动性模式或无线资源控制RRC信令移动性模式。
基于同一发明构思，参阅图7所示，本申请实施例还提供一种终端移动性模式的管理装置700，用以执行图2所示的终端移动性模式的管理方法。该终端移动性模式的管理装置700包括接收单元701、确定单元702和发送单元703。其中：
接收单元701，用于接收控制面功能CPF实体发送的终端的第一移动性模式；
确定单元702，用于根据接收单元701接收的第一移动性模式，确定终端的第二移动性模式；
发送单元703，用于将确定单元702确定的第二移动性模式发送给终端。
可选的，确定单元702用于：
预先获取装置能够支持的移动性模式；
若装置能够支持第一移动性模式中包括的移动性管理配置信息，则将第一移动性模式确定为第二移动性模式；或者，
若装置不支持第一移动性模式中包括的移动性管理配置信息，则选择默认的移动性模式作为第二移动性模式。
可选的，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
可选的，连接状态包括信令连接状态和会话连接状态中的至少一种；
信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
基于同一发明构思，参阅图8所示，本申请实施例还提供另一种终端移动性模式的管理装置800，用以执行图5所示的终端移动性模式的管理方法。该终端移动性模式的管理装置800包括：接收单元801、确定单元802和发送单元803。其中：
接收单元801，用于接收控制面功能CPF实体发送的终端的移动性模式相关信息；
确定单元802，用于根据接收单元801接收的移动性模式相关信息，确定终端的移动性模式；
发送单元803，用于将确定单元802确定的移动性模式发送给终端。
可选的，移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
其中，移动性模式能力信息包括终端能够支持的移动性模式，业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
可选的，确定单元802用于：
根据终端的移动性模式能力信息，确定终端支持的移动性模式；
根据终端的移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，根据终端的业务特征信息，在终端能够支持的移动性模式中选择至少一个移动性模式；或者，根据终端的业务特征信息和移动性事件历史统计信息，在终端能够支持的移动性模式中选择至少一个移动性模式；
根据选择的至少一个移动性模式确定终端的移动性模式。
可选的，所述移动性模式包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
可选的，连接状态包括信令连接状态和会话连接状态中的至少一种；
信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
基于同一发明构思，参阅图9所示，本申请实施例还提供了一种终端900，用以执行图2所示的终端移动性模式的管理方法。该终端900包括：发送单元901、接收单元902和确定单元903。
发送单元901，用于向控制面功能CPF实体发送所述终端的移动性模式相关信息，所述移动性模式相关信息用于确定所述终端的第一移动性模式；
接收单元902，用于接收RAN节点发送的第二移动性模式；
确定单元903，用于根据所述第二移动性模式中包含的至少一个移动性模式，确定所述终端采用的移动性模式。
可选的，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
其中，所述移动性模式能力信息包括终端能够支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
基于同一发明构思，参阅图10所示，本申请实施例还提供了一种CPF实体1000，包括：收发器1001、处理器1002和存储器1003。其中，存储器1003用于存储一组程序，处理器1002用于调用存储器1003存储的程序以执行图2所示的终端移动性模式的管理方法。
处理器1002可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。
处理器1002还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑 器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。
存储器1003可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器1003也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器1003还可以包括上述种类的存储器的组合。
基于同一发明构思，参阅图11所示，本申请实施例还提供了另一种RAN节点1100，包括：收发器1101、处理器1102和存储器1103。其中，存储器1103用于存储一组程序，处理器1102用于调用存储器1103存储的程序以执行执行图2所示的终端移动性模式的管理方法。
处理器1102可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。
处理器1102还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。
存储器1103可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器1103也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英 文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器1103还可以包括上述种类的存储器的组合。
基于同一发明构思，参阅图12所示，本申请实施例还提供了另一种RAN节点1200，包括：收发器1201、处理器1202和存储器1203。其中，存储器1203用于存储一组程序，处理器1202用于调用存储器1203存储的程序以用以执行图5所示的终端移动性模式的管理方法。
处理器1202可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。
处理器1202还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。
存储器1203可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器1203也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器1203还可以包括上述种类的存储器的组合。
基于同一发明构思，参阅图13所示，本申请实施例还提供了另一种终端1300，包括：收发器1301、处理器1302和存储器1303。其中，存储器1303用于存储一组程序，处理器1302用于调用存储器1303存储的程序以执行用以执行图2所示的终端移动性模式的管理方法。
处理器1302可以是中央处理器(英文：central processing unit，缩写：CPU)， 网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。
处理器1302还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。
存储器1303可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器1303也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器1303还可以包括上述种类的存储器的组合。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (32)

  1. 一种终端移动性模式的管理方法，其特征在于，包括：
    控制面功能CPF实体获取终端的移动性模式相关信息；
    所述CPF实体根据所述终端的移动性模式相关信息，确定所述终端的第一移动性模式；
    所述CPF实体发送所述第一移动性模式给无线接入网络RAN节点，所述第一移动性模式用于所述RAN节点确定所述终端的第二移动性模式；
    其中，所述第一移动性模式和所述第二移动性模式中均包括移动性管理配置信息。
  2. 如权利要求1所述的方法，其特征在于，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
    其中，所述移动性模式能力信息包括终端支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
  3. 如权利要求2所述的方法，其特征在于，所述CPF实体根据所述终端的移动性模式相关信息，确定所述终端的所述第一移动性模式，包括：
    所述CPF实体根据所述终端的移动性模式能力信息，确定所述终端支持的移动性模式；
    所述CPF实体根据所述终端的移动性事件历史统计信息，在所述终端支持的移动性模式中选择移动性模式；或者，所述CPF实体根据所述终端的所述业务特征信息，在所述终端支持的移动性模式中选择移动性模式；或者，所述CPF实体根据所述终端的所述业务特征信息和所述移动性事件历史统计 信息，在所述终端支持的移动性模式中选择移动性模式。
  4. 如权利要求1-3任一所述的方法，其特征在于，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
  5. 如权利要求4所述的方法，其特征在于，所述连接状态包括信令连接状态和会话连接状态中的至少一种；
    所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
  6. 一种终端移动性模式的管理方法，其特征在于，包括：
    无线接入网络RAN节点接收控制面功能CPF实体发送的终端的第一移动性模式；
    所述RAN节点根据所述第一移动性模式，确定所述终端的第二移动性模式；
    所述RAN节点将确定的所述第二移动性模式发送给所述终端。
  7. 如权利要求6所述的方法，其特征在于，所述RAN节点根据所述第一移动性模式确定所述终端的第二移动性模式，包括：
    所述RAN节点预先获取所述RAN节点支持的移动性模式；
    若所述RAN节点支持所述第一移动性模式中包括的移动性管理配置信息，则所述RAN节点将所述第一移动性模式确定为所述第二移动性模式；或者，
    若所述RAN节点不支持第一移动性模式中包括的移动性管理配置信息，则所述RAN节点选择默认的移动性模式作为所述第二移动性模式。
  8. 如权利要求6或7所述的方法，其特征在于，所述第一移动性模式和所述第二移动性模式均包括以下中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
  9. 如权利要求6-8任一项所述的方法，其特征在于，所述连接状态包括信令连接状态和会话连接状态中的至少一种；
    所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
  10. 一种终端移动性模式的管理方法，其特征在于，包括：
    无线接入网络RAN节点接收控制面功能CPF实体发送的终端的移动性模式相关信息；
    所述RAN节点根据所述移动性模式相关信息，确定所述终端的移动性模式，所述移动性模式包括移动性管理配置信息；
    所述RAN节点将所述移动性模式发送给所述终端。
  11. 如权利要求10所述的方法，其特征在于，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
    其中，所述移动性模式能力信息包括终端支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
  12. 如权利要求10或11所述的方法，其特征在于，所述RAN节点根据所述终端的移动性模式相关信息，确定所述终端的移动性模式，包括：
    所述RAN节点根据所述终端的移动性模式能力信息，确定所述终端支持的移动性模式；
    所述RAN节点根据所述终端的移动性事件历史统计信息，在所述终端支持的移动性模式中选择移动性模式；或者，所述RAN节点根据所述终端的所述业务特征信息，在所述终端支持的移动性模式中选择移动性模式；或者，所述RAN节点根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端支持的移动性模式中选择一个移动性模式确定为最终选择的移动性模式。
  13. 如权利要求10-12任一所述的方法，其特征在于，所述移动性模式包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
  14. 如权利要求10-13任一项所述的方法，其特征在于，所述连接状态包括信令连接状态和会话连接状态中的至少一种；
    所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
  15. 一种终端移动性模式的管理方法，其特征在于，包括：
    终端向控制面功能CPF实体发送所述终端的移动性模式相关信息，所述移动性模式相关信息用于确定所述终端的第一移动性模式；
    所述终端接收RAN节点发送的第二移动性模式，所述第二移动性模式包括移动性管理配置信息；
    所述终端根据所述第二移动性模式确定所述终端移动性管理的配置信息。
  16. 如权利要求15所述的方法，其特征在于，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
    其中，所述移动性模式能力信息包括终端支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
  17. 一种终端移动性模式的管理装置，其特征在于，包括：
    获取单元，用于获取终端的移动性模式相关信息；
    确定单元，用于根据所述获取单元获取的终端的移动性模式相关信息，确定所述终端的第一移动性模式；
    发送单元，用于发送所述确定单元确定的所述第一移动性模式给无线接入网络RAN节点，所述第一移动性模式用于所述RAN节点确定所述终端的第二移动性模式。
  18. 如权利要求17所述的装置，其特征在于，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
    其中，所述移动性模式能力信息包括终端支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
  19. 如权利要求18所述的装置，其特征在于，所述确定单元用于：
    根据所述终端的移动性模式能力信息，确定所述终端支持的移动性模式；
    根据所述终端的移动性事件历史统计信息，在所述终端支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息，在所述终端支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端支持的移动性模式中选择移动性模式。
  20. 如权利要求17-19任一所述的装置，其特征在于，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
  21. 如权利要求17-20任一项所述的装置，其特征在于，所述连接状态包括信令连接状态和会话连接状态中的至少一种；
    所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
  22. 一种终端移动性模式的管理装置，其特征在于，包括：
    接收单元，用于接收控制面功能CPF实体发送的终端的第一移动性模式；
    确定单元，用于根据所述接收单元接收的所述第一移动性模式，确定所述终端的第二移动性模式；
    发送单元，用于将所述确定单元确定的所述第二移动性模式发送给所述终端。
  23. 如权利要求22所述的装置，其特征在于，所述确定单元用于：
    预先获取所述装置支持的移动性模式；
    若所述装置支持第一移动性模式中包括的移动性管理配置信息，则将所述第一移动性模式确定为所述第二移动性模式；或者，
    若所述装置不支持所述第一移动性模式中包括的移动性管理配置信息，则选择默认的移动性模式作为所述第二移动性模式。
  24. 如权利要求22或23所述的装置，其特征在于，所述第一移动性模式和所述第二移动性模式均包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
  25. 如权利要求22-24任一项所述的装置，其特征在于，所述连接状态包括信令连接状态和会话连接状态中的至少一种；
    所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
  26. 一种终端移动性模式的管理装置，其特征在于，包括：
    接收单元，用于接收控制面功能CPF实体发送的终端的移动性模式相关信息；
    确定单元，用于根据所述接收单元接收的所述移动性模式相关信息，确定所述终端的移动性模式；
    发送单元，用于将所述确定单元确定的所述移动性模式发送给所述终端。
  27. 如权利要求26所述的装置，其特征在于，所述移动性模式相关信息包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
    其中，所述移动性模式能力信息包括终端支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
  28. 如权利要求26或27所述的装置，其特征在于，所述确定单元用于：
    根据所述终端的移动性模式能力信息，确定所述终端支持的移动性模式；
    根据所述终端的移动性事件历史统计信息，在所述终端支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息，在所述终端支持的移动性模式中选择移动性模式；或者，根据所述终端的所述业务特征信息和所述移动性事件历史统计信息，在所述终端支持的移动性模式中选择移动性模式。
  29. 如权利要求26-28任一所述的装置，其特征在于，所述移动性模式包括以下移动性管理配置信息中的至少一种：连接状态，位置区列表，位置更新定时器，寻呼区域。
  30. 如权利要求26-29任一项所述的装置，其特征在于，所述连接状态包括信令连接状态和会话连接状态中的至少一种；
    所述信令连接状态包括非接入层NAS信令连接状态或无线资源控制RRC信令连接状态。
  31. 一种终端，其特征在于，包括：
    发送单元，用于向控制面功能CPF实体发送所述终端的移动性模式相关信息，所述移动性模式相关信息用于确定所述终端的第一移动性模式；
    接收单元，用于接收RAN节点发送的第二移动性模式；
    确定单元，用于根据所述第二移动性模式确定所述终端移动性管理的配置信息。
  32. 如权利要求31所述的终端，其特征在于，所述移动性模式相关信息 包括以下信息中的至少一种：移动性模式能力信息、业务特征信息和移动性事件历史统计信息；
    其中，所述移动性模式能力信息包括终端支持的移动性模式，所述业务特征信息包括终端的周期性业务指示、单次业务通信持续时间和业务周期中的至少一种，所述移动性事件历史统计信息包括终端在特定时间段发生切换或位置更新，或者，所述移动性事件历史统计信息包括在特定位置发生切换或位置更新，或者所述移动性事件历史统计信息包括在特定时间段或特定位置发生的移动速度类型。
PCT/CN2016/096443 2016-08-23 2016-08-23 一种终端移动性模式的管理方法及装置 WO2018035726A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
CN202110446352.XA CN113225754A (zh) 2016-08-23 2016-08-23 一种终端移动性模式的管理方法及装置
JP2019510771A JP7026675B2 (ja) 2016-08-23 2016-08-23 端末の移動性パターンを管理する方法及び機器
BR112019002990A BR112019002990A2 (pt) 2016-08-23 2016-08-23 método, aparelho, terminal, sistema, meio legível por computador e um produto de programa de computador para gerenciar padrão de mobilidade de terminal
CN201680085471.4A CN109076362B (zh) 2016-08-23 2016-08-23 一种终端移动性模式的管理方法及装置
EP16913750.2A EP3496445B1 (en) 2016-08-23 2016-08-23 Determination of a suitable mobility pattern for a terminal
KR1020197007523A KR102290689B1 (ko) 2016-08-23 2016-08-23 단말의 이동성 패턴을 관리하는 방법 및 장치
PCT/CN2016/096443 WO2018035726A1 (zh) 2016-08-23 2016-08-23 一种终端移动性模式的管理方法及装置
US16/283,324 US11533606B2 (en) 2016-08-23 2019-02-22 Method and apparatus for managing mobility pattern of terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/096443 WO2018035726A1 (zh) 2016-08-23 2016-08-23 一种终端移动性模式的管理方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/283,324 Continuation US11533606B2 (en) 2016-08-23 2019-02-22 Method and apparatus for managing mobility pattern of terminal

Publications (1)

Publication Number Publication Date
WO2018035726A1 true WO2018035726A1 (zh) 2018-03-01

Family

ID=61246046

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/096443 WO2018035726A1 (zh) 2016-08-23 2016-08-23 一种终端移动性模式的管理方法及装置

Country Status (7)

Country Link
US (1) US11533606B2 (zh)
EP (1) EP3496445B1 (zh)
JP (1) JP7026675B2 (zh)
KR (1) KR102290689B1 (zh)
CN (2) CN109076362B (zh)
BR (1) BR112019002990A2 (zh)
WO (1) WO2018035726A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110225512A (zh) * 2019-06-04 2019-09-10 浙江大学 一种蜂窝物联网的无线资源控制方法及系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108076488B (zh) * 2016-11-14 2021-01-05 华为技术有限公司 用于小区切换的方法、装置和系统
CN108617012B (zh) * 2017-01-03 2020-04-17 电信科学技术研究院 一种建立连接的方法及装置
US10749796B2 (en) * 2017-04-27 2020-08-18 At&T Intellectual Property I, L.P. Method and apparatus for selecting processing paths in a software defined network
CN109863784B (zh) * 2018-05-14 2021-08-20 Oppo广东移动通信有限公司 控制网络拥塞的方法、终端设备和网络设备
GB2606408A (en) * 2021-05-07 2022-11-09 Nec Corp Communication system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1446002A (zh) * 2002-03-15 2003-10-01 国际商业机器公司 对移动台进行位置管理的系统和方法、移动台和移动网络
CN104871608A (zh) * 2012-10-29 2015-08-26 阿尔卡特朗讯公司 分组移动系统中网络信令负载和/或用户设备功率消耗的优化
CN104980959A (zh) * 2015-07-13 2015-10-14 东莞理工学院 基于移动终端移动模式认知的网络切换优化方法及系统
CN105027649A (zh) * 2012-12-27 2015-11-04 瑞典爱立信有限公司 用于基于机器装置能力信息调整资源管理过程的方法和装置
CN105432118A (zh) * 2013-07-31 2016-03-23 高通股份有限公司 使用预测移动性调适移动设备行为

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2428236A1 (en) * 2003-05-08 2004-11-08 M-Stack Limited Apparatus and method of handling universal terrestrial radio access network radio resource control connecting messages in universal mobile telecommunications system user equipment
US8218512B2 (en) * 2006-06-14 2012-07-10 Toshiba America Research, Inc. Distribution of session keys to the selected multiple access points based on geo-location of APs
US7974228B2 (en) * 2008-01-07 2011-07-05 Alcatel-Lucent Usa Inc. Method of signaling-free idle mode mobility for an integrated 3GPP and 3GPP2 network
US8331319B2 (en) * 2009-06-19 2012-12-11 Clearwire Ip Holdings Llc Optimizing handovers in a communication network
JP5277210B2 (ja) * 2010-06-24 2013-08-28 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法及びリレーノード
EP2628344A1 (en) * 2010-10-11 2013-08-21 Telefonaktiebolaget L M Ericsson (publ) A method for associating a tracking area identity list with a user equipment in a wireless communications network
US8863256B1 (en) * 2011-01-14 2014-10-14 Cisco Technology, Inc. System and method for enabling secure transactions using flexible identity management in a vehicular environment
WO2013113137A1 (en) * 2012-01-30 2013-08-08 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for rrc switching
GB2504701A (en) * 2012-08-06 2014-02-12 Nec Corp Determining current state of a mobile device
ES2786003T3 (es) * 2012-09-18 2020-10-08 Alcatel Lucent Soporte de usuarios nómadas o fijos en una red móvil
US9160515B2 (en) * 2013-04-04 2015-10-13 Intel IP Corporation User equipment and methods for handover enhancement using scaled time-to-trigger and time-of-stay
US9474000B2 (en) * 2013-07-31 2016-10-18 Qualcomm Incorporated Handover and reselection searching using predictive mobility
KR102234979B1 (ko) * 2013-11-07 2021-04-02 삼성전자주식회사 무선 통신 시스템에서 이동성 관리를 위한 장치 및 방법
US10375646B2 (en) * 2014-04-18 2019-08-06 Apple Inc. Coordination between application and baseband layer operation
US9967838B2 (en) * 2014-11-21 2018-05-08 Apple Inc. Network synchronization for system configuration exchanges
US9591613B2 (en) * 2014-11-28 2017-03-07 Alcatel-Lucent Usa Inc. Adaptive paging using user equipment localization method in a network
US10354200B2 (en) * 2015-12-14 2019-07-16 Here Global B.V. Method, apparatus and computer program product for collaborative mobility mapping

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1446002A (zh) * 2002-03-15 2003-10-01 国际商业机器公司 对移动台进行位置管理的系统和方法、移动台和移动网络
CN104871608A (zh) * 2012-10-29 2015-08-26 阿尔卡特朗讯公司 分组移动系统中网络信令负载和/或用户设备功率消耗的优化
CN105027649A (zh) * 2012-12-27 2015-11-04 瑞典爱立信有限公司 用于基于机器装置能力信息调整资源管理过程的方法和装置
CN105432118A (zh) * 2013-07-31 2016-03-23 高通股份有限公司 使用预测移动性调适移动设备行为
CN104980959A (zh) * 2015-07-13 2015-10-14 东莞理工学院 基于移动终端移动模式认知的网络切换优化方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3496445A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110225512A (zh) * 2019-06-04 2019-09-10 浙江大学 一种蜂窝物联网的无线资源控制方法及系统

Also Published As

Publication number Publication date
CN113225754A (zh) 2021-08-06
EP3496445A4 (en) 2019-06-12
BR112019002990A2 (pt) 2019-05-14
KR20190039270A (ko) 2019-04-10
US11533606B2 (en) 2022-12-20
CN109076362B (zh) 2021-05-04
CN109076362A (zh) 2018-12-21
JP7026675B2 (ja) 2022-02-28
KR102290689B1 (ko) 2021-08-17
EP3496445B1 (en) 2021-11-24
JP2019525676A (ja) 2019-09-05
EP3496445A1 (en) 2019-06-12
US20190191297A1 (en) 2019-06-20

Similar Documents

Publication Publication Date Title
WO2018035726A1 (zh) 一种终端移动性模式的管理方法及装置
CA3045535C (en) Communication method, access network device, core network device, and user equipment
US11317451B2 (en) Session activation method, device, and system
JP2021520675A (ja) Ｒｒｃインアクティブ状態における測定の一時停止／再開
US10602475B2 (en) Method and system for device location management
WO2018137459A1 (zh) 通信的方法、终端和接入网设备
JP2021522743A (ja) 再開要求の拒否に伴うｕｅ挙動
JP2020504502A (ja) 不連続受信のための方法及び装置
CN112690021A (zh) 确定是否传送网络切片选择辅助信息的方法和装置
KR20140052397A (ko) 이동 통신 시스템에서 가상 머신 관리 장치 및 방법
CN110366855B (zh) 用户设备和用于无线通信网络的网络实体
US11588788B2 (en) Systems and methods for facilitating data transmission to internet of things devices
JP6668484B2 (ja) システム情報送信方法、システム情報更新方法、及びデバイス
US11601947B2 (en) Systems and methods for network slice selection according to application specific request
US11197243B1 (en) Systems and methods for acquiring network control data of a user equipment in cellular networks
CN111543030B (zh) 一种信息指示方法及装置、计算机存储介质
US20240040494A1 (en) Systems and methods for network slice modification by policy control function in a wireless network
TW201743640A (zh) 通信方法、核心網設備、接入網設備、以及終端設備
US20240089797A1 (en) Systems and methods for network-based detection of idle dedicated bearer resources
CN110708727B (zh) 搬迁管理方法及装置
WO2018058439A1 (zh) 一种支撑数据传输的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16913750

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019510771

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019002990

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20197007523

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016913750

Country of ref document: EP

Effective date: 20190304

ENP Entry into the national phase

Ref document number: 112019002990

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190213