KR101911197B1 - Handoff for satellite communication - Google Patents

Abstract

Various aspects of the disclosure relate to a handoff of a user terminal communicating with a satellite network portal through a satellite. In some aspects, the satellite network portal and the user terminal utilize the satellite handoff information to determine when to hand off the user terminal from one cell to another and / or from one satellite to another. In some aspects, the user terminal transmits capability information, location information, or other information to the satellite network portal, whereby based on this information, the satellite network portal generates satellite handoff information and / or And selects a handoff procedure for the user terminal. In some aspects, a handoff of a user terminal to a different satellite involves the user terminal performing satellite signal measurements and transmitting the measurement message to a satellite network portal. In some aspects, the satellite network portal generates new satellite handoff information as a result of receiving the measurement message.

Description

HANDOFF FOR SATELLITE COMMUNICATION < RTI ID = 0.0 >

Cross-reference to related application (s)

This application is a continuation-in-part application of Serial No. 14 / 856,933 filed on September 17, 2015, filed with the United States Patent and Trademark Office on April 28, 2016 Claims of priority and benefit of provisional application Serial No. 15 / 141,641, filed on May 1, 2015, and provisional application No. 62 / 156,063, filed with the USPTO on May 1, 2015, the entire contents of which are incorporated herein by reference .

The various aspects described herein relate to satellite communications, and more particularly, but not exclusively, to handoffs for non-geosynchronous satellite communications.

The satellite-based communication systems may include gateways, and one or more satellites for relaying communication signals between gateways and one or more user terminals. A gateway is an earth station having antennas for transmitting signals to communication satellites and for receiving signals from communication satellites. The gateways use satellites to connect user terminals to other user terminals or users of other communication systems such as the public switched telephone network, the Internet, and various public and / or private networks. Communication links. A satellite is a receiver and a repeater that traverse orbits used to relay information.

If the user terminal is within a " footprint " of the satellite, the satellite can receive signals from the user terminal and transmit signals to the user terminal. The satellite 's footprint is the geographical area on the Earth' s surface within the range of the satellite 's signals. The footprint is usually geographically divided into " cells " (e.g., " beams "), through the use of beam-forming antennas. Each cell (e.g., a beam) covers a specific geographic area within the footprint. Cells from the same satellite, or from different satellites, may overlap (e.g., partially overlap). For example, beams of a particular satellite may be directed such that more than one beam from the satellite covers the same particular geographic area.

Geosynchronous satellites have long been used for communication. The earth synchronous satellites are stationary for a given location on the earth such that timing shifts and Doppler frequency shifts in radio signal propagation between the communication transceiver and the earth synchronous satellite none. However, the geostationary satellites are limited to a geosynchronous orbit (GSO), a circle with a radius of approximately 42,164 km from the center of the earth just above the earth's equator, so the number of satellites that may be deployed in the GSO is limited do.

As alternatives to geostationary satellites, communication systems that use constellations of satellites in non-geocentric orbits, such as low-earth orbit (LEO) It has been designed to serve at least most of the planet. In non-geostationary satellite-based systems, such as LEO satellite-based systems, satellites move about ground-based communication devices such as gateways or user terminals. Thus, at some point in time, the user terminal will be handed off from one satellite to another.

The following presents a simplified overview of some aspects of the disclosure to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all the envisioned features of the disclosure, nor is it intended to identify key or critical elements of all aspects of the disclosure, nor is it intended to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present various concepts of some aspects of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.

The disclosure relates, in some aspects, to mobility and / or link management. Some aspects of the disclosure are directed to handoffs for non-geostationary satellite communications.

In one aspect, the disclosure provides an apparatus configured for communication comprising a memory and a processor coupled to the memory. The processor and the memory generate satellite handoff information that specifies a handoff time for a particular cell of a particular satellite; And transmit the satellite handoff information to the user terminal.

Another aspect of the disclosure includes generating satellite handoff information that specifies a handoff time for a particular cell of a particular satellite; And transmitting satellite handoff information to the user terminal.

Another aspect of the disclosure provides an apparatus configured for communication. The apparatus comprising: means for generating satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And means for transmitting satellite handoff information to the user terminal.

 Another aspect of the disclosure provides a method of generating satellite handoff information that specifies a handoff time for a particular cell of a particular satellite; And non-transitory computer-readable media storing computer-executable code comprising code for transmitting satellite hand-off information to a user terminal.

In one aspect, the disclosure provides an apparatus configured for communication comprising a memory and a processor coupled to the memory. The processor and the memory receive satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And to perform a handoff to a particular cell of a particular satellite based on the satellite handoff information.

Another aspect of the disclosure provides a method comprising: receiving satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And performing a handoff to a particular cell of a particular satellite based on the satellite handoff information.

Another aspect of the disclosure provides an apparatus configured for communication. The apparatus comprises means for receiving satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And means for performing a handoff to a particular cell of a particular satellite based on the satellite handoff information.

Another aspect of the disclosure includes receiving satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And non-transitory computer-readable media storing computer-executable code comprising code for performing handoffs to specific cells of a particular satellite based on satellite handoff information.

These and other aspects of the disclosure will be more fully understood upon review of the following detailed description. Other aspects, features, and implementations of the disclosure will become apparent to those skilled in the art upon review of the following description of specific embodiments of the disclosure in conjunction with the accompanying drawings. Although the features of the disclosure may be discussed with respect to certain implementations and drawings, all implementations of the disclosure may include one or more of the advantageous features discussed herein. In other words, one or more implementations may be discussed as having certain advantageous features, but one or more of these features may also be utilized in accordance with various implementations of the disclosure discussed herein. In a similar manner, it is to be understood that while some implementations may be discussed below as implementations of a device, system, or method, such implementations may be implemented in a variety of devices, systems, and methods.

The accompanying drawings are presented to aid in the description of the aspects of the disclosure and are provided solely for the purposes of illustration and not of limitation of the aspects.
1 is a block diagram of an example communication system, in accordance with some aspects of the disclosure.
2 is a block diagram of one example of a satellite network portal (SNP) of FIG. 1, in accordance with some aspects of the disclosure.
Figure 3 is a block diagram of one example of the satellite of Figure 1, in accordance with some aspects of the disclosure.
4 is a block diagram of one example of a user terminal of FIG. 1, in accordance with some aspects of the disclosure.
5 is a block diagram of one example of the user equipment of FIG. 1, in accordance with some aspects of the disclosure.
6 is a block diagram of an example communication system, in accordance with some aspects of the disclosure.
7 is a diagram illustrating an example of inter-satellite handoff signaling, in accordance with some aspects of the disclosure.
8 is a diagram illustrating another example of inter-satellite handoff signaling, in accordance with some aspects of the disclosure.
9 is a diagram illustrating an example of a feeder link, in accordance with some aspects of the disclosure.
10 is a diagram illustrating an example of a satellite pointing error, according to some aspects of the disclosure.
11 is a diagram illustrating an example of a call flow for a non-random access-based BxP handoff, in accordance with some aspects of the disclosure.
12 is a diagram illustrating an example of a call flow for a non-random access-based BxP handoff with user terminal (UT) measurements, according to some aspects of the disclosure.
13 is a diagram illustrating an example of a call flow for a random access-based BxP handoff, in accordance with some aspects of the disclosure.
Figures 14 and 15 are diagrams illustrating examples of call flows for random access-based BxP handoffs with UT measurements, in accordance with some aspects of the disclosure.
Figures 16, 17, and 18 are diagrams illustrating examples of call flows for AxP handoff, in accordance with some aspects of the disclosure.
19 is a diagram illustrating an example of a call flow for a radio link failure, in accordance with some aspects of the disclosure.
20 is a diagram illustrating an example of generating and using satellite and cell transition tables, in accordance with some aspects of the disclosure.
21 is a diagram illustrating an example of using satellite and cell transition tables, in accordance with some aspects of the disclosure.
22 is a diagram illustrating an example of signaling user terminal capabilities in accordance with some aspects of the disclosure.
23 is a diagram illustrating an example of using user terminal capabilities, in accordance with some aspects of the disclosure.
24 is a diagram illustrating an example of signaling user terminal location information, according to some aspects of the disclosure.
25 is a diagram illustrating an example of using user terminal location information, in accordance with some aspects of the disclosure.
26 is a diagram illustrating an example of user terminal handoff operations, in accordance with some aspects of the disclosure.
27 is a diagram illustrating an example of SNP handoff operations, in accordance with some aspects of the disclosure.
28 is a diagram illustrating another example of inter-satellite handoff signaling, in accordance with some aspects of the disclosure.
29 is a diagram illustrating an example of signaling ephemeris information according to some aspects of the disclosure.
30 is a diagram illustrating an example of radio link failure operations, in accordance with some aspects of the disclosure.
31 is a diagram illustrating an example of measurement gap-related operations, in accordance with some aspects of the disclosure.
32 is a diagram illustrating another example of measurement gap-related operations, in accordance with some aspects of the disclosure.
33 is a diagram illustrating an example of user queue-related operations, in accordance with some aspects of the disclosure.
34 is a diagram illustrating an example of random access-related operations, in accordance with some aspects of the disclosure.
35 is a block diagram illustrating an example hardware implementation for a device (e.g., an electronic device) capable of supporting satellite-related communications, in accordance with some aspects of the disclosure.
36 is a flow chart illustrating an example of a process involving the generation of satellite handoff information, in accordance with some aspects of the disclosure.
37 is a flow chart illustrating an example of a process involving generation of satellite and cell transition information, in accordance with some aspects of the disclosure.
38 is a block diagram illustrating an example hardware implementation for another device (e.g., an electronic device) capable of supporting satellite-related communications, in accordance with some aspects of the disclosure.
39 is a flow chart illustrating an example of a process involving a handoff, in accordance with some aspects of the disclosure.
40 is a flow chart illustrating an example of a process involving a handoff, in accordance with some aspects of the disclosure.

The disclosure relates, in some aspects, to a handoff of a user terminal communicating with a satellite network portal (also referred to as a gateway) through a satellite of a non-geostationary satellite communication system. In some embodiments, the satellite communication system is a low-earth orbit (LEO) satellite communication system for communicating data, voice, video, or other information. The satellite network portals and user terminals use satellite and cell transition tables to determine when to hand off the user terminal from one cell to another, and / or from one satellite to another. In some aspects, the user terminal may transmit capability information, location information, or other information to a satellite network portal, and thus, based on this information, the satellite network portal may generate satellite and cell transition tables, and / And selects a handoff procedure for the user terminal. The user terminal may also perform satellite signal measurements and may transmit corresponding measurement messages to the satellite network portal. The satellite network portal may then generate a new satellite and cell transition table as a result of receiving the measurement message. Various other aspects of the disclosure will also be described in further detail below.

Aspects of the disclosure are set forth in the following description of specific examples and the associated drawings. Alternative examples may be devised without departing from the scope of the disclosure. In addition, well-known elements will not be described or illustrated in detail in order not to obscure the relevant details of the disclosure.

FIG. 1 is a block diagram of a plurality of satellites (although only one satellite 300 is shown for clarity of illustration) at non-geostationary orbitals, e. G., Low-earth orbits LEO, (E.g., a satellite gateway), a plurality of user terminals (UTs) 400 and 401 in communication with satellites 300, and UTs 400 and 401, respectively, Which includes a plurality of user equipment (UE) (s) 500 and 501, Each UE 500 or 501 may be a user device such as a mobile device, a phone, a smartphone, a tablet, a laptop computer, a computer, a wearable device, a smart clock, an audiovisual device, Lt; / RTI > Additionally, UE 500 and / or UE 501 may be a device (e.g., access point, small cell, etc.) used to communicate with one or more end user devices. In the example illustrated in Figure 1, the UT 400 and the UE 500 communicate with each other via a bidirectional access link (with a forward access link and a return access link) UT 401 and UE 501 communicate with each other via another bi-directional access link. In yet another embodiment, one or more additional UEs (not shown) may only receive and therefore be configured to communicate with the UT using only the forward access link. In yet another embodiment, one or more additional UEs (not shown) may also communicate with the UT 400 or the UT 401. Alternatively, the UT and the corresponding UE may be integral parts of a single physical device, such as, for example, a mobile telephone with an antenna and an integrated satellite transceiver for direct communication with the satellite.

SNP 200 may access the Internet 108, or one or more other types of public, semi-private, or private networks. In the example illustrated in FIG. 1, the SNP 200 communicates with the Internet 108, or with the infrastructure 106, which can access one or more other types of public, semi-private, or private networks. SNP 200 may also be coupled to various types of communication backhaul including, for example, landline networks such as fiber optic networks or public switched telephone networks (PSTN) In addition, in alternative embodiments, the SNP 200 may be used by the Internet 108, PSTN 110, or one or more other types of public, semi-private, or private networks Lt; / RTI > Still further, the SNP 200 may communicate with other SNPs, such as the SNP 201, via the infrastructure 106, or alternatively may communicate with the SNP 201 without using the infrastructure 106. [ . The infrastructure 106 may include, in whole or in part, a network control center (NCC), a satellite control center (SCC), a wired and / or wireless core network, and / And / or any other components or systems utilized to enable communication with the satellite communication system 100. [

The communication between the satellite 300 and the SNP 200 in both directions is referred to as feeder links while the communication between the satellites 300 and the UTs 400 and 401 in the directions of both Are referred to as service links. The signal path from satellite 300 to a ground station, which may be one of SNP 200 or UTs 400 and 401, may be collectively referred to as downlink. The signal paths from the ground stations to the satellites 300 may collectively be referred to as uplinks. Additionally, as illustrated, the signals may have general directionality such as a forward link and a return link (or reverse link). Thus, the communication link in the direction originating from the SNP 200 and terminated at the UT 400 via the satellite 300 is referred to as the forward link, while the communication originating from the UT 400, The communication link in the direction terminated at the SNP 200 is referred to as a return link or a reverse link. 1, the signal path from the SNP 200 to the satellite 300 is denoted as " Forward Feeder Link " 112, while the signal path from the satellite 300 to the SNP 200 The signal path is denoted as " Return Feeder Link " 114. 1, the signal path from each UT (400 or 401) to the satellite 300 is denoted as a " Return Service Link " 116, while a signal path from each satellite (300) The signal path up to the UT 400 or 401 of " Forward Service Link "

The handoff controller 122 of the UT 401 and the handoff controller 124 of the SNP 200 may cooperate to control the handoff of the UT 401 from one satellite or cell to another. Other components of the satellite communication system 100 may also include corresponding handoff controllers. However, handoff controllers are only illustrated for UT 401 and SNP 200 to reduce the complexity of FIG.

Handoff controller 122 may send UT information 126 (e.g., including UT location and capabilities information) and measurement messages 128 (e.g., including satellite measurement information) to handoff controller 124 send. The satellite / cell transition information generation module 130 of the handoff controller 124 generates satellite / cell transition information (e.g., a table) indicating the handoff timing for the UT 401. In some aspects, the satellite / cell transition information generation module 130 may generate the UT information 126 and the measurement messages 128 received from the UT 401, the time (obtained from the ephemeris data) And may generate satellite / cell transition information based at least in part on satellite locations, satellite cell patterns, and satellite cell turn-on and turn-off schedules over time . The information transmission module 132 transmits the satellite / cell transition information to the handoff controller 122 through the current satellite 300.

The information receiving module 136 of the handoff controller 122 receives this satellite / cell transition information 134 via the current satellite 300. The satellite / cell handoff module 138 of the handoff controller 122 may then control the handoff of the UT 401 based on the received satellite / cell transition information.

2 is a block diagram of an example of a SNP 200 that may also be applied to the SNP 201 of FIG. SNP 200 includes a plurality of antennas 205, an RF subsystem 210, a digital subsystem 220, a public switched telephone network (PSTN) interface 230, a local area network (LAN) A SNP interface 240, a SNP interface 245, and a SNP controller 250. [ RF subsystem 210 is coupled to antennas 205 and digital subsystem 220. The digital subsystem 220 is coupled to the PSTN interface 230, the LAN interface 240, and the SNP interface 245. SNP controller 250 is coupled to RF subsystem 210, digital subsystem 220, PSTN interface 230, LAN interface 240, and SNP interface 245.

An RF subsystem 210, which may include multiple RF transceivers 212, an RF controller 214, and an antenna controller 216, transmits communication signals to the satellite 300 via a forward feeder link 301F And may receive communication signals from the satellite 300 via the return feeder link 301R. Although not shown for simplicity, each of the RF transceivers 212 may include a transmit chain and a receive chain. Each receive chain may include a low noise amplifier (LNA) and a down-converter (e.g., a mixer) for amplifying and downconverting received communication signals, respectively, in a well known manner. In addition, each receive chain may include an analog-to-digital converter (not shown) for converting received communication signals from the analog signals into digital signals (e.g., for processing by the digital subsystem 220) converter (ADC). Each transmit chain may include an up-converter (e.g., a mixer) and a power amplifier (PA) for up-converting and amplifying the communication signals to be transmitted to the satellite 300 in well known fashion . In addition, each transmit chain is coupled to a digital-to-analog converter (DAC) 220 for converting the digital signals received from the digital subsystem 220 into analog signals to be transmitted to the satellite 300. [ ).

The RF controller 214 may be utilized to control various aspects of the multiple RF transceivers 212 (e.g., carrier frequency selection, frequency and phase correction, gain settings, etc.). Antenna controller 216 may control various aspects of antennas 205 (e.g., beamforming, beam steering, gain settings, frequency tuning, etc.).

The digital subsystem 220 includes a plurality of digital receiver modules 222, a plurality of digital transmitter modules 224, a baseband (BB) processor 226, and a control (CTRL) processor 228 You may. The digital subsystem 220 may process the communication signals received from the RF subsystem 210 and forward the processed communication signals to the PSTN interface 230 and / 230 and / or LAN interface 240 and may forward the processed communication signals to the RF subsystem 210. [0033]

Each digital receiver module 222 may correspond to signal processing elements used to manage communication between the SNP 200 and the UT 400. One of the receive chains of the RF transceivers 212 may provide input signals to the plurality of digital receiver modules 222. A plurality of digital receiver modules 222 may be utilized to accommodate all of the possible satellite cells and possible diversity mode signals at any given time. Although not shown for simplicity, each digital receiver module 222 may include one or more digital data receivers, a searcher receiver, and diversity combiner and decoder circuitry. The searcher receiver may be used to search for appropriate diversity modes of carrier signals and may be used to search for pilot signals (or other relatively fixed pattern of strong signals).

Digital transmitter modules 224 may process signals to be transmitted to UT 400 via satellite 300. Although not shown for simplicity, each digital transmitter module 224 may include a transmit modulator that modulates data for transmission. The transmit power of each transmit modulator may be reduced by (1) applying a minimum level of power for purposes of interference reduction and resource allocation, and (2) May be controlled by a corresponding digital transmit power controller (not shown for the sake of simplicity) that may apply appropriate levels of power.

The control processor 228 coupled to the digital receiver modules 222, digital transmitter modules 224, and baseband processor 226 may be any of a variety of types of signal processing, timing signal generation, power control, handoff control, diversity synthesis, And to provide functions such as, but not limited to, system interfacing.

The control processor 228 may also control the generation and power, synchronization, and paging channel signals of the pilots and their coupling to a transmit power controller (not shown for simplicity). The pilot channel is a signal that is not modulated by data and may utilize a repetitive unaltered pattern or a non-varying frame structure type (pattern) or tone type input. For example, the orthogonal function used to form the channel for the pilot signal is generally a constant value such as all ones or zeros, or a well-known repetitive pattern such as a structured pattern of interspersed ones and zeros .

The baseband processor 226 is well known in the art and is therefore not specifically described herein. For example, the baseband processor 226 may include various known elements such as (but not limited to) coder's, data modems, and data data switching and storage components.

The PSTN interface 230 may either provide communication signals to the external PSTN or receive communication signals from an external PSTN, either directly or through an additional infrastructure 106, as illustrated in Figure 1 . The PSTN interface 230 is well known in the art and is therefore not described in detail herein. For other implementations, the PSTN interface 230 may be omitted or replaced by any other suitable interface that connects the SNP 200 to a terrestrial-based network (e.g., the Internet).

The LAN interface 240 may provide communication signals to an external LAN and may receive communication signals from an external LAN. For example, the LAN interface 240 may be coupled to the Internet 108 either directly or through an additional infrastructure 106, as illustrated in FIG. The LAN interface 240 is well known in the art and is therefore not described in detail herein.

The SNP interface 245 may provide communication signals to one or more other SNPs associated with the satellite communication system 100 of FIG. 1 and may receive communication signals from one or more other SNPs associated with the satellite communication system 100 of FIG. (And / or to / from SNPs associated with other satellite communication systems not shown for the sake of simplicity). For some implementations, the SNP interface 245 may communicate with other SNPs via one or more dedicated communication lines or channels (not shown for simplicity). For other implementations, the SNP interface 245 may communicate with other SNPs using other networks, such as the PSTN 110, and / or the Internet 108 (see also Fig. 1). For at least one implementation, the SNP interface 245 may communicate with other SNPs through the infrastructure 106.

The overall SNP control may be provided by the SNP controller 250. The SNP controller 250 may plan and control the use of the resources of the satellite 300 by the SNP 200. For example, the SNP controller 250 may analyze trends, generate traffic plans, allocate satellite resources, monitor (or track) satellite positions, / RTI > and / or the performance of the satellite (300). The SNP controller 250 also maintains and monitors the trajectories of the satellite 300 and relays the satellite usage information to the SNP 200 and tracks the locations of the satellites 300 and / May be coupled to a terrestrial-based satellite controller (not shown for simplicity) that adjusts various channel settings.

2, SNP controller 250 may provide local time or frequency information to RF subsystem 210, digital subsystem 220, and / or interfaces 230, 240, and / Frequency, and position references 251 that may be provided to the base stations 245, 245, The time or frequency information may be used to synchronize the various components of the SNP 200 with each other and / or with the satellite (s) Local time, frequency, and location references 251 may also provide location information (e.g., ephemeris data) of the satellite (s) 300 to various components of the SNP 200. 2, and for other implementations, the local time, frequency, and location references 251 may be stored in the SNP controller 250 (and / or the digital subsystem 220 and one or more of the RF subsystem 210).

Although not shown in FIG. 2 for simplicity, the SNP controller 250 may also be coupled to a network control center (NCC) and / or a satellite control center (SCC). For example, the SNP controller 250 may allow the SCC to communicate directly with the satellite (s) 300, for example, to retrieve ephemeris data from the satellite (s) 300 It is possible. SNP controller 250 may also be used by SNP controller 250 to schedule cell transmissions, coordinate handoffs, and perform various other well-known functions. (E.g., from the SCC and / or the NCC) that allows the antennas 205 to be aimed appropriately.

SNP controller 250 may include processing circuitry 232, memory device 234, or handoff controller 236 that independently or cooperatively performs handoff-related operations for SNP 200 as taught herein ). ≪ / RTI > In one example implementation, processing circuit 232 is configured (e.g., programmed) to perform some or all of these operations. In another example implementation, processing circuitry 232 (e.g., in the form of a processor) executes code stored in memory device 234 to perform some or all of these operations. In another example implementation, the handoff controller 236 is configured (e.g., programmed) to perform some or all of these operations. 2, one or more of the processing circuitry 232, the memory device 234, or the handoff controller 236 may be coupled to the SNP controller 250, as shown in FIG. 2 as being included in the SNP controller 250, (And / or to one or more of digital subsystem 220 and RF subsystem 210).

3 is a block diagram of an example of satellite 300 for illustrative purposes only. It will be appreciated that certain satellite configurations may vary considerably and may or may not include on-board processing. Also, while illustrated as a single satellite, two or more satellites utilizing inter-satellite communication may provide a functional connection between the SNP 200 and the UT 400. [ It is to be understood that the disclosure is not limited to any particular satellite configuration and that any satellite or combination of satellites capable of providing a functional connection between the SNP 200 and the UT 400 may be considered within the scope of the disclosure Will be recognized. In one example, satellite 300 includes a forward transponder 310, a return transponder 320, an oscillator 330, a controller 340, forward link antennas 351 and 352 (1) through 352 (N ), And return link antennas 362 and 361 (1) through 361 (N). The forward transponder 310, which may process communication signals within a corresponding channel or frequency band, is coupled to a respective one of the first bandpass filters 311 (1) through 311 (N), a first low noise amplifier (LNA) (1) through 314 (N) of the frequency converters 313 (1) through 313 (N), each one of the first LNAs 312 (1) ), One of each of the second band-pass filters 315 (1) through 315 (N), and one of the power amplifiers PA 316 (1) through 316 (N) Each of the PAs 316 (1) through 316 (N) may be coupled to an individual one of the antennas 352 (1) through 352 (N), as shown in FIG. do.

Within each of the respective forward paths FP (1) through FP (N), the first bandpass filter 311 is coupled to a signal having frequencies in the channels or frequency bands of the respective forward path (FP) Components, and filters signal components having frequencies outside the channel or frequency band of the respective forward path (FP). Thus, the passband of the first bandpass filter 311 corresponds to the width of the channel associated with the respective forward path (FP). The first LNA 312 amplifies the received communication signals to a suitable level for processing by the frequency converter 313. The frequency converter 313 converts the frequency of the communication signals in the respective forward path (FP) (e.g., to a frequency suitable for transmission from the satellite 300 to the UT 400). The second LNA 314 amplifies the frequency-converted communication signals and the second band-pass filter 315 filters signal components having frequencies outside the associated channel width. PA 316 amplifies the filtered signals to a suitable power level for transmission to UTs 400 via respective antenna 352. [ A return transponder 320 comprising a number N of return paths RP (1) through RP (N) follows the return service link 302R via antennas 361 (1) through 361 (N) Receives communication signals from the UT 400 and transmits communication signals to the SNP 200 along one or more of the antennas 362 along the return feeder link 301R. Each of return paths RP (1) through RP (N), which may process communication signals within a corresponding channel or frequency band, is coupled to a respective one of antennas 361 (1) through 361 And each one of the first LNAs 322 (1) through 322 (N), one of the bandpass filters 321 (1) through 321 (N), the frequency converters 323 (1) to 323 (N)), and each of the second LNAs 324 (1) to 324 (N) ). ≪ / RTI >

Within each of the individual return paths RP (1) to RP (N), the first bandpass filter 321 is coupled to a signal (e.g., a signal having a frequency within a channel or frequency band of an individual return path Components, and filters signal components having frequencies outside the channel or frequency band of the respective return path (RP). Accordingly, the passband of the first bandpass filter 321 may correspond to the width of the channel associated with the respective return path RP, for some implementations. The first LNA 322 amplifies all received communication signals to an appropriate level for processing by the frequency converter 323. The frequency converter 323 converts the frequency of the communication signals on the respective return paths RP (e.g., to a frequency suitable for transmission from the satellite 300 to the SNP 200). The second LNA 324 amplifies the frequency-converted communication signals and the second band-pass filter 325 filters signal components having frequencies outside the associated channel width. The signals from return paths RP (1) through RP (N) are combined and provided to one or more antennas 362 via PA 326. The PA 326 amplifies the synthesized signals for transmission to the SNP 200.

The oscillator 330, which may be any suitable circuit or device that generates an oscillating signal, converts the forward local oscillator signal LO (F) to frequency converters 313 (1) through 313 (N) of the forward transponder 310, And provides a return local oscillator signal LO (R) to the frequency converters 323 (1) through 323 (N) of the return transponder 320. For example, the LO (F) signal is used to transmit communication signals from a frequency band associated with the transmission of signals from SNP 200 to satellite 300, a frequency band associated with transmission of signals from satellite 300 to UT 400, May be used by the frequency converters 313 (1) to 313 (N) to convert them to the frequency converters 313 (1) to 313 (N). The LO (R) signal is used to convert communication signals from the frequency band associated with the transmission of signals from the UT 400 to the satellite 300, to the frequency band associated with the transmission of signals from the satellite 300 to the SNP 200 , And frequency converters 323 (1) through 323 (N).

The controller 340 coupled to the forward transponder 310, the return transponder 320 and the oscillator 330 controls various operations of the satellite 300 including but not limited to channel assignments It is possible. In one aspect, the controller 340 may include a memory (not shown) coupled to a processing circuit (e.g., a processor). The memory may be a non-transitory computer-readable medium (e.g., non-volatile memory) that when executed by the processing circuit stores instructions that cause the satellite 300 to perform operations including, but not limited to, those described herein One or more non-volatile memory elements such as, for example, EPROM, EEPROM, flash memory, hard drive, etc.).

An example of a transceiver for use in UT 400 or UT 401 is illustrated in FIG. In Figure 4, at least one antenna 410 is provided for receiving forward link communication signals (e.g., from satellite 300) that are communicated to analog receiver 414, where they are down- And digitized. The duplexer element 412 is often used to allow the same antenna to serve both transmit and receive functions. Alternatively, the UT transceiver may employ separate antennas to operate at different transmit and receive frequencies.

The digital communication signals output by analog receiver 414 are passed to at least one digital data receiver 416A and at least one searcher receiver 418. [ Additional digital data receivers (e. G., As represented by digital data receiver 416N) may be implemented at a desired level of signal diversity, depending on the acceptable level of transceiver complexity, as will be apparent to those skilled in the relevant art / RTI >

At least one user terminal control processor 420 is coupled to the digital data receivers 416A-416N and the searcher receiver 418. [ The control processor 420 provides, among other functions, basic signal processing, timing, power, and handoff control or adjustment, and selection of frequencies used for signal carriers. Another basic control function that may be performed by control processor 420 is the selection or manipulation of functions that should be used to process various signal waveforms. Signal processing by the control processor 420 may include determining a relative signal strength, and computing various related signal parameters. These operations of signal parameters, such as timing and frequency, may include increased efficiency or speed in measurements, or the use of additional or separate dedicated circuitry to provide improved allocation of control processing resources.

The outputs of the digital data receivers 416A through 416N are coupled to the digital baseband circuitry 422 in the UT 400. [ Digital baseband circuitry 422 includes processing and presentation elements that are used to convey information, for example, to UE 500 as shown in FIG. 1 and from UE 500. Referring to FIG. 4, when diversity signal processing is employed, the digital baseband circuitry 422 may include a diversity combiner and a decoder (not shown). Some of these elements may also be operable under control of the control processor 420, or in communication with the control processor 420.

When voice or other data is prepared as an output message or communication signal originating from the UT 400, the digital baseband circuitry 422 receives, stores, and processes the desired data for transmission, and if not Is used to prepare for. The digital baseband circuitry 422 provides this data to a transmit modulator 426 that operates under the control of the control processor 420. The output of the transmit modulator 426 is coupled to a power controller 428 that provides output power control to the transmit power amplifier 430 for ultimate transmission of the output signal from the antenna 410 (e.g., the satellite 300) ).

In FIG. 4, the UT transceiver also includes a memory 432 associated with the control processor 420. The memory 432 may include data for processing by the control processor 420 as well as instructions for execution by the control processor 420. [ 4, the memory 432 includes instructions for performing time or frequency adjustments to be applied to the RF signal to be transmitted by the UT 400 over the return service link to the satellite 300 You may.

4, the UT 400 may also send local time, frequency, and / or location information for the UT 400 to the control processor (e. G. Frequency, and / or location references 434 (e.g., a GPS receiver) that may be provided to the base stations 420, 420,

The digital data receivers 416A through 416N and the searcher receiver 418 comprise signal correlation elements for demodulating and tracking specific signals. The searcher receiver 418 is used to search for pilot signals, or other relatively fixed patterns of strong signals, while the digital data receivers 416A-416N demodulate other signals associated with the detected pilot signals . However, the digital data receiver 416 may be assigned to track the pilot signal after acquisition to accurately determine the ratio of signal chip energies to signal noise and formulate the pilot signal strength. Therefore, the outputs of these units can be monitored to determine the energy in the pilot signal or other signals, or the frequency of the pilot signal or other signals. These receivers also employ frequency tracking elements that can be monitored to provide current frequency and timing information to the control processor 420 for the signals being demodulated.

Control processor 420 may use this information to determine to what extent the received signals are offset from the oscillator frequency when scaled as appropriate to the same frequency band. These and other information related to frequency errors and frequency shifts may be stored in a storage device or memory element (e.g., memory 432) as desired.

The control processor 420 may also be coupled to the UE interface circuitry 450 to allow communications between the UT 400 and one or more UEs. The UE interface circuitry 450 may be configured as desired for communication with the various UE configurations and may thus be implemented by various transceivers and associated components in accordance with various communication technologies employed to communicate with the various UEs supported . For example, UE interface circuitry 450 may include one or more antennas, a wide area network (WAN) transceiver, a wireless local area network (WLAN) transceiver, a local area network (PSTN) interface, and / or other known communication techniques configured to communicate with one or more UEs in communication with the UT 400. [

Control processor 420 may be coupled to processing circuitry 442, memory device 444, or handoff controller 446, which independently or cooperatively performs handoff-related operations for UT 400 as taught herein. ). ≪ / RTI > In one example implementation, processing circuit 442 is configured (e.g., programmed) to perform some or all of these operations. In another example implementation, processing circuit 442 (e.g., in the form of a processor) executes code stored in memory device 444 to perform some or all of these operations. In another example implementation, the handoff controller 446 is configured (e.g., programmed) to perform some or all of these operations. 4, but for other implementations, one or more of the processing circuitry 442, the memory device 444, or the handoff controller 446 may be implemented within the control processor 420 Lt; RTI ID = 0.0 > a < / RTI >

5 is a block diagram illustrating an example of a UE 500 that may also be applied to the UE 501 of FIG. The UE 500 as shown in FIG. 5 may be, for example, a mobile device, a handheld computer, a tablet, a wearable device, a smart clock, or any type of device capable of interacting with a user. In addition, the UE 500 may be a network-side device that provides connectivity to various ultimate end user devices and / or various public or private networks. 5, the UE 500 includes a LAN interface 502, one or more antennas 504, a wide area network (WAN) transceiver 506, a wireless local area network (WLAN) transceiver 508, and And a satellite positioning system (SPS) receiver 510. The SPS receiver 510 may be compatible with a Global Positioning System (GPS), a Global Navigation Satellite System (GLONASS), and / or any other global or local satellite based positioning system . In an alternative embodiment, UE 500 includes a WLAN transceiver 508, such as a Wi-Fi transceiver, with or without LAN interface 502, WAN transceiver 506, and / or SPS receiver 510 ). UE 500 also includes Bluetooth, ZigBee, and / or Bluetooth devices with or without LAN interface 502, WAN transceiver 506, WLAN transceiver 508, and / And may include additional transceivers such as other known technologies. Thus, the elements illustrated for UE 500 are provided as an example configuration only, and are not intended to limit the configuration of UEs according to various aspects disclosed herein.

5, the processor 512 is connected to a LAN interface 502, a WAN transceiver 506, a WLAN transceiver 508, and an SPS receiver 510. In the example shown in FIG. Optionally, the motion sensor 514 and other sensors may also be coupled to the processor 512.

The memory 516 is connected to the processor 512. In one aspect, memory 516 may include data 518 that may be transmitted to UT 400 and / or received from UT 400, as shown in FIG. 5, memory 516 may also include stored instructions 520 to be executed by processor 512 to perform process steps for communicating with, for example, UT 400, have. The UE 500 may also include a user interface that may include hardware and software for interfacing the inputs or outputs of the processor 512 with the user via, for example, light, sound, or tactile inputs or outputs (522). 5, the UE 500 includes a microphone / speaker 524, a keypad 526, and a display 528 connected to the user interface 522. The microphone / speaker 524, Alternatively, the user's tactile input or output may be integrated with the display 528, for example, by using a touch-screen display. Once again, the elements illustrated in FIG. 5 are not intended to limit the configurations of the UEs disclosed herein, and that the elements contained within the UE 500 will vary based on the device's end-use and system engineer's design choices Will be recognized.

In addition, the UE 500 may be a user device, such as a mobile device or an external network side device, which is in communication with the UT 400, but is separate from the UT 400, for example, as illustrated in FIG. Alternatively, UE 500 and UT 400 may be integral parts of a single physical device.

In the example shown in FIG. 1, two UTs 400 and 401 may perform bi-directional communication with satellite 300 over return and forward service links within cell coverage. The satellite may communicate with more than two UTs within the cell coverage. The return service link from the UTs 400 and 401 to the satellite 300 may thus be a many-to-one channel. For example, some of the UTs may be mobile, while others may be static. In a satellite communication system such as the example illustrated in FIG. 1, multiple UTs 400 and 401 in cell coverage may be time-division-multiplexed (TDM) or frequency-division- frequency-division-multiplex (FDM), or both.

UT handoff

At some point in time, the UT may need to be handed off to another satellite (not shown in FIG. 1). The handoff may be caused by scheduled events or non-scheduled events.

Some examples of handoffs due to scheduled events follow. Inter-cell and inter-satellite handoffs may be caused by movement of satellites, movement of UTs, or turning off of satellite cells (e.g. due to geo-stationary satellite (GEO) confinement) . The handoff may also be due to the satellite moving outside the range of the SNP while the satellite is still in the line of sight of the UT.

Some examples of handoffs due to unscheduled events follow. The handoff may be triggered by the satellite being blocked by an obstacle (e.g., a tree). The handoff may also be triggered due to a drop in channel quality (e.g., signal quality) due to rain fades or other atmospheric conditions.

In some implementations, at a particular point in time, a particular satellite may be controlled by a particular entity (e.g., a network access controller, NAC) at the SNP. Accordingly, the SNP may have several NACs (e.g., implemented by the SNP controller 250 of FIG. 2), each of which controls a corresponding one of the satellites controlled by the SNP. In addition, a given satellite may support multiple cells. Hence, different types of handoffs may occur over time.

In an inter-cell handoff, the UT is handed off from one cell of the satellite to another cell of the satellite. For example, a particular cell serving an intelligent UT may change over time as the serving satellite moves.

In an inter-satellite handoff, the UT is handed off from the current serving satellite (referred to as the source satellite) to another satellite (referred to as the target satellite). For example, the UT may be handed off to the target satellite as the source satellite moves away from the UT and the target satellite moves towards the UT.

6, various aspects of the disclosure relate to handoff of a user terminal (UT) 602 in communication with a satellite network portal (SNP) 604 via a satellite 606 in a satellite communication system 600 . In some implementations, the system 600 may be a non-geostationary satellite communication system, such as a low-earth orbit (LEO) satellite communication system for data, voice, video, or other communication. UT 602 is an example of UT 400 or UT 501 in Fig. SNP 604 is an example of SNP 200 or SNP 201 in FIG. The satellite 606 is an example of the satellite 300 of FIG.

In some aspects, the SNP 604 and the UT 602 may communicate with the satellite 602 to determine when to hand off the UT 602 from one cell to another and / or from one satellite to another. Transition information 608 is used. For example, the UT 602 may transmit the UT information 610 (e.g., capability information, location information, or other information) to the SNP 604 via the first signaling 612. Based on the information 610, the SNP 604 or some other entity generates satellite and cell transition information 608 and transmits the information 608 to the UT 602 via the second signaling 614. [ Alternatively or additionally, the SNP 604, or some other entity, selects a handoff procedure for the UT 602 based on the information 610. In some aspects, the handoff of the UT 602 to a different satellite (new serving satellite) involves the UT 602 making satellite signal measurements and sending the measurement message 616 to the SNP 604 . In some aspects, the SNP 604 generates new satellite and cell transition information (e.g., modifies the satellite and cell transition tables) as a result of receiving the measurement message 616.

The UT 602 may perform other handoff-related operations in accordance with the teachings herein. In some aspects, the UT 602 may receive satellite ephemeris information via the SNP 604 and may use satellite ephemeris information to synchronize to a satellite (e.g., satellite 606). In some aspects, the UT 602 invokes a radio link failure mode if the UT 602 loses connectivity to the satellite and / or cell.

In some aspects, the handoff design may attempt to meet one or more design goals. An example of this purpose is to minimize signaling during handoffs; Minimizing data disruption during handoffs; Or reducing the dependence of the satellite ephemeris data on the knowledge of the UT (e.g., instead of relying on knowledge of the SNP of the satellite location and the UT location).

In the example of FIG. 6, the SNP 604 includes network access controllers (NACs) 618, each of which is connected to the UT 602 via a satellite 606 (or some other satellite, not shown) And interfaces with one or more radio frequency (RF) subsystems 620 for communicating with UTs (not shown). The SNP 604 also includes a core network control plane (CNCP) 622 and a core network user plane (CNUP) 624 for communicating with the network 626, Functionality (e. G., Control and user plane functionality for other types of networks). The network 626 may represent one or more of, for example, a core network (e.g., 3G, 4G, 5G, etc.), an intranet, or the Internet.

In some implementations, the SNP 604 determines (e.g., receives or generates) satellite and cell transition information 608. For example, the NAC 618 may communicate with the NAC 618 based on information received over the network 626 (e.g., e-mail information) and information received from the UTs (e.g., configuration information and measurement messages) Lt; RTI ID = 0.0 > UT < / RTI > As another example, the NAC 618 may receive satellite and cell transition information for its UTs over the network 626 (e.g., from the network entity 628).

Other entities in the system may similarly generate satellite and cell transition information 608. In some implementations, the controller 630 of the network entity 628 may generate satellite and cell transition information 608 and may generate satellite and cell transitions (e.g., during system start-up and / or other times) Information 608 may be transmitted to the control components of system 600. For example, the network entity 628 may transmit satellite and cell transition information 608 to the SNP 604 via a network 626 (e.g., a core network, an intranet, or the Internet) or some other data delivery mechanism have. For purposes of illustration, network entity 628 is shown as being external to network 626. However, the network entity 628 may be part of the network 626.

Some examples of UTs, SNPs, or satellites that may be used in conjunction with UT handoffs in accordance with the teachings herein will now be described. These aspects include, for a given one of these satellite system components: parameters or other information used by the components, parameters assigned to the components, characteristics (e.g., capabilities) of the components, signaling used by the components, ≪ / RTI >

Satellite ID

The satellite identifier (ID) is a unique ID of a particular satellite in the satellite system. The satellite ID allows the satellite to be uniquely identified in the satellite system (e.g., by the UT). In order to allow for large satellite deployment, the satellite ID may be more than 16 bits. In some implementations, the satellite ID is transmitted on the overhead channel and is not required to be read immediately by the UT. The UT and the SNP may index the ephemeris information table and use the satellite ID to locate the projections of the satellite and satellite cells on earth at a given time.

Cell or beam ID

The cell ID is a unique ID for the cell. Similarly, the beam ID is a unique ID for the beam. For convenience, the term cell / beam may be used herein to indicate a cell and / or a beam. The cell / beam ID allows a cell / beam from a given satellite to be uniquely identified (e.g., by a UT). In some aspects, the cell / beam ID may be detectable by the UT in a very short period of time (e.g., the cell / beam ID may be a continuous signature used on the cell / beam's pilot. In one non-limiting example, the cell / beam ID may comprise 10 bits: 2 bits (e.g., 2 bits) for the SNP ID For example, the two bits may be sufficient to have a unique SNP visible by the UT; four values for the SNP ID may be reused across the globe) and 8 for the cell / beam commanded by the SNP (E.g., the SNP controls approximately 10 satellites x 16 beams / satellite = 160 beams / SNP => 8 bits to uniquely identify the cells / beams). A different number of bits may be used in other implementations ≪ / RTI > In addition, the spatial diversity of satellites can be considered to reduce the number of bits.

UT capabilities

The UT may exchange its capabilities with the SNP at connection time or some other time. Some non-limiting examples of UT capabilities follow.

The UT may be dual cell / beam detectable. Accordingly, one UT capability parameter (e.g., taking the value of YES or NO) may indicate whether the UT can detect more than one cell / beam. For example, this capability parameter may be used to determine if the UT can detect and detect the cell / beam ID of another cell / beam of the same satellite while the UT is actively communicating using the cell / Or not. In some implementations, this capability parameter may be used to indicate whether the UT can support two cells / beams simultaneously. A different number of cells / beams (e.g., three or more) may be supported in other implementations.

The UT may be dual satellite capable. Accordingly, another UT capability parameter (e.g., taking a value of YES or NO) may indicate whether the UT can detect more than one satellite. For example, this capability parameter may indicate whether or not the UT can detect and detect the cell / beam ID of another satellite while the UT is actively communicating using the cell / beam of the particular satellite have. In some implementations, this capability parameter may be used to indicate whether or not the UT can support two satellites at the same time. Different numbers of satellites (e.g., three or more) may be supported in other implementations.

As discussed in more detail below, the SNP may utilize the detection capabilities of the UT to determine what type of handoff to use for the UT. For example, if the UT can only support a single cell / beam at a time, then the handoff can be based simply on the satellite and cell transition tables. Conversely, if the UT can support multiple cells / beams / satellites at one time, the SNP can monitor for measurement messages from the UT during the handoff, When and / or where) are handed off.

Another UT capability parameter may indicate an inter-cell tune time and / or an inter-beam tune time (e.g., in microseconds (μsec)) for the UT. For convenience, the term inter-cell / beam tune time may be used to refer to inter-cell tune time and / or inter-beam tune time. This UT capability parameter may indicate the time period that it takes for the UT to stop listening to the cell / beam and start listening to another cell / beam of the same satellite. Thus, in some aspects, the inter-cell / beam-tune time indicates how long it takes for the UT to tune from one cell / beam to another cell / beam.

Another UT capability parameter may indicate the inter-satellite tune time for the UT (e.g., in microseconds (μsec). This UT capability parameter may indicate the time period that it takes for the UT to stop listening to the cell / beam on the current satellite and begin listening to another satellite's cell / beam. Thus, in some aspects, the inter-satellite tune time indicates how long it takes for the UT to tune from one satellite to another.

In some implementations, the tune time may be given as an upper limit. For example, the tune time may indicate the maximum amount of time that the UT is expected to take to tune from one cell / beam or satellite to another.

In some implementations, the tune time may be described according to a formula. A non-limiting example of such a formula is: a + b *? Where a is a constant indicating the minimum time period for inter-satellite tuning,? Is the degree between the current satellite and the target satellite ) Is the angular distance, and b is the moving speed of the antenna of the UT, which is the degree of travel per millisecond.

Tune- Away  Definitions

Signaling may be employed to allow the UT to tune-away for inter-satellite and inter-cell / beam sensing. This signaling can be used to define tune-away periods for the UT to sense other cells / beams of the same satellite or other satellites.

UT Location

The UT location reporting mechanism is employed for handoff processing and paging such that the SNP knows the location of the UT (e.g., on a continuous or regular basis). In some implementations, the UT will have a reliable global positioning system (GPS) positioning.

For well-known UTs, the UT location reporting mechanism may involve the UT transmitting a signaling message to the SNP reporting the UT's location (e.g., GPS coordinates).

For mobile UTs (e.g., UTs on board or airplanes), the UT location reporting mechanism may involve the UT sending a signaling message to the SNP reporting the UT's speed and direction. This allows the SNP to continuously estimate the location of the UT. Even for mobile UTs, the direction and speed information may be relatively stable when the UTs are carried (e.g., attached to) by relatively large vessels.

In addition, through location-related signaling, the UT may be notified of the allowed location drift before the new location update message is needed.

Some implementations may employ thresholds for location tolerances. Some implementations may employ GEO fencing. For example, the UT may be configured to transmit location updates to the SNP if the UT exceeds a specified boundary for satellite and / or SNP (e.g., the UT is some distance away).

Efemeris  Forwarding and update Signaling

These messages may be used to deliver satellite ephemeris data to the UTs. In some aspects, the ephemeris data includes a geographic description of where a given satellite is at a given point in time. This data may be used by the UT when it searches for the next satellite and the cell / beam (e.g., after the UT detects radio link failure). For example, in some aspects, the UT may utilize efferent data for a given satellite to determine where to direct the antennas (antennas) of the UT at a given point in time. In some aspects, the SNP may send a signaling message including satellite ephemeris data to all connected UTs (e.g., whenever there is an update). In some aspects, the UT may request satellite ephemeris data from the SNP (e.g., when the UT establishes a connection).

Satellite and cell transition tables

Each satellite beam may be viewed as a separate cell with its own data and control channels, and signals. The SNP or some other entity may generate a satellite and cell transition table that provides a list of satellites that the UT may elect to next hand off. The transition table may also accurately describe at what time the UT will switch from one cell to another (e.g., corresponding to the beam and / or RF band) of the next satellite. The transition table may indicate, for a number of satellites, the cells (e.g., beams and / or bands) to be used for each satellite. The transition table may also indicate the frequency of the cell (e.g., radio frequency or frequency band of a pastor) for each cell (e.g., beam). The transition table may also display the cell ID of each cell (or the beam ID of each beam).

SNPs may define satellite and cell transition tables based on various information. In some aspects, the SNP may define a table using the location of the UT (and, if specified, the speed and direction). In some aspects, the SNP may define a table using satellite locations over time calculated from ephemeris data. In some aspects, the SNP may define a table based on information about which cells / beams and / or satellites are turned off at which times.

Table 1 below is an example of the satellite and cell transition tables. The entries for this table include satellite IDs, beam IDs, beam frequencies Freq, start times, and end times. This table may also be referred to as satellite and beam transition tables. TA _beam represents a tune-away from one _beam of the same satellite to another. In this example, the UT is for tuning to satellite 1, beam 1 from time a ₁ to time b ₁ (on frequency F ₁₁ ). The UT is then for tuning to satellite 1, beam 2 from time b ₁ + TA _beam to time c ₁ (on frequency F ₂₁ ), and so on.

In some implementations, the table may be transmitted in a signaling message to the UT it is serving by the SNP at any time before the UT is handed off to the next satellite.

In one example, the overhead of the satellite and cell transition table messages (assuming there are two satellites listed in the table) are: satellite ID = 16 bits; Beam ID = 10 bits; (Assuming 16 beam frequencies per satellite) frequency = 4 bits; And start and end times = 15 bits.

The start time and end time may be specified in terms of frame numbers. The physical layer may specify the use of 10 millisecond (ms) transmission frames for the system. Assuming that a satellite handoff occurs every 3 minutes, the number of frames that can be transmitted between handoffs is 18,000. The frame numbers may be reinitialized from zero after every handoff. Next, the number of bits required to specify the frame number is accordingly 15 bits in this example.

In this example, the total overhead of the message would be (approximately) 1020 bits = 128 bytes. the values of a ₁ , b ₁ , ..., n ₁ , and TA _beam will be specified.

If the maximum of 1000 active users can be served at one time by one beam and the beam overhead downlink (DL) throughput is approximately 300 Mbps, then the overhead is: (approximately) overhead = (128 bytes x numUsersBeam) / (total bytes delivered by the beam in 3 minutes) = (128 bytes x 1000) / (300 x 10 ⁶ x 3 x 60) = 19 x 10 ^-6 .

Table 2 below is another example of the satellite and cell transition tables. The SatelliteID is the unique ID assigned to the satellite by the system. The forward link (FL) band is a positive integer index that identifies the transmission frequency band of the FL. The return link (RL) band is a positive integer index that identifies the transmission frequency band of the RL.

The handoff activation time specifies the time when the UT should stop transmitting and receiving. In some implementations, this time is specified in the source cell in units of system frame numbers (SFNs). SFNs may be, for example, sequence numbers assigned to 10 ms physical layer transmitted radio frames. The UT stops sending and receiving at the beginning of the SFN. For example, if the handoff activation time is specified as being in SFN 5, the UT stops sending or receiving in sub-frame 0 of SFN 5.

The UT begins to transmit or receive in the target cell in the handoff activation time plus tune-away time. Two examples of UT parameters related to the tune-away time are the inter-cell tune-away time and the inter-satellite tune-away time. These parameters may be included in the UT capability information.

Inter - satellite handoff

Figures 7 and 8 illustrate examples of inter-satellite handoffs. In these examples, the SNP includes a source NAC controlling the first satellite and a target NAC controlling the second satellite. In each case, the UT is initially connected to the source satellite (and hence the source NAC) and then handed off to the target satellite (and hence the target NAC). Different numbers of NACs and satellites may be supported in different implementations. Also, in some implementations, a common (e.g., the same) entity may support multiple satellites.

7 is an example in which the UT 702 does not transmit a measurement message. For example, UT 702 may not support sensing of multiple cells / beams and / or satellites, or UT 702 may determine that a measurement message does not need to be transmitted to SNP 704. In this case, the UT 702 and the SNP 704 are used to determine when to transition to the next cell / beam and / or satellite and where to transit (e.g., which cell / beam, which frequency, which satellite) It relies on existing satellite and cell transition tables. The UT 702 is an example of the UT 400 or the UT 501 in Fig. SNP 704 is an example of SNP 200 or SNP 201 in FIG.

The source NAC 706 sends control signaling 708 to the UT 702. The control signaling 708 may include, for example, measurement information and tune-away control information (e.g., tune-away definitions). In addition, packet data 710 is exchanged between UT 702 and source NAC 706. Source NAC 706 is an example of NAC 612 in FIG.

At some point in time, a handoff is triggered (712). For example, the current time may correspond to the time for a transition from one satellite to the next indicated by the satellite and cell transition tables.

Other handoff triggers may be employed as well. For example, SNP 704 (e.g., source NAC 706) may autonomously determine that UT 702 needs to be handed off. Such triggers may include, for example: the current serving satellite is moving outside the range of UT 702; That the satellite is moving outside the range of SNP 704, even though the satellite may be within range of UT 702; Or the cell / beam serving UT 702 will be black-out due to GEO requirements.

If the UT 702 is able to sense another cell / beam and / or satellite while it is connected to the first satellite, the UT 702 may also search the signal strength of the default satellite and cell / beam for handoff have. UT 702 may be assumed to have location information of this satellite for doing so. This location information may be obtained from the satellite emegas data owned by the UT 702. [ If the signal strength is satisfactory, the UT 702 does nothing and waits for the source NAC 706 to begin the inter-satellite handoff process.

Accordingly, in the example of FIG. 7, both the UT 702 and the source NAC 706 will follow the table and begin handoff to the new serving satellite. For this purpose, the source NAC 706 will perform handoff processing 714. For example, the source NAC 706 may communicate with the target NAC 716 to initiate a handoff. In some aspects, this may involve synchronizing queues 718 (e.g., packet traffic queues) between NACs 706 and 716. Further, since the time of the handoff is known in advance, the user queues can be delivered in advance. Target NAC 716 is an example of NAC 612 in FIG.

The source NAC 706 then sends a handoff signaling 720 to the UT 702. [ In some aspects, the handoff signaling 720 may include information that enables the UT 702 to communicate with the target NAC 716. In some aspects, the handoff signaling 720 may include a new satellite and cell transition table (e.g., that the source NAC 706 has received from the target NAC 716).

Next, the UT 702 is separated 722 from the first satellite and synchronizes to the second satellite. For this purpose, the UT 702 may send a synchronization signaling 724 for the second satellite to the target NAC 716. In some aspects, this may involve the UT 702 performing a random access procedure at the second satellite.

The UT 702 and the target NAC 716 may then exchange connection signaling 726 and 728. [ In some aspects, this may involve sending the target NAC 716 to the UT 702 and requesting a channel quality indicator from the UT 702. In some aspects, UT 702 may use ephemeris information to synchronize with the second satellite.

In addition, various entities may perform various background operations to ensure that packet forwarding is properly performed and any necessary clean-up (e.g., cache clean-up) is performed.

Fig. 8 is an example in which the UT 802 transmits a measurement message. For example, the UT 802 may transmit a measurement message to the SNP 804 because the measured channel conditions (e.g., signal strength) from the serving satellite or the target satellite are unacceptable (e.g., signal strength is too low) You may decide that you need it. In this case, the SNP 804 may generate a new satellite and cell transition table based on the measurement message. Next, UT 802 and SNP 804 determine when to transition to the next cell / beam and / or satellite and where to transit (e.g., which cell / beam, which frequency, which satellite) We will use the new satellite and cell transition tables. UT 802 is an example of UT 400 or UT 501 in Fig. SNP 804 is an example of SNP 200 or SNP 201 in FIG.

As in FIG. 7, the source NAC 806 sends control signaling 808 to the UT 802. The control signaling 808 may include, for example, measurement information and tune-away control information (e.g., tune-away definitions). In addition, packet data 810 is exchanged between UT 802 and source NAC 806. Source NAC 806 is an example of NAC 612 in FIG.

At some point in time, a handoff is triggered (812). In some cases, the current time corresponding to the time from one satellite to the next, as indicated by the satellite and cell transition table, constitutes a handoff trigger. In some cases, the measurement message sent by the UT 802 indicating that the neighboring satellite is substantially stronger (e.g., associated with a stronger received signal strength) than the current serving satellite may result in a handoff trigger .

Other handoff triggers may be employed as well. For example, SNP 804 (e.g., source NAC 806) may autonomously determine that UT 802 needs to be handed off. Such triggers may include, for example: the current serving satellite is moving outside the range of UT 802; That the satellite is moving outside the range of SNP 804, even though the satellite may be within range of UT 802; Or the cell / beam serving UT 802 will be blacked out due to GEO requirements.

In the example of FIG. 8, the UT 802 may sense another cell / beam and / or satellite while connected to the first satellite. Accordingly, the UT 802 may perform channel quality measurements (e.g., satellite signal strength measurements). For example, the UT 802 may measure the signal strength from the current serving satellite (first satellite) and the target satellite (second satellite) (814).

Next, the UT 802 performs measurement processing 816 to determine, for example, which channel quality is inadequate (e.g., signal strength is too low). If any one of the channel qualities is improper, the UT 802 may choose to send the measurement message 818 to the source NAC 806. This measurement message 818 may include, for example, the results of measurements (e.g., signal strength in dB), an indication that the handoff time needs to be advanced (e.g., because the signal from the source satellite is currently too low) An indication that the handoff time needs to be delayed (e.g., because the signal from the target satellite is currently too low), or some other indication.

Accordingly, similar to FIG. 7, the UT 802 may search for the default satellite for handoff and the cell / beam signal strength. Again, UT 802 may be assumed to have location information for this satellite to do so (e.g., obtained from satellite eFemales data owned by UT 802). If the signal strength is not satisfactory, the UT 802 may send a measurement message 818 to the source NAC 806 indicating that the satellite is different from the default, in order to trigger or delay the handoff process prematurely.

The source NAC 806 then transmits the UT 802 to the target satellite and the target NAC 806 based on the satellite and cell transition table and any measurement message 818 that the source NAC 806 receives from the UT 802. [ (820). Thus, as indicated in FIG. 8, the source NAC 806 will perform some handoff processing 822. For example, the source NAC 806 may determine, based on the measurement message 818, whether the handoff time is to be advanced (early handoff) or delayed (late handoff), or whether some other satellite Or not. In addition, the source NAC 806 may communicate with the target NAC 820 to initiate a handoff. In some aspects, this may involve synchronizing the queues 824 (e.g., packet traffic queues) between the NACs 806 and 820. The target NAC 820 is an example of the NAC 612 in FIG.

Next, the source NAC 806 sends a handoff signaling 826 to the UT 802. In some aspects, the handoff signaling 826 may include information that enables the UT 802 to communicate with the target NAC 820. [ In some aspects, the handoff signaling 826 may include a new satellite and cell transition table (e.g., that the source NAC 806 has received from the target NAC 820).

The UT 802 is then detached (828) from the first satellite and synchronized to the second satellite. For this purpose, the UT 802 may send a synchronization signaling 830 for the second satellite to the target NAC 820.

Next, the UT 802 and the target NAC 820 may exchange connection signaling 832 and 834. In some aspects, this may involve the target NAC 820 sending the e-mail information to the UT 802 and requesting the channel quality indicator from the UT 802. [ Again, the various entities may perform various background operations to ensure that packet forwarding is performed appropriately and any necessary clean-up (e.g., cache clean-up) is performed.

With normal inter-satellite handoff, hybrid automatic repeat request (HARQ) processes may be terminated. However, the source NAC may know exactly when the handoff will occur, and therefore the source NAC can ensure that the forward link data buffers are emptied. Also, the gap for the data flow can be minimized since the time of the handoff is known.

Inter - beam handoff

The inter-cell / beam handoff is performed synchronously by the SNP and the UT according to the timeline specified in the satellite and cell transition tables. Using tune-away cycles or dual receive capability, the UT detects the presence of the next cell / beam specified in the satellite and cell transition tables. If the UT successfully detects the next cell / beam, the normal inter-cell / beam handoff is performed without any signaling between the UT and the SNP.

With normal inter-cell / beam handoff, forward link HARQ processes may lead from one cell / beam to the next. In addition, the reverse assignments may be canceled when the UT handoffs from one cell / beam to the next. For example, the UT may instead send new request messages to transmit the reverse link data.

Exception Scenarios

If the UT loses its current serving cell / beam before the expiration of the specified time in the satellite and cell transition tables, the UT enters a radio link failure (RLF) mode. In RLF mode, the UT may attempt to obtain an alternative cell / beam or satellite (e.g., based on ephemeris information at the UT). For example, the UT may attempt to connect to the next satellite that should be serving the UT. If the UT successfully establishes another connection, the UT may send signaling messages to the SNP to continue the communication that the UT has interrupted prior to the RLF.

While being served by the cell / beam, the UT may fail to detect the next cell / beam specified in the satellite and cell transition table, but may also detect another cell / beam. This may occur, for example, to a high-speed mobile UT (e.g., a UT attached to an airplane). In this case, the UT may send a measurement message to initiate another handoff procedure. In addition, the UT may also send a location update if it has moved after the last time the location update was sent. In response, the SNP may transmit updated satellite and cell transition tables. In this case, the UT follows the updated table. Alternatively, the SNP may initiate a completely new handoff process.

In one example, mode  Handoff Details

Referring now to Figures 9-19, various aspects of a radio connected mode handoff in accordance with the teachings herein will be described in greater detail. The following describes examples of call flows for various connected mode handoff operations. In addition, the following details describe some procedures that may be used to improve handoff performance. In various aspects, these procedures may be used to define handoff measurements, determine when to trigger measurements, determine when to hand off the UT, or trigger the UT to obtain return link synchronization after handoff May be used to determine whether or not the " For purposes of explanation, these details will be discussed in the context of a NAC that includes two components, BxP and AxP, for controlling satellites and / or communicating with satellites.

Figure 9 illustrates the evolution of an example of BxP and AxP components in a satellite system. At some point in time, the UT 902 communicates with one of the AxPs 904 via one of the satellites 906 and BxPs 908, where each BxP 908 is associated with a satellite RF Subsystem 910, or is associated with a satellite RF subsystem 910.

BxP refers to the combination of BCP and BTP (hence the acronym BxP). In some aspects, BxP may include radio network components for controlling satellites. For example, BxP may include, for a given cell / beam of a satellite, a corresponding set of digital circuits serving that cell / beam. Thus, in some aspects, BxP corresponds to a particular antenna. Further, in some aspects, a given BxP may be associated with a particular band for a given cell / beam of satellites.

AxP refers to the combination of ACP and ATP (hence the acronym AxP). In some aspects, AxP corresponds to an anchor point. In some aspects, the anchor point may be associated with a particular area (e.g., a management area, a national boundary, etc.). A given AxP may serve one or more satellites. In addition, a given satellite may serve one or more AxPs.

In this scenario, the connected mode UT may go through two types of handoffs: BxP handoff or AxP handoff. For example, when satellites move in a non-GSO satellite system, the cells / beams (and hence, the circuits and antennas associated with those cells / beams) used to serve a given UT may change over time Will be. Thus, in some aspects, the BxP handoff may correspond to a handoff to a different cell / beam (or antenna, etc.). As another example, a lane fade on a particular cell / beam operating on the first band may require switching to a different band for that cell / beam. Thus, in some aspects, the BxP handoff may correspond to a handoff to a different band for a given cell / beam. The AxP handoff corresponds to a handoff to a different anchor point. For example, the UT may move to a different management area, thus requiring a change in the serving AxP. The BxP handoff may or may not be associated with an AxP handoff.

In some aspects, the following disclosures resolve satellite pointing errors that may occur in a satellite communication system. These errors may be caused by various causes in the system.

Graph 1000 in FIG. 10 illustrates expected gain contours 1002 and 1004 from different satellite beams, a first predicted beam and a second predicted beam, respectively. In some aspects, these beam gain contours may be used to determine when to UT handoff from one beam to the next. For example, the UT may be handed over when the beam gain from the first expected beam (source beam) currently serving the UT falls below the beam gain of the second expected beam (the candidate target beam).

For the first expected beam, Figure 10 illustrates an actual beam gain contour 1006 that may be viewed by the UT due to satellite pointing errors. As indicated in FIG. 10, a shift 1008 in the gain contour due to satellite pointing error shifts the gain contour intersection between the two beam contours from the first intersection 1010 to the second intersection 1012. Thus, at the expected (ideal) handoff time 1014, the gain from the first beam would be lower (by the indicated amount) than the expected gain 1016, thereby adversely affecting the handoff performance will be. As a result, the signal quality at the UT may be lower than desired just prior to handoff. To solve this issue, the ideal handoff time may be shifted by? (Earlier in time in this example) based on shift 1008 in the beam contour due to satellite pointing errors. Accordingly, the handoff will occur at new handoff time 1018. [ 10, the gain 1020 at the new handoff time 1018 may be lower by the A gain 1022 than the expected gain 1016 associated with the expected first beam.

For this purpose, the UT may make measurements of satellite signals (e.g., inter-satellite and intra-satellite) and may transmit this information to the SNP. Based on these signals, the SNP may modify the handoff time for the UT. Thus, the SNP may send the updated handoff information (e.g., via satellite and cell transition tables or a subset of satellite and cell transition tables) to the UT to account for satellite pointing errors.

In some aspects, the random access procedure may be used in scenarios in which the UT has not yet achieved synchronization with the satellite during the handoff. For example, a random access procedure based on UT measurements of satellite signals may allow the UT to achieve return link synchronization.

BxP  Handoff

The logical BxP may be uniquely identified by a 4-tuple including a satellite access network (SAN), a SNP antenna, a satellite beam, and a forward service link (FSL) Here, the SNP antenna refers to the antenna in Fig. The BxP handoff occurs for the UT in radio-connected mode when the BxP 4-tuple of the connection is changed.

Table 3 lists examples of BxP handoffs of the four types and changes associated with the BxP 4-tuple for each type of BxP handoff (highlighted in bold). For the feeder link switching handoff, only the BxP is changed, not the entire SAN.

The BxP handoff occurs in either the handoff time based on the a priori information indicated as THO_a_priori, or the new handoff time recalculated using the UT measurement reports indicated as THO_recalc, where (e.g., as in FIG. 10) THO_recalc = THO_a_priori ± Δ.

If satellite antenna pointing errors are known a priori, the BxP handoff will be initiated by the UT based solely on its satellite handoff table (e.g., satellite and cell transition table). Otherwise, the BxP handoff may require subsequent measurement reports by the UT to the source AxP based on the UT measurements of the target cell, and which source AxP will update the UTs satellite and cell transition table.

BxP  Handoff - Feeder  Link switching

Referring again to FIG. 9, the first configuration 902 and the second configuration 904 illustrate a feeder link switching BxP handoff. Each satellite has dual feeder link connections to two SNPs, but only one feeder link connection is active at any one time. Dual feeder link connections allow momentary switching of the active feeder link connection at the satellite. Feeder link switching appears as an idempt handoff in which the UT handles the same satellite, the same cell, and the same frequency. However, the feeder link switching BxP handoff may also be done to occur simultaneously with cell handoffs for some UTs, in which case the target cell is different from the source cell.

The call flows for feeder link switching BxP handoff are the same as those illustrated in Figures 11 and 13 discussed below. The call flow in FIG. 11 is applicable to the case where the UT does not need to perform a random access procedure to achieve RL synchronization after feeder link switching has occurred. The call flow in FIG. 13 is applicable when the UT needs to perform a random access procedure to achieve RL synchronization after feeder link switching has occurred.

BxP  Handoff - Non-random access

Figure 11 illustrates a non-random access-based BxP handoff call flow without UT measurements and measurement reports. A typical use-case is an intra-satellite BxP handoff. The call flow is between UT 1102, source BxP 1104, target BxP 1106, source AxP 1108, and SNP 1110.

A description of the steps in a non-random access-based BxP handoff call flow that does not have UT measurements and measurement reports is provided below. The initial packet data flow is represented by lines 1112, 1114, and 1116.

At point 1118, the source AxP 1108 pre-configures the target BxP 1106 for handoff prior to the handoff activation time (e.g., one second before it) (e.g., before THO_a_priori). In step 1A, the source AxP 1108 sends a radio access reconfiguration message to the UT 1102. In step 1B, the message is sent to the UT 1102 well ahead of the handoff activation time, such that the UT 1102 has the appropriate time to receive the message. This message may include satellite handoff information such as a row of the transition table (e.g., indicating the handoff activation time) and other parameters. UT 1102 starts timer T-4. If T-4 expires (e.g., a handoff failure occurs), UT 1102 performs a radio access re-establishment procedure.

In steps 2A and 2B, based on a single row of the satellite and cell transition tables included in the radio access reconfiguration message at step 1, both UT 1102 and source AxP 1108 are configured to transmit at a handoff activation time (e.g., THO_a_priori) BxP handoff at the same time. Thus, the UT 1102 prepares to handoff from the source BxP 1104 to the target BxP 1106 and the source AxP 1108 handles the UT 1102 from the source BxP 1104 to the target BxP 1106, Ready to turn off.

In step 3, the UT 1102 resets the media access control (MAC) state. Next, the UT 1102 acquires a new cell (e.g., FL synchronization).

In step 4, after handoff activation + inter-cell tune-away time, target BxP 1106 sends a RL acknowledgment + channel quality indicator (CQI) request to UT 1102. The RL acknowledgment is addressed to the UT identifier (UT-ID) that the source AxP 1108 has assigned to the UT 1102 in the radio access reconfiguration message (see step 1).

In step 5, upon receiving the RL acknowledgment from the target BxP 1106, the UT 1102 stops the timer T-4 (e.g., the handoff is successful) and forwards it to the source AxP 1108 Step 5B) sends the CQI report and radio access reconfiguration complete message to the target BxP 1106 (step 5A). The radio access reconfiguration complete message does not include information elements (IEs), but is integrity protected and encrypted with the old keys (e.g., Kint and Kenc, respectively). The final packet data flow is represented by lines 1120, 1122, and 1124.

Figure 12 illustrates a non-random access-based BxP handoff call flow with UT measurements and measurement reports. A typical use-case is an intra-satellite BxP handoff. The call flow is between UT 1202, source BxP 1204, target BxP 1206, source AxP 1208, and SNP 1210.

A description of the steps in the non-random access-based BxP handoff call flow with UT measurements and measurement report follows. The initial packet data flow is represented by lines 1212, 1214, and 1216.

A radio access reconfiguration message sent to the UT 1202 while the UT 1202 is being served by a given source cell may instruct the UT 1202 when to make measurements for the next target cell. Thus, at point 1218, while in a previous cell, source AxP 1208 may configure UT 1202 with measurement gap information (e.g., gap pattern) corresponding to the measurement time. The satellite pointing error may require that the satellite handoff occur at the ideal handoff time +/- Δ, and thus may require measurements by the UT 1202, so that the source AxP 1208 may use this information Lt; / RTI > In steps 1A and 1B, the source AxP 1208 sends a radio access reconfiguration message to the UT 1202. The message includes measurement gap configuration information (in addition to the handoff activation time and other IEs described herein) and measurement activation / deactivation time. In step 3, the UT 1202 measures the signal strength of the target cell according to the measurement gap configuration information it received from the source AxP 1208. [ The packet data flow continues as represented by lines 1218, 1220, and 1222.

In steps 4A and 4B, the UT 1202 uses the event-based reporting of the signal strength to send a measurement report to the source AxP 1208, which indicates the signal strength (e.g., RSRP) send. The source AxP 1208 configures the UT 1202 to use Event 1 (the source cell becomes better than the threshold) as the criteria for triggering the measurement report. The source AxP 1208 sets the threshold to be low enough so that the signal strength of the source cell is always greater than the threshold and thereby triggers the UT 1202 to send a measurement report to the source AxP 1208. [ Similarly, source AxP 1208 configures UT 1202 to use Event 4 (the target cell becomes better than the threshold) as criteria for triggering the measurement report. The source AxP 1208 sets the threshold sufficiently low such that the signal strength of the target cell is always greater than the threshold, thereby triggering the UT 1202 to send a measurement report to the source AxP 1208. Other reporting criteria may also be used.

In step 5, based on the UT measurement report (see step 4), the source AxP 1208 calculates a new handoff activation time (e.g., THO_recalc), and before the new handoff activation time (e.g., before THO_recalc) Pre-configures the target BxP 1206 for. For example, based on the satellite ephemeris information, beam patterns, and UT measurement report, the source AxP 1208 may prepare a BxP handover to occur at the ideal handover time +/- delta . In steps 6A and 6B, the source AxP 1208 sends a radio access reconfiguration message to the UT 1202. The contents of the message are described herein and include a new handoff activation time. Optionally, the message may also include measurement gap configuration information and measurement activation / deactivation time. The message is sent to the UT 1202 well ahead of the new handoff activation time so that the UT 1202 has the appropriate time to receive the message. UT 1202 starts timer T-4. If T-4 expires (e.g., a handoff failure occurs), UT 1202 performs a radio access re-establishment procedure. Also, if the source AxP 1208 does not receive a measurement report from the UT 1202 in a timely manner, then the source AxP 1208 will configure both the target BxP 1206 and UT 1202 for handoff (E.g., THO_a_priori) in the past.

Based on the single row of the satellite and cell transition tables contained in the radio access reconfiguration message at step 6, both UT 1202 and source AxP 1208 receive a BxP handoff at the new handoff activation time (e.g., THO_recalc) Get ready at the same time.

In step 7, the UT 1202 resets the MAC state. UT 1202 acquires a new cell (e.g., FL synchronization).

In step 8A, after handoff activation + inter-cell tune-away time, target BxP 1206 sends a RL Ack + CQI request to UT 1202. The RL acknowledgment is addressed to the UT-ID that the source AxP 1208 assigned to the UT 1202 in the radio access reconfiguration message (see step 3).

Upon receiving the RL acknowledgment from the target BxP 1206, the UT 1202 stops the timer T-4 (e.g., the handoff is successful), sends a CQI report (step 8A) and a radio access reconfiguration complete message to the target BxP 1206 / source AxP 1208 (steps 9A and 9B). The radio access reconfiguration complete message does not contain IEs, but is integrity protected and encrypted with the old keys (e.g., Kint and Kenc, respectively). The final packet data flow is represented by lines 1224, 1226, and 1228.

BxP  Handoff - Random Access

Figure 13 illustrates a random access-based BxP handoff call flow without UT measurements and measurement reports. A typical use-case is an inter-satellite BxP handoff. The call flow is between UT 1302, source BxP 1304, target BxP 1306, source AxP 1308, and SNP 1310.

Followed by a description of the steps in the random access-based BxP handoff call flow without UT measurements and measurement report. The initial packet data flow is represented by lines 1312, 1314, and 1316.

In steps 1A and 1B, the source AxP 1308 pre-configures the target BxP 1306 for handoff before the handoff activation time (e.g., before THO_a_priori). The source AxP 1308 sends a radio access reconfiguration message to the UT 1302. The contents of the message are described herein. The message is sent to the UT 1302 well ahead of the handoff activation time, so that the UT 1302 has the appropriate time to receive the message. UT 1302 starts timer T-4. If T-4 expires (e.g., a handoff failure occurs), UT 1302 performs a radio access re-establishment procedure.

In step 2, based on the single row of the satellite and cell transition tables contained in the radio access reconfiguration message in step 1, both the UT 1302 and the source AxP 1308 are transmitted at handoff activation time (e.g., in THO_a_priori) Prepare BxP handoff at the same time. These operations may be similar to the corresponding operations discussed above in conjunction with FIG.

In step 3, the UT 1302 resets the MAC state. UT 1302 acquires a new cell (e.g., FL synchronization). As represented by parentheses 1318, if step 1 does not include the RA procedure sequence, steps 4 through 7 are not required.

After the handoff activation + inter-satellite tune-away time, the target BxP 1306 transmits an FL control including a dedicated preamble signature to trigger the UT 1302 to perform a non-contention based random access procedure (FL) control channel (FLCC) sequence to the UT 1302. This enables UT 1302 to achieve RL synchronization later.

In step 4, UT 1302 sends a non-contention-based random access preamble on random access to target BxP 1306. Upon receiving a non-contention-based random access preamble from UT 1302, target BxP 1306 validates the received signature sequence.

In step 5, target BxP 1306 sends a random access response addressed to the appropriate group of UTs (e.g., RA-RNTI) to UT 1302. The random access response includes a paging area (PA), an RL acknowledgment (including a CQI request), and a temporary UT-ID.

If a dedicated preamble signature is used, the RL acknowledgment may include a CQI request. In this case, the process may skip from point 1320 to step 8B. Otherwise, the operations of block 1322, including steps 6 and 7, and the operations of step 8A, may be performed.

(E.g., in step 8A), the UT 1302 stops the timer T-4 (e.g., the handoff is successful) and reports the CQI (step 1304) when receiving the RL Ack + CQI request from the target BxP 1306 8B to the target BxP 1306. If a dedicated preamble signature is used, the UT 1302 also sends a radio access reconfiguration complete message to the target BxP 1306 (step 9A) for forwarding to the source AxP 1308 (step 9B). The radio access reconfiguration complete message does not contain IEs, but is integrity protected and encrypted with the old keys (e.g., Kint and Kenc, respectively). The final packet data flow is represented by lines 1324, 1326, and 1328.

Figures 14 and 15 illustrate a random access-based BxP handoff call flow with UT measurements and measurement reports. A typical use-case is an inter-satellite BxP handoff. The call flow is between UT 1402, source BxP 1404, target BxP 1406, source AxP 1408, and SNP 1410.

A description of the steps in the random access-based BxP handoff with UT measurements and measurement report follows. The initial packet data flow is represented by lines 1412, 1414, and 1416.

14, while in the previous cell, the UT 1402 transmits a radio access (in addition to the handoff activation time and other IEs described herein) with measurement gap configuration information and measurement activation / deactivation time Lt; RTI ID = 0.0 > AxP 1408 < / RTI > In step 1, the UT 1402 measures the signal strength of the target cell according to the measurement gap configuration information it received from the source AxP 1408. [ The packet data flow continues as represented by lines 1418, 1420, and 1422.

In step 2, the UT 1402 sends a measurement report to the source AxP 1408 indicating the signal strength (e.g., RSRP) of both the source cell and the target cell, using an event-based report of the signal strength. Source AxP 1408 configures UT 1402 to use Event 1 (the source cell becomes better than the threshold) as criteria for triggering the measurement report. Source AxP 1408 sets the threshold sufficiently low such that the signal strength of the source cell is always greater than the threshold, thereby triggering UT 1402 to send a measurement report to source AxP 1408. [ Similarly, the source AxP 1408 configures the UT 1402 to use Event 4 (the target cell becomes better than the threshold) as criteria for triggering the measurement report. The source AxP 1408 triggers the UT 1402 to set the threshold low enough so that the signal strength of the target cell is always greater than the threshold, thereby sending a measurement report to the source AxP 1408. Other reporting criteria may also be used.

On the basis of the UT measurement report (see step 2), the source AxP 1408 calculates a new handoff activation time (e.g., THO_recalc) and determines the target BxP (1406).

The operations of steps 3 to 11 correspond to steps 1 to 9 of Fig. Accordingly, these operations will be briefly discussed. In step 3, the source AxP 1408 sends a radio access reconfiguration message to the UT 1402. The contents of the message are described herein and include a handoff activation time. Optionally, the message may also include measurement gap configuration information and measurement activation / deactivation time. The message is sent to the UT 1402 well before the handoff activation time, so that the UT 1402 has the appropriate time to receive the message. UT 1402 starts timer T-4. If T-4 expires (e.g., a handoff failure occurs), UT 1402 performs a radio access re-establishment procedure. Also, if the source AxP 1408 does not receive a measurement report from the UT 1402 in a timely manner, then the source AxP 1408 will configure both the target BxP 1406 and the UT 1402 for handoff (E.g., THO_a_priori) in the past.

In step 4, based on the single row of the satellite and cell transition table included in the radio access reconfiguration message in step 3, both the UT 1402 and the source AxP 1408 are updated at a new handoff activation time (e.g., THO_recalc) Prepare BxP handoff at the same time.

In step 5, the UT 1402 resets the MAC state. UT 1402 acquires a new cell (e.g., FL synchronization).

15, after a handoff activation + inter-cell tune-away time, a target BxP 1406 may send an FLCC (e.g., a FLCC) containing a dedicated preamble signature to trigger the UT 1402 to perform a non- And transmits the sequence to the UT 1402. This enables UT 1402 to achieve RL synchronization later on.

In step 6, the UT 1402 sends a non-contention based random access preamble on the random access to the target BxP 1406. Upon receiving a non-contention based random access preamble from UT 1402, target BxP 1406 validates the received signature sequence.

In step 7, the target BxP 1406 sends a random access response addressed to the appropriate RA-RNTI to the UT 1402. The random access response includes a paging area, an RL acknowledgment (including a CQI request), and a temporary UT-ID.

Upon receiving the RL Ack + CQI request from the target BxP 1406 (step 10A), the UT 1402 stops the timer T-4 (e.g., the handoff is successful) and sends a CQI report to the target BxP 1406 (Step 10B), and sends a radio access reconfiguration complete message to the target BxP 1406 / source AxP 1408 (step 11). The radio access reconfiguration complete message does not contain IEs, but is integrity protected and encrypted with the old keys (e.g., Kint and Kenc, respectively). The final packet data flow is represented by lines 1424, 1426, and 1428.

BxP  Handoff - Failover

In intra-SNP, SNP antenna failover, the antenna assembly serving satellites failed. In this case, one of two scenarios is possible. In the first scenario, the UT is responsible for maintaining connectivity and data services in the data service, which are managed by the SNP as part of normal operation (e.g., scheduling of FL and RL resources for UT by the SNP, HARQ retransmissions, and ARQ retransmissions). I experience a break for a while. In the second scenario, the UT experiences loss of FL synchronization, or connectivity and a significant interruption in data service resulting in radio link failure (RLF).

AxP  Handoff

Inter-AxP handoffs may be performed for load-balancing purposes, or for non-transient UTs requiring inter-AxP handoffs due to changes in the location of the UT resulting in intersection of the management domain boundaries. The AxP handoff procedure includes three distinct phases: AxP handoff preparation, AxP handoff execution, and AxP handoff completion.

The following procedures may be used for AxP handoff preparation.

When direct forwarding of data is applied to radio control (RC) acknowledged mobile (AM) data bearers, the tunnels are used for both forward link and reverse link data forwarding AxP in one direction) may be established for each RL-AM data bearer. Conversely, when indirect forwarding of data is applied, the tunnels may be established per RL-AM data bearer (in one direction from the source AxP to the target AxP via the SNP) for both forward and reverse link data forwarding.

For unacknowledged mobile (AM) data bearers, when direct forwarding of data is applied, the tunnels are used only for forward link data forwarding (in one direction from the source AxP to the target AxP) to the RL-UM data It may be established for each bearer. The reverse link data is not forwarded from the source AxP to the target AxP, but instead is transmitted by the source AxP to the SNP. Conversely, when indirect forwarding of data is applied, the tunnels may be established per RL-UM data bearer (only in one direction from source AxP to target AxP) for forward link data forwarding. The reverse link data is not forwarded from the source AxP to the target AxP, but instead is transmitted by the source AxP to the SNP.

The following procedures may be used for AxP handoff execution.

For RL-AM data bearers, the reverse link forwarded data includes sequence numbers (SNs). The forward link forwarded data may include SNs or may not include forward link data if it is not yet assigned by the source AxP and forward link data is received from the SNP. The source AxP transmits both forward link and reverse link SN and frame number (FN) information to the target AxP. MAC and RL states are reset.

For RL-UM data bearers, the forward link forwarded data may include SNs or may not include forward link data if received from the SNP while the SN has not yet been assigned by the source AxP. If the forward link forwarded data includes an SN, the target AxP must first transmit this data to the UT (after resetting both SN and FN). The state is reset (e.g., the forward link and reverse link SN and FN are reset). MAC and RL states are reset.

The following procedures may be used for handoff completion.

For RL-AM data bearers, the UT may send a list of missing / received forward link protocol data units (PDUs) to the target AxP, and the target AxP may list the missing / received reverse link PDUs UT. For both RL-AM and RL-UM data bearers, the forward link tunnels per data bearer are switched from the source AxP to the target AxP, and the UT resources are released at the source AP.

Figures 16-18 illustrate an AxP handoff call flow with no mobility management (MM) relocation and no SNP relocation. 16 illustrates handoff preparation. 17 shows a handoff execution. 18 shows handoff completion. A description of the steps in the AxP handoff call flow follows.

14, the call flow includes a UT 1602, a source BxP 1604, a target BxP 1606, a source AxP 1608, a target AxP 1612, a mobility management (MM) component 1614 ), And SNP 1610. The initial packet data flow is represented by lines 1616, 1618, and 1620.

In step 1, the source AxP 1608 makes a decision to hand off the UT 1602 to the target cell and the target AxP 1612 based on the satellite EMI information and beam patterns.

In step 2, source AxP 1608 sends a handoff requested message to MM 1614 to request provisioning of resources in target AxP 1612. The message may include a paging area identifier (PAI) of the target AxP 1612 (such that the MM 1614 may determine which target AxP 1612 should send the handoff request message in step 3) Target transparent container (transparently passing MM 1614) carrying a handoff ready information message that includes a forwarding path (e.g., via an appropriate interface) and whether it is available or not : The security configuration of the UT in the source AxP 1608; the target cell ID (e.g., the target BxP ID indicating the beam to be prepared); and the source AxP 1608) indicates whether or not to suggest forward link data forwarding).

In step 3, MM 1614 sends a handoff request message to target AxP 1612 to request preparation of resources in target AxP 1612. The message includes a list of data bearers to be set up (e.g., quality of service (QoS) information, data-per-SNP tunneling protocol (e.g., tunneling protocol (TP) addressing information), and a pair of security context information (e.g., 1-hop security for the derivation of the target AxP of new security keys for user plane traffic and radio signaling NH, NCC).

 In step 4, upon receiving the handoff request message from MM 1614, target AxP 1612 determines that it can establish the UE context.

In step 5, the target AxP 1612 sends a handoff request acknowledgment message to the MM 1614 to inform the MM 1614 about the resources that are ready in the target AxP 1612. Source transparent container (which transparently passed MM 1614) carrying a handoff command message to be used by the source AxP 1608 when constructing a radio access reconfiguration message (see step 8) . The handoff request acknowledgment message may also be transmitted to the target AxP 1612 on the designated interface per data bearer (e.g., for data transmitted directly from the SNP 1610 to the target AxP 1612, rather than via the source AxP 1608) And a list of data bearers to be set up, including downlink TP addressing information. The handoff request message may also be forwarded to additional target AxP 1612 data bearer per data bearer (if the source AxP 1608 has proposed forward link data forwarding for the data bearer and the target AxP 1612 has accepted the offer) Link TP addressing information and a target AxP reverse link TP addressing information per data bearer (if the target AxP 1612 requests the source AxP 1608 to perform reverse link data forwarding for the RL-AM data bearer) have.

In step 6, if the indirect forwarding of the data (e.g., via the designated interface) is applied, the MM 1614 sends an indirect data forwarding tunnel creation request message to the SNP 1610. The message includes a list of data bearers that contain the following information per data bearer: a data bearer ID, if applicable, a tunnel ID and IP address of the target AxP for indirect forwarding of the forward link data on the specified interface, and The tunnel ID and IP address of the target AxP for indirect forwarding of reverse link data on the specified interface. Later, the SNP 1610 sends an indirect data forwarding tunnel creation response message to the MM 1614. The message includes the following information per data bearer: the data bearer ID, the tunnel ID and IP address of the SNP for indirect forwarding of the forward link data on the designated interface, and the reverse link data on the designated interface The tunnel ID and IP address of the SNP for indirect forwarding.

In step 7, the MM 1614 sends a handoff command message to the source AxP 1608 to inform the source AxP 1608 that the resources for handoff are ready in the target AxP 1612. Source transparent container returned in the handoff request acknowledgment message (see step 5) that should be used by the source AxP 1608 in constructing the radio access reconfiguration message (see step 8) . The handoff command message also includes a list of data bearers to be set up. If the direct forwarding of the data is applied (e.g., via an appropriate interface), the message will be forwarded to the destination (if the source AxP 1608 has proposed forward link data forwarding for the data bearer and the target AxP 1612 accepts the offer ) Target AxP forward link TP addressing information per data bearer, and a target AxP reverse link per data bearer (if the target AxP 1612 requests source AxP 1608 to perform reverse link data forwarding for the RL-AM data bearer) TP addressing information. If the indirect forwarding of the data is applied (e.g., via a designated interface), the message will suggest that the source AxP 1608 performs forward-link data forwarding for the data bearer, and that the target AxP 1612 will accept the offer SNP forward link TP addressing information per data bearer (if the target AxP 1612 requests the source AxP 1608 to perform reverse link data forwarding for the RL-AM data bearer), and SNP reverse link TP Addressing information. See step 6. The message also includes a new satellite and cell transition table. Upon receiving the handoff command message, the source AxP 1608 freezes the transmitter / receiver status for the data bearers of the UT.

In step 8, the source AxP (1608) sends a radio access reconfiguration message to the UT (1602). The message includes new UT-ID, PCI, and frequency for the target BxP 1606, security information, radio resource common and private configuration information as required (e.g., random access information, CQI reporting information) (If there are any changes in the target data bearer configuration information). The message also includes a new paging area identifier that uniquely identifies the target AxP 1612. Upon receiving the radio access reconfiguration message from the source AxP 1608, the UE starts timer T-4. If T-4 expires (e.g., a handoff failure occurs), UT 1602 performs a radio access re-establishment procedure.

In step 9, UT 1602 derives new KAxP, KUPenc, Kint, and Kenc that should be used when UT 1602 performs a handoff to target AxP 1612.

Referring to FIG. 17, for RL-AM data bearers, UT 1602 resets MAC and RL states (step 10). For the RL-UM data bearers, the UT 1602 resets the MAC, RL, and states. The UT 1602 later acquires a new cell (e.g., FL synchronization).

In steps 11 and 12, the source AxP 1608 sends a UT status delivery message to the target AxP 1612 via the MM 1614. The source AxP 1608 sends this message to the target AxP 1612 only if at least one data bearer is configured for RL-AM operation. The message contains the following information per RL-AM data bearer: reverse link SN and FN receiver status, forward link SN and FN transmitter status, and (optionally) (target AxP 1612) for the RL-AM data bearer. The reception status of the reverse link service data units (SDUs) when the source AxP 1608 has requested the reverse link data forwarding and the source AxP 1608 has accepted the request. Also, for RL-AM and RL-UM data bearers, the source AxP 1608 begins to forward the forward-link data (stored in the source AxP 1608 data bearer buffers) to the target AxP 1612 in order do. For RL-AM data bearers, this includes all forward-link SDUs with that SN whose successful delivery of the corresponding PDU was not confirmed by the UT 1602 (e.g., via the RL Status PDU). For RL-AM and RL-UM data bearers, this also includes new forward link data arriving on the designated interface from SNP 1610. For the RL-AM data bearers to which reverse link data forwarding is applied, the source AxP 1608 transmits the reverse link SDUs with that SN that were received out-of-sequence to the target AxP 1612, Lt; / RTI > For RL-AM data bearers where reverse link data forwarding is not applied, the source AxP 1608 discards the reverse link SDUs that were received in the out-of-sequence. For the RL-UM data bearers, the source AxP 1608 transmits the reverse link SDUs that were received in an out-of-sequence to the SNP 1610 over the designated interface. NOTE: When direct forwarding of data is applied, the source AxP 1608 forwards the data to the target AxP 1612 on the appropriate interface.

When indirect forwarding of the data is applied, the source AxP 1608 forwards the data 1622 to the target AxP 1612 over the designated interface via the SNP 1610. The forwarded data is stored in the target AxP data bearer buffers (step 12).

In step 12, the UT 1602 sends a contention-based random access preamble on the random access to the target BxP 1606, where the source BxP 1604 and the target BxP 1606 may be the same entity. Upon receiving the random access preamble from UT 1602, target BxP 1606 validates the received signature sequence. If a dedicated preamble signature is available at target BxP 1606 and UT 1602 is assigned a dedicated preamble signature at step 8, UT 1602 transmits a contention-free random access preamble on random access to target BxP (1606), and as a result, there is no possibility of collision.

In step 14, the target BxP 1606 sends a random access response addressed to the appropriate RA-RNTI to the UT 1602. The random access response includes a paging area, an RL acknowledgment, and a temporary UT-ID.

In operations of block 1630, the UT 1602 sends a radio access reconfiguration complete message to the target AxP 1612 (step 15). The message does not contain IEs. The radio access reconfiguration complete message is integrity protected and encrypted with the new Kint and Kenc, respectively, and the UT-ID MAC control element and the two new MAC control elements: the PAI MAC control element and the location management information (LMI) MAC control element. The UT-ID MAC control element contains the UT-ID assigned to the UT 1602 by the target AxP 1612 in the radio access reconfiguration message (see step 8). The PAI MAC control element includes the PAI assigned to UT 1602 by target AxP 1612 in step 8. The LMI MAC control element contains the most recent location information of the UT. The target BxP 1606 parses the PAI MAC control element to determine to which AxP it should forward the radio access reconfiguration complete message. The target BxP 1606 may then send a handover notification message to the MM 1614 (e.g., instead of step 19). UT 1602 starts a contention analysis timer.

In step 16, the target BxP 1606 sends an RL acknowledgment to the UT 1602 for the new transmission. The RL acknowledgment is addressed to the UT-ID that the target AxP 1612 has assigned to the UT 1602 in the radio access reconfiguration message (see step 8). Upon receiving the RL acknowledgment from the target BxP 1606, the UT 1602 stops the contention analysis timer and the timer T-4. The UT 1602 may begin to transmit reverse link signaling on the signaling radio bearers (e.g., SRB1 and SRB2) and reverse link data on all data radio bearers (DRBs). UT 1602 may also begin to receive forward link signaling on SRB1 and SRB2, and forward link forwarded data on all DRBs.

18, for the RL-AM data bearers to which reverse link data forwarding is applied, the target AxP 1612 sends a status report message including the missing and received reverse link PDUs list to the UT 1602, (Step 17). The target AxP 1612 uses the information in the UT status delivery message (see step 11) from the source AxP 1608 via the MM 1614 to configure the status report. Upon receiving the status report message from the target AxP 1612, the UT 1602 does not perform retransmission of any PDUs whose successful delivery is confirmed by the status report message. After the reverse link PDU retransmissions are successfully completed, the UT 1602 begins transmitting the new RL-AM reverse link PDUs to the target AxP 1612. Because the reverse link SN is maintained based on the RL-AM data bearer, the target AxP 1612 uses a windows-based mechanism for in-sequence delivery and replication avoidance. For the RL-UM data bearers, the UT 1602 begins transmitting new RL-UM reverse link PDUs to the target AxP 1612. The packet data flow is represented by arrows 1632, 1634, and 1636.

For all RL-AM data bearers that have configured UT 1602 to transmit the status report on the reverse link during re-establishment, UT 1602 includes a list of missing and received forward link PDUs To the target AxP 1612 (step 18). Upon receiving this message, the target AxP 1612 begins forwarding the forward link PDUs that have been forwarded to the target AxP 1612 by the source AxP 1608 with or without their SNs to the UE. This packet data flow is represented by arrows 1638 and 1640. The target AxP 1612 continues to do this until it receives one or more TP end marker packets from the source AxP 1608 for its RL-AM data bearer. Target AxP 1612 does not perform retransmission of any PDUs whose successful delivery is confirmed by the status report message from UT 1602. [ Because the forward link SN is maintained based on the RL-AM data bearer, the UT 1602 uses a Windows-based mechanism for in-sequence delivery and replication avoidance. For the RL-UM data bearers, the target AxP 1612 receives the target AxP (1610) by the source AxP 1608 (without continuing its original SNs since the SN is not maintained based on the RL-UM data bearer) 1612 to the UT 1602. The forward link PDUs are forwarded to the UT 1602, The target AxP 1612 continues to do this until it receives one or more TP end marker packets from the source AxP 1608 for each RL-AM data bearer.

Step 19 may occur immediately after step 15. [ In step 19, the target AxP 1612 sends a handoff notification message to the MM 1614 to inform the MM 1614 that the UT 1602 has been identified in the target cell and the handoff has been completed. The message includes the PAI of the target AxP 1612 and the target cell ID (e.g., the target BxP ID indicating the beam from which the UT 1602 was identified).

In step 20, MM 1614 sends a bearer modification request message to SNP 1610. The message includes a list of data bearers comprising the following information per data bearer: a data bearer ID (for uniquely identifying the data bearers of the UT), and a tunnel ID and IP address of the target AxP for the forward link user plane ).

In step 21, the SNP 1610 switches the forward link data path from the source AxP 1608 to the target AxP 1612 and sends one or more TP end marker packets 1642 per data bearer to the source AxP 1608 do. SNP 1610 also begins transmitting the forward link data intended for UT 1602 directly to target AxP 1612 (arrows 1644 and 1646). Source AxP 1608 forwards the TP end marker packet (s) per data bearer to target AxP 1612. Upon receiving the TP end marker packet (s) per data bearer from the source AxP 1608, the target AxP 1612 may begin to forward the forward link data received directly from the SNP 1610 to the UT 1602 have. NOTE: When direct forwarding of data is applied, the source AxP 1608 forwards the TP end marker packet (s) 1648 to the target AxP 1612 on the appropriate interface. When indirect forwarding of the data is applied, the source AxP 1608 forwards the data via the SNP 1610 to the target AxP 1612 (arrow 1650).

In step 22, the SNP 1610 sends a bearer modification response message to the MM 1614. The message includes a list of data bearers that contain the following information per data bearer: the data bearer ID and cause (e.g., the accepted request). At step 23A, MM 1614 sends a UE Context Release Command message to source AxP 1608 to request the release of the UT-associated S1-logical connection on the S1 interface. Subsequently, at step 23B, the source AxP 1608 sends a UE Context Release Command message to the MM 1614 to confirm the release of the UT-associated logical connection on the appropriate interface. At step 24, the source AxP 1608 releases UT radio resources and context. In step 25, the indirect data forwarding tunnel request (from step 6) is deleted. The final packet data flow is represented by lines 1652, 1654, and 1656.

Use of satellite and cell transition tables

In some implementations, AxP may generate and / or update satellite and cell transition tables, as needed, using one or more of the following: UT location and / or speed, satellite location, satellite beam / Cell patterns, satellite beam / cell turn on / off schedules, or satellite pointing error. The location and / or speed of the UT may, if specified, be transmitted by the UT via radio signaling messages. The locations of the satellite over time may be obtained from the ephemeris data. For example, in some satellite access networks (SANs) that include multiple SNPs, the NOC / SOC at the SAN may provide updated satellite ephemeris information to all AxPs in the SAN .

In some implementations, the system provides a UT with a single row of satellites and cell transition tables to be used for connected mode handoffs (e.g., the rows of Table 2 described above). For example, the source AxP / BxP may include a single row of satellite and cell transition tables in an information element (IE) of a radio access reconfiguration message that is transmitted in the UT while the UT is still on the serving cell. Thus, while the UT is being served by one cell / beam, the UT may receive satellite and cell transition information for use by the UT to transition to another cell / beam.

BxP  Configuration messages in handoff

As mentioned above, each satellite beam may be viewed as a separate cell with its own data and control channels, and signals. When the UT is handing over from one cell to another, some of the radio configuration parameters that were valid for the source cell may be changed and may need to be updated for UT operation on the target cell.

The radio message used for radio reconfiguration of the radio parameters for the serving cell is also used to convey updated configuration parameters for the target cell.

AxP communicates the reconfiguration parameters for the target cell to the source cell (step 1 in FIG. 11, and also applicable to radio access reconfiguration delivery in FIGS. 12, 13, and 14). The reconfiguration message for the target cell is forwarded by the source cell to the UT before the handoff occurs, as shown in step 1 in FIG. The transmission of the message needs to be done well in advance of the handoff, so the UT has time to receive the message in a timely manner to allow reliable transmission. Upon receiving a reconfiguration message for the target cell, the UT stores it and applies reconfiguration if it starts communicating on the target cell.

The handoff is performed based on the handoff transition table (Table 3) and follows the procedures defined for BxP handoff. The new configuration is applied at the handoff time and the UT is configured appropriately for the new serving cell before the data and control exchange begins.

The radio reconfiguration message for the target beam may include radio parameters that are UT specific (dedicated) and cell specific (common). They can be: dedicated to DRX, discontinuous reception (DRX), power headroom reporting (PHR), buffer status reporting (BSR) scheduling request (SR) Parameters of the MAC configuration, HARQ for semi-persistent scheduling, parameters of SPS configuration (periodicity, resources), power control of data and control channels, CQI reporting, sounding reference signal (SRS) PHY configuration, and random access (such as preamble information, power control, monitoring information), physical random access (such as root sequence information and physical random access configuration index), reference signal power and power control, RL criteria Signals, ACK / NACK and CQI mapping, SRS (such as bandwidth and sub-frame configuration), p-Max (used to limit the RL transmit power of UTs in the cell) SR, random access configuration, UT-ID, PCI, common radio resource configuration. It should be noted that since the UT-ID is provided to the UT for each serving cell, the 16-bit UT-ID may be sufficient to uniquely address a given number of about 5000 UTs per cell.

Radio link failure

During normal operation, when the UT is handed off from one satellite or cell / beam to another satellite or cell / beam, the signaling for the handoff is completed between the SNP entity supporting the handoff and the UT. A radio link failure (RLF) may be declared (e.g., at the UT) if the UT loses communication with the SNP before the handoff signaling is complete. RLF can occur in the system because the UT loses its connection to the cell due to various possible reasons - for example, due to rain or snow, or fading effects due to blockage by buildings or trees. In this case, the UT may employ an RLF restoration mechanism to reestablish communication with the SNP. The RLF procedure strives to reconnect the UT to the same source cell or to a different (e.g., target) cell.

Figure 19 illustrates an example of a call flow for an RLF procedure. The call flow is between UT 1902, source BxP or target BxP 1904, and source AxP or target AxP 1906. A description of the steps of the call flow follows.

In step 1, radio link detection procedures are used to detect an RLF (e.g., problems in a radio link connection). This can occur in the physical layer (e.g., when the SNR is less than a certain threshold), or in the MAC layer (e.g., when a certain number of packets are decoded in error) (If it has been reached with respect to < / RTI > UT 1902 initiates a radio access re-establishment procedure by initiating a target satellite and cell search and selection procedure.

After the UT 1902 acquires the appropriate target satellite and cell (step 2), the UT 1902 sends a contention-based random access preamble on the random access to the target BxP 1904 (step 3). Upon receiving the random access preamble from UT 1902, target BxP 1904 validates the received signature sequence. The target BxP 1904 may be the same as the source BxP (e.g., the UT 1902 selects the same cell it was connected to before the RLF occurred).

In step 4, the target BxP 1904 sends a random access response addressed to the appropriate UT-ID to the UT 1902. The random access response includes a paging area, an RL acknowledgment, and a temporary UT-ID.

In step 5, the UT 1902, in conjunction with the two new MAC control elements (the PAI MAC control element and the LMI MAC control element), sends a radio access re-establishment request message to the appropriate target AxP 1906. The radio access re-establishment message includes the UT's old UT-ID, the old PCI, and the MAC-I for verification during the radio access re-establishment procedure. The PAI MAC control element contains the most recent PAI assigned to the UT (1902) by the source AxP. The PAI belongs to the target AxP if the handover was in progress before the RLF; Otherwise, the PAI belongs to the source AxP. The LMI MAC control element contains the most recent location information of the UT. The target BxP 1904 parses the PAI MAC control element and the LMI MAC control element to determine to which AxP it should forward the radio access re-establishment request message. When the LMI MAC control element indicates a management area that is not handled by the AxP mapped to the PAI MAC control element, the target BxP 1904 forwards the radio access re-establishment request message to the appropriate target AxP The procedure will result in failure and will cause the UT 1902 to initiate a NAS restore procedure (e.g., a service request procedure). UT 1902 starts timer T-3. If T-3 expires (e.g., the radio access re-establishment procedure fails), UT 1902 performs the NAS service request procedure.

In step 6, the target AxP 1906 sends a radio access re-establishment message to the UT 1902 along with a UT contention analysis identity MAC control element (to provide contention analysis). The radio access re-establishment message includes security configuration information used by the UT 1902 to derive a new control plane and user plane keys (see step 7). The message may also include SRB1 configuration information.

In step 7, the UT 1902 derives new KAxP, KUPenc, Kint, and Kenc to be used with the re-established radio access.

In step 8, the UT 1902 sends a radio access re-establishment complete message to the target AxP 1906. The message does not contain IEs, is integrity protected, and is encrypted with the new Kint and Kenc, respectively.

In step 9, the target AxP 1906 sends a radio access reconfiguration message to the UT 1902. The message includes SRB2 and DRB configuration information.

In step 10, the UT 1902 sends a radio access reconfiguration complete message to the target AxP 1906. The message does not contain IEs. The final packet data flow is represented by lines 1912 and 1914.

One example of operations

With the above in mind, additional examples of operations that may be performed by the UT and / or the SNP under the support of the handoff of the UT will now be described with respect to Figures 20-34.

20 is a diagram illustrating an example of a process 2000 for generating and using satellite handoff information, in accordance with some aspects of the disclosure. Process 2000 may occur within a processing circuit that may be located in a SNP or some other suitable device (device). In some implementations, the process 2000 represents the operations performed by the SNP controller 250 of FIG. In some implementations, process 2000 represents operations performed (e.g., by processing circuitry 3510) by apparatus 3500 of FIG. Of course, in various aspects within the context of the disclosure, the process 2000 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2002, the SNP (or other suitable device) optionally receives information from the user terminal. For example, the SNP may receive user terminal capabilities and location information.

At block 2004, the generation of satellite handoff information is triggered in the SNP (or other suitable device). This information may include some or all of the satellite and beam / cell transition tables. For example, the creation of a table may be triggered based on handoff of the user terminal to the satellite, or based on reception of the measurement message from the user terminal.

At block 2006, the SNP (or other suitable device) generates satellite handoff information that specifies the handoff time for a particular beam of a particular satellite. For example, the information may be a table indicating the timing for transitioning between the cells / beams and the satellites. In some aspects, the table is optionally based, in part, on the information received from the user terminal in block 2002.

At block 2008, the SNP (or other suitable device) transmits satellite handoff information to the user terminal.

At block 2010, the SNP (or other suitable device) performs handoffs for user terminals to different cells / beams and at least one satellite based on satellite handoff information.

21 is a diagram illustrating an example of a process 2100 for utilizing satellite handoff information, in accordance with some aspects of the disclosure. Process 2100 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 2100 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 2100 represents operations performed (e.g., by the processing circuitry 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, the process 2100 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2102, the user terminal (or other suitable device) optionally transmits a measurement message.

At block 2104, the user terminal (or other suitable device) receives satellite handoff information specifying a handoff time for a particular beam of a particular satellite. For example, the information may be a table indicating the timing for transitioning between the cells / beams and the satellites.

At block 2106, the user terminal (or other suitable device) performs handoffs (e.g., to different cells / beams and at least one satellite) with a particular beam of different satellites based on the satellite handoff information.

22 is a diagram illustrating an example of a process 2200 for signaling user terminal capability information, in accordance with some aspects of the disclosure. Process 2200 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 2200 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 2200 represents operations performed (e.g., by the processing circuit 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, the process 2200 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2202, the transmission of user terminal capability information is triggered at the user terminal (or other suitable device). For example, the transmission may be triggered as a result of an initial connection to the satellite.

At block 2204, the user terminal (or other suitable device) generates capabilities messages. In some aspects, the message indicates whether the UT can sense multiple cells / beams and / or satellites, and / or the message indicates UT inter-cell / beam and / or inter-satellite tune time .

At block 2206, the user terminal (or other suitable device) transmits capabilities messages to the SNP.

23 is a diagram illustrating an example of a process 2300 for utilizing user terminal capabilities in accordance with some aspects of the disclosure. Process 2300 may occur within a processing circuit that may be located in a SNP or some other suitable device (device). In some implementations, the process 2300 represents the operations performed by the SNP controller 250 of FIG. In some implementations, the process 2300 represents operations performed (e.g., by the processing circuit 3510) by the device 3500 of FIG. Of course, in various aspects within the context of the disclosure, process 2300 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2302, the SNP (or other suitable device) receives capabilities messages from the user terminal. These capabilities messages include user terminal capability information.

At block 2304, the SNP (or other suitable device) includes satellite handoff information. For example, a portion of a table or table may be generated based in part on the limitations due to user terminal capability information (e.g., tune times), user terminal location information, satellite motion, ephemeris information, and current systems .

At block 2306, the SNP (or other suitable device) selects a handoff procedure for the user terminal based in part on the user terminal capability information. For example, monitoring of a measurement message from a user terminal may be enabled or disabled based on whether the user terminal is dual-detectable. Accordingly, the device may enable or disable whether the device monitors for a measurement message based on user terminal capability information.

24 is a diagram illustrating an example of a process 2400 for signaling user terminal location information, in accordance with some aspects of the disclosure. Process 2400 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 2400 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 2400 represents operations performed (e.g., by the processing circuitry 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, process 2400 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2402, the transmission of the user terminal location information is triggered at the user terminal (or other suitable device). This may be the result of an initial connection, or it may be based on whether the UT exceeds a geographic boundary (geo-fencing) or based on whether an error limit has been exceeded.

At block 2404, the user terminal (or other suitable device) generates a location message. In some aspects, the message may indicate the current location if the UT is stationary, or may display a motion vector if the UT is moving.

At block 2406, the user terminal (or other suitable device) sends a location message to the SNP.

25 is a diagram illustrating an example of a process 2500 for utilizing user terminal location information, in accordance with some aspects of the disclosure. Process 2500 may occur within a processing circuit that may be located in a SNP or some other suitable device (device). In some implementations, the process 2500 represents the operations performed by the SNP controller 250 of FIG. In some implementations, the process 2500 represents operations performed (e.g., by the processing circuit 3510) by the device 3500 of FIG. Of course, in various aspects within the context of the disclosure, the process 2500 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2502, the SNP (or other suitable device) receives a location message from the user terminal. This location message includes user terminal location information.

At block 2504, the SNP (or other suitable device) generates satellite handoff information based in part on the user terminal location information. For example, if the UT is stationary, the SNP may generate a table or portion of the table based on the current UT location. As another example, if the UT is moving, the SNP may generate a table (or portion) based on the UT motion vector.

26 is a diagram illustrating an example of a user terminal handoff process 2600, in accordance with some aspects of the disclosure. Process 2600 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 2600 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 2600 represents operations performed (e.g., by the processing circuit 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, the process 2600 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2602, the user terminal handoff is encountered at the user terminal (or other suitable device). For example, the handoff may be displayed based on the satellite handoff information.

At block 2604, the user terminal (or other suitable device) measures satellite signals (e.g., signals from the satellites displayed in the satellite handoff information).

At block 2606, the user terminal (or other suitable device) determines whether to transmit a measurement message. In some aspects, this determination may involve determining whether signals from the current cell / beam and / or satellite are inappropriate, or whether signals from the target cell / beam and / or satellite are inadequate.

At block 2608, if applicable, the user terminal (or other suitable device) transmits a measurement message and receives new satellite handoff information. In some aspects, the message may include a request to advance / delay measurement data and / or handoff timing. Accordingly, in some aspects, the user terminal may send a measurement message based on the measured signals at block 2604, and may receive satellite handoff information as a result of transmitting the measurement message.

At block 2610, the user terminal (or other suitable device) handoffs to the target cell / beam and / or satellite in accordance with the satellite handoff information.

27 is a diagram illustrating an example of a SNP handoff process 2700, in accordance with some aspects of the disclosure. Process 2700 may occur within a processing circuit that may be located in a SNP or some other suitable device (device). In some implementations, the process 2700 represents the operations performed by the SNP controller 250 of FIG. In some implementations, the process 2700 represents operations performed (e.g., by the processing circuit 3510) by the device 3500 of FIG. Of course, in various aspects within the context of the disclosure, the process 2700 may be implemented by any suitable device capable of supporting communication-related operations.

At block 2702, the SNP (or other suitable device) receives a measurement message from the user terminal.

At block 2704, the SNP (or other suitable device) determines, based on the measurement message, whether to modify the satellite handoff information.

At block 2706, the SNP (or other suitable device), if applicable, modifies the satellite handoff information (e.g., advances or delays the transition timing) and sends the modified satellite handoff information to the user terminal .

At block 2708, the SNP (or other suitable device) handoffs the user terminal according to the satellite handoff information.

28 is a diagram illustrating another example of an inter-satellite handoff signaling process 2800, in accordance with some aspects of the disclosure. Process 2800 may occur within a processing circuit that may be located at a SNP, a user terminal, or some other suitable devices (devices). In some implementations, the process 2800 represents one or more operations performed by the SNP controller 280 of FIG. In some implementations, the process 2800 represents one or more operations performed by the control processor 420 of FIG. In some implementations, the process 2800 represents one or more operations performed (e.g., by the processing circuit 3510) by the apparatus 3500 of FIG. In some implementations, the process 2800 represents one or more operations performed by the device 3800 of FIG. 38 (e.g., by the processing circuit 3810). Of course, in various aspects within the context of the disclosure, the process 2800 may be implemented by any suitable devices capable of supporting communications-related operations.

At block 2802, the user terminal (or other suitable device) connects to the first satellite controlled by the first NAC at the SNP.

At block 2804, a handoff of the user terminal (or other suitable device) to the second satellite controlled by the second NAC at the SNP is indicated.

At block 2806, the second NAC (or other suitable device) generates satellite handoff information for the user terminal.

At block 2808, the second NAC (or other suitable device) transmits satellite handoff information to the first NAC.

At block 2810, the first NAC (or other suitable device) transmits satellite handoff information to the user terminal.

At block 2812, the user terminal (or other suitable device) is handed off to the second satellite in accordance with the satellite handoff information.

FIG. 29 is a diagram illustrating an example of a process 2900 for signaling ephemeris information, in accordance with some aspects of the disclosure. Process 2900 may occur within a processing circuit that may be located at a SNP, a user terminal, or some other suitable devices (devices). In some implementations, the process 2900 represents one or more operations performed by the SNP controller 250 of FIG. In some implementations, the process 2900 represents one or more operations performed by the control processor 420 of FIG. In some implementations, the process 2900 represents one or more operations performed (e.g., by the processing circuitry 3510) by the apparatus 3500 of FIG. In some implementations, the process 2900 represents one or more operations performed (e.g., by the processing circuit 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, the process 2900 may be implemented by any suitable devices capable of supporting communication-related operations.

At block 2902, the SNP (or other suitable device) sends this information to the user terminal.

At block 2904, the user terminal (or other suitable device) receives e-mail information.

At block 2906, the user terminal (or other suitable device) uses ephesemis information to synchronize with the satellite.

30 is a diagram illustrating an example of a radio link failure process 3000, in accordance with some aspects of the disclosure. Process 3000 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 3000 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 3000 represents operations performed (e.g., by the processing circuit 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, the process 3000 may be implemented by any suitable device capable of supporting communication-related operations.

At block 3002, the user terminal (or other suitable device) loses connectivity to the cell / beam or satellite.

At block 3004, the user terminal (or other suitable device) enters a radio link failure mode.

At block 3006, the user terminal (or other suitable device) identifies an alternative cell / beam and / or satellite (e.g., based on e-pharmace information stored at the user terminal).

At block 3008, the user terminal (or other suitable device) establishes a connection using an alternative cell / beam and / or satellite.

At block 3010, the user terminal (or other suitable device) communicates with the SNP through a new connection.

At block 3012, the user terminal (or other suitable device) exits the radio link failure mode.

31 is a diagram illustrating an example of a measurement gap-related process 3100, in accordance with some aspects of the disclosure. Process 3100 may occur within a processing circuit that may be located in a SNP or some other suitable device (device). In some implementations, the process 3100 represents the operations performed by the SNP controller 250 of FIG. In some implementations, the process 3100 represents operations performed (e.g., by the processing circuit 3510) by the device 3500 of FIG. Of course, in various aspects within the context of the disclosure, the process 3100 may be implemented by any suitable device capable of supporting communication-related operations.

At block 3102, the SNP (or other suitable device) determines whether the measurement gap is needed to measure satellite signals.

At block 3104, if a measurement gap is not needed, the SNP (or other suitable device) does not include a tune-away time within the satellite handoff information.

At block 3106, if a measurement gap is required, the SNP (or other suitable device) determines the measurement gap that should be used to measure the satellite signals.

At block 3108, the SNP (or other suitable device) sends information indicative of the measurement gap to the user terminal.

32 is a diagram illustrating an example of a measurement gap-related process 3200, in accordance with some aspects of the disclosure. Process 3200 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 3200 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 3200 represents operations performed (e.g., by the processing circuit 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, the process 3200 may be implemented by any suitable device capable of supporting communication-related operations.

At block 3202, the user terminal (or other suitable device) receives information indicative of a measurement gap for measuring satellite signals (e.g., from a SNP).

At block 3204, the user terminal (or other suitable device) measures signals from at least one satellite during a measurement gap (indicated by the received information).

33 is a diagram illustrating an example of a user queue process 3300, in accordance with some aspects of the disclosure. Process 3300 may occur within a processing circuit that may be located in a SNP or some other suitable device (device). In some implementations, the process 3300 represents the operations performed by the SNP controller 250 of FIG. In some implementations, process 3300 represents operations performed by device 3500 (e.g., by processing circuitry 3510) of FIG. Of course, in various aspects within the context of the disclosure, process 3300 may be implemented by any suitable device capable of supporting communication-related operations.

At block 3302, the SNP (or other suitable device) determines the time of handoff of the user terminal.

At block 3304, the SNP (or other suitable device) delivers at least one user queue prior to handoff.

34 is a diagram illustrating an example of a random access process 3400, in accordance with some aspects of the disclosure. Process 3400 may occur within a processing circuit that may be located at a user terminal or some other suitable device (device). In some implementations, the process 3400 represents the operations performed by the control processor 420 of FIG. In some implementations, the process 3400 represents operations performed (e.g., by the processing circuit 3810) by the device 3800 of FIG. Of course, in various aspects within the context of the disclosure, process 3400 may be implemented by any suitable device capable of supporting communication-related operations.

At block 3402, the user terminal (or other suitable device) receives a dedicated preamble signature (e.g., the UT receives a dedicated preamble signature from the SNP in control channel order).

At block 3404, the user terminal (or other suitable device) performs a non-contention-based random access procedure using a dedicated preamble signature.

An example device

35 illustrates a block diagram of an example hardware implementation of an apparatus 3500 configured to communicate, according to one or more aspects of the disclosure. For example, device 3500 may embody or be implemented within a SNP or some other type of device that supports satellite communications. Accordingly, in some aspects, apparatus 3500 may be an example of SNP 200 or SNP 201 in FIG. In various implementations, the device 3500 may embody or be embodied in any other electronic device having a gateway, a ground station, a vehicle component, or a circuitry.

The device 3500 includes a communication interface (e.g., at least one transceiver) 3502, a storage medium 3504, a user interface 3506, a memory device (e.g., memory circuit) 3508, 3510 < / RTI > In various implementations, the user interface 3506 may include one or more of a keypad, a display, a speaker, a microphone, a touch screen display, or some other circuitry for receiving input from or transmitting output to a user.

These components may be coupled to one another and / or arranged to communicate electrically with each other via a signaling bus or other suitable component represented generally by the connection lines in FIG. The signaling bus may include any number of interconnecting busses and bridges in accordance with the particular application of the processing circuitry 3510 and overall design constraints. The signaling bus is used to communicate with the processing circuitry 3510 and / or electrically communicate with the processing circuitry 3510, each of the communication interface 3502, the storage medium 3504, the user interface 3506, and the memory device 3508, To link various circuits together. The signaling bus may also be used to link various other circuits (not shown), such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described any further have.

Communication interface 3502 provides a means for communicating with other devices on the transmission medium. In some implementations, communication interface 3502 includes circuitry and / or programming adapted to enable communication of information in both directions to one or more communication devices in the network. In some implementations, communication interface 3502 is provided to enable wireless communication of device 3500. In these implementations, communication interface 3502 may be coupled to one or more antennas 3512, as shown in FIG. 35, for wireless communication within a wireless communication system. The communication interface 3502 may comprise one or more stand-alone receivers and / or transmitters, as well as one or more transceivers. In the illustrated example, the communication interface 3502 includes a transmitter 3514 and a receiver 3516. Communication interface 3502 serves as an example of means for receiving and / or means for transmitting.

Memory device 3508 may represent one or more memory devices. As indicated, the memory device 3508 may maintain satellite-related information 3518, along with other information used by the device 3500. In some implementations, memory device 3508 and storage medium 3504 are implemented as a common memory component. The memory device 3508 may also be used to store data manipulated by the processing circuitry 3510 of the device 3500 or some other component.

Storage medium 3504 may include one or more computer-readable, machine-readable, readable media for storing programming, electronic data, databases, or other digital information, such as processor executable code or instructions (e.g., And / or processor-readable devices. The storage medium 3504 may also be used to store data manipulated by the processing circuitry 3510 when performing programming. The storage medium 3504 can be any or all of the following: portable or non-removable storage devices, optical storage devices, and any other that may be accessed by a general purpose or special purpose processor, including various other mediums capable of storing, ≪ / RTI >

By way of example, and not limitation, storage medium 3504 can be a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD) or digital versatile disk (DVD) Readable memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory device (e.g., , A register, a removable disk, and any other suitable medium for storing software and / or instructions that may be accessed and read by the computer. The storage medium 3504 may be embodied in an article of manufacture (e.g., a computer program product). By way of example, the computer program product may comprise a computer-readable medium of packaging materials. Given the above, in some implementations, the storage medium 3504 may be a non-transitory (e.g., type) storage medium.

The storage medium 1404 may be coupled to the processing circuitry 3510 such that the processing circuitry 3510 can read information from and store information to the storage medium 3504. That is, storage medium 3504 can be coupled to processing circuitry 3510 such that storage medium 3504 is at least accessible by processing circuitry 3510, which allows at least one storage medium to be coupled to processing circuitry 3510 (E.g., resident in device 3500, external to device 3500, distributed across multiple entities, etc.) from processing circuitry 3510. In one embodiment, Examples.

The programming stored by the storage medium 3504 causes the processing circuit 3510 to perform one or more of the various functions and / or process operations described herein when executed by the processing circuitry 3510. [ For example, storage medium 3504 may be configured to utilize communication interface 3502 for wireless communication using its respective communication protocols, as well as for coordinating operations in one or more hardware blocks of processing circuitry 3510 And < / RTI >

Processing circuitry 3510 is generally provided for processing involving the execution of such programming stored on storage medium 3504. As used herein, the terms "code" or "programming" refer to instructions, instruction sets, data, code, code, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, Programs, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, But are not to be construed as limiting the scope of the present invention.

The processing circuit 3510 is arranged to acquire, process, and / or transmit data, control data access and storage, issue commands, and control other desired operations. The processing circuitry 3510 may include circuitry configured to implement the desired programming provided by suitable media in at least one example. For example, the processing circuitry 3510 may be implemented as one or more processors, one or more controllers, and / or other structures configured to execute executable programming. Examples of the processing circuitry 3510 include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array field programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may include any conventional processor, controller, microcontroller, or state machine as well as a microprocessor. The processing circuit 3510 may also be implemented as a combination of computing components, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, an ASIC and a microprocessor, May be implemented as configurations. These examples of processing circuit 3510 are for illustration purposes, and other suitable configurations within the scope of the disclosure are also contemplated.

According to one or more aspects of the disclosure, the processing circuitry 3510 may include any of the features, processes, functions, operations, and / or routines for any or all of the devices described herein Or all of them. For example, the processing circuitry 3510 may be implemented as described with respect to Figures 7, 8, 11 through 20, 23, 25, 27 through 29, 31, 33, 36, May be configured to perform one or more of the steps, functions, and / or processes. As used herein, the term " comprising " in connection with processing circuitry 3510 is intended to encompass various types of processing circuitry, including, but not limited to, processing circuitry 3510 configured to perform particular processes, functions, operations, and / or routines in accordance with various features described herein Employed, implemented, and / or programmed in accordance with the present invention.

Processing circuitry 3510 may include one of the operations described with reference to Figures 7, 8, 11 to 20, 23, 25, 27 to 29, 31, 33, 36, May be a specialized processor, such as an application specific integrated circuit (ASIC), which acts as a means (e.g., a structure for it) to perform the above. The processing circuit 3510 serves as an example of a means for transmitting and / or means for receiving. In some implementations, the processing circuitry 3510 incorporates the functionality of the SNP controller 250 of FIG.

In accordance with at least one example of an apparatus 3500, a processing circuit 3510 includes a circuit / module 3520 for generating, a circuit / module 3522 for transmitting, a circuit / module 3524 for performing handoffs, A circuit / module 3526 for selecting a time, a circuit / module 3528 for selecting a time, a circuit / module 3526 for selecting a circuit / May include one or more of circuit / module 3534, circuit / module 3536 for determining a measurement gap, or circuit / module 3538 for determining that a measurement gap is not needed. In various implementations, circuit / module 3520 for generating, circuit / module 3522 for transmitting, circuit / module 3524 for performing handoffs, circuit / module 3526 for receiving, Module 3532 for selecting a time, circuit / module 3535 for determining time, circuit / module 3535 for determining whether a measurement gap is to be determined, / RTI > circuit / module 3536 for determining a measurement gap, or circuit / module 3538 for determining that a measurement gap is not needed, may correspond at least in part to the SNP controller 250 of FIG.

The circuit / module 3520 for generating includes, for example, a satellite that specifies the time to start and end the communication with a particular cell of a particular satellite, and the satellite and cell transition information associated with generating the cell transition information And may include circuitry and / or programming (e.g., code 3540 for generating stored on storage medium 3504), which are adapted to perform some functions. In some implementations, circuit / module 3520 for generating calculates information (e.g., data for Table 1) based on satellite ephemeris data and user terminal location data. Module 3520 for generating and processing the data to generate the information and sending the information to a component of device 3500 (e.g., memory device 3508) do. For example, for a given location of a user terminal, a circuit / module 3520 for generating, based on the location of the satellite and the directionality and coverage of the cells of the satellite over time, It is possible to determine when to provide coverage for the terminal.

The circuitry / module 3522 for transferring may include circuitry and / or programming (e.g., storage medium 3540), such as those provided to perform some functions related to, for example, transferring information (e.g., data) (E.g., code 3542 for transmission stored on the network). Initially, the circuit / module 3522 for transfer obtains information to be transferred (e.g., from the memory device 3508, the circuit / module 3520 for generating, or some other component). In various implementations, the information to be transmitted may include satellite and cell transition information to be transmitted to the user terminal. In various implementations, the information to be transmitted may include information indicating a measurement gap. The circuit / module for transmission 3522 may then format the information for transmission (e.g., by message, protocol, etc.). Next, the circuit / module 3522 for transmitting causes information to be transmitted over the wireless communication medium (e.g., via satellite signaling). For this purpose, circuit / module 3522 for transmission may transmit data to communication interface 3502 (e.g., a digital subsystem or an RF subsystem) or some other component for transmission. In some implementations, communication interface 3502 includes circuitry / module 3522 for transmission and / or code 3542 for transmission.

The circuitry / module 3524 for performing handoffs may include circuitry and / or software, such as, for example, to perform some functions related to performing handoffs for user terminals to different cells and at least one satellite, (E.g., code 3544 for performing a handoff stored on storage medium 3504). In some implementations, circuit / module 3524 for performing handoff identifies the target satellite and / or target cell based on satellite and cell transition information (e.g., Table 1). For this purpose, the circuit / module 3524 for performing the handoff collects this information, processes the information to identify the target, and communicates the communication parameters Lt; / RTI > For example, for a given location of a user terminal, a circuit / module 3524 for performing handoff may be configured to determine the location of a particular satellite based on the location of the satellite and the directionality and coverage of the cells of the satellite over time It may be determined whether the cell will provide sufficient coverage for the user terminal. If the satellite / cell provides sufficient coverage, the circuit / module 3524 for performing the handoff may designate the satellite / cell as the target for handoff, and thus may initiate handoff signaling.

The circuitry / module 3526 for receiving may include circuitry and / or programming (e.g., storage medium 3540), such as, for example, (E. G., Code 3546 for reception stored on the < / RTI > In various implementations, the information to be received may include a measurement message from the user terminal. In various implementations, the information to be received may include capability information from the user terminal. In various implementations, the information to be received may include a message from the user terminal. Initially, a circuit / module 3526 for receiving acquires the received information. For example, the circuit / module 3526 for receiving may be a component of the device 3500 (e.g., a communication interface 3502 (e.g., a digital subsystem or RF subsystem), a memory device 3508, ), Or directly from a device (e.g., satellite) that relayed information from the user terminal. In some implementations, the circuit / module for receiving 3526 identifies the memory location of the value in memory device 3508 and invokes a read of the location. In some implementations, circuitry / module for receiving 3526 processes (e.g., decodes) the received information. The circuit / module for receiving 3526 outputs the received information (e.g., stores information received within memory device 3508, or transmits information to another component of device 3500). In some implementations, communication interface 3502 includes circuitry / module 3526 for receiving and / or code 3542 for receiving.

The circuit / module 3528 for determining whether or not to modify the circuitry and / or programming (e. G., Storage medium 3528) is configured to perform some functions related to determining whether to modify satellite and cell transition information, (E.g., code 3548 for determining whether to modify stored on memory 3504). In some implementations, the circuit / module 3528 for determining whether to modify will make this determination based on the received measurement message. For this purpose, circuit / module 3528 for determining whether to modify (e.g., from circuit / module 3526 for receiving, memory device 3508, or some other component of device 3500) Collect measurement message information. The circuit / module 3528 for determining whether to modify is then used to determine whether the current timing parameters need to be modified (e.g., due to poor RF conditions or improved RF conditions) Lt; / RTI > For example, circuit / module 3528 for determining whether to modify may compare the signal quality information included in the measurement message with one or more signal quality thresholds. Finally, the circuit / module 3528 for determining whether to modify (e.g., indicating the advance of the handoff, or the delay of the handoff) generates an indication of this determination.

The circuit / module 3530 for selecting may include circuitry and / or programming adapted to perform some of the functions associated with, for example, a handoff procedure for a user terminal (e.g., Code 3550). In some implementations, the circuit / module for selection 3530 makes this determination based on capability information received from the user terminal. For this purpose, a circuit / module for selection 3530 collects this capability information, processes the information to identify the handoff procedure, and generates an indication of this determination. For example, the selection of the handoff procedure may include determining whether the user terminal is dual-detectable, enabling or disabling monitoring of the measurement message from the user terminal based on whether the user terminal is dual- . Thus, in some implementations, circuit / module 3530 for selection may obtain configuration information for the user terminal (e.g., from memory device 3508, from receiver 3516, or some other component) (E.g., memory device 3508, circuitry / module 3524 for performing handoffs, or some other component) to identify the capability of the user terminal to select a supported handoff procedure To be transmitted).

The circuit / module 3532 for determining the time may be implemented on circuitry and / or programming (e.g., on storage medium 3540), such as, for example, (E.g., code 3552 for determining the time stored in memory). In some implementations, circuit / module 3532 for determining time makes this determination based on satellite and cell transition information (e.g., Table 1). For this purpose, the circuit / module 3532 for determining the time (e.g., from the circuit / module 3526 for receiving, the memory device 3508, or some other component of the device 3500) . The circuit / module 3532 for determining the time may then process the information to determine the time (e.g., frame number) for the next handoff of the user terminal. For example, the circuit / module 3532 for determining the time may compare the current time representation (e.g., frame number) with the timing indications in Table 1. The circuit / module 3532 for determining the time generates an indication of this decision (e.g., indicating the time of the handoff) and sends the indication to the component (e.g., circuit / module 3534 ), Memory device 3508, or some other component).

The circuitry / module 3534 for delivery may be implemented as circuitry and / or programming (e. G., Stored on storage medium 3540), which is configured to perform some functions related to delivering user queues prior to handoff, for example. (Code 3554 for < / RTI > Initially, circuit / module 3534 for delivery receives an indication of the time of handoff (e.g., from memory device 3508, circuit / module 3532 for determining time, or some other component). Next, prior to the time of the handoff, the circuit / module 3534 for delivery obtains the queue information to be transmitted (e.g., from the memory device 3508, or some other component). In various implementations, this information may be sent to another SNP. The circuit / module 3534 for delivery may then format the queue information for transmission (e.g., by message, protocol, etc.). Next, the circuit / module 3534 for delivery causes the queue information to be transmitted over an appropriate communication medium (e.g., via infrastructure 106 of FIG. 1). For this purpose, the circuit / module for transferring 3534 may transmit data to the communication interface 3502 or some other component for transmission. In some implementations, communication interface 3502 includes circuitry / module 3534 for communicating and / or code 3554 for communicating.

The circuit / module 3536 for determining the measurement gap may include circuitry and / or programming (e.g., storage medium 3504) configured to perform some functions related to determining a measurement gap for measuring satellite signals, for example, (E.g., code for determining the measurement gap 3556 stored on the substrate). In some implementations, circuit / module 3536 for determining a measurement gap determines that there may be a satellite pointing error that requires a change in handoff time. As a result of this decision or some other trigger, circuit / module 3536 for determining the measurement gap may be used to indicate an indication of the measurement gap to be used by the UT (e.g., a measurement gap Pattern). The circuit / module 3536 for determining the measurement gap may then send the indication to a component of the device 3500 (e.g., circuit / module 3522 for transfer, memory device 3508, or some other component) send.

The circuit / module 3538 for determining that a measurement gap is not needed may be implemented by, for example, circuitry and / or circuitry arranged to perform some functions related to determining that the measurement gap is not needed for measuring satellite signals, And may include programming (e.g., code 3558 stored on storage medium 3504 to determine that a measurement gap is not needed). In some implementations, circuit / module 3538 for determining that a measurement gap is not needed acquires information about the status of one or more satellites. Based on this information, circuit / module 3538 for determining that a measurement gap is not needed determines that there is no satellite pointing error that would require a change in handoff time. The circuit / module 3538 for determining that a measurement gap is not needed, as a result of this determination or some other trigger, generates an indication of this determination and sends an indication to the component of device 3500 (e.g., / Module 3520, memory device 3508, or some other component).

As noted above, the programming stored by the storage medium 3504 can be used by the processing circuitry 3510 to cause the processing circuitry 3510 to perform one or more of the various functions and / or process operations described herein . For example, programming may be performed by processing circuitry 3510, when executed by processing circuitry 3510, in various implementations, such as in Figures 7, 8, 11 to 20, 23, 25, Steps, and / or processes described herein with reference to FIGS. 29, 31, 33, 36, and 37. FIG. 35, storage medium 3504 includes code 3540 for generating, code 3542 for transmitting, code 3544 for performing handoffs, code 3546 for receiving, A code 3555 for determining whether a measurement is to be performed, a code 3552 for determining whether a measurement is to be performed, a code 3552 for selecting, a code 3552 for determining a time, a code 3554 for delivering, a code 3556 for determining a measurement gap, And code 3558 for determining that a gap is not needed.

One example process

Figure 36 illustrates a process 3600 for communication, in accordance with some aspects of the disclosure. Process 3600 may occur within a processing circuit (e.g., processing circuitry 3510 of FIG. 35) that may be located in a SNP or some other suitable device. In some implementations, the process 3600 may be performed by a SNP for at least one non-geostationary satellite. In some implementations, the process 3600 represents the operations performed by the SNP controller 250 of FIG. Of course, in various aspects within the context of the disclosure, the process 3600 may be implemented by any suitable device capable of supporting communications operations.

At block 3602, the device (e.g., the SNP) generates satellite handoff information that specifies the handoff time for a particular cell of a particular satellite. In some aspects, the operations of block 3602 may correspond to the operations of block 2006 of FIG.

In some aspects, the generation of the satellite handoff information may be based on at least one of capabilities information for the user terminal, or location information for the user terminal. In some aspects, capabilities information may indicate at least one of whether the user terminal is capable of sensing multiple cells, or whether the user terminal is capable of sensing multiple satellites. In some aspects, the capabilities information may indicate at least one of an inter-beam tune time for a user terminal, or an inter-satellite tune time for a user terminal have. In some aspects, the location information may include at least one of a current location for the user terminal, or a motion vector for the user terminal.

In some aspects, the generation of satellite handoff information may be based on at least one of ephemeris information, limitation due to the current system, or satellite pointing error. In some aspects, the generation of satellite handoff information may be triggered based on at least one of handoff of the user terminal to a different satellite, or reception of a measurement message from the user terminal.

In some implementations, the circuit / module 3520 for generating in FIG. 35 performs the operations of block 3602. FIG. In some implementations, the code for generating 3540 of FIG. 35 is executed to perform the operations of block 3602. [

At block 3604, the device sends satellite handoff information to the user terminal. In some aspects, this information is transmitted over satellites. In some aspects, the operations of block 3604 may correspond to the operations of block 2008 of FIG.

The satellite handoff information may take various forms as taught herein. In some aspects, the satellite handoff information may include a table that includes a handover activation time. In some aspects, the satellite handoff information may include at least one tune-away time. In some aspects, the handoff information may be for at least one future handoff (e.g., a next handoff, a further handoff, or some other handoff that may occur in the future). In some aspects, the handoff information may be for a next beam handoff and may include at least one future satellite handoff (e.g., for the next two handoffs to occur, the next handoff and some other future handoffs) Off, etc.).

In some implementations, the circuit / module 3522 for transmission of FIG. 35 performs the operations of block 3604. In some implementations, the code for sending 3542 of FIG. 35 is executed to perform the operations of block 3604.

In some aspects, process 3600 may further comprise performing handoffs for user terminals to different beams and at least one satellite based on satellite handoff information. The handoffs may involve a change of at least one of a satellite access network (SAN) or a satellite network portal (SNP) antenna. The handoffs may involve a change of at least one of a satellite beam or a forward service link (FSL) frequency. In some aspects, these operations may correspond to the operations of block 2010 of FIG. In some implementations, the circuit / module 3524 for performing the handoff of FIG. 35 performs these operations. In some implementations, code 3544 for performing the handoff of FIG. 35 is executed to perform these operations.

In some aspects, the process 3600 may further comprise receiving a measurement message from the user terminal and determining, based on the measurement message, whether to modify the satellite handoff information. Modification of the satellite handoff information may include advancing the handoff timing, or delaying the handoff timing. In some aspects, these operations may correspond to the operations of blocks 2702 and 2704 of FIG. In some implementations, the receiving circuit / module 3526 of Fig. 35 performs receiving operations. In some implementations, the receive code 3546 of FIG. 35 is executed to perform receive operations. In some implementations, circuit / module 3528 for determining whether to modify in FIG. 35 performs decision operations. In some implementations, the code 3548 for determining whether to modify the Figure 35 is executed to perform the determining operations.

In some aspects, the process 3600 may further comprise determining a measurement gap for measuring satellite signals and transmitting information indicative of the measurement gap to the user terminal, wherein the measurement message is transmitted during a measurement gap And an indication of a measurement of signals from at least one satellite performed. In some aspects, these operations may correspond to the operations of blocks 3106 and 3108 of FIG. In some implementations, the circuit / module 3536 for determining the measurement gap of Figure 35 performs decision operations. In some implementations, code 3556 for determining the measurement gap in Figure 35 is executed to perform the determination operations. In some implementations, the circuit / module 3522 for transfer of FIG. 35 performs the transfer operations. In some implementations, the code 3542 for transfer of FIG. 35 is executed to perform transfer operations.

In some aspects, the process 3600 may further comprise receiving capability information from the user terminal and selecting a handoff procedure for the user terminal based on the received capability information. The capability information may indicate whether the user terminal is dual-detectable. The selection of the handoff procedure may include enabling or disabling monitoring of the measurement message from the user terminal based on whether the user terminal is dual detectable. In some aspects, these operations may correspond to the operations of blocks 2302 and 2306 of FIG. In some implementations, the receiving circuit / module 3526 of Fig. 35 performs receiving operations. In some implementations, the receive code 3546 of FIG. 35 is executed to perform receive operations. In some implementations, the circuit / module 3530 for selecting in FIG. 35 performs the selection operations. In some implementations, the select code 3550 of FIG. 35 is executed to perform select operations.

In some aspects, the process 3600 may further comprise determining a time of handoff of the user terminal and communicating at least one user queue prior to handoff. In some aspects, these operations may correspond to the operations of blocks 3302 and 3304 of FIG. In some implementations, the circuit / module 3532 for determining the time of Figure 35 performs decision operations. In some implementations, code 3552 for determining the time of Figure 35 is executed to perform the decision operations. In some implementations, the circuit / module 3534 for transfer of FIG. 35 performs propagation operations. In some implementations, the forwarding code 3554 of FIG. 35 is executed to perform forwarding operations.

In some aspects, the process 3600 may further comprise receiving, from a user terminal, a message comprising at least one of user terminal paging area information or user terminal location information. In some aspects, these operations may correspond to the operations of block 2502 of Fig. In some implementations, the circuit / module 3526 for receiving in FIG. 35 performs these operations. In some implementations, the receive code 3546 of Fig. 35 is executed to perform these operations.

In some aspects, the process 3600 may further comprise determining that the measurement gap is not needed to measure the satellite signals, wherein, as a result of the determination, the generation of the satellite hand- Lt; RTI ID = 0.0 > tune-away < / RTI > In some aspects, these operations may correspond to the operations of blocks 3102 and 3104 of FIG. In some implementations, the circuit / module 3538 for determining that the measurement gap of Figure 35 is not needed performs these operations. In some implementations, code 3558 for determining that the measurement gap of Figure 35 is not needed is executed to perform these operations.

Figure 37 illustrates a process 3700 for communication, in accordance with some aspects of the disclosure. Process 3700 may occur within a processing circuit (e.g., processing circuit 3510 of FIG. 35) that may be located in a SNP or some other suitable device. In some implementations, the process 3700 may be performed by a SNP for at least one non-geostationary satellite. In some implementations, the process 3700 represents the operations performed by the SNP controller 250 of FIG. Of course, in various aspects within the context of the disclosure, process 3700 may be implemented by any suitable device capable of supporting communications operations.

At block 3702, a device (e.g., a SNP) generates satellite and cell transition information that specifies the time to start and end the communication with a particular cell of a particular satellite. In some aspects, the operations of block 3702 may correspond to the operations of block 2006 of Fig.

In some aspects, the satellite and cell transition information is generated based on at least one of capabilities for user terminal, location information for user terminal, ephemeris information, or restriction due to the current system. In some aspects, capabilities information may include whether the user terminal is capable of sensing multiple cells, whether the user terminal is capable of sensing multiple satellites, the inter-cell tune time for the user terminal, And at least one of inter-satellite tune times. In some aspects, the location information includes the current location for the user terminal, or the motion vector for the user terminal.

In some aspects, the generation of satellite and cell transition information is triggered based on at least one of handoff of the user terminal to a different satellite, or reception of a measurement message from the user terminal.

In some implementations, the circuit / module 3520 for generating in FIG. 35 performs the operations of block 3702. In some implementations, the code 3540 for generating in Figure 35 is executed to perform the operations of block 3702. [

At block 3704, the device transmits satellite and cell transition information to the user terminal. In some aspects, this information is transmitted over satellites. In some aspects, the operations of block 3704 may correspond to the operations of block 2008 of Fig.

In some implementations, the circuit / module 3522 for transmission of FIG. 35 performs the operations of block 3704. In some implementations, the code for sending 3542 of Fig. 35 is executed to perform the operations of block 3704.

In some aspects, process 3700 further includes performing handoffs for user terminals to different cells and at least one satellite based on satellite and cell transition information. In some aspects, these operations may correspond to the operations of block 2010 of FIG. In some implementations, the circuit / module 3524 for performing the handoff of FIG. 35 performs these operations. In some implementations, code 3544 for performing the handoff of FIG. 35 is executed to perform these operations.

In some aspects, process 3700 includes receiving a measurement message from a user terminal; And determining whether to modify the satellite and cell transition information based on the measurement message. In some aspects, modification of the satellite and cell transition information includes advancing the handoff, or delaying the handoff. In some aspects, these operations may correspond to the operations of blocks 2702 and 2704 of FIG. In some implementations, circuit / module 3526 for receiving and / or circuit / module 3528 for determining whether to modify, in FIG. 35, perform these operations. In some implementations, the code for receiving 3546 in FIG. 35 and / or code 3548 for determining whether to modify is executed to perform these operations.

In some aspects, the process 3700 further includes selecting a handoff procedure for the user terminal based on capability information received from the user terminal. In some aspects, the selection of the handoff procedure includes enabling or disabling monitoring for a measurement message from the user terminal based on whether the user terminal is dual-detectable. In some aspects, these operations may correspond to the operations of block 2306 of FIG. In some implementations, the circuit / module 3530 for selecting in FIG. 35 performs these operations. In some implementations, the select code 3550 of FIG. 35 is executed to perform these operations.

In some aspects, the process 3700 further comprises determining a time of handoff of the user terminal and communicating user queues prior to handoff. In some implementations, circuit / module 3532 for determining the time of Figure 35 and / or circuit / module 3534 for communicating perform these operations. In some implementations, the code 3552 for determining the time of Figure 35 and / or the code 3554 for communicating is executed to perform these operations.

An example device

38 illustrates a block diagram of an example hardware implementation of another apparatus 3800 configured to communicate, in accordance with one or more aspects of the disclosure. For example, device 3800 may embody or be implemented within a UT or some other type of device that supports wireless communication. Thus, in some aspects, the device 3800 may be an example of the UT 400 or UT 401 of FIG. In various implementations, the device 3800 may embody any other electronic device having a mobile phone, smart phone, tablet, portable computer, server, personal computer, sensor, entertainment device, vehicle component, medical device, Or may be implemented within.

The device 3800 includes a memory device 3808 (e.g., which stores satellite-related information 3818), a communication interface (e.g., at least one transceiver) 3802, a storage medium 3804, a user interface 3806, , And a processing circuit (e.g., at least one processor) 3810. In various implementations, the user interface 3806 may include one or more of a keypad, a display, a speaker, a microphone, a touch screen display, or some other circuitry for receiving input from a user or for transmitting an output to a user. Communications interface 3802 may be coupled to one or more antennas 3812 and may include a transmitter 3814 and a receiver 3816. [ Generally, the components of FIG. 38 may be similar to corresponding components of device 3500 of FIG.

According to one or more aspects of the disclosure, the processing circuitry 3810 may include any of the features, processes, functions, operations, and / or routines for any or all of the devices described herein Or all of them. For example, the processing circuitry 3810 may include one or more of the processing circuits 3810 and 3810 as shown in Figures 7, 8, 11 to 19, 21, 22, 24, 26, 28 to 30, 32, 34, 39, May be configured to perform one or more of the steps, functions, and / or processes described with respect to FIG. As used herein, the term " comprise " associated with processing circuitry 3810 is intended to encompass a wide variety of configurations and configurations in which processing circuitry 3810 is configured to perform particular processes, functions, operations, and / or routines in accordance with various features described herein. Employed, implemented, and / or programmed in accordance with the present invention.

The processing circuitry 3810 may be implemented in conjunction with any of the processing circuits 3810 in conjunction with Figures 7, 8, 11 to 19, 21, 22, 24, 26, 28 to 30, 32, 34, 39, May be a specialized processor, such as an application specific integrated circuit (ASIC), which acts as a means (e.g., a structure for it) to perform one or more of the described operations. The processing circuit 3810 serves as an example of a means for transmitting and / or means for receiving. In various implementations, the processing circuit 3810 may incorporate the functionality of the control processor 420 of FIG.

According to at least one example of the device 3800, the processing circuit 3810 includes a circuit / module 3820 for receiving, a circuit / module 3822 for performing handoff, a circuit / module A circuit / module 3826 for transmitting data, a circuit / module 3826 for transmitting, a circuit / module 3828 for determining whether to transmit, or a circuit / module 3830 for performing a random access procedure. Module 3822 for performing handoff, circuit / module 3824 for measuring signals, circuit / module 3826 for transmitting, a circuit / The circuit / module 3828 for determining whether to transmit a random access procedure, and the circuit / module 3830 for performing a random access procedure may at least partially correspond to the control processor 420 of FIG.

The circuit / module 3820 for receiving may include circuitry and / or programming (e.g., storage medium 3804), such as, for example, (E.g., code 3832 for receiving stored on the network). In various implementations, the information to be received may include satellite and cell transition information that specifies the time to start and end the communication with a particular cell of a particular satellite. In various implementations, the information to be received may include information indicating a measurement gap. In various implementations, the information to be received may include a dedicated preamble signature. Initially, the circuit / module 3820 for receiving acquires the received information. For example, circuit / module 3820 for receiving may obtain this information directly from a component of device 3800, or from a device (e.g., satellite) that has relayed information from the SNP. In the former case, the circuit / module 3820 for receiving may include a communication interface 3802 (e.g., a UT transceiver as described above for UT 400 in FIG. 4), a memory device 3808, Lt; / RTI > In some implementations, the circuit / module 3820 for receiving identifies the memory location of the value in the memory device 3808 and invokes a read of the location. In some implementations, the circuit / module 3820 for receiving processes (e. G., Decodes) the received information. The circuit / module 3820 for receiving (e.g., receiving the received information from memory device 3808, circuit / module 3822 for performing handoff, or some other Component). In some implementations, communication interface 3802 includes circuit / module 3820 for receiving and / or code 3832 for receiving.

Circuits / modules 3822 for performing handoffs include circuitry and / or programming (e. G., Storage media 3804 < RTI ID = 0.0 > (E.g., code 3834 for performing handoffs stored on the network). In some implementations, circuit / module 3822 for performing handoff identifies a particular cell of a particular satellite based on satellite and cell transition information (e.g., Table 1). For this purpose, the circuit / module 3822 for performing the handoff collects this information, processes the information to identify the satellite and the cell, and communicates with the SNP that should be done over the identified satellite and cell And reconfigures its communication parameters to cause it. For example, at a particular point in time, the circuit / module 3822 for performing a handoff may utilize the information in Table 1 to determine whether the user terminal should switch to a different satellite cell. As another example, the triggers may be set up at the cell / satellite transit times (e.g., frame numbers) shown in Table 1.

The circuit / module 3824 for measuring signals may include circuitry and / or programming (e.g., storage medium 3804, such as, for example, (E.g., code 3836 for measuring the signals stored on the receiver). Initially, circuit / module 3824 for measuring signals receives signals. For example, circuit / module 3824 for measuring signals may obtain signal information directly from a component of device 3800, or from a satellite that has transmitted signals. As an example of the former case, the circuit / module 3824 for measuring signals may include a communication interface 3802 (e.g., a UT transceiver as described above for UT 400 of FIG. 4) May obtain signaling information from memory device 3808, or some other component of device 3800 (if the signals have been digitized). The circuit / module 3824 for measuring signals then processes the received signals (e.g., to determine the signal quality of at least one of the signals). Finally, the circuit / module 3824 for measuring signals may be used to generate an indication of this measurement and to provide the indication to the memory device 3808, circuit / module 3824 for transfer, or some other component of the device 3800 Lt; / RTI > In some implementations, communication interface 3802 includes circuitry / module 3824 for measuring signals, and / or code 3836 for measuring signals.

The circuitry / module 3826 for transferring may include circuitry and / or programming (e.g., storage medium 3840), such as, for example, circuitry and / or code that is configured to perform some of the functions associated with, for example, (E.g., code 3838 for transmission stored on the network). Initially, a circuit / module 3826 for transmission obtains information to be transmitted (e.g., from memory device 3808, circuit / module 3824 for measuring signals, or some other component). In various implementations, the information to be transmitted may include a measurement message based on measured signals, a message including user terminal capability information, or a message including user terminal location information. In various implementations, the information to be transmitted may include a message including user terminal capability information. In various implementations, the information to be transmitted may include a message including user terminal location information. In various implementations, the information to be transmitted may include a message including user terminal paging area information. The circuit / module for sending 3826 may format the information for transmission (e.g., according to message format, protocol, etc.). The circuit / module 3826 for transmission then allows the information to be transmitted over the wireless communication medium (e.g., via satellite signaling). For this purpose, the circuit / module 3826 for transmitting may send data to a communications interface 3802 (e.g., a UT transceiver as described above for UT 400 in FIG. 4), or some other component . In some implementations, communication interface 3802 includes circuit 3836 for transmitting and / or code 3838 for transmitting.

The circuit / module 3828 for determining whether to transmit or not may include circuitry and / or programming (e.g., on storage medium 3804) to perform some functions related to determining whether to transmit a message, for example, (E.g., code 3840 for determining whether to modify, save, or not). In some implementations, the information to be transmitted may include a measurement message based on the measured signals. Initially, circuit / module 3828 for determining whether to transmit (e.g., to make a transfer decision), such as from memory device 3808, circuit / module 3824 for measuring signals, or some other component Obtain the information used. For example, circuit / module 3828 for determining whether to transmit may obtain signal quality information from circuit / module 3824 for measuring signals. In this case, the circuit / module 3828 for determining whether to transmit (e.g., comparing the signal quality information to the signal quality threshold) determines whether signals from the current serving satellite and / or the target satellite are inadequate You can decide. For example, transmission of a measurement message may be triggered when signals are inadequate. Finally, the circuit / module 3828 for determining whether to transmit will generate an indication of this decision and send the indication to the memory device 3808, the circuit / module 3826 for transmitting, or a part of the device 3800 To another component.

The circuit / module 3830 for performing the random access procedure may include circuitry and / or programming (e.g., circuitry and / or software) that is configured to perform some of the functions associated with performing a non-contention-based random access procedure using a dedicated preamble signature, (E.g., code 3842 for performing a random access procedure stored on storage medium 3804). In some implementations, the circuit / module 3830 for performing the random access procedure performs the random access operations described above in conjunction with FIG. In some implementations, the circuit / module 3830 for performing the random access procedure performs the random access operations described above in conjunction with FIG. In some implementations, the circuit / module 3830 for performing the random access procedure performs the random access operations described above in conjunction with FIG. In some implementations, the circuit / module 3830 for performing the random access procedure performs the random access operations described above in conjunction with FIG. In some implementations, the circuit / module 3830 for performing the random access procedure performs the operations described above in conjunction with FIG.

As noted above, the programming stored by the storage medium 3804 may be used by the processing circuitry 3810 to cause the processing circuitry 3810 to perform one or more of the various functions and / or process operations described herein . For example, programming may be performed by the processing circuit 3810, when executed by the processing circuit 3810, to cause the processing circuit 3810 to perform, in various implementations, the operations shown in Figures 7, 8, 11-19, 21, 22, Steps, and / or processes described herein with respect to FIGs. 26, 28, 30, 32, 34, 39, and 40. FIG. 38, storage medium 3804 includes code 3832 for receiving, code 3834 for performing handoffs, code 3836 for measuring signals, code 3838 for transmitting, , Code 3840 for determining whether to transmit, or code 3842 for performing a random access procedure.

One example process

Figure 39 illustrates a process 3900 for communication, in accordance with some aspects of the disclosure. Process 3900 may occur within a processing circuit (e.g., processing circuitry 3810 of FIG. 38) that may be located in a UT or some other suitable device. In some implementations, the process 3900 represents the operations performed by the control processor 420 of FIG. Of course, in various aspects within the context of the disclosure, the process 3900 may be implemented by any suitable device capable of supporting communications operations.

At block 3902, the device (e.g., UT) receives satellite handoff information that specifies a handoff time for a particular cell of a particular satellite. In some aspects, the operations of block 3902 may correspond to the operations of block 2104 of FIG.

The satellite handoff information may take various forms as taught herein. In some aspects, the satellite handoff information may include a table that includes a handover activation time. In some aspects, the satellite handoff information may include at least one tune-away time. In some aspects, the handoff information may be defined based in part on satellite pointing errors. In some aspects, the handoff information may be for at least one future handoff (e.g., a next handoff, a further handoff, or some other handoff that may occur in the future). In some aspects, the handoff information may be for a next beam handoff and may include at least one future satellite handoff (e.g., for the next two handoffs to occur, the next handoff and some other future handoffs) Off, etc.).

In some implementations, the circuit / module 3820 for receiving in FIG. 38 performs the operations of block 3902. In some implementations, the receive code 3832 of FIG. 38 is executed to perform the operations of block 3902. [

At block 3904, the device performs a handoff to a particular cell of a particular satellite based on the satellite handoff information. In some aspects, the operations of block 3904 may correspond to the operations of block 2106 of FIG.

In some aspects, the handoff may involve a change in at least one of a satellite access network (SAN), a satellite network portal (SNP) antenna, a satellite beam, or a forward service link (FSL) frequency.

In some implementations, the circuit / module 3822 for performing the handoff of FIG. 38 performs the operations of block 3904. In some implementations, the code 3834 for performing the handoff of FIG. 38 is executed to perform the operations of block 3904.

In some aspects, the process 3900 may further include measuring signals from at least one satellite and transmitting a measurement message based on the measured signals, wherein the satellite handoff information includes a measurement message Is received as a result of being transmitted. The measurement message may include at least one of measurement data based on the measured signals, a request to advance the handoff timing, or a request to delay the handoff timing. In some aspects, these operations may correspond to the operations of blocks 2604 and 2608 of Fig.

In some aspects, process 3900 may further comprise receiving information indicative of a measurement gap for measuring satellite signals, wherein measurements of signals from at least one satellite are made during a measurement gap. In some aspects, these operations may correspond to the operations of blocks 3202 and 3204 of FIG.

In some aspects, the process 3900 further includes determining whether to send a measurement message based on at least one of whether signals from the current serving satellite are inadequate, or whether signals from the target satellite are inadequate . In some aspects, these operations may correspond to the operations of block 2606 of FIG.

In some aspects, process 3900 may further comprise transmitting a message including user terminal capability information, wherein the received satellite handoff information is based on user terminal capability information. The user terminal capability information includes at least one of whether the user terminal can sense multiple beams, whether the user terminal can sense multiple satellites, the user terminal inter-beam tune time, or the user terminal inter- May be displayed. The transmission of a message containing user terminal capability information may be triggered as a result of an initial connection to the satellite. In some aspects, these operations may correspond to the operations of block 2206 of FIG.

In some aspects, process 3900 may further comprise transmitting a message comprising user terminal location information, wherein the received satellite handoff information is based on user terminal location information. The user terminal location information may include at least one of a current user terminal location or a user terminal motion vector. The transmission of a message containing user terminal location information may be triggered as a result of at least one of an initial connection to the satellite, whether the user terminal crosses a geographical boundary, or whether an error limit has been exceeded. In some aspects, these operations may correspond to the operations of block 2406 of FIG.

In some aspects, process 3900 may further comprise receiving a dedicated preamble signature and performing a non-contention-based random access procedure using a dedicated preamble signature. In some aspects, these operations may correspond to the operations of blocks 3402 and 3404 of Fig.

In some aspects, the process 3900 further includes determining whether to send a measurement message based on at least one of whether signals from the current serving satellite are inadequate, or whether signals from the target satellite are inadequate . In some aspects, these operations may correspond to the operations of block 2406 of FIG.

40 illustrates a process 4000 for communication, in accordance with some aspects of the disclosure. Process 4000 may occur within a processing circuit (e.g., processing circuit 3810 of FIG. 38) that may be located in a UT or some other suitable device. In some implementations, the process 4000 represents the operations performed by the control processor 420 of FIG. Of course, in various aspects within the context of the disclosure, the process 4000 may be implemented by any suitable device capable of supporting communications operations.

At block 4002, the device (e.g., UT) receives satellite and cell transition information specifying the time to start and end the communication with a particular cell of a particular satellite. In some aspects, the operations of block 4002 may correspond to the operations of block 2104 of FIG.

In some implementations, the circuit / module 3820 for receiving in FIG. 38 performs the operations of block 4002. In some implementations, the receive code 3832 of FIG. 38 is executed to perform the operations of block 4002. [

At block 4004, the device performs a handoff to a particular cell of a particular satellite based on satellite and cell transition information. In some aspects, the operations of block 4004 may correspond to the operations of block 2106 of FIG.

In some implementations, the circuit / module 3822 for performing the handoff of FIG. 38 performs the operations of block 4004. In some implementations, the code 3834 for performing the handoff of FIG. 38 is executed to perform the operations of block 4004.

In some aspects, the process 4000 includes measuring signals from at least one satellite; And transmitting a measurement message based on the measured signals, wherein the satellite and cell transition information is received as a result of transmitting the measurement message. In some aspects, the measurement message includes at least one of measurement data, a request to advance the handoff timing, or a request to delay the handoff timing. In some aspects, the process 4000 further comprises determining whether to send a measurement message based on at least one of whether signals from the current serving satellite are inadequate, or whether signals from the target satellite are inadequate . In some aspects, these operations may correspond to the operations of blocks 2604 through 2608 of FIG. In some implementations, circuit / module 3824 for measuring the signals of FIG. 38 and / or circuit / module 3828 for determining whether to transmit may perform these operations. In some implementations, code 3836 for measuring the signals of Figure 38 and / or code 3840 for determining whether to transmit is performed to perform these operations.

In some aspects, the process 4000 further comprises transmitting a message including user terminal capability information, wherein the satellite and cell transition information is based on user terminal capability information. In some aspects, the user terminal capability information includes whether the user terminal can sense multiple cells, whether the user terminal can sense multiple satellites, the user terminal inter-cell tune time, or the user terminal inter- And at least one of the tune times. In some aspects, the transmission of a message containing user terminal capability information is triggered as a result of an initial connection to the satellite. In some aspects, these operations may correspond to the operations of blocks 2202-2206 of FIG. In some implementations, circuit / module 3826 for transmitting in FIG. 38 performs these operations. In some implementations, the code 3838 for transfer of FIG. 38 is executed to perform these operations.

In some aspects, the process 4000 further comprises transmitting a message including user terminal location information, wherein the satellite and cell transition information is based on user terminal location information. In some aspects, the user terminal location information includes the current user terminal location or the user terminal motion vector. In some aspects, the transmission of the message including the user terminal location information is triggered as a result of at least one of an initial connection to the satellite, whether the user terminal crosses a geographical boundary, or whether an error limit has been exceeded. In some aspects, these operations may correspond to the operations of blocks 2402 through 2406 of FIG. In some implementations, circuit / module 3826 for transmitting in FIG. 38 performs these operations. In some implementations, the code 3838 for transfer of FIG. 38 is executed to perform these operations.

Additional aspects

A number of aspects are described in terms of, for example, sequences of actions to be performed by elements of a computing device. The various actions described herein may be performed in conjunction with specific circuits, such as, for example, central processing units (CPUs), graphics processing units (GPUs), digital signal processors , Application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or various other types of general purpose or special purpose processors or circuits, one or more processors Or by a combination of both. ≪ RTI ID = 0.0 > Additionally, this sequence of actions described herein may be implemented in any form of computer readable storage medium having stored thereon a corresponding set of computer instructions for causing an associated processor to perform the functionality described herein, It can be considered to be fully embodied within the scope of the present invention. Accordingly, various aspects of the disclosure may be embodied in many different forms, all of which are contemplated as being within the scope of the claimed subject matter. In addition, for each of the aspects described herein, any corresponding form of such aspects may be described herein as " configured logic " to perform, for example, the described actions.

Those skilled in the art will recognize that information and signals 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 refer to voltages, currents, electromagnetic waves, , Optical fields or particles, or any combination thereof.

Those skilled in the art will also appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both ≪ / RTI > In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

The methods, sequences, or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium is coupled to the processor such that the processor can read information from the storage medium and write the information to the storage medium. Alternatively, the storage medium may be integral to the processor.

Thus, one aspect of the disclosure may include a computer readable medium embodying a method for time or frequency synchronization in non-geostationary satellite communication systems. Accordingly, the disclosure is not limited to the illustrated examples, and any means for performing the functionality described herein are encompassed within aspects of the disclosure.

The word " exemplary " is used herein to mean " serving as an example, instance, or illustration. &Quot; Any aspect described herein as " exemplary " is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term " aspects " does not require all aspects to include the features, advantages, or modes of operation discussed.

The terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting of the aspects. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms comprise, " comprise, " " include, " or " including, " when used in this specification, , Elements, or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof, It will be understood. The word "or" has the same meaning as the Boolean operator "OR", that is, it encompasses the possibilities of "any one" and "both" and unless otherwise explicitly stated, the term "exclusive" or " (" XOR "). It is also understood that the symbol " / " between two adjacent words has the same meaning as " or " unless expressly stated otherwise. Also, phrases such as " connected to ", " coupled to ", or " in communication with ", unless expressly stated otherwise, .

While the foregoing disclosure shows illustrative aspects, it should be noted that various changes and modifications may be made herein without departing from the scope of the appended claims. The functions, steps, or actions of method claims in accordance with the aspects described herein need not be performed in any particular order unless explicitly stated otherwise. In addition, elements may be described or claimed in the singular, but the plural is contemplated unless limitation to the singular is explicitly stated.

Claims (75)

As a communication method,
Generating satellite handoff information that specifies a handoff time for a particular cell of a particular satellite;
Receiving a measurement message from a user terminal;
Modifying the satellite handoff information based on the measurement message; And
And transmitting the modified satellite handoff information to the user terminal. The method according to claim 1,
Wherein the generation of the satellite handoff information is based on capability information for the user terminal. 3. The method of claim 2,
Wherein the capability information indicates at least one of whether the user terminal is capable of sensing multiple cells or the user terminal is capable of sensing multiple satellites. 3. The method of claim 2,
Wherein the capability information indicates at least one of an inter-cell tune time for the user terminal, or an inter-satellite tune time for the user terminal. 3. The method of claim 2,
Wherein the generation of the satellite handoff information is based on location information for the user terminal; And
Wherein the location information comprises a motion vector for the user terminal. The method according to claim 1,
Wherein the generation of the satellite handoff information is based on at least one of ephemeris information, limitation due to the current system, or satellite pointing error. The method according to claim 1,
Wherein the generation of the satellite handoff information is triggered based on at least one of handoff of the user terminal to a different satellite or reception of a measurement message from the user terminal. The method according to claim 1,
Further comprising performing handoffs for the user terminal to different cells and at least one satellite based on the satellite handoff information. 9. The method of claim 8,
Wherein the handoffs involve a change of at least one of a satellite access network (SAN) or a satellite network portal (SNP) antenna. 9. The method of claim 8,
Wherein the handoffs involve a change of at least one of a satellite cell or a forward service link (FSL) frequency. The method according to claim 1,
Wherein the modification of the satellite handoff information includes advancing the handoff timing, or delaying the handoff timing. The method according to claim 1,
Determining a measurement gap for measuring satellite signals; And
Further comprising transmitting information indicating the measurement gap to the user terminal,
Wherein the measurement message comprises an indication of a measurement of signals from at least one satellite performed during the measurement gap. The method according to claim 1,
Receiving capability information from the user terminal; And
Further comprising selecting a handoff procedure for the user terminal based on the received capability information. 14. The method of claim 13,
Wherein the capability information indicates whether the user terminal is dual detectable; And
Wherein the selection of the handoff procedure comprises enabling or disabling monitoring of a measurement message from the user terminal based on whether the user terminal is dual detectable. The method according to claim 1,
Determining a time of handoff of the user terminal; And
And forwarding at least one user queue prior to the handoff. The method according to claim 1,
Wherein the satellite handoff information includes a table including a handoff activation time. The method according to claim 1,
Wherein the satellite handoff information comprises at least one tune-away time. The method according to claim 1,
Further comprising receiving, from the user terminal, a message including user terminal paging area information. The method according to claim 1,
Further comprising the step of determining that the measurement gap is not needed to measure satellite signals,
Wherein as a result of the determination, the generation of the satellite handoff information includes not including a tune-away time in the satellite handoff information. The method according to claim 1,
Wherein the handoff information is for at least one future handoff. The method according to claim 1,
Wherein the handoff information is for a next beam handoff and is for at least one future satellite handoff. The method according to claim 1,
Wherein the generation of the satellite handoff information is based on a satellite beam pattern. An apparatus for communication,
Memory; And
A processor coupled to the memory,
The processor and the memory,
Generating satellite handoff information specifying a handoff time for a particular cell of a particular satellite;
Receive a measurement message from a user terminal;
Modify the satellite handoff information based on the measurement message; And
And transmits the modified satellite handoff information to the user terminal
A device for communication. 24. The method of claim 23,
The processor and the memory,
To generate the satellite handoff information based on at least one of capability information for the user terminal, location information for the user terminal, ephemeris information, limitation due to the current system, or satellite pointing error
A device for communication, further comprising: 25. The method of claim 24,
The capability information indicates whether the user terminal can detect a plurality of cells, whether the user terminal can detect a plurality of satellites, an inter-cell tune time for the user terminal, - a satellite tune time. 24. The method of claim 23,
The processor and the memory,
To perform handoffs for the user terminal to different cells and at least one satellite based on the satellite handoff information
A device for communication, further comprising: 24. The method of claim 23,
Wherein the processor and the memory are further configured to advance handoff timing or delay handoff timing to modify the satellite handoff information. 24. The method of claim 23,
The processor and the memory,
Determining a measurement gap for measuring satellite signals; And
To transmit information indicating the measurement gap to the user terminal
Further comprising:
Wherein the measurement message comprises an indication of a measurement of signals from at least one satellite performed during the measurement gap. 24. The method of claim 23,
The processor and the memory,
Receive capability information from the user terminal; And
And to select a handoff procedure for the user terminal based on the received capability information
A device for communication, further comprising: 30. The method of claim 29,
Wherein the capability information indicates whether the user terminal is dual detectable; And
To select the handoff procedure, the processor and the memory are configured to enable or disable whether the device monitors for a measurement message from the user terminal, based on whether the user terminal is dual detectable A device for communication, further comprising: 24. The method of claim 23,
The processor and the memory,
Determining a time of handoff of the user terminal; And
To deliver user queues prior to the handoff
A device for communication, further comprising: 24. The method of claim 23,
The processor and the memory,
Receiving, from the user terminal, a message including user terminal paging area information
A device for communication, further comprising: 24. The method of claim 23,
Wherein the processor and the memory are further configured to determine that a measurement gap is not needed to measure satellite signals; And
Wherein as a result of the determination, the generation of the satellite handoff information includes not including a tune-away time in the satellite handoff information. An apparatus for communication,
Means for generating satellite handoff information specifying a handoff time for a particular cell of a particular satellite;
Means for receiving a measurement message from a user terminal;
Means for modifying the satellite handoff information based on the measurement message; And
And means for transmitting the modified satellite handoff information to the user terminal. 35. The method of claim 34,
And means for performing handoffs for the user terminal to different cells and at least one satellite based on the satellite handoff information. 35. The method of claim 34,
Means for receiving capability information from the user terminal; And
And means for selecting a handoff procedure for the user terminal based on the received capability information. 35. The method of claim 34,
Means for determining a time of handoff of the user terminal; And
And means for communicating user queues prior to the handoff. 18. A non-transitory computer-readable storage medium storing computer-executable code,
Code for generating satellite handoff information specifying a handoff time for a particular cell of a particular satellite;
Code for receiving a measurement message from a user terminal;
Code for modifying the satellite handoff information based on the measurement message; And
And code for transmitting the modified satellite handoff information to the user terminal. ≪ Desc / Clms Page number 19 > As a communication method,
Measuring at least one signal from at least one satellite;
Generating a measurement message based on the measurement of the at least one signal;
Transmitting the measurement message;
Receiving satellite handoff information based on the measurement message, the satellite handoff information comprising: receiving the satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And
And performing a handoff to the particular cell of the particular satellite based on the satellite handoff information. 40. The method of claim 39,
Wherein the measurement message comprises at least one of measurement data based on the at least one signal, a request to advance the handoff timing, or a request to delay the handoff timing. 40. The method of claim 39,
Further comprising receiving information indicative of a measurement gap for measuring satellite signals,
Wherein the measurement of the at least one signal is performed during the measurement gap. 40. The method of claim 39,
Further comprising determining whether to transmit the measurement message based on at least one of whether signals from the current serving satellite are inadequate or whether signals from the target satellite are inadequate. 40. The method of claim 39,
Further comprising transmitting a message including user terminal capability information,
Wherein the received satellite handoff information is based on the user terminal capability information. 44. The method of claim 43,
The user terminal capability information includes at least one of whether the user terminal is capable of sensing multiple cells, the user terminal is capable of sensing multiple satellites, the user terminal inter-cell tune time, or the user terminal inter- And displaying one of the communication methods. 44. The method of claim 43,
Wherein transmission of the message including user terminal capability information is triggered as a result of an initial connection to the satellite. 40. The method of claim 39,
Further comprising transmitting a message including user terminal location information,
Wherein the received satellite handoff information is based on the user terminal location information. 47. The method of claim 46,
Wherein the user terminal location information comprises at least one of a current user terminal location or a user terminal motion vector. 47. The method of claim 46,
Wherein the transmission of the message comprising the user terminal location information is triggered as a result of at least one of an initial connection to the satellite, whether the user terminal crosses a geographic boundary, or whether an error limit has been exceeded. 40. The method of claim 39,
Wherein the handoff involves a change of at least one of a satellite access network (SAN), a satellite network portal (SNP) antenna, a satellite cell, or a forward service link (FSL) frequency. 40. The method of claim 39,
Receiving a dedicated preamble signature; And
Further comprising performing a non-contention-based random access procedure using the dedicated preamble signature. 40. The method of claim 39,
Wherein the satellite handoff information includes a table including a handoff activation time. 40. The method of claim 39,
Wherein the satellite handoff information comprises at least one tune-away time. 40. The method of claim 39,
Wherein the satellite handoff information is defined based in part on satellite pointing errors. 40. The method of claim 39,
Further comprising: transmitting a message including user terminal paging area information. 40. The method of claim 39,
Wherein the handoff information is for at least one future handoff. 40. The method of claim 39,
Wherein the handoff information is for a next beam handoff and is for at least one future satellite handoff. An apparatus for communication,
Memory; And
A processor coupled to the memory,
The processor and the memory,
Measuring at least one signal from at least one satellite;
Generate a measurement message based on the measurement of the at least one signal;
Transmit the measurement message;
Receiving satellite handoff information based on the measurement message, the satellite handoff information receiving the satellite handoff information specifying a handoff time for a particular cell of a particular satellite; And
And performs handoff to the specific cell of the specific satellite based on the satellite handoff information
A device for communication. 58. The method of claim 57,
Wherein the processor and the memory are further configured to receive information indicative of a measurement gap for measuring satellite signals; And
Wherein measurement of the at least one signal is made during the measurement gap. 59. The method of claim 58,
The processor and the memory,
To determine whether to transmit the measurement message based on at least one of whether signals from the current serving satellite are inadequate or whether signals from the target satellite are inadequate
A device for communication, further comprising: 58. The method of claim 57,
Wherein the processor and the memory are further configured to send a message containing user terminal capability information; And
Wherein the received satellite handoff information is based on the user terminal capability information. 64. The method of claim 60,
The user terminal capability information includes at least one of whether the user terminal is capable of sensing multiple cells, the user terminal is capable of sensing multiple satellites, the user terminal inter-cell tune time, or the user terminal inter- A device for communication, displaying one. 58. The method of claim 57,
Wherein the processor and the memory are further configured to transmit a message including user terminal location information; And
Wherein the received satellite handoff information is based on the user terminal location information. 63. The method of claim 62,
Wherein the transmission of the message comprising user terminal location information is triggered as a result of at least one of an initial connection to the satellite, whether the user terminal crosses a geographical boundary, or whether an error limit has been exceeded. 58. The method of claim 57,
The processor and the memory,
Receive a dedicated preamble signature; And
To perform a non-contention-based random access procedure using the dedicated preamble signature
A device for communication, further comprising: 58. The method of claim 57,
The processor and the memory,
To send a message containing the user terminal paging area information
A device for communication, further comprising: An apparatus for communication,
Means for measuring at least one signal from at least one satellite;
Means for generating a measurement message based on the measurement of the at least one signal;
Means for transmitting the measurement message;
Means for receiving satellite handoff information based on the measurement message, the satellite handoff information specifying a handoff time for a particular cell of a particular satellite; means for receiving the satellite handoff information; And
And means for performing a handoff to the particular cell of the particular satellite based on the satellite handoff information. 18. A non-transitory computer-readable storage medium storing computer-executable code,
Code for measuring at least one signal from at least one satellite;
Code for generating a measurement message based on the measurement of the at least one signal;
A code for transmitting the measurement message;
Code for receiving satellite handoff information based on the measurement message, wherein the satellite handoff information specifies a handoff time for a particular cell of a particular satellite; And
And code for performing a handoff to the particular cell of the particular satellite based on the satellite handoff information. delete delete delete delete delete delete delete delete

Images