Communication method and user equipment

By generating and sending multicast broadcast service interest indications that contain upper-level information determined in user equipment, the problem of insufficient frequency information correspondence in 5G/NR multicast and broadcast services is solved, and service continuity and efficiency are improved.

CN119014012APending Publication Date: 2024-11-22KYOCERA CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033292.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-02-10
Filing Date
2023-02-08
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing 5G/NR multicast and broadcast services have defects in the frequency information correspondence relationship, which makes it difficult for user equipment to accurately identify the frequency of interest, affecting service continuity and efficiency.

Method used

By receiving the frequency information in the predetermined system information block (SIB), the user equipment generates and sends a multicast broadcast service (MBS) interest indication. Even if the frequency information of interest is not provided in the SIB, it uses the upper layer information to determine and include the sense of inclusion. Frequency of interest ensures the integrity of the frequency list.

Benefits of technology

It improves the frequency identification accuracy and service continuity of user equipment in multicast broadcast services, and enhances the support capabilities of 5G/NR multicast and broadcast services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014012A_ABST
    Figure CN119014012A_ABST
Patent Text Reader

Abstract

There is provided a communication method performed by a user equipment in a mobile communication system providing a multicast broadcast service (MBS), the communication method including receiving a predetermined system information block (SIB) from a serving cell, the predetermined system information block (SIB) may include frequency information, the frequency information indicates a corresponding relationship between the identifier of the MBS and the frequency on which the MBS is provided; generating an MBS interest notification, the MBS interest notification comprising a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user device is receiving or is interested in receiving; and transmitting an MBS interest notification to the serving cell, in which the user equipment includes the frequency of interest in the list if the frequency of interest is indicated by the higher layer information even if the frequency of interest is not included in the predetermined SIB.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a communication method and user equipment used in a mobile communication system. Background Art

[0002] In the 3rd Generation Partnership Project (3GPP) standard, technical specifications for New Radio (NR) as a fifth generation (5G) radio access technology have been defined. Compared with Long Term Evolution (LTE) as a fourth generation (4G) radio access technology, NR has features such as high speed, large capacity, high reliability, and low latency. In 3GPP, the establishment of technical specifications for a multicast broadcast service (MBS) for 5G / NR has been discussed (for example, see Non-Patent Document 1).

[0003] Reference List

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP Contribution: RP-201038, "WID revision: NR Multicast and Broadcast Services" Summary of the invention

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

[0007] In view of this, the present disclosure provides a communication method and user equipment capable of implementing enhanced multicast broadcast services.

[0008] In a first aspect, a communication method is performed by a user equipment in a mobile communication system for providing a multicast broadcast service (MBS). The communication method includes: receiving a predetermined system information block (SIB) from a serving cell, the predetermined system information block including frequency information indicating a correspondence between an identifier of an MBS service and a frequency for providing the MBS service; generating an MBS interest indication, the MBS interest indication including a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user equipment is receiving or interested in receiving; and sending the MBS interest indication to the serving cell. Even when the predetermined SIB does not include the frequency of interest, the user equipment includes the frequency of interest in the list when the frequency of interest is indicated in the upper layer information.

[0009] In a second aspect, a user equipment is used in a mobile communication system for providing a multicast broadcast service (MBS). The user equipment includes: a receiver configured to receive a predetermined system information block (SIB) from a serving cell, the predetermined system information block including frequency information indicating a correspondence between an identifier of an MBS service and a frequency for providing the MBS service; a controller configured to generate an MBS interest indication, the MBS interest indication including a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user equipment is receiving or interested in receiving; and a transmitter configured to send the MBS interest indication to the serving cell. The controller is configured to include the frequency of interest in the list when the frequency of interest is indicated in upper layer information, even when the predetermined SIB does not include the frequency of interest. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram showing a configuration of a mobile communication system according to an embodiment.

[0011] Figure 2 is a diagram showing a configuration of a user equipment (UE) according to an embodiment.

[0012] Figure 3 is a diagram showing the configuration of a gNB (base station) according to an embodiment.

[0013] Figure 4 is a diagram showing a configuration of a protocol stack of a radio interface of a user plane processing data.

[0014] Figure 5 : is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that processes signaling (control signals).

[0015] Figure 6 is a diagram showing an overview of MBS service delivery according to an embodiment.

[0016] Figure 7 is a diagram showing a transmission mode according to an embodiment.

[0017] Figure 8 is a diagram showing an example of internal processing related to MBS reception of a UE according to an embodiment.

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

[0019] Fig.10 is a diagram showing an overview of MII according to an embodiment.

[0020] Fig.11is a diagram showing a configuration example of SIBx1 according to the embodiment.

[0021] Fig.12 is a diagram illustrating the operation of Option 1 according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0022] Fig.13 is a diagram illustrating the operation of Option 2 according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0023] Fig.14 is a diagram illustrating the operation of Option 3 according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0024] Fig.15 is a diagram illustrating the operation of Option A according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0025] Fig.16 is a diagram showing an operation example 1 of option B according to the embodiment, which is specifically a specification change in 3GPP technical specification TS38.331.

[0026] Fig.17 is a diagram showing operation example 2 of option B according to the embodiment, which is specifically a specification change in 3GPP technical specification TS38.331.

[0027] Fig.18 is a diagram showing an operation example 1 of Option C according to the embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0028] Fig.19 is a diagram showing an operation example 2 of option C according to the embodiment, which is specifically a specification change in 3GPP technical specification TS38.331.

[0029] Fig. 20 is a diagram showing a configuration example 1 of the MII according to the embodiment, which is specifically a specification change in the 3GPP technical specification TS38.331.

[0030] Fig.21 is a diagram showing a modification of configuration example 1 of the MII according to the embodiment, which is specifically a specification change in 3GPP technical specification TS 38.331. DETAILED DESCRIPTION

[0031] The mobile communication system according to the embodiment is described with reference to the accompanying drawings. In the description of the drawings, the same or similar reference numerals represent the same or similar parts.

[0032] (1) Configuration of mobile communication system

[0033] Figure 1 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. The mobile communication system 1 complies with the fifth generation system (5GS) of the 3GPP standard. The following description takes 5GS as an example, but the long term evolution (LTE) system may be at least partially applied to the mobile communication system. The sixth generation (6G) system may be at least partially applied to the mobile communication system.

[0034] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (next generation 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.

[0035] UE 100 is a mobile wireless communication device. UE 100 may be any device as long as UE 100 is used by a user. Examples of UE 100 include a mobile phone terminal (including a smart phone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided on a sensor, a vehicle or a device provided on a vehicle (vehicle UE), or a flying object and a device provided on the flying object (air UE).

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

[0037] Note that the gNB can be connected to the Evolved Packet Core (EPC) corresponding to the core network of LTE. The LTE base station can also be connected to the 5GC. The LTE base station and the gNB can be connected via an inter-base station interface.

[0038] 5GC 20 includes an access and mobility management function (AMF) and a user plane function (UPF) 300. AMF performs various types of mobility control, etc. for UE 100. AMF manages the mobility of UE 100 by communicating with UE 100 using non-access stratum (NAS) signaling. UPF controls data transmission. AMF and UPF are connected to gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0039] Figure 2 1 is a diagram showing a configuration of a UE 100 (User Equipment) according to an embodiment. The UE 100 includes a receiver 110, a transmitter 120, and a controller 130. The receiver 110 and the transmitter 120 constitute a wireless communicator that performs wireless communication with the gNB 200.

[0040] The receiver 110 performs various types of reception under the control of the controller 130. The receiver 110 includes an antenna and a receiving device. The receiving device converts a radio signal received through the antenna into a baseband signal (received signal) and outputs the obtained signal to the controller 130.

[0041] The transmitter 120 performs various types of transmission under the control of the controller 130. The transmitter 120 includes an antenna and a transmission device. The transmission device converts a baseband signal (transmission signal) output by the controller 130 into a radio signal and transmits the resulting signal through the antenna.

[0042] The controller 130 performs various types of control and processing in the UE 100. Such processing includes processing of various layers to be described later. The controller 130 includes at least one processor and at least one memory. The memory stores programs to be executed by the processor and information to be used for processing by the processor. The processor may include a baseband processor and a central processing unit (CPU). The baseband processor performs modulation and demodulation, encoding and decoding of baseband signals, etc. The CPU executes the program stored in the memory, thereby performing various types of processing.

[0043] Figure 3 2 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 communicator 240. The transmitter 210 and the receiver 220 constitute a wireless communicator that performs wireless communication with the UE 100. The backhaul communicator 240 constitutes a network communicator that performs communication with the CN 20.

[0044] The transmitter 210 performs various types of transmission under the control of the controller 230. The transmitter 210 includes an antenna and a transmission device. The transmission device converts a baseband signal (transmission signal) output by the controller 130 into a radio signal and transmits the resulting signal through the antenna.

[0045] The receiver 220 performs various types of reception under the control of the controller 230. The receiver 220 includes an antenna and a receiving device. The receiving device converts a radio signal received through the antenna into a baseband signal (received signal) and outputs the obtained signal to the controller 130.

[0046] The controller 230 performs various types of control and processing in the gNB 200. Such processing includes processing of various layers to be described later. The controller 230 includes at least one processor and at least one memory. The memory stores programs to be executed by the processor and information to be used for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation and demodulation, encoding and decoding of baseband signals, etc. The CPU executes the program stored in the memory, thereby performing various types of processing.

[0047] The backhaul communicator 240 is connected to the neighboring base station via the Xn interface which is an interface between base stations. The backhaul communicator 240 is connected to the AMF / UPF 300 via the NG interface between the base station and the core network. Note that the gNB 200 may include a central unit (CU) and a distributed unit (DU) (ie, the functions are divided), and the two units may be connected via the F1 interface which is a fronthaul interface.

[0048] Figure 4 is a diagram showing a configuration of a protocol stack of a radio interface of a user plane processing data.

[0049] The radio interface protocol of the user plane 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.

[0050] The PHY layer performs encoding and decoding, modulation and demodulation, antenna mapping and demapping, and resource mapping and demapping. Data and control information are transmitted between the PHY layer of UE 100 and the PHY layer of gNB 200 via a physical channel. Note that the PHY layer of UE 100 receives downlink control information (DCI) transmitted from gNB 200 through a physical downlink control channel (PDCCH). Specifically, UE 100 blindly decodes PDCCH using a radio network temporary identifier (RNTI) and obtains the successfully decoded DCI as DCI addressed to UE 100. The DCI transmitted from gNB 200 is attached with CRC parity bits scrambled by RNTI.

[0051] The MAC layer performs priority control of data, retransmission processing by hybrid ARQ (HARQ: Hybrid Automatic Repeat Request), a random access procedure, etc. Data and control information are transmitted between the MAC layer of UE 100 and the MAC layer of gNB 200 via a transport channel. The MAC layer of gNB 200 includes a scheduler. The scheduler determines the transport format (transport block size, modulation and coding scheme (MCS)) in uplink and downlink and the resource blocks to be allocated to UE 100.

[0052] The RLC layer transmits data to the RLC layer of 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.

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

[0054] The SDAP layer performs mapping between IP flows (as a unit of QoS (Quality of Service) control performed by the core network) and radio bearers (as a unit of QoS control performed by the access stratum (AS)). Note that when the RAN is connected to the EPC, SDAP does not need to be provided.

[0055] Figure 5 : is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that processes signaling (control signals).

[0056] The protocol stack of the radio interface of the control plane includes the Radio Resource Control (RRC) layer and the Non-Access Stratum (NAS) layer instead of Figure 4 The SDAP layer shown in .

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

[0058] The NAS layer 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 includes an application layer in addition to the protocol of the radio interface. A layer lower than the NAS layer is called an AS layer.

[0059] (2) Overview of MBS

[0060] An overview of MBS according to an embodiment will be described below. MBS is a service in which the NG-RAN 10 can provide broadcast or multicast, i.e., point-to-multipoint (PTM) data transmission to the UE 100. It is assumed that use cases (service types) of MBS include public safety communications, mission-critical communications, vehicle-to-everything (V2X) communications, IPv4 or IPv6 multicast delivery, Internet Protocol Television (IPTV), group communications, and software delivery.

[0061] The broadcast service provides services to each UE 100 within a specific service area for applications that do not require highly reliable QoS. An MBS session for the broadcast service is called a broadcast session.

[0062] The multicast service does not provide services to each UE 100, but provides services to a group of UEs 100 that join the multicast service (multicast session). An MBS session for a multicast service is called a multicast session. A multicast service can provide the same content to the group of UEs 100 in a method with higher radio efficiency than a broadcast service.

[0063] Figure 6 is a diagram showing an overview of MBS service delivery according to an embodiment.

[0064] MBS services (MBS data) are transmitted from a single data source (application service provider) to multiple UEs. 5G CN (5GC) 20, which is a 5G core network, receives MBS data from the application service provider and performs replication of the MBS data to transmit the replication product.

[0065] From the perspective of 5GC 20, two multicast delivery methods are possible: 5GC shared MBS service delivery, and 5GC individual MBS service delivery.

[0066] In the 5GC individual MBS service delivery method, the 5GC 20 receives a single copy of an MBS data packet and transmits respective copies of these MBS data packets to each UE 100 via the PDU session of each UE 100. Therefore, one PDU session of each UE 100 needs to be associated with the multicast session.

[0067] In the 5GC shared MBS service delivery method, the 5GC 20 receives a single copy of an MBS data packet and transmits the single copy of the MBS data packet to a RAN node (i.e., gNB 200). The gNB 200 receives the MBS data packet via an MBS tunnel connection and transmits the MBS data packet to one or more UEs 100.

[0068] From the perspective of RAN (5G RAN) 10, for radio transmission of MBS data in the 5GC shared MBS service transmission method, two transmission methods are possible: point-to-point (PTP) transmission method, and point-to-multipoint (PTM) transmission method. PTP means unicast, and PTM means multicast and broadcast.

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

[0070] The PTP and PTM transmission methods are mainly related to the user plane. The mode for controlling MBS data transmission includes two transmission modes: a first transmission mode and a second transmission mode.

[0071] Figure 7 is a diagram showing a transmission mode according to an embodiment.

[0072] The first transmission mode (transmission mode 1 (DM1)) is a transmission mode that can be used by the UE 100 in the RRC connected state, and is a transmission mode for high QoS requirements. The first transmission mode is used for a multicast session among MBS sessions. Note that the first transmission mode can be used for a broadcast session. The first transmission mode can be available to the UE 100 in the RRC idle state or the RRC inactive state.

[0073] MBS reception configuration in the first transmission mode is performed through UE-specific signaling. For example, MBS reception configuration in the first transmission mode is performed through an RRC reconfiguration message (or an RRC release message), which is an RRC message unicast from gNB200 to UE 100.

[0074] The MBS reception configuration includes MBS service channel configuration information (hereinafter referred to as "MTCH configuration information") regarding the configuration of an MBS service channel for transmitting MBS data. The MTCH configuration information includes MBS session information related to an MBS session (including the MBS session identifier described below) and scheduling information of an MBS service channel corresponding to the MBS session. The scheduling information of the MBS service channel may include a discontinuous reception (DRX) configuration of the MBS service channel. The discontinuous reception configuration may include at least one parameter of: a timer value (on duration timer) for defining an on period (on duration: receiving period), a timer value (inactive timer) for extending the on period, a scheduling interval or a DRX cycle (scheduling period, DRX cycle), an offset value (starting offset, DRX cycle offset) for the starting subframe of the scheduling period or the DRX cycle, a starting delay time slot value (time slot offset) of the on period timer, a timer value (retransmission timer) for defining the maximum time before retransmission, and a timer value (HARQ RTT timer) for defining the minimum interval before DL assignment of HARQ retransmission.

[0075] Note that the MBS traffic channel is a kind 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 kind of transport channel.

[0076] The second transmission mode (transmission mode 2 (DM2)) is a transmission 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 transmission mode for low QoS requirements. The second transmission mode is used for a broadcast session among MBS sessions. However, the second transmission mode can also be applied to a multicast session.

[0077] MBS reception configuration in the second transmission mode is performed by broadcast signaling. For example, MBS reception configuration in the second transmission mode is performed using a logical channel (e.g., a broadcast control channel (BCCH) and / or a multicast control channel (MCCH)) sent from gNB200 to UE 100 by broadcast. For example, UE 100 may receive BCCH and MCCH using a dedicated RNTI predefined in the technical specification. The RNTI for BCCH reception may be an SI-RNTI, and the RNTI for MCCH reception may be an MCCH-RNTI.

[0078] In the second transmission mode, UE 100 can receive MBS data in the following three processes. First, on BCCH, UE 100 receives MCCH configuration information about SIB (MBS-SIB) sent from gNB 200. Second, UE 100 receives MCCH from gNB 200 based on MCCH configuration information. On MCCH, MTCH configuration information is sent. Third, UE 100 receives MTCH (MBS data) based on MTCH configuration information. Hereinafter, MTCH configuration information and / or MCCH configuration information may be referred to as MBS reception configuration.

[0079] In the first transmission mode and the second transmission mode, the UE 100 may receive the MTCH using a group RNTI (G-RNTI) assigned from 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).

[0080] The network can provide different MBS services for different MBS sessions. The MBS session is identified by at least one item selected from the group consisting of a temporary mobile group identity (TMGI), a source-specific IP multicast address (which includes a source unicast IP address such as an application function and an application server and an IP multicast address indicating a destination address), a session identifier, and a G-RNTI. At least one item selected from the group consisting of a TMGI, a source-specific IP multicast address, and a session identifier is referred to as an MBS session identifier. The TMGI, the source-specific IP multicast address, the session identifier, and the G-RNTI are collectively referred to as MBS session information.

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

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

[0083] The MRB and corresponding logical channel (e.g., MTCH) of the UE 100 are configured from the gNB 200 through RRC signaling. The MRB configuration process can be separated from the data radio bearer (DRB) configuration process. In the RRC signaling, one MRB can be configured with "PTM only", "PTP only", or "both PTM and PTP". The type of MRB can be changed through RRC signaling.

[0084] Figure 8 An example is shown 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 configured with a PTP-only MRB, MRB#2 is configured with a PTM-only MRB, and MRB#3 is configured with a PTM-only MRB. Note that the DTCH is scheduled using the cell RNTI (C-RNTI). The MTCH is scheduled using the G-RNTI.

[0085] The PHY layer of the UE 100 processes user data (received data) received on the PDSCH, which is one of the physical channels, and routes the processed user 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 routes 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.

[0086] Fig. 9 An example is shown in which DTCH and MTCH are associated with an MRB associated with a multicast session. Specifically, an MRB is split into two branches, one branch is associated with DTCH, and the other branch is associated with MTCH. The two branches are merged at the PDCP layer (PDCP entity). That is, the MRB is an MRB configured with both PTM and PTP. Such an MRB may be referred to as a split MRB.

[0087] (3) Overview of MBS Interest Indications

[0088] An overview of MBS Interest Indication (MII) according to an embodiment will be described. Fig.10 is a diagram for showing an overview of MII according to an embodiment.

[0089] In the RRC connected state (step S1), the UE 100 is receiving or is interested in receiving an MBS session (step S2).

[0090] In step S3, UE 100 receives a SIB (hereinafter referred to as "SIBx1") for service continuity of MBS from gNB 200 (serving cell). SIBx1 is a SIB indicating the correspondence (mapping) between MBS service and frequency. A configuration example of SIBx1 will be described later. Note that SIBx1 is a SIB different from the above-mentioned MBS SIB. UE 100 may receive SIBx1 from gNB 200 before step S1 or before step S2.

[0091] UE 100 may send an MBS interest indication (MII) to a serving cell that provides SIBx1 (i.e., a serving cell that has a function for service continuity for MBS). In other words, UE 100 sends MII to the serving cell only when the serving cell provides SIBx1. MII is an RRC message and is a message used by UE 100 to inform the network that UE 100 is receiving or is interested in receiving MBS broadcast services via a broadcast MRB. Based on MII, the network (gNB 200) may control MBS service delivery and switch UE 100 to an appropriate cell.

[0092] In step S4, an MII transmission trigger (trigger event) occurs in the UE 100. Examples of types of MII transmission triggers (trigger events) include: when connection establishment has succeeded, when entering into or exiting from a broadcast service area, when an MBS broadcast session starts or stops, when interest in an MBS changes, when the priority between MBS broadcast reception and unicast reception changes, and when a cell changes to a cell (primary cell) that broadcasts an SIB for service continuity of an MBS.

[0093] In step S5, the UE 100 generates the MII. The MII includes at least one item selected from the group consisting of: a frequency list (MBS frequency list), which is a list of MBS frequencies that the UE 100 is receiving or is interested in receiving; priority information indicating the priority of which one is given priority between receiving all listed MBS frequencies and receiving unicast bearers; and a TMGI list, which is a list of MBS sessions that the UE 100 is receiving or is interested in receiving. The frequency list in the MII will be mainly described below.

[0094] Step S5 includes: step S51 for identifying the MBS frequency that UE 100 is receiving or interested in receiving (hereinafter referred to as "frequency of interest"); and step S52 for setting the frequency list to include the identified frequency of interest. The details of step S51 and step S52 will be described later.

[0095] In step S6, UE 100 sends MII to gNB 200 (serving cell).

[0096] Fig.11 is a diagram showing a configuration example of SIBx1 according to an embodiment. SIBx1 is used by UE 100 to derive a frequency (MBS frequency of interest) providing a desired MBS service (desired MBS session) that UE 100 is receiving or interested in receiving.

[0097] The term "MBS service" is used hereinafter as a term including the concept of "MBS session". The identifier of the MBS service is referred to as an "MBS service identifier". The MBS service identifier may be the above-mentioned MBS session identifier (e.g., TMGI). The MBS service identifier may be an MBS service area identifier (MBS SAI). The MBS service identifier may be denoted as MBS SAI.

[0098] like Fig.11 As shown, SIBx1 may include mbs-SAI-IntraFreq-r17 and / or mbs-SAI-InterFreqList-r17. mbs-SAI-IntraFreq-r17 includes MBS-SAI-List-r17, which is a list of MBS service identifiers of MBS services provided in the same frequency (i.e., the same frequency as the frequency of the serving cell). mbs-SAI-InterFreqList-r17 includes MBS-SAI-InterFreq-r17, which indicates, for each frequency regarding the inter-frequency (i.e., a frequency different from the frequency of the serving cell), the correspondence (mapping) between the frequency and the MBS service provided in the frequency. MBS-SAI-InterFreq-r17 includes a frequency identifier (ARFCN-ValueNR) indicating a downlink carrier frequency (dl-CarrierFreq-r17), and includes a list of MBS service identifiers (mbs-SAI-List-r17).

[0099] (4) Operation according to the embodiment

[0100] The operation according to the embodiment will be described.

[0101] In the frequency priority sorting at the time of cell reselection, the UE 100 in the RRC idle state or the RRC inactive state identifies the frequency providing the desired MBS service based on SIBx1, and sets the identified frequency to the highest priority. Note that when the frequency information (mbs-SAI-IntraFreq-r17 and mbs-SAI-InterFreqList-r17) is not provided in SIBx1, it is assumed that the frequency of interest providing the desired MBS service is identified based on the user service description (USD) as the upper layer information, and the identified frequency of interest is set to the highest priority.

[0102] Here, for example, the USD is provided to the UE 100 from an application function (AF) / multicast broadcast service function (MBSF) in the network. Such USD is an example of upper layer information provided from the network in an upper layer (specifically, an application layer) of the RRC layer. The USD may be referred to as service announcement information. The USD includes information indicating a correspondence between an MBS service and a frequency. The USD may include at least one MBS service identifier and a frequency information set. For example, the USD may include at least one item selected from the group consisting of: an MBS session identifier for identifying an MBS session, information on the start and end time of the MBS session, an SAI indicating an MBS service area in which the MBS session is provided, and information on the frequency at which the MBS session is provided.

[0103] The USD-based cell reselection control as described above assumes the following scenario. Specifically, even when the gNB 200 provides SIBx1, the gNB 200 may not provide the adjacent frequency information (mbs-SAI-InterFreqList-r17) in SIBx1. For example, when MBS services are uniformly provided in a certain frequency / area, even if all cells in the area do not broadcast the adjacent frequency information, the UE 100 can derive the appropriate frequency of interest from the frequency information provided in the USD. Therefore, by controlling the cell reselection using the frequency of interest set to the highest priority, service continuity of the broadcast service can be ensured.

[0104] On the other hand, the UE 100 in the RRC connected state identifies the frequency of interest based on SIBx1 to generate the frequency list in the MII. However, when the adjacent frequency information is not provided in SIBx1, the UE 100 cannot properly identify the frequency of interest. It is assumed that the UE 100 in the RRC idle state or the RRC inactive state identifies the frequency of interest based on USD; however, there is a problem that such operation is not assumed for the UE 100 in the RRC connected state. In the following embodiments, a method and operation for solving such a problem will be described.

[0105] As described above, the UE 100 receives a predetermined SIB (SIBx1) which may include frequency information indicating a correspondence relationship between an identifier of an MBS service (MBS service identifier) ​​and a frequency for providing the MBS service from a serving cell ( Fig.10 The UE 100 generates an MII including a frequency list indicating frequencies of interest as MBS frequencies that the UE 100 is receiving or is interested in receiving ( Fig.10 Step S5), and sends MII to the serving cell ( Fig.10 Step S6).

[0106] In an embodiment, when generating the MII, the UE 100 includes the frequencies of interest in the frequency list even when the frequencies of interest to the UE 100 are not indicated in the predetermined SIB (SIBx1). Therefore, even when the frequency information is not provided in the SIBx1 (specifically, mbs-SAI-InterFreqList-r17), the network can identify the frequencies of interest to the UE 100 based on the frequency list in the MII.

[0107] For example, even when the frequency of interest is not indicated in the predetermined SIB, the UE 100 includes the frequency of interest in the frequency list based on upper layer information (USD) stored in the UE 100, which is information indicating a correspondence relationship between an identifier of an MBS service (MBS service identifier) ​​and a frequency for providing the MBS service. In other words, the UE 100 includes the frequency of interest in the frequency list based on the USD instead of the SIBx1.

[0108] The UE 100 may include the frequency of interest in the frequency list based on the SIB for cell reselection received from the serving cell instead of SIBx1. The SIB for cell reselection is a SIB provided from the serving cell and is a SIB indicating a different frequency from the frequency of the serving cell. The SIB for cell reselection may be SIB type 4 (SIB4) and / or SIB type 5 (SIB5) defined in the 3GPP technical specification.

[0109] Such SIB for cell reselection includes one or more inter-frequency identifiers and a set of cell reselection parameters (e.g., frequency priority). The inter-frequency indicated in the SIB for cell reselection corresponds to the frequency of the neighboring cell and is therefore considered as a frequency available to the UE 100. The UE 100 includes the frequencies of interest (which are only such available frequencies) in the frequency list. Note that since the desired MBS service is not necessarily provided at the inter-frequency indicated in the SIB for cell reselection, the UE 100 includes the frequencies of interest in the frequency list using the SIB for cell reselection and the USD.

[0110] (4.1) Operations to identify frequencies of interest

[0111] Options 1 to 3 of an operation of identifying a frequency of interest according to an embodiment will be described. The UE 100 identifies a frequency of interest according to one of the following options 1 to 3.

[0112] (4.1.1) Option 1

[0113] In Option 1, when generating MII, UE 100 identifies the frequency of interest based on upper layer information (USD) regardless of frequency information in a predetermined SIB (SIBx1). In other words, UE 100 identifies the frequency of interest based on USD information without checking frequency information provided in SIBx1.

[0114] Fig.12 is a diagram illustrating the operation of Option 1 according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0115] UE 100 regards a frequency satisfying the conditions of steps S102 to S104 as a frequency of interest (MBS frequency of interest) (step S101).

[0116] Step S102 is a determination of the following condition: at least one MBS session (desired MBS service) that the UE 100 is currently receiving or is interested in receiving via a broadcast MRB is currently in progress or is about to start.

[0117] Step S103a is a determination of the following condition: regarding a certain frequency, the service identifier for the desired MBS service indication in the USD is included in the SIBx1 acquired from the PCell (serving cell). In Option 1, this condition determination is omitted. In other words, the UE 100 identifies the frequency of interest based on the USD regardless of the frequency information included in the SIBx1.

[0118] Step S104 is to determine the following condition: the supportedBandCombination of UE 100 included in UE-NR-Capability includes at least one frequency band combination, and the at least one frequency band combination includes a set of frequencies of interest (MBS frequencies of interest) (that is, UE 100 can simultaneously receive broadcast MRBs under the set of frequencies of interest).

[0119] In this way, by omitting (disabling) the condition determination of step S103a, even when SIBx1 does not include adjacent frequency information (and an MBS service identifier at an adjacent frequency), the UE 100 can identify a frequency of interest (MBS frequency of interest) based on the USD. For example, the UE 100 reads a service identifier and frequency information for providing a service from the USD, and identifies a frequency providing a service of interest (desired MBS service) as a frequency of interest.

[0120] Note that UE 100 may determine whether to omit (disable) the conditional determination in step S103a based on an indication (or permission) from gNB 200. For example, gNB 200 may use SIBx1 to notify UE 100 of information for permitting or indicating to omit the conditional determination of step S103a (or using information of USD to identify the frequency of interest).

[0121] (4.1.2) Option 2

[0122] In Option 2, when generating the MII, in response to the UE 100 recognizing that the predetermined SIB (SIBx1) does not include frequency information, the UE 100 identifies the frequency of interest based on the upper layer information (USD). In other words, only when the frequency information is not provided in the SIBx1, the UE 100 identifies the frequency of interest based on the frequency information provided in the USD.

[0123] Fig.13 is a diagram illustrating the operation of Option 2 according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0124] The operations other than step S103b are the same and / or similar to those of Option 1 above.

[0125] In step S103b, first, the UE 100 determines the following condition: regarding a certain frequency, the service identifier indicated in the USD regarding the desired MBS service is included in the SIBx1 acquired from the PCell (serving cell). Secondly, when the frequency information is not available in the SIBx1 regarding the MBS service (MBS session), the UE 100 determines the frequency regarding the desired MBS service based on the USD. Specifically, when the UE 100 recognizes that the adjacent frequency information (and / or the MBS service identifier at the adjacent frequency) is not provided, the UE 100 reads the service identifier (SAI, etc.) and the frequency information for providing the service from the USD, and identifies the frequency providing the service of interest as the frequency of interest.

[0126] In this way, by adding determination based on USD as the conditional determination of step S103b, UE 100 can identify the frequency of interest (MBS frequency of interest) based on USD even when SIBx1 does not include adjacent frequency information (and MBS service identifiers at adjacent frequencies).

[0127] (4.1.3) Option 3

[0128] In Option 3, in response to UE 100 recognizing that a predetermined SIB (SIBx1) does not include frequency information when generating MII, UE 100 identifies a frequency of interest based on SIB for cell reselection and upper layer information. For example, when frequency information is not provided in SIBx1, UE 100 identifies a frequency that matches a frequency associated with a desired MBS service in USD among frequencies provided in SIB4 and / or SIB5 as a frequency of interest.

[0129] Fig.14 is a diagram illustrating the operation of Option 3 according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0130] The operations other than step S103c are the same and / or similar to those of Option 1 above.

[0131] In step S103c, first, the UE 100 determines the following condition: regarding a certain frequency, the service identifier indicated in the USD regarding the desired MBS service is included in the SIBx1 acquired from the PCell (serving cell). Secondly, when the frequency information is not available in the SIBx1 regarding the MBS service (MBS session), the UE 100 performs a determination based on SIB4 and / or SIB5. Specifically, when the UE 100 recognizes that the adjacent frequency information (and / or the MBS service identifier at the adjacent frequency) is not provided in the SIBx1, the UE 100 reads the service identifier (SAI, etc.) and the frequency information for providing the service from the USD. Then, when SIB4 (and / or SIB5) includes a frequency for providing a service of interest, the UE 100 identifies the frequency as a frequency of interest.

[0132] In this way, by adding a determination based on USD and SIB4 and / or SIB5 as a conditional determination of step S103c, UE 100 can identify the frequency of interest (MBS frequency of interest) based on USD and SIB4 and / or SIB5 even when SIBx1 does not include adjacent frequency information (and an MBS service identifier at the adjacent frequency).

[0133] Note that the UE 100 may determine whether to perform the SIB4 and / or SIB5-based determination in step S103c based on an indication (or permission) from the gNB 200. For example, the gNB 200 may use SIBx1 to notify the UE 100 of information for permitting or indicating the SIB4 and / or SIB5-based determination in step S103c. Under this assumption, in step S103c, in response to the presence of an indication to use SIB4 and / or SIB5 in SIBx1, rather than the frequency information being unavailable in SIBx1, the UE 100 may read a service identifier (SAI, etc.) and frequency information for providing a service from the USD, and when a frequency providing a service of interest is included in SIB4 (and / or SIB5), the UE 100 may identify the frequency as a frequency of interest.

[0134] (4.2) Operation to set the frequency of interest to the frequency list

[0135] Options A to C of an operation of setting a frequency of interest as a frequency list according to an embodiment will be described. The UE 100 sets the frequency list to include the frequency of interest according to one of the following options A to C.

[0136] Based on the operation for identifying the frequency of interest in (4.1) above, the frequency of interest can be identified even when the adjacent frequency information is not provided in SIBx1. However, it is assumed that the frequency list in the MII is set to include the frequency identifier (absolute radio frequency channel number (ARFCN)) provided in SIBx1. Therefore, even when the frequency of interest is identified, the frequency of interest cannot be included in the MII. In options A to C, this problem can be solved.

[0137] (4.2.1) Option A

[0138] In option A, when generating the MII, the UE 100 sets the frequency list to include all the MBS frequencies of interest identified based on the upper layer information (USD), regardless of the frequency information in the predetermined SIB (SIBx1). In other words, the UE 100 sets the MII to include all the frequencies of interest identified based on the operation for identifying the frequencies of interest in (4.1) above.

[0139] Fig.15 is a diagram illustrating the operation of Option A according to an embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0140] When there is a frequency of interest (MBS frequency of interest) identified based on the operation for identifying a frequency of interest in (4.1) above (step S201), in step S202a, UE 100 sets a frequency list (mbs-FreqList) to include the frequency of interest. Specifically, UE 100 includes all frequencies of interest into the frequency list regardless of the frequency information in SIBx1. UE 100 may convert the frequency information of USD into an ARFCN value and then include the ARFCN value in the MBS frequency list.

[0141] When the UE 100 does not use the frequency information in SIBx1 to identify the frequency of interest in the above-mentioned (4.1) operation for identifying the frequency of interest, the UE 100 may perform an operation of including all frequencies of interest in the frequency list regardless of the frequency information in SIBx1. In other words, when the UE 100 uses the frequency information in SIBx1 to identify the frequency of interest, the UE 100 may use the frequency information in SIBx1 to perform an operation of including the frequency of interest in the frequency list.

[0142] Note that UE 100 may determine whether to include all frequencies of interest into the frequency list regardless of the frequency information in SIBx1 based on an indication (or permission) from gNB 200. For example, gNB 200 uses SIBx1 to notify UE 100 of information for permitting or indicating the following operation: including all frequencies of interest into the frequency list regardless of the frequency information in SIBx1.

[0143] (4.2.2) Option B

[0144] In option B, when generating the MII, in response to the UE 100 recognizing that the predetermined SIB (SIBx1) does not include frequency information, the UE 100 sets the frequency list to include all MBS frequencies of interest identified based on the upper layer information (USD). In other words, only when the frequency information is not provided in the SIBx1, the UE 100 sets the MII to include all frequencies of interest.

[0145] Fig.16 is a diagram showing an operation example 1 of option B according to the embodiment, which is specifically a specification change in 3GPP technical specification TS38.331.

[0146] When there is a frequency of interest (MBS frequency of interest) identified based on the operation for identifying the frequency of interest in (4.1) above (step S201), in step S202b, UE 100 sets the frequency list (mbs-FreqList) to include the frequency of interest. Here, UE 100 includes the frequencies of interest in the frequency list (mbs-FreqList) in descending order of interest. As an identifier of the frequency of interest (the frequency list (mbs-FreqList) is set to include the frequency of interest), absoluteFrequencySSB is used for the serving frequency, and ARFCN-ValueNR included in SIBx1 is used for the adjacent frequency. Note that when there is no frequency identifier (ARFCN-ValueNR) regarding the desired MBS service in SIBx1, UE 100 includes all frequencies of interest in the frequency list.

[0147] Fig.17 is a diagram showing operation example 2 of option B according to the embodiment, which is specifically a specification change in 3GPP technical specification TS38.331.

[0148] When there is a frequency of interest (MBS frequency of interest) identified based on the operation for identifying the frequency of interest in (4.1) above (step S201) and there is frequency information (mbs-SAI-InterFreqList) in SIBx1, in step S202c, UE 100 sets the frequency list (mbs-FreqList) in MII to include the frequency of interest. Here, UE 100 includes the frequency of interest in the frequency list (mbs-FreqList) in descending order of interest. As an identifier of the frequency of interest (the frequency list (mbs-FreqList) is set to include the frequency of interest), absoluteFrequencySSB is used for the serving frequency, and ARFCN-ValueNR included in SIBx1 is used for the adjacent frequency.

[0149] On the other hand, when there is no frequency information (mbs-SAI-InterFreqList) in SIBx1, in step S203, the frequency list (mbs-FreqList) in MII is set to include the frequencies of interest. Here, UE 100 sets the frequency list to include all MBS frequencies of interest identified based on the upper layer information (USD).

[0150] In option B, the UE 100 may convert the frequency information of the USD into an ARFCN value and then include the ARFCN value in the MBS frequency list.

[0151] (4.2.3) Option C

[0152] In option C, when generating the MII, in response to the UE 100 recognizing that the predetermined SIB (SIBx1) does not include frequency information, the UE 100 sets the frequency list to include all MBS frequencies of interest identified based on the SIB for cell reselection and upper layer information (USD). In other words, when the frequency information is not provided in SIBx1, the UE 100 sets the MII to include the ARFCN included in SIB4 (and / or SIB5).

[0153] Fig.18 is a diagram showing an operation example 1 of Option C according to the embodiment, which is specifically a specification change in 3GPP Technical Specification TS38.331.

[0154] When there is a frequency of interest (MBS frequency of interest) identified based on the operation for identifying the frequency of interest in (4.1) above (step S201), in step S202d, the UE 100 sets the frequency list (mbs-FreqList) to include the frequency of interest. Here, the UE 100 includes the frequencies of interest in the frequency list (mbs-FreqList) in descending order of interest. As an identifier of the frequency of interest (the frequency list (mbs-FreqList) is set to include the frequencies of interest), the absoluteFrequencySSB is used for the serving frequency, and the ARFCN-ValueNR included in SIBx1 is used for the adjacent frequency. Note that when there is no frequency identifier (ARFCN-ValueNR) regarding the desired MBS service in SIBx1, the UE 100 includes the frequency identifier (ARFCN-ValueNR) included in SIB4 (and / or SIB5) into the frequency list regarding the adjacent frequency. In other words, when UE 100 recognizes that adjacent frequency information (and / or MBS service identifiers at adjacent frequencies) is not provided in SIBx1, UE 100 sets the frequency list to include frequencies (ARFCN values) broadcast using SIB4 (and / or SIB5) among the frequencies of interest.

[0155] Fig.19 is a diagram showing an operation example 2 of option C according to the embodiment, which is specifically a specification change in 3GPP technical specification TS38.331.

[0156] When there is a frequency of interest (MBS frequency of interest) identified based on the operation for identifying the frequency of interest in (4.1) above (step S201) and there is frequency information (mbs-SAI-InterFreqList) in SIBx1, in step S202e, UE 100 sets the frequency list (mbs-FreqList) in MII to include the frequency of interest. Here, UE 100 includes the frequency of interest in the frequency list (mbs-FreqList) in descending order of interest. As an identifier of the frequency of interest (the frequency list (mbs-FreqList) is set to include the frequency of interest), absoluteFrequencySSB is used for the serving frequency, and ARFCN-ValueNR included in SIBx1 is used for the adjacent frequency.

[0157] On the other hand, when there is no frequency information (mbs-SAI-InterFreqList) in SIBx1, in step S204, the frequency list (mbs-FreqList) in the MII is set to include the frequency of interest. Here, the UE 100 includes the frequency identifier (ARFCN-ValueNR) included in SIB4 (and / or SIB5) into the frequency list about the adjacent frequency. In other words, when the UE 100 recognizes that the adjacent frequency information (and / or the MBS service identifier at the adjacent frequency) is not provided in SIBx1, the UE 100 sets the frequency list to include the frequency (ARFCN value) broadcasted using SIB4 (and / or SIB5) among the frequencies of interest.

[0158] Note that UE 100 may determine whether to perform an operation of setting the frequency list to include ARFCN values ​​included in SIB4 and / or SIB5 based on an indication (or permission) from gNB 200. For example, gNB 200 may use SIBx1 to notify UE 100 of information for permitting or indicating the following operation: setting the frequency list to include ARFCN values ​​included in SIB4 and / or SIB5. Under this assumption, in response to the presence of an indication (or permission) to use SIB4 and / or SIB5 in SIBx1, rather than the frequency information not being provided in SIBx1, UE 100 may set the frequency list to include frequencies (ARFCN values) broadcast using SIB4 (and / or SIB5) among the frequencies of interest.

[0159] In response to using SIB4 and / or SIB5 to identify the frequency of interest in the operation of identifying the frequency of interest in the above (4.1) instead of the frequency information being provided in SIBx1, UE 100 may set the frequency list to include frequencies (ARFCN values) broadcast using SIB4 (and / or SIB5) among the frequencies of interest.

[0160] (4.3) MII configuration example

[0161] Configuration examples 1 and 2 of MII according to the embodiment will be described. UE 100 may transmit MII having the characteristics of the following configuration example 1 or 2 to the serving cell (gNB 200).

[0162] (4.3.1) MII Configuration Example 1

[0163] In configuration example 1 of MII, UE 100 adds an information source identifier indicating the information based on which the frequency of interest indicated in the frequency list (mbs-FreqList) is identified and / or set. In other words, when UE 100 does not use SIBx1 to report the frequency of interest, UE 100 notifies gNB 200 that the frequency of interest is based on USD (or the frequency of interest is based on SIB4 and / or SIB5).

[0164] As described above, when the frequency list is not identified or set based on SIBx1, it is preferable to consider notifying the information source to the gNB 200. For example, when the gNB 200 processes the frequency list notified to the gNB by the UE 100, the gNB 200 can perform different processing depending on the information source.

[0165] Fig. 20 is a diagram showing a configuration example 1 of the MII according to the embodiment, which is specifically a specification change in the 3GPP technical specification TS38.331.

[0166] The MII includes an MBSInterestIndication-r17-IE. The MBSInterestIndication-r17-IEs or MII include at least one item selected from the group consisting of: a frequency list (mbs-FreqList-r17), which is a list of MBS frequencies that the UE 100 is receiving or is interested in receiving; priority information (mbs-Priority-r17), which indicates the priority of which to prioritize between receiving all listed MBS frequencies and receiving unicast bearers; a TMGI list (mbs-ServiceList-r17), which is a list of MBS sessions that the UE 100 is receiving or is interested in receiving.

[0167] In configuration example 1, each entry (CarrierFreqMBS-r17) of the frequency list (mbs-FreqList-r17) includes MBS-frequency and Source-info. MBS-frequency is a frequency identifier (ARFCN-ValueNR) of a frequency of interest. Source-info is an information source identifier that indicates the information source referenced when the frequency list is identified or set to include the frequency of interest. Source-info indicates at least one item selected from the group consisting of SIBx1, SIB4, SIB5, and USD as information sources. Note that when Source-info is not present in the MII, it may be implicitly indicated that SIBx1 is the information source, it may be implicitly indicated that SIB4 and / or SIB5 are the information sources, or it may be implicitly indicated that USD is the information source.

[0168] Fig.21 is a diagram showing a modification of configuration example 1 of the MII according to the embodiment, which is specifically a specification change in 3GPP technical specification TS 38.331.

[0169] In this variant, unlike the mbs-FreqList-SIBx1-r17 corresponding to the existing frequency list, the MBSInterestIndication-r17-IEs in the MII may include one of the following items: mbs-FreqList-SIB4-r17, which is a frequency list of frequencies of interest when the information source is SIB4; mbs-FreqList-SIB5-r17, which is a frequency list of frequencies of interest when the information source is SIB5; or mbs-FreqList-USD-r17, which is a frequency list of frequencies of interest when the information source is USD.

[0170] When the information source is SIB4, UE 100 sets mbs-FreqList-SIB4-r17 to include the frequencies of interest, when the information source is SIB5, UE 100 sets mbs-FreqList-SIB5-r17 to include the frequencies of interest, and when the information source is USD, UE 100 sets mbs-FreqList-USD-r17 to include the frequencies of interest.

[0171] Note that, for example, the lists of SIB4 and SIB5 may be integrated as mbs-RfeqList-SIB4-SIB5-r17.

[0172] (4.3.2) MII Configuration Example 2

[0173] In configuration example 2 of the MII, depending on which piece of information the frequency of interest is identified based on, the UE 100 classifies each frequency of interest by information source. Then, the UE 100 sets the corresponding list among the lists of each information source to include the frequency of interest. In other words, the UE 100 classifies the frequency of interest for each information source, includes the frequency of interest in its corresponding list, and reports in the MII.

[0174] In this way, for all frequencies of interest, the UE 100 classifies its information sources and then reports to the network (gNB 200) using MII. Providing all frequencies of interest to the network can prompt the gNB 200 to perform further advanced determinations and facilitate information collection on the network side.

[0175] In MII configuration example 2, you can use Fig.21 UE 100 then performs processing on the identified frequencies of interest. First, UE 100 includes frequencies that match the adjacent frequencies (ARFCN) provided in SIBx1 in a frequency list whose information source is SIBx1. Second, UE 100 includes frequencies that match the adjacent frequencies (ARFCN) provided in SIB4 and / or SIB5 in a frequency list whose information source is SIB4 and / or SIB5. Third, UE 100 includes frequencies that match the frequencies provided in USD in a frequency list whose information source is USD.

[0176] Other embodiments

[0177] The above operation flow can be implemented individually and independently, and can also be implemented by combining two or more of the operation flows. For example, some steps of one operation flow can be added to another operation flow, or some steps of one operation flow can be replaced by some steps of another operation flow.

[0178] In the above embodiments and examples, an example is described in which the base station is an NR base station (i.e., gNB); however, the base station may be an LTE base station (i.e., eNB) or a 6G base station. The base station may be a relay node, such as an integrated access and backhaul (IAB) node. The base station may be a DU of an IAB node. UE 100 may be a mobile terminal (MT) of an IAB node.

[0179] A program that causes a computer to perform each process performed by UE 100 or gNB 200 may be provided. The program may be recorded in a computer-readable medium. The use of a computer-readable medium enables the program to be installed 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. A circuit for performing a process to be performed by UE 100 or gNB 200 may be integrated, and at least a portion of UE 100 or gNB 200 may be implemented as a semiconductor integrated circuit (chip set, system on chip (SoC)).

[0180] Unless otherwise expressly stated, the phrases "based on" and "depending on" used in this disclosure do not mean "based only on" and "depending only on". The phrase "based on" means both "based only on" and "based at least in part on". The phrase "depending on" means "depending only on" and "depending at least in part on". The terms "include", "comprising" and their variants do not mean "including only the items", but mean "may only include the items" or "may include not only the items but also other items". The term "or" used in this disclosure is not intended to be "exclusive or". In addition, any reference to elements using names such as "first" and "second" in this disclosure does not generally limit the number or order of these elements. These names can be used as a convenient method to distinguish two or more elements in this article. Therefore, the reference to the first element and the second element does not mean that only two elements can be adopted there or that the first element needs to be in some way before the second element. For example, when English articles such as "one", "an" and "the" are added in this disclosure by translation, these articles include plural unless otherwise clearly indicated in the context.

[0181] The embodiments have been described in detail above with reference to the accompanying drawings, but the specific configuration is not limited to the above configuration, and various design changes may be made without departing from the gist of the present disclosure.

[0182] This application claims priority to U.S. Provisional Patent Application No. 63 / 308,561 (filed on February 10, 2022), the entire contents of which are incorporated herein by reference.

[0183] Additional Notes

[0184] introduction

[0185] In RAN2#116bis-e, further discussions on MBS, idle / inactive mode procedures and RRC execution CR are mentioned as assumptions for completion of work items. The list of open issues broadly covers the important issues considered for discussion in the email. However, issues due to the frequency of interest of the MBS interest indication are not included in the list, which may have an adverse impact on the continuity of broadcast services in some deployments.

[0186] In this supplementary note, potential issues related to the frequencies of interest reported in the MBS Interest Indication are discussed.

[0187] discuss

[0188] Deployment scenarios in TS 38.304

[0189] In RAN2#116bis-e, it is agreed that whether to use the frequency information of SIBy or USD for frequency prioritization during cell reselection depends on the UE implementation.

[0190] When SIBy is provided in a cell but no frequency mapping for service is provided, the UE may preferentially use the frequency indicated in the USD.

[0191] How the information in the USD is used to determine whether to perform (or how to perform) frequency prioritization for a particular frequency / frequencies in the USD is up to the UE implementation (eg, using other explicit knowledge).

[0192] Observation 1: Which frequency information of SIBy or USD is used for frequency prioritization during cell reselection depends on the UE implementation.

[0193] Therefore, in the CR being implemented with respect to TS 38.304, conditions for prioritizing the frequencies of interest to the UE are obtained (i.e., 2) and below). Specifically, the last condition of 2) (i.e., "SIBy is provided in the serving cell, but the frequency mapping of the service is not provided, and the frequency is included in the USD of the service") is different from LTE eMBMS.

[0194] When a UE supporting MBS broadcast is receiving or is interested in receiving an MBS broadcast service and can only perform reception by camping on a frequency providing the MBS broadcast service (as defined in TS 38.300), the UE may consider that frequency to have the highest priority during the MBS broadcast session provided that the following two conditions are met.

[0195] 1) The cell reselected by the UE provides SIBx based on the frequency priority of the MBS.

[0196] SIBx is the MBS SIB used to carry the configuration of MCCH. The terminology of SIBx will be updated later to be consistent with other RAN2 specifications.

[0197] 2) One of the following:

[0198] One or more IDs (e.g., SAI) indicating the frequency in the SIBy of the serving cell, and indicating the same ID (e.g., SAI) in / with respect to the MBS broadcast service in the MBS User Service Description (USD) defined in TS 26.346, or

[0199] When the following occurs: SIBy is not provided in the serving cell and the frequency is included in the currently serving USD, or

[0200] SIBy is provided in the serving cell, but the serving frequency map is not provided and the frequencies are included in the serving USD.

[0201] NOTE: How to use the information of USD to determine whether to perform frequency prioritization on a specific frequency / frequencies included in USD depends on the UE implementation.

[0202] Under the last condition (i.e., “SIBs are provided in the serving cell, but the served frequency mapping is not provided and the frequencies are included in the served USD”), a deployment is also assumed in which the gNB does not provide frequency information in SIBy (or SIBx1 in a CR being performed with respect to RRC) even when broadcasting SIBy itself.

[0203] Observation 2: Even when broadcasting SIBy, the gNB may not provide frequency information in the SIBy.

[0204] Possibility of service continuity issues in RRC connected state

[0205] For connected UEs, the gNB ensures continuity of broadcast services while taking into account the MBS interest indication sent from the UE. The MBS interest indication may include three pieces of information (i.e., frequency of interest, service of interest, and priority between unicast and broadcast) as an alternative.

[0206] In the currently implemented CR, a method for a UE to determine the frequency of interest included in the MBS interest indication is obtained as follows (this is basically the same as the method in LTE eMBMS).

[0207] 5.x.4.3 Determination of MBS frequencies of interest

[0208] The UE performs the following operations:

[0209] 1> When the following conditions are met, the frequency is considered to be part of the MBS frequencies of interest.

[0210] 2> At least one MBS session that the UE is currently receiving or is interested in receiving via a broadcast MRB is ongoing or about to start, and

[0211] Note 1: Referring to TS 38.300 or TS 23.247, the UE can determine whether a session is in progress based on the start time and stop time indicated in the User Service Description (USD).

[0212] 2> for SIBx1 for at least one of the MBS sessions acquired from the PCell, include in the frequency one or more MBS SAIs indicated in the USD of that session, and

[0213] Note 2: The UE considers this frequency as part of the target MBS frequency even when the NG-RAN is not (temporarily) using the broadcast MRBs for this session (i.e. the UE does not check whether this session is indicated on the MCCH).

[0214] 2>The supportedBandCombination of the UE included in the UE-NR-Capability includes at least one frequency band combination, and the at least one frequency band combination includes a set of MBS frequencies of interest (that is, the UE 100 can simultaneously receive broadcast MRBs under the set of frequencies of interest).

[0215] Note 3: When the UE evaluates whether it can simultaneously receive broadcast MRBs in the set of MBS frequencies of interest, the UE does not consider the currently configured serving frequencies. In other words, the UE only considers the MBS frequencies that the UE is interested in receiving, regardless of whether these MBS frequencies can be received together using the current serving cell.

[0216] Note: USD / SAI terminology will be consistent with SA2 specifications after being updated.

[0217] Only when all conditions (i.e., the three parts of the above "2>") are met, the UE can determine the frequency of interest. In particular, for the second condition (i.e., "For at least one of these MBS sessions, SIBx1 obtained from the PCell includes one or more MBS SAIs for the frequency indicated in the USD of the session"), SIBx1 (or SIBy) needs to provide the MBS SAI for the frequency.

[0218] Observation 3: The UE is permitted to determine the frequency of interest reported in the MBS Interest Indication when the SAI for that frequency is provided in SIBx1.

[0219] The details of the SAI for NR MBS, although not determined, are assumed to be the same and / or similar to the details of SIB15 for LTE eMBMS, and as Fig.11 The results are obtained in the CR that has been executed.

[0220] In the same and / or similar manner as LTE eMBMS, SAI lists are prepared for both intra-frequency and inter-frequency. Needless to say, for inter-frequency ("mbs-SAI-InterFreqList-r17" includes "dl-CarrierFreq-r17" and "mbs-SAI-List-r17"), the SAI list is associated with the DL carrier frequency (the so-called "frequency information").

[0221] By considering Observation 2 above, it is allowed in a part of the deployment that the gNB does not provide frequency information, and this means that the gNB does not provide the SAI list for that frequency.

[0222] Observation 4: When the gNB does not provide frequency information in the same and / or similar manner as Observation 2, the gNB does not provide SAI lists for different frequencies.

[0223] In this case, the UE cannot consider this frequency as a frequency of interest and therefore cannot report it in the MBS Interest Indication as described in Observation 3 above. This means that broadcast service continuity for this frequency is not considered in the gNB.

[0224] Observation 5: When the UE does not provide the SAI list in SIBx1 as in Observation 4, the UE cannot determine the frequency of interest of the MBS interest indication as in Observation 3.

[0225] When SIBx1 (or SIBy) does not provide the SAI list (or does not provide frequency information) as in Observation 5, the connected UE cannot use the frequency information of USD for MBS interest indication, and when SIBy (or SIBx1) does not provide frequency information (or the SAI list does not exist) as in Observation 1, it is a bit strange that the idle / inactive UE can use the frequency in USD for cell reselection. In other words, in this deployment scenario, broadcast service continuity is ensured for idle / inactive UEs, but not for connected UEs.

[0226] Observation 6: In a portion of the deployment, based on Observation 5, broadcast service continuity is not ensured for connected UEs, whereas based on Observation 1, it is ensured for idle / inactive UEs.

[0227] In view of the above observations, whether the frequency information in USD needs to be processed consistently between cell reselection and MBS interest indication in RAN2 needs to be discussed. If consistency is required, the following solutions can be studied.

[0228] Alternative 1: Delete the condition "For at least one of the MBS sessions, the SIBx1 obtained from the PCell includes one or more MBS SAIs associated with the frequency indicated in the session USD."

[0229] Alternative Solution 2: After the condition of "or when there is no frequency for an MBS session available in SIBx1, the USD can be used to determine the frequency", an additional condition of "SIBx1 associated with at least one of these MBS sessions obtained from the PCell includes one or more MBS SAIs associated with the frequency indicated in the USD of the session" is provided.

[0230] In both alternatives, the UE can determine the frequencies of interest, thus ensuring broadcast service continuity in all deployment scenarios (when reported in the MBS Interest Indication).

[0231] Recommendation 1: In RAN2, it needs to be discussed whether the UE can include the frequency of the USD in the MBS interest indication in the same and / or similar way as the frequency prioritization in cell reselection even when the frequency is not provided in SIBx1.

[0232] Option 2: When consensus is reached on Recommendation 1, in RAN2, further discussion is conducted on whether to delete the sentence "2> For at least one of these MBS sessions, for the relevant frequency, the SIBx1 obtained from the PCell includes one or more MBS SAIs indicated in the USD for the session" by adopting Alternative 1, and whether to add the condition "or if there is no relevant frequency available for the MBS session in SIBx1, the relevant frequency may be determined by the USD" in Section 5.x.4.3 of the CR being implemented with respect to TS 38.331 by adopting Alternative 2.

[0233] Another related issue is the "Configuration of the content of MBS interest indication" in Section 5.x.4.5 of the CR currently being implemented, and the process is extremely similar to that of LTE eMBMS.

[0234] 5.x.4.5 Configuration of the content of MBS interest indication

[0235] The UE configures the content of the MBS interest indication as follows.

[0236] 1> When the set of MBS frequencies of interest determined according to 5.x.4.3 is not empty:

[0237] 2> Include mbs-FreqList, and in that case include the MBS frequencies of interest arranged in ascending order using the absoluteFrequencySSB of the serving frequency and the ARFCN-ValueNR (for neighboring frequencies) included in SIBx1.

[0238] As described in “ARFCN-ValueNR included in SIBx1 (for adjacent frequencies)”, when the gNB does not provide frequency information in SIBx1, and even if the UE has determined the frequency of interest, the frequency of interest cannot be included in the MBS interest indication (due to Recommendation 2, etc.).

[0239] Observation 7: When the gNB does not provide frequency information in SIBx1, and even if the UE has determined the UE’s frequencies of interest, the frequencies of interest are not included.

[0240] When consensus is reached on Recommendation 1 above, the following three alternatives are investigated to resolve the issue.

[0241] Alternative A: Delete the description "ARFCN-ValueNR included in SIBx1 (for adjacent frequencies)".

[0242] Alternative B: Change the alternative condition "mbs-FreqList including interested MBS sessions from USD" to describe "ARFCN-ValueNR included in SIBx1 (for adjacent frequencies)".

[0243] Alternative C: An alternative condition is to describe the ARFCN in SIB4 (NR inter-frequency) and / or SIB5 (inter-RAT inter-frequency) instead of SIBx1.

[0244] In any of the alternatives, the UE can report the target frequency regardless of whether the gNB can provide the frequency information in SIBx1. Thus, broadcast service continuity can be ensured in all introduced scenarios.

[0245] Recommendation 3: When consensus is reached on Recommendation 1, in RAN2, further discussions are held on whether to delete the description "ARFCN-ValueNR included in SIBx1 (for adjacent frequencies)" by adopting Alternative A, whether to add the alternative condition "mbs-FreqList including the MBS sessions of interest from USD" by adopting Alternative B, and whether to add the alternative condition of using SIB4 and SIB5 to reference ARFCN to 5.x.4.3 of CR executed regarding TS 38.331 by adopting Alternative C.

[0246] Supplementary Note 2

[0247] Features related to the above-described embodiment are described below as supplements. (1)

[0249] A communication method performed by a user equipment in a mobile communication system for providing a multicast broadcast service (MBS), the communication method comprising:

[0250] receiving a predetermined system information block (SIB) from a serving cell, the predetermined system information block including frequency information indicating a correspondence between an identifier of an MBS service and a frequency for providing the MBS service;

[0251] generating an MBS interest indication, the MBS interest indication comprising a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user equipment is receiving or is interested in receiving; and

[0252] Sending MBS interest indication to the serving cell,

[0253] Therein, even if the frequency of interest is not indicated in the predetermined SIB, the user equipment includes the frequency of interest in the list. (2)

[0255] The communication method according to (1) above, wherein:

[0256] Even if the frequency of interest is not indicated in the predetermined SIB, the user equipment includes the frequency of interest in the list based on upper layer information stored in the user equipment, which is information indicating a correspondence relationship between an identifier of the MBS service and a frequency for providing the MBS service. (3)

[0258] The communication method according to (1) or (2) above, wherein:

[0259] The frequency information indicates a correspondence between an identifier of the MBS service and an inter-frequency, where the inter-frequency is a frequency used to provide the MBS service and is different from a frequency of the serving cell. (4)

[0261] The communication method according to any one of (1) to (3) above, wherein:

[0262] The generating includes identifying the frequency of interest based on the upper layer information, regardless of the frequency information in the predetermined SIB. (5)

[0264] The communication method according to any one of (1) to (4) above, wherein:

[0265] The generating includes identifying the frequency of interest based on the upper layer information in response to the user equipment recognizing that the predetermined SIB does not include frequency information. (6)

[0267] The communication method according to any one of (1) to (5) above, further comprising:

[0268] Receive a SIB for cell reselection from the serving cell, the SIB indicating an out-of-frequency frequency different from the frequency of the serving cell,

[0269] The generating includes: in response to the user equipment recognizing that the predetermined SIB does not include frequency information, identifying the frequency of interest based on the SIB for cell reselection and upper layer information. (7)

[0271] The communication method according to any one of (1) to (6) above, wherein:

[0272] The generating includes setting the list to include all MBS frequencies of interest identified based on the upper layer information, regardless of frequency information in a predetermined SIB. (8)

[0274] The communication method according to any one of (1) to (7) above, wherein:

[0275] The generating includes: in response to the user equipment recognizing that the predetermined SIB does not include frequency information, setting the list to include all MBS frequencies of interest identified based on the upper layer information. (9)

[0277] The communication method according to any one of (1) to (8) above, wherein:

[0278] The generating includes: in response to the user equipment recognizing that the predetermined SIB does not include frequency information, setting the list to include all MBS frequencies of interest identified based on the SIB for cell reselection and upper layer information. (10)

[0280] The communication method according to any one of (1) to (9) above, wherein:

[0281] The generating includes adding to the list an information source identifier indicating on the basis of which piece of information the frequencies of interest indicated in the list are identified and / or set. (11)

[0283] The communication method according to any one of (1) to (10) above, wherein:

[0284] The build includes:

[0285] categorizing each frequency of interest by information source, depending on which piece of information the frequency of interest is identified based on; and

[0286] A corresponding list among the lists for each information source is arranged to include the frequencies of interest. (12)

[0288] A user equipment used in a mobile communication system for providing a multicast broadcast service (MBS), the user equipment comprising:

[0289] a receiver configured to receive a predetermined system information block (SIB) from a serving cell, the predetermined system information block may include frequency information indicating a correspondence between an identifier of an MBS service and a frequency for providing the MBS service;

[0290] a controller configured to generate an MBS interest indication, the MBS interest indication comprising a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user equipment is receiving or is interested in receiving; and

[0291] A transmitter configured to send an MBS interest indication to a serving cell,

[0292] Therein, the controller includes the frequency of interest in the list even if the frequency of interest is not indicated in the predetermined SIB.

[0293] Reference numerals

[0294] 1: Mobile communication system

[0295] 10: RAN

[0296] 20: CN

[0297] 100: UE

[0298] 110: Receiver

[0299] 120: Transmitter

[0300] 130: Controller

[0301] 200: gNB

[0302] 210: Transmitter

[0303] 220: Receiver

[0304] 230: Controller

[0305] 240: Backhaul communicator.

Claims

1. A communication method performed by a user equipment in a mobile communication system for providing a multicast broadcast service MBS, the communication method comprising the following steps: receiving a predetermined system information block SIB from a serving cell, wherein the predetermined system information block can include frequency information indicating a correspondence between an identifier of an MBS service and a frequency for providing the MBS service; generating an MBS interest indication, the MBS interest indication comprising a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user equipment is receiving or is interested in receiving; as well as sending the MBS interest indication to the serving cell, Even when the predetermined SIB does not include the frequency of interest, when the frequency of interest is indicated in upper layer information, the user equipment includes the frequency of interest in the list.

2. The communication method according to claim 1, wherein: The upper layer information is a user service description (USD), and the USD includes an identifier of the MBS service, information indicating a service area in which the MBS service is provided, and a frequency for providing the MBS service.

3. The communication method according to claim 1, wherein The frequency information includes information indicating a correspondence between an identifier of the MBS service and an inter-frequency, where the inter-frequency is a frequency used to provide the MBS service and is different from a frequency of the serving cell.

4. The communication method according to claim 1, wherein The generating comprises: The list is configured to include all MBS frequencies of interest identified based on the upper layer information.

5. The communication method according to claim 1, wherein The generating comprises: The frequency of interest is identified based on the upper layer information regardless of frequency information in the predetermined SIB.

6. The communication method according to claim 1, wherein: The generating includes identifying the frequency of interest based on the upper layer information in response to the user equipment recognizing that the predetermined SIB does not include the frequency information.

7. The communication method according to claim 6, further comprising: receiving a SIB for cell reselection from the serving cell, the SIB indicating an out-of-frequency frequency different from the frequency of the serving cell, The generating includes: in response to the user equipment recognizing that the predetermined SIB does not include the frequency information, identifying the frequency of interest based on the SIB for cell reselection and the upper layer information.

8. The communication method according to claim 4, wherein: The generating includes setting the list to include all MBS frequencies of interest identified based on the upper layer information, regardless of frequency information in the predetermined SIB.

9. The communication method according to claim 4, wherein The generating comprises: In response to the user equipment recognizing that the predetermined SIB does not include the frequency information, the list is set to include all MBS frequencies of interest identified based on the upper layer information.

10. The communication method according to claim 9, wherein The generating comprises: In response to the user equipment recognizing that the predetermined SIB does not include the frequency information, the list is set to include all the MBS frequencies of interest identified based on the SIB for cell reselection and the upper layer information.

11. The communication method according to any one of claims 1 to 10, wherein: The generating comprises adding an information source identifier to the list, the information source identifier indicating on the basis of which piece of information the frequencies of interest indicated in the list are identified and / or set.

12. The communication method according to any one of claims 1 to 10, wherein: The generation comprises the following steps: categorizing each frequency of interest by information source depending on which piece of information the frequency of interest is identified based on; and A corresponding list among the lists of each information source is arranged to include the frequency of interest.

13. A user equipment used in a mobile communication system for providing a multicast broadcast service MBS, the user equipment comprising: A receiver configured to receive a predetermined system information block SIB from a serving cell, wherein the predetermined system information block can include frequency information, wherein the frequency information indicates a correspondence between an identifier of an MBS service and a frequency for providing the MBS service; a controller configured to generate an MBS interest indication, the MBS interest indication comprising a list indicating frequencies of interest, the frequencies of interest being MBS frequencies that the user equipment is receiving or is interested in receiving; as well as a transmitter configured to send the MBS interest indication to the serving cell, The controller is configured to include the frequency of interest in the list even when the predetermined SIB does not include the frequency of interest when the frequency of interest is indicated in upper layer information.