Channel Access Indication for Spectrum Reuse, Power Saving, and Coexistence

Abstract

To provide methods and devices for using a channel access indicator in new radio unlicensed (NR-U).SOLUTION: In a method in a communication system, UE1 accesses a channel before UE2 and transmits its channel access indicator (CAI). UE2 starts sensing the channel with clear channel assessment (CCA) with a prescribed threshold as part of category 4 listen-before-talk (CAT 4 LBT). As UE2 continues to sense the channel during its random backoff, UE2 detects higher energy. UE2 listens for and detects a CAI, and recognizes it as an intra-cell transmission. UE2 changes the LBT threshold and continues extended sensing with the higher threshold. If the energy is within this threshold, then UE2 transmits its scheduled physical uplink shared channel (PUSCH) which is in frequency division multiplex (FDM) resources with the PUSCH of UE1.SELECTED DRAWING: Figure 4

Description

[Background technology]

[0001] LTE License Assisted Access

[0002] A carrier with at least one Scell operating in unlicensed spectrum Aggregation is a method of Licensed-Assisted Access (LA) A) is called the Serving Center A) configured for the UE. The set of cells is a frame, also called an LAA SCell, in the unlicensed spectrum. Always contains at least one SCell that operates according to system structure type 3. Therefore, the LAA SCell functions as a normal SCell (Jonathan Ling, David Lopez-Perez, Mohammad R. Khawer, “Practical LTE and Wi-Fi Coexistence T. (See "Techniques beyond LBT," IEEE Communications Magazine, Oct 2017).

[0003] The LAA eNB and UE listen before transmitting on the LAA SCell. Apply Listen-Before-Talk (LBT). LBT is a method for The printer first detects the media and only when it detects that the media is idle This is a method of transmitting signals, also known as Clear Channel Assessment (CCA). When LBT is applied, the transmitter listens / senses the channel and Determine whether the channel is free or busy. If the channel is determined to be free, , The transmitter can perform transmission, but otherwise does not perform transmission. LAA When the eNB uses the channel access signal of other technologies for the purpose of LAA channel access the LAA eNB needs to continue to meet the requirements of the LAA maximum energy detection threshold There is a need to do so.

[0004] There are various LBT techniques, but what the Third Generation Partnership Project (3GPP) recommends is called LBT-Load Based Equipment Category 4. This is a standardized method that adds a random access protocol similar to Wi-Fi (Wireless Fidelity) to ensure not only LTE / WiFi coexistence but also LTE / LTE coexistence. In Release 14 (Rel-14), several channel access procedures that can be performed by the eNB and UE have been introduced for both downlink (DL) and uplink (UL) transmissions. The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0). eration Partnership Project: 3GPP) is recommended, which is called LBT-Load Based Equipment Category 4. This is a standardized method that adds a random access protocol similar to Wi-Fi (Wireless Fidelity) to ensure not only LTE / WiFi coexistence but also LTE / LTE coexistence. In Release 14 (Rel-14), several channel access procedures that can be performed by the eNB and UE have been introduced for both downlink (DL) and uplink (UL) transmissions. The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0). i (Wireless Fidelity) to ensure not only LTE / WiFi coexistence but also LTE / LTE coexistence. In Release 14 (Rel-14), several channel access procedures that can be performed by the eNB and UE have been introduced for both downlink (DL) and uplink (UL) transmissions. The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0). i (Wireless Fidelity) and adds a random access protocol similar to Wi-Fi (Wireless Fidelity) to ensure not only LTE / WiFi coexistence but also LTE / LTE coexistence. In Release 14 (Rel-14), several channel access procedures that can be performed by the eNB and UE have been introduced for both downlink (DL) and uplink (UL) transmissions. The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0). and ensures a standardized method for LTE / LTE coexistence as well. In Release 14 (Rel-14), several channel access procedures that can be performed by the eNB and UE have been introduced for both downlink (DL) and uplink (UL) transmissions. The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0). In Release 14 (Rel-14), for both downlink (DL) and uplink (Uplink: UL) transmissions, several channel access procedures that can be performed by the eNB and UE have been introduced. The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0). The main channel access procedure is described in Section 15 of 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0 (3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0) )

[0005] LTE frame structure type 3

[0006] Frame structure type 3 is only applicable to the secondary battery operation of LAA with a normal cyclic prefix. Each radio frame has a length of T ​f = 307200·T S = 10 is in ms and has a length of T slоt = 15360·T S = 0.5 ms and numbers from 0 to 19 and consists of 20 slots numbered from 0 to 19. A subframe is defined as two consecutive slots and subframe i consists of slot i and 2i + 1.

[0007] Ten subframes within a radio frame are available for downlink or uplink transmission to be used. Downlink transmission occupies one or more consecutive subframes, starts at any location within a subframe and is either fully occupied or ends in the last subframe following one of the DwPTS periods defined in 3GPP TS 36 213, Physical layer procedures (Release 15), V15.0.0, Table 4.2-1 Uplink transmission occupies one or more consecutive subframes. ends at the last subframe following one of the DwPTS periods defined in 3GPP TS 36.213, Physical layer procedures (Release 15), V15.0.0, Table 4.2-1

[0008] NextGen Network Requirements

[0009] 3GPP TR 38.913, Study on Scenarios and Requirements for Next Generation Access Technologies (Release 14), V14.3.0 (3GPP TR 38.913, Study on Scenarios and Requirements for Next Generation Access Technologies (Release 14), V14 .3.0) defines scenarios and requirements for next generation access technologies. Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (U ltra-Reliable Low-Latency Communications: URLLC), and massive Machine Type Communications (mMTC) are considered as the main use cases for 5G networks ltra-Reliable Low-Latency Communications (URLLC), and massive Machine Type Communications (mMTC) are considered as the main use cases for 5G networks Ultra-Reliable and Low-Latency Communications: URLLC), and Key Performance Indicators (KPIs) for Massive Machine Type Communication (mMTC) are summarized in Table 1. Key Performance Indicator (KPI) are summarized in Table 1.

[0010] [Table 1-1] [Table 1-2]

[0011] Receiver-Assisted Unlicensed Operations

[0012] To adjust spectrum access between technologies in a decentralized and simple way, the transmitter must first detect the energy over the intended transmission band. This energy detection (ED) mechanism notifies the transmitter of ongoing transmissions by other nodes and helps in the decision of whether to transmit or not. However, this scheme, also called listen-before-talk (LBT), is simple but not always effective in all situations. For example, when the information is encoded such that it is received below the background noise level, or when the nodes are far apart and the signal at the receiver is weak. Thus, a node wishing to transmit can detect that the channel is not occupied by the received energy being below a certain ED threshold, but it may still interfere with nearby nodes that are receiving. This energy detection (ED) mechanism notifies the transmitter of ongoing transmissions by other nodes and helps in the decision of whether to transmit or not. However, this scheme, also called listen-before-talk (LBT), is simple but not always effective in all situations. For example, when the information is encoded such that it is received below the background noise level, or when the nodes are far apart and the signal at the receiver is weak. Thus, a node wishing to transmit can detect that the channel is not occupied by the received energy being below a certain ED threshold, but it may still interfere with nearby nodes that are receiving. For example, when the information is encoded such that it is received below the background noise level, or when the nodes are far apart and the signal at the receiver is weak. Thus, a node wishing to transmit can detect that the channel is not occupied by the received energy being below a certain ED threshold, but it may still interfere with nearby nodes that are receiving. However, this scheme, also called listen-before-talk (LBT), is simple but not always effective in all situations. This energy detection (ED) mechanism notifies the transmitter of ongoing transmissions by other nodes and helps in the decision of whether to transmit or not. Thus, a node wishing to transmit can detect that the channel is not occupied by the received energy being below a certain ED threshold, but it may still interfere with nearby nodes that are receiving.

[0013] Nevertheless, LBT is the first step towards coexistence and is mandated in the regulations of unlicensed bands in many countries. Since false detections occur due to noise, the ED threshold cannot be lowered significantly. Therefore, additional information for effective wireless media access between and within technologies is required.

[0014] The RTS / CTS mechanism in WiFi

[0015] The 802.11 Media Access Control (MAC) protocol assists the ED mechanism with a Virtual Carrier Sense (VCS) mechanism. As a result, the 802.11 packet header is received and decoded at the lowest power level because it uses the most robust modulation and coding. The Network Allocation Vector (NAV), i.e., the time schedule at each station (STA) when the channel is idle or occupied, is updated based on the content of such a header or control packet indicating the period during which the channel will be used. For example, the Request to Send / Clear to Send (RTS / CTS) mechanism reserves the channel by causing the NAV to be updated by all nodes that receive the RTS around the transmitter and the CTS around the receiver. However, due to the capture effect, where a stronger overlapping packet is captured over a weaker one, an unfairness occurs where the stronger nodes do not encounter collisions and the weaker nodes concede, so there are still problems even with VCS. ​

[0016] Virtual carrier sensing is a logical abstraction that restricts the need for physical carrier sensing at the air interface to save power. The MAC layer frame header contains a duration field that specifies the transmission time required for that frame, during which the medium becomes busy. Each station listening on the wireless medium reads that duration field and sets a Network Allocation Vector (NAV), which is an indicator of the period during which the station needs to defer access to the medium. The NAV can be considered a counter that counts down linearly to zero. When the counter reaches zero, the VSC indicates that the medium is idle; otherwise, it indicates that the medium is busy.

[0017] Unlicensed in LTE

[0018] There are two types of LTE access on unlicensed frequencies. Licensed-Assisted Access (LAA), which functions as an additional downlink to a licensed LTE carrier (note: the uplink of eLAA is still connected to a licensed carrier), and MulteFire, which features full stand-alone operation within an unlicensed band. In LAA, both the licensed and unlicensed bands operate simultaneously. That is, data can be received on both bands at the same time. The Physical Broadcast Channel (PBCH) is carried only on the licensed carrier. However, the reference signal including the Primary Synchronization Signal (PSS) The discovery reference signal (DRS) of S12 (Rel-12) is , transmitted on unlicensed carriers at 40 millisecond intervals. Just detecting the DRS does not provide any further information, i.e., the cell identifier (ID), and cannot even identify the operator . MulteFire transmission includes PBC H / Physical Downlink Shared Channel (PDSCH )(currently called Enhanced PBCH (ePBCH)) in its downlink transmission, and by this , the energy in the sequences of the PSS and the Secondary Synchronization Signal (SSS ) is doubled, improving the detectability (see MulteFire Release 1.0.1 (www.multefire.org / specification)).

Summary of the Invention

[0019] The core of 3GPP NR Rel.15 PHY is a beam-based architecture . It is highly desirable for New Radio (NR) Unlicensed (NR-U) to utilize as many features of NR as possible, including the beam-based architecture. Different from eLAA which performs wide-beam-based sensing, narrow-beam sensing can help with coexistence by enabling efficient use of spatial resources . The LBT scheme is extended to support Carrier Sense Multiple Access and Collision Avoidance (CSMA / CA) . . Thus, the UE can avoid unnecessary carrier busy detection, thereby improving power efficiency. In NR-U, to improve spatial reuse and coexistence, the introduction of a signaling ring indicating channel occupancy may be considered. This means that new methods and signal designs in NR-U are required.

[0020] For example, to indicate channel occupancy by a node to nodes outside its cell, to indicate channel occupancy by a node to nodes within its cell to assist spectrum reuse, and also, to trigger handshakes between nodes within a cell to ensure that the receiver has a clear channel for transmission and reception, this specification discloses methods and apparatuses using channel access indicators in NR-U.

[0021] Also disclosed is the behavior of a node when it receives a CAI, that is, the method by which the node waits using a timer until it detects a channel. Information carried by the CAI for various use cases is also described.

[0022] Some procedures are also described to enable the transmission of Physical Uplink Shared Channel (PUSCH) from multiple starting positions within the UL grant. However, the starting positions are carried to the gNB via the CAI. The methods include the following. · A method of signaling PUSCH starting position candidates. · Procedures for adjusting the UL Demodulation Reference Signal (UL DMRS) based on the selected starting position of the PUSCH. · The DMRS may be power-boosted for the first PUSCH following the UE's Channel Occupancy Time (COT). · The first PUSCH may be power-boosted. · The PUSCH Resource Element (PUSCH RE) may be power-boosted for the first PUSCH following the UE's COT. · The first PUSCH following the UE's COT may be power-boosted. · The UE can signal the selected PUSCH start symbol using different DMRS sequences. · The UE can signal it. · The UE can use a higher density DMRS for the first PUSCH following the UE's COT. · It can use a higher density DMRS. · A puncturing procedure for fitting the PUSCH within the available resources. · A procedure for adapting the Modulation and Coding Scheme (MCS) based on the selected start position of the PUSCH to facilitate the detection of the MCS selected by the gNB. · A procedure for adapting the Modulation and Coding Scheme (MCS) based on the selected start position of the PUSCH to facilitate the detection of the MCS selected by the gNB. · A procedure to facilitate the detection of the MCS selected by the gNB. · A procedure for transmitting piggybacked Uplink Control Information (UCI). · A procedure for transmitting it.

[0023] · The PHY layer signaling techniques that enable CAI transmission on DL and UL will also be described. The PHY layer signaling techniques include the following. · The Physical Downlink Control Channel (PDCCH) such as signals on DL, PSS / SSS, · The Physical Downlink Control Channel (PDCCH) such as signals on DL, PSS / SSS, · and PSS / SSS, · PRACH, PUCCH on UL, and · Preamble-based transmissions including the following: · A partial indication of the CAI information regarding the preamble, and the rest via signals such as PDCCH or PRACH · A partial indication of the CAI information regarding the preamble, and the rest via signals such as PDCCH or PRACH · Asynchronous with respect to symbol timing, · Involving repeated and orthogonal cover codes (Orthogonal Cover Code: OCC) for providing some information regarding one or both of the cell ID and the channel occupancy time.

[0024] This summary is provided to introduce, in a simplified form, a selection of concepts that are further described in the detailed description below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all of the disadvantages described in any part of this disclosure.

[0025] (Brief Description of the Drawings) A more detailed understanding can be obtained from the following description, which is presented by way of example in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0026]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 3C

Figure 3D

Figure 3E

Figure 4

Figure 5A

Figure 5B

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21A

Figure 21B

Figure 21C

Figure 21D

Figure 21E

Figure 21F

Figure 21G

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37A

Figure 37B

Figure 38

Figure 39

Figure 40

Figure 41

Figure 42

Figure 43

Figure 44

Figure 45

Figure 46

Figure 47

Figure 48

Figure 49

Figure 50A

Figure 50B

Figure 50C

Figure 50D

Figure 51

Figure 52A

Figure 52B

Figure 53A

Figure 53B

Figure 54A

Figure 54B

Figure 54C

DETAILED DESCRIPTION OF THE INVENTION

[0027] The following is a list of abbreviations that may appear in the following description. Unless otherwise specified, the abbreviations used in this specification refer to the corresponding terms described in Table 2 below.

[0028]

Table 2-1

Table 2-2

[0029] In the Third Generation Partnership Project (3GPP), radio access, core transport sports network, and codec, security, and quality of service related Develop the technical standards of cellular communication network technology, including service capabilities that include such efforts to do. Recent wireless access technology (RAT) standards include Wideband Code Division Multiple Access: WCDMA (Registered Trademark) (commonly referred to as 3G ), LTE (commonly referred to as 4G), and LTE-Advanced specifications are included. 3GPP has started working on the standardization of the next-generation cellular technology, called New Radio (NR) and also referred to as "5G". The development of the 3GPP NR standard is expected to include the definition of next-generation wireless access technology (new RAT), which is expected to include provisions for new flexible wireless access below 6 GHz and new ultra-mobile broadband wireless access above 6 GHz. Flexible wireless access is expected to consist of new, non-backward-compatible wireless access in new spectrum below 6 GHz and is expected to include different operating modes that can be multiplexed within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with optimized designs specific to centimeter-wave and millimeter-wave with flexible wireless access below 6 GHz to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with optimized designs specific to centimeter-wave and millimeter-wave with flexible wireless access below 6 GHz to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband

[0030] 3GPP has identified various use cases that NR is expected to support, and as a result , various user experience requirements for data transfer speed, latency, and mobility were defined. Use cases include the following general categories: namely, extended mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in crowded areas, 50 Mbps or more anywhere, ultra-low-cost broadband access, in-vehicle mobile broadband), critical communications, massive machine type communications, network operations (e.g., network slicing, routing, migration and interworking, and energy saving ), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications within these categories include, for example, monitoring and sensor networks, remote control of devices, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, connectivity to first responders, automotive eCall, disaster alerts, real-time gaming, multi-party video calls, autonomous driving, augmented reality, touch internet, virtual reality, etc. This specification contemplates all of these use cases and others.

[0031] Figure 21A shows an embodiment of an example of a communication system 100 that can implement the methods and apparatuses described and claimed herein. As illustrated, an example of a communication system 100 includes wireless transmit / receive units , at least one of 102c and 102d (generally or collectively referred to as W which may also be referred to as TRU102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108 and the Internet 110, and other networks 112 may be included, but the disclosed embodiments are contemplated to include any number of WTRUs, base stations, networks, and network elements. It will be understood that each of WTRUs 102a, 102b, 102c, 102d, 102e is any type of device or apparatus configured to operate and communicate in a wireless environment. Each of WTRUs 102a, 102b, 102c, 102d, 102 e is illustrated as a handheld wireless communication device in FIGS. 21A - 21E, but assuming various use cases for 5 G wireless communication, each of the WTRUs is, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a wireless calling device, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a home appliance, a wearable device such as a smartwatch or smart clothing, a medical device or eHealth device, a robot, an industrial machine, a drone, a transportation device such as a passenger vehicle, a truck, a train, an aircraft, etc., including any device or apparatus configured to transmit and receive wireless signals, or may be embodied therein. It is understood that this may be the case.

[0032] The communication system 100 can further include a base station 114a and a base station 114b. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The RRHs 118a, 118b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The TRPs 119a, 119b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. As an example, the base stations 114a, 114b can be base transceiver stations. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, ... The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114a is wirelessly interfaced with at least one of the WTRUs 102a, 102b, 102c to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. The base station 114b can be any type of device configured to interface, either wired or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b and the transmission and reception points (TRPs) 119a, 119b to provide smooth access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and other networks 112. As an example, the base stations 114a, 114b can be base transceiver stations. (Base Transceiver Station: BTS), Node B, eNode B, Home Node B, Home eNode B, Site Controller, Access Point (AP), wireless router, etc. may also be used. Base stations 114a and 114b are each illustrated as a single element here, but it will be understood that base stations 114a and 114b can include any number of interconnected base stations or network elements.

[0033] Base station 114a may be part of RAN103 / 104 / 105, and RAN103 / 104 / 105 may also include other base stations or network elements (not shown) such as a Base Station Controller (BSC ), Radio Network Controller (RNC), relay node, etc. Base station 114b may be part of RAN103b / 104b / 105b, and RAN103b / 104b / 105b may also include other base stations or network elements (not shown) such as a Base Station Controller (BSC), Radio Network Controller (RNC), relay node, etc. Base station 114a may be configured to transmit and receive radio signals within a specific geographical area sometimes referred to as a cell (not shown). Base station 114b may be configured to transmit and receive wired or wireless signals within a specific geographical area sometimes referred to as a cell (not shown). A cell can be further divided into cell sectors. For example, the cell associated with base station 114a can be divided into three sectors. In one embodiment, base station 114a includes three transceivers, such that, for example, there is one for each sector of the cell. ​ is possible. In one embodiment, the base station 114a can adopt multiple-input multiple-output (MIMO) technology, and thus, multiple transceivers can be utilized per cell sector. Multiple Output:MIMO) technology can be employed, and accordingly, multiple transceivers can be utilized per cell sector.

[0034] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c via an air interface 115 / 116 / 117, and the air interfaces 115 / 116 / 117 may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interfaces 115 / 116 / 117 can be constructed using any suitable radio access technology (RAT). interface 115 / 116 / 117, and the air interfaces 115 / 116 / 117 may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interfaces 115 / 116 / 117 can be constructed using any suitable radio access technology (RAT). interface 115 / 116 / 117 may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interfaces 115 / 116 / 117 can be constructed using any suitable radio access technology (RAT). o Frequency:RF), microwave, infrared (IR), ultraviolet (Ultraviolet :UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 11 5 / 116 / 117 can be constructed using any suitable radio access technology (RAT). is possible.

[0035] The base station 114b may communicate with one or more of the RRHs 118a, 118b or TRPs 119a, 119b via a wired or air interface 115b / 116b / 117b, and the wired or air interface 115b / 116b / 117b may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT). interface 115b / 116b / 117b, and the wired or air interface 115b / 116b / 117b may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT). interface 115b / 116b / 117b may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT). propriate wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT). frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT). wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT).

[0036] The RRHs 118a, 118b or TRPs 119a, 119b are the WTRUs 102c, 102​ communicate with one or more of d via the air interfaces 115c / 116c / 117c which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV ), visible light, centimeter wave, millimeter wave, etc.). The air interfaces 115c / 116c / 117c can be constructed using any suitable radio access technology (RAT).

[0037] More specifically, as described above, the communication system 100 may be a multi - access system and may employ one or more channel access methods such as, for example, Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC - FDMA A), etc. For example, the base station 114a within RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, or the RRHs 118a, 118b and TRPs 119a, 119b within RAN 103b / 104b / 105b and the WTRUs 102c, 102d may be Universal Mobile Telecommunications System (UMTS) terrestrial radio access (T errestrial radio access (UTRA) in a UMTS network​​​ Terrestrial radio access: It may implement radio technologies such as UTRA), and according to that technology Therefore, an air interface 115 / 116 / 117 or 115c / 116c / 117c may be constructed respectively. WCDMA is It can include communication protocols such as High-Speed Packet Access (HSPA) and evolved HSPA (H SPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and High-Speed Uplink Packet Access (HSUPA). It is possible.

[0038] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or the RRHs 118a, 118b and the TRPs 1 19a, 119b in the RANs 103b / 104b / 105b and the WTRUs 102c, 102d may implement radio technologies such as evolved UMTS terrestrial radio access( E-UTRA), and according to that technology, air interfaces 115 / 116 / 117 or 115c / 116c / 117c using Long Term Evolution (LTE) or LTE-Advanced (LTE-A) may be constructed respectively. In the future, the air interfaces 115 / 116 / 117 may implement 3GPP NR technology as well.

[0039] In one embodiment, the base station 114a in the RANs 103 / 104 / 105 and the WTRU 102a, 102b, 102c, or the RRHs in the RANs 103b / 104b / 105b ​​​118a, 118b, TRP119a, 119b and WTRU102c, 102d are IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 Evolution-Data Optimized (EV-DO), Interim Standard (IS) 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GSM EDGE Radio Access Network (GERAN)), and other radio technologies may be implemented.

[0040] The base station 114c of FIG. 21A may be, for example, a wireless router, a home node B, a home e-node B, or an access point, and may utilize any suitable radio access technology (RAT) to facilitate wireless connectivity in a local area such as an office, a home, a vehicle, a campus, etc. In one embodiment, the base station 114c and the 02d may implement a wireless technology such as IEEE 802.15 to construct a Wireless Personal Area Network (WPAN). Further, in another embodiment, the base station 114c and the WTRU102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to construct a pico cell or a femto cell. As shown in FIG. 21A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. The RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are communicable with the core network 106 / 107 / 109, and the core network 106 / 107 / 109 is any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, ringing service, mobile location information service, prepaid calling, Internet connectivity, video distribution, etc., or perform advanced security functions such as user authentication. Although not shown in FIG. 21A, the RANs 103 / 104 / 105 and RANs 103b / 104b / 105b In another embodiment, 02d may implement a wireless technology such as IEEE 802.15 to construct a Wireless Personal Area Network (WPAN). Further, in another embodiment, the base station 114c and the WTRU102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to construct a pico cell or a femto cell. As shown in FIG. 21A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. The RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are communicable with the core network 106 / 107 / 109, and the core network 106 / 107 / 109 is any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, ringing service, mobile location information service, prepaid calling, Internet connectivity, video distribution, etc., or perform advanced security functions such as user authentication. Although not shown in FIG. 21A, the RANs 103 / 104 / 105 and RANs 103b / 104b / 105b In another embodiment, 02d may implement a wireless technology such as IEEE 802.15 to construct a Wireless Personal Area Network (WPAN). Further, in another embodiment, the base station 114c and the WTRU102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to construct a pico cell or a femto cell. As shown in FIG. 21A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109.

[0041] The RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are communicable with the core network 106 / 107 / 109, and the core network 106 / 107 / 109 is any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, ringing service, mobile location information service, prepaid calling, Internet connectivity, video distribution, etc., or perform advanced security functions such as user authentication. Although not shown in FIG. 21A, the RANs 103 / 104 / 105 and RANs 103b / 104b / 105b In another embodiment, 02d may implement a wireless technology such as IEEE 802.15 to construct a Wireless Personal Area Network (WPAN). Further, in another embodiment, the base station 114c and the WTRU102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to construct a pico cell or a femto cell. As shown in FIG. 21A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. The RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are communicable with the core network 106 / 107 / 109, and the core network 106 / 107 / 109 is any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, ringing service, mobile location information service, prepaid calling, Internet connectivity, video distribution, etc., or perform advanced security functions such as user authentication. Although not shown in FIG. 21A, the RANs 103 / 104 / 105 and RANs 103b / 104b / 105b In another embodiment, 02d may implement a wireless technology such as IEEE 802.15 to construct a Wireless Personal Area Network (WPAN). Further, in another embodiment, the base station 114c and the WTRU102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to construct a pico cell or a femto cell. As shown in FIG. 21A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. The RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are communicable with the core network 106 / 107 / 109, and the core network 106 / 107 / 109 is any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, ringing service, mobile location information service, prepaid calling, Internet connectivity, video distribution, etc., or perform advanced security functions such as user authentication. Although not shown in FIG. 21A, the RANs 103 / 104 / 105 and RANs 103b / 104b / 105b In another embodiment, 02d may implement a wireless technology such as IEEE 802.15 to construct a Wireless Personal Area Network (WPAN). Further, in another embodiment, the base station 114c and the WTRU102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to construct a pico cell or a femto cell. As shown in FIG. 21A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109.

[0042] Although not shown in FIG. 21A, the RANs 103 / 104 / 105 and RANs 103b / 104b / 105b b / 105b and core network 106 / 107 / 109 may communicate directly or indirectly with other RANs using the same RAT or a different RAT as RAN103 / 104 / 105 and RAN103b / 104b / 105b. It will be understood that it can communicate with other RANs using the same RAT or a different RAT as RAN103 / 104 / 105 and RAN103b / 104b / 105b. For example, core network 106 / 107 / 109 may be connected to RANs 103 / 104 / 105 and RAN103b / 104b / 105b that utilize E-UTRA radio technology and may also communicate with another RAN (not shown) that employs GSM radio technology without being limited to just being connected to RANs 103 / 104 / 105 and RAN103b / 104b / 105b. .

[0043] Core network 106 / 107 / 109 may also function as a gateway for WTRUs 102a, 102b, 102c , 102d, 102e to access PSTN 108, Internet 110, and other networks 112. PSTN 108 may include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) within the TCP / IP Internet protocol suite. Network 112 may include wired or wireless communication networks owned and operated by other service providers. For example, network 112 may include RANs 103 / 104 / 105 and RAN103b / 104b / 105b. RAN103b / 104b / 105b. RAN103b / 104b / 105b. RAN103b / 104b / 105b. RAN103b / 104b / 105b. RAN103b / 104b / 105b. RAN103b / 104b / 105b. RAN103b / 104b / 105b. One or more of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may use the same RAT as RAN103b / 104b / 105b or a different RAT. It may include another core network connected to one or more RANs.

[0044] A portion or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may have multi-mode capabilities. For example, the WTRUs 102a, 102b, 10 2c, 102d, and 102e may have multiple transceivers for communicating with different wireless networks via different wireless links. For example, the WTRU10 shown in FIG. 21A may be configured to communicate with a base station 114a that can employ a cellular-based wireless technology and a base station 114c that can employ IEEE 80 2 wireless technology.

[0045] FIG. 21B is a block diagram of an example of a device or apparatus, such as a WTRU10 configured for wireless communication according to an embodiment shown herein. As shown in FIG. 21B, the exemplary WTRU102 may include a processor 118, a transceiver 120, a transmit / receive element 1 22, a speaker / microphone 124, a keypad 126, a display / touch pad / indicator 128, a non-removable 130, a removable memory 132 a power supply 134, a Global Positioning System (GPS) chipset 136 and other peripheral devices 138. The WTRU102 can include any sub-combination of the above-described elements while maintaining consistency with one embodiment. It will also be understood that in each embodiment, the base stations 114a, 114b, and nodes that the base stations 114a, 114b may represent (especially, for example ), If so, the transceiver base station (BTS), Node B, site controller, access point (AP), Home Node B, Evolved Home Node-B (eNodeB), Home Evolved Node-B (HeNB), Home Evolved Node-B gateway, and proxy node, etc. (but not limited to these) are assumed to be able to include some or all of the elements described in this specification as shown in FIG. 21B. It is contemplated.

[0046] Processor 118 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and any other functions that enable the operation of WTRU 102 in a wireless environment. Processor 118 may be connected to transceiver 120, and transceiver 120 may be connected to transceiver element 122. FIG. 21B shows processor 1 18 and transceiver 120 as separate components, but it should be understood that processor 118 and transceiver 120 may be integrated into one electronic package or chip. It should be understood that it is also possible to integrate processor 118 and It will be done.

[0047] The transmit / receive element 122 communicates with a base station ( For example, it may be configured to transmit and receive signals to and from a base station 114a. In this embodiment, the transmit / receive element 122 is an antenna configured to transmit and receive RF signals. In one embodiment, the transmit / receive element 122 may be, for example, an IR, UV, or UV-sensitive element. It may be an emitter / detector configured to transmit and receive visible light signals. In one embodiment, the transmit / receive element 122 is adapted to transmit and receive both RF and optical signals. The transmit / receive element 122 may be configured to transmit and receive any combination of wireless signals. It will be understood that it can be configured as follows.

[0048] Additionally, although the transmit / receive element 122 is illustrated as a single element in FIG. 21B, the WTR The WTRU 102 may include any number of transmit / receive elements 122. More specifically, 2 may employ MIMO technology. 2 is for transmitting and receiving radio signals via the air interface 115 / 116 / 117. The transmitter / receiver element 122 (eg, multiple antennas) may be included.

[0049] The transceiver 120 modulates the signals transmitted by the transmit / receive element 122, and the transmit / receive element 122 As mentioned above, the WTRU 102 may be configured to demodulate the received signal. Thus, the transceiver 120 may be configured to allow the WTRU 102 to, for example, It supports multiple RATs, such as UTRA and IEEE 802.11. The transceiver may include:

[0050] The processor 118 of the WTRU 102 can receive input data from the speaker / microphone 124, keypad 126, and the display / touchpad / indicator 128 (e.g., a liquid crystal display (Liquid Crystal Display: LCD) display unit or an organic light-emitting diode (Organi c Light-Emitting Diode: OLED) display unit) to which it is connected. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and display / touchpad / indicator 128. Further, the processor 118 can access information from any suitable type of memory, such as non-removable 130 and removable memory 132, and store data therein. The non-removable 130 can include a random-access memory (Ra ndom-Access Memory: RAM), read-only memory (Read-Only Memory: ROM), hard disk, or any other type of storage device. The removable memory 132 can include a subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc. In one embodiment, the processor 118 can access information from a memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data therein. ndom-Access Memory: RAM), read-only memory (Read-Only Memory: ROM), hard disk, or any other type of storage device. The removable memory 132 can include a subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc. In one embodiment, the processor 118 can access information from a memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data therein. listick, secure digital (SD) memory card, etc. In one embodiment, the processor 118 can access information from a memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data therein. In one embodiment, the processor 118 can access information from a memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data therein. puter (not shown), and store data therein. cess and store data therein.

[0051] The processor 118 can receive power from the power supply 134 and other configured to distribute or control power to the components thereof. The power source 134 may be any suitable device for supplying power to the WTRU 102. For example, the power source 134 may include one or more dry cells, solar cells, fuel cells, and the like.

[0052] The processor 118 may also be connected to a GPS chipset 136 configured to provide position information (e.g., longitude and latitude) regarding the current position of the WTRU 102. The WTRU 102 may receive position information from the base station (e.g., base stations 114a, 114b) via the air interface 115 / 116 / 117 in addition to, or instead of, the information from the GPS chipset 136, or may determine its position based on the timing of signals received from two or more neighboring base stations. It will be understood that the WTRU 102 may obtain position information by any suitable positioning method while maintaining consistency with one embodiment. 116 / 117, or may determine its own position based on the timing of signals received from two or more neighboring base stations. The WTRU 102 can also receive position information from the base station (for example, base stations 114a, 114b) via the air interface 115 / 116 / 117 in addition to, or instead of, the information from the GPS chipset 136, or can determine its position based on the timing of signals received from two or more neighboring base stations. It is understood that the WTRU 102 may obtain position information by any appropriate positioning method while maintaining consistency with one embodiment. will be understood.

[0053] The processor 118 may also be further connected to other peripheral devices 138, which may include one or more software or hardware modules that provide additional features, functionality, and wired or wireless connectivity. For example, the peripheral devices 138 may include various sensors such as an accelerometer and a biometric (e.g., fingerprint) sensor, an electronic compass (e-Comp ass), a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands-free headset, a Bluetooth ass), a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands-free headset, a Bluetooth ass), a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands-free headset, a Bluetooth interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth Tooth (Registered Trademark) (Bluetooth) module, Frequency Modulated (FM) radio unit, digital music player, media player, video game player module, Internet browser, etc. can be included. WTRU102 can be embodied in other devices such as sensors, household appliances, wearable devices such as smartwatches and smart clothing, medical devices and eHealth devices, robots, industrial

[0054] devices, drones, transportation devices such as passenger cars, trucks, trains, airplanes, etc. WTRU102 can be connected to one of the peripheral devices 138 in such devices or other components, modules, or systems of such devices or devices through one or more interconnect interfaces such as an interconnect interface that may include. Figure 21C is a diagram of a system of RAN103 and core network 106 according to one embodiment. As described above, RAN103 can communicate with WTRU102a, 102b, 102c via air interface 115 using UTRA radio technology RAN103 can also communicate with core network 106. As shown in Figure 21C, RAN103 can include Node Bs 140a, 140b, 140c, and Node Bs 140a, 140b, 140c can each include one or more transceivers for communicating with WTRU102a, 102b, 102c via air interface 115. Node Bs 140a, 140b, 140c can each be connected to the specific in RAN103 through one or more interconnect interfaces such as an interconnect interface. Figure 21C is a diagram of a system of RAN103 and core network 106 according to one embodiment. As described above, RAN103 can communicate with WTRU102a, 102b, 102c via air interface 115 using UTRA radio technology

[0055] Figure 21C is a diagram of a system of RAN103 and core network 106 according to one embodiment. As described above, RAN103 can communicate with WTRU102a, 102b, 102c via air interface 115 using UTRA radio technology RAN103 can also communicate with core network 106. As shown in Figure 21C, RAN103 can include Node Bs 140a, 140b, 140c, and Node Bs 140a, 14Gb, 140c can each include one or more transceivers for communicating with WTRU102a, 102b, 102c via air interface 115. Node Bs 140a, 140b, 140c can each be connected to the specific in RAN103 through one or more interconnect interfaces such as an interconnect interface. As shown in Figure 21C, RAN103 can include Node Bs 140a, 140b, 140c, and Node Bs 140a, 140b, 140c can each include one or more transceivers for communicating with WTRU102a, 102b, 102c via air interface 115. Node Bs 140a, 140b, 140c can each be connected to the specific in RAN103 through one or more interconnect interfaces such as an interconnect interface. in RAN103 through one or more interconnect interfaces such as an interconnect interface. It may be associated with a fixed cell (not shown). RAN103 may further include RNCs 142a and 142 b. It will be understood that RAN103 may include any number of Node Bs and RNCs while maintaining consistency with one embodiment.

[0056] As shown in Figure 21C, Node Bs 140a and 140b can communicate with RNC 142a . Further, Node B 140c can communicate with RNC 142b. Node Bs 140a, 140b, and 140c can communicate with RNCs 142a and 142b respectively via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of RNCs 142a and 142b may be configured to control each of the Node Bs 140a, 140b, and 140c to which it is connected. Further, each of RNCs 142a and 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.

[0057] The core network 106 shown in Figure 21C includes a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving General Packet Radio Service (GPRS) Support Node (SGSN) 148, and a Gateway GPRS Support Node (GGSN) 150 ​​​​​​​Of which, at least one can be included. Each of the above elements is shown as a part of the core network 106 Although shown as parts of these elements, it will be understood that any of these elements may be owned and operated by entities other than the core network operator

[0058] The RNC 142a within the RAN 103 may be connected to the MSC 146 within the core network 106 via the IuCS interface The MSC 146 may be connected to the MGW 144 The MSC 146 and the MGW 144 provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, enabling smooth communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices

[0059] The RNC 142a within the RAN 103 may be further connected to the SGSN 148 within the core network 106 via the IuPS interface The SGSN 148 may be connected to the GGSN 150 The SGSN 148 and the GGSN 150 provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, enabling smooth communication between the WTRUs 102a, 102b, 102c and IP-compatible devices

[0060] As described above, the core network 106 may be further connected to a network 112 that may include a wired or wireless network owned and operated by another service provider

[0061] Figure 21D shows a system of the RAN 104 and the core network 107 according to one embodiment ​​​​​​​​​It is a figure. As described above, RAN 104 adopts the E-UTRA radio technology and can communicate with WTRUs 102a, 102b, and 102c via the air interface 116. RAN 104 can also communicate with the core network 107. RAN 104 can communicate with the core network 107.

[0062] RAN 104 may include eNodeBs 160a, 160b, and 160c. However, it will be understood that RAN 104 can include any number of eNodeBs while maintaining consistency with one embodiment. RAN 104 may include eNodeBs 160a, 160b, and 160c. However, it will be understood that RAN 104 can include any number of eNodeBs while maintaining consistency with one embodiment. Each of eNodeBs 160a, 160b, and 160c can include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via the air interface 116. In one embodiment, eNodeBs 160a, 160b, and 160c may implement MIMO technology. In this way, eNodeB 160a can transmit and receive radio signals from WTRU 102a using, for example, multiple antennas. Each of eNodeBs 160a, 160b, and 160c can include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via the air interface 116. In one embodiment, eNodeBs 160a, 160b, and 160c may implement MIMO technology. In this way, eNodeB 160a can transmit and receive radio signals from WTRU 102a using, for example, multiple antennas. 160b, and 160c may implement MIMO technology. In this way, eNodeB 160a can transmit and receive radio signals from WTRU 102a using, for example, multiple antennas. 160b, and 160c may implement MIMO technology. In this way, eNodeB 160a can transmit and receive radio signals from WTRU 102a using, for example, multiple antennas.

[0063] Each of eNodeBs 160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to perform processes such as radio resource management decisions, handover decisions, and user scheduling in the uplink and downlink. As shown in FIG. 21D, eNodeBs 160a, 160b, and 160c can communicate with each other via the X2 interface. Each of eNodeBs 160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to perform processes such as radio resource management decisions, handover decisions, and user scheduling in the uplink and downlink. As shown in FIG. 21D, eNodeBs 160a, 160b, and 160c can communicate with each other via the X2 interface. Each of eNodeBs 160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to perform processes such as radio resource management decisions, handover decisions, and user scheduling in the uplink and downlink. As shown in FIG. 21D, eNodeBs 160a, 160b, and 160c can communicate with each other via the X2 interface. As shown in FIG. 21D, the core network 107 includes a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (Packet Data As shown in FIG. 21D, the core network 107 includes a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (Packet Data

[0064] As shown in FIG. 21D, the core network 107 includes a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (Packet Data As shown in FIG. 21D, the core network 107 includes a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (Packet Data The network: may include a PDN gateway 166. Each of the above elements is illustrated as part of the core network 107, but it is understood that any of these elements may be owned and operated by entities other than the core network operator. It will be so.

[0065] The MME 162 may be connected to each of the eNodeBs 160a , 160b, 160c within the RAN 104 via the S1 interface and may function as a control node. For example, the MME 162 may be in charge of user authentication of the WTRUs 102a, 102b, 102c, activation / deactivation of bearers, selection of a specific serving gateway during the initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may further provide control plane functions for switching between the RAN 104 and other RANs (not shown) using other radio technologies such as GSM and WCDMA.

[0066] The serving gateway 164 may be connected to each of the eNodeBs 160a , 160b, 160c within the RAN 104 via the S1 interface. The serving gateway 164 can generally route and forward user data packets to and from the WTRUs 102a, 102b, 102 c. The serving gateway 164 can further perform other functions such as anchoring of user planes during handover between eNodeBs, triggering paging when the WTRUs 102a, 102b, 102c are capable of using downlink data, and management and storage of contexts of the WTRUs 102a, 102b, 102c, etc. It can execute other functions such as.

[0067] The serving gateway 164 may further be connected to the PDN gateway 166. Well, the PDN gateway 166 provides access to a packet switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and can smooth the communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The core network 107 can smooth the communication with other networks. For example, the core network 107 provides access to a circuit switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and can smooth the communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. Further, the core network 107 can provide the WTRUs 102a, 102b, 102c with access to a network 112 that may include wired or wireless communication networks owned and operated by other service providers. The core network 107 can smooth the communication with other networks. For example, the core network 107 provides access to a circuit switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and can smooth the communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. Further, the core network 107 can provide the WTRUs 102a, 102b, 102c with access to a network 112 that may include wired or wireless communication networks owned and operated by other service providers.

[0068] The core network 107 can smooth the communication with other networks. For example, the core network 107 provides access to a circuit switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and can smooth the communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. For example, the core network 107 provides access to a circuit switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and can smooth the communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. Further, the core network 107 can provide the WTRUs 102a, 102b, 102c with access to a network 112 that may include wired or wireless communication networks owned and operated by other service providers. the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. Further, the core network 107 can provide the WTRUs 102a, 102b, 102c with access to a network 112 that may include wired or wireless communication networks owned and operated by other service providers. the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. Further, the core network 107 can provide the WTRUs 102a, 102b, 102c with access to a network 112 that may include wired or wireless communication networks owned and operated by other service providers. IP Multimedia Subsystem: IMS) server), or communicate with it. Furthermore, the core network 107 can provide the WTRUs 102a, 102b,

END

[0069] Figure 21E is a diagram of a system of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 employs IEEE 802.16 wireless technology and communicates with the WTRUs 102a, 102b, 102c via the air interface 117. Figure 21E is a diagram of a system of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 employs IEEE 802.16 wireless technology and communicates with the WTRUs 102a, 102b, 102c via the air interface 117. Figure 21E is a diagram of a system of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 employs IEEE 802.16 wireless technology and communicates with the WTRUs 102a, 102b, 102c via the air interface 117. It may also be an access service network (ASN). As will be discussed later, the communication links between different functional entities such as WTRU102a, 102b, 102c, RAN105, and core network 109 can be defined with reference points. This can be done.

[0070] As shown in Figure 21E, RAN105 may include base stations 180a, 180b, 180c and an ASN gateway 182. However, it will be understood that RAN105 may include any number of base stations and ASN gateways while maintaining consistency with one embodiment. The base stations 180a, 180b, 180c may each be associated with a specific cell within RAN105 and may include one or more transceivers for communicating with WTRU102a, 102b, 10 2c via the air interface 117. In one embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. In this way, the base station 180a, for example, can transmit and receive wireless signals to and from WTRU102a using multiple antennas. The base stations 180a, 180b, 18 0c can further provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, and enforcement of quality of service (QoS) policies. The ASN gateway 182 can function as a traffic aggregation point and can be responsible for paging, caching of subscriber profiles, routing to the core network 109, etc.

[0071] The air interface 1 between WTRU102a, 102b, 102c and RAN105 17 can be defined as an R1 reference point implementing the IEEE 802.16 specification. Further, each of the WTRUs 102a, 102b, 102c can establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and mobility management. Furthermore, each of the WTRUs 102a, 102b, 102c can establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and mobility management. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and mobility management. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and mobility management. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and mobility management.

[0072] The communication links between each of the base stations 180a, 180b, 180c can be defined as an R8 reference point that includes a protocol for facilitating WTRU handover and data transfer between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 can be defined as an R6 reference point.The R6 reference point can include a protocol for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c. The communication links between each of the base stations 180a, 180b, 180c can be defined as an R8 reference point that includes a protocol for facilitating WTRU handover and data transfer between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 can be defined as an R6 reference point. The R6 reference point can include a protocol for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 can be defined as an R6 reference point. The R6 reference point can include a protocol for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0073] As shown in Figure 21E, the RAN 105 can be connected to the core network 109. The communication link between the RAN 105 and the core network 109 can be defined as an R3 reference point that includes a protocol for facilitating data transfer and mobility management capabilities. The core network 109 can include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. The communication link between the RAN 105 and the core network 109 can be defined as an R3 reference point that includes a protocol for facilitating data transfer and mobility management capabilities. The communication link between the RAN 105 and the core network 109 can be defined as an R3 reference point that includes a protocol for facilitating data transfer and mobility management capabilities. The core network 109 can include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. The core network 109 can include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. The core network 109 can include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. It is possible. Although each of the above elements is illustrated as part of the core network 109, it should be understood that any of these elements may be owned and operated by entities other than the core network operator. It should be understood that any of these elements may be owned and operated by entities other than the core network operator. It should be understood that any of these elements may be owned and operated by entities other than the core network operator.

[0074] MIP-HA can be in charge of IP address management, enabling the WTRU102a, 102b, 102c to roam between different ASNs and different core networks. MIP-HA can be in charge of IP address management, enabling the WTRU102a, 102b, 102c to roam between different ASNs and different core networks. MIP-HA 184 can provide access to a packet-switched network such as the Internet 110 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and IP-compatible devices. The AAA server 186 can be in charge of user authentication and user service support. The gateway 188 can smooth the interworking with other networks. MIP-HA 184 can provide access to a packet-switched network such as the Internet 110 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and IP-compatible devices. The AAA server 186 can be in charge of user authentication and user service support. The gateway 188 can smooth the interworking with other networks. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRU102a, 102b, 102c, and can smooth the communication between the WTRU102a, 102b, 102c and conventional fixed wired communication devices. Furthermore, the gateway 188 can provide access to a network 112 that may include a wired or wireless communication network owned and operated by other service providers to the WTRU102a, 102b, 102c.

[0075] Although not shown in FIG. 21E, it should be understood that the RAN 105 may be connected to other ASNs, and the core network 109 may be connected to other core networks. Although not shown in FIG. 21E, it should be understood that the RAN 105 may be connected to other ASNs, and the core network 109 may be connected to other core networks. The communication link between the RAN 105 and other ASNs can be defined with the R4 reference point. The R4 reference point can include a protocol for adjusting the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs. The communication link between core network 109 and other core networks can be defined as an R5 reference, and the R5 reference can include a protocol for facilitating interworking between the home core network and the visited core network. c between RAN 105 and other ASNs. The communication link between core network 109 and other core networks can be defined as an R5 reference, and the R5 reference can include a protocol for facilitating interworking between the home core network and the visited core network. 9 and other core networks can be defined as an R5 reference, and the R5 reference can include a protocol for facilitating interworking between the home core network and the visited core network. 5 reference can include a protocol for facilitating interworking between the home core network and the visited core network. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future.

[0076] The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future. The core network entities described herein and shown in FIGS. 21A, 21C, 21D, 21E are identified by the names given to those entities in certain existing 3GPP specifications, but those entities and functionality may be identified by other names in the future, and it is understood that certain entities or functionality may be combined in future specifications, including 3GPP NR specifications, issued by 3GPP. Accordingly, the specific network entities and functionality described and shown in FIGS. 21A, 21B, 21C, 21D, 21E are presented by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future.

[0077] FIG. 21F can embody one or more devices of the communication network shown in FIGS. 21A, 21C, 21D, 21E, such as, for example, certain nodes or functional entities within RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, Internet 110, or other network 112. FIG. 21F can embody one or more devices of the communication network shown in FIGS. 21A, 21C, 21D, 21E, such as, for example, certain nodes or functional entities within RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, Internet 110, or other network 112. FIG. 21F can embody one or more devices of the communication network shown in FIGS. 21A, 21C, 21D, 21E, such as, for example, certain nodes or functional entities within RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, Internet 110, or other network 112. FIG. 21F can embody one or more devices of the communication network shown in FIGS. 21A, 21C, 21D, 21E, such as, for example, certain nodes or functional entities within RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, Internet 110, or other network 112. It is a block diagram of system 90. Computing system 90 can include a computer or a server, and may be mainly controlled by computer-readable instructions. The instructions may be in the form of software, and the software may be stored or accessed anywhere or by any means. Such computer-readable instructions may be executed within processor 91 to operate computing system 90. Processor 91 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 91 can execute signal encoding, data processing, power control, input / output processing, and any other functions to enable the operation of computing system 90 within a communication network. The co-processor 81 is an optional processor that executes additional functions separately from the main processor 91 or assists the processor 91. At least one of the processor 91 and the co-processor 81 can receive, generate, and process data related to the methods and devices disclosed in this specification. During operation, the processor 91 fetches, decodes, and executes instructions to communicate with other resources via the system bus 80, which is the main data transfer path of the computing system.

[0078] ​​​​​​​​​​​​​​Transfers information. Such a system bus connects the components within the computing system 90 and defines the mediation of data exchange. The system bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for sending interrupts and operating the system bus. An example of such a system bus 80 is the Peripheral Component Interconnect (PCI) bus. :PCI) bus.

[0079] The memory connected to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes circuits that enable information to be stored and read. The ROM 93 generally stores non-easily modifiable stored data. The data stored in the RAM 82 can be read or modified by the processor 91 or other hardware devices. Access to at least one of the RAM 82 and the ROM 9 3 can be controlled by the memory controller 92. The memory controller 92 can provide an address translation function that converts virtual addresses to physical addresses as instructions are executed. The memory controller 92 can further provide a memory protection function that isolates each process within the system and isolates system processes from user processes. Thus, a program running in the first mode can access only the memory mapped by its own process virtual address space and cannot access the memory within the virtual address space of another process unless memory sharing between processes is set.

[0080] Furthermore, the computing system 90 can include a peripheral controller 83 that facilitates the transmission of instructions from the processor 91 to peripheral devices such as the printer 94, keyboard 84, mouse 95, and disk drive 85.

[0081] The display 86, which is controlled by the display controller 96, is used to display visual output generated by the computing system 90. Such visual output can include text, graphics, video graphics, and video. The visual output can be presented in the form of a graphical user interface (GUI). The display 86 can be implemented using a cathode-ray tube (CRT)-based video display, an LCD-based flat panel display , a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components necessary to generate the video signals transmitted to the display 86.

[0082] Furthermore, the computing system 90 can include a communication circuit, such as a network adapter 97, that can be used to connect the computing system 90 to an external communication network, such as the RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other network 112 shown in FIGS. 21A, 21B, 21C, 21D, and 2 1E, thereby enabling the computing system 90 to communicate with other devices and systems over the network. - The ting system 90 can communicate with other nodes or functional entities of those networks. The communication circuit can be used alone or together with the processor 91 to execute the transmission and reception steps of the specific devices, nodes, or functional entities described herein.

[0083] Introduction of Channel Access Indicator (CAI) in NR-U

[0084] According to one aspect of the systems and methods disclosed herein, NR-U supports channel access indication using a channel access indicator (CAI), and the channel access indicator (CAI) can be signaled to indicate information about channel occupancy, such as the cell occupying the channel, the occupied bandwidth / spatial direction, and the occupancy time.

[0085] An NR-U node is a node that can transmit and receive within the NR-U band. To distinguish the types of nodes in the NR-U channel, the following terms are introduced. · Sibling node: A node served by the same serving NR-U cell as the reference node. More specifically, the sibling nodes of a particular node can be defined as any co-channel node or any co-channel user having the same serving cell as that particular node. Note: Co-channel transmission can be UL transmission by a specific UE or DL transmission to a specific UE. s is used to indicate a general sibling node. In other words, nodes within the same NR-U serving cell as the reference node are considered sibling nodes. This includes gNBs within the serving cell. ​ General node: A node that is not served by the same NR-U cell as the reference node. The same Public Land Mobile Network (PLM) number is used for N), another cell in a different PLMN, or WiFi It may contain nodes of other technologies. More specifically, it may contain general information related to a particular node. A node may be any co-channel node or any co-channel node with different serving cells. as a local user or as a serving cellular or non-cellular RAT of a particular node Any controller with a serving cellular or non-cellular RAT different from the AT Note: Co-channel transmissions can be defined as either a channel UE or a co-channel user. This can be a UL transmission by the UE or a DL transmission to a specific UE. g is a generic Used to indicate a general node.

[0086] CAI may serve one or more of the following purposes: Use Case 1: Demonstrates network domination for coexistence. Use case 2: Allowing nodes to distinguish between intra-cell transmissions and enabling spectrum reuse Improve. Use case 3: Ensure that there are no hidden nodes blocking access to the channel To do this, the receiver triggers a handshake. Use Case 4: Allows the receiver to know when the transmitter is transmitting This allows for power saving.

[0087] Use Case 1: Using CAI to Indicate Network Occupancy for Coexistence

[0088] When the sibling node and the general node detect the CAI, they can obtain the time when the channel is occupied from the CAI. Therefore, it is not necessary to perform channel sensing during the occupancy period. Figure 1(A) shows an example in which the gNB transmits the CAI in cell 1, indicating that the transmission source, that is, cell 1, occupies the transmission. Also, it can indicate the occupancy time of the channel. The node UE1 from cell 1 identifies this as an in-cell transmission. General nodes such as UE2 from NR-U cell 2 and gNB2 of NR-U cell 2 identify the transmission as a transmission from a node outside their own cell, but can read the occupancy time. A node 3 within the WiFi network may have the ability to detect and read the CAI from the NR-U network. The general node may not perform LBT until the occupancy time of cell 1 has elapsed. Figure 1(B) shows the response method of the general node when receiving the CAI communication from cell 1. In that method, after the channel occupancy time of cell 1, the general node resumes the Clear Channel Assessment (CCA). CCA is an initial channel sensing that performs at least Energy Detection (ED) over a specific period using a specific threshold. For this reason, it is not necessary to execute channel sensing during the occupancy period. Figure 1(A) shows an example in which the gNB transmits the CAI in cell 1, that is, the transmission source, i.e., cell 1, occupies the transmission. Also, it can show the occupancy time of the channel. The node UE1 from cell 1 identifies this as an in-cell transmission. General nodes such as UE2 from NR-U cell 2 and gNB2 of NR-U cell 2 identify the transmission as a transmission from a node outside their own cell, but can read the occupancy time. A node 3 within the WiFi network may have the ability to detect and read the CAI from the NR-U network. The general node may not perform LBT until the occupancy time of cell 1 has elapsed. Figure 1(B) shows the response method of the general node when receiving the CAI communication from cell 1. In that method, after the channel occupancy time of cell 1, the general node resumes the Clear Channel Assessment (CCA). CCA is an initial channel sensing that performs at least Energy Detection (ED) over a specific period using a specific threshold. In that method, after the channel occupancy time of cell 1, the general node resumes the Clear Channel Assessment (CCA). CCA is an initial channel sensing that performs at least Energy Detection (ED) over a specific period using a specific threshold. is a single.

[0089] Generally, the CAI can be signaled in both the DL and UL. In Autonomous UL (AUL) and semi-persistent scheduling, the UE is configured semi-statically for its resources. It is not guaranteed that the UE's resources are within the Maximum Channel Occupancy Time (MCOT) of its gNB. (Autonomous UL:AUL) and semi-persistent scheduling, the UE is configured semi-statically for its resources. The UE's resources are configured semi-statically for its resources. It is not guaranteed that the UE's resources are within the Maximum Channel Occupancy Time (MCOT) of its gNB. In this case, the UE is classified as Category 4 LBT (CAT4LBT). The LBT may be performed in the UL after a successful LBT to determine the availability of the channel. Send CAI.

[0090] Use Case 2: Using CAI to demonstrate spectrum reuse

[0091] When a node notices that another node in its cell is occupying the channel, it It can adjust its threshold for energy detection accordingly: ,If the node receives energy from its sibling nodes, the CC without CAI is A higher threshold (lower) compared to the lower threshold (equation 1 below) typically used in A The following equation (2) can be used for energy detection to determine LBT failure. The method in Figure 4 illustrates this concept.

[0092]

number

[0093]

number

[0094] This feature allows multiple UEs to be multiplexed in frequency or time, allowing for better spatial reuse. This is particularly useful in the UL where the UE is able to reduce intra-cell usage and high energy If ,detected, the detected energy is from a multiplexed intra-cell UE, so The CAI allows the UE to transmit on a co-channel with its sibling nodes through multiplexing. Resource sharing: co-channel resources are multiplexed onto the same time / frequency resource Either multiplexed only by time, only by frequency, or by both time and frequency. For example, in NR UL, multiple UEs (orthogonally) share physical uplink control channel (PUCCH) resources, or multiple UEs non-orthogonally share resources in non-orthogonal multiple access (NOMA), or multiple UEs are time / frequency multiplexed for PUSCH. As shown in Figure 2(A), taking the example of two sibling nodes multiplexed in time, where UE1 has UL transmission within mini-slot #1 and UE2 has UL transmission within mini-slot #2. UE2 may be blocked due to the energy level from UE1. Similarly, when two sibling nodes are multiplexed within the same frequency and time resources for PUCCH and perform CAT4 LBT for transmission, UE1 can access the channel earlier. Since UE2 may have a large random backoff, it is assumed that UE2 listens to UE1 and cannot access the channel as shown in Figure 2(B). When sibling node UE2 performs energy detection, it may detect the energy from UE1 and not transmit within the scheduled resources. Therefore, within an NR-U cell, even though multiplexed nodes should be able to transmit within the scheduled resources, they may fail in CCA / LBT due to the high energy level from other sibling nodes. For example, in NR UL, multiple UEs share physical uplink control channel (PUCCH) resources (orthogonally), or multiple UEs non-orthogonally share resources in non-orthogonal multiple access (NOMA), or multiple UEs are time / frequency multiplexed for PUSCH. As shown in Figure 2(A), taking the example of two sibling nodes multiplexed in time, where UE1 has UL transmission within mini-slot #1 and UE2 has UL transmission within mini-slot #2. UE2 may be blocked due to the energy level from UE1. Similarly, when two sibling nodes are multiplexed within the same frequency and time resources for PUCCH and perform CAT4 LBT for transmission, UE1 can access the channel earlier. Since UE2 may have a large random backoff, it is assumed that UE2 listens to UE1 and cannot access the channel as shown in Figure 2(B). When sibling node UE2 performs energy detection, it may detect the energy from UE1 and not transmit within the scheduled resources. Therefore, within an NR-U cell, even though multiplexed nodes should be able to transmit within the scheduled resources, they may fail in CCA / LBT due to the high energy level from other sibling nodes. When sibling node UE2 performs energy detection, it may detect the energy from UE1 and not transmit within the scheduled resources. Therefore, within an NR-U cell, even though multiplexed nodes should be able to transmit within the scheduled resources, they may fail in CCA / LBT due to the high energy level from other sibling nodes. Even though multiplexed nodes should be able to transmit within the scheduled resources, they may fail in CCA / LBT due to the high energy level from other sibling nodes.

[0095] As shown in Figure 3A, UE1 transmits a CAI. Upon hearing it, UE2, the sibling Identify node transmission and transmit the scheduled multiplexed PUSCH.

[0096] To ensure that the CAI of the UE is reliably heard by other UEs, particularly the multiplexed sibling node UEs, it is proposed in this specification to use a method similar to CAT4LBT. As a result, the UE backs off randomly. The UE that first accesses the channel transmits the CAI, and other UEs with a larger backoff listen to this CAI. As shown in FIGS. 3B and 3C, UE1 accesses the channel before UE2 and transmits its own CAI. UE2 starts channel sensing by means of CCA using a threshold (Equation 1) as part of CAT4LBT. If UE2 continues to sense the channel during its random backoff, it detects higher energy. Therefore, UE2 listens for the CAI. UE2 detects the CAI and recognizes it as an in-cell transmission. At this point, UE2 can perform any of the following. · UE2 changes its LBT threshold to the threshold (Equation 2) and continues extended sensing with a higher threshold. If the energy is within this threshold, UE2 transmits its scheduled PUSCH together with the PUSCH of UE1 within the Frequency Division Multiplexing (FDM) resource. This is shown in FIGS. 3A(B). The method is shown in FIG. 5A. · Due to the change of UE2, the current LBT ends and its random backoff timer is reset. UE2 performs CCA (e.g., CCA of 25 microseconds) which is usually a short procedure using the threshold (Equation 2). If it succeeds, UE2 schedules The PUSCH transmission continues as scheduled. This is shown in Figure 3C. The method is shown in Figure 5B.

[0097] If the UE does not receive a CAI from a sibling node, it may send its own CAI. Figure 3D shows an example in which UE2 does not receive CAI from UE1 and transmits its own CAI. Other sibling nodes, UE or gNB, may hear the CAIs of both UE1 and UE2. Therefore, CAIs from multiple UEs may collide in time / frequency. According to one aspect, by utilizing the orthogonality / low correlation between CAIs from different UEs, This makes the UL CAI design robust against collisions. One way to achieve this is to provide different frequency resources for different UE CAIs. Another method that provides robustness is PRACH, which has good cross-correlation properties. It is through a sequence.

[0098] The CAI is also signaled by the gNB on cell 1 to indicate the occupancy time. The CAI receives the data from the server that is scheduled or configured to transmit during its dedicated time. For rule 1 UEs, it is possible to do so using a higher threshold for CCA. For example, in Figure 3E, UE1 and UE2 are connected to the gNB. When it receives a CAI from the To do this, a higher threshold (Equation 2) is used.

[0099] For UE, the threshold for LBT energy level detection is specified as part of the UL certification. via radio resource control (RRC) in a cell-wide or UE-specific manner. It can be constituted by B. For example, two UEs are frequency multiplexed, and among them, if UE 1 occupies 80% of the frequency resources, while UE2 occupies the remaining 20% , the threshold (Equation 2) by UE2 may be higher than that for UE1. gNB can configure a table of values of V thresh for the UE. It can indicate the actual values used as an index to the table. The index can be signaled in a DCI format such as 1_1, 0_1, 1_0, or 0_0. If the BWP for the UE is not configured to support a field for indicating the index, the UE can apply the threshold (Equation 1) for LBT regardless of whether it detects the CAI of the sibling node.

[0100] It is also possible to provide radio resource control (RRC)-configured values for use in a specific scenario. For example, since gNB does not know the number of UEs it can access, V t hresh may be configured to a specific value for PRACH signaling.

[0101] Alternatively, the UE may implicitly derive the threshold from the reference threshold configured for the BWP. If the UE occupies a part of the bandwidth part, the UE may scale the reference threshold by that part.

[0102] CAI can be used as a reservation signal to ensure efficient use of the spectrum. .

[0103] Figure 4 shows the general procedure at the node when receiving CAI from the sibling node. ​​​​​​​

[0104] Use Case 3: Use of CAI to handshake between Tx and Rx to overcome hidden nodes

[0105] The CAI from the transmitter indicates that the channel is available at the transmitter. Also, before scheduling a large payload, the transmitter may request a handshake with the receiver to ensure that the channel is available at the receiver. This helps to solve the problem of hidden nodes near the receiver. In this case, the CAI from the transmitter can be defined as CAI-Initial (CAI-I), and the CAI response from the receiver can be defined as CAI-Response (CAI-R). If the CAI-R is not received at the initiating node, the responding side is considered to have failed in LBT, and in that case, the initiating side may not transmit to the responding side until later. CAI-I and CAI-R can be transmitted from both gNB and UE.

[0106] When the gNB transmits the CAI-I, it can wait for the CAI-R before scheduling the grant to the UE. The CAI-I may be transmitted after CAT4 LBT because the initiating node intends to use the channel to transmit a payload to the responding node. Sensing at the responding node may be in the form of CCA (which may be short sensing intervals such as 25 microsecond sensing for DRS in FR1 in unlicensed LTE). This is short and reduces the possibility of other nodes occupying the channel during the sensing period.

[0107] ​​​​​​​​​​​​​​​Figure 6 shows a method for establishing a handshake between two nodes.

[0108] Figure 7(A) shows the concept of a handshake between two sibling nodes where the gNB starts CAI-I and the UE responds with CAI-R. CAI-I may be transmitted by the UE on the UL, especially when performing the CAT4 LBT procedure. When the gNB's channel is cleared and then the UE transmits a UL signal such as PUSCH or PUCCH, the gNB may respond with CAI-R. As shown in Figure 7(B), CAI-R can be synchronized to the symbol boundary. To achieve this, the responding node transmits a reservation signal following LBT. The starting node receives CAI-R assuming there is symbol boundary alignment. Synchronous transmission is beneficial when there is a large amount of information to be carried during CAI and it needs to be carried in signals such as PDCCH or PUCCH. Or, as shown in Figure 7(C), CAI-I and CAI-R may be transmitted asynchronously with respect to the symbol boundary. CAI may carry only a few bits of information and may be transmitted as a signal (e.g., with a preamble) in a way that can be detected through a temporal correlation relationship. In such a case, asynchronous transmission of CAI is suitable to keep the latency low. This can minimize the latency until the handshake is completed, especially for CAI-R. The responding node transmits a reservation signal following CAI-R to keep the channel occupied for at least the time it takes for the starting node to detect the channel. When the gNB's channel is cleared and then the UE transmits a UL signal such as PUSCH or PUCCH, the gNB may respond with CAI-R.

[0109] As shown in Figure 7(B), CAI-R can be synchronized to the symbol boundary. To achieve this, the responding node transmits a reservation signal following LBT. The starting node receives CAI-R assuming there is symbol boundary alignment. Synchronous transmission is beneficial when there is a large amount of information to be carried during CAI and it needs to be carried in signals such as PDCCH or PUCCH. To achieve this, the responding node transmits a reservation signal following LBT. The starting node receives CAI-R assuming there is symbol boundary alignment. Synchronous transmission is beneficial when there is a large amount of information to be carried during CAI and it needs to be carried in signals such as PDCCH or PUCCH. The starting node receives CAI-R assuming there is symbol boundary alignment. Synchronous transmission is beneficial when there is a large amount of information to be carried during CAI and it needs to be carried in signals such as PDCCH or PUCCH. Synchronous transmission is beneficial when there is a large amount of information to be carried during CAI and it needs to be carried in signals such as PDCCH or PUCCH.

[0110] Alternatively, as shown in Figure 7(C), CAI-I and CAI-R may be transmitted asynchronously with respect to the symbol boundary. CAI may carry only a few bits of information and may be transmitted as a signal (e.g., with a preamble) in a way that can be detected through a temporal correlation relationship. Alternatively, as shown in Figure 7(C), CAI-I and CAI-R may be transmitted asynchronously with respect to the symbol boundary. CAI may carry only a few bits of information and may be transmitted as a signal (e.g., with a preamble) in a way that can be detected through a temporal correlation relationship. CAI may carry only a few bits of information and may be transmitted as a signal (e.g., with a preamble) in a way that can be detected through a temporal correlation relationship. In such a case, asynchronous transmission of CAI is suitable to keep the latency low. This can minimize the latency until the handshake is completed, especially for CAI-R. This can minimize the latency until the handshake is completed, especially for CAI-R. The responding node transmits a reservation signal following CAI-R to keep the channel occupied for at least the time it takes for the starting node to detect the channel. ​​A reservation can be made so that other nodes cannot acquire the channel. Next, the starting node may send a transmission to the response node without re - executing LBT. Therefore, a reservation signal may be sent after CAI - R is transmitted.

[0111] The reservation signal can be generated by repeating the CAI - R signal for a required period .

[0112] Since the gNB can use CAI - R to evaluate the UE's environment when other multiplexed UEs are transmitting, the gNB can sometimes trigger CAI - R for a specific UE and use the result to determine future scheduling. The UE can also send back the detected energy level (during the LBT period) to the gNB. This helps to detect the impact of interference from sibling UEs on a specific UE within the UL, and the gNB can make a decision (orthogonal or non - orthogonal) on UE multiplexing based on CAI - R. In this case, the UE can be RRC - configured with resources for CAI - R, but the UE transmits CAI - R only when it receives a trigger via CAI - I.

[0113]

[0113] Use Case 4: Use of CAI to enable power saving

[0114] A receiver node such as a UE can monitor the channel occupancy of its transmitter, for example, a low - power - state gNB that monitors only CAI. When CAI is received, the receiver switches to the nominal power state and monitors the control channel, data channel, and reference signals from the transmitter. When the COT expires, the receiver returns to the low - power state and monitors the control channel, data channel, and reference signals from the transmitter. When the COT expires, the receiver returns to the low - power state and monitors the control channel, data channel, and reference signals from the transmitter. When the COT expires, the receiver returns to the low - power state It may return to the state and monitor the CAI.

[0115] Methods related to CAI

[0116] CAI transmission operation

[0117] If Node 1 transmits the CAI at time t milliseconds, T REL milliseconds can be defined as the time when Node 1 releases the channel. Therefore, T = t + T REL milliseconds, provided that T оcc m illiseconds, where T оcc is the indicated channel occupancy time. T REF can be defined as the length of a known interval such as a slot, OFDM symbol, subframe, half-frame, etc. in the reference numerology. For the remaining description, consider the example where T is given in the context of the reference numerology slot period. T REF can be defined as a multiple of T оcc · (in milliseconds). Therefore, the CAI can use D bits to indicate T REF in the context of the reference slot period. Node 1 may find the maximum T оcc = T оcc MCOT However, T

[0118] is the time of the MCOT for that channel access instance of Node 1 оcc = T MCOT and T оcc M COT can be based on the priority class for the LBT used in channel access. In such cases, there may be situations where the M bits for the MCOT cannot be transmitted separately. MCOT

[0119] ​​​​​Figure 8 gives an example for T in CAI. Here, Node 1 accesses the channel at T оcc = 10 ms and transmits CAI in slot #N of the frame M COT = 10 ms. Node 1 intends to use a 7-slot channel and then release it. Thus, CAI indicates T = 7 ms assuming T = 1 ms REF = 1 ms оcc = 7 ms

[0120] Node s and Node g can operate T оcc using the following method Node s and Node g set the channel availability timer to T оc c when receiving CAI. Assume that Node s and Node g know T REF . Counter decrements all T REF . Node s and Node g expect the channel to become available when the timer reaches 0 CAI can be transmitted at the beginning of the slot to ensure that the channel is truly released when the counter is reset. However, CAI cannot always be transmitted at the beginning of the slot. In addition, to decode CAI considering propagation delay and receiver latency

[0121] Node s and Node g can start monitoring the channel after the timer reaches c ≥ 0. As a typical setting, c = 1 can be used

[0122] FIG. 9 shows a method for using a timer in a general node.

[0123] Furthermore, to enhance detectability and ensure that the CAI can be received even by UEs with different discontinuous reception (DRX) configurations, the CAI can be transmitted periodically or multiple times in a known pattern within the COT. The UE is not necessarily configured to receive all occasions of the CAI. Therefore, multiple instances increase the chance of receiving the CAI. An example where the CAI is transmitted in slot #0 and slot #5 of a frame is shown in FIG. 10. Both CAIs indicate the same T although T is decremented by 5 for each in slot #5, indicating that 5 slots have elapsed since the transmission of the CAI in slot #0. REL Although both indicate T оcc it is decremented by 5 in slot #5 indicating that 5 slots have elapsed since the transmission of the CAI in slot #0. This is shown.

[0124] It is also proposed herein that Node 1 can increase or decrease its intended occupancy time within its MCOT and indicate the update in a subsequent CAI. FIG. 11 shows an example where in the first CAI transmitted when the channel becomes available, T = 7 ms. оcc In the next CAI transmission, T is changed by incrementing T оcc by 2 m REL s via the updated T = 4 ms. For Node REL and Node s and Node g here the channel availability timer is set to T оcc when the first CAI is received and decremented for each slot (T ms). In this example, T REF is 1 millisecond per slot REF and... When the second CAI is received, the timer is started at T оcc =4ms new The counter is updated to the new value, then decremented until it reaches 1 or 0, at which point it Then, the node s and node g attempts channel access.

[0125] In general, this method can be applied when a new CAI is received from any cell. That is, when a node detects a new CAI, it starts the channel availability timer Value T оcc Update to the latest value of T REF Starts the timer decrement every ms .

[0126] (UL transmission within gNB MCOT) For example, if a transmitter such as a gNB occupies a channel, that transmitter Tatter is his T оcc is shown in the CAI, thereby providing the value of Equation 3 below. However, T оcc During this period, the UE may be able to transmit on the UL. The UE then notifies other UEs that may also be attempting to access the channel. The gNB sends a UL CAI to indicate in-network operation or requests a response. In this case, the UL CAI may transmit CAI-R. , that T оcc is expressed as the time up to the following formula 3, not as the period of channel occupation. It is proposed to do so.

[0127]

number

[0128] In the example shown in FIG. 12, the UL transmission from UE1 is only for one slot, but the UL CAI is T оcc = 2 ms, and thus, the channel availability timers at Node s and Node g are decremented based on Equation 3 and are not affected by UL CAI.

[0129] In this specification, it is proposed that the UE can obtain T REL from DL CAI or CAI-I, or the UE can obtain the explicit value of Equation 3 through permission.

[0130] (CAI Using Omnidirectional and Spatial LBT) When omnidirectional LBT is performed, the channel can be accessed with multiple beams simultaneously. In this specification, the nodes can have different T оcc for each beam, but it is proposed that the MCO T is the same for all beams. CAI can be transmitted on multiple beams to indicate the occupancy of the channel including the T оcc of each beam. However, if all beams have the same T , only one field may be required to indicate the T оcc of all beams. оcc

[0131] When spatial LBT is performed, the gNB may have different T REL for different beams. Also in this case, CAI can carry the information of the T of each beam. Thus, a receiver that receives one of the CAIs does not need to detect the CAIs on other beams and оcc knows the network occupancy in multiple spatial directions. This reduces the computational overhead. ​​​​​​​Can be clearly saved. The spatial direction is shown as spatial QCL for one of the signals in PBCH DMRS in DRS or specific CSI -RS, etc., which can be shown for one of the signals in DRS or SSB Figure 13 shows an example where the gNB accesses the channel with beams B1 and B2. However However, T оcc differs depending on the beam. The CAIs transmitted with B1 and B2 show the values for both beams Also, the CAI of some beams is CAI-I and carries the trigger for the handshake while the CAI of other beams does not carry the trigger and only indicates channel occupancy in some cases Also, it may be necessary for the gNB to sweep the beams to transmit the CAI, and at the same time even if the gNB accesses the channel with those beams, the position of the CAI may be different depending on the beam is different

[0132] Information carried by CAI

[0133] · CAI can carry the following information · The field cellID that may be related to the NCellID of the gNB. This is 10 bits and may be exactly the same as the N CellID. Alternatively, it may have fewer bits obtained by operations such as the following Equation 4. However, L may be a power of 2 such as 64 or 128, and this can reduce the overhead while enabling discrimination between different cells CellID helps the listening node identify the cell that is occupying the channel · The transmitter ID field transmitterID of T bits · When the gNB (TRP in the network) is transmitting, the T bit can be set to a value (the following Equation 5) in one of the following ways · A fixed value common to the entire NR-U network​​ ·Cell-specific value provided during SI of the cell. ·T = 0. If the field may not exist, it is implicitly indicated that it is from the gNB. To implicitly indicate this. ·When the UE is transmitting, the T bit is set to a value (Equation 6 below) based on its ID. The ID is of the type such as C-RNTI or Configured Scheduling RNTI ( Configured Scheduling RNTI: CS-RNTI), or may be part of the C-RNTI or CS-RNTI configured by the connected network. . ·The receiver ID field receiverID of the R bit. However, R may be equal to T. There is a possibility. ·When the gNB (TRP within the network) is receiving, the R bit can be set to a value (Equation 7 below) in one of the following ways. ·A fixed value common to all NR-U networks ·Cell-specific value provided during SI of the cell. ·T = 0. If the field may not exist, it is implicitly indicated that it is from the gNB. To implicitly indicate this. . ·When the UE is receiving, the value is set based on the receiver ID such as C-RNTI or CS-RNTI, or part of C- RNTI or CS-RNTI, (Equation 8 below ). ·The 1-bit field responseIndicator can indicate whether the CAI requests CAI-R in the response from the receiver (when set to 1), or whether the CAI does not request CAI-R in the response from the receiver (when set to 0). ·CAI-I is a P-bit field to indicate the resources for transmitting CAI-R. It is possible to carry RUD resource CAIR. · CAI-I can carry the U-bit field triggeredUEID to indicate the ID of the UE that needs to respond with CAI-R. · CAI-R can carry the E-bit field detEnergy to indicate the energy detected during the LBT period preceding CAI-R. By assigning pre-defined thresholds for different energy levels, the number of bits E can be kept small. Knowledge of the energy detected by the responding node helps the initiating node, such as a gNB, to evaluate the environment on the response side. Thus, the initiating node can set the threshold level for LBT at the responding node.

[0134]

Number

[0135]

Number

[0136]

Number

[0137]

Number

[0138]

Number

[0139] The following fields can be defined for each of the numBeams that carry information in the CAI. For omnidirectional LBT, numBeams = 1. Therefore, a single instance is used for the following fields. For spatial LBT, numBeams can be defined according to the specifications of different unlicensed bands for FR1 and FR2, or can be configured during the SI of the cell. numBeams can be set to the number of SSBs within the cell. Instances within the payload can be arranged in ascending order of the SSB index. · Field intendedChannelOccTime. The intended channel occupancy time T represented by D bits ms. This can be expressed in the form of the number of slots of the reference numerology, such as 15 kHz for FR1 and 120 kHz for FR2. · Field mcotTransmitter indicating the MCOT of T ms. This is given in M bits such that T ≤ T · Field freqResourceMCOT indicates the frequency resources of the frequency domain for accessing the channel. This enables the listening node to access channels outside the specified frequency band. In general, since the CAI is signaled for different purposes (e.g., for occupancy time, use within the network, or to indicate a handshake), it may carry different fields and different amounts of information depending on the use case. оcc MCOT

[0140] OCC MCOT

[0141] The CAI on one cell can indicate channel occupancy on other aggregated NR-U cells.

[0140]

[0141]

[0141] For example, an NR-U PCell / primary / secondary cell (PSCell) may indicate its own CAI along with other aggregated NR-U cells.

[0142] PUSCH start position candidates

[0143] The execution of LBT before UL PUSCH imposes uncertainty on when the UE can access the channel. Therefore, allowing the UE to be able to have multiple start positions within one or more slots is beneficial for dealing with channel uncertainty.

[0144] To support variable start positions of PUSCH, the following two aspects need to be considered. a. Signaling of PUSCH start position candidates: The load on the gNB for detecting the start position needs to be minimized. To simplify the hardware requirements for detecting PUSCH, the gNB can limit the number of start positions of the first PUSCH transmission from the UE within the UE's COT. b. UL channel access indication by the UE: Indication of the start position by the UE. The UE can indicate the selected start position of its first PUSCH transmission within its COT from the set of permitted start positions. Therefore, UL CAI can be transmitted on the UL by the UE to indicate the intended channel occupancy time. The UL CAI can be explicitly indicated via a new signal such as an RS or a preamble sequence, or implicitly indicated via an existing signal such as the DMRS of PUSCH. The gNB recognizes the start position of the UE's PUSCH by detecting the UL CAI. For example, DMRS If the presence of can clearly indicate the start position, the gNB can detect the start position of the UE's PUSCH by detecting and processing the UE's DMRS (auto-correlation or cross-correlation). Otherwise, the gNB can detect it through energy detection for each received PUSCH symbol.

[0145] Signaling of PUSCH start position candidates

[0146] The gNB can potentially detect the presence of PUSCH transmission by detecting the DMRS signal from the UE. However, the gNB needs to determine the start of PUSCH transmission that may change according to the UE's channel access. The gNB can blindly decode the PUSCH for all [[ID=1ó]]candidate PUSCH start OSs. For example, assume that UL grants are given for 14 OS slots. However, the UE can only access the channel from OS #2 and punctures the PUSCHs of OS #0 and OS #1. Next, the gNB receives the transmission and decodes it assuming that the PUSCH starts at OS #0. If it fails, it decodes it at PUSCH start position OS #1. If it fails again, it decodes it at PUSCH start position OS #2 and continues this until the decoding of the PUSCH is successful. If the decoding fails, it assumes that it starts at OS #0 of the slot, buffers the PUSCH, and schedules a retransmission of the PUSCH. Assuming that the retransmission is received in its entirety, the gNB can decode it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and decodes it #2 from which only the channel is accessible and punctures the PUSCHs of OS #0 and OS #1. Next, the gNB receives the transmission and decodes it assuming that the PUSCH starts at OS #0. If it fails, it decodes it at PUSCH start position OS #1. If it fails again, and decodes it assuming that the PUSCH starts at OS #2 and continues this until the decoding of the PUSCH is successful. If the decoding fails, it assumes that it starts at OS #0 of the slot, buffers the PUSCH, and schedules a retransmission of the PUSCH. Assuming that the retransmission is received in its entirety, the gNB can decode it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and decodes it, and if it fails, decodes it at PUSCH start position OS #2 and continues this until the decoding of the PUSCH is successful. If the decoding fails, it buffers the PUSCH assuming that it started at OS #0 of the slot and schedules a retransmission of the PUSCH. Assuming that the retransmission is received in its entirety, the gNB can decode it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and decodes it, and if it fails, decodes it at PUSCH start position OS #2 and continues this until the decoding of the PUSCH is successful. If the decoding fails, it buffers the PUSCH assuming that it started at OS #0 of the slot and schedules a retransmission of the PUSCH. Assuming that the retransmission is received in its entirety, the gNB can decode it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and continues this until the decoding of the PUSCH is successful. If the decoding fails, it buffers the PUSCH assuming that it started at OS #0 of the slot and schedules a retransmission of the PUSCH. Assuming that the retransmission is received in its entirety, the gNB can decode it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and decodes it, and if it fails, decodes it at PUSCH start position OS #2 and continues this until the decoding of the PUSCH is successful. If the decoding fails, it buffers the PUSCH assuming that it started at OS #0 of the slot and schedules a retransmission of the PUSCH. Assuming that the retransmission is received in its entirety, the gNB can decode it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and decodes it by Chase combining assuming that the original transmission started at OS #0. If it fails, it assumes that the original transmission started at OS #1 and decodes it , assume that if decoding fails with Chase combining, the original transmission started at OS#2, decode with Chase combining, and if this attempt is successful, stop. This blind decoding procedure may lead to a very significant complication of the gNB's hardware.

[0147] Also, to minimize blind decoding, it can be seen that it is advantageous to enable the gNB to know the start position of the PUSCH. If information becomes available at the time of the PUSCH transmission itself via signals such as the CAI transmitted at the start of the PUSCH, the gNB can avoid blind decoding while processing the retransmission via Chase combining. However, even if the gNB cannot utilize the CAI during the processing of the PUSCH, if the CAI information can be transmitted to the gNB before the scheduled retransmission, it becomes possible for the gNB to reduce blind decoding during the retransmission process. According to one aspect, the UE can transmit its channel access information via the preamble or UCI. This can indicate the time when the COT started and can also indicate when the UE's COT ends. The gNB recognizes the start position of the PUSCH based on this and identifies the symbols punctured in the original transmission before Chase combining with the retransmission is performed. This concept is shown in FIG. 48, where the start of the COT is indicated by the UE via the UCI on the PUSCH. This occurs after the first PUSCH transmission started at OS#2 ends. ends.

[0148] To keep the overhead of blind decoding at the gNB within an acceptable range, the UE can be restricted to transmit the PUSCH starting from a specific start position. Disclosed in this specification In the method, the gNB can transmit a plurality of DCIs similar to DCI format, format 0_0 or 0_1, to provide the UE with a plurality of starting positions of PUSCH having all parameters related to different PUSCH starting positions, such as UL DMRS configuration, MCS, Transmission Power Control (TPC), etc. For this purpose, the gNB can use the same value of New Data Indicator (NDI) and Redundancy Version (RV) across a plurality of DCIs, but for example, fields such as time domain resource allocation, MCS, TPC, etc. can be adjusted. In this case, the UE can interpret the reception of a plurality of UL authorizations with the same NDI value and RV value as an alternative, and the UE can also use only one of the UL authorizations based on the result of LBT on the UE side and ignore other UL authorizations. To provide the UE with sufficient processing time to prepare the PUSCH based on the starting position, the previous DCI can be associated with the UL authorization at the previous starting position. For example, FIG. 21G shows three DCIs providing different PUSCH starting positions, and the UE can expand only one of them based on the LBT result on the UE side. Or, for example, as shown in FIG. 22, all DCIs can be transmitted in the same CORESET. These DCIs carry the same NDI and RV, indicating that the provided UL authorizations are mutually alternative, and the UE can select only one authorization and ignore the other provided authorizations. The UE first provides the largest amount of resources, and then the second largest amount of resources. [[ID=I7]]

[0149] ​​​​​​​​​​​​​​​UL approval such as providing can be used.

[0150] For example, within the DCI of a 1-bit sized field called the DCI repetition flag The new field can carry the same RV and NDI with the repetition flag set to 1 All DCIs can indicate that they are mutually replaceable, and the UE can choose to use the approval provided by only one of these DCIs. On the other hand, when the repetition flag is set to zero, one DCI may overwrite another DCI. Here, the UE does not select which DCI to use, and the gNB determines which DCI can be used according to, for example, the following rules. · The DCI transmitted in a later CORESET can overwrite the DCI transmitted in the previous CORESET, and · When multiple DCIs are transmitted in the same CORESET, the DCI transmitted in the lowest physical resource block (Physical Resource Block: PRB) can overwrite the DCI transmitted in a higher PRB.

[0151] According to another aspect, a single DCI may provide multiple starting positions. For example, the cyclic redundancy check (CRC) scrambled by C-RNTI (any other RNTI can be used whenever applicable) can be used to transmit the following information in this DCI. · The number of starting positions indicating the number of PUSCH starting position candidates available to the UE according to the result of LBT. The size of this field is a higher layer parameter, for example, called maxNumStartPosit ​​​It can be defined by the RRC parameters to be obtained. · Or / And, for each start position candidate, use dedicated time domain resource allocation to signal the start position for each PUSCH start position candidate. The bit width of this field is determined as log2(I) bits. However, as shown in the aforementioned field, I is the product of the number of entries in the upper layer parameter pusch-TimeDomainAllocationList and the number of start positions. · Or / And, the MCS field for each start position candidate. The bit width of this field is the product of the number of start positions shown in the aforementioned field and the number of bits required to carry the MCS for each start position separately. · Or / And, NDI and RV can be the same for all PUSCH start position candidates and possible. · The antenna port field for each PUSCH start position candidate.

[0152] To reduce the overhead of transmitting a plurality of DCIs indicating different start positions of the PUSCH the UE may select one of a plurality of position candidates given by an upper layer parameter, for example, the RRC parameter named PUSCH-start-Positions-set beforehand. The set position candidates may be relative to the slot or relative to the scheduled PUSCH . If PUSCH-start-Positions-set is relative to the slot the UE can select one start position candidate from the start position candidates that overlap with the original PUSCH grant. Figure 23 shows a plurality of phases for the slot of symbols {0, 2, 5, 8, 10} and An example of a PUSCH-start-Positions-set that provides symmetric PUSCH start positions is shown. In this example the PUSCH is scheduled to start from OS4. The PUSCH start position may be the start position of the UL grant as indicated by the DCI, or it may overlap with the grant and be one of the symbol candidates {5, 8, 10} for the start position according to the result of LBT on the UE side.

[0153] Alternatively, the start position candidates may be given relative to the original start position of the PUSCH given in the UL grant by upper layer parameters such as the RRC parameter PUSCH-start-Positions-set. In other words, the actual symbol index of the start position candidates is given by the PUSCH-start-Positions-set after shifting them relatively to the index of the first symbol in the UL grant. If some of the actual symbol indices of the start position candidates exceed the end position of the scheduled PUSCH the UE can ignore those position candidates. In the example shown as an illustration in Figure 24, PUSCH-start- Positions-set = {2, 5, 7} and the original start position provided by the UL grant is the 4th symbol. Therefore, the actual start position candidates are {6, 9, 11} and the UE will attempt to access the channel at one of these positions based on the LBT result. Furthermore, to avoid signaling of the start position candidates, they can be defined according to some rules regarding either the slot boundary

[0154] or the PUSCH grant itself. ​​​For example, all even / odd symbols can be potential starting points. The starting position candidates are all symbols after the first symbol in the licensed PUSCH or slot. All L symbols can follow a certain pattern, e.g., L = 1 means one This means that every other symbol is a candidate for the starting position. The value of L is the authorization period, M It may depend on some parameters in the PUSCH grant, such as CS. For example, if L is When dependent on the MCS, L is given by Table 3.

[0155] [Table 3]

[0156] In Table 3, I MCS is the MCS given the DCI providing the PUSCH grant, {}Equation 9 below is used to determine the higher layer parameters such as the RRC parameter PUSCH-start-Positions-th. The higher layer parameters may be provided by the MCS thresholds for any row. If it shows that, i.e., MCS th_(i-1) = MCS th_i In this case, these MCS thresholds The L in the associated line where both the L and the L appear is invalid.

[0157]

number

[0158] Table 4 shows the number of starting positions and their corresponding scheduled PUSCH periods. In this example, if the duration of the PUSCH grant is less than or equal to 3 symbols, L can be set to zero to allow the UE to attempt to access the channel at each symbol. It can be shown. When the period of PUSCH grant is 4 symbols, L can be set to 1. This means, for example, that the UE can attempt to access the channel every other symbol. The value of L for different PUSCH grant periods can be given by a higher layer parameter.

[0159] [Table 4]

[0160] Applying other mathematical rules, the index (L) that satisfies L mod M = 0 can also be defined for the index of candidate start positions such as OFDM symbols. However, M can depend on some of the original PUSCH grant parameters, for example, MCS, grant period in symbol units, etc. To establish the functional dependency of M on any of the original PUSCH grant parameters, for example, a table similar to Table 3 can be used. When any of the aforementioned rules is applied with respect to the slot boundary, the UE may consider only the candidate start positions that overlap with the UL grant. For example,

[0161] In another aspect, it is possible to combine explicitly indicating (using higher layer parameters) the candidate start positions and implicitly indicating (according to the specified rules). For example, the candidate start positions can be the union of the explicitly and implicitly given positions. Further, when there is no explicit indication of the candidate start positions, the UE can apply the use of the implicit indication. For example,

[0162] Extending at least one of the aforementioned solutions and any possible combinations thereof, through a single or multiple UL grants, multiple scheduled adjacent or non - adjacent PUSCs ​​​​​​​​​It is understood that possible starting position candidates for H can be provided to the UE. As a possible solution, R RC parameters can provide the positions of the starting position candidates to the UE. These positions can be relative to the scheduled PUSCH, or relative to the slot boundary. Next, the UE can consider only the positions that overlap with the scheduled PUSCH.

[0163] In the example shown in Figure 50A, the starting position candidates are configured as shifts from the first OFDM symbol in each scheduled PUSCH, and the shift values can be indicated by upper layer signaling such as RRC parameters. As shown in Figure 50A, the shift values can depend on the PUSCH index. For example, in PUSCHk, the starting position candidate is delimited by S where k is the index of the PUSCH. The UE can receive an indication via upper layer signaling using the shift values of adjacent PUSCHs. For example, a set of shift levels can be indicated to the UE, such as {a, b, c, d, ...}. Next, the UE can set S0 = a for PUSCH0, S1 = b for PUSCH1, and so on. Alternatively, the UE can be indicated via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. It can be, for example, a function of the PUSCH index. In Figure 50A, the shift value can depend on the PUSCH index. For example, in PUSCHk, the starting position candidate is delimited by S where k is the index of the PUSCH. The UE can receive an indication via upper layer signaling using the shift values of adjacent PUSCHs. For example, a set of shift levels can be indicated to the UE, such as {a, b, c, d, ...}. Next, the UE can set S0 = a for PUSCH0, S1 = b for PUSCH1, and so on. Alternatively, the UE can be indicated via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. It can be, for example, a function of the PUSCH index. k separated where k is the index of the PUSCH. The UE can receive an indication via upper layer signaling using the shift values of adjacent PUSCHs. For example, a set of shift levels can be indicated to the UE, such as {a, b, c, d, ...}. Next, the UE can set S0 = a for PUSCH0, S1 = b for PUSCH1, and so on. Alternatively, the UE can be indicated via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. It can be, for example, a function of the PUSCH index. values of adjacent PUSCHs. For example, a set of shift levels can be indicated to the UE, such as {a, b, c, d, ...}. Next, the UE can set S0 = a for PUSCH0, S1 = b for PUSCH1, and so on. Alternatively, the UE can be indicated via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. It can be, for example, a function of the PUSCH index. levels can be indicated to the UE, such as {a, b, c, d, ...}. Next, the UE can set S0 = a for PUSCH0, S1 = b for PUSCH1, and so on. Alternatively, the UE can be indicated via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. It can be, for example, a function of the PUSCH index. The UE can set it as S0 = a for PUSCH0, S1 = b for PUSCH1, and so on. Alternatively, the UE can be signaled via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. It can be signaled to the UE via upper layer signaling with a single parameter that it can use that parameter to derive the positions of the starting position candidates for each PUSCH. parameter to derive the positions of the starting position candidates for each PUSCH. It can be, for example, a function of the PUSCH index.

[0164] Alternatively, the PUSCH starting position candidates can be, for example, as shown in Figure 50B, first scheduled the shift S when starting from the first OFDM symbol in the scheduled PUSCH can be separated. Other rules can also be applied to define the position of the starting position candidate In addition to what is indicated by the upper layer signaling, the UE can also treat the first OFDM symbol of each PUSC H as a starting position candidate

[0165] Figure 50C illustrates the case where the starting position candidate is defined relative to the slot boundary The number and position of the starting position candidates may be the same between slots or different for each slot The upper layer signaling can indicate these positions. In addition to the first OFDM symbol of each PUS CH, the UE can consider the starting position candidates that overlap with any scheduled PUSCH as valid starting position candidates for the UE to attempt access to the channel, while the other starting positions outside the scheduled PUSCH can be considered invalid, and the UE may not attempt access to the channel at those positions The upper layer can indicate the index of the OFDM symbol of each slot that the UE can use as a starting position candidate. For example, a 14-bit size bit map can indicate which OFDM symbol can be used as a starting position candidate when the corresponding bit is set to 1 Furthermore, each slot within the subframe / radio frame can have a different position with respect to the starting position candidate, and the concatenated bitmaps of each slot signaled to the UE, and the position of the starting position candidate are repeated for each subframe or radio frame. Also, the gNB can group a set of slots or radio frame. Also, the gNB can group a set of slots or radio frame. Also, the gNB can group a set of slots or radio frame. Also, the gNB can group a set of slots or radio frame. Also, the gNB can group a set of slots A pattern where one group has specific start position candidates and other groups have different position candidates can be defined over a specific number of slots. This pattern can be applied repeatedly For example, FIG. 50D shows a pattern P = 101 over three slots. In this pa tern, there are four start position candidates in the slot corresponding to 1 and two start position candidates in the slot corresponding to 0. This pattern is repeated every three slots.

[0166] The gNB can semi - statically indicate a specific set of start position candidate configurations so that the gNB can flexibly adjust these configurations. For example, the gNB can provide the UE with multiple upper layer configurations indicating different sets of start position candidate arrangements. Then, the gNB can use a MAC control element (MAC Control Element: MAC - CE) to select the appropriate configuration by indicating the upper layer message ID carrying these configurations.

[0167] Furthermore, the gNB can dynamically indicate an appropriate configuration of start position candidates, for example, a bit field of length equal to log2(k), by using DCI. However, k is the number of configurations indicated via upper layer signaling. This bit field can be indicated either in the DCI carrying the grant or within the UE - specific search space or within an individual DCI in the group - common search space using an appropriate RNTI. Additionally, the gNB can signal a subset of start position candidates to the UE using MAC - CE and then the gNB can use DCI to indicate the selected configuration of start position candidates.

[0168] UL Channel Access Indication by UE

[0169] Adjustment of DMRS Scheduling Based on PUSCH Start Position

[0170] For PUSCH mapping type A, the position of the DMRS symbol is defined relative to the slot boundary Accordingly, if the UE fails to acquire the channel according to the scheduled / configured grant, ambiguous behavior may occur. For example, as shown in FIGS. 21 and 22, when multiple start positions are provided by dedicated DCI, i.e., when the DCI is mapped one-to-one to individual PUSCH start positions, each DCI can carry appropriate DMRS scheduling information combined with the DMRS RRC configuration corresponding to the PUSCH start position. However, this may involve a large overhead from the perspective of signaling for decoding multiple DCIs for the same grant and the UE's power consumption. Therefore, to reduce such a load, it may be beneficial to explicitly (using upper layer parameters) or implicitly (according to the specified rules) signal the start position candidates rather than using multiple DCIs. However, such a static configuration may not be appropriate for adjusting the DMRS scheduling based on the PUSCH start position selected by the UE. Next, some embodiments for dealing with such problems will be described For single UE MIMO (Single User MIMO: SU-MIMO ), several alternatives can be adopted ). ), several alternatives can be adopted ). ), several alternatives can be adopted ). Next, some embodiments for dealing with such problems will be described ).

[0171] For single UE MIMO (Single User MIMO: SU-MIMO ), several alternatives can be adopted

[0172] PUSCH start before l0

[0173] If the UE is in a position before the channel l0 given by the higher layer parameter dmrs-TypeA-Position, For accessing the LTE network (3GPP TS 36.211, Physical Channels and Modulation (Released) V15.3.0 (3GPP TS 36.211, Physical channels and modulati on (Release 15), V15.3.0)), the D of the PUSCH selected by the UE as the starting position The MRS symbol and its new duration are compared with the DMRS symbol of the PUSCH with the old duration. As long as the UL DMRS is the same, the UE can deploy the configured and scheduled UL DMRS. For example, the PUSCH period can be equal to 10, 11, or 12 OFDM symbols. In this case, the DMRS occupies symbols 10, 9 as shown in Table 5 (3GPP TS 36 .211, Physical Channels and Modulation (Release 15), see V15.3.0).

[0174] [Table 5]

[0175] Figure 25 shows 12 UL DMRS symbols, OS0 to OS11, with one additional UL DMRS symbol. Transmission over an OFDM symbol is scheduled, but the UE fails the LBT. This figure shows an example of PUSCH where access to the channel fails due to the location candidate, OS1 When a channel starting from OS2 becomes available, the UE selects the P The USCH periods are 11 and 10 respectively. Therefore, the UE continues to use the same schedule. Modulated DMRS can be used.

[0176] When using a DMRS configuration in which the PUSCH period from the start position selected by the UE is different from the original PUSCH period, the UE can follow the new DMRS configuration associated with the new PUSCH period with the same number of additional DMRS symbols. In the example shown in Figure 26, the PUSCH is scheduled for a period of 10 symbols from OS0 to OS9 initially, and one additional UL DMRS symbol is added, but the UE cannot access the channel at OS0. However, when the UE accesses the channel at OS1 or OS2, the PUSCH periods at the start positions selected by the UE are 9 and 8 respectively. Therefore, the UE can use the new DMRS configuration associated with the OFDM symbols of PUSCH periods 8 and 9 without using the old DMRS configuration associated with the original PUSCH grant. In this case, as shown in the figure, the DMRS needs to be at OS10, 7. When using a DMRS configuration in which the PUSCH period from the start position selected by the UE is different from the original PUSCH period, the UE can follow the new DMRS configuration associated with the new PUSCH period with the same number of additional DMRS symbols. In the example shown in Figure 26, the PUSCH is scheduled for a period of 10 symbols from OS0 to OS9 initially, and one additional UL DMRS symbol is added, but the UE cannot access the channel at OS0. However, when the UE accesses the channel at OS1 or OS2, the PUSCH periods at the start positions selected by the UE are 9 and 8 respectively. Therefore, the UE can use the new DMRS configuration associated with the OFDM symbols of PUSCH periods 8 and 9 without using the old DMRS configuration associated with the original PUSCH grant. In this case, as shown in the figure, the DMRS needs to be at OS10, 7. When the UE accesses the channel starting from symbol 10 given by the upper layer parameter dmrs-TypeA-Position or later, it can be assumed that the PUSCH mapping type A in which the DMRS is mapped relative to the slot boundary is effectively changed to the PUSCH mapping type B in which the DMRS is mapped relative to the PUSCH based on the new PUSCH period. In other words, the UE sets 10 to zero, and the new PUSCH period and the upper layer parameter dmrs-additionalPoist When using a DMRS configuration in which the PUSCH period from the start position selected by the UE is different from the original PUSCH period, the UE can follow the new DMRS configuration associated with the new PUSCH period with the same number of additional DMRS symbols. In the example shown in Figure 26, the PUSCH is scheduled for a period of 10 symbols from OS0 to OS9 initially, and one additional UL DMRS symbol is added, but the UE cannot access the channel at OS0.

[0177] PUSCH start from 10 or later

[0178] When the UE accesses the channel starting from symbol 10 given by the upper layer parameter dmrs-TypeA-Position or later, the UE can assume that the PUSCH mapping type A in which the DMRS is mapped relative to the slot boundary is effectively changed to the PUSCH mapping type B in which the DMRS is mapped relative to the PUSCH based on the new PUSCH period. In other words, the UE sets 10 to zero, and the new PUSCH period and the upper layer parameter dmrs-additionalPoist When the UE accesses the channel starting from symbol 10 given by the upper layer parameter dmrs-TypeA-Position or later, the PUSCH mapping type A in which the DMRS is mapped relative to the slot boundary is effectively changed to the PUSCH mapping type B in which the DMRS is mapped relative to the PUSCH based on the new PUSCH period. When the UE accesses the channel starting from symbol 10 given by the upper layer parameter dmrs-TypeA-Position or later, the PUSCH mapping type A in which the DMRS is mapped relative to the slot boundary is effectively changed to the PUSCH mapping type B in which the DMRS is mapped relative to the PUSCH based on the new PUSCH period. In other words, the UE can set 10 to zero, and the new PUSCH period and the upper layer parameter dmrs-additionalPoist When the UE accesses the channel starting from symbol 10 given by the upper layer parameter dmrs-TypeA-Position or later, the PUSCH mapping type A in which the DMRS is mapped relative to the slot boundary is effectively changed to the PUSCH mapping type B in which the DMRS is mapped relative to the PUSCH based on the new PUSCH period. Map the DMRS according to the additional number of DMRS symbols given by the ion This is possible. Figure 27 shows the transmission via 12 OFDM symbols from OS0 to OS1 with one additional UL DMRS symbol scheduled, but an example of a PUSCH that fails to access the channel because the UE fails in LBT is shown. At the position shown in the figure candidate, that is, when the channel starting from OS5 becomes available, the period of the PUSCH according to the start position selected by the UE is 7 OFDM symbols. In this case, as shown in the figure and Table 6 the UE can map the UL DMRS according to the new 7OS PUSCH period, which is relative to the start of the PUSCH and is l0 and 4 according to mapping type B This is possible

[0179]

Table 6

[0180] As another example, Figure 28 shows a PUSCH that fails to access the channel because the transmission via 12 OFDM symbols from OS0 to OS 11 with one additional UL DMRS symbol is scheduled, but the UE fails in LB T. In this example, the UE accesses the channel starting from OS7, and the period of the PUSCH from the start position selected by the UE is 4 OFDM symbols, but there is only one symbol carrying the DMRS and no additional DMRS positions In the examples so far, these aspects have been shown for a single-symbol DMRS with one additional DMRS position, but these aspects apply to a single

[0181] with any number of additional DMRS positions with any number of additional DMRS positions It is further applicable to a single-symbol DMRS and has double with any number of additional DMRS positions It is also applicable to a symbol DMRS.

[0182] FIG. 29 shows a procedure for adjusting the DMRS configuration according to the PUSCH start position candidate An example is shown. In the example of FIG. 29, first, the gNB sends a request for allocation of PUSCH mapping type A and schedules the corresponding DMRS based on the PUSCH period. Next, the UE attempts access to the channel to start the PUSCH from the first scheduled OS. If the channel is available, the procedure ends. If the channel is not available, the UE attempts access to the channel at a new start position. To access the channel before Io, the UE selects the UL DMRS configuration according to the PUSCH mapping type A and the new period of the PUSCH, but the configuration of the scheduled DMRS is the same in terms of the DMRS type (1 or 2), the number of additional DMRS positions, and single or double DMRS symbols. To access the channel at or after Io, the UE selects the UL DMRS configuration according to the PUSCH mapping type B and the new period of the PUSCH, but the configuration of the scheduled DMRS is the same in terms of the DMRS type (1 or 2), the number of additional DMRS positions, and single or double DMRS symbols. In either case, the UE transmits the PUSCH with the new DMRS configuration. In the case of multi-user MIMO (Multi-User MIMO: MU-MIMO), that is, other UL DMRS configurations are selected according to the new period of the PUSCH mapping type A and the PUSCH, but the configuration of the scheduled DMRS is the same in terms of the DMRS type (1 or 2), the number of additional DMRS positions, and single or double DMRS symbols. To access the channel at or after Io, the UE selects the UL DMRS configuration according to the PUSCH mapping type B and the new period of the PUSCH, but the configuration of the scheduled DMRS is the same in terms of the DMRS type (1 or 2), the number of additional DMRS positions, and single or double DMRS symbols. In either case, the UE transmits the PUSCH with the new DMRS configuration. In the case of multi-user MIMO (Multi-User MIMO: MU-MIMO), that is, other UL DMRS configurations are selected according to the new period of the PUSCH mapping type A and the PUSCH, but the configuration of the scheduled DMRS is the same in terms of the DMRS type (1 or 2), the number of additional DMRS positions, and single or double DMRS symbols. In either case, the UE transmits the PUSCH with the new DMRS configuration. transmits.

[0183] In the case of multi-user MIMO (Multi-User MIMO: MU-MIMO), that is, other If the DMRS of the UE shares the same code division multiplexing (CDM) group with different OCC sequences or uses orthogonal frequency resources, it is more difficult because the UE shares the same PUSCH resources. Therefore, by shifting the DMRS of a certain UE that is independent of the DMRS of other UEs, significant interference may occur between different antenna ports used by different UEs. To address such problems, several alternatives can be adopted as described below. le:CDM) group or is using orthogonal frequency resources, it is more difficult because the UE is sharing the same PUSCH resources. Therefore, by shifting the DMRS of a certain UE that is independent of the DMRS of other UEs, significant interference may occur between different antenna ports used by different UEs. To address such problems, several alternatives can be adopted as described below. To address such problems, several alternatives can be adopted as described below.

[0184] As long as the UL DMRS symbol of the PUSCH from the start position selected by the UE occupies the same symbol that carries the UL DMRS of the old PUSC H or some of those symbols, the UE can change the PUSCH start position. For example, in the case of PUSCH mapping type A with a single-symbol DMRS having three additional DMRS positions, if the PUS CH period is 12, 13, or 14, the DMRS occupies the same symbols l0, 5, 8, 11 . Therefore, if the original PUSCH recognition period is 14 symbols and three additional D MRS are configured as shown in, for example, Figure 30, UE1 can attempt to access the channel starting from OS1 or 2 , and the periods of the PUSCH from the start position selected by the UE become equal to 13 and 12 symbols, respectively. For both PUSC H start positions, the UL DMRS can occupy the same symbols as the UL DMRS of the first scheduled PUSCH. In such a case, even after changing the start position of the PUSCH of UE1, the DMRS of UE1 and UE2 are orthogonal. H start positions, the UL DMRS can occupy the same symbols as the UL DMRS of the first scheduled PUSCH. In such a case, even after changing the start position of the PUSCH of UE1, the DMRS of UE1 and UE2 are orthogonal. After changing the start position of the PUSCH of UE1, the DMRS of UE1 and UE2 are orthogonal.

[0185] This is not always the case, i.e., the UL DMRS may not always be the same as the UE selected development The same symbol is used for the PUSCH from the start position and the first scheduled PUSCH. Therefore, according to another aspect, the UL D of the PUSCH with a new period is The symbol index set S of the OFDM symbols carrying the MRS new has an older period Symbol index set S carrying UL DMRS for PUSCH old To be selected from If the two sets are non-overlapping and S new Some of the indexes belonging to S old If they do not belong to S, then their indices are old to the closest index in Replaced. S old and transmits UL DMRS for PUSCH in the new period. Symbols not used for carrying data shall be used to avoid collisions between DMRSs of other UEs. Figure 31 shows 12 symbols, OS0 to OS11. 3. The example shows a PUSCH grant of duration equal to 1. The three additional DMRSs are allocated to That is, S old = {l0, 5, 8, 11}. or OS2, and the UE selects the PUSC from the selected starting position. If the duration of H is set to 11 and 10 respectively, unfortunately, the starting position selected by the UE During the PUSCH period from the position, the UL DMRS is new = {l0, 6, 9} This means that only 10 overlaps with the symbols carrying UE2's UL DMRS. Furthermore, the UE new 6 and 9 of Sold at the closest index of Replace with certain 5 and 8 respectively, to get S new = {l0, 5 6, 8 9}, which is possible. By doing so, the orthogonality between UE1 and UE2 is maintained.

[0186] Channel estimation from the last OFDM symbol of the last DMRS to the end of the PUSCH may significantly deteriorate. To avoid extrapolation of a large number of OFDM symbols, if multiple OFDM symbols are required to carry the PUSCH in a new period, the index of the last OFDM symbol of the PUSCH can be used in the old period. In the example where S = {l0, 5, 8, 11} and S old = {l0, 5, 8, 11} and S new = {l0, 6, 9}, the UE can replace 6 and 9 in S new with 5 and 11 respectively, as shown in Figure 32, to get S new = {l0, 5 6, 11 9}.

[0187] When PUSCH mapping type A is used, but the UE acquires the channel after l0, PUSCH mapping type B can be used to map the DMRS according to the period of the PUSCH starting from the starting position selected by the UE. If the index set S of the symbols carrying the UL DMRS of the new period PUSCH is different from the index set of the symbols carrying the UL DMRS of the old period PUSCH, each element of S new is replaced by the closest element of S . Figure 33 shows 12 symbols from OS0 to OS11 new o ld of An example of PUSCH grant for an equal period is shown. So that three additional DMRSs are occupied, i.e., it is configured such that S = {l0, 5, 8, 11}. If UE1 fails to access the channel starting from OS0 but succeeds in accessing the channel starting from OS7, i.e., starting after l0, the DMRS is mapped according to PUSCH mapping type B. Since the new period of PUSCH is 5 symbols, the UL DMRS can occupy the symbols indexed at l0, 4 relative to the PUSCH start position OS7. Therefore, S old = {7, 11}. Comparing S with S and replacing OS7 with OS8, the UE can set S = {8, 11}. When the UE accesses the channel at OS8, the new period of PUSCH is 5, and according to PUSCH mapping type B, the index of the symbol carrying the DMRS is l0 relative to the PUSCH, i.e., S = {8}. In this case, as shown in Figure 34, the last symbol S new cannot be used to carry the DMRS. new Replacing S old with S and comparing with U new E, the UE can replace OS7 with OS8 and set S

[0188] = {8, 11}. When the UE accesses the channel at OS8, the new period of PUSCH is 5, and according to PUSCH mapping type B, the index of the symbol carrying the DMRS is l0 relative to the PUSCH, i.e., S = {8}. In this case, as shown in Figure 34, the last symbol S new cannot be used to carry the DMRS. Furthermore, for example, as shown in Figure 51, the UE can shift the entire scheduled PUSCH to a new start position, and instead of simply starting PUSCH transmission from the new start position without shifting the entire PUSCH, the scheduled DMRS can be shifted relative to the new start position. Figure 52A shows one additional U old cannot be used to carry the DMRS.

[0189] Furthermore, for example, as shown in Figure 51, the UE can shift the entire scheduled PUSCH to a new start position, and instead of simply starting PUSCH transmission from the new start position without shifting the entire PUSCH, the scheduled DMRS can be shifted relative to the new start position. Figure 52A shows one additional U to a new start position, and instead of simply starting PUSCH transmission from the new start position without shifting the entire PUSCH, the scheduled DMRS can be shifted relative to the new start position. Figure 52A shows one additional U to a new start position, and instead of simply starting PUSCH transmission from the new start position without shifting the entire PUSCH, the scheduled DMRS can be shifted relative to the new start position. Figure 52A shows one additional U When the UE accesses the channel at OS8, the new period of PUSCH is 5, and according to PUSCH mapping type B, the index of the symbol carrying the DMRS is l0 relative to the PUSCH, i.e., S Transmission via 12 OFDM symbols from OS0 to OS11 with L DMRS symbols is scheduled, but an example of PUSCH that fails to access the channel due to the UE's failure in LBT is shown. When the indicated position candidates in the figure, i.e., the channel starting from OS2, become available, the PUSCH start position is shifted by 2 OFDM symbols. Next, the DMRS symbols are shifted by 2 OFDM symbols, and the new positions become OS5 and OS11. By shifting the entire PUSCH, the UE can puncture / rate-match the truncated symbols at the end of the licensed PUSCH. If, depending on the new start position, the new shifted position exceeds the end of the scheduled PUSCH, the UE can puncture one or more scheduled DMRS symbols. For example, FIG. 52B shows an example of a UE that transmits only one DMRS symbol instead of the first two scheduled DMRS symbols. The UE can transmit the DMRS symbol scheduled to be transmitted at OS3 at OS11. On the other hand, the DMRS scheduled to be transmitted at OS9 can be removed. The UE can be configured to transmit at least one DMRS symbol, for example, at the first OFDM symbol of the new PUSCH start position. This is the case when all of the scheduled DMRS symbols are shifted beyond the end of the scheduled PUSCH, i.e., when all of the scheduled DMRS symbols are removed. When the channel starting from OS2 as shown in the figure becomes available, the PUSCH start position is shifted by 2 OFDM symbols. Next, the DMRS symbols are shifted by 2 OFDM symbols, and the new positions become OS5 and OS11. By shifting the entire PUSCH, the UE can puncture / rate-match the truncated symbols at the end of the licensed PUSCH. Depending on the new start position, if the new shifted position exceeds the end of the scheduled PUSCH, the UE can puncture one or more scheduled DMRS symbols. For example, FIG. 52B shows an example of a UE that transmits only one DMRS symbol instead of the first two scheduled DMRS symbols.

[0190] The UE can transmit the DMRS symbol scheduled to be transmitted at OS3 at OS11. On the other hand, the DMRS scheduled to be transmitted at OS9 can be removed. The UE can be configured to transmit at least one DMRS symbol, for example, at the first OFDM symbol of the new PUSCH start position. This is the case when all of the scheduled DMRS symbols are shifted beyond the end of the scheduled PUSCH, i.e., when all of the scheduled DMRS symbols are removed. When the channel starting from OS2 as shown in the figure becomes available, the PUSCH start position is shifted by 2 OFDM symbols. Next, the DMRS symbols are shifted by 2 OFDM symbols, and the new positions become OS5 and OS11. By shifting the entire PUSCH, the UE can puncture / rate-match the truncated symbols at the end of the licensed PUSCH.

[0191] The UE can be configured to transmit at least one DMRS symbol, for example, at the first OFDM symbol of the new PUSCH start position. This is the case when all of the scheduled DMRS symbols are shifted beyond the end of the scheduled PUSCH, i.e., when all of the scheduled DMRS symbols are removed. If, depending on the new start position, the new shifted position exceeds the end of the scheduled PUSCH, the UE can puncture one or more scheduled DMRS symbols. For example, FIG. 52B shows an example of a UE that transmits only one DMRS symbol instead of the first two scheduled DMRS symbols. is beneficial. As a result of the PUSCH being shifted, if any of the scheduled DMRS symbols cannot be transmitted, the upper layer signaling can indicate the minimum number of DMRS symbols and their positions, etc. Further, if the remaining number of OFDM symbols for carrying the PUSCH is less than a specific threshold, the UE can be configured not to transmit this PUSCH because the probability that this PUSCH can be successfully decoded is the highest. Such a threshold can be indicated to the UE by upper layer signaling.

[0192] The PUSCH is not allowed to cross the slot boundary. When the UE is scheduled with a plurality of adjacent PUSCHs, each scheduled PUSCH may not be shifted to start beyond the end of the slot containing the original scheduled PUSCH. For example, FIG. 53A shows an example of N PUSCHs scheduled by the UE, and three start position candidates are shown for PUSCH0. Next, based on the channel availability, PUSCH0 can be shifted to start from any of the shown start position candidates. If the channel is not available at any of the shown PUSCH start position candidates, or if the remaining number of OFDM symbols in slot 0 is less than a specific threshold indicated by the upper layer, for example, the UE can remove PUSCH0. Next, the UE can attempt to access the channel to transmit the next PUSCH.

[0193] When a slot contains a plurality of PUSCHs, the UE can shift all the scheduled PUSCHs in the slot, for example, as shown in FIG. 53B. ​​​​In the figure, since the channel is unavailable, PUSCH0 is removed. Therefore, the UE may attempt to access the channel to transmit PUSCH1. If the channel is unavailable, both PUSCH1 and subsequent PUSCH2 are shifted to a new starting position. When any PUSCH reaches the end of a slot boundary, the OFDM symbols beyond the slot boundary are punctured. Since the number of available OFDM symbols for this PUSCH decreases, the UE may perform data rate matching / puncturing.

[0194] Furthermore, the UE shifts the PUSCH to a new starting position, but the UE can maintain the scheduled DMRS symbols at their original authorized positions as shown in, for example, Figure 54A. If one or more DMRS symbols are before the new starting position of the PUSCH, those symbols are removed as shown in, for example, Figure 54B. If the new starting position of the PUSCH exceeds all the scheduled DMRS symbols, the UE may abort transmission of the PUSCH. Alternatively, as described above, the UE can transmit, for example, a specific number of compensating DMRS symbols, their positions, and any other configuration such that the UE can transmit all the removed scheduled DMRS symbols, via, for example, upper layer signaling. In the example shown in Figure 54C, the starting position of the PUSCH is at OS10 where all previous DMRS symbols have been removed. In this case, the UE can transmit a DMRS symbol in the first OFDM symbol of the PUSCH at the new starting position. ​

[0195] Power boost in the initial PUSCH transmission

[0196] For the first PUSCH transmission in the UE's COT, the DMRS power is boosted compared to the DMRS in subsequent PUSCH transmissions within that COT. This ensures an improved reliability of PUSCH detection at the gNB and improves the channel quality estimation. This results in the PUSCH transmission being rate-matched to fewer resources or, if punctured due to channel access delay, the block error rate (BL ock Error Rate: BLER) of the PUSCH is improved. This concept is illustrated in Figure 35, in which the nominal power in the DMRS sequence of the UE's first PUSCH transmission following CA T4LBT is boosted. ock Error Rate:BLER) of the PUSCH is improved. This concept is illustrated in Figure 35, in which the nominal power in the DMRS sequence of the UE's first PUSCH transmission following CA ock Error Rate:BLER) of the PUSCH is improved. This concept is illustrated in Figure 35, in which the nominal power in the DMRS sequence of the UE's first PUSCH transmission following CA T4LBT is boosted. is boosted.

[0197] As another use case, if the UE is to remove one or more OSs carrying the DMRS sequence due to the position where the PUSCH transmission starts, the UE can boost the power of the remaining DMRS sequences to improve the quality of channel estimation. Figure 3 S shows an example of a type B PUS CH transmission in which OS#0 is not transmitted due to insufficient channel availability. The power is boosted in the remaining DMRS symbols within the grant, thereby compensating to some extent for the loss of the DMRS sequence in OS#0. Here, the gNB detects the absence of DMRS in OS#0 and recognizes that the PUSCH did not start in OS#0 . The gNB identifies the DMRS of OS#3 and attempts to decode the PUSCH starting from the start positions OS#1, 2, and also 3. S#0 to detect the absence of DMRS in OS#0 and recognize that the PUSCH did not start in OS#0 . The gNB identifies the DMRS of OS#3 and attempts to decode the PUSCH starting from the start positions OS#1, 2, and also 3.

[0198] Power boost value α DMRS-CAI is set for the UE via RRC signaling This value may depend on the number of DMRS sequences actually transmitted within the available PUSCH resources

[0199] Also, the power for PUSCH REs can be boosted within the PUSCH resources available for the first PUSCH transmission within the UE's COT following the UE's LBT. The boost can be a function of the number of available OSs. If the original grant has N OSs and the UE can access only K OSs the UE can increase the power of the PUSCH REs in the K OSs by a factor of P = 10·log10(α ·N / K PUSCH,bооst PUSCH-CAI ) Here, α PUSCH-CAI is set for the UE via RRC signaling α PUSCH-CAI is a value greater than or equal to 0 and is applied to the first PUSCH following channel access. In normal settings, the value 1 can be used. The UE can apply the power boost only if there is power headroom for the given N and K. Otherwise, the device can boost the power up to the maximum possible value P = ma x(P PUSCH-CAI + P PUSCH,nоminal PUSCH,bооst , P max ) Here, P is the power applied to the first PUSCH transmission following LBT PUSCH-CAI and P is the maximum power that the UE can transmit (P max may depend on the UE's capabilities, be set for the UE via RRC signaling, or both max P is either set for the UE via RRC signaling or both). P PUSCH,nоminal is the nominal power at which the PUSCH transmission is sent​​​​​ is power. The power level that can be used in PUSCH transmissions following the first PUSCH transmission is P P USCH,nоminal .

[0200] DMRS sequence depending on the PUSCH start position

[0201] The UE can be configured via RRC signaling with multiple DMRS sequences wherein the UE selects a DMRS sequence indicating the start OS of the PUSCH . This concept is shown in Figure 37, where the UE consists of four start position candidates OS#0, OS# 1, OS#2, OS#3 and four corresponding DMRS sequences. When the UE accesses the channel at OS#0, it transmits the DMRS sequence #1, and when accessing the channel at OS#1 , it transmits the DMRS sequence #2, and so on for transmission . Here, the gNB monitors all DMRS sequence candidates. When it finds a valid sequence , the gNB infers the start position of the PUSCH transmission from that sequence . This way, the need to blindly detect the start OS of the PUSCH transmission is avoided.

[0202] The sequences can be defined by providing different initialization parameters for the start position candidates in a pseudo-random sequence generator. For example, the parameter n can be introduced into the DMRS sequence. However, n CAI is a function of the start CAI position of the PUSCH . When transform precoding for the PUSCH is active, the reference signal sequence r(n) needs to be generated according to Equation 10 below.

[0203] ​

Number

[0204]

Number

[0205] However, the above Equation 10 is a low peak-to-average power ratio (Peak-to-Av erage Power Ratio: PAPR) sequence defined as follows. That is, for PUSCH transmissions dynamically scheduled by DCI, δ = 1 and α = 0. The low peak-to-average power ratio sequence (the above Equation 11) is defined by the cyclic shift α of the base sequence (the following Equation 13) according to the following Equation 12.

[0206]

Number

[0207]

Number

[0208]

Number

[0209] However, the above Equation 14 is the length of the sequence. A plurality of sequences are defined from a single base sequence via different values of α and δ. The base sequence (Equation 13) is divided into a plurality of groups.

[0210]

Number

[0211] [Number]

[0212] [Number]

[0213] However, in Equation 15, the group number is, and v is the base sequence number within the group. For each group, there is one base sequence (v = 0) with each length of Equation 16 (where 1 ≤ m / 2 δ ≤ 5) and two base sequences ( v = 0, 1) with each length of Equation 17 (where 6 ≤ m / 2 δ ). is included.

[0214] The sequence group is given by the following Equation 18.

[0215] [Number]

[0216] [Number]

[0217] [Number]

[0218] [Number]

[0219] [Number]

[0220] However, the above Equation 19 is given by the following. · The above formula 20 is constituted by the upper layer parameter nPUSCH-Identity-Transform-precoding. When the PUSCH is not the msg3 PUSCH, the above formula 21 · Otherwise, the above formula 22 However, n is defined as a parameter for identifying the start position of the PUSCH. CAI However, f and the sequence number v are given as follows. gh · When neither group nor sequence hopping is used, f = 0 gh v = 0 · When group hopping is used but sequence hopping is not used (the following formula 23), · When sequence hopping is used instead of loop hopping (the following formula 25),

[0221]

Equation

[0222] However, the pseudo-random sequence C(i) is a pseudo-random Gold sequence of length 31 and needs to be initialized by the following formula 24 at the start of each radio frame.

Equation

[0223]

Equation

[0224] · When sequence hopping is used instead of loop hopping (the following formula 25),

[0225]

Equation

[0226] However, the pseudo-random sequence C(i) is a pseudo-random Gold sequence of length 31​​ It is necessary that the generator be initialized by the following mathematical formula 26 at the start of each radio frame. It is necessary.

[0227]

Number

[0228] When the conversion precoding of PUSCH is not effective, the sequence r(n) needs to be generated according to the following mathematical formula 27.

[0229]

Number

[0230] However, the pseudo-random sequence C(i) is a pseudo-random Gold sequence with a length of 31, and its generator needs to be initialized using the following mathematical formula 28. It is necessary.

[0231]

Number

[0232]

Number

[0233]

Number

[0234]

Number

[0235]

Number

[0236]

Number

[0237] However, l is the OFDM symbol number in the slot, and the above formula 29 is the slot number within the frame and, · The upper layer parameter UL-DMRS-Scrambling-ID is provided. When the PUSCH is not msg3 PUSCH SCH, the above formula 30 and the above formula 31 are given by the upper layer parameter UL-DMRS-Scrambling-ID and, · Otherwise, the above formula 32 and the above formula 33 are given However, n CAI is defined as a parameter to identify the start position of the PUSCH

[0238] DMRS resource density in the first PUSCH transmission

[0239] The UE is RRC-configured for a specific number of DMRS sequences for PUSCH transmission According to another aspect, when the UE performs PUSCH transmission following a successful LBT , the UE can use a different number of DMRS sequences. That is, the UE can use a different number of DMRS transmissions in the first PUSCH transmission of its COT . Thereby, the gNB can improve channel estimation, and as a result, the BLER on the PUSCH when punctured or rate-matched to fewer resources can be improved. The DMRS configuration of the PUSCH following a successful LBT can be constructed via RRC signaling to the UE. As shown in FIG. 38, in the first PUSCH transmission following the LBT, the density of the DMRS is higher compared to the next PUSCH transmission in the UE's COT ​ The time resources of the DMRS are different. Here, the UE has two UL authorizations of PUSCH type B, and in the first PUSCH transmission, it is at OS#{0, 3, 6, 9}, and in subsequent P USCH transmissions, it is RRC-configured to transmit DMRS at OS#{0, 10} .

[0240] UL preamble for indicating a variable start position

[0241] The UE can transmit a UL preamble to indicate the start position of the first PUSCH following LBT. The PUSCH resources are associated with the position of this preamble . For example, as shown in Figure 39, the PUSCH can start at the same OS as the preamble . In this example, the preamble is transmitted every other RE. However, generally, the preamble can include any set of time / frequency resources set for the UE . The gNB monitors and detects the preamble, and when it detects it, the gNB discovers the PUSCH at the same O S .

[0242] The gNB configures the spatial direction of the preamble transmission. For example, the preamble can have the same correspondence as the DMRS sequence of the P USCH transmission . Alternatively, the preamble can be transmitted in a spatial direction corresponding to different RS such as SSB / PBCH or CSI-RS . When the preamble resources collide with the DMRS resources of the PUSCH, the DMR S is removed and the preamble is transmitted

[0243] Furthermore, as shown in Figure 40, the preamble is such that the gNB can easily detect it can be narrowband compared to the bandwidth of the PUSCH. The frequency resources can be configured relative to the authorized PUSCH resources, such as an offset from the lowest RB of the PUSCH shown in FIG. 40A, or can be fixed relative to the center of the carrier as shown in FIG. 40B. For example, the preamble sequence is configured for the UE via RRC signaling. The sequence can be configured uniquely for the UE or commonly for all UEs. When the UE is specially configured, the preamble can have the same sequence as the DMRS of the PUSCH. The preamble can be applied only to the entire frequency resource of the PUSCH. The preamble can be transmitted corresponding to DL RS such as SSB, CSI-RS, or DMRS. For example, the preamble can have the same correspondence as the DMRS of the PUSCH following the preamble. Alternatively, the correspondence can be configured via RRC signaling to the UE.

[0244] In addition to indicating the start of PUSCH transmission, the preamble can be used to indicate the duration of the UE's COT. A set of preambles can be configured for the UE. Each preamble can indicate a specific period of the COT. The UE can select the preamble to transmit according to the channel occupancy period it intends. For example, in autonomous UL transmission using the configured grant, if there is no upper layer information such as a Buffer Status Report (BSR) at the gNB, the gNB does not know how many PUSCH transmissions will come from the UE. The sequence can be configured uniquely for the UE or commonly for all UEs.

[0245] When the UE is specially configured, the preamble can have the same sequence as the DMRS of the PUSCH. The preamble can be applied only to the entire frequency resource of the PUSCH.

[0246] The preamble can be transmitted corresponding to DL RS such as SSB, CSI-RS, or DMRS. For example, the preamble can have the same correspondence as the DMRS of the PUSCH following the preamble. Alternatively, the correspondence can be configured via RRC signaling to the UE.

[0247] In addition to indicating the start of PUSCH transmission, the preamble can be used to indicate the duration of the UE's COT. A set of preambles can be configured for the UE. Each preamble can indicate a specific period of the COT. The UE can select the preamble to transmit according to the channel occupancy period it intends. For example, in autonomous UL transmission using the configured grant, if there is no upper layer information such as a Buffer Status Report (BSR) at the gNB, the gNB does not know how many PUSCH transmissions will come from the UE. will come from the UE.​​ There may be a possibility that it is not known whether it is expected. To shorten the waiting time, the preamble can indicate the usage period of the configured authorized resources through PHY signaling. This is useful for the gNB to plan resources according to the UE's COT or to enable efficient COT sharing between the UE and the gNB.

[0248] If the preamble sequence is common to multiple UEs, other nodes can recognize that the channel is occupied, so the preamble can provide improved power efficiency and coexistence. If the preamble is common for DL and UL, coexistence becomes easier. The position of the preamble resources can be common for DL and UL. The PUSCH may be rate-matched around the preamble, or the preamble may puncture the PUSCH.

[0249] In the case of PUSCH mapping type B for either SU-MIMO or MU-MIMO, the position of the DMRS symbols is defined relatively to the PUSCH resources. Thus, when the UE selects a PUSCH start position different from what it was first scheduled, the UE can transmit UL DMRS symbols according to PUSCH type B. In this case, the first DMRS symbol can occupy the first symbol of the PUSCH from the start position selected by the UE. The position and number of the additional DMRS symbols can be based on the PUSCH period from the position selected by the UE according to the DMRS mapping rule of PUSCH type B. For example, Figure 49 shows two additional UL DMRS symbols Scheduled to be transmitted over eight OFDM symbols from OS5 to OS12, but the UE fails in LBT and fails to access the channel, showing an example of a PUSCH. When the candidate position shown in the figure, i.e., the channel starting from OS7, becomes available, the period of the PUSCH according to the starting position selected by the UE is 6 OFDM symbols. In this case, as shown in Figure 49, the UE can map the UL DMRS according to the new 6OS PUSCH period that is relative to the start of the PUSCH and is 10 and 4 according to mapping type B. SCH. SCH is shown. When the candidate position shown in the figure, i.e., the channel starting from OS7, becomes available, the period of the PUSCH according to the starting position selected by the UE is 6 OFDM symbols. In this case, as shown in Figure 49, the UE can map the UL DMRS according to the new 6OS PUSCH period that is relative to the start of the PUSCH and is 10 and 4 according to mapping type B.

[0250] Transmission of PUSCH in available symbols

[0251] Some of the above procedures enable the gNB and the UE to have the same understanding of from which starting position the UE can attempt to access the channel in case the UE fails to access the channel at the start of UL grant. Also, some of the above methods can show how the DMRS is affected by shifting the starting position and how the UE selects a PUSCH candidate position using it. Procedures for puncturing and adapting the MCS and methods for transmitting piggybacked UCI will be described below.

[0252] Puncturing

[0253] As a simple procedure, after the UE generates the PUSCH based on the grant provided by the gNB, the UE can use some of those symbols without adjusting the UL DMRS position. ​​​​​​​​​​It can puncture one and transmit the others. According to one aspect, the UE punctures all symbols from the start of the PUSCH grant to the symbol at which the UE accesses the channel. It can. FIG. 41 shows an example of a PUSCH grant for a period equal to 12 symbols from OS0 to OS11 with three additional DM RS configured to occupy l0, 5, 8, 11. When the UE accesses the channel starting from OS7, the UE can puncture OS0 to OS6.

[0254] In some situations, especially when the last two OFDM symbols of the PUSCH do not carry any DMRS at all, if all DMRS symbols are punctured the remaining DMRS may not be sufficient for the gNB to obtain an accurate channel estimate. Thus, according to another aspect, in order to obtain reliable decoding at the gNB, it can transmit the minimum number of necessary DMRS symbols. If the remaining DMRS symbols are less than this minimum threshold, since the gNB may have a low possibility of decoding the transmitted PUSCH, the UE can abandon UL transmission to reduce power consumption.

[0255] This threshold can be a higher layer parameter called min_DMRS_num that can provide the absolute minimum number of necessary DMRS symbols or a part of the already scheduled DMRS symbols. Further, the minimum number of necessary DMRS symbols can depend on the scheduled PUSCH grant parameters such as MCS and PUSCH duration. Table 7 shows an example of the minimum number of necessary DMRS symbols as a function of the scheduled MCS. However, I ​MCS is the MC given to the DCI that provides PUSCH authorization S. Further, the following Equation 34 can be provided by a higher layer parameter such as the RRC parameter min_DMRS_num. When the higher layer parameter indicates that the MCS thresholds for any row are equal, that is, when MCS = MCS th_(i-1) = MCS th_i of, the minimum number of necessary DMRS symbols for the relevant rows where both of these M CS thresholds appear is invalid.

[0256]

Number

[0257]

Table 7

[0258] Similarly, the minimum number of necessary DMRS symbols can be a function of the PUSCH period, for example, as shown in Table 7. However, L is the actual number of OFDM symbols that can be transmitted,{ }and the following Equation 35 can be provided by a higher layer parameter such as the RRC parameter min_DMRS_num. When the higher layer parameter indicates that the PUSCH period thresholds for any row are equal, that is, when D }of, the minimum number of necessary DMRS symbols for the relevant rows where both of these MCS thresholds appear is invalid. provided. When the higher layer parameter indicates that the PUSCH period thresholds for any row are equal, that is, when D = D th_(i-1) = D th_i of, the minimum number of necessary DMRS symbols for both of these MCS thresholds appearing in the relevant rows is invalid.

[0259]

Number

[0260]

Table 8

[0261] Also, in the case of MU-MIMO scheduling, puncturing may be used to avoid loss of orthogonality between the UEs scheduled simultaneously. The UE may use only one of the scheduled DMRS symbols and may not attempt to adjust the UL DMRS based on the PUSCH period from the newly selected start position.

[0262] Adaptation of MCS

[0263] Assuming that the license transport block size (TBS) is fixed and does not depend on the LBT result, the MCS associated with the scheduled PUSCH may not be an effective MCS for transmitting the entire TBS in one transmission. On the other hand, if the UE changes the MCS associated with the scheduled PUSCH autonomously based on the LBT result without a common understanding between the UE and the gNB regarding the new MCS, it will be a significant burden for the gNB to detect the used MCS.

[0264] If multiple PUSCH start positions are signals via multiple DCIs as described above, the appropriate MCS associated with the new PUSCH start position may be signaled in these DCIs.

[0265] If multiple PUSCH start positions are configured via upper layer parameters, the new MCS may be determined as a function of some of the parameters provided in the PUSCH grant. ​​​​​​​​​​​​​For example, the new MCS depends on the PUSCH period, PUSCH grant such as MCS, and, as shown in Table 9 and may depend on the PUSCH period from the start position selected by the UE based on the LBT result as follows.

[0266]

Table 9

[0267] However, L is the PUSCH period provided by the UL grant from the perspective of symbols , and I MCS is the MCS given by the PUSCH grant. I new, N(L-1) is MCS a function of I and can be. For example, I new, x = max {2 I MCS , MCS_max} means that the new MCS is twice the MCS with a specific maximum MCS represented by MCS_max given by the PUSCH grant .

[0268] Alternatively, the UE can autonomously change the MCS and indicate the selected MCS by transmitting the piggybacked UCI on the PUSCH. Also, the piggybacked UCI can be transmitted at the position specified during the new PUSCH period. For example, the piggybacked UCI can be transmitted after the first DMRS symbol so that the gNB first decodes the UCI to know the MCS selected by the UE and then decodes the data part in the PUSCH.

[0269] Instead of transmitting the UCI to carry the selected MCS, the UL DMRS can indicate the selected MCS. For example, the UE is provided with some initialization sequences ​​​It is possible, and they have a one-to-one mapping relationship with the MCS candidates. Therefore, the gNB can determine the selected MCS by knowing the DMRS initialization sequence . This is achieved by signaling a plurality of values (Equation 37 below) used to generate the DMRS initialization sequence using the following equation (Equation 36 below) . It can be done.

[0270]

Equation

[0271]

Equation

[0272] The additional value (Equation 37) can be given by a higher layer parameter such as an RRC parameter such as scrambling_to_MCS_mapping, and the other parameters in the above equation are defined previously . The gNB needs to blindly detect the DMRS and the corresponding initialization for the purpose of detecting the MCS .

[0273] Transmission of piggybacked UCI

[0274] If the PUSCH symbol is punctured or shifted based on the LBT result, especially , if the piggybacked UCI is mapped to the first few OFDM symbols at the start of the PUSCH grant , the piggybacked UCI may be affected . According to another aspect, the UCI can have a higher priority than the PUSCH, and the UCI does not carry the DMRS, or in the case of the first single-symbol / double-symbol DMRS It can be transmitted at the first available symbol immediately after transmission.

[0275] Based on the result of LBT, there are very few OFDM symbols available for UL transmission and thus, especially when the size of UCI is large, there may not be enough resources to carry UCI. Therefore, according to another aspect, specific priority rules can be defined to specify which content of UCI can be removed. For example, · The part 2 CSI report may have a lower priority than the part 1 CSI report . · The part 2 CSI report may have a lower priority than the acknowledgement / negative-acknowledgement (ACK / NACK) feedback . · The part 1 CSI report may have a lower priority than the ACK / NACK feedback .

[0276] Since the content of UCI can vary according to the LBT result, blindly decoding different UCIs with different contents can be a burden for the gNB. Thus, according to another aspect, the UL DMRS can indicate the content of the piggybacked UCI . For example, if the content of UCI is divided into three categories, namely, part 2 CSI report < part 1 CSI report < ACK / NACK feedback, the possible DMRS initialization sequences can be divided into three groups, and each group of the initialization sequences corresponds to a specific UCI category.

[0277] Signaling of CAI

[0278] CAI is particularly important in terms of latency and can be read by other general nodes. If necessary, it may be signaled entirely as a PHY signal, but in scenarios where latency is not a problem, it may be sent via upper layer signaling.

[0279] PHY Signaling of CAI

[0280] Signaling via PDCCH in the common search space

[0281] In the DL, NR DCI can carry a payload and can be used to signal to CAI within the physical layer via PDCCH.

[0282] The intention is to enable sibling nodes and general nodes to detect CAI transmitted by nodes within the cell (at least from other NR-U cells). The PDCCH is scrambled with the DL-CAI-RNTI provided by the specification to be common across NR-U cells. Therefore, general nodes know the CAI-RNTI and do not need to obtain the cell's Remaining Minimum System Information (RMSI) to acquire that CAI-RNTI.

[0283] When the NR-U cell is in DC or Stand-Alone (SA) deployment, the cell can signal on the PBCH and RMSI. The DL CAI can be transmitted within the CORESET of index 0 and the common search space. Other gNBs within the NR-U band periodically detect each other's presence and signal to their UEs about those The cell ID can be monitored for the CAI. The gNB can also provide synchronization information to its UE so that the general node does not need to perform synchronization with other cells. Therefore, the sibling node and the general node can know the presence and location of the PBCH of the coexisting NR-U cell. The cell occupying the channel can transmit the CAI at CORESET index 0. The sibling node and the general node can know the CORESET to detect the CAI. A method for detecting the CAI is described in FIG. 14. Here, gNB2 and its UE are general nodes, and gNB1 transmits the CAI on cell 1. In the NR-U cell in carrier aggregation with the licensed PCell, the PCell can configure the CORESET for the sibling node to monitor the DL-CAI-RNTI DCI on the NR-U cell. Alternatively, the SSB / RMSI signal can be present in the SCell to enable the general node to monitor the CAI. For the DCI format with a CRC scrambled by the DL-CAI-RNTI for the CAI, type 0B-PDCCH common search can be introduced. The association of the monitoring occasion of the type 0B-PDCCH common search space with the SS / PBCH block index can be the same as that of the type 0-PDCCH common search space. The UE can be associated with the DMRS antenna port related to PDCCH reception in the type 0B-PDCCH common search space, and the SS / PBCH reception.

[0284] In the NR-U cell in carrier aggregation with the licensed PCell, the PCell can configure the CORESET for the sibling node to monitor the DL-CAI-RNTI DCI on the NR-U cell. Alternatively, the SSB / RMSI signal can be present in the SCell to enable the general node to monitor the CAI. In the NR-U cell in carrier aggregation with the licensed PCell, the PCell can configure the CORESET for the sibling node to monitor the DL-CAI-RNTI DCI on the NR-U cell. Alternatively, the SSB / RMSI signal can be present in the SCell to enable the general node to monitor the CAI.

[0285] For the DCI format with a CRC scrambled by the DL-CAI-RNTI for the CAI, type 0B-PDCCH common search can be introduced. For the DCI format with a CRC scrambled by the DL-CAI-RNTI for the CAI, type 0B-PDCCH common search can be introduced. The association of the monitoring occasion of the type 0B-PDCCH common search space with the SS / PBCH block index can be the same as that of the type 0-PDCCH common search space. The association of the monitoring occasion of the type 0B-PDCCH common search space with the SS / PBCH block index can be the same as that of the type 0-PDCCH common search space. The UE can be associated with the DMRS antenna port related to PDCCH reception in the type 0B-PDCCH common search space, and the SS / PBCH reception. The UE can be associated with the DMRS antenna port related to PDCCH reception in the type 0B-PDCCH common search space, and the SS / PBCH reception. The attached DMRS antenna ports are assumed to be co-located with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. This can be done. The value for initializing the DMRS scrambling sequence can be set as follows . · It can be set to a fixed constant defined by the specification. · It can be set to the cell ID.

[0286] The length of the DCI based on the DL-CAI-RNTI can be defined by the specification or can be configured within the RMSI . If the number of DCI lengths monitored within CORESET index 0 exceeds the maximum limit in NR during a monitoring occasion, the NR-U UE may stop monitoring this DCI.

[0287] The higher layer parameter dlCAIPeriod can be defined to indicate the periodicity of signaling the CAI (as seen in FIGS. 10 and 11, the CAI is signaled multiple times by the gNB within the MCOT to ensure that the listening nodes can detect the signal without missing it).

[0288] Not all cells may support the transmission of the CAI. One bit of the PBCH can indicate whether the cell supports CAI transmission.

[0289] Alternatively, the CAI can be multicast to a group of UEs. For example, it can be carried using a group common PDCCH (e.g., the PDCCH of DCI format 2_0). Since this PDCCH will be configured with the GC-CAI-RNTI of the CAI for the UE, it can be decoded by the RRC-connected UEs. The DCI is for the group ​​​​​​​​Scrambled with the group common RNTI "GC-CAI-RNTI". It can be

[0290] It is advantageous for a node such as a gNB to indicate the start of channel access to the UE. By this the UE can identify the presence of at least one of valid CSI-RS, DRS, SSB / PBCH, PRACH opportunities, and the resources for COT sharing with the gNB and the configured authorization resources.

[0291] DCI with DL-CAI-RNTI can be sent by the gNB to the UE to provide the state of the COT. The DCI can carry up to the maximum C bits indicating the COT of the gNB. C can be set for the UE via RRC signaling or predefined in the specification. For example, for an MCOT up to 10 milliseconds, C = 4. The DCI can also carry a B-bit bitmap corresponding to the bandwidth for which the COT is valid, e.g., B 20 MHz sub-bands within the spectrum. The bits corresponding to the set of 20 MHz sub-bands accessible by the gNB are set to 1. In this case, when the UE receives a DCI having both DL-CAI-RNTI and the slot format indication RNTI (Slot Format Indication-RNTI: SFI-RNTI), it can ignore the SFI of the slot indicated by the CAI-RNTI as having no channel access. Alternatively, the DCI can indicate the COT by specifying the slot format of N slots of the COT. DL-CAI-RNTI indicates to the UE the slot ​​​​​​​​​​​​It can be the SFI-RNTI that provides the format indication. DL, flexible In addition to the "D", "X", and "U" states that exist in the slot format to identify the DL, flexible burst, and UL states respectively, a "null" format can be introduced to identify invalid channel access. For example, the slot format "NNNNN NNNNNNNNN" means that channel access is not available at any of the 14 symbols of the slot. A slot format with partial channel access can also be defined as, for example, "XXXXXXXNNNNNNN", in which case the last 7 symbols of the slot are outside the COT of the node, so channel access cannot be obtained. Since the DCI can carry the slot formats of multiple slots, when a null format is detected for a certain symbol, the UE may recognize that the gNB cannot access the channel and ignore the SFI of the symbols following the null. The second DCI with the Bandwidth-RNTI (BW-RNTI) can carry information about the 20 MHz subband where the COT is valid. The BW-RNT I can be detected during the same CORESET and monitoring occasion as the SFI-RNTI. Therefore, the UE uses both the SFI-RNTI and the BW-RNTI to determine the bandwidth and time of the gNB's channel access. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. the last 7 symbols of the slot are outside the COT of the node, so channel access cannot be obtained. Since the DCI can carry the slot formats of multiple slots, when a null format is detected for a certain symbol, the UE may recognize that the gNB cannot access the channel and ignore the SFI of the symbols following the null. The second DCI with the Bandwidth-RNTI (BW-RNTI) can carry information about the 20 MHz subband where the COT is valid. The BW-RNT I can be detected during the same CORESET and monitoring occasion as the SFI-RNTI. Therefore, the UE uses both the SFI-RNTI and the BW-RNTI to determine the bandwidth and time of the gNB's channel access. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. cannot be obtained. Since the DCI can carry the slot formats of multiple slots, when a null format is detected for a certain symbol, the UE may recognize that the gNB cannot access the channel and ignore the SFI of the symbols following the null. The second DCI with the Bandwidth-RNTI (BW-RNTI) can carry information about the 20 MHz subband where the COT is valid. The BW-RNT I can be detected during the same CORESET and monitoring occasion as the SFI-RNTI. Therefore, the UE uses both the SFI-RNTI and the BW-RNTI to determine the bandwidth and time of the gNB's channel access. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. OT can carry information about the 20 MHz subband where the COT is valid. The BW-RNT I can be detected during the same CORESET and monitoring occasion as the SFI-RNTI. Therefore, the UE uses both the SFI-RNTI and the BW-RNTI to determine the bandwidth and time of the gNB's channel access. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. Therefore, the UE uses both the SFI-RNTI and the BW-RNTI to determine the bandwidth and time of the gNB's channel access. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. In the case of directional LBT, the COT may vary depending on the spatial direction. In this case, a single DCI can provide the COT information of multiple spatial directions. Therefore, the DCI can carry the TCI state of each COT it indicates. Alternatively, the DCI can carry the COTs for D spatial directions configured for the UE. D can be used to check whether the RMSI or other system information (OS I) or can be configured in a UE specific way. DCI received in a spatial direction may indicate the COT for that spatial direction. This RS, which determines the direction of the channel, is called the Channel-Access-RS (CA-RS). For example, the spatial direction of the DMRS of DCI (carrying COT) is called its spatial It may indicate the COT of the direction. Here, the CA-RS is a DC Therefore, multiple DCIs can be transmitted by the gNB and can be used for different C A-RS can be used to show COT in different spatial directions.

[0292] A CA-RS group is a group of nodes where a gNB has channel access to a given CA-RS. In this case, it can be defined to include the set of RSs that can be transmitted by the gNB. For example, -RS groups can be defined for DMRSs of DCIs carrying COT, This includes other RSs such as CSI-RS that may be transmitted by the gNB in the same spatial direction as the RS. The UE must have a grant or R that belongs to a CA-RS group that the gNB has channel access to. If the UE has CA-RS, the UE processes the grant or RS. If successful, the gNB can perform spatial LBT in the given direction. A CA-RS can transmit signals within the CA-RS group. , RSs with the same / similar spatial orientation as the reference CA-RS in that CA-RS group. It is necessary to be rare. As shown in FIG. 42, the gNB carries COT information to CA-RS1 and transmits the DCI. When the UE receives this, the UE can only receive signals in the spatial direction given by the RS within the CA-RS group in its COT and recognizes this.

[0293] Furthermore, in the case of directional LBT, if the gNB is sharing its COT with the UE, the UE can perform the authorized transmission configured on the shared COT only when the configured authorized spatial direction corresponds to the DL spatial direction of the COT. The UE also performs CAT2LBT and can access the channels in the shared COT in the direction corresponding to each DL CA-RS. As shown in FIG. 43, the UE transmits within the COT of the gNB using the spatial direction corresponding to the DL CA-RS group of CA-RS1.

[0294] When a node such as a gNB acquires channel access from the beginning of a partial slot, the node can have channel access only for the partial slot at the end of the COT. In this case, since the format of the last partial slot requires additional bits to indicate it with finer granularity of the COT, the node may not indicate it. Unless the UE has an explicit authorization in the last partial slot, the UE cannot recognize the COT of the gNB in the last partial slot. Therefore, for the last partial slot, even if a COT indication of valid channel access is not received, if the UE has an authorization, the UE considers the channel access to be valid and continues to process that slot. This is especially true for scheduled authorizations where the authorization is received within its COT ​​​​​​​​​​​​​​ It can be used when If the COT indication of channel access is not received for a configured grant for a partial slot, the UE considers that the channel access is not valid and does not transmit in that slot.

[0295] To keep the power consumption low during the CAI monitoring period, the UE can monitor the CAI only on the selected resources. For example, the UE can monitor the CAI on the CORESET within the narrow BWP in the search space with periodic S ... CAI ... within the WP. When the UE receives the CAI, it can switch to a pre-configured wider BWP and monitor the CORESET configured for control information. ... ... ...

[0296] As another way, after receiving the CAI on a common BWP, the UE can monitor the CAI and control information, but can configure different search spaces for monitoring the CAI and other control information. ... ...

[0297] Alternatively, when the CAI is detected, the search space configured for the CAI is automatically disabled for the remaining period of the COT detected from the CAI. ...

[0298] Signaling via PDCCH to trigger a handshake

[0299] In DL, the NR DCI can carry the payload of CAI-I to trigger a handshake on UL. This can happen as follows. ... · The PDCCH of CAI-I can be signaled using the C-RNTI or CS-RNTI. The UE blindly decodes the PDCCH and if its LBT is successful, the CA ... Responds with I-R. CAI-I may also indicate the type of LBT that the UE must perform before transmitting CAI-R. The method is shown in Figure 15. In this case, other UEs that are continuously connected to the same cell and nodes outside the cell cannot receive CAI-I. The trigger may be transmitted as part of DL or UL grant in a UE-specific search space or a type 0-PDCCH common search space. New DCI formats 1_1C, 1_0C, 0_1C, 0_0C may be introduced with one or more of the following fields. · A 1-bit indicating the need for handshake

[0300] · An L-bit (priority class) indicating the type of LBT to be performed by the UE · A D-bit for T indicating the channel occupancy time. As a result, the UE can signal CAI-R within T of the gNB in its cell. · An H-bit indicating the threshold to be used for sensing prior to transmission of CAI-R The PDCCH of CAI-I can be signaled in a common search space with CAI-RNTI in a search space such as a type 0-PDCCH common search space. CAI-RNTI can be configured via RMSI or a constant value specified in the specification. Multiple sibling nodes can receive the DCI, and one or more UEs can transmit its CAI-R depending on how CAI-I is triggered. General nodes of other NR-U cells can also detect CAI-I and obtain T therefrom. The DCI may also have an L-bit for indicating the type of LBT to be performed by the triggered UE. оcc

[0301] оcc оcc -R includes an implicit or explicit identification of the receiver so that the receiving side can identify the source of CAI-R. CAI-R may also include an identification of the node that requests a handshake. This may be useful in Device-to-Device (D2D) or Vehicle-to-Everything (V2X) applications where multiple nodes may access resources via frequency / time multiplexing. Therefore, multiple CAI-Is and CAI-Rs may be transmitted, and it is necessary to identify their sources and receiving sides. The trigger may be provided in the following ways. When the CAI-RNTI is received, a handshake is implicitly triggered. A UE that receives DL or UL authorization within time T from the reception of CAI-I is triggered to transmit CAI-R. As shown in Figure 16, UE1 receives CAI-I and DL authorization within time T. Therefore, if CCA / LB T is successful, UE1 responds with CAI-R. Similar to the Paging RNTI (P-RNTI), the CAI-RNTI may carry a PD SCH authorization for the ID (e.g., C-RNTI) of the UE that needs to respond using CAI-R. A UE that finds its ID in the message transmits CAI-R. In this method, since the message needs to be processed at the upper layer, a specific latency may occur. The CAI-RNTI itself may carry the ID of the triggered UE. When the UE receives that ID within CAI-I, it transmits CAI-R. However, in this method, D etween different types of messages may cause interference, so it needs to be carefully designed. There may be a situation where multiple CAI-Is and CAI-Rs are transmitted, and it is necessary to identify their sources and receiving sides. The trigger can be provided in the following ways. When the CAI-RNTI is received, the handshake is implicitly triggered. From the reception of CAI-I, the UE that receives DL or UL authorization within time T Resp is triggered to transmit CAI-R. As shown in Figure 16, UE1 receives CAI-I and DL authorization within time T of CAI-I. Re sp Therefore, if CCA / LB T is successful, UE1 responds with CAI-R. Similar to the Paging RNTI (P-RNTI), the CAI-RNTI may carry a PD SCH authorization for the ID (e.g., C-RNTI) of the UE that needs to respond using CAI-R. A UE that finds its ID in the message transmits CAI-R. In this method, since the message needs to be processed at the upper layer, a specific latency may occur. There may be a situation where multiple CAI-Is and CAI-Rs are transmitted, and it is necessary to identify their sources and receiving sides. The CAI-RNTI itself may carry the ID of the triggered UE. When the UE receives that ID within CAI-I, it transmits CAI-R. The payload of CI becomes very large.

[0302] CAI-R signaling via RACH

[0303] In addition to indicating that the node's channel is receivable, the CAI-R response may not carry much information. Therefore, the PRACH preamble is a good candidate for CAI-R. The RACH preamble of CAI-R can be RRC-configured for the UE. To ensure that all CAI-R signals are received at the gNB without collision, conflict-free RACH resources are desirable. Due to the orthogonality of the PRACH preamble, multiple CAI-Rs can be received simultaneously. Following the reception of the preamble, the handshake is completed and the gNB proceeds with DL / UL authorization for the UE.

[0304] UL CAI-R signaling on PUCCH

[0305] The short PUCCH format used for SR can be used for CAI-R. When the gNB detects the energy within the UE's CAI-R resource, it considers that the CAI-R has been received and the handshake is completed.

[0306] CAI-R may include additional information such as the energy level detected during CCA / LBT at the UE. Furthermore, it can carry the energy levels of multiple beams (corresponding to QCL using DL RS or UL sounding reference signal (UL SRS)). In this case, the payload is too large to be indicated via RACH. For CAI-R, short PUCCH or long PUCCH can be used. It is possible.

[0307] CAI-Rs from multiple UEs can be orthogonally multiplexed or multiplexed with other PUCCH signals from other UEs. It can be multiplexed with PUCCH signals.

[0308] Preamble-assisted CAI

[0309] A preamble can be used to indicate CAI. The preamble can carry some or all of the information necessary to indicate the channel or cell. Furthermore, it can indicate resources where more information about occupancy may be obtained. With such a design, other cells or nodes of other technologies may be able to easily detect the preamble without obtaining the SI of the NR-U node occupying the channel. The node monitors the preamble within a time and looks for a high correlation with a known preamble. When the correlation exceeds a threshold, the preamble is detected. or T using the channel оcc or carry some or all of the information necessary to indicate the cell. Furthermore, it can indicate resources where more information about occupancy may be obtained. With such a design, other cells or nodes of other technologies may be able to easily detect the preamble without obtaining the SI of the NR-U node occupying the channel. The node monitors the preamble within a time and looks for a high correlation with a known preamble. When the correlation exceeds a threshold, the preamble is detected. When the correlation exceeds a threshold, the preamble is detected.

[0310] By using a common preamble across all NR-U nodes, the detection of general nodes can be simplified. The preamble may be a Zadoff-Chu (ZC) sequence, or an M-sequence (m-sequence) such as PSS or SSS, or an RS sequence such as Channel Quality Information RS (CQI-RS) for DL. It can be a sequence such as PRACH or SRS on UL. By using a common preamble across all NR-U nodes, the detection of general nodes can be simplified. The preamble may be a Zadoff-Chu (ZC) sequence, or an M-sequence (m-sequence) such as PSS or SSS, or an RS sequence such as Channel Quality Information RS (CQI-RS) for DL. It can be a sequence such as PRACH or SRS on UL. It can be a sequence such as PRACH or SRS on UL. It can be a sequence such as PRACH or SRS on UL.

[0311] Cell coloring

[0312] The preamble can carry S-bit information indicating the cell that transmits the CAI. The S bit can be derived from the cell ID of the gNB or UE connected to the cell ID. When S is small est (e.g., 2 or 3 bits), the listening node needs to correlate with a small set of known sequences of possible preambles (4 or 8 in the case of 2 or 3 bits). The S bit provides "cell coloring" that enables the listening node to distinguish whether the transmission is within the cell or outside the cell. When the number of bits shown is less than the number of cell IDs there is ambiguity in identifying the cell where the preamble is transmitted. Therefore, a general node cannot be sure whether it is from its own cell, but can quickly identify the CAI from many cells. To resolve the ambiguity additional information may be attached to the preamble, but a node that identifies the transmission as that of another cell does not need to look for this information. A method for detecting the preamble is shown in FIG. 17. If complete information about the cell ID can be obtained, nodes within the cell can use a higher threshold for LBT failures to enable spatial reuse.

[0313] Indication of T on the preamble оcc

[0314] The S bit of the preamble is used to indicate T оcc A general node knows the state of the channel and when to start sensing the channel.

[0315] Indication of the S bit on the preamble

[0316] The S bit can be indicated in one of the following ways. Generally, when there is capacity to indicate the S bit in the preamble it is possible to divide it into the indication of T оcc and the cell coloring. And. · The S bit can be used as part of the root or cyclic shift of the ZC-based preamble · The S bit can be used as part of the initialization of the M-sequence based preamble. · The preamble sequence (Equation 38 below) can be repeated S times in time · Applying the OCC vector of length S (Equation 39 below) to the S repetitions can carry the information of the S bits Here, the preamble is repeated 4 times, (Equation 40 below) And. Let it be.

[0317]

Number

[0318]

Number

[0319]

Number

[0320] Figure 18(A) shows an example of how the preamble can be transmitted by time repetition. Since the preamble may be transmitted asynchronously, Node 1 transmits the preamble immediately after successful completion of LBT. After transmitting the preamble, Node 1 can transmit a reservation signal to synchronize with the symbol boundary. After transmitting the preamble, Node 1 can transmit a reservation signal to synchronize with the symbol boundary.

[0321] Figure 18(B) shows an example in which the preamble is transmitted synchronized with the symbol boundary. After a successful completion, the reservation signal follows. At the beginning of a symbol boundary, a preamble is transmitted.

[0322] Preamble Resources

[0323] The CAI preamble is narrowband so that the receiving node can detect it with minimal power consumption. The bandwidth can be greater than the minimum BWP supported by NR-U. The frequency can also be reduced to, for example, 5 MHz for FR1. European Telecommunications Standards Institute (ETSI) harmonized standard According to the 20 MHz band, a 20 MHz channel is required for 5 GHz. Since operation in a smaller band than the center (small band of about 5 MHz) is also permitted, CAI Choosing 5MHz for the preamble is effective for coexistence with WiFi. The preamble may be smaller than the minimum occupied channel bandwidth (OCB). B) Meeting the requirement, i.e., 80% of 5MHz, may be sufficient.

[0324] The preamble is used to identify the location of a general node in the unlicensed band. At a predefined location, such as the center of a 20 MHz band, or at a specific predefined location, such as a raster location In Figure 19, the 80 MHz band is divided into 20 MHz bands and the channel The example shows how the CAI preamble is transmitted within the central 5 MHz.

[0325] The CAI resource is configured to allow all UEs to find the CAI through the RRC. configured via SI and can be indicated via SI. In CA, the information can be provided by the PCell. In DC, the information can be provided by the Master Cell Group (MCG) or obtained from the SI carried by the DRS or SSB. In SA as well, this information can be obtained from the SI carried by the DRS or SSB. SI can provide frequency resources as an offset from the lowest PRB of the Channel Bandwidth (CBW). Since NR supports operation in a wider bandwidth, an NR-U node can create a composite carrier with a wider bandwidth within a single cell by using multiple 20 MHz bands (instead of carrier aggregation where many SCell are aggregated, multiple chunks of bandwidth are combined into one cell). Also in this case, it is proposed in this specification to transmit the preamble at the center of each 20 MHz sub-band of the aggregated bandwidth. As shown in Figure 20, in the unlicensed spectrum, an 80 MHz band composed of four 20 MHz channels is used. The NR-U node creates a composite 60 MHz channel by using three 20 MHz channels. According to another aspect, the CAI preamble can be transmitted at the center of each 20 MHz channel so that each 20 MHz general node can detect the channel state without the need to switch frequencies. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI.

[0326] NR supports operation in a wider bandwidth, so an NR-U node can create a composite carrier with a wider bandwidth within a single cell by using multiple 20 MHz bands (instead of carrier aggregation where many SCell are aggregated, multiple chunks of bandwidth are combined into one cell). Also in this case, it is proposed in this specification to transmit the preamble at the center of each 20 MHz sub-band of the aggregated bandwidth. As shown in Figure 20, in the unlicensed spectrum, an 80 MHz band composed of four 20 MHz channels is used. The NR-U node creates a composite 60 MHz channel by using three 20 MHz channels. According to another aspect, the CAI preamble can be transmitted at the center of each 20 MHz channel so that each 20 MHz general node can detect the channel state without the need to switch frequencies. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI. Since NR supports operation in a wider bandwidth, an NR-U node can create a composite carrier with a wider bandwidth within a single cell by using multiple 20 MHz bands (instead of carrier aggregation where many SCell are aggregated, multiple chunks of bandwidth are combined into one cell). Also in this case, it is proposed in this specification to transmit the preamble at the center of each 20 MHz sub-band of the aggregated bandwidth. As shown in Figure 20, in the unlicensed spectrum, an 80 MHz band composed of four 20 MHz channels is used. The NR-U node creates a composite 60 MHz channel by using three 20 MHz channels. According to another aspect, the CAI preamble can be transmitted at the center of each 20 MHz channel so that each 20 MHz general node can detect the channel state without the need to switch frequencies. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI. Since NR supports operation in a wider bandwidth, an NR-U node can create a composite carrier with a wider bandwidth within a single cell by using multiple 20 MHz bands (instead of carrier aggregation where many SCell are aggregated, multiple chunks of bandwidth are combined into one cell). Also in this case, it is proposed in this specification to transmit the preamble at the center of each 20 MHz sub-band of the aggregated bandwidth. As shown in Figure 20, in the unlicensed spectrum, an 80 MHz band composed of four 20 MHz channels is used. The NR-U node creates a composite 60 MHz channel by using three 20 MHz channels. According to another aspect, the CAI preamble can be transmitted at the center of each 20 MHz channel so that each 20 MHz general node can detect the channel state without the need to switch frequencies. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI. Since NR supports operation in a wider bandwidth, an NR-U node can create a composite carrier with a wider bandwidth within a single cell by using multiple 20 MHz bands (instead of carrier aggregation where many SCell are aggregated, multiple chunks of bandwidth are combined into one cell). Also in this case, it is proposed in this specification to transmit the preamble at the center of each 20 MHz sub-band of the aggregated bandwidth. As shown in Figure 20, in the unlicensed spectrum, an 80 MHz band composed of four 20 MHz channels is used. The NR-U node creates a composite 60 MHz channel by using three 20 MHz channels. According to another aspect, the CAI preamble can be transmitted at the center of each 20 MHz channel so that each 20 MHz general node can detect the channel state without the need to switch frequencies. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI. Since NR supports operation in a wider bandwidth, an NR-U node can create a composite carrier with a wider bandwidth within a single cell by using multiple 20 MHz bands (instead of carrier aggregation where many SCell are aggregated, multiple chunks of bandwidth are combined into one cell). Also in this case, it is proposed in this specification to transmit the preamble at the center of each 20 MHz sub-band of the aggregated bandwidth. As shown in Figure 20, in the unlicensed spectrum, an 80 MHz band composed of four 20 MHz channels is used. The NR-U node creates a composite 60 MHz channel by using three 20 MHz channels. According to another aspect, the CAI preamble can be transmitted at the center of each 20 MHz channel so that each 20 MHz general node can detect the channel state without the need to switch frequencies. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI.

[0327] Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI. Alternatively, the gNB can provide a bitmap in the SI or dynamically (especially via the authorization when triggering the handshake) to indicate which 20 MHz band carries the CAI. ​​

[0328] The numerology of the preamble can be determined as follows. · The preamble uses a pre-defined numerology based on the frequency band. For example, using 15 kHz for FR1, a UE with various processing functions can receive this signal. 30 kHz and 60 kHz are also available to keep the latency due to the CAI preamble short and to enable more repetitions using barcodes. · The preamble uses the same numerology as the SSB. In this case, the listening node needs to know the numerology regarding the SSB or NR-U cell either by performing initial access or through the configuration from the PCell or PSCell.

[0329] Generally, the information that can be transmitted on the preamble is limited. Therefore, this specification proposes using the preamble in combination with other forms of transmitting CAI (such as PDCCH, RACH, and RS). The preamble can indicate the occasion and resources for receiving the remaining information of the CAI. In other words, if the information of the preamble is related to the node, the node wakes up and looks for the remaining CAI information as shown in Figure 17. The remaining information of the CAI may appear in the first occasion (of the signal type) after the preamble, or within the first N occasions after the preamble. For example, if the remaining information is transmitted on the PDCCH, the node can look for this information at the first monitoring opportunity following the preamble. This concept is shown in Figure 44. In the figure, the UE monitors the preamble of the DL Sometimes it decodes the DCI that carries the COT information.

[0330] Another example is shown in Figure 45, where C is inserted immediately after the preamble to save resources. ORESET and monitoring occasions are provided. Preamble and next monitoring occasion If there are multiple symbols between the two periods, the gNB may not indicate the COT information or schedule the UE. Scheduling cannot be performed immediately, which may result in wasted resources. In addition, for CORESET and search space monitoring occasions, the minimum waiting time following the preamble is This control resource may be aperiodic, i.e., Presence is determined by the position of the preamble.

[0331] Aperiodic CORESET / search space monitoring occasions are shown in Figure 46. It can be in the same OS as the preamble. This allows for a wait between the preamble and the DCI. This reduces the time required for the process, allowing for better resource utilization.

[0332] The preamble of the DCI carrying the COT information and the DMRS can be QCL signals. Therefore, when a UE receives a preamble in a particular spatial direction, it will receive aperiodic A periodic CORESET is also received, i.e., the aperiodic CORESET is In order to cover all UEs, the gNB is expected to have the same QCL as in Figure 4. 7, the preamble is transmitted multiple times in different spatial directions. The ESET is configured via RRC signaling. The occasions are defined to be aperiodic. For example, the search space monitoring occasions are Occurs only once in relation to the detected preamble. This search space is configured for the UE via RRC signaling, and the offset is determined by the occurrence of the preamble and is not periodic, so it may not have the parameter monitoringSlotPeriodicityAndOffset. Furthermore, the preamble can be in the form of the DMRS of the PDCCH in the CORESET. The gNB can schedule the preamble to be in the form of wideband DMRS to provide sufficient reliability. It may not have the parameter monitoringSlotPeriodicityAndOffset because it is not periodic.

[0333] Furthermore, the preamble can be in the form of the DMRS of the PDCCH in the CORESET. The gNB can schedule the preamble to be in the form of wideband DMRS to provide sufficient reliability.

[0334] Any or all of the apparatuses, systems, methods, and processes described herein can be embodied in the form of computer-executable instructions (e.g., program code) stored in a computer-readable storage medium that causes a processor, such as the processors 118 or 91 of FIGS. 21B and 21F, to execute the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein can be implemented in the form of such computer-executable instructions executed on a processor of an apparatus or computing system configured for at least one of wireless and wired network communications. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. It is understood that when the instructions are executed by a processor such as the processors 118 or 91 of FIGS. 21B and 21F. The systems, methods, and processes described herein can be implemented on a processor of an apparatus or computing system configured for at least one of wireless and wired network communications. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. Specifically, any of the steps, operations, or functions described herein can be implemented in the form of such computer-executable instructions executed on a processor of an apparatus or computing system configured for at least one of wireless and wired network communications. Any of the steps, operations, or functions described herein can be implemented in the form of such computer-executable instructions executed on a processor of an apparatus or computing system configured for at least one of wireless and wired network communications. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, but does not include signals. ​​The tangible readable storage media include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), flash memory or other memory technologies, com pact disc ROM (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, magnetic disc storage, or other magnetic storage devices, or any other arbitrary tangible or physical media that can be used to store desired information and can be accessed by a com puting system, but are not limited thereto.

[0335] When describing the preferred embodiments of the subject matter of the present disclosure, as shown in the figures, specific terms are adopted for clarification. However, the claimed subject matter is not intended to be limited to such selected specific terms, and it should be understood that

[0336] each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose. This written description discloses the present invention, including the best mode, by using examples, and enables any person skilled in the art to practice the present invention, including the creation and use of any device or system and the implementation of any incorporated methods. The It is intended to be within the scope of the claims.

Claims

1. An apparatus comprising a processor, a memory, and a communication circuit, wherein the processor, the memory, and the communication circuit are configured to: Receive a Radio Resource Control (RRC) message, the RRC message including an indication of the number of bits used to indicate a Channel Occupancy Time (COT) in Downlink Control Information (DCI) transmission; Execute a first type of channel access procedure; Receive a first DCI associated with a Slot Format Indicator Radio Network Temporary Identifier (SFI-RNTI), the first DCI including a slot format indication, an indication of the COT according to the number of bits indicated in the RRC message, and a bitmap indicating one or more available sub-bands; Determine the COT from the first DCI; Switch from the first type of channel access procedure to a second type of channel access procedure based at least on the indication of the COT received in the first DCI; Receive a second DCI associated with a Cell Radio Network Temporary Identifier (C-RNTI), the second DCI including an uplink grant indicating a plurality of time domain resource allocations; Perform a Physical Uplink Shared Channel transmission in response to at least one of the plurality of time domain resource allocations during at least a portion of the COT. An apparatus configured to perform the above.

2. The apparatus according to claim 1, wherein the slot format indication indicates that channel access is partially available in a first slot associated with the SFI-RNTI.

3. The apparatus according to claim 2, wherein the slot format indication includes an indication indicating that the channel access is available in one or more first symbols of the first slot.

4. The apparatus according to claim 3, wherein the slot format indication includes an indication indicating that the channel access is not available in one or more second symbols of the first slot.

5. The apparatus according to claim 1, wherein the first DCI is a multicast DCI.

6. The apparatus according to claim 1, wherein the second DCI is a UE-specific DCI.

7. An apparatus comprising a processor, a memory, and a communication circuit, wherein the processor, the memory, and the communication circuit are to transmit a Radio Resource Control (RRC) message, the RRC message including an indication of the number of bits used to indicate a Channel Occupancy Time (COT) in Downlink Control Information (DCI) transmission, to transmit a first DCI associated with a Slot Format Indicator Radio Network Temporary Identifier (SFI-RNTI) to a Wireless Transmit / Receive Unit (WTRU), the first DCI including a slot format indication, an indication of the COT according to the number of bits indicated in the RRC message, and a bitmap indicating one or more available subbands, to transmit a second DCI associated with a Cell Radio Network Temporary Identifier (C-RNTI), the second DCI including an uplink grant indicating a plurality of time domain resource allocations, to receive a Physical Uplink Shared Channel transmission from the WTRU according to at least one of the plurality of time domain resource allocations during at least a part of the COT An apparatus configured to perform **Claim 8** The apparatus according to claim 7, wherein the slot format indication indicates that channel access is partially available in a first slot associated with the SFI-RNTI. **Claim 9** The apparatus according to claim 8, wherein the slot format indication includes an indication indicating that the channel access is available in one or more first symbols of the first slot. **Claim 10** The apparatus according to claim 9, wherein the slot format indication includes an indication indicating that the channel access is not available in one or more second symbols of the first slot. **Claim 11** The apparatus according to claim 7, wherein the first DCI is a multicast DCI. **Claim 12** The apparatus according to claim 7, wherein the second DCI is a UE-specific DCI. **Claim 13** Receiving a Radio Resource Control (RRC) message, the RRC message including an indication of the number of bits used to indicate a Channel Occupancy Time (COT) in downlink control information (DCI) transmission, Performing a first type of channel access procedure, Receiving a first DCI associated with a Slot Format Indicator Radio Network Temporary Identifier (SFI-RNTI), the first DCI including a slot format indication, an indication of the COT according to the number of bits indicated by the RRC message, and a bitmap indicating one or more available subbands, Determining the COT from the first DCI, Switching from the first type of channel access procedure to a second type of channel access procedure based at least on the indication of the COT received in the first DCI Receiving a second DCI associated with a Cell Radio Network Temporary Identifier (C-RNTI), wherein the second DCI includes an uplink grant indicating a plurality of time domain resource allocations, and performing physical uplink shared channel transmission in accordance with at least one of the plurality of time domain resource allocations during at least a portion of the COT A method comprising:

14. The method of claim 13, wherein the slot format indication indicates that channel access is partially available in a first slot associated with the SFI-RNTI.

15. The method of claim 14, wherein the slot format indication includes an indication that channel access is available in one or more first symbols of the first slot and an indication that channel access is not available in one or more second symbols of the first slot.

16. The method of claim 13, wherein the first DCI is a multicast DCI.

17. The method of claim 13, wherein the second DCI is a UE-specific DCI.

18. A wireless transmit / receive unit (WTRU) comprising a processor, a memory, and a communication circuit, wherein the processor, the memory, and the communication circuit are configured to: receive a radio resource control (RRC) message, the RRC message including an indication of the number of bits used to indicate a channel occupancy time (COT) in downlink control information (DCI) transmission, and perform a first type of channel access procedure Receiving a first DCI associated with a Slot Format Indicator Radio Network Temporary Identifier (SFI-RNTI), wherein the first DCI includes a slot format indication, an indication of the COT based on the number of bits indicated in the RRC message, and a bitmap indicating one or more available sub-bands, and the first DCI indicates that the WTRU is capable of switching from a first type of channel access procedure to a second type of channel access procedure, Determining the COT from the first DCI, Receiving a second DCI associated with a Cell Radio Network Temporary Identifier (C-RNTI), wherein the second DCI includes an uplink grant indicating a plurality of time domain resource allocations, Performing physical uplink shared channel transmission in accordance with at least one of the plurality of time domain resource allocations during at least a portion of the COT A WTRU configured to perform the above.

19. The WTRU according to claim 18, wherein the slot format indication indicates that channel access is partially available in a first slot associated with the SFI-RNTI.

20. The WTRU according to claim 19, wherein the slot format indication includes an indication indicating that channel access is available in one or more first symbols of the first slot.

Images