Patent Application
20230108496
The present disclosure is related to connection reconfigurations, such as handovers, in wireless communication systems, and is more particularly related to techniques for handling connection reconfigurations during dual-active protocol stack (DAPS) handovers.
For wireless communication systems confirming to the 3rd Generation Partnership Project (3GPP) specifications for the Evolved Packet System (EPS), also referred to as Long Term Evolution (LTE) or 4G, as specified in 3GPP TS 36.300 and related specifications, the access nodes 103, 104 correspond typically to base stations referred to in 3GPP specifications as Evolved NodeBs (eNBs), while the network node 106 corresponds typically to either a Mobility Management Entity (MME) and/or a Serving Gateway (SGW). The eNB is part of the RAN 100, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network). The eNBs are inter-connected via the X2 interface, and connected to EPC via the S1 interface, more specifically via S1-C to the MME and S1-U to the SGW.
On the other hand, for wireless communication systems pursuant to 3GPP specifications for the 3GPP 5G System, 5GS (also referred to as New Radio, NR, or 5G), as specified in 3GPP TS 38.300 and related specifications, the access nodes 103, 104 correspond typically to base stations referred to as 5G NodeBs, or gNBs, while the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and/or a User Plane Function (UPF). In this example, the gNB is part of the RAN 100, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC). The gNBs are inter-connected via the Xn interface, and connected to 5GC via the NG interface, more specifically via NG-C to the AMF and NG-U to the UPF.
To support fast mobility between NR and LTE while avoiding a change of core network, LTE eNBs can also be connected to the 5G-CN via NG-U/NG-C and support the Xn interface. An eNB connected to 5GC is called a next generation eNB (ng-eNB) and is considered part of the NG-RAN. LTE connected to 5GC will not be discussed further in this document, but it should be noted that most of the solutions/features described for LTE and NR in this document also apply to LTE connected to 5GC. In this document, when the term LTE is used without further specification it refers to LTE-EPC.
5G is designed to support, among other things, new use cases requiring ultra-reliable low-latency communication (URLLC), such as factory automation and autonomous driving. To meet stringent requirements on reliability and latency during mobility, two new handover types are introduced in 5G Release 16. These are called make-before-break handover and conditional handover. The make-before-break handover, also known as Dual Active Protocol Stack (DAPS) handover, is relevant in the context of this invention disclosure and is described in more detail below after a review of the NG-RAN architecture and the legacy handover procedure.
Like E-UTRAN in 4G, the NG-RAN (also referred to as the NR, or “new radio” network) uses a flat architecture and consists of base stations, called gNBs, which are interconnected with each other by means of the Xn-interface. A simplified illustration of the NG-RAN architecture is shown in
It is expected that NR will be rolled out gradually on top of the legacy LTE network starting in areas where high data traffic is expected. This means that NR coverage will be limited in the beginning and users must move between NR and LTE as they go in and out of coverage. To support fast mobility between NR and LTE and avoid change of core network, LTE eNBs will also connect to the 5GC and support the Xn interface. An eNB connected to 5GC is called a next generation eNB (ng-eNB) and is considered part of the NG-RAN (see
Mobility in RRC_CONNECTED state is also known as handover. The purpose of handover is to move the UE from a source access node using a source radio connection (also known as source cell connection), to a target access node, using a target radio connection (also known as target cell connection). The handover may be caused by movement of the UE, for example, or for other reasons where the target cell is better positioned to serve the UE. The source radio connection is associated with a source cell controlled by the source access node. The target radio connection is associated with a target cell controlled by the target access node. In other words, during a handover, the UE moves from the source cell to a target cell. Sometimes the source access node or the source cell is referred to as the “source”, and the target access node or the target cell is sometimes referred to as the “target”. The source access node and the target access node may also be referred to as the source node and the target node, the source radio network node and the target radio network node or the source gNB and the target gNB.
In some cases, the source access node and target access node are different nodes, such as different eNBs or gNBs. These cases are also referred to as inter-node handover, inter-eNB handover or inter-gNB handover. In other cases, the source access node and target access node are the same node, such as the same eNB and gNB. These cases are also referred to as intra-node handover, intra-eNB handover or intra-gNB handover and covers the case then source and target cells are controlled by the same access node. In yet other cases, handover is performed within the same cell (and thus also within the same access node controlling that cell) - these cases are also referred to as intra-cell handover.
It should therefore be understood that the terms “source access node” and “target access node” each refer to a role served by a given access node during a handover of a specific UE. For example, a given access node may serve as source access node during handover of one UE, while it also serves as the target access node during handover of a different UE. And, in the case of an intra-node or intra-cell handover of a given UE, the same access node serves both as the source access node and target access node for that UE.
An inter-node handover can further be classified as an Xn-based or NG-based handover, depending on whether the source and target node communicate directly using the Xn interface or indirectly via the core network using the NG interface.
An RRC_CONNECTED UE in E-UTRAN or NG-RAN can be configured by the network to perform measurements of serving and neighbor cells and based on the measurement reports sent by the UE, the network may decide to perform a handover of the UE to a neighbor cell. The network then sends a Handover Command message to the UE (in LTE an RRConnectionReconfiguration message with a field called mobilityControlInfo and in NR an RRCReconfiguration message with a reconfigurationWithSync field).
These reconfigurations are prepared by the target access node upon a request from the source access node (over X2 or S1 interface in case of EUTRA-EPC or Xn or NG interface in case of NG-RAN-5GC) and take into account the existing Radio Resource Control (RRC) configuration and UE capabilities, as provided in the request from the source access node, as well as the capabilities and resource situation in the intended target cell and target access node. The reconfiguration parameters provided by the target access node contain, for example, information needed by the UE to access the target access node, e.g., random access configuration, a new C-RNTI assigned by the target access node, and security parameters enabling the UE to calculate new security keys associated to the target access node so the UE can send a Handover Complete message (in LTE an RRConnectionReconfiguratioComplete message and in NR an RRCReconfigurationComplete message) on SRB1 encrypted and integrity protected based on new security keys upon accessing the target access node.
Handovers in NR like the one illustrated in
To shorten the interruption time during handover, a new type of handover, known as Dual Active Protocol Stack (DAPS) handover, is being introduced for NR and LTE in 3GPP Release 16. In DAPS handover the UE maintains the connection to the source cell while the connection to the target is being established. Thus, the DAPS handover can be classified as make-before-break handover. DAPS handover reduces the handover interruption but comes at the cost of increased UE complexity, as the UE needs to be able to simultaneously receive/transmit from/to two cells at the same time.
The DAPS procedure in NR is illustrated in
Note that, like in normal handover, the handover command (i.e., a RRCReconfiguration message containing the reconfigurationWithSync field) that is sent to the UE to trigger the handover procedure is generated by the target node (handling the target cell) but transmitted to the UE by the source node (in the source cell, i.e., the cell where the UE currently has its connection). In case of an inter-node handover, the handover command is sent from the target node to the source node within the Xn HANDOVER REQUEST ACKNOWLEDGE message as a transparent container, meaning that the source node does not change the contents of the handover command.
In order to not exceed the UE capabilities during a DAPS handover where the UE is simultaneously connected to both the source node (in the source cell) and the target node (in the target cell), the source node may need to reconfigure (also known as “downgrade”) the UE’s source cell configuration before triggering the DAPS handover. This reconfiguration can be done by performing an RRC connection reconfiguration procedure before the DAPS handover command is sent to the UE, i.e., before step 305. Alternatively, the updated (downgraded) source cell configuration can be sent together with the handover command, i.e., in the same RRC message and applied by the UE before the handover is executed. This can possibly speed up the DAPS handover by, for example, reducing processing time, as there is a single RRC message providing both source cell configuration downgrading and handover command.
Dual Active Protocol Stack (DAPS) handover is also being specified for LTE. An example of a DAPS inter-node handover is illustrated in
Some highlights in this solution are:
As an alternative to source access node starting packet data forwarding after step 405 (i.e., after sending the Handover Command to the UE, also known as “early packet forwarding”), the target access node may indicate to the source access node when to start packet data forwarding. For instance, the packet data forwarding may start at a later stage when the link to the target cell has been established, e.g., after the UE has performed random access in the target cell or when the UE has sent the RRC Connection Reconfiguration Complete message to the target access node (also known as “late packet forwarding”). By starting the packet data forwarding in the source access node at a later stage, the number of duplicated PDCP SDUs received by the UE from the target cell will potentially be less and by that the DL latency will be somewhat reduced. However, starting the packet data forwarding at a later stage is also a trade-off between robustness and reduced latency if, e.g., the connection between the UE and the source access node is lost before the connection to the target access node is established. In such case there will be a short interruption in the DL data transfer to the UE.
For the purposes of the present disclosure, the term DAPS handover should be understood as referring to a handover procedure in which the UE maintains a distinct uplink/downlink connection to the source base station after reception of an RRC message for handover and until releasing the source cell after successful random access to the target base station. Thus, unlike Rel-14 make before break handovers, with a DAPS handover the UE does not release the connection to the source base station until after its first transmission (e.g., the PRACH preamble) to the target base station.
It will be appreciated that a DAPS handover in accordance with the above definition may carry a different name, in various contexts. It will be further appreciated, however, that a DAPS handover is distinct from such things as soft handover, MIMO, multi-transmission point transmission/reception, dual connectivity, etc. Each of these also involve redundant paths from the UE to the network, where an endpoint combines information from the paths into a reliable stream of data. However, the combining is done on different protocol layers, and most of these do not involve a handover in that a source cell is released once a connection to the target cell is established. In soft handover, the same bitstream is transmitted to the UE from two different cells, where combining is done at the physical layer. With soft handover, there are not distinct UL/DL links between the UE and two base stations, but merely a redundant bitstream. The other examples mentioned above involve redundant paths or transmission layers, but these redundant paths or transmission layers are distinct from a handover scenario.
Note that in case of NR, there is an additional protocol layer called Service Data Adaptation Protocol (SDAP), on top of PDCP. SDAP is responsible for mapping QoS flows to bearers. This layer is not shown in
In DAPS handover as presently specified, the source connection is released by the target node using a separate RRC reconfiguration procedure after the target connection has been established. The UE then receives an indication in an RRCReconfiguration message that indicates that it shall release the connection to the source cell, i.e., the cell to which it was connected when the DAPS handover was started.
In some cases, the UE should perform a new handover (to a second target cell) immediately after the first (DAPS) handover to the first target cell. As an example, the UE has a connection in a first cell (C1) and performs a DAPS handover to a second cell (C2). When entering C2, the UE is instructed to perform a subsequent handover to a third cell (C3). The second handover could then either also be run as a DAPS handover or as handover not using DAPS. The UE would thus receive a new handover command (i.e., RRCReconfiguration message) just when it has entered cell C2. However, since the first handover was a DAPS handover, and there thus is a need to release the connection to the source cell (C1), the UE would need to receive both a first RRCReconfiguration message with the indication to release the source cell (C1) and a second RRCReconfiguration message that triggers the subsequent handover to the new, second target cell (C3). The reason is that the new (second) target node, which controls the second target cell (C3), and which prepares the handover command, does not know that the UE has a connection to a previous source cell (C1), which needs to be released (unless the second target node and the first target node are one and the same, i.e., both cell C2 and cell C3 are controlled by the same node). It cannot thus include an indication for it in the RRCReconfiguration message (handover command).
This may delay a subsequent handover since there is a delay to wait for the first RRC reconfiguration procedure to complete before a new handover can be triggered. Delayed handover in turn results in an increased risk of radio link failure or handover failure. The techniques described herein enable the network to transmit a subsequent handover command message to a UE and enable the UE to receive and process the subsequent handover command message, when a DAPS handover is in progress for that UE. The result is that a well-defined UE behavior can be ensured when the UE receives this subsequent handover command.
Several embodiments of the presently disclosed techniques provide solutions for the UE to release the source connection when a new handover is triggered after a DAPS handover, without the need for a reconfiguration message dedicated for that purpose. These techniques enable a subsequent handover to be performed faster after a DAPS handover, which reduces the risk of radio link failure.
An example method, according to some embodiments of these techniques, is carried out by a first target access node of a radio access network. This example method comprises the step of sending a first handover command to a source access node serving a UE, for transmission by the source access node to the UE. This first handover command indicates a DAPS handover from a source cell served by the source access node to a first target cell, served by the first target access node. Prior to the UE releasing the source cell for the DAPS handover, the first target access node determines to perform a handover of the UE to a second target cell, served by a second target access node. The first target access node then transmits a second handover command to the UE, the second handover command ordering a handover from the first target cell to the second target cell. This second handover command includes an explicit indication that the UE is to release the source cell upon receiving the second handover command.
Other embodiments include a corresponding example method carried out in a UE, for handling connection reconfiguration commands received during ongoing DAPS, handovers. This example method includes the step of receiving, prior to releasing a source cell from a DAPS handover from the source cell to a first target cell, a connection reconfiguration command from the first target cell. The method further comprises the step of releasing the UE’s connection to the source cell, responsive to the connection reconfiguration message command. The connection reconfiguration message referred to here is a handover command specifying a handover to a second target cell, where the handover command includes an explicit indication that the UE’s connection to the source cell is to be released.
Other embodiments described herein are several variations of the above-described methods, as well as corresponding apparatuses adapted to carry out these and similar methods, associated computer program products and non-transitory computer-readable mediums.
This disclosure details solutions for a UE to release the source connection when a new handover is triggered after a DAPS handover, to avoid delaying this subsequent handover. The various solutions described herein are discussed in the context of scenarios with two sequential handovers, a first handover from cell C1 and node N1 to cell C2 and node N2, and a subsequent second handover from cell C2 and node N2 to cell C3 and node N3. C1 and N1 are referred to as the source cell and the source node (or source gNB). C2 and N2 are referred to as the first target cell and the first target node (or first target gNB). Note that the first target cell and the first target node acts as source cell and source node in the second handover. C3 and N3 are referred to as the second target cell and the second target node (or the second target gNB). It should also be understood that while these techniques are described using mainly NR terminology, they are equally applicable to LTE, where, for instance, RRCConnectionReconfiguration/RRCConnectionReconfigurationComplete messages in LTE correspond to, or (in the context of this document) are equivalent to RRCReconfiguration/RRCReconfigurationComplete in NR and the handover command in LTE consists of an RRCConnectionReconfiguration message including a mobilityControlInfo information element (IE).
The solutions described herein include various alternatives and variations, including:
As yet another alternative, the UE receives a new handover command (i.e., RRCReconfiguration message) which instructs the UE to perform a DAPS handover to a second target cell, and this new handover command does not instruct the UE to release the source cell connection. In this alternative, the UE keeps the connections to both the source cell and first target cell while connecting to the second target cell.
All of these techniques enable a subsequent handover to be performed faster after a DAPS handover, which reduces the risk of radio link failure.
According to a first solution variant, or embodiment, if a subsequent handover is triggered by the target node before the source connection has been released after a DAPS handover, the UE releases the source connection when it receives the handover command.
The release of the source cell can either be triggered implicitly from the reception of the handover command (e.g., by introducing a rule in industry standards) or it can be triggered explicitly by including an indication in the handover command. In the latter case, since it is the second target node that prepares the handover command, the first target node (now acting as source node in the second handover) informs the second target node in the HANDOVER REQUEST message that the (previous) source cell connection has not yet been released, so that the second target node can include the release indication in the handover command. As an alternative, the first target node (acting as source node in the second handover) instead changes the content of the handover command to also include an indication to the UE to release the previous source cell connection.
A signaling flow for this procedure for handling a subsequent handover triggered after DAPS handover begins but before source connection release is illustrated in
The implicit release solution described above (without explicit release source cell connection indication) can also be applied to other cases besides handover. For example, the UE may release the source cell at reception of any kind of RRCReconfiguration message from the target (i.e., not just upon reception of a handover command (i.e., an RRCReconfiguration message containing a reconfigurationWithSync field)). The UE may also implicitly release the source connection when the UE changes state, for example, when the UE moves from connected to idle or inactive state. In this case the release of the source cell may be triggered by the reception of the RRCRelease message which orders the UE to move from connected to idle or inactive state.
As yet another option, the first target node may include in the handover command for the first handover (the DAPS handover from the source cell to the first target cell) an indication to the UE whether it should accept implicit source cell connection release indications (any of the variants, i.e., source cell connection release triggered only by a handover command, any RRCReconfiguration message or any RRC message received in the first target cell) or require an explicit indication to trigger release of the source cell connection
Some of the embodiments described above may be further illustrated with reference to
As shown at block 810, the illustrated method includes the step of receiving, prior to releasing a source cell from a DAPS handover from the source cell to a first target cell, a connection reconfiguration command from the first target cell. This connection reconfiguration message may be a handover command specifying a handover to a second target cell or a message ordering the UE to move from a connected state to an idle or inactive state, for example.
As shown at block 820, the method further includes the step of releasing the UE’s connection to the source cell, responsive to the connection reconfiguration message command.
In some embodiments, the connection reconfiguration command is a message ordering the UE to move from a connected state to an idle or inactive state, where the method comprises releasing the UE’s connection to the source cell response to the message ordering the UE to move from the connected state to an idle or inactive state, without receiving any explicit indication that the UE’s connection to the source cell is to be released.
In other embodiments, the connection reconfiguration message is a handover command, the handover command specifying a handover to a second target cell. In some of these embodiments, the handover command does not include an explicit indication that the UE’s connection to the source cell is to be released, and the method comprises releasing the UE’s connection to the source cell without receiving any explicit indication that the UE’s connection to the source cell is to be released. In some of these embodiments, the releasing of the UE’s connection to the source cell without receiving any explicit indication that the UE’s connection to the source cell is to be released is conditioned upon having previously received an indication that implicit source cell release is permitted.
In other embodiments where the connection reconfiguration message is a handover command, the handover command includes an explicit indication that the UE’s connection to the source cell is to be released. In others, releasing the UE’s connection to the source cell is in response to determining whether the handover command includes an explicit indication that the UE’s connection to the source cell is to be kept. In some of these latter embodiments, releasing the UE’s connection to the source cell is in response to determining that the handover command does not include an explicit indication that the UE’s connection to the source cell is to be kept.
In any of several of the embodiments described above, the handover command may be an RRCConnectionReconfiguration message, in an LTE network, or a RRCReconfiguration message, in an NR network. The handover command may include an indication to perform a DAPS handover to the second target cell. In this case, the method further comprises maintaining the UE’s connection to the first target cell until the UE is instructed to release the UE’s connection to the first target cell or until the UE receives a further handover command.
As shown at block 910, the method begins with sending a first handover command to a source access node serving a user equipment, UE, for transmission by the source access node to the UE. This first handover command indicates a dual-active protocol stack, DAPS, handover from a source cell served by the source access node to a first target cell, served by the first target access node. The method further comprises, prior to the UE releasing the source cell for the DAPS handover, determining to perform a handover of the UE to a second target cell served by a second target access node. This is shown at block 920. Finally, the method comprises transmitting a second handover command to the UE, the second handover command ordering a handover from the first target cell to the second target cell. The second handover command includes an indication of whether the UE is to release the source cell upon receiving the second handover command. This is shown at block 930.
In some embodiments, the second handover command includes an explicit indication that the UE is to release the source cell upon receiving the second handover command. In some other embodiments, the second handover command includes an explicit indication that the UE is to keep its connection to the source cell upon receiving the second handover command.
In some embodiments, the method comprises receiving the second handover command from the second target access node before said transmitting, where the transmitting comprises forwarding the second handover command without modification. In some of these embodiments, the method comprises sending a handover request message to the second target access node prior to receiving the second handover command from the second target access node, the handover request message including an indication that the UE has not released the source cell from an ongoing DAPS handover. In others, the method comprises sending a handover request message to the second target access node prior to receiving the second handover command from the second target access node, the handover request message including an indication that the UE is to release the source cell from an ongoing DAPS handover.
In some embodiments, the method comprises receiving the second handover command from the second target cell before transmitting it, and modifying the second handover command to add the indication of whether the UE is to release the source cell upon receiving the second handover command.
In some of the embodiments discussed above, the second handover command is an RRCConnectionReconfiguration message, in an LTE network, or a RRCReconfiguration message, in an NR network. In some embodiments, the second handover command includes an indication to perform a DAPS handover to the second target cell.
The receiving step shown in block 1020 is preceded by the step of receiving, from the first target access node, a handover request for handing over the UE to the second target cell, where sending the handover command is responsive to the handover request. In some embodiments, the handover request indicates that the UE has not released the source cell from the ongoing DAPS handover to the first target cell. In other embodiments, the handover request indicates that the UE is to release the source cell from the ongoing DAPS handover to the first target cell.
In some of the embodiments illustrated generally in
In some embodiments, the handover command is an RRCConnectionReconfiguration message, in an LTE network, or a RRCReconfiguration message, in an NR network. In some embodiments, the handover command includes an indication to perform a DAPS handover to the second target cell.
User equipment 50 is configured to communicate with a network node or base station in a wide-area cellular network via antennas 54 and transceiver circuitry 56. Transceiver circuitry 56 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of using cellular communication services. The radio access technology can be NR or LTE, for the purposes of this discussion.
User equipment 50 also includes one or more processing circuits 52 that are operatively associated with the radio transceiver circuitry 56. Processing circuitry 52 comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. More generally, processing circuitry 52 may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the functionality taught herein, or may comprise some mix of fixed and programmed circuitry. Processing circuitry 52 may be multi-core.
Processing circuitry 52 also includes a memory 64. Memory 64, in some embodiments, stores one or more computer programs 66 and, optionally, configuration data 68. Memory 64 provides non-transitory storage for computer program 66 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, memory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 52 and/or separate from processing circuitry 52. Memory 64 may also store any configuration data 68 used by wireless device 50. Processing circuitry 52 may be configured, e.g., through the use of appropriate program code stored in memory 64, to carry out one or more of the methods and/or signaling processes detailed herein.
Processing circuitry 52 of the user equipment 50 is configured, according to some embodiments, to perform any or all of the techniques described herein for a user equipment, including those techniques illustrated in
In the discussion herein, network node 30 is described as being configured to operate as a cellular network access node in an LTE network or NR network, but network node 30 may also correspond to similar access nodes in other types of network.
Those skilled in the art will readily appreciate how each type of node may be adapted to carry out one or more of the methods and signaling processes described herein, e.g., through the modification of and/or addition of appropriate program instructions for execution by processing circuits 32.
Network node 30 facilitates communication between wireless terminals (e.g., UEs), other network access nodes and/or the core network. Network node 30 may include communication interface circuitry 38 that includes circuitry for communicating with other nodes in the core network, radio nodes, and/or other types of nodes in the network for the purposes of providing data and/or cellular communication services. Network node 30 communicates with wireless devices using antennas 34 and transceiver circuitry 36. Transceiver circuitry 36 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of providing cellular communication services.
Network node 30 also includes one or more processing circuits 32 that are operatively associated with the transceiver circuitry 36 and, in some cases, the communication interface circuitry 38. Processing circuitry 32 comprises one or more digital processors 42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific integrated Circuits (ASICs), or any mix thereof. More generally, processing circuitry 32 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or some mix of fixed and programmed circuitry. Processor 42 may be multi-core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.
Processing circuitry 32 also includes a memory 44. Memory 44, in some embodiments, stores one or more computer programs 46 and, optionally, configuration data 48. Memory 44 provides non-transitory storage for the computer program 46 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. Here, “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution. By way of non-limiting example, memory 44 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 32 and/or separate from processing circuitry 32. Memory 44 may also store any configuration data 48 used by the network access node 30. Processing circuitry 32 may be configured, e.g., through the use of appropriate program code stored in memory 44, to carry out one or more of the methods and/or signaling processes detailed hereinafter.
Processing circuitry 32 of the network node 30 is configured, according to some embodiments, to perform the techniques described herein for a network node, such as the first target node or second target node described in the several example techniques described above and illustrated in
It will be appreciated that key aspects of several of the UE-related techniques described above include:
For the first target node, key aspects of several of the techniques described herein include:
For the second target nodes described herein, key aspects of several techniques include:
Although the subject matter described herein can 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
The wireless network can 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 can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can 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 1406 can 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 1460 and WD 1410 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 can 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 can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
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 can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. A network node can 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 can also be referred to as nodes in a distributed antenna system (DAS).
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 can be a virtual network node as described in more detail below. More generally, however, network nodes can 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 1460 can 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 can each have their own respective components. In certain scenarios in which network node 1460 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node 1460 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium 1480 for the different RATs) and some components can be reused (e.g., the same antenna 1462 can be shared by the RATs). Network node 1460 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 1460.
Processing circuitry 1470 can be 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 1470 can include processing information obtained by processing circuitry 1470 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 1470 can 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 1460 components, such as device readable medium 1480, network node 1460 functionality. For example, processing circuitry 1470 can execute instructions stored in device readable medium 1480 or in memory within processing circuitry 1470. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1470 can include a system on a chip (SOC).
In some embodiments, processing circuitry 1470 can include one or more of radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474. In some embodiments, radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474 can 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 1472 and baseband processing circuitry 1474 can 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 can be performed by processing circuitry 1470 executing instructions stored on device readable medium 1480 or memory within processing circuitry 1470. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 1470 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 1470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1470 alone or to other components of network node 1460, but are enjoyed by network node 1460 as a whole, and/or by end users and the wireless network generally.
Device readable medium 1480 can 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 can be used by processing circuitry 1470. Device readable medium 1480 can 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 1470 and, utilized by network node 1460. Device readable medium 1480 can be used to store any calculations made by processing circuitry 1470 and/or any data received via interface 1490. In some embodiments, processing circuitry 1470 and device readable medium 1480 can be considered to be integrated.
Interface 1490 is used in the wired or wireless communication of signalling and/or data between network node 1460, network 1406, and/or WDs 1410. As illustrated, interface 1490 comprises port(s)/terminal(s) 1494 to send and receive data, for example to and from network 1406 over a wired connection. Interface 1490 also includes radio front end circuitry 1492 that can be coupled to, or in certain embodiments a part of, antenna 1462. Radio front end circuitry 1492 comprises filters 1498 and amplifiers 1496. Radio front end circuitry 1492 can be connected to antenna 1462 and processing circuitry 1470. Radio front end circuitry can be configured to condition signals communicated between antenna 1462 and processing circuitry 1470. Radio front end circuitry 1492 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1492 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1498 and/or amplifiers 1496. The radio signal can then be transmitted via antenna 1462. Similarly, when receiving data, antenna 1462 can collect radio signals which are then converted into digital data by radio front end circuitry 1492. The digital data can be passed to processing circuitry 1470. In other embodiments, the interface can comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 1460 may not include separate radio front end circuitry 1492, instead, processing circuitry 1470 can comprise radio front end circuitry and can be connected to antenna 1462 without separate radio front end circuitry 1492. Similarly, in some embodiments, all or some of RF transceiver circuitry 1472 can be considered a part of interface 1490. In still other embodiments, interface 1490 can include one or more ports or terminals 1494, radio front end circuitry 1492, and RF transceiver circuitry 1472, as part of a radio unit (not shown), and interface 1490 can communicate with baseband processing circuitry 1474, which is part of a digital unit (not shown).
Antenna 1462 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1462 can be coupled to radio front end circuitry 1490 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1462 can 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 can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a particular area, and a panel antenna can 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 can be referred to as MIMO. In certain embodiments, antenna 1462 can be separate from network node 1460 and can be connectable to network node 1460 through an interface or port.
Antenna 1462, interface 1490, and/or processing circuitry 1470 can 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 can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1462, interface 1490, and/or processing circuitry 1470 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry 1487 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 1460 with power for performing the functionality described herein. Power circuitry 1487 can receive power from power source 1486. Power source 1486 and/or power circuitry 1487 can be configured to provide power to the various components of network node 1460 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1486 can either be included in, or external to, power circuitry 1487 and/or network node 1460. For example, network node 1460 can 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 1487. As a further example, power source 1486 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1487. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.
Alternative embodiments of network node 1460 can include additional components beyond those shown in
In some embodiments, a wireless device (WD, e.g. WD 1410) can be configured to communicate wirelessly with network nodes (e.g., 1460) and/or other wireless devices (e.g., 1410b,c). Communicating wirelessly can 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 can be configured to transmit and/or receive information without direct human interaction. For instance, a WD can 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 (VoIP) 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 can 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 can 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 can 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 can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one particular example, the WD can 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 can 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 can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device 1410 includes antenna 1411, interface 1414, processing circuitry 1420, device readable medium 1430, user interface equipment 1432, auxiliary equipment 1434, power source 1436 and power circuitry 1437. WD 1410 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 1410.
Antenna 1411 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1414. In certain alternative embodiments, antenna 1411 can be separate from WD 1410 and be connectable to WD 1410 through an interface or port. Antenna 1411, interface 1414, and/or processing circuitry 1420 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1411 can be considered an interface.
As illustrated, interface 1414 comprises radio front end circuitry 1412 and antenna 1411. Radio front end circuitry 1412 comprise one or more filters 1418 and amplifiers 1416. Radio front end circuitry 1414 is connected to antenna 1411 and processing circuitry 1420, and can be configured to condition signals communicated between antenna 1411 and processing circuitry 1420. Radio front end circuitry 1412 can be coupled to or a part of antenna 1411. In some embodiments, WD 1410 may not include separate radio front end circuitry 1412; rather, processing circuitry 1420 can comprise radio front end circuitry and can be connected to antenna 1411. Similarly, in some embodiments, some or all of RF transceiver circuitry 1422 can be considered a part of interface 1414. Radio front end circuitry 1412 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1412 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1418 and/or amplifiers 1416. The radio signal can then be transmitted via antenna 1411. Similarly, when receiving data, antenna 1411 can collect radio signals which are then converted into digital data by radio front end circuitry 1412. The digital data can be passed to processing circuitry 1420. In other embodiments, the interface can comprise different components and/or different combinations of components.
Processing circuitry 1420 can 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 1410 components, such as device readable medium 1430, WD 1410 functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1420 can execute instructions stored in device readable medium 1430 or in memory within processing circuitry 1420 to provide the functionality disclosed herein.
As illustrated, processing circuitry 1420 includes one or more of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1420 of WD 1410 can comprise a SOC. In some embodiments, RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1424 and application processing circuitry 1426 can be combined into one chip or set of chips, and RF transceiver circuitry 1422 can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1422 and baseband processing circuitry 1424 can be on the same chip or set of chips, and application processing circuitry 1426 can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1422 can be a part of interface 1414. RF transceiver circuitry 1422 can condition RF signals for processing circuitry 1420.
In certain embodiments, some or all of the functionality described herein as being performed by a WD can be provided by processing circuitry 1420 executing instructions stored on device readable medium 1430, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 1420 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 1420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1420 alone or to other components of WD 1410, but are enjoyed by WD 1410 as a whole, and/or by end users and the wireless network generally.
Processing circuitry 1420 can 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 1420, can include processing information obtained by processing circuitry 1420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1410, 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 1430 can 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 1420. Device readable medium 1430 can 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 can be used by processing circuitry 1420. In some embodiments, processing circuitry 1420 and device readable medium 1430 can be considered to be integrated.
User interface equipment 1432 can include components that allow and/or facilitate a human user to interact with WD 1410. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1432 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 1410. The type of interaction can vary depending on the type of user interface equipment 1432 installed in WD 1410. For example, if WD 1410 is a smart phone, the interaction can be via a touch screen; if WD 1410 is a smart meter, the interaction can 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 1432 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1432 can be configured to allow and/or facilitate input of information into WD 1410, and is connected to processing circuitry 1420 to allow and/or facilitate processing circuitry 1420 to process the input information. User interface equipment 1432 can 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 1432 is also configured to allow and/or facilitate output of information from WD 1410, and to allow and/or facilitate processing circuitry 1420 to output information from WD 1410. User interface equipment 1432 can 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 1432, WD 1410 can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein.
Auxiliary equipment 1434 is operable to provide more specific functionality which may not be generally performed by WDs. This can 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 1434 can vary depending on the embodiment and/or scenario.
Power source 1436 can, 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, can also be used. WD 1410 can further comprise power circuitry 1437 for delivering power from power source 1436 to the various parts of WD 1410 which need power from power source 1436 to carry out any functionality described or indicated herein. Power circuitry 1437 can in certain embodiments comprise power management circuitry. Power circuitry 1437 can additionally or alternatively be operable to receive power from an external power source; in which case WD 1410 can 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 1437 can also in certain embodiments be operable to deliver power from an external power source to power source 1436. This can be, for example, for the charging of power source 1436. Power circuitry 1437 can perform any converting or other modification to the power from power source 1436 to make it suitable for supply to the respective components of WD 1410.
In
In
In the depicted embodiment, input/output interface 1505 can be configured to provide a communication interface to an input device, output device, or input and output device. UE 1500 can be configured to use an output device via input/output interface 1505. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE 1500. The output device can 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 1500 can be configured to use an input device via input/output interface 1505 to allow and/or facilitate a user to capture information into UE 1500. The input device can 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 can include a capacitive or resistive touch sensor to sense input from a user. A sensor can 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 can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In
RAM 1517 can be configured to interface via bus 1502 to processing circuitry 1501 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 1519 can be configured to provide computer instructions or data to processing circuitry 1501. For example, ROM 1519 can 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 1521 can 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 1521 can be configured to include operating system 1523, application program 1525 such as a web browser application, a widget or gadget engine or another application, and data file 1527. Storage medium 1521 can store, for use by UE 1500, any of a variety of various operating systems or combinations of operating systems.
Storage medium 1521 can 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 1521 can allow and/or facilitate UE 1500 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 can be tangibly embodied in storage medium 1521, which can comprise a device readable medium.
In
In the illustrated embodiment, the communication functions of communication subsystem 1531 can 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 1531 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1543b can 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 1543b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1513 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1500.
The features, benefits and/or functions described herein can be implemented in one of the components of UE 1500 or partitioned across multiple components of UE 1500. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1531 can be configured to include any of the components described herein. Further, processing circuitry 1501 can be configured to communicate with any of such components over bus 1502. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1501 perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry 1501 and communication subsystem 1531. In another example, the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
In some embodiments, some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes 1630. 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 can be entirely virtualized.
The functions can be implemented by one or more applications 1620 (which can 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 1620 are run in virtualization environment 1600 which provides hardware 1630 comprising processing circuitry 1660 and memory 1690. Memory 1690 contains instructions 1695 executable by processing circuitry 1660 whereby application 1620 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment 1600, comprises general-purpose or special-purpose network hardware devices 1630 comprising a set of one or more processors or processing circuitry 1660, which can 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 can comprise memory 1690-1 which can be non-persistent memory for temporarily storing instructions 1695 or software executed by processing circuitry 1660. Each hardware device can comprise one or more network interface controllers (NICs) 1670, also known as network interface cards, which include physical network interface 1680. Each hardware device can also include non-transitory, persistent, machine-readable storage media 1690-2 having stored therein software 1695 and/or instructions executable by processing circuitry 1660. Software 1695 can include any type of software including software for instantiating one or more virtualization layers 1650 (also referred to as hypervisors), software to execute virtual machines 1640 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines 1640, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1650 or hypervisor. Different embodiments of the instance of virtual appliance 1620 can be implemented on one or more of virtual machines 1640, and the implementations can be made in different ways.
During operation, processing circuitry 1660 executes software 1695 to instantiate the hypervisor or virtualization layer 1650, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1650 can present a virtual operating platform that appears like networking hardware to virtual machine 1640.
As shown in
Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV can 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 1640 can 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 1640, and that part of hardware 1630 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 1640, forms a separate virtual network elements (VNE).
In the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1640 on top of hardware networking infrastructure 1630, and can correspond to application 1620 in
In some embodiments, one or more radio units 16200 that each include one or more transmitters 16220 and one or more receivers 16210 can be coupled to one or more antennas 16225. Radio units 16200 can communicate directly with hardware nodes 1630 via one or more appropriate network interfaces and can 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 signaling can be affected with the use of control system 16230 which can alternatively be used for communication between the hardware nodes 1630 and radio units 16200.
With reference to
Telecommunication network 1710 is itself connected to host computer 1730, which can 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 1730 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 1721 and 1722 between telecommunication network 1710 and host computer 1730 can extend directly from core network 1714 to host computer 1730 or can go via an optional intermediate network 1720. Intermediate network 1720 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1720, if any, can be a backbone network or the Internet; in particular, intermediate network 1720 can 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 1800 can also include base station 1820 provided in a telecommunication system and comprising hardware 1825 enabling it to communicate with host computer 1810 and with UE 1830. Hardware 1825 can include communication interface 1826 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1800, as well as radio interface 1827 for setting up and maintaining at least wireless connection 1870 with UE 1830 located in a coverage area (not shown in
Communication interface 1826 can be configured to facilitate connection 1860 to host computer 1810. Connection 1860 can be direct or it can pass through a core network (not shown in
Communication system 1800 can also include UE 1830 already referred to. Its hardware 1835 can include radio interface 1837 configured to set up and maintain wireless connection 1870 with a base station serving a coverage area in which UE 1830 is currently located. Hardware 1835 of UE 1830 can also include processing circuitry 1838, which can 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 1830 further comprises software 1831, which is stored in or accessible by UE 1830 and executable by processing circuitry 1838. Software 1831 includes client application 1832. Client application 1832 can be operable to provide a service to a human or non-human user via UE 1830, with the support of host computer 1810. In host computer 1810, an executing host application 1812 can communicate with the executing client application 1832 via OTT connection 1850 terminating at UE 1830 and host computer 1810. In providing the service to the user, client application 1832 can receive request data from host application 1812 and provide user data in response to the request data. OTT connection 1850 can transfer both the request data and the user data. Client application 1832 can interact with the user to generate the user data that it provides.
It is noted that host computer 1810, base station 1820 and UE 1830 illustrated in
In
Wireless connection 1870 between UE 1830 and base station 1820 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 1830 using OTT connection 1850, in which wireless connection 1870 forms the last segment. More precisely, the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end-to-end quality-of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network. These and other advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions. Furthermore, such embodiments can facilitate flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and important for the growth of OTT services.
A measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve. There can further be an optional network functionality for reconfiguring OTT connection 1850 between host computer 1810 and UE 1830, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1850 can be implemented in software 1811 and hardware 1815 of host computer 1810 or in software 1831 and hardware 1835 of UE 1830, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection 1850 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1811, 1831 can compute or estimate the monitored quantities. The reconfiguring of OTT connection 1850 can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1820, and it can be unknown or imperceptible to base station 1820. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer 1810's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software 1811, 1831 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1850 while it monitors propagation times, errors, etc.
The exemplary embodiments described herein provide techniques for pre-configuring a UE for operation in a 3GPP non-terrestrial network (NTN). Such embodiments reduce the time needed for initial acquisition of an NTN (e.g., PLMN) and a cell within the NTN. This can provide various benefits and/or advantages, including reducing UE energy consumption (or, equivalently, increasing UE operational time on one battery charge) and improving user access to services provided by an NTN. When used in UEs and/or network nodes, exemplary embodiments described herein can enable UEs to access network resources and OTT services more consistently and without interruption. This improves the availability and/or performance of these services as experienced by OTT service providers and end-users, including more consistent data throughout and fewer delays without excessive UE power consumption or other reductions in user experience.
The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.
The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can 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.
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (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 (RAM), 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 some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
In addition, certain terms used in the present disclosure, including the specification, drawings and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g., data and information. It should be understood that while these words and/or other words that can be synonymous to one another can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.
Embodiments of the presently disclosed techniques and apparatuses include, but are not limited to, the following enumerated examples:
1. A method, in a user equipment, UE, for handling connection reconfiguration commands received during ongoing dual-active protocol stack, DAPS, handovers, the method comprising:
2. The method of example 1, wherein the connection reconfiguration command is a message ordering the UE to move from a connected state to an idle or inactive state, and wherein the method comprises releasing the UE’s connection to the source cell response to the message ordering the UE to move from the connected state to an idle or inactive state, without receiving any explicit indication that the UE’s connection to the source cell is to be released.
3. The method of example embodiment 1, wherein the connection reconfiguration message is a handover command, the handover command specifying a handover to a second target cell.
4. The method of example embodiment 3, wherein the handover command does not include an explicit indication that the UE’s connection to the source cell is to be released, and wherein the method comprises releasing the UE’s connection to the source cell without receiving any explicit indication that the UE’s connection to the source cell is to be released.
5. The method of example embodiment 4, wherein the releasing of the UE’s connection to the source cell without receiving any explicit indication that the UE’s connection to the source cell is to be released is conditioned upon having previously received an indication that implicit source cell release is permitted.
6. The method of example embodiment 3, wherein the handover command includes an explicit indication that the UE’s connection to the source cell is to be released.
7. The method of example embodiment 3, wherein releasing the UE’s connection to the source cell is in response to determining that the handover command does not include an explicit indication that the UE’s connection to the source cell is to be released.
8. The method of example embodiment 3, wherein releasing the UE’s connection to the source cell is in response to determining that the handover command does not include an explicit indication that the UE’s connection to the source cell is to be kept.
9. The method of any of example embodiments 3-8, wherein the handover command is an RRCConnectionReconfiguration message, in an LTE network, or a RRCReconfiguration message, in an NR network.
10. The method of any of example embodiments 3-9, wherein the handover command includes an indication to perform a DAPS handover to the second target cell.
11. The method of example embodiment 10, wherein the method further comprises maintaining the UE’s connection to the first target cell until the UE is instructed to release the UE’s connection to the first target cell or until the UE receives a further handover command.
12. A method, in a first target access node of a radio access network, the method comprising:
13. The method of example embodiment 12, wherein the second handover command includes an explicit indication that the UE is to release the source cell upon receiving the second handover command.
14. The method of example embodiment 12, wherein the second handover command includes an explicit indication that the UE is to keep its connection to the source cell upon receiving the second handover command.
15. The method of any of example embodiments 12-14, wherein the method comprises receiving the second handover command from the second target access node before said transmitting, wherein said transmitting comprises forwarding the second handover command without modification.
16. The method of example embodiment 15, wherein the method comprises sending a handover request message to the second target access node prior to receiving the second handover command from the second target access node, the handover request message including an indication that the UE has not released the source cell from an ongoing DAPS handover.
17. The method of example embodiment 15, wherein the method comprises sending a handover request message to the second target access node prior to receiving the second handover command from the second target access node, the handover request message including an indication that the UE is to release the source cell from an ongoing DAPS handover.
18. The method of any of example embodiments 12-14, wherein the method comprises:
19. The method of any of example embodiments 12-18, wherein the second handover command is an RRCConnectionReconfiguration message, in an LTE network, or a RRCReconfiguration message, in an NR network.
20. The method of any of example embodiments 12-19, wherein the second handover command includes an indication to perform a DAPS handover to the second target cell.
21. A method, in a second target access node of a radio access network, the method comprising:
22. The method of example embodiment 21, wherein the method comprises:
23. The method of example embodiment 21, wherein the method comprises:
24. The method of any of example embodiments 21-23, wherein the handover command includes an explicit indication that the UE is to release the source cell upon receiving the handover command.
25. The method of any of example embodiments 21-23, wherein the handover command includes an explicit indication that the UE is to keep its connection to the source cell upon receiving the handover command.
26. The method of any of example embodiments 21-25, wherein the handover command is an RRCConnectionReconfiguration message, in an LTE network, or a RRCReconfiguration message, in an NR network.
27. The method of any of example embodiments 22-26, wherein the handover command includes an indication to perform a DAPS handover to the second target cell.
28. A user equipment (UE) configured to operate in a radio access network, the UE comprising:
29. A user equipment (UE) for operating in a radio access network, the UE being adapted to perform operations corresponding to any of the methods of claims 1-11.
30. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE), configure the UE to perform operations corresponding to any of the methods of claims 1-11.
31. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE), configure the UE to perform operations corresponding to any of the methods of claims 1-11.
32. A network node configured to serve one or more cells in a radio access network, the network node comprising:
33. A network node adapted to serve at least one cell in a radio access network, the network node being further adapted to perform operations corresponding to any of the methods of claims 12-27.
34. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node, configure the network node to perform operations corresponding to any of the methods of claims 12-27.
35. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node in a radio access network, configure the network node to perform operations corresponding to any of the methods of claims 12-27.
36. A communication system including a host computer comprising:
37. The communication system of the previous embodiment further including the base station.
38. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
39. The communication system of the previous 3 embodiments, wherein:
40. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
41. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
42. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
43. A communication system including a host computer comprising:
44. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
45. The communication system of the previous 2 embodiments, wherein:
46. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
47. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
48. A communication system including a host computer comprising:
49. The communication system of the previous embodiment, further including the UE.
50. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
51. The communication system of the previous 3 embodiments, wherein:
52. The communication system of the previous 4 embodiments, wherein:
53. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
54. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
55. The method of the previous 2 embodiments, further comprising:
56. The method of the previous 3 embodiments, further comprising:
57. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of example embodiments 12-27.
58. The communication system of the previous embodiment further including the base station.
59. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
60. The communication system of the previous 3 embodiments, wherein:
61. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
62. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
63. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2021/050016 | 1/13/2021 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 62968635 | Jan 2020 | US |
