Communication method, user equipment, and network node

The implementation of Small Data Transmission technology in 5G NR systems allows user equipment to participate in multicast sessions while maintaining an RRC inactive state, addressing the inefficiency of current 5G NR multicast services by reducing network and device loads through optimized resource management.

WO2024232392A1PCT designated stage expired Publication Date: 2024-11-14KYOCERA CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/017136
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-09
Filing Date
2024-05-08
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current 5G NR multicast/broadcast services in 3GPP Release 17 only allow user equipment to receive multicast sessions while in an RRC connected state, limiting efficiency and increasing load on devices and networks, as transitioning to an RRC connected state is necessary for session participation, which is not preferable for load reduction.

Method used

Implementing Small Data Transmission (SDT) technology to enable user equipment to participate in multicast sessions while maintaining an RRC inactive state, allowing communication with network nodes using SDT for session participation and data transmission, thereby reducing the need for RRC connection resumption.

Benefits of technology

Enables efficient multicast reception in an RRC inactive state, reducing network and device loads by allowing session participation without transitioning to an RRC connected state, thus optimizing resource usage and improving user equipment and network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024017136_14112024_PF_FP_ABST
    Figure JP2024017136_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a communication method executed by user equipment in a mobile communication system that provides a multicast / broadcast service (MBS), the method comprising the steps of: receiving, from a base station, information on whether or not to permit execution of session participation processing of a multicast session using a small data transmission (SDT) technology for communicating with the base station while maintaining a radio resource control (RRC) inactive state; and executing the session participation processing using the SDT technology while maintaining the RRC inactive state, on the basis of the information indicating permission of the execution of the session participation processing using the SDT technology.
Need to check novelty before this filing date? Find Prior Art

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) has defined 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 has defined 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.4.0

[0005] A communication method according to a first aspect is a communication method executed by a user equipment in a mobile communication system providing a multicast / broadcast service (MBS), the communication method comprising: receiving, from a network node, information regarding whether to permit execution of a session join procedure for a multicast session using a small data transmission (SDT) technique for communicating with the network node while maintaining a radio resource control (RRC) inactive state; and, based on the information indicating that execution of the session join procedure using the SDT technique is permitted, performing the session join procedure using the SDT technique while maintaining the RRC inactive state.

[0006] A user equipment according to a second aspect is a user equipment for use in a mobile communication system providing a multicast / broadcast service (MBS), comprising: a receiving unit that receives, from a network node, information regarding whether to permit execution of a session join procedure for a multicast session using a small data transmission (SDT) technique that communicates with the network node while maintaining a radio resource control (RRC) inactive state; and a control unit that, based on the information indicating that execution of the session join procedure using the SDT technique is permitted, performs the session join procedure using the SDT technique while maintaining the RRC inactive state.

[0007] A network node according to a third aspect is a network node for use in a mobile communication system providing a multicast / broadcast service (MBS), comprising: a transmitter configured to transmit to a user device information regarding whether or not the user device is permitted to perform a session join process for a multicast session using a small data transmission (SDT) technique that communicates with the network node while maintaining a radio resource control (RRC) inactive state.

[0008] 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 (base station) 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 example of the basic operation of a UE according to an embodiment; FIG. 7 is a diagram showing an example of the operation of a mobile communication system according to an embodiment;

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

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

[0011] 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 the network of the mobile communication system 1.

[0012] 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) and / or 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).

[0013] The NG-RAN 10 includes a base station (referred to as "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with the UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, 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 for wireless communication with the UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

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

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

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

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

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

[0019] 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 under the control of 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.

[0020] 3 is a diagram showing an example of the configuration of a gNB 200 (base station) 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] (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 RRC idle state, RRC inactive state, and RRC connected state. Note that the MBS session can be identified by an MBS session ID (e.g., TMGI (Temporary Mobile Group Identity)).

[0038] 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 scrambled by the G-RNTI.

[0039] 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 for a multicast traffic channel (MTCH), which is a type of logical channel, and a configuration of a broadcast MRB, 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).

[0040] The MCCH is a PTM downlink channel for transmitting MBS broadcast control information associated with one or more MTCHs from the network 10 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 10 to the UE 100.

[0041] (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.

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

[0043] 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, this will be extended so that UEs 100 in an RRC inactive state can also receive a multicast session.

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

[0045] 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 for the MTCH for receiving the multicast session and a setting for 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). The settings related to MTCH (MTCH settings) are settings related to MTCH reception, and include at least one of, for example, a group identifier (G-RNTI), discontinuous reception settings (DRX settings or scheduling information: MTCH transmission ON time, MTCH transmission period, reference time and time offset, HARQ retransmission settings), Layer 2 settings (PDCP settings, RLC settings), and physical channel settings (PDCCH settings, PDSCH settings, SSB mapping settings).

[0046] (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.

[0047] 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 a "new SIB") from the gNB 200. The new SIB includes a configuration of a newly introduced MCCH (also referred to as a "multicast MCCH"). Second, the UE 100 in the RRC inactive state receives a multicast MCCH from the gNB 200 based on the new SIB. The multicast MCCH includes a PTM configuration. The PTM configuration transmits a configuration related to the MTCH for receiving the multicast session and a configuration of a multicast MRB, which is an MRB for the multicast session. Third, the UE 100 in the RRC inactive state receives the MTCH based on the multicast MCCH. The MTCH transmits the multicast session (specifically, MBS data belonging to the multicast session).

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

[0049] (3) Example of System Operation The following describes operations related to multicast reception in the RRC inactive state.

[0050] In order to receive a multicast session, UE 100 needs to perform a process of joining the multicast session with CN 20. Therefore, a basic scenario is assumed in which UE 100 that is interested in receiving a multicast session first performs a process of joining the multicast session while in an RRC connected state, second transitions from the RRC connected state to an RRC inactive state, and third receives the multicast session in an RRC inactive state. Note that UE 100 joining a multicast session may mean that UE 100 is registered with CN 20 in association with the multicast session.

[0051] However, the UE 100 may be interested in receiving a multicast session after transitioning to the RRC inactive state. In such a case, the UE 100 may need to transition to the RRC connected state by resuming the RRC connection in order to perform the process of joining the multicast session. When the UE 100 transitions to the RRC connected state, the load on the UE 100 and the network 5 (particularly the gNB 200) increases. Therefore, it is not preferable from the viewpoint of load reduction for the UE 100 to resume the RRC connection in order to perform the process of joining the multicast session.

[0052] On the other hand, the mobile communication system 1 supports Small Data Transmission (SDT) technology, which enables the UE 100 to communicate (data transmission and / or signaling transmission) with the gNB 200 while remaining in an RRC inactive state (i.e., without transitioning to an RRC connected state).

[0053] The SDT procedure is initiated by transmission via a random access channel (RACH) resource configured in system information or a type 1 configuration grant (CG) resource configured in dedicated signaling (RRC Release message). In the case of RACH, the network 5 can configure RA resources for two-stage RA or four-stage RA for SDT. In the following embodiment, an example using RA-SDT, which is SDT using random access (RA), will be mainly described, but CG-SDT, which is SDT using CG, may also be used. Note that SDT is enabled on a radio bearer basis, and is initiated by the UE 100 only when the amount of uplink data waiting to be transmitted on all SDT-enabled radio bearers is less than a set amount, the downlink reference signal received power (RSRP) exceeds a set threshold, and there are valid SDT resources.

[0054] By using such SDT technology, UE 100 performs session participation processing, and UE 100 participates in the multicast session while in the RRC inactive state, and it is considered that multicast reception in the RRC inactive state is possible. However, as described above, in the basic scenario, it is assumed that UE 100 has already participated in the session, so there may be cases where gNB 200 does not support session participation processing using SDT technology.

[0055] FIG. 6 is a diagram showing an example of a basic operation of the UE 100 according to this embodiment.

[0056] In step S1, UE100 receives information from gNB200 regarding whether to allow the UE to perform a session participation process for a multicast session using SDT (SDT technology), which communicates with gNB200 while maintaining an RRC inactive state. In this embodiment, UE100 in the RRC inactive state receives broadcast information broadcast from gNB200 in a system information block (SIB) or a multicast control channel (MCCH).

[0057] In step S2, the UE 100 performs the session participation process using the SDT while maintaining the RRC inactive state, based on the broadcast information indicating that the execution of the session participation process using the SDT is permitted.

[0058] As a result, UE100 can perform a session participation process using SDT technology after confirming that gNB200 supports the session participation process using SDT technology. Therefore, if gNB200 does not support the session participation process using SDT technology, it becomes easier to prevent UE100 from performing the session participation process using SDT technology.

[0059] In this embodiment, the SDT is a random access SDT (RA-SDT) that communicates with the gNB 200 during the random access procedure. In step S2, the UE 100 may send a non-access stratum (NAS) request message for session participation processing together with message 3 (Msg3) or message A (MsgA) to be sent to the gNB 200 during the random access procedure.

[0060] Also, in step S2, UE100 may receive a NAS response message to the NAS request message for the session participation process along with message 4 (Msg4) or message B (MsgB) received from gNB200 during the random access procedure.

[0061] Furthermore, in step S2, UE100 may receive, together with the NAS response message, a point-to-multipoint (PTM) setting required for receiving the multicast session from gNB200. This makes it easy for UE100 to perform multicast reception in an RRC inactive state. Alternatively, UE100 may acquire the PTM setting in the MCCH by receiving the MCCH from gNB200 after performing a session participation process using SDT in an RRC inactive state.

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

[0063] In step S101, UE100 is in an RRC inactive state in the cell of gNB200.

[0064] In step S102, the UE 100 in the RRC inactive state is interested in multicast reception. For example, the UE 100 is interested in receiving a certain multicast session (hereinafter referred to as "multicast session #1").

[0065] In step S103, gNB200 transmits broadcast information regarding whether or not to allow the session join process of the multicast session to be performed using SDT. For example, gNB200 may transmit an SIB including an information element indicating that the session join process of the multicast session is allowed to be performed using SDT, or an information element indicating that the session join process of the multicast session is not allowed to be performed using SDT. In this operation example, gNB200 transmits an SIB including an information element indicating that the session join process of the multicast session is allowed to be performed using SDT.

[0066] UE100 determines that the session participation process using SDT is permitted based on the broadcast information received in the SIB from gNB200 (cell). Then, in step S104, UE100 starts RA-SDT.

[0067] In step S105, the UE 100 transmits Msg3 or MsgA to the gNB 200. Specifically, in the case of a four-stage RA, the UE 100 transmits a random access preamble on a physical random access channel (PRACH) to the gNB 200, the gNB 200 transmits a random access response to the UE 100, and the UE 100 transmits Msg3 to the gNB 200. The Msg3 transmission may include the transmission of an RRC resume request message. In the case of a two-stage RA, the random access preamble and Msg3 transmission are transmitted collectively as MsgA from the UE 100 to the gNB 200.

[0068] In step S105, when transmitting Msg3 or MsgA, UE100 transmits a NAS message addressed to AMF300A of CN20. The NAS message is a join request message including the session ID of the multicast session to which UE100 requests to join. AMF300A of CN20 receives the join request message from UE100. Note that in Msg3 or MsgA, when the NAS message is transmitted using an RRC message, the RRC message may include a container (dedicated NAS-Message IE) for storing the NAS message. The container may be included in an RRC Resume Request message or another RRC message.

[0069] In response to receiving the join request message from the UE 100, the AMF 300A of the CN 20 transmits a join request to the MB-SMF (Multicast Broadcast Session Management Function) of the CN 20. The MB-SMF of the CN 20 permits the join request and transmits a join response to the AMF 300A.

[0070] In step S106, in response to receiving the join response from the MB-SMF, the AMF 300A of the CN 20 transmits a NAS message (join response message) addressed to the UE 100.

[0071] In step S107, gNB200 transmits a NAS message (join response message) from AMF300A of CN20 to UE100 together with Msg4 or MsgB. Msg4 transmission or MsgB transmission may include transmission of an RRC Release message to maintain UE100 in an RRC inactive state. gNB200 may transmit the RRC Release message to UE100, including part of the PTM settings (e.g., basic settings) required to receive multicast session #1. In addition, when the NAS message is transmitted using an RRC message in Msg4 or MsgB, the RRC message may include a container for storing the NAS message (dedicated NAS-Message IE). The container may be included in an RRC Release message, an RRC Resume message, or another RRC message.

[0072] In step S108, AMF300A of CN20 may send a UE context update message to gNB200. The UE context update message may include the session ID of multicast session #1 in which UE100 has joined as the updated UE context. Based on the UE context update message, gNB200 recognizes multicast session #1 in which UE100 has joined. Note that step S108 may be performed before step S106 or simultaneously with step S106.

[0073] In step S109, gNB200 may transmit PTM settings including the settings of multicast session #1 on the MCCH for UE100. If gNB200 has transmitted the basic settings of multicast session #1 in the RRC Release message, it may transmit the remaining PTM settings on the MCCH.

[0074] In step S110, CN20 transmits multicast data for multicast session #1 to gNB200.

[0075] In step S111, gNB200 transmits multicast data of multicast session #1 from CN20 by multicast on MTCH to UE100. UE100, which is in an RRC inactive state, receives multicast data of multicast session #1 from gNB200 on MTCH.

[0076] In this operation example, an example in which gNB200 provides PTM settings to UE100 in step S107 has been described, but a scenario in which gNB200 cannot provide PTM settings to UE100 in step S107 is also assumed. In such a scenario, all PTM settings required for UE100 to perform multicast reception (MTCH reception) must be provided on the MCCH. However, it is also possible that gNB200 does not provide such PTM settings on the MCCH.

[0077] Therefore, in step S103, instead of transmitting a block configuration in an SIB indicating whether or not to allow session participation processing for a multicast session to be performed using SDT, gNB200 may also transmit an MCCH regarding whether or not to allow session participation processing for a multicast session to be performed using SDT.

[0078] Here, when gNB200 allows the execution of a session participation process for a multicast session using SDT, it may transmit an MCCH including all information necessary for multicast reception. On the other hand, when it does not allow the execution of a session participation process for a multicast session using SDT, gNB200 may transmit an MCCH including only a portion of the information necessary for multicast reception. UE100 determines whether or not it is permitted to execute a session participation process for a multicast session using SDT based on the contents of the MCCH received from gNB200.

[0079] When performing a session participation process using SDT, UE100 may notify gNB200 in step S105 that the process will be performed. This notification may be performed by transmitting Msg1 using a specific PRACH resource. Note that gNB200 may notify UE100 of the specific PRACH resource (PRACH resource for notifying session participation process using SDT) using SIB, MCCH, or dedicated signaling. Alternatively, the notification may be notified by Msg3. In this case, a restoration cause information element (Resume Cause) may be used in the RRC Resume Request message, or a new information element may be used for notification. This notification allows gNB200 to optimize the reception in steps S106 and S108 and the transmission in steps S107 and S109. For example, by performing the transmission in step S107 after the reception in step S108, the multicast reception setting can be included in the RRC Request message in step S107.

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

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

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

[0083] That is, the UE 100 may be a terminal function unit (a type of communication module) for a base station to control a repeater that relays signals. Such a terminal function unit is referred to as an MT. Examples of the MT include, in addition to the IAB-MT, an NCR (Network Controlled Repeater)-MT and a RIS (Reconfigurable Intelligent Surface)-MT.

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

[0085] A program may be provided that causes a computer to execute each process performed by the UE 100 or the gNB 200. 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 performed by the UE 100 or the gNB 200 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).

[0086] The functions performed by the UE 100 or the gNB 200 (network node) may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (Central Processing Units), 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 memory. In this specification, circuitry, unit, or means refers to hardware that is programmed to perform the described functions or hardware that executes them. 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 hardware and software used to configure the hardware and / or processor.

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

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

[0089] This application claims priority to U.S. Provisional Application No. 63 / 500,966 (filed May 9, 2023), the entire contents of which are incorporated herein by reference.

[0090] (5) Supplementary Notes The following are additional notes regarding the features of the above-described embodiment.

[0091] (Supplementary Note 1) A communication method executed by a user equipment in a mobile communication system that provides a multicast / broadcast service (MBS), comprising: receiving, from a network node, information regarding whether to permit execution of a session join process for a multicast session using a small data transmission (SDT) technique for communicating with a network node while maintaining a radio resource control (RRC) inactive state; and, based on the information indicating that execution of the session join process using the SDT technique is permitted, executing the session join process using the SDT technique while maintaining the RRC inactive state.

[0092] (Supplementary Note 2) The communication method according to Supplementary Note 1, wherein the receiving step includes a step in which the user equipment in the RRC inactive state receives the information broadcasted from the network node in a system information block (SIB) or a multicast control channel (MCCH).

[0093] (Supplementary Note 3) The communication method according to Supplementary Note 1 or 2, wherein the SDT technique is a random access SDT that performs the communication during a random access procedure, and the performing step includes a step of sending a Non-Access Stratum (NAS) request message for the session join process together with a Message 3 (Msg3) or a Message A (MsgA) that is sent to the network node during the random access procedure.

[0094] (Supplementary Note 4) The communication method according to Supplementary Note 3, wherein the performing step further comprises receiving a NAS response message to the request message together with a message 4 (Msg4) or a message B (MsgB) received from the network node during the random access procedure.

[0095] (Supplementary Note 5) The communication method according to Supplementary Note 4, wherein the performing step further comprises receiving, together with the response message, a point-to-multipoint (PTM) configuration required for receiving the multicast session from the network node.

[0096] (Supplementary Note 6) A user equipment used in a mobile communication system that provides a multicast / broadcast service (MBS), comprising: a receiving unit that receives, from a network node, information regarding whether or not to permit execution of a session join process for a multicast session using a small data transmission (SDT) technique that communicates with a network node while maintaining a radio resource control (RRC) inactive state; and a control unit that, based on the information indicating that execution of the session join process using the SDT technique is permitted, executes the session join process using the SDT technique while maintaining the RRC inactive state.

[0097] (Supplementary Note 7) A network node used in a mobile communication system that provides a multicast / broadcast service (MBS), comprising: a transmitter that transmits to a user device information on whether or not to allow the user device to perform a session join process for a multicast session using a small data transmission (SDT) technique that communicates with the network node while maintaining a radio resource control (RRC) inactive state.

[0098] 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 executed by a user device in a mobile communication system providing a multicast / broadcast service (MBS), comprising: receiving information from a network node regarding whether or not to permit execution of a session join process for a multicast session using a small data transmission (SDT) technology for communicating with a network node while maintaining a radio resource control (RRC) inactive state; and, based on the information indicating that execution of the session join process using the SDT technology is permitted, executing the session join process using the SDT technology while maintaining the RRC inactive state.

2. The communication method according to claim 1, wherein the receiving step includes the user equipment in the RRC inactive state receiving the information broadcast in a system information block (SIB) or a multicast control channel (MCCH) from the network node.

3. The communication method according to claim 1, wherein the SDT technique is a random access SDT that performs the communication during a random access procedure, and the performing includes sending a non-access stratum (NAS) request message for the session join process together with a message 3 (Msg3) or a message A (MsgA) that is sent to the network node during the random access procedure.

4. The communication method of claim 3, wherein the performing further comprises receiving a NAS response message to the request message together with a message 4 (Msg4) or a message B (MsgB) received from the network node during the random access procedure.

5. The method of claim 4, wherein said performing further comprises receiving, together with said response message, from said network node, a point-to-multipoint (PTM) setting required for receiving said multicast session.

6. A user equipment used in a mobile communication system that provides a multicast / broadcast service (MBS), comprising: a receiving unit that receives information from a network node regarding whether or not to permit execution of a session participation process for a multicast session using a small data transmission (SDT) technology that communicates with a network node while maintaining a radio resource control (RRC) inactive state; and a control unit that performs the session participation process using the SDT technology while maintaining the RRC inactive state, based on the information indicating that execution of the session participation process using the SDT technology is permitted.

7. A network node used in a mobile communication system providing a multicast / broadcast service (MBS), comprising: a transmitter that transmits to a user device information regarding whether or not to permit the user device to perform a session join process for a multicast session using a small data transmission (SDT) technique that communicates with the network node while maintaining a radio resource control (RRC) inactive state.