Terminal device, method, and integrated circuit

Abstract

To provide a multipath remote terminal device, a method, and an integrated circuit capable of operating with signaling from a base station applied appropriately.SOLUTION: In a communication system, a terminal device receives an RRC message including an information element related to a reconfiguration with synchronization from a base station device, and performs the reconfiguration with synchronization according to the RRC message. Based on determining that at least two conditions are satisfied, the terminal device instructs an upper layer to trigger a PC5 unicast link release. The two conditions are that the terminal device plays the role of a remote terminal device and that a non-direct path is not set after applying the RRC message.SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present invention relates to a terminal device, a method, and an integrated circuit. [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 base stations, core networks, and services, are currently 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) and LTE-Advanced Pro (LTE-A Pro).

[0004] In addition, 3GPP has begun technical discussions and standardization of NR (New Radio, or NR Radio access) as a radio access technology (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 v17.3.0,"Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specifications" pp70-116,pp218-223,pp316-1107 [Non-Patent Document 2] 3GPP TS 38.321 v17.2.0, "NR;Medium Access Control (MAC) protocol specification" pp17-104 [Non-Patent Document 3] 3GPP TS 38.213 v17.1.0, "NR; Physical layer procedures for control" pp14-20 [Non-Patent Document 4] 3GPP TS 38.300 v17.2.0, "NR; NR and NG-RAN Overall Description; Stage 2" [Non-Patent Document 5] 3GPP TS 38.351 v17.1.0, "NR; Sidelink Relay Adaptation Protocol (SRAP) Specification" 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) in which terminal devices communicate directly with each other without going through the core network has been considered, and a technology called UE-to-Network Relay (U2N Relay) in which a relay terminal device provides communication via sidelink, allowing the terminal device to communicate with a base station device via the relay terminal device, has also been considered. Furthermore, a technology called UE-to-Network Relay (U2N Relay) in which a terminal device communicates with a base station device using two types (or more) of paths: a non-direct path in which the terminal device communicates with a base station device using a U2N Relay, and a direct path in which the terminal device communicates directly with a base station device without using a U2N Relay, has been considered. Research has begun on a technology called Multi-path Relay, which can achieve this.

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

[0008] In order to achieve the above object, one aspect of the present invention provides the following means. That is, one aspect of the present invention provides a terminal device that communicates with a base station device, the terminal device having a receiving unit that receives an RRC message including an information element related to a synchronous reconfiguration from the base station device, and a processing unit. The processing unit performs synchronous reconfiguration according to the RRC message, and notifies an upper layer of a PC5 unicast link release based on determining that at least two conditions are satisfied. to trigger the RRC message, and the two conditions are: (a) the terminal device is playing the role of a remote terminal device, and (b) after applying the RRC message, a non-direct path is not set.

[0009] Another aspect of the present invention is a method for a terminal device communicating with a base station device, comprising the steps of: receiving an RRC message including an information element related to a synchronous reconfiguration from the base station device; Instructing an upper layer to trigger a release of the PC5 unicast link based on performing synchronized reconfiguration according to the RRC message and determining that at least two conditions are satisfied. and a step of: determining whether or not a non-direct path has been established after applying the RRC message; and

[0010] Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the integrated circuit receiving an RRC message including an information element regarding a reconfiguration with synchronization from the base station device. and performing a synchronized reconfiguration according to the RRC message and triggering a PC5 unicast link release to an upper layer based on determining that at least two conditions are met. and a function of instructing the terminal device to perform the above-mentioned two conditions: (a) the terminal device is playing the role of a remote terminal device, and (b) after applying the RRC message, a non-direct path is not set.

[0011] 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. Effect of the Invention

[0012] According to one aspect of the present invention, a terminal device, a method, and an integrated circuit can realize efficient communication control processing. [Brief description of the drawings]

[0013] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Diagram 2] A diagram showing an example of a protocol configuration for NR sidelink communication in this embodiment. [Diagram 3]A diagram showing an example of a protocol configuration for NR sidelink communication in this embodiment. [Figure 4] FIG. 13 is a diagram showing an example of a protocol configuration in a discovery procedure according to the embodiment; [Diagram 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 embodiment. [Figure 7] FIG. 1 is a diagram showing an example of a protocol configuration in NR according to this embodiment. [Figure 8] FIG. 2 is a diagram showing 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 showing an example of a protocol configuration of a user plane of an L2 U2N relay according to the embodiment. [Figure 10] 4 is an example of processing according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0015] In this embodiment, the names of the nodes and entities and the processes in the nodes and entities are described when the radio access technology is NR, 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.

[0016] 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.

[0017] 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 an E-UTRA protocol, which will be described later. The E-UTRA protocol may be composed of an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA Control Plane (CP) protocol, which will be described later. 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 composed of eNBs may be referred to as E-UTRAN.

[0018] NR may be a radio access technology. NR also provides 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 (Control Plane: CP) protocol to the UE 122. It may terminate the control plane protocols.

[0019] The interface 110 between the ng-eNB 100 and the gNB 102 may be called an Xn interface. The ng-eNB and the gNB may be connected 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 be connected to the 5GC via the NG interface.

[0020] 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 sidelink (SL) communication. Furthermore, a terminal device capable of performing sidelink communication may be referred to as a terminal device capable of sidelink communication.

[0021] In the following description, the ng-eNB 100 and / or the gNB 102 are also simply referred to as base station devices, and the UE 122 is also simply referred to as terminal devices or UEs. The PC5 interface is also simply referred to as PC5. The Uu interface is also referred to simply as Uu.

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

[0023] 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 L2 ID. The three transmission modes are "Unicast transmission", "Groupcast transmission", and "Broadcast transmission". The transmission mode may be referred to as a broadcast type, etc. Unicast transmission for direct communication is supported on PC5, and a PC5 unicast link between two UEs may be established for direct communication. The PC5 unicast link may be maintained, changed, or released according to application layer requests or communication requirements.

[0024] Unicast transmission is characterized by: (1) support of 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.

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

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

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

[0028] Fig. 2(A) 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. 2(A), the control plane protocol stack for SCCH using RRC includes PHY (Physical layer) 200 which is a wireless physical layer, MAC (Medium Access Control) 202 which is a medium access control layer, 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 a layer for wireless resource control (RF control) The RRC 208 may be configured as a radio resource control layer (RRC layer). FIG. 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 FIG. 2(B), 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, a 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 signalling layer (PC5 signalling layer) PC5-S (PC5 Signalling) 210.

[0029] FIG. 3(A) is a diagram of the control plane protocol stack for SBCCH configured on the PC5 interface. As shown in FIG. 3(A), the control plane protocol stack for SBCCH is The network includes a PHY (Physical layer) 200, which is a wireless physical layer, a medium access control layer (MACL), and a The QoS layer may be composed of a MAC (Medium Access Control) 202, a Radio Link Control (RLC) 204, and a Radio Resource Control (RRC) 208. FIG. 3B is a diagram of a protocol stack of the user plane (UP) for STCH configured on the PC5 interface. As shown in FIG. 3B, the control plane protocol stack for STCH 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, 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.

[0030] 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. Also, the PC5-S 210 and Discovery 400 described later may be layers higher than the AS layer.

[0031] In this embodiment, the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), SDAP (SDAP layer), RRC (RRC layer), and PC5-S (PC5-S layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), SDAP (SDAP layer), RRC (RRC layer), and PC5-S (PC5-S layer) may be PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), SDAP (SDAP layer), RRC (RRC layer), and PC5-S (PC5-S layer) of the NR sidelink protocol, respectively. In addition, when sidelink communication is performed using the E-UTRA technology, the SDAP layer may not be required. In order to clarify that it is a protocol for sidelink, for example, RLC may be expressed as sidelink RLC, SL RLC, PC5 RLC, etc., and for other protocols, the term "sidelink", "SL", or "PC5" may be added to the beginning to indicate that they are protocols for sidelink.

[0032] In addition, in this embodiment, when distinguishing between E-UTRA protocols and NR protocols, PHY, MAC, RLC, PDCP, and RRC may be referred to as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE, respectively. Also, PHY, MAC, RLC, PDCP, and RRC are referred to as These are sometimes 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. In addition, when distinguishing between E-UTRA protocols and NR protocols, PHY, MAC, RLC, PDCP, and RRC are sometimes referred to as PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. In addition, PHY, MAC, RLC, PDCP, and RRC may be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

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

[0034] Note that data provided to lower layers from 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 the data provided to higher layers by MAC, RLC, PDCP, and SDAP may be called SDAP PDU. The data is 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.

[0035] Here, the base station device and the terminal device communicate with each other through the higher layer (Uu interface). 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 may transmit and receive an RRC message (also referred to as RRC signaling) in a Radio Resource Control (RRC) layer. Also, a base station device and a terminal device may transmit and receive a MAC Control Element (MAC CE) in a Medium Access Control (MAC) layer. In addition, the RRC layer of the terminal device may receive system information broadcast from the base station device. Here, RRC messages, system information, and / or MAC control elements are The statement is based on higher layer signaling or higher layer parameters. The higher layer parameter is also called a metric (higher layer parameter). Each of the parameters included in the upper layer signal may be referred to as an upper layer parameter. For example, in the processing of the PHY layer, the upper layer means an upper layer seen from the PHY layer, and may mean one or more of the MAC layer, the RRC layer, the RLC layer, the PDCP layer, the NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer may mean one or more of the RRC layer, the RLC layer, the PDCP layer, the NAS layer, etc.

[0036] Moreover, terminal devices also exchange (transmit and receive) signals at higher layers on the PC5 interface. Terminal devices may 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 (also referred to as RRC signaling) at a Medium Access Control (MAC) layer. In the RRC message, the MAC control element (MAC CE) may be transmitted and received by the higher layer. 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 the layer processing, the upper layer means a higher layer from the viewpoint of the PHY layer, and may mean one or more of the MAC layer, the RRC layer, the RLC layer, the PDCP layer, the PC5-S layer, the Discovery layer, etc. In the processing of layers, the higher 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.

[0037] Hereinafter, the meaning of "A is given (provided) by the upper layer" or "A is given (provided) by the upper layer" may mean that the upper layer (mainly the RRC layer, the MAC layer, etc.) of the terminal device receives A from a base station device or another terminal device, and the received A is given (provided) to the physical layer of the terminal device from the upper layer of the terminal device. For example, in a terminal device, "being provided with upper layer parameters" may mean receiving an upper layer signal from a base station device or another terminal device, and providing the upper layer parameters included in the received upper layer signal to the physical layer of the terminal device from the upper layer of the terminal device. Setting upper layer parameters in a terminal device may mean that the upper layer parameters are given (provided) 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 or another terminal device, and setting the received upper layer parameters in the upper layer. However, setting upper layer parameters in a terminal device may include using default parameters that are given in advance to the upper layer of the terminal device. In describing the transmission of an RRC message from a terminal device to a base station device or another terminal device, an expression of "submitting a message to a lower layer" from an RRC entity of the terminal device may be used. may mean submitting a message to the PDCP layer. Here, "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 a PHY layer, a MAC layer, an RLC layer, a PDCP layer, etc.

[0038] An example of the PHY function will be described. The PHY of the terminal device can communicate with the PHY of other terminal devices via a side link. The PHY may have a function of transmitting and receiving data transmitted via a sidelink (SL) physical channel. The PHY may be connected to a higher 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.

[0039] 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.

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

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

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

[0043] The PSSCH transmits data to other terminal devices and control regarding HARQ / CSI feedback. It may be used to transmit information.

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

[0045] An example of the functions of the MAC will be described. The MAC may be called a MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by a logical channel identity (or logical channel ID). The MAC may be connected to the higher RLC via a logical channel. Depending on the type of information to be transmitted, the logical channels may be divided into a control channel that transmits control information and a traffic channel that transmits user information. The MAC may be configured to transmit one or more different logical channels. The MAC may have a function of multiplexing MAC SDUs belonging to a logical channel and providing them to the PHY. The MAC may also have a function of demultiplexing MAC PDUs provided from the PHY and providing them to a higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a function of reporting scheduling information. MAC has a function to perform priority processing among terminal devices using dynamic scheduling. MAC should also have a function for performing priority processing between logical channels within one terminal device. MAC has the function of prioritizing overlapping resources within one terminal device. E-UTRA MAC has the function of identifying Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have the ability to identify Multicast / Broadcast Services (MBS). The MAC may have the ability to select the transport format. The MAC may support Discontinuous Reception (DRX) and The functions include: calling and / or discontinuous transmission (DTX), executing the Random Access (RA) procedure, reporting available transmission power information, and power header. It has a Power Headroom Report (PHR) function, a 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 control element), which is an element for performing control in the MAC. The MAC control element (MAC CE) may be included.

[0046] In addition, the MAC sublayer may provide additional services and functions on 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).

[0047] Sidelink (SL) logical channels used in E-UTRA and / or NR In this section, we will explain the mapping between sidelink logical channels and transport channels.

[0048] 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 pinged.

[0049] The SCCH (Sidelink Control Channel) may be a logical channel for sidelink 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 be mapped to the SL-SCH, which is a sidelink transport channel.

[0050] 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. The STCH may be mapped to the SL-SCH, which is a sidelink transport channel.

[0051] An example of the function of the RLC will be described. The RLC may be called an RLC sublayer. The E-UTRA RLC may have a function of segmenting and / or concatenating data provided from the PDCP of the upper layer and providing it to a lower layer. The E-UTRA RLC may perform reassembly and reordering of data provided from the lower layer. The 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 the PDCP of the layer that is independent of the sequence number added by the PDCP. The NR RLC may also have a function to segment data provided by the PDCP and provide it to a lower layer. The NR RLC may also have a function to reassemble data provided by the lower layer and provide it to a higher layer. The RLC may also have a function to retransmit data and / or a function to request retransmission (Automatic RLC may have a repeat reQuest (ARQ) function. RLC also has a function to correct errors by ARQ. The control information that is sent from the receiving side of the RLC to the transmitting side to perform ARQ and indicates the data that needs to be retransmitted may be called a status report. The status report transmission instruction sent by the RLC is 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 uni-directional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity. In UM, data received from a higher layer is segmented and / or combined, an RLC header is added, etc., but data retransmission control is not required. The UM RLC entity may be a uni-directional entity or a bi-directional entity. If the UM RLC entity is a uni-directional entity, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If the UM RLC entity is a bi-directional entity, the UM RLC entity 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 dividing and / or combining data received from a higher 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 TMD PDU. The data provided by the E-UTRA RLC may be called AMD PDU. The RLC PDU format used in the NR RLC may be different from the RLC PDU format used in the NR RLC. Furthermore, the RLC PDU may be an RLC PDU for data and an RLC PDU for control. The RLC PDU for data may be called an RLC DATA PDU (RLC Data PDU). Furthermore, the RLC PDU for control may be called an RLC CONTROL PDU (RLC Control PDU). Note that, The control RLC PDU used to transmit the status report is called the status PDU (STATUS PDU). That's fine.

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

[0053] An example of the function of PDCP will be described. PDCP may be called a PDCP sublayer. PDCP may have a function for maintaining sequence numbers. PDCP also provides a mechanism for efficiently transmitting user data such as IP packets and Ethernet frames over wireless sections. The protocol used for IP packet header compression and decompression 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 Header Compression Protocol (PDCP). PDCP may also have a function for encrypting and decrypting data. PDCP may also have a function for protecting and verifying the integrity of data. PDCP may also have a function for re-ordering. PDCP may also have a function for retransmitting PDCP SDUs. PDCP may also have a function for discarding data 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 also be used. The PDCP PDU format used in the NR PDCP and NR PDCP may be different. There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0054] 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 on the PC5 interface is not supported.

[0055] An example of the SDAP function is explained below. SDAP is a service data adaptation protocol layer (SDAP). In the sidelink, the SDAP is a data adaption protocol layer (DAPA). The sidelink QoS flow (PC5 QoS flow) and sidelink data sent from the The SDAP may have a function of mapping the QoS flow ID (QoS Flow ID: QFI) and the PC5 QoS flow ID (PC5 QoS Flow ID: PQFI or PFI). The SDAP PDU may have a function for controlling the data. 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 SDAP PDU for control may be called SDAP CONTROL PDU (SDAP Control PDU). In the side link, the SDAP entity of the terminal device is called the SDAP control PDU. The property is the unicast transmission, groupcast transmission, and There may be one per destination for either forwarding, forwarding, or broadcast transmissions. Also, reflective QoS is not supported on PC5 interfaces.

[0056] An example of the RRC function is described below. The RRC is a function for communicating between peer UEs on the PC5 interface. The PC5-RRC protocol may support services and functions such as forwarding PC5-RRC messages for the UE, maintenance and release of PC5-RRC connection between two UEs, detection of sidelink radio link failure for 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 to be established after the corresponding PC5 unicast link is established. There is a one-to-one correspondence between PC5-RRC connection and PC5 unicast link. A UE may have multiple PC5-RRC connections to one or multiple UEs for different pairs of source L2ID and destination L2ID. Separate PC5-RRC procedures and messages may be used by the 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 transmissions, they may not use sidelink for PC5-RRC connections. 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.

[0057] A terminal device capable of sidelink communication may perform discovery. Discovery may include Model A and Model B. The protocol for the discovery procedure is shown in Figure 4. 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 announcement message, invitation message, and response message may be collectively called discovery messages, and other messages used in the discovery procedure may be called discovery messages. The following is an outline of the procedures of Model A and Model B in ProSe Direct Discovery.

[0058] 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 include information such as the type of discovery message, ProSe Application Code or ProSe Restricted Code, security protection element, and may additionally include metadata information. The announce message is sent using a destination Layer-2 ID and a source Layer-2 ID, and the monitored UE determines the destination L2 ID to receive 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 simply be referred to as the destination.

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

[0060] 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. The above-mentioned discovery is implemented by an application called ProSe. In addition to the above-mentioned types, there may be different types of discovery depending on the application or service that performs sidelink communication. Also, depending on the type of discovery, the information included in the discovery protocol message may be different, or additional messages may be sent to transmit additional information.

[0061] 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, The RLC 204 may be a radio link control layer, a packet data convergence protocol layer, and a discovery protocol layer, Discovery 400. Discovery 400 is a discovery protocol layer. The interface between UEs performing discovery may be referred to as PC5-D.

[0062] A plurality of resource pools for transmitting messages (discovery messages) used in discovery procedures may be set. When a resource pool dedicated to discovery is configured, the UE uses the resource pool dedicated to discovery as a resource pool for transmitting discovery messages, and If a resource pool for sidelink communication is not configured, a resource pool for sidelink communication may be used as a resource pool for transmitting a discovery message. Note that multiple resource pools for sidelink communication and resource pools dedicated to discovery may be configured at the same time. Each resource pool may be configured by UE-dedicated signaling or may be configured in advance.

[0063] 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. A sidelink SRB used to transmit a PC5-S message for establishing PC5-S security may be referred to as SL-SRB1. A sidelink SRB used to transmit a protected PC5-S message after PC5-S security is established may be referred to as SL-SRB2. A sidelink SRB used to transmit a 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. The PC5-RRC signaling may be RRC signaling between UEs transmitted and received on PC5. The PC5-RRC signaling may be a PC5-RRC message. It may also be called sage.

[0064] Explain Multi-path relay (or Multi-path relaying) Multipath relay may be a technology in which a terminal device communicates with a base station device using two paths, a direct path and an indirect path. The direct path may be a path in which the terminal device communicates directly with the base station device via a Uu interface. The indirect path may be a path in which the terminal device communicates with the base station device via a relay terminal device. The interface between the terminal device and the relay terminal device may be a PC5 interface or a different interface. In addition, The relay terminal device may be a terminal device that plays the role of U2N Relay UE.

[0065] In multi-path relaying, a bearer that is mapped to a direct path may be called a direct bearer, a bearer that is mapped to an indirect path may be called an indirect bearer, and a bearer that is mapped to both direct and indirect paths may be called a multi-path split bearer (MP) or simply a split bearer.

[0066] In a multipath split bearer, an RLC channel for the Uu interface and an RLC channel for the non-direct path may be set for a PDCP entity of a terminal device having two paths, a direct path and a non-direct path. If the interface between the multipath split bearer and the non-direct path is a PC5 interface, the RLC channel for the non-direct path may be an RLC channel for the PC5 interface. If PDCP duplication is configured for the multipath split bearer and PDCP duplication is activated, the PDCP entity duplicates a PDCP DATA PDU to be submitted to a lower layer, and the PDCP entity transmits the duplicated PDCP DATA PDU to the lower layer. Submit data to both of the multiple RLC channels configured for the same identity. A multi-path split bearer may be referred to as a bearer for which a multi-path split bearer is configured. A multi-path split bearer may be configured as both a data radio bearer and a signaling radio bearer. When PDCP replication is not configured for a bearer for which a split bearer is configured (or PDCP replication is configured but not activated) and a preferred path is configured, a PDCP DATA PDU may be submitted to a primary RLC entity configured for the preferred path, and when a split secondary RLC entity is configured and the amount of data to be submitted to the primary RLC entity and the split secondary RLC entity is equal to or greater than a threshold, a PDCP DATA PDU may be submitted to either the primary RLC entity or the split secondary RLC entity.

[0067] Here, a UE-to-Network (U2N) relay used in communication in a non-direct path will be described. The U2N relay may be a function that provides connectivity to a network for a remote terminal device (Remote UE). A remote terminal device that connects to a network using a U2N relay 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 uses a Uu interface to communicate with a base station device. Alternatively, a PC5 interface may be used for communication with a U2N Remote UE. In addition, the U2N relay may be classified into a layer 2 (L2) U2N relay and a layer 3 (L3) U2N relay. A remote terminal device in an L2 U2N relay may be specifically referred to as an L2 U2N Remote UE, or a PC5 interface may be used for communication with an L2 U2N Remote UE. The relay terminal device in the relay may be specifically referred to as an L2 U2N Relay UE. In the layer, there may be a Sidelink Relay Adaptation Protocol (SRAP) layer, SRAP (SRAP layer) 600. Note that the SRAP 600 may be simply expressed as an SRAP.

[0068] FIG. 6 is a diagram showing an example of a protocol configuration of a control plane (C-plane) including a SRAP layer according to the present embodiment. FIG. 7 is a diagram showing an example of a protocol configuration of a user plane (U-plane) including a SRAP layer according to the present embodiment. As shown in FIG. 6 and FIG. 7, the SRAP layer is a layer between a Remote UE and a Relay The association may be made between the UE and the gNB 102, and may also be made between the Relay UE and the gNB 102. 6 and 7 may be the ng-eNB 100. Also, the Remote UE or the Relay UE may be the UE 122.

[0069] Here, we will describe the SRAP layer. The SRAP layer may be called the SRAP sublayer, or simply SRAP. The SRAP sublayer handles the control plane and user interfaces of both the PC5 and Uu interfaces. The SRAP sublayer may reside above the RLC sublayer for the user plane. The SRAP sublayer on PC5 may be used for bearer mapping purposes. In an L2 U2N Relay UE, the SRAP sublayer resides on the Uu interface. In the L2 U2N Remote UE, the SRAP sublayer may include one SRAP entity on the PC5 interface and a separate collocated 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 a 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 the 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. Relay may be associated with the transmitter of the SRAP entity of the UE. Also, the Uu interface In the above, the transmission unit of the SRAP entity of the L2 U2N Relay UE is connected to the SRAP entity of the gNB102. The L2 U2N Relay UE may be associated with a receiving unit of an SRAP entity, and the receiving unit of the SRAP entity of the L2 U2N Relay UE may be associated with a transmitting unit of an SRAP entity of the gNB102.

[0070] The SRAP entity also has a function of forwarding data, a function of determining the UE ID field and the bearer ID field of the SRAP header to be added to the data packet, and a function of determining an exit link. The RLC channel determining unit 102 may have a function of determining an egress RLC channel.

[0071] 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 gNB102.

[0072] Next, a protocol configuration used between the base station device and the terminal device will be described. In the communication performed via the relay terminal device set in the non-direct path, the communication performed via the relay terminal device set in the non-direct path, and the communication performed on the Uu interface between the relay terminal device and the base station 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.

[0073] FIG. 7 is a diagram showing an example of an NR protocol configuration according to this embodiment. The functions of each protocol described with reference to FIG. 7 are some of the functions closely related to this embodiment, and may have other functions. In this embodiment, uplink (UL) refers to a transmission 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.

[0074] FIG. 7(A) is a diagram of the NR control plane (CP) protocol stack. As shown in FIG. 7(A), 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 Fig. 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, a packet data convergence (PDC) 705 which is a packet data convergence (PDC) 706 which is a packet data convergence (PDC) 707 which is a packet data convergence (PDC) 708 which is a packet data convergence (PDC) 709 which is a packet data convergence (PDC) 710 which is a packet data convergence (PDC) 711 which is a packet data convergence (PDC) 712 which is a packet data convergence (PDC) 713 which is a packet data convergence (PDC) 714 which is a packet data convergence (PDC) 715 which is a packet data convergence (PDC) 716 which is a packet data convergence (PDC) 717 which is a packet data convergence (PDC) 718 which is a packet data convergence (PDC) 719 which is a packet data convergence (PDC) 720 which is a packet data convergence (PDC) 721 which is a packet data convergence (PDC) 722 which is a packet data convergence (PDC) 723 which is a packet data convergence (PDC) 724 which is a packet data convergence (PDC) 725 which is a packet data convergence (PDC) 726 which is a packet data convergence (PDC) 727 which is a packet data convergence (PDC) 728 which is a packet data convergence (PDC) 729 which is a packet data convergence (PDC) 730 which is a packet data convergence (PDC) 731 which is a packet data convergence (P 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. 7B shows the NR user plane (UP) plane. As shown in FIG. 7(B), the NR UP protocol may be a protocol between the UE 122 and the gNB 102. That is, the NR UP protocol is terminated at the gNB 102 on the network side. As shown in FIG. 7B, the NR user plane protocol stack includes a PHY 700, a radio physical layer, a MAC 702, a medium access control layer, a RLC 704, a packet data convergence protocol layer, a PDCP 706, and a service data layer. It may be configured with an adaptation protocol layer (service data adaptation protocol layer) SDAP (Service Data Adaptation Protocol) 710 .

[0075] 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 be used. may not exist, and the E-UTRA protocol may have some different functions than the NR protocol.

[0076] In the present embodiment, the E-UTRA protocol and the NR protocol may not be distinguished from each other, and the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) of the E-UTRA protocol, and may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer) of the NR protocol. In addition, SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

[0077] In addition, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 are referred to as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or LTE, respectively. The PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 are also referred to as the E-UTRA PHY or LTE PHY, the E-UTRA MAC, or the LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or It may also be written as LTE RRC. Also, distinguish between E-UTRA protocols and NR protocols. In this case, PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 may be referred to as PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. Also, PHY 500, MAC 502, RLC 504, PDCP 506, and RRC 508 may be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0078] This section 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 referred to as a PHY entity. An entity that has some or all of the functionality of the MAC layer may be referred to as 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.

[0079] Note that data provided to lower layers from 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 the data provided to higher layers by MAC, RLC, PDCP, and SDAP may be called SDAP PDU. The data is 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.

[0080] Here, the base station device and the terminal device transmit signals in a higher layer. The higher layer may 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 transmit and receive MAC control elements in a Medium Access Control (MAC) 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 A parameter included in a higher layer signaling received by a terminal device may be referred to as a higher layer parameter. For example, in PHY layer processing, a higher layer means a higher layer seen from the PHY layer, and may mean one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, a higher layer may mean one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer, etc.

[0081] 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 a base station device, and the received A is given (provided) by the upper layer of the terminal device to a physical layer of the terminal device. For example, "higher layer parameters are provided" in the terminal device may be used. "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 an upper layer of the terminal device to a physical layer of the terminal device. Setting upper layer parameters in a terminal device may mean that upper layer parameters are given (provided) 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 sets the received upper layer parameters in the upper layer. However, setting upper layer parameters in a terminal device may include a case where the upper layer of the terminal device is provided with the upper layer parameters. This may include setting default parameters that are given in advance. When describing the 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" may be used. 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.), and therefore, the PDCP message corresponding to each SRB is 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.

[0082] An example of the function of the PHY will be described. 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 with respect to the PHY of the base station device. The PHY may have a function of transmitting data via a physical channel. The PHY may be connected to a higher MAC via a transport channel. The PHY may pass data to the MAC via the transport channel. The PHY may also pass 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.

[0083] 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.

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

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

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

[0087] The PDCCH is a downlink radio communication channel (radio communication from a base station device to a terminal device). To transmit (or carry) Downlink Control Information (DCI) Here, one or more DCIs (which may be referred to as DCI formats) may be defined for the transmission of downlink control information. That is, a field for downlink control information may be defined as DCI and mapped to information bits. The PDCCH may be a PDCCH candidate. The PDCCH may be transmitted in a search space. 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 PDCCH candidate may be monitored at configured monitoring occasions in one or more configured control resource sets (CORESETs) configured by the service configuration. The DCI format may be used for scheduling the PUSCH in the serving cell. The PUSCH may be used for transmitting user data, transmitting an RRC message (to be described later), and the like.

[0088] Explicitly linked by configuration provided by higher layers (RRC layer) By using two search space sets, PDCCH repetition may be operated. Also, 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 has the same number of control channel elements (CCEs) and coded bits. The IEEE 802.11b / g / n ...

[0089] The PUCCH is used in uplink wireless communication (wireless communication from a terminal device to a base station device). It 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 a downlink channel. The uplink control information may also include CSI (Channel State Information) used to request an Uplink Shared CHannel (UL-SCH) resource. The uplink control information may include a scheduling request (SR) used in the uplink control information. In addition, the uplink control information may include a hybrid automatic repeat reQuest ACKnowledgement (HARQ-ACK). may be included.

[0090] PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. In addition, the PDSCH may be used for transmitting system information (SI) and random access responses (RAR) in the case of downlink.

[0091] The PUSCH is used for uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or uplink The PUSCH may be used to transmit HARQ-ACK and / or CSI along with the link data, and the PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only the UCI. Also, the PDSCH or the PUSCH may be used to transmit an RRC message and a MAC CE, which will be 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 information specific to the terminal apparatus (UE specific) may be dedicated signaling for a certain terminal apparatus. The PUSCH may be transmitted using the signaling for the UE in the uplink. It may be used to transmit UE Capability.

[0092] 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 for synchronization (timing alignment) for uplink transmissions and to indicate a request for UL-SCH resources.

[0093] An example of the functions of the MAC will be described. The MAC may be called a MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by a logical channel identity (or logical channel ID). The MAC may be connected to the higher RLC via a logical channel. Depending on the type of information to be transmitted, the logical channels may be divided into a control channel that transmits control information and a traffic channel that transmits user information. The logical channels may also be divided into an uplink logical channel and a downlink logical channel. The MAC may be configured to transmit one or more different The MAC may have a function of multiplexing MAC SDUs belonging to different logical channels and providing them to the PHY. The MAC may also have a function of demultiplexing MAC PDUs provided from the PHY and providing them to a higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a function of reporting scheduling information. The MAC has the function of performing priority processing between terminal devices using dynamic scheduling. MAC may also have a function for performing priority processing between logical channels within one terminal device. The MAC provides a function for prioritizing overlapping resources within one terminal device. The 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 have the ability to select the transport format. The MAC may have the ability to perform Discontinuous Reception (DRX) and / or Discontinuous Transmission (DTX), random access, and other functions. The function to execute the Random Access (RA) procedure, notify the information of the available transmission power, - Power Headroom Report (PHR) function, Buffer Status Report (BSR) function to notify 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 include a MAC control element (MAC CE), which is an element for performing control in the MAC.

[0094] This section describes logical channels for the uplink (UL) and / or downlink (DL) used in E-UTRA and / or NR.

[0095] BCCH (Broadcast Control Channel) is used to transmit system information (SI), etc. It may be a downlink logical channel for broadcasting control information.

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

[0097] A Common Control Channel (CCCH) 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. In addition, the CCCH may be used between a base station device and multiple terminal devices.

[0098] A DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information in a point-to-point bidirectional manner 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.

[0099] A Dedicated Traffic Channel (DTCH) 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. The dedicated user data may be user data dedicated to each terminal device. The DTCH may exist in both the uplink and the downlink.

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

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

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

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

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

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

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

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

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

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

[0110] An example of the function of the RLC will be described. The RLC may be called an RLC sublayer. The E-UTRA RLC may have a function of segmenting and / or concatenating data provided from the PDCP of the upper layer and providing it to a lower layer. The E-UTRA RLC may perform reassembly and reordering of data provided from the lower layer. The 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 the PDCP of the layer that is independent of the sequence number added by the PDCP. The NR RLC may also have a function to segment data provided by the PDCP and provide it to a lower layer. The NR RLC may also have a function to reassemble data provided by the lower layer and provide it to a higher layer. The RLC may also have a function to retransmit data and / or a function to request retransmission (Automatic RLC may have a repeat reQuest (ARQ) function. RLC also has a function to correct errors by ARQ. The control information that is sent from the receiving side of the RLC to the transmitting side to perform ARQ and indicates the data that needs to be retransmitted may be called a status report. The status report transmission instruction sent by the RLC is 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 uni-directional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity. In UM, the RLC entity divides and / or combines data received from the upper layer, adds an RLC header, etc., but does not need to control retransmission of data. The UM RLC entity may be a uni-directional entity or a bi-directional entity. If the UM RLC entity is a uni-directional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If the UM RLC entity is If it is a bidirectional entity, the UM RRC 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 dividing and / or combining data received from a higher 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 TMD PDU. The data provided by the E-UTRA RLC may be called an AMD PDU. The RLC PDU format used in the NR RLC may be different from the RLC PDU format used in the NR RLC. In addition, the RLC PDU may be a data RLC PDU and a control RLC PDU. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). In addition, the control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU).

[0111] An example of the function of PDCP will be described. PDCP may be called a PDCP sublayer. PDCP may have a function for maintaining sequence numbers. PDCP also provides a mechanism for efficiently transmitting user data such as IP packets and Ethernet frames over wireless sections. The protocol used for IP packet header compression and decompression 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 a Header Compression Protocol (PDCP). PDCP may also have a function for encrypting and decrypting data. PDCP may also have a function for protecting and verifying the integrity of data. PDCP may also have a function for re-ordering. PDCP may also have a function for retransmitting PDCP SDUs. PDCP may also have a function for discarding data 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 the PDCP PDU format used in NR PDCP. There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0112] 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 a function to map the downlink QoS flow sent from the 5GC to the terminal device via the base station device with a data radio bearer (DRB), and / or map the uplink QoS flow sent from the terminal device to the 5GC via the base station device with a DRB. The SDAP may also have a function to store mapping rule information. The SDAP may also have a function to mark the QoS flow identifier (QoS Flow ID: QFI). The SDAP PDU may include an SDAP PDU for data and an SDAP PDU for control. The SDAP PDU for data is called an SDAP DATA PDU (SDAP Data PDU, SDAP Data PDU). Also, the SDAP PDU for control may be called SDAP CONTROL PDU (SDAP Control PDU). The SDAP entity of the terminal device may be called an SDAP control PDU (SDAP control PDU). One SDAP entity of the terminal device may exist for each PDU session.

[0113] 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. RRC may also have the Terminal Equipment Measurement Reporting and Terminal Equipment Measurement Reporting. 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 and terminal equipment measurement and reporting control, QoS management, radio link loss In addition, RRC messages and packets used in E-UTRA RRC may be used for The parameters may be different from the RRC message and parameters used in NR RRC. Note that the RRC message may include a plurality of information elements (IEs) for performing the above-mentioned control and the like.

[0114] 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. In addition, RRC messages sent using the DCCH are referred to as Dedicated RRC signaling, or RRC signaling.

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

[0116] 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 message may include an RRC System Info Request message, etc. Also, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. Also, other RRC messages may be included.

[0117] 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), and an RRC connection reestablishment reject message (RRC Connection Reestablishment Reject). Also, for example, an RRC reject message, an RRC setup message, etc. may be included. Also, other RRC messages may be included.

[0118] RRC signaling sent in the uplink (UL) direction using the DCCH includes, for example, measurement reports. The message may include, for example, a measurement report message, 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. 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.

[0119] RRC signaling sent in the downlink (DL) direction using the DCCH includes, for example, an RRC connection reconfiguration message, an RRC connection release message, and so on. The RRC signaling may include 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, 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.

[0120] 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 another layer.

[0121] The radio bearer will now be explained. When a terminal device communicates with a base station device, a radio bearer (RB) is established between the terminal device and the base station device to establish a wireless connection. A radio bearer used for CP may be called a Signaling Radio Bearer (SRB), and a radio bearer used for UP may be called a Data Radio Bearer (DRB). Each radio bearer has a Radio Bearer Identity (ID). A radio bearer identifier for an SRB may be assigned. A radio bearer identifier for a DRB may be referred to as an SRB identity (SRB ID). A radio bearer identifier for a DRB may be referred to as a DRB identity (DRB ID). SRB0 to SRB2 may be defined as the SRBs of E-UTRA, or other SRBs may be defined. SRB0 to SRB3 may be defined as the SRBs of NR, or other SRBs may be defined. SRB0 may be an SRB for RRC messages transmitted and / or received using the logical channel CCCH. SRB1 may be an SRB for RRC signaling and for NAS signaling before establishment of SRB2. A radio bearer identifier for a DRB may be assigned. A radio bearer identifier for a DRB may be assigned. The RRC signaling received may include piggybacked NAS signaling. All RRC and NAS signaling transmitted and / or received using SRB1 The logical channel DCCH may be used for signaling. SRB2 is used for NAS signaling and All RRC signaling and NAS signals transmitted and / or received using SRB2 may be transmitted using SRB1. A logical channel DCCH may be used for signaling. 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 RRC signaling may be an SRB for transmitting and / or receiving specific RRC signaling when All RRC and NAS signalling sent and / or received using SRB3 The logical channel DCCH may be used for this purpose, and other SRBs may be used for other purposes. The DRB may be a radio bearer for user data. The logical channel DTCH may be used for RRC signaling transmitted and / or received using the DRB.

[0122] 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 logical channels. The SRB0 is active in all states of the terminal equipment (RRC idle, RRC connected, RRC inactive, etc.). 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 logical channels. The RLC bearer of SRB2 may consist of an RLC entity of the AM and logical channels. One is established and / or configured in the terminal device by RRC signaling received from the station device. The SRB2 consists of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB2 may consist of an AM RLC entity and a logical channel. The PDCP on the base station 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, One may be established and / or configured in the terminal device by RRC signaling received by the terminal device 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 the SRB3 may consist of an RLC entity of the AM and a logical channel. The PDCP on the base station side of the SRB3 may be placed in the secondary node. The DRB is AS security. One or more DRBs may be established and / or configured in the terminal device by RRC signaling received from the base station device by the 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.

[0123] For an RLC bearer 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 an RLC bearer established and / or configured in a cell group consisting of NR, the RLC entity established and / or configured may be an E-UTRA RLC. When 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 end device, all bearer types are The PDCP entity established and / or configured for the radio bearer in may be an NR PDCP.

[0124] In NR, the DRB established and / or configured in the terminal device is one PDU session. In the terminal device, one SDAP entity can be associated with one PDU session. The SDAP entity, the PDCP entity, the RLC entity, and the logical channels 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.

[0125] Reference signal received power (RSRP) measured in the sidelink may be, for example, the following RSRP. In addition, the following RSRP may be referred to as SL-RSRP. (a) PSBCH RSRP (b) PSSCH RSRP (c) PSCCH RSRP

[0126] PSBCH-RSRP (PSBCH RSRP) is a set of multiple demodulation reference signals (DRMs) associated with the PSBCH. The power distribution of resource elements that transmit the Dynamic Multipath Reference Signal (DMRS) 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 values ​​of the RSRP 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, and in the case of multiple antenna ports, the values ​​of the RSRP for each antenna port may be summed. The power contribution of the resource elements carrying multiple associated DMRSs may be defined as the linear average of the power contributions of the resource elements carrying multiple associated DMRSs, e.g., for demodulating the 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. In addition, the terminal device may measure the RSRP (SD-RSRP) of the discovery message by using, for example, the power contribution of a resource element that transmits a DMRS associated with the discovery message.

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

[0128] The SL RSSI is the line of power ([W]) observed on the configured subchannels in 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 set from slot [na] to slot [n+b]. In addition, 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 (from slot [na] to slot [n-1]). The ratio may be defined as the percentage of subchannels that are

[0129] After discovering candidate L2 U2N Relay UEs and measuring the RSRP of the candidate L2 U2N Relay UEs, the L2 U2N Remote UE may report one or more candidate L2 U2N Relay UEs to the base station device. In addition, 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 measured RSRP of the candidate L2 U2N Relay UE is checked to see if it meets the L2 U2N Relay selection criteria. The L2 U2N Remote UE may determine whether or not the candidate L2 U2N Relay UE satisfies the selection criteria and matches the criteria of the higher layer to the base station device. When the L2 U2N Remote UE reports one or more candidate L2 U2N Relay UEs to the base station device, the L2 U2N Remote 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 a measurement result in the report to the base station device. Note that the measurement result may include identification information of the candidate L2 U2N Relay UE. 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).

[0130] In addition, the L2 U2N Remote UE having the serving L2 U2N Relay UE may include the serving L2 U2N Relay UE in the measurement result. The serving L2 U2N Relay UE may use RSRP (SL-RSRP) measured in sidelink communication with the serving L2 U2N Relay UE. If the measurement result does not allow SL-RSRP, 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.

[0131] There are two resource allocation modes for NR sidelink communication, Therefore, the mode in which the UE performs sidelink transmission using scheduled resources is called mode 1, and the mode in which the UE automatically selects resources and performs sidelink transmission is called mode 2. In mode 1, the UE must be RRC_CONNECTED, and in mode 2, the UE can perform sidelink transmission regardless of the RRC state or whether it is inside or outside NG-RAN. The UE then automatically selects resources available for sidelink transmission from one or more resource pools configured prior to the sidelink transmission.

[0132] Here, the band portion (BWP) will be described.

[0133] The BWP may be a part or the whole of the band of the serving cell. The BWP may also be called a carrier BWP. One or more BWPs are set in the terminal device. A BWP may be used to store system information associated with a synchronization signal detected during initial cell search. A BWP may be set by the information included in the initial cell search. A BWP may be a frequency bandwidth associated with a frequency band. For example, it may be set in Dedicated RRC signaling. Also, the downlink BWP (DL BWP) and an uplink BWP (UL BWP) may be configured separately. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. The correspondence between the BWP of the UE and the BWP of the downlink may be a default correspondence or may be determined by RRC signaling. The association may be by dedicated RRC signaling or by physical layer signaling. For example, the association may be based on downlink control information (DCI) notified on a downlink control channel, or a combination thereof. In addition, a CORESET may be set in a downlink BWP.

[0134] A BWP may be composed of a group of consecutive physical resource blocks (PRBs). In addition, the BWP (one or more) of each component carrier is sent to a terminal device in a connected state. The parameters of the BWP of each component carrier may be set. The data includes (A) the type of cyclic prefix, (B) the subcarrier spacing, and (C) the frequency location of the BWP (e.g., the start location or center frequency location of the BWP on the lower frequency side) (for example, the ARFCN may be used, or the offset from a specific subcarrier of the serving cell may be used). Alternatively, the offset may be set in units of subcarriers or resource blocks. Both the ARFCN and the offset may be set. (D) BWP bandwidth (e.g., number of PRBs), (E) resource setting information for the control signal, (F) center frequency position of the SS block (for example, the ARFCN may be used as the frequency position, or an offset from a specific subcarrier of the serving cell may be used. The offset may be in subcarrier units or in resource block units. In addition, the ARFCN and the In addition, resource configuration information of the control signal may be included in the configuration of at least some or all of the BWPs of the PCell and / or the PSCell.

[0135] The terminal device selects the Active BWP from among one or more configured BWPs. The terminal device may transmit and receive signals in one serving cell associated with the terminal device. In this case, one or more BWPs may be set. Among one or more BWPs configured for a serving cell, at most one uplink BWP and / or at most one downlink BWP shall be the Active BWP at any given time. The Active BWP in the downlink is also called Active DL BWP. The Active BWP is also called an Active UL BWP. In addition, among the BWPs set in the terminal device, a BWP that is not an Active BWP may be called an Inactive BWP. .

[0136] Next, a serving cell will be described. In a terminal device in an RRC connected state (RRC_CONNECTED) in which 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 is A PCell may refer to a 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) can use to transmit the RRC The PCell may be a cell used in an RRC connection establishment procedure when transitioning to a connected state. The PCell may also be a cell used in an RRC connection re-establishment procedure in which a terminal device re-establishes an RRC connection. The PCell may also be a cell used in a random access procedure during handover. The SpCell may also be a cell used for purposes other than those mentioned above.

[0137] 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. .

[0138] A cell group configured by a base station device for a terminal device will be described. A cell group may be composed of one SpCell. Also, a cell group may be composed of one SpCell and one or more SCells. and optionally one or more SCells. A loop may be expressed as a set of cell(s).

[0139] 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 configuration of the cell group may include a special cell configuration (information named spCellConfig). An information element named spCellConfigDedicated included in an information element named spCellConfig may include a cell configuration dedicated to the UE 122 set by this SpCellConfig. The information element named spCellConfigDedicated may be rephrased as SpCellConfigDedicated or SpCell dedicated setting. The information element named may include a BWP identifier parameter named firstActiveDownlinkBWP-Id, which will be described later. The configuration of the special cell 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 IE may be used to set parameters. In order to clarify that a certain term is an information element, the term "IE" may be added. For example, the 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.

[0140] 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.

[0141] Fig. 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 main components closely related to this embodiment. Show only.

[0142] 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, and the like from other terminal devices, a processor 502 that performs processing according to parameters included in the received control information, and and other terminal devices, control information (SCI, MAC control elements, RRC signaling, etc.) and discovery A transmission unit 504 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 processing unit 502 may receive information including control information (MAC control elements, RRC signaling, etc.) and user data from the base station device (gNB102). The transmitting unit 504 may transmit 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 section), RLC layer processing section (RLC processing section), PDCP layer processing section (PDCP processing section), SDAP processing section (SDAP processing section), RRC layer processing section (RRC processing section), PC5-S layer processing section (PC5-S processing section), Discovery layer processing section (Discover ry processing unit), and some or all of the application layer processing unit.

[0143] FIG. 6 is a block diagram showing the configuration of a base station device (gNB102) in this embodiment. In order to avoid complicating the description, FIG. 6 shows only the main components closely related to this embodiment. Only a portion is shown.

[0144] 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 to cause 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 includes a physical layer processor, a MAC layer processor, an RLC layer processor, a PDCP layer processor, an SDAP processor, an RRC layer processor, and one of the NAS layer processors. Part or all of the above may be included.

[0145] FIG. 10 shows an example of an embodiment of the present invention.

[0146] In step S1000, the UE 122 that has received the RRC signaling from the base station device A determination is made and, in step S1002, an action is taken based on the determination.

[0147] In step S1000, the condition may be, for example, some or all of the following conditions: It may be a part. (sa) The UE 122 acts as a remote terminal device. (sb) after applying the RRC signaling, no direct path is established to the UE (122); stomach.

[0148] In the condition (sa), the remote terminal device is an L2 U2N remote UE. It may be a L3 U2N remote UE, or it may be a terminal device that communicates with a base station device via a relay node. The disconnection is performed by disabling the relay setting used by the remote terminal device in the UE 122. Alternatively, the UE 122 may determine that a relay-related configuration used by a remote terminal device is applied to the UE 122 by the RRC signaling. Alternatively, the UE 122 may determine that a SRAP layer is configured by the base station device. Alternatively, the UE 122 may determine that a SRAP layer is configured by the RRC signaling. The condition (sb) may be that a direct path is not added by the RRC signaling, that only a non-direct path is used by the RRC signaling, or that the condition (sb) may be that a direct path is not added by the RRC signaling, or that only a non-direct path is used by the RRC signaling. This may be expressed in other words as being configured to communicate with a base station device using the same.

[0149] If it is determined that all of the above conditions are satisfied, in step S1002, For example, the remote terminal device may apply only the settings that need to be applied, or if it is determined that some or all of the conditions are not met, step S1002 In the above, the operation may be, for example, applying a configuration including a configuration that the remote terminal device needs to apply. Applying only a configuration that the remote terminal device needs to apply may include, for example, applying a configuration to the RRC signaling or system information in a special cell configuration. Applying the configuration, including the configuration that the remote terminal device needs to apply, may be, for example, in the configuration of a special cell, applying the RRC signaling Alternatively or additionally, a dedicated configuration of the special cell may be applied to T301, T310, and T311 based on the RRC signaling. If the special cell is included in the ring, the special cell is set according to the dedicated setting of the special cell. In addition or alternatively, the dedicated configuration of the special cell may be The first active uplink BWP identifier (firstActiveUplinkBWP-Id) is included in the If the special cell dedicated configuration is included in the RRC signaling, the BWP indicated by the ID may be considered to be the Active UL BWP, and in addition or instead, the special cell dedicated configuration may be included in the RRC signaling. The first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is included in the If included in the dedicated configuration of the special cell, the BWP indicated by the identifier may be considered to be an Active DL BWP.

[0150] The T301, the T310, and the T311 are timers that can be set in the UE 122. The following is an example of the operation of the UE 122 with respect to each of the above timers. The UE 122 may start T301 when it sends a re-establishment request, may stop T301 when it receives an RRC re-establishment message or an RRC setup message, when the selected cell or relay UE becomes unsuitable, etc., and may enter RRC_IDLE when T301 expires. The UE 122 may also start T310 when it detects a physical layer problem for a special cell, For example, when an RRC reconfiguration message including a reconfiguration IE with synchronization is received, when a command indicating a handover to another RAT is received from NR, when a connection re-establishment procedure is started, etc., the T310 may be stopped. When the T310 expires, the MCG The UE 122 may initiate a failure information procedure or may initiate a connection re-establishment procedure. The UE 122 may also initiate the T311 when it initiates a connection re-establishment procedure, and may select a suitable cell or resource. The T311 may be stopped when a layer UE is selected, and RRC_IDLE may occur when the T311 expires.

[0151] Another embodiment of the present invention will be described with reference to FIG.

[0152] In step S1000, the UE 122 that has received the RRC signaling from the base station device A determination is made and, in step S1002, an action is taken based on the determination.

[0153] In step S1000, the condition may be, for example, some or all of the following conditions: It may be a part. (wa) The UE 122 plays the role of a remote terminal device on the source side. (wb) after applying the RRC signaling, no non-direct path is established for the UE 122; stomach.

[0154] In the condition (wa), the remote terminal device is an L2 U2N remote UE. It may be a L3 U2N remote UE, or it may be a terminal device that communicates with a base station device via a relay node. The disconnection is performed by disabling the relay setting used by the remote terminal device in the UE 122. Alternatively, or in addition, the UE 122 may determine that a relay-related configuration used by a remote terminal device is applied to the UE 122. Alternatively, the base station device may determine that a SRAP layer has been configured by the RRC signaling. Alternatively, the base station device may determine that a SRAP layer has been configured by the RRC signaling. In addition, or alternatively, the UE 122 may act as a remote terminal. The condition (wb) may be that the non-direct path is released by the RRC signaling, that the non-direct path is released after applying the RRC signaling, and that the non-direct path is released after applying the RRC signaling. No direct path is established, and the UE 122 plays the role of a multipath remote terminal device. This can also be rephrased as ``not meeting the requirements.''

[0155] If it is determined in step S1000 that all of the above conditions are satisfied, the above operation in step S1002 is, for example, to transmit a unicast link to a higher layer (such as a ProSe layer) of a PC5 unicast link. In step S1000, the condition may be to trigger the release. If it is determined that any of the above conditions is not satisfied, the operation in step S1002 is, for example, It is also possible not to instruct an upper layer (such as a ProSe layer) to trigger the release of the PC5 unicast link. An upper layer (such as a ProSe layer) instructed by a lower layer (such as an RRC layer) to trigger the release of the PC5 unicast link may release the PC5 unicast link.

[0156] In addition, the remote terminal device in which the multipath is set (i.e., the multipath remote terminal device) A remote terminal device that is not configured for multipath may operate differently from a remote terminal device that is not configured for multipath. For example, when the UE 122 receives an RRC message including a reconfiguration IE with synchronization from a base station device, if the UE 122 determines that the UE 122 is a remote terminal device for which multipath is set, A remote terminal device in which the UE ID (newUE-Identity) included in the synchronized reconfiguration IE is not applied as the C-RNTI (Cell - Radio Network Temporary Identifier) ​​and multipath is not configured. If the UE 122 determines that the UE 122 is a UE that is a remote terminal device, the UE ID (newUE-Identity) included in the synchronization-attached reconfiguration IE may be applied as a C-RNTI. In addition, when the base station apparatus transmits an RRC message including a reconfiguration IE with synchronization to the UE 122, and when the UE 122 If the terminal is a multipath remote terminal before and after applying the RRC message, The station device transmits the ID of the UE included in the synchronization reconfiguration IE immediately before transmitting the RRC message. The ID may be the same as the UE ID set in the UE 122.

[0157] Conventional sidelink relay technology does not assume multipath relay, and when multipath relay is performed, the terminal device operates based on inappropriate decisions. The present invention reduces unnecessary operations of the terminal device and enables operation that appropriately applies signaling from the base station device.

[0158] In addition, in the above description, expressions such as "to be notified" and "to be pointed out" may be interchangeable.

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

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

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

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

[0163] Furthermore, in each of the process examples or process flow examples in the above description, some or all of the steps may not be executed. Furthermore, in each of the process examples or process flow examples in the above description, the order of the steps may be different. Furthermore, in each of the process examples or process flow examples in the above description, some or all of the processing within each step may not be executed. Furthermore, in each of the process examples or process flow examples in the above description, the order of the processing within each step may be different. Furthermore, in the above description, "doing B based on A being true" may be rephrased as "doing B". In other words, "doing B" is "being A" may be performed independently.

[0164] In the above explanation, "A may be replaced with B" means that A may be replaced with B as well as , B may be replaced with A. Also, in the above explanation, when it is written that "C may be D" and "C may be E", it may also include 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 include that "F may be H".

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

[0166] 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 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. The information is stored in non-volatile memory such as a memory or a hard disk drive (HDD) and is retrieved by the CPU as needed. Reading, modifying and writing are performed by this.

[0167] It should be noted that a part of the device in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing this control function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the control function. The "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

[0168] Furthermore, the term "computer-readable recording medium" includes those that dynamically hold a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in such a case. The program may be for implementing 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 realize this in combination with

[0169] Also, each functional block or feature of the device used in the above-described embodiment may be implemented or executed by an electric circuit, i.e., typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute 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 (PLC), or a combination of such circuits. The general purpose processor may include a general purpose 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. Also, when an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, an integrated circuit based on that technology may be used.

[0170] In addition, the present embodiment is not limited to the above-mentioned embodiment. In the embodiment, an example of the device has been described, but the present embodiment is not limited to this, and may be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices such as AV devices, kitchen devices, cleaning and washing machines, air conditioners, office devices, vending machines, and other household appliances. This can be applied to communication devices.

[0171] Although this embodiment has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes within the scope of the gist of this embodiment are also included. In addition, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. In addition, configurations in which elements described in the above embodiment are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0172] 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 terminal device that communicates with a base station device using a direct path and an indirect path, A direct path is a path through which the terminal device communicates with the base station device using the Uu interface. The aforementioned indirect path is a path through which the terminal device communicates with the base station device via a relay terminal device. A receiving unit that receives RRC messages from the base station device, It has a processing unit, The processing unit makes a setting according to the RRC message and, based on its determination that both of the two conditions are met, instructs the upper layer to trigger the release of the PC5 unicast link. The two conditions mentioned above are that (a) the terminal device acts as a remote terminal device on the source side, and (b) the indirect path is released by the RRC message. Terminal device.

2. A method for a terminal device to communicate with a base station device using a direct path and an indirect path, A direct path is a path through which the terminal device communicates with the base station device using the Uu interface. The aforementioned indirect path is a path through which the terminal device communicates with the base station device via a relay terminal device. The steps include receiving an RRC message from the base station device, The process includes the step of configuring according to the RRC message and, based on the determination that both of the two conditions are met, instructing the upper layer to trigger the release of the PC5 unicast link, The two conditions mentioned above are that (a) the terminal device acts as a remote terminal device on the source side, and (b) the indirect path is released by the RRC message. method.

3. An integrated circuit to be implemented in a terminal device that communicates with a base station device using a direct path and an indirect path, A direct path is a path through which the terminal device communicates with the base station device using the Uu interface. The aforementioned indirect path is a path through which the terminal device communicates with the base station device via a relay terminal device. The function of receiving RRC messages from the base station device, The terminal device is given the function of performing the settings according to the RRC message and, based on the determination that both of the two conditions are met, instructing the upper layer to trigger the release of the PC5 unicast link. The two conditions mentioned above are that (a) the terminal device is acting as a remote terminal device, and (b) the indirect path is released by the RRC message. Integrated circuit.

Images