# US 10,375,566 B2 · Methods and nodes for handling updated subscriber data

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

- Number: US 10,375,566 B2
- Document ID: US10375566B2
- Status: Granted
- Kind: B2
- Application number: 15/893,482
- Filed: 2018-02-09
- Published: 2018-06-14
- Granted: 2019-08-06
- Earliest claimed: 2018-02-09
- Assignees: Telefonaktiebolaget L M Ericsson (publ)
- Applicants: Telefonaktiebologet LM Ericsson (publ)
- Inventors: Yong Yang; Roland Gustafsson; Gunnar Rydnell
- Web page: https://patentgrep.com/patent/US10375566B2

## CPC

- H04W 8/12: between location registers or mobility servers
- H04L 1/02: by diversity reception
- H04L 1/04: using frequency diversity
- H04L 5/003: {Arrangements for allocating sub-channels of the transmission path}
- H04L 5/0057: {Physical resource allocation for CQI}
- H04L 5/02: Channels characterised by the type of signal
- H04W 24/02: Arrangements for optimising operational condition
- H04W 76/18: Management of setup rejection or failure
- H04W 76/28: Discontinuous transmission [DTX]; Discontinuous reception [DRX]
- H04W 8/06: Registration at serving network Location Register, VLR or user mobility server
- H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The embodiments herein relate to a method in a first mobility management node (108a) for handling updated subscriber data associated with a UE (101). The UE (101) is currently unreachable by the first mobility management node (108a). The first mobility management node (108a) receives, from a subscriber database (128), updated subscriber data associated with the UE (101). At least part of the updated subscriber data is modified. The first mobility management node (108a) determines that transmission of the updated subscriber data to a gateway node (110) should be postponed until the UE (101) has become reachable.

## Claims

### Claim 1

A method in a first mobility management node for handling updated subscriber data associated with a User Equipment, UE, the UE being currently unreachable by the first mobility management node and wherein the updated subscriber data comprises Quality of Service, QoS, parameters, the method comprising:
receiving, from a subscriber database, updated subscriber data associated with the UE, wherein at least part of the updated subscriber data is modified; and
determining that transmission of the updated subscriber data to a gateway node should be postponed until the UE has become reachable;
where the UE is unreachable by the first mobility management node because a Paging Proceed Flag, PPF, associated with the UE is cleared in the first mobility management node.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
setting an indication indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 3 (depends on 2)

The method according to claim 2, further comprising:
clearing the indication when the at least part of the updated subscriber data which is modified has been transmitted to the gateway node.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising:
determining that the UE has become reachable by the first mobility management node; and
transmitting at least the part of the updated subscriber data which is modified to the gateway node.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising:
determining, that the UE has become reachable by a second mobility management node; and
transmitting, to the second mobility node, information indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the information transmitted to the second mobility node is an indication indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the first mobility management node is a Mobility Management Entity, MME, or a Serving General packet radio service Support Node, SGSN, or a combined MME and SGSN node.

### Claim 8 (depends on 5)

The method according to claim 5, wherein the second mobility management node is a Mobility Management Entity, MME, or a Serving General packet radio service Support Node, SGSN, or a combined MME and SGSN node.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the gateway node is a Serving GateWay, SGW, or a Packet data network GateWay, PGW or a combined SGW and PGW node.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the subscriber database is a Home Subscriber Server, HSS, or a Home Location Register, HLR.

### Claim 11

A method in a second mobility management node for handling updated subscriber data associated with a User Equipment, UE wherein the updated subscriber data comprises Quality of Service, QoS, parameters, the method comprising:
determining that the UE has become reachable by the second mobility management node when a Paging Proceed Flag, PPF, associated with the UE is cleared;
receiving, from a first mobility management node, information indicating that there is updated subscriber data waiting to be transmitted to a gateway node where a transmission of the updated subscriber data to the gateway node was postponed by the first mobility management node because the UE was unreachable;
receiving the updated subscriber data from a subscriber database, wherein at least part of the updated subscriber data is modified; and
transmitting the updated subscriber data to the gateway node.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the received information is an indication indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 13 (depends on 12)

The method according to claim 12, further comprising:
clearing the indication when the updated subscriber data has been transmitted to the gateway node.

### Claim 14 (depends on 11)

The method according to claim 11, wherein the first mobility management node is a first Mobility Management Entity, MME, and the second mobility management node is a second MME, or
wherein the first mobility management node is a first Serving General packet radio service Support Node, SGSN, and the second mobility management node is a second SGSN, or
wherein the first mobility management node is a first combined MME and SGSN node and the second mobility management node is a second combined MME and SGSN node.

### Claim 15 (depends on 11)

The method according to claim 11, wherein the gateway node is a Serving GateWay, SGW, or a Packet data network GateWay, PGW or a combined SGW and PGW node.

### Claim 16

A first mobility management node for handling updated subscriber data associated with a User Equipment, UE wherein the updated subscriber data comprises Quality of Service, QoS, parameters, the UE being currently unreachable by the first mobility management node, the first mobility management node being configured to:
receive, from a subscriber database, updated subscriber data associated with the UE, wherein at least part of the updated subscriber data is modified; and to
determine that transmission of the updated subscriber data to a gateway node should be postponed until the UE has become reachable;
where the UE is unreachable by the first mobility management node because a Paging Proceed Flag, PPF, associated with the UE is cleared in the first mobility management node.

### Claim 17 (depends on 16)

The first mobility management node according to claim 16, being further configured to:
set an indication indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 18 (depends on 17)

The first mobility management node according to claim 17, being further configured to:
clear the indication when the at least part of the updated subscriber data which is modified has been transmitted to the gateway node.

### Claim 19 (depends on 16)

The first mobility management node according to claim 16, being further configured to:
determine that the UE has become reachable by the first mobility management node; and to
transmit at least the part of the updated subscriber data which is modified to the gateway node.

### Claim 20 (depends on 16)

The first mobility management node according to claim 16, being further configured to:
determine, that the UE has become reachable by a second mobility management node; and to
transmit, to the second mobility node, information indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 21 (depends on 20)

The first mobility management node according to claim 20, wherein the information transmitted to the second mobility node is an indication indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 22 (depends on 16)

The first mobility management node according to claim 16, wherein the first mobility management node is a Mobility Management Entity, MME, or a Serving General packet radio service Support Node, SGSN, or a combined MME and SGSN node.

### Claim 23 (depends on 20)

The first mobility management node according to claim 20, wherein the second mobility management node is a Mobility Management Entity, MME, or a Serving General packet radio service Support Node, SGSN, or a combined MME and SGSN node.

### Claim 24 (depends on 16)

The first mobility management node according to claim 16, wherein the gateway node is a Serving GateWay, SGW, or a Packet data network GateWay, PGW or a combined SGW and PGW node.

### Claim 25 (depends on 16)

The first mobility management node according to claim 16, wherein the subscriber database is a Home Subscriber Server, HSS, or a Home Location Register, HLR.

### Claim 26

A second mobility management node for handling updated subscriber data associated with a User Equipment, UE wherein the updated subscriber data comprises Quality of Service, QoS, parameters, the second mobility management node being configured to:
determine that the UE has become reachable by the second mobility management node when a Paging Proceed Flag, PPF, associated with the UE is cleared;
receive, from a first mobility management node, information indicating that there is updated subscriber data waiting to be transmitted to a gateway node where a transmission of the updated subscriber data to the gateway node was postponed by the first mobility management node because the UE was unreachable;
receive the updated subscriber data from a subscriber database, wherein at least part of the updated subscriber data is modified; and
transmit the updated subscriber data to the gateway node.

### Claim 27 (depends on 26)

The second mobility management node according to claim 26, wherein the received information is an indication indicating that there is updated subscriber data waiting to be transmitted to the gateway node.

### Claim 28 (depends on 27)

The second mobility management node according to claim 27, being further configured to:
clear the indication when the updated subscriber data has been transmitted to the gateway node.

### Claim 29 (depends on 26)

The second mobility management node according to claim 26, wherein the first mobility management node is a first Mobility Management Entity, MME, and the second mobility management node is a second MME, or
wherein the first mobility management node is a first Serving General packet radio service Support Node, SGSN, and the second mobility management node is a second SGSN, or
wherein the first mobility management node is a first combined MME and SGSN node and the second mobility management node is a second combined MME and SGSN node.

### Claim 30 (depends on 26)

The second mobility management node according to claim 26, wherein the gateway node is a Serving GateWay, SGW, or a Packet data network GateWay, PGW or a combined SGW and PGW node.