# US 2019/0380167 A1 · Method of processing ue idle state, mobility management mm function entity, and session management sm function entity

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0380167 A1
- Document ID: US20190380167A1
- Status: Published application
- Kind: A1
- Application number: 16/476,808
- Filed: 2018-02-08
- Published: 2019-12-12
- Earliest claimed: 2017-01-09
- Assignees: China Academy of Telecommunications Technology
- Applicants: China Academy of Telecommunications Technology
- Inventors: Zhimi CHENG; Weiqi HU; Hui XU
- Web page: https://patentgrep.com/patent/US20190380167A1

## CPC

- H04W 76/22: Manipulation of transport tunnels
- H04W 76/30: Connection release
- H04W 8/08: Mobility data transfer
- H04W 76/11: Allocation or use of connection identifiers
- H04W 76/34: Selective release of ongoing connections
- H04W 80/10: adapted for {application} session management, e.g. SIP [Session Initiation Protocol] {(connection management H04W76/00; arrangements for session management H04L67/14)}
- H04W 76/15: Setup of multiple wireless link connections
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure provides a method of processing UE idle state, a mobility management (MM) entity, and a session management (SM) function entity. The method includes: receiving, by the mobility management MM function entity, a connection release request sent by an access network entity, wherein the connection release request carries identifier information of the UE; and sending, by the MM function entity, a user plane connection deactivation request to the SM function entity according to the connection release request, the user plane connection deactivation request is used to request the SM function entity to delete the user plane connection of the UE, and maintain the signaling plane connection of the UE. In this way, after the UE is in an idle state, the user plane between the UE and the core network is not maintained, but the signaling plane remains.

## Claims

### Claim 1

A method of processing user terminal (UE) idle state, comprising:
receiving, by a mobility management (MM) function entity, a connection release request sent by an access network entity, wherein the connection release request carries identity information of the UE;
sending, by the MM function entity, a user plane connection deactivation request to a SM function entity according to the connection release request, the user plane connection deactivation request is used to request the SM function entity to delete a user plane connection of the UE, and maintain a signaling plane connection of the UE.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
receiving, by the MM function entity, a user plane connection deactivation completion message sent by the SM function entity;
sending, by the MM function entity, a connection release instruction to the access network entity according to the user plane connection deactivation completion message, the connection release instruction is used to instruct the access network entity to release a signaling plane connection and a user plane connection between the access network entity and the UE, and UE context information.

### Claim 3 (depends on 2)

The method according to claim 2, further comprising:
receiving, by the MM function entity, a service request message sent by the access network entity, wherein the service request message carries the identity information of the UE;
sending, by the MM function entity, a connection establishment request message to the access network entity according to the service request message, the connection establishment request message is used to instruct the access network entity to establish a signaling plane connection and a user plane connection between the access network entity and the UE, and UE context information.

### Claim 4 (depends on 3)

The method according to claim 3 further comprising:
receiving, by the MM function entity, a connection establishment completion message sent by the access network entity;
sending, by the MM function entity, a user plane connection activation request to the SM function entity according to the connection establishment completion message, the user plane connection activation request message is used to request the SM function entity to create a user plane connection of the UE.

### Claim 5 (depends on 2)

The method according to claim 2, further comprising:
receiving, by the MM function entity, a downlink data packet report (DDN) sent by the SM function entity, where the DDN carries an identifier information of a target UE;
paging, by the MM function entity, the target UE according to the DDN.

### Claim 6

A method of processing user terminal (UE) idle state, comprising:
receiving, by a session management (SM) function entity, a user plane connection deactivation request sent by a mobility management (MM) function entity, wherein the user plane connection deactivation request carries identity information of the UE;
deleting, by the SM function entity, a user plane connection of the UE according to the user plane connection deactivation request, and maintains a signaling plane connection of the UE.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the SM function entity deletes the user plane connection of the UE according to the user plane connection deactivation request, comprising:
sending, by the SM function entity, a first user plane configuration instruction to the user plane (UP) function entity that serves the UE according to the user plane connection deactivation request, the first user plane configuration instruction is used to instruct the UP function entity that serves the UE to modify a user plane configuration of the UE.

### Claim 8 (depends on 7)

The method according to claim 7, further comprising:
receiving, by the SM function entity, a user plane configuration completion message sent by the UP function entity;
sending, by the SM function entity, a user plane connection deactivation completion message to the MM function entity according to the user plane configuration completion message.

### Claim 9 (depends on 7)

The method according to claim 7, wherein the UP function entity that serves the UE comprises at least an access network (AN) side UP function entity and a data network (DN) side UP function entity, the first user plane configuration instruction is used to instruct the DN side UP function entity to modify a user plane of the UE, and is used to instruct UP function entities other than the DN side UP function entity on the UE user plane connection to delete a user plane connection of the UE.

### Claim 10 (depends on 6)

The method according to claim 6 further comprising:
receiving, by the SM function entity, a user plane connection activation request sent by the MM function entity;
selecting, by the SM function entity, a target UP function entity for the UE according to the user plane connection activation request and session related information, wherein the target UP function entity is an UP function entity other than the DN side UP function entity;
sending, by the SM function entity, a second user plane configuration instruction to the target UP function entity, the second user plane configuration instruction is used to instruct the target UP function entity to establish a user plane connection with the UE, and is used to instruct the DN side UP function entity to modify the user plane of the UE.

### Claim 11 (depends on 10)

The method according to claim 10, wherein the session related information comprises at least one of the following:
location information of UE, service requirements, node load, and congestion level of a link.

### Claim 12 (depends on 9)

The method according to claim 9 further comprising:
receiving, by the SM function entity, data packet identifier information sent by the DN side UP function entity;
searching, by the SM function entity, the session information related to the target UE in the stored UE context according to the data packet identifier information;
if the session information related to the target UE is found, the SM function entity sends a downlink data packet report (DDN) to the MM function entity;
if the session information related to the target UE is not found, the SM function entity sends a third user plane configuration instruction to the DN side UP function entity, the third user plane configuration instruction is used to instruct the DN side UP function entity to discard data packet corresponding to the data packet identifier.

### Claim at position 13

13-24. (canceled)

### Claim 25 (depends on 1)

A mobility management (MM) function entity, comprising:
a processor, a transceiver, a memory, a user interface, and a bus interface, wherein the processor is configured to read a program in the memory to perform the method of processing UE idle state as claimed in claim 1, the transceiver is configured to receive and send data under control of the processor.

### Claim 26 (depends on 6)

A session management (SM) function entity, comprising: a processor, a transceiver, a memory, a user interface, and a bus interface, wherein the processor is configured to read a program in the memory to perform the method of processing UE idle state as claimed in claim 6, wherein the transceiver is configured to receive and send data under control of the processor.

### Claim at position 16

27-28. (canceled)

### Claim 29 (depends on 25)

The MM function entity of claim 25, wherein the processor is further configured to perform:
receiving a user plane connection deactivation completion message sent by the SM function entity;
sending a connection release instruction to the access network entity according to the user plane connection deactivation completion message, the connection release instruction is used to instruct the access network entity to release a signaling plane connection and a user plane connection between the access network entity and the UE, and UE context information.

### Claim 30 (depends on 29)

The MM function entity of claim 29, wherein the processor is further configured to perform:
receiving a service request message sent by the access network entity, wherein the service request message carries the identity information of the UE;
sending a connection establishment request message to the access network entity according to the service request message, the connection establishment request message is used to instruct the access network entity to establish a signaling plane connection and a user plane connection between the access network entity and the UE, and UE context information.
receiving, by the MM function entity, a connection establishment completion message sent by the access network entity;

### Claim 31 (depends on 30)

The MM function entity of claim 30, wherein the processor is further configured to perform:
receiving a connection establishment completion message sent by the access network entity; and
sending a user plane connection activation request to the SM function entity according to the connection establishment completion message, the user plane connection activation request message is used to request the SM function entity to create a user plane connection of the UE.

### Claim 32 (depends on 26)

The SM function entity of claim 26, wherein the processor is further configured to perform:
sending a first user plane configuration instruction to the user plane (UP) function entity that serves the UE according to the user plane connection deactivation request, the first user plane configuration instruction is used to instruct the UP function entity that serves the UE to modify a user plane configuration of the UE.

### Claim 33 (depends on 32)

The SM function entity of claim 32, wherein the processor is further configured to perform:
receiving a user plane configuration completion message sent by the UP function entity;
sending a user plane connection deactivation completion message to the MM function entity according to the user plane configuration completion message.

### Claim 34 (depends on 26)

The SM function entity of claim 26, wherein the processor is further configured to perform:
receiving a user plane connection activation request sent by the MM function entity;
selecting a target UP function entity for the UE according to the user plane connection activation request and session related information, wherein the target UP function entity is an UP function entity other than the DN side UP function entity; and
sending a second user plane configuration instruction to the target UP function entity, the second user plane configuration instruction is used to instruct the target UP function entity to establish a user plane connection with the UE, and is used to instruct the DN side UP function entity to modify the user plane of the UE.
