Providing user equipment location information indication on user plane

• US 10,285,155 B1
• Filed: 09/24/2018
• Issued: 05/07/2019
• Est. Priority Date: 09/24/2018
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Dodd-Noble, Aeneas Sean, Garvia, Pablo Camarillo, Suthar, Om Prakash
• Primary Examiner(s): Bhattacharya, Sam
• Application Number:
  US16/140,255
• Time in Patent Office: 225 Days
• Field of Search: 4554141, 4554561, 4554563, 370242, 370331, 370338
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 2212/00 Encapsulation of packets
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 64/003 locating network equipment
• CPC Class Codes: H04W 8/08 Mobility data transfer
• CPC Class Codes: H04W 8/16 selectively restricting mobility data tracking
• CPC Class Codes: H04W 8/24 Transfer of terminal data

Abstract

Aspects of the disclosed technology provide ways to report User Equipment (UE) device locations in a 5G network for the purpose of redirecting application traffic from proximately located Data Networks (DNs). In one aspect, the disclosed technology encompasses a process for conveying User Equipment (UE) information to an Application Function (AF), the process includes steps for receiving, at an intermediate-User Plane Function (I-UPF) entity, User Equipment (UE) uplink data from a Radio Access Network (RAN), determining if sharing of location information or application information associated with the UE is restricted, and encapsulating first location metadata or application metadata in an SRv6 packet if the sharing of location information or application information is not restricted. Systems and machine-readable media are also provided.

Claims

1. A method for conveying User Equipment (UE) information to an Application Function (AF), the method comprising:

receiving, at an intermediate-User Plane Function (I-UPF) entity, User Equipment (UE) uplink data from a Radio Access Network (RAN), wherein the UE uplink data originated from a User Equipment (UE) device;

determining, at the I-UPF entity, if sharing of location information or application information associated with the UE is restricted;

encapsulating, by the I-UPF entity, first location metadata or application metadata in an SRv6 packet if the sharing of location information or application information is not restricted; and

transmitting the SRv6 packet to an anchor-User Plane Function (A-UPF) entity for forwarding to a Data Network (DN), wherein the SRv6 packet is configured to cause the DN to transmit a first location report to at least one Application Function (AF) entity associated with an application associated with the UE device.

2. The method of claim 1, wherein the first location metadata comprises one or more of:

a Tracking Area Identifier (TAI) or a Presence Reporting Area (PRA).

3. The method of claim 1, wherein the application metadata comprises a list of one or more applications associated with the UE device.

4. The method of claim 1, wherein the first location report is configured to cause the AF to re-provision at least one application to a server proximate to the UE device.

5. The method of claim 1, further comprising:

calculating, at the A-UPF entity, a location of the UE device based on a measured latency between the I-UPF entity and the A-UPF entity, if the sharing of location information or application information is restricted;

generating a second location report, wherein the second location report comprises second location metadata comprising the location of the UE device; and

transmitting the second location report to a Session Management Function (SMF) entity, wherein the second location report is configured to cause the SMF entity to transmit the second location report to the AF entity via a Network Exposure Function (NEF) entity.

6. The method of claim 5, wherein the sharing of location information or application information is restricted by network policy.

7. The method of claim 5, wherein the sharing of location information or application information is restricted by the AF entity.

8. An intermediate-User Plane Function (I-UPF) entity comprising:

one or more network interfaces configured to communicate with a communication network;

one or more processors coupled to the network interfaces and adapted to execute one or more processes; and

a memory coupled to the one or more processors, wherein the memory is configured to store instructions executable by the one or more processors, and wherein the instructions are configured to execute operations comprising;

receiving User Equipment (UE) uplink data from a Radio Access Network (RAN), wherein the UE uplink data originated from a User Equipment (UE) device;

determining if sharing of location information or application information associated with the UE is restricted; and

encapsulating first location metadata or application metadata in an SRv6 packet if the sharing of location information or application information is not restricted; and

transmitting the SRv6 packet to a Data Network (DN), wherein the SRv6 packet is configured to cause the DN to transmit a first location report to at least one Application Function (AF) entity associated with an application associated with the UE device.

9. The I-UPF entity of claim 8, wherein the first location metadata comprises one or more of:

a Tracking Area Identifier (TAI) or a Presence Reporting Area (PRA) identifier.

10. The I-UPF entity of claim 8, wherein the application metadata comprises a list of one or more applications associated with the UE device.

11. The I-UPF entity of claim 8, wherein the first location report is configured to cause the AF to re-provision at least one application to a server proximate to the UE device.

12. The I-UPF entity of claim 8, further comprising:

an anchor-User Plane Function (A-UPF) entity, wherein the A-UPF is configured to communicate with the I-UPF entity, and wherein the A-UPF entity is configured to perform operations comprising;

calculating a location of the UE device based on a measured latency between the I-UPF entity and the A-UPF entity, if the sharing of location information or application information is restricted;

generating a second location report, wherein the second location report comprises second location metadata comprising the location of the UE device; and

transmitting the second location report to a Session Management Function (SMF) entity, wherein the second location report is configured to cause the SMF entity to transmit the second location report to the AF entity via a Network Exposure Function (NEF) entity.

13. The I-UPF entity claim 12, wherein the sharing of location information or application information is restricted by network policy.

14. The I-UPF entity claim 12, wherein the sharing of location information or application information is restricted by the AF entity.

15. A non-transitory computer-readable storage medium comprising instructions stored therein, which when executed by one or more processors, cause the processors to perform operations comprising:

receiving, at an intermediate-User Plane Function (I-UPF) entity, User Equipment (UE) uplink data from a Radio Access Network (RAN), wherein the UE uplink data originated from a User Equipment (UE) device;

determining, at the I-UPF entity, if sharing of location information or application information associated with the UE is restricted;

encapsulating, by the I-UPF entity, first location metadata or application metadata in an SRv6 packet if the sharing of location information or application information is not restricted; and

transmitting the SRv6 packet to an anchor-User Plane Function (A-UPF) entity for forwarding to a Data Network (DN), wherein the SRv6 packet is configured to cause the DN to transmit a first location report to at least one Application Function (AF) entity associated with an application associated with the UE device.

16. The non-transitory computer-readable storage medium of claim 15, wherein the first location metadata comprises one or more of:

a Tracking Area Identifier (TAI) or a Presence Reporting Area (PRA).

17. The non-transitory computer-readable storage medium of claim 15, wherein the application metadata comprises a list of one or more applications associated with the UE device.

18. The non-transitory computer-readable storage medium of claim 15, wherein the first location report is configured to cause the AF to re-provision at least one application to a server proximate to the UE device.

19. The non-transitory computer-readable storage medium of claim 15, wherein the instructions are further configured to perform operations comprising:

calculating, at the A-UPF entity, a location of the UE device based on a measured latency between the I-UPF entity and the A-UPF entity, if the sharing of location information or application information is restricted;

generating a second location report, wherein the second location report comprises second location metadata comprising the location of the UE device; and

transmitting the second location report to a Session Management Function (SMF) entity, wherein the second location report is configured to cause the SMF entity to transmit the second location report to the AF entity via a Network Exposure Function (NEF) entity.

20. The non-transitory computer-readable storage medium of claim 19, wherein the sharing of location information or application information is restricted by network policy.