Terminal device, method, and integrated circuit

Abstract

To provide a terminal device, a method, and an integrated circuit for efficiently providing a multicast broadcast service (MBS).SOLUTION: In a communication system, a terminal device UE 122 communicating with a base station device includes a receiving unit that receives control information and region information related to an MBS from the base station device, and a processing unit. The control information includes information that associates an MBS multicast session with the region information, and each piece of the region information indicates a cell region. The processing unit determines that the terminal device has entered one of the regions included in the control information on the basis of the region information included in the control information and location information held by the terminal device, and acquires the control information from the base station device on the basis of the determination that the terminal device has entered one of the regions.SELECTED DRAWING: Figure 7

Description

[Technical Field]

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

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

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

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

[0005] [Non-Patent Document 1] 3GPP TS 38.331 v18.0.0,"Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specifications" pp70-354,pp427-435,439-1472 Summary of the Invention [Problem to be solved by the invention]

[0006] In 3GPP, as an extension technology of NR, for example, in the study of non-terrestrial networks (NTN: Non-Terrestrial Network), multicast / broadcast services are provided. However, because the size of a cell provided by a satellite is larger than that of a cell in a terrestrial network, it may be difficult to provide broadcast services to a specific area (such as within a country or state).

[0007] One aspect of the present invention has been made in consideration of the above-mentioned circumstances, and is a method for transmitting multicast / broadcast One of the objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently provide a broadcast service. [Means for solving the problem]

[0008] In order to achieve the above object, one aspect of the present invention provides the following means: That is, one aspect of the present invention provides a terminal device that communicates with a base station device, the terminal device receiving one or more multicast broadcast services (MBS) provided in a cell of the base station device, The control information includes a part or all of a session of an MBS and one or more pieces of region information, and a processing unit. The area information includes information that associates the area information with information that indicates a part or all of the area of ​​the cell, and the processing unit is configured to The MBS session is not associated with any of the area information, or The MBS center is connected to the area information indicating the area where the terminal device is located. The frequency on which the session is provided is considered the highest priority frequency.

[0009] Another aspect of the present invention is a method applied to a terminal device that communicates with a base station device, the method comprising: receiving control information relating to one or more multicast broadcast services (MBS) provided in a cell of the base station device, and one or more pieces of area information; The control information includes a part or all of the sessions of the MBS and one or more The information includes information associating the MBS session with the area information of each of the cell, each of the area information being information indicating a part or all of the area of ​​the cell, and the processing unit detects that the MBS session being received or being interested in receiving is not associated with any of the area information. Alternatively, the frequency through which the MBS session is provided is regarded as the frequency with the highest priority based on the fact that it is associated with area information indicating the area in which the terminal device is located.

[0010] Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the integrated circuit receiving control information and one or more area information related to one or more multicast broadcast services (MBS) provided in a cell of the base station device. The control information includes a part or all of the MBS session. and one or more pieces of area information, each piece of area information being information indicating a part or all of the area of ​​the cell, and the processing unit is configured to determine whether an MBS session being received or interested in receiving corresponds to any of the area information. The frequency on which the MBS session is provided is determined to be the frequency with the highest priority based on whether the frequency is associated with area information indicating the area in which the terminal device is located or whether the frequency is associated with area information indicating the area in which the terminal device is located. I reckon.

[0011] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. [Effects of the Invention]

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

[0013] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of an E-UTRA protocol configuration according to the present embodiment. [Figure 3] FIG. 1 is a diagram illustrating an example of an NR protocol configuration according to this embodiment. [Figure 4] FIG. 10 is a diagram showing an example of a flow of procedures for various settings in RRC according to the present embodiment. [Figure 5] FIG. 2 is a block diagram showing the configuration of a terminal device according to the embodiment. [Figure 6] FIG. 2 is a block diagram showing the configuration of a base station device according to the present embodiment. [Figure 7] 10 shows an example of processing in this embodiment. [Figure 8] 10 shows an example of an ASN.1 description of area information in this embodiment. [Figure 9] 10 is an example of an ASN.1 description of a system information block in this embodiment. [Figure 10] 10 shows an example of an ASN.1 description of an MBS broadcast setting in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (RATs). LTE, which can be connected to NR via Multi-Radio Dual Connectivity (MR-DC), may be distinguished from conventional LTE. LTE, which uses 5GC for the core network (Core Network: CN), may be distinguished from conventional LTE, which uses EPC for the core network. Conventional LTE may refer to LTE that does not implement technologies standardized in 3GPP Release 15 or later. This embodiment may be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR are used, but this embodiment may also apply to technologies that use other terms. , and / or other radio access technologies. The terms LTE and LTE may be used interchangeably.

[0016] In this embodiment, the names of each node and entity, and the processes in each node and entity 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 each node and entity, and the names of 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] 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 the Uu interface. The eNB (E-UTRAN Node B) 102 is the base station of the E-UTRA 100. The eNB 102 may be a base station device. The eNB 102 may have the 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 the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol. A radio access network made up of eNBs may be called E-UTRAN.

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

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

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

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

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

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

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

[0026] The gNB 108 may have a function to connect to the EPC 104. The gNB 108 having a function to connect to the EPC 104 may be called an en-gNB. The interface 118 is an interface between the gNB 108 and the EPC 104, and is an S1 The interface 118 may be referred to as a user program interface through which user data passes. There may be a lane interface. The interface may terminate at an S-GW (not shown) in the EPC 104. The interface may be referred to as an S1-U interface. The eNB 102 connecting to the EPC 104 and the gNB 108 connecting to the EPC 104 may be connected by an interface 120. The interface 120 between the eNB 102 connecting to the EPC 104 and the gNB 108 connecting to the EPC 104 may be referred to as an X2 interface.

[0027] The interface 124 is an interface between the EPC 104 and the 5GC 110, and can be used with only the CP or the UP. In addition, 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 be interfaces that are connected to a communication system provided by a communication carrier or the like. It may not be present depending on the system.

[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. The UE 122 may also be a terminal device capable of wireless connection with the eNB 102 and / or the gNB 108. The UE 122 may also be a terminal device capable of wireless connection with the eNB 102. The UE 122 may be a terminal device capable of simultaneously establishing a radio connection with the gNB 108 and a radio connection with the gNB 108. The UE 122 may have an E-UTRA protocol and / or an NR protocol. The radio connection may be a Radio Resource Control (RRC) connection.

[0029] The UE 122 also communicates with the EPC 104 and / or the 5GC 110 via the eNB 102 and / or the gNB 108. When the core network to which the eNB 102 and / or gNB 108 with which the UE 122 communicates is connected is the EPC 104, each Data Radio Bearer (DRB) (described later) established between the UE 122 and the eNB 102 and / or gNB 108 is further routed through the EPC 104. Each EPS bearer may be uniquely associated with an Evolved Packet System (EPS) bearer. Each EPS bearer may be identified by an EPS bearer identity (ID). In addition, IP packets passing through the same EPS bearer may be uniquely associated with an EPS bearer. The same QoS may be guaranteed for data such as packets and Ethernet frames. .

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

[0031] There may be no PDU sessions and / or QoS flows in the EPC 104. When the UE 122 is connected to the EPC 104, the UE 122 has knowledge of the EPS bearers, but may not have knowledge of the PDU sessions and / or QoS flows. Also, when the UE 122 is connected to the 5GC 110, the UE 122 may It has information about the EPS bearer, but does not need to have information about the EPS bearer.

[0032] In the following description, eNB102 and / or gNB108 will also be simply referred to as base station devices, and UE122 will also be simply referred to as terminal devices or UEs.

[0033] FIG. 2 is a diagram illustrating an example of an E-UTRA protocol architecture according to this embodiment. FIG. 3 is a diagram illustrating an example of an NR protocol architecture according to this embodiment. The functions of each protocol described with reference to FIG. 3 are some of the functions closely related to this embodiment. In this embodiment, the uplink (UL) may be a link from a terminal device to a base station device. The link (downlink: DL) may be a link from a base station device to a terminal device. In this configuration, sidelink (SL) refers to the base station equipment from the terminal equipment to the terminal equipment. It may be a link that does not involve a

[0034] Figure 2(A) is a diagram of an E-UTRA user plane (UP) protocol stack. As shown in Figure 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 that terminates at the eNB 102 on the network side. As shown in Figure 1, the E-UTRA user plane protocol stack includes a PHY (Physical layer) 200, which is a radio physical layer, and a MA (Media Access Control) layer. It may be composed of a Medium Access Control (C) 202, a Radio Link Control (RLC) 204 which is a radio link control layer, and a Packet Data Convergence Protocol (PDCP) 206 which is a packet data convergence protocol layer.

[0035] Figure 3(A) shows the NR user plane (UP) protocol stack. As shown in Figure 3(A), the NR The UP protocol may be a protocol between the UE 122 and the gNB 108, i.e., the NR UP protocol. On the network side, the NR user plane protocol stack may be a protocol that terminates at the gNB 108. As shown in Figure 3(A), the NR user plane protocol stack may consist of a radio physical layer, PHY 300, a medium access control layer, MAC 302, a radio link control layer, RLC 304, a packet data convergence protocol layer, PDCP 306, and a service data adaptation protocol layer, SDAP (Service Data Adaptation Protocol) 310.

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

[0037] Figure 3(B) shows the NR control plane (CP) protocol configuration. As shown in Figure 3(B), the NR CP protocol In the protocol, the radio resource control layer RRC 308 controls the protocol between the UE 122 and the gNB 108. That is, the RRC 308 may be a protocol that terminates at the gNB 108 on the network side. In the NR CP protocol, the NAS 312, which is a non-AS layer, is a protocol between the UE 122 and the AMF. That is, NAS 312 may be a protocol that terminates at AMF on the network side. It's okay.

[0038] The AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and / or the gNB 108. That is, the AS layer may be one of the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208. Layers including some or all of the PHY300, MAC302, RLC304, PDCP306, SDAP310, and and RRC 308.

[0039] In the present embodiment, the E-UTRA protocol and the NR protocol may not be distinguished from each other, and the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), 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 respectively refer to 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, 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. The SDAP (SDAP layer) may also be the SDAP (SDAP layer) of the NR protocol.

[0040] In this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 are referred to as the PHY for E-UTRA or the PHY for LTE, the MAC for E-UTRA or the MAC for LTE, the RLC for E-UTRA or the RLC for LTE, and the PDCP for E-UTRA or the LTE The PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are sometimes referred to as the E-UTRA PHY or LTE PHY, and the E-UTRA MAC or LTE RRC, respectively. It may also be written as MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC. Also, a distinction is made between E-UTRA protocols and NR protocols. In this case, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Also, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively. There are cases like this.

[0041] This section describes entities in the AS layer of E-UTRA and / or NR. An entity that has some or all of the functions of the MAC layer may be called a MAC entity. An entity that has some or all of the functions of the RLC layer may be called an RLC entity. An entity that has 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 referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.

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

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

[0044] Hereinafter, "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 the base station device, and the received A is transmitted from the higher layer of the terminal device to a lower layer (mainly a MAC layer or a physical layer) of the terminal device. For example, in a terminal device, "Upper layer parameters are provided" may mean that an upper layer signal is received from a base station device, and the upper layer parameters included in the received upper layer signal are provided from the upper layer of the terminal device to the lower layer of the terminal device. "Upper layer parameters are set in a terminal device" may mean that upper layer parameters are given (provided) to the terminal device. For example, "upper layer parameters are set in a terminal device" may mean that the terminal device receives an upper layer signal from a base station device, and the received upper layer parameters are set in the upper layer. However, "upper layer parameters are set in a terminal device" may also include setting default parameters that are given in advance to the upper layer of the terminal device. When describing transmission of an RRC message from a terminal device to a base station device, Then, a message is sent from the RRC entity of the terminal device to the lower layer. In the terminal device, the RRC entity In the terminal device, "submitting a message to a lower layer" from the RRC layer may mean submitting a message to the PDCP layer. This is because RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.). This means submitting the message to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from a lower layer, The layer may refer to one or more of a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and the like.

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

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

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

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

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

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

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

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

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

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

[0055] An example of the MAC function will be described below. MAC may also be called a MAC sublayer. MAC maps various logical channels to corresponding transport channels. A logical channel may have a function to map it to a logical channel identifier. The MAC may be identified by a logical channel identity (Channel Identity, or Logical Channel ID). The MAC may be connected to the higher RLC via a logical channel. Depending on the type of information to be transmitted, the logical channel may be divided into a control channel that transmits control information and a traffic channel that transmits user information. The logical channel may also be divided into an uplink logical channel and a downlink logical channel. The MAC may have a function to multiplex MAC SDUs belonging to one or more different logical channels and provide them to the PHY. The MAC may also have a function to multiplex MAC SDUs provided by the PHY. The MAC may have a function to demultiplex the MAC PDUs and provide them to a higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a scheduling report function to report scheduling information. MAC should have the function of using dynamic scheduling to prioritize between terminal devices. In addition, MAC may have a function to perform priority processing between logical channels within one terminal device. MAC has the function of prioritizing overlapping resources within a single terminal device. The MAC may have the ability to identify Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have the ability to identify Multicast / Broadcast Services (MBS). The MAC selects the transport format. The MAC may have the functionality to support discontinuous reception (DRX) and / or It has a function to perform discontinuous transmission (DTX), a function to execute random access (RA) procedures, a power headroom report (PHR) function to notify information on the available transmission power, and a buffer function to notify information on the amount of data in the transmission buffer. The NR MAC may have a Buffer Status Report (BSR) function, etc. The NR MAC may have a Bandwidth Adaptation (BA) function. The MAC PDU format used in the E-UTRA MAC and the MAC PDU format used in the NR MAC may be different. may include a MAC control element (MAC CE), which is an element for performing control in the MAC.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] An example of the functions of the RRC will be described. The RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and / or the 5GC 110. The RRC may have a paging function from the eNB 102 connected to the gNB 108 or 5GC 110. The RRC may also have an RRC connection management function. The RRC may also have a The RRC may have a radio bearer control function. The RRC may also have a cell group control function. The RRC may also have a mobility control function. The RRC may also have a terminal device measurement reporting and terminal device measurement reporting control function. The RRC may also have a QoS management function. The RRC may also have the function of detecting and recovering from radio link failures. The RRC may use RRC messages to perform broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. Note that the RRC messages and parameters used in E-UTRA RRC are the same as the RRC messages and parameters used in NR RRC. parameter.

[0080] RRC messages may be sent using the logical channel BCCH. Alternatively, RRC messages may be sent using the logical channel PCCH. Alternatively or additionally, RRC messages may be sent using the logical channel CCCH. Additionally or alternatively, RRC messages may be sent using the logical channel DCCH. Additionally or alternatively, the RRC message may include the MCCH of the logical channel. RRC messages sent using the DCCH are also referred to as dedicated RRC signaling or RRC signaling.

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

[0082] RRC messages sent in the uplink (UL) direction using CCCH include, for example, an RRC Setup Request message, an RRC Resume Request message, an RRC Reestablishment Request message, and an RRC System Information Request message. The RRC message may include an RRC System Info Request message, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. Alternatively, the RRC message may include other RRC messages.

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

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

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

[0086] The RRC message sent in the downlink (DL) direction using the MCCH may include, for example, an MBS broadcast configuration message (MBSBroadcastConfiguration message). , and other RRC signaling may be included.

[0087] An example of the NAS function is explained below. The NAS may have an authentication function. The NAS may also have the functionality to perform security control. You can have it.

[0088] The above-mentioned PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS functions are examples, and only a portion of each function is shown. In addition, some or all of the functions of each layer may be included in other layers.

[0089] Next, the state transition of the UE 122 in LTE and NR will be described. When the UE 122 connected to the EPC or 5GC has an RRC connection established, the UE 122 may be in the RRC_CONNECTED state. The state in which the RRC connection is established means that the UE 122 is in the RRC_CONNECTED state after This may include a state in which the UE holds some or all of the above-mentioned UE contexts. The established state may include a state in which the UE 122 can transmit and / or receive unicast data. Furthermore, the UE 122 may be in the RRC_INACTIVE state when the RRC connection is suspended. Furthermore, the UE 122 may be in the RRC_INACTIVE state when the UE 122 is connected to 5GC and the RRC connection is suspended. When the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state, the UE 122 may be in the RRC_IDLE state.

[0090] Note that when the UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but is connected to the E-UTRAN. If the UE 122 is connected to the EPC, when the RRC connection is suspended, the UE 122 may transition to the RRC_IDLE state, retaining the UE AS context and an identifier (resumeIdentity) used for resuming. An upper layer (e.g., NAS layer) of the RRC layer of the UE 122 may initiate the suspension of the suspended RRC connection when the UE 122 retains the UE AS context, the E-UTRAN has permitted the RRC connection to be resumed, and the UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. Recovery may be initiated.

[0091] The definition of dormancy may be different for the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110. In addition, when the UE 122 is connected to the EPC (when the UE 122 is dormant in the RRC_IDLE state), and when the UE 122 is connected to the 5GC (when the UE 122 is dormant in the RRC_INACTIVE state), However, some or all of the procedures for waking up from hibernation may be different.

[0092] The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state are connected, respectively. These may be referred to as connected mode, inactive mode, or idle mode, or may be referred to as RRC connected mode, RRC inactive mode, or RRC idle mode.

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

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

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

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

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

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

[0099] Furthermore, when DC is not configured, the cell group configured in the terminal device may be called an MCG. Furthermore, when DC is not configured, the SpCell configured in the terminal device may be a PCell. Furthermore, an NR in which DC is not configured may be called an NR standalone (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. MR-DC is also a technology that performs DC using NR for MCG and E-UTRA for SCG. MR-DC is a technique for performing DC using NR on both MCG and SCG. MR-DC may be a technology included in DC. An example of MR-DC using E-UTRA for MCG and NR for SCG is EN-DC (E-UTRA-NR Dual Connectivity) which uses EPC for the core network. An example of MR-DC using NR for MCG and E-UTRA for SCG is NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity), which uses 5GC for the core network. An example of MR-DC using NR for MCG and E-UTRA for SCG is NE-DC (NR-E-UTRA Dual Connectivity), which uses 5GC for the core network. An example of MR-DC using NR for both MCG and SCG is NE-DC (NR-E-UTRA Dual Connectivity). Therefore, it would be good to have NR-DC (NR-NR Dual Connectivity) that uses 5GC in the core network.

[0101] In the terminal device, one MAC entity may exist for each cell group. For example, when DC or MR-DC is set in the terminal device, one MAC address for MCG is There may be one MAC entity for the MCG and one MAC entity for the SCG in the terminal device. The MAC entity for the MCG in the terminal device may be always established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). The MAC entity for the SCG is CLEARED by the terminal device when the SCG is configured in the terminal device. A MAC entity for each cell group of the terminal device may be created. The terminal device receives RRC signaling from the base station device to perform the setting. If the MAC entity is associated with an MCG, the SpCell may refer to the PCell. Also, if the MAC entity is associated with an SCG, SpCell may refer to a Primary SCG Cell (PSCell). If not specified, SpCell may mean PCell. PCell, PSCell and SCell are In EN-DC and NGEN-DC, the MAC entity for MCG is E-UTRA In the NE-DC, the MAC entity for the SCG may be an NR MAC entity, and the MAC entity for the MCG may be an NR MAC entity. The MAC entity for the SCG may be an E-UTRA MAC entity. In NR-DC, the MAC entities for the MCG and SCG may both be NR MAC entities. The existence of one MAC entity for each cell group may be rephrased as the existence of one MAC entity for each SpCell. In addition, one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.

[0102] Explains the RRC signaling flow transmitted and received between the terminal device and the base station device FIG. 4 is a flow chart of procedures for various settings in the RRC according to this embodiment. 4 is a diagram illustrating an example of a flow when RRC signaling is sent from a base station device (eNB 102 and / or gNB 108) to a terminal device (UE 122).

[0103] In FIG. 4, the base station device creates an RRC message (step S400). The base station device may create an RRC message in order to deliver system information (SI) or a paging message. The message is created by the base station device sending RRC signaling to a specific terminal device to perform processing. The processing to be performed on a specific terminal device may be, for example, security-related settings, re-establishment of an RRC connection, handover to a different RAT, or RRC connection reset. The RRC connection re-establishment process may include processes such as radio bearer control (establishment, modification, release, etc.), cell group control (establishment, modification, release, etc.), etc. ,addition, modification, release, etc.), measurement configuration, handover, security key update, etc. The base station device may generate an RRC message based on the received RRC message transmitted from the terminal device. The RRC message may be performed in response to the RRC signaling transmitted from the terminal device. Responses to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or field values ​​(including information elements). RRC Message The structure of the data is described using a notation method called ASN.1 (Abstract Syntax Notation One). stomach.

[0104] In FIG. 4, the base station device then transmits the created RRC signaling to the terminal device (step (Step S402). Next, the terminal device performs processing such as setting according to the received RRC signaling if necessary (step S404). After performing the processing, the terminal device may transmit RRC signaling in response to the base station device (not shown).

[0105] RRC signaling may be used for other purposes, not limited to the above examples.

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

[0107] It should be noted that the RRC signal for E-UTRA transmitted from the eNB 102 to the UE 122 is not limited to the case where MR-DC is used. The RRC signaling for NR may be included in the RRC signaling transmitted from the gNB 108 to the UE 122, and the RRC signaling for NR may include the RRC signaling for E-UTRA.

[0108] This section explains MBS (Multicast / Broadcast Services).

[0109] In a broadcast service, the same service and the same specific content data may be provided simultaneously to all terminal devices (UEs 122) within a geographical area. Services may be delivered to terminal devices using broadcast sessions. Terminal devices broadcast in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. You should be able to receive the service.

[0110] In a multicast service, the same service and the same specific content data may be provided simultaneously to one or more specific terminal devices (also referred to as a UE set). The multicast service may be distributed to the terminal devices using a multicast session. The terminal devices can receive the multicast service using mechanisms such as Point to Point (PTP) distribution and / or Point to Multipoint (PTM) distribution. HARQ feedback / retransmission is applicable to both PTP and PTM transmissions.

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

[0112] An example of how RNTIs are used in PTM transmission is shown below. The terminal can receive different services using the same or different G-CS-RNTI. can be used to receive different services.

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

[0114] If both PTM and PTP transmissions are configured in the terminal device, the gNB Based on information such as requirements, number of participating terminals, and reception quality feedback of individual terminals, multicast data can be sent to specific terminals on either the PTM leg and / or the PTP leg. The PTM and PTP transmissions may dynamically determine whether to deliver the PTM data or not, and regardless of the determination, 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) 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 broadcast services transmitted on the MTCH and / or information related to the broadcast session. The information related to the MBS session includes the MBS session ID, the associated G-RNTI scheduler, The MCCH content may include information about the MCCH repetition period, MCCH window period, and radio frame / slot number. The time domain time 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 changes in MCCH content due to broadcast session start, change, or stop, and changes in neighbor cell information. Upon receiving the MCCH change notification, the terminal device may acquire the updated MCCH in the same MCCH change period in which the change notification was sent.

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

[0118] The mobility procedures for MBS reception allow a terminal device to start or continue receiving MBS services when changing cells. The gNB transmits the MBS blocks provided by the serving cell on the MCCH. List of neighboring cells that provide the same MBS broadcast service as the broadcast service This allows the terminal device to request unicast reception of the service before moving to a cell that does not provide MBS broadcast services using PTM transmission. This eliminates the need to read MBS broadcast-related system information on adjacent frequencies. The terminal device can know on which frequency the MBS broadcast service via PTM is provided via the User Service Description (USD) or the following combination: can be done. USD System Information (System Information Block: SIB, e.g. SIB21)

[0119] The USD may include information indicating the correspondence between the MBS service and the frequency. For example, the USD includes at least one set of an MBS service identifier that identifies the MBS service and information about the frequency. Additionally or alternatively, for example, the USD may include an MBS session identifier for identifying an MBS session, information on the start and end times of the MBS session, The MBS session information may include at least one of an identifier indicating an MBS service area in which the MBS session is provided, and information on a frequency in which the MBS session is provided.

[0120] In the RRC_IDLE and RRC_INACTIVE states, the terminal device may apply the following modifications to the normal cell reselection rules: Terminal devices receiving or interested in receiving MBS broadcast services via PTM must camp on the frequencies that provide these MBS broadcast services. You can receive these MBS broadcast services while you are using the service and certain conditions are met. If so, this frequency can be made the highest priority frequency. The MBS broadcast service that the terminal device is interested in is no longer available. The terminal device may stop providing these MBS broadcast services when the terminal device is no longer interested in receiving the service (e.g., after the session has ended) or when the terminal device is no longer interested in receiving the service. There is no need to give higher priority to frequencies that are

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

[0122] In order to ensure the continuity of the MBS broadcast service, a terminal device in the RRC_CONNECTED state sends an MBS Interest Indication (MII) consisting of the following information to the gNB: It can be trusted. A list of MBS frequencies that the device is listening to or interested in listening to, sorted by importance The MBS frequency that the terminal device is receiving or interested in receiving, Priority of receiving multicast bearers and multicast MRBs If an SIB (e.g., SIB20) containing information necessary to obtain the configuration of an MCCH and / or MTCH for MBS broadcast is provided on the PCell or SCell, a list of MBS broadcast services that the terminal device is receiving or is interested in receiving.

[0123] Current carrier frequency and / or adjacent carrier frequencies and MBS Frequency Selection Whether or not there is a SIB (e.g., SIB21) that contains mapping information with the FSAI The reporting of the MBS Interest indication may be implicitly enabled / disabled based on whether the MBS Interest indication is enabled or disabled. The information contained in the MBS Interest indication may also be exchanged between the source gNB and the target gNB during handover.

[0124] For broadcast services, gNBs broadcast using the following methods: The 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, a gNB may transmit a group-common PDCCH CRC-scrambled with a group-common RNTI. This is used to schedule a group-common PDSCH scrambled with the same group-common RNTI. You can take a few minutes.

[0125] We will explain MBS Broadcast in detail.

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

[0127] MCCH is used to identify MBS broadcast sessions provided by the cell and the It may be used to deliver an MBS Broadcast Configuration message indicating the relevant scheduling information. Optionally, the MBS Broadcast Configuration message may contain information about the MBS Broadcast services offered in the current cell. A list of neighboring cells that provide the same service as the MBS broadcast service may be included. Configuration information required for the terminal device to receive the MCCH may be provided in SIB1 and SIB20. Furthermore, information regarding service continuity of the MBS broadcast may be provided in SIB21.

[0128] MCCH information (i.e., information transmitted in messages transmitted on the MCCH) may be transmitted periodically within a configured transmission window with a configurable recurrence period. MCCH transmissions (and associated radio resources and MCS) are routed by the PDCCH addressed to the MCCH-RNTI. It may be shown as follows.

[0129] The PDCCH monitoring occasion for MCCH transmission is determined by searchspaceMCCH. The search space may be determined according to the common search space indicated in If searchspaceMCCH is set to non-zero, the PDCCH monitoring opportunities for MCCH message reception in the MCCH transmission window may be the same as the PDCCH monitoring opportunities in SIB1. In this case, the PDCCH monitoring opportunity for the MCCH message may be determined based on the search space indicated by searchspaceMCCH.

[0130] The modification of the MCCH information occurs only in a specific radio frame, and the concept of a modification period may be used. Within a modification period, the same MCCH information may be used in different radio frames depending on its scheduling. If the network changes some or all of the MCCH information, the network uses the PDCCH that schedules the MCCH to transmit the MCCH change period. The terminal device that receives the notification of the change may be notified of the change from the start of the MBS broadcast. The terminal device that receives the notification of the change may be receiving or will be able to receive the MBS service transmitted using the MBS broadcast. If the terminal device is interested in the MCCH information, it may acquire new MCCH information from the same slot in which it received the notification of the change. The terminal device may apply the previously acquired MCCH information until it acquires the new MCCH information.

[0131] The terminal device receives the MBS broadcast setting information broadcast by the network. To acquire the MCCH information, the MCCH information acquisition procedure may be applied. The MCCH information acquisition procedure is performed in RRC_IDLE state, RRC_INACTIVE state, or in the common search space configured by searchSpaceMCCH. This may apply to MBS broadcast services that an MBS-capable terminal device in RRC_CONNECTED state, where a BWP is the active BWP, is receiving or is interested in receiving. stomach.

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

[0133] Devices receiving or interested in receiving MBS broadcast services If the MCCH information acquisition procedure is triggered based on notification that there has been a change in the MCCH information, the device may start acquiring an MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which it has been notified that there has been a change in the MCCH information. If the information contained in is received by RRC signaling, the MCCH is used from the next recurrence period. You may start receiving MBSBroadcastConfiguration messages as they are sent.

[0134] The Broadcast MRB Configuration procedure is used by the terminal device to configure PDCP, RLC, MAC, and PHY when the terminal device starts and / or stops receiving broadcast MRBs transmitted on the MTCH, or when the configuration of a broadcast MRB received by the terminal device is changed. The Broadcast MRB configuration procedure can be performed in the RRC_IDLE state, the RRC_INACTIVE state, or or an MBS broadcast service that an MBS-capable terminal device in RRC_CONNECTED state, where a BWP with a common search space configured by searchSpaceMTCH or searchSpaceMCCH is the active BWP, is receiving or is interested in receiving. .

[0135] The terminal device may apply (start) the broadcast MRB configuration procedure to start receiving the MBS session of the MBS broadcast service in which it is interested. The MBS broadcast broadcast request (MBS) setup procedure is a procedure in which an MBS-capable terminal device that is interested in receiving an MBS broadcast service selects a server that provides the MBS broadcast service at the start of an MBS session. When you enter the internet, when you become interested in the ongoing MBS broadcast service, The capacity limit has been lifted and reception of ongoing MBS broadcast services will not be hindered. It may be started when

[0136] The terminal device must stop receiving the MBS broadcast service session. The broadcast MRB release procedure may be applied (started). The broadcast MRB release procedure is used when an MBS session is terminated, when the terminal device leaves the cell broadcasting the MBS service in which it is interested, when it loses interest in the MBS service, or when it terminates reception of the related service. It may be initiated when a capability restriction that prevents communication is initiated.

[0137] As a broadcast MRB configuration procedure, the terminal device may perform the following operations:

[0138] The terminal device may establish a PDCP entity, an RLC entity, and / or an SDAP entity according to the information about this broadcast MRB included in the MBSBroadcastConfiguration message. The terminal device may also configure the MAC layer based on the scheduling information of the MTCH (mtch-SchedulingInfo). The terminal device may also configure the MAC layer based on the information about this broadcast MRB. The terminal device may configure the PHY layer based on the applied configuration. The terminal device may also receive the DL-SCH in the same cell as the cell in which it received the MBSBroadcastConfiguration message for broadcast MRB establishment using the G-RNTI and / or mtch-SchedulingInfo for this MBS broadcast service.

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

[0140] The terminal device configures the PDCP entity, the RLC entity, and the associated MAC and PHY settings. The terminal may release the setting. Also, the terminal may release the setting of the SDAP entity that no longer has an associated MRB. You may release the tee.

[0141] The above-mentioned MBS broadcast configuration message (MBSBroadcastConfiguration message) may include information indicating one or more MBS broadcast sessions (MBS session information list). The configuration message contains a list of neighboring cells that provide the same broadcast MBS service. Each entry in the MBS Session Information List may include MBS Broadcast Session Identifier Information (TMGI). The TMGI may include a Public Land Mobile Network (PLMN) identifier or an index value associated with the PLMN identifier. Additionally or alternatively, the TMGI may include a unique identifier for identifying the MBS service within the PLMN. Additionally or alternatively, the MBS session ID may include an identifier for the MBS session (Service ID). The session information list contains one or more entries, and the MBS session information list The entry may include a G-RNTI used for scheduling the MTCH and for scrambling transmissions. Additionally or alternatively, an entry in the MBS session information list may include broadcast MRB settings (e.g., PDCP settings and RLC settings).

[0142] We will explain MBS interest indication.

[0143] The terminal may perform the MBS interest indication procedure. The UE notifies the network that the UE in RRC_CONNECTED state is receiving or is interested in receiving the MBS broadcast service. In addition, this procedure may be used to indicate to the network whether a terminal device in RRC_CONNECTED state prefers MBS broadcast reception or unicast / multicast MRB reception. Additionally or alternatively, this procedure may be used for other purposes.

[0144] (MBS interest indication procedure)

[0145] An MBS capable UE in RRC_CONNECTED state may initiate an MBS interest indication procedure in several cases, including RRC connection establishment / resumption. When the MBS broadcast session is started or stopped, when the MBS broadcast service area is entered or left, or when the MBS broadcast service area is opened or closed, The events may include when there is a change in interest in the service, when there is a change in priority between MBS broadcast reception and unicast / multicast reception, when the serving cell is changed to a PCell that provides SIB21 (i.e., when SIB21 is included in the scheduling information of SIB1), when SIB20 of an SCell is received via dedicated signaling, when handover occurs, and when an RRC connection is re-established. In addition, when there is a change in the serving cell to a PCell that provides a parameter (nonServingCellMII) in SIB1 indicating that an MBS interest indication for receiving an MBS broadcast service on a non-serving cell may be sent to the serving cell, when an MBS broadcast interest indication for receiving an MBS broadcast service on a non-serving cell is sent to the serving cell, and when an MBS broadcast interest indication for receiving an MBS broadcast service on a non-serving cell is sent to the serving cell. When starting or stopping reception of a remote service, the MBS broadcast in the non-serving cell When the received CFR (common frequency resources) information or subcarrier spacing is changed If the UE does not have CFR information and subcarrier spacing for MBS broadcast reception in a non-serving cell, the UE shall obtain these before transmitting the MBS Interest Indication. The information may be obtained from a non-serving cell.

[0146] The terminal device that initiated this procedure shall, if SIB21 is provided by the PCell, If the UE has a PCell with nonServingCellMII enabled, or if the PCell provides nonServingCellMII in SIB1, it may perform some or all of the following (a) to (b): (a) Verify that a valid version of SIB21 for the PCell is obtained. (b) If the UE has sent an MBS Interest Indication since it last entered RRC_CONNECTED state If the UE has not, or if, since the last time it sent an MBS Interest Indication, it has been connected to a PCell that does not provide SIB21 or does not include nonServingCellMII in SIB1. , the content of the MBSInterestIndication message may be set according to the MBS interest indication content preparation procedure based on the set of MBS broadcast frequencies determined according to the procedure for determining MBS frequencies of interest being not empty, and the transmission of the MBSInterestIndication message may be started.

[0147] Additionally or alternatively, if SIB21 is not provided by the PCell and nonServingCellMII is not provided in SIB1 by the PCell, the terminal device that initiated this procedure may perform the following process (pa) based on whether some or all of the following conditions (ca) to (ce) are satisfied: Based on this, the following treatment (pb) may be carried out. (ca) The set of MBS broadcast frequencies of interest, as determined in accordance with the MBS frequency of interest determination procedure, is included in the last transmission of the previous MBS interest indication. This is different from the mbs-FreqList included in the mbs-FreqList. (cb) Non-serving MBS frequencies determined according to the determination procedure for MBS frequencies of interest. The set of MBS broadcast frequencies of interest for MBS broadcast reception in the cell is different from that included in the previous MBS interest indication. (cc) Either the subcarrier spacing or CFR information for MBS broadcast reception in a non-serving cell has changed since the last transmission of an MBS interest indication. (cd) Subcarrier spacing and CFR information for MBS broadcast reception in non-serving cells is updated from non-serving cells that were not reported in the previous MBS interest indication. It was obtained from (ce) The priority of receiving MBS broadcast frequencies compared to receiving established unicast bearers and multicast MRBs is increased by 100% since the last transmission of an MBS interest indication. was changed later. (pa) Set the content of the MBS Interest Indication according to the MBS interest indication content preparation procedure and start sending the MBSInterestIndication message. (pb) SIB20 is provided on a PCell or SCell, and (1) since the UE last transmitted an MBS Interest Indication, the UE has been connected to a PCell that does not provide SIB20 and the UE has not been provided with SIB20 for an SCell, or (2) the determination procedure for an MBS service of interest. the set of MBS broadcast services determined in accordance with The content of the MBSInterestIndication message is set according to the MBS interest indication content preparation procedure, and transmission of the MBSInterestIndication message is started.

[0148] (MBS frequencies of interest determination procedure)

[0149] The terminal device may determine (judge) a frequency to be part of the MBS frequency of interest based on the fact that all of the following conditions (ca) to (cc) are satisfied for that frequency: (ca) The terminal device is receiving or will receive via a broadcast MRB. At least one MBS session of interest has started or is about to start. is doing. (cb) The terminal device is receiving or will receive via a broadcast MRB. For at least one MBS session that is interested in The SIB21 obtained from contains information on the mapping between the frequency and one or more MBS FSAIs indicated in the USD of this MBS session, or the frequency is not included in SIB21 but Shown in session USD. (cc) The information on the band combinations supported by the terminal device (e.g., supportedBandCombinationList) included in the capability information of the terminal device (e.g., UE-NR-Capability) notified to the network by the terminal device includes at least one band combination including the frequency. do.

[0150] (MBS services of interest determination procedure) (Ja)

[0151] The terminal device determines its MBS based on whether all of the following conditions (ca) to (cc) are met. The service may be determined to be part of an MBS service of interest. (ca) The terminal device is receiving or is interested in receiving the MBS service via a broadcast MRB. (cb) A session for that MBS service is starting or about to start. do. (cc) One or more of the USD (User Service Description) for the MBS service The MBS FSAI (Frequency Specific Application Identifier) ​​of the MBS is the MBS frequency of interest determined by the MBS frequency of interest determination procedure of SIB21 obtained from the PCell. or the SIB21 obtained from the PCell does not provide frequency mapping information for the MBS service, but the USD of the MBS service contains frequencies belonging to the set of MBS frequencies of interest determined by the MBS frequencies of interest determination procedure.

[0152] (Procedure for setting the contents of MBS interest indication)

[0153] The terminal device may provide content for the MBS interest indication.

[0154] The terminal device may perform some or all of the following processes (pa) to (pd) based on (1) having a valid version of SIB21 and (2) the set of MBS frequencies of interest determined by the procedure for determining MBS frequencies of interest is not empty. (pa) You may set a list (mbs-FreqList) of MBS frequencies of interest sorted in descending order to be included in the MBS interest indication. (pb) The terminal device receives MBS broadcast rather than any unicast / multicast MRB. Based on the priority of receiving MBS broadcasts over receiving any unicast or multicast MRBs, the terminal device may include a parameter mbs-Priority in the MBS interest indication. By sending the mbs-Priority in the MBS interest indication, the terminal device may inform the network that the terminal device prioritizes receiving MBS broadcasts over receiving any unicast or multicast MRBs. (pc) Based on the provision of SIB20 for PCell or SCell, the MBS services of interest sorted in descending order may be set in a list (mbs-ServiceList) to be included in the MBS interest indication. (pd) SIB1 for the PCell includes nonServingCellMII and MBS broadcast reception in a non-serving cell determined by the procedure for determining the MBS frequency of interest. Based on the fact that the set of MBS frequencies for reception is not empty, (1) the content of the MBS interest indication includes freqInfoMBS, and (2) if the terminal device is not serving, If you have acquired a cfr-InfoMBS and subcarrierSpacing to receive a broadcast, include that cfr-InfoMBS and subcarrierSpacing in the content of your MBS interest indication. That's fine.

[0155] The RRC connection release procedure will now be described.

[0156] The RRC connection release procedure may be used for the following purposes (oa) to (ob): Additionally or alternatively, the RRC connection release procedure may be used for other purposes. It's okay to stay there. (oa) Established radio bearers (excluding broadcast MRBs), backhaul RLC channels, Uu relay RLC channels, PC5 relay RLC channels, and / or radio resources To release the RRC connection, including releasing the (ob) Suspension of established radio bearers (except broadcast MRBs) To suspend the RRC connection, including

[0157] The network shall only allow the terminal device to transition from RRC_CONNECTED state to RRC_IDLE state, or, in the case of IAB and NCR, if SRB2 is configured in RRC_CONNECTED state, if SRB2 and at least one DRB or multicast MRB are configured in RRC_CONNECTED state. To initiate the transition of the terminal from RRC_CONNECTED state to RRC_INACTIVE state only if In this case, the network may initiate an RRC connection release procedure. This procedure may also be initiated when the terminal device attempts to resume the RRC connection (due to resumption of a suspended RRC connection or the start of an SDT) in order for the network to transition the terminal device from the RRC_INACTIVE state to the RRC_INACTIVE state or to the RRC_IDLE state. Additionally or alternatively, this procedure may be used by the network to release the terminal device and redirect it to another frequency. Additionally or alternatively, this procedure may be used for other purposes.

[0158] A terminal device that receives an RRC connection release message may perform some or all of the following processes (pa) to (pf) based on the fact that suspendConfig is included in this message. (pa) Release MAC (pb) Release the default MAC cell group settings (pc) Apply all or part of the received suspendConfig (pd) Quiesce all SRBs and DRBs (except SRB0 and broadcast MRBs) (pe) Quiesce all multicast MRBs associated with multicast sessions that are not configured to receive in the RRC_INACTIVE state. (pf) Enter RRC_INACTIVE state

[0159] The reception of the MBS multicast service by a terminal device in the RRC_INACTIVE state will be described.

[0160] Terminal equipment configured to receive MBS multicast services in the RRC_INACTIVE state The MBS multicast procedure may be applied. The MBS multicast configuration information may be provided in the RRCRelease message and / or the multicast MCCH logical channel. If there is temporarily no data in an active multicast session or if the multicast session is deactivated, the network may notify the terminal device through the MBS multicast configuration information to stop monitoring the corresponding G-RNTI. When the terminal device is notified to stop monitoring the G-RNTIs of all multicast sessions in which it is participating, the terminal device may You may stop monitoring.

[0161] The multicast MCCH is used to connect the MBS multicast sessions provided in the cell and these An MBSMulticastConfiguration message indicating scheduling information related to this session. In addition, the MBSMulticastConfiguration message may carry the same MBS multicast services as those offered in the current cell for the terminal device in RRC_INACTIVE state. The broadcast information (for example, SIB24) may also include a list of neighboring cells that provide services. Configuration information required for a terminal device to receive the multicast MCCH may be provided in the broadcast information.

[0162] The multicast MCCH information acquisition procedure will now be described.

[0163] The terminal device receives the MBS multicast configuration information from the network. In this case, a multicast MCCH information acquisition procedure may be applied to a terminal device configured to receive the MBS multicast service in the RRC_INACTIVE state.

[0164] When configured to receive MBS multicast services in the RRC_INACTIVE state The terminal device may apply the multicast MCCH information acquisition procedure for updating the PTM configuration and / or when reselecting to a new cell that provides SIB 24. In addition, the terminal device receiving MBS multicast data in the RRC_INACTIVE state may apply the multicast MCCH information acquisition procedure for updating the PTM configuration and / or when reselecting to a new cell that provides SIB 24. If the change is notified by the network, the multicast MCCH information acquisition procedure may be applied.

[0165] In the multicast MCCH information acquisition procedure, a terminal device configured to receive the MBS multicast service in the RRC_INACTIVE state may receive some or all of the following (pa) to (pb): may perform all the processing. (pa) If this procedure is triggered by a notification from the network that the multicast MCCH information has changed, the MBSMulticastConfiguration carried on the multicast MCCH in the relevant cell from the slot in which this change notification was received. Start getting messages (pb) If the terminal equipment moves to another cell that provides SIB24, or if the terminal The device receives the RRCRelease message and the terminal device is in the RRC_INACTIVE state and is using MBS multicast. If the RRC release message does not include a PTM configuration for at least one multicast session for which the terminal device has not indicated that it will stop monitoring the G-RNTI, then in the next recurrence period, the terminal device shall Obtain the MBSMulticastConfiguration message carried on the Multicast MCCH.

[0166] The terminal device receives the MBSMulticastConfiguration message obtained by the above process. settings may be applied.

[0167] The RRC connection resumption procedure will now be described.

[0168] The purpose of the RRC connection resumption procedure may be to resume a suspended RRC connection, including resuming SRBs, DRBs, and multicast MRBs. Additionally or alternatively, the purpose of the RRC connection resumption procedure may be to perform an RNA update. Alternatively, the purpose of the RRC connection resumption procedure may be some other purpose.

[0169] If the terminal is configured to receive MBS multicast in the RRC_INACTIVE state, In this case, in the RRC_INACTIVE state, the terminal device may send an RRCResumeRequest message and / or an RRCResumeRequest1 message to resume the RRC connection based on any one or any combination of the following conditions (ca) to (cd) being met. (ca) SIB24 is not scheduled by SIB1 (cb) In a cell after cell selection or reselection, the PTM configuration for a multicast session that does not indicate that the terminal device stops monitoring the G-RNTI in which it participates is used. I can't (cc) The terminal equipment monitors the G-RNTI according to the mbs-NeighborCellList acquired in the previous cell. Multicast sessions that have not indicated they will stop monitoring will be terminated if they are not currently serving The processing cell is not provided for a terminal device in RRC_INACTIVE state. (cd) The measured RSRP and / or RSRQ of the serving cell is less than or equal to the thresholdIndex. Below the threshold

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

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

[0172] The UE 122 shown in FIG. 5 includes a receiver 500 that receives control information (DCI, MAC control elements, RRC signaling, broadcast information, etc.) from a base station device, a processor 502 that processes the control information according to parameters included in the received control information, and a processor 503 that transmits the control information (UCI, MAC control elements, RRC signaling, broadcast information, etc.) to the base station device. The base station device may be the eNB 102 or the gNB 108. The processing unit 502 may include some or all of the functions of various layers (for example, a physical layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer, an RRC layer, and an NAS layer). That is, The processing unit 502 includes a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), an RLC layer processing unit (RLC processing section), PDCP layer processing section (PDCP processing section), SDAP processing section (SDAP processing section), RRC layer processing section (RRC processing section), and NAS layer processing section (NAS processing section).

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

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

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

[0176] 7 is a diagram showing an example of processing by the terminal device (UE 122) in this embodiment. The processing unit 502 of the terminal device receives control information for the MBS session from the base station device (step S700). The processing unit 502 of the terminal device determines whether the terminal device is to be placed in any of the areas based on the received control information. The processing unit 502 of the terminal device performs the operation based on the above-mentioned determination (step S702). Then, the operation is performed (step S704).

[0177] The first 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) Messages transmitted using MCCH (b) System Information Block (e.g., SIB20) (c) RRC signaling transmitted using DCCH (d) USD

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

[0179] 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) Reference Location (geographical coordinates indicated by longitude and latitude) and additional information ( The area described by the radius, diameter, and / or angle is treated as one entry. and a list containing one or more entries (b) An area formed by connecting multiple reference points is treated as one entry. A list containing at least one entry (c) SSB index (d) Other information indicating a geographic area

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

[0181] In addition, when an area is indicated by an SSB index, if the terminal device can receive the indicated SSB, the terminal device is considered to be located in the area indicated by the SSB index. Furthermore, 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. This threshold may be notified in the first information, may be notified in the second information, or may be a predetermined value.

[0182] One or more areas notified by the second information are associated with an MBS session. It is okay to do so.

[0183] For example, zero or more regions may be associated with each entry of the MBS session information list included in the MBS broadcast configuration message. In this case, for example, each entry of the MBS session information list may be associated with a list having zero or more region identifiers in the entry. Additionally or alternatively, the MBS session information list may include The TMGI included in each entry may be associated with zero or more areas. Additionally or alternatively, a G-RNTI included in each entry of the MBS session information list may be associated with zero or more fields. Additionally or alternatively, a PLMN included in each entry of the MBS session information list may be associated with zero or more fields. Additionally or alternatively, a G-RNTI included in each entry of the MBS session information list may be associated with zero or more fields. The service ID included in each entry may be associated with zero or more regions. Fig. 9 is a diagram showing an example in which a region identifier is included in an MBS broadcast configuration message. The MBS broadcast configuration message (MBSBroadcastConfiguration) includes an MBS session information list (MBS-SessionInfoList), and each entry in the MBS session information list includes a TMGI and a G-RNTI, and optionally has one or more region identifiers in the entry. The MbsAreaList contains the list of MBS session information. The absence of a region in an entry indicates that the entry is associated with zero regions. It is okay to do so.

[0184] For example, SIB20 may contain setting information required to receive one or more MCCHs. Each piece of setting information required to receive the MCCH is associated with zero or more areas. In this case, the MBS broadcast to be received based on the setting information required to receive a certain MCCH may be All MBS sessions notified in the broadcast setup message receive this MCCH. There may be zero or more fields associated with the setting information required to perform the above steps. 1 is a diagram showing an example in which a region identifier is included in SIB 20. SIB 20 includes a list (McchConfigList) of setting information required to receive one or more MCCHs, and each entry in McchConfigList includes setting information (MCCH-Config) required to receive an MCCH. A list (MbsAreaList) having one or more area identifiers as entries is included as an area configuration. In other words, if MbsAreaList is not included in McChConfig, it may be indicated that the McChConfig is associated with zero areas.

[0185] In addition, one or more MBS sessions are stored in each of the areas notified by the second information. The corresponding options may be associated.

[0186] Furthermore, each of the areas notified by the second information may be associated with one or more FSAIs.

[0187] Also, each of the areas notified by the second information and one or more MBS services (for example, an MBS service identifier notified in USD) may be associated with the MBS service identifier.

[0188] Furthermore, there may be MBS sessions and / or MBS services that are not associated with any area (ie, associated with zero areas). Start receiving MCCH messages

[0189] The determination in step S702 is, for example, whether or not the MBS multicast service is being received. The terminal device set to the second information is Determining which MBS service is receiving or attempting to receive a multicast session In addition, or alternatively, the determination in step S702 may be, for example, determining whether the terminal device has entered the area at the start of or during the process of the determination procedure. In the procedure for determining the service, the terminal equipment is installed in the area associated with a certain MBS service. In this case, in step S704, the terminal device determines whether the MBS service associated with the MBS service it is currently receiving is located based on the determination. The method may determine whether the first information has entered the area defined by the first information acquisition procedure, and based on the determination, may instruct the receiving unit to receive the first information, for example the instruction may be to start a multicast MCCH information acquisition procedure.

[0190] (One method for determining area movement) Whether the device has entered the area associated with the MBS service it is currently receiving The determination may be, for example, to confirm that the state in which the terminal device's location is included in the area included in the second information has transitioned from a state in which the terminal device's location is included in the area to a state in which the terminal device's location is not included in the area. The state in which the terminal device's location is included in the area may indicate a state in which the terminal device's current location information is included in the range indicated by the information of one or more areas among the entries included in the second information, and the state is determined by checking whether the terminal device is located in any of the areas in the list indicated by the SSB index. In addition to or instead of that, it may be determined whether the terminal device has moved or entered an area based on information obtained by a location information acquisition function of the terminal device, and the information obtained by the location information acquisition function For example, inertial measurement units (IMUs) such as inclinometers and angular rate sensors are used. The location information may be information obtained by a GPS (Global Positioning System) or a GNSS (Global Navigation Satellite System), or by other means. Additionally or alternatively, the information may be used to estimate the time it will take to enter the area from the current location, and if that time has passed, to move from the current location to the area associated with the MBS session information. In other words, the terminal device may constantly grasp location information and estimate the current location without comparing it with the second information.

[0191] By using the above mechanism, the base station device can receive MBS multicast services within its cell range. For a terminal device in a non-active state that can be received, the area information associated with the MBS session information is It is possible to provide an appropriate MBS multicast service based on the

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

[0193] Each piece of region information may be information indicating a part or all of the region of the cell, or information indicating a region independent of the cell. Additionally or alternatively, each piece of region information may be information common to one or more cells. Additionally or alternatively, each piece of region information may be information indicating a region based on a relative position with respect to the reference location of the cell. Additionally or alternatively, each piece of region information may be information indicating a region based on an absolute position independent of the cell.

[0194] Furthermore, other information may be notified to the terminal device as the second information, instead of information indicating the area. For example, the terminal device may be notified of information on MBS broadcast services and / or MBS sessions that it is permitted to receive from the network (base station device). For example, the information may include information such as the G-RNTI and service ID of the MBS session that is permitted to be received. It may also contain information necessary to decrypt the MBS sessions that are allowed to be In addition, the information may include information indicating a period for which the information is valid (for example, a timer value). The network (base station device) may notify the information based on location information notified from the terminal device. Additionally or alternatively, the network (base station device) may notify the information based on a report of measurement results of reference signals transmitted from one or more cells notified from the terminal device. Additionally or alternatively, the network (base station device) may notify the information based on other information.

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

[0196] In the above explanation, "link to" and "correspond to" are used interchangeably. , "associate with," etc. may be used interchangeably.

[0197] In the above explanation, "confirmed as A", "A is set", "A is included" Expressions such as these may be interchangeable.

[0198] In the above explanation, "transition from X to Y" can be rephrased as "X becomes Y." In the above description, "causing a transition" may be rephrased as "determining a transition."

[0199] In addition, in the above-described examples of processes or process flows, some or all of the steps may not be executed. In addition, in the above-described examples of processes or process flows, the order of the steps may be different. In addition, in the above-described examples of processes or process flows, some or all of the processing within each step may not be executed.

[0200] In the above description, when it is stated that "C may be D" and "C may be E", it may also include that "D may be E". Also, in the above description, when it is stated that "F may be G" and "G may be H", it may also include that "F may be H".

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

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

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

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

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

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

[0207] 100 E-UTRA 102 eNB 104 EPC 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interfaces 122UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 Processing section 504, 600 Transmitter

Claims

1. A terminal device that communicates with a base station device, The base station device transmits one or more multicast broadcast services (MBS a receiving unit for receiving control information relating to the one or more regions and a processing unit for receiving one or more region information; The control information may include part or all of the MBS multicast session and one or more and information associating the number of pieces of area information with the number of pieces of area information, each piece of area information is information indicating a part or all of an area of ​​the cell; The processing unit determines that the terminal device has entered one of the areas included in the control information based on area information included in the control information and location information held by the terminal device, and acquires the control information from the base station device based on the determination that the terminal device has entered one of the areas. Terminal device.

2. 1. A method for communicating with a base station device, comprising: The base station device transmits one or more multicast broadcast services (MBS receiving control information for the one or more regions; The control information may include part or all of the MBS multicast session and one or more and information associating the number of pieces of area information with the number of pieces of area information, each piece of area information is information indicating a part or all of an area of ​​the cell; The processing unit determines that the terminal device has entered one of the areas included in the control information based on area information included in the control information and location information held by the terminal device, and acquires the control information from the base station device based on the determination that the terminal device has entered one of the areas. method.

3. An integrated circuit implemented in a terminal device that communicates with a base station device, The base station device transmits one or more multicast broadcast services (MBS ) and one or more pieces of area information; The control information may include part or all of the MBS multicast session and one or more and information associating the number of pieces of area information with the number of pieces of area information, each piece of area information is information indicating a part or all of an area of ​​the cell; The integrated circuit determines that the terminal device has entered one of the areas included in the control information based on area information included in the control information and location information held by the terminal device, and performs a function of acquiring the control information from the base station device based on the determination that the terminal device has entered one of the areas. Integrated circuit.

Images