WO2016138937A1

WO2016138937A1 - Connection suspend and resume requests for wireless network

Info

Publication number: WO2016138937A1
Application number: PCT/EP2015/054386
Authority: WO
Inventors: Mikko Saily; Per Henrik Michaelsen; Simone BARBERA
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2015-03-03
Filing date: 2015-03-03
Publication date: 2016-09-09

Abstract

An example technique is provided for establishing a wireless connection between a first network node and a second network node, controlling receiving signals by the first network node from one or more other network nodes, and controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

Description

DESCRIPTION

TITLE

CONNECTION SUSPEND AND RESUME REQUESTS FOR WIRELESS NETWORK

TECHNICAL FIELD

[0001 ] This description relates to wireless networks.

BACKGROUND

[0002] 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.

[0003] 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. E-UTRA (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, which are referred to as evolved Node Bs (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as a user equipment (UE). LTE has included a number of improvements or developments. 5G wireless networks are also being developed.

[0004] Dual Connectivity (DC) is a mode of operation in which a user equipment (UE) or mobile station is connected with two base stations, such as a master eNB (or MeNB or master base station) and a secondary eNB (SeNB or secondary base station). Dual connectivity may have several advantages, such as, for example, reducing the number of handover failures and/or increasing a user's throughput. Similarly, for 5G wireless networks, multi-connectivity allows a UE or mobile station to be connected to multiple base stations or eNBs.

SUMMARY

[0005] According to an example implementation, a method may include establishing a wireless connection between a first network node and a second network node, controlling receiving signals by the first network node from one or more other network nodes, and controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[0006] According to an example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: establish a wireless connection between a first network node and a second network node, control receiving signals by the first network node from one or more other network nodes, and control sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[0007] According to another example implementation, a computer program product includes a non-transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: establishing a wireless connection between a first network node and a second network node, controlling receiving signals by the first network node from one or more other network nodes, and controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[0008] According to another example implementation, an apparatus may include means for establishing a wireless connection between a first network node and a second network node, means for controlling receiving signals by the first network node from one or more other network nodes, and means for controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[0009] According to an example implementation, a method may include establishing a wireless connection between a first network node and a second network node, and controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[0010] According to an example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: establish a wireless connection between a first network node and a second network node; and control receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[001 1 ] According to another example implementation, a computer program product includes a non-transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: establishing a wireless connection between a first network node and a second network node, and controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node. [0012] According to another example implementation, an apparatus may include means for establishing a wireless connection between a first network node and a second network node, and means for controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[0013] The details of one or more implementations are set forth in the accompa-nying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG. 1 is a block diagram of a dual connectivity wireless network 130 according to an example implementation.

[0015] FIG. 2 is a block diagram illustrating a dual connectivity wireless network in more detail according to an example implementation.

[0016] FIG. 3 is a diagram illustrating operation of a wireless network according to an example implementation.

[0017] FIG. 4 is a diagram illustrating use of remote radio heads according to an example implementation.

[0018] FIG. 5 is a diagram illustrating sending a connection suspend request or a connection resume request according to an example implementation.

[0019] FIG. 6 is a diagram illustrating sending a connection release request according to an example implementation.

[0020] FIG. 7 is a flow chart illustrating operation of a network node according to an example implementation.

[0021 ] FIG. 8 is a flow chart illustrating operation of a network node according to another example implementation.

[0022] FIG. 9 is a block diagram of a network node (e.g., BS or user device) according to an example implementation.

DETAILED DESCRIPTION

[0023] FIG. 1 is a block diagram of a dual connectivity wireless network 130 according to an example implementation. In the wireless network 130 of FIG. 1 , a plurality of network nodes are shown. Referring to FIG. 1 , a user device 132, which may also be referred to as a user equipment (UE), may be connected (and in communication) with multiple base stations (BSs), which may also be referred to as evolved Node Bs (eNBs). Therefore, according to an example implementation, a network node may include (or may be) a user device or UE, and/or a BS or eNB. At least part of the functionalities of a base station or (e)Node B (eNB) may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. [0024] Referring to FIG. 1 , user device (or UE) 132 may be connected (and in

communication) with a master BS 134 (or master eNB or MeNB) which provides wireless coverage within a master cell group (MCG), which may include one or more cells associated with master BS 134, such as primary cell (Pcell) 136. The user device 132 may also be simultaneously connected to and/or in communication with one or more secondary BSs, such as to a secondary BS 138 (also referred to as secondary BS or SeNB), which provides wireless coverage within a secondary cell group (SCG), which may include one or more secondary cells (Scells), such as Scell 140, associated with secondary BS 138.

[0025] Thus a wireless connection may be established between a user device and a BS. Establishing a wireless connection may include, for example, the user device obtaining information that may be necessary for the user device to communicate with the BS. In an illustrative example implementation, as part of establishing a wireless connection with a BS, a user device may obtain a terminal/UE identity (such as a cell radio network temporary identifier or C-RNTI of the UE) for the user device and uplink synchronization information from the BS to allow the user device to communicate with the BS. Also, as part of establishing a wireless connection, resources for the wireless connection may be allocated by the user device and/or BS to allow communication to occur between the user device and BS, and/or context (or context information) for the wireless connection may be stored by the user device and/or the BS.

[0026] According to one illustrative (and non-limiting) example implementation, a user device may establish a connection with a BS by performing a random access procedure with the BS via a random access channel (RACH), which may be referred to as a RACH procedure, for example. As part of an example RACH procedure, a user device may send a random access preamble to the BS to allow the BS to estimate transmission timing for the user device. The BS may then send a user device/UE identity (e.g., C-RNTI) for the user device to use in communicating with the BS or cell, and a timing advance offset (synchronization information) to allow the user device to transmit uplink signals to the BS. In one example implementation, by performing random access, the user device may transition from an idle (e.g., an RRC_idle) state with respect to the BS, to a connected

(e.g., RRC_connected) state with respect to the BS, where RRC refers to radio resource control. Also, RACH-less procedures may also be used to establish a connection between a user device and a BS, e.g., such as where the user device already has synchronization information or timing advance offset information for a cell or BS. A random access procedure is merely one illustrative example of a technique that may be used to establish a connection between a user device and a BS, and other techniques or procedures may be used to establish a connection. Also, a user device may be connected with a plurality of (or multiple) cells or BSs at the same time. A connection may use one or more wireless links to communicate data between a user device and a BS.

[0027] Thus, with reference to FIG. 1 , in an illustrative example implementation, user device 132 may receive wireless services via one or more cells (e.g., including a primary cell and possibly one or more secondary cells) of a master cell group (MCG) associated with the master BS (or MeNB) 134, and via one or more secondary cells or Scells (e.g., including at least a primary secondary cell or Pscell) associated with the secondary BS 138 (or SeNB). Thus, the example network nodes shown in FIG. 1 include a SeNB 138, a MeNB 134 and a user device 132. BS 134 is also connected to a core network 150 via a S1 interface 151 . BS 138 may also be connected to core network 150. Secondary BS 138 may be connected via an interface to master BS 134. This is merely an example of a wireless network, and others may be used.

[0028] According to an example implementation, a user device (user terminal, user equipment (UE)) may refer to a portable computing device that includes wireless mobile communication devices operating 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, and a multimedia device, as examples. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.

[0029] In LTE (as an example), the 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.

[0030] Therefore, according to one example implementation, a dual connectivity wireless network allows for a user device (such as user device 132) to be simultaneously connected to multiple base stations, e.g., simultaneously connected to both a master BS (or MeNB) 134, and a secondary BS (SeNB) 138 (or to one or more SeNBs). A dual connectivity wireless network, such as the network 130 shown in FIG. 1 may have several advantages, such as, for example, decreasing a signaling load towards the core network, sharing traffic/packet processing among multiple base stations, as well as benefitting from flexible resource usage where one or more carriers may be used on a radio link between the MS and each BS, e.g., inter-site carrier aggregation.

[0031 ] Similarly, 5G multi-connectivity allows a user device (or UE) to be connected to one or more master BSs (MeNBs) and one or more secondary BSs (SeNBs). A master BS may typically include a radio resource control (RRC) protocol entity. In 4G/LTE, the RRC may be provided at a single MeNB for dual connectivity with respect to a user device. In 5G multi-connectivity, the RRC protocol functionality or MeNB functionality may instead be distributed among a plurality of (or multiple) base stations/eNBs.

[0032] FIG. 2 is a block diagram illustrating a dual connectivity wireless network 208 in more detail according to an example implementation. Although not shown, each base station (BS) and the user device (or UE) 132 includes a processor, memory and one or more wireless transceivers (wireless transmitter/receiver). Master BS 134 (or MeNB) and secondary BS 138 (or SeNB) may be connected via a bidirectional backhaul connection

(which may be wired or wireless), which is shown in FIG. 2 as an Xn interface 21 1 . One or both of BSs 134, 138 may be connected to the core network 210 via a bidirectional S1 interface. A user device 132 may, for example, be simultaneously connected to master BS 134 via a radio link 212 and to secondary BS 138 via a radio link 214.

[0033] User device 132, BS 134 and BS 138 each includes at least one radio protocol stack that may be implemented in hardware and/or software. According to an example implementation, a protocol stack may include logic, and/or computer instructions executed by a processor to perform the functions or operations for each entity of the protocol stack. An example protocol stack for the master BS 134 may include, for example, at least a Packet Data Convergence Protocol (PDCP) entity 220A, a Radio Link Control (RLC) entity 222A, a Media Access Control (MAC) entity 224, a Physical layer (PHY) entity 226, and a Radio Resource Control (RRC) entity 228.

[0034] The PDCP entity 220A performs ciphering (encryption and decryption of data) and header compression-decompression. There is one PDCP entity 222A per radio bearer configured for a user device. The RLC entity 222A performs segmentation/concatenation, error detection and correction, data retransmission, duplicate detection and in-sequence data delivery to higher layers. According to an example implementation, there may be one RLC entity per radio bearer or multiple RLC entities per radio bearer configured for a user device. According to one example implementation, the radio protocol stack may include two RLC entities per radio bearer. MAC entity 224 performs multiplexing of logical channels (where there may be one or more logical channel per radio bearer), hybrid ARQ retransmissions, inserting of MAC control elements (MAC CEs) used for in-band control signaling, and other MAC-related functions. The BS MAC entity 224 also performs uplink and downlink scheduling (located in MAC entity of each BS). The MAC entity 224 provides services to the RLC entities in the form of logical channels. The PHY entity 226 handles or performs coding/decoding, modulation/demodulation, multi-antenna mapping, and other physical layer functions. Multiple RLC entities within a BS may, for example, share one MAC entity 224 and one PHY entity 226.

[0035] RRC entity 228 is responsible for handling a number of functions or procedures related to the Radio Access Network (RAN) (e.g., shown in FIGs. 1 -2), including broadcast of system information necessary for the user device to be able to communicate with a cell or BS, transmission of paging messages originating from the core network 210 to notify a user device about incoming connection requests, connection management including setting up bearers and mobility, mobility functions such as change of servings cells and handover, and other control related functions. According to an illustrative example implementation, the RRC entity may be provided in a master BS and a user device, but may not be (necessarily) provided (or operating) in a secondary BS (SeNB), for example.

[0036] As shown in FIG. 2, secondary BS 138 may include at least one protocol stack that includes protocol entities that are the same or similar to those of master BS 134. For example, secondary BS 138 (SeNB) may include a RLC entity 232A (e.g., receiving data associated with a split bearer 203), a MAC entity 234, and a PHY entity 236. BS 138 may also include, for example, PDCP entity 233 and RLC entity 232B (e.g., receiving data for a

SCG bearer 207). According to an example implementation, MAC entity 234 and PHY entity 236 may be shared by multiple RLC entities of secondary BS (RLC entities 232A and 232B). [0037] User device 132 includes protocol entities that communicate with the peer entities at the master BS 134 and/or secondary BS 138. While only one protocol stack (e.g., RRC, PDCP, RLC, MAC and PHY) is shown for the user device 132, it should be understood that user device 132 may include at least one protocol stack (or portion thereof) for communicating with master BS 134 and at least one protocol stack (or portion thereof) for communicating with secondary BS 138, according to an example implementation, e.g., one PDCP entity and one RLC entity at user device 132 for each peer entity at master BS 134 or secondary BS 138. Therefore, user device 132 may include the following example protocol entities: PDCP entity 240, RLC entity 242, MAC entity 244, PHY entity 246 and RRC entity 248. These protocol entities at user device 132 may, for example, perform the same or very similar functions as performed by the peer protocol entities of the master BS 134 or secondary BS 138, and/or communicate with the peer entities at one or more BSs.

[0038] According to an example implementation, the Radio Access Network (RAN), which includes a group of BSs or eNBs, provides one or more radio bearers. A radio bearer generally provides a transport service between two points. For example, packets may be mapped to bearers according to their QoS (quality of service) requirements and the destination (IP address or MS) of the packets.

[0039] Several different bearer types may be used. A first type of bearer is a master cell group (MCG) bearer in which data or traffic for the MCG bearer is handled or processed by a master cell group (MCG) and an associated master BS 134. MCG may include one or more cells controlled by the master BS, such as at least a Pcell (primary cell). A second type of a bearer is a secondary cell group (SCG) bearer, such as, for example, SCG bearer 207, in which data or traffic are processed and forwarded to a mobile station from the secondary BS (or SeNB) 138 via PDCP entity 233 and RLC entity 232B. Thus, for example, data for the SCG bearer 207 may be processed or forwarded via the one or more cells of the secondary cell group (SCG). A third type of bearer is a split bearer, such as split bearer 203, in which data for the split bearer may be split or divided between base stations for forwarding. For example, for split bearer 203, the PDCP entity 220B

(receiving data for the split bearer 203) of master BS 134 may split the data or traffic associated with bearer 203 between RLC entity 222B at master BS 134 and RLC entity

232A at secondary BS (SeNB) 138. Thus, in the example of a split bearer, the PDCP entity 220B may split traffic between RLC entities of the master BS 134 and the secondary BS 138, e.g., to allow offloading of some traffic to the secondary BS 138.

[0040] In dual connectivity, at least one cell (e.g., a Pcell) of the master cell group (MCG) serves the user device 132 via the master BS 134 (MeNB), and at least one cell (e.g., a Scell, and/or or Pscell) of the secondary cell group (SCG) serves the user device 132 via the secondary BS 138 (SeNB). In some cases, a change may need to be performed to the SCG, e.g., as the user device 132 moves or changes location, the SCG may need to be updated to replace Scell 1 with Scell 2 within the SCG, where Scell 2 is now a better serving cell than ScelM based on a changed location of the MS 132. Similarly, a SeNB (or secondary BS) change (or SeNB change procedure) may be performed in which a new SeNB/secondary BS may be added for a user device, or an existing SeNB may be dropped or released for a user device, or a target SeNB may replace a source (current) SeNB for a user device. [0041 ] According to an example implementation, after a wireless connection has been established between a first network node and a second network node, the first network node may send a connection request to the second network node to change the status of the wireless connection between the first and second network nodes. The network nodes may include, for example, a user device (UE) or a BS (eNB). For example, a wireless connection may be established between a user device and a BS.

[0042] As noted, the connection request may be a request to change a status of a wireless connection between the first network node and the second network node. For example, a connection request may include a request to suspend, resume or release the wireless connection between the first network node and the second network node. Thus, in a first example implementation, a user device may send a connection request to a BS to change the status of a wireless connection between the user device and the BS. In a second example implementation, a BS (or eNB) may send a connection request to a user device to change the status of the wireless connection between the user device and the BS. A number of examples are described herein with a user device sending a connection request to a BS to cause the BS to change a status of the wireless connection between the user device and the BS. However, a BS may also send a connection request to the user device. In other words, in an example implementation, both a user device and/or a BS may initiate or request a change to a wireless connection status.

[0043] According to an example implementation, when a wireless connection is established between two network nodes (e.g., between a user device and a BS), resources (e.g., processing resources, storage/buffer resources, network resources, etc.) may be allocated by each network node for the connection, and context/context information for the connection may be stored. Data bearers may be established or configured to forward data between the BS and the user device. The BS may receive data from the network via a data bearer, temporarily buffer the downlink data, and then may forward/transmit the data to the user device. The BS may receive scheduling requests from the user device, and may issue scheduling grants to allocate uplink resources to allow the user device to transmit data to the BS.

[0044] A connection suspend request may be used to suspend a wireless connection.

According to an example implementation, a user device may suspend one or more activities related to a wireless connection when the wireless connection is suspended or when the user device receives a connection suspend request. For example, a user device may cease or suspend requesting uplink resources (via scheduling requests) and may cease or suspend transmitting data to the BS when the wireless connection is suspended and/or in response to a connection suspend request from a BS.

[0045] Also, when a BS receives a connection suspend request from a user device (or when the wireless connection is suspended), the BS may also suspend one or more actions or activities related to the wireless connection. For example, the BS may buffer data directed to the user device and delay forwarding this data until operation of the wireless connection is resumed. In an example implementation, the BS may also notify the core network (or may notify the master BS/MeNB) of the suspension of the

connection. Based on this notification of the connection suspension, the master BS/MeNB and/or the core network may suspend a bearer, e.g., may suspend data transmissions over a data bearer to the BS for data addressed/directed to the user device, and/or may suspend transmission of downlink data over one or more bearers that serve or feed data to the suspended wireless connection. Thus, for example, the master BS/MeNB and/or core network may re-route data addressed to the user device via an alternate (active) wireless connection(s) to the user device, e.g., to avoid forwarding data to the BS that suspended the wireless connection. For example, if a SeNB suspends a wireless connection with a user device, a split bearer for the MeNB serving the user device may be suspended or reconfigured so that data directed to the user device is transmitted to the user device via the MeNB/via other wireless connections that are not suspended, e.g., during the period which the wireless connection between the user device and SeNB is suspended. The SeNB may also buffer or temporarily store downlink data to be forwarded to the user device while the connection is suspended.

[0046] A connection resume request may be used to resume a wireless connection (or resume operation of wireless connection). According to an example implementation, a user device may resume one or more activities related to a wireless connection (e.g., activities that may have been suspended) when the wireless connection is resumed or when the user device receives a connection resume request. For example, a user device may resume receiving data from the BS, may resume requesting resources from the BS for uplink data transmission (e.g., by sending a scheduling request to the BS, and receiving a scheduling grant from the BS).

[0047] Similarly, according to an example implementation, a BS may resume one or more activities related to a wireless connection (e.g., activities that may have been suspended) when the wireless connection is resumed or when the BS receives a connection resume request. For example, the BS may resume forwarding data to the user device, granting scheduling requests received from the user device, receive uplink data from the user device and forward the uplink data to the core network. In one example implementation, the BS (e.g., SeNB) may also notify the master BS/MeNB and/or core network that the wireless connection has been resumed, which may cause the core network to resume the data bearer or reconfigure the data bearer to resume forwarding data to the BS to be forwarded to the user device over the resumed wireless connection.

[0048] A connection release request may be used to release a wireless connection.

According to an example implementation, a user device may send a connection release request to a BS to request the BS to release a wireless connection between the user device and BS. Release (by the user device or BS) of a wireless connection may include for example, releasing resources allocated for the wireless connection, deletion or removal of context/context information associated with the connection, discarding (e.g., by the BS) of data packets to be forwarded as part of the connection, discarding of packets received as part of the connection, and no longer servicing the connection, e.g., no longer transmitting data and/or submitting or granting scheduling requests for the connection, etc. The resources that have been released are now available (at the user device and BS) to be re-allocated to another wireless connection, for example.

[0049] FIG. 3 is a diagram illustrating operation of a wireless network according to an example implementation. In an example implementation, a user device (UE) 132 may be connected to one or more BS/eNBs, such as being connected to a master BS (or (MeNB) 134 (FIG. 1 ) and one or more secondary BSs (or SeNBs), for example. For example, depending on the received signals from each BS, the user device may select which wireless connections to suspend, resume, or release. Thus, by sending the connection requests (e.g., connection suspend request, connection resume request, and connection release request) directly from the user device to the BS (e.g., secondary BS/SeNB), the impacted/effected BSs may receive a notification that the connection status has changed quicker than relying upon the network to make a decision for a SeNB change or a connection status change and/or relying on the network or other BSs to communicate the connection status change to the impacted BS.

[0050] With reference to FIG. 3, at 310, a first wireless connection is established between user device 132 and a first secondary BS (first SeNB) 138A. For example, user device 132 may perform a random access procedure (RACH procedure) with the first SeNB 138A to establish a wireless connection with first SeNB 138A.

[0051 ] At 312, user device 132 may receive signals (e.g., pilot sequences or reference signals) from one or more BSs/eNBs, such as from first SeNB 138A and from second secondary BS (second SeNB) 138B.

[0052] At 314, based on these received signals (e.g., based on the signal power and/or signal quality of these received signals), the user device may determine one or more wireless connections to establish, suspend, resume or release. In this illustrative example, the user device 132 may determine that the second SeNB 138B is a better SeNB to serve the user device 132 than the first SeNB 138A, e.g., due to higher quality signals or higher power signals received from SeNB 138B as compared to he signals received from SeNB 138A, for example.

[0053] At 316, the user device may send a connection suspend request to the first SeNB 138A to request SeNB 138A to suspend the first wireless connection between the user device 132 and the first SeNB 138A. In response to receiving the connection suspend request, first SeNB 138A may suspend the first wireless connection between the user device 132 and first SeNB 138A.

[0054] At 318, in response to the first SeNB 138 receiving the connection suspend request, the first SeNB 138A may activate a suspend timer for the first wireless

connection. First SeNB 138A will release the first wireless connection if the suspend timer expires before SeNB 138A receives a connection resume request from the user device 132 for the first wireless connection. The suspend timer may be used to ensure that the user device does not suspend the first wireless connection for an indefinite or long period of time, since resources are still allocated for a suspended wireless connection. For example, the suspend timer may be set to a value (or maximum time) that the wireless connection should be suspended before being released. Thus, a suspend timer may prevent the problem where a user device may establish and then suspend a wireless connection, and then the user device never resumes or releases the wireless connection, which occupies resources without the benefit of the resources. In such case, the suspend timer for the first wireless connection may be activated based upon receiving a connection suspend request, and the suspend timer would cause the first SeNB 138A to release the first wireless connection upon expiration of the suspend timer. The suspend timer for the first wireless connection, if not expired, may be stopped and then reset to its initial value upon receiving a connection resume request for the first wireless connection. Upon receiving a second connection suspend request for the first wireless connection, the suspend timer may again be activated (or started).

[0055] At 320, a second wireless connection is established between the user device 132 and the second SeNB 138B. For example, to establish a second wireless connection with second SeNB 138B, the user device 132 may perform a random access procedure with the second SeNB 138B.

[0056] At 322, after establishing the connection with the second SeNB 138B, user device 132 may send a connection release request to first SeNB 138A, causing the first SeNB 138A to release the first wireless connection. Thus, in this example, the user device 132 may send a connection release request to release the first connection after a (e.g., better) second wireless connection with a second SeNB 138B has been established, for example.

[0057] Operations at 324 and 326 may be performed instead of the operation at 322. At 324, user device 132 may send a connection suspend request to the second SeNB 138B, causing the second SeNB 138B to suspend the second wireless connection. At 326, the user device may send a connection resume request to first SeNB 138A to resume the first wireless connection, causing the first SeNB 138A to resume the first wireless connection. In this manner, the user device may have established two wireless connections (a first wireless connection with first SeNB 138A and a second wireless connection with second SeNB 138B), and may select to resume the wireless connection of the two wireless connections that provides the best service or signal to user device, and may suspend the other wireless connection.

[0058] While only two wireless connections are described in the examples of FIG. 3, any number of wireless connections may be established, and then suspended, resumed or released. Also, while the examples of FIG. 3 are illustrated for secondary BSs/SeNBS, a user device may similarly establish and then suspend, resume or release wireless connections with other types of network nodes, such as with master BSs/MeNBs, remote radio heads (RRHs), etc.

[0059] Also, while the connection requests in FIG. 3 are sent directly from a user device to the SeNB (that established the connection with the user device), alternatively, the connection request(s) may be indirectly sent to the impacted/effected BS (e.g., via another BS). For example, a user device may send a connection request (e.g., requesting that a SeNB suspend, resume or release a connection with the user device) to a master

BS/MeNB, and the MeNB may then forward the connection request to the SeNB, for example.

[0060] Also, the connection requests (e.g., requests to suspend, resume, or release a wireless connection) shown in the illustrative examples of FIG. 3 are sent by the user device to the BS. However, in another example implementation, the BS may send the connection requests (e.g., to suspend, resume or release a wireless connection) to the user device, causing the user device to perform the requested change to the wireless connection. [0061 ] Therefore, various example implementations may provide or describe techniques for signalling and controlling data flow control (e.g., sending and/or receiving various connection requests) between network nodes, such as between a user device (or UE) and a base station/eNB. The various example connection requests described herein include connection requests to suspend, resume and/or release a wireless connection, but this description is not limited thereto. Other types of connection requests may be used or provided.

[0062] According to one illustrative example implementation, signalling (e.g., various connection requests) may be provided between network nodes, such as between a user device (or UE) and a BS (or eNB). An example implementation may use UE-initiated uplink control signalling (e.g., connection requests sent by the user device/UE to a BS) for controlling the data flow of a wireless/radio link. Alternatively, a BS may send the connection requests to the user device/UE. According to one illustrative example, the UE- autonomous mobility control signalling (e.g., connection requests) may be sent or performed without RRC protocol between user device/UE and BS/eNB, but not limited to this. Optionally the uplink control signalling (e.g., connection requests, or messages that include the connection request(s)) may include encapsulated RRC protocol details.

[0063] According to an example implementation, suspending the wireless connection may mean that the BS will stop scheduling the downlink data and may take other core network related actions. For example, based on a received connection suspend request, the BS (e.g., SeNB) may, for example, inform the master node (master BS/MeNB) and possibly other nodes participating in multi-connectivity about the suspended wireless connection. Thereafter, for example, the master node (or MeNB) can suspend or stop the data bearer functions towards the BS (e.g., SeNB) that provides the suspended wireless connection to the user device. In some cases, suspending bearer functions may cause or may require other functions or tasks to be performed, such as, for example: 1 ) for LTE Dual

Connectivity, when a link or connection to a SeNB is suspended, the RRC entity located at the MeNB must/should be informed through X2 signalling, and bearers terminated at the SeNB must be handled, possibly by also suspending these, so that the signalling gateway (S-GW) at the core network stops forwarding data, for example; 2) A multi-connectivity solution may require or involve a similar handling (similar tasks or functions being performed to suspend a bearer). However, in some cases for multi-connectivity (e.g., for 5G), the involved entities may be distributed, such that the actions may have more local impact. The various implementations, however, are not necessarily dependent on the control system being centralized or distributed.

[0064] As indicated above related to LTE, the actions that may be performed, for example, by the network in order to properly handle a suspended link may involve control plane, and may typically involve user plane in the sense that downlink data transmissions and uplink allocations may be suspended, resumed or released.

[0065] Two illustrative examples will be briefly described:

[0066] Example 1 : UE performs configured measurements and eventually meets the condition, where the autonomous mobility procedure is triggered towards the candidate T- SeNB (target SeNB). Using the proposed signalling, the UE informs the S-SeNB (source SeNB) to suspend downlink data transmission. That is, S-SeNB may be suspended using uplink control signalling (e.g., UE send a connection suspend request to S-SeNB) instead of slow RRC procedure. If the autonomous SeNB operation failed, UE can revert back the S-SeNB to continue scheduling using the same uplink control signalling approach. When the SeNB change is ready and acknowledged, the RRC protocol can continue according to current specifications and for example the S-SeNB can release the UE context.

[0067] Example 2: In 5G Multi-Connectivity the UE may use at least two independent connections. To minimize the latency of flow control related signalling, according to an example implementation, the UE may make the decision and indicate either to (one of) serving MeNB/PCell or active SeNB/SCell that UE is about to move to the next available cell/SeNB (e.g., target cell/target SeNB) or start using another available link/wireless connection at the target cell/target SeNB. The same principle of using the uplink control signalling for suspend, resume and release can be used here as well.

[0068] According to an example implementation, UE autonomous mobility operation (e.g., allowing connection requests/operations to be signalled by the UE or other network node) is described, e.g., in example cases of LTE Dual Connectivity and 4G/5G Multi- Connectivity. In one example implementation, the LTE Layer 2 (RLC) protocol stack can send and receive control signalling, e.g., the RLC protocol data units may carry the connection requests (e.g., connection suspend request, connection resume request and/or connection release request) to suspend, resume or release the SeNB data flow to the user device/UE, for example. During the suspension, the SeNB can either start buffering the incoming downlink data, or alternatively inform the other peers to

stop/suspend the bearer until the UE autonomous operation has been completed (e.g., until the wireless connection has been resumed). In another embodiment the persistent SeNB functionality can be configured with a timer (for example by the MeNB), which indicates the duration of the period, when S-SeNB is expected to suspend and preserve the UE context and configuration for the potentially leaving UE. For example, MAC, RLC, PDCP or RRC protocols can contain suspend timers in case UE is not resuming nor releasing the connection within a time limit that the suspend timer is initialized to. In another embodiment the master BS/MeNB receiving the suspension signal may suspend splitting the bearer in downlink, e.g., in the case of a split bearer. In another embodiment the BS holding RRC protocol and receiving the suspend/suspension signal by another BS may suspend splitting the bearer in downlink.

[0069] In another embodiment the base station is operating a number of remote radio heads (RRH) which operate on the same carrier, on different carriers or transmit using coordinated radio resources. In one example implementation, the control plane may be centralized and operates all RRHs. UE can suspend, resume or release wireless connections with individual RRHs using the signalling (e.g., by using the connection requests, such as connection suspend, request, connection resume request, and/or connection release request).

[0070] According to an example implementation, implementation of the control signalling (e.g., connection request) can be done at different protocol entities of the protocol stack. Implementation using PUCCH (physical uplink control channel) is extending the current UCI (Uplink Control Information) design, where a new field may be used indicating the requested mobility/connection operation (e.g., suspend, resume, release).

Implementation using PUSCH (physical uplink shared data channel) may extend the current composition, where a new field is introduced indicating the mobility/connection operation (e.g., suspend, resume, release). Current composition of PUSCH has following options, which would be extended with mobility indication or command as follows (non- limiting example), where mobility/connection signalling may also be provided:

[0071 ] User Data only

1 ) User Data + CQI (channel quality indication)

2) User Data + CQI + Rl (Rank Indication)

3) User Data + CQI + Mobility/connection signalling (e.g., connection suspend, resume, or release)

4) User Data + CQI + Rl + Mobility/connection signalling

[0072] Implementation using MAC layer introduces a new MAC PDU control element which may be delivered to BS using physical channels. This control element can contain request to stop (suspend) or resume scheduling, for example.

[0073] Implementation using RLC may introduce a new RLC Control PDU which delivers suspend, resume and release control information between RLC entities. This is the most relevant option for RLC Acknowledged Mode where the PDU format contains 1 -bit field indicating if the RLC PDU is RLC Data PDU or an RLC Control PDU. An example implementation considers RLC Control PDUs where control signalling is introduced for example as a new information element field with required number of bits. Another example implementation introduces a new RLC Control PDU type, which is indicated by the STATUS PDU format containing information about the PDU types including the new PDU type.

[0074] Implementation using Packet Data Convergence Control (PDCP) may introduce or use a new function where local mobility/connection operations, e.g., connection suspend, resume and release functions are processed. In case of local mobility (e.g. within the same MeNB coverage) the new functionality can be a local entity managing the data flows in the user plane, as well as in the control plane. In case of wide area mobility event the valid suspend, resume and release control messages can be delivered to upper network layers (e.g. MME) to take into account in handling of signalling and data bearers. Because PDCP layer is responsible transfer of data (user plane and control plane), maintenance of PDCP Sequence Numbers (SNs), header compression, security functions and in- sequence delivery of upper layer PDUs at re-establishment of lower layers, it is also a potential protocol layer for implementing the proposed control signalling (e.g., connection requests). In case of multi-connectivity, PDCP entity may provide sequence numbers for all the active links/connections, and therefore can also control the wireless connections of multiple BSs without RRC for local mobility, and in case of wide area mobility the PDCP in multi-connectivity can provide the control signals to upper layers and MME. [0075] For example, in current LTE user plane protocol stack the implementation of PDCP PDUs for user plane data comprise a 'D/C field in order to distinguish Data and Control PDUs. In this case the proposed implementation, PDCP may include a new Control PDU type which carries the proposed control signalling (e.g., the connection suspend request, connection resume request, and/or the connection release request). In another implementation a new information element bit field is added to one of the existing PDCP Control PDUs. In both cases the PDCP Control PDUs are used to control the PDCP entities handling user plane data and allowing the functions of suspend, resume and release of the data flow.

[0076] Implementation using Radio Resource Control (RRC) may contain configuration of local area mobility. The setup, maintenance and release of a connection between the UE and BS may be performed using RRC, and therefore suspend, resume and release requests from UE can delivered to RRC either directly as part of the protocol, or by encapsulating them to other messaging. For instance the PDCP defines headers allowing for encapsulation of an RRC message in a PDCP frame, which allows

transmission of an RRC packet through user plane transmission. On reception the PDCP (e.g., PDCP entity at MeNB) extracts the encapsulated packet and delivers it to the RRC entity (e.g., RRC entity of the MeNB). For such a solution the operations of suspend, resume, and release may also be introduced as new RRC messages, but adding this control information as information element fields may also be added to existing messages.

[0077] For example, for Rel-12 LTE dual connectivity where the RRC entity is located only in the MeNB, such a proposed RRC message (e.g., including the connection

requests/control signalling) would be sent by the UE to the MeNB, and the action taken by the MeNB RRC entity may then send this RRC message (e.g., including control signalling/connection request) to the SeNB, via X2 interface. So there may, for example, be a considerable latency due to the BS-to-BS forwarding of this signalling/connection request. Thus, according to an example implementation, a solution where the UE directly sends the mobility signalling/connection request to the SeNB (rather than via the MeNB) may be quicker/involve lower delay or latency than forwarding this signalling/connection request via a MeNB to the SeNB. For multi-connectivity (e.g., 5G) solution with distributed

RRC, the solution may work more efficiently, and the encapsulation in RRC message is not required, since the UE should be able to send RRC messages directly to plurality of MeNBs and SeNBs.

[0078] FIG. 4 is a diagram illustrating use of remote radio heads according to an example implementation. A remote radio head may include a mobile station or user device (e.g., UE) within a cell that performs BS functions, e.g., in the absence of a BS. In an example implementation, the suspend, resume and release of Remote Radio Head connections is shown FIG. 4 where number n of RRHs are connected to UE. For example, the UE may have active (not suspended) wireless connections with RRH 1 and RRH3 (indicated with solid lines for link 1 and link 3) and may have suspended connections with RRH2 and

RRHn (indicated by dashed or broken lines for link 2 and link n). For example, UE may measure signals for each of the RRH and use uplink control signalling to suspend, resume and/or release a wireless connection with each of the RRHs. As an example, UE is having active connections to RRH1 and RRH3, and a suspended connection towards RRH2, and UE may have also suspended potentially some other RRHs. Thereafter UE can change the status/operation of any connected state links using the uplink control signaling, e.g., UE may suspend an active connection, or resume a suspended connection, release a connection, etc.

[0079] In another embodiment the Remote Radio Heads shown FIG. 4 may form a UE specific Single Frequency Network (SFN), e.g. RRH1/Link1 , RRH2/Link2 and

RRH3/Link3, where RRH1 and RRH3 are actively transmitting and RRH2 is suspended from SFN. Resources from RRH2 are available for other users, or persistent for the UE shown in figure. When UE moves within the coverage of RRC, then UE can use suspend, resume or release the RRHs in terms of configured mobility control. The UE may also request resources from eNB/RRH, where UE is not necessarily connected to eNB/RRH.

[0080] According to another example implementation, in case of base band processing units of several cells are hosted in centralized location (baseband pool) or within one BS, then some of the protocol entities of different cells are able to communicate seamlessly. This gives yet another option of implementing the control signalling, where for example RLC/MAC protocols of different cells (RRHs) are able to communicate together without delay and share the link or connection status (suspend, resume, release) for example for joint-scheduling.

[0081 ] FIG. 5 is a diagram illustrating sending a connection suspend request or a connection resume request according to an example implementation. For example, in FIG. 5, the UE may perform signal measurements for signals received from one or more BSs/eNBs, such as from a source SeNB (S-SeNB) and a target SeNB (T-SeNB). For example, in the case of dual or multi connectivity, based on the signal measurements (e.g., signal power or quality for target SeNB is determined by UE to be better than signal power or quality of the source SeNB), the UE determines to perform a SeNB change, e.g., to replace SeNB source with SeNB target (and thus, activate/establish a new wireless connection with target SeNB and suspend or release the source SeNB). Under option A, the UE may establish a connection (e.g., via random access procedure) with target SeNB before suspending the connection with the source SeNB. While, in option B, the UE may establish a connection via random access procedure after suspending the connection with the source SeNB. For example, in order to send the connection suspend request to the source SeNB, the UE may, for example: send sounding reference signals to the source SeNB (e.g., to allow the source SeNB to measure the channel), send a scheduling request (e.g., to obtain an uplink resource), and then receive a scheduling grant from the source SeNB. The UE may then send the connection suspend request to the source SeNB via the resource obtained via the scheduling grant. SeNB change signaling may then be performed, e.g., to allow MeNB (in some cases) to release the connection with source SeNB (unless user device handles that release), and then to move or reconfigure bearers for the new connection with target SeNB, forward buffered data from source SeNB to target SeNB, for example. The same or a similar procedure may be used by a UE to send a connection resume request to the source SeNB. Note that the source SeNB and target SeNB may be located in the same local area and thus synchronization may not be needed. [0082] Therefore, according to an example implementation, uplink control signalling may include requesting the uplink resources and sending a suspend indication (e.g., a connection suspend request), in this example case using PUSCH (physical uplink shared data channel). Following the same principle, the UE can also resume back the previously suspended S-SeNB by requesting uplink resources and sending a resume indication (e.g., a connection resume request) to the source SeNB. In case of resuming back to S-SeNB (resuming the wireless connection for the source SeNB), the random access/RACH procedure may not be needed for synchronization, for example.

[0083] Also, for example, if the UE has RRC or UE context with the target cell/target SeNB (T-SeNB), in some cases the UE may directly request a new cell/new connection with target SeNB using the proposed uplink control signalling. In this case the uplink control signalling includes resource request and a resume indication/connection resume and would be sent to T-SeNB instead of S-SeNB. This is useful for example if the T-SeNB is located in the same local area and thus synchronization may not be needed.

[0084] FIG. 6 is a diagram illustrating sending a connection release request according to an example implementation. The procedure in FIG. 6 for a release operation may be very similar to the procedure shown in FIG. 5, including signal measurements, sending sounding reference signals, sending a scheduling request, receiving a scheduling grant, sending (from the UE to the source SeNB) the release indication, and SeNB release signaling being performed.

[0085] Therefore, the various example implementations may have a number of advantages, including, for example:

[0086]

Reduced latency in control signalling between UE and network.

· Maintaining protocol consistency between UE and MeNB/SeNB.

Minor additional air interface signalling load.

Some of the autonomous mobility (connection request signals) signalling between UE and S-SeNB can be done without RRC protocol.

Suspended SeNB can be re-activated (resumed), for example in a case where handover towards T-SeNB fails

Method supports local mobility in distributed architecture even if the control plane is centralized.

Method enables layered mobility where the local are mobility is done using the proposed signalling and the wide area mobility using the existing mobility mechanisms.

[0087] FIG. 7 is a flow chart illustrating operation of a network node according to an example implementation. In an example implementation, a network node may include a user device (UE), a BS, or other node. Operation 710 may include establishing a wireless connection between a first network node and a second network node. Operation 720 may include controlling receiving signals by the first network node from one or more other network nodes. And, operation 730 may include controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[0088] According to an example implementation of the method of FIG. 7, the message may include a first message, the method further includes: controlling sending, by the first network node to the second network node, a second message including a connection resume request that indicates a request by the first network node to the second network node to resume the wireless connection between the first network node and the second network node.

[0089] According to an example implementation of the method of FIG. 7, the message may include a first message, the method further including: controlling sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the wireless connection between the first network node and the second network node.

[0090] According to an example implementation of the method of FIG. 7, wherein the establishing a wireless connection between a first network node and a second network node may include: performing a random access procedure between the first network node and the second network node to establish the wireless connection.

[0091 ] According to an example implementation of the method of FIG. 7, wherein the wireless connection includes a first wireless connection, and wherein the controlling receiving signals may include: controlling receiving signals by the first network node from at least the second network node and a third network node; wherein the method further includes: selecting, based on the received signals, the third wireless node; and establishing, by the first network node, a second wireless connection between the first network node and the third network node.

[0092] According to an example implementation of the method of FIG. 7, the message includes a first message, the method further including: controlling sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the first wireless connection between the first network node and the second network node.

[0093] According to an example implementation of the method of FIG. 7, the first network node includes a user device, and the second network node includes a base station.

[0094] According to an example implementation of the method of FIG. 7, the first network node includes a base station, and the second network node includes a user device.

[0095] According to an example implementation of the method of FIG. 7, wherein the first network node includes a user device and the second network node comprises a secondary base station, wherein: the establishing includes establishing a wireless connection between the user device and the secondary base station; wherein the controlling receiving includes controlling receiving signals by the user device from one or more base stations; and wherein the controlling sending includes controlling sending, by the user device to the secondary base station, a message including a connection suspend request that indicates a request by the user device to the secondary base station to suspend the wireless connection between the user device and the secondary base station.

[0096] According to an example implementation of the method of FIG. 7, the controlling sending includes: controlling sending, by the first network node to the second network node via a third network node, a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[0097] According to an example implementation of the method of FIG. 7, the first network node includes a user device and the second network node includes a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein the controlling sending includes: controlling sending, by the user device to the secondary base station via a master base station, a connection suspend request that indicates a request by the to suspend the wireless connection between the user device and the secondary base station.

[0098] According to an example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: establish a wireless connection between a first network node and a second network node, control receiving signals by the first network node from one or more other network nodes, and control sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[0099] According to an example implementation of the apparatus, the message may include a first message, the apparatus is further caused to: control sending, by the first network node to the second network node, a second message including a connection resume request that indicates a request by the first network node to the second network node to resume the wireless connection between the first network node and the second network node.

[00100] According to an example implementation of the apparatus, the message may include a first message, apparatus further caused to: control sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the wireless connection between the first network node and the second network node.

[00101 ] According to an example implementation of the apparatus, wherein the apparatus being caused to establish a wireless connection between a first network node and a second network node may include causing the apparatus to perform a random access procedure between the first network node and the second network node to establish the wireless connection.

[00102] According to an example implementation of the apparatus, wherein the wireless connection includes a first wireless connection, and wherein causing the apparatus to control receiving signals may include causing the apparatus to: control receiving signals by the first network node from at least the second network node and a third network node; wherein the apparatus is further caused to: select, based on the received signals, the third wireless node; and establish, by the first network node, a second wireless connection between the first network node and the third network node.

[00103] According to an example implementation of the apparatus, the message includes a first message, the apparatus is further caused to: control sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the first wireless connection between the first network node and the second network node.

[00104] According to an example implementation of the apparatus, the first network node includes a user device, and the second network node includes a base station.

[00105] According to an example implementation of the apparatus, the first network node includes a base station, and the second network node includes a user device.

[00106] According to an example implementation of the apparatus, wherein the first network node includes a user device and the second network node includes a secondary base station, wherein causing the apparatus to establish includes causing the apparatus to establish a wireless connection between the user device and the secondary base station; wherein causing the apparatus to control receiving includes causing the apparatus to control receiving signals by the user device from one or more base stations; and wherein causing the apparatus to control sending includes causing the apparatus to control sending, by the user device to the secondary base station, a message including a connection suspend request that indicates a request by the user device to the secondary base station to suspend the wireless connection between the user device and the secondary base station.

[00107] According to an example implementation of the apparatus, causing the apparatus to control sending includes: causing the apparatus to control sending, by the first network node to the second network node via a third network node, a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00108] According to an example implementation of the apparatus, the first network node includes a user device and the second network node includes a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein causing the apparatus to control sending includes causing the apparatus to control sending, by the user device to the secondary base station via a master base station, a connection suspend request that indicates a request by the to suspend the wireless connection between the user device and the secondary base station.

[00109] According to another example implementation, a computer program product includes a non-transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: establishing a wireless connection between a first network node and a second network node, controlling receiving signals by the first network node from one or more other network nodes, and controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node. Also, any of the method operations described herein may be applied to the computer program product.

[001 10] According to another example implementation, an apparatus may include means (902A/902B, 904, FIG. 9) for establishing a wireless connection between a first network node and a second network node, means (902A/902B, 904, FIG. 9) for controlling receiving signals by the first network node from one or more other network nodes, and means (902A/902B, 904, FIG. 9) for controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[001 1 1 ] According to an example implementation of the apparatus, the message may include a first message, the apparatus further includes: means (902A/902B, 904, FIG. 9) for controlling sending, by the first network node to the second network node, a second message including a connection resume request that indicates a request by the first network node to the second network node to resume the wireless connection between the first network node and the second network node.

[001 12] According to an example implementation of the apparatus, the message may include a first message, the apparatus further including: means (902A/902B, 904, FIG. 9) for controlling sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the wireless connection between the first network node and the second network node.

[001 13] According to an example implementation of the apparatus, wherein the means for establishing a wireless connection between a first network node and a second network node may include: means (902A/902B, 904, FIG. 9) for performing a random access procedure between the first network node and the second network node to establish the wireless connection.

[001 14] According to an example implementation of the apparatus, wherein the wireless connection includes a first wireless connection, and wherein the means for controlling receiving signals may include: means (902A/902B, 904, FIG. 9) for controlling receiving signals by the first network node from at least the second network node and a third network node; wherein the method further includes: means (902A/902B, 904, FIG. 9) for selecting, based on the received signals, the third wireless node; and means

(902A/902B, 904, FIG. 9) for establishing, by the first network node, a second wireless connection between the first network node and the third network node.

[001 15] According to an example implementation of the apparatus, the message includes a first message, the apparatus further including: means (902A/902B, 904, FIG. 9) for controlling sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the first wireless connection between the first network node and the second network node.

[001 16] According to an example implementation of the apparatus, the first network node includes a user device, and the second network node includes a base station.

[001 17] According to an example implementation of apparatus, the first network node includes a base station, and the second network node includes a user device.

[001 18] According to an example implementation of the apparatus, wherein the first network node includes a user device and the second network node comprises a secondary base station, wherein: the means for establishing includes means (902A/902B, 904, FIG. 9) for establishing a wireless connection between the user device and the secondary base station; wherein the means for controlling receiving includes means (902A/902B, 904, FIG. 9) for controlling receiving signals by the user device from one or more base stations; and wherein the means for controlling sending includes means (902A/902B, 904, FIG. 9) for controlling sending, by the user device to the secondary base station, a message including a connection suspend request that indicates a request by the user device to the secondary base station to suspend the wireless connection between the user device and the secondary base station.

[001 19] According to an example implementation of the apparatus, the means for controlling sending includes: means (902A/902B, 904, FIG. 9) for controlling sending, by the first network node to the second network node via a third network node, a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00120] According to an example implementation of the apparatus, the first network node includes a user device and the second network node includes a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein the means for controlling sending includes: means (902A/902B, 904, FIG. 9) for controlling sending, by the user device to the secondary base station via a master base station, a connection suspend request that indicates a request by the to suspend the wireless connection between the user device and the secondary base station.

[00121 ] FIG. 8 is a flow chart illustrating operation of a network node according to another example implementation. Operation 810 may include establishing a wireless connection between a first network node and a second network node. Operation 820 may include controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00122] According to an example implementation of the method of FIG. 8, the controlling receiving may include: controlling receiving, by the second network node from the first network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[00123] According to an example implementation of the method of FIG. 8, the controlling receiving may include: controlling receiving, by the second network node from a third network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00124] According to an example implementation of the method of FIG. 8, wherein the first network node includes a user device, and the second network node includes a base station.

[00125] According to an example implementation of the method of FIG. 8, the first network node includes a base station, and the second network node includes a user device.

[00126] According to an example implementation of the method of FIG. 8, wherein the message includes a first message, the method further including: controlling receiving, by the second network node, a second message including a connection resume request that indicates a request to resume the wireless connection between the first network node and the second network node.

[00127] According to an example implementation of the method of FIG. 8, wherein the message includes a first message, the method further including: controlling receiving, by the second network node, a second message including a connection release request that indicates a request to release the wireless connection between the first network node and the second network node.

[00128] According to an example implementation of the method of FIG. 8, the establishing a wireless connection between a first network node and a second network node includes: performing a random access procedure between the first network node and the second network node to establish the wireless connection.

[00129] According to an example implementation of the method of FIG. 8, wherein the method further includes activating, by the second network node, a connection suspend timer for the wireless connection based upon receiving the connection suspend request; and releasing, by the second network node, the wireless connection if the connection suspend timer expires before the second network node receives a connection resume request for the wireless connection.

[00130] According to an example implementation of the method of FIG. 8, the first network node includes a user device and the second network node includes a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein: the establishing includes establishing a wireless connection between the user device and the secondary base station; wherein the controlling receiving includes controlling receiving, by the secondary base station, a message including a connection suspend request that indicates a request to suspend the wireless connection between the user device and the secondary base station.

[00131 ] According to an example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: establish a wireless connection between a first network node and a second network node; and control receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00132] According to an example implementation of the apparatus, wherein causing the apparatus to control receiving includes causing the apparatus to: control receiving, by the second network node from a third network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00133] According to an example implementation of the apparatus, wherein the first network node comprises a user device, and the second network node comprises a base station. According to an example implementation of the apparatus, wherein the first network node comprises a base station, and the second network node comprises a user device.

[00134] According to an example implementation of the apparatus, wherein the message comprises a first message, the apparatus being further caused to: control receiving, by the second network node, a second message including a connection resume request that indicates a request to resume the wireless connection between the first network node and the second network node.

[00135] According to an example implementation of the apparatus, wherein the message comprises a first message, the apparatus being further caused to: control receiving, by the second network node, a second message including a connection release request that indicates a request to release the wireless connection between the first network node and the second network node.

[00136] According to an example implementation of the apparatus, the apparatus being further caused to: activate, by the second network node, a connection suspend timer for the wireless connection based upon receiving the connection suspend request; and release, by the second network node, the wireless connection if the connection suspend timer expires before the second network node receives a connection resume request for the wireless connection.

[00137] According to another example implementation, a computer program product includes a non-transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: establishing a wireless connection between a first network node and a second network node, and controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node. Also, any of the method operations described herein may be applied to the computer program product.

[00138] According to another example implementation, an apparatus may include means (902A/902B, 904, FIG. 9) for establishing a wireless connection between a first network node and a second network node, and means for controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00139] According to an example implementation of the apparatus, the means for controlling receiving may include: means (902A/902B, 904, FIG. 9) for controlling receiving, by the second network node from the first network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

[00140] According to an example implementation of the apparatus, the means for controlling receiving may include: means (902A/902B, 904, FIG. 9) for controlling receiving, by the second network node from a third network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

[00141 ] According to an example implementation of the apparatus, wherein the first network node includes a user device, and the second network node includes a base station. According to an example implementation of the apparatus, the first network node includes a base station, and the second network node includes a user device.

[00142] According to an example implementation of the apparatus, wherein the message includes a first message, the apparatus further including: means (902A/902B, 904, FIG. 9) for controlling receiving, by the second network node, a second message including a connection resume request that indicates a request to resume the wireless connection between the first network node and the second network node.

[00143] According to an example implementation of the apparatus, wherein the message includes a first message, the apparatus further including: means (902A/902B, 904, FIG. 9) for controlling receiving, by the second network node, a second message including a connection release request that indicates a request to release the wireless connection between the first network node and the second network node.

[00144] According to an example implementation of the apparatus, the means for establishing a wireless connection between a first network node and a second network node includes: means (902A/902B, 904, FIG. 9) for performing a random access procedure between the first network node and the second network node to establish the wireless connection. [00145] According to an example implementation of the apparatus, wherein the apparatus further includes means (902A/902B, 904, FIG. 9) for activating, by the second network node, a connection suspend timer for the wireless connection based upon receiving the connection suspend request; and means (902A/902B, 904, FIG. 9) for releasing, by the second network node, the wireless connection if the connection suspend timer expires before the second network node receives a connection resume request for the wireless connection.

[00146] According to an example implementation of the apparatus, the first network node includes a user device and the second network node includes a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein: the means for establishing includes means (902A/902B, 904, FIG. 9) for establishing a wireless connection between the user device and the secondary base station; wherein the means for controlling receiving includes means (902A/902B, 904, FIG. 9) for controlling receiving, by the secondary base station, a message including a connection suspend request that indicates a request to suspend the wireless connection between the user device and the secondary base station.

[00147] FIG. 9 is a block diagram of a network node (e.g., BS or user device) 900 according to an example implementation. The network node (or wireless station) 900 may include, for example, two RF (radio frequency) or wireless transceivers 902A, 902B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor 904 to execute instructions or software and control transmission and receptions of signals, and a memory 906 to store data and/or instructions.

[00148] Processor 904 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 904, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 902. Processor 904 may control transmission of signals or messages over a wireless network, and may receive signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 902, for example). Processor 904 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 904 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 904 and transceiver 902 together may be considered as a wireless transmitter/receiver system, for example.

[00149] In addition, referring to FIG. 9, a controller (or processor) 908 may execute software and instructions, and may provide overall control for the network node 900, 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 network node 900, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.

[00150] 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 904, or other controller or processor, performing one or more of the functions or tasks described above.

[00151 ] The embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other

communication systems. Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced or it may be one radio access system of multiple radio access systems utilized in 5G. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[00152] It should be appreciated that future networks will most probably utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.

[00153] Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may 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. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).

[00154] 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.

[00155] Furthermore, implementations 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 implementation 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 implementations of techniques described herein may be provided via one or more of these technologies.

[00156] 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 stand alone 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.

[00157] 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).

[00158] 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, magneto optical 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. [00159] To provide for interaction with a user, implementations 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.

[00160] Implementations may be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back end, middleware, or front end 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.

[00161 ] While certain features of the described implementations 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 . A method comprising:

establishing a wireless connection between a first network node and a second network node;

controlling receiving signals by the first network node from one or more other network nodes; and

controlling sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

2. The method of claim 1 , wherein the message comprises a first message, the method further comprising:

controlling sending, by the first network node to the second network node, a second message including a connection resume request that indicates a request by the first network node to the second network node to resume the wireless connection between the first network node and the second network node.

3. The method of claim 1 , wherein the message comprises a first message, the method further comprising:

controlling sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the wireless connection between the first network node and the second network node.

4. The method of claim 1 wherein the establishing a wireless connection between a first network node and a second network node comprises:

performing a random access procedure between the first network node and the second network node to establish the wireless connection.

5. The method of claim 1 , wherein the wireless connection comprises a first wireless connection, and wherein the controlling receiving signals comprises:

controlling receiving signals by the first network node from at least the second network node and a third network node; wherein the method further comprises:

selecting, based on the received signals, the third wireless node; and

establishing, by the first network node, a second wireless connection between the first network node and the third network node.

6. The method of claim 5, wherein the message comprises a first message, the method further comprising:

controlling sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the first wireless connection between the first network node and the second network node.

7. The method of claim 1 wherein the first network node comprises a user device, and the second network node comprises a base station.

8. The method of claim 1 wherein the first network node comprises a base station, and the second network node comprises a user device.

9. The method of claim 1 wherein the first network node comprises a user device and the second network node comprises a secondary base station, wherein:

the establishing comprises establishing a wireless connection between the user device and the secondary base station;

wherein the controlling receiving comprises controlling receiving signals by the user device from one or more base stations; and

wherein the controlling sending comprises controlling sending, by the user device to the secondary base station, a message including a connection suspend request that indicates a request by the user device to the secondary base station to suspend the wireless connection between the user device and the secondary base station.

10. The method of claim 1 wherein the controlling sending comprises:

controlling sending, by the first network node to the second network node via a third network node, a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

1 1 . The method of claim 1 wherein the first network node comprises a user device and the second network node comprises a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein the controlling sending comprises:

controlling sending, by the user device to the secondary base station via a master base station, a connection suspend request that indicates a request by the to suspend the wireless connection between the user device and the secondary base station.

12. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:

establish a wireless connection between a first network node and a second network node; control receiving signals by the first network node from one or more other network nodes; and

control sending, by the first network node to the second network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

13. The apparatus of claim 12, wherein the message comprises a first message, wherein the apparatus is further caused to:

control sending, by the first network node to the second network node, a second message including a connection resume request that indicates a request by the first network node to the second network node to resume the wireless connection between the first network node and the second network node.

14. The apparatus of claim 12, wherein the message comprises a first message, wherein the apparatus is further caused to:

control sending, by the first network node to the second network node, a second message including a connection release request that indicates a request by the first network node to the second network node to release the wireless connection between the first network node and the second network node.

15. The apparatus of claim 12, wherein the establishing a wireless connection between a first network node and a second network node comprises: performing a random access procedure between the first network node and the second network node to establish the wireless connection.

16. The apparatus of claim 12, wherein the wireless connection comprises a first wireless connection, and wherein the controlling receiving signals comprises:

controlling receiving signals by the first network node from at least the second network node and a third network node;

wherein the method further comprises:

selecting, based on the received signals, the third wireless node; and

17. The apparatus of claim 12, wherein the controlling sending comprises:

18. A computer program product, the computer program product comprising a non- transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising:

19. A method comprising:

establishing a wireless connection between a first network node and a second network node; and controlling receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

20. The method of claim 19 wherein the controlling receiving comprises:

controlling receiving, by the second network node from the first network node, a message including a connection suspend request that indicates a request by the first network node to the second network node to suspend the wireless connection between the first network node and the second network node.

21 . The method of claim 19 wherein the controlling receiving comprises:

controlling receiving, by the second network node from a third network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

22. The method of claim 19 wherein the first network node comprises a user device, and the second network node comprises a base station.

23. The method of claim 19 wherein the first network node comprises a base station, and the second network node comprises a user device.

24. The method of claim 19, wherein the message comprises a first message, the method further comprising:

controlling receiving, by the second network node, a second message including a connection resume request that indicates a request to resume the wireless connection between the first network node and the second network node.

25. The method of claim 19, wherein the message comprises a first message, the method further comprising:

controlling receiving, by the second network node, a second message including a connection release request that indicates a request to release the wireless connection between the first network node and the second network node.

26. The method of claim 19 wherein the establishing a wireless connection between a first network node and a second network node comprises:

27. The method of claim 19 and further comprising:

activating, by the second network node, a connection suspend timer for the wireless connection based upon receiving the connection suspend request; and

releasing, by the second network node, the wireless connection if the connection suspend timer expires before the second network node receives a connection resume request for the wireless connection.

28. The method of claim 19 wherein the first network node comprises a user device and the second network node comprises a secondary base station in a dual-connectivity or multi-connectivity arrangement with respect to the user device, wherein :

the establishing comprises establishing a wireless connection between the user device and the secondary base station ;

wherein the controlling receiving comprises controlling receiving, by the secondary base station, a message including a connection suspend request that indicates a request to suspend the wireless connection between the user device and the secondary base station.

29. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:

establish a wireless connection between a first network node and a second network node; and

control receiving, by the second network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

30. The apparatus of claim 29 wherein causing the apparatus to control receiving comprises causing the apparatus to: control receiving, by the second network node from a third network node, a message including a connection suspend request that indicates a request to suspend the wireless connection between the first network node and the second network node.

31 . The apparatus of claim 29 wherein the first network node comprises a user device, and the second network node comprises a base station.

32. The apparatus of claim 29 wherein the first network node comprises a base station, and the second network node comprises a user device.

33. The apparatus of claim 29, wherein the message comprises a first message, the apparatus being further caused to:

control receiving, by the second network node, a second message including a connection resume request that indicates a request to resume the wireless connection between the first network node and the second network node.

34. The apparatus of claim 29, wherein the message comprises a first message, the apparatus being further caused to:

control receiving, by the second network node, a second message including a connection release request that indicates a request to release the wireless connection between the first network node and the second network node.

35. The apparatus of claim 29, the apparatus being further caused to:

activate, by the second network node, a connection suspend timer for the wireless connection based upon receiving the connection suspend request; and

release, by the second network node, the wireless connection if the connection suspend timer expires before the second network node receives a connection resume request for the wireless connection.

36. A computer program product, the computer program product comprising a non- transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising:

37. An apparatus comprising means for carrying out the method according to any of claims 1 to 1 1 and/or 19 to 28.

38. A computer program product for a computer, comprising software code portions for performing the steps of any of claims 1 to 1 1 and/or 19 to 28, when said product is run on the computer.