Communication method, user equipment, and network node

Abstract

A communication method used in a mobile communication system for providing a multicast broadcast service (MBS) comprises: a user equipment in an RRC inactive state starting an RRC connection resume procedure for a network node on the basis of the fact that the reception quality of the user equipment at the time of multicast reception has deteriorated and / or the fact that the need for the user equipment to acquire a multicast reception setting from the network node; and the user equipment transmitting, to the network node, an RRC resume request message that includes an information element pertaining to the cause of RRC resume. The information element is first information which indicates RRC resume that is related to multicast reception, second information which indicates mobile terminated (MT) access, or third information which indicates multimedia priority access (MPS) priority access.

Description

COMMUNICATION METHOD, USER EQUIPMENT, AND NETWORK NODE

[0001] The present disclosure relates to a communication method, a user equipment, and a network node for use in a mobile communication system.

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

[0003] In 3GPP Release 17, reception of MBS multicast (i.e., multicast reception) is possible only for user equipment in a radio resource control (RRC) connected state (see, for example, Non-Patent Document 1). In contrast, in 3GPP Release 18, the technical specifications are planned to be extended so that user equipment in an RRC inactive state can perform multicast reception.

[0004] 3GPP Technical Specification: TS 38.300 V17.5.0

[0005] A communication method according to a first aspect is a communication method for use in a mobile communication system providing a Multicast Broadcast Service (MBS), the method comprising: a user equipment (UE) in an RRC inactive state participating in a multicast session initiating an RRC connection resume procedure with a network node based on reception quality falling below a threshold; and the user equipment transmitting an RRC resume request message to the network node, the RRC resume request message including an information element regarding a cause of the RRC resume, the information element being information indicating Mobile Terminated (MT) access or Multimedia Priority Access (MPS) priority access.

[0006] A communication method according to a second aspect is a communication method used in a mobile communication system providing a Multicast Broadcast Service (MBS), the method comprising: a user equipment (UE) in an RRC inactive state initiating an RRC connection resume procedure with the network node based on deterioration of reception quality during multicast reception at the user equipment and / or a need for the user equipment to acquire a multicast reception configuration from a network node; and the user equipment transmitting an RRC resume request message to the network node, the RRC resume request message including an information element regarding a cause of the RRC resume, the information element being first information indicating an RRC resume related to multicast reception, second information indicating Mobile Terminated (MT) access, or third information indicating Multimedia Priority Access (MPS) priority access.

[0007] A user equipment according to a third aspect is a user equipment used in a mobile communication system providing a Multicast Broadcast Service (MBS), the user equipment comprising: a controller configured to initiate an RRC connection resume procedure with the network node when, in an RRC inactive state, the user equipment detects a deterioration in reception quality during multicast reception in the user equipment and / or when the user equipment needs to acquire a multicast reception configuration from a network node; and a transmitter configured to transmit an RRC resume request message to the network node, the RRC resume request message including an information element regarding a cause of the RRC resume, the information element being first information indicating an RRC resume related to multicast reception, second information indicating Mobile Terminated (MT) access, or third information indicating Multimedia Priority Access (MPS) priority access.

[0008] A network node according to a fourth aspect is a network node used in a mobile communication system providing a Multicast Broadcast Service (MBS), and includes a receiver that receives, from a user equipment (UE) in an RRC inactive state, an RRC resume request message including an information element regarding a cause of RRC resume, based on a deterioration in reception quality during multicast reception in the user equipment and / or a need for the user equipment to acquire a multicast reception configuration from the network node, wherein the information element is first information indicating an RRC resume related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

[0009] 1 is a diagram showing an example of the configuration of a mobile communication system according to an embodiment. FIG. 2 is a diagram showing an example of the configuration of a UE (user equipment) according to an embodiment. FIG. 3 is a diagram showing an example of the configuration of a gNB (network node) according to an embodiment. FIG. 4 is a diagram showing a protocol stack configuration of a radio interface of a user plane that handles data. FIG. 5 is a diagram showing a protocol stack configuration of a radio interface of a control plane that handles signaling (control signals). FIG. 6 is a diagram showing an overview of the operation of a UE according to an embodiment. FIG. 7 is a diagram showing an example of a first operation pattern of a mobile communication system according to an embodiment. FIG. 8 is a diagram showing another example of the first operation pattern of a mobile communication system according to an embodiment. FIG. 9 is a diagram showing an example of a second operation pattern of a mobile communication system according to an embodiment. FIG. 10 is a diagram showing another example of the second operation pattern of a mobile communication system according to an embodiment.

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

[0011] (1) System Configuration Example Fig. 1 is a diagram showing a configuration example of a mobile communication system 1 according to an embodiment. The mobile communication system 1 conforms to the 3GPP standard 5th Generation System (5GS). Although 5GS will be described below as an example, the mobile communication system may be at least partially based on an LTE (Long Term Evolution) system. The mobile communication system may be at least partially based on a 6th Generation (6G) system.

[0012] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, and a 5G core network (5GC: 5G Core Network) 20. Hereinafter, the NG-RAN 10 may be simply referred to as the RAN 10. Furthermore, the 5GC 20 may be simply referred to as the core network (CN) 20. The RAN 10 and the CN 20 constitute a network 5 of the mobile communication system 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0031] The PDCP layer performs header compression / decompression, encryption / decryption, and the like.

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

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

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

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

[0036] The NAS layer (also simply referred to as "NAS") located above the RRC layer performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300A. Note that the UE 100 has an application layer and the like in addition to the radio interface protocol. Also, a layer lower than the NAS layer is referred to as the AS layer (also simply referred to as "AS").

[0037] (2) Overview of MBS The mobile communication system 1 can perform resource-efficient distribution using multicast / broadcast services (MBS).

[0038] (2.1) MBS Broadcast In the case of a broadcast communication service (also referred to as "MBS Broadcast"), the same service and the same specific content data are simultaneously provided to all UEs 100 in a geographical area. That is, all UEs 100 within the broadcast service area are permitted to receive the data. The broadcast communication service is delivered to the UEs 100 using a broadcast session, which is a type of MBS session. The UEs 100 can receive the broadcast session in any of the following states: RRC idle state, RRC inactive state, and RRC connected state.

[0039] Point-to-Multipoint (PTM) delivery is applied to broadcast communication services. In the case of PTM transmission, the gNB 200 delivers a single copy of an MBS packet to a set (group) of multiple UEs 100. For example, the gNB 200 schedules a group-common PDSCH scrambled by a G-RNTI (Group RNTI), which is a group-common RNTI, using a group-common PDCCH having a CRC (Cyclic Redundancy Code) scrambled by the G-RNTI.

[0040] In the case of a broadcast communication service, the UE 100 receives a broadcast session in the following procedure. First, the UE 100 receives a system information block type 20 (SIB20) from the gNB 200. The SIB20 includes a configuration of a multicast control channel (MCCH), which is a type of logical channel. Second, the UE 100 receives the MCCH from the gNB 200 based on the SIB20. The MCCH includes a PTM configuration. The PTM configuration transmits a configuration (MTCH configuration) for a multicast traffic channel (MTCH), which is a type of logical channel, and a broadcast MRB configuration, which is a multicast radio bearer (MRB) for the broadcast session. The information transmitted by the MCCH is sometimes referred to as MBS broadcast control information. Third, the UE 100 receives the MTCH based on the MCCH. The MTCH transmits the broadcast session (specifically, MBS data belonging to the broadcast session).

[0041] The MCCH is a PTM downlink channel for transmitting MBS broadcast control information associated with one or more MTCHs from the network 5 to the UE 100. The MTCH is a PTM downlink channel for transmitting MBS data of either a multicast session or a broadcast session from the network 5 to the UE 100.

[0042] (2.2) MBS Multicast In the case of a multicast communication service (also referred to as "MBS multicast"), the same service and the same specific content data are simultaneously provided to a specific set of UEs. That is, not all UEs 100 within a multicast service area are permitted to receive the data. The multicast communication service is delivered to the UEs 100 using a multicast session, which is a type of MBS session.

[0043] The UE 100 can receive the multicast session only after joining the multicast session (session join). Joining the multicast session may mean being registered in the network 5 (CN 20) as the UE 100 that can receive the multicast session.

[0044] In the case of a multicast communication service, only UEs 100 in an RRC connected state can receive a multicast session in 3GPP Release 17. On the other hand, in 3GPP Release 18, the standard is extended so that UEs 100 in an RRC inactive state can also receive a multicast session.

[0045] (2.2.1) Multicast reception in RRC connected state UE100 in the RRC connected state can receive a multicast session (specifically, MBS data belonging to the multicast session) using mechanisms such as PTP (Point-to-Point) and / or PTM (Point-to-Multipoint) delivery.

[0046] In the case of a multicast communication service, the UE 100 in the RRC connected state receives a multicast session in the following procedure. First, the UE 100 receives an RRC Reconfiguration message from the gNB 200. The RRC Reconfiguration message is a message transmitted on a dedicated control channel (DCCH). The RRC Reconfiguration message transmits a setting (MTCH setting) for the MTCH for receiving the multicast session and a setting of a multicast MRB, which is an MRB for the multicast session. Second, the UE 100 receives the MTCH based on the RRC Reconfiguration message. The MTCH transmits the multicast session (specifically, MBS data belonging to the multicast session).

[0047] (2.2.2) Multicast Reception in RRC Inactive State The UE 100 in the RRC inactive state can receive a multicast session (specifically, MBS data belonging to the multicast session) using the PTM distribution mechanism.

[0048] In the case of a multicast communication service, the UE 100 in the RRC inactive state can receive a multicast session in the following procedure. First, the UE 100 in the RRC inactive state receives a newly introduced system information block (also referred to as "SIBx") from the gNB 200. The SIBx includes a configuration of a newly introduced MCCH (also referred to as "multicast MCCH"). Second, the UE 100 in the RRC inactive state receives a multicast MCCH from the gNB 200 based on the SIBx. The multicast MCCH includes a PTM configuration. The PTM configuration transmits a configuration for an MTCH for receiving a multicast session (MTCH configuration) and a configuration of a multicast inactive MRB, which is an MRB for receiving a multicast session in the RRC inactive state (multicast inactive MRB configuration). The MTCH configuration may be included in the multicast inactive MRB configuration. Third, the UE 100 in the RRC inactive state receives the MTCH based on the multicast MCCH. The MTCH transmits the multicast session, specifically, the MBS data (i.e., multicast data) belonging to the multicast session.

[0049] When gNB200 configures UE100 to receive a multicast session in an RRC inactive state, it can send a PTM setting (multicast inactive MRB setting) to UE100 using an RRC Release message including a suspend setting. In this case, when UE100 receives an RRC Release message including a PTM setting from gNB200, it transitions to an RRC inactive state and receives the multicast session (multicast reception) in the RRC inactive state.

[0050] (2.2.3) Group Notification When there is temporarily no data to transmit to UE 100 in an active multicast session, gNB 200 may transition UE 100 to an RRC inactive state. When the multicast session is deactivated, gNB 200 may transition UE 100 to an RRC idle state or an RRC inactive state.

[0051] A gNB 200 that supports MBS uses a group notification mechanism to notify UEs 100 in an RRC idle state or an RRC inactive state when a multicast session is activated by CN 20. For example, a gNB 200 that supports MBS may use a group notification mechanism to notify UEs 100 in an RRC inactive state when a multicast session has been activated and there is multicast session data to be distributed in the gNB 200.

[0052] Upon receiving the group notification, the UE 100 reconnects or resumes connection to the network 5 and transitions to the RRC connected state. The group notification is processed in the paging RNTI (P-RNTI) on the PDCCH, and the paging channel is monitored by the UE 100.

[0053] The group notification paging message includes a session identifier (MBS Session ID) that is used to page all UEs 100 in RRC idle and RRC inactive states that have joined the associated MBS multicast session, i.e., the UEs 100 are not paged individually.

[0054] When UE 100 transitions to the RRC connected state, UE 100 may stop monitoring group notifications related to a particular multicast session. That is, UE 100 stops checking the MBS session ID in paging messages. UE 100 does not monitor group notifications in cases where UE 100 leaves this multicast session, network 5 requests UE 100 to leave, or network 5 releases the multicast session.

[0055] The group notification may be performed using the MCCH or may be performed using an MCCH Change Notification. When the MCCH is used, the determination may be made based on whether or not an MTCH configuration for the MBS session of interest exists in the MCCH. When the MCCH Change Notification is used, the group notification may be notified in a predetermined bit of the DCI.

[0056] (3) Operation of the Mobile Communication System The operation of the mobile communication system 1 according to the embodiment will be described.

[0057] (3.1) Operation Overview In the embodiment, a scenario is assumed in which a UE 100 in an RRC inactive state initiates an RRC connection resume (also referred to as "RRC resume") in relation to a multicast session (multicast reception).

[0058] In the RRC connection resume procedure, the UE 100 transmits an RRC resume request message to the gNB 200. The RRC resume request message includes a Resume Cause, which is an information element regarding the cause of the RRC resume. The gNB 200 that receives the RRC resume request message can identify the cause of the RRC resume of the UE 100 based on the Resume Cause. This makes it possible to determine whether to accept the RRC resume request based on the Resume Cause, for example, during network congestion.

[0059] However, when the UE 100 in the RRC inactive state starts the RRC connection resume in relation to the multicast session (multicast reception), there is a problem that it is not clear what information the UE 100 should set in the Resume Cause. In the following embodiment, an operation for enabling the UE 100 to set appropriate information in the Resume Cause in such a case will be described.

[0060] Here, cases in which UE100 in an RRC inactive state starts RRC connection resume in connection with a multicast session (multicast reception) are when the reception quality during multicast reception at UE100 deteriorates and / or when UE100 needs to obtain multicast reception settings (PTM settings) from gNB200.

[0061] In the embodiment, the case where the reception quality during multicast reception at UE 100 has deteriorated is a case where the reference signal received power (RSRP) measured by UE 100 for the serving cell falls below an RSRP threshold set in UE 100 by the network 5, and / or a case where the reference signal received quality (RSRQ) measured by UE 100 for the serving cell falls below an RSRQ threshold set in UE 100 by the network 5. However, the case where the reception quality during multicast reception at UE 100 has deteriorated may also be a case where the bit error rate (BER) measured by UE 100 for the multicast session exceeds a BER threshold set in UE 100 by the network 5, and / or a case where the block error rate (BLER) measured by UE 100 for the multicast session exceeds a BLER threshold set in UE 100 by the network 5.

[0062] A case where UE100 needs to acquire the multicast reception setting from gNB200 is a case where UE100 has not received the multicast reception setting of the multicast session in which UE100 has joined in the RRC release (Release) message, and the serving cell does not provide the multicast reception setting on the multicast MCCH, and UE100 may receive a paging message (group notification) indicating activation of the multicast session from the serving cell. A case where UE100 needs to acquire the multicast reception setting from gNB200 is a case where UE100 has performed cell reselection from the first cell to the second cell, and the second cell (reselected cell) does not provide the multicast reception setting of the multicast session in which UE100 has joined on the multicast MCCH.

[0063] FIG. 6 is a diagram showing an overview of the operation of the UE 100 according to the embodiment.

[0064] In step S1, UE100 in an RRC inactive state initiates an RRC connection resume procedure with gNB200 based on the deterioration of reception quality during multicast reception at UE100 and / or the need for UE100 to obtain multicast reception settings from gNB200.

[0065] In step S2, the UE 100 transmits to the gNB 200 an RRC resume request (Resume Request) message including a Resume Cause, which is an information element regarding the cause of the RRC resume. The information element (Resume Cause) is first information indicating an RRC resume related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access. The MT access may be access based on an incoming call (i.e., paging reception). The MPS may be a service that allows communication even during network congestion. The MPS priority access may be priority access by the MPS.

[0066] In this way, when UE100 in an RRC inactive state starts an RRC connection resume in relation to a multicast session (multicast reception), it transmits an RRC Resume Request message to gNB200, the RRC Resume Request message including, as a Resume Cause, first information indicating that the RRC resume is related to multicast reception, second information indicating MT access, or third information indicating MPS.

[0067] The first information is a new Resume Cause that is not specified in the technical specifications up to Release 17 of the 3GPP standard. By introducing such a new Resume Cause, the gNB 200 can understand that the RRC resume is related to multicast reception. For example, the gNB 200 that receives an RRC Resume Request message including the first information as a Resume Cause may make an acceptance decision to preferentially accept the RRC resume request. When gNB200 receives an RRC Resume Request message including the first information as a Resume Cause, in response to receiving the RRC Resume Request message, gNB200 may send an RRC Release message to UE100 including multicast reception settings for the multicast session in which UE100 has joined, and maintain UE100 in an RRC inactive state.

[0068] The first information may be different when the reception quality during multicast reception in the UE 100 deteriorates and when it becomes necessary for the UE 100 to acquire the multicast reception setting from the gNB 200. For example, when the reception quality during multicast reception in the UE 100 deteriorates, the new Resume Cause may be "multicast quality (Multicast Quality)", and when it becomes necessary for the UE 100 to acquire the multicast reception setting from the gNB 200, the new Resume Cause may be "multicast configuration (Multicast configuration)".

[0069] On the other hand, the second information and the third information are existing Resume Causes already defined in the technical specifications up to Release 17 of the 3GPP standard. By reusing such existing Resume Causes, it becomes easier to minimize specification changes. The second information and the third information may be existing Resume Causes that have a higher priority than other existing Resume Causes. The second information and the third information may be existing Resume Causes for which the gNB 200 preferentially accepts RRC resume requests. This can prevent the gNB 200 from rejecting an RRC connection resume related to a multicast session (multicast reception). The third information may be an existing Resume Cause that has a higher priority than the second information.

[0070] 6 includes a control unit 130 that starts an RRC connection resume procedure with the gNB 200 in an RRC inactive state based on a deterioration in reception quality during multicast reception at the UE 100 and / or a need for the UE 100 to acquire multicast reception settings from the gNB 200, and a transmission unit 120 that transmits an RRC Resume Request message including an information element regarding the cause of the RRC resume to the gNB 200. The information element is first information indicating that the RRC resume is related to multicast reception, second information indicating MT access, or third information indicating MPS. On the other hand, gNB200 has a receiving unit 220 that receives an RRC Resume Request message including the information element from UE100 in an RRC inactive state based on the fact that the reception quality during multicast reception at UE100 has deteriorated and / or the UE100 needs to obtain multicast reception settings from gNB200.

[0071] Further based on the fact that multicast reception in the RRC inactive state is permitted by the gNB 200, the UE 100 may initiate an RRC connection resume procedure and transmit an RRC Resume Request message including any of the first to third information as an information element to the gNB 200. Multicast reception in the RRC inactive state being permitted by the gNB 200 may mean that the RRC Release message (suspend setting) indicates that multicast reception in the RRC inactive state is permitted for the multicast session in which the UE 100 has joined. This makes it easy to differentiate the operation of the UE 100 regarding the Resume Cause when multicast reception in the RRC inactive state is permitted by the gNB 200 from conventional operations.

[0072] In a first operation pattern of the embodiment, the UE 100 in the RRC inactive state may receive a paging message (group notification) indicating activation of a multicast session in which the UE 100 has joined from the gNB 200. In step S1, when the UE 100 receives the paging message, if the UE 100 does not have a multicast reception setting corresponding to the multicast session in which the UE 100 has joined, the UE 100 may initiate an RRC connection resume procedure. In step S2, the UE 100 may transmit an RRC Resume Request message to the gNB 200, the RRC Resume Request message including the first information (new Resume Cause) as an information element.

[0073] In the second operation pattern of the embodiment, in step S2, the UE 100 transmits an RRC Resume Request message including the second information or the third information (existing Resume Cause) as an information element to the gNB 200.

[0074] In a second operation pattern of the embodiment, if UE100 has not received a paging message indicating activation of a multicast session in which UE100 has joined, UE100 may initiate an RRC connection resume procedure and send an RRC Resume Request message to gNB200 that includes the second information or the third information as an information element.

[0075] In a second operation pattern of the embodiment, the UE 100, based on the fact that the UE 100 is performing multicast reception in an RRC inactive state, may start an RRC connection resume procedure and transmit an RRC Resume Request message including the second information or the third information as an information element to the gNB 200. The UE 100, based on the fact that the UE 100 is performing multicast reception in an RRC inactive state and the reception quality during multicast reception has deteriorated, may start an RRC connection resume procedure and transmit an RRC Resume Request message including the second information or the third information as an information element to the gNB 200.

[0076] In a second operation pattern of the embodiment, UE100 may initiate an RRC connection resume procedure and transmit an RRC Resume Request message to gNB200 that includes the second information or the third information as an information element based on UE100 being unable to obtain multicast reception settings from a cell that UE100 has reselected by cell reselection.

[0077] (3.2) Specific Operation Examples A first operation pattern and a second operation pattern will be described as specific examples of the operation of the mobile communication system 1. The first operation pattern and the second operation pattern may be implemented independently, or the two operation patterns may be implemented in combination.

[0078] (3.2.1) First Operation Pattern In the first operation pattern, when the UE 100 receives a group notification (paging message) and must transition to an RRC connected state to receive the multicast reception setting (PTM setting), the UE 100 sets first information (new Resume Cause) in the RRC Resume Request message. Such an operation may be applicable only when multicast session reception in the RRC inactive state is permitted by the gNB 200.

[0079] FIG. 7 is a diagram showing an example of a first operation pattern of the mobile communication system 1 according to the embodiment.

[0080] In step S101, UE100 is in an RRC connected state in the cell of gNB200. UE100 is assumed to have joined a multicast session, and this multicast session is also referred to as a joined multicast session. Being joined to a multicast session may mean being registered in network 5 (CN20) as UE100 receiving the multicast session. In the first operation pattern, the joined multicast session of UE100 is assumed to be activated after UE100 transitions to an RRC inactive state.

[0081] In step S102, gNB200 transmits an RRC Release message including a suspend setting, i.e., an RRC Release message for transitioning UE100 to an RRC inactive state, to UE100. UE100 receives the RRC Release message.

[0082] The RRC Release message in step S102 includes at least one of the following information 1) to 3).

[0083] 1) Information permitting (or instructing) multicast reception in an RRC inactive state. The information may be provided for each multicast session. The information may also be information indicating joined multicast sessions for which multicast reception in an RRC inactive state is permitted (or instructed).

[0084] 2) Information instructing the use of a new Resume Cause (first information).

[0085] 3) Information notifying that a joined multicast session is not active (i.e., inactive). The information may be information indicating, for each joined multicast session, whether the multicast session is active or not. Whether a multicast session is active or not may be synonymous with whether reception of MBS data (MTCH) corresponding to the multicast session will immediately start or not.

[0086] However, the RRC Release message in step S102 does not include multicast reception settings (PTM settings) for multicast reception in the RRC inactive state.

[0087] In step S103, in response to the reception of the RRC Release message in step S102, the UE 100 transitions to an RRC inactive state.

[0088] In step S104, gNB200 transmits a paging message (group notification) including a session identifier (MBS session ID) of the joined multicast session in response to activation of the joined multicast session of UE100. UE100 receives the paging message (group notification).

[0089] In step S105, UE 100 initiates an RRC connection resume procedure in response to receiving the paging message in step S104. Specifically, UE 100 initiates the RRC connection resume procedure in response to the paging message including the session identifier of the multicast session to which UE 100 has joined and UE 100 not having a multicast reception configuration for the multicast session to which UE 100 has joined. Not having a multicast reception configuration may mean that the multicast reception configuration has not been received in the RRC Release message in step S132 and the serving cell has not broadcast the multicast reception configuration on the multicast MCCH.

[0090] In step S106, the UE 100 sets the first information (new Resume Cause) in an RRC Resume Request message and transmits the RRC Resume Request message to the gNB 200. The gNB 200 receives the RRC Resume Request message. The UE 100 may set the first information (new Resume Cause) in the RRC Resume Request message in response to the fact that multicast reception in the RRC inactive state is permitted (or instructed) in the RRC Release message of step S102, or that the UE 100 is instructed to use the new Resume Cause (first information). The first information may be, for example, "multicast setting for RRC inactivity". The first information may be a Cause indicating that the cause is not related to unicast communication, or a Cause indicating that the cause is related only to multicast communication.

[0091] In step S107, in response to receiving the RRC Resume Request message including the first information (new Resume Cause) of step S106, gNB200 transmits to UE100 an RRC Release message including multicast reception settings and suspend settings for the multicast session to which UE100 has joined. That is, gNB200 provides UE100 with the multicast reception settings in the RRC Release message without transitioning UE100 to the RRC connected state. UE100 receives the RRC Release message.

[0092] In step S108, gNB200 transmits MBS data (multicast data) of the multicast session in which UE100 has joined on MTCH.

[0093] In step S109, UE100 applies the multicast reception setting of step S107 and performs multicast reception in the RRC inactive state. Specifically, UE100 receives MBS data (multicast data) of the multicast session in which UE100 has joined from gNB200 on MTCH.

[0094] 8 is a diagram showing another example of the first operation pattern of the mobile communication system 1 according to the embodiment. Here, differences from the operation example in FIG. 7 will be described.

[0095] The operations of steps S131 to S136 are the same as the operation example of Fig. 7 . However, the operation of step S134 may be omitted. For example, the UE 100 may start the RRC connection resume procedure in response to a deterioration in the reception quality during multicast reception at the UE 100 (step S135). The first information (new Resume Cause) included in the RRC Resume Request message of step S136 may be information indicating a deterioration in multicast reception quality.

[0096] In step S137, in response to receiving the RRC Resume Request message including the first information (new Resume Cause) of step S136, the gNB200 decides to transition the UE100 to an RRC connected state, and transmits an RRC Resume message to the UE100. The UE100 receives the RRC Resume message. The gNB200 may decide to transition the UE100 to an RRC connected state in response to the network congestion being alleviated.

[0097] In step S138, in response to receiving the RRC Resume message in step S137, UE100 transmits an RRC Resume Complete message to gNB200. gNB200 receives the RRC Resume Complete message.

[0098] In step S139, the UE 100 transitions from the RRC inactive state to the RRC connected state.

[0099] In step S140, gNB200 transmits to UE100 an RRC Reconfiguration message including multicast reception settings for the multicast session to which UE100 has joined. UE100 receives the RRC Reconfiguration message.

[0100] In step S141, gNB200 transmits MBS data (multicast data) of the multicast session in which UE100 has joined on MTCH.

[0101] In step S142, UE100 applies the multicast reception setting of step S140 and performs multicast reception in the RRC connected state. Specifically, UE100 receives MBS data (multicast data) of the multicast session in which UE100 has joined from gNB200 on MTCH.

[0102] (3.2.2) Second Operation Pattern In the second operation pattern, UE100 sets Resume Cause to "MT Access" or "MPS Priority Access" in RRC resume related to a multicast session (multicast reception). Such an operation may be applied when UE100 has not received a group notification (paging message). Such an operation may be applied when UE100 is receiving a multicast session in an RRC inactive state, particularly when the reception quality of the multicast session deteriorates in the RRC inactive state. Such an operation may be applied when UE100 performs cell reselection and is unable to obtain PTM settings from the reselected cell. Such an operation may be applied when UE100 has received permission (instruction) for multicast reception in an RRC inactive state from gNB200.

[0103] 9 is a diagram showing an example of the second operation pattern of the mobile communication system 1 according to the embodiment. Here, differences from the above-described first operation pattern will be mainly described.

[0104] In step S201, UE100 is in an RRC connected state in the cell of gNB200. It is assumed that UE100 has already participated in a certain multicast session.

[0105] In step S202, the gNB 200 transmits an RRC Release message including a suspend setting, i.e., an RRC Release message for transitioning the UE 100 to an RRC inactive state, to the UE 100. The UE 100 receives the RRC Release message. The RRC Release message of step S202 may include information similar to that of the first operation pattern.

[0106] In step S203, the UE 100 transitions to an RRC inactive state in response to the reception of the RRC Release message in step S202. The UE 100 in the RRC inactive state may perform multicast reception.

[0107] In step S204, the UE 100 starts an RRC connection resume procedure. In a second operation pattern, the UE 100 may start the RRC connection resume procedure in response to at least one of the following conditions 1) to 3) being satisfied.

[0108] 1) The reception quality at the time of multicast reception at UE 100 has deteriorated.

[0109] 2) UE100 performs cell reselection, and the reselected cell (the cell on which UE100 is newly camped) does not provide a multicast MCCH including multicast reception settings for the multicast session to which UE100 has joined.

[0110] 3) As in the first operation pattern, the UE 100 receives a group notification (paging message) and does not hold a valid PTM setting. In addition, it may be the case that multicast reception in the RRC inactive state is permitted (instructed).

[0111] In step S205, the UE 100 sets the second information (MT Access) as Resume Cause in an RRC Resume Request message, and transmits the RRC Resume Request message to the gNB 200. The gNB 200 receives the RRC Resume Request message.

[0112] In step S206, in response to receiving the RRC Resume Request message including the second information of step S205 as Resume Cause, gNB200 preferentially accepts the RRC resume of UE100 and transmits an RRC Resume message to UE100. UE100 receives the RRC Resume message.

[0113] In step S207, in response to receiving the RRC Resume message in step S206, UE100 transmits an RRC Resume Complete message to gNB200. gNB200 receives the RRC Resume Complete message.

[0114] In step S208, the UE 100 transitions from the RRC inactive state to the RRC connected state.

[0115] In step S209, gNB200 transmits to UE100 an RRC Reconfiguration message including multicast reception settings for the multicast session to which UE100 has joined. UE100 receives the RRC Reconfiguration message.

[0116] In step S210, gNB200 transmits MBS data (multicast data) of the multicast session in which UE100 has joined on MTCH.

[0117] In step S211, UE100 applies the multicast reception setting of step S140 and performs multicast reception in the RRC connected state. Specifically, UE100 receives MBS data (multicast data) of the multicast session in which UE100 has joined from gNB200 on MTCH.

[0118] FIG. 10 is a diagram showing another example of the second operation pattern of the mobile communication system 1 according to the embodiment.

[0119] The operations of steps S231 to S241 are basically the same as the specific example of the operation of Figure 9. However, in step S235, UE100 sets the third information (MPS Priority Access) as Resume Cause in an RRC Resume Request message and transmits the RRC Resume Request message to gNB200. The gNB200 receives the RRC Resume Request message. In step S236, in response to receiving the RRC Resume Request message including the third information of step S235 as Resume Cause, gNB200 preferentially accepts the RRC resume of UE100 and transmits an RRC Resume message to UE100. The UE 100 receives the RRC Resume message.

[0120] (4) Other Embodiments In the above-described embodiment, multicast reception in the RRC inactive state has been mainly described, but the operation according to the above-described embodiment may be applied to multicast reception in the RRC idle state. In the RRC idle state, the above-described RRC resume (Resume) is replaced with RRC establishment (Establishment), and the above-described resume cause is replaced with establishment cause.

[0121] The above-described operational flows are not limited to being implemented independently, but can be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow. In each flow, it is not necessary to execute all steps, and only some steps may be executed. Furthermore, the order of steps in each flow may be changed as appropriate.

[0122] In the above-described embodiments and examples, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB) or a 6G base station. The base station may also be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may also be a DU of the IAB node. The UE 100 may also be an MT (Mobile Termination) of the IAB node. That is, the UE 100 may be a terminal function unit (a type of communication module) for the base station to control a relay that relays signals. Such a terminal function unit is referred to as an MT. Examples of MTs include, in addition to IAB-MT, NCR (Network Controlled Repeater)-MT and RIS (Reconfigurable Intelligent Surface)-MT.

[0123] The term "network node" primarily refers to a base station, but may also refer to a core network device or a part of a base station (CU, DU, or RU). A network node may also be configured by a combination of at least a part of a core network device and at least a part of a base station.

[0124] A program that causes a computer to execute each process according to the above-described embodiments may be provided. The program may be recorded on a computer-readable medium. Using a computer-readable medium, the program can 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. Furthermore, circuits that execute each process according to the above-described embodiments may be integrated, and at least a portion of the UE 100 or the gNB 200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0125] The functions performed by the apparatus according to the above-described embodiments may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a central processing unit (CPU), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes a program stored in a memory. In this disclosure, circuitry, units, and means refer to hardware that is programmed to perform or executes the described functions. The hardware may be any hardware disclosed herein or any hardware known to be programmed or capable of performing the described functions. If the hardware is a processor, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

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

[0127] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes can be made within the scope that does not deviate from the gist of the invention.

[0128] This application claims priority to U.S. Provisional Application No. 63 / 540,261 (filed September 25, 2023), the entire contents of which are incorporated herein by reference.

[0129] (5) First Supplementary Note The following is a supplementary note regarding the features of the above-described embodiment.

[0130] (Supplementary Note 1) A communication method used in a mobile communication system that provides a Multicast Broadcast Service (MBS), comprising: a user equipment in an RRC inactive state initiating an RRC connection resume procedure with the network node based on deterioration of reception quality during multicast reception in the user equipment and / or the need for the user equipment to acquire a multicast reception setting from a network node; and the user equipment transmitting an RRC resume request message to the network node, the RRC resume request message including an information element regarding a cause of the RRC resume, the information element being first information indicating that the RRC resume is related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

[0131] (Supplementary Note 2) The communication method according to Supplementary Note 1, wherein the user equipment initiates the RRC connection resume procedure and transmits the RRC resume request message to the network node, the RRC connection resume request message including any one of the first information to the third information as the information element, based further on the fact that multicast reception in an RRC inactive state is permitted by the network node.

[0132] (Supplementary Note 3) The communication method according to Supplementary Note 1 or 2, further comprising the user equipment receiving, from the network node, a paging message indicating activation of a multicast session in which the user equipment has joined; the initiating includes initiating the RRC connection resume procedure if, upon receiving the paging message, the user equipment does not have the multicast reception configuration corresponding to the multicast session; and the sending includes sending, to the network node, the RRC resume request message including the first information as the information element.

[0133] (Supplementary Note 4) The communication method according to Supplementary Note 1 or 2, wherein the transmitting includes transmitting the RRC resume request message including the second information or the third information as the information element to the network node.

[0134] (Supplementary Note 5) The communication method according to Supplementary Note 4, wherein the user equipment initiates the RRC connection resume procedure and sends the RRC resume request message to the network node, the RRC connection resume request message including the second information or the third information as the information element, if the user equipment has not received a paging message indicating activation of a multicast session in which the user equipment has joined.

[0135] (Supplementary Note 6) The communication method according to Supplementary Note 4 or 5, wherein the user equipment initiates the RRC connection resume procedure based on the user equipment performing multicast reception in an RRC inactive state, and transmits the RRC resume request message to the network node, the RRC resume request message including the second information or the third information as the information element.

[0136] (Supplementary Note 7) The communication method according to Supplementary Note 6, wherein the user equipment initiates the RRC connection resume procedure and transmits the RRC resume request message to the network node, the RRC resume request message including the second information or the third information as the information element, based on the user equipment performing multicast reception in an RRC inactive state and the reception quality during multicast reception having deteriorated.

[0137] (Supplementary Note 8) The communication method according to any one of Supplementary Notes 4 to 7, wherein the user equipment initiates the RRC connection resume procedure and transmits the RRC resume request message to the network node, the RRC connection resume procedure including the second information or the third information as the information element, based on the user equipment being unable to acquire a multicast reception configuration from a cell reselected by the user equipment through cell reselection.

[0138] (Supplementary Note 9) A user equipment used in a mobile communication system that provides a Multicast Broadcast Service (MBS), comprising: a control unit that initiates an RRC connection resume procedure with the network node when, in an RRC inactive state, reception quality during multicast reception in the user equipment has deteriorated and / or the user equipment needs to acquire a multicast reception setting from a network node; and a transmission unit that transmits to the network node an RRC resume request message including an information element on a cause of RRC resume, wherein the information element is first information indicating that the RRC resume is related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

[0139] (Supplementary Note 10) A network node used in a mobile communication system that provides a Multicast Broadcast Service (MBS), comprising: a receiving unit that receives, from a user equipment in an RRC inactive state, an RRC resume request message including an information element regarding a cause of RRC resume, based on a deterioration in reception quality during multicast reception in the user equipment and / or a need for the user equipment to acquire a multicast reception setting from the network node, wherein the information element is first information indicating that the RRC resume is related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

[0140] (6) Supplementary Note 2 1. Introduction The work item on enhanced MBS (eMBS) aims to support multicast reception by UEs in inactive state as follows: - Specify support for multicast reception by UEs in RRC inactive state [RAN2, RAN3]. - PTM configuration for UEs receiving multicast in RRC inactive state [RAN2]. - Investigate the impact of mobility and state transitions for UEs receiving multicast in RRC inactive state (seamless / lossless mobility is not mandatory) [RAN2, RAN3].

[0141] This appendix discusses the details of RRC resume due to bad quality and the causes of the resume.

[0142] 2. Discussion 2.1. RRC Resume Due to Deterioration of Reception Quality RAN2#123 agreed to introduce RSRP / RSRQ-based RRC Resume as follows.

[0143] For a UE receiving multicast in an RRC inactive state, the UE resumes the RRC connection when the RSRP or RSRQ measured based on the existing measurement requirements of the serving cell (whichever is set by the network) falls below a threshold set by the network. Whether the ping-pong issue needs to be addressed is a matter for further study.

[0144] The threshold can be PTM configured per MBS session via RRC Release or multicast MCCH messages.

[0145] Based on the agreement, remaining issues are discussed in the following sections.

[0146] 2.1.1 Ping-pong issue The agreement captures the considerations of "whether or not the ping-pong issue needs to be addressed / how to address it." Possible scenarios for resuming ping-pong include the following:

[0147] 1. A UE in an inactive state with deteriorating radio quality will initiate RRC resume when the RSRP / RSRQ falls below the threshold. 2. In response to the RRC resume request, a gNB under network congestion will send an RRC release with a suspend config. that includes the RSRP / RSRQ threshold. 3. A UE whose radio quality remains deteriorating will transition to an inactive state again, and since the RSRP / RSRQ will soon fall below the threshold, RRC resume will be initiated again.

[0148] To avoid ping-pong in the above scenario, the gNB may keep the UE in a connected state or set appropriate RSRP / RSRQ thresholds for the UE.

[0149] To support such a decision, the gNB may need to know the radio conditions and / or the reason for RRC resume (in this case, due to deterioration in radio quality) as soon as the UE requests RRC resume.

[0150] Observation 1: In order to guarantee QoS requirements, the gNB may need to know the UE's radio conditions when the UE requests RRC resume and the reason for RRC resume.

[0151] It should be noted that, according to the RAN2 discussions in the early stages of Release 18, the two main motivations for supporting multicast reception in the inactive state are network congestion mitigation and UE power consumption. Therefore, it is not reasonable for the gNB to always keep the UE in the connected state and configure measurement reporting every time the UE requests RRC resume.

[0152] Observation 2: Since the motivation for supporting multicast reception in the inactive state is to reduce network congestion and save UE power, it is not reasonable to rely on measurement reports to guarantee QoS requirements.

[0153] Considering the above observations, when the UE initiates RRC resume due to a deterioration in reception quality during the RRC resume procedure, it is useful for the UE to report the measurement results in the RRC resume request or RRC resume complete. Another option is for the UE to indicate the deterioration in radio conditions in the resume cause. With such information, the gNB can make an appropriate decision on whether to keep the UE in connected state for QoS guarantees.

[0154] Proposal 1: RAN2 should agree that the measurement results are reported within the RRC resume procedure or a new resume cause "Multicast quality" is introduced.

[0155] 2.1.2 Validity of RSRP / RSRQ Thresholds Configured by RRC Release RAN2 agreed that "thresholds can be configured by RRC release or by PTM configuration per MBS session via multicast MCCH messages." For dedicated configurations provided by RRC release, many settings remain valid until the corresponding timer expires. For example, dedicated frequency priority remains valid until T320 expires. This occurs regardless of cell reselection; dedicated settings provided by the source cell remain valid even after the UE reselects the target cell.

[0156] Observation 3: According to the current specification, many dedicated settings remain valid until a timer expires, regardless of cell reselection.

[0157] Regarding the RSRP / RSRQ thresholds, if they are valid after cell reselection, problems may occur assuming the following conditions: - In the source cell, PTM is transmitted with a low MCS, so the UE sets a low RSRP threshold to ensure a certain reception quality. - In the target cell after cell reselection, PTM is transmitted with a higher MCS, but the UE still applies the old RSRP threshold. - As a result, the UE will experience MTCH reception errors even though the RSRP is still better than the old threshold.

[0158] To avoid this problem, the RSRP / RSRQ thresholds should be cell-specific, considering that the PTM transmission of NR MBS is cell-specific, i.e., if the UE reselects a different cell, the old RSRP / RSRQ thresholds should be discarded.

[0159] Proposal 2: RAN2 should agree to discard the RSRP / RSRQ thresholds upon cell reselection.

[0160] Another possible issue in handling RSRP / RSRQ thresholds is which threshold should the UE apply when thresholds are provided by both RRC release and multicast MCCH. In the current specification, dedicated settings provided by RRC release generally take precedence over settings provided by SIB. However, for inactive multicast reception, RAN2 agreed that "if the PTM setting needs to be changed, RAN2 will use the MCCH to indicate it," meaning that the PTM setting provided by RRC release may be changed by the PTM setting provided by multicast MCCH. This means that the RSRP / RSRQ thresholds cannot be UE-specific, i.e., TMGI-specific, because they are overwritten by the multicast MCCH.

[0161] Proposal 3: RAN2 should ensure that the PTM configuration including RSRP / RSRQ thresholds provided by RRC release is always overridden by the configuration provided by multicast MCCH, i.e. there is no UE-specific configuration for inactive multicast reception.

[0162] 2.1.3 Other Confirmations RAN2#123 agreed that "for a UE receiving multicast in an RRC inactive state, the UE resumes the RRC connection when the measured RSRP or RSRQ [...] of the serving cell falls below a threshold [...]." The RSRP / RSRQ threshold is introduced to guarantee QoS for multicast reception in an inactive state.

[0163] On the other hand, if the multicast session is deactivated by the network, a UE in an inactive state may not receive the MTCH (or temporarily not receive data) when the session is deactivated. In this case, the UE is considered the same as a legacy UE in an inactive state, so RRC resume due to quality deterioration (RSRP / RSRQ threshold) is not required. As already implied in the above agreement, a UE in an inactive state must ensure that it does not initiate RRC resume if the multicast session is deactivated (or there is temporarily no data), even if the RSRP / RSRQ deteriorates below the threshold.

[0164] Proposal 4: RAN2 needs to ensure that inactive UEs do not initiate RRC resume when the multicast session is disabled (or there is temporarily no data), even if the RSRP / RSRQ becomes worse than the threshold.

[0165] In RAN2#123, RAN2 discussed whether the threshold could be based on BLER, but ultimately RAN2 decided to adopt RSRP / RSRQ.

[0166] On the other hand, in Release 17, it was a common understanding in RAN2 that SFN (single frequency network) can only be deployed depending on the network implementation, e.g., within a DU. In inter-cell SFN, reception quality is stable even at the cell edge by combining reception from MTCHs of different cells. However, RSRP / RSRQ are cell-specific and degrade at the cell edge when moving away from SFN. Therefore, RSRP / RSRQ thresholds do not work well in SFN deployments, but BLER thresholds can avoid such issues.

[0167] Proposal 5: RAN2 should ensure that the NW implementation does not operate the SFN (Single Frequency Network) allowed in Release 17 at the RSRP / RSRQ threshold in Release 18.

[0168] RAN2#123 agreed to reuse existing resume causes for RRC resume due to several reasons other than the deterioration of reception quality discussed in the previous section in Release 18. However, it is still necessary to analyze which existing resume causes are applicable and whether new resume causes are really unnecessary.

[0169] No new resume causes are introduced for UEs receiving inactive MC when resuming due to quality degradation or incorrect SIBx / PTM configuration, unless a problem is identified with using one of the existing resume causes.

[0170] Currently, 11 resumes are defined, along with five spare fields: ResumeCause ::= ENUMERATED {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess, spare1, spare2, spare3, spare4, spare5}

[0171] Similar to observation 2 above, one of the motivations for inactive multicast reception is to alleviate network congestion, so the analysis must consider the case when the network is congested.

[0172] Observation 4: The mapping of RRC resume and existing resume causes for multicast reception needs to take into account the congestion state of the network.

[0173] Typical gNB decisions when receiving an RRC Resume request during network congestion can be classified as follows: - Always accept emergency situations; - Prioritize highPriorityAccess, mps-PriorityAccess, and mcs-PriorityAccess; - Accept mt-Access and mo-Signalling (as much as possible); - May reject mo-Data, mo-VoiceCall, mo-VideoCall, and mo-SMS; - In the case of rna-Update, respond with an RRC release with a new RNA.

[0174] Observation 5: Resume allows the gNB to decide whether to accept, reject, or release with a new RNA in response to an RRC resume request, especially in the case of NW congestion.

[0175] RAN2 has agreed that the UE will initiate RRC resume in two cases: due to quality degradation or insufficient SIBx / PTM configuration. From the perspective of the impact on network load, these reasons are characterized as follows:

[0176] As discussed in Section 2.1.1, in the case of RRC resume due to quality deterioration, the UE must remain connected because if the UE is released again while in inactive, QoS requirements will no longer be guaranteed. Considering that the UE must remain connected, the UE does not consume additional downlink resources (since it only receives PTMs already sent to other UEs), but it does consume uplink resources (e.g., HARQ ACKs). In times of network congestion, this consumes slightly more resources compared to multicast reception in inactive state, but may still be prioritized over resume requests for unicast services. In other words, the gNB may prioritize RRC resume requests for multicast reception over RRC resume requests for unicast reception, but may still reject the RRC resume request due to high congestion.

[0177] In the case of RRC resume due to incomplete SIBx / PTM configuration, if the radio conditions are good, the UE is released with PTM configuration, i.e., RRC resume, and can receive the multicast session. Therefore, in terms of network congestion, it is "light," i.e., it consumes almost no downlink / uplink resources. In other words, the NW can immediately accept the RRC resume request, assuming the RRC release with PTM configuration of RRC resume.

[0178] Observation 6: In order to keep the UE connected when the network is congested, the gNB may reject RRC resume due to quality degradation, which may have some impact on the network congestion.

[0179] Observation 7: Due to SIBx / PTM configuration deficiency, the gNB can accept RRC resume and immediately release UEs with PTM configuration, as this does not affect network congestion.

[0180] Considering the above discussion, RRC resume due to bad quality may be mapped to either mo-Data, mo-VoiceCall, mo-VideoCall, or mo-SMS. However, since multicast reception in Connected does not require additional PDSCH resources (i.e., PTM is already provided for other UEs), current gNB implementations for these existing resume causes may be affected if a different type of communication (i.e., multicast reception only) is mapped to an existing resume cause.

[0181] For RRC resume due to lack of SIBx / PTM settings, there is no mapped resume cause because there is a new intent of RRC resume with PTM settings. For rna-Update, a similar gNB decision is assumed, but the gNB provides RNA instead of PTM settings for RRC resume. This means that the gNB cannot send an RRC release with PTM settings in response to an RRC resume request, and the gNB may mistakenly reject the UE's request even though the UE is only requesting a PTM setting update, which has no impact on network congestion.

[0182] Observation 8: There is no existing resume cause that matches the gNB's expected decision in the case of an RRC resume request, either due to quality degradation or insufficient SIBx / PTM configuration.

[0183] RAN2 has indeed identified new possible resume causes with the following discussion: Resume Causes: 1. Multicast Quality 2. Multicast Configuration

[0184] These two resume causes can easily solve all the problems discussed above without potentially impacting current gNB implementations. As discussed above, the two resume causes are useful for gNBs to appropriately guide different results. Therefore, two new resume causes should be introduced accordingly.

[0185] Since 3GPP is likely to begin considering 6G from Release 20, 5G NR is expected to evolve over only the next two releases (i.e., up to Release 20 at most). Given the history of additional resumes in past releases, three resumes in Release 18 will be sufficient.

[0186] Proposal 6: RAN2 should agree on a new resume cause "Multicast Quality" to be set when RRC resume is initiated due to quality degradation. Expected gNB decisions take priority over MO data, etc.

[0187] Proposal 7: RAN2 should agree on a new resume cause "multicast configuration" that is set when RRC resume is initiated due to SIBx / PTM misconfiguration. The expected gNB decision is to respond with an RRC release with PTM configuration.

[0188] 1: Mobile communication system 5: Network 10: RAN 20: CN 100: UE (user equipment) 110: Receiving unit 120: Transmitting unit 130: Control unit 200: gNB (base station) 210: Transmitting unit 220: Receiving unit 230: Control unit 240: Backhaul communication unit

Claims

1. A communication method used in a mobile communication system providing a Multicast Broadcast Service (MBS), comprising: a user equipment (UE) participating in a multicast session and in a Radio Resource Control (RRC) inactive state initiates an RRC connection resume procedure with a network node based on reception quality falling below a threshold; and the user equipment transmits an RRC resume request message to the network node, the RRC resume request message including an information element regarding a cause of the RRC resume, the information element being information indicating Mobile Terminated (MT) access or Multimedia Priority Access (MPS) priority access.

2. A communication method used in a mobile communication system providing a Multicast Broadcast Service (MBS), comprising: a user equipment in an RRC inactive state initiates an RRC connection resume procedure with respect to the network node based on deterioration of reception quality during multicast reception in the user equipment and / or the need for the user equipment to acquire multicast reception settings from a network node; and the user equipment transmits an RRC resume request message to the network node, the RRC resume request message including an information element regarding a cause of the RRC resume, the information element being first information indicating an RRC resume related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

3. The communication method according to claim 2, further comprising: based on the fact that multicast reception in an RRC inactive state is permitted by the network node, the user equipment initiates the RRC connection resume procedure and transmits the RRC resume request message to the network node, the RRC resume request message including any one of the first information to the third information as the information element.

4. The communication method according to claim 2, further comprising the user equipment receiving from the network node a paging message indicating activation of a multicast session to which the user equipment has joined, wherein the initiating includes initiating the RRC connection resume procedure if the user equipment does not have the multicast reception setting corresponding to the multicast session upon receiving the paging message, and wherein the sending includes sending the RRC resume request message to the network node, the RRC resume request message including the first information as the information element.

5. The communication method according to claim 2, wherein the transmitting step includes transmitting the RRC resume request message including the second information or the third information as the information element to the network node.

6. The communication method according to claim 5, wherein, if the user equipment does not receive a paging message indicating activation of a multicast session in which the user equipment has joined, the user equipment initiates the RRC connection resume procedure and transmits the RRC resume request message to the network node, the RRC resume request message including the second information or the third information as the information element.

7. The communication method according to claim 5, wherein the user equipment initiates the RRC connection resume procedure based on the user equipment being in an RRC inactive state and performing multicast reception, and transmits the RRC resume request message including the second information or the third information as the information element to the network node.

8. The communication method according to claim 7, wherein the user equipment initiates the RRC connection resume procedure based on the fact that the user equipment is performing multicast reception in an RRC inactive state and reception quality during multicast reception has deteriorated, and transmits the RRC resume request message including the second information or the third information as an information element to the network node.

9. The communication method according to claim 5, wherein the user equipment initiates the RRC connection resume procedure and transmits the RRC resume request message including the second information or the third information as the information element to the network node based on the user equipment being unable to acquire a multicast reception setting from a cell reselected by cell reselection.

10. A user equipment used in a mobile communication system providing a Multicast Broadcast Service (MBS), comprising: a control unit that initiates an RRC connection resume procedure with respect to the network node when, in an RRC inactive state, the user equipment detects deterioration in reception quality during multicast reception and / or the user equipment needs to acquire a multicast reception setting from a network node; and a transmission unit that transmits to the network node an RRC resume request message including an information element regarding a cause of the RRC resume, wherein the information element is first information indicating an RRC resume related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

11. A network node used in a mobile communication system providing a Multicast Broadcast Service (MBS), comprising: a receiving unit that receives an RRC resume request message including an information element regarding a cause of RRC resume from a user equipment in an RRC inactive state, based on a deterioration in reception quality during multicast reception in the user equipment and / or a need for the user equipment to acquire a multicast reception setting from the network node, wherein the information element is first information indicating an RRC resume related to multicast reception, second information indicating MT (Mobile Terminated) access, or third information indicating MPS (Multimedia Priority Access) priority access.

Images