Apparatus, method, and computer program

Abstract

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

Description

[Technical Field] 【0001】 The present disclosure relates to an apparatus, method, and computer program for attempting to resume a network connection via a base station mounted on a vehicle. [Background technology] 【0002】 A communication system can 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 carriers between the various entities involved in the communication path. 【0003】 The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) that operate based on radio standards such as those provided by 3GPP, satellite-based communication systems, and different wireless local networks, e.g., wireless local area networks (WLANs). Wireless systems can typically be divided into cells, whereby they are often referred to as cellular systems. 【0004】 Communication systems and associated devices typically operate according to a given standard or specification that sets out the permitted behavior of various entities associated with the system and how to achieve it. The communication protocols and / or parameters used for the connections are also typically defined. An example of a standard is the so-called 5G standard. Summary of the Invention 【0005】 According to an aspect, an apparatus is provided that includes means for suspending a network connection via a first base station onboard a first vehicle, determining that an apparatus context stored on the first base station onboard the first vehicle is expected to be available to a second base station onboard a second vehicle, and attempting to resume the network connection via the second base station onboard the second vehicle. 【0006】 The second base station on the second vehicle may or may not be connected to the network. Different scenarios can be considered when attempting to resume network connectivity via the second base station on the second vehicle. 【0007】 In this scenario, a second base station may be connected to the network and may not have previously received and stored device context from the first base station. The second base station may now receive and store the device context from the first base station. Thus, the device context may be available to the second base station. Resumption of network connection via the second base station may be successful. 【0008】 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. Resumption of the network connection through the second base station may be successful. 【0009】 In another scenario, the second base station may not be connected to the network or 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. Resumption of the network connection through the second base station may be successful. 【0010】 In another scenario, the second base station may not be connected to the network, or may 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. Resumption of the network connection through the second base station may not be successful. 【0011】 The apparatus may include means for receiving a network connection release message from a first base station onboard the first vehicle, and attempting to resume the network connection via a second base station onboard the second vehicle may include sending a network connection resume message to the second base station onboard the second vehicle. 【0012】 The network connection release message may include an identifier associated with the device context, and the network connection resume message may include an identifier associated with the device context. 【0013】 The apparatus may include means for receiving a network connection resume complete message from a second base station onboard the second vehicle. 【0014】 The apparatus may include means for detecting a failure to receive a network connection resume complete message from a second base station onboard the second vehicle and storing on the apparatus an identifier associated with the apparatus context. 【0015】 The apparatus may include means for later retransmitting, to a second base station on a second vehicle, a network connection resume message including an identifier associated with the apparatus context. 【0016】 The identifier may be stored with at least one of a time parameter indicating how long the identifier is stored on the device before removing the identifier from the device, a maximum number of attempts parameter indicating the maximum number of times the device will subsequently retransmit to a second base station mounted on a second vehicle, a network connection resume message including the identifier before removing the identifier from the device, or a maximum number of identifiers parameter indicating the maximum number of identifiers the device will store. 【0017】 The apparatus may include means for transmitting, to a second base station on a second vehicle, a network connection setup message that does not include an identifier associated with the apparatus context. 【0018】 The apparatus may include means for detecting a failure to receive a network connection setup complete message from a second base station onboard the second vehicle when the second base station onboard the second vehicle is not connected to the network. 【0019】 The apparatus may include means for detecting a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determining that device context stored on a first base station onboard the first vehicle is expected to be available to a third base station onboard the third vehicle, and transmitting a network connection resume message to the third base station onboard the third vehicle, the network connection resume message including an identifier associated with the device context. 【0020】 The apparatus may include means for detecting a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determining that a third base station onboard the third vehicle is expected to be connected to the network, and sending a network connection setup message to the third base station onboard the third vehicle that does not include an identifier associated with the apparatus context. 【0021】 Determining that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle may include determining that a device context transfer time has expired from a time when connection with the network was interrupted. 【0022】 The device context transfer time may be received by the device from a first base station onboard the first satellite or may be calculated by the device. 【0023】 Determining that the device context stored on the first base station onboard the first vehicle is expected to be available to the second base station onboard the second vehicle may include receiving, from the first base station onboard the first vehicle, an indication of the second base station onboard the second vehicle or an indication of a cell served by the second base station onboard the second vehicle. 【0024】 The indication may indicate that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0025】 The network connection release message may include at least one of a device context transfer time, an indicator of a second base station mounted on the second vehicle, or an indicator of a cell served by the second base station mounted on the second vehicle. 【0026】 Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle may include receiving a paging message from the second base station mounted on the second vehicle. 【0027】 The paging message may include at least one of an indication that the device context is available to a second base station onboard the second vehicle or an indication that the second base station onboard the second vehicle expects the device to resume network connectivity via the second base station onboard the second vehicle. 【0028】 The apparatus may include means for determining that the apparatus is moving out of coverage or into coverage of a first base station mounted on the first vehicle, and transmitting an indication to the first base station mounted on the first vehicle or to a second base station mounted on the second vehicle that the apparatus is moving out of coverage or into coverage of the first base station mounted on the first vehicle. 【0029】 The apparatus may include means for determining that the apparatus is moving within or out of coverage of a second base station mounted on a second vehicle. 【0030】 The apparatus may include means for determining that the apparatus has high priority data and attempting to set up a network connection via a second base station onboard the second vehicle without prior attempting to reinstate the network connection via a second base station onboard the second vehicle. 【0031】 The device may be a user equipment. 【0032】 The first vehicle, the second vehicle, and / or the third vehicle may be a satellite, a drone, or a car. 【0033】 The first vehicle, the second vehicle, and / or the third vehicle may be stations that may have intermittent connectivity with the network. 【0034】 According to an aspect, an apparatus is provided that includes at least one processor and at least one memory containing computer code for one or more programs, wherein the at least one memory and computer code are configured to cause, with the at least one processor, the apparatus to at least: suspend a network connection via a first base station onboard a first vehicle; determine that device context stored on the first base station onboard the first vehicle is expected to be available to a second base station onboard a second vehicle; and attempt to resume the network connection via the second base station onboard the second vehicle. 【0035】 The second base station on the second vehicle may or may not be connected to the network. Different scenarios can be considered when attempting to resume network connectivity via the second base station on the second vehicle. 【0036】 In this scenario, a second base station may be connected to the network and may not have previously received and stored device context from the first base station. The second base station may now receive and store the device context from the first base station. Thus, the device context may be available to the second base station. Resumption of network connection by the second base station may be successful. 【0037】 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. Resumption of the network connection through the second base station may be successful. 【0038】 In another scenario, the second base station may not be connected to the network or 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. Resumption of the network connection through the second base station may be successful. 【0039】 In another scenario, the second base station may not be connected to the network, or may 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. Resumption of the network connection through the second base station may not be successful. 【0040】 The at least one memory and computer code may be configured, using the at least one processor, to cause the apparatus to at least receive a network connection release message from a first base station mounted on the first vehicle, and attempting to resume the network connection via a second base station mounted on the second vehicle may include sending a network connection resume message to the second base station mounted on the second vehicle. 【0041】 The network connection release message may include an identifier associated with the device context, and the network connection resume message may include an identifier associated with the device context. 【0042】 The at least one memory and computer code may be configured, using the at least one processor, to cause the apparatus to at least receive a network connection resume completion message from a second base station mounted on a second vehicle. 【0043】 The at least one memory and computer code may be configured, with the at least one processor, to cause the device to at least detect a failure to receive a network connection resume complete message from a second base station onboard the second vehicle and store on the device an identifier associated with the device context. 【0044】 The at least one memory and computer code may be configured, with the at least one processor, to cause the device to later retransmit, to at least a second base station mounted on a second vehicle, a network connection resume message including an identifier associated with the device context. 【0045】 The identifier may be stored with at least one of a time parameter indicating how long the identifier is stored on the device before removing the identifier from the device, a maximum number of attempts parameter indicating the maximum number of times the device will subsequently retransmit to a second base station mounted on a second vehicle, a network connection resume message including the identifier before removing the identifier from the device, or a maximum number of identifiers parameter indicating the maximum number of identifiers the device will store. 【0046】 The at least one memory and computer code may be configured, using the at least one processor, to cause the device to send, to at least a second base station mounted on a second vehicle, a network connection setup message that does not include an identifier associated with the device context. 【0047】 The at least one memory and computer code may be configured, with the at least one processor, to cause the apparatus to at least detect a failure to receive a network connection setup complete message from a second base station mounted on the second vehicle when the second base station mounted on the second vehicle is not connected to the network. 【0048】 The at least one memory and computer code may be configured, using the at least one processor, to cause the device to at least detect a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determine that device context stored on a first base station onboard the first vehicle is expected to be available to a third base station onboard the third vehicle, and send a network connection resume message to the third base station onboard the third vehicle, the network connection resume message including an identifier associated with the device context. 【0049】 The at least one memory and computer code may be configured, using the at least one processor, to cause the device to at least detect a failure to receive a network connection setup complete message from a second base station mounted on a second vehicle, determine that a third base station mounted on a third vehicle is expected to be connected to the network, and send a network connection setup message to the third base station mounted on the third vehicle that does not include an identifier associated with the device context. 【0050】 Determining that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle may include determining that a device context transfer time has expired from a time when connection with the network was interrupted. 【0051】 The device context transfer time may be received by the device from a first base station onboard the first satellite or may be calculated by the device. 【0052】 Determining that the device context stored on the first base station onboard the first vehicle is expected to be available to the second base station onboard the second vehicle may include receiving, from the first base station onboard the first vehicle, an indication of the second base station onboard the second vehicle or an indication of a cell served by the second base station onboard the second vehicle. 【0053】 The indication may indicate that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0054】 The network connection release message may include at least one of a device context transfer time, an indicator of a second base station mounted on the second vehicle, or an indicator of a cell served by the second base station mounted on the second vehicle. 【0055】 Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle may include receiving a paging message from the second base station mounted on the second vehicle. 【0056】 The paging message may include at least one of an indication that the device context is available to a second base station onboard the second vehicle or an indication that the second base station onboard the second vehicle expects the device to resume network connectivity via the second base station onboard the second vehicle. 【0057】 The at least one memory and computer code may be configured, using the at least one processor, to cause the device to at least determine that the device is moving out of coverage or into coverage of a first base station mounted on the first vehicle, and transmit to the first base station mounted on the first vehicle or to a second base station mounted on the second vehicle an indication that the device is moving out of coverage or into coverage of the first base station mounted on the first vehicle. 【0058】 The at least one memory and computer code may be configured, using the at least one processor, to cause the device to at least determine that the device is moving within or out of coverage of a second base station mounted on a second vehicle. 【0059】 The at least one memory and computer code may be configured, using the at least one processor, to cause the device to at least determine that the device has high priority data and attempt to set up a network connection via a second base station mounted on the second vehicle without previously attempting to resume the network connection via a second base station mounted on the second vehicle. 【0060】 The device may be a user equipment. 【0061】 The first vehicle, the second vehicle, and / or the third vehicle may be a satellite, a drone, or a car. 【0062】 The first vehicle, the second vehicle, and / or the third vehicle may be stations that may have intermittent connectivity with the network. 【0063】 According to an aspect, an apparatus is provided, the apparatus comprising: circuitry configured to suspend a network connection via a first base station onboard a first vehicle; determine that device context stored on the first base station onboard the first vehicle is expected to be available to a second base station onboard a second vehicle; and attempt to resume the network connection via the second base station onboard the second vehicle. 【0064】 The second base station on the second vehicle may or may not be connected to the network. Different scenarios can be considered when attempting to resume network connectivity via the second base station on the second vehicle. 【0065】 In this scenario, a second base station may be connected to the network and may not have previously received and stored device context from the first base station. The second base station may now receive and store the device context from the first base station. Thus, the device context may be available to the second base station. Resumption of network connection via the second base station may be successful. 【0066】 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. Resumption of the network connection through the second base station may be successful. 【0067】 In another scenario, the second base station may not be connected to the network or 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. Resumption of the network connection through the second base station may be successful. 【0068】 In another scenario, the second base station may not be connected to the network, or may 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. Resumption of the network connection through the second base station may not be successful. 【0069】 The apparatus may include circuitry configured to receive a network connection release message from a first base station onboard the first vehicle, and attempting to resume the network connection via a second base station onboard the second vehicle may include sending a network connection resume message to the second base station onboard the second vehicle. 【0070】 The network connection release message may include an identifier associated with the device context, and the network connection resume message may include an identifier associated with the device context. 【0071】 The apparatus may include circuitry configured to receive a network connection resume complete message from a second base station onboard a second vehicle. 【0072】 The apparatus may include circuitry configured to detect a failure to receive a network connection resume complete message from a second base station onboard a second vehicle and store an identifier associated with the apparatus context on the apparatus. 【0073】 The apparatus may include circuitry configured to later retransmit, to a second base station on a second vehicle, a network connection resume message including an identifier associated with the apparatus context. 【0074】 The identifier may be stored with at least one of a time parameter indicating how long the identifier is stored on the device before removing the identifier from the device, a maximum number of attempts parameter indicating the maximum number of times the device will subsequently retransmit to a second base station mounted on a second vehicle, a network connection resume message including the identifier before removing the identifier from the device, or a maximum number of identifiers parameter indicating the maximum number of identifiers the device will store. 【0075】 The apparatus may include circuitry configured to transmit, to a second base station on a second vehicle, a network connection setup message that does not include an identifier associated with the apparatus context. 【0076】 The apparatus may include circuitry configured to detect a failure to receive a network connection setup complete message from a second base station onboard the second vehicle when the second base station onboard the second vehicle is not connected to the network. 【0077】 The apparatus may include circuitry configured to detect a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determine that a device context stored on a first base station onboard the first vehicle is expected to be available to a third base station onboard the third vehicle, and send a network connection resume message to the third base station onboard the third vehicle, the network connection resume message including an identifier associated with the device context. 【0078】 The apparatus may include circuitry configured to detect a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determine that a third base station onboard the third vehicle is expected to be connected to the network, and send a network connection setup message to the third base station onboard the third vehicle that does not include an identifier associated with the apparatus context. 【0079】 Determining that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle may include determining that a device context transfer time has expired from a time when connection with the network was interrupted. 【0080】 The device context transfer time may be received by the device from a first base station onboard the first satellite or may be calculated by the device. 【0081】 Determining that the device context stored on the first base station onboard the first vehicle is expected to be available to the second base station onboard the second vehicle may include receiving, from the first base station onboard the first vehicle, an indication of the second base station onboard the second vehicle or an indication of a cell served by the second base station onboard the second vehicle. 【0082】 The indication may indicate that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0083】 The network connection release message may include at least one of a device context transfer time, an indicator of a second base station mounted on the second vehicle, or an indicator of a cell served by the second base station mounted on the second vehicle. 【0084】 Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle may include receiving a paging message from the second base station mounted on the second vehicle. 【0085】 The paging message may include at least one of an indication that the device context is available to a second base station onboard the second vehicle or an indication that the second base station onboard the second vehicle expects the device to resume network connectivity via the second base station onboard the second vehicle. 【0086】 The device may include circuitry configured to determine that the device is moving out of coverage or into coverage of a first base station mounted on the first vehicle and to transmit an indication to the first base station mounted on the first vehicle or to a second base station mounted on the second vehicle that the device is moving out of coverage or into coverage of the first base station mounted on the first vehicle. 【0087】 The device may include circuitry configured to determine when the device is moving within or out of coverage of a second base station mounted on a second vehicle. 【0088】 The device may include circuitry configured to determine that the device has high priority data and to attempt to set up a network connection via a second base station onboard the second vehicle without first attempting to reinstate the network connection via a second base station onboard the second vehicle. 【0089】 The device may be a user equipment. 【0090】 The first vehicle, the second vehicle, and / or the third vehicle may be a satellite, a drone, or a car. 【0091】 The first vehicle, the second vehicle, and / or the third vehicle may be stations that may have intermittent connectivity with the network. 【0092】 According to an aspect, a method is provided that includes suspending a network connection via a first base station onboard a first vehicle; determining that device context stored on the first base station onboard the first vehicle is expected to be available to a second base station onboard a second vehicle; and attempting to resume the network connection via the second base station onboard the second vehicle. 【0093】 The method may be performed by an apparatus. 【0094】 The second base station on the second vehicle may or may not be connected to the network. Different scenarios can be considered when attempting to resume network connectivity via the second base station on the second vehicle. 【0095】 In this scenario, a second base station may be connected to the network and may not have previously received and stored device context from the first base station. The second base station may now receive and store the device context from the first base station. Thus, the device context may be available to the second base station. Resumption of network connection via the second base station may be successful. 【0096】 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. Resumption of the network connection through the second base station may be successful. 【0097】 In another scenario, the second base station may not be connected to the network or 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. Resumption of the network connection through the second base station may be successful. 【0098】 In another scenario, the second base station may not be connected to the network, or may 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. Resumption of the network connection through the second base station may not be successful. 【0099】 The method may include receiving a network connection release message from a first base station onboard the first vehicle, and attempting to resume the network connection via a second base station onboard the second vehicle may include sending a network connection resume message to the second base station onboard the second vehicle. 【0100】 The network connection release message may include an identifier associated with the device context, and the network connection resume message may include an identifier associated with the device context. 【0101】 The method may include receiving a network connection resume complete message from a second base station onboard the second vehicle. 【0102】 The method may include detecting a failure to receive a network connection resume complete message from a second base station onboard the second vehicle and storing on the device an identifier associated with the device context. 【0103】 The method may include later retransmitting to a second base station on the second vehicle a network connection resume message that includes an identifier associated with the device context. 【0104】 The identifier may be stored with at least one of a time parameter indicating how long the identifier is stored on the device before removing the identifier from the device, a maximum number of attempts parameter indicating the maximum number of times the device will subsequently retransmit to a second base station mounted on a second vehicle, a network connection resume message including the identifier before removing the identifier from the device, or a maximum number of identifiers parameter indicating the maximum number of identifiers the device will store. 【0105】 The method may include transmitting a network connection setup message to a second base station onboard the second vehicle that does not include an identifier associated with the device context. 【0106】 The method may include detecting a failure to receive a network connection setup complete message from a second base station onboard the second vehicle when the second base station onboard the second vehicle is not connected to the network. 【0107】 The method may include detecting a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determining that device context stored on a first base station onboard the first vehicle is expected to be available to a third base station onboard the third vehicle, and sending a network connection resume message to the third base station onboard the third vehicle, the network connection resume message including an identifier associated with the device context. 【0108】 The method may include detecting a failure to receive a network connection setup complete message from a second base station onboard the second vehicle, determining that a third base station onboard the third vehicle is expected to be connected to the network, and sending a network connection setup message to the third base station onboard the third vehicle that does not include an identifier associated with the device context. 【0109】 Determining that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle may include determining that a device context transfer time has expired from a time when connection with the network was interrupted. 【0110】 The device context transfer time may be received by the device from a first base station onboard the first satellite or may be calculated by the device. 【0111】 Determining that the device context stored on the first base station onboard the first vehicle is expected to be available to the second base station onboard the second vehicle may include receiving, from the first base station onboard the first vehicle, an indication of the second base station onboard the second vehicle or an indication of a cell served by the second base station onboard the second vehicle. 【0112】 The indication may indicate that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0113】 The network connection release message may include at least one of a device context transfer time, an indicator of a second base station mounted on the second vehicle, or an indicator of a cell served by the second base station mounted on the second vehicle. 【0114】 Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle may include receiving a paging message from the second base station mounted on the second vehicle. 【0115】 The paging message may include at least one of an indication that the device context is available to a second base station onboard the second vehicle or an indication that the second base station onboard the second vehicle expects the device to resume network connectivity via the second base station onboard the second vehicle. 【0116】 The method may include determining that the device is moving out of coverage or into coverage of a first base station mounted on the first vehicle, and transmitting an indication to the first base station mounted on the first vehicle or to a second base station mounted on the second vehicle that the device is moving out of coverage or into coverage of the first base station mounted on the first vehicle. 【0117】 The method may include determining that the device is moving into or out of coverage of a second base station mounted on a second vehicle. 【0118】 The method may include determining that the device has high priority data and attempting to set up a network connection with a second base station mounted on the second vehicle without a prior attempt to reinitiate the network connection with the second base station mounted on the second vehicle. 【0119】 The device may be a user equipment. 【0120】 The first vehicle, the second vehicle, and / or the third vehicle may be a satellite, a drone, or a car. 【0121】 The first vehicle, the second vehicle, and / or the third vehicle may be stations that may have intermittent connectivity with the network. 【0122】 According to an aspect, a computer program is provided, the computer program including computer executable code configured, when executed on at least one processor, to suspend a network connection via a first base station onboard a first vehicle, determine that device context stored on the first base station onboard the first vehicle is expected to be available to a second base station onboard a second vehicle, and attempt to resume the network connection via the second base station onboard the second vehicle. 【0123】 At least one processor may be part of the device. 【0124】 The second base station on the second vehicle may or may not be connected to the network. Different scenarios can be considered when attempting to resume network connectivity via the second base station on the second vehicle. 【0125】 In this scenario, a second base station may be connected to the network and may not have previously received and stored device context from the first base station. The second base station may now receive and store the device context from the first base station. Thus, the device context may be available to the second base station. Resumption of network connection via the second base station may be successful. 【0126】 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. Resumption of the network connection through the second base station may be successful. 【0127】 In another scenario, the second base station may not be connected to the network or 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. Resumption of the network connection through the second base station may be successful. 【0128】 In another scenario, the second base station may not be connected to the network, or may 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. Resumption of the network connection through the second base station may not be successful. 【0129】 The computer program may include computer executable code that, when executed on at least one processor, is configured to receive a network connection release message from a first base station mounted on the first vehicle, and wherein attempting to resume the network connection via a second base station mounted on the second vehicle may include sending a network connection resume message to the second base station mounted on the second vehicle. 【0130】 The network connection release message may include an identifier associated with the device context, and the network connection resume message may include an identifier associated with the device context. 【0131】 The computer program may include computer executable code that, when executed on at least one processor, is configured to receive a network connection resume completion message from a second base station mounted on a second vehicle. 【0132】 The computer program may include computer executable code configured, when executed on at least one processor, to detect a failure to receive a network connection resume complete message from a second base station onboard a second vehicle and store an identifier associated with the device context on the device. 【0133】 The computer program may include computer executable code that, when executed on the at least one processor, is configured to subsequently retransmit, to a second base station on a second vehicle, a network connection resume message that includes an identifier associated with the device context. 【0134】 The identifier may be stored with at least one of a time parameter indicating how long the identifier is stored on the device before removing the identifier from the device, a maximum number of attempts parameter indicating the maximum number of times the device will subsequently retransmit to a second base station mounted on a second vehicle, a network connection resume message including the identifier before removing the identifier from the device, or a maximum number of identifiers parameter indicating the maximum number of identifiers the device will store. 【0135】 The computer program may include computer executable code configured, when executed on at least one processor, to send a network connection setup message to a second base station mounted on a second vehicle, the network connection setup message not including an identifier associated with the device context. 【0136】 The computer program may include computer executable code that, when executed on at least one processor, is configured to detect a failure to receive a network connection setup complete message from a second base station mounted on the second vehicle when the second base station mounted on the second vehicle is not connected to the network. 【0137】 The computer program may include computer-executable code configured, when executed on at least one processor, to detect a failure to receive a network connection setup complete message from a second base station mounted on a second vehicle, determine that a device context stored on a first base station mounted on a first vehicle is expected to be available to a third base station mounted on a third vehicle, and send a network connection resume message to the third base station mounted on the third vehicle, the network connection resume message including an identifier associated with the device context. 【0138】 The computer program may include computer executable code configured, when executed on at least one processor, to detect a failure to receive a network connection setup complete message from a second base station mounted on a second vehicle, determine that a third base station mounted on a third vehicle is expected to be connected to the network, and send a network connection setup message to the third base station mounted on the third vehicle that does not include an identifier associated with the device context. 【0139】 Determining that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle may include determining that a device context transfer time has expired from a time when connection with the network was interrupted. 【0140】 The device context transfer time may be received by the device from a first base station onboard the first satellite or may be calculated by the device. 【0141】 Determining that the device context stored on the first base station onboard the first vehicle is expected to be available to the second base station onboard the second vehicle may include receiving, from the first base station onboard the first vehicle, an indication of the second base station onboard the second vehicle or an indication of a cell served by the second base station onboard the second vehicle. 【0142】 The indication may indicate that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0143】 The network connection release message may include at least one of a device context transfer time, an indicator of a second base station mounted on the second vehicle, or an indicator of a cell served by the second base station mounted on the second vehicle. 【0144】 Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle may include receiving a paging message from the second base station mounted on the second vehicle. 【0145】 The paging message may include at least one of an indication that the device context is available to a second base station onboard the second vehicle or an indication that the second base station onboard the second vehicle expects the device to resume network connectivity via the second base station onboard the second vehicle. 【0146】 The computer program may include computer-executable code configured, when executed on at least one processor, to determine that a device is moving out of coverage or into coverage of a first base station mounted on a first vehicle, and to transmit an indication to the first base station mounted on the first vehicle or to a second base station mounted on a second vehicle that the device is moving out of coverage or into coverage of the first base station mounted on the first vehicle. 【0147】 The computer program may include computer executable code configured, when executed on at least one processor, to determine that the device is moving within or out of coverage of a second base station mounted on a second vehicle. 【0148】 The computer program may include computer executable code configured, when executed on at least one processor, to determine that the device has high priority data and attempt to set up a network connection via a second base station mounted on the second vehicle without first attempting to reinstate the network connection via a second base station mounted on the second vehicle. 【0149】 The device may be a user equipment. 【0150】 The first vehicle, the second vehicle, and / or the third vehicle may be a satellite, a drone, or a car. 【0151】 The first vehicle, the second vehicle, and / or the third vehicle may be stations that may have intermittent connectivity with the network. 【0152】 According to an aspect, a computer-readable medium is provided that includes program instructions stored thereon for performing at least one of the above methods. 【0153】 According to an aspect, a non-transitory computer-readable medium is provided that includes program instructions stored thereon for performing at least one of the above methods. 【0154】 According to an aspect, a non-volatile tangible memory medium is provided that includes program instructions stored thereon for performing at least one of the above methods. 【0155】 A number of different aspects have been described above, and it should be understood that further aspects may be provided by combining any two or more of the above-described aspects. 【0156】 Various other aspects are also set forth in the following detailed description and appended claims. 【0157】 List of abbreviations AF: Application Features AMF: Access and Mobility Management Function API: Application Programming Interface AS: Access Layer BS: Base station CU: Centralized Unit CP: Control Plane DL: Downlink DU: Distributed Unit EPS: Evolved Packet System eMTC: Enhanced Machine Type Communication eNB: eNodeB or eNodeB or E-UTRAN NodeB gNB; gNode B GSM: Global System for Mobile Communications GW: Gateway HSS: Home Subscriber Server ID: Identifier IoT: Internet of Things LTE: Long Term Evolution MAC: Media Access Control MS: Mobile station MTC: Machine Type Communication NAS: Non-access layer NEF: Network Exposure Function NF: Network function NR:New Radio NRF: Network Repository Facility NTN: Non-terrestrial network PDU: Packet Data Unit RAM: Random Access Memory (R)AN: (Radio) Access Network ROM: Read-Only Memory RRC: Radio Resource Control S&F: Store and Forward SMF: Session Management Facility TAU: Tracking Area Update TN: Terrestrial network TR: Technical Report TS: Technical Specifications UE: User Equipment UMTS: Universal Mobile Telecommunications System UP: User plane WI:Work item 3GPP: Third Generation Partnership Project 5G: Fifth Generation 5GC: 5G Core Network 5GS: 5G system 【0158】 Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief explanation of the drawings] 【0159】 [Figure 1] 1 shows a schematic representation of a 5G system. [Figure 2] 1 shows a schematic representation of a control device. [Figure 3] 1 shows a schematic representation of a user equipment. [Figure 4]This shows a signaling diagram of the radio resource control connection resumption procedure in an evolved packet system according to TS36.330 (Figure 7.3a.3-3: RRC connection resumption procedure in eNBs with different EPS). [Figure 5] A deployment is shown in which a first eNodeB on board a first satellite is connected to the network, a second eNodeB on board a second satellite is not connected to the network, and a third eNodeB on board a third satellite is connected to the network. [Figure 6] 1 is a flowchart of a method for attempting to resume a network connection via a base station onboard a vehicle. [Figure 7] 1 shows a block diagram of a method for attempting to resume network connectivity via a base station onboard a vehicle. [Figure 8] 8 illustrates a schematic representation of a non-volatile memory medium storing instructions that, when executed by a processor, enable the processor to perform one or more of the steps of the method of FIG. 7. DETAILED DESCRIPTION OF THE INVENTION 【0160】

[0013] The following describes certain embodiments relating to mobile communication devices that enable communication over a wireless cellular system, and mobile communication systems that serve such mobile communication devices. Before describing the exemplary embodiments in detail, certain general principles of wireless communication systems, their access systems, and mobile communication devices will be briefly described with reference to Figures 1, 2, and 3 to aid in understanding the technology underlying the described examples. 【0161】 Figure 1 shows a schematic representation of a 5G system (5GS), which 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). 【0162】 A 5G (R)AN may include a terrestrial network (TN) portion, where one or more gNBs are located on one or more masts or towers on the ground. A 5G (R)AN may include a non-terrestrial network (NTN) portion, where one or more gNBs are located on one or more satellites or on one or more masts or towers on the ground. 【0163】 One or more gNBs may include one or more gNB distributed unit functions connected to one or more gNB centralized unit functions. 【0164】 The 5GC may include an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a User Data Management Function (UDM), a User Plane Function (UPF), and / or a Network Exposure Function (NEF). The 5GC may include a Gateway (GW) to the NTN portion of the 5G (R)AN. 【0165】 FIG. 2 shows an example of a controller 200 that controls functions of an (R)AN or 5GC as shown in FIG. 1. The controller 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. The at least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, perform one or more steps to enable one or more of the present aspects to be performed. The software code 215 may be stored in the ROM 211b. The controller 200 may be interconnected with another controller 200 that controls another function of the 5G (R)AN or 5GC. In some embodiments, each function of the (R)AN or 5GC includes a controller 200. In alternative embodiments, two or more functions of the (R)AN or 5GC may share a controller. 【0166】 FIG. 3 illustrates an example of a user equipment (UE) 300, such as the user equipment (UE) illustrated in FIG. 1. The UE 300 may be provided by any device capable of transmitting and receiving wireless signals. Non-limiting examples of the user equipment include a mobile device, such as a mobile station (MS) or a mobile phone or what is referred to as a "smartphone," a computer equipped with a wireless interface card or other wireless interface equipment (e.g., a USB dongle), a personal digital assistant (PDA) or tablet equipped with wireless communication capabilities, a machine-type communication (MTC) device, a cellular Internet of things (CIoT) device, or any combination thereof. The UE 300 may provide communication of data, for example, to carry the communication. The communication may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data, etc. 【0167】 The UE 300 may receive signals over the air or wireless interface 307 via suitable equipment for receiving wireless signals and may transmit signals via suitable equipment for transmitting wireless signals. The transceiver equipment is shown schematically in Figure 3 by block 306. The transceiver equipment 306 may be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement may be located internal or external to the mobile device. 【0168】 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 software and hardware-assisted execution of tasks it is designed to perform, including controlling access to and communicating with the access system 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, enable one or more of the present aspects to be performed. The software code 308 may be stored in the ROM 302a. 【0169】 The processor, storage, and other associated controls may be provided on a suitable 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 keypad 305, a touch-sensitive screen or pad, or a combination thereof. Optionally, one or more of a display, a speaker, and a microphone may be provided, depending on the type of device. 【0170】 One or more aspects of the present disclosure relate to NTN, which is defined for NR and Narrow Band Internet of Things (NB-IoT) and / or enhanced machine type communications (eMTC) in Release 17. As part of preparations for Release 18, companies submitted proposals for work item descriptions in RAN#94e in December 2021. 【0171】 In RP-212940, satellite companies submitted a joint proposal that included a new scenario: store-and-forward operation for IoT NTN. RP-212940 (Section 4.1.4 Support for Store-and-Forward Operation) states: 【0172】 "Store and Forward (S&F) is a new feature that enables satellites to serve IoT NTN devices even during periods / areas when they are not connected to a terrestrial gateway. An eNB on-board architecture is envisioned. Asynchronous operation of service link and feeder link is envisioned. Messages are stored on board until line of sight with the GW is established. A candidate set of enhancement goals are: Support for separate signaling procedures for UE <-> satellite with onboard RAN node and satellite with onboard RAN node <-> terrestrial CN to achieve end-to-end functionality [RAN2, RAN3] Dynamic attachment between S-GW and eNB [RAN3] 【0173】 The store-and-forward operation is based on the Rel-17 concept of discontinuous coverage scenarios, where the UE only has coverage from the satellite occasionally and temporarily. The discontinuous coverage scenario can also be extended by defining that the satellite is not always connected to the core network (i.e., GW). 【0174】 The following description applies to EPS as an example, but it should be understood that it may be applicable to other systems, such as 5GS or its next generation systems. The description relates to eNB as an example, but it should be understood that it may be applicable to other BSs, such as gNB or its next generation BSs. 【0175】 Store-and-forward operation can enable low-cost deployments consisting of only a few BSs onboard satellites and a few BSs on the ground, which means that connection costs per UE can be reduced only at the cost of being able to support delay-tolerant data. 【0176】 A challenge in the store-and-forward operating scenario is how the UE can establish an RRC connection (i.e., a secure connection) with the EPC when the link between the UE and the eNB on board the satellite and the link between the eNB on board the satellite and the EPC are not simultaneously available. 【0177】 Assuming that an RRC connection with the EPC has been established by the UE, it may be beneficial to maintain a UE context in the UE and the eNB on board the satellite. The UE context may include access stratum (AS) and radio resource control (RRC) configuration. 【0178】 The UE may receive an RRC connection release message from an eNB onboard the satellite. The RRC connection release message may include an indication (e.g., a cause) that the RRC connection has been interrupted. The RRC connection release message may include a resume ID. 【0179】 The resume ID may be associated with the UE context. The resume ID may be stored by the eNB onboard the satellite along with the UE context. The resume ID may include a UE ID portion and / or an eNB ID portion. The resume ID may include a 5GS inactive radio network primary identifier. 【0180】 The UE may then decide to resume the RRC connection. For example, the UE may want to resume the RRC connection when the UE has UE-originated traffic to send to the EPC. The UE may want to resume the RRC connection after a radio link failure. The UE may want to resume the RRC connection after a handover failure. The UE may want to resume the RRC connection after receiving a paging message from the EPC. 【0181】 When the UE wishes to resume the RRC connection, the UE may send an RRC connection resume message to another eNB on board another satellite. The RRC connection resume message may include a resume ID. The resume ID may enable the other eNB on board the other satellite to fetch the UE context from the eNB on board the satellite via the EPC and store the UE context on the other eNB on board the other satellite. 【0182】 Figure 4 shows a signaling diagram of the radio resource control connection resumption procedure in an evolved packet system according to TS36.330 (Figure 7.3a.3-3: RRC connection resumption procedure in eNBs with different EPS). TS36.330 (Section 7.3a.3-3 User Plane CIoT EPS / 5GS Optimization) is written as follows: 【0183】 "1. Same as step 1 of Internal (ng-)eNB Connection Resumption. 2. The new (ng-) eNB locates the old (ng-) eNB using the Resumption ID (for EPS) or I-RNTI (for 5GS) and retrieves the UE context using the X2-AP (for EPS) or Xn-AP (for 5GS) Acquire UE Context procedure. 3. The old (ng-) eNB responds with the UE context associated with the resumption ID (for EPS) or I-RNTI (for 5GS). 4. Same as step 2 for internal (ng-)eNB connection resumption. 5. Same as step 3 for internal (ng-)eNB connection resumption. 6. Same as step 4 for internal (ng-)eNB connection resumption. 7. In the case of EPS, the new eNB initiates an S1-AP path switch procedure to establish an S1 UE-related signaling connection to the serving MME and requests the MME to resume the UE context. In the case of 5GS, the new ng-eNB initiates an NG-AP path switch procedure to establish an NG UE-related signaling connection to the serving AMF and requests the AMF to resume the UE context. 8. In the case of EPS, the MME requests the S-GW to activate the S1-U bearer for the UE and update the downlink path. In the case of 5GS, the AMF requests the SMF to resume the PDU session, and the SMF requests the UPF to create tunnel information for the UE and update the downlink path. 9. MME / AMF acknowledges step 7. 10. In the case of EPS, after the S1-AP path switch procedure, the new eNB triggers the release of the UE context at the old eNB using the X2-AP UE context release procedure. In the case of 5GS, after the NG-AP path switch procedure, the new ng-eNB triggers the release of the UE context at the old ng-eNB using the Xn-AP UE context release procedure. 【0184】 As shown in Figure 4, another eNB on board another satellite (i.e., the "new eNB") may be expected to obtain the UE context from the eNB on board the satellite (i.e., the "old eNB") via the EPC. This may be a challenge in store-and-forward operation because the other eNB on board the other satellite (i.e., the "new eNB") and the eNB on board the satellite (i.e., the "old eNB") may not be connected to the EPC at the same time. 【0185】 One or more aspects of the present disclosure may provide options for how to configure a UE to attempt to resume an RRC connection via another base station (i.e., a “new eNB”) onboard another satellite, particularly in store-and-forward operations. 【0186】 TS36.331 (Section 5.3.3.2 Initiation) defines the conditions for resuming an RRC connection and states the following: 【0187】 "The UE initiates the procedure when higher layers request establishment or resumption of an RRC connection while the UE is in RRC_IDLE state, or when higher layers request resumption of an RRC connection while the UE is in RRC_INACTIVE state, or when the RRC layer requests resumption of an RRC connection, e.g., for reception of RNAU or RAN paging." 【0188】 The UE may initiate the RRC connection procedure by sending an RRC connection resume request message to another eNB on board another satellite. The RRC connection resume request message may include information such as: 【0189】 RRCConnectionResumeRequest Message -- ASN1START RRCConnectionResumeRequest-r13 ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionResumeRequest-r13 RRCConnectionResumeRequest-r13-IEs, rrcConnectionResumeRequest-r15 RRCConnectionResumeRequest-5GC-r15-IEs } } RRCConnectionResumeRequest-r13-IEs ::= SEQUENCE { resumeIdentity-r13 CHOICE { resumeID-r13 ResumeIdentity-r13, truncatedResumeID-r13 BIT STRING (SIZE (24)) }, shortResumeMAC-I-r13 BIT STRING (SIZE (16)), resumeCause-r13 ResumeCause, spare BIT STRING (SIZE (1)) } RRCConnectionResumeRequest-5GC-r15-IEs ::= SEQUENCE { resumeIdentity-r15 CHOICE { fullI-RNTI-r15 I-RNTI-r15, shortI-RNTI-r15 ShortI-RNTI-r15 }, shortResumeMAC-I-r15 BIT STRING (SIZE (16)), resumeCause-r15 ResumeCause-r15, spare BIT STRING (SIZE (1)) } ResumeCause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, delayTolerantAccess-v1020, mo-VoiceCall-v1280, mt-EDT-v1610 } ResumeCause-r15 ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, rna-Update, mo-VoiceCall, spare1 } -- ASN1STOP 【0190】 【Table 1】 【0191】 Upon sending an RRC connection resume message to another eNB (i.e., a "new eNB") on board another satellite, the UE may restore the RRC configuration. The UE may apply integrity protection and ciphering according to the existing security context. 【0192】 In this scenario, another eNB (i.e., a "new eNB") on board another satellite may respond to the RRC connection resumption message with another RRC connection resumption message. The UE may update security keys based on the content of the other RRC connection resumption message and the UE context. The UE may continue resuming the RRC connection via the other eNB (i.e., a "new eNB") on board another satellite. 【0193】 In another scenario, another eNB (i.e., a "new eNB") on board another satellite may respond to the RRC connection resume message with an RRC connection setup message. The UE may destroy the UE context (including security keys). 【0194】 In another scenario, another eNB (i.e., a "new eNB") on board another satellite may respond to the RRC connection resumption message with an RRC connection reject message. The UE may destroy the UE context (including security keys). The UE may notify higher layers about the failure to resume the RRC connection via the other eNB on board the other satellite. 【0195】 In another scenario, another eNB (i.e., a "new eNB") on board another satellite 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 a suspended RRC state. 【0196】 One or more aspects of the present disclosure may configure how and / or when a UE is permitted to attempt to resume an RRC connection via another eNB (i.e., a “new eNB”) onboard another satellite in a store-and-forward operation scenario. 【0197】 In the scenario, it may be assumed that the UE context is likely to be available to other eNBs (i.e., "new eNBs") on other satellites before and / or when the UE is within the coverage of the other eNBs (i.e., "new eNBs") on other satellites. 【0198】 FIG. 5 shows a deployment in which a first eNodeB onboard a first satellite SAT1 is connected to an EPC, a second eNodeB onboard a second satellite SAT2 is not connected to an EPC, and a third eNodeB onboard a third satellite SAT3 is connected to an EPC. 【0199】 The UE may set up an RRC connection via a first eNodeB onboard the first satellite SAT1. For example, the UE may send an RRC connection setup message to the first eNodeB onboard the first satellite SAT1. The first eNodeB onboard the first satellite SAT1 may store a resumption ID associated with the UE context along with the UE context. 【0200】 The first eNodeB onboard the first satellite SAT1 may instruct the UE to suspend the RRC connection. For example, the first eNodeB onboard the first satellite SAT1 may send an RRC connection release message to the UE. 【0201】 The RRC connection release message may include a resumption ID associated with the UE context. 【0202】 The RRC connection release message may include a UE context transfer time that allows the first eNodeB, EPC, or proxy on board the first satellite SAT1 to transfer the UE context to a third eNodeB on board the third satellite SAT3. 【0203】 The RRC connection release message may include an indicator (e.g., SAT ID) of a third eNodeB onboard a third satellite SAT3 from the first satellite SAT1, or an indicator (e.g., PCI) of a cell served via the third eNodeB onboard the third satellite SAT3. 【0204】 The RRC connection release message may include an indicator to attempt to resume the RRC connection via a third eNodeB onboard the third satellite SAT3. The indicator may include a cause set to "resume_store_forward." 【0205】 The UE may store the resumption ID associated with the UE context. The UE may suspend the RRC connection via the first eNodeB onboard the first satellite SAT1. 【0206】 The UE context may not be available to a second eNodeB on board a second satellite SAT2, but the UE context may be available to a third eNodeB on board a third satellite SAT3. 【0207】 In an embodiment, the UE may not attempt to resume the RRC connection with the second eNodeB on board the second satellite SAT2. The EPC may prevent sending data for the UE to the second eNodeB on board the second satellite SAT2. However, this may make it difficult for the EPC to know that the UE context may not be available to the second eNodeB on board the second satellite SAT2 when the first eNodeB on board the first satellite SAT1 is not connected to the EPC and therefore cannot obtain such information from the first eNodeB on board the first satellite SAT1. 【0208】 In another embodiment, the UE context may not be available to a second eNodeB onboard the second satellite SAT2. The UE may attempt to resume the RRC connection via the second eNodeB onboard the second satellite SAT2. The attempt for RRC connection resumption via the second eNodeB onboard the second satellite SAT2 may fail. The UE may store a resumption ID associated with the UE context received in an RRC connection release message from the first eNodeB onboard the first satellite SAT1. The UE may use the resumption ID to later retry resuming the RRC connection via the second eNodeB onboard the second satellite SAT2 or to attempt resumption of the RRC connection via a third eNodeB onboard the third satellite SAT3. 【0209】 The UE may store the resumption ID along with one or more parameters. 【0210】 The UE may use the resumption ID to retry resuming the RRC connection via a second eNodeB onboard the second satellite SAT2, or may store the resumption ID associated with the UE context along with a timer parameter indicating how long to attempt resumption of the RRC connection via a third eNodeB onboard the third satellite SAT3. 【0211】 The UE may use the resumption ID to retry resuming the RRC connection via the second eNodeB onboard the second satellite SAT2, or may store the resumption ID associated with the UE context together with a max attempts parameter indicating the maximum number of times to attempt resumption of the RRC connection via the third eNodeB onboard the third satellite SAT3. 【0212】 The UE may store the resume IDs associated with the UE context along with a max resume IDs parameter that indicates the maximum number of IDs that may be stored by the UE. 【0213】 In this way, the UE can control the length and number of resumption IDs that can be stored by the UE. 【0214】 In another embodiment, the UE context may be available to a third eNodeB onboard a third satellite SAT3. The UE may attempt to resume the RRC connection via the third eNodeB onboard the third satellite SAT3. For example, the UE may send an RRC connection resume message to the third eNodeB onboard the third satellite SAT3. The RRC connection resume message may include a resumption ID associated with the UE context. 【0215】 After receiving the RRC connection release message, the UE may attempt to resume the RRC connection via the third eNodeB on board the third satellite SAT3. As described above, the RRC connection release message may include that a UE context transfer time that allows the first eNodeB, EPC, or proxy on board the first satellite SAT1 to transfer the UE context to the third eNodeB on board the third satellite SAT3 has expired from the time the RRC connection was interrupted. 【0216】 After receiving the RRC connection release message, the UE may attempt to resume the RRC connection via the third eNodeB onboard the third satellite SAT3. As described above, the RRC connection release message may include an indicator (e.g., SAT ID) of the third eNodeB onboard the third satellite SAT3 from the first satellite SAT1 or an indicator (e.g., PCI) of the cell served by the third eNodeB onboard the third satellite SAT3. 【0217】 The UE may attempt to resume the RRC connection via the third eNodeB on board the third satellite SAT3 after receiving a paging message from the third eNodeB on board the third satellite SAT3. The paging message may be a specialized or dedicated paging message. 【0218】 The paging message may include an indication that the UE may continue UL transmission to the EPC via a third eNodeB on board the third satellite SAT3, or that the third eNodeB on board the third satellite SAT3 has feedback about a previous UL transmission to the EPC via the first eNodeB on board the first satellite SAT1. 【0219】 This may include the case where the UE transmitted data in a previous UL transmission via the first satellite SAT1, and the application transmitting the data may expect feedback to the UE from the EPC or an application on the other side. The third satellite SAT3 may be carrying this feedback from the EPC to the UE. 【0220】 The third eNodeB on board the third satellite SAT3 may be carrying application layer feedback for some application layer data that the UE previously transmitted to the EPC via the first eNodeB on board the first satellite SAT1. The first eNodeB on board the first satellite SAT1 may be providing data to the EPC. The EPC may obtain the application feedback from an application layer sink (e.g., a database or server). The application layer feedback may be forwarded from the EPC to the third eNodeB on board the third satellite SAT3 so that the third eNodeB on board the third satellite SAT3 may provide the application layer feedback to the UE. 【0221】 The paging message may include an indication that the UE context is available to a third eNodeB onboard a third satellite, SAT3. 【0222】 The paging message may include an indication to attempt resumption of the RRC connection via a third eNodeB onboard the third satellite SAT3. The indication may include a flag bit (e.g., a resumption flag) set to '1' or '0' to indicate per UE ID in the paging record to attempt resumption of the RRC connection by a third eNodeB onboard the third satellite SAT3 or to attempt setup of a new RRC connection via a third eNodeB onboard the third satellite SAT3. The flag bit may be added to TS36.331 as follows: 【0223】 The paging message may include a resume ID delivered to the third satellite SAT3 via the EPC or proxy, which the UE may then match to a resume ID associated with a UE context stored on the UE. 【0224】 "Paging ::= SEQUENCE { pagingRecordList PagingRecordList OPTIONAL, -- Need ON systemInfoModification ENUMERATED {true} OPTIONAL, -- Need ON etws-Indication ENUMERATED {true} OPTIONAL, -- Need ON nonCriticalExtension Paging-v890-IEs OPTIONAL } PagingRecordList ::= SEQUENCE (SIZE (1..maxPageRec)) OF PagingRecord PagingRecord ::= SEQUENCE { ue-Identity PagingUE-Identity, cn-Domain ENUMERATED {ps, cs}, ResumeFlag BOOLEAN ... } PagingUE-Identity ::= CHOICE { s-TMSI S-TMSI, imsi IMSI, ..., ng-5G-S-TMSI-r15 NG-5G-S-TMSI-r15, fullI-RNTI-r15 I-RNTI-r15 }" 【0225】 Alternatively, the UE context may not be available to a second eNodeB on board a second satellite SAT2, and the UE context may also not be available to a third eNodeB on board a third satellite SAT3. 【0226】 In an embodiment, when a third eNodeB on board the third satellite SAT3 is connected to the EPC, the UE may set up a new RRC connection with the third eNodeB on board the third satellite SAT3. For example, the UE may send an RRC connection setup message to the third eNodeB on board 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 board the third satellite SAT3. 【0227】 In another embodiment, when the third eNodeB on board the third satellite SAT3 is not connected to the EPC, the UE may wait for the UE context to become available to the fourth eNodeB on board the fourth satellite SAT4 and may attempt to resume the RRC connection via the fourth eNodeB on board the fourth satellite SAT4. For example, the UE may send an RRC connection resume message to the fourth eNodeB on board the fourth satellite SAT4. 【0228】 In another embodiment, 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. 【0229】 In another embodiment, when the third eNodeB on board the third satellite SAT3 is not connected to the EPC, the UE may set up a new RRC connection via the third eNodeB on board the third satellite SAT3. The UE may send an RRC connection setup message to the third eNodeB on board the third satellite SAT3. The UE may wait for the third eNodeB on board the third satellite SAT3 to connect to the EPC and complete the setup of the new RRC connection via the third eNodeB on board the third satellite SAT3. 【0230】 The first eNodeB on board the first satellite SAT1 may provide a time (i.e., delay) for completing the setup of a new RRC connection via the third eNodeB on board the third satellite SAT3 when the first eNodeB on board the first satellite SAT1 instructs the UE to suspend the RRC connection. The time (i.e., delay) for completing the setup of a new RRC connection via the third eNodeB on board the third satellite SAT3 may be provided in an RRC connection release message. 【0231】 If the UE supports a control plane (CP) solution in which packets can be delivered using the NAS security key, the UE may set up an RRC connection to transmit packets using the NAS security key via a third eNodeB onboard the third satellite SAT3. In this case, the EPC may ensure that the security key provided to the (R)AN for the UP solution is not released. In other words, the EPC may ensure coexistence of UP and CP-based solutions for this scenario. If the third eNodeB onboard the third satellite SAT3 is not connected to the EPC, packets may be buffered by the third satellite SAT3 to allow the EPC (i.e., GW) to subsequently verify the security of the packets. The EPS may conditionally configure this "switch to CP solution." The condition may be based on packet priority and / or the number of packets. 【0232】 When the UE moves out of the coverage area of ​​the first eNodeB on the first satellite SAT1, the UE may perform a Tracking Area Update (TAU) to indicate to the first eNodeB on the first satellite SAT1 that the UE is in a new area. The new area may be a tracking area, a coverage area of ​​a third eNodeB on the 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, etc. 【0233】 After performing the TAU, the UE may wait for the UE context to become available in the new area. The UE may know that the context is available based on a paging message. For uplink-oriented data, the EPC may respond to the TAU with an "estimated time until context is available in new TAU" parameter, which allows the UE to postpone the RRC connection resumption procedure accordingly. 【0234】 When the UE has high priority data (e.g., an emergency call or exceptional data), the UE may attempt to set up a new RRC connection via the third eNodeB on board the third satellite SAT3 as soon as possible without attempting to resume the RRC connection via the third eNodeB on board the third satellite SAT3. 【0235】 One or more aspects of the present disclosure may enable a UE to use an RRC connection release (i.e., suspension) procedure and an RRC connection resumption procedure, thereby significantly reducing the time to complete random access and initiate data transfer compared to a full RRC connection setup. 【0236】 One or more aspects of the present disclosure may enable a UE to determine when / which satellite-borne eNodeB to use to perform RRC connection release (i.e., suspension) and RRC connection resumption procedures (RRC inactive in NR) in a store-and-forward operation scenario, which may be useful to avoid failed and complete RRC connection setup procedures. 【0237】 FIG. 6 is a flowchart of a method for attempting to resume network connectivity via an eNodeB onboard a satellite. 【0238】 First, the UE may set up an RRC connection via a first eNodeB onboard the first satellite SAT1. For example, the UE may send an RRC connection setup message to the first eNodeB onboard the first satellite SAT1. The first eNodeB onboard the first satellite SAT1 may store a resumption ID associated with the UE context along with the UE context. 【0239】 The first eNodeB onboard the first satellite SAT1 may instruct the UE to release the RRC connection. For example, the first eNodeB onboard the first satellite SAT1 may send an RRC connection release message to the UE. 【0240】 The RRC connection release message may include a resumption ID associated with the UE context. 【0241】 The RRC connection release message may include a UE context transfer time that allows the first eNodeB, EPC, or proxy on board the first satellite SAT1 to transfer the UE context to a third eNodeB on board the third satellite SAT3. 【0242】 The RRC connection release message may include an indicator (e.g., SAT ID) of a third eNodeB on board a third satellite SAT3 from the first satellite SAT1, or an indicator (e.g., PCI) of a cell served by the third eNodeB on board the third satellite SAT3. 【0243】 The RRC connection release message may include an indicator to attempt to resume the RRC connection via a third eNodeB onboard the third satellite SAT3. The indicator may include a cause set to "resume_store_forward." 【0244】 The UE may store the resumption ID associated with the UE context. The UE may release (i.e., suspend) the RRC connection via the first eNodeB onboard the first satellite SAT1. 【0245】 In step 600, the UE may determine that the UE has a resumption ID associated with a UE context stored on the UE. 【0246】 In step 602, the UE may determine that a third eNodeB onboard 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 eNodeB onboard the third satellite SAT3. The UE may determine whether a UE context is expected to be available for the third eNodeB onboard the third satellite SAT3. 【0247】 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. 【0248】 If the RRC release message includes a UE context transfer time and the UE context transfer time has expired, the method proceeds to step 606 . 【0249】 If the RRC release message does not include a UE context transfer time, or if the RRC release message includes a UE context transfer time and the UE context transfer time has not expired, the method proceeds to step 608 . 【0250】 In step 610 (option B), the UE may determine whether the RRC release message includes an indicator (e.g., SAT ID) of a third eNodeB mounted on a third satellite SAT3 from the first satellite SAT1, or an indicator (e.g., PCI) of a cell served by the third eNodeB mounted on the third satellite SAT3. 【0251】 If the RRC release message includes an indicator (e.g., SAT ID) of a third eNodeB onboard a third satellite SAT3 from the first satellite SAT1, or an indicator (e.g., PCI) of a cell served by a third eNodeB onboard the third satellite SAT3, the method proceeds to step 606. 【0252】 If the RRC release message does not include an indicator (e.g., SAT ID) of a third eNodeB onboard a third satellite SAT3 from the first satellite SAT1 or an indicator (e.g., PCI) of a cell served by the third eNodeB onboard the third satellite SAT3, the method proceeds to step 608. 【0253】 In step 612 (option C), the UE may determine whether the UE has received a paging message, the paging message including an indication that the UE context is available to a third eNodeB onboard a third satellite SAT3. 【0254】 If the UE determines that it has received a paging message and the paging message includes an indication that the UE context is available to a third eNodeB onboard a third satellite SAT3, the method proceeds to step 606. 【0255】 If the UE can determine that it did not receive the paging message, or if the paging message does not include an indication that the UE context is available to a third eNodeB onboard a third satellite SAT3, the method proceeds to step 608. 【0256】 In step 614 (option D), the UE may determine whether the UE received a paging message from a third eNodeB onboard a third satellite, SAT3. 【0257】 If the UE can determine that it has received a paging message from a third eNodeB onboard a third satellite SAT3, the method proceeds to step 606. 【0258】 If the UE can determine that it did not receive a paging message from a third eNodeB onboard a third satellite SAT3, the method proceeds to step 608. 【0259】 In step 606, the UE may attempt to resume the RRC connection via a third eNodeB onboard the third satellite SAT3. For example, the UE may send an RRC connection resume message to the third eNodeB onboard the third satellite SAT3. The RRC connection resume message may include a resume ID. 【0260】 In step 616, the UE may determine whether the RRC connection is resumed via a third eNodeB onboard the third satellite SAT3. For example, the UE may determine whether an RRC connection resumed complete message is received from the third eNodeB onboard the third satellite SAT3. 【0261】 If the RRC connection is resumed via a third eNodeB on board a third satellite SAT3, the method proceeds to 618. 【0262】 If the RRC connection was not resumed via the third eNodeB on board the third satellite SAT3, the method proceeds to 620. 【0263】 In step 618, an RRC connection is established via a third eNodeB onboard a third satellite, SAT3. 【0264】 In step 620, the UE may store the resumption ID for later use (e.g., may again attempt to relaunch the RRC connection via the third eNodeB onboard the third satellite SAT3). The method proceeds to step 608. 【0265】 In step 608, the UE may attempt to set up a new RRC connection with a third eNodeB onboard the third satellite SAT3. For example, the UE may send an RRC connection setup message to the third eNodeB onboard the third satellite SAT3. The RRC connection setup message does not include a resumption ID. 【0266】 7 illustrates a block diagram of a method for attempting to resume network connectivity via a base station on a satellite. The method may be performed by an apparatus, such as a user equipment. 【0267】 In step 700, the device may discontinue network connectivity via a first base station onboard a first vehicle. 【0268】 In step 702, the device may determine that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0269】 In step 704, the device may attempt to re-establish network connectivity via a second base station onboard a second vehicle. 【0270】 The second base station on the second vehicle may or may not be connected to the network. Different scenarios can be considered when attempting to resume network connectivity via the second base station on the second vehicle. 【0271】 In this scenario, a second base station may be connected to the network and may not have previously received and stored device context from the first base station. The second base station may now receive and store the device context from the first base station. Thus, the device context may be available to the second base station. Resumption of network connection via the second base station may be successful. 【0272】 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. The second base station may successfully resume network connectivity. 【0273】 In another scenario, the second base station may not be connected to the network or 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. Resumption of the network connection through the second base station may be successful. 【0274】 In another scenario, the second base station may not be connected to the network, or may 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. Resumption of the network connection through the second base station may not be successful. 【0275】 The apparatus may receive a network connection release message from a first base station onboard the first vehicle. Attempting to resume the network connection via a second base station onboard the second vehicle may include sending a network connection resume message to the second base station onboard the second vehicle. 【0276】 The network connection release message may include an identifier associated with the device context. The network connection resume message may include an identifier associated with the device context. 【0277】 The apparatus may receive a network connection resume complete message from a second base station onboard a second vehicle. 【0278】 The device may detect a failure to receive a network connection resume complete message from a second base station onboard the second vehicle. The device may store an identifier associated with the device context on the device. 【0279】 The device may later retransmit a network connection resume message including the identifier associated with the device context to a second base station on a second vehicle. 【0280】 The identifier may be stored with at least one of a time parameter indicating how long the identifier is stored on the device before removing the identifier from the device, a maximum number of attempts parameter indicating the maximum number of times the device will subsequently retransmit to a second base station mounted on a second vehicle, a network connection resume message including the identifier before removing the identifier from the device, or a maximum number of identifiers parameter indicating the maximum number of identifiers the device will store. 【0281】 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. 【0282】 The apparatus may detect a failure to receive a network connection setup complete message from a second base station onboard the second vehicle when the second base station onboard the second vehicle is not connected to the network. 【0283】 The apparatus may detect a failure to receive a network connection setup complete message from a second base station onboard a second vehicle. The apparatus may determine that a device context stored on a first base station onboard a first vehicle is expected to be available to a third base station onboard a third vehicle. The apparatus may transmit a network connection resume message to the third base station onboard the third vehicle, the network connection resume message including an identifier associated with the device context. 【0284】 The apparatus may detect a failure to receive a network connection setup complete message from a second base station onboard a second vehicle. The apparatus may determine that a third base station onboard a third vehicle is expected to be connected to the network. The apparatus may transmit a network connection setup message to the third base station onboard the third vehicle that does not include an identifier associated with the apparatus context. 【0285】 Determining that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle may include determining that a device context transfer time has expired from a time when connection with the network was interrupted. 【0286】 The device context transfer time may be received by the device from a first base station onboard the first satellite or may be calculated by the device. 【0287】 Determining that the device context stored on the first base station onboard the first vehicle is expected to be available to the second base station onboard the second vehicle may include receiving, from the first base station onboard the first vehicle, an indication of the second base station onboard the second vehicle or an indication of a cell served by the second base station onboard the second vehicle. 【0288】 The indication may indicate that device context stored on a first base station mounted on a first vehicle is expected to be available to a second base station mounted on a second vehicle. 【0289】 The network connection release message may include at least one of a device context transfer time, an indicator of a second base station mounted on the second vehicle, or an indicator of a cell served by the second base station mounted on the second vehicle. 【0290】 Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle may include receiving a paging message from the second base station mounted on the second vehicle. 【0291】 The paging message may include at least one of an indication that the device context is available to a second base station onboard the second vehicle or an indication that the second base station onboard the second vehicle expects the device to resume network connectivity via the second base station onboard the second vehicle. 【0292】 The device may determine that the device is moving out of coverage or into coverage of a first base station mounted on the first vehicle. The device may transmit an indication to the first base station mounted on the first vehicle or to a second base station mounted on the second vehicle that the device is moving out of coverage or into coverage of the first base station mounted on the first vehicle. 【0293】 The device may determine that the device is moving within or out of coverage of a second base station mounted on a second vehicle. 【0294】 The device may determine that the device has high priority data. The device may attempt to set up a network connection via a second base station onboard the second vehicle without first attempting to reinstate the network connection via the second base station onboard the second vehicle. 【0295】 The first vehicle, the second vehicle, and / or the third vehicle may be a satellite, a drone, or a car. 【0296】 The first vehicle, the second vehicle, and / or the third vehicle may be stations that may have intermittent connectivity with the network. 【0297】 FIG. 8 shows a schematic representation of a non-volatile memory medium that stores instructions and / or parameters that, when executed by a processor, enable the processor to perform one or more of the steps of the method of FIG. 【0298】 Although exemplary embodiments have been described above, it should be noted that there are several variations and modifications that can be made to the disclosed solution without departing from the scope of the present invention. 【0299】 Although the above concepts are discussed in the context of EPS (i.e., LTE), it should be understood that one or more of these concepts may be applied to other cellular systems, particularly 5GS or next generation systems. 【0300】 Although the above concepts are discussed in the context of a BS onboard a satellite, it should be understood that one or more of these concepts may be applied to a BS onboard other vehicles that provide intermittent CN connectivity, such as a drone, a car, or other. 【0301】 Thus, embodiments may vary within the scope of the appended claims. In general, some embodiments may be implemented in hardware or special-purpose 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 that may be executed by a controller, microprocessor, or other computing device, but the embodiments are not limited thereto. While various embodiments may be shown or described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, by way of non-limiting example, hardware, software, firmware, special-purpose circuits or logic, general-purpose hardware or controller, or other computing device, or some combination thereof. 【0302】 The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the participating entities, or by hardware, or by a combination of software and hardware. Furthermore, in this regard, it should be noted that any procedure, such as that shown in Figure 8, may represent program steps or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. Software may be stored on physical media, such as memory chips or blocks embodied within a processor, magnetic media, such as hard disks or floppy disks, and optical media, such as DVDs and their data variants, CDs, and the like. 【0303】 The memory may be of any type suitable for the local technology 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 and removable memory, etc. The data processor may be of any type suitable for the local technology environment and may include, by way of non-limiting examples, one or more of 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. 【0304】 Alternatively or additionally, some embodiments may be implemented using circuitry that may be configured to perform one or more of the functions and / or method steps described above, and that may be provided in a base station and / or a communications device. 【0305】 The term "circuitry" as used in this application may refer to one or more, or all, of the following: (a) Hardware-only circuit implementations (e.g., implementations using only analog and / or digital circuitry) (b) a combination of hardware circuitry and software, e.g. (i) a combination of analog and / or digital hardware circuitry and software / firmware; (ii) Any portion of hardware processors with software (including digital signal processors), software, and memory that cooperate to cause an apparatus, such as a communications device or base station, to perform the various functions described above. (c) a processor, such as a microprocessor or part of a microprocessor, that requires hardware circuitry and / or software (e.g., firmware) to operate, but the software may be absent when not necessary for operation; 【0306】 This definition of circuit applies to all uses of this term in this application, including in any claims. As a further example, the term circuit as used herein may also encompass a simple hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, as well as its (or their) accompanying software and / or firmware implementations. The term circuit also encompasses, for example, integrated devices. 【0307】 The foregoing description has provided a complete and informative description of several embodiments by way of illustrative and non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in light of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings are intended to still fall within the scope defined in the appended claims.

Claims

[Claim 1] Interrupting the network connection via the first base station mounted on the first vehicle, Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle, Attempting to resume the network connection via the second base station mounted on the second vehicle. A device equipped with means for that purpose. [Claim 2] The system includes means for receiving a network connection release message from the first base station mounted on the first vehicle, Attempting to resume the network connection via the second base station mounted on the second vehicle, The apparatus according to claim 1, comprising transmitting a network connection resumption message to the second base station mounted on the second vehicle. [Claim 3] The network connection release message includes an identifier associated with the device context, The apparatus according to claim 2, wherein the network connection resumption message includes the identifier associated with the apparatus context. [Claim 4] The apparatus according to claim 2, further comprising means for receiving a network connection resumption completion message from the second base station mounted on the second vehicle. [Claim 5] To detect failure to receive a network connection resumption completion message from the second base station mounted on the second vehicle, The identifier associated with the device context is stored on the device. The apparatus according to claim 3, comprising means for the purpose of [Claim 6] The apparatus according to claim 5, further comprising means for transmitting a network connection setup message, which does not include the identifier associated with the apparatus context, to the second base station mounted on the second vehicle. [Claim 7] Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle is: The apparatus according to claim 2, comprising determining that the device context transfer time has expired since the time the network connection was interrupted. [Claim 8] Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle is: The apparatus according to claim 7, comprising receiving an indicator of a second base station mounted on a second vehicle, or an indicator of a cell serviced by the second base station mounted on the second vehicle, from the first base station mounted on the first vehicle. [Claim 9] The aforementioned network connection release message, The device context transfer time, The indicator of the second base station mounted on the second vehicle, or The indicator of the cell serviced by the second base station mounted on the second vehicle, The apparatus according to claim 8, comprising at least one of the following. [Claim 10] Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle is: The apparatus according to claim 1, comprising receiving a paging message from the second base station mounted on the second vehicle. [Claim 11] The aforementioned paging message, An indicator showing that the device context is available to the second base station mounted on the second vehicle, or An indicator that the second base station mounted on the second vehicle anticipates the device will resume the network connection via the second base station mounted on the second vehicle. The apparatus according to claim 10, comprising at least one of the following. [Claim 12] Determining that the device has moved outside the coverage of the first base station mounted on the first vehicle, or that the first base station mounted on the first vehicle has moved so that the device is outside its coverage, Transmitting an indicator to the first base station mounted on the first vehicle, or to the second base station mounted on the second vehicle, that the device has moved outside the coverage of the first base station mounted on the first vehicle, or that the first base station mounted on the first vehicle has moved so that the device is outside its coverage. The apparatus according to any one of claims 1 to 11, comprising means for the purpose of [Claim 13] The apparatus according to claim 12, further comprising means for determining that the apparatus is moving within the coverage of the second base station mounted on the second vehicle, or that the second base station mounted on the second vehicle is moving so that the apparatus is within its coverage. [Claim 14] It is a method, Interrupting the network connection via the first base station mounted on the first vehicle, Determining that the device context stored on the first base station mounted on the first vehicle is expected to be available to the second base station mounted on the second vehicle, Attempting to resume the network connection via the second base station mounted on the second vehicle. Methods that include... [Claim 15] A computer program that, when executed on one or more processors, includes computer-executable instructions that perform the steps of the method according to claim 14.

Images