Example embodiments described herein generally relate to communication technologies, and more particularly, to devices and methods for implementing timing advance (TA) alignment between user equipment (UE) and a base station for UE autonomous uplink TA adjustment at beam change.
Certain abbreviations that may be found in the description and/or in the figures are herewith defined as follows:
In 5G New Radio (NR), a base station can be divided into two physical and/or logical entities, i.e., a centralized unit (CU) and a distributed unit (DU). There are several functional split options between the CU and the DU. Generally speaking, the CU provides higher layer functionalities, and the DU provides lower layer functionalities. The DU may be connected via optical fibers to one or more remote radio heads (RRHs) (also known as remote radio units, RRUs). The RRHs include one or more transceivers to receive and transmit signals from and to user equipment (UE). The RRHs may also handle beamforming functionalities. In Frequency Range 2 (FR2), it is a common understanding that both the UE and the network will use beamforming in order to ensure a sufficient link budget.
A brief summary of exemplary embodiments is provided below to provide basic understanding of some aspects of various embodiments. It should be noted that this summary is not intended to identify key features of essential elements or define scopes of the embodiments, and its sole purpose is to introduce some concepts in a simplified form as a preamble for a more detailed description provided below.
In a first aspect, an example embodiment of user equipment is provided. The user equipment may comprise at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the user equipment to perform actions of switching from a first beam associated with a first access point to a second beam associated with a second access point, performing autonomous timing adjustment based on a timing difference between a first timing associated with the first access point and a second timing associated with the second access point, and transmitting assistant information related to the timing difference to the second access point.
In a second aspect, an example embodiment of a base station is provided. The base station may comprise at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the base station to perform actions of receiving from user equipment assistant information related to a timing difference between a first timing associated with a first access point and a second timing associated with a second access point, the base station including at least the second access point, and updating uplink timing of the user equipment maintained at the base station based on the assistant information.
Example embodiments of methods, apparatus and computer program products are also provided. Such example embodiments generally correspond to the above example embodiments of the user equipment and the base station, and a repetitive description thereof is omitted here for convenience.
Other features and advantages of the example embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of example embodiments of the present disclosure.
Some example embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings.
Throughout the drawings, same or similar reference numbers indicate same or similar elements. A repetitive description on the same elements would be omitted.
Herein below, some example embodiments are described in detail with reference to the accompanying drawings. The following description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known circuits, techniques and components are shown in block diagram form to avoid obscuring the described concepts and features.
As used herein, the term “network device” refers to any suitable entities or devices that can provide cells or coverage, through which terminal devices can access the network or receive services. The network device may be commonly referred to as a base transceiver station (BTS) or base station. The term “base station” used herein can represent a node B (NodeB or NB), an evolved node B (eNodeB or eNB), or a gNB. The base station may be embodied as a macro base station, a relay node, or a low power node such as a pico base station or a femto base station. The base station may include several distributed network units, such as a centralized unit (CU), one or more distributed units (DUs), one or more remote radio heads (RRHs) or remote radio units (RRUs). The number and functions of these distributed units depend on the applied split RAN architecture.
As used herein, the term “terminal device” or “user equipment” (UE) refers to any entities or devices that can wirelessly communicate with the network devices or with each other. Examples of the terminal device can include a mobile phone, a mobile terminal (MT), a mobile station (MS), a subscriber station (SS), a portable subscriber station (PSS), an access terminal (AT), a computer, a wearable device, an on-vehicle communication device, a machine type communication (MTC) device, a D2D communication device, a V2X communication device, a sensor and the like. The term “terminal device” can be used interchangeably with UE, a user terminal, a mobile terminal, a mobile station, or a wireless device.
Referring to
As an example,
As discussed above, the RRHs 126 transmit one or more downlink (DL) beams, which of the DL beams the UE 110 is required to use is controlled by the network based on UE-assisted measurements and reporting. The network configures the UE 110 with one or more reference signals (RSs) to measure the beams, which may be synchronization signal block (SSB) (as shown in
However, the current BM concept is based on an assumption that the transmission points for all the DL beams used in a serving cell are collocated, seen from UE point of view. Hence, transmissions from the cell are from the same point in the space, seen from the UE. The UE uses this assumption to direct its Rx beam settings correctly. When the RRHs from one serving cell are located in physically different positions, e.g. in the HST scenario shown in
One such challenge is that in uplink (UL), the basic assumption that UL synchronization and timing advance (TA) used at the UE does not change at the time of beam change (due to the transmission points collocation assumption), is not always true. Referring to
In the current networks, the UL TA is controlled by the network. However, the target RRH 126b cannot measure the UL signals from the UE 110, and consequently the propagation delay, before the beam change. On the other hand, if the wrong TA is used after the beam change, the UL signals could be out of the evaluation window at the base station 120. Moreover, the wrong UL timing could result in significant degradation or complete loss of data transmissions.
One possible solution is to perform autonomous timing adjustment at the UE 110 based on measurements of DL signals received from the source and target RRHs, an example of which is shown in
At 212, the RRH 126a may monitor UL reference signals such as a demodulation reference signal (DMRS) and/or a sounding reference signal (SRS) from the UE 110. The UE 110 transmits the UL signals based on the current TA so that the RRH 126a can receive the UL signals within in a given window. At 214, the base station 120 evaluates UL timing of the UE 110 based on the UL signals received from the UE 110. If the UL signals are received in the reception window, the RRH 126a determines that the current TA is still valid for the UE 110. If the UL signals are not seen by the network as being adequately within the reception window e.g., at least partially out of the reception window, for example due to propagation delay change resulting from UE movement, or for any other reason decided by the network, the RRH 126a may decide that the current TA for the UE 110 needs to be adjusted. Then at 216 the RRH 126a sends a TA adjustment command (TAC) to the UE 110 to adjust the TA for the UE 110. The TAC indicates an amount of adjustment relative to the current TA applied to the UE 110. Accordingly, the UE 110 can update its uplink timing based on the adjusted TA (adjusted by adding the amount of adjustment to the current TA) at 218.
At 220, the UE 110 may receive DL RSs from RRHs including the serving RRH 126a and one or more neighboring/non-serving RRHs such as the RRH 126b. The network may configure the UE 110 with a set of reference signals to monitor quality or signal strength of certain reference signals (RSS) e.g., representing DL radio beams for the beam management purpose. The set of reference signals may include a list of synchronization signal block (SSB) and/or channel state information reference signal (CSI-RS) resources. At the operation 220, the UE 110 may periodically receive the DL RSs from the RRHs 126a, 126b, 126c. At 222, the UE 110 may evaluate DL propagation delay values from the RRHs 126a, 126b to the UE 110 based on the received DL RSs and obtain a DL propagation delay difference (dPD) between the RRH 126a and the RRH 126b. The dPD between the RRH 126a and the RRH 126b is in proportionality with a difference between a distance from the RRH 126a to the UE 110 and a distance from the RRH 126b to the UE 110. It would be appreciated that the UE 110 may evaluate more than one dPD values between the serving RRH 126a and more than one neighboring RRHs in the operation 222.
At 224, the UE 110 may assess quality of the beams based on e.g. L1-RSRP of the received DL RSs and send a beam management related measurement report to the RRH 126a. The beam measurement report may include one or more strongest beam measurements. The UE 110 may send the measurement report periodically or when one or more neighboring/non-serving beams are better than the serving beam or a predetermined threshold level or when the serving beam has a quality worse than a predetermined threshold level. Assuming that the base station 120 determines from the measurement report that the second beam Beam2 of the RRH 126b is (offset) better than the first beam Beam1 of the RRH 126a, the base station 120 may decide at 226 to switch the UE 110 from the first beam Beam1 of the RRH 126a to the second beam Beam2 of the RRH 126b. Then the RRH 126a sends a transmission configuration indicator (TCI) state change command to the UE 110 at 228. The TCI state change command may include e.g. a serving cell ID, a TCI state ID and a control resource set (CORESET) ID associated with a target beam, i.e., the second beam Beam2 of the RRH 126b. The TCI state change command may be carried in downlink control information (DCI) transmitted on the physical downlink control channel (PDCCH) or in a medium access control (MAC) control element (CE).
In response to the TCI state change command received from the base station 120, the UE 110 may switch from the first beam Beam1 of the RRH 126a to the second beam Beam2 of the RRH 126b. Although beam switching by the beam management procedure is discussed here, it would be appreciated that the UE 110 may also perform autonomous beam change. For example, when the UE 110 finds a better beam by measuring available beams, the UE 110 may autonomously decide to switch to the better beam and inform the network of the autonomous beam switching.
The UE 110 may perform at 230 autonomous timing adjustment based on the propagation delay difference dPD between the source RRH 126a and the target RRH 126b, which is also called as a one-shot large autonomous TA adjustment, so that a UL transmission from the UE 110 will, when it is received at the target RRH 126b, align to the DL timing at the base station 120. The propagation delay difference dPD between the source RRH 126a and the target RRH 126b was already evaluated by the UE 110 at the operation 222. For example, referring to
TA2−TA1+2*(PD2−PD1)=TA1+2*dPD (Equation 1)
With the autonomous TA, the UE 110 can resume at 232 UL data transmission on the new beam to the RRH 126b after the beam switch. Similar to the operations 212 and 214, the UE 110 may transmit UL RSs such as DMRS and/or SRS to the RRH 126b at 234, and the base station 120 may evaluate UL timing of the UE 110 based on the UL signals received from the UE 110 at 236. However, it should be noted that the TA for the UE 110 maintained at the base station 120 is still the value TA1 before the UE autonomous TA adjustment, not the UE autonomous TA value TA2. As mentioned above with reference to the operations 214 and 216, the base station 120 determines an amount of adjustment relative to the current TA (TA1) for the UE 110, not an absolute value of the TA. Therefore, the TA value for the UE 110 maintained at the base station 120 would be misaligned with the TA value maintained at the UE 110.
The misalignment of the TA between the UE 110 and the base station 120 would also accumulate as the UE 110 moves along the railway track and switches to subsequent RRHs such as the RRH 126c.
When the UE 110 moves to a second position and switches from the first RRH 126a to the second RRH 126b, the propagation delay between the RRH 126b and the UE 110 becomes PD2, which is different from the propagation delay PD1 between the RRH 126a and the UE 110. The UE 110 performs autonomous TA adjustment as in the operation 230 in
As the UE 110 moves away from the RRH 126b to a third position, the propagation delay between the RRH 126b to the UE 110 becomes PD2′ which is larger than the value PD2 when the UE 110 is at the second position. The base station 120 measures UL RSs such as DMRS and/or SRS as in the operation 212 (
It can be understood from the process shown in
Hereinafter, some example embodiments of devices and methods to ensure TA alignment between UE and the network will be discussed in detail with reference to the accompanying drawings. The example embodiments can minimize or eliminate TA misalignment between the UE and the network without incurring significant signaling overhead increase. Although the HST scenario and the beam management are discussed above to introduce relevant arts, it would be appreciated that the example embodiments may also be applied in other scenarios to both the beam switch by beam management and the UE autonomous beam change.
Referring to
At 320, the UE 110 may perform autonomous timing adjustment based on a timing difference between the first RRH 126a and the second RRH 126b. In some example embodiment, the propagation delay difference dPD between the first RRH 126a and the second RRH 126b may be used as an example of the timing difference, based on which the UE 110 may autonomously adjust its uplink timing so that UL transmission, when it is received at the RRH 126b, will align to the DL timing at the RRH 126b. As discussed above, the UE 110 can get in DL synchronization with the first RRH 126a and the second RRH 126b by receiving DL RSs such as SSB and/or CSI-RS and evaluate the propagation delay difference dPD between the first RRH 126a and the second RRH 126b.
Then the UE 110 may transmit assistant information related to the timing difference to the second RRH 126b for the TA alignment purpose at 330. In some example embodiment, the assistance information may be requested by the network e.g. after beam switch has been performed (not illustrated in the figure). Based on the assistant information related to the timing difference, the base station 120 can update the TA value for the UE 110 so as to align with the TA maintained at the UE 110. Although
Referring to
The UE 110 may receive DL RSs such as SSB and CSI-RS from the RRHs 126a, 126b at 304 and evaluate a propagation delay difference dPD between the RRHs 126a and 126b at 306.
When the base station 120 decides at 312 to switch the UE 110 from the first RRH 126a to the second RRH 126b e.g., based on a beam measurement report received from the UE 110, the base station 120 may transmit a TCI state change command to the UE 110 e.g., via DCI on PDCCH or via MAC CE at 314. The TCI state change command may comprise a TCI state ID and a control resource set (CORESET) ID associated with the second beam Beam2 of the second RRH 126b. The TCI state includes information of one or more DL RSs and quasi co-located (QCL) type associated with the respective DL RSs. Then the UE 110 may replace the first beam Beam1 of the first RRH 126a with the second beam Beam2 of the second RRH 126b by activating the new TCI state indicated in the TCI state change command. In some example embodiments where the RRH 126b serves a cell different from the cell served by the RRH 126b, the TCI state change command may further comprise a cell ID indicating the new cell for the beam switching.
In some example embodiments, the TCI state change command transmitted in the operation 314 may carry the instruction to report autonomous TA adjustment, and the operation 302 may be omitted. For example, a special CORESET ID or TCI state ID may be defined/reserved to indicate that the UE 110 is instructed to report the autonomous TA adjustment.
In some example embodiments, the UE 110 may perform autonomous beam switching based on for example beam measurements, and the operations 312, 314 may be omitted.
As discussed above, in some example embodiments, the RRHs 126a, 126b may belong to different base stations. In such a case, the source base station including the RRH 126a may indicate to the target base station including the RRH 126b that the UE 110 will switch to a beam operated by the RRH 126b and further send UE context information via an Xn interface to the target base station. The UE context may include information such as UE TA maintained at the network side. In some example embodiments, instead of the operation 302, the RRH 126b may instruct the UE 110 to report autonomous timing adjustment when it receives the indication of beam switching for the UE 110.
At 322, the UE 110 may perform autonomous timing adjustment based on e.g. the propagation delay difference dPD between the first RRH 126a and the second RRH 126b obtained in the operation 306. Then the UE 110 can send UL transmissions to the second RRH 126b using the autonomous TA.
As the autonomous TA at the UE 110 may be different from the TA maintained at the base station 120 for the UE 110, the UE 110 may report the autonomous timing adjustment to the second RRH 126b at 332. The autonomous timing adjustment report may indicate an amount (dPD) of the adjustment relative to the old timing (TA) as the assistant information for the TA alignment to the base station 120. In some example embodiments, the UE 110 may use a CSI report to send the amount of the autonomous timing adjustment.
Then at 342, the base station 120 may update the TA value for the UE 110 based on the amount of the autonomous timing adjustment performed at the UE 110. By the operation 342, the TA maintained at the base station 120 for the UE 110 may be aligned to the autonomous TA at the UE 110. In subsequent operations, the base station 120 may periodically monitor UL RSs such as DMRS and/or SRS from the UE 110 and update the TA at the UE 110 by the TA adjustment command if needed.
In the procedure shown in
Referring to
At 404, the base station 120 may configure RA resources for the UE 110. For example, the base station 120 may allocate a dedicated (contention free) preamble for the UE 110 via RRC signaling e.g. ra-PreambleIndex or DCI on the PDCCH. For example, when there are not many UEs in a cell, the network can allocate dedicated preambles for the UEs. The base station 120 can identify the UE 110 when it receives the dedicated preamble allocated to the UE 110. If there are many UEs in a cell and the base station 120 cannot allocate a dedicated preamble for a UE, the UE can select a preamble from a set of common (contention-based) preambles, and the operation 404 may be omitted.
In some example embodiments, the base station 120 may also allocate dedicated UL resources for the UE 110 to transmit a contention based or contention free preamble in the operation 404.
The UE 110 may receive DL RSs such as SSB and CSI-RS from the RRHs 126a, 126b at 304 and evaluate a propagation delay difference dPD between the RRHs 126a and 126b at 306. When the base station 120 decides to switch the UE 110 from the RRH 126a to the RRH 126b e.g. based on a measurement report at 312, the base station 120 may transmit a TCI state change command to the UE 110 via DCI MAC CE at 414. In response to the TCI state change command, the UE 110 may switch to RRH 126b by activating the new TCI state indicated in the command.
In some example embodiments, the TCI state change command transmitted in the operation 414 may carry the instruction to transmit the RA preamble upon the autonomous TA adjustment, and the operation 402 may be omitted. For example, the TCI state change command may include a special CORESET ID or TCI state ID that is defined/reserved to indicate the instructed of transmitting the RA preamble.
In some example embodiments, the UE 110 may perform autonomous beam switching based on for example beam measurements, and the operations 312, 414 may be omitted.
In some example embodiments where the RRHs 126a, 126b belong to different base stations, the source base station including the RRH 126a may indicate to the target base station including the RRH 126b that the UE 110 will switch to a beam operated by the RRH 126b and further send UE context information via an Xn interface to the target base station. The UE context may include information such as UE TA maintained at the network side. In some example embodiments, instead of the operations 402 and 404, the RRH 126b may instruct the UE 110 to send RA preamble and allocate resources for transmission of the RA preamble when it receives the indication of beam switching for the UE 110.
At 322, the UE 110 may perform autonomous timing adjustment based on the timing difference e.g. the propagation delay difference dPD between the first RRH 126a and the second RRH 126b obtained in the operation 306. Then the UE 110 can send UL transmissions to the second RRH 126b using the autonomous TA.
At 434, the UE 110 may transmit a random access RA preamble to the second RRH 126b. If the UE 110 has been allocated with a dedicated (contention-free) preamble at the operation 404, the UE 110 may use the allocated dedicated preamble in the operation 434. If the base station 120 does not allocate a dedicated preamble to the UE 110, the UE 110 may transmit a contention-based preamble to the base station 120. In some example embodiments, the UE 110 may transmit the RA preamble on a physical random access channel (PRACH) or using dedicated UL resources allocated e.g. in the operation 404.
Then at 442, the base station 120 may calculate UE UL timing e.g. a valid TA value based on the received preamble.
Referring back to
Referring to
In some example embodiments where the RRHs 126a, 126b belong to different base stations, when the source base station including the RRH 126a triggers the beam switching for the UE 110 at the operation 414, the source base station may indicate the beam switching to the target base station including the RRH 126b and further send UE context information via an Xn interface to the target base station. The UE context may include information such as UE TA maintained at the network side. In some example embodiments, instead of the operation 404, the RRH 126b may allocate resources for transmission of the RA preamble when it receives the indication of beam switching for the UE 110.
In the above example embodiments, the network performs the TA alignment in response to a message e.g. the autonomous TA report or the PRACH preamble from the UE 110. In some example embodiments, the network may perform the TA alignment proactively, an example of which is shown in
Referring to
As the base station 120, which is associated with both the RRHs 126a and 126b, knows the propagation delay difference of the second beam Beam2 of the second (target) RRH 126b relative to the first beam Beam1 of the first (source) RRH 126a from the beam measurement report at the operation 608, the base station 120 can perform TA alignment based on the propagation delay difference of the second beam Beam2 at 642 after it sends the TCI state change command to the UE 110 at 314. In some example embodiments, the base station 120 may monitor UL transmissions from the UE 110 to the first RRH 126a and the second RRH 126b to confirm if the beam switching is successful or not. When the base station 120 determines that the beam switching has been performed successfully, the base station 120 may perform the TA alignment. In some example embodiments, the base station 120 may perform the TA alignment when it is informed by the UE 110 that the UE 110 has autonomously switched to the second beam Beam2 of the RRH 126b.
In some example embodiments where the RRHs 126a, 126b belong to different base stations, the UE 110 sends the beam measurement report including the candidate beams and the timing difference (dPD) of the candidate beams relative to the serving beam may be sent to the source base station including the first RRH 126a. When the source base station triggers the beam switching for the UE 110 at the operation 314, the source base station may indicate the beam switching to the target base station including the RRH 126b. For example, source base station may notify the target base station of the target beam and the timing difference (dPD) of the target beam relative to the source beam. The source base station may further send UE context information via an Xn interface to the target base station. The UE context may include information such as UE TA maintained at the network side.
Referring to
The network device 720 may comprise one or more processors 721, one or more memories 722, one or more transceivers 723 and one or more network interfaces 727 interconnected through one or more buses 724. The one or more buses 724 may be address, data, or control buses, and may include any interconnection mechanism such as a series of lines on a motherboard or integrated circuit, fiber, optics or other optical communication equipment, and the like. Each of the one or more transceivers 723 may comprise a receiver and a transmitter, which are connected to one or more antennas 726. The network device 720 may wirelessly communicate with the terminal device 710 through the one or more antennas 726. The one or more transceivers 723 and the one or more antennas 726 may be implemented as one or more remote radio heads (RRHs) 728. The one or more RRHs 728 may be collocated or located at different positions. The one or more buses 724 could be implemented in part as fiber optic cable to connect the RRHs 728 to other components of the network device 720. The one or more network interfaces 727 may provide wired or wireless communication links through which the network device 720 may communicate with other network devices, entities, elements or functions. The one or more memories 722 may include computer program code 725. The one or more memories 722 and the computer program code 725 may be configured to, when executed by the one or more processors 721, cause the network device 720 to perform processes and steps relating to the base station 120 as described above.
The one or more processors 711, 721 and 731 discussed above may be of any appropriate type that is suitable for the local technical network, and may include one or more of general purpose processors, special purpose processor, microprocessors, a digital signal processor (DSP), one or more processors in a processor based multi-core processor architecture, as well as dedicated processors such as those developed based on Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC). The one or more processors 711, 721 and 731 may be configured to control other elements of the UE/network device/network element and operate in cooperation with them to implement the procedures discussed above.
The one or more memories 712, 722 and 732 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory. The volatile memory may include but not limited to for example a random access memory (RAM) or a cache. The non-volatile memory may include but not limited to for example a read only memory (ROM), a hard disk, a flash memory, and the like. Further, the one or more memories 712, 722 and 732 may include but not limited to an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
It would be understood that blocks in the drawings may be implemented in various manners, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more blocks may be implemented using software and/or firmware, for example, machine-executable instructions stored in the storage medium. In addition to or instead of machine-executable instructions, parts or all of the blocks in the drawings may be implemented, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-Chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
Some exemplary embodiments further provide computer program code or instructions which, when executed by one or more processors, may cause a device or apparatus to perform the procedures described above. The computer program code for carrying out procedures of the exemplary embodiments may be written in any combination of one or more programming languages. The computer program code may be provided to one or more processors or controllers of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
Some exemplary embodiments further provide a computer program product or a computer readable medium having the computer program code or instructions stored therein. The computer readable medium may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
Although the subject matter has been described in a language that is specific to structural features and/or method actions, it is to be understood the subject matter defined in the appended claims is not limited to the specific features or actions described above. On the contrary, the above-described specific features and actions are disclosed as an example of implementing the claims.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2021/079095 | 10/20/2021 | WO |