Terminal and method

Abstract

To provide an apparatus and a method in which a relay terminal temporarily stops relaying between a remote terminal and a base station.SOLUTION: In a communication system, a first terminal (relay terminal) serves to relay communication between a second terminal (remote terminal) and a base transceiver station, transmits a PC5RRC message including instruction information elements for suspending transmission of the second terminal to the second terminal, and realizes efficient communication control processing.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a terminal device and a method. [Background technology]

[0002] The 3G Partnership Project, a standardization project for cellular mobile communication systems, In the 3rd Generation Partnership Project (3GPP [registered trademark]), Technical studies and standardization of cellular mobile communication systems, including the base station, core network, and services, are underway.

[0003] For example, technical studies and standardization of E-UTRA (Evolved Universal Terrestrial Radio Access) have begun in 3GPP as a radio access technology (Radio Access Technology: RAT) for 3.9G and 4G cellular mobile communication systems. Currently, 3GPP is also conducting technical studies and standardization of E-UTRA extension technologies. E-UTRA is a Long Term It is also called LTE Evolution (registered trademark), and the extended technology is sometimes called LTE-Advanced (LTE-A) or LTE-Advanced Pro (LTE-A Pro).

[0004] In addition, 3GPP has begun technical studies and standardization of NR (New Radio, or NR Radio access) as a radio access technology (RAT) for cellular mobile communication systems for the 5th generation (5G). Technical studies and standardization are currently underway. [Prior art documents] [Non-patent literature]

[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 Summary of the Invention [Problem to be solved by the invention]

[0006] In 3GPP, as an extension technology of NR, a technology called sidelink (SL) has been studied, which allows terminal devices to communicate directly with each other without going through the core network. In addition, a technology called UE-to-Network Relay (U2N Relay) has been developed, in which a relay terminal device provides communication via sidelink, allowing terminal devices to communicate with a base station device via the relay terminal device, and service continuity in U2N Relay has been enhanced. Furthermore, a technology called UE-to-Network Relay (U2N Relay) has been developed, in which multiple relay terminal devices are connected in a row. Multi-hop relays have been investigated to enhance connectivity to remote terminals.

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

[0008] In order to achieve the above object, one aspect of the present invention takes the following measures.

[0009] (1) A first aspect of the present invention is a first terminal device that communicates with a base station device, comprising a processing unit and a transmission unit, wherein the first terminal device serves to relay communication between a second terminal device and the base station device, and the processing unit includes a first indication information element in a PC5 RRC message. The transmitting unit transmits the PC5 RRC message to the second terminal device, and The indication information element is an instruction information element for suspending transmission of the second terminal device.

[0010] (2) A second aspect of the present invention is a second terminal device that communicates with a base station device, comprising a processing unit and a receiving unit, wherein the second terminal device communicates with the base station device via a first terminal device, the receiving unit receives PC5 RRC signaling from the first terminal device, and the processing unit based on determining that the PC5 RRC signaling includes a first indication information element, and a second terminal device that suspends transmission of a radio bearer that terminates at the base station device.

[0011] (3) A third aspect of the present invention is a method for a first terminal device communicating with a base station device, wherein the first terminal device serves to relay communication between a second terminal device and the base station device, and includes the steps of including a first instruction information element in a PC5 RRC message and transmitting the PC5 RRC message to the second terminal device, wherein the first instruction information element is an instruction information element that suspends transmission of the second terminal device.

[0012] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. [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 drawings]

[0014] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Figure 2] A diagram showing an example of a protocol configuration for NR sidelink communication according to this embodiment. [Figure 3] A diagram showing an example of a protocol configuration for NR sidelink communication according to this embodiment. [Figure 4] FIG. 10 is a diagram showing an example of a protocol configuration in a discovery procedure according to the embodiment. [Figure 5] FIG. 2 is a block diagram showing the configuration of a terminal device according to the embodiment. [Figure 6] FIG. 2 is a block diagram showing the configuration of a base station device according to the present embodiment. [Figure 7] FIG. 1 is a diagram illustrating an example of a protocol configuration in NR according to this embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a protocol configuration of a control plane of an L2 U2N relay according to the embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of a protocol configuration of a user plane of an L2 U2N relay according to the embodiment. [Figure 10] 10 is an example of processing according to the present embodiment. [Figure 11] FIG. 2 is a diagram illustrating an example of a protocol configuration of a control plane of a multi-hop L2 U2N relay according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0016] In this embodiment, the names of the nodes and entities and the processes in the nodes and entities when the radio access technology is NR will be described, but this embodiment may be applied to other radio access technologies. The names of the nodes and entities in this embodiment may be different names.

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

[0018] E-UTRA may be a radio access technology. E-UTRA may also be an air interface between the UE 122 and the ng-eNB 100. The interface 112 may be referred to as a Uu interface. The ng-eNB (ng E-UTRAN Node B) 100 may be a base station device of the E-UTRAN. The ng-eNB 100 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol described below and the E-UTRA Control Plane (CP) protocol described below. The ng-eNB 100 The E-UTRA user plane protocol and the E-UTRA control plane protocol are transmitted to the UE 122. The radio access network consisting of eNBs may be called E-UTRAN.

[0019] NR may be a radio access technology. NR may also be an air interface between the UE 122 and the gNB 102. The air interface 112 between the UE 122 and the gNB 102 may be referred to as an air interface. The air interface 112 between the UE 122 and the gNB 102 may be referred to as a Uu interface. The gNB (g Node B) 102 may be an NR base station device. The gNB 102 may have the NR protocol described below. The NR protocol may be composed of an NR user plane (User Plane: UP) protocol described below and an NR control plane (Control Plane: CP) protocol described below. The gNB 102 transmits the NR user plane protocol and the NR control plane protocol to the UE 122. It may terminate the control plane protocol.

[0020] The interface 110 between the ng-eNB 100 and the gNB 102 may be referred to as an Xn interface. The ng-eNB and the gNB may connect to the 5GC via an interface called an NG interface (not shown). The 5GC may be a core network. One or more base station devices may connect to the 5GC via the NG interface.

[0021] The state in which a base station can be connected only via the Uu interface may be called Inside NG-RAN Coverage or In-Coverage (IC). The state in which it is not possible to connect to the device is called Outside NG-RAN Coverage or Out-of-Coverage (OoC). The air interface 114 between the UEs 122 may be referred to as a PC5 interface. Communication between the UEs 122 via the PC5 interface may be referred to as a sidelink (SL). Furthermore, a terminal device capable of performing sidelink communication may be referred to as a sidelink communication-capable terminal device.

[0022] In the following description, the ng-eNB 100 and / or the gNB 102 will also be referred to simply as a base station device, and the UE 122 will also be referred to simply as a terminal device or a UE. The PC5 interface will also be referred to simply as a PC5. The Uu interface is also referred to simply as Uu.

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

[0024] There are three transmission modes for NR SL communication, and SL communication is performed in one of the transmission modes by a pair of Source Layer-2 (L2) ID and Destination Layer-2 (L2) ID. The Source Layer-2 ID and Destination Layer-2 ID are respectively called Source L2ID. , may be referred to as destination L2 ID. The three transmission modes are "Unicast transmission", "Groupcast transmission", and "Broadcast The transmission mode may be referred to as a "broadcast type" or the like. 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, changed, or released according to application layer requests or communication requirements.

[0025] Unicast transmission is characterized by (1) support for one PC5-RRC connection between a paired UE, (2) transmission and reception of control information and user traffic between UEs on the sidelink, (3) support for sidelink HARQ feedback, (4) transmit power control on the sidelink, (5) support for RLC AM, and (6) radio link failure detection for the PC5-RRC connection.

[0026] Groupcast transmission is also performed between UEs belonging to a sidelink group. (1) Support for sidelink HARQ feedback. do.

[0027] In addition, broadcast transmission is performed for (1) sending and receiving user traffic between UEs on the sidelink. It is characterized by faith.

[0028] 2 and 3 are diagrams showing an example of a protocol architecture for NR sidelink communication according to this embodiment. Note that the functions of each protocol described using FIG. 2 and / or FIG. 3 are only some of the functions closely related to this embodiment, and other functions may also be included. Note that in this embodiment, a sidelink (SL) is a communication between terminal devices. It may be a link.

[0029] 2A is a diagram of a protocol stack of a control plane (CP) for SCCH using RRC, configured on a PC5 interface. As shown in FIG. 2A, the control plane protocol stack for SCCH using RRC includes a PHY (Physical layer) 200, which is a radio physical layer, a MAC (Medium Access Control) 202, which is a medium access control layer, a RLC (Radio Link Control) 204, which is a radio link control layer, and a packet data convergence protocol layer. PDCP (Packet Data Convergence Protocol) 206, which is the layer, and the radio resource control layer (radio The RRC 208 may be configured as a radio resource control layer. Also, 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 is The control plane protocol stack includes a PHY (Physical layer) 200, which is a wireless physical layer, a MAC (Medium Access Control) 202, which is a medium access control layer, an RLC (Radio Link Control) 204, which is a radio link control layer, and a Packet Data Convergence Protocol (PDCP) 206, which is a packet data convergence protocol layer, and a PC5 signaling layer (PC5 signaling layer) PC5-S (PC5 Signalling) 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 network may be configured from a PHY (Physical layer) 200, which is a wireless physical layer, a MAC (Medium Access Control) 202, which is a medium access control layer, a RLC (Radio Link Control) 204, which is a radio link control layer, and an RRC (Radio Resource Control) 208, which is a radio resource control layer. FIG. 3B is a diagram of the protocol stack of the user plane (UP) for the STCH configured on the PC5 interface. As shown in FIG. 3B, the control plane protocol stack for the STCH is made up of a PHY (Physical layer) 200, which is the wireless physical layer, a MAC (Medium Access Control) 202, which is the medium access control layer, and a IEEE 802.11a protocol stack. It may be composed of RLC (Radio Link Control) 204, which is a radio link control layer, PDCP (Packet Data Convergence Protocol) 206, which is a packet data convergence protocol layer, and SDAP (Service Data Adaptation Protocol) 310, which is a service data adaptation protocol layer.

[0031] The AS (Access Stratum) layer may be a layer including some or all of the PHY 200, MAC 202, RLC 204, PDCP 206, SDAP 310, and RRC 208. The PC5-S 210 and Discovery 400 described later may be layers higher than 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 respectively refer to 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. Note that when sidelink communication is performed using E-UTRA technology, the SDAP layer may not be required. To clarify that it is a protocol for sidelink, for example, RLC may be expressed as sidelink RLC, and other protocols may also be referred to with "sidelink," "SL," or "PC5" at the beginning. This may indicate that it is a protocol for sidelink.

[0033] In this embodiment, when distinguishing between E-UTRA protocols and NR protocols, 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. Furthermore, when distinguishing between E-UTRA protocols, sidelink protocols, and NR protocols, PHY, MAC, RLC, PDCP, and RRC are sometimes referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Furthermore, PHY, MAC, RLC, PDCP, and RRC are sometimes referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0034] For entities in the AS layer of E-UTRA, NR, and / or sidelink An entity that has some or all of the physical layer functions is called a PHY entity. An entity having some or all of the functions of the MAC layer may be called a MAC entity. An entity having some or all of the functions of the RLC layer may be called an RLC entity. An entity having some or all of the functions of the PDCP layer may be called a PDCP entity. An entity having some or all of the functions of the SDAP layer may be called an SDAP entity. An entity having some or all of the functions of the RRC layer The PHY entity, MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be referred to as PHY, MAC, RLC, PDCP, SDAP, and RRC, respectively. Furthermore, each entity in the AS layer is related to E-UTRA, NR, and and / or side links may be common entities or may be separate entities. It may also be a

[0035] Note that data provided to lower layers by MAC, RLC, PDCP, and SDAP, and / or MAC, RLC The data provided to MAC, RLC, PDCP, and SDAP from lower layers may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data provided to MAC, RLC, PDCP, and SDAP from higher layers and / or data provided from MAC, RLC, PDCP, and SDAP to higher layers may be called RLC PDU (Protocol Data Unit), PDCP PDU (PDCP PDU), and SDAP PDU (SDAP PDU). These data are called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. A segmented RLC SDU may be referred to as an RLC SDU segment.

[0036] Here, the base station device and the terminal device communicate with each other through the Uu interface via a higher layer (higher layer). A higher layer may be referred to as an upper layer, and the two may be interchangeable. For example, a base station device and a terminal device exchange signals in a Radio Resource Control (RRC) layer. The base station apparatus and the terminal apparatus may transmit and receive MAC control elements (also referred to as MAC CEs) in the MAC (Medium Access Control) layer. The RRC layer of the terminal apparatus may acquire system information broadcast from the base station apparatus. Here, RRC messages, system information, and / or MAC control elements are The event is a higher layer signal or a higher layer parameter. The data received by the terminal device is also called higher layer parameter. Each of the parameters included in the higher layer signal may be referred to as a higher layer parameter. For example, in PHY layer processing, the higher layer means a layer higher than the PHY layer, and may therefore mean one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, the higher layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0037] Furthermore, terminal devices also exchange (transmit and receive) signals at higher layers on the PC5 interface. Terminal devices may also transmit and receive RRC messages (also referred to as RRC signaling) at a Radio Resource Control (RRC) layer. Terminal devices may also transmit and receive RRC messages at a Medium Access Control (MAC) layer. In this case, MAC Control Element (MAC CE) may be transmitted and received. Here, RRC messages and / or MAC control elements are Each of the parameters included in the higher layer signal received by the terminal device may be referred to as a higher layer parameter. For example, PHY In layer processing, the upper layer refers to the upper layer from the perspective of the PHY layer, and may 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 the layer processing, the upper layer may refer to one or more of the RRC layer, the RLC layer, the PDCP layer, the PC5-S layer, the Discovery layer, etc.

[0038] Hereinafter, the meaning of "A is given (provided) by an upper layer" or "A is given (provided) by an upper layer" may mean that an upper layer (mainly an RRC layer, a MAC layer, etc.) of a terminal device receives A from a base station device or another terminal device, and the received A is given (provided) to a physical layer of the terminal device from the upper layer of the terminal device. For example, in a terminal device, "being provided with an upper layer parameter" may mean receiving an upper layer signal from a base station device or another terminal device, and providing an upper layer parameter included in the received upper layer signal from the upper layer of the terminal device to the physical layer of the terminal device. Setting an upper layer parameter in a terminal device may mean that the upper layer parameter is given (provided) to the terminal device. For example, setting an upper layer parameter in a terminal device may mean that the terminal device receives an upper layer signal from a base station device or another terminal device, and setting the received upper layer parameter in the upper layer. However, setting an upper layer parameter in a terminal device may include setting a default parameter that is given in advance to an upper layer of the terminal device. When describing the transmission of an RRC message from a terminal device to a base station device or another terminal device, the expression "submitting a message from the RRC entity of the terminal device to a lower layer" is sometimes used. This may mean submitting a message to the PDCP layer. In this context, "submitting a message to a lower layer" may mean submitting the message to a PDCP entity corresponding to each SRB, since the RRC message is transmitted using an SRB (SRB0, SRB1, SRB2, SRB3, etc.). When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0039] An example of the PHY function will be explained. The PHY of a terminal device can communicate with the PHY of other terminal devices. Sends and receives data transmitted via the sidelink (SL) physical channel The PHY may be connected to the upper MAC via a transport channel. The PHY may pass data to the MAC via the transport channel. The PHY may also receive data from the MAC via a transport channel. In this case, a Radio Network Temporary Identifier (RNTI) may be used to identify various pieces of control information.

[0040] Here, the physical channels will be described. The physical channels used for wireless communication between a terminal device and another terminal device may include the following physical channels.

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

[0042] The PSBCH may be used to broadcast system information required by the terminal device.

[0043] The PSCCH may be used to indicate resources and other transmission parameters for the PSSCH.

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

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

[0046] An example of the functions of MAC will be described. MAC may be called MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. A logical channel may be identified by a logical channel identity (or logical channel ID). MAC may be connected to a higher RLC via a logical channel. Depending on the type of information to be transmitted, logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information. MAC may be configured to handle one or more different logical channels. The MAC may have a function to multiplex MAC SDUs belonging to a logical channel and provide them to the PHY. The MAC may also have a function to demultiplex MAC PDUs provided by the PHY and provide them to a higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a function to report scheduling information. MAC has a function to perform priority processing among terminal devices using dynamic scheduling. MAC should also have a function to perform priority processing between logical channels within one terminal device. MAC has the function of prioritizing overlapping resources within a single terminal device. E-UTRA MAC has the function to identify Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have the ability to identify Multicast / Broadcast Services (MBS). The MAC is The MAC may have the function of performing discontinuous reception (DRX) and / or discontinuous transmission (DTX), the function of performing random access (RA) procedures, the function of reporting information on available transmission power, and the function of selecting a power header. Power Headroom Report (PHR) function, which notifies the amount of data in the transmission buffer. The NR MAC may have a Bandwidth Adaptation (BA) function. The MAC PDU format used in the NR MAC may be different from that used in the MAC. The MAC PDU also contains a MAC control element (MAC control element) for controlling the MAC. The MAC address may include a MAC rule element (MAC CE).

[0047] In addition, the MAC sublayer may provide additional services and functions over the PC5 interface, such as radio resource selection for selecting radio resources for sidelink transmission, filtering of packets received in sidelink communication, priority processing between uplink and sidelink, and reporting of sidelink channel state information (Sidelink CSI).

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

[0049] SBCCH (Sidelink Broadcast Control Channel) transmits sidelink system information in one The SBCCH may be a sidelink logical channel for broadcasting from a terminal device to one or more terminal devices. The SBCCH may be mapped to the SL-BCH, which is a sidelink transport channel. It may be tagged.

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

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

[0052] An example of the RLC function will be described below. The RLC may be called an RLC sublayer. The E-UTRA RLC may have the function of segmenting and / or concatenating data provided from the PDCP of the upper layer and providing it to the lower layer. The E-UTRA RLC may perform reassembly and reordering of the data provided from the lower layer. NR RLC may have the function of re-ordering and providing it to higher layers. The NR RLC may have a function to add a sequence number to data provided by PDCP in the layer that is independent of the sequence number added by PDCP. The NR RLC may also have a function to segment data provided by PDCP and provide it to a lower layer. The NR RLC may also have a function to reassemble data provided by a lower layer and provide it to a higher layer. The RLC may also have a function to retransmit data and / or request retransmission (Automatic The RLC may have a Repeat reQuest (ARQ) function. The RLC may also have a function to perform error correction using ARQ. The control information sent from the receiving side of the RLC to the transmitting side to indicate the data that needs to be retransmitted may be called a status report. The control information sent from the transmitting side of the RLC to the receiving side may also be called a status report. The instruction to send a status report can be called a poll. The RLC may have a function to detect data duplication. The RLC may also have a function to discard data. The RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The TM does not divide data received from the upper layer, and does not need to add an RLC header. The TM RLC entity The entity is a uni-directional entity, and the transmitting TM RLC element The UM may be configured as a receiving entity or as a receiving TM RLC entity. The UM performs the division and / or concatenation of data received from higher layers, adds RLC headers, etc. The UM RLC entity may be either a unidirectional entity or a bidirectional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UM RLC entity. If the UM RLC entity is a bidirectional entity, the UM RLC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. The AM RLC entity may perform operations such as segmenting and / or combining data received from an upper 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. Note that the data provided to the lower layer by TM and / or the data provided by the lower layer The data provided to and / or from a lower layer in UM may be called a UMD PDU. The data provided to and / or from a lower layer in AM may be called a UMD PDU. Data provided by the E-UTRA RLC or a lower layer may be called an AMD PDU. The RLC PDU format used in NR RLC may be different from the RLC PDU format used in NR RLC. RLC PDUs may include data RLC PDUs and control RLC PDUs. Data RLC PDUs may be called RLC DATA PDUs (RLC Data PDUs). Control RLC PDUs may be called RLC CONTROL PDUs (RLC Control PDUs). The control RLC PDU used to transmit the status report may be called a status PDU.

[0053] In addition, in the sidelink, TM may be used for SBCCH, and groupcast Only UM is used for groupcast and broadcast transmission, while both UM and AM are available for unicast transmission. In the sidelink, UM for groupcast and broadcast transmission only supports one-way transmission.

[0054] An example of the function of PDCP will be explained. PDCP may be called a PDCP sublayer. PDCP may have a function to maintain sequence numbers. PDCP also allows efficient transmission of user data such as IP packets and Ethernet frames over wireless sections. The protocol used for header compression and decompression of IP packets may be called ROHC (Robust Header Compression) protocol. The protocol used for Ethernet frame header compression and decompression is EHC (Ethernet (registered trademark) PDCP may be called the PDCP (Data Header Compression Protocol). PDCP may also have a data encryption / decryption function. PDCP may also have a data integrity protection / verification function. PDCP may also have a re-ordering function. PDCP may also have a PDCP SDU retransmission function. PDCP may also have a data discard function using a discard timer. PDCP may also have a duplication function. PDCP may also have a function to discard duplicated received data. The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from that used in NR PDCP. PDCP PDUs may also include There may be data PDCP PDUs and control PDCP PDUs. Data PDCP PDUs may be called PDCP DATA PDUs (PDCP Data PDUs). Control PDCP PDUs may be called PDCP CONTROL PDUs (PDCP Control PDUs).

[0055] In addition, the following restrictions apply to PDCP functions and services in Sidelink: (1) Out-of-order delivery is supported only for unicast transmission. That's fine. (2) Duplication over the PC5 interface is not supported.

[0056] An example of the SDAP function is explained below. SDAP is a service data adaptation protocol layer (SDAP). In the sidelink, SDAP is a data adaption protocol layer (SDAP). The sidelink QoS flow (PC5 QoS flow) and sidelink data sent from the PC to other terminal devices are The SDAP may have a function to map the QoS flow identifier (QoS) to the corresponding Data Radio Bearer (DRB). The SDAP may also have a function to store mapping rule information. Flow ID: QFI) and PC5 QoS Flow Identifier (PC5 QoS Flow ID: PQFI or PFI) marking The SDAP PDU may have a function to perform control. There may be a data SDAP PDU and a control SDAP PDU. The data SDAP PDU is called an SDAP DATA PDU (SDAP Data PDU). Also, the SDAP PDU for control can be called SDAP CONTROL PDU (SDAP Control PDU). In the sidelink, the SDAP entity of the terminal device is called the SDAP control PDU. The property is a unicast transmission, a groupcast transmission associated with a destination. There may be one per destination for either QoS, QoS, or broadcast transmissions. Also, reflective QoS is not supported on PC5 interfaces.

[0057] An example of the RRC function is described below. RRC is a communication system between peer UEs on the PC5 interface. The PC5-RRC protocol may support services and functions such as forwarding PC5-RRC messages, maintaining and releasing a PC5-RRC connection between two UEs, and detecting sidelink radio link failures for a PC5-RRC connection. A PC5-RRC connection is a logical connection between two UEs corresponding to a pair of source L2ID and destination L2ID, and is considered established after the corresponding PC5 unicast link is established. There is a one-to-one correspondence between a PC5-RRC connection and a PC5 unicast link. A UE may have multiple PC5-RRC connections to one or more UEs for different pairs of source L2ID and destination L2ID. Separate PC5-RRC procedures and messages may be used by a UE to forward UE capabilities and sidelink configuration to a peer UE. Both peer UEs may also exchange their UE capabilities and sidelink configuration with each other using a separate bidirectional procedure. If they are not interested in sidelink transmission, they may use the sidelink configuration for the PC5-RRC connection. When a link radio link failure is detected and the Layer 2 link release procedure is completed If so, the UE releases the PC5-RRC connection.

[0058] A UE performing sidelink transmission may transmit a PSCCH and a PSSCH in association with each other. Note that sidelink transmission is performed via a physical channel for sidelink (such as a PSBCH, PSSCH, or PSCCH). It may transmit signals and / or data (messages) or receive sidelink signals. The receiver receives signals and / or data (messages) via a physical channel for the side link. Alternatively, 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 PSCCH (a PSCCH) transmission. The PSCCH transmission may carry 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 the PSCCH transmission may include the first SCI, and the PSSCH transmission may include the second SCI. In addition, PSCCH transmission and PSSCH transmission may be referred to as sidelink transmission, and SCI is a sidelink The first SCI may be control information (Sidelink Control Information). The first SCI may include 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 information such as data priority, frequency and time resources on which the PSSCH is transmitted, resource reservation period, DMRS allocation pattern, second SCI format, beta offset indication value, number of DMRS ports, modulation The SCI carried on the PSSCH may include information such as information indicating a sidelink scheduling scheme and a coding scheme, and other information. In addition, the SCI carried on the PSSCH may be a second SCI, and the second SCI may include sidelink scheduling information and / or information related to inter-UE coordination. The second SCI may be SCI Format 2-A, SCI Format 2-B, or or 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 the data is new, a redundancy version, a source ID for identifying a source UE, a destination ID for identifying a destination UE, and information indicating whether HARQ feedback is possible. Furthermore, the SCI format 2-A may additionally include information indicating a cast type and information indicating whether or not channel state information (CSI) is required. Format 2-B may additionally include a zone identifier and required information regarding communication range. Furthermore, SCI format 2-C may additionally include information indicating whether to request channel state information and information indicating whether to provide or request inter-UE coordination information. When SCI format 2-C includes information providing inter-UE coordination information, SCI format 2-C may additionally include information such as information indicating a resource combination, information indicating the first resource position, information on the position of a reference slot, information indicating the type of resource set, and the lowest subchannel index. When SCI format 2-C includes information requesting inter-UE coordination information, SCI format 2-C may additionally include information such as priority, the number of subchannels, a resource reservation interval, the position of a resource selection window, and information indicating the type of resource set. Each SCI format may include information other than the above information. .

[0059] Next, the procedure for a UE to receive a PSSCH will be described. When a UE detects SCI format 1-A on a PSCCH, it can decode the PSSCH according to the detected SCI format 2-A or SCI format 2-B and the associated PSSCH resource configuration configured by a higher layer. Note that a UE may decode more than one PSCCH for each PSCCH resource candidate. In addition, if the UE does not support the modulation and coding scheme indicated in SCI Format 1-A, it does not need to decode the corresponding SCI Format 2-A and SCI Format 2-B and the PSSCH associated with SCI Format 1-A.

[0060] In addition, if the UE is configured in the upper (RRC) layer with a parameter indicating whether the DMRS used for L1 RSRP measurement during the sensing operation is the DMRS of the PSCCH or the DMRS of the PSSCH, Measure the PSSCH RSRP from the DMRS resource element for the PSSCH associated with the received SCI format 1-A, and if the PSCCH is configured, The PSCCH RSRP may be measured from the DMRS resource elements for the PSCCH RSRP.

[0061] A terminal device capable of sidelink communication may perform discovery. Discovery may be performed in Model A or Model B. Figure 4 shows the protocol for the discovery procedure. The stack is described below. Mode A may use a single discovery protocol message, and Model B may use two discovery protocol messages. A discovery protocol message in Model B may be an announcement message, and a discovery protocol message in Model B may be a solicitation message. The Announce message, Solicit message, and Response message may be collectively referred to as Discovery message, and other messages used in the discovery procedure may also be referred to as Discovery messages. Below is an outline of the procedures for Model A and Model B in ProSe Direct Discovery.

[0062] In Model A, a UE that transmits an announcement message may be called an announcing UE, and a UE that monitors the announcement message may be called a monitoring UE. The Announce message may contain information such as the discovery message type, ProSe Application Code or ProSe Restricted Code, security protection element, and may additionally contain metadata information. The Announce message may contain the Destination Layer-2 ID and Source Layer-2 ID. The Announce message is transmitted using the Destination L2ID, and the monitoring UE determines a Destination L2ID for receiving the Announce message. Note that the Destination L2ID may be a Layer-2 identifier of the destination UE, and the Source L2ID may be a Layer-2 identifier of the source UE. The Destination UE may be simply referred to as the Destination.

[0063] In Model B, a UE that sends an invitation message may be called a discoverer UE. Instead, a UE that receives an INVITE message and / or a UE that sends a response message to a discoverer UE may be referred to as a discoveree UE. The INVITE message may include information such as a discovery message type, a ProSe Query Code, and a security protection element. The INVITE message is sent using a destination L2 ID and a source L2 ID, and the discoveree UE determines the destination L2 ID to receive the INVITE message. A discoveree UE that responds to the INVITE message sends a response message. The response message may include information such as a discovery message type, a ProSe Response Code, and a security protection element, and may also include metadata information. The response message is sent using the source L2 ID, and the destination L2 ID is set to the source L2 ID of the received INVITE message.

[0064] Discovery may include types other than ProSe Direct Discovery, which discovers other UEs in order to communicate directly with them, such as Group Member Discovery, which discovers one or more UEs in order to communicate within a group using a sidelink, and 5G ProSe UE-to-Network Relay Discovery, which discovers candidate relay UEs in order to connect to the network via a relay UE. Note that the above-mentioned discovery is implemented using an application called ProSe. In addition to the above-mentioned examples of discovery provided by the application, different types of discovery may exist depending on the application or service performing sidelink communication. Furthermore, depending on the type of discovery, the information included in the discovery protocol message may differ, or additional messages may be sent to transmit additional information.

[0065] FIG. 4 is a diagram showing an example of a protocol configuration including a discovery protocol according to this embodiment. As shown in Figure 4, the discovery plane, including the discovery protocol, The protocol stack includes a PHY (Physical layer) 200, which is a wireless physical layer, a MAC (Medium Access Control) 202, which is a medium access control layer, and a wireless The RLC 204 may be a radio link control layer, a PDCP 206 may be a packet data convergence protocol layer, and a Discovery 400 may be a discovery protocol layer. The interface between UEs that perform discovery may be referred to as PC5-D.

[0066] A plurality of resource pools may be set up for transmitting messages (discovery messages) used in discovery procedures. One or more resource pools may be configured exclusively for discovery. If a resource pool dedicated to discovery is configured, the UE may use the resource pool dedicated to discovery as the resource pool for transmitting discovery messages. If a resource pool dedicated to discovery is not configured, the UE may use the resource pool for sidelink communication as the resource pool for transmitting discovery messages. Note that multiple resource pools for sidelink communication and multiple resource pools dedicated to discovery may be configured simultaneously. Each resource pool may be configured by UE-dedicated signaling or may be configured in advance.

[0067] For 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. The sidelink SRB used to transmit PC5-S messages for establishing the PC5-S security may be referred to as SL-SRB1. After the PC5-S security is established, the protected A sidelink SRB used to transmit PC5-S messages may be referred to as SL-SRB2. A sidelink SRB used to transmit protected PC5-RRC signaling after PC5-S security is 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 over PC5. Note that PC5-RRC signaling is a signal that is transmitted between UEs over PC5. It may also be called sage.

[0068] Here, we will explain UE-to-Network (U2N) relay. U2N relay is a relay that relays a remote terminal device. The U2N relay may be a function that provides network connectivity to a remote terminal device (UE). A remote terminal device that connects to a network using a U2N relay may be referred to as a U2N Remote UE. In addition, a terminal device that provides network connectivity to a U2N Remote UE may be referred to as a U2N relay terminal device (Relay UE), or simply as a relay terminal device (Relay UE). A U2N Relay UE may use a Uu interface for communication with a base station device, and may also use a Uu interface for communication with a U2N Remote UE. A PC5 interface may be used for transmission. U2N relays may be classified into Layer 2 (L2) U2N relays and Layer 3 (L3) U2N relays. A remote terminal device in an L2 U2N relay may be particularly referred to as an L2 U2N Remote UE, and a relay terminal device in an L2 U2N relay may be particularly referred to as an L2 U2N Relay UE. In an L2 U2N relay, a side link relay may be applied. The SRAP (SRAP layer) 800 is a Sidelink Relay Adaptation Protocol (SRAP) layer. The SRAP 800 may be simply referred to as the SRAP.

[0069] FIG. 8 is a diagram showing an example of a protocol configuration of a control plane (C-plane) of an L2 U2N relay, including an SRAP layer (SRAP 800) according to this embodiment. Also, FIG. 9 is a diagram showing an example of a protocol configuration of a user plane (U-plane) of an L2 U2N relay, including an SRAP layer according to this embodiment. As shown in FIGS. 8 and 9, the SRAP layer may be associated between a Remote UE and a Relay UE, and may also be associated between a Relay UE and a gNB 102. Note that the gNB 102 shown in FIGS. 8 and 9 is an ng-eNB 100. The Remote UE or the Relay UE may be the UE 122. The Relay UE may have the same configuration as the UE 122.

[0070] The SRAP layer will now be described. The SRAP layer may also be called the SRAP sublayer, or simply the SRAP. The SRAP sublayer handles the control plane and user interface for both the PC5 and Uu interfaces. The SRAP sublayer on PC5 may be used for bearer mapping purposes. In L2 U2N Relay UE, the SRAP sublayer is used on the Uu interface. In an L2 U2N Remote UE, the SRAP sublayer may include only one SRAP entity on the PC5 interface. The SRAP entity associated between the Remote UE and the Relay UE via the PC5 interface is specifically referred to as PC5-SRAP. Alternatively, an SRAP entity associated between a Relay UE and a gNB via Uu may be specifically referred to as a Uu-SRAP. In addition, to clarify the interface name, 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 the SRAP entity of the L2 U2N Remote UE may be associated with the receiver of the SRAP entity of the L2 U2N Relay UE, and the receiver of the SRAP entity of the L2 U2N Remote UE may be associated with the receiver of the SRAP entity of the L2 U2N Relay UE. It may be associated with the transmitter of the SRAP entity of the Relay UE. In the above, the transmitter of the SRAP entity of the L2 U2N Relay UE is connected to the SRAP entity of the gNB102. The receiving unit of the SRAP entity of the L2 U2N Relay UE may be associated with the transmitting unit of the SRAP entity of the gNB102.

[0071] The SRAP entity also has the functions of forwarding data, determining the UE ID field and bearer ID field of the SRAP header to be added to the data packet, and determining the exit link. The RLC channel determining function may include: determining an egress RLC channel;

[0072] Also, in Figures 8 and 9, a PC5 Relay RLC channel may be established between the Remote UE and the Relay UE, and a Uu Relay RLC channel may be established between the Relay UE and the gNB102.

[0073] Next, we will explain multi-hop relay. A multi-hop relay may be a U2N relay in which multiple relay terminal devices are involved in one path from a remote terminal device to a gNB102. Figure 11 is an example of a C-plane protocol stack in a multi-hop relay. For example, of the multiple relay terminal devices, a relay terminal device that is directly connected to the gNB102 via the Uu interface may be referred to as a last relay terminal device (MH U2N Last Relay UE in Figure 11), and of the multiple relay terminal devices, relay terminal devices other than the last relay terminal device (UEs belonging to the dotted line part including the MH U2N First Relay UE in Figure 11) may be referred to as intermediate relay terminal devices. The intermediate relay terminal device may be referred to as a first relay terminal device, a second relay terminal device, a third relay terminal device, etc. in order of hop proximity to the remote terminal device. The plurality of relay terminal devices may be terminal devices that provide connectivity to the remote terminal device with a gNB. The names of the terminal devices mentioned above are examples and are not limited to these. This is an 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, an SDAP layer may be used instead of the RRC layer in the figure. In addition, in a multi-hop relay, if the node at 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 at which the link with the remote UE terminates is a UE, it may be called a multi-hop U2U relay.

[0074] Next, the protocol configuration used between the base station device and the terminal device will be described. In the communication performed over the Uu interface between the relay terminal device and the base station device, and in the communication performed between the remote terminal device and the base station device via the relay terminal device, the protocol used between the base station device and the terminal device may be used. Note that in the communication performed between the remote terminal device and the base station device via the relay terminal device, some protocols may not be associated between the remote terminal device and the base station device.

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

[0076] 7A is a diagram of the NR control plane (CP) protocol stack. As shown in FIG. 7A, the NR CP protocol may be a protocol between the UE 122 and the gNB 102. That is, the NR CP protocol is , and on the network side, it may be a protocol that terminates at the gNB 102. As shown in Figure 7(A), the NR control plane protocol stack includes a PHY (Physical layer) 700, which is a radio physical layer, a MAC (Medium Access Control) 702, which is a medium access control layer, an RLC 704, which is a radio link control layer, and a packet data convergence (PDC) 706. It may be composed of a PDCP (Packet Data Convergence Protocol) 706, which is a protocol layer (packet data convergence protocol layer), and an RRC (Radio Resource Control) 708, which is a radio resource control layer. Also, FIG. 7(B) shows the NR user plane (UP) plane. As shown in Figure 7(B), the NR UP protocol may be a protocol between the UE 122 and the gNB 102. That is, the NR UP protocol terminates at the gNB 102 on the network side. As shown in FIG. 7B, the NR user plane protocol stack includes a PHY 700, which is a radio physical layer, a MAC 702, which is a medium access control layer, a RLC 704, which is a radio link control layer, a PDCP 706, which is a packet data convergence protocol layer, and a service data It may be configured with an SDAP (Service Data Adaptation Protocol) 710, which is an adaptation protocol layer (service data adaptation protocol layer).

[0077] The AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the gNB 102. The AS layer includes some or all of PHY 700, MAC 702, RLC 704, PDCP 706, and RRC 708. The gNB 102 may be a ng-eNB 100. ... However, the E-UTRA protocol may also be used. may not exist, and the E-UTRA protocol may have some different functions from the NR protocol.

[0078] In the present 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 respectively refer to 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. Furthermore, SDAP (SDAP layer) may refer to the SDAP (SDAP layer) of the NR protocol.

[0079] In this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, the PHY 500, the MAC 502, the RLC 504, the PDCP 506, and the RRC 508 are referred to as the PHY for E-UTRA or the PHY for LTE, the MAC for E-UTRA or the MAC for LTE, the RLC for E-UTRA or the RLC for LTE, and the PDCP for E-UTRA or the LTE The PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 are sometimes referred to as the E-UTRA PHY or LTE PHY, and the E-UTRA MAC or LTE RRC, 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. Also, a distinction is made between E-UTRA protocols and NR protocols. In this case, the PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. The PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 may also be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0080] Describes the entities in the AS layer of E-UTRA and / or NR. An entity that has some or all of the functionality of the MAC layer may be called a PHY entity. An entity that has some or all of the functionality of the MAC layer may be called a MAC entity. An entity having some or all of the functions of the RLC layer may be called an RLC entity. An entity having some or all of the functions of the PDCP layer may be called a PDCP entity. An entity having some or all of the functions of the SDAP layer may be called an SDAP entity. An entity having 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 PHY, MAC, RLC, PDCP, SDAP, and RRC entities are referred to as PHY, MAC, RLC, PDCP, SDAP, and RRC, respectively. You can replace it.

[0081] Note that data provided to lower layers by MAC, RLC, PDCP, and SDAP, and / or MAC, RLC The data provided to MAC, RLC, PDCP, and SDAP from lower layers may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data provided to MAC, RLC, PDCP, and SDAP from higher layers and / or data provided from MAC, RLC, PDCP, and SDAP to higher layers may be called RLC PDU (Protocol Data Unit), PDCP PDU (PDCP PDU), and SDAP PDU (SDAP PDU). These data are called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. A segmented RLC SDU may be referred to as an RLC SDU segment.

[0082] Here, the base station device and the terminal device transmit signals in a higher layer. The higher layer can be called the upper layer, and they are interchangeable. For example, the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC signaling) in a Radio Resource Control (RRC) layer. The base station apparatus and the terminal apparatus may also transmit and receive MAC control elements in the MAC (Medium Access Control) layer. The RRC layer of the terminal apparatus acquires system information broadcast from the base station apparatus. Here, the RRC message, the system information, and and / or the MAC control element receives higher layer signaling (higher layer signaling). A parameter included in a higher layer signal received by a terminal device may be referred to as a higher layer parameter. Each parameter included in a higher layer signal received by a terminal device may be referred to as a higher layer parameter. For example, in PHY layer processing, a higher layer refers to a layer higher than the PHY layer, and may therefore refer to one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, an NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, a higher layer may refer to one or more of an RRC layer, an RLC layer, a PDCP layer, an NAS layer, etc.

[0083] Hereinafter, "A is given (provided) by an upper layer" or "A is given (provided) by an upper layer" means that an upper layer (mainly an RRC layer or a MAC layer) of the terminal device receives A from the base station device, and the received A is given (provided) by the upper layer of the terminal device to the physical layer of the terminal device. For example, it may mean that "higher layer parameters are provided" in a terminal device. "Provided" may mean receiving an upper layer signal from a base station device, and providing upper layer parameters included in the received upper layer signal 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 providing (providing) upper layer parameters to the terminal device. 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, and the upper layer sets the received upper layer parameters. However, setting upper layer parameters in a terminal device may also include setting default parameters that are provided in advance to the upper layer of the terminal device. When describing transmission of an RRC message from a terminal device to a base station device, the expression "submitting a message from the RRC entity of the terminal device to a lower layer" is sometimes used. In the terminal device, when an RRC entity "submits a message to a lower layer," In the terminal device, "submitting a message to a lower layer" from the RRC layer may mean submitting a message to the PDCP layer. Since RRC messages are transmitted using SRBs (SRB0, SRB1, SRB2, SRB3, etc.), the PDCP message corresponding to each SRB must be transmitted. It may also mean that the RRC entity of the terminal device submits the request to the lower layer. When receiving an indication from the PHY layer, the lower layer, such as the MAC layer, the RLC layer, the PDCP layer, etc. It may mean one or more.

[0084] An example of the function of the PHY is explained below. The PHY of the terminal device receives the downlink from the PHY of the base station device. Receives data transmitted via a Downlink (DL) physical channel. The PHY of the terminal device may have an uplink (UL) object function with respect to the PHY of the base station device. The PHY may have a function to transmit data via a transport channel. The PHY may be connected to the upper MAC via a transport channel. The PHY may pass data to the MAC via the transport channel. The PHY may also receive data from the MAC via the transport channel. In the PHY, a Radio Network Temporary Identifier (RNTI) may be used to identify various control information.

[0085] Here, the physical channels will be described. The physical channels used for wireless communication between a terminal device and a base station device may include the following physical channels.

[0086] 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)

[0087] The PBCH may be used to broadcast system information required by a terminal device.

[0088] In addition, in NR, the PBCH may be used to broadcast a time index (SSB-Index) within a synchronization signal block (SSB) period.

[0089] The PDCCH is used in downlink wireless communication (wireless communication from a base station device to a terminal device). The UE may be used to transmit (or carry) Downlink Control Information (DCI), where one or more DCIs (DCIs) may be used for the transmission of the downlink control information. In other words, a format for the downlink control information may be defined. The fields in the PDCCH are defined as DCI and may be mapped to information bits. The terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. In addition, the terminal device may The serving cell may monitor PDCCH candidates at configured monitoring occasions in one or more configured control resource sets (CORESETs) configured by resource configuration. The DCI format may be used for scheduling a PUSCH in the serving cell. The PUSCH may be used for transmitting user data and RRC messages (described later).

[0090] PDCCH repetition is achieved by using two search space sets that are explicitly linked by a configuration provided by higher layers (RRC layer). may be operated. In addition, two linked search space sets may be associated with a corresponding CORESET. For PDCCH repetition, The two search space sets are configured in the terminal with the same number of PDCCH candidates. Two PDCCH candidates that exist in two linked search space sets may be the same candidate. The PDCCH repetitions may be linked by a complementary index. When a slot is allocated, inter-slot repetition may be allowed, and each repetition may have the same number of Control Channel Elements (CCEs) and coded bits, and the same DCI payload.

[0091] The PUCCH is used in uplink wireless communication (wireless communication from a terminal device to a base station device). The uplink control information may be used to transmit uplink control information (UCI). Here, the uplink control information may include channel state information (CSI) used to indicate the state of the downlink channel. The uplink control information may include a scheduling request (SR) used to request UL-SCH (Uplink Shared CHannel) resources. The link control information includes HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement). It's okay to be surrounded.

[0092] The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer, and may also be used to transmit system information (SI) and random access responses (RAR) in the downlink.

[0093] The PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or uplink data together with HARQ-ACK and / or CSI, or may be used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only UCI, and the PDSCH or PUSCH may be used to transmit RRC messages and MAC CE (described later). In the PDSCH, the RRC message transmitted from the base station apparatus may be common signaling for a plurality of terminal apparatuses in the cell. Also, the RRC message transmitted from the base station apparatus may be dedicated signaling for a certain terminal apparatus. In other words, the terminal apparatus-specific (UE-specific) information may be dedicated to a certain terminal apparatus. The PUSCH may be transmitted using the UE's uplink signaling. It may also be used to transmit UE Capability.

[0094] The PRACH may be used to transmit a random access preamble. The PRACH is used for initial connection establishment procedures, handover procedures, connection re-establishment procedures, and the above. It may be used to indicate synchronization (timing alignment) for downlink transmissions and a request for UL-SCH resources.

[0095] An example of the functions of MAC will be described. MAC may be called a MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. A logical channel may be identified by a logical channel identity (or logical channel ID). MAC may be connected to a higher RLC via a logical channel. Depending on the type of information to be transmitted, logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information. Logical channels may also be divided into uplink logical channels and downlink logical channels. MAC may be configured to handle one or more different transport channels. The MAC may have a function to multiplex MAC SDUs belonging to different logical channels and provide them to the PHY. The MAC may also have a function to demultiplex MAC PDUs provided by the PHY and provide them to a higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a function to report scheduling information. The MAC has the function of performing priority processing among terminal devices using dynamic scheduling. MAC may also have a function to perform priority processing between logical channels within one terminal device. MAC is a function that prioritizes overlapping resources within a single terminal device. E-UTRA MAC identifies Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have the ability to identify Multicast / Broadcast Services (MBS). The MAC may also have the ability to select transport formats. The MAC may also have the ability to perform Discontinuous Reception (DRX) and / or Discontinuous Transmission (DTX), random access, and so on. It has the function of executing the Random Access (RA) procedure, notifying the information of the available transmission power, and - Power Headroom Report (PHR) function, Buffer Status Report (BSR) function that notifies the amount of data in the transmission buffer, etc. The NR MAC may have a bandwidth adaptation (BA) function. The MAC PDU format used in the E-UTRA MAC may differ from the MAC PDU format used in the NR MAC. The MAC PDU may also include a MAC control element (MAC CE), which is an element for performing control in the MAC.

[0096] Uplink (UL) and / or downlink (DL) used in E-UTRA and / or NR Next, a description will be given of the DL (Downlink) logical channels.

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

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

[0099] A CCCH (Common Control Channel) may be a logical channel for transmitting control information between a terminal device and a base station device. The CCCH is used when the terminal device does not have an RRC connection. The CCCH may also be used between a base station device and multiple terminal devices.

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

[0101] A DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data point-to-point between a terminal device and a base station device. The DTCH may be a logical channel for transmitting user data. Dedicated user data may be user data dedicated to each terminal device. The DTCH may exist in both the uplink and downlink.

[0102] Logical channels and transport channels for the uplink in E-UTRA and / or NR This section explains the mapping of rules.

[0103] CCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel) may be mapped to

[0104] DCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel) may be mapped to

[0105] DTCH is an uplink transport channel, UL-SCH (Uplink Shared Channel) may be mapped to

[0106] Logical channels and transport channels for downlink in E-UTRA and / or NR This section explains the mapping of rules.

[0107] BCCH is a downlink transport channel, BCH (Broadcast Channel), and / or Alternatively, it may be mapped to a DL-SCH (Downlink Shared Channel).

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

[0109] CCCH is a downlink transport channel, DL-SCH (Downlink Shared Channel) may be mapped to

[0110] DCCH is a downlink transport channel, DL-SCH (Downlink Shared Channel) may be mapped to

[0111] DTCH is a downlink transport channel, DL-SCH (Downlink Shared Channel) may be mapped to

[0112] An example of the RLC function will be described below. The RLC may also be called an RLC sublayer. The E-UTRA RLC performs segmentation and / or The E-UTRA RLC may have the function of reassembly and reordering the data provided by the lower layer. NR RLC may have the function of re-ordering and providing it to higher layers. The NR RLC may have a function to add a sequence number to data provided by PDCP in the layer that is independent of the sequence number added by PDCP. The NR RLC may also have a function to segment data provided by PDCP and provide it to a lower layer. The NR RLC may also have a function to reassemble data provided by a lower layer and provide it to a higher layer. The RLC may also have a function to retransmit data and / or request retransmission (Automatic RLC may have a Repeat reQuest (ARQ). RLC also has the function of performing error correction by ARQ. The control information sent from the receiving side of the RLC to the transmitting side to indicate the data that needs to be retransmitted in order to perform ARQ can be called a status report. The instruction to send a status report can be called a poll. RLC may have a function to detect data duplication. RLC may also have a function to discard data. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). TM has the above The data received from the next layer is not divided and no RLC header needs to be added. The UM RLC entity is a unidirectional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity. In UM, the RLC entity performs functions such as segmenting and / or combining data received from higher layers and adding RLC headers, but does not need to control data retransmission. The UM RLC entity may be a unidirectional entity or a bidirectional entity. If the UM RLC entity is a unidirectional entity, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If the UM RLC entity is a bidirectional entity, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. AM The AM RLC entity may perform operations such as segmenting and / or combining data received from the upper layer, adding an RLC header, and controlling data retransmission. The AM RLC entity is a bidirectional entity and is configured as an AM RLC consisting of a transmitting side and a receiving side. In addition, data provided to lower layers by TM and / or data provided by lower layers The data provided to the lower layer in UM and / or the data provided by the lower layer may be called a UMD PDU. The data provided to the lower layer in AM may be called a UMD PDU. The data provided by the E-UTRA RLC may be called AMD PDU. The RLC PDU format used in NR RLC may differ from the RLC PDU format used in NR RLC. RLC PDUs may include data RLC PDUs and control RLC PDUs. Data RLC PDUs may be called RLC DATA PDUs (RLC Data PDUs). Control RLC PDUs may be called RLC CONTROL PDUs (RLC Control PDUs).

[0113] An example of the function of PDCP will be explained. PDCP may be called a PDCP sublayer. PDCP may have a function to maintain sequence numbers. PDCP also allows efficient transmission of user data such as IP packets and Ethernet frames over wireless sections. The protocol used for header compression and decompression of IP packets may be called ROHC (Robust Header Compression) protocol. The protocol used for Ethernet frame header compression and decompression is EHC (Ethernet (registered trademark) PDCP may be called the PDCP (Data Header Compression Protocol). PDCP may also have a data encryption / decryption function. PDCP may also have a data integrity protection / verification function. PDCP may also have a re-ordering function. PDCP may also have a PDCP SDU retransmission function. PDCP may also have a data discard function using a discard timer. PDCP may also have a duplication function. PDCP may also have the functionality to discard duplicate received data. The PDCP entity is a bidirectional entity, consisting of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. There may be data PDCP PDUs and control PDCP PDUs. Data PDCP PDUs may be called PDCP DATA PDUs (PDCP Data PDUs). Control PDCP PDUs may be called PDCP CONTROL PDUs (PDCP Control PDUs).

[0114] An example of the SDAP function is explained below. SDAP is a service data adaptation protocol layer (SDAP). The SDAP is a service data adaptation protocol layer (SDAP). The SDAP may have the function of mapping the downlink QoS flow sent from 5GC to the terminal device via the base station device with a data radio bearer (DRB), and / or the function of mapping the uplink QoS flow sent from the terminal device via the base station device with a DRB. The SDAP may also have the function of storing mapping rule information. The SDAP may also have the function of marking the QoS flow identifier (QoS Flow ID: QFI). The SDAP PDU may be a data SDAP PDU and a control SDAP PDU. The data SDAP PDU is called an SDAP DATA PDU (SDAP Data PDU). Also, the control SDAP PDU can be called SDAP CONTROL PDU (SDAP Control PDU). The SDAP entity of the terminal device may be called a PDU (SDAP control PDU, SDAP control PDU). One SDAP entity may exist for each PDU session.

[0115] An example of the functions of the RRC will be described. The RRC may have a broadcast function. The RRC may have a paging function from the 5GC. The RRC may have a paging function from the gNB 102 or the ng-eNB 100. The RRC may have an RRC connection management function. The RRC may also have a radio 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 a terminal device measurement reporting function. The RRC may have a radio link control function. The RRC may also have a QoS management function. RRC uses RRC messages for broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device Terminal equipment measurement and reporting control, QoS management, radio link loss It is also possible to detect and recover from failures in the RRC messages and packets used in E-UTRA RRC. The parameters may be different from the RRC messages and parameters used in NR RRC. Note that the RRC message may include multiple information elements (IEs) for performing the above-mentioned control.

[0116] RRC messages may be sent using the logical channel BCCH, or the logical channel PCCH. RRC messages may be sent using the logical channel CCCH, or may be sent using the logical channel DCCH. RRC messages sent using the DCCH are also called dedicated RRC signaling or RRC signaling.

[0117] The RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), various types of System Information Blocks (SIBs), or other RRC messages.The RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.

[0118] RRC messages sent in the uplink (UL) direction using CCCH include, for example, an RRC Setup Request message, an RRC Resume Request message, an RRC Reestablishment Request message, and an RRC System Information Request message. The RRC connection request message may include an RRC System Info Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, and the like. ) etc. Other RRC messages may also be included.

[0119] RRC messages sent in the downlink (DL) direction using CCCH include, for example, an RRC connection reject message (RRC Connection Reject), an RRC connection setup message (RRC Connection Setup), an RRC connection reestablishment message (RRC Connection Reestablishment Reject), and an RRC connection reestablishment reject message (RRC Connection Reestablishment Reject). For example, an RRC reject message, an RRC setup message, etc. may be included. Other RRC messages may also be included.

[0120] RRC signaling sent in the uplink (UL) direction using DCCH includes, for example, measurement reports. The message may include a Measurement Report, an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message, an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, etc. Also, for example, the message may include a Measurement Report, an RRC Reconfiguration Complete message, an RRC Setup Complete message, an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, etc. RRC Setup Complete, RRC Reestablishment Complete, RRC Resume Complete, Security Mode Complete The RRC signaling may include a Security Mode Complete message, a UE Capability Information message, etc., and may also include other RRC signaling.

[0121] The RRC signaling sent in the downlink (DL) direction using the DCCH may include, for example, an RRC connection reconfiguration message, an RRC connection release message, a security mode command message, a UE capability inquiry message, etc. Also, for example, an RRC reconfiguration message, an RRC resume message, an RRC release message, an RRC reestablishment message, a security mode command message, a UE capability inquiry message, etc. Also, other RRC signaling may be included.

[0122] The above-mentioned functions of PHY, MAC, RLC, PDCP, SDAP, and RRC are merely examples, and some or all of the functions may not be implemented. Also, some or all of the functions of each layer may be included in other layers.

[0123] 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 radio connection. A radio bearer used for CP may be called a signaling radio bearer (SRB). A radio bearer used for UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identity (ID). A radio bearer identifier for an SRB may be called an SRB identity (SRB ID). A radio bearer identifier for a DRB may be called a DRB identity (DRB ID). SRB0 to SRB2 may be defined as SRBs for E-UTRA, or other SRBs may be defined. SRB0 to SRB3 may be defined as SRBs for NR, or other SRBs may be defined. SRB0 may be an SRB for RRC messages that are transmitted and / or received using the CCCH of the logical channel. SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2. The RRC signaling may include piggybacked NAS signaling. All RRC and NAS signaling transmitted and / or received using SRB1 The logical channel DCCH may be used for NAS signalling and for recording. It was an SRB for RRC signaling including logged measurement information. All RRC signaling and NAS signaling transmitted and / or received using SRB2 For nulling, the logical channel DCCH may be used. SRB2 may have a lower priority than SRB1. SRB3 is used when EN-DC, NGEN-DC, NR-DC, etc. are set in the terminal device. The logical channel DCCH may be used for all RRC and NAS signaling transmitted and / or received using SRB3. Other SRBs may be provided for other uses. The DRB may be a radio bearer for user data. RRC signaling transmitted and / or received using the DRB may use the logical channel DTCH.

[0124] The radio bearer in the terminal device is explained. The radio bearer includes the RLC bearer. An RLC bearer may consist of one or two RLC entities and logical channels. If an RLC bearer has two RLC entities, the RLC entity is a TM RLC entity. and / or the transmitting RLC entity and the RLC entity in unidirectional UM mode. The SRB0 may be a receiving RLC entity and a receiving RLC entity. The SRB0 may consist of one RLC bearer. The RLC bearer of the SRB0 may consist of the RLC entity of the TM and a logical channel. The SRB0 is active in all states (RRC idle, RRC connected, RRC inactive, etc.) of the terminal device. SRB1 may be established and / or configured in the 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 is a PDCP entity and one or more RLC bearers. The RLC bearer of SRB1 may consist of an RLC entity of the AM and a logical channel. The RLC bearer of SRB2 ... An SRB2 may be established and / or configured in the terminal device by RRC signaling received from the station device. An SRB2 consists of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB2 may consist of an RLC entity of AM and a logical channel. The PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node. SRB3 may be added when a secondary node in EN-DC, NGEN-DC, or NR-DC is added, or When the AS security is activated or the secondary node is changed, the RRC connection state One SRB may be established and / or configured in the terminal device by RRC signaling received from the base station device. SRB3 is a direct SRB between the terminal device and a secondary node. The SRB3 consists of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB3 may consist of an RLC entity of AM and a logical channel. The PDCP on the base station device side of SRB3 may be placed in the secondary node. The DRB is AS security. One or more DRBs may be established and / or configured in a terminal device by RRC signaling received from a base station device by a terminal device in an RRC connected state with activated security. A DRB may consist of one PDCP entity and one or more RLC bearers. RLC bearers of a DRB may consist of an AM or UM RLC entity and logical channels.

[0125] For RLC bearers established and / or configured in a cell group consisting of E-UTRA, the RLC entity established and / or configured may be an E-UTRA RLC. For RLC bearers established and / or configured in a cell group consisting of NR, the RLC entity established and / or configured may be an E-UTRA RLC. If an EN-DC is configured in the terminal device, the PDCP entity established and / or configured for the MN (Master Node) terminated MCG bearer may be an NR RLC. The PDCP may be either E-UTRA PDCP or NR PDCP. In this case, the PDCP established and / or configured for radio bearers of other bearer types, i.e., MN terminated split bearer, MN terminated SCG bearer, SN (Secondary Node) terminated MCG bearer, SN terminated split bearer, and SN terminated SCG bearer, may be an NR PDCP. If NGEN-DC, NE-DC, or NR-DC is set in the terminal device, all bearer types The PDCP entity established and / or configured for the radio bearer in may be an NR PDCP.

[0126] In NR, a DRB established and / or configured in a terminal device is one PDU session. In the terminal device, one SDAP entity can be associated with one PDU session. The SDAP entity, PDCP entity, RLC entity, and logical channels established and / or configured in the terminal device may be established and / or configured in the terminal device. It may be established and / or configured by RRC signaling received from a base station device.

[0127] The reference signal received power (RSRP) measured in the sidelink may be, for example, the following RSRP: Furthermore, the following RSRP may be referred to as SL-RSRP. (a) PSBCH RSRP (b) PSSCH RSRP (c) PSCCH RSRP

[0128] PSBCH-RSRP (PSBCH RSRP) is a set of multiple demodulation reference signals (DRSs) associated with the PSBCH. The power distribution of resource elements that transmit the DMRS (Division Multiplexing Reference Signal) is The PSSCH-RSRP (PSSCH RSRP) may be defined as the linear average of the power contributions of the resource elements of the antenna ports transmitting the multiple DMRSs associated with the PSSCH, and in the case of multiple antenna ports, the RSRP values ​​for each antenna port may be summed. The PSCCH-RSRP (PSCCH RSRP) may be defined as the linear average of the power contributions of the resource elements of the antenna ports transmitting the multiple DMRSs associated with the PSSCH. It may be defined as the linear average of the power contributions of resource elements carrying multiple associated DMRSs, e.g., for demodulating PSBCH, PSSCH, and PSCCH signals. In addition, a terminal device that performs sidelink communication with another terminal device may measure the RSRP of the sidelink communication (SL-RSRP) using the PSSCH or PSCCH transmitted from the other terminal device. Furthermore, the terminal device may measure the RSRP (SD-RSRP) of the discovery message by using, for example, the power contribution of the resource element that transmits the DMRS associated with the discovery message.

[0129] In addition to the SL-RSRP, the UE 122 may measure the following quantities in the sidelink measurements: (a) Sidelink received signal strength indicator (SL RSSI) (b) Sidelink channel occupancy ratio (SL CR) (c) Sidelink channel busy ratio(SL CBR)

[0130] The SL RSSI is the line of power ([W]) observed on the configured subchannels within the OFDM symbols of the slots configured for PSCCH and PSSCH, starting from the second OFDM symbol. The SLCR in slot n may be defined as the shape average. It may be defined as the sum of the number of subchannels used for sidelink transmission from slot [n] to slot [n-1] and the number of subchannels allocated from slot [n] to slot [n+b] divided by the total number of subchannels allocated from slot [na] to slot [n+b]. The SL CBR in slot n is determined by determining whether the SL RSSI exceeds a threshold in the resource pool during a period set as a CBR measurement window (slot [na] to slot [n-1]). It may be defined as the percentage of subchannels that are

[0131] 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 device. The L2 U2N Remote UE reports one or more candidate L2 U2N Relay UEs to the base station device. Before announcing the L2 U2N Relay, the RSRP of the candidate L2 U2N Relay UE is checked to see if it satisfies the L2 U2N Relay selection criteria. The L2 U2N Remote UE may report only candidate L2 U2N Relay UEs that satisfy the selection criteria and match the criteria of the higher layer to the base station device. When reporting one or more candidate L2 U2N Relay UEs to the base station device, the L2 U2N Remote UE may The report to the candidate L2 U2N Relay UE may include identification information of the candidate L2 U2N Relay UE, identification information of the serving cell of the candidate L2 U2N Relay UE, and measurement results. The RSRP (SD-RSRP) of the discovery message transmitted by the Relay UE may be used. Note that the identification information may be an identifier (ID).

[0132] Furthermore, the L2 U2N Remote UE having the serving L2 U2N Relay UE may include the serving L2 U2N Relay UE in the measurement results. The Serving L2 U2N Relay UE may use RSRP (SL-RSRP) measured in sidelink communication with the Serving L2 U2N Relay UE. If SL-RSRP is not available 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 device to the L2 U2N Remote UE.

[0133] Next, the serving cell will be described. In a terminal device in an RRC connected state (RRC_CONNECTED) where one serving cell is configured, the serving cell may be configured as one primary cell (PCell). In a terminal device in an RRC connected state, the serving cell A PCell may refer to a set of cells (set of cells) consisting of a Special Cell (SpCell) and one or more Secondary Cells (SCells). An SpCell may support PUCCH transmission and contention-based random access (CBRA). A PCell is a cell that a terminal device in an RRC idle state (RRC_IDLE) uses to transmit RRC packets. The PCell may be a cell used in the RRC connection establishment procedure when transitioning to a connected state. The PCell may also be a cell used in the RRC connection re-establishment procedure when the terminal device re-establishes the RRC connection. The PCell may also be a cell used in the random access procedure during handover. The SpCell may also be a cell used for purposes other than those mentioned above.

[0134] When a group of serving cells configured for a terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device. Also, for a terminal device in which CA is configured, a cell providing additional radio resources to the SpCell may refer to an SCell. .

[0135] This section describes a cell group configured by a base station device for a terminal device. A cell group may be configured with one SpCell. A cell group may also be configured with one SpCell and one or more SCells. In other words, a cell group may be configured with one SpCell. and optionally one or more SCells. A loop may be expressed as a set of cell(s).

[0136] Dual Connectivity (DC) is a technology that performs data communication using the radio resources of cell groups that are respectively configured by a first base station device (first node) and a second base station device (second node). When DC or MR-DC (described later) is performed, the base station device A cell group may be added. To perform DC, a first base station device may add a second base station device. The first base station device may be called a master node (MN). The cell group configured by the master node may be called a Master Cell Group (MCG). The second base station device is called a Secondary Node (SN). A cell group configured by a secondary node may be called a secondary cell group (SCG). The master node and the secondary node may be configured within the same base station device.

[0137] Furthermore, when DC is not configured, the cell group configured in the terminal device may be called an MCG. Furthermore, when DC is not configured, the SpCell configured in the terminal device may be a PCell. Furthermore, an NR in which DC is not configured may be called an NR standalone. good.

[0138] The UE 122 may receive a special cell (SpCell) configuration from the gNB 102. For example, the RRCReconfiguration message may include a cell group configuration (information element named CellGroupConfig). The cell group configuration may include special cell configuration (information named spCellConfig). An information element named spCellConfigDedicated included in the information element named spCellConfig may include a cell configuration dedicated to the UE 122 configured by this SpCellConfig. The information element named spCellConfigDedicated may be rephrased as SpCellConfigDedicated or SpCell dedicated setting. The information element named "firstActiveDownlinkBWP-Id" may include a parameter of a BWP identifier named "firstActiveDownlinkBWP-Id" (described later). The special cell configuration may also include an information element named "reconfigurationWithSync". spCellConfigCommon included in the information element named reconfigurationWithSync The information element named is a cell-specific information element of the serving cell (i.e., special cell) of the UE 122. The synchronization-with-reconfiguration IE may be used to set parameters. In order to clearly indicate that a certain term is an information element, the term "IE" may be added. For example, the synchronization-with-reconfiguration IE may be included in an RRC reconfiguration message, and the UE 122 that receives the RRC reconfiguration message may In accordance with the RRC reconfiguration message, a synchronized reconfiguration (procedure) may be performed.

[0139] Next, we will explain Radio Link Monitoring (RLM) in Uu. do.

[0140] In the RRC connected state, the terminal device uses Active BWP or radio link monitoring, which will be described later. RLM may be performed in the BWP designated as the BWP that performs the RLM. For example, the reference signal may be CRS in E-UTRA, SSB / CSI-RS in NR, and a signal quality threshold. The reference signal may include SSB. The signal quality threshold may be set by the network. Alternatively, a default threshold may be used. SSB-based RLM may be performed based on the SSB associated with the initial DL BWP, which will be described later. SSB-based RLM may be configured for the initial DL BWP and one or more DL BWPs including the SSB associated with the initial DL BWP. CSI-RS-based RLM may be performed for other DL BWPs.

[0141] In the RLM, a terminal device is considered to be a device that meets any of the following criteria (A) to (D): May declare or detect Radio Link Failure (RLF) . (A) The radio problem timer, which starts based on in-sync and out-of-sync notifications from the PHY, expires. (B) A measurement report for a specific measurement identifier is triggered while the radio problem timer is running. A timer that starts based on the (C) The random access procedure failed. (D) RLC failure detected

[0142] A terminal device that detects RLF of an MCG remains in an RRC connected state and selects and re-establishes the optimal cell. If DC is configured, the terminal device that declared RLF may remain in the RRC connected state and notify the network of the RLF. Note that the terminal device may determine that any of the above criteria (A) to (D) is met in the PCell (for example, in the case of (A), the radio problem timer of the PCell has expired, or in the case of (C), the random access procedure has failed in the MAC of the MCG). Based on this, the RLF of the MCG may be detected.

[0143] The terminal device may be configured with a reference signal used for RLM from the network by RRC signaling. The RRC signaling includes radio link monitoring configuration (RadioLinkM The terminal device may perform RLM using one or more reference signals (referred to as RLM-RS) configured by the radio link monitoring configuration. In addition, if the RLM-RS is not specified, the terminal device may perform RLM using a default reference signal. The radio link monitoring configuration may be configured in the UE for each DL BWP. The radio link monitoring configuration may be configured for the DL BWP of the PCell and / or the PSCell.

[0144] The PHY of the terminal device may notify the upper layer (RRC layer) that it is in sync when the conditions for being in sync are met. In this case, the out-of-synchronization may be notified to a higher layer (such as RRC).

[0145] The radio link monitoring configuration may include information indicating a monitoring purpose and identifier information indicating a reference signal. For example, the monitoring purpose may include a purpose of monitoring a radio link failure, a purpose of monitoring a beam failure, or both purposes. Furthermore, for example, the identifier information indicating the reference signal may include information indicating an SSB-Index of an SSB of a cell. Furthermore, for example, the identifier information indicating the reference signal may include information indicating an identifier linked to a channel state information reference signal (CSI-RS) configured in the terminal device.

[0146] If the terminal device is not provided with an RLM-RS and has one or more CSI-RSs, If the TCI status(es) for transmission are provided, the terminal equipment shall Or do all of them. (A) If the activated TCI state for PDCCH reception contains only one reference signal, Use the reference signal provided in the activated TCI state for radio link monitoring (B) If the activated TCI state for PDCCH reception includes two reference signals, it is expected that the QCL type of one reference signal is set to type D, and the reference signal whose QCL type is set to type D is used for radio link monitoring.

[0147] If multiple downlink BWPs are configured in a serving cell, the terminal device may perform RLM using a reference signal corresponding to the RLM-RS in the active downlink BWP. Also, if multiple downlink BWPs are configured in a serving cell and the RLM-RS is not provided in the active downlink BWP, the terminal device receives the PDCCH in the CORESET of the active downlink BWP. The terminal device may perform RLM using the reference signal(s) provided in the activated TCI state for the RLM. In other words, the terminal device performing RLM may be said to have the PHY of the terminal device assess the radio link quality. In addition, the PHY may assess the measured radio link quality based on the configured If the condition worsens below the threshold, the out-of-sync condition is reported to the upper layer (RRC, etc.). You may know.

[0148] The notification message in U2N relay is explained. The relay terminal device The notification message is sent to the remote UE when: RLF is detected in the UE; an RRC reconfiguration message including a reconfiguration information element with synchronization is received; cell reselection is initiated; an RRC connection failure (including an RRC connection rejection) is detected; T300 expires; or an RRC resumption procedure fails. The relay terminal device may transmit the notification message to a terminal device. The relay terminal device may include a notification type in the notification message. Different values ​​may be set for the notification type depending on the reason for starting transmission of the notification message, and the notification type may indicate, for example, a radio link failure in Uu, a radio link failure in a PC5 link, an RRC reconfiguration failure, a handover of a relay terminal device, a cell reselection of a relay terminal device, or another type. The remote terminal device that received the notification message may establish an RRC connection based on being in an RRC_CONNECCTED state. It may initiate a re-establishment procedure or decide to release the PC5 RRC connection with the relay terminal device. The upper layer may be notified of the release of the PC5 unicast link based on the The notification message may be a message named NotificationMessageSidelink, and may be considered to have initiated cell reselection based on the notification type being relayUE-HO. The notification type may be a message named IndicationType or may be a message named other.

[0149] Based on the above description, various embodiments of the present invention will be described. Note that the above-described processes may be applied to processes that are omitted in the following description.

[0150] 5 is a block diagram showing the configuration of a terminal device (UE 122) in this embodiment. In order to avoid a complicated explanation, FIG. 5 shows only the main components closely related to this embodiment. Show only.

[0151] The UE 122 shown in FIG. 5 includes a receiver 500 that receives control information (SCI, MAC control element, RRC signaling, etc.), discovery messages, information including user data, etc. from other terminal devices, a processor 502 that performs processing in accordance with parameters included in the received control information, etc., and and other terminal equipment, control information (SCI, MAC control elements, RRC signaling, etc.) and discovery A transmitting unit 504 is provided for transmitting information including a message and user data. The receiver 500 receives control information (MAC control elements, RRC signaling, etc.) from the base station device (gNB 102). The transmitting unit 504 may receive information including control information (MAC control elements, RRC signaling, etc.) and user data to the base station device (gNB102). The processing unit 502 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, PC5-S layer, Discovery layer, and application layer). That is, the processing unit 502 includes a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), RLC layer processing unit (RLC processing unit), PDCP layer processing unit (PDCP processing unit), SDAP processing unit (SDAP processing unit), RRC layer processing unit (RRC processing unit), PC5-S layer processing unit (PC5-S processing unit), Discovery layer processing unit (Discovery processing unit), and some or all of the application layer processing unit.

[0152] FIG. 6 is a block diagram showing the configuration of a base station device (gNB102) in this embodiment. To avoid complicating the explanation, FIG. 6 only shows the main components closely related to this embodiment. Only part is shown.

[0153] The base station apparatus shown in FIG. 6 includes a transmitter 604 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to the UE 122, a processor 602 that creates control information (DCI, MAC CE, RRC signaling, etc.) and transmits it to the UE 122, causing the processor 502 of the UE 122 to process it, and a receiver 600 that receives the control information (UCI, MAC CE, RRC signaling, etc.) from the UE 122. The processor 602 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 processor 602 may include some or all of the functions of a physical layer processor, MAC layer processor, RLC layer processor, PDCP layer processor, SDAP processor, RRC layer processor, and NAS layer processor. Part or all of it may be included.

[0154] In a multi-hop U2N relay that provides connectivity to a base station device for a remote terminal device using multiple relay terminal devices, the multiple relay terminal devices may have the same functions as the above-mentioned U2N relay terminal device, or may have extended functions. The multiple relay terminal devices may establish PC5-RRC connections with other adjacent relay terminal devices and remote terminal devices. Alternatively, the RRC connection with the base station apparatus may be maintained via another relay terminal apparatus. good.

[0155] An example of an embodiment of the present invention will be described with reference to FIG.

[0156] The UE 122 that communicates with the base station device makes a decision (step S1000) and operates based on the decision. (step S1002).

[0157] For example, the UE 122 may be a relay terminal device. In this case, the determination in step S1000 may be, for example, determining that the UE 122 satisfies one or more of the following conditions: It may also be possible to do so. (a) It serves as a relay terminal device (b) receiving RRC signaling including an accompaniment instruction information element from the base station device; (c) A radio link failure is detected on the Uu interface. (d) A sidelink radio link failure is detected. (e) Initiating the RRC connection re-establishment procedure (f) receiving RRC signaling including a path switching configuration information element from the base station device; (g) RRC reconfiguration failure detected

[0158] In step S1002, for example, the action may be, for example, sending PC5 RRC signaling including a waiting indication information element to the remote terminal device. Additionally or alternatively, in step S1002, for example, the action may be, for example, sending a message including no notification type. The notification message (NotificationMessageSidelink) is sent to the remote terminal device. Additionally or alternatively, in step S1002, for example, The wait instruction information element may for example be to pause relaying of data received from the remote terminal. The wait instruction information element may be, for example, one information element or a combination of multiple information elements. When the wait instruction information element is one information element, it may be, for example, one type of notification type included in a notification message (NotificationMessageSidelink), or may be, in addition to or instead of, In addition, the waiting instruction information element may be an information element included in a notification message. When the waiting instruction information element is a plurality of information elements, it may be, for example, a combination of a notification type and other information elements included in the notification message. Note that, when the notification message is used as the PC5 RRC signaling, Alternatively, other messages may be used. The relay terminal device may be an intermediate relay terminal device or a last relay terminal device. The accompaniment instruction information element may be an information element instructing that the connection with the remote terminal device be maintained, or alternatively, may be an information element instructing that the connection with the remote terminal device be maintained when performing path switching.

[0159] Also, for example, the UE 122 may be a remote terminal device. In this case, the steps In step S1000, the determination is made whether the remote terminal device satisfies one of the following conditions: It may be determined that a plurality of conditions are satisfied. (a) Acting as a remote terminal device (b) receiving PC5 RRC signaling including the standby instruction information element from the relay terminal device; (c) receiving RRC signaling including the standby instruction information element from the base station device; (d) receiving a notification message from the relay terminal device that does not include a notification type;

[0160] The operation in step S1002 is, for example, when the remote terminal device is the relay terminal Additionally or alternatively, it may be to suspend transmission through the device. Alternatively, the operation in step S1002 may be, for example, The relay terminal device may be configured to suspend transmission via the relay terminal device A. This may mean pausing transmission on a non-direct path, or pausing transmission on a DRB terminating at the base station device, or pausing transmission on an SRB terminating at the base station device, or if the remote terminal device also serves as a relay terminal device, pausing relaying of received data.

[0161] In step S1002, if the remote terminal device suspends transmission via the relay terminal device based on receiving PC5 RRC signaling including the standby instruction information element from the relay terminal device, the remote terminal device receives an RRC signal from the base station device. In addition, in step S1002, if the remote terminal device has temporarily stopped transmission via the relay terminal device based on receiving RRC signaling including the standby instruction information element from the base station device, the remote terminal device may resume transmission via the relay terminal device based on receiving RRC signaling including the standby instruction information element from the relay terminal device. The relay terminal device may resume transmission via the relay terminal device based on reception of the signaling. The PC5 RRC signaling may include a resume indication information element. The terminal device may transmit the PC5 RRC signaling including the resume indication information element to the remote terminal device, for example based on the completion of a path switching procedure. The information element may be an information element for resuming transmission via the relay terminal device. The PC5 RRC signaling may be a notification message (NotificationMessageSidelink) or an RRC reconfiguration message for sidelink (RRCReconfigurationSidelink). The RRC signaling may also be an RRC reconfiguration message.

[0162] The notification type in the notification message may indicate, for example, path switching of a relay terminal device, or other types. As the path switching of a relay terminal device, switching from a direct path to an indirect path (d2i path switching), switching from an indirect path to a direct path (i2d path switching), and switching from an indirect path to an indirect path (i2i path switching) may be indicated as individual types, or may be indicated simply as path switching. Note that the indirect path may be a path connecting to a base station device via a relay terminal device, and the direct path may be a path connecting directly to a base station device via Uu.

[0163] In one example of this embodiment, when a multi-hop relay is terminated at a base station device (multi-hop However, the case where a multi-hop relay terminates at another terminal device (multi-hop Even if the UE 122 is a U2U relay, the UE 122 may perform the same operation.

[0164] According to an example of this embodiment, a notification message is received at a multi-hop U2N relay. This allows the terminal device to be provided with connectivity to the base station device without having to perform RRC reconnection.

[0165] In the above description, expressions such as "notified" and "indicated" may be interchangeable.

[0166] In the above description, expressions such as "link," "associate," and "link" may be interchangeable.

[0167] In addition, in the above description, expressions such as "included," "included," and "was included" may be used interchangeably.

[0168] In the above description, "the above" may be replaced with "the above-mentioned."

[0169] In the above explanation, "confirmed to be...", "set to be...", "includes..." Expressions such as these may be interchangeable.

[0170] In addition, in the examples of each process or the example flow of each process described above, some or all of the steps may not be executed. In the example of the flow, the order of the steps may be different. Also, in the example of each process or example of the flow of each process in the above explanation, some or all of the processes in each step may not be executed. Also, in the example of each process or example of the flow of each process in the above explanation, the order of the processes in each step may be different. Also, in the above explanation, "doing B based on A" may be rephrased as "doing B". In other words, "doing B" means "A" may be executed independently.

[0171] In the above explanation, "A may be replaced with B" may mean replacing A with B, as well as replacing B with A. Also, in the above explanation, when it is written that "C may be D" and "C may be E", it may also mean that "D may be E". Also, in the above explanation, when it is written that "F may be G" and "G may be H", it may also mean that "F may be H".

[0172] In the above explanation, if the conditions "A" and "B" are contradictory conditions, the condition "B" may be expressed as the "other" condition of the condition "A."

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

[0174] The program that runs on the device according to this embodiment may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of this embodiment. The program or the information handled by the program is temporarily loaded into a volatile memory such as a random access memory (RAM) during processing, or is stored in a flash memory. It is stored in non-volatile memory such as memory or a hard disk drive (HDD) and is retrieved by the CPU as needed. Reading, modifying and writing are performed by this.

[0175] Note that a part of the device in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer system. The "computer system" here refers to a computer system built into the device, including hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0176] Furthermore, "computer-readable recording media" includes those that dynamically store programs for a short period of time, such as communication lines when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that store programs for a certain period of time, such as volatile memory within computer systems that serve as servers or clients in such cases. The program may be for realizing part of the above-mentioned functions, or may be a program that already has the above-mentioned functions recorded in a computer system. It may be possible to achieve this in combination with

[0177] Furthermore, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electric circuit, typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable logic circuit (FPLC), a microprocessor (MCU), a microcomputer (CPU ... The general-purpose processor may include a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the aforementioned circuits may be composed of digital circuits or analog circuits. Additionally, if advances in semiconductor technology result in the emergence of integrated circuit technologies that can replace current integrated circuits, integrated circuits based on those technologies may also be used.

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

[0179] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the gist of this embodiment. 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. Furthermore, configurations in which elements described in the above embodiment are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0180] 100 ng-eNB 102 gNB 110, 112, 114 Interface 122UE 200, 700 PHY 202, 702 MAC 204, 704 RLC 206, 706 PDCP 208, 708 RRC 210 PC5-S 310, 710 SDAP 400 Discovery 500, 600 receiver 502, 602 Processing section 504, 604 Transmitter 712 NAS 800 SRAP

Claims

1. A first terminal device that communicates with a base station device, a processing unit; a transmitter unit, the first terminal device serves to relay communication between the second terminal device and the base station device; The processing unit includes a first indication information element in a PC5 RRC message. The transmission unit transmits the PC5 RRC message to the second terminal device; the first instruction information element is an instruction information element to suspend transmission of the second terminal device; A first terminal device.

2. A second terminal device that communicates with a base station device, a processing unit; a receiving unit, the second terminal device communicates with the base station device via the first terminal device; The receiving unit receives PC5 RRC signaling from a first terminal device; The processing unit determines that the PC5 RRC signaling includes a first indication information element. suspending transmission of a radio bearer terminated at the base station device based on the result; A second terminal device.

3. The second terminal device according to claim 2, the receiving unit receives RRC signaling from the base station device; the processing unit resumes transmission of the radio bearer, based on the fact that transmission of the radio bearer terminated at the base station device has been suspended; A first terminal device.

4. A method for a first terminal device communicating with a base station device, comprising: the first terminal device serves to relay communication between the second terminal device and the base station device; including a first indication information element in a PC5 RRC message; sending the PC5 RRC message to the second terminal device; the first instruction information element is an instruction information element to suspend transmission of the second terminal device; method.

Images