Apparatus, method and computer program

Abstract

The present disclosure relates to an apparatus comprising means for suspending (700) a network connection via a first base station on a first vehicle; determining (702) that a device context stored on a first base station on the first vehicle is expected to be available for a second base station on a second vehicle; and attempting (704) to resume the network connection via the second base station on the second vehicle.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present disclosure relates to apparatus, methods and computer programs for attempting to restore a network connection via a base station on a vehicle. Background Art

[0003] A communication system may be viewed as a facility that enables communication sessions between two or more entities, such as communication devices, base stations, and / or other nodes, by providing carrier waves between the various entities involved in the communication path.

[0004] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards such as those provided by 3GPP, satellite-based communication systems, and different wireless local networks, such as wireless local area networks (WLANs). Wireless systems can typically be divided into cells and are therefore often referred to as cellular systems.

[0005] Communication systems and associated equipment typically operate in accordance with a given standard or specification that specifies what the various entities associated with the system are allowed to do and how it should be achieved. Communication protocols and / or parameters that should be used for the connection are also typically defined. An example of a standard is the so-called 5G standard. Summary of the invention

[0006] According to an aspect, a device is provided that includes components for: suspending a network connection via a first base station on a first vehicle; determining that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; and attempting to resume the network connection via the second base station on the second vehicle.

[0007] The second base station on the second vehicle may or may not be connected to the network.When attempting to restore network connectivity via the second base station on the second vehicle, different scenarios may be envisioned.

[0008] In the scenario, a second base station may be connected to the network and may not have previously received and stored the device context from the first base station. The second base station may now receive and store the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0009] In another scenario, the second base station may be connected to the network and may have previously received and stored the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0010] In another scenario, the second base station may not be connected to the network, and may have previously been connected to the network. The second base station may have previously received and stored the device context. Therefore, the device context may be used for the second base station. Restoring the network connection via the second base station may be successful.

[0011] In another scenario, the second base station may not be connected to the network, and may have been previously connected to the network or may not have been previously connected to the network. The second base station may not have previously received and stored the device context. Therefore, the device context may not be available to the second base station, and restoring the network connection via the second base station may not be successful.

[0012] The apparatus may include means for receiving a network connection release message from a first base station on a first vehicle; and wherein attempting to restore the network connection via a second base station on a second vehicle may include sending a network connection restoration message to the second base station on the second vehicle.

[0013] The network connection release message may include an identifier associated with the device context; and wherein the network connection restoration message may include the identifier associated with the device context.

[0014] The apparatus may include means for receiving a network connection recovery complete message from a second base station on the second vehicle.

[0015] The apparatus may include means for detecting a failure to receive a network connection recovery complete message from a second base station on a second vehicle; and storing an identifier associated with the device context on the apparatus.

[0016] The apparatus may include means for subsequently resending the network connection restoration message including the identifier associated with the apparatus context to a second base station on the second vehicle.

[0017] The identifier may be stored together with at least one of: a time parameter indicating how long the identifier is to be stored on the device before it is deleted from the device; a maximum number of attempts parameter indicating the maximum number of times the device is to subsequently resend a network connection recovery message including the identifier to a second base station on a second vehicle before the identifier is deleted from the device; or a maximum number of identifiers parameter indicating the maximum number of identifiers to be stored by the device.

[0018] The apparatus may include means for sending a network connection setup message to a second base station on a second vehicle that does not include an identifier associated with the apparatus context.

[0019] The apparatus may include means for detecting a failure to receive a network connection setup complete message from a second base station on the second vehicle when the second base station on the second vehicle is not connected to the network.

[0020] The device may include components for: detecting a failure to receive a network connection setup completion message from a second base station on a second vehicle; determining that a device context stored on a first base station on a first vehicle is expected to be available to a third base station on a third vehicle; and sending a network connection recovery message including an identifier associated with the device context to the third base station on the third vehicle.

[0021] The device may include components for: detecting a failure to receive a network connection setup completion message from a second base station on a second vehicle; determining that a third base station on a third vehicle is expected to connect to a network; and sending a network connection setup message to a third base station on the third vehicle that does not include an identifier associated with a device context.

[0022] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include determining that a device context transfer time has expired since a connection with the network was suspended.

[0023] The device context transfer time may be received by the device from the first base station on the first satellite or may be calculated by the device.

[0024] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving an indication of the second base station on the second vehicle or an indication of a cell served by the second base station on the second vehicle from the first base station on the first vehicle.

[0025] The indication may indicate that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle.

[0026] The network connection release message may include at least one of: a device context transfer time; an indication of a second base station on the second carrier; or an indication of a cell served by the second base station on the second carrier.

[0027] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving a paging message from the second base station on the second vehicle.

[0028] The paging message may include at least one of: an indication that the device context is available for the second base station on the second vehicle; or an indication that the second base station on the second vehicle expects the device to resume network connectivity via the second base station on the second vehicle.

[0029] The device may include components for: determining that the device is moving out of the coverage of a first base station on a first vehicle, or vice versa; and sending an indication to the first base station on the first vehicle or the second base station on the second vehicle that the device is moving out of the coverage of the first base station on the first vehicle, or vice versa.

[0030] The apparatus may include means for determining that the apparatus is moving within the coverage of a second base station on a second vehicle, or vice versa.

[0031] The apparatus may include means for determining that the apparatus has high priority data; attempting to set up a network connection via a second base station on a second vehicle without first attempting to restore a network connection via the second base station on the second vehicle.

[0032] The apparatus may be user equipment.

[0033] The first vehicle, the second vehicle and / or the third vehicle may be a satellite, a drone or a car.

[0034] The first vehicle, the second vehicle, and / or the third vehicle may have an intermittent connection to the network.

[0035] According to one aspect, a device is provided, comprising at least one processor and at least one memory, the at least one memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, with the at least one processor, cause the device to at least: suspend a network connection via a first base station on a first vehicle; determine that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; and attempt to resume the network connection via the second base station on the second vehicle.

[0036] The second base station on the second vehicle may or may not be connected to the network.When attempting to restore network connectivity via the second base station on the second vehicle, different scenarios may be envisioned.

[0037] In the scenario, a second base station may be connected to the network and may not have previously received and stored the device context from the first base station. The second base station may now receive and store the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0038] In another scenario, the second base station may be connected to the network and may have previously received and stored the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0039] In another scenario, the second base station may not be connected to the network, and may have previously been connected to the network. The second base station may have previously received and stored the device context. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0040] In another scenario, the second base station may not be connected to the network, and may have been previously connected to the network or may not have been previously connected to the network. The second base station may not have previously received and stored the device context. Therefore, the device context may not be available to the second base station, and restoring the network connection via the second base station may not be successful.

[0041] At least one memory and computer code may be configured to, with at least one processor, cause the apparatus to at least: receive a network connection release message from a first base station on a first vehicle; and wherein attempting to restore a network connection via a second base station on a second vehicle may include: sending a network connection restoration message to the second base station on the second vehicle.

[0042] The network connection release message may include an identifier associated with the device context; and wherein the network connection restoration message may include the identifier associated with the device context.

[0043] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to at least: receive a network connection recovery complete message from a second base station on the second vehicle.

[0044] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to at least: detect a failure to receive a network connection recovery complete message from a second base station on a second vehicle; and store an identifier associated with the apparatus context on the apparatus.

[0045] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to at least: subsequently resend a network connection restoration message including an identifier associated with the apparatus context to a second base station on a second vehicle.

[0046] The identifier may be stored together with at least one of: a time parameter indicating how long the identifier is to be stored on the device before it is deleted from the device; a maximum number of attempts parameter indicating the maximum number of times the device is to subsequently resend a network connection recovery message including the identifier to a second base station on a second vehicle before the identifier is deleted from the device; or a maximum number of identifiers parameter indicating the maximum number of identifiers to be stored by the device.

[0047] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to at least: send a network connection setup message to a second base station on a second vehicle that does not include an identifier associated with the apparatus context.

[0048] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to at least: detect failure to receive a network connection setup completion message from a second base station on the second vehicle when the second base station on the second vehicle is not connected to the network.

[0049] At least one memory and computer code can be configured to, together with at least one processor, cause the device to at least: detect a failure to receive a network connection setup completion message from a second base station on a second vehicle; determine that a device context stored on a first base station on a first vehicle is expected to be available to a third base station on a third vehicle; and send a network connection recovery message including an identifier associated with the device context to a third base station on the third vehicle.

[0050] At least one memory and computer code may be configured to, together with at least one processor, cause the device to at least: detect a failure to receive a network connection setup completion message from a second base station on a second vehicle; determine that a third base station on a third vehicle is expected to connect to a network; and send a network connection setup message to a third base station on the third vehicle that does not include an identifier associated with a device context.

[0051] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include determining that a device context transfer time has expired since a connection with the network was suspended.

[0052] The device context transfer time may be received by the device from the first base station on the first satellite or may be calculated by the device.

[0053] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving an indication of the second base station on the second vehicle or an indication of a cell served by the second base station on the second vehicle from the first base station on the first vehicle.

[0054] The indication may indicate that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle.

[0055] The network connection release message may include at least one of: a device context transfer time; an indication of a second base station on the second carrier; or an indication of a cell served by the second base station on the second carrier.

[0056] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving a paging message from the second base station on the second vehicle.

[0057] The paging message may include at least one of: an indication that the device context is available for the second base station on the second vehicle; or an indication that the second base station on the second vehicle expects the device to resume network connectivity via the second base station on the second vehicle.

[0058] At least one memory and computer code may be configured together with at least one processor to cause the apparatus to at least: determine that the apparatus is moving out of coverage of a first base station on a first vehicle, or vice versa; and send an indication to the first base station on the first vehicle or the second base station on the second vehicle that the apparatus is moving out of coverage of the first base station on the first vehicle, or vice versa.

[0059] The at least one memory and the computer code may be configured to, with the at least one processor, cause the apparatus to at least: determine that the apparatus is moving within the coverage of a second base station on a second vehicle, or vice versa.

[0060] At least one memory and computer code may be configured to, together with at least one processor, cause the apparatus to at least: determine that the apparatus has high priority data; attempt to set up a network connection via a second base station on a second vehicle without first attempting to restore the network connection via the second base station on the second vehicle.

[0061] The apparatus may be user equipment.

[0062] The first vehicle, the second vehicle and / or the third vehicle may be a satellite, a drone or a car.

[0063] The first vehicle, the second vehicle, and / or the third vehicle may have an intermittent connection to the network.

[0064] According to one aspect, a device is provided that includes circuits configured to: suspend a network connection via a first base station on a first vehicle; determine that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; and attempt to resume the network connection via the second base station on the second vehicle.

[0065] The second base station on the second vehicle may or may not be connected to the network.When attempting to restore network connectivity via the second base station on the second vehicle, different scenarios may be envisioned.

[0066] In the scenario, a second base station may be connected to the network and may not have previously received and stored the device context from the first base station. The second base station may now receive and store the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0067] In another scenario, the second base station may be connected to the network and may have previously received and stored the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0068] In another scenario, the second base station may not be connected to the network, and may have previously been connected to the network. The second base station may have previously received and stored the device context. Therefore, the device context may be used for the second base station. Restoring the network connection via the second base station may be successful.

[0069] In another scenario, the second base station may not be connected to the network, and may have been previously connected to the network or may not have been previously connected to the network. The second base station may not have previously received and stored the device context. Therefore, the device context may not be available to the second base station, and restoring the network connection via the second base station may not be successful.

[0070] The apparatus may include circuitry configured to receive network connection release information from a first base station on a first vehicle; and wherein attempting to restore network connection via a second base station on a second vehicle may include sending a network connection restoration message to the second base station on the second vehicle.

[0071] The network connection release message may include an identifier associated with the device context; and wherein the network connection restoration message may include the identifier associated with the device context.

[0072] The apparatus may include circuitry configured to receive a network connection recovery complete message from a second base station on a second vehicle.

[0073] The apparatus may include circuitry configured to: detect a failure to receive a network connection recovery complete message from a second base station on a second vehicle; and store an identifier associated with the device context on the apparatus.

[0074] The apparatus may include circuitry configured to subsequently resend the network connection restoration message including the identifier associated with the apparatus context to a second base station on the second vehicle.

[0075] The identifier may be stored together with at least one of: a time parameter indicating how long the identifier is to be stored on the device before it is deleted from the device; a maximum number of attempts parameter indicating the maximum number of times the device is to subsequently resend a network connection recovery message including the identifier to a second base station on a second vehicle before the identifier is deleted from the device; or a maximum number of identifiers parameter indicating the maximum number of identifiers to be stored by the device.

[0076] The apparatus may include circuitry configured to send a network connection setup message to a second base station on a second vehicle that does not include an identifier associated with the apparatus context.

[0077] The apparatus may include circuitry configured to, when the second base station on the second vehicle is not connected to the network, detect a failure to receive a network connection setup complete message from the second base station on the second vehicle.

[0078] The device may include circuits configured to: detect a failure to receive a network connection setup completion message from a second base station on a second vehicle; determine that a device context stored on a first base station on a first vehicle is expected to be available to a third base station on a third vehicle; and send a network connection recovery message including an identifier associated with the device context to a third base station on the third vehicle.

[0079] The device may include circuits configured to: detect a failure to receive a network connection setup completion message from a second base station on a second vehicle; determine that a third base station on a third vehicle is expected to connect to a network; and send a network connection setup message to a third base station on the third vehicle that does not include an identifier associated with a device context.

[0080] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include determining that a device context transfer time has expired since a connection with the network was suspended.

[0081] The device context transfer time may be received by the device from the first base station on the first satellite or may be calculated by the device.

[0082] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving an indication of the second base station on the second vehicle or an indication of a cell served by the second base station on the second vehicle from the first base station on the first vehicle.

[0083] The indication may indicate that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle.

[0084] The network connection release message may include at least one of: a device context transfer time; an indication of a second base station on the second carrier; or an indication of a cell served by the second base station on the second carrier.

[0085] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving a paging message from the second base station on the second vehicle.

[0086] The paging message may include at least one of: an indication that the device context is available for the second base station on the second vehicle; or an indication that the second base station on the second vehicle expects the device to resume network connectivity via the second base station on the second vehicle.

[0087] The device may include circuits for: determining that the device is moving out of the coverage of a first base station on a first vehicle, or vice versa; and sending an indication to the first base station on the first vehicle or the second base station on the second vehicle that the device is moving out of the coverage of the first base station on the first vehicle, or vice versa.

[0088] The apparatus may include circuitry for determining that the apparatus is moving within a coverage area of ​​a second base station on a second vehicle, or vice versa.

[0089] The apparatus may include circuitry for determining that the apparatus has high priority data; attempting to set up a network connection via a second base station on a second vehicle without first attempting to restore a network connection via the second base station on the second vehicle.

[0090] The apparatus may be user equipment.

[0091] The first vehicle, the second vehicle and / or the third vehicle may be a satellite, a drone or a car.

[0092] The first vehicle, the second vehicle, and / or the third vehicle may have an intermittent connection to the network.

[0093] According to one aspect, a method is provided, comprising: suspending a network connection via a first base station on a first vehicle; determining that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; and attempting to resume the network connection via the second base station on the second vehicle.

[0094] The method may be performed by a device.

[0095] The second base station on the second vehicle may or may not be connected to the network.When attempting to restore network connectivity via the second base station on the second vehicle, different scenarios may be envisioned.

[0096] In the scenario, a second base station may be connected to the network and may not have previously received and stored the device context from the first base station. The second base station may now receive and store the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0097] In another scenario, the second base station may be connected to the network and may have previously received and stored the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0098] In another scenario, the second base station may not be connected to the network, and may have previously been connected to the network. The second base station may have previously received and stored the device context. Therefore, the device context may be used for the second base station. Restoring the network connection via the second base station may be successful.

[0099] In another scenario, the second base station may not be connected to the network, and may have been previously connected to the network or may not have been previously connected to the network. The second base station may not have previously received and stored the device context. Therefore, the device context may not be available to the second base station, and restoring the network connection via the second base station may not be successful.

[0100] The method may include receiving a network connection release message from a first base station on a first vehicle; and wherein attempting to restore the network connection via a second base station on a second vehicle may include sending a network connection restoration message to the second base station on the second vehicle.

[0101] The network connection release message may include an identifier associated with the device context; and wherein the network connection restoration message may include the identifier associated with the device context.

[0102] The method may include receiving a network connection recovery completion message from a second base station on the second vehicle.

[0103] The method may include detecting a failure to receive a network connection recovery complete message from a second base station on a second vehicle; and storing an identifier associated with the device context on the device.

[0104] The method may include subsequently resending the network connection restoration message including the identifier associated with the device context to a second base station on the second vehicle.

[0105] The identifier may be stored together with at least one of: a time parameter indicating how long the identifier is to be stored on the device before it is deleted from the device; a maximum number of attempts parameter indicating the maximum number of times the device is to subsequently resend a network connection recovery message including the identifier to a second base station on a second vehicle before the identifier is deleted from the device; or a maximum number of identifiers parameter indicating the maximum number of identifiers to be stored by the device.

[0106] The method may include sending a network connection setup message to a second base station on a second vehicle that does not include an identifier associated with the device context.

[0107] The method may include detecting a failure to receive a network connection setup complete message from a second base station on the second vehicle when the second base station on the second vehicle is not connected to the network.

[0108] The method may include: detecting a failure to receive a network connection setup completion message from a second base station on a second vehicle; determining that a device context stored on a first base station on a first vehicle is expected to be available to a third base station on a third vehicle; and sending a network connection recovery message including an identifier associated with the device context to the third base station on the third vehicle.

[0109] The method may include: detecting a failure to receive a network connection setup completion message from a second base station on a second vehicle; determining that a third base station on a third vehicle is expected to connect to a network; and sending a network connection setup message to the third base station on the third vehicle that does not include an identifier associated with a device context.

[0110] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include determining that a device context transfer time has expired since a connection with the network was suspended.

[0111] The device context transfer time may be received by the device from the first base station on the first satellite or may be calculated by the device.

[0112] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving an indication of the second base station on the second vehicle or an indication of a cell served by the second base station on the second vehicle from the first base station on the first vehicle.

[0113] The indication may indicate that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle.

[0114] The network connection release message may include at least one of: a device context transfer time; an indication of a second base station on the second carrier; or an indication of a cell served by the second base station on the second carrier.

[0115] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving a paging message from the second base station on the second vehicle.

[0116] The paging message may include at least one of: an indication that the device context is available for the second base station on the second vehicle; or an indication that the second base station on the second vehicle expects the device to resume network connectivity via the second base station on the second vehicle.

[0117] The method may include: determining that the device is moving out of the coverage of a first base station on a first vehicle, or vice versa; and sending an indication to the first base station on the first vehicle or the second base station on the second vehicle that the device is moving out of the coverage of the first base station on the first vehicle, or vice versa.

[0118] The method may include determining that the apparatus is moving within the coverage area of ​​a second base station on a second vehicle, or vice versa.

[0119] The method may include determining that the device has high priority data; attempting to set up a network connection via a second base station on a second vehicle without first attempting to restore a network connection via the second base station on the second vehicle.

[0120] The apparatus may be user equipment.

[0121] The first vehicle, the second vehicle and / or the third vehicle may be a satellite, a drone or a car.

[0122] The first vehicle, the second vehicle, and / or the third vehicle may have an intermittent connection to the network.

[0123] According to one aspect, a computer program is provided, comprising computer executable code, which, when executed on at least one processor, is configured to: suspend a network connection via a first base station on a first vehicle; determine that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; and attempt to restore the network connection via the second base station on the second vehicle.

[0124] The at least one processor may be part of the apparatus.

[0125] The second base station on the second vehicle may or may not be connected to the network.When attempting to restore network connectivity via the second base station on the second vehicle, different scenarios may be envisioned.

[0126] In the scenario, a second base station may be connected to the network and may not have previously received and stored the device context from the first base station. The second base station may now receive and store the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0127] In another scenario, the second base station may be connected to the network and may have previously received and stored the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0128] In another scenario, the second base station may not be connected to the network, and may have previously been connected to the network. The second base station may have previously received and stored the device context. Therefore, the device context may be used for the second base station. Restoring the network connection via the second base station may be successful.

[0129] In another scenario, the second base station may not be connected to the network, and may have been previously connected to the network or may not have been previously connected to the network. The second base station may not have previously received and stored the device context. Therefore, the device context may not be available to the second base station, and restoring the network connection via the second base station may not be successful.

[0130] The computer program may include computer executable code, which, when executed on at least one processor, is configured to: receive network connection release information from a first base station on a first vehicle; and wherein attempting to restore the network connection via a second base station on a second vehicle may include: sending a network connection recovery message to the second base station on the second vehicle.

[0131] The network connection release message may include an identifier associated with the device context; and wherein the network connection restoration message may include the identifier associated with the device context.

[0132] The computer program may include computer executable code that, when executed on at least one processor, is configured to: receive a network connection recovery completion message from a second base station on a second vehicle.

[0133] The computer program may include computer executable code, which, when executed on at least one processor, is configured to: detect a failure to receive a network connection recovery completion message from a second base station on a second vehicle; and store an identifier associated with the device context on the device.

[0134] The computer program may include computer executable code that, when executed on at least one processor, is configured to subsequently resend a network connection restoration message including an identifier associated with the device context to a second base station on the second vehicle.

[0135] The identifier may be stored together with at least one of: a time parameter indicating how long the identifier is to be stored on the device before it is deleted from the device; a maximum number of attempts parameter indicating the maximum number of times the device is to subsequently resend a network connection recovery message including the identifier to a second base station on a second vehicle before the identifier is deleted from the device; or a maximum number of identifiers parameter indicating the maximum number of identifiers to be stored by the device.

[0136] The computer program may include computer executable code that, when executed on at least one processor, is configured to: send a network connection setup message to a second base station on a second vehicle that does not include an identifier associated with a device context.

[0137] The computer program may include computer executable code, which, when executed on at least one processor, is configured to: detect a failure to receive a network connection setup completion message from a second base station on the second vehicle when the second base station on the second vehicle is not connected to the network.

[0138] The computer program may include computer executable code, which, when executed on at least one processor, is configured to: detect a failure to receive a network connection setup completion message from a second base station on a second vehicle; determine that a device context stored on a first base station on a first vehicle is expected to be available to a third base station on a third vehicle; and send a network connection recovery message including an identifier associated with the device context to a third base station on the third vehicle.

[0139] The computer program may include computer executable code, which, when executed on at least one processor, is configured to: detect a failure to receive a network connection setup completion message from a second base station on a second vehicle; determine that a third base station on a third vehicle is expected to connect to a network; and send a network connection setup message to a third base station on the third vehicle that does not include an identifier associated with a device context.

[0140] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include determining that a device context transfer time has expired since a connection with the network was suspended.

[0141] The device context transfer time may be received by the device from the first base station on the first satellite or may be calculated by the device.

[0142] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving an indication of the second base station on the second vehicle or an indication of a cell served by the second base station on the second vehicle from the first base station on the first vehicle.

[0143] The indication may indicate that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle.

[0144] The network connection release message may include at least one of: a device context transfer time; an indication of a second base station on the second carrier; or an indication of a cell served by the second base station on the second carrier.

[0145] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving a paging message from the second base station on the second vehicle.

[0146] The paging message may include at least one of: an indication that the device context is available for the second base station on the second vehicle; or an indication that the second base station on the second vehicle expects the device to resume network connectivity via the second base station on the second vehicle.

[0147] The computer program may include computer executable code, which, when running on at least one processor, is configured to: determine that the device is moving out of the coverage of the first base station on the first vehicle, or vice versa; and send an indication to the first base station on the first vehicle or the second base station on the second vehicle that the device is moving out of the coverage of the first base station on the first vehicle, or vice versa.

[0148] The computer program may include computer executable code that, when executed on at least one processor, is configured to determine that the apparatus is moving within the coverage of a second base station on a second vehicle, or vice versa.

[0149] The computer program may include computer executable code, which, when executed on at least one processor, is configured to: determine that the device has high priority data; attempt to set up a network connection via a second base station on a second vehicle without first attempting to restore the network connection via the second base station on the second vehicle.

[0150] The apparatus may be user equipment.

[0151] The first vehicle, the second vehicle and / or the third vehicle may be a satellite, a drone or a car.

[0152] The first vehicle, the second vehicle, and / or the third vehicle may have an intermittent connection to the network.

[0153] According to one aspect, a computer-readable medium is provided, the computer-readable medium including program instructions stored thereon for executing at least one of the above methods.

[0154] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions stored thereon for executing at least one of the above methods.

[0155] According to one aspect, a non-volatile tangible memory medium is provided, the non-volatile tangible memory medium comprising program instructions stored thereon for performing at least one of the above methods.

[0156] In the above, a number of different aspects have been described. It will be appreciated that further aspects may be provided by combining any two or more of the above aspects.

[0157] Various other aspects are also described in the following detailed description and in the appended claims.

[0158] List of abbreviations

[0159] AF: Application Function

[0160] AMF: Access and Mobility Management Function

[0161] API: Application Programming Interface

[0162] AS: Access layer

[0163] BS: Base Station

[0164] CU: Centralized Unit

[0165] CP: Control Plane

[0166] DL: Downlink

[0167] DU: Distributed Unit

[0168] EPS: Evolved Packet System

[0169] eMTC: enhanced machine type communication

[0170] eNB: eNodeB or eNode B or E-UTRAN Node B

[0171] gNB: gNode B

[0172] GSM: Global System for Mobile Communications

[0173] GW: Gateway

[0174] HSS: Home Subscriber Server

[0175] ID: Identifier

[0176] IoT: Internet of Things

[0177] LTE: Long Term Evolution

[0178] MAC: Medium Access Control

[0179] MS: Mobile Station

[0180] MTC: Machine Type Communication

[0181] NAS: Non-Access Stratum

[0182] NEF: Network Exposure Function

[0183] NF: Network Function

[0184] NR: New Radio

[0185] NRF: Network Repository Function

[0186] NTN: Non-Terrestrial Network

[0187] PDU: Packet Data Unit

[0188] RAM: Random Access Memory (R)AN: (Radio) Access Network

[0189] ROM: Read Only Memory

[0190] RRC: Radio Resource Control

[0191] S&F: Store and Forward

[0192] SMF: Session Management Function

[0193] TAU: Tracking Area Update

[0194] TN: Terrestrial Network

[0195] TR: Technical Report

[0196] TS: Technical Specifications

[0197] UE: User Equipment

[0198] UMTS: Universal Mobile Telecommunications System

[0199] UP: User Plane

[0200] WI: Work Item

[0201] 3GPP: Third Generation Partnership Project

[0202] 5G: Fifth Generation

[0203] 5GC: 5G Core Network

[0204] 5GS: 5G System BRIEF DESCRIPTION OF THE DRAWINGS

[0205] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0206] Figure 1 A schematic representation of a 5G system is shown;

[0207] Figure 2 A schematic representation of the control arrangement is shown;

[0208] Figure 3 A schematic representation of a user equipment is shown;

[0209] Figure 4 According to TS 36.330 ( Figure 7 .3a.3-3: Signalling diagram of the Radio Resource Control Connection Restoration Procedure in an Evolved Packet System (RRC Connection Restoration Procedure in Different eNBs in EPS);

[0210] Figure 5 A deployment is shown in which a first eNode B on a first satellite is connected to a network, a second eNode B on a second satellite is not connected to the network, and a third eNode B on a third satellite is connected to the network;

[0211] Figure 6 is a flow chart of a method for attempting to restore a network connection via a base station on a vehicle;

[0212] Figure 7 A block diagram showing a method for attempting to restore network connectivity via a base station on a vehicle; and

[0213] Figure 8 shows that storage, when executed by a processor, allows the processor to execute Figure 7 A schematic representation of a non-volatile memory medium of instructions for one or more of the steps of a method. DETAILED DESCRIPTION

[0214] In the following, certain embodiments are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a mobile communication device. Figure 1 , Figure 2 and Figure 3Certain general principles of wireless communication systems, their access systems and mobile communication devices are briefly explained to help understanding the technology based on the described examples.

[0215] Figure 1 A schematic representation of a 5G system (5GS) is shown. The 5GS may include a user equipment (UE), a (radio) access network ((R)AN), a 5G core network (5GC), one or more application functions (AFs), and one or more data networks (DNs).

[0216] The 5G(R)AN may include a terrestrial network (TN) portion, in which one or more gNBs are located on one or more masts or towers on the ground. The 5G(R)AN may include a non-terrestrial network (NTN) portion, in which one or more gNBs are located on one or more satellites or on one or more masts or towers on the ground.

[0217] One or more gNBs may include one or more gNB distributed unit functions connected to one or more gNB centralized unit functions.

[0218] 5GC may include access and mobility management function (AMF), session management function (SMF), authentication server function (AUSF), user data management (UDM), user plane function (UPF) and / or network exposure function (NEF). 5GC may include the gateway (GW) of the NTN part of 5G(R)AN.

[0219] Figure 2 shows the control method for Figure 1 An example of a control device 200 for the functions of (R)AN or 5GC shown above. The control device may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213 and an input / output interface 214. At least one processor 212, 213 may be coupled to RAM 211a and ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow one or more steps to be executed to perform one or more aspects of the aspects of this document. The software code 215 may be stored in ROM 211b. The control device 200 may be interconnected with another control device 200 that controls another function of a 5G (R)AN or 5GC. In some embodiments, each function of the (R)AN or 5GC includes a control device 200. In an alternative embodiment, two or more functions of the (R)AN or 5GC may share a control device.

[0220] Figure 3 An example of a user device 300 is shown, such as Figure 1 UE 300 is a user equipment (UE) shown above. UE 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include user equipment, mobile stations (MS) or mobile devices, such as mobile phones or so-called "smart phones", computers provided with wireless interface cards or other wireless interface facilities (such as USB dongles), personal data assistants (PDAs) or tablets provided with wireless communication capabilities, machine type communication (MTC) devices, cellular Internet of Things (CIoT) UEs, or any combination of these or the like. For example, UE 300 can provide communications for carrying data for communication. The communication can be one or more of voice, electronic mail (email), text messaging, multimedia, data, machine data, etc.

[0221] The UE 300 may receive signals over the air or radio interface 307 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 3 In the mobile device, the transceiver arrangement is schematically designated by block 306. The transceiver arrangement 306 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0222] The UE 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for use in the software and hardware assisted execution of the tasks it is designed to perform, including control of access and communication with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow one or more of the aspects of this document to be performed. The software code 308 may be stored in the ROM 302a.

[0223] The processor, memory and other related control means may be provided on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface such as a keyboard 305, a touch sensitive screen or pad, a combination thereof or the like. One or more of a display, a speaker and a microphone may optionally be provided depending on the type of device.

[0224] One or more aspects of the present disclosure relate to NTN. NTN has been defined in Release 17 for NR and Narrowband Internet of Things (NB-IoT) and / or Enhanced Machine Type Communication (eMTC). As part of the preparations for Release 18, companies submitted proposals for work item descriptions at RAN#94e in December 2021.

[0225] In RP-212940, satellite companies submitted a joint proposal that includes a new scenario: store and forward operation for IoT NTN. The content of RP-212940 (Section 4.1.4 Support for store and forward operation) is as follows.

[0226] “Store and Forward (S&F) is a new feature that will allow satellite to provide services to IoT NTN devices in periods / areas where the satellite is not connected to a gateway on the ground. An eNB on-board architecture is assumed. The service link and feeder link are assumed not to operate simultaneously. The information is stored on-board until there is a line of sight with the GW. The following candidate set of enhancement targets are listed:

[0227] Support decoupled signaling procedures "UE <-> satellite with RAN node" and "satellite with RAN node <-> terrestrial CN" for end-to-end functionality. [RAN2,RAN3]

[0228] Dynamic attachment between S-GW and eNB [RAN3]

[0229] The store and forward operation builds on the concept of discontinuous coverage scenarios from Release 17, where the UE only occasionally and temporarily has coverage from the satellite. The discontinuous coverage scenarios can also be extended by defining that the satellite is not always connected to the core network (i.e., the GW).

[0230] As an example, the following description applies to EPS, but it should be understood that it can be applicable to other systems, such as 5GS or subsequent generation systems. As an example, the present description involves eNB, but it should be understood that it can be applicable to other BSs, such as gNB or subsequent generation BSs.

[0231] Store and forward operation can enable low-cost deployment consisting of only a few BSs on the satellite and a few BSs on the ground. This means that the connectivity cost per UE may be reduced, but at the expense of supporting only delay-tolerant data.

[0232] The challenge in the store and forward operation scenario is how the UE can establish an RRC connection (ie, a secure connection) with the EPC when the link between the UE and the eNB on the satellite and the link between the eNB on the satellite and the EPC are not available at the same time.

[0233] Assuming that an RRC connection has been established by the UE with the EPC, it may be beneficial to retain the UE context at the UE and the eNB on the satellite. The UE context may include access stratum (AS) and radio resource control (RRC) configuration.

[0234] The UE may receive an RRC connection release message from the eNB on the satellite. The RRC connection release message may include an indication (eg, a cause) indicating that the RRC connection is suspended. The RRC connection release message may include a resume ID.

[0235] The Recovery ID may be associated with the UE context. The Recovery ID may be stored by the eNB on the satellite together with the UE context. The Recovery ID may include a UE ID portion and / or an eNB ID portion. The Recovery ID may include an Inactive Radio Network Temporary Identifier in the 5GS.

[0236] The UE may subsequently decide to resume the RRC connection. For example, the UE may wish to resume the RRC connection when the UE has UE-originated traffic to send to the EPC. The UE may wish to resume the RRC connection after a radio link failure. The UE may wish to resume the RRC connection after a handover failure. The UE may wish to resume the RRC connection after receiving a paging message from the EPC.

[0237] When the UE wishes to resume the RRC connection, the UE may send an RRC connection resume message to another eNB on another satellite. The RRC connection resume message may include a resume ID. The resume ID may allow another eNB on another satellite to obtain the UE context from the eNB on the satellite via the EPC and store the UE context on another eNB on another satellite.

[0238] Figure 4 According to TS 36.330 ( Figure 7 .3a.3-3: Signaling diagram of the Radio Resource Control Connection Restoration Procedure in an Evolved Packet System of TS 36.330 (Chapter 7.3a.3-3 User Plane CIoT EPS / 5GS Optimization) is as follows.

[0239] "1. Same as step 1 of intra-(ng-)eNB connection recovery.

[0240] 2. The new (ng-)eNB locates the old (ng-)eNB using the recovery ID (for EPS) or I-RNTI (for 5GS), and retrieves the UE context with the help of the X2-AP (for EPS) or Xn-AP (for 5GS) retrieval UE context procedure.

[0241] 3. The old (ng-)eNB responds with the UE context associated with the recovery ID (for EPS) or I-RNTI (for 5GS).

[0242] 4. Same as step 2 of intra-(ng-)eNB connection recovery.

[0243] 5. Same as step 3 of intra-(ng-)eNB connection recovery.

[0244] 6. Same as step 4 of intra-(ng-)eNB connection recovery.

[0245] 7. For EPS, the new eNB initiates the S1-AP path switching procedure to establish the S1 UE-associated signaling connection to the serving MME and requests the MME to restore the UE context. For 5GS, the new NG-eNB initiates the NG-AP path switching procedure to establish the NG UE-associated signaling connection to the serving AMF and requests the AMF to restore the UE context.

[0246] 8. For EPS, MME requests S-GW to activate S1-U bearer for UE and update downlink path. For 5GS, AMF requests SMF to resume PDU session, and SMF requests UPF to create tunnel information for UE and update downlink path.

[0247] 9.MME / AMF confirms step 7.

[0248] 10. For EPS, after the S1-AP path switching procedure, the new eNB triggers the release of the UE context at the old eNB by means of the X2-AP UE context release procedure. For 5GS, after the NG-AP path switching procedure, the new ng-eNB triggers the release of the UE context at the old ng-eNB by means of the Xn-AP UE context release procedure. "

[0249] like Figure 4 As shown in , it is expected that another eNB on another satellite (i.e., the "new eNB") can retrieve the UE context from the eNB on the satellite (i.e., the "old eNB") via the EPC. This can be challenging in a store and forward operation because the other eNB on the other satellite (i.e., the "new eNB") and the eNB on the satellite (i.e., the "old eNB") may not be connected to the EPC at the same time.

[0250] One or more aspects of the present disclosure may provide options on how to configure a UE to attempt to resume an RRC connection via another base station on another satellite (ie, a "new eNB"), particularly in store and forward operations.

[0251] TS 36.331 (Section 5.3.3.2 Initialization) defines the conditions for resuming the RRC connection, and the contents are as follows.

[0252] "The UE initiates this procedure when upper layers request establishment or resumption of an RRC connection while the UE is in RRC_IDLE, or when upper layers request resumption of an RRC connection while the UE is in RRC_INACTIVE or the RRC layer requests resumption of an RRC connection for reception of, for example, RNAU or RAN paging."

[0253] The UE may initiate the RRC connection procedure by sending an RRC connection restoration request message to another eNB on another satellite. The RRC connection restoration request message may include the following information.

[0254] RRCConnectionResumeRequest message

[0255]

[0256]

[0257] When sending an RRC Connection Resume message to another eNB on another satellite (ie, a "new eNB"), the UE may resume the RRC configuration. The UE may apply integrity protection and ciphering according to the existing security context.

[0258] In the scenario, another eNB on another satellite (i.e., the "new eNB") may respond to the RRC connection recovery message with another RRC connection recovery message. The UE may update security keys based on the content of the other RRC connection recovery message and the UE context. The UE may continue to recover the RRC connection via another eNB on another satellite (i.e., the "new eNB").

[0259] In another scenario, another eNB on another satellite (ie, the "new eNB") may respond to the RRC Connection Resume message with an RRC Connection Setup message. The UE may discard the UE context (including security keys).

[0260] In another scenario, another eNB on another satellite (i.e., a "new eNB") may respond to the RRC Connection Resume message with an RRC Connection Reject message. The UE may discard the UE context (including security keys). The UE may notify upper layers of the failure to resume the RRC connection via another eNB on another satellite.

[0261] In another scenario, another eNB on another satellite (ie, the "new eNB") may respond to the RRC Connection Resume message with an RRC Connection Release message. The UE may update the UE context (including security keys and C-RNTI). The UE may remain in the suspended RRC state.

[0262] One or more aspects of the present disclosure may configure how and / or when a UE is allowed to attempt to resume an RRC connection via another eNB on another satellite (ie, a “new eNB”) in a store and forward operation scenario.

[0263] In the scenario, it may be assumed that UE context may be available to another eNB on another satellite (ie, the "new eNB") before and / or while the UE is within coverage of the other eNB on another satellite (ie, the "new eNB").

[0264] Figure 5 A deployment is shown where a first eNode B on a first satellite SAT1 is connected to the EPC, a second eNode B on a second satellite SAT2 is not connected to the EPC, and a third eNode B on a third satellite SAT3 is connected to the EPC.

[0265] The UE may set up an RRC connection via a first eNode B on a first satellite SAT1. For example, the UE may send an RRC connection setup message to the first eNode B on the first satellite SAT1. The first eNode B on the first satellite SAT1 may store a recovery ID associated with the UE context together with the UE context.

[0266] The first eNode B on the first satellite SAT1 may instruct the UE to suspend the RRC connection. For example, the first eNode B on the first satellite SAT1 may send an RRC connection release message to the UE.

[0267] The RRC Connection Release message may include a resumption ID associated with the UE context.

[0268] The RRC connection release message may include a UE context transfer time that allows the first eNode B, EPC, or proxy on the first satellite SAT1 to transfer the UE context to the third eNode B on the third satellite SAT3.

[0269] The RRC connection release message may include an indication of a third eNode B on a third satellite SAT3 from the first satellite SAT1 (eg, a SAT ID) or an indication of a cell served by the third eNode B on the third satellite SAT3 (eg, a PCI).

[0270] The RRC Connection Release message may include an indication of attempting to resume the RRC connection via a third eNode B on a third satellite SAT3. The indication may include a cause set to "resume_store_forward".

[0271] The UE may store the resume ID associated with the UE context.The UE may suspend the RRC connection via the first eNode B on the first satellite SAT1.

[0272] The UE context may not be available to the second eNode B on the second satellite SAT2, but the UE context may be available to the third eNode B on the third satellite SAT3.

[0273] In implementation, the UE may not attempt to resume the RRC connection via the second eNode B on the second satellite SAT2. The EPC may not send data for the UE to the second eNode B on the second satellite SAT2. However, when the first eNode B on the first satellite SAT1 is not connected to the EPC and thus cannot obtain such information from the first eNode B on the first satellite SAT1, it may be difficult for the EPC to know that the UE context may not be available to the second eNode B on the second satellite SAT2.

[0274] In another implementation, the UE context may not be available for the second eNode B on the second satellite SAT2. The UE may attempt to resume the RRC connection via the second eNode B on the second satellite SAT2. The attempt to resume the RRC connection via the second eNode B on the second satellite SAT2 may fail. The UE may store a resumption ID associated with the UE context received in the RRC connection release message from the first eNode B on the first satellite SAT1. The UE may use the resumption ID to subsequently re-attempt to resume the RRC connection via the second eNode B on the second satellite SAT2, or to attempt to resume the RRC connection via a third eNode B on the third satellite SAT3.

[0275] The UE may store the resumption ID and the one or more parameters.

[0276] The UE may store the recovery ID associated with the UE context and a timer parameter indicating a time to use the recovery ID to re-attempt to recover the RRC connection via the second eNode B on the second satellite SAT2 or to attempt to recover the RRC connection via the third eNode B on the third satellite SAT3.

[0277] The UE may store the recovery ID associated with the UE context and a maximum number of attempts parameter indicating a maximum number of times the recovery ID may be used to retry recovering the RRC connection via the second eNode B on the second satellite SAT2 or to attempt recovering the RRC connection via the third eNode B on the third satellite SAT3.

[0278] The UE may store the recovery ID associated with the UE context and a maximum number of recovery IDs parameter indicating the maximum number of IDs to be stored by the UE.

[0279] In this way, the UE may control how long and how many recovery IDs the UE may store.

[0280] In another implementation, the UE context may be available to a third eNode B on a third satellite SAT3. The UE may attempt to restore the RRC connection via the third eNode B on the third satellite SAT3. For example, the UE may send an RRC connection restoration message to the third eNode B on the third satellite SAT3. The RRC connection restoration message may include a restoration ID associated with the UE context.

[0281] After receiving the RRC connection release message, the UE may attempt to resume the RRC connection via the third eNode B on the third satellite SAT3. As explained above, the RRC connection release message may include that a UE context transfer time allowing the first eNode B, EPC or proxy on the first satellite SAT1 to transfer the UE context to the third eNode B on the third satellite SAT3 has expired from the moment the RRC connection was suspended.

[0282] After receiving the RRC connection release message, the UE may attempt to resume the RRC connection via the third eNode B on the third satellite SAT3. As explained above, the RRC connection release message may include an indication of the third eNode B on the third satellite SAT3 from the first satellite SAT1 (e.g., SAT ID) or an indication of the cell served by the third eNode B on the third satellite SAT3 (e.g., PCI).

[0283] After receiving the paging message from the third eNode B on the third satellite SAT3, the UE may attempt to resume the RRC connection via the third eNode B on the third satellite SAT3. The paging message may be a dedicated or special paging message.

[0284] The paging message may include an indication that the UE may continue UL transmissions to the EPC via the third eNode B on the third satellite SAT3 or that the third eNode B on the third satellite SAT3 has feedback for a previous UL transmission to the EPC via the first eNode B on the first satellite SAT1.

[0285] This may cover the case where the UE sent data in a previous UL transmission via the first satellite SAT1 and the application in which the data was sent may expect feedback from the EPC or from an application at the other end to the UE. The third satellite SAT3 may carry this feedback from the EPC to the UE.

[0286] The third eNodeB on the third satellite SAT3 may carry application layer feedback for some application layer data, which the UE previously sent to the EPC via the first eNodeB on the first satellite SAT1. The first eNodeB on the first satellite SAT1 may have provided the data to the EPC. The EPC may have obtained the application feedback from an application layer receiver (e.g., a database or server). The application layer feedback may be delivered from the EPC to the third eNodeB on the third satellite SAT3, so that the third eNodeB on the third satellite SAT3 may provide the application layer feedback to the UE.

[0287] The paging message may include an indication that the UE context is available for a third eNode B on a third satellite SAT3.

[0288] The paging message may include an indication of attempting to restore the RRC connection via a third eNode B on a third satellite SAT3. The indication may include a flag bit (e.g., a restoration flag) set to "1" or "0" to indicate that each UE ID of the paging record attempts to restore the RRC connection via a third eNode B on a third satellite SAT3 or attempts to set up a new RRC connection via a third eNode B on a third satellite SAT3. The flag bit may be added to TS 36.331 as follows.

[0289] The paging message may include a recovery ID delivered to the third satellite SAT3 via the EPC or proxy, which the UE may then match with the recovery ID associated with the UE context stored on the UE.

[0290] "Paging::=SEQUENCE{

[0291] pagingRecordList PagingRecordList OPTIONAL,--Need ONsystemInfoModification ENUMERATED{true}OPTIONAL,--Need ON etws-IndicationENUMERATED{true}OPTIONAL,--Need ON nonCriticalExtension Paging-v890-IEsOPTIONAL

[0292] }

[0293] PagingRecordList::=SEQUENCE(SIZE(1..maxPageRec))OF PagingRecord

[0294] PagingRecord::=SEQUENCE{

[0295] ue-Identity PagingUE-Identity,

[0296] cn-Domain ENUMERATED{ps,cs},

[0297] ResumeFlag BOOLEAN ...

[0299] }

[0300] PagingUE-Identity::=CHOICE{

[0301] s-TMSI S-TMSI,

[0302] imsi IMSI,

[0303] ...,

[0304] ng-5G-S-TMSI-r15 NG-5G-S-TMSI-r15,

[0305] fullI-RNTI-r15 I-RNTI-r15

[0306] r

[0307] Alternatively, the UE context may not be available for a second eNode B on a second satellite SAT2, and the UE context may also not be available for a third eNode B on a third satellite SAT3.

[0308] In implementation, when the third eNodeB on the third satellite SAT3 is connected to the EPC, the UE may set up a new RRC connection via the third eNodeB on the third satellite SAT3. For example, the UE may send an RRC connection setup message to the third eNodeB on the third satellite SAT3. The RRC connection may be an RRC connection for non-access stratum-based recovery. The EPC (i.e., GW) may clean up the previous UE context stored by the third eNodeB on the third satellite SAT3.

[0309] In another implementation, when the third eNodeB on the third satellite SAT3 is not connected to the EPC, the UE may wait for the UE context to be available for the fourth eNodeB on the fourth satellite SAT4, and may attempt to restore the RRC connection via the fourth eNodeB on the fourth satellite SAT4. For example, the UE may send an RRC connection restoration message to the fourth eNodeB on the fourth satellite SAT4.

[0310] In another implementation, when the third eNodeB on the third satellite SAT3 is not connected to the EPC, the UE may wait for the fourth eNodeB on the fourth satellite SAT4 to connect to the EPC, and may set up a new RRC connection via the fourth eNodeB on the fourth satellite SAT4. The UE may send an RRC connection setup message to the fourth eNodeB on the fourth satellite SAT4.

[0311] In another implementation, when the third eNodeB on the third satellite SAT3 is not connected to the EPC, the UE may set up a new RRC connection via the third eNodeB on the third satellite SAT3. The UE may send an RRC connection setup message to the third eNodeB on the third satellite SAT3. The UE may wait for the third eNodeB on the third satellite SAT3 to connect to the EPC to complete the setup of the new RRC connection via the third eNodeB on the third satellite SAT3.

[0312] When the first eNodeB on the first satellite SAT1 instructs the UE to suspend the RRC connection, the first eNodeB on the first satellite SAT1 may provide a time (i.e., a delay) for completing the setup of a new RRC connection via the third eNodeB on the third satellite SAT3. The time (i.e., a delay) for completing the setup of the new RRC connection via the third eNodeB on the third satellite SAT3 may be provided in the RRC connection release message.

[0313] When the UE supports a control plane (CP) technical solution in which packets can be delivered using NAS security keys, the UE can set up an RRC connection for sending packets using NAS security keys via a third eNode on the third satellite SAT3. In this case, the EPC can ensure that it does not release the security keys provided to the (R)AN for the UP technical solution. In other words, the EPC can ensure the coexistence of UP and CP-based technical solutions for this scenario. If the third eNode on the third satellite SAT3 is not connected to the EPC, the third satellite SAT3 can buffer the packets to allow the EPC (i.e., GW) to subsequently confirm the security of the packets. The EPS can configure this "switching to the CP technical solution" with conditions. The conditions can be based on the priority of the packets and / or the number of packets.

[0314] When the UE moves out of the coverage area of ​​the first eNode B on the first SAT1, the UE may perform a Tracking Area Update (TAU) and may indicate its presence in a new area to the first eNode B on the first SAT1. The new area may be a tracking area, a coverage area of ​​a third eNodeB on a third satellite SAT3 indicated in the RRC release message, a coverage area of ​​a cell served by the third eNodeB on the third satellite SAT3 indicated in the RRC release message, or other.

[0315] After performing a TAU, the UE may wait for the UE context to be available in the new area. The UE may know that the context is available based on the paging message. For uplink-oriented data, the EPC may respond to the TAU with an "estimated time until the context is available in the new TAU" parameter, which will allow the UE to postpone the RRC connection recovery procedure accordingly.

[0316] When the UE has high priority data (eg, an emergency call or abnormal data), the UE may attempt to set up a new RRC connection via the third eNode B on the third satellite SAT3 as quickly as possible without attempting to resume the RRC connection via the third eNodeB on the third satellite SAT3.

[0317] One or more aspects of the present disclosure may enable a UE to use an RRC connection release (ie, suspension) procedure and an RRC connection resumption procedure, which significantly reduces the time to complete random access and initiate data transfer compared to a full RRC connection setup.

[0318] One or more aspects of the present disclosure may enable a UE to determine which eNode B to use when / on which satellite to perform an RRC connection release (i.e., suspension) procedure and an RRC connection recovery procedure (RRC is inactive in NR). This may help avoid failures and a complete RRC connection setup procedure.

[0319] Figure 6 is a flow chart of a method for attempting to restore network connectivity via an eNode B on a satellite.

[0320] Initially, the UE may set up an RRC connection via a first eNode B on a first satellite SAT1. For example, the UE may send an RRC connection setup message to the first eNode B on the first satellite SAT1. The first eNode B on the first satellite SAT1 may store a recovery ID associated with the UE context together with the UE context.

[0321] The first eNode B on the first satellite SAT1 may instruct the UE to release the RRC connection. For example, the first eNode B on the first satellite SAT1 may send an RRC connection release message to the UE.

[0322] The RRC Connection Release message may include a resumption ID associated with the UE context.

[0323] The RRC connection release message may include a UE context transfer time that allows the first eNode B, EPC, or proxy on the first satellite SAT1 to transfer the UE context to the third eNode B on the third satellite SAT3.

[0324] The RRC connection release message may include an indication of a third eNode B on a third satellite SAT3 from the first satellite SAT1 (eg, a SAT ID) or an indication of a cell served by the third eNode B on the third satellite SAT3 (eg, a PCI).

[0325] The RRC Connection Release message may include an indication of attempting to resume the RRC connection via a third eNode B on a third satellite SAT3. The indication may include a cause set to "resume_store_forward".

[0326] The UE may store the resume ID associated with the UE context.The UE may release (ie, suspend) the RRC connection via the first eNode B on the first satellite SAT1.

[0327] In step 600, the UE may determine that the UE has a resumption ID associated with a UE context stored on the UE.

[0328] In step 602, the UE may determine that a third eNode B on a third satellite SAT3 (i.e., a new satellite) is available. That is, the UE may determine that the UE is within the coverage of the third eNode B on the third satellite SAT3. The UE may determine whether the UE context is expected to be available for the third eNode B on the third satellite SAT3.

[0329] In step 604 (option A), the UE may determine whether the RRC release message includes a UE context transfer time and whether the UE context transfer time has expired.

[0330] If the RRC release message includes the UE context transfer time and the UE context transfer time has expired, the method proceeds to step 606 .

[0331] If the RRC release message does not include the UE context transfer time or if the RRC release message includes the UE context transfer time and the UE context transfer time has not expired, the method proceeds to step 608 .

[0332] In step 610 (option B), the UE may determine whether the RRC release message includes an indication of a third eNode B on a third satellite SAT3 from the first satellite SAT1 (eg, SAT ID) or an indication of a cell served by the third eNode B on the third satellite SAT3 (eg, PCI).

[0333] If the RRC release message includes an indication of a third eNode B on a third satellite SAT3 from the first satellite SAT1 (eg, a SAT ID) or an indication of a cell served by the third eNode B on the third satellite SAT3 (eg, a PCI), the method proceeds to step 606 .

[0334] If the RRC publication message does not include an indication of a third eNode B on a third satellite SAT3 from the first satellite SAT1 (eg, SAT ID) or an indication of a cell served by the third eNode B on the third satellite SAT3 (eg, PCI), the method proceeds to step 608 .

[0335] In step 612 (option C), the UE may determine whether the UE receives a paging message and the paging message includes an indication that the UE context is available for a third eNode B on a third satellite SAT3.

[0336] If the UE can determine that the UE received the paging message and the paging message includes an indication that the UE context is available for the third eNode B on the third satellite SAT3, the method proceeds to step 606.

[0337] If the UE can determine that the UE has not received the paging message or the paging message does not include an indication that the UE context is available for the third eNode B on the third satellite SAT3, the method proceeds to step 608.

[0338] In step 614 (option D), the UE may determine whether the UE receives a paging message from a third eNode B on a third satellite SAT3.

[0339] If the UE can determine that the UE receives the paging message from the third eNode B on the third satellite SAT3 , the method proceeds to step 606 .

[0340] If the UE can determine that the UE has not received the paging message from the third eNode B on the third satellite SAT3 , the method proceeds to step 608 .

[0341] In step 606, the UE may attempt to restore the RRC connection via the third eNode B on the third satellite SAT3. For example, the UE may send an RRC connection restoration message to the third eNode B on the third satellite SAT3. The RRC connection restoration message may include a restoration ID.

[0342] In step 616, the UE may determine whether the RRC connection has been restored via the third eNode B on the third satellite SAT3. For example, the UE may determine whether an RRC connection restoration complete message has been received from the third eNode B on the third satellite SAT3.

[0343] If the RRC connection has been restored via the third eNode B on the third satellite SAT3 , the method proceeds to 618 .

[0344] If the RRC connection has not been restored via the third eNode B on the third satellite SAT3 , the method proceeds to 620 .

[0345] In step 618, an RRC connection is established via a third eNode B on a third satellite SAT3.

[0346] In step 620 , the UE may store the recovery ID for later use (eg, attempting to recover the RRC connection via a third eNode B on a third satellite SAT3 ). The method proceeds to step 608 .

[0347] In step 608, the UE may attempt to set up a new RRC connection via a third eNode B on the third satellite SAT3. For example, the UE may send an RRC connection setup message to the third eNode B on the third satellite SAT3. The RRC connection setup message does not include a recovery ID.

[0348] Figure 7 A block diagram of a method for attempting to restore a network connection via a base station on a satellite is shown. The method may be performed by an apparatus (eg, user equipment).

[0349] In step 700 , the device may suspend a network connection via a first base station on a first vehicle.

[0350] In step 702, the device may determine that a device context stored on a first base station on a first vehicle is expected to be available to a second base station on a second vehicle.

[0351] In step 704, the device may attempt to restore network connection via a second base station on a second vehicle.

[0352] The second base station on the second vehicle may or may not be connected to the network.When attempting to restore network connectivity via the second base station on the second vehicle, different scenarios may be envisioned.

[0353] In the scenario, a second base station may be connected to the network and may not have previously received and stored the device context from the first base station. The second base station may now receive and store the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0354] In another scenario, the second base station may be connected to the network and may have previously received and stored the device context from the first base station. Therefore, the device context may be available to the second base station. Restoring the network connection via the second base station may be successful.

[0355] In another scenario, the second base station may not be connected to the network, and may have previously been connected to the network. The second base station may have previously received and stored the device context. Therefore, the device context may be used for the second base station. Restoring the network connection via the second base station may be successful.

[0356] In another scenario, the second base station may not be connected to the network, and may have been previously connected to the network or may not have been previously connected to the network. The second base station may not have previously received and stored the device context. Therefore, the device context may not be available to the second base station, and restoring the network connection via the second base station may not be successful.

[0357] The apparatus may receive network connection release information from a first base station on the first vehicle. Attempting to restore the network connection via a second base station on the second vehicle may include sending a network connection restoration message to the second base station on the second vehicle.

[0358] The network connection release message may include an identifier associated with the device context. The network connection restoration message may include an identifier associated with the device context.

[0359] The device may receive a network connection recovery completion message from a second base station on the second vehicle.

[0360] The device may detect a failure to receive a network connection recovery complete message from a second base station on a second vehicle, and store an identifier associated with the device context on the device.

[0361] The device may then resend a network connection restoration message including the identifier associated with the device context to a second base station on the second vehicle.

[0362] The identifier may be stored together with at least one of: a time parameter indicating how long the identifier is to be stored on the device before it is deleted from the device; a maximum number of attempts parameter indicating the maximum number of times the device is to subsequently resend a network connection recovery message including the identifier to a second base station on a second vehicle before the identifier is deleted from the device; or a maximum number of identifiers parameter indicating the maximum number of identifiers to be stored by the device.

[0363] The device may send a network connection setup message to a second base station on a second vehicle that does not include an identifier associated with the device context.

[0364] When the second base station on the second vehicle is not connected to the network, the apparatus may detect a failure to receive a network connection setup completion message from the second base station on the second vehicle.

[0365] The apparatus may include detecting a failure to receive a network connection setup complete message from a second base station on a second vehicle. The apparatus may determine that a device context stored on a first base station on a first vehicle is expected to be available to a third base station on a third vehicle. The apparatus may send a network connection resume message including an identifier associated with the device context to the third base station on the third vehicle.

[0366] The apparatus may include detecting a failure to receive a network connection setup complete message from a second base station on a second vehicle. The apparatus may determine that a third base station on a third vehicle is expected to connect to a network. The apparatus may send a network connection setup message that does not include an identifier associated with the apparatus context to the third base station on the third vehicle.

[0367] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include determining that a device context transfer time has expired since a connection with the network was suspended.

[0368] The device context transfer time may be received by the device from the first base station on the first satellite or may be calculated by the device.

[0369] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving an indication of the second base station on the second vehicle or an indication of a cell served by the second base station on the second vehicle from the first base station on the first vehicle.

[0370] The indication may indicate that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle.

[0371] The network connection release message may include at least one of: a device context transfer time; an indication of a second base station on the second carrier; or an indication of a cell served by the second base station on the second carrier.

[0372] Determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle may include receiving a paging message from the second base station on the second vehicle.

[0373] The paging message may include at least one of: an indication that the device context is available for the second base station on the second vehicle; or an indication that the second base station on the second vehicle expects the device to resume network connectivity via the second base station on the second vehicle.

[0374] The apparatus may determine that the apparatus is moving out of coverage of a first base station on a first vehicle, or vice versa. The apparatus may send an indication to the first base station on the first vehicle or the second base station on the second vehicle that the apparatus is moving out of coverage of the first base station on the first vehicle, or vice versa.

[0375] The device may determine that the device is moving within the coverage area of ​​a second base station on a second vehicle, or vice versa.

[0376] The device may determine that the device has high priority data; attempt to set up a network connection via a second base station on a second vehicle without first attempting to restore the network connection via the second base station on the second vehicle.

[0377] The first vehicle, the second vehicle and / or the third vehicle may be a satellite, a drone or a car.

[0378] The first vehicle, the second vehicle, and / or the third vehicle may have an intermittent connection to the network.

[0379] Figure 8 A schematic representation of a non-volatile memory medium storing instructions and / or parameters that, when executed by a processor, allow the processor to perform Figure 7 One or more of the steps of the method.

[0380] It should be noted that while example embodiments are described above, several variations and modifications may be made to the disclosed solutions without departing from the scope of the present invention.

[0381] It will be appreciated that although the concepts above have been discussed in the context of EPS (i.e., LTE), one or more of these concepts may be applied to other cellular systems, particularly 5GS or next generation systems.

[0382] It should be understood that although the above concepts have been discussed in the context of a BS on a satellite, one or more of these concepts may be applied to BSs on other vehicles (such as drones, cars, or others) that provide intermittent CN connectivity.

[0383] Therefore, the embodiments may vary within the scope of the appended claims. In general, some embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, although the embodiments are not limited thereto. Although various embodiments may be illustrated and described with block diagrams, flow charts, or using some other graphical representation, it is well known that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0384] The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. In addition, in this regard, it should be noted that, for example Figure 8 Any process in the software may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as, for example, DVDs and their data variants, CDs.

[0385] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a gate-level circuit, and a processor based on a multi-core processor architecture.

[0386] Alternatively or additionally, some embodiments may be implemented using a circuit. The circuit may be configured to perform one or more of the previously described functions and / or method steps. The circuit may be provided in a base station and / or a communication device.

[0387] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0388] (a) hardware circuit implementation only (e.g., implementation using only analog and / or digital circuits);

[0389] (b) a combination of hardware circuitry and software, such as:

[0390] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0391] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software and memory(s) that work together to enable an apparatus, such as a communication device or base station, to perform the various functions previously described; and

[0392] (c) Hardware circuits and or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) for operation, but where the software is not required for operation, the software may not be present.

[0393] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example, an integrated device.

[0394] The above description has provided a complete and informative description of some embodiments by way of exemplary and non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the above description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of these teachings will still fall within the scope as defined in the appended claims.

Claims

1. An apparatus comprising components for: suspending a network connection via a first base station on a first vehicle; determining that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; as well as An attempt is made to restore the network connection via the second base station on the second vehicle.

2. The device according to claim 1, comprising means for: receiving network connection release information from the first base station on the first vehicle; and Wherein attempting to restore the network connection via the second base station on the second vehicle comprises: Send a network connection recovery message to the second base station on the second vehicle.

3. The apparatus according to claim 2, wherein the network connection release message comprises: an identifier associated with the device context; as well as The network connection recovery message includes: the identifier associated with the device context.

4. The device according to claim 2 or claim 3, comprising means for: A network connection recovery completion message is received from the second base station on the second vehicle.

5. The device according to claim 2 or claim 3, comprising means for: detecting a failure to receive a network connection recovery complete message from the second base station on the second vehicle; and The identifier associated with the device context is stored on the device.

6. The device according to claim 5, comprising means for: A network connection setup message is sent to the second base station on the second vehicle that does not include the identifier associated with the device context.

7. The apparatus of any one of claims 1 to 6, wherein determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle comprises: It is determined that the device context transfer time has expired from the time the connection with the network was suspended.

8. The apparatus of any one of claims 1 to 7, wherein determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle comprises: An indication of the second base station on the second vehicle, or an indication of a cell served by the second base station on the second vehicle, is received from the first base station on the first vehicle.

9. The apparatus according to any one of claims 3 to 8, wherein the network connection release message comprises at least one of the following: The device context transfer time; the indication of the second base station on the second vehicle; or The indication of the cell served by the second base station on the second vehicle.

10. The apparatus of any one of claims 1 to 9, wherein determining that the device context stored on the first base station on the first vehicle is expected to be available to the second base station on the second vehicle comprises: A paging message is received from the second base station on the second vehicle.

11. The apparatus of claim 10, wherein the paging message comprises at least one of: The device context may be used for an indication of the second base station on the second vehicle; or The second base station on the second vehicle expects an indication by the device to resume the network connection via the second base station on the second vehicle.

12. The device according to any one of claims 1 to 11, comprising means for: determining that the device is moving out of coverage of the first base station on the first vehicle, or vice versa; and An indication is sent to the first base station on the first vehicle, or to the second base station on the second vehicle, that the apparatus is moving out of coverage of the first base station on the first vehicle, or vice versa.

13. The apparatus of claim 12, comprising means for: It is determined that the device is moving within the coverage of the second base station on the second vehicle, or vice versa.

14. A method comprising: suspending a network connection via a first base station on a first vehicle; determining that a device context stored on the first base station on the first vehicle is expected to be available to a second base station on a second vehicle; as well as An attempt is made to restore the network connection via the second base station on the second vehicle.

15. A computer program comprising computer executable instructions for performing the steps of the method according to claim 14 when executed on one or more processors.

Images