Terminal devices, methods, and integrated circuits

Abstract

The present invention provides terminal equipment, methods, and integrated circuits that provide services to appropriate areas in a non-terrestrial network (NTN). [Solution] In a mobile communication system, the terminal device comprises a receiving unit that receives configuration information transmitted from a base station device, and a processing unit. The configuration information includes a first area information list, which is a list composed of one or more geographic area information elements that indicate one or more geographic areas. The processing unit initiates the MRB setting procedure based on its determination that the terminal device is not located within the set of geographic areas indicated by one or more geographic area information elements included in the first area information list.

Description

Technical Field

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

Background Art

[0002] In the 3rd Generation Partnership Project (3GPP (registered trademark)), which is a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems including radio access, core network, services, etc. are being carried out. For example, in 3GPP, E-UTRA (Evolved Universal Terrestrial Radio Access) was started for technical studies and standardization as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th generation and 4th generation. Even now, in 3GPP, technical studies and standardization of extended technologies of E-UTRA are being carried out. Note that E-UTRA is also referred to as Long Term Evolution (LTE (registered trademark)), and extended technologies may also be referred to as LTE-Advanced (LTE-A), LTE-Advanced Pro (LTE-A Pro).

[0003]

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

Prior Art Documents

Non-Patent Documents

[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 [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] Within 3GPP, as an extension of NR technology, for example in the consideration of non-terrestrial networks (NTN), the provision of multicast / broadcast services (MBS) is being considered. And, as MBS, we provide content to a collection of one or more cells in the area where we can offer the service. A specific mechanism defines an area as a "sea area" and establishes a session for all terminals within that area that are intended to receive content. However, because the size of a single cell provided by a satellite has a much larger coverage area than a cell in a terrestrial network, there is a problem in that content may be unintentionally delivered to areas where it is not necessary or where it should not be delivered.

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of its objectives is to provide a terminal device, a communication method, and an integrated circuit that can efficiently provide communication control. [Means for solving the problem]

[0008] To achieve the above objective, one aspect of the present invention employs the following means. That is, one aspect of the present invention is a terminal device comprising a receiving unit that receives configuration information transmitted from a base station device, and a processing unit, wherein the configuration information includes a first area information list, and the first area information list indicates one or more geographical areas. A list comprising a number of geographical area information elements, wherein the processing unit indicates the terminal device by one or more geographical area information elements included in the first area information list. Based on the determination that it is not located within the set of geographical areas, the setting of the MRB This is the terminal device that initiates the procedure.

[0009] Furthermore, one aspect of the present invention is a method applied to a terminal device, wherein the configuration information transmitted from the base station device includes a first area information list, and the first area information list is a list comprising one or more geographic area information elements indicating one or more geographic areas, the steps of receiving the configuration information and the terminal device being the first The steps include determining that the area is not located within a set of geographical areas indicated by one or more geographical area information elements included in the area information list, and setting the MRB based on the said determination. This method includes a step to initiate the procedure.

[0010] Furthermore, one aspect of the present invention is an integrated circuit implemented in a terminal device, wherein the configuration information transmitted from the base station device includes a first area information list, and the first area information list The list is composed of one or more geographic area information elements that indicate one or more geographic areas, and the terminal device has a function to receive the configuration information and the terminal device has the first A function to determine that a location is not located within a set of geographical areas indicated by one or more geographical area information elements included in the area information list, and an MRB setting procedure based on the said determination. An integrated circuit that causes the terminal device to exhibit a function of starting.

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

Advantages of the Invention

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

Brief Description of the Drawings

[0013] [Figure 1] Schematic diagram of the communication system according to this embodiment. [Figure 2] Diagram of an example of the E-UTRA protocol configuration according to this embodiment. [Figure 3] Diagram of an example of the NR protocol configuration according to this embodiment. [Figure 4] Diagram showing an example of the flow of procedures for various settings in RRC according to this embodiment. [Figure 5] Block diagram showing the configuration of the terminal device in this embodiment. [Figure 6] Block diagram showing the configuration of the base station device in this embodiment. [Figure 7] An example of the processing in this embodiment. [Figure 8] An example of the ASN.1 description of the area information in this embodiment. [Figure 9] An example of the ASN.1 description of the MBS broadcast setting in this embodiment. [Figure 10] ]>END]]An example of the ASN.1 description of the frequency selection area ID in this embodiment.

Mode for Carrying Out the Invention

[0014] This embodiment will now 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). Furthermore, LTE that can connect with NR via Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. Additionally, LTE using 5GC in its core network (CN) may be distinguished from conventional LTE using EPC in its 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. The following description will use terms related to LTE and NR, but this embodiment may refer to technologies that use other terms. , and / or other wireless access technologies may be applied. Also, E-UTRA in this embodiment The terms "LTE" and "LTE" can be used interchangeably.

[0016] In this embodiment, the names of each node and entity, and the processing at each node and entity, are described when the wireless access technology is E-UTRA or NR, but this embodiment may also be applied to other wireless access technologies. The names of each node and entity, and the names of parameters and messages in this embodiment may differ from those described in this embodiment.

[0017] Figure 1 is a schematic diagram of the communication system according to this embodiment. The functions of each node, wireless access technology, core network, interface, etc., described using Figure 1 are only some of the functions closely related to this embodiment, and other functions may also be present.

[0018] E-UTRA100 may be a wireless access technology. Also, E-UTRA100 is between UE122 and eNB102. It may be an air interface. The air interface between UE122 and eNB102 may be called the Uu interface. eNB (E-UTRAN Node B)102 is the base of E-UTRA100 It may be a local station device. The eNB102 may have the E-UTRA protocol described below. The E-UTRA protocol is the E-UTRA User Plane (UP) protocol described below, and the E-UTRA protocol described below. It may consist of a Control Plane (CP) protocol. eNB102 is connected to UE122. Conversely, the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol may be terminated. The wireless access network composed of eNBs may be called E-UTRAN.

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

[0020] One or more eNB102 may be connected to the EPC104 via interface 112. Interfaces may exist between multiple eNB102 connected to EPC104 (not shown). These interfaces between multiple eNB102 connected to EPC104 may be called X2 interfaces.

[0021] NR106 may be a wireless access technology. Also, NR106 is an air connection between UE122 and gNB108. It may be an air interface. The air interface between UE122 and gNB108 may be called the Uu interface. gNB (g Node B)108 may be the base station equipment for NR106. The gNB108 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. It may consist of a Tocol. The gNB108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol to the UE122.

[0022] 5GC110 may be the core network. Interface 116 is the interface between gNB108 and 5GC110. It is an interface, and can be called an NG interface. Interface 116 includes: Control plane interface through which control signals pass, and / or user interface through which user data passes. A plane interface may exist. Control plane interface of interface 116 The process terminates in the Access and Mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 116 may be terminated by a User Plane Function (UPF: not shown) in 5GC110. The control plane interface of interface 116 may be called the NG-C interface. The user plane interface of interface 116 may be called the NG-U interface.

[0023] One or more gNB108s may be connected to the 5GC110 via interface 116. Interfaces may exist between multiple gNB108 connected to the 5GC110 (not shown). The interfaces between multiple gNB108 connected to the 5GC110 may be called Xn interfaces.

[0024] eNB102 may have the function to connect to 5GC110. An eNB102 that has the function to connect to 5GC110 may be called ng-eNB. Interface 114 is the interface between eNB102 and 5GC110, NG It can be called an interface. The control plane through which control signals pass is the interface 114. An interface, and / or a user plane interface through which user data passes, exists. It may be present. The control plane interface of interface 114 may be terminated at the AMF in 5GC110. The user plane interface of interface 114 may be terminated at the UPF in 5GC110. The control plane interface of interface 114 is called the NG-C interface. Good. The user plane interface of interface 114 is called the NG-U interface. That's fine. A wireless access network consisting of ng-eNB or gNB can be called NG-RAN. . NG-RAN, E-UTRAN, etc. may simply be referred to as networks. Also, networks include This may include eNB, ng-eNB, and gNB.

[0025] One or more eNB102s may be connected to the 5GC110 via interface 114. Interfaces may exist between multiple eNB102 connected to 5GC110 (not shown). These interfaces between multiple eNB102 connected to 5GC110 may be called Xn interfaces. Furthermore, the eNB102 connected to 5GC110 and the gNB108 connected to 5GC110 are connected via interface 120. It is permissible to do so. The interface 120 between eNB102 connected to 5GC110 and gNB108 connected to 5GC110 may be called the Xn interface.

[0026] gNB108 may have the function to connect to EPC104. A gNB108 that has the function to connect to EPC104 may be called an en-gNB. Interface 118 is the interface between gNB108 and EPC104, S1 It can be called an interface. Interface 118 is a user interface through which user data passes. A lane interface may exist. User plane interface of interface 118 The line may be terminated at the S-GW (not shown) in EPC104. User plane of interface 118 The interface may be called the S1-U interface. Also, the eNB102 connected to EPC104 and the gNB108 connected to EPC104 may be connected by interface 120. The interface 120 between the eNB102 connected to EPC104 and the gNB108 connected to EPC104 may be called the X2 interface.

[0027] Interface 124 is the interface between EPC104 and 5GC110, and is CP only, or UP It may be an interface that passes through both CP and UP. In addition, some or all of the interfaces among interfaces 114, 116, 118, 120, and 124 may be communications systems provided by telecommunications carriers, etc. It is acceptable for it not to exist depending on the situation.

[0028] UE122 may be a terminal device capable of receiving system information and paging messages transmitted from eNB102 and / or gNB108. UE122 may also be a terminal device capable of wireless connection with eNB102 and / or gNB108. Furthermore, UE122 may be a terminal device capable of wireless connection with eNB102. The terminal device may be capable of simultaneously establishing a wireless connection with the gNB108. The UE122 may have the E-UTRA protocol and / or the NR protocol. The wireless connection may be a Radio Resource Control (RRC) connection.

[0029] Furthermore, UE122 connects to EPC104 and / or 5GC110 via eNB102 and / or gNB108. It may be a terminal device capable of connection. If the core network to which the eNB102 and / or gNB108 that UE122 communicates is connected is EPC104, then the Data Radio Bearers (DRBs) established between UE122 and the eNB102 and / or gNB108, as described below, will further pass through EPC104. Each EPS (Evolved Packet System) bearer may be uniquely associated with it. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Also, IP traffic passing through the same EPS bearer may be uniquely associated with it. Data such as packets and Ethernet® frames should be guaranteed the same QoS. .

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

[0031] EPC104 does not need to have a PDU session and / or QoS flow. Also, 5GC110 An EPS bearer does not need to exist. When UE122 is connected to EPC104, UE122 will have information about the EPS bearer, but it does not need to have information about the PDU session and / or QoS flow. Furthermore, when UE122 is connected to 5GC110, UE122 will manage PDU sessions and / or QoS flows. It should have internal information, but it does not need to have EPS bearer information.

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

[0033] Figure 2 is a diagram of an example of the E-UTRA protocol architecture according to this embodiment. Figure 3 is a diagram of an example of the NR protocol architecture according to this embodiment. Note that Figures 2 and / The functions of each protocol, as explained using Figure 3, are some of the functions closely related to this embodiment. And it may have other functions. In this embodiment, the uplink (UL) may be a link from a terminal device to a base station device. Also in this embodiment, the downlink A link (downlink: DL) may be a link from a base station device to a terminal device. In terms of configuration, a sidelink (SL) refers to a base station device connecting one terminal device to another. It's fine if it's a link that doesn't involve intermediaries.

[0034] Figure 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in Figure 2(A), the E-UTRA UP protocol may be a protocol between UE122 and eNB102. That is, the E-UTRA UP protocol may be a protocol that terminates on the network side at eNB102. Figure 2(A) As shown, the E-UTRA user plane protocol stack may consist of a radio physical layer (PHY) 200, a medium access control layer (MAC) 202, a radio link control layer (RLC) 204, and a packet data convergence protocol layer (PDCP) 206.

[0035] Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in Figure 3(A), NR The UP protocol may be the protocol between UE122 and gNB108. That is, the NR UP protocol. This protocol may terminate at gNB108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack may consist of the wireless physical layer PHY300, the media access control layer MAC302, the wireless link control layer RLC304, the packet data convergence protocol layer PDCP306, and the service data adaptation protocol layer (service data adaptation protocol layer) SDAP (Service Data Adaptation Protocol)310.

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

[0037] Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in Figure 3(B), the NR CP In Rotokol, the RRC308, which is the wireless resource control layer, is the protocol between UE122 and gNB108. It may be a protocol that terminates with gNB108 on the network side. Also, in the NR CP protocol, the non-AS layer NAS312 is a protocol that connects UE122 and AMF. It can be a protocol. That is, the NAS312 is a protocol that terminates with AMF on the network side. It's okay to have it.

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

[0039] In this embodiment, the E-UTRA protocol and the NR protocol are not distinguished below, 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 be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, respectively, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. Furthermore, SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

[0040] Furthermore, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 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 protocol, respectively. These are sometimes called PDCP for E-UTRA and RRC for E-UTRA or LTE. Also, PHY200, MAC202, RLC204, PDCP206, and RRC208 are referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE, 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. Furthermore, a distinction is made between the E-UTRA protocol and the NR protocol. In such cases, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Furthermore, PHY300, MAC302, RLC304, PDCP306, and RRC308 may also be written as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0041] This section describes entities in the AS layer of E-UTRA and / or NR. Entities that possess some or all of the functionality of the MAC layer may be called MAC entities. RLC Entities that possess some or all of the layer's functionality may be called RLC entities. Entities that possess some or all of the PDCP layer's functionality may be called PDCP entities. An entity that possesses some or all of the functions of the SDAP layer may be called an SDAP entity. An entity that possesses some or all of the functions of the RRC layer may be called an RRC entity. MAC entities, RLC entities, PDCP entities, SDAP entities, and RRC entities may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0042] Furthermore, data provided to lower layers from MAC, RLC, PDCP, SDAP, and / or MAC, RLC The data provided to PDCP and SDAP from lower layers can be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Furthermore, the data provided to MAC, RLC, PDCP, and SDAP from higher layers, and / or the data provided from MAC, RLC, PDCP, and SDAP to higher layers, can also be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU. These data units are referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. You may call it that. Also, you may call a segmented RLC SDU an RLC SDU segment.

[0043] Here, the base station equipment and the terminal equipment transmit signals in the upper layer. To exchange (send and receive). The higher layer can also be called the upper layer, and they are interchangeable. For example, base station equipment and terminal equipment send and receive RRC messages (also called RRC message or RRC signalling) at the Radio Resource Control (RRC) layer. It is also possible that the base station equipment and the terminal equipment transmit and receive MAC control elements at the MAC (Medium Access Control) layer. Furthermore, the RRC layer of the terminal equipment acquires system information broadcast from the base station equipment. Here, RRC messages, system information, and or / or, the MAC control element controls the signals of the upper layer (upper layer signals). These are also called signaling or higher layer parameters. Each parameter included in the higher layer signal received by a terminal device may also be called a higher layer parameter. For example, in the processing of the PHY layer, the higher layer refers to the layer above the PHY layer, and may refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the higher layer may refer to one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.

[0044] The following means that the upper layers of the terminal device (mainly the RRC layer and MAC layer, etc.) receive A from the base station device, and the received A is then passed from the upper layers of the terminal device to the lower layers of the terminal device (mainly the MAC layer and object layer). It may also mean that it is given (provided) to the (rational layer). For example, in a terminal device, "up "Higher layer parameters are provided" may mean that the terminal device receives a higher layer signal from the base station device, and the higher layer parameters contained in the received higher layer signal are provided from the upper layer of the terminal device to the lower layer of the terminal device. "Higher layer parameters are set in the terminal device" may mean that the higher layer parameters are given (provided) to the terminal device. For example, "higher layer parameters are set in the terminal device" may mean that the terminal device receives a higher layer signal from the base station device and sets the received higher layer parameters in its upper layer. However, "higher layer parameters are set in the terminal device" may also include setting default parameters that are pre-assigned to the upper layer of the terminal device. When describing the transmission of an RRC message from the terminal device to the base station device... The RRC entity of the terminal device sends a message to the lower layer. The expression "submit" is sometimes used. In terminal devices, RRC entities Therefore, "submitting a message to a lower layer" may also mean submitting a message to the PDCP layer. In a terminal device, "submitting a message to a lower layer" from the RRC layer. This is because RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.). This also means submitting messages to the PDCP entity corresponding to each SRB. Good. When the RRC entity of a terminal device receives an indication from a lower layer, The term "layer" may refer to one or more layers, such as the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0045] An example of PHY functionality is described below. The PHY of the terminal device receives downlink from the PHY of the base station device. Downlink (DL) receives data transmitted via the Physical Channel. It may have the function. The PHY of the terminal device is related to the PHY of the base station device, and is an uplink (UL) device. The PHY may have the function of transmitting data via a transport channel. The PHY may be connected to the higher-level MAC via a transport channel. The PHY may transfer data to the MAC via the transport channel. The PHY may also transfer data from the MAC via the transport channel. Data may be provided. In the PHY, RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0046] Now, let's explain physical channels. The following physical channels may be included in the physical channels used for wireless communication between terminal equipment and base station equipment.

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

[0048] PBCH may be used to broadcast system information required by terminal devices.

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

[0050] PDCCH is used in downlink wireless communication (wireless communication from base station equipment to terminal equipment). It may be used to transmit (or carry) Downlink Control Information (DCI). Here, for the transmission of Downlink Control Information, one or more DCIs (DCI A format (which may also be called a format) may be defined. That is, for downlink control information The field may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate. It may be transmitted in the candidate. The terminal device may monitor the set of PDCCH candidates in the serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The terminal device may also perform a search sample PDCCH candidates may be monitored at configured monitoring occasions within one or more configured control resource sets (CORESET) as set by the configuration. The DCI format may be used for scheduling PUSCH in serving cells. PUSCH may be used for sending user data or sending RRC messages, as described later.

[0051] PUCCH is used in uplink wireless communication (wireless communication from terminal equipment to base station equipment), It may be used to transmit Uplink Control Information (UCI). Here, the Uplink Control Information may include Channel State Information (CSI), which is used to indicate the state of the Downlink channel. The control information may include scheduling requests (SRs) used to request UL-SCH (UL-SCH: Uplink Shared Channel) resources. The link control information includes HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement). It's okay to be born.

[0052] PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. In the case of downlinks, PDSCH may also transmit system information (SI: System Information). n) It may be used for sending Random Access Responses (RARs), etc.

[0053] PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or to transmit HARQ-ACK and / or CSI along with uplink data. Alternatively, PUSCH may be used to transmit CSI only, or HARQ-ACK and CSI only. In other words, PUSCH may be used to transmit only UCI messages. Alternatively, PDSCH or PUSCH may be used to transmit RRC messages and MAC CE messages, as described later. In PDSCH, RRC messages transmitted from a base station may be common signaling for multiple terminal devices within a cell. Alternatively, RRC messages transmitted from a base station may be dedicated signaling for a particular terminal device. That is, terminal device-specific (UE-specific) information may be dedicated to a particular terminal device. It may also be transmitted using the signaling of the UE. In addition, PUSCH can transmit on the uplink. It may be used to transmit force (UE Capability).

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

[0055] This section describes an example of MAC functionality. MAC may also be called a MAC sublayer. MAC connects various logical channels to their corresponding transport channels. It may have a function to perform mapping. A logical channel has a logical channel identifier (Logical MAC may be identified by Channel Identity (or Logical Channel ID). MAC may be connected to the higher-level RLC via a logical channel. Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information, depending on the type of information being transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. MAC may have the function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY. MAC may also provide from the PHY MACs may have a function to demultiplex the processed MAC PDUs and provide them to higher layers via the logical channels to which each MAC SDU belongs. MACs may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). Furthermore, MACs may have a scheduling reporting function to report scheduling information. MAC has the ability to perform priority processing between terminal devices using dynamic scheduling. Furthermore, MAC may have the functionality to handle priority processing between logical channels within a single terminal device. MAC has the ability to prioritize the processing of 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 Service (MBS). The MAC selects the transport format. MAC may have the function of intermittent reception (DRX: Discontinuous Reception) and / or Features include: discontinuous transmission (DTX), random access (RA) procedure execution, power headroom report (PHR) function to notify transmit power information, and data buffer size information to notify the data buffer. It may have a Buffer Status Report (BSR) function, etc. NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. Furthermore, MAC PDU may include MAC control elements (MAC CE), which are elements for control within the MAC.

[0056] Uplink (UL) and / or downlink used in E-UTRA and / or NR This section explains logical channels for Downlink (DL).

[0057] 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] CCCH (Common Control Channel) may be a logical channel for transmitting control information between terminal equipment and base station equipment. CCCH is used when terminal equipment does not have RRC connection. It may be used. Furthermore, CCCH may 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 terminal equipment and base station equipment. That is fine. Dedicated control information may be control information specific to each terminal device. 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 one-to-one (point-to-point) between a terminal device and a base station device. It may be a logical channel for transmitting data. Dedicated user data may be user data specific to each terminal device. DTCH may exist on both the uplink and downlink.

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

[0063] MTCH (Multicast Traffic Channel) transmits data from base station equipment to terminal equipment. It may be a point-to-multipoint downlink channel for this purpose. The MTCH may be a logical channel for multicast and / or broadcast.

[0064] Logical channels and transport channels of the uplink in E-UTRA and / or NR Let's explain the mapping of the 'ru'.

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

[0066] DCCH is an uplink transport channel, also known as UL-SCH (Uplink Shared Channel). It can be mapped to this.

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

[0068] Logical channels and transport channels of downlinks in E-UTRA and / or NR Let's explain the mapping of the 'ru'.

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

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

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

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

[0073] DTCH stands for Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

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

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

[0076] An example of RLC functionality is described below. RLC may also be called an RLC sublayer. E-UTRA RLC may have the functionality to segment and / or concatenate data provided from the upper layer PDCP and provide it to the lower layer. E-UTRA RLC may also reassemble and reorder data provided from the lower layer. It may have the functionality to perform ring (re-ordering) and provide it to the upper layer. NR RLC is the upper layer The NR RLC may have the function of adding a sequence number to the data provided by the PDCP of the layer, independent of the sequence number added by the PDCP. The NR RLC may also have the function of segmenting the data provided by the PDCP and providing it to the lower layer. Furthermore, the NR RLC may have the function of reassembling the data provided by the lower layer and providing it to the upper layer. The RLC may also have a data retransmission function and / or a retransmission request function (Automatic RLC may have a Repeat Request (ARQ) function. RLC may also have a function to perform error correction using ARQ. The control information sent from the RLC receiver to the transmitter, indicating the data that needs to be retransmitted, can be called a status report. Also, the RLC transmitter sends this information to the receiver. The instruction to send a status report can be called a "poll." Also, RLC is a data It may have a function to detect duplicate data. RLC may also have a data discard function. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM mode, data received from higher layers is not split, and an RLC header is not required. TM RLC entity A T is a unidirectional entity, and transmits™ RLC. It may be configured as an entity or as a receiving TM RLC entity. UM performs tasks such as splitting and / or joining data received from higher layers, and adding RLC headers. Data retransmission control is not required. A UM RLC entity may be a unidirectional or bidirectional entity. If a UM RLC entity is a unidirectional entity, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If a 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 splitting and / or merging of data received from a higher 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. Furthermore, the data provided to lower layers by TM, and / or the data provided from lower layers, The data provided to lower layers by UM, and / or data provided from lower layers, may be called UMD PDUs. The data provided to lower layers by AM, and Alternatively, data provided from lower layers can be called AMD PDU. Used in E-UTRA RLC. The RLC PDU format used in NR RLC and the RLC PDU format used in NR RLC may be different. Furthermore, there may be data RLC PDUs and control RLC PDUs. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). The control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU).

[0077] This section describes an example of PDCP functionality. PDCP may be referred to as the PDCP sublayer. PDCP may have the function of maintaining sequence numbers. Furthermore, PDCP efficiently transmits user data such as IP packets and Ethernet frames over the wireless section. It may have a header compression / decompression function for this purpose. The protocol used for compressing and decompressing IP packet headers may be called the ROHC (Robust Header Compression) protocol. The protocol used for compressing and decompressing Ethernet frame headers is EHC (Ethernet(registered trademark)). It may be called a Header Compression (PDCP) protocol. PDCP may also have data encryption / decryption capabilities. PDCP may also have data integrity protection / verification capabilities. PDCP may also have reordering capabilities. PDCP may also have PDCP SDU retransmission capabilities. PDCP may also have data discarding capabilities using a discard timer. PDCP may also have duplication capabilities. Furthermore, PDCP may have a function to discard duplicate received data. A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0078] This section describes an example of SDAP functionality. SDAP is a Service Data Adaptive Protocol Layer (SAP). SDAP is a bis-data adaptive protocol layer. SDAP transmits data from the 5GC110 to the terminal via the base station equipment. Mapping the downlink QoS flow sent to the device with the data radio bearer (DRB) (map The SDAP may have the function of mapping (mapping) and / or mapping the uplink QoS flow sent from the terminal device to the 5GC110 via the base station device to the DRB. The SDAP may also have the function of storing mapping rule information. The SDAP may also have the function of marking QoS flow identifiers (QoS Flow ID: QFI). Note that there may be data SDAP PDUs and control SDAP PDUs. The data SDAP PDU may be an SDAP DATA PDU (SDAP Data PDU, SDAP Data It is acceptable to call it a PDU. Also, a control SDAP PDU is called an SDAP CONTROL PDU (SDAP Control PDU, SDAP PDU). These may be called control PDUs or SDAP control PDUs. Note that there may be only one SDAP entity for each PDU session on the terminal device.

[0079] An example of RRC functionality is described below. RRC may have broadcast functionality. RRC may also have paging capabilities from EPC104 and / or 5GC110. It may have the following capabilities. The RRC may have the ability to call (paging) from the eNB102 connected to the gNB108 or 5GC110. The RRC may also have the ability to manage RRC connections. The RRC may also have the ability to manage RRC connections. It may have wireless bearer control functionality. Furthermore, the RRC may have cell group control functionality. The RRC may have mobility control functions. The RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions. Furthermore, the RRC may have QoS management functions. The RRC may also have wireless link failure detection and recovery functions. The RRC may use RRC messages to perform functions such as broadcasting, paging, RRC connection management, wireless bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, and wireless link failure detection and recovery. Note: E-UTRA The RRC messages and parameters used in RRC are... It may be different from Lameta.

[0080] RRC messages may be sent using the logical channel BCCH. In addition to that or Alternatively, RRC messages may be sent using the logical channel PCCH. In addition... Alternatively, RRC messages may be sent using the logical channel CCCH. In addition to or instead of, RRC messages are sent using the logical channel DCCH. It may be done. In addition to or instead of that, the RRC message may use the MCCH of the logical channel. It may be used to send messages. Furthermore, RRC messages sent using DCCH are referred to as dedicated RRC signaling or RRC signaling.

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

[0082] RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request messages, RRC Resume Request messages, RRC Reestablishment Request messages, and RRC System Information Request messages. This may include messages such as Sage (RRC System Info Request). It may also include messages such as RRC Connection Request, RRC Connection Resume Request, and RRC Connection Reestablishment Request. Other RRC messages may also be included.

[0083] RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject messages, RRC Connection Setup messages, RRC Connection Reestablishment messages, and RRC Connection Reestablishment Reject messages. It may include, for example, RRC rejection messages and RRC setup messages. It may also include other RRC messages.

[0084] RRC signaling transmitted in the uplink (UL) direction using DCCH includes, for example, measurement reports. Messages such as Measurement Report, RRC Connection Reconfiguration Complete, RRC Connection Setup Complete, RRC Connection Reestablishment Complete, Security Mode Complete, and UE Capability Information may be included. RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message, Security Mode Complete message This may include messages such as "Security Mode Complete" and "UE Capability Information." It may also include other RRC signaling.

[0085] RRC signaling sent in the downlink (DL) direction using DCCH may include, for example, RRC Connection Reconfiguration messages, RRC Connection Release messages, Security Mode Command messages, and UE Capability Enquiry messages. Other examples include RRC Reconfiguration messages, RRC Resume messages, RRC Release messages, RRC Reestablishment messages, and Security Mode Command messages. This may include messages such as Security Mode Commands and UE Capability Enquiry messages. It may also include other RRC signaling.

[0086] RRC messages sent in the downlink (DL) direction using MCCH may include, for example, MBS broadcast configuration messages (MBSBroadcastConfiguration messages). Other RRC signaling may be included.

[0087] Let's explain an example of NAS functionality. A NAS may have authentication functionality. Also, a NAS can be mobile... It may have a mobility management function. Furthermore, the NAS may have security control functions. You may have it.

[0088] The aforementioned functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS are just examples, and some of each function may be present. Not all of these features need to be implemented. Also, some or all of the functionality of each layer may be included in other layers.

[0089] Next, we will explain the state transitions of UE122 in LTE and NR. When UE122 is connected to EPC or 5GC, it may be in the RRC_CONNECTED state when an RRC connection has been established. The state in which an RRC connection has been established means that UE122 has... This may include a state that holds some or all of the UE context described above. Also, the RRC connection is An established state may include a state in which UE122 can send and / or receive unicast data. UE122 may also be in the RRC_INACTIVE state when the RRC connection is suspended. Furthermore, UE122 may be in the RRC_INACTIVE state when it is connected to 5GC and the RRC connection is suspended. UE122 may be in the RRC_IDLE state when it is neither in the RRC_CONNECTED state nor the RRC_INACTIVE state.

[0090] Note that when UE122 is connected to EPC, it does not have the RRC_INACTIVE state, but E-UTRAN The RRC connection may be put into a pause state. If UE122 is connected to EPC, when the RRC connection is put into a pause state, UE122 may transition to the RRC_IDLE state, retaining the UE's AS context and the identifier (resumeIdentity) used for resuming. The upper layer of the UE122's RRC layer (e.g., the NAS layer) will, when UE122 retains the UE's AS context, E-UTRAN has permitted the resumption of the RRC connection, and UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state, then the paused RRC connection You may begin your recovery.

[0091] The definition of hibernation may differ between UE122 connected to EPC104 and UE122 connected to 5GC110. Also, the definition of hibernation may differ depending on whether UE122 is connected to EPC (when UE122 is hibernating in the RRC_IDLE state) or UE122 is connected to 5GC (when UE122 is hibernating in the RRC_INACTIVE state). The procedure for resuming from hibernation may be partially or entirely different.

[0092] Note that the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state are respectively referred to as "connection". These states may be referred to as connected mode, inactive mode, or idle mode, or as RRC connected mode, RRC inactive mode, or RRC idle mode.

[0093] The AS context of the UE held by UE122 may include all or part of the following information: current RRC settings, current security context, PDCP status including ROHC (RObust Header Compression) status, C-RNTI (Cell Radio Network Temporary Identifier) ​​used by the source PCell, cell identifier, and physical cell identifier of the source PCell. Furthermore, the AS context of the UE held by any or all of eNB102 and gNB108 is: It may contain the same information as the AS context of the UE held by UE122, or it may contain information different from the information contained in the AS context of the UE held by UE122.

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

[0095] Next, we will explain the Serving Cell. The CA and / or DC described later are In terminal devices with an unconfigured RRC connection, the serving cell has one primer It may consist of primary cells (PCells). Also, the CA and / or DC described later may In terminal devices with configured RRC connection status, multiple serving cells are one or Multiple Special Cells (SpCells) and one or more secondary A SpCell may refer to a set of cells (s) composed of multiple Secondary Cells (SCells). A SpCell may support PUCCH transmission and contention-based Random Access (CBRA), and may always be activated. A 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. A PCell may also be used when a terminal device re-establishes its RRC connection. It may be a cell used in the establishment procedure. Also, PCell is a random element during handover. A cell may be used in the access procedure. A PSCell may be used in the random access procedure when adding a secondary node, as described later. A SpCell may be used for purposes other than those mentioned above.

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

[0097] This section describes cell groups, which are configured on terminal devices by base station devices. A cell group may consist of one SpCell. Alternatively, a cell group may consist of one SpCell and one or more SCells. In other words, a cell group may consist of one SpCell And, as needed, it may consist of one or more SCells. A loop can be described as a set of cells.

[0098] Dual Connectivity (DC) is a method of data communication that utilizes the radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node). It is acceptable for this technology to be used. When DC or MR-DC (described later) is performed, the base station equipment is connected to the terminal equipment. Cell groups may be added from the first base station device. To perform data center operations, the first base station device may add a second base station device. The first base station device may be called the Master Node (MN). The cell group formed by the Master Node may be called the Master Cell Group (MCG). The second base station device may be called the Secondary Node (SN). The cell group formed by the Secondary Node may be called the Secondary Cell Group (SCG). Note that the Master Node and Secondary Node may be configured within the same base station device.

[0099] Furthermore, when a DC is not configured, the cell group configured on the terminal device may be called an MCG. Also, when a DC is not configured, the SpCell configured on the terminal device may be a PCell. Furthermore, an NR without a configured DC may be called an NR standalone (NR SA).

[0100] Furthermore, Multi-Radio Dual Connectivity (MR-DC) may be defined as a technology that performs DC using E-UTRA for MCG and NR for SCG. It is acceptable. Furthermore, MR-DC is a technology that performs DC using NR in both MCG and SCG. Yes, it is acceptable. MR-DC may be a technology included in DC. As an example of MR-DC using E-UTRA for MCG and NR for SCG, there is EN-DC (E-UTRA-NR Dual Connectivity) which uses EPC for the core network. An NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC in the core network is acceptable. Furthermore, as an example of an MR-DC using NR in the MCG and E-UTRA in the SCG, an NE-DC (NR-E-UTRA Dual Connectivity) using 5GC in the core network is acceptable. Also, as an example of an MR-DC using NR in both the MCG and SCG... Therefore, it is acceptable to have NR-DC (NR-NR Dual Connectivity) that uses 5GC in the core network.

[0101] In a terminal device, there may be one MAC entity for each cell group. For example, when DC or MR-DC is configured on a terminal device, one MAC address for MCG There may be one MAC entity for the MCG. The MAC entity for the MCG in a terminal device may always be established in all states of the terminal device (RRC idle state, RRC connected state, and RRC inactive state, etc.). The MAC entity for the SCG is determined by the terminal device when the SCG is set up on the terminal device. It may be created. Also, MAC entities for each cell group of the terminal device. The terminal device is configured when it receives RRC signaling from the base station device. i. If the MAC entity is associated with MCG, SpCell may mean PCell. Furthermore, if a MAC entity is associated with an SCG, SpCell may mean Primary SCG Cell (PSCell). Also, if a MAC entity is associated with a cell group... If not specified, SpCell may mean PCell. PCell, PSCell, and SCell are service It is a ng cell. In EN-DC and NGEN-DC, the MAC entity for MCG is E-UTRA It may be a MAC entity, and the MAC entity for SCG may be an NR MAC entity. Also, in NE-DC, the MAC entity for MCG is an NR MAC entity. It is acceptable for the MAC entity for SCG to be an E-UTRA MAC entity. Also, in NR-DC, the MAC entities for both MCG and SCG may be NR MAC entities. Note that the statement that there is one MAC entity for each cell group can be rephrased as the statement that there is one MAC entity for each SpCell. Furthermore, the statement that there is one MAC entity for each cell group can be rephrased as the statement that there is one MAC entity for each SpCell.

[0102] This section describes the RRC signaling flow transmitted and received between terminal equipment and base station equipment. Figure 4 shows the flowchart for the various settings in the RRC according to this embodiment. This is a diagram illustrating an example of this. Figure 4 shows an example of the flow when RRC signaling is sent from the base station equipment (eNB102, and / or gNB108) to the terminal equipment (UE122).

[0103] In Figure 4, the base station device creates an RRC message (step S400). The creation of an RRC message by the base station device may be performed in order for the base station device to distribute system information (SI) or paging messages. The creation of a data entry involves the base station sending RRC signaling to a specific terminal device to perform a specific action. This may be done for the purpose of trust. Processes performed on a specific terminal device include, for example, security settings, RRC connection reconfiguration, handover to a different RAT, and RRC connection reconfiguration. This may include processes such as pausing the session and releasing the RRC connection. RRC connection resetting processes may include, for example, control of wireless bearers (establishment, modification, release, etc.) and control of cell groups (establishment). Processes such as adding, changing, releasing, measuring settings, handover, and security key updates. It may include. Also, the creation of RRC messages in the base station equipment is transmitted from the terminal equipment. This may be done in response to RRC signaling. Responses to RRC signaling transmitted from terminal devices include, for example, responses to RRC setup requests, responses to RRC reconnection requests, and RR This may include responses to C restart requests, etc. RRC messages contain various information notifications and information (parameters) for configuration. These parameters may be fields of the RRC message and / or information elements, or the values ​​of fields (including information elements). RRC message The structure is described using a notation method called ASN.1 (Abstract Syntax Notation One). stomach.

[0104] In Figure 4, the base station device then transmits the created RRC signaling to the terminal device (S Step S402). Next, the terminal device performs any necessary processing, such as configuration, according to the RRC signaling it has received (Step S404). The terminal device that has performed the processing may send an RRC signaling response to the base station device (not shown).

[0105] RRC signaling may be used for purposes other than those mentioned above.

[0106] In MR-DC, the RRC signaling for SCG settings (cell group settings, wireless bearer settings, measurement settings, etc.) may be transmitted between the master node and the terminal device. For example, in EN-DC or NGEN-DC, transmission and reception between eNB102 and UE122. The RRC signaling of E-UTRA may include the RRC signaling of NR in the form of a container. Also, in NE-DC, the RRC signaling of NR transmitted and received between gNB108 and UE122 may include the RRC signaling of E-UTRA in the form of a container. The RRC signaling for SCG-side configuration may be transmitted and received between the master node and the secondary node.

[0107] Note that the RRC signature for E-UTRA sent from eNB102 to UE122 is not limited to cases where MR-DC is used. The signaling may include RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include RRC signaling for E-UTRA.

[0108] This section explains the system information.

[0109] System information may be divided into a Master Information Block (MIB) and multiple System Information Blocks (SIBs). Furthermore, system information may include information blocks other than MIBs and SIBs.

[0110] MIB may be transmitted periodically from the base station equipment via BCH. MIB must be necessary to obtain SIB1. It may include necessary parameters. SIB1 may be transmitted periodically from the base station equipment via DL-SCH. SIB1 may include information regarding the availability and scheduling of other SIBs. That's fine. For example, SIB1 may include multiple fields, and one of those fields may include system information scheduling information. The system information scheduling information may include information on whether or not one or more SIBs are being broadcast, and information on the broadcast period. It may include things like "report" or "information."

[0111] SIBs other than SIB1 are included in the System Information Message (SI message) and are DL-SCH for base station equipment It may be sent from. System information messages may contain one or more SIBs. .

[0112] Terminal devices may apply a system information acquisition procedure to obtain system information. This procedure is used when terminals are in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. This may apply to terminal devices. Terminal devices in the RRC_IDLE state and RRC_INACTIVE state must have valid versions of MIB and SIB1.

[0113] The terminal device may apply the system information acquisition procedure when a cell is selected, when a cell is re-selected, or when it returns to coverage from outside the coverage area. Furthermore, the terminal device may use a valid version You may apply the system information retrieval procedure when you do not have an SIB (System Information Box).

[0114] This document explains the notification of changes to system information.

[0115] A change period may be used when changing system information. That is, updated system information messages (excluding some SI messages such as ETWS and CMAS, which will be described later) may be broadcast during the next change period following the transmission of the system information change instruction.

[0116] The boundary of the change period may be defined by the value of the SFN (System Frame Number) such that SFN mod m = 0 (where m is the number of wireless frames that make up the change period). The change period may be set by system information.

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

[0118] In a broadcast service, the same service and the same specific content data may be provided simultaneously to all terminal devices (UE122) within a geographical area. The service may be delivered to terminal devices using a broadcast session. Terminal devices broadcast in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. It's good that you can receive the service.

[0119] In a multicast service, the same service and the same specific content data may be delivered simultaneously to one or more specific terminal devices (also known as UE sets). Multicast services may be delivered to terminal devices using multicast sessions. Terminal devices can receive multicast services using mechanisms such as PTP (Point to Point) delivery and / or PTM (Point to Multipoint) delivery. HARQ feedback / retransmission This can be applied to both PTP and PTM transmissions.

[0120] MBS distribution may utilize some or all of the following logical channels: MTCH: Multicast session or broadcast from network to terminal device PTM downlink channel for transmitting session MBS data DTCH: A PTP channel defined for sending MBS data for multicast sessions from the network to terminal devices. MCCH: A PTM downlink channel used to transmit MBS broadcast control information and / or MBS multicast control information for one or more MTCHs associated with terminal devices from the network.

[0121] This shows an example of how RNTI is used in PTM transmission. The terminal device uses the same or different G-RNTI. Different services can be received using this. Terminal devices can use the same or different G-CS-RNTI. You can use it to receive different services.

[0122] In multicast services, gNBs may use the following methods to deliver MBS data packets: PTP transmission: The gNB may independently deliver separate copies of MBS data packets to each terminal device. In other words, the gNB may deliver the MBS data packets scrambled with a terminal device-specific RNTI (e.g., C-RNTI) to each terminal device. A terminal device-specific PDSCH is used to schedule a terminal device-specific PDSCH, and separate copies of the MBS data packets, scrambled with the same terminal device-specific RNTI, are distributed to each terminal device. good. PTM transmission: The gNB may deliver a single copy of the MBS data packets to the UE set. That is, the gNB schedules a group-common PDSCH using a group-common PDCCH scrambled with a group-common RNTI, and scrambles with the same group-common RNTI. A single copy of the MBS data packet may be delivered to the UE set.

[0123] If both PTM and PTP transmission are configured on the terminal device, gNB will perform MBS session QoS. Based on information such as requirements, the number of participating terminal devices, and individual terminal device reception quality feedback, multicast distribution is performed for specific terminal devices using either the PTM leg and / or the PTP leg. Whether or not to deliver data may be determined dynamically. Furthermore, regardless of the aforementioned determination, the same QoS requirements may apply to both PTM and PTP transmissions.

[0124] MBS broadcasts may be received by terminal devices in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. Terminal devices may receive MBS settings for a broadcast session (e.g., parameters required for MCCH reception) via MCCH in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. The parameters required for MCCH reception may be provided via system information.

[0125] The following principles may apply to the structure of 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. Information related to the session includes the MBS session ID and the associated G-RNTI scheduler. MCCH content may include MCCH repetition period, MCCH window period, and wireless frame / series information. It may be sent within a time-domain window that occurs periodically, defined by the lot offset. • MCCH uses a change period, and MCCH content may only be allowed to be modified at the change period boundary. A notification mechanism may be used to notify of changes to MCCH content due to the start, modification, or termination of a broadcast session, and changes in adjacent cell information. When a terminal device receives an MCCH change notification, it may obtain the updated MCCH for the same MCCH change period in which the change notification was sent.

[0126] This section describes the continuity of broadcast services in the RRC_IDLE and RRC_INACTIVE states.

[0127] The mobility procedure for MBS reception allows terminal devices to start or continue receiving MBS services when changing cells. gNB is a list of neighboring cells in the MCCH that provide the same MBS broadcast service as the serving cell. This allows terminal devices to request unicast reception of services before moving to cells that do not provide MBS broadcast services using PTM transmission, eliminating the need to read MBS broadcast-related system information on adjacent frequencies. The terminal device can determine which frequency the MBS broadcast service is provided via PTM through the MBS User Service Description (USD), or the following: This can be determined by the combination of these factors. • USD • System information (System Information Block: SIB, e.g., SIB21)

[0128] USD is information relating to one or more MBS services (also known as MBS user services). It may include. For example, USD may include one or more MBS user service description objects. Each of the MBS user service description objects may carry information about a single MBS user service. Each of the MBS user service description objects This includes one or more external service identifiers for a given MBS user service, a unique identifier for that MBS user service within the scope of the MBS system, information indicating when that MBS user service becomes active, and / or that the MBS user service It may include one or more MBS delivery session description objects. Each of the MBS delivery session description objects may contain parameters for that MBS delivery session. The URL to the session description document carrying the data, and the MBS service area of ​​that MBS-delivered session. Information, one or more MBS Frequency Selection Area Identities (FSAIs) associated with that MBS distribution session, one or more transmissions associated with each of the FSAIs The session description document may include some or all of the information regarding the signal frequency. The session description document may include information indicating the service type of the MBS, such as whether it is Broadcast or Multicast, and information regarding the Temporary Mobile Group Identity (TMGI). The TMGI may consist of the MBS service ID, MCC, and MNC.

[0129] In the RRC_IDLE and RRC_INACTIVE states, the terminal device may apply the following modifications to the normal cell reselection rules. Terminal devices that are receiving or interested in receiving MBS broadcast services via PTM are camped on the frequencies that provide these MBS broadcast services. During this time, these MBS broadcast services can be received, and certain conditions are met. In this case, this frequency can be set as the highest priority frequency. • The MBS broadcast service that the terminal device was interested in became unavailable. In cases where (for example, after a session has ended) or when the terminal device is no longer interested in receiving the service, the terminal device will not provide these MBS broadcast services. There is no need to give higher priority to certain frequencies.

[0130] This document explains the continuity of MBS broadcast services in the RRC_CONNECTED state.

[0131] Terminal devices in the RRC_CONNECTED state send an MBS Interest Indication (MII) consisting of the following information to the gNB to ensure the continuity of the MBS broadcast service. It is possible to believe. • A list of MBS frequencies that the terminal device is receiving or is interested in receiving, sorted by importance. • MBS frequencies that the terminal device is receiving or is interested in receiving, Uni Prioritizing the reception of cast bearers and multicast MRBs. • If PCell or SCell provides an SIB (e.g., SIB20) containing the information necessary to obtain the MCCH and / or MTCH settings for MBS broadcasts, then list the MBS broadcast services that the terminal device is receiving or is interested in receiving.

[0132] Current carrier frequency, and / or adjacent carrier frequency, and MBS Frequency Selection Does an SIB (e.g., SIB21) exist that includes mapping information with Area Identities (FSAI)? Based on this, the reporting of MBS Interest indications may be implicitly enabled / disabled. Furthermore, the information contained in MBS Interest indications may be exchanged between the source gNB and the target gNB during handover.

[0133] In broadcast services, gNBs use the following methods to broadcast You may distribute MBS data packets. PTM transmission: The gNB delivers a single copy of the MBS data packet to the UE set. For example, gNB is a group-common PDCCH scrambled with a group-common RNTI. Use to schedule group-common PDSCH scrambled with the same group-common RNTI. You may use Joules.

[0134] This section provides details about MBS Broadcasting.

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

[0136] MCCH provides MBS broadcast sessions in the cell and these sessions It may be used to deliver an MBS broadcast configuration message (MBSBroadcastConfiguration message) containing relevant scheduling information. Optionally, the MBSBroadcastConfiguration message may include the MBS broadcast information provided in the current cell. A list of adjacent cells that provide the same service as the service may be included. If the service area represents a portion of a cell, a list of information indicating that area may be included. It may also be indicated that the area representing a portion of a cell is excluded from the service area. Configuration information necessary for the terminal device to receive MCCH may be provided in SIB1 and SIB20. Furthermore, SIB21 may contain information on MBS broadcast service Information regarding the continuity of the service should be provided.

[0137] MCCH information (i.e., information transmitted in a message sent via MCCH) may be transmitted periodically within a configured transmission window using a configurable repetition period. MCCH transmissions (and associated radio resources and MCS) are transmitted via a PDCCH addressed to MCCH-RNTI. It's fine to show it that way.

[0138] PDCCH monitoring occasions for MCCH transmission are determined by searchspaceMCCH. It may be determined according to the common search space shown. searchspaceMCCH is set to zero. If searchspaceMCCH is set to a non-zero value, the PDCCH monitoring opportunity for receiving MCCH messages in the MCCH transmission window may be the same as the PDCCH monitoring opportunity for SIB1. In this case, the opportunity for PDCCH monitoring of an MCCH message may be determined based on the search space indicated by searchspaceMCCH.

[0139] Changes to MCCH information occur only in specific radio frames, and the concept of a modification period may be used. Within the modification period, the same MCCH information is used in its scheduling. Therefore, it may be transmitted only the defined number of times. If the network modifies some or all of the MCCH information, the network uses the PDCCH that schedules the MCCH to determine the MCCH change period. Changes may be notified to terminal devices from the start of the service. Terminal devices that receive notification of changes are receiving or will receive MBS services transmitted using MBS broadcast. If interested, the terminal device may obtain the new MCCH information from the same slot that received the change notification. The terminal device may apply the previously obtained MCCH information until it obtains the new MCCH information.

[0140] The terminal device receives information about MBS broadcast settings that the network broadcasts. To obtain the information, you may apply the MCCH information acquisition procedure. The MCCH information acquisition procedure is based on the RRC_IDLE state, RRC_INACTIVE state, or the common search space set by searchSpaceMCCH. This applies to MBS broadcast services that an MBS-enabled terminal device, which is in the RRC_CONNECTED state and has a certain BWP as an active BWP, is receiving or is interested in receiving. stomach.

[0141] If you are interested in receiving MBS broadcast services, the terminal device will have MCCH information You may apply the information acquisition procedure. If you are interested in receiving the MBS broadcast service... When a terminal device enters a cell that provides SIB20 (for example, when powered on), the terminal device moves (After activation), when SCell's SIB20 is received via dedicated signaling, and a new MBS service When notification is received that there has been a change in MCCH information due to the start of a service, the MCCH information acquisition procedure may be applied. Terminal devices receiving data via broadcast MRB should apply the new M If you are notified that your MCCH information has been changed due to a change in MCCH information other than the commencement of BS services, you may apply the MCCH information acquisition procedure. Unless explicitly specified in the MCCH information acquisition procedure, the MCCH information acquisition procedure may overwrite the stored MCCH information.

[0142] Devices that receive or are interested in receiving MBS broadcast services If the MCCH information acquisition procedure is triggered based on notification of a change in MCCH information, the device may begin acquiring MBSBroadcastConfiguration messages transmitted using MCCH from the slot where the change in MCCH information was notified. Also, if the terminal device enters a cell that provides SIB20, or if SIB20 is announced in SCell If the information contained in is received via RRC signaling, then from the next repetition period, use MCCH You may begin retrieving incoming MBSBroadcastConfiguration messages.

[0143] The broadcast MRB configuration procedure is used when a terminal device starts and / or stops receiving broadcast MRBs transmitted via MTCH, or when the settings of a broadcast MRB received by the terminal device are changed, to configure the PDCP, RLC, MAC, and PHY. It may be used. The broadcast MRB configuration procedure is as follows: RRC_IDLE state, RRC_INACTIVE state, This may apply to MBS broadcast services that an MBS-enabled terminal device is receiving or interested in receiving, if the BWP with a common search space set by searchSpaceMTCH or searchSpaceMCCH is in the RRC_CONNECTED state where the BWP is the active BWP. .

[0144] The terminal device may apply (start) the broadcast MRB configuration procedure to begin receiving an MBS session of an MBS broadcast service of interest. The MRB configuration procedure is for MBS-enabled terminal devices that are interested in receiving MBS broadcast services, and when an MBS session starts, the MBS broadcast service provider... When I entered the building, when I became interested in the ongoing MBS broadcast service, terminal device The capacity restrictions have been lifted, and the reception of ongoing MBS broadcast services will no longer be interrupted. It may be started when, for example, [this event occurs].

[0145] The terminal device stops receiving the MBS broadcast service session. The loadcast MRB release procedure may be applied (initiated). The broadcast MRB release procedure is applied when an MBS session is terminated, when a terminal device leaves the cell broadcasting the MBS service it is interested in, when it loses interest in the MBS service, or when it loses interest in the associated service. It may be initiated when restrictions on abilities that hinder faith are put into place.

[0146] As part of the broadcast MRB configuration procedure, the terminal device may perform the following operations:

[0147] The terminal device may establish PDCP entities, RLC entities, and / or SDAP entities according to the information about this broadcast MRB contained in the MBSBroadcastConfiguration message. The terminal device may also configure the MAC layer based on the MTCH scheduling information (mtch-SchedulingInfo). Furthermore, the terminal device may configure this broadcast MRB. The PHY layer may be configured based on the applicable settings. Additionally, the terminal device may receive DL-SCH in the same cell that received the MBSBroadcastConfiguration message for broadcast MRB establishment, using G-RNTI and / or mtch-SchedulingInfo for this MBS broadcast service.

[0148] As part of the broadcast MRB release procedure, the terminal device may perform the following operations:

[0149] The terminal device includes PDCP entities, RLC entities, and associated MAC settings and PHY. The settings may be released. Also, the terminal device will not be associated with an SDAP entity for which there is no MRB to associate. You may release Ti.

[0150] The above-mentioned MBS broadcast configuration message (MBSBroadcastConfiguration message) may include information indicating one or more MBS broadcast sessions (MBS session information list). In addition to or instead of the above, the MBS broadcast configuration The regular message includes a list of neighboring cells that provide the same broadcast MBS service. It may be included. Each entry in the MBS session information list may include MBS broadcast session identifier information (TMGI). The TMGI may include PLMN (Public Land Mobile Network) identifier information, or an index value associated with PLMN identifier information, in addition to or instead of that, the TMGI may include information to identify the MBS service within PLMN. It may include a service identifier (service ID). In addition to or instead of that, the MBS set The session information list contains one or more entries, and the MBS session information list The entries may include G-RNTI, which is used for MTCH scheduling and transmission scrambling. In addition to or instead of the entries in the MBS session information list. This may include broadcast MRB settings (e.g., PDCP settings and RLC settings). In addition to or instead of this, the MBS broadcast settings message may include the target area It may include a list of information indicating the (intended area). In addition to or instead Furthermore, the MBS broadcast configuration message may include information to link the target area with the MBS session. In addition to or instead of this, the MBS broadcast The configuration message may include information about areas excluded from the target area. The MBS broadcast configuration message may include either a list of information indicating the target area (intended area), information about areas excluded from the target area, or both.

[0151] (Procedure for determining MBS frequencies of interest)

[0152] A terminal device may determine that a certain frequency is part of the MBS frequency of interest on the basis that all of the following conditions (ca) to (cc) are met at that frequency. (ca) The terminal device is receiving or will receive broadcast MRB. I am interested in at least one MBS session that has started or is about to start. They are doing it. (cb) The terminal device is receiving or will receive broadcast MRB. For at least one MBS session of interest, the SIB21 obtained from the PCell or non-serving cell contains information mapping the frequency to one or more MBS FSAIs, indicated in USD for this MBS session, or the frequency is not included in the SIB21, but this The session is shown in USD. (cc) The terminal device's capability information (e.g., UE-NR-Capability) that the terminal device notifies the network includes information on the combinations of bands the terminal device supports (e.g., supportedBandCombinationList), and at least one band combination that includes the frequency in question is included. ru.

[0153] (Determining MBS services of interest procedure) -Ja)

[0154] The terminal device is based on the fact that all of the following conditions (ca) to (cc) are met, and its MBS You may decide (determine) that the service is part of the MBS services you are interested in. (ca) The terminal device is receiving, or is interested in receiving, the MBS service via broadcast MRB. (cb) The session for that MBS service is starting or about to start ru. (cc) One or more USD (User Service Description) for that MBS service The MBS FSAI (Frequency Selection Area Identities) of the SIB21 obtained from PCell, For frequencies belonging to the set of MBS frequencies of interest, determined by the procedure for determining the MBS frequencies of interest, the SIB21 obtained from PCell is included for that MBS service While it does not provide frequency mapping information for the BBS, the USD for that MBS service includes frequencies belonging to the set of MBS frequencies of interest determined by the procedure for determining the MBS frequencies of interest.

[0155] Based on the above description, various embodiments will be explained. Note that any processes omitted in the following description may be replaced by the processes described above.

[0156] Figure 5 is a block diagram showing the configuration of the terminal device (UE122) in this embodiment. Note that, to avoid making the explanation complicated, Figure 5 shows only the main components closely related to this embodiment. To show.

[0157] The UE122 shown in Figure 5 includes a receiving unit 500 that receives control information (DCI, MAC control elements, RRC signaling, broadcast information, etc.) from the base station equipment, a processing unit 502 that processes according to the parameters contained in the received control information, and a receiving unit 502 that processes control information (DCI, MAC control elements, RRC signaling, broadcast information, etc.) from the base station equipment. The base station device includes a transmitting unit 504 that transmits (e.g., G). This base station device may be an eNB102 or a gNB108. Furthermore, the processing unit 502 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, The processing unit 502 includes a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), and an RLC layer processing unit (RLC The processing unit may include some or all of the following: the PDCP layer processing unit, the SDAP processing unit, the RRC layer processing unit, and the NAS layer processing unit.

[0158] Figure 6 is a block diagram showing the configuration of the base station equipment in this embodiment. To avoid sloppiness, Figure 6 shows only the main components closely related to this embodiment. This shows that the base station device may be eNB102 or gNB108.

[0159] The base station equipment shown in Figure 6 includes a transmitting unit 600 that transmits control information (DCI, RRC signaling, broadcast information, etc.) to UE122, and control information (DCI, RRC signaling including parameters, broadcast information, etc.) The system consists of a processing unit 602 that creates a data set and sends it to the UE122, causing the UE122's processing unit 502 to perform processing, and a receiving unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE122. The processing unit 602 also handles various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and The functions of the physical layer (and NAS layer) may be included in some or all of them. That is, the processing unit 602 includes physical layer processing The processor may include some or all of the following: the logic unit, the MAC layer processing unit, the RLC layer processing unit, the PDCP layer processing unit, the SDAP processing unit, the RRC layer processing unit, and the NAS layer processing unit.

[0160] An example of the processing of the terminal device in this embodiment will be explained using Figures 7 to 10.

[0161] Figure 7 shows an example of processing by the terminal device (UE122) in this embodiment. The processing unit 502 of the terminal device receives configuration information necessary to receive MBS services transmitted from the base station device (step 700). The configuration information received by the terminal device includes a first area information list, and the processing unit provided in the UE122 indicates that the terminal device is represented by one or more geographic area information elements included in the first area information list. After determining that it is not located within the set of geographical areas (step S702), UE122 initiates the MRB setup procedure (step S704).

[0162] The configuration information received from the base station device in step S700 is, for example, (a) below It may be any one of (a) to (c), or any combination thereof. (a) Downlink Control Information (DCI) (b) System Information Block (c) Information notified by RRC signaling

[0163] For example, the DCI of (a) may be DCI scrambled by P-RNTI with CRC. For example, the DCI of (a) may also be DCI scrambled by RNTI associated with each target area with CRC. For example, the System Information Block of (b) may be SIB1, or other SIBs. For example, the RRC signaling of (c) may be an RRC reconfiguration message, or other RRC messages.

[0164] The configuration information received from the base station device in step S700 may include one or more first area information lists, and may be composed of one or more geographical area information elements indicating one or more geographical areas. The one or more geographical area information elements indicating the geographical area may be expressed, for example, by any one of the following (a) to (d), or any combination thereof. In addition or instead, these information may be expressed as one or more lists and may be expressed as lists independently for each of the following (a) to (d), or one or more of the following (a) to (d) may be expressed in the same list. (a) An area indicated by a Reference Location (geographical coordinates indicated by longitude and latitude) and additional information ( such as radius, diameter, and / or angle, etc.) as one entry and a list including one or more entries (b) An area formed by connecting a plurality of Reference points as one entry and a list including one or more entries (c) SSB index (d) Other information indicating a geographical area Furthermore, the list of first area information included in the configuration information may include areas to be treated as the target area, or in addition to or instead of including areas to be excluded from the target area. If the list of first area information included in the configuration information is configured as information to be excluded from the target area, A set of geographical areas indicated by one or more geographical area information elements included in the list may be excluded from the target area. The scope of the target area indicated by the exclusion of the set of geographical areas from the target area may be the entire range of the cell where UE122 received the configuration information, excluding the excluded set of areas. If the first area information list is included in the configuration information together with another area information list which is configured as information that is not excluded from the target area, then the first area information list is included The target area may be a set of geographical areas indicated by one or more geographical area information elements included in the other area information list, excluding the set of geographical areas indicated by one or more geographical area information elements.

[0165] Each of the aforementioned target areas may be identified by an identifier. The identifier used to identify the target area is also called the target area identifier. The target area identifier may be included in the system information along with the information indicating the target area, or in the MCCH information, or in addition to or instead of these, in the MBSBroadcastConfiguration message. Figure 8 shows an example of the case described in (a) above. Figure 8 shows an example in which a list (MBSAreaInfoList) containing the target area identifier (TargetAreaId), the Reference Location (ReferenceLocation) indicating the target area, and radius information (mbs-DistanceRadius) is provided from the base station device to the terminal device as the configuration information.

[0166] Furthermore, for a target area to be indicated by an SSB index, it is sufficient that a certain SSB index is associated with a certain target area. For example, a terminal device may have an SSB index. If a terminal device can receive the SSB of a specific SSB, it can be considered that the terminal device is located in the target area associated with that SSB index. Furthermore, the ability to receive the SSB may be defined as the received power of that SSB being above (or exceeding) a certain threshold. This threshold may be indicated in the configuration information.

[0167] The one or more target areas notified in the aforementioned configuration information correspond to the MBS session. It's okay to be kicked.

[0168] For example, each entry in the MBS session information list included in the MBS broadcast configuration message may be associated with zero or more target areas. In this case, for example, each entry in the MBS session information list may be associated with zero or more target area identifiers. The list may include the following: In addition to or instead of the MBS session information Each entry in the list is associated with zero or more target areas. You may also include the following in addition to or instead of the MBS session information list. A G-RNTI contained in the entry may be associated with zero or more target areas. Alternatively, the PLMN contained in each entry of the MBS session information list may be associated with zero or more target areas. In addition, or alternatively, the service ID contained in each entry of the MBS session information list may be associated with zero or more target areas. Figure 9 shows an example in which a target area 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 of the MBS session information list includes TMGI and G-RNTI, and optional The entry includes a list (TargetAreaList) that contains one or more target area identifiers. This means that TargetAreaList is not included in the MBS session information list entries. It can be shown that the entry is associated with zero target areas.

[0169] For example, SIB20 includes configuration information necessary to receive one or more MCCHs. Each of the configuration pieces required to receive MCCH corresponds to zero or more target areas. It is acceptable to reject it. In this case, all MBS sessions notified by an MBS broadcast configuration message received based on the configuration information required to receive a certain MCCH will have zero or more target areas associated with the configuration information required to receive this MCCH. good.

[0170] Furthermore, one or more MBS sets are provided for each of the target areas notified in the configuration information. A session may be associated with it. In addition to or instead of that, one or more FSAIs may be associated with each of the target areas notified in the configuration information. In addition to or instead of that, one or more MBS services may be associated with each of the target areas notified in the configuration information. In addition to or instead of that, one or more MBS sessions may be associated with each of the MBS services.

[0171] One of the geographical areas included in the aforementioned first area information list Alternatively, if a set of geographical areas indicated by a list consisting of multiple geographical area information elements is indicated as "an area excluded from the target area," the terminal device determines that it is not inside the set of geographical areas and sets the MRB accordingly. You may begin the procedure. In addition to or instead of that, if it is indicated that “it is not an area excluded from the target area”, you may begin the procedure to set up the MRB based on being inside the set of geographical areas. The set of geographical areas is the target area Information to indicate whether or not an area is excluded is the entry in the first area information list. It may be expressed as a list with one-to-one correspondences in the same order as Ri, and the aforementioned target E It may be associated with a rear identifier, and may also be associated in conjunction with other information. It may be excluded, and if only that information is included, it may be treated as an excluded area. Outside of the first area information list, it is expressed together with the correspondence information. Such information may be included in the configuration information. Furthermore, if there is no set of geographic areas indicated as excluded areas among the entries of one or more geographic area information elements that indicate one or more geographic areas, the total number of entries in the list indicating whether or not an area is excluded from the target area may be 0, and the terminal device may be notified by including information indicating that there are no entries in the configuration information, or all entries in the list indicating whether or not an area is excluded from the target area may have information indicating that "it is not an area excluded from the target area".

[0172] The set of geographical areas indicated as "areas excluded from the target area" and the set of geographical areas indicated as "areas not excluded from the target area" may each be included in the aforementioned configuration information as independent lists, and each may be the first Area information list, second area information list, and in addition to or Alternatively, they may be represented in a mixed manner within the same list. In addition, or instead, information indicating whether each of the aforementioned geographical areas is an area excluded from the target area or not may be represented by bit information of 0 or 1, or by some string such as Yes or No. It may also be, in addition to or instead of that, expressed by other information capable of distinguishing the two values of "an area excluded from the target area" and "not an area excluded from the target area". It may also be expressed as one value represented in binary notation with the same number of bits as the number of entries in the list of specific geographical areas, and may be expressed by listing the identifier numbers of the identifiers of the specific geographical areas, respectively indicating excluded and non-excluded areas. When each of the set of geographical areas indicated as "an area excluded from the target area" and the set of geographical areas indicated as "not an area excluded from the target area" is included in the configuration information, the terminal device may use any one or both of these lists to determine the presence or absence of the target area and whether the terminal device is located inside or outside the target area. Based on the determination that the terminal device is located inside the target area, the terminal device may start the procedure for setting the MRB. Based on the determination that the terminal device is located inside the target area, the terminal device may start the procedure for setting the MRB.

[0173] FIG. 10 is an example of system information (SIB21) including FSAI information. The system information includes information on the list of FSAIs and an inter-frequency list including adjacent frequencies. The inter-frequency list includes a list of FSAIs assigned to the frequencies of the carrier waves. That is, the area indicated by the FSAI included in SIB21 may be specified by combining with the above-mentioned USD, and the association information may be provided to the terminal device by another system information. In addition to or instead of that, the association information may be included in SIB21.

[0174] There may also be MBS services, MBS sessions, and / or FSAIs that are not associated with any target area (that is, associated with 0 target areas).

[0175] The target area is a provider of MBS services, a network operator, or other fans ​​​It may be defined by an action, and the smallest unit may not be defined as a single cell. For example If a portion of the cell's range is defined as a range that can be set as a target area, in addition to or instead of this, information regarding the target area may be included in a system information block and communicated within the cell. The system information block may be an SIB1 or another SIB. In addition to or instead of this, the target area may be Information relating to this may be included outside the system information block, for example, as USD. It may be included as one of the parameter sets that can be transmitted to the terminal device. In addition to or instead of the above, the scope of the area may be defined based on geographical information. For example, it may be defined based on divisions such as national borders, prefectures, cities, towns, and counties; in addition to or instead of these, it may be defined based on transportation information such as roads, highways, bridges, tunnels, and railways; in addition to or instead of these, it may be defined based on topographic information such as mountains, rivers, seas, and islands; in addition to or instead of these, it may be defined based on buildings and land information. In addition to or instead of these, at least one of these definition methods may be used to define the scope of the target area. In addition to the above, Instead, it can be configured via pre-configuration without network configuration. It may be configured, and prior configuration may be done manually, and may override network settings. In addition, or instead, it may be possible to switch between network settings and other settings. Furthermore, the target area is a service area included in existing USD, etc. The information may be included as part of the information provided to the terminal device, or the target area may be provided to the terminal device as information independent of the service area information included in existing USD etc. good.

[0176] Each of the areas indicated by the service area information included in the aforementioned existing USD etc. is identified It may be identified by a child. The identifier is also called a service area identifier. The service area identifier may be transmitted to the terminal device together with the MBS service information, MBS session information, and FSAI information. For example, it may be transmitted in the system information transmitted based on the scheduling information contained in the SIB1 broadcast from the base station device, and by the SIB20. The information may be included in the MCCH message that is scheduled for transmission, or it may be included in the MBS configuration information included in the MCCH message, or it may be provided to the terminal device by other messages (e.g., NAS messages).

[0177] The MCCH message may include target area information, and in addition to or instead of that, it may include information linking to the target area information. If the terminal device receives the MCCH message and is provided with the area information, or in addition to or instead of that, information linking to the target area information, it may determine whether it is located within the target area. If it is not provided, it does not need to determine whether it is located within the target area, and in that case, it may perform the existing actions performed when an MCCH message is received as described above.

[0178] The determination in step S702 is that the terminal device is included in the first area information list. It is possible to determine that the device is not located within a set of geographical areas indicated by one or more geographical area information elements. Alternatively, it is possible to determine that the device is located within a set of geographical areas indicated by the one or more geographical area information elements. If the configuration information received by the terminal device includes information indicating whether or not to exclude it from the target area, it is possible to determine whether or not the terminal device is located within the target area by combining the set of geographical areas and the information indicating whether or not to exclude it from the target area. To determine whether the terminal device is located within the aforementioned target area, the terminal device will check if the MBS frequency it is interested in receiving is present in the FSAI list. This may involve determining that the device's location is within the target area, or, in addition to or instead of this, determining the location by comparing it with previously received service area information. The location of the terminal device itself may be determined using a known method, such as a GPS function. Location information may be obtained using, or in addition to or instead, it may be determined using tripoint positioning from the reception status of radio waves from multiple base stations, or in addition to or instead, location information may be obtained from other surrounding terminal devices, or in addition to or instead, a method such as a Kalman filter that estimates the destination based on the immediately preceding coordinate information may be used. In addition to or instead, if it is determined that the terminal device is not located inside the target area, the terminal device does not need to receive the configuration information necessary to receive the MBS, and In addition to or instead of the above, the determination receives the configuration information necessary to receive the MBS. You may discard it after doing so. Furthermore, in the determination, if both the first area information list and the second area information list are included in the configuration information, the terminal device may determine the target area by combining a set of geographical areas indicated by one or more geographical area information elements included in these lists. In this case, if the terminal device is located inside the second area Determination of whether or not it is located, and whether or not the terminal device is located outside the first area. The target area may be substantially determined by making the judgment and performing the same, and the order of the combination may be reversed.

[0179] Through the mechanism described above, the terminal device determines whether or not it can receive the configuration information necessary to receive the MBS based on whether or not its current location is within the target area. This becomes possible. Furthermore, the first area indicated as "an area excluded from the target area" The set of geographical areas indicated by a list consisting of one or more geographical area information elements indicating one or more geographical areas included in the area information list, and the set of geographical areas indicated as "areas not excluded from the target area", may be included in the configuration information, and the terminal device, If you are located within the target area, whether in one or both of the above conditions A determination of whether or not it is, and the configuration necessary to receive MBS based on the said determination. It becomes possible to decide whether or not to receive the information.

[0180] Furthermore, the above-described operation may also apply to a system in which only an area information list indicating "areas excluded from the target area" is provided to the terminal device. In this case, the terminal device provides the terminal device with the first area information indicating "areas excluded from the target area" as described above. Processing may be performed when a report list is provided. Furthermore, the above operation may also apply to a system in which only an area information list indicating "areas not excluded from the target area" is provided to the terminal device. In this case, the terminal device performs the above-mentioned processing when the first area information list indicating "areas not excluded from the target area" is provided. good.

[0181] Furthermore, "areas that are not excluded from the target area" in each embodiment may be rephrased as "areas that are the target area."

[0182] Furthermore, the above mechanism may be applied to cells in a non-terrestrial network or to cells in a terrestrial network.

[0183] In the above description, the processing unit 502 of UE122 may be a processing unit that processes the RRC layer. .

[0184] Furthermore, in each embodiment, the first area information list includes RRC messages and RRC signals. The terminal device may be notified by any or any combination of the following: a message from the upper layer of the RRC layer, a MAC control element, or downlink control information, and this also applies to the second area information list. It is permissible.

[0185] Also, in the above explanation, "link to" and "corresponding to" Expressions such as "associate with" can be used interchangeably.

[0186] Furthermore, in the above explanation, the phrases "confirmed as A," "A is set," and "A is included" are used. These expressions may be interchangeable.

[0187] In the above explanation, "transition from X to Y" can be rephrased as "become X to Y". Also, in the above explanation, "cause a transition" can be rephrased as "determine a transition".

[0188] Furthermore, in the examples of processes or process flows described above, some or all of the steps may not be executed. Also, in the examples of processes or process flows described above, the order of the steps may differ. Also, in the examples of processes or process flows described above, some or all of the processes within each step may not be executed.

[0189] Furthermore, in the above explanation, if it states "C may be D" and "C may be E," it may also include the statement "D may be E." Also, in the above explanation, if it states "F may be G" and "G may be H," it may also include the statement "F may be H."

[0190] The program running on the device according to this embodiment may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of this embodiment. The program or the information handled by the program may be temporarily loaded into volatile memory such as Random Access Memory (RAM) or flashed during processing. It is stored in non-volatile memory such as RAM or a Hard Disk Drive (HDD), and the CPU processes it as needed. This is how data is read, modified, and written.

[0191] Furthermore, some parts of the apparatus in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here refers to a computer system built into the apparatus, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of the following: a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0192] Furthermore, "computer-readable recording media" includes not only those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs over networks like the Internet or communication lines like telephone lines, but also those that hold programs for a fixed period of time, such as the volatile memory inside computer systems that act as servers or clients in such cases. That's fine. Also, the above program may be for the purpose of implementing some of the functions mentioned above, and may also be a program that already has the aforementioned functions recorded in the computer system. It is also acceptable if it can be achieved in combination with the above.

[0193] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, typically an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), and field-programmable circuits. This may include a multi-gate array (FPGA), other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, a conventional processor, controller, microcontroller, or state machine. The general-purpose processor, or each of the aforementioned circuits, may consist of digital or analog circuits. Furthermore, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, integrated circuits using such technologies may also be used.

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

[0195] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not depart from the gist of this embodiment are also included. 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. In addition, configurations in which elements described in the above embodiment that produce similar effects are substituted for each other are also included. [Explanation of symbols]

[0196] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 Interfaces 122 UE 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 unit 504, 600 Transmitter

Claims

1. A terminal device, It comprises a receiving unit that receives configuration information transmitted from the base station equipment, and a processing unit, The aforementioned configuration information includes one first area information list, The aforementioned first area information list indicates one or more geographical areas. A list composed of a number of geographical area information elements, The processing unit determines that one or more terminal devices are included in the first area information list. A terminal device that initiates the MRB configuration procedure based on the determination that it is not located within the set of geographical areas indicated by the geographical area information element.

2. A method applicable to terminal devices, The configuration information transmitted from the base station equipment includes one first area information list. The aforementioned first area information list indicates one or more geographical areas. A list composed of a number of geographical area information elements, The steps include receiving the aforementioned configuration information, The terminal device is one or more geographical areas included in the first area information list. A method comprising the steps of: determining that the location is not within a set of geographical areas indicated by an information element; and initiating an MRB setting procedure based on the determination.

3. An integrated circuit implemented in a terminal device, The configuration information transmitted from the base station equipment includes one first area information list. The aforementioned first area information list indicates one or more geographical areas. A list composed of a number of geographical area information elements, A function for receiving the aforementioned configuration information, The terminal device is one or more geographical areas included in the first area information list. A function that determines whether an object is located within the set of geographical areas indicated by the information element, An integrated circuit that enables the terminal device to perform the function of initiating the MRB setting procedure based on the aforementioned determination. 。

Images