JP2019517186A - Hand-off for satellite communication - Google Patents

Abstract

Various aspects of the present disclosure relate to handoff for a user terminal (eg, idle mode handoff or other type of handoff). In some aspects, a user terminal (UT) may request idle mode handoff information from a terrestrial network (GN). Idle mode handoff information may include, for example, start times for a set of satellites, with each specific start time indicating when the UT can handoff to the corresponding satellite. The UT may send a request for idle mode handoff information to the GN when the UT has a defined number of valid entries (eg, one non-expired entry) remaining in the idle mode handoff table. In some aspects, an idle UT may GN requests for idle mode handoff information based on the time associated with a particular entry in the idle mode handoff table or based on the idle mode handoff table lifetime. Can be sent to

Description

This application claims the benefit of provisional application no. 62 / 409,289 filed on Oct. 17, 2016 in the United States Patent and Trademark Office, non-provisional application filed on Apr. 28, 2016 in the United States Patent and Trademark Office No. 15 / 141,641 and non-provisional application No. 15 / 498,388 filed on Apr. 26, 2017 in the US Patent and Trademark Office claim the priority and benefit of each of which is incorporated herein by reference in its entirety. Is incorporated into the book.

  Various aspects described herein relate to satellite communications, and more particularly, but not exclusively, to handoffs for non-geostationary satellite communications.

  The satellite based communication system may include the gateway and one or more satellites to relay communication signals between the gateway and one or more user terminals. A gateway is a ground station that has an antenna for transmitting signals to and receiving signals from communication satellites. The gateway uses communication links to connect user terminals to other user terminals or users of the public switched telephone network, the Internet, and other communication systems such as various public networks and / or private networks, etc. I will provide a. Satellites are orbiting receivers and repeaters that are used to relay information.

  The satellite may receive signals from the user terminal and transmit signals to the user terminal as long as the user terminal is in the satellite's "footprint". The footprint of a satellite is a geographical area on the surface within the range of the satellite signal. The footprint is usually geographically divided into multiple "beams" through the use of an antenna (eg, the antenna may be used to form a fixed static beam, or May be used to form a beam that can be dynamically adjusted through forming techniques). Each beam covers a specific geographical area in the footprint. The beams may be directed such that multiple beams from the same satellite cover the same specific geographic area. In addition, beams from multiple satellites can be directed to cover the same geographical area. The cells may constitute the frequency of any forward link in the beam and / or the frequency of the return link. If each beam only uses one frequency, the terms "cell" and "beam" may be interchangeable.

  Geostationary satellites have long been used for communication. Because the geostationary satellites are stationary relative to a given location on the earth, there is very little timing shift and Doppler frequency shift in the wireless signal propagation between the communications transceiver on the earth and the geostationary satellites. However, since geostationary satellites are limited to geosynchronous orbit (GSO) and GSO is a circle just above the equator and with a radius of about 42,164 km from the center of the earth, the number of satellites that can be placed in GSO is limited.

  As an alternative to geostationary satellites, communication systems that utilize constellations of satellites in non-geostationary orbits, such as Earth Low Earth Orbit (LEO), have been devised to provide communication coverage for the entire earth or at least a large portion of the earth. In non-geostationary satellite based systems, such as LEO satellite based systems, satellites move relative to ground based communication devices, such as gates or user terminals. Thus, at some point in time, the user terminal is handed off from one satellite to another. As a result, there is a need for techniques that allow user terminals to be efficiently handed off to the best available satellites.

  The following presents a simplified summary of such aspects in order to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of all contemplated features of the disclosure, nor does it identify key or critical elements of all aspects of the disclosure, and any or all aspects of the disclosure It does not define the scope of 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.

  In one aspect, the disclosure determines a time associated with a particular one of a set of handoff entries, the set of handoff entries identifying a set of satellites for device handoff. Determining whether to send a request for the updated set of handoff entries based on the identified time; and if the determination is to send the request, the request for the updated set of handoff entries Providing a method for communication.

  In some aspects, the set of handoff entries may include (eg, be) an idle mode handoff table. In some aspects, the time may include the start time of the handoff to one satellite of the set of satellites. In some aspects, that particular entry may include the last entry of the set of handoff entries. In some aspects, that set of satellites may be for idle mode operation of the device. In some aspects, this time may indicate when the device should be handed off to one satellite of the set of satellites while the device is in idle mode. In some aspects, the set of handoff entries may identify the time at which devices in idle mode should be handed off to each satellite of the set of satellites. In some aspects, the set of handoff entries may include the time for devices in idle mode to handoff to the satellites for each satellite. In some aspects, the request may be communicated when the device establishes a wireless connection with the terrestrial network. In some aspects, an apparatus may include (eg, be) a user terminal. In some aspects, the request may be sent to the terrestrial network.

  In one aspect, the present disclosure provides an apparatus configured for communication, including a memory and a processor coupled to the memory. The processor and the memory identify the time associated with a particular entry of the set of handoff entries, the set of handoff entries identifying the set of satellites for the device handoff. Based on the identified time, determining whether to send a request for the updated set of handoff entries and, if the determination is to send the request, request for the updated set of handoff entries. And transmitting.

  In some aspects, the set of handoff entries may include an idle mode handoff table, and the idle mode handoff table may include, for each satellite, the time when a device in idle mode is to be handed off to the satellites. In some aspects, the processor and memory may be further configured to transmit an indication of that time along with the transmission of the request. In some aspects, the processor and memory may be further configured to transmit an indication of valid time associated with the set of handoff entries along with transmitting the request. In some aspects, the processor and memory further receive the updated set of handoff entries after sending the request, and identify by the updated set of handoff entries at the time indicated by the updated set of handoff entries. Can be configured to handoff to the In some aspects, the processor and the memory may be further configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit. The handoff to the satellite identified by the updated set of handoff entries may be performed on at least one carrier frequency. In some aspects, the processor and memory may be further configured to determine location information of the device and to transmit the location information upon transmission of the request.

  In one aspect, the present disclosure provides an apparatus configured for communication. The apparatus is identified as a means for identifying a time associated with a particular one of the set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of the apparatus. Means for determining whether to send a request for the updated set of handoff entries based on the time of day and a request for the updated set of handoff entries if the determination is to send the request And means for transmitting.

  In some aspects, the means for transmitting may be configured to transmit an indication of that time along with the transmission of the request. In some aspects, the means for transmitting may be configured to transmit an indication of valid time associated with that set of handoff entries along with transmitting the request. In some aspects, the apparatus, after sending the request, with means for receiving the updated set of handoff entries, and an updated set of handoff entries at a time indicated by the updated set of handoff entries. And means for handing off the device to the identified satellite. In some aspects, the means for receiving is configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit. The handoff to the satellite identified by the updated set of handoff entries may be performed on at least one carrier frequency. In some aspects, the device may include means for determining position information of the device, and the means for transmitting may be further configured to transmit the position information with the transmission of the request. .

  In one aspect, the disclosure is identifying a time associated with a particular one of a set of handoff entries, the set of handoff entries identifying a set of satellites for handoff of a device. And determining whether to send a request for the updated set of handoff entries based on the identified time, and if the determination is to send the request, the updated set of handoff entries. A non-transitory computer readable medium having computer executable code stored thereon, comprising: code for transmitting a request for

  In one aspect, the disclosure is the step of identifying the amount of valid entries in the set of handoff entries, wherein the set of handoff entries identifies the set of satellites for device handoff. Determining whether to send a request for the updated set of handoff entries based on the amount that was sent and, if the determination is to send the request, send the request for the updated set of handoff entries And providing a method for communication.

  In some aspects, determining whether to send a request for the updated set of handoff entries may include determining whether the set of handoff entries includes only one valid entry. In some aspects, the request may be communicated when the device establishes a wireless connection with the terrestrial network. In some aspects, the set of handoff entries may identify the time at which devices in idle mode should be handed off to each satellite of the set of satellites.

  In one aspect, the present disclosure provides an apparatus configured for communication, including a memory and a processor coupled to the memory. The processor and the memory are to identify the amount of valid entries in the set of handoff entries, the set of handoff entries to identify the set of satellites for the handoff of the device, and Based on the volume, determining whether to send a request for the updated set of handoff entries and if the determination is to send the request, send the request for the updated set of handoff entries. Configured to do things.

  In some aspects, the processor and memory further receive the updated set of handoff entries after sending the request, and identify by the updated set of handoff entries at the time indicated by the updated set of handoff entries. Can be configured to handoff to the In some aspects, the processor and the memory may be further configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit. The handoff to the satellite identified by the updated set of handoff entries may be performed on at least one carrier frequency. In some aspects, the processor and memory may be further configured to determine location information of the device and to transmit the location information upon transmission of the request.

  In one aspect, an apparatus configured for communication is provided. The apparatus is a means for identifying the amount of valid entries in the set of handoff entries, wherein the set of handoff entries identifies the set of satellites for handoff of the apparatus, and the identified quantity. Means for determining whether to send a request for the updated set of handoff entries based on and sending a request for the updated set of handoff entries if the determination is to send the request. And means for

  In some aspects, the apparatus, after sending the request, with means for receiving the updated set of handoff entries, and an updated set of handoff entries at a time indicated by the updated set of handoff entries. And means for handing off the device to the identified satellite. In some aspects, the means for receiving is configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit. The handoff to the satellite identified by the updated set of handoff entries may be performed on at least one carrier frequency. In some aspects, the device may include means for determining position information of the device, and the means for transmitting may be configured to transmit the position information along with the transmission of the request.

  In one aspect, the present disclosure is to identify the amount of valid entries in a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for device handoff. A request for the updated set of handoff entries, if based on the identified amount, determining whether to transmit a request for the updated set of handoff entries, and if the determination is to transmit the request. A non-transitory computer readable medium having computer executable code stored thereon, comprising code for: transmitting.

  In one aspect, the disclosure identifies a valid time period associated with a set of handoff entries, the set of handoff entries identifying a set of satellites for handoff of another device. Determining whether to send the updated set of handoff entries based on the valid time, and if the decision is to send the updated set of handoff entries, the updated set of handoff entries Providing a method for communication.

  In some aspects, the time to live indicates the length of time that the set of entries for the handoff may be valid. In some aspects, determining the valid time may include receiving an indication of the valid time. In some aspects, determining the valid time includes receiving an indication of a time associated with a particular entry of the set of handoff entries, and determining the valid time based on the received indication. obtain. In some aspects, determining the valid time may include determining a time associated with the last valid entry in the set of handoff entries. In some aspects, the set of handoff entries may include the last set of handoff entries sent by the device to other devices. In some aspects, an apparatus may include (eg, be) a terrestrial network. In some aspects, the updated set of handoff entries may be sent to the user terminal.

  In one aspect, the present disclosure provides an apparatus configured for communication, including a memory and a processor coupled to the memory. The processor and the memory are to specify an effective time associated with the set of handoff entries, wherein the set of handoff entries is to identify a set of satellites for another device's handoff. Based on the time to live, determining whether to send the updated set of handoff entries and if the decision is to send the updated set of handoff entries, the updated set of handoff entries And transmitting.

  In some aspects, the processor and memory may be further configured to receive location information of other devices. In some aspects, the processor and memory may be further configured to generate an updated set of handoff entries based on the location information, and the updated set of handoff entries is transmitted to the other device. There is a thing. In some aspects, the processor and memory may be further configured to receive location information of other devices, and the determination of whether to send the updated set of handoff entries further to location information. May be based. In some aspects, the processor and memory may be further configured to receive location information of other devices. In some aspects, the processor and memory may be further configured to determine the movement of the other device based on the location information, and the determination of whether to transmit the updated set of handoff entries further. , May be based on the movement of other devices. In some aspects, the processor and memory further receive location information of the other device, determine movement of the other device based on the location information, and how many updated handoffs are based on movement of the other device It may be configured to decide whether to send an entry.

  In one aspect, the present disclosure provides an apparatus configured for communication. A device is means for identifying an effective time associated with a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for another device's handoff, and the identified effective time. Means for determining whether to send the updated set of handoff entries based on the and the updated set of handoff entries if the decision is to send the updated set of handoff entries. And means for transmitting.

  In some aspects, an apparatus may include means for receiving location information of another apparatus, and means for generating an updated set of handoff entries based on the location information, the handoff entry The updated set of may be sent to other devices. In some aspects, the apparatus may include means for receiving position information of the other apparatus, and the determination of whether to transmit the updated set of handoff entries is further based on the position information. is there. In some aspects, an apparatus may include means for receiving position information of another apparatus, and means for determining movement of the other apparatus based on the position information, and updating the handoff entry. The determination of whether to transmit the set may also be based on the movement of the other device. In some aspects, the device may be based on the means for receiving location information of the other device, the means for determining the motion of the other device based on the location information, and the number of motions of the other device. And means for determining whether to transmit the updated handoff entry.

  In one aspect, the disclosure is identifying a valid time associated with a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of another device; Based on the determined validity time, determining whether to send the updated set of handoff entries and if the decision is to send the updated set of handoff entries, the handoff entry is updated. And providing a non-transitory computer readable medium storing computer executable code for the device, including code for transmitting the set.

  These and other aspects of the disclosure will be more fully understood upon consideration of the following detailed description of the invention. Other aspects, features, and implementations of the present disclosure will be apparent to those skilled in the art upon review of the following description of specific implementations of the present disclosure in conjunction with the accompanying figures. Although features of the present disclosure may be discussed with respect to some implementations and figures below, all implementations of the present disclosure include one or more of the advantageous features described herein. obtain. In other words, one or more implementations may be described as having some advantageous features, although one or more of such features may also be described herein. May be used according to various implementations of Similarly, while some implementations may be discussed below as implementations of devices, systems, or methods, it should be understood that such implementations may be implemented with various devices, systems, and methods. .

  The accompanying drawings are presented to aid in the description of the aspects of the present disclosure and are provided solely for illustration of the aspects and not limitation of the aspects.

  The accompanying drawings are presented to aid in the description of the aspects of the present disclosure and are provided solely for illustration of the aspects and not limitation of the aspects.

FIG. 1 is a block diagram of an example communication system, in accordance with certain aspects of the present disclosure. FIG. 2 is a block diagram of an example terrestrial network (GN) of FIG. 1 in accordance with certain aspects of the present disclosure. FIG. 2 is a block diagram of an example satellite of FIG. 1 in accordance with certain aspects of the present disclosure. FIG. 7 is a block diagram of an example of the user terminal of FIG. 1 in accordance with certain aspects of the present disclosure. FIG. 2 is a block diagram of an example of the user equipment of FIG. 1 according to some aspects of the present disclosure. FIG. 16 is a block diagram illustrating an example transmitter device and a receiver device, in accordance with certain aspects of the present disclosure. FIG. 1 is a block diagram of an example communication system, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of communicating idle mode information, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of idle mode handoff in accordance with certain aspects of the present disclosure. FIG. 1 is a block diagram of an example communication system, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of inter-satellite handoff signaling in accordance with certain aspects of the present disclosure. FIG. 5 illustrates another example of inter-satellite handoff signaling in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of feeder link switching, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of satellite pointing error according to some aspects of the present disclosure. FIG. 10 illustrates an example non-random access based BxP handoff call flow, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of a non-random access based BxP handoff call flow with user terminal (UT) measurements, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of a random access based BxP handoff call flow, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of a random access based BxP handoff call flow with UT measurements, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of a random access based BxP handoff call flow with UT measurements, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example AxP handoff call flow, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example AxP handoff call flow, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example AxP handoff call flow, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of a radio link failure call flow, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of generating and using satellite and cell transition tables, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of using satellite and cell transition tables, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of signaling user terminal capabilities in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of using user terminal capabilities in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of signaling user terminal location information, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of using user terminal location information, in accordance with certain aspects of the present disclosure. FIG. 16 illustrates an example user terminal handoff operation, in accordance with certain aspects of the present disclosure. FIG. 10 illustrates an example of a GN handoff operation, in accordance with certain aspects of the present disclosure. FIG. 5 illustrates another example of inter-satellite handoff signaling in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of signaling ephemeris information, in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of a radio link failure operation in accordance with certain aspects of the present disclosure. FIG. 7 illustrates an example of measurement gap related operations according to some aspects of the present disclosure. FIG. 7 illustrates another example of measurement gap related operations according to some aspects of the present disclosure. FIG. 10 illustrates an example of user queue related operations in accordance with certain aspects of the present disclosure. FIG. 8 illustrates an example of random access related operations in accordance with certain aspects of the present disclosure. FIG. 16 is a block diagram illustrating an example hardware implementation for an apparatus (eg, an electronic device) that can support communication, in accordance with certain aspects of the present disclosure. 5 is a flowchart illustrating an example communication process, in accordance with certain aspects of the present disclosure. 5 is a flowchart illustrating an example communication process, in accordance with certain aspects of the present disclosure. 5 is a flowchart illustrating an example communication process, in accordance with certain aspects of the present disclosure. FIG. 16 is a block diagram illustrating an example hardware implementation for an apparatus (eg, an electronic device) that can support communication, in accordance with certain aspects of the present disclosure. 5 is a flowchart illustrating an example communication process, in accordance with certain aspects of the present disclosure. 5 is a flowchart illustrating an example communication process, in accordance with certain aspects of the present disclosure. FIG. 16 is a block diagram of an example hardware implementation for an apparatus (eg, an electronic device) capable of supporting satellite related communications, in accordance with certain aspects of the present disclosure. 7 is a flow chart illustrating an example of a process involved in generating satellite handoff information in accordance with certain aspects of the present disclosure. 7 is a flow chart illustrating an example of a process involved in generating satellite and cell transition information in accordance with certain aspects of the present disclosure. FIG. 16 is a block diagram of an example hardware implementation for another device (eg, an electronic device) that can support satellite related communications, in accordance with certain aspects of the present disclosure. 7 is a flow chart illustrating an example of a process involved in handoff in accordance with certain aspects of the present disclosure. 7 is a flow chart illustrating an example of a process involved in handoff in accordance with certain aspects of the present disclosure.

  Various aspects of the present disclosure relate to idle mode handoff for a user terminal (UT). In some scenarios, idle UTs request idle mode handoff information from the terrestrial network (GN). Idle mode handoff information may include, for example, start times for a set of satellites, with each particular start time indicating when an idle UT can hand off to a corresponding satellite. In some aspects, an idle UT is idle when the idle UT has a defined number of valid entries (eg, one non-expired entry) remaining in the idle mode handoff table. A request for mode handoff information may be sent to the GN. In some aspects, an idle UT may send a request for idle mode handoff information to the GN based on the time associated with a particular entry (eg, the last entry) in the idle mode handoff table. In some aspects, an idle UT may send a request for idle mode handoff information to the GN based on the idle mode handoff table's lifetime. In some aspects, an idle UT may send a request for idle mode handoff information to the GN when the idle UT establishes a wireless connection with the GN. In some aspects, the GN autonomously (eg, without a request from the idle UT) idle mode handoff information to the idle UT when the idle UT establishes a wireless connection with the GN. Can be sent.

  Aspects of the present disclosure are described in the following description and related drawings directed to specific embodiments. Alternate embodiments may be devised without departing from the scope of the present disclosure. In addition, well known elements are not described in detail or are omitted so as not to obscure the relevant details of the present disclosure.

  FIG. 1 illustrates a satellite communication system 100, a satellite 300, comprising a plurality of satellites in a non-geostationary orbit, eg, low earth orbit (LEO) (although only one satellite 300 is shown for clarity of illustration) A terrestrial network 200 (eg, corresponding to a satellite gateway or satellite network portal) in communication, a plurality of UTs 400 and 401 in communication with satellites 300, and a plurality of user equipments (UEs in communication with UTs 400 and 401, respectively) The example of 500) and 501 is shown. 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 watch, an audio visual device, or any device that includes the ability to communicate with a UT . Additionally, UE 500 and / or UE 501 may be devices (eg, access points, small cells, etc.) used to communicate with one or more end user devices. In the example shown in FIG. 1, UT 400 and UE 500 communicate with each other via a bi-directional access link (with forward and return access links), and similarly, UT 401 and UE 501 are separate bi-directional access links Communicate with each other through In another implementation, one or more additional UEs (not shown) may be configured to receive only, and thus communicate with the UT using only the forward access link. In another implementation, one or more additional UEs (not shown) may also communicate with UT 400 or UT 401. Alternatively, the UT and corresponding UE may be an integral part of a single physical device such as, for example, a mobile phone with an embedded satellite transceiver and antenna for direct communication with the satellite.

  The GN 200 may have access to the Internet 108, or to one or more other types of public, semi-private or private networks. In the example shown in FIG. 1, GN 200 is in communication with infrastructure 106, which accesses Internet 108, or one or more other types of public, semi-private, or private networks. It is possible. GN 200 may also be coupled to various types of communication backhaul, including, for example, fixed networks such as fiber optic networks or public switched telephone networks (PSTNs) 110. Furthermore, in alternative implementations, the GN 200 interfaces with the Internet 108, the PSTN 110, or one or more other types of public, semi-private, or private networks without using the infrastructure 106. obtain. Still further, GN 200 may communicate with other GNs such as GN 201 through infrastructure 106, or alternatively may be configured to communicate with GN 201 without using infrastructure 106. Infrastructure 106 may be, in whole or in part, a network control center (NCC), a satellite control center (SCC), a wired and / or wireless core network, and / or an operation of satellite communication system 100 and / or a satellite communication system 100. May include any other component or system used to support communication with.

  Communication between satellite 300 and GN 200 in both directions is called a feeder link, and communication between satellites in both directions and each of UTs 400 and 401 is called a service link. A single path from satellite 300 to a ground station, which may be GN 200 or one of UTs 400 and 401, may generally be referred to as the downlink. The single path from the ground station to the satellite 300 may be generally referred to as the uplink. In addition, as shown, the signals may have general directionality, such as forward and return links (or reverse links). Thus, the communication link in the direction starting at GN 200 through satellite 300 and terminating at UT 400 is referred to as the forward link, and the communication link in the direction starting at UT 400 through satellite 300 and terminating at GN 200 is referred to as the return or reverse link. . Thus, in FIG. 1, the signal path from GN 200 to satellite 300 is named “forward feeder link” 112 while the signal path from satellite 300 to GN 200 is named “return feeder link” 114. Similarly, in FIG. 1, the signal path from each UT 400 or 401 to the satellite 300 is named "Return Service Link" 116, while the signal path from the satellite 300 to each UT 400 or 401 is "Forward service link It is named "118".

  The handoff controller 122 of UT 401 and the handoff controller 124 of GN 200 cooperate to control the handoff of UT 401 from one satellite or cell to another. Other components of satellite communication system 100 may also include corresponding handoff controllers. For example, other GNs, satellites, and UTs (not shown) may include corresponding controllers. However, to reduce the complexity of FIG. 1, the handoff controller is illustrated for UT 401 and GN 200 only.

  Handoff controller 122 of UT 401 transmits UT information (eg, including UT location information and / or UT capability information) to handoff controller 124 of GN 200 via satellite 300 (eg, via signaling 126). In addition, the handoff controller 122 includes a handoff information request controller 136 that determines whether the handoff information request will also be sent to the handoff controller 124 of the GN 200 (eg, via signaling 126).

  Handoff controller 124 includes a handoff information generator 130 that generates handoff information (eg, a handoff table) indicating the timing of the UT 401 handoff. In some aspects, the handoff information generator 130 is based at least in part on UT information, satellite position over time (obtained from ephemeris data), satellite cell patterns, and satellite cell on and off schedules. , Handoff information may be generated. The handoff controller 124 also includes a handoff information transmission controller 132 that determines whether to send the handoff information 134 to the handoff controller 122 via the current satellite 300. In some aspects, the handoff information transmission controller 132 may transmit the handoff information 134 in response to the handoff information request from the UT 401.

  Handoff controller 122 receives handoff information 134 via current satellite 300 and maintains a local copy of handoff information (e.g., handoff table) 138. The handoff controller 122 may then control the UT 401 handoff based on the handoff information 138.

  In some implementations, satellite communication system 100 manages idle mode handoff information. For example, handoff controller 124 may determine (eg, generate) idle mode handoff information and transmit idle mode handoff information to handoff controller 122. In some aspects, the handoff controller 124 can receive UT information (eg, UT location information) from the UT 401 and manages idle mode handoff information based on the UT information. In some aspects, handoff controller 122 may receive and manage a local copy of idle mode handoff information.

  FIG. 2 is an exemplary block diagram of GN 200, which may also apply to GN 201 of FIG. GN 200 includes several antennas 205, RF subsystem 210, digital subsystem 220, public switched telephone network (PSTN) interface 230, local area network (LAN) interface 240, GN interface 245, and GN controller 250. It is shown. RF subsystem 210 is coupled to antenna 205 and digital subsystem 220. Digital subsystem 220 is coupled to PSTN interface 230, LAN interface 240, and GN interface 245. GN controller 250 is coupled to RF subsystem 210, digital subsystem 220, PSTN interface 230, LAN interface 240, and GN interface 245.

  The RF subsystem 210, which may include several RF transceivers 212, an RF controller 214, and an antenna controller 216, can transmit communication signals to the satellite 300 via the forward feeder link 301F, the return feeder link 301R. Communication signals from the satellite 300 can be received via the Although not shown for the sake of brevity, 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) to respectively amplify and down convert the received communication signals in a well known manner. In addition, each receive chain may include an analog-to-digital converter (ADC) to convert received communication signals (eg, for processing by digital subsystem 220) from analog signals to digital signals. Each transmit chain may include an upconverter (e.g., a mixer) and a power amplifier (PA) to respectively upconvert and amplify the communication signals to be transmitted to the satellite 300 in a well known manner. In addition, each transmit chain may include a digital to analog converter (DAC) to convert digital signals received from the digital subsystem 220 into analog signals to be transmitted to the satellite 300.

  RF controller 214 may be used to control various aspects of several RF transceivers 212 (eg, carrier frequency selection, frequency and phase calibration, gain setting, etc.). Antenna controller 216 may control various aspects of antenna 205 (eg, beamforming, beam steering, setting of gain, adjustment of frequency, etc.).

  Digital subsystem 220 may include several digital receiver modules 222, several digital transmitter modules 224, a baseband (BB) processor 226, and a control (CTRL) processor 228. The digital subsystem 220 may process the communication signals received from the RF subsystem 210 and transfer the processed communication signals to the PSTN interface 230 and / or the LAN interface 240, the PSTN interface 230 and / or the LAN interface The communication signals received from 240 may be processed and the processed communication signals may be forwarded to RF subsystem 210.

  Each digital receiver module 222 may correspond to a signal processing element used to manage the communication between the GN 200 and the UT 400. One of the receive chains of the RF transceiver 212 can provide input signals to multiple digital receiver modules 222. Several digital receiver modules 222 may be used to accept all of the satellite beams and possible diversity mode signals being handled at any given time. Although not shown for brevity, each digital receiver module 222 may include one or more digital data receivers, searcher receivers, and diversity combiner and decoder circuits. A searcher receiver may be used to search for the appropriate diversity mode of the carrier signal, and may be used to search for the pilot signal (or other relatively unchanged pattern of strong signals) .

  Digital transmitter module 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 is required to (1) apply the lowest level of power for the purpose of interference reduction and resource allocation, and (2) to compensate for transmit path attenuation and other path transfer characteristics. It can be controlled by a corresponding digital transmit power controller (not shown for the sake of simplicity), which can apply the appropriate level of power when done.

  Control processor 228 coupled to digital receiver module 222, digital transmitter module 224, and baseband processor 226 includes, but is not limited to, signal processing, timing signal generation, power control, handoff control, diversity combining, and systems Command and control signals to provide functions such as an interface of

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

  The baseband processor 226 is well known in the art and will not be described in detail herein. For example, baseband processor 226 may include various known elements such as (but not limited to) coders, data modems, and components for switching and storing digital data.

  The PSTN interface 230 may provide communication signals to the external PSTN, either directly or through additional infrastructure 106, as shown in FIG. 1, and may receive communication signals from the external PSTN. The LAN interface 230 is well known in the art and will not be described in detail herein. In other implementations, PSTN interface 230 may be omitted or replaced by any other suitable interface that connects GN 200 to a terrestrial network (eg, 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, LAN interface 240 may be coupled to the Internet 108 directly or through additional infrastructure 106, as shown in FIG. The LAN interface 240 is well known in the art and will not be described in detail herein.

  GN interface 245 may be to / from one or more other GNs associated with satellite communication system 100 of FIG. 1 (and / or to GN associated with other satellite communication systems not shown for brevity). /) Can provide communication signals and receive communication signals. In some implementations, the GN interface 245 may communicate with other GNs via one or more dedicated communication lines or channels (not shown for brevity). In other implementations, the GN interface 245 may communicate with other GNs using the PSTN 110 and / or other networks such as the Internet 108 (see also FIG. 1). In at least one implementation, GN interface 245 may communicate with other GNs via infrastructure 106.

  Global GN control may be provided by the GN controller 250. GN controller 250 may plan and control the utilization of satellite 300 resources by GN 200. For example, GN controller 250 may analyze trends, generate traffic plans, allocate satellite resources, monitor (or track) satellite locations, and monitor GN 200 and / or satellite 300 performance. The GN controller 250 also maintains the orbit of the satellite 300 and monitors it, relays satellite usage information to the GN 200, tracks the location of the satellite 300, and / or adjusts the settings of various channels of the satellite 300, the ground May be coupled to a satellite controller (not shown for brevity).

  In the exemplary implementation shown in FIG. 2, the GN controller 250 includes local time, frequency, and location references 251, which include the RF subsystem 210, the digital subsystem 220, and / or the interface 230, 240 and 245 may be provided with local time or frequency information. Time or frequency information may be used to synchronize the various components of GN 200 with each other and / or with satellite 300. Local time, frequency, and location reference 251 may also provide satellite 300 location information (eg, ephemeris data) to various components of GN 200. Further, although illustrated in FIG. 2 as included in GN controller 250, in other implementations, local time, frequency, and location reference 251 may be associated with GN controller 250 (and / or digital subsystem 220). And one or more of the RF subsystems 210) may be separate subsystems.

  Although not shown in FIG. 2 for simplicity, the GN controller 250 may also be coupled to a network control center (NCC) and / or a satellite control center (SCC). For example, GN controller 250 may allow SCC to communicate directly with satellite 300, eg, retrieve ephemeris data from satellite 300. The GN controller 250 also allows the GN controller 250 to properly target the antenna 205 (e.g., of the appropriate satellite 300), to schedule beam transmissions, to coordinate handoffs, and various other well known Processed information (eg, from SCC and / or NCC) may be received that allows the function to be performed.

  The GN controller 250 performs one or more of the handoff information related operations for the GN 200 as taught herein separately or in concert, one of the processing circuitry 232, the memory device 234, or the handoff controller 236 or May contain more than one. In an example implementation, processing circuitry 232 is configured (eg, programmed) to perform some or all of these operations. In another exemplary implementation, processing circuitry 232 (eg, in the form of a processor) executes code stored in memory device 234 to perform some or all of these operations. In another exemplary implementation, handoff controller 236 is configured (eg, programmed) to perform some or all of these operations. Although illustrated in FIG. 2 as being included in GN controller 250, in other implementations, one or more of processing circuitry 232, memory device 234, or handoff controller 236 may And / or may be separate subsystems coupled to one or more of digital subsystem 220 and RF subsystem 210.

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

  Within each of the respective forward paths FP (1) to FP (N), the first bandpass filter 311 passes signal components having frequencies within the channel or frequency band of the respective forward path FP, Filter signal components having frequencies outside the channel or frequency band of each forward path FP. Thus, the pass band of the first band pass filter 311 corresponds to the width of the channel associated with the respective forward path FP. The first LNA 312 amplifies the received communication signal to a level suitable for processing by the frequency converter 313. The frequency converter 313 converts the frequency of the communication signal in each forward path FP (eg, to a frequency suitable for transmission from the satellite 300 to the UT 400). The second LNA 314 amplifies the frequency converted communication signal, and the second band pass filter 315 filters signal components having frequencies outside the associated channel width. The PA 316 amplifies the filtered signal to a power level suitable for transmission to the UT 400 via the respective antenna 352. A return transponder 320 including a number (N) of return paths RP (1) to RP (N) communicates communication signals from UT 400 along return service link 302R via antennas 361 (1) to 361 (N). A signal is received and a communication signal is sent to GN 200 along return feeder link 301 R via one or more of antennas 362. Each of the return paths RP (1) to RP (N) that may process communication signals in the corresponding channel or frequency band may be coupled to a respective one of the antennas 361 (1) to 361 (N) , One each of the first band pass filters 321 (1) to 321 (N), one each of the first LNAs 322 (1) to 322 (N), and frequency converters 323 (1) to 323 (N) , One each of the second LNAs 324 (1) -324 (N), and one each of the second band pass filters 325 (1) -325 (N).

  In each of the respective return paths RP (1) to RP (N), the first bandpass filter 321 passes signal components having frequencies within the channel or frequency band of the respective reverse path RP, respectively The signal component having a frequency outside the channel or frequency band of the reverse path RP is filtered. Thus, the passband of the first band pass filter 321 may correspond to the width of the channel associated with the respective return path RP in some implementations. The first LNA 322 amplifies all received communication signals to a level appropriate for processing by the frequency converter 323. The frequency converter 323 converts the frequency of the communication signal in each return path RP (eg, to a frequency suitable for transmission from the satellite 300 to the GN 200). The second LNA 324 amplifies the frequency converted communication signal, and the second band pass filter 325 filters signal components having frequencies outside the associated channel width. The signals from the return paths RP (1) to RP (N) are combined and provided to one or more antennas 362 via PA 326. PA 326 amplifies the synthesized signal for transmission to GN 200.

  Oscillator 330, which may be any suitable circuit or device that generates an oscillating signal, provides forward local oscillator signal LO (F) to frequency converters 313 (1) -313 (N) of forward transponder 310; A return local oscillator signal LO (R) is provided to the frequency converters 323 (1) -323 (N) of the return transponder 320. For example, the LO (F) signal is frequency converted to convert the communication signal from the frequency band associated with the transmission of the signal from GN 200 to satellite 300 to the frequency band associated with the transmission of the signal from satellite 300 to UT 400 May be used by the vessels 313 (1) -313 (N). The LO (R) signal is a frequency converter 323 to convert the communication signal from the frequency band associated with the transmission of the signal from UT 400 to satellite 300 to the frequency band associated with the transmission of the signal from satellite 300 to GN 200. (1) to 323 (N) may be used.

  Controller 340 coupled to forward transponder 310, return transponder 320, and oscillator 330 may control various operations of satellite 300, including (but not limited to) channel allocation. In one aspect, controller 340 may include processing circuitry 364 (eg, a processor) coupled to a memory (eg, memory device 366). The memory is a non-transitory computer readable medium (e.g., a computer readable medium) storing instructions which, when executed by the processing circuitry 364, cause the satellite 300 to perform operations including (but not limited to) the operations described herein. It may include one or more non-volatile memory devices, such as EPROM, EEPROM, flash memory, hard drive, etc.

  FIG. 4 is an exemplary block diagram of UT 400 or UT 401 for purposes of illustration only. It should be understood that the specific UT configuration can vary widely. Thus, the present disclosure is not limited to any particular UT configuration, and any UT capable of providing a functional connection between satellite 300 and UE 500 or 501 is considered to be within the scope of the present disclosure. It can be done.

  UTs may be used in various applications. In some scenarios, the UT may provide a cellular backhaul. In this case, the UT may have a relatively large antenna and / or multiple antennas (eg, to protect from jamming). In some scenarios, UT can be deployed in a corporate environment (eg, can be placed on the roof of a building). In this case, the UT may have a relatively large antenna and / or multiple antennas (eg, to provide a relatively high backhaul bandwidth). In some scenarios, UT can be deployed in a residential environment (eg, can be placed on the roof of a house). In this case, the UT may have a smaller (and relatively inexpensive) antenna and provide fixed access (eg, internet access) to data services. In some scenarios, UT can be deployed in a marine environment (eg, can be placed on a cruise ship, cargo ship, etc.). In this case, the UT may have a relatively large antenna and / or multiple antennas (eg, to prevent jamming and provide relatively high bandwidth data service). In some scenarios, UTs can be deployed to vehicles (eg, carried by first responders, emergency personnel, etc.). In this case, the UT may have smaller antennas and may be used to provide temporary Internet access to certain areas (eg, where cellular services are out of range). Other scenarios are possible.

  The configuration of a particular UT may depend on the application for which the UT is used. For example, the type of antenna, the shape of the antenna, the amount of antenna, the bandwidth supported, the transmission power supported, the sensitivity of the receiver etc may depend on the corresponding application. As an example, planar antennas (relatively inconspicuous) may be used in aircraft applications.

  In the example of FIG. 4, the UT is shown to include a transceiver, and at least one antenna 410 is provided to receive the forward link communication signal (eg, from satellite 300), and the forward link communication signal is It is forwarded to an analog receiver 414 where it is downconverted, amplified and digitized. Duplexer element 412 is often used to enable the same antenna to provide both transmit and receive functions. Alternatively, the UT transceiver may utilize separate antennas for operation at different transmit and receive frequencies.

  Digital communication signals output by analog receiver 414 are forwarded to at least one digital data receiver 416A and at least one searcher receiver 418. As will be apparent to those skilled in the relevant art, additional digital data receivers (e.g., as represented by digital data receiver 416N) may be desired depending on the acceptable level of transceiver complexity. It may be used to obtain a level of signal diversity.

  At least one user terminal control processor 420 is coupled to the digital data receivers 416A-416N and the searcher receiver 418. Control processor 420 provides, among other functions, basic signal processing, timing, power and handoff control or coordination, and selection of the frequency used for the signal carrier. Another basic control function that may be performed by control processor 420 is the selection or manipulation of the function to be used to process various signal waveforms. Signal processing by control processor 420 may include determination of relative signal strength and calculation of various associated signal parameters. Such calculations of signal parameters such as timing and frequency may include the use of additional or separate dedicated circuits to provide improved efficiency or speed in measurement, or improved allocation of control processing resources.

  The outputs of digital data receivers 416A-416N are coupled to digital baseband circuitry 422 in UT400. Digital baseband circuitry 422 includes, for example, processing and presentation elements used to transfer information to and from UE 500, as shown in FIG. Referring to FIG. 4, when diversity signal processing is utilized, digital baseband circuit 422 may include a diversity combiner and decoder (not shown). Some of these elements may also operate under the control of control processor 420 or in communication with control processor 420.

  When audio data or other data is prepared as an output message or communication signal starting from UT 400, digital baseband circuit 422 receives, stores, processes and otherwise prepares the desired data for transmission. Used for Digital baseband circuitry 422 provides this data to transmit modulator 426 operating under control of control processor 420. The output of transmit modulator 426 is forwarded to power controller 428, which provides output power control to transmit power amplifier 430 for final transmission of the output signal from antenna 410 to the satellite (eg, satellite 300).

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

  In the example shown in FIG. 4, UT 400 also includes an optional local time, frequency, and / or location reference 434 (eg, a GPS receiver), which may be local time, frequency, and / or Location information may be provided to control processor 420 for various applications including, for example, time or frequency synchronization for UT 400.

  Digital data receivers 416A-416N and searcher receiver 418 are configured with signal correlation elements to demodulate and track specific signals. While searcher receiver 418 is used to search for pilot signals or other relatively unchanged patterns of strong signals, digital data receivers 416A-416N may be other signals associated with detected pilot signals. Is used to demodulate. However, digital data receiver 416 may be responsible for tracking the pilot signal after acquisition to properly determine the ratio of signal chip energy to signal noise and to determine pilot signal strength. Thus, the outputs of these units may be monitored to determine the energy in the pilot signal or other signals, or their frequency. These receivers also utilize frequency tracking elements that can be monitored to provide current frequency and timing information to the control processor 420 for the signal being demodulated.

  Control processor 420 may use such information to appropriately determine how far the received signal is offset from the frequency of the oscillator when scaled to the same frequency band. This and other information regarding frequency error and frequency shift may be stored in a storage or memory element (eg, memory 432) as desired.

  Control processor 420 may also be coupled to UE interface circuit 450 to enable communication between UT 400 and one or more UEs. Because UE interface circuit 450 may be configured as desired for communication with various UE configurations, various may be used depending on various communication techniques utilized to communicate with various supported UEs. It may include a transceiver and associated components. For example, UE interface circuit 450 may include one or more antennas, wide area network (WAN) transceivers, wireless local area network (WLAN) transceivers, local area network (LAN) interfaces, public switched telephone network (PSTN) interfaces, and the like. And / or other known communication techniques configured to communicate with one or more UEs in communication with UT 400.

  Control processor 420 may independently or cooperatively perform handoff information related operations for UT 400 as taught herein, one of processing circuitry 442, memory device 444, or handoff controller 446 or May contain more than one. In an exemplary implementation, processing circuitry 442 is configured (eg, programmed) to perform some or all of these operations. In another exemplary implementation, processing circuitry 442 (eg, in the form of a processor) executes code stored in memory device 444 to perform some or all of these operations. In another exemplary implementation, handoff controller 446 is configured (eg, programmed) to perform some or all of these operations. Although illustrated in FIG. 4 as included in control processor 420, in other implementations, one or more of processing circuitry 442, memory device 444, or handoff controller 446 are coupled to control processor 420. Can be separate subsystems.

  FIG. 5 is a block diagram illustrating an example of UE 500, which may also apply to 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 watch, or any type of device capable of interacting with a user. In addition, UE 500 may be a network-side device providing connectivity to various ultimate end-user devices and / or various public or private networks. In the example shown in FIG. 5, UE 500 receives LAN interface 502, one or more antennas 504, wide area network (WAN) transceiver 506, wireless local area network (WLAN) transceiver 508, and satellite positioning system (SPS) reception. Machine 510 may be included. The SPS receiver 510 may be compatible with the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), and / or any other global or regional satellite based positioning system. In an alternative aspect, UE 500 may include, for example, a WLAN transceiver 508 such as a Wi-Fi transceiver with or without LAN interface 502, a WAN transceiver 506, and / or an SPS receiver 510. In addition, UE 500 may or may not include LAN interface 502, additional transceivers such as Bluetooth, ZigBee and other known technologies, WAN transceiver 506, WLAN transceiver 508, and / or SPS. A receiver 510 may be included. Thus, the elements shown for UE 500 are provided merely as an example configuration and are not intended to limit the configuration of the UE in accordance with the various aspects disclosed herein.

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

  Memory 516 is coupled to processor 512. In one aspect, memory 516 may include data 518 that may be sent to UT 400 and / or received from UT 400, as shown in FIG. Referring to FIG. 5, memory 516 may also include stored instructions 520 that will be executed by processor 512 to perform, for example, processing steps to communicate with UT 400. Further, the UE 500 may also include a user interface 522, which is hardware and for communicating the input or output of the processor 512 to the user, for example through light, sound or tactile input or output. It may include software. In the example shown in FIG. 5, the UE 500 includes a microphone / speaker 524, a keypad 526, and a display 528 connected to the user interface 522. Alternatively, the user's tactile input or output may be integrated with the display 528, for example by using a touch screen display. Again, the elements shown in FIG. 5 are not intended to limit the configuration of the UE disclosed herein, and the elements included in UE 500 are the final usage of the device and the design choice of the system engineer It will be understood to change based on

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

  In the example shown in FIG. 1, two UTs 400 and 401 may perform two-way communication with satellite 300 via the return service link and forward service link within beam coverage. A satellite may communicate with more than two UTs in beam coverage. Thus, the return service link from UTs 400 and 401 to satellite 300 may be a many-to-one channel. For example, some of the UTs may be mobile, while other UTs may be stationary. In satellite communication systems, such as the example shown in FIG. 1, multiple UTs 400 and 401 within beam coverage may be time division multiplexed (TDM'ed), frequency division multiplexed (FDM'ed), or both May be

UT Handoff At some point, the UT may need to be handed off to another satellite (not shown in FIG. 1). Handoffs may be triggered by scheduled or unscheduled events.

  Several examples of hand-offs due to scheduled events follow. Inter-beam and inter-satellite handoffs can be caused by satellite motion, UT motion, or satellite beam off (eg, due to geostationary satellite (GEO) constraints). The handoff may also be due to the satellite moving out of range of the GN while the satellite is still in the UT line of sight.

  Several 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). Handoffs can also be triggered due to degradation of channel quality (eg, signal quality) due to rainfall attenuation or other atmospheric conditions.

  In some implementations, at a particular point in time, a particular satellite may be controlled by a particular entity (eg, network access controller, NAC) in the GN. Thus, the GN may have several NACs (eg, implemented by the GN controller 250 of FIG. 2), each of which controls a corresponding one of the satellites controlled by the GN. In addition, a given satellite may support multiple beams. Thus, over time, different types of handoff may occur.

  In inter-beam handoff, the UT is handed off from one beam of satellites to another beam of satellites. For example, the particular beam serving the stationary UT may change with time as the serving satellite moves.

  In 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 as the target satellite moves towards the UT.

Idle Mode Handoff In a satellite network, UTs in idle mode should point towards the best satellite and beam to receive pages for idle UTs. Similarly, the GN should page to an idle UT using the same satellite beam. In practice, selection of the correct satellites and beams may be difficult (eg, relatively complex), as satellites and beams are known to the GN but to the idle UT. Because it may be turned off for various reasons. As a result, an idle UT may be able to point to a different satellite than what the GN uses to page the idle UT.

  To address this issue, the present disclosure, in some aspects, enables a network-initiated idle mode handoff procedure that enables an idle UT to reliably receive paging messages sent by a GN. About. To receive a page, an idle UT identifies a satellite that will provide coverage for the idle UT at that time, and directs an antenna to that satellite. This causes the idle UT to then tune into the beam that the satellite will transmit in, camp on the corresponding cell, and control channel to determine if there is a page for the idle UT. It becomes possible to monitor.

  In some aspects, the network-induced idle mode handoff algorithm may be performed by the UT when the UT is in idle mode (eg, periodically or non-periodically) or as needed. And providing the idle UT with information that can be used to perform the reselection. This information may be referred to as idle mode information. The UT may maintain this information in the idle mode handoff table.

  The idle mode information may take various forms. In some cases, the idle mode information then indicates a train of satellites that covers the idle UT for a period of time, so that the idle UT will then point to the correct satellite (eg, at the designated time) Pages can be received. In some cases, the idle mode information includes start times for a set of satellites, and each particular start time indicates when an idle UT can handoff to the corresponding satellite. Thus, in some aspects, the application relates to network induced idle reselection, where the UT is directed by the network to the appropriate list of satellites for idle mode operation.

  In some scenarios, an idle UT requests idle mode handoff information from the GN. In some scenarios, an idle UT sends a request for idle mode handoff information to the GN when the idle UT has a defined number of valid entries remaining in the idle mode handoff table. obtain. For example, an idle UT may send a request when only one unexpired entry remains in the table. In some scenarios, an idle UT may send a request for idle mode handoff information to the GN when the idle mode handoff table is about to expire or has expired. In some scenarios, an idle UT may send a request for idle mode handoff information to the GN based on the time associated with a particular entry (eg, the last entry) of the idle mode handoff table.

  The request may include, for example, the start time of the last entry in the current idle mode handoff table at the UT and the location of the UT. This information allows the GN to determine the next set of satellites that will cover an idle UT, and to determine when to send an indication of the next set of satellites to the UT.

  In some scenarios, the GN may transmit idle mode information to the UT during wireless connection operation. For example, an idle UT may send a request for idle mode handoff information to the GN when the idle UT establishes a wireless connection with the GN. As another example, the GN may transmit idle mode handoff information to idle UTs autonomously (eg, without a request from the idle UT) when the idle UT establishes a wireless connection with the GN. It can.

Exemplary Handoff Signaling The present disclosure, in some aspects, relates to signaling to support idle mode handoff. FIG. 6 shows a communication system 600 that includes a first device 602 and a second device 604. The first device 602 includes a transmitter 608 that can maintain (eg, generate) idle mode handoff information (eg, a table) 606 and send idle mode handoff information 610 to the second device 604. The second device 604 includes a receiver 612 for receiving idle mode handoff information 610 so that it can maintain local idle mode handoff information 614. In some aspects, the first device 602 may be an example of the GN 200 or GN 201 of FIG. In addition, the second device 604 may be an example of the UT 400 or UT 401 of FIG.

  In some implementations, communication system 600 is a satellite communication system. FIG. 7 shows UT 702 in communication with GN 704 via satellite 706 in non-geostationary satellite communication system 700, such as the LEO satellite communication system for data communication, voice communication, video communication, or other communication. . UT 702, GN 704, and satellite 706 may correspond to, for example, UT 401, GN 200, and satellite 300 of FIG.

  GN 704 includes a network access controller (NAC) 712 for each of the NAC 712 to communicate with UT 702 and other UTs (not shown) via satellite 706 (or some other satellite not shown). It interfaces with one or more radio frequency (RF) subsystems 714. GN 704 also includes a core network control plane (CNCP) 716 and a core network user plane (CNUP) 718, or other similar functionality for communicating with another network 720. Network 720 may represent, for example, one or more of a core network (eg, 3G, 4G, 5G, etc.), an intranet, or the Internet.

  At various times, GN 704 may determine (eg, receive or generate) idle mode handoff information 722. The GN may then broadcast or unicast idle mode handoff information 722 to UT 702 via messages 724 and 726 relayed by satellite 706. UT 702 thus maintains unique idle mode handoff information 728. The GN 704 may transmit idle mode handoff information 722 to the UT responsive to the request from the UT or autonomously (eg, not responding to the request).

  In one exemplary implementation, the request for the idle mode handoff table may include two fields. The first field contains the start time of the last row entry of the current table (e.g. absolute GPS time). If the UT does not have a current table, the start time may be set to zero. This first field may be 32 bits or some other size. The second field contains the position of the UT corresponding to the last received table (e.g. this field may be used only for moving UTs). This field may be 32 bits or some other size. In some implementations, the request also includes (eg, in a separate field) an indication of the current idle mode handoff table's expiration time at the UT (eg, an indication of how long the table will remain valid). obtain.

  The disclosure relates in some aspects to using unicast signaling based transfer of idle mode handoff information (eg, idle mode handoff table). In some aspects, unicast signaling may provide greater flexibility than idle mode updates based on broadcast information blocks (eg, unicast signaling may be more adaptable to future developments).

  FIG. 8 shows an example of a signaling call flow 800 for providing handoff information (eg, a handoff table) to an idle UT. Signaling call flow 800 includes request-response pairs of wireless messages, which may be based on, for example, a network-induced idle mode handoff algorithm.

  In some aspects, request-response pairs of messages may be exchanged between UT 802 and GN 804 when the UT is wirelessly connected and when security is active (806). That is, the radio request-response message may be used to provide an idle mode handoff table to the wirelessly connected UT, and the table may be provided after security has been activated.

  The idle mode handoff table request message 808 may be sent (or may be sent simultaneously) after the UT location information is sent. For example, request message 808 may be provided simultaneously with wireless UT location report message 810.

  In some aspects, the GN may use the UT location information to prepare an idle mode handoff table for the UT. For example, the GN may determine which satellites may be able to service the UT for a given period of time based on the satellite ephemeris information and the position of the UT. The GN then sends an idle mode handoff table response message 812 containing this satellite information to the UT, which updates the UT's table 814.

  In some implementations, the GN may determine whether to send the idle mode handoff table to the UT based on the current idle mode handoff table's lifetime at the UT. In some cases, the GN may receive this lifetime indication from the UT (eg, in an idle mode handoff table request message). In some cases, the GN may track this lifetime on its own (e.g., based on the lifetime that the GN calculates for the last table it sent to the UT).

  In some implementations, the GN sends the idle mode handoff table to the UT based on the time (e.g., start time) associated with the current idle mode handoff table entry (e.g., last entry) in the UT. You can decide whether or not. In some cases, the GN may receive an indication of this time (eg, in a handoff table request message) from the UT. In some cases, the GN may track this time itself (eg, by storing the last table that the GN sent to the UT).

  In view of the above, the disclosure relates in some aspects to transmitting to the UT at least one satellite indication for idle mode operation of the UT. Here, the indication of the at least one satellite may take the form of a satellite table, a satellite list, or some other form. For each satellite of the at least one satellite (eg, in the satellite list), an indication may also be sent to the UT indicating the time at which the UT should handoff to the satellite. An indication of at least one carrier frequency that the next satellite cell (eg, the cell of the next satellite that will service the UT) will use for transmission may also be sent to the UT.

  In some aspects, the determination of whether to send an indication is: 1) location of UT, 2) start time of entry (eg, last entry) in current idle mode handoff table, 3) idle mode handoff It may be based on the number of valid entries in the table, or 4) their combination. In some aspects, the determination to send the indication may be based on the last available idle mode handoff table availability time provided by the GN to the UT. The above information allows the GN to determine if the UT is likely to run out of current satellite information. As a result, the GN may send a new table to the UT if the last table sent to the UT is likely to run out of valid entries, or if the table is likely to expire.

Exemplary handoff table
The GN may send idle mode handoff information (eg, autonomously or in response to a request) via an idle mode handoff table. An exemplary idle mode handoff table is shown in Table 1 (Table 1). The reference time of the table (eg, in seconds) may be, for example, absolute GPS time (eg, 32 bits). This table is updated with time (eg, as the satellites move and / or as the UTs move). It should be understood that different handoff tables may include different types of information and / or different entries.

  In one exemplary implementation, the handoff table may include three fields that follow. The first field is for table reference time (e.g., in seconds): absolute GPS time (e.g., 32 bits). The second field is for satellite ID (e.g., 16 bits). Table 1 shows an example of this field. As shown, the second field may also indicate outage periods where the satellite does not cover the UT (eg, due to EPFD mitigation). The third field is for start times: startTime1, ..., startTimeN (eg, 32 bits each). Table 1 also shows an example of this field. These times may be chosen such that GN can specify a sufficiently long period relative to the reference time during which the entries in the table are valid.

  The size of the handoff table provided to the UT may depend on whether the UT is stationary or moving. In general, smaller handoff tables may be used for the moving UT, such that the size of such a handoff table may depend on the speed at which the UT is moving.

  For UTs moving at high speeds (e.g., UTs on an aircraft), smaller tables may be provided as the tables may become invalid sooner as the UT moves. Such a table may for example be valid for several minutes.

  For UTs traveling at low speeds (eg, UTs on a cruise ship or cargo ship), larger tables may be provided. Such a table may for example be valid for one hour.

  For stationary UTs, to reduce overhead due to the establishment of a new connection (eg, as discussed below in Option 1) or by signaling overhead (eg, as discussed below in Option 3) Large tables can be provided. Such a table may be valid, for example, for several hours (e.g. 10 hours).

  The GN can estimate the speed of the UT based on the position reports that the GN receives from the UT. Combining this information with the information received in the request message regarding when the current table at the UT is valid, the GN can optimize the size of the table that the GN provides to the UT that it is moving. This is to achieve a good trade-off between the signaling overhead incurred in transmitting the table and the period in which the table provided for the moving UT can remain valid. Can help.

  Outage periods may exist for different reasons under different circumstances. For example, one or more satellites may become inactive (e.g., for a period of time otherwise the UT would be in coverage of those satellites), thereby providing service. It may not be possible. As another example, service constraints (e.g., by regulatory constraints or countries) can prevent the UT from receiving service from a particular satellite (e.g., the service is always constrained at a certain time or at a certain location). Constraints) may be specified.

  In some aspects, outage period information may be used by the UT to determine whether to stay in or enter a low power (eg, sleep) mode. For example, a UT in idle mode or entering idle mode may decide to be able to sleep between startTime2 and startTime3, based on Table 1 (Table 1).

Triggers to Request or Send Idle Mode Handoff Information Various types of triggers may be used to determine when to request or send idle mode handoff information (eg, an idle mode handoff table). A trigger that can be used to determine when the UT requests idle mode handoff information, or a trigger that can be used to determine when the GN (or some other type of device) transmits idle mode handoff information Some examples of will follow.

  The first request trigger is based on the number of valid entries remaining in the set of idle mode handoff information (eg, idle mode handoff table) maintained by the UT (or some other suitable device). For example, the UT may send a request for idle mode handoff information based on the number of valid entries (eg, 1, 2, etc.) remaining in the idle mode handoff table maintained by the UT. As a specific example, the UT sends a request for idle mode handoff information to the GN if the idle mode handoff table contains only one valid entry (or two valid entries, or three valid entries etc) It can. In this way, the UT can obtain a new idle mode handoff table from the GN before there are no valid (e.g., latest) entries from the idle mode handoff table maintained by the UT. In some aspects, entries in the table may be considered invalid (e.g., not current) after the time associated with the entry (e.g., start time, end time, etc.) has elapsed.

  The second request trigger is based on the timing of the entry of a set of idle mode handoff information (eg, idle mode handoff table) maintained by the UT (or some other suitable device). For example, the UT may be based on the timing (eg, start time, end time, etc.) associated with a particular entry (eg, last entry, penultimate entry, etc.) of the idle mode handoff table maintained by the UT. , Request for idle mode handoff information may be sent. In a particular example, the UT has a difference between the current time and the time (eg, start time, etc.) for a particular entry (eg, the last entry) of the idle mode handoff tail is less than a threshold length of time In some cases, a request for idle mode handoff information may be sent to the GN. In this way, the UT is new from the GN before the latest entries are exhausted from the idle mode handoff table maintained by the UT (e.g. before the entries are no longer in the table or before the table is no longer valid). An idle mode handoff table can be obtained.

  The third request trigger is based on the combination of the first request trigger and the second request trigger. For example, if the idle mode handoff table contains only one valid entry, or if the difference between the current time and the last entry time is less than the threshold time length, then the UT is idle mode handoff information Request for can be sent to GN. Other combinations may be used in other scenarios.

  In some scenarios, the GN (or some other suitable device) may use the UT's table (or some other device) to determine when to transmit idle mode handoff information (eg, idle mode handoff table) Table) can be tracked. Such a scenario may occur, for example, if the UT (or some other device) does not send a request for a new table.

  The first transmission trigger is based on how much idle mode handoff information (eg, idle mode handoff table) sent to the UT (or some other suitable device) remains valid. For example, the GN (or some other suitable device) may send idle mode handoff information to the UT based on the remaining lifetime of the UT's idle mode handoff table. In a particular example, the GN may send a new idle mode handoff table to the UT if the remaining lifetime of the last idle mode handoff table that the GN sent to the UT is less than the threshold time length. In this way, the GN may provide the UT with a new idle mode handoff table before the UT's held idle mode handoff table becomes invalid.

  Other triggers for transmitting idle mode handoff information may be similar to the first request trigger, the second request trigger, and the third request trigger. For example, the GN may determine the time (eg, start time) for a particular entry (eg, the last entry) in the UT's idle mode handoff table based on the number of valid entries remaining in the UT's idle mode handoff table. Idle mode handoff information may be sent on the basis of, or a combination of these triggers.

Example message
The GN (or some other suitable device) may send various types of information to an idle UT (or some other suitable device). In some scenarios, this information may be sent via a Broadcast Information Block (BIB) message. In one exemplary implementation, this information indicates at least one carrier frequency (eg, absolute radio frequency channel number) that the next cell will use to transmit. This information may be carried by a 16-bit (or other size) parameter called "nextCellTransmitFreq". As an example, nextCellTransmitFreq may indicate a list of possible frequencies that may follow. As another example, nextCellTransmitFreq may indicate a particular frequency. It should be understood that nextCellTransmitFreq may take other forms. It is assumed that the satellites will transmit using a limited number N (eg, 8 or some other suitable number) of carrier frequencies on the forward service link (FSL) over a given area Ru. The set of N carrier frequencies may vary from region to region.

  The UT may perform the following operations to align with the satellite's beam. When the UT switches from one satellite to another according to the idle mode handoff table, the UT may perform a search over N frequencies and select one frequency to camp on. The UT may use nextCellTransmitFreq information when switching from one beam of satellites to another beam of satellites. For example, when the UT is covered by a satellite, the UT may use the nextCellTransmitFreq information to determine the next beam that the UT is to align.

Exemplary Signaling Some examples of signaling and UT procedures based on the above follow. These examples are called Option 1, Option 2, Option 3, and Option 4.

  In option 1, the idle UT sends a request message to the GN when only one entry remains in the UT's current table. Here, the UT establishes a wireless connection to the GN and sends a request message. The UT radio layer may trigger the control layer to initiate a service request procedure to establish a wireless connection to the GN. Upon receipt of the request message, the GN sends a response containing the new handoff table to the UT. When the UT receives the response message, it replaces the current table with a new one.

  In option 2, the UT does not send a request message. Instead, GN maintains, for each UT, information about the last table validity time that GN provided UT. Whenever the UT establishes a wireless connection to the network, the GN checks if a new table needs to be provided with the UT and sends a new table if necessary. In some cases, the GN may send a new table after the GN receives from the UT a wireless location report message indicating the location of the UT.

  In option 3, the UT sends a request message to the GN each time the UT establishes a wireless connection to the GN. Based on the information provided in the request message, the GN determines whether a table needs to be provided to the UT. For example, a stationary UT need not be provided with a new table if the UT has an entry for a sufficient time in the future. For a moving UT, the GN provides a table to the UT based on the information provided in the request message (eg, as discussed with respect to table sizes for the stationary UT and the moving UT). The size of the can be optimized. When the UT receives a response message from the GN, the UT may replace the duplicate entry and add a new entry to the current table.

  Option 2 varies when the UT has uplink (UL) data to send, or when the UT responds to a page, or when a periodic timer (eg, a 54 minute period) expires It enables the procedure to piggyback on the wireless connection established by the UT. Thus, in these scenarios, it may not be necessary to set up an additional connection to send a request or to receive an idle mode handoff. In some implementations, the timer may be a paging area update timer. Other types of timers may be used in other implementations.

  Option 4 is a combination of Option 1 and Option 3. For example, the UT may establish a wireless connection to obtain a new table whenever the UT approaches the end of the current table. In addition, the UT may request a table whenever a wireless connection is established for other reasons. An example of option 4 follows.

  When an idle UT discovers that only one entry remains in the UT's current table, the UT radio triggers the control layer to initiate a service request procedure to establish a radio connection to the GN Do. The UT then sends a handoff request over the connection, and the GN responds by providing a new table to the UT. The UT then replaces the current table with a new one.

  As discussed above, stationary UTs and moving UTs may have different constraints. Stationary UTs may benefit from large tables (10 hours or more) to reduce connection overhead. A moving UT may use a smaller table because large movements can invalidate the table. Thus, the amount of handoff information sent by the GN may be based on the movement (eg, speed) of the UT.

  As discussed above, the UT may send a handoff table request message whenever it obtains a radio connected to the GN. Upon receiving this message, the GN determines if the UT should be provided a table. A stationary UT does not have to be provided with a new table if the UT's current table has an entry for a sufficient future time. For moving UTs, GN can provide smaller sized tables. When the UT receives the response message, it can add to the handoff table (eg, replace duplicate entries).

Exemplary Timeline FIG. 9 is an exemplary illustration of idle UT when idle UT switches from the first satellite (designated SAT1) to the second satellite (designated SAT2) according to the handoff table. The timeline 900 is shown. This example is for a UT having two parabolic antennas. In the exemplary implementation, a worst case time 902 is shown for the UT's antenna (e.g., antenna 2) to complete its rotation and to face SAT2. In an exemplary scenario, such an antenna may take about 5 minutes to rotate an elevation of 90 degrees (e.g., the minimum elevation sweep rate at a particular azimuthal angle is 18 degrees / second) is there).

  At time 904, the UT's antenna (antenna 2) begins to rotate and point towards SAT2. At time 906, the UT reads the BIB in the current cell to find the next cell to combine. At paging occasion (PO) 908, the UT monitors the control channel in the subframe using another antenna (eg, antenna 1) to determine if there is a page for UT 910. At SAT2 start time 912, the antenna 2 of the UT faces the second satellite SAT2. At time 914, the UT measures the FSL frequency in the next cell to be camped on. For example, the UT may measure for 120 milliseconds, or some other time period. At time 916, the UT reads and processes BIB1. For example, the UT may perform these operations for 85 milliseconds, or some other time period. The UT joins the page during PO918. In one exemplary implementation, the page period 920 is 1280 milliseconds.

Additional Handoff Operation Referring to FIG. 10, various aspects of the present disclosure relate to the handoff of UT 1002 in communication with GN 1004 via satellite 1006 in satellite communication system 1000. In some implementations, system 1000 can be a non-geostationary satellite communication system, such as a global low earth orbit (LEO) satellite communication system for data communication, voice communication, video communication, or other communication. The UT 1002 is an example of the UT 400 or UT 401 of FIG. GN 1004 is an example of GN 200 or GN 201 of FIG. The satellite 1006 is an example of the satellite 300 of FIG.

  In some aspects, GN 1004 and UT 1002 use satellite and cell transition information 1008 to determine when to hand-off UT 1002 from one cell to another and / or from one satellite to another. For example, UT 1002 may transmit UT information 1010 (eg, capability information, location information, or other information) to GN 1004 via first signaling 1012. Based on the information 1010, the GN 1004 or some other entity generates satellite and cell transition information 1008 and transmits the information 1008 to the UT 1002 via the second signaling 1014. Alternatively, or additionally, the GN 1004 or some other entity selects a handoff procedure for the UT 1002 based on the information 1010. In some aspects, the UT 1002's handoff to a different satellite (new serving satellite) involves the UT 1002 performing satellite signal measurements and transmitting a measurement message 1016 to the GN 1004. In some aspects, GN 1004 generates new satellite and cell transition information as a result of receiving measurement message 1016 (eg, modify satellite and cell transition tables).

  UT 1002 may perform other handoff related operations in accordance with the teachings herein. In some aspects, UT 1002 may receive satellite ephemeris information via GN 1004 and synchronize to a satellite (eg, satellite 1006) using satellite ephemeris information. In some aspects, UT 1002 invokes a radio link failure mode if UT 1002 loses connection to the satellite and / or cell.

  In some aspects, the handoff design may attempt to meet one or more design goals. Examples of such purposes include minimizing signaling during handoff, minimizing outage of data during handoff, or reducing reliance on UT's knowledge of satellite ephemeris data. (For example, instead relying on GN's knowledge of satellite position and UT position).

  In the example of FIG. 10, GN 1004 includes Network Access Controller (NAC) 1018, each of NAC 1018 being via UT 1002 and other UTs (not shown) and satellite 1006 (or some other satellite not shown). It interfaces with one or more radio frequency (RF) subsystems 1020 to communicate. GN 1004 may also communicate with network 1026, core network control plane (CNCP) 1022 and core network user plane (CNUP) 1024, or other similar functions (eg, control planes for other types of networks and User plane function). Network 1026 may, for example, represent one or more of a core network (eg, 3G, 4G, 5G, etc.), an intranet, or the Internet.

  In some implementations, the GN 1004 determines (eg, receives or generates) satellite and cell transition information 1008. For example, NAC 1018 may be configured for all UTs under control of NAC 1018 based on information received via network 1026 (eg, ephemeris information) and information received from UTs (eg, configuration information and measurement messages). Satellite and cell transition information. As another example, NAC 1018 may receive satellite and cell transition information for UTs of NAC 1018 via network 1026 (eg, from network entity 1028).

  Other entities in the system may also generate satellite and cell transition information 1008. In some implementations, the controller 1030 of the network entity 1028 generates satellite and cell transition information 1008, and transmits the satellite and cell transition information 1008 to control components of the system 1000 (eg, during system startup and / or Or at other times). For example, network entity 1028 may transmit satellite and cell transition information 1008 to GN 1004 via network 1026 (eg, a core network, an intranet, or the Internet) or some other data transfer mechanism. For purposes of illustration, network entity 1028 is illustrated as being outside of network 1026. However, network entity 1028 may be part of network 1026.

  Several exemplary aspects of UT, GN, or satellite, which may be used in conjunction with UT handoff in accordance with the teachings herein, are now described. These aspects include, for a given one of these satellite system components, parameters used by the component or other information, parameters assigned to the component, characteristics of the component (eg, capabilities), It may include one or more of the signaling used by the component or the operations performed by the component.

Satellite ID
A satellite identifier (ID) is a unique identifier of a particular satellite in the satellite system. Satellite IDs allow satellites to be uniquely identified (e.g., by UTs) within the satellite system. The satellite ID may be 16 bits or more to enable large scale satellite deployment. In some implementations, the satellite ID is transmitted on the overhead channel and does not need to be read immediately by the UT. The UT and GN may index the ephemeris information table using satellite IDs to locate the satellites and their projection onto the surface of the earth at a given time.

Cell or beam ID
Cell ID is a unique ID of a cell. Similarly, the beam ID is a unique ID of the beam. For convenience, the term cell / beam may be used herein to denote a cell and / or a beam. Cell / Beam ID allows cells / beams from a given satellite to be uniquely identified (eg, by the UT). In some aspects, the cell / beam ID may be detectable by the UT for a very short period of time (eg, the cell / beam ID may be a continuous signature used on cell / beam pilots) ). Thus, the UT may not need to decode the overhead message to find the cell / beam ID. In one non-limiting example, the cell / beam ID may be 2 bits for the GN ID (e.g., 2 bits may be sufficient to have a unique GN that the UT can see). 4 values can be reused throughout the earth), 8 bits for cells / beams directed by GN (eg, GN is approximately 10 satellites × 16 beams / satellites = 160 beams / 10 bits may be included to control GN → 8 bits to uniquely identify a cell / beam. In other implementations, different numbers of bits may be used. Also, satellite spatial diversity may be considered to reduce the number of bits.

UT ability
The UT may exchange UT capabilities with GN at connection time or some other time. Several non-limiting examples of UT capabilities follow.

  The UT may be capable of dual cell / beam sensing. Thus, one UT capability parameter (eg, taking a value of YES or NO) may indicate whether the UT can sense more than one cell / beam. For example, this capability parameter can be detected by the UT sensing and detecting the cell / beam ID of another cell / beam of the same satellite while the UT is actively communicating using the cell / beam of a particular satellite It can indicate whether or not. In some implementations, this capability parameter may be used to indicate whether the UT can support two cells / beams simultaneously. In other implementations, different numbers of cells / beams (eg, three or more) may be supported.

  The UT may be capable of dual satellite sensing. Thus, another UT capability parameter (eg, taking a value of YES or NO) may indicate whether the UT can sense more than one satellite. For example, this capability parameter may indicate whether the UT can sense and detect another satellite's cell / beam ID while the UT is actively communicating using the particular satellite's cell / beam. . In some implementations, this capability parameter may be used to indicate whether the UT can support two satellites simultaneously. In other implementations, different numbers of satellites (eg, three or more) may be supported.

  As discussed in more detail below, the GN may use the sensing capabilities of the UT to determine what type of handoff to use for the UT. For example, if the UT can support only a single cell / beam at a given time, handoff may simply be based on satellite and cell transition tables. Conversely, if the UT can support multiple cells / beams / satellites at a given time, the GN can monitor measurement messages from the UT during handoff, which allows the UT to determine how (eg, The measurement message may influence when and / or where) it is handed off.

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

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

  In some implementations, the tuning time may be capped. For example, the tuning time may indicate the maximum amount of time it will take for the UT to tune from one cell / beam or satellite to another.

  In some implementations, the tuning time can be expressed according to an equation. A non-limiting example of such an equation is a + b * τ, where a is a constant indicating the minimum time length for tuning between satellites, and τ is the current satellite and The difference in angle (in degrees) from the target satellite, and b is the velocity of movement of the UT antenna in degrees of motion per millisecond.

Definition of detuning
Signaling may be utilized to allow the UT to detune for sensing between satellites and sensing between cells / beams. This signaling may be used to define a detuning period for the UT to sense other cells / beams of the same satellite or other satellites.

UT position
The UT location reporting mechanism is utilized for handoff processing and paging so that the GN knows the location of the UT (e.g., continuously or periodically). In some implementations, the UT has reliable Global Positioning System (GPS) positioning.

  For stationary UTs, the UT location reporting mechanism may involve the UT sending to the GN a signaling message that reports the UT's location (eg, GPS coordinates).

  For a moving UT (e.g., a UT in a ship or aircraft), the UT position reporting mechanism may involve the UT sending a signaling message to the GN that reports the speed and direction of the UT. This allows the GN to continuously estimate the position of the UT. Also for moving UTs, the direction and speed information may be relatively stable if the UTs are carried by (eg, attached to) a relatively large container.

  Also, through location related signaling, the UT can be informed of the misalignment that is allowed before a new location update message is needed.

  Some implementations may utilize position tolerance thresholds. Some implementations may utilize GEO fencing. For example, if the UT is beyond the designed boundaries for the satellite and / or GN (eg, the UT is a certain distance apart), the UT may be configured to send a location update to the GN.

Ephemeris Transfer and Update Signaling Ephemeris transfer and update signaling messages may be used to transmit satellite ephemeris data to the UT. In some aspects, ephemeris data includes a geographic description of where a given satellite is at a given time. This data may be used by the UT when looking for the next satellite and cell / beam (eg, after the UT has detected a radio link failure). For example, in some aspects, the UT may use the ephemeris data of a given satellite to determine where to point the UT's antenna (s) at a given time. In some aspects, the GN may send signaling messages including satellite ephemeris data to all connected UTs (eg, whenever there is an update). In some aspects, the UT may request satellite ephemeris data from GN (eg, when the UT establishes a connection).

Satellite and Cell Transition Tables Each satellite beam can be considered as a separate cell, with its own data and control channels, and signals. A GN or some other entity may generate satellite and cell transition tables that provide a list of satellites that the UT may choose to hand off next. The transition table may also strictly define at what time the UT switches from one cell of the next satellite (e.g., corresponding to one beam and / or RF band) to another cell. The transition table may indicate, for some satellites, the cells (eg, beams and / or bands) to be used for each satellite. The transition table may indicate, for each cell (e.g., beam), the frequency of the cell (e.g., a nominal radio frequency or frequency band). The transition table may also indicate the cell ID of each cell (or the beam ID of each beam).

  GN may define satellite and cell transition tables based on various information. In some aspects, the GN may define the table using UT's position (and velocity and direction, if specified). In some aspects, the GN may define a table using satellite positions over time calculated from ephemeris data. In some aspects, the GN may define a table based on information as to whether some cells / beams and / or satellites are turned off at some time.

Table 2 is an example of a satellite and cell transition table. The entries in this table include satellite ID, beam ID, beam frequency (Freq), start time, and end time. This table may also be referred to as a satellite and beam transition table. TA _beam represents the detuning time from one _beam of the same satellite to another. In this example, UT is between the time a ₁ time b _1, satellite 1, will be tuned to the beam 1 (in a frequency F _11). The UT will then tune to satellite 1, beam 2 (on frequency F ₂₁ ) from time b ₁ + TA _beam to time c ₁ and so on.

  In some implementations, the table may be sent in a signaling message by the GN to the UT served by the GN at any time before the UT is handed off to the next satellite.

  In one example, the overhead of satellite and cell transition table messages (assuming that there are two satellites listed in the table) are as follows. Satellite ID = 16 bits, Beam ID = 10 bits, Frequency = 4 bits (assuming 16 beam frequencies per satellite), and Start time and End time = 15 bits.

  The start and end times may be specified in terms of frame numbers. The physical layer may specify to use 10 millisecond (ms) transmission frames for the system. Assuming that satellite handoff occurs every three minutes, the number of frames that can be transmitted during handoff is 18,000. The frame number may be reinitialized from zero after each handoff. Thus, in this example, the number of bits needed to specify the frame number is 15 bits.

In the above example, the total overhead of the message is 1020 bits = 128 bytes (general). Values of a ₁ , b ₁ ,..., n ₁ and TA _beam are specified.

If up to 1000 active users can be served at any time by one beam, and the total downlink (DL) throughput of the beam is about 300 Mbps, then the overhead is overhead = (128 bytes × numUsersBeam) / (total bytes delivered by beam over 3 minutes) = (128 bytes × 1000) / (300 × 10 ⁶ × 3 × 60) = 19 × 10 ⁻⁶ (schematic).

  Table 3 is another example of the satellite and cell transition table. The satellite ID is a unique ID assigned to a satellite in the system. The forward link (FL) band is a positive integer index specifying the transmission frequency band of FL. The return link (RL) band is a positive integer index specifying the transmission frequency band of the RL.

  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). The SFN may be, for example, a sequence number assigned to a 10 ms physical layer transmission radio frame. The UT stops transmission and reception at the beginning of the SFN. For example, if the handoff activation time is specified to be at SFN 5, the UT stops transmitting or receiving in subframe 0 of SFN 5.

  The UT starts transmission or reception in the target cell at the time obtained by adding the handoff activation time and the detuning time. Two examples of UT parameters for the detuning time are inter-cell detuning time and inter-satellite detuning time. These parameters may be included in UT capability information.

Inter-Satellite Handoff FIGS. 11 and 12 show examples of inter-satellite handoff. In these examples, the GN includes a source NAC controlling a first satellite and a target NAC controlling a second satellite. In each case, the UT is first connected to the source satellite (and thus the source NAC) and subsequently handed off to the target satellite (and thus the target NAC). In other implementations, different numbers of NAC and satellites may be supported. Also, in some implementations, a common (eg, the same) entity may support multiple satellites.

  FIG. 11 is an example in which the UT 1102 does not transmit a measurement message. For example, UT 1102 may not support sensing of multiple cells / beams and / or satellites, or UT 1102 may determine that a measurement message does not need to be sent to GN 1104. In this case, to determine when the UT 1102 and GN 1 104 transition to the next cell / beam and / or satellite, and where (for example, to which cell / beam, to which frequency, to which satellite). , Rely on existing satellite and cell transition tables. The UT 1102 is an example of the UT 400 or UT 401 of FIG. GN 1104 is an example of GN 200 or GN 201 of FIG.

  Source NAC 1106 sends control signaling 1108 to UT 1102. The control signaling 1108 may include, for example, measurement information and detuning control information (eg, definition of detuning). In addition, packet data 1110 is exchanged between UT 1102 and source NAC 1106. Source NAC 1106 is an example of NAC 1012 in FIG.

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

  Other handoff triggers may also be utilized. For example, GN 1104 (eg, source NAC 1106) may autonomously determine that UT 1102 needs to be handed off. Such triggers may, for example, be that the current serving satellite is moving out of range of UT 1102, that the satellite is moving out of range of GN 1104 even though it may be in range of UT 1102, or to UT 1102. It may be due to the serving cell / beam being blacked out due to GEO requirements.

  If it is possible to sense another cell / beam and / or satellite while the UT 1102 is connected to the first satellite, then the UT 1102 will signal the default satellite and cell / beam signal strength for handoff. I can find it. The UT 1102 may be assumed to have this satellite's position information to do that. This position information may be obtained from satellite ephemeris data processed by UT 1102. If the signal strength is satisfactory, the UT 1102 only waits for the source NAC 1106 to initiate an inter-satellite handoff process.

  Thus, in the example of FIG. 11, both the UT 1102 and the source NAC 1106 initiate a handoff to a new serving satellite according to the table. For this purpose, the source NAC 1106 performs a handoff process 1114. For example, source NAC 1106 may communicate with target NAC 1116 to initiate a handoff. In some aspects, this may involve synchronizing 1118 queues (eg, packet traffic queues) between NAC 1106 and 1116. Also, because it is known that the time of handoff is early, the user queue may be forwarded early. The target NAC 1116 is an example of the NAC 1012 of FIG.

  The source NAC 1106 then sends the handoff signaling 1120 to the UT 1102. In some aspects, this handoff signaling 1120 may include information that allows the UT 1102 to communicate with the target NAC 1116. In some aspects, this handoff signaling 1120 may include new satellite and cell transition tables (eg, received by the source NAC 1106 from the target NAC 1116).

  The UT 1102 then disconnects from the first satellite (1122) and synchronizes with the second satellite. For this purpose, UT 1102 may send synchronization signaling 1124 for the second satellite to target NAC 1116. In some aspects, this may involve the UT 1102 performing a random access procedure at the second satellite.

  The UT 1102 and target NAC 1116 may then exchange connection signaling 1126 and 1128. In some aspects, this may involve the target NAC 1116 transmitting ephemeris information to the UT 1102 and requesting a channel quality indicator from the UT 1102. In some aspects, UT 1102 may synchronize with the second satellite using ephemeris information.

  Also, various entities may perform various background operations to ensure that packet forwarding takes place properly and any necessary cleanup (eg, cache cleanup) is performed.

  FIG. 12 is an example in which the UT 1202 transmits a measurement message. For example, the UT 1202 needs to send a measurement message to the GN 1204 because the measured channel conditions (eg, signal strength) from the serving satellite or target satellite are not acceptable (eg, the signal strength is too low) It may be decided. In this case, GN 1204 may generate a new satellite and cell transition table based on the measurement message. UT 1202 and GN 1204 are then new to determine when to transition to the next cell / beam and / or satellite and where to transition (eg to which cell / beam, which frequency, to which satellite) Use satellite and cell transition tables. The UT 1202 is an example of the UT 400 or UT 401 of FIG. GN 1204 is an example of GN 200 or GN 201 of FIG.

  As in the case of FIG. 11, source NAC 1206 sends control signaling 1208 to UT 1202. The control signaling 1208 may include, for example, measurement information and detuning control information (eg, definition of detuning). In addition, packet data 1210 is exchanged between UT 1202 and source NAC 1206. Source NAC 1206 is an example of NAC 1012 in FIG.

  At some point, a handoff is triggered (1212). In some cases, the current time, which corresponds to the time for transition from one satellite to the next satellite indicated by the satellite and cell transition table, triggers the handoff. In some cases, a measurement message sent by UT 1202 may trigger a handoff, indicating that nearby satellites are significantly stronger (e.g., associated with stronger received signal strength) than the current serving satellite.

  Other handoff triggers may also be utilized. For example, GN 1204 (eg, source NAC 1206) may autonomously determine that UT 1202 needs to be handed off. Such triggers may, for example, be that the current serving satellite is moving out of range of UT 1202, that the satellite is moving out of range of GN 1204, even though it may be in range of UT 1202, or It may be due to the serving cell / beam being blacked out due to GEO requirements.

  In the example of FIG. 12, UT 1202 may sense another cell / beam and / or satellite while connected to the first satellite. Thus, UT 1202 may perform channel quality measurements (eg, satellite signal strength measurements). For example, UT 1202 may measure signal strength from the current serving satellite (first satellite) and the target satellite (second satellite) (1214).

  The UT 1202 then performs a measurement process, eg, to determine if any channel quality is inappropriate (eg, the signal strength is too low) (1216). If either channel quality is inappropriate, UT 1202 may choose to send measurement message 1218 to source NAC 1206. This measurement message 1218 may, for example, indicate the result of the measurement (eg, signal strength in dB), an indication that the handoff time needs to be increased (eg, because the signal from the source satellite is currently too weak) (eg, It may include an indication that the handoff time needs to be delayed, or some other indication, since the signal from the target satellite is currently too weak.

  Thus, as in FIG. 11, UT 1202 may look for default satellite and cell / beam signal strengths for handoff. Again, UT 1202 may be assumed to have this satellite's position information (eg, obtained from satellite ephemeris data processed by UT 1202) to do that. If the signal strength is not satisfactory, UT 1202 may send measurement message 1218 to source NAC 1206 indicating a satellite different from the default satellite to trigger the handoff process early or to delay it.

  Thus, the source NAC 1206 may make the decision to hand off the UT 1202 to the target satellite and target NAC 1220 based on the satellite and cell transition table and any measurement messages 1218 that the source NAC 1206 receives from the UT 1202. Thus, as shown in FIG. 12, the source NAC 1206 performs some handoff process 1222. For example, the source NAC 1206 should either need to accelerate the handoff (early handoff) or need to delay (delayed handoff) based on the measurement message 1218, or some other satellite should be selected as a target. You can judge if there is any. In addition, source NAC 1206 may communicate with target NAC 1220 to initiate a handoff. In some aspects, this may involve synchronizing queues 1224 (eg, packet traffic queues) between NACs 1206 and 1220. The target NAC 1220 is an example of the NAC 1012 of FIG.

  The source NAC 1206 then sends a handoff signaling 1226 to the UT 1202. In some aspects, this handoff signaling 1226 may include information that enables the UT 1202 to communicate with the target NAC 1220. In some aspects, this handoff signaling 1226 may include new satellite and cell transition tables (eg, received by the source NAC 1206 from the target NAC 1220).

  The UT 1202 then disconnects from the first satellite (1228) and synchronizes with the second satellite. For this purpose, UT 1202 may send synchronization signaling 1230 for the second satellite to target NAC 1220.

  The UT 1202 and target NAC 1220 may then exchange connection signaling 1232 and 1234. In some aspects, this may involve the target NAC 1220 transmitting ephemeris information to the UT 1202 and requesting a channel quality indicator from the UT 1202. Again, various entities may perform various background operations to ensure that packet forwarding is done properly and any necessary cleanup (eg, cache cleanup) is performed.

  With normal inter-satellite handoff, the hybrid automatic repeat request (HARQ) process may be terminated. However, since the source NAC can know exactly when the handoff will occur, it can ensure that the forward link data buffer is empty. Also, since the handoff time is known, data flow gaps can be minimized.

Inter-Beam Handoff Inter-cell / inter-beam handoff is performed synchronously by the GN and UT according to timelines specified in the satellite and cell transition tables. Using the detuning period or dual reception capability, the UT detects the presence of the next cell / beam specified in the satellite and cell transition table. If the UT succeeds in detecting the next cell / beam, normal cell / inter-beam handoff is performed without any signaling between UT and GN.

  With normal cell / beam handoff, the forward link HARQ process may be carried over from one cell / beam to the next. In addition, when the UT is handed off from one cell / beam to the next, the reverse assignment may be canceled. For example, the UT may instead send a new request message to send reverse link data.

Exceptional scenario
If the UT loses its current serving cell / beam before expiration of a specified time in the satellite and cell transition table, the UT enters Radio Link Failure (RLF) mode. In RLF mode, the UT may attempt to find alternative cells / beams or satellites (eg, based on ephemeris information in the UT). For example, the UT may attempt to connect to the next satellite to service the UT. If the UT succeeds in establishing another connection, the UT can send a signaling message to the GN to continue communication, where the UT quits before the RLF.

  While being served by one cell / beam, the UT may not detect the next cell / beam specified in the satellite and cell transition table but may detect another cell / beam. This may occur, for example, in UTs moving at high speeds (eg, UTs attached to an aircraft). 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 the UT has moved since the last time the location update was sent. In response, the GN may transmit the updated satellite and cell transition table. In this case, UT follows the updated table. Alternatively, the GN may initiate a completely new handoff process.

Exemplary Connection Mode Handoff Details Referring now to FIGS. 13-23, various aspects of wireless connection mode handoff will be described in more detail in accordance with the teachings herein. In the following, examples of call flows for various connected mode handoff operations are described. In addition, the following details describe some procedures that may be used to improve handoff performance. In various aspects, these procedures define hand-off measurements, determine when to trigger measurements, determine when to hand-off UT, or to obtain return link synchronization after hand-off. Can be used to decide whether to trigger. For the purpose of illustration, these details are discussed in the context of NAC comprising two components, BxP and AxP, for controlling and / or communicating with the satellites.

  FIG. 13 shows an exemplary deployment of BxP and AxP components in a satellite system. At a given time, UT 1306 communicates with one of AxPs 1308 via satellite 1310 and one of BxPs 1312, where each BxP 1312 includes or is associated with satellite RF subsystem 1314.

  BxP refers to the combination of BCP and BTP (hence the acronym BxP). In some aspects, the BxP may include a wireless network component for controlling satellites. For example, BxP may include, for a given cell / beam of satellites, a corresponding set of digital circuits that serve that cell / beam. Thus, in some aspects, BxP corresponds to a particular antenna. Also, 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, anchor points may be associated with particular areas (eg, administrative areas, borders, etc.). A given AxP may service one or more satellites. Also, a given satellite may service one or more AxPs.

  In the above situation, the UT in connected mode may experience two types of handoff: BxP handoff or AxP handoff. For example, as satellites move in non-GSO satellite systems, the cells / beams used to service a given UT (and hence the circuits and antennas associated with those cells / beams) change with time Do. Thus, in some aspects, BxP handoff may correspond to handoff to a different cell / beam (or antenna, etc.). As another example, rainfall attenuation at a particular cell / beam operating on a first band may force switching to a different band for that cell / beam. Thus, in some aspects, BxP handoff may correspond to handoff to a different band for a given cell / beam. AxP handoffs correspond to handoffs to different anchor points. For example, UTs may be forced to change serving AxP as they may move to different administrative areas. BxP handoff may or may not be associated with AxP handoff.

  In some aspects, the present disclosure below addresses satellite pointing errors that may occur in a satellite communication system. These errors can arise from various causes in the system.

  Graph 1400 of FIG. 14 shows respective expected gain contours 1402 and 1404 from different satellite beams, a first expected beam and a second expected beam. In some aspects, these beam gain contours may be used to determine when to hand off the UT 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 is below the beam gain of the second expected beam (candidate target beam).

  For the first predicted beam, FIG. 14 shows the actual beam gain contours 1406 visible to the UT due to satellite pointing errors. As shown in FIG. 14, the shift 1408 of gain contours due to satellite pointing errors shifts the intersection of the gain contours between the two beam contours from the first intersection 1410 to the second intersection 1412. Thus, at the expected (ideal) handoff time 1414, the gain from the first beam is lower (by the amount shown) than the expected gain 1416, which adversely affects the performance of the handoff. As a result, the signal quality at the UT may be lower than desired just prior to the handoff. To address this issue, the ideal handoff time may be shifted by Δ (to be earlier in time in this example) based on the beam contour shift 1408 due to satellite pointing error. Thus, the handoff occurs at new handoff time 1418. As shown in FIG. 14, the gain 1420 at the new handoff time 1418 may be lower by a Δ gain 1422 than the expected gain 1416 associated with the expected first beam.

  To this end, the UT may perform satellite signal measurements (e.g., inter- and intra-satellite) and transmit this information to the GN. Based on these signals, the GN may correct the handoff time for the UT. Thus, the GN may send updated handoff information to the UT (eg, via the satellite and cell transition table or a subset of the satellite and cell transition table) to account for satellite pointing errors.

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

BxP Handoff The logical BxP can be uniquely identified by a 4-tuple containing a satellite access network (SAN), a GN antenna, a satellite beam, and a forward service link (FSL) frequency, where the GN antenna is shown in FIG. Point to the antenna. A BxP handoff occurs for the UT if the BxP 4-tuple of the UT's connection in wireless connected mode changes.

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

  A BxP handoff occurs either at a handoff time based on a priori information denoted THO_a_priori or at a new handoff time recalculated using UT measurement reports denoted THO_recalc (eg 14) THO_recalc = THO_a_priori ± Δ.

  If the satellite antenna pointing error is well known a priori, then the BxP handoff shall be initiated by the UT based solely on the UT's satellite handoff table (e.g., satellite and cell transition tables). Otherwise, the BxP handoff may require UT measurement of the target cell and subsequent measurement reporting by the UT to the source AxP, based on which the source AxP updates the UT's satellite and cell transition tables. .

BxP Handoff-Feeder Link Switching Referring again to FIG. 13, a first configuration 1302 and a second configuration 1304 illustrate a feeder link switching BxP handoff. Each satellite has dual feeder link connections to two GNs, but only one feeder link connection is active at any one time. The dual feeder link connection allows instant switching of the active feeder link connection at the satellite. Feeder link switching appears as a peer handoff, where the UT hands over to the same satellite, the same cell, and the same frequency. However, a feeder link switching BxP handoff can also be made to occur at the same time as a cell handoff to several UTs, in which case the target cell is different from the source cell.

  The call flow for the feeder link switched BxP handoff is the same as shown in FIGS. 15 and 17 discussed below. The call flow of FIG. 15 is applicable when the UT does not need to perform a random access procedure to achieve RL synchronization after feeder link switching has occurred. The call flow of FIG. 17 is applicable if the UT needs to perform a random access procedure to achieve RL synchronization after feeder link switching has occurred.

BxP Handoff-Non-Random Access FIG. 15 shows the call flow for non-random access based BxP handoff without UT measurement and measurement reporting. A typical use case is intra-satellite BxP handoff. The call flow is between UT 1502, source BxP 1504, target BxP 1506, source AxP 1508, and GN 1510.

  A description of the steps in the non-random access based BxP handoff call flow without UT measurement and measurement reporting is given below. Initial packet data flow is represented by lines 1512, 1514 and 1516.

  At point 1518, the source AxP 1508 pre-configures the target BxP 1506 for handoff prior to the handoff activation time (eg, prior to THO_a_priori) (eg, 1 second ago). In step 1A, the source AxP 1508 sends a radio connection reconfiguration message to the UT 1502. In step 1 B, the message is sent to UT 1502 well in advance of the handoff activation time so that UT 1502 has an appropriate time to receive the message. This message may include satellite handoff information, such as transition table rows (eg, indicating handoff activation time) and other parameters. The UT 1502 starts the timer T-4. If T-4 expires (eg, a handoff failure occurs), UT 1502 performs a wireless connection re-establishment procedure.

  In steps 2A and 2B, both the UT 1502 and the source AxP 1508 simultaneously at the handoff activation time (eg, in THO_a_priori, based on the single row of the satellite and cell transition table included in the wireless connection reconfiguration message in step 1). ) Prepare for BxP handoff. Thus, UT 1502 prepares to handoff from source BxP 1504 to target BxP 1506, and source AxP 1508 prepares to handoff UT 1502 from source BxP 1504 to target BxP 1506.

  In step 3, UT 1502 resets the medium access control (MAC) state. The UT 1502 then obtains a new cell (eg, FL sync).

  In step 4, after handoff activation + inter-cell detuning time, the target BxP 1506 sends an UT 1502 a RL Grant + Channel Quality Indicator (CQI) request. The RL grant is addressed to the UT identifier (UT-ID) that the source AxP 1508 assigned to the UT 1502 in the radio connection reconfiguration message (see step 1).

  In step 5, upon receiving the RL grant from the target BxP 1506, the UT 1502 stops timer T-4 (eg, the handoff is successful), CQI report and wireless connection reconnection for transfer to the source AxP 1508 (step 5B) A configuration complete message is sent to the target BxP 1506 (step 5A). The wireless connection reconfiguration complete message does not include an information element (IE), and integrity protection and encryption are performed using old keys (eg, Kint and Kenc, respectively). The final packet data flow is represented by lines 1520, 1522, and 1524.

  FIG. 16 shows the call flow for non-random access based BxP handoff with UT measurement and measurement reporting. A typical use case is intra-satellite BxP handoff. The call flow is between UT 1602, source BxP 1604, target BxP 1606, source AxP 1608 and GN 1610.

  A description of the steps in the non-random access based BxP handoff call flow with UT measurements and measurement reporting follows. Initial packet data flow is represented by lines 1612, 1614 and 1616.

  The radio connection reconfiguration message sent to UT 1602 while UT 1602 is serviced by a given source cell may indicate to UT 1602 when to take measurements for the next target cell. Thus, at point 1617, while in the previous cell, source AxP 1608 may configure UT 1602 with measurement gap information (eg, gap pattern) corresponding to the measurement time. Source AxP 1608 may transmit this information because satellite pointing error may require that satellite handoff be performed at the ideal handoff time ± Δ, thereby forcing the measurement by UT 1602 is there. In steps 1A and 1B, the source AxP 1608 sends a radio connection reconfiguration message to the UT 1602. This message includes measurement gap configuration information and measurement activation / deactivation time (in addition to the handoff activation time and other IEs described herein). In step 3, the UT 1602 measures the signal strength of the target cell according to the measurement gap configuration information received from the source AxP 1608. The packet data flow continues as represented by lines 1618, 1620 and 1622.

  In steps 4A and 4B, the UT 1602 sends a measurement report indicating the signal strength (eg, RSRP) of both the source cell and the target cell to the source AxP 1608 using event based reporting of signal strength. Source AxP 1608 configures UT 1602 to use Event 1 (the source cell goes better than the threshold) as a reference to trigger measurement reporting. Source AxP 1608 sets the threshold low enough so that the signal strength of the source cell is always greater than the threshold, thereby triggering UT 1602 to send a measurement report to source AxP 1608. Similarly, source AxP 1608 configures UT 1602 to use event 4 (the target cell goes better than the threshold) as a reference to trigger measurement reporting. The source AxP 1608 sets the threshold low enough that the signal strength of the target cell is always greater than the threshold, thereby triggering the UT 1602 to send a measurement report to the source AxP 1608. Other reporting criteria may also be used.

  In step 5, based on the UT measurement report (see step 4), the source AxP 1608 calculates a new handoff activation time (eg, THO_recalc), and before the new handoff activation time (eg, before THO_recalc) Preconfigure target BxP 1606 for handoff. For example, based on satellite ephemeris information, beam patterns, and UT measurement reports, source AxP 1608 may prepare BxP handoff to occur at an ideal handoff time ± Δ. In steps 6A and 6B, the source AxP 1608 sends a radio connection reconfiguration message to the UT 1602. The content of the message is described herein, including the new handoff activation time. Optionally, the message may also include measurement gap configuration information and measurement activation / deactivation time. The message is sent to UT 1602 well in advance of the new handoff activation time so that UT 1602 has an appropriate time to receive the message. The UT 1602 starts timer T-4. If T-4 expires (eg, a handoff failure occurs), UT 1602 performs a wireless connection re-establishment procedure. Also, if source AxP 1608 does not timely receive measurement reports from UT 1602, source AxP 1608 uses the old handoff activation time (eg, THO_a_priori) when configuring both targets BxP 1606 and UT 1602 for handoff.

  Both the UT 1602 and the source AxP 1608 simultaneously prepare the BxP handoff at the new handoff activation time (eg, in THO_recalc) based on the single row of the satellite and cell transition table included in the wireless connection reconfiguration message in step 6. Do.

  In step 7, UT 1602 resets the MAC state. The UT 1602 obtains a new cell (eg, FL sync).

  In step 8A, after the handoff activation + inter-cell detuning time, the target BxP 1606 sends an RL grant + CQI request to the UT 1602. The RL grant is addressed to the UT-ID that the source AxP 1608 has assigned to UT 1602 in the radio connection reconfiguration message (see step 3).

  Upon receiving the RL grant from target BxP 1606, UT 1602 stops timer T-4 (eg, handoff is successful) and sends CQI report (step 8A) and radio connection reconfiguration complete message to target BxP 1606 / source AxP 1608 ( Steps 9A and 9B). The wireless connection reconfiguration complete message does not include the IE, and integrity protection and encryption are performed using the old key (eg, Kint and Kenc, respectively). The final packet data flow is represented by lines 1624 1626 and 1628.

BxP Handoff-Random Access FIG. 17 shows the call flow for random access based BxP handoff without UT measurement and measurement reporting. A typical use case is BxP handoff between satellites. The call flow is between UT 1702, source BxP 1704, target BxP 1706, source AxP 1708 and GN 1710.

  A description of the steps in the random access based BxP handoff call flow without UT measurements and measurement reporting follows. The initial packet data flow is represented by lines 1712, 1714 and 1716.

  In steps 1A and 1B, the source AxP 1708 pre-configures the target BxP 1706 for handoff prior to the handoff activation time (eg, prior to THO_a_priori). The source AxP 1708 sends a radio connection reconfiguration message to the UT 1702. The content of the message is described herein. The message is sent to UT 1702 well in advance of the handoff activation time so that UT 1702 has an appropriate time to receive the message. The UT 1702 starts the timer T-4. If T-4 expires (eg, a handoff failure occurs), UT 1702 performs a wireless connection re-establishment procedure.

  In step 2, both the UT 1702 and the source AxP 1708 simultaneously (in THO_a_priori, for example) BxP at the handoff activation time, based on the single row of the satellite and cell transition table included in the radio connection reconfiguration message in step 1. Prepare for the handoff. These operations may be similar to the corresponding operations discussed above in connection with FIG.

  In step 3, the UT 1702 resets the MAC state. The UT 1702 obtains a new cell (eg, FL sync). As represented by brackets 1718, steps 4-7 are not necessary if step 1 does not include an RA procedure command.

  After handoff activation + inter-satellite detuning time, target BxP 1706 sends FL control channel (FLCC) command including dedicated preamble signature to trigger UT 1702 to perform non-contention based random access procedure. Send to UT 1702. This enables the UT 1702 to achieve RL synchronization later.

  In step 4, the UT 1702 transmits a non-contention based random access preamble to the target BxP 1706 on random access. Upon receiving a non-contention based random access preamble from UT 1702, target BxP 1706 verifies the received signature sequence.

  In step 5, the target BxP 1706 sends to UT 1702 a random access response addressed to the appropriate group of UTs (eg, RA-RNTI). The random access response includes paging area (PA), RL grant (including CQI request), and temporary UT-ID.

  The RL grant may include a CQI request if dedicated preamble signatures are used. In this case, the process may skip from point 1720 to step 8B. Otherwise, the operations of block 1722 including steps 6 and 7 and the operation of step 8A may be performed.

  Upon receiving the RL grant + CQI request from target BxP 1706 (eg, in step 8A), UT 1702 stops timer T-4 (eg, a successful handoff) and sends a CQI report (step 8B) to target BxP 1706. If a dedicated preamble signature is used, UT 1702 also sends a radio connection reconfiguration complete message to target BxP 1706 (step 9A) for transfer to source AxP 1708 (step 9B). The wireless connection reconfiguration complete message does not include the IE, and integrity protection and encryption are performed using the old key (eg, Kint and Kenc, respectively). The final packet data flow is represented by lines 1724, 1726 and 1728.

  18 and 19 show the call flow for random access based BxP handoff with UT measurement and measurement report. A typical use case is BxP handoff between satellites. The call flow is between UT 1802, source BxP 1804, target BxP 1806, source AxP 1808 and GN 1810.

  A description of the steps in a random access based BxP handoff with UT measurements and measurement reports follows. Initial packet data flow is represented by lines 1812, 1814 and 1816.

  Referring first to FIG. 18, while in the previous cell, UT 1802 (in addition to the handoff activation time and other IEs described herein) measurement gap configuration information and measurement activation / deactivation. Configured by source AxP 1808 in a wireless connection reconfiguration message with activation time. In step 1, the UT 1802 measures the signal strength of the target cell according to the measurement gap configuration information received from the source AxP 1808. The packet data flow continues as represented by lines 1818, 1820 and 1822.

  In step 2, UT 1802 sends a measurement report to source AxP 1808 that indicates the signal strength (eg, RSRP) of both the source and target cells using event-based reporting of signal strength. Source AxP 1808 configures UT 1802 to use Event 1 (the source cell goes better than the threshold) as a reference to trigger measurement reporting. Source AxP 1808 sets the threshold low enough so that the signal strength of the source cell is always greater than the threshold, thereby triggering UT 1802 to send a measurement report to source AxP 1808. Similarly, source AxP 1808 configures UT 1802 to use event 4 (the target cell goes better than the threshold) as a reference to trigger measurement reporting. Source AxP 1808 sets the threshold low enough so that the signal strength of the target cell is always greater than the threshold, thereby triggering UT 1802 to send a measurement report to source AxP 1808. Other reporting criteria may also be used.

  Based on the UT measurement report (see step 2), the source AxP 1808 calculates a new handoff activation time (eg, THO_recalc) and for the handoff before the new handoff activation time (eg, before THO_recalc) Preconfigure target BxP 1806.

  The operations in steps 3 to 11 correspond to steps 1 to 9 in FIG. Thus, these actions are briefly discussed. In step 3, the source AxP 1808 sends a wireless connection reconfiguration message to the UT 1802. The contents of the message are described herein, including the handoff activation time. Optionally, the message may also include measurement gap configuration information and measurement activation / deactivation time. The message is sent to UT 1802 well in advance of the handoff activation time so that UT 1802 has an appropriate time to receive the message. The UT 1802 starts the timer T-4. If T-4 expires (eg, a handoff failure occurs), UT 1802 performs a wireless connection re-establishment procedure. Also, if source AxP 1808 does not timely receive measurement reports from UT 1802, source AxP 1808 uses the old handoff activation time (eg, THO_a_priori) when configuring both targets BxP 1806 and UT 1802 for handoff.

  In step 4, both the UT 1802 and the source AxP 1808 simultaneously at the new handoff activation time (eg, in THO_recalc), based on the single row of the satellite and cell transition table included in the radio connection reconfiguration message in step 3. Prepare for BxP handoff.

  In step 5, the UT 1802 resets the MAC state. The UT 1802 obtains a new cell (eg, FL synchronization).

  Referring to FIG. 19, after handoff activation + inter-cell detuning time, target BxP 1806 includes a dedicated preamble signature FLCC command to trigger UT 1802 to perform non-contention based random access procedure To the UT 1802. This allows the UT 1802 to achieve RL synchronization later.

  In step 6, the UT 1802 transmits a non-contention based random access preamble to the target BxP 1806 on random access. Upon receiving a non-contention based random access preamble from UT 1802, target BxP 1806 verifies the received signature sequence.

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

  Upon receiving the RL grant + CQI request from target BxP 1806 (step 10A), UT 1802 stops timer T-4 (eg, a successful handoff), sends a CQI report to target BxP 1806 (step 10B), and reestablishes a radio connection. The configuration complete message is sent to the target BxP 1806 / source AxP 1808 (step 11). The wireless connection reconfiguration complete message does not include the IE, and integrity protection and encryption are performed using the old key (eg, Kint and Kenc, respectively). The final packet data flow is represented by lines 1824, 1826 and 1828.

BxP Handoff-Failover In intra-GN's GN antenna failover, the antenna assembly serving the satellite fails. In this case, one of two scenarios is possible. In the first scenario, the UT is managed by GN as part of normal operation (eg, scheduling of FL and RL resources for UT by GN, HARQ retransmission and ARQ retransmission) connections and data Experience a short interruption of service. In the second scenario, there is a significant disruption of connection and data services where the UT experiences loss of FL synchronization or leads to radio link failure (RLF).

AxP handoff
Inter-AxP handoff may be performed for the purpose of load leveling, or for non-stationary UTs that require inter-AxP handoff due to changes in location of the UT resulting in crossing administrative domain boundaries. The AxP handoff procedure comprises three distinct phases: AxP handoff preparation, AxP handoff execution, and AxP handoff completion.

  The following procedure may be used for AxP handoff preparation.

  For Radio Controlled (RC) Acknowledged Mobile (AM) data bearers, per direct RL-AM data bearer for data transfer on both forward and reverse links, if direct transfer of data is applied (In one direction from source AxP to target AxP). Conversely, if an indirect transfer of data is applied, the tunnel may be configured per RL-AM data bearer (from source AxP to target AxP via GN) for data transfer on both forward and reverse links. Can be established).

  For RC unacknowledged mobile (UM) data bearers, if direct transfer of data is applied, the tunnel is for each RL-UM data bearer only for forward link data transfer (from the source AxP Can be established in one direction to the target AxP. Reverse link data is not transferred from the source AxP to the target AxP, but instead is sent to the GN by the source AxP. Conversely, if indirect transfer of data is applied, a tunnel may be established per RL-UM data bearer (in one direction from source AxP to target AxP) for forward link data transfer only . Reverse link data is not transferred from the source AxP to the target AxP, but instead is sent to the GN by the source AxP.

  The following procedure may be used for AxP handoff execution.

  For RL-AM data bearers, the data transferred on the reverse link includes the sequence number (SN). Forward link forwarded data may include the SN, or may not include forward link data if received from the GN without being assigned the SN by the source AxP. The source AxP sends both the forward link SN and the reverse link SN and frame number (FN) information to the target AxP. MAC state and RL state are reset.

  For RL-UM data bearers, the data transferred on the forward link may include the SN, or if the forward link data is received by the source AxP from GN without having yet been assigned the SN, May not be included. If the data transferred on the forward link includes an SN, the target AxP should send this data to the UT first (after resetting both SN and FN). The state is reset (e.g., the SN and FN of the forward and reverse links are reset). MAC state and RL state are reset.

  The following procedure may be used for handoff completion.

  For RL-AM data bearers, the UT can send the list of missing / received Forward Link Protocol Data Units (PDUs) to the target AxP, the target AxP is missing / received reverse A list of directional link PDUs can be sent to the UT. For both RL-AM data bearer and RL-UM data bearer, the forward link tunnel per data bearer is switched from source AxP to target AxP and UT resources are released at source AP.

  FIGS. 20-22 show AxP handoff call flows without mobility management (MM) relocation and without GN relocation. FIG. 20 illustrates the handoff preparation. FIG. 21 illustrates the handoff execution. FIG. 22 illustrates the handoff completion. A description of the steps in the AxP handoff call flow follows below.

  Referring first to FIG. 18, the call flow is between UT 2002, source BxP 2004, target BxP 2006, source AxP 2008, target AxP 2012, mobility management (MM) 2014 (e.g. MM component) and GN 2010 It is in. The initial packet data flow is represented by lines 2016, 2018 and 2020.

  In step 1, the source AxP 2008 makes a decision to hand over the UT 2002 to the target cell and the target AxP 2012 based on the satellite ephemeris information and the beam pattern.

  In step 2, the source AxP 2008 sends a handoff required message to the MM 2014 to request the preparation of resources on the target AxP 2012. This message may be used by the paging area identifier (PAI) of the target AxP 2012 (so that MM 2014 can decide to which target AxP 2012 to send the handoff request message in step 3), direct data transfer path (eg via an appropriate interface) Availability of the UT at the source AxP 2008, the security configuration of the UT at the source AxP 2008, the target cell ID (eg target BxP ID indicating the beam to be prepared) and the radio bearer information Source-to-target transparent container (transparent through MM 2014), which carries a handoff preparation information message (including whether the source AxP 2008 proposes to forward forward link data) Included).

  In step 3, the MM 2014 sends a handoff request message to the target AxP 2012 to request resource preparation on the target AxP 2012. The message is carried in the Handoff Request message, Source-to-target transparent container (see step 2), a list of data bearers to be set up (eg quality of service (QoS) information, GN tunneling protocol (TP) address per data bearer) Designated information) and security context information (eg, one pair of NH, NCC for one-hop security between target plane's derivation of new security keys for user plane traffic and radio signaling).

  In step 4, upon receiving the handoff request message from MM 2014, the target AxP 2012 determines that the UE context can be established.

  In step 5, the target AxP 2012 sends a handoff request acknowledgment message to the MM 2014 to inform the MM 2014 about the resources prepared at the target AxP 2012. This message includes the target-to-source transparent container (passed transparently through MM 2014), which carries the handoff command message to be used by the source AxP 2008 when constructing the wireless connection reconfiguration message (see step 8). The Handoff Request Acknowledgment message may also target AxP downlink TP addressing on the specified interface per data bearer (for example, for data sent directly from GN 2010 to target AxP 2012 but not via source AxP 2008) It contains a list of data bearers to be set up, including information. The Handoff Request message (if the source AxP 2008 proposes to perform forward link data transfer for the data bearer and the target AxP 2012 accepts that proposal) additional target AxP 2012 forward link TP addressing information per data bearer And may contain target AxP reverse link TP addressing information per data bearer (if target AxP 2012 requests source AxP 2008 to perform reverse link data transfer for RL-AM data bearers). There is.

  In step 6, if indirect transfer of data is applied (eg, via the specified interface), the MM 2014 sends an indirect data transfer tunnel creation request message to the GN 2010. This message optionally includes the data bearer ID, the tunnel ID and IP address of the target AxP for indirect transfer of forward link data on the specified interface, and reverse link data on the specified interface And a list of data bearers including information of target AxP tunnel ID and IP address for indirect transfer of H.sup. Subsequently, the GN 2010 sends an indirect data transfer tunnel reply creation message to the MM 2014. This message may optionally include a data bearer ID, a GN tunnel ID and IP address for indirect transfer of forward link data on the specified interface, and reverse link data on the specified interface. The information of tunnel ID and IP address of GN for indirect transfer is included for each data bearer.

  In step 7, the MM 2014 sends a handoff command message to the source AxP 2008 to inform the source AxP 2008 that resources for the handoff have been received at the target AxP 2012. This message includes the target-to-source transparent container (see step 5) carried in the handoff request acknowledgment message to be used by the source AxP 2008 when constructing the wireless connection reconfiguration message (see step 8). The handoff order message also contains a list of data bearers to be set up. If direct transfer of data is applied (eg via an appropriate interface), the message proposes that the source AxP 2008 performs forward link data transfer for the data bearer, the target AxP 2012 proposes that It may contain target AxP forward link TP addressing information per data bearer (if accepted) (if target AxP 2012 requests source AxP 2008 to perform reverse link data transfer for RL-AM data bearer) It may include target AxP reverse link TP addressing information per data bearer. If indirect transfer of data is applied (eg via the specified interface), the message proposes that the source AxP 2008 perform forward link data transfer for the data bearer, the target AxP 2012 proposes that May contain GN forward link TP addressing information per data bearer (when the target AxP 2012 requests the source AxP 2008 to perform reverse link data transfer for the RL-AM data bearer) It may include GN reverse link TP addressing information per data bearer. See step 6. This message also contains the new satellite and cell transition tables. Upon receiving the handoff order message, the source AxP 2008 freezes the transmitter / receiver status for the UT's data bearer.

  In step 8, the source AxP 2008 sends a radio connection reconfiguration message to the UT 2002. This message includes: new UT-ID, PCI and frequency for target BxP 2006, security information, radio resource common and dedicated configuration information as needed (eg random access information, CQI report information), and target data It contains bearer configuration information (if there is a change from the current configuration). This message also includes a new paging area identifier that uniquely identifies the target AxP 2012. Upon receiving the radio connection reconfiguration message from the source AxP 2008, the UE starts timer T-4. If T-4 expires (eg, a handoff failure occurs), UT 2002 performs a wireless connection re-establishment procedure.

  In step 9, the UT 2002 derives new KAxP, KUPenc, Kint, and Kenc to be used when performing the handoff to the target AxP 2012.

  Referring to FIG. 21, for the RL-AM data bearer, UT 2002 resets the MAC state and the RL state (step 10). For the RL-UM data bearer, UT 2002 resets MAC, RL, and state. The UT 2002 then obtains a new cell (eg, FL sync).

  In steps 11 and 12, the source AxP 2008 sends a UT status transfer message to the target AxP 2012 via MM 2014. The source AxP 2008 sends this message to the target AxP 2012 only if at least one data bearer is configured for RL-AM operation. This message includes reverse link SN and FN receiver status, forward link SN and FN transmitter status, and (optionally) reverse link service data unit (SDU) reception status (target AxP 2012 RL-AM Request for the source AxP 2008 to perform reverse link data transfer for the data bearer, and the information (when the source AxP 2008 accepts the request) is included for each RL-AM data bearer. Also, for the RL-AM data bearer and the RL-UM data bearer, the source AxP 2008 starts forwarding forward link data (stored in the source AxP 2008 data bearer buffer) to the target AxP 2012 in order. For the RL-AM data bearer, this includes all forward link SDUs with SNs for which the successful delivery of the corresponding PDU has not been acknowledged by the UT 2002 (eg via the RL Status PDU). For the RL-AM data bearer and the RL-UM data bearer, this also includes new forward link data arriving on the interface specified from GN 2010. For RL-AM data bearers to which reverse link data transfer is applied, the source AxP 2008 starts to transfer reverse link SDUs with SNs received out of order to the target AxP 2012. For RL-AM data bearers where reverse link data transfer is not applied, the source AxP 2008 discards reverse link SDUs received out of order. For RL-UM data bearers, the source AxP 2008 sends the reverse link SDUs received out of order to the GN 2010 via the designated interface. Note that if direct transfer of data is applied, the source AxP 2008 transfers data to the target AxP 2012 on the appropriate interface.

  If indirect transfer of data is applied, the source AxP 2008 transfers data 2022 to the target AxP 2012 on the interface specified via GN 2010. The transferred data is stored in the target AxP data bearer buffer (step 12).

  In step 12, the UT 2002 sends a contention based random access preamble on random access to the target BxP 2006 (where source BxP 2004 and target BxP 2006 may be the same entity). Upon receiving a random access preamble from UT 2002, target BxP 2006 verifies the received signature sequence. If a dedicated preamble signature is available at target BxP 2006 and UT 2002 is assigned a dedicated preamble signature at step 8, UT 2002 sends a contention free random access preamble on the random access to target BxP 2006 and so on There is no possibility of collision.

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

  In operation of block 2030, UT 2002 sends a wireless connection reconfiguration complete message to target AxP 2012 (step 15). This message does not include IE. The radio connection reconfiguration complete message is integrity protected and encrypted using new Kint and Kenc respectively, and the UD-ID MAC Control Element (CE) and the PAI MAC Control Element and Location Management Information (LMI) MAC It is sent along with two new MAC control elements: control element. The UT-ID MAC control element includes the UT-ID assigned to the UT 2002 by the target AxP 2012 in the radio connection reconfiguration message (see step 8). The PAI MAC control element includes the PAI assigned to the UT 2002 by the target AxP 2012 in step 8. The LMI MAC control element contains the latest location information of the UT. The target BxP 2006 parses the PAI MAC Control Element to determine to which AxP the Wireless Connection Reconfiguration Complete message should be forwarded. The target BxP 2006 may send a handoff notification message to the MM 2014 at this time (eg, not at step 19). The UT 2002 starts a contention resolution timer.

  In step 16, the target BxP 2006 sends the UT 2002 an RL grant for a new transmission. The RL grant is addressed to the UT-ID that the target AxP 2012 assigned to the UT 2002 in the radio connection reconfiguration message (see step 8). Upon receiving the RL grant from the target BxP 2006, the UT 2002 stops the contention resolution timer and timer T-4. The UT 2002 may initiate reverse link signaling on signaling radio bearers (eg, SRB1 and SRB2) and sending reverse link data on all data radio bearers (DRBs). The UT 2002 may also initiate to receive forward link signaling on SRB1 and SRB2 and forward link forwarded data on all DRBs.

  Referring now to FIG. 22, for RL-AM data bearers to which reverse link data transfer applies, the target AxP 2012 has a status that includes the list of missing reverse link PDUs and received reverse link PDUs. A report message is sent to UT 2002 (step 17). The target AxP 2012 builds a status report using the information in the UT status transfer message from the source AxP 2008 via MM 2014 (see step 11). Upon receiving a status report message from the target AxP 2012, the UT 2002 will not retransmit any PDUs whose delivery success has been confirmed by the status report message. After the reverse link PDU retransmission is successfully completed, UT 2002 starts transmitting a new RL-AM reverse link PDU to the target AxP 2012. As the reverse link SN is maintained for each RL-AM data bearer, the target AxP 2012 uses a window based mechanism to avoid in-sequence delivery and duplication. For the RL-UM data bearer, the UT 2002 starts transmitting a new RL-UM reverse link PDU to the target AxP 2012. The upper packet data flow is represented by arrows 2032, 2034 and 2036.

  UT 2002 configured the UT 2002 to send a status report on the reverse link during re-establishment, for all RL-AM data bearers, the UT 2002 is missing the Forward Link PDU and received A status report message including a list of forward link PDUs is sent to the target AxP 2012 (step 18). Upon receiving this message, the target AxP 2012 starts transmitting forward link PDUs forwarded by the source AxP 2008 to the target AxP 2012 with the SN and without the SN to the UE. This packet data flow is represented by arrows 2038 and 2040. The target AxP 2012 continues to do this until it receives one or more end of TP marker packets from the source AxP 2008 for its RL-AM data bearer. The target AxP 2012 does not perform retransmission of any PDUs whose delivery success has been confirmed by the status report message from UT 2002. Since the forward link SN is maintained for each RL-AM data bearer, UT 2002 uses a window based mechanism for delivery and duplication avoidance in the sequence. For the RL-UM data bearer, the target AxP 2012 forwards the forward link PDUs forwarded by the source AxP 2008 to the target AxP 2012 (without continuing the original SN, as the SN is not maintained for each RL-UM data bearer) Start sending to UT 2002. The target AxP 2012 continues to do this until it receives one or more end of TP marker packets from the source AxP 2008 for each RL-UM data bearer.

  Step 19 may be performed immediately after step 15. In step 19, the target AxP 2012 sends a handoff notification message to the MM 2014 to inform the MM 2014 that the UT 2002 was identified in the target cell and that the handoff is complete. This message includes the PAI of the target AxP 2012 and the target cell ID (eg, the target BxP ID indicating the beam in which the UT 2002 was identified).

  In step 20, the MM 2014 sends a Bearer Modification Request message to the GN 2010. This message contains a list of data bearers, including data bearer ID, tunnel ID of target AxP, and IP address of forward link user plane (for uniquely identifying data bearer of UT), for each data bearer. Including.

  In step 21, the GN 2010 switches the forward link data path from the source AxP 2008 to the target AxP 2012 and sends one or more end of TP marker packets 2042 per data bearer to the source AxP 2008. GN 2010 also begins transmitting forward link data destined for UT 2002 directly to target AxP 2012 (arrows 2044 and 2046). The source AxP 2008 forwards the end of TP marker packet per data bearer to the target AxP 2012. Upon receiving the TP termination marker packet for each data bearer from the source AxP 2008, the target AxP 2012 may start transmitting the received forward link data directly from GN 2010 to UT 2002. It should be noted that if direct data transfer is applied, the source AxP 2008 transfers the end of TP marker packet 2048 to the target AxP 2012 on the appropriate interface. If indirect transfer of data is applied, the source AxP 2008 transfers data to the target AxP 2012 via GN 2010 (arrow 2050).

  In step 22, GN 2010 sends a Modify Bearer Response message to MM 2014. This message contains a list of data bearers, including data bearer ID and information of cause (e.g. request accepted) for each data bearer.

  In step 23A, the MM 2014 sends a release UE context message to the source AxP 2008 to request release of the UT related S1 logical connection on the S1 interface. Subsequently, in step 23B, the source AxP 2008 sends a release UE context message to the MM 2014 to confirm the release of the UT related logical connection on the appropriate interface. At step 24, the source AxP 2008 releases UT radio resources and context. At step 25, the indirect data transfer tunnel request (from step 6) is deleted. The final packet data flow is represented by lines 2052, 2054, and 2056.

Use of Satellite and Cell Transition Tables In some implementations, AxP may, if necessary, position and / or velocity of UT, position of satellites, satellite beam / cell pattern, satellite beam / cell on / off schedule The satellite and cell transition tables may be generated and / or updated using one or more of the or satellite pointing errors. The location and / or speed of the UT may be sent by the UT via wireless signaling messages, if specified. The position of time over time may be obtained from ephemeris data. For example, in a given satellite access network (SAN) that includes multiple GNs, the NOC / SOC in the SAN may provide updated satellite ephemeris information to all AxPs in the SAN.

  In some implementations, the system sends a single row of satellite and cell transition tables to be used for connected mode handoff (eg, the rows of Table 2 described above) to UT. provide. For example, the source AxP / BxP may include its single row of satellite and cell transition tables in the information element (IE) of the radio connection reconfiguration message that is sent to the UT while the UT is still on the serving cell. Thus, while the UT is being serviced by one cell / beam, the UT may receive satellite and cell transition information that the UT should use for transitioning to another cell / beam.

Configuration Messages in BxP Handoff As mentioned above, each satellite beam can be considered as a separate cell, with its own data and control channels, and signals. When the UT is handed over from one cell to another, some of the radio configuration parameters that were valid for the source cell may change due to the operation of the UT on the target cell Yes, there are things that need to be updated.

  Radio messages used for radio reconfiguration of radio parameters for the serving cell are also used to deliver updated configuration parameters for the target cell.

  AxP communicates the reconfiguration parameters for the target cell to the source cell (applicable also to the delivery of the radio connection reconfiguration in step 1 of FIG. 15 and also in FIGS. 16, 17 and 18). The reconfiguration message for the target cell is delivered by the source cell to the UT before the handoff occurs, as illustrated in step 1 of FIG. The message transmission needs to be done well before the handoff so that the UT has time to receive the message in a timely manner to enable reliable transmission. Upon receiving the reconfiguration message for the target cell, the UT stores it and applies the reconfiguration when initiating communication on the target cell.

  The handoff is performed based on the handoff transition table (Table 4) and follows the procedure defined for BxP handoff. The new configuration is applied at the time of handoff so that the UT is properly configured for the new serving cell before the data and control exchange starts.

  The radio reconfiguration message for the target beam may include radio parameters that are UT specific (dedicated) and radio parameters that are cell specific (common). They are for dedicated (dedicated), MAC configuration, non-continuous reception (DRX) parameters, power headroom report (PHR), buffer status report (BSR) scheduling request (SR), HARQ, SPS configuration, semi-persistent scheduling Parameters (period, resources), PHY configuration, dedicated PHY parameters for power control of data channel and control channel, CQI report, sounding reference signal (SRS), SR, random access configuration, UT-ID, PCI, common radio resource configuration , Common parameters for random access (preamble information, power control, management information, etc.), physical random access (route sequence information and physical random access configuration index, etc.), power and power control of reference signal, RL reference signal, ACK / NACK and CQI mapping, SRS (such as bandwidth and subframe configuration), p-Max (in cells Can be used to limit the RL transmit power of the UT). Since UT-IDs are provided to the UT for each serving cell, it is possible that 16-bit UT-IDs may be sufficient to uniquely address the defined number of about 5000 UTs per cell. Please keep in mind.

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 between the UT and the GN entity that supports the handoff. It is completed. A radio link failure (RLF) may be declared (eg, at the UT) if the UT loses communication with the GN before handoff signaling is complete. RLF may occur in the system due to the UT losing connection to the cell for various possible reasons, for example, under the influence of rain or snow attenuation, or due to building or tree shielding. In this case, the UT may utilize the RLF recovery mechanism to reestablish communication with the GN. The RLF procedure attempts to reconnect the UT to the same source cell or to a different (eg, target) cell.

  FIG. 23 shows an example of call flow for RLF procedure. This call flow is between UT 2302, source BxP or target BxP 2304, and source AxP or target AxP 2306. A description of the call flow steps follows.

  In step 1, a radio link detection procedure is used to detect RLF (eg, problems with radio link connection). This may be at the physical layer (eg, if the SNR is below a certain threshold), or at the MAC layer (eg, if a certain number of packets are mistakenly decoded), or at the RL layer (eg, for (If it has reached a number of RL retransmissions). The UT 2302 initiates a wireless connection re-establishment procedure by initiating a target satellite and cell search and selection procedure.

  After the UT 2302 has acquired the appropriate target satellites and cells (step 2), the UT 2302 sends a contention based random access preamble on random access to the target BxP 2304 (step 3). Upon receiving a random access preamble from UT 2302, target BxP 2304 verifies the received signature sequence. The target BxP 2304 may be the same as the source BxP (eg, UT 2302 selects the same cell to which UT 2302 was connected before RLF occurred).

  In step 4, the target BxP 2304 sends to the UT 2302 a random access response addressed to the appropriate UT-ID. The random access response includes paging area, RL grant, and temporary UT-ID.

  In step 5, the UT 2302 sends a radio connection reestablishment request message to the appropriate target AxP 2306 with two new MAC control elements (PAI MAC control element and LMI MAC control element). The wireless connection re-establishment message includes the UT's old UT-ID, old PCI, and MAC-I for verification during the wireless connection re-establishment procedure. The PAI MAC Control Element contains the latest PAI assigned to the UT 2302 by the source AxP. The PAI belongs to the target AxP if the handoff was in progress before RLF, otherwise the PAI belongs to the source AxP. The LMI MAC control element contains the latest location information of the UT. The target BxP 2304 parses the PAI MAC control element and the LMI MAC control element to determine to which AxP the wireless connection reestablishment request message should be forwarded. If the LMI MAC Control Element indicates an administrative area not covered by the AxP mapped to the PAI MAC Control Element, then the Target BxP 2304 forwards the Wireless Connection Re-establishment Request message to the appropriate Target AxP (this is a wireless connection This results in a failure of the re-establishment procedure and causes UT 2302 to initiate a NAS restore procedure (eg, a service request procedure). The UT 2302 starts timer T-3. When T-3 expires (eg, the wireless connection reestablishment procedure fails), the UT 2302 performs a NAS service request procedure.

  In step 6, the target AxP 2306 sends a radio connection re-establishment message to the UT 2302 along with the UE contention resolution identification MAC control element (to effect contention resolution). The wireless connection re-establishment message includes security configuration information used by the UT 2302 to derive new control plane and user plane keys (see step 7). This message may also include SRB1 configuration information.

  In step 7, the UT 2302 derives new KAxP, KUPenc, Kint, and Kenc to be used with the re-established wireless connection.

  In step 8, the UT 2302 sends a wireless connection reestablishment complete message to the target AxP 2306. This message does not contain an IE, and integrity protection and encryption are performed using the new Kint and Kenc, respectively.

  In step 9, the target AxP 2306 sends a radio connection reconfiguration message to the UT 2302. This message contains SRB2 and DRB configuration information.

  In step 10, the UT 2302 sends a wireless connection reconfiguration complete message to the target AxP 2306. This message does not include IE. The final packet data flow is represented by lines 2312 and 2314.

Exemplary Operation With the above in mind, additional examples of operations that may be performed by the UT and / or GN in support of UT handoff are now described with respect to FIGS. 24-38.

  FIG. 24 is an illustration of an example process 2400 for generating and using satellite handoff information in accordance with certain aspects of the present disclosure. Process 2400 may be performed in processing circuitry that may be located in a GN or some other suitable device. In some implementations, process 2400 represents operations performed by GN controller 250 of FIG. In some implementations, process 2400 represents an operation performed by apparatus 4600 of FIG. 46 (eg, by processing circuit 4610). Of course, in various aspects within the scope of the present disclosure, process 2400 may be implemented by any suitable device capable of supporting communication related operations.

  At block 2402, a GN (or other suitable device) optionally receives information from the user terminal. For example, the GN may receive user terminal capability and location information.

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

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

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

  At block 2410, the GN (or other suitable device) performs a handoff for the user terminal to different cells / beams and at least one satellite based on the satellite handoff information.

  FIG. 25 is an illustration of an example process 2500 for using satellite handoff information, in accordance with certain aspects of the present disclosure. Process 2500 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 2500 represents operations performed by control processor 420 of FIG. In some implementations, process 2500 represents operations performed by apparatus 4900 of FIG. 49 (eg, by processing circuitry 4910). Of course, in various aspects within the scope of the present disclosure, process 2500 may be implemented by any suitable device capable of supporting communication related operations.

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

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

  At block 2506, the user terminal (or other suitable device) performs a handoff (eg, to a different cell / beam and at least one satellite) to a particular beam of a particular satellite based on the satellite handoff information Do.

  FIG. 26 is an illustration of an example process 2600 for signaling user terminal capability information, in accordance with certain aspects of the present disclosure. Process 2600 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 2600 represents operations performed by control processor 420 in FIG. In some implementations, process 2600 represents an operation performed by apparatus 4900 of FIG. 49 (eg, by processing circuitry 4910). Of course, in various aspects within the scope of the present disclosure, process 2600 may be implemented by any suitable device capable of supporting communication related operations.

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

  At block 2604, a user terminal (or other suitable device) generates a capability message. In some aspects, the message indicates whether the UT can sense multiple cells / beams and / or satellites, and / or the message indicates inter-cell / beam tuning time of UT and / or inter-satellites. Indicates tuning time.

  At block 2606, the user terminal (or other suitable device) sends a capability message to the GN.

  FIG. 27 is an illustration of an example process 2700 for using user terminal capabilities, in accordance with certain aspects of the present disclosure. Process 2700 may be performed in processing circuitry that may be located in a GN or some other suitable device. In some implementations, process 2700 represents operations performed by GN controller 250 of FIG. In some implementations, process 2700 represents an operation performed by apparatus 4600 of FIG. 46 (eg, by processing circuit 4610). Of course, in various aspects within the scope of the present disclosure, process 2700 may be implemented by any suitable device capable of supporting communication related operations.

  At block 2702, a GN (or other suitable device) receives a capability message from a user terminal. This capability message contains user terminal capability information.

  At block 2704, the GN (or other suitable device) generates satellite handoff information. For example, a table or a portion of a table may be generated based in part on user terminal capability information (e.g., tuning time), user terminal location information, satellite motion, ephemeris information, and constraints caused by the operating system. obtain.

  At block 2706, the GN (or other suitable device) selects a handoff procedure for the user terminal based in part on the user terminal capability information. For example, monitoring measurement messages from the user terminal may be enabled or disabled based on whether the user terminal supports dual sensing. Thus, the device may enable or disable the device to monitor the measurement message based on the user terminal capability information.

  FIG. 28 is an illustration of an example process 2800 for signaling user terminal location information in accordance with certain aspects of the present disclosure. Process 2800 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 2800 represents operations performed by control processor 420 of FIG. In some implementations, process 2800 represents an operation performed by the apparatus 4900 of FIG. 49 (eg, by the processing circuit 4910). Of course, in various aspects within the scope of the present disclosure, process 2800 may be implemented by any suitable device capable of supporting communication related operations.

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

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

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

  FIG. 29 is an illustration of an example process 2900 for using user terminal location information, in accordance with certain aspects of the present disclosure. Process 2900 may be performed in processing circuitry that may be located in a GN or some other suitable device. In some implementations, process 2900 represents operations performed by GN controller 250 of FIG. In some implementations, process 2900 represents an operation performed by the apparatus 4600 of FIG. 46 (eg, by the processing circuit 4610). Of course, in various aspects within the scope of the present disclosure, process 2900 may be implemented by any suitable device capable of supporting communication related operations.

  At block 2902, a GN (or other suitable device) receives a location message from a user terminal. This location message contains user terminal location information.

  At block 2904, the GN (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 GN may generate the table or a portion of the table based on the current UT position. As another example, if the UT is moving, the GN may generate a table (or portion) based on the motion vector of the UT.

  FIG. 30 is an illustration of an example user terminal handoff process 3000, in accordance with certain aspects of the present disclosure. Process 3000 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 3000 represents operations performed by control processor 420 of FIG. In some implementations, process 3000 represents an operation performed by apparatus 4900 of FIG. 49 (eg, by processing circuit 4910). Of course, in various aspects within the scope of the present disclosure, process 3000 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3002, a next user terminal handoff is indicated at the user terminal (or other suitable device). For example, handoff may be indicated based on satellite handoff information.

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

  At block 3006, the user terminal (or other suitable device) determines whether to send a measurement message. In some aspects, this determination may be whether the signal from the current cell / beam and / or satellite is inappropriate or whether the signal from the target cell / beam and / or satellite is inappropriate. It may involve determining the

  At block 3008, if applicable, the user terminal (or other suitable device) transmits a measurement message and receives new satellite handoff information. In some aspects, this message may include measurement data and / or requests to advance / delay the timing of the handoff. Thus, in some aspects, the user terminal may transmit a measurement message based on the measured signal at block 3004, and may receive satellite handoff information as a result of transmitting the measurement message.

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

  FIG. 31 is an illustration of an example GN handoff process 3100 in accordance with some aspects of the present disclosure. Process 3100 may be performed in processing circuitry that may be located in a GN or some other suitable device. In some implementations, process 3100 represents operations performed by GN controller 250 of FIG. In some implementations, process 3100 represents an operation performed by the apparatus 4600 of FIG. 46 (eg, by the processing circuit 4610). Of course, in various aspects within the scope of the present disclosure, process 3100 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3102, a GN (or other suitable device) receives a measurement message from a user terminal.

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

  At block 3106, if applicable, the GN (or other suitable device) modifies satellite handoff information (eg, advances or delays the timing of the transition) and transmits the modified satellite handoff information to the user terminal .

  At block 3108, the GN (or other suitable device) performs a handoff of the user terminal in accordance with the satellite handoff information.

  FIG. 32 is an illustration of another example of an inter-satellite handoff signaling process 3200 in accordance with certain aspects of the present disclosure. Process 3200 may be performed in processing circuitry that may be located in a GN, a user terminal, or some other suitable device. In some implementations, process 3200 represents one or more operations performed by GN controller 280 of FIG. In some implementations, process 3200 represents one or more operations performed by control processor 420 of FIG. In some implementations, process 3200 represents one or more operations performed by apparatus 4600 of FIG. 46 (eg, by processing circuit 4610). In some implementations, process 3200 represents one or more operations performed by apparatus 4900 of FIG. 49 (eg, by processing circuitry 4910). Of course, in various aspects within the scope of the present disclosure, process 3200 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3202, a user terminal (or other suitable device) connects to a first satellite controlled by a first NAC in the GN.

  At block 3204, handoff of the user terminal (or other suitable device) to a second satellite controlled by a second NAC in the GN is illustrated.

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

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

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

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

  FIG. 33 is an illustration of an example process 3300 for signaling ephemeris information, in accordance with certain aspects of the present disclosure. Process 3300 may be performed in processing circuitry that may be located in a GN, a user terminal, or some other suitable device. In some implementations, process 3300 represents one or more operations performed by GN controller 250 in FIG. In some implementations, process 3300 represents one or more operations performed by control processor 420 of FIG. In some implementations, process 3300 represents one or more operations performed by apparatus 4600 of FIG. 46 (eg, by processing circuitry 4610). In some implementations, process 3300 represents one or more operations performed by apparatus 4900 of FIG. 49 (eg, by processing circuitry 4910). Of course, in various aspects within the scope of the present disclosure, process 3300 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3302, the GN (or other suitable device) transmits ephemeris information to the user terminal.

  At block 3304, a user terminal (or other suitable device) receives ephemeris information.

  At block 3306, the user terminal (or other suitable device) uses the ephemeris information to synchronize with the satellites.

  FIG. 34 is an illustration of an example wireless link failure process 3400 in accordance with certain aspects of the present disclosure. Process 3400 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 3400 represents operations performed by control processor 420 of FIG. In some implementations, process 3400 represents an operation performed by the apparatus 4900 of FIG. 49 (eg, by the processing circuit 4910). Of course, in various aspects within the scope of the present 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) loses connection to the cell / beam or satellite.

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

  At block 3406, the user terminal (or other suitable device) identifies an alternative cell / beam and / or satellite (eg, based on ephemeris information stored at the user terminal).

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

  At block 3410, a user terminal (or other suitable device) communicates with the GN via the new connection.

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

  FIG. 35 is an illustration of an example measurement gap related process 3500, in accordance with certain aspects of the present disclosure. Process 3500 may be performed in processing circuitry that may be located in a GN or some other suitable device. In some implementations, process 3500 represents operations performed by GN controller 250 of FIG. In some implementations, process 3500 represents an operation performed by the apparatus 4600 of FIG. 46 (eg, by the processing circuit 4610). Of course, in various aspects within the scope of the present disclosure, process 3500 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3502, the GN (or other suitable device) determines whether a measurement gap for measuring satellite signals is required.

  At block 3504, if no measurement gap is required, the GN (or other suitable device) does not include the detuning time in the satellite handoff information.

  At block 3506, if a measurement gap is required, the GN (or other suitable device) determines the measurement gap to be used to measure the satellite signal.

  At block 3508, the GN (or other suitable device) transmits information indicating a measurement gap to the user terminal.

  FIG. 36 is an illustration of an example measurement gap related process 3600 in accordance with some aspects of the present disclosure. Process 3600 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 3600 represents operations performed by control processor 420 of FIG. In some implementations, process 3600 represents an operation performed by the apparatus 4900 of FIG. 49 (eg, by the processing circuit 4910). Of course, in various aspects within the scope of the present disclosure, process 3600 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3602, a user terminal (or other suitable device) receives information indicative of measurement gaps for measuring satellite signals (eg, from GN).

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

  FIG. 37 is an illustration of an example user queue process 3700, in accordance with certain aspects of the present disclosure. Process 3700 may be performed in processing circuitry that may be located in a GN or some other suitable device. In some implementations, process 3700 represents operations performed by GN controller 250 of FIG. In some implementations, process 3700 represents an operation performed by the apparatus 4600 of FIG. 46 (eg, by the processing circuit 4610). Of course, in various aspects within the scope of the present disclosure, process 3700 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3702, the GN (or other suitable device) determines the time of handoff for the user terminal.

  At block 3704, the GN (or other suitable device) transfers at least one user queue prior to the handoff.

  FIG. 38 is an illustration of an example random access process 3800, in accordance with certain aspects of the present disclosure. Process 3800 may be performed in processing circuitry that may be located in a user terminal or some other suitable device. In some implementations, process 3800 represents operations performed by control processor 420 of FIG. In some implementations, process 3800 represents operations performed by apparatus 4900 of FIG. 49 (eg, by processing circuitry 4910). Of course, in various aspects within the scope of the present disclosure, process 3800 may be implemented by any suitable device capable of supporting communication related operations.

  At block 3802, a user terminal (or other suitable device) receives a dedicated preamble signature (eg, a UT receives a dedicated preamble signature from a GN in a control channel command).

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

First Exemplary Apparatus FIG. 39 shows a block diagram of an exemplary hardware implementation of an apparatus 3900 configured to communicate in accordance with one or more aspects of the present disclosure. For example, apparatus 3900 may be embodied or implemented within a UT or some other type of device that supports satellite communications. Thus, in some aspects, device 3900 may be an example of UT 400 or UT 401 of FIG. In various implementations, the apparatus 3900 may be embodied or implemented in satellite system components, vehicle components, or any other electronic device having circuitry.

  The apparatus 3900 includes a communication interface 3902 (eg, at least one transceiver), a storage medium 3904, a user interface 3906, a memory device (eg, memory circuit) 3908, and a processing circuit 3910 (eg, at least one processor). In various implementations, the user interface 3906 may be a keypad, a display, a speaker, a microphone, a touch screen display, or one of several other circuits for receiving input from the user or sending output to the user. Or may include more than one.

  These components may be coupled to one another and / or arranged in electrical communication with one another via a signaling bus or other suitable component, represented generally by connection lines in FIG. The signaling bus may include any number of interconnecting buses and bridges, depending on the specific application of processing circuit 3910 and the overall design constraints. The signaling bus combines the various circuits together so that the communication interface 3902, the storage medium 3904, the user interface 3906 and the memory device 3908 are each coupled to the processing circuit 3910 and / or in electrical communication with the processing circuit 3910. connect. The signaling bus may also connect various other circuits (not shown) such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, Therefore, it will not be described further.

  Communication interface 3902 provides a means for communicating with other devices over a transmission medium. In some implementations, communication interface 3902 includes circuitry and / or programming adapted to facilitate communication of information in a bi-directional manner with one or more communication devices in a network. In some implementations, communication interface 3902 is adapted to facilitate wireless communication of device 3900. In these implementations, communication interface 3902 may be coupled to one or more antennas 3912 as shown in FIG. 39 for wireless communication in a wireless communication system. Communication interface 3902 may be configured with one or more stand-alone receivers and / or transmitters, and one or more transceivers. In the illustrated example, communication interface 3902 includes a transmitter 3914 and a receiver 3916. Communication interface 3902 serves as an example of means for receiving and / or means for transmitting.

  Memory device 3908 may represent one or more memory devices. As shown, memory device 3908 may maintain idle mode handoff information 3918 along with other information used by apparatus 3900. In some implementations, memory device 3908 and storage medium 3904 are implemented as a common memory component. Memory device 3908 may also be used to store data manipulated by processing circuitry 3910, or some other component of apparatus 3900.

  A storage medium 3904 is one or more computer readable, machine readable, and computer readable instructions for storing programming such as processor executable code or instructions (eg, software, firmware), electronic data, databases, or other digital information. And / or may represent a processor readable device. Storage medium 3904 may also be used to store data manipulated by processing circuitry 3910 when performing programming. A storage medium 3904 is accessed by a general purpose or special purpose processor, including a portable or fixed storage device, an optical storage device, and various other media capable of storing, accommodating, or transporting programming. Can be any available medium that can

  By way of example and not limitation, storage medium 3904 may be a magnetic storage device (eg, hard disk, floppy disk, magnetic strip), optical disk (eg, compact disk (CD) or digital versatile disk (DVD)), smart card, flash memory Device (eg card, stick or key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), register , Removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Storage medium 3904 may be embodied in an article of manufacture (eg, a computer program product). By way of example, a computer program product may include a computer readable medium in packaging material. In view of the above, in some implementations, storage medium 3904 may be non-transitory (eg, tangible) storage medium.

  Storage medium 3904 can be coupled to processing circuit 3910 such that processing circuit 3910 can read information from storage medium 3904 and write information to storage medium 3904. That is, storage medium 3904 is an example in which at least one storage medium is integral with processing circuit 3910 and / or an example in which at least one storage medium is separate from processing circuit 3910 (eg, an example existing in apparatus 3900) Storage medium 3904 may be coupled to processing circuitry 3910 such that the storage medium 3904 is accessible by at least processing circuitry 3910, including instances external to the device 3900, instances distributed across multiple entities, and the like.

  The programming stored by storage medium 3904, when executed by processing circuitry 3910, causes processing circuitry 3910 to perform one or more of the various functions and / or processing operations described herein. . For example, storage medium 3904 is configured to coordinate operation at one or more hardware blocks of processing circuitry 3910, as well as to utilize communication interface 3902 for wireless communications utilizing their respective communications protocols. May include actions.

  Processing circuitry 3910 is generally adapted for processing including the execution of such programming stored on storage medium 3904. The terms "code" or "programming" as used herein are referred to as software, firmware, middleware, microcode, hardware description language, or otherwise Instruction, instruction set, data, code, code segment, program code, program, programming, subprogram, software module, application, software application, software package, routine, subroutine, object regardless of whether it is called by It should be interpreted broadly to include executables, threads of execution, procedures, functions etc.

  Processing circuitry 3910 is configured to obtain, process, and / or transmit data, control data access and storage, issue instructions, and control desired operations. Processing circuitry 3910 may include circuitry configured to implement the desired programming provided by the appropriate media in at least one example. For example, processing circuitry 3910 may be implemented as one or more processors, one or more controllers, and / or other structures configured to perform executable programming. Examples of processing circuitry 3910 include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic components, discrete gate or transistor logic, discrete hard disks. It may include wear components, or any combination thereof designed to perform the functions described herein. A general purpose processor may include a microprocessor, as well as any conventional processor, controller, microcontroller, or state machine. Processing circuit 3910 may also be a combination of DSP and microprocessor, several microprocessors, one or more microprocessors in conjunction with DSP core, ASICs and microprocessors, or any other number of different configurations Can be implemented as a combination of These examples of processing circuitry 3910 are for illustration, and other suitable configurations within the scope of the present disclosure are also contemplated.

  In accordance with one or more aspects of the present disclosure, processing circuitry 3910 may be any of features, processes, functions, operations, and / or routines for any or all of the devices described herein. Or can be adapted to perform all. For example, processing circuitry 3910 may be configured to perform any of the steps, functions, and / or processes described with respect to FIGS. 1-9 and 40-42. As used herein, the term "adapted" with respect to processing circuitry 3910 means that processing circuitry 3910 performs particular processes, functions, operations, and / or routines in accordance with the various features described herein. It may refer to one or more of being configured, used as such, implemented as such, and / or programmed as such.

  Processing circuit 3910 may be an application specific integrated circuit (eg, a structure for performing one of the operations described with reference to FIGS. 1-9 and 40-42). It may be a special processor such as an ASIC). The processing circuit 3910 serves as an example of means for transmitting and / or means for receiving. In some implementations, processing circuitry 3910 may at least partially provide and / or incorporate the functionality of control processor 420 of FIG.

  According to at least one example of the apparatus 3900, the processing circuitry 3910 receives circuitry / module 3920 for identifying, circuitry / module 3922 for determining whether to transmit, circuitry / module 3924 for transmitting, May include one or more of circuits / modules 3926, circuits / modules 3928 for hand-off, or circuits / modules 3930 for determining location information. In various implementations, circuits / modules 3920 to identify, circuits / modules 3922 to determine whether to transmit, circuits / modules 3924 to transmit, circuits / modules 3926 to receive, to handoff The circuit / module 3928 of or the circuit / module 3930 for determining position information may at least partially provide and / or incorporate the functionality of the control processor 420 of FIG.

  As mentioned above, the programming stored by storage medium 3904, when executed by processing circuitry 3910, causes processing circuitry 3910 to perform one of the various functions and / or processing operations described herein. Or run more than one. For example, programming may cause processing circuitry 3910 to perform the various functions, steps, and / or processes described herein with respect to FIGS. 1-9 and 40-42 in various implementations. it can. As shown in FIG. 39, the storage medium 3904 includes a code 3932 for identifying, a code 3934 for determining whether to send, a code 3936 for sending, a code 3938 for receiving, and a handoff. It may include one or more of code 3940 or code 3942 for determining position information. In various implementations, code 3932 to identify, code 3934 to determine whether to transmit, code 3936 to transmit, code 3938 to receive, code 3940 to hand off, or position information. The code for determining 3942 is a circuit / module 3920 for identifying, a circuit / module 3922 for determining whether to transmit, a circuit / module 3924 for transmitting, a circuit / module 3926 for receiving, a handoff Or may be implemented or otherwise used to provide the functionality described herein for circuits / modules 3928 to perform or circuits / modules 3930 to determine position information.

  Circuitry / module 3920 for identifying, for example, circuitry and / or programming adapted to perform certain functions related to identifying information associated with at least one handoff entry (eg, storage medium 4604 And a stored identification code 3932). In some aspects, circuitry / modules 3920 (eg, means for identifying) for identifying may correspond to, for example, processing circuitry.

  In some implementations, the identifying circuit / module 3920 identifies the time associated with the handoff entry. For example, the identifying circuit / module 3920 may identify the time based on the idle mode handoff table (eg, Table 1). Here, the idle mode handoff table may include an entry indicating the start time of the handoff to a particular satellite. To this end, the identifying circuit / module 3920 obtains entry information (eg, from the memory device 3908, the circuit / module 3926 to receive, or some other component of the apparatus 3900). The identifying circuit / module 3920 may then process this information to determine the time (eg, frame number) associated with the entry. The identifying circuit / module 3920 then generates an indication of this determination (eg, indicative of time) and a component of the apparatus 3900 (eg, a circuit / module 3922 for determining whether to transmit). , Memory device 3908, or some other component).

  In some implementations, the identifying circuit / module 3920 identifies the amount of valid entries in the set of handoff entries. For example, the identifying circuit / module 3920 may determine how many valid entries remain in the idle mode handoff table (eg, Table 1). To this end, the identifying circuit / module 3920 obtains handoff entry information (eg, from memory device 3908, circuit / module 3926 to receive, or some other component of apparatus 3900). In some scenarios, the identifying circuit / module 3920 may process this information to determine the number of valid entries remaining in the table (e.g., the entry is a table after it has expired). If left in). For example, the identifying circuit / module 3920 compares the value of time for each entry (eg, handoff time) to the current time, thereby determining which entry corresponds to a time that has not yet passed It can. In some scenarios, the identifying circuit / module 3920 may process this information to determine the total number of entries remaining (eg, if the entries are removed from the table upon expiration). In any case, the circuitry / module 3920 for identifying generates an indication of this determination (eg, a count indicative of the determined quantity) and whether the indication is to be transmitted to components of the apparatus 3900 (eg, whether to transmit Transmit to circuit / module 3922, memory device 3908, or some other component to determine.

  Circuits / modules 3922 for determining whether to transmit, for example, circuits and / or programming adapted to perform some functions related to determining whether to transmit information (eg storage medium 3904 may include code 3934) for determining whether to transmit or not. In some aspects, circuitry / modules 3922 for determining whether to transmit (eg, means for determining whether to transmit) may correspond to, for example, processing circuitry.

  In some implementations, the information to be sent may include a request for an updated set of handoff entries. In some scenarios, the circuit / module 3922 for determining whether to transmit (eg, from the identifying circuit / module 3920, the memory device 3908, or some other component) makes the determination of the transmission Get the information used for

  In some scenarios, the circuitry / module 3922 for determining whether to transmit may obtain an indication of the time associated with a particular entry of the set of handoff entries. In this case, the circuit / module 3922 for determining whether to transmit should update the set of handoff entries (eg, due to the reduced number of valid entries in the table). Whether to send a request may be determined based on whether the time indicates that it is. For example, transmission of the request may be triggered if the difference between the current time and the indicated time is less than a threshold time period.

  In some scenarios, the circuitry / module 3922 for determining whether to transmit may obtain an indication of the amount of valid entries in the set of handoff entries. In this case, the circuit / module 3922 for determining whether to transmit should update the set of handoff entries (eg, due to the reduced number of valid entries in the table). Based on whether the quantity indicates that there is, one may decide whether to send the request. For example, transmission of the request may be triggered when the number of valid entries is less than a threshold count (e.g., 1 or 2 or some other amount).

  In either scenario, the circuit / module 3922 for determining whether to transmit generates an indication of the above determination and for this indication, the circuit / module 3924, the memory device 3908, or the apparatus 3900 for transmitting. Send to some other component.

  Circuits / modules 3924 for transmitting, for example, circuits and / or programming adapted to perform some functions related to sending (eg, outputting or sending) information (eg, storage on storage medium 3904) May be included code 3936) for sending. In some implementations, the circuit / module 3924 for transmitting (eg, from the circuit / module 3922 for determining whether to transmit, the memory device 3908, or some other component of the apparatus 3900) You can get instructions to trigger the In some implementations, the circuit / module 3924 for transmitting is the circuit / module 3920 for identifying, the circuit / module 3930 for determining location information, the memory device 3908, or some other configuration of the apparatus 3900. From the elements, information to be sent (eg, request messages, instructions, location information, etc.) may be obtained and the information may be processed (eg, encoding information for transmission). In some scenarios, circuit / module 3924 for transmitting provides information to another component (eg, transmitter 3914, communication interface 3902, or some other component) that transmits information to another device Do. In some scenarios (eg, if the circuit / module 3924 for transmitting includes a transmitter), the circuit / module 3924 for transmitting may be radio frequency signaling or some other type suitable for an applicable communication medium Information directly to another device (eg, final destination) via

  The circuitry / modules 3924 for transmission (eg, means for transmitting) may take various forms. In some aspects, the circuitry / modules 3924 for transmitting may correspond to, for example, processing circuitry as discussed herein. In some aspects, circuitry / modules 3924 for transmitting may be, for example, an interface (eg, a bus interface, a transmitting interface, or some other type of signal interface), a communication device, a transceiver, a transmitter, or the present disclosure. May correspond to some other similar components as discussed in. In some implementations, communication interface 3902 includes circuitry / modules 3924 for transmitting and / or code 3936 for transmitting. In some implementations, the circuit / module 3924 for transmitting and / or the code 3936 for transmitting are configured to control the communication interface 3902 (eg, transceiver or transmitter) to transmit information. Ru.

  Circuits / modules 3926 for receiving, for example, circuits and / or programming adapted to perform some functions related to receiving information (eg stored on storage medium 3904, for receiving Code 3938). This information may include, but is not limited to, an indication, a set of handoff entries, a handoff table, etc. In some scenarios, circuitry / modules 3926 to receive (eg, from communication interface 3902, memory device, or some other component of apparatus 3900) obtains information and processes (eg, decodes) the information It can. In some scenarios (e.g., if the circuit / module 3926 to receive is an RF receiver, or if it includes), the circuit / module 3926 to receive directs the information directly from the device that sent the information. Can receive. In any case, circuitry / module 3926 for receiving may be another component of apparatus 3900 (eg, circuitry / module 3928 for hand-off, memory device 3908, or some other component) of the acquired information. Can be output to

  The circuitry / modules 3926 for receiving (eg, means for receiving) may take various forms. In some aspects, circuitry / modules 3926 for receiving may be, for example, an interface (eg, a bus interface, a transmit / receive interface, or some other type of signal interface), a communication device, a transceiver, a receiver, or a book It may correspond to some other similar component as discussed in the specification. In some implementations, communication interface 3902 includes circuitry / modules 3926 for receiving and / or code 3938 for receiving. In some implementations, the circuitry / modules 3926 for receiving and / or the code 3938 for receiving are configured to control the communication interface 3902 (eg, transceiver or receiver) to receive information. Ru.

  Circuits / modules 3928 for hand-off are, for example, circuits and / or programming adapted to perform several functions related to performing hand-off for the user terminal to the target cell, beam or satellite ( For example, code 3940) for hand-off stored in storage medium 3904 may be included. In some aspects, circuitry / modules 3928 (eg, means for handing off) for handing off may correspond to, for example, processing circuitry.

  In some implementations, based on the set of handoff entries (eg, Table 1 (Table 1)), the circuitry / module 3928 for handoff may be one or more of a target satellite, a target cell, or a target beam. Identify multiple. For this purpose, the circuit / module 3928 for hand-off collects this information, processes this information to identify the target (and optionally at least one carrier frequency of the target) and targets the user terminal The communication parameters of the device 3900 can be reconfigured to cause communication. For example, the circuitry / module 3928 for handoff may determine whether to handoff to a particular cell of a particular satellite at a particular time based on timing information in the set of handoff entries. As another example, the circuitry / module 3928 for handoff may determine whether to handoff to a particular cell of a particular satellite on a particular carrier frequency based on frequency information in the set of handoff entries. Can. If handoff is indicated, the circuitry / module 3928 for handoff may initiate handoff signaling accordingly.

  Circuits / modules 3930 for determining position information are, for example, circuits and / or programming adapted to perform several functions related to determining the position information of the device (for example stored in storage medium 3904 Code (3942) for determining position information. In some aspects, circuitry / modules 3930 (eg, means for determining location information) for determining location information may correspond to, for example, processing circuitry.

  In some scenarios, the circuitry / module 3930 for determining location information obtains information regarding at least one location of the device. For example, the circuitry / module 3930 for determining position information may obtain Global Positioning System (GPS) coordinates from the GPS receiver that indicate the current position of the device. As another example, the circuitry / module 3930 for determining location information may obtain a set of Global Positioning System (GPS) coordinates from the GPS receiver indicating movement of the device (e.g., the path the device traveled). . In some scenarios, this acquired information may constitute location information. In some scenarios, the circuit / module 3930 for determining position information processes this acquired information (eg, by generating a velocity indication or a vector indicating motion) to generate position information It can. Finally, the circuitry / module 3930 for determining location information outputs the location information to the circuitry / module 3924 for transmitting, the memory device 3908, or some other component of the apparatus 3900.

First Exemplary Process FIG. 40 illustrates a process 4000 for communication, in accordance with certain aspects of the present disclosure. Process 4000 may be performed within processing circuitry (eg, processing circuitry 3910 of FIG. 39) that may be located in a UT or some other suitable device. Of course, in various aspects within the scope of the present disclosure, process 4000 may be implemented by any suitable device capable of supporting communication related operations.

  At block 4002, a device (eg, UT) identifies a time associated with a particular entry of the set of handoff entries. In some aspects, the set of handoff entries may identify a set of satellites for device handoff. In some aspects, the time may include the start time of the handoff to one satellite of the set of satellites. In some aspects, that particular entry may include the last entry of the set of handoff entries.

  The set of handoff entries may take different forms in different implementations. In some aspects, the set of handoff entries may include an idle mode handoff table. In some aspects, this time may indicate when the device should be handed off to one satellite of the set of satellites while the device is in idle mode. In some aspects, the idle mode handoff table may include the time for devices in idle mode to hand off to the satellites for each satellite. In some aspects, that set of satellites may be for idle mode operation of the device. In some aspects, the set of handoff entries may include the time for devices in idle mode to handoff to the satellites for each satellite.

  At block 4004, the apparatus determines whether to send a request for the updated set of handoff entries based on the identified time of block 4002.

  At block 4006, the apparatus sends a request for the updated set of handoff entries if the determination is to send a request. In some aspects, the request may be communicated when the device establishes a wireless connection with a terrestrial network (GN).

  In some aspects, the apparatus may perform any of the operations discussed above for FIG. 40, or any combination thereof.

Second Exemplary Process FIG. 41 illustrates a process 4100 for communication, in accordance with certain aspects of the present disclosure. Process 4100 may be performed within processing circuitry (eg, processing circuitry 3910 of FIG. 39) that may be located in a UT or some other suitable device. Of course, in various aspects within the scope of the present disclosure, process 4100 may be implemented by any suitable device capable of supporting communication related operations.

  At block 4102, a device (eg, UT) identifies an amount of valid entries in the set of handoff entries. In some aspects, the set of handoff entries may identify a set of satellites for device handoff.

  The set of handoff entries may take different forms in different implementations. In some aspects, the set of handoff entries may include an idle mode handoff table. In some aspects, that set of satellites may be for idle mode operation of the device. In some aspects, the set of handoff entries may identify the time at which devices in idle mode should be handed off to each satellite of the set of satellites. In some aspects, the set of handoff entries may include the time for devices in idle mode to handoff to the satellites for each satellite.

  At block 4104, the apparatus determines whether to send a request for the updated set of handoff entries based on the identified amount. In some aspects, determining whether to send a request for the updated set of handoff entries may include determining whether the set of handoff entries includes only one valid entry.

  At block 4106, the apparatus sends a request for the updated set of handoff entries if the determination is to send a request. In some aspects, the request may be communicated when the device establishes a wireless connection with a terrestrial network (GN).

  In some aspects, the apparatus may perform any of the operations discussed above for FIG. 41, or any combination thereof.

Third Exemplary Process FIG. 42 shows a process 4200 for communication, in accordance with certain aspects of the present disclosure. One or more aspects of process 4200 may be used with (eg, in addition to or as part of) process 4000 of FIG. 40 or process 4100 of FIG. Process 4200 may be performed within processing circuitry (eg, processing circuitry 3910 of FIG. 39) that may be located in a UT or some other suitable device. Of course, in various aspects within the scope of the present disclosure, process 4200 may be implemented by any suitable device capable of supporting communication related operations.

  At optional block 4202, the device (eg, UT) may determine position information (eg, of the UT) of the device.

  At block 4204, the apparatus sends (eg, to the GN) a request for the updated set of handoff entries.

  At optional block 4206, the device may transmit information with the request. For example, the device may transmit the device's location information, an indication of the time associated with a particular entry of the set of handoff entries, an indication of the effective time associated with the set of handoff entries, or any combination thereof.

  At block 4208, the apparatus receives the updated set of handoff entries (eg, after sending the request at block 4202).

  At optional block 4210, the device may receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit. For example, the UT may receive the nextCellTransmitFreq parameter from the GN (eg, via a BIB message). As discussed above, this parameter may include a list of possible frequencies, single frequencies, etc.

  At block 4212, the apparatus handoffs to the satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. In the scenario using block 4210, this handoff may occur on at least one of the indicated carrier frequencies.

  In some aspects, the apparatus may perform any of the operations discussed above for FIG. 42, or any combination thereof.

Second Exemplary Device FIG. 43 shows a block diagram of an exemplary hardware implementation of another device 4300 configured to communicate, in accordance with one or more aspects of the present disclosure. For example, apparatus 4300 may be embodied or implemented within a GN or some other type of device supporting wireless communication. Thus, in some aspects, apparatus 4300 may be an example of GN 200 or GN 201 of FIG. In various implementations, the apparatus 4300 may be embodied or implemented in a gateway, a ground station, a vehicle component, or any other electronic device having circuitry.

  Apparatus 4300 includes communication interface (eg, at least one transceiver) 4302, storage medium 4304, user interface 4306, memory device 4308 (eg, stores idle mode handoff information 4318), and processing circuitry (eg, at least one processor). ) 4310 is included. In various implementations, the user interface 4306 may be a keypad, a display, a speaker, a microphone, a touch screen display, or one of several other circuits for receiving input from the user or sending output to the user. Or may include more than one. Communication interface 4302 may be coupled to one or more antennas 4312 and may include a transmitter 4314 and a receiver 4316. In general, the components of FIG. 43 may be similar to corresponding components of apparatus 3900 of FIG.

  In accordance with one or more aspects of the present disclosure, processing circuitry 4310 may be any of features, processes, functions, operations, and / or routines for any or all of the devices described herein. Or can be adapted to perform all. For example, processing circuitry 4310 may be configured to perform one or more of the steps, functions, and / or processes described with respect to FIGS. 1-9, 44, and 45. The term "adapted" with respect to processing circuitry 4310 is configured such that processing circuitry 4310 performs particular processes, functions, operations and / or routines in accordance with the various features described herein. , May be utilized, implemented, and / or programmed.

  Processing circuit 4310 is an application specific integrated circuit that functions as a means (eg, a structure therefor) for performing one or more of the operations described with respect to FIGS. 1-9, 44, and 45. It may be a special processor such as (ASIC). The processing circuit 4310 serves as an example of means for transmitting and / or means for receiving. In various implementations, processing circuitry 4310 may at least partially provide and / or incorporate the functionality of GN controller 250 of FIG.

  According to at least one example of the apparatus 4300, the processing circuitry 4310 transmits circuitry / module 4320 for identifying, circuitry / module 4322 for determining whether to transmit, circuitry / module 4324 for transmitting, Circuit / module 4326, circuit / module 4328 for generating, circuit / module 4330 for determining movement, or one of the circuits / module 4332 for determining how many entries to send May contain more than one. In various implementations, circuits / modules 4320 for identification, circuits / modules 4322 for determining whether to transmit, circuits / modules 4324 for transmitting, circuits / modules 4326 for receiving, to generate Circuit / module 4328, circuit / module 4330 for determining movement, or circuit / module 4332 for determining how many entries to send, at least partially provide the functionality of GN controller 250 of FIG. And / or may be incorporated.

  As mentioned above, the programming stored by storage medium 4304, when executed by processing circuit 4310, causes processing circuit 4310 to perform one of the various functions and / or processing operations described herein. Or run more than one. For example, programming may be performed on processing circuitry 4310 in various implementations one of the various functions, steps, and / or processes described herein with respect to FIGS. 1-9, 44, and 45. One or more can be run. As shown in FIG. 43, the storage medium 4304 includes a code 4340 for identifying, a code 4342 for determining whether to transmit, a code 4344 for transmitting, a code 4346 for receiving, and It may include one or more of code 4348, code 4350 for determining motion, or code 4352 for determining how many entries to send. In various implementations, code 4340 to identify, code 4342 to determine whether to transmit, code 4344 to transmit, code 4346 to receive, code 4348 to generate, determine motion Code 4350, or code 4352 for determining how many entries to send, circuit / module 4320 for identifying, circuit / module 4322 for determining whether to transmit, circuit for transmitting / Module 4324, circuit for receiving / circuit 4326, circuit for generating / circuit 4328, circuit for determining movement / module 4330, or circuit for determining how many entries to send / module 4332 May be implemented or otherwise used to provide the functionality described herein.

  Circuits / modules 4320 for identifying, for example, circuits and / or programming adapted to perform several functions related to identifying information associated with the at least one handoff entry (for example in storage medium 4604 And a stored identification code 4340). In some aspects, circuitry / modules 4320 (eg, means for identifying) for identifying may correspond to, for example, processing circuitry.

  In some implementations, the identifying circuit / module 4320 identifies an effective time associated with the set of handoff entries. For example, the identifying circuit / module 4320 may identify the effective time of the idle mode handoff table (eg, Table 1). To this end, the identifying circuit / module 4320 may obtain temporal information from the memory device 4308, the circuit / module 4326 for receiving, or some other component of the apparatus 4300. In some scenarios, identification of the valid time may include receiving an indication of the valid time (eg, from another device such as a UT). In some scenarios, identification of valid time may include receiving an indication of a time associated with a particular entry (eg, the last entry) of the set of handoff entries. In some cases, the identifying circuit / module 4320 processes the obtained information to determine an effective time associated with the set of handoff entries. For example, the identifying circuit / module 4320 may identify the handoff time associated with the last entry in the idle mode handoff table. In any of these scenarios, the identifying circuit / module 4320 thereby generates an indication of the time to live, and the element / device for determining whether to transmit this indication (eg, whether to transmit 4322, memory device 4308, or some other component).

  Circuits / modules 4322 for determining whether to transmit, for example, circuits and / or programming adapted to perform some functions related to determining whether to transmit information (eg storage medium 4304 may be included to determine whether to transmit or not. In some aspects, circuitry / modules 4322 for determining whether to transmit (eg, means for determining whether to transmit) may correspond to, for example, processing circuitry.

  In some implementations, the information to be sent may include a request for an updated set of handoff entries. In some scenarios, the circuitry / module 4322 for determining whether to transmit (eg, circuitry / module 4320 for identifying, circuitry / module 4330 for determining motion, memory device 4308, or some other Obtain information used to make a decision on transmission) from other components. In some scenarios, the circuitry / module 4322 for determining whether to transmit may obtain an indication of the time to live associated with the set of handoff entries. In this case, the circuit / module 4322 for determining whether to transmit determines whether to transmit the request based on whether the effective time indicates that the set of handoff entries should be updated. obtain. For example, transmission of the request may be triggered if the handoff entry indicates an expiration time, or that it will expire soon. In some scenarios, the circuit / module 4322 for determining whether to transmit may obtain an indication of the movement of another device (eg, UT). In this case, the circuit / module 4322 for determining whether to transmit may determine whether to transmit the request, for example based on how fast the other device is moving. In any case, the circuit / module 4322 for determining whether to transmit generates an indication of the determination, and this indication may be Output to some other component of

  Circuits / modules 4324 for transmitting, for example, circuits and / or programming adapted to perform some functions related to sending (eg, outputting or sending) information (eg, stored on storage medium 4304) Code for sending 4344). In some implementations, the circuit / module 4324 for transmitting (eg, from the circuit / module 4322 for determining whether to transmit, the memory device 4308, or some other component of the apparatus 4300) You can get instructions to trigger the In some implementations, the circuit / module 4324 for transmitting, the circuit / module 4320 for identifying, the circuit / module 4330 for determining motion, the memory device 4308, or some other component of the apparatus 4300 From, the information to be transmitted (eg, request message, instructions, location information, etc.) can be obtained and the information processed (eg, information encoded for transmission). In some scenarios, the circuit / module for transmitting 4324 provides information to another component (eg, transmitter 4314, communication interface 4302, or some other component) that transmits the information to another device. Do. In some scenarios (eg, if the circuit / module 4324 for transmitting includes a transmitter), the circuit / module 4324 for transmitting may be radio frequency signaling or some other type suitable for an applicable communication medium Information directly to another device (eg, final destination) via

  The circuitry / modules 4324 for transmission (eg, means for transmitting) may take various forms. In some aspects, circuitry / modules 4324 for transmitting may correspond to, for example, processing circuitry as discussed herein. In some aspects, circuitry / modules 4324 for transmitting may be, for example, an interface (eg, a bus interface, a transmitting interface, or some other type of signal interface), a communication device, a transceiver, a transmitter, or the present disclosure. May correspond to some other similar components as discussed in. In some implementations, communication interface 4302 includes circuitry / modules 4324 for transmitting and / or code 4344 for transmitting. In some implementations, the circuitry / modules 4324 for transmitting and / or the code 4344 for transmitting are configured to control the communication interface 4302 (eg, transceiver or transmitter) to transmit information. Ru.

  The circuitry / modules 4326 for receiving, for example, circuitry and / or programming adapted to perform some functions related to receiving information (eg, for receiving stored on the storage medium 4304) Code 4346). This information may include, but is not limited to, instructions, location information, and the like. In some scenarios, circuitry / modules 4326 to receive (eg, from communication interface 4302, a memory device, or some other component of apparatus 4300) obtains information and processes (eg, decodes) the information. It can. In some scenarios (eg, if the circuit / module 4326 to receive is an RF receiver, or if it includes), the circuit / module 4326 to receive information directly from the device that sent the information. Can receive. In any case, circuitry / module 4326 for receiving may be another component of apparatus 4300 (eg, circuitry / module 4328 for generating the acquired information, memory device 4308, or some other component). Can be output to

  The circuitry / modules 4326 (eg, means for receiving) for receiving may take various forms. In some aspects, circuitry / modules 4326 for receiving may be, for example, an interface (eg, a bus interface, a transmit / receive interface, or some other type of signal interface), a communication device, a transceiver, a receiver, or a book It may correspond to some other similar component as discussed in the specification. In some implementations, communication interface 4302 includes circuitry / modules 4326 for receiving and / or code 4338 for receiving. In some implementations, the circuitry / modules 4326 for receiving and / or the code 4338 for receiving are configured to control the communication interface 4302 (eg, transceiver or receiver) to receive information. Ru.

  The circuitry / modules 4328 for generating may be, for example, circuitry and / or programming adapted to perform some of the functions associated with generating the set of handoff entries (eg, stored on storage medium 4304, It may include code 4348) for generating. In some aspects, circuitry / modules 4328 (eg, means for generating) for generating may correspond to, for example, processing circuitry.

  In some implementations, the circuitry / modules for generating 4328 generates a set of handoff entries based on location information of another device (eg, UT). To this end, circuitry / modules 4328 for generating may obtain this location information from circuitry / modules 4326 to receive, communication interface 4302, memory device, or some other component of apparatus 4300. This allows the circuitry / modules 4328 to generate to create an updated set of handoff entries (eg, Table 1) based on satellite ephemeris information and location information. In some scenarios, the circuitry / modules 4328 to generate receives an indication of the number of handoff entries to transmit (eg, from the circuitry / module 4332 to determine how many entries to transmit). The circuitry / module 4328 for generating then outputs this information (eg, to the circuitry / module 4324 for transmitting, the memory device 4308, or some other component of the apparatus 4300).

  Circuits / modules 4330 for determining movement are, for example, circuits and / or programming adapted to perform several functions related to determining movement of the device (eg stored in storage medium 4304) Code 4350) for determining movement. In some aspects, circuitry / modules 4330 (eg, means for determining motion) to determine motion may correspond to, for example, processing circuitry.

  In some scenarios, the circuitry / modules 4330 for determining movement generates an indication of movement of another device (eg, UT) based on position information of the other device. To this end, circuitry / modules 4330 for determining motion may obtain this location information from circuitry / modules 4326 for receiving, communication interface 4302, memory device, or some other component of device 4300. Thereby, the circuitry / module 4330 for determining motion may process this acquired information to generate a motion indication (eg, by generating a velocity indication or a vector indicative of the motion). The circuitry / module 4330 for determining motion then outputs an indication (eg, to the circuitry / module 4324 for determining whether to transmit, the memory device 4308, or some other component of the apparatus 4300).

  The circuit / module 4332 for determining how many entries to transmit, for example, perform several functions related to determining how many updated handoff entries should be transmitted to another device. And / or programming (eg, code 4352 for determining how many entries stored in storage medium 4304 to send). In some aspects, circuitry / modules 4332 for determining how many entries to send (eg, means for determining how many entries to send) may correspond to, for example, processing circuitry.

  In some scenarios, the circuit / module 4332 for determining how many entries to send determines the number of entries based on the movement of other devices. To this end, the circuit / module 4332 for determining how many entries to send get motion information from the circuit / module 4330 for determining motion, memory device or some other component of the device 4300 It can. Thereby, the circuit / module 4332 for determining how many entries to send may process this obtained information to determine how many entries to send. For example, as discussed herein, fewer entries may be sent to UTs that are moving relatively faster than UTs that are moving relatively slowly or UTs that are stationary. obtain. Thus, in some aspects, the determination of the number of entries may be based on at least one threshold of motion, mapping of motion to the number of entries, or other criteria. The circuit / module 4332 for determining how many entries to send then indicates (eg, the circuit / module 4328 for generating the number of entries to send, the memory device 4308, or some other Output to the component of

Fourth Exemplary Process FIG. 44 shows a process 4400 for communication, in accordance with certain aspects of the present disclosure. Process 4400 may be performed within processing circuitry (eg, processing circuitry 4310 of FIG. 43) that may be located in a GN or some other suitable device. Of course, in various aspects within the scope of the present disclosure, process 4400 may be implemented by any suitable device capable of supporting communication related operations.

  At block 4402, the device (eg, GN) identifies an effective time associated with the set of handoff entries. In some aspects, the set of handoff entries may identify a set of satellites for handoff of another device (eg, UT). In some aspects, the valid time may indicate the length of time that the set of entries for the handoff is valid.

  The identification of the valid time may take different forms in different implementations. In some aspects, determining the valid time may include receiving an indication of the valid time. In some aspects, determining the valid time includes receiving an indication of a time associated with a particular entry of the set of handoff entries, and determining the valid time based on the received indication. obtain. In some aspects, determining the valid time may include determining the time associated with the last valid entry in the set of handoff entries.

  The set of handoff entries may take different forms in different implementations. In some aspects, the set of handoff entries may include an idle mode handoff table. In some aspects, the set of handoff entries may identify at least one satellite for idle mode operation of the other device. In some aspects, the set of handoff entries may identify the time at which devices in idle mode should be handed off to each satellite of the set of satellites. In some aspects, the set of handoff entries may include the time for devices in idle mode to handoff to the satellites for each satellite. In some aspects, the set of handoff entries may include the last set of handoff entries sent by the device to other devices.

  At block 4404, the apparatus determines whether to transmit the updated set of handoff entries based on the identified valid time at block 4402.

  At block 4406, the apparatus transmits the updated set of handoff entries if the determination is to transmit the updated set of handoff entries.

  In some aspects, the apparatus may perform any of the operations discussed above for FIG. 44, or any combination thereof.

Fifth Exemplary Process FIG. 45 shows a process 4500 for communication in accordance with certain aspects of the present disclosure. One or more aspects of process 4500 may be performed with (eg, in addition to or as part of) process 4400 of FIG. Process 4500 may be performed within processing circuitry (eg, processing circuitry 4310 of FIG. 43) that may be located in a GN or some other suitable device. Of course, in various aspects within the scope of the present disclosure, process 4500 may be implemented by any suitable device capable of supporting communication related operations.

  At optional block 4502, an apparatus (eg, GN) may receive an indication of a time to be associated with a particular entry of the set of handoff entries.

  At optional block 4504, the device may receive position information of the device (eg, another device such as a UT).

  At block 4506, the apparatus generates an updated set of handoff entries (eg, based on location information and / or an indication of time).

  At optional block 4508, the device may determine movement of the device (eg, another device such as a UT) based on the position information.

  At optional block 4510, the device may determine whether to transmit the updated set of handoff entries (eg, based on location information and / or other device movements). In some aspects, an apparatus may determine how many updated handoff entries to send (e.g., based on the movements of other apparatuses).

  At block 4512, the apparatus transmits the updated set of handoff entries.

  At optional block 4514, the apparatus may transmit an indication of at least one carrier frequency that the next cell providing coverage for the other apparatus (eg, UT) will use to transmit.

  In some aspects, the apparatus may perform any of the operations discussed above for FIG. 45, or any combination thereof.

Third Exemplary Apparatus FIG. 46 shows a block diagram of an exemplary hardware implementation of an apparatus 4600 configured to communicate in accordance with one or more aspects of the present disclosure. For example, apparatus 4600 may be embodied or implemented within a UT or some other type of device that supports satellite communications. Thus, in some aspects, the apparatus 4600 may be an example of the GN 200 or GN 201 of FIG. In various implementations, the apparatus 4600 may be embodied or implemented in a gateway, a ground station, a vehicle component, or any other electronic device having circuitry.

  The apparatus 4600 includes a communication interface (eg, at least one transceiver) 4602, a storage medium 4604, a user interface 4606, a memory device (eg, memory circuit) 4608, and processing circuitry (eg, at least one processor) 4610. In various implementations, the user interface 4606 may be a keypad, a display, a speaker, a microphone, a touch screen display, or one of several other circuits for receiving input from the user or sending output to the user. Or may include more than one.

  These components may be coupled to one another and / or arranged to be in electrical communication with one another via a signaling bus or other suitable component schematically represented by connection lines in FIG. . The signaling bus may include any number of interconnecting buses and bridges, depending on the specific application of processing circuit 4610 and the overall design constraints. The signaling bus combines the various circuits together so that each of the communication interface 4602, the storage medium 4604, the user interface 4606, and the memory device 4608 are coupled to and / or in electrical communication with the processing circuit 4610. connect. The signaling bus may also connect various other circuits (not shown) such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, Therefore, it will not be described further.

  Communication interface 4602 provides a means for communicating with other devices through a transmission medium. In some implementations, communication interface 4602 includes circuitry and / or programming adapted to facilitate communication of information in a bi-directional manner with one or more communication devices in a network. In some implementations, communication interface 4602 is adapted to facilitate wireless communication of device 4600. In these implementations, communication interface 4602 may be coupled to one or more antennas 4612 as shown in FIG. 46 for wireless communication in a wireless communication system. Communication interface 4602 may be configured with one or more stand-alone receivers and / or transmitters, and one or more transceivers. In the illustrated example, communication interface 4602 includes a transmitter 4614 and a receiver 4616. Communication interface 4602 serves as an example of means for receiving and / or means for transmitting.

  Memory device 4608 may represent one or more memory devices. As shown, memory device 4608 may maintain satellite related information 4618 along with other information used by apparatus 4600. In some implementations, memory device 4608 and storage medium 4604 are implemented as a common memory component. Memory device 4608 may also be used to store data manipulated by processing circuitry 4610 or some other component of apparatus 4600.

  A storage medium 4604 is one or more computer readable, machine readable, and computer readable instructions for storing programming such as processor executable code or instructions (eg, software, firmware), electronic data, databases, or other digital information. And / or may represent a processor readable device. Storage medium 4604 may also be used to store data manipulated by processing circuitry 4610 when performing programming. Storage medium 4604 is accessed by a general purpose or special purpose processor, including a portable or fixed storage device, an optical storage device, and various other media capable of storing, accommodating, or transporting programming. Can be any available medium that can

  By way of example and not limitation, storage medium 4604 may be a magnetic storage device (eg, hard disk, floppy disk, magnetic strip), optical disk (eg, compact disk (CD) or digital versatile disk (DVD)), smart card, flash memory Device (eg card, stick or key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), register , Removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Storage medium 4604 may be embodied in an article of manufacture (eg, a computer program product). By way of example, a computer program product may include a computer readable medium in packaging material. In view of the above, in some implementations, storage medium 4604 may be non-transitory (eg, tangible) storage medium.

  Storage medium 4604 can be coupled to processing circuit 4610 such that processing circuit 4610 can read information from storage medium 4604 and write information to storage medium 4604. That is, storage medium 4604 is an example in which at least one storage medium is integral with processing circuit 4610 and / or an example in which at least one storage medium is separate from processing circuit 4610 (eg, an example existing in apparatus 4600 Storage medium 4604 may be coupled to processing circuitry 4610 such that the storage medium 4604 is accessible by at least processing circuitry 4610, including instances external to device 4600, instances distributed across multiple entities, and the like.

  The programming stored by storage medium 4604, when executed by processing circuitry 4610, causes processing circuitry 4610 to perform one or more of the various functions and / or processing operations described herein. . For example, storage medium 4604 is configured to coordinate operation at one or more hardware blocks of processing circuitry 4610, as well as to utilize communication interface 4602 for wireless communications that utilize their respective communication protocols. May include actions.

  Processing circuitry 4610 is generally adapted for processing including the execution of such programming stored on storage medium 4604. The terms "code" or "programming" as used herein are referred to as software, firmware, middleware, microcode, hardware description language, or otherwise Instruction, instruction set, data, code, code segment, program code, program, programming, subprogram, software module, application, software application, software package, routine, subroutine, object regardless of whether it is called by It should be interpreted broadly to include executables, threads of execution, procedures, functions, etc.

  Processing circuitry 4610 is configured to obtain, process, and / or transmit data, control data access and storage, issue instructions, and control desired operations. Processing circuitry 4610 may include circuitry configured to implement the desired programming provided by the appropriate media in at least one example. For example, processing circuitry 4610 may be implemented as one or more processors, one or more controllers, and / or other structures configured to perform executable programming. Examples of processing circuits 4610 include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic components, discrete gate or transistor logic, discrete hard disks. It may include wear components, or any combination thereof designed to perform the functions described herein. A general purpose processor may include a microprocessor, as well as any conventional processor, controller, microcontroller, or state machine. The processing circuitry 4610 may also be a combination of DSP and microprocessor, several microprocessors, one or more microprocessors in conjunction with a DSP core, ASICs and microprocessors, or any other number of different configurations, etc. Can be implemented as a combination of These examples of processing circuitry 4610 are for illustration, and other suitable configurations within the scope of the present disclosure are also contemplated.

  In accordance with one or more aspects of the present disclosure, processing circuitry 4610 may be any of features, processes, functions, operations, and / or routines for any or all of the devices described herein. Or can be adapted to perform all. For example, the processing circuit 4610 may be implemented by the steps and functions described with reference to FIGS. 11, 12, 15-24, 27, 29, 31-33, 35, 37, 47, and 48. And / or may be configured to perform one or more of the operations. As used herein, the term "adapted" with respect to processing circuitry 4610 means that processing circuitry 4610 performs particular processes, functions, operations, and / or routines in accordance with the various features described herein. May refer to one or more of being configured, to be utilized as such, to be implemented as such, and / or to be programmed as such.

  Processing circuit 4610 performs one of the operations described with respect to FIGS. 11, 12, 15-24, 27, 29, 31-33, 35, 37, 47, and 48. It may be a special processor, such as an application specific integrated circuit (ASIC) that functions as a means (eg, structure for it) to perform one or more. The processing circuit 4610 serves as an example of means for transmitting and / or means for receiving. In some implementations, processing circuitry 4610 incorporates the functionality of GN controller 250 of FIG.

  According to at least one example of the apparatus 4600, the processing circuit 4610 comprises: circuit / module 4620 for generating, circuit / module 4622 for transmitting, circuit / module 4624 for performing handoff, circuit for receiving / Module 4626, circuit / module 4628 for determining whether to modify, circuit / module 4630 for selecting, circuit / module 4632 for determining time, circuit / module 4634 for transferring, measurement gap It may include one or more of circuit / module 4636 to determine, or circuit / module 4638 to determine that a measurement gap is not needed. In various implementations, circuits / modules 4620 to generate, circuits / modules 4622 to transmit, circuits / modules 4624 to perform handoff, circuits / modules 4626 to receive, and whether to modify Circuit / module 4628 for selecting, circuit / module 4630 for selecting, circuit / module 4632 for determining time, circuit / module 4634 for transferring, circuit / module 4636 for determining measurement gap, or The circuit / module 4638 for determining that a measurement gap is not needed may correspond at least in part to the GN controller 250 of FIG.

  The circuitry / modules 4620 for generating perform, for example, several functions related to generating satellite and cell transition information specifying when to start and end communication with a particular cell of a particular satellite And / or programming (eg, code 4640 for generating stored in storage medium 4604) adapted to do so. In some implementations, the circuitry / modules 4620 for generating calculate information (eg, data for Table 1) based on satellite ephemeris data and user terminal location data. To this end, circuitry / modules 4620 for generating collect this data, process the data to generate its information, and send the information to components of device 4600 (eg, memory device 4608). For example, for a given position of the user terminal, the circuit / module 4620 for generating is based on the position of the satellite and the direction and coverage of the satellite's cell over time, when a particular cell of a particular satellite is It can be determined whether to provide coverage for the user terminal.

  Circuits / modules 4622 for transmitting may be, for example, circuits and / or programming adapted to perform certain functions related to transmitting information (eg, data) to another device (eg, storage medium 4604). And the code for transmission 4642 stored in Initially, circuitry / module 4622 for transmitting obtains information to be transmitted (eg, from memory device 4608, circuitry / module 4620 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 measurement gaps. The circuit / module 4622 for transmitting may then format the information for transmission (eg, in a message, according to a protocol, etc.). A circuit / module 4622 for transmitting then causes the information to be transmitted (eg, via satellite signaling) via a wireless communication medium. To this end, circuitry / modules 4622 for sending may send data to communication interface 4602 (eg, digital subsystem or RF subsystem) or some other component for transmission. In some implementations, communication interface 4602 includes circuitry / modules 4622 for transmitting and / or code 4642 for transmitting.

  Circuits / modules 4624 for performing the handoff are, for example, circuits and / or adapted to perform some functions related to performing the handoff for the user terminal to a different cell and at least one satellite. Programming may be included (eg, code 4644 for performing the handoff stored on storage medium 4604). In some implementations, the circuitry / modules 4624 for performing the handoff identify the target satellite and / or target cell based on the satellite and cell transition information (eg, Table 1). To this end, circuitry / modules 4624 for performing the handoff collect this information, process this information to identify the target, and communicate parameters to allow communication with the user terminal through the target. Reconfigure. For example, for a given position of the user terminal, the circuit / module 4624 for performing the handoff may be a particular cell of a particular satellite based on the position of the satellite and the satellite's cell direction and coverage over time It can be determined whether to provide sufficient coverage for the user terminal. If the satellite / cell provides sufficient coverage, the circuitry / module 4624 for performing the handoff may designate that satellite / cell as the target of the handoff and initiate handoff signaling accordingly.

  The circuitry / modules 4626 for receiving may be, for example, circuitry and / or programming (eg, storage medium 4604) adapted to perform certain functions related to receiving information (eg, data) from another device. And the code for receiving 4646 stored in In various implementations, the information to be received may include measurement messages 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. First, circuitry / modules 4626 for receiving obtain the received information. For example, circuitry / modules 4626 for receiving may be from components of apparatus 4600 (eg, from communication interface 4602 (eg, digital subsystem or RF subsystem), memory device 4608, or some other component) or This information may be obtained directly from the device (eg, satellite) that relayed the information from the terminal. In some implementations, circuitry / modules 4626 for receiving locates the memory location of the value in memory device 4608 and invokes a read of that location. In some implementations, circuitry / modules 4626 for receiving may process (eg, decode) the received information. The circuitry / modules 4626 for receiving may output the received information (eg, store the received information in the memory device 4608 or send the information to another component of the apparatus 4600). In some implementations, communication interface 4602 includes circuitry / modules 4626 for receiving and / or code 4642 for receiving.

  Circuits / modules 4628 for determining whether to modify, for example, circuits and / or programming adapted to perform some functions related to determining whether to modify satellite and cell transition information For example, it may include code 4648) stored in storage medium 4604 for determining whether to make corrections. In some implementations, the circuit / module 4628 for determining whether to make corrections makes this determination based on the received measurement message. For this purpose, the circuit / module 4628 for determining whether to modify (for example from the circuit / module 4626 for receiving, the memory device 4608, or some other component of the apparatus 4600) this measurement message information To collect The circuit / module 4628 for determining whether to correct then processes this information to see if the current timing parameters need to be changed (eg, due to bad RF conditions or RF condition improvements). It can be decided. For example, circuitry / module 4628 for determining whether to modify may compare the signal quality information included in the measurement message to one or more signal quality thresholds. Finally, the circuit / module 4628 for determining whether to modify or not generates an indication of this determination (eg, indicating to accelerate the handoff or to delay the handoff).

  Circuits / modules 4630 for selecting are, for example, circuits and / or programming adapted to perform some functions related to selecting a handoff procedure for the user terminal (eg stored in storage medium 4604 Code for selection 4650). In some implementations, the circuit / module for selecting 4630 makes this determination based on the capability information received from the user terminal. To this end, the circuit / module 4630 for selection collects this capability information, processes this information to identify the handoff procedure, and generates an indication of this decision. For example, selection of the handoff procedure enables or does monitoring of the measurement message from the user terminal based on determining whether the user terminal is dual sensitive and whether the user terminal is dual sensitive or not May be accompanied by disabling. Thus, in some implementations, circuitry / modules 4630 for selecting obtain configuration information for the user terminal (eg, from memory device 4608, from receiver 4616, or from some other component), This information is verified to identify the user terminal's ability to select a supported handoff procedure, and an indication of this determination (eg, memory device 4608, circuitry / module 4624 for performing the handoff, or some other To be sent to the components of

  Circuits / modules 4632 for determining time may, for example, be circuits and / or programming adapted to perform several functions related to determining the time of handoff of the user terminal (eg stored in storage medium 4604) Code 4652) for determining the time being done. In some implementations, the circuit / module 4632 for determining time makes this determination based on satellite and cell transition information (eg, Table 1). To this end, the circuit / module 4632 for determining time obtains this information (eg, from the circuit / module 4626 to receive, the memory device 4608, or some other component of the apparatus 4600). The circuit / module 4632 for determining time may then process this information to determine the time of the next handoff of the user terminal (eg, frame number). For example, the circuit / module 4632 for determining time may compare the current time indication (eg, frame number) to the timing indication of Table 1 (Table 1). The circuit / module 4632 for determining the time generates an indication of this determination (for example indicating the time of the handoff) and a component of the apparatus 4600 (for example the circuit / module 4634 for transferring, memory Send to device 4608, or some other component).

  Circuits / modules 4634 for transferring may be, for example, circuits and / or programming adapted to perform some of the functions associated with transferring user queues prior to handoff (eg stored in storage medium 4604 Code for transmitting 4655). Initially, circuitry / module 4634 for forwarding receives an indication of a time for handoff (eg, from memory device 4608, circuitry / module 4632 for determining time, or some other component). Next, prior to the time of handoff, circuitry / modules 4634 for forwarding obtain queue information to be transmitted (eg, from memory device 4608 or some other component). In various implementations, this information may be sent to another GN. The circuit / module 4634 for forwarding may then format the queue information for transmission (eg, in a message, according to a protocol, etc.). Circuitry / module 4634 for forwarding then causes the queue information to be transmitted (eg, via infrastructure 106 of FIG. 1) via an appropriate communication medium. To this end, circuitry / modules 4634 for forwarding may send data to communication interface 4602 or some other component for transmission. In some implementations, communication interface 4602 includes circuitry / modules 4634 for transferring and / or code 4565 for transferring.

  Circuits / modules 4636 for determining measurement gaps are, for example, circuits and / or programming adapted to perform some functions related to determining measurement gaps for measuring satellite signals (eg storage Code 4656) for determining the measurement gap stored in the medium 4604 may be included. In some implementations, the circuit / module 4636 for determining the measurement gap determines that there may be satellite pointing errors that may necessitate a change in handoff time. As a result of this determination or some other trigger, the circuit / module 4636 for determining the measurement gap may measure the measurement gap to be used by the UT (for example, a measurement gap pattern indicating the time that the GN has not sent to the UT). Generate instructions for The circuit / module 4636 for determining the measurement gap then sends this indication to a component of the apparatus 4600 (eg, the circuit / module 4622 for transmitting, the memory device 4608, or some other component).

  The circuit / module 4638 for determining that a measurement gap is not necessary is, for example, a circuit adapted to perform some functions related to determining that a measurement gap for measuring satellite signals is not necessary. And / or programming (eg, code 4658 for determining that measurement gaps stored on storage medium 4604 are not needed). In some implementations, the circuitry / module 4638 for determining that a measurement gap is not needed obtains information regarding the status of one or more satellites. Based on this information, the circuit / module 4638 for determining that a measurement gap is not needed determines that there is no satellite pointing error that would necessitate a change in the handoff time. As a result of this determination or some other trigger, the circuit / module 4638 for determining that a measurement gap is not necessary generates an indication of this determination, and the indication is for example a component of the apparatus 4600 Circuit 4200, memory device 4608, or some other component).

  As mentioned above, the programming stored by storage medium 4604, when executed by processing circuitry 4610, causes processing circuitry 4610 to perform one of the various functions and / or processing operations described herein. Or run more than one. For example, programming may be performed by the processing circuitry 4610 to cause the processing circuitry 4610 to, in various implementations, FIGS. 11, 12, 15-24, 27, 29, 31-33, One or more of the various functions, steps, and / or processes described herein with respect to 35, FIG. 37, FIG. 47, and FIG. 48 may be performed. As shown in FIG. 46, storage medium 4604 determines code 4640 to generate, code 4642 to transmit, code 4644 to perform a handoff, code 4646 to receive, whether to modify. For code 4648, code for selecting 4650, code for determining time 4652, code for transferring 4652, code for determining measurement gap 4656, or for determining that measurement gap is not necessary One or more of the cords 4658 may be included.

Sixth Exemplary Process FIG. 47 illustrates a process 4700 for communication, in accordance with certain aspects of the present disclosure. Process 4700 may be performed within processing circuitry (eg, processing circuitry 4610 of FIG. 46) that may be located in a GN or some other suitable device. In some implementations, process 4700 may be performed by GN for at least one non-geostationary satellite. In some implementations, process 4700 represents operations performed by GN controller 250 of FIG. Of course, in various aspects within the scope of the present disclosure, process 4700 may be implemented by any suitable device capable of supporting communication operations.

  At block 4702, an apparatus (eg, GN) generates satellite handoff information that specifies a handoff time for a particular cell of a particular satellite. In some aspects, the operations of block 4702 may correspond to the operations of block 2406 of FIG.

  In some aspects, the generation of satellite handoff information may be based on at least one of the user terminal's capability information or the user terminal's location information. In some aspects, the capability information may indicate at least one of whether the user terminal can sense multiple beams or whether the user terminal can sense multiple satellites. In some aspects, the capability information may indicate at least one of inter-beam tuning time for the user terminal or inter-satellite tuning time for the user terminal. In some aspects, the position information may include at least one of a current position of the user terminal or a motion vector of the user terminal.

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

  In some implementations, the circuit / module 4620 for generating in FIG. 46 performs the operations of block 4702. In some implementations, the generating code 4640 of FIG. 46 is executed to perform the operations of block 4702.

  At block 4704, the apparatus transmits satellite handoff information to the user terminal. In some aspects, this information is transmitted via satellite. In some aspects, the operations of block 4704 may correspond to the operations of block 2408 of FIG.

  Satellite handoff information may take various forms as taught herein. In some aspects, the satellite handoff information may include a table that includes the handoff activation time. In some aspects, the satellite handoff information may include at least one detuning time. In some aspects, the handoff information may be for at least one future handoff (eg, a next handoff, a later handoff, or some other handoff that may occur). In some aspects, the handoff information may be for the next beam handoff and the occurrence of at least one future satellite handoff (eg, the next handoff and any other subsequent handoffs, etc.) May be for the next two handoffs).

  In some implementations, the transmit circuitry / module 4622 of FIG. 46 performs the operations of block 4704. In some implementations, the transmitting code 4642 of FIG. 46 is executed to perform the operations of block 4704.

  In some aspects, process 4700 may further include performing a handoff for the user terminal to different beams and at least one satellite based on the satellite handoff information. This handoff may involve a change of at least one of a satellite access network (SAN) or a GN antenna. This handoff may involve at least one change of satellite beam or forward service link (FSL) frequency. In some aspects, these operations may correspond to the operations of block 2410 of FIG. In some implementations, the circuitry / module 4624 for performing the handoff of FIG. 46 performs these operations. In some implementations, code 4644 for performing the handoff of FIG. 46 is executed to perform these operations.

  In some aspects, process 4700 may further include receiving a measurement message from the user terminal and determining whether to modify satellite handoff information based on the measurement message. Modification of the satellite handoff information may include advancing the timing of the handoff or delaying the timing of the handoff. In some aspects, these operations may correspond to the operations of block 3102 and block 3104 of FIG. In some implementations, the receive circuitry / module 4626 of FIG. 46 performs a receive operation. In some implementations, the receive code 4646 of FIG. 46 is executed to perform a receive operation. In some implementations, the circuit / module 4628 for determining whether to modify in FIG. 46 performs the determining operation. In some implementations, code 4648 for determining whether to modify in FIG. 46 is executed to perform the determining operation.

  In some aspects, the process 4700 may further include the steps of determining a measurement gap for measuring a satellite signal and transmitting information indicative of the measurement gap to the user terminal, the measurement message measuring the measurement An indication of measurement of signals from at least one satellite made during the gap is included. In some aspects, these operations may correspond to the operations of block 3506 and block 3508 of FIG. In some implementations, the circuit / module 4636 for determining the measurement gap of FIG. 46 performs the determining operation. In some implementations, code 4656 for determining the measurement gap of FIG. 46 is executed to perform the determination operation. In some implementations, the transmit circuitry / module 4622 of FIG. 46 performs a transmit operation. In some implementations, the transmit code 4642 of FIG. 46 is executed to perform a transmit operation.

  In some aspects, process 4700 may further include 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 sensitive. Selection of the handoff procedure may include enabling or disabling monitoring of measurement messages from the user terminal based on whether the user terminal is dually sensitive. In some aspects, these operations may correspond to the operations of block 2702 and block 2706 of FIG. In some implementations, the receive circuitry / module 4626 of FIG. 46 performs a receive operation. In some implementations, the receive code 4646 of FIG. 46 is executed to perform a receive operation. In some implementations, the circuit / module 4630 for selecting in FIG. 46 performs the selecting operation. In some implementations, the code for selection 4650 of FIG. 46 is executed to perform the selection operation.

  In some aspects, the process 4700 may further include determining a handoff time of the user terminal and transferring at least one user queue prior to the handoff. In some aspects, these operations may correspond to the operations of block 3702 and block 3704 of FIG. In some implementations, the circuit / module 4632 for determining the time of FIG. 46 performs the determining operation. In some implementations, code 4652 for determining the time in FIG. 46 is executed to perform the determination operation. In some implementations, the transmit circuitry / module 4634 of FIG. 46 performs a transmit operation. In some implementations, the forwarding code 4654 of FIG. 46 is executed to perform a forwarding operation.

  In some aspects, the process 4700 may further include receiving from the 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 2902 of FIG. In some implementations, the receiving circuit / module 4626 of FIG. 46 performs these operations. In some implementations, the receiving code 4646 of FIG. 46 is executed to perform these operations.

  In some aspects, the process 4700 may further include determining that a measurement gap for measuring satellite signals is not needed, and as a result of the determination, generating the satellite handoff information comprises satellite handoff information. Not include the detuning time. In some aspects, these operations may correspond to the operations of blocks 3502 and 3504 of FIG. In some implementations, the circuit / module 4638 performs these operations to determine that the measurement gap of FIG. 46 is not needed. In some implementations, code 4658 is executed to perform these operations to determine that the measurement gap of FIG. 46 is not necessary.

Seventh Exemplary Process FIG. 48 shows a process 4800 for communication, in accordance with certain aspects of the present disclosure. Process 4800 may be performed within processing circuitry (eg, processing circuitry 4610 of FIG. 46) that may be located in a GN or some other suitable device. In some implementations, process 4800 may be performed by GN for at least one non-geostationary satellite. In some implementations, process 4800 represents operations performed by GN controller 250 of FIG. Of course, in various aspects within the scope of the present disclosure, process 4800 may be implemented by any suitable device capable of supporting communication operations.

  At block 4802, a device (eg, GN) generates satellite and cell transition information that specifies when to start and end communication with a particular cell of a particular satellite. In some aspects, the operations of block 4802 may correspond to the operations of block 2406 of FIG.

  In some aspects, the satellite and cell transition information is generated based on at least one of user terminal capability information, user terminal location information, ephemeris information, or constraints due to a running system. . In some aspects, the capability information may be whether the user terminal can sense multiple cells, whether the user terminal can sense multiple satellites, inter-cell tune time for the user terminal, or for the user terminal Indicates at least one of the inter-satellite tuning times. In some aspects, the position information includes the current position of the user terminal or the motion vector of the user terminal.

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

  In some implementations, the circuitry / module 4620 for generating in FIG. 46 performs the operations of block 4802. In some implementations, the generating code 4640 of FIG. 46 is executed to perform the operations of block 4802.

  At block 4804, the apparatus transmits satellite and cell transition information to the user terminal. In some aspects, this information is transmitted via satellite. In some aspects, the operations of block 4804 may correspond to the operations of block 2408 of FIG.

  In some implementations, the transmit circuitry / module 4622 of FIG. 46 performs the operations of block 4804. In some implementations, the sending code 4642 of FIG. 46 is executed to perform the operations of block 4804.

  In some aspects, process 4800 further includes performing a handoff for the user terminal to a different cell and at least one satellite based on the satellite and cell transition information. In some aspects, these operations may correspond to the operations of block 2410 of FIG. In some implementations, the circuitry / module 4624 for performing the handoff of FIG. 46 performs these operations. In some implementations, code 4644 for performing the handoff of FIG. 46 is executed to perform these operations.

  In some aspects, the process 4800 may further include receiving a measurement message from the user terminal and determining whether to modify satellite and cell transition information based on the measurement message. In some aspects, the 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 block 3102 and block 3104 of FIG. In some implementations, the circuit / module 4626 for receiving in FIG. 46 and / or the circuit / module 4628 for determining whether to modify or perform these operations. In some implementations, code 4646 for receiving in FIG. 46 and / or code 4648 for determining whether to modify are performed to perform these operations.

  In some aspects, the process 4800 further includes selecting a handoff procedure for the user terminal based on the capability information received from the user terminal. In some aspects, selection of the handoff procedure includes enabling or disabling monitoring of measurement messages from the user terminal based on whether the user terminal is dually sensitive. In some aspects, these operations may correspond to the operations of block 2706 of FIG. In some implementations, the circuit / module 4630 for the selection of FIG. 46 performs these operations. In some implementations, the code for selection 4650 of FIG. 46 is executed to perform these operations.

  In some aspects, the process 4800 further includes determining a handoff time of the user terminal and transferring the user queue prior to the handoff. In some implementations, circuit / module 4632 for determining the time in FIG. 46 and / or circuit / module 4634 for transferring perform these operations. In some implementations, code 4652 for determining the time in FIG. 46 and / or code 465 for transferring are performed to perform these operations.

Fourth Exemplary Device FIG. 49 shows a block diagram of an exemplary hardware implementation of another device 4900 configured to communicate, in accordance with one or more aspects of the present disclosure. For example, apparatus 4900 may be embodied or implemented within a UT or some other type of device supporting wireless communication. Thus, in some aspects, apparatus 4900 may be an example of UT 400 or UT 401 of FIG. In various implementations, the device 4900 may be embodied in a mobile phone, a smartphone, a tablet, a portable computer, a server, a personal computer, a sensor, an entertainment device, a vehicle component, a medical device, or any other electronic device having circuitry. Or may be implemented.

  Apparatus 4900 includes a communication interface (eg, at least one transceiver) 4902, a storage medium 4904, a user interface 4906, a memory device 4908 (eg, storing satellite related information 4918), and processing circuitry (eg, at least one processor) Including 4910). In various implementations, the user interface 4906 may be a keypad, a display, a speaker, a microphone, a touch screen display, or one of several other circuits for receiving input from the user or sending output to the user. Or may include more than one. Communication interface 4902 may be coupled to one or more antennas 4912 and may include a transmitter 4914 and a receiver 4916. In general, the components of FIG. 49 may be similar to corresponding components of apparatus 4600 of FIG.

  In accordance with one or more aspects of the present disclosure, processing circuitry 4910 may be any of features, processes, functions, operations, and / or routines for any or all of the devices described herein. Or can be adapted to perform all. For example, processing circuit 4910 is described with reference to FIGS. 11, 12, 15-23, 25, 26, 28, 30, 32-34, 36, 38, 50, and 51. It may be configured to perform one or more of the steps, functions, and / or processes described. As used herein, the term "adapted" with respect to processing circuitry 4910 means that processing circuitry 4910 performs particular processes, functions, operations, and / or routines in accordance with the various features described herein. May refer to one or more of being configured, to be utilized as such, to be implemented as such, and / or to be programmed as such.

  Processing circuit 4910 is described with respect to FIGS. 11, 12, 15-23, 25, 26, 28, 30, 32-34, 36, 38, 50, and 51. It may be a special processor, such as an application specific integrated circuit (ASIC) that functions as a means (eg, a structure for it) to perform one or more of the described operations. The processing circuit 4910 serves as an example of means for transmitting and / or means for receiving. In various implementations, processing circuitry 4910 may incorporate the functionality of control processor 420 of FIG.

  According to at least one example of the apparatus 4900, the processing circuit 4910 comprises: circuit / module 4920 for receiving, circuit / module 4922 for performing a handoff, circuit / module 4924 for measuring a signal, Circuit / module 4926, circuit / module 4928 for determining whether to transmit, or circuit / module 4930 for performing a random access procedure. In various implementations, circuits / modules 4920 for receiving, circuits / modules 4922 for performing handoff, circuits / modules 4924 for measuring signals, circuits / modules 4926 for transmitting, whether to transmit Circuits / modules 4928 for determining and circuits / modules 4930 for performing random access procedures may correspond at least in part to control processor 420 of FIG.

  The circuitry / modules 4920 for receiving may be, for example, circuitry and / or programming (eg, storage medium 4904) adapted to perform certain functions related to receiving information (eg, data) from another device. And the code for reception 4932 stored in In various implementations, the information to be received may include satellite and cell transition information that specifies when to start and end communication with a particular cell of a particular satellite. In various implementations, the information to be received may include information indicative of a measurement gap. In various implementations, the information to be received may include a dedicated preamble signature. First, the circuitry / modules 4920 for receiving obtain the received information. For example, circuitry / modules 4920 for receiving may obtain this information directly from components of apparatus 4900 or from devices (eg, satellites) that have relayed information from GN. In the former case, circuitry / modules 4920 to receive this information from communication interface 4902 (eg, UT transceiver as described above for UT 400 in FIG. 4), memory device 4908, or some other component You can get In some implementations, circuitry / modules 4920 for receiving locate a memory location of a value in memory device 4908 and invoke a read of that location. In some implementations, circuitry / modules 4920 for receiving may process (eg, decode) the received information. A circuit / module 4920 for receiving outputs the received information (eg, memory device 4908, a circuit / module 4922 for performing a handoff, or some other component of apparatus 4900) Send to In some implementations, communication interface 4902 includes circuitry / modules 4920 for receiving and / or code 4932 for receiving.

  Circuits / modules 4922 for performing the handoff may, for example, be circuits and / or programming adapted to perform some of the functions associated with performing the handoff to a particular cell of a particular satellite and / or programming (eg, storage Code 4934) for performing the handoff stored in medium 4904 may be included. In some implementations, the circuitry / module 4922 for performing the handoff identifies a particular cell of a particular satellite based on the satellite and cell transition information (eg, Table 1). To this end, the circuit / module 4922 for performing the handoff collects this information, processes this information to identify the satellites and cells, and communicates with the GN through the identified satellites and cells Reconfigure communication parameters to make them For example, at a particular point in time, the circuitry / module 4922 for performing the handoff may use the information in Table 1 to determine whether the user terminal should switch to a different satellite cell Can. As another example, triggers can be prepared at the cell / satellite transition times (eg, frame numbers) shown in Table 1 (Table 1).

  Circuits / modules 4924 for measuring signals are, for example, circuits and / or programming adapted to perform several functions related to receiving and processing signals from at least one satellite (eg storage medium 4904) can be included to measure the signal stored in 4904. First, a circuit / module 4924 for measuring the signal receives the signal. For example, circuitry / module 4924 for measuring signals may obtain signal information directly from components of apparatus 4900 or from satellites that transmitted the signals. As an example of the former case, circuitry / module 4924 for measuring signals may be received via communication interface 4902 (eg, UT transceiver as described above for UT 400 in FIG. 4), memory device 4908 (eg, received Signal information may be obtained if the signal is digitized) or from some other component of the device 4900. The circuit / module 4924 for measuring the signal then processes the received signal (eg, to determine at least one signal quality of the signal). Finally, the circuit / module 4924 for measuring the signal generates an indication of this measurement and sends this indication to the memory device 4908, the circuit / module 4924 for transmitting, or some other component of the apparatus 4900. Send. In some implementations, communication interface 4902 includes circuitry / modules 4924 for measuring signals and / or code 4936 for measuring signals.

  Circuits / modules 4926 for transmitting may be, for example, circuits and / or programming (eg, storage medium 4904) adapted to perform certain functions related to transmitting information (eg, a message) to another device. And the code for transmission 4938 stored in First, circuitry / module 4926 for transmitting obtains information to be transmitted (eg, from memory device 4908, circuitry / module 4924 for measuring signals, or some other component). In various implementations, the information to be transmitted may include a measurement message based on a measured signal, 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 that includes user terminal capability information. In various implementations, the information to be transmitted may include a message that includes user terminal location information. In various implementations, the information to be transmitted may include a message that includes user terminal paging area information. Circuitry / module 4926 for transmitting may format the information for transmission (eg, according to message format, according to protocol, etc.). The circuit / module 4926 for transmitting then causes the information to be transmitted (eg, via satellite signaling) via the wireless communication medium. To this end, circuitry / modules 4926 for transmitting transmit data to communication interface 4902 (eg, a UT transceiver as described above for UT 400 in FIG. 4) or some other component It can. In some implementations, communication interface 4902 includes circuitry / modules 4926 for transmitting and / or code 4938 for transmitting.

  Circuits / modules 4928 for determining whether to transmit, for example, circuits and / or programming adapted to perform some functions related to determining whether to transmit a message (eg storage medium 4904) may be included to determine whether to transmit or not. In some implementations, the information to be transmitted may include a measurement message based on the signal to be measured. First, the circuit / module 4928 for determining whether to transmit (for example, from the memory device 4908, the circuit / module 4924 for measuring a signal, or some other component) to make a determination of the transmission. Get information used for For example, circuitry / module 4928 for determining whether to transmit may obtain signal quality information from circuitry / module 4924 for measuring the signal. In this case, the circuit / module 4928 for determining whether to transmit determines whether the signal from the current serving satellite and / or the signal from the target satellite is inappropriate (eg, signal quality information signal quality Can be determined by comparison with a threshold). For example, transmission of a measurement message may be triggered if the signal is inappropriate. Finally, the circuit / module 4928 for determining whether to transmit generates an indication of this determination, the memory device 4908, the circuit / module 4926 for transmitting this indication or some other of the apparatus 4900. Send to a component.

  The circuit / module 4930 for performing the random access procedure is, for example, a circuit adapted to perform some functions related to performing a non-contention based random access procedure using a dedicated preamble signature And / or programming (eg, code 4942 for performing random access procedures stored on storage medium 4904). In some implementations, the circuitry / modules 4930 for performing random access procedures perform the random access operations described above with respect to FIG. In some implementations, the circuitry / modules 4930 for performing random access procedures perform the random access operations described above with respect to FIG. In some implementations, the circuitry / modules 4930 for performing random access procedures perform the random access operations described above with respect to FIG. In some implementations, the circuitry / modules 4930 for performing random access procedures perform the random access operations described above with respect to FIG. In some implementations, the circuitry / modules 4930 for performing random access procedures perform the operations described above with respect to FIG.

  As mentioned above, the programming stored by storage medium 4904, when executed by processing circuitry 4910, causes processing circuitry 4910 to perform one of the various functions and / or processing operations described herein. Or run more than one. For example, programming may be performed by the processing circuitry 4910 to cause the processing circuitry 4910 to, in various implementations, FIGS. 11, 12, 15-23, 25, 26, 28, 30, 30, One or more of the various functions, steps, and / or processes described herein with respect to 32-34, 36, 38, 50, and 51 may be performed. As shown in FIG. 49, the storage medium 4904 has a code 4932 to receive, a code 4934 to perform a handoff, a code 4936 to measure a signal, a code 4938 to transmit, and determine whether to transmit. Code 4940, or code 4942 for performing a random access procedure.

Eighth Exemplary Process FIG. 50 illustrates a process 5000 for communication in accordance with certain aspects of the present disclosure. Process 5000 may be performed within processing circuitry (eg, processing circuitry 4910 of FIG. 49) that may be located in a UT or some other suitable device. In some implementations, process 5000 represents operations performed by control processor 420 of FIG. Of course, in various aspects within the scope of the present disclosure, process 5000 may be implemented by any suitable device capable of supporting communication operations.

  At block 5002, an apparatus (eg, 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 5002 may correspond to the operations of block 2504 of FIG.

  Satellite handoff information may take various forms as taught herein. In some aspects, the satellite handoff information may include a table that includes the handoff activation time. In some aspects, the satellite handoff information may include at least one detuning time. In some aspects, handoff information may be defined based in part on satellite pointing error. In some aspects, the handoff information may be for at least one future handoff (eg, a next handoff, a later handoff, or some other handoff that may occur). In some aspects, the handoff information may be for the next beam handoff and the occurrence of at least one future satellite handoff (eg, the next handoff and any other subsequent handoffs, etc.) May be for the next two handoffs).

  In some implementations, the receiving circuit / module 4920 of FIG. 49 performs the operations of block 5002. In some implementations, the receiving code 4932 of FIG. 49 is executed to perform the operations of block 5002.

  At block 5004, the apparatus performs a handoff to a particular cell of a particular satellite based on the satellite handoff information. In some aspects, the operations of block 5004 may correspond to the operations of block 2506 of FIG.

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

  In some implementations, the circuitry / module 4922 for performing the handoff of FIG. 49 performs the operations of block 5004. In some implementations, code 4934 for performing the handoff of FIG. 49 is executed to perform the operations of block 5004.

  In some aspects, the process 5000 may further include measuring a signal from at least one satellite and transmitting a measurement message based on the measured signal, the satellite handoff information measuring A message is received as a result of being sent. The measurement message may include at least one of measurement data based on the measured signal, a request to advance the timing of the handoff, or a request to delay the timing of the handoff. In some aspects, these operations may correspond to the operations of block 3004 and block 3008 of FIG.

  In some aspects, the process 5000 may further include receiving information indicative of a measurement gap for measuring a satellite signal, wherein measurement of a signal from at least one satellite is performed during the measurement gap. . In some aspects, these operations may correspond to the operations of block 3602 and block 3604 of FIG.

  In some aspects, the process 5000 further determines the measurement message based on at least one of whether the signal from the current serving satellite is inappropriate or whether the signal from the target satellite is inappropriate. It may include the step of determining whether to send. In some aspects, these operations may correspond to the operations of block 3006 of FIG.

  In some aspects, process 5000 may further include transmitting a message including user terminal capability information, wherein the received satellite handoff information is based on the 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, inter-beam tuning time of the user terminal, or inter-satellite tuning time of the user terminal One can be shown. Transmission of a message containing user terminal capability information may be triggered as a result of the initial connection to the satellite. In some aspects, these operations may correspond to the operations of block 2606 of FIG.

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

  In some aspects, process 5000 may further include receiving a dedicated preamble signature and performing a non-contention based random access procedure using the dedicated preamble signature. In some aspects, these operations may correspond to the operations of block 3802 and block 3804 of FIG.

  In some aspects, the process 5000 further determines the measurement message based on at least one of whether the signal from the current serving satellite is inappropriate or whether the signal from the target satellite is inappropriate. It may include the step of determining whether to send. In some aspects, these operations may correspond to the operations of block 2806 of FIG.

Ninth Exemplary Process FIG. 51 shows a process 5100 for communication, in accordance with certain aspects of the present disclosure. Process 5100 may be performed within processing circuitry (eg, processing circuitry 4910 of FIG. 49) that may be located in a UT or some other suitable device. In some implementations, process 5100 represents operations performed by control processor 420 in FIG. Of course, in various aspects within the scope of the present disclosure, process 5100 may be implemented by any suitable device capable of supporting communication operations.

  At block 5102, a device (eg, UT) receives satellite and cell transition information that specifies when to start and end communication with a particular cell of a particular satellite. In some aspects, the operations of block 5102 may correspond to the operations of block 2504 of FIG.

  In some implementations, the receive circuitry / module 4920 of FIG. 49 performs the operations of block 5102. In some implementations, the receiving code 4932 of FIG. 49 is executed to perform the operations of block 5102.

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

  In some implementations, the circuitry / module 4922 for performing the handoff of FIG. 49 performs the operations of block 5104. In some implementations, code 4934 for performing the handoff of FIG. 49 is executed to perform the operations of block 5104.

  In some aspects, the process 5100 further includes measuring a signal from the at least one satellite and transmitting a measurement message based on the measured signal, the satellite and cell transition information including the measurement message. Received as a result of sending In some aspects, the measurement message includes at least one of measurement data, a request to advance the timing of the handoff, or a request to delay the timing of the handoff. In some aspects, process 5100 further determines the measurement message based on at least one of whether the signal from the current serving satellite is inappropriate or whether the signal from the target satellite is inappropriate. Including the step of determining whether to send. In some aspects, these operations may correspond to the operations of blocks 3004-3008 of FIG. In some implementations, circuit / module 4924 for measuring the signal of FIG. 49 and / or circuit / module 4928 for determining whether to transmit may perform these operations. In some implementations, code 4936 for measuring the signal of FIG. 49 and / or code 4940 for determining whether to transmit are performed to perform these operations.

  In some aspects, process 5100 further includes transmitting a message including user terminal capability information, wherein the satellite and cell transition information is based on the user terminal capability information. In some aspects, the user terminal capability information may be whether the user terminal can sense multiple cells, whether the user terminal can sense multiple satellites, inter-cell tuning time of the user terminal, or inter-satellite satellites of the user terminal Indicates at least one of the tuning times. In some aspects, transmission of a message containing user terminal capability information is triggered as a result of the initial connection to the satellite. In some aspects, these operations may correspond to the operations of blocks 2602-2606 of FIG. In some implementations, the transmit circuitry / module 4926 of FIG. 49 performs these operations. In some implementations, the transmit code 4938 of FIG. 49 is executed to perform these operations.

  In some aspects, the process 5100 further includes transmitting a message including user terminal location information, wherein the satellite and cell transition information is based on the user terminal location information. In some aspects, the user terminal location information includes the current user terminal location or the motion vector of the user terminal. In some aspects, transmission of the message including the user terminal location information is at least one result of an initial connection to the satellite, whether the user terminal has crossed a geographical boundary, or has exceeded an error limit. Triggered In some aspects, these operations may correspond to the operations of blocks 2802-2806 of FIG. In some implementations, the transmit circuitry / module 4926 of FIG. 49 performs these operations. In some implementations, the transmit code 4938 of FIG. 49 is executed to perform these operations.

Additional Embodiments The examples described herein are provided to illustrate some concepts of the present disclosure. Those skilled in the art will appreciate that these are merely exemplary in nature and that other examples may fall within the scope of the present disclosure and the appended claims. Based on the teachings herein, the aspects disclosed herein may be implemented independently of any other aspects, and two or more of these aspects may be combined in various ways. Those skilled in the art should understand that there is a possibility. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such devices may also be implemented using other structures, functions, or structures and functions in addition to or in addition to one or more of the aspects described herein. Well, or such a method may be practiced.

  As those skilled in the art will readily appreciate, the various aspects described throughout the present disclosure may be extended to any suitable telecommunication system, network architecture, and communication standard. By way of example, the various aspects may be applied to wide area networks, peer to peer networks, local area networks, other suitable systems, or any combination thereof, including those described by standards not yet defined. .

  Many aspects are described, for example, with respect to a series of activities to be performed by an element of a computing device. The various activities described herein include specific circuits such as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), field programmable gates May be executed by an array (FPGA), or various other types of general purpose or special purpose processors or circuits, and may be executed by program instructions executed by one or more processors, or both It will be appreciated that the combination may be performed. In addition, these sequences of activities described herein, when executed, store any corresponding set of computer instructions that, when executed, causes the associated processor to perform the functions described herein. It may be considered to be fully embodied in a computer readable storage medium. Thus, the various aspects of the present disclosure may be embodied in several different forms, all considered to be within the scope of the claimed subject matter. Further, for each aspect described herein, the corresponding form of any such aspect is described herein as, for example, "a logic configured to perform the described operations". There is a thing.

  Those skilled in the art will appreciate 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 mentioned throughout the above description may be voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any of them It can be expressed by a combination.

  Further, those skilled in the art will appreciate that various exemplary logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein may be electronic hardware, computer software, or a combination of both. It will be understood that it can be implemented as 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 be interpreted as causing a departure from the scope of the present disclosure. is not.

  One or more of the components, steps, features and / or functions shown above may be rearranged and / or combined as a single component, step, feature or function Or it may be embodied in several components, steps or functions. Additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. The apparatus, devices, and / or components shown above may be configured to perform one or more of the methods, features, or steps described herein. Also, the novel algorithms described herein may be efficiently implemented in software and / or may be embedded in hardware.

  It is to be understood that the specific order or hierarchy of steps in the disclosed method is an illustration of an exemplary process. It is understood that the particular order or hierarchy of steps in the method may be rearranged based on design preferences. The appended method claims present elements of the various steps in a sample order, and are intended to be limited to the specific order or hierarchy presented, unless specifically stated in the claims. It is not something to do.

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

  The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. Similarly, the term "aspect" does not require that all aspects include the discussed feature, advantage, or mode of operation.

  The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural as well, unless the context clearly indicates otherwise. The terms "comprises, comprising" or "includes," as used herein, denote the presence of the recited feature, integer, step, action, element or component. It will be further understood that the explicitness does not exclude the presence or addition of one or more other features, integers, steps, acts, elements, components, or groups thereof. Furthermore, the term "or" has the same meaning as the Boolean operator "OR", ie, includes the possibilities of "any" and "both", and unless otherwise specified, "exclusive logic It should be understood that it is not limited to "sum" ("XOR"). It is also to be understood that the symbol "/" between two adjacent words has the same meaning as "or" unless expressly stated otherwise. Furthermore, phrases such as “connected to,” “coupled to,” or “communicating with” are not limited to direct connections, unless expressly stated otherwise.

  Any reference to an element, using the designation "first", "second", etc., herein does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient way of distinguishing between two or more elements or instances of elements. Thus, reference to the first element and the second element does not mean that only two elements can be used there, or that the first element must somehow precede the second element . Also, unless otherwise stated, the set of elements may comprise one or more elements. In addition, the term “at least one of a, b, or c” or “a, b, c, or any combination thereof” used in the description or claims may be “a or b” Or c or any combination of these elements. For example, the term may include a or b or c or a or b or a and c or a and b and c or 2a or 2b or 2c or 2c or 2a and b or the like.

  The term "determining" as used herein encompasses a wide variety of activities. For example, "determining" may be calculating, calculating, processing, deriving, examining, looking up (eg, looking up in a table, database or other data structure) , May include such as confirmation. Also, "determining" may include receiving (eg, receiving information), accessing (eg, accessing data in a memory) and the like. Also, "determining" may include resolving, selecting, choosing, establishing and the like.

  While the above disclosure illustrates exemplary embodiments, 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 activities of the method claims in accordance with the aspects described herein need not be performed in any particular order, unless explicitly stated otherwise. Furthermore, although elements may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

100 satellite communication system
106 Infrastructure
108 Internet
110 PSTN
112 forward feeder link
114 Return feeder link
116 Return Service Link
118 forward service link
122 Hand-off controller
124 Hand-off controller
126 signaling
130 Handoff Information Generator
132 Handoff Information Transmission Controller
134 Handoff Information
136 Handoff Information Request Controller
138 Handoff Information
200 GN
201 GN, ground network
205 antenna
210 RF subsystem
212 RF transceiver
214 RF controller
216 antenna controller
220 Digital Subsystem
222 Digital Receiver
224 Digital Transmitter
226 BB processor
228 CTRL processor
230 PSTN interface
232 processing circuit
234 Memory Device
236 Hand-off controller
240 LAN interface
245 GN interface
250 GN controller
251 Local time / frequency / location reference
300 satellites
301F Forward Feeder Link
301R Return feeder link
302F Forward Feeder Link
302R Return feeder link
310 forward transponder
311 First band pass filter
312 first low noise amplifier
313 Frequency converter
314 Second low noise amplifier
315 Second band pass filter
316 power amplifier
320 return transponder
321 First band pass filter
322 first low noise amplifier
323 frequency converter
324 Second low noise amplifier
325 Second band pass filter
326 Power Amplifier
330 Oscillator
340 controller
351 Forward Link Antenna
352 Forward Link Antenna
361 Return Link Antenna
362 Return Link Antenna
400 user terminal
401 User terminal
410 antenna
412 duplexer
414 Analog Receiver
416 Digital Data Receiver
418 searcher receiver
420 control processor
422 Digital baseband circuit
426 transmit modulator
428 Digital Transmit Power Controller
430 Analog Transmit Power
432 memory
434 Local time / frequency / location reference
442 processing circuit
444 memory device
446 handoff controller
450 UE interface circuit
500 user equipment
501 User Equipment
502 LAN interface
504 antenna
506 WAN transceiver
508 WLAN transceiver
510 SPS receiver
512 processor
514 motion sensor
516 Memory
518 data
520 instructions
522 User Interface
524 Microphone / Speaker
526 Keypad
528 Display
600 communication system
602 First device
604 Second device
606 Idle Mode Handoff Information
608 transmitter
610 Idle mode handoff information
612 Receiver
614 Idle mode handoff information
700 non-geostationary satellite communication system
702 UT
704 ground network
712 NAC
714 RF subsystem
716 CNCP
718 CNUP
720 Other networks
722 Handoff Information
724 Idle mode handoff information
726 Idle Mode Handoff Information
728 Handoff information
800 signaling call flow
802 UT
804 GN
808 Idle mode handoff table request message
810 UL location report message
812 Idle mode handoff table response message
900 timeline
908 Paging opportunity
1000 satellite communication system
1002 UT
1004 GN
1008 Transition information
1010 UT information
1012 first signaling
1014 second signaling
1016 Measurement message
1018 NAC
1020 RF subsystem
1022 CNCP
1024 CNUP
1026 Other networks
1028 Network Entity
1030 controller
1102 UT
1104 GN
1106 Source NAC
1108 Control signaling
1110 packet data
1112 Handoff trigger
1114 Handoff process
1116 Target NAC
1120 Handoff signaling
Synchronous signaling for new satellites
1126 Connection signaling
1128 connection signaling
1202 UT
1204 GN
1206 Source NAC
1208 Control signaling
1210 packet data
1212 Handoff trigger
1218 Measurement message
1220 Target NAC
1222 Handoff process
1226 Handoff signaling
1230 Synchronous signaling for new satellites
1232 connection signaling
1234 connection signaling
1306 UT
1308 AxP (ACP / ATP)
1310 Satellite RF subsystem
1312 BxP (BCP / BTP)
1400 graph
1402 expected first beam
1404 expected second beam
1406 shifted first beam
1408 Gain contour shift
1410 first intersection point
1412 second intersection point
1414 Expected Handoff Time
1416 Expected Handoff Time Gain
1418 New Handoff Time
1420 Gain at New Handoff Time
1502 UT
1504 Source BxP
1506 Target BxP
1508 Source AxP
1510 GN
1512 packet data
1514 packet data
1516 packet data
1518 points
1520 packet data
1522 packet data
1524 packet data
1602 UT
1604 Source BxP
1606 Target BxP
1608 Source AxP
1610 GN
1612 packet data
1614 packet data
1616 packet data
1618 packet data
1620 packet data
1622 packet data
1624 packet data
1626 packet data
1628 packet data
1702 UT
1704 Source BxP
1706 Target BxP
1708 Source AxP
1710 GN
1712 packet data
1714 packet data
1716 packet data
1718 parentheses
1720 points
1722 blocks
1724 packet data
1726 packet data
1728 packet data
1802 UT
1804 Source BxP
1806 Target BxP
1808 Source AxP
1810 GN
1812 packet data
1814 packet data
1816 packet data
1818 packet data
1820 packet data
1822 packet data
1824 packet data
1826 packet data
1828 packet data
2002 UT
2004 Source BxP
2006 Target BxP
2008 Source AxP
2010 GN
2012 Target AxP
2014 MM
2016 packet data
2018 packet data
2020 packet data
2022 packet data transfer
2024 packet data transfer
2028 packet data transfer
2030 blocks
2032 packet data
2034 packet data
2036 packet data
2038 packet data
2040 packet data
2042 end marker packet
2044 arrow
2046 arrow
2048 end marker packet
2050 packet data
2052 packet data
2054 packet data
2056 packet data
2302 UT
2304 Source BxP or Target BxP
2306 Source AxP or Target BxP
2312 packet data
2314 packet data
2400 processes
2500 processes
2600 process
2700 processes
2800 processes
2900 process
3000 processes
3100 process
3200 process
3300 process
3400 processes
3900 devices
3902 communication interface
3904 storage medium
3906 user interface
3908 memory device
3910 processing circuit
3912 antenna
3914 transmitter
3916 Receiver
3918 Idle Mode Handoff Information
3920 Circuits / modules to identify
3922 Circuits / modules to decide whether to transmit
Circuits / modules for transmitting 3924
3926 Circuits / modules for receiving
3928 Circuits / modules for handing off
3930 Circuits / modules for determining position information
Code to identify 3932
3934 Code to decide whether to send
3936 Code to send
3938 Code to receive
Code for 3940 Handoff
3942 Code for determining location information
4000 processes
4100 Process
4200 process
4300 devices
4302 communication interface
4304 Storage medium
4306 User Interface
4308 memory device
4310 Processing Circuit
4312 antenna
4314 Transmitter
4316 Receiver
4318 Idle Mode Handoff Information
4320 Circuits / modules to identify
4322 Circuits / modules for deciding whether to send
4324 Circuits / modules for transmission
4326 Circuits / modules for receiving
Circuits / modules for generating 4328
4330 Circuits / modules to determine movement
4332 Circuits / modules to determine how many entries to send
4340 Code to identify
4342 Code to decide whether to send
4344 Code to send
4346 Code to receive
Code to generate 4348
4350 Code to determine movement
4352 Code to determine how many entries to send
4400 processes
4500 processes
4600 devices
4602 communication interface
4604 storage medium
4606 User Interface
4608 memory device
4610 processing circuit
4612 antenna
4614 transmitter
4616 Receiver
4618 satellite related information
4620 Circuits / Modules to Generate
4622 Circuits / modules for transmission
Circuit / module to perform 4624 handoff
4626 Circuits / modules for receiving
4628 Circuits / modules to decide whether to fix
4630 Circuits / modules to choose
Circuit / module for determining 4632 time
4634 Circuits / modules for transfer
4636 Circuits / modules to determine measurement gap
4638 Circuits / modules to determine that a measurement gap is not required
Code to generate 4640
4642 Code to send
4644 Code to Handoff
4646 Code to receive
4648 Code to decide whether to fix
4650 Code to select
Code for determining time 4652
4654 Code to transfer
4656 Code to determine measurement gap
4658 Code to determine that a measurement gap is not required
4700 processes
4800 process
4900 devices
4902 communication interface
4904 Storage medium
4906 User Interface
4908 memory device
4910 processing circuit
4912 antenna
4914 transmitter
4916 Receiver
4918 Satellite related information
4920 Circuits / modules for receiving
4922 Circuits / Modules to Perform Handoff
Circuits / modules for measuring 4924 signals
4926 Circuits / modules for transmission
4928 Circuits / modules to decide whether to send
4930 Circuits / Modules to Perform Random Access Procedure
Code to receive 4932
Code to perform the 4934 handoff
Code for measuring 4936 signals
4938 Code to send
4940 Code to decide whether to send
4942 Code to perform the random access procedure
5000 processes
5100 process

Claims (86)

A method of communication for the device,
Identifying a time associated with a particular one of the set of handoff entries, wherein the set of handoff entries identifies a set of satellites for the handoff of the device;
Determining whether to send a request for an updated set of handoff entries based on the identified time;
Sending the request for an updated set of handoff entries if the determination is to send the request.   The method of claim 1, wherein the set of handoff entries comprises an idle mode handoff table.   The method of claim 1, wherein the time comprises a start time of a handoff to a satellite of the set of satellites.   The method of claim 1, wherein the particular entry comprises the last entry of the set of handoff entries.   The method of claim 1, wherein the set of satellites is for idle mode operation of the device.   The method of claim 1, wherein the time indicates when the device should hand off to one satellite of the set of satellites while the device is in idle mode.   The method of claim 1, further comprising transmitting the indication of time along with the transmission of the request.   The method of claim 1, further comprising transmitting an indication of a time to live associated with the set of handoff entries with the transmission of the request. Receiving the updated set of handoff entries after sending the request;
The method of claim 1, further comprising: handing off the device to a satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. Further comprising receiving an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit;
10. The method of claim 9, wherein the handoff to the satellite identified by the updated set of handoff entries is performed on the at least one carrier frequency.   The method according to claim 1, wherein the request is communicated when the device establishes a wireless connection with a terrestrial network (GN). Determining location information of the device;
Transmitting the location information along with the transmission of the request.   The method of claim 1, wherein the device comprises a user terminal.   The method of claim 1, wherein the request is sent to a terrestrial network. With memory
A processor coupled to the memory;
The processor and the memory are
Identifying a time associated with a particular one of the set of handoff entries, wherein the set of handoff entries identifies a set of satellites for the handoff of the device;
Determining whether to send a request for an updated set of handoff entries based on the identified time;
Transmitting the request for the updated set of handoff entries if the determination is to send the request.   16. The apparatus of claim 15, wherein the time comprises a start time of a handoff to a satellite of the set of satellites.   16. The apparatus of claim 15, wherein the particular entry comprises the last entry of the set of handoff entries.   16. The apparatus of claim 15, wherein the time indicates when the apparatus should handoff to one satellite of the set of satellites while the apparatus is in idle mode. The processor and the memory are further
16. The apparatus of claim 15, configured to transmit the indication of time along with the transmission of the request. The processor and the memory are further
16. The apparatus of claim 15, configured to transmit an indication of a time to live associated with the set of handoff entries along with the transmission of the request. The processor and the memory are further
Receiving the updated set of handoff entries after sending the request;
16. The apparatus of claim 15, configured to handoff to a satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. The processor and the memory are further configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit.
22. The apparatus of claim 21, wherein the handoff to the satellite identified by the updated set of handoff entries is performed on the at least one carrier frequency. The processor and the memory are further
Determine the location information of the device;
The apparatus of claim 15, configured to transmit the location information with the transmission of the request. A device for communication,
Means for identifying a time associated with a particular one of a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for the device's handoff.
Means for determining whether to send a request for an updated set of handoff entries based on the determined time;
Means for sending the request for an updated set of handoff entries, if the determination is to send the request. Said means for transmitting
25. The apparatus of claim 24, configured to transmit the indication of time with the transmission of the request. Said means for transmitting
25. The apparatus of claim 24, configured to transmit an indication of a time to live associated with the set of handoff entries along with the transmission of the request. Means for receiving the updated set of handoff entries after sending the request;
25. The apparatus of claim 24, further comprising: means for handing off the apparatus to a satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. The means for receiving is configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit.
28. The apparatus of claim 27, wherein the handoff to the satellite identified by the updated set of handoff entries is performed at the at least one carrier frequency. Further comprising means for determining position information of the device;
25. The apparatus of claim 24, wherein the means for transmitting is configured to transmit the location information with the transmission of the request. Non-transitory computer readable medium storing computer executable code, said code comprising
Identifying a time associated with a particular entry of the set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of the device;
Determining whether to send a request for an updated set of handoff entries based on the identified time;
A non-transitory computer readable medium comprising code for: sending the request for an updated set of handoff entries if the determination is to send the request. A method of communication for the device,
Identifying the amount of valid entries in the set of handoff entries, wherein the set of handoff entries identifies the set of satellites for the handoff of the device;
Determining whether to send a request for an updated set of handoff entries based on the identified amount;
Sending the request for an updated set of handoff entries if the determination is to send the request.   32. The method of claim 31, wherein the set of handoff entries comprises an idle mode handoff table.   32. The method of claim 31, wherein the set of satellites is for idle mode operation of the device.   32. The method of claim 31, wherein the set of handoff entries further specifies the time at which the device in idle mode is to be handed off to each satellite of the set of satellites. The determination of whether to send the request for the updated set of handoff entries may be:
32. The method of claim 31, comprising determining whether the set of handoff entries includes only one valid entry. Receiving the updated set of handoff entries after sending the request;
32. The method of claim 31, further comprising: handing off the device to a satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. Further comprising receiving an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit;
37. The method of claim 36, wherein the handoff to the satellite identified by the updated set of handoff entries is performed on the at least one carrier frequency.   The method according to claim 31, wherein the request is communicated when the device establishes a wireless connection with a terrestrial network (GN). Determining location information of the device;
Transmitting the position information with the transmission of the request.   32. The method of claim 31, wherein the device comprises a user terminal.   32. The method of claim 31, wherein the request is sent to a terrestrial network. A device for communication,
With memory
A processor coupled to the memory;
The processor and the memory are
Identifying the amount of valid entries in the set of handoff entries, wherein the set of handoff entries identifies the set of satellites for the handoff of the device;
Determining whether to send a request for an updated set of handoff entries based on the identified amount;
Transmitting the request for the updated set of handoff entries if the determination is to send the request.   43. The apparatus of claim 42, wherein the set of satellites is for idle mode operation of the apparatus.   43. The apparatus of claim 42, wherein the set of handoff entries further specifies the time at which the apparatus in idle mode is to be handed off to each satellite of the set of satellites. The determination of whether to send the request for the updated set of handoff entries may be:
43. The apparatus of claim 42, comprising determining whether the set of handoff entries includes only one valid entry. The processor and the memory are further
Receiving the updated set of handoff entries after sending the request;
43. The apparatus of claim 42, configured to handoff to a satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. The processor and the memory are further configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit.
47. The apparatus of claim 46, wherein the handoff to the satellite identified by the updated set of handoff entries is performed on the at least one carrier frequency. The processor and the memory are further
Determine the location information of the device;
43. The apparatus of claim 42, configured to transmit the location information with the transmission of the request. A device for communication,
Means for identifying an amount of valid entries in a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of the device;
Means for determining whether to send a request for an updated set of handoff entries based on the identified amount;
Means for sending the request for an updated set of handoff entries, if the determination is to send the request. Means for receiving the updated set of handoff entries after sending the request;
50. The apparatus of claim 49, further comprising: means for handing off the apparatus to a satellite identified by the updated set of handoff entries at a time indicated by the updated set of handoff entries. The means for receiving is configured to receive an indication of at least one carrier frequency that the next cell providing coverage for the device will use to transmit.
51. The apparatus of claim 50, wherein the handoff to the satellite identified by the updated set of handoff entries is performed on the at least one carrier frequency. Further comprising means for determining position information of the device;
50. The apparatus of claim 49, wherein the means for transmitting is configured to transmit the location information with the transmission of the request. Non-transitory computer readable medium storing computer executable code, said code comprising
Identifying the amount of valid entries in the set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of the device;
Determining whether to send a request for an updated set of handoff entries based on the identified amount;
A non-transitory computer readable medium comprising code for: sending the request for an updated set of handoff entries if the determination is to send the request. A method of communication for the device,
Identifying an effective time associated with a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of another device;
Determining whether to transmit an updated set of handoff entries based on the determined valid time;
Transmitting the updated set of handoff entries if the determination is to transmit the updated set of handoff entries.   55. The method of claim 54, wherein the set of handoff entries comprises an idle mode handoff table.   55. The method of claim 54, wherein the set of satellites is for idle mode operation of the other device.   55. The method of claim 54, wherein the set of handoff entries further specifies the time at which the other device in idle mode is to be handed off to each satellite of the set of satellites.   55. The method of claim 54, wherein the expiration time indicates the length of time that the set of entries for handoff is valid. The identification of the effective time is
55. The method of claim 54, comprising receiving the indication of the expiration time. The identification of the effective time is
Receiving an indication of a time associated with a particular one of said set of handoff entries;
Determining the valid time based on the received indication. The identification of the effective time is
55. The method of claim 54, comprising determining the time associated with the last valid entry in the set of handoff entries.   55. The method of claim 54, wherein the set of handoff entries comprises the last set of handoff entries sent by the device to the other device.   55. The method of claim 54, further comprising the step of transmitting an indication of at least one carrier frequency that a next cell providing coverage for the other device will use to transmit. Receiving location information of the other device;
Generating the updated set of handoff entries based on the location information.
55. The method of claim 54, wherein the updated set of handoff entries is sent to the other device. Further comprising receiving location information of the other device;
55. The method of claim 54, wherein the determination of whether to transmit the updated set of handoff entries is further based on the location information. Receiving location information of the other device;
Determining the movement of the other device based on the position information;
55. The method of claim 54, wherein the determination of whether to transmit the updated set of handoff entries is further based on the movement of the other device. Receiving location information of the other device;
Determining the movement of the other device based on the position information;
56. The method of claim 54, further comprising: determining how many updated handoff entries to send based on the movement of the other device.   55. The method of claim 54, wherein the device comprises a terrestrial network.   55. The method of claim 54, wherein the updated set of handoff entries is transmitted to a user terminal. A device for communication,
With memory
A processor coupled to the memory;
The processor and the memory are
Identifying an effective time associated with a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of another device;
Determining whether to transmit an updated set of handoff entries based on the determined validity time.
Transmitting the updated set of handoff entries if the determination is to transmit the updated set of handoff entries.   71. The apparatus of claim 70, wherein the set of satellites is for idle mode operation of the other apparatus.   71. The apparatus of claim 70, wherein the set of handoff entries further specifies the time at which the other apparatus in idle mode is to be handed off to each satellite of the set of satellites.   71. The apparatus of claim 70, wherein the expiration time indicates a length of time that the set of entries for handoff is valid. The identification of the effective time is
71. The apparatus of claim 70, comprising receiving the indication of the expiration time. The identification of the effective time is
Receiving an indication of a time associated with a particular entry of the set of handoff entries;
71. The apparatus of claim 70, comprising determining the expiration time based on the received indication. The identification of the effective time is
71. The apparatus of claim 70, comprising determining a time associated with a last valid entry in the set of handoff entries. The processor and the memory are further configured to receive position information of the other device;
The processor and the memory are further configured to generate the updated set of handoff entries based on the location information;
71. The apparatus of claim 70, wherein the updated set of handoff entries is sent to the other device. The processor and the memory are further configured to receive position information of the other device;
71. The apparatus of claim 70, wherein the determination of whether to transmit the updated set of handoff entries is further based on the location information. The processor and the memory are further configured to receive position information of the other device;
The processor and the memory are further configured to determine movement of the other device based on the position information;
71. The apparatus of claim 70, wherein the determination of whether to transmit the updated set of handoff entries is further based on the movement of the other apparatus. The processor and the memory are further
Receiving location information of the other device;
Determine the movement of the other device based on the position information;
71. The apparatus of claim 70 configured to determine how many updated handoff entries to send based on the movement of the other apparatus. A device for communication,
Means for identifying an effective time associated with a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of another device;
Means for determining whether to transmit an updated set of handoff entries based on the determined valid time;
Means for transmitting the updated set of handoff entries if the determination is to transmit the updated set of handoff entries. Means for receiving location information of the other device;
Means for generating the updated set of handoff entries based on the location information;
82. The apparatus of claim 81, wherein the updated set of handoff entries is sent to the other device. Further comprising means for receiving position information of the other device;
82. The apparatus of claim 81, wherein the determination of whether to transmit the updated set of handoff entries is further based on the location information. Means for receiving location information of the other device;
And means for determining the movement of the other device based on the position information;
82. The apparatus of claim 81, wherein the determination of whether to transmit the updated set of handoff entries is further based on the movement of the other apparatus. Means for receiving location information of the other device;
Means for determining movement of the other device based on the position information;
82. The apparatus of claim 81, further comprising: means for determining how many updated handoff entries to send based on the movement of the other apparatus. Non-transitory computer readable medium storing computer executable code for a device, said code comprising
Identifying an effective time associated with a set of handoff entries, wherein the set of handoff entries identifies a set of satellites for handoff of another device;
Determining whether to transmit an updated set of handoff entries based on the determined validity time.
A non-transitory computer readable medium, comprising code for: transmitting the updated set of handoff entries if the determination is to transmit the updated set of handoff entries.