User device connection release

Abstract

A method includes receiving, by a user device having a connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receiving, from a third access node, restriction information of the third access node for accessing the network, and determining to release the connection based on the restriction information of the third access node.

Description

[0001] USER DEVICE CONNECTION RELEASE

[0002] TECHNICAL FIELD

[0003] [1] This description relates to wireless communications.

[0004] BACKGROUND

[0005] [2] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.

[0006] [3] An example of a cellular communication system is an architecture that is being standardized by the 3rd Generation Partnership Project (3GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. EUTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell.

[0007] In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LTE has included a number of improvements or developments. Aspects of LTE are also continuing to improve.

[0008] [4] 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G and 4G wireless networks. In addition, 5G is also targeted at the new emerging use cases in addition to mobile broadband A goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security. 5G NR may also scale to efficiently connect the massive Internet of Things (loT) and may offer new types of mission-critical services. For example, ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency. 6G and other networks are also being developed.

[0009] SUMMARY

[0010] [5] An apparatus may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receive, from a third access node, an identifier of the third access node, determine based on at least one of the timing information, or the identifier of the third access node being different from the identifier of the second access node to: wait until the second access node becomes available, or send a second message to the third access node indicating a request for assistance information for the first connection or for a second connection to the network via the third access node.

[0011] [6] A method may include: receiving, by a user device having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receiving, from a third access node, an identifier of the third access node, and determining based on at least one of the timing information, or the identifier of the third access node being different from the identifier of the second access node to wait until the second access node becomes available, or send a second message to the third access node indicating a request for assistance information for the first connection or for a second connection to the network via the third access node.

[0012] [7] An apparatus may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receive, from a third access node, an identifier of the third access node, send to the third access node, a second message indicating a request for a resume of the first connection via the third access node, and receive from the third access node, a third message including assistance information indicating at least one of: whether to resume the first connection, to wait for the second access node to resume the first connection, to release the first connection, or to establish a second connection via the third access node.

[0013] [8] A method may include: receiving, by a user device having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receiving, from a third access node, an identifier of the third access node, sending, to the third access node, a second message indicating a request for a resume of the first connection via the third access node, and receiving from the third access node, a third message including assistance information indicating at least one of: whether to resume the first connection, to wait for the second access node to resume the first connection, to release the first connection, or to establish a second connection via the third access node. [9] An apparatus may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receive from a third access node, restriction information of the third access node for accessing the network, and determine to release the connection based on the restriction information of the third access node.

[0014]

[0010] A method may include: receiving, by a user device having a connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receiving, from a third access node, restriction information of the third access node for accessing the network, and determining to release the connection based on the restriction information of the third access node.

[0015]

[0011] Other example embodiments are provided or described for each of the example methods, including: means for performing any of the example methods; a non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform any of the example methods; and an apparatus including at least one processor, and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform any of the example methods.

[0016]

[0012] The details of one or more examples of embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

[0017] BRIEF DESCRIPTION OF THE DRAWINGS

[0018]

[0013] FIG. l is a block diagram of a wireless network.

[0019]

[0014] FIG. 2A is a diagram illustrating an operation of a satellite system or network under a default or normal satellite operation mode.

[0020]

[0015] FIG. 2B is a diagram illustrating an operation of a satellite system based on the store and forward (S&F) satellite operation mode.

[0021]

[0016] FIG. 3 is a diagram illustrating an example operation of a satellite in S&F mode.

[0022]

[0017] FIG. 4 is a diagram illustrating an aspect of an example embodiment.

[0023]

[0018] FIG. 5A is a diagram illustrating an operation of a satellite system based on an aspect of an example embodiment.

[0024]

[0019] FIG. 5B is a diagram illustrating an operation of a satellite system based on an aspect of an example embodiment.

[0025]

[0020] FIG. 6 is a flow chart illustrating operation of an apparatus (e.g., which may be a UE or user device, or other apparatus) according to an example embodiment.

[0026]

[0021] FIG. 7 is a flow chart illustrating operation of an apparatus (e g., which may be a UE or user device, or other apparatus) according to an example embodiment.

[0027]

[0022] FIG. 8 is a flow chart illustrating operation of an apparatus (e g., which may be a UE or user device, or other apparatus) according to an example embodiment.

[0028]

[0023] FIG. 9 is a block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node).

[0029] DETAILED DESCRIPTION

[0030]

[0024] It shall be understood that although the terms “first,” “second,” ... , etc. in front of noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0031]

[0025] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.

[0032]

[0026] FIG. 1 is a block diagram of a wireless network 130. In the wireless network 130 of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a gNB or a network node. The terms user device and user equipment (UE) may be used interchangeably. A BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as e.g., such as a centralized unit (CU) and / or a distributed unit (DU) in the case of a split BS or split gNB. At least part of the functionalities of a BS (e.g., access point (AP), base station (BS) or (e)Node B (eNB), gNB, RAN node) may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface 151. This is merely one simple example of a wireless network, and others may be used.

[0033]

[0027] A base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network. A BS (or a RAN node) may be or may include

[0034] (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a centralized unit (CU) and / or a distributed unit (DU) in the case of a split BS or split gNB), or other network node.

[0035]

[0028] Some functionalities of the communication network may be carried out, at least partly, in a central / centralized unit, CU, (e.g., server, host or node) operationally coupled to distributed unit, DU, (e.g., a radio head / node). Thus, 5G networks architecture may be based on a so-called CU-DU split. The gNB-CU (central node) may control a plurality of spatially separated gNB-DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some embodiments, however, the gNB-DUs (also called DU) may comprise e.g., a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU (also called a CU) may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too.

[0036]

[0029] According to an illustrative example, a BS node (e.g., BS, eNB, gNB, CU / DU, .. .) or a radio access network (RAN) may be part of a mobile telecommunication system. A RAN (radio access network) may include one or more BSs or RAN nodes that implement a radio access technology, e.g., to allow one or more UEs to have access to a network or core network (CN). Thus, for example, the RAN (RAN nodes, such as BSs or gNBs) may reside between one or more user devices or UEs and a core network. According to an example embodiment, each RAN node (e.g., BS, eNB, gNB, CU / DU, . . .) or BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node. Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and / or receiving data from one or more of the UEs. For example, after establishing a connection to a UE, a RAN node or network node (e.g., BS, eNB, gNB, CU / DU, . ..) may forward data to the UE that is received from a network or the core network, and / or forward data received from the UE to the network or core network. RAN nodes or network nodes (e.g., BS, eNB, gNB, CU / DU, . . .) may perform a wide variety of other wireless functions or services, e.g., such as broadcasting control information (e.g., such as system information or on-demand system information) to UEs, paging UEs when there is data to be delivered to the UE, assisting in handover of a UE between cells, scheduling of resources for uplink data transmission from the UE(s) and downlink data transmission to UE(s), sending control information to configure one or more UEs, and the like. These are a few examples of one or more functions that a RAN node or BS may perform.

[0037]

[0030] A user device or user node (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc ), a laptop and / or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, and a multimedia device, as examples, or any other wireless device. It should be appreciated that a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. Also, a user node may include a user equipment (UE), a user device, a user terminal, a mobile terminal, a mobile station, a mobile node, a subscriber device, a subscriber node, a subscriber terminal, or other user node. For example, a user node may be used for wireless communications with one or more network nodes (e.g., gNB, eNB, BS, AP, CU, DU, CU / DU) and / or with one or more other user nodes, regardless of the technology or radio access technology (RAT). In LTE (as an illustrative example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility / handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks. Other types of wireless networks, such as 5G (which may be referred to as New Radio (NR)) may also include a core network.

[0038]

[0031] In addition, the techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types. New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), Internet of Things (loT), and / or narrowband loT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC). Many of these new 5G (NR) - related applications may require generally higher performance than previous wireless networks.

[0039]

[0032] loT may refer to an ever-growing group of obj ects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices. For example, many sensor type applications or devices may monitor a physical condition or a status and may send a report to a server or other network device, e.g., when an event occurs. Machine Type Communications (MTC, or Machine to Machine communications) may, for example, be characterized by fully automatic data generation, exchange, processing and actuation among intelligent machines, with or without intervention of humans. Enhanced mobile broadband (eMBB) may support much higher data rates than currently available in LTE.

[0040]

[0033] Ultra-reliable and low-latency communications (URLLC) is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems. This enables emerging new applications and services, such as industrial automations, autonomous driving, vehicular safety, e-health services, and so on. 3 GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10-5 and up to 1 ms U-Plane (user / data plane) latency, by way of illustrative example. Thus, for example, URLLC user devices / UEs may require a significantly lower block error rate than other types of user devices / UEs as well as low latency (with or without requirement for simultaneous high reliability). Thus, for example, a URLLC UE (or URLLC application on a UE) may require much shorter latency, as compared to an eMBB UE (or an eMBB application running on a UE).

[0041]

[0034] The techniques described herein may be applied to a wide variety of wireless technologies or wireless networks, such as 5G (New Radio (NR)), cmWave, and / or mmWave band networks, loT, MTC, eMTC, eMBB, URLLC, 6G, etc., or any other wireless network or wireless technology. These example networks, technologies or data service types are provided only as illustrative examples.

[0042]

[0035] A user device (or UE) may measure various signals and may transmit one or more measurement reports to the network. For example, a UE may measure reference signals received from one or more network nodes (e.g., gNBs or DUs), including channel state information-reference signals (CSLRSs) and / or synchronization signal block (SSB) reference signals, demodulation references signals, and / or other reference signals. Based on received reference signals, the UE may measure various signal parameters, e.g., such as reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), received signal strength indicator (RSSI), or other signal parameter.

[0043]

[0036] The PHY (physical) layer may refer to layer 1 (LI) and MAC (media access control) may refer to layer 2 (L2). RSRP, RSRQ, SINR and RSSI are signal quantities measured at layer 1 (LI). The UE may send LI measurement reports (e.g., CSLRS reports, which include measurements of one or more signal parameters for one or more cells) to a gNB, source DU or serving cell. These LI measurement reports may be sent periodically, for example, or aperiodically. L1 / L2 measurement reports may include no averaging or filtering of measurement values or may include less averaging or filtering than what is performed for L3 measurement reports. LI (or L1 / L2) measurement reports may be transmitted by a UE to a serving network node or source DU and may cause the network node to trigger or initiate a L1 / L2 triggered mobility (LTM) handover of the UE to another cell. LI measurements (e.g., RSRP RSRQ, RSSI) may be provided or reported periodically to the DU (MAC / PHY).

[0044]

[0037] In an example embodiment, transition of a UE from a power-saving state where data is not exchanged (idle state) to a connected state optimized for data transmissions (connected state) may cause frequent signalling event(s) in 3 GPP networks. Examples of signalling events may include RRC connection establishment, RRC release, paging messages, and / or the like. The transition may include an extensive signalling sequence between the device and the network, and between network nodes, which may lead to latency issues and high battery consumption.

[0045]

[0038] In an example, in the loT, MTC, and / or the like scenarios, the amount of data that UE may exchange with the network may be small, infrequent and not urgent enough to justify the high battery consumption required to handle all the signalling involved in the idle-to- connected transition. To address this issue, methods may be employed to provide the transition enhancements such as suspend and resume. In the suspend procedure, the UE may store its radio configuration and security parameters before it transitions from connected state to idle state. Then, when the UE needs to connect to the network again (due to some uplink (UL) data being available to transmit), the UE may trigger the resume procedure. The resume procedure may include restoring the previously stored configuration and resuming the connection without the need for extensive signalling with the core network (CN) or having to reestablish security. In an example, a resume procedure for resuming a connection may include: sending by the UE to the access node a RRC resume request including a resume identifier, receiving from the access node a RRC resume message and sending by the UE to the access node a RRC resume complete message.

[0046]

[0039] In an example embodiment, the UE may transition to a RRC inactive state. The main principle of the inactive state is that the UE is able to return to the connected state as quickly and efficiently as possible. When the UE transitions to inactive state, both the UE and the RAN node may store all the information necessary to quickly resume the connection. The message that causes the UE to transition to inactive state may include a set of parameters employed for inactive state operation, such as a RAN notification area (RNA) within which the UE may be allowed to move without notifying the network.

[0047]

[0040] In an example, the resume procedure may include the following. An inactive state or idle state UE may initiate a resume procedure for example when there is a need to transmit or receive data or signalling. In this case, the UE may transmit a RRC resume request that may include the UE identifier (provided by the serving node to identify the UE’s configuration repository), a resume ID, and / or a security token to verify the legitimacy of the resume request.

[0048]

[0041] In an example embodiment, the UE may resume a connection via a cell served by a different RAN node or a target node., In an example, context information of a user device or UE may include a user device resume context information, a UE resume context information. In an example, the UE or user device resume context information may include at least one of a resume identifier of the user device, an identifier of a mobility management entity serving the user device, and / or the like.

[0049]

[0042] Therefore, since many of the loT, cellular loT (CIoT), MTC, and / or the like use cases involve transmission of delay tolerant and small data sizes, deployment of a satellite based system to support these use cases may be feasible. In addition, since delay tolerant data communication is not time sensitive, it may be possible to use satellite systems that operate in a store and forward (S&F) mode. The description of satellite systems and differences between normal mode of operation and the S&F mode are described in the following.

[0050]

[0043] A satellite may be a space-borne vehicle that may provide a bent pipe payload or a regenerative payload telecommunication transmitter. The bent pipe method may include a satellite communications system that transmits to an earth station the same signal it receives from another earth station. The regenerative payload may actively enhance signals, which may include error correction, modulation / demodulation, and amplification. The satellite may, for example, be placed into a low-earth orbit (LEO) at an altitude between 300 km to 1500 km, a medium-earth orbit (MEO) at an altitude between 8000 to 20000 km, or a geostationary satellite earth orbit (GEO) at 35,786 km altitude. A satellite network may be a network or network segment that may employ a space-borne vehicle to provide a transmission equipment relay node or a base station. While a terrestrial network is a network located on the surface of the earth, a non-terrestrial network (NTN) may be a network which may employ a satellite as an access network, a backhaul interface network, or both. The NTN architecture may include a wireless device, a satellite, an NTN gateway, a base station, a core network, and a data network. The NTN gateway may connect to a base station on the ground. The wireless device may transmit and receive via the satellite and the satellite may implement frequency conversion and radio frequency amplification in both the uplink and downlink directions. The satellite may correspond to an analogue RF repeater that repeats the Uu radio interface from a service link (between the satellite and the UE) to a feeder link (between the NTN gateway and the satellite, or between the satellite and a network entity), and vice-versa.

[0051]

[0044] In an example, when the satellite is deployed based on the regenerative satellite model, the NTN architecture may include a wireless device, a satellite that may include an eNB, a gNB, an access node or a base station (which may be referred to as a satellite access node, satellite base station, satellite-based eNB, or satellite-based gNB), an NTN gateway, a core network, and / or the like. The satellite may regenerate signals received from the earth (e.g. from a wireless device or from an NTN gateway). In an example, the satellite may behave as an access node or a base station, or may include a base station, eNB, or gNB. In some cases, or during certain periods of time, only one of the service link or feeder link may be operational.

[0052]

[0045] In an example, a satellite may include a low earth orbit (LEO) satellite with an altitude ranging from 300 km to 1500 km above the surface of the earth. An orbital period of the LEO may be between about 84 minutes and 127 minutes. In an example, mean orbital velocity needed to maintain a stable LEO may be 7.8 km / s and may be reduced with increased orbital altitude. In an example, mean orbital velocity for circular orbit at an altitude of 200 km may be 7.79 km / s. In an example, mean orbital velocity for circular orbit at an altitude of 1500 km may be 7.12 km / s. In another example, a geostationary satellite earth orbit (GEO) satellite may orbit the earth with an altitude 35,786 km above the surface of the earth. The GEO may be established at an altitude very close to 35,786 km (22,236 mi) and directly above the equator. This may equate to an orbital velocity of 3.07 km / s (1.91 mi / s) and an orbital period of 1,436 minutes, which may equate to almost one sidereal day (23.934461223 hours). From the perspective of a given point on the surface of the earth, the position of the LEO satellite may change, while the position of the GEO may not move.

[0053]

[0046] In an example embodiment, a store and forward (S&F) satellite operation may include the following: The S&F satellite operation may be a mode of operation of a 5G (e g., 3GPP, 3G, 4G, and / or the like) system with satellite-access where the 5G system may provide some level of service (in storing and forwarding the data) when satellite connectivity to the ground network (the feeder link) is intermittently or temporarily unavailable, e.g., to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment.

[0054]

[0047] FIG. 2A is a diagram illustrating an operation of a satellite system or network under a default or normal satellite mode of operation. Signalling and data traffic exchange between a UE with satellite access and the remote ground network may require the service link and the feeder links to be active simultaneously, so that, at the time that the UE interacts over the service link with the satellite, there is a continuous end-to-end connectivity path between the UE, the satellite and the ground network.

[0055]

[0048] FIG. 2B is a diagram illustrating an operation of a satellite system based on the satellite in S&F mode of operation. An example of the satellite in S&F mode of operation is illustrated in FIG. 2B, in contrast to what may be considered a normal or default satellite operation of a 5G system with satellite access. In an example, under the S&F mode of operation, the end-to-end exchange of signalling / data traffic may be handled as a combination of two steps not concurrent in time (Step A and Step B in FIG. 2B). In step A, the UE may be in communication with an access node or base station provided on the satellite (satellite access node) via the service link, but the feeder link (between the satellite and ground network) is not provided. Later, at step B, the feeder link is established between the satellite and the ground network. In Step A, signalling / data exchange between the UE and the satellite may take place, without the satellite being simultaneously connected to the ground network (e g., the satellite is able to operate the service link without an active feeder link connection). In Step B, connectivity between the satellite (e g., satellite access node) and the ground network is now established so that communication between the satellite and the ground network may take place. Therefore, the satellite may move from being connected to the UE in step A to being connected to the ground network in step B.

[0056]

[0049] In other words, the S&F mode of operation may provide communication service (e.g., in storing and forwarding of information) to a UE in periods of time and / or geographical areas in which a serving satellite (serving access node or serving satellite base station) is not simultaneously connected to the ground network via feeder link or intersatellite link (ISL). For the case of uplink (UL), "store" may refer to on-board storage of UL information received from the UE and "forward" may refer to forwarding of stored UL information to the ground network. For the case of downlink (DL), "store" may refer to onboard storage of DL information received from the ground network and "forward" may refer to forwarding of stored DL information to the UE

[0057]

[0050] Therefore, in the S&F mode of operation, the 5G system may provide mobile originate (MO) communication service (e.g., for UL / uplink data transmitted by the UE) for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment (or ground network). In addition, the 5G system may provide mobile terminating (MT) communication service for UEs (for DL / downlink data transmitted by the ground network to the UE) via a satellite having a feeder link connection and is expected to provide coverage in the future to UE(s). As a result, delay tolerant and non-real time services may be served via a satellite in the S&F mode of operation.

[0058]

[0051] In an example deployment, an access node (e.g., in the S&F mode of operation), such as an eNB or a gNB, may include an MME co-located with the access node. Therefore, the deployment of MME on-board (e.g., MME that is on-board the satellite, or co-located with the base station) may provide basic connection management procedures. The MME onboard may execute all the procedures (e.g., mobility-related procedures) with the UE which may not need interaction with other core network nodes on the ground when the service link is available. Whenever a procedure needs an interaction with a core network node on the ground, the MME on-board may store the respective message when feeder link is not available and may continue the procedure when feeder link becomes available. In an example, non-access stratum (NAS) signalling messages may be stored at MME on the ground network and / or at a packet data network (PDN) gateway (P-GW) on the ground network when service link is available and feeder link is not available. The NAS signalling messages may be delivered to the ground network when the feeder link becomes available.

[0059]

[0052] FIG. 3 is a diagram illustrating an example operation of a satellite communication system in the S&F mode of operation. The S&F mode of operation may rely on the regenerative architecture where a base station or a RAN node (e.g., eNB or gNB) may be placed in satellite e.g., being co-located or on-board the satellite. In the S&F mode of operation, a management entity such as a mobility management entity (MME) (or access and mobility management function (AMF) for 5G system type of deployment) may be on-board or co-located with the satellite and may be responsible to provide management functionality for the S&F mode of operation. The MME in satellite (e.g., the MME on-board) may be represented as MME-NT (non-terrestrial) as depicted in FIG. 3. For example, at time T1 (for example between 10:00 AM-10:20 AM) and T2 (for example, between 10:40 AM-11 :00 AM), the satellites (310, 312) may have ground station coverage when hovering over Rennes and Orleans but not when crossing Le Mans. At time Tl, the black satellite 412 may cover Le Mans and the white satellite 310 may provide coverage to Rennes. At time T2, the black satellite 312 may be at Orleans and white satellite 310 may be covering Le Mans. At time T3, the white satellite 310 may synchronize with the MME-NT at Orleans.

[0060]

[0053] In an example, in existing technologies, when the satellite or NTN in the S&F mode of operation is employed for transmission and reception of UL and DL data packets, the UE may send an UL data packet with an expectation of receiving a DL data packet in response to the UL data packet. A problem may arise when the UL data packet is transmitted via a serving access node or a first access node (e.g., SAT1), where SAT1 has left or may leave the area and the service link to the UE becomes unavailable. The UE may (be configured to) release or suspend the connection. In an example, the UE may suspend the connection by storing context information of the UE. In an example, the UE may resume the connection by restoring the context information of the UE. In an example, the UE may resume the connection via a different access node that may not have the context information of the UE to properly resume the connection because the different access node (e.g., SAT3) did not store the context information of the UE. In an example, context information of the UE may include a UE resume context information or a user device resume context information. In an example, the UE resume context information may include at least one of a resume identifier of the UE, an identifier of a mobility management entity serving the UE, and / or the like. In an example, the UE may be the user device. As a result, degradation to service continuity may occur and data transmission and / or reception may be interrupted.

[0061]

[0054] Therefore, it may be desirable to provide a technique or mechanism in which the S&F satellite or network provides assistance information to the UE.

[0062]

[0055] SAT1 may refer to satellite 1 or first satellite. SAT2 may refer to satellite 2 or second satellite. SAT3 may refer to satellite 3 or third satellite. SAT may generally refer to satellite. Satellite herein may refer to a satellite access node or satellite base station capable of providing cellular service to one or more user devices, such as on or more UEs. For instance, satellite access node may be an eNB or a gNB.

[0063]

[0056] In other words, the UE may send UL a control plane (CP) message or UP (user plane) data, referred to as UL message, to the access node in the S&F mode of operation. Therefore, when service link is available, the UE may not receive the DL response or acknowledgement from the core network (CN) side, referred to as DL message, to complete the corresponding network transaction immediately, because the feeder link between the same access node and the ground station is not available simultaneously with the service link. In an example a network transaction may include transmission of UL data packets to the network and receiving DL data packets in response to the transmission of the UL data packets. In an example, the UL data packets and the DL data packets may be related to each other. In an example, an event of subsequent transmission ofUL data packets and reception of DL data packets may be referred to as a transaction and may be identified by a transaction identifier or an identifier of a transaction (transaction ID). Thus, the UE that has successfully transmitted the UL message to SAT1 may be suspended and released into RRC idle (or inactive) by a first access node (SAT1) while waiting for or expecting the DL message to complete the network transaction. The first access node (SAT1) may configure the UE with the UE resume context information when suspending the UE, also referred to as suspend configuration or considered as part of suspend configuration provided to the UE by the first access node. The UE resume context information may include radio access contexts and information of one or more target access nodes (SATs), denoted as a second access node (SAT2) or a plurality of second access nodes. In an example, the UE may be expected to resume the connection via the second access node to receive the DL message that is expected to be received from the CN side. In another example, the UE may also be expected to resume the connection via the second access node to transmit a new UL message that may include UL data packets while expecting to receive the DL message. Therefore, the first access node and the CN need to ensure that the second access node (SAT2) has the UE context information to resume the connection of the UE in order to transmit the DL message to the UE. In an example, due to lack of accurate information of UE mobility, SAT1 (or CN) may provide inaccurate information about the next access node, e.g.,, the second access node (SAT2) that is expected to provide connectivity to the UE. As a result, the UE may resume the connection via a third access node (SAT3) that was not in the list that included the second access node or the plurality of the second access nodes. However, SAT3 may not have the context information of the UE in order to successfully resume the connection. In an example, resuming a connection may include sending by the UE to the access node a RRC resume request including a resume identifier, receiving from the access node a RRC resume message and sending by the UE to the access node a RRC resume complete message. In an example, context information of the UE may include a UE resume context information or a user device resume context information. In an example, the UE resume context information may include at least one of a resume identifier of the UE, an identifier of a mobility management entity serving the UE, and / or the like. As a result, service interruption or loss of data may occur because it is not clear how the UE may behave and what kinds of network control or assistance may be provided to the UE for a simple and efficient support for service continuity of the UE in NTN S&F (or an access node in the S&F mode of operation).

[0064]

[0057] Thus, according to an example embodiment, the UE may request assistance information from the network (SAT3) and the network (SAT3) may provide instructions to the UE. Accordingly, an example embodiment is directed to enhance the performance of the system by improvements in signalling procedures between the UE and the network e g., an access node (in the S&F mode of operation). After the UE receives a first message for a suspension of a connection via the first access node from a first access node that includes information of a second access node, e g., a plurality of second access nodes to be expected for a resume of the connection, the UE may determine whether to resume the connection with the third access node when the service link of the third access node becomes available. For example, the UE may determine to wait for an access node of the plurality of the second access nodes to become available. In an example, the UE may request the third access node to provide assistance information on how the UE should proceed. In an example, when the UE receives the assistance information from the third access node, the UE may perform an action based on the received assistance information. In another example, the UE may receive restriction information associated with the first access node, and when the restriction information received from the third access node does not match the restriction information associated with the first access node, the UE may determine not to resume the connection and may determine to restart the data transmission or establish a new connection with the third access node. In an example, the UE may determine to release the connection. In an example, the UE may determine to suspend the connection. In an example, the UE may determine to keep the connection suspended or extend the suspension of the connection for a period of time..

[0065]

[0058] FIG. 4 is a diagram illustrating an aspect of an example embodiment. In an initial condition as indicated by step 0, the UE may suspend a connection (the first connection) via the first access node (SAT1). The UE may receive a first message from SAT1 that may include UE resume context information for the suspension of the connection. In an example, the UE resume context information may include at least one of a resume identifier of the UE, an identifier of a mobility management entity serving the UE, and / or the like. The first message may include the information of a second access node (e.g., a list or plurality of target access nodes) for resuming the connection to complete a pending data transmission. At step

[0066] 1, the UE may receive a SIB (system information block) message from the third access node (SAT3). In an example, the SAT3 may indicate (or provide an indication) in the SIB message whether SAT3 is able to provide assistance information to the UE. This means that the UE may employ the SIB message to take this indication into account when determining whether to request assistance information from the SAT3. In other words, the UE may determine whether to request assistance information from SAT3 based on the indication from SAT3 that indicates whether the SAT3 is able to provide assistance information. The indication may be provided by the SAT3, e.g., when the SAT3 has a connection (e.g., feeder link) with the ground network and / or may be expected to connect to the ground network within x time units wherein x is lower than a configured threshold. In an example embodiment, the indication may be associated with the support for the S&F mode by the SAT3. At step 2, the UE may determine or detect that the third access node (SAT3) is not in the list that was provided by the SAT1, e.g., not being in the list of the plurality of the target access nodes (SAT2). The UE may determine to request assistance information from the SAT3. In step 3, the UE may send to the SAT3, a RRC message such as a RRC connection establishment request message indicating a request to receive assistance information. In an alternative example implementation, the UE may send to the SAT3 a resume request to trigger the SAT3 to provide the assistance information. In an example, the assistance information may include at least one of an indication of whether to resume the first connection, an indication to delay resuming the first connection, e.g., to wait for the second access node to resume the first connection via the second access node (SAT2), an indication of whether to release the first connection, an indication of whether to establish a second connection via the third access node (SAT3). In an example, the assistance information may correspond to the S&F mode of operation.

[0067]

[0059] In an alternative example implementation, the request for the assistance information from the UE may be separated from (or provided via different message than) the RRC connection establishment request or resume request. For example, the UE may first set up a RRC connection with the SAT3 by transmitting a RRC connection establishment request with a new cause (e g., establishment cause) for assistance information request. Then the UE may provide (e.g., in a separate message) the request for assistance information and UE location report to SAT3 to request the assistance information. In an example, the assistance information may include at least one of an indication of whether to resume the first connection, an indication to delay resuming the first connection, e.g., to wait for the second access node to resume the first connection via the second access node (SAT2), an indication of whether to release the first connection, an indication of whether to establish a second connection via the third access node (SAT3). At step 4, the SAT3, may determine the assistance information for the UE. In an alternative example, in case the SAT3 includes the eNB and MME on-board (e.g., referred to as NT -MME), the eNB (SAT3 access node) may interact with NT -MME on SAT3 for the determination of the assistance information, provided that NT -MME has more information on the connected MME on the ground and other SAT(s) that may be added to or removed from the list of SAT2 for the UE, e.g., the list or plurality of target access nodes. In an example embodiment, the SAT3 may inform the MME on the ground about the assistance information provided to the UE. In an example, the MME may perform necessary release of a signalling connection for the UE according to the assistance information that instructs the UE to release the connection (the first connection). The signalling connection may include a non-access stratum (NAS) connection, or a connection between the UE and a node of the core network. For example, the MME may release a feeder link connection of the UE via the interface between the core network and the access node. In an example, the release of the feeder link may trigger an access network (AN) release procedure by an access node. In an example, the core network may determine to release a non-access stratum (NAS) connection of the UE with the network. In an example, the core network may determine to change a connection management (CM) state of the UE e.g., from CM-CONNECTED to CM-IDLE. In case the assistance information instructs the UE to resume the connection later to a target access node in the modified or updated list of target access nodes (SAT2) provided to the UE by SAT3, the MME may ensure that the resume context information of the UE and expected DL data packets or messages of the UE are provided to the target access nodes in the modified or updated list of target access nodes before the service link of these target access nodes becomes available for the UE to resume.

[0068]

[0060] The lower part of FIG. 4 includes two options, including option 1 (including steps 6-7) and option 2 (including steps 5 and 6) for examples. The example of option 1 corresponds to the case that the assistance information instructs the UE to release the connection (the first connection). The example of option 2 corresponds to the case that the assistance information instructs the UE to resume the connection later to a target access node in the modified or updated list of target access nodes (SAT2).

[0069]

[0061] In an example a network transaction may include transmission of UL data packet(s) to the network and receiving DL data packet(s) in response to the transmission of the UL data packet(s). In an example, the UL data packets and the DL data packets may be related to each other. In an example, an event of subsequent transmission of UL data packets and reception of DL data packets may be referred to as a transaction and may be identified by a transaction identifier or an identifier of a transaction (transaction ID). A pending network transaction may be an incomplete network transaction wherein the UL data packet is transmitted but the expected DL data packet is not received.

[0070]

[0062] At option 1, the UE terminates the pending network transaction and releases the UE resume context information, and then restarts the network transaction. This may also imply that the UE is instructed to release the connection (the first connection). With respect to FIG. 4, at step 5 in option 1, the UE may receive a RRC connection establishment message from the SAT3 that may include the assistance information instructing the UE to terminate the pending network transaction. At step 6 in option 1, the UE may release or terminate the pending network transaction and may release or remove the UE resume context information. At step 7 in option 1, the UE may restart the network transaction using the connection that has been established via SAT3 (the second connection).

[0071]

[0063] At option 2, the UE receives a connection release from SAT3, including the assistance information to resume the connection (the first connection) to SAT2 later. This means that the UE is suspended and released into idle (or inactive) state for a later resume. With respect to FIG. 4, at step 5 in option 2, the UE may receive a RRC connection release from the SAT3 that may include the assistance information instructing the UE to resume to SAT2 later (when the SAT2) becomes available. In an example, the RRC connection release may include an updated list or plurality of target access nodes (SAT2). In an example implementation, the UE may use a timer that is associated with the pending network transaction. The timer may be started from the time that the corresponding UL message was sent. Based on the timer, it may be determined whether the expected time of connecting the next SAT2 (satellite access node) has passed. At step 6 in option 2, the UE may determine to reset the timer associated with the pending network transaction. In another example, at step 6 in option 2, the UE may determine to extend the timer associated with the pending network transaction. In an example, at step 6 in option 2, the UE may determine to transition to a RRC idle mode or state for the suspension of the connection (the first connection).

[0072]

[0064] FIG. 5A is a diagram illustrating an operation of a satellite system based on an aspect of an example embodiment. The UE may have a first connection to a network via access node 1 (a first access node). In an example the UE may start a network transaction by sending an UL data packet to the access node 1. The UE may expect to receive a DL data packet in response to the UL data packet as part of the network transaction. In an example a network transaction may include transmission of UL data packets to the network and receiving DL data packets in response to the transmission of the UL data packets. In an example, the UL data packets and the DL data packets may be related to each other. In an example, an event of subsequent transmission of UL data packets and reception of DL data packets may be referred to as a transaction and may be identified by a transaction identifier or an identifier of a transaction (transaction ID). The access node 1 may suspend the connection before leaving the area of the UE. The access node 1 may send a first message to the UE. The first message may include at least one of an identifier of a second access node (access node 2) or timing information associated with an availability of the second access node (access node 2). The access node 1 may leave the area of the E and the service link between the UE and the access node 1 may become unavailable.

[0073]

[0065] FIG. 5B is a diagram illustrating an operation of a satellite system based on an aspect of an example embodiment. The access node 3 may cover the area of the UE and the access node 3 may send a broadcast message to the UE that may include an identifier of the access node 3 (e.g., a third access node). In an example, the UE may determine based on at least one of the timing information, or the identifier of the access node 3 (the third access node) being different from the identifier of the second access node (access node 2) to wait until the access node 2 becomes available. In another example, the UE may determine based on at least one of the timing information, or the identifier of the access node 3 (the third access node) being different from the identifier of the second access node (access node 2), to send a second message to the access node 3 indicating a request for assistance information for the first connection or for a second connection to the network via the access node 3. In an example, the assistance information may include at least one of an indication of whether to resume the first connection, an indication to delay resuming the first connection until the second access node becomes available, an indication of whether to release the first connection, an indication of whether to establish a second connection via the third access node (SAT3). In an example, the assistance information may correspond to the S&F mode of operation.

[0074]

[0066] In an example embodiment, the UE may detect that the UE is under coverage of SAT3 and that SAT3 is not in the list of SAT2 (e.g., the list or plurality of target access nodes) configured by SAT1 for an expected resume to receive the DL message. In an example, upon the detecting, the UE may determine to send a request to SAT3 for the assistance information (or instruction). In an example, the determination to send the request to SAT3 may be based on whether the UE determines to wait for a next SAT2 (e g., the next SAT (next satellite access node) in the configured list, e.g., the list or plurality of target access nodes for possible resume) to become available. If the UE does not wait for the next SAT2, the UE may send the request to SAT3. For example, the determination may be based on information of the next SAT2 (expected time of coverage availability) vs. tolerable delay for reception of the DL message. In an example implementation, the UE may use a timer that is associated with a pending network transaction. The timer may be started from the time that the corresponding UL message was sent. Based on the timer, it may be determined whether the expected time of connecting the next SAT2 (satellite access node) has passed. In an example, the determination to wait may be based on mobility of the UE, e.g., the location deviation between the current location and the estimated location based on the location information provided to the network.

[0075]

[0067] In an example embodiment, the UE may initiate RRC connection establishment with SAT3 to report an update of the UE location information (e.g., the current location and updated trajectory information), and may request the assistance information. In an example, the UE may send to SAT3, the RRC connection establishment request that may include a request for the assistance information. In an example, the assistance information may include at least one of an indication of whether to resume the first connection, an indication to delay resuming the first connection, e.g., to wait for the second access node to resume the first connection via the second access node (SAT2), an indication of whether to release the first connection, an indication of whether to establish a second connection via the third access node (SAT3). In an example, the assistance information may correspond to the S&F mode of operation. In an example, the request for assistance information may include at least one the following: e.g., the UE resume context information of the UE (at least the resume ID of the UE), the information of the last serving access node e.g., SAT1 (such as a SAT ID, a Cell ID, a base station (BS) ID, an identifier of the ground station, an identifier of the MME that SAT1 is connected to and selected for the UE, tracking area ID, and / or the like) which configured the UE resume context information for the UE, the information of the pending network transaction or DL message (such as transaction ID of the pending network transaction or DL message, started time or the remaining duration of the timer associated with the network transaction or DL message), the location information, the mobility information of the UE, and / or the like.

[0076]

[0068] In an example, the UE may determine not to resume the connection. For example, the UE may be configured to release, terminate or abort an ongoing transaction or the connection including all ongoing or pending transactions. In an example, the UE may determine to send a message to the SAT3 to perform at least UE location or tracking-area update if the UE determines that the UE in not in a targeted service area. In an example, the targeted service area of the UE may be given by the tracking area(s) supported by the list or plurality of target access nodes or SAT2 that was provided in the suspend configuration by the first access node SAT1. In an example, the determination of not to resume the connection may be based on restriction information such as tracking area(s) supported by SAT3 being different from restrictions in accordance with the list or plurality of target access nodes. In an example, the targeted service area of the UE may be a geographical area, e.g., within a configured distance from a configured reference position.

[0077]

[0069] In an example embodiment, the third access node (SAT3), (based on the request for assistance information provided by the UE and information from a connected ground station and MME and other SAT(s)), may determine one of the following options for the UE:

[0078]

[0070] Option 1 : SAT3 may request the UE to release or terminate a pending network transaction. In this case, the existing UE resume context information may be terminated or released. SAT3 may indicate to the UE that the UE may restart the network transaction with SAT3. In an example, the UE may restart the network transaction with a delay. In an example, the UE may determine to perform the UE location update or tracking area update with the CN via SAT3.

[0079]

[0071] Option 2: SAT3 may suspend the UE to wait for a target SAT2 (e.g., from the list or plurality of target access nodes) to resume and complete the pending network transaction. In an example, the SAT3 may send to the UE, updated information of the UE resume context information. In an example, the SAT3 may indicate to the UE to reset the timer or extend the duration of the timer. In an example, the SAT3 may provide an updated list of the list or plurality of target access nodes, e.g., an updated identifier of the second access node.

[0080]

[0072] In an example, the SAT3 may send instructions to the UE based on option 1 or option 2.

[0081]

[0073] In an example embodiment, in the S&F mode of operation, an access node (or the network) may determine (or predict) a target access node (or the plurality of second access nodes) for a possible resume of the UE and may (proactively) provide UE resume context information to the target access node. In an example, the UE may receive information of the target access node (e.g., information of the plurality of second access nodes according to an example embodiment) from the access node (e g., the first access node).

[0082]

[0074] FIG. 6 is a flow chart illustrating operation of an apparatus (e.g., which may be a UE or user device, or other apparatus) according to an example embodiment. Operation 610 includes receiving, by a user device having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node. Operation 620 includes receiving, from a third access node, an identifier of the third access node. Operation 630 includes determining based on at least one of the timing information, or the identifier of the third access node being different from the identifier of the second access node to: wait until the second access node becomes available, or send a second message to the third access node indicating a request for assistance information for the first connection or for a second connection to the network via the third access node.

[0083]

[0075] With respect to the method of FIG. 6, the method may further include: determining, based on the timing information, a first time duration until a coverage of the second access node is expected to become available.

[0084]

[0076] With respect to the method of FIG. 6, the method may further include: determining to wait for the second access node for the first time duration.

[0085]

[0077] With respect to the method of FIG. 6, the method may further include: wherein the determining to wait is based on the first time duration being less than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet.

[0086]

[0078] With respect to the method of FIG. 6, the method may further include: wherein the determining to send the second message is based on the first time duration being greater than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet.

[0087]

[0079] With respect to the method of FIG. 6, the method may further include: wherein the second message is a request to resume the first connection.

[0088]

[0080] With respect to the method of FIG. 6, the method may further include: wherein the identifier of the third base station is received via a system information block (SIB).

[0089]

[0081] With respect to the method of FIG. 6, the method may further include: wherein the first message is a radio resource control (RRC) release message, wherein the RRC release message triggers the user device to transition to a RRC inactive mode or a RRC idle mode for a suspension of the first connection.

[0090]

[0082] With respect to the method of FIG. 6, the method may further include: wherein the RRC release message may include suspend configuration, wherein the suspend configuration may include configuration information of a RRC inactive mode or a RRC idle mode, wherein the configuration information may include context information of the user device wherein the context information may include user device resume context information.

[0091]

[0083] With respect to the method of FIG. 6, the method may further include: wherein the user device resume context information may include at least one of: information of one or more target access nodes acting as the second access node; a resume identifier of the user device; an identifier of a mobility management entity serving the user device; an identifier of a transaction associated with the first connection of the user device with the network or associated with reception of an expected data packet; or timing information associated with the transaction, wherein the timing information includes at least one of starting time information, or information of remaining duration of timer associated with the transaction.

[0092]

[0084] With respect to the method of FIG. 6, the method may further include: wherein at least one of the first access node, the second access node, and the third access node is an access node in a store and forward (S&F) mode.

[0093]

[0085] With respect to the method of FIG. 6, the method may further include: wherein the second access node includes one or more access nodes.

[0094]

[0086] With respect to the method of FIG. 6, the method may further include: wherein the first message may include the identifier of the second access node.

[0095]

[0087] With respect to the method of FIG 6, the method may further include: wherein the first message may include the timing information associated with the availability of the second access node.

[0096]

[0088] With respect to the method of FIG. 6, the method may further include: wherein the first message may include at least one of service area information, tracking area information, or location information associated with the second access node.

[0097]

[0089] With respect to the method of FIG. 6, the method may further include: further includes determining to send the second message indicating the request for the assistance information, based on a determination to resume the first connection.

[0098]

[0090] With respect to the method of FIG. 6, the method may further include: wherein the assistance information provides instruction to the user device on at least one of: whether to resume the first connection; to wait for the second access node to resume the first connection via the second access node; to release the first connection; or to establish the second connection via the third access node.

[0099]

[0091] With respect to the method of FIG. 6, the method may further include: determining to send the second message based on at least one of service area information, tracking area information, or location information received from the first access node.

[0100]

[0092] With respect to the method of FIG. 6, the method may further include: wherein the access node may include at least one of a satellite base station, or a moving base station.

[0101]

[0093] FIG. 7 is a flow chart illustrating operation of an apparatus (e g., which may be a UE or user device, or other apparatus) according to an example embodiment. Operation 710 includes receiving, by a user device having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node. Operation 720 includes receiving, from a third access node, an identifier of the third access node. Operation 730 includes sending, to the third access node, a second message indicating a request for a resume of the first connection via the third access node. Operation 740 includes receiving from the third access node, a third message including assistance information indicating at least one of: whether to resume the first connection, to wait for the second access node to resume the first connection, to release the first connection, or to establish a second connection via the third access node.

[0102]

[0094] With respect to the method of FIG. 7, the method may further include: determining to send the second message indicating the request for the resume of the first connection, based on a determination to resume the first connection.

[0103]

[0095] With respect to the method of FIG 7, the method may further include: wherein the determination of whether to resume the first connection is based on at least one of service area information, tracking area information, or location information received from at least one of the first access node or the third access node.

[0104]

[0096] With respect to the method of FIG. 7, the method may further include: sending the second message to the third access node based on the timing information and based on the identifier of the third access node being different from the identifier of the second access node.

[0105]

[0097] With respect to the method of FIG. 7, the method may further include: wherein the second message indicates a request to receive assistance information for accessing the network via an access node in a store and forward (S&F) mode.

[0106]

[0098] With respect to the method of FIG. 7, the method may further include: wherein the second message may include at least one of: context information of the user device associated with the first connection including a resume identifier of the user device, wherein the context information may include user device resume context information; information of the first access node including at least one of an identifier of the first access node, an identifier of a cell of the first access node, a network identifier of a ground station, information of a mobility management entity serving the user device for access to the network; an identifier of a transaction associated with the first connection of the user device with the network or associated with reception of an expected data packet; timing information associated with the transaction, wherein the timing information includes at least one of starting time information, or information of remaining duration of timer associated with the transaction; location information of the user device including at least one of positioning related information, information of global positioning system (GPS) latitude and longitude, zone identifier, or cell identifier; or mobility information of the user device including location resolution information on a zone basis, location resolution information on a cell basis, velocity and direction estimation information, or trajectory information.

[0107]

[0099] With respect to the method of FIG. 7, the method may further include: wherein the second access node includes one or more access nodes.

[0108]

[0100] With respect to the method of FIG. 7, the method may further include: wherein the first message may include the identifier of the second access node.

[0109]

[0101] With respect to the method of FIG. 7, the method may further include: wherein the first message may include the timing information associated with the availability of the second access node.

[0110]

[0102] With respect to the method of FIG 7, the method may further include: wherein the assistance information further may include updated context information, wherein the context information may include user device resume context information.

[0111]

[0103] With respect to the method of FIG. 7, the method may further include: wherein the user device resume context information may include at least one of: information of one or more target access nodes acting as the second access node; a resume identifier of the user device; an identifier of a mobility management entity serving the user device; an identifier of a transaction associated with the first connection of the user device with the network or associated with reception of an expected data packet; or timing information associated with the transaction, wherein the timing information includes at least one of starting time information, or information of remaining duration of timer associated with the transaction.

[0112]

[0104] With respect to the method of FIG. 7, the method may further include: wherein the assistance information indicates whether to resume the first connection

[0113]

[0105] With respect to the method of FIG. 7, the method may further include: wherein the assistance information indicates to wait for the second access node to resume the first connection via the second access node.

[0114]

[0106] With respect to the method of FIG. 7, the method may further include: wherein the assistance information indicates to release the first connection.

[0115]

[0107] With respect to the method of FIG. 7, the method may further include: wherein the assistance information indicates to establish the second connection via the third access node.

[0108] FIG. 8 is a flow chart illustrating operation of an apparatus (e g., which may be a UE or user device, or other apparatus) according to an example embodiment. Operation 810 includes receiving, by a user device having a connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node. Operation 820 includes receiving, from a third access node, restriction information of the third access node for accessing the network. Operation 830 includes determining to release the connection based on the restriction information of the third access node.

[0116]

[0109] With respect to the method of FIG. 8, the method may further include: wherein the restriction information of the third access node may include at least one of service area information, or tracking area information.

[0117] [HO] With respect to the method of FIG. 8, the method may further include: releasing the connection, wherein the releasing includes releasing context information associated with the connection of the user device.

[0118] [Hl] With respect to the method of FIG 8, the method may further include: receiving from the third access node, an updated list of one or more access nodes for the user device to resume the connection.

[0119]

[0112] With respect to the method of FIG. 8, the method may further include: determining based on the timing information, a value of a first time duration to wait until a coverage of the second access node is expected to become available; and starting, a first timer, wherein the first timer is set to expire based on the value of the first time duration.

[0120]

[0113] With respect to the method of FIG. 8, the method may further include: wherein the determining to wait is based on: the value of the first time duration being less than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet; or expiry of the first timer.

[0121]

[0114] With respect to the method of FIG. 8, the method may further include: releasing the connection, wherein the releasing includes: stopping the first timer and starting a second timer based on a value of a second time duration; or extending a duration of the first timer based on the value of the second time duration.

[0122]

[0115] With respect to the method of FIG. 8, the method may further include: wherein the second access node includes one or more access nodes.

[0123]

[0116] With respect to the method of FIG. 8, the method may further include: wherein the first message may include restriction information of the first access node.

[0124]

[0117] With respect to the method of FIG. 8, the method may further include: wherein the determining to release the connection is based on the restriction information of the third access node being different from the restriction information of the first access node.

[0125] [H8] With respect to the method of FIG. 8, the method may further include: wherein the restriction information of the first access node may include at least one of service area information or tracking area information.

[0126] [H9] With respect to the method of FIG. 8, the method may further include: wherein the first message may include the identifier of the second access node.

[0127]

[0120] With respect to the method of FIG. 8, the method may further include: wherein the first message may include the timing information associated with the availability of the second access node.

[0128]

[0121] Some examples will now be described, based on the description and figures provided herein.

[0129]

[0122] Example Al. An apparatus including: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receive from a third access node, an identifier of the third access node, and determine based on at least one of the timing information, or the identifier of the third access node being different from the identifier of the second access node to: wait until the second access node becomes available, or send a second message to the third access node indicating a request for assistance information for the first connection or for a second connection to the network via the third access node.

[0130]

[0123] Example A2. The apparatus of example Al, wherein the apparatus is further caused to: determine, based on the timing information, a first time duration until a coverage of the second access node is expected to become available.

[0131]

[0124] Example A3. The apparatus of example Al, wherein the apparatus is further caused to: determine to wait for the second access node for the first time duration.

[0132]

[0125] Example A4. The apparatus of any of example A3, wherein the determining to wait is based on the first time duration being less than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet.

[0133]

[0126] Example A5. The apparatus of any of example A4, wherein the determining to send the second message is based on the first time duration being greater than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet.

[0134]

[0127] Example A6. The apparatus of any of examples A1-A4, wherein the second message is a request to resume the first connection.

[0135]

[0128] Example A7. The apparatus of example Al, wherein the identifier of the third base station is received via a system information block (SIB).

[0136]

[0129] Example A8. The apparatus of example Al, wherein the first message is a radio resource control (RRC) release message, wherein the RRC release message triggers the user device to transition to a RRC inactive mode or a RRC idle mode for a suspension of the first connection.

[0137]

[0130] Example A9. The apparatus of example A8, wherein the RRC release message may include suspend configuration, wherein the suspend configuration may include configuration information of a RRC inactive mode or a RRC idle mode, wherein the configuration information may include context information of the user device wherein the context information may include user device resume context information.

[0138]

[0131] Example A10. The apparatus of example A9, wherein the user device resume context information may include at least one of: information of one or more target access nodes acting as the second access node; a resume identifier of the user device; an identifier of a mobility management entity serving the user device; an identifier of a transaction associated with the first connection of the user device with the network or associated with reception of an expected data packet; or timing information associated with the transaction, wherein the timing information includes at least one of starting time information, or information of remaining duration of timer associated with the transaction.

[0139]

[0132] Example Al 1. The apparatus of example Al, wherein at least one of the first access node, the second access node, and the third access node is an access node in a store and forward (S&F) mode.

[0140]

[0133] Example A12. The apparatus of example Al, wherein the second access node includes one or more access nodes.

[0141]

[0134] Example A13. The apparatus of example Al, wherein the first message may include the identifier of the second access node.

[0142]

[0135] Example A14. The apparatus of example Al, wherein the first message may include the timing information associated with the availability of the second access node.

[0143]

[0136] Example Al 5. The apparatus of example Al, wherein the first message may include at least one of service area information, tracking area information, or location information associated with the second access node.

[0144]

[0137] Example A16. The apparatus of example Al, wherein the apparatus is further caused to: determine to send the second message indicating the request for the assistance information, based on a determination to resume the first connection.

[0145]

[0138] Example A17. The apparatus of example Al, wherein the assistance information provides instruction to the user device on at least one of whether to resume the first connection; to wait for the second access node to resume the first connection via the second access node; to release the first connection; or to establish the second connection via the third access node.

[0146]

[0139] Example Al 8. The apparatus of example Al, wherein the apparatus is further caused to: determine to send the second message based on at least one of service area information, tracking area information, or location information received from the first access node.

[0147]

[0140] Example A19. The apparatus of example Al, wherein the access node may include at least one of a satellite base station, or a moving base station.

[0148]

[0141] Example B 1 . An apparatus including: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a first connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receive from a third access node, an identifier of the third access node, send to the third access node, a second message indicating a request for a resume of the first connection via the third access node, and receive from the third access node, a third message including assistance information indicating at least one of: whether to resume the first connection; to wait for the second access node to resume the first connection; to release the first connection; or to establish a second connection via the third access node.

[0149]

[0142] Example B2. The apparatus of example Bl, wherein the apparatus is further caused to: determine to send the second message indicating the request for the resume of the first connection, based on a determination to resume the first connection.

[0150]

[0143] Example B3. The apparatus of example B2, wherein the determination of whether to resume the first connection is based on at least one of service area information, tracking area information, or location information received from at least one of the first access node or the third access node.

[0151]

[0144] Example B4. The apparatus of example Bl, wherein the apparatus is further caused to: send the second message to the third access node based on the timing information and based on the identifier of the third access node being different from the identifier of the second access node.

[0152]

[0145] Example B5. The apparatus of example Bl, wherein the first message is a RRC message.

[0153]

[0146] Example B6. The apparatus of example Bl, wherein the second message indicates a request to receive assistance information for accessing the network via an access node in a store and forward (S&F) mode.

[0154]

[0147] Example B7. The apparatus of example Bl, wherein the second message may include at least one of: context information of the user device associated with the first connection including a resume identifier of the user device, wherein the context information may include user device resume context information; information of the first access node including at least one of an identifier of the first access node, an identifier of a cell of the first access node, a network identifier of a ground station, information of a mobility management entity serving the user device for access to the network; an identifier of a transaction associated with the first connection of the user device with the network or associated with reception of an expected data packet; timing information associated with the transaction, wherein the timing information includes at least one of starting time information, or information of remaining duration of timer associated with the transaction; location information of the user device including at least one of positioning related information, information of global positioning system (GPS) latitude and longitude, zone identifier, or cell identifier; or mobility information of the user device including location resolution information on a zone basis, location resolution information on a cell basis, velocity and direction estimation information, or trajectory information.

[0155]

[0148] Example B8. The apparatus of example Bl, wherein the second access node may include one or more access nodes.

[0156]

[0149] Example B9. The apparatus of example Bl, wherein the first message may include the identifier of the second access node.

[0157]

[0150] Example BIO. The apparatus of example B 1 , wherein the first message may include the timing information associated with the availability of the second access node.

[0158]

[0151] Example B 11. The apparatus of example B 1 , wherein the assistance information further includes updated context information, wherein the context information may include user device resume context information.

[0159]

[0152] Example B12. The apparatus of example Bl 1, wherein the user device resume context information may include at least one of: information of one or more target access nodes acting as the second access node; a resume identifier of the user device; an identifier of a mobility management entity serving the user device; an identifier of a transaction associated with the first connection of the user device with the network or associated with reception of an expected data packet; or timing information associated with the transaction, wherein the timing information includes at least one of starting time information, or information of remaining duration of timer associated with the transaction.

[0160]

[0153] Example B 13. The apparatus of example Bl, wherein the assistance information indicates whether to resume the first connection.

[0161]

[0154] Example B14. The apparatus of example Bl, wherein the assistance information indicates to wait for the second access node to resume the first connection via the second access node.

[0162]

[0155] Example B15. The apparatus of example Bl, wherein the assistance information indicates to release the first connection.

[0163]

[0156] Example Bl 6. The apparatus of example Bl, wherein the assistance information indicates to establish the second connection via the third access node.

[0164]

[0157] Example Cl . An apparatus including: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a connection to a network via a first access node, a first message including at least one of an identifier of a second access node or timing information associated with an availability of the second access node, receive from a third access node, restriction information of the third access node for accessing the network, and determine to release the connection based on the restriction information of the third access node.

[0165]

[0158] Example C2. The apparatus of example Cl, wherein the restriction information of the third access node may include at least one of service area information, or tracking area information.

[0166]

[0159] Example C3. The apparatus of example Cl, wherein the apparatus is further caused to: release the connection, wherein the release includes releasing context information associated with the connection of the user device.

[0167]

[0160] Example C4. The apparatus of example Cl, wherein the apparatus is further caused to: receive from the third access node, an updated list of one or more access nodes for the user device to resume the connection.

[0168]

[0161] Example C5. The apparatus of example Cl, wherein the apparatus is further caused to: determine based on the timing information, a value of a first time duration to wait until a coverage of the second access node is expected to become available; and start a first timer, wherein the first timer is set to expire based on the value of the first time duration.

[0169]

[0162] Example C6. The apparatus of example C5, wherein the determining to wait is based on: the value of the first time duration being less than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet; or expiry of the first timer.

[0170]

[0163] Example C7. The apparatus of any of example C6, wherein the apparatus is further caused to: release the connection, wherein the release includes: stop the first timer and start a second timer based on a value of a second time duration; or extend a duration of the first timer based on the value of the second time duration.

[0171]

[0164] Example C8. The apparatus of any of examples C1-C7, wherein the second access node includes one or more access nodes.

[0172]

[0165] Example C9. The apparatus of example Cl, wherein the first message may include restriction information of the first access node.

[0173]

[0166] Example CIO. The apparatus of any of examples C1-C9, wherein the determining to release the connection is based on the restriction information of the third access node being different from the restriction information of the first access node.

[0174]

[0167] Example Cl 1. The apparatus of example C9 or CIO, wherein the restriction information of the first access node may include at least one of service area information or tracking area information.

[0175]

[0168] Example C12. The apparatus of example Cl, wherein the first message may include the identifier of the second access node.

[0176]

[0169] Example C13. The apparatus of example Cl, wherein the first message may include the timing information associated with the availability of the second access node.

[0177]

[0170] FIG. 9 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 1300 according to an example embodiment. The wireless station 1300 may include, for example, one or more (e.g., two as shown in FIG. 9) RF (radio frequency) or wireless transceivers 1302A, 1302B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit / entity (controller) 1304 to execute instructions or software and control transmission and receptions of signals, and a memory 1306 to store data and / or instructions.

[0178]

[0171] Processor 1304 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 1304, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1302 (1302A or 1302B). Processor 1304 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1302, for example). Processor 1304 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1304 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 1304 and transceiver 1302 together may be considered as a wireless transmitter / receiver system, for example.

[0179]

[0172] In addition, referring to FIG. 9, a controller (or processor) 1308 may execute software and instructions, and may provide overall control for the station 1300, and may provide control for other systems not shown in FIG. 9, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 1300, such as, for example, an email program, audio / video applications, a word processor, a Voice over IP application, or other application or software.

[0180]

[0173] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1304, or other controller or processor, performing one or more of the functions or tasks described above.

[0181]

[0174] According to another example embodiment, RF or wireless transceiver(s) 1302A / 1302B may receive signals or data and / or transmit or send signals or data. Processor 1304 (and possibly transceivers 1302A / 1302B) may control the RF or wireless transceiver 1302A or 1302B to receive, send, broadcast or transmit signals or data.

[0182]

[0175] Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 1300, FIG. 9) including means (e.g., processor 1304, RF transceivers 1302A and / or 1302B, and / or memory 1306, in FIG. 9) for carrying out any of the methods; a non-transitory computer-readable storage medium (e g., memory 1306, FIG. 9) comprising instructions stored thereon that, when executed by at least one processor (processor 1304, FIG. 9), are configured to cause a computing system (e.g., 1300, FIG. 9) to perform any of the example methods; and an apparatus (e.g., 1300, FIG. 9) including at least one processor (e.g., processor 1304, FIG. 9), and at least one memory (e.g., memory 1306, FIG. 9) including computer program code, the at least one memory (1306) and the computer program code configured to, with the at least one processor (1304), cause the apparatus (e.g., 1300) at least to perform any of the example methods.

[0183]

[0176] Embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and / or programs and / or software embodiments that are downloadable via the Internet or other network(s), either wired networks and / or wireless networks. In addition, embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).

[0184]

[0177] As used in this application, the term ‘circuitry’ or “circuit” refers to all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of circuits and soft-ware (and / or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s) / software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term in this application. As a further example, as used in this application, the term ‘circuitry’ would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and / or firmware. The term ‘circuitry’ would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.

[0185]

[0178] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer, or it may be distributed amongst a number of computers.

[0186]

[0179] Furthermore, embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the embodiment and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.

[0187]

[0180] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[0188]

[0181] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0189]

[0182] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magnetooptical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0190]

[0183] To provide for interaction with a user, embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0191]

[0184] Embodiments may be implemented in a computing system that includes a backend component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a frontend component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such backend, middleware, or frontend components. Components may be interconnected by any form or medium of digital data communication, e g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.

[0192]

[0185] While certain features of the described embodiments have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

WHAT IS CLAIMED IS:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, by the apparatus having a connection to a network via a first access node, a first message comprising at least one of an identifier of a second access node or timing information associated with an availability of the second access node; receive from a third access node, restriction information of the third access node for accessing the network; and determine to release the connection based on the restriction information of the third access node.

2. The apparatus of claim 1, wherein the restriction information of the third access node comprises at least one of service area information, or tracking area information.

3. The apparatus of claim 1, wherein the apparatus is further caused to: release the connection, wherein the release includes releasing context information associated with the connection of the user device.

4. The apparatus of claim 1, wherein the apparatus is further caused to: receive from the third access node, an updated list of one or more access nodes for the user device to resume the connection.

5. The apparatus of claim 1, wherein the apparatus is further caused to: determine based on the timing information, a value of a first time duration to wait until a coverage of the second access node is expected to become available; and start, a first timer, wherein the first timer is set to expire based on the value of the first time duration.

6. The apparatus of claim 5, wherein the determining to wait is based on: the value of the first time duration being less than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet; or expiry of the first timer.

7. The apparatus of any of claim 6, wherein the apparatus is further caused to: release the connection, wherein the release includes: stop the first timer and start a second timer based on a value of a second time duration; or extend a duration of the first timer based on the value of the second time duration.

8. The apparatus of any of claims 1-7, wherein the second access node includes one or more access nodes.

9. The apparatus of claim 1, wherein the first message comprises restriction information of the first access node.

10. The apparatus of any of claims 1-9, wherein the determining to release the connection is based on the restriction information of the third access node being different from the restriction information of the first access node.

11. The apparatus of claim 9 or 10, wherein the restriction information of the first access node comprises at least one of service area information or tracking area information.

12. The apparatus of claim 1, wherein the first message comprises the identifier of the second access node.

13. The apparatus of claim 1, wherein the first message comprises the timing information associated with the availability of the second access node.

14. A method comprising: receiving, by a user device having a connection to a network via a first access node, a first message comprising at least one of an identifier of a second access node or timing information associated with an availability of the second access node; receiving, from a third access node, restriction information of the third access node for accessing the network; and determining to release the connection based on the restriction information of the third access node.

15. The method of claim 14, wherein the restriction information of the third access node comprises at least one of service area information, or tracking area information.

16. The method of claim 14, further comprising releasing the connection, wherein the releasing includes releasing context information associated with the connection of the user device.

17. The method of claim 14, further comprising receiving from the third access node, an updated list of one or more access nodes for the user device to resume the connection.

18. The method of claim 14, further comprising: determining based on the timing information, a value of a first time duration to wait until a coverage of the second access node is expected to become available; and starting, a first timer, wherein the first timer is set to expire based on the value of the first time duration.

19. The method of claim 18, wherein the determining to wait is based on: the value of the first time duration being less than a threshold, wherein the threshold is determined based on a maximum delay that can be tolerated for reception of an expected data packet; or expiry of the first timer.

20. The method of any of claim 19, further comprising releasing the connection, wherein the releasing includes: stopping the first timer and starting a second timer based on a value of a second time duration; or extending a duration of the first timer based on the value of the second time duration.

21. The method of any of claims 14-20, wherein the second access node includes one or more access nodes.

22. The method of claim 14, wherein the first message comprises restriction information of the first access node.

23. The method of any of claims 14-22, wherein the determining to release the connection is based on the restriction information of the third access node being different from the restriction information of the first access node.

24. The method of claim 22 or 23, wherein the restriction information of the first access node comprises at least one of service area information or tracking area information.

25. The method of claim 14, wherein the first message comprises the identifier of the second access node.

26. The method of claim 14, wherein the first message comprises the timing information associated with the availability of the second access node.

Images