Communication method and user equipment
By receiving multicast sessions in the RRC idle or inactive state in the user equipment and measuring the reception quality, the problem that 5G/NR multicast service cannot transition to the RRC connection state when the reception quality is lower than the threshold is solved, and the multi-to-many service is realized Guarantee of broadcast reception quality and optimization of resource consumption.
Patent Information
- Application Number
- CN202380027741.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-01-18
- Filing Date
- 2023-01-10
- Publication Date
- 2024-11-05
AI Technical Summary
The existing 5G/NR multicast and broadcast services are difficult to effectively transition to the RRC connection state when the reception quality is below the threshold, resulting in the QoS requirements of multicast reception that may not be met, increasing the resource consumption of network and equipment.
The user equipment receives a multicast session in the RRC idle or inactive state and measures the reception quality. When the reception quality is below the threshold, a transition to the RRC connection state is performed to ensure the multicast received QoS, which is in this way when necessary to RRC connection state to meet high QoS requirements.
Effectively ensure the quality of multicast reception, reduce network load, and keep the RRC idle or inactive in the case of good reception quality to reduce resource consumption.
Smart Images

Figure CN118901281A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a communication method and user equipment used in a mobile communication system. Background Art
[0002] In the 3rd Generation Partnership Project (3GPP) standard, technical specifications for New Radio (NR) as a fifth generation (5G) radio access technology have been defined. Compared with Long Term Evolution (LTE) as a fourth generation (4G) radio access technology, NR has features such as high speed, large capacity, high reliability, and low latency. In 3GPP, the establishment of technical specifications for multicast and broadcast services (MBS) for 5G / NR has been discussed (for example, see Non-Patent Document 1).
[0003] Reference List
[0004] Non-patent literature
[0005] Non-patent document 1: 3GPP Contribution: RP-201038, "WID revision: NR Multicast and Broadcast Services" Summary of the invention
[0006] A communication method according to a first aspect is a method performed by a user equipment in a mobile communication system for providing a multicast broadcast service (MBS). The communication method includes: receiving a multicast session from a network in an RRC idle state or an RRC inactive state; measuring a reception quality from the network in a multicast reception state in which the multicast session is being received; and in response to the measured reception quality being lower than a threshold, performing a transition process of transitioning to an RRC connected state for multicast reception.
[0007] A user equipment according to a second aspect is used in a mobile communication system to provide a multicast broadcast service (MBS). The user equipment includes: a receiver configured to receive a multicast session from a network in an RRC idle state or an RRC inactive state; and a controller configured to measure a reception quality from the network in a multicast reception state in which the multicast session is being received. The controller is configured to: in response to the measured reception quality being lower than a threshold, perform a transition process of transitioning to an RRC connected state for multicast reception. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 is a diagram showing a configuration of a mobile communication system according to an embodiment.
[0009] Figure 2 is a diagram showing a configuration of a user equipment (UE) according to an embodiment.
[0010] Figure 3 is a diagram showing the configuration of a gNB (base station) according to an embodiment.
[0011] Figure 4 is a diagram showing a configuration of a protocol stack of a radio interface of a user plane processing data.
[0012] Figure 5 : is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that processes signaling (control signals).
[0013] Figure 6 is a diagram showing an overview of MBS service delivery according to an embodiment.
[0014] Figure 7 is a diagram showing a transmission mode according to an embodiment.
[0015] Figure 8 is a diagram showing an example of internal processing related to MBS reception of a UE according to an embodiment.
[0016] Fig. 9 is a diagram showing another example of internal processing related to MBS reception of a UE according to an embodiment.
[0017] Fig.10 is a diagram showing an operation example of the mobile communication system according to the embodiment.
[0018] Fig.11 is a diagram showing a first modification example of the operation of the mobile communication system according to the embodiment.
[0019] Fig.12 is a diagram showing a second modification example of the operation of the mobile communication system according to the embodiment. DETAILED DESCRIPTION
[0020] 5G / NR multicast and broadcast services are expected to provide enhanced services compared to 4G / LTE multicast and broadcast services.
[0021] The present disclosure provides improved multicast broadcast services.
[0022] The mobile communication system according to the embodiment is described with reference to the accompanying drawings. In the description of the drawings, the same or similar reference numerals represent the same or similar parts.
[0023] Configuration of mobile communication system
[0024] Figure 11 is a diagram showing a configuration of a mobile communication system according to an embodiment. The mobile communication system 1 complies with the fifth generation system (5GS) of the 3GPP standard. The following description takes 5GS as an example, but the long term evolution (LTE) system may be at least partially applied to the mobile communication system. The sixth generation (6G) system may be at least partially applied to the mobile communication system.
[0025] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (next generation radio access network (NG-RAN)) 10, and a 5G core network (5GC) 20. Hereinafter, the NG-RAN 10 may be simply referred to as the RAN 10. The 5GC 20 may be simply referred to as the core network (CN) 20.
[0026] UE 100 is a mobile wireless communication device. UE 100 may be any device as long as UE 100 is used by a user. Examples of UE 100 include a mobile phone terminal (including a smart phone) or a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided on a sensor, a vehicle or a device provided on a vehicle (vehicle UE), and a flying object or a device provided on a flying object (air UE).
[0027] The NG-RAN 10 includes a base station (referred to as a "gNB" in a 5G system) 200. The gNBs 200 are interconnected via an Xn interface which is an interface between base stations. Each gNB 200 manages one or more cells. The gNB 200 performs wireless communication with the UE 100, which has established a connection to the cell of the gNB 200. The gNB 200 has a radio resource management (RRM) function, a function of routing user data (hereinafter, referred to as "data"), a measurement control function for mobility control and scheduling, and the like. "Cell" is used as a term to represent the smallest unit of a wireless communication area. "Cell" is also used as a term to represent a function or resource used to perform wireless communication with the UE 100. One cell belongs to one carrier frequency (hereinafter referred to as "frequency").
[0028] Note that the gNB can be connected to the Evolved Packet Core (EPC) corresponding to the core network of LTE. The LTE base station can also be connected to the 5GC. The LTE base station and the gNB can be connected via an inter-base station interface.
[0029] 5GC 20 includes an access and mobility management function (AMF) and a user plane function (UPF) 300. AMF performs various types of mobility control, etc. for UE 100. AMF manages the mobility of UE 100 by communicating with UE 100 using non-access stratum (NAS) signaling. UPF controls data transmission. AMF and UPF are connected to gNB 200 via an NG interface, which is an interface between a base station and a core network.
[0030] Figure 2 1 is a diagram showing a configuration of a UE 100 (User Equipment) according to an embodiment. The UE 100 includes a receiver 110, a transmitter 120, and a controller 130. The receiver 110 and the transmitter 120 constitute a wireless communicator that performs wireless communication with the gNB 200.
[0031] The receiver 110 performs various types of reception under the control of the controller 130. The receiver 110 includes an antenna and a receiving device. The receiving device converts a radio signal received through the antenna into a baseband signal (received signal) and outputs the obtained signal to the controller 130.
[0032] The transmitter 120 performs various types of transmission under the control of the controller 130. The transmitter 120 includes an antenna and a transmission device. The transmission device converts a baseband signal (transmission signal) output by the controller 130 into a radio signal and transmits the resultant signal through the antenna.
[0033] The controller 130 performs various types of control and processing in the UE 100. Such processing includes processing of various layers to be described later. The controller 130 includes at least one processor and at least one memory. The memory stores programs to be executed by the processor and information to be used for processing by the processor. The processor may include a baseband processor and a central processing unit (CPU). The baseband processor performs modulation and demodulation, encoding and decoding of baseband signals, etc. The CPU executes the program stored in the memory, thereby performing various types of processing.
[0034] Figure 3 2 is a diagram showing a configuration of a gNB 200 (base station) according to an embodiment. The gNB 200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communicator 240. The transmitter 210 and the receiver 220 constitute a wireless communicator that performs wireless communication with the UE 100. The backhaul communicator 240 constitutes a network communicator that performs communication with the CN 20.
[0035] The transmitter 210 performs various types of transmission under the control of the controller 230. The transmitter 210 includes an antenna and a transmission device. The transmission device converts a baseband signal (transmission signal) output by the controller 230 into a radio signal and transmits the resulting signal through the antenna.
[0036] The receiver 220 performs various types of reception under the control of the controller 230. The receiver 220 includes an antenna and a receiving device. The receiving device converts a radio signal received through the antenna into a baseband signal (received signal) and outputs the obtained signal to the controller 230.
[0037] The controller 230 performs various types of control and processing in the gNB 200. Such processing includes processing of various layers to be described later. The controller 230 includes at least one processor and at least one memory. The memory stores programs to be executed by the processor and information to be used for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation and demodulation, encoding and decoding of baseband signals, etc. The CPU executes the program stored in the memory, thereby performing various types of processing.
[0038] The backhaul communicator 240 is connected to the neighboring base station via the Xn interface between the base stations. The backhaul communicator 240 is connected to the AMF / UPF 300 via the NG interface between the base station and the core network. Note that the gNB 200 may include a central unit (CU) and a distributed unit (DU) (ie, the functions are divided), and the two units may be connected via the F1 interface as the fronthaul interface.
[0039] Figure 4 is a diagram showing a configuration of a protocol stack of a radio interface of a user plane processing data.
[0040] The radio interface protocol of the user plane includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.
[0041] The PHY layer performs encoding and decoding, modulation and demodulation, antenna mapping and demapping, and resource mapping and demapping. Data and control information are transmitted between the PHY layer of UE 100 and the PHY layer of gNB 200 via a physical channel. Note that the PHY layer of UE 100 receives downlink control information (DCI) transmitted from gNB 200 through a physical downlink control channel (PDCCH). Specifically, UE 100 blindly decodes PDCCH using a radio network temporary identifier (RNTI) and obtains the successfully decoded DCI as DCI addressed to UE 100. The DCI transmitted from gNB 200 is attached with CRC parity bits scrambled by RNTI.
[0042] The MAC layer performs priority control of data, retransmission processing by hybrid ARQ (HARQ: Hybrid Automatic Repeat Request), a random access procedure, etc. Data and control information are transmitted between the MAC layer of UE 100 and the MAC layer of gNB 200 via a transport channel. The MAC layer of gNB 200 includes a scheduler. The scheduler determines the transport format (transport block size, modulation and coding scheme (MCS)) in uplink and downlink and the resource blocks to be allocated to UE 100.
[0043] The RLC layer transmits data to the RLC layer of the receiving side by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.
[0044] The PDCP layer performs header compression / decompression, encryption / decryption, etc.
[0045] The SDAP layer performs mapping between IP flows (as a unit of QoS (Quality of Service) control performed by the core network) and radio bearers (as a unit of QoS control performed by the access stratum (AS)). Note that when the RAN is connected to the EPC, SDAP does not need to be provided.
[0046] Figure 5 : is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that processes signaling (control signals).
[0047] The protocol stack of the radio interface of the control plane includes the Radio Resource Control (RRC) layer and the Non-Access Stratum (NAS) layer instead of Figure 4 The SDAP layer shown in .
[0048] RRC signaling for various configurations is transmitted between the RRC layer of UE 100 and the RRC layer of gNB 200. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, reestablishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of UE 100 and the RRC of gNB 200, UE 100 is in the RRC connected state. When there is no connection (RRC connection) between the RRC of UE 100 and the RRC of gNB 200, UE 100 is in the RRC idle state. When the connection between the RRC of UE 100 and the RRC of gNB 200 is suspended, UE 100 is in the RRC inactive state.
[0049] The NAS layer located above the RRC layer performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300A. Note that the UE 100 includes an application layer in addition to the protocol of the radio interface. A layer lower than the NAS layer is called an AS layer.
[0050] Overview of MBS
[0051] An overview of MBS according to an embodiment will be provided below. MBS is a service in which NG-RAN 10 can provide broadcast or multicast, i.e., point-to-multipoint (PTM) data transmission to UE 100. Use cases (service types) of MBS are assumed to include public safety communications, mission-critical communications, vehicle-to-everything (V2X) communications, IPv4 or IPv6 multicast delivery, Internet Protocol Television (IPTV), group communications, and software delivery.
[0052] The broadcast service provides services to each UE 100 within a specific service area for applications that do not require highly reliable QoS. An MBS session for the broadcast service is called a broadcast session.
[0053] The multicast service does not provide services to each UE 100, but provides services to a group of UEs 100 that join the multicast service (multicast session). An MBS session for a multicast service is called a multicast session. A multicast service can provide the same content to the group of UEs 100 in a method with higher radio efficiency than a broadcast service.
[0054] Figure 6 is a diagram showing an overview of MBS service delivery according to an embodiment.
[0055] MBS services (MBS data) are transmitted from a single data source (application service provider) to multiple UEs. 5G CN (5GC) 20, which is a 5G core network, receives MBS data from the application service provider and performs replication of the MBS data to transmit the replication product.
[0056] From the perspective of 5GC 20, two multicast delivery methods are possible: 5GC shared MBS service delivery, and 5GC individual MBS service delivery.
[0057] In the 5GC individual MBS service delivery method, the 5GC 20 receives a single copy of the MBS data packets and delivers respective copies of these MBS data packets to each UE 100 via the PDU session of each UE 100. Therefore, one PDU session for each UE 100 needs to be associated with the multicast session.
[0058] In the 5GC shared MBS service delivery method, the 5GC 20 receives a single copy of an MBS data packet and transmits the single copy of the MBS data packet to a RAN node (i.e., gNB 200). The gNB 200 receives the MBS data packet via an MBS tunnel connection and transmits the MBS data packet to one or more UEs 100.
[0059] From the perspective of RAN (5G RAN) 10, for radio transmission of MBS data in the 5GC shared MBS service transmission method, two transmission methods are possible: point-to-point (PTP) transmission method, and point-to-multipoint (PTM) transmission method. PTP means unicast, and PTM means multicast and broadcast.
[0060] In the PTP transmission method, the gNB 200 wirelessly transmits individual copies 100 of the MBS data packet to each UE. On the other hand, in the PTM transmission method, the gNB 200 wirelessly transmits a single copy of the MBS data packet to a group of UEs 100. The gNB 200 can dynamically determine whether to use the PTM transmission method or the PTP transmission method as a method for transmitting MBS data to one UE 100.
[0061] The PTP and PTM transmission methods are mainly related to the user plane. The mode for controlling MBS data transmission includes two transmission modes: a first transmission mode and a second transmission mode.
[0062] Figure 7 is a diagram showing a transmission mode according to an embodiment.
[0063] The first transmission mode (transmission mode 1 (DM1)) is a transmission mode that can be used by the UE 100 in the RRC connected state, and is a transmission mode for high QoS requirements. The first transmission mode is used for a multicast session among MBS sessions. Note that the first transmission mode can be used for a broadcast session. The first transmission mode can be available to the UE 100 in the RRC idle state or the RRC inactive state.
[0064] MBS reception configuration in the first transmission mode is performed through UE-specific signaling. For example, MBS reception configuration in the first transmission mode is performed through an RRC reconfiguration message (or an RRC release message), which is an RRC message unicast from gNB200 to UE 100.
[0065] The MBS reception configuration includes MBS service channel configuration information (hereinafter referred to as "MTCH configuration information") regarding the configuration of an MBS service channel for transmitting MBS data. The MTCH configuration information includes MBS session information related to an MBS session (including the MBS session identifier described below) and scheduling information of an MBS service channel corresponding to the MBS session. The scheduling information of the MBS service channel may include a discontinuous reception (DRX) configuration of the MBS service channel. The discontinuous reception configuration may include at least one parameter of: a timer value (on duration timer) for defining an on period (on duration: receiving period), a timer value (inactive timer) for extending the on period, a scheduling interval or a DRX cycle (scheduling period, DRX cycle), an offset value (starting offset, DRX cycle offset) for the starting subframe of the scheduling period or the DRX cycle, a starting delay time slot value (time slot offset) of the on period timer, a timer value (retransmission timer) for defining the maximum time before retransmission, and a timer value (HARQ RTT timer) for defining the minimum interval before DL assignment of HARQ retransmission.
[0066] Note that the MBS traffic channel is a kind of logical channel and may be referred to as an MTCH. The MBS traffic channel is mapped to a downlink shared channel (DL-SCH) which is a kind of transport channel.
[0067] The second transmission mode (transmission mode 2 (DM2)) is a transmission mode that can be used not only by the UE 100 in the RRC connected state but also by the UE 100 in the RRC idle state or the RRC inactive state, and is a transmission mode for low QoS requirements. The second transmission mode is used for a broadcast session among MBS sessions. However, the second transmission mode can also be applied to a multicast session.
[0068] MBS reception configuration in the second transmission mode is performed by broadcast signaling. For example, MBS reception configuration in the second transmission mode is performed using a logical channel (e.g., a broadcast control channel (BCCH) and / or a multicast control channel (MCCH)) sent from gNB200 to UE 100 by broadcast. For example, UE 100 may receive BCCH and MCCH using a dedicated RNTI predefined in the technical specification. The RNTI for BCCH reception may be an SI-RNTI, and the RNTI for MCCH reception may be an MCCH-RNTI.
[0069] In the second transmission mode, UE 100 can receive MBS data in the following three processes. First, UE 100 receives MCCH configuration information about SIB (MBS-SIB) sent from gNB 200 on BCCH. Second, UE 100 receives MCCH from gNB 200 based on MCCH configuration information. On MCCH, MTCH configuration information is sent. Third, UE 100 receives MTCH (MBS data) based on MTCH configuration information. Hereinafter, MTCH configuration information and / or MCCH configuration information may be referred to as MBS reception configuration.
[0070] In the first transmission mode and the second transmission mode, the UE 100 may receive the MTCH using a group RNTI (G-RNTI) assigned from the gNB 200. The G-RNTI corresponds to an RNTI for MTCH reception. The G-RNTI may be included in the MBS reception configuration (MTCH configuration information).
[0071] The network can provide different MBS services for different MBS sessions. The MBS session is identified by at least one item selected from the group consisting of a temporary mobile group identity (TMGI), a source-specific IP multicast address (which includes a source unicast IP address such as an application function and an application server and an IP multicast address indicating a destination address), a session identifier, and a G-RNTI. At least one item selected from the group consisting of a TMGI, a source-specific IP multicast address, and a session identifier is referred to as an MBS session identifier. The TMGI, the source-specific IP multicast address, the session identifier, and the G-RNTI are collectively referred to as MBS session information.
[0072] Figure 8 is a diagram showing an example of internal processing related to MBS reception of UE 100 according to an embodiment. Fig. 9 is a diagram showing another example of internal processing related to MBS reception of UE 100 according to an embodiment.
[0073] An MBS Radio Bearer (MRB) is a radio bearer that transmits a multicast session or a broadcast session. That is, a multicast session may be associated with an MRB, or a broadcast session may be associated with an MRB.
[0074] The MRB and corresponding logical channel (e.g., MTCH) of the UE 100 are configured from the gNB 200 through RRC signaling. The MRB configuration process can be separated from the data radio bearer (DRB) configuration process. In the RRC signaling, one MRB can be configured with "PTM only", "PTP only", or "both PTM and PTP". The type of MRB can be changed through RRC signaling.
[0075] Figure 8 An example is shown in which a multicast session and a dedicated traffic channel (DTCH) are associated with MRB#1, a multicast session and MTCH#1 are associated with MRB#2, and a broadcast session and MTCH#2 are associated with MRB#3. That is, MRB#1 is configured with a PTP-only MRB, MRB#2 is configured with a PTM-only MRB, and MRB#3 is configured with a PTM-only MRB. Note that the DTCH is scheduled using the cell RNTI (C-RNTI). The MTCH is scheduled using the G-RNTI.
[0076] The PHY layer of the UE 100 processes user data (received data) received on the PDSCH, which is one of the physical channels, and routes the processed user data to a downlink shared channel (DL-SCH), which is one of the transport channels. The MAC layer (MAC entity) of the UE 100 processes the data received on the DL-SCH, and routes the received data to a corresponding logical channel (corresponding RLC entity) based on a logical channel identifier (LCID) included in a header (MAC header) included in the received data.
[0077] Fig. 9 An example is shown in which DTCH and MTCH are associated with an MRB associated with a multicast session. Specifically, an MRB is split into two branches, one branch is associated with DTCH, and the other branch is associated with MTCH. The two branches are merged at the PDCP layer (PDCP entity). That is, the MRB is an MRB configured with both PTM and PTP. Such an MRB may be referred to as a split MRB.
[0078] Operation of mobile communication systems
[0079] The operation of the mobile communication system 1 according to the embodiment will be described. In the following, it is mainly assumed that multicast transmission is performed in the first transmission mode (DM1) described above. As described above, the first transmission mode is a transmission mode that can be used by the UE 100 in the RRC connected state, and is a transmission mode for high QoS requirements.
[0080] In an embodiment, it is assumed that the UE 100 in the RRC idle state or the RRC inactive state receives a multicast session (i.e., multicast reception). For example, after starting multicast transmission to the UE 100 in the RRC connected state, the gNB 200 continues the multicast transmission while causing the UE 100 to transition to the RRC idle state or the RRC inactive state in response to an increase in the load on the gNB 200. After starting multicast reception in the RRC connected state, the UE 100 continues the multicast reception in the RRC idle state or the RRC inactive state.
[0081] Since the first transmission mode (DM1) may be required to ensure high QoS requirements, the UE 100 in the RRC idle state or the RRC inactive state may also need to ensure high QoS requirements. Although the QoS will be satisfied if the UE 100 remains in the RRC connected state, a large amount of resources will be consumed on the network side, and a large amount of power will be consumed on the UE 100 side. Although this problem can be solved by making the UE 100 transition to the RRC idle state or the RRC inactive state, there is a possibility that the QoS is not satisfied. Therefore, in an embodiment, the UE 100 performing multicast reception in the RRC idle state or the RRC inactive state can transition to the RRC connected state in response to the deterioration of the reception quality of the multicast reception.
[0082] First, the UE 100 according to the embodiment receives a multicast session from the network (gNB 200) in the RRC idle state or the RRC inactive state. Second, the UE 100 measures the reception quality from the network in the multicast reception state in which the multicast session is being received (hereinafter, also referred to as "multicast reception quality"). Third, in response to the measured reception quality being lower than a threshold, the UE 100 performs a transition process of transitioning to the RRC connected state for multicast reception. Therefore, by transitioning to the RRC connected state and continuing the multicast reception, the QoS required for the multicast reception can be easily ensured.
[0083] When the multicast reception quality is higher than the threshold, the UE 100 does not transition to the RRC connected state for multicast reception. That is, when the multicast reception quality is higher than the threshold, the UE 100 is prohibited from transitioning to the RRC connected state for multicast reception. Therefore, the RRC idle state or the RRC inactive state can be maintained, so that the load on the network side can be reduced.
[0084] UE 100 may receive configuration information for configuring a threshold from the network (gNB 200). UE 100 may compare the measured reception quality with the threshold configured according to the configuration information. In this way, a threshold may be configured for UE 100 from the network (gNB 200), at which threshold the UE 100 starts a transition process to the RRC connected state. Therefore, UE 100 may be transitioned to the RRC connected state under the management of the network.
[0085] Fig.10 : is a diagram showing an operation example of the mobile communication system 1 according to the embodiment.
[0086] In step S101, UE 100 is in an RRC connected state in a cell of gNB 200. It is assumed that UE 100 is interested in a certain multicast session (hereinafter referred to as "target multicast session"). "Interested in a multicast session" means that the upper layer of UE 100 requests or wishes to receive the multicast session. The upper layer includes a NAS layer. The upper layer may also include an application. UE 100 (NAS entity) performs a multicast session joining procedure for joining the target multicast session on the network. For example, UE 100 has joined the target multicast session by sending a first NAS message requesting to join the target multicast session to AMF 300A and receiving a second NAS message from AMF 300A approving to join the target multicast session. For example, the first NAS message may be a PDU session modification request, and the message may include an MBS session identifier and information for joining the request. When the approval of the first NAS message is implicitly notified using the MRB configuration from gNB 200, the second NAS message may be omitted. "Joining the target multicast session" means registering the UE 100 into the CN device as a member of the UE group (multicast group) receiving the multicast session. The CN device may authenticate the UE 100 at the time of registration. The CN device may allow the UE 100 to receive the multicast session. Note that the multicast session may be joined when the multicast session is in an active state (sending the multicast session) or in an inactive state (waiting for transmission to start or when transmission is interrupted).
[0087] In step S102, the UE 100 in the RRC connected state starts receiving the target multicast session. Before the multicast reception, the gNB 200 may configure the UE 100 with a multicast reception configuration for the target multicast session reception. The multicast reception configuration may be performed by using, for example, an RRC reconfiguration message including an MRB configuration.
[0088] In step S103, the UE 100 in the RRC connected state receives the target multicast session. More specifically, the UE 100 receives the MBS data belonging to the target multicast session from the gNB 200.
[0089] Subsequently, in step S104, the gNB 200 determines to transition the UE 100 to the RRC idle state or the RRC inactive state, and sends an RRC release message to the UE 100 to transition the UE 100 to the RRC idle state or the RRC inactive state. The gNB 200 may transition the UE 100 to the RRC idle state or the RRC inactive state in response to an increase in a load (e.g., a resource load) on the gNB 200. By transitioning the UE 100 to the RRC idle state or the RRC inactive state, the load on the gNB 200 is reduced.
[0090] In an embodiment, the gNB 200 sends an RRC release message to the UE 100, which includes configuration information for configuring the above-mentioned threshold. The threshold may be a radio quality threshold, such as a threshold of reference signal received power (RSRP), a threshold of reference signal received quality (RSRQ), and / or a threshold of signal to interference plus noise ratio (SINR). The threshold may be a demodulation quality threshold, such as a threshold of bit error rate (BER), a threshold of block error rate (BLER), and / or a threshold of packet error rate (PER). The threshold may be configured for each multicast session. That is, the threshold may be configured in association with an MRB configuration (MRB ID) or a multicast session ID (TMGI). Therefore, when the UE 100 receives multiple multicast sessions, the UE 100 may maintain multiple thresholds associated with the multiple multicast sessions. The gNB 200 may send an RRC release message to the UE 100, which includes configuration information for configuring the duration (first predetermined time period) of the threshold condition. By including these configuration information in the RRC release message, UE-specific configuration information can be effectively sent to UE 100. Such configuration can be sent through RRC reconfiguration in step S102. When the configuration is included in the RRC reconfiguration, UE 100 can determine that the multicast session can be received (allowed to be received) in the RRC idle or inactive state.
[0091] In step S105, UE 100 having received the RRC release message transitions to the RRC idle state or the RRC inactive state. UE 100 continues multicast reception in the RRC idle state or the RRC inactive state by using the multicast reception configuration configured in the RRC connected state.
[0092] In step S107, the UE 100 receives the multicast reception quality associated with the threshold configured by the gNB 200. For example, the UE 100 may measure radio quality such as RSRP, RSRQ and / or SINR. The UE 100 may measure demodulation quality such as BER, BLER and / or PER.
[0093] In step S108, UE 100 compares the multicast reception quality measured in step S107 with the threshold configured by gNB 200. When the measured multicast reception quality is higher than the threshold (step S108: No), UE 100 returns the process to step S107. In this case, UE 100 performs multicast reception while maintaining the RRC idle state or the RRC inactive state.
[0094] On the other hand, when the measured multicast reception quality is lower than the threshold (step S108: Yes), in step S109, UE 100 starts the transition process to the RRC connected state, that is, the random access procedure for gNB 200.
[0095] Note that the case where the multicast reception quality is lower than the threshold may be the case where the radio quality (RSRP, RSRQ and / or SINR) is lower than the threshold. When the multicast reception quality is lower than the threshold, the error rate (BER, BLER and / or PER) corresponding to the demodulation quality may be higher than the threshold.
[0096] In step S108, the UE 100 may determine whether the state in which the multicast reception quality is lower than the threshold value has continued for a first predetermined period of time. The first predetermined period of time may be configured for the UE 100 according to the configuration information from the gNB 200. When the state in which the multicast reception quality is lower than the threshold value continues for the first predetermined period of time, the UE 100 may start a transition process to the RRC connected state, that is, a random access procedure for the gNB 200 (step S109). Therefore, the influence of the instantaneous deterioration of the multicast reception quality may be easily eliminated.
[0097] In step S109, the UE 100 performs a random access procedure. In the case of the RRC inactive state, the AS layer of the UE 100 may start the RRC recovery. On the other hand, in the case of the RRC idle state, the AS layer of the UE 100 may start the RRC establishment. The AS layer of the UE 100 may notify the NAS layer that the threshold condition has been met. The NAS layer may instruct the AS layer to transition to the RRC connected state based on the notification.
[0098] UE 100 transitions to the RRC connected state by performing the random access procedure in step S109. UE 100 that has transitioned to the RRC connected state continues multicast reception. Note that since gNB 200 can schedule UE 100 in the RRC connected state individually, the load on gNB 200 is higher when high quality services can be provided to UE 100.
[0099] Note that when a predetermined event other than multicast reception occurs during a period in which the UE 100 is in the RRC idle state or the RRC inactive state, the UE 100 may be allowed to transition to the RRC connected state regardless of the above circumstances. The predetermined event may be that paging from the network has been received, i.e., a mobile terminated (MT) service has occurred. The predetermined event may be that uplink transmission has become necessary, i.e., a mobile originated (MO) service has occurred.
[0100] The above embodiment has described an example in which the threshold is configured for the UE 100 from the gNB 200. However, the threshold may be configured in advance for the UE 100. The UE 100 may maintain the threshold pre-configured for each QoS level (5QI). The UE 100 may compare the threshold matched with the QoS level of the target multicast session and pre-configured with the multicast reception quality.
[0101] First Modification
[0102] like Fig.11 As shown, the gNB 200 may include the above configuration information in a system information block (SIB) for broadcasting (step S106). The UE 100 in the RRC idle state or the RRC inactive state may receive the SIB including the configuration information from the gNB 200, and apply the threshold (and the first predetermined time period) according to the received configuration information. The SIB may include separate configuration information for each bearer (MRB) (or each service) or for each QoS level (5QI). The SIB may include configuration information common to all bearers.
[0103] For example, the SIB may include a 5QI or multiple groups of bearer identifiers and configuration information associated with the bearer identifiers or 5QIs. The UE 100 having received the SIB may obtain configuration information matching the bearer or QoS level of the target multicast session from the SIB, and apply the threshold (and the first predetermined time period) according to the obtained configuration information.
[0104] Second Modification
[0105] like Fig.12As shown, before a predetermined time period (second predetermined time period) has passed after the transition to the RRC idle state or the RRC inactive state, the UE 100 may be prohibited from transitioning to the RRC connected state for multicast reception. Therefore, the UE 100 may be inhibited from transitioning to the RRC connected state immediately after the transition to the RRC idle state or the RRC inactive state. The second predetermined time period may be configured for the UE 100 from the gNB 200 according to the RRC release message or the SIB. The RRC release message or the SIB may include configuration information for configuring the second predetermined time period. Therefore, the gNB 200 may configure an appropriate second predetermined time period according to, for example, the load state of the gNB 200.
[0106] In step S201, the UE 100 that has transitioned to the RRC idle state or the RRC inactive state starts a timer to which a second predetermined period of time (timer value) has been set. That is, the UE 100 counts the elapsed period of time after transitioning to the RRC idle state or the RRC inactive state. The second predetermined period of time (timer value) can be configured from, for example, the gNB 200 and is specified as seconds, subframes, radio frames, or time.
[0107] Before the elapsed time period after the UE 100 transitions to the RRC idle state or the RRC inactive state exceeds the second predetermined time period, the UE 100 avoids performing a transition process (random access procedure) to transition to the RRC connected state for multicast reception. When a predetermined event other than multicast reception occurs, the UE 100 may be allowed to transition to the RRC connected state regardless of the above circumstances. The predetermined event may be that paging from the network has been received, that is, a mobile terminated (MT) service has occurred. The predetermined event may be that uplink transmission has become necessary, that is, a mobile originated (MO) service has occurred.
[0108] After determining that the reception quality is lower than the threshold value (step S108: Yes), in step S202, the UE 100 determines whether the timer started in step S201 has expired, that is, whether the elapsed period after transitioning to the RRC idle state or the RRC inactive state exceeds the second predetermined period of time. If the timer has not expired (step S202: No), the UE 100 returns the process to step S107. On the other hand, if the timer has expired (step S202: Yes), in step S109, the UE 100 starts a transition process to the RRC connected state, that is, a random access procedure for the gNB 200. In this way, in response to the elapsed period after transitioning to the RRC idle state or the RRC inactive state exceeding the second predetermined period of time and the measured reception quality (multicast reception quality) being lower than the threshold value, the UE 100 performs a transition process to the RRC connected state.
[0109] Other embodiments
[0110] The above operation flow can be implemented individually and independently, and can also be implemented by combining two or more of the operation flows. For example, some steps of one operation flow can be added to another operation flow, or some steps of one operation flow can be replaced by some steps of another operation flow.
[0111] In the above embodiments and examples, an example in which the base station is an NR base station (i.e., gNB) is described; however, the base station may be an LTE base station (i.e., eNB) or a 6G base station. The base station may be a relay node, such as an integrated access and backhaul (IAB) node. The base station may be a DU of an IAB node. UE 100 may be a mobile terminal (MT) of an IAB node.
[0112] A program that causes a computer to perform each process performed by UE 100 or gNB 200 may be provided. The program may be recorded in a computer-readable medium. The use of a computer-readable medium enables the program to be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. A circuit for performing a process to be performed by UE 100 or gNB 200 may be integrated, and at least a portion of UE 100 or gNB 200 may be implemented as a semiconductor integrated circuit (chip set, system on chip (SoC)).
[0113] Unless otherwise expressly stated, the phrases "based on" and "depending on" used in this disclosure do not mean "based only on" and "depending only on". The phrase "based on" means both "based only on" and "based at least in part on". Similarly, the phrase "depending on" means both "depending only on" and "depending at least in part on". "Obtaining" or "obtaining" can mean obtaining information from stored information, can mean obtaining information from information received from another node, or can mean obtaining information by generating information. The terms "including", "comprising" and their variants do not mean "including only the items", but mean "can only include the items" or "can include not only the items but also other items". The term "or" used in this disclosure is not intended to be an "exclusive or". In addition, any reference to elements using names such as "first" and "second" in this disclosure does not generally limit the number or order of these elements. These names can be used as a convenient method to distinguish two or more elements in this article. Therefore, the reference to the first element and the second element does not mean that only two elements can be adopted there or that the first element needs to be in some way before the second element. For example, when English articles such as "a", "an" and "the" are added in this disclosure by translation, these articles include plural unless the context clearly indicates otherwise.
[0114] The embodiments have been described in detail above with reference to the accompanying drawings, but the specific configuration is not limited to the above configuration, and various design changes may be made without departing from the gist of the present disclosure.
[0115] This application claims priority from Japanese Patent Application No. 2021-005614 (filed on January 18, 2022), the entire contents of which are incorporated herein by reference.
[0116] Reference numerals
[0117] 1: Mobile communication system
[0118] 10: RAN
[0119] 20: CN
[0120] 100: UE
[0121] 110: Receiver
[0122] 120: Transmitter
[0123] 130: Controller
[0124] 200: gNB
[0125] 210: Transmitter
[0126] 220: Receiver
[0127] 230: Controller
[0128] 240: Backhaul communicator.
Claims
1. A communication method performed by a user equipment in a mobile communication system for providing a multicast broadcast service MBS, the communication method comprising the following steps: In the RRC idle state or the RRC inactive state, receiving a multicast session from the network; In a multicast reception state in which the multicast session is being received, measuring a reception quality from the network; as well as In response to the measured reception quality being lower than a threshold, a transition process to an RRC connected state for multicast reception is performed.
2. The communication method according to claim 1, further comprising the following steps: Receiving configuration information for configuring the threshold from a base station included in the network; as well as The measured reception quality is compared with a threshold configured according to the configuration information.
3. The communication method according to claim 1 or 2, further comprising: In response to the measured reception quality being higher than the threshold, the multicast reception is performed while maintaining the RRC idle state or the RRC inactive state.
4. The communication method according to claim 1, wherein: The performing of the transition process includes performing the transition process in response to a state in which the measured reception quality is lower than the threshold value for a first predetermined period of time.
5. The communication method according to claim 4, further comprising: Configuration information configuring the first predetermined time period is received from a base station included in the network.
6. The communication method according to claim 1, further comprising the following steps: timing a period of time that elapses after transitioning to the RRC idle state or the RRC inactive state; as well as refraining from executing the transition process for performing the multicast reception until the elapsed period exceeds a second predetermined period of time, The performing of the transition process comprises: in response to the elapsed time period exceeding the second predetermined time period and the measured reception quality being lower than the threshold, performing the transition process.
7. The communication method according to claim 6, further comprising: Configuration information configuring the second predetermined time period is received from a base station included in the network.
8. The communication method according to claim 2, 5 or 7, wherein: Receiving the configuration information includes receiving an RRC release message including the configuration information from the base station.
9. The communication method according to claim 2, 5 or 7, wherein: Receiving the configuration information includes receiving a system information block including the configuration information from the base station.
10. A user equipment used in a mobile communication system for providing a multicast broadcast service MBS, the user equipment comprising: a receiver configured to receive a multicast session from a network in an RRC idle state or an RRC inactive state; as well as a controller configured to measure a reception quality from the network in a multicast reception state in which the multicast session is being received, The controller is configured to: in response to the measured reception quality being lower than a threshold, execute a transition process of transitioning to an RRC connected state for multicast reception.
