Terminal device, method, and integrated circuit

Abstract

To provide a terminal device, a method, and an integrated circuit that efficiently provide a broadcast service to a specific area in a non-terrestrial network providing a multicast / broadcast service (MBS).SOLUTION: In a terminal device communicating with a base station device, a receiving unit receives control information and area information related to an MBS provided in cells of the base station device. The control information includes information associating sessions in the MBS with the area information, and the area information are information indicating the areas of the cells. A 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 on the basis of determining that an MBS session receiving information is not the MBS session permitted to receive information, executes broadcast MRB release procedures.SELECTED DRAWING: Figure 7

Description

Technical Field

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

Background Art

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

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

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

Prior Art Documents

Non-Patent Documents

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

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

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of the 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 has taken the following means. That is, one aspect of the present invention is a terminal device that communicates with a base station device, including a receiving unit that receives control information regarding one or more multicast broadcast services (MBS) provided in the cell of the base station device, and one or more area information, and a processing unit. The control information includes a part or all of an MBS session, and one or more of the above-mentioned areas information. Information is included that associates with rear information, and each of the area information indicates information on a part or all of the area of the cell, and the processing unit is the one or more MBS sessions Among them, an MBS session with no area information associated therewith, and the area information indicating the area where the terminal device is located is associated, is determined to be an MBS session for which reception is permitted and, based on determining that the received MBS session is not an MBS session for which reception is permitted, executes a broadcast MRB release procedure . .

[0009] Also, one aspect of the present invention is a method applied to a terminal device that communicates with a base station device, the method including steps of receiving control information regarding one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more area information, 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 on a part or all of the area of the cell, and among the one or more MBS sessions a session with no area information associated therewith, 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 based on determining that the received MBS session is not an MBS session for which reception is permitted, executes a broadcast MRB release procedure.

[0010] Also, one aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the integrated circuit receiving 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 Cause the terminal device to exhibit the function, and the control information includes information associating part or all of the 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. The processing unit determines, among the one or more MBS sessions, an MBS session that is not associated with any of the area information and an MBS session associated with the area information indicating the area where the terminal device is located as an MBS session whose reception is permitted. Based on the determination that the received MBS session is not an MBS session whose reception is permitted, execute a broadcast MRB release procedure.

[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 (RAT). 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 for the core network (core network, Core Network: CN) may be distinguished from conventional LTE that uses EPC for the core network. Note that Conventional LTE may mean LTE that does not implement technologies 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 be applied to technologies that use other terms , and / or other radio access technologies. Also, E-UTRA in this embodiment and the term LTE may be used interchangeably.

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

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

[0018] The E-UTRA 100 may be a radio access technology. The air interface between the UE 122 and the eNB 102 may be referred to as a Uu interface. The eNB (E-UTRAN Node B) 102 is the basis of the E-UTRA 100. The eNB 102 may be a base station device. The eNB 102 may have an E-UTRA protocol, which will be described later. The E-UTRA protocol includes an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA The eNB 102 may be configured with a control plane (CP) protocol. In contrast, the eNB may terminate an E-UTRA User Plane (UP) protocol and an E-UTRA Control Plane (CP) protocol. A radio access network configured with the eNB may be referred to as an E-UTRAN.

[0019] The EPC (Evolved Packet Core) 104 may be a core network. The interface 112 is an interface between the eNB 102 and the EPC 104, and may be referred to as an 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 the S1-MME interface. The user plane interface of the interface 112 may be referred to as the 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 the 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 the Uu interface. The gNB (g Node B) 108 may be a base station device of NR 106. The gNB 108 may have the NR protocol described below. The NR protocol may be composed of the NR user plane (UP) protocol described below and the 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] 5GC110 may be a core network. Interface 116 is an interface between gNB108 and 5GC110 and may be referred to as the NG interface. Interface 116 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 interface 116 may terminate at an Access and mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC110. The control plane interface of interface 116 may be referred to as the NG-C interface. The user plane interface of interface 116 may be referred to as the NG-U interface. In addition, one or more gNB108s may be connected to 5GC110 via interface 116. An interface may exist (not shown) between multiple gNB108s connected to 5GC110. The interface between multiple gNB108s connected to 5GC110 may be referred to as the Xn interface. eNB102 may have a function to connect to 5GC110. An eNB102 having a function to connect to 5GC110 may be referred to as an ng-eNB. Interface 114 is an interface between eNB102 and 5GC110 and may be referred to as the NG interface. Interface 114 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 interface 114 may terminate at an Access and mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC110. The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of interface 114 may be referred to as the NG-U interface.

[0023] One or more gNB108s may be connected to 5GC110 via interface 116. An interface may exist (not shown) between multiple gNB108s connected to 5GC110. The interface between multiple gNB108s connected to 5GC110 may be referred to as the Xn interface. eNB102 may have a function to connect to 5GC110. An eNB102 having a function to connect to 5GC110 may be referred to as an ng-eNB. Interface 114 is an interface between eNB102 and 5GC110 and may be referred to as the NG interface. Interface 114 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes.

[0024] The control plane interface of interface 114 may terminate at an Access and mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC110. The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of interface 114 may be referred to as the NG-U interface. The control plane interface of interface 114 may terminate at an Access and mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC110. The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of interface 114 may be referred to as the NG-U interface. The control plane interface of interface 114 may terminate at an Access and mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC110. The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of interface 114 may be referred to as the NG-U interface. ​This may be done. The control plane interface of interface 114 may terminate at the AMF within 5GC 110. The user plane interface of interface 114 may terminate at the UPF within 5GC 110. 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-eNBs or gNBs 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 eNBs, ng-eNBs, gNBs, etc.

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

[0026] The gNB 108 may have the function of connecting to the EPC 104. The gNB 108 having the function of connecting to the EPC 104 may be referred to as an en-gNB. Interface 118 is the interface between the gNB 108 and the EPC 104 and may be referred to as the S1 interface. There may be a user plane interface through which user data passes on interface 118 . The user plane interface of interface 118 may terminate at the S-GW (not shown) within the EPC 104. 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, some or all of the interfaces such as the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by a communications carrier or the like.

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

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

[0030] Also, when the core network to which eNB102 and / or gNB108 with which UE122 communicates is connected is 5GC110, each DRB established between UE122 and eNB102 and / or gNB108 may be further associated with one of the PDU (Packet Data Unit) sessions established within 5GC110. 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 may have information within a PDU session and / or a QoS flow, but does not necessarily have information on an EPS bearer. The UE 122 does not necessarily have information on an EPS bearer, but may have information within a PDU session and / or a QoS flow.

[0032] In the following description, the eNB 102 and / or the gNB 108 may also be simply referred to as a base station device, and the UE 122 may also be simply referred to as a terminal device or a UE.

[0033] FIG. 2 is a diagram of an example of an E-UTRA protocol architecture according to the present embodiment. FIG. 3 is a diagram of an example of an NR protocol architecture according to the present embodiment. The functions of each protocol described with reference to 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 a terminal device to a base station device. Also, in the present embodiment, the downlink (DL) may be a link from a base station device to a terminal device. Also, in the present embodiment, the sidelink (SL) may be a link from a terminal device to a terminal device without passing through a base station device. The functions of each protocol described with reference to 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 a terminal device to a base station device. Also, in the present embodiment, the downlink (DL) may be a link from a base station device to a terminal device. Also, in the present embodiment, the sidelink (SL) may be a link from a terminal device to a terminal device without passing through a base station device. In the present embodiment, the downlink (DL) may be a link from a base station device to a terminal device. Also, in the present embodiment, the sidelink (SL) may be a link from a terminal device to a terminal device without passing through a base station device. In the present embodiment, the sidelink (SL) may be a link from a terminal device to a terminal device without passing through a base station device. That is, the sidelink (SL) may be a link from a terminal device to a terminal device without passing through a base station device.

[0034] FIG. 2(A) is a diagram of an 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 by the eNB 102 on the network side. FIG. 2(A) 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 by 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 a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol terminated at the gNB 108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack may be composed of 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 a protocol between the UE 122 and the eNB 102. That is, the RRC 208 may be a protocol terminated at the eNB 102 on the network side. Also, 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 the protocol between the UE 122 and the MME. That is, NAS 210 may be the 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 the radio resource control layer, may be the protocol between the UE 122 and the gNB 108. That is, RRC 308 may be the 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 the protocol between the UE 122 and the AMF. That is, NAS 312 may be the protocol that terminates at the AMF on the network side.

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

[0039] ​In this embodiment, without distinguishing between the E-UTRA protocol and the NR protocol hereinafter, terms such as 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 E-UTRA protocol and the NR protocol hereinafter, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively referred to as the E-UTRA PHY or LTE PHY, the E-UTRA MAC or LTE MAC, the E-UTRA RLC or LTE RLC, the E-UTRA PDCP or LTE PDCP, and the E-UTRA RRC or LTE RRC. Also, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively the E-UTRA PHY or LTE PHY, the E-UTRA MAC or LTE MAC, the E-UTRA RLC or LTE RLC, the E-UTRA PDCP or LTE PDCP, and the E-UTRA RRC or LTE RRC, etc. may also be described. Also, when distinguishing between the E-UTRA protocol and the NR protocol 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, SDAP, and / or the data provided by the lower layer to MAC, RLC , PDCP, 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, SDAP, and / or the data provided by MAC, RLC, PDCP, 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 transmit signals in a higher layer. The higher layer may be called the upper layer, and they are interchangeable. For example, the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC signaling) in a Radio Resource Control (RRC) layer. The base station apparatus and the terminal apparatus may transmit and receive MAC control elements in a Medium Access Control (MAC) layer. The RRC layer of the terminal apparatus acquires system information broadcast from the base station apparatus. Here, the RRC message, the system information, and and / or the MAC control element receives higher layer signaling A parameter included in a higher layer signaling received by a terminal device may be referred to as a higher layer parameter. For example, in PHY layer processing, a higher layer means a higher layer seen from the PHY layer, and may mean one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, a higher layer may mean one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer, etc.

[0044] In the following, "A is given (provided) by a higher layer" or "A is given (provided) by a higher layer" means that a higher layer (mainly an RRC layer or a MAC layer) of the terminal device receives A from a base station device, and the received A is transmitted from the higher layer of the terminal device to a lower layer of the terminal device (mainly a MAC layer or a physical layer). For example, in a terminal device, The statement "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 statement "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 statement that 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 setting of a higher layer parameter in the terminal device may include the setting of a default parameter that is pre-given to the higher layer of the terminal device. 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: lower layer)" may be used. In the terminal device, "submit a message to the lower layer" from the RRC entity may mean submitting a message to the PDCP layer. In the terminal device, "submit a message to the lower layer" from the RRC layer may mean that since the RRC message is transmitted using an SRB (such as SRB0, SRB1, SRB2, SRB3), it means submitting a 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 PHY function 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. 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. PBCH (Physical Broadcast Channel)

[0046] It may be used to notify the system information required by the terminal device.

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

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

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

[0050] The PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, for the transmission of downlink control information, one or more DCIs (which may also be referred to as DCI formats) may be defined. That is, fields for downlink control information may be defined as DCIs and mapped to information bits. The PDCCH may be transmitted at PDCCH candidates. The terminal device may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. Also, the terminal device may monitor PDCCH candidates at one or more configured monitoring occasions within a configured control resource set (CORESET) set by a search space configuration. The DCI format may also be used for scheduling of the PUSCH in a serving cell. The PUSCH may be used for transmitting user data, transmitting an RRC message described later, etc.

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

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

[0053] PUSCH may be used for transmitting uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer or for transmitting HARQ-ACK and / or CSI together with the uplink data. Also, PUSCH may be used for transmitting only CSI, or only HARQ-ACK and CSI. That is, PUSCH may be used for transmitting only UCI. Also, PDSCH or PUSCH may be used for transmitting RRC messages and 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 in the cell. Also, the RRC message transmitted from the base station device may be dedicated signaling for a certain terminal device. That is, UE specific information is dedicated to a certain terminal device ​It may be transmitted using the signaling of the UE. Also, the PUSCH may be used for transmitting the UE's capabilities in the uplink.

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

[0055] An example of the MAC function will be described. The MAC may be referred to as the MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by logical channel identifiers (or Logical Channel IDs). The MAC may be connected to the upper RLC via a logical channel. The logical channels may be divided into a control channel for transmitting control information and a traffic channel for transmitting user information according to the type of information to be transmitted. Also, the logical channels may be divided into uplink logical channels and downlink logical channels. 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 be provided from the PHY It may have a function of demultiplexing the received MAC PDU and providing it to the upper layer via 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 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 discontinuous transmission (DTX), a function of executing a random access (RA) procedure, a power headroom report (PHR) function of notifying information on transmit power available, and a buffer status report function of notifying information on the data amount in the transmit buffer. It may have functions such as a Buffer Status Report (BSR) function. The NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. Further, the MAC PDU may include a MAC control element (MAC CE), which is an element for performing control in the MAC.

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

[0057] The 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 a plurality of 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 the terminal device and the base station device. ​​This may be the case. The dedicated control information may be control information dedicated to each terminal device. The DCCH may be used when the terminal device has an RRC connection.

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

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

[0063] 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. MTCH may be a logical channel for multicast and / or broadcast. This may be the case.

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

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

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

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

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

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

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

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

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

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

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

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

[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 the function of segmenting and / or concatenating the data provided by the upper-layer PDCP and providing it to the lower layer. E-UTRA RLC may have the function of performing reassembly and re-ordering on the data provided by the lower layer and providing it to the upper layer. NR RLC may have the function of adding a sequence number independent of the sequence number added by PDCP to the data provided by the upper-layer PDCP. Also, NR RLC may have the function of segmenting the data provided by PDCP and providing it to the lower layer. Also, NR RLC may have the function of performing reassembly on the data provided by the lower layer and providing it to the upper layer. Also, RLC may have the function of retransmitting data and / or the retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have the function of performing error correction by ARQ. To perform ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of RLC to the transmitting side, may be referred to as a status report. Also, the status report transmission instruction sent from the transmitting side of RLC to the receiving side may be referred to as a poll. Also, RLC may have the function of retransmitting data and / or the retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have the function of performing error correction by ARQ. To perform ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of RLC to the transmitting side, may be referred to as a status report. Also, the status report transmission instruction sent from the transmitting side of RLC to the receiving side may be referred to as a poll. Also, RLC may have the function of adding a sequence number independent of the sequence number added by PDCP to the data provided by the upper-layer PDCP. Also, NR RLC may have the function of segmenting the data provided by PDCP and providing it to the lower layer. Also, NR RLC may have the function of performing reassembly on the data provided by the lower layer and providing it to the upper layer. Also, RLC may have the function of retransmitting data and / or the retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have the function of performing error correction by ARQ. To perform ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of RLC to the transmitting side, may be referred to as a status report. Also, the status report transmission instruction sent from the transmitting side of RLC to the receiving side may be referred to as a poll. Also, RLC may have the function of retransmitting data and / or the retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have the function of performing error correction by ARQ. To perform ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of RLC to the transmitting side, may be referred to as a status report. Also, the status report transmission instruction sent from the transmitting side of RLC to the receiving side may be referred to as a poll. Also, RLC may have the function of retransmitting data and / or the retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have the function of performing error correction by ARQ. To perform ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of RLC to the transmitting side, may be referred to as a status report. Also, the status report transmission instruction sent from the transmitting side of RLC to the receiving side may be referred to as a poll. Also, RLC may It may have a function to detect packet duplication. Also, RLC may have a function to discard data. RLC may have three modes: transparent mode (TM: Transparent Mode), unacknowledged mode (UM: Unacknowledged Mode), and acknowledged mode (AM: Acknowledged Mode). In TM, data received from the upper layer is not segmented, and addition of an RLC header may not be performed. A TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity. In UM, data received from the upper layer is segmented and / or concatenated, an RLC header is added, etc., but retransmission control of data may not be performed. A UM RLC entity may be a uni-directional entity or a bi-directional entity. When a UM RLC entity is a uni-directional entity, the UM RLC entity may be configured 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 configured as a UM 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, retransmission control of data may be performed, etc. An AM RLC entity is a bi-directional entity and may be configured as an AM RLC composed of a transmitting side and a receiving side. Note that data provided to the lower layer in TM and / or data provided from the lower layer may be called a TMD PDU. Also, data provided to the lower layer in UM and / or data provided from the lower layer may be called a UMD PDU. Also, data provided to the lower layer in AM, A TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity. In UM, data received from the upper layer is segmented and / or concatenated, an RLC header is added, etc., but retransmission control of data may not be performed. A UM RLC entity may be a uni-directional entity or a bi-directional entity. When a UM RLC entity is a uni-directional entity, the UM RLC entity may be configured 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 configured as a UM 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, retransmission control of data may be performed, etc. When a UM RLC entity is a bi-directional entity, the UM RLC entity may be configured as a UM RLC entity composed of a transmitting side and a receiving side. In AM, data received from the upper layer may be segmented and / or concatenated, an RLC header may be added, retransmission control of data may be performed, etc. An AM RLC entity is a bi-directional entity and may be configured as an AM RLC composed of a transmitting side and a receiving side. Note that data provided to the lower layer in TM and / or data provided from the lower layer may be called a TMD PDU. Also, data provided to the lower layer in UM and / or data provided from the lower layer may be called a UMD PDU. Also, data provided to the lower layer in AM, and data provided from the lower layer may be called an AMD PDU. or the data provided from the lower layer may be referred to as an AMD PDU. The RLC PDU formats used in E-UTRA RLC and the RLC PDU formats 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 referred to as an RLC DATA PDU (RLC Data PDU, RLC data PDU). Also, the control RLC PDU may be referred to as an RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU). An example of the functions of PDCP will be described. PDCP may be referred to as a PDCP sublayer. PDCP may have a function of maintaining sequence numbers. Also, PDCP may have a header compression / decompression function for efficiently transmitting user data such as IP packets (IP Packets) and Ethernet frames in a radio section. The protocol used for header compression / decompression of IP packets may be referred to as a ROHC (Robust Header Compression) protocol. Also, the protocol used for header compression / decompression of an Ethernet frame may be referred to as an EHC (Ethernet (registered trademark) Header Compression) protocol. Also, PDCP may have a function of encrypting / decrypting data. Also, PDCP may have a function of protecting data integrity / verifying data integrity. Also, PDCP may have a re-ordering function. Also, PDCP may have a retransmission function of PDCP SDUs. Also, PDCP may have a function of discarding data using a discard timer. Also, PDCP may have a duplication function

[0077] ​​​​PDCP may also have a function to discard duplicated received data. The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from the PDCP PDU format used in NR PDCP. There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0078] An example of the SDAP function is explained below. SDAP is a service data adaptation protocol layer (SDAP). SDAP is a data service adaptation protocol layer (SDAP). Mapping of downlink QoS flows sent to the device and data radio bearers (DRBs) The SDAP may have a function of mapping between the DRB and an uplink QoS flow sent from the terminal device to the 5GC110 via the base station device, and / or a function of mapping between the DRB and an uplink QoS flow sent from the terminal device to the 5GC110 via the base station device. The SDAP may also have a function of storing mapping rule information. The SDAP may also have a function of marking a QoS flow identifier (QoS Flow ID: QFI). The SDAP PDU may include a data SDAP PDU and a control SDAP PDU. The data SDAP PDU is called an SDAP DATA PDU (SDAP Data PDU, SDAP Data PDU). The SDAP PDU for control may be called SDAP CONTROL PDU (SDAP Control PDU, SDAP It may be called a control PDU, an SDAP control PDU). Note that there may be one SDAP entity for the terminal device for each PDU session.

[0079] An example of the functions of RRC will be described. RRC may have a notification (broadcast) function. RRC may have a calling (paging) function from the EPC 104 and / or the 5GC 110. RRC may have a calling (paging) function from the eNB 102 connected to the gNB 108 or the 5GC 110. Also, RRC may have an RRC connection management function. Also, RRC may have a radio bearer control function. Also, RRC may have a cell group control function. Also, RRC may have a mobility control function. Also, RRC may have a terminal device measurement reporting and terminal device measurement reporting control function. Also, RRC may have a QoS management function. Also, RRC may have a function for detecting and recovering from a radio link failure. RRC may 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 from radio link failure, etc. using RRC messages. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC. parameters.

[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 DCCH of the logical channel. ​​It may be. In addition to or instead of that, the RRC message may be sent using the MCCH of the logical channel. An RRC message sent using the DCCH is also referred to as dedicated RRC signaling or RRC signaling.

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

[0082] The RRC messages sent in the uplink (UL) direction using the CCCH may include, for example, an RRC Setup Request message, an RRC Resume Request message, an RRC Reestablishment Request message, an RRC System Info Request message, etc. Also, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. may be included. Other RRC messages may also be included. An RRC message sent using the DCCH is also referred to as dedicated RRC signaling or RRC signaling.

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

[0084] RRC signaling sent in the uplink (UL) direction using the DCCH includes, for example, a measurement report 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. They may also include, for example, 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 Informa It may include (such as) etc. Also, other RRC signaling may be included.

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

[0086] RRC messages sent in the downlink (DL) direction using MCCH may include, for example, MBS Broadcast Configuration 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. It may have a function for performing mobility management. Also, NAS may have a function for security control. It may have a function for security control.

[0088] The functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS described above are just 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. Some or all of the functions of each layer may be included in other layers.

[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 in which 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 in which 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. including a state in which UE 122 holds some or all of the UE context described later. Also, the RRC connection has been established may include a state in which 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., NAS layer) of the RRC layer of UE 122 may start the resume of the suspended RRC connection when UE 122 holds the UE's AS context, the resume of the RRC connection is permitted by the E-UTRAN, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. resume of the suspended RRC connection when UE 122 holds the UE's AS context, the resume of the RRC connection is permitted by the E-UTRAN, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. resume may be started.

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

[0092] Note that the RRC_CONNECTED state, the RRC_INACTIVE state, and the RRC_IDLE state may be referred to as the connected mode (connected mode), the inactive mode (inactive mode), and the idle mode (idle mode), respectively. Alternatively, they may be referred to as the RRC connected mode (RRC connected mode), the RRC inactive mode (RRC inactive mode), and the RRC idle mode (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 identity, 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 the gNB 108 may include the same information as the UE AS context held by the UE 122, or may include information different from the information included in the UE AS context held by the UE 122.

[0094] A security context may be information that includes all or part 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 an RRC connection 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 an RRC connection state where CA and / or DC described later are configured, a 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 connection 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-described 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 by the base station device for the terminal device will be described. The cell group may be composed of one SpCell. Also, the cell group may be composed of one SpCell and one or more SCell. That is, the cell group is one SpCell and, optionally, may be composed of one or more SCell as needed. Also, the cell group may be expressed as a set of cells

[0098] Dual Connectivity (DC) may be a technology that performs data communication using the radio resources of the cell groups respectively configured by the first base station device (first node) and the second base station device (second node). When DC or MR-DC described later is performed, the base station device may add a cell group to the terminal device . For 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 . The node may be called the "secondary node: SN". Also, the cell group constituted by the secondary node 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 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 stand-alone (NR SA)".

[0100] Note that "Multi-Radio Dual Connectivity (MR-DC)" may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technology that performs DC using NR for MCG and E-UTRA for SCG and may be a technology that performs DC using NR for both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC using E-UTRA for MCG and NR for SCG, there may be "E-UTRA-NR Dual Connectivity (EN-DC)" using EPC for the core network, or there may be "NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC)" using 5GC for the core network. Also, as an example of MR-DC using NR for MCG and E-UTRA for 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 MCG and 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, when DC or MR-DC is configured in the terminal device, there may be one MAC entity for MCG and one MAC entity for SCG. The MAC entity for 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 SCG in the terminal device may be created by the terminal device when 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 MCG, SpCell may mean PCell. Also, when the MAC entity is associated with SCG, SpCell may mean Primary SCG Cell (PSCell). Also, when the MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be an NR MAC entity. entity, and one MAC entity for SCG may exist. The MAC entity for 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 SCG may be created by the terminal device when 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 MCG, SpCell may mean PCell. Also, when the MAC entity is associated with SCG, SpCell may mean Primary SCG Cell (PSCell). Also, when the MAC entity is not associated with a cell group SpCell may mean PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be an NR MAC entity. It may be the case that the MAC entity for the SCG may be an E-UTRA MAC entity. Also, in NR-DC, the MAC entities for both the MCG and the SCG may both be NR MAC entities. Note that it may be rephrased that there is one MAC entity for each cell group, or that 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. Do so. 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) or paging messages. Also, the creation of the RRC message in the base station device may be performed to transmit RRC signaling for causing the base station device to perform processing on a specific terminal device. The processing to be performed on a specific terminal device may include, for example, settings related to security, 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. processing such as It may be included. Also, the creation of the RRC message in the base station apparatus may be performed in response to the RRC signaling transmitted from the terminal apparatus. The response to the RRC signaling transmitted from the terminal apparatus may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or values of the fields (including information elements). The RRC message may be described using a description method called ASN.1 (Abstract Syntax Notation One). The structure of the RRC message may be described using a description method called ASN.1 (Abstract Syntax Notation One).

[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 according to the received above-mentioned RRC signaling if necessary (step S404). The terminal apparatus that has performed the processing may transmit RRC signaling for response to the base station apparatus (not shown). The RRC signaling is not limited to the above example and may be used for other purposes.

[0105] In MR-DC, the RRC of the master node side may be used to transfer the RRC signaling for the SCG side settings (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 the eNB 102 and the UE 122. 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 the gNB 108 and the UE 122. The RRC signaling for the SCG side settings may be transmitted and received between the master node and the secondary node.

[0106] The RRC signaling for the SCG side settings may be transmitted and received between the master node and the secondary node.The RRC signaling for the 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 eNB 102 to UE 122 may include RRC signaling for NR, and the RRC signaling for NR transmitted from gNB 108 to UE 122 may include RRC signaling for E-UTRA.

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

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

[0110] In the 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. The multicast service may be delivered to the terminal devices using a multicast session. The terminal devices may receive the multicast ser vice using mechanisms such as PTP delivery and / or PTM delivery. HARQ feedback / resending can be applied to both PTP transmission and PTM transmission as well.

[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: A PTP channel defined for transmitting MBS data of a multicast session from a network to a terminal device MCCH: A PTM downlink channel used to transmit MBS broadcast control information related to one or more MTCHs and / or MBS multicast control information from a network to a terminal device to a terminal device

[0112] An example of the usage of RNTI in PTM transmission is shown. A terminal device can receive different services using the same or different G-RNTIs A terminal device can receive different services using the same or different G-CS-RNTIs

[0113] In a multicast service, the gNB may distribute MBS data packets using the following methods PTP transmission: The gNB may independently distribute 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 distributes separate copies of the MBS data packets scrambled with the same terminal device-specific RNTI to each terminal device PTM transmission: The gNB may distribute 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 distributes 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 shall use the MBS session QoS ​​​​Based on information such as requirements, number of participating terminals, and reception quality feedback of individual terminals, multicast data transfer is performed on either the PTM leg and / or the PTP leg for a specific terminal. In addition, regardless of the decision, the same QoS requirements may be applied to both PTM and PTP transmissions.

[0115] The MBS broadcast may be received by a terminal device in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. The terminal device may receive the MBS configuration for the broadcast session (e.g., parameters required for MTCH reception, etc.) via the MCCH in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. The parameters required for MCCH reception may be provided via system information.

[0116] The following principles may be applied to the structure of the MCCH. The MCCH may provide a list of some or all of the broadcast services transmitted on the MTCH and / or information related to the broadcast session. The information related to the cast session includes the MBS session ID, the associated G-RNTI scheduler, The MCCH content may include information about the MCCH repetition period, the MCCH window period, and the radio frame / sequence number. The time domain window may be transmitted within a regularly occurring time domain window defined by a lot offset. · The MCCH uses modification periods and MCCH content may only be allowed to change at modification period boundaries. A notification mechanism may be used to notify of MCCH content changes due to broadcast session start, change or stop, and neighbor cell information changes. When the terminal device receives an MCCH change notification, the terminal device may acquire an updated MCCH in the same MCCH change period in which the change notification was sent.

[0117] Regarding the continuity of broadcast services in the RRC_IDLE state and the RRC_INACTIVE state will be described.

[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 . Thereby, the terminal device can 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 at which frequencies the MBS broadcast service via PTM is provided through the User Service Description (USD) or in the following combination . · 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 camps on the frequencies that provide these MBS broadcast services and can receive these MBS broadcast services, and if certain conditions are met , this frequency can be set as the highest priority frequency. · When the MBS broadcast service that the terminal device is interested in becomes unavailable In the case (for example, after the session ends) or when the terminal device loses interest in receiving services, the terminal device does not need to increase the priority of the frequencies that provide these MBS broadcast services.

[0120] The continuity of the MBS broadcast service in the RRC_CONNECTED state will be described.

[0121] A terminal device in the RRC_CONNECTED state can send an MBS Interest Indication composed of the following information to the gNB to ensure the continuity of the MBS broadcast service. · A list of MBS frequencies that the terminal device is receiving or interested in receiving, sorted in descending order of importance · The MBS frequencies that the terminal device is receiving or interested in receiving, the priority of receiving unicast bearers, and 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 the mapping information between the current carrier frequency and / or adjacent carrier frequencies and the MBS Frequency Selection Area Identities (FSAI), the reporting of the MBS Interest indication may be implicitly enabled / disabled. Also, the information included in the MBS Interest indication may be exchanged between the source gNB and the target gNB during handover.

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

[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] MCCH may be used to deliver an MBS broadcast session provided in a cell and an MBS broadcast configuration message (MBSBroadcastConfiguration message) indicating 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 currently provided in the 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. related scheduling information is shown. It may be included. The terminal device may be provided with the configuration information required to receive the MCCH 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 within a set transmission window using a configurable repetition period. The MCCH transmission (and related radio resources and MCS) may be indicated by a PDCCH addressed to the MCCH-RNTI. It may be indicated by.

[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 receiving the MCCH message within the MCCH transmission window may be the same as that of the PDCCH monitoring occasion of SIB1. If searchspaceMCCH is set to a value other than zero, the PDCCH monitoring occasion for the MCCH message may be determined based on the search space indicated by searchspaceMCCH. It may be indicated by. If it is set to zero, the PDCCH monitoring occasion for receiving the MCCH message within the MCCH transmission window may be the same as that of the PDCCH monitoring occasion of SIB1. If searchspaceMCCH is set to a value other than zero, the PDCCH monitoring occasion for the MCCH message may be determined based on the search space indicated by searchspaceMCCH. If it is set to a value other than zero, the PDCCH monitoring occasion for the MCCH message may be determined based on the search space indicated by searchspaceMCCH.

[0129] The change of MCCH information may occur only in a specific radio frame, and the concept of a modification period may be used. Within the modification period, the same MCCH information may be transmitted the number of times defined by its scheduling. When the network changes some or all of the MCCH information, the network may notify the terminal device of the change from the start of the MCCH modification period using the PDCCH that schedules the MCCH. A terminal device that has received a 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 MBS broadcast. The terminal device may apply the previously obtained MCCH information until it obtains the new MCCH information. It may be transmitted the number of times defined by its scheduling. When the network changes some or all of the MCCH information, the network may notify the terminal device of the change from the start of the MCCH modification period using the PDCCH that schedules the MCCH. It may notify the terminal device of the change from the start of the MCCH modification period using the PDCCH that schedules the MCCH. A terminal device that has received a 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 MBS broadcast. If it is receiving or interested in receiving the MBS service transmitted using MBS broadcast, it may obtain the new MCCH information from the same slot in which the notification of the change was received. The terminal device may apply the previously obtained MCCH information until it obtains the new MCCH information.

[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 applied to the MBS broadcast services received by or of interest to the MBS-capable terminal device in the RRC_IDLE state, the RRC_INACTIVE state, or the RRC_CONNECTED state where a certain BWP is the active BWP in the common search space set by searchSpaceMCCH. When the terminal device is interested in receiving the MBS broadcast service, it may apply the MCCH information acquisition procedure. The terminal device interested in receiving the MBS broadcast service may apply the MCCH information acquisition procedure when entering a cell that provides SIB20 (for example, when powering 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. A terminal device receiving data via the broadcast MRB may apply the MCCH information acquisition procedure when 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. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information. 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 applied to the MBS broadcast services received by or of interest to the MBS-capable terminal device in the RRC_IDLE state, the RRC_INACTIVE state, or the RRC_CONNECTED state where a certain BWP is the active BWP in the common search space set by searchSpaceMCCH. Yes.

[0131] If the terminal device is interested in receiving the MBS broadcast service, it may apply the MCCH information acquisition procedure. If the terminal device is interested in receiving the MBS broadcast service, it may apply the MCCH information acquisition procedure. When the terminal device interested in receiving the MBS broadcast service enters a cell that provides SIB20 (for example, when powering 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, it may apply the MCCH information acquisition procedure. When the terminal device interested in receiving the MBS broadcast service enters a cell that provides SIB20 (for example, when powering 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, it may apply the MCCH information acquisition procedure. When the terminal device interested in receiving the MBS broadcast service enters a cell that provides SIB20 (for example, when powering 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, it may apply the MCCH information acquisition procedure. When the terminal device interested in receiving the MBS broadcast service enters a cell that provides SIB20 (for example, when powering 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, it may apply the MCCH information acquisition procedure. A terminal device receiving data via the broadcast MRB may apply the MCCH information acquisition procedure when 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. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information.

[0132] The terminal device that is receiving or interested in receiving the MBS broadcast service If the MCCH information acquisition procedure is triggered based on being notified of a change in MCCH information, the device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which the change in MCCH information was notified. Also, if the terminal device enters a cell that provides SIB20 or receives the information included in SIB20 notified by an SCell by RRC signaling, it 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 on the MTCH or when the configuration of the broadcast MRB received by the terminal device changes. The broadcast MRB configuration procedure may be applied to MBS-corresponding terminal devices that are in the RRC_IDLE state, RRC_INACTIVE state, or RRC_CONNECTED state where the BWP with a common search space set by searchSpaceMTCH or searchSpaceMCCH is the active BWP and that are receiving or interested in receiving an MBS broadcast service. .

[0134] The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The broadcast MRB configuration procedure is for MBS-corresponding terminal devices interested in receiving an MBS broadcast service when, at the start of an MBS session, when entering a cell that provides the MBS broadcast service, or when becoming interested in an ongoing MBS broadcast service. ​​​​​The ability limit is lifted, and the reception of the ongoing MBS broadcast service is no longer hindered It may be started when, for example

[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 started when the MBS session stops, when the terminal device leaves the cell that is broadcasting the MBS service it is interested in, when it loses interest in the MBS service, or when an ability limit that interferes with the reception of the relevant service is started such as

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

[0137] The terminal device may establish the PDCP entity, RLC entity, and / or 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

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

[0139] The terminal device may release the PDCP entity, RLC entity, and the relevant MAC settings and PHY ​​The settings may be released. Also, the terminal device may release the SDAP entity for which the associated MRB has disappeared.

[0140] The above-mentioned MBS broadcast configuration message (MBSBroadcastConfiguration message) may include information indicating one or more MBS broadcast sessions (MBS session information list). In addition to or instead of that, the MBS broadcast setting message may include a list of adjacent cells providing the same broadcast MBS service. 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 that, the TMGI may include an identifier (service ID) for identifying the MBS service within the PLMN. In addition to or instead of that, the MBS session information list may include one or a plurality of entries, and 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 that, 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 respective 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 the present embodiment. Note that, in order to avoid complication of the description, FIG. 5 shows only the main constituent parts closely related to the present embodiment.

[0143] ​ The UE 122 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 apparatus, 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 apparatus. This base station apparatus may be the eNB 102 or the gNB 108. Further, 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 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. In order 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 the eNB 102 or the gNB 108.

[0145] The base station apparatus shown in FIG. 6 includes a transmitting 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 receiving unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. Further, the processing unit 602 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 602 may include physical layer processing ​​​​ It may include part 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 (UE122) in the present embodiment. The processing unit 502 of the terminal device receives the first information and / or the second information from the base station device (step S700). The processing unit 502 of the terminal device determines, based on the second information, which of 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 region indicated by a reference location (geographical coordinates represented by longitude and latitude) and additional information ( for example, radius, diameter, and / or angle, etc.) is regarded as one entry, and a list containing one or more entries (b) A region formed by connecting a plurality of reference points is regarded as one entry, and one or more entries are included in the list (c) The index of the SSB (d) Information indicating other geographical regions

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

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

[0153] One or more regions 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 have a list with zero or more area identifiers in the entry. may be included. 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 or alternatively, the G-RNTI included in each entry of the MBS session information list may be associated with zero or more areas. In addition or alternatively, the PLMN included in each entry of the MBS session information list may be associated with zero or more areas. In addition or alternatively, the service ID included in each entry of the MBS session information list may be associated with zero or more areas. FIG. 9 is a diagram showing an example in which an area identifier is included in the 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 list (MbsAreaList). That is, since the MbsAreaList is not included in the entry of the MBS session information list, it may be shown that the entry is associated with zero areas. list (MbsAreaList). That is, since the MbsAreaList is not included in the entry of the MBS session information list, it may be shown that the entry is associated with zero areas. list (MbsAreaList). That is, it may be shown that the entry is associated with zero areas by the MbsAreaList not being included in the entry of the MBS session information list. list (MbsAreaList). That is, it may be shown that the entry is associated with zero areas by the MbsAreaList not being included in the entry of the MBS session information list. be.

[0155] Also, for example, SIB20 includes setting information necessary to receive one or more MCCHs, and each of the setting information necessary to receive the MCCH is associated with zero or more areas. is included, and each of the setting information necessary to receive the MCCH is associated with zero or more areas. This is acceptable. In this case, the MBS broadcast settings message to be received is based on the configuration information required to receive a certain MCCH, and all MBS sessions notified by the MBS broadcast settings message may be associated with zero or more regions corresponding to the configuration information required to receive this MCCH. FIG. 10 shows an example in which a region identifier is included in SIB20. SIB20 includes a list (McchConfigList) of configuration information required to receive one or more MCCHs. Each entry in McchConfigList includes the configuration information (MCCH-Config) required to receive an MCCH, and optionally includes a list (MbsAreaList) having one or more region identifiers in the entry. That is, it may be shown that since MbsAreaList is not included in McchConfig, the McchConfig is associated with zero regions. Further, one or more MBS sessions may be associated with each of the regions notified by the second information. Moreover, there may be an MBS session that is not associated with any region (i.e., is associated with zero regions). The determination in step S702 may be, for example, for the terminal device to determine 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. Additionally or alternatively, the determination in step S702 may be, for example, to determine whether the terminal device is located in the region associated with the MBS session of the MBS broadcast service it is interested in receiving. That is, it may be shown that since MbsAreaList is not included in McchConfig, the McchConfig is associated with zero regions.

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

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

[0158] The determination in step S702 may be, for example, for the terminal device to determine 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 or instead, the determination in step S702 may be, for example, to determine whether the terminal device is located in the region associated with the MBS session of the MBS broadcast service it is interested in receiving. That is, it may be shown that since MbsAreaList is not included in McchConfig, the McchConfig is associated with zero regions. Moreover, there may be an MBS session that is not associated with any region (i.e., is associated with zero regions).

[0159] In step S704, the terminal device may apply (start) the broadcast MRB setting procedure based on the determination. 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. Additionally or alternatively, for example, the terminal device may apply (start) the broadcast MRB setting procedure based on the fact that the terminal device is located in the area associated with the MBS session of the MBS broadcast service it is interested in receiving. The terminal device may determine that the MBS session is a permitted (receivable) MBS session based on the fact that the MBS session of the MBS broadcast service it is interested in receiving is not associated with any area. Additionally or alternatively, the terminal device may determine that the MBS session is a permitted (receivable) MBS session based on the fact that the terminal device is located in the area associated with the MBS session of the MBS broadcast service it is interested in receiving. The terminal device may apply (start) the broadcast MRB setting procedure only for the permitted (receivable) MBS sessions. In addition or alternatively, in step S704, the terminal device may apply (start) the broadcast MRB release procedure based on the determination. For example, the terminal device may apply (start) the broadcast MRB release procedure based on the fact that the terminal device is not located in the area associated with the MBS session of the MBS broadcast service it is receiving. The MBS session of the MBS broadcast service is not associated with any area. Based on this, the broadcast MRB setting procedure may be applied (started). In addition to this, Alternatively, for example, the terminal device may be located in the area associated with the MBS session of the MBS broadcast service it is interested in receiving. Based on this, the broadcast MRB setting procedure may be applied (started). The terminal device may determine that the MBS session is a permitted (receivable) MBS session based on the fact that the MBS session of the MBS broadcast service it is interested in receiving is not associated with any area. In addition to this or alternatively, the terminal device may determine that the MBS session is a permitted (receivable) MBS session based on the fact that the terminal device is located in the area associated with the MBS session of the MBS broadcast service it is interested in receiving. The terminal device may apply (start) the broadcast MRB setting procedure only for the permitted (receivable) MBS sessions.

[0160] In addition to this or alternatively, in step S704, the terminal device may apply (start) the broadcast MRB release procedure based on the determination. For example, the terminal device may apply (start) the broadcast MRB release procedure based on the fact that the terminal device is not located in the area associated with the MBS session of the MBS broadcast service it is receiving. This is also acceptable. Based on the fact that the terminal device is not located in the area associated with the MBS session of the received MBS broadcast service, the terminal device may determine that the MBS session is a non-permitted (unreceivable) MBS session. The terminal device may also apply (start) the broadcast MRB release procedure to a non-permitted (unreceivable) MBS session. In addition or alternatively, a terminal device in the RRC_IDLE state and the RRC_INACTIVE state may, in step S702, while camping on the frequency on which the MBS session of the MBS broadcast service being received or of interest to be received 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.

[0161] In step S704, based on the determination, the terminal device may regard the frequency on which the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or of interest to be received is provided as the highest-priority frequency. For example, based on the fact that there is no area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or of interest to be received, the terminal device may regard the frequency on which this MBS session is provided as the highest-priority frequency. In addition or alternatively, for example, based on the fact that the terminal device is located in the area associated with the MBS broadcast service (or the MBS session of the MBS broadcast service) being received or of interest to be received, the terminal device may regard the frequency on which this MBS session is provided as the highest-priority frequency.

[0162] ​​​​​​It may be regarded as a wave number.

[0163] In addition, in step S704, based on the determination, the terminal device does not regard the frequency at which the received or interesting MBS broadcast service (or the MBS session of the MBS broadcast service) is provided as the highest priority frequency. For example, based on the fact that the terminal device is not located in the area associated with the area associated with the received or interesting MBS broadcast service (or the MBS session of the MBS broadcast service), the terminal device does not regard the frequency at which this MBS session is provided as the highest priority frequency. It may be done. For example, based on the fact that the terminal device is not located in the area associated with the area associated with the received or interesting MBS broadcast service (or the MBS session of the MBS broadcast service), the terminal device does not regard the frequency at which this MBS session is provided as the highest priority frequency. It may be done. It may be done.

[0164] Note that as the above-mentioned 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. Thus, 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 obtaining only the 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 obtaining both lists. It may be done. By this, the base station device can provide an MBS broadcast service by PTM distribution in 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. It may be done. It may be done. It may be done.

[0165] With the above mechanism, the base station device can provide an MBS broadcast service by PTM distribution in 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. It becomes possible to receive the

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

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

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

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

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

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

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

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

[0174] In the above description, "transition from X to Y" may be rephrased as "become Y from X". Also, in the above description, "cause a transition" may be rephrased as "determine a 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, "D may be E" may also be included. Also, in the above description, when "F may be G" and "G may be H" are described, "F may be H" may also be included.

[0177] The program that operates on the device according to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of this embodiment. The program or the information handled by the program is temporarily read into a volatile memory such as Random Access Memory (RAM) during processing, or stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD), and is read by the CPU as needed and 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 includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0179] Furthermore, the "computer-readable recording medium" 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 that serves as a server or a client in that case. Moreover, the above program may be for realizing a part of the aforementioned functions, and may further be a combination with a program already recorded in the computer system for realizing the aforementioned functions.

[0180] Also, each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, that is, typically an integrated circuit or a plurality of integrated circuits. An electric circuit designed to execute the functions described in this specification includes a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable It may include a 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 the 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 is described, but this embodiment is not limited thereto, and it can be applied to stationary or non-mobile electronic devices installed indoors and outdoors, 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. However, 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 effect are replaced with each other is included.

Explanation 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, 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; a receiving unit; and a processing unit, wherein the control information includes information associating part or all of an MBS session with one or more of the area information, each of the area information is information indicating part or all of the area of the cell, the processing unit determines, among the one or more MBS sessions, an MBS session not associated with any of the area information and an MBS session associated with area information indicating the area where the terminal device is located as an MBS session permitted to be received, and based on determining that the received MBS session is not an MBS session permitted to be received, executes a broadcast MRB release procedure 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 part or all of an MBS session with one or more of the area information, each of the area information is information indicating part or all of the area of the cell, among the one or more MBS sessions, determining an MBS session not associated with any of the area information and an MBS session associated with area information indicating the area where the terminal device is located as an MBS session permitted to be received, and based on determining that the received MBS session is not an MBS session permitted to be received, executes a broadcast MRB release procedure 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 part or all of an MBS session with one or more of the area information, ​ ​ ​ ​ ​ ​ ​ ​ ​ including information associated with the A information, each of the area information indicates information of a part or all of the area of the cell, the processing unit, among the one or more MBS sessions, any of the area information an MBS session not associated therewith, and an area indicating the area where the terminal device is located information is determined to be an MBS session for which reception is permitted, based on determining that the received MBS session is not an MBS session for which reception is permitted, execute a broadcast MRB release procedure Integrated circuit.

Images