Patent Application
20220141730
Embodiments of the disclosure relate wireless communications, and particularly to methods and apparatus relating to mobility between cells in a wireless network.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.
Non-terrestrial networks (NTNs) refer to networks, or segments of networks, using an airborne or spaceborne vehicle for transmission. Airborne vehicles may include high altitude platforms (HAPs) such as unmanned aircraft systems (UASs) including tethered UASs, lighter-than-air UASs, and heavier-than-air UASs. Spaceborne vehicles may include satellites in orbit around the Earth, e.g., in low Earth orbit (LEO), medium Earth orbit (MEO) or geostationary Earth orbit (GEO). The airborne or spaceborne vehicle may be used for transmission by implementing a network node (e.g., base station, etc) on the airborne or spaceborne vehicle itself (e.g., such that the network node is an airborne or spaceborne network node). Thus, in such examples, a wireless device or UE communicates directly with the airborne or spaceborne network node to access the services of the network. Alternatively, the network node (e.g., base station, etc) may be implemented on the ground, but transmissions between the wireless device or UE and the network node are indirect and travel via a simple forwarding or repeating mechanism on the airborne or spaceborne vehicle. Both of these examples are discussed in more detail below.
There is an ongoing resurgence of satellite communications. Several plans for satellite networks have been announced in the past few years. The target services vary, from backhaul and fixed wireless, to transportation, to outdoor mobile, to Internet of Things (IoT). Satellite networks could complement mobile networks on the ground by providing connectivity to underserved areas and multicast/broadcast services.
To benefit from the strong mobile ecosystem and economy of scale, satellite networks for terrestrial wireless access technologies including Long Term Evolution (LTE) and New Radio (NR) are drawing significant interest. For example, the Third Generation Partnership Project (3GPP) completed an initial study in Release 15 on adapting NR to support non-terrestrial networks (mainly satellite networks); see TR 38.811, Study on New Radio (NR) to support non-terrestrial networks. This initial study focused on the channel model for the non-terrestrial networks, defining deployment scenarios, and identifying the key potential impacts. 3GPP is conducting a follow-up study item in Release 16 on solutions evaluation for NR to support non-terrestrial networks (RP-181370, Study on solutions evaluation for NR to support non-terrestrial Network).
A satellite radio access network may include one or more of the following components:
The link from gateway to terminal is often called forward link, and the link from terminal to gateway is often called return link. Depending on the functionality of the satellite in the system, we can consider two transponder options
Depending on the orbit altitude, a satellite may be categorized as LEO, MEO, or GEO satellite.
A satellite typically generates several beams over a given area. The footprint of a beam is usually an elliptic shape, which has been traditionally considered as a cell. The footprint of a beam is also often referred to as a spotbeam. The footprint of a spotbeam may move over the Earth's surface with the satellite movement or may be fixed on the Earth's surface with some beam pointing mechanism used by the satellite to compensate for its motion. The size of a spotbeam depends on the system design, and may range from tens of kilometers to a few thousands of kilometers.
The two main physical phenomena that affect satellite communications system design are the long propagation delay and Doppler effects. The Doppler effects are especially pronounced for LEO satellites.
Propagation delay is one main physical phenomenon in a satellite communication system that makes the design different from that of a terrestrial mobile system. For a bent pipe satellite network, the following delays are relevant.
Note that there may be additional delay between the ground BS antenna and BS, which may or may not be collocated. This delay depends on deployment. If the delay cannot be ignored, it should be taken into account in the communications system design.
The propagation delay depends on the length of the signal path, which further depends on the elevation angles of the satellite seen by the BS and UE on the ground. The minimum elevation angle is typically more than 10° for UE and more than 5° for BS on the ground.
The following Tables 1 and 2 are taken from 3GPP TR 38.811. We can see that the round-trip delay is much larger in satellite systems. For example, it is about 545 ms for a GEO satellite system. In contrast, the round-trip time is normally no more than 1 ms for typical terrestrial cellular networks.
Generally, within a spot beam covering one cell, the delay can be divided into a common delay component and a differential delay component. The common delay is the same for all UEs in the cell and is determined with respect to a reference point in the spot beam. In contrast, the differential delay is different for different UEs which depends on the propagation delay between the reference point and the point at which a given UE is positioned within the spot beam.
The differential delay is mainly due to the different path lengths of the access links, since the feeder link is normally the same for terminals in the same spotbeam. Further, the differential delay is mainly determined by the size of the spotbeam. It may range from sub-millisecond (for spotbeam on the order of tens of kilometres) to tens of millisecond (for spotbeam on the order of thousands of kilometres).
In RAN #80, a new study item (SI) “Solutions for NR to support Non-Terrestrial Network” was agreed. It is a continuation of a preceding SI “NR to support Non-Terrestrial Networks” (RP-171450), where the objective was to study the channel model for the non-terrestrial networks, to define deployment scenarios, parameters and identify the key potential impacts on NR. The results are reflected in TR 38.811.
The objectives of the current SI are to evaluate solutions for the identified key impacts from the preceding SI and to study impact on radio access network (RAN) protocols/architecture.
The coverage pattern of NTN is described in TR 38.811 in Section 4.6 as follows:
Satellite or aerial vehicles typically generate several beams over a given area. The foot print of the beams is typically elliptic shape.
The beam footprint may be moving over the earth with the satellite or the aerial vehicle motion on its orbit. Alternatively, the beam foot print may be earth fixed, in such case some beam pointing mechanisms (mechanical or electronic steering feature) will compensate for the satellite or the aerial vehicle motion.
Typical beam patterns of various NTN access networks are shown in
The TR of the ongoing SI, TR 38.821, describes scenarios for the NTN work as follows:
Non-Terrestrial Network typically features the following elements:
Four scenarios are considered as depicted in Table 4.2-1 and are detailed in Table 4.2-2.
For scenario D, which is LEO with regenerative payload, both Earth-fixed and Earth-moving beams have been listed. So, when we factor in the fixed/non-fixed beams, we have an additional scenario. The complete list of 5 scenarios in 3GPP TR 38.821 is then:
Scenario A—GEO, transparent satellite, Earth-fixed beams;
Scenario B—GEO, regenerative satellite, Earth fixed beams;
Scenario C—LEO, transparent satellite, Earth-moving beams;
Scenario D1—LEO, regenerative satellite, Earth-fixed beams;
Scenario D2—LEO, regenerative satellite, Earth-moving beams.
A UE in connected mode is typically configured to measure and report the radio environment in its serving cell and neighboring cells. When the quality of the serving cell is below a certain threshold and the quality of a neighbor cell is above, the network may instruct the UE to perform a Hand Over (HO) by sending a HO command to the UE which then drops the connection to the serving cell (source) and initiates access to the neighbor (target) cell. During the attach procedure to the target cell, which could include synchronization, reading system information and the access attempt, the UE is interrupted from uplink (UL) and downlink (DL) transmission until the connection to the target cell is established.
In later LTE releases, this procedure has been optimized to allow the UE to keep its connection to the source cell until the actual access attempt is initiated, i.e. when the random-access preamble is transmitted in the target cell. This allows for a decreased interruption time so that the UE can maintain data transaction for a longer time. When the UE, as part of the handover procedure, performs a first transmission to the target cell it will first release its connection to the source cell.
There currently exist certain challenge(s).
Existing mobility procedures have been designed for terrestrial networks where the round-trip/propagation delay is restricted to be within one or a few milliseconds. For UEs in cells experiencing longer delays, e.g. such as a satellite communication system, the interruption time at HO is related to the propagation delay.
A UE connected to a non-terrestrial network (NTN), e.g. a GEO satellite system, may experience a round-trip time (RTT) around 550 ms which will interrupt the data transmission for several RTTs before the connections are up and running with the target Cell.
5. The total delay is (2Tp+T1+T2).
We now highlight the main issues with existing HO process for cells with large propagation delays.
In short, the existing HO mechanism is ill-suited to networks with large propagation delays, such as NTNs.
Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.
The proposed solutions introduce methods enabling a UE to maintain the connection to the source cell during a handover to a target cell suffering from long (propagation) delays, thus allowing for continued data reception/transmission in the source cell while the UE is not able to receive/transmit in the target cell. The use of the source cell connection may be limited to only some occasions, such as occasions where the UE is waiting for a response from the target cell, allowing the source cell connection to be maintained/used even by a UE without dual connection capability. The use of the source cell connection during the handover, including what specific occasions it shall be used, may be configured by the network.
There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.
One aspect of the disclosure provides a method performed by a wireless device for performing handover from a source network node to a target network node. The method comprises: obtaining an indication of a round-trip time for transmissions to the target network node; initiating access to the target network node; and, subsequent to initiating access to the target network node, transmitting data to or receiving data from the source network node for a time window following initiation of access to the target network node. The time window has a duration of at least the round-trip time for transmissions to the target network node.
Apparatus for performing the method set out above is also provided. For example, in one aspect there is provided a wireless device. The wireless device comprises: power supply circuitry configured to supply power to the wireless device; and processing circuitry configured to, when performing handover of the wireless device from a source network node to a target network node: obtain an indication of a round-trip time for transmissions to the target network node; initiate access to the target network node; and, subsequent to initiating access to the target network node, transmit data to or receive data from the source network node for a time window following initiation of access to the target network node. The time window has a duration of at least the round-trip time for transmissions to the target network node.
A further aspect of the disclosure provides a method performed by a source network node during handover of a wireless device from the source network node to a target network node. The method comprises: obtaining an indication of a round-trip time for transmissions from the wireless device to the target network node; and, subsequent to the wireless device initiating access to the target network node, transmitting data to or receiving data from the wireless device for a time window following the initiation of access to the target network node. The time window has a duration of at least the round-trip time for transmissions from the wireless device to the target network node.
Apparatus for performing the method set out above is also provided. For example, in one aspect there is provided a network node. The network node comprises processing circuitry configured to, when performing handover of a wireless device from the network node, acting as source network node, to a target network node: obtain an indication of a round-trip time for transmissions from the wireless device to the target network node; and, subsequent to the wireless device initiating access to the target network node, transmit data to or receive data from the wireless device for a time window following the initiation of access to the target network node. The time window has a duration of at least the round-trip time for transmissions from the wireless device to the target network node.
Another aspect of the disclosure provides a method performed by a target network node relating to handover of a wireless device from a source network node to the target network node. The method comprises: causing transmission, to the source network node, of an indication of a time window following initiation of access to the target network node by the wireless device, in which the source network node is to transmit data to or receive data from the wireless device.
Apparatus for performing the method set out above is also provided. For example, in one aspect there is provided a network node. The network node comprises processing circuitry configured to, when performing handover of a wireless device to the network node, acting as a target network node, from a source network node: cause transmission, to the source network node, of an indication of a time window following initiation of access to the network node by the wireless device, in which the source network node is to transmit data to or receive data from the wireless device.
Certain embodiments may provide one or more technical advantage(s), including significantly decreased interruption times at handovers to a target cell that is suffering from long delays, such as cells belonging to a non-terrestrial network. Certain embodiments may also limit the memory requirements on the network nodes and UEs in a satellite system and improve the end-to-end user experience.
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
According to embodiments of the disclosure, the UE maintains its connection to the source cell, after it has initiated access to the target cell, by performing receptions/transmissions in the source cell while waiting (due to target cell RTT) for responses in the target cell. This allows the UE to perform reception and/or transmission in one of the cells at a time but still continue reception/transmission in the source cell after initiating access in the target cell. This concept is illustrated in the signaling diagrams of
The left-hand side of
The right-hand side of
After the source network node transmits the handover command or trigger to the UE (and/or the UE requests handover), the connection between the source network node and the UE remains valid and data continues to be transmitted between them. The illustrated embodiment shows only DL data being transmitted from the source network node to the UE, although those skilled in the art will appreciate that UL data may additionally or alternatively be transmitted from the UE to the source network node. Those skilled in the art will also appreciate that the transmissions may utilize radio resources which are scheduled or granted via transmissions on a control channel such as the Physical Downlink Control Channel (PDCCH), e.g., via Downlink Control Information (DCI) messages.
The data transmissions between the source network node and the UE may continue for a time window after access has been initiated to the target network node (e.g., a RA message has been transmitted). The time window may extend for approximately one RTT in the target network node (e.g., for non-contention-based random access in the target cell) or, as in the illustrated embodiment, approximately two RTTs in the target network node (e.g., for contention-based random access). After the time window has ended, the transmissions between the UE and the source network node may cease, with further data transmissions taking place between the UE and the target network node.
It will be noted that at certain times during the time window, no data transmissions take place between the UE and the source network node. These times may correspond to those times at which the UE is performing transmissions in the target cell, e.g., as part of the random access procedure. For example, the times may correspond to times at which the UE is monitoring for a random access response message (RAR or Msg2) from the target network node. Thus the time window may comprise one or more breaks in which data transmissions between the UE and the source network node do not take place.
One possible implementation of this embodiment is described as follows.
After the source network node sends the HO command to the UE, it continues UL and DL communication (e.g., on the Physical Uplink Shared Channel (PUSCH) and the Physical Downlink Shared Channel (PDSCH), respectively) by indicating uplink grants or downlink assignments on the PDCCH. In one embodiment, the UE monitors PDCCH for UL/DL traffic in the source cell according to the serving cell configuration prior to HO command (which may include specific PDCCH/Coreset configuration for this purpose). Any preconfigured transmission such as measurement reports, configured scheduling etc. may also be maintained in the source cell.
The UE consequently monitors and receives in the DL and transmits in the UL of the source cell continuously with the exception for when it needs to perform a transmission or reception in the target cell that makes it unable to monitor the DL or transmit in the UL in the source cell at the same time. For example, after transmission of the random-access preamble (Msg1) to the target network node, the UE may monitor (including receive/transmit in) the source cell connection during the time period of around one RTT in the target cell, since during that time it will not receive Random Access Response (RAR) message (Msg2) in the target cell, see
The UE should thus be informed about the minimum propagation delay and/or the minimum waiting time T for the target cell during the handover procedure (before initiating the access in the target cell) or before the start of the handover procedure. For example, the UE may be informed about the target cell minimum propagation delay and/or minimum waiting time T in the Handover Command message, which may be included in the RRCConnectionReconfiguration message in LTE or the RRCReconfiguration message in NR. Alternatively, the value of the target cell minimum propagation delay and/or minimum waiting time T may be broadcasted in target cell system information.
In some embodiments, the source network node may take into account knowledge of when the UE may be occupied by sending/receiving in the target cell, for UL/DL communication in the source cell (e.g., when indicating uplink grants or downlink assignments on the PDCCH). For example, the source network node may be informed of the Random Access occasions in the target cell and pause any scheduling during such occasions in order to avoid lost packets/resources. The source network node may be informed about the target cell's access information during the handover procedure, e.g. in the Handover Request Ack message from the target network node or the wireless device.
In case contention based random access (CBRA) is used in the target cell the UE needs to send Msg3 and then wait for a time period related to the RTT (or T) in the target cell before it receives confirmation from the target node (Msg4) that completes the contention resolution. No transmission/reception can therefore typically be performed in the target cell until Msg4 has been received. During this wait time, i.e. between transmission of Msg3 and reception of Msg4, the UE can then continue its connection with the source cell and reduce the interruption even further.
After the HO command is sent to the UE, configuring a HO using CBRA in the target cell (node), the source node continues to schedule the UE for a time period of 3/2 RTT ms or until notified. The source node then pauses transmissions to and/or scheduling of the UE for the length of the RAR window of the target cell, knowing that the UE will then be monitoring the target Cell. The source node then restarts the transmission to and/or scheduling of the UE for RTT ms while the UE waits for Msg4 from the target cell. The source node may be informed that the HO includes use of CBRA in the target cell from the target node in the HO Request Ack message, or by checking the HO Command message (e.g. RRCConnnectionReconfiguration or RRCReconfiguration). As an alternative, the source node is informed by the UE about the use of CBRA in the target cell during the HO. The source node may also be informed about the RTT that is applicable for the UE in the target cell (node) through the same mechanisms. After handover is complete, data may be transmitted or received in the target cell by monitoring PDCCH for UL/DL traffic according to RRCreconfiguration received in the HO command (which may contain a specific PDCCH/Coreset configuration for this).
In a further embodiment, the UE may transmit to the source node an indication of when the preamble was sent in the target cell so that the source node can make a more accurate estimation of the start and end of the RTT period in the target Cell. The UE may also transmit an indication of when Msg3 was sent in the target cell if four-step random access (e.g., contention based random access) is used in the target cell. This would avoid scheduling of the UE that will not be received.
Alternatively, the source node may receive this information from the target node. For example, for contention free random access, the target node may inform the source node when the preamble is received or RAR sent (and/or when Msg3 is received or Msg4 sent). If both source and target network nodes are on the ground, this information may be exchanged over a direct interface between the source and target network nodes (e.g., Xn).
In a further alternative or additional embodiment, the status of the ongoing handover may be indicated by the target network node to the source network node over a direct interface (e.g., Xn). The status may be indicated in a new message. In this way, the target node may thus inform the source node about how long to keep the connection to the UE, e.g., to continue with transmissions to and/or UL scheduling and reception from the UE for the time window, and when the source node should pause such connection (DL transmissions, UL scheduling and/or reception) due to the UE being active in the target cell (e.g., the breaks in the time window described above).
Alternatively the UE can be configured, e.g. using a control message (such as a radio resource control (RRC) message), to indicate to the source node when the UE will be active in the target cell (node) during the handover procedure, and when the source node should pause the connection to the UE.
The UE can be configured to perform the here proposed solution, i.e. to return to the source cell (node) when it is waiting for response from the target node, or while waiting for an occasion to transmit during the HO procedure, with an indication in the HO Command message (e.g. RRCConnnectionReconfiguration or RRCReconfiguration). As an alternative the activation (of this minimum interruption procedure) could also be by using a new Medium Access Control (MAC) Control Element (CE) or indicated in the DCI sent to indicate the transmitted HO command message.
As an alternative, the UE indicates that it supports a return to the source cell (node) when it e.g. is waiting for response from the target node during the HO procedure through a UE capability indication.
In a yet further embodiment, the source node may communicate to the target node which data packets (e.g., Packet Data Convergence Protocol (PDCP) packets), sequence numbers (SNs), range of SNs, it is still attempting to deliver to the UE. This can be per bearer, or Quality of Service (QoS) flow or Protocol Data Unit (PDU) session. This can be done separately or together with normal data forwarding between the nodes. Further the source network node may also communicate later which packets are delivered successfully. Or, the UE may be configured to send a status report directly to the target network node comprising an indication of successfully delivered data packets from the source network node.
Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in
According to embodiments of the disclosure, at least one of the network nodes 560 belongs to a non-terrestrial network, such that transmissions between a wireless device 510 and the at least one network node 560 pass via an airborne or spaceborne vehicle. As noted above, the airborne or spaceborne vehicle may be used for transmission by implementing the at least one network node 560 on the airborne or spaceborne vehicle itself (e.g., such that the network node is an airborne or spaceborne network node). Thus, in such examples, a wireless device or UE communicates directly with the airborne or spaceborne network node to access the services of the network. Alternatively, the at least one network node 560 may be implemented on the ground, but transmissions between the wireless device or UE and the network node are indirect and travel via a simple forwarding or repeating mechanism on the airborne or spaceborne vehicle (not illustrated in
The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
Network 506 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
Network node 560 and WD 510 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
In
Similarly, network node 560 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 560 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 560 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 580 for the different RATs) and some components may be reused (e.g., the same antenna 562 may be shared by the RATs). Network node 560 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 560, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 560.
Processing circuitry 570 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 570 may include processing information obtained by processing circuitry 570 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
Processing circuitry 570 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 560 components, such as device readable medium 580, network node 560 functionality. For example, processing circuitry 570 may execute instructions stored in device readable medium 580 or in memory within processing circuitry 570. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 570 may include a system on a chip (SOC).
In some embodiments, processing circuitry 570 may include one or more of radio frequency (RF) transceiver circuitry 572 and baseband processing circuitry 574. In some embodiments, radio frequency (RF) transceiver circuitry 572 and baseband processing circuitry 574 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 572 and baseband processing circuitry 574 may be on the same chip or set of chips, boards, or units
In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 570 executing instructions stored on device readable medium 580 or memory within processing circuitry 570. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 570 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 570 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 570 alone or to other components of network node 560, but are enjoyed by network node 560 as a whole, and/or by end users and the wireless network generally.
Device readable medium 580 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 570. Device readable medium 580 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 570 and, utilized by network node 560. Device readable medium 580 may be used to store any calculations made by processing circuitry 570 and/or any data received via interface 590. In some embodiments, processing circuitry 570 and device readable medium 580 may be considered to be integrated.
Interface 590 is used in the wired or wireless communication of signalling and/or data between network node 560, network 506, and/or WDs 510. As illustrated, interface 590 comprises port(s)/terminal(s) 594 to send and receive data, for example to and from network 506 over a wired connection. Interface 590 also includes radio front end circuitry 592 that may be coupled to, or in certain embodiments a part of, antenna 562. Radio front end circuitry 592 comprises filters 598 and amplifiers 596. Radio front end circuitry 592 may be connected to antenna 562 and processing circuitry 570. Radio front end circuitry may be configured to condition signals communicated between antenna 562 and processing circuitry 570. Radio front end circuitry 592 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 592 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 598 and/or amplifiers 596. The radio signal may then be transmitted via antenna 562. Similarly, when receiving data, antenna 562 may collect radio signals which are then converted into digital data by radio front end circuitry 592. The digital data may be passed to processing circuitry 570. In other embodiments, the interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 560 may not include separate radio front end circuitry 592, instead, processing circuitry 570 may comprise radio front end circuitry and may be connected to antenna 562 without separate radio front end circuitry 592. Similarly, in some embodiments, all or some of RF transceiver circuitry 572 may be considered a part of interface 590. In still other embodiments, interface 590 may include one or more ports or terminals 594, radio front end circuitry 592, and RF transceiver circuitry 572, as part of a radio unit (not shown), and interface 590 may communicate with baseband processing circuitry 574, which is part of a digital unit (not shown).
Antenna 562 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 562 may be coupled to radio front end circuitry 590 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 562 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 562 may be separate from network node 560 and may be connectable to network node 560 through an interface or port.
Antenna 562, interface 590, and/or processing circuitry 570 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 562, interface 590, and/or processing circuitry 570 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry 587 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 560 with power for performing the functionality described herein. Power circuitry 587 may receive power from power source 586. Power source 586 and/or power circuitry 587 may be configured to provide power to the various components of network node 560 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 586 may either be included in, or external to, power circuitry 587 and/or network node 560. For example, network node 560 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 587. As a further example, power source 586 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 587. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.
Alternative embodiments of network node 560 may include additional components beyond those shown in
As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (Vol P) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device 510 includes antenna 511, interface 514, processing circuitry 520, device readable medium 530, user interface equipment 532, auxiliary equipment 534, power source 536 and power circuitry 537. WD 510 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 510, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 510.
Antenna 511 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 514. In certain alternative embodiments, antenna 511 may be separate from WD 510 and be connectable to WD 510 through an interface or port. Antenna 511, interface 514, and/or processing circuitry 520 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 511 may be considered an interface.
As illustrated, interface 514 comprises radio front end circuitry 512 and antenna 511. Radio front end circuitry 512 comprise one or more filters 518 and amplifiers 516. Radio front end circuitry 514 is connected to antenna 511 and processing circuitry 520, and is configured to condition signals communicated between antenna 511 and processing circuitry 520. Radio front end circuitry 512 may be coupled to or a part of antenna 511. In some embodiments, WD 510 may not include separate radio front end circuitry 512; rather, processing circuitry 520 may comprise radio front end circuitry and may be connected to antenna 511. Similarly, in some embodiments, some or all of RF transceiver circuitry 522 may be considered a part of interface 514. Radio front end circuitry 512 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 512 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 518 and/or amplifiers 516. The radio signal may then be transmitted via antenna 511. Similarly, when receiving data, antenna 511 may collect radio signals which are then converted into digital data by radio front end circuitry 512. The digital data may be passed to processing circuitry 520. In other embodiments, the interface may comprise different components and/or different combinations of components.
Processing circuitry 520 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 510 components, such as device readable medium 530, WD 510 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 520 may execute instructions stored in device readable medium 530 or in memory within processing circuitry 520 to provide the functionality disclosed herein.
As illustrated, processing circuitry 520 includes one or more of RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 520 of WD 510 may comprise a SOC. In some embodiments, RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 524 and application processing circuitry 526 may be combined into one chip or set of chips, and RF transceiver circuitry 522 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 522 and baseband processing circuitry 524 may be on the same chip or set of chips, and application processing circuitry 526 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 522 may be a part of interface 514. RF transceiver circuitry 522 may condition RF signals for processing circuitry 520.
In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 520 executing instructions stored on device readable medium 530, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 520 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 520 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 520 alone or to other components of WD 510, but are enjoyed by WD 510 as a whole, and/or by end users and the wireless network generally.
Processing circuitry 520 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 520, may include processing information obtained by processing circuitry 520 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 510, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
Device readable medium 530 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 520. Device readable medium 530 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 520. In some embodiments, processing circuitry 520 and device readable medium 530 may be considered to be integrated.
User interface equipment 532 may provide components that allow for a human user to interact with WD 510. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 532 may be operable to produce output to the user and to allow the user to provide input to WD 510. The type of interaction may vary depending on the type of user interface equipment 532 installed in WD 510. For example, if WD 510 is a smart phone, the interaction may be via a touch screen; if WD 510 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 532 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 532 is configured to allow input of information into WD 510, and is connected to processing circuitry 520 to allow processing circuitry 520 to process the input information. User interface equipment 532 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 532 is also configured to allow output of information from WD 510, and to allow processing circuitry 520 to output information from WD 510. User interface equipment 532 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 532, WD 510 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
Auxiliary equipment 534 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 534 may vary depending on the embodiment and/or scenario.
Power source 536 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 510 may further comprise power circuitry 537 for delivering power from power source 536 to the various parts of WD 510 which need power from power source 536 to carry out any functionality described or indicated herein. Power circuitry 537 may in certain embodiments comprise power management circuitry. Power circuitry 537 may additionally or alternatively be operable to receive power from an external power source; in which case WD 510 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 537 may also in certain embodiments be operable to deliver power from an external power source to power source 536. This may be, for example, for the charging of power source 536. Power circuitry 537 may perform any formatting, converting, or other modification to the power from power source 536 to make the power suitable for the respective components of WD 510 to which power is supplied.
In
In
In the depicted embodiment, input/output interface 605 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 600 may be configured to use an output device via input/output interface 605. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 600. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 600 may be configured to use an input device via input/output interface 605 to allow a user to capture information into UE 600. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In
RAM 617 may be configured to interface via bus 602 to processing circuitry 601 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 619 may be configured to provide computer instructions or data to processing circuitry 601. For example, ROM 619 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 621 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 621 may be configured to include operating system 623, application program 625 such as a web browser application, a widget or gadget engine or another application, and data file 627. Storage medium 621 may store, for use by UE 600, any of a variety of various operating systems or combinations of operating systems.
Storage medium 621 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 621 may allow UE 600 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 621, which may comprise a device readable medium.
In
In the illustrated embodiment, the communication functions of communication subsystem 631 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 631 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 643b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 643b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 613 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 600.
The features, benefits and/or functions described herein may be implemented in one of the components of UE 600 or partitioned across multiple components of UE 600. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 631 may be configured to include any of the components described herein. Further, processing circuitry 601 may be configured to communicate with any of such components over bus 602. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 601 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 601 and communication subsystem 631. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 700 hosted by one or more of hardware nodes 730. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
The functions may be implemented by one or more applications 720 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 720 are run in virtualization environment 700 which provides hardware 730 comprising processing circuitry 760 and memory 790. Memory 790 contains instructions 795 executable by processing circuitry 760 whereby application 720 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment 700, comprises general-purpose or special-purpose network hardware devices 730 comprising a set of one or more processors or processing circuitry 760, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 790-1 which may be non-persistent memory for temporarily storing instructions 795 or software executed by processing circuitry 760. Each hardware device may comprise one or more network interface controllers (NICs) 770, also known as network interface cards, which include physical network interface 780. Each hardware device may also include non-transitory, persistent, machine-readable storage media 790-2 having stored therein software 795 and/or instructions executable by processing circuitry 760. Software 795 may include any type of software including software for instantiating one or more virtualization layers 750 (also referred to as hypervisors), software to execute virtual machines 740 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines 740, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 750 or hypervisor. Different embodiments of the instance of virtual appliance 720 may be implemented on one or more of virtual machines 740, and the implementations may be made in different ways.
During operation, processing circuitry 760 executes software 795 to instantiate the hypervisor or virtualization layer 750, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 750 may present a virtual operating platform that appears like networking hardware to virtual machine 740.
As shown in
Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
In the context of NFV, virtual machine 740 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 740, and that part of hardware 730 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 740, forms a separate virtual network elements (VNE).
Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 740 on top of hardware networking infrastructure 730 and corresponds to application 720 in
In some embodiments, one or more radio units 7200 that each include one or more transmitters 7220 and one or more receivers 7210 may be coupled to one or more antennas 7225. Radio units 7200 may communicate directly with hardware nodes 730 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
In some embodiments, some signalling can be effected with the use of control system 7230 which may alternatively be used for communication between the hardware nodes 730 and radio units 7200.
With reference to
Telecommunication network 810 is itself connected to host computer 830, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 830 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 821 and 822 between telecommunication network 810 and host computer 830 may extend directly from core network 814 to host computer 830 or may go via an optional intermediate network 820. Intermediate network 820 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 820, if any, may be a backbone network or the Internet; in particular, intermediate network 820 may comprise two or more sub-networks (not shown).
The communication system of
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to
Communication system 900 further includes base station 920 provided in a telecommunication system and comprising hardware 925 enabling it to communicate with host computer 910 and with UE 930. Hardware 925 may include communication interface 926 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 900, as well as radio interface 927 for setting up and maintaining at least wireless connection 970 with UE 930 located in a coverage area (not shown in
Communication system 900 further includes UE 930 already referred to. Its hardware 935 may include radio interface 937 configured to set up and maintain wireless connection 970 with a base station serving a coverage area in which UE 930 is currently located. Hardware 935 of UE 930 further includes processing circuitry 938, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 930 further comprises software 931, which is stored in or accessible by UE 930 and executable by processing circuitry 938. Software 931 includes client application 932. Client application 932 may be operable to provide a service to a human or non-human user via UE 930, with the support of host computer 910. In host computer 910, an executing host application 912 may communicate with the executing client application 932 via OTT connection 950 terminating at UE 930 and host computer 910. In providing the service to the user, client application 932 may receive request data from host application 912 and provide user data in response to the request data. OTT connection 950 may transfer both the request data and the user data. Client application 932 may interact with the user to generate the user data that it provides.
It is noted that host computer 910, base station 920 and UE 930 illustrated in
In
Wireless connection 970 between UE 930 and base station 920 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 930 using OTT connection 950, in which wireless connection 970 forms the last segment. More precisely, the teachings of these embodiments may reduce the length of service interruptions during handover and thereby provide benefits such as reduced user waiting time and better responsiveness.
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 950 between host computer 910 and UE 930, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 950 may be implemented in software 911 and hardware 915 of host computer 910 or in software 931 and hardware 935 of UE 930, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 911, 931 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 920, and it may be unknown or imperceptible to base station 920. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 910's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 911 and 931 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 950 while it monitors propagation times, errors etc.
Thus the method may relate to handover of the wireless device from a source network node to a target network node. The target network node may belong to a NTN. The source network node may or may not belong to the NTN.
The method begins at step 1402, in which the wireless device obtains an indication of a round-trip time for transmissions to the target network node. For example, the indication may be contained within a system information broadcast by the target network node, or in a message transmitted by the source network node (e.g., a handover message—see step 1404). The indication may comprise an indication of the round-trip time itself, for transmissions in the target network node, or a parameter which is related to the round-trip time. For example, such a parameter may comprise any propagation delay associated with transmissions to and/or from the target network node (e.g., a one way delay, a minimum delay, a differential delay, etc). The parameter may also comprise the duration of a time window following initiation of access to the target network node, in which the wireless device is permitted to transmit data to or receive data from the source network node (see step 1408 below).
In step 1404, the wireless device receives a handover command message or trigger from the source network node, instructing handover to the target network node. As noted above, in some embodiments the handover command message or trigger may contain the indication of the round-trip time referred to in step 1402. Those skilled in the art will appreciate that handover may be triggered by the network or requested by the wireless device itself, e.g., based on measurements of radio metrics of the source network node and the target network node. These aspects are not described in further detail herein.
In step 1406, the wireless device initiates access to the target network node, e.g., through the transmission of a random access message or preamble. The random access transmission opportunities may be indicated to the wireless device in the system information broadcast from the target network node, or in the handover command message, for example.
In step 1408, the wireless device continues to transmit and/or receive data from the source network node. Those skilled in the art will also appreciate that the transmissions may utilize radio resources which are scheduled or granted via transmissions on a downlink control channel such as the PDCCH, e.g., via DCI messages, and thus this step may comprise the wireless device monitoring the downlink control channel for any such scheduled or granted resources.
The data transmissions between the source network node and the UE may continue for a time window after access has been initiated to the target network node (e.g., a RA message has been transmitted). The time window may extend for approximately one RTT in the target network node (e.g., for non-contention-based random access in the target cell) or, as in the illustrated embodiment, approximately two RTTs in the target network node (e.g., for contention-based random access). After the time window has ended, the transmissions between the UE and the source network node may cease, with further data transmissions taking place between the UE and the target network node.
It will be noted that at certain times during the time window, no data transmissions take place between the UE and the source network node. These times may correspond to those times at which the UE is performing transmissions in the target cell, e.g., as part of the random access procedure. For example, the times may correspond to times at which the UE is monitoring for a random access response message (RAR or Msg2) from the target network node. Thus the time window may comprise one or more breaks in which data transmissions between the UE and the source network node do not take place.
In step 1410, the wireless device transmits information to the source network node and/or the target network node. Such information may be transmitted in one or more information messages, e.g., via an uplink control channel (such as the Physical Uplink Control Channel or similar).
For example, in one embodiment, the wireless device may transmit to the source network node an indication of when the random access preamble was sent in the target cell so that the source network node can make a more accurate estimation of the start and end of the RTT period (and/or the time window) in the target Cell. The UE may also transmit an indication of when Msg3 was sent in the target cell if four-step random access (e.g., contention based random access) is used in the target cell. This would avoid scheduling of the UE that will not be received.
Alternatively or additionally, the wireless device may transmit to the source network node an indication of when the wireless device will be active in the target cell, i.e., when the time window, in which data transmission in the source cell can take place, comes to an end.
Alternatively or additionally, the wireless device may transmit to the target network node a status report comprising an indication of which data packets have been successfully received from the source network node. The indication may comprise sequence numbers or ranges of sequence numbers. The packets can be indicated per bearer, per QoS flow, per PDU session, or in any other suitable granularity. This embodiment is particularly advantageous when the connection between the source network node and the wireless device is or is about to be terminated (e.g., upon establishment of a connection with the target network node), as the source network node may not be able to receive or transmit acknowledgement messages (e.g., ACK/NACK) in respect of data packets which are transmitted at such times.
Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause initiating unit 1502 and transmitting/receiving unit 1504, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
The apparatus 1500 may be useful when implementing handover of the wireless device from a source network node to a target network node. As illustrated in
Thus the method may relate to handover of a wireless device from the source network node to a target network node. The target network node may belong to a NTN. The source network node may or may not belong to the NTN.
The method begins at step 1602, in which the source network node obtains an indication of a time window from the target network node or the wireless device. For example, the indication may be contained within a message transmitted by the target network node (e.g., via a direct interface such as the Xn interface). The indication may comprise an indication of the time window, the round-trip time for transmissions to and/or from the target network node, or a parameter which is related to the round-trip time. For example, such a parameter may comprise any propagation delay associated with transmissions to and/or from the target network node (e.g., a one way delay, a minimum delay, a differential delay, etc).
In step 1604, the source network node transmits a handover command message or trigger to the wireless device instructing handover to the target network node. In some embodiments the handover command message or trigger may contain the indication of the round-trip time or time window referred to in step 1602. Those skilled in the art will appreciate that handover may be triggered by the network or requested by the wireless device itself, e.g., based on measurements of radio metrics of the source network node and the target network node. These aspects are not described in further detail herein.
In step 1606, subsequent to the wireless device initiating access to the target network node, the source network node transmits data to or receives data from the wireless device.
The data transmissions between the source network node and the UE may continue for a time window after access has been initiated to the target network node (e.g., a RA message has been transmitted). The time window may extend for approximately one RTT in the target network node (e.g., for non-contention-based random access in the target cell) or, as in the illustrated embodiment, approximately two RTTs in the target network node (e.g., for contention-based random access). After the time window has ended, the transmissions between the UE and the source network node may cease, with further data transmissions taking place between the UE and the target network node.
It will be noted that at certain times during the time window, no data transmissions take place between the UE and the source network node. These times may correspond to those times at which the UE is performing transmissions in the target cell, e.g., as part of the random access procedure. For example, the times may correspond to times at which the UE is monitoring for a random access response message (RAR or Msg2) from the target network node. Thus the time window may comprise one or more breaks in which data transmissions between the UE and the source network node do not take place.
In one embodiment, the wireless device may transmit to the source network node an indication of when the random access preamble was sent in the target cell so that the source network node can make a more accurate estimation of the start and end of the RTT period (and/or the time window) in the target Cell. The UE may also transmit an indication of when Msg3 was sent in the target cell if four-step random access (e.g., contention based random access) is used in the target cell. Thus the source network node obtains an indication as to the times at which the wireless device is likely to be unreachable owing to its interactions with the target network node (e.g., listening for responses from the target network node). Alternatively or additionally, the wireless device may transmit to the source network node an indication of when the wireless device will be active in the target cell, i.e., when the time window, in which data transmission in the source cell can take place, comes to an end. The source network node may thus avoid scheduling of the UE during these breaks in the time window.
Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause causing unit 1702, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
The apparatus 1700 may be useful when implementing handover of a wireless device from the source network node to a target network node. As illustrated in
Thus the method may relate to handover of a wireless device from a source network node to the target network node. The target network node may belong to a NTN. The source network node may or may not belong to the NTN. The method shown in
The method begins at step 1802, in which the target network node causes transmission, to the source network node, of information relating to the handover of the wireless device to the target network node. Thus, in one embodiment, step 1802 is performed subsequent to initiation of the handover of the wireless device from the source network node to the target network node. For example, in one embodiment the indication may be transmitted subsequent to receipt of a random access message from the wireless device by the target network node. The information may be transmitted via a direct interface between the target network node and the source network node (e.g., Xn).
For example, the information may comprise an indication of a time window following initiation of access to the target network node by the wireless device, in which the source network node is able to transmit data to or receive data from the wireless device.
The time window may extend for approximately one RTT in the target network node (e.g., for non-contention-based random access in the target cell) or, as in the embodiment illustrated in
It will be noted that at certain times during the time window, no data transmissions take place between the UE and the source network node. These times may correspond to those times at which the UE is performing transmissions in the target cell, e.g., as part of the random access procedure. For example, the times may correspond to times at which the UE is monitoring for a random access response message (RAR or Msg2) from the target network node. Thus the time window may comprise one or more breaks in which data transmissions between the UE and the source network node do not take place.
In one embodiment, the target network node may transmit to the source network node an indication of when the random access preamble was received in the target cell or the RAR message was sent, so that the source network node can make a more accurate estimation of the start and end of the RTT period (and/or the time window) in the target Cell. The target network node may also transmit an indication of when Msg3 was received in the target cell or the Msg4 was sent, if four-step random access (e.g., contention based random access) is used in the target cell. In this way, the source network node obtains an indication as to the times at which the wireless device is likely to be unreachable owing to its interactions with the target network node (e.g., listening for responses from the target network node).
In step 1804, the target network node receives a status report from the wireless device or the source network node comprising an indication of which data packets have been successfully received by the wireless device from the source network node. The indication may comprise sequence numbers or ranges of sequence numbers. The packets can be indicated per bearer, per QoS flow, per PDU session, or in any other suitable granularity. Receiving the status report from the wireless device may be particularly advantageous when the connection between the source network node and the wireless device is or is about to be terminated (e.g., upon establishment of a connection with the target network node), as the source network node may not be able to receive or transmit acknowledgement messages (e.g., ACK/NACK) in respect of data packets which are transmitted at such times.
Virtual Apparatus 1900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause causing unit 1902, and any other suitable units of apparatus 1900 to perform corresponding functions according one or more embodiments of the present disclosure.
The apparatus 1900 may be useful when implementing handover of a wireless device from a source network node to the target network node. As illustrated in
The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
The following numbered paragraphs set out some embodiments of the disclosure.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2020/050111 | 2/5/2020 | WO | 00 |
| Number | Date | Country | |
|---|---|---|---|
| 62807985 | Feb 2019 | US |
