Terminal device, method, and integrated circuit

Abstract

To provide a terminal device, a method, and an integrated circuit that efficiently provide a multicast / broadcast service (MBS) to a specific area in a non-terrestrial network providing the MBS.SOLUTION: In a terminal device communicating with a base station device, a receiving unit receives control information and / or area information related to an MBS provided in cells of the base station device. The control information includes information associating part or all of sessions in the MBS with the area information, and the area information are respectively information indicating part or all of the areas of the cells. On the basis of the fact that an MBS session receiving or interested in receiving information is not associated with any area information, or is associated with area information indicating an area where the terminal device is located, a processing unit regards a frequency at which the MBS session is provided as a frequency with the highest priority.SELECTED DRAWING: Figure 7

Description

Technical Field

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

Background Art

[0002] In the 3rd Generation Partnership Project (3GPP), which is a standardization project for cellular mobile communication systems, technical studies and standard setting for cellular mobile communication systems, including radio access, core network, services, etc., are being carried out.

[0003] For example, in 3GPP, E-UTRA (Evolved Universal Terrestrial Radio Access) was started for technical studies and standard setting as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th and 4th generations. Even now, in 3GPP, technical studies and standard setting for extended technologies of E-UTRA are being carried out. Note that E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and extended technologies may also be referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

[0004] In addition, in 3GPP, NR (New Radio, or NR Radio access) was started for technical studies and standard setting as a radio access technology (RAT) for cellular mobile communication systems for the 5th generation (5G). Even now, in 3GPP, technical studies and standard setting for extended technologies of NR

Prior Art Documents

Non-Patent Documents

[0005] [Non-Patent Document 1] 3GPP TS 38.331 v17.0.0, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specifications" pp70-116, pp218-223, pp316-1107 [Summary of the Invention] [Problems to be Solved by the Invention]

[0006] In 3GPP, as an extended technology of NR, for example, in the study of non-terrestrial networks (NTN: Non-Terrestrial Network), providing multicast / broadcast services is being considered. However, since the size of one cell provided by a satellite is large compared to that of a terrestrial network cell, it may be difficult to provide broadcast services for a specific area (e.g., within a country or a state).

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of the objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently provide multicast / broadcast services. [Means for Solving the Problems]

[0008] To achieve the above object, one aspect of the present invention takes the following means. That is, one aspect of the present invention is a terminal device that communicates with a base station device, and includes a receiving unit that receives control information regarding one or more multicast broadcast services (MBS) provided in the cell of the base station device, and one or more area information, and a processing unit. The control information includes a part or all of an MBS session, and one or more of the above-mentioned areas information. information including information associated with rear information, each of the area information being information indicating a part or all of the area of the cell, and the processing unit is interested in receiving or receiving an MBS session that is not associated with any of the area information or is associated with area information indicating the area where the terminal device is located. Based on this, the frequency at which the MBS session is provided is regarded as the highest priority frequency. or is associated with area information indicating the area where the terminal device is located, and based on this, the frequency at which the MBS session is provided is regarded as the highest priority frequency.

[0009] Another aspect of the present invention is a method applied to a terminal device that communicates with a base station device, the method including steps of receiving control information regarding one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more area information, the control information including information associating a part or all of an MBS session with one or more of the area information, each of the area information being information indicating a part or all of the area of the cell, and the processing unit determines that an MBS session that is being received or that the processing unit is interested in receiving is not associated with any of the area information or is associated with area information indicating the area where the terminal device is located, and based on this, the frequency at which the MBS session is provided is regarded as the highest priority frequency.

[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 causing the terminal device to perform a function of receiving control information regarding one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more area information, the control information including a part or all of an MBS session ​​​​information associating a part with one or more pieces of the area information, each of the area information being information indicating a part or all of the area of the cell, and the processing unit determines whether an MBS session being received or of interest to receive is associated with any of the area information is not associated with any of them, or is associated with area information indicating the area where the terminal device is located, and regards the frequency at which the MBS session is provided as the highest-priority frequency frequency.

[0011] Note that these general or specific aspects may be implemented by a system, apparatus, method, integrated circuit, computer program, or recording medium, or may be implemented by any combination of a system, apparatus, method, integrated circuit, computer program, and recording medium.

Advantages of the Invention

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

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Mode for Carrying Out the Invention

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

[0015] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (RAT). Also, LTE that can be connected with NR and Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. Also, LTE using 5GC in the core network (core network, Core Network: CN) may be distinguished from conventional LTE using EPC in the core network. Note that Conventional LTE may mean LTE that does not implement the technology standardized after Release 15 in 3GPP. This embodiment may be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR will be used for the description, but this embodiment may use other terms , and / or may be applied to other radio access technologies. Also, the term E-UTRA in this embodiment and the term LTE may be used interchangeably.

[0016] Note that in this embodiment, the names of each node and entity when the radio access technology is E-UTRA or NR, and the processing, etc. in each node and entity will be described, but this embodiment may be applied to other radio access technologies. The names of each node and entity, and the names of parameters and messages in this embodiment may be different names from the description of this embodiment.

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

[0018] E-UTRA 100 may be a radio access technology. Also, E-UTRA 100 may be an air interface between the UE 122 and the eNB 102. The air interface between the UE 122 and the eNB 102 may be called the Uu interface. The eNB (E-UTRAN Node B) 102 may be a base station device of E-UTRA 100. The eNB 102 may have the E-UTRA protocol described later. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described later. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol with respect to the UE 122. The radio access network composed of eNBs may be called E-UTRAN.

[0019] The EPC (Evolved Packet Core) 104 may be a core network. The interface 112 is an interface between the eNB 102 and the EPC 104, and may be called the S1 interface. The interface 112 may include a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 112 may terminate at a Mobility Management Entity (MME; not shown) in the EPC 104. The user plane interface of the interface 112 may terminate at a Serving Gateway (S-GW; not shown) in the EPC 104. The control plane interface of the interface 112 may be referred to as an S1-MME interface. The interface may be called the S1-U interface.

[0020] Note that one or more eNBs 102 may be connected to the EPC 104 via an interface 112. There may be an interface (not shown) between the multiple eNBs 102 that connect to the EPC 104. The interface between the multiple eNBs 102 that connect to the EPC 104 may be referred to as an X2 interface.

[0021] NR 106 may be a radio access technology. NR 106 may also be an air interface between UE 122 and gNB 108. The air interface between the UE 122 and the gNB 108 may be called a Uu interface. The gNB (g Node B) 108 may be a base station device of the NR 106. The gNB 108 may have the NR protocol described below. The NR protocol includes the NR User Plane (UP) protocol described below and the NR Control Plane (CP) protocol described below. The gNB 108 may be configured with an NR user plane (UP) protocol for the UE 122. It may terminate the NR control plane (CP) protocol, as well as the NR control plane (RCP) protocol.

[0022] The 5GC 110 may be a core network. The interface 116 is an interface between the gNB 108 and the 5GC 110. The interface 116 may be a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. There may be a control plane interface for the interface 116. The access point should be terminated by the Access and Mobility Management Function (AMF: not shown) in the 5GC110. The user plane interface of the interface 116 may terminate in a User Plane Function (UPF: not shown) in the 5GC 110. The control plane interface of the interface 116 may be referred to as an NG-C interface. The user plane interface of the interface 116 may be referred to as an NG-U interface.

[0023] Note that one or more gNBs 108 may be connected to the 5GC 110 via an interface 116. There may be an interface (not shown) between multiple gNBs 108 connected to the 5GC 110. The interface between multiple gNBs 108 connected to the 5GC 110 may be referred to as an Xn interface.

[0024] The eNB 102 may have a function to connect to the 5GC 110. The eNB 102 having a function to connect to the 5GC 110 may be called an ng-eNB. The interface 114 is an interface between the eNB 102 and the 5GC 110, and is an NG The interface 114 may be referred to as a control plane through which control signals pass. There exists a user plane interface through which user data passes. This may be done. The control plane interface of interface 114 may terminate at the AMF within 5GC110. The user plane interface of interface 114 may terminate at the UPF within 5GC110. The control plane interface of interface 114 may be referred to as the NG-C interface This may be done. The user plane interface of interface 114 may be referred to as the NG-U interface This may be done. A radio access network composed of ng-eNB or gNB may be referred to as NG-RAN This may be done. NG-RAN, E-UTRAN, etc. may simply be referred to as the network. Also, the network may include eNB, ng-eNB, gNB, etc.

[0025] Note that one or more eNBs 102 may be connected to 5GC110 via interface 114 . An interface may exist (not shown) between multiple eNBs 102 connected to 5GC110. The interface between multiple eNBs 102 connected to 5GC110 may be referred to as the Xn interface. Also, the eNB 102 connected to 5GC110 and the gNB 108 connected to 5GC110 may be connected via interface 120. The interface 120 between the eNB 102 connected to 5GC110 and the gNB 108 connected to 5GC110 may be referred to as the Xn interface.

[0026] gNB 108 may have the function of connecting to EPC104. A gNB 108 having the function of connecting to EPC104 may be referred to as an en-gNB. Interface 118 is the interface between gNB 108 and EPC104 and may be referred to as the S1 interface. Interface 118 may have a user plane interface through which user data passes . The user plane interface of interface 118 may terminate at the S-GW (not shown) within EPC104. The user plane interface of interface 118 The interface may be referred to as the S1-U interface. Also, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected by the interface 120. The interface 120 between the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be referred to as the X2 interface.

[0027] The interface 124 is an interface between the EPC 104 and the 5GC 110, and may be an interface that passes only the CP, or only the UP, or both the CP and the UP. Also, some or all of the interfaces such as the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by a telecommunications carrier or the like.

[0028] The UE 122 may be a terminal device capable of receiving system information and paging messages transmitted from the eNB 102 and / or the gNB 108. Also, the UE 122 may be a terminal device capable of establishing a radio connection with the eNB 102 and / or the gNB 108. Also, the UE 122 may be a terminal device capable of simultaneously establishing a radio connection with the eNB 102 and the gNB 108. The UE 122 may have the E-UTRA protocol and / or the NR protocol. Note that the radio connection may be a Radio Resource Control (RRC) connection.

[0029] Also, the UE 122 may communicate with the EPC 104 and / or the 5GC 110 via the eNB 102 and / or the gNB 108. It may be a terminal device capable of making a connection. When the core network to which eNB102 and / or gNB108 with which UE122 communicates is EPC104, each data radio bearer (DRB) described below established between UE122 and eNB102 and / or gNB108 may be further uniquely associated with each EPS (Evolved Packet System) bearer passing through EPC104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Also, the same QoS may be guaranteed for IP packets and data such as Ethernet (registered trademark) frames passing through the same EPS bearer. It may pass through each EPS bearer. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Also, the same QoS may be guaranteed for IP packets passing through the same EPS bearer and data such as Ethernet (registered trademark) frames.

[0030] Also, when the core network to which eNB102 and / or gNB108 with which UE122 communicates is 5GC110, each DRB established between UE122 and eNB102 and / or gNB108 may be further associated with one of the PDU (Packet Data Unit) sessions established within 5GC110. One or more QoS flows may exist in each PDU session. Each DRB may be associated (mapped) with one or more QoS flows, or may not be associated with any QoS flow. Each PDU session may be identified by a PDU session identifier (Identity, or ID). Also, each QoS flow may be identified by a QoS flow identifier (Identity, or ID). Also, the same QoS may be guaranteed for IP packets and data such as Ethernet frames passing through the same QoS flow.

[0031] There may be no PDU session and / or QoS flow in EPC104. Also, there may be no EPS bearer in 5GC110. When UE122 is connected to EPC104, UE122 has information on EPS bearers, but may not have information on PDU sessions and / or QoS flows. ​​​​​When the UE 122 is connected to the 5GC 110, the UE 122 has information within the PDU session and / or QoS flow, but does not necessarily have information on the EPS bearer. In addition, in the following description, the eNB 102 and / or gNB 108 are also simply referred to as base station apparatuses, and the UE 122 is also simply referred to as a terminal apparatus or UE.

[0032] In addition, in the following description, the eNB 102 and / or gNB 108 are also simply referred to as base station apparatuses, and the UE 122 is also simply referred to as a terminal apparatus or UE.

[0033] FIG. 2 is a diagram of an example of the E-UTRA protocol architecture according to the present embodiment. FIG. 3 is a diagram of an example of the NR protocol architecture according to the present embodiment. 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. In the present embodiment, the uplink (UL) may be a link from the terminal apparatus to the base station apparatus. Also, in the present embodiment, the downlink (DL) may be a link from the base station apparatus to the terminal apparatus. Also, in the present embodiment, the sidelink (SL) may be a link from the terminal apparatus to the terminal apparatus without passing through the base station apparatus. 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. In the present embodiment, the uplink (UL) may be a link from the terminal apparatus to the base station apparatus. Also, in the present embodiment, the downlink (DL) may be a link from the base station apparatus to the terminal apparatus. Also, in the present embodiment, the sidelink (SL) may be a link from the terminal apparatus to the terminal apparatus without passing through the base station apparatus. FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol terminated at the eNB 102 on the network side. As shown in FIG. 2(A), the E-UTRA user plane protocol stack includes the PHY (Physical layer) 200 which is the radio physical layer, and the MAC (Medium Access Control layer) which is the medium access control layer. FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol terminated at the eNB 102 on the network side. As shown in FIG. 2(A), the E-UTRA user plane protocol stack includes the PHY (Physical layer) 200 which is the radio physical layer, and the MAC (Medium Access Control layer) which is the medium access control layer. FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol terminated at the eNB 102 on the network side. As shown in FIG. 2(A), the E-UTRA user plane protocol stack includes the PHY (Physical layer) 200 which is the radio physical layer, and the MAC (Medium Access Control layer) which is the medium access control layer. FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol terminated at the eNB 102 on the network side. As shown in FIG. 2(A), the E-UTRA user plane protocol stack includes the PHY (Physical layer) 200 which is the radio physical layer, and the MAC (Medium Access Control layer) which is the medium access control layer.

[0034] FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol terminated at the eNB 102 on the network side. As shown in FIG. 2(A), the E-UTRA user plane protocol stack includes the PHY (Physical layer) 200 which is the radio physical layer, and the MAC (Medium Access Control layer) which is the medium access control layer. As shown in FIG. 2(A), the E-UTRA user plane protocol stack includes the PHY (Physical layer) 200 which is the radio physical layer, and the MAC (Medium Access Control layer) which is the medium access control layer. It may be composed of a Medium Access Control (MAC) 202, a Radio Link Control (RLC) 204 which is a radio link control layer, and a Packet Data Convergence Protocol (PDCP) 206 which is a packet data convergence protocol layer.

[0035] Figure 3(A) is a diagram of an NR user plane (UP) protocol stack. As shown in Figure 3(A), the NR UP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol terminated at the gNB 108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack may be composed of a Physical (PHY) layer 300 which is a radio physical layer, a Medium Access Control (MAC) layer 302, a Radio Link Control (RLC) layer 304, a Packet Data Convergence Protocol (PDCP) layer 306, and a Service Data Adaptation Protocol (SDAP) 310 which is a service data adaptation protocol layer.

[0036] Figure 2(B) is a diagram of an E-UTRA control plane (CP) protocol configuration. As shown in Figure 2(B), in the E-UTRA CP protocol, a Radio Resource Control (RRC) 208 which is a radio resource control layer may be a protocol between the UE 122 and the eNB 102. That is, the RRC 208 may be a protocol terminated at the eNB 102 on the network side. Also, in the E-UTRA CP protocol, a Non-Access Stratum (NAS) 210 which is a non-AS layer may be a protocol between the UE 122 and the MME. That is, the NAS 210 may be a protocol terminated at the MME on the network side.

[0037] Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in Figure 3(B), in the NR CP protocol, the radio resource control layer RRC308 may be the protocol between UE122 and gNB108. That is, RRC308 may be the protocol that terminates at gNB108 on the network side. Also, in the NR CP protocol, the non-access stratum NAS312 may be the protocol between UE122 and AMF. That is, NAS312 may be the protocol that terminates at AMF on the network side.

[0038] Note that the AS (Access Stratum) layer may be the layer that terminates between UE122 and eNB102 and / or gNB108. That is, the AS layer may be a layer that includes some or all of PHY200, MAC202, RLC204, PDCP206, and RRC208, and / or a layer that includes some or all of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308.

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

[0040] Also, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol hereinafter, PHY200, MAC202, RLC204, PDCP206, and RRC208 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 LTE PDCP, and RRC for E-UTRA or RRC for LTE, respectively. Also, PHY200, MAC202, RLC204, PDCP206, and RRC208 may be described 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, etc. Also, when distinguishing between the E-UTRA protocol and the NR protocol PHY300, MAC302, RLC304, PDCP306, RRC308 may be referred to as PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. Also, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc. in some cases.

[0041] An entity in the AS layer of E-UTRA and / or NR will be described. An entity having some or all of the functions of the MAC layer may be called a MAC entity. An entity having some or all of the functions of the RLC layer may be called an RLC entity. An entity having some or all of the functions of the PDCP layer may be called a PDCP entity Entities that possess some or all of the functions of the SDAP layer may be referred to as SDAP entities. Entities that possess some or all of the functions of the RRC layer may be referred to as RRC entities. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be respectively rephrased as MAC, RLC, PDCP, SDAP, and RRC.

[0042] Note that the data provided by the lower layer to MAC, RLC, PDCP, and SDAP, and / or the data provided by the lower layer to MAC, RLC , PDCP, and SDAP may be respectively referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU. Also, the data provided by the upper layer to MAC, RLC, PDCP, and SDAP, and / or the data provided by MAC, RLC, PDCP, and SDAP to the upper layer may be respectively referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU. Also, the segmented RLC SDU may be referred to as the RLC SDU segment.

[0043] Here, the base station device and the terminal device exchange signals in the upper layer (higher layer). The higher layer may also be referred to as the upper layer and they may be used interchangeably. For example, the base station device and the terminal device may exchange RRC messages (also referred to as RRC messages or RRC signalling) in the Radio Resource Control (RRC) layer. Also, the base station device and the terminal device may exchange MAC control elements in the MAC (Medium Access Control) layer. Also, the RRC layer of the terminal device acquires the system information notified by the base station device. Here, the RRC message, system information, and ​ and / or, the MAC control element is also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). 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, in the processing of the PHY layer, the higher layer means the higher layer seen from the PHY layer, and may mean one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc. signaling) or a higher layer parameter (higher layer parameter). 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, in the processing of the PHY layer, the higher layer means the higher layer seen from the PHY layer, and may mean one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0044] Hereinafter, the meaning of "A is given (provided) at the higher layer" or "A is given (provided) by the higher layer" may mean that the higher layer (mainly the RRC layer, MAC layer, etc.) of the terminal device receives A from the base station device, and the received A is given (provided) from the higher layer of the terminal device to the lower layer (mainly the MAC layer and the physical layer) of the terminal device. For example, in the terminal device, "a higher layer parameter is provided" may mean that the terminal device receives a higher layer signal from the base station device, and the higher layer parameter included in the received higher layer signal is provided from the higher layer of the terminal device to the lower layer of the terminal device. That the higher layer parameter is set in the terminal device may mean that the higher layer parameter is given (provided) to the terminal device. For example, that the higher layer parameter is set in the terminal device may mean that the terminal device receives a higher layer signal from the base station device and sets the received higher layer parameter at the higher layer. However, that the higher layer parameter is set in the terminal device may include that the default parameter previously given to the higher layer of the terminal device is set. When explaining that the terminal device transmits an RRC message to the base station device and / or, the MAC control element is also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). 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, in the processing of the PHY layer, the higher layer means the higher layer seen from the PHY layer, and may mean one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc. and / or, the MAC control element is also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). 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, in the processing of the PHY layer, the higher layer means the higher layer seen from the PHY layer, and may mean one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc. There may be a case where an expression of submitting a message from the RRC entity of the terminal device to a lower layer is used. In the terminal device, "submitting a message to a lower layer" from the RRC entity may mean submitting a message to the PDCP layer. In the terminal device, "submitting a message to a lower layer" from the RRC layer means that the RRC message is transmitted using an SRB (such as SRB0, SRB1, SRB2, SRB3), so it may mean submitting a message to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc. An example of the function of the PHY will be described. The PHY of the terminal device may have a function of receiving data transmitted via a downlink physical channel from the PHY of the base station device. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink physical channel. The PHY may be connected to the upper MAC via a transport channel. The PHY may transfer data to the MAC via the transport channel. Also, the PHY may be provided with data from the MAC via the transport channel. In the PHY, an RNTI (Radio Network Temporary Identifier) may be used to identify various control information. From the RRC layer in the terminal device, "submit a message to the lower layer" means that the RRC message is transmitted using an SRB (such as SRB0, SRB1, SRB2, SRB3), so it may mean submitting a message to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc. Since the RRC message is transmitted using an SRB (such as SRB0, SRB1, SRB2, SRB3), it may mean submitting a message to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc. It may mean submitting a message to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc. It may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0045] An example of the function of the PHY will be described. The PHY of the terminal device may have a function of receiving data transmitted via a downlink physical channel from the PHY of the base station device. The PHY of the terminal device may have a function of receiving data transmitted via a downlink physical channel from the PHY of the base station device. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink physical channel. The PHY may be connected to the upper MAC via a transport channel. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink physical channel. The PHY may be connected to the upper MAC via a transport channel. The PHY may transfer data to the MAC via the transport channel. Also, the PHY may be provided with data from the MAC via the transport channel. In the PHY, an RNTI (Radio Network Temporary Identifier) may be used to identify various control information.

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

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

[0048] PBCH may be used to notify the system information required by the terminal device.

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

[0050] PDCCH may be used to transmit (or carry) the downlink control information (DCI) in downlink wireless communication (wireless communication from the base station device to the terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) may be defined for the transmission of the downlink control information. That is, the fields for the downlink control information may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate link control information (Downlink Control Information:DCI) to be transmitted (or carried). Here, for the transmission of the downlink control information, one or more DCIs (which may also be referred to as DCI formats) may be defined. That is, the fields for the downlink control information may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate set. It may be transmitted in a candidate. 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. Also, the terminal device may search for In one or more configured monitoring occasions within a configured control resource set (CORESET) set by the search space configuration, the terminal device may monitor PDCCH candidates. The DCI format may be used for scheduling PUSCH in the serving cell. PUSCH may be used for transmitting user data, transmitting RRC messages described later, etc.

[0051] PUCCH may be used to transmit uplink control information (Uplink Control Information: UCI) in uplink wireless communication (wireless communication from the terminal device to the base station device). Here, the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel. Also, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources. Also, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement). It may be included.

[0052] ​The PDSCH may be used for transmitting downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. Also, in the case of downlink, the PDSCH may be used for transmitting system information (SI: System Information), random access response (RAR: Random Access Response), etc.

[0053] The PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer or to transmit HARQ-ACK and / or CSI together with the uplink data. Also, 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 UCI. Also, the PDSCH or PUSCH may be used to transmit RRC messages and the MAC CE described later. Here , in the PDSCH, the RRC message transmitted from the base station device may be common signaling for a plurality of terminal devices within the cell. Also, the RRC message transmitted from the base station device may be dedicated signaling for a certain terminal device. That is, UE specific information may be transmitted using dedicated signaling for a certain terminal device. Also, the PUSCH may be used to transmit the UE's capability (UE Capability) in the uplink.

[0054] The PRACH may be used to transmit a random access preamble. The PRACH is used in the initial connection establishment procedure, handover procedure, connection re-establishment procedure, up It may be used to indicate synchronization (timing adjustment) for link transmission and requests for UL-SCH resources.

[0055] An example of the MAC function will be described. The MAC may be referred to as the MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by logical channel identifiers (or Logical Channel IDs). The MAC may be connected to the upper RLC via the logical channels. The logical channels may be divided into a control channel for transmitting control information and a traffic channel for transmitting user information according to the type of information to be transmitted. Also, the logical channels may be divided into an uplink logical channel and a downlink logical channel. The MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY. Also, the MAC may have a function of demultiplexing the MAC PDUs provided from the PHY and providing them to the upper layer via the logical channels to which each MAC SDU belongs. Also, the MAC may have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). Also, the MAC may have a scheduling report function of reporting scheduling information. The MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Also, the MAC may have a function of performing priority processing between logical channels within one terminal device. Also, the MAC may have a function of performing priority processing for overlapping resources within one terminal device. 。 。 。 This is acceptable. The MAC may have a function to identify Multimedia Broadcast Multicast Services (MBMS). Also, the NR MAC may have a function to identify Multicast Broadcast Service (MBS). The MAC may have a function to select a transport format. This is acceptable. The MAC may have a function to perform discontinuous reception (DRX) and / or discontinuous transmission (DTX), a function to execute a random access (RA) procedure, a Power Headroom Report (PHR) function to notify information on transmit power, a Buffer Status Report (BSR) function to notify data volume information of a transmission buffer, etc. The NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. Also, the MAC PDU may include a MAC control element (MAC CE), which is an element for control in the MAC.

[0056] The uplink (UL) and / or downlink (DL) logical channels used in E-UTRA and / or NR will be described.

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

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

[0059] The CCCH (Common Control Channel) may be a logical channel for transmitting control information between a terminal device and a base station device. The CCCH may be used when the terminal device does not have an RRC connection. Also, the CCCH may be used between a base station device and a plurality of terminal devices.

[0060] The DCCH (Dedicated Control Channel) may be a logical channel for transmitting dedicated control information in a one-to-one (point-to-point) and bi-directional 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. 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.

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

[0062] The MCCH (Multicast Control Channel) may be a one-to-many (point-to-multipoint) downlink channel for sending MBMS control information for one or more MTCHs from a base station device to terminal devices. The MCCH may be a logical channel for multicast and / or broadcast. The MCCH is provided in the cell where the MCCH is transmitted for MBS broadcasts. The MCCH may be a one-to-many (point-to-multipoint) downlink channel for sending MBMS control information for one or more MTCHs from a base station device to terminal devices. The MCCH may be a logical channel for multicast and / or broadcast. The MCCH is provided in the cell where the MCCH is transmitted for MBS broadcasts. It may carry the configuration (MBS Broadcast Configuration).

[0063] MTCH (Multicast Traffic Channel) may be a one-to-many (point-to-multipoint) downlink channel for transmitting data from the base station apparatus to the terminal apparatus. MTCH may be a logical channel for multicast and / or broadcast. It may be a logical channel for multicast and / or broadcast.

[0064] The mapping between the logical channel and the transport channel for the uplink in E-UTRA and / or NR will be described. will be described.

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

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

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

[0068] The mapping between the logical channel and the transport channel for the downlink in E-UTRA and / or NR will be described. will be described.

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

[0070] The PCCH may be mapped to the PCH (Paging Channel), which is a downlink transport channel. It may be.

[0071] The CCCH may be mapped to the DL-SCH (Downlink Shared Channel), which is a downlink transport channel. It may be mapped thereto.

[0072] The DCCH may be mapped to the DL-SCH (Downlink Shared Channel), which is a downlink transport channel. It may be mapped thereto.

[0073] The DTCH may be mapped to the DL-SCH (Downlink Shared Channel), which is a downlink transport channel. It may be mapped thereto.

[0074] The MCCH may be mapped to the DL-SCH (Downlink Shared Channel), which is a downlink transport channel. It may be mapped thereto.

[0075] The MTCH may be mapped to the DL-SCH (Downlink Shared Channel), which is a downlink transport channel. It may be mapped thereto.

[0076] An example of the function of the RLC will be described. The RLC may also be referred to as the RLC sublayer. The E-UTRA RLC may have a function of segmenting and / or concatenating the data provided from the upper-layer PDCP and providing it to the lower layer. The E-UTRA RLC may have a function of performing reassembly and re-ordering on the data provided from the lower layer and providing it to the upper layer. The NR RLC is the upper layer The data provided from the PDCP of the layer may have a function of adding a sequence number independent of the sequence number added by the PDCP. Also, the NR RLC may have a function of segmenting the data provided from the PDCP and providing it to the lower layer. Further, the NR RLC may have a function of performing reassembly on the data provided from the lower layer and providing it to the upper layer. Also, the RLC may have a function of retransmitting data and / or a retransmission request function (Automatic Repeat reQuest: ARQ). Additionally, the RLC may have a function of performing error correction by ARQ. To perform ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of the RLC to the transmitting side, may be referred to as a status report. Also, the thing called a status report transmission instruction sent from the transmitting side of the RLC to the receiving side may be referred to as a poll. Further, the RLC may have a function of detecting data duplication. Also, the RLC may have a function of discarding data. The RLC may have three modes: transparent mode (TM: Transparent Mode), unacknowledged mode (UM: Unacknowledged Mode), and acknowledged mode (AM: Acknowledged Mode). In TM, the data received from the upper layer is not segmented, and the addition of the RLC header may not be performed. The TM RLC entity is a unidirectional entity and may be set as a transmitting TM RLC entity or a receiving TM RLC entity. In UM, the segmentation and / or combination of the data received from the upper layer, the addition of the RLC header, etc. are performed, but in the UM, the segmentation and / or combination of the data received from the upper layer, the addition of the RLC header, etc. are performed, but , Data retransmission control may not be performed. The UM RLC entity may be a unidirectional entity or a bi-directional entity. When the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. When the UM RLC entity is a bi-directional entity, the UM RLC entity may be configured as a UM RLC entity composed of a transmitting side and a receiving side. In AM It may perform splitting and / or combining of data received from the upper layer, addition of an RLC header, data retransmission control, etc. The AM RLC entity is a bi-directional entity and may be configured as an AM RLC composed of a transmitting side and a receiving side . Note that the data provided to the lower layer in TM, and / or the data provided from the lower layer may be called a TMDPDU. Also, the data provided to the lower layer in UM, and / or the data provided from the lower layer may be called a UMDPDU. Also, the data provided to the lower layer in AM, or the data provided from the lower layer may be called an AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Also, the RLC PDU may include a data RLC PDU and a control RLC PDU. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU, RLC data PDU). Also, the control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).

[0077] An example of the functions of PDCP will be described. PDCP may be referred to as the PDCP sublayer. PDCP may have a function of maintaining sequence numbers. Also, PDCP may have a header compression / decompression function for efficiently transmitting user data such as IP packets and Ethernet frames in the radio section. The protocol used for header compression / decompression of IP packets may be called the ROHC (Robust Header Compression) protocol. Also, the protocol used for header compression / decompression of Ethernet frame headers may be called the EHC (Ethernet (registered trademark) Header Compression) protocol. Also, PDCP may have a function of encrypting / decrypting data. Also, PDCP may have a function of protecting data integrity / verifying data integrity. Also, PDCP may have a re-ordering function. Also, PDCP may have a retransmission function of PDCP SDUs. Also, PDCP may have a function of discarding data using a discard timer. Also, PDCP may have a duplication function. Also, PDCP may have a function of discarding duplicate received data. The PDCP entity may be a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU). For transmission, it may have a header compression / decompression function. The protocol used for header compression / decompression of IP packets may be called the ROHC (Robust Header Compression) protocol. Also, the protocol used for header compression / decompression of Ethernet frame headers may be called the EHC (Ethernet (registered trademark) Header Compression) protocol. Also, PDCP may have a function of encrypting / decrypting data. Also, PDCP may have a function of protecting data integrity / verifying data integrity. Also, PDCP may have a re-ordering function. Also, PDCP may have a retransmission function of PDCP SDUs. Also, PDCP may have a function of discarding data using a discard timer. Also, PDCP may have a duplication function. Also, PDCP may have a function of discarding duplicate received data. The PDCP entity may be a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU). The protocol used for header compression / decompression of Ethernet frame headers may be called the EHC (Ethernet (registered trademark) Header Compression) protocol. Also, PDCP may have a function of encrypting / decrypting data. Also, PDCP may have a function of protecting data integrity / verifying data integrity. Also, PDCP may have a re-ordering function. Also, PDCP may have a retransmission function of PDCP SDUs. Also, PDCP may have a function of discarding data using a discard timer. Also, PDCP may have a duplication function. Also, PDCP may have a function of discarding duplicate received data. The PDCP entity may be a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU). Header Compression) protocol. Also, PDCP may have a function of encrypting / decrypting data. Also, PDCP may have a function of protecting data integrity / verifying data integrity. Also, PDCP may have a re-ordering function. Also, PDCP may have a retransmission function of PDCP SDUs. Also, PDCP may have a function of discarding data using a discard timer. Also, PDCP may have a duplication function. Also, PDCP may have a function of discarding duplicate received data. The PDCP entity may be a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU). Also, PDCP may have a function of discarding duplicate received data. The PDCP entity may be a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU). There may be data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU).

[0078] An example of the function of SDAP will be described. SDAP is the Service Data Adaptation Protocol layer (Service Data Adaptation Protocol layer). SDAP may have a function of associating (mapping) a downlink QoS flow sent from the 5GC 110 to a terminal device via a base station device with a data radio bearer (DRB), and / or mapping an uplink QoS flow sent from the terminal device to the 5GC 110 via the base station device with a DRB. Also, SDAP may have a function of storing mapping rule information. Also, SDAP may have a function of marking a QoS flow identifier (QoS Flow ID: QFI). Note that the SDAP PDU may include a data SDAP PDU and a control SDAP PDU. The data SDAP PDU may be called an SDAP DATA PDU (SDAP Data PDU, SDAP data PDU). Also, the control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that there may be one SDAP entity for a PDU session in the terminal device.

[0079] An example of the function of RRC will be described. RRC may have a notification (broadcast) function. RRC may have a call (paging) function from the EPC 104 and / or the 5GC 110. RRC may have a call (paging) function from an eNB 102 connected to the gNB 108 or the 5GC 110. Also, RRC may have an RRC connection management function. Also, RRC may have a radio bearer control function. Also, RRC may have a cell group control function. Also, RRC may have a mobility control function. Also, RRC may have a terminal device measurement reporting and terminal device measurement reporting control function. Also, RRC may have a QoS management function.​ It may have capabilities. Also, RRC may have functions for detecting and recovering from radio link failures. RRC may use RRC messages to perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, UE measurement reporting and UE measurement reporting control, QoS management, detection and recovery from radio link failures, etc. Note that the RRC messages and parameters used in E-UTRA RRC may be different from those used in NR RRC. They may be different.

[0080] RRC messages may be sent using the BCCH of the logical channel. In addition to or instead of that, RRC messages may be sent using the PCCH of the logical channel. In addition to or instead of that, RRC messages may be sent using the CCCH of the logical channel. In addition to or instead of that, RRC messages may be sent using the CCCH of the logical channel. In addition to or instead of that, RRC messages may be sent using the DCCH of the logical channel. In addition to or instead of that, RRC messages may be sent using the DCCH of the logical channel. In addition to or instead of that, RRC messages may be sent using the MCCH of the logical channel. Also, RRC messages sent using the DCCH are referred to as dedicated RRC signaling or RRC signaling. RRC messages sent using the DCCH are referred to as dedicated RRC signaling or RRC signaling.

[0081] RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), each type of System Information Block (SIB), or other RRC messages. RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.

[0082] RRC messages sent in the uplink (UL) direction using the CCCH may include, for example, an RRC setup request message (RRC Setup Request), an RRC resume request message (RRC Resume Request), an RRC reestablishment request message (RRC Reestablishment Request), an RRC system information request mess age (RRC System Info Request), etc. Further, for example, an RRC connection request message (RRC Connection Request), an RRC connection resume request message (RRC Connection Resume Request), an RRC connection reestablishment request message (RRC Connection Reestablishment Request), etc. may be included. Further, other RRC messages may be included.

[0083] RRC messages sent in the downlink (DL) direction using the CCCH may 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), an RRC connection reestablishment reject message (RRC Connection Reestablishment Reject), etc. Further, for example, an RRC reject message (RRC Reject), an RRC setup message (RRC Setup), etc. may be included. Further, other RRC messages may be included.

[0084] RRC signaling sent in the uplink (UL) direction using the DCCH may include, for example, a measurement report It may include a message (Measurement Report), an RRC connection reconfiguration complete message (RRC Connection Reconfiguration Complete), an RRC connection setup complete message (RRC Connection Setup Complete), an RRC connection reestablishment complete message (RRC Connection Reestablishment Complete), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), etc. For example, it may also include a measurement report message (Measurement Report), an RRC reconfiguration complete message (RRC Reconfiguration Complete), an RRC setup complete message (RRC Setup Complete), an RRC reestablishment complete message (RRC Reestablishment Complete), an RRC resume complete message (RRC Resume Complete), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), etc. It may include an RRC setup complete message (RRC Setup Complete), an RRC reestablishment complete message (RRC Reestablishment Complete), an RRC resume complete message (RRC Resume Complete), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), etc. It may also include other RRC signaling.

[0085] RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, an RRC connection reconfiguration message (RRC Connection Reconfiguration), an RRC connection release message (RRC Connec (Initial Release), Security Mode Command message, UE Capability Enquiry message, etc. may be included. Also, for example, RRC Reconfiguration message, RRC Resume message, RRC Release message, RRC Reestablishment message, Security Mode Command message, UE Capability Enquiry message, etc. may be included. Also, other RRC signaling may be included.

[0086] RRC messages sent in the downlink (DL) direction using MCCH may include, for example, MBS Broadcast Configuration messages (MBSBroadcastConfiguration messages). Also , other RRC signaling may be included.

[0087] An example of the NAS function will be described. NAS may have an authentication function. Also, NAS may have a function for performing mobility management. Also, NAS may have a function for security control. The functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS described above are examples, and some or all of each function may not be implemented. Also, some or all of the functions of each layer may be included in other layers.

[0088]

[0089] ​​​Next, the state transitions of UE 122 in LTE and NR will be described. When UE 122 is connected to the EPC or 5GC, UE 122 may be in the RRC_CONNECTED state when the RRC connection has been established. The state where the RRC connection has been established may include the state where UE 122 holds some or all of the UE context described later. Also, the state where the RRC connection has been established may include the state where UE 122 can transmit and / or receive unicast data. Also, when the RRC connection of UE 122 is suspended, UE 122 may be in the RRC_INACTIVE state. Also, UE 122 may enter the RRC_INACTIVE state when UE 122 is connected to the 5GC and the RRC connection is suspended. When UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state, UE 122 may be in the RRC_IDLE state. Also, the state where the RRC connection has been established may include the state where UE 122 holds some or all of the UE context described later. Also, the state where the RRC connection has been established may include the state where UE 122 can transmit and / or receive unicast data.

[0090] Note that when UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the suspension of the RRC connection may be started by the E-UTRAN. When UE 122 is connected to the EPC and the RRC connection is suspended, UE 122 may transition to the RRC_IDLE state while holding the UE's AS context and the resumeIdentity used for resume. The upper layer (e.g., NAS layer) of the RRC layer of UE 122 may start the resume of the suspended RRC connection when UE 122 holds the UE's AS context, the resume of the RRC connection is permitted by the E-UTRAN, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. Note that when UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the suspension of the RRC connection may be started by the E-UTRAN. When UE 122 is connected to the EPC and the RRC connection is suspended, UE 122 may transition to the RRC_IDLE state while holding the UE's AS context and the resumeIdentity used for resume. The upper layer (e.g., NAS layer) of the RRC layer of UE 122 may start the resume of the suspended RRC connection when UE 122 holds the UE's AS context, the resume of the RRC connection is permitted by the E-UTRAN, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. resume of the suspended RRC connection when UE 122 holds the UE's AS context, the resume of the RRC connection is permitted by the E-UTRAN, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state.

[0091] The definition of inactivity may be different between the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110. Also, when the UE 122 is connected to the EPC (when the UE 122 is in the RRC_IDLE state and is in an inactive state) and when the UE 122 is connected to the 5GC (when the UE 122 is in the RRC_INACTIVE state and is in an inactive state), part or all of the procedure for the UE 122 to resume from inactivity may be different.

[0092] Note that the RRC_CONNECTED state, the RRC_INACTIVE state, and the RRC_IDLE state may be referred to as the connected state (connected mode), the inactive state (inactive mode), and the idle state (idle mode), respectively, or may be referred to as the RRC connected state (RRC connected mode), the RRC inactive state (RRC inactive mode), and the RRC idle state (RRC idle mode).

[0093] The UE AS context held by the UE 122 may be information including all or part of the current RRC configuration, the current security context store, the PDCP state including the ROHC (RObust Header Compression) state, the C-RNTI (Cell Radio Network Temporary Identifier) used in the source PCell of the connection source, the cell identifier (cellIdentity), and the physical cell identifier of the source PCell. Note that the UE AS context held by any or all of the eNB 102 and the gNB 108 may include the same information as the UE AS context held by the UE 122, or may include information different from the information included in the UE AS context held by the UE 122.

[0094] The security context may be information including all or part of the encryption key at the AS level, the Next Hop parameter (NH), the Next Hop Chaining Counter parameter (NCC) used to derive the next hop access key, an identifier for the selected AS level encryption algorithm, and a counter used for replay protection.

[0095] Next, the serving cell will be explained. CA and / or DC, which will be described later, In a terminal device in an unconfigured RRC connected state, the serving cell has one primary In addition, the CA and / or DC may be configured as In a terminal device in an established RRC connected state, the multiple serving cells are one or Multiple Special Cells (SpCells) and one or more of all secondary The term "PCell" may refer to a set of multiple cells (set of cell(s)) consisting of a secondary cell (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may be always activated. The PCell may be a cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. The PCell may also be a cell used in the RRC connection reestablishment procedure when a terminal device reestablishes an RRC connection. The PCell may be the cell used in the establishment procedure. The PCell may also be the cell used for random addressing during handover. The PSCell may be a cell used in a random access procedure when adding a secondary node, which will be described later. The SpCell may be a cell used for purposes other than those described above.

[0096] 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. Therefore, a cell providing additional radio resources to an SpCell may refer to an SCell. .

[0097] 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).

[0098] Dual Connectivity (DC) is a technology that performs data communication using the wireless resources of cell groups that are respectively configured by a first base station device (first node) and a second base station device (second node). When DC or MR-DC is performed, the base station device A cell group may be added from the first base station device. In order to perform DC, the first base station device may add a second base station device. The first base station device may be called a master node (MN). Also, a cell group configured by the master node may be called a master cell group (MCG). The second base station device may be called a secondary node (SN). Also, a cell group configured by the secondary node may be called a secondary cell group (SCG). The master node and the secondary node may be configured in the same base station device.

[0099] Also, when DC is not configured, the cell group configured in the terminal device may be referred to as MCG. Also, when DC is not configured, the SpCell configured in the terminal device may be the PCell. Also, NR without DC configured may be referred to as NR Standalone (NR SA).

[0100] Note that Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technology that performs DC using NR for MCG and E-UTRA for SCG and may be a technology that performs DC using NR for both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC using E-UTRA for MCG and NR for SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) using EPC in the core network, or there may be NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC in the core network. Also, as an example of MR-DC using NR for MCG and E-UTRA for SCG, there may be NE-DC (NR-E-UTRA Dual Connectivity) using 5GC in the core network. Also, as an example of MR-DC using NR for both MCG and SCG there may be NR-DC (NR-NR Dual Connectivity) using 5GC in the core network.

[0101] Note that in the terminal device, there may be one MAC entity for each cell group . For example, when DC or MR-DC is configured in the terminal device, one MAC e ​There may be one MAC entity for the MCG and one MAC entity for the SCG. The MAC entity for the MCG in the terminal device may always be established in the terminal device in all states (such as RRC idle state, RRC connected state, and RRC inactive state). Also, in the terminal device the MAC entity for the SCG that exists may be created by the terminal device when the SCG is configured in the terminal device. Also, the MAC entity for each cell group of the terminal device may be configured when the terminal device receives RRC signaling from the base station device. When the MAC entity is associated with the MCG, the SpCell may mean the PCell. Also, when the MAC entity is associated with the SCG, the SpCell may mean the Primary SCG Cell (PSCell). Also, when the MAC entity is not associated with a cell group the SpCell may mean the PCell. The PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for the MCG may be an E-UTRA MAC entity, and the MAC entity for the SCG may be an NR MAC entity. Also, in NE-DC, the MAC entity for the MCG may be an NR MAC entity and the MAC entity for the SCG may be an E-UTRA MAC entity. Also, in NR-DC, the MAC entities for the MCG and SCG may both be NR MAC entities. Note that it may be said that there is one MAC entity for each cell group, or equivalently, there is one MAC entity for each SpCell. Also, the one MAC entity for each cell group may be equivalently referred to as the one MAC entity for each SpCell.

[0102] ​Describe the flow of RRC signaling transmitted and received between the terminal device and the base station device. This is shown in FIG. 4, which is an example of a flow of procedures for various settings in the RRC according to this embodiment. FIG. 4 is an example of a flow when RRC signaling is sent from the base station device (eNB102 and / or gNB108) to the terminal device (UE122). In FIG. 4, the base station device creates an RRC message (step S400). The creation of the RRC message in the base station device may be performed for the base station device to distribute system information (SI) and paging messages. Also, the creation of the RRC message in the base station device may be performed to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message

[0103] In FIG. 4, the base station device creates an RRC message (step S400). The creation of the RRC message in the base station device may be performed for the base station device to distribute system information (SI) and paging messages. Also, the creation of the RRC message in the base station device may be performed to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message is sent for the base station device to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message is sent for the base station device to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message is sent for the base station device to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message is sent for the base station device to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message is sent for the base station device to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message is sent for the base station device to send RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, etc. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. Also, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message The structure may be described using a description method called ASN.1 (Abstract Syntax Notation One). Yes.

[0104] In FIG. 4, next, the base station apparatus transmits the created RRC signaling to the terminal apparatus (step S402). Next, if processing such as setting is necessary, the terminal apparatus performs the processing according to the received RRC signaling (step S404). The terminal apparatus that has performed the processing may transmit RRC signaling for response to the base station apparatus (not shown). The RRC signaling is not limited to the above example and may be used for other purposes.

[0105] In MR-DC, for transferring RRC signaling for SCG side settings (such as cell group settings, radio bearer settings, measurement settings, etc.) between the terminal apparatus, the RRC on the master node side may be used. For example, in EN-DC or NGEN-DC, the RRC signaling of E-UTRA transmitted and received between the eNB 102 and the UE 122 may include the RRC signaling of NR in the form of a container. Also, in NE-DC, the RRC signaling of E-UTRA may be included in the form of a container in the RRC signaling of NR transmitted and received between the gNB 108 and the UE 122. The RRC signaling for SCG side settings may be transmitted and received between the master node and the secondary node.

[0106] Note that not only when using MR-DC, the RRC signaling for E-UTRA transmitted from the eNB 102 to the UE 122 may include the RRC signaling for NR, and the RRC signaling for NR transmitted from the gNB 108 to the UE 122 may include the RRC signaling for E-UTRA. The RRC signaling for E-UTRA transmitted and received between the eNB 102 and the UE 122 may include the RRC signaling of NR in the form of a container. Also, in NE-DC, the RRC signaling of E-UTRA may be included in the form of a container in the RRC signaling of NR transmitted and received between the gNB 108 and the UE 122. The RRC signaling for SCG side settings may be transmitted and received between the master node and the secondary node.

[0107] Note that not only when using MR-DC, the RRC signaling for E-UTRA transmitted from the eNB 102 to the UE 122 may include the RRC signaling for NR, and the RRC signaling for NR transmitted from the gNB 108 to the UE 122 may include the RRC signaling for E-UTRA. The RRC signaling for E-UTRA transmitted from the eNB 102 to the UE 122 may include the RRC signaling for NR, and the RRC signaling for NR transmitted from the gNB 108 to the UE 122 may include the RRC signaling for E-UTRA.

[0108] Multicast / Broadcast Services (MBS) will be described.

[0109] In a broadcast service, the same service and the same specific content data may be provided to all terminal devices (UE122) within a geographical area simultaneously. Broadcast services may be delivered to terminal devices using a broadcast session. Terminal devices may receive broadcast services in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state.

[0110] In a multicast service, the same service and the same specific content data may be provided to one or more specific terminal devices (also referred to as a UE set) simultaneously. Multicast services may be delivered to terminal devices using a multicast session. Terminal devices may receive multicast ser vices using mechanisms such as PTP delivery and / or PTM delivery. HARQ feedback / resending can be applied to both PTP transmissions and PTM transmissions.

[0111] The following logical channels may be used for MBS delivery. MTCH: PTM downlink channel for transmitting MBS data of a multicast session or a broadcast session from the network to the terminal device DTCH: PTP channel defined for transmitting MBS data of a multicast session from the network to the terminal device MCCH: PTM downlink channel used to transmit MBS broadcast control information related to one or more MTCHs from the network to the terminal device, and / or MBS multicast control information

[0112] An example of the usage method of RNTI in PTM transmission is shown. Terminal devices may use the same or different G-RNTIs It can receive different services using it. The terminal device can receive different services using the same or different G-CS-RNTIs. using it.

[0113] In a multicast service, the gNB may deliver MBS data packets using the following methods. PTP transmission: The gNB may independently deliver separate copies of MBS data packets for each terminal device. That is, the gNB schedules the terminal device-specific PDSCH using the terminal device-specific PDCCH scrambled with the terminal device-specific RNTI (e.g., C-RNTI), and delivers separate copies of the MBS data packets scrambled with the same terminal device-specific RNTI to each terminal device. to each terminal device. may. PTM transmission: The gNB may deliver a single copy of the MBS data packet to a set of UEs. That is, the gNB schedules the group-common PDSCH using the group-common PDCCH scrambled with the group-common RNTI, and delivers a single copy of the MBS data packet scrambled with the same group-common RNTI to the set of UEs. to the set of UEs.

[0114] When both PTM transmission and PTP transmission are set for a terminal device, the gNB may dynamically determine whether to deliver multicast data to a specific terminal device via either the PTM leg and / or the PTP leg based on information such as MBS session QoS requirements, the number of participating terminal devices, and the individual reception quality feedback of the terminal devices. Also, regardless of the above determination, the same QoS requirements may be applied to both PTM transmission and PTP transmission. requirements, the number of participating terminal devices, and the individual reception quality feedback of the terminal devices. data to be delivered. Also, regardless of the determination, the same QoS requirements may be applied to both PTM transmission and PTP transmission.

[0115] MBS broadcasts may be received by terminal devices in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. The terminal device may receive MBS settings (such as parameters necessary for MTCH reception) for the broadcast session via the MCCH in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. Parameters necessary for MCCH reception may be provided via system information.

[0116] The following principles may apply to the structure of the MCCH. · The MCCH may provide a list of some or all of the broadcast services transmitted on the MTCH and / or information related to the broadcast session. Information related to the bro adcast session may include the MBS session ID, associated G-RNTI scheduling information, and information about neighboring cells that provide a specific service on the MTCH. The MCCH content may be transmitted within a periodically occurring time domain window defined by the MCCH repetition period, MCCH window period, and radio frame / s lot offset. · The MCCH may use a change period, and the MCCH content may be allowed to change only at the change period boundary. A notification mechanism may be used to notify the start, change, or stop of the broadcast session and the change of the MCCH content due to the change of neighboring cell information. · When receiving an MCCH change notification, the terminal device may obtain the MCCH updated in the same MCCH change period in which the change notification was transmitted.

[0117] Describe the continuity of broadcast services in the RRC_IDLE state and RRC_INACTIVE state.

[0118] Due to the mobility procedure for MBS reception, the terminal device can start or continue receiving the MBS service when changing cells. The gNB can indicate, in the MCCH, a list of adjacent cells that provide the same MBS broadcast service as the MBS broadcast service provided in the serving cell. This enables the terminal device to request unicast reception of the service before moving to a cell that does not provide the MBS broadcast service using PTM transmission. To eliminate the need to read MBS broadcast-related system information on adjacent frequencies, the terminal device can know, via the User Service Description (USD) or in the following combination, on which frequencies the MBS broadcast service via PTM is provided. · USD · System information (System Information Block: SIB, e.g., SIB21)

[0119] In the RRC_IDLE state and the RRC_INACTIVE state, the terminal device may apply the following modifications to the normal cell reselection rules. · A terminal device that is receiving or interested in receiving the MBS broadcast service via PTM can receive these MBS broadcast services while camping on the frequencies that provide these MBS broadcast services, and if certain conditions are met, this frequency can be set as the highest priority frequency. · If the MBS broadcast service that the terminal device is interested in becomes unavailable (e.g., after the session ends), or if the terminal device is no longer interested in receiving the service, the terminal device does not need to increase the priority of the frequencies that provide these MBS broadcast services.

[0120] ​​​​​Describe the continuity of the MBS broadcast service in the RRC_CONNECTED state.

[0121] In order to ensure the continuity of the MBS broadcast service, a terminal device in the RRC_CONNECTED state can send an MBS Interest Indication composed of the following information to the gNB. · A list of MBS frequencies that the terminal device is receiving or interested in receiving, sorted in descending order of importance · The MBS frequencies that the terminal device is receiving or interested in receiving, the uni cast bearer, and the priority of receiving the multicast MRB · If an SIB (e.g., SIB20) containing information necessary to obtain the MCCH and / or MTCH settings for MBS broadcast is provided on the PCell or SCell, a list of MBS broadcast services that the terminal device is receiving or interested in receiving

[0122] Based on whether there is an SIB (e.g., SIB21) containing the mapping information between the current carrier frequency and / or adjacent carrier frequencies and the MBS Frequency Selection Area Identities (FSAI), the reporting of the MBS Interest indication may be implicitly enabled / disabled. Also, the information included in the MBS Interest indication may be exchanged between the source gNB and the target gNB during handover.

[0123] In the broadcast service, the gNB may deliver the MBS data packets to be broadcast using the following method. PTM transmission: The gNB may deliver a single copy of the MBS data packet to the UE set. ​​Yes. For example, the gNB may schedule a group-common PDSCH scrambled with the same group-common RNTI using a group-common PDCCH scrambled with a group-common RNTI. uled.

[0124] Details of MBS broadcast will be described.

[0125] The configuration information of MBS broadcast may be provided on the MCCH logical channel. Some configuration information, including the CFR (Common Frequency Resources) configuration for MCCH and MTCH, may be provided on logical channels other than the MCCH logical channel (e.g., BCCH, CCCH, DCCH, or DTCH, etc.).

[0126] The MCCH may be used to deliver the MBS broadcast sessions provided by the cell and the MBS broadcast configuration message (MBSBroadcastConfiguration message) indicating the scheduling information related to these sessions. Optionally, the MBSBroadcastConfiguration message may include a list of neighboring cells providing the same services as the MBS services provided by the current cell. The configuration information required for the terminal device to receive the MCCH may be provided in SIB1 and SIB20. Further, information regarding the service continuity of MBS broadcast may be provided in SIB21.

[0127] The MCCH information (i.e., the information transmitted in the message transmitted on the MCCH) may be transmitted periodically using a configurable repetition period within the configured transmission window. The MCCH transmission (and related radio resources and MCS) may be indicated by a PDCCH addressed to the MCCH-RNTI.

[0128] ​​​​​ The PDCCH monitoring occasion for MCCH transmission may be determined according to the common search space indicated by searchspaceMCCH. If searchspaceMCCH is set to zero, the PDCCH monitoring occasion for MCCH message reception in the MCCH transmission window may be the same as that of SIB1. If searchspaceMCCH is set to a value other than zero, the PDCCH monitoring occasion for the MCCH message may be determined based on the search space indicated by searchspaceMCCH.

[0129] The change of MCCH information may occur only in a specific radio frame, and the concept of a modification period may be used. Within the modification period, the same MCCH information may be transmitted the number of times defined by its scheduling. When the network changes some or all of the MCCH information, the network may use the PDCCH that schedules the MCCH to notify the terminal device of the change starting from the beginning of the MCCH modification period. A terminal device that has received a notification of the change may obtain the new MCCH information from the same slot in which the change notification was received if it is receiving or interested in receiving the MBS services transmitted using MBS broadcast. The terminal device may apply the previously obtained MCCH information until the new MCCH information is obtained.

[0130] The terminal device may apply the MCCH information acquisition procedure to obtain the information on the MBS broadcast settings broadcast by the network. The MCCH information acquisition procedure may be in the RRC_IDLE state, the RRC_INACTIVE state, or the common search space set by searchSpaceMCCH. This applies to MBS broadcast services that an MBS-capable terminal device in RRC_CONNECTED state, for which a BWP is the active BWP, is receiving or is interested in receiving. stomach.

[0131] If the terminal is interested in receiving the MBS broadcast service, the terminal The information acquisition procedure may be applied to those who are interested in receiving the MBS broadcast service. When a terminal device that is using the SIB20 enters a cell that provides the SIB20 (for example, when the power is turned on, After the MBS server is started, when SIB20 for the SCell is received via dedicated signaling, and when a new MBS server is started, A terminal device receiving data via a broadcast MRB may apply the MCCH information acquisition procedure when notified that the MCCH information has changed due to a change in the MCCH information other than a change due to the start of a new MBS service. A terminal device receiving data via a broadcast MRB may apply the MCCH information acquisition procedure when notified that the MCCH information has changed due to a change in the MCCH information other than a change due to the start of a new MBS service. The MCCH information acquisition procedure may overwrite the stored MCCH information unless explicitly specified in the MCCH information acquisition procedure.

[0132] Devices receiving or interested in receiving MBS broadcast services If the MCCH information acquisition procedure is triggered based on notification that the MCCH information has been changed, the device may start acquiring an MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which the MCCH information change has been notified. In addition, if the terminal device enters a cell that provides SIB20 or the SIB20 broadcast in the SCell, the terminal device may start acquiring an MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which the MCCH information change has been notified. If the information contained in is received by RRC signaling, the MCCH is used from the next repetition period. You may begin receiving MBSBroadcastConfiguration messages as they are sent.

[0133] The broadcast MRB configuration procedure may be used for the terminal device to configure PDCP, RLC, MAC, and PHY when the terminal device starts and / or stops receiving the broadcast MRB transmitted by MTCH, or when the configuration of the broadcast MRB received by the terminal device is changed. The broadcast MRB configuration procedure may be applied to MBS-capable terminal devices that are in the RRC_IDLE state, RRC_INACTIVE state, or RRC_CONNECTED state where the BWP with a common search space configured by searchSpaceMTCH or searchSpaceMCCH is the active BWP, and that are receiving or interested in receiving MBS broadcast services. The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-capable terminal device interested in receiving an MBS broadcast service enters a cell that provides the MBS broadcast service at the start of the MBS session, when it becomes interested in an ongoing MBS broadcast service, when the terminal device's capability limitations are lifted and the reception of the ongoing MBS broadcast service is no longer blocked, etc. The terminal device may apply (start) the broadcast MRB release procedure to stop receiving an MBS broadcast service session. The broadcast MRB release procedure may be performed when the MBS session is stopped, when the terminal device leaves the cell that is broadcasting the MBS service it is interested in, when it loses interest in the MBS service, when the reception of related services is... .

[0134] The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-capable terminal device interested in receiving an MBS broadcast service enters a cell that provides the MBS broadcast service at the start of the MBS session, when it becomes interested in an ongoing MBS broadcast service, when the terminal device's capability limitations are lifted and the reception of the ongoing MBS broadcast service is no longer blocked, etc. The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-capable terminal device interested in receiving an MBS broadcast service enters a cell that provides the MBS broadcast service at the start of the MBS session, when it becomes interested in an ongoing MBS broadcast service, when the terminal device's capability limitations are lifted and the reception of the ongoing MBS broadcast service is no longer blocked, etc. The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-capable terminal device interested in receiving an MBS broadcast service enters a cell that provides the MBS broadcast service at the start of the MBS session, when it becomes interested in an ongoing MBS broadcast service, when the terminal device's capability limitations are lifted and the reception of the ongoing MBS broadcast service is no longer blocked, etc. The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-capable terminal device interested in receiving an MBS broadcast service enters a cell that provides the MBS broadcast service at the start of the MBS session, when it becomes interested in an ongoing MBS broadcast service, when the terminal device's capability limitations are lifted and the reception of the ongoing MBS broadcast service is no longer blocked, etc. The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-capable terminal device interested in receiving an MBS broadcast service enters a cell that provides the MBS broadcast service at the start of the MBS session, when it becomes interested in an ongoing MBS broadcast service, when the terminal device's capability limitations are lifted and the reception of the ongoing MBS broadcast service is no longer blocked, etc.

[0135] The terminal device may apply (start) the broadcast MRB release procedure to stop receiving an MBS broadcast service session. The broadcast MRB release procedure may be performed when the MBS session is stopped, when the terminal device leaves the cell that is broadcasting the MBS service it is interested in, when it loses interest in the MBS service, when the reception of related services is... The terminal device may apply (start) the broadcast MRB release procedure to stop receiving an MBS broadcast service session. The broadcast MRB release procedure may be performed when the MBS session is stopped, when the terminal device leaves the cell that is broadcasting the MBS service it is interested in, when it loses interest in the MBS service, when the reception of related services is... It may be started when the ability restriction that interferes with the signal is started.

[0136] As a broadcast MRB setting procedure, the terminal device may perform the following operations.

[0137] The terminal device may establish a PDCP entity, an RLC entity, and / or an SDAP entity according to the information regarding this broadcast MRB included in the MBSBroadcastConfiguration message. Also, the terminal device may configure the MAC layer based on the scheduling information of MTCH (mtch-SchedulingInfo). Further, the terminal device may configure the PHY layer based on the settings applied to this broadcast MRB. Also, the terminal device may receive the DL-SCH in the same cell as the cell in which the MBSBroadcastConfiguration message for establishing the broadcast MRB was received, using the g-RNTI and / or mtch-SchedulingInfo for this MBS broadcast service. Based on the settings applied to this broadcast MRB. Also, the terminal device may configure the PHY layer. Also, the terminal device may receive the DL-SCH in the same cell as the cell in which the MBSBroadcastConfiguration message for establishing the broadcast MRB was received, using the g-RNTI and / or mtch-SchedulingInfo for this MBS broadcast service.

[0138] As a broadcast MRB release procedure, the terminal device may perform the following operations.

[0139] The terminal device may release the PDCP entity, the RLC entity, and the related MAC settings and PHY settings. Also, the terminal device may release the SDAP entity when there is no associated MRB.

[0140] The above-mentioned MBS broadcast setting message (MBSBroadcastConfiguration message) may include information indicating one or more MBS broadcast sessions (MBS session information list). In addition to or instead of that, the MBS broadcast setting message may include a list of adjacent cells that provide the same broadcast MBS service. It may be rare. Each entry in the MBS session information list may include the identifier information (TMGI) of the MBS broadcast session. The TMGI may include the identifier information of the PLMN, or the value of the index associated with the identifier information of the PLMN. In addition to or instead of this, the TMGI may include an identifier (service ID) for identifying the MBS service within the PLMN. It may be rare. In addition to or instead of this, the MBS session information list may have one or a plurality of entries. The entries in the MBS session information list may include the G-RNTI used for scheduling and transmission scrambling of MTCH. In addition to or instead of this, the entries in the MBS session information list may include the settings of the broadcast MRB (for example, PDCP settings and RLC settings). It may be included.

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

[0142] FIG. 5 is a block diagram showing the configuration of the terminal device (UE122) in the present embodiment. In order to avoid complexity in the description, FIG. 5 shows the main components closely related to the present embodiment.

[0143] The UE122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, MAC control element, RRC signaling, notification information, etc.) from the base station device, a processing unit 502 that performs processing according to the parameters included in the received control information, and a transmission unit 504 that transmits control information (UCI, MAC control element, RRC signaling etc.) to the base station device. This base station device may be the eNB102 or the gNB108. In addition, the processing unit 502 may include some or all of the functions of various layers (for example, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, The processing unit 502 includes a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), an RLC layer processing unit (RLC processing unit), PDCP layer processing unit (PDCP processing unit), SDAP processing unit (SDAP processing unit), RRC layer processing unit (RRC processing unit), and some or all of the NAS layer processing unit (NAS processing unit).

[0144] FIG. 6 is a block diagram showing the configuration of a base station device in this embodiment. In order to avoid clutter, FIG. 6 shows only the main components closely related to this embodiment. This base station device may be an eNB 102 or a gNB 108.

[0145] The base station apparatus shown in FIG. 6 includes a transmitter 600 that transmits control information (DCI, RRC signaling, broadcast information, etc.) to the UE 122, and a receiver 601 that receives control information (DCI, RRC signaling including parameters, broadcast information, etc.). The processing unit 602 creates a control information (UCI, RRC signaling, etc.) and transmits it to the UE 122, causing the processing unit 502 of the UE 122 to perform the processing, and a receiving unit 604 receives control information (UCI, RRC signaling, etc.) from the UE 122. The processing unit 602 also includes various layers (for example, a physical layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer, an RRC layer, and In other words, the processing unit 602 may include a part or all of the functions of the physical layer processing, The UE may include some or all of a management unit, a MAC layer processing unit, an RLC layer processing unit, a PDCP layer processing unit, an SDAP processing unit, an RRC layer processing unit, and an NAS layer processing unit.

[0146] An example of the processing of the terminal device in this embodiment will be described with reference to FIGS.

[0147] FIG. 7 is a diagram showing an example of the processing of the terminal device (UE122) in the present embodiment. The processing unit 502 of the terminal device receives the first information and / or the second information from the base station device (step S700). The processing unit 502 of the terminal device determines, based on the second information, which of the one or more MBS sessions specified by the received first information can be received (step S702). The processing unit 502 of the terminal device performs an operation based on the determination (step S704).

[0148] The first information received from the base station device in step S700 may be, for example, any one of the following (a) to (c), or any combination thereof. (a) A message transmitted using MCCH (b) A system information block (e.g., SIB20) (c) RRC signaling transmitted using DCCH

[0149] For example, the message in (a) may be an MBS broadcast setting message or another message. For example, the system information block in (b) may be SIB20 or another SIB. For example, the RRC signaling in (c) may be an RRC reconfiguration message or another message.

[0150] The second information received from the base station device in step S700 may be, for example, any one of the following (a) to (d), or any combination thereof. (a) A list including one or more entries, where each entry is a region indicated by a Reference Location (geographical coordinates represented by longitude and latitude) and additional information ( e.g., radius, diameter, and / or angle, etc.) as one entry (b) A list including one or more entries, where each entry is a region formed by connecting a plurality of Reference points as one entry (c) The index of the SSB (d) Information indicating other geographical areas

[0151] Each of the areas indicated by the entry may be identified by an identifier. Also, the areas indicated by the one or more entries may be defined as one area, and in this case, an identifier may be associated with each of the areas indicated by the one or more entries. The identifier for identifying an area is also referred to as an area identifier. The area identifier may be included in the second information together with the entry. FIG. 8 is a diagram showing an example in the case of (a) above. In FIG. 8, a list (MBSAreaInfoList) including an area identifier (MBS-AreaId), a Reference Location (ReferenceLocation), and a radius information (mbs-DistanceRadius) is provided from the base station device to the terminal device .

[0152] Also, that an area is indicated by an SSB index means that when the terminal device can receive the indicated SSB, the terminal device is considered to be located in the area indicated by the SSB index is acceptable. Also, being able to receive the indicated SSB may mean that the received power of the SSB is equal to or greater than a certain threshold (or exceeds the threshold). This threshold may be notified in the first information, may be notified in the second information, or may be a default value

[0153] One or more areas notified in the second information may be associated with the MBS session

[0154] For example, zero or more areas may be associated with each entry in the MBS session information list included in the MBS broadcast setting message. In this case, for example, each entry in the MBS session information list may include a list having zero or more area identifiers in the entry may be included. In addition to or instead of that, each of the MBS session information lists The TMGI included in each entry may be associated with zero or more regions. In addition or alternatively, the G-RNTI included in each entry of the MBS session information list may be associated with zero or more regions. In addition or alternatively, the PLMN included in each entry of the MBS session information list may be associated with zero or more regions. In addition or alternatively, the service ID included in each entry thereof may be associated with zero or more regions. Fig. 9 is a diagram showing an example in which a region identifier is included in the MBS broadcast configuration message. The MBS broadcast configuration message (MBSBroadcastConfiguration) includes an MBS session information list (MBS-SessionInfoList), and each entry of the MBS session information list includes a TMGI and a G-RNTI, and optionally has one or more region identifiers in the entry list (MbsAreaList). That is, since the MbsAreaList is not included in the entry of the MBS session information list, it may be shown that the entry is associated with zero regions

[0155] Also, for example, SIB20 includes the setting information necessary to receive one or more MCCHs and each of the setting information necessary to receive the MCCH may be associated with zero or more regions In this case, all MBS sessions notified in the MBS broadcast configuration message received based on the setting information necessary to receive a certain MCCH may be associated with zero or more regions associated with the setting information necessary to receive this MCCH. Fig. 10 ​​​​FIG. 0 shows an example in which the area identifier is included in SIB20. SIB20 includes a list of configuration information (McchConfigList) necessary to receive one or more MCCHs. Each entry in the McchConfigList includes configuration information (MCCH-Config) necessary to receive the MCCH, and as an option, a list (MbsAreaList) having one or more area identifiers in the entry. That is, since the MbsAreaList is not included in the McchConfig, it may be shown that the McchConfig is associated with zero areas. Also, one or more MBS sessions may be associated with each of the areas notified by the second information.

[0156]

[0157] There may also be an MBS session that is not associated with any area (i.e., is associated with zero areas).

[0158] The determination in step S702 is, for example, that the terminal device determines whether the MBS sessions of the MBS broadcast services it is interested in receiving are not associated with any area in the cell providing the MBS broadcast service. In addition or instead, the determination in step S702 may be, for example, that the terminal device determines whether it is located in the area associated with the MBS session of the MBS broadcast service it is interested in receiving.

[0159] In step S704, the terminal device may apply (start) the broadcast MRB setting procedure based on the determination. For example, the terminal device determines that the MBS sessions of the MBS broadcast services it is interested in receiving are not associated with any area. ​​​​​​Based on this, the broadcast MRB setting procedure may be applied (started). In addition to this, Instead, for example, the terminal device may be located in an area associated with an MBS session of an MBS broadcast service that it is interested in receiving. Based on this, the broadcast MRB setting procedure may be applied (started). The terminal device may determine that the MBS session is a permitted (receivable) MBS session based on the fact that the MBS session of the MBS broadcast service that it is interested in receiving is not associated with any area. In addition to or instead of this, Based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that it is interested in receiving, the terminal device may determine that the MBS session is a permitted (receivable) MBS session. The terminal device may apply (start) the broadcast MRB setting procedure only for permitted (receivable) MBS sessions. Based on the fact that the MBS session of the MBS broadcast service that it is interested in receiving is not associated with any area, the terminal device may determine that the MBS session is a permitted (receivable) MBS session. In addition to or instead of this, Based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that it is interested in receiving, the terminal device may determine that the MBS session is a permitted (receivable) MBS session. The terminal device may apply (start) the broadcast MRB setting procedure only for permitted (receivable) MBS sessions. Based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that it is interested in receiving, the terminal device may determine that the MBS session is a permitted (receivable) MBS session. The terminal device may apply (start) the broadcast MRB setting procedure only for permitted (receivable) MBS sessions. Based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that it is interested in receiving, the terminal device may determine that the MBS session is a permitted (receivable) MBS session. The terminal device may apply (start) the broadcast MRB setting procedure only for permitted (receivable) MBS sessions. Based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that it is interested in receiving, the terminal device may determine that the MBS session is a permitted (receivable) MBS session. The terminal device may apply (start) the broadcast MRB setting procedure only for permitted (receivable) MBS sessions.

[0160] In addition to or instead of this, in step S704, the terminal device may apply (start) the broadcast MRB release procedure based on the above determination. For example, based on the fact that the terminal device is not located in an area associated with an MBS session of an MBS broadcast service that it is receiving, the terminal device may apply (start) the broadcast MRB release procedure. Based on the fact that the terminal device is not located in an area associated with an MBS session of an MBS broadcast service that it is receiving, the terminal device may determine that the MBS session is not a permitted (non - receivable) MBS session. The terminal device may Based on the fact that the terminal device is not located in an area associated with an MBS session of an MBS broadcast service that it is receiving, the terminal device may apply (start) the broadcast MRB release procedure. Based on the fact that the terminal device is not located in an area associated with an MBS session of an MBS broadcast service that it is receiving, the terminal device may determine that the MBS session is not a permitted (non - receivable) MBS session. Based on the fact that the terminal device is not located in an area associated with an MBS session of an MBS broadcast service that it is receiving, the terminal device may determine that the MBS session is not a permitted (non - receivable) MBS session. The terminal device may Based on the fact that the terminal device is not located in an area associated with an MBS session of an MBS broadcast service that it is receiving, the terminal device may determine that the MBS session is not a permitted (non - receivable) MBS session. The terminal device may A broadcast MRB release procedure may be applied (started) to an MBS session for which reception is not permitted (unable to receive).

[0161] In addition or alternatively, UE in the RRC_IDLE state and the RRC_INACTIVE state may, in step S702, while camping on the frequency on which the MBS session of the MBS broadcast service being received or interested in receiving is provided, determine whether there is no area associated with the MBS session of that MBS broadcast service, or whether the UE is located in the associated area. While camping on the frequency on which the MBS session of the MBS broadcast service being received or interested in receiving is provided, determine whether there is no area associated with the MBS session of that MBS broadcast service, or whether the UE is located in the associated area. In step S704, the UE may, based on the determination, regard the frequency on which the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving is provided as the highest priority frequency.

[0162] For example, the UE may, based on the absence of an area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving, regard the frequency on which this MBS session is provided as the highest priority frequency. In addition or alternatively, for example, the UE may, based on the UE being located in the area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving, regard the frequency on which this MBS session is provided as the highest priority frequency. For example, the UE may, based on the absence of an area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving, regard the frequency on which this MBS session is provided as the highest priority frequency. Based on the absence of an area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving, regard the frequency on which this MBS session is provided as the highest priority frequency. In addition or alternatively, for example, the UE may, based on the UE being located in the area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving, regard the frequency on which this MBS session is provided as the highest priority frequency. Based on the UE being located in the area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or interested in receiving, regard the frequency on which this MBS session is provided as the highest priority frequency. May be regarded as the highest priority frequency.

[0163] In addition, in step S704, based on the determination, the terminal device sets the frequency on which the MBS broadcast service being received or the MBS broadcast service in which the terminal device is interested in receiving (or the MBS session of the MBS broadcast service) is provided as the highest priority frequency and may not consider it. For example, based on the fact that the terminal device is not located in the area associated with the area associated with the MBS broadcast service being received or the MBS broadcast service in which the terminal device is interested in receiving (or the MBS session of the MBS broadcast service), the terminal device sets the frequency on which this MBS session is provided as the highest priority frequency and may not consider it.

[0164] Note that as the above MBS session information list, a list composed only of entries not associated with an area and a list composed of entries associated with zero or more areas may be independently included in the MBS broadcast setting message. Thereby, a conventional terminal device that does not support the operation of this embodiment can receive an MBS broadcast service not limited to an area by acquiring only a list composed of entries not associated with an area, and a terminal device that supports the operation of this embodiment can receive both an MBS broadcast service not limited to an area and an MBS broadcast service limited to an area by acquiring both lists.

[0165] With the above mechanism, the base station device can provide the MBS broadcast service by PTM distribution to a specific area within the cell without using PTP distribution. Also, the terminal device can receive the MBS broadcast service in an appropriate area within the cell.

[0166] ​​​​​In the above description, the processing unit 502 of the UE 122 may be a processing unit that performs RRC layer processing. .

[0167] Also, as the second information, information other than the information indicating the area may be notified to the terminal device. For example, the terminal device may be notified of the MBS broadcast service permitted to be received from the network (base station device) and / or information on the MBS session. For example, the information may include information such as the G-RNTI and service ID of the MBS session permitted to be received. In addition to or instead of that, the information may include information necessary for decrypting the MBS session permitted to be received. In addition, the information may include information indicating the period during which the information is valid (for example, the value of a timer). The network (base station device) may notify the information based on the location information notified from the terminal device. In addition to or instead of that, the network (base station device) may notify the information based on the report of the measurement result of the reference signal transmitted from one or more cells notified from the terminal device. In addition to or instead of that, the network (base station device) may notify the information based on other information.

[0168] In step S704, for example, based on the fact that the MBS session of the MBS broadcast service in which the terminal device is interested in receiving is not associated with any area, the terminal device may apply (start) the broadcast MRB setting procedure. In addition to or instead of that, for example, based on the fact that the MBS session of the MBS broadcast service in which the terminal device is interested in receiving is the MBS broadcast service and / or MBS session permitted to be received from the network (base station device), the terminal device may ​​​​​​You may apply (start) the broadcast MRB setting procedure. The terminal device may determine that the MBS session of the MBS broadcast service it is interested in receiving is a permitted (receivable) MBS session based on the fact that the MBS session is not associated with any area. In addition or alternatively, the terminal device may determine that the MBS session of the MBS broadcast service it is interested in receiving is a permitted MBS broadcast service received from the network (base station device), and / or based on the fact that it is an MBS session, the MBS session may be determined to be a permitted ( receivable) MBS session. The terminal device may apply (start) the broadcast MRB setting procedure only for permitted ( receivable) MBS sessions.

[0169] In addition or alternatively, in step S704, for example, the terminal device may apply (start) the broadcast MRB release procedure based on the fact that the MBS session of the received MBS broadcast service is not a permitted MBS broadcast service received from the network (base station device) and / or an MBS session. The terminal device may determine that the MBS session is a non-permitted (non-receivable) MBS session based on the fact that the MBS session of the received MBS broadcast service is not a permitted MBS broadcast service received from the network (base station device) and / or an MBS session. The terminal device may apply (start) the broadcast MRB release procedure for non-permitted ( non-receivable) MBS sessions.

[0170] ​​​In addition to or instead of this, in step S704, for example, the terminal device may consider the frequency at which an MBS broadcast service (or an MBS session of the MBS broadcast service) that it is receiving or is interested in receiving is permitted to be received from the network (base station device) as the highest priority frequency. In addition, in step S704, for example, the terminal device may not consider the frequency at which an MBS broadcast service (or an MBS session of the MBS broadcast service) that it is receiving or is interested in receiving is not permitted to be received from the network (base station device) as the highest priority frequency, based on the fact that the MBS broadcast service and / or the MBS session is not such an MBS broadcast service and / or MBS session that is permitted to be received from the network (base station device). and / or MBS session that is permitted to be received from the network (base station device). Based on this, the frequency at which this MBS session is provided may be regarded as the highest priority frequency. In addition, in step S704, for example, the terminal device may consider the frequency at which an MBS broadcast service (or an MBS session of the MBS broadcast service) that it is receiving or is interested in receiving is permitted to be received from the network (base station device) as the highest priority frequency. In addition, in step S704, for example, the terminal device may not consider the frequency at which an MBS broadcast service (or an MBS session of the MBS broadcast service) that it is receiving or is interested in receiving is not permitted to be received from the network (base station device) as the highest priority frequency, based on the fact that the MBS broadcast service and / or the MBS session is not such an MBS broadcast service and / or MBS session that is permitted to be received from the network (base station device). and / or MBS session that is permitted to be received from the network (base station device). Based on this, the frequency at which this MBS session is provided may not be regarded as the highest priority frequency.

[0171] Also, in each embodiment, the first information and / or the second information may be notified to the terminal device in any one or any combination of an RRC message, RRC signaling, a message of an upper layer of the RRC layer, and a MAC control element.

[0172] Also, in the above description, expressions such as "link to", "corresponding to", "associate with", etc. may be paraphrased with each other.

[0173] Also, in the above description, expressions such as "determined as A", "set with A", "included A", etc. may be paraphrased with each other.

[0174] ​​​​In the above description, "transitioning from X to Y" may be rephrased as "becoming Y from X". Also, in the above description, "causing a transition" may be rephrased as "determining a transition".

[0175] In addition, in the examples of each process or the examples of the flow of each process in the above description, some or all of the steps may not be executed. Also, in the examples of each process or the examples of the flow of each process in the above description, the order of the steps may be different. Further, in the examples of each process or the examples of the flow of each process in the above description, some or all of the processes within each step may not be executed.

[0176] Note that in the above description, when "C may be D" and "C may be E" are described, it may include that "D may be E". Also, in the above description, when "F may be G" and "G may be H" are described, it may include that "F may be H".

[0177] The program that operates on the device according to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of this embodiment. The program or the information handled by the program is temporarily read into a volatile memory such as a Random Access Memory (RAM) during processing, or stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD), and is read by the CPU as needed and modified and written.

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

[0179] Furthermore, the "computer-readable recording medium" also includes those that hold a program dynamically for a short 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 in that case, the servers and client computers - and those that hold a program for a certain period of time, such as the volatile memory inside a computer system. Also, the above program may be for realizing a part of the aforementioned functions, and furthermore, it may be realized in combination with a program already recorded in the computer system that realizes the aforementioned functions.

[0180] In addition, each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, that is, typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described in this specification includes a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable It may include a programmable logic device such as a field programmable gate array (FPGA), or other programmable logic devices, discrete gates 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 circuits described above, may be composed of digital circuits or analog circuits. Also, when a technology for integrating circuits that replaces current integrated circuits appears due to the progress of semiconductor technology, it is also possible to use integrated circuits based on such technology.

[0181] Note that this embodiment is not limited to the above-described embodiment. In the embodiment, an example of the device is described, but this embodiment is not limited thereto, and it can be applied to stationary or non-mobile electronic devices installed indoors and outdoors, such as terminal devices or communication devices such as AV devices, kitchen devices, cleaning and washing devices, air conditioning devices, office devices, vending machines, and other household devices.

[0182] As described above, this embodiment has been described in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and design changes and the like within the scope not departing from the gist of this embodiment are also included. Also, this embodiment can be variously modified within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of this embodiment. Also, configurations in which elements described in the above embodiment and elements having the same effect are replaced with each other are included.

Description of Reference Numerals

[0183] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC Interfaces 112, 114, 116, 118, 120, 124 UE 122 PHYs 200, 300 MACs 202, 302 RLCs 204, 304 PDCPs 206, 306 RRCs 208, 308 SDAP 310 NASs 210, 312 Receivers 500, 604 Processing units 502, 602 Transmitters 504, 600

Claims

1. A terminal device that communicates with a base station device, comprising: a receiving unit that receives control information regarding one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more area information; and a processing unit, wherein the control information includes information associating a part or all of an MBS session with one or more of the area information, each of the area information indicates information of a part or all of the area of the cell, and based on that the MBS session being received or of interest to be received is not associated with any of the area information or is associated with the area information indicating the area where the terminal device is located, the processing unit regards the frequency at which the MBS session is provided as the highest priority frequency The terminal device.

2. A method applied to a terminal device that communicates with a base station device, comprising: receiving control information regarding one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more area information, wherein the control information includes information associating a part or all of an MBS session with one or more of the area information, each of the area information indicates information of a part or all of the area of the cell, and based on that the MBS session being received or of interest to be received is not associated with any of the area information or is associated with the area information indicating the area where the terminal device is located, the processing unit regards the frequency at which the MBS session is provided as the highest priority frequency The method.

3. An integrated circuit implemented in a terminal device that communicates with a base station device, causing the terminal device to perform a function of receiving control information regarding one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more area information, wherein the control information includes information associating a part or all of an MBS session with one or more of the area information, each of the area information indicates information of a part or all of the area of the cell, and based on that the MBS session being received or of interest to be received is not associated with any of the area information or is associated with the area information indicating the area where the terminal device is located, the processing unit regards the frequency at which the MBS session is provided as the highest priority frequency ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ Based on not being associated with any of the area information or being associated with area information indicating the area where the terminal device is located, the MBS session is provided Regard the frequency as the highest-priority frequency Integrated circuit

Images