Terminal devices, methods, integrated circuits

Abstract

The present invention provides a terminal device, a method, and an integrated circuit that enable efficient communication control when a terminal device communicates with a base station device via a relay terminal device. [Solution] In a communication system, a terminal device UE communicating with a base station device includes an information element in a first message indicating that the terminal device is fulfilling the role of an intermediate relay UE, based on the processing unit's determination that the terminal device is fulfilling the role of an intermediate relay UE, and the transmitting unit transmits the first message to the base station device.

Description

Technical Field

[0001] The present invention relates to a terminal device, a method, and an integrated circuit.

Background Art

[0002] In the 3rd Generation Partnership Project (3GPP [registered trademark]), which is a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems including radio access, core network, services, etc. are being carried out. For example, in 3GPP, E-UTRA (Evolved Universal Terrestrial Radio Access) was started for technical studies and standardization as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th generation and 4th generation. Even now, in 3GPP, technical studies and standardization of extended technologies of E-UTRA are being carried out. Note that E-UTRA is also referred to as Long Term Evolution (LTE [registered trademark]), and extended technologies may be referred to as LTE-Advanced (LTE-A), LTE-Advanced Pro (LTE-A Pro).

[0003]

[0004]

Prior Art Documents

Non-Patent Documents

[0005] [Non-Patent Document 1] 3GPP TS 38.331 v18.2.0," NR; Radio Resource Control (RRC) protocol specification" pp90-108,pp372-450, pp1493-1516 [Non-Patent Document 2] 3GPP TS 38.300 v18.2.0, "NR; NR and NG-RAN Overall Description" pp50-52,pp166-176, pp187-207 [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] Within 3GPP, as an extension of NR, a technology called sidelink (SL) was considered, which allows terminal devices to communicate directly with each other without going through the core network. Furthermore, a technology called UE-to-Network relay (U2N Relay) was developed, in which relay terminal devices provide sidelink communication, allowing terminal devices to communicate with base station devices via relay terminal devices, and improvements were made to enhance service continuity in U2N Relay. In addition, by connecting multiple relay terminal devices... Studies have begun on multi-hop relays to improve connectivity to mote terminal devices.

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of its objectives is to provide a terminal device, a base station device, a method, and an integrated circuit that can efficiently perform communication control. [Means for solving the problem]

[0008] To achieve the above objective, one aspect of the present invention employs the following means.

[0009] (1) A first aspect of the present invention is a terminal device that communicates with a base station device, comprising a processing unit and a transmitting unit, wherein the processing unit determines that the terminal device is playing the role of an intermediate relay UE and includes an information element indicating that it is playing the role of an intermediate relay UE in a first message, and the transmitting unit transmits the first message to the base station device.

[0010] (2) A second aspect of the present invention is a method for a terminal device to communicate with a base station device, comprising the steps of: including an information element indicating that the terminal device is playing the role of an intermediate relay UE based on the determination that the terminal device is playing the role of an intermediate relay UE in a first message; and transmitting the first message to the base station device.

[0011] (3) A third aspect of the present invention is an integrated circuit mounted on a terminal device that communicates with a base station device, which includes a function to include an information element indicating that the terminal device is playing the role of an intermediate relay UE in a first message, based on the terminal device's determination to play the role of an intermediate relay UE, and a function to transmit the first message to the base station device.

[0012] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media. [Effects of the Invention]

[0013] According to one aspect of the present invention, it is possible to provide a terminal device, a base station device, and a method for realizing efficient communication control processing. [Brief explanation of the drawing]

[0014] [Figure 1] A schematic diagram of the communication system according to this embodiment. [Figure 2] A diagram illustrating an example of the protocol configuration in NR sidelink communication according to this embodiment. [Figure 3] Diagram of an example of the protocol configuration in NR side link communication according to this embodiment. [Figure 4] Diagram of an example of the protocol configuration in the discovery procedure according to this embodiment. [Figure 5] Block diagram showing the configuration of the terminal device according to this embodiment. [Figure 6] Block diagram showing the configuration of the base station device according to this embodiment. [Figure 7] Diagram of an example of the protocol configuration in NR according to this embodiment. [Figure 8] Diagram of an example of the protocol configuration of the control plane of the L2 U-to-N relay according to this embodiment. [Figure 9] Diagram of an example of the protocol configuration of the user plane of the L2 U-to-N relay according to this embodiment. <无数000086> [Figure 10] An example of the process according to this embodiment. [Figure 11] Diagram of an example of the protocol configuration of the control plane of the multi-hop L2 U-to-N relay according to this embodiment.

Mode for Carrying Out the Invention

[0015] Hereinafter, this embodiment will be described in detail with reference to the drawings.

[0016] In this embodiment, the names of each node and entity in the case where the radio access technology is NR, and the processing in each node and entity will be described. However, this embodiment may be applied to other radio access technologies. The names of each node and entity in this embodiment may be different names.

[0017] FIG. 1 is a schematic diagram of the communication system according to this embodiment. The functions of each node, radio access technology, core network, interface, etc. described using FIG. 1 are some functions closely related to this embodiment, and may have other functions.

[0018] E-UTRA may be a wireless access technology. E-UTRA may also be an air interface between UE122 and ng-eNB100. Face 112 may be called the Uu interface. ng-eNB (ng E-UTRAN Node B) 100 may be an E-UTRAN base station device. ng-eNB 100 may have the E-UTRA protocol described below. The E-UTRA protocol may consist of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described below. ng-eNB 100 This involves the E-UTRA user plane protocol and the E-UTRA control plane protocol for UE122. The col may be terminated. A wireless access network composed of eNBs may be called E-UTRAN.

[0019] NR may be a wireless access technology. Also, NR is an air interface between UE122 and gNB102. It may be an air interface. The air interface 112 between UE122 and gNB102 may be called the Uu interface. gNB (g Node B) 102 may be an NR base station device. gNB102 may have the NR protocol described below. The NR protocol may consist of the NR User Plane (UP) protocol described below and the NR Control Plane (CP) protocol described below. gNB102 provides UE122 with the NR User Plane protocol and the NR Control Plane (CP) protocol. You may terminate the plane protocol.

[0020] The interface 110 between ng-eNB100 and gNB102 may be called the Xn interface. Furthermore, ng-eNB and gNB may be connected to 5GC via an interface called the NG interface (not shown). 5GC may be the core network. One or more base station devices may be connected to 5GC via the NG interface.

[0021] The state in which base station equipment can be connected only via the Uu interface may be called Inside NG-RAN Coverage or In-Coverage (IC). The state in which the device cannot be connected is called Outside NG-RAN Coverage or Out-of-Coverage (OoC). That's fine. The air interface 114 between UE122 and UE122 may be called the PC5 interface. Communication between UE122 via the PC5 interface is called sidelink (SL). It may be called communication. Furthermore, a terminal device capable of sidelink communication may be referred to as a sidelink communication-enabled terminal device.

[0022] In the following description, ng-eNB100 and / or gNB102 will also be simply referred to as base station equipment, and UE122 will be simply referred to as terminal equipment or UE. Furthermore, the PC5 interface will also be simply referred to as PC5. Furthermore, the Uu interface is also simply referred to as Uu.

[0023] Sidelink is a technology that enables direct communication between terminal devices via PC5, and sidelink transmission and reception on PC5 take place both inside and outside the NG-RAN coverage.

[0024] NR SL communication has three transmission modes, and SL communication is performed using one of the transmission modes with a pair of Source Layer-2 (L2) IDs and Destination Layer-2 (L2) IDs. The Source Layer-2 ID and Destination Layer-2 ID are respectively the Source L2 ID. It may also be called the destination L2ID. The three transmission modes are "Unicast transmission", "Groupcast transmission", and "Broadcast". This is a "Broadcast transmission." The transmission mode may also be referred to as the cast type, etc. Unicast transmission for direct communication is supported on PC5, and a PC5 unicast link between two UEs may be established for direct communication. The PC5 unicast link may be maintained, modified, or released according to the requirements or communication requirements of the application layer.

[0025] Unicast transmission supports (1) a single PC5-RRC connection between paired UEs, (2) transmission and reception of control information and user traffic between UEs via sidelink, (3) support for sidelink HARQ feedback, (4) transmit power control via sidelink, and (5) support for RLC AM. (6) Detection of wireless link failure for PC5-RRC connection.

[0026] Furthermore, group cast transmission is (1) between UEs belonging to a side link group Characterized by (1) sending and receiving RAFIC, and (2) support for sidelink HARQ feedback. ru.

[0027] Furthermore, broadcast transmission involves (1) sending and receiving user traffic between UEs on side links. It is characterized by faith.

[0028] Figures 2 and 3 are diagrams illustrating an example of the protocol architecture in NR sidelink communication according to this embodiment. Note that the functions of each protocol described using Figures 2 and / or 3 are only some of the functions closely related to this embodiment, and other functions may also be present. In this embodiment, sidelink (SL) refers to communication between terminal devices. A link is fine.

[0029] Figure 2(A) is a diagram of the control plane (CP) protocol stack for SCCH using RRC, configured on the PC5 interface. As shown in Figure 2(A), the control plane protocol stack for SCCH using RRC consists of the radio physical layer (PHY) 200, the medium access control layer (MAC) 202, the radio link control layer (RLC) 204, and the packet data convergence protocol layer (RLC). PDCP (Packet Data Convergence Protocol) 206, and the Wireless Resource Control Layer (Non- It may consist of an RRC (Radio Resource Control) 208, which is a linear resource control layer. Figure 2(B) is a diagram of the protocol stack of the control plane for SCCH using PC5-S, configured on the PC5 interface. As shown in Figure 2(B), the control plane for SCCH using PC5-S Your plane protocol stack consists of the PHY (Physical Layer) 200, the MAC (Medium Access Control) 202, and the RLC (Radio Link Control) 204. It may consist of a Packet Data Convergence Protocol (PDCP) 206, which is the Packet Data Convergence Protocol Layer, and a PC5 Signaling Layer (PC5-S) 210.

[0030] Figure 3(A) is a diagram of the control plane protocol stack for SBCCH configured on the PC5 interface. As shown in Figure 3(A), the control plane protocol stack for SBCCH The system may consist of a PHY (Physical layer) 200, a MAC (Medium Access Control) 202, a Radio Link Control (RLC) 204, and a Radio Resource Control (RRC) 208. Furthermore, Figure 3(B) is a diagram of the User Plane (UP) protocol stack for STCH configured on the PC5 interface. As shown in Figure 3(B), the control plane protocol stack for STCH consists of the Radio Physical Layer (PHY) 200, the Medium Access Control (MAC) 202, and It may consist of a Radio Link Control (RLC) 204, which is the linear link control layer (radio link control layer), a Packet Data Convergence Protocol (PDCP) 206, which is the packet data convergence protocol layer, and a Service Data Adaptation Protocol (SDAP) 310, which is the service data adaptation protocol layer.

[0031] The AS (Access Stratum) layer may be a layer that includes some or all of PHY200, MAC202, RLC204, PDCP206, SDAP310, and RRC208. Also, PC5-S210 and Discov (described later) ery400 can be a layer above the AS layer.

[0032] In this embodiment, the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), SDAP (SDAP layer), RRC (RRC layer), and PC5-S (PC5-S layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), SDAP (SDAP layer), RRC (RRC layer), and PC5-S (PC5-S layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), SDAP (SDAP layer), RRC (RRC layer), and PC5-S (PC5-S layer) of the NR sidelink protocol, respectively. Note that when performing sidelink communication using E-UTRA technology, the SDAP layer may be omitted. Furthermore, to clearly indicate that it is a protocol for sidelinking, for example, RLC may be expressed as sidelink RLC, and other protocols may also be preceded by "sidelink," "SL," or "PC5." This can be used to indicate that it is a protocol for sidelinking.

[0033] Furthermore, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY, MAC, RLC, PDCP, and RRC may be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. These may also be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Yes. Also, when distinguishing between the E-UTRA protocol, the sidelink protocol and the NR protocol, PHY, MAC, RLC, PDCP, and RRC are sometimes referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. In addition, PHY, MAC, RLC, PDCP, and RRC may also be written as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0034] Regarding entities in the AS layer of E-UTRA, NR, and / or sidelinks Let me explain. A PHY entity is an entity that possesses some or all of the functions of the physical layer. It may be called an "i". An entity that possesses some or all of the functions of the MAC layer may be called a MAC entity. An entity that possesses some or all of the functions of the RLC layer may be called an RLC entity. An entity that possesses some or all of the functions of the PDCP layer may be called a PDCP entity. An entity that possesses some or all of the functions of the SDAP layer may be called an SDAP entity. An entity that possesses some or all of the functions of the RRC layer It is acceptable to call this the RRC entity. The PHY entity, MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity can be rephrased as PHY, MAC, RLC, PDCP, SDAP, and RRC, respectively. In addition, each entity in the AS layer is E-UTRA, NR, or They may be common entities in a call / side link, or they may be independent entities. It's fine.

[0035] Furthermore, data provided to lower layers from MAC, RLC, PDCP, SDAP, and / or MAC, RLC The data provided to PDCP and SDAP from lower layers can be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Furthermore, the data provided to MAC, RLC, PDCP, and SDAP from higher layers, and / or the data provided from MAC, RLC, PDCP, and SDAP to higher layers, can also be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU. These data units are referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. You may call it that. Also, you may call a segmented RLC SDU an RLC SDU segment.

[0036] Here, the base station equipment and the terminal equipment are connected on the Uu interface to the upper layer. Signals are exchanged (sent and received) at the higher layer. The higher layer may also be called the upper layer, and the terms are interchangeable. For example, a base station device and a terminal device may send and receive RRC messages (also called RRC message or RRC signalling) at the Radio Resource Control (RRC) layer. Also, a base station device and a terminal device may send and receive MAC Control Elements (MAC CE) at the MAC (Medium Access Control) layer. Furthermore, the RRC layer of the terminal device acquires system information broadcast from the base station device. Here, RRC messages, system information, and / or MAC control elements are used. The input is a signal from the upper layer (higher layer signaling) or a parameter from the upper layer. Also called a data (higher layer parameter). The terminal device receives... Each of the parameters included in the upper layer signal may also be called an upper layer parameter. For example, in the processing of the PHY layer, the upper layer refers to the layer above the PHY layer, and may refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer may refer to one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0037] Furthermore, terminal devices also exchange signals (send and receive) at the higher layer (upper layer) over the PC5 interface. Terminal devices may also send and receive RRC messages (also called RRC signallings) at the Radio Resource Control (RRC) layer. In addition, terminal devices communicate with each other at the MAC (Medium Access Control) layer. In this case, MAC Control Element (MAC CE) may be sent and received. Here, the RRC message and / or MAC control element are located in the upper layer. These are also called signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each parameter included in the higher layer signal received by a terminal device may also be called a higher layer parameter. For example, PHY In layer processing, the upper layer refers to the layer above the PHY layer, and can refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, PC5-S layer, Discovery layer, etc. For example, MAC In layer processing, the upper layers may refer to one or more of the following: RRC layer, RLC layer, PDCP layer, PC5-S layer, Discovery layer, etc.

[0038] In the following, the phrases "A is provided in the upper layer" or "A is provided by the upper layer" may mean that the upper layer of a terminal device (mainly the RRC layer or MAC layer, etc.) receives A from a base station device or other terminal device, and that received A is provided from the upper layer of the terminal device to the physical layer of the terminal device. For example, "being provided with upper layer parameters" in a terminal device may mean that the terminal device receives an upper layer signal from a base station device or other terminal device, and the upper layer parameters contained in the received upper layer signal are provided from the upper layer of the terminal device to the physical layer of the terminal device. Setting upper layer parameters in a terminal device may mean that the terminal device is provided with upper layer parameters. For example, setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from a base station device or other terminal device and sets the received upper layer parameters in the upper layer. However, setting upper layer parameters in a terminal device may also include setting default parameters that are pre-assigned to the upper layer of the terminal device. When describing the transmission of RRC messages from a terminal device to a base station device or other terminal devices, the expression "submitting a message from the terminal device's RRC entity to a lower layer" is sometimes used. This may also mean submitting a message to the PDCP layer. In a terminal device, the RRC layer or "Submitting a message to a lower layer" may mean submitting an RRC message to the corresponding PDCP entity, since RRC messages are transmitted using SRBs (SRB0, SRB1, SRB2, SRB3, etc.). When an RRC entity on a terminal device receives an indication from a lower layer, that lower layer may refer to one or more layers such as the PHY layer, MAC layer, RLC layer, or PDCP layer.

[0039] An example of PHY functionality is described below. The PHY of a terminal device interacts with the PHY of other terminal devices, and is shared with other devices. Sending and receiving data via the sidelink (SL) physical channel. It may have the following function. The PHY may be connected to the higher-level MAC via a transport channel. The PHY may transfer data to the MAC via the transport channel. The PHY may also receive data from the MAC via the transport channel. In order to identify various control information, an RNTI (Radio Network Temporary Identifier) ​​may be used.

[0040] Now, let's explain physical channels. The following physical channels may be used for wireless communication between terminal devices:

[0041] PSBCH (Physical Sidelink Broadcast Channel) PSCCH (Physical Sidelink Control Channel) PSSCH (Physical Sidelink Shared Channel) PSFCH (Physical Sidelink Feedback Channel)

[0042] PSBCH may be used to broadcast system information required by terminal devices.

[0043] PSCCH may be used to indicate resources or other transmission parameters related to PSCCH.

[0044] PSSCH controls data and HARQ / CSI feedback to other terminal devices. It may be used to transmit information.

[0045] PSFCH may be used to carry HARQ feedback to other terminal devices. .

[0046] An example of MAC functionality is described below. MAC may also be called a MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. Logical channels may be identified by a Logical Channel Identity (Logical Channel ID). MAC may be connected to the higher-level RLC via logical channels. Logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information, depending on the type of information being transmitted. MAC may map one or more different logical channels. MAC may have the function of multiplexing MAC SDUs belonging to a logical channel and providing them to the PHY. MAC may also have the function of demultiplexing MAC PDUs provided by the PHY and providing them to the higher layer via the logical channel to which each MAC SDU belongs. MAC may also have the function of performing error correction through HARQ (Hybrid Automatic Repeat request). MAC may also have the function of reporting scheduling information. MAC has the function of prioritizing processing between terminal devices using dynamic scheduling. Good. Also, MAC has the function of prioritizing between logical channels within a single terminal device. MAC has the ability to prioritize the processing of overlapping resources within a single terminal device. That's fine. E-UTRA MAC is a device that identifies Multimedia Broadcast Multicast Services (MBMS). It may have the ability to identify a Multicast Broadcast Service (MBS). The MAC is a transport format. It may have the ability to select a set. The MAC may have the ability to perform discontinuous reception (DRX) and / or discontinuous transmission (DTX), the ability to perform random access (RA) procedures, the ability to notify information on available power, and power heads. Power Headroom Report (PHR) function notifies of data volume information of the transmission buffer. It may have a Buffer Status Report (BSR) function, etc. NR MAC may have a Bandwidth Adaptation (BA) function. Also, it may be used in E-UTRA MAC. The MAC PDU format used by [unspecified] and the MAC PDU format used by NR MAC may be different. Furthermore, a MAC PDU may contain MAC control elements (MAC control elements), which are elements used for control within a MAC. The element (MAC CE) may be included.

[0047] Furthermore, the MAC sublayer may provide additional services and functions on the PC5 interface, such as radio resource selection for selecting the radio resource to perform sidelink transmission, filtering of packets received in sidelink communication, priority processing between the uplink and sidelink, and reporting of Sidelink Channel State Information (Sidelink CSI).

[0048] This document describes the logical channels for sidelinks (SL) used in E-UTRA and / or NR, and the mapping between the sidelink logical channels and transport channels.

[0049] SBCCH (Sidelink Broadcast Control Channel) is a channel that collects sidelink system information. It may be a logical channel for sidelinks used to broadcast from one terminal device to one or more terminal devices. Furthermore, SBCCH is a sidelink transport channel, connected to SL-BCH. It's okay to top it.

[0050] SCCH (Sidelink Control Channel) may be a logical channel for sidelinks used to transmit control information, such as PC5-RRC messages and PC5-S messages, from one terminal device to one or more terminal devices. SCCH may also be mapped to SL-SCH, which is a sidelink transport channel.

[0051] STCH (Sidelink Traffic Control Channel) may be a logical channel for sidelinks used to transmit user information from one terminal device to one or more terminal devices. STCH may also be mapped to SL-SCH, which is a sidelink transport channel.

[0052] An example of RLC functionality is described below. RLC may also be called an RLC sublayer. E-UTRA RLC may have the functionality to segment and / or concatenate data provided from the upper layer PDCP and provide it to the lower layer. E-UTRA RLC may also reassemble and reorder data provided from the lower layer. It may have the functionality to perform ring (re-ordering) and provide it to the upper layer. NR RLC is the upper layer The NR RLC may have the function of adding a sequence number to the data provided by the PDCP of the layer, independent of the sequence number added by the PDCP. The NR RLC may also have the function of segmenting the data provided by the PDCP and providing it to the lower layer. Furthermore, the NR RLC may have the function of reassembling the data provided by the lower layer and providing it to the upper layer. The RLC may also have a data retransmission function and / or a retransmission request function (Automatic RLC may have a Repeat Request (ARQ) function. RLC may also have a function to perform error correction using ARQ. The control information sent from the RLC receiver to the transmitter, indicating the data that needs to be retransmitted, can be called a status report. Also, the RLC transmitter sends this information to the receiver. The instruction to send a status report can be called a "poll." Also, RLC is a data It may have a function to detect duplicate data. RLC may also have a data discard function. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM mode, data received from higher layers is not split, and an RLC header is not required. TM RLC entity A T is a unidirectional entity, and transmits™ RLC. It may be configured as an entity or as a receiving TM RLC entity. UM performs tasks such as splitting and / or joining data received from higher layers, and adding RLC headers. Data retransmission control is not required. UM RLC entities may be unidirectional or bidirectional. If a UM RLC entity is unidirectional, it may be configured as either a transmitting or receiving UM RLC entity. If a UM RLC entity is bidirectional, it may be configured as either a transmitting or receiving UM RLC entity. It may be configured as a UM RLC entity composed of the receiving side. The AM RLC entity may perform operations such as splitting and / or merging of data received from a higher layer, adding an RLC header, and controlling data retransmission. The AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side. Furthermore, the data provided to lower layers by TM, and / or the data provided from lower layers, The data provided to lower layers by UM, and / or data provided from lower layers, may be called UMD PDUs. The data provided to lower layers by AM, and Alternatively, data provided from lower layers can be called AMD PDU. Used in E-UTRA RLC. The RLC PDU format used in NR RLC and the RLC PDU format used in NR RLC may be different. Furthermore, there may be data RLC PDUs and control RLC PDUs. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). The control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU). The control RLC PDU used to send status reports may be called a status PDU (STATUS PDU).

[0053] In addition, in sidelinks, TM may be used for SBCCH and groupcast. For transmission and broadcast transmission, only UM is used, while UM and AM can be used for unicast transmission. Furthermore, in sidelinks, UM for groupcast and broadcast transmission supports unidirectional transmission only.

[0054] This section describes an example of PDCP functionality. PDCP may be referred to as the PDCP sublayer. PDCP may have the function of maintaining sequence numbers. Furthermore, PDCP efficiently transmits user data such as IP packets and Ethernet frames over the wireless section. It may have a header compression / decompression function for this purpose. The protocol used for compressing and decompressing IP packet headers may be called the ROHC (Robust Header Compression) protocol. The protocol used for compressing and decompressing Ethernet frame headers is EHC (Ethernet(registered trademark)). This can be called a Header Compression protocol. PDCP may also have data encryption / decryption capabilities. PDCP may also have data integrity protection / verification capabilities. PDCP may also have reordering capabilities. PDCP may also have PDCP SDU retransmission capabilities. PDCP may also have data discarding capabilities using a discard timer. PDCP may also have duplication capabilities. Furthermore, PDCP may have a function to discard duplicate received data. A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, PDCP PDUs may include There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0055] Please note that the following limitations apply to the functionality and services of PDCP in SideLink. (1) Out-of-order shipping is supported only by unicast transmission. That's fine. (2) Duplication on the PC5 interface is not supported.

[0056] This section describes an example of SDAP functionality. SDAP is a Service Data Adaptive Protocol Layer (SAP). It is a bisdata adaptive protocol layer. In sidelink, SDAP is a terminal device or The QoS flow of the side link sent to other terminal devices (PC5 QoS flow) and side link data SDAP may have a function to perform mapping with a wireless bearer (DRB). SDAP may also have a function to store mapping rule information. Furthermore, SDAP may have a QoS flow identifier (QoS). Markings for Flow ID: QFI and PC5 QoS flow identifier (PC5 QoS Flow ID: PQFI or PFI) It may have a function to perform ping. Furthermore, an SDAP PDU may consist of a data SDAP PDU and a control SDAP PDU. The data SDAP PDU is called an SDAP DATA PDU (SDAP Data PDU). That's fine. Also, the control SDAP PDU is an SDAP CONTROL PDU (SDAP Control PDU, SDAP Control It can be called a PDU (SDAP control PDU). Note that in sidelink, the SDAP entity of the terminal device T refers to unicast transmissions and groupcast transmissions associated with a destination. There may be one for each destination for either a direct transmission or a broadcast transmission. Furthermore, reflective QoS is not supported on the PC5 interface.

[0057] This section describes an example of RRC functionality. RRC operates on the PC5 interface between peer UEs. The system may support services and functions such as forwarding PC5-RRC messages, maintaining and releasing PC5-RRC connections between two UEs, and detecting sidelink radio link failures for PC5-RRC connections. A PC5-RRC connection is a logical connection between two UEs corresponding to a source L2ID and destination L2ID pair, and is considered established after the corresponding PC5 unicast link has been established. Furthermore, there is a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. A UE may also have multiple PC5-RRC connections for one or more UEs for different pairs of source L2IDs and destination L2IDs. Individual PC5-RRC procedures and messages are used by the UE to forward UE capability and sidelink configuration to the peer UE. Furthermore, both peer UEs may exchange their UE capabilities and sidelink settings with each other using separate bidirectional procedures. If you are not interested in sidelink transmission, sidelink transmission is not possible for PC5-RRC connections. If a drink wireless link failure is detected, and the Layer 2 link release procedure is completed, In conclusion, the UE releases the PC5-RRC connection.

[0058] A UE performing sidelink transmission may transmit by associating PSCCH and PSSCH. Note that sidelink transmission is transmitted via a physical channel for sidelinks (PSBCH, PSSCH, PSCCH, etc.). This may involve sending a number and / or data (message), or receiving a side link. The signal receives signals and / or data (messages) via a physical channel for the side link. It may also be believed. Furthermore, communication using sidelink transmission and sidelink reception may be referred to as sidelink communication. The UE may recognize the data (message) based on the signal. Each PSSCH transmission may be associated with a certain PSCCH (a PSCCH) transmission. A PSCCH transmission carries a first SCI (1st stage of the SCI) associated with the PSSCH transmission, and a second SCI (2nd stage of the SCI) may be carried within the resources of the PSSCH (the PSSCH). Note that a PSCCH transmission may include a first SCI, and a PSSCH transmission may include a second SCI. Furthermore, PSCCH transmission and PSSCH transmission may be referred to as sidelink transmission, and SCI is a sidelink This may be Sidelink Control Information. The first SCI may contain information in a format called SCI format 1-A and may be used for scheduling the PSSCH and the second SCI on the PSSCH. SCI format 1-A may include data priority, frequency and time resources on which the PSSCH is transmitted, resource reservation period, DMRS arrangement pattern, format of the second SCI, beta offset indication value, number of DMRS ports, modulation This may include information such as information indicating the coding scheme, and other information. Furthermore, the SCI carried on the PSSCH may be a second SCI, and the second SCI may be sidelink scheduling information and / or inter-UE coordination related information. It is permissible to transport it. The second SCI is SCI format 2-A, SCI format 2-B, and The information may be included in a format referred to as SCI format 2-C, etc. SCI format 2-A, SCI format 2-B, and SCI format 2-C may include information such as HARQ process-related information, information indicating whether it is new data, redundancy version, source ID identifying the source UE, destination ID identifying the destination UE, and information indicating whether HARQ feedback is possible. In addition, SCI format 2-A may include information indicating the cast type and information indicating whether Channel State Information (CSI) is requested. Format 2-B may include additional zone identifiers and communication range requirements. Furthermore, SCI format 2-C may include information indicating whether or not to request additional channel status information, and information indicating whether or not to provide or request inter-UE coordination information. If SCI format 2-C includes information to provide inter-UE coordination information, SCI format 2-C may also include information indicating resource combinations, information indicating the initial resource location, reference slot location information, resource set type, lowest subchannel index, etc. If SCI format 2-C includes information requesting inter-UE coordination information, SCI format 2-C may also include information indicating priority, number of subchannels, resource reservation interval, resource selection window location, resource set type, etc. It may include information. Furthermore, each SCI format may include information other than that described above. .

[0059] Next, we will describe the procedure for the UE receiving the PSSCH. When the UE detects SCI format 1-A on the PSSCH, it can decode the PSSCH according to the detected SCI format 2-A or SCI format 2-B, and the associated PSSCH resource settings configured by the higher layer. Note that the UE decodes one or more PSCCHs for each candidate PSCCH resource. It is not necessary to do so. Furthermore, if the UE does not support the modulation and coding scheme shown in SCI format 1-A, it is not necessary to decode the corresponding SCI format 2-A and SCI format 2-B, and the PSSCH associated with SCI format 1-A.

[0060] Furthermore, in the upper (RRC) layer, if the parameter indicating whether the DMRS used for L1 RSRP measurement during sensing operations is the PSCCH DMRS or the PSSCH DMRS is set to PSSCH, the UE will... From the DMRS resource element for PSSCH related to the received SCI format 1-A, measure the PSSCH RSRP, and if PSCCH is set, the PSCCH related to the received SCI format 1-A PSCCH RSRP may be measured from the DMRS resource elements for this purpose.

[0061] Terminal devices capable of side-link communication may perform discovery. Discovery may involve both Model A and Model B devices. Figure 4 shows the protocol for the discovery procedure. Describe the stack. Mode A uses a single discovery protocol message, while Model B may use two discovery protocol messages. One Discovery Protocol message may be an Announcement message, while in Model B, the Discovery Protocol message is a Solicitation message. These may be announcement and response messages. Furthermore, announcement messages, solicitation messages, and response messages may be collectively referred to as discovery messages, and other messages with different names used in the discovery procedure may also be referred to as discovery messages. The following outlines the procedures for Model A and Model B in ProSe Direct Discovery.

[0062] In Model A, the UE that sends an announcement message may be called the Announcing UE, and the UE that monitors the announcement message may be called the Monitoring UE. The announcement message may include information such as the type of discovery message, ProSe Application Code or ProSe Restricted Code, and security protection element, and may also include additional metadata information. The announcement message may include the Destination Layer-2 ID and Source Layer-2 ID. The message is transmitted using this method, and the monitoring UE determines the destination L2ID to receive the announcement message. The destination L2ID may be the Layer 2 identifier of the destination UE, and the source L2ID may be the Layer 2 identifier of the source UE. The destination UE may simply be referred to as the destination.

[0063] In Model B, the UE that sends the solicitation message may be referred to as the discoverer UE. The UE that receives the solicitation message, and / or sends a response message to the discoverer UE, may be referred to as the discoveree UE. The solicitation message may include the discovery message. The information may include the message type, ProSe Query Code, and security protection elements. The solicitation message is sent using the destination L2ID and source L2ID, and the discovered UE determines the destination L2ID to receive the solicitation message. Also, a discovered UE that responds to the solicitation message sends a response message. The response message may include information such as the discovery message type, ProSe Response Code, and security protection elements, and may also include additional metadata information. The response message is sent using the source L2ID, and the destination L2ID is set to the source L2ID of the received solicitation message.

[0064] Discovery may include types other than ProSe Direct Discovery, which discovers other UEs for direct communication with them. Other types may include Group Member Discovery, which discovers one or more UEs for communication within a group using side links, and 5G ProSe UE-to-Network Relay Discovery, which discovers candidate relay UEs for connecting to the network via relay UEs. Note that the above-mentioned discovery is an application called ProSe. The above is an example of discovery provided by the protocol, but there may be other types of discovery depending on the application or service performing side-link communication. Also, the information contained in the discovery protocol message may differ depending on the type of discovery, and additional messages may be sent to transmit additional information.

[0065] Figure 4 is a diagram showing an example of a protocol configuration including the discovery protocol according to this embodiment. As shown in Figure 4, the discovery plane, including the discovery protocol, The protocol stack consists of a radio physical layer (PHY) 200, a medium access control layer (MAC) 202, and It may consist of a Radio Link Control (RLC) 204, which is the linear link control layer (radio link control layer), a Packet Data Convergence Protocol (PDCP) 206, which is the packet data convergence protocol layer, and a Discovery 400, which is the discovery protocol layer. Discovery 400 is related to discovery. It may be a protocol used to process the procedure. Furthermore, the interface between UEs performing discovery may be referred to as PC5-D.

[0066] Multiple resource pools may be configured for sending messages used in discovery procedures (discovery messages), and the discovery process may also be configured. One or more resource pools may be configured specifically for discovery. If a resource pool dedicated to discovery is configured, the UE may use the discovery-dedicated resource pool for sending discovery messages. If a resource pool dedicated to discovery is not configured, the UE may use the resource pool for sidelink communication for sending discovery messages. Note that multiple resource pools for sidelink communication and discovery-dedicated resource pools may be configured simultaneously. Each resource pool may be configured in UE-dedicated signaling or may be configured in advance.

[0067] We will also explain Direct Communication Request (DCR) messages. The Direct Communication Request message may be a message used to establish a unicast link. The DCR message may include at least the identifier of the source UE. - If the get UE identifier is provided by the application layer, it may include the target UE identifier and other information, such as security information or application information. Also, the DCR message uses the source L2ID and destination L2ID to uniquely They may be transmitted via chats or broadcast. Discovery messages and DCR messages may also be transmitted via sidelink. The discovery message may be integrated into the DCR message. If an integrated discovery message is used for a U2N relay or U2U relay, the DCR message may include additional information, such as relay_indication, to indicate that it is a message for a relay.

[0068] In each unicast PC5-RRC connection, a sidelink signaling radio bearer (SRB) may be configured. The sidelink SRB used to transmit PC5-S messages before PC5-S security is established may be referred to as SL-SRB0. A sidelink SRB used to transmit PC5-S messages to establish security may be referred to as SL-SRB1. A sidelink SRB used to transmit protected PC5-S messages after PC5-S security has been established may be referred to as SL-SRB2. A sidelink SRB used to transmit protected PC5-RRC signaling after PC5-S security has been established may be referred to as SL-SRB3. A sidelink SRB used to transmit and / or receive discovery messages in NR may be referred to as SL-SRB4. Note that PC5-RRC signaling may be RRC signaling between UEs transmitted and received on PC5. Note that PC5-RRC signaling is PC5-RRC message It can be called sage, for example.

[0069] Here, we will explain UE-to-Network (U2N) relays. U2N relays are used in remote terminal equipment The function may be one that provides network connectivity to a Remote UE. A remote terminal device that connects to the network using a U2N relay may be called a U2N Remote UE. Furthermore, terminal devices that provide network connectivity to U2N Remote UEs may be referred to as U2N relay terminal devices (Relay UEs), or simply relay terminal devices (Relay UEs). U2N Relay UEs may use a Uu interface for communication with base station devices, and for communication with U2N Remote UEs. A PC5 interface may be used for communication. Furthermore, U2N relays may include different types such as Layer 2 (L2) U2N relays and Layer 3 (L3) U2N relays. The remote terminal device in an L2 U2N relay may be specifically called an L2 U2N Remote UE, and the relay terminal device in an L2 U2N relay may be specifically called an L2 U2N Relay UE. Also, in an L2 U2N relay, a side-link relay may be used. The SRAP (Sidelink Relay Adaptation Protocol) layer, SRAP 800, It is acceptable for it to exist. Furthermore, SRAP800 may simply be referred to as SRAP.

[0070] Figure 8 is a diagram showing an example of the protocol configuration of the control plane (C-plane) of an L2 U2N relay, including the SRAP layer (SRAP800) according to this embodiment. Figure 9 is a diagram showing an example of the protocol configuration of the user plane (U-plane) of an L2 U2N relay, including the SRAP layer according to this embodiment. As shown in Figures 8 and 9, the SRAP layer may be associated between the Remote UE and the Relay UE, or between the Relay UE and the gNB102. Note that the gNB102 shown in Figures 8 and 9 is ng-eNB100. This is also acceptable. Furthermore, the Remote UE or Relay UE may be UE122. Also, the Relay UE may have the same configuration as UE122.

[0071] Here, we will explain the SRAP layer. The SRAP layer may also be called the SRAP sublayer or simply SRAP. The SRAP sublayer controls the control planes and Uu interfaces for both the PC5 interface and the Uu interface. - May reside above the RLC sublayer for the plane. The SRAP sublayer on PC5 may be used for bearer mapping purposes. In L2 U2N Relay UE, the SRAP sublayer is on the Uu interface. It may include one SRAP entity and separate collocated SRAP entities on the PC5 interface. In an L2 U2N Remote UE, the SRAP sublayer may include only one SRAP entity on the PC5 interface. An SRAP entity associated between the Remote UE and the Relay UE via the PC5 interface is specifically referred to as PC5-SRAP. It is acceptable to refer to SRAP entities associated between Relay UE and gNB via Uu as Uu-SRAP. Furthermore, when clarifying interface names, other entities may also be expressed in the same format as SRAP, such as (interface name)-(entity name). Each SRAP entity may have a transmitter and a receiver. On the PC5 interface, the transmitter of an L2 U2N Remote UE SRAP entity may be associated with the receiver of an L2 U2N Relay UE SRAP entity, and the receiver of an L2 U2N Remote UE SRAP entity may be associated with an L2 U2N It may be associated with the transmitter portion of the SRAP entity of the Relay UE. Also, the Uu interface. Above, the transmission unit of the SRAP entity of the L2 U2N Relay UE is the SRAP entity of gNB102. The receiver of the L2 U2N Relay UE may be associated with the receiver of the gNB102 SRAP entity, and the receiver of the L2 U2N Relay UE may be associated with the transmitter of the gNB102 SRAP entity.

[0072] Furthermore, SRAP entities have the functions to transfer data, determine the UE ID field and bearer ID field of the SRAP header attached to the data packet, and establish an egress link. It may have a function to determine the exit (egress) RLC channel.

[0073] Furthermore, in Figures 8 and 9, a PC5 Relay RLC channel may be set between the Remote UE and the Relay UE, and a Uu Relay RLC channel may be set between the Relay UE and the gNB102.

[0074] This section describes multi-hop relays. A multi-hop relay may be a U2N relay in which multiple relay terminals intervene in a single path from a remote terminal device to the gNB102. Figure 11 shows an example of a C-plane protocol stack in a multi-hop relay. For example, among the multiple relay terminals, the relay terminal directly connected to the gNB102 via the Uu interface may be called the last relay terminal (MH U2N Last Relay UE in Figure 11), and among the multiple relay terminals, the relay terminals other than the last relay terminal (UEs belonging to the dotted line area including the MH U2N First Relay UE in Figure 11) may be called intermediate relay terminals. The intermediate relay terminal devices may be referred to as the first relay terminal device, second relay terminal device, third relay terminal device, etc., in order of hopping from the remote terminal device. The plurality of relay terminal devices may also be terminal devices that provide connectivity to the gNB to the remote terminal device. The names of the terminal devices mentioned above are examples only and are not exhaustive. Figure 11 shows a C-plane This is just one example of a protocol stack, and the implementation method is not limited to this. A similar structure may also be used for the U-plane protocol stack. For example, the SDAP layer may be used instead of the RRC layer in the figure. In addition, in a multi-hop relay, if the node to which the link with the remote UE terminates is a base station device, as shown in Figure 11, it may be called a multi-hop U2N relay, and if the node to which the link with the remote UE terminates is a UE, it may be called a multi-hop U2U relay.

[0075] Next, the protocol configuration used between the base station equipment and the terminal equipment will be described. In communication conducted via the Uu interface between the relay terminal equipment and the base station equipment, and in communication conducted between the remote terminal equipment and the base station equipment via the relay terminal equipment, the protocol used between the base station equipment and the terminal equipment may be used. However, in communication conducted between the remote terminal equipment and the base station equipment via the relay terminal equipment, some protocols may not need to be associated between the remote terminal equipment and the base station equipment.

[0076] Figure 7 is a diagram showing an example of the NR protocol configuration according to this embodiment. The functions of each protocol described using Figure 7 are some of the functions closely related to this embodiment, and other functions may also be present. In this embodiment, the uplink (UL) refers to the connection from the terminal device to the base station device. It may be a link to the base. Also, in this embodiment, a downlink (DL) is a base It may be a link from a central station to a terminal device.

[0077] Figure 7(A) is a diagram of the NR control plane (CP) protocol stack. As shown in Figure 7(A), the NR CP protocol may be the protocol between UE122 and gNB102. That is, the NR CP protocol is The protocol may terminate on the network side with gNB102. As shown in Figure 7(A), the NR control plane protocol stack consists of a radio physical layer (PHY) ayer)700, MAC (Medium Access Control)702 which is the medium access control layer, RLC704 which is the wireless link control layer, packet data convergence It may consist of a protocol layer (packet data convergence protocol layer), PDCP (Packet Data Convergence Protocol) 706, and a radio resource control layer (radio resource control layer), RRC (Radio Resource Control) 708. Also, Figure 7(B) shows the NR user plane (UP) This is a diagram of the protocol stack. As shown in Figure 7(B), the NR UP protocol may be the protocol between UE122 and gNB102. That is, the NR UP protocol terminates at gNB102 on the network side. It may be an end protocol. As shown in Figure 7(B), the NR user plane protocol stack consists of the radio physical layer PHY700, the medium access control layer MAC702, the radio link control layer RLC704, the packet data convergence protocol layer PDCP706, and service data It may consist of an adaptive protocol layer (service data adaptive protocol layer) called SDAP (Service Data Adaptation Protocol) 710.

[0078] The AS (Access Stratum) layer may be the layer that terminates between UE122 and gNB102. The AS layer includes some or all of PHY700, MAC702, RLC704, PDCP706, and RRC708. It may be a layer. Also, gNB102 may be ng-eNB100. Also, only the NR protocol. Although this was shown, the E-UTRA protocol may also be used. In the E-UTRA protocol, SDAP710 It does not need to exist, and the E-UTRA protocol may have some functions that differ from the NR protocol.

[0079] In this embodiment, the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) may be used without distinguishing between the E-UTRA protocol and the NR protocol. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) of the E-UTRA protocol, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) of the NR protocol, respectively. Also, SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

[0080] Furthermore, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY500, MAC502, RLC504, PDCP506, and RRC508 are referred to as the E-UTRA PHY or LTE PHY, the E-UTRA MAC or LTE MAC, the E-UTRA RLC or LTE RLC, and the E-UTRA PDCP or LTE These are sometimes called PDCP for E-UTRA, and RRC for E-UTRA or RRC for LTE. Also, PHY500, MAC502, RLC504, PDCP506, and RRC508 are referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE PHY, respectively. It may also be written as MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC. Furthermore, a distinction is made between the E-UTRA protocol and the NR protocol. In such cases, PHY500, MAC502, RLC504, PDCP506, and RRC508 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Furthermore, PHY500, MAC502, RLC504, PDCP506, and RRC508 may also be written as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0081] This section describes entities in the AS layer of E-UTRA and / or NR. Entities that possess some or all of the functionality of a layer may be called PHY entities. Entities that possess some or all of the functionality of a MAC layer may be called MAC entities. An entity possessing some or all of the functions of the RLC layer may be called an RLC entity. An entity possessing some or all of the functions of the PDCP layer may be called a PDCP entity. An entity possessing some or all of the functions of the SDAP layer may be called an SDAP entity. An entity possessing some or all of the functions of the RRC layer may be called an RRC entity. PHY entity, MAC entity, RLC entity, PDCP entity The SDAP entity and RRC entity are referred to as PHY, MAC, RLC, PDCP, SDAP, and RRC, respectively. You may substitute it.

[0082] Furthermore, data provided to lower layers from MAC, RLC, PDCP, SDAP, and / or MAC, RLC The data provided to PDCP and SDAP from lower layers can be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Furthermore, the data provided to MAC, RLC, PDCP, and SDAP from higher layers, and / or the data provided from MAC, RLC, PDCP, and SDAP to higher layers, can also be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU. These data units are referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. You may call it that. Also, you may call a segmented RLC SDU an RLC SDU segment.

[0083] Here, the base station equipment and the terminal equipment transmit signals in the upper layer. To exchange (send and receive). The higher layer can also be called the upper layer, and they are interchangeable. For example, base station equipment and terminal equipment send and receive RRC messages (also called RRC message or RRC signalling) at the Radio Resource Control (RRC) layer. It is also possible that the base station equipment and the terminal equipment transmit and receive MAC control elements at the MAC (Medium Access Control) layer. Furthermore, the RRC layer of the terminal equipment acquires system information broadcast from the base station equipment. Here, RRC messages, system information, and or / or, the MAC control element controls the signals of the upper layer (upper layer signals). These are also called signaling or higher layer parameters. Each parameter included in the higher layer signal received by a terminal device may also be called a higher layer parameter. For example, in the processing of the PHY layer, the higher layer refers to the layer above the PHY layer, and may refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may refer to one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0084] In the following, the meaning of “A is provided (given) at the upper layer” or “A is provided (given) by the upper layer” is that the upper layer of the terminal device (mainly the RRC layer and MAC layer, etc.) receives A from the base station device, and that received A is provided (given) from the upper layer of the terminal device to the physical layer of the terminal device. It may also mean that "higher layer parameters are provided" in a terminal device. "Provided" may mean that the terminal device receives an upper-layer signal from the base station device, and the upper-layer parameters contained in the received upper-layer signal are provided from the upper layer of the terminal device to the physical layer of the terminal device. Setting upper-layer parameters in the terminal device may mean that the upper-layer parameters are given (provided) to the terminal device. For example, setting upper-layer parameters in the terminal device may mean that the terminal device receives an upper-layer signal from the base station device and sets the received upper-layer parameters in the upper layer. However, setting upper-layer parameters in the terminal device may also include setting default parameters that are pre-assigned to the upper layer of the terminal device. When describing the transmission of an RRC message from the terminal device to the base station device, the expression "submitting a message from the RRC entity of the terminal device to the lower layer" may be used. "Submitting" may also mean submitting a message to the PDCP layer. In a terminal device, "submitting a message to a lower layer" from the RRC layer means that since RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.), the PDCP corresponding to each SRB... This may also mean submitting to an entity. The RRC entity of the terminal device is at a lower layer or When receiving an indication, the lower layers include the PHY layer, MAC layer, RLC layer, PDCP layer, etc. It may mean one or more.

[0085] An example of PHY functionality is described below. The PHY of the terminal device receives downlink from the PHY of the base station device. Downlink (DL) receives data transmitted via the Physical Channel. It may have the function. The PHY of the terminal device is related to the PHY of the base station device, and is an uplink (UL) device. The PHY may have the function of transmitting data via a transport channel. The PHY may be connected to the higher-level MAC via a transport channel. The PHY can then transfer data to the MAC. Also, the PHY can receive data from the MAC via the transport channel. Data may be provided. In the PHY, RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0086] Now, let's explain physical channels. The following physical channels may be included in the physical channels used for wireless communication between terminal equipment and base station equipment.

[0087] PBCH (Physical Broadcast Channel) PDCCH (Physical Downlink Control Channel) PDSCH (Physical Downlink Shared Channel) PUCCH (Physical Uplink Control Channel) PUSCH (Physical Uplink Shared Channel) PRACH (Physical Random Access Channel)

[0088] PBCH may be used to broadcast system information required by terminal devices.

[0089] Furthermore, in NR, the PBCH may be used to announce the time index (SSB-Index) within the period of the Synchronization Signal Block (SSB).

[0090] PDCCH is used in downlink wireless communication (wireless communication from base station equipment to terminal equipment). It may be used to transmit (or carry) Downlink Control Information (DCI). Here, for the transmission of Downlink Control Information, one or more DCIs (DCI A format (which may also be called a format) may be defined. That is, for downlink control information The field may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate. It may be transmitted in the candidate. The terminal device may monitor the set of PDCCH candidates in the serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The terminal device may also perform a search sample PDCCH candidates may be monitored at configured monitoring occasions within one or more configured control resource sets (CORESET) as set by the configuration. The DCI format may be used for scheduling PUSCH in serving cells. PUSCH may be used for sending user data or sending RRC messages, as described later.

[0091] By using two sets of search spaces explicitly linked by the configuration provided by the upper layer (RRC layer), PDCCH repetition is performed. This may be operated. Also, the two linked search space sets may be associated with the corresponding CORESET (corresponding CORESET). For PDCCH iteration, link The two search space sets were configured on the terminal device along with the same number of PDCCH candidates. Yes, that's fine. Two PDCCH candidates present in two linked search space sets are the same candidate. It may be linked by a supplementary index. PDCCH repetition is scheduled on the terminal device. When this occurs, inter-slot repetition may be allowed, and each repetition These may have the same number of control channel elements (CCEs), coded bits, and the same DCI payload.

[0092] PUCCH is used in uplink wireless communication (wireless communication from terminal equipment to base station equipment), It may be used to transmit Uplink Control Information (UCI). Here, the Uplink Control Information may include Channel State Information (CSI), which is used to indicate the state of the Downlink channel. The control information may include scheduling requests (SRs) used to request UL-SCH (UL-SCH: Uplink Shared Channel) resources. The link control information includes HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement). It's okay to be born.

[0093] PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. In the case of downlinks, PDSCH may also be used to transmit system information (SI) and random access responses (RAR).

[0094] PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or to transmit HARQ-ACK and / or CSI along with uplink data. Alternatively, PUSCH may be used to transmit CSI only, or HARQ-ACK and CSI only. In other words, PUSCH may be used to transmit only UCI messages. Alternatively, PDSCH or PUSCH may be used to transmit RRC messages and MAC CE messages, as described later. In PDSCH, RRC messages transmitted from a base station may be common signaling for multiple terminal devices within a cell. Alternatively, RRC messages transmitted from a base station may be dedicated signaling for a particular terminal device. In other words, terminal device-specific (UE-specific) information may be dedicated to a particular terminal device. It may also be transmitted using the signaling of the UE. In addition, PUSCH can transmit on the uplink. It may be used to transmit force (UE Capability).

[0095] PRACH may be used to send a random access preamble. PRACH is used in the initial connection establishment procedure, handover procedure, connection re-establishment procedure, and above It may be used to indicate synchronization (timing adjustment) for relink transmissions and requests for UL-SCH resources.

[0096] An example of MAC functionality is described below. MAC may also be called a MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. Logical channels may be identified by a Logical Channel Identity (Logical Channel ID). MAC may be connected to the higher-level RLC via logical channels. Logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information, depending on the type of information being transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. MAC may have one or more different The MAC may have the function of multiplexing MAC SDUs belonging to a logical channel and providing them to the PHY. The MAC may also have the function of demultiplexing MAC PDUs provided by the PHY and providing them to the upper layer via the logical channel to which each MAC SDU belongs. Furthermore, the MAC may have the function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). Finally, the MAC may have the function of reporting scheduling information. That's fine. MAC uses dynamic scheduling to perform priority processing between terminal devices. You may have it. Furthermore, MAC has the function of prioritizing between logical channels within a single terminal device. That's fine. MAC is a device that prioritizes the processing of overlapping resources within a single terminal device. It is possible to have this ability. E-UTRA MAC identifies Multimedia Broadcast Multicast Services (MBMS). The MAC may have the function to identify Multicast Broadcast Service (MBS). The MAC may have the function to select the transport format. The MAC may have the function to perform Discontinuous Reception (DRX) and / or Discontinuous Transmission (DTX), random Functions to perform access (Random Access: RA) procedures, notify information on transmittable power, power Features include a Power Headroom Report (PHR) function, a Buffer Status Report (BSR) function that notifies users of the amount of data in the transmit buffer, and more. It is permissible to have it. NR MAC may have Bandwidth Adaptation (BA) functionality. Also, E-UT The MAC PDU format used in RA MAC and the MAC PDU format used in NR MAC may be different. Furthermore, the MAC PDU may include MAC control elements (MAC CEs), which are elements used for control within the MAC.

[0097] Uplink (UL) and / or downlink used in E-UTRA and / or NR This section explains logical channels for Downlink (DL).

[0098] BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information, such as system information (SI).

[0099] A PCCH (Paging Control Channel) may be a downlink logical channel for carrying paging messages.

[0100] CCCH (Common Control Channel) may be a logical channel for transmitting control information between terminal equipment and base station equipment. CCCH is used when terminal equipment does not have RRC connection. It may be used. Furthermore, CCCH may be used between a base station device and multiple terminal devices.

[0101] DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information bidirectionally (point-to-point) between terminal equipment and base station equipment. That is fine. Dedicated control information may be control information specific to each terminal device. DCCH may be used when the terminal device has an RRC connection.

[0102] A DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data one-to-one (point-to-point) between a terminal device and a base station device. It may be a logical channel for transmitting data. Dedicated user data may be user data specific to each terminal device. DTCH may exist on both the uplink and downlink.

[0103] Logical channels and transport channels of the uplink in E-UTRA and / or NR Let's explain the mapping of the 'ru' element.

[0104] CCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0105] DCCH is an uplink transport channel, also known as UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0106] DTCH is an uplink transport channel, UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0107] Logical channels and transport channels of downlinks in E-UTRA and / or NR Let's explain the mapping of the 'ru' element.

[0108] BCCH stands for Broadcast Channel, which is a downlink transport channel, and / Alternatively, it may be mapped to DL-SCH (Downlink Shared Channel).

[0109] PCCH is mapped to PCH (Paging Channel), which is a downlink transport channel. That's fine.

[0110] CCCH is a Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0111] DCCH is a Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0112] DTCH stands for Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0113] An example of RLC functionality is described below. RLC may also be called an RLC sublayer. E-UTRA RLC may have the functionality to segment and / or concatenate data provided from the upper layer PDCP and provide it to the lower layer. E-UTRA RLC may also reassemble and reorder data provided from the lower layer. It may have the functionality to perform ring (re-ordering) and provide it to the upper layer. NR RLC is the upper layer The NR RLC may have the function of adding a sequence number to the data provided by the PDCP of the layer, independent of the sequence number added by the PDCP. The NR RLC may also have the function of segmenting the data provided by the PDCP and providing it to the lower layer. Furthermore, the NR RLC may have the function of reassembling the data provided by the lower layer and providing it to the upper layer. The RLC may also have a data retransmission function and / or a retransmission request function (Automatic It is permitted to have a Repeat request (ARQ). Furthermore, RLC has the functionality to perform error correction using ARQ. Yes, that's correct. The control information sent from the RLC receiver to the transmitter to perform ARQ, indicating data that needs to be retransmitted, can be called a status report. Also, the information sent from the RLC transmitter to the receiver... The instruction to send a status report can be called a "poll." Also, RLC is a de The RLC may have a function to detect duplicate data. The RLC may also have a data discard function. The RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM, the above The data received from the layer does not need to be split, and the addition of an RLC header is not required. TM RLC header An entity is a unidirectional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity. UM performs splitting and / or joining of data received from higher layers, adds RLC headers, etc., but does not need to control data retransmission. UM RLC entities may be unidirectional or bidirectional entities. If a UM RLC entity is unidirectional, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If a UM RLC entity is bidirectional, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. AM The data received from the upper layer may be split and / or merged, an RLC header may be added, and data retransmission control may be performed. The AM RLC entity is a bidirectional entity and is configured as an AM RLC consisting of a transmitting side and a receiving side. Good. Also, the data that TM provides to lower layers, and / or the data provided by lower layers. This can be called TMD PDU. Also, the data provided to lower layers by UM, and / or the data provided by lower layers, can be called UMD PDU. Also, the data provided to lower layers by AM Alternatively, the data provided from lower layers may be called AMD PDU. Used in E-UTRA RLC The RLC PDU format used in [unspecified] and the RLC PDU format used in NR RLC may be different. Furthermore, there may be data RLC PDUs and control RLC PDUs. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). The control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU).

[0114] This section describes an example of PDCP functionality. PDCP may be referred to as the PDCP sublayer. PDCP may have the function of maintaining sequence numbers. Furthermore, PDCP efficiently transmits user data such as IP packets and Ethernet frames over the wireless section. It may have a header compression / decompression function for this purpose. The protocol used for compressing and decompressing IP packet headers may be called the ROHC (Robust Header Compression) protocol. The protocol used for compressing and decompressing Ethernet frame headers is EHC (Ethernet(registered trademark)). It may be called a Header Compression (PDCP) protocol. PDCP may also have data encryption / decryption capabilities. PDCP may also have data integrity protection / verification capabilities. PDCP may also have reordering capabilities. PDCP may also have PDCP SDU retransmission capabilities. PDCP may also have data discarding capabilities using a discard timer. PDCP may also have duplication capabilities. Furthermore, PDCP may have a function to discard duplicate received data. A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0115] This section describes an example of SDAP functionality. SDAP is a Service Data Adaptive Protocol Layer (SAP). SDAP is a bis-data adaptive protocol layer. SDAP may have the function of mapping downlink QoS flows sent from 5GC to terminal devices via base station equipment to data radio bearers (DRBs), and / or mapping uplink QoS flows sent from terminal devices to 5GC via base station equipment to DRBs. SDAP may also have the function of storing mapping rule information. SDAP may also have the function of marking QoS flow identifiers (QoS Flow ID: QFI). Note that there may be data SDAP PDUs and control SDAP PDUs. Data SDAP PDUs may be SDAP DATA PDUs (SDAP Data PDUs, SDAP data PDUs) You can call it that. Also, the control SDAP PDU is called an SDAP CONTROL PDU (SDAP Control PDU, SDAP Control). These may be called PDUs (PDUs or SDAP control PDUs). Note that there may be only one SDAP entity for each PDU session on the terminal device.

[0116] An example of RRC functionality is described below. RRC may have broadcast functionality. RRC may have paging functionality from 5GC. RRC may have paging functionality from gNB102 or ng-eNB100. Furthermore, RRC The RRC may have an RRC connection management function. The RRC may also have a wireless bearer control function. The RRC may also have a cell group control function. The RRC may also have a mobility control function. The RRC may also have terminal device measurement reporting and terminal device measurement reporting It may have a wireless link control function. Furthermore, the RRC may have a QoS management function. Also, the RRC may have a wireless link control function. It may have failure detection and recovery functions. RRC may use RRC messages for notification, paging, RRC connection management, wireless bearer control, cell group control, mobility control, and terminal equipment. On-site measurement reporting and terminal device measurement reporting control, QoS management, wireless link loss Failure detection and recovery may be performed. Note that RRC messages and other information used in E-UTRA RRC may be used. The parameters may differ from those used in NR RRC, such as RRC messages and parameters. The RRC message may contain multiple information elements (IE) for the control functions described above.

[0117] RRC messages may be sent using the logical channel BCCH, or the logical channel PCCH. It may be sent using the logical channel CCCH, or it may be sent using the logical channel DCCH. Furthermore, RRC messages sent using DCCH are called dedicated RRC signaling or RRC signaling.

[0118] RRC messages sent using BCCH may include, for example, a Master Information Block (MIB), and various types of System Information Blocks (System Informa A tion Block (SIB) may be included, and other RRC messages may be included. RRC messages sent using PCCH may include, for example, paging messages, and other RRC messages.

[0119] RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request messages, RRC Resume Request messages, RRC Reestablishment Request messages, and RRC System Information Request messages. This may include messages such as Sage (RRC System Info Request). It may also include messages such as RRC Connection Request, RRC Connection Resume Request, and RRC Connection Reestablishment Request. Other RRC messages may also be included.

[0120] RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject messages, RRC Connection Setup messages, RRC Connection Reestablishment messages, and RRC Connection Reestablishment Reject messages. It may include, for example, RRC rejection messages and RRC setup messages. It may also include other RRC messages.

[0121] RRC signaling transmitted in the uplink (UL) direction using DCCH includes, for example, measurement reports. Messages such as Measurement Report, RRC Connection Reconfiguration Complete, RRC Connection Setup Complete, RRC Connection Reestablishment Complete, Security Mode Complete, and UE Capability Information may be included. RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message, Security Mode Complete message This may include messages such as "Security Mode Complete" and "UE Capability Information." It may also include other RRC signaling.

[0122] RRC signaling sent in the downlink (DL) direction using DCCH may include, for example, RRC Connection Reconfiguration messages, RRC Connection Release messages, Security Mode Command messages, and UE Capability Enquiry messages. It may also include, for example, RRC Reconfiguration messages, RRC Resume messages, RRC Release messages, RRC Reestablishment messages, Security Mode Command messages, and UE Capability Enquiry messages. Other RRC signaling may also be included.

[0123] The aforementioned PHY, MAC, RLC, PDCP, SDAP, and RRC functions are merely examples, and some or all of each function may not be implemented. Furthermore, some or all of the functions of each layer may be included in other layers.

[0124] This section explains radio bearers. When a terminal device communicates with a base station device, a radio bearer (RB) is established between the terminal device and the base station device to establish a wireless connection. Good. Radio bearers used in CP may be called Signaling Radio Bearers (SRBs). Radio bearers used in UP may be called Data Radio Bearers (DRBs). Each radio bearer may be assigned a radio bearer identifier (Identity: ID). The radio bearer identifier for SRBs is the SRB identifier (SRB Identity, or SRB ID) and It may be called. The radio bearer identifier for DRB may be called the DRB identifier (DRB Identity, or DRB ID). E-UTRA's SRB may define SRB0 to SRB2, or other SRBs may be defined. NR's SRB may define SRB0 to SRB3, or other SRBs may be defined. SRB0 may be the SRB for RRC messages, transmitted and / or received using the logical channel CCCH. SRB1 may be the SRB for RRC signaling and for NAS signaling before SRB2 is established. Transmitting and / or receiving using SRB1 The RRC signaling performed may include piggybacked NAS signaling. All RRC and NAS signaling transmitted and / or received using SRB1 The DCCH of the logical channel may be used. SRB2 is for NAS signaling and, It may be an SRB for RRC signaling that includes logged measurement information. All RRC signaling and NAS signaling transmitted and / or received using SRB2. For narring, the logical channel DCCH may be used. Also, SRB2 may have a lower priority than SRB1. SRB3 is used when EN-DC, NGEN-DC, NR-DC, etc. are configured on the terminal device. It may be an SRB for transmitting and / or receiving specific RRC signaling. All RRC signaling and NAS signaling transmitted and / or received using SRB3 may use the DCCH logical channel. In addition, other SRBs may be provided for other purposes. The DRB may be a radio bearer for user data. A logical channel (DTCH) may be used for RRC signaling transmitted and / or received using the DRB.

[0125] This section describes wireless bearers in terminal devices. Wireless bearers include RLC bearers. Good. An RLC bearer may consist of one or two RLC entities and a logical channel. If an RLC bearer has two RLC entities, the RLC entities are TM RLC entities. , and / or in unidirectional UM mode RLC entities, the transmitting RLC entity and SRB0 may consist of a single RLC bearer. The RLC bearer of SRB0 may consist of a TM RLC entity and a logical channel. SRB0 may always be established in terminal devices in all RRC states (RRC idle state, RRC connected state, and RRC inactive state, etc.). SRB1 may be established and / or set in a terminal device by RRC signaling received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state. SRB1 may consist of a single PDCP entity and one or more RLC bearers. It may consist of an ara. The RLC bearer of SRB1 may consist of an AM RLC entity and a logical channel. SRB2 is based on a terminal device in an RRC connection state with AS security activated. RRC signaling received from the ground station equipment may establish and / or configure one on the terminal equipment. SRB2 consists of one PDCP entity and one or more RLC bearers. This may be done. The RLC bearer of SRB2 may consist of AM's RLC entities and logical channels. Note that the PDCP on the base station equipment side of SRB1 and SRB2 may be located on the master node. When a secondary node is added in EN-DC, NGEN-DC, or NR-DC, SRB3 Alternatively, when the secondary node is changed, the RRC connection state with AS security activated. The terminal device receives RRC signaling from the base station device, and one connection is established to the terminal device. It may be configured as follows: SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 consists of one PDCP entity and one or more RLC bearers. This may be done. The RLC bearer of SRB3 may consist of the AM RLC entity and logical channel. The PDCP on the base station equipment side of SRB3 may be located on the secondary node. DRB is AS security One or more RLC bearers may be established and / or configured on a terminal device when the terminal device is in an RRC connection state with the utility activated by RRC signaling received from the base station device. The DRB may consist of one PDCP entity and one or more RLC bearers. The RLC entity may consist of an AM or UM RLC entity and a logical channel.

[0126] For RLC bearers established and / or configured in cell groups composed of E-UTRA, the established and / or configured RLC entities may be E-UTRA RLCs. Also composed of NR For RLC bearers established and / or configured in the cell group, establish and / or The RLC entity to be configured may be an NR RLC. When EN-DC is configured on the terminal device, the PDCP entity established and / or configured for the MN (Master Node) terminating MCG bearer i may be either E-UTRA PDCP or NR PDCP. Also, EN-DC is set on the terminal device. In this case, the PDCP established and / or set for other bearer types of wireless bearers, namely MN-terminated split bearers, MN-terminated SCG bearers, SN (Secondary Node)-terminated MCG bearers, SN-terminated split bearers, and SN-terminated SCG bearers, may be an NR PDCP. If NGEN-DC, NE-DC, or NR-DC is set for the end device, all bearer types will have The PDCP entity established and / or configured for the wireless bearer may be an NR PDCP.

[0127] In NR, a DRB established and / or configured on a terminal device is considered one PDU session. It may be linked to one PDU session in the terminal device. The entities may be established and / or configured. The SDAP entities, PDCP entities, RLC entities, and logical channels established and / or configured on the terminal device are based on the terminal device. It may be established and / or set by RRC signaling received from a local station.

[0128] The Reference Signal Received Power (RSRP) measured in the sidelink may be, for example, one of the following RSRPs. Furthermore, the following RSRP may be referred to as SL-RSRP. (a) PSBCH RSRP (b) PSSCH RSRP (c) PSCCH RSRP

[0129] PSBCH-RSRP (PSBCH RSRP) is a set of multiple demodulation reference signals associated with the PSBCH. Power supply of resource elements that transmit Reference Signal (DMRS) It may be defined as the linear average of the given (power contributions). Also, PSSCH-RSRP (PSSCH RSRP) may be defined as the linear average of the power contributions of resource elements of antenna ports transmitting multiple DMRS associated with PSSCH, and if there are multiple antenna ports, the RSRP values ​​for each antenna port may be summed up. PSCCH-RSRP (PSCCH RSRP) is related to PSCCH DMRS may be defined as the linear average of the power contributions of resource elements transmitting multiple interconnected DMRS. Note that DMRS is used, for example, to demodulate PSBCH, PSSCH, and PSCCH signals. It may be used. Furthermore, a terminal device that performs sidelink communication with another terminal device may use the PSSCH or PSCCH transmitted from the other terminal device to measure the RSRP (SL-RSRP) of the sidelink communication. Alternatively, the terminal device may measure the RSRP (SD-RSRP) of the discovery message using the power contribution of the resource element that transmits the DMRS associated with the discovery message.

[0130] Furthermore, in measurements at the side link, the UE122 may measure the following quantities in addition to SL-RSRP. (a) Sidelink received signal strength indicator (SL RSSI) (b) Sidelink channel occupancy ratio (SL CR) (c) Sidelink channel busy ratio(SL CBR)

[0131] The aforementioned SL RSSI is a line of power ([W]) observed in the configured subchannels within the OFDM symbols of the slots configured for PSCCH and PSSCH, starting from the second OFDM symbol. It may be defined as a shape average. Also, the SL CR in slot n is in slot [na] It may be defined as the sum of the number of subchannels used for sidelink transmission up to slot [n-1] and the number of subchannels allocated between slot [n] and slot [n+b], divided by the total number of subchannels set between slot [na] and slot [n+b]. Furthermore, the SL CBR in slot n is measured from the CBR measurement window (slot [na] to slot [n]). During the period set as -1), if the SL RSSI in the resource pool exceeds the threshold It can be defined as the proportion of subchannels.

[0132] The L2 U2N Remote UE may discover candidate L2 U2N Relay UEs, measure the RSRP of the candidate L2 U2N Relay UEs, and then report one or more candidate L2 U2N Relay UEs to the base station equipment. Furthermore, the L2 U2N Remote UE will report one or more candidate L2 U2N Relay UEs to the base station equipment. Before making a decision, check whether the measured RSRP of the candidate L2 U2N Relay UE meets the selection criteria for the L2 U2N relay. A determination of whether or not is made. The L2 U2N Remote UE may report only candidate L2 U2N Relay UEs that satisfy the selection criteria and conform to the criteria of the higher layer to the base station equipment. Furthermore, when the L2 U2N Remote UE reports one or more candidate L2 U2N Relay UEs to the base station equipment, the report to the base station equipment may include the identification information of the candidate L2 U2N Relay UE, the identification information of the serving cell of the candidate L2 U2N Relay UE, and the measurement results. Note that the measurement results include the candidate L2 U2N The RSRP (SD-RSRP) of the discovery message sent by the Relay UE may be used. The identification information may be an identifier (ID).

[0133] Furthermore, an L2 U2N Remote UE with a serving L2 U2N Relay UE will use the measurement results to determine the value of the serving L2 U2N Relay UE. RSRP (SL-RSRP) measured during sidelink communication with the serving L2 U2N Relay UE may be used. If SL-RSRP cannot be used in the measurement results, SD-RSRP may be used. The serving L2 U2N Relay UE may be an L2 U2N Relay UE that provides connectivity to the base station equipment for the L2 U2N Remote UE.

[0134] Next, we will explain the Serving Cell. In a terminal device with an RRC connection state (RRC_CONNECTED) in which one Serving Cell is configured, the Serving Cell may consist of one Primary Cell (PCell). Alternatively, multiple Serving Cells may be configured. In a terminal device with a defined RRC connection state, the serving cell has one or more specs A PCell may refer to a set of cells consisting of a Special Cell (SpCell) and one or more Secondary Cells (SCells). A SpCell may support PUCCH transmission and contention-based Random Access (CBRA). A PCell refers to a terminal device in the RRC_IDLE state. A PCell may be a cell used in the RRC connection establishment procedure when transitioning to a connected state. A PCell may also be a cell used in the RRC connection re-establishment procedure when a terminal device re-establishes the RRC connection. Furthermore, a PCell may be a cell used in the random access procedure during handover. Furthermore, SpCell may be a cell used for purposes other than those mentioned above.

[0135] If a group of serving cells configured for a terminal device consists of a SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device. Furthermore, for a terminal device with CA configured, a cell providing additional radio resources to a SpCell may be considered an SCell. .

[0136] This section describes cell groups, which are configured on terminal devices by base station equipment. A cell group may consist of one SpCell. Alternatively, a cell group may consist of one SpCell and one or more SCells. In other words, a cell group may consist of one SpCell And, as needed, it may consist of one or more SCells. A loop can be described as a set of cells.

[0137] UE122 may receive special cell (SpCell) settings from gNB102. For example, the RRCReconfiguration message contains cell group settings (an information element named CellGroupConfig). It may include, and the settings of the cell group are special cell settings (information named spCellConfig). It may include elements. spCellConfigDedic, which is contained within an information element named spCellConfig. The information element named "ated" is a cell setting specific to the UE122, configured in this SpCellConfig. It may be an information element that indicates [something]. The information element named spCellConfigDedicated may be rephrased as SpCellConfigDedicated or SpCell-specific settings. The information element named may include a parameter for the BWP identifier named firstActiveDownlinkBWP-Id, which will be described later. Furthermore, the settings for the special cell may also include a reconfiguration with synchronization (an information element named reconfigurationWithSync). Good. The spCellConfigCommon information element is included in the information element named reconfigurationWithSync. The information element with that name is cell-specific to the serving cell (i.e., special cell) of the UE122. It may be used to set parameters. In addition, the term "IE" may be added to indicate that a certain word is an information element. For example, a synchronized reset IE may be included in the RRC reset message, and the UE122 that receives the RRC reset message Alternatively, a synchronized reset (procedure) may be performed according to the RRC reset message.

[0138] This section describes notification messages in U2N relay. The relay terminal device uses the Uu interface. When RLF is detected on the face, when an RRC reset message containing synchronized reset information elements is received, when cell reselection is initiated, when an RRC connection failure (including RRC connection rejection) is detected, when T300 expires, or when the RRC restart procedure fails, the notification message is sent remotely. The notification may be sent to a terminal device. The relay terminal device may include a notification type in the notification message. The notification type may be set to a different value depending on the reason for initiating the transmission of the notification message, for example, it may indicate a wireless link failure in Uu or a PC5 link A wireless link failure may be indicated, or a failure of RRC reconfiguration may be indicated, The message may indicate a handover by a relay terminal device, a cell reselection by a relay terminal device, or other types. Upon receiving the notification message, the remote terminal device may initiate the RRC connection re-establishment procedure based on being in the RRC_CONNECCTED state. Furthermore, based on the determination to release the PC5 RRC connection with the relay terminal device, the higher-level You can also notify the PC5 unicast link to be opened, and the notification type is relayUE-HO. It may be considered that cell reselection was initiated based on this. The notification message may be a message named NotificationMessageSidelink or a message with a different name. It may also be sage. The notification type may be a message named IndicationType, or a message with any other name.

[0139] UE122, which performs sidelink transmission, uses sidelink grant (SL grant). The transmission is performed by the PDCCH transmitted by the base station equipment. It is either dynamically received, semi-persistently set by RRC signaling transmitted from the base station equipment, or automatically selected by the MAC entity of the terminal device. The MAC entity of the terminal device will automatically select the side link grant. The transmission mode is called Mode 2, the transmission mode in which sidelink grants are dynamically assigned by the PDCCH transmitted by the base station equipment, and the RRC signal received from the base station equipment. The side link grant is set semi-persistently by the signaling. The signal mode may be referred to as mode 1. The aforementioned mode 1 and mode 2 are... Each of these may be a sidelink resource allocation mode.

[0140] A terminal device capable of Sidelink communication may transmit a Sidelink terminal information message to the base station device. The Sidelink terminal information message may be a type of RRC message. Also, a terminal device in the RRC_CONNECTED state that is capable of sending and receiving discovery messages. The device, or a terminal device capable of U2N relay operation, a terminal device capable of U2U relay operation, a terminal device capable of sidelink positioning, or other operational terminal devices, may transmit the sidelink terminal information message to the base station device. The sidelink communication-capable terminal device may transmit and receive sidelink communications, transmit and receive discovery messages, and perform U2N relay operations. To show interest in U2U relay operation, SL-PRS transmission / reception, or other operations, The sidelink terminal information message may be transmitted to the base station device. The sidelink terminal information message may be a message used to notify the network of sidelink terminal information. The sidelink terminal information message may be transmitted if the connection with the base station device is successfully established or resumed, or if there is a change in interest, via QoS. If the file changes, if sidelink-related capability information is received from the associated peer UE, if RLC mode information is updated from the associated peer UE, sidelink If you switch to a PCell that provides SIB12 including common settings (sl-ConfigCommonNR), This may be sent when changing to a PCell that provides SIB23 including the drink positioning common setting (sl-PosConfigCommonNR). Also, Sidelink-enabled terminal devices request the assignment of a dedicated Sidelink DRB setting, and Sidelink communication transmission resources A terminal device capable of Sidelink communication may send the Sidelink terminal information message to request a resource allocation. A terminal device capable of Sidelink communication may also send the Sidelink terminal information message to report to the network (the base station device) that a Sidelink radio link failure, Sidelink RRC reconfiguration failure, Sidelink carrier failure, etc., has been declared. A terminal device capable of sending and receiving discovery messages may send the Sidelink terminal information message to request the allocation of a dedicated resource for sending and receiving discovery messages. A terminal device capable of U2N relay operation may use a U2N relay UE or U2N remote UE. The sidelink terminal information message may be sent to report or update parameters for fulfilling the role of a U2U relay UE or U2U remote UE. A terminal device capable of U2U relay operation may send the sidelink terminal information message to report or update parameters for fulfilling the role of a U2U relay UE or U2U remote UE. A link terminal information message may be sent. A terminal device capable of sidelink positioning may send the sidelink terminal information message to indicate whether it is interested in or no longer interested in either transmitting or receiving SL-PRS.

[0141] The terminal device may send the sidelink terminal information message when the SIB12, which includes the sidelink common settings, is provided by PCell. The terminal device may set several information elements in the sidelink terminal information message. The terminal device may include all relevant information (information elements) in the sidelink terminal information message regardless of the reason that triggered the transmission of the sidelink terminal information message. For example, it may include an information element indicating whether the terminal device is playing the role of a U2N relay UE or a U2N remote UE. The information element indicating whether the terminal device is playing the role of a U2N relay UE or a U2N remote UE may be an information element named ue-Type and may take the value relayUE or remoteUE. For example, the terminal device is configured such that the SIB12 includes L2U2N relay settings and the upper layer is configured to transmit U2N relay communication, and Based on the determination that the terminal device is acting as a U2N relay UE, the ue-Type may be included in the sidelink terminal information message, and the value of the ue-Type may be set to relayUE. For example, the terminal device may have SIB12 which includes L2U2N relay settings, and the higher layer may configure U2N relay communication. It is configured to transmit, and the terminal device is determined to be acting as a U2N remote UE. Based on this, the ue-Type may be included in the side link terminal information message, and the value of the ue-Type may be set to remoteUE. That is, the value of ue-Type relayUE may indicate that the terminal device is acting as a U2N relay UE, and the value of ue-Type remoteUE may indicate that the terminal device is acting as a U2N remote UE. In addition, The drink terminal information message may include information elements other than ue-Type. For example, side Information elements including an index of frequencies of interest for receiving link communications, an information element indicating the source L2ID used to establish a PC5 link with the target U2N relay UE, an information element containing parameters for requesting resources for transmitting sidelink communications (to the associated destination UE), an information element containing parameters for requesting resources for transmitting discovery messages, and an information element containing parameters for requesting transmission resources for U2N relay communications. It may include informational elements, or other informational elements. For example, U2 The parameters for requesting transmission resources for N relay communication are the destination for sidelink communication. Information indicating the L2ID, and one or more frequencies of interest for U2N relay communication transmission. This may include information indicating the DEX, a list of synchronization types associated with one or more frequency indices, information requesting the local ID of a U2N remote UE that has transitioned to RRC_CONNECTED or is in the RRC_CONNECTED state, a paging identifier received from a peer U2N remote UE, and information indicating the capability in sidelink communication received from a peer UE.

[0142] The aforementioned SIB12 may be a type of System Information Block (SIB) and may be set specifically for the cell or area transmitted via DL-SCH. The SIB12 is used for sidelink communication and It may also be a system information block that includes settings related to sending and receiving discovery messages. The SIB12 may include side link common settings, L2U2N relay settings, U2N Disk This may include information such as Coverage common settings, and other information may also be included. The aforementioned Sidelink common settings include settings related to sidelink transmission by mode2, and the frequency used. The settings may include the number of waves, wireless bearer settings, etc. The L2U2N relay settings may also be settings that indicate that the cell providing the SIB12 supports L2U2N relay operation. The above U2N Discovery common settings apply to the settings of the U2N relay UE and / or U2N remote UE. The configuration information may include fixed information, and this configuration information may include the setting of thresholds used for making decisions during discovery transmission and reception.

[0143] Based on the above description, various embodiments will be explained. Note that any processes omitted in the following description may be replaced by the processes described above.

[0144] Figure 5 is a block diagram showing the configuration of the terminal device (UE122) in this embodiment. Note that, to avoid making the explanation complicated, Figure 5 shows only the main components closely related to this embodiment. To show.

[0145] The UE122 shown in Figure 5 includes a receiving unit 500 that receives control information (SCI, MAC control elements, RRC signaling, etc.), discovery messages, user data, etc., from other terminal devices, and a processing unit 502 that processes according to the parameters contained in the received control information, etc. Control information (SCI, MAC control elements, RRC signaling, etc.) and discoverers are transmitted to other terminal devices. It includes a transmission unit 504 that transmits Barry messages, user data, and other information. The receiving unit 500 receives control information (MAC control elements, RRC signaling, etc.) from the base station equipment (gNB102). The transmitter 504 may also receive information including user data. The transmitter 504 may also transmit control information (MAC control elements, RRC signaling, etc.) and information including user data to the base station device (gNB102). Furthermore, the processing unit 502 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, PC5-S layer, Discovery layer, and application layer). That is, the processing unit 502 may include a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC The processing unit may include part or all of the following: RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, PC5-S layer processing unit, Discovery layer processing unit, and application layer processing unit.

[0146] Figure 6 is a block diagram showing the configuration of the base station device (gNB102) in this embodiment. To avoid making the explanation complicated, Figure 6 shows the main configurations closely related to this embodiment. Only the part is shown.

[0147] The base station device shown in Figure 6 consists of a transmitting unit 604 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to UE122, a processing unit 602 that creates control information (DCI, MAC CE, RRC signaling, etc.) and transmits it to UE122, causing the processing unit 502 of UE122 to perform processing, and a receiving unit 600 that receives control information (UCI, MAC CE, RRC signaling, etc.) from UE122. This may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 may include some of the functions of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit. It may include a part or the whole.

[0148] In a multi-hop U2N relay that provides connectivity to a base station device using multiple U2N relay UEs for a U2N remote UE, the U2N relay UE that has a direct path (Uu link) to the base station device among the multiple U2N relay UEs may be called the last relay UE, or simply the U2N relay UE. Among the relay UEs, the U2N relay UE that does not have a direct path to the base station equipment is referred to as the last relay To distinguish it from a relay UE, it may be referred to as an intermediate relay UE. The intermediate rel ay UE may establish a PC5 link (or unicast link, PC5-RRC) connection with an adjacent U2N remote UE, an adjacent other intermediate relay UE, or an adjacent last rel ay UE. In the multi-hop U2N relay, the U2N remote UE may establish a PC5 link (or unicast link, PC5-RRC) connection with the intermediate relay UE. The plurality of U2N relay UEs and the U2N remote UE may maintain an RRC connection with the base station device when in the RRC_CONNECTED state. Note that the U2N relay UE and the relay UE may be used interchangeably. Note that the U2N remote UE and the remote UE may be used interchangeably. Note that the U2N intermediate UE and the intermediate UE, and the intermediate rel ay UE may be used interchangeably.

[0149] An example of an embodiment in the present invention is shown using FIG. 10.

[0150] UE122 that communicates with the base station device makes a determination (step S1000) and operates based on the determination (step S1002).

[0151] In the determination in step S1000, for example, the UE122 may determine that the UE122 plays the role of an intermediate rel ay UE. Based on the UE122's determination that it plays the role of an intermediate relay UE, in the operation in step S1002, for example, the UE122 may include an information element indicating that the UE122 plays the role of an intermediate relay UE in the sidelink terminal information message. The information element may be included in the RRC message to indicate that the UE122 plays the role of an intermediate relay UE, or alternatively The information element is a variable that can take on multiple values, and by setting it to a specific value among the multiple values, it may indicate that the UE122 will play the role of an intermediate relay UE. Alternatively, the information element may be a parameter capable of storing multiple values, and the inclusion of a specific value in the information element may indicate that the UE122 is acting as an intermediate relay UE. good.

[0152] In addition to or instead of the above, in the determination in step S1000, for example, The UE122 may determine that it does not perform the role of an intermediate relay UE. Based on the determination by the UE122 that it does not perform the role of an intermediate relay UE, in the operation in step S1002, for example, the UE122 may determine that the UE122 is a remote UE Information elements indicating the role it plays may be included in the sidelink terminal information message. In addition to or instead of this, in the determination in step S1000, for example, UE122 may determine that UE122 does not play the role of an intermediate relay UE. Based on the determination by UE122 that UE122 does not play the role of an intermediate relay UE and the determination by UE122 that UE122 does not play the role of a remote UE, in the operation in step S1002, for example, UE122 may include information elements in the sidelink terminal information message indicating that UE122 plays the role of a remote UE.

[0153] In addition to or instead of the above, in the determination in step S1000, for example, The aforementioned UE122 may determine that some of the following conditions are met. (C-1) SIB12 includes L2U2N relay settings (C-2) The upper layer has configured the transmission of U2N relay communication. (C-3) The aforementioned UE122 is acting as a relay UE. (C-4) The aforementioned UE122 is acting as a remote UE. (C-5) SIB12 includes L2U2N multihop relay configuration (C-6) The aforementioned UE122 acts as an intermediate relay UE. (C-7) The upper layer has configured the transmission of U2N multihop relay communication. (C-8) The UE122 is not functioning as an intermediate relay UE.

[0154] For example, based on the UE122's determination that (C-1), (C-2), and (C-3) are satisfied, in the operation in step S1002, for example, the UE122 determines that the relay UE Information elements indicating the role of the terminal may be included in the side-link terminal information message.

[0155] In addition to or instead of the above, for example, if (C-1) and (C-2), (C-4) are satisfied, then Based on what UE122 has determined, in the operation in step S1002, for example, UE122 may include an information element in the sidelink terminal information message indicating that UE122 is playing the role of a remote UE. Alternatively, based on what UE122 has determined that conditions (C-1), (C-2), (C-4), and (C-8) are met, in the operation in step S1002, for example, UE122 may include an information element in the sidelink terminal information message indicating that UE122 is playing the role of a remote UE.

[0156] In addition to or instead of the above, for example, if (C-1) and (C-2), (C-6) are satisfied, then Based on the determination made by UE122, in the operation in step S1002, for example, UE122 may include an information element in the sidelink terminal information message indicating that UE122 is acting as an intermediate relay UE. Alternatively, for example, (C-1) and (C-6), (C-7) may be satisfied Based on the UE122's determination that the conditions are met, in the operation in step S1002, for example, the UE122 may include an information element in the sidelink terminal information message indicating that the UE122 is playing the role of an intermediate relay UE. Alternatively, based on the UE122's determination that conditions (C-5), (C-2), and (C-6) are met, in the operation in step S1002, for example, the UE122 may include an information element in the sidelink terminal information message indicating that the UE122 is playing the role of an intermediate relay UE. In the operation described above, for example, UE122 may include an information element in the sidelink terminal information message indicating that UE122 is playing the role of an intermediate relay UE. Alternatively, for example, based on the UE122's determination that (C-1), (C-7), and (C-6) are satisfied, in the operation in step S1002, for example, UE122 may play the role of an intermediate relay UE. Information elements indicating that a link is being added may be included in the side link terminal information message.

[0157] Furthermore, the information element indicating that UE122 is acting as an intermediate relay UE may be included in the sidelink terminal information message together with the information element indicating that UE122 is acting as a remote UE.

[0158] In addition to or instead of the above, the UE122 sends the aforementioned sidelink terminal information message Based on the decision of what type of UE to send the message as, the aforementioned information elements may be included in the sidelink terminal information message. For example, based on the decision to send the sidelink terminal information message as a remote UE, UE122 may take on the role of a remote UE. Information elements indicating that the side link terminal information message will be sent may be included in the side link terminal information message, or, for example, information elements indicating that the UE122 will act as a relay UE may be included in the side link terminal information message based on the decision to send the side link terminal information message as a relay UE. This may be included in the message, or, for example, based on the decision to send a sidelink terminal information message as an intermediate relay UE, the UE122 will perform the role of an intermediate relay UE. Information elements indicating this may be included in the sidelink terminal information message.

[0159] The L2U2N multihop relay configuration is such that the cell providing the SIB12 is an L2U2N multihop relay. The setting may indicate that it supports pre-lay operations. The UE122 may transmit the aforementioned side-link terminal information message to the base station device. The Sidelink terminal information message may be an RRC message named SidelinkUEInformation, or it may be an RRC message with a different name. In this embodiment, The SIB12, which is a system information block containing settings related to iDrink communication and / or the sending and receiving of discovery messages, is used as an example of implementing the use of a system information block. However, other system information blocks or RRC messages may be used instead of the SIB12 mentioned above.

[0160] The UE122, based on the fact that threshold information for the relay UE has not been set, It may be determined that the UE122 plays the role of, or in addition to or instead of, The UE122 may determine that it is acting as a relay UE based on the determination that the RSRP measurement result in the camping cell or the PCell of the UE122 is within the range of the threshold set by the threshold information. In addition or alternatively, the UE122 may determine that it is not acting as a relay UE based on the determination that the RSRP measurement result in the cell where the UE122 is camping or the PCell of the UE122 is outside the range of the threshold set by the threshold information. In addition or alternatively, the UE122 may determine that it is not acting as a relay UE based on the determination that the threshold for a remote UE is within the range of the threshold set by the threshold information. Based on the fact that no value information is set, it may be determined that the remote UE plays a role. In addition to or instead of this, the RSRP measurement result in the cell where the UE 122 camps or the PCell of the UE 122 is within the range of the threshold set by the threshold information. Based on the determination that the remote UE plays a role, it may be determined that the remote UE plays a role. In addition to or instead of this, based on the determination that the UE 122 has no serving cell. It may be determined that the remote UE plays a role. In addition to or instead of this, the UE 122 may be determined not to play the role of the remote UE based on the determination that the RSRP measurement result in the cell where the UE 122 camps or the PCell of the UE 122 is outside the range of the threshold set by the threshold information. In addition to or instead of this, the UE 122 may be determined to play the role of the intermediate UE based on the fact that no threshold information for the intermediate UE is set. It may be determined to play the role of the intermediate UE. In addition to or instead of this, the UE 122 camps. It may be determined to play the role of the intermediate UE based on the determination that the RSRP measurement result in the cell where the UE 122 camps or the PCell of the UE 122 is within the range of the threshold set by the threshold information. In addition to or instead of this, it may be determined to play the role of the intermediate UE based on the determination that it does not play the role of the relay UE. In addition to or instead of this, the UE 122 may be determined not to play the role of the intermediate UE based on the determination that the RSRP measurement result in the cell where the UE 122 camps or the PCell of the UE 122 is outside the range of the threshold set by the threshold information. In addition to or instead of this, the UE 122 may be determined not to play the role of the intermediate UE based on the determination that the UE 122 plays the role of the relay UE. [[ID=⑨]] [[ID=⑩]]

[0161] [[ID=⑪]] According to an example of this embodiment, in a multi-hop U2N relay, the base station device can appropriately identify the type of the UE that transmitted the RRC message.

[0162] Furthermore, in the above explanation, expressions such as "to be notified" and "to be pointed out" may be used interchangeably.

[0163] Furthermore, in the above explanation, expressions such as "link," "correspond," and "associate" may be used interchangeably.

[0164] Furthermore, in the above explanation, expressions such as "included," "included," and "was included" may be interchangeable.

[0165] Furthermore, in the above explanation, "the aforementioned..." may be replaced with "the aforementioned...".

[0166] Also, in the above explanation, the phrases "~ has been confirmed," "~ is set," and "~ is included" are used. These expressions may be interchangeable.

[0167] Furthermore, in the examples of processes or process flows described above, some or all of the steps may not be executed. Also, in the examples of processes or process flows described above, the order of the steps may differ. Furthermore, in the examples of processes or process flows described above, some or all of the processes within each step may not be executed. Furthermore, in the examples of processes or process flows described above, the order of the processes within each step may differ. Also, in the above description, "perform B based on the fact that A is true" may be rephrased as "perform B." That is, "performing B" is equivalent to "being true A." It may be executed independently.

[0168] Furthermore, in the above explanation, "A may be replaced with B" may include not only replacing A with B, but also replacing B with A. Also, in the above explanation, if it states "C may be D" and "C may be E", it may also include "D may be E". Also, in the above explanation, if it states "F may be G" and "G may be H", it may also include "F may be H".

[0169] Furthermore, in the above explanation, if condition "A" and condition "B" are contradictory, condition "B" may be expressed as an "other" condition of condition "A".

[0170] Furthermore, in the above explanation, "determining whether or not A is true" may also mean "determining that A is true," or "determining that A is not true." "Determining that A is not true" may also mean "not determining that A is true," and "determining that A is true" may also mean "not determining that A is not true."

[0171] The program running on the device according to this embodiment may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of this embodiment. The program or the information handled by the program may be temporarily loaded into volatile memory such as Random Access Memory (RAM) or flashed during processing. It is stored in non-volatile memory such as RAM or a Hard Disk Drive (HDD), and the CPU processes it as needed. This is how data is read, modified, and written.

[0172] Furthermore, some parts of the apparatus in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here refers to a computer system built into the apparatus, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of the following: a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0173] Furthermore, "computer-readable recording media" includes not only those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs over networks like the Internet or communication lines like telephone lines, but also those that hold programs for a fixed period of time, such as the volatile memory inside computer systems that act as servers or clients in such cases. That's fine. Also, the above program may be for the purpose of implementing some of the functions mentioned above, and may also be a program that already has the aforementioned functions recorded in the computer system. It is also acceptable if it can be achieved in combination with the above.

[0174] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, typically an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), and field-programmable circuits. This may include a multi-gate array (FPGA), other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, a conventional processor, controller, microcontroller, or state machine. The general-purpose processor, or each of the aforementioned circuits, may consist of digital or analog circuits. Furthermore, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, integrated circuits using such technologies may also be used.

[0175] It should be noted that this embodiment is not limited to the embodiments described above. Although the embodiments describe an example of a device, this embodiment is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0176] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not depart from the gist of this embodiment are also included. Furthermore, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. In addition, configurations in which elements described in the above embodiment that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

[0177] 100 ng-eNB 102 gNB 110, 112, 114 Interfaces 122 UE 200, 700 PHY 202, 702 MAC 204, 704 RLC 206, 706 PDCP 208, 708 RRC 210 PC5-S 310, 710 SDAP 400 safety 500, 600 Receiver 502, 602 processing unit 504, 604 Transmitter 712 NAS 800 SRAP

Claims

1. A terminal device that communicates with a base station device, Processing unit and It comprises a transmitting unit, Based on its determination that the terminal device is fulfilling the role of an intermediate relay UE, the processing unit includes an information element in the first message indicating that it is fulfilling the role of an intermediate relay UE. The transmitting unit transmits the first message to the base station device. Terminal device.

2. A method for a terminal device to communicate with a base station device, Based on the determination that the terminal device is fulfilling the role of an intermediate relay UE, the first message includes an information element indicating that it is fulfilling the role of an intermediate relay UE. The process includes the step of transmitting the first message to the base station device, method.

3. An integrated circuit mounted on a terminal device that communicates with a base station device, Based on the determination that the terminal device is fulfilling the role of an intermediate relay UE, the first message includes an information element indicating that it is fulfilling the role of an intermediate relay UE. Having a function to transmit the first message to the base station device, Integrated circuit.

Images