[go: up one dir, main page]

WO2025197209A1 - Équipement terminal, procédé et circuit intégré - Google Patents

Équipement terminal, procédé et circuit intégré

Info

Publication number
WO2025197209A1
WO2025197209A1 PCT/JP2024/043410 JP2024043410W WO2025197209A1 WO 2025197209 A1 WO2025197209 A1 WO 2025197209A1 JP 2024043410 W JP2024043410 W JP 2024043410W WO 2025197209 A1 WO2025197209 A1 WO 2025197209A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
rrc
mbs
information
multicast
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2024/043410
Other languages
English (en)
Japanese (ja)
Inventor
秀和 坪井
昇平 山田
恭輔 井上
拓真 河野
太一 三宅
昂生 野村
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sharp Corp filed Critical Sharp Corp
Publication of WO2025197209A1 publication Critical patent/WO2025197209A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present invention relates to a terminal device, a method, and an integrated circuit.
  • 3GPP 3rd Generation Partnership Project
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • RAT Radio Access Technology
  • 3GPP is currently conducting technical studies and standardization of E-UTRA extension technologies.
  • E-UTRA is also known as Long Term Evolution (LTE: registered trademark), and the extension technologies are sometimes referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
  • NR New Radio, or NR Radio access
  • RAT radio access technology
  • 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 3GPP RP-234078," New WID: Non-Terrestrial Networks (NTN) forNR Phase 3", ⁇ https://www.3gpp.org/ftp/tsg_ran/TSG_RAN/TSGR_102/Docs/RP-234078.zip>
  • Non-Patent Document 2 the provision of multicast/broadcast services is being considered as an extension technology of NR, for example, in the study of non-terrestrial networks (NTN).
  • NTN non-terrestrial networks
  • Non-Patent Document 2 the size of a cell provided by a satellite is larger than that of a cell in a terrestrial network, it may be difficult to provide broadcast services to a specific area (for example, within a country or state)
  • One aspect of the present invention was made in consideration of the above-mentioned circumstances, and one of its objectives is to provide a terminal device, base station device, communication method, and integrated circuit that can efficiently provide multicast/broadcast services.
  • one aspect of the present invention provides the following: Specifically, one aspect of the present invention provides a terminal device communicating with a base station device, the terminal device comprising: a receiver that receives from the base station device an RRC release message including control information related to one or more multicast broadcast services (MBS) and one or more pieces of area information; and a processor, wherein the control information includes information associating some or all of the multicast sessions with one or more pieces of area information, each piece of area information indicating some or all of the regions in which the multicast sessions are provided.
  • MMS multicast broadcast services
  • the processor in an RRC_INACTIVE state, transmits an RRC resumption request message to the base station device to resume the RRC connection based on the fact that, in a cell after cell reselection, PTM configuration for a multicast session in which the terminal device is participating and that does not indicate that monitoring of the G-RNTI in question is to be stopped is unavailable, and the terminal device is located in an area notified by the area information associated with a multicast session in which the terminal device is participating and that does not indicate that monitoring of the G-RNTI in question is to be stopped.
  • Another aspect of the present invention is a method applied to a terminal device communicating with a base station device, comprising the steps of: receiving an RRC release message from the base station device, the RRC release message including control information related to one or more multicast broadcast services (MBS) and one or more pieces of area information; and, in an RRC_INACTIVE state, transmitting an RRC resumption request message to the base station device to resume the RRC connection based on the fact that, in a cell after cell reselection, PTM configuration for a multicast session in which the terminal device is participating and that does not indicate that monitoring of the G-RNTI in the multicast session is stopped is not available and the terminal device is located in an area notified by the area information associated with the participating multicast session in which monitoring of the G-RNTI in the multicast session is not indicated to be stopped, wherein the control information includes information associating some or all of the multicast sessions with one or more pieces of area information, and each piece of area information indicates some or all of the areas in which the multicast sessions
  • Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, which causes the terminal device to perform the following functions: receive an RRC release message including control information related to one or more multicast broadcast services (MBS) provided in the cell of the base station device and one or more pieces of area information; and, in an RRC_INACTIVE state, transmit an RRC resumption request message to the base station device to resume the RRC connection based on the fact that, in a cell after cell reselection, PTM configuration for a multicast session in which the terminal device is participating and that does not indicate that monitoring of the G-RNTI is to be stopped is unavailable, and the terminal device is located in an area notified by the area information associated with the multicast session in which the terminal device is participating and that does not indicate that monitoring of the G-RNTI is to be stopped; the control information includes information associating some or all of the multicast sessions with one or more pieces of area information, and each piece of area information is information indicating the area of some or all of
  • a terminal device, method, and integrated circuit can achieve efficient communication control processing.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of an E-UTRA protocol configuration according to the present embodiment.
  • FIG. 1 is a diagram illustrating an example of an NR protocol configuration according to this embodiment.
  • FIG. 10 is a diagram showing an example of a flow of procedures for various settings in RRC according to the present embodiment.
  • FIG. 2 is a block diagram showing the configuration of a terminal device according to the embodiment.
  • FIG. 2 is a block diagram showing the configuration of a base station device according to the present embodiment.
  • 10 shows an example of processing in this embodiment. 3 shows an example of an ASN.1 description of area information in this embodiment.
  • 10 is an example of an ASN.1 description of a system information block in this embodiment.
  • 10 shows an example of an ASN.1 description of an MBS broadcast setting in this embodiment.
  • LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (Radio Access Technologies: RATs).
  • LTE that can connect to NR via Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE.
  • LTE that uses 5GC for the core network (Core Network: CN) may be distinguished from conventional LTE that uses EPC for the core network.
  • Conventional LTE may refer to LTE that does not implement technologies standardized in 3GPP Release 15 or later.
  • This embodiment may be applied to NR, LTE, and other RATs.
  • the following explanation uses terms related to LTE and NR, but this embodiment may also be applied to technologies that use other terms and/or other radio access technologies.
  • E-UTRA and LTE may be used interchangeably.
  • this embodiment describes the names of each node and entity, and the processing of each node and entity when the radio access technology is E-UTRA or NR, but this embodiment may be applied to other radio access technologies.
  • the names of each node and entity, and the names of parameters and messages in this embodiment may be different from those described in this embodiment.
  • Figure 1 is a schematic diagram of a communications system according to this embodiment. Note that the functions of each node, radio 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 included.
  • E-UTRA100 may be a radio access technology. E-UTRA100 may also be the air interface between UE122 and eNB102. The air interface between UE122 and eNB102 may be referred to as the Uu interface.
  • eNB (E-UTRAN Node B) 102 may be a base station device for E-UTRA100. eNB102 may have the E-UTRA protocol described below.
  • the E-UTRA protocol may be composed of the E-UTRA user plane (User Plane: UP) protocol described below and the E-UTRA control plane (Control Plane: CP) protocol described below.
  • eNB102 may terminate the E-UTRA user plane (User Plane: UP) protocol and the E-UTRA control plane (Control Plane: CP) protocol for UE122.
  • E-UTRAN E-UTRA user plane
  • CP Control Plane
  • a radio access network composed of eNBs may be referred to as E-UTRAN.
  • EPC (Evolved Packet Core) 104 may be a core network.
  • Interface 112 is an interface between eNB 102 and EPC 104, and may be referred to as an 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.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • the control plane interface of interface 112 may be referred to as an S1-MME interface.
  • the user plane interface of interface 112 may be referred to as an S1-U interface.
  • one or more eNBs 102 may be connected to the EPC 104 via an interface 112.
  • An interface (not shown) may exist between the multiple eNBs 102 connected to the EPC 104.
  • the interface between the multiple eNBs 102 connected to the EPC 104 may be referred to as an X2 interface.
  • NR106 may be a radio access technology.
  • NR106 may also be the air interface between UE122 and gNB108.
  • the air interface between UE122 and gNB108 may be referred to as the Uu interface.
  • gNB (g Node B) 108 may be the base station equipment of NR106.
  • gNB108 may have the NR protocol described below.
  • the NR protocol may consist of the NR user plane (User Plane: UP) protocol described below and the NR control plane (Control Plane: CP) protocol described below.
  • gNB108 may terminate the NR user plane (User Plane: UP) protocol and the NR control plane (Control Plane: CP) protocol for UE122.
  • 5GC110 may be a core network.
  • Interface 116 is an interface between gNB108 and 5GC110, and may be referred to as an NG interface.
  • Interface 116 may have a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
  • the control plane interface of interface 116 may terminate at an Access and Mobility Management Function (AMF: not shown) within 5GC110.
  • AMF Access and Mobility Management Function
  • the user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC110.
  • the control plane interface of interface 116 may be referred to as an NG-C interface.
  • the user plane interface of interface 116 may be referred to as an NG-U interface.
  • one or more gNBs 108 may be connected to 5GC 110 via interface 116.
  • An interface may exist between multiple gNBs 108 connected to 5GC 110 (not shown).
  • the interface between multiple gNBs 108 connected to 5GC 110 may be referred to as an Xn interface.
  • the eNB102 may have the ability to connect to the 5GC110.
  • the eNB102 with the ability to connect to the 5GC110 may be referred to as an ng-eNB.
  • the interface 114 is an interface between the eNB102 and the 5GC110 and may be referred to as an NG interface.
  • the interface 114 may have a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
  • the control plane interface of the interface 114 may terminate at the AMF within the 5GC110.
  • the user plane interface of the interface 114 may terminate at the UPF within the 5GC110.
  • the control plane interface of the interface 114 may be referred to as an NG-C interface.
  • the user plane interface of the interface 114 may be referred to as an NG-U interface.
  • a radio access network consisting of an ng-eNB or a gNB may be referred to as an NG-RAN.
  • the NG-RAN, E-UTRAN, etc. may simply be referred to as a network.
  • the network may include an eNB, ng-eNB, gNB, etc.
  • one or more eNB102 may be connected to 5GC110 via interface 114.
  • An interface may exist between multiple eNB102 connected to 5GC110 (not shown).
  • the interface between multiple eNB102 connected to 5GC110 may be called an Xn interface.
  • an eNB102 connected to 5GC110 and a gNB108 connected to 5GC110 may be connected via interface 120.
  • the interface 120 between an eNB102 connected to 5GC110 and a gNB108 connected to 5GC110 may be called an Xn interface.
  • the gNB108 may have the ability to connect to the EPC104.
  • a gNB108 with the ability to connect to the EPC104 may be referred to as an en-gNB.
  • Interface 118 is an interface between the gNB108 and the EPC104 and may be referred to as an S1 interface.
  • Interface 118 may have a user plane interface through which user data passes.
  • the user plane interface of interface 118 may terminate at an S-GW (not shown) within the EPC104.
  • the user plane interface of interface 118 may be referred to as an S1-U interface.
  • the eNB102 connecting to the EPC104 and the gNB108 connecting to the EPC104 may be connected by interface 120.
  • Interface 120 between the eNB102 connecting to the EPC104 and the gNB108 connecting to the EPC104 may be referred to as an X2 interface.
  • Interface 124 is an interface between EPC 104 and 5GC 110, and may be an interface that passes only CP, only UP, or both CP and UP. Furthermore, some or all of interfaces such as interface 114, interface 116, interface 118, interface 120, and interface 124 may not exist depending on the communication system provided by the telecommunications carrier, etc.
  • 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. UE122 may also be a terminal device capable of simultaneously establishing a wireless connection with eNB102 and a wireless connection with gNB108. UE122 may have the E-UTRA protocol and/or the NR protocol.
  • the wireless connection may be a Radio Resource Control (RRC) connection.
  • RRC Radio Resource Control
  • UE122 may be a terminal device capable of connecting to EPC104 and/or 5GC110 via eNB102 and/or gNB108. If the core network to which eNB102 and/or gNB108, with which UE122 communicates, is connected is EPC104, each Data Radio Bearer (DRB) described below established between UE122 and eNB102 and/or gNB108 may further be uniquely linked to each EPS (Evolved Packet System) bearer passing through EPC104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.
  • EPS bearer Evolved Packet System
  • each DRB established between UE122 and eNB102 and/or gNB108 may be further linked to one of the PDU (Packet Data Unit) sessions established within 5GC110.
  • PDU Packet Data Unit
  • One or more QoS flows may exist in each PDU session.
  • Each DRB may be mapped to one or more QoS flows, or 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 be identified by a QoS flow identifier (Identity, or ID).
  • the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.
  • PDU sessions and/or QoS flows may not exist in EPC104.
  • EPS bearers may not exist in 5GC110.
  • UE122 When UE122 is connected to EPC104, UE122 has information about EPS bearers, but may not have information about PDU sessions and/or QoS flows. Also, when UE122 is connected to 5GC110, UE122 has information about PDU sessions and/or QoS flows, but may not have information about EPS bearers.
  • eNB102 and/or gNB108 will also be referred to simply as base station devices, and UE122 will also be referred to simply as terminal device or UE.
  • 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 the functions of each protocol described using Figure 2 and/or Figure 3 are only some of the functions closely related to this embodiment, and other functions may also be included.
  • the uplink (UL) may be a link from the terminal device to the base station device.
  • the downlink (DL) may be a link from the base station device to the terminal device.
  • the sidelink (SL) may be a link from the terminal device to the terminal device that does not go through the base station device.
  • FIG 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack.
  • the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol that terminates at the eNB 102 on the network side.
  • the E-UTRA user plane protocol stack may be composed of a PHY (Physical layer) 200, which is the radio physical layer, a MAC (Medium Access Control) 202, which is the medium access control layer, a RLC (Radio Link Control) 204, which is the radio link control layer, and a PDCP (Packet Data Convergence Protocol) 206, which is the packet data convergence protocol layer.
  • PHY Physical layer
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • Figure 3(A) is a diagram of the NR user plane (UP) protocol stack.
  • the NRUP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side.
  • the NR user plane protocol stack may be composed of a radio physical layer, PHY 300, a medium access control layer, MAC 302, a radio link control layer, RLC 304, a packet data convergence protocol layer, PDCP 306, and a service data adaptation protocol layer, SDAP (Service Data Adaptation Protocol) 310.
  • PHY 300 a radio physical layer
  • MAC 302 medium access control layer
  • RLC 304 radio link control layer
  • PDCP 306 Packet Control Protocol
  • SDAP Service Data Adaptation Protocol
  • FIG. 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration.
  • RRC Radio Resource Control
  • NAS Non Access Stratum
  • NAS 210 which is the non-AS (Access Stratum) layer
  • NAS 210 may be a protocol that terminates at MME on the network side.
  • Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration.
  • RRC308 which is the radio resource control layer
  • RRC308 may be a protocol that terminates at gNB108 on the network side.
  • NAS312 which is the non-AS layer
  • NAS312 may be a protocol that terminates at AMF on the network side.
  • the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and/or the gNB 108.
  • the AS layer may be a layer that includes some or all of the PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208, and/or a layer that includes some or all of the PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308.
  • PHY PHY layer
  • MAC MAC layer
  • RLC RLC layer
  • PDCP PDCP layer
  • RRC RRC layer
  • NAS NAS layer
  • PHY PHY layer
  • MAC MAC layer
  • RLC RLC layer
  • PDCP PDCP layer
  • RRC RRC layer
  • NAS NAS layer
  • PHY PHY layer
  • MAC MAC layer
  • RLC RLC layer
  • PDCP layer PDCP layer
  • RRC RRC layer
  • NAS NAS layer
  • the SDAP SDAP layer
  • SDAP layer may also be the SDAP (SDAP layer) of the NR protocol.
  • PHY200, MAC202, RLC204, PDCP206, and RRC208 may be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively.
  • PHY200, MAC202, RLC204, PDCP206, and RRC208 may also be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively.
  • PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively.
  • PHY300, MAC302, RLC304, PDCP306, and RRC308 may also be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.
  • An entity that has some or all of the functions of the MAC layer may be called a MAC entity.
  • An entity that has some or all of the functions of the RLC layer may be called an RLC entity.
  • An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity.
  • An entity that has some or all of the functions of the SDAP layer may be called an SDAP entity.
  • An entity that has some or all of the functions of the RRC layer may be called an RRC entity.
  • the MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.
  • MAC PDU Protocol Data Unit
  • RLC PDU Packet Data Unit
  • PDCP PDU Packet Data Unit
  • SDAP PDU Serial Protocol Data Unit
  • data provided from higher layers to MAC, RLC, PDCP, and SDAP, and/or data provided from MAC, RLC, PDCP, and SDAP to higher layers may be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively.
  • segmented RLC SDUs may be referred to as RLC SDU segments.
  • the base station device and the terminal device exchange (transmit and receive) signals at a higher layer.
  • the higher layer may also be referred to as the upper layer, and the terms may be interchangeable.
  • the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC signaling) at the Radio Resource Control (RRC) layer.
  • RRC Radio Resource Control
  • the base station device and the terminal device may also transmit and receive MAC control elements at the Medium Access Control (MAC) layer.
  • the RRC layer of the terminal device also acquires system information broadcast from the base station device.
  • the RRC message, system information, and/or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters).
  • each of the parameters included in the higher layer signals received by the terminal device may be referred to as a higher layer parameter.
  • an upper layer means a layer higher than 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.
  • an upper layer may refer to one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.
  • the meanings of "A is given (provided) by an upper layer” and “A is given (provided) by an upper layer” may mean that an upper layer (mainly the RRC layer, MAC layer, etc.) of a terminal device receives A from a base station device, and the received A is given (provided) from the upper layer of the terminal device to a lower layer (mainly the MAC layer or physical layer) of the terminal device.
  • “upper layer parameters are provided” may mean that an upper layer signal is received from a base station device, and the upper layer parameters included in the received upper layer signal are provided from the upper layer of the terminal device to the lower layer of the terminal device.
  • Setting upper layer parameters in a terminal device may mean that the upper layer parameters are given (provided) to the terminal device.
  • setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from a base station device, and the received upper layer parameters are set in the upper layer.
  • setting upper layer parameters in a terminal device may also include setting default parameters that have been given in advance to the upper layer of the terminal device.
  • the expression "submitting a message from the terminal device's RRC entity to a lower layer” is sometimes used.
  • "submitting a message to a lower layer” from the RRC entity may mean submitting a message to the PDCP layer.
  • "submitting a message to a lower layer” from the RRC layer may mean submitting a message to the PDCP entity corresponding to each SRB, since RRC messages are transmitted using SRBs (SRB0, SRB1, SRB2, SRB3, etc.).
  • the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.
  • the PHY of the terminal device may have the function of receiving data transmitted from the PHY of the base station device via the downlink (DL) physical channel.
  • the PHY of the terminal device may have the function of transmitting data to the PHY of the base station device via the uplink (UL) physical channel.
  • the PHY may be connected to the upper MAC via a transport channel.
  • the PHY may pass data to the MAC via the transport channel.
  • the PHY may also be provided with data from the MAC via the transport channel.
  • an RNTI Radio Network Temporary Identifier
  • the physical channels used for wireless communication between terminal devices and base station devices may include the following physical channels:
  • 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
  • PBCH may be used to broadcast system information required by terminal devices.
  • the PBCH may be used to broadcast the time index (SSB-Index) within the period of a synchronization signal block (SSB).
  • SSB-Index time index within the period of a synchronization signal block
  • the PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device).
  • DCI downlink control information
  • one or more DCIs (which may also be referred to as DCI formats) may be defined for transmitting the downlink control information. That is, a field for the downlink control information may be defined as DCI and mapped to information bits.
  • the PDCCH may be transmitted in PDCCH candidates.
  • the terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format.
  • the terminal device may monitor the PDCCH candidates in configured monitoring occasions in one or more configured control resource sets (CORESETs) configured by search space configuration.
  • the DCI format may be used for scheduling the PUSCH in the serving cell.
  • PUSCH may be used to transmit user data and RRC messages, which will be described later.
  • the PUCCH may be used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device).
  • the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel.
  • CSI Channel State Information
  • the uplink control information may also include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources.
  • SR Scheduling Request
  • UL-SCH Uplink Shared CHannel
  • the uplink control information may also include a HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).
  • PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer.
  • DL-SCH Downlink Shared CHannel
  • PDSCH may also be used to transmit system information (SI: System Information) and random access response (RAR: Random Access Response).
  • SI System Information
  • RAR Random Access Response
  • PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or HARQ-ACK and/or CSI together with uplink data. PUSCH may also be used to transmit only CSI, or only HARQ-ACK and CSI. In other words, PUSCH may be used to transmit only UCI. PDSCH or PUSCH may also be used to transmit RRC messages and MAC CE, which will be described later.
  • RRC messages transmitted from a base station device may be signaling common to multiple terminal devices within a cell.
  • RRC messages transmitted from a base station device may also be signaling dedicated to a certain terminal device.
  • terminal device-specific information (UE-specific) may be transmitted using signaling dedicated to a certain terminal device.
  • PUSCH may also be used to transmit UE capabilities in the uplink.
  • the PRACH may be used to transmit a random access preamble.
  • the PRACH may also be used for initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmissions, and to indicate requests for UL-SCH resources.
  • MAC may also be called a MAC sublayer.
  • MAC may have the function of mapping various logical channels to corresponding transport channels.
  • Logical channels may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID).
  • Logical Channel ID Logical Channel ID
  • MAC may be connected to a higher-level RLC via a logical channel.
  • logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information.
  • 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 have the function of demultiplexing MAC PDUs provided by the PHY and providing them to a higher layer via the logical channel to which each MAC SDU belongs. MAC may also have the function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a scheduling report function that reports scheduling information. The MAC may also have a function to perform priority processing between terminal devices using dynamic scheduling. The MAC may also have a function to perform priority processing between logical channels within one terminal device. The MAC may also have a function to perform priority processing of overlapping resources within one terminal device. The MAC may also have a function to identify Multimedia Broadcast Multicast Services (MBMS).
  • MBMS Multimedia Broadcast Multicast Services
  • the NR MAC may also have a function to identify Multicast/Broadcast Services (MBS).
  • the MAC may have a function to select a transport format.
  • the MAC may have functions such as discontinuous reception (DRX) and/or discontinuous transmission (DTX), a function to execute random access (RA) procedures, a power headroom report (PHR) function to notify information on the transmit power available, and a buffer status report (BSR) function to notify information on the amount of data in the transmit buffer.
  • DRX discontinuous reception
  • DTX discontinuous transmission
  • PHR power headroom report
  • BSR buffer status report
  • the NR MAC may have a bandwidth adaptation (BA) function.
  • BA bandwidth adaptation
  • the MAC PDU format used in the E-UTRA MAC may differ from the MAC PDU format used in the NR MAC.
  • the MAC PDU may also include a MAC control element (MAC CE), which is an element for performing control in the MAC.
  • MAC CE MAC control element
  • This section describes the uplink (UL) and/or downlink (DL) logical channels used in E-UTRA and/or NR.
  • the BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information such as system information (SI).
  • SI system information
  • PCCH Packet Control Channel
  • PCCH Packet Control Channel
  • the CCCH may be a logical channel for transmitting control information between a terminal device and a base station device.
  • the CCCH may be used when the terminal device does not have an RRC connection.
  • the CCCH may also be used between a base station device and multiple terminal devices.
  • the DCCH (Dedicated Control Channel) may be a logical channel for transmitting dedicated control information bidirectionally, point-to-point, between a terminal device and a base station device.
  • the dedicated control information may be control information dedicated to each terminal device.
  • the DCCH may be used when the terminal device has an RRC connection.
  • DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data point-to-point between a terminal device and a base station device.
  • DTCH may be a logical channel for transmitting dedicated user data.
  • Dedicated user data may be user data dedicated to each terminal device.
  • DTCH may exist on both the uplink and downlink.
  • the MCCH may be a point-to-multipoint downlink channel for transmitting MBMS control information for one or more MTCHs from a base station device to a terminal device.
  • the MCCH may be a multicast and/or broadcast logical channel.
  • the MCCH may carry the MBS broadcast configuration provided in the cell from which the MCCH is transmitted.
  • MTCH Multicast Traffic Channel
  • MTCH may be a point-to-multipoint downlink channel for transmitting data from a base station device to a terminal device.
  • MTCH may be a logical channel for multicast and/or broadcast.
  • This section describes the mapping of logical channels and transport channels for the uplink in E-UTRA and/or NR.
  • the CCCH may be mapped to the uplink transport channel, UL-SCH (Uplink Shared Channel).
  • UL-SCH Uplink Shared Channel
  • the DCCH may be mapped to the uplink transport channel, UL-SCH (Uplink Shared Channel).
  • UL-SCH Uplink Shared Channel
  • DTCH may be mapped to the uplink transport channel, UL-SCH (Uplink Shared Channel).
  • UL-SCH Uplink Shared Channel
  • This section describes the mapping of logical channels and transport channels for the downlink in E-UTRA and/or NR.
  • the BCCH may be mapped to the downlink transport channel BCH (Broadcast Channel) and/or DL-SCH (Downlink Shared Channel).
  • BCH Broadcast Channel
  • DL-SCH Downlink Shared Channel
  • the PCCH may be mapped to the PCH (Paging Channel), which is a downlink transport channel.
  • PCH Packet Control Channel
  • the CCCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • the DCCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • DTCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • the MCCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • the MTCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • RLC may also be called an RLC sublayer.
  • E-UTRA RLC may have the function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer.
  • E-UTRA RLC may have the function of reassembling and reordering data provided from the lower layer and providing it to the upper layer.
  • NR RLC may have the function of adding a sequence number independent of the sequence number added by PDCP to data provided from the upper layer PDCP.
  • NR RLC may also have the function of segmenting data provided from PDCP and providing it to the lower layer.
  • NR RLC may also have the function of reassembling data provided from the lower layer and providing it to the upper layer.
  • RLC may also have the function of data retransmission and/or retransmission request (Automatic Repeat reQuest: ARQ). RLC may also have the ability to perform error correction using ARQ.
  • the control information sent from the receiving side of RLC to the transmitting side to indicate data that needs to be retransmitted in order to perform ARQ may be called a status report.
  • the instruction to send a status report sent from the transmitting side of RLC to the receiving side may be called a poll.
  • RLC may also have the ability to detect data duplication.
  • RLC may also have the ability to discard data.
  • RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM).
  • TM data received from upper layers is not segmented and an RLC header does not need to be added.
  • the TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity.
  • UM the division and/or concatenation of data received from a higher layer, the addition of RLC headers, etc. are performed, but data retransmission control is not required.
  • a UM RLC entity may be a unidirectional entity or a bidirectional entity. If the UM RLC entity is a unidirectional entity, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity.
  • the UM RLC entity is a bidirectional entity, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.
  • AM the division and/or concatenation of data received from a higher layer, the addition of RLC headers, data retransmission control, etc. are performed.
  • An AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side.
  • data provided to a lower layer in TM and/or data provided by a lower layer may be called a TMD PDU.
  • data provided to a lower layer in UM and/or data provided from a lower layer may be called a UMD PDU.
  • RLC PDU data provided to a lower layer in AM and/or data provided from a lower layer may be called an AMD PDU.
  • the RLC PDU format used in E-UTRA RLC may differ from the RLC PDU format used in NR RLC.
  • RLC PDUs may include data RLC PDUs and control RLC PDUs.
  • Data RLC PDUs may be called RLC DATA PDUs (RLC Data PDUs).
  • Control RLC PDUs may be called RLC CONTROL PDUs (RLC Control PDUs).
  • PDCP may be called the PDCP sublayer.
  • PDCP may have a function for maintaining sequence numbers.
  • PDCP may also have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over wireless sections.
  • the protocol used for IP packet header compression/decompression may be called the ROHC (Robust Header Compression) protocol.
  • the protocol used for Ethernet frame header compression/decompression may be called the EHC (Ethernet (registered trademark) Header Compression) protocol.
  • PDCP may also have data encryption/decryption functionality.
  • PDCP may also have data integrity protection/verification functionality.
  • PDCP may also have a re-ordering function.
  • PDCP may also have a PDCP SDU retransmission function.
  • PDCP may also have a data discard function using a discard timer.
  • PDCP may also have a duplication function.
  • PDCP may also have a function to discard duplicated received data.
  • a PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity.
  • the PDCP PDU format used in E-UTRA PDCP may differ from the PDCP PDU format used in NR PDCP.
  • PDCP PDUs may include data PDCP PDUs and control PDCP PDUs.
  • Data PDCP PDUs may be called PDCP DATA PDUs (PDCP Data PDUs).
  • Control PDCP PDUs may be called PDCP CONTROL PDUs (PDCP Control PDUs).
  • SDAP is a service data adaptation protocol layer.
  • SDAP may have the function of mapping the downlink QoS flow sent from 5GC110 to the terminal device via the base station device to a data radio bearer (DRB), and/or the function of mapping the uplink QoS flow sent from the terminal device to 5GC110 via the base station device to a DRB.
  • SDAP may also have the function of storing mapping rule information.
  • SDAP may also have the function of marking the QoS flow identifier (QoS Flow ID: QFI).
  • SDAP PDUs may include data SDAP PDUs and control SDAP PDUs.
  • Data SDAP PDUs may be called SDAP DATA PDUs (SDAP Data PDUs, SDAP Data PDUs).
  • Control SDAP PDUs may be called SDAP CONTROL PDUs (SDAP Control PDUs, SDAP Control PDUs).
  • SDAP CONTROL PDUs SDAP CONTROL PDUs (SDAP Control PDUs, SDAP Control PDU
  • RRC may have a broadcast function.
  • RRC may have a paging function from EPC104 and/or 5GC110.
  • RRC may have a paging function from eNB102 connected to gNB108 or 5GC110.
  • RRC may also have an RRC connection management function.
  • RRC may also have a radio bearer control function.
  • RRC may also have a cell group control function.
  • RRC may also have a mobility control function.
  • RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions.
  • RRC may also have a QoS management function.
  • RRC may also have a radio link failure detection and recovery function.
  • RRC may use RRC messages to perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. Note that the RRC messages and parameters used in E-UTRA RRC may differ from the RRC messages and parameters used in NR RRC.
  • RRC messages may be sent using the logical channel BCCH. Additionally or alternatively, RRC messages may be sent using the logical channel PCCH. Additionally or alternatively, RRC messages may be sent using the logical channel CCCH. Additionally or alternatively, RRC messages may be sent using the logical channel DCCH. Additionally or alternatively, RRC messages may be sent using the logical channel MCCH. RRC messages sent using the DCCH are also referred to as dedicated RRC signaling or RRC signaling.
  • RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), various types of System Information Blocks (SIB), or other RRC messages.
  • RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.
  • RRC messages sent in the uplink (UL) direction using CCCH may include, for example, an RRC setup request message (RRC Setup Request), an RRC resume request message (RRC Resume Request), an RRC reestablishment request message (RRC Reestablishment Request), an RRC system information request message (RRC System Info Request), etc. They may also include, for example, an RRC connection request message (RRC Connection Request), an RRC connection resume request message (RRC Connection Resume Request), an RRC connection reestablishment request message (RRC Connection Reestablishment Request), etc. They may also include other RRC messages.
  • RRC messages sent in the downlink (DL) direction using CCCH may include, for example, an RRC connection reject message (RRC Connection Reject), an RRC connection setup message (RRC Connection Setup), an RRC connection reestablishment message (RRC Connection Reestablishment Reject), an RRC connection reestablishment rejection message (RRC Connection Reestablishment Reject), etc. They may also include, for example, an RRC reject message (RRC Reject), an RRC setup message (RRC Setup), etc. They may also include other RRC messages.
  • RRC signaling sent in the uplink (UL) direction using DCCH may include, for example, a measurement report message (Measurement Report), an RRC connection reconfiguration complete message (RRC Connection Reconfiguration Complete), an RRC connection setup complete message (RRC Connection Setup Complete), an RRC connection reestablishment complete message (RRC Connection Reestablishment Complete), a security mode complete message (Security Mode Complete), and a UE capability information message (UE Capability Information).
  • Measurement Report Measurement Report
  • RRC Connection Reconfiguration Complete RRC connection reconfiguration Complete
  • RRC Connection Setup Complete RRC connection setup complete message
  • RRC Connection reestablishment complete RRC Connection Reestablishment Complete
  • a security mode complete message Security Mode Complete
  • UE Capability Information UE Capability Information
  • RRC signaling sent in the downlink (DL) direction using the DCCH may include, for example, an RRC connection reconfiguration message (RRC Connection Reconfiguration), an RRC connection release message (RRC Connection Release), a security mode command message (Security Mode Command), a UE capability enquiry message (UE Capability Enquiry), etc. It may also include, for example, an RRC reconfiguration message (RRC Reconfiguration), an RRC resume message (RRC Resume), an RRC release message (RRC Release), an RRC reestablishment message (RRC Reestablishment), a security mode command message (Security Mode Command), a UE capability enquiry message (UE Capability Enquiry), etc. It may also include other RRC signaling.
  • RRC messages sent in the downlink (DL) direction using the MCCH may include, for example, an MBS broadcast configuration message (MBSBroadcastConfiguration message). They may also include other RRC signaling.
  • MBSBroadcastConfiguration message MBS broadcast configuration message
  • the NAS may have authentication functionality.
  • the NAS may also have mobility management functionality.
  • the NAS may also have security control functionality.
  • UE122 connected to EPC or 5GC may be in the RRC_CONNECTED state when the RRC connection has been established.
  • the state in which the RRC connection is established may include a state in which UE122 holds some or all of the UE context described below.
  • the state in which the RRC connection is established may also include a state in which UE122 is able to send and/or receive unicast data.
  • UE122 may be in the RRC_INACTIVE state when the RRC connection is suspended.
  • UE122 may be in the RRC_INACTIVE state when UE122 is connected to 5GC and the RRC connection is suspended.
  • UE122 may be in the RRC_IDLE state when UE122 is neither in the RRC_CONNECTED state nor the RRC_INACTIVE state.
  • UE122 when UE122 is connected to the EPC, it does not have the RRC_INACTIVE state, but E-UTRAN may initiate suspension of the RRC connection.
  • UE122 When UE122 is connected to the EPC and the RRC connection is suspended, UE122 may transition to the RRC_IDLE state, retaining the UE's AS context and the identifier (resumeIdentity) used for resumption.
  • a layer above the RRC layer of UE122 e.g., the NAS layer
  • dormancy may be different for UE122 connected to EPC104 and UE122 connected to 5GC110. Furthermore, some or all of the procedures for UE122 to return from dormancy may be different when UE122 is connected to EPC (when UE122 is dormant in RRC_IDLE state) and when UE122 is connected to 5GC (when UE122 is dormant in RRC_INACTIVE state).
  • the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may also be referred to as the connected state (connected mode), inactive state (inactive mode), and idle state (idle mode), respectively, or as the RRC connected state (RRC connected mode), RRC inactive state (RRC inactive mode), and RRC idle state (RRC idle mode).
  • the UE AS context held by UE122 may be information including all or part of the current RRC settings, current security context, PDCP state including ROHC (RObust Header Compression) state, C-RNTI (Cell Radio Network Temporary Identifier) used in the source PCell, cell identifier, and physical cell identifier of the source PCell.
  • PDCP state including ROHC (RObust Header Compression) state
  • C-RNTI Cell Radio Network Temporary Identifier
  • the UE AS context held by either or all of eNB102 and gNB108 may include the same information as the UE AS context held by UE122, or may include information different from the information contained in the UE AS context held by UE122.
  • the security context may be information that includes all or part of the following: an AS-level encryption key, a Next Hop parameter (NH), a Next Hop Chaining Counter parameter (NCC) used to derive the next-hop access key, an identifier for the selected AS-level encryption algorithm, and a counter used for replay protection.
  • an AS-level encryption key a Next Hop parameter (NH), a Next Hop Chaining Counter parameter (NCC) used to derive the next-hop access key, an identifier for the selected AS-level encryption algorithm, and a counter used for replay protection.
  • NH Next Hop parameter
  • NCC Next Hop Chaining Counter parameter
  • the serving cell may be composed of one primary cell (PCell).
  • multiple serving cells may refer to a set of multiple cells (set of cell(s)) consisting of one or more special cells (SpCells) and all one or more secondary cells (SCells).
  • the SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may be always activated.
  • the PCell may be the cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state.
  • the PCell may also be the cell used in the RRC connection re-establishment procedure in which the terminal device re-establishes the RRC connection.
  • the PCell may also be a cell used for the random access procedure during handover.
  • the PSCell may also be a cell used for the random access procedure when adding a secondary node, as described below.
  • the SpCell may also be a cell used for purposes other than those mentioned above.
  • CA carrier aggregation
  • a cell group may consist of one SpCell.
  • a cell group may also consist of one SpCell and one or more SCells.
  • a cell group may consist of one SpCell and, optionally, one or more SCells.
  • a cell group may also be expressed as a set of cells (set of cell(s)).
  • Dual Connectivity may be a technology for performing data communication using the radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node).
  • first base station device first node
  • second base station device second node
  • a cell group may be added from the base station device to the terminal device.
  • 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 configured by the master node may be called the master cell group (MCG).
  • the second base station device may be called the secondary node (SN).
  • the cell group configured by the secondary node may be called the secondary cell group (SCG).
  • the master node and secondary node may be configured within the same base station device.
  • the cell group configured in the terminal device may be called an MCG.
  • the SpCell configured in the terminal device may be a PCell.
  • an NR in which a DC is not configured may be called an NR standalone (NR SA).
  • Multi-Radio Dual Connectivity may be a technology that performs DC using E-UTRA for the MCG and NR for the SCG.
  • MR-DC may also be a technology that performs DC using NR for the MCG and E-UTRA for the SCG.
  • MR-DC may also be a technology that performs DC using NR for both the MCG and SCG.
  • MR-DC may be a technology included in DC. Examples of MR-DC that use E-UTRA for the MCG and NR for the SCG include EN-DC (E-UTRA-NR Dual Connectivity), which uses EPC in the core network, and NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity), which uses 5GC in the core network.
  • EN-DC E-UTRA-NR Dual Connectivity
  • NG-RAN E-UTRA-NR Dual Connectivity which uses 5GC in the core network.
  • MR-DC examples include NE-DC (NR-E-UTRA Dual Connectivity), which uses 5GC in the core network.
  • NR-DC NR-NR Dual Connectivity
  • NR-NR Dual Connectivity Another example of MR-DC that uses NR for both MCG and SCG.
  • one MAC entity may exist for each cell group.
  • the MAC entity for the MCG in the terminal device may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.).
  • the MAC entity for the SCG in the terminal device may be created by the terminal device when an SCG is configured in the terminal device.
  • the MAC entity for each cell group in the terminal device may be configured by the terminal device receiving RRC signaling from a base station device.
  • SpCell may mean PCell.
  • SpCell When the MAC entity is associated with an SCG, SpCell may mean primary SCG cell (PSCell). When the MAC entity is not associated with a cell group, SpCell may mean PCell. The PCell, PSCell, and SCell are serving cells.
  • the MAC entity for the MCG may be an E-UTRA MAC entity
  • the MAC entity for the SCG may be an NR MAC entity.
  • the MAC entity for the MCG may be an NR MAC entity
  • the MAC entity for the SCG may be an E-UTRA MAC entity.
  • the MAC entities for both the MCG and SCG may be NR MAC entities.
  • the existence of one MAC entity for each cell group may also be rephrased as the existence of one MAC entity for each SpCell.
  • one MAC entity for each cell group may also be rephrased as one MAC entity for each SpCell.
  • Figure 4 is a diagram showing an example of the flow of procedures for various settings in RRC according to this embodiment.
  • Figure 4 shows an example of the flow when RRC signaling is sent from a base station device (eNB102 and/or gNB108) to a terminal device (UE122).
  • eNB102 and/or gNB108 base station device
  • UE122 terminal device
  • the base station device creates an RRC message (step S400).
  • the base station device may create an RRC message in order to deliver system information (SI) or paging messages.
  • the base station device may also create an RRC message in order to send RRC signaling that causes a specific terminal device to perform a process.
  • the process that is caused to be performed by a specific terminal device may include, for example, security settings, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, and RRC connection release.
  • the RRC connection reconfiguration process may include, for example, radio bearer control (establishment, modification, release, etc.), cell group control (establishment, addition, modification, release, etc.), measurement settings, handover, security key update, etc.
  • the base station device may also create an RRC message in order to respond to RRC signaling sent from a terminal device.
  • Responses to RRC signaling sent from a terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc.
  • RRC messages contain information (parameters) for various information notifications and settings. These parameters may be fields of RRC messages and/or information elements, or field values (including information elements).
  • the structure of RRC messages may be described using a description method called ASN.1 (Abstract Syntax Notation One).
  • the base station device then transmits the created RRC signaling to the terminal device (step S402).
  • the terminal device then performs processing such as setting according to the received RRC signaling (step S404) if necessary.
  • the terminal device may transmit RRC signaling in response to the base station device (not shown).
  • RRC signaling may be used for other purposes, not limited to the above examples.
  • the master node's RRC may be used to transfer RRC signaling for SCG-side configuration (cell group configuration, radio bearer configuration, measurement configuration, etc.) between the terminal device.
  • RRC signaling for SCG-side configuration may be transmitted and received between the master node and secondary node.
  • the RRC signaling for E-UTRA transmitted from the eNB 102 to the UE 122 may include the RRC signaling for NR
  • the RRC signaling for NR transmitted from the gNB 108 to the UE 122 may include the RRC signaling for E-UTRA.
  • an MBS broadcast service (also simply referred to as a broadcast service)
  • the same service and the same specific content data may be provided simultaneously to all terminal devices (UE 122) within a geographical area.
  • Broadcast services may be delivered to terminal devices using broadcast sessions.
  • Terminal devices may be able to receive broadcast services in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states.
  • an MBS multicast service (also simply referred to as a multicast service)
  • the same service and the same specific content data may be provided simultaneously to one or more specific terminal devices (also referred to as a UE set).
  • the multicast service may be distributed to the terminal devices using a multicast session.
  • the terminal devices can receive the multicast service using mechanisms such as PTP (Point to Point) distribution and/or PTM (Point to Multipoint) distribution.
  • PTP Point to Point
  • PTM Point to Multipoint
  • HARQ feedback/retransmission is applicable to both PTP and PTM transmissions.
  • MTCH PTM downlink channel for transmitting MBS data of a multicast or broadcast session from the network to a terminal device.
  • DTCH PTP channel defined for transmitting MBS data of a multicast session from the network to a terminal device.
  • MCCH PTM downlink channel used to transmit MBS broadcast control information and/or MBS multicast control information for one or more MTCHs associated with a terminal device from the network.
  • a terminal device can receive different services using the same or different G-RNTIs.
  • a terminal device can receive different services using the same or different G-CS-RNTIs.
  • the gNB may deliver MBS data packets using the following methods: PTP transmission: The gNB may independently deliver a separate copy of the MBS data packet to each terminal device, i.e., the gNB may schedule a terminal-specific PDSCH using a terminal-specific PDCCH scrambled with a terminal-specific RNTI (e.g., C-RNTI) and deliver a separate copy of the MBS data packet scrambled with the same terminal-specific RNTI to each terminal device.
  • a terminal-specific RNTI e.g., C-RNTI
  • the gNB may deliver a single copy of an MBS data packet to a set of UEs, i.e., the gNB may schedule a group-common PDSCH using a group-common PDCCH scrambled with a group-common RNTI, and deliver a single copy of the MBS data packet scrambled with the same group-common RNTI to the set of UEs.
  • the gNB may dynamically decide whether to deliver multicast data to a specific terminal device via the PTM leg and/or the PTP leg based on information such as the MBS session QoS requirements, the number of participating terminal devices, and reception quality feedback for each terminal device. Furthermore, regardless of this decision, the same QoS requirements may be applied to both PTM and PTP transmissions.
  • 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 broadcast sessions (e.g., parameters required for MTCH reception) via the MCCH in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states.
  • Parameters required for MCCH reception may be provided via system information.
  • the MCCH may provide a list of some or all broadcast services transmitted on the MTCH and/or information related to the broadcast session.
  • the information related to the broadcast session may include the MBS Session ID, associated G-RNTI scheduling information, and information about neighboring cells providing a particular service on the MTCH.
  • the MCCH content may be transmitted within a regularly occurring time domain window defined by the MCCH repetition period, the MCCH window period, and the radio frame/slot offset.
  • the MCCH uses modification periods and MCCH content may only be allowed to change at modification period boundaries.
  • a notification mechanism may be used to signal changes in MCCH content due to broadcast session start, change, or stop, and neighbor cell information changes. When the terminal device receives an MCCH change notification, it may acquire the updated MCCH in the same MCCH change period in which the change notification was sent.
  • the mobility procedure for MBS reception allows a terminal device to start or continue receiving an MBS service when changing cells.
  • the gNB can indicate on the MCCH a list of neighboring cells that provide the same MBS broadcast service as the MBS broadcast service provided in the serving cell. This allows the terminal device to request unicast reception of the service before moving to a cell that does not provide an MBS broadcast service using PTM transmission.
  • the terminal device can learn on which frequencies the MBS broadcast service via PTM is provided via the User Service Description (USD) or the following combinations: ⁇ USD System information (System Information Block: SIB, e.g. SIB21)
  • the USD may include information indicating the correspondence between an MBS service and a frequency.
  • the USD may include at least one set of an MBS service identifier that identifies an MBS service and frequency information.
  • the USD may include at least one of an MBS session identifier that identifies an MBS session, information on the start and end times of the MBS session, an identifier that indicates the MBS service area in which the MBS session is provided, and information on the frequency in which the MBS session is provided.
  • the terminal device may apply the following modifications to the normal cell reselection rules: -
  • a terminal device that is receiving or interested in receiving MBS broadcast services via PTM can receive these MBS broadcast services while camping on a frequency that provides these MBS broadcast services, and can make this frequency the highest priority frequency if certain conditions are met.
  • the terminal device does not need to increase the priority of the frequencies that provide these MBS broadcast services.
  • a terminal device in the RRC_CONNECTED state can send an MBS Interest Indication (MII) consisting of the following information to the gNB to ensure continuity of the MBS broadcast service.
  • MII MBS Interest Indication
  • SIB e.g., SIB20
  • the reporting of MBS Interest indication may be implicitly enabled/disabled based on the presence or absence of a SIB (e.g., SIB21) containing mapping information between the current carrier frequency and/or adjacent carrier frequencies and MBS Frequency Selection Area Identities (FSAI). Additionally, the information contained in the MBS Interest indication may be exchanged between the source gNB and the target gNB during handover.
  • SIB e.g., SIB21
  • FSAI MBS Frequency Selection Area Identities
  • the gNB may deliver the broadcasted MBS data packets using the following methods: PTM Transmission: The gNB may deliver a single copy of an MBS data packet to a set of UEs. For example, the gNB may use a group-common PDCCH CRC-scrambled with a group-common RNTI to schedule a group-common PDSCH scrambled with the same group-common RNTI.
  • MBS broadcast configuration information may be provided on the MCCH logical channel.
  • Some configuration information including CFR (Common Frequency Resources) configuration for MCCH and MTCH, may be provided on logical channels other than the MCCH logical channel (e.g., BCCH, CCCH, DCCH, or DTCH).
  • CFR Common Frequency Resources
  • the MCCH may be used to deliver MBS broadcast configuration messages (MBSBroadcastConfiguration messages) indicating the MBS broadcast sessions offered in the cell and the scheduling information related to these sessions.
  • MBSBroadcastConfiguration message may include a list of neighboring cells that offer the same MBS broadcast service as the current cell.
  • the configuration information required for the terminal device to receive the MCCH may be provided in SIB1 and SIB20. Additionally, information regarding MBS broadcast service continuity may be provided in SIB21.
  • MCCH information (i.e., information transmitted in messages transmitted on the MCCH) may be transmitted periodically within a configured transmission window with a configurable recurrence period.
  • MCCH transmissions (and associated radio resources and MCS) may be indicated by a PDCCH addressed to the MCCH-RNTI.
  • the PDCCH monitoring occasion for MCCH transmission may be determined according to the common search space indicated by searchspaceMCCH. If searchspaceMCCH is set to zero, the PDCCH monitoring occasion for MCCH message reception in the MCCH transmission window may be the same as the PDCCH monitoring occasion of SIB1. If searchspaceMCCH is set to a non-zero value, the PDCCH monitoring occasion for MCCH messages may be determined based on the search space indicated by searchspaceMCCH.
  • Modifications to MCCH information may occur only in specific radio frames, and the concept of a modification period may be used. Within the modification period, the same MCCH information may be transmitted a number of times defined by its scheduling. If the network modifies some or all of the MCCH information, the network may notify the terminal device of the change from the start of the MCCH modification period using the PDCCH that schedules the MCCH. If a terminal device receives notification of the change and is receiving or interested in receiving an MBS service transmitted using an MBS broadcast, it may acquire new MCCH information from the same slot in which it received notification of the change. The terminal device may apply the previously acquired MCCH information until it acquires the new MCCH information.
  • the terminal device may apply the MCCH information acquisition procedure to acquire information on MBS broadcast settings broadcast by the network.
  • the MCCH information acquisition procedure may be applied to MBS broadcast services that an MBS-capable terminal device in the RRC_IDLE state, the RRC_INACTIVE state, or the RRC_CONNECTED state where a BWP with a common search space configured by searchSpaceMCCH is the active BWP is receiving or is interested in receiving.
  • the terminal device may apply the MCCH information acquisition procedure.
  • a terminal device interested in receiving the MBS broadcast service may apply the MCCH information acquisition procedure when entering a cell that provides SIB20 (e.g., when powered on, after the terminal device has moved), when receiving SIB20 on the SCell via dedicated signaling, and when notified that the MCCH information has changed due to the start of a new MBS service.
  • a terminal device receiving data via a broadcast MRB may apply the MCCH information acquisition procedure when notified that the MCCH information has changed due to a change in the MCCH information other than a change due to the start of a new MBS service.
  • the MCCH information acquisition procedure may overwrite stored MCCH information unless explicitly specified in the MCCH information acquisition procedure.
  • a terminal device receiving or interested in receiving an MBS broadcast service may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the slot in which it was notified that there was a change in the MCCH information if the MCCH information acquisition procedure was triggered based on being notified that there was a change in the MCCH information. Also, if the terminal device has entered a cell that provides SIB20 or has received information contained in SIB20 broadcast on the SCell via RRC signaling, the terminal device may start acquiring the MBSBroadcastConfiguration message transmitted using the MCCH from the next recurrence period.
  • the broadcast MRB configuration procedure may be used by a terminal device to configure PDCP, RLC, MAC, and PHY when the terminal device starts and/or stops receiving a broadcast MRB transmitted on the MTCH, or when the configuration of a broadcast MRB received by the terminal device is changed.
  • the broadcast MRB configuration procedure may apply to an MBS broadcast service that an MBS-capable terminal device in the RRC_IDLE state, the RRC_INACTIVE state, or the RRC_CONNECTED state where a BWP with a common search space configured by searchSpaceMTCH or searchSpaceMCCH is the active BWP is receiving or is interested in receiving.
  • a terminal device may apply (initiate) a broadcast MRB configuration procedure to start receiving an MBS session for an MBS broadcast service in which it is interested.
  • the broadcast MRB configuration procedure may be initiated when an MBS-capable terminal device interested in receiving an MBS broadcast service starts an MBS session, when it enters a cell that provides the MBS broadcast service, when it becomes interested in an ongoing MBS broadcast service, or when the terminal device's capability restrictions are lifted and it no longer prevents it from receiving an ongoing MBS broadcast service.
  • the terminal device may apply (initiate) the broadcast MRB release procedure to stop receiving an MBS broadcast service session.
  • the broadcast MRB release procedure may be initiated when the MBS session is stopped, when the terminal device moves away from the cell broadcasting the MBS service in which it is interested, when it loses interest in the MBS service, or when a capacity restriction that prevents reception of the associated service is initiated.
  • the terminal device may perform the following operations:
  • the terminal device may establish a PDCP entity, an RLC entity, and/or an SDAP entity 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 scheduling information (mtch-SchedulingInfo) of the MTCH.
  • the terminal device may also configure the PHY layer based on the settings applied to this broadcast MRB.
  • the terminal device may also receive the DL-SCH in the same cell as the cell in which it received the MBSBroadcastConfiguration message for establishing the broadcast MRB, using the G-RNTI and/or mtch-SchedulingInfo for this MBS broadcast service.
  • the terminal device may perform the following operations:
  • the terminal device may release the PDCP entity, the RLC entity, and the associated MAC and PHY settings.
  • the terminal device may also release the SDAP entity that no longer has an associated MRB.
  • the above-mentioned MBS broadcast configuration message may include information (MBS session information list) indicating one or more MBS broadcast sessions. Additionally or alternatively, the MBS broadcast configuration message may include a list of neighboring cells that provide the same broadcast MBS service. Each entry in the MBS session information list may include MBS broadcast session identifier information (TMGI).
  • the TMGI may include PLMN (Public Land Mobile Network) identifier information or an index value associated with the PLMN identifier information. Additionally or alternatively, the TMGI may include an identifier (service ID) for identifying the MBS service within the PLMN.
  • the MBS session information list may include one or more entries, and the entries in the MBS session information list may include a G-RNTI used for MTCH scheduling and transmission scrambling. Additionally or alternatively, the entries in the MBS session information list may include broadcast MRB settings (e.g., PDCP settings and RLC settings).
  • broadcast MRB settings e.g., PDCP settings and RLC settings.
  • the terminal device may perform an MBS interest indication procedure. This procedure may be used to indicate to the network that the terminal device in the RRC_CONNECTED state is receiving or is interested in receiving the MBS broadcast service. In addition, this procedure may be used to indicate to the network whether the terminal device in the RRC_CONNECTED state prioritizes MBS broadcast reception or unicast/multicast MRB reception. Additionally or alternatively, this procedure may be used for other purposes.
  • An MBS capable UE in the RRC_CONNECTED state may initiate the MBS interest indication procedure in several cases, including when an RRC connection is successfully established/restarted, when entering or leaving a broadcast service area, when an MBS broadcast session is started or stopped, when interest in the MBS broadcast service changes, when the priority of MBS broadcast reception and unicast/multicast reception changes, when the serving cell changes to a PCell providing SIB21 (i.e., when SIB21 is included in the scheduling information of SIB1), when SIB20 on an SCell is received via dedicated signaling, during handover, and when an RRC connection is re-established.
  • SIB21 i.e., when SIB21 is included in the scheduling information of SIB1
  • SIB20 on an SCell is received via dedicated signaling, during handover, and when an RRC connection is re-established.
  • This may also include when the serving cell is changed to a PCell that provides a parameter (nonServingCellMII) in SIB1 indicating that an MBS interest indication for receiving the MBS broadcast service in a non-serving cell may be sent to the serving cell, when reception of the MBS broadcast service in a non-serving cell is started or stopped, or when the CFR (common frequency resources) information or subcarrier spacing for MBS broadcast reception in a non-serving cell is changed. If the UE does not have the CFR information and subcarrier spacing for MBS broadcast reception in the non-serving cell, the UE may obtain this information from the non-serving cell before sending the MBS Interest Indication.
  • nonServingCellMII common frequency resources
  • the terminal device that initiated this procedure may perform some or all of the following (a) to (b) if SIB21 is provided by the PCell or if nonServingCellMII is provided in SIB1 by the PCell. (a) Verify that a valid version of SIB21 for the PCell is obtained.
  • the UE may set the content of the MBSInterestIndication message according to the MBS interest indication content preparation procedure based on the set of MBS broadcast frequencies determined according to the procedure for determining MBS frequencies of interest being non-empty, and start transmitting the MBSInterestIndication message.
  • the terminal device that initiated this procedure may perform the following process (pa) based on some or all of the following conditions (ca) to (ce) being met, or may perform the following process (pb) based on none of the conditions (ca) to (ce) being met.
  • the set of MBS broadcast frequencies of interest determined according to the procedure for determining MBS frequencies of interest is different from the mbs-FreqList included in the last transmission of the previous MBS interest indication.
  • (pa) Set the content of the MBS Interest Indication according to the MBS interest indication content preparation procedure and start transmitting the MBSInterestIndication message.
  • (pb) If SIB20 is provided on the PCell or SCell and (1) since the UE last transmitted an MBS Interest Indication, the UE has been connected to a PCell that does not provide SIB20 and the UE has not been provided with SIB20 for the SCell, or (2) the set of MBS broadcast services determined according to the procedure for determining MBS services of interest is different from the list included in the last MBS Interest Indication transmission, set the content of the MBS Interest Indication according to the MBS interest indication content preparation procedure and start transmitting the MBSInterestIndication message.
  • the terminal device may determine (judge) a frequency to be part of an MBS frequency of interest based on the fact that all of the following conditions (ca) to (cc) are satisfied for that frequency: (ca) At least one MBS session that the terminal device is receiving or is interested in receiving via a broadcast MRB has started or is about to start. (cb) For at least one MBS session that the terminal device is receiving or is interested in receiving via a broadcast MRB, SIB21 obtained from the PCell or a non-serving cell includes information on mapping between the frequency and one or more MBS FSAIs indicated in the USD of this MBS session, or the frequency is not included in SIB21 but is indicated in the USD of this session.
  • the information on the band combinations supported by the terminal device e.g., supportedBandCombinationList
  • the capability information of the terminal device e.g., UE-NR-Capability
  • the terminal device may determine (judge) that the MBS service is part of the MBS services of interest based on whether all of the following conditions (ca) to (cc) are met: (ca) The terminal device is receiving or is interested in receiving the MBS service via a broadcast MRB. (cb) A session for that MBS service has started or is about to start.
  • MBS FSAIs Frequency Specific Application Identifiers
  • SIB21 Service Description
  • SIB21 Service Description
  • Terminal devices may provide content for MBS interest indications.
  • the terminal device may perform some or all of the following processes (pa) to (pd) based on (1) having a valid version of SIB21 and (2) the set of MBS frequencies of interest determined by the procedure for determining MBS frequencies of interest is not empty.
  • You may set a list (mbs-FreqList) of MBS frequencies of interest sorted in descending order to be included in the MBS interest indication.
  • the terminal device may include the parameter mbs-Priority in the MBS interest indication based on the terminal device's preference for receiving MBS broadcasts over receiving any unicast/multicast MRBs.
  • the terminal device may inform the network that the terminal device prioritizes receiving MBS broadcasts over receiving any unicast/multicast MRBs.
  • the MBS services of interest sorted in descending order may be set in a list (mbs-ServiceList) to be included in the MBS interest indication.
  • the content of the MBS interest indication may include freqInfoMBS
  • the terminal device has acquired cfr-InfoMBS and subcarrierSpacing for receiving MBS broadcasts in non-serving cells, the cfr-InfoMBS and subcarrierSpacing may be included in the content of the MBS interest indication.
  • the RRC connection release procedure may be used for the following purposes (oa) to (ob): Additionally or alternatively, the RRC connection release procedure may be used for other purposes.
  • To release the RRC connection including releasing established radio bearers (except broadcast MRBs), backhaul RLC channels, Uu relay RLC channels, PC5 relay RLC channels, and/or radio resources.
  • To suspend the RRC connection including the suspension of established radio bearers (except broadcast MRBs)
  • the network may initiate the RRC connection release procedure to transition the terminal device from the RRC_CONNECTED state to the RRC_IDLE state, or to initiate the terminal device's transition from the RRC_CONNECTED state to the RRC_INACTIVE state only if SRB2 and at least one DRB or multicast MRB are configured in the RRC_CONNECTED state, or in the case of IAB and NCR, only if SRB2 is configured in the RRC_CONNECTED state.
  • This procedure may also be initiated by the network to transition the terminal device from the RRC_INACTIVE state to the RRC_INACTIVE state or the RRC_IDLE state when the terminal device attempts to resume the RRC connection (due to resumption of a suspended RRC connection or the start of an SDT). Additionally or alternatively, this procedure may be used by the network to release the terminal device and redirect it to another frequency. Additionally or alternatively, this procedure may be used for other purposes.
  • a terminal device that receives an RRC connection release message may perform some or all of the following processes (pa) to (pf) based on the fact that suspendConfig is included in this message.
  • pf Enter RRC_INACTIVE state
  • This section explains how a terminal device receives MBS multicast services in the RRC_INACTIVE state.
  • a terminal device configured to receive the MBS multicast service in the RRC_INACTIVE state may apply the MBS multicast procedure.
  • the MBS multicast configuration information may be provided in the RRCRelease message and/or the multicast MCCH logical channel. If there is temporarily no data in an active multicast session or if the multicast session is deactivated, the network may notify the terminal device through the MBS multicast configuration information to stop monitoring the corresponding G-RNTI. If the terminal device is notified to stop monitoring the G-RNTIs of all multicast sessions in which it participates, the terminal device may stop monitoring the multicast MCCH-RNTI of the notified cell.
  • the multicast MCCH may carry an MBS Multicast Configuration message indicating the MBS multicast sessions (multicast sessions) offered in the cell and the scheduling information associated with these sessions.
  • the MBSMulticastConfiguration message may also include a list of neighboring cells that provide the same MBS multicast service as that offered in the current cell for a terminal device in RRC_INACTIVE state.
  • the configuration information required for the terminal device to receive the multicast MCCH may be provided in broadcast information (e.g., SIB24).
  • the terminal device may apply the multicast MCCH information acquisition procedure to acquire MBS multicast configuration information from the network. This procedure may be applied to terminal devices configured to receive MBS multicast services in the RRC_INACTIVE state.
  • the terminal device may apply the multicast MCCH information acquisition procedure to update the PTM configuration and/or when reselecting to a new cell that provides SIB24. Furthermore, a terminal device receiving MBS multicast data in the RRC_INACTIVE state may apply the multicast MCCH information acquisition procedure when notified by the network that the multicast MCCH information has changed.
  • a terminal device configured to receive the MBS multicast service in the RRC_INACTIVE state may perform some or all of the following processes (pa) to (pb). (pa) If this procedure is triggered by notification from the network that multicast MCCH information has changed, it starts acquiring the MBSMulticastConfiguration message carried on the multicast MCCH in the associated cell from the slot in which this change notification was received.
  • the terminal device moves to another cell that provides SIB24, or if the terminal device receives an RRCRelease message and the terminal device is configured to receive MBS multicast in the RRC_INACTIVE state, and the RRC release message does not include PTM configuration for at least one multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI, it acquires the MBSMulticastConfiguration message carried on the multicast MCCH of the associated cell in the next recurrence period.
  • the terminal device may apply the settings contained in the MBSMulticastConfiguration message obtained by the above process.
  • the purpose of the RRC connection restart procedure may be to restart a suspended RRC connection, including restarting SRBs, DRBs, and multicast MRBs. Additionally or alternatively, the purpose of the RRC connection restart procedure may be to perform an RNA update. Additionally or alternatively, the purpose of the RRC connection restart procedure may be for other purposes.
  • the terminal device may send an RRCResumeRequest message and/or an RRCResumeRequest1 message to resume the RRC connection based on some or all of the conditions (ca) to (cd) below being met.
  • SIB24 is not scheduled by SIB1.
  • PTM configuration is not available for a multicast session in which the terminal device is participating and for which it does not indicate that it will stop monitoring the G-RNTI.
  • the mbs-NeighborCellList obtained in the previous cell indicates that a multicast session in which the terminal device is participating and for which it does not indicate that it will stop monitoring the G-RNTI is not provided in the current serving cell for a terminal device in RRC_INACTIVE state.
  • the measured RSRP and/or RSRQ of the serving cell are below the threshold indicated by thresholdIndex.
  • Figure 5 is a block diagram showing the configuration of a terminal device (UE122) in this embodiment. Note that to avoid complicating the explanation, Figure 5 shows only the main components closely related to this embodiment.
  • the UE 122 shown in FIG. 5 includes a receiver 500 that receives control information (DCI, MAC control elements, RRC signaling, broadcast information, etc.) from a base station device, a processor 502 that performs processing according to parameters included in the received control information, and a transmitter 504 that transmits the control information (UCI, MAC control elements, RRC signaling, etc.) to the base station device.
  • This base station device may be the eNB 102 or the gNB 108.
  • the processor 502 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer).
  • the processor 502 may include some or all of the physical layer processor (PHY processor), MAC layer processor (MAC processor), RLC layer processor (RLC processor), PDCP layer processor (PDCP processor), SDAP processor (SDAP processor), RRC layer processor (RRC processor), and NAS layer processor (NAS processor).
  • PHY processor physical layer processor
  • MAC processor MAC layer processor
  • RLC processor RLC layer processor
  • PDCP processor PDCP layer processor
  • SDAP processor SDAP processor
  • RRC layer processor RRC layer processor
  • NAS processor NAS layer processor
  • FIG. 6 is a block diagram showing the configuration of a base station device in this embodiment. Note that to avoid complicating the explanation, Figure 6 shows only the main components closely related to this embodiment.
  • This base station device may be an eNB102 or a gNB108.
  • the base station apparatus shown in FIG. 6 comprises a transmitter 600 that transmits control information (DCI, RRC signaling, broadcast information, etc.) to UE 122, a processor 602 that creates control information (DCI, RRC signaling including parameters, broadcast information, etc.) and transmits it to UE 122, causing processing unit 502 of UE 122 to process it, and a receiver 604 that receives control information (UCI, RRC signaling, etc.) from UE 122.
  • processing unit 602 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, processing unit 602 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit.
  • FIG. 7 is a diagram showing an example of processing by the terminal device (UE 122) in this embodiment.
  • the processing unit 502 of the terminal device receives first information and/or second information from the base station device (step S700).
  • the processing unit 502 of the terminal device determines, based on the second information, which of one or more MBS sessions identified by the received first information is available for reception (step S702).
  • the processing unit 502 of the terminal device performs an operation based on this determination (step S704).
  • the first information received from the base station device in step S700 may be, for example, information included in any one of the following (a) to (d) or any combination thereof: (a) Messages transmitted using the Multicast MCCH logical channel (b) System Information Block (e.g., SIB24) (c) RRC signaling (e.g., RRC release messages) transmitted using the DCCH (d) USD
  • the message in (a) may be an MBSMulticastConfiguration message or another message.
  • the system information block in (b) may be SIB24 or another SIB.
  • the RRC signaling in (c) may be an RRC release message or another RRC signaling or RRC message.
  • the second information received from the base station device in step S700 may be, for example, any one of the following (a) to (d) or any combination thereof.
  • Each of the areas indicated by the entries may be identified by an identifier.
  • the areas indicated by the one or more entries may also be defined as one area, in which case an identifier may be associated with each of the areas indicated by the one or more entries.
  • the identifier that identifies an area is also referred to as an area identifier.
  • the area identifier may be included in the second information together with the entry.
  • Figure 8 is a diagram showing an example of the above case (a).
  • a list (MBSAreaInfoList) in which one entry contains an area identifier (MBS-AreaId), Reference Location (ReferenceLocation), and radius information (mbs-DistanceRadius) is provided from the base station device to the terminal device.
  • an area is indicated by an SSB index may mean that if the terminal device can receive the indicated SSB, the terminal device is considered to be located in the area indicated by the SSB index.
  • the expression "being able to receive the indicated SSB” may mean that the received power of the SSB is equal to or greater than a certain threshold (or exceeds a threshold). This threshold may be notified in the first information, may be notified in the second information, or may be a predetermined value.
  • One or more areas notified in the second information may be associated with an MBS session.
  • each entry in the MBS session information list may include a list having zero or more area identifiers in the entry.
  • the TMGI included in each entry in the MBS session information list may be associated with zero or more areas.
  • the G-RNTI included in each entry in the MBS session information list may be associated with zero or more areas.
  • the PLMN included in each entry in the MBS session information list may be associated with zero or more areas.
  • the service ID included in each entry in the MBS session information list may be associated with zero or more areas.
  • FIG. 9 is a diagram showing an example in which area identifiers are included in an MBS multicast configuration message.
  • the MBS multicast configuration message (MBSMulticastConfiguration) includes an MBS session information list (MBS-SessionInfoListMulticast), and each entry in the MBS session information list includes a TMGI and G-RNTI, and optionally includes a list (MbsAreaList) with one or more area identifiers in the entry.
  • MBS session information list includes a TMGI and G-RNTI, and optionally includes a list (MbsAreaList) with one or more area identifiers in the entry.
  • MbsAreaList list with one or more area identifiers in the entry.
  • SIB24 and/or the RRC release message may include configuration information required to receive one or more multicast MCCHs, and each piece of configuration information required to receive a multicast MCCH may be associated with zero or more areas.
  • all MBS sessions notified in an MBS multicast configuration message received based on the configuration information required to receive a certain multicast MCCH may be associated with zero or more areas corresponding to the configuration information required to receive this multicast MCCH.
  • Figure 10 is a diagram showing an example of area identifiers included in SIB24.
  • SIB24 includes a list (MulticastMcchConfigList) of configuration information required to receive one or more multicast MCCHs, and each entry (McchConfig) in MulticastMcchConfigList includes configuration information (MCCH-Config) required to receive a multicast MCCH, and optionally includes a list (MbsAreaList) whose entries have one or more area identifiers. In other words, if MbsAreaList is not included in McchConfig, it may indicate that the McchConfig is associated with zero areas.
  • one or more MBS sessions may be associated with each of the areas notified in the second information.
  • each of the areas notified in the second information may be associated with one or more FSAIs.
  • each of the areas notified in the second information may be associated with one or more MBS services (e.g., MBS service identifiers notified in USD).
  • MBS services e.g., MBS service identifiers notified in USD.
  • MBS sessions and/or MBS services may be not associated with any area (i.e., associated with zero areas).
  • the determination in step S702 may be, for example, when the terminal device is configured to receive MBS multicast in the RRC_INACTIVE state, determining whether the terminal device satisfies some or all of the following conditions (ca) to (ce) in the RRC_INACTIVE state. (ca) SIB24 is not scheduled by SIB1. (cb) In the cell after cell selection or reselection, PTM settings are not available for a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it is participating.
  • a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI by the mbs-NeighborCellList obtained in the previous cell is not provided for a terminal device in RRC_INACTIVE state in the current serving cell.
  • the measured RSRP and/or RSRQ of the serving cell are below the threshold indicated by thresholdIndex.
  • the terminal device is not located in the area (notified by the second information) associated with a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it is participating, or the terminal device has left the area (notified by the second information) associated with a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it is participating.
  • the terminal device may send an RRCResumeRequest message and/or an RRCResumeRequest1 message to resume the RRC connection based on whether some or all of the above conditions (c-a) to (c-e) are met. This allows the terminal device to resume the RRC connection when it is unable to receive the multicast session based on its location within the cell.
  • the determination in step S702 may be, for example, when the terminal device is configured to receive MBS multicast in the RRC_INACTIVE state, determining whether the terminal device satisfies some or all of the following conditions (ca) to (cd) in the RRC_INACTIVE state. (ca) SIB24 is not scheduled by SIB1. (cb) In the cell after cell selection or reselection, PTM configuration for a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it participates is not available, and the terminal device is located in an area (notified by the second information) associated with a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it participates.
  • a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it participates is not provided in the current serving cell for a terminal device in RRC_INACTIVE state by the mbs-NeighborCellList acquired in the previous cell, and the terminal device is located in an area (notified by the second information) associated with a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it participates.
  • the measured RSRP and/or RSRQ of the serving cell are below the threshold indicated by thresholdIndex, and the terminal device is located in an area (notified by the second information) associated with a multicast session that does not indicate that the terminal device will stop monitoring the G-RNTI to which it participates.
  • the terminal device may send an RRCResumeRequest message and/or an RRCResumeRequest1 message to resume the RRC connection based on whether some or all of the above conditions (c-a) to (c-d) are met. This prevents unnecessary resumption of the RRC connection when the terminal device is not permitted to receive the multicast session based on its location within the cell.
  • a list consisting only of entries with no area associated with it, and a list consisting of entries with zero or more areas associated with it may be included independently in the MBS multicast configuration message.
  • the above mechanism enables base station devices to provide terminal devices with MBS multicast services via PTM delivery in specific areas within a cell without using PTP delivery. Furthermore, terminal devices can receive MBS multicast services in appropriate areas within the cell.
  • the processing unit 502 of the UE 122 may be a processing unit that performs RRC layer processing.
  • Each piece of area information may be information indicating part or all of the area of the cell, or information indicating an area independent of the cell. Additionally or alternatively, each piece of area information may be information common to one or more cells. Additionally or alternatively, each piece of area information may be information indicating an area based on a relative position with respect to the Reference location of the cell. Additionally or alternatively, each piece of area information may be information indicating an area based on an absolute position independent of the cell.
  • information other than the information indicating the area may be notified to the terminal device as the second information or included in the second information.
  • the terminal device may be notified from the network (base station device) of information on the MBS multicast services and/or MBS sessions that it is permitted to receive.
  • the information may include information such as the G-RNTI and service ID of the MBS sessions that it is permitted to receive.
  • the information may include information necessary for decoding the MBS sessions that it is permitted to receive.
  • the information may include information indicating the period for which the information is valid (e.g., a timer value).
  • the network (base station device) may notify the information based on location information notified by the terminal device. Additionally or alternatively, the network (base station device) may notify the information based on a report of measurement results of reference signals transmitted from one or more cells notified by the terminal device. Additionally or alternatively, the network (base station device) may notify the information based on other information.
  • the first information and/or the second information may be notified to the terminal device by any one or any combination of an RRC message, RRC signaling, a message from a layer above the RRC layer, and a MAC control element.
  • the MBS session described above may be a multicast session.
  • the program running on the device related to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make the computer function so as to realize the functions of this embodiment.
  • the program or the information handled by the program is temporarily loaded into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or a Hard Disk Drive (HDD), and is read, modified, and written by the CPU as needed.
  • volatile memory such as Random Access Memory (RAM) during processing
  • non-volatile memory such as flash memory or a Hard Disk Drive (HDD)
  • part of the device in the above-described embodiments may be implemented by a computer.
  • 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 read and executed by a computer system.
  • the term "computer system” here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices.
  • the term "computer-readable recording medium” may be any of a semiconductor recording medium, optical recording medium, magnetic recording medium, etc.
  • “computer-readable recording medium” may include something that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or something that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such cases.
  • the above program may be one that realizes some of the functions described above, or one that can realize the functions described above in combination with a program already recorded in the computer system.
  • each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, typically an integrated circuit or multiple integrated circuits.
  • the electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof.
  • the general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each of the aforementioned circuits may be composed of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology result in the emergence of integrated circuit technology that can replace current integrated circuits, integrated circuits based on that technology may also be used.
  • this embodiment is not limited to the above-described embodiment. While one example of a device has been described in the embodiment, this embodiment is not limited to this and can be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.
  • terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.
  • One aspect of the present invention can be used, for example, in communication systems, communication devices (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.
  • communication devices e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices
  • integrated circuits e.g., communication chips
  • E-UTRA 102 eNB 104 EPC 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interfaces 122UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 Processing section 504, 600 Transmitter

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention porte sur un équipement terminal qui reçoit, en provenance d'un dispositif de station de base, des informations de commande relatives à un ou plusieurs services de multidiffusion/diffusion (MBS), et un message de libération RRC comprenant un ou plusieurs éléments d'informations de zone. Pendant un état RRC_INACTIVE, une unité de traitement émet un message de demande de reprise RRC vers le dispositif de station de base afin de reprendre une connexion RRC, sur la base de l'impossibilité d'utiliser, dans une cellule après une resélection de cellule, une configuration PTM pour une session de multidiffusion dans laquelle l'équipement terminal participe et pour lequel l'arrêt de la surveillance G-RNTI n'est pas indiqué, et sur la base du fait que l'équipement terminal est situé dans une région autour de laquelle il y a notification dans les informations de zone, ladite région étant associée à la session de multidiffusion dans laquelle l'équipement terminal participe et pour lequel l'arrêt de la surveillance G-RNTI n'est pas indiqué.　
PCT/JP2024/043410 2024-03-22 2024-12-09 Équipement terminal, procédé et circuit intégré Pending WO2025197209A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2024-046585 2024-03-22
JP2024046585A JP2025146021A (ja) 2024-03-22 2024-03-22 端末装置、方法、および集積回路

Publications (1)

Publication Number Publication Date
WO2025197209A1 true WO2025197209A1 (fr) 2025-09-25

Family

ID=97138701

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/043410 Pending WO2025197209A1 (fr) 2024-03-22 2024-12-09 Équipement terminal, procédé et circuit intégré

Country Status (2)

Country Link
JP (1) JP2025146021A (fr)
WO (1) WO2025197209A1 (fr)

Also Published As

Publication number Publication date
JP2025146021A (ja) 2025-10-03

Similar Documents

Publication Publication Date Title
US20230309185A1 (en) Terminal apparatus, base station apparatus, and method
EP4145937B1 (fr) Dispositif terminal, procédé et circuit intégré
EP4224914A1 (fr) Dispositif terminal, procédé de communication et dispositif station de base
JP2024102379A (ja) 端末装置、方法、および、集積回路
US12120598B2 (en) Terminal apparatus, method, and integrated circuit
US20230247687A1 (en) Terminal apparatus, base station apparatus, and method
WO2025197209A1 (fr) Équipement terminal, procédé et circuit intégré
WO2025197205A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025197188A1 (fr) Équipement terminal, procédé et circuit intégré
WO2025191926A1 (fr) Dispositif terminal, procédé, et circuit intégré
WO2025150263A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025150264A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025150260A1 (fr) Dispositif terminal, procédé et circuit intégré
JP7747605B2 (ja) 端末装置、方法、および、集積回路
WO2025023297A1 (fr) Dispositif terminal, procédé et circuit intégré
JP2025142177A (ja) 端末装置、方法、および、集積回路
WO2025022679A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025022678A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025032841A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025158919A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025070742A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024232112A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023106315A1 (fr) Dispositif terminal, dispositif de station de base et procédé
JP2024049827A (ja) 端末装置、方法、および、集積回路
JP2024049826A (ja) 端末装置、および、方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24930672

Country of ref document: EP

Kind code of ref document: A1