Patent ID: 12245320

DETAILED DESCRIPTION

Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

As used herein, the term “base station” may refer to either a terrestrial base station (e.g., as reached by the UE via a satellite as in the terrestrial base station104ofFIG.1) or a satellite base station (e.g., a satellite that itself performs base station functionalities as in the satellite base station206ofFIG.2).

As used herein, “coverage” may mean that the UE is in a state of being able to communicate with a RAN of a wireless communication system via a cell of the RAN.

FIG.1illustrates a non-terrestrial network (NTN) architecture100of a wireless communication system, according to an embodiment. The NTN architecture100includes a core network (CN)102, a terrestrial base station104, a satellite gateway106, a satellite108, and a UE110. The terrestrial base station104, the satellite gateway106, and the satellite108may be included in a RAN112.

In some embodiments, the RAN112includes E-UTRAN, the CN102includes an EPC and the terrestrial base station104includes an eNB. In these cases, the CN link114connecting the CN102and the terrestrial base station104may include an S1 interface.

In some embodiments, RAN112includes NG-RAN, the CN102includes a 5GC and the terrestrial base station104includes a gNB or a next generation eNB (ng-eNB). In such cases, the CN link114connecting the CN102and the terrestrial base station104may include an NG interface.

The NTN architecture100illustrates a “bent-pipe” or “transparent” satellite based architecture. In such bent-pipe systems, the terrestrial base station104uses the satellite gateway106to communicate with the satellite108over a feeder link116. The satellite108may be equipped with one or more antennas capable of broadcasting a cell according to the RAN112, and the UE110may be equipped with one or more antennas (e.g., a moving parabolic antenna, an omni-directional phased-array antenna, etc.) capable of communicating with the satellite108via a Uu interface on that cell (such communications may be said to use the illustrated service link118). A payload sited on the satellite108then transparently forwards data between the satellite gateway106and the UE110using the feeder link116between the satellite gateway106and the satellite108and the service link118between the satellite108and the UE110. The payload may perform RF conversion and/or amplification in both uplink (UL) and downlink (DL) to enable this communication.

In the embodiment shown inFIG.1, the terrestrial base station104is illustrated without the capability of terrestrial wireless communication directly with a UE. However, it is contemplated that in other embodiments, such a terrestrial base station using the satellite gateway106to communicate with the satellite108could (also) have this functionality (e.g., as in the terrestrial base station812and the terrestrial base station814ofFIG.8, to be described below).

FIG.2illustrates an NTN architecture200of a wireless communication system, according to an embodiment. The NTN architecture200includes a CN202, a satellite gateway204, a satellite base station206, and a UE208. The satellite gateway204and the satellite base station206may be included in the RAN210.

In some embodiments, the RAN210includes E-UTRAN and the CN202includes an EPC. In these cases, the CN link212connecting the CN202and the satellite gateway204may include an S1 interface.

In some embodiments, RAN210includes NG-RAN and the CN202includes a 5GC. In such cases, the CN link212connecting the CN202and the satellite gateway204may include an NG interface.

The NTN architecture100implements a “regenerative” satellite based architecture. In such regenerative systems, the functionalities of a base station are sited on the satellite base station206, and the communications between these base station functions and the CN202occur through a forwarding of interface(s) (e.g., a S1 interface and/or an NG interface) found on the CN link212through the satellite gateway204and a feeder link214to the satellite base station206. The satellite base station206may be equipped with one or more antennas capable of broadcasting a cell according to the RAN210, and the UE208may be equipped with one or more antennas (e.g., a moving parabolic antenna, an omni-directional phased-array antenna, etc.) capable of communicating with the satellite base station206via a Uu interface on that cell (such communications may be said to use the illustrated service link216). A payload sited on the satellite base station206then forwards data between the satellite gateway204and the UE208using the feeder link214between the satellite gateway204and the satellite base station206and the service link216between the satellite base station206and the UE208. The payload may perform RF conversion and/or amplification in both uplink (UL) and downlink (DL) to enable this communication, as well as implement the functionalities of the base station (e.g., as an eNB, ng-eNB or a gNB, as corresponding to the type of the RAN210) as these have been sited on the satellite base station206.

In embodiments of NTN architectures comprising NG-RAN that also use integrated access and backhaul (IAB), it is possible that a gNB control unit functionality (CU) could be sited terrestrially and may use a satellite gateway to communicate with a satellite that hosts a corresponding gNB donor unit functionality (DU), with the F1 interface(s) between the CU and the DU underpinned by the feeder link214. In such cases, the CU and the DU may each be understood to be part of the NG-RAN.

In wireless communications systems using NTN architectures (such as those described in relation toFIG.1andFIG.2above), it may be that coverage holes may exist when the density of satellites used is insufficient to provide cells covering the entire network operator's deployment area.

Such coverage holes may be spatial and/or temporal in nature. An example of a spatial coverage hole may be that a satellite may provide coverage of a first area, and there may not be a second satellite providing a cell to a second area (meaning that the second area is a coverage hole). As a UE using the satellite to communicate moves, it may leave the first area and enter the second area such that it leaves coverage.

Temporal coverage holes may occur due to satellite movement relative to a fixed position on the planetary surface. While some satellites of some NTNs may be placed in a geostationary earth orbit (GEO), this requires placement at a specific radius relative to the earth. Further, this distance is further out that many feasible distances for low earth orbits (LEOs) or medium earth orbits (MEOs) where a satellite could alternatively be placed. Accordingly, due to cost, orbital capacity, and other factors, it is anticipated that (at least some) satellites of (at least some) NTNs may be placed in, for example, LEOs or MEOs (rather than GEOs).

However, a satellite in LEO or MEO (instead of GEO) travels faster than the rotation speed of the earth in order to maintain its orbit. Accordingly, from the perspective of a fixed position on the earth's surface, such a satellite will move (taking any of its cells along with it). This may occur even in the case of quasi-earth fixed cells (where a satellite changes an antenna beam pattern to illuminate a determined portion of the surface while it is moving), as eventually the satellite (due to movement) will be outright unable to reach that portion of the surface. Thus, a UE at that position on the surface may enjoy coverage provided by the satellite when the satellite is in an appropriate location within its orbit to provide a cell at that position, and may lose coverage (fall into a temporal coverage hole) as the satellite moves further along its orbit.

In networks (or portions of networks) implementing terrestrial transmission reception points (TRPs), when a UE leaves coverage provided by a terrestrial TRP (e.g., due to UE mobility), the UE may be configured to continuously/constantly perform cell search. This behavior may be based on an implicit assumption that the UE is relatively likely to soon enter a coverage state associated with the same or another terrestrial TRP in such networks (e.g., due to an underlying assumption that the UE is likely being operated in locations where terrestrial-based coverage is anticipated by the user of the UE).

However, due to the cost and complexity of provisioning satellites for an NTN (as compared to, e.g., providing terrestrial TRPs), the satellite density of the NTN and thus the density of cells corresponding to the satellites of the NTN may be relatively lower than in the network (or portion of the network) using terrestrial TRPs. Accordingly, it may be expected that UEs operating using cells provided by the satellites of NTNs may encounter more frequent and extended periods of time (relative to a typical terrestrial TRP case) where they are out of coverage (due to their entry into the coverage holes described above). Herein, a UE that is expected to experience these (or other) types of frequent and extended periods out of coverage may be said to be experiencing “discontinuous coverage.”

It may be that some UE use the satellites of the NTN for coverage (and thus may experience discontinuous coverage) because they are located remotely from established infrastructure supporting terrestrial TRPs. This may motivate a use of lower amounts of power at such a UE (e.g., to conserve a battery of the UE and/or to not overtax a relatively limited power source for the UE such as a small solar panel). It may also be that satellites of the NTN can also benefit from power savings, in that these are also usually supplied with power by more limited power sources that can be available while in orbit, such as batteries and/or solar panels.

In these NTN (and other) circumstances, it may be beneficial to configure one or more elements of the wireless communication system to gracefully suspend/interrupt certain procedures (e.g., cell search/connect/camping procedures at the UE, network paging/communication procedures that use the satellite, etc.) in reaction to a loss of coverage at the UE due to a coverage hole, out of a recognition that there is no point in using power to perform these procedures during periods when communications are in any event not possible.

Then, assuming that an ephemeris for the satellites of the NTN is known at the UE (e.g., via pre-configuration and/or by system information provided by one or more satellites themselves), and that the location and/or mobility of the UE is known to the UE (e.g., via preconfiguration (in the case of a stationary UE) and/or global positioning system (GPS)/global navigation satellite system (GNSS) (in the case of a mobile UE)), it may be that the UE can predict when and/or where it is likely to be in or out of coverage. Accordingly, the UE may preemptively (prior to losing coverage) inform the either/both of a CN (e.g., via non-access stratum (NAS) messages) and/or a base station (e.g., via access stratum (AS) messages, such as radio resource control (RRC) messages) that it is going to lose coverage, and/or when and/or where it will regain coverage. The CN/base station may then accordingly be aware of the later time and/or location at which coverage to the UE is expected to be restored. This time and/or location may be used to restart, at the relevant element (UE, CN, base station) any suspended procedures of the wireless communication system relative to these elements.

In some cases, the UE may send the CN a NAS message comprising a release request in response to a determination, at the UE, that it is going out of coverage. The release request may indicate to the CN that the UE is going out of coverage. In some embodiments, the UE may also send assistance information (e.g., either in the same NAS message comprising the release request, or in a separate message).

In the case of a CN that is an EPC, the NAS message having the release request may be a tracking area update (TAU) message, a service request message, or a generic uplink NAS transport message. In the case of a CN that is a 5GC, the NAS message having the release request may be a mobility registration update (MRU) message, a service request message, or an uplink NAS transport message. Alternatively, a new mobility management (MM) message could be defined and used.

In response to the release request, the CN may, among other things, interrupt any paging of the UE that the CN may otherwise perform. Paging by the CN may include a process whereby the CN (via the RAN) informs the UE that there is available DL data for the UE, with such paging occurring according to a discontinuous reception (DRX) schedule or the like being used at the UE. Due to receiving the release request, the CN is aware that subsequent paging (at least for a time) will not be received at the UE (because the UE is leaving coverage). Accordingly, to save transmission resources within the NTN (e.g., at the satellite), the CN interrupts its paging process.

Later, the CN may resume paging the UE. This resumption may occur according to any assistance information that was received with or corresponding to the NAS message having the release request, as described above. The assistance information may include an outage time duration representing the amount of time that the UE expects to be out of coverage. The UE may calculate this amount of time, in some cases, through the use of the UE location information (e.g., as determined by GPS/GNSS) and satellite ephemeris information for satellites of the NTN. In cases where the UE expects to itself move during the time that it is out of coverage, the UE may also use its current and/or past mobility information (mobility amount, mobility direction), to inform the calculation of this amount of time. In such cases, the CN may resume paging the UE once the outage time duration passes (e.g., relative to the interruption of the UE paging by the CN). The outage time duration may also be useful to the CN in determining the dimensions of any network buffers for the UE.

The assistance information may indicate that the CN should resume paging the UE after an interruption duration (ultimately) determined by the CN. The interruption duration may be determined by the CN based on an indication, from the UE, of an amount of time that the UE expects to be out of coverage. This interruption duration may be determined to be equal to, or greater than, any UE-indicated outage time duration. In such cases, the CN may resume paging the UE once the interruption duration passes (e.g., relative to the interruption of the UE paging by the CN). In some embodiments, the CN sends the UE the interruption duration, which may allow the UE to be aware of when to expect paging to resume (such that it does not waste resources attempting to receive paging during the period that any paging for the UE is interrupted at the CN).

The assistance information may indicate that the CN should resume paging the UE after it receives a TAU message or an MRU message from the UE. In such cases, the network may assume that the UE will be out of coverage until such a time as it is shown otherwise via a reception of the TAU message or the MRU message from the UE. In such cases, the CN may resume paging the UE once a TAU message or a MRU message is received.

The assistance information may indicate a location where the UE is likely to be found where it later enters coverage. This may be particularly beneficial in the case that the UE is expected to move during the period that it is out of coverage. Prior to going out of coverage, the UE may make a current mobility estimate, and determine a location where it is likely to be present when it later enters coverage based on this mobility estimate and the known satellite ephemeris information. In a first case, the UE may provide GPS/GNSS coordinates and a radius (of a circle crawn out with the GPS/GNSS coordinates at the center) corresponding to an area including the location where it is likely to be found when it later enters coverage. The size of the area (e.g., corresponding to the length/size of the radius) so determined may depend on the mobility estimate of the UE (e.g., with a higher mobility estimate corresponding to a larger area/radius). The UE can send GPS/GNSS coordinates and/or the radius that so indicate the location to the CN in the assistance information.

In a second case, the assistance information may indicate the location with a cell index. In other words, the UE may provide, in the assistance information, a cell index (e.g., as mapped to TN cells, or some (other) kind of virtual cell index) for a cell that provides coverage to the location where it is likely to be when it later enters coverage. Once the location where the UE is likely to be found is known at the CN, the CN can resume paging the UE at some later time at that location (e.g., as opposed to some other potentially irrelevant location, thereby reducing the paging burden on the network).

In some embodiments, the assistance information sent by the UE may further include the UE's data treatment preference. This data treatment preference may describe the manner in which the UE prefers the CN treat any DL data for the UE while the UE is out of coverage. For example, it may be that in some cases, the UE prefers that some of all of the DL data for the UE is kept until the UE later enters coverage, such that it can be sent to the UE at that time. In other cases, the UE may prefer that some or all of the DL data for the UE is instead discarded. The CN may accordingly handle the DL data. These indications may be made by the UE to the CN relative to identifications of PDU sessions (5GS) or PDN connections (EPS) for which DL data is to be kept or discarded, as the case may be.

FIG.3illustrates a method300of a CN, according to an embodiment. The method300includes receiving302, from a UE, a release request and assistance information, the release request indicating that the UE is leaving coverage corresponding to the CN.

The method300further includes interrupting304a paging of the UE in response to the release request.

The method300further includes resuming306the paging of the UE according to the assistance information.

In some embodiments of the method300, the assistance information comprises an outage time duration during which the UE expects to be out of the coverage, and wherein the resuming of the paging of the UE occurs after the outage time duration passes.

In some embodiments of the method300, the assistance information indicates that the CN should resume the paging after an interruption duration determined by the CN, and wherein the resuming of the paging of the UE occurs after the interruption duration passes. In some of these embodiments, the method300further includes sending, to the UE, the interruption duration.

In some embodiments of the method300, the assistance information indicates that the CN should resume the paging after it receives one of a TAU message and an MRU message from the UE.

In some embodiments of the method300, the assistance information indicates a location where the UE is likely to be found when it later enters the coverage, and wherein the resuming of the paging of the UE occurs at the location. In some of these embodiments, the location is indicated with a GNSS coordinate. In some of these embodiments, the location is indicated with a GPS coordinate. In some of these embodiments, the location is indicated with a cell index.

In some embodiments of the method300, the assistance information comprises a data treatment preference for the handling of data for the UE while the UE is out of the coverage, and the method300further includes handling the data for the UE while the UE is out of the coverage according to the data treatment preference.

Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method300. This apparatus may be, for example, an apparatus of a CN (such as a CN device936, as described herein).

Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method300. This non-transitory computer-readable media may be, for example, a memory of a CN (such as a memory940of a CN device936, as described herein).

Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method300. This apparatus may be, for example, an apparatus of a CN (such as a CN device936, as described herein).

Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method300. This apparatus may be, for example, an apparatus of a CN (such as a CN device936, as described herein).

Embodiments contemplated herein include a signal as described in or related to one or more elements of the method300.

Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method300. The processor may be a processor of a CN (such as a processor(s)938of a CN device936, as described herein). These instructions may be, for example, located in a processor and/or on a memory of the CN (such as processor(s)938and memory940of a CN device936, as described herein).

FIG.4illustrates a method400of a UE, according to an embodiment. The method400includes determining402duration that the UE is likely to be out of coverage based on a current location of the UE and satellite ephemeris information. In cases of the method400where the UE expects to move while it is out of coverage, the determining402may further use current mobility information for the UE when determining402the duration.

The method400further optionally includes determining404a likely location of the UE when it later enters coverage based on the current mobility information for the UE and the satellite ephemeris information.

The method400further includes sending406, to a CN, the duration.

Embodiments of the method400that include the determining404further optionally include sending408, to the CN, the likely location.

In some embodiments of the method400including the sending408, the likely location is sent to the CN as one or more of GPS coordinates and GNSS coordinates.

In some embodiments of the method400including the sending408, the likely location is sent to the CN as a cell index.

Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method400. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method400. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory906of a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method400. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method400. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include a signal as described in or related to one or more elements of the method400.

Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method400. The processor may be a processor of a UE (such as a processor(s)904of a wireless device902that is a UE, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory906of a wireless device902that is a UE, as described herein).

Once the UE leaves coverage, it may be beneficial for the UE to enter a low power usage mode so that less power is used while the UE is out of coverage. As a first example, for a UE that is an LTE device, the low power mode may be a power save mode (PSM). A PSM may be similar to a power-off mode for the UE, in that there is no monitoring of DL transmissions from a base station. However, in PSM, the UE remains registered with the network. Further, the UE may periodically wake up according to a timer in order to send periodic tracking area update (TAU) messages to the CN via the base station.

As another example, for a UE that is a 5G device, the low power mode may be a mobile initiated connection only (MICO) mode. This MICO mode may be similar to the PSM described above (however, with some differences). For the MICO mode, if an AMF of the 5GC in communication with the UE has provided a “strictly periodic registration time indication” to the UE (and assuming that the UE supports the same), the UE periodically wakes up to send a mobility registration update (MRU) message as a timer set for the amount of time in the strictly periodic registration indication message periodically expires while the UE remains in a connection management (CM) idle (CM-IDLE) mode.

A PSM or a MICO mode may be examples of “low power usage modes” as used herein. Further, a TAU message of a PSM and/or an MRU message of a MICO mode may be examples of “mobility update messages” as used herein. Timers that control the (periodic) wakeup timing for a UE in a low power usage mode may be examples of “low power usage timers” as disclosed herein.

For cases where the UE is in a low power usage mode, the UE behavior when the UE finds itself out of coverage when it wakes up in order to send a mobility update message may be unknown/undefined. In such cases where NTN satellites are used for coverage (as described above), it may be beneficial for the UE to avoid unnecessary cell selection/re-selection procedures (e.g., including the sending of such mobility update messages) when it is out of coverage. Because, as described above, it is not necessarily expected in this situation that the UE (may) re-enter a coverage state at any given time (and a time for re-entering coverage, as described above, may not have arrived yet), the use of the power needed to perform these operations has a relatively higher likelihood (as opposed to the terrestrial TRP use case) of being wasted. Accordingly, it may be beneficial to establish methods of waking according to one of the PSM and the MICO mode in NTN discontinuous coverage scenarios in ways that can save power and/or network resources. These methods may be discussed herein as “discontinuous coverage power saving modes.”

A UE may indicate support of discontinuous coverage methods/modes in an attach message to the CN and/or in a mobility update message to the CN. Accordingly, the network may be apprised of the UE ability to use a discontinuous coverage power saving mode (e.g., prior to a use by the UE of the discontinuous coverage power saving mode behaviors discussed here, such that the CN is prepared to operate with those behaviors).

In a first case, upon wakeup from a low power usage mode (when a low power usage mode timer expires), a UE first determines whether it is in coverage. If the UE is in coverage, the UE sends the mobility update message. If the UE is not in coverage, the UE does not send the mobility update message. Instead, the UE continuously checks for coverage, and sends the mobility update message when it determines that it has entered coverage.

In a second case, upon wakeup from a low power usage mode (when a low power usage mode timer expires), a UE first determines whether it is in coverage. If the UE is in coverage, the UE sends the mobility update message. If the UE is not in coverage, the UE does not send the mobility update message. Instead, the UE starts a periodic coverage checking timer. Upon each expiration of the coverage checking timer, the UE checks whether it is in coverage, and sends the mobility update message when it determines (according to one of these periodic checks) that it has entered coverage. In between the checks according to the coverage checking time, the UE may return to the low power usage mode.

FIG.5illustrates a method500of a UE, according to an embodiment. The method500optionally includes receiving, from a CN, a duration for a coverage checking timer.

The method500further includes entering504a low power usage mode upon leaving coverage corresponding to a CN.

The method500further includes starting506a low power usage mode timer.

The method500further includes determining508, after an expiration of the low power usage mode timer, that the UE has entered coverage.

The method500further includes sending510a mobility update message to the CN upon determining that the UE has entered the coverage.

Some embodiments of the method500further include indicating that the UE supports a discontinuous coverage power saving mode.

In some embodiments of the method500, the determining508, after the expiration of the low power usage mode timer, that the UE has entered the coverage comprises continuously checking whether the UE has entered the coverage after the expiration of the low power usage mode timer.

In some embodiments of the method500that include the receiving502, the determining508, after the expiration of the low power usage mode timer, that the UE has entered the coverage comprises checking whether the UE has entered the coverage periodically according to the duration of the coverage checking timer.

In some embodiments of the method500, the low power usage mode is one of a PSM and a MICO mode.

In some embodiments of the method500, the mobility update message comprises one of a TAU message and a MRU message.

Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method500. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method500. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory906of a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method500. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method500. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include a signal as described in or related to one or more elements of the method500.

Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method500. The processor may be a processor of a UE (such as a processor(s)904of a wireless device902that is a UE, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory906of a wireless device902that is a UE, as described herein).

In some cases, a UE may send a base station an RRC message including a release request in response to a determination, at the UE, that it is going out of coverage. The release request may indicate to the base station that the UE is going out of coverage. It is contemplated that the coverage being left could be a coverage provided by the RAN itself, or more generally any coverage provided by any RAN of an associated CN.

In some cases, such an RRC message may be a new RRC message developed for this use. It is also contemplated that a pre-existing RRC message may be modified for this use. For example, a UEAssistanceInformation message may be modified to include the release request so that it may be used for this purpose.

In response to the receipt of the release request in the RRC message, the RAN may release the UE to an RRC idle mode or (in the case where the UE is connected through the RAN to a 5GC) an RRC inactive mode.

In the case where the RRC idle mode is used, the RAN may also indicate a time duration for which the UE is not required to perform cell selection/re-selection methods (e.g., including cell measurements and/or monitoring of control channels).

In the case where the RRC inactive mode is used, the RAN may (additionally, or alternatively) indicate a future time at which it intends to resume RAN paging. This may allow the UE to pause any attempt to interact with the RAN until that time (such that power that would have been used for this purpose during that time may be saved).

When the base station receives the RRC message, it may further inform the CN to which the UE connects through the RAN to suspend the connection to the UE.

In some cases, the RRC message may also include assistance information. This assistance information may in some cases be similar to that described above in relation to NAS messaging. For a first example, this assistance information may indicate an outage time duration during which the UE expects to be out of coverage. As another example, the assistance information may indicate a location where the UE is likely to be found when it later enters coverage. As another example, the assistance information may indicate a data treatment preference for the handling of data for the UE while the UE is out of coverage. As another example, the assistance information may indicate that the CN should resume paging after an interruption duration determined by the CN (e.g., as potentially informed by a UE recommendation for that value, in the manner described above). Each of these items of assistance information may be presented by the UE according to the manner previously described.

Then, when the base station receives the RRC message, the RAN (e.g., via the base station) may indicate to the CN that the UE has made the release request, such that, for example, unnecessary paging (from the CN) can be dropped according to this assistance information (as previously discussed). Any relevant assistance information may be forwarded by the RAN (e.g., via the base station) to the CN.

In some embodiments, the decision to trigger the RRC message may be made at the UE and may be based on UE implementation. In some embodiments, the RAN may control when the UE can trigger the RRC message. For example, the RAN may send the UE a condition messaging having one or more conditions according to which the UE may (or should) perform the sending of the RRC message. The sending of the RRC message may then be performed at the UE according to the condition(s) (e.g., the RRC message may be sent if the condition(s) are met). RAN control of conditions when the UE can trigger the RRC message may, for example, simplify implementation of these methods for operators of NTNs and/or help them maintain control of such NTNs generally.

In a first example, a condition may be that the UE is at a location indicated by the condition message. For example, the condition message may indicate a set of GPS and/or GNSS coordinates and a radius. The UE may accordingly trigger the RRC message if it is inside of a circle corresponding to the measurement of the radius amount outward from the GPS and/or GNSS coordinates.

In a second example, a condition may be that a current time maps to a time indication in the condition message. For example, the condition message may include a time indication (e.g., 6 PM to 12 PM every Monday). The UE may accordingly trigger the RRC message if a current time (as determined at the UE) maps to the time indication (e.g., if the UE determines that is between 6 PM and 12 PM on a Monday). It is contemplated that a time indication may be given using time (e.g., corresponding to single time or a range of times), days of the week, months of the year, years, etc. and/or any combination of these.

It is contemplated that these uses of the RRC message may be implemented for either/both NR NTNs and in LTE systems using NTNs, such as an LTE-based IoT NTN network.

FIG.6illustrates a method600of a UE, according to an embodiment. The method600optionally includes receiving602, from a base station, a condition message comprising a condition according to which the UE may perform a sending of an RRC message comprising a release request that indicates that the UE is leaving coverage.

The method600further includes sending604, to the base station, the RRC message comprising the release request. In embodiments of the method600that include the receiving602, the sending604is performed according to the condition.

The method600further includes receiving606, from the base station, an RRC release message.

The method600further includes entering608one of an RRC idle mode and an RRC inactive mode in response to the RRC release message.

In some embodiments of the method600, the RRC message is a UEAssistanceInformation message

In some embodiments of the method600, the RRC release message indicates a duration during which the UE is not expected to perform cell selection methods.

In some embodiments of the method600, the one of the RRC idle mode and the RRC inactive mode comprises the RRC inactive mode, and the RRC release message indicates a time at which a RAN of the base station intends to resume RAN paging.

In some embodiments of the method600, the RRC message includes assistance information indicating an outage time duration during which the UE expects to be out of the coverage.

In some embodiments of the method600, the RRC message includes assistance information indicating a location where the UE is likely to be found when it later enters the coverage.

In some embodiments of the method600, the RRC message includes assistance information indicating a data treatment preference for the handling of data for the UE while the UE is out of the coverage.

In some embodiments of the method600, the RRC message includes assistance information indicating that a CN corresponding to the base station should resume paging after an interruption duration determined by the CN.

In some embodiments of the method600that include the receiving602, the condition is that the UE is at a location indicated by the condition message.

In some embodiments of the method600that include the receiving602, the condition is that a current time maps to a time indication in the condition message.

Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method600. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method600. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory906of a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method600. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method600. This apparatus may be, for example, an apparatus of a UE (such as a wireless device902that is a UE, as described herein).

Embodiments contemplated herein include a signal as described in or related to one or more elements of the method600.

Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method600. The processor may be a processor of a UE (such as a processor(s)904of a wireless device902that is a UE, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory906of a wireless device902that is a UE, as described herein).

FIG.7illustrates a method700of a base station, according to an embodiment. The method700optionally includes sending702, to a UE, a condition message comprising a condition according to which the UE may perform a sending of an RRC message comprising a release request that indicates that the UE is leaving coverage.

The method700further includes receiving704, from the UE, the RRC message comprising the release request.

The method700further includes sending706, to the UE, an RRC release message.

The method700further optionally includes forwarding708, to a CN corresponding to the base station, assistance information from the RRC message.

In some embodiments of the method700, the RRC message is a UEAssistanceInformation message.

In some embodiments of the method700the RRC release message indicates a duration during which the UE is not expected to perform cell selection methods.

In some embodiments of the method700the RRC release message indicates a time at which a RAN of the base station intends to resume RAN paging.

In some embodiments of the method700including the forwarding708, the assistance information from the RRC message indicates an outage time duration during which the UE expects to be out of the coverage.

In some embodiments of the method700including the forwarding708, the assistance information from the RRC message indicates a location where the UE is likely to be found when it later enters the coverage.

In some embodiments of the method700including the forwarding708, the assistance information from the RRC message indicates a data treatment preference for the handling of data for the UE while the UE is out of the coverage.

In some embodiments of the method700including the forwarding708, the assistance information from the RRC message indicates that the CN should resume paging after an interruption duration determined by the CN.

In some embodiments of the method700that include the sending702, the condition is that the UE is at a location indicated by the condition message.

In some embodiments of the method700, that include the sending702, the condition is that a current time maps to a time indication in the condition message.

Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method700. This apparatus may be, for example, an apparatus of a base station (such as a RAN device918that is a base station, as described herein).

Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method700. This non-transitory computer-readable media may be, for example, a memory of a base station (such as a memory922of a RAN device918that is a base station, as described herein).

Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method700. This apparatus may be, for example, an apparatus of a base station (such as a RAN device918that is a base station, as described herein).

Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method700. This apparatus may be, for example, an apparatus of a base station (such as a RAN device918that is a base station, as described herein).

Embodiments contemplated herein include a signal as described in or related to one or more elements of the method700.

Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method700. The processor may be a processor of a base station (such as a processor(s)920of a RAN device918that is a base station, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the base station (such as a memory922of a RAN device918that is a base station, as described herein).

FIG.8illustrates an example architecture of a wireless communication system800, according to embodiments disclosed herein. The following description is provided for an example wireless communication system800that operates in conjunction with the LTE system standards and/or 5G or NR system standards as provided by 3GPP technical specifications and other 3GPP documents.

As shown byFIG.8, the wireless communication system800includes UE802and UE804(although any number of UEs may be used). In this example, the UE802and the UE804are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

The UE802and UE804may be configured to communicatively couple with a RAN806. In embodiments, the RAN806may be NG-RAN, E-UTRAN, etc. The UE802and UE804utilize connections (or channels) (shown as connection808and connection810, respectively) with the RAN806, each of which comprises a physical communications interface. The RAN806can include one or more base stations (such as terrestrial base station812, the terrestrial base station814the satellite base station836and the satellite base station838) and/or other entities (e.g., the satellite842, which may not have base station functionality) that enable the connection808and connection810. One or more satellite gateways834may integrate the satellite base station836, satellite base station838, and/or the satellite842into the RAN806, in the manners (and with the appropriate elements) described in relation to the NTN architecture100ofFIG.1and the NTN architecture200ofFIG.2.

In this example, the connection808and connection810are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN806, such as, for example, an LTE and/or NR. It is contemplated that the connection808and connection810may include, in some embodiments, service links between their respective UE802, UE804and one or more of the satellite base station836, the satellite base station838, and the satellite842.

In some embodiments, the UE802and UE804may also directly exchange communication data via a sidelink interface816.

The UE804is shown to be configured to access an access point (shown as AP818) via connection820. By way of example, the connection820can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP818may comprise a Wi-Fi® router. In this example, the AP818may be connected to another network (for example, the Internet) without going through a CN824.

In embodiments, the UE802and UE804can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other, with the terrestrial base station812, the terrestrial base station814, the satellite base station836, the satellite base station838, and/or the satellite842over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, all or parts of the terrestrial base station812, terrestrial base station814, the satellite base station836and/or the satellite base station838may be implemented as one or more software entities running on server computers as part of a virtual network.

In addition, or in other embodiments, the terrestrial base station812or terrestrial base station814may be configured to communicate with one another via interface822. In embodiments where the wireless communication system800is an LTE system (e.g., when the CN824is an EPC), the interface822may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC. It is contemplated than an inter-satellite link (ISL) may carry the X2 interface between in the case of two satellite base stations.

In embodiments where the wireless communication system800is an NR system (e.g., when CN824is a 5GC), the interface822may be an Xn interface. An Xn interface is defined between two or more base stations that connect to 5GC (e.g., CN824). For example, the Xn interface may be between two or more gNBs that connect to 5GC, a gNB connecting to 5GC and an eNB, between two eNBs connecting to 5GC, and/or two or more satellite base stations via an ISL (as in, e.g., the interface840between the satellite base station836and the satellite base station838).

The RAN806is shown to be communicatively coupled to the CN824. The CN824may comprise one or more network elements826, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE802and UE804) who are connected to the CN824via the RAN806. The components of the CN824may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). For example, the components of the CN824may be implemented in one or more processors and/or one or more associated memories.

In embodiments, the CN824may be an EPC, and the RAN806may be connected with the CN824via an S1 interface828. In embodiments, the S1 interface828may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the terrestrial base station812, terrestrial base station814, the satellite base station836, or the interface840and a serving gateway (S-GW), and the S1-MME interface, which is a signaling interface between the terrestrial base station812, the terrestrial base station814the satellite base station836, or the interface840and mobility management entities (MMEs).

In embodiments, the CN824may be a 5GC, and the RAN806may be connected with the CN824via an NG interface828. In embodiments, the NG interface828may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the terrestrial base station812, terrestrial base station814, satellite base station836, or satellite base station838and a user plane function (UPF), and the S1 control plane (NG-C) interface, which is a signaling interface between the terrestrial base station812, terrestrial base station814satellite base station836, or satellite base station838and access and mobility management functions (AMFs).

Generally, an application server830may be an element offering applications that use internet protocol (IP) bearer resources with the CN824(e.g., packet switched data services). The application server830can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE802and UE804via the CN824. The application server830may communicate with the CN824through an IP communications interface832.

FIG.9illustrates a system900for performing signaling934between a wireless device902and a RAN device918connected to a core network of a CN device936, according to embodiments disclosed herein. The system900may be a portion of a wireless communications system as herein described. The wireless device902may be, for example, a UE of a wireless communication system. The RAN device918may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system that is a terrestrial base station or a satellite base station. The CN device936may be one or more devices making up a CN, as described herein.

The wireless device902may include one or more processor(s)904. The processor(s)904may execute instructions such that various operations of the wireless device902are performed, as described herein. The processor(s)904may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

The wireless device902may include a memory906. The memory906may be a non-transitory computer-readable storage medium that stores instructions908(which may include, for example, the instructions being executed by the processor(s)904). The instructions908may also be referred to as program code or a computer program. The memory906may also store data used by, and results computed by, the processor(s)904.

The wireless device902may include one or more transceiver(s)910that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna(s)912of the wireless device902to facilitate signaling (e.g., the signaling934) to and/or from the wireless device902with other devices (e.g., the RAN device918) according to corresponding RATs. In some embodiments, the antenna(s)912may include a moving parabolic antenna, an omni-directional phased-array antenna, or some other antenna suitable for communication with a satellite, (e.g., as described above in relation to the UE110ofFIG.1and the UE208ofFIG.2).

For a RAN device918that is a terrestrial base station, the network device signaling934may occur on a feeder link between the wireless device902and a satellite and a service link between the satellite and the RAN device918(e.g., as described in relation toFIG.1). For a RAN device918that is a satellite base station, the signaling934may occur on a feeder link between the wireless device902and the RAN device918(e.g., as described in relation toFIG.2).

The wireless device902may include one or more antenna(s)912(e.g., one, two, four, or more). For embodiments with multiple antenna(s)912, the wireless device902may leverage the spatial diversity of such multiple antenna(s)912to send and/or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device902may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device902that multiplexes the data streams across the antenna(s)912according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and/or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

In certain embodiments having multiple antennas, the wireless device902may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s)912are relatively adjusted such that the (joint) transmission of the antenna(s)912can be directed (this is sometimes referred to as beam steering).

The wireless device902may include one or more interface(s)914. The interface(s)914may be used to provide input to or output from the wireless device902. For example, a wireless device902that is a UE may include interface(s)914such as microphones, speakers, a touch-screen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s)910/antenna(s)912already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

The wireless device902may include a release module916. The release module916may be implemented via hardware, software, or combinations thereof. For example, the release module916may be implemented as a processor, circuit, and/or instructions908stored in the memory906and executed by the processor(s)904. In some examples, the release module916may be integrated within the processor(s)904and/or the transceiver(s)910. For example, the release module916may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s)904or the transceiver(s)910.

The release module916may be used for various aspects of the present disclosure, for example, aspects ofFIG.3throughFIG.7. The release module916is configured to for example, generate NAS messages to be sent to a core network (which may include a release request and/or assistance information); determine whether a UE is out of coverage, enter a low power usage mode, implement one or more timers such as a low power usage mode timer and/or a coverage checking timer, and generate a mobility update message for a CN after the UE returns to coverage; and/or generate RRC messages to be sent to a base station (which may include a release request and/or assistance information), etc., as described herein.

The RAN device918may include one or more processor(s)920. The processor(s)920may execute instructions such that various operations of the RAN device918are performed, as described herein. The processor(s)920may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

The RAN device918may include a memory922. The memory922may be a non-transitory computer-readable storage medium that stores instructions924(which may include, for example, the instructions being executed by the processor(s)920). The instructions924may also be referred to as program code or a computer program. The memory922may also store data used by, and results computed by, the processor(s)920.

The RAN device918may include one or more transceiver(s)926that may include RF transmitter and/or receiver circuitry that use the antenna(s)928of the RAN device918to facilitate signaling (e.g., the signaling934) to and/or from the RAN device918with other devices (e.g., the wireless device902) according to corresponding RATs.

The RAN device918may include one or more antenna(s)928(e.g., one, two, four, or more). In embodiments having multiple antenna(s)928, the RAN device918may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

For a RAN device918that is a terrestrial base station, one or more of the transceiver(s)926and/or the antenna(s)928may instead be present on a satellite gateway associated with the base station (e.g., as shown in reference to the terrestrial base station104and the satellite gateway106ofFIG.1). For a RAN device918that is a satellite base station, the transceiver(s)926and/or the antenna(s)928may be present on the satellite, and one or more of those antenna(s)928may be antenna(s) appropriate for satellite communication (such as a moving parabolic antenna, an omni-directional phased-array antenna, etc.)

The RAN device918may include one or more interface(s)930. The interface(s)930may be used to provide input to or output from the RAN device918. For example, a RAN device918that is a base station may include interface(s)930made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s)926/antenna(s)928already described) that enables the base station to communicate with other equipment in a CN, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

The RAN device918may include a release module932. The release module932may be implemented via hardware, software, or combinations thereof. For example, the release module932may be implemented as a processor, circuit, and/or instructions924stored in the memory922and executed by the processor(s)920. In some examples, the release module932may be integrated within the processor(s)920and/or the transceiver(s)926. For example, the release module932may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s)920or the transceiver(s)926.

The release module932may be used for various aspects of the present disclosure, for example, aspects ofFIG.3throughFIG.7. The release module932is configured to, for example, send to a UE a condition message having a condition for which the UE may send an RRC message comprising a release request, receiving the RRC message, sending an RRC release message to the UE in response, and forwarding assistance information from the RRC message to a CN.

The RAN device918may communicate with the CN device936via the interface948, which may be analogous to the interface828ofFIG.8(e.g., may be an S1 and/or NG interface, either of which may be split into user plane and control plane parts).

The CN device936may include one or more processor(s)938. The processor(s)938may execute instructions such that various operations of the CN device936are performed, as described herein. The processor(s)938may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

The CN device936may include a memory940. The memory940may be a non-transitory computer-readable storage medium that stores instructions942(which may include, for example, the instructions being executed by the processor(s)938). The instructions942may also be referred to as program code or a computer program. The memory940may also store data used by, and results computed by, the processor(s)938.

The CN device936may include one or more interface(s)944. The interface(s)944may be used to provide input to or output from the CN device936. For example, a CN device936may include interface(s)930made up of transmitters, receivers, and other circuitry that enables the CN device936to communicate with other equipment in the CN, and/or that enables the CN device936to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the CN device936or other equipment operably connected thereto.

The CN device936may include a release module946. The release module932may be implemented via hardware, software, or combinations thereof. For example, the release module946may be implemented as a processor, circuit, and/or instructions942stored in the memory940and executed by the processor(s)938. In some examples, the release module946may be integrated within the processor(s)938. For example, the release module932may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s)938.

The release module946may be used for various aspects of the present disclosure, for example, aspects ofFIG.3throughFIG.7. The release module946is configured to, for example, receive NAS messaging from a UE having a release request and (optionally) assistance information, interrupt a paging (by the CN) of the UE in response to the release request, and resume a paging of the UE according to the assistance information. In some cases, the release module946is used to receive a indicate from a RAN device (such as a base station) that the UE has made a release request, and further to receive any assistance information that may have been forwarded to the CN device936by the RAN device, such that, e.g., the interruption of paging may be performed. The release module946may also be configured to respond (e.g., by resuming a paging of the UE by the CN) to a mobility update message received at the CN device936from a UE that was previously out of coverage.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.