Orthogonal cover code with global navigation satellite system fix

Abstract

Example embodiments of the present disclosure are directed to orthogonal cover code (OCC) with global navigation satellite system (GNSS) fix. A method comprises receiving a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and performing a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

Description

ORTHOGONAL COVER CODE WITH GLOBAL NAVIGATION SATELLITE SYSTEM FIXFIELD

[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for orthogonal cover code (OCC) with global navigation satellite system (GNSS) fix.BACKGROUND

[0002] OCC is a coding technique that can be used to enhance the multiplexing capacity / throughput of a cellular network. One could generate a set of orthogonal codes (e.g. Walsh-Hadamard codes) having ideal zero cross-correlation and assign different codes to different UEs to achieve orthogonal uplink transmissions on the same timefrequency resources.SUMMARY

[0003] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: obtain a configuration of an OCC operation associated with a GNSS based timing advance (TA) update at the first apparatus; and determine, based on the configuration, whether an uplink transmission is to be performed and / or an OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0004] In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: determine a configuration of an OCC operation associated with a GNSS based TA update at a first apparatus; and transmit the configuration to the first apparatus.

[0005] In a third aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: obtain a configuration indicating that at least one TA parameter is not to beapplied within an OCC time window; and perform the TA update with an open-loop type and / or a closed loop type based on the configuration.

[0006] In a fourth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: determine a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and transmit the configuration to the first apparatus.

[0007] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and perform the GNSS based TA update based on the configuration.

[0008] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: determine a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and transmit the configuration to the first apparatus.

[0009] In a seventh aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and perform a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

[0010] In an eighth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: determine a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; andtransmit the configuration to the first apparatus.

[0011] In a ninth aspect of the present disclosure, there is provided a method. The method comprises: obtaining a configuration of an OCC operation associated with a GNSS based TA update at the first apparatus; and determining, based on the configuration, whether an uplink transmission is to be performed and / or an OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0012] In a tenth aspect of the present disclosure, there is provided a method. The method comprises: determining a configuration of an OCC operation associated with a GNSS based TA update at a first apparatus; and transmitting the configuration to the first apparatus.

[0013] In an eleventh aspect of the present disclosure, there is provided a method. The method comprises: obtaining a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and performing the TA update with an open-loop type and / or a closed loop type based on the configuration.

[0014] In a twelfth aspect of the present disclosure, there is provided a method. The method comprises: determining a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and transmitting the configuration to the first apparatus.

[0015] In a thirteenth aspect of the present disclosure, there is provided a method. The method comprises: receiving a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and performing the GNSS based TA update based on the configuration.

[0016] In a fourteenth aspect of the present disclosure, there is provided a method. The method comprises: determining a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and transmitting the configuration to the first apparatus.

[0017] In a fifteenth aspect of the present disclosure, there is provided a method. The method comprises: receiving a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and performing a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

[0018] In a sixteenth aspect of the present disclosure, there is provided a method. The method comprises: determining a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and transmitting the configuration to the first apparatus.

[0019] In a seventeenth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for obtaining a configuration of an OCC operation associated with a GNSS based TA update at the first apparatus; and means for determining, based on the configuration, whether an uplink transmission is to be performed and / or an OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0020] In an eighteenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for determining a configuration of an OCC operation associated with a GNSS based TA update at a first apparatus; and means for transmitting the configuration to the first apparatus.

[0021] In a nineteenth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for obtaining a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and means for performing the TA update with an open-loop type and / or a closed loop type based on the configuration.

[0022] In a twentieth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for determining a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and means for transmitting the configuration to the first apparatus.

[0023] In a twenty-first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and means for performing the GNSS based TA update based on the configuration.

[0024] In a twenty-second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for determining a configuration associated with a dropping of an uplink data transmission under a GNSS based TA updateoccurring within an OCC time window; and means for transmitting the configuration to the first apparatus.

[0025] In a twenty-third aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and means for performing a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

[0026] In a twenty-fourth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for determining a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and means for transmitting the configuration to the first apparatus.

[0027] In a twenty-fifth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the ninth aspect.

[0028] In a twenty-sixth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the tenth aspect.

[0029] In a twenty-seventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the eleventh aspect.

[0030] In a twenty-eighth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the twelfth aspect.

[0031] In a twenty-ninth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the thirteenth aspect.

[0032] In a thirtieth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourteenth aspect.

[0033] In a thirty-first aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fifteenth aspect.

[0034] In a thirty-second aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the sixteenth aspect.

[0035] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Some example embodiments will now be described with reference to the accompanying drawings, where:

[0037] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

[0038] FIG. 2 illustrates an example of OCC of length 2 for different UEs doing 2 Physical Uplink Shared Channel (PUSCH) repetitions in same time-frequency resources;

[0039] FIG. 3 illustrates an example that GNSS fix impacts the OCC orthogonality;

[0040] FIG. 4 illustrates a signaling chart for a communication in accordance with some example embodiments of the present disclosure;

[0041] FIG. 5 illustrates a signaling chart for a communication in accordance with some example embodiments of the present disclosure;

[0042] FIG. 6 illustrates a signaling chart for a communication in accordance with some example embodiments of the present disclosure;

[0043] FIG. 7 illustrates a signaling chart for a communication in accordance with some example embodiments of the present disclosure;

[0044] FIG. 8 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;

[0045] FIG. 9 illustrates a flowchart of a method implemented at a second apparatus inaccordance with some example embodiments of the present disclosure;

[0046] FIG. 10 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;

[0047] FIG. 11 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;

[0048] FIG. 12 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;

[0049] FIG. 13 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;

[0050] FIG. 14 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;

[0051] FIG. 15 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;

[0052] FIG. 16 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

[0053] FIG. 17 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

[0054] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION

[0055] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

[0056] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0057] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

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

[0059] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

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

[0061] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0062] As used in this application, the term “circuitry” may refer to one or more or all ofthe following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause a first apparatus, such as a mobile phone or server, to perform various functions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0063] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0064] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), 5.5G, the sixth generation (6G) communication protocols,and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0065] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.

[0066] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remotesurgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0067] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0068] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. As shown in FIG. 1, the communication network 100 may comprise a first apparatus 110 which may be, for example, a terminal device. In some example embodiments, the terminal device may also be discussed as a UE.

[0069] The communication network 100 may further comprise a second apparatus 120, which may be, for example, a network device. In some example embodiments, the network device may be discussed as a BS, a gNB, or an eNB.

[0070] A serving area provided by the first apparatus 110 is called a cell. The second apparatus 120 may communicate with the first apparatus 110 within the cell 102. The cell currently serving the second apparatus 120 may be considered as a serving cell 102.

[0071] In the following, for the purpose of illustration, some example embodiments are described with the first apparatus 110 operating as a terminal device and the second apparatus 120 operating as a network device. However, in some example embodiments,operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.

[0072] In some example embodiments, if the first apparatus 110 is a terminal device and second apparatus 120 is a network device, a link from the second apparatus 120 to first apparatus 110 is referred to as a downlink (DL), while a link from the first apparatus 110 to second apparatus 120 is referred to as an uplink (UL). In DL, the second apparatus 120 is a transmitting (TX) apparatus (or a transmitter) and the first apparatus 110 is a receiving (RX) apparatus (or a receiver). In UL, the first apparatus 110 is a TX apparatus (or a transmitter) and the second apparatus 120 is a RX apparatus (or a receiver).

[0073] It is to be understood that the number of network devices and terminal devices shown in FIG. 1 is given for the purpose of illustration without suggesting any limitations. The communication environment 100 may include any suitable number of network devices and terminal devices.

[0074] Communications in the communication environment 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G), the sixth generation (6G), and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0075] Some schemes on NR Non-Terrestrial Network (NR NTN) enhancements were discussed and approved. The uplink capacity / throughput enhancement for Frequency Range 1 -Non-Terrestrial Network (FR1-NTN) can be achieved, in particular using orthogonal cover codes (OCC). The objective description is as follows:Uplink Capacity / Throughput Enhancement for FR1-NTN:• Study then specifies, if beneficial, DFT-s-OFDM Physical Uplink Shared Channel (PUSCH) enhancements via the OCC o Determine the achievable capacity improvement to be targeted taking into account realistic impairments (e.g. Doppler, time variation, phase distortion, etc.) o Specify necessary signaling, if needed o Update Radio Frequency (RF) requirements accordingly, if needed o Note: The study can consider orthogonal cover codes across OFDM symbols, across slots, and / or within an OFDM symbol. o Note: the study phase is targeted to be completed in future specification• Notes for this objective: o The enhancement is not targeting improvements / impacts of Multi-User Multiple-Input Multiple-Output (MU-MIMO) capability o The enhancement is not targeted to PUSCH Demodulation Reference Signal (DMRS) o No enhancement for initial access o Enhancements to Physical Random Access Channel (PRACH) are not in scope. o This feature may be applicable for UEs operating in terrestrial networks based on a common design

[0076] Hence, the applicability of the OCC to the NTN NR PUSCH is being discussed and potential issues and enhancements may be identified if necessary. In the above- mentioned objectives, the OCC is providing multiplexing gain in the code domain while using the same time-frequency resources. As can be seen from the above description of the objective, the study can consider the OCC in time domain across OFDM symbols, across slots, and / or within an OFDM symbol.

[0077] The latest agreements are as follows:For the normative phase, at least one of the OCC techniques will be specified:• Inter-slot time-domain OCC with PUSCH repetition Type A with OCC length 2 or 4• Inter-symbol(s) time domain OCC with the OCC length 2 or 4• Intra-symbol pre-DFT-s OCC (comb-like structure as in Physical Uplink Control Channel (PUCCH) format 4) with the OOC length 2 or 4• For Further Study (FFS) Combination of OCC techniques including multiplexing of 8 UEs• FFS Use of OCC techniques with Transport Block Processing over Multiple Slot (TBoMS)• FFS Backward compatibility with previously discussed UEs

[0078] The OCC is a coding technique that can be used to enhance the multiplexingcapacity / throughput of a cellular network. One could generate a set of orthogonal codes (e.g. Walsh-Hadamard codes) having ideal zero cross-correlation and assign different codes to different UEs to achieve orthogonal (i.e. no interference) UL transmissions on the same time-frequency resources.

[0079] To illustrate the principle of OCC, an example is shown in FIG. 2 wherein two UEs are transmitting 2 PUSCH repetitions at the same time-frequency resources. For the transmissions, the two UEs apply different OCCs to their transmission signal (which is assumed here to stay constant across the repetitions) allowing a gNB receiver to receive (i.e. demodulate and decode) the signals of each UE without the interference of the other UE. In mathematical form, how this works is represented in the system of Equation 1 below (without channel impairments and additive noise for simplicity of description):

[0080] In Equation 1, xi and X2 are the signals transmitted by the UEi and the UE2, respectively and in both repetitions, whereas yi and y2 are the total signals received by the gNB in the first and second repetition, respectively. It is to be noted that in this example, UEi is applying the OCC [1, 1] whereas UE2 is applying the OCC [1, -1], In the example of the equations, the gNB retrieves the signal of the UE2 without interference from UEi by cross correlating the two received signal yi and y2 with the OCC used by UE2 (i.e. [1, -1]). For generating the digital cross-correlation, the normal operation used is “sum of the products” at time “zero”.

[0081] The example shown in FIG. 2 and Equation 1 is only illustrative and uses Walsh- Hadamard orthogonal codes as the OCC set. Different sequences can be used to realize orthogonality among users without impacting the applicability, where one known alternative to the Walsh-Hadamard codes is the functions that are defined as part of the Discrete Fourier transform (DFT). In addition, it is to be noted that in general, in order to multiplex N UEs, a number of at least N PUSCH (or signal) repetitions (or duplications) per UE are necessary.

[0082] In some previously discussed schemes, the NTN UE is equipped with GNSS capability which can be used by the NTN UE to know its position. This information, when combined with satellite ephemeris information (either broadcasted by the network or provisioned via other means), allows the UE to carry out the frequency pre-compensationand the timing adjustment.

[0083] The ephemeris information can be represented by either the position-velocity vector format or the orbital element format. In either case, the UE applies the orbit propagation to determine the delay and Doppler frequency of the service link at any time. Some NTN system architectures require the UE to estimate the feeder link delay and delay variation. For this purpose, the network provides the UE with another information called TA common, which is in the form of coefficients of a quadratic polynomial and indicates the feeder link variation over time. Combined with location knowledge, the UE can apply a timing advance described by the following Equation 2:

[0084] In Equation 2, NTAis the closed-loop timing advance element based on feedback received from the network (NW); NTA UE-specificis UE self-estimated TA based on ephemeris and UE location information to pre-compensate for the service link delay; NTA, common is network-controlled common TA that can be computed by the UE based on received TA common parameters; NTA> Offsetis a fixed offset reserved by the NW for additional timing advance control; and Tcis the smallest timing unit equal to 0.508ns.

[0085] The NTN UE may be equipped with the GNSS receiver and the 5G module. The 5G module is designed under 3GPP framework, while the GNSS receiver is designed separately. Therefore, radio protocol specification can not specify the procedure to control GNSS behavior, meaning that the GNSS update / fix is not controlled by the NW.

[0086] The GNSS fix timeline is not controlled by the NW, however, the UE uses the GNSS output for the UE to apply the pre-compensate to the service link delay as follows: NTA,UE- specif ic isaUE self-estimated TA based on ephemeris and UE location information to pre-compensate for the service link delay. This means that the timing adjustment at the UE is largely dependent by the GNSS output and thus largely dependent by the GNSS fix.

[0087] In the OCC, orthogonality of N sequences associated to N UEs, is dependent on the time synchronization between the N UEs. The time misalignment impacts the OCC orthogonality and thus the OCC performance, since each UE would unintentionally create interference to other UEs that are multiplexed with the OCC.

[0088] Reference is now made to FIG. 3, which shows a situation where a problem of time misalignment appears when the GNSS fix occurs during the OCC time window. The occurrence of the GNSS fix during the OCC time window may potentially breaks the OCC orthogonality and degrades all the UEs performance. As shown in FIG. 3, since the NTA,UE- specif ic is UE self-estimated, and each NTA UE-specificestimated by each UE may very which result in an influence on the alignment of the OCC sequence. Therefore, a solution for how a UE should handle the GNSS fix if it occurs during OCC time window subject to maintaining the orthogonality between OCC sequences is desirable. Similar problem can occur if the UE applies the TA adjustment during OCC window. However, this problem is less severe as the NW is controlling NTA, i.e., the closed-loop timing advance element.

[0089] The present disclosure proposes a solution of best effort radio resource management measurements. In this solution, the first apparatus 110, upon receiving the

[0090] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0091] Reference is now made to FIG. 4, which shows a signaling chart 400 for communication according to some example embodiments of the present disclosure. As shown in FIG. 4, the signaling chart 400 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 400.

[0092] The first apparatus 110 may send (405) capabilities related to the OCC operation in presence of the GNSS based TA update. For example, the first apparatus 110 may report, to the second apparatus, a capability for supporting a full OCC transmission or a partial OCC transmission. Hereinafter, the full OCC transmission means the OCC operation can be applied for the uplink transmission within an OCC time window comprising a plurality of slots. The partial OCC transmission means the OCC operation can be applied for the uplink transmission on one or more slot within an OCC time window, e.g., the first one or more slots within an OCC time window and the uplink transmission on other slots within an OCC time window may be omitted or dropped.

[0093] For example, during the first one or more slots within an OCC time window, the estimated TA is below a threshold, or no TA update occurred, and thus the OCC PUSCH transmission may start, then at least one of the following slots during the OCC time10window, the estimated TA becomes larger than the threshold and thus the first apparatus 110 may stop the OCC transmission. That is, the partial OCC transmission may occur within the OCC time window.

[0094] The second apparatus 120 may configure (410) the UE behavior with the GNSS TA update. The configuration, for example, may indicate a full OCC transmission, a partial OCC transmission or an uplink transmission dropping is allowed under the GNSS based TA update occurring within the OCC time window.

[0095] Thus, the first apparatus 110 may obtain (415) a configuration of an OCC operation associated with the GNSS based TA update. The OCC operation associated with the GNSS based TA update may be understood as being behaviors of the first apparatus 110 for performing OCC uplink transmission in case of an occurrence of TA update of the first apparatus 110, which may impact the orthogonality of the OCC, e.g., if the time frame of the TA update overlaps with the OCC time window. It is to be understood that the TA update may refers to GNSS based TA update or autonomous TA update or a generic TA update.

[0096] The configuration of an OCC operation associated with the GNSS based TA update may also configure some conditions, e.g., a set of events for which the first apparatus 110 may drop the UL transmission.

[0097] The OCC time window used hereinafter may refer to a time interval on which the OCC UL transmi ssion(s) is allowed for the first apparatus 110. The OCC time window may comprise a plurality of slots.

[0098] As another option, the configuration may be pre-configured. That is, the first apparatus 110 may obtain the configuration without a signaling exchange with the second apparatus 120.

[0099] Based on the configuration, the second apparatus 120 may configure and schedule (420) the UL OCC transmission. Then the first apparatus 110 may determine (425) when / how to drop / transmit the OCC transmission if the GNSS update occurs. As an example, the first apparatus 110 may determine whether an uplink transmission is to be performed within an OCC time window. If the first apparatus 110 determines the uplink transmission is to be performed within the OCC time window, the first apparatus 110 may further determine an OCC transmission pattern under the GNSS based TA updateoccurring within the OCC time window, i.e., a full OCC transmission or a partial OCC transmission.

[0100] For example, first apparatus 110 may also obtain an indication of a threshold associated with the GNSS-based TA update to help the first apparatus 110 to determine the OCC transmission pattern under the GNSS based TA update occurring within the OCC time window. For example, during the one or more slots, e.g., the first one or more slots, within the OCC time window, the estimated TA is below the threshold, the OCC uplink transmission may start within the OCC time window.

[0101] In addition to the configuration, the first apparatus 110 may also obtain an indication of at least one time frame associated with the GNSS based TA update, which may indicate a time instance within which the first apparatus 110 is allowed to perform the GNSS based TA update.

[0102] Furthermore, the first apparatus 110 may also obtain an indication associated with enabling or disabling the GNSS based TA update. This indication may be indicated by the second apparatus 120 dynamically.

[0103] If the first apparatus 110 determines the uplink transmission is to be performed within the OCC time window, the first apparatus 110 may send (430) the UL data to the second apparatus 120, e.g., by using a determined OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0104] The firs apparatus 110 may report (435) how the OCC data was treated to the second apparatus 120. That is, the first apparatus 110 may report a determination of the OCC transmission pattern to the second apparatus 120. Then the second apparatus 120 may perform uplink transmission and / or repetition from the first apparatus 110 based on the determined OCC transmission pattern.

[0105] Reference is now made to FIG. 5, which shows a signaling chart 500 for communication according to some example embodiments of the present disclosure. As shown in FIG. 5, the signaling chart 500 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 500.

[0106] The first apparatus 110 may determine (510) at least one TA parameter component is not to be applied within an OCC time window. The TA parameter maycomprise an open-loop TA parameter and / or a closed-loop TA parameter. The openloop TA parameter, for example, may comprise an update of a TA controlled by the second apparatus 120, e.g., NTA common, and / or an self-estimated TA by the first apparatus 110, e.g., NTA)UE-specifiC- The closed-loop TA parameter may comprise a TA element based on feedback received from a second apparatus 120, i.e., NTA.

[0107] For example, the second apparatus 120 may indicate (505) the at least TA parameter / component is not applied during the OCC time window. It is also possible that whether at least TA parameter / component is or is not applied during the OCC time window may be pre-configured, i.e., determined by the first apparatus 110. That is, the first apparatus 110 may obtain this configuration without a signaling exchange with the second apparatus 120. The first apparatus 110, if it determines that TA parameter / component is not applied during the OCC time window, may apply the TA parameter / component at the end of the OCC time window.

[0108] The second apparatus 120 may configure and schedule (520) the UL OCC transmission.

[0109] Based on the configuration whether the at least TA parameter / component is not applied during the OCC time window, the second apparatus 120 may perform (525) the TA update based on the GNSS fix, e.g., prior to 1stOCC transmission or after the last OCC transmission.

[0110] For example, if the at least TA parameter / component is not applied during the OCC time window and the first apparatus 110 determines the TA update occurs within the OCC time window, the first apparatus 110 may postpone the TA update to a slot after the OCC time window. For example, the first apparatus 110 may postpone the TA update to right at the end of the OCC time window.[OHl] In some embodiments, only if the TA update occurs in the first slot of the OCC time window, the first apparatus 110 may perform the TA update.

[0112] Optionally, the second apparatus 120 may indicate (515) to perform the TA based on the GNSS fix. If the first apparatus 110 receives from the second apparatus, an indication for the first apparatus to perform the TA update based on a GNSS fix, the first apparatus 110 may perform the TA update based on the GNSS fix after a completion of an OCC uplink transmission or before a beginning of the OCC uplink transmission.

[0113] In some example embodiments, the second apparatus 120 may indicate the first apparatus 110 to disable an GNSS fix within the OCC time window. If so, after sending (530) the OCC uplink transmission within the OCC time window, e.g., by using full OCC transmission, the first apparatus 110 may set back the GNSS fix autonomously.

[0114] In some other embodiments, after the OCC uplink transmission is received by the second apparatus 120, the second apparatus 120 may indicate (535) to enable / resume the TA based on the GNSS fix. The first apparatus 110 may resume (540) the GNSS fix.

[0115] Reference is now made to FIG. 6, which shows a signaling chart 600 for communication according to some example embodiments of the present disclosure. As shown in FIG. 6, the signaling chart 600 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 600.

[0116] The second apparatus 120 may determine (605) a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window. For example, the second apparatus 120 may configure the behavior of the first apparatus 110 based on the open-loop TA parameter estimation (e.g., to drop uplink data transmission, e.g., PUSCH transmission, if the UE self-determined TA is larger than a threshold.

[0117] The second apparatus 120 may send, to the first apparatus 110, the configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window The first apparatus 110 may obtain (610) the configuration.

[0118] As another option, the configuration may be pre-configured. That is, the first apparatus 110 may obtain the configuration without a signaling exchange with the second apparatus 120.

[0119] In some embodiments, the second apparatus 120 may indicate (615) a threshold related to the UE self-determined TA with the GNSS. The threshold may be associated with a time frame and / or a periodicity of GNSS based TA update.

[0120] The second apparatus 120 may configure and schedule (620) the UL OCC transmission. The first apparatus 110 may determine (630) to fully transmit or omit the OCC data at least based on the received configuration and / or the threshold.

[0121] In some example embodiments, if the first apparatus 110 determines that the GNSS based TA update occurs within the OCC time window, the first apparatus 110 may drop the uplink data transmission.

[0122] As described, the threshold may be indicated by the second apparatus 120. In some other example embodiments, if the first apparatus 110 determines that the GNSS based TA update occurs within the OCC time window and an estimated_open-loop TA parameter is larger than the threshold, the first apparatus 110 may drop the uplink data transmission.

[0123] Optionally, the second apparatus 120 may also indicate (625) to drop the uplink data transmission.

[0124] If the first apparatus determines a dropping of the uplink data transmission, the first apparatus 110 may indicate (635) to the second apparatus 120 the uplink data transmission dropping.

[0125] Reference is now made to FIG. 7, which shows a signaling chart 700 for communication according to some example embodiments of the present disclosure. As shown in FIG. 7, the signaling chart 700 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 700.

[0126] The first apparatus 110 may send (705) capability for partial OCC transmission to the second apparatus 120. As described above, the partial OCC transmission means the OCC operation can be applied for the uplink transmission on one or more slot within an OCC time window, e.g., the first one or more slots within an OCC time window and the uplink transmission on other slots within an OCC time window may be omitted or dropped.

[0127] The second apparatus 120 may configure (710) the UE behavior in case of the GNSS update during the OCC, e.g., to perform the partial OCC transmission. The configuration, for example, may indicate an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window.

[0128] As another option, the configuration may be pre-configured. That is, the first apparatus 110 may obtain the configuration without a signaling exchange with the second apparatus 120.

[0129] The second apparatus 120 may indicate (715) a threshold related to the estimationof the UE self-determined TA with the GNSS and the partial OCC transmission, which may be used for the first apparatus to determine whether the partial OCC transmission is to be performed. It is also possible that the first apparatus 110 may determine the threshold based on a periodicity of the GNSS based TA update.

[0130] For example, during the first one or more slots within an OCC time window, the estimated TA is below a threshold, or no TA update occurred, and thus the OCC PUSCH transmission may start, then at least one of the following slots during the OCC time window, the estimated TA becomes larger than the threshold and thus the first apparatus 110 may stop the OCC transmission. That is, the partial OCC transmission may occur within the OCC time window.

[0131] The second apparatus 120 may configure and schedule (720) the OCC transmission. Based on the obtained configuration and the threshold, the first apparatus 110 may determine (725) to perform a full OCC uplink transmission or a partial OCC uplink transmission, e.g., transmit the full OCC UL data or a partial of the OCC UL data based on the estimation of the self-determined TA based on the GNSS update.

[0132] In some example embodiments, if the GNSS based TA update is after the last OCC transmission or before the first OCC uplink transmission, the first apparatus 110 may perform (730) a full OCC uplink transmission within the OCC time window.

[0133] In some other example embodiments, if an estimated_open-loop TA parameter is not larger than a threshold during one or more slots within OCC time window, the first apparatus 110 may perform (730) the OCC uplink transmission on the one or more slots. If the first apparatus 110 determines the estimated_open-loop TA parameter is larger than the threshold during at least one other slot within OCC time window, the first apparatus 110 may stop uplink transmission on the at least one other slot. This procedure may refer to a partial OCC uplink transmission.

[0134] In some other example embodiments, if a duration between the last GNSS based TA update and the last OCC symbol is less than a threshold, the first apparatus 110 may perform (730) the full OCC uplink transmission.

[0135] If the partial OCC uplink transmission is used, the first apparatus 110 may indicate (735) the partial UL OCC transmission to the second apparatus 120. If the second apparatus 120 knows the partially stopping of an OCC uplink transmission withinthe OCC time window, the second apparatus 120 may decode omitted OCC data on at least one slot within the OCC time window based on received OCC data on one or more other slots within the OCC time window.

[0136] In addition or optionally, the first apparatus 110 may send a GNSS based TA update timing to the second apparatus 120. The second apparatus 120 may schedule the OCC operation of the first apparatus that are not encountering a GNSS fix within the OCC time window based on the GNSS based TA update timing.

[0137] Based on the solution of the present disclosure, potential issues with GNSS update when OCC is applied may be addressed. As mentioned, if UE applies the GNSS fix during the OCC time window, time alignment with other UEs can be broken. Therefore, we should specify rules and requirement at UE side and coordination with NW to avoid timing misalignment, breaking orthogonality, and creating interference to all other UEs.

[0138] In some embodiments, the UE may not apply the GNSS fix in timing adjustment open loop or TAC during OCC.

[0139] In one embodiment, the UE may postpone the GNSS fix to the slot after OCC time window.

[0140] In another embodiment, the UE may perform the GNSS fix only if it occurs in the first slot of an OCC time window

[0141] In one embodiment, the gNB may mandate UE to disable GNSS fix.

[0142] In one embodiment, the UE may autonomously set back the GNSS fix after sending the OCC UL data.

[0143] In one embodiment, the gNB may indicate the UE to perform the GNSS fix after receiving the UE OCC PUSCH.

[0144] In some other embodiments, the UE may stop OCC application within the time window if GNSS fix occurs within the window.

[0145] In some other embodiments, the UE may stop OCC application (within the time window) and performs GNSS fix if the timing adjustment deriving from the GNSS fix is larger than a threshold. If timing adjustment becomes too large, orthogonality would be lost anyway.

[0146] If the UE stops the OCC transmission within the OCC time window (i.e. partial OCC operation), then the UE may indicate to NW the UL OCC dropping due to large TA, and NW may perform OCC data decoding accordingly (e.g., using (1) if XI in y2 is omitted by UE1, then X2 is deduced from y2 only, then NW may attempt to recover and decode XI using yl and X2).

[0147] In some other embodiments, the UE may transmit the configured / scheduled OCC UL repetitions if and only if the next GNSS update time instant known by UE (GNSS update rate is known) is after the last OCC repetition (or outside pre-defined OCC time window). Alternatively, the duration between the last TA update with GNSS and the last OCC symbol is less than a threshold (this threshold may depend on GNSS update periodicity of 1 second as example).

[0148] This proactive approach targets to avoid partial OCC transmission that may interfere with other UEs’ data due to large potential time misalignment and require to update OCC data decoding at gNB based on this partial transmission, otherwise OCC orthogonality between all UEs is impacted.

[0149] This threshold may be indicated by UE or controlled by NW, and UE may indicate OCC UL dropping to NW.

[0150] In some other embodiments, UEs GNSS update timings may be indicated to the gNB and the gNB schedules the OCC operations of the UEs that are not encountering GNSS fix within the OCC time window.

[0151] FIG. 8 shows a flowchart of an example method 800 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0152] At block 810, the first apparatus obtains a configuration of an OCC operation associated with a GNSS based TA update at the first apparatus.

[0153] At block 820, the first apparatus determines, based on the configuration, whether an uplink transmission is to be performed and / or an OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0154] In some example embodiments, the configuration indicates a full OCC transmission, a partial OCC transmission or an uplink transmission dropping is allowedunder the GNSS based TA update occurring within the OCC time window.

[0155] In some example embodiments, the method 800 further comprises: reporting a determination of the OCC transmission pattern to the second apparatus.

[0156] In some example embodiments, the method 800 further comprises: performing uplink transmission and / or repetition based on the determination of the OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0157] In some example embodiments, the method 800 further comprises: reporting, to the second apparatus, a capability for supporting a full OCC transmission or a partial OCC transmission.

[0158] In some example embodiments, the method 800 further comprises: obtaining an indication of at least one time frame associated with the GNSS based TA update.

[0159] In some example embodiments, the method 800 further comprises: obtaining an indication of a threshold associated with the GNSS-based TA update.

[0160] In some example embodiments, the method 800 further comprises: obtaining, from the second apparatus, an indication associated with enabling or disabling the GNSS based TA update.

[0161] In some example embodiments, the method 800 further comprises: determining a time instant for the GNSS-based TA update based on the indication.

[0162] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0163] FIG. 9 shows a flowchart of an example method 900 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the second apparatus 120 in FIG. 1.

[0164] At block 910, the second apparatus determines a configuration of an OCC operation associated with a GNSS based TA update at a first apparatus.

[0165] At block 920, the second apparatus transmits the configuration to the first apparatus.

[0166] In some example embodiments, the configuration indicates a full OCCtransmission, a partial OCC transmission or an uplink transmission dropping is allowed under the GNSS based TA update occurring within the OCC time window.

[0167] In some example embodiments, the method 900 further comprises: receiving an indication of determined OCC transmission pattern from the first apparatus; and receiving uplink transmission and / or repetition from the first apparatus based on the indication.

[0168] In some example embodiments, the method 900 further comprises: reporting, to the first apparatus, a capability for supporting a full OCC transmission or a partial OCC transmission.

[0169] In some example embodiments, the method 900 further comprises: transmitting, to the first apparatus, an indication of at least one time frame associated with the GNSS based TA update.

[0170] In some example embodiments, the method 900 further comprises: transmitting, to the first apparatus, an indication of a threshold associated with the GNSS-based TA update.

[0171] In some example embodiments, the method 900 further comprises: transmitting, to the first apparatus, an indication associated with enabling or disabling the GNSS based TA update.

[0172] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0173] FIG. 10 shows a flowchart of an example method 1000 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0174] At block 1010, the first apparatus obtains a configuration indicating that at least one TA parameter is not to be applied within an OCC time window.

[0175] At block 1020, the first apparatus performs the TA update with an open-loop type and / or a closed loop type based on the configuration.

[0176] In some example embodiments, the at least one TA parameter comprises at least one open-loop TA parameter and / or at least one closed loop TA parameter, and wherein the TA update with a closed-loop type refers to an update of a TA element based onfeedback received from a second apparatus, and the TA update with an open-loop type refers to an update of a TA controlled by the second apparatus and / or an estimated TA by the first apparatus.

[0177] In some example embodiments, the method 1000 further comprises: in accordance with a determination that the TA update occurs within the OCC time window, postponing based on the configuration, the TA update to a slot after the OCC time window.

[0178] In some example embodiments, the method 1000 further comprises: in accordance with a determination that the TA update occurs in the first slot of the OCC time window, performing the TA update.

[0179] In some example embodiments, the method 1000 further comprises: receiving, from the second apparatus, an indication for the first apparatus to perform the TA update based on a GNSS fix; and performing, based on the indication and the configuration, the TA update based on the GNSS fix after a completion of an OCC uplink transmission or before a beginning of the OCC uplink transmission.

[0180] In some example embodiments, the method 1000 further comprises: in accordance with a determination of an indication for disabling an GNSS fix within the OCC time window, setting back the GNSS fix after sending the OCC uplink transmission autonomously.

[0181] In some example embodiments, the method 1000 further comprises: in accordance with a determination of an indication for disabling an GNSS fix within the OCC time window, receiving an indication for resuming the GNSS fix after the OCC uplink transmission is received by the second apparatus.

[0182] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0183] FIG. 11 shows a flowchart of an example method 1100 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the second apparatus 120 in FIG. 1.

[0184] At block 1110, the second apparatus determines a configuration indicating that at least one TA parameter is not to be applied within an OCC time window.

[0185] At block 1120, the second apparatus transmits the configuration to the first apparatus.

[0186] In some example embodiments, the at least one TA parameter comprises at least one open-loop TA parameter and / or at least one closed loop TA parameter, and wherein the TA update with a closed-loop type refers to an update of a TA element based on feedback received from a second apparatus, and the TA update with an open-loop type refers to an update of a TA controlled by the second apparatus and / or an estimated TA by the first apparatus.

[0187] In some example embodiments, the method 1100 further comprises: transmitting, to the first apparatus, an indication for the first apparatus to perform the TA update based on a GNSS fix.

[0188] In some example embodiments, the method 1100 further comprises: transmitting, to the first apparatus, an indication for disabling an GNSS fix within the OCC time window; and in accordance with a determination that an OCC uplink data transmission is received, transmitting an indication for resuming the GNSS fix to the first apparatus.

[0189] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0190] FIG. 12 shows a flowchart of an example method 1200 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0191] At block 1210, the first apparatus receives a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window.

[0192] At block 1220, the first apparatus performs the GNSS based TA update based on the configuration.

[0193] In some example embodiments, the method 1200 further comprises: in accordance with a determination that the GNSS based TA update occurs within the OCC time window, drop the uplink data transmission.

[0194] In some example embodiments, the method 1200 further comprises: receiving,from the second apparatus, an indication of a threshold associated with the GNSS-based TA update; and in accordance with a determination that the GNSS based TA update occurs within the OCC time window and an estimated open-loop TA parameter is larger than the threshold, drop the uplink data transmission.

[0195] In some example embodiments, the method 1200 further comprises: in accordance with a determination that the GNSS based TA update does not occur within the OCC time window or an estimated open-loop TA parameter is not larger than the threshold, performing an OCC uplink transmission.

[0196] In some example embodiments, the method 1200 further comprises: receiving, from the second apparatus, an indication for dropping an uplink data transmission.

[0197] In some example embodiments, the method 1200 further comprises: in accordance with a determination of a dropping of the uplink data transmission, transmitting to the second apparatus, an indication of the uplink data transmission dropping.

[0198] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0199] FIG. 13 shows a flowchart of an example method 1300 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the second apparatus 120 in FIG. 1.

[0200] At block 1310, the second apparatus determines a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window.

[0201] At block 1320, the second apparatus transmits the configuration to the first apparatus.

[0202] In some example embodiments, the method 1300 further comprises: transmitting, to the first apparatus, an indication of a threshold associated with the GNSS-based TA update.

[0203] In some example embodiments, the method 1300 further comprises: transmitting, to the first apparatus, an indication for dropping an uplink data transmission.

[0204] In some example embodiments, the method 1300 further comprises: receiving,from the first apparatus, an indication of a dropping of the uplink data transmission.

[0205] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0206] FIG. 14 shows a flowchart of an example method 1400 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1400 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0207] At block 1410, the first apparatus receives a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window.

[0208] At block 1420, the first apparatus performs a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

[0209] In some example embodiments, the method 1400 further comprises: in accordance with a determination that the GNSS based TA update is after the last OCC transmission or before the first OCC uplink transmission, performing a full OCC uplink transmission within the OCC time window.

[0210] In some example embodiments, the method 1400 further comprises: determining whether a full OCC uplink transmission or a partial OCC uplink transmission is to be performed based on a comparison of an estimated open-loop TA parameter with a threshold.

[0211] In some example embodiments, the method 1400 further comprises: in accordance with a determination that an estimated open-loop TA parameter is larger than the threshold, stopping at least partial OCC uplink transmission within the OCC time window.

[0212] In some example embodiments, the method 1400 further comprises: in accordance with a determination that a duration between the last GNSS based TA update and the last OCC symbol is less than a threshold, performing the OCC uplink transmission.

[0213] In some example embodiments, the method 1400 further comprises: determining the threshold based on a periodicity of the GNSS based TA update.

[0214] In some example embodiments, the method 1400 further comprises: obtaining the threshold from the second apparatus.

[0215] In some example embodiments, the method 1400 further comprises: transmitting a GNSS based TA update timing to the second apparatus for a scheduling of the OCC operation based on the GNSS based TA update timing.

[0216] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0217] FIG. 15 shows a flowchart of an example method 1500 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1500 will be described from the perspective of the second apparatus 120 in FIG. 1.

[0218] At block 1510, the second apparatus determines a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window.

[0219] At block 1520, the second apparatus transmits the configuration to the first apparatus.

[0220] In some example embodiments, the method 1500 further comprises in accordance with a determination that an indication at least partially stopping of an OCC uplink transmission within the OCC time window is received from the first apparatus, decoding omitted OCC data on one or more slots within the OCC time window based on received OCC data on one or more other slots within the OCC time window.

[0221] In some example embodiments, the method 1500 further comprises: receiving a GNSS based TA update timing from the first apparatus; and scheduling, based on the GNSS based TA update timing, the OCC operation of the first apparatus that are not encountering a GNSS fix within the OCC time window.

[0222] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0223] In some example embodiments, a first apparatus capable of performing any of the method 800 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0224] In some example embodiments, the first apparatus comprises means for obtaining a configuration of an OCC operation associated with a GNSS based TA update at the first apparatus; and means for determining, based on the configuration, whether an uplink transmission is to be performed and / or an OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0225] In some example embodiments, the configuration indicates a full OCC transmission, a partial OCC transmission or an uplink transmission dropping is allowed under the GNSS based TA update occurring within the OCC time window.

[0226] In some example embodiments, the first apparatus further comprises: means for reporting a determination of the OCC transmission pattern to the second apparatus.

[0227] In some example embodiments, the first apparatus further comprises: means for performing uplink transmission and / or repetition based on the determination of the OCC transmission pattern under the GNSS based TA update occurring within an OCC time window.

[0228] In some example embodiments, the first apparatus further comprises: means for reporting, to the second apparatus, a capability for supporting a full OCC transmission or a partial OCC transmission.

[0229] In some example embodiments, the first apparatus further comprises: means for obtaining an indication of at least one time frame associated with the GNSS based TA update.

[0230] In some example embodiments, the first apparatus further comprises: means for obtaining an indication of a threshold associated with the GNSS-based TA update.

[0231] In some example embodiments, the first apparatus further comprises: means for obtaining, from the second apparatus, an indication associated with enabling or disabling the GNSS based TA update.

[0232] In some example embodiments, the first apparatus further comprises: means for determining a time instant for the GNSS-based TA update based on the indication.

[0233] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0234] In some example embodiments, a second apparatus capable of performing any ofthe method 900 (for example, the second apparatus 120 in FIG. 1) may comprise means for performing the respective operations of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.

[0235] In some example embodiments, the second apparatus comprises means for determining a configuration of an OCC operation associated with a GNSS based TA update at a first apparatus; and means for transmitting the configuration to the first apparatus.

[0236] In some example embodiments, the configuration indicates a full OCC transmission, a partial OCC transmission or an uplink transmission dropping is allowed under the GNSS based TA update occurring within the OCC time window.

[0237] In some example embodiments, the second apparatus further comprises: means for receiving an indication of determined OCC transmission pattern from the first apparatus; and means for receiving uplink transmission and / or repetition from the first apparatus based on the indication.

[0238] In some example embodiments, the second apparatus further comprises: means for reporting, to the first apparatus, a capability for supporting a full OCC transmission or a partial OCC transmission.

[0239] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication of at least one time frame associated with the GNSS based TA update.

[0240] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication of a threshold associated with the GNSS-based TA update.

[0241] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication associated with enabling or disabling the GNSS based TA update.

[0242] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0243] In some example embodiments, a first apparatus capable of performing any of the method 1000 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 1000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0244] In some example embodiments, the first apparatus comprises means for obtaining a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and means for performing the TA update with an open-loop type and / or a closed loop type based on the configuration.

[0245] In some example embodiments, the at least one TA parameter comprises at least one open-loop TA parameter and / or at least one closed loop TA parameter, and wherein the TA update with a closed-loop type refers to an update of a TA element based on feedback received from a second apparatus, and the TA update with an open-loop type refers to an update of a TA controlled by the second apparatus and / or an estimated TA by the first apparatus.

[0246] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that the TA update occurs within the OCC time window, postponing based on the configuration, the TA update to a slot after the OCC time window.

[0247] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that the TA update occurs in the first slot of the OCC time window, performing the TA update.

[0248] In some example embodiments, the first apparatus further comprises: means for receiving, from the second apparatus, an indication for the first apparatus to perform the TA update based on a GNSS fix; and means for performing, based on the indication and the configuration, the TA update based on the GNSS fix after a completion of an OCC uplink transmission or before a beginning of the OCC uplink transmission.

[0249] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination of an indication for disabling an GNSS fix within the OCC time window, setting back the GNSS fix after sending the OCC uplink transmissionautonomously.

[0250] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination of an indication for disabling an GNSS fix within the OCC time window, receiving an indication for resuming the GNSS fix after the OCC uplink transmission is received by the second apparatus.

[0251] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0252] In some example embodiments, a second apparatus capable of performing any of the method 1100 (for example, the second apparatus 120 in FIG. 1) may comprise means for performing the respective operations of the method 1100. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.

[0253] In some example embodiments, the second apparatus comprises means for determining a configuration indicating that at least one TA parameter is not to be applied within an OCC time window; and means for transmitting the configuration to the first apparatus.

[0254] In some example embodiments, the at least one TA parameter comprises at least one open-loop TA parameter and / or at least one closed loop TA parameter, and wherein the TA update with a closed-loop type refers to an update of a TA element based on feedback received from a second apparatus, and the TA update with an open-loop type refers to an update of a TA controlled by the second apparatus and / or an estimated TA by the first apparatus.

[0255] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication for the first apparatus to perform the TA update based on a GNSS fix.

[0256] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication for disabling an GNSS fix within the OCC time window; and means for in accordance with a determination that an OCC uplink data transmission is received, transmitting an indication for resuming the GNSS fix to the first apparatus.

[0257] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0258] In some example embodiments, a first apparatus capable of performing any of the method 1200 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0259] In some example embodiments, the first apparatus comprises means for receiving a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and means for performing the GNSS based TA update based on the configuration.

[0260] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that the GNSS based TA update occurs within the OCC time window, drop the uplink data transmission.

[0261] In some example embodiments, the first apparatus further comprises: means for receiving, from the second apparatus, an indication of a threshold associated with the GNSS-based TA update; and means for in accordance with a determination that the GNSS based TA update occurs within the OCC time window and an estimated open-loop TA parameter is larger than the threshold, drop the uplink data transmission.

[0262] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that the GNSS based TA update does not occur within the OCC time window or an estimated open-loop TA parameter is not larger than the threshold, performing an OCC uplink transmission.

[0263] In some example embodiments, the first apparatus further comprises: means for receiving, from the second apparatus, an indication for dropping an uplink data transmission.

[0264] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination of a dropping of the uplink data transmission, transmitting to the second apparatus, an indication of the uplink data transmission dropping.

[0265] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0266] In some example embodiments, a second apparatus capable of performing any of the method 1300 (for example, the second apparatus 120 in FIG. 1 may comprise means for performing the respective operations of the method 1300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.

[0267] In some example embodiments, the second apparatus comprises means for determining a configuration associated with a dropping of an uplink data transmission under a GNSS based TA update occurring within an OCC time window; and means for transmitting the configuration to the first apparatus.

[0268] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication of a threshold associated with the GNSS-based TA update.

[0269] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, an indication for dropping an uplink data transmission.

[0270] In some example embodiments, the second apparatus further comprises: means for receiving, from the first apparatus, an indication of a dropping of the uplink data transmission.

[0271] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0272] In some example embodiments, a first apparatus capable of performing any of the method 1400 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 1400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.

[0273] In some example embodiments, the first apparatus comprises means for receiving a configuration indicating that an OCC operation is allowed to be partially kept under aGNSS based TA update occurring within an OCC time window; and means for performing a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

[0274] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that the GNSS based TA update is after the last OCC transmission or before the first OCC uplink transmission, performing a full OCC uplink transmission within the OCC time window.

[0275] In some example embodiments, the first apparatus further comprises: means for determining whether a full OCC uplink transmission or a partial OCC uplink transmission is to be performed based on a comparison of an estimated open-loop TA parameter with a threshold.

[0276] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that an estimated open-loop TA parameter is larger than the threshold, stopping at least partial OCC uplink transmission within the OCC time window.

[0277] In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that a duration between the last GNSS based TA update and the last OCC symbol is less than a threshold, performing the OCC uplink transmission.

[0278] In some example embodiments, the first apparatus further comprises: means for determining the threshold based on a periodicity of the GNSS based TA update.

[0279] In some example embodiments, the first apparatus further comprises: means for obtaining the threshold from the second apparatus.

[0280] In some example embodiments, the first apparatus further comprises: means for transmitting a GNSS based TA update timing to the second apparatus for a scheduling of the OCC operation based on the GNSS based TA update timing.

[0281] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0282] In some example embodiments, a second apparatus capable of performing any of the method 1500 (for example, the second apparatus 120 in FIG. 1) may comprise meansfor performing the respective operations of the method 1500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.

[0283] In some example embodiments, the second apparatus comprises means for determining a configuration indicating that an OCC operation is allowed to be partially kept under a GNSS based TA update occurring within an OCC time window; and means for transmitting the configuration to the first apparatus.

[0284] In some example embodiments, the second apparatus further comprises: means for in accordance with a determination that an indication at least partially stopping of an OCC uplink transmission within the OCC time window is received from the first apparatus, decoding omitted OCC data on one or more slots within the OCC time window based on received OCC data on one or more other slots within the OCC time window.

[0285] In some example embodiments, the second apparatus further comprises: means for receiving a GNSS based TA update timing from the first apparatus; and means for scheduling, based on the GNSS based TA update timing, the OCC operation of the first apparatus that are not encountering a GNSS fix within the OCC time window.

[0286] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network device.

[0287] FIG. 16 is a simplified block diagram of a device 1600 that is suitable for implementing example embodiments of the present disclosure. The device 1600 may be provided to implement a communication device, for example, the first apparatus 110 or the second apparatus 120 as shown in FIG. 1. As shown, the device 1600 includes one or more processors 1610, one or more memories 1620 coupled to the processor 1610, and one or more communication modules 1640 coupled to the processor 1610.

[0288] The communication module 1640 is for bidirectional communications. The communication module 1640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1640 may include at least one antenna.

[0289] The processor 1610 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0290] The memory 1620 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1624, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 1622 and other volatile memories that will not last in the power-down duration.

[0291] A computer program 1630 includes computer executable instructions that are executed by the associated processor 1610. The instructions of the program 1630 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1630 may be stored in the memory, e.g., the ROM 1624. The processor 1610 may perform any suitable actions and processing by loading the program 1630 into the RAM 1622.

[0292] The example embodiments of the present disclosure may be implemented by means of the program 1630 so that the device 1600 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 15. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0293] In some example embodiments, the program 1630 may be tangibly contained in a computer readable medium which may be included in the device 1600 (such as in the memory 1620) or other storage devices that are accessible by the device 1600. The device 1600 may load the program 1630 from the computer readable medium to the RAM 1622 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitationof the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0294] FIG. 17 shows an example of the computer readable medium 1700 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1700 has the program 1630 stored thereon.

[0295] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0296] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non- transitory computer readable medium. The computer program product includes computerexecutable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0297] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller 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 inthe 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.

[0298] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0299] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but 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 computer 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.

[0300] Further, although 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, although 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. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.

[0301] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific featuresor acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

I / We claim:

1. A first apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive a configuration indicating an orthogonal cover code, OCC, operation is allowed to be partially kept under a global navigation satellite system, GNSS, based timing advance, TA, update occurring within an OCC time window; and perform a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

2. The first apparatus of claim 1, wherein the first apparatus is caused to: in accordance with a determination that the GNSS based TA update is after the last OCC transmission or before the first OCC uplink transmission, perform a full OCC uplink transmission within the OCC time window.

3. The first apparatus of claim 1, wherein the first apparatus is caused to: determine whether a full OCC uplink transmission or a partial OCC uplink transmission is to be performed based on a comparison of an estimated open-loop TA parameter with a threshold.

4. The first apparatus of claim 3, wherein the first apparatus is caused to: in accordance with a determination that an estimated_open-loop TA parameter is not larger than a threshold during one or more slots within OCC time window, perform the OCC uplink transmission on the one or more slots; and in accordance with a determination that the estimated_open-loop TA parameter is larger than the threshold during at least one other slot within OCC time window, stop uplink transmission on the at least one other slot.

5. The first apparatus of claim 1, wherein the first apparatus is caused to: in accordance with a determination that a duration between the last GNSS based TA update and the last OCC symbol is less than a threshold, perform the OCC uplink transmission.

446. The first apparatus of any of claims 3-5, wherein the first apparatus is caused to: determine the threshold based on a periodicity of the GNSS based TA update.

7. The first apparatus of any of claims 3-5, wherein the first apparatus is caused to: obtain the threshold from the second apparatus.

8. The first apparatus of claim 1, wherein the first apparatus is caused to: transmit a GNSS based TA update timing to the second apparatus for a scheduling of the OCC operation based on the GNSS based TA update timing.

9. The second apparatus of any of claims 1-7, wherein the first apparatus comprises a terminal device and the second apparatus comprises a network device.

10. A second apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: determine a configuration indicating an orthogonal cover code, OCC, operation is allowed to be partially kept under a global navigation satellite system, GNSS, based timing advance, TA, update occurring within an OCC time window; and transmit the configuration to the first apparatus.

11. The second apparatus of claim 10, wherein the second apparatus is caused to: in accordance with a determination that an indication of partially stopping of an OCC uplink transmission within the OCC time window is received from the first apparatus, decode omitted OCC data on at least one slot within the OCC time window based on received OCC data on one or more other slots within the OCC time window.

12. The second apparatus of claim 10, wherein the second apparatus is caused to: receive a GNSS based TA update timing from the first apparatus; and schedule, based on the GNSS based TA update timing, the OCC operation of the first apparatus that are not encountering a GNSS fix within the OCC time window.

13. The second apparatus of any of claims 10-12, wherein the first apparatus45comprises a terminal device and the second apparatus comprises a network device.

14. A method comprising: receiving a configuration indicating an orthogonal cover code, OCC, operation is allowed to be partially kept under a global navigation satellite system, GNSS, based timing advance, TA, update occurring within an OCC time window; and performing a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

15. A method comprising: determining a configuration indicating an orthogonal cover code, OCC, operation is allowed to be partially kept under a global navigation satellite system, GNSS, based timing advance, TA, update occurring within an OCC time window; and transmitting the configuration to the first apparatus.

16. A first apparatus comprising: means for receiving a configuration indicating an orthogonal cover code, OCC, operation is allowed to be partially kept under a global navigation satellite system, GNSS, based timing advance, TA, update occurring within an OCC time window; and means for performing a full OCC uplink transmission or a partial OCC uplink transmission based on the configuration.

17. A second apparatus comprising: means for determining a configuration indicating an orthogonal cover code, OCC, operation is allowed to be partially kept under a global navigation satellite system, GNSS, based timing advance, TA, update occurring within an OCC time window; and transmitting the configuration to the first apparatus.

18. A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 14 or the method of claim 15.

Images