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: A terminal device communicating with a base station device comprises a receiving unit and a processing unit, and the 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. The processing unit determines that, of the MBS sessions, an MBS session not associated with any of the area information and an MBS session associated with area information indicating an area where the terminal device is located, are an MBS session permitted to receive information, and executes broadcast MRB setting procedures for starting reception of the MBS session.SELECTED DRAWING: Figure 7

Description

[Technical field]

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

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

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

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

[0005] [Non-Patent Document 1] 3GPP TS 38.331 v17.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 a 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 state).

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of the objectives 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 a cell of the base station device, and one or more area information, and a processing unit. The control information includes part or all of an MBS session and one or more of the above-mentioned areas information, and one or more of the above-mentioned areas Information for associating with rear information is included, and each of the area information indicates information of a part or all of the area of the cell. The processing unit performs the one or more MBS sessions Among them, an MBS session with which none of the area information is associated, and the terminal An MBS session associated with area information indicating the area where the device is located is determined to be an MBS session for which reception is permitted And in order to start receiving the MBS session determined to be permitted to receive, a broadcast MRB setting procedure is executed.

[0009] Also, one aspect of the present invention is a method applied to a terminal device that communicates with a base station device, 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 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. Among the one or more MBS sessions An MBS session with which none of the area information is associated, and an MBS session associated with area information indicating the area where the terminal device is located are determined to be MBS sessions for which reception is permitted And in order to start receiving the MBS session determined to be permitted to receive, a broadcast MRB setting procedure is executed. And in order to start receiving the MBS session determined to be permitted to receive, a broadcast MRB setting procedure is executed. And in order to start receiving the MBS session determined to be permitted to receive, a broadcast MRB setting procedure is executed. And in order to start receiving the MBS session determined to be permitted to receive, a broadcast MRB setting procedure is executed.

[0010] Also, one aspect of the present invention is an integrated circuit mounted on a terminal device that communicates with a base station device, causing the terminal device to exhibit 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 includes a part or all of an MBS session And causing the terminal device to exhibit a function of receiving one or more area information. The control information includes information associating a part or all of an MBS session with one or more of the area information. The information includes a unit and one or more pieces of the area information, each of the area information indicating information of a part or all of the area of the cell. The processing unit determines, among the one or more MBS sessions, an MBS session to which none of the area information is associated, and an MBS session to which the area information indicating the area where the terminal device is located is associated as an MBS session whose reception is permitted, and executes a broadcast MRB setting procedure to start receiving the determined MBS session whose reception is permitted. session as an MBS session whose reception is permitted, and executes a broadcast MRB setting procedure to start receiving the determined MBS session whose reception is permitted.

[0011] These general or specific aspects may be implemented in a system, apparatus, method, integrated circuit, computer program, or recording medium, or may be implemented in 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 realize 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 (RATs). Also, LTE that can be connected with NR and Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. Also, LTE that uses 5GC in the core network (core network, Core Network: CN) may be distinguished from conventional LTE that uses EPC in the core network. Note that Conventional LTE may be 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 technology, and / or may be applied to other radio access technologies. Also, 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] Figure 1 is a schematic diagram of the communication system according to this embodiment. Note that the functions of each node, radio access technology, core network, interface, etc. described with reference to Figure 1 are some functions closely related to this embodiment, and other functions may be provided.

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

[0019] EPC (Evolved Packet Core) 104 may be the core network. Interface 112 is the interface between eNB 102 and EPC 104 and may be called the S1 interface. ​​The interface 112 may have 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) within the EPC 104. The user plane interface of the interface 112 may terminate at a Serving Gateway (S-GW, not shown) within the EPC 104. The control plane interface of the interface 112 may be referred to as an S1-MME interface. The user plane interface of the interface 112 may be referred to as an S1-U interface.

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

[0021] NR 106 may be a radio access technology. Also, NR 106 may be an air interface between the UE 122 and the gNB 108. The air interface between the UE 122 and the gNB 108 may be referred to as a Uu interface. The gNB (g Node B) 108 may be a base station device of NR 106 . The gNB 108 may have an NR protocol described below. The NR protocol may be composed of an NR User Plane (UP) protocol and an NR Control Plane (CP) protocol described below. The gNB 108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol for the UE 122.

[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 . There may be an interface (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 a function to connect to EPC104. A gNB 108 having a function to connect 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. There may be a user plane interface through which user data passes in interface 118 . 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 an 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, among the interfaces 11 4, interface 116, interface 118, interface 120, and interface 124, some or all of these interfaces 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 a radio connection with the gNB 108. The UE 122 may have an E-UTRA protocol and / or an NR protocol. Note that the radio connection may be a Radio Resource Control (RRC) connection. Furthermore, the UE 122 may communicate with the EPC 104 and / or the 5GC 110 via the eNB 102 and / or the gNB 108.

[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 connected core network of eNB102 and / or gNB108 with which UE122 communicates is EPC104, each of the data radio bearers (DRBs) described below established between UE122 and eNB102 and / or gNB108 may be 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 (Evolved Packet System) 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 connected core network of eNB102 and / or gNB108 with which UE122 communicates is 5GC110, each DRB established between UE122 and eNB102 and / or gNB108 may be associated with one of the PDU (Packet Data Unit) sessions established within 5GC110. Each PDU session may have one or more QoS flows. 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 the information of the EPS bearer. It does not necessarily have the information of the EPS bearer.

[0032] 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. In the present embodiment, the downlink (DL) may be a link from the base station apparatus to the terminal apparatus. 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. It may be a link without passing through the base station apparatus.

[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. FIG. 2(A) The E-UTRA UP protocol may be a protocol terminated at the eNB 102 on the network side. FIG. 2(A) As shown, the E-UTRA user plane protocol stack may be composed of the PHY (Physical layer) 200 which is the radio physical layer, the MAC (Medium Access Control) 202 which is the medium access control layer, the RLC (Radio Link Control) 204 which is the radio link control layer, and the PDCP (Packet Data Convergence Protocol) 206 which is the packet data convergence protocol layer.

[0035] Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in Figure 3(A), the NR UP protocol may be the protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be the 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 the PHY 300 which is the radio physical layer, the MAC 302 which is the medium access control layer, the RLC 304 which is the radio link control layer, the PDCP 306 which is the packet data convergence protocol layer, and the SDAP (Service Data Adaptation Protocol) 310 which is the service data adaptation protocol layer.

[0036] Figure 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration. As shown in Figure 2(B), in the E-UTRA CP protocol, the RRC (Radio Resource Control) 208 which is the radio resource control layer may be the protocol between the UE 122 and the eNB 102. That is, the RRC 208 may be the protocol terminated at the eNB 102 on the network side. Also, the E-UTRA CP pro In Tokor, the NAS (Non-Access Stratum) 210, which is a non-AS (Access Stratum) layer (non-AS layer), may be a protocol between the UE 122 and the MME. That is, the NAS 210 may be a protocol that terminates 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 RRC 308, which is a radio resource control layer, may be a protocol between the UE 122 and the gNB 108. That is, the RRC 308 may be a protocol that terminates at the gNB 108 on the network side. Also, in the NR CP protocol, the NAS 312, which is a non-AS layer, may be a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates at the AMF on the network side.

[0038] Note that the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and / or the gNB 108. That is, the AS layer may be a layer that includes some or all of the PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208, and / or a layer that includes some or all of the PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308.

[0039] ​In this embodiment, when the protocols of E-UTRA and NR are not distinguished hereinafter, 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 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 protocols of E-UTRA and NR hereinafter, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively referred to as the 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. Also, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, etc. Also, when distinguishing between the protocols of E-UTRA and NR When doing so, PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 may also be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Also, PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 may sometimes be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.

[0041] Entities in the AS layer of E-UTRA and / or NR are 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. An entity having some or all of the functions of the SDAP layer may be called an SDAP entity. An entity having some or all of the functions of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be alternatively referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.

[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 called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. 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 called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Also, the segmented RLC SDU may be called an RLC SDU segment. ​

[0043] Here, the base station device and the terminal device exchange signals in the higher layer. The higher layer may also be referred to as the upper layer and can be paraphrased with each other. 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. Further, the RRC layer of the terminal device acquires system information notified from the base station device. Here, the RRC message, the system information, and / or the MAC control element may also be referred to as higher layer signals or higher layer parameters. Each parameter 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 as 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. Here, the base station device and the terminal device exchange signals in the higher layer. The higher layer may also be referred to as the upper layer and can be paraphrased with each other. 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. Further, the RRC layer of the terminal device acquires system information notified from the base station device. Here, the RRC message, the system information, and / or the MAC control element may also be referred to as higher layer signals or higher layer parameters. Each parameter 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 as 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. Here, the base station device and the terminal device exchange signals in the higher layer. The higher layer may also be referred to as the upper layer and can be paraphrased with each other. 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. Further, the RRC layer of the terminal device acquires system information notified from the base station device. Here, the RRC message, the system information, and / or the MAC control element may also be referred to as higher layer signals or higher layer parameters. Each parameter 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 as 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) in the higher layer" or "A is given (provided) by the higher layer" may mean that the higher layer of the terminal device (mainly the RRC layer, MAC layer, etc.) 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 of the terminal device (mainly the MAC layer and the physical layer). For example, in the terminal device, "up " The phrase "a higher layer parameter is provided" may mean that the base station device receives a higher layer signal 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. The phrase "a higher layer parameter is set in the terminal device" may mean that a higher layer parameter is given (provided) to the terminal device. For example, the phrase "a 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 in the higher layer. However, the phrase "a higher layer parameter is set in the terminal device" may include the case where a default parameter pre-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 the expression "submit a message from the RRC entity of the terminal device to the lower layer (lower layer)" may be used. In the terminal device, "submit a message from the RRC entity to the lower layer" may mean submitting the message to the PDCP layer. In the terminal device, "submit a message from the RRC layer to the lower layer" means that since the RRC message is transmitted using an SRB (such as SRB0, SRB1, SRB2, SRB3), it may mean submitting the message to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from the 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 receives data transmitted from the PHY of the base station device via a downlink (DL) physical channel.

[0045] It may have functions. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink (UL) 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 channels 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] The PBCH may be used to notify the system information required by the terminal device.

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

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

[0051] The PUCCH is used in uplink wireless communication (wireless communication from a terminal device to a base station device). It may be used to transmit uplink control information (UCI). Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. Also, the uplink control information may include a scheduling request (SR) used to request 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 to transmit downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. Also, the PDSCH may be used to transmit system information (SI) or a random access response (RAR) in the case of the downlink.

[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 an RRC message and a MAC CE described later. Here , in PDSCH, the RRC message transmitted from the base station device may be common signaling for a plurality of terminal devices within a 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. signaling. Also, PUSCH may be used for transmitting the UE Capability in the uplink.

[0054] PRACH may be used to transmit a random access preamble. PRACH may be used for an initial connection establishment procedure, a handover procedure, a connection re-establishment procedure, synchronization (timing adjustment) for uplink transmission, and indicating a request for UL-SCH resources.

[0055] An example of the MAC function will be described. MAC may be called the MAC sublayer. MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channel has a logical channel identifier (Logical ​​​It may be identified by a Channel Identity, or a Logical Channel ID. The MAC may be connected to the upper RLC through a logical channel. The logical channel 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 channel 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 through the logical channel 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. The MAC may have a function of performing priority processing of overlapping resources within one terminal device. The MAC may have a function of identifying Multimedia Broadcast Multicast Services (MBMS). Also, the NR MAC may have a function of identifying a Multicast Broadcast Service (MBS). The MAC may have a function of selecting a transport format. The MAC may perform discontinuous reception (DRX) and / or 。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 。The MAC may have a function of performing priority processing of overlapping resources within one terminal device 。The MAC may have a function of identifying Multimedia Broadcast Multicast Services (MBMS). Also, the NR MAC may have a function of identifying a Multicast Broadcast Service (MBS). The MAC may have a function of selecting a transport format 。The MAC may have a function of performing discontinuous reception (DRX) and / or It may have functions such as discontinuous transmission (DTX), a function to execute a random access (RA) procedure, a power headroom report (PHR) function to notify information on transmit power, and a buffer status report (BSR) function to notify the data volume information of the transmit buffer. 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. Further, the MAC PDU may include a MAC control element (MAC CE), which is an element for control in MAC.

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

[0057] The BCCH (Broadcast Control Channel) 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 the terminal device and the 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 the base station device and multiple terminal devices.

[0060] ​ The DCCH (Dedicated Control Channel) is 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. This 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. This 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 a terminal device. The MCCH may be a logical channel for multicast and / or broadcast. The MCCH may carry the MBS broadcast configuration (MBSBroadcastConfiguration) provided in the cell where the MCCH is transmitted. The MCCH may carry the MBS broadcast configuration (MBSBroadcastConfiguration) provided in the cell where the MCCH is transmitted.

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

[0064] Describe the mapping between logical channels and transport channels in the uplink of E-UTRA and / or NR.

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

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

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

[0068] Describe the mapping between logical channels and transport channels in the downlink of E-UTRA and / or NR.

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

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

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

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

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

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

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

[0076] An example of the RLC function will be described. RLC may also be referred to as the RLC sublayer. E-UTRA RLC may have a function of segmenting and / or concatenating data provided from the upper-layer PDCP and providing it to the lower layer. 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. NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to the data provided from the upper-layer PDCP. Also, NR RLC may have a function of segmenting the data provided from PDCP and providing it to the lower layer. Also, 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, RLC may have a data retransmission function and / or a retransmission request function (Automatic retransmission function) and may perform re-ordering on the data provided from the lower layer and provide it to the upper layer. It may have Repeat reQuest: ARQ). Also, RLC may have a function to perform error correction by ARQ. For performing ARQ, control information indicating data that needs to be retransmitted and is sent from the receiving side of RLC to the transmitting side may be referred to as a status report. Also, what is sent from the transmitting side of RLC to the receiving side and is an instruction to send a status report may be referred to as a poll. Also, RLC may have a function to detect data duplication. Also, RLC may have a function to discard data. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM, data received from the upper layer is not split, and addition of an RLC header may not be performed. A TM RLC entity is a unidirectional entity and may be set as a transmitting TM RLC entity or as a receiving TM RLC entity. In UM, data received from the upper layer is split and / or combined, and an RLC header is added, etc., but retransmission control of data may not be performed. A UM RLC entity may be a unidirectional entity or a bi-directional entity. When a UM RLC entity is a unidirectional entity, the UM RLC entity may be set as a transmitting UM RLC entity or as a receiving UM RLC entity. When a UM RLC entity is a bi-directional entity, the UM RLC entity may be set as a UM RLC entity composed of a transmitting side and a receiving side. In AM it may perform data retransmission control. An AM RLC entity may be a unidirectional entity or a bi-directional entity. When an AM RLC entity is a unidirectional entity, the AM RLC entity may be set as a transmitting AM RLC entity or as a receiving AM RLC entity. When an AM RLC entity is a bi-directional entity, the AM RLC entity may be set as an AM RLC entity composed of a transmitting side and a receiving side. In AM Data received from the upper layer may be segmented and / or concatenated, an RLC header may be added, and retransmission control of the data may be performed. The AM RLC entity is a bidirectional entity and may be configured as AM RLC composed of a transmitting side and a receiving side. Note that the data provided to the lower layer by TM and / or the data provided from the lower layer may be called a TMDPDU. Also, the data provided to the lower layer by UM and / or the data provided from the lower layer may be called a UMDPDU. Also, the data provided to the lower layer by 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). An example of the function of PDCP will be described. PDCP may be called a PDCP sublayer. PDCP may have a function of maintaining a sequence number. Also, PDCP may have a header compression / decompression function for efficiently transmitting user data such as IP packets (IP Packets) and Ethernet frames in a radio section. The protocol used for header compression / decompression of IP packets may be called a ROHC (Robust Header Compression) protocol. Also, the protocol used for header compression / decompression of Ethernet frame headers may be called an EHC (Ethernet (registered trademark)) header compression / decompression protocol. header compression / decompression protocol.

[0077] header compression / decompression protocol. header compression / decompression protocol. header compression / decompression protocol. It can be called the (Header Compression) protocol. Also, PDCP may have the function of encrypting / decrypting data. Also, PDCP may have the function of protecting data integrity / verifying data integrity. Also, PDCP may have the function of re-ordering. Also, PDCP may have the function of retransmitting PDCP SDUs. Also, PDCP may have the function of discarding data using a discard timer. Also, PDCP may have a Duplication function . Also, PDCP may have the function of discarding duplicate received data. The PDCP entity is a two-way 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, in the PDCP PDU there may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the PDCP PDU for control may be called a 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 (ser vice data adaptation protocol layer). SDAP is responsible for associating (mapping) the downlink QoS flow sent from the 5GC 110 to the terminal device via the base station device with the data radio bearer (DRB) ​It may have a function of performing mapping between an uplink QoS flow sent from a terminal device via a base station device to 5GC 110 and a DRB. Also, SDAP may have a function of storing mapping rule information. Further, 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 referred to as an SDAP DATA PDU (SDAP Data PDU, SDAP data PDU). Also, the control SDAP PDU may be referred to as an SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that there may be one SDAP entity in the terminal device for each PDU session.

[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 EPC 104 and / or 5GC 110. RRC may have a call (paging) function from eNB 102 connected to gNB 108 or 5GC 110. Also, RRC may have an RRC connection management function. Further, RRC may have a radio bearer control function. Also, RRC may have a cell group control function. Also The RRC may have a mobility control function. Also, the RRC may have a terminal device measurement reporting and terminal device measurement reporting control function. Further, the RRC may have a QoS management function. Additionally, the RRC may have a function for detecting and recovering radio link failures. The RRC may use RRC messages to perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, detection and recovery of 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. The parameters may be different.

[0080] RRC messages may be sent using the BCCH of the logical channel. In addition or instead, RRC messages may be sent using the PCCH of the logical channel. In addition or instead, RRC messages may be sent using the CCCH of the logical channel. In addition or instead, RRC messages may be sent using the DCCH of the logical channel. In addition or instead, 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. In addition or instead, RRC messages may be sent using the DCCH of the logical channel. In addition or instead, 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. In addition or instead, RRC messages may be sent using the DCCH of the logical channel. In addition or instead, RRC messages may be sent using the MCCH of the logical channel. In addition or instead, 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.

[0081] RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), various types of System Information Blocks (SIBs), or other RRC messages. 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 message (RRC System Info Request), etc. Also, 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. Other RRC messages may also be included. 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. Also, for example, an RRC reject message (RRC Reject), an RRC setup message (RRC Setup), etc. may be included. Other RRC messages may also be included.

[0083] RRC signaling sent in the uplink (UL) direction using the DCCH may include, for example, a measurement report 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. Also, for example, an RRC reject message (RRC Reject), an RRC setup message (RRC Setup), etc. may be included. Other RRC messages may also 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 also include other RRC signaling.

[0085] RRC signaling sent in the downlink (DL) direction using DCCH may include, for example, an RRC Connection Reconfiguration message, an RRC Connection Release message, a Security Mode Command message, a UE Capability Enquiry message, etc. Also, for example, an RRC Reconfiguration message, an RRC Resume message, an RRC Release message, an RRC Reestablishment message, a Security Mode Command message, a UE Capability Enquiry message, etc. may be included. Other RRC signaling may also be included.

[0086] RRC messages sent in the downlink (DL) direction using MCCH may include, for example, an MBS Broadcast Configuration message (MBSBroadcastConfiguration message). 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 the foregoing PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS 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 a 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 a 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. The state where the RRC connection has been established may include a state where UE 122 holds some or all of the UE context described later. Also, the RRC connection being established may include a 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.

[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., the 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., the 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.

[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, the procedure for the UE 122 to resume from inactivity may be partially or entirely different when the UE 122 is connected to the EPC (when the UE 122 is in the RRC_IDLE state and 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 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, RRC_INACTIVE state, and RRC_IDLE state may be referred to as the connected mode, inactive mode, and idle mode, respectively, or as the RRC connected mode, RRC inactive mode, and RRC idle mode. state (connected mode), inactive state (inactive mode), idle state (idle mode), or may be referred to as the RRC connection state (RRC connected mode), RRC inactive state (RRC inactive mode), and 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, the PDCP state including the ROHC (RObust Header Compression) state, the C-RNTI (Cell Radio Network Temporary Identifier) used in the serving PCell of the source, the cell identifier (cellIdentity), and the physical cell identifier of the serving PCell of the source. Note that the UE AS context held by any or all of the eNB 102 and 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] A security context may be information that includes all or some of a cryptographic key at the AS level, an NH (Next Hop parameter), an NCC (Next Hop Chaining Counter parameter) used for deriving an access key for the next hop, an identifier of a selected AS-level encryption algorithm, and a counter used for replay protection.

[0095] Next, the serving cell will be described. In a terminal device in the RRC connected state where CA and / or DC described later are not configured, the serving cell may be composed of one primary cell (PCell). Also, in a terminal device in the RRC connected state where CA and / or DC described later are configured, the plurality of serving cells may mean a set of cells composed of one or more special cells (SpCell) and one or more secondary cells (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be the cell used in the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be the cell used in the RRC connection re-establishment procedure when the terminal device performs RRC connection re-establishment. Also, the PCell may be the cell used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes. more special cells (SpCell) and one or more secondary cells (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be the cell used in the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be the cell used in the RRC connection re-establishment procedure when the terminal device performs RRC connection re-establishment. Also, the PCell may be the cell used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes. more special cells (SpCell) and one or more secondary cells (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be the cell used in the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be the cell used in the RRC connection re-establishment procedure when the terminal device performs RRC connection re-establishment. Also, the PCell may be the cell used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes. more special cells (SpCell) and one or more secondary cells (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be the cell used in the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be the cell used in the RRC connection re-establishment procedure when the terminal device performs RRC connection re-establishment. Also, the PCell may be the cell used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes. more special cells (SpCell) and one or more secondary cells (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be the cell used in the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be the cell used in the RRC connection re-establishment procedure when the terminal device performs RRC connection re-establishment. Also, the PCell may be the cell used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes.

[0096] If the group of serving cells configured for the terminal device consists of a SpCell and one or more SCell, it may be considered that carrier aggregation (CA) is configured for the terminal device. Also, for a terminal device with CA configured, a cell that provides additional radio resources for the SpCell may also mean an SCell .

[0097] The cell group configured from the base station device for the terminal device will be described. The cell group may consist of one SpCell. Also, the cell group may consist of one SpCell and one or more SCell. That is, the cell group consists of one SpCell and, optionally, one or more SCell. Also, the cell group may be expressed as a set of cell(s).

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

[0099] Also, in the case where DC is not set, the cell group set in the terminal device may be called the MCG. Also, in the case where DC is not set, the SpCell set in the terminal device may be the PCell. Also, NR where DC is not set may be called NR Standalone (NR SA).

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

[0101] For example, in the case where DC or MR-DC is set in the terminal device, one MAC entity for the MCG and one MAC entity for the SCG may exist. 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, SpCell may mean the PCell. Also, when the MAC entity is associated with the SCG, SpCell may mean the Primary SCG Cell (PSCell). Also, when the MAC entity is not associated with a cell group, 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 the E-UTRA MAC entity, and the MAC entity for the SCG may be the NR MAC entity. Also, in NE-DC, the MAC entity for the MCG may be the NR MAC entity and the MAC entity for the SCG may be the E-UTRA MAC entity. Also, in NR-DC, the MAC entities for the MCG and SCG may both be NR MAC entities. Note that the fact that there is one MAC entity for each cell group may be rephrased as there is one MAC entity for each SpCell. Also, the one MAC entity for each cell group may be rephrased as the one MAC entity for each SpCell. In addition, the MAC entity for the MCG may be the E-UTRA MAC entity, and the MAC entity for the SCG may be the NR MAC entity. Also, in NE-DC, the MAC entity for the MCG may be the NR MAC entity, and the MAC entity for the SCG may be the E-UTRA MAC entity. Also, in NR-DC, the MAC entities for the MCG and SCG may both be NR MAC entities. It should be noted that the fact that there is one MAC entity for each cell group can be rephrased as there is one MAC entity for each SpCell. Also, the one MAC entity for each cell group can be rephrased as the one MAC entity for each SpCell. 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, the MAC entity for the SCG in the terminal device 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, SpCell may mean the PCell. Also, when the MAC entity is associated with the SCG, SpCell may mean the Primary SCG Cell (PSCell). Also, when the MAC entity is not associated with a cell group, 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 the E-UTRA MAC entity, and the MAC entity for the SCG may be the NR MAC entity. Also, in NE-DC, the MAC entity for the MCG may be the NR MAC entity, and the MAC entity for the SCG may be the E-UTRA MAC entity. Also, in NR-DC, the MAC entities for the MCG and SCG may both be NR MAC entities. Note that the fact that there is one MAC entity for each cell group may be rephrased as there is one MAC entity for each SpCell. Also, the one MAC entity for each cell group may be rephrased 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 will be described. FIG. 4 is a diagram showing an example of a flow of procedures for various settings in the RRC according to the present 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).

[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: System Information) 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, security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and the like. 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, and the like. 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, and the like. 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 causing a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and the like. The processing to be performed on a specific terminal device may include, for example, security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and the like. The processing to be performed on a specific terminal device may include, for example, security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and the like. 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, and the like. The creation of the RRC message in the base station device may also 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, and the like. 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, the terminal apparatus performs processing such as setting if necessary according to the received above-described 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] For MR-DC, the RRC of the master node side may be used to transfer RRC signaling for SCG side settings (such as cell group settings, radio bearer settings, measurement settings, etc.) between the terminal apparatus. For example, in EN-DC or NGEN-DC, the RRC signaling of NR may be included in the form of a container in the E-UTRA RRC signaling transmitted and received between eNB102 and UE122. Also, in NE-DC, the RRC signaling of E-UTRA may be included in the form of a container in the NR RRC signaling transmitted and received between gNB108 and UE122. The RRC signaling for SCG side settings may be transmitted and received between the master node and the secondary node.

[0106] In addition, not limited to the case of using MR-DC, the RRC signaling for E-UTRA transmitted from eNB102 to UE122 may include the RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include the RRC signaling for E-UTRA. The RRC signaling for NR may be included in the form of a container in the E-UTRA RRC signaling transmitted and received between eNB102 and UE122. Also, in NE-DC, the RRC signaling for E-UTRA may be included in the form of a container in the NR RRC signaling transmitted and received between gNB108 and UE122. The RRC signaling for SCG side settings may be transmitted and received between the master node and the secondary node.

[0107] Note that not limited to the case of using MR-DC, the RRC signaling for E-UTRA transmitted from eNB102 to UE122 may include the RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include the RRC signaling for E-UTRA. The RRC signaling for NR may be included in the RRC signaling for E-UTRA transmitted from eNB102 to UE122, and the RRC signaling for E-UTRA may be included in the RRC signaling for NR transmitted from gNB108 to UE122.

[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 the terminal devices using a broadcast session. The terminal devices may receive the 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 the terminal devices using a multicast session. The terminal devices may receive the multicast ser vices using mechanisms such as PTP delivery and / or PTM delivery. HARQ feedback / resending is applicable to both PTP transmission and PTM transmission and can be carried out.

[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 for transmitting 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. The terminal device may use the same or different G-RNTI can be used to receive different services. The terminal device can use the same or different G-CS-RNTIs to receive different services.

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

[0114] When both PTM transmission and PTP transmission are configured for a terminal device, the gNB may dynamically determine whether to deliver multicast data to a specific terminal device via the PTM leg and / or the PTP leg based on information such as the MBS session QoS requirements, the number of participating terminal devices, and the per-terminal device reception quality feedback. Also, regardless of the above 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 MCCH in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. Parameters necessary for receiving MCCH may be provided via system information.

[0116] The following principles may apply to the structure of MCCH. · MCCH may provide a list of some or all of the broadcast services transmitted on MTCH, and / or information related to the broadcast session. The information related to the broa dcast session may include the MBS session ID, related G-RNTI scheduling information, and information about neighboring cells that provide a specific service on 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. · MCCH may use a change period, and the MCCH content may only be allowed to change 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 the terminal device receives an MCCH change notification, it may obtain the updated MCCH in the same MCCH change period in which the change notification was sent.

[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 neighboring 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 as follows. · 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 made 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 · MBS frequencies that the terminal device is receiving or interested in receiving, uni Cast bearers, and the priority of receiving multicast MRBs · 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 mapping information between the current carrier frequency and / or adjacent carrier frequencies and 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 a set of UEs. ​​Yes. For example, the gNB may use the group common PDCCH scrambled with the group common RNTI to schedule the group common PDSCH scrambled with the same 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 session 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 service as the MBS broadcast service 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 the 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 other than zero, the PDCCH monitoring occasion for the MCCH message may be determined based on the search space indicated by searchspaceMCCH. 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.

[0129] If the network changes some or all of the MCCH information, the network may notify the terminal device of the change from the start of the MCCH modification period using the PDCCH for scheduling the MCCH. The terminal device that has received the notification of the change may obtain the new MCCH information from the same slot in which the notification of the change was received if it is receiving or interested in receiving the MBS service transmitted using the MBS broadcast. The terminal device may apply the previously obtained MCCH information until the new MCCH information is obtained. 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.

[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. It may be applied to an MBS broadcast service that a certain BWP is in the RRC_CONNECTED state where it is an active BWP and that an MBS-capable terminal device is receiving or is interested in receiving. Yes.

[0131] If the terminal device is interested in receiving the MBS broadcast service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device is interested in receiving the MBS broadcast service, when the terminal device enters a cell that provides SIB20 (for example, when powered on or after the terminal device moves), when receiving SIB20 of the SCell via dedicated signaling, and when notified of a change in the MCCH information due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device receiving data via the broadcast MRB is notified of a change in the MCCH information due to a change in the MCCH information other than the change due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information. If the terminal device is interested in receiving the MBS broadcast service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device is interested in receiving the MBS broadcast service, when the terminal device enters a cell that provides SIB20 (for example, when powered on or after the terminal device moves), when receiving SIB20 of the SCell via dedicated signaling, and when notified of a change in the MCCH information due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device receiving data via the broadcast MRB is notified of a change in the MCCH information due to a change in the MCCH information other than the change due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information. When the terminal device is interested in receiving the MBS broadcast service, when the terminal device enters a cell that provides SIB20 (for example, when powered on or after the terminal device moves), when receiving SIB20 of the SCell via dedicated signaling, and when notified of a change in the MCCH information due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device receiving data via the broadcast MRB is notified of a change in the MCCH information due to a change in the MCCH information other than the change due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information. When the terminal device is interested in receiving the MBS broadcast service, when the terminal device enters a cell that provides SIB20 (for example, when powered on or after the terminal device moves), when receiving SIB20 of the SCell via dedicated signaling, and when notified of a change in the MCCH information due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device receiving data via the broadcast MRB is notified of a change in the MCCH information due to a change in the MCCH information other than the change due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information. When the terminal device is interested in receiving the MBS broadcast service, when the terminal device enters a cell that provides SIB20 (for example, when powered on or after the terminal device moves), when receiving SIB20 of the SCell via dedicated signaling, and when notified of a change in the MCCH information due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device receiving data via the broadcast MRB is notified of a change in the MCCH information due to a change in the MCCH information other than the change due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information. When the terminal device is interested in receiving the MBS broadcast service, when the terminal device enters a cell that provides SIB20 (for example, when powered on or after the terminal device moves), when receiving SIB20 of the SCell via dedicated signaling, and when notified of a change in the MCCH information due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. When the terminal device receiving data via the broadcast MRB is notified of a change in the MCCH information due to a change in the MCCH information other than the change due to the start of a new MBS service, the terminal device may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information.

[0132] If the terminal device is receiving or is interested in receiving the MBS broadcast service If the MCCH information acquisition procedure is triggered based on being notified of a change in the MCCH information, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which the change in the MCCH information was notified. Also, if the terminal device enters a cell that provides SIB20 or receives the information included in SIB20 notified by the SCell via RRC signaling, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the next repetition period. If the terminal device is receiving or is interested in receiving the MBS broadcast service, if the MCCH information acquisition procedure is triggered based on being notified of a change in the MCCH information, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which the change in the MCCH information was notified. Also, if the terminal device enters a cell that provides SIB20 or receives the information included in SIB20 notified by the SCell via RRC signaling, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the next repetition period. If the terminal device is receiving or is interested in receiving the MBS broadcast service, if the MCCH information acquisition procedure is triggered based on being notified of a change in the MCCH information, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which the change in the MCCH information was notified. Also, if the terminal device enters a cell that provides SIB20 or receives the information included in SIB20 notified by the SCell via RRC signaling, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the next repetition period.

[0133] The broadcast MRB configuration procedure may be used by 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-enabled 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 the MBS session of the MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-enabled terminal device interested in receiving the MBS broadcast service enters the cell providing 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 limitation is 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 the session of the MBS broadcast service. The broadcast MRB release procedure may be performed when the MBS session is stopped, when the terminal device leaves the cell 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 the MBS session of the MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-enabled terminal device interested in receiving the MBS broadcast service enters the cell providing 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 limitation is 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 the MBS session of the MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-enabled terminal device interested in receiving the MBS broadcast service enters the cell providing 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 limitation is 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 the MBS session of the MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-enabled terminal device interested in receiving the MBS broadcast service enters the cell providing 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 limitation is 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 the MBS session of the MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-enabled terminal device interested in receiving the MBS broadcast service enters the cell providing 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 limitation is 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 the MBS session of the MBS broadcast service it is interested in. The broadcast MRB configuration procedure may be started when an MBS-enabled terminal device interested in receiving the MBS broadcast service enters the cell providing 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 limitation is 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 the session of the MBS broadcast service. The broadcast MRB release procedure may be performed when the MBS session is stopped, when the terminal device leaves the cell 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 the session of the MBS broadcast service. The broadcast MRB release procedure may be performed when the MBS session is stopped, when the terminal device leaves the cell 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 limit that hinders communication is started, etc.

[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). Also, 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, 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 for which the associated MRB has disappeared. ties.

[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 set ting 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 identifier information (TMGI) of the MBS broadcast session. The TMGI may include identifier information of the PLMN, or a value of an 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 include one or a plurality of entries. The entries in the MBS session information list may include a 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 settings of broadcast MRB (for example, PDCP settings and RLC settings).

[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 a terminal device (UE122) in this embodiment. Note that, in order to avoid complicating the description, FIG. 5 shows the main components closely related to this 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 parameters included in the received control information, and a transmitting unit 504 that transmits control information (UCI, MAC control element, RRC signaling, etc.) to the base station device. This base station device may be an eNB102 or a 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 may include some or all of a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), an RLC layer processing unit (RLC processing unit), a PDCP layer processing unit (PDCP processing unit), an SDAP layer processing unit (SDAP processing unit), an RRC layer processing unit (RRC processing unit), and a part of the NAS layer processing unit (NAS processing unit).

[0144] FIG. 6 is a block diagram showing the configuration of the base station apparatus in the present embodiment. Note that, to avoid complication of the description, FIG. 6 shows only the main components closely related to the present embodiment. This base station apparatus may be an eNB 102 or a gNB 108.

[0145] The base station apparatus shown in FIG. 6 includes a transmission unit 600 that transmits control information (DCI, RRC signaling, notification information, etc.) to the UE 122, and a processing unit 602 that creates control information (DCI, RRC signaling including parameters, notification information, etc.) and causes the processing unit 502 of the UE 122 to perform processing by transmitting it to the UE 122, and a reception unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. The processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, the MAC layer, the RLC layer, the PDCP layer, the SDAP layer, the RRC layer, and also the NAS layer). That is, the processing unit 602 may include some or all of a physical layer processing 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 a part of the NAS layer processing unit.

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

[0147] FIG. 7 is a diagram showing an example of the processing of the terminal device (UE 122) 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 apparatus (step S7 ​​00). 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 an area 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 an area formed by connecting a plurality of Reference points as one entry (c) The index of the SSB (d) Other information indicating a geographical area

[0151] Each of the areas indicated by the entry may be identified by an identifier. Also, the area indicated by the one or more entries may be defined as one area, and in this case, an identifier may be associated with each area indicated by the one or more entries. The identifier for identifying the 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 the area is indicated by the 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 . 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 configuration 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 . In addition or alternatively, the TMGI included in each entry of the MBS session information list may be associated with zero or more areas. In addition to that, zero or more areas may be associated with each entry of the MBS session information list Alternatively or instead, a G-RNTI included in each entry of the MBS session information list may be associated with zero or more areas. In addition or instead, an MB A PLMN included in each entry of the S session information list may be associated with zero or more areas. In addition or instead, each of the MBS session information list A service ID included in each entry may be associated with zero or more areas. FIG. 9 is a diagram showing an example in which an area identifier is included in an MBS broadcast configuration message. The MBS broadcast configuration message (MBSBroadcastConfiguration) includes an MBS session information list (MBS-SessionInfoList). Each entry of the MBS session information list includes a TMGI and a G-RNTI, and optionally has one or more area identifiers in the entry A list (MbsAreaList) is included. 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 areas may be.

[0155] Also, for example, SIB20 includes setting information necessary to receive one or more MCCHs Each of the setting information necessary to receive the MCCH may be associated with zero or more areas 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 areas associated with the setting information necessary to receive this MCCH. FIG. 10 ​​This is a diagram showing an example in which a region identifier is included in SIB20. SIB20 includes a list of configuration information (McchConfigList) necessary for receiving one or more MCCHs. Each entry in the McchConfigList includes configuration information (MCCH-Config) necessary for receiving an MCCH, and as an option, a list (MbsAreaList) having one or more region identifiers in the entry is included. That is, since the MbsAreaList is not included in the McchConfig, it may be shown that the McchConfig is associated with zero regions. Also, one or more MBS sessions may be associated with each of the regions notified by the second information.

[0156] Also, one or more MBS sessions may be associated with each of the regions notified by the second information.

[0157] Also, there may be an MBS session that is not associated with any region (that is, is associated with zero regions).

[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 region in the cell providing the MBS broadcast service. In addition to or instead of that, the determination in step S702 is, for example, that the terminal device determines whether it is located in the region associated with the MBS sessions of the MBS broadcast services it is interested in receiving. The determination in step S702 may be, 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 region. In addition to or instead of that, the determination in step S702 is, for example, that the terminal device determines whether it is located in the region associated with the MBS sessions of the MBS broadcast services 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 region. 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 region. 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 region. Based on this, broadcast MRB setting procedures may be applied (started). In addition to this, instead, for example, the terminal device may apply (start) broadcast MRB setting procedures based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that the terminal device is interested in receiving. Based on the fact that the terminal device is located in an area associated with an MBS session of an MBS broadcast service that the terminal device is interested in receiving, broadcast MRB setting procedures may be applied (started). Based on the fact that the terminal device is not associated with any area of an MBS session of an MBS broadcast service that the terminal device is interested in receiving, the MBS session may be determined to be a permitted (receivable) MBS session. In addition to this 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 the terminal device is interested in receiving, the MBS session may be determined to be a permitted (receivable) MBS session. The terminal device may apply (start) broadcast MRB setting procedures only for permitted (receivable) MBS sessions. In addition to this or instead of this, in step S704, the terminal device may apply (start) broadcast MRB release procedures based on the 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 the terminal device is receiving, the terminal device may apply (start) broadcast MRB release procedures. 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 the terminal device is receiving, the MBS session may be determined to be a non-permitted (unreceivable) MBS session. The terminal device may apply (start) broadcast MRB release procedures only for permitted (receivable) MBS sessions.

[0160] In addition to this or instead of this, in step S704, based on the determination, the terminal device may apply (start) broadcast MRB release procedures. 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 the terminal device is receiving, the terminal device may apply (start) broadcast MRB release procedures. 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 the terminal device is receiving, the MBS session may be determined to be a non-permitted (unreceivable) MBS session. The terminal device ​A broadcast MRB release procedure may be applied (started) to an MBS session that is not permitted (unable to receive) reception.

[0161] In addition or alternatively, a terminal device in the RRC_IDLE state and the RRC_INACTIVE state may, in step S702, while camping on a frequency on which an MBS session of an MBS broadcast service being received or in which it is interested in receiving is provided, determine whether there is no area associated with the MBS session of the MBS broadcast service or whether the terminal device is located in the associated area.

[0162] In step S704, the terminal device may, based on the determination, regard the frequency on which an MBS broadcast service being received or in which it is interested in receiving (or an MBS session of the MBS broadcast service) is provided as the highest priority frequency. For example, the terminal device may, based on there being no area associated with the MBS broadcast service (or an MBS session of the MBS broadcast service) being received or in which it is 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 terminal device may, based on being located in the area associated with the MBS broadcast service (or an MBS session of the MBS broadcast service) being received or in which it is interested in receiving, regard the frequency on which this MBS session is provided 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 that 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 that 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 an 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 and / or the information of the MBS session that is permitted to be received from the network (base station device). Yes. 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. In step S704, for example, based on the fact that the MBS session of the MBS broadcast service that 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 that the terminal device is interested in receiving is the MBS broadcast service and / or the MBS session permitted to be received from the network (base station device),

[0168] In step S704, for example, the terminal device may apply (start) the broadcast MRB setting procedure based on the fact that the MBS session of the MBS broadcast service it is interested in receiving is not associated with any area. In addition to or instead of that, for example, the terminal device may be based on the fact that the MBS session of the MBS broadcast service it is interested in receiving is the MBS broadcast service and / or the MBS session permitted to be received from the network (base station device). Based on the fact that the MBS session of the MBS broadcast service that 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 that the terminal device is interested in receiving is the MBS broadcast service and / or the MBS session permitted to be received from the network (base station device), Based on this, the terminal device may apply (start) the broadcast MRB setting procedure. In addition to or instead of that, for example, the terminal device may be based on the fact that the MBS session of the MBS broadcast service it is interested in receiving is the MBS broadcast service and / or the MBS session permitted to be received from the network (base station device). Instead of that, for example, the terminal device may be based on the fact that the MBS session of the MBS broadcast service it is interested in receiving is the MBS broadcast service and / or the MBS session permitted to be received from the network (base station device). The MBS session of the broadcast service is permitted to be received from the network (base station device). Based on this, It may be applicable (start) the broadcast MRB setting procedure. The terminal device may receive Based on the fact that the MBS session of the MBS broadcast service that the terminal device 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 or alternatively, based on the fact that the MBS session of the MBS broadcast service that the terminal device is interested in receiving is an MBS broadcast service permitted to be received from the network (base station device), and / or an MBS session, 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 to the permitted ( receivable) MBS session.

[0169] In addition or alternatively, in step S704, for example, based on the fact that the MBS session of the received MBS broadcast service is not an MBS broadcast service permitted to be received from the network (base station device) and / or an MBS session, the terminal device may apply (start) the broadcast MRB release procedure. 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 an MBS broadcast service permitted to be received from the network (base station device) and / or an MBS session. The terminal device may apply (start) the broadcast MRB release procedure to the non-permitted ( non-receivable) MBS session. Based on the fact that the MBS session of the received MBS broadcast service is not an MBS broadcast service permitted to be 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. The terminal device may apply (start) the broadcast MRB release procedure to the non-permitted ( non-receivable) MBS session.

[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 provided as the highest priority frequency based on the fact that the MBS broadcast service is permitted to be received from the network (base station device), and / or the fact that there is an MBS session. 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 provided as the highest priority frequency based on the fact that the MBS broadcast service is not permitted to be received from the network (base station device), and / or the fact that there is no MBS session. from the network (base station device), and based on the fact that the MBS broadcast service is permitted to be received, and / or there is an MBS session in the MBS broadcast service, 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 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 provided as the highest priority frequency based on the fact that the MBS broadcast service is not permitted to be received from the network (base station device), and / or the fact that there is no MBS session. 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 provided as the highest priority frequency based on the fact that the MBS broadcast service is not permitted to be received from the network (base station device), and / or the fact that there is no MBS session. 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 provided as the highest priority frequency based on the fact that the MBS broadcast service is permitted to be received from the network (base station device), and / or the fact that there is an MBS session. from the network (base station device), and based on the fact that the MBS broadcast service is permitted to be received, and / or there is an MBS session in the MBS broadcast service, the frequency at which this MBS session is provided may be regarded as the highest priority frequency. from the network (base station device), and based on the fact that the MBS broadcast service is permitted to be received, and / or there is an MBS session in the MBS broadcast service, 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 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 provided as the highest priority frequency based on the fact that the MBS broadcast service is not permitted to be received from the network (base station device), and / or the fact that there is no MBS session.

[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. 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", and "associate with" may be mutually paraphrased. Also, in the above description, expressions such as "link to", "corresponding to", and "associate with" may be mutually paraphrased.

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

[0174] In the above description, "transition from X to Y" may be rephrased as "become Y from X". Also, in the above description, "cause to transition" may be rephrased as "determine the transition".

[0175] Also, 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. Also, 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 function a computer 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 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 read by the CPU as needed and corrected and written.

[0178] Note that a part of the device in the above-described embodiment may be implemented by a computer. In that case, a 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 including 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" 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 those that hold a program for a certain time, such as a volatile memory inside a computer system serving as a server or a client in that case. Also, the above program may be for realizing a part of the aforementioned functions, and furthermore, it may be possible to realize the aforementioned functions in combination with a program already recorded in the computer system.

[0180] Also, each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, that is, typically an integrated circuit or a plurality of integrated circuits. An electric circuit designed to execute the functions described in this specification may be a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable It may include a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor, or each of the circuits described above, may be composed of digital circuits or analog circuits. Also, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, it is also possible to use an integrated circuit based on such technology.

[0181] Note that this embodiment is not limited to the above-described embodiment. In the embodiment, an example of the apparatus has been described, but this embodiment is not limited thereto, and it can be applied to stationary or non-mobile electronic devices installed indoors and outdoors, for example, 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 the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. Also, a configuration in which elements described in the above embodiment and having the same effects are replaced with each other is also included.

Description of Reference Numerals

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

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 is information indicating a part or all of the area of the cell, the processing unit determines that an MBS session to which none of the area information is associated among the one or more MBS sessions, and an MBS session to which area information indicating the area where the terminal device is located is associated, are MBS sessions for which reception is permitted, and executes a broadcast MRB setting procedure to start receiving the MBS sessions determined to be permitted for reception. A terminal device.

2. A method applied to a terminal device that communicates with a base station device, the method 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 is information indicating a part or all of the area of the cell, determining that an MBS session to which none of the area information is associated among the one or more MBS sessions, and an MBS session to which area information indicating the area where the terminal device is located is associated, are MBS sessions for which reception is permitted, and executing a broadcast MRB setting procedure to start receiving the MBS sessions determined to be permitted for reception. A method.

3. 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, 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 part or all of the area of the cell, Among the one or more MBS sessions, the processing unit An MBS session not associated with any of the area information and an area indicating the area where the terminal device is located Information is associated, and it is determined that the MBS session is an MBS session for which reception is permitted, In order to start receiving the MBS session determined to be permitted to receive, a broadcast MRB setting procedure is executed Integrated circuit. Integrated circuit.

Images