Communication method, user device, network device, mobile communication system, program, and chipset

The communication method allows user equipment to efficiently receive MBS from SCG/SCell in DC/CA by exchanging MBS-related information and using RNTI for PDCCH monitoring, addressing the lack of defined mechanisms in current specifications and improving network efficiency and user experience.

JP2024160309AActive Publication Date: 2024-11-13KYOCERA CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024130922
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-07-19
Filing Date
2024-08-07
Publication Date
2024-11-13
Estimated Expiration
2042-07-19

AI Technical Summary

Technical Problem

Current 3GPP technical specifications do not define a mechanism for user equipment to efficiently receive multicast broadcast services (MBS) from a secondary cell group (SCG) in dual connectivity (DC) or a secondary cell (SCell) in carrier aggregation (CA), making it difficult for user equipment to effectively receive MBS from these entities.

Method used

A communication method that enables user equipment to efficiently receive MBS from an SCG in DC or an SCell in CA by allowing MBS-related information exchange and monitoring of the physical downlink control channel using a radio network temporary identifier (RNTI), even if the SCG or SCell is deactivated, and managing MBS sessions through interest notifications and configuration information sharing between master and secondary nodes.

Benefits of technology

Enables seamless and efficient MBS reception from SCG/SCell by optimizing communication methods, reducing power consumption, and maintaining connectivity with the master node, thereby enhancing the user experience and network efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024160309000001_ABST
    Figure 2024160309000001_ABST
Patent Text Reader

Abstract

To provide a communication method that enables a user device to efficiently receive multicast broadcast services (MBS) from a secondary cell group (SCG) in dual connectivity (DC) in which the user device communicates with two base stations simultaneously, or from a secondary cell (SCell) in carrier aggregation (CA) in which the user device communicates with multiple cells of one base station simultaneously.SOLUTION: A communication method for use in a mobile communication system supporting MBS, includes a step S12a of communicating with a master cell group (MCG) in DC by a user device performing the DC, and a step S13a of performing MBS reception from an SCG in the DC by the user device. The step S12a of communicating includes a step of communicating MBS-related information regarding the MBS reception from the SCG with the MCG.SELECTED DRAWING: Figure 10
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a communication method for use in a mobile communication system. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) (registered trademark; the same applies below) standard prescribes the technical specifications for NR (New Radio), a fifth-generation (5G) wireless access technology. Compared to LTE (Long Term Evolution), a fourth-generation (4G) wireless access technology, NR has features such as high speed, large capacity, high reliability, and low latency. The introduction of multicast and broadcast services (MBS) into such 5G systems is being considered.

[0003] In addition, the 3GPP technical specifications prescribe carrier aggregation (CA), in which a user device communicates with multiple cells of one base station simultaneously, and dual connectivity (DC), in which a user device communicates with two base stations simultaneously. In DC, one of the two base stations is a master node (MN) and the other is a secondary node (SN).

[0004] Currently, in the case of CA, it is assumed that the user equipment receives the MBS from a primary cell (PCell) managed by the base station, and in the case of DC, it is assumed that the user equipment receives the MBS from a master cell group (MCG) managed by the MN. Here, Non-Patent Document 1 proposes that the secondary cell group (SCG) managed by the SN can transmit the MBS to the user equipment. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP contribution: RWS-210126, “Discussion on MBS enhancement” Summary of the Invention

[0006] A communication method according to a first aspect is a communication method for use in a mobile communication system supporting a multicast / broadcast service (MBS), comprising: a user equipment performing dual connectivity (DC) or carrier aggregation (CA) communicating with a master cell group in the DC or a primary cell in the CA; and the user equipment receiving an MBS from a secondary cell group in the DC or a secondary cell in the CA. The communicating includes communicating MBS-related information regarding the MBS reception from the secondary cell group or the secondary cell with the master cell group or the primary cell.

[0007] A communication method according to a second aspect is a communication method used in a mobile communication system supporting a multicast / broadcast service (MBS), comprising: a user equipment performing dual connectivity (DC) or carrier aggregation (CA); the user equipment monitoring a physical downlink control channel (PDCCH) in a secondary cell group in the DC or a secondary cell in the CA using a radio network temporary identifier (RNTI) for performing MBS reception in the secondary cell group in the DC or a secondary cell in the CA; and the user equipment continuing to monitor the PDCCH using the RNTI even if the secondary cell group or the secondary cell is deactivated.

[0008] A communication method according to a third aspect is a communication method used in a mobile communication system supporting a multicast / broadcast service (MBS), comprising: a user equipment performing dual connectivity (DC) identifying, from a master cell group and a secondary cell group, a cell group that provides an MBS session that the user equipment is receiving or is interested in receiving; and the user equipment transmitting an MBS interest notification regarding the MBS session to the identified cell group.

[0009] A communication method according to a fourth aspect is a communication method used in a mobile communication system supporting a multicast / broadcast service (MBS), comprising: a master node managing a master cell group in a dual connectivity (DC) performed by a user equipment communicating with a secondary node managing a secondary cell group in the DC; and transmitting an MBS from the master cell group or the secondary cell group to the user equipment. The communicating includes communicating with the secondary node an MBS interest notification regarding an MBS session that the user equipment is receiving or is interested in receiving.

[0010] A communication method according to a fifth aspect is a communication method used in a mobile communication system supporting a multicast / broadcast service (MBS), comprising: a secondary node managing a secondary cell group in dual connectivity (DC) with a user device communicating with a master node managing a master cell group in the DC; and the secondary node transmitting an MBS to the user device. The communicating includes transmitting MBS setting information indicating a setting for the user device to receive an MBS in the secondary cell group from the secondary node to the master node. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing a configuration of a UE (user equipment) according to an embodiment. [Diagram 3] A diagram showing the configuration of a gNB (base station) according to an embodiment. [Figure 4] A diagram showing the configuration of a protocol stack of a wireless interface of a user plane that handles data. [Diagram 5] FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals). [Figure 6] FIG. 2 is a diagram showing an overview of MBS traffic distribution according to an embodiment. [Figure 7] FIG. 13 is a diagram illustrating a distribution mode according to the embodiment. [Figure 8] FIG. 2 is a diagram showing a first operation scenario according to the embodiment. [Figure 9] FIG. 11 is a diagram showing a second operation scenario according to the embodiment. [Figure 10] FIG. 4 is a diagram illustrating a first operation example according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating a second operation example according to the embodiment. [Figure 12] FIG. 11 is a diagram illustrating a third operation example according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating a fourth operation example according to the embodiment. [Figure 14] FIG. 13 is a diagram illustrating a fifth operation example according to the embodiment. [Figure 15] FIG. 13 is a diagram illustrating a sixth operation example according to the embodiment. [Figure 16] FIG. 1 is a diagram illustrating a first embodiment. [Figure 17] FIG. 13 is a diagram illustrating a second embodiment. [Figure 18] FIG. 13 is a diagram illustrating a third embodiment. [Figure 19] FIG. 13 is a diagram illustrating a fourth embodiment. [Figure 20] FIG. 13 is a diagram illustrating a fifth embodiment. [Figure 21] A diagram showing the operation of a MAC entity of a UE in the sixth embodiment. [Figure 22] FIG. 13 is a diagram illustrating a sixth embodiment. [Diagram 23] FIG. 13 is a diagram illustrating a seventh embodiment. [Figure 24] FIG. 13 is a diagram illustrating an eighth embodiment. [Diagram 25] FIG. 13 is a diagram illustrating a ninth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] In the current technical specifications of 3GPP, a mechanism for a user equipment to receive an MBS from an SCG in a DC or a secondary cell (SCell) in a CA is not specified. Therefore, it is difficult for a user equipment to efficiently receive an MBS from an SCG in a DC or a SCell in a CA.

[0013] Therefore, the present disclosure provides a communication method that enables a user equipment to efficiently receive MBS from an SCG in a DC or an SCell in a CA.

[0014] A mobile communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0015] (Configuration of a mobile communication system) FIG. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. The mobile communication system 1 complies with the 3GPP standard 5th Generation System (5GS). In the following description, 5GS is taken as an example, but the mobile communication system may be at least partially applied to a Long Term Evolution (LTE) system. The mobile communication system may be at least partially applied to a sixth generation (6G) system.

[0016] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN) 10, and a 5G core network (5GC) 20. Hereinafter, the NG-RAN 10 may be simply referred to as the RAN 10. The 5GC 20 may be simply referred to as the core network (CN) 20.

[0017] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user, and may be, for example, a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0018] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with the UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, and the like. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource for performing wireless communication with the UE 100. One cell belongs to one carrier frequency.

[0019] In addition, gNBs can also be connected to the Evolved Packet Core (EPC), which is the core network of LTE. LTE base stations can also be connected to 5GC. LTE base stations and gNBs can also be connected via an inter-base station interface.

[0020] The 5GC20 includes an Access and Mobility Management Function (AMF) and a User Plane Function (UPF) 300. The AMF performs various mobility controls for the UE 100. The AMF manages the mobility of the UE 100 by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF controls data forwarding. The AMF and the UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0021] 2 is a diagram showing a configuration of a UE 100 (user equipment) according to an embodiment. The UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130. The receiving unit 110 and the transmitting unit 120 configure a wireless communication unit that performs wireless communication with the gNB 200.

[0022] The receiving unit 110 performs various receptions under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0023] The transmission unit 120 performs various transmissions under the control of the control unit 130. The transmission unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0024] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes of each layer described below. The control unit 130 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes.

[0025] 3 is a diagram showing a configuration of a gNB 200 (base station) according to an embodiment. The gNB 200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communication unit 240. The transmitter 210 and the receiver 220 constitute a wireless communication unit that performs wireless communication with the UE 100. The backhaul communication unit 240 constitutes a network communication unit that performs communication with the CN 20.

[0026] The transmission unit 210 performs various transmissions under the control of the control unit 230. The transmission unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.

[0027] The receiving unit 220 performs various receptions under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.

[0028] The control unit 230 performs various controls and processes in the gNB 200. Such processes include processes of each layer described below. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes.

[0029] The backhaul communication unit 240 is connected to adjacent base stations via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF / UPF 300 via a base station-core network interface. Note that the gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (i.e., the functions are divided), and both units may be connected to each other via an F1 interface.

[0030] FIG. 4 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0031] The user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0032] The PHY layer performs coding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the gNB 200 via a physical channel. The PHY layer of the UE 100 receives downlink control information (DCI) transmitted from the gNB 200 on a physical downlink control channel (PDCCH). Specifically, the UE 100 performs blind decoding of the PDCCH using a radio network temporary identifier (RNTI) and acquires the successfully decoded DCI as DCI addressed to the UE. The DCI transmitted from the base station 200 has CRC parity bits scrambled by the RNTI added thereto.

[0033] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of UE100 and the MAC layer of gNB200 via a transport channel. The MAC layer of gNB200 includes a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be assigned to UE100.

[0034] The RLC layer transmits data to the RLC layer on the receiving side by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.

[0035] The PDCP layer performs header compression / decompression, encryption / decryption, etc.

[0036] The SDAP layer maps IP flows, which are units for QoS (Quality of Service) control by the core network, to radio bearers, which are units for QoS control by the AS (Access Stratum). Note that if the RAN is connected to the EPC, the SDAP is not necessary.

[0037] FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0038] The protocol stack of the radio interface of the control plane has a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer instead of the SDAP layer shown in FIG.

[0039] Between the RRC layer of the UE 100 and the RRC layer of the gNB 200, RRC signaling for various settings is transmitted. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC idle state. When the connection between the RRC of the UE 100 and the RRC of the gNB 200 is suspended, the UE 100 is in an RRC inactive state.

[0040] The NAS layer positioned above the RRC layer performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300a.

[0041] In addition, the UE 100 has an application layer and the like in addition to the protocol of the radio interface.

[0042] (Overview of MBS) An overview of the MBS according to the embodiment will be described. The MBS is a service that enables broadcast or multicast, i.e., point-to-multipoint (PTM) data transmission from the NG-RAN 10 to the UE 100. Possible use cases (service types) of the MBS include public safety communication, mission-critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV (Internet Protocol TeleVision), group communication, and software distribution.

[0043] The broadcast service provides a service to all UEs 100 within a specific service area for applications that do not require highly reliable QoS. An MBS session used for the broadcast service is called a broadcast session.

[0044] The multicast service provides services to a group of UEs 100 participating in the multicast service, rather than to all UEs 100. The MBS session used in the multicast service is called a multicast session. The multicast service provides the same content to a group of UEs 100 in a more radio-efficient manner than the broadcast service.

[0045] FIG. 6 is a diagram showing an overview of MBS traffic delivery according to the embodiment.

[0046] As shown in Fig. 6, MBS traffic (MBS data) is distributed from a single data source (application service provider) to multiple UEs. A 5G core network, 5G CN (5GC) 20, receives the MBS data from the application service provider, creates a copy (replication) of the MBS data, and distributes it.

[0047] From the 5GC20 perspective, two multicast delivery methods are possible: 5GC Shared MBS Traffic delivery and 5GC Individual MBS Traffic delivery.

[0048] In the 5GC individual MBS traffic delivery method, the 5GC 20 receives a single copy of MBS data packets and delivers individual copies of those MBS data packets to individual UEs 100 via a PDU session for each UE 100. Therefore, one PDU session for each UE 100 needs to be associated with the multicast session.

[0049] In the 5GC shared MBS traffic delivery method, the 5GC 20 receives a single copy of MBS data packets and delivers the single copy of those MBS packets to a RAN node (i.e., the gNB 200). The gNB 200 receives the MBS data packets via an MBS tunnel connection and delivers them to one or more UEs 100.

[0050] From the perspective of the RAN (5G RAN) 10, there are two possible delivery methods for transmitting MBS data over the air in the 5GC shared MBS traffic delivery method: PTP (Point-to-Point) and PTM (Point-to-Multipoint). PTP stands for unicast, and PTM stands for multicast and broadcast.

[0051] In the PTP distribution method, the gNB 200 distributes individual copies of the MBS data packets wirelessly to each UE 100. On the other hand, in the PTM distribution method, the gNB 200 distributes a single copy of the MBS data packet wirelessly to a group of UEs 100. The gNB 200 can dynamically determine whether to use PTM or PTP as the distribution method for MBS data to one UE 100.

[0052] The PTP distribution method and the PTM distribution method are mainly related to the user plane. There are two distribution modes, a first distribution mode and a second distribution mode, as the control mode of MBS data distribution. Figure 7 is a diagram showing the distribution modes according to the embodiment.

[0053] As shown in Fig. 7, the first delivery mode (Delivery mode 1) is a delivery mode that can be used by the UE 100 in the RRC connected state, and is a delivery mode for high QoS requirements. The first delivery mode is used for a multicast session among MBS sessions. However, the first delivery mode may also be used for a broadcast session. The first delivery mode may also be available to the UE 100 in the RRC idle state or the RRC inactive state.

[0054] In the embodiment, the setting of the MBS reception in the first distribution mode is performed by UE-dedicated signaling. For example, the setting of the MBS reception in the first distribution mode is performed by an RRC Reconfiguration message (or an RRC Release message), which is an RRC message transmitted by unicast from the gNB 200 to the UE 100.

[0055] The MBS reception configuration includes MBS traffic channel configuration information (hereinafter referred to as "MTCH configuration information") related to the configuration of the MBS traffic channel carrying MBS data. The MTCH configuration information includes MBS session information related to the MBS session and scheduling information of the MBS traffic channel corresponding to the MBS session. The scheduling information of the MBS traffic channel may include a discontinuous reception (DRX) configuration of the MBS traffic channel. The discontinuous reception configuration may include one or more parameters of a timer value (On Duration Timer) defining an on-duration (On Duration: reception period), a timer value (Inactivity Timer) extending the on-duration, a scheduling interval or DRX cycle (Scheduling Period, DRX Cycle), an offset value of the start subframe of the scheduling or DRX cycle (Start Offset, DRX Cycle Offest), a start delay slot value of the on-duration timer (Slot Offset), a timer value (Retransmission Timer) defining the maximum time until retransmission, and a timer value (HARQ RTT Timer) defining the minimum interval until DL allocation of HARQ retransmission.

[0056] The MBS traffic channel is a type of logical channel and may be referred to as an MTCH. The MBS traffic channel is mapped to a downlink shared channel (DL-SCH), which is a type of transport channel.

[0057] The second delivery mode (Delivery mode 2) is a delivery mode that can be used not only by the UE 100 in the RRC connected state, but also by the UE 100 in the RRC idle state or the RRC inactive state, and is a delivery mode for low QoS requirements. The second delivery mode is used for a broadcast session among MBS sessions. However, the second delivery mode may also be applicable to a multicast session.

[0058] The setting of MBS reception in the second distribution mode is performed by broadcast signaling. For example, the setting of MBS reception in the second distribution mode is performed by a logical channel broadcast from the gNB 200 to the UE 100, such as a broadcast control channel (BCCH) and / or a multicast control channel (MCCH). The UE 100 can receive the BCCH and MCCH using a dedicated RNTI predefined in the technical specifications, for example. The RNTI for BCCH reception may be SI-RNTI, and the RNTI for MCCH reception may be MCCH-RNTI.

[0059] In the second distribution mode, UE 100 may receive MBS data in the following three procedures. First, UE 100 receives MCCH configuration information by a SIB (MBS-SIB) transmitted on a BCCH from gNB 200. Second, UE 100 receives an MCCH from gNB 200 based on the MCCH configuration information. The MCCH transmits the MTCH configuration information. Third, UE 100 receives an MTCH (MBS data) based on the MTCH configuration information. Hereinafter, MTCH configuration information and / or MCCH configuration information may be referred to as MBS configuration information.

[0060] In the first distribution mode and the second distribution mode, the UE 100 may receive the MTCH using a group RNTI (G-RNTI) assigned by the gNB 200. The G-RNTI corresponds to an RNTI for receiving the MTCH.

[0061] The network can provide different MBS services for each MBS session. An MBS session is identified by at least one of a Temporary Mobile Group Identity (TMGI), a source-specific IP multicast address (consisting of a source unicast IP address of an application function or application server, etc., and an IP multicast address indicating a destination address), a session identifier, and a G-RNTI. At least one of the TMGI, the source-specific IP multicast address, and the session identifier is called an MBS session identifier (MBS session ID). The TMGI, the source-specific IP multicast address, the session identifier, and the G-RNTI are collectively called MBS session information.

[0062] (Mobile communication system operation) FIG. 8 is a diagram showing a first operation scenario according to the embodiment. The first operation scenario is a scenario in which the UE 100 performs DC in which the UE 100 communicates with two base stations (MN 200A and SN 200B) simultaneously. The MN 200A may be an NR base station (gNB) or an LTE base station (eNB). The MN (master node) 200A may be called a master base station. The SN 200B may be an NR base station (gNB) or an LTE base station (eNB). The SN (secondary node) 200B may be called a secondary base station.

[0063] The UE 100 in the RRC connected state is assigned radio resources by the respective schedulers of the MN 200A and the SN 200B that are connected to each other via a backhaul (network interface), and performs radio communication using the radio resources of the MN 200A and the radio resources of the SN 200B. The network interface between the MN 200A and the SN 200 may be an Xn interface or an X2 interface. The MN 200A and the SN 200 communicate with each other via the network interface.

[0064] The MN 200A may have a control plane connection with a core network. The MN 200A provides a main radio resource for the UE 100. The MN 200A manages the MCG 201A. The MCG 201A is a group of serving cells associated with the MN 200A. The MCG 201A has a PCell and optionally has one or more SCells.

[0065] The SN 200B may not have a control plane connection to the core network. The SN 200B provides additional radio resources to the UE 100. The SN 200B manages the SCG 201B. The MCG 201A has a Primary Secondary Cell (PSCell) and optionally has one or more SCells.

[0066] Currently, in the case of DC, it is assumed that the UE 100 receives the MBS from the MCG 201A managed by the MN 200A. In the embodiment, the MBS is transmitted to the UE 100 from the SCG 201B managed by the SN 200B. Specifically, the SN 200B supports transmission of MBS data by multicast or broadcast (PTM transmission). The UE 100 receives the MBS from either the MN 200A (MCG 201A) or the SN 200B (SCG 201B).

[0067] 9 is a diagram showing a second operation scenario according to the embodiment. The second operation scenario is a scenario in which the UE 100 performs CA in which the UE 100 simultaneously communicates with multiple serving cells of one base station (gNB 200). The multiple serving cells include a PCell 202A and one or more SCells 202B.

[0068] The PCell 202A provides NAS mobility information to the UE 100 upon establishment, re-establishment, or handover of the RRC connection of the UE 100, and provides security information upon re-establishment or handover of the RRC connection of the UE 100. The SCell 202B forms a serving cell set together with the PCell 202A.

[0069] Currently, in the case of CA, it is assumed that the UE 100 receives the MBS from the PCell 202A. In an embodiment, the MBS is transmitted from the SCell 202B to the UE 100. Specifically, the SCell 202B supports transmission of MBS data by multicast or broadcast (PTM transmission). The UE 100 receives the MBS from either the PCell 202A or the SCell 202B.

[0070] The following describes operations that enable the UE 100 to efficiently receive MBS from the SCG 201B in the DC or the SCell 202B in the CA.

[0071] 10 is a diagram showing a first operation example according to the embodiment. The first operation example is an operation example related to the above-mentioned first operation scenario (scenario in which DC is performed).

[0072] In step S11a, the UE 100 starts a DC as shown in Fig. 8. For example, the MCG 201A (MN 200A) sets an SCG 201B for the UE 100 and activates the SCG 201B.

[0073] In step S12a, the UE 100 performing DC communicates with the MCG 201A. Here, the UE 100 communicates MBS-related information regarding MBS reception from the SCG 201B with the MCG 201A.

[0074] In step S13a, the UE 100 receives the MBS from the SCG 201B. Step S13a may be performed before step S12a.

[0075] In this way, the UE 100 performing DC communicates MBS-related information regarding MBS reception from the SCG 201B with the MCG 201A. This enables the UE 100 to efficiently receive MBS from the SCG 201B under the management of the MCG 201A (MN 200A).

[0076] 11 is a diagram showing a second operation example according to the embodiment. The second operation example is an operation example related to the above-mentioned second operation scenario (scenario for performing CA).

[0077] In step S11b, the UE 100 starts CA as shown in Fig. 9. For example, the PCell 202A (gNB 200) configures the SCell 202B for the UE 100 and activates the SCell 202B.

[0078] In step S12b, the UE 100 performing CA communicates with the PCell 202A. Here, the UE 100 communicates MBS-related information regarding MBS reception from the SCell 202B with the PCell 202A.

[0079] In step S13b, the UE 100 performs MBS reception from the SCell 202B. Step S13b may be performed before step S12b.

[0080] In this way, the UE 100 performing CA communicates MBS-related information regarding MBS reception from the SCell 202B with the PCell 202A. This enables the UE 100 to efficiently receive MBS from the SCell 202B under the management of the PCell 202A.

[0081] In the above-mentioned first and second operation examples, MCG201A and PCell202A play similar roles, and SCell202B and SCell202B play similar roles. In the following, when DC and CA are not distinguished, MCG201A or PCell202A is described as MCG201A / PCell202A, and SCell202B or SCell202B is described as SCell202B / SCell202B. In addition, when steps S11a and S11b are not distinguished, they are simply called step S11, when steps S12a and S12b are not distinguished, they are simply called step S12, and when steps S13a and S13b are not distinguished, they are simply called step S13.

[0082] Step S12 may be a step in which the UE 100 receives the MBS-related information from the MCG 201A / PCell 202A. The UE 100 may receive the MBS-related information from the MCG 201A / PCell 202A by an RRC Reconfiguration message, a paging message, a SIB (BCCH), an MCCH, a MAC control element (MAC CE), or downlink control information (DCI).

[0083] The MBS-related information received by the UE 100 may include at least one of MBS session information indicating an MBS session provided by the SCG 201B / SCell 202B, frequency-related information regarding a frequency at which the MBS session is provided, MBS setting information indicating a setting for MBS reception, and cell identification information indicating the SCG 201B / SCell 202B. This allows the UE 100 to smoothly receive MBS from the SCG 201B / SCell 202B.

[0084] The MBS related information that the UE 100 receives from the MCG 201A / PCell 202A may be a session start notification indicating the start of an MBS session in the SCG 201B / SCell 202B. This allows the UE 100 to start MBS reception in the SCG 201B / SCell 202B in accordance with the start of the MBS session in the SCG 201B / SCell 202B. The MBS related information that the UE 100 receives from the MCG 201A / PCell 202A may be session modification information (session modification notification) indicating a change of the MBS session in the SCG 201B / SCell 202B, or a session stop notification indicating the stop of the MBS session. The stop of the MBS session may be notified as session modification information.

[0085] The MBS-related information that the UE 100 receives from the MCG 201A / PCell 202A may be MTCH setting information related to the MTCH in the SCG 201B / SCell 202B. This allows the UE 100 to receive the MTCH from the SCG 201B / SCell 202B without receiving the MTCH setting information from the SCG 201B / SCell 202B. Here, in the case of DC, the MTCH setting information transmitted by the MCG 201A (MN 200A) may be obtained from the SCG 201B (SN 200B). That is, the SN 200B that manages the SCG 201B may transmit the MTCH setting information to the MN 200A that manages the MCG 201A by using a network interface (such as Xn or X2).

[0086] The MBS related information that the UE 100 receives from the MCG 201A / PCell 202A may be MCCH setting information related to the MCCH in the SCG 201B / SCell 202B. This allows the UE 100 to receive the MCCH from the SCG 201B / SCell 202B without receiving the MCCH setting information from the SCG 201B / SCell 202B. Here, in the case of DC, the MCCH setting information transmitted by the MCG 201A (MN 200A) may be acquired from the SCG 201B (SN 200B). That is, the SN 200B that manages the SCG 201B may transmit the MCCH setting information to the MN 200A that manages the MCG 201A using a network interface (such as Xn or X2). In the following, the MTCH setting information and / or the MCCH setting information may be referred to as MBS setting information.

[0087] The MBS-related information that the UE 100 receives from the MCG 201A / PCell 202A may be notification information indicating that MBS setting information indicating the setting of MBS reception in the SCG 201B / SCell 202B is transmitted from the SCG 201B / SCell 202B. This allows the UE 100 to recognize that the MBS setting information of the SCG 201B / SCell 202B is not provided from the MCG 201A / PCell 202A.

[0088] Step S12 may be a step in which the UE 100 transmits the MBS-related information to the MCG 201A / PCell 202A. The UE 100 may transmit the MBS-related information to the MCG 201A / PCell 202A by an RRC message, a MAC CE, a PDCP Control PDU (Protocol Data Unit), or uplink control information (UCI).

[0089] The MBS-related information transmitted by the UE 100 to the MCG 201A / PCell 202A may include at least one of MBS session information indicating an MBS session that the UE 100 is receiving or is interested in receiving, frequency-related information regarding a frequency at which the MBS session is provided, and priority information indicating whether the UE 100 prioritizes MBS reception or unicast reception. This allows the MCG 201A / PCell 202A to grasp the interest of the UE 100 in MBS.

[0090] The MBS-related information that the UE 100 transmits to the MCG 201A / PCell 202A may be an MBS Interest Indication (MII) regarding an MBS session that the UE 100 is receiving or is interested in receiving. The MII includes at least one of MBS session information indicating an MBS session that the UE 100 is receiving or is interested in receiving, frequency-related information regarding a frequency at which the MBS session is provided, and priority information indicating whether the UE 100 prioritizes MBS reception or unicast reception.

[0091] When the MCG 201A provides an MBS session that the UE 100 is receiving or is interested in receiving, the UE 100 may transmit the MII to the MCG 201A. Alternatively, when the SCG 201B / SCell 202B provides an MBS session that the UE 100 is receiving or is interested in receiving, the UE 100 may transmit the MII indicating that the SCG 201B / SCell 202B provides the MBS session to the MCG 201A / PCell 202A.

[0092] In the case of DC, it is desirable that the MBS-related information (e.g., MII) received by the MCG 201A (MN 200A) from the UE 100 be shared with the SCG 201B (SN 200B). Therefore, the MN 200A that manages the MCG 201A may transmit the MBS-related information (e.g., MII) received from the UE 100 to the SN 200B that manages the SCG 201B, using a network interface (Xn or X2, etc.).

[0093] The MBS-related information transmitted by the UE 100 to the MCG 201A / PCell 202A may be MBS reception gap information indicating the timing at which the UE 100 suspends communication with the MCG 201A / PCell 202A in order to receive an MBS from the SCG 201B / SCell 202B (hereinafter referred to as an "MBS reception gap") This enables the UE 100 to efficiently receive an MBS from the SCG 201B / SCell 202B using the MBS reception gap while maintaining a connection with the MCG 201A / PCell 202A.

[0094] The MBS-related information transmitted by the UE 100 to the MCG 201A / PCell 202A may be information for the UE 100 to receive MBS data retransmission from the SCG 201B / SCell 202B (or the MCG 201A / PCell 202A). The information indicates packets that the PDCP layer has successfully and / or unsuccessfully received, and may be, for example, a PDCP Status Report. The PDCP Status Report may include one or more of FMC (First missing packet: sequence number information of the first packet that has failed to be received) and Bitmap (bitmap information indicating success / failure of packet reception after the FMC). The information may be shared between the MN 200A and the SCell 202B (the MN 200A may transmit the information to the SN 200B).

[0095] 12 is a diagram showing a third operation example according to the embodiment. The third operation example is an operation example in which the UE 100 monitors the physical downlink control channel (PDCCH) of the SCG 201B / SCell 202B in a scenario in which DC or CA is performed.

[0096] In step S21, the UE 100 starts DC or CA.

[0097] In step S22, UE 100 performing MBS reception in SCG201B / SCell202B monitors PDCCH in SCG201B / SCell202B using RNTI for performing MBS reception in SCG201B / SCell202B. The RNTI for performing MBS reception is called RNTI for MBS reception. The RNTI for MBS reception may be at least one of RNTI for MTCH for receiving MTCH, RNTI for MCCH for receiving MCCH, and RNTI for change notification for receiving MCCH change notification.

[0098] In step S23, the SCG 201B / SCell 202B is deactivated. For example, the UE 100 deactivates the SCG 201B / SCell 202B in response to the SCG 201B / SCell 202B receiving a deactivation instruction from the MCG 201A / PCell 202A via the MAC CE.

[0099] In step S24, even if the SCG201B / SCell202B is deactivated, the UE 100 continues to monitor the PDCCH in the SCG201B / SCell202B by using the RNTI for MBS reception.

[0100] This allows the UE 100 to continue receiving the MBS in the SCG 201B / SCell 202B even if the SCG 201B / SCell 202B is deactivated.

[0101] 13 is a diagram showing a fourth operation example according to the embodiment. The fourth operation example is an operation example in which the UE 100 transmits an MII in a scenario in which DC is performed.

[0102] In step S31, the UE 100 starts the DC.

[0103] In step S32, the UE 100 identifies a cell group (CG) that provides an MBS session that the UE 100 is receiving or is interested in receiving, from among the MCG 201A and the SCG 201B.

[0104] In step S33, the UE 100 transmits the MII related to the MBS session to the cell group identified in step S32.

[0105] This allows the UE 100 to transmit the MII to an appropriate CG on the assumption that the UE 100 can receive the MBS data from the SCG 201B.

[0106] 14 is a diagram showing a fifth operation example according to the embodiment. The fifth operation example is an operation example in which the MN 200A and the SN 200B communicate with each other in a scenario in which DC is performed.

[0107] In step S41, the UE 100 starts the DC.

[0108] In step S42, the MN 200A communicates with the SN 200B. The MN 200A may obtain an MII related to an MBS session that the UE 100 is receiving or is interested in receiving, and transmit the MII to the SN 200B. Alternatively, when the SN 200B obtains the MII of the UE 100, the MN 200A may receive the MII from the SN 200B. Step S42 may be performed before step S41.

[0109] In step S43, the MCG 201A (MN 200A) or the SCG 201B (SN 200B) transmits an MBS to the UE 100.

[0110] In this way, the MCG 201A (MN 200A) and the SCG 201B (SN 200B) share the interest of the UE 100 in the MBS, and thus it becomes possible to perform efficient communication with the UE 100 taking into consideration the MBS interest.

[0111] 15 is a diagram showing a sixth operation example according to the embodiment. The sixth operation example is an operation example in which the MN 200A and the SN 200B communicate with each other in a scenario in which DC is performed.

[0112] In step S51, the UE 100 starts the DC.

[0113] In step S52, the SN 200B communicates with the MN 200A. The SN 200B transmits, to the MN 200A, MBS setting information indicating settings for the UE 100 to receive the MBS in the SCG 201B.

[0114] In step S53, the SN 200B transmits an MBS to the UE 100.

[0115] In this way, by sharing the MBS setting information of the SN 200B with the MN 200A, the MN 200A can perform efficient communication with the UE 100 by taking into account the MBS setting information. For example, the MN 200A performs scheduling or activation / deactivation control of the SCG 201B / SCell 202B by taking into account the MBS setting information of the SN 200B. The MN 200A may transmit the MBS setting information of the SN 200B to the UE 100.

[0116] (Example) Next, a first embodiment to a ninth embodiment will be described on the premise of the above-mentioned embodiment. These embodiments are not limited to being implemented separately and independently, and two or more embodiments may be combined and implemented. In addition, in the operation flow of each of the following embodiments, it is not necessary to execute all steps, and only some steps may be executed. In addition, in the operation flow of each of the following embodiments, the order of steps may be changed. In the following embodiments, MCG201A may be replaced with MN200A, SCG201B may be replaced with SN200B, and PCell202A may be replaced with base station (gNB200).

[0117] (1) First Example 16 is a diagram showing a first embodiment. Here, it is assumed that DC or CA has been started, and the UE 100 is waiting for the start of an MBS session to be provided from the SCG 201B / SCell 202B.

[0118] In step S101, the MCG 201A / PCell 202A detects the start of an MBS session to be provided by the SCG 201B / SCell 202B. In the case of CA, since the PCell 202A and the SCell 202B belong to the same gNB 200, the gNB 200 can grasp the start of an MBS session to be provided by the SCell 202B. In the case of DC, the MCG 201A (MN 200A) may obtain session start information from the AMF 300 (core network) and / or from the SN 200B.

[0119] In step S102, the MCG 201A / PCell 202A notifies the UE 100 of the start of the MBS session of the SCG 201B / SCell 202B by an RRC Reconfiguration message, a paging message, an SIB, or an MCCH. The notification (session start notification) includes at least one of the following information.

[0120] MBS Session Information This is information indicating the MBS session that the SCG201B / SCell202B is to provide, and is, for example, a session ID, a TMGI, a source-specific IP multicast address, a G-RNTI, and the like.

[0121] Frequency-related information For example, it is at least one of frequency information indicating the frequency (carrier frequency) at which the MBS session to be provided by SCG201B / SCell202B will be provided, BWP information indicating the bandwidth portion (BWP) at which the MBS session will be provided, and CFR information indicating the CFR (Common Frequency Resource) at which the MBS session will be provided.

[0122] MBS setting information for SCG201B / SCell202B For example, it is at least one of the MCCH setting information and the MTCH setting information of the SCG201B / SCell202B.

[0123] Cell identification information for SCG201B / SCell202B For example, it is the cell ID or cell index of the SCG 201B / SCell 202B. For the SCG 201B, it may be the cell ID or cell index of the PSCell.

[0124] In step S103, UE 100 starts MBS reception in SCG201B / SCell202B in response to reception of the session start notification. For example, UE 100 may switch a receiver (reception circuit, RF circuit) for performing MBS reception in SCG201B / SCell202B to an on state. That is, UE 100 may keep a receiver for performing MBS reception in SCG201B / SCell202B in an off state until a session start notification of SCG201B / SCell202B is received from MCG201A / PCell202A. This reduces power consumption of UE 100. Alternatively, UE 100 may start PDCCH monitoring for SCG201B / SCell202B using the RNTI for MBS in response to reception of the session start notification of SCG201B / SCell202B from MCG201A / PCell202A while maintaining the receiver in an on state.

[0125] In step S104, the UE 100 receives the MTCH (MBS data) from the SCG 201B / SCell 202B based on the session start notification received from the MCG 201A / PCell 202A.

[0126] In this way, according to the first embodiment, the MCG 201A / PCell 202A notifies the UE 100 of the start of the MBS session of the SCG 201B / SCell 202B. This enables the UE 100 to efficiently receive the MBS in the SCG 201B / SCell 202B.

[0127] In addition, MCG201A / PCell202A may notify UE 100 of a session change or session stop of SCG201B / SCell202B. This allows UE 100 to grasp the session change or session stop of SCG201B / SCell202B. Such a session change notification or session stop notification is transmitted in a similar manner to the above-mentioned session start notification, and may include information elements similar to those of the above-mentioned session start notification.

[0128] The MCG 201A / PCell 202A may notify the UE 100 of the change in the MBS-SIB of the SCG 201B / SCell 202B (or the value tag of the MBS-SIB of the SCG 201B / SCell 202B). This allows the UE 100 to grasp the change in the MBS-SIB of the SCG 201B / SCell 202B.

[0129] (2) Second Example 17 is a diagram showing Example 2. Here, it is assumed that DC or CA has been started.

[0130] In step S201, the SCG201B / SCell202B shares its own MBS setting information with the MCG201A / PCell202A. For example, the SCG201B (SN200B) transmits its own MBS setting information to the MCG201A (MN200A). The SCG201B (SN200B) may transmit its own MBS setting information to the MCG201A (MN200A) when triggered by a change in its own MBS setting or an inquiry from the MN200A.

[0131] The SCG 201B (SN 200B) may request the MCG 201A (MN 200A) to transmit the MBS setting information from the MCG 201A (MN 200A). When the MCG 201A (MN 200A) accepts the request, it may transmit a response to that effect to the SCG 201B (SN 200B).

[0132] In step S202, the SCG 201B / SCell 202B may notify the UE 100, by MBS-SIB, that the MCCH (MTCH setting information) of the SCG 201B / SCell 202B is transmitted from the MCG 201A / PCell 202A. Here, the SCG 201B / SCell 202B may transmit the MCCH setting information of the MCG 201A / PCell 202A by MBS-SIB. This allows the UE 100 to smoothly receive the MCCH of the MCG 201A / PCell 202A.

[0133] The MCCH setting information includes at least one of settings related to the MCCH, for example, a repetition period, an offset, a first subframe, a duration, a modification period, and scheduling information (on-duration, a DRX inactivity timer, a scheduling period, and a start offset). The MCCH setting information may include at least one of a frequency of the MCCH of the MCG 201A / PCell 202A, an ID of a cell that provides the MCCH of the MCG 201A / PCell 202A, BWP information / CFR information of the MCCH of the MCG 201A / PCell 202A, and MBS session information.

[0134] In response to receiving the MBS-SIB from the SCG 201B / SCell 202B, the UE 100 may start monitoring the MCCH of the MCG 201A / PCell 202A based on the MBS-SIB.

[0135] In step S203, the MCG201A / PCell202A may notify the UE 100, by the MBS-SIB, that the MCCH of the MCG201A / PCell202A includes the MBS setting information (MTCH setting information) of the SCG201B / SCell202B. Here, the MCG201A / PCell202A may notify the UE 100, by the MBS-SIB, of at least one of the MBS providing frequency of the SCG201B / SCell202B, the ID of the cell providing the MBS of the SCG201B / SCell202B, the MBS providing BWP / CFR information of the SCG201B / SCell202B, and the MBS session information.

[0136] In step S204, the MCG201A / PCell202A transmits MBS configuration information (MTCH configuration information) of the SCG201B / SCell202B on the MCCH. The MBS configuration information includes, for example, information of each MTCH of the SCG201B / SCell202B (for example, MBS session information, G-RNTI, MTCH scheduling info (DRX configuration)) and a neighboring cell list that provides the MBS session. The MBS configuration may include at least one of the MBS providing frequency of the SCG201B / SCell202B, the ID of the cell that provides the MBS of the SCG201B / SCell202B, and the MBS providing BWP / CFR information of the SCG201B / SCell202B.

[0137] The UE 100 acquires the MCCH on the MCG 201A / PCell 202A, and receives the MTCH (MBS data) of the SCG 201B / SCell 202B based on the MBS setting information (MTCH setting information) acquired on the MCCH (step S205).

[0138] In this way, according to the second embodiment, the MCG 201A / PCell 202A notifies the UE 100 of the MBS setting information (MTCH setting information) of the SCG 201B / SCell 202B, so that the UE 100 can efficiently receive the MBS in the SCG 201B / SCell 202B. For example, the UE 100 only needs to monitor the MCCH for the MCG 201A / PCell 202A in relation to the MCCH reception, and does not need to monitor the MCCH for the SCG 201B / SCell 202B, so that the power consumption of the UE 100 can be reduced.

[0139] (3) Third Example 18 is a diagram showing a third embodiment, in which it is assumed that DC or CA has been started.

[0140] In step S301, the MCG201A / PCell202A notifies the UE 100, by the MBS-SIB (or MCCH), that MBS setting information of the MBS session provided by the SCG201B / SCell202B is transmitted from the SCG201B / SCell202B. Here, the MCG201A / PCell202A may notify the UE 100 of the MCCH setting information of the SCG201B / SCell202B by the MBS-SIB (or MCCH). In addition, the MCG201A / PCell202A may notify the UE 100 of at least one of the frequency information of the MCCH of the SCG201B / SCell202B, the ID of the cell providing the MCCH of the SCG201B / SCell202B, the BWP / CFR information of the MCCH of the SCG201B / SCell202B, and the MBS session information.

[0141] In step S302, the UE 100 may receive the MBS-SIB (MCCH configuration information) on the MCG 201A / PCell 202A. When the UE 100 has acquired the MCCH configuration information of the SCG 201B / SCell 202B from the MCG 201A / PCell 202A in step S301, the UE 100 does not need to receive the MBS-SIB on the MCG 201A / PCell 202A.

[0142] In step S303, the UE 100 receives the MCCH (MTCH configuration information) on the MCG 201A / PCell 202A based on the MCCH configuration information acquired in step S301 or S302.

[0143] In step S304, the UE 100 receives the MTCH (MBS data) on the SCG 201B / SCell 202B based on the MTCH configuration information acquired in step S303.

[0144] In this way, according to the third embodiment, the MCG 201A / PCell 202A notifies the UE 100 that the MBS setting information of the SCG 201B / SCell 202B is transmitted from the SCG 201B / SCell 202B. This enables the UE 100 to efficiently receive the MBS in the SCG 201B / SCell 202B.

[0145] (4) Fourth Example 19 is a diagram showing a fourth embodiment, in which it is assumed that DC or CA has been started.

[0146] In step S401, the UE 100 is receiving or is interested in receiving an MBS session provided by the SCG 201B / SCell 202B.

[0147] In step S402, the UE 100 transmits an MII indicating that the UE 100 is receiving or is interested in receiving an MBS session provided by the SCG 201B / SCell 202B to the MCG 201A / PCell 202A. For example, the MII includes at least one of the following information: MBS session information, a frequency and cell ID of the SCG 201B / SCell 202B, and information indicating whether or not to prioritize the reception of the MBS session in the SCG 201B / SCell 202B (for example, whether or not the same service can be received in the MCG 201A / PCell 202A).

[0148] In step S403, the MCG 201A / PCell 202A performs activation / deactivation control of the SCG 201B / SCell 202B based on the MII from the UE 100. For example, the MCG 201A / PCell 202A controls not to deactivate or to activate a cell of the SCG 201B / SCell 202B that provides an MBS session that the UE 100 is receiving or is interested in receiving.

[0149] The MCG 201A / PCell 202A may set a new session or radio bearer for the UE 100 to receive MBS at the MCG 201A / PCell 202A based on the MII from the UE 100. The MCG 201A / PCell 202A may perform handover control of the UE 100 based on the MII from the UE 100.

[0150] In this way, according to the fourth embodiment, the UE 100 transmits an MII indicating that the UE 100 is receiving or is interested in receiving an MBS session provided by the SCG 201B / SCell 202B to the MCG 201A / PCell 202A. This enables the MCG 201A / PCell 202A to perform appropriate communication control in consideration of the UE 100's MBS interest in the SCG 201B / SCell 202B.

[0151] (5) Fifth Example 20 is a diagram showing a fifth embodiment, in which it is assumed that DC or CA has been started.

[0152] In step S501, the UE 100 that is receiving or is interested in receiving an MBS session provided by the SCG 201B / SCell 202B determines an MBS reception gap (MBS reception gap pattern) for receiving the MBS from the SCG 201B / SCell 202B. The MBS reception gap may be a timing when the MTCH is scheduled in the SCG 201B / SCell 202B. The MBS reception gap may include a switching time for RF switching (receiver frequency switching) in the UE 100.

[0153] In step S502, the UE 100 transmits a message including reception gap information indicating the determined MBS reception gap to the MCG 201A / PCell 202A. The reception gap information may be information indicating a reception gap pattern by its start timing and bitmap pattern. The message including the reception gap information may include information such as the cell ID and frequency of the SCG 201B / SCell 202B. The reception gap information may be information indicating an MBS reception gap that the UE 100 requests to be set. The MCG 201A / PCell 202A that receives the message may set the MBS reception gap to the UE 100 by, for example, an RRC Reconfiguration message based on the reception gap information.

[0154] In step S503, the MCG 201A / PCell 202A performs scheduling control so as not to perform scheduling to the UE 100 in the MBS reception gap. Specifically, the MCG 201A / PCell 202A performs control so as not to perform unicast communication with the UE 100 at the timing (MBS reception gap) when the UE 100 receives an MBS from the SCG 201B / SCell 202B.

[0155] In step S504, the UE 100 performs MBS reception from the SCG 201B / SCell 202B in the MBS reception gap. For example, the UE 100 receives MBS data transmitted on the MTCH from the SCG 201B / SCell 202B in the MBS reception gap.

[0156] In this way, according to the fifth embodiment, the UE 100 notifies the MCG 201A / PCell 202A of an MBS reception gap (MBS reception gap pattern) for receiving the MBS from the SCG 201B / SCell 202B. This makes it possible to receive the MBS from the SCG 201B / SCell 202B while maintaining a connection with the MCG 201A / PCell 202A, even if the number of receivers of the UE 100 is insufficient.

[0157] Note that instead of the UE 100 notifying the MCG 201A / PCell 202A of the MBS reception gap (MBS reception gap pattern), the SCG 201B / SCell 202B may notify the MCG 201A / PCell 202A of the MTCH setting information (MTCH scheduling information). In this way, the MCG 201A / PCell 202A can grasp the timing at which the SCG 201B / SCell 202B transmits the MBS by the notification from the SCG 201B / SCell 202B, and can control not to perform unicast communication with the UE 100 at that timing.

[0158] Alternatively, instead of UE 100 notifying MCG 201A / PCell 202A of the MBS reception gap (MBS reception gap pattern), UE 100 may transfer MTCH configuration information (MTCH scheduling information) acquired from SCG 201B / SCell 202B to MCG 201A / PCell 202A. In this way, MCG 201A / PCell 202A can grasp the timing at which SCG 201B / SCell 202B performs MBS transmission based on the information transferred from UE 100, and can control not to perform unicast communication with UE 100 at that timing.

[0159] (6) Sixth Example Fig. 21 is a diagram showing the operation of a MAC entity of the UE 100 according to the sixth embodiment. Fig. 21 shows an example of a modification of the technical specifications (TS38.321) of the MAC layer.

[0160] The SCell 202B configured in the UE 100 may be deactivated by the control of the PCell 202A. In a typical CA operation, the UE 100 does not monitor the PDCCH of the deactivated SCell 202B. In addition, the UE 100 does not transmit a physical uplink control channel (PUCCH) or a random access channel (RACH) to the deactivated SCell 202B. However, the activation / deactivation of the SCell 202B in a typical CA is intended for unicast communication. When the MBS supports CA, it is desirable to enable MBS reception independently of the activation / deactivation of the SCell 202B.

[0161] For example, if the UE 100 does not monitor the PDCCH in the SCell 202B at all, the UE 100 does not monitor the PDCCH using a group RNTI (G-RNTI) for receiving the MTCH, and therefore the UE 100 cannot receive the MTCH. Here, the G-RNTI corresponds to the RNTI for the MTCH.

[0162] Also, if UE 100 does not perform any PUCCH transmission in SCell 202B, HARQ feedback in MBS reception cannot be performed for SCell 202B. Furthermore, if UE 100 does not perform any RACH transmission in SCell 202B, an on-demand system information request (on-demand SI request) cannot be made to SCell 202B, and transmission of MBS-SIB cannot be requested from SCell 202B.

[0163] In the sixth embodiment, as shown in FIG. 21, for each configured SCell 202B, if the SCell 202B is deactivated, the UE 100 performs the following operation.

[0164] The MAC entity of the UE 100 does not transmit on RACH on the SCell 202B, except for an on-demand SI request for an MBS-SIB of interest. In other words, even if the SCell 202B is deactivated, the UE 100 is allowed to transmit the RACH to the SCell 202B when making an on-demand SI request for an MBS-SIB of interest.

[0165] The MAC entity of the UE 100 does not monitor the PDCCH on the SCell 202B, except for G-RNTI, MCCH-RNTI, and Notification-RNTI for MBS reception of interest. The MCCH-RNTI corresponds to the RNTI for MCCH, and the Notification-RNTI corresponds to the RNTI for change notification. In other words, even if the SCell 202B is deactivated, the UE 100 is allowed to monitor the PDCCH of the SCell 202B using the G-RNTI, MCCH-RNTI, and Notification-RNTI for MBS reception of interest.

[0166] The MAC entity of the UE 100 does not transmit PUCCH on the SCell 202B, except for HARQ feedback for MBS reception. In other words, even if the SCell 202B is deactivated, the UE 100 is allowed to transmit PUCCH to the SCell 202B when performing HARQ feedback for MBS reception.

[0167] Although such an operation is related to CA, the same operation can be applied to DC. In the case of DC, SCell202B in the above-mentioned operation is replaced with SCG201B (or PSCell of SCG201B).

[0168] 22 is a diagram showing a sixth embodiment, in which the operation relating to PDCCH monitoring will be mainly explained.

[0169] In step S601, the UE 100 is receiving or is interested in receiving an MBS session provided by the SCG 201B / SCell 202B.

[0170] In step S602, the UE 100 monitors the PDCCH (DCI) of the SCG 201B / SCell 202B using the G-RNTI, the MCCH-RNTI, and the Notification RNTI. The UE 100 may further monitor the SI-RNTI for receiving the MBS-SIB.

[0171] In step S603, the MCG 201A / PCell 202A deactivates the SCG 201B / SCell 202B, for example, by sending a deactivation instruction for the SCG 201B / SCell 202B to the UE 100 and the SCG 201B / SCell 202B.

[0172] In step S604, even if the SCG201B / SCell202B is deactivated, the UE 100 continues to monitor the PDCCH using the G-RNTI, the MCCH-RNTI, the Notification RNTI, and the SI-RNTI, and receives DCI from the SCG201B / SCell202B.

[0173] In step S605, the UE 100 receives the MTCH (MBS data) from the SCG 201B / SCell 202B based on the DCI received by monitoring the PDCCH.

[0174] In this way, according to the fifth embodiment, even if the SCG201B / SCell202B is deactivated, the UE 100 continues to monitor the PDCCH using the G-RNTI, the MCCH-RNTI, the Notification RNTI, and the SI-RNTI. This makes it possible to improve the continuity of reception of the MBS.

[0175] (7) Seventh Example 23 is a diagram showing a seventh embodiment, in which the operation in the case of DC will be described.

[0176] In step S701, the UE 100 (RRC layer) generates an MII. The MII generated by the UE 100 is assumed to be an RRC message.

[0177] In step S702, the UE 100 (RRC layer) determines whether the MBS session of interest is provided by the MCG 201A or the SCG 201B.

[0178] In steps S703 and S704, the UE 100 transmits the MII to the CG in which the MBS session of interest is provided. For example, the RRC layer of the UE 100 passes the MII to a MAC entity corresponding to the CG.

[0179] The RRC layer of the UE 100 transmits the MII via a signaling radio bearer (SRB) corresponding to the CG. For example, if the MBS session of interest is provided by the MCG 201A (step S702: NO), the RRC layer of the UE 100 transmits the MII to the MCG 201A via SRB1 in step S703. The SRB1 is an SRB established between the UE 100 and the MCG 201A (MN 200A). On the other hand, if the MBS session of interest is provided by the SCG 201B (step S702: YES), the RRC layer of the UE 100 transmits the MII to the SCG 201B via SRB3 in step S704. The SRB3 is an SRB established between the UE 100 and the SCG 201B (SN 200B).

[0180] In addition, when both CGs provide the MBS session of interest (for example, when TMGI#1 is provided by MCG201A and TMGI#2 is provided by SCG201B), UE100 may transmit MII to both CGs. Here, UE100 may transmit the same message (a copy of the same) to both CGs. UE100 may transmit separate messages (only related to TMGI#1 / only related to TMGI#2, etc.) to the corresponding CGs.

[0181] Thus, according to the seventh embodiment, the UE 100 transmits the MII to the CG in which the MBS session of interest is provided. For example, if the MBS session of interest is provided by the SCG 201B, the UE 100 transmits the MII to the SCG 201B by the SRB3. This makes it possible to transmit the MII to an appropriate destination.

[0182] (8) Eighth Example 24 is a diagram showing the eighth embodiment, in which the operation in the case of DC will be described.

[0183] In step S801, the MCG 201A acquires the MII (MBS interest information) of the UE 100. For example, the MCG 201A receives the MII from the UE 100, or acquires the MII from the AMF 300 (core network).

[0184] In step S802, the MCG 201A (MN 200A) recognizes that the MBS session of interest to the UE 100 is provided by the SCG 201B (SN 200B). Here, information on the MBS session provided by the SN 200B may be provided by the AMF 300 (core network) and / or the SN 200B. The information on the MBS session may be set by OAM (Operation Administration and Maintenance). The MCG 201A (MN 200A) may identify the SCG 201B (SN 200B) from information on the frequency on which the MBS session is provided.

[0185] In step S803, the MCG 201A (MN 200A) transmits the MII of the UE 100 to the SCG 201B (SN 200B). The MII may be included in an Xn message (inter-base station communication message) transmitted from the MN 200A to the SN 200B. The Xn message may be an SN Addition message used at the start of DC and / or an SN Modification message used to change the settings of the SCG 201B (SN 200B) after the start of DC. The MII may be included as UE context in these messages. The Xn message may be an X2 message.

[0186] As described above, the MII includes at least one of MBS session information (such as a session ID, TMGI, or G-RNTI), MBS frequency information, BWP (CFR) information, and priority information between MBS and unicast. The MII or Xn message may include at least one of an MBS tunnel identifier related to the MB-UPF (Multicast Broadcast User Plane Function) of the core network and a UE identifier (such as an XnAP UE-ID).

[0187] In step S804, the SCG201B (SN200B) schedules MBS transmission and unicast communication based on the Xn message (MII) received from the MCG201A (MN200A). For example, the SCG201B (SN200B) performs operations such as allocating unicast communication resources to the UE 100 while avoiding multicast, by scheduling. The SCG201B (SN200B) may transmit MBS setting information to the UE 100 via an RRC Reconfiguration message or the MCG201A based on the Xn message (MII).

[0188] In this way, according to the eighth embodiment, the MCG 201A (MN 200A) transmits the MII of the UE 100 to the SCG 201B (SN 200B). This enables the SCG 201B (SN 200B) to appropriately perform communication control (scheduling, etc.) of the UE 100 in consideration of the MBS interest of the UE 100.

[0189] (9) Ninth Example 25 is a diagram showing a ninth embodiment, in which the operation in the case of DC will be described.

[0190] In step S901, the SCG 201B acquires the MII (MBS interest information) of the UE 100. For example, the SCG 201B receives the MII from the UE 100, or acquires the MII from the AMF 300 (core network).

[0191] In step S902, the SCG 201B (SN 200B) transmits to the MCG 201A (MN 200A) the MII of the UE 100. The SCG 201B (SN 200B) may transmit the MII to the MCG 201A (MN 200A) when triggered by notification of the MII from the UE 100 or an inquiry from the MN 200A.

[0192] The MII may be included in an Xn message (inter-base station communication message) transmitted from the SN 200B to the MN 200A. The Xn message may be a gNB Configuration Update message related to a setting change of the SN 200B, a response message to an SN Addition message, and / or a response message to an SN Modification message. The MII may be included as UE context in these messages. The information included in the MII and the Xn message is the same as that in the above-mentioned eighth embodiment. The Xn message may be an X2 message.

[0193] In step S903, the MCG 201A (MN 200A) performs activation / deactivation control of the SCG 201B / SCell 202B based on the Xn message (MII) received from the SCG 201B (SN 200B). The MCG 201A (MN 200A) may set a new session or radio bearer for the UE 100 to receive MBS in the MCG 201A / PCell 202A based on the Xn message (MII).

[0194] (Other embodiments) In the above-mentioned embodiment and example, DC may be multi-connectivity (MC). In MC, UE 100 communicates with two or more base stations simultaneously. For example, UE 100 communicates with one master base station (MN) and two secondary base stations (SN), i.e., three base stations simultaneously.

[0195] In the above-described embodiment and example, when the gNB200 (MN200A, SN200B) is configured with a CU and a DU (i.e., functionally divided) and both units are connected with an F1 interface, the CU that has acquired the MII of the UE100 may notify the DU of the MII on the F1 interface. This enables the scheduler provided in the DU to perform scheduling that takes the MII into consideration.

[0196] The above-mentioned operational flows are not limited to being implemented separately and independently, but can be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow.

[0197] In the above-mentioned embodiment and example, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB) or a 6G base station. The base station may be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may be a DU of the IAB node. The user equipment may be an MT (Mobile Termination) of the IAB node.

[0198] A program may be provided that causes a computer to execute each process performed by UE100 or gNB200. The program may be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in a computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. In addition, a circuit that executes each process performed by UE100 or gNB200 may be integrated, and at least a part of UE100 or gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0199] As used in this disclosure, the terms "based on" and "depending on" do not mean "based only on" or "depending only on," unless otherwise specified. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "based only on" and "based at least in part on." Additionally, "obtain / acquire" may mean obtaining information from stored information, from information received from other nodes, or by generating information. The terms "include," "comprise," and variations thereof do not mean including only the items listed, but may include only the items listed, or may include additional items in addition to the items listed. Additionally, the term "or" as used in this disclosure is not intended to be an exclusive or. Additionally, any reference to elements using designations such as "first," "second," etc., as used in this disclosure is not intended to generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some manner. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles are intended to include the plural unless the context clearly indicates otherwise.

[0200] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes, etc. are possible without departing from the spirit of the invention.

[0201] This application claims priority to Japanese Patent Application No. 2021-119144 (filed July 19, 2021), the entire contents of which are incorporated herein by reference. [Explanation of symbols]

[0202] 1: Mobile communication systems 10:NG-RAN 20:5GC 100:UE 110: Receiving unit 120: Transmitter 130: Control section 200: gNB 200A:MN 200B :SN 201A: MCG 201B: SCG 202A: PCell 202B:SCell 210: Transmission unit 220: Receiving unit 230: Control section 240: Backhaul communication unit 300:AMF / UPF

Claims

1. A communication method for use in a mobile communication system supporting a multicast and broadcast service (MBS), comprising: A user equipment performing carrier aggregation (CA) communicates with a primary cell in the CA; The user equipment performs MBS reception from a secondary cell in the CA, The communicating step includes the user equipment receiving, from the primary cell, MBS-related information regarding the MBS reception from the secondary cell; The MBS-related information includes configuration information regarding an MBS control channel (MCCH) in the secondary cell. Communication methods.

2. The MBS-related information further includes at least one of MBS session information indicating an MBS session provided by the secondary cell, frequency-related information regarding a frequency on which the MBS session is provided, and cell identification information indicating the secondary cell. The communication method according to claim 1 .

3. A user device, A communication unit that performs carrier aggregation (CA), The communication unit receives a multicast broadcast service (MBS) from a secondary cell in the CA, The communication unit receives MBS-related information regarding the MBS reception from the secondary cell from a primary cell in the CA; The MBS-related information includes configuration information regarding an MBS control channel (MCCH) in the secondary cell. User equipment.

4. A network device supporting a Multicast and Broadcast Service (MBS), comprising: A communication unit that communicates with a user device that performs carrier aggregation (CA), The communication unit transmits an MBS to the user equipment in a secondary cell in the CA, The communication unit transmits, in a primary cell in the CA, MBS-related information regarding reception of the MBS from the secondary cell to the user equipment; The MBS-related information includes configuration information regarding an MBS control channel (MCCH) in the secondary cell. Network device.

5. A mobile communication system for providing a multicast and broadcast service (MBS) from a network device to a user device, comprising: The user equipment performing carrier aggregation (CA) receives a multicast / broadcast service (MBS) from a secondary cell in the CA, The network device transmits, in a primary cell in the CA, MBS-related information regarding reception of the MBS from the secondary cell to the user device; The MBS-related information includes configuration information regarding an MBS control channel (MCCH) in the secondary cell. Mobile communication system.

6. A program for controlling a user device, Carrier aggregation (CA) is performed; receiving a multicast and broadcast service (MBS) from a secondary cell in the CA; receiving MBS-related information from a primary cell in the CA regarding the MBS reception from the secondary cell; The MBS-related information includes configuration information regarding an MBS control channel (MCCH) in the secondary cell. program.

7. A chipset for controlling a user equipment, comprising: Carrier aggregation (CA) is performed; receiving a multicast and broadcast service (MBS) from a secondary cell in the CA; receiving MBS-related information from a primary cell in the CA regarding the MBS reception from the secondary cell; The MBS-related information includes configuration information regarding an MBS control channel (MCCH) in the secondary cell. Chipset.

Citation Information

Patent Citations

  • Communication control method and user terminal

    WO2015141842A1