Interrupt handling

Abstract

The embodiment of the invention relates to an interrupt processing device and method and a computer readable storage medium. In the method, a first device determines that a channel access procedure of a first transmission potentially causes an interruption to a second transmission. Further, the first device determines information regarding whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, availability for additional opportunities of the first transmission, the additional opportunity is different from a first opportunity at which the second transmission is performed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of channel access procedure. In this way, the interruption of the UL transmission by the SL transmission can be effectively reduced.

Description

Technical Field

[0001] The exemplary embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to methods, devices, apparatus, and computer-readable storage media for sidelink (SL) unlicensed spectrum wide area network (WAN) outage handling. Background Art

[0002] With the development of communication technology, SL unlicensed spectrum has been studied and various enhancements to SL transmission have been proposed. For example, mechanisms related to the channel access process associated with SL transmission (such as the Listen Before Talk (LBT) mechanism) are being studied to improve performance on the unlicensed spectrum. Summary of the invention

[0003] In a first aspect of the present disclosure, a first device is provided. The first device includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first device to at least: determine that a channel access process of a first transmission will potentially cause an interruption to a second transmission, the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device; and determine information about whether the interruption is allowed based on at least one of the following modes to avoid the interruption: a first priority of the first transmission and a second priority of the second transmission, availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity for the second transmission to be executed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of channel access process.

[0004] In a second aspect of the present disclosure, a second device is provided. The second device includes: at least one processor; and at least one memory storing instructions, which when executed by the at least one processor, cause the second device to at least: transmit information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access process of a first transmission to a second transmission, the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0005] In a third aspect of the present disclosure, a method is provided. The method includes: determining that a channel access procedure of a first transmission may potentially cause an interruption to a second transmission, the first transmission being a sidelink transmission to be initiated from a first device to a third device, and the second transmission being a transmission from the first device to the second device; and determining information about whether the interruption is allowed based on at least one of the following modes to avoid the interruption: a first priority of the first transmission and a second priority of the second transmission, availability of an additional opportunity for the first transmission, the additional opportunity being different from a first opportunity for the second transmission to be performed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of channel access procedure.

[0006] In a fourth aspect of the present disclosure, a method is provided. The method includes: transmitting information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access procedure of a first transmission to a second transmission, the first transmission is a sidelink transmission to be initiated from a first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0007] In a fifth aspect of the present disclosure, a first device is provided. The first device includes: a component for determining that a channel access process of a first transmission will potentially cause an interruption to a second transmission, the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device; and a component for determining information about whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity when the second transmission is performed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of channel access process.

[0008] In a sixth aspect of the present disclosure, a second device is provided. The second device includes: a component for transmitting information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access procedure of a first transmission to a second transmission, the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0009] In a seventh aspect of the present disclosure, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and the instructions are used to cause a device to at least execute the method according to the third aspect.

[0010] In an eighth aspect of the present disclosure, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and the instructions are used to cause a device to at least execute the method according to the fourth aspect.

[0011] It should be understood that the invention summary is not intended to identify the key features or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0013] Figure 1 An example communication environment is shown in which example embodiments of the present disclosure may be implemented;

[0014] Figure 2A A diagram showing a clear channel assessment (CCA) time slot in which energy detection occurs;

[0015] Figure 2B A diagram showing COT acquisition via Listen Before Talk (LBT) Type 1;

[0016] FIG. 2C to FIG. 2E Schematic diagrams of the LBT type 1 contention window countdown process are respectively shown.

[0017] Figure 3A A diagram showing SL transmission with LBT Type 2 is shown;

[0018] Figure 3B Another diagram showing SL transmission with LBT Type 2;

[0019] Figure 4 A signaling diagram illustrating a sidelink discontinuous reception (SL-DRX) configuration procedure;

[0020] Figure 5 A diagram showing a simplified representation of a SL-DRX cycle;

[0021] Figure 6 A diagram showing a detailed illustration of a SL-DRX cycle;

[0022] Figure 7 shows a diagram illustrating an outage to a WAN due to LBT operation;

[0023] Figure 8 shows a signaling diagram for interrupt handling according to some example embodiments of the present disclosure;

[0024] Fig. 9 A diagram illustrating an example processing of a WAN outage according to some example embodiments of the present disclosure;

[0025] Fig.10 A flowchart showing a first option for WAN outage handling according to some example embodiments of the present disclosure is shown;

[0026] Fig.11 A diagram illustrating another example processing of a WAN outage according to some example embodiments of the present disclosure;

[0027] Fig.12 A diagram illustrating yet another example processing of a WAN outage according to some example embodiments of the present disclosure;

[0028] Fig.13 A flowchart showing a second option for WAN outage handling according to some example embodiments of the present disclosure;

[0029] Fig.14 A diagram illustrating yet another example processing of a WAN outage according to some example embodiments of the present disclosure;

[0030] Fig.15 shows a signaling diagram for reconfiguring SL-DRX offset according to some example embodiments of the present disclosure;

[0031] Fig.16 A diagram illustrating yet another example processing of a WAN outage according to some example embodiments of the present disclosure;

[0032] Fig.17 A flowchart showing a fourth option for WAN outage handling according to some example embodiments of the present disclosure;

[0033] Fig.18 shows a signaling diagram for a mode selection process according to some example embodiments of the present disclosure;

[0034] Fig.19 A flowchart showing a method implemented at a first device according to some example embodiments of the present disclosure is shown;

[0035] Fig. 20 A flowchart showing a method implemented at a second device according to some example embodiments of the present disclosure is shown;

[0036] Fig.21 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0037] Fig. 22 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.

[0038] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0039] The principles of the present disclosure will now be described with reference to some example embodiments. It should 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 implying any limitation on the scope of the present disclosure. In addition to the embodiments described below, the embodiments described herein can be implemented in various ways.

[0040] 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 skill in the art to which this disclosure belongs.

[0041] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in other embodiments, whether or not explicitly described.

[0042] It should be understood that, although the terms "first", "second", etc. can be used before nouns in this article to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiment, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more listed terms.

[0043] As used herein, “at least one of: ,” “at least one of ,” and similar descriptions (wherein a list of two or more elements is connected by “and” or “or”) mean at least any one element, or at least any two or more elements, or at least all elements.

[0044] As used herein, unless explicitly stated, performing a step “in response to A” does not mean performing the step immediately after “A” occurs, but may include one or more intermediate steps.

[0045] The terms used herein are used only to describe specific embodiments and are not intended to limit the 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 should also be understood that when used herein, the terms "comprise", "comprising", "having", "having", "includes", and / or "including", when used herein, specify the presence of the described features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0046] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry); and (b) a combination of hardware circuitry and software such as (where applicable): (i) a combination of analog and / or digital hardware circuits and software / firmware; and (ii) any portion of a hardware processor (including a digital signal processor) with software, software and memory that work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (eg, firmware) to operate, but which may not be present when the software is not required for operation.

[0047] This definition of circuitry applies to all uses of the 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 only a hardware circuit, or a processor (or multiple processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers (e.g., if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0048] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network can be carried out according to any suitable generation communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), sixth generation (6G) communication protocol and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there are of course communication technologies and systems of future types that can implement the present disclosure. The scope of the present disclosure should not be limited to the above-mentioned system.

[0049] As used herein, the term "network device" refers to the following node in a communication network, via which a terminal device accesses the network and receives services from the node. A network device may refer to a base station (BS) or an access point (AP), such as a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a repeater, an integrated access and backhaul (IAB) node, a low-power node, such as a femto, a micro, a non-terrestrial network (NTN) or a non-terrestrial network device, such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous orbit (GEO) satellite, an aircraft network device, etc., depending on the terminology and technology applied. In some example embodiments, a radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at an IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves like a user equipment (UE) to a parent node, and a distributed unit (DU) portion of the IAB node that behaves like a base station to a next-hop IAB node.

[0050] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a 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 is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback facility, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a smart device, a wireless user terminal equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automatic processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) part of an IAB node (eg, a relay node).In the following description, the terms "terminal device", "communication device", "terminal", "user device", "user equipment" and "UE" may be used interchangeably.

[0051] As used herein, the term "resource", "transmission resource", "resource block", "physical resource block" (PRB), "uplink resource" or "downlink resource" may refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as a resource in the time domain, a resource in the frequency domain, a resource in the spatial domain, a resource in the code domain, or any other resource supporting communication. In the following, unless explicitly stated, resources in the frequency domain and the time domain will be used as examples of transmission resources for describing some example embodiments of the present disclosure. It should be noted that the example embodiments of the present disclosure are also applicable to other resources in other domains.

[0052] Figure 1 An example communication environment 100 is shown in which an example embodiment of the present disclosure may be implemented. In the communication environment 100, a first device 110, a second device 120, and a third device 130 are shown. The second device 120 may include a network device and have a certain coverage. This coverage may be referred to as a service area or cell 102. One or more terminal devices may be located within or outside the cell 102. As shown, the first device 110 and the third device 130 are located within the cell 102 and may communicate with the second device 120. In other words, the first device 110 and the third device 130 are served by the second device 120.

[0053] In some embodiments, the first device 110 and the third device 130 are both terminal devices. Different terminal devices can establish communication connections with each other. For example, the first device 110 and the third device 130 can establish communication connections with each other. Communication between terminal devices can be referred to as side link (SL) communication.

[0054] During SL communication, the first device 110 may communicate data and / or control information with the third device 130. In SL communication, a terminal device that performs transmission is referred to as a transmitting (TX) device (or transmitter), and a terminal device that receives transmission is referred to as a receiving (RX) device (or receiver).

[0055] For SL communication on unlicensed spectrum, the terminal device that initiates channel occupation time (COT) may be referred to as a COT initiator or a COT initiating device, and the terminal device that responds may be referred to as a COT responder or a COT responding device. In some example embodiments of the present disclosure, the first device 110 may be a COT initiator or a COT initiating device, and the third device 130 may be a COT responder or a COT responding device.

[0056] It should be understood that Figure 1 The number of devices and their connections shown in the example are for illustrative purposes only and do not imply any limitation. Environment 100 may include any suitable number of devices suitable for implementing embodiments of the present disclosure. Although not shown, it should be understood that one or more additional devices may be located in cell 102, and one or more additional cells may be deployed in environment 100.

[0057] In the following, for the purpose of illustration, some example embodiments are described with the first device 110 operating as a COT responder and the third device 130 operating as a COT initiator. It should be understood that the above is assumed only for the purpose of discussion and does not imply any limitation. In some embodiments, the first device 110 can operate as a COT initiator and the third device 130 can operate as a COT responder.

[0058] The communication in the communication environment 100 may be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), sixth generation (6G), etc., wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc., and / or any other protocol currently known or developed in the future. In addition, the communication may use any suitable wireless communication technology, including 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 access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or developed in the future.

[0059] In some unlicensed bands (e.g., sub-7 GHz or other frequencies for unlicensed bands), coexistence of New Radio (NR) with other systems (e.g., IEEE802.11) is ensured via a listen-before-talk (LBT) channel access mechanism. A user equipment (UE) that desires to perform a sidelink (SL) transmission first needs to successfully complete an LBT check before being able to initiate a SL transmission. LBT may also be referred to as a clear channel assessment (CCA) or a channel access procedure.

[0060] In order for a UE to pass the LBT check, it must observe that the channel is available for multiple consecutive CCA slots. In sub-7 GHz, the duration of these slots is 9 microseconds (μs), such as Figure 1 If the measured power (i.e., the energy collected during the CCA slot) is below the energy detection threshold (EDT), the UE considers the channel to be available in the CCA slot. The maximum value of EDT may depend on regulatory limits, transmit power, operating frequency band, and geographic region.

[0061] Figure 2A 2 shows a diagram of a CCA time slot 200A in which energy detection occurs. Figure 2A As shown, CCA time slot 200A has a duration T sl =9 μs, where sensing is performed within 4 μs. That is, energy detection occurs during 4 μs.

[0062] When a UE initiates communication (i.e., the UE acts as an initiating device), then the UE must obtain "permission" to access the channel for a certain period of time (represented in the rules as the Channel Occupancy Time (COT) 240) by applying an "extended" LBT procedure, where the channel must be considered idle for the entire duration of the Contention Window (CW) 230. This "extended" LBT procedure is generally referred to as LBT Type 1 as known in TS 37.213. This is in Figure 2B The process is shown in 200B.

[0063] The duration of both COT and CW depends on the channel access priority class (CAPC) associated with the UE's traffic, as shown in Table 1. Control plane traffic (such as the physical sidelink control channel (PSCCH)) is transmitted with p=1, while user plane traffic has p>1. In Table 1, we depict the LBT Type 1 details for the Uu uplink (UL) case, but we note that in principle the LBT Type 1 parameters for the downlink (DL) case can also be adopted in SL.

[0064] Table 1 is based on TS 37.213 "Table 4.2.1-1: Channel Access Priority Classes (CAPC) for UL". The contention window length in the CCA slot associated with each CAPC has a minimum value (CW min,p ) and maximum (CW max,p ). The duration of COT is determined by T ulm cot,p Given. Table 1

[0065] exist Figures 2C to 2E An example of the behavior during the contention window countdown process is depicted in . It should be noted that if during the countdown process, the LBT check fails in any CCA slot, the countdown will stop and resume only if the channel is considered idle (i.e., the LBT check succeeded) during the delay time.

[0066] Figure 2C A diagram of a process 200C of LBT Type 1 contention window countdown is shown, wherein neither the delay time nor the countdown is interrupted (ie, the channel is not detected as busy during the sensing slot). Figure 2D A diagram of a process 200D for LBT Type 1 contention window countdown is shown, wherein the delay time is interrupted (ie, the channel is detected as busy during the delay time sensing slot). Figure 2E A diagram of a process 200E for LBT Type 1 contention window countdown is shown, wherein the contention window countdown is interrupted (ie, the channel is detected as busy during the countdown sensing time slot). FIG. 2C to FIG. 2E In the example shown, T d is the delay time, T sl refers to the CCA slot duration, and N refers to the number of CCA slots that need to be considered idle before the contention window countdown is completed.

[0067] The UE initiating the transmission (the initiating device) acquires a COT with a duration associated with the corresponding CAPC upon successful completion of LBT Type 1 and transmission. The acquired COT is valid even in the case where the initiating device suspends its transmission, although if the initiating device wants to perform a new transmission (within the COT), it still needs to perform a "simplified" LBT procedure. This "simplified" LBT procedure is generally referred to as LBT Type 2 (TS 37.213), with the following variations:

[0068] 1) Type 2A (25 μs LBT)—for SL transmissions within the COT acquired by the initiator (in the case where the interval between two SL transmissions is ≥ 25 μs, and for SL transmissions following another SL transmission). Figure 3A A diagram 300A shows SL transmission via LBT Type 2, and Figure 3B Another diagram 300B showing SL transmission via LBT Type 2. Figure 3A A time interval 301 between a first transmission 310 and a second transmission 320 initiated by a COT initiating device is shown. Figure 3B A time interval 302 is shown between a first transmission 310 initiated by a COT initiating device and a second transmission 320 initiated by a COT responding device. Figure 3A and Figure 3B Type 2A is illustrated, where both time intervals 301 and 302 are greater than or equal to 25 μs.

[0069] 2) Type 2B (16μs LBT) - for SL transmission within the COT acquired by the initiator (can only be used for SL transmission following another SL with an interval exactly equal to 16μs). Figure 3A and Figure 3B Type 2B is illustrated, in which time intervals 301 and 302 are both equal to 16 μs.

[0070] 3) Type 2C (no LBT) - can only be used for a SL transmission following another SL, where the interval is < 16 μs and the allowed duration of the SL transmission is ≤ 584 μs). Figure 3A and Figure 3B Type 2C is shown, where time intervals 301 and 302 are both less than 16 μs.

[0071] A COT initiating device (also referred to as an "initiating device") may share its acquired COT with its intended receiver, i.e., a COT responding device (also referred to as a "responding device"). To this end, the initiating device shall inform (e.g., via control signaling) the responding device of the duration of the COT. The responding device then uses this information to decide which type of LBT it should apply when performing a transmission where the intended receiver is the initiating device. If the responding device transmission falls outside the COT, the responding device will have to acquire a new COT using LBT Type 1 with an appropriate CAPC.

[0072] The sidelink discontinuous reception (SL DRX) configuration may be based on a recommendation from the RX UE to the TX UE for which the RX UE may provide assistance information (desired SL DRX configuration) to the TX UE. In case Mode 1 is used, the TX UE may report the assistance information received from the RX UE to the gNB. The RX UE may accept or reject the SL DRX configuration. A default SL DRX configuration for multicast / broadcast may be used for initial setup (e.g., via a DCR (Direct Communication Request) message). The SL DRX MACCE (SL DRX command from the TX UE to the RX UE) may be used to indicate that the UE may go to sleep. Figure 4 A signaling diagram 400 for the sidelink DRX configuration procedure is shown. At 410, the SL RX UE 401 transmits a UEAssistanceInformationSideLink message including the desired SL DRX configuration to the SL TX UE 402. At 420, the SL TX UE 402 transmits an RRCReconfigurationSidelink message with the SL DRX configuration to the SL RX UE 401. At 430, the SL RX UE 401 transmits an RRCReconfigurationCompleteSidelink message indicating acceptance or rejection of the SL DRX configuration to the SL TX UE 402.

[0073] The SL DRX MAC CE, which is a SL DRX command from the TX UE to the RX UE, may be configured by the RRC with SL DRX function, which controls the SCI of the UE (ie, first stage SCI and second stage SCI) to monitor unicast, groupcast, and broadcast activities. Figure 5 Diagram 500 is shown showing a simplified representation of a SL-DRX cycle.

[0074] The RRC controls the sidelink DRX operation by configuring at least one of the following parameters:

[0075] 1) sl-drx-onDurationTimer / sl-DRX-GC-BC-OnDurationTimer: duration at the start of the SL DRX cycle;

[0076] 2) sl-drx-SlotOffset: the delay before starting sl-drx-onDurationTimer / sl-DRX-GC-BC-onDurationTimer;

[0077] 3) sl-drx-InactivityTimer / sl-DRX-GC-InactivityTimer (except SL broadcast communication): duration after reception of the first time slot of SCI (i.e., first phase SCI and second phase SCI), where SCI indicates a new SL transmission for the MAC entity;

[0078] 4) sl-drx-RetransmissionTimer / sl-DRX-GC-RetransmissionTimer (for each sidelink process except the SL broadcast process): maximum duration until a SL retransmission is received;

[0079] 5)sl-drx-StartOffset: the time slot at which the SL DRX cycle starts;

[0080] 6) sl-drx-Cycle / sl-DRX-GC-BC-Cycle: sidelink DRX cycle;

[0081] 7) sl-drx-HARQ-RTT-Timer / sl-DRX-GC-HARQ-RTT-Timer (for each sidelink process except the SL broadcast process): the minimum duration that the MAC entity expects before SL HARQ retransmission.

[0082] Figure 6Diagram 600 showing a detailed illustration of the SL-DRX cycle. A UE transmitting SL-SCH data determines the SL DRX active time based on the SL DRX timers (e.g., sl-drx-onDurationTimer, sl-drx-InactivityTimer, sl-drx-RetransmissionTimer) that are running or will be running in the future at the UE receiving SL-SCH data. The UE can select resources for the initial transmission of multicast within the time when the sl-drx-onDurationTimer or sl-drx-InactivityTimer of the destination is running. The UE can send a SL DRX command MAC CE to the receiving UE for unicast, and when to transmit the SL DRX command MAC CE depends on the UE implementation.

[0083] If sl-DRX-ConfigUC-ToAddModList is contained in sl-ConfigDedicatedNR within RRCReconfiguration, for each sl-DestinationIndex contained in the received sl-DRX-ConfigUC-ToAddModList (which is part of the currently stored NR sidelink DRX configuration), reconfigure the entry according to the value for that sl-DestinationIndex received from the stored NR sidelink DRX configuration information. If it is not part of the currently stored NR sidelink DRX configuration, add a new entry for that sl-DestinationIndex to the stored NR sidelink DRX configuration.

[0084] When the configured SL-DRX cycle is less than 640ms, interruptions on the PCell / serving cell due to sensing during the SL DRX off duration are allowed with up to 1% probability of lost acknowledgement (ACK) or negative acknowledgement (NACK), and when the configured SL-DRX cycle is 640ms or longer, a 0.625% probability of lost ACK / NACK is allowed. When multiple SL-DRX cycles are configured, the shortest SL-DRX cycle applies. Each interruption should not exceed X time slots as defined in Table 2, which shows the interruption length X during the transition between active and inactive during SL-DRX. Table 2

[0085] Considering that the transmission in the unlicensed carrier is subject to LBT success, it also needs to be guaranteed by the TX UE before initiating any transmission during the SL-DRX on period of the RX UE. When the SL-U TX UE is performing concurrent SL-U communication along with Uu communication, when LBT is performed at the SL-U TX UE over the PC5 carrier at the UL timeslot opportunity intended for Uu ACK / NACK transmission, there will be a potential disruption to the WAN, as it may not be expected that the UE can transmit in Uu and sense PC5 at the same time. Figure 7 A diagram illustrating WAN outage due to LBT operation during SL-DRX off duration at SL-U TX UE is shown 700. If the above problem is not addressed, it may cause WAN outage every time LBT is performed on the PC5 carrier during SL-DRX off duration at SL-U TX UE.

[0086] Several solutions are proposed in this article to at least solve the above problems. The proposed solutions involve one or more of the following options:

[0087] 1) First option: Consider the priority of SL operation over Uu operation,

[0088] 2) Second option: Considering the candidate timing awareness of SL transmission,

[0089] 3) Third option: Introduce SL-DRX RX UE on-duration offset, or

[0090] 4) Fourth option: Consider LBT type and / or CAPC.

[0091] Additionally, a mode selection procedure is proposed to determine how the SL-U TX UE is configured with one of the above options.By virtue of the above features, the proposed solution may advantageously ensure minimal disruption to the WAN during the sensing performed at the SL-DRX off duration.

[0092] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0093] Figure 8 A signaling diagram 800 for interrupt handling according to some example embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The signaling diagram 800 is discussed, for example, by using the first device 110 , the second device 120 , and the third device 130 .

[0094] In About Figure 8In the discussed embodiments, the first device 110 may be a terminal device, the second device 120 may be a network device, and the third device 130 may be another terminal device. The first device 110 may initiate a sidelink (SL) transmission to the third device 130 (hereinafter also referred to as a "first transmission"), and the first device 110 may also perform an uplink (UL) transmission to the second device 120 (hereinafter also referred to as a "second transmission").

[0095] The channel access process for SL transmission may potentially cause interruption to other transmissions (e.g., UL transmission to the second device 120). In other words, it is the channel access process for SL transmission, such as the Listen Before Talk (LBT) process, that causes interruption to UL transmission.

[0096] In signaling diagram 800, the first device 110 first determines (820) that a channel access procedure for a first transmission may potentially cause disruption to a second transmission.

[0097] Then, the first device 110 determines (825) information on whether the interruption is allowed to avoid the interruption. The determination of the information on whether the interruption is allowed is based on at least one mode determined from among the plurality of modes.

[0098] These modes may be preconfigured or predetermined. For example, the mode may be configured by the second device 120. Figure 8 As shown, the second device 120 transmits (810) information about the mode for determining whether the interruption is allowed. After receiving (815) information about the above mode from the second device 120, the first device 110 can determine (825) information about whether the interruption is allowed based on the received information about the mode.

[0099] The pattern can be related to various factors, such as, but not limited to, a first priority of the first transmission and a second priority of the second transmission, the availability of additional opportunities for the first transmission, which are different from the first opportunities when the second transmission is performed, offset information configured for the first transmission, the channel access priority category of the first transmission, the type of channel access procedure, and the like.

[0100] Specifically, during the determination (825), in some example embodiments, the first device 110 may compare the first priority of the first transmission with the second priority of the second transmission. If the first priority is higher than the second priority, the first device 110 may determine that the interruption is allowed. Otherwise, if the first priority is lower than the second priority, the first device 110 may determine that the interruption is not allowed.

[0101] Alternatively, in some example embodiments, during the determination (825), the first device 110 may determine whether an additional opportunity for the first transmission is available. That is, the first device 110 may attempt to avoid using the first opportunity for performing UL transmission by finding another suitable opportunity for SL transmission so as to avoid any interruption caused to the UL transmission. If the additional opportunity is available, the first device 110 may determine that the first transmission is allowed to be performed at the additional opportunity. Otherwise, if the additional opportunity is not available, the first device 110 may determine that the interruption is not allowed.

[0102] As another alternative, in some example embodiments, during the determination (825), the first device 110 may transmit a configuration indicating offset information to the third device 130. The offset information may include information about an offset to be used for SL transmission. For example, the offset information may include, but is not limited to, an offset of SL discontinuous reception (DRX), a duration of SL DRX, a period of a cycle of DRX (i.e., a period of a DRX cycle), and the like. Then, the first device 110 may perform a first transmission with the third device 130 based on the offset information.

[0103] As yet another alternative, in some example embodiments, during the determination (825), the first device 110 may compare the value of the channel access priority category of the first transmission to a threshold value. If the value of the channel access priority category is below the threshold value, the first device 110 may determine that the first transmission is allowed to be performed. On the other hand, if the value of the channel access priority category is greater than the threshold value, the first device 110 may determine that the interruption is not allowed.

[0104] Alternatively, in some example embodiments, the above determination (825) may refer to the type of channel access procedure of the first transmission (e.g., SL transmission). As discussed above, the type of channel access procedure may include, for example, different LBT types, such as LBT Type 1, LBT Type 2A, LBT Type 2B, LBT Type 2C, and the like. LBT Type 1 applies an "extended" LBT procedure in which the channel must be considered idle for the entire duration of the contention window (CW). LBT Type 2A (25μs LBT) is for SL transmissions within the COT acquired by the initiating device (in the case where the interval between two SL transmissions is ≥25μs, and for SL transmissions following another SL transmission). LBT Type 2B (16μs LBT) is for SL transmissions within the COT acquired by the initiating device (can only be used for SL transmissions that follow another SL with an interval exactly equal to 16μs). Type 2C (no LBT) can only be used for SL transmissions that follow another SL, where the interval is <16μs and the allowed duration of the SL transmission is ≤584μs.

[0105] It can be seen that if the first device 110 performs LBT type 2A or LBT type 2B, it may cause an interruption to the second transmission. On the contrary, if the first device 110 performs LBT type 1, it can skip LBT and not cause an interruption. In the case of LBT type 2C, since LBT is not required, there should not be any interruption.

[0106] Therefore, in the above exemplary embodiment, for example, if the type of the channel access procedure is listen before talk (LBT) type 1 or LBT type 2C, the first device 110 may determine that the interruption is allowed. If the type of the channel access procedure is LBT type 2A or LBT type 2B, the first device 110 may determine that the interruption is not allowed.

[0107] In view of the above, the first device 110 may determine whether the interruption is allowed. In some example embodiments, alternatively, the first device 110 may determine whether the first transmission is allowed to be performed. This determination may be made based on one or more preconfigured or predetermined modes.

[0108] In some example embodiments, the first device 110 may determine whether the interruption is allowed by selecting at least one mode from preconfigured or predetermined modes. The first device 110 may then transmit information about the selected at least one mode to the second device 120. After receiving the information about the selected at least one mode, the second device 120 will have knowledge about the manner in which the interruption is allowed or not allowed.

[0109] In some cases, there may be some changes or needs to reconfigure the mode. In some example embodiments, the first device 110 may transmit a request to the second device 120 for reconfiguring the mode. Upon receiving the request from the first device 110, the second device 120 may transmit information about the reconfigured mode to the first device 110. The first device 110 may then determine whether to allow further interruptions or later interruptions based on the reconfigured mode received from the second device 120. Likewise, such a determination may be made by selecting an appropriate mode from the reconfigured modes. In some implementations, the first device 110 may transmit information about the mode selected from the reconfigured modes to the second device 120 so that the second device 120 will have knowledge of the mode used by the first device 110.

[0110] In this way, the interruption of SL transmission to UL transmission can be effectively reduced.

[0111] The following will refer to Figures 9 to 18 By using the four different options described above in more detail Figure 8 The solution presented in . First option

[0112] As briefly mentioned above, in the first option, the priority of SL operation and the priority of Uu operation are considered. For example, the priority of SL operation can be compared with the priority of Uu operation, and then the option with higher priority is performed. Figures 9 and 10 This first option is described in more detail.

[0113] Fig. 9 A diagram 900 is shown illustrating an example processing of a WAN outage according to some example embodiments of the present disclosure. Fig. 9 In the example, the SL-U TX UE can be Figure 1 An example implementation of the first device 110 in FIG. 1 and the SL-U RX UE may be Figure 1 An example implementation of the third device 130 in .

[0114] like Fig. 9 As shown, based on the relative priorities of SL and Uu transmissions, the SL-U TX UE can determine whether it needs to introduce an outage to the WAN. For example, if the associated priority (P Uu =1) is higher than the associated priority (P SL =2), and assuming that a lower value indicates a higher priority, the SL-U TX UE abandons SL operation. In other words, the SL-U TX UE does not need to abandon Uu transmission, and therefore should not be allowed to interrupt the WAN. Otherwise, if SL transmission has a higher priority than Uu transmission, interruption to the WAN may occur.

[0115] In some example embodiments, the priority associated with a Uu transmission and / or a SL transmission may be determined as follows:

[0116] 1) First solution: The network (NW) can configure the priority based on the service profile. For example, if the service is delay tolerant, the UE will be associated with a low priority. Otherwise, if the UE is expected to transmit delay sensitive data, a high priority is associated with the UE. Such a configuration will be delivered from the NW to the UE.

[0117] 2) Second solution: The UE is allowed to determine the priority of Uu transmission and SL transmission.

[0118] It should be noted that the first solution can also be applied together with the second solution. To this end, when the first solution is executed, the NW will transmit an indication allowing the UE to calculate and set a new priority for Uu / SL transmission. The UE can then override all priorities or any part of the priorities determined using the first solution.

[0119] It should be understood that the above description and / or examples are described for description purposes only. The priority associated with Uu transmission and / or SL transmission may also be determined based on any other appropriate scheme. The scope of the present disclosure is not limited in this respect.

[0120] Now turn to Fig.10 , which shows a flowchart 1000 of a first option for WAN outage handling according to some example embodiments of the present disclosure. Fig. 9 SL-U TX UE in and / or in Figure 1 The first device 110 executes Fig.10 For discussion purposes, flowchart 1000 will be described from the perspective of a SL-U TX UE.

[0121] At block 1010, the SL-U TX UE has data to transmit in the SL, so a channel access procedure needs to be initiated. At block 1020, the SL-U TX UE determines whether the channel access procedure will potentially cause an outage to the WAN. In some example embodiments, the SL-U TX UE may determine an outage to the WAN in the event that sensing of the channel access procedure (also referred to as LBT) overlaps with Uu communications.

[0122] If it is determined that the channel access process does not potentially cause disruption to the WAN, the decision process proceeds to block 1040, where disruption to the WAN (if any) is allowed while performing LBT in the SL, and sensing information is collected to form a candidate resource set. At 1050, the SL-U TX UE starts SL transmission.

[0123] If it is determined that the channel access procedure may potentially cause disruption to the WAN, the decision process proceeds to block 1030. The SL-U TX UE determines whether the priority associated with the SL transmission is greater than the priority associated with the Uu transmission. If the priority associated with the SL transmission is not greater than the priority associated with the Uu transmission, the decision process proceeds to block 1060, where the SL-UTX UE avoids any disruption to the WAN and performs a random backoff. By way of example and not limitation, the SL-U TX UE may wait for a random duration before performing the sensing procedure.

[0124] If it is determined that the priority associated with SL transmission is greater than the priority associated with Uu transmission, the decision process proceeds to block 1040, where the SL-U TX UE performs LBT in SL and allows interruption to the WAN (if any). At block 1040, sensing information is collected and a candidate resource set is formed, and at 1050, the SL-U TX UE starts SL transmission.

[0125] In view of the above description, the proposed solution may advantageously minimize the disruption to the WAN during the sensing performed at the SL-DRX off duration. Second option

[0126] As briefly mentioned above, in the second option, the candidate opportunity awareness of SL transmission is considered. Figures 11 to 13 This second option is described in more detail.

[0127] In some example embodiments, an associated SL transmission may be configured with multiple transmission opportunities. In such a case, the SL-U TX UE may consider not performing LBT operation during the candidate opportunity when Uu transmission is scheduled, and thus disruption to the WAN may be avoided. For example, when one PSCCH transmission or physical sidelink shared channel (PSSCH) transmission has N associated candidate physical sidelink feedback channel (PSFCH) or sidelink synchronization signal block (S-SSB) opportunities via (pre) configuration, PSFCH transmission may be avoided in the candidate opportunity where there is a potential overlap with the Uu transmission opportunity.

[0128] Fig.11 Diagram 1100 shows another example processing of a WAN outage according to some example embodiments of the present disclosure. Fig.11 In the example, the SL-U TX UE can be Figure 1 An example implementation of the first device 110 in FIG. 1 and the SL-U RX UE may be Figure 1 An example implementation of the third device 130 in FIG. Fig.11 In the example scenario shown in , WAN outage is avoided by canceling / delaying PSFCH in case of potential overlap with Uu Tx.

[0129] Additionally, if multiple consecutive time slots (MCSt) are acquired for transmission of TB, the Tx UE may consider avoiding those candidate time slots where WAN outage is expected. Alternatively, the UE may consider performing LBT on empty Uu time slots where no Uu transmission / reception is scheduled.

[0130] Fig.12 A diagram 1200 shows another example processing of a WAN outage according to some example embodiments of the present disclosure. Fig.12 In the example, the SL-U TX UE can be Figure 1 An example implementation of the first device 110 in FIG. 1 and the SL-U RX UE may be Figure 1 An example implementation of the third device 130 in FIG. Fig.12 In the example scenario shown, LBT operation is performed in empty Uu time slots when multiple consecutive time slots are acquired.

[0131] Now turn to Fig.13 , which shows a flowchart 1300 for a second option for WAN outage handling according to some example embodiments of the present disclosure. Figure 11 to Figure 12 SL-U TX UE and / or Figure 1 The first device 110 executes Fig.13 For discussion purposes, flowchart 1300 will be described from the perspective of a SL-U TX UE.

[0132] At block 1310, the SL-U TX UE has data to transmit in the SL, so a channel access procedure needs to be initiated. At block 1320, the SL-U TX UE determines whether the channel access procedure will potentially cause an outage to the WAN. In some example embodiments, the SL-U TX UE may determine an outage to the WAN in the event that sensing of the channel access procedure (also referred to as LBT) overlaps with Uu communications.

[0133] If it is determined that the channel access process does not potentially cause disruption to the WAN, the decision process proceeds to block 1340, where disruption to the WAN (if any) is allowed while performing LBT in the SL, and sensing information is collected to form a candidate resource set. At 1350, the SL-U TX UE starts SL transmission.

[0134] If it is determined that the channel access procedure will potentially cause disruption to the WAN, the decision process proceeds to block 1330. The SL-U TX UE determines whether there are additional opportunities for associated SL transmissions. If not, the decision process proceeds to block 1360, where the SL-UTX UE avoids any disruption to the WAN and performs a random backoff. As an example and not limitation, the SL-U TX UE may wait for a random duration before performing the sensing procedure.

[0135] If it is determined that there are additional opportunities for associated SL transmissions, the decision process proceeds to block 1340 where sensing information is collected and a candidate resource set is formed, and the SL-U TX UE starts SL transmission at 1350. In this way, minimal disruption to the WAN during the sensing performed at the SL-DRX off duration can be advantageously ensured. Third option

[0136] As briefly mentioned above, in the third option, an on-duration offset of the SL-DRX RX UE is introduced. Figure 14 to Figure 15 This third option is described in more detail.

[0137] In some example embodiments, if frequent outages to the WAN are observed such that the outages tend to exceed defined requirements, the SL-U TX UE may configure or reconfigure at least one of the following:

[0138] 1)SL-DRX offset sl-drx-SlotOffset, sl-drx-StartOffset,

[0139] 2) the duration of SL-DRX or the period of the SL-DRX cycle of the SL-U RX UE for each sl-DestinationIndex in the received sl-DRX-ConfigUC-ToAddModList, or

[0140] 3) sl-DRX-Config-GC-BC included in sl-ConfigDedicatedNR in RRCReconfiguration.

[0141] It should be understood that the above examples are described for illustrative purposes only. The SL-U TX UE may also configure or reconfigure any other suitable parameters. The scope of the present disclosure is not limited in this respect.

[0142] Fig.14 A diagram 1400 shows another example processing of a WAN outage according to some example embodiments of the present disclosure. Fig.14 In the example, the SL-U TX UE can be Figure 1 An example implementation of the first device 110 in FIG. 1 and the SL-U RX UE may be Figure 1 An example implementation of the third device 130 in FIG. Fig.14 As shown, the offset of the SL-U RX UE is adjusted.

[0143] Now turn to Fig.15 , which shows a signaling diagram 1500 for reconfiguring SL-DRX offset according to some example embodiments of the present disclosure. Fig.15 In the example, SL-U TX UE 1502 may be Figure 1 110 in an example embodiment, and the SL-U RX UE 1501 may be Figure 1 An example embodiment of the third device 130 in.

[0144] At 1510, the SL-U RX UE 1501 transmits a UEAssistanceinformationSidelink message including the desired SL DRX configuration to the SL-U TX UE 1502. At 1515, the SL-U TX UE 1502 transmits an RRCReconfigurationSidelink message with the SL DRX configuration to the SL-U RX UE 1501. At 1520, the SL-U RX UE 1501 transmits an RRCReconfigurationCompleteSidelink message indicating acceptance or rejection of the SL DRX configuration to the SL-UTX UE 1502. At 1525, the SL-U TX UE 1502 determines that an outage to the WAN is observed or an outage to the WAN is frequently observed due to the LBT. Then, at 1530, the SL-U TX UE 1502 transmits an RRCReconfigurationSidelink message for SL DRX reconfiguration to the SL-U RX UE 1501. At 1535, the SL-U RX UE 1501 applies the reconfigured SL-DRX offset. At 1540, the SL-U RX UE 1501 transmits a RRCReconfigurationCompleteSidelink message to the SL-U TX UE 1502 indicating acceptance or rejection of the SL DRX reconfiguration.

[0145] In view of the above, the proposed solution can advantageously reduce the disruption to the WAN during the sensing performed at the SL-DRX off duration. Fourth option

[0146] As briefly mentioned above, in the fourth option, LBT type and / or CAPC are considered. Figure 16 to Figure 17 This fourth option is described in more detail.

[0147] In some example embodiments, the SL-U TX UE may determine information about whether to interrupt WAN transmission based on the CAPC value of the associated SL transmission. For example, if the CAPC(p) value is high, the UE may abandon LBT operation in the SL and not cause an interruption to the WAN. Otherwise, if the CAPC is low, the UE may perform LBT and potentially cause an interruption. It is assumed that a low CAPC means a high priority level and a high CAPC means a low priority level.

[0148] Fig.16 A diagram 1600 shows another example processing of a WAN outage according to some example embodiments of the present disclosure. Fig.16In the example, the SL-U TX UE can be Figure 1 An example implementation of the first device 110 in FIG. 1 and the SL-U RX UE may be Figure 1 An example implementation of the third device 130 in FIG. Fig.16 In the example scenario shown, in the case where SL-U CAPC is equal to 3 (which indicates that the SL transmission has a low priority), no LBT operation is performed. In the case where SL-U CAPC is equal to 1 (which indicates that the SL transmission is in a high priority category), the SL-U TX UE performs LBT and potentially causes an interruption.

[0149] Now turn to Fig.17 , which shows a flowchart 1700 for a fourth option for WAN outage handling according to some example embodiments of the present disclosure. Fig.16 SL-U TX UE and / or Figure 1 The first device 110 executes Fig.17 For discussion purposes, flowchart 1700 will be described from the perspective of a SL-U TX UE.

[0150] At block 1710, the SL-U TX UE has data to transmit in the SL, so a channel access procedure needs to be initiated. At block 1720, the SL-U TX UE determines whether the channel access procedure will potentially cause an outage to the WAN. In some example embodiments, the SL-U TX UE may determine an outage to the WAN in the event that sensing of the channel access procedure (also referred to as LBT) overlaps with Uu communications.

[0151] If it is determined that the channel access process does not potentially cause disruption to the WAN, the decision process proceeds to block 1740, where disruption to the WAN (if any) is allowed while performing LBT in the SL, and sensing information is collected to form a candidate resource set. At block 1750, the SL-U TX UE starts SL transmission.

[0152] If it is determined that the channel access procedure may potentially cause disruption to the WAN, the decision process proceeds to block 1730. The SL-U TX UE determines whether the SL transmission has a high priority. By way of example and not limitation, the SL-U TX UE may determine whether the CAPC value of the associated SL transmission is low to decide whether the SL transmission has a high priority. If the SL transmission does not have a high priority, the decision process proceeds to block 1760, where the SL-U TX UE avoids any disruption to the WAN and performs a random backoff. By way of example and not limitation, the SL-UTX UE may wait for a random duration before performing a sensing procedure.

[0153] If it is determined that the SL transmission has a high priority (eg, the CAPC value of the associated SL transmission is low), the decision process proceeds to block 1740 where sensing information is collected and a candidate resource set is formed. At block 1750, the SL-U TX UE starts SL transmission.

[0154] In some alternative or additional example embodiments, the SL-U TX UE may determine information about whether to interrupt WAN transmission based on the type of the channel access procedure. If the type of the channel access procedure is type 2A or type 2B, the SL-UTX UE may interrupt the WAN. If the type of the channel access procedure is type 1 with a higher probability of failure, the SL-U TX UE may skip LBT and not cause an interruption. In the case where the type of the channel access procedure is type 2C, LBT is not required. Therefore, there should not be any interruption to the WAN.

[0155] In view of the above description, the proposed solution may advantageously minimize the disruption to the WAN during the sensing performed at the SL-DRX off duration. Mode Selection

[0156] In the above description, four different options for WAN outage handling are presented and discussed in detail. In this section, a mode selection process is presented and described. The SL-U TX UE may be configured with one of the above options based on the mode selection process. Fig.18 Describe the mode selection process in more detail.

[0157] Fig.18 A signaling diagram 1800 for a mode selection process according to some example embodiments of the present disclosure is shown. Fig.18 In the example, SL-U TX UE 1802 may be Figure 1 In an example implementation of the first device 110, the gNB 1803 may be Figure 1 An example implementation of the second device 120 in FIG. 1 , and the SL-U RX UE 1801 may be Figure 1 An example implementation of the third device 130 in .

[0158] At 1810, the gNB 1803 provides information about a set of configurable modes to the SL-U TX UE 1802. The set of configurable modes may include at least one of the above options. After receiving the information, at 1815, the SL-U TX UE 1802 selects a configurable mode from the set of configurable modes. At 1820, the SL-U TX UE 1802 reports the selected mode to the gNB 1803. At 1825, the SL-U TX UE 1802 runs the operation of the selected mode. That is, the SL-U TX UE 1802 performs the behavior defined in the mode. At 1830, the SL-U TX UE 1802 may perform LBT transmission to the SL-URX UE 1801. If the mode needs to be reselected due to any changes in business, priority, etc., at 1835, the SL-U TX UE 1802 may request reconfiguration of the mode selection. Then, similar to the previous steps, at 1840, the gNB 1803 may transmit information about a set of configurable modes to the SL-U TX UE 1802. After selecting a mode from the set of configurable modes, at 1845, the SL-U TX UE 1802 reports the selected mode to the gNB 1803.

[0159] In view of the above, the mode selection process may advantageously facilitate configuring or reconfiguring the SL-U TX UE utilizing the proposed solution for WAN outage handling.

[0160] Fig.19 A flowchart of an example method 1900 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purpose of discussion, Figure 1 The perspective description method 1900 of the first device 110 in FIG.

[0161] At block 1910, the first device 110 determines that a channel access procedure for a first transmission may potentially cause an interruption to a second transmission. The first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0162] At box 1920, the first device 110 determines information about whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, the availability of an additional opportunity for the first transmission, which is different from the first opportunity when the second transmission is performed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of channel access procedure.

[0163] In some example embodiments, method 1900 further includes: comparing a first priority of the first transmission with a second priority of the second transmission; determining that an interrupt is allowed if it is determined that the first priority is higher than the second priority; and determining that an interrupt is not allowed if it is determined that the first priority is lower than the second priority.

[0164] In some example embodiments, method 1900 further includes: determining whether an additional opportunity for the first transmission is available; if it is determined that the additional opportunity is available, determining that the first transmission is allowed to be performed at the additional opportunity; and if it is determined that the additional opportunity is not available, determining that interruption is not allowed.

[0165] In some example embodiments, method 1900 further includes: transmitting a configuration indicating offset information to a third device, the offset information including at least one of: an offset of sidelink discontinuous reception, a duration of sidelink discontinuous reception, or a period of a cycle of sidelink discontinuous reception; and performing a first transmission with the third device based on the offset information.

[0166] In some example embodiments, method 1900 further includes: comparing the value of the channel access priority category of the first transmission with a threshold; if it is determined that the value of the channel access priority category is lower than the threshold, determining that the first transmission is allowed to execute; and if it is determined that the value of the channel access priority category is greater than the threshold, determining that interruption is not allowed.

[0167] In some example embodiments, method 1900 further includes: if it is determined that the type of the channel access process is listen-before-talk LBT type 1 or LBT type 2C, determining that interruption is allowed; and if it is determined that the type of the channel access process is LBT type 2A or LBT type 2B, determining that interruption is not allowed.

[0168] In some example embodiments, the method 1900 further includes receiving information about the mode from the second device.

[0169] In some example embodiments, the method 1900 further includes transmitting information about at least one mode selected from the modes to the second device.

[0170] In some example embodiments, method 1900 further includes: transmitting a request to reconfigure the mode to the second device; receiving information about the reconfigured mode from the second device; and transmitting information about the mode selected from the reconfigured mode to the second device.

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

[0172] Fig. 20FIG. 2 is a flowchart of an example method 2000 implemented at a second device according to some example embodiments of the present disclosure. Figure 1 The method 2000 is described from the perspective of the second device 120 in FIG.

[0173] At block 2010, the second device 120 transmits information about a mode for determining whether an interruption is allowed. The interruption is potentially caused by a channel access procedure of a first transmission to a second transmission. The first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0174] In some example embodiments, the method 2000 further includes receiving information about at least one mode from the first device, the at least one mode being selected from the modes for determining whether the first transmission is allowed to be performed.

[0175] In some example embodiments, the method 2000 further includes: receiving a request for reconfiguring the mode from the first device; transmitting information about the reconfigured mode to the first device; and receiving information about the mode selected from the reconfigured mode from the first device.

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

[0177] In some example embodiments, a first device (eg, Figure 1 The first device 110 in the method 1900 may include components for performing the corresponding operations of the method 1900. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module. The first device may be implemented as Figure 1 The first device 110 or is included in Figure 1 In the first device 110.

[0178] In some example embodiments, the first device includes: a component for determining that a channel access procedure for a first transmission will potentially cause an interruption to a second transmission, the first transmission being a sidelink transmission to be initiated from the first device to a third device, and the second transmission being a transmission from the first device to the second device; and a component for determining information about whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity for the second transmission to be performed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of channel access procedure.

[0179] In some example embodiments, the first device further includes: a component for comparing a first priority of the first transmission with a second priority of the second transmission; a component for determining that an interrupt is allowed if it is determined that the first priority is higher than the second priority; and a component for determining that an interrupt is not allowed if it is determined that the first priority is lower than the second priority.

[0180] In some example embodiments, the first device further includes: a component for determining whether an additional opportunity for the first transmission is available; a component for determining that the first transmission is allowed to be performed at the additional opportunity if it is determined that the additional opportunity is available; and a component for determining that interruption is not allowed if it is determined that the additional opportunity is not available.

[0181] In some example embodiments, the first device further includes: a component for transmitting a configuration indicating offset information to a third device, the offset information including at least one of: an offset of sidelink discontinuous reception, a duration of sidelink discontinuous reception, or a period of a cycle of sidelink discontinuous reception; and a component for performing a first transmission with the third device based on the offset information.

[0182] In some example embodiments, the first device also includes: a component for comparing the value of the channel access priority category of the first transmission with a threshold; a component for determining that the first transmission is allowed to be executed if it is determined that the value of the channel access priority category is lower than the threshold; and a component for determining that interruption is not allowed if it is determined that the value of the channel access priority category is greater than the threshold.

[0183] In some example embodiments, the first device also includes: a component for determining that interruption is allowed if it is determined that the type of the channel access process is listen-before-talk LBT type 1 or LBT type 2C; and a component for determining that interruption is not allowed if it is determined that the type of the channel access process is LBT type 2A or LBT type 2B.

[0184] In some example embodiments, the first device further comprises means for receiving information about the mode from the second device.

[0185] In some example embodiments, the first device further comprises means for transmitting information about at least one mode selected from the modes to the second device.

[0186] In some example embodiments, the first device further includes: a component for transmitting a request for reconfiguring the mode to the second device; a component for receiving information about the reconfigured mode from the second device; and a component for transmitting information about the mode selected from the reconfigured modes to the second device.

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

[0188] In some example embodiments, the first apparatus further comprises means or the first apparatus 110 for performing other operations in some example embodiments of the method 1900. In some example embodiments, the means comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the first apparatus.

[0189] In some example embodiments, a second device (eg, Figure 1 The second device 120 in the method 2000 may include components for performing the corresponding operations of the method 2000. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module. The second device may be implemented as Figure 1 The second device 120 in or included in Figure 1 In the second device 120.

[0190] In some example embodiments, the second device includes components for transmitting information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access procedure of a first transmission to the second transmission, the first transmission being a sidelink transmission to be initiated from the first device to a third device, and the second transmission being a transmission from the first device to the second device.

[0191] In some example embodiments, the second device further includes means for receiving information about at least one mode from the first device, the at least one mode being selected from the modes for determining whether the first transmission is allowed to be performed.

[0192] In some example embodiments, the second device further includes: a component for receiving a request for reconfiguring the mode from the first device; a component for transmitting information about the reconfigured mode to the first device; and a component for receiving information about a mode selected from the reconfigured mode from the first device.

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

[0194] In some example embodiments, the second apparatus further comprises means or the second apparatus 120 for performing other operations in some example embodiments of the method 2000. In some example embodiments, the means comprises at least one processor and at least one memory storing instructions which, when executed by the at least one processor, cause execution of the first apparatus.

[0195] Fig.21 2 is a simplified block diagram of a device 2100 suitable for implementing an example embodiment of the present disclosure. The device 2100 may be provided to implement a communication device, such as Figure 1 2100 . As shown, the device 2100 includes one or more processors 2110 , one or more memories 2120 coupled to the processors 2110 , and one or more communication modules 2140 coupled to the processors 2110 .

[0196] The communication module 2140 is used for two-way communication. The communication module 2140 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface necessary for communicating with other network elements. In some example embodiments, the communication module 2140 may include at least one antenna.

[0197] Processor 2110 may be of any type suitable for the local technology network and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 2100 may have multiple processors, such as application specific integrated circuit chips, which are time-slaved to a clock synchronized with a main processor.

[0198] The memory 2120 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 2124, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 2122 and other volatile memories that will not persist during a power outage.

[0199] The computer program 2130 includes computer executable instructions executed by the associated processor 2110. The instructions of the program 2130 may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program 2130 may be stored in a memory, such as ROM 2124. The processor 2110 may perform any suitable actions and processes by loading the program 2130 into the RAM 2122.

[0200] The exemplary embodiments of the present disclosure may be implemented by the program 2130 so that the device 2100 may execute the reference Figures 8 to 20 Any process of the present disclosure discussed. Example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0201] In some example embodiments, the program 2130 may be tangibly contained in a computer-readable medium, which may be included in the device 2100 (such as in the memory 2120) or in other storage devices accessible by the device 2100. The device 2100 may load the program 2130 from the computer-readable medium to the RAM 2122 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein is a limitation of the medium itself (i.e., tangible, not a signal), not a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0202] Fig. 22 An example of a computer readable medium 2200 is shown, which may be in the form of a CD, DVD, or other optical storage disk. The computer readable medium 2200 has a program 2130 stored thereon.

[0203] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated 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 the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or illustrated and described using some other graphical representations, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0204] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer-readable medium (such as, non-volatile computer-readable medium). The computer program product includes computer executable instructions, such as those computer executable instructions executed in a device on a target physical or virtual processor included in a program module, to perform any method as described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of the program modules can be combined or split between program modules as needed. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.

[0205] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller in a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0206] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0207] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0208] In addition, although operations are depicted in a particular order, this should not be construed as requiring such operations to be performed in the particular order shown or in a sequential order, or performing all illustrated operations, to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specified in a particular embodiment. Unless expressly stated, certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, unless expressly stated, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0209] Although the present disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

[0210] In addition, various implementations of the present disclosure may be described with reference to the following clauses, and features thereof may be combined in any reasonable manner.

[0211] Item 1. A first device, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first device to at least: determine that a channel access process for a first transmission will potentially cause an interruption to a second transmission, wherein the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device; and determine information about whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity when the second transmission is executed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of the channel access process.

[0212] Clause 2. A first device according to clause 1, wherein the first device is configured to: compare the first priority of the first transmission with the second priority of the second transmission; determine that the interrupt is allowed if it is determined that the first priority is higher than the second priority; and determine that the interrupt is not allowed if it is determined that the first priority is lower than the second priority.

[0213] Clause 3. A first device according to clause 1, wherein the first device is configured to: determine whether the additional opportunity for the first transmission is available; if it is determined that the additional opportunity is available, determine that the first transmission is allowed to be performed at the additional opportunity; and if it is determined that the additional opportunity is not available, determine that the interruption is not allowed.

[0214] Clause 4. A first device according to Clause 1, wherein the first device is configured to: transmit a configuration indicating the offset information to the third device, the offset information comprising at least one of: an offset of sidelink discontinuous reception, a duration of the sidelink discontinuous reception, or a period of a cycle of the sidelink discontinuous reception; and based on the offset information, perform the first transmission with the third device.

[0215] Clause 5. A first device according to Clause 1, wherein the first device is configured to: compare the value of the channel access priority category of the first transmission with a threshold; if it is determined that the value of the channel access priority category is lower than the threshold, determine that the first transmission is allowed to be executed; and if it is determined that the value of the channel access priority category is greater than the threshold, determine that the interruption is not allowed.

[0216] Clause 6. A first device according to Clause 1, wherein the first device is configured to: determine that the interruption is allowed if it is determined that the type of the channel access process is listen-before-talk (LBT) type 1 or LBT type 2C; and determine that the interruption is not allowed if it is determined that the type of the channel access process is LBT type 2A or LBT type 2B.

[0217] Clause 7. A first device as described in any of clauses 1 to 6, wherein the first device is caused to: receive information about the mode from the second device.

[0218] Clause 8. The first device of any of clauses 1 to 7, wherein the first device is caused to transmit information about the at least one mode selected from the modes to the second device.

[0219] Clause 9. A first device according to any one of clauses 1 to 8, wherein the first device is caused to: transmit a request to reconfigure the mode to the second device; receive information about the reconfigured mode from the second device; and transmit information about a mode selected from the reconfigured mode to the second device.

[0220] Clause 10. The first apparatus of any of clauses 1 to 9, wherein the first apparatus comprises a terminal device, the second apparatus comprises a network device, and the third apparatus comprises another terminal device.

[0221] Item 11. A second device, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the second device to at least: transmit information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access process of a first transmission to a second transmission, the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0222] Clause 12. The second apparatus of clause 11, wherein the second apparatus is caused to: receive information about at least one mode from the first apparatus, the at least one mode being selected from the modes for determining whether the first transmission is allowed to be performed.

[0223] Clause 13. A second device according to clause 11 or 12, wherein the second device is caused to: receive a request for reconfiguring the mode from the first device; transmit information about the reconfigured mode to the first device; and receive information about a mode selected from the reconfigured mode from the first device.

[0224] Clause 14. The second apparatus of any of clauses 11 to 13, wherein the first apparatus comprises a terminal device, the second apparatus comprises a network device, and the third apparatus comprises another terminal device.

[0225] Clause 15. A method comprising: determining that a channel access process for a first transmission may potentially cause an interruption to a second transmission, wherein the first transmission is a sidelink transmission to be initiated from a first device to a third device, and the second transmission is a transmission from the first device to the second device; and determining information about whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity at which the second transmission is executed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of the channel access process.

[0226] Clause 16. A method comprising: transmitting information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access process of a first transmission to a second transmission, the first transmission is a sidelink transmission to be initiated from a first device to a third device, and the second transmission is a transmission from the first device to a second device.

[0227] Item 17. A first device, comprising: a component for determining that a channel access process for a first transmission will potentially cause an interruption to a second transmission, wherein the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device; and a component for determining information about whether the interruption is allowed to avoid the interruption based on at least one of the following modes: a first priority of the first transmission and a second priority of the second transmission, the availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity when the second transmission is performed, offset information configured for the first transmission, a channel access priority category of the first transmission, or a type of the channel access process.

[0228] Item 18. A second device, comprising: a component for transmitting information about a mode for determining whether an interruption is allowed, wherein the interruption is potentially caused by a channel access process of a first transmission to a second transmission, the first transmission is a sidelink transmission to be initiated from the first device to a third device, and the second transmission is a transmission from the first device to the second device.

[0229] Clause 19. A computer-readable medium comprising instructions stored thereon for causing an apparatus to at least perform the method according to any one of clauses 15 to 16.

Claims

1. A first device for communication, comprising: at least one processor; as well as at least one memory storing instructions, which when executed by the at least one processor cause the first device to at least: determining that a channel access procedure for a first transmission may potentially cause an interruption to a second transmission, the first transmission being a sidelink transmission to be initiated from the first device to a third device, and the second transmission being a transmission from the first device to a second device; as well as The information on whether the interruption is allowed is determined based on at least one of the following modes to avoid the interruption: a first priority level for the first transmission and a second priority level for the second transmission, the availability of an additional opportunity for the first transmission, the additional opportunity being different from the first opportunity at which the second transmission is performed, offset information configured for the first transmission, the channel access priority class of the first transmission, or The type of the channel access procedure.

2. The first device according to claim 1, wherein the first device is configured to: comparing the first priority of the first transmission with the second priority of the second transmission; If it is determined that the first priority level is higher than the second priority level, determining that the interrupt is allowed; and If it is determined that the first priority level is lower than the second priority level, it is determined that the interruption is not allowed.

3. The first device according to claim 1, wherein the first device is configured to: determining whether the additional opportunity for the first transmission is available; If it is determined that the additional opportunity is available, determining that the first transmission is allowed to be performed at the additional opportunity; as well as If it is determined that the additional opportunity is not available, it is determined that the interruption is not allowed.

4. The first device according to claim 1, wherein the first device is configured to: Transmitting a configuration indicating the offset information to the third device, the offset information comprising at least one of: an offset of a sidelink discontinuous reception, a duration of the sidelink discontinuous reception, or a period of a cycle of the sidelink discontinuous reception; and Based on the offset information, the first transmission with the third device is performed.

5. The first device according to claim 1, wherein the first device is caused to: comparing a value of the channel access priority class of the first transmission to a threshold; If it is determined that the value of the channel access priority category is lower than the threshold, determining that the first transmission is allowed to be performed; as well as If it is determined that the value of the channel access priority category is greater than the threshold, it is determined that the interruption is not allowed.

6. The first device according to claim 1, wherein the first device is caused to: If it is determined that the type of the channel access procedure is listen-before-talk (LBT) type 1 or LBT type 2C, determining that the interruption is allowed; and If it is determined that the type of the channel access procedure is LBT Type 2A or LBT Type 2B, it is determined that the interruption is not allowed.

7. The first device according to any one of claims 1 to 6, wherein the first device is configured to: Information about the mode is received from the second device.

8. The first device according to any one of claims 1 to 6, wherein the first device is configured to: Information about the at least one mode selected from the modes is transmitted to the second device.

9. The first device according to any one of claims 1 to 6, wherein the first device is configured to: transmitting to the second device a request to reconfigure the mode; receiving information about the reconfigured mode from the second device; as well as Information about a mode selected from the reconfigured modes is transmitted to the second device.

10. The first apparatus according to any one of claims 1 to 6, wherein the first apparatus comprises a terminal device, the second apparatus comprises a network device, and the third apparatus comprises another terminal device.

Images