INTER/INTRA RADIO ACCESS TECHNOLOGY MOBILITY AND USER-PLANE SPLIT MEASUREMENT CONFIGURATION

• US 20160057687A1
• Filed: 01/16/2015
• Published: 02/25/2016
• Est. Priority Date: 08/19/2014
• Status: Abandoned Application

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: HORN, Gavin Bernard, TENNY, Nathan Edward
• Application Number:
  US14/599,088
• Publication Number:
  US 20160057687A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: H04W 36/0069 in case of dual connectivity, e.g. decoupled uplink/downlink
• CPC Class Codes: H04W 36/08 Reselecting an access point
• CPC Class Codes: H04W 36/165 for reducing network power consumption H04W36/18 - H04W36/22 take precedence
• CPC Class Codes: H04W 36/28 involving a plurality of connections, e.g. multi-call or multi-bearer connections
• CPC Class Codes: H04W 36/30 by measured or perceived connection quality data
• CPC Class Codes: H04W 36/305 Handover due to radio link failure control signalling for hand-off failure H04W36/0079
• CPC Class Codes: H04W 36/385 of the core network
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

Certain aspects of the present disclosure relate to methods and apparatus for wireless communication, and more particularly, to methods and apparatus for inter/intra RAT mobility and U-plane split measurement configuration based on context and service awareness. For example, in certain aspects, a mobile device may manage at least one data flow between a core network and the mobile device by identifying at least one constraint on selection of an aggregation point for the data flow. The constraint may be based on at least one of a context for the mobile device or a service associated with the data flow. The mobile device may send a report to a first node based on the at least one identified constraint and receive a configuration request to establish a connection with a second node based on the report.

Claims

1. A method of wireless communication by a mobile device for managing at least one data flow between a core network and the mobile device comprising:

identifying at least one constraint on selection of an aggregation point for the data flow wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

sending a report to a first node based on the at least one identified constraint; and

receiving a configuration request to establish a connection with a second node based on the report.

2. The method of claim 1, wherein the report comprises an indication of the identified constraint.

3. The method of claim 1, wherein the report indicates at least one suggested aggregation point based on the constraint.

4. The method of claim 3 further comprising determining the at least one suggested aggregation point from the at least one constraint based on a policy.

5. The method of claim 4, wherein the policy associates data flows with at least one of a preferred aggregation point or a forbidden aggregation point.

6. The method of claim 1, wherein receiving the configuration request to establish the connection with the second node based on the report comprises at least one of:

receiving a request to handover to the second node;

or

receiving a request to configure multi-connectivity with the first and second node.

7. The method of claim 1, wherein the constraints are based on capabilities of the mobile device.

8. The method of claim 1, wherein the aggregation point comprises at least one of an eNodeB, a Mobility Management Entity (MME), or a gateway (GW).

9. A method of wireless communication by a first node for managing at least one data flow between a core network and a mobile device comprising:

selecting an aggregation point or type of aggregation for the data flow based on at least one constraint, wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

identifying at least one second node for delivering at least a portion of the data flow to the mobile device based on the selection;

evaluating a capability of the second node to deliver the at least one data flow to the mobile device; and

directing the at least one data flow to be routed to the second node.

10. The method of claim 9, wherein the second node is configured to manage the data flow according to a plurality of layers in a protocol stack that are below a layer that is determined based on a selection of a packet routing option at the aggregation point.

11. The method of claim 10, wherein the packet routing option comprises at least one of a data flow split or a packet split.

12. The method of claim 10, further comprising selecting the packet routing option.

13. The method of claim 9, wherein the constraint is based on at least one of a subscription and policy of the mobile device, one or more capabilities of the mobile device, a context of the mobile device, or which services have active traffic being exchanged between the core network and the mobile device.

14. The method of claim 9, wherein evaluating the capability of the second node comprises consideration of at least one of:

whether the first node and the second node operate according to distinct radio access technologies (RATs);

a quality of service contract;

availability of radio resources at the second node;

an indication by the mobile device of information related to radio conditions;

one or more indicated capabilities of the mobile device;

or

an estimate of a geographic position of the mobile device.

15. The method of claim 9, further comprising configuring the mobile device to report, to the first node, information related to delivery of at least a portion of the data flow from the second node.

16. The method of claim 15, wherein the configuration is for the mobile device to report feedback to support the selection of candidate aggregation points.

17. The method of claim 16, wherein the feedback comprises at least one of radio frequency conditions or throughput information for the second node.

18. The method of claim 15, wherein the configuration is for the mobile device to report feedback to support the selection of the second node.

19. The method of claim 18, wherein the feedback comprises radio frequency conditions for a plurality of candidate second nodes.

20. The method of claim 9, wherein evaluating the capability of the second node to deliver the at least one data flow to the mobile device comprises sending an admission request to the second node.

21. The method of claim 9, wherein the selecting, identifying, and evaluating are performed in response to a request to establish one or more new data flows.

22. The method of claim 9, wherein the selecting, identifying, and evaluating are performed in response to a request to modify one or more existing data flows.

23. The method of claim 9, wherein the selecting, identifying, and evaluating are performed in response to evaluation of one or more existing data flows for relocation to a new serving node.

24. A mobile device for managing at least one data flow between a core network and the mobile device comprising:

means for identifying at least one constraint on selection of an aggregation point for the data flow wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

means for sending a report to a first node based on the at least one identified constraint; and

means for receiving a configuration request to establish a connection with a second node based on the report.

25. The mobile device of claim 24, wherein the report comprises an indication of the identified constraint.

26. The mobile device of claim 24, wherein the report indicates at least one suggested aggregation point based on the constraint.

27. The mobile device of claim 26 further comprising means for determining the at least one suggested aggregation point from the at least one constraint based on a policy.

28. The mobile device of claim 27, wherein the policy associates data flows with at least one of a preferred aggregation point or a forbidden aggregation point.

29. The mobile device of claim 24, wherein receiving the configuration request to establish the connection with the second node based on the report comprises at least one of:

means for receiving a request to handover to the second node;

or

means for receiving a request to configure multi-connectivity with the first and second node.

30. The mobile device of claim 24, wherein the constraints are based on capabilities of the mobile device.

31. The mobile device of claim 24, wherein the aggregation point comprises at least one of an eNodeB, a Mobility Management Entity (MME), or a gateway (GW).

32. A first node for managing at least one data flow between a core network and a mobile device comprising:

means for selecting an aggregation point or type of aggregation for the data flow based on at least one constraint, wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

means for identifying at least one second node for delivering at least a portion of the data flow to the mobile device based on the selection;

means for evaluating a capability of the second node to deliver the at least one data flow to the mobile device; and

means for directing the at least one data flow to be routed to the second node.

33. The first node of claim 32, wherein the second node is configured to manage the data flow according to a plurality of layers in a protocol stack that are below a layer that is determined based on a selection of a packet routing option at the aggregation point.

34. The first node of claim 33, wherein the packet routing option comprises at least one of a data flow split or a packet split.

35. The first node of claim 33, further comprising means for selecting the packet routing option.

36. The first node of claim 32, wherein the constraint is based on at least one of a subscription and policy of the mobile device, one or more capabilities of the mobile device, a context of the mobile device, or which services have active traffic being exchanged between the core network and the mobile device.

37. The first node of claim 32, wherein means for evaluating the capability of the second node comprises consideration of at least one of:

whether the first node and the second node operate according to distinct radio access technologies (RATs);

a quality of service contract;

availability of radio resources at the second node;

an indication by the mobile device of information related to radio conditions;

one or more indicated capabilities of the mobile device;

or

an estimate of a geographic position of the mobile device.

38. The first node of claim 32, further comprising means for configuring the mobile device to report, to the first node, information related to delivery of at least a portion of the data flow from the second node.

39. The first node of claim 38, wherein the configuration is for the mobile device to report feedback to support the selection of candidate aggregation points.

40. The first node of claim 39, wherein the feedback comprises at least one of radio frequency conditions or throughput information for the second node.

41. The first node of claim 38, wherein the configuration is for the mobile device to report feedback to support the selection of the second node.

42. The first node of claim 41, wherein the feedback comprises radio frequency conditions for a plurality of candidate second nodes.

43. The first node of claim 32, wherein means for evaluating the capability of the second node to deliver the at least one data flow to the mobile device comprises means for sending an admission request to the second node.

44. The first node of claim 32, wherein the means for selecting, means for identifying, and means for evaluating are performed in response to a request to establish one or more new data flows.

45. The first node of claim 32, wherein the means for selecting, means for identifying, and means for evaluating are performed in response to a request to modify one or more existing data flows.

46. The first node of claim 32, wherein the means for selecting, means for identifying, and means for evaluating are performed in response to evaluation of one or more existing data flows for relocation to a new serving node.

47. A computer-readable medium for managing at least one data flow between a core network and a mobile device having instructions stored thereon for causing the mobile device to:

identify at least one constraint on selection of an aggregation point for the data flow wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

send a report to a first node based on the at least one identified constraint; and

receive a configuration request to establish a connection with a second node based on the report.

48. A computer-readable medium for managing at least one data flow between a core network and a mobile device having instructions stored thereon for causing a first node to:

select an aggregation point or type of aggregation for the data flow based on at least one constraint, wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

identify at least one second node for delivering at least a portion of the data flow to the mobile device based on the selection;

evaluate a capability of the second node to deliver the at least one data flow to the mobile device; and

direct the at least one data flow to be routed to the second node.

49. A mobile device for managing at least one data flow between a core network and the mobile device comprising:

a processing system configured to identify at least one constraint on selection of an aggregation point for the data flow wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow;

a transmitter configured to send a report to a first node based on the at least one identified constraint; and

a receiver configured to receive a configuration request to establish a connection with a second node based on the report.

50. A first node for managing at least one data flow between a core network and a mobile device comprising:

a receiver to receive an indication of a capability of a second node; and

a processing system configured to select an aggregation point or type of aggregation for the data flow based on at least one constraint, wherein the constraint is based on at least one of a context for the mobile device or a service associated with the data flow, identify the second node for delivering at least a portion of the data flow to the mobile device based on the selection, evaluate a capability of the second node to deliver the at least one data flow to the mobile device, and direct the at least one data flow to be routed to the second node.