WO2018127231A1 - 一种终端空闲态的处理方法及装置 - Google Patents

一种终端空闲态的处理方法及装置 Download PDF

Info

Publication number
WO2018127231A1
WO2018127231A1 PCT/CN2018/075589 CN2018075589W WO2018127231A1 WO 2018127231 A1 WO2018127231 A1 WO 2018127231A1 CN 2018075589 W CN2018075589 W CN 2018075589W WO 2018127231 A1 WO2018127231 A1 WO 2018127231A1
Authority
WO
WIPO (PCT)
Prior art keywords
user plane
function body
connection
ran
request message
Prior art date
Application number
PCT/CN2018/075589
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 US16/476,244 priority Critical patent/US10827538B2/en
Publication of WO2018127231A1 publication Critical patent/WO2018127231A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • 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
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a terminal idle state.
  • the Mobility Management Entity supports both Mobility Management (MM) functions and Session Management (SM).
  • the function, the MM function is, for example, an attachment, a tracking area update, etc.
  • the SM function is, for example, the establishment, modification, and deletion of a public data network connection.
  • Both the MM message and the SM message sent by the terminal UE are terminated at the MME and processed by the MME.
  • the MM (Mobility Management) function and the SM (Session Management) function exist as two independent functional modules, and the 5G network supports The control and forwarding separation of the gateway, the MM function and the SM function are separated.
  • the main functions of the MM function main body are user registration, UE unreachable discovery, location registration, UE state transition, connected state and inactive state mobility, UE mobility restriction, UE mobility management control, and anchor point. The choice, the establishment of the user plane path.
  • the main functions of the SM function body are packet forwarding and detection, session control, user plane function selection, and UE IP address allocation (connection type is IP). Signaling interaction between the MM function body and the SM function body is required to implement information interaction and collaboration.
  • the access network when the access network (RAN) finds that the UE is in an inactive state, it changes the state of the terminal and triggers the UE to enter the idle state.
  • the terminal state is also changed. And triggering the UE to enter the connected state from the idle state.
  • An object of the present disclosure is to provide a method and a device for processing a terminal idle state, so as to be able to effectively process a terminal idle state when the MM function is separated from the SM function, for example, to enable the UE to enter a connected state from an idle state.
  • the present disclosure provides a method for processing a terminal idle state, which is applied to an MM function body, including:
  • the requesting SM function body establishes a user plane connection for the UE.
  • the step of requesting the SM function body to establish a user plane connection for the UE according to the service request message includes:
  • the user plane connection activation request message carries the connection information of the RAN and the UE, and is used to indicate that the SM function body establishes a user plane connection for the UE.
  • the step of requesting the RAN to establish a connection with the UE and acquiring connection information between the RAN and the UE according to the service request message includes:
  • connection establishment request message Sending a connection establishment request message to the RAN according to the service request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • connection information between the RAN and the UE Obtaining connection information between the RAN and the UE according to the connection establishment complete message.
  • the step of requesting the SM function body to establish a user plane connection for the UE according to the service request message includes:
  • the connection established by the RAN with the UE includes a signaling connection, a user plane connection, and/or creating UE context information.
  • the service request message is initiated by the UE or initiated by the network.
  • the method before the step of receiving the service request message from the UE that is forwarded by the RAN, when the service request message is initiated by the network, the method further includes:
  • the SM function body receives a downlink data notification message sent by the SM function body; wherein, when the core network receives the downlink data packet, the SM function body matches the saved UE according to the data packet identifier corresponding to the downlink data packet Context information, if the relevant session information is found, the downlink data notification message is sent to the MM function body, otherwise the downlink data message is discarded, and the user plane configuration command is generated and sent to the RAN side UP function body;
  • the paging message After receiving the downlink data notification message, the paging message is sent to the UE, where the paging message is used to instruct the UE to initiate a service request.
  • the method further includes:
  • connection release request message a user plane connection deactivation request message to the session management SM function body, where the user plane connection deactivation request message is used to instruct the SM function body to modify the user plane path;
  • connection release instruction After receiving the user plane connection deactivation complete message, sending a connection release instruction to the RAN, the connection release instruction is used to instruct the RAN to perform connection release with the terminal UE.
  • connection release request message or the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the RAN-released connection with the UE includes a signaling connection, a user plane connection, and/or deleting UE context information.
  • the present disclosure further provides a method for processing a terminal idle state, which is applied to an SM function body, and includes:
  • the user plane connection activation request message is sent by the MM function body after requesting the RAN to establish a connection with the UE according to the received service request message from the UE that is forwarded by the RAN, and is carried therein.
  • the step of acquiring the connection information between the RAN and the UE according to the user plane connection activation request message includes:
  • connection establishment request message Sending a connection establishment request message to the RAN according to the user plane connection activation request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • connection information between the RAN and the UE Obtaining connection information between the RAN and the UE according to the connection establishment complete message.
  • the step of establishing a user plane connection for the UE according to the connection information and the SM related information of the RAN and the UE includes:
  • the user plane configuration command is generated and sent to the RAN side UP function body on the user plane path, where the user plane configuration command is used to indicate the RAN side UP function.
  • the main body performs the modification of the downlink user plane path;
  • the method further includes:
  • the step of establishing a user plane connection for the UE according to the connection information and the SM related information of the RAN and the UE includes:
  • the step of establishing a user plane connection for the UE according to the connection information and the SM related information of the RAN and the UE includes:
  • the method further includes:
  • the method further includes:
  • the method further includes:
  • the timer is started, and the timer is used to determine a lifetime of a user plane path established by the original UP function entity;
  • a user plane deletion instruction is generated and sent to the original UP function body, and the user plane deletion instruction is used to indicate that the original UP function body releases the user plane connection with the UE;
  • the method further includes:
  • the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the RAN-released connection with the UE includes a signaling connection, a user plane connection, and/or deleting UE context information.
  • the present disclosure further provides a processing device for a terminal idle state, which is applied to an MM function body, and includes:
  • a fifth receiving module configured to receive a service request message from the UE forwarded by the RAN
  • a requesting module configured to request the SM function body to establish a user plane connection for the UE according to the service request message.
  • the request module includes:
  • a requesting unit configured to request the RAN to establish a connection with the UE and obtain connection information between the RAN and the UE according to the service request message;
  • a first sending unit configured to send a user plane connection activation request message to the SM function body, where the user plane connection activation request message carries connection information of the RAN and the UE, and is used to indicate that the SM function body is The UE establishes a user plane connection.
  • the request unit includes:
  • a sending subunit configured to send a connection establishment request message to the RAN according to the service request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • a receiving subunit configured to receive a connection establishment complete message sent by the RAN
  • the obtaining subunit is configured to acquire connection information of the RAN and the UE according to the connection establishment complete message.
  • the request module includes:
  • a second sending unit configured to send a user plane connection activation request message to the SM function body according to the service request message, where the user plane connection activation request message is used to instruct the SM function body to request the RAN to establish
  • the connection of the UE acquires connection information between the RAN and the UE, and establishes a user plane connection for the UE.
  • the connection established by the RAN with the UE includes a signaling connection, a user plane connection, and/or creating UE context information.
  • the service request message is initiated by the UE or initiated by the network.
  • the method further includes:
  • a sixth receiving module configured to receive a downlink data notification message sent by the SM function body, where, when the core network receives the downlink data packet, the SM function body is configured according to the data packet corresponding to the downlink data packet The identifier of the message matches the saved UE context information. If the related session information is found, the downlink data notification message is sent to the MM function body. Otherwise, the downlink data packet is discarded, and the user plane configuration command is generated and sent.
  • RAN side UP function body configured to receive a downlink data notification message sent by the SM function body, where, when the core network receives the downlink data packet, the SM function body is configured according to the data packet corresponding to the downlink data packet The identifier of the message matches the saved UE context information. If the related session information is found, the downlink data notification message is sent to the MM function body. Otherwise, the downlink data packet is discarded, and the user plane configuration command is generated and sent.
  • RAN side UP function body configured to receive a downlink
  • the fifth sending module is configured to send a paging message to the UE after receiving the downlink data notification message, where the paging message is used to instruct the UE to initiate a service request.
  • the device further includes:
  • a first receiving module configured to receive a connection release request message sent by the access network RAN
  • a first sending module configured to send a user plane connection deactivation request message to the SM function body according to the connection release request message, where the user plane connection deactivation request message is used to instruct the SM function body to modify the user plane path;
  • a second receiving module configured to receive a user plane connection deactivation completion message sent by the SM function body
  • a second sending module configured to send a connection release command to the RAN after receiving the user plane connection deactivation complete message, where the connection release instruction is used to instruct the RAN to perform connection release with the UE.
  • connection release request message or the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the RAN-released connection with the UE includes a signaling connection, a user plane connection, and/or deleting UE context information.
  • the present disclosure further provides a processing apparatus for a terminal idle state, which is applied to an SM function body, and includes:
  • a seventh receiving module configured to receive a user plane connection activation request message sent by the MM function body
  • An obtaining module configured to obtain connection information between the RAN and the UE according to the user plane connection activation request message
  • a establishing module configured to establish a user plane connection for the UE according to the connection information of the RAN and the UE and the SM related information.
  • the user plane connection activation request message is sent by the MM function body after requesting the RAN to establish a connection with the UE according to the received service request message from the UE that is forwarded by the RAN, and is carried therein.
  • the obtaining module includes:
  • a third sending unit configured to send a connection establishment request message to the RAN according to the user plane connection activation request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • a first receiving unit configured to receive a connection establishment complete message sent by the RAN
  • an obtaining unit configured to acquire connection information of the RAN and the UE according to the connection establishment complete message.
  • the establishing module includes:
  • a first determining unit configured to determine, according to the connection information of the RAN and the UE and the SM related information, that the user plane path of the UE is unchanged;
  • a fourth sending unit configured to: after determining that the user plane path of the UE is unchanged, generate and send a user plane configuration command to the RAN side UP function body on the user plane path, where the user plane configuration command is used Instructing the RAN side UP function body to perform modification of a downlink user plane path;
  • the second receiving unit is configured to receive a user plane modification complete message sent by the RAN side UP function body.
  • the device further includes:
  • the sixth sending module is configured to send a user plane connection completion message to the MM function body.
  • the establishing module includes:
  • a second determining unit configured to determine, according to the connection information of the RAN and the UE and the SM related information, a new user plane path that is reselected by the UE;
  • a fifth sending unit configured to generate and send a user plane configuration command to the new RAN side UP function body on the new user plane path, where the user plane configuration command is used to indicate that the new RAN side UP function body establishes a route or Forwarding rules
  • a sixth sending unit configured to send a user plane modification request message to the original RAN side UP function body on the original user plane path of the UE, where the user plane modification request message is used to indicate that the original RAN side UP function body performs User plane path modification;
  • a third receiving unit configured to receive a user plane setup complete message sent by the new RAN side UP function body, and receive a user plane modification complete message sent by the original RAN side UP function body.
  • the establishing module includes:
  • a third determining unit configured to determine, according to the connection information of the RAN and the UE and the SM related information, a new user plane path that is reselected by the UE;
  • a seventh sending unit configured to generate and send a user plane configuration command to the new UP function body and the DN side UP function body on the new user plane path, where the user plane configuration instruction is used to indicate that the new UP function body is established Routing or forwarding the rule, and instructing the DN side UP function body to perform the user plane path modification, and forwarding the received data packet sent to the UE to the new UP function body;
  • the fourth receiving unit is configured to receive a user plane establishment completion message sent by the new UP function body, and receive a user plane modification completion message sent by the DN side UP function body.
  • the device further includes:
  • a seventh sending module configured to generate and send a user plane deletion command to the original UP function body on the original user plane path of the UE, where the user plane deletion instruction is used to indicate that the original UP function body releases the UE User plane connection;
  • the eighth receiving module is configured to receive a user plane deletion completion message sent by the original UP function body.
  • the device further includes:
  • An eighth sending module configured to generate and send a user plane configuration command to the original UP function body on the original user plane path of the UE, where the user plane configuration command is used to indicate that the original UP function body establishes a user plane path, Forwarding the received data packet to the DN side UP function body;
  • the ninth receiving module is configured to receive a user plane modification complete message sent by the original UP function body.
  • the device further includes:
  • the opening module is configured to enable a timer, where the timer is used to determine a lifetime of a user plane path established by the original UP function body;
  • a ninth sending module configured to: when the timer expires, generate and send a user plane deletion instruction to the original UP function body, where the user plane deletion instruction is used to indicate that the original UP function body releases the UE User plane connection;
  • the tenth receiving module is configured to receive a user plane deletion completion message sent by the original UP function body.
  • the device further includes:
  • a third receiving module configured to receive a user plane connection deactivation request message sent by the MM function body
  • the third sending module is configured to generate and send a user plane configuration command to the RAN side UP function body according to the user plane connection deactivation request message, where the user plane configuration command is used to indicate that the RAN side UP function body performs downlink Modification of the user plane path;
  • a fourth receiving module configured to receive a user plane modification completion message sent by the RAN side UP function body
  • the fourth sending module is configured to send a user plane connection deactivation completion message to the MM function body according to the user plane modification completion message.
  • the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the RAN-released connection with the UE includes a signaling connection, a user plane connection, and/or deleting UE context information.
  • the present disclosure provides a processing apparatus for a terminal idle state, which is applied to an MM function body, including: a processor, a memory, and a computer program stored on the memory and operable on the processor, The steps in the above-described processing method applied to the terminal idle state of the MM function body are implemented when the computer program is executed by the processor.
  • the present disclosure provides a method for processing a terminal idle state, which is applied to an SM function body, a processor, a memory, and a computer program stored on the memory and operable on the processor, the computer program The steps in the above-described processing method applied to the terminal idle state of the SM function body when executed by the processor.
  • the present disclosure provides a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the processing of the terminal idle state applied to the MM function body The steps in the method.
  • the present disclosure provides a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the processing of the terminal idle state applied to the SM function body The steps in the method.
  • the method for processing the terminal idle state of the present disclosure in the case that the MM function is separated from the SM function, the UE can enter the idle state by using the signaling interaction between the MM function body and the SM function body, and when the UE enters the idle state, The connection between the RAN and the UE is released, and the user plane connection in the core network is maintained, which is beneficial to the fast response of the service.
  • the user plane connection can also be established for the UE, so that the UE enters the connection state from the idle state, and reduces the control plane and the user plane. Inter-signaling overhead, shortening the delay into the connected state, and so on.
  • FIG. 1 is a flow chart showing a processing method of a terminal idle state in the first embodiment of the present disclosure.
  • FIG. 2 shows a flow chart of a RAN triggering a UE to enter an idle state in a specific example in the first embodiment of the present disclosure.
  • FIG. 3 is a flow chart showing a method of processing a terminal idle state according to a second embodiment of the present disclosure.
  • FIG. 4 is a flow chart showing a method of processing a terminal idle state in the third embodiment of the present disclosure.
  • 5A and 5B are flowcharts showing two types of network initiated service requests in the third embodiment of the present disclosure.
  • FIG. 6 is a flowchart showing a method of processing a terminal idle state according to a fourth embodiment of the present disclosure.
  • FIGS. 7A-7J are flowcharts showing a UE entering a connected state from an idle state in a specific example in the fourth embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram showing the structure of a processing apparatus for a terminal idle state according to a fifth embodiment of the present disclosure.
  • FIG. 9 is a second schematic structural diagram of a processing apparatus for a terminal idle state according to a fifth embodiment of the present disclosure.
  • FIG. 10 is a third schematic structural diagram of a processing apparatus for a terminal idle state according to a fifth embodiment of the present disclosure.
  • FIG. 11 is a fourth schematic structural diagram of a processing apparatus for a terminal idle state according to a fifth embodiment of the present disclosure.
  • FIG. 12 is a block diagram showing the structure of an MM function main body of a sixth embodiment of the present disclosure.
  • Fig. 13 is a view showing the structure of an SM functional main body of a seventh embodiment of the present disclosure.
  • a first embodiment of the present disclosure provides a method for processing a terminal idle state, which is applied to a mobility management MM function body, and includes the following steps 101 to 104, which are described in detail below.
  • Step 101 Receive a connection release request message sent by the access network RAN.
  • the connection release request message is sent to the MM function body, so that the MM function body requests the SM function body to modify the user plane path of the UE. , the UE is put into an idle state.
  • the connection release request message may carry at least one of the following information: the UE identifier, the MM context identifier, the base station identifier, and the reason for the release (eg, user inactivity, that is, the system saves due to the user's long-term traffic being below a certain threshold. Resource-initiated release) and so on.
  • the reason for the release eg, user inactivity, that is, the system saves due to the user's long-term traffic being below a certain threshold. Resource-initiated release
  • Step 102 Send a user plane connection deactivation request message to the SM function body according to the connection release request message.
  • the user plane connection deactivation request message is used to indicate that the SM function body modifies the user plane path, and may carry at least one of the following information: the UE identifier, the MM context identifier, the base station identifier, and the reason for the release ( For example, user inactivity) and so on.
  • the user plane connection deactivation request message may also include a session modification request message.
  • the SM function body After receiving the user plane connection deactivation request message, the SM function body generates and sends a user plane configuration command to the RAN side UP function body, so that the RAN side UP function body performs according to the user plane configuration instruction. Modification of the downstream user plane path.
  • the user plane configuration command is used, for example, to instruct the RAN side UP function body to report the SM function body when receiving the downlink data message.
  • the RAN side UP function body is specifically a user plane connected to the RAN in the core network.
  • Step 103 Receive a user plane connection deactivation completion message sent by the SM function body.
  • the SM function body sends a user plane connection deactivation completion message to the MM function body.
  • Step 104 After receiving the user plane connection deactivation completion message, send a connection release instruction to the RAN.
  • the connection release instruction is used to instruct the RAN to perform connection release with the UE.
  • the RAN Upon receiving the connection release command, the RAN performs a connection release with the UE.
  • the connection with the UE released by the RAN may include: a signaling connection, a user plane connection, and/or deletion of UE context information, and the like.
  • the RAN may notify the UE and send a connection release complete message to the MM function body. In this way, the network will consider the UE to enter an idle state.
  • the process in which the RAN triggers the UE to enter an idle state includes the following steps:
  • Step 201 When it is found that the signaling connection and the user plane connection of the UE need to be released, the RAN sends a connection release request message to the MM function body.
  • Step 202 After receiving the connection release request message, the MM function body sends a user plane connection deactivation request message to the SM function body.
  • Step 203 The SM function body sends a user plane modification request message to the RAN side UP function body according to the user plane connection deactivation request message, where the user plane modification request message carries the user plane configuration instruction generated by the SM function body.
  • Step 204 The RAN side UP function body performs the modification of the downlink user plane path according to the user plane configuration instruction, and sends the user plane modification completion message to the SM function body after the modification;
  • Step 205 After receiving the user plane modification complete message, the SM function body sends a user plane connection deactivation completion message to the MM function body.
  • Step 206 After receiving the user plane connection deactivation completion message, the MM function body sends a connection release instruction to the RAN;
  • Step 207 The RAN performs a connection release with the UE according to the connection release instruction.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or creation of UE context information.
  • Step 208 After releasing the connection with the UE, the RAN sends a connection release complete message to the MM function main body; at this point, the network considers the UE to enter an idle state.
  • the UE in the case that the MM function is separated from the SM function, the UE can enter the idle state by using the signaling interaction between the MM function body and the SM function body, and when the UE enters the idle state, In the state, the connection between the RAN and the UE is released, and the user plane connection in the core network is maintained, which is beneficial to the fast response of the service.
  • a second embodiment of the present disclosure provides a method for processing a terminal idle state, which is applied to an SM function body, and includes the following steps 301 to 304, which are described in detail below.
  • Step 301 Receive a user plane connection deactivation request message sent by the MM function body.
  • the connection release request message is sent to the MM function body, so that the MM function body requests the SM function body to modify the user plane path of the UE. And send a user plane connection deactivation request message to the SM function body.
  • the user plane connection deactivation request message is used to indicate that the SM function body modifies the user plane path, and may carry at least one of the following information: the UE identifier, the MM context identifier, the base station identifier, and the reason for the release (eg, user inactivity), and the like. .
  • the user plane connection deactivation request message may also include a session modification request message.
  • Step 302 Generate and send a user plane configuration command to the RAN side UP function body according to the user plane connection deactivation request message.
  • the user plane configuration command is used to indicate that the RAN side UP function body performs the modification of the downlink user plane path.
  • the user plane configuration command may indicate that the RAN side UP function body reports the SM function body when receiving the downlink data message.
  • Step 303 Receive a user plane modification complete message sent by the RAN side UP function body.
  • the RAN side UP function body may send the user plane modification completion message to the SM function body.
  • Step 304 Send a user plane connection deactivation completion message to the MM function body according to the user plane modification completion message.
  • the MM function body may send a connection release request message to the RAN to instruct the RAN to perform connection release with the UE.
  • the connection with the UE released by the RAN may include: a signaling connection, a user plane connection, and/or deletion of UE context information, and the like.
  • the UE in the case that the MM function is separated from the SM function, the UE can enter the idle state by using the signaling interaction between the MM function body and the SM function body, and when the UE enters the idle state, In the state, the connection between the RAN and the UE is released, and the user plane connection in the core network is maintained, which is beneficial to the fast response of the service.
  • a third embodiment of the present disclosure provides a method for processing a terminal idle state, which is applied to an MM function body, and includes the following steps 401 to 402, which are described in detail below.
  • Step 401 Receive a service request message from the UE forwarded by the RAN.
  • the service request message may carry at least one of the following information: a UE identifier, an MM context identifier, and a base station identifier.
  • the service request message may be initiated by the UE or initiated by the network.
  • the service request message may be sent to the RAN autonomously and forwarded to the MM function body via the RAN.
  • the UE sending the service request message may also receive the paging message sent by the network side.
  • the method for processing the terminal idle state of the embodiment of the present disclosure further includes:
  • the SM function body matches the saved UE context according to the data packet identifier corresponding to the downlink data packet, and if the related session information is found, the downlink data notification is sent. The message is sent to the MM function body. Otherwise, the downlink data packet is discarded.
  • the user plane configuration command is generated and sent to the RAN side UP function body of the data network to complete the configuration of the routing or forwarding rule (ie, the downlink data packet is discarded).
  • the paging message is used to indicate that the UE initiates a service request, that is, sends a service request message to the MM function body.
  • Step 402 The SM functional entity is requested to establish a user plane connection for the UE according to the service request message.
  • the MM function body requests the SM function body to establish a user plane connection for the UE according to the service request message.
  • Method 1 MM function body handles connection request
  • the MM function body requests the SM function body to establish a user plane connection for the UE according to the service request message:
  • the MM function body requests the RAN to establish a connection with the UE and obtain connection information between the RAN and the UE according to the service request message. Then, the MM function body sends a user plane connection activation request message to the SM function body.
  • the user plane connection activation request message carries the connection information of the RAN and the UE, and is used to indicate that the SM function entity establishes a user plane connection for the UE.
  • the process of requesting the RAN to establish a connection with the UE and obtain the connection information between the RAN and the UE according to the service request message is:
  • the MM function body sends a connection establishment request message to the RAN according to the service request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE; and then, the MM function body receives the connection establishment sent by the RAN. The message is completed. Finally, the MM function body obtains connection information between the RAN and the UE according to the connection establishment complete message.
  • Method 2 The SM function body processes the connection request
  • the MM function body requests the SM function body to establish a user plane connection for the UE according to the service request message:
  • the MM function body directly sends a user plane connection activation request message to the SM function body according to the service request message, where the user plane connection activation request message is used to indicate that the SM function body requests the RAN to establish a connection with the UE, and acquire the RAN. Connection information with the UE and establishing a user plane connection for the UE.
  • the connection established by the RAN with the UE may include a signaling connection, a user plane connection, and/or creation of UE context information and the like.
  • the method for processing the idle state of the terminal further includes:
  • connection release request message a user plane connection deactivation request message to the session management SM function body, where the user plane connection deactivation request message is used to instruct the SM function body to modify the user plane path;
  • connection release instruction After receiving the user plane connection deactivation complete message, sending a connection release instruction to the RAN, the connection release instruction is used to instruct the RAN to perform connection release with the terminal UE (refer to the first implementation for a specific implementation process) The contents described in the example).
  • connection release request message or the user plane connection deactivation request message may carry at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or deletion of UE context information.
  • a network initiated service request process includes the following steps:
  • Step 501 The RAN side UP function body reports the data packet identifier to the SM function body.
  • the core network that is, the RAN side UP function body receives the downlink data packet
  • the downlink data is buffered because there is no downlink user plane path. Transmitting the downlink data packet to obtain the data packet identifier, and then reporting the data packet identifier to the SM function body;
  • Step 502 The SM function body matches the saved UE context information according to the data packet identifier; if the related session information is found, step 503 is performed, otherwise step 504 is performed;
  • Step 503 The SM function body sends a downlink data notification message DDN to the MM function body.
  • Step 504 The SM function body determines to discard the downlink data packet, and generates and sends a user plane configuration command to the RAN side UP function body to complete the configuration of the routing or forwarding rule (ie, discarding the downlink data packet);
  • Step 505 After receiving the DDN, the MM function body sends a DDN ACK to the SM function body.
  • Step 506 The MM function body sends a paging message to the RAN;
  • Step 507 The RAN sends the paging message to the UE, so that the UE initiates a service request.
  • another network initiated service request process (based on a Software Defined Network (SDN), using the OpenFlow protocol) includes the following steps:
  • Step 511 The RAN side UP function body sends a Packet-in message to the SM function body.
  • the core network that is, the RAN side UP function body receives the downlink data packet
  • the downlink data is buffered because there is no downlink user plane path.
  • the packet is sent, and the entire downlink data packet is sent as a packet-in message to the SM function body;
  • Step 512 The SM function body matches the saved UE context information according to the Packet-in message; if the relevant session information is found, step 513 is performed, otherwise step 514 is performed;
  • Step 513 The SM function body sends a DDN to the MM function body.
  • Step 514 The SM function body determines to discard the downlink data packet, and generates a corresponding flow entry, and sends a Packet-out message to the RAN side UP function body to configure a flow entry (ie, discarding the downlink data packet);
  • Step 515 After receiving the DDN, the MM function body sends a DDN ACK to the SM function body.
  • Step 516 The MM function body sends a paging message to the RAN;
  • Step 517 The RAN sends the paging message to the UE, so that the UE initiates a service request.
  • the processing method of the terminal idle state of the third embodiment of the present disclosure in the case that the MM function is separated from the SM function, by means of signaling interaction between the MM function body and the SM function body, a user plane connection can be established for the UE, and the UE is idle.
  • the state enters the connected state, reducing the signaling overhead between the control plane and the user plane, and shortening the delay into the connected state.
  • a fourth embodiment of the present disclosure provides a method for processing a terminal idle state, which is applied to an SM function body, and includes the following steps 601 to 603, which are described in detail below.
  • Step 601 Receive a user plane connection activation request message sent by the MM function body.
  • the MM function body may directly send the user plane connection activation request message to the SM function body according to the service request message, to indicate the SM.
  • the functional entity requests the RAN to establish a connection with the UE, and may also send the user plane connection activation request message after requesting the RAN to establish a connection with the UE according to the received service request message from the UE that is forwarded by the RAN.
  • the service request message or the user plane connection activation request message may carry at least one of the following information: a UE identifier, an MM context identifier, and a base station identifier.
  • Step 602 Acquire connection information between the RAN and the UE according to the user plane connection activation request message.
  • connection between the RAN and the UE may be requested by the MM function body, or may be requested by the SM function body.
  • the user plane connection activation request message in the step 602 is specifically that the MM function body requests the service request message from the UE that is forwarded by the RAN.
  • the RAN is sent after establishing a connection with the UE, and carries the connection information of the RAN and the UE.
  • the step 602 may be specifically:
  • connection establishment request message Sending a connection establishment request message to the RAN according to the user plane connection activation request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • connection information between the RAN and the UE is obtained.
  • the connection established by the RAN with the UE may include a signaling connection, a user plane connection, and/or creation of UE context information, and the like.
  • Step 603 Establish a user plane connection for the UE according to the connection information of the RAN and the UE and the SM related information.
  • the SM function body when establishing a user plane connection for the UE, may be based on the connection information of the RAN and the UE and the SM related information, and may also refer to other auxiliary information, such as service requirements, Node load, link congestion, etc. (can be a combination of factors, or a certain factor).
  • the SM related information may include at least UE current location information.
  • the user interface connection established by the SM function body for the UE may be at least the following four, as described in detail below.
  • the first type the user plane path of the UE is unchanged.
  • the process of establishing a user plane connection for the UE by the SM function body is:
  • the SM function body determines, according to the connection information of the RAN and the UE and the SM related information (including the current location information of the UE), that the user plane path of the UE is unchanged;
  • the SM function body After determining that the user plane path of the UE is unchanged, the SM function body generates and sends a user plane configuration command to the RAN side UP function body on the user plane path, where the user plane configuration command is used to indicate the RAN side.
  • the UP function body performs the modification of the downlink user plane path, that is, when receiving the downlink data packet, it is sent according to the routing or forwarding rule;
  • the SM function body receives the user plane modification completion message sent by the RAN side UP function body.
  • the RAN side UP function body is specifically a user plane connected to the RAN in the core network.
  • the first case is applicable to the UE autonomously initiating a service request, and is also applicable to a network initiated service request.
  • the SM function body may also send a user plane connection completion message to the MM function body to complete establishing a user plane connection for the UE. .
  • the SM function body determines, according to the connection information of the RAN and the UE and the SM related information (including the current location information of the UE), a new user plane path that is reselected by the UE;
  • the SM function body generates and sends a user plane configuration command to the new RAN side UP function body on the new user plane path, where the user plane configuration command is used to indicate that the new RAN side UP function body establishes a routing or forwarding rule, that is, The received uplink data packet sent to the UE is routed or converted to the original RAN side UP function body (uplink routing or forwarding rule); and the SM function body sends the user plane modification request message to the original user plane path of the UE.
  • the original RAN side UP function body, the user plane modification request message is used to indicate that the original RAN side UP function body performs user plane path modification, that is, the downlink data packet sent to the UE is received or converted to the new RAN side.
  • UP functional body downlink routing or forwarding rules
  • the SM function body receives the user plane establishment completion message sent by the new RAN side UP function body, and receives the user plane modification completion message sent by the original RAN side UP function body.
  • the new RAN side UP function body is specifically a user plane connected to the RAN on the new user plane path in the core network.
  • the original RAN side UP function body is specifically a user plane connected to the RAN on the original user plane path in the core network. This second case applies to network initiated business requests.
  • the process of establishing a user plane connection for the UE by the SM function body is:
  • the SM function body determines, according to the connection information of the RAN and the UE and the SM related information (including the current location information of the UE), a new user plane path that is reselected by the UE;
  • the SM function body generates and sends a user plane configuration command to the new UP function body and the DN side UP function body on the new user plane path, where the user plane configuration instruction is used to indicate that the new UP function body establishes a routing or forwarding rule. And instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data packet sent to the UE to the new UP function body;
  • the SM function body receives the user plane establishment completion message sent by the new UP function body, and receives the user plane modification completion message sent by the DN side UP function body.
  • the new UP function body specifically includes a new RAN side UP function body and other UP function bodies on the new user plane path in the core network.
  • the DN side UP function body is specifically a user plane connected to the data network DN on the new user plane path in the core network.
  • the third case is applicable to the UE autonomously initiating a service request, and is also applicable to a network initiated service request.
  • the SM function body may also generate and send a user plane deletion.
  • the user plane deletion instruction is used to indicate that the original UP function body releases the user plane connection with the UE, and receives the user plane deletion completed by the original UP function body. Message.
  • the process for the SM function body to establish a user plane connection for the UE is:
  • the SM function body determines, according to the connection information of the RAN and the UE and the SM related information (including the current location information of the UE), a new user plane path that is reselected by the UE;
  • the SM function body generates and sends a user plane configuration command to the new UP function body and the DN side UP function body on the new user plane path, where the user plane configuration instruction is used to indicate that the new UP function body establishes a routing or forwarding rule. And instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data packet sent to the UE to the new UP function body;
  • the SM function body receives the user plane establishment completion message sent by the new UP function body, and receives the user plane modification completion message sent by the DN side UP function body.
  • the SM function body may also generate and send a user plane configuration.
  • the command is sent to the original UP function body on the original user plane path of the UE, and the user plane configuration command is used to indicate that the original UP function body establishes a user plane path, and forwards the received data packet to the DN side UP function body.
  • receiving the user plane modification completion message sent by the original UP function body is also generated and send a user plane configuration.
  • the SM function body may further enable a timer, where the timer is used to determine the lifetime of the user plane path established by the original UP function body.
  • a user plane deletion instruction is generated and sent to the original UP function body, and the user plane deletion instruction is used to indicate that the original UP function body releases the user plane connection with the UE, and receives the original UP function body and sends the The user plane deletes the completion message.
  • the method for processing the idle state of the terminal may further include:
  • the user plane connection deactivation completion message is sent to the MM function body according to the user plane modification completion message (for details, refer to the content described in the second embodiment).
  • the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or deletion of UE context information.
  • the UE initiates a service request autonomously, the user plane path of the UE is unchanged, and the MM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 701 The UE sends a service request message to the RAN.
  • Step 702 The RAN forwards the service request message to the MM function body.
  • Step 703 After receiving the service request message, the MM function body updates the UE location information and sends a connection setup request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and a UE-related establishment ( Context) information;
  • Step 704 The RAN performs connection establishment with the UE.
  • Step 705 After the RAN is established, send a connection establishment complete message to the MM function body.
  • Step 706 After receiving the connection establishment complete message, the MM function body sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 707 The SM function body determines that the user plane path of the UE is unchanged according to the SM related information and the current location information of the UE, and generates and sends a user plane configuration command (transmitted by using a user plane modification request message) to the RAN side UP function body, Instructing the RAN-side UP function body to perform the modification of the downlink user plane path, that is, when receiving the downlink data packet, sending according to the routing or forwarding rule;
  • Step 708 The RAN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 709 After receiving the user plane modification complete message, the SM function body sends a user plane connection completion message to the MM function body to complete establishing a user plane connection for the UE.
  • the UE initiates a service request, and the user plane path of the UE is unchanged, and the SM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 711 The UE sends a service request message to the RAN.
  • Step 712 The RAN forwards the service request message to the MM function body.
  • Step 713 After receiving the service request message, the MM function body updates the UE location information and sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 714 The SM function body sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, at least including a signaling connection, a user plane connection, and creating UE related (context) information; the message may be directly sent to the RAN. Can be forwarded by the MM functional entity or other network elements;
  • Step 715 The RAN performs connection establishment with the UE.
  • Step 716 After the RAN is established, the connection establishment completion message is sent to the SM function main body; the message may be directly sent to the SM function main body, or may be forwarded by the MM function main body or other network element;
  • Step 717 The SM function body determines, according to the SM related information and the current location information of the UE, that the user plane path of the UE is unchanged, and generates and sends a user plane configuration command (transmitted by using a user plane modification request message) to the RAN side UP function body, Instructing the RAN-side UP function body to perform the modification of the downlink user plane path, that is, when receiving the downlink data packet, sending according to the routing or forwarding rule;
  • Step 718 The RAN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 719 After receiving the user plane modification complete message, the SM function body sends a user plane connection completion message to the MM function body to complete establishing a user plane connection for the UE.
  • the UE initiates a service request
  • the user plane path of the UE changes
  • the MM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 721 The UE sends a service request message to the RAN.
  • Step 722 The RAN forwards the service request message to the MM function body.
  • Step 723 After receiving the service request message, the MM function body updates the UE location information and sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and a UE-related establishment ( Context) information;
  • Step 724 The RAN performs connection establishment with the UE.
  • Step 725 After the RAN is established, send a connection establishment complete message to the MM function body.
  • Step 726 After receiving the connection establishment complete message, the MM function body sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 727 The SM function body determines, according to the SM related information, the current location information of the UE, the service requirement, the node load, the congestion degree of the link, etc., a new user plane path that is reselected for the UE, and generates and sends a user plane configuration command to the
  • the new UP function body and the DN side UP function body on the new user plane path that is, the user plane establishment request message is sent to the new UP function body and the user plane modification request message is sent to the DN side UP function body, and the user plane configuration instruction is used for Instructing the new UP function body to establish a routing or forwarding rule, and instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data message sent to the UE to the new UP function body;
  • Step 728 The new UP function body sends a user plane establishment completion message to the SM function body, and the DN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 729 The SM function body generates and sends a user plane deletion command (transmitted by the user plane deletion request message) to the original UP function body, to indicate that the original UP function body releases the user plane connection with the UE;
  • Step 7210 The original UP function body sends a user plane deletion completion message to the SM function body.
  • Step 7211 After receiving the user plane deletion complete message, the SM function body sends a user plane connection completion message to the MM function body.
  • the UE initiates a service request
  • the user plane path of the UE changes
  • the SM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 731 The UE sends a service request message to the RAN.
  • Step 732 The RAN forwards the service request message to the MM function body.
  • Step 733 After receiving the service request message, the MM function body updates the UE location information and sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 734 The SM function body sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and UE related (context) information; the message may be directly sent to the RAN. Can be forwarded by the MM functional entity or other network elements;
  • Step 735 The RAN performs connection establishment with the UE.
  • Step 736 After the RAN is established, the connection establishment completion message is sent to the SM function main body; the message may be directly sent to the SM function main body, or may be forwarded by the MM function main body or other network element;
  • Step 737 The SM function body determines a new user plane path reselected for the UE according to the SM related information, the current location information of the UE, the service requirement, the node load, the congestion degree of the link, and the like, and generates and sends a user plane configuration command to the
  • the new UP function body and the DN side UP function body on the new user plane path that is, the user plane establishment request message is sent to the new UP function body and the user plane modification request message is sent to the DN side UP function body, and the user plane configuration instruction is used for Instructing the new UP function body to establish a routing or forwarding rule, and instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data message sent to the UE to the new UP function body;
  • Step 738 The new UP function body sends a user plane establishment completion message to the SM function body, and the DN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 739 The SM function body generates and sends a user plane deletion command (transmitted by the user plane deletion request message) to the original UP function body, to indicate that the original UP function body releases the user plane connection with the UE;
  • Step 7310 The original UP function body sends a user plane deletion completion message to the SM function body.
  • Step 7311 After receiving the user plane deletion complete message, the SM function body sends a user plane connection completion message to the MM function body.
  • the network initiates a service request
  • the user plane path of the UE changes
  • the MM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 741 The UE sends a service request message to the RAN.
  • Step 742 The RAN forwards the service request message to the MM function body.
  • Step 743 After receiving the service request message, the MM function body updates the UE location information and sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and a UE-related establishment ( Context) information;
  • Step 744 The RAN performs connection establishment with the UE.
  • Step 745 After the RAN is established, send a connection establishment complete message to the MM function body.
  • Step 746 After receiving the connection establishment complete message, the MM function body sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 747 The SM function body determines, according to the SM related information and the current location information of the UE, a new user plane path that is reselected by the UE, and generates and sends a user plane configuration command (transmitted by using a user plane setup request message) to the new RAN side UP function.
  • the main body instructing the new RAN side UP function main body to establish a routing or forwarding rule, that is, routing or transmitting the received uplink data packet sent to the UE to the original RAN side UP function main body (uplink routing or forwarding rule); Sending a user plane modification request message to the original RAN side UP function body, to indicate that the original RAN side UP function body performs the user plane path modification, that is, the downlink data packet sent to the UE is received or converted to the new RAN side UP function.
  • Subject downlink routing or forwarding rules
  • Step 748 The new RAN side UP function body sends a user plane establishment completion message to the SM function body, and the original RAN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 749 After receiving the user plane establishment/modification completion message, the SM function body sends a user plane connection completion message to the MM function body.
  • the network initiates a service request
  • the user plane path of the UE changes
  • the SM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 751 The UE sends a service request message to the RAN.
  • Step 752 The RAN forwards the service request message to the MM function body.
  • Step 753 After receiving the service request message, the MM function body updates the UE location information and sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 754 The SM function body sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and creating UE related (context) information; the message may be directly sent to the RAN, and Can be forwarded by the MM functional entity or other network elements;
  • Step 755 The RAN performs connection establishment with the UE.
  • Step 756 After the RAN is established, the connection establishment complete message is sent to the SM function body; the message may be directly sent to the SM function body, or may be forwarded by the MM function body or other network element;
  • Step 757 The SM function body determines, according to the SM related information and the current location information of the UE, a new user plane path that is reselected by the UE, and generates and sends a user plane configuration command (transmitted by using a user plane setup request message) to the new RAN side UP function.
  • the main body instructing the new RAN side UP function main body to establish a routing or forwarding rule, that is, routing or transmitting the received uplink data packet sent to the UE to the original RAN side UP function main body (uplink routing or forwarding rule); Sending a user plane modification request message to the original RAN side UP function body, to indicate that the original RAN side UP function body performs the user plane path modification, that is, the downlink data packet sent to the UE is received or converted to the new RAN side UP function.
  • Subject downlink routing or forwarding rules
  • Step 758 The new RAN side UP function body sends a user plane establishment completion message to the SM function body, and the original RAN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 759 After receiving the user plane establishment/modification completion message, the SM function body sends a user plane connection completion message to the MM function body.
  • the network initiates a service request
  • the user plane path of the UE changes
  • the MM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 761 The UE sends a service request message to the RAN.
  • Step 762 The RAN forwards the service request message to the MM function body.
  • Step 763 After receiving the service request message, the MM function body updates the UE location information and sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and a UE-related establishment ( Context) information;
  • Step 764 The RAN performs connection establishment with the UE.
  • Step 765 After the RAN is established, send a connection establishment complete message to the MM function body.
  • Step 766 After receiving the connection establishment complete message, the MM function body sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 767 The SM function body determines a new user plane path reselected for the UE according to the SM related information, the current location information of the UE, the service requirement, the node load, the congestion degree of the link, and the like, and generates and sends a user plane configuration command to the
  • the new UP function body and the DN side UP function body on the new user plane path that is, the user plane establishment request message is sent to the new UP function body and the user plane modification request message is sent to the DN side UP function body, and the user plane configuration instruction is used for Instructing the new UP function body to establish a routing or forwarding rule, and instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data message sent to the UE to the new UP function body;
  • Step 768 The new UP function body sends a user plane establishment completion message to the SM function body, and the DN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 769 The SM function body generates and sends a user plane deletion command (transmitted by the user plane deletion request message) to the original UP function body, to indicate that the original UP function body releases the user plane connection with the UE, and simultaneously receives the datagram. Processing (discarding);
  • Step 7610 The original UP function body sends a user plane deletion completion message to the SM function body.
  • Step 761 After receiving the user plane deletion complete message, the SM function body sends a user plane connection completion message to the MM function body.
  • the network initiates a service request
  • the user plane path of the UE changes
  • the SM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 771 The UE sends a service request message to the RAN.
  • Step 772 The RAN forwards the service request message to the MM function body.
  • Step 773 After receiving the service request message, the MM function body updates the UE location information and sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 774 The SM function body sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and UE related (context) information; the message may be directly sent to the RAN. Can be forwarded by the MM functional entity or other network elements;
  • Step 775 The RAN performs connection establishment with the UE.
  • Step 776 After the RAN is established, the connection establishment completion message is sent to the SM function main body; the message may be directly sent to the SM function main body, or may be forwarded by the MM function main body or other network element;
  • Step 777 The SM function body determines a new user plane path reselected for the UE according to the SM related information, the current location information of the UE, the service requirement, the node load, the congestion degree of the link, and the like, and generates and sends a user plane configuration command to the
  • the new UP function body and the DN side UP function body on the new user plane path that is, the user plane establishment request message is sent to the new UP function body and the user plane modification request message is sent to the DN side UP function body, and the user plane configuration instruction is used for Instructing the new UP function body to establish a routing or forwarding rule, and instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data message sent to the UE to the new UP function body;
  • Step 778 The new UP function body sends a user plane establishment completion message to the SM function body, and the DN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 779 The SM function body generates and sends a user plane deletion command (transmitted by the user plane deletion request message) to the original UP function body, to indicate that the original UP function body releases the user plane connection with the UE, and simultaneously receives the datagram. Processing (discarding);
  • Step 7710 The original UP function body sends a user plane deletion completion message to the SM function body.
  • Step 7711 After receiving the user plane deletion complete message, the SM function body sends a user plane connection completion message to the MM function body.
  • the network initiates a service request
  • the user plane path of the UE changes
  • the MM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 781 The UE sends a service request message to the RAN.
  • Step 782 The RAN forwards the service request message to the MM function body.
  • Step 783 After receiving the service request message, the MM function body updates the UE location information and sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, including at least a signaling connection, a user plane connection, and a UE-related establishment ( Context) information;
  • Step 784 The RAN performs connection establishment with the UE.
  • Step 785 After the RAN is established, send a connection establishment complete message to the MM function body.
  • Step 786 After receiving the connection establishment complete message, the MM function body sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 787 The SM function body determines a new user plane path reselected for the UE according to the SM related information, the current location information of the UE, the service requirement, the node load, the congestion degree of the link, and the like, and generates and sends a user plane configuration command to the
  • the new UP function body and the DN side UP function body on the new user plane path that is, the user plane establishment request message is sent to the new UP function body and the user plane modification request message is sent to the DN side UP function body, and the user plane configuration instruction is used for Instructing the new UP function body to establish a routing or forwarding rule, and instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data message sent to the UE to the new UP function body;
  • Step 788 The new UP function body sends a user plane establishment completion message to the SM function body, and the DN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 789 The SM function body generates and sends a user plane configuration command (transmitted by the user plane modification request message) to the original UP function body, to indicate that the original UP function body establishes a user plane path, and forwards the received data packet to the DN side UP function body;
  • Step 7810 The original UP function body sends a user plane modification completion message to the SM function body.
  • Step 7811 The SM function body sends a user plane connection completion message to the MM function body.
  • Step 7812 The SM function body starts a timer, and the timer is used to determine the lifetime of the user plane path established by the original UP function body, and the downstream flow table is reserved.
  • Step 7813 When the timer expires, the SM function body generates and sends a user plane deletion command (transmitted by the user plane deletion request message) to the original UP function body to indicate that the original UP function body releases the user plane connection with the UE. ;
  • Step 7814 The original UP function body sends a user plane deletion completion message to the SM function body.
  • the network initiates a service request
  • the user plane path of the UE changes
  • the SM function body processes the connection request of the RAN and the UE.
  • the process of the UE entering the connected state includes the following steps:
  • Step 791 The UE sends a service request message to the RAN.
  • Step 792 The RAN forwards the service request message to the MM function body.
  • Step 793 After receiving the service request message, the MM function body updates the UE location information and sends a user plane connection activation request message to the SM function body, including a session modification request.
  • Step 794 The SM function body sends a connection establishment request message to the RAN to request the RAN to establish a connection with the UE, at least including a signaling connection, a user plane connection, and creating UE related (context) information; the message may be directly sent to the RAN. Can be forwarded by the MM functional entity or other network elements;
  • Step 795 The RAN performs connection establishment with the UE.
  • Step 796 After the RAN is established, the connection establishment completion message is sent to the SM function main body; the message may be directly sent to the SM function main body, or may be forwarded by the MM function main body or other network element;
  • Step 797 The SM function body determines, according to the SM related information, the current location information of the UE, the service requirement, the node load, the congestion degree of the link, etc., a new user plane path that is reselected for the UE, and generates and sends a user plane configuration command to the
  • the new UP function body and the DN side UP function body on the new user plane path that is, the user plane establishment request message is sent to the new UP function body and the user plane modification request message is sent to the DN side UP function body, and the user plane configuration instruction is used for Instructing the new UP function body to establish a routing or forwarding rule, and instructing the DN side UP function body to perform a user plane path modification, and forwarding the received data message sent to the UE to the new UP function body;
  • Step 798 The new UP function body sends a user plane establishment completion message to the SM function body, and the DN side UP function body sends a user plane modification completion message to the SM function body.
  • Step 799 The SM function body generates and sends a user plane configuration command (transmitted by the user plane modification request message) to the original UP function body, to indicate that the original UP function body establishes a user plane path, and forwards the received data packet to the DN side UP function body;
  • Step 7910 The original UP function body sends a user plane modification completion message to the SM function body.
  • Step 7911 The SM function body sends a user plane connection completion message to the MM function body.
  • Step 7912 The SM function body starts a timer, and the timer is used to determine the lifetime of the user plane path established by the original UP function body, and the downstream flow table is reserved.
  • Step 7931 When the timer expires, the SM function body generates and sends a user plane deletion command (transmitted by the user plane deletion request message) to the original UP function body, to indicate that the original UP function body releases the user plane connection with the UE. ;
  • Step 7714 The original UP function body sends a user plane deletion completion message to the SM function body.
  • the user plane connection can be established for the UE by using the signaling interaction between the MM function body and the SM function body, so that the UE is idle.
  • the state enters the connected state, reducing the signaling overhead between the control plane and the user plane, and shortening the delay into the connected state.
  • a fifth embodiment of the present disclosure provides a processing device for a terminal idle state, which is applied to an MM function body, and includes:
  • the first receiving module 81 is configured to receive a connection release request message sent by the access network RAN;
  • the first sending module 82 is configured to send a user plane connection deactivation request message to the SM function body according to the connection release request message, where the user plane connection deactivation request message is used to instruct the SM function body to modify the user plane path. ;
  • a second receiving module 83 configured to receive a user plane connection deactivation complete message sent by the SM function body
  • the second sending module 84 is configured to send a connection release command to the RAN after receiving the user plane connection deactivation complete message, where the connection release instruction is used to instruct the RAN to perform connection release with the UE.
  • connection release request message or the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or deletion of UE context information.
  • the fifth embodiment of the present disclosure further provides a processing device for a terminal idle state, which is applied to an SM function body, and includes:
  • the third receiving module 91 is configured to receive a user plane connection deactivation request message sent by the MM function body;
  • the third sending module 92 is configured to generate and send a user plane configuration command to the RAN side UP function body according to the user plane connection deactivation request message, where the user plane configuration command is used to indicate that the RAN side UP function body performs Modification of the downstream user plane path;
  • the fourth receiving module 93 is configured to receive a user plane modification complete message sent by the RAN side UP function body;
  • the fourth sending module 94 is configured to send a user plane connection deactivation completion message to the MM function body according to the user plane modification completion message.
  • the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or deletion of UE context information.
  • a fifth embodiment of the present disclosure further provides a processing device for a terminal idle state, which is applied to an MM function body, and includes:
  • the fifth receiving module 111 is configured to receive a service request message from the UE forwarded by the RAN;
  • the requesting module 112 is configured to request the SM function body to establish a user plane connection for the UE according to the service request message.
  • the requesting module 112 includes:
  • a requesting unit configured to request the RAN to establish a connection with the UE and obtain connection information between the RAN and the UE according to the service request message;
  • a first sending unit configured to send a user plane connection activation request message to the SM function body, where the user plane connection activation request message carries connection information of the RAN and the UE, and is used to indicate that the SM function body is The UE establishes a user plane connection.
  • the request unit includes:
  • a sending subunit configured to send a connection establishment request message to the RAN according to the service request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • a receiving subunit configured to receive a connection establishment complete message sent by the RAN
  • the obtaining subunit is configured to acquire connection information of the RAN and the UE according to the connection establishment complete message.
  • the requesting module 112 includes:
  • a second sending unit configured to send a user plane connection activation request message to the SM function body according to the service request message, where the user plane connection activation request message is used to instruct the SM function body to request the RAN to establish
  • the connection of the UE acquires connection information between the RAN and the UE, and establishes a user plane connection for the UE.
  • the connection established by the RAN with the UE includes a signaling connection, a user plane connection, and/or creation of UE context information.
  • the service request message may be initiated by the UE or initiated by the network.
  • the device When the service request message is initiated by the network, the device further includes:
  • a sixth receiving module configured to receive a downlink data notification message sent by the SM function body, where, when the core network receives the downlink data packet, the SM function body is configured according to the data packet corresponding to the downlink data packet The identifier of the message matches the saved UE context information. If the related session information is found, the downlink data notification message is sent to the MM function body. Otherwise, the downlink data packet is discarded, and the user plane configuration command is generated and sent.
  • RAN side UP function body configured to receive a downlink data notification message sent by the SM function body, where, when the core network receives the downlink data packet, the SM function body is configured according to the data packet corresponding to the downlink data packet The identifier of the message matches the saved UE context information. If the related session information is found, the downlink data notification message is sent to the MM function body. Otherwise, the downlink data packet is discarded, and the user plane configuration command is generated and sent.
  • RAN side UP function body configured to receive a downlink
  • the fifth sending module is configured to send a paging message to the UE after receiving the downlink data notification message, where the paging message is used to instruct the UE to initiate a service request.
  • the processing device of the terminal idle state may further include:
  • the first receiving module 81 is configured to receive a connection release request message sent by the RAN.
  • the first sending module 82 is configured to send a user plane connection deactivation request message to the SM function body according to the connection release request message, where the user plane connection deactivation request message is used to instruct the SM function body to modify the user plane path. ;
  • a second receiving module 83 configured to receive a user plane connection deactivation complete message sent by the SM function body
  • the second sending module 84 is configured to send a connection release command to the RAN after receiving the user plane connection deactivation complete message, where the connection release instruction is used to instruct the RAN to perform connection release with the UE.
  • connection release request message or the user plane connection deactivation request message may carry at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or deletion of UE context information.
  • a fifth embodiment of the present disclosure further provides a processing device for a terminal idle state, which is applied to an SM function body, and includes:
  • the seventh receiving module 121 is configured to receive a user plane connection activation request message sent by the MM function body;
  • the obtaining module 122 is configured to obtain connection information between the RAN and the UE according to the user plane connection activation request message.
  • the establishing module 123 is configured to establish a user plane connection for the UE according to the connection information of the RAN and the UE and the SM related information.
  • the user plane connection activation request message is sent by the MM function body after requesting the RAN to establish a connection with the UE according to the received service request message from the UE that is forwarded by the RAN.
  • the connection information between the RAN and the UE is carried therein.
  • the obtaining module 122 includes:
  • a third sending unit configured to send a connection establishment request message to the RAN according to the user plane connection activation request message, where the connection establishment request message is used to indicate that the RAN establishes a connection with the UE;
  • a first receiving unit configured to receive a connection establishment complete message sent by the RAN
  • an obtaining unit configured to acquire connection information of the RAN and the UE according to the connection establishment complete message.
  • the establishing module 123 may include:
  • a first determining unit configured to determine, according to the connection information of the RAN and the UE and the SM related information, that the user plane path of the UE is unchanged;
  • a fourth sending unit configured to: after determining that the user plane path of the UE is unchanged, generate and send a user plane configuration command to the RAN side UP function body on the user plane path, where the user plane configuration command is used Instructing the RAN side UP function body to perform modification of a downlink user plane path;
  • the second receiving unit is configured to receive a user plane modification complete message sent by the RAN side UP function body.
  • the processing device of the terminal idle state further includes:
  • the sixth sending module is configured to send a user plane connection completion message to the MM function body.
  • the establishing module 123 may include:
  • a second determining unit configured to determine, according to the connection information of the RAN and the UE and the SM related information, a new user plane path that is reselected by the UE;
  • a fifth sending unit configured to generate and send a user plane configuration command to the new RAN side UP function body on the new user plane path, where the user plane configuration command is used to indicate that the new RAN side UP function body establishes a route or Forwarding rules
  • a sixth sending unit configured to send a user plane modification request message to the original RAN side UP function body on the original user plane path of the UE, where the user plane modification request message is used to indicate that the original RAN side UP function body performs User plane path modification;
  • a third receiving unit configured to receive a user plane setup complete message sent by the new RAN side UP function body, and receive a user plane modification complete message sent by the original RAN side UP function body.
  • the establishing module 123 may include:
  • a third determining unit configured to determine, according to the connection information of the RAN and the UE and the SM related information, a new user plane path that is reselected by the UE;
  • a seventh sending unit configured to generate and send a user plane configuration command to the new UP function body and the DN side UP function body on the new user plane path, where the user plane configuration instruction is used to indicate that the new UP function body is established Routing or forwarding the rule, and instructing the DN side UP function body to perform the user plane path modification, and forwarding the received data packet sent to the UE to the new UP function body;
  • the fourth receiving unit is configured to receive a user plane establishment completion message sent by the new UP function body, and receive a user plane modification completion message sent by the DN side UP function body.
  • the processing device of the terminal idle state further includes:
  • a seventh sending module configured to generate and send a user plane deletion command to the original UP function body on the original user plane path of the UE, where the user plane deletion instruction is used to indicate that the original UP function body releases the UE User plane connection;
  • the eighth receiving module is configured to receive a user plane deletion completion message sent by the original UP function body.
  • the processing device of the terminal idle state further includes:
  • An eighth sending module configured to generate and send a user plane configuration command to the original UP function body on the original user plane path of the UE, where the user plane configuration command is used to indicate that the original UP function body establishes a user plane path, Forwarding the received data packet to the DN side UP function body;
  • the ninth receiving module is configured to receive a user plane modification complete message sent by the original UP function body.
  • the processing device of the terminal idle state further includes:
  • the opening module is configured to enable a timer, where the timer is used to determine a lifetime of a user plane path established by the original UP function body;
  • a ninth sending module configured to: when the timer expires, generate and send a user plane deletion instruction to the original UP function body, where the user plane deletion instruction is used to indicate that the original UP function body releases the UE User plane connection;
  • the tenth receiving module is configured to receive a user plane deletion completion message sent by the original UP function body.
  • the processing device of the terminal idle state may further include:
  • the third receiving module 91 is configured to receive a user plane connection deactivation request message sent by the MM function body;
  • the third sending module 92 is configured to generate and send a user plane configuration command to the RAN side UP function body according to the user plane connection deactivation request message, where the user plane configuration command is used to indicate that the RAN side UP function body performs Modification of the downstream user plane path;
  • the fourth receiving module 93 is configured to receive a user plane modification complete message sent by the RAN side UP function body;
  • the fourth sending module 94 is configured to send a user plane connection deactivation completion message to the MM function body according to the user plane modification completion message.
  • the user plane connection deactivation request message carries at least one of the following information: a UE identifier, an MM context identifier, a base station identifier, and a reason for the release.
  • the connection with the UE released by the RAN includes a signaling connection, a user plane connection, and/or deletion of UE context information.
  • the processing device of the terminal idle state of the fifth embodiment of the present disclosure in the case that the MM function is separated from the SM function, enables the UE to enter an idle state by means of signaling interaction between the MM function body and the SM function body, and when the UE enters the idle state In the state, the connection between the RAN and the UE is released, and the user plane connection in the core network is maintained, which is beneficial to the fast response of the service; the user plane connection can also be established for the UE, so that the UE enters the connected state from the idle state, and reduces the control plane and The signaling overhead between user planes shortens the delay into the connected state.
  • a sixth embodiment of the present disclosure provides an MM function main body, where the MM function main body includes a first bus 131, a first transceiver 132, an antenna 133, a first bus interface 134, and a first processor 135. And a first memory 136.
  • the first processor 135 is configured to read the program in the first memory 136 and perform the following process:
  • the first transceiver 132 is controlled to receive a service request message from the UE forwarded by the RAN, and according to the service request message, request the SM function body to establish a user plane connection for the UE.
  • first processor 135 can also perform the following processes:
  • the message is used to indicate that the SM function body modifies the user plane path, and controls the first transceiver 132 to receive the user plane connection deactivation completion message sent by the SM function body, after receiving the user plane connection deactivation completion message,
  • the first transceiver 132 is controlled to send a connection release command to the RAN, and the connection release instruction is used to instruct the RAN to perform connection release with the terminal UE.
  • the first transceiver 132 is configured to receive and transmit data under the control of the first processor 135.
  • a bus architecture (represented by a first bus 131), which may include any number of interconnected buses and bridges, the first bus 131 will include one or more of the first processor 135
  • the processor and various circuits of the memory represented by the first memory 136 are linked together.
  • the first bus 131 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • the first bus interface 134 provides an interface between the first bus 131 and the first transceiver 132.
  • the first transceiver 132 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the first processor 135 is transmitted over the wireless medium via the antenna 133. Further, the antenna 133 also receives the data and transmits the data to the first processor 135.
  • the first processor 135 is responsible for managing the first bus 131 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the first memory 136 can be used to store data used by the first processor 135 when performing operations.
  • the first processor 134 can be a CPU, an ASIC, an FPGA, or a CPLD.
  • a seventh embodiment of the present disclosure provides an SM function main body, where the SM function main body includes a second bus 141 , a second transceiver 142 , an antenna 143 , a second bus interface 144 , and a second processor 145 . And a second memory 146.
  • the second processor 145 is configured to read the program in the second memory 146 and perform the following process:
  • the second transceiver 142 is configured to receive the user plane connection activation request message sent by the MM function body, and obtain the connection information between the RAN and the UE according to the user plane connection activation request message, according to the connection information and SM related information of the RAN and the UE. Establishing a user plane connection for the UE.
  • the second processor 145 can also perform the following processes:
  • the second transceiver 142 is configured to receive and transmit data under the control of the second processor 145.
  • a bus architecture (represented by a second bus 141), the second bus 141 may include any number of interconnected buses and bridges, and the second bus 141 will include one or more represented by the second processor 145.
  • the various circuits of the memory represented by the processor and the second memory 146 are linked together.
  • the second bus 141 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • the second bus interface 144 provides an interface between the second bus 141 and the second transceiver 142.
  • the second transceiver 142 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • Data processed by the second processor 145 is transmitted over the wireless medium via the antenna 143. Further, the antenna 143 also receives the data and transmits the data to the second processor 145.
  • the second processor 145 is responsible for managing the second bus 141 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the second memory 66 can be used to store data used by the second processor 145 when performing operations.
  • the second processor 144 can be a CPU, an ASIC, an FPGA, or a CPLD.

Landscapes

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

Abstract

本公开提供一种终端空闲态的处理方法及装置，其中，所述终端空闲态的处理方法包括：接收接入网RAN转发的来自UE的业务请求消息；根据所述业务请求消息，请求会话管理SM功能主体为所述UE建立用户面连接。

Description

一种终端空闲态的处理方法及装置
相关申请的交叉引用
本申请主张在2017年1月9日在中国提交的中国专利申请号No.201710013651.8的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种终端空闲态的处理方法及装置。
背景技术
当前，在演进的分组系统(Evolved Packet System，简称EPS)中，移动性管理实体(Mobility Management Entity，简称MME)同时支持移动性管理(Mobility Management，MM)功能和会话管理(Session Management，SM)功能，MM功能例如为附着、跟踪区更新等，SM功能例如为公用数据网连接的建立、修改和删除等。终端UE发出的MM消息和SM消息均被终止于MME，由MME处理。
为了提高网络的模块化程度，在第五代移动通信系统(5 Generation，5G)中，MM(移动性管理)功能和SM(会话管理)功能作为两个独立的功能模块存在，且5G网络支持网关的控制与转发分离、MM功能与SM功能分离。其中，MM功能主体的主要功能为用户注册、UE不可达到的发现、位置注册、UE状态的变迁、连接态和非激活态态的移动性、UE移动限制性、UE移动性管理控制、锚点的选择、建立用户面路径等。SM功能主体的主要功能为数据包的转发和检测、会话控制、用户平面功能的选择、UE IP地址的分配(连接类型为IP)等。MM功能主体与SM功能主体之间需要信令交互以实现信息交互与协同。
实际应用中，当接入网(Residential Access Network，RAN)发现UE处于不活动状态时，会改变终端状态并触发UE进入空闲态，而当UE或网络需要进行数据传输时，也会改变终端状态并触发UE从空闲态进入连接态。
但目前，还没有关于MM功能与SM功能分离后终端空闲态的处理方法。
发明内容
本公开的目的在于提供一种终端空闲态的处理方法及装置，以能够在MM功能与SM功能分离的情况下，对终端空闲态进行有效处理，例如使UE从空闲态进入连接态。
为了实现上述的目的，一方面，本公开提供一种终端空闲态的处理方法，应用于MM功能主体，包括：
接收接入网RAN转发的来自UE的业务请求消息；
根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接。
可选的，所述根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接的步骤，包括：
根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息；
发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息中携带所述RAN与UE的连接信息，用于指示所述SM功能主体为所述UE建立用户面连接。
可选的，所述根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息的步骤，包括：
根据所述业务请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
接收所述RAN发送的连接建立完成消息；
根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
可选的，所述根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接的步骤，包括：
根据所述业务请求消息，发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息用于指示所述SM功能主体请求所述RAN建立与所述UE的连接，获取所述RAN与UE的连接信息，并为所述UE建立用户面连接。
可选的，所述RAN建立的与所述UE的连接包括信令连接、用户面连接和/或创建UE上下文信息。
可选的，所述业务请求消息由UE自主发起或者网络发起。
可选的，当所述业务请求消息由网络发起时，所述接收RAN转发的来自UE的业务请求消息的步骤之前，还包括：
接收所述SM功能主体发送的下行数据通知消息；其中，当核心网接收到下行数据报文时，所述SM功能主体根据与所述下行数据报文对应的数据报文标识，匹配保存的UE上下文信息，若找到相关的会话信息，则发送所述下行数据通知消息给所述MM功能主体，否则确定丢弃所述下行数据报文，生成并发送用户面配置指令给RAN侧UP功能主体；
在接收到所述下行数据通知消息后，发送寻呼消息给所述UE，所述寻呼消息用于指示所述UE发起业务请求。
可选的，所述方法还包括：
接收RAN发送的连接释放请求消息；
根据所述连接释放请求消息，发送用户面连接去激活请求消息给会话管理SM功能主体，所述用户面连接去激活请求消息用于指示所述SM功能主体修改用户面路径；
接收所述SM功能主体发送的用户面连接去激活完成消息；
在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与终端UE的连接释放。
可选的，所述连接释放请求消息或用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
可选的，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
另一方面，本公开还提供一种终端空闲态的处理方法，应用于SM功能主体，包括：
接收MM功能主体发送的用户面连接激活请求消息；
根据所述用户面连接激活请求消息，获取RAN与UE的连接信息；
根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
可选的，所述用户面连接激活请求消息是所述MM功能主体根据接收到 的所述RAN转发的来自UE的业务请求消息，请求所述RAN建立与UE的连接之后发送的，其内携带有所述RAN与UE的连接信息。
可选的，所述根据所述用户面连接激活请求消息，获取RAN与UE的连接信息的步骤，包括：
根据所述用户面连接激活请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
接收所述RAN发送的连接建立完成消息；
根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
可选的，所述根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接的步骤，包括：
根据所述RAN与UE的连接信息和SM相关信息，确定所述UE的用户面路径不变；
在确定出所述UE的用户面路径不变后，生成并发送用户面配置指令给所述用户面路径上的RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
接收所述RAN侧UP功能主体发送的用户面修改完成消息。
可选的，所述接收所述RAN侧UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
发送用户面连接完成消息给所述MM功能主体。
可选的，所述根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接的步骤，包括：
根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
生成并发送用户面配置指令给所述新用户面路径上的新RAN侧UP功能主体，所述用户面配置指令用于指示所述新RAN侧UP功能主体建立路由或转发规则；
发送用户面修改请求消息给所述UE的原用户面路径上的原RAN侧UP功能主体，所述用户面修改请求消息用于指示所述原RAN侧UP功能主体进行用户面路径修改；
接收所述新RAN侧UP功能主体发送的用户面建立完成消息，并接收所述原RAN侧UP功能主体发送的用户面修改完成消息。
可选的，所述根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接的步骤，包括：
根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
生成并发送用户面配置指令给所述新用户面路径上的新UP功能主体和DN侧UP功能主体，所述用户面配置指令用于指示所述新UP功能主体建立路由或转发规则，并指示所述DN侧UP功能主体进行用户面路径修改，将接收到的发送给所述UE的数据报文转发给所述新UP功能主体；
接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息。
可选的，所述接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
生成并发送用户面删除指令给所述UE的原用户面路径上的原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
接收所述原UP功能主体发送的用户面删除完成消息。
可选的，所述接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
生成并发送用户面配置指令给所述UE的原用户面路径上的原UP功能主体，所述用户面配置指令用于指示所述原UP功能主体建立用户面路径，将接收到的数据报文转发给所述DN侧UP功能主体；
接收所述原UP功能主体发送的用户面修改完成消息。
可选的，所述接收所述原UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
开启定时器，所述定时器用于确定所述原UP功能主体建立的用户面路 径的生存期；
当所述定时器超时时，生成并发送用户面删除指令给所述原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
接收所述原UP功能主体发送的用户面删除完成消息。
可选的，所述方法还包括：
接收MM功能主体发送的用户面连接去激活请求消息；
根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧用户面UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
接收所述RAN侧UP功能主体发送的用户面修改完成消息；
根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
可选的，所述用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
可选的，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
又一方面，本公开还提供一种终端空闲态的处理装置，应用于MM功能主体，包括：
第五接收模块，用于接收RAN转发的来自UE的业务请求消息；
请求模块，用于根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接。
可选的，所述请求模块包括：
请求单元，用于根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息；
第一发送单元，用于发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息中携带所述RAN与UE的连接信息，用于指示所述SM功能主体为所述UE建立用户面连接。
可选的，所述请求单元包括：
发送子单元，用于根据所述业务请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
接收子单元，用于接收所述RAN发送的连接建立完成消息；
获取子单元，用于根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
可选的，所述请求模块包括：
第二发送单元，用于根据所述业务请求消息，发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息用于指示所述SM功能主体请求所述RAN建立与所述UE的连接，获取所述RAN与UE的连接信息，并为所述UE建立用户面连接。
可选的，所述RAN建立的与所述UE的连接包括信令连接、用户面连接和/或创建UE上下文信息。
可选的，所述业务请求消息由UE自主发起或者网络发起。
可选的，当所述业务请求消息由网络发起时，还包括：
第六接收模块，用于接收所述SM功能主体发送的下行数据通知消息；其中，当核心网接收到下行数据报文时，所述SM功能主体根据与所述下行数据报文对应的数据报文标识，匹配保存的UE上下文信息，若找到相关的会话信息，则发送所述下行数据通知消息给所述MM功能主体，否则确定丢弃所述下行数据报文，生成并发送用户面配置指令给RAN侧UP功能主体；
第五发送模块，用于在接收到所述下行数据通知消息后，发送寻呼消息给所述UE，所述寻呼消息用于指示所述UE发起业务请求。
可选的，所述装置还包括：
第一接收模块，用于接收接入网RAN发送的连接释放请求消息；
第一发送模块，用于根据所述连接释放请求消息，发送用户面连接去激活请求消息给SM功能主体，所述用户面连接去激活请求消息用于指示所述SM功能主体修改用户面路径；
第二接收模块，用于接收所述SM功能主体发送的用户面连接去激活完成消息；
第二发送模块，用于在接收到所述用户面连接去激活完成消息后，发送 连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与UE的连接释放。
可选的，所述连接释放请求消息或用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
可选的，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
又一方面，本公开还提供一种终端空闲态的处理装置，应用于SM功能主体，包括：
第七接收模块，用于接收MM功能主体发送的用户面连接激活请求消息；
获取模块，用于根据所述用户面连接激活请求消息，获取RAN与UE的连接信息；
建立模块，用于根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
可选的，所述用户面连接激活请求消息是所述MM功能主体根据接收到的所述RAN转发的来自UE的业务请求消息，请求所述RAN建立与UE的连接之后发送的，其内携带有所述RAN与UE的连接信息。
可选的，所述获取模块包括：
第三发送单元，用于根据所述用户面连接激活请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
第一接收单元，用于接收所述RAN发送的连接建立完成消息；
获取单元，用于根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
可选的，所述建立模块包括：
第一确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定所述UE的用户面路径不变；
第四发送单元，用于在确定出所述UE的用户面路径不变后，生成并发送用户面配置指令给所述用户面路径上的RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
第二接收单元，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息。
可选的，所述装置还包括：
第六发送模块，用于发送用户面连接完成消息给所述MM功能主体。
可选的，所述建立模块包括：
第二确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
第五发送单元，用于生成并发送用户面配置指令给所述新用户面路径上的新RAN侧UP功能主体，所述用户面配置指令用于指示所述新RAN侧UP功能主体建立路由或转发规则；
第六发送单元，用于发送用户面修改请求消息给所述UE的原用户面路径上的原RAN侧UP功能主体，所述用户面修改请求消息用于指示所述原RAN侧UP功能主体进行用户面路径修改；
第三接收单元，用于接收所述新RAN侧UP功能主体发送的用户面建立完成消息，并接收所述原RAN侧UP功能主体发送的用户面修改完成消息。
可选的，所述建立模块包括：
第三确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
第七发送单元，用于生成并发送用户面配置指令给所述新用户面路径上的新UP功能主体和DN侧UP功能主体，所述用户面配置指令用于指示所述新UP功能主体建立路由或转发规则，并指示所述DN侧UP功能主体进行用户面路径修改，将接收到的发送给所述UE的数据报文转发给所述新UP功能主体；
第四接收单元，用于接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息。
可选的，所述装置还包括：
第七发送模块，用于生成并发送用户面删除指令给所述UE的原用户面路径上的原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
第八接收模块，用于接收所述原UP功能主体发送的用户面删除完成消息。
可选的，所述装置还包括：
第八发送模块，用于生成并发送用户面配置指令给所述UE的原用户面路径上的原UP功能主体，所述用户面配置指令用于指示所述原UP功能主体建立用户面路径，将接收到的数据报文转发给所述DN侧UP功能主体；
第九接收模块，用于接收所述原UP功能主体发送的用户面修改完成消息。
可选的，所述装置还包括：
开启模块，用于开启定时器，所述定时器用于确定所述原UP功能主体建立的用户面路径的生存期；
第九发送模块，用于当所述定时器超时时，生成并发送用户面删除指令给所述原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
第十接收模块，用于接收所述原UP功能主体发送的用户面删除完成消息。
可选的，所述装置还包括：
第三接收模块，用于接收MM功能主体发送的用户面连接去激活请求消息；
第三发送模块，用于根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
第四接收模块，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息；
第四发送模块，用于根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
可选的，所述用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
可选的，所述RAN释放的与UE的连接包括信令连接、用户面连接和/ 或删除UE上下文信息。
再一方面，本公开提供一种终端空闲态的处理装置，应用于MM功能主体，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述应用于MM功能主体的终端空闲态的处理方法中的步骤。
再一方面，本公开提供一种终端空闲态的处理方法，应用于SM功能主体，处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述应用于SM功能主体的终端空闲态的处理方法中的步骤。
再一方面，本公开提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述应用于MM功能主体的终端空闲态的处理方法中的步骤。
再一方面，本公开提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述应用于SM功能主体的终端空闲态的处理方法中的步骤。本公开的的终端空闲态的处理方法，在MM功能与SM功能分离的情况下，借助MM功能主体和SM功能主体的信令交互，可使UE进入空闲态，且当UE进入空闲态时，释放掉RAN与UE的连接，依然保持核心网中的用户面连接，有利于业务的快速响应；还可为UE建立用户面连接，使UE从空闲态进入连接态，减少控制面与用户面之间的信令开销，缩短进入连接态的时延等。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1表示本公开第一实施例的终端空闲态的处理方法的流程图。
图2表示本公开第一实施例中具体实例的RAN触发UE进入空闲态的流程图。
图3表示本公开第二实施例的终端空闲态的处理方法的流程图。
图4表示本公开第三实施例的终端空闲态的处理方法的流程图。
图5A和图5B表示本公开第三实施例中的两种网络发起业务请求的流程图。
图6表示本公开第四实施例的终端空闲态的处理方法的流程图。
图7A～图7J表示本公开第四实施例中具体实例的UE从空闲态进入连接态的流程图。
图8表示本公开第五实施例的终端空闲态的处理装置的结构示意图之一。
图9表示本公开第五实施例的终端空闲态的处理装置的结构示意图之二。
图10表示本公开第五实施例的终端空闲态的处理装置的结构示意图之三。
图11表示本公开第五实施例的终端空闲态的处理装置的结构示意图之四。
图12表示本公开第六实施例的MM功能主体的结构示意图。
图13表示本公开第七实施例的SM功能主体的结构示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
第一实施例
参见图1所示，本公开第一实施例提供一种终端空闲态的处理方法，应用于移动性管理MM功能主体，包括如下步骤101至步骤104，详述如下。
步骤101：接收接入网RAN发送的连接释放请求消息。
本公开实施例中，当RAN发现需要释放UE的信令连接和用户面连接时，会发送连接释放请求消息给MM功能主体，以由该MM功能主体请求SM功能主体修改该UE的用户面路径，使该UE进入空闲态。
该连接释放请求消息可携带如下信息中的至少一种：UE标识、MM上下 文标识、基站标识和释放的原因(例如user inactivity，即由于用户长时间流量低于某一门限值，系统为节省资源发起的释放)等等。
步骤102：根据所述连接释放请求消息，发送用户面连接去激活请求消息给SM功能主体。
本公开实施例中，该用户面连接去激活请求消息用于指示该SM功能主体修改用户面路径，可携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因(例如user inactivity)等等。该用户面连接去激活请求消息也可包括会话修改请求消息。
其中，在接收到该用户面连接去激活请求消息后，该SM功能主体会生成并发送用户面配置指令给RAN侧UP功能主体，以使该RAN侧UP功能主体根据该用户面配置指令，进行下行用户面路径的修改。该用户面配置指令例如用于，指示该RAN侧UP功能主体在接收到下行数据报文时，上报所述SM功能主体。
该RAN侧UP功能主体具体为核心网中的与RAN相连的用户面。
步骤103：接收所述SM功能主体发送的用户面连接去激活完成消息。
本公开实施例中，在完成对用户面路径的修改后，该SM功能主体会发送用户面连接去激活完成消息给该MM功能主体。
步骤104：在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN。
本公开实施例中，该连接释放指令用于指示该RAN执行与UE的连接释放。在接收到该连接释放指令后，该RAN会执行与UE的连接释放。具体来说，该RAN释放的与UE的连接可包括：信令连接、用户面连接和/或删除UE上下文信息等。
在释放完与UE的连接后，该RAN可以通知该UE，并发送连接释放完成消息给该MM功能主体。这样，网络会认为该UE进入空闲态。
下面，结合图2对本公开第一实施例中具体实例的RAN触发UE进入空闲态的过程进行说明。
参见图2所示，该RAN触发UE进入空闲态的过程包括如下步骤：
步骤201：当发现需要释放UE的信令连接和用户面连接时，RAN发送 连接释放请求消息给MM功能主体；
步骤202：MM功能主体在接收到该连接释放请求消息后，发送用户面连接去激活请求消息给SM功能主体；
步骤203：SM功能主体根据该用户面连接去激活请求消息，发送用户面修改请求消息给RAN侧UP功能主体，该用户面修改请求消息中携带有该SM功能主体生成的用户面配置指令；
步骤204：RAN侧UP功能主体根据该用户面配置指令，进行下行用户面路径的修改，并在修改完后发送用户面修改完成消息给SM功能主体；
步骤205：SM功能主体在接收到该用户面修改完成消息后，发送用户面连接去激活完成消息给MM功能主体；
步骤206：MM功能主体在接收到该用户面连接去激活完成消息后，发送连接释放指令给RAN；
步骤207：RAN根据该连接释放指令，执行与UE的连接释放；该RAN释放的与UE的连接包括信令连接、用户面连接和/或创建UE上下文信息；
步骤208：RAN在释放完与UE的连接后，发送连接释放完成消息给MM功能主体；至此，网络会认为该UE进入空闲态。
本公开第一实施例的终端空闲态的处理方法，在MM功能与SM功能分离的情况下，借助MM功能主体和SM功能主体的信令交互，可使UE进入空闲态，且当UE进入空闲态时，释放掉RAN与UE的连接，依然保持核心网中的用户面连接，有利于业务的快速响应。
第二实施例
参见图3所示，本公开第二实施例提供一种终端空闲态的处理方法，应用于SM功能主体，包括如下步骤301至步骤304，详述如下。
步骤301：接收MM功能主体发送的用户面连接去激活请求消息。
本公开实施例中，当RAN发现需要释放UE的信令连接和用户面连接时，会发送连接释放请求消息给MM功能主体，以由该MM功能主体请求SM功能主体修改该UE的用户面路径，并发送用户面连接去激活请求消息给该SM功能主体。
该用户面连接去激活请求消息用于指示该SM功能主体修改用户面路径， 可携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因(例如user inactivity)等等。该用户面连接去激活请求消息也可包括会话修改请求消息。
步骤302：根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧UP功能主体。
本公开实施例中，该用户面配置指令用于指示该RAN侧UP功能主体进行下行用户面路径的修改。例如，该用户面配置指令可指示该RAN侧UP功能主体在接收到下行数据报文时，上报该SM功能主体。
步骤303：接收所述RAN侧UP功能主体发送的用户面修改完成消息。
本公开实施例中，该RAN侧UP功能主体在完成对用户面路径的修改后，可发送该用户面修改完成消息给该SM功能主体。
步骤304：根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
本公开实施例中，该MM功能主体在接收到该用户面连接去激活完成消息后，可发送连接释放请求消息给该RAN，以指示该RAN执行与UE的连接释放。具体的，该RAN释放的与UE的连接可包括：信令连接、用户面连接和/或删除UE上下文信息等。
本公开第一实施例的终端空闲态的处理方法，在MM功能与SM功能分离的情况下，借助MM功能主体和SM功能主体的信令交互，可使UE进入空闲态，且当UE进入空闲态时，释放掉RAN与UE的连接，依然保持核心网中的用户面连接，有利于业务的快速响应。
第三实施例
参见图4所示，本公开第三实施例提供一种终端空闲态的处理方法，应用于MM功能主体，包括如下步骤401至步骤402，详述如下。
步骤401：接收RAN转发的来自UE的业务请求消息。
本公开实施例中，该业务请求消息可携带如下信息中的至少一种：UE标识、MM上下文标识和基站标识等。
其中，该业务请求消息可由UE自主发起或者网络发起。当UE有业务要进行时，可自主发送业务请求消息至RAN，并经该RAN转发至该MM功能 主体。该UE发送业务请求消息也可因接收到网络侧发送的寻呼消息。
具体的，当该业务请求消息由网络发起时，该步骤401之前，本公开实施例的终端空闲态的处理方法还包括：
接收SM功能主体发送的下行数据通知消息；
在接收到所述下行数据通知消息后，发送寻呼消息给所述UE。
其中，当核心网接收到下行数据报文时，该SM功能主体根据与该下行数据报文对应的数据报文标识，匹配保存的UE上下文，若找到相关的会话信息，则发送该下行数据通知消息给该MM功能主体，否则确定丢弃该下行数据报文，生成并发送用户面配置指令给数据网RAN侧UP功能主体，以完成路由或转发规则的配置(即丢弃该下行数据报文)。该寻呼消息用于指示该UE发起业务请求，即发送业务请求消息给MM功能主体。
步骤402：根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接。
本公开实施例中，该MM功能主体根据该业务请求消息，请求SM功能主体为UE建立用户面连接可至少有如下两种方式，详述如下。
方式一：MM功能主体处理连接请求
在方式一下，该MM功能主体根据该业务请求消息，请求SM功能主体为UE建立用户面连接的过程为：
首先，该MM功能主体根据该业务请求消息，请求该RAN建立与UE的连接并获取该RAN与UE的连接信息；然后，该MM功能主体发送用户面连接激活请求消息给该SM功能主体，该用户面连接激活请求消息中携带该RAN与UE的连接信息，用于指示该SM功能主体为UE建立用户面连接。
其中，该MM功能主体根据该业务请求消息，请求该RAN建立与UE的连接并获取该RAN与UE的连接信息的过程为：
首先，该MM功能主体根据该业务请求消息，发送连接建立请求消息给该RAN，该连接建立请求消息用于指示该RAN建立与UE的连接；然后，该MM功能主体接收该RAN发送的连接建立完成消息；最后，该MM功能主体根据该连接建立完成消息，获取该RAN与UE的连接信息。
方式二：SM功能主体处理连接请求
在方式二下，该MM功能主体根据该业务请求消息，请求SM功能主体为UE建立用户面连接的过程为：
该MM功能主体直接根据该业务请求消息，发送用户面连接激活请求消息给该SM功能主体，该用户面连接激活请求消息用于指示该SM功能主体请求该RAN建立与UE的连接，获取该RAN与UE的连接信息，并为该UE建立用户面连接。
本公开实施例中，该RAN建立的与UE的连接可包括信令连接、用户面连接和/或创建UE上下文信息等。
本公开实施例中，该终端空闲态的处理方法还包括：
接收RAN发送的连接释放请求消息；
根据所述连接释放请求消息，发送用户面连接去激活请求消息给会话管理SM功能主体，所述用户面连接去激活请求消息用于指示所述SM功能主体修改用户面路径；
接收所述SM功能主体发送的用户面连接去激活完成消息；
在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与终端UE的连接释放(具体实现过程可参见第一实施例中记载的内容)。
其中，该连接释放请求消息或用户面连接去激活请求消息可携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
其中，该RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息等。
下面，结合图5A和图5B对本公开第三实施例中的两种网络发起业务请求的过程进行说明。
参见图5A所示，其中一种网络发起的业务请求过程包括如下步骤：
步骤501：RAN侧UP功能主体上报数据报文标识给SM功能主体；其中，当核心网即RAN侧UP功能主体接收到下行数据报文时，由于没有下行的用户面路径，则缓存该下行数据报文，并解析该下行数据报文以得到数据报文标识，而后将该数据报文标识上报给该SM功能主体；
步骤502：SM功能主体根据该数据报文标识，匹配保存的UE上下文信 息；若找到相关的会话信息，则执行步骤503，否则执行步骤504；
步骤503：SM功能主体发送下行数据通知消息DDN给MM功能主体；
步骤504：SM功能主体确定丢弃该下行数据报文，生成并发送用户面配置指令给RAN侧UP功能主体，以完成路由或转发规则的配置(即丢弃该下行数据报文)；
步骤505：MM功能主体在接收到该DDN后，发送DDN ACK给SM功能主体；
步骤506：MM功能主体发送寻呼消息给RAN；
步骤507：RAN发送该寻呼消息给UE，使UE发起业务请求。
参见图5B所示，其中另一种网络发起的业务请求过程(基于软件定义网络(Software Defined Network，SDN)，采用OpenFlow协议)包括如下步骤：
步骤511：RAN侧UP功能主体发送Packet-in消息给SM功能主体；其中，当核心网即RAN侧UP功能主体接收到下行数据报文时，由于没有下行的用户面路径，则缓存该下行数据报文，并将整个下行数据报文作为Packet-in消息的附带内容发送Packet-in消息给SM功能主体；
步骤512：SM功能主体根据该Packet-in消息，匹配保存的UE上下文信息；若找到相关的会话信息，则执行步骤513，否则执行步骤514；
步骤513：SM功能主体发送DDN给MM功能主体；
步骤514：SM功能主体确定丢弃该下行数据报文，并生成相应的流表项，发送Packet-out消息给RAN侧UP功能主体，以配置流表项(即丢弃该下行数据报文)；
步骤515：MM功能主体在接收到该DDN后，发送DDN ACK给SM功能主体；
步骤516：MM功能主体发送寻呼消息给RAN；
步骤517：RAN发送该寻呼消息给UE，使UE发起业务请求。
本公开第三实施例的终端空闲态的处理方法，在MM功能与SM功能分离的情况下，借助MM功能主体和SM功能主体的信令交互，可为UE建立用户面连接，使UE从空闲态进入连接态，减少控制面与用户面之间的信令开销，缩短进入连接态的时延等。
第四实施例
参见图6所示，本公开第四实施例提供一种终端空闲态的处理方法，应用于SM功能主体，包括如下步骤601至步骤603，详述如下。
步骤601：接收MM功能主体发送的用户面连接激活请求消息。
本公开实施例中，该MM功能主体可以在接收到RAN转发的来自UE的业务请求消息之后，直接根据该业务请求消息，发送该用户面连接激活请求消息给该SM功能主体，以指示该SM功能主体请求RAN建立与UE的连接，也可以在根据接收到的该RAN转发的来自UE的业务请求消息，请求该RAN建立与UE的连接之后，发送该用户面连接激活请求消息。
其中，该业务请求消息或该用户面连接激活请求消息可携带如下信息中的至少一种：UE标识、MM上下文标识和基站标识等。
步骤602：根据所述用户面连接激活请求消息，获取RAN与UE的连接信息。
本公开实施例中，该RAN与UE的连接可以由该MM功能主体请求建立，也可以由该SM功能主体请求建立。
当该RAN与UE的连接由该MM功能主体请求建立时，该步骤602中的用户面连接激活请求消息具体是该MM功能主体根据接收到的该RAN转发的来自UE的业务请求消息，请求该RAN建立与UE的连接之后发送的，其内携带有该RAN与UE的连接信息。
而当该RAN与UE的连接由该SM功能主体请求建立时，该步骤602可具体为：
根据该用户面连接激活请求消息，发送连接建立请求消息给该RAN，该连接建立请求消息用于指示该RAN建立与UE的连接；
接收该RAN发送的连接建立完成消息；
根据该连接建立完成消息，获取该RAN与UE的连接信息。
其中，该RAN建立的与UE的连接可包括信令连接、用户面连接和/或创建UE上下文信息等。
步骤603：根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
本公开实施例中，该SM功能主体在为UE建立用户面连接时，可根据该RAN与UE的连接信息和SM相关信息，除此之外，也可参考其他的辅助信息，例如业务需求、节点负载、链路的拥塞程度等等(可以是多种因素的组合，也可以是某一种因素)。该SM相关信息可至少包括UE当前位置信息。
具体的，该SM功能主体为UE建立的用户面连接分情况可至少有如下四种，详述如下。
第一种：UE的用户面路径不变
在第一种情况下，该SM功能主体为UE建立用户面连接的过程为：
首先，该SM功能主体根据该RAN与UE的连接信息和SM相关信息(可包括UE当前位置信息)，确定该UE的用户面路径不变；
然后，该SM功能主体在确定出该UE的用户面路径不变后，生成并发送用户面配置指令给该用户面路径上的RAN侧UP功能主体，该用户面配置指令用于指示该RAN侧UP功能主体进行下行用户面路径的修改，即接收到下行数据报文时，按照路由或者转发规则发送；
最后，该SM功能主体接收该RAN侧UP功能主体发送的用户面修改完成消息。
其中，该RAN侧UP功能主体具体为核心网中的与RAN连接的用户面。该第一种情况适用于UE自主发起业务请求，也适用于网络发起业务请求。
本公开具体实施例中，在接收到该RAN侧UP功能主体发送的用户面修改完成消息后，该SM功能主体还可发送用户面连接完成消息给MM功能主体，以完成为UE建立用户面连接。
第二种：UE的用户面路径改变
在第二种情况下，该SM功能主体为UE建立用户面连接的过程为：
首先，该SM功能主体根据该RAN与UE的连接信息和SM相关信息(可包括UE当前位置信息)，确定为该UE重新选择的新用户面路径；
然后，该SM功能主体生成并发送用户面配置指令给该新用户面路径上的新RAN侧UP功能主体，该用户面配置指令用于指示该新RAN侧UP功能主体建立路由或转发规则，即将接收到的发送给该UE的上行数据报文路由或者转化给原RAN侧UP功能主体(上行的路由或者转发规则)；同时该 SM功能主体发送用户面修改请求消息给该UE的原用户面路径上的原RAN侧UP功能主体，该用户面修改请求消息用于指示该原RAN侧UP功能主体进行用户面路径修改，即将接收到发送给该UE的下行数据报文路由或者转化给新RAN侧UP功能主体(下行的路由或者转发规则)；
最后，该SM功能主体接收该新RAN侧UP功能主体发送的用户面建立完成消息，并接收该原RAN侧UP功能主体发送的用户面修改完成消息。
其中，该新RAN侧UP功能主体具体为核心网中的新用户面路径上的与RAN连接的用户面。该原RAN侧UP功能主体具体为核心网中的原用户面路径上的与RAN连接的用户面。该第二种情况适用于网络发起的业务请求。
第三种：UE的用户面路径改变
在第三种情况下，该SM功能主体为UE建立用户面连接的过程为：
首先，该SM功能主体根据该RAN与UE的连接信息和SM相关信息(可包括UE当前位置信息)，确定为该UE重新选择的新用户面路径；
然后，该SM功能主体生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，该用户面配置指令用于指示该新UP功能主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
最后，该SM功能主体接收该新UP功能主体发送的用户面建立完成消息，并接收该DN侧UP功能主体发送的用户面修改完成消息。
其中，该新UP功能主体具体包括核心网中的新用户面路径上的新RAN侧UP功能主体和其它UP功能主体。该DN侧UP功能主体具体为核心网中的新用户面路径上的与数据网DN连接的用户面。该第三种情况适用于UE自主发起业务请求，也适用于网络发起业务请求。
本公开具体实施例中，在接收到该新UP功能主体发送的用户面建立完成消息和该DN侧UP功能主体发送的用户面修改完成消息后，该SM功能主体还可生成并发送用户面删除指令给该UE的原用户面路径上的原UP功能主体，该用户面删除指令用于指示该原UP功能主体释放与UE的用户面连接，并接收该原UP功能主体发送的用户面删除完成消息。
第四种：UE的用户面路径改变
在第四种情况下，该SM功能主体为UE建立用户面连接的过程为：
首先，该SM功能主体根据该RAN与UE的连接信息和SM相关信息(可包括UE当前位置信息)，确定为该UE重新选择的新用户面路径；
然后，该SM功能主体生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，该用户面配置指令用于指示该新UP功能主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
最后，该SM功能主体接收该新UP功能主体发送的用户面建立完成消息，并接收该DN侧UP功能主体发送的用户面修改完成消息。
本公开具体实施例中，在接收到该新UP功能主体发送的用户面建立完成消息和该DN侧UP功能主体发送的用户面修改完成消息后，该SM功能主体还可生成并发送用户面配置指令给该UE的原用户面路径上的原UP功能主体，该用户面配置指令用于指示该原UP功能主体建立用户面路径，将接收到的数据报文转发给该DN侧UP功能主体，并接收该原UP功能主体发送的用户面修改完成消息。
进一步的，在接收到该原UP功能主体发送的用户面修改完成消息后，该SM功能主体还可开启定时器，该定时器用于确定该原UP功能主体建立的用户面路径的生存期，当该定时器超时时，生成并发送用户面删除指令给该原UP功能主体，该用户面删除指令用于指示该原UP功能主体释放与UE的用户面连接，并接收该原UP功能主体发送的用户面删除完成消息。
本公开实施例中，该终端空闲态的处理方法还可包括：
接收MM功能主体发送的用户面连接去激活请求消息；
根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
接收所述RAN侧UP功能主体发送的用户面修改完成消息；
根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体(具体实现过程可参见第二实施例中记载的内容)。
其中，该用户面连接去激活请求消息携带如下信息中的至少一种：UE标 识、MM上下文标识、基站标识和释放的原因。
其中，该RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息等。
下面，结合图7A～图7J对本公开第四实施例中具体实例的UE从空闲态进入连接态的过程进行说明。
实例一
实例一中，UE自主发起业务请求，UE的用户面路径不变，MM功能主体处理RAN与UE的连接请求。参见图7A所示，该UE进入连接态的过程包括如下步骤：
步骤701：UE发送业务请求消息给RAN；
步骤702：RAN转发该业务请求消息给MM功能主体；
步骤703：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；
步骤704：RAN执行与UE的连接建立；
步骤705：RAN建立完成后，发送连接建立完成消息给MM功能主体；
步骤706：MM功能主体接收到连接建立完成消息后，发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤707：SM功能主体根据SM相关信息和UE当前位置信息，确定该UE的用户面路径不变，生成并发送用户面配置指令(借助用户面修改请求消息发送)给RAN侧UP功能主体，以指示该RAN侧UP功能主体进行下行用户面路径的修改，即接收到下行数据报文时，按照路由或者转发规则发送；
步骤708：RAN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤709：SM功能主体接收到该用户面修改完成消息后，发送用户面连接完成消息给MM功能主体，以完成为UE建立用户面连接。
实例二
实例二中，UE自主发起业务请求，UE的用户面路径不变，SM功能主体处理RAN与UE的连接请求。参见图7B所示，该UE进入连接态的过程 包括如下步骤：
步骤711：UE发送业务请求消息给RAN；
步骤712：RAN转发该业务请求消息给MM功能主体；
步骤713：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤714：SM功能主体发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；此消息可直接发送给RAN，也可由MM功能主体或其它网元转发；
步骤715：RAN执行与UE的连接建立；
步骤716：RAN建立完成后，发送连接建立完成消息给SM功能主体；此消息可直接发送给SM功能主体，也可由MM功能主体或其它网元转发；
步骤717：SM功能主体根据SM相关信息和UE当前位置信息，确定该UE的用户面路径不变，生成并发送用户面配置指令(借助用户面修改请求消息发送)给RAN侧UP功能主体，以指示该RAN侧UP功能主体进行下行用户面路径的修改，即接收到下行数据报文时，按照路由或者转发规则发送；
步骤718：RAN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤719：SM功能主体接收到该用户面修改完成消息后，发送用户面连接完成消息给MM功能主体，以完成为UE建立用户面连接。
实例三
实例三中，UE自主发起业务请求，UE的用户面路径改变，MM功能主体处理RAN与UE的连接请求。参见图7C所示，该UE进入连接态的过程包括如下步骤：
步骤721：UE发送业务请求消息给RAN；
步骤722：RAN转发该业务请求消息给MM功能主体；
步骤723：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；
步骤724：RAN执行与UE的连接建立；
步骤725：RAN建立完成后，发送连接建立完成消息给MM功能主体；
步骤726：MM功能主体接收到连接建立完成消息后，发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤727：SM功能主体根据SM相关信息、UE当前位置信息、业务需求、节点负载、链路的拥塞程度等，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，即发送用户面建立请求消息给新UP功能主体和发送用户面修改请求消息给DN侧UP功能主体，该用户面配置指令用于指示该新UP功能主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
步骤728：新UP功能主体发送用户面建立完成消息给SM功能主体，DN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤729：SM功能主体生成并发送用户面删除指令(借助用户面删除请求消息发送)给原UP功能主体，以指示该原UP功能主体释放与UE的用户面连接；
步骤7210：原UP功能主体发送用户面删除完成消息给SM功能主体；
步骤7211：SM功能主体接收到该用户面删除完成消息后，发送用户面连接完成消息给MM功能主体。
实例四
实例四中，UE自主发起业务请求，UE的用户面路径改变，SM功能主体处理RAN与UE的连接请求。参见图7D所示，该UE进入连接态的过程包括如下步骤：
步骤731：UE发送业务请求消息给RAN；
步骤732：RAN转发该业务请求消息给MM功能主体；
步骤733：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤734：SM功能主体发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；此消息可直接发送给RAN，也可由MM功能主体或其它网元转发；
步骤735：RAN执行与UE的连接建立；
步骤736：RAN建立完成后，发送连接建立完成消息给SM功能主体；此消息可直接发送给SM功能主体，也可由MM功能主体或其它网元转发；
步骤737：SM功能主体根据SM相关信息、UE当前位置信息、业务需求、节点负载、链路的拥塞程度等，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，即发送用户面建立请求消息给新UP功能主体和发送用户面修改请求消息给DN侧UP功能主体，该用户面配置指令用于指示该新UP功能主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
步骤738：新UP功能主体发送用户面建立完成消息给SM功能主体，DN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤739：SM功能主体生成并发送用户面删除指令(借助用户面删除请求消息发送)给原UP功能主体，以指示该原UP功能主体释放与UE的用户面连接；
步骤7310：原UP功能主体发送用户面删除完成消息给SM功能主体；
步骤7311：SM功能主体接收到该用户面删除完成消息后，发送用户面连接完成消息给MM功能主体。
实例五
实例五中，网络发起业务请求，UE的用户面路径改变，MM功能主体处理RAN与UE的连接请求。参见图7E所示，该UE进入连接态的过程包括如下步骤：
步骤741：UE发送业务请求消息给RAN；
步骤742：RAN转发该业务请求消息给MM功能主体；
步骤743：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；
步骤744：RAN执行与UE的连接建立；
步骤745：RAN建立完成后，发送连接建立完成消息给MM功能主体；
步骤746：MM功能主体接收到连接建立完成消息后，发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤747：SM功能主体根据SM相关信息和UE当前位置信息，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令(借助用户面建立请求消息发送)给新RAN侧UP功能主体，以指示该新RAN侧UP功能主体建立路由或转发规则，即将接收到的发送给该UE的上行数据报文路由或者转化给原RAN侧UP功能主体(上行的路由或者转发规则)；同时发送用户面修改请求消息给原RAN侧UP功能主体，以指示该原RAN侧UP功能主体进行用户面路径修改，即将接收到发送给该UE的下行数据报文路由或者转化给新RAN侧UP功能主体(下行的路由或者转发规则)；
步骤748：新RAN侧UP功能主体发送用户面建立完成消息给SM功能主体，原RAN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤749：SM功能主体接收到该用户面建立/修改完成消息后，发送用户面连接完成消息给MM功能主体。
实例六
实例六中，网络发起业务请求，UE的用户面路径改变，SM功能主体处理RAN与UE的连接请求。参见图7F所示，该UE进入连接态的过程包括如下步骤：
步骤751：UE发送业务请求消息给RAN；
步骤752：RAN转发该业务请求消息给MM功能主体；
步骤753：MM功能主体接收到该业务请求消息后，更新UE位置信息并并发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤754：SM功能主体发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；此消息可直接发送给RAN，也可由MM功能主体或其它网元转发；
步骤755：RAN执行与UE的连接建立；
步骤756：RAN建立完成后，发送连接建立完成消息给SM功能主体；此消息可直接发送给SM功能主体，也可由MM功能主体或其它网元转发；
步骤757：SM功能主体根据SM相关信息和UE当前位置信息，确定为 该UE重新选择的新用户面路径，生成并发送用户面配置指令(借助用户面建立请求消息发送)给新RAN侧UP功能主体，以指示该新RAN侧UP功能主体建立路由或转发规则，即将接收到的发送给该UE的上行数据报文路由或者转化给原RAN侧UP功能主体(上行的路由或者转发规则)；同时发送用户面修改请求消息给原RAN侧UP功能主体，以指示该原RAN侧UP功能主体进行用户面路径修改，即将接收到发送给该UE的下行数据报文路由或者转化给新RAN侧UP功能主体(下行的路由或者转发规则)；
步骤758：新RAN侧UP功能主体发送用户面建立完成消息给SM功能主体，原RAN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤759：SM功能主体接收到该用户面建立/修改完成消息后，发送用户面连接完成消息给MM功能主体。
实例七
实例七中，网络发起业务请求，UE的用户面路径改变，MM功能主体处理RAN与UE的连接请求。参见图7G所示，该UE进入连接态的过程包括如下步骤：
步骤761：UE发送业务请求消息给RAN；
步骤762：RAN转发该业务请求消息给MM功能主体；
步骤763：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；
步骤764：RAN执行与UE的连接建立；
步骤765：RAN建立完成后，发送连接建立完成消息给MM功能主体；
步骤766：MM功能主体接收到连接建立完成消息后，发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤767：SM功能主体根据SM相关信息、UE当前位置信息、业务需求、节点负载、链路的拥塞程度等，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，即发送用户面建立请求消息给新UP功能主体和发送用户面修改请求消息给DN侧UP功能主体，该用户面配置指令用于指示该新UP功能 主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
步骤768：新UP功能主体发送用户面建立完成消息给SM功能主体，DN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤769：SM功能主体生成并发送用户面删除指令(借助用户面删除请求消息发送)给原UP功能主体，以指示该原UP功能主体释放与UE的用户面连接，同时对接收到的数据报文进行处理(丢弃)；
步骤7610：原UP功能主体发送用户面删除完成消息给SM功能主体；
步骤7611：SM功能主体接收到该用户面删除完成消息后，发送用户面连接完成消息给MM功能主体。
实例八
实例八中，网络发起业务请求，UE的用户面路径改变，SM功能主体处理RAN与UE的连接请求。参见图7H所示，该UE进入连接态的过程包括如下步骤：
步骤771：UE发送业务请求消息给RAN；
步骤772：RAN转发该业务请求消息给MM功能主体；
步骤773：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤774：SM功能主体发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；此消息可直接发送给RAN，也可由MM功能主体或其它网元转发；
步骤775：RAN执行与UE的连接建立；
步骤776：RAN建立完成后，发送连接建立完成消息给SM功能主体；此消息可直接发送给SM功能主体，也可由MM功能主体或其它网元转发；
步骤777：SM功能主体根据SM相关信息、UE当前位置信息、业务需求、节点负载、链路的拥塞程度等，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，即发送用户面建立请求消息给新UP功能主体和发送用户面修改请求消息给DN侧UP功能主体，该用户面配置指令用于指示该新UP功能 主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
步骤778：新UP功能主体发送用户面建立完成消息给SM功能主体，DN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤779：SM功能主体生成并发送用户面删除指令(借助用户面删除请求消息发送)给原UP功能主体，以指示该原UP功能主体释放与UE的用户面连接，同时对接收到的数据报文进行处理(丢弃)；
步骤7710：原UP功能主体发送用户面删除完成消息给SM功能主体；
步骤7711：SM功能主体接收到该用户面删除完成消息后，发送用户面连接完成消息给MM功能主体。
实例九
实例九中，网络发起业务请求，UE的用户面路径改变，MM功能主体处理RAN与UE的连接请求。参见图7I所示，该UE进入连接态的过程包括如下步骤：
步骤781：UE发送业务请求消息给RAN；
步骤782：RAN转发该业务请求消息给MM功能主体；
步骤783：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；
步骤784：RAN执行与UE的连接建立；
步骤785：RAN建立完成后，发送连接建立完成消息给MM功能主体；
步骤786：MM功能主体接收到连接建立完成消息后，发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤787：SM功能主体根据SM相关信息、UE当前位置信息、业务需求、节点负载、链路的拥塞程度等，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，即发送用户面建立请求消息给新UP功能主体和发送用户面修改请求消息给DN侧UP功能主体，该用户面配置指令用于指示该新UP功能主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修 改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
步骤788：新UP功能主体发送用户面建立完成消息给SM功能主体，DN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤789：SM功能主体生成并发送用户面配置指令(借助用户面修改请求消息发送)给原UP功能主体，以指示该原UP功能主体建立用户面路径，将接收到的数据报文转发给该DN侧UP功能主体；
步骤7810：原UP功能主体发送用户面修改完成消息给SM功能主体；
步骤7811：SM功能主体发送用户面连接完成消息给MM功能主体；
步骤7812：SM功能主体开启定时器，该定时器用于确定该原UP功能主体建立的用户面路径的生存期，保留下行流表；
步骤7813：当该定时器超时时，SM功能主体生成并发送用户面删除指令(借助用户面删除请求消息发送)给该原UP功能主体，以指示该原UP功能主体释放与UE的用户面连接；
步骤7814：原UP功能主体发送用户面删除完成消息给SM功能主体。
实例十
实例十中，网络发起业务请求，UE的用户面路径改变，SM功能主体处理RAN与UE的连接请求。参见图7J所示，该UE进入连接态的过程包括如下步骤：
步骤791：UE发送业务请求消息给RAN；
步骤792：RAN转发该业务请求消息给MM功能主体；
步骤793：MM功能主体接收到该业务请求消息后，更新UE位置信息并发送用户面连接激活请求消息给SM功能主体，包括会话的修改请求；
步骤794：SM功能主体发送连接建立请求消息给RAN，以请求RAN建立与UE的连接，至少包括信令连接、用户面连接和创建UE相关(上下文)信息；此消息可直接发送给RAN，也可由MM功能主体或其它网元转发；
步骤795：RAN执行与UE的连接建立；
步骤796：RAN建立完成后，发送连接建立完成消息给SM功能主体；此消息可直接发送给SM功能主体，也可由MM功能主体或其它网元转发；
步骤797：SM功能主体根据SM相关信息、UE当前位置信息、业务需 求、节点负载、链路的拥塞程度等，确定为该UE重新选择的新用户面路径，生成并发送用户面配置指令给该新用户面路径上的新UP功能主体和DN侧UP功能主体，即发送用户面建立请求消息给新UP功能主体和发送用户面修改请求消息给DN侧UP功能主体，该用户面配置指令用于指示该新UP功能主体建立路由或转发规则，并指示该DN侧UP功能主体进行用户面路径修改，将接收到的发送给该UE的数据报文转发给该新UP功能主体；
步骤798：新UP功能主体发送用户面建立完成消息给SM功能主体，DN侧UP功能主体发送用户面修改完成消息给SM功能主体；
步骤799：SM功能主体生成并发送用户面配置指令(借助用户面修改请求消息发送)给原UP功能主体，以指示该原UP功能主体建立用户面路径，将接收到的数据报文转发给该DN侧UP功能主体；
步骤7910：原UP功能主体发送用户面修改完成消息给SM功能主体；
步骤7911：SM功能主体发送用户面连接完成消息给MM功能主体；
步骤7912：SM功能主体开启定时器，该定时器用于确定该原UP功能主体建立的用户面路径的生存期，保留下行流表；
步骤7913：当该定时器超时时，SM功能主体生成并发送用户面删除指令(借助用户面删除请求消息发送)给该原UP功能主体，以指示该原UP功能主体释放与UE的用户面连接；
步骤7914：原UP功能主体发送用户面删除完成消息给SM功能主体。
本公开第四实施例的终端空闲态的处理方法，在MM功能与SM功能分离的情况下，借助MM功能主体和SM功能主体的信令交互，可为UE建立用户面连接，使UE从空闲态进入连接态，减少控制面与用户面之间的信令开销，缩短进入连接态的时延等。
第五实施例
参见图8所示，本公开第五实施例提供一种终端空闲态的处理装置，应用于MM功能主体，包括：
第一接收模块81，用于接收接入网RAN发送的连接释放请求消息；
第一发送模块82，用于根据所述连接释放请求消息，发送用户面连接去激活请求消息给SM功能主体，所述用户面连接去激活请求消息用于指示所 述SM功能主体修改用户面路径；
第二接收模块83，用于接收所述SM功能主体发送的用户面连接去激活完成消息；
第二发送模块84，用于在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与UE的连接释放。
其中，所述连接释放请求消息或用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
参见图9所示，本公开第五实施例还提供一种终端空闲态的处理装置，应用于SM功能主体，包括：
第三接收模块91，用于接收MM功能主体发送的用户面连接去激活请求消息；
第三发送模块92，用于根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
第四接收模块93，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息；
第四发送模块94，用于根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
其中，所述用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
参见图10所示，本公开第五实施例还提供一种终端空闲态的处理装置，应用于MM功能主体，包括：
第五接收模块111，用于接收RAN转发的来自UE的业务请求消息；
请求模块112，用于根据所述业务请求消息，请求SM功能主体为所述 UE建立用户面连接。
本公开实施例中，所述请求模块112包括：
请求单元，用于根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息；
第一发送单元，用于发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息中携带所述RAN与UE的连接信息，用于指示所述SM功能主体为所述UE建立用户面连接。
其中，所述请求单元包括：
发送子单元，用于根据所述业务请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
接收子单元，用于接收所述RAN发送的连接建立完成消息；
获取子单元，用于根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
本公开实施例中，所述请求模块112包括：
第二发送单元，用于根据所述业务请求消息，发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息用于指示所述SM功能主体请求所述RAN建立与所述UE的连接，获取所述RAN与UE的连接信息，并为所述UE建立用户面连接。
其中，所述RAN建立的与所述UE的连接包括信令连接、用户面连接和/或创建UE上下文信息。
本公开实施例中，所述业务请求消息可由UE自主发起或者网络发起。
当所述业务请求消息由网络发起时，该装置还包括：
第六接收模块，用于接收所述SM功能主体发送的下行数据通知消息；其中，当核心网接收到下行数据报文时，所述SM功能主体根据与所述下行数据报文对应的数据报文标识，匹配保存的UE上下文信息，若找到相关的会话信息，则发送所述下行数据通知消息给所述MM功能主体，否则确定丢弃所述下行数据报文，生成并发送用户面配置指令给RAN侧UP功能主体；
第五发送模块，用于在接收到所述下行数据通知消息后，发送寻呼消息给所述UE，所述寻呼消息用于指示所述UE发起业务请求。
进一步的，在图10所示的终端空闲态的处理装置的基础上，该终端空闲态的处理装置还可包括：
第一接收模块81，用于接收RAN发送的连接释放请求消息；
第一发送模块82，用于根据所述连接释放请求消息，发送用户面连接去激活请求消息给SM功能主体，所述用户面连接去激活请求消息用于指示所述SM功能主体修改用户面路径；
第二接收模块83，用于接收所述SM功能主体发送的用户面连接去激活完成消息；
第二发送模块84，用于在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与UE的连接释放。
其中，该连接释放请求消息或用户面连接去激活请求消息可携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
其中，该RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
参见图11所示，本公开第五实施例还提供一种终端空闲态的处理装置，应用于SM功能主体，包括：
第七接收模块121，用于接收MM功能主体发送的用户面连接激活请求消息；
获取模块122，用于根据所述用户面连接激活请求消息，获取RAN与UE的连接信息；
建立模块123，用于根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
本公开实施例中，所述用户面连接激活请求消息是所述MM功能主体根据接收到的所述RAN转发的来自UE的业务请求消息，请求所述RAN建立与UE的连接之后发送的，其内携带有所述RAN与UE的连接信息。
本公开实施例中，所述获取模块122包括：
第三发送单元，用于根据所述用户面连接激活请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所 述UE的连接；
第一接收单元，用于接收所述RAN发送的连接建立完成消息；
获取单元，用于根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
本公开实施例中，所述建立模块123可包括：
第一确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定所述UE的用户面路径不变；
第四发送单元，用于在确定出所述UE的用户面路径不变后，生成并发送用户面配置指令给所述用户面路径上的RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
第二接收单元，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息。
其中，所述终端空闲态的处理装置还包括：
第六发送模块，用于发送用户面连接完成消息给所述MM功能主体。
本公开实施例中，所述建立模块123可包括：
第二确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
第五发送单元，用于生成并发送用户面配置指令给所述新用户面路径上的新RAN侧UP功能主体，所述用户面配置指令用于指示所述新RAN侧UP功能主体建立路由或转发规则；
第六发送单元，用于发送用户面修改请求消息给所述UE的原用户面路径上的原RAN侧UP功能主体，所述用户面修改请求消息用于指示所述原RAN侧UP功能主体进行用户面路径修改；
第三接收单元，用于接收所述新RAN侧UP功能主体发送的用户面建立完成消息，并接收所述原RAN侧UP功能主体发送的用户面修改完成消息。
本公开实施例中，所述建立模块123可包括：
第三确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
第七发送单元，用于生成并发送用户面配置指令给所述新用户面路径上 的新UP功能主体和DN侧UP功能主体，所述用户面配置指令用于指示所述新UP功能主体建立路由或转发规则，并指示所述DN侧UP功能主体进行用户面路径修改，将接收到的发送给所述UE的数据报文转发给所述新UP功能主体；
第四接收单元，用于接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息。
其中，所述终端空闲态的处理装置还包括：
第七发送模块，用于生成并发送用户面删除指令给所述UE的原用户面路径上的原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
第八接收模块，用于接收所述原UP功能主体发送的用户面删除完成消息。
其中，所述终端空闲态的处理装置还包括：
第八发送模块，用于生成并发送用户面配置指令给所述UE的原用户面路径上的原UP功能主体，所述用户面配置指令用于指示所述原UP功能主体建立用户面路径，将接收到的数据报文转发给所述DN侧UP功能主体；
第九接收模块，用于接收所述原UP功能主体发送的用户面修改完成消息。
其中，所述终端空闲态的处理装置还包括：
开启模块，用于开启定时器，所述定时器用于确定所述原UP功能主体建立的用户面路径的生存期；
第九发送模块，用于当所述定时器超时时，生成并发送用户面删除指令给所述原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
第十接收模块，用于接收所述原UP功能主体发送的用户面删除完成消息。
进一步的，在图11所示的终端空闲态的处理装置的基础上，该终端空闲态的处理装置还可包括：
第三接收模块91，用于接收MM功能主体发送的用户面连接去激活请求 消息；
第三发送模块92，用于根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
第四接收模块93，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息；
第四发送模块94，用于根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
其中，所述用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
本公开第五实施例的终端空闲态的处理装置，在MM功能与SM功能分离的情况下，借助MM功能主体和SM功能主体的信令交互，可使UE进入空闲态，且当UE进入空闲态时，释放掉RAN与UE的连接，依然保持核心网中的用户面连接，有利于业务的快速响应；还可为UE建立用户面连接，使UE从空闲态进入连接态，减少控制面与用户面之间的信令开销，缩短进入连接态的时延等。
第六实施例
参见图12所示，本公开第六实施例提供一种MM功能主体，所述MM功能主体包括第一总线131、第一收发机132、天线133、第一总线接口134、第一处理器135和第一存储器136。
其中，第一处理器135，用于读取第一存储器136中的程序，执行下列过程：
控制第一收发机132接收RAN转发的来自UE的业务请求消息，根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接。
此外，第一处理器135还可执行下列过程：
控制第一收发机132接收RAN发送的连接释放请求消息，根据所述连接释放请求消息，控制第一收发机132发送用户面连接去激活请求消息给SM 功能主体，所述用户面连接去激活请求消息用于指示所述SM功能主体修改用户面路径，控制第一收发机132接收所述SM功能主体发送的用户面连接去激活完成消息，在接收到所述用户面连接去激活完成消息后，控制第一收发机132发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与终端UE的连接释放。
第一收发机132，用于在第一处理器135的控制下接收和发送数据。
在图12中，总线架构(用第一总线131来代表)，第一总线131可以包括任意数量的互联的总线和桥，第一总线131将包括由第一处理器135代表的一个或多个处理器和第一存储器136代表的存储器的各种电路链接在一起。第一总线131还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。第一总线接口134在第一总线131和第一收发机132之间提供接口。第一收发机132可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第一处理器135处理的数据通过天线133在无线介质上进行传输，进一步，天线133还接收数据并将数据传送给第一处理器135。
第一处理器135负责管理第一总线131和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而第一存储器136可以被用于存储第一处理器135在执行操作时所使用的数据。
可选的，第一处理器134可以是CPU、ASIC、FPGA或CPLD。
第七实施例
参见图13所示，本公开第七实施例提供一种SM功能主体，所述SM功能主体包括第二总线141、第二收发机142、天线143、第二总线接口144、第二处理器145和第二存储器146。
其中，第二处理器145，用于读取第二存储器146中的程序，执行下列过程：
控制第二收发机142接收MM功能主体发送的用户面连接激活请求消息，根据所述用户面连接激活请求消息，获取RAN与UE的连接信息，根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
此外，第二处理器145还可执行下列过程：
控制第二收发机142接收MM功能主体发送的用户面连接去激活请求消息，根据所述用户面连接去激活请求消息，控制第二收发机142生成并发送用户面配置指令给RAN侧用户面UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改，控制第二收发机142接收所述RAN侧UP功能主体发送的用户面修改完成消息，根据所述用户面修改完成消息，控制第二收发机142发送用户面连接去激活完成消息给所述MM功能主体。
第二收发机142，用于在第二处理器145的控制下接收和发送数据。
在图13中，总线架构(用第二总线141来代表)，第二总线141可以包括任意数量的互联的总线和桥，第二总线141将包括由第二处理器145代表的一个或多个处理器和第二存储器146代表的存储器的各种电路链接在一起。第二总线141还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。第二总线接口144在第二总线141和第二收发机142之间提供接口。第二收发机142可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第二处理器145处理的数据通过天线143在无线介质上进行传输，进一步，天线143还接收数据并将数据传送给第二处理器145。
第二处理器145负责管理第二总线141和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而第二存储器66可以被用于存储第二处理器145在执行操作时所使用的数据。
可选的，第二处理器144可以是CPU、ASIC、FPGA或CPLD。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本公开实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本公开各个实施例所述的方法。
以上所述仅是本公开的可选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (50)

  1. 一种终端空闲态的处理方法，应用于移动性管理MM功能主体，包括：
    接收接入网RAN转发的来自终端UE的业务请求消息；
    根据所述业务请求消息，请求会话管理SM功能主体为所述UE建立用户面连接。
  2. 根据权利要求1所述的方法，其中，所述根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接的步骤，包括：
    根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息；
    发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息中携带所述RAN与UE的连接信息，用于指示所述SM功能主体为所述UE建立用户面连接。
  3. 根据权利要求2所述的方法，其中，所述根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息的步骤，包括：
    根据所述业务请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
    接收所述RAN发送的连接建立完成消息；
    根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
  4. 根据权利要求1所述的方法，其中，所述根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接的步骤，包括：
    根据所述业务请求消息，发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息用于指示所述SM功能主体请求所述RAN建立与所述UE的连接，获取所述RAN与UE的连接信息，并为所述UE建立用户面连接。
  5. 根据权利要求2-4中任一项所述的方法，其中，所述RAN建立的与所述UE的连接包括信令连接、用户面连接和/或创建UE上下文信息。
  6. 根据权利要求1所述的方法，其中，所述业务请求消息由UE自主发起或者网络发起。
  7. 根据权利要求6所述的方法，其中，当所述业务请求消息由网络发起时，所述接收RAN转发的来自UE的业务请求消息的步骤之前，还包括：
    接收所述SM功能主体发送的下行数据通知消息；其中，当核心网接收到下行数据报文时，所述SM功能主体根据与所述下行数据报文对应的数据报文标识，匹配保存的UE上下文信息，若找到相关的会话信息，则发送所述下行数据通知消息给所述MM功能主体，否则确定丢弃所述下行数据报文，生成并发送用户面配置指令给RAN侧UP功能主体；
    在接收到所述下行数据通知消息后，发送寻呼消息给所述UE，所述寻呼消息用于指示所述UE发起业务请求。
  8. 根据权利要求1所述的方法，还包括：
    接收RAN发送的连接释放请求消息；
    根据所述连接释放请求消息，发送用户面连接去激活请求消息给会话管理SM功能主体，所述用户面连接去激活请求消息用于指示所述SM功能主体修改用户面路径；
    接收所述SM功能主体发送的用户面连接去激活完成消息；
    在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与终端UE的连接释放。
  9. 根据权利要求8所述的方法，其中，所述连接释放请求消息或用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
  10. 根据权利要求8所述的方法，其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
  11. 一种终端空闲态的处理方法，应用于SM功能主体，包括：
    接收MM功能主体发送的用户面连接激活请求消息；
    根据所述用户面连接激活请求消息，获取RAN与UE的连接信息；
    根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
  12. 根据权利要求11所述的方法，其中，所述用户面连接激活请求消息是所述MM功能主体根据接收到的所述RAN转发的来自UE的业务请求消息，请求所述RAN建立与UE的连接之后发送的，其内携带有所述RAN与UE的连接信息。
  13. 根据权利要求11所述的方法，其中，所述根据所述用户面连接激活请求消息，获取RAN与UE的连接信息的步骤，包括：
    根据所述用户面连接激活请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
    接收所述RAN发送的连接建立完成消息；
    根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
  14. 根据权利要求11所述的方法，其中，所述根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接的步骤，包括：
    根据所述RAN与UE的连接信息和SM相关信息，确定所述UE的用户面路径不变；
    在确定出所述UE的用户面路径不变后，生成并发送用户面配置指令给所述用户面路径上的RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
    接收所述RAN侧UP功能主体发送的用户面修改完成消息。
  15. 根据权利要求14所述的方法，其中，所述接收所述RAN侧UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
    发送用户面连接完成消息给所述MM功能主体。
  16. 根据权利要求11所述的方法，其中，所述根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接的步骤，包括：
    根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
    生成并发送用户面配置指令给所述新用户面路径上的新RAN侧UP功能主体，所述用户面配置指令用于指示所述新RAN侧UP功能主体建立路由或转发规则；
    发送用户面修改请求消息给所述UE的原用户面路径上的原RAN侧UP 功能主体，所述用户面修改请求消息用于指示所述原RAN侧UP功能主体进行用户面路径修改；
    接收所述新RAN侧UP功能主体发送的用户面建立完成消息，并接收所述原RAN侧UP功能主体发送的用户面修改完成消息。
  17. 根据权利要求11所述的方法，其中，所述根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接的步骤，包括：
    根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
    生成并发送用户面配置指令给所述新用户面路径上的新UP功能主体和DN侧UP功能主体，所述用户面配置指令用于指示所述新UP功能主体建立路由或转发规则，并指示所述DN侧UP功能主体进行用户面路径修改，将接收到的发送给所述UE的数据报文转发给所述新UP功能主体；
    接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息。
  18. 根据权利要求17所述的方法，其中，所述接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
    生成并发送用户面删除指令给所述UE的原用户面路径上的原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
    接收所述原UP功能主体发送的用户面删除完成消息。
  19. 根据权利要求17所述的方法，其中，所述接收所述新UP功能主体发送的用户面建立完成消息，并接收所述DN侧UP功能主体发送的用户面修改完成消息的步骤之后，还包括：
    生成并发送用户面配置指令给所述UE的原用户面路径上的原UP功能主体，所述用户面配置指令用于指示所述原UP功能主体建立用户面路径，将接收到的数据报文转发给所述DN侧UP功能主体；
    接收所述原UP功能主体发送的用户面修改完成消息。
  20. 根据权利要求19所述的方法，其中，所述接收所述原UP功能主体 发送的用户面修改完成消息的步骤之后，还包括：
    开启定时器，所述定时器用于确定所述原UP功能主体建立的用户面路径的生存期；
    当所述定时器超时时，生成并发送用户面删除指令给所述原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
    接收所述原UP功能主体发送的用户面删除完成消息。
  21. 根据权利要求11所述的方法，还包括：
    接收MM功能主体发送的用户面连接去激活请求消息；
    根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧用户面UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
    接收所述RAN侧UP功能主体发送的用户面修改完成消息；
    根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
  22. 根据权利要求21所述的方法，其中，所述用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
  23. 根据权利要求21所述的方法，其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
  24. 一种终端空闲态的处理装置，应用于MM功能主体，包括：
    第五接收模块，用于接收RAN转发的来自UE的业务请求消息；
    请求模块，用于根据所述业务请求消息，请求SM功能主体为所述UE建立用户面连接。
  25. 根据权利要求24所述的装置，其中，所述请求模块包括：
    请求单元，用于根据所述业务请求消息，请求所述RAN建立与所述UE的连接并获取所述RAN与UE的连接信息；
    第一发送单元，用于发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息中携带所述RAN与UE的连接信息，用于指示 所述SM功能主体为所述UE建立用户面连接。
  26. 根据权利要求25所述的装置，其中，所述请求单元包括：
    发送子单元，用于根据所述业务请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
    接收子单元，用于接收所述RAN发送的连接建立完成消息；
    获取子单元，用于根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
  27. 根据权利要求24所述的装置，其中，所述请求模块包括：
    第二发送单元，用于根据所述业务请求消息，发送用户面连接激活请求消息给所述SM功能主体，所述用户面连接激活请求消息用于指示所述SM功能主体请求所述RAN建立与所述UE的连接，获取所述RAN与UE的连接信息，并为所述UE建立用户面连接。
  28. 根据权利要求25-27中任一项所述的装置，其中，所述RAN建立的与所述UE的连接包括信令连接、用户面连接和/或创建UE上下文信息。
  29. 根据权利要求24所述的装置，其中，所述业务请求消息由UE自主发起或者网络发起。
  30. 根据权利要求29所述的装置，其中，当所述业务请求消息由网络发起时，还包括：
    第六接收模块，用于接收所述SM功能主体发送的下行数据通知消息；其中，当核心网接收到下行数据报文时，所述SM功能主体根据与所述下行数据报文对应的数据报文标识，匹配保存的UE上下文信息，若找到相关的会话信息，则发送所述下行数据通知消息给所述MM功能主体，否则确定丢弃所述下行数据报文，生成并发送用户面配置指令给RAN侧UP功能主体；
    第五发送模块，用于在接收到所述下行数据通知消息后，发送寻呼消息给所述UE，所述寻呼消息用于指示所述UE发起业务请求。
  31. 根据权利要求24所述的装置，还包括：
    第一接收模块，用于接收RAN发送的连接释放请求消息；
    第一发送模块，用于根据所述连接释放请求消息，发送用户面连接去激活请求消息给SM功能主体，所述用户面连接去激活请求消息用于指示所述 SM功能主体修改用户面路径；
    第二接收模块，用于接收所述SM功能主体发送的用户面连接去激活完成消息；
    第二发送模块，用于在接收到所述用户面连接去激活完成消息后，发送连接释放指令给所述RAN，所述连接释放指令用于指示所述RAN执行与UE的连接释放。
  32. 根据权利要求31所述的装置，其中，所述连接释放请求消息或用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
  33. 根据权利要求31所述的装置，其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
  34. 一种终端空闲态的处理装置，应用于SM功能主体，包括：
    第七接收模块，用于接收MM功能主体发送的用户面连接激活请求消息；
    获取模块，用于根据所述用户面连接激活请求消息，获取RAN与UE的连接信息；
    建立模块，用于根据所述RAN与UE的连接信息和SM相关信息，为所述UE建立用户面连接。
  35. 根据权利要求34所述的装置，其中，所述用户面连接激活请求消息是所述MM功能主体根据接收到的所述RAN转发的来自UE的业务请求消息，请求所述RAN建立与UE的连接之后发送的，其内携带有所述RAN与UE的连接信息。
  36. 根据权利要求34所述的装置，其中，所述获取模块包括：
    第三发送单元，用于根据所述用户面连接激活请求消息，发送连接建立请求消息给所述RAN，所述连接建立请求消息用于指示所述RAN建立与所述UE的连接；
    第一接收单元，用于接收所述RAN发送的连接建立完成消息；
    获取单元，用于根据所述连接建立完成消息，获取所述RAN与UE的连接信息。
  37. 根据权利要求34所述的装置，其中，所述建立模块包括：
    第一确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定所述UE的用户面路径不变；
    第四发送单元，用于在确定出所述UE的用户面路径不变后，生成并发送用户面配置指令给所述用户面路径上的RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
    第二接收单元，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息。
  38. 根据权利要求37所述的装置，还包括：
    第六发送模块，用于发送用户面连接完成消息给所述MM功能主体。
  39. 根据权利要求34所述的装置，其中，所述建立模块包括：
    第二确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
    第五发送单元，用于生成并发送用户面配置指令给所述新用户面路径上的新RAN侧UP功能主体，所述用户面配置指令用于指示所述新RAN侧UP功能主体建立路由或转发规则；
    第六发送单元，用于发送用户面修改请求消息给所述UE的原用户面路径上的原RAN侧UP功能主体，所述用户面修改请求消息用于指示所述原RAN侧UP功能主体进行用户面路径修改；
    第三接收单元，用于接收所述新RAN侧UP功能主体发送的用户面建立完成消息，并接收所述原RAN侧UP功能主体发送的用户面修改完成消息。
  40. 根据权利要求34所述的装置，其中，所述建立模块包括：
    第三确定单元，用于根据所述RAN与UE的连接信息和SM相关信息，确定为所述UE重新选择的新用户面路径；
    第七发送单元，用于生成并发送用户面配置指令给所述新用户面路径上的新UP功能主体和DN侧UP功能主体，所述用户面配置指令用于指示所述新UP功能主体建立路由或转发规则，并指示所述DN侧UP功能主体进行用户面路径修改，将接收到的发送给所述UE的数据报文转发给所述新UP功能主体；
    第四接收单元，用于接收所述新UP功能主体发送的用户面建立完成消 息，并接收所述DN侧UP功能主体发送的用户面修改完成消息。
  41. 根据权利要求40所述的装置，还包括：
    第七发送模块，用于生成并发送用户面删除指令给所述UE的原用户面路径上的原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
    第八接收模块，用于接收所述原UP功能主体发送的用户面删除完成消息。
  42. 根据权利要求40所述的装置，还包括：
    第八发送模块，用于生成并发送用户面配置指令给所述UE的原用户面路径上的原UP功能主体，所述用户面配置指令用于指示所述原UP功能主体建立用户面路径，将接收到的数据报文转发给所述DN侧UP功能主体；
    第九接收模块，用于接收所述原UP功能主体发送的用户面修改完成消息。
  43. 根据权利要求42所述的装置，还包括：
    开启模块，用于开启定时器，所述定时器用于确定所述原UP功能主体建立的用户面路径的生存期；
    第九发送模块，用于当所述定时器超时时，生成并发送用户面删除指令给所述原UP功能主体，所述用户面删除指令用于指示所述原UP功能主体释放与所述UE的用户面连接；
    第十接收模块，用于接收所述原UP功能主体发送的用户面删除完成消息。
  44. 根据权利要求34所述的装置，还包括：
    第三接收模块，用于接收MM功能主体发送的用户面连接去激活请求消息；
    第三发送模块，用于根据所述用户面连接去激活请求消息，生成并发送用户面配置指令给RAN侧UP功能主体，所述用户面配置指令用于指示所述RAN侧UP功能主体进行下行用户面路径的修改；
    第四接收模块，用于接收所述RAN侧UP功能主体发送的用户面修改完成消息；
    第四发送模块，用于根据所述用户面修改完成消息，发送用户面连接去激活完成消息给所述MM功能主体。
  45. 根据权利要求44所述的装置，其中，所述用户面连接去激活请求消息携带如下信息中的至少一种：UE标识、MM上下文标识、基站标识和释放的原因。
  46. 根据权利要求44所述的装置，其中，所述RAN释放的与UE的连接包括信令连接、用户面连接和/或删除UE上下文信息。
  47. 一种终端空闲态的处理装置，应用于MM功能主体，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至10中任一项所述的终端空闲态的处理方法中的步骤。
  48. 一种终端空闲态的处理方法，应用于SM功能主体，处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求11至23中任一项所述的终端空闲态的处理方法中的步骤。
  49. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10中任一项所述的终端空闲态的处理方法中的步骤。
  50. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求11至23中任一项所述的终端空闲态的处理方法中的步骤。
PCT/CN2018/075589 2017-01-09 2018-02-07 一种终端空闲态的处理方法及装置 WO2018127231A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/476,244 US10827538B2 (en) 2017-01-09 2018-02-07 User equipment idle state processing method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710013651.8 2017-01-09
CN201710013651.8A CN108616868B (zh) 2017-01-09 2017-01-09 一种终端空闲态的处理方法及装置

Publications (1)

Publication Number Publication Date
WO2018127231A1 true WO2018127231A1 (zh) 2018-07-12

Family

ID=62791329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075589 WO2018127231A1 (zh) 2017-01-09 2018-02-07 一种终端空闲态的处理方法及装置

Country Status (3)

Country Link
US (1) US10827538B2 (zh)
CN (1) CN108616868B (zh)
WO (1) WO2018127231A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020024863A1 (zh) * 2018-07-31 2020-02-06 华为技术有限公司 一种连接建立方法及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107241369B (zh) * 2016-03-28 2020-06-16 电信科学技术研究院 一种数据传输的方法、装置及会话管理功能实体设备
US11647554B2 (en) * 2020-12-21 2023-05-09 T-Mobile Usa, Inc. Intelligent carrier aggregation in millimeter wave resources
CN115038050B (zh) * 2021-03-05 2023-09-05 中国移动通信有限公司研究院 业务通知方法、装置、设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242645A (zh) * 2007-02-09 2008-08-13 华为技术有限公司 移动终端从空闲态进入激活态的方法及系统
CN102348207A (zh) * 2010-07-29 2012-02-08 华为技术有限公司 无线通信系统、mtc器件及网关
CN103686845A (zh) * 2012-09-07 2014-03-26 京信通信系统（中国）有限公司 网络扁平化架构的实现方法、装置及系统
WO2015142048A1 (ko) * 2014-03-19 2015-09-24 엘지전자 주식회사 서비스 요청 절차 수행 방법 및 사용자 장치

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070223450A1 (en) * 2005-09-20 2007-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Minimized setup time for IMS multimedia telephony using PRE provisioned resources reserve at answer
US9125137B2 (en) * 2012-07-26 2015-09-01 Lg Electronics Inc. Method and terminal for applying an extended access barring
EP3163943B1 (en) * 2014-06-24 2020-01-08 Nec Corporation Control node and network node, and method carried out using these
US20180007614A1 (en) * 2015-01-21 2018-01-04 Nec Europe Ltd. Mitigation of signalling congestion in cellular networks
CN106162705B (zh) 2015-03-31 2020-02-04 电信科学技术研究院 一种控制用户面承载建立的方法及设备
CN105813079B (zh) * 2016-05-17 2019-06-07 工业和信息化部电信研究院 一种终端接入方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242645A (zh) * 2007-02-09 2008-08-13 华为技术有限公司 移动终端从空闲态进入激活态的方法及系统
CN102348207A (zh) * 2010-07-29 2012-02-08 华为技术有限公司 无线通信系统、mtc器件及网关
CN103686845A (zh) * 2012-09-07 2014-03-26 京信通信系统（中国）有限公司 网络扁平化架构的实现方法、装置及系统
WO2015142048A1 (ko) * 2014-03-19 2015-09-24 엘지전자 주식회사 서비스 요청 절차 수행 방법 및 사용자 장치

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020024863A1 (zh) * 2018-07-31 2020-02-06 华为技术有限公司 一种连接建立方法及装置

Also Published As

Publication number Publication date
CN108616868A (zh) 2018-10-02
US20190357276A1 (en) 2019-11-21
CN108616868B (zh) 2020-03-06
US10827538B2 (en) 2020-11-03

Similar Documents

Publication Publication Date Title
US11178717B2 (en) Traffic distribution method through multi-access network in a network and network entity performing the same
WO2020001572A1 (zh) 通信方法及装置
EP2717538B1 (en) Communication method and system, access network device, and application server
US11071015B2 (en) Access traffic steering/switching/splitting method in a network and network entity performing the same
WO2020034791A1 (zh) 一种持续在线pdu会话的管理方法及装置
CN111629450B (zh) 一种数据传输方法、相关设备以及存储介质
JP2022500898A (ja) リリースおよびリダイレクトが続く再開の要求
WO2018127231A1 (zh) 一种终端空闲态的处理方法及装置
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
WO2018018631A1 (zh) 一种锚点网关的切换方法、装置及系统
EP3528517B1 (en) Data packet processing method, control plane network element and user plane network element
US10362557B2 (en) Downlink data notification message sending method, and apparatus
WO2019047935A1 (zh) 一种会话建立方法及装置
WO2018170747A1 (zh) 一种通信方法及装置
WO2010105410A1 (zh) 一种建立无线承载的方法、装置及系统
US20220150797A1 (en) Method for performing access control on user equipment, network system, and related device
US11109265B2 (en) Method and apparatus for transmitting control message in software defined network-based mobile communication system
CN109819530B (zh) 一种通信方法及装置
WO2021047454A1 (zh) 位置信息获取、位置服务配置方法和通信设备
CN111629406B (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
WO2022205995A1 (zh) 一种业务流处理方法、装置及系统
WO2018001301A1 (zh) 用户设备的控制方法、装置及系统和网关
KR20200092070A (ko) 무선 통신 시스템에서 등록 관리 방법 및 장치
CN112740824B (zh) 恢复请求随后释放和重定向
JP2018534795A (ja) ダウンリンクデータ通知

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: 18736244

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18736244

Country of ref document: EP

Kind code of ref document: A1