Sign In to Follow Application
View All Documents & Correspondence

Mobile Communication Method, Mobile Management Nodes, And Serving Gateways

Abstract: A mobile communication method in a mobile communication system according to the present invention in which when MME#1 is restarted in a first state in which a PDN connection #1 including one or more EPS bearers #1 is set among a UE, an S-GW#1, and a P-GW#1, the first state transitions to a second state in which the PDN connection #1 is released between the UE and the S-GW#1 and the connection is maintained only between the S-GW#1 and the P-GW#1, the mobile communication method including the step of not transmitting, by the MME#1, "Paging" whose destination is the UE upon receiving "DDN" including IMSI of the UE after detecting that re-attach processing for the mobile station has been executed in the second state. Fig 2.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
07 November 2019
Publication Number
46/2019
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
patent@depenning.com
Parent Application

Applicants

NEC Corporation
7-1, Shiba 5-chome, Minato-ku, Tokyo 108-8001, Japan

Inventors

1. NISHIDA, Katsutoshi
c/o Intellectual Property Department, NTT DOCOMO, INC., Sanno Park Tower, 11-1, Nagatacho 2-chome, Chiyoda-ku, Tokyo 100-6150, Japan
2. TAMURA, Toshiyuki
c/o NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo 108-8001, Japan

Claims

1. A system comprising: a terminal; a first core network node; a second core network node; a device for managing subscriber information; and a gateway; wherein a connection between the terminal and the first core network node has been established, the terminal is configured to: send an Attach Request to the second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send an Update Location Request to the device, the device is configured to: receive the Update Location Request from the second core network node, then send a Cancel Location Request to the first core network node, and the first core network node is configured to: send a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to the gateway based on having received the Cancel Location Request from the device.

2. A terminal, wherein a connection between the terminal and a first core network node has been established, configured to: send an Attach Request to a second core network node after the first core network node restarts, so that the second core network node sends an Update Location Request to a device for managing subscriber information, and then the device sends a Cancel Location Request to the first core network node, and the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device.

3. A first core network node, wherein a connection between a terminal and the first core network node has been established, configured to: send a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received a Cancel Location Request from a device for managing subscriber information, wherein the terminal is configured to: send an Attach Request to a second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send an Update Location Request to the device, and the device is configured to: receive the Update Location Request from the second core network node, then send the Cancel Location Request to the first core network node.

4. A second core network node, wherein a connection between a terminal and a first core network node has been established, configured to: receive an Attach Request from the terminal, then send an Update Location Request to a device for managing subscriber information, so that the device sends a Cancel Location Request to the first core network node, and the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device, wherein the terminal is configured to: send the Attach Request to the second core network node after the first core network node restarts.

5. A device for managing subscriber information, wherein a connection between a terminal and a first core network node has been established, configured to: receive an Update Location Request from a second core network node, then send a Cancel Location Request to the first core network node, so that the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device, wherein the terminal is configured to: send an Attach Request to the second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send the Update Location Request to the device.

6. A gateway, wherein a connection between a terminal and a first core network node has been established, configured to: receive a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure from the first core network node, wherein the terminal is configured to: send an Attach Request to a second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send an Update Location Request to a device for managing subscriber information, the device is configured to: receive the Update Location Request from the second core network node, then send a Cancel Location Request to the first core network node, and the first core network node is configured to: send the Downlink Data Notification Acknowledge or the Downlink Data Notification Failure to the gateway based on having received the Cancel Location Request from the device.

7. A method, wherein a connection between a terminal and a first core network node has been established, comprising: sending an Attach Request to a second core network node after the first core network node restarts, so that the second core network node sends an Update Location Request to a device for managing subscriber information, and then the device sends a Cancel Location Request to the first core network node, and the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device. 8. A method, wherein a connection between a terminal and a first core network node has been established, comprising: sending a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received a Cancel Location Request from a device for managing subscriber information, wherein the terminal is configured to: send an Attach Request to a second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send an Update Location Request to the device, and the device is configured to: receive the Update Location Request from the second core network node, then send the Cancel Location Request to the first core network node.

9. A method, wherein a connection between a terminal and a first core network node has been established, comprising: receiving an Attach Request from the terminal; then sending an Update Location Request to a device for managing subscriber information, so that the device sends a Cancel Location Request to the first core network node, and the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device, wherein the terminal is configured to: send the Attach Request to a second core network node after the first core network node restarts.

10. A method, wherein a connection between a terminal and a first core network node has been established, comprising: receiving an Update Location Request from a second core network node; then sending a Cancel Location Request to the first core network node, so that the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from a device for managing subscriber information, wherein the terminal is configured to: send an Attach Request to the second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send the Update Location Request to the device.

11. A method, wherein a connection between a terminal and a first core network node has been established, comprising: receiving a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure from the first core network node, wherein the terminal is configured to: send an Attach Request to a second core network node after the first core network node restarts, the second core network node is configured to: receive the Attach Request from the terminal, then send an Update Location Request to a device for managing subscriber information, the device is configured to: receive the Update Location Request from the second core network node, then send a Cancel Location Request to the first core network node, and the first core network node is configured to: send the Downlink Data Notification Acknowledge or the Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device.

Specification

We Claim:
1. A system comprising:
a terminal;
a first core network node;
a second core network node;
a device for managing subscriber information; and
a gateway; wherein
a connection between the terminal and the first core network node has been established,
the terminal is configured to:
send an Attach Request to the second core network node after the first core network node restarts,
the second core network node is configured to:
receive the Attach Request from the terminal, then
send an Update Location Request to the device,
the device is configured to:
receive the Update Location Request from the second core network node, then
send a Cancel Location Request to the first core network node, and the first core network node is configured to:
send a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to the gateway based on having received the Cancel Location Request from the device.
2. A terminal, wherein a connection between the terminal and a
first core network node has been established, configured to:
send an Attach Request to a second core network node after the first core network node restarts, so that

the second core network node sends an Update Location Request to a device for managing subscriber information, and then
the device sends a Cancel Location Request to the first core network node, and
the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device.
3. A first core network node, wherein a connection between a terminal and the first core network node has been established, configured to:
send a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received a Cancel Location Request from a device for managing subscriber information, wherein
the terminal is configured to:
send an Attach Request to a second core network node after the first core network node restarts,
the second core network node is configured to:
receive the Attach Request from the terminal, then
send an Update Location Request to the device, and
the device is configured to:
receive the Update Location Request from the second core network node, then
send the Cancel Location Request to the first core network node.

4. A second core network node, wherein a connection between a
terminal and a first core network node has been established, configured
to:
receive an Attach Request from the terminal, then send an Update Location Request to a device for managing subscriber information, so that
the device sends a Cancel Location Request to the first core network node, and
the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device, wherein
the terminal is configured to:
send the Attach Request to the second core network node after the first core network node restarts.
5. A device for managing subscriber information, wherein a
connection between a terminal and a first core network node has been
established, configured to:
receive an Update Location Request from a second core network node, then send a Cancel Location Request to the first core network node, so that
the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device, wherein
the terminal is configured to:
send an Attach Request to the second core network node after the first core network node restarts,
the second core network node is configured to:

receive the Attach Request from the terminal, then send the Update Location Request to the device.
6. A gateway, wherein a connection between a terminal and a first
core network node has been established, configured to:
receive a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure from the first core network node, wherein
the terminal is configured to:
send an Attach Request to a second core network node after the first core network node restarts,
the second core network node is configured to:
receive the Attach Request from the terminal, then
send an Update Location Request to a device for managing subscriber information,
the device is configured to:
receive the Update Location Request from the second core network node, then
send a Cancel Location Request to the first core network node, and
the first core network node is configured to:
send the Downlink Data Notification Acknowledge or the Downlink Data Notification Failure to the gateway based on having received the Cancel Location Request from the device.
7. A method, wherein a connection between a terminal and a first
core network node has been established, comprising:

sending an Attach Request to a second core network node after the first core network node restarts, so that
the second core network node sends an Update Location Request to a device for managing subscriber information, and then
the device sends a Cancel Location Request to the first core network node, and
the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device. 8. A method, wherein a connection between a terminal and a first core network node has been established, comprising:
sending a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received a Cancel Location Request from a device for managing subscriber information, wherein
the terminal is configured to:
send an Attach Request to a second core network node after the first core network node restarts,
the second core network node is configured to:
receive the Attach Request from the terminal, then
send an Update Location Request to the device, and
the device is configured to:
receive the Update Location Request from the second core network node, then
send the Cancel Location Request to the first core network node.
9. A method, wherein a connection between a terminal and a first core network node has been established, comprising:

receiving an Attach Request from the terminal; then
sending an Update Location Request to a device for managing subscriber information, so that
the device sends a Cancel Location Request to the first core network node, and
the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device, wherein
the terminal is configured to:
send the Attach Request to a second core network node after the first core network node restarts.
10. A method, wherein a connection between a terminal and a first core network node has been established, comprising:
receiving an Update Location Request from a second core network node; then
sending a Cancel Location Request to the first core network node, so that
the first core network node sends a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from a device for managing subscriber information, wherein
the terminal is configured to:
send an Attach Request to the second core network node after the first core network node restarts,
the second core network node is configured to:
receive the Attach Request from the terminal, then
send the Update Location Request to the device.

11. A method, wherein a connection between a terminal and a first core network node has been established, comprising:
receiving a Downlink Data Notification Acknowledge or a Downlink Data Notification Failure from the first core network node, wherein
the terminal is configured to:
send an Attach Request to a second core network node after the first core network node restarts,
the second core network node is configured to:
receive the Attach Request from the terminal, then
send an Update Location Request to a device for managing subscriber information,
the device is configured to:
receive the Update Location Request from the second core network node, then
send a Cancel Location Request to the first core network node, and
the first core network node is configured to:
send the Downlink Data Notification Acknowledge or the Downlink Data Notification Failure to a gateway based on having received the Cancel Location Request from the device.

Documents

Application Documents

# Name Date
1 201948045282-TRANSLATIOIN OF PRIOIRTY DOCUMENTS ETC. [07-11-2019(online)].pdf 2019-11-07
2 201948045282-STATEMENT OF UNDERTAKING (FORM 3) [07-11-2019(online)].pdf 2019-11-07
3 201948045282-REQUEST FOR EXAMINATION (FORM-18) [07-11-2019(online)].pdf 2019-11-07
4 201948045282-PRIORITY DOCUMENTS [07-11-2019(online)].pdf 2019-11-07
5 201948045282-POWER OF AUTHORITY [07-11-2019(online)].pdf 2019-11-07
6 201948045282-FORM 18 [07-11-2019(online)].pdf 2019-11-07
7 201948045282-FORM 1 [07-11-2019(online)].pdf 2019-11-07
8 201948045282-DRAWINGS [07-11-2019(online)].pdf 2019-11-07
9 201948045282-DECLARATION OF INVENTORSHIP (FORM 5) [07-11-2019(online)].pdf 2019-11-07
10 201948045282-COMPLETE SPECIFICATION [07-11-2019(online)].pdf 2019-11-07
11 Abstract 201948045282.jpg 2019-11-11
12 201948045282-FORM 3 [01-05-2020(online)].pdf 2020-05-01
13 201948045282-FER.pdf 2021-10-18
14 201948045282-OTHERS [24-11-2021(online)].pdf 2021-11-24
15 201948045282-Information under section 8(2) [24-11-2021(online)].pdf 2021-11-24
16 201948045282-Information under section 8(2) [24-11-2021(online)]-5.pdf 2021-11-24
17 201948045282-Information under section 8(2) [24-11-2021(online)]-4.pdf 2021-11-24
18 201948045282-Information under section 8(2) [24-11-2021(online)]-3.pdf 2021-11-24
19 201948045282-Information under section 8(2) [24-11-2021(online)]-2.pdf 2021-11-24
20 201948045282-Information under section 8(2) [24-11-2021(online)]-1.pdf 2021-11-24
21 201948045282-FORM 3 [24-11-2021(online)].pdf 2021-11-24
22 201948045282-FER_SER_REPLY [24-11-2021(online)].pdf 2021-11-24
23 201948045282-DRAWING [24-11-2021(online)].pdf 2021-11-24
24 201948045282-CLAIMS [24-11-2021(online)].pdf 2021-11-24
25 201948045282-ABSTRACT [24-11-2021(online)].pdf 2021-11-24
26 201948045282-US(14)-HearingNotice-(HearingDate-29-04-2024).pdf 2023-12-12
27 201948045282-US(14)-HearingNotice-(HearingDate-13-01-2025).pdf 2024-11-27
28 201948045282-Correspondence to notify the Controller [09-01-2025(online)].pdf 2025-01-09

Search Strategy

1 2021-05-2317-47-31E_24-05-2021.pdf