阅读说明：本技术 自主无线接入网络通知区域配置 (Autonomous wireless access network notification area configuration ) 是由 柳回春 G·B·霍恩 L·F·B·洛佩斯 于 2017-12-25 设计创作，主要内容包括：描述了用于无线通信的方法、系统和设备。用户设备(UE)可以从与第一小区的连接状态转换为不活动状态,并且识别被配置用于不活动状态的包括第一小区的通知区域。当在不活动状态中时并且独立于第一小区,UE可以重选到第二小区,并且识别用于报告移动性历史信息的触发。移动性历史信息可以包括UE先前已经附着到的先前的小区集合以及针对小区集合中的每个小区的对应的通知区域。UE可以基于触发来报告移动性历史信息。(Methods, systems, and devices for wireless communication are described. A User Equipment (UE) may transition from a connected state with a first cell to an inactive state and identify a notification region including the first cell configured for the inactive state. While in the inactive state and independent of the first cell, the UE may reselect to the second cell and identify a trigger for reporting mobility history information. The mobility history information may include a previous set of cells to which the UE has previously attached and a corresponding notification area for each cell in the set of cells. The UE may report mobility history information based on the trigger.)

1. A method for wireless communication, comprising:

transitioning, at a User Equipment (UE), from a connected state with a first cell to an inactive state;

identifying a notification region configured for the inactive state that includes at least the first cell;

reselecting to a second cell while in the inactive state and independently of the first cell;

identifying a trigger for reporting mobility history information while in the inactive state; and

reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

2. The method of claim 1, wherein identifying the trigger for reporting mobility history information comprises: identifying that the second cell is not within the notification area.

3. The method of claim 1, wherein identifying the trigger for reporting mobility history information comprises:

identifying that the neighbor list for the second cell does not include the first cell upon the reselection to the second cell.

4. The method of claim 1, wherein identifying the trigger for reporting mobility history information comprises:

a connection establishment procedure or a connection restoration procedure is performed.

5. The method of claim 1, wherein identifying the trigger for reporting mobility history information comprises:

receiving a request for the mobility history information.

6. The method of claim 1, wherein identifying the trigger for reporting mobility history information is based at least in part on expiration of a timer associated with periodic reporting of the mobility history information.

7. The method of claim 1, further comprising:

reporting the mobility history information includes: reporting the mobility history information to the second cell as part of a connection establishment procedure, a connection recovery procedure, or a notification area update procedure.

8. The method of claim 1, wherein the plurality of cells comprises a predetermined number of cells.

9. The method of claim 1, wherein in the inactive state, the UE maintains an access stratum context associated with a session connection and is configured for autonomous cell reselection.

10. A method for wireless communication in a wireless communication network including a first cell and a second cell, comprising:

receiving, by a base station associated with the second cell, mobility history information from a User Equipment (UE) via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells to which the UE has reselected in an inactive state;

identifying, based at least in part on the mobility history information, that the first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and

determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

11. The method of claim 10, wherein the second cell is not associated with the notification area when receiving the mobility history information for the UE, and wherein the determining comprises: determining to associate the second cell with the notification region for the UE, the method further comprising: sending a setup request for a logical connection between the first cell and the second cell.

12. The method of claim 11, further comprising:

retrieving a context for the UE from the first cell;

performing a connection handover procedure to handover a session connection for the UE from the first cell to the second cell; and

perform notification area registration to associate the second cell with the notification area for the UE.

13. The method of claim 12, further comprising:

receiving downlink data traffic for the UE from a core network; and

sending a paging request to the first cell via the logical connection for paging the UE via the first cell.

14. The method of claim 11, further comprising:

receiving a setup response indicating a failure to establish the logical connection between the first cell and the second cell; and

determining to refrain from associating the second cell with the notification area for the UE.

15. The method of claim 10, wherein the second cell is associated with the notification area when mobility history information for the UE is received, and wherein the determining comprises: disassociating the second cell from the notification area for the UE based at least in part on the mobility history information.

16. The method of claim 15, further comprising:

perform notification area registration to disassociate the second cell from the notification area for the UE.

17. The method of claim 10, wherein the second cell is associated with a second, different notification area when receiving the mobility history information for the UE, the method further comprising: determining to merge the second notification area with the notification area.

18. The method of claim 10, wherein the second cell is associated with a second, different notification area when receiving the mobility history information for the UE, the method further comprising: determining to disassociate the second cell from the second notification area and to associate the cell with the notification area.

19. An apparatus for wireless communication, comprising:

means for transitioning, at a User Equipment (UE), from a connected state with a first cell to an inactive state;

means for identifying a notification region configured for the inactive state that includes at least the first cell;

means for reselecting to a second cell while in the inactive state and independently of the first cell;

means for identifying a trigger for reporting mobility history information while in the inactive state; and

means for reporting the mobility history information based at least in part on the trigger, the mobility history information comprising a plurality of cells to which the UE has previously attached and a corresponding notification area for each cell of the plurality of cells.

20. An apparatus for wireless communication, comprising:

means for receiving, by a base station associated with a second cell, mobility history information from a User Equipment (UE) via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells to which the UE has reselected in an inactive state;

means for identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and

means for determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

21. An apparatus for wireless communication, comprising:

a processor;

a memory in electronic communication with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

transitioning, at a User Equipment (UE), from a connected state with a first cell to an inactive state;

identifying a notification region configured for the inactive state that includes at least the first cell;

reselecting to a second cell while in the inactive state and independently of the first cell;

identifying a trigger for reporting mobility history information while in the inactive state; and

reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

22. The apparatus of claim 21, wherein the instructions to identify the trigger to report mobility history information are executable by the processor to cause the apparatus to:

identifying that the second cell is not within the notification area.

23. The apparatus of claim 21, wherein the instructions to identify the trigger to report mobility history information are executable by the processor to cause the apparatus to:

identifying that the neighbor list for the second cell does not include the first cell upon the reselection to the second cell.

24. The apparatus of claim 21, wherein the instructions to identify the trigger to report mobility history information are executable by the processor to cause the apparatus to:

a connection establishment procedure or a connection restoration procedure is performed.

25. The apparatus of claim 21, wherein the instructions to identify the trigger to report mobility history information are executable by the processor to cause the apparatus to:

receiving a request for the mobility history information.

26. The apparatus of claim 21, wherein the instructions for identifying the trigger for reporting mobility history information are based at least in part on expiration of a timer associated with periodic reporting of the mobility history information.

27. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

reporting the mobility history information includes: reporting the mobility history information to the second cell as part of a connection establishment procedure, a connection recovery procedure, or a notification area update procedure.

28. The apparatus of claim 21, wherein the plurality of cells comprises a predetermined number of cells.

29. The apparatus of claim 21, wherein in the inactive state, the UE maintains an access stratum context associated with a session connection and is configured for autonomous cell reselection.

30. An apparatus for wireless communication, comprising:

a processor;

a memory in electronic communication with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

receiving, by a base station associated with a second cell from a User Equipment (UE) via the second cell, mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells, the UE having reselected to the second cell in an inactive state;

identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and

determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

31. The apparatus of claim 30, wherein the second cell is not associated with the notification area when the mobility history information for the UE is received, and wherein the instructions to determine whether to associate or disassociate with the second cell are executable by the processor to cause the apparatus to:

determining to associate the second cell with the notification region for the UE; and

sending a setup request for a logical connection between the first cell and the second cell.

32. The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

retrieving a context for the UE from the first cell;

performing a connection handover procedure to handover a session connection for the UE from the first cell to the second cell; and

perform notification area registration to associate the second cell with the notification area for the UE.

33. The apparatus of claim 32, wherein the instructions are further executable by the processor to cause the apparatus to:

receiving downlink data traffic for the UE from a core network; and

sending a paging request to the first cell via the logical connection for paging the UE via the first cell.

34. The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

receiving a setup response indicating a failure to establish the logical connection between the first cell and the second cell; and

determining to refrain from associating the second cell with the notification area for the UE.

35. The apparatus of claim 30, wherein the second cell is associated with the notification area when the mobility history information for the UE is received, and wherein the instructions to determine whether to associate or disassociate with the second cell are executable by the processor to cause the apparatus to:

disassociating the second cell from the notification area for the UE based at least in part on the mobility history information.

36. The apparatus of claim 35, wherein the instructions are further executable by the processor to cause the apparatus to:

perform notification area registration to disassociate the second cell from the notification area for the UE.

37. The apparatus of claim 30, wherein the second cell is associated with a second, different notification area when the mobility history information for the UE is received, wherein the instructions are further executable by the processor to cause the apparatus to:

determining to merge the second notification area with the notification area.

38. The apparatus of claim 30, wherein the second cell is associated with a second, different notification area when the mobility history information for the UE is received, wherein the instructions are further executable by the processor to cause the apparatus to:

determining to disassociate the second cell from the second notification area and to associate the cell with the notification area.

39. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to:

transitioning, at a User Equipment (UE), from a connected state with a first cell to an inactive state;

identifying a notification region configured for the inactive state that includes at least the first cell;

reselecting to a second cell while in the inactive state and independently of the first cell;

identifying a trigger for reporting mobility history information while in the inactive state; and

reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

40. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to:

receiving, by a base station associated with a second cell from a User Equipment (UE) via the second cell, mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells, the UE having reselected to the second cell in an inactive state;

identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and

determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

Technical Field

The following generally relates to wireless communications and, more particularly, to autonomous Radio Access Network (RAN) notification area configuration.

Background

Examples of such multiple-access systems include fourth generation (4G) systems, such as long term evolution (L TE) systems, advanced L TE (L TE-A) systems, or L TE-A specialty systems, and fifth generation (5G) systems, which may be referred to as New Radio (NR) systems, which may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or discrete Fourier transform spread spectrum OFDM (DFT-S-OFDM).

In some wireless communication systems, the UE may be highly mobile within the tracking area. In some cases, the Radio Access Network (RAN) may inform the core network each time the UE reselects to a different cell in the tracking area for the core network to page the UE. If the UE frequently reselects a cell, many notifications to the core network may adversely affect throughput in the RAN.

Disclosure of Invention

The base station may configure a Radio Access Network (RAN) notification area (RNA) for a User Equipment (UE) when the UE enters an inactive state for Radio Resource Control (RRC) signaling. The RNA may be UE-specific and include a list of cells associated with the RNA. In some cases, cells in the RNA may be connected by logical connections that the cells may use to transmit access stratum or non-access stratum signaling for the UE. In the inactive state, the UE may move within the RNA and attach to a cell in the RNA without notifying the RAN. The UE may maintain a connection history for cells to which it has previously attached and RNAs associated with the cells. In some cases, the RAN may manage RNA configuration for the UE based on the connection history and mobility of the UE. For example, if a UE attaches to a cell that is not in RNA, the UE may send its mobility information and connection history in an autonomous RNA configuration (autonomous RAC) report during RRC connection establishment. The RAN may determine whether a cell should join the RNA of the UE based on mobility information and connection history of the UE. In some other examples, an autonomous RAC report may be sent by a UE to a cell that is already in the UE-specific RNA, and a base station associated with the cell may determine whether the cell should remain in the RNA. Thus, larger RNAs may be classified if autonomous RAC reports indicate that the UE may attach to cells of larger RNAs infrequently. In some cases, the RAN may connect or disconnect logical connections between cells in the RNA based on the cells joining or leaving the RNA. Based on autonomous RAC reports, the RAN may determine that the UE often selects cells of neighboring RNAs and change the UE RNA list to include cells of neighboring RNAs, thereby reducing the number of RRC connection registrations for RAN-based notification area updates (RNAUs).

A method of wireless communication is described. The method may include: transitioning, at the UE, from a connected state with the first cell to an inactive state; identifying a notification region configured for the inactive state that includes at least the first cell; reselecting to a second cell while in the inactive state and independently of the first cell; identifying a trigger for reporting mobility history information while in the inactive state; and reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

An apparatus for wireless communication is described. The apparatus may include: means for transitioning, at a UE, from a connected state with a first cell to an inactive state; means for identifying a notification region configured for the inactive state that includes at least the first cell; means for reselecting to a second cell while in the inactive state and independently of the first cell; means for identifying a trigger for reporting mobility history information while in the inactive state; and means for reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be operable to cause the processor to: transitioning, at the UE, from a connected state with the first cell to an inactive state; identifying a notification region configured for the inactive state that includes at least the first cell; reselecting to a second cell while in the inactive state and independently of the first cell; identifying a trigger for reporting mobility history information while in the inactive state; and reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: transitioning, at the UE, from a connected state with the first cell to an inactive state; identifying a notification region configured for the inactive state that includes at least the first cell; reselecting to a second cell independently of the first cell while in the inactive state; identifying a trigger for reporting mobility history information while in the inactive state; and reporting the mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, identifying the trigger for reporting mobility history information comprises: identifying that the second cell may not be within the notification area.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, identifying the trigger for reporting mobility history information comprises: identifying that the neighbor list for the second cell does not include the first cell upon the reselection to the second cell.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, identifying a trigger for reporting the mobility history information comprises: a connection establishment procedure or a connection restoration procedure is performed.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, identifying a trigger for reporting mobility history information comprises: receiving a request for the mobility history information.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, identifying the trigger for reporting mobility history information is based at least in part on expiration of a timer associated with periodic reporting of the mobility history information.

Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: reporting the mobility history information includes: reporting the mobility history information to the second cell as part of a connection establishment procedure, a connection recovery procedure, or a notification area update procedure.

In some examples of the above method, apparatus, and non-transitory computer-readable medium, the plurality of cells comprises a predetermined number of cells.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, the UE maintains an access stratum context associated with a session connection and may be configured for autonomous cell reselection while in the inactive state.

A method of wireless communication is described. The method may include: receiving, by a base station associated with a second cell, mobility history information from a UE via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells to which the UE has reselected in an inactive state; identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

An apparatus for wireless communication is described. The apparatus may include: means for receiving, by a base station associated with a second cell, mobility history information from a UE via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification region for each of the plurality of cells, the UE having reselected to the second cell in an inactive state; means for identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and means for determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be operable to cause the processor to: receiving, by a base station associated with a second cell, mobility history information from a UE via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells to which the UE has reselected in an inactive state; identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: receiving, by a base station associated with a second cell, mobility history information from a UE via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells to which the UE has reselected in an inactive state; identifying, based at least in part on the mobility history information, that a first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE; and determining whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, the second cell may not be associated with the notification area when receiving mobility history information for the UE, and some examples of the above methods, apparatus, and non-transitory computer-readable media may further include processes, features, means, or instructions for: determining to associate the second cell with the notification region for the UE, the method further comprising: sending a setup request for a logical connection between the first cell and the second cell.

Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: retrieving a context for the UE from the first cell. Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: performing a connection handover procedure to handover a session connection for the UE from the first cell to the second cell. Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: perform notification area registration to associate the second cell with the notification area for the UE.

Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: receiving downlink data traffic for the UE from a core network. Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: sending a paging request to the first cell via the logical connection for paging the UE via the first cell.

Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: receiving a setup response indicating a failure to establish the logical connection between the first cell and the second cell. Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: determining to refrain from associating the second cell with the notification area for the UE.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, the second cell may be associated with the notification area when receiving mobility history information for the UE, and wherein the determining comprises: disassociating the second cell from the notification area for the UE based at least in part on the mobility history information.

Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, or instructions for: perform notification area registration to disassociate the second cell from the notification area for the UE.

In some examples of the above methods, apparatus, and non-transitory computer-readable media, the second cell may be associated with a second, different notification area when receiving the mobility history information for the UE, and some examples of the above methods, apparatus, and non-transitory computer-readable media may further include processes, features, means, or instructions for: determining to merge the second notification area with the notification area.

Drawings

Fig. 1 illustrates an example of a system for wireless communication that supports autonomous Radio Access Network (RAN) notification area configuration, in accordance with aspects of the present disclosure.

Fig. 2 illustrates an example of a wireless communication system that supports autonomous RAN notification area configuration in accordance with aspects of the present disclosure.

Fig. 3 illustrates an example of a process flow to support autonomous RAN notification area configuration in accordance with aspects of the present disclosure.

Fig. 4 illustrates an example of a process flow to support autonomous RAN notification area configuration in accordance with aspects of the present disclosure.

Fig. 5-7 show block diagrams of devices supporting autonomous RAN notification area configuration, according to aspects of the present disclosure.

Fig. 8 illustrates a block diagram of a system including a UE supporting autonomous RAN notification area configuration, in accordance with aspects of the present disclosure.

Fig. 9-11 show block diagrams of devices supporting autonomous RAN notification area configuration, according to aspects of the present disclosure.

Fig. 12 illustrates a block diagram of a system including a base station supporting autonomous RAN notification area configuration, in accordance with aspects of the present disclosure.

Fig. 13-14 illustrate methods for autonomous RAN notification area configuration, according to aspects of the present disclosure.

Detailed Description

The base station may configure a Radio Access Network (RAN) notification area (RNA) for the User Equipment (UE) before or while the UE enters an inactive state for Radio Resource Control (RRC) signaling. The RNA may be UE-specific and include a list of cells associated with the RNA. In some cases, cells in the RNA may be connected by a logical connection (e.g., an Xn or X2 connection) that the cells may use to communicate access stratum or non-access stratum signaling for the UE. In the inactive state, the UE may move within the RNA and attach to a cell in the RNA without notifying the RAN. The UE may maintain a connection history for cells to which it has previously attached and RNAs associated with the cells. When the UE is in the inactive state, the core network may consider the UE to be in the connected state, and the UE may switch between the RRC inactive state and the RRC connected state without notifying the core network. In some cases, the terms "cell" and "base station" may be used interchangeably, where a cell corresponds to a cell of a base station and transmitting to or receiving from a base station implies transmitting or receiving on the cell of the base station. The RAN may provide mobile connectivity to UEs over Radio Access Technologies (RATs) via multiple access points, such as base stations, and may interface with a core network to enable connectivity to an IP-based network or a circuit-switched network.

In some cases, the RAN may manage RNA configuration for the UE based on the connection history and mobility of the UE. In a first example, if a UE attaches to a cell that is not in an RNA (e.g., is associated with another RNA), the UE may send its mobility information and connection history in an autonomous RNA configuration (autonomous RAC) report during RRC connection establishment. The RAN may determine whether a cell should join the RNA of the UE based on mobility information and connection history of the UE. For example, if autonomous RAC reports indicate that the UE frequently attaches to the cell from other cells of the RNA, the RAN may determine that the cell joins the RNA. The cell may then establish a logical connection (e.g., an Xn or X2 connection) with other cells in the RNA. In some cases, the RNA of the cell and the RNA of the UE may be merged or combined. In some other examples, an autonomous RAC report may be sent by a UE to a cell in the UE-specific RNA, and a base station associated with the cell may determine whether the cell should remain in the RNA. Thus, larger RNAs may be classified if autonomous RAC reports indicate that the UE may attach to cells of larger RNAs infrequently. In some cases, cells in the RNA may connect or disconnect logical connections based on the cells joining or leaving the RNA. Based on autonomous RAC reports, the RAN may determine that the UE often selects cells of neighboring RNAs and change the UE RNA list to include cells of neighboring RNAs, thereby reducing the number of RRC connection registrations for RAN-based notification area updates (RNAUs).

Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts related to autonomous RAN notification area configuration.

Fig. 1 illustrates an example of a wireless communication system 100 in accordance with various aspects of the disclosure the wireless communication system 100 includes base stations 105, UEs 115, and a core network 130 in some examples, the wireless communication system 100 may be a long term evolution (L TE) network, a modified L TE (L TE-a) network, a L TE-a professional network, or a New Radio (NR) network in some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low cost and low complexity devices.

The base station 105 may communicate wirelessly with the UE115 via one or more base station antennas. The base stations 105 described herein may include or may be referred to by those skilled in the art as base station transceivers, wireless base stations, access points, wireless transceivers, node bs, evolved node bs (enbs), next generation node bs or gigabit node bs (any of which may be referred to as gnbs), home node bs, home evolved node bs, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE115 described herein is capable of communicating with various types of base stations 105 and network devices, including macro enbs, small cell enbs, gnbs, relay base stations, and the like.

Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with various UEs 115 are supported. Each base station 105 may provide communication coverage for a respective geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE115 may utilize one or more carriers. The communication links 125 shown in the wireless communication system 100 may include: uplink transmissions from the UE115 to the base station 105, or downlink transmissions from the base station 105 to the UE 115. Downlink transmissions may also be referred to as forward link transmissions, and uplink transmissions may also be referred to as reverse link transmissions.

The geographic coverage areas 110 for the base stations 105 may be divided into sectors that make up only a portion of the geographic coverage area 110, and each sector may be associated with a cell, for example, each base station 105 may provide communication coverage for a macro cell, a small cell, a hot spot, or other type of cell, or various combinations thereof.

The term "cell" refers to a logical communication entity used for communication with the base station 105 (e.g., on a carrier) and may be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish neighboring cells operating via the same or different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine Type Communication (MTC), narrowband internet of things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access for different types of devices. In some cases, the term "cell" may refer to a portion (e.g., a sector) of geographic coverage area 110 over which a logical entity operates.

The UEs 115 may also be referred to as mobile devices, wireless devices, remote devices, handheld devices, or user equipment, or some other suitable terminology, wherein a "device" may also be referred to as a unit, station, terminal, or client UE115 may also be a personal electronic device, e.g., a cellular telephone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, or a personal computer.

Some UEs 115 (e.g., MTC or IoT devices) may be low cost or low complexity devices and may provide automated communication between machines (e.g., communication via machine-to-machine (M2M)). M2M communication or MTC may refer to data communication techniques that allow devices to communicate with each other or base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application that may utilize the information or present the information to a human interacting with the program or application. Some UEs 115 may be designed to collect information or implement automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing for services.

Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE115 include: a power-saving "deep sleep" mode is entered when not engaged in active communications or operating on a limited bandwidth (e.g., according to narrowband communications). In some cases, the UE115 may be designed to support critical functions (e.g., mission critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.

In some cases, the UE115 may also be able to communicate directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs 115 in the group of UEs 115 communicating with D2D may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some cases, multiple groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1: M) system, where each UE115 transmits to every other UE115 in the group. In some cases, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base stations 105.

The base stations 105 may communicate with the core network 130 and with each other. For example, the base station 105 may interface with the core network 130 over a backhaul link 132 (e.g., via S1 or other interface). The base stations 105 may communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) over a backhaul link 134 (e.g., via the X2 or other interface).

Core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an Evolved Packet Core (EPC) that may include at least one Mobility Management Entity (MME), at least one serving gateway (S-GW), and at least one Packet Data Network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets may be transported through the S-GW, which may itself be connected to the P-GW. The P-GW may provide IP address assignment as well as other functions. The P-GW may be connected to a network operator IP service. The operator IP services may include access to the internet, intranets, IP Multimedia Subsystem (IMS) or Packet Switched (PS) streaming services.

At least some of the network devices (e.g., base stations 105) may include subcomponents such as access network entities, which may be examples of Access Node Controllers (ANCs). Each access network entity may communicate with the UE115 through a plurality of other access network transport entities, which may be referred to as radio heads, intelligent radio heads, or transmission/reception points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., base station 105).

The wireless communication system 100 may operate using one or more frequency bands (typically in the range of 300MHz to 300 GHz). Typically, the region from 300MHz to 3GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by building and environmental features. However, the waves may be sufficient to penetrate the structure for the macro cell to provide service to the UE115 located indoors. UHF-wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100km) than transmission of smaller and longer waves using the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz.

The wireless communication system 100 may also operate in the ultra high frequency (SHF) region using a frequency band from 3GHz to 30GHz, also referred to as a centimeter frequency band. The SHF area includes frequency bands such as the 5GHz industrial, scientific, and medical (ISM) band, which may be opportunistically used by devices that can tolerate interference from other users.

The wireless communication system 100 may also operate in the Extremely High Frequency (EHF) region of the spectrum, e.g., from 30GHz to 300GHz (also referred to as the millimeter-band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE115 and the base station 105, and EHF antennas of respective devices may be even smaller and more closely spaced compared to UHF antennas. In some cases, this may facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the specified use of frequency bands across these frequency regions may differ depending on the country or regulatory agency.

For example, the wireless communication system 100 may employ a licensed-assisted access (L AA), L TE unlicensed (L TE-U) radio access technology, or NR technology, in an unlicensed frequency band (e.g., a 5GHz ISM band).

In some examples, a base station 105 or UE115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, the wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Likewise, a receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

Beamforming (which may also be referred to as spatial filtering, directional transmission or directional reception) is a signal processing technique that: the techniques may be used at a transmitting device or a receiving device (e.g., base station 105 or UE 115) to form or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by: signals transmitted via the antenna elements of the antenna array are combined such that signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signal transmitted via the antenna element may comprise: a transmitting device or a receiving device applies certain amplitude and phase offsets to signals carried via each of the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to an antenna array of a transmitting device or a receiving device, or relative to some other orientation).

In one example, the base station 105 may use multiple antennas or antenna arrays for beamforming operations for directional communication with the UE 115. For example, the base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions, which may include signals transmitted according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used to identify beam directions (e.g., by the base station 105 or a receiving device (e.g., UE 115)) for subsequent transmission and/or reception by the base station 105. The base station 105 may transmit some signals (e.g., data signals associated with a particular receiving device) in a single beam direction (e.g., a direction associated with the receiving device (e.g., UE 115)). In some examples, a beam direction associated with a transmission along a single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, the UE115 may receive one or more of the signals transmitted in different directions by the base station 105, and the UE115 may report an indication to the base station 105 of the signal it receives with the highest or otherwise acceptable signal quality. Although the techniques are described with reference to signals transmitted by the base station 105 in one or more directions, the UE115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmission or reception by the UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

When receiving various signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) from the base station 105, a receiving device (e.g., UE115, which may be an example of a mmW receiving device) may attempt multiple receive beams. For example, the receiving device may attempt multiple receive directions by receiving via different antenna sub-arrays, by processing received signals according to different antenna sub-arrays, by receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array (any of the above operations may be referred to as "listening" according to different receive beams or receive directions). In some examples, a receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving data signals). The single receive beam may be aligned in a beam direction determined based at least in part on listening from different receive beam directions (e.g., a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio, or otherwise acceptable signal quality based at least in part on listening from multiple beam directions).

In some cases, the antennas of a base station 105 or UE115 may be located within one or more antenna arrays that may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with the base station 105 may be located at different geographic locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UEs 115. Likewise, the UE115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

In some cases, the wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack, in the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based, in some cases, a radio link control (R L C) layer may perform packet segmentation and reassembly to communicate on logical channels, a Media Access Control (MAC) layer may perform priority processing and multiplexing of logical channels to transport channels, the MAC layer may also provide retransmission at the MAC layer using hybrid automatic repeat request (HARQ) to improve link efficiency.

In some cases, the UE115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique that increases the likelihood that data will be received correctly on the communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), Forward Error Correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise conditions). In some cases, a wireless device may support same slot HARQ feedback, where the device may provide HARQ feedback in a particular slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in subsequent time slots or according to some other time interval.

Time intervals in L TE or NR may be organized according to radio frames each having a duration of 10 milliseconds (ms), where the frame period may be denoted as Tf 307,200 Ts. the radio frames may be identified by a System Frame Number (SFN) ranging from 0 to 1023 each frame may include 10 subframes numbered from 0 to 9 and each subframe may have a duration of 1 ms.

In some wireless communication systems, a slot may be further divided into a plurality of minislots comprising one or more symbols. In some examples, the symbol of the micro-slot or the micro-slot may be a minimum scheduling unit. Each symbol may vary in duration depending on, for example, the subcarrier spacing or frequency band of operation. Further, some wireless communication systems may implement timeslot aggregation, where multiple timeslots or minislots are aggregated together and used for communication between the UE115 and the base station 105.

The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over the communication link 125. For example, the carrier of the communication link 125 may include a portion of the radio frequency spectrum band that operates according to physical layer channels for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. The carriers may be associated with predefined frequency channels (e.g., E-UTRA absolute radio frequency channel numbers (EARFCNs)) and may be placed according to a channel grid for discovery by UEs 115. The carriers may be downlink or uplink (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted on a carrier may be made up of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as OFDM or DFT-s-OFDM).

The organization of carriers may be different for different radio access technologies (e.g., L TE, L TE-a, L TE-a specialty, NR, etc.).

The physical channels may be multiplexed on the carriers according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using Time Division Multiplexing (TDM) techniques, Frequency Division Multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, the control information sent in the physical control channel may be distributed in a cascaded manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

The carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or "system bandwidth" of the wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80MHz) of the carrier for the particular wireless access technology. In some examples, each served UE115 may be configured to operate over part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using a narrowband protocol type associated with a predefined portion or range within a carrier (e.g., a set of subcarriers or RBs) (e.g., "in-band" deployment of narrowband protocol types).

In a system employing MCM technology, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements the UE115 receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE 115. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers may further increase the data rate for communication with the UE 115.

Devices of the wireless communication system 100 (e.g., base stations 105 or UEs 115) may have a hardware configuration that supports communication over a particular carrier bandwidth or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and/or a UE capable of supporting simultaneous communication via carriers associated with more than one different carrier bandwidth.

The wireless communication system 100 may support communication with UEs 115 over multiple cells or carriers (a feature that may be referred to as carrier aggregation or multi-carrier operation). According to a carrier aggregation configuration, a UE115 may be configured with multiple downlink CCs and one or more uplink CCs. Carrier aggregation may be used with both FDD and TDD component carriers.

In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). An eCC may be characterized by one or more features including: a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be used by UEs 115 that may not be able to monitor the entire carrier bandwidth or otherwise be configured to use a limited carrier bandwidth (e.g., to save power).

In some cases, an eCC may utilize a different symbol duration than other CCs, which may include using a reduced symbol duration compared to the symbol durations of the other CCs. Shorter symbol durations may be associated with increased spacing between adjacent subcarriers. A device utilizing an eCC (e.g., UE115 or base station 105) may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, 80MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). A TTI in an eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable.

In addition, wireless communication systems (such as NR systems) may utilize any combination of licensed, shared, and unlicensed spectrum bands. Flexibility in eCC symbol duration and subcarrier spacing may allow eCC to be used across multiple frequency spectrums. In some examples, NR sharing spectrum may improve spectrum utilization and spectrum efficiency, particularly through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.

The wireless communication system 100 may support techniques for autonomous RNA configuration and updating as described herein. The base station 100 may configure the RNA for the UE115 entering an inactive state for RRC signaling. The RNA may be UE115 specific and include a list of cells associated with the RNA. Cells in the RNA may be connected by logical connections that the cells may use to transmit access stratum or non-access stratum signaling for the UE. In the inactive state, the UE115 may move within the RNA and attach to a cell in the RNA without notifying the RAN. The UE115 may maintain a connection history for cells to which it has previously attached and RNAs associated with the cells.

The RAN may manage the RNA configuration for the UE115 based on the connection history and mobility of the UE 115. In a first example, if the UE115 attaches to a cell that is not in RNA, the UE115 may send its mobility information and connection history in an autonomous RAC report during RRC connection establishment. The RAN may determine whether a cell should join the RNA based on mobility information and connection history of the UE 115. For example, if autonomous RAC reports indicate that UE115 frequently attaches to the cell from other cells in the RNA, the RAN may determine that the cell joins the RNA. This cell can then establish a logical connection with other cells in the RNA. In some other examples, an autonomous RAC report may be sent by the UE115 to a cell that is already in the RNA, and the RAN may determine whether the cell should remain in the RNA. Thus, if autonomous RAC reports indicate that the UE115 may be attached to cells of the RNA infrequently, the RNA may be reduced. Cells in the RNA can establish or break logical connections based on the cells joining or leaving the RNA.

Fig. 2 illustrates an example of a wireless communication system 200 that supports autonomous RAN notification area configuration in accordance with various aspects of the disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a base station 105-a and a base station 105-b (which may be examples of base station 105 described herein) and a UE115-a (which may be examples of UE115 described herein).

The base station 105-a may be connected to the core network 205 via a backhaul link 220. The core network 205 may include an access and mobility management function (AMF)210 and a User Plane Function (UPF) 215. The UE115-a may communicate with the core network 205 via a cell 225 of the RAN240 that includes one or more base stations 105.

In a first example, a UE115-a may attach to a base station 105-a and enter a connected state. For example, the UE115-a may perform a random access procedure and establish an RRC connection to the base station 105-a. With the UE115-a in the connected state, the base station 105-a may establish a context for the UE115-a and establish (e.g., via the UPF215) an Access Stratum (AS) session associated with the UE115-a with the core network 205. The UE context may include a first signaling radio bearer (such as radio resource management, mobility, etc.) for RRC signaling and a second signaling radio bearer (which may be forwarded to the AMF 210) for NAS messages. The UE context may also include one or more data radio bearers for user data of the UE 115-a. That is, the base station 105-a may be an anchor base station 105 for the UE115-a within the RAN 240. UE115-a may also establish an AS context associated with the AS session, which may include radio bearers for communications between RAN240 and UE 115-a.

From the connected state with the base station 105-a, the UE115-a may enter an inactive state. RAN240 may configure RNA235 for UE115-a prior to or concurrently with releasing UE115-a into an inactive state. The RNA235 may be configured based on a variety of factors, such as mobility information or mobility class of the UE115-a, system information, whether the UE115-a is in a new or old RAN region, or any combination thereof. In a first example, RAN240 may configure UE115-a to include RNA235 of cell 225-a of base station 105-a and cell 225-b of base station 105-b. Cell 225-c of base station 105-c, although included in RAN240, may not be included in RNA 235. When the UE115-a is in the inactive state, the UE115-a and the base station 105-a may each maintain an active state UE context. Thus, in the inactive state, the core network 205 may consider the UE115-a to remain in the connected state. For example, the core network 205 may maintain a session connection with the base station 105-a for the UE 115-a. However, the RRC connection between the UE115-a and the base station 105-a may be released.

In the inactive state, RAN240 may manage paging for UE115-a via intra-RAN communications. If RAN based paging fails, the base station 105-a may release the context and session connection and return the page to the core network 205, which the core network 205 may initiate based on the last known tracking or registration area for the UE 115-a. The inactive state may reduce signaling between the base station 105 and the core network 205 because the core network 205 may not be notified each time the UE115 changes state between the inactive state and the connected state. In some cases, a UE115 in an inactive state may follow idle state cell reselection behavior within the RNA235 while still being connected to the anchor base station 105 of the RAN240 in the view of the core network 205.

RAN240 may configure RNA235 for UE 115-a. For example, RNA235 of UE115-a may be a list of cells. Additionally or alternatively, RNA235 may be UE-specific. For example, each cell 225 may have an attribute that indirectly identifies whether the cell 225 belongs to the RNA 235. Each cell may broadcast its associated RNA in system information. In some cases, the UE-specific RNA may be a list of cell-specific RNAs.

UE115-a may move within RNA235 without notifying RAN240 of the change in location. UE115-a may camp on a different cell 225 of RNA235 while moving (e.g., via cell reselection) and not inform RAN 240. For example, the UE115-a may camp on the base station 105-b and read system information transmitted by the base station 105-b. The UE115-a may record the cell ID and corresponding RNA of the base station 105-b.

The RNA235 for the UE115 may be defined by a list of cells 225, a list of registration or tracking areas, or a list of RNAs in which each RNA includes one or more cells. The RNA235 may include cells 225 to which the UE115-a frequently connects, cells 225 to which the UE115-a may be predicted to connect, or cells to which the UE115-a has previously connected. The RNA235 may be UE115-a specific. Cell 225 may be associated with RNA even when not included in UE-specific RNA 235. For example, cell 225-c may be associated with an RNA other than RNA 235.

In some examples, logical connection 230 may be established between two base stations 105 associated with cells in RNA 235. For example, the logical connection 230 shown in FIG. 2 may connect the cell 225-a of the base station 105-a and the cell 225-b of the base station 105-b. Logical connection 230 may be used to transport AS and non-access stratum (NAS) signaling for UE 115-a. The logical connection 230 may be, for example, an Xn or X2 connection that supports a direct logical interface between the cells 225 so that the base stations 105 can communicate directly via the logical connection 230 rather than through the core network 205. The logical connection 230 may be established through a direct physical connection between base stations, or via an indirect physical connection (e.g., a switched or routed IP network connection). In some cases, if cell 225 leaves RNA235, logical connection 230 to cell 225 may be broken. Logical connection 230 may form a mesh network for each cell 225 associated with RNA 235. Logical connection 230 may include a control plane interface and a user plane interface, each of which may be implemented using a transport protocol. The control plane interface may for example employ Stream Control Transmission Protocol (SCTP), while the user plane interface may employ General Packet Radio Service (GPRS) tunneling protocol (GTP) and/or User Datagram Protocol (UDP).

In some examples, paging for inactive UEs 115 may be handled by the RAN240 rather than the core network 205. RAN paging may be initiated when downlink signaling or data arrives at the base station 105-a. The base station 105-a may forward the paging information to each cell 225 of the RNA via a logical connection 230. In some cases, RAN240 may not know where UE115-a is in RNA235 or on which cell 225 of RNA235 UE115-a is attached (e.g., camped), so each cell 225 of RNA235 may broadcast a paging message to page UE 115-a.

RAN-based paging may be performed using cell-specific RNA, UE-specific RNA, or a combination of cell-specific RNA and UE-specific RNA (e.g., UE-specific RNA may be specified by a list of cell-specific RNA or registration areas). RAN240 may dynamically update the list of cells, registration areas, or RNAs included in RNA 235. RAN240 may update UE-specific RNA235 for UE115-a by adding or removing cells, cell-specific RNAs, or registration areas. In some cases, RAN240 may update the cell-specific RNAs by rearranging cell attributes such that different cell-specific RNAs comprise different sets of cells. For example, a first cell-specific RNA and a second cell-specific RNA can each have two associated cells 225. In some cases, the first cell-specific RNA may be updated to include one of the cells 225 of the second cell-specific RNA. Thus, the updated first cell-specific RNA may have three cells 225 and the second cell-specific RNA may have one cell 225. In another example, the first cell-specific RNA and the second cell-specific RNA can be combined, thereby combining the list of cells 225 for the two cell-specific RNAs to produce a larger cell-specific RNA. Alternatively, in some examples, a larger cell-specific RNA can be split into two cell-specific RNAs. The rearrangement of cell attributes may affect other UEs 115 (not shown) in RAN240 by updating the cell-specific RNA.

In some cases, UE115-a may send an autonomous RNA configuration (autonomous RAC) report to the cell 225 of base station 105 to which UE115-a is attached. The autonomous RAC report may include anchor base station information, a list of previously visited cells 225, and corresponding RNA information for each previously visited cell 225. The UE115-a may store the connection history information and report the mobility information and the connection history information when queried by the RAN240, when performing an RRC connection establishment procedure, when it reselects to the cell that does not provide the anchor base station 105 in the system information as a neighboring cell, periodically, or when it reselects to the cell 225 of the new RNA. The base station 105-a may configure the UE115-a with an autonomous RAC configuration prior to or concurrently with releasing the UE115-a to the inactive state. The autonomous RAC configuration may indicate content to be included in the autonomous RAC report. For example, the UE115-a may include an ID of the anchor base station 105, IDs of N cells (e.g., base station 105-a and base station 105-b) previously connected, and corresponding RNA IDs of each of the last N cells. As described above, the autonomous RAC configuration may also include when to send autonomous RAC reports.

As one example, if UE115-a selects a cell 225-c that is not in RNA235, RAN240 (e.g., base station 105-c) may decide whether to join cell 225-c to RNA235 based on autonomous RAC reporting. UE115-a may send an autonomous RAC report to base station 105-c on cell 225-c during the RRC connection procedure. In some cases, the base station 105-c may determine that the cell 225-c is likely to be selected frequently based on the autonomous RAC indicating that the RNA235 includes the nearby cell 225 and the mobility information of the UE 115-a. If so, cell 225-c may add RNA 235. In some examples, cell 225-c may be associated with a second RNA, and RNA235 for UE115-a may be merged with the second RNA. If cell 225-c joins RNA235, cell 225-c may establish a logical connection 230 with other cells 225 in RNA235 and cell 225-c may be added to the list of cells in RNA 235. Thus, AS and NAS signaling may be conveyed over logical connection 230 rather than repeatedly performing RRC connection registration. In some other examples, the base station 105-c may determine that the cell 225-c will not be frequently selected for the UE115-a in the inactive state, and that the cell 225-c may not add the RNA 235.

In another example, UE115-a may send an autonomous RAC report when beginning an RRC establishment procedure with cell 225 in RNA 235. For example, the UE115-a may begin an RRC establishment procedure with the cell 225-b of the base station 105-b by sending an RRC recovery request to the base station 105-b via the cell 225-b. If base station 105-b has a logical connection established with base station 105-a in RNA235, base station 105-b may retrieve the UE context via the logical connection. In some other examples, no logical connection may be established and the base station 105-b may retrieve the UE context via signaling from the core network 205. After taking the UE context, the base station 105-b may respond with an RRC recovery message. If the base station 105-b cannot get the UE context, the base station 105-b may reply with an RRC connection setup on cell 225-b. UE115-a may send an autonomous RAC report with either an RRC recovery complete message or an RRC connection setup complete message. Base station 105-b may identify mobility information and connection history information for UE115-a from the autonomous RAC report. Based on the cell IDs in the connection history and their corresponding RNA IDs, base station 105-b may determine whether cell 225-b should remain in RNA235 or should be removed from RNA 235. The logical connection 230 may be established or broken accordingly based on the determination. In some cases, after the UE115-a attaches, the base station 105-b may become the anchor base station 105 for the UE 115-a.

Fig. 3 illustrates an example of a process flow 300 for supporting autonomous RAN notification area configuration in accordance with various aspects of the present disclosure. In some examples, the process flow 300 may implement aspects of the wireless communication system 100.

Process flow 300 may include UE115-b, which may be an example of UE115 as described herein. The process flow 300 may also include a cell 225-a and a cell 225-b, which may be cells of the base station 105 as described herein. Cell 225-a and cell 225-b may be included in RNA 235-a. In some cases, cell 225-a and cell 225-b may have an established logical connection 230-a. The neighboring base station 105-d may be associated with a second RNA 235-b. The process flow 300 may also include an operations, administration, and management unit (OAM) 304. OAM 304 may handle RNA registrations. In some cases, OAM 304 may be part of one of the base stations 105, or the OAM may be a separate node within the RAN. The RAN may provide mobile connectivity for the UE115-b over a RAT via multiple access points (such as the base station 105 or a cell 225 of the base station 105) and may interface with a core network to enable connectivity to an IP or circuit switched based network.

Initially, the UE115-b may attach to the cell 225-a of the anchor base station 105 in an RRC connected state. At 305, cell 225-a may release the RRC connection with UE 115-b. The RAN may determine an autonomous RAC configuration for UE115-b and anchor base station 105 may send the autonomous RAC configuration to UE115-b via cell 225-a during or before RRC connection release. In some examples, the autonomous RAC configuration may indicate content to be included in the autonomous RAC report. For example, the autonomous RAC configuration may indicate to the UE115-b to include the anchor base station 105, the IDs of the previous N cells, and the corresponding RNA IDs for each of the cells. The autonomous RAC configuration may also include when reporting. For example, UE115-b may send an autonomous RAC report based on event triggers such as: when UE115-b moves to a new RNA235, during cell reselection (if the anchor cell is not provided as a neighbor in the system information broadcast of the reselected cell), at the beginning of the RRC establishment procedure, or when requested by the RAN. Additionally or alternatively, UE115-b may periodically send autonomous RAC reports to the cell to which UE115-b is attached.

At 310, the UE115-b may transition to an inactive state. The UE115-b may identify an RNA235 including at least the cell 225-a and the cell 225-b configured for an inactive state. In the inactive state, UE115-b is able to move in RNA235 without notifying the RAN. The UE115-b may follow some idle state cell reselection behavior within the RNA235-a, such as reading system information broadcast, while still being connected to the RAN as seen by the core network. At 315 and 320, UE115-b may read the system information broadcast from cell 225-a and cell 225-b, respectively, and store the cell ID and corresponding RNA ID. In some examples, the UE115-b may move about another RNA, such as the RNA235-b associated with the cell 225 of the neighboring base station 105-d.

At 325, the UE115-b may reselect to the cell of the base station 105-d in an inactive state and independently (e.g., without any messaging or notification) of the cell 225-a or the cell 225-b. The UE115-b may send an RRC recovery request to the base station 105-d. When sending the RRC recovery request, the UE115-b may be in a new RNA235, and the UE115-b may send the RRC recovery request to update its RNA 235. The UE115-b may receive the system information broadcast from the base station 105-d and determine whether it is in the new RNA235 based on the received system information.

At 330, the base station 105-d may determine whether there is a logical connection established with the RNA 235-a. If a connection exists (e.g., an Xn or X2 connection), base station 105-d may request a UE context from anchor base station 105 via a logical connection. If an Xn connection does not exist, the base station 105-d may request a UE context from the core network. After receiving the UE context, the base station 105-d may respond with an RRC recovery message. Otherwise, the base station 105-d may perform an RRC connection establishment procedure. At 335, the base station 105-d may send an RRC recovery message based on the UE context. If the base station 105-d cannot obtain the UE context, the base station 105-d may fall back to RRC connection establishment and send an RRC establishment message.

The UE115-b may transition to an RRC connected state after receiving an RRC recovery message or an RRC connection setup, at 340, the UE115-b may send an RRC recovery complete message or an RRC connection setup complete message to the base station 105-d, the UE115-b may include an autonomous RAC report with the message, the autonomous RAC report may include a cell ID of a cell in a connection history of the UE115-b and a corresponding RNA ID., e.g., the connection history of the UE115-b may include the cell 225-a and the cell 225-b, and the RNA ID. autonomous RAC report of the RNA235-a may also include mobility information for the UE 115-b.

If base station 105-d does not have a logical connection established with base station 105 indicated in the autonomous RAC report, then base station 105-d may request a logical connection establishment with cell 225-b and cell 225-a at 350 and 355, respectively. Cell 225-a and cell 225-b may reply with logical connection setup responses at 360 and 365, respectively.

At 370 and 375, the base station 105-d may exchange RNA information with the cell 225-a and the cell 225-b associated with the RNA235-a and the RNA 235-b. Base station 105-d may exchange RNA information with each cell 225 included in the connection history reported by the autonomous RAC. When UE115-b enters the inactive state, the RNA information may be used to generate another automatic RAC configuration and RNA235 for UE 115-b. In some cases, RNA information may be exchanged via logical connections. If no logical connection is established, RNA information may be exchanged by indirect communication via intermediate node routing.

At 380 and 385, the RAN may perform RAN paging area management. For example, the RAN may determine whether the base station 105-d adds RNA235-a or whether to combine RNA235-a and RNA 235-b. This determination may be made based on the content of the autonomous RAC report. For example, if the base station 105-d determines that the UE115-b may frequently reselect from the cell 225 of the RNA235-a to the base station 105-d, the base station 105-d may join the RNA235-a to reduce the number of RRC registrations that the UE115-b may perform with the base station 105-d. Base station 105-d may establish logical connection 230 with other base stations associated with RNA235-a based on autonomous RAC reporting, and base station 105-d may retrieve UE context and RRC information via logical connection 230 rather than requesting the UE context from the core network. As described, the RAN may decide to associate or disassociate the cell 225 with the RNA235 independent of the core network (e.g., the RNA235 may be managed by the base station 105 and OAM 304 independent of the AMF and/or UPF). In some examples, the determination as to whether to associate or disassociate a cell with the RNA235 may also be made based on autonomous RAC reports from other UEs 115. At 390, the base station 105-d may register the new, extended, or combined RNA235 with the OAM 304.

In some cases, RNA235-a may be UE115-b specific. In some cases, the cell 225 of the base station 105-d may be added to the UE-specific RNA 235-a. Thus, the UE115-b may move in the cell-specific RNA235-a of the cell that includes the base station 105-d without notifying the RAN. This may not affect another UE115 with UE-specific RNA235-b, as only the UE-specific RNA235-a is updated

In another example, RNA235-a and RNA235-b can each be cell-specific RNA. RNA management may include combining cell-specific RNAs 235-a and 235-b. Thus, RNA235-a and RNA235-b can be combined to produce larger RNA235, which includes small regions of RNA235-a and RNA 235-b. Alternatively, a small region in RNA235-b can be moved from RNA235-b to RNA 235-a. In some cases, altering the cell-specific RNA may affect each UE-specific RNA of one or more cells having the altered cell-specific RNA. For example, UE115-b may have a UE-specific RNA that includes RNA235-a, and if RNA235-a is extended by adding a cell or merging with another cell-specific RNA235, the UE-specific RNA is similarly extended. In addition, if RNA235-a and RNA235-b are merged, another UE115 (not shown) that has a UE-specific RNA that previously included only RNA235-b will now also include RNA 235-a.

When the base station 115-d releases the UE115-b to an inactive state at 395, the UE115-b may be configured with a new RNA list. For example, a new RNA list may be configured based on the combined RNA235, the RNA information exchanged at 370 and 375, and the RNA paging area management information exchanged at 380 and 385. The base station 105-d may send an RRC connection release to the UE115-b to release the UE115-b to an inactive state. Base station 105-d may include the updated RNA list in the updated autonomous RAC configuration and send the updated autonomous RAC configuration upon or prior to releasing UE115-b to the inactive state.

As described, the RNA region may be autonomously redesigned using an autonomous RAC reporting procedure based on inactive UEs 115 reporting connection history information including the anchor cell, the previous N cells to which the UE115 is connected, and the RNAID of each of the previously connected N cells. Based on the autonomous RAC procedure, smaller RNAs may be merged to create larger RNAs or to reconfigure a new RNA list for the UE115 based on the mobility history of the UE to reduce RNA update signaling costs. The logical connection may be established automatically based on autonomous RAC reports.

Fig. 4 illustrates an example of a process flow 400 supporting autonomous RAN notification area configuration in accordance with various aspects of the present disclosure. In some examples, process flow 400 may implement aspects of wireless communication system 100.

Process flow 400 may include UE115-c, which may be an example of UE115 as described herein. Process flow 400 may also include base station 105-e (which may be an anchor base station 105 for UE115-c in an inactive state), base station 105-f, and base station 105-g, each of which may be included in RNA 235-c. In some cases, none of the base stations 105 may have a logical connection or Xn connection established. Process flow 400 may also include OAM 404. OAM404 may handle RAN area registration.

Initially, UE115-c may connect to base station 105-e in an RRC connected state. At 405, the base station 105-e may release the RRC connection with the UE 115-c. During or prior to RRC connection release, the base station 105-e may configure autonomous RAC information for the UE115-c at 405 and send the autonomous RAC configuration to the UE 115-c. In some examples, the autonomous RAC configuration may indicate content to be included in the autonomous RAC report. For example, the autonomous RAC configuration may indicate that includes IDs of N cells previously connected by the anchor base station 105 (e.g., of base station 105-e, base station 105-f, and base station 105-g), and a corresponding RNA ID for each of the last N cells. The autonomous RAC configuration may also include when to send autonomous RAC reports. For example, UE115-c may send an autonomous RAC report based on an event trigger, such as when UE115-c moves to a new RAN area. In some other examples, UE115-c may report an autonomous RAC for cell reselection if the anchor cell is not provided as a neighbor in the system information broadcast of the new selected cell. In some cases, UE115-c may send an autonomous RAC report when starting the RRC establishment procedure. In some other examples, UE115-c may send an autonomous RAC report upon request by the RAN. Additionally or alternatively, UE115-c may periodically send autonomous RAC reports to the cell to which UE115-c is attached.

At 410, the UE115-c may transition to an inactive state. UE115-b may identify an RNA configured for an inactive state that includes at least base station 105-e, base station 105-f, and base station 105-g. In the inactive state, the UE115-c is able to move within the RNA235-c without notifying the RAN. The UE115-c may follow some idle state cell reselection behavior within the RNA235-c, such as reading system information broadcast, while still being connected to the RAN as seen by the core network. At 415 and 420, UE115-c may read the system information broadcast from base station 105-e and base station 105-f, respectively, and store the cell ID and corresponding RNA 235.

At 425, the UE115-c may reselect to the cell of the base station 105-g in an inactive state and independently of the base station 105-e or the base station 105-f. The UE115-c may send an RRC recovery request to the base station 105-g. In some cases, UE115-c may initiate an RRC recovery procedure to send mobile-originated data based on received pages, timers for periodic autonomous RAC reports, or in response to a request to send autonomous RAC reports. When sending the RRC recovery request, UE115-c may be in the same RNA, which may be determined based on receiving the system information broadcast.

The base station 105-g may determine whether a logical connection established with the anchor base station 105 (e.g., base station 105-e) exists. If there is an existing logical connection, base station 105-g may request the UE context from anchor base station 105 via the logical connection and perform an RRC recovery procedure. If there is no logical connection, the base station 105-g may request a UE context for the UE115-c from the core network. If the base station 105-g takes the UE context, the base station 105-g may send an RRC resume message at 435. If the base station 105-g cannot get the UE context, the base station 105-g may send an RRC establishment message.

The UE115-c may transmit an RRC recovery complete message or an RRC connection setup complete message to the base station 105-g along with an autonomous RAC report at 440. the autonomous RAC report may include the cell ID of the cell and corresponding RNA ID. in the connection history of the UE 115-c-e.g., the connection history of the UE115-c may include the RNAID of base station 105-e and base station 105-f and RNA 235-c. the autonomous RAC report may also include information related to the mobility of the UE115-c (e.g., mobility in any combination of inactive, connected, or idle states). at 445, the base station 105-g may identify the TN L address of base station 105-e and base station 105-f.

At 450 and 455, base station 105-g may exchange RNA information with base station 105-e and base station 105-f. In some examples, base station 105-g may exchange RNA information with each RNA included in the connection history reported by the autonomous RAC. The RNA information may be used to generate another autonomous RAC configuration and RNA list for UE 115-c. If a logical connection is not established between base stations 105, RNA information may be exchanged through indirect communication via intermediate node routing (e.g., via OAM 404).

At 460 and 465, the RAN may perform RAN paging area management. For example, the RAN may determine to split RNA235-c into two smaller RNAs 235. This determination may be made based on the content of the autonomous RAC report. The base station 105-g may determine that the UE115-c may be attached infrequently and the base station 105-g may split into individual RNAs 235. Thus, the RAN may release the logical connection by removing base station 105-g from the RNA list of UE 115-c. In some other examples, for example, as described with reference to fig. 3, the base station 105-g may stay in the RNA235-c if the base station 105-g determines that the UE115-c may frequently request attachment. At 470, the base station 105-g may register the two RNAs created by splitting RNA235-c with OAM 404.

When the base station 115-g releases the UE115-c to an inactive state at 475, the UE115-c may be configured with a new RNA list. For example, a new RNA list may be configured based on the RNA associated with base station 105-g. In some examples, the new RNA list for UE115-c may not include base station 105-e and base station 105-f. The RNA list may be based on the RNA information exchanged at 460 and 465. The base station 105-g may send an RRC connection release to the UE115-c to release the UE115-c to an inactive state.

As described, the RNA may be autonomously redesigned using an autonomous RAC procedure based on an inactive UE115 reporting connection history information including the anchor cell, the previous N cells to which the UE115 is connected, and the RNA ID of each of the previously connected N cells. In this example, the RNA initially configured for the inactive UE115 may be split into smaller RAN regions. The registration area may be utilized to define the RNA235 regardless of whether a logical connection exists between each of the base stations 105. The RNA235 may be initially defined by a registration area, which may initially not include logical connections between cells 225 or base stations 105 in the registration area. Thus, the RNA235-c of fig. 4 may be a large, initially defined registration region that may be split into smaller RNAs 235 when the RAN determines which cells of the RNA235-c the UE115-c may attach to. The RAN may also merge or partition the RNAs 235 based on whether logical connections between cells of the RNAs 235 can be established.

When downlink data arrives at the anchor base station 105 for paging, RAN paging may be confined within the anchor base station 105 due to a lack of logical connections to other base stations 105 or due to paging being performed only in the RNA 235. In this case, the UE115 may be under another base station 105 than the anchor base station 105, and the RAN paging may fail because no response is received from the UE 115. In some cases, the anchor base station 105 may release the connection with the UE115 and may trigger a core network page.

Fig. 5 illustrates a block diagram 500 of a wireless device 505 that supports autonomous RAN notification area configuration in accordance with aspects of the present disclosure. The wireless device 505 may be an example of aspects of a UE115 as described herein. The wireless device 505 may include a receiver 510, a UE communication manager 515, and a transmitter 520. The wireless device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

The receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to autonomous RAN notification area configuration, etc.). Information may be passed to other components of the device. The receiver 510 may be an example of aspects of the transceiver 835 described with reference to fig. 8. Receiver 510 may utilize a single antenna or a group of antennas.

The UE communications manager 515 may be an example of aspects of the UE communications manager 815 described with reference to fig. 8.

UE communications manager 515 and/or at least some of its various subcomponents may be implemented in hardware, software executed by a processor, firmware or any combination thereof. If implemented in software executed by a processor, the functions of the UE communication manager 515 and/or at least some of its various subcomponents may be performed by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure. UE communications manager 515 and/or at least some of its various subcomponents may be physically located at various locations, including being distributed such that some of the functionality is implemented by one or more physical devices at different physical locations. In some examples, UE communications manager 515 and/or at least some of its various subcomponents may be separate and distinct components in accordance with various aspects of the present disclosure. In other examples, UE communications manager 515 and/or at least some of its various subcomponents, in accordance with various aspects of the present disclosure, may be combined with one or more other hardware components (including, but not limited to, an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

The UE communications manager 515 may: transitioning, at the UE, from a connected state with the first cell to an inactive state; identifying a notification region configured for an inactive state comprising at least a first cell; reselecting to a second cell while in an inactive state and independently of the first cell; identifying a trigger for reporting mobility history information while in an inactive state; and reporting mobility history information based on the trigger, the mobility history information including a set of cells to which the UE has previously attached and a corresponding notification area for each cell in the set of cells.

The transmitter 520 may transmit signals generated by other components of the device. In some examples, the transmitter 520 may be collocated with the receiver 510 in a transceiver module. For example, the transmitter 520 may be an example of aspects of the transceiver 835 described with reference to fig. 8. The transmitter 520 may utilize a single antenna or a group of antennas.

Fig. 6 shows a block diagram 600 of a wireless device 605 supporting autonomous RAN notification area configuration, in accordance with aspects of the present disclosure. The wireless device 605 may be an example of aspects of the wireless device 505 or the UE115 as described with reference to fig. 5. The wireless device 605 may include a receiver 610, a UE communication manager 615, and a transmitter 620. The wireless device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 610 may receive information such as control information associated with packets, user data, or various information channels (e.g., control channels, data channels, and information related to autonomous RAN notification area configuration, etc.). Information may be passed to other components of the device. The receiver 610 may be an example of aspects of the transceiver 835 described with reference to fig. 8. Receiver 610 may utilize a single antenna or a group of antennas.

The UE communication manager 615 may be an example of aspects of the UE communication manager 815 described with reference to fig. 8.

The UE communications manager 615 may also include a UE state transition component 625, an RNA identification component 630, a cell reselection component 635, a reporting trigger identifier 640, and a mobility history reporting component 645.

UE state transition component 625 may transition from a connected state with the first cell to an inactive state at the UE. UE state transition component 625 may also maintain an access stratum context associated with the session connection in an inactive state and configured for autonomous cell reselection. In some cases, in the inactive state, the UE may maintain an access stratum context associated with the session connection and may be configured for autonomous cell reselection.

The RNA identification component 630 can identify a notification region comprising at least a first cell configured for an inactive state.

Cell reselection component 635 may reselect to a second cell while in an inactive state and independent of the first cell.

The reporting trigger identifier 640 may identify a trigger for reporting mobility history information when in an inactive state. In some cases, identifying a trigger for reporting mobility history information includes: identifying that the second cell is not within the notification area. In some cases, identifying a trigger for reporting mobility history information includes: upon reselection to the second cell, it is identified that the neighbor list for the second cell does not include the first cell. In some examples, identifying a trigger for reporting mobility history information includes: a connection establishment procedure or a connection restoration procedure is performed. In some cases, identifying a trigger for reporting mobility history information includes: a request for mobility history information is received. In some cases, identifying a trigger for reporting mobility history information is based at least in part on expiration of a timer associated with periodic reporting of mobility history information.

Mobility history reporting component 645 may report mobility history information based on the trigger, the mobility history information including a set of cells to which the UE has previously attached and a corresponding notification area for each cell in the set of cells, and reporting the mobility history information includes: the mobility history information is reported to the second cell as part of a connection establishment procedure, a connection recovery procedure, or a notification area update procedure. In some cases, the set of cells includes a predetermined number of cells.

The transmitter 620 may transmit signals generated by other components of the device. In some examples, the transmitter 620 may be collocated with the receiver 610 in a transceiver module. For example, the transmitter 620 may be an example of aspects of the transceiver 835 described with reference to fig. 8. The transmitter 620 may utilize a single antenna or a group of antennas.

Fig. 7 illustrates a block diagram 700 of a UE communication manager 715 supporting autonomous RAN notification area configuration, in accordance with aspects of the present disclosure. The UE communication manager 715 may be an example of aspects of the UE communication manager 515, the UE communication manager 615, or the UE communication manager 815 described with reference to fig. 5, 6, and 8. The UE communications manager 715 may include a UE state transition component 720, an RNA identification component 725, a cell reselection component 730, a reporting trigger identifier 735, and a mobility history reporting component 740. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

UE state transition component 720 may transition from a connected state with a first cell to an inactive state at the UE. UE state transition component 720 may also maintain an access stratum context associated with the session connection in an inactive state and configured for autonomous cell reselection. In some cases, in the inactive state, the UE may maintain an access stratum context associated with the session connection and may be configured for autonomous cell reselection.

The RNA identification component 725 may identify a notification region including at least a first cell configured for an inactive state. Cell reselection component 730 may reselect to a second cell while in an inactive state and independently of the first cell.

The reporting trigger identifier 735 may identify a trigger for reporting mobility history information when in an inactive state. In some cases, identifying a trigger for reporting mobility history information includes: identifying that the second cell is not within the notification area. In some cases, identifying a trigger for reporting mobility history information includes: upon reselection to the second cell, it is identified that the neighbor list for the second cell does not include the first cell. In some cases, identifying a trigger for reporting mobility history information includes: a connection establishment procedure or a connection restoration procedure is performed. In some cases, identifying a trigger for reporting mobility history information includes: a request for mobility history information is received. In some cases, identifying a trigger for reporting mobility history information is based at least in part on expiration of a timer associated with periodic reporting of mobility history information.

Mobility history reporting component 740 may report mobility history information based on the trigger, the mobility history information including a set of cells to which the UE has previously attached and a corresponding notification area for each cell in the set of cells, and reporting the mobility history information includes: the mobility history information is reported to the second cell as part of a connection establishment procedure, a connection recovery procedure, or a notification area update procedure. In some cases, the set of cells includes a predetermined number of cells.

Fig. 8 illustrates a diagram of a system 800 including a device 805 that supports autonomous RAN notification area configuration in accordance with aspects of the present disclosure. Device 805 may be an example of or a component that includes: the wireless device 505, the wireless device 605, or the UE115 as described above (e.g., with reference to fig. 5 and 6). Device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, including: UE communications manager 815, processor 820, memory 825, software 830, transceiver 835, antenna 840, and I/O controller 845. These components may be in electronic communication via one or more buses, such as bus 810. The device 805 may communicate wirelessly with one or more base stations 105.

The processor 820 may include intelligent hardware devices (e.g., a general purpose processor, a DSP, a Central Processing Unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 820 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 820. Processor 820 may be configured to execute computer-readable instructions stored in memory to perform various functions (e.g., functions or tasks to support autonomous RAN notification area configuration).

The memory 825 may include Random Access Memory (RAM) and read-only memory (ROM). The memory 825 may store computer-readable, computer-executable software 830 comprising instructions that, when executed, cause the processor to perform various functions described herein. In some cases, memory 825 may contain, among other things, a basic input/output (I/O) system (BIOS) that may control basic hardware or software operations (e.g., interactions with peripheral components or devices).

The software 830 may include code for implementing aspects of the present disclosure, including code for supporting autonomous RAN notification area configuration. The software 830 may be stored in a non-transitory computer-readable medium (e.g., system memory or other memory). In some cases, the software 830 may not be directly executable by a processor, but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

The transceiver 835 may communicate bi-directionally via one or more antennas, wired or wireless links as described above. For example, transceiver 835 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 835 may also include a modem to modulate packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 840. However, in some cases, a device may have more than one antenna 840 capable of sending or receiving multiple wireless transmissions concurrently.

I/O controller 845 may manage input and output signals to and from device 805. The I/O controller 845 can also manage peripheral devices that are not integrated into the device 805. In some cases, I/O controller 845 may represent a physical connection or port to an external peripheral device. In some cases, I/O controller 845 may utilize a control signal such as Such as an operating system or another known operating system. In other cases, I/O controller 845 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I/O controller 845 may be implemented as part of a processor. In some cases, a user may interact with device 805 via I/O controller 845 or via hardware components controlled by I/O controller 845.

Fig. 9 illustrates a block diagram 900 of a wireless device 905 supporting autonomous RAN notification area configuration in accordance with aspects of the present disclosure. The wireless device 905 may be an example of aspects of the base station 105 as described herein. The wireless device 905 may include a receiver 910, a base station communications manager 915, and a transmitter 920. The wireless device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to autonomous RAN notification area configuration, etc.). Information may be passed to other components of the device. The receiver 910 may be an example of aspects of the transceiver 1235 described with reference to fig. 12. Receiver 910 can utilize a single antenna or a group of antennas. The base station communications manager 915 may be an example of aspects of the base station communications manager 1215 described with reference to fig. 12.

The base station communications manager 915 and/or at least some of its various subcomponents may be implemented in hardware, software executed by a processor, firmware or any combination thereof. If implemented in software executed by a processor, the functions of the base station communications manager 915 and/or at least some of its various subcomponents may be performed by a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure. The base station communications manager 915 and/or at least some of its various subcomponents may be physically located at various locations, including being distributed such that some of the functionality is implemented by one or more physical devices at different physical locations. In some examples, base station communications manager 915 and/or at least some of its various subcomponents may be separate and distinct components in accordance with various aspects of the present disclosure. In other examples, base station communications manager 915 and/or at least some of its various subcomponents, in accordance with various aspects of the present disclosure, may be combined with one or more other hardware components (including, but not limited to, an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

The base station communications manager 915 may perform the following operations: receiving, by a base station associated with a second cell from the UE via the second cell, mobility history information comprising a set of cells to which the UE has previously attached and a corresponding notification area for each cell in the set of cells, the UE having reselected to the second cell in an inactive state; identifying, based on the mobility history information, that the first cell is an anchor cell for the UE and a notification area corresponding to the first cell for the UE; and determining whether to associate or disassociate the second cell with the notification area based on the mobility history information.

Transmitter 920 may transmit signals generated by other components of the device. In some examples, the transmitter 920 may be collocated with the receiver 910 in a transceiver module. For example, the transmitter 920 may be an example of aspects of the transceiver 1235 described with reference to fig. 12. Transmitter 920 may utilize a single antenna or a group of antennas.

Fig. 10 shows a block diagram 1000 of a wireless device 1005 supporting autonomous RAN notification area configuration, in accordance with aspects of the present disclosure. The wireless device 1005 may be an example of aspects of the wireless device 905 or the base station 105 as described with reference to fig. 9. The wireless device 1005 may include a receiver 1010, a base station communication manager 1015, and a transmitter 1020. The wireless device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 1010 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to autonomous RAN notification area configuration, etc.). Information may be passed to other components of the device. The receiver 1010 may be an example of aspects of the transceiver 1235 described with reference to fig. 12. Receiver 1010 may utilize a single antenna or a group of antennas.

The base station communications manager 1015 may be an example of aspects of the base station communications manager 1215 described with reference to fig. 12. The base station communications manager 1015 may also include a mobility history component 1025, a RAN area identifier 1030, and an association determination component 1035.

The mobility history component 1025 may receive mobility history information from the UE via the second cell through a base station associated with the second cell, the mobility history information including a set of cells to which the UE has previously attached and a corresponding notification region for each cell in the set of cells to which the UE has reselected in an inactive state.

RAN area identifier 1030 may identify that the first cell is an anchor cell for the UE and a notification area corresponding to the first cell for the UE based on the mobility history information.

An association determining component 1035 may determine whether to associate or disassociate the second cell with the notification area based on the mobility history information. The association determination component 1035 may also: performing notification area registration to associate the second cell with a notification area for the UE; receiving an establishment response indicating a failure to establish a logical connection between the first cell and the second cell; determining to refrain from associating the second cell with a notification area for the UE; and performing notification area registration to disassociate the second cell from the notification area for the UE. In some cases, the second cell may not be associated with the notification area when receiving mobility history information for the UE, and the association determining component 1035 may also send a setup request for a logical connection between the first cell and the second cell. In some cases, the second cell is associated with the notification area when mobility history information for the UE is received, and wherein the determining comprises: disassociating the second cell from the notification area for the UE based on the mobility history information. In some cases, upon receiving mobility history information for the UE, the second cell may be associated with a second, different notification area, and association determining component 1035 may determine to merge the second notification area with the notification area.

The transmitter 1020 may transmit signals generated by other components of the device. In some examples, the transmitter 1020 may be collocated with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be an example of aspects of the transceiver 1235 described with reference to fig. 12. The transmitter 1020 may utilize a single antenna or a group of antennas.

Fig. 11 illustrates a block diagram 1100 of a base station communication manager 1115 that supports autonomous RAN notification area configuration in accordance with aspects of the present disclosure. The base station communications manager 1115 may be an example of aspects of the base station communications manager 1215 described with reference to fig. 9, 10 and 12. The base station communications manager 1115 can include a mobility history component 1120, a RAN area identifier 1125, an association determination component 1130, a context retrieval component 1135, a connection switching component 1140, and a paging component 1145. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

Mobility history component 1120 may receive mobility history information from the UE via the second cell by a base station associated with the second cell, the mobility history information including a set of cells to which the UE has previously attached and a corresponding notification area for each cell in the set of cells to which the UE has reselected in an inactive state.

The RAN area identifier 1125 may identify that the first cell is an anchor cell for the UE and a notification area corresponding to the first cell for the UE based on the mobility history information.

An association determining component 1130 may determine whether to associate or disassociate the second cell with the notification area based on the mobility history information. The association determination component 1130 may also perform the following operations: performing notification area registration to associate the second cell with a notification area for the UE; receiving an establishment response indicating a failure to establish a logical connection between the first cell and the second cell; determining to refrain from associating the second cell with a notification area for the UE; and performing notification area registration to disassociate the second cell from the notification area for the UE. Association determining component 1130 may also send a setup request for a logical connection between the first cell and the second cell. In some cases, the second cell is associated with the notification area when mobility history information for the UE is received, and wherein the determining comprises: determining to disassociate the second cell from the notification area for the UE based on the mobility history information. In some cases, upon receiving mobility history information for the UE, the second cell may be associated with a second, different notification area, and association determining component 1130 may determine to merge the second notification area with the notification area.

Context retrieving component 1135 may retrieve a context for the UE from the first cell. Connection switching component 1140 may perform a connection switching procedure to switch the session connection for the UE from the first cell to the second cell. Paging component 1145 can receive downlink data traffic for the UE from a core network and transmit a paging request to the first cell via the logical connection regarding paging of the UE via the first cell.

Fig. 12 shows a diagram of a system 1200 including a device 1205 that supports autonomous RAN notification area configuration, in accordance with aspects of the present disclosure. The device 1205 may be an example of a base station 105 as described above (e.g., with reference to fig. 1) or include components of a base station 105. Device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, including: a base station communications manager 1215, a processor 1220, memory 1225, software 1230, a transceiver 1235, an antenna 1240, a network communications manager 1245, and an inter-station communications manager 1250. These components may be in electronic communication via one or more buses, such as bus 1210. The device 1205 may communicate wirelessly with one or more UEs 115.

Processor 1220 may include intelligent hardware devices (e.g., general purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combinations thereof). In some cases, processor 1220 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor 1220. Processor 1220 may be configured to execute computer-readable instructions stored in memory to perform various functions (e.g., functions or tasks to support autonomous RAN notification area configuration).

Memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable software 1230 comprising instructions that, when executed, cause the processor to perform various functions described herein. In some cases, memory 1225 may contain, among other things, a BIOS that may control basic hardware or software operations (e.g., interactions with peripheral components or devices).

Software 1230 may include code for implementing aspects of the present disclosure, including code for supporting autonomous RAN notification area configuration. The software 1230 may be stored in a non-transitory computer-readable medium (e.g., system memory or other memory). In some cases, the software 1230 may not be directly executable by a processor, but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

The transceiver 1235 may communicate bi-directionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1235 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1235 may also include a modem to modulate packets and provide the modulated packets to the antennas for transmission, as well as demodulate packets received from the antennas.

In some cases, a wireless device may include a single antenna 1240. However, in some cases, a device may have more than one antenna 1240 that is capable of concurrently sending or receiving multiple wireless transmissions.

The network communications manager 1245 may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1245 may manage the transmission of data communications for client devices (e.g., one or more UEs 115).

The inter-station communication manager 1250 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with the UE115 in cooperation with the other base stations 105 for example, the inter-station communication manager 1250 may coordinate scheduling of transmissions to the UE115 for various interference mitigation techniques such as beamforming or joint transmission in some examples, the inter-station communication manager 1250 may provide an X2 interface within Long term evolution (L TE)/L TE-A wireless communication network technologies to provide communications between base stations 105.

Fig. 13 shows a flow diagram illustrating a method 1300 for autonomous RAN notification area configuration, in accordance with aspects of the present disclosure. The operations of method 1300 may be implemented by UE115 or components thereof as described herein. For example, the operations of method 1300 may be performed by a UE communications manager as described with reference to fig. 5-8. In some examples, the UE115 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE115 may use dedicated hardware to perform aspects of the functions described below.

At 1305, the UE115 may transition from a connected state with the first cell to an inactive state. 1305 may be performed according to the methods described herein. In some examples, aspects of the operation of 1305 may be performed by a state transition component as described with reference to fig. 5-8.

At 1310, the UE115 may identify a notification region including at least a first cell configured for an inactive state. 1310 may be performed according to the methods described herein. In certain examples, aspects of the operations of 1310 may be performed by an RNA recognition component as described with reference to fig. 5-8.

At 1315, the UE115 may reselect to the second cell while in the inactive state and independently of the first cell. 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed by a cell reselection component as described with reference to fig. 5-8.

At 1320, the UE115 may identify a trigger for reporting mobility history information while in the inactive state. 1320 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1320 may be performed by a report trigger identifier as described with reference to fig. 5-8.

At 1325, the UE115 may report mobility history information based at least in part on the trigger, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification area for each of the plurality of cells. 1325 may be performed according to the methods described herein. In certain examples, aspects of the operations of 1325 may be performed by a mobility history reporting component as described with reference to fig. 5-8.

Fig. 14 shows a flow diagram illustrating a method 1400 for autonomous RAN notification area configuration, in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of method 1400 may be performed by a base station communications manager as described with reference to fig. 9-12. In some examples, the base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may use dedicated hardware to perform aspects of the functions described below.

At 1405, the base station 105 associated with the second cell may receive mobility history information from the UE via the second cell, the mobility history information including a plurality of cells to which the UE has previously attached and a corresponding notification region for each of the plurality of cells to which the UE has reselected in an inactive state. 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed by a mobility history component as described with reference to fig. 9-12.

At 1410, the base station 105 may identify, based at least in part on the mobility history information, that the first cell is an anchor cell for the UE and a notification region corresponding to the first cell for the UE. 1410 may be performed according to the methods described herein. In certain examples, aspects of the operations of 1410 may be performed by a RAN area identifier as described with reference to fig. 9-12.

At 1415, the base station 105 may determine whether to associate or disassociate the second cell with the notification area based at least in part on the mobility history information. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operation of 1415 may be performed by an association determination component as described with reference to fig. 9-12.

It should be noted that the above described methods describe possible implementations and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more methods may be combined.

The techniques described herein may be used for various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. The IS-2000 version may be generally referred to as CDMA 20001X, 1X, etc. IS-856(TIA-856) IS commonly referred to as CDMA 20001 xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes wideband CDMA (W-CDMA) and other variants of CDMA. TDMA systems may implement radio technologies such as global system for mobile communications (GSM).

An OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE)802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, flash-OFDM, etc. UTRA and E-UTRA are part of a Universal Mobile Telecommunications System (UMTS) L TE, L TE-A, and L0 TE-A are specialties of UMTS versions that use E-UTRA.UTRA, E-UTRA, UMTS, L TE, L2 TE-A, L3 TE-A specialties, NR, and GSM are described in documents from the organization named "3 rd Generation partnership project 2" (3 GPP). the techniques described in CDMA2000 and UMB. the techniques described herein may be used for the systems and radio technologies mentioned above and for other systems and radio technologies and other than those described herein, and although the techniques described herein may be applied for most purposes to the systems and radio technologies described herein as special for example, TE-3884, TE-NR-85, TE-80, and TE-80, and TE-NR 84, TE-80, and TE-TE.

A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider. A small cell may be associated with a lower power base station 105 than a macro cell, and the small cell may operate in the same or different (e.g., licensed, unlicensed, etc.) frequency band as the macro cell. According to various examples, the small cells may include pico cells, femto cells, and micro cells. For example, a pico cell may cover a small geographic area and may allow unrestricted access by UEs 115 with service subscriptions with the network provider. A femto cell may also cover a small geographic area (e.g., a residence) and may provide restricted access by UEs 115 having an association with the femto cell (e.g., UEs 115 in a Closed Subscriber Group (CSG), UEs 115 for users in the residence, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communication using one or more component carriers.

The wireless communication system 100 or systems described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timings, and transmissions from different base stations 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operations.

The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device (P L D), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features implementing functions may also be physically located at various locations, including being distributed such that portions of functions are implemented at different physical locations.

By way of example, and not limitation, a non-transitory computer-readable medium may include Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory, Compact Disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code elements in the form of instructions or data structures and that can be accessed by a general or special purpose computer, or a general or special purpose processor.

As used herein (including in the claims), an "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list such that, for example, a list of at least one of A, B or C means a or B or C or AB or AC or BC or ABC (i.e., a and B and C). Further, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition a" may be based on both condition a and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on" is interpreted.

In the drawings, similar components or features may have the same reference numerals. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description applies to any one of the similar components having the same first reference label irrespective of the second or other subsequent reference label.

The description set forth herein in connection with the appended drawings describes example configurations and is not intended to represent all examples that may be implemented or within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.