User equipment, processor, program, network node, and mobile communication system

Abstract

Provided are a user equipment, a processor, a program, a network node, and a mobile communication system that realize a multicast and broadcast service more improved than 5G / LTE in a multicast and broadcast service of 4G / NR.SOLUTION: A communication method performed by a user equipment (UE100) communicating with a first cell (cell #1) in a mobile communication system providing a multicast broadcast service (MBS) includes a step (S106) of transmitting, to the first cell, a message related to an MBS reception timing at which the user equipment performs MBS reception from a second cell (cell #2) belonging to a frequency different from a frequency to which the first cell belongs.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present disclosure relates to a user device, a processor, a program, a network node, and a mobile communication system. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) standard defines the technical specifications for NR (New Radio), a fifth-generation (5G) radio access technology. Compared to LTE (Long Term Evolution), a fourth-generation (4G) radio access technology, NR offers higher speed, larger capacity, higher reliability, and lower latency. 3GPP is currently discussing the formulation of technical specifications for 5G / NR multicast and broadcast services (MBS) (see, for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP contribution: RP-201038, “WID revision: NR Multicast and Broadcast Services” Summary of the Invention

[0004] 5G / NR multicast and broadcast services are expected to provide improved services compared to 4G / LTE multicast and broadcast services.

[0005] Therefore, an object of the present disclosure is to make it possible to realize improved multicast and broadcast services.

[0006] A communication method according to a first aspect is a method executed by a user equipment (UE) communicating with a first cell in a mobile communication system that provides a multicast broadcast service (MBS), the method comprising the steps of: transmitting, to the first cell, a message regarding MBS reception timing at which the user equipment (UE) receives the MBS from a second cell that belongs to a frequency different from that of the first cell;

[0007] A communication method according to a second aspect is a method executed by a network device in a mobile communication system that provides a multicast broadcast service (MBS), the method comprising: receiving, from the user device via the first cell, a message regarding MBS reception timing at which the user device receives the MBS from a second cell that belongs to a frequency different from the frequency to which the first cell belongs.

[0008] A communication method according to a third aspect is a method executed by a user equipment (UE) communicating with a first cell in a mobile communication system providing a multicast broadcast service (MBS), the method comprising the steps of receiving, from the cell, broadcast information indicating an MBS session being provided by the cell in a receive-only mode (ROM) and / or a free-to-air (FTA), and identifying the MBS session being provided by the cell in the ROM and / or the FTA based on the broadcast information. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating a configuration of a mobile communication system according to an embodiment. [Figure 2] 1 is a diagram illustrating a configuration of a UE (user equipment) according to an embodiment. [Figure 3] A diagram showing the configuration of a gNB (base station) according to an embodiment. [Figure 4] FIG. 10 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data. [Figure 5]FIG. 1 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. 1 is a diagram illustrating an overview of MBS traffic distribution according to an embodiment. [Figure 7] FIG. 10 is a diagram illustrating a distribution mode according to the embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of internal processing related to MBS reception of the UE 100 according to the embodiment. [Figure 9] FIG. 10 is a diagram showing another example of internal processing related to MBS reception of the UE 100 according to the embodiment. [Figure 10] FIG. 2 is a diagram for explaining the operation of the mobile communication system according to the embodiment. [Figure 11] FIG. 4 is a diagram illustrating a first operation example according to the embodiment. [Figure 12] FIG. 10 is a diagram illustrating a second operation example according to the embodiment. [Figure 13] FIG. 10 is a diagram illustrating a third operation example according to the embodiment. [Figure 14] FIG. 10 is a diagram illustrating a fourth operation example according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] 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.

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

[0012] 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.

[0013] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user. For example, the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a laptop 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).

[0014] 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 a 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, etc. 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 that performs wireless communication with a UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

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

[0016] 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 NAS (Non-Access Stratum) signaling. The UPF controls data forwarding. The AMF and UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0017] 2 is a diagram showing the configuration of a UE 100 (user equipment) according to the 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 constitute a wireless communication unit that performs wireless communication with the gNB 200.

[0018] The receiving unit 110 performs various types of reception 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.

[0019] The transmitting unit 120 performs various transmissions under the control of the control unit 130. The transmitting 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.

[0020] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes of each layer, which will be described later. 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.

[0021] 3 is a diagram showing the 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.

[0022] 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.

[0023] The receiving unit 220 performs various types of reception 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.

[0024] The control unit 230 performs various controls and processes in the gNB 200. Such processes include processes for each layer, which will be described later. 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.

[0025] The backhaul communication unit 240 is connected to neighboring base stations via an Xn interface, which is an interface between base stations. The backhaul communication unit 240 is connected to the AMF / UPF 300 via an NG interface, which is an interface between a base station and a core network. Note that the gNB 200 may be configured (i.e., functionally divided) with a CU (Central Unit) and a DU (Distributed Unit), and both units may be connected via an F1 interface, which is a fronthaul interface.

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

[0027] 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.

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

[0029] 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 transport channels. The MAC layer of gNB200 includes a scheduler, which determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be allocated to UE100.

[0030] The RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and 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 logical channels.

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

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

[0033] 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).

[0034] 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.

[0035] RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200. 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 UE100 and the RRC of gNB200, UE100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC idle state. When the connection between the RRC of UE100 and the RRC of gNB200 is suspended, UE100 is in an RRC inactive state.

[0036] The NAS layer, which is located 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. Note that the UE 100 has an application layer and the like in addition to the radio interface protocol. Also, the layer below the NAS layer is called the AS layer.

[0037] (MBS Overview) 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 communications, mission-critical communications, V2X (Vehicle to Everything) communications, IPv4 or IPv6 multicast distribution, IPTV (Internet protocol television), group communications, and software distribution.

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

[0039] The multicast service provides a service to a group of UEs 100 participating in the multicast service (multicast session), rather than to all UEs 100. An MBS session used for the multicast service is called a multicast session.

[0040] FIG. 6 is a diagram illustrating an overview of MBS traffic distribution according to the embodiment.

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

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

[0043] 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.

[0044] 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.

[0045] 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.

[0046] In the PTP distribution method, the gNB 200 distributes individual copies of the MBS data packet 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 for one UE 100.

[0047] The PTP distribution method and the PTM distribution method are mainly related to the user plane. There are two control modes for MBS data distribution: a first distribution mode and a second distribution mode.

[0048] FIG. 7 is a diagram showing distribution modes according to the embodiment.

[0049] The first delivery mode (Delivery mode 1: DM1) 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.

[0050] The setting of MBS reception in the first distribution mode is performed by UE-dedicated signaling. For example, the setting of 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.

[0051] The MBS reception configuration includes MBS traffic channel configuration information (hereinafter referred to as "MTCH configuration information") related to the configuration of an MBS traffic channel for transmitting MBS data. The MTCH configuration information includes MBS session information (including an MBS session identifier, described later) related to an MBS session and scheduling information for the MTCH corresponding to this MBS session. The MTCH scheduling information may include discontinuous reception (DRX) configuration for the MTCH. The discontinuous reception configuration may include one or more parameters: 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 (Start Offset, DRX Cycle Offset) of the start subframe of the scheduling or DRX cycle, a start delay slot value (Slot Offset) of the on-duration timer, 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 for HARQ retransmission. The MTCH (Multicast Traffic Channel) is a type of logical channel, and is mapped to a Down Link Shared Channel (DL-SCH), which is a type of transport channel.

[0052] The second delivery mode (Delivery mode 2: DM2) 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.

[0053] 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 the MCCH using, for example, a dedicated RNTI predefined in a technical specification. The RNTI for BCCH reception may be SI-RNTI, and the RNTI for MCCH reception may be MCCH-RNTI.

[0054] In the second distribution mode, the UE 100 may receive MBS data in the following three procedures. First, the UE 100 receives MCCH configuration information from the MBS system information block (MBS SIB) transmitted on the BCCH from the gNB 200. Second, the UE 100 receives the MCCH from the gNB 200 based on the MCCH configuration information. The MCCH transmits MTCH configuration information. The MCCH may include neighboring cell information indicating whether the currently provided MBS session is also provided in a neighboring cell. Third, the UE 100 receives the MTCH (MBS data) based on the MTCH configuration information. Hereinafter, the MTCH configuration information and / or the MCCH configuration information may be referred to as an MBS reception configuration. In the following embodiments, a case where the UE 100 receives an MBS session distributed in the second distribution mode will be mainly described.

[0055] 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 MTCH reception. The G-RNTI may be included in the MBS reception configuration (MTCH configuration information).

[0056] 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, application server, etc., and an IP multicast address indicating the 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. The TMGI, the source-specific IP multicast address, the session identifier, and the G-RNTI are collectively called MBS session information.

[0057] Fig. 8 is a diagram showing an example of internal processing related to MBS reception of the UE 100 according to the embodiment. Fig. 9 is a diagram showing another example of internal processing related to MBS reception of the UE 100 according to the embodiment.

[0058] An MBS Radio Bearer (MRB) is a radio bearer that carries a multicast session or a broadcast session. That is, an MRB may be associated with a multicast session or a broadcast session.

[0059] The MRB and corresponding logical channels (e.g., MTCH) are configured in the UE 100 from the gNB 200 by RRC signaling. The MRB configuration procedure may be separated from the data radio bearer (DRB) configuration procedure. In RRC signaling, one MRB can be configured with "PTM only," "PTP only," or "both PTM and PTP." The bearer type of such an MRB can be changed by RRC signaling.

[0060] 8 shows an example in which a multicast session and a dedicated traffic channel (DTCH) are associated with MRB#1, a multicast session and MTCH#1 are associated with MRB#2, and a broadcast session and MTCH#2 are associated with MRB#3. That is, MRB#1 is a PTP-only MRB, MRB#2 is a PTM-only MRB, and MRB#3 is a PTM-only MRB. Note that DTCH is scheduled using the cell RNTI (C-RNTI). MTCH is scheduled using the G-RNTI.

[0061] The PHY layer of the UE 100 processes user data (received data) received on a PDSCH, which is one of the physical channels, and transmits the data to a downlink shared channel (DL-SCH), which is one of the transport channels. The MAC layer (MAC entity) of the UE 100 processes the data received on the DL-SCH and transmits the received data to a corresponding logical channel (corresponding RLC entity) based on a logical channel identifier (LCID) included in a header (MAC header) included in the received data.

[0062] 9 shows an example in which a DTCH and an MTCH are associated with an MRB associated with a multicast session. Specifically, one MRB is split into two legs, one leg associated with a DTCH and the other leg associated with an MTCH. The two legs are combined in the PDCP layer (PDCP entity). That is, the MRB is an MRB for both PTM and PTP. Such an MRB is sometimes called a split MRB.

[0063] (Mobile communication system operation) Fig. 10 is a diagram for explaining the operation of the mobile communication system 1 according to the embodiment. Note that the numbers indicated by "#" in Fig. 10 may represent identifiers or indexes.

[0064] UE 100, which exists in an overlapping area of ​​cell #1 (first cell) and cell #2 (second cell), communicates with cell #1. That is, cell #1 is the serving cell of UE 100, and cell #2 is a neighboring cell of the serving cell. UE 100 is in an RRC connected state, an RRC idle state, or an RRC inactive state in cell #1.

[0065] Cell #1 operates on frequency (carrier frequency) #1, and cell #2 operates on frequency (carrier frequency) #2. This type of frequency relationship is called inter-frequency. Cell #1 is managed by gNB200#1, and cell #2 is managed by gNB200#2. Cell #1 (gNB200#1) belongs to Public Land Mobile Network (PLMN) #1, and cell #2 (gNB200#2) belongs to PLMN#2. This type of PLMN relationship is called inter-PLMN. gNB200#1 and CN20#1 are included in network 50#1 of PLMN#1 (first PLMN). gNB200#2 and CN20#2 are included in network 50#2 of PLMN#2 (second PLMN). Generally, one operator is assigned one PLMN identifier. Each cell broadcasts the identifier of the PLMN to which it belongs.

[0066] UE100 in an RRC connected state in cell #1 performs data communication with cell #1 (gNB200#1). Specifically, UE100 is assigned a C-RNTI from gNB200#1 as an identifier of the RRC connection. gNB200#1 assigns radio resources to UE100 by scheduling for UE100.

[0067] UE 100 in the RRC idle state or the RRC inactive state in cell #1 monitors paging from cell #1 (gNB 200 #1). Specifically, UE 100 monitors paging transmitted from cell #1 (gNB 200 #1) at paging reception timing (paging occasion) determined according to parameters such as its own UE identifier.

[0068] In an embodiment, cell #2 (gNB200#2) transmits MBS data belonging to an MBS session (e.g., a broadcast session) in PTM. Specifically, cell #2 (gNB200#2) transmits MBS data in a second distribution mode. Cell #2 (gNB200#2) may provide the MBS session in Receive-Only Mode (ROM) and / or Free-To-Air (FTA).

[0069] ROM is a mode in which MBS reception is possible even for a UE 100 that does not have a SIM (Subscriber Identity Module) and / or does not have a service contract with an operator (PLMN). For example, the UE 100 may be a device (e.g., a television receiver) that has a downlink reception function but does not have an uplink transmission function. FTA is an application (service) that enables free-to-air content broadcasting. FTA may be one aspect of ROM. MBS sessions provided in FTA may be made available to all users who are not mobile subscribers. In the following, when there is no particular distinction between ROM and FTA, they will be referred to as ROM / FTA.

[0070] For example, UE 100 belongs to PLMN #1. UE 100 may have a SIM of PLMN #1 and / or a service contract with PLMN #1. UE 100 is assumed to be interested in receiving an MBS session provided by PLMN #2, i.e., cell #2 (gNB200 #2). It is assumed that the MBS session provided by cell #2 (gNB200 #2) via ROM / FTA can be received by UE 100 belonging to PLMN #1. However, it may be assumed that the MBS session provided by cell #2 (gNB200 #2) via PTM can be received by UE 100 belonging to PLMN #1, regardless of ROM / FTA. Below, a scenario is mainly assumed in which UE 100 belonging to PLMN #1 receives an MBS session provided by cell #2 (gNB200 #2) via ROM / FTA.

[0071] Here, UE100 communicating with cell #1 (gNB200#1) has a limited number of receivers, which makes it difficult for it to receive MBS from cell #2 (gNB200#2) while maintaining communication with cell #1 (gNB200#1).

[0072] Specifically, it is difficult for UE 100 to receive an MBS from cell #2 (frequency #2), which is an inter-frequency, while maintaining cell #1 (frequency #1) as its own serving cell (serving frequency). For example, UE 100, which has only one receiver, cannot receive an MBS from cell #2 (frequency #2) while receiving from cell #1 (frequency #1). Even if UE 100 has multiple receivers, in a scenario where all of the multiple receivers are being used for communication with network 50 #1 (e.g., carrier aggregation), UE 100 cannot receive an MBS from cell #2 (frequency #2).

[0073] Here, if gNB200#1 (network 50#1) knows the MBS interest of UE100 and the MBS transmission setting (particularly, MBS timing) of gNB200#2, it can communicate with UE100, for example, perform data communication or paging transmission, so as to avoid the timing. This allows UE100 to receive an MBS from cell #2 (gNB200#2) at the timing. However, in an inter-PLMN scenario, gNB200#1 and gNB200#2 belong to different PLMNs, making it difficult to share MBS transmission settings through network cooperation.

[0074] Therefore, UE100 according to the embodiment transmits a message regarding the MBS reception timing at which UE100 receives an MBS from cell #2 to cell #1. The message may be an RRC message transmitted from UE100 to cell #1 (gNB200#1). The RRC message may be a UE Assistance Information message. The message may also be an MBS Interest Indication message. Alternatively, the message may be an NAS message transmitted from UE100 to CN20#1 (AMF300A) via cell #1 (gNB200#1). The NAS message may be a CONFIGURATION UPDATE COMPLETE message, a REGISTRATION REQUEST message, or a SERVICE REQUEST message.

[0075] A network device included in network 50#1, for example, gNB200#1 or CN20#1 (AMF300A), receives the message from UE 100 via cell #1. This enables the network device to communicate with UE 100, for example, perform data communication or paging transmission, so as to avoid the MBS reception timing when UE 100 receives an MBS from cell #2.

[0076] (1) First operation example In the first operation example, gNB200#1 receives a message (e.g., an RRC message) from UE100 and transmits an MBS gap setting to UE100 via cell #1, the MBS gap setting indicating the setting of an MBS gap for suspending communication with cell #1 in order to receive an MBS from cell #2. After transmitting the message, UE100 receives from cell #1 the MBS gap setting indicating the setting of an MBS gap for suspending communication with cell #1 in order to receive an MBS from cell #2.

[0077] UE 100, which is in the RRC connected state in cell #1, suspends data communication with cell #1 during the MBS gap based on the MBS gap setting from gNB 200 #1 and receives an MBS from cell #2. This allows UE 100 to receive an MBS from cell #2 while maintaining the RRC connected state with cell #1 (gNB 200 #1).

[0078] In a first operation example, UE100 generates requested gap information indicating the configuration of an MBS gap requested by UE100 based on the MCCH configuration of cell #2 and / or the MTCH configuration of cell #2. UE100 transmits a message including the requested gap information to cell #1 (gNB200#1). Cell #1 (gNB200#1) receives the message including the requested gap information and transmits an MBS gap configuration based on the requested gap information to UE100. This allows the MBS gap to be appropriately configured in UE100.

[0079] 11 is a diagram illustrating a first operation example. In the following description, cell #1 (gNB 200 #1) may be replaced with network 50 #1 (PLMN #1). Cell #2 (gNB 200 #2) may be replaced with network 50 #2 (PLMN #2).

[0080] In step S100, UE 100 is in an RRC connected state in cell #1.

[0081] In step S101, UE 100 is receiving or interested in receiving an MBS. Here, assume an example in which UE 100 is receiving or interested in receiving an MBS session (e.g., a broadcast session) provided by ROM / FTA. Here, "receiving an MBS" may mean a state in which UE 100 is receiving an MBS session provided by ROM / FTA from cell #2.

[0082] Note that UE 100 may have previously acquired higher layer information indicating a correspondence relationship between an MBS session (MBS session identifier) ​​provided by ROM / FTA and a frequency (frequency identifier). The higher layer information may further include information indicating a start time of the MBS session and / or information indicating an MBS service area in which the MBS session is provided. UE 100 may know a desired MBS frequency for providing the MBS session (desired MBS session) based on the higher layer information. Such higher layer information may be provided as a USD (User Service Description) or may be provided by a NAS message (for example, a REGISTRATION ACCEPT message, a CONFIGURATION UPDATE COMMAND message, or a PDU SESSION ESTABLISHMENT ACCEPT message).

[0083] In step S102, the UE 100 receives, from the cell #1 (gNB 200#1), MBS information indicating the correspondence between the MBS sessions and frequencies provided by the network 50#1 (PLMN#1) and / or the MBS sessions provided by the cell #1 in ROM / FTA. Such MBS information may be information broadcast in the SIB or MCCH of the cell #1.

[0084] For example, the MBS information indicating the correspondence between the MBS sessions and the frequencies provided by the network 50#1 may include multiple sets of MBS session identifiers and frequency identifiers. Based on such MBS information, the UE 100 can determine which MBS sessions are provided at which frequencies.

[0085] The MBS information indicating the MBS sessions provided by the cell #1 in the ROM / FTA may include an MBS session identifier list of the MBS sessions provided by the cell #1 in the ROM / FTA. Based on such MBS information, the UE 100 can determine which MBS sessions the cell #1 provides in the ROM / FTA.

[0086] In step S103, the UE 100 recognizes, based on the MBS information received in step S102, that the desired MBS session to which ROM / FTA is applied is not provided by the network 50#1 (PLMN#1).

[0087] For example, based on MBS information indicating the correspondence between MBS sessions and frequencies provided by network 50#1, UE 100 may recognize that the desired MBS session and / or the desired MBS frequency is not indicated in the MBS information, and that the desired MBS session is not provided from network 50#1 (PLMN#1). If the desired MBS frequency providing the desired MBS session to which ROM / FTA is applied is not indicated in the MBS information, UE 100 may recognize that the desired MBS session and / or the desired MBS frequency can be provided from another network, i.e., network 50#2 (PLMN#2).

[0088] Alternatively, based on MBS information indicating MBS sessions provided by cell #1 in ROM / FTA, UE 100 may recognize that if the desired MBS session is not indicated in the MBS information, the desired MBS session is not provided from network 50 #1 (PLMN #1), and the desired MBS session and / or the desired MBS frequency may be provided from another network, i.e., network 50 #1 (PLMN #1).

[0089] In step S104, the UE 100 may receive MBS information from the cell #2 (gNB 200 #2) indicating the correspondence between the MBS sessions and frequencies provided by the network 50 #2 (PLMN #2) and / or the MBS sessions provided by the cell #2 in ROM / FTA. Such MBS information may be information broadcast in the SIB or MCCH of the cell #2. The UE 100 may confirm that the desired MBS session and / or the desired MBS frequency is provided by the cell #2 based on the MBS information.

[0090] In step S104, UE 100 receives MBS reception configuration for cell #2 from cell #2. Such MBS reception configuration includes MCCH configuration information broadcast in a SIB (MBS SIB) of cell #2 and / or MTCH configuration information broadcast in an MCCH of cell #2. For example, UE 100 receives MCCH configuration information via an MBS SIB transmitted on a BCCH from cell #2, and then receives the MTCH configuration information by receiving an MCCH from gNB 200 based on the MCCH configuration information.

[0091] The MCCH configuration information includes scheduling information of the MCCH, i.e., information indicating the MCCH reception timing (MCCH reception opportunity). The MTCH configuration information includes scheduling information of the MTCH, i.e., information indicating the MTCH reception timing (MTCH reception opportunity). Such MCCH reception timing (MCCH reception opportunity) and / or MTCH reception timing (MTCH reception opportunity) corresponds to the MBS reception timing at which UE 100 receives an MBS from cell #2. Specifically, the MTCH reception timing constituting the MBS reception timing may be the MTCH reception timing associated with the desired MBS session, among the MTCH reception timings indicated for each MBS session by the MCCH.

[0092] In step S105, UE 100 determines a gap pattern setting for MBS gaps that interrupt data communication with cell #1 based on the MBS reception timing determined in step S104, and generates requested gap information indicating the determined gap pattern setting. A gap pattern refers to a periodically repeated pattern of MBS gaps. The requested gap information includes information indicating the start timing of the gap pattern (such as a system frame number and / or a subframe number) and information indicating the gap pattern, such as a bitmap for each subframe or a period (cycle length) of MBS gaps. The requested gap information may also include information indicating the duration of each MBS gap. Note that UE 100 determines the requested gap pattern in accordance with the timing of cell #1 (such as a system frame number). Here, when determining the requested gap pattern, UE 100 may add to the requested gap pattern a time (margin) required for changing the frequency of the receiver of UE 100 and / or a measurement time for establishing synchronization with cell #2.

[0093] In step S106, UE 100 transmits an RRC message including the request gap information generated in step S105 to cell #1 (gNB 200 #1). UE 100 may further include a desired MBS session identifier (e.g., TMGI) and / or a desired MBS frequency identifier associated with the request gap information in the RRC message.

[0094] In step S107, cell #1 (gNB200#1) generates an MBS gap configuration indicating the configuration of MBS gaps (gap pattern) based on the requested gap information in the RRC message received from UE 100 in step S106, and transmits the MBS gap configuration to UE 100. For example, cell #1 (gNB200#1) transmits an RRC Reconfiguration message including the MBS gap configuration to UE 100. The type of information included in the MBS gap configuration may be the same as the type of information included in the requested gap information. Cell #1 (gNB200#1) may further include a cell identifier and / or a cell group identifier associated with the MBS gap configuration in the RRC reconfiguration message. Cell #1 (gNB200#1) may include multiple sets of MBS gap configurations and cell identifiers and / or cell group identifiers in the RRC reconfiguration message.

[0095] In step S108, UE100 suspends data communication with cell #1 (gNB200#1) during the MBS gap indicated by the MBS gap setting received from cell #1 (gNB200#1) in step S107, and performs MBS reception for the desired MBS session from cell #2 (gNB200#2). Specifically, UE100 changes (tunes) the receiving frequency of the receiver from frequency #1 to frequency #2, and then performs MBS reception from cell #2 (gNB200#2), i.e., MTCH reception (and MCCH reception). Cell #1 (gNB200#1) does not allocate radio resources to UE100 during the set MBS reception gap.

[0096] Here, when the UE 100 uses a plurality of serving cells (or a plurality of cell groups) for communication with the network 50#1 (i.e., in the case of carrier aggregation or dual connectivity), the UE 100 may identify the serving cell (and / or cell group) to which the MBS gap setting is applied based on the cell identifier and / or cell group identifier in the RRC reconfiguration message, and may perform MBS reception from cell #2 (gNB200#2) using a receiver assigned to the identified serving cell (and / or cell group). Note that receivers assigned to serving cells (and / or cell groups) other than the identified serving cell (and / or cell group) may remain on the same frequency / serving cell and continue reception from the serving cell.

[0097] When UE100 is no longer interested in receiving MBS from cell #2 (gNB200#2) (step S109), it may notify cell #1 (gNB200#1) (step S110). UE100 may send the notification in an RRC message, for example, a UE Assistance Information message or an MBS Interest Indication message. The notification may be a gap release request. Alternatively, the notification may be an MBS reception gap request that does not include a requested gap pattern. Cell #1 (gNB200#1) may remove (release) the MBS reception gap setting from UE100 based on the notification (step S111).

[0098] (2) Second operation example In the above-described first operation example, an example in which UE100 determines a requested gap pattern has been described. However, UE100 may transmit to cell #1 (gNB200#1) an RRC message including configuration information indicating the configuration of an MCCH of cell #2 and / or the configuration of an MTCH of cell #2 without determining a requested gap pattern. That is, UE100 may forward the MBS reception configuration received from cell #2 to cell #1 (gNB200#1). Cell #1 (gNB200#1) receives the RRC message from UE100, determines a gap pattern based on the MBS reception configuration in the RRC message, and sets the gap pattern to UE100.

[0099] 12 is a diagram showing a second operation example, in which differences from the first operation example described above will be explained, and overlapping explanations will be omitted.

[0100] In step S151, UE100 transmits to cell #1 (gNB200#1) an RRC message including at least a portion of the MBS reception information received from cell #2 in step S104. For example, UE100 includes in the RRC message the MCCH configuration information and / or MTCH configuration information of cell #2. UE100 may include in the RRC message only the MTCH configuration information (MTCH scheduling information) associated with the desired MBS session, among the MTCH configuration information (MTCH scheduling information) for each MBS session. UE100 may further include in the RRC message information indicating the amount of the deviation (offset) when there is a deviation in the radio frame timing between cell #1 and cell #2. UE100 may further include in the RRC message a desired MBS session identifier (e.g., TMGI) and / or a desired MBS frequency identifier.

[0101] In step S152, cell #1 (gNB200#1) determines a gap pattern in the same manner as in step S105 described above, based on the MBS reception configuration in the RRC message received from UE 100 in step S106. Then, cell #1 (gNB200#1) transmits an MBS gap configuration indicating the MBS gap configuration (gap pattern) to UE 100. For example, cell #1 (gNB200#1) transmits an RRC Reconfiguration message including the MBS gap configuration to UE 100. Cell #1 (gNB200#1) may further include a cell identifier and / or a cell group identifier associated with the MBS gap configuration in the RRC Reconfiguration message, similar to the first operation example described above.

[0102] (3) Third operation example In the above-described first and second operation examples, an example has been described in which the MBS gap used by UE100 in the RRC connected state is set to UE100 from cell #1 (gNB200#1).

[0103] When the UE 100 is in the RRC idle state, the UE 100 needs to monitor paging transmitted from the network 50#1, specifically, the AMF 300A#1 included in the CN 20#1, via the cell #1 (gNB 200#1). If the timing of such paging reception (paging reception opportunity) and the timing of MBS reception (MBS reception opportunity) from the cell #2 at least partially overlap, the UE 100 has difficulty in properly receiving the MBS from the cell #2.

[0104] In the third operation example, UE100 transmits a NAS message regarding the MBS reception timing at which UE100 receives an MBS from cell #2 to AMF300A#1 via cell #1 (gNB200#1). Here, UE100 may transmit a NAS message including request information requesting a change in paging reception timing to AMF300A#1. The request information may include request gap information as in the first operation example described above. Furthermore, the request information may include an MBS reception setting as in the second operation example described above.

[0105] Based on the received request information, AMF300A#1 transmits a paging reception setting to UE100 via cell #1 (gNB200#1), the paging reception setting setting setting the paging reception timing to avoid the MBS reception timing in cell #2. That is, AMF300A#1 adjusts the paging reception timing of UE100 to avoid the MBS reception timing in cell #2. In this operation example, AMF300A#1 corresponds to a paging management device.

[0106] UE 100 in the RRC idle state monitors paging from cell #1 at the adjusted paging reception timing based on the paging reception setting from AMF 300A #1, and receives an MBS from cell #2 at a timing different from the paging reception timing. This allows UE 100 to receive an MBS from cell #2 while maintaining the RRC idle state in cell #1.

[0107] 13 is a diagram showing a third operation example, in which differences from the first and second operation examples described above will be mainly explained, and overlapping explanations will be omitted.

[0108] In step S200, UE 100 is in an RRC idle state in cell #1. UE 100 in the RRC idle state in cell #1 monitors paging from cell #1 (gNB 200 #1). Specifically, UE 100 monitors paging transmitted from cell #1 (gNB 200 #1) at paging reception timing (paging occasion) determined according to parameters such as its own UE identifier.

[0109] In step S201, the UE 100 is receiving or is interested in receiving an MBS. Here, an example is assumed in which the UE 100 is receiving or is interested in receiving an MBS session (e.g., a broadcast session) provided in ROM / FTA.

[0110] In step S202, the UE 100 receives, from the cell #1 (gNB 200#1), MBS information indicating a correspondence between MBS sessions and frequencies provided by the network 50#1 (PLMN#1) and / or MBS sessions provided by the cell #1 in ROM / FTA. Such MBS information may be information broadcast in the SIB or MCCH of the cell #1.

[0111] In step S203, the UE 100 recognizes, based on the MBS information received in step S202, that the desired MBS session to which ROM / FTA is applied is not provided by the network 50#1 (PLMN#1).

[0112] In step S204, the UE 100 may receive, from the cell #2 (gNB200#2), MBS information indicating the correspondence between the MBS session and the frequency provided by the network 50#2 (PLMN#2) and / or the MBS session provided by the cell #2 in ROM / FTA. Based on the MBS information, the UE 100 may confirm that the desired MBS session and / or the desired MBS frequency is provided by the cell #2.

[0113] In step S204, the UE 100 receives the MBS reception setting in the cell #2 from the cell #2, and ascertains the MBS reception timing in the cell #2.

[0114] In step S205, the UE 100 recognizes that the MBS reception timing in the cell #2 overlaps (collides with) the paging reception timing in the cell #1.

[0115] In step S206, the UE 100 transmits a NAS message including request information requesting a change in the paging reception timing to the AMF 300A #1 via the cell #1 (gNB 200 #1). Such request information may be information requesting a change in the UE identifier (e.g., 5G-S-TMSI), or may include an alternative UE identifier (i.e., a desired UE identifier) ​​or an offset value of the UE identifier (i.e., an offset value to be added to the UE identifier when calculating the paging reception timing, which may be a desired offset value). Alternatively, the request information may be information indicating a desired paging reception timing (PO: paging occasion). Here, the UE 100 may transmit the NAS message after transitioning from the RRC idle state to the RRC connected state.

[0116] In step S207, AMF300A#1 transmits, to UE100 via cell #1 (gNB200#1), a paging reception configuration that sets the paging reception timing so as to avoid the MBS reception timing in cell #2 based on the received request information. Such paging reception configuration may include a parameter that determines the adjusted paging reception timing, for example, a UE identifier (5G-S-TMSI). Furthermore, such paging reception configuration may include an offset value to be added to the 5G-S-TMSI. Upon receiving the paging reception configuration, UE100 may transition to an RRC idle state.

[0117] UE 100 in the RRC idle state monitors paging from cell #1 at the adjusted paging reception timing based on the paging reception setting from AMF 300A #1 (step S208), and receives an MBS from cell #2 at a timing different from the paging reception timing (step S209). Note that the order of steps S208 and S209 may be reversed.

[0118] When UE 100 is no longer interested in receiving MBS from cell #2 (gNB 200 #2) (step S210), UE 100 may notify AMF 300A #1 (step S211). Here, UE 100 may make the notification after transitioning from RRC idle state to RRC connected state. The notification may be a request to cancel adjustment of paging occasions. Alternatively, the notification may be an adjustment request that does not include a requested gap pattern. Based on the notification, AMF 300A #1 may restore the paging reception setting in UE 100 (step S212).

[0119] In this operation example, an example has been described in which a NAS message is transmitted from UE 100 to AMF 300A #1 in step S206. However, an RRC message including request information may be transmitted from UE 100 to cell #1 (gNB 200 #1) in step S206. Cell #1 (gNB 200 #1) may forward the received request information to AMF 300A #1 over the NG interface.

[0120] (4) Fourth operation example In the above-described third operation example, an example in which AMF300A#1 adjusts the paging reception timing of UE100 in the RRC idle state has been described. In the fourth operation example, an example in which gNB200#1 adjusts the paging reception timing of UE100 in the RRC inactive state will be described. For UE100 in the RRC inactive state, paging is managed by gNB200#1, not AMF300A#1. Such paging is sometimes called RAN paging. In this operation example, gNB200#1 corresponds to a paging management device.

[0121] 14 is a diagram showing a fourth operation example, in which differences from the above-described third operation example will be explained, and overlapping explanations will be omitted.

[0122] In step S250, UE 100 is in an RRC inactive state in cell #1. UE 100 in the RRC inactive state in cell #1 monitors paging from cell #1 (gNB 200 #1). Specifically, UE 100 monitors paging transmitted from cell #1 (gNB 200 #1) at paging reception timing (paging occasion) determined according to parameters such as its own UE identifier.

[0123] In step S251, the UE 100 transmits an RRC message including request information requesting a change in paging reception timing to the cell #1 (gNB 200 #1). Here, the UE 100 may transmit the RRC message after transitioning from the RRC inactive state to the RRC connected state.

[0124] In step S252, based on the received request information, cell #1 (gNB200#1) transmits to UE100 a paging reception configuration that sets the paging reception timing to avoid the MBS reception timing in cell #2. Such paging reception configuration may include a parameter that determines the adjusted paging reception timing, for example, a UE identifier (5G-S-TMSI). Furthermore, such paging reception configuration may include an offset value to be added to the 5G-S-TMSI. Upon receiving the paging reception configuration, UE100 may transition to an RRC inactive state. Note that steps S251 and S252 may be performed between AMF300A#1 and UE100, similar to steps S206 and S207 of the third operation example. In this case, AMF300A#1 or UE100 may notify gNB200#1 of the parameter that determines the adjusted paging reception timing using an NG-AP message or an RRC message.

[0125] UE 100 in the RRC inactive state monitors paging from cell #1 at the adjusted paging reception timing based on the paging reception setting from cell #1 (gNB 200 #1) (step S253), and receives an MBS from cell #2 at a timing different from the paging reception timing (step S254). Note that the order of steps S253 and S254 may be reversed.

[0126] When UE100 is no longer interested in receiving MBS from cell #2 (gNB200#2) (step S255), it may notify cell #1 (gNB200#1) (step S256). Here, UE100 may make the notification after transitioning from the RRC inactive state to the RRC connected state. The notification may be a request to cancel adjustment of paging occasions. Alternatively, the notification may be an adjustment request that does not include a requested gap pattern. Cell #1 (gNB200#1) may restore the paging reception setting in UE100 based on the notification (step S257).

[0127] (Other embodiments) In the above embodiment, an example has been described in which UE 100 receives broadcast information (MBS information) indicating an MBS session being provided by a cell in ROM / FTA from the cell via an SIB or an MCCH. That is, the cell (gNB 200) broadcasts MBS information indicating an MBS session being provided by the cell in ROM / FTA. UE 100 identifies the MBS session being provided by the cell in ROM / FTA based on the broadcast information (MBS information).

[0128] Such an operation may be used in a cell reselection procedure performed by UE 100 in an RRC idle state or an RRC inactive state. For example, when UE 100 in an RRC idle state or an RRC inactive state is receiving or interested in receiving a desired MBS session to which ROM / FTA is applied, UE 100 preferentially reselects a cell that provides the desired MBS session and camps on the cell. Here, UE 100 may receive MBS information broadcast from the cell and determine whether the cell provides the desired MBS session. If UE 100 determines that the cell provides the desired MBS session, UE 100 may determine the frequency to which the cell belongs as the highest priority for cell reselection.

[0129] In the above-described embodiment, an example has been described in which cell #1 is a cell belonging to PLMN #1 and cell #2 is a cell belonging to PLMN #2. However, the present invention is not limited to such an inter-PLMN scenario, and cell #1 and cell #2 may belong to the same PLMN. Furthermore, although an inter-frequency scenario has been assumed, an intra-frequency scenario, i.e., a scenario in which cell #1 and cell #2 operate on the same frequency, may also be used. Furthermore, in the above-described embodiment, an example has been described in which MBS reception from cell #2 (gNB200#2) is reception of an MBS session provided by ROM / FTA. However, the MBS session provided by cell #2 (gNB200#2) does not necessarily have to be ROM / FTA. The MBS session provided by cell #2 (gNB200#2) may be a broadcast session or a multicast session.

[0130] The above-mentioned operational flows are not limited to being implemented independently, but can also 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.

[0131] In the above-described 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 also be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may also be a DU of the IAB node. The user equipment may also be an MT (Mobile Termination) of the IAB node.

[0132] A program may be provided that causes a computer to execute each process performed by UE100 or gNB200. The program may be recorded on a computer-readable medium. The computer-readable medium can be used to install the program on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. Furthermore, circuits that execute 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).

[0133] 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 can be made within the scope that does not deviate from the gist of the invention.

[0134] As used in this disclosure, the terms "based on" and "depending on" do not mean "based only on" or "depending only on," unless expressly stated otherwise. 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 "at least in part on." Furthermore, "obtain" may mean obtaining information from stored information, obtaining information from information received from another node, or obtaining information by generating the information. The terms "include," "comprise," and variations thereof do not mean including only the listed items, but may also mean including only the listed items or including additional items in addition to the listed items. Furthermore, as used in this disclosure, the term "or" is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not 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 first and second elements 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 shall include the plural unless the context clearly indicates otherwise.

[0135] This application claims priority to Japanese Patent Application No. 2021-174776 (filed October 26, 2021), the entire contents of which are incorporated herein by reference. [Explanation of symbols]

[0136] 1: Mobile communication system 10:RAN 20 :CN 100:UE 110: Receiving unit 120: Transmitter 130: Control unit 200 :gNB 210: Transmission unit 220: Receiving unit 230: Control unit 240: Backhaul communication unit

Claims

1. A user equipment communicating with a first network in a mobile communication system, comprising: a receiving unit that receives, from the first network, a gap setting that sets a gap pattern for interrupting communication with the first network so that the user device can receive from a second network that belongs to a SIM different from a SIM that the first network corresponds to; a transmitting unit that transmits information requesting cancellation of the gap setting to the first network. User equipment.

2. 1. A processor for controlling a user equipment communicating with a first network in a mobile communication system, comprising: receiving a gap setting from the first network, the gap setting setting being a gap pattern for interrupting communication with the first network, in order for the user device to receive from a second network belonging to a SIM different from a SIM corresponding to the first network; and transmitting information to the first network requesting cancellation of the gap setting. Processor.

3. A user equipment communicating with a first network in a mobile communication system, receiving a gap setting from the first network, the gap setting setting being a gap pattern for interrupting communication with the first network, in order for the user device to receive from a second network belonging to a SIM different from a SIM corresponding to the first network; and transmitting information to the first network requesting cancellation of the gap setting. program.

4. A network node in a first network communicating with a user equipment in a mobile communication system, comprising: a transmitter configured to transmit to the user device a gap setting, the gap setting setting setting a gap pattern for interrupting communication with the first network, so that the user device can receive from a second network that belongs to a SIM different from a SIM corresponding to the first network; a receiving unit that receives information requesting cancellation of the gap setting from the user device. Network node.

5. 1. A mobile communication system comprising a first network and a user device communicating with the first network, the user device receives, from the first network, a gap setting that sets a gap pattern for interrupting communication with the first network in order for the user device to receive from a second network that belongs to a SIM different from a SIM that the first network corresponds to; The user equipment transmits information to the first network requesting cancellation of the gap setting. Mobile communication system.

Images