Method and apparatus for transmitting and receiving a signal in a wireless communication system

Abstract

In an example embodiment, a method performed by a relay UE in a wireless communication system is provided. The method includes receiving, from a BS, a paging configuration including at least one of a number of total paging frames, a number of paging occasions of a paging frame, an offset of the paging frame, a first DRX cycle of a remote UE, or a paging search space; transmitting, to the remote UE, the paging configuration; receiving, from the remote UE, information related to the remote UE including at least one of an identification of the remote UE, a paging identification of the remote UE, or a second DRX cycle of the remote UE; identifying a paging occasion of the remote UE based on the information related to the remote UE and the paging configuration; and monitoring the paging occasion of the remote UE in order to receive a paging message of the remote UE.

Description

Technical Field

[0001] This application generally relates to wireless communication systems, and more specifically, this disclosure relates to determining the availability of reference signals, sending and receiving paging by a relay UE, and sending and receiving paging by a relay UE for a remote UE. Background Technology

[0002] To meet the increasing demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or near-5G communication systems. 5G or near-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technologies are discussed for 5G communication systems. Furthermore, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), receiver interference cancellation, and more. In 5G systems, hybrid frequency shift keying (FSK) and Feher quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The internet, a human-centric network in which humans generate and consume information, has now evolved into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, a product of combining IoT technology and big data processing technology through connections to cloud servers. Because the concrete implementation of IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). Such IoT environments can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields through the convergence and combination of existing information technology (IT) with various industrial applications, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communication can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology can also be seen as an example of the connection between 5G and IoT technologies.

[0005] As mentioned above, various services can be provided based on the development of wireless communication systems, and therefore a method for easily providing such services is needed. Summary of the Invention

[0006] Solution

[0007] In an exemplary embodiment, a method performed by a relay user equipment (UE) in a wireless communication system is provided. The method includes receiving a paging configuration from a base station (BS), the paging configuration including at least one of a total number of paging frames, a number of paging timings for paging frames, a paging frame offset, a first DRX cycle of a remote UE, or a paging search space; sending the paging configuration to the remote UE; receiving information related to the remote UE from the remote UE, including at least one of an identifier of the remote UE, a paging identifier of the remote UE, or a second DRX cycle of the remote UE; identifying the paging timing of the remote UE based on the information related to the remote UE and the paging configuration; and monitoring the paging timing of the remote UE for receiving paging messages from the remote UE. Attached Figure Description

[0008] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which the same reference numerals denote the same parts:

[0009] Figure 1 A diagram illustrating sidelink communication according to an embodiment of the present disclosure is shown;

[0010] Figure 2 A flowchart is shown of a method performed by a UE to identify a single notification of TRS and CSI RS in a short message according to an embodiment of the present disclosure;

[0011] Figure 3 A flowchart is shown illustrating a method performed by a UE to identify separate notifications of TRS and CSI RS in a short message according to an embodiment of the present disclosure;

[0012] Figure 4 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify a single notification of TRS and CSI RS in a DCI of a PDCCH addressed to P-RNTI sent during paging timing;

[0013] Figure 5 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify separate notifications of TRS and CSI RS in the DCI of the PDCCH addressed to the P-RNTI sent during paging timing;

[0014] Figure 6 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify a single notification of TRS and CSI RS in a DCI of a PDCCH addressed to RNTI sent at the wake-up signal or early paging indication timing.

[0015] Figure 7 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify separate notifications of TRS and CSI RS in a DCI of a PDCCH addressed to RNTI sent at the wake-up signal or early paging indication timing.

[0016] Figure 8 A diagram illustrating a method for sending and receiving paging messages in a DCI of a wake-up signal or an early paging indication, according to an embodiment of the present disclosure;

[0017] Figure 9 A diagram is shown illustrating a scenario where scheduling information in the DCI of the first PDCCH and the scheduling information in the DCI of the second PDCCH are used for paging messages, according to an embodiment of the present disclosure.

[0018] Figure 10A diagram is shown illustrating a scenario where scheduling information in the DCI of the first PDCCH and scheduling information in the DCI of the second PDCCH are used for paging messages, according to an embodiment of the present disclosure.

[0019] Figure 11 A flowchart of a method for monitoring paging of a remote UE according to an embodiment of the present disclosure is shown;

[0020] Figure 12 A flowchart of a method for monitoring paging of a remote UE according to an embodiment of the present disclosure is shown;

[0021] Figure 13 A flowchart of a method for monitoring paging of a remote UE according to an embodiment of the present disclosure is shown;

[0022] Figure 14 A diagram illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure;

[0023] Figure 15 A diagram illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure;

[0024] Figure 16 A diagram illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure;

[0025] Figure 17 A diagram illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure;

[0026] Figure 18 This is a diagram showing a list of RACH configurations according to embodiments of this disclosure;

[0027] Figure 19 This is a diagram showing a list of RACH configurations according to embodiments of this disclosure;

[0028] Figure 20 This is a diagram showing a list of RACH configurations according to embodiments of this disclosure;

[0029] Figure 21 A diagram illustrating a UE according to an embodiment of the present disclosure; and

[0030] Figure 22 This is a diagram illustrating a base station according to an embodiment of the present disclosure.

[0031] Optimal Implementation

[0032] In an exemplary embodiment, a method performed by a relay user equipment (UE) in a wireless communication system is provided. The method includes receiving a paging configuration from a base station (BS), the paging configuration including at least one of a total number of paging frames, a number of paging timings for paging frames, a paging frame offset, a first DRX cycle of a remote UE, or a paging search space; sending the paging configuration to the remote UE; receiving information related to the remote UE from the remote UE, including at least one of an identifier of the remote UE, a paging identifier of the remote UE, or a second DRX cycle of the remote UE; identifying the paging timing of the remote UE based on the information related to the remote UE and the paging configuration; and monitoring the paging timing of the remote UE for receiving paging messages from the remote UE.

[0033] In one embodiment, identifying the paging timing of a remote UE includes identifying a third DRX cycle based on at least one of a first DRX cycle or a second DRX cycle; identifying a paging frame of a remote UE based on at least one of the third DRX cycle, the identifier of the remote UE, the offset of the paging frame, or the total number of paging frames; and identifying the paging timing of a remote UE based on the identifier of the remote UE, the total number of paging frames, and the number of paging timings of the paging frames.

[0034] In an exemplary embodiment, the second DRX cycle of the remote UE is identified based on at least one of the DRX cycle configured for the remote UE by the upper layer or the DRX cycle configured for the remote UE by the base station.

[0035] In an exemplary embodiment, the method further includes: receiving downlink control information (DCI) via a physical downlink control channel (PDCCH) addressing a paging radio network temporary identifier (P-RNTI) during a paging event of a remote UE; obtaining a paging message based on the DCI; and identifying whether the paging message includes a paging identifier of the remote UE; wherein the paging identifier includes at least one of a 5G-S-Temporary Mobile Subscriber Identity (TMSI) of the remote UE or an inactive radio network temporary identifier (I-RNIT) of the remote UE.

[0036] In an exemplary embodiment, identifying whether a paging message includes a paging identifier of a remote UE includes: in response to identifying that the paging message includes a paging identifier of a remote UE, sending a message indicating that the remote UE is paging to the remote UE; wherein the paging message includes the 5G-S-TMSI of the remote UE, the message includes information indicating that the paging corresponds to a core network paging, and wherein the paging message includes the I-RNTI of the remote UE, the message includes information indicating that the paging corresponds to a radio network paging.

[0037] In an exemplary embodiment, the method further includes: receiving a request message from a remote UE to monitor paging messages of the remote UE when the relay UE is in a radio resource control (RRC) connection state; sending a message to the BS indicating that the relay UE needs to monitor paging messages of the remote UE; receiving from the BS a message indicating that the active bandwidth portion (BWP) of the relay UE is configured with a search space for monitoring paging messages of the remote UE; and monitoring paging messages of the remote UE based on the active BWP of the relay UE.

[0038] In an exemplary embodiment, the method further includes: sending a message to the BS including a paging identifier of a remote UE; receiving from the BS a message instructing a relay UE to page a remote UE based on the paging identifier of the remote UE; and receiving from the BS an RRC message including a paging identifier of at least one paged remote UE.

[0039] In an exemplary embodiment, a method performed by a remote user equipment (UE) in a wireless communication system includes: receiving a paging configuration from a relay user equipment (UE), wherein the paging configuration includes at least one of a total number of paging frames, a number of paging timings for paging frames, a paging frame offset, a first DRX period of the remote UE, or a paging search space; and sending information related to the remote UE to the relay UE, including at least one of an identifier of the remote UE, a paging identifier of the remote UE, or a second DRX period of the remote UE; wherein the relay UE identifies the paging timing of the remote UE based on the information related to the remote UE and the paging configuration; and wherein the relay UE monitors the paging timing of the remote UE for receiving paging messages from the remote UE.

[0040] In an exemplary embodiment, a third DRX cycle is identified based on at least one of a first DRX cycle or a second DRX cycle; a paging frame of a remote UE is identified based on at least one of the third DRX cycle, the identifier of the remote UE, the offset of the paging frame, or the total number of paging frames; and the paging timing of the remote UE is identified based on the identifier of the remote UE, the total number of paging frames, and the number of paging timings of the paging frames.

[0041] In an exemplary embodiment, the method further includes: identifying a second DRX cycle of the remote UE based on at least one of a DRX cycle configured by the upper layer for the remote UE or a DRX cycle configured by the base station for the remote UE.

[0042] In an exemplary embodiment, a relay UE receives downlink control information (DCI) via a physical downlink control channel (PDCCH) addressing a paging radio network temporary identifier (P-RNTI) during a paging event of a remote UE; a paging message is obtained based on the DCI; and it is identified whether the paging message includes a paging identifier of the remote UE, wherein the paging identifier includes at least one of the remote UE's 5G-S-Temporary Mobile Subscriber Identity (TMSI) or the remote UE's Inactive Radio Network Temporary Identifier (I-RNIT).

[0043] In an exemplary embodiment, the method further includes: in response to identifying that the paging message includes a paging identifier of a remote UE, receiving from a relay UE a message indicating a paging of a remote UE; wherein the paging message includes a 5G-S-TMSI of the remote UE, the message includes information indicating that the paging corresponds to a core network paging, and wherein the paging message includes an I-RNTI of the remote UE, the message includes information indicating that the paging corresponds to a radio network paging;

[0044] In an exemplary embodiment, the method further includes: when the relay UE is in a Radio Resource Control (RRC) connection state, sending a request message to the relay UE to monitor paging messages of a remote UE; wherein a message indicating that the relay UE needs to monitor paging messages of a remote UE is sent by the relay UE to the BS, wherein a message indicating that the active bandwidth portion (BWP) of the relay UE is configured with a search space for monitoring paging messages of a remote UE is received by the relay UE from the BS; and wherein the paging messages of the remote UE are monitored based on the active BWP of the relay UE.

[0045] In an exemplary embodiment, a message including the paging identifier of a remote UE is sent from a relay UE to a BS, a message instructing the relay UE to paging a remote UE based on the paging identifier of the remote UE is received by the relay UE from the BS, and an RRC message including the paging identifier of at least one paged remote UE is received by the relay UE from the BS.

[0046] In an exemplary embodiment, a relay user equipment (UE) in a wireless communication system is provided. The relay UE includes: a transceiver; and at least one processor connected to the transceiver and configured to: receive paging configuration from a base station (BS), the paging configuration including at least one of the following: the total number of paging frames, the number of paging timings of paging frames, the offset of paging frames, a first DRX cycle of a remote UE, or a paging search space; send the paging configuration to a remote UE; receive information related to the remote UE from the remote UE, including at least one of the following: the identifier of the remote UE, the paging identifier of the remote UE, or a second DRX cycle of the remote UE; identify the paging timing of the remote UE based on the information related to the remote UE and the paging configuration; and monitor the paging timing of the remote UE for receiving paging messages from the remote UE.

[0047] In an exemplary embodiment, at least one processor is configured to: identify a third DRX cycle based on at least one of a first DRX cycle or a second DRX cycle; identify a paging frame of a remote UE based on at least one of the third DRX cycle, the identifier of the remote UE, the offset of the paging frame, or the total number of paging frames; and identify the paging timing of the remote UE based on the identifier of the remote UE, the total number of paging frames, and the number of paging timings of the paging frames.

[0048] In an exemplary embodiment, the second DRX cycle of the remote UE is identified based on at least one of the DRX cycle configured for the remote UE by the upper layer or the DRX cycle configured for the remote UE by the base station.

[0049] In an exemplary embodiment, at least one processor is configured to: receive downlink control information (DCI) via a physical downlink control channel (PDCCH) addressing a paging radio network temporary identifier (P-RNTI) during a paging event of a remote UE; obtain a paging message based on the DCI; and identify whether the paging message includes a paging identifier of the remote UE; wherein the paging identifier includes at least one of a 5G-S-Temporary Mobile Subscriber Identity (TMSI) of the remote UE or an inactive radio network temporary identifier (I-RNIT) of the remote UE.

[0050] In an exemplary embodiment, at least one processor is configured to: receive a request message from a remote UE to monitor paging messages of the remote UE when the relay UE is in a Radio Resource Control (RRC) connection state; send a message to the BS indicating that the relay UE needs to monitor paging messages of the remote UE; receive from the BS a message indicating that the active bandwidth portion (BWP) of the relay UE is configured with a search space for monitoring paging messages of the remote UE; and monitor paging messages of the remote UE based on the active BWP of the relay UE.

[0051] In an exemplary embodiment, at least one processor is configured to: send a message to a BS including a paging identifier of a remote UE; receive from the BS a message instructing a relay UE to paging a remote UE based on the paging identifier of the remote UE; and receive from the BS an RRC message including a paging identifier of at least one paging remote UE. Detailed Implementation

[0052] The following discussion Figures 1 to 22 The various embodiments used to describe these principles of the disclosure in this patent document are merely illustrative and should not be construed in any way as limiting the scope of the disclosure. Those skilled in the art will understand that the principles of the disclosure can be implemented in any suitably arranged system or apparatus.

[0053] Throughout this disclosure, the expression "at least one of a, b, or c" indicates only a; only b; only c; both a and b; both a and c; both b and c; all of a, b, and c, or variations thereof. Throughout the specification, a layer (or layer device) may also be referred to as an entity. The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. Well-known functions or configurations are not described in detail in the following description, as they would obscure this disclosure with unnecessary detail. The terminology used in this specification is defined with reference to the functions used in this disclosure and may be changed according to the intent or common practice of the user or operator. Therefore, the definitions of the terms should be understood based on the entire description of this specification.

[0054] For the same reason, some elements may be exaggerated, omitted, or roughly shown in the accompanying drawings. Additionally, the size of each element does not exactly correspond to its actual size. In each drawing, the same or corresponding elements are given the same reference numerals.

[0055] The advantages and features of this disclosure, as well as methods for achieving said advantages and features, can be more readily understood by referring to the following detailed description of embodiments and accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of this disclosure to those skilled in the art. Therefore, the scope of this disclosure is defined by the appended claims. Throughout this specification, the same reference numerals refer to the same elements. It will be understood that the blocks in a flowchart or combination of flowcharts can be executed by computer program instructions. Since these computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing apparatus, the instructions, which are executed by the processor of the computer or other programmable data processing apparatus, create units for performing the functions described in the flowchart blocks.

[0056] Computer program instructions can be stored in a computer-usable or computer-readable storage medium capable of directing a computer or other programmable data processing device to perform functions in a particular manner. Therefore, the instructions stored in the computer-usable or computer-readable storage medium can also produce an article of art containing instruction units for performing the functions described in the flowchart block. The computer program instructions can also be loaded into a computer or other programmable data processing device, and thus, instructions for operating the computer or other programmable data processing device by generating a process executed by the computer when a series of operations are performed in the computer or other programmable data processing device can provide operations for performing the functions described in the flowchart block.

[0057] Furthermore, each box can represent a module, section, or part of code, which includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in a box can occur out of order. For example, depending on their corresponding functions, two consecutive boxes can be executed simultaneously or in reverse order.

[0058] As used herein, the term "cell" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), that performs a certain function. However, the term "cell" is not limited to software or hardware. A "cell" can be formed to be stored in an addressable memory medium or to operate one or more processors. Thus, for example, the term "cell" can include elements (e.g., software elements, object-oriented software elements, class elements, and task elements), processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables.

[0059] The functionality provided by the elements and "units" can be combined with a smaller number of elements and "units," or can be divided into additional elements and "units." Furthermore, elements and "units" can be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card. Additionally, in embodiments of this disclosure, a "unit" may include at least one processor. In the following description of this disclosure, well-known functions or configurations are not described in detail, as such details would obscure this disclosure unnecessarily.

[0060] In the following text, for ease of explanation, this disclosure uses the terms and names defined in the 3GPP LTE standard. However, this disclosure is not limited to the stated terms and names, but may also be applied to systems conforming to other standards.

[0061] In this disclosure, for ease of explanation, the evolved Node B (eNB) can be used interchangeably with the next-generation Node B (gNB). That is, a base station (BS) described by an eNB can represent a gNB. In the following description, the term "base station" refers to an entity used to allocate resources to a user equipment (UE) and can be used interchangeably with at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller (BSC), or node on a network. The term "terminal" can be used interchangeably with a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. However, this disclosure is not limited to the foregoing examples. Specifically, this disclosure applies to the 3GPP New Radio (NR) (or 5G) mobile communication standard. In the following description, for ease of explanation, the term eNB can be used interchangeably with the term gNB. That is, a base station interpreted as an eNB can also indicate a gNB. The term UE can also indicate a mobile phone, NB-IoT device, sensor, and other wireless communication device.

[0062] The following discussion Figures 1 to 22 The various embodiments described in this patent document to illustrate the principles of this disclosure are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0063] In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband subscribers and provide more and better applications and services. Second-generation wireless communication systems have been developed to provide voice services while ensuring user mobility. Third-generation wireless communication systems support not only voice services but also data services. Fourth-generation wireless communication systems have been developed in recent years to provide high-speed data services. However, currently, fourth-generation wireless communication systems suffer from resource shortages and cannot meet the growing demand for high-speed data services. Therefore, fifth-generation wireless communication systems (also known as next-generation radio or NR) are being developed to meet the growing demand for high-speed data services and support ultra-reliable and low-latency applications.

[0064] Fifth-generation (5G) wireless communication systems support not only lower frequency bands but also higher frequency (millimeter-wave) bands, such as the 10GHz to 100GHz band, to achieve higher data rates. To mitigate radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are considered in the design of 5G wireless communication systems. Furthermore, 5G wireless communication systems are expected to address diverse use cases with completely different requirements in terms of data rate, latency, reliability, and mobility. However, the air interface design of 5G wireless communication systems is expected to be flexible enough to serve UEs with vastly different performance characteristics, depending on the use case and market segment the UE serves for the end customer. Several example use cases that 5G wireless communication systems are expected to address include enhanced mobile broadband (eMBB), massive machine-type communication (m-MTC), and ultra-reliable low latency communication (URLL). eMBB requirements (such as tens of Gbps data rates, low latency, and high mobility) address the market segment representing regular wireless broadband subscribers who actively require internet connectivity anytime, anywhere. m-MTC requirements (such as extremely high connection density, infrequent data transfer, ultra-long battery life, and low mobility addresses) address the market segment representing connectivity for the billions of devices envisioned in the Internet of Things (IoT) / Internet of Everything (IoE). URLL requirements (such as extremely low latency, extremely high reliability, and variable mobility) address the market segment representing industrial automation applications (i.e., vehicle-to-vehicle / vehicle-to-infrastructure communication, which is foreseeable as one of the driving forces behind autonomous vehicles).

[0065] In fifth-generation wireless communication systems operating in higher frequency (millimeter-wave) bands, UEs and gNBs use beamforming to communicate with each other. Beamforming technology is used to mitigate propagation path loss and increase propagation distance for communication at higher frequency bands. Beamforming enhances the transmission and reception performance using high-gain antennas. Beamforming can be classified into transmit (TX) beamforming performed at the transmitting end and receive (RX) beamforming performed at the receiving end. Generally, TX beamforming increases directivity by allowing the area that the propagation can reach to be densely located in a specific direction using multiple antennas. In this case, the aggregation of multiple antennas can be called an antenna array, and each antenna included in the array can be called an array element. Antenna arrays can be configured in various forms, such as linear arrays, planar arrays, etc. The use of TX beamforming results in increased signal directivity, thereby increasing propagation distance. Furthermore, since the signal is almost never transmitted in directions other than the directive direction, signal interference acting on another receiver is significantly reduced. The receiver can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the strength of an RX signal transmitted in a specific direction by allowing propagation to be concentrated in that direction, and excludes signals transmitted in directions other than that specific direction from the RX signal, thus providing a blocking effect against interfering signals. By using beamforming techniques, a transmitter can generate multiple transmit beam patterns in different directions. Each of these transmit beam patterns can also be referred to as a transmit (TX) beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals within a cell because each narrow TX beam provides coverage to a portion of the cell. The narrower the TX beam, the higher the antenna gain, and therefore the greater the propagation distance of a signal transmitted using beamforming. Receivers can also generate multiple receive (RX) beam patterns in different directions. Each of these receive patterns can also be referred to as a receive (RX) beam.

[0066] CA / Multi-Connectivity in 5G Wireless Communication Systems: 5G wireless communication systems support independent operating modes as well as dual connectivity (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or NBs) via a non-ideal backhaul connection. One node acts as the primary node (MN), and the other as the secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports Multi-RAT Dual Connectivity (MR-DC) operation, which configures a UE in RRC_CONNECTED to utilize radio resources provided by two different schedulers located in two different nodes via a non-ideal backhaul connection, providing E-UTRA (i.e., if the node is an ng-eNB) or NR access (i.e., if the node is a gNB). In an NR for a UE in RRC_CONNECTED without CA / DC configuration, there is only one serving cell, which includes the primary cell. For a UE in RRC_CONNECTED with CA / DC configuration, the term 'serving cell' is used to refer to the set of cells consisting of the primary cell and all secondary cells. In NR, the term Primary Cell Group (MCG) refers to the serving cell group associated with the primary node, which includes PCells and optionally one or more SCells. In NR, the term Secondary Cell Group (SCG) refers to the serving cell group associated with the secondary node, which includes PSCells and optionally one or more SCells. In NR, a PCell (primary cell) is the serving cell in the MCG operating at the primary frequency, where the UE performs the initial connection establishment procedure or initiates a connection re-establishment procedure. In NR with a UE configured with CA, an Scell ​​is a cell that provides additional radio resources above a special cell. The primary SCG cell (PSCell) is the serving cell in the SCG, where the UE performs random access during reconfiguration with a synchronization procedure. For dual connectivity operation, the term SpCell (i.e., special cell) refers to either the PCell of the MCG or the PSCell of the SCG; otherwise, the term special cell refers to the PCell.

[0067] In fifth-generation wireless communication systems, the Physical Downlink Control Channel (PDCCH) is used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The downlink control information (DCI) on the PDCCH includes: downlink assignment containing at least modulation and coding formats, resource allocation, and hybrid HARQ information related to the DL-SCH; and uplink scheduling clearance containing at least modulation and coding formats, resource allocation, and hybrid ARQ information related to the UL-SCH. Besides scheduling, the PDCCH can be used for: activating and deactivating configured PUSCH transmissions with configured clearance; activating and deactivating PDSCH semi-persistent transmissions; notifying one or more UEs of slot formats; notifying one or more UEs of PRB and OFDM symbols, where the UE may assume there are no transmissions for the UE; transmitting TPC commands for the PUCCH and PUSCH; transmitting one or more TPC commands for SRS transmissions for one or more UEs; switching the active bandwidth portion of a UE; and initiating a random access procedure. Based on the corresponding search space configuration, the UE monitors the PDCCH candidate set during configured monitoring times within one or more configured control resource sets (CORESETs). A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. Within a CORESET, resource element groups (REGs) and control channel elements (CCEs) are defined, with each CCE consisting of a set of REGs. The control channel is formed by aggregating CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE-to-REG mappings are supported in the CORESET. Polarity coding is used for the PDCCH. Each resource element group carrying the PDCCH carries its own DMRS. QPSK modulation is used for the PDCCH.

[0068] In fifth-generation wireless communication systems, for each configured BWP of the serving cell, the gNB signals a list of search space configurations, where each search configuration is uniquely identified by a search space identifier. The search space identifier is unique within the serving cell's BWP. The gNB explicitly signals the identifier of the search space configuration for each configured BWP, which will be used for specific purposes, such as paging reception, SI reception, and random access response reception. In NR, the search space configuration includes parameter monitoring-periodic-PDCCH-slot, monitoring-offset-PDCCH-slot, intra-slot monitoring-symbol-PDCCH, and duration. The UE uses the parameter PDCCH monitoring period (monitoring-periodic-PDCCH-slot), PDCCH monitoring offset (monitoring-offset-PDCCH-slot), and PDCCH monitoring mode (intra-slot monitoring-symbol-PDCCH) to determine one or more PDCCH monitoring opportunities within a slot. PDCCH monitoring opportunities exist in slot "x" to x+ duration, where the slot with number "x" in a radio frame with number "y" satisfies the following equation:

[0069] (y*(number of slots in a radio frame)+x-monitoring-offset-PDCCH-slot)mod(monitoring-periodicity-PDCCH-slot)=0

[0070] The start symbol of the PDCCH monitoring opportunity in each time slot with a PDCCH monitoring opportunity is given by the in-slot-monitor-symbol-PDCCH. The length of the PDCCH monitoring opportunity (in symbols) is given in the coreset associated with the search space. The search space configuration includes the identifier of the coreset configuration associated with it. For each configured BWP of the serving cell, the GNB signals a list of coreset configurations, where each coreset configuration is uniquely identified by a coreset identifier. The coreset identifier is unique in the BWP of the serving cell. It should be noted that each radio frame has a duration of 10 ms. Radio frames are identified by radio frame number or system frame number. Each radio frame includes multiple time slots, where the number of time slots in the radio frame and the duration of the time slots depend on the subcarrier spacing. The number of time slots in the radio frame and the duration of the time slots depend on the radio frames of each supported SCS and are predefined in the NR. Each coreset configuration is associated with a TCI (Transmission Configuration Indicator) list state. A DL RS ID (SSB or CSI RS) is configured for each TCI state. The gNB sends a list of TCI states corresponding to the coreset configuration via RRC signaling. One of the TCI states in the TCI state list is activated by the gNB and indicated to the UE. The TCI state indication is used by the GNB to transmit the DL TX beam of the PDCCH during the PDCCH monitoring time in the search space (the DL TX beam is quasi-co-located (QCL) with the SSB / CSI RS of the TCI state).

[0071] Bandwidth Adaptive (BA) Operation in 5G Wireless Communication Systems: 5G wireless communication systems support bandwidth adaptation (BA). With BA, the UE's receive and transmit bandwidth does not need to be as large as the cell's bandwidth and can be adjusted: bandwidth can be commanded to change (e.g., shrinking during less active periods to save power); location can be moved in the frequency domain (e.g., to improve scheduling flexibility); and subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the cell's total bandwidth is called the Bandwidth Part (BWP). BA is implemented by configuring a BWP for the RRC-connected UE and informing the UE which configured BWP is currently active. When configuring BA, the UE only needs to monitor the PDCCH on one active BWP; that is, it does not need to monitor the PDCCH on the entire DL frequency of the serving cell. In RRC-connected state, one or more DL and UL BWPs are configured for the UE for each configured serving cell (i.e., PCell or SCell). For an active serving cell, there will always be one active UL and DL BWP at any given time. Serving cell BWP handover is used to simultaneously activate inactive BWPs and deactivate active BWPs. BWP handover is controlled by the PDCCH indicating downlink assignment or uplink clearance, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself after the random access procedure. After adding a SpCell or activating an SCell, the DL BWP and ULBWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, respectively, are active without receiving the PDCCH indicating downlink assignment or uplink clearance. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP handover is shared for both UL and DL. After the BWP inactivity timer expires, the UE will switch the active DL BWP to the default DL BWP or the initial DL BWP (if the default DL BWP is not configured).

[0072] Random Access in 5G Wireless Communication Systems: Random access (RA) is supported in 5G wireless communication systems. RA is used for uplink (UL) time synchronization. RA is used during: initial access, handover, Radio Resource Control (RRC) connection re-establishment procedures, scheduling request transmissions, secondary cell group (SCG) addition / modification, beam fault recovery, and data or control information transmissions in the UL via asynchronous UEs in RRC CONNECTED state. Several types of random access procedures are supported, such as contention-based random access and contention-free random access, each of which can be a 2-step or 4-step random access procedure.

[0073] Contention-Based Random Access (CBRA): This is also known as 4-step CBRA. In this type of random access, the UE first sends a random access preamble (also known as Msg1) and then waits for a random access response (RAR) within the RAR window. The RAR is also known as Msg2. The next-generation node B (gNB) sends the RAR on the Physical Downlink Shared Channel (PDSCH). The PDCCH that schedules the PDSCH carrying the RAR is addressed to the RA-Radio Network Temporary Identifier (RA-RNTI). The RA-RNTI identifies the time-frequency resource (also known as the Physical RA Channel (PRACH) timing, PRACH Transmission (TX) timing, or RA Channel (RACH) timing) where the gNB detects the RA preamble. The RA-RNTI is calculated as follows: RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id, where s_id is the index of the first Orthogonal Frequency Division Multiplexing (OFDM) symbol of the PRACH timing in which the UE transmits Msg1, i.e., the RA preamble; 0 ≤ s_id < 14; t_id is the index of the first slot of the PRACH timing (0 ≤ t_id < 80); f_id is the index of the PRACH timing within the slot in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for transmission of Msg1 (0 for normal UL (NUL) carrier and 1 for supplementary UL (SUL) carrier). The gNB can multiplex several RARs of various random access preambles detected by the gNB within the same RAR Media Access Control (MAC) Protocol Data Unit (PDU). If the RAR includes the RA preamble identifier (RAPID) of the RA preamble sent by the UE, then the RAR in the MAC PDU corresponds to the UE's RA preamble transmission. If no RAR corresponding to its RA preamble transmission is received during the RAR window, and the UE has not yet transmitted the RA preamble a configurable number of times (configured by the gNB in ​​the RACH configuration), the UE returns to step one, i.e., selects random access resources (preamble / RACH timing) and transmits the RA preamble. Backoff can be applied before returning to step one.

[0074] If a RAR corresponding to its RA preamble is received, the UE sends message 3 (Msg3) in the UL clearance received in the RAR. Msg3 includes messages such as RRC connection request, RRC connection re-establishment request, RRC handover confirmation, scheduling request, SI request, etc. It may include the UE identifier (i.e., Cell-Radio Network Temporary Identifier (C-RNTI) or System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identifier (S-TMSI) or a random number). After sending Msg3, the UE starts a contention resolution timer. While the contention resolution timer is running, if the UE receives a Physical Downlink Control Channel (PDCCH) addressed to the C-RNTI included in Msg3, contention resolution is considered successful, the contention resolution timer stops, and the RA process is completed. While the contention resolution timer is running, if the UE receives a Contention Resolution MAC Control Element (CE) including the UE's contention resolution identifier (the first X bits of the Common Control Channel (CCCH) Service Data Unit (SDU) sent in Msg3), contention resolution is considered successful, the contention resolution timer stops, and the RA process is completed. If the contention resolution timer expires and the UE has not yet sent a configurable number of RA preambles, the UE returns to step one, i.e., selects random access resources (preamble / RACH timing) and sends the RA preamble. Backoff can be applied before returning to step one.

[0075] Contention-Free Random Access (CFRA): This is also known as Traditional CFRA or 4-Step CFRA. The CFRA procedure is used in scenarios requiring low latency handovers and early timing establishment of secondary cells (Scells). The ENB assigns a dedicated random access preamble to the UE. The UE sends the dedicated RA preamble. The ENB sends a RAR on the PDSCH addressed to the RA-RNTI. The RAR conveys the RA preamble identifier and timing alignment information. The RAR may also include UL clearance. The RAR is sent in a RAR window similar to the Contention-Based RA (CBRA) procedure. CFRA is considered successfully completed upon receiving a RAR including the RA preamble identifier (RAPID) of the RA preamble sent by the UE. In the case of initiating RA for beam fault recovery, CFRA is considered successfully completed if a PDCCH addressed to the C-RNTI is received in the search space used for beam fault recovery. If the RAR window expires and the RA is not successfully completed, and the UE has not yet sent the RA preamble a configurable number of times (configured by gNB in ​​the RACH configuration), the UE will resend the RA preamble.

[0076] For certain events, such as handover and beam failure recovery, if one or more dedicated preambles are assigned to the UE, the UE determines whether to send a dedicated or non-dedicated preamble during the first step of random access, i.e., during the random access resource selection for Msg1. Typically, dedicated preambles are provided for a subset of SSB / CSI-RS. If none of the SSB / CSI RSs for which the gNB has provided contention-free random access resources (i.e., dedicated preambles / ROs) has a DL RSRP above a threshold, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during the RA process, one random access attempt can be CFRA, while other random access attempts can be CBRA.

[0077] Two-Step Contention-Based Random Access (2-Step CBRA): In the first step, the UE transmits a random access preamble on the PRACH and a payload (i.e., a MAC PDU) on the PUSCH. The transmission of the random access preamble and payload is also referred to as MsgA. In the second step, after transmitting MsgA, the UE monitors for a response from the network (i.e., the gNB) within a configured window. This response is also referred to as MsgB. If a CCCH SDU is transmitted in the MsgA payload, the UE uses the contention resolution information in MsgB to perform contention resolution. If the contention resolution identifier received in MsgB matches the first 48 bits of the CCCH SDU transmitted in MsgA, contention resolution is successful. If a C-RNTI is transmitted in the MsgA payload, contention resolution is successful if the UE receives a PDCCH addressed to the C-RNTI. If contention resolution is successful, the random access procedure is considered successfully completed. MsgB may include backoff information corresponding to the random access preamble sent in MsgA, instead of contention resolution information corresponding to MsgA. If backoff information is received, the UE sends Msg3 and performs contention resolution using Msg4 as in the CBRA procedure. If contention resolution is successful, the random access procedure is considered to have completed successfully. If contention resolution fails during backoff (i.e., when sending Msg3), the UE retransmits MsgA. If the configuration window for monitoring network response expires after the UE sends MsgA and the UE does not receive MsgB including contention resolution or backoff information as described above, the UE retransmits MsgA. If the random access procedure is not successfully completed even after sending a configurable number of MsgA steps, the UE backoffs to the 4-step RACH procedure, i.e., the UE only sends the PRACH preamble.

[0078] The MsgA payload may include one or more of the following: Common Control Channel (CCCH) Service Data Unit (SDU), Dedicated Control Channel (DCCH) SDU, Dedicated Flow Channel (DTCH) SDU, Buffer Status Report (BSR) MAC Control Element (CE), Power Headroom Report (PHR) MAC CE, SSB information, C-RNTI MAC CE, or padding. MsgA may include the UE ID (e.g., Random ID, S-TMSI, C-RNTI, Recovery ID, etc.) and the preamble from the first step. The UE ID may be included in the MAC PDU of MsgA. UE IDs such as C-RNTI may be carried in the MAC CE, which is included in the MAC PDU. Other UE IDs (such as Random ID, S-TMSI, C-RNTI, Recovery ID, etc.) may be carried in the CCCH SDU. The UE ID may be one of the following: Random ID, S-TMSI, C-RNTI, Recovery ID, IMSI, Idle Mode ID, Inactive Mode ID, etc. The UE ID may differ depending on the UE's execution of the RA procedure. When a UE performs a Reset Request (RA) after power-on (before it is attached to the network), the UE ID is a random ID. When a UE performs an idle RA after it is attached to the network, the UE ID is the S-TMSI. If the UE has an assigned C-RNTI (e.g., in a connected state), the UE ID is the C-RNTI. When the UE is in an inactive state, the UE ID is the recovery ID. In addition to the UE ID, some additional control information can be sent in the MsgA. The control information can be included in the MAC PDU of the MsgA. The control information may include one or more of the following: connection request indication, connection restoration request indication, SI request indication, buffer status indication, beam information (e.g., one or more DL TX beam IDs or one or more SSB IDs), beam failure recovery indication / information, data indicator, cell / BS / TRP handover indication, connection re-establishment indication, reconfiguration completion or handover completion message, etc.

[0079] Two-Step Contention-Free Random Access (2-Step CFRA): In this case, the gNB assigns a dedicated random access preamble and PUSCH resources to the UE for MsgA transmission. It may also indicate the RO (Resource Allocation) for preamble transmission. In the first step, the UE transmits the random access preamble on the PRACH and the payload on the PUSCH using the contention-free random access resources (i.e., dedicated preamble / PUSCH resources / RO). In the second step, after transmitting MsgA, the UE monitors for responses from the network (i.e., the gNB) within the configured window. If the UE receives a PDCCH addressed to C-RNTI, the random access procedure is considered successfully completed. If the UE receives a backoff message corresponding to its transmitted preamble, the random access procedure is considered successfully completed.

[0080] For certain events, such as handover and beam failure recovery, if one or more dedicated preambles and one or more PUSCH resources are assigned to the UE, the UE determines whether to send a dedicated preamble or a non-dedicated preamble during the first step of random access, i.e., during the random access resource selection for MsgA transmission. Typically, a dedicated preamble is provided for a subset of the SSB / CSI-RS. If none of the SSB / CSI-RS for which the gNB has provided contention-free random access resources (i.e., dedicated preamble / RO / PUSCH resources) has a DL RSRP above a threshold, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during the RA procedure, one random access attempt can be a 2-step CFRA, while other random access attempts can be a 2-step CBRA.

[0081] When initiating a random access procedure, the UE first selects a carrier (SUL or NUL). If the gNB explicitly signals a carrier for the random access procedure, the UE selects the signaled carrier to perform the random access procedure. If the gNB does not explicitly signal a carrier for the random access procedure; and if the serving cell for the random access procedure has a supplementary uplink configured, and if the downlink path loss reference RSRP is less than rsrp-ThresholdSSB-SUL: the UE selects the SUL carrier to perform the random access procedure. Otherwise, the UE selects the NUL carrier to perform the random access procedure. After selecting the UL carrier, the UE determines the UL and DL BWP for the random access procedure, as specified in Section 5.15 of TS 38.321. The UE then determines whether to perform a 2-step or 4-step RACH for this random access procedure.

[0082] - If this random access procedure is initiated by a PDCCH command, and if the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, then the UE selects a 4-step RACH.

[0083] Otherwise, if the gNB signals a 2-step contention-free random access resource for the random access procedure, the UE selects a 2-step RACH.

[0084] Otherwise, if the gNB signals a 4-step contention-free random access resource for the random access procedure, the UE selects a 4-step RACH.

[0085] Otherwise, if the UL BWP selected for the random access procedure has only 2-step RACH resources configured, the UE selects 2-step RACH.

[0086] Otherwise, if the UL BWP selected for the random access procedure has only 4-step RACH resources, the UE selects 4-step RACH.

[0087] Otherwise, if the UL BWP selected for this random access procedure is configured with 2-step and 4-step RACH resources,

[0088] - If the RSRP referenced for downlink path loss is lower than the configured threshold, the UE selects a 4-step RACH. Otherwise, the UE selects a 2-step RACH.

[0089] System Information Acquisition in Fifth Generation Wireless Communication Systems: In fifth-generation wireless communication systems, the cell broadcast synchronization signal and the Node B (gNB) or base station in the PBCH block (SSB) consist of primary and secondary synchronization signals (PSS, SSS) and system information. System information includes common parameters required for communication within the cell. In fifth-generation wireless communication systems (also known as next-generation radio or NR), system information (SI) is divided into MIB and multiple SIBs, among which:

[0090] - The MIB is always sent on the BCH at a period of 80ms and is repeated within 80ms, and it includes the parameters required to obtain SIB1 from the cell.

[0091] SIB1 is transmitted on the DL-SCH with a period of 160ms and variable transmission repetition. The default transmission repetition period for SIB1 is 20ms, but the actual transmission repetition period depends on the network implementation. The scheduling information in SIB1 includes the mapping between SIBs and SI messages, the periodicity of each SI message, and the SI window length. The scheduling information in SIB1 includes an indicator for each SI message, indicating whether the relevant SI message is being broadcast. If at least one SI message is not being broadcast, SIB1 may include random access resources (PRACH preamble and PRACH resources) to request the gNB to broadcast one or more SI messages.

[0092] SIBs other than SIB1 are carried in System Information (SI) messages, which are transmitted on the DL-SCH. Only SIBs with the same periodicity can be mapped to the same SI message. Each SI message is transmitted within a periodically occurring time-domain window (an SI window of the same length for all SI messages). Each SI message is associated with an SI window, and the SI windows of different SI messages do not overlap. That is, within an SI window, only the corresponding SI message is transmitted. Any SIB other than SIB1 can be configured as cell-specific or area-specific using the indication in SIB1. Cell-specific SIBs are only applicable to the cell providing the SIB, while area-specific SIBs are applicable to an area called an SI area, which consists of one or more cells and is identified by the systemInformationAreaID.

[0093] Paging in 5G wireless communication systems: In 5G (also known as NR or New Radio) wireless communication systems, the UE can be in one of the following RRC states: RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED. The RRC states can be further characterized as follows:

[0094] - In RRC_IDLE state, UE-specific DRX can be configured by the upper layer (i.e., NAS). The UE monitors short messages sent via DCI with P-RNTI; monitors paging channels for CN paging using 5G-S-TMSI; performs neighbor cell measurements and cell (re)selection; acquires system information and can send SI requests (if configured). - In RRC_INACTIVE state, UE-specific DRX can be configured by the upper layer or the RRC layer; in this state, the UE stores the UE inactive AS context. RAN-based notification area is configured by the RRC layer. The UE monitors short messages sent via DCI with P-RNTI; monitors paging channels for CN paging using 5G-S-TMSI and RAN paging using full I-RNTI; performs neighbor cell measurements and cell (re)selection; periodically performs RAN-based notification area updates, and when moving outside the configured RAN-based notification area; acquires system information and can send SI requests (if configured).

[0095] - Under RRC_CONNECTED, the UE stores the AS context. Unicast data is sent to / received from the UE. At lower layers, the UE can be configured with a UE-specific DRX. The UE monitors short messages sent via DCI along with P-RNTI (if configured); monitors control channels associated with shared data channels to determine whether to schedule data for them; provides channel quality and feedback information; performs neighbor cell measurements and measurement reports; and acquires system information.

[0096] Under RRC_CONNECTED, the network can initiate an RRC connection suspension by sending an RRCLease with a suspension configuration. When an RRC connection is suspended, the UE stores its inactive AS context and any configurations received from the network, and transitions to the RRC_INACTIVE state. If the UE has an SCG configured, the UE releases the SCG configuration when initiating the RRC connection recovery process. The RRC messages used to suspend the RRC connection are integrity protected and encrypted.

[0097] When a UE needs to transition from the RRC_INACTIVE state to the RRC_CONNECTED state, the restoration of the suspended RRC connection is initiated by the upper layer, or by the RRC layer to perform an RNA update, or by a RAN paging from the NG-RAN. When the RRC connection is restored, the network configures the UE according to the RRC connection restoration procedure based on the stored UE inactive AS context and any RRC configuration received from the network. The RRC connection restoration procedure reactivates AS security and rebuilds the SRB and DRB. In response to a request to restore the RRC connection, the network may restore the suspended RRC connection and send the UE to RRC_CONNECTED, or reject the restoration request and send the UE to RRC_INACTIVE (using a wait timer), or directly re-suspend the RRC connection and send the UE to RRC_INACTIVE, or directly release the RRC connection and send the UE to RRC_IDLE, or instruct the UE to initiate NAS-level restoration (in which case the network sends an RRC setup message).

[0098] After initiating the recovery process, the UE:

[0099] In addition to the parameters provided in SIB1, apply the default L1 parameter values ​​as specified in the corresponding physical layer specification; apply the default MAC cell group configuration; apply the CCCH configuration; start timer T319; apply the timeAlignmentTimerCommon included in SIB1; apply the default SRB1 configuration; set the pendingRNA-Update variable to error; initiate the transmission of the RRCResumeRequest message or RRCResumeRequest1; restore the RRC configuration, RoHC state, stored QoS flow to DRB mapping rules, and KgNB and KRRCint keys from the stored UE inactive AS context, except for the following: masterCellGroup, mrdc-SecondaryCellGroup (if stored), and pdcp-Config; set resumeMAC-I to the 16 least significant bits of MAC-I calculated using the following: K in the UE inactive AS context. RRCint The key and the previously configured integrity protection algorithm, along with all input bits of COUNT, BEARER, and DIRECTION set to binary one; using the stored nextHopChainingCount value, based on the current K... gNB Key or NH derived K gNB Key; Export K RRCenc Key, K RRCint Key, K UPint Key and K UPencKey; using the configured algorithm and K RRCint Key and K UPint The key is configured to apply integrity protection to all signaling radio bearers except SRB0; that is, integrity protection should be applied to all subsequent messages received and transmitted by the UE. The lower layer is also configured to apply encryption to all signaling radio bearers except SRB0, using the configured encryption algorithm derived in this sub-clause. RRCenc Key and K UPenc The key, i.e., the encryption configuration, should be applied to all subsequent messages received and sent by the UE; rebuild the PDCP entity for SRB1; restore SRB1; send RRCresumeRequest or RRCresumeRequest1.

[0100] In 5G wireless communication systems, Small Data Transmission (SDT) in RRC_INACTIVE is supported. With a 4-step RA procedure in SDT, uplink data can be transmitted in Msg3; with a 2-step RA procedure in SDT, it can be transmitted in MsgA; and with a CG-based SDT procedure, it can be transmitted in pre-configured CG resources.

[0101] NR-based 5G or next-generation radio access networks (NG-RAN) consist of NG-RAN nodes, where each NG-RAN node is a gNB, providing NR user plane and control plane protocol terminals to the UE. The gNB also connects to the 5GC via the NG interface, more specifically to the AMF (Access and Mobility Management Function) via the NG-C interface, and to the UPF (User Plane Function) via the NG-U interface. In fifth-generation (also known as NR or New Radio) wireless communication systems, the UE can use discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. In the RRC_IDLE / RRC_INACTIVE states, the UE briefly wakes up at regular intervals (i.e., each DRX cycle) to receive paging, SI update notifications, and emergency notifications. Paging messages are sent using the Physical Downlink Shared Channel (PDSCH). If a paging message is present in the PDSCH, the Physical Downlink Common Control Channel (PDCCH) is addressed to the P-RNTI. The P-RNTI is shared by all UEs. The UE identifier (i.e., the S-TMSI of an RRC_IDLE UE or the I-RNTI of an RRC_INACTIVE UE) is included in the paging message to indicate that paging is being performed for a specific UE. A paging message may include multiple UE identifiers to paging multiple UEs. The paging message is broadcast on the data channel (i.e., the PDSCH) (i.e., the PDCCH is masked with the P-RNTI). SI updates and emergency notifications are included in the DCI, and the PDCCH carrying the DCI is addressed to the P-RNTI. In RRC idle / inactive mode, the UE monitors one paging opportunity (PO) per DRX cycle. In RRC idle / inactive mode, the UE monitors the PO in the initial DL BWP. In RRC connected state, the UE monitors one or more POs to receive SI update notifications and emergency notifications. In RRC connected state, the UE may monitor any PO in the paging DRX cycle and at least one PO in the SI modification cycle. In RRC idle / inactive mode, the UE monitors the PO in each DRX cycle in its active DL BWP. PO is a set of "S" PDCCH monitoring opportunities used for paging, where "S" is the number of SSBs (i.e., synchronization signals and PBCH blocks, which consist of primary and secondary synchronization signals (PSS, SSS) and PBCH) transmitted in the cell. The UE first determines the paging frame (PF), and then determines the PO relative to the determined PF. One PF is a radio frame (10ms).

[0102] - The PF of the UE is a radio frame with system frame number "SFN", which satisfies the equation (SFN+PF_offset)mod T=(T div N)*(UE_ID mod N).

[0103] - Index (i_s), indicating the index of the PO is determined by i_s = floor(UE_ID / N) mod Ns.

[0104] -T is the UE's DRX period.

[0105] --In the RRC_INACTIVE state, T is determined by the shortest of the UE-specific DRX value configured by RRC, the UE-specific DRX value configured by NAS, and the default DRX value broadcast in the system information.

[0106] --In the RRC_IDLE state, T is determined by the shortest of the UE-specific DRX value configured by the NAS and the default DRX value broadcast in the system information. If the UE-specific DRX is not configured by the upper layer (i.e., the NAS), the default value is applied.

[0107] -N: Total number of paging frames in T

[0108] -Ns: Number of paging opportunities for PF

[0109] -PF_offset: The offset used to determine PF.

[0110] -UE_ID: 5G-S-TMSI mod 1024

[0111] - In SIB1, the parameters Ns, nAndPagingFrameOffset, and the length of the default DRX period are signaled. The values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset. If the UE does not have a 5G-S-TMSI, for example, when the UE has not yet registered with the network, the UE should use UE_ID=0 as the default identifier in the above PF and i_s equations.

[0112] - The timing of PDCCH monitoring for paging is determined based on the paging search space configuration signaled by the gNB.

[0113] - When SearchSpaceId is configured as 0 for pagingSearchSpace, the PDCCH monitoring timing for paging is the same as RMSI. When SearchSpaceId is configured as 0 for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO, which starts from the first PDCCH monitoring timing for paging in the PF. For Ns=2, the PO is in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0114] - When SearchSpaceId is configured to be non-zero for pagingSearchSpace, the UE monitors the (i_s+1)th PO. The PDCCH monitoring timing for paging is determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. The PDCCH monitoring timings for paging that do not overlap with the UL symbol (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially from 0, starting from the first PDCCH monitoring timing for paging in the PF. The gNB can signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. When firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PO is the set of "S" consecutive PDCCH monitoring timings for paging, starting from the PDCCH monitoring timing number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is a set of "S" consecutive PDCCH monitoring opportunities used for paging, starting from the (i_s*S)th PDCCH monitoring opportunity used for paging. "S" is the number of SSBs actually transmitted, determined by the parameter ssb-PositionsInBurst signaled in SystemInformationBlock1 received from the gNB. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 used for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0115] The PDCCH addressing to the P-RNTI carries information according to DCI format 1_0. The following information is transmitted using DCI format 1_0, where the CRC is scrambled by the P-RNTI:

[0116] -Short message indicator-2 digits, according to Table 1.

[0117] -Short Message- 8 bits, according to Table 2. This bit field is retained if it only carries scheduling information for paging.

[0118] -Frequency domain resource allocation– This bit is reserved if the message is only intended for short messages.

[0119] - It is the size of CORESET 0.

[0120] -Time-domain resource allocation-4 bits. This bit field is reserved if the message is only being sent to short messages.

[0121] -VRB-to-PRB mapping -1 bit, this bit field is retained if only short messages are carried.

[0122] -Modulation and encoding scheme-5 bits. This bit field is reserved if the message is only being transmitted via short message.

[0123] -TB scaling -2 bits: This bit field is retained if the message is only being sent to short messages.

[0124] -Reserved bits-6 bits

[0125] Table 1 allows you to define short message indicators.

[0126] Table 1

[0127] Bit field SMS indicator 00 reserve 01 Scheduling information used only for paging exists in the DCI. 10 Only short messages exist in DCI 11 Both the scheduling information and the short message used for paging exist in the DCI.

[0128] Table 2 defines a short message. Bit 1 is the most significant bit.

[0129] Table 2

[0130]

[0131] In RRC IDLE and RRC INACTIVE states, a UE can use the SSB for AGC, time / frequency tracking, RRM measurements of the serving cell, RRM measurements of neighboring cells, and paging reception. The SSB, consisting of PSS / SSS / PBCH, is broadcast periodically by the cell. Since the periodicity of the SSB can be longer, it is under discussion that the TRS / CSI-RS timing configured for connected UEs in a cell can be shared with idle / inactive UEs. Idle / inactive UEs can use the shared TRS / CSI-RS timing to perform functions such as AGC, time / frequency tracking, RRM measurements of the serving cell, RRM measurements of neighboring cells, and paging reception. The configuration of the TRS / CSI-RS timing for idle / inactive UEs (such as time and frequency resources, periodicity, etc.) is provided by RRC signaling in the system information.

[0132] TRS / CSI RS can be dynamically enabled / disabled within the cell. When TRS / CSI RS is disabled, the gNB can remove the TRS / CSI RS timing configuration from the SIB and send an SI update notification to the UE. When TRS is enabled, the gNB can add the TRS / CSI RS timing configuration to the SIB and send an SI update notification to the UE. This method is straightforward and reuses the existing SI framework. However, this method requires the UE to acquire SIB1 each time TRS is enabled / disabled. This could also affect other UEs that are not interested in TRS / CSI RS, as they will all acquire SIB1 upon receiving an SI update notification and determine which SIB has been updated. Therefore, an enhanced method is needed to indicate the availability / unavailability of TRS / CSI RS for RRC IDLE and RRC INACTIVE UEs.

[0133] In fifth-generation wireless communication systems, SI change indications and PWS notifications utilize a modification cycle. Updated SI messages (excluding SI messages used for ETWS, CMAS, and location-aided data) are broadcast in a modification cycle following the transmission of the SI change indication. The boundaries of the modification cycle are defined by the SFN value, where SFN mod m = 0, and m is the number of radio frames including the modification cycle. The modification cycle is configured by system information. The UE uses short messages transmitted via P-RNTI on the DCI to receive indications of SI modifications and / or PWS notifications. Repetition of SI change indications may occur within preceding modification cycles.

[0134] UEs in RRC_IDLE or RRC_INACTIVE should monitor SI change indications during their own paging time in each DRX cycle. UEs in RRC_CONNECTED should monitor SI change indications during any paging time, at least once per modification cycle if the UE is provided with a common search space on the active BWP, including pagingSearchSpace, searchSpaceSIB1, and searchSpaceOtherSystemInformation, to monitor paging.

[0135] UEs with ETWS or CMAS capabilities in RRC_IDLE or RRC_INACTIVE should monitor for indications regarding PWS notifications during their own paging time in each DRX cycle. If a UE with ETWS or CMAS capabilities in RRC_CONNECTED is provided with a common search space on the active BWP, including pagingSearchSpace, searchSpaceSIB1, and searchSpaceOtherSystemInformation, to monitor paging, then that UE should monitor for indications regarding PWS notifications at least once per default Paging Cycle during any paging time.

[0136] Sidelink Communication: 4G and 5G wireless communication systems support vehicle communication services. Vehicle communication services, represented by V2X services, can include four different types: V2V, V2I, V2N, and V2P. In fifth-generation (also known as NR or New Radio) wireless communication systems, V2X communication is being enhanced to support enhanced V2X use cases, which are broadly arranged into four groups:

[0137] 1) Vehicle platooning enables vehicles to dynamically form a convoy and travel together. All vehicles in the convoy receive information from the lead vehicle to manage the convoy. This information allows vehicles to drive closer together in a coordinated manner than normal, heading in the same direction and traveling together.

[0138] 2) Extended sensor coverage enables the exchange of raw or processed data collected via local sensors or real-time video imagery between vehicles, roadside station units, pedestrian devices, and V2X application servers. Vehicles can gain increased environmental awareness beyond the range of their own sensors and have a broader and more comprehensive view of the local situation. High data rates are a key feature.

[0139] 3) Advanced driving enables semi-autonomous or fully autonomous driving. Each vehicle and / or RSU shares its perception data obtained from local sensors with nearby vehicles, which allows vehicles to synchronize and coordinate their trajectories or actions. Each vehicle also shares its driving intentions with nearby vehicles.

[0140] 4) Remote driving enables remote drivers or V2X applications to operate remote vehicles for passengers who cannot drive themselves or for vehicles in hazardous environments. For situations with limited variation and predictable routes, such as public transportation, cloud-based driving can be used. High reliability and low latency are key requirements.

[0141] Figure 1 A diagram illustrating sidelink communication according to an embodiment of the present disclosure is shown.

[0142] V2X services can be provided via PC5 interfaces 110, 112, and 114 and / or Uu interfaces 120 and 132. Support for V2X services via PC5 interfaces 110, 112, and 114 is provided by NR sidechain communication or V2X sidechain communication. This is a communication mode where UEs 130, 132, and 134 can communicate directly with each other on PC5 interfaces 110, 112, and 114 using NR technology or EUTRA technology respectively, without traversing any network nodes. This communication mode is supported when the UE is served by the RAN and when the UE is outside the RAN coverage area. Only UEs authorized for V2X services can perform NR or V2X sidechain communication. Figure 1 As shown, the NG-RAN architecture supports PC5 interfaces 110, 112, and 114. When the UE is within NG-RAN coverage, regardless of its RRC state, and when the UE is outside NG-RAN coverage, sidelink transmission and reception via PC5 interfaces 110, 112, and 114 are supported. Support for V2X services via the PC5 interfaces can be provided by NR sidelink communication and / or V2X sidelink communication. NR sidelink communication can be used to support services other than V2X services.

[0143] NR or V2X sidelink communication can support three types of transmission modes. (1) Unicast transmission, characterized by: supporting at least one PC5-RRC connection between peer UEs; transmitting and receiving control information and user traffic between peer UEs in the sidelink; supporting sidelink HARQ feedback; supporting RLC AM; and supporting sidelink RLM so that two peer UEs can detect RLF. (2) Multicast transmission, characterized by: transmitting and receiving user traffic between UEs belonging to the same group in the sidelink; supporting sidelink HARQ feedback. (3) Broadcast transmission, characterized by: transmitting and receiving user traffic between UEs in the sidelink.

[0144] The AS protocol stack in the control plane of the PC5 interface includes RRC, PDCP, RLC, and MAC sublayers, as well as the physical layer. The AS protocol stack in the user plane of the PC5 interface includes SDAP, PDCP, RLC, and MAC sublayers, as well as the physical layer. Sidelink radio bearers (SLRBs) are divided into two groups: sidelink data radio bearers (SLDRBs) for user plane data and sidelink signaling radio bearers (SLSRBs) for control plane data. Independent SLSRBs using different SCCHs are configured separately for PC5-RRC and PC5-S signaling.

[0145] The MAC sublayer provides the following services and functions through the PC5 interface: - Radio resource selection; packet filtering; priority handling between uplink and sidelink transmissions for a given UE; sidelink CSI reporting. Through LCP restrictions in the MAC, only sidelink logical channels belonging to the same destination can be multiplexed into each MAC PDU associated with that destination for each unicast, multicast, and broadcast transmission. NG-RAN can also control whether sidelink logical channels can utilize resources allocated to configured sidelink grant type 1. For packet filtering, an SL-SCH MAC header including portions of both the source-2 ID and destination-2 ID is added to each MAC PDU. The LCID contained within the MAC subheader uniquely identifies logical channels within the combined range of the source-2 ID and destination-2 ID. The following logical channels are used for sidelinks:

[0146] - Sidelink Control Channel (SCCH): A sidelink channel used to send control information from one UE to other UEs;

[0147] - Sidelink Traffic Channel (STCH): A sidelink channel used to send user information from one UE to other UEs;

[0148] - Sidelink Broadcast Control Channel (SBCCH): A sidelink channel used to broadcast sidelink system information from one UE to other UEs.

[0149] The logical channel and the transport channel have the following relationship:

[0150] -SCCH can be mapped to SL-SCH;

[0151] -STCH can be mapped to SL-SCH;

[0152] -SBCCH can be mapped to SL-BCH.

[0153] The RRC sublayer provides the following services and functions through the PC5 interface:

[0154] - Transmit PC5-RRC messages between peer UEs;

[0155] - Maintenance and release of PC5-RRC connection between two UEs;

[0156] - Detect sidelink radio link faults in the PC5-RRC connection.

[0157] A PC5-RRC connection is a logical connection between two UEs for a pair of source and destination stratum-2 IDs, which is considered to be established after the corresponding PC5 unicast link as specified in TS 23.287 is established. There is a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. A UE can have multiple PC5-RRC connections with one or more UEs for different pairs of source and destination stratum-2 IDs. Separate PC5-RRC procedures and messages are used by the UE to transmit UE capabilities and sidelink configurations (including SLRB configurations) to its peer UE. Two peer UEs can exchange their own UE capabilities and sidelink configurations in both sidelink directions using separate bidirectional procedures. A UE will release the PC5-RRC connection if it is no longer interested in sidelink transmissions, if a sidelink RLF is declared on the PC5-RRC connection, or if the stratum-2 link release procedure as specified in TS 23.287 is completed.

[0158] The sidelink or PC5 interface supports UE-to-UE direct communication using sidelink resource allocation modes and physical layer signals / channels. Two sidelink resource allocation modes are supported: Mode 1 and Mode 2. In Mode 1, sidelink resource allocation is provided by the network. In Mode 2, the UE determines the SL transmission resources in the resource pool.

[0159] The Physical Sidelink Control Channel (PSCCH) indicates the resources and other transmission parameters that the UE uses for the PSCCH. PSCCH transmission is associated with DM-RS. Sidelink Control Information (Phase 1 SCI) is transmitted on the PSCCH.

[0160] The Physical Side Link Shared Channel (PSSCH) transmits the data itself in transport blocks (TBs), as well as control information triggered by HARQ procedures and CSI feedback. This control information is referred to as the second-stage SCI. At least six OFDM symbols are used for PSSCH transmission within a time slot. PSSCH transmission is associated with DM-RS and can also be associated with PT-RS.

[0161] The Physical Sidelink Feedback Channel (PSFCH) provides HARQ feedback from the UE, the intended receiver of the PSFCH transmission, to the UE performing the transmission via a sidelink bearer. The PSFCH sequence is repeated on two OFDM symbols within a single PRB and transmitted near the end of the sidelink resource in the time slot.

[0162] The sidelink synchronization signal consists of the sidelink primary synchronization signal and the sidelink secondary synchronization signal (S-PSS, S-SSS), each occupying 2 symbols and 127 subcarriers. The physical sidelink broadcast channel (PSBCH) occupies 9 symbols in normal and 5 symbols in extended cyclic prefix mode, including the associated DM-RS.

[0163] Sidelink HARQ feedback uses the PSFCH and can operate in one of two options. In one option, which can be configured for unicast and multicast, the PSFCH uses resources dedicated to a single PSFCH-transmitting UE to send ACK or NACK. In the other option, which can be configured for multicast, the PSFCH sends NACK on resources that can be shared by multiple PSFCH-transmitting UEs, or does not send PSFCH signals.

[0164] For data transmission via the PC5 interface, the transmitting UE first transmits the Phase 1 SCI on the PSCCH resource. The Phase 1 SCI includes information about the transport block, such as priority, frequency resource allocation, time resource allocation, resource reservation period, DMRS mode, Phase 2 SCI format, MCS, and the number of DMRS ports. Then, the transmitting UE transmits the Phase 2 SCI via the PSCCH. The Phase 2 SCI includes information such as HARQ process number, NDI, RV, source ID, destination ID, HARQ feedback enable / disable indicator, broadcast type, CSI request, area ID, and range. Finally, the transmitting UE transmits the TB carrying the SLMAC PDU via the PSCCH.

[0165] <Non-Availability of TRS / CSI RS for RRC IDLE and RRC INACTIVE UEs>

[0166] Example 1-1: Single notification of TRS and / or CSI RS in SMS messages

[0167] Figure 2 A flowchart is shown of a method performed by a UE to identify a single notification of TRS and CSI RS in a short message according to an embodiment of the present disclosure.

[0168] In an exemplary embodiment, a new notification (trsNotification) may be included in a short message, which is included in a PDCCH addressed to P-RNTI.

[0169] In an exemplary embodiment, the PDCCH addressed to the P-RNTI can carry information according to DCI format 1_0. For example, the following information can be transmitted using DCI format 1_0, wherein the CRC is scrambled by the P-RNTI:

[0170] -Short message indicator-2 digits, according to Table 1.

[0171] -Short Message- 8 bits, according to Table 2. This bit field is retained if it only carries scheduling information for paging.

[0172] -Frequency domain resource allocation– This bit is reserved if the message is only intended for short messages.

[0173] - It is the size of CORESET 0.

[0174] -Time-domain resource allocation-4 bits (e.g., 4 bits as defined in sub-clause 5.1.2.1 of [6,TS38.214]). This bit field is reserved if only short messages are carried.

[0175] -VRB-to-PRB mapping-1 bit (e.g., 1 bit according to Table 7.3.1.1.2-33 of TS 38.212). This bit field is reserved if only short messages are carried.

[0176] -Modulation and encoding scheme-5 bits. (For example, as defined in sub-clause 5.1.3 of [6, TS38.214], 5 bits, using Table 5.1.3.1-1 of TS 38.214). This bit field is reserved if only short messages are carried.

[0177] -TB scaling -2 bits. (For example, as defined in sub-clause 5.1.3.2 of [6,TS38.214], 2 bits), this bit field is reserved if only short messages are carried.

[0178] -Reserved bits-6 bits

[0179] Table 3 can define short messages that include trsNotification. Bit 1 can be the most significant bit. In alternative embodiments, any other bits from 4 to 8, replacing bit 3, can be used for trsNotification.

[0180] Table 3

[0181]

[0182]

[0183] In step S210, the UE can identify whether the UE is in RRC IDLE state or RRC INACTIVE state.

[0184] In step S220, the UE can obtain SIB X. SIB X can be an SIB, which is used by the gNB to configure the TRS / CSI RS timing for the RRC IDLE UE and the RRC INACTIVE UE.

[0185] In step S230, the UE can identify whether SIB X includes a configuration for TRS / CSI RS timing. In step S240, if SIBX includes a configuration for TRS / CSI RS timing:

[0186] - The UE can address the PDCCH of P-RNTI for trsNotification monitoring in the UE's PO.

[0187] In step S250, if the UE receives a PDCCH addressed to P-RNTI, and the DCI of the received PDCCH includes a short message indicator set to "10" or "11":

[0188] -UE can check short messages in DCI.

[0189] In step S260, the UE can receive TRS / CSI RS based on the short message in the DCI. If the trsNotification bit is set to 1, the gNB sends TRS / CSI RS at the TRS / CSI RS timing according to the following rules:

[0190] --In one embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the SI modification period "N". In one embodiment, the TRS / CSI RS is sent by the GNB at the TRS / CSI RS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0191] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", then the GNB sends a TRS / CSI RS during the TRS / CSI RS timing in the SI modification period "N+1".

[0192] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", then the GNB sends a TRS / CSI RS during the TRS / CSI RS timings in the SI modification periods "N" and "N+1".

[0193] --In another embodiment, if a trsNotification set to 1 is received, the GNB sends a TRS / CSI RS at the TRS / CSI RS timing that occurs after the notification, until a trsNotification set to 0 is received or until the TRS / CSI RS configuration is removed from SIB X (whichever occurs first).

[0194] --In another embodiment, if a trsNotification set to 1 is received in the activation period "N", the GNB transmits a TRS / CSI RS during the TRS / CSI RS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period can begin from SFN X, where X mod activation period = 0; or the activation period can begin from SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the TRS / CSI RS is transmitted by the GNB during the TRS / CSI RS timing in "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0195] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB transmits a TRS / CSI RS during the TRS / CSI RS timing in the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0196] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB transmits TRS / CSI RS during the TRS / CSI RS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0197] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB transmits a TRS / CSI RS at the TRS / CSI RS timing in the (default) DRX cycle "N". In one embodiment, the TRS / CSI RS is transmitted by the GNB at the TRS / CSI RS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0198] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS / CSI RS during the TRS / CSI RS timing in the (default) DRX cycle "N+1".

[0199] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX period "N", the GNB sends TRS / CSIRS during the TRS / CSIRS timings in the (default) DRX periods "N" and "N+1".

[0200] Examples 1-2: Separate notifications of TRS and CSI RS in short messages

[0201] Figure 3 A flowchart is shown of a method performed by a UE to identify separate notifications of TRS and CSI RS in a short message, according to an embodiment of the present disclosure.

[0202] In an exemplary embodiment, new notifications (trsNotification and CsirsNotification) may be included in short messages, wherein the short messages are included in the PDCCH addressed to P-RNTI.

[0203] In an exemplary embodiment, the PDCCH addressed to the P-RNTI can carry information according to DCI format 1_0. For example, the following information can be transmitted using DCI format 1_0, wherein the CRC is scrambled by the P-RNTI:

[0204] -Short message indicator-2 digits, according to Table 1.

[0205] -Short Message- 8 bits, according to Table 2. This bit field is retained if it only carries scheduling information for paging.

[0206] -Frequency domain resource allocation– This bit is reserved if the message is only intended for short messages.

[0207] - It is the size of CORESET 0.

[0208] -Time-domain resource allocation-4 bits (e.g., 4 bits as defined in sub-clause 5.1.2.1 of [6,TS38.214]). This bit field is reserved if only short messages are carried.

[0209] -VRB-to-PRB mapping-1 bit (e.g., 1 bit according to Table 7.3.1.1.2-33 of TS 38.212). This bit field is reserved if only short messages are carried.

[0210] - Modulation and encoding scheme - 5 bits. (For example, as defined in sub-clause 5.1.3 of [6, TS38.214], 5 bits, using Table 5.1.3.1-1 of TS38.214). This bit field is reserved if only short messages are carried.

[0211] -TB scaling -2 bits. (For example, as defined in sub-clause 5.1.3.2 of [6,TS38.214], 2 bits). This bit field is reserved if only short messages are carried.

[0212] -Reserved bits-6 bits

[0213] Table 4 can define short messages that include trsNotification. Bit 1 can be the most significant bit. In alternative embodiments, any other bits from 4 to 8, replacing bits 3 and 4, can be used for trsNotification and CsirsNotification.

[0214] Table 4

[0215]

[0216] In step S310, the UE can identify whether the UE is in RRC IDLE state or RRC INACTIVE state.

[0217] In step S320, the UE can obtain SIB X. SIB X can be an SIB, which is used by the GNB to configure the TRS / CSI RS timing for the RRC IDLE UE and the RRC INACTIVE UE.

[0218] In step S330, the UE can identify whether SIB X includes at least one of the configuration of TRS timing or the configuration of CSI RS timing.

[0219] In step S340-A, if SIB X includes a configuration for TRS timing:

[0220] - The UE addresses the PDCCH of P-RNTI for trsNotification monitoring in the UE's PO.

[0221] In step S340-B, if SIB X includes the configuration of CSI RS timing:

[0222] - The UE addresses the PDCCH of P-RNTI for CsirsNotification monitoring in the UE's PO.

[0223] In step S350, if the UE receives a PDCCH addressed to P-RNTI, and the DCI of the received PDCCH includes a short message indicator set to "10" or "11":

[0224] -UE can check short messages in DCI.

[0225] In step S360, the UE may receive at least one of TRS or CSI RS based on a short message in the DCI.

[0226] If the trsNotification bit is set to 1, the GNB transmits the TRS at the TRS timing according to the following rules:

[0227] --In one embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification period "N". In one embodiment, the TRS is sent by the GNB during the TRS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0228] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", then the GNB sends a TRS at the TRS timing in the SI modification period "N+1".

[0229] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification periods "N" and "N+1".

[0230] --In another embodiment, if a trsNotification set to 1 is received, the GNB sends a TRS at the TRS timing that occurs after that notification, until a trsNotification set to 0 is received or until the TRS configuration is removed from the SIBX (whichever occurs first).

[0231] --In another embodiment, if a trsNotification set to 1 is received in the activation period "N", the GNB transmits a TRS during the TRS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the TRS is transmitted by the GNB during the TRS timing of "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0232] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB sends a TRS at the TRS timing during the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0233] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB sends a TRS during the TRS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0234] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS during the TRS timing in the (default) DRX cycle "N". In one embodiment, the TRS is sent by the GNB during the TRS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0235] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS at the TRS timing in the (default) DRX cycle "N+1".

[0236] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS during the TRS timings in the (default) DRX cycles "N" and "N+1".

[0237] If the CsirsNotification bit is set to 1, the GNB sends CSI RS at the CSI RS timing according to the following rules:

[0238] --In one embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification period "N". In one embodiment, the TRS is sent by the GNB during the TRS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0239] --In another embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", then the GNB sends a CSI RS at the CSI RS timing in the SI modification period "N+1".

[0240] --In another embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", the GNB sends a CSI RS during the CSI RS timings in the SI modification periods "N" and "N+1".

[0241] --In another embodiment, if a CsirsNotification set to 1 is received, the GNB sends a CSI RS at the CSI RS timing that occurs after the notification, until a CsirsNotification set to 0 is received or until the CSI RS configuration is removed from SIB X (whichever occurs first).

[0242] --In another embodiment, if a CsirsNotification set to 1 is received in the activation period "N", the GNB transmits a CSI RS during the CSI RS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the CSI RS is transmitted by the GNB during the CSI RS timing of "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0243] --In another embodiment, if a CsirsNotification set to 1 is received in the activation period "N", the GNB transmits a CSI RS at the CSI RS timing in the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0244] --In another embodiment, if a CsirsNotification set to 1 is received during the activation period "N", the GNB transmits CSI RS during the CSI RS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0245] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS at the CSI RS timing in the (default) DRX cycle "N". In one embodiment, the CSI RS is sent by the GNB at the CSI RS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0246] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS at the CSI RS timing in the (default) DRX cycle "N+1".

[0247] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS during the CSI RS timings in the (default) DRX cycles "N" and "N+1".

[0248] Examples 1-3: Single notification of TRS and / or CSI RS in the DCI of the PDCCH addressed to P-RNTI sent in PO

[0249] Figure 4 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify a single notification of TRS and CSI RS in a DCI of a PDCCH addressed to P-RNTI sent during paging timing.

[0250] In an exemplary embodiment, the new notification (trsNotification) may be included in the DCI in the PDCCH addressed to the P-RNTI.

[0251] In an exemplary embodiment, the PDCCH addressed to the P-RNTI can carry information according to DCI format 1_0. For example, the following information can be transmitted using DCI format 1_0, wherein the CRC is scrambled by the P-RNTI:

[0252] -Short message indicator-2 digits, according to Table 1.

[0253] -Short Message- 8 bits, according to Table 2. This bit field is retained if it only carries scheduling information for paging.

[0254] -Frequency domain resource allocation– This bit is reserved if the message is only intended for short messages.

[0255] - It is the size of CORESET 0.

[0256] -Time-domain resource allocation-4 bits (e.g., 4 bits as defined in sub-clause 5.1.2.1 of [6,TS38.214]). This bit field is reserved if only short messages are carried.

[0257] -VRB-to-PRB mapping-1 bit (e.g., 1 bit according to Table 7.3.1.1.2-33 of TS 38.212). This bit field is reserved if only short messages are carried.

[0258] - Modulation and encoding scheme - 5 bits. (For example, as defined in sub-clause 5.1.3 of [6, TS38.214], 5 bits, using Table 5.1.3.1-1 of TS38.214). This bit field is reserved if only short messages are carried.

[0259] -TB scaling -2 bits. (For example, as defined in sub-clause 5.1.3.2 of [6,TS38.214], 2 bits), this bit field is reserved if only short messages are carried.

[0260] -trsNotification

[0261] - Reserved bits - 5 bits

[0262] In step S410, the UE can identify whether the UE is in RRC IDLE state or RRC INACTIVE state.

[0263] In step S420, the UE can obtain SIB X. SIB X can be an SIB, which is used by the GNB to configure the TRS / CSI RS timing for the RRC IDLE UE and the RRC INACTIVE UE.

[0264] In step S430, the UE can identify whether SIB X includes the configuration of TRS / CSI RS timing.

[0265] In step S440, if SIB X includes the configuration of TRS / CSI RS timing:

[0266] - The UE addresses the PDCCH of P-RNTI for trsNotification monitoring in the UE's PO.

[0267] In step S450, the UE can receive TRS / CSI RS based on trsNotification included in the DCI of the PDCCH addressed to the P-RNTI. If the UE receives a PDCCH addressed to the P-RNTI, and the DCI of the received PDCCH includes trsNotification:

[0268] - If the trsNotification bit is set to 1, the GNB sends TRS / CSI RS during the TRS / CSI RS timing according to the following rules:

[0269] --In one embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the SI modification period "N". In one embodiment, the TRS / CSI RS is sent by the GNB at the TRS / CSI RS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0270] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the SI modification period "N+1".

[0271] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends TRS / CSIRS during the TRS / CSIRS timings in the SI modification periods "N" and "N+1".

[0272] --In another embodiment, if a trsNotification set to 1 is received, the GNB sends a TRS / CSI RS at the TRS / CSI RS timing that occurs after the notification, until a trsNotification set to 0 is received or until the TRS / CSI RS configuration is removed from SIB X (whichever occurs first).

[0273] --In another embodiment, if a trsNotification set to 1 is received in the activation period "N", the GNB transmits a TRS / CSI RS during the TRS / CSI RS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the TRS / CSI RS is transmitted by the GNB during the TRS / CSI RS timing in "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0274] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB transmits a TRS / CSI RS during the TRS / CSI RS timing in the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0275] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB transmits TRS / CSI RS during the TRS / CSI RS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0276] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB transmits a TRS / CSI RS at the TRS / CSI RS timing in the (default) DRX cycle "N". In one embodiment, the TRS / CSI RS is transmitted by the GNB at the TRS / CSI RS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0277] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the (default) DRX cycle "N+1".

[0278] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends TRS / CSIRS during the TRS / CSIRS timings in the (default) DRX cycles "N" and "N+1".

[0279] Examples 1-4: Separate notifications of TRS and CSI RS in the DCI of the PDCCH addressed to P-RNTI sent in PO

[0280] Figure 5 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify separate notifications of TRS and CSI RS in a DCI of a PDCCH addressed to P-RNTI sent during paging timing.

[0281] In an exemplary embodiment, new notifications (trsNotification and CsirsNotification) may be included in the DCI in the PDCCH addressed to P-RNTI.

[0282] In an exemplary embodiment, the PDCCH addressed to the P-RNTI can carry information according to DCI format 1_0. For example, the following information can be transmitted using DCI format 1_0, wherein the CRC is scrambled by the P-RNTI:

[0283] -Short message indicator-2 digits, according to Table 1.

[0284] -Short Message- 8 bits, according to Table 2. This bit field is retained if it only carries scheduling information for paging.

[0285] -Frequency domain resource allocation– This bit is reserved if the message is only intended for short messages.

[0286] - It is the size of CORESET 0.

[0287] -Time-domain resource allocation-4 bits (e.g., 4 bits as defined in sub-clause 5.1.2.1 of [6,TS38.214]). This bit field is reserved if only short messages are carried.

[0288] -VRB-to-PRB mapping-1 bit (e.g., 1 bit according to Table 7.3.1.1.2-33 of TS 38.212). This bit field is reserved if only short messages are carried.

[0289] - Modulation and encoding scheme - 5 bits. (For example, as defined in sub-clause 5.1.3 of [6, TS38.214], 5 bits, using Table 5.1.3.1-1 of TS38.214). This bit field is reserved if only short messages are carried.

[0290] -TB scaling -2 bits. (For example, as defined in sub-clause 5.1.3.2 of [6,TS38.214], 2 bits), this bit field is reserved if only short messages are carried.

[0291] -trsNotification

[0292] -CsirsNotification

[0293] - Reserved bits - 4 bits

[0294] In step S510, the UE can identify whether the UE is in RRC IDLE state or RRC INACTIVE state.

[0295] In step S520, the UE can obtain SIB X. SIB X can be an SIB, which is used by the GNB to configure the TRS / CSI RS timing for the RRC IDLE UE and the RRC INACTIVE UE.

[0296] In step S530, the UE can identify whether SIB X includes at least one of the configuration of TRS timing or the configuration of CSI RS timing.

[0297] In step S540-A, if SIB X includes a configuration for TRS timing:

[0298] - In step S540-B, if the SIBX includes the configuration of CSI RS timing, the UE addresses the PDCCH of the P-RNTI for trsNotification monitoring in the UE's PO.

[0299] - The UE addresses the PDCCH of P-RNTI for CsirsNotification monitoring in the UE's PO.

[0300] In step S550, the UE may receive at least one of TRS or CSI RS based on at least one of trsNotification or CsirsNotification included in the DCI of the PDCCH addressed to the P-RNTI. If the UE receives a PDCCH addressed to the P-RNTI, and the DCI of the received PDCCH includes at least one of trsNotification or CsirsNotification:

[0301] If the trsNotification bit is set to 1, the GNB transmits the TRS at the TRS timing according to the following rules:

[0302] --In one embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification period "N". In one embodiment, the TRS is sent by the GNB during the TRS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0303] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", then the GNB sends a TRS at the TRS timing in the SI modification period "N+1".

[0304] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification periods "N" and "N+1".

[0305] --In another embodiment, if a trsNotification set to 1 is received, the GNB sends a TRS at the TRS timing that occurs after that notification, until a trsNotification set to 0 is received or until the TRS configuration is removed from the SIBX (whichever occurs first).

[0306] --In another embodiment, if a trsNotification set to 1 is received in the activation period "N", the GNB transmits a TRS during the TRS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the TRS is transmitted by the GNB during the TRS timing of "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0307] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB sends a TRS at the TRS timing during the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0308] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB sends a TRS during the TRS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0309] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS during the TRS timing in the (default) DRX cycle "N". In one embodiment, the TRS is sent by the GNB during the TRS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0310] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS at the TRS timing in the (default) DRX cycle "N+1".

[0311] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS during the TRS timings in the (default) DRX cycles "N" and "N+1".

[0312] If the CsirsNotification bit is set to 1, the GNB sends CSI RS at the CSI RS timing according to the following rules:

[0313] --In one embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification period "N". In one embodiment, the TRS is sent by the GNB during the TRS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0314] --In another embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", then the GNB sends a CSI RS at the CSI RS timing in the SI modification period "N+1".

[0315] --In another embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", the GNB sends a CSI RS during the CSI RS timings in the SI modification periods "N" and "N+1".

[0316] --In another embodiment, if a CsirsNotification set to 1 is received, the GNB sends a TRS at the CSI RS timing that occurs after the notification, until a CsirsNotification set to 0 is received or until the CSIRS configuration is removed from SIB X (whichever occurs first).

[0317] --In another embodiment, if a CsirsNotification set to 1 is received in the activation period "N", the GNB transmits a CSI RS during the CSI RS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the CSI RS is transmitted by the GNB during the CSI RS timing of "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0318] --In another embodiment, if a CsirsNotification set to 1 is received in the activation period "N", the GNB transmits a CSI RS at the CSI RS timing in the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0319] --In another embodiment, if a CsirsNotification set to 1 is received during the activation period "N", the GNB transmits CSI RS during the CSI RS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0320] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS at the CSI RS timing in the (default) DRX cycle "N". In one embodiment, the CSI RS is sent by the GNB at the CSI RS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0321] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS at the CSI RS timing in the (default) DRX cycle "N+1".

[0322] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS during the CSI RS timings in the (default) DRX cycles "N" and "N+1".

[0323] Examples 1-5: Single notification of TRS and / or CSI RS in the DCI of the PDCCH addressed to the RNTI, sent during the wake-up signal or early paging indication timing.

[0324] Figure 6 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify a single notification of TRS and CSI RS in the DCI of the PDCCH addressed to RNTI sent at the wake-up signal or early paging indication timing.

[0325] In an exemplary embodiment, the new notification (trsNotification) may include a DCI in the PDCCH addressed to the RNTI, sent during a wake-up signal or early paging indication timing. The wake-up signal or early paging indication is sent before the PO. The early paging indication is sent during the PDCCH monitoring timing for the early paging indication, prior to the PO. The RNTI used for the early paging indication may be a P-RNTI or any other predefined RNTI.

[0326] In step S610, the UE can identify whether it is in RRC IDLE state or RRC INACTIVE state.

[0327] In step S620, the UE can obtain SIB X. SIB X can be an SIB, which is used by the GNB to configure the TRS / CSI RS timing for the RRC IDLE UE and the RRC INACTIVE UE.

[0328] In step S630, the UE can identify whether SIB X includes the configuration of TRS / CSI RS timing.

[0329] In step S640, if SIBX includes the configuration of TRS / CSI RS timing:

[0330] - The UE can monitor the addressing of the PDCCH to the RNTI for the wake-up signal or early paging indication timing.

[0331] In one embodiment, the UE can also address the PDCCH of the P-RNTI for trsNotification monitoring in the PO as in embodiments 1-3 (e.g., in the case where trsNotification is not received during the wake-up signal or early paging indication timing).

[0332] In step S650, the UE can receive TRS and CSI RS based on the trsNotification included in the DCI of the PDCCH addressed to the RNTI sent by the gNB during the wake-up signal or early paging indication. If the UE receives the PDCCH addressed to the RNTI during the wake-up signal or early paging indication, and the DCI of the received PDCCH includes trsNotification:

[0333] - If the trsNotification bit is set to 1, the GNB sends TRS / CSI RS during the TRS / CSI RS timing according to the following rules:

[0334] --In one embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the SI modification period "N". In one embodiment, the TRS / CSI RS is sent by the GNB at the TRS / CSI RS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0335] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the SI modification period "N+1".

[0336] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends TRS / CSIRS during the TRS / CSIRS timings in the SI modification periods "N" and "N+1".

[0337] --In another embodiment, if a trsNotification set to 1 is received, the GNB sends a TRS / CSI RS at the TRS / CSI RS timing that occurs after the notification, until a trsNotification set to 0 is received or until the TRS / CSI RS configuration is removed from SIB X (whichever occurs first).

[0338] --In another embodiment, if a trsNotification set to 1 is received in the activation period "N", the GNB transmits a TRS / CSI RS during the TRS / CSI RS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the TRS / CSI RS is transmitted by the GNB during the TRS / CSI RS timing in "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0339] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB transmits a TRS / CSI RS during the TRS / CSI RS timing in the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0340] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB transmits TRS / CSI RS during the TRS / CSI RS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0341] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB transmits a TRS / CSI RS at the TRS / CSI RS timing in the (default) DRX cycle "N". In one embodiment, the TRS / CSI RS is transmitted by the GNB at the TRS / CSI RS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0342] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS / CSI RS at the TRS / CSI RS timing in the (default) DRX cycle "N+1".

[0343] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends TRS / CSIRS during the TRS / CSIRS timings in the (default) DRX cycles "N" and "N+1".

[0344] Examples 1-6: Separate notifications of TRS and CSI RS in the DCI of the PDCCH addressed to RNTI sent during wake-up signal or early paging indication.

[0345] Figure 7 A flowchart of a method performed by a UE according to an embodiment of the present disclosure is shown, the method being used to identify separate notifications of TRS and CSI RS in the DCI of the PDCCH addressed to RNTI sent at the wake-up signal or early paging indication timing.

[0346] In an exemplary embodiment, new notifications (trsNotification and CsirsNotification) may include a DCI addressing the PDCCH to the RNTI sent during a wake-up signal or early paging indication timing. The early paging indication is sent during a PDCCH monitoring timing prior to the PO for early paging indication. The RNTI used for early paging indication may be a P-RNTI or any other predefined RNTI.

[0347] In step S710, the UE can identify whether the UE is in RRC IDLE state or RRC INACTIVE state.

[0348] In step S720, the UE can obtain SIB X. SIB X can be an SIB, which is used by the GNB to configure the TRS / CSI RS timing for the RRC IDLE UE and the RRC INACTIVE UE.

[0349] In step S730, the UE can identify whether SIB X includes at least one of the configuration of TRS timing or the configuration of CSI RS timing.

[0350] In step S740-A, if SIB X includes a configuration for TRS timing:

[0351] - The UE can monitor the addressing of the PDCCH to the RNTI for the wake-up signal or early paging indication timing.

[0352] In one embodiment, the UE can also address the PDCCH of the P-RNTI in the PO for trsNotification monitoring, as in embodiments 1-4 (e.g., in the case where trsNotification is not received during the wake-up signal or early paging indication timing).

[0353] In step S740-B, if SIBX includes the configuration of CSI RS timing:

[0354] - The UE monitors the PDCCH of RNTI for CsirsNotification during the wake-up signal or early paging indication timing.

[0355] In one embodiment, the UE can also address the PDCCH of the P-RNTI for CsirsNotification monitoring in the PO as in embodiments 1-5 (e.g., in the case where CsirsNotification is not received during the wake-up signal or early paging indication timing).

[0356] In step S750, the UE can receive at least one of TRS or CSI RS based on at least one of trsNotification or CsirsNotification included in the DCI of the PDCCH addressed to the RNTI sent by the gNB during the wake-up signal or early paging indication timing. If the UE receives the PDCCH addressed to the RNTI during the wake-up signal or early paging indication timing, and the DCI of the received PDCCH includes at least one of trsNotification or CsirsNotification,

[0357] If the trsNotification bit is set to 1, the GNB transmits the TRS at the TRS timing according to the following rules:

[0358] --In one embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification period "N". In one embodiment, the TRS is sent by the GNB during the TRS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0359] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", then the GNB sends a TRS at the TRS timing in the SI modification period "N+1".

[0360] --In another embodiment, if a trsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification periods "N" and "N+1".

[0361] --In another embodiment, if a trsNotification set to 1 is received, the GNB sends a TRS at the TRS timing that occurs after that notification, until a trsNotification set to 0 is received or until the TRS configuration is removed from the SIBX (whichever occurs first).

[0362] --In another embodiment, if a trsNotification set to 1 is received in the activation period "N", the GNB transmits a TRS during the TRS timing in the activation period "N". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the TRS is transmitted by the GNB during the TRS timing of "X" activation periods starting from activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0363] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB sends a TRS at the TRS timing during the activation period "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0364] --In another embodiment, if a trsNotification set to 1 is received during the activation period "N", the GNB sends a TRS during the TRS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, or in units of slots / subframes / frames, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins at SFN X, where X mod activation period = 0; or the activation period begins at SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0365] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS during the TRS timing in the (default) DRX cycle "N". In one embodiment, the TRS is sent by the GNB during the TRS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0366] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS at the TRS timing in the (default) DRX cycle "N+1".

[0367] --In another embodiment, if a trsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a TRS during the TRS timings in the (default) DRX cycles "N" and "N+1".

[0368] If the CsirsNotification bit is set to 1, the GNB sends CSI RS at the CSI RS timing according to the following rules:

[0369] --In one embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", the GNB sends a TRS during the TRS timing in the SI modification period "N". In one embodiment, the TRS is sent by the GNB during the TRS timing of an "X" SI modification period from the SI modification period "N" or SI modification period "N+1", wherein the parameter X is signaled by the GNB.

[0370] --In another embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", then the GNB sends a CSI RS at the CSI RS timing in the SI modification period "N+1".

[0371] --In another embodiment, if a CsirsNotification set to 1 is received in the SI modification period "N", the GNB sends a CSI RS during the CSI RS timings in the SI modification periods "N" and "N+1".

[0372] --In another embodiment, if a CsirsNotification set to 1 is received, the GNB sends a TRS at the CSI RS timing that occurs after the notification, until a CsirsNotification set to 0 is received or until the CSIRS configuration is removed from SIB X (whichever occurs first).

[0373] --In another embodiment, if a CsirsNotification set to 1 is received during the activation period "N", the GNB sends a CSI RS at the CSI RS timing within the activation period "N". The length of the activation period is a multiple of the default DRX period, signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI. In one embodiment, the CSI RS is sent by the GNB at the CSI RS timing within the activation period "X" of activation period "N" or activation period "N+1", where the parameter X is signaled by the gNB.

[0374] --In another embodiment, if a CsirsNotification set to 1 is received during activation period "N", the GNB sends a CSI RS at the CSI RS timing during activation period "N+1". The length of the activation period is a multiple of the default DRX period, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0375] --In another embodiment, if a CsirsNotification set to 1 is received during the activation period "N", the GNB sends a CSI RS during the CSI RS timings in activation periods "N" and "N+1". The length of the activation period is a multiple of the default DRX period, signaled by the gNB in ​​the SI. The length of the default DRX period is also signaled by the gNB in ​​the SI. The activation period begins with SFN X, where X mod activation period = 0; or the activation period begins with SFN X, where X mod activation period = offset, where the offset is also signaled by the gNB in ​​the SI.

[0376] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS at the CSI RS timing in the (default) DRX cycle "N". In one embodiment, the CSI RS is sent by the GNB at the CSI RS timing in "X" DRX cycles starting from DRX cycle "N" or DRX cycle "N+1", where the parameter X is signaled by the gNB.

[0377] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS at the CSI RS timing in the (default) DRX cycle "N+1".

[0378] --In another embodiment, if a CsirsNotification set to 1 is received in the (default) DRX cycle "N", the GNB sends a CSI RS during the CSI RS timings in the (default) DRX cycles "N" and "N+1".

[0379] Early paging instructions with paging message information

[0380] The UE receives a wake-up signal or early paging indication configuration from the gNB for paging monitoring. This configuration can be received in system information or RRC signaling messages. In one embodiment, the configuration is cell-specific, and the UE applies the configuration to the DL BWP in which the UE monitors paging. In another embodiment, the configuration is BWP-specific. For example, a separate configuration is provided for each BWP in which paging is supported. In one embodiment, the configuration is provided only for the initial DL BWP, and the UE uses it to receive the wake-up signal or early paging indication in the initial DL BWP. In this case, the UE does not monitor the wake-up signal or early paging indication in other DL BWPs. The configuration indicates timing (or wake-up signal monitoring timing or early paging indication monitoring timing) and / or frequency domain resources (i.e., PRB). The configuration includes: the length of a wake-up signal or early paging indication monitoring timing (number of OFDM symbols), the number of wake-up signal or early paging indication monitoring timings per time slot, the number of time slots carrying wake-up signal or early paging indication monitoring timings, and the offset of the first time slot carrying the wake-up signal or early paging indication monitoring timing, wherein the offset is relative to the start of a paging frame (PF) or the start of a paging timing (PO). It should be noted that the wake-up signal or early paging indication precedes the PF and PO. The wake-up signal or early paging indication can be a PDCCH addressed to a predefined RNTI or an RNTI signaled by the gNB for early paging indication. In this case, the wake-up signal monitoring timing or early paging indication monitoring timing can also be referred to as the PDCCH monitoring timing for early paging indication. The PDCCH monitoring timing for early paging indication or wake-up signal can be indicated by search space parameters. The list of search space configurations can be signaled by the GNB. The search configuration to be used for early paging indication or wake-up signal can be signaled by the gNB. The gNB can indicate the search space ID of the search space configuration to be used for early paging indication or wake-up signal.

[0381] There can be one or more sets of wake-up signal monitoring opportunities, early paging indication monitoring opportunities, or PDCCH monitoring opportunities for early paging indication. The UE monitors the wake-up signal, early paging indication, or PDCCH for early paging indication within this set of monitoring opportunities. Each wake-up signal monitoring opportunity, early paging indication monitoring opportunity, or PDCCH monitoring opportunity for early paging indication in this set is associated with an SSB. This set can be per paging frame or per paging opportunity. If the set is per paging frame, UEs belonging to different POs of the paging frame will monitor the same set of wake-up signal monitoring opportunities, early paging indication monitoring opportunities, or PDCCH monitoring opportunities for early paging indication. If the set is per PO, UEs belonging to different POs of the paging frame will monitor different sets of wake-up signal monitoring opportunities, early paging indication monitoring opportunities, or PDCCH monitoring opportunities for early paging indication. Depending on the configuration, it is possible for several POs or PFs to have the same set of monitoring opportunities for wake-up signal, early paging indication, or PDCCH for early paging indication.

[0382] This group of wake-up signal monitoring opportunities, early paging indication monitoring opportunities, or PDCCH monitoring opportunities used for early paging indication consists of "S*X" monitoring opportunities. Parameters S and X are signaled by the gNB. S is the number of SSBs transmitted, and X is the number of monitoring opportunities for each SSB. If X is not signaled, it is assumed to be 1. SSBs are sequentially mapped to "S*X" monitoring opportunities, such that each SSB is sequentially mapped to a subset of "X" monitoring opportunities. For example, if there are 4 SSBs and X equals 2, the first two monitoring opportunities in the group are mapped to the first transmitted SSB, the next two monitoring opportunities in the group are mapped to the second transmitted SSB, the next two monitoring opportunities in the group are mapped to the third transmitted SSB, and so on.

[0383] Alternatively, the set of wake-up signal monitoring opportunities, early paging indication monitoring opportunities, or PDCCH monitoring opportunities used for early paging indication consists of "S" monitoring opportunities. The parameter S is signaled by the gNB. S is the number of SSBs transmitted. Each transmitted SSB is mapped sequentially to these monitoring opportunities in ascending order of its SSB index.

[0384] Monitoring opportunities that overlap with UL symbols are considered invalid. The UE can identify UL symbols based on the TDD configuration received from the gNB. The UE identifies its set of wake-up signal monitoring opportunities, early paging indication monitoring opportunities, or PDCCH monitoring opportunities used for early paging indication from the valid monitoring opportunities.

[0385] Effective wake-up signal monitoring opportunities, starting from the time slot “offset” before the start of the PF (or PO in another embodiment) and between that time slot and the start of the PF (or PO in another embodiment), are sequentially numbered / indexed. Then, “S*X” or “S” monitoring opportunities in ascending order are used to monitor wake-up signals or early paging indications or PDCCHs for early paging indications.

[0386] The earliest set of “S*X” valid monitoring opportunities at the offset before PF (in one embodiment) or PO (in another embodiment) are monitoring opportunities for monitoring wake-up signals or early paging indications, or for monitoring PDCCHs used for early paging indications. In one embodiment, X is always 1.

[0387] Alternatively, the earliest set of “S*X” valid monitoring opportunities, which begin after an offset prior to the first monitoring opportunity (in one embodiment) or the PO (in another embodiment), are monitoring opportunities for monitoring wake-up signals or early paging indications, or for monitoring the PDCCH used for early paging indications. In one embodiment, X is always 1.

[0388] Alternatively, valid monitoring opportunities preceding the PF (in one embodiment) or PO (in another embodiment) are sequentially numbered / indexed. The first opportunity number is signaled by the gNB. When monitoring is performed per PO, a starting opportunity number is signaled for each PO of the PF. The earliest set of "S*X" monitoring opportunities, starting from the first opportunity, are monitoring opportunities for monitoring wake-up signals or early paging indications, or for the PDCCH used for early paging indications.

[0389] Alternatively, valid monitoring opportunities preceding a PF (in one embodiment) or PO (in another embodiment) within a timer interval (duration) are sequentially numbered / indexed. The first opportunity number is signaled by the gNB. When monitoring is performed per PO, a starting opportunity number is signaled for each PO of the PF. The earliest set of "S*X" monitoring opportunities, starting from the first opportunity, are monitoring opportunities for monitoring wake-up signals or early paging indications, or for monitoring the PDCCH used for early paging indications. The timer interval duration can be signaled by the gNB, or the timer interval duration can be the timer interval between two PFs, or the timer interval duration can be equal to the SSB cycle, or the timer interval duration can be equal to a multiple of the SSB cycle, where the SSB cycle is signaled by the gNB.

[0390] Alternatively, the monitoring timing for the wake-up signal or early paging indication, or for the PDCCH used for early paging indication, is a valid monitoring timing within a first "duration" slot after an offset prior to the PF (in one embodiment) or PO (in another embodiment). Monitoring timing occurs periodically within duration slots according to the search space, where the duration and period are configured in the search space configuration.

[0391] Alternatively, the monitoring timing for the PDCCH used to monitor wake-up signals or early paging indications, or for early paging indications, is "S*X" consecutive valid monitoring timings starting from the first "duration" slot after the offset before the PF (in one embodiment) or PO (in another embodiment). Monitoring timing occurs periodically within duration slots according to the search space, where the duration and period are configured in the search space configuration.

[0392] Alternatively, the monitoring timing for the wake-up signal or early paging indication, or the PDCCH for the early paging indication, is the same as the timing for transmitting the SSB in the time domain. In the frequency domain, the PRB for the monitoring timing is frequency-division multiplexed (FDM) with the SSB PRB. The exact PRB signaled for the monitoring timing is transmitted by the gNB. The UE monitors the wake-up signal or early paging indication, or the PDCCH for the early paging indication, during the monitoring timing of the Nth SSB cycle before the start of the PF (in one embodiment) or PO (in another embodiment). N can be predefined or transmitted by the gNB. Alternatively, the UE monitors the wake-up signal or early paging indication, or the PDCCH for the early paging indication, during the monitoring timing of the Nth SSB cycle after the offset before the start of the PF (in one embodiment) or PO (in another embodiment). N can be predefined or transmitted by the gNB.

[0393] The UE also receives paging configuration from the gNB and determines the UE's PF / PO, as explained in each DRX cycle above.

[0394] The UE determines the wake-up signal timing, early paging indication monitoring timing, or PDCCH monitoring timing corresponding to the PF / PO determined by the UE. If a wake-up signal or early paging indication is received at the determined monitoring timing, or a PDCCH for early paging indication is received, and the wake-up signal or early paging indication indicates that there is paging for the UE, then the UE monitors the PO of the UE, or the UE monitors the PDCCH addressed to the P-RNTI in the PO of the UE. Otherwise, the UE does not monitor the PO. This operation is performed by the UE for its PO in each DRX cycle. It should be noted that the UE needs to monitor the PO, that is, receive and decode the PDCCH addressed to the P-RNTI in the PO, because the scheduling information for paging information is contained in the DCI of the PDCCH transmitted in the PO.

[0395] To reduce UE power consumption, it is recommended to include scheduling information for paging messages in the DCI of the wake-up signal or early paging indication. When an early paging indication is received during the monitoring period, the UE does not need to monitor its PO to obtain scheduling information for paging messages.

[0396] Figure 8 A diagram illustrates a method for sending and receiving scheduling information in a DCI for a wake-up signal or an early paging indication, according to an embodiment of the present disclosure.

[0397] In step S810, the gNB can send PF / PO configuration and early paging indication configuration.

[0398] 1.gNB can send PF / PO configuration and early paging indication configuration in system information.

[0399] 2. If one or more UEs are paging:

[0400] -gNB sends the first PDCCH addressed to the first RNTI during the first set of PDCCH monitoring opportunities, where these PDCCH monitoring opportunities occur before the paging opportunity.

[0401] -gNB sends the second PDCCH addressed to the second RNTI during the second set of PDCCH monitoring times, where these PDCCH monitoring times are the monitoring times of the PO.

[0402] The DCI of the first PDCCH includes paging information, which includes frequency domain resource allocation, time domain resource allocation, VRB-to-PRB mapping, modulation and coding scheme, and TB scaling. The time domain resource allocation pertains to the time slot in which the DCI of the first PDCCH is received. The DCI of the first PDCCH also includes paging group / subgroup information, indicating the paging group / subgroup where paging is present. The DCI of the first PDCCH may also include short messages, SI update notifications, or emergency notifications, etc.

[0403] The DCI of the second PDCCH includes paging information scheduling information, which includes frequency domain resource allocation, time domain resource allocation, VRB-to-PRB mapping, modulation and coding scheme, and TB scaling. Time domain resource allocation pertains to the time slot in which the DCI of the second PDCCH is received. The DCI of the second PDCCH may also include short messages, SI update notifications, or emergency notifications, etc.

[0404] Figure 9A diagram is shown illustrating a scenario where scheduling information in the DCI of the first PDCCH and the scheduling information in the DCI of the second PDCCH are used for paging messages, according to an embodiment of the present disclosure.

[0405] - In one embodiment, the scheduling information in the DCI of the first PDCCH and the scheduling information in the DCI of the second PDCCH ensures that time-domain and frequency-domain resources, VRB-to-PRB mapping, modulation and coding schemes, and TB scaling are for the same scheduling paging message (or in other words, corresponding to the same TB). This is in Figure 8 As shown in the diagram. Its advantage is that the paging identifiers of UEs that support early paging indication and those that do not support early paging indication can be included in the same paging message.

[0406] Figure 10 A diagram is shown illustrating a scenario where scheduling information in the DCI of the first PDCCH and the scheduling information in the DCI of the second PDCCH are used for paging messages, according to an embodiment of the present disclosure.

[0407] In one embodiment, the scheduling information in the DCI of the first PDCCH and the scheduling information in the DCI of the second PDCCH are respectively for the first paging message and the second paging message. The first paging information includes the paging identifier of the UE that supports early paging indication. The second paging information includes the paging identifier of the UE that does not support early paging indication.

[0408] 3. The UE receives system information from the gNB.

[0409] In step S820, the UE can obtain at least one of PF / PO configuration or early paging indication configuration. In one embodiment, the UE can obtain the PF / PO configuration from the received system information. If the UE supports early paging indication, the UE also obtains the early paging indication configuration from the received system information.

[0410] In step S830, the UE can determine its PF / PO based on the PF / PO configuration. If the UE supports early paging indication, the UE also determines the early paging indication timing corresponding to its PF / PO.

[0411] - If the UE supports early paging indication, the UE monitors the first PDCCH addressed to the first RNTI during the early paging indication timing.

[0412] --If a first PDCCH is received and the DCI indicates paging corresponding to the UE's paging group / subgroup, the UE obtains scheduling information for the paging message from the DCI of the first PDCCH. The UE receives the paging information in the resource according to the scheduling information.

[0413] -- In one embodiment, if the UE fails to receive the first PDCCH, the UE monitors the second PDCCH addressed to the second RNTI in the PO. In one embodiment, when the UE fails to receive the first PDCCH, the gNB may indicate to the UE whether it should monitor the second PDCCH addressed to the second RNTI in the PO

[0414] - If the UE does not support early paging indication, the UE monitors the second PDCCH addressed to the second RNTI in the PO.

[0415] If the second PDCCH is received and the short message indicator in the DCI indicates that the paging message is scheduled, the UE obtains the scheduling information for the paging message from the DCI of the second PDCCH. The UE receives the paging information in the resource according to the scheduling information.

[0416] <UE-to-Network Relay and Paging Aspects>

[0417] The remote UE uses the UE-to-network relay UE to receive paging from the gNB. The remote UE may communicate with the UE-to-network relay UE via the PC5 interface (the interface between UEs over which UEs communicate with each other using sidelink communication). The UE-to-network relay UE is a UE within the coverage of the gNB and may be in the RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED state.

[0418] Embodiment 2-1:

[0419] The remote UE may send its UE_ID and DRX period T to the UE-to-network relay UE.

[0420] - T is the UE-specific DRX period configured by the network to the remote UE using NAS signaling

[0421] - T is the UE-specific inactive state DRX period configured to the remote UE via RRC signaling when the UE enters the RRC INACTIVE state

[0422] - If the UE-specific DRX period is configured by both NAS and RRC signaling, T is the minimum of the two DRX periods.

[0423] - The UE_ID is equal to 5G S-TMSI mod 1024. In an alternative embodiment, one of other values such as 2048, 3072, 4096, 5120, 6144, 1024*X (where X is an integer) may be used instead of 1024 to determine the UE_ID.

[0424] UE to Network Relay: The UE can receive system information from the gNB or paging configuration (N, Ns, default DRX cycle length, paging search space (and CORESET) configuration) in the BWP configuration.

[0425] - To monitor paging by a remote UE, the UE determines the PF / PO to the network relay UE as follows:

[0426] --PF is a radio frame with system frame number "SFN", which satisfies the equation (SFN + PF_offset) mod T1 = (T1 div N) * (UE_ID mod N), where UE_ID is the UE_ID received from the remote UE, and T1 is the minimum value of [the DRX period T received from the remote UE and the default DRX period length received from the gNB].

[0427] --Index(i_s), indicating the index of the PO is determined by i_s = floor(UE_ID / N) mod Ns.

[0428] --N: The total number of paging frames received from the gNB

[0429] --Ns: The number of paging opportunities received from the gNB for the PF

[0430] --PF_offset: The offset determined by PF and received from gNB.

[0431] --UE_ID: Received from remote UE

[0432] -UE to Network Relay: The UE can monitor the PF / PO determined above to receive paging from remote UEs.

[0433] When a PDCCH addressing to a P-RNTI is received in the PO, the UE can decode the TB scheduled by the PDCCH and obtain the paging message from the decoded TB.

[0434] -UE to Network Relay: A UE can forward received paging messages to a remote UE.

[0435] Example 2-2:

[0436] The remote UE sends its UE_ID, DRX period T, and paging identifier (5G S-TMSI and / or I-RNTI) to the network relay UE. In one embodiment, the UE_ID can be skipped.

[0437] -T is the UE-specific DRX period configured by the network to the remote UE using NAS signaling.

[0438] -T is a UE-specific inactive state DRX period configured for the remote UE via RRC signaling when the UE enters the RRC INACTIVE state.

[0439] - If the UE's specific DRX period is configured by NAS and RRC signaling, T is the minimum of these two DRX periods.

[0440] - The UE ID is equal to 5G S-TMSI mod 1024. In alternative embodiments, one of other values ​​such as 2048, 3072, 4096, 5120, 6144, 1024*X (where X is an integer) can be used instead of 1024 to determine the UE_ID.

[0441] In one embodiment, if the remote UE is in the RRC_INACTIVE state, the remote UE can send an indicator to the UE-to-network relay UE to indicate that the PO should be monitored using the same index (i_s) as in the RRC_IDLE case. In this case, the remote UE also sends a UE-specific DRX cycle to the UE-to-network relay UE, which is configured by the network to the remote UE using NAS signaling. In another embodiment, if the remote UE is in the RRC_INACTIVE state and the network supports monitoring the PO in RRC_INACTIVE using the same index (i_s) as in RRC_IDLE, the remote UE can send an indicator to the UE-to-network relay UE to indicate that the PO should be monitored using the same index (i_s) as in the RRC_IDLE case. In this case, the remote UE also sends a UE-specific DRX cycle to the UE-to-network relay UE, which is configured by the network to the remote UE using NAS signaling. A remote UE can learn whether the network supports monitoring POs with the same index (i_s) as in RRC_IDLE in RRC_INACTIVE via system information received from the network by the remote UE or from the network relay UE (the network relay UE can receive system information from the gNB and forward it to the remote UE), or via an RRCLease message received by the remote UE from the GNB. When the remote UE is in the RRC_CONNECTED state, the remote UE can receive RRCLease from the gNB.

[0442] UE to Network Relay: The UE can receive system information from the gNB or paging configuration (N, Ns, default DRX cycle length, paging search space (and CORESET) configuration) in the BWP configuration.

[0443] - To monitor paging by a remote UE, the PF / PO can be determined from the network relay UE as follows:

[0444] --PF is a radio frame with system frame number "SFN" that satisfies the equation (SFN+PF_offset)mod T1=(T1div N)*(UE_ID mod N), where UE_ID is the UE_ID received from the remote UE, and T1 is the minimum of [the DRX period T received from the remote UE and the default DRX period length received from the gNB].

[0445] --Index (i_s), indicating the index of the PO, is determined by i_s = floor(UE_ID / N) mod Ns. N is signaled by the network in the form of DRX cycle lengths (e.g., DRX cycle length, DRX cycle length / 2, DRX cycle length / 4, DRX cycle length / 8, DRX cycle length / 16). To calculate i_s, the DRX cycle length is set to T1.

[0446] If the UE-to-network relay UE has received an indication from the remote UE indicating that a PO with the same index (i_s) as RRC_IDLE should be monitored, and the system information received by the UE-to-network relay UE from the gNB includes an indication to monitor the PO in RRC_INACTIVE with the same index as RRC_IDLE (or alternatively, if the UE-to-network relay UE has received an indication indicating that a PO with the same index (i_s) as RRC_IDLE should be monitored from the remote UE, and the system information received by the UE-to-network relay UE from the gNB includes an indication to monitor the PO in RRC_INACTIVE with the same index as RRC_IDLE, and Ns>1, and T1 is not equal to T2): index (i_s), the index of the indicated PO is determined by i_s = floor(UE_ID / N) mod Ns, where N is signaled by the network with a DRX cycle length (e.g., DRX cycle length, DRX cycle length / 2, DRX cycle length / 4, DRX cycle length / 8, DRX cycle length / 16). To calculate i_s, the DRX cycle length is set to T2, where T2 = the minimum of [the UE-specific DRX cycle configured by the network for the remote UE using NAS signaling and the default DRX cycle length received from the gNB]. The UE-specific DRX cycle configured by the network for the remote UE using NAS signaling is received by the UE from the remote UE by the network relay UE.

[0447] --N: The total number of paging frames received from the gNB, transmitted by the network in DRX period lengths (e.g., DRX period length, DRX period length / 2, DRX period length / 4, DRX period length / 8, DRX period length / 16).

[0448] --Ns: The number of paging opportunities received from the gNB for the PF

[0449] --PF_offset: The offset determined by PF and received from gNB.

[0450] --UE_ID: Received from a remote UE, or UE_ID equal to 5G S-TMSI mod 1024 received from a remote UE. In alternative embodiments, one of other values ​​such as 2048, 3072, 4096, 5120, 6144, 1024*X (where X is an integer) can be used instead of 1024 to determine UE_ID.

[0451] -UE to Network Relay: The UE can monitor the PF / PO determined above to receive paging from remote UEs.

[0452] When a PDCCH addressing to a P-RNTI is received in the PO, the UE can decode the TB scheduled by the PDCCH and obtain the paging message from the decoded TB.

[0453] - UE to network relay UE can check whether the received paging information includes the UE's paging identifier, which is received from the remote UE.

[0454] --If the received paging information includes the UE's paging identifier, the UE-to-network relay UE can indicate to the remote UE that a paging has occurred. If the remote UE has sent both the 5G S-TMSI and I-RNTI to the UE-to-network relay UE, and if the UE's 5G S-TMSI is included in the received paging message, the UE-to-network relay UE can indicate that the paging is a CN paging; if the UE's I-RNTI is included in the received paging message, the UE-to-network relay UE can indicate that the paging is a RAN paging.

[0455] Examples 2-3:

[0456] The UE can receive system information from the gNB or paging configuration (N, Ns, default DRX cycle length, paging search space (and CORESET) configuration) in the BWP configuration.

[0457] UE sends paging configuration or default DRX cycle length to remote UE via network relay UE

[0458] The remote UE sends its UE_ID and DRX period T to the network relay UE. In one embodiment, the UE_ID can be skipped.

[0459] --In the RRC_INACTIVE state, T is determined by the shortest of the UE-specific DRX value configured by RRC, the UE-specific DRX value configured by NAS, and the default DRX value received from the UE to the network relay UE.

[0460] - In the RRC_IDLE state, T is determined by the shortest of the UE-specific DRX value configured by the NAS and the default DRX value received from the UE to the network relay UE. If the UE-specific DRX is not configured by the upper layer (i.e., the NAS), the default value is applied.

[0461] -UE_ID equals 5GS TMSI mod 1024. In alternative embodiments, one of other values ​​such as 2048, 3072, 4096, 5120, 6144, 1024*X (where X is an integer) can be used instead of 1024 to determine UE_ID.

[0462] UE to Network Relay: The UE receives system information from the gNB or paging configuration (N, Ns, default DRX cycle length, paging search space (and CORESET) configuration) in the BWP configuration.

[0463] - To monitor paging by a remote UE, the UE determines the PF / PO to the network relay UE as follows:

[0464] --PF is a radio frame with system frame number "SFN", which satisfies the equation (SFN + PF_offset) mod T1 = (T1 div N) * (UE_ID mod N), where UE_ID is the UE_ID received from the remote UE, and T1 is the DRX period length received from the UE.

[0465] --Index(i_s), indicating the index of the PO is determined by i_s = floor(UE_ID / N) mod Ns.

[0466] --N: The total number of paging frames received from the gNB, transmitted by the network in DRX period lengths (e.g., DRX period length, DRX period length / 2, DRX period length / 4, DRX period length / 8, DRX period length / 16).

[0467] --Ns: The number of paging opportunities received from the gNB for the PF

[0468] --PF_offset: The offset determined by PF and received from gNB.

[0469] --UE_ID: Received from a remote UE, or UE_ID equal to 5G S-TMSI mod 1024 received from a remote UE. In alternative embodiments, one of other values ​​such as 2048, 3072, 4096, 5120, 6144, 1024*X (where X is an integer) can be used instead of 1024 to determine UE_ID.

[0470] -UE to Network Relay: The UE can monitor the PF / PO determined above to receive paging from remote UEs.

[0471] When a PDCCH addressing to a P-RNTI is received in the PO, the UE can decode the TB scheduled by the PDCCH and obtain the paging message from the decoded TB.

[0472] -UE to Network Relay: A UE can forward received paging messages to a remote UE.

[0473] Examples 2-4:

[0474] UE to Network Relay: The UE can receive system information from the gNB or paging configuration (N, Ns, default DRX cycle length, paging search space (and CORESET) configuration) in the BWP configuration.

[0475] UE to network relay UE can send paging configuration or default DRX cycle length to remote UE.

[0476] The remote UE can send its UE_ID, DRX period T, and paging identifier (5G S-TMSI and / or I-RNTI) to the network relay UE.

[0477] --In the RRC_INACTIVE state, T is determined by the shortest of the UE-specific DRX value configured by RRC, the UE-specific DRX value configured by NAS, and the default DRX value received from the UE to the network relay UE.

[0478] - In the RRC_IDLE state, T is determined by the shortest of the UE-specific DRX value configured by the NAS and the default DRX value received from the UE to the network relay UE. If the UE-specific DRX is not configured by the upper layer (i.e., the NAS), the default value is applied.

[0479] - The UE ID is equal to 5G S-TMSI mod 1024. In alternative embodiments, one of other values ​​such as 2048, 3072, 4096, 5120, 6144, 1024*X (where X is an integer) can be used instead of 1024 to determine the UE_ID.

[0480] UE to Network Relay: The UE can receive system information from the gNB or paging configuration (N, Ns, default DRX cycle length, paging search space (and CORESET) configuration) in the BWP configuration.

[0481] - To monitor paging by a remote UE, the PF / PO can be determined from the network relay UE as follows:

[0482] --PF is a radio frame with system frame number "SFN", which satisfies the equation (SFN + PF_offset) mod T1 = (T1 div N) * (UE_ID mod N), where UE_ID is the UE_ID received from the remote UE, and T1 is the DRX period length received from the UE.

[0483] --Index(i_s), indicating the index of the PO is determined by i_s = floor(UE_ID / N) mod Ns.

[0484] --N: The total number of paging frames received from the gNB

[0485] --Ns: The number of paging opportunities received from the gNB for the PF

[0486] --PF_offset: The offset determined by PF and received from gNB.

[0487] --UE_ID: Received from remote UE

[0488] -UE to Network Relay: The UE can monitor the PF / PO determined above to receive paging from remote UEs.

[0489] When a PDCCH addressing to a P-RNTI is received in the PO, the UE can decode the TB scheduled by the PDCCH and obtain the paging message from the decoded TB.

[0490] - UE to network relay UE can check whether the received paging information includes the UE's paging identifier, which is received from the remote UE.

[0491] --If the received paging information includes the UE's paging identifier, the UE-to-network relay UE indicates to the remote UE that there is a paging. If the remote UE has sent both the 5GS-TMSI and I-RNTI to the UE-to-network relay UE, and if the remote UE's 5GS-TMSI is included in the received paging message, the UE-to-network relay UE can indicate to the remote UE that the paging is a CN paging; if the UE's I-RNTI is included in the received paging message, the UE-to-network relay UE can indicate to the remote UE that the paging is a RAN paging.

[0492] If the UE-to-network relay UE is in RRC CONNECTED state, upon receiving a request to monitor paging from a remote UE or to monitor paging from a remote UE, the UE-to-network relay UE can notify the gNB that it needs to monitor paging from a remote UE. The gNB ensures that the UE-to-network relay UE's active BWP is configured for monitoring the paging search space (and CORESET). It should be noted that when the UE-to-network relay UE's active BWP is configured for monitoring the paging search space, the UE-to-network relay UE monitors paging within its active BWP.

[0493] Alternatively, the UE-to-Network Relay UE can notify the gNB of the paging identifier of a remote UE that the UE-to-Network Relay UE intends to monitor. The gNB ensures that the UE-to-Network Relay UE's active BWP is configured for monitoring the paging search space (i.e., the common search space and coreset for paging) or (e.g., if the UE-to-Network Relay UE's active BWP is not configured for monitoring the paging search space), the gNB can indicate to the UE-to-Network Relay UE that it has notified the gNB of its paging identifier whenever there is a paging for a remote UE. The gNB can send a dedicated RRC message (where the PDCCH of the TB including the dedicated RRC message is addressed to the C-RNTI, and the PDCCH of the TB including the paging message is addressed to the P-RNTI) which includes the paging identifier of one or more paging UEs, wherein the paging UEs are those whose paging identifiers were notified to the GNB by the UE-to-Network Relay UE. In one embodiment, the gNB may indicate an index of the paging identifier instead of the paging identifier itself, where the index refers to an entry in the list of paging identifiers sent by the UE to the gNB from the network relay UE. For example, suppose the UE to network relay UE has sent a list of 5 paging identifiers to the gNB. These 5 paging identifiers can be indexed sequentially from 0 to 4. 0 refers to the first entry in the list, 1 refers to the second entry, and so on.

[0494] In one embodiment, a UE-to-network relay UE can indicate in its relay discovery message whether it is in RRC IDLE, RRC INACTIVE, or RRC CONNECTED state. Remote UEs interested in UE-to-network relay monitoring can use paging monitoring, or if a remote UE is in RRC IDLE or RRC INACTIVE, it can preferentially select a relay UE from those not in RRC CONNECTED state.

[0495] We are currently researching a UE-to-network relay architecture, where the relay UE relays traffic between the remote UE and the network. UE-to-network relay achieves extended coverage and power savings for the remote UE. Communication between the UE-to-network relay and the gNB is based on 5G communication between the UE and the gNB. Communication between the remote UE and the UE-to-network relay UE is based on sidelink communication. The UE-to-network relay UE can relay paging and system information to the remote UE. For paging, the relay UE monitors both its own paging timing and the paging timing of the remote UE. If the relay UE is in RRC_CONNECTED and the pagingSearchSpace is not configured in an active DL BWP, the relay UE cannot monitor any POs. Therefore, it cannot relay paging.

[0496] Example 3-1:

[0497] Figure 11 A flowchart of a method for monitoring paging of a remote UE according to an embodiment of the present disclosure is shown.

[0498] One method disclosed herein ( Figure 11 In this context, the operation for monitoring paging of at least one remote UE is as follows:

[0499] At steps S1110-A and S1110-B, remote UEs 30 and 35 can send paging monitoring requests to relay UE 40.

[0500] For example, remote UEs 30 and 35 can send their 5G-S-TMSI (also known as UE-to-network relay UE) to relay UE 40; for example, if the remote UE is in RRC_INACTIVE, remote UEs 30 and 35 can send their I-RNTI (refer to steps S1100-A and S1100-B). These parameters can be sent by remote UEs 30 and 35 to relay UE 40 via sidelink signaling radio bearer (SL SLRB) or via sidelink data radio bearer using RRC signaling messages. The signaling message carrying these parameters is sent in a MAC PDU, in which the Layer 2 identifier of the remote UE (or a portion thereof) and the Layer 2 identifier of the relay UE (or a portion thereof) are added to the header of the MAC PDU. The MAC PDU is then sent via PSSCH.

[0501] In one embodiment, the relay UE 40 may be in the RRC_CONNECTED state (refer to step S1105). In one embodiment, the relay UE 40 may receive an RRCReconfiguration message including the DL BWP configuration.

[0502] At step S1115-A, the relay UE 40 can check whether the active DL BWP is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration). The paging search space can also be referred to as "public search space and public coreset for paging" or "public search space for paging".

[0503] -If the active DL BWP of relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration):

[0504] a. In step S1120, the relay UE 40 may send a list of paging identifiers (i.e., the 5G-S-TMSI and I-RNTI of the remote UEs) received from the remote UEs 30 and 35 to the gNB 10. For example, if the relay UE 40 is connected to two remote UEs, namely remote UE1 and remote UE2, and the relay UE receives 5G-S-TMSI-1 and I-RNTI-1 from remote UE1 and 5G-S-TMSI-2 and I-RNTI-2 from remote UE2, the relay UE 40 sends 5G-S-TMSI-1, I-RNTI-1, 5G-S-TMSI-2, and I-RNTI-2 to the gNB 10. In one embodiment, the gNB 10 may send two lists, one of which includes the 5G-S-TMSI and the second list includes the I-RNTI.

[0505] b. At step S1140, relay UE 40 may receive a dedicated RRC message including paging information of one or more remote UEs 30, 35. This RRC message can be received via DCCH. The PDCCH of the TB including this RRC message is addressed to C-RNTI.

[0506] i. In one embodiment, in step S1130, the paging information may include the paging identifier (5G-S-TMSI or I-RNTI) of one or more remote UEs 30, 35.

[0507] ii. In another embodiment, in step S1130, the paging information may include a paging identifier index corresponding to a paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10.

[0508] 1. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially starting from zero. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is zero, the paging identifier index of the paging identifier in the second entry of the list is one, the paging identifier index of the paging identifier in the third entry of the list is two, and the paging identifier index of the paging identifier in the fourth entry of the list is three.

[0509] 2. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially from the beginning. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is one, the paging identifier index of the paging identifier in the second entry of the list is two, the paging identifier index of the paging identifier in the third entry of the list is three, and the paging identifier index of the paging identifier in the fourth entry of the list is four.

[0510] 3. In one embodiment, the relay UE 40 may send a paging identifier index along with each paging identifier.

[0511] -If the active DL BWP of relay UE 40 is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration):

[0512] a. In step S1150, the relay UE 40 can monitor the PO of the remote UE in order to receive the paging of the remote UE.

[0513] - If a 5G-S-TMSI is received from a remote UE, and that 5G-S-TMSI (or the corresponding paging identifier index) is included in the received paging message:

[0514] --The relay UE 40 can send a CN paging indication to the remote UE (using a signaling message via MAC CE or through a sidelink signaling radio bearer or SCI). The relay UE can send a 5G-S-TMSI to the remote UE.

[0515] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0516] - If an I-RNTI is received from a remote UE, and the I-RNTI (or the corresponding paging identifier index) is included in the received paging message: the relay UE may send the I-RNTI to the remote UE.

[0517] --Relay UE 40 can send RAN paging instructions to the remote UE (using MAC CE or signaling messages via sidelink signaling radio bearer or SCI).

[0518] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0519] -gNB 10 Operation: If the active DL BWP of the relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration).

[0520] a. If gNB 10, connected to relay UE 40, receives paging messages from remote UEs 30 and 35—that is, if gNB 10 receives a paging message from a CN or another GNB, wherein the paging message includes one or more paging identifiers included in the paging identifier list received from relay UE 40, or if gNB receives DL data from a remote UE in RRC_INACTIVE, and its paging identifier is received from the relay UE—in steps S1135 to S1140, gNB 10 may send a dedicated RRC message including paging information for remote UEs 30 and 35. The RRC message can be sent via DCCH. The MAC sub-header may be included in the MAC PDU carrying this RRC message, and the LCID of the DCCH is included in the MAC sub-header. gNB 10 may send a PDCCH addressing to C-RNTI and a TB / MAC PDU carrying this RRC message on the PDSCH.

[0521] i. In one embodiment, in step S1130, the paging information may include the paging identifiers (5G-S-TMSI, I-RNTI) of one or more remote UEs.

[0522] ii. In another embodiment, in step S1130, the paging information may include a paging identifier index corresponding to a paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10.

[0523] 1. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially starting from zero. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is zero, the paging identifier index of the paging identifier in the second entry of the list is one, the paging identifier index of the paging identifier in the third entry of the list is two, and the paging identifier index of the paging identifier in the fourth entry of the list is three.

[0524] 2. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially from the beginning. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is one, the paging identifier index of the paging identifier in the second entry of the list is two, the paging identifier index of the paging identifier in the third entry of the list is three, and the paging identifier index of the paging identifier in the fourth entry of the list is four.

[0525] 3. In one embodiment, the relay UE 40 may send a paging identifier index along with each paging identifier.

[0526] - If the active DL BWP of relay UE 40 is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration): In steps S1170, S1180, and S1190, gNB 10 can transmit the paging message on the PDSCH via the PDCCH addressed to the P-RNTI in the PO and the corresponding TB / MAC PDU carrying the paging message. In this case, the MAC sub-header is not included in the MAC PDU carrying the paging information MAC SDU.

[0527] Example 3-2:

[0528] Figure 12 A flowchart of a method for monitoring paging of a remote UE according to an embodiment of the present disclosure is shown.

[0529] One method disclosed herein ( Figure 12 In this context, the operation for monitoring paging of at least one remote UE is as follows:

[0530] In steps S1210-A and S1210-B, remote UEs 30 and 35 can send paging monitoring requests to relay UE 20.

[0531] For example, remote UEs 30 and 35 can send their 5G-S-TMSI to relay UE 40; for example, if the remote UE is in RRC_INACTIVE (refer to steps S1100-a and S1100-b), remote UEs 30 and 35 can send their I-RNTI. These parameters can be sent by remote UEs 30 and 35 to relay UE 40 via sidelink signaling radio bearer (SL SLRB) or via sidelink data radio bearer using RRC signaling messages. The signaling message carrying these parameters is sent in a MAC PDU, in which the Layer 2 identifier of the remote UE (or a portion of the Layer 2 identifier of the remote UE) and the Layer 2 identifier of the relay UE (or a portion of the Layer 2 identifier of the relay UE) are added to the header of the MAC PDU. The MAC PDU is then sent via PSSCH.

[0532] In one embodiment, the relay UE 40 may be in the RRC_CONNECTED state (see step S1205).

[0533] In one embodiment, the relay UE 40 may receive an RRCReconfiguration message that includes the DL BWP configuration.

[0534] At step S1215, the relay UE 40 may send a list of paging identifiers (i.e., the 5G-S-TMSI and I-RNTI of the remote UEs) received from the remote UEs 30 and 35 to the gNB 10. For example, if the relay UE 40 is connected to two remote UEs, namely remote UE1 and remote UE2, and the relay UE 40 receives 5G-S-TMSI-1 and I-RNTI-1 from remote UE1 and 5G-S-TMSI-2 and I-RNTI-2 from remote UE2, the relay UE 40 sends 5G-S-TMSI-1, I-RNTI-1, 5G-S-TMSI-2, and I-RNTI-2 to the gNB 10. In one embodiment, the gNB 10 may send two lists, one of which includes the 5G-S-TMSI and the second list includes the I-RNTI.

[0535] At step S1220-A, the relay UE 40 can check whether the active DL BWP is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration).

[0536] -If the active DL BWP of relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration):

[0537] a. In step S1240, the relay UE 40 may receive a dedicated RRC message that includes paging information from one or more remote UEs 30, 35. This RRC message can be received via the DCCH.

[0538] i. In one embodiment, at step S1230, the paging information may include the paging identifiers (5G-S-TMSI or I-RNTI) of one or more remote UEs.

[0539] ii. In another embodiment, in step S1230, the paging information may include a paging identifier index corresponding to a paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10.

[0540] 1. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially starting from zero. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is zero, the paging identifier index of the paging identifier in the second entry of the list is one, the paging identifier index of the paging identifier in the third entry of the list is two, and the paging identifier index of the paging identifier in the fourth entry of the list is three.

[0541] 2. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially from the beginning. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is one, the paging identifier index of the paging identifier in the second entry of the list is two, the paging identifier index of the paging identifier in the third entry of the list is three, and the paging identifier index of the paging identifier in the fourth entry of the list is four.

[0542] 3. In one embodiment, the relay UE 40 may send a paging identifier index along with each paging identifier.

[0543] -If the active DL BWP of relay UE 40 is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration):

[0544] a. In step S1250, the relay UE 40 can monitor the PO of the remote UE in order to receive the paging of the remote UE.

[0545] - If a 5G-S-TMSI is received from a remote UE, and that 5G-S-TMSI (or the corresponding paging identifier index) is included in the received paging message.

[0546] --The relay UE 40 can send a CN paging indication to the remote UE (using a signaling message via MAC CE or through a sidelink signaling radio bearer or SCI). The relay UE can send a 5G-S-TMSI to the remote UE.

[0547] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0548] - If an I-RNTI is received from a remote UE, and that I-RNTI (or its corresponding paging identifier index) is included in the received paging message.

[0549] --A relay UE can send a RAN paging instruction to the remote UE (using a MAC CE or a signaling message via a sidelink signaling radio bearer or SCI). A relay UE can send an I-RNTI to the remote UE.

[0550] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0551] -gNB Operation: If the active DL BWP of relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration),

[0552] a. If gNB 10, connected to relay UE 40, receives paging messages from remote UEs 30 and 35—that is, if gNB 10 receives a paging message from a CN or another GNB, wherein the paging message includes one or more paging identifiers included in the paging identifier list received from relay UE 40, or if gNB receives DL data from a remote UE in RRC_INACTIVE, whose paging identifier is received from the relay UE: In steps S1235 to S1240, gNB 10 may send a dedicated RRC message including paging information for remote UEs 30 and 35. The RRC message can be sent via DCCH. The MAC PDU carrying the RRC message may include a MAC sub-header, and the LCID of DCCH is included in the MAC sub-header. gNB 10 may send a PDCCH addressing to C-RNTI and a TB / MAC PDU carrying the RRC message on the PDSCH.

[0553] i. In one embodiment, in step S1230, the paging information may include the paging identifiers (5G-S-TMSI, I-RNTI) of one or more remote UEs.

[0554] ii. In another embodiment, in step S1230, the paging information may include a paging identifier index corresponding to a paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10.

[0555] 1. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially starting from zero. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is zero, the paging identifier index of the paging identifier in the second entry of the list is one, the paging identifier index of the paging identifier in the third entry of the list is two, and the paging identifier index of the paging identifier in the fourth entry of the list is three.

[0556] 2. In one embodiment, each paging identifier in the paging identifier list sent by the relay UE 40 to the gNB 10 is indexed sequentially from the beginning. For example, if there are 4 entries in the paging identifier list, the paging identifier index of the paging identifier in the first entry of the list is one, the paging identifier index of the paging identifier in the second entry of the list is two, the paging identifier index of the paging identifier in the third entry of the list is three, and the paging identifier index of the paging identifier in the fourth entry of the list is four.

[0557] 3. In one embodiment, the relay UE 40 may send a paging identifier index along with each paging identifier.

[0558] - If the active DL BWP of relay UE 40 is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration): gNB 10 can send the paging message on the PDSCH via the PDCCH addressed to the P-RNTI in the PO and the corresponding TB / MAC PDU carrying the paging message in steps S1270, S1280, and S1290. In this case, the MAC sub-header is not included in the MAC PDU carrying the paging information MAC SDU.

[0559] In alternative embodiments of Examples 3-1 and 3-2:

[0560] - In one embodiment, the remote UE 30 may notify the relay UE 40 of the new paging ID (instead of 5G-S-TMSI / I-RNTI).

[0561] --RRC IDLE and RRC INACTIVE can have separate new paging IDs.

[0562] --RRC IDLE and RRC_INACTIVE can both have the same new paging ID.

[0563] ---For example, in this case, the remote UE can additionally indicate whether the remote UE wants to monitor RAN paging; or the remote UE can indicate its RRC status.

[0564] - In one embodiment, the relay UE 40 may send a list of paging identifiers (i.e., new IDs) received from the remote UE to the gNB 10.

[0565] - In one embodiment, the relay UE 40 will check the new paging ID or the corresponding paging identifier index in the paging message received from the gNB 10, instead of the I-RNTI / 5G-S-TMSI of the remote UE.

[0566] --If the new paging ID is common to both RRC IDLE and RRC_INACTIVE and is included in the paging message, the paging message from gNB 10 can indicate whether the paging is a RAN paging / CN paging (or UE state).

[0567] - In one embodiment, if a new paging ID is received from a remote UE and that paging ID is included in the received paging message.

[0568] --The relay UE 40 can send a paging indication to the remote UE (using MAC CE, signaling message, or SCI). The relay UE 40 can also indicate whether the paging is RAN paging or CN paging.

[0569] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0570] In the public disclosures that use the new paging ID instead of 5G-S-TMSI / I-RNTI, the aspects of the new paging ID are as follows:

[0571] Option 1: CN assigns a new ID

[0572] - During registration or in RRC connection state (e.g., when the UE connects via a relay UE), the UE can request a new ID, and the network (i.e., the AMF) can assign a new ID using a NAS message.

[0573] - For CN paging, the AMF can include this new ID of the remote UE instead of the 5G-S-TMSI in the paging message sent to gNB 10. Then, gNB 10 can include this new ID in the paging message sent in PDSCH.

[0574] For RAN paging, the AMF can use the RAN Assist Information message to notify the RAN (i.e., gNB) of this new ID of the remote UE, and the ID can then be stored in the anchor gNB. The anchor gNB can include this new ID in the paging message sent to another gNB. The gNB then includes the new ID in the paging message sent in the PDSCH.

[0575] Option 2: RAN can assign a new ID.

[0576] - When the remote UE is in a connected state, the remote UE can notify the gNB 10 that the remote UE is interested in relay operation, and the gNB 10 can assign a new ID.

[0577] -When the remote UE is in Idle state:

[0578] When the gNB 10 assigns an ID to a remote UE while in connected state, the gNB 10 notifies the AMF of the UE's new ID. The AMF stores the ID and links it to the 5G-S-TMSI. In the CN paging message, the AMF can include the remote UE's ID instead of the 5G-S-TMSI in the paging information sent to the gNB 10. The GNB 10 can then include this ID in the paging message sent in the PDSCH.

[0579] -When the remote UE is in INACTIVE state:

[0580] --For CN paging, the operation can be interpreted as being in the Idle state.

[0581] --For RAN paging, the new ID can be stored in the anchor gNB. The anchor gNB can include the new ID in the paging message sent to another gNB. The gNB then includes the ID in the paging message sent in the PDSCH.

[0582] Example 3-3:

[0583] Figure 13 A flowchart of a method for monitoring paging of a remote UE according to an embodiment of the present disclosure is shown.

[0584] One method disclosed herein ( Figure 13 In this context, the operation for monitoring paging of at least one remote UE is as follows:

[0585] At steps S1310-A ​​and S1310-B, remote UEs 30 and 35 can send paging monitoring requests to relay UE 40.

[0586] For example, remote UEs 30 and 35 can send their 5G-S-TMSI to relay UE 40; for example, if the remote UE is in RRC_INACTIVE (refer to steps S1300-A and S1300-B), remote UEs 30 and 35 can send their I-RNTI. These parameters can be sent by remote UEs 30 and 35 to relay UE 40 via sidelink signaling radio bearer (SL SLRB) or via sidelink data radio bearer using RRC signaling messages. The signaling message carrying these parameters is sent in a MAC PDU, in which the Layer 2 identifier of the remote UE (or a portion thereof) and the Layer 2 identifier of the relay UE (or a portion thereof) are added to the header of the MAC PDU. The MAC PDU is then sent via PSSCH.

[0587] In one embodiment, the relay UE 40 may be in the RRC_CONNECTED state (see step S1305).

[0588] In one embodiment, the relay UE 40 may receive an RRCReconfiguration message that includes the DL BWP configuration.

[0589] At step S1315, the relay UE 40 may send a list of paging identifiers (i.e., the 5G-S-TMSI and I-RNTI of the remote UEs) received from the remote UEs 30 and 35 to the gNB 10. For example, if the relay UE 40 is connected to two remote UEs, namely remote UE1 and remote UE2, and the relay UE 40 receives 5G-S-TMSI-1 and I-RNTI-1 from remote UE1 and 5G-S-TMSI-2 and I-RNTI-2 from remote UE2, the relay UE 40 sends 5G-S-TMSI-1, I-RNTI-1, 5G-S-TMSI-2, and I-RNTI-2 to the gNB 10. In one embodiment, the gNB 10 may send two lists, one of which includes the 5G-S-TMSI and the second list includes the I-RNTI.

[0590] At step S1320-A, the relay UE 40 can check whether the active DL BWP is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration). The paging search space can also be referred to as "public search space and public coreset for paging" or "public search space for paging".

[0591] -If the active DL BWP of relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration):

[0592] a. Relay UE 40 does not monitor paging requests from remote UEs 30 and 35.

[0593] b. At step S1340, the relay UE 40 may receive a BWP handover command to switch to another BWP configured for paging search space.

[0594] -If the active DL BWP of relay UE 40 is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration):

[0595] a. In step S1350, the relay UE 40 can monitor the PO of the remote UE in order to receive the paging of the remote UE.

[0596] - If a 5G-S-TMSI is received from a remote UE, and that 5G-S-TMSI is included in the received paging message.

[0597] --The relay UE 40 can send a CN paging indication to the remote UE (using a MAC CE or a sidelink signaling message via a sidelink signaling radio bearer or SCI). The relay UE can send a 5G-S-TMSI to the remote UE.

[0598] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0599] - If an I-RNTI is received from a remote UE, and the I-RNTI is included in the received paging message.

[0600] --The relay UE 40 can send a RAN paging indication (using a MAC CE or a signaling message via a sidelink signaling radio bearer or SCI) to the remote UE. The relay UE can send an I-RNTI to the remote UE.

[0601] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0602] -gNB operation:

[0603] -If the active DL BWP of relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration),

[0604] a. If gNB 10 connected to relay UE 40 receives paging messages from remote UEs 30 and 35, i.e., if gNB 10 receives a paging message from CN or another GNB, wherein the paging message includes one or more paging identifiers included in the paging identifier list received from relay UE 40, or if gNB receives DL data from a remote UE in RRC_INACTIVE, whose paging identifier is received from the relay UE: in steps S1330 to S1340, gNB 10 may send a BWP handover command, i.e., DCI, instructing the UE to switch to another BWP configured for paging search space.

[0605] b. In steps S1360 to S1370, gNB 10 can then send the PDCCH of the PO addressed to P-RNTI and the corresponding paging message on the PDSCH of the new active DL BWP.

[0606] - If the active DL BWP of relay UE 40 is configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is signaled by gNB 10 in the DL BWP configuration): gNB transmits the PDCCH addressed to P-RNTI in PO and the corresponding TB / MAC PDU carrying the paging message on the PDSCH. In this case, the MAC sub-header is not included in the MAC PDU carrying the paging information MAC SDU.

[0607] In one embodiment, if the active DL BWP of the relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by the gNB in ​​the DL BWP configuration): the relay UE 40 autonomously switches to the initial DL BWP for PO monitoring of remote UE paging.

[0608] In one embodiment, if the active DL BWP of relay UE 40 is not configured for the paging search space (i.e., the parameter pagingSearchSpace (paging search space identifier) ​​is not signaled by gNB 10 in the DL BWP configuration): relay UE 40 can notify (using SCI, MAC CE, or RRC messages) the remote UE that it cannot detect paging. Upon receiving this information, the remote UE can select (reselect) another relay.

[0609] In one of the embodiments 3-1 to 3-3, when the relay UE 40 is transferred from one cell to another, the source cell / gNB forwards a list of paging identifiers received by the relay UE 40 to the target cell / gNB. Therefore, the relay UE 40 does not need to send the list to the target cell / gNB during the transfer.

[0610] We are currently researching a UE-to-network relay architecture, where the relay UE relays traffic between remote UEs and the network. UE-to-network relay achieves extended coverage and power savings for remote UEs. Communication between the UE-to-network relay and the gNB is based on 5G communication between the UE and the gNB. Communication between the remote UE and the UE-to-network relay UE is based on sidelink communication. The UE-to-network relay UE can relay paging and system information to the remote UE. For paging, the relay UE monitors not only its own paging timing but also the paging timing of the remote UE. The question is how the relay UE determines the paging timing of the remote UE and monitors the paging of the remote UE.

[0611] Example 4-1:

[0612] Figure 14 A diagram is shown illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure.

[0613] In one method of this disclosure ( Figure 14 Remote UE 30 can send the following parameters to relay UE 40 via a side link.

[0614] - 5G-S-TMSI for remote UE 30;

[0615] - I-RNTI of remote UE 30, if remote UE 30 is in RRC_INACTIVE

[0616] - The length (T1) of the DRX cycle configured by the upper layer (i.e., NAS) to the remote UE 30, if available / configured.

[0617] - Default DRX cycle length (T2)

[0618] - If remote UE 30 is in RRC_INACTIVE, the length of the DRX cycle (T3) is configured for remote UE 30 by the RAN. If the RAN does not provide / configure this parameter to remote UE 30, remote UE 30 will not send it to relay UE 40. When remote UE 30 is in RRC_CONNECTED, the RAN can use the RCRelease message to configure / signal it to the UE. When remote UE 30 is in RRC_INACTIVE, the RAN can use the RCRelease message to configure / signal it to the UE during small data transmission procedures / sessions.

[0619] - Paging subgroup information (e.g., a paging subgroup identifier, which may be received by the remote UE from the CN (i.e., AMF), or it may be determined by the remote UE based on the UE_ID), if available. The remote UE may indicate whether a paging subgroup has been received from the CN or whether the paging subgroup was determined by the remote UE based on its identifier. In one embodiment, this may be sent only if the cell in which the relay UE 40 is camped supports early paging indication and / or if the relay UE 40 supports early paging indication. Information that the cell in which the relay UE 40 is camped supports early paging indication can be obtained from a relay discovery message or from system information sent by the relay UE 40 to the remote UE 30. Information that the relay UE 40 supports early paging indication can be obtained from signaling messages sent by the relay UE 40 to the remote UE 30.

[0620] -If the remote UE 30 supports e-DRX

[0621] The e-DRX cycle length and the PTW length. If the PTW is configured separately for RRC_IDLE and RRC_INACTIVE, then two PTWs are included. Similarly, the e-DRX cycle length can be included separately for RRC_IDLE and RRC_INACTIVE.

[0622] - Indicates that the PO index (i_s) in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE. "If the remote UE supports using the same i_s in the PO determination in the RRC_INACTIVE state as in the RRC_IDLE state," and "the remote UE has received an indication in the RRCCRelease message to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination (or the remote UE has received an indication in the system information to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination)," the remote UE can send this indication. Alternatively, if the remote UE supports using the same i_s in the PO determination in the RRC_INACTIVE state as in the RRC_IDLE state, and if the remote UE has received an indication in the RRCCRelease message to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination (or the remote UE has received an indication in the system information to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination), the remote UE in the RRC_INACTIVE state can send this indication.

[0623] The aforementioned parameters can be transmitted from remote UE 30 to relay UE 10 via RRC signaling messages through a sidelink signaling radio bearer (SLSLRB) or via a sidelink data radio bearer. The signaling message carrying these parameters can be transmitted in a MAC PDU, where the Layer 2 identifier of the remote UE (or a portion thereof) and the Layer 2 identifier of the relay UE (or a portion thereof) are added to the header of the MAC PDU. The MAC PDU is then transmitted via PSSCH.

[0624] In the method disclosed herein, the paging operation of the relay UE to the remote UE is as follows:

[0625] At steps S1410 and S1415, the relay UE 40 can receive parameters N (number of paging frames), Ns (number of paging opportunities), PF_Offset (paging frame offset), and pagingSearchSpace (paging search space identifier) ​​from the gNB 10. It can also receive the parameter firstPDCCH-MonitoringOccasionOfPO (a list of first PDCCH monitoring opportunity numbers for each of the Ns POs) from the gNB 10. N, Ns, and PF_Offset are received from SIB1 sent by the gNB 10. N is one of a T, half a T, a quarter T, an eighth T, or a sixteenth T. In other words, N is in units of DRX cycle length. Its value can be equal to DRX cycle length, DRX cycle length / 2, DRX cycle length / 4, DRX cycle length / 8, and DRX cycle length / 16. pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO are received in the DL BWP configuration for paging monitoring by the relay UE 40. If relay UE 40 is in RRC_IDLE / RRC_INACTIVE, the DL BWP monitored by relay UE 40 for paging is the initial DL BWP. If relay UE 40 is in RRC_CONNECTED, the DL BWP monitored by relay UE 40 for paging is the active DL BWP. If relay UE 40 is in RRC_IDLE / RRC_CONNECTED, the initial DL BWP configuration will be received in SIB1 sent by gNB 10. If relay UE 40 is in RRC_CONNECTED, the DL BWP configuration is received by relay UE 40 in the RRC reconfiguration message.

[0626] At step S1405, the relay UE 40 can receive 5G-S-TMSI, I-RNTI (optional), T1 (optional), T2 and T3 (optional) from the remote UE 30 via a side link (using the mechanism explained above).

[0627] At step S1420, the relay UE 40 can determine the value of T. For example, the relay UE 40 can determine that T = minimum (T1, T2, T3), or if T3 is not received from the remote UE 30, then T = minimum (T2, T1), or if T1 is not received from the remote UE 30, then T = minimum (T2, T3), or if both T1 and T3 are not received from the remote UE 30, then T = T2.

[0628] At step S1425, the relay UE 40 can determine the value of U. For example, the relay UE 40 can determine that U = 5G-S-TMSI mod 1024 of the remote UE (or 5G-S-TMSI mod 2048 of the remote UE or 5G-S-TMSI mod 4096 of the remote UE).

[0629] At step S1430, the relay UE 40 can determine the value of PF. For example, the relay UE 40 can determine PF, where PF is SFN, given by (SFN+PF_Offset)Mod T=(T div N)*(U mod N). For N, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter T", N equals T / 4. If N received from the gNB is "one-eighth T", N equals T / 8. If N received from the gNB is "one-sixteenth T", N equals T / 16.

[0630] At step S1435, the relay UE 40 can determine the PO index. For example, the relay UE can determine the PO index as i_s = floor(U / N) mod Ns. For N used to determine i_s, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter a T", N equals T / 4. If N received from the gNB is "one-eighth a T", N equals T / 8. If N received from the gNB is "one-sixteenth a T", N equals T / 16.

[0631] If the PO index (i_s) received by the relay UE from the remote UE in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE, the DRX cycle length for determining i_s is set to Tx = min(T1, T2) or Tx = T2 (if T1 is not received from the remote UE). If the N received from the gNB is "one T", N equals Tx. If the N received from the gNB is "half a T", N equals Tx / 2. If the N received from the gNB is "one-quarter a T", N equals Tx / 4. If the N received from the gNB is "one-eighth a T", N equals Tx / 8. If the N received from the gNB is "one-sixteenth a T", N equals Tx / 16.

[0632] Alternatively, if the remote UE is in RRC_INACTIVE, and if the relay UE receives from the remote UE an indication that the PO index (i_s) in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE, then for N determining i_s, the DRX cycle length is set to Tx = min(T1, T2) or Tx = T2 (if T1 is not received from the remote UE). If N received from the gNB is "one T", N equals Tx. If N received from the gNB is "half a T", N equals Tx / 2. If N received from the gNB is "one-quarter a T", N equals Tx / 4. If N received from the gNB is "one-eighth a T", N equals Tx / 8. If N received from the gNB is "one-sixteenth a T", N equals Tx / 16.

[0633] At step S1440, the relay UE 40 can then use pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO (if received from gNB 10) to identify the PDCCH monitoring timing corresponding to the identified i_s PO.

[0634] - When SearchSpaceId is configured as 0 for pagingSearchSpace, the PDCCH monitoring timing for paging is the same as RMSI. When SearchSpaceId is configured as 0 for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO, which starts from the first PDCCH monitoring timing for paging in the PF. For Ns=2, the PO is in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0635] - When SearchSpaceId is configured to be non-zero for pagingSearchSpace, relay UE 40 monitors the (i_s+1)th PO. The PDCCH monitoring timing for paging is determined based on the paging search space configuration (paging-SearchSpace) signaled by gNB 10. The PDCCH monitoring timings for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon received in SI) are sequentially numbered from 0, starting from the first PDCCH monitoring timing for paging in the PF. gNB 10 can signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. When the firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PO is a set of "S*X" consecutive PDCCH monitoring opportunities for paging, starting from the PDCCH monitoring opportunity number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is a set of "S" consecutive PDCCH monitoring opportunities for paging, starting from the (i_s*S*X)th PDCCH monitoring opportunity for paging. "S" is the number of SSBs actually transmitted, determined by the parameter ssb-PositionsInBurst signaled from SystemInformationBlock1 received from the gNB. X is the number of PDCCH monitoring opportunities for each SSB and is signaled by the GNB. If X is not signaled, it is assumed to be equal to 1. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0636] At step S1445, the relay UE 40 can monitor the PDCCH addressed to the P-RNTI during the PDCCH monitoring time of the identified PO.

[0637] - If an I-RNTI is received from remote UE 30, then relay UE 40 monitors CN paging and RAN paging of remote UE 30.

[0638] If no I-RNTI is received from the remote UE 30, the relay UE 40 will only monitor the CN paging of the remote UE 30.

[0639] At step S1450, the relay UE 40 can receive the PDCCH addressed to the P-RNTI. Additionally, at step S1455, the relay UE 40 can receive a paging message. If a PDCCH addressed to the P-RNTI is received in the monitored PO, and the paging message's DCI includes the paging message's scheduling information (i.e., the short message indicator in the DCI is set to 01 or 11), the UE receives and decodes the TB based on the scheduling information and obtains the paging message from the decoded TB.

[0640] At step S1460, if an I-RNTI is received from the remote UE 30, and the I-RNTI is included in the received paging message...

[0641] - At step S1465, the relay UE 40 sends a RAN paging instruction to the remote UE 30 via the side link (using a MAC CE or a signaling message or SCI via the side link SRB).

[0642] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0643] At step S1470, if a 5G-S-TMSI is received from the remote UE 30 and the 5G-S-TMSI is included in the received paging message...

[0644] - At step S1475, the relay UE 40 sends a CN paging instruction to the remote UE 30 (using MAC CE or signaling messages or SCI via the side link SRB).

[0645] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0646] In one embodiment, the relay UE 40 may simply forward paging messages received from gNB 10 via a side link.

[0647] If the early paging indication is supported by relay UE 40, and the early paging indication is supported by the cell where relay UE 40 is camped (or by the PCell in the case of relay UE 40 being RRC_CONNECTED):

[0648] - The relay UE 40 can identify the early paging indication monitoring timing corresponding to the PO determined above, and monitor the early paging indication.

[0649] - If the early paging indication includes / indicates that the paging subgroup of the remote UE or the relay UE 40 fails to receive the early paging indication, then the relay UE 40 monitors the PO of the remote UE (as determined above).

[0650] - If the early paging indication does not include / indicates the paging subgroup of the remote UE, the relay UE 40 may not monitor the PO of the remote UE (as determined above).

[0651] - The relay UE 40 can receive the paging subgroup of the remote UE from the remote UE 30, or the relay UE 40 can identify the paging subgroup of the remote UE based on the remote UE's ID ("If no paging subgroup identifier is received from the remote UE, and the cell where the relay UE is currently camped supports paging subgroups based on UE ID" or "If the paging subgroup identifier received from the UE is assigned by the CN, and the cell where the relay UE is currently camped does not support paging subgroups based on CN but supports paging subgroups based on UE ID").

[0652] --The paging subgroup "k" of the remote UE is (U / (N*Ns))mod P, where P is the number of paging subgroups received by the relay UE from gNB 10.

[0653] When relay UE 40 receives e-DRX configuration from remote UE 30 and the cell where relay UE 40 is camped (or the PCell in the case of relay UE being RRC_CONNECTED) supports e-DRX,

[0654] - The relay UE 40 first identifies the PTW used for paging remote UEs.

[0655] --Determine the paging super high frame (PH). The PH is an H-SNF that satisfies the following equation:

[0656] ---H-SFN mod T eDRX,H =(UE_ID_H mod T) eDRX,H ),

[0657] ---T eDRX,H eDRX period for remote UEs, in units of ultra-high frames (T). eDRX,H =1, 2, ..., 256 ultra-high frame rate)

[0658] ---UE_ID_H: The 10 most significant bits of the hash ID

[0659] ---Hash_ID is the Frame Check Sequence (FCS) of bits b31, b30, ..., b0 of the 5G S-TMSI of the remote UE.

[0660] ---The 5G S-TMSI is 48 bits, including the AMF set ID (10 bits), the AMF pointer (6 bits), and the 5G TMSI (32 bits).

[0661] --Determine PTW_start. PTW_start represents the first radio frame of the PH, which is part of the PTW, and its SFN satisfies the following equation:

[0662] --SFN = 256 * ieDRX, where ieDRX = floor(UE_ID_H / TeDRX,H) mod 4

[0663] - The relay UE 40 then applies paging monitoring operations within the PTW, as explained above under "Paging Operations of Relay UE to Remote UE" (i.e., the SFN considered for PF determination is some within the PTW).

[0664] In alternative embodiments of this method:

[0665] - The remote UE 30 can notify the relay UE 40 of the new paging ID (instead of 5G-S-TMSI / I-RNTI).

[0666] --RRC IDLE and RRC INACTIVE can have separate new paging IDs.

[0667] --RRC IDLE and RRC_INACTIVE can both have the same new paging ID.

[0668] ---In this case, the remote UE can additionally indicate whether it wants to monitor RAN paging; or it can indicate its RRC status.

[0669] -U = UE_ID, meaning the 5G-S-TMSI mod 1024 of the remote UE is also notified to the relay UE 40 by the remote UE 30, and the relay UE 40 does not need to calculate it.

[0670] - The relay UE 40 will check the new paging ID in the paging information received from gNB 10, instead of the I-RNTI / 5G-S-TMSI of the remote UE 30.

[0671] --If the new paging ID is common to both RRC IDLE and RRC_INACTIVE and is included in the paging message, then the paging message from gNB 10 indicates whether the paging is a RAN paging / CN paging (or UE state).

[0672] -If a new paging ID is received from remote UE 30 and that paging ID is included in the received paging message.

[0673] --The relay UE 40 sends a paging indication to the remote UE 30 (using MAC CE, signaling message, or SCI). The relay UE 40 can also indicate whether the paging is RAN paging or CN paging.

[0674] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0675] In one embodiment, the method described herein is applied when the relay UE 40 is in RRC IDLE, RRC_INACTIVE, or RRC_CONNECTED, wherein the active DL BWP is configured for the paging Search Space (the pagingSearchSpace is signaled).

[0676] In one embodiment, when a remote UE 30, whose paging is relayed by relay UE 1, reselects another relay UE 2, the remote UE sends the parameters as described above to relay UE 2, and relay UE 2 will monitor the paging of remote UE 30 as described in this method. Upon reselection, remote UE 30 may notify relay UE 1 that it no longer needs to monitor paging for it, relay UE 1 releases the configuration / parameters received from remote UE 30 and stops monitoring paging for remote UE 30.

[0677] Example 4-2:

[0678] Figure 15 A diagram is shown illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure.

[0679] In one method of this disclosure ( Figure 15 Remote UE 30 can send the following parameters to relay UE 40 via a side link.

[0680] - 5G-S-TMSI for remote UE 30;

[0681] - I-RNTI of remote UE 30, if remote UE 30 is in RRC_INACTIVE

[0682] - The length (T1) of the DRX cycle configured by the upper layer (i.e., NAS) to the remote UE 30, if available / configured.

[0683] - If remote UE 30 is in RRC_INACTIVE, the length of the DRX cycle (T3) is configured for remote UE 30 by the RAN. If the RAN does not provide / configure this parameter to remote UE 30, remote UE 30 will not send it to relay UE 40. When remote UE 30 is in RRC_CONNECTED, the RAN can use the RCRelease message to configure / signal it to the UE. When remote UE 30 is in RRC_INACTIVE, the RAN can use the RCRelease message to configure / signal it to the UE during small data transmission procedures / sessions.

[0684] - Paging subgroup information (e.g., a paging subgroup identifier, which may be received by the remote UE from the CN (i.e., AMF), or it may be determined by the remote UE based on the UE_ID), if available. The remote UE may indicate whether a paging subgroup has been received from the CN or whether the paging subgroup was determined by the remote UE based on its identifier. In one embodiment, this may be sent only if the cell in which the relay UE 40 is camped supports early paging indication and / or if the relay UE 40 supports early paging indication. Information that the cell in which the relay UE 40 is camped supports early paging indication can be obtained from a relay discovery message or from system information sent by the relay UE 40 to the remote UE 30. Information that the relay UE 40 supports early paging indication can be obtained from signaling messages sent by the relay UE 40 to the remote UE 30.

[0685] -If the remote UE 30 supports e-DRX

[0686] The e-DRX cycle length and the PTW length. If the PTW is configured separately for RRC_IDLE and RRC_INACTIVE, then two PTWs are included. Similarly, the e-DRX cycle length can be separately included for RRC_IDLE and RRC_INACTIVE. - Indicates that the PO index (i_s) in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE. "If the remote UE supports using the same i_s in the PO determination in the RRC_INACTIVE state as in the RRC_IDLE state," and "the remote UE has received an indication in the RRCCRelease message to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination (or the remote UE has received an indication in the system information to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination)," the remote UE can send this indication. Alternatively, if the remote UE supports using the same i_s in the PO determination in the RRC_INACTIVE state as in the RRC_IDLE state, and if the remote UE has received an indication in the RRCCRelease message to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination (or the remote UE has received an indication in the system information to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination), the remote UE in the RRC_INACTIVE state can send this indication.

[0687] The aforementioned parameters can be transmitted from the remote UE 30 to the relay UE 40 via a sidelink signaling radio bearer (SLSLRB) or a sidelink data radio bearer using RRC signaling messages. The signaling message carrying these parameters is transmitted in a MAC PDU, in which the Layer 2 identifier of the remote UE (or a portion thereof) and the Layer 2 identifier of the relay UE (or a portion thereof) are added to the header of the MAC PDU. The MAC PDU is then transmitted via PSSCH.

[0688] In the method disclosed herein, the paging operation of the relay UE to the remote UE is as follows:

[0689] At steps S1510 and S1515, the relay UE 40 can receive parameters N (number of paging frames), Ns (number of paging opportunities), T2 (default DRX cycle), PF_Offset (paging frame offset), and pagingSearchSpace (paging search space identifier) ​​from gNB 10. It can also receive the parameter firstPDCCH-MonitoringOccasionOfPO (a list of first PDCCH monitoring opportunity numbers for each of the Ns POs) from gNB 10. N, Ns, and PF_Offset are received from SIB1 sent by gNB 10. N is one of a T, half a T, a quarter T, an eighth T, or a sixteenth T. In other words, N is in units of DRX cycle length. Its value can be equal to DRX cycle length, DRX cycle length / 2, DRX cycle length / 4, DRX cycle length / 8, and DRX cycle length / 16. The pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO are received in the DL BWP configuration for paging monitoring by relay UE 40. If relay UE 40 is in RRC_IDLE / RRC_INACTIVE, the DL BWP for paging monitoring by relay UE 40 is the initial DL BWP. If relay UE 40 is in RRC_CONNECTED, the DL BWP for paging monitoring by relay UE 40 is the active DL BWP. If relay UE 40 is in RRC_IDLE / RRC_CONNECTED, the initial DL BWP configuration is received in SIB1 sent by gNB 10. If relay UE 40 is in RRC_CONNECTED, the DL BWP configuration is received by relay UE 40 in the RRC reconfiguration message.

[0690] At step S1505, the relay UE 40 can receive 5G-S-TMSI, I-RNTI (optional), T1 (optional), and T3 (optional) from the remote UE 30 via a side link (using the mechanism explained above).

[0691] At step S1520, the relay UE 40 can determine the value of T. For example, the relay UE 40 can determine that T = minimum (T1, T2, T3), or if T3 is not received from the remote UE 30, then T = minimum (T2, T1), or if T1 is not received from the remote UE 30, then T = minimum (T2, T3), or if both T1 and T3 are not received from the remote UE 30, then T = T2.

[0692] At step S1525, the relay UE 40 can determine the value of U. For example, the relay UE 40 can determine U = 5G-S-TMSI mod 1024 of the remote UE 30 (or 5G-S-TMSI mod 2048 or 5G-S-TMSI mod 4096 of the remote UE).

[0693] At step S1530, the relay UE 40 can determine the value of PF. For example, the relay UE 40 can determine PF, where PF is SFN, given by (SFN+PF_Offset)Mod T=(T div N)*(U mod N). For N used to determine PF, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter T", N equals T / 4. If N received from the gNB is "one-eighth T", N equals T / 8. If N received from the gNB is "one-sixteenth T", N equals T / 16.

[0694] At step S1535, the relay UE 40 can determine the PO index. For example, the relay UE 40 can determine the PO index i_s = floor(U / N) mod Ns. For N used to determine i_s, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter a T", N equals T / 4. If N received from the gNB is "one-eighth a T", N equals T / 8. If N received from the gNB is "one-sixteenth a T", N equals T / 16.

[0695] If the PO index (i_s) received by the relay UE from the remote UE in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE, the DRX cycle length for determining i_s is set to Tx = min(T1, T2) or Tx = T2 (if T1 is not received from the remote UE). If the N received from the gNB is "one T", N equals Tx. If the N received from the gNB is "half a T", N equals Tx / 2. If the N received from the gNB is "one-quarter a T", N equals Tx / 4. If the N received from the gNB is "one-eighth a T", N equals Tx / 8. If the N received from the gNB is "one-sixteenth a T", N equals Tx / 16.

[0696] Alternatively, if the remote UE is in RRC_INACTIVE, and if the relay UE receives from the remote UE an indication that the PO index (i_s) in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE, then for N determining i_s, the DRX cycle length is set to Tx = min(T1, T2) or Tx = T2 (if T1 is not received from the remote UE). If N received from the gNB is "one T", N equals Tx. If N received from the gNB is "half a T", N equals Tx / 2. If N received from the gNB is "one-quarter a T", N equals Tx / 4. If N received from the gNB is "one-eighth a T", N equals Tx / 8. If N received from the gNB is "one-sixteenth a T", N equals Tx / 16.

[0697] At step S1540, the relay UE 40 can then use pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO (if received from gNB 10) to identify the PDCCH monitoring timing corresponding to the identified i_s PO.

[0698] - When SearchSpaceId is configured as 0 for pagingSearchSpace, the monitoring timing of the PDCCH used for paging is the same as that of RMSI. When SearchSpaceId is configured as 0 for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO, which starts from the first PDCCH monitoring timing used for paging in the PF. For Ns=2, the PO is in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0699] - When SearchSpaceId is configured to be non-zero for pagingSearchSpace, relay UE 40 monitors the (i_s+1)th PO. The PDCCH monitoring timing for paging is determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. The PDCCH monitoring timings for paging that do not overlap with the UL symbols (determined according to the tdd-UL-DL-ConfigurationCommon received in the SI) are sequentially numbered from 0, starting from the first PDCCH monitoring timing for paging in the PF. gNB 10 can signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. When the firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PO is a set of "S*X" consecutive PDCCH monitoring opportunities for paging, starting from the PDCCH monitoring opportunity number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is a set of "S" consecutive PDCCH monitoring opportunities for paging, starting from the (i_s*S*X)th PDCCH monitoring opportunity for paging. "S" is the number of SSBs actually transmitted, determined by the parameter ssb-PositionsInBurst signaled from SystemInformationBlock1 received from gNB 10. X is the number of PDCCH monitoring opportunities for each SSB and is signaled by gNB 10. If X is not signaled, it is assumed to be equal to 1. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0700] At step S1545, the relay UE 40 can monitor the PDCCH addressed to the P-RNTI during the PDCCH monitoring time of the identified PO.

[0701] - If an I-RNTI is received from remote UE 30, then relay UE 40 monitors CN paging and RAN paging of remote UE 30.

[0702] - If no I-RNTI is received from the remote UE, the relay UE will only monitor the CN paging of the remote UE.

[0703] At step S1550, the relay UE 40 can receive the PDCCH addressed to the P-RNTI. Additionally, at step S1555, the relay UE 40 can receive a paging message. If a PDCCH addressed to the P-RNTI is received in the monitored PO, and the paging message's DCI includes the paging message's scheduling information (i.e., the short message indicator in the DCI is set to 01 or 11), the UE receives and decodes the TB based on the scheduling information and obtains the paging message from the decoded TB.

[0704] At step S1560, if an I-RNTI is received from the remote UE 30, and the I-RNTI is included in the received paging message...

[0705] - At step S1565, the relay UE 40 sends a RAN paging instruction to the remote UE 30 via the side link (using a MAC CE or a signaling message or SCI via the side link SRB).

[0706] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0707] At step S1570, if a 5G-S-TMSI is received from the remote UE 30 and the 5G-S-TMSI is included in the received paging message...

[0708] - At step S1575, the relay UE 40 sends a CN paging instruction to the remote UE 30 (using MAC CE or signaling messages or SCI via the side link SRB).

[0709] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0710] In one embodiment, the relay UE 40 may simply forward paging messages received from gNB 10 via a side link.

[0711] If the early paging indication is supported by relay UE 40, and the early paging indication is supported by the cell where relay UE 40 is camped (or the PCell in the case of relay UE 40 being RRC_CONNECTED).

[0712] - The relay UE 40 can identify the early paging indication monitoring timing corresponding to the PO determined above, and monitor the early paging indication.

[0713] - If the early paging indication includes / indicates that the paging subgroup of the remote UE or the relay UE fails to receive the early paging indication, then the relay UE 40 monitors the PO of the remote UE (as determined above).

[0714] - If the early paging indication does not include / indicates the paging subgroup of the remote UE, the relay UE 40 may not monitor the PO of the remote UE (as determined above).

[0715] - The relay UE 40 can identify the paging subgroup of a remote UE based on the remote UE ID.

[0716] - The relay UE can receive the paging subgroup of the remote UE from the remote UE, or the relay UE can identify the paging subgroup of the remote UE based on the remote UE's ID ("If no paging subgroup identifier is received from the remote UE, and the cell where the relay UE is currently camped supports paging subgroups based on UE ID" or "If the paging subgroup identifier received from the UE is assigned by the CN, and the cell where the relay UE is currently camped does not support paging subgroups based on CN but supports paging subgroups based on UE ID").

[0717] --The paging subgroup "k" of the remote UE is (U / (N*Ns))mod P, where P is the number of paging subgroups received by the relay UE 40 from the gNB 10.

[0718] When relay UE 40 receives e-DRX configuration from remote UE 30 and the cell where relay UE 40 is camped (or the PCell in the case of relay UE being RRC_CONNECTED) supports e-DRX,

[0719] - The relay UE 40 first identifies the PTW used for paging remote UEs.

[0720] --Determine the paging super high frame (PH). The PH is an H-SNF that satisfies the following equation:

[0721] ---H-SFN mod T eDRX,H =(UE_ID_H mod T) eDRX,H ),

[0722] ---T eDRX,H eDRX period for remote UEs, in units of ultra-high frames (T). eDRX,H =1, 2, ..., 256 ultra-high frame rate)

[0723] ---UE_ID_H: The 10 most significant bits of the hash ID

[0724] ---Hash_ID is the Frame Check Sequence (FCS) of bits b31, b30, ..., b0 of the 5G S-TMSI of the remote UE.

[0725] The 5G-S-TMSI is 48 bits, including the AMF set ID (10 bits), the AMF pointer (6 bits), and the 5G TMSI (32 bits).

[0726] --Determine PTW_start. PTW_start represents the first radio frame of the PH, which is part of the PTW, and its SFN satisfies the following equation:

[0727] --SFN = 256 * ieDRX, where ieDRX = floor(UE_ID_H / TeDRX,H) mod 4

[0728] - The relay UE 40 then applies paging monitoring operations within the PTW, as explained above under "Paging Operations of Relay UE to Remote UE" (i.e., the SFN considered for PF determination is some within the PTW).

[0729] In alternative embodiments of this method:

[0730] - The remote UE 30 can notify the relay UE 40 of the new paging ID (instead of 5G-S-TMSI / I-RNTI).

[0731] --RRC IDLE and RRC INACTIVE can have separate new paging IDs.

[0732] --RRC IDLE and RRC_INACTIVE can have the same new paging ID.

[0733] ---In this case, the remote UE 30 can additionally indicate whether it wants to monitor RAN paging; or it can indicate its RRC status.

[0734] -U = UE_ID, that is, the 5G-S-TMSI mod 1024 of the remote UE is also notified to the relay UE 40 by the remote UE 30, and the relay UE 40 does not need to calculate it.

[0735] - The relay UE 40 will check the new paging ID in the paging information received from gNB 10, instead of the I-RNTI / 5G-S-TMSI of the remote UE 30.

[0736] --If the new paging ID is common to both RRC IDLE and RRC_INACTIVE and is included in the paging message, then the paging message from the gNB indicates whether the paging is a RAN paging / CN paging (or UE state).

[0737] -If a new paging ID is received from remote UE 30 and that paging ID is included in the received paging message.

[0738] --The relay UE 40 sends a paging indication to the remote UE 30 (using MAC CE, signaling message, or SCI). The relay UE 40 can also indicate whether the paging is RAN paging or CN paging.

[0739] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE.

[0740] In one embodiment, the method described herein is applied when the relay UE 40 is in RRC IDLE, RRC_INACTIVE, or RRC_CONNECTED, wherein the active DL BWP is configured for the paging Search Space (the pagingSearchSpace is signaled).

[0741] In one embodiment, when a remote UE 30, whose paging is relayed by relay UE 1, reselects another relay UE 2, the remote UE sends the parameters as described above to relay UE 2, and relay UE 2 will monitor the paging of remote UE 30 as described in this method. Upon reselection, the remote UE may notify relay UE 1 that it no longer needs to monitor paging for it, and relay UE 1 releases the configuration / parameters received from remote UE 30 and stops monitoring paging for remote UE 30.

[0742] Example 4-3:

[0743] Figure 16 A diagram is shown illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure.

[0744] In one method of this disclosure ( Figure 16 Remote UE 30 can send the following parameters to relay UE 40 via a side link.

[0745] - 5G-S-TMSI for remote UE 30;

[0746] - I-RNTI of remote UE 30, if remote UE 30 is in RRC_INACTIVE

[0747] - The length of the DRX period (T), where

[0748] aT = Min(T1, T2, T3) or

[0749] bT = Min(T2, T1), if T3 is unavailable

[0750] cT = Min(T2, T3), if T1 is unavailable

[0751] dT = T2, if neither T1 nor T3 is available.

[0752] T1 = The length of the DRX cycle configured from the upper layer (i.e., NAS) to the remote UE 30;

[0753] T2 = Length of the default DRX cycle

[0754] T3 = The length of the DRX period configured by the RAN to the remote UE 30. When the remote UE 30 is in RRC_CONNECTED, the RAN can use the RRCLease message to send its configuration / use signal to the remote UE 30. When the remote UE 30 is in RRC_INACTIVE, the RAN can use the RRCLease message to send its configuration / use signal to the UE during a small data transmission process / session.

[0755] e. In one embodiment, T = the minimum of T1 or T3 or (T1, T3).

[0756] - Paging subgroup information (e.g., a paging subgroup identifier, which may be received by the remote UE from the CN (i.e., AMF), or it may be determined by the remote UE based on the UE_ID), if available. The remote UE may indicate whether a paging subgroup has been received from the CN or whether the paging subgroup was determined by the remote UE based on its identifier. In one embodiment, this may be sent only if the cell in which the relay UE 40 is camped supports early paging indication and / or if the relay UE 40 supports early paging indication. Information that the cell in which the relay UE 40 is camped supports early paging indication can be obtained from a relay discovery message or from system information sent by the relay UE 40 to the remote UE 30. Information that the relay UE 40 supports early paging indication can be obtained from signaling messages sent by the relay UE 40 to the remote UE 30.

[0757] -If the remote UE 30 supports e-DRX

[0758] The e-DRX cycle length and the PTW length. If the PTW is configured separately for RRC_IDLE and RRC_INACTIVE, then two PTWs are included. Similarly, the e-DRX cycle length can be separately included for RRC_IDLE and RRC_INACTIVE. - Indicates that the PO index (i_s) in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE. "If the remote UE supports using the same i_s in the PO determination in the RRC_INACTIVE state as in the RRC_IDLE state," and "the remote UE has received an indication in the RRCCRelease message to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination (or the remote UE has received an indication in the system information to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination)," the remote UE can send this indication. Alternatively, if the remote UE supports using the same i_s in the PO determination in the RRC_INACTIVE state as in the RRC_IDLE state, and if the remote UE has received an indication in the RRCCRelease message to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination (or the remote UE has received an indication in the system information to enable the use of the same i_s in both RRC_INACTIVE and RRC_IDLE in the PO determination), the remote UE in the RRC_INACTIVE state can send this indication.

[0759] The aforementioned parameters can be transmitted from the remote UE 30 to the relay UE 40 via a sidelink signaling radio bearer (SLSLRB) or a sidelink data radio bearer using RRC signaling messages. The signaling message carrying these parameters is transmitted in a MAC PDU, in which the Layer 2 identifier of the remote UE (or a portion thereof) and the Layer 2 identifier of the relay UE (or a portion thereof) are added to the header of the MAC PDU. The MAC PDU is then transmitted via PSSCH.

[0760] In the method disclosed herein, the paging operation of the relay UE to the remote UE is as follows:

[0761] At step S1605, the remote UE 30 can determine the value of T as described above.

[0762] At steps S1615 and S1620, the relay UE 40 can receive parameters N (number of paging frames), Ns (number of paging opportunities), T2 (default DRX period), PF_Offset (paging frame offset), and pagingSearchSpace (paging search space identifier) ​​from the gNB 10. It can also receive the parameter firstPDCCH-MonitoringOccasionOfPO (a list of first PDCCH monitoring opportunity numbers for each of the Ns POs) from the gNB 10. N, Ns, and PF_Offset are received from SIB1 sent by the gNB. N is one of a T, half a T, a quarter T, an eighth T, or a sixteenth T. In other words, N is in units of DRX period length. Its value can be equal to the DRX period length, DRX period length / 2, DRX period length / 4, DRX period length / 8, and DRX period length / 16. pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO are received in the DL BWP configuration for paging monitoring by the relay UE 40. If relay UE 40 is in RRC_IDLE / RRC_INACTIVE, the DL BWP monitored by relay UE 40 for paging is the initial DL BWP. If relay UE 40 is in RRC_CONNECTED, the DL BWP monitored by relay UE 40 for paging is the active DL BWP. If relay UE 40 is in RRC_IDLE / RRC_CONNECTED, the initial DL BWP configuration will be received in SIB1 sent by gNB 10. If relay UE 40 is in RRC_CONNECTED, the DL BWP configuration is received by relay UE 40 in the RRC reconfiguration message.

[0763] At step S1610, the relay UE 40 can receive 5G-S-TMSI, I-RNTI (optional), and T from the remote UE 30 via a side link (using the mechanism explained above).

[0764] At step S1625, the relay UE 40 can determine the value of U. For example, the relay UE 40 can determine U = 5G-S-TMSI mod 1024 of the remote UE (or 5G-S-TMSI mod 2048 of the remote UE or 5G-S-TMSI mod 4096 of the remote UE).

[0765] At step S1630, the relay UE 40 can determine the value of PF. For example, the relay UE 40 can determine PF, where PF is SFN, given by (SFN+PF_Offset)Mod T=(T div N)*(U mod N). For N used to determine PF, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter T", N equals T / 4. If N received from the gNB is "one-eighth T", N equals T / 8. If N received from the gNB is "one-sixteenth T", N equals T / 16.

[0766] At step S1635, the relay UE 40 can determine the PO index. For example, the relay UE can determine the PO index as i_s = floor(U / N) mod Ns. For N used to determine i_s, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter a T", N equals T / 4. If N received from the gNB is "one-eighth a T", N equals T / 8. If N received from the gNB is "one-sixteenth a T", N equals T / 16. If the PO index (i_s) received by the relay UE from the remote UE in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE, for N that determines i_s, the DRX cycle length is set to Tx = min(the length of the DRX cycle configured for the remote UE by the upper layer (i.e., NAS), the default DRX cycle received from the gNB in ​​the system information), or if no length of the DRX cycle configured for the remote UE by the upper layer (i.e., NAS) is received from the remote UE, then Tx = the default DRX cycle received from the gNB in ​​the system information. If N received from the gNB is "one T", N equals Tx. If N received from the gNB is "half a T", N equals Tx / 2. If N received from the gNB is "one-quarter a T", N equals Tx / 4. If N received from the gNB is "one-eighth a T", N equals Tx / 8. If N received from the gNB is "one-sixteenth a T", N equals Tx / 16.

[0767] Alternatively, if the remote UE is in RRC_INACTIVE, and if the relay UE receives from the remote UE an indication that the PO index (i_s) in RRC_INACTIVE is the same as the PO index i_s used for RRC_IDLE, for N determining i_s, the DRX cycle length is set to Tx = min(the length of the DRX cycle configured for the remote UE by the upper layer (i.e., NAS), the default DRX cycle received from the gNB in ​​the system information), or if no length of the DRX cycle configured for the remote UE by the upper layer (i.e., NAS) is received from the remote UE, then Tx = the default DRX cycle received from the gNB in ​​the system information. If N received from the gNB is "one T", N equals Tx. If N received from the gNB is "half a T", N equals Tx / 2. If N received from the gNB is "one-quarter a T", N equals Tx / 4. If N received from the gNB is "one-eighth a T", N equals Tx / 8. If the N received from gNB is "one-sixteenth of T", then N equals Tx / 16.

[0768] At step S1640, the relay UE 40 can then use pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO (if received from gNB 10) to identify the PDCCH monitoring timing corresponding to the identified i_s PO.

[0769] - When SearchSpaceId is configured as 0 for pagingSearchSpace, the monitoring timing of the PDCCH used for paging is the same as that of RMSI. When SearchSpaceId is configured as 0 for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO, which starts from the first PDCCH monitoring timing used for paging in the PF. For Ns=2, the PO is in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0770] - When SearchSpaceId is configured to be non-zero for pagingSearchSpace, the UE monitors the (i_s+1)th PO. The PDCCH monitoring timing for paging is determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. The PDCCH monitoring timings for paging that do not overlap with UL symbols (determined according to the tdd-UL-DL-ConfigurationCommon received in the SI) are sequentially numbered from 0, starting from the first PDCCH monitoring timing for paging in the PF. The gNB can signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. When the firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PO is a set of "S*X" consecutive PDCCH monitoring opportunities for paging, starting from the PDCCH monitoring opportunity number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is a set of "S" consecutive PDCCH monitoring opportunities for paging, starting from the (i_s*S*X)th PDCCH monitoring opportunity for paging. "S" is the number of SSBs actually transmitted, determined by the parameter ssb-PositionsInBurst signaled from SystemInformationBlock1 received from the gNB. X is the number of PDCCH monitoring opportunities for each SSB and is signaled by the GNB. If X is not signaled, it is assumed to be equal to 1. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0771] At step S1645, the relay UE 40 can monitor the PDCCH addressed to the P-RNTI during the PDCCH monitoring time of the identified PO.

[0772] - If an I-RNTI is received from remote UE 30, then relay UE 40 monitors CN paging and RAN paging of remote UE 30.

[0773] If no I-RNTI is received from the remote UE 30, the relay UE 40 will only monitor the CN paging of the remote UE 30.

[0774] At step S1650, the relay UE 40 can receive the PDCCH addressed to the P-RNTI. Additionally, at step S1655, the relay UE 40 can receive a paging message. If a PDCCH addressed to the P-RNTI is received in the monitored PO, and the paging message's DCI includes the paging message's scheduling information (i.e., the short message indicator in the DCI is set to 01 or 11), the UE receives and decodes the TB based on the scheduling information and obtains the paging message from the decoded TB.

[0775] At step S1660, if an I-RNTI is received from the remote UE 30, and the I-RNTI is included in the received paging message.

[0776] - At step S1665, the relay UE 40 sends a RAN paging instruction to the remote UE 30 via the side link (using a MAC CE or a signaling message or SCI via the side link SRB).

[0777] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0778] At step S1670, if a 5G-S-TMSI is received from the remote UE and the 5G-S-TMSI is included in the received paging message.

[0779] - At step S1675, the relay UE 40 sends a CN paging instruction to the remote UE 30 (using a MAC CE or a signaling message via the sidelink SRB or SCI).

[0780] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0781] In one embodiment, the relay UE 40 may simply forward paging messages received from gNB 10 via a side link.

[0782] If the early paging indication is supported by relay UE 40, and the early paging indication is supported by the cell where relay UE 40 is camped (or the PCell in the case of relay UE 40 being RRC_CONNECTED).

[0783] - The relay UE 40 can identify the early paging indication monitoring timing corresponding to the PO determined above, and monitor the early paging indication.

[0784] - If the early paging indication includes / indicates that the paging subgroup of the remote UE or the relay UE 40 fails to receive the early paging indication, then the relay UE 40 monitors the PO of the remote UE (as determined above).

[0785] - If the early paging indication does not include / indicates the paging subgroup of the remote UE, the relay UE 40 may not monitor the PO of the remote UE (as determined above).

[0786] - The relay UE 40 can identify the paging subgroup of a remote UE based on the remote UE ID.

[0787] - The relay UE 40 can receive the paging subgroup of the remote UE from the remote UE 30, or the relay UE 40 can identify the paging subgroup of the remote UE based on the remote UE's ID ("If no paging subgroup identifier is received from the remote UE, and the cell where the relay UE is currently camped supports paging subgroups based on UE ID" or "If the paging subgroup identifier received from the UE is assigned by the CN, and the cell where the relay UE is currently camped does not support paging subgroups based on CN but supports paging subgroups based on UE ID").

[0788] --The paging subgroup "k" of the remote UE is (U / (N*Ns))mod P, where P is the number of paging subgroups received by the relay UE 40 from the gNB 10.

[0789] When relay UE 40 receives e-DRX configuration from remote UE 30 and the cell where relay UE 40 is camped (or the PCell in which relay UE 40 is RRC_CONNECTED) supports e-DRX,

[0790] - The relay UE 40 first identifies the PTW used for paging remote UEs.

[0791] --Determine the paging super high frame (PH). The PH is an H-SNF that satisfies the following equation:

[0792] ---H-SFN mod T eDRX,H =(UE_ID_H mod T) eDRX,H ),

[0793] ---T eDRX,H eDRX period for remote UEs, in units of ultra-high frames (T). eDRX,H =1, 2, ..., 256 ultra-high frame rate)

[0794] ---UE_ID_H: The 10 most significant bits of the hash ID

[0795] ---Hash_ID is the Frame Check Sequence (FCS) of bits b31, b30, ..., b0 of the 5G S-TMSI of the remote UE.

[0796] The 5G-S-TMSI is 48 bits, including the AMF set ID (10 bits), the AMF pointer (6 bits), and the 5G TMSI (32 bits).

[0797] --Determine PTW_start. PTW_start represents the first radio frame of the PH, which is part of the PTW, and its SFN satisfies the following equation:

[0798] ---SFN = 256 * ieDRX, where ieDRX = floor(UE_ID_H / TeDRX,H) mod 4

[0799] - The relay UE 40 then applies paging monitoring operations within the PTW, as explained above under "Paging Operations of Relay UE to Remote UE" (i.e., the SFN considered for PF determination is some within the PTW).

[0800] In alternative embodiments of this method:

[0801] - The remote UE 30 can notify the relay UE 40 of the new paging ID (instead of 5G-S-TMSI / I-RNTI).

[0802] --RRC IDLE and RRC INACTIVE can have separate new paging IDs.

[0803] --RRC IDLE and RRC_INACTIVE can both have the same new paging ID.

[0804] ---In this case, the remote UE 30 can additionally indicate whether it wants to monitor RAN paging; or it can indicate its RRC status.

[0805] -U = UE_ID, meaning the 5G-S-TMSI mod 1024 of the remote UE is also notified to the relay UE 40 by the remote UE 30, and the relay UE 40 does not need to calculate it.

[0806] - Relay UE 40 will check the new paging ID in the paging information received from gNB 10, instead of the I-RNTI / 5G-S-TMSI of the remote UE 30.

[0807] --If the new paging ID is common to both RRC IDLE and RRC_INACTIVE and is included in the paging message, then the paging message from gNB 10 indicates whether the paging is a RAN paging / CN paging (or UE state).

[0808] - If a new paging ID is received from the remote UE 30 and that paging ID is included in the received paging message.

[0809] --The relay UE 40 sends a paging indication to the remote UE 30 (using MAC CE, signaling message, or SCI). The relay UE 40 can also indicate whether the paging is RAN paging or CN paging.

[0810] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0811] In one embodiment, the method described herein is applied when the relay UE 40 is in RRC IDLE, RRC_INACTIVE, or RRC_CONNECTED, wherein the active DL BWP is configured for the paging Search Space (the pagingSearchSpace is signaled).

[0812] In one embodiment, when a remote UE 30, whose paging is relayed by relay UE 1, reselects another relay UE 2, the remote UE 30 sends the parameters as described above to the relay UE 2, and the relay UE 2 will monitor the paging of the remote UE 30 as described in this method. Upon reselection, the remote UE 30 may notify the relay UE 1 that it no longer needs to monitor paging for it, and the relay UE 1 releases the configuration / parameters received from the remote UE 30 and stops monitoring the paging of the remote UE 30.

[0813] Example 4-4:

[0814] Figure 17 A diagram is shown illustrating a method for determining the paging timing of a remote UE and monitoring the paging of a remote UE according to an embodiment of the present disclosure.

[0815] In one method of this disclosure ( Figure 17 Remote UE 30 can send the following parameters to relay UE 40 via a side link.

[0816] - 5G-S-TMSI for remote UE 30;

[0817] - I-RNTI of remote UE 30, if remote UE 30 is in RRC_INACTIVE

[0818] - The length of the DRX period (T'), where

[0819] a.T' = Min(T1, T3) or

[0820] b.T' = T1, if T3 is unavailable

[0821] Do not send T' if neither T1 nor T3 is available.

[0822] T1 = The length of the DRX cycle configured from the upper layer (i.e., NAS) to the remote UE 30;

[0823] T3 = The length of the DRX period configured by the RAN to the remote UE 30. When the remote UE 30 is in RRC_CONNECTED, the RAN can use the RRCLease message to send its configuration / use signal to the remote UE 30. When the remote UE 30 is in RRC_INACTIVE, the RAN can use the RRCLease message to send its configuration / use signal to the UE during a small data transmission process / session.

[0824] - Paging subgroup information (e.g., a paging subgroup identifier, which may be received by the remote UE from the CN (i.e., AMF), or it may be determined by the remote UE based on the UE_ID), if available. The remote UE may indicate whether a paging subgroup has been received from the CN or whether the paging subgroup was determined by the remote UE based on its identifier. In one embodiment, this may be sent only if the cell in which the relay UE 40 is camped supports early paging indication and / or if the relay UE 40 supports early paging indication. Information that the cell in which the relay UE 40 is camped supports early paging indication can be obtained from a relay discovery message or from system information sent by the relay UE 40 to the remote UE 30. Information that the relay UE 40 supports early paging indication can be obtained from signaling messages sent by the relay UE 40 to the remote UE 30.

[0825] -If the remote UE 30 supports e-DRX

[0826] The e-DRX cycle length and the PTW length. If the PTW is configured separately for RRC_IDLE and RRC_INACTIVE, then two PTWs are included. Similarly, the e-DRX cycle length can be separately included for RRC_IDLE and RRC_INACTIVE.

[0827] The aforementioned parameters can be transmitted from the remote UE 30 to the relay UE 40 via a sidelink signaling radio bearer (SLSLRB) or a sidelink data radio bearer using RRC signaling messages. The signaling message carrying these parameters is transmitted in a MAC PDU, in which the Layer 2 identifier of the remote UE (or a portion thereof) and the Layer 2 identifier of the relay UE (or a portion thereof) are added to the header of the MAC PDU. The MAC PDU is then transmitted via PSSCH.

[0828] In the method disclosed herein, the paging operation of the relay UE to the remote UE is as follows:

[0829] At step S1705, the remote UE 30 can determine the value of T as described above.

[0830] At steps S1715 and S1720, the relay UE 40 can receive parameters N (number of paging frames), Ns (number of paging opportunities), T2 (default DRX cycle), PF_Offset (paging frame offset), and pagingSearchSpace (paging search space identifier) ​​from gNB 10. It can also receive the parameter firstPDCCH-MonitoringOccasionOfPO (a list of first PDCCH monitoring opportunity numbers for each of the Ns POs) from gNB 10. N, Ns, and PF_Offset are received from SIB1 sent by gNB 10. N is one of a T, half a T, a quarter T, an eighth T, or a sixteenth T. In other words, N is in units of DRX cycle length. Its value can be equal to DRX cycle length, DRX cycle length / 2, DRX cycle length / 4, DRX cycle length / 8, and DRX cycle length / 16. The pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO are received in the DL BWP configuration for paging monitoring by relay UE 40. If relay UE 40 is in RRC_IDLE / RRC_INACTIVE, the DL BWP for paging monitoring by relay UE 40 is the initial DL BWP. If relay UE 40 is in RRC_CONNECTED, the DL BWP for paging monitoring by relay UE 40 is the active DL BWP. If relay UE 40 is in RRC_IDLE / RRC_CONNECTED, the initial DL BWP configuration is received in SIB1 sent by gNB 10. If relay UE 40 is in RRC_CONNECTED, the DL BWP configuration is received by relay UE 40 in the RRC reconfiguration message.

[0831] At step S1710, the relay UE 40 can receive 5G-S-TMSI, I-RNTI (optional), and T from the remote UE 30 via a side link (using the mechanism explained above).

[0832] At step S1725, the relay UE 40 can determine the value of T. For example, the relay UE 40 can determine T = Min(T', T2), or if T' is not received from the remote UE 30, then T = T2.

[0833] At step S1730, the relay UE 40 can determine the value of U. For example, the relay UE 40 can determine U = 5G-S-TMSI mod 1024 of the remote UE (or 5G-S-TMSI mod 2048 of the remote UE or 5G-S-TMSI mod 4096 of the remote UE).

[0834] At step S1735, the relay UE 40 can determine the value of PF. For example, the relay UE 40 can determine PF, where PF is SFN, given by (SFN+PF_Offset)Mod T=(T div N)*(U mod N). For N used to determine PF, the DRX cycle length is set to T. If N received from the gNB is "one T", N equals T. If N received from the gNB is "half a T", N equals T / 2. If N received from the gNB is "one-quarter T", N equals T / 4. If N received from the gNB is "one-eighth T", N equals T / 8. If N received from the gNB is "one-sixteenth T", N equals T / 16.

[0835] At step S1740, the relay UE 40 can determine the PO index. For example, the relay UE 40 can determine the PO index as i_s = floor(U / N) mod Ns.

[0836] At step S1745, the relay UE 40 can then use pagingSearchSpace and firstPDCCH-MonitoringOccasionOfPO (if received from gNB 10) to identify the PDCCH monitoring timing corresponding to the identified i_s PO.

[0837] - When SearchSpaceId is configured as 0 for pagingSearchSpace, the PDCCH monitoring timing for paging is the same as RMSI. When SearchSpaceId is configured as 0 for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO, which starts from the first PDCCH monitoring timing for paging in the PF. For Ns=2, the PO is in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0838] - When SearchSpaceId is configured to be non-zero for pagingSearchSpace, the UE monitors the (i_s+1)th PO. The PDCCH monitoring timing for paging is determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. The PDCCH monitoring timings for paging that do not overlap with UL symbols (determined according to the tdd-UL-DL-ConfigurationCommon received in the SI) are sequentially numbered from 0, starting from the first PDCCH monitoring timing for paging in the PF. The gNB can signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. When the firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PO is a set of "S*X" consecutive PDCCH monitoring opportunities for paging, starting from the PDCCH monitoring opportunity number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is a set of "S" consecutive PDCCH monitoring opportunities for paging, starting from the (i_s*S*X)th PDCCH monitoring opportunity for paging. "S" is the number of SSBs actually transmitted, determined by the parameter ssb-PositionsInBurst signaled from SystemInformationBlock1 received from the gNB. X is the number of PDCCH monitoring opportunities for each SSB and is signaled by the GNB. If X is not signaled, it is assumed to be equal to 1. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0839] At step S1750, the relay UE 40 can monitor the PDCCH addressed to the P-RNTI during the PDCCH monitoring time of the identified PO.

[0840] - If an I-RNTI is received from remote UE 30, then relay UE 40 monitors CN paging and RAN paging of remote UE 30.

[0841] If no I-RNTI is received from the remote UE 30, the relay UE 40 will only monitor the CN paging of the remote UE 30.

[0842] At step S1755, the relay UE 40 can receive the PDCCH addressed to the P-RNTI. Additionally, at step S1760, the relay UE 40 can receive a paging message.

[0843] - If a PDCCH addressed to P-RNTI is received in the monitored PO, and the DCI of the paging message includes the scheduling information of the paging message (i.e., the short message indicator in the DCI is set to 01 or 11), the UE receives and decodes the TB based on the scheduling information and obtains the paging message from the decoded TB.

[0844] At step S1765, if an I-RNTI is received from the remote UE 30, and the I-RNTI is included in the received paging message.

[0845] - At step S1770, the relay UE 40 sends a RAN paging instruction (using MAC CE or signaling message or SCI) to the remote UE 30 via a side link.

[0846] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0847] At step S1775, if a 5G-S-TMSI is received from the remote UE 30 and the 5G-S-TMSI is included in the received paging message.

[0848] - At step S1780, the relay UE 40 sends a CN paging instruction to the remote UE 30 (using MAC CE or signaling message or SCI).

[0849] - The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0850] In one embodiment, the relay UE 40 may simply forward paging messages received from gNB 10 via a side link.

[0851] If the early paging indication is supported by relay UE 40, and the early paging indication is supported by the cell where relay UE 40 is camped (or the PCell in the case of relay UE 40 being RRC_CONNECTED).

[0852] - The relay UE 40 can identify the early paging indication monitoring timing corresponding to the PO determined above, and monitor the early paging indication.

[0853] - If the early paging indication includes / indicates that the paging subgroup of the remote UE or the relay UE 40 fails to receive the early paging indication, then the relay UE 40 monitors the PO of the remote UE (as determined above).

[0854] - If the early paging indication does not include / indicates the paging subgroup of the remote UE, the relay UE 40 may not monitor the PO of the remote UE (as determined above).

[0855] - The relay UE 40 can identify the paging subgroup of a remote UE based on the remote UE ID.

[0856] - The relay UE 40 can receive the paging subgroup of the remote UE from the remote UE 30, or the relay UE 40 can identify the paging subgroup of the remote UE based on the remote UE's ID ("If no paging subgroup identifier is received from the remote UE, and the cell where the relay UE is currently camped supports paging subgroups based on UE ID" or "If the paging subgroup identifier received from the UE is assigned by the CN, and the cell where the relay UE is currently camped does not support paging subgroups based on CN but supports paging subgroups based on UE ID").

[0857] --The paging subgroup "k" of the remote UE is (U / (N*Ns))mod P, where P is the number of paging subgroups received by the relay UE 40 from the gNB 10.

[0858] When relay UE 40 receives e-DRX configuration from remote UE 30 and the cell where relay UE 40 is camped (or the PCell in which relay UE 40 is RRC_CONNECTED) supports e-DRX,

[0859] - The relay UE 40 first identifies the PTW used for paging remote UEs.

[0860] --Determine the paging super high frame (PH). The PH is an H-SNF that satisfies the following equation:

[0861] ---H-SFN mod T eDRX,H =(UE_ID_H mod T) eDRX,H ),

[0862] ---T eDRX,H eDRX period for remote UEs, in units of ultra-high frames (T). eDRX,H =1, 2, ..., 256 ultra-high frame rate)

[0863] ---UE_ID_H: The 10 most significant bits of the hash ID

[0864] ---Hash_ID is the Frame Check Sequence (FCS) of bits b31, b30, ..., b0 of the 5G S-TMSI of the remote UE.

[0865] The 5G-S-TMSI is 48 bits, including the AMF set ID (10 bits), the AMF pointer (6 bits), and the 5G TMSI (32 bits).

[0866] --Determine PTW_start. PTW_start represents the first radio frame of the PH, which is part of the PTW, and its SFN satisfies the following equation:

[0867] ---SFN = 256 * ieDRX, where ieDRX = floor(UE_ID_H / TeDRX,H) mod 4

[0868] - The relay UE 40 then applies paging monitoring operations within the PTW, as explained above under "Paging Operations of Relay UE to Remote UE" (i.e., the SFN considered for PF determination is some within the PTW).

[0869] In alternative embodiments of this method:

[0870] - The remote UE 30 can notify the relay UE 40 of the new paging ID (instead of 5G-S-TMSI / I-RNTI).

[0871] --RRC IDLE and RRC INACTIVE can have separate new paging IDs.

[0872] --RRC IDLE and RRC_INACTIVE can have the same new paging ID.

[0873] ---In this case, the remote UE 30 can additionally indicate whether it wants to monitor RAN paging; or it can indicate its RRC status.

[0874] -U = UE_ID, meaning the 5G-S-TMSI mod 1024 of the remote UE is also notified to the relay UE 40 by the remote UE 30, and the relay UE 40 does not need to calculate it.

[0875] - The relay UE 40 will check the new paging ID in the paging information received from gNB 10, instead of the remote UE's I-RNTI / 5G-S-TMSI.

[0876] --If the new paging ID is common to both RRC IDLE and RRC_INACTIVE and is included in the paging message, then the paging message from the gNB indicates whether the paging is a RAN paging / CN paging (or UE state).

[0877] -If a new paging ID is received from remote UE 30 and that paging ID is included in the received paging message.

[0878] --The relay UE 40 sends a paging indication to the remote UE 30 (using MAC CE, signaling message, or SCI). The relay UE 40 can also indicate whether the paging is RAN paging or CN paging.

[0879] --The access type (non-3GPP) and / or paging reason received in the paging message can also be sent to the remote UE30.

[0880] In one embodiment, the method described herein is applied when the relay UE 40 is in RRC IDLE, RRC_INACTIVE, or RRC_CONNECTED, wherein the active DL BWP is configured for the paging Search Space (the pagingSearchSpace is signaled).

[0881] In one embodiment, when a remote UE 30, whose paging is relayed by relay UE 1, reselects another relay UE 2, the remote UE 30 sends the parameters as described above to the relay UE 2, and the relay UE 2 will monitor the paging of the remote UE 30 as described in this method. Upon reselection, the remote UE 30 may notify the relay UE 1 that it no longer needs to monitor paging for it, and the relay UE 1 releases the configuration / parameters received from the remote UE 30 and stops monitoring the paging of the remote UE 30.

[0882] In Examples 4-1 to 4-4, a new paging ID is used instead of 5G-S-TMSI / I-RNTI. The aspects of the new paging ID are as follows:

[0883] Option 1: CN assigns a new ID

[0884] --During registration or in RRC connection state (e.g., when the UE is connected via relay UE 40), the UE can request a new ID, and the network (i.e., AMF) can assign a new ID using NAS messages.

[0885] --For CN paging, the AMF can include this new ID of the remote UE 30 instead of the 5G-S-TMSI in the paging message sent to gNB 10. gNB 10 then includes this new ID in the paging message sent in the PDSCH.

[0886] --For RAN paging, the AMF can use the RAN Assist Information message to notify the RAN (i.e., gNB) of this new ID of the remote UE 30, and the ID can then be stored in the anchor gNB. The anchor gNB can include this new ID in the paging message sent to another gNB. The gNB 10 then includes the new ID in the paging message sent in the PDSCH.

[0887] Option 2: RAN can assign a new ID.

[0888] --When the remote UE 30 is in a connected state, it can notify the gNB that it is interested in relay operations, and the gNB can assign a new ID.

[0889] --When remote UE 30 is in Idle state:

[0890] When gNB 10 assigns an ID to remote UE 30 while in connected state, it notifies the AMF of the UE's new ID. The AMF stores the ID and links it to the 5G-S-TMSI. In the CN paging message, the AMF can include the remote UE's ID instead of the 5G-S-TMSI in the paging information sent to the gNB. The gNB then includes this ID in the paging message sent in the PDSCH.

[0891] --When remote UE 30 is in INACTIVE state:

[0892] ---For CN paging, the operation can be interpreted as being in the Idle state.

[0893] For RAN paging, the new ID can be stored in the anchor gNB. The anchor gNB can include the new ID in the paging message sent to another gNB. The gNB then includes the new ID in the paging message sent in the PDSCH.

[0894] Preamble and RACH resources are used for feature / feature combination:

[0895] Currently, the configuration of random access resources (RACH timing, preamble) for various feature / feature combinations is under discussion. The network can configure several RACH configurations, each corresponding to a feature / feature combination. This list of RACH configurations can be signaled by BWP or by cell in system information or RRCReconfiguration messages. "Redcap" refers to UEs with reduced capabilities, such as reducing the number of UE RX / TX antennas, reducing bandwidth, relaxing UE processing time, relaxing UE processing capacity, reducing the maximum DL MIMO layers, relaxing the maximum modulation order, and reducing duplex operation. A RACH configuration corresponding to redcap (where "Redcap indication" is set to "Yes" in the RACH configuration) means that the RACH configuration is for UEs with reduced capabilities, and the redcap UE uses it when initiating the random access procedure. "CE" refers to coverage extension. A RACH configuration corresponding to CE (where "CE indication" is set to "Yes" in the RACH configuration) means that it can be used by UEs with DL RSRP < threshold. A RACH configuration corresponding to SDT (where "SDT Indication" is set to "Yes" in the RACH configuration) means that it can be used by the UE when initiating random access for small data transmission. A RACH configuration corresponding to a slice refers to a RACH configuration associated with one or more slices, and it can be used by the UE if the slice of interest to the UE is included in that RACH configuration. Table 5 shows examples of various features / feature combinations, where each row indicates a RACH configuration and its associated features / feature combination. When a UE initiates a random access procedure, it can select the RACH configuration if the conditions corresponding to each feature associated with that RACH configuration are met. For example, if a RACH configuration is associated with redcap+SDT+slice+CE, and if the UE is a redcap UE, and the UE has initiated random access for SDT, and the UE's DL RSRP < a threshold, and the slice of interest to the UE is one of the slices associated with the RACH configuration, then the UE can select this RACH configuration.

[0896] Table 5

[0897] Features / Feature Combinations Redcap CE SDT slice 0 yes yes yes yes 1 yes yes yes no 2 yes yes no yes 3 yes yes no no 4 yes no yes yes 5 yes no yes no 6 yes no no yes 7 yes no no no 8 no yes yes yes 9 no yes yes no 10 no yes no yes 11 no yes no no 12 no no yes yes 13 no no yes no 14 no no no yes 15 no no no no

[0898] In the existing design, when a 2-step RA and the RO of the 2-step RA are shared with the RO of the 4-step RA, a predefined rule is introduced, and according to this rule, the preamble of each SSB of each valid RO of the 2-step RA is followed by the preamble of each SSB of each valid RO of the 4-step RA.

[0899] For random access resource (RACH timing, preamble) configurations of various feature / feature combinations, the RO can be shared across one or more RACH configurations corresponding to the features / feature combinations listed in Table 5. This means that the RO corresponding to a RACH configuration of a feature / feature combination can be shared with a conventional RO and / or the RO corresponding to a RACH configuration of another feature / feature combination. The RO of a 2-step RA configuration of a feature / feature combination can be shared with the RO of a 2-step RA configuration of another feature / feature combination, and / or it can be shared with the RO of a 4-step RA configuration of another feature / feature combination. Similarly, the RO of a 4-step RA configuration of a feature / feature combination can be shared with the RO of a 4-step RA configuration of another feature / feature combination, and / or it can be shared with the RO of a 2-step RA configuration of another feature / feature combination. Due to the existence of multiple feature / feature combinations and RO sharing options, a method based on predefined rules is not suitable. Therefore, in one embodiment of the invention, network signals are used to signal the start preamble index for each RACH configuration corresponding to a feature / feature combination.

[0900] The start preamble index is used to determine the preamble of a feature / feature combination, as follows:

[0901] -S is the start preamble index of the RACH configuration for a feature / feature combination. The RACH configuration is either a 2-step RACH configuration or a 4-step RACH configuration.

[0902] -X is a contention-based preamble for each SSB used for RACH configuration of feature / feature combinations.

[0903] -Y is the number of SSBs per RACH timing for the RACH configuration of feature / feature combination.

[0904] - If Y < 1, an SS / PBCH block is mapped to 1 / Y consecutive valid PRACH opportunities, and the X-based contention-based preamble with consecutive indices associated with the SS / PBCH block of each valid PRACH opportunity starts from the preamble index S.

[0905] - If Y≥1, then at each valid PRACH timing, the X-competition-based preamble with a continuous index associated with SS / PBCH block n (0≤n≤Y-1) is generated from the preamble index. In the beginning, among them It is the total number of RA preambles.

[0906] The start preamble index can be configured optionally. If not configured, the UE assumes the start preamble index is zero.

[0907] In the existing design, the PRACH configuration index (prach-ConfigurationIndex) in a 4-step RACH configuration indicates the RO (Redirect Access Point) of the 4-step RACH configuration. The PRACH configuration index in a 2-step RACH configuration indicates the RO in the 2-step RACH configuration. A predefined PRACH configuration table indicates the number of PRACH opportunities in a PRACH configuration cycle, the PRACH configuration cycle, and the position of the PRACH opportunity within the PRACH configuration cycle. The prach-ConfigurationIndex is the index of the entry in this PRACH configuration table. When the ROs of the 2-step RACH configuration and the ROs of the 4-step RACH configuration are shared, the PRACH configuration index is not signaled in the 2-step RACH configuration. In the case of shared ROs, msgA-SSB-SharedRO-MaskIndex is optionally signaled, indicating the subset of ROs shared by the 4-step type and the 2-step random access type for each SSB. In the case of shared ROs, if msgA-SSB-SharedRO-MaskIndex is not signaled, then all ROs are shared.

[0908] For random access resource (RACH timing, preambles) configurations of various feature / feature combinations, the network can configure several RACH configurations, each corresponding to a feature / feature combination in Table 5. When the ROs of the RACH configurations are shared, the UE needs to know the RACH configurations of the shared ROs so that the UE can determine the RO used for random access. The following options can be considered for this purpose:

[0909] Option 1: The PRACH configuration index (prach-ConfigurationIndex) is always signaled in the RACH configuration corresponding to the feature / feature combination. The SSB-SharedRO-MaskIndex is optionally signaled in the RACH configuration corresponding to the feature / feature combination, indicating that the subset of ROs indicated by the PRACH configuration index is available for that RACH configuration. If the SSB-SharedRO-MaskIndex is not signaled, all ROs indicated by the PRACH configuration index are available for that RACH configuration. The SSB-PerRACH-OccasionAndCB-PreamblesPerSSB is also always signaled in this RACH configuration, indicating the number of SSBs for each RO and the number of contention-based preambles for each SSB.

[0910] Figure 18 This is a diagram showing a list of RACH configurations according to embodiments of this disclosure.

[0911] Option 2: The prach-ConfigurationIndex is not always signaled in the RACH configuration corresponding to a feature / feature combination. It can be skipped if the RO of a RACH configuration is shared with another RACH configuration. The index of the RACH configuration sharing the RO can be included in the RACH configuration. For example, suppose there are six RACH configurations in the list. If the ROs of the 6th, 5th, and 3rd RACH configurations are shared, then the prach-ConfigurationIndex can be included in the 3rd RACH configuration, and the index (i.e., 2) of the 3rd RACH configuration in the list is included in the 5th and 6th RACH configurations, as shown below. Figure 18 As shown, each entry in the list configured by RACH is indexed sequentially starting from zero.

[0912] Figure 19 This is a diagram showing a list of RACH configurations according to embodiments of this disclosure.

[0913] Alternatively, the index for each RACH configuration can also be explicitly signaled by the network within the RACH configuration; for example, the network can assign the same identifier / index to RACH configurations sharing a RO, such as... Figure 19 As shown. It can also indicate whether RO is shared with the 2-step or 4-step RACH configuration.

[0914] In this option, the SSB-SharedRO-MaskIndex can also be signaled in the RACH configuration corresponding to the feature / feature combination, as in Option 1. The SSB-SharedRO-MaskIndex indicates a subset of shared ROs indicated by the prach-ConfigurationIndex, which is available for that RACH configuration. If the SSB-SharedRO-MaskIndex is not a signaled RACH configuration corresponding to the feature / feature combination, then all ROs indicated by the prach-ConfigurationIndex are available for that RACH configuration. It should be noted that if the prach-ConfigurationIndex is not signaled in the RACH configuration, the UE applies the prach-ConfigurationIndex of the RACH configuration indicated by the parameter index explained above.

[0915] In this option, SSB-PerRACH-OccasionAndCB-PreamblesPerSSB can be skipped, and CB-PreamblesPerSSB-PerSharedRO is included in some RACH configurations that share ROs with other RACH configurations. SSB-PerRACH-OccasionAndCB-PreamblesPerSSB and the PRACH configuration index are only included in one RACH configuration that shares ROs. It should be noted that if SSB-PerRACH-OccasionAndCB-PreamblesPerSSB is not signaled in the RACH configuration, the UE applies the number of SSBs for each RO of the RACH configuration indicated by the parameter index explained above.

[0916] Figure 20 This is a diagram showing a list of RACH configurations according to embodiments of this disclosure.

[0917] Option 3: The PRACH configuration index is not always signaled in the RACH configuration corresponding to a feature / feature combination. It can be skipped if the RO of a RACH configuration is shared with another RACH configuration. RACH configurations with shared ROs can be included one after another in the list of RACH configurations, and only the PRACH configuration index can be included for the first RACH configuration with shared ROs. This is in... Figure 20 As shown in the diagram. If a RACH configuration in the RACH configuration list has a prach-ConfigurationIndex, then all subsequent RACH configurations will not include a prach-ConfigurationIndex until another RACH configuration that does include a prach-ConfigurationIndex applies that prach-ConfigurationIndex. For example, in... Figure 20 In RACH configuration 2, the same prach-ConfigurationIndex and SSB are applied to each RO as in RACH configuration 1. RACH configurations 4 and 5 apply the same prach-ConfigurationIndex and SSB to each RO as in RACH configuration 4. If a prach-ConfigurationIndex is not included in the RACH configuration, the UE will apply the prach-ConfigurationIndex to the earliest RACH configuration in the list of RACH configurations signaled by the RACH configuration.

[0918] In this option, the SSB-SharedRO-MaskIndex can also be signaled in the RACH configuration corresponding to the feature / feature combination, as in Option 1. The SSB-SharedRO-MaskIndex indicates a subset of shared ROs indicated by the prach-ConfigurationIndex, which is available for that RACH configuration. If the SSB-SharedRO-MaskIndex is not a signaled RACH configuration corresponding to the feature / feature combination, then all ROs indicated by the prach-ConfigurationIndex are available for that RACH configuration. It should be noted that if the prach-ConfigurationIndex is not signaled in the RACH configuration, the UE applies the prach-ConfigurationIndex of another RACH configuration as explained above.

[0919] When initiating a random access procedure for a feature / feature combination, the UE selects the RACH configuration corresponding to the feature / feature combination from the list of RACH configurations. The UE determines the preamble corresponding to the selected RACH configuration (as mentioned earlier, the UE determines the preamble start index, the SSB of each RO, the CB preamble to be applied to each SSB of the selected RACH configuration, and then uses these parameters to determine the preamble), and the RO corresponding to the selected RACH configuration (as mentioned earlier, the UE determines the prach-ConfigurationIndex and SSB-SharedRO-MaskIndex to be applied to the selected RACH configuration (optional), and then uses these parameters to determine the RO). The UE selects the preamble and RO from the determined preamble, and selects the RO from the determined RO, and sends the selected preamble in the selected RO.

[0920] Figure 21 This is a diagram illustrating a UE 2100 according to an embodiment of the present disclosure.

[0921] refer to Figure 21 UE 2100 may include a processor 2110, a transceiver 2120, and a memory 2130. However, not all of the components shown are necessary. UE 2100 may be composed of components such as processor 2110, transceiver 2120, and memory 2130. Figure 21 The components shown can be implemented with more or fewer components. Alternatively, according to another embodiment, the processor 2110, transceiver 2120, and memory 2130 can be implemented as a single chip.

[0922] UE 2100 may correspond to at least one of UE 20, remote UE 30, 35 or relay UE 40.

[0923] The above-mentioned components will now be described in detail.

[0924] Processor 2110 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. Operation of UE 2100 may be performed by processor 2110.

[0925] Transceiver 2120 can be connected to processor 2110 and transmit and / or receive signals. Additionally, transceiver 2120 can receive signals via a wireless channel and output signals to processor 2110. Transceiver 2120 can also transmit signals output from processor 2110 via a wireless channel.

[0926] Memory 2130 may store control information or data included in the signals acquired by UE 2100. Memory 2130 may be connected to processor 2110 and store at least one instruction or protocol or parameter for the proposed function, process, and / or method. Memory 2130 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0927] Figure 22 This is a diagram illustrating a base station 2200 according to an embodiment of the present disclosure.

[0928] refer to Figure 22 The base station 2200 may include a processor 2210, a transceiver 2220, and a memory 2230. However, not all of the components shown are necessary. The base station 2200 can be made of a processor 2210, a transceiver 2220, and a memory 2230. Figure 22 The components shown can be implemented with more or fewer components. Alternatively, according to another embodiment, the processor 2210, transceiver 2220, and memory 2230 can be implemented as a single chip.

[0929] The above-mentioned components will now be described in detail.

[0930] Processor 2210 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of base station 2200 may be performed by processor 2210.

[0931] Transceiver 2220 can be connected to processor 2210 and transmit and / or receive signals. Additionally, transceiver 2220 can receive signals via a wireless channel and output signals to processor 2210. Transceiver 2220 can also transmit signals output from processor 2210 via a wireless channel.

[0932] The memory 2230 may store control information or data included in the signals acquired by the base station 2200. The memory 2230 may be connected to the processor 2210 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 2230 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0933] The methods described in the claims of this disclosure or the various embodiments of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0934] When implemented in software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs may include instructions that cause the electronic device to perform methods according to the claims of this disclosure or various embodiments of this disclosure as described in this specification.

[0935] The program (software module, software) can be stored in random access memory (RAM), non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), magnetic disk storage devices, compact optical disc-ROM (CD-ROM), digital versatile optical disc (DVD), or other types of optical storage devices and / or magnetic tape cartridges. Alternatively, the program can be stored in a memory comprising some or all of the memories. Multiple memories may exist.

[0936] The program can also be stored in an attachable storage device, which can be accessed via a communication network including the Internet, intranet, local area network (LAN), wide area network (WAN), or storage area network (SAN), or a combination thereof. The storage device can be connected to an apparatus executing various embodiments of this disclosure via an external port. Additionally, a separate storage device within the communication network can be connected to an apparatus executing various embodiments of this disclosure.

[0937] In various embodiments of this disclosure, components are represented in either a singular or plural form. However, it should be understood that the singular or plural representation is chosen appropriately depending on the presented context for ease of interpretation, and this disclosure is not limited to the singular or plural form of components. Furthermore, a component expressed in a plural form may also imply a singular form, and vice versa.

[0938] While this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made in this disclosure without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a relay user equipment (UE) in a wireless communication system, the method comprising: Receive paging identification information from a remote UE that is in an inactive state of Radio Resource Control (RRC), wherein the paging identification information of the remote UE includes the 5G-S-Temporary Mobile Subscriber Identity (TMSI) of the remote UE and the inactive Radio Network Temporary Identifier (I-RNIT) of the remote UE; Identify whether the relay UE is in an RRC connected state on the active bandwidth portion (BWP) configured with information related to the paging search space; and When the relay UE is in an RRC connection state on an active BWP configured with information related to the paging search space, the paging messages for the remote UE are monitored based on the paging identification information of the remote UE.

2. The method of claim 1, further comprising: Identify paging configuration, which includes at least one of the following: total number of paging frames, number of paging opportunities for paging frames, paging frame offset, or a first discontinuous DRX cycle of the remote UE corresponding to the default cycle; Among them, information related to the second DRX cycle of the remote UE is received from the remote UE along with the paging identifier information, and The paging message for the remote UE is received based on the paging timing of the remote UE.

3. The method of claim 2, further comprising: The third DRX cycle is identified based on the first DRX cycle; The paging frame of the remote UE is identified based on at least one of the third DRX cycle, the identifier of the remote UE, the offset of the paging frame, or the total number of paging frames; as well as The paging timing of the remote UE is identified based on the identifier of the remote UE, the total number of paging frames, and the number of paging timings of the paging frames. The identifier of the remote UE is identified based on the modal function of the 5G-S-TMSI of the remote UE.

4. The method of claim 2, wherein, The second DRX period of the remote UE is the minimum value between the DRX period configured for the remote UE by the upper layer and the DRX period configured for the remote UE by the base station BS, or the DRX period configured for the remote UE by the upper layer.

5. The method of claim 1, further comprising: Receive an RRC message from the base station (BS) including the paging message for the remote UE; as well as Identify whether the paging message includes the paging identifier information of the remote UE.

6. The method of claim 5, further comprising: In response to recognizing that the paging message includes the paging identifier information of the remote UE, a message including the paging information of the remote UE is sent to the remote UE.

7. The method of claim 1, further comprising: When the relay UE is in an RRC connection state and the active BWP is configured with the information related to the paging search space, the paging message of the remote UE is monitored based on the paging timing of the remote UE. as well as When the relay UE is in an RRC connection state and the active BWP of the relay UE is not configured with the information related to the paging search space, a message including the paging identification information of the remote UE is sent to the base station BS.

8. The method of claim 1, wherein, When the relay UE switches to the target base station BS, the message including the paging identification information of the remote UE is forwarded by the source base station BS to the target base station BS.

9. A method performed by a remote user equipment (UE) in a wireless communication system, the method comprising: When in an inactive Radio Resource Control (RRC) state, the paging identifier information of the remote UE is sent to the relay UE. This paging identifier information includes the remote UE's 5G-S-Temporary Mobile Subscriber Identity (TMSI) and the remote UE's Inactive Radio Network Temporary Identifier (I-RNIT). The relay UE, which is in an RRC connection state on the active bandwidth portion (BWP) configured with information related to the paging search space, receives a paging message for the remote UE associated with the paging identification information of the remote UE.

10. The method of claim 9, further comprising: The paging configuration is received from the relay UE, the paging configuration including at least one of the following: the total number of paging frames, the number of paging times for paging frames, the offset of paging frames, or the first discontinuous reception DRX cycle of the remote UE.

11. The method of claim 9, further comprising: The second DRX of the remote UE is identified as the minimum value between the DRX period configured for the remote UE by the upper layer and the DRX period configured for the remote UE by the base station BS, or it is identified as the DRX period configured for the remote UE by the upper layer.

12. The method of claim 9, further comprising: When a paging message containing the paging identifier information of the remote UE is sent from the base station BS in an RRC message, a message including the paging information of the remote UE is received from the relay UE.

13. The method of claim 9, wherein, When the relay UE switches to the target base station BS, the message including the paging identification information of the remote UE is forwarded by the source base station BS to the target base station BS.

14. A relay user equipment (UE) in a wireless communication system, the relay UE comprising: transceiver; as well as At least one processor, the at least one processor being coupled to the transceiver and configured to: The transceiver is controlled to receive paging identification information of a remote UE that is in an inactive state of Radio Resource Control (RRC). The paging identification information of the remote UE includes the remote UE's 5G-S-Temporary Mobile Subscriber Identity (TMSI) and the remote UE's Inactive Radio Network Temporary Identifier (I-RNIT). Identify whether the relay UE is in an RRC connection state on the active bandwidth portion (BWP) configured with information related to the paging search space, and When the relay UE is in an RRC connection state on an active BWP configured with information related to the paging search space, the paging messages for the remote UE are monitored based on the paging identification information of the remote UE.

Images