Communication control method

The communication control method in 5G mobile systems addresses MBS service delivery inefficiencies by configuring multiple MBS control channels with varying quality requirements and employing flexible scheduling, ensuring timely and optimized service delivery for diverse applications.

JP2024161557AActive Publication Date: 2024-11-19KYOCERA CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2024139474
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-07-30
Filing Date
2024-08-21
Publication Date
2024-11-19
Estimated Expiration
2041-07-26

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in providing efficient and delay-tolerant multicast/broadcast services (MBS) due to limitations in channel scheduling and resource allocation, which affect the quality of service requirements for different types of services.

Method used

The proposed communication control method involves configuring multiple MBS control channels within a cell, each associated with distinct service quality requirements, and utilizing flexible scheduling mechanisms such as on-demand transmission and unicast signaling to optimize service delivery based on user equipment needs.

Benefits of technology

This approach enables efficient and timely delivery of MBS services by aligning channel configurations with specific service categories, reducing delays and optimizing resource usage, thereby enhancing the overall quality of service for diverse applications like public safety, IoT, and IPTV.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161557000001_ABST
    Figure 2024161557000001_ABST
Patent Text Reader

Abstract

To provide a communication control method of a multi-cast and broadcast service (MBS) for supporting different service quality conditions, a network node, a chip set, a program, and a mobile communication system.SOLUTION: A communication control method is used for a mobile communication system for providing a multi-cast and broadcast service (MBS) to user equipment UE from a base station gNB, and contains steps of: transmitting a plurality of MBS control channels where the base station that manages a cell is associated with different service quality requests in the cell; and receiving each MBS control channel corresponding to the service quality requirement demanded by the user equipment from the plurality of MBS control channels in the user equipment.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a communication control method for use in a mobile communication system. [Background technology]

[0002] In recent years, the fifth generation (5G) mobile communication system has been attracting attention. NR (New Radio), the radio access technology (RAT) of the 5G system, has features such as high speed, large capacity, high reliability, and low latency compared to LTE (Long Term Evolution), the fourth generation radio access technology. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP technical specification "3GPP TS 38.300 V16.2.0 (2020-07)" Summary of the Invention

[0004] The communication control method of the first aspect is a communication control method used in a mobile communication system that provides a multicast broadcast service (MBS) from a base station to a user device, and includes the steps of: the base station managing a cell transmitting a plurality of MBS control channels in the cell, each of which corresponds to a different service quality requirement; and the user device receiving an MBS control channel among the plurality of MBS control channels that corresponds to the service quality requirement requested by the user device.

[0005] A communication control method according to a second aspect is a communication control method used in a mobile communication system in which a base station provides a multicast broadcast service (MBS) to a user device, the method comprising: the base station transmitting MBS system information via a broadcast control channel; the MBS system information including first MBS system information indicating scheduling of an MBS control channel that transmits MBS control information; and second MBS system information indicating scheduling of an MBS traffic channel that transmits MBS data.

[0006] A communication control method according to a third aspect is a communication control method used in a mobile communication system in which a base station provides a multicast broadcast service (MBS) to a user device, the method comprising: the user device transmitting a transmission request to a base station requesting transmission of MBS control information via an MBS control channel; and the base station transmitting the MBS control information via the MBS control channel in response to receiving the transmission request.

[0007] A communication control method according to a fourth aspect is a communication control method used in a mobile communication system in which a base station provides a multicast broadcast service (MBS) to a user device, the method comprising: the user device transmitting to the base station a unicast transmission request specifying at least one of MBS system information to be transmitted via a broadcast control channel and MBS control information to be transmitted via an MBS control channel; and the base station, in response to receiving the unicast transmission request, transmitting by unicast to the user device the information specified in the unicast transmission request.

[0008] A communication control method according to a fifth aspect is a communication control method used in a mobile communication system in which a base station provides a multicast broadcast service (MBS) to a user device, and includes the step of, when the base station starts providing an MBS session, sending a session start notification to the user device, the session start notification including an MBS service identifier corresponding to the MBS session.

[0009] A communication control method according to a sixth aspect is a communication control method used in a mobile communication system in which a base station provides a multicast broadcast service (MBS) to a user device, the base station managing a cell transmitting to the user device an MBS service identifier corresponding to an MBS session and bandwidth portion information associated with the MBS service identifier, the bandwidth portion information being information indicating a first bandwidth portion used to provide the MBS session in the cell. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. [Diagram 2] 1 is a diagram illustrating a configuration of a UE 100 (user equipment) according to an embodiment. [Diagram 3] A diagram showing the configuration of a gNB200 (base station) according to an embodiment. [Figure 4] A diagram showing the configuration of a protocol stack of a wireless interface of a user plane that handles data. [Diagram 5] FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals). [Figure 6] FIG. 2 is a diagram illustrating a correspondence relationship between downlink logical channels and transport channels according to an embodiment. [Figure 7] FIG. 2 is a diagram illustrating a communication control method according to the first embodiment. [Figure 8] FIG. 4 is a diagram illustrating an example of an operation according to the first embodiment. [Figure 9] FIG. 11 is a diagram showing a correspondence relationship of channels according to the second embodiment. [Figure 10] FIG. 11 is a diagram illustrating an example of an operation according to the second embodiment. [Figure 11] FIG. 13 is a diagram illustrating an example of an operation according to the third embodiment. [Figure 12]FIG. 13 is a diagram illustrating an example of an operation according to the fourth embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of an operation according to the fifth embodiment. [Figure 14] FIG. 1 is a diagram showing an example of a BWP. [Figure 15] FIG. 23 is a diagram illustrating an example of an operation according to the sixth embodiment. [Figure 16] FIG. 1 is a diagram showing two-stage configuration in LTE SC-PTM. [Figure 17] A diagram showing functional enhancements for NR MBS. [Figure 18] A diagram showing the U-plane architecture of LTE MBMS. [Figure 19] FIG. 1 illustrates an enhancement to reliable reception and multicast / unicast switching. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The introduction of multicast and broadcast services to the 5G system (NR) is being considered. It is hoped that the NR multicast and broadcast services will provide improved services compared to the LTE multicast and broadcast services.

[0012] Therefore, an object of the present disclosure is to realize an improved multicast / broadcast service.

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

[0014] (Configuration of a mobile communication system) First, a configuration of a mobile communication system according to an embodiment will be described. Fig. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. This mobile communication system complies with the 3GPP standard 5th Generation System (5GS). In the following, 5GS will be described as an example, but the LTE (Long Term Evolution) system may be applied at least in part to the mobile communication system.

[0015] As shown in FIG. 1, the mobile communication system includes a user equipment (UE) 100, a 5G radio access network (NG-RAN) 10, and a 5G core network (5GC) 20.

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

[0017] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with 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, and the like. 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 performing wireless communication with the UE 100. One cell belongs to one carrier frequency.

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

[0019] The 5GC20 includes an Access and Mobility Management Function (AMF) and a User Plane Function (UPF) 300. The AMF performs various mobility controls for the UE 100. The AMF manages the mobility of the UE 100 by communicating with the UE 100 using Non-Access Stratum (NAS) 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.

[0020] FIG. 2 is a diagram showing a configuration of a UE 100 (user equipment) according to the embodiment.

[0021] As shown in FIG. 2, the UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit .

[0022] The receiving unit 110 performs various receptions 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.

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

[0024] The control unit 130 performs various controls in the UE 100. 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 processing.

[0025] FIG. 3 is a diagram showing the configuration of a gNB200 (base station) according to an embodiment.

[0026] As shown in FIG. 3, the gNB 200 includes a transmitter 210, a receiver 220, a control unit 230, and a backhaul communication unit 240.

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

[0028] The receiving unit 220 performs various receptions 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.

[0029] The control unit 230 performs various controls in the gNB 200. 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 processing.

[0030] The backhaul communication unit 240 is connected to adjacent base stations via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF / UPF 300 via a base station-core network interface. Note that the gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (i.e., the functions are divided), and both units may be connected to each other via an F1 interface.

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

[0032] As shown in FIG. 4, 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.

[0033] 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 the UE 100 and the PHY layer of the gNB 200 via a physical channel.

[0034] The MAC layer performs data priority control, retransmission processing using hybrid ARQ (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 assigned to the UE 100.

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

[0036] The PDCP layer performs header compression / decompression and encryption / decryption.

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

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

[0039] As shown in FIG. 5, the protocol stack of the radio interface of the control plane has a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer instead of the SDAP layer shown in FIG.

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

[0041] The NAS layer, which is located above the RRC layer, performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300.

[0042] In addition, the UE 100 has an application layer and the like in addition to the protocol of the radio interface.

[0043] (MBS) Next, the MBS according to the embodiment will be described. The MBS is a service for broadcasting or multicasting, that is, transmitting data from the NG-RAN 10 to the UE 100 in a one-to-many (PTM: Point To Multipoint) manner. The MBS may be called an MBMS (Multimedia Broadcast and Multicast Service). Note that use cases (service types) of the MBS include public safety communication, mission critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV, group communication, and software distribution.

[0044] There are two types of MBS transmission methods in LTE: MBSFN (Multicast Broadcast Single Frequency Network) transmission and SC-PTM (Single Cell Point To Multipoint) transmission. Fig. 6 is a diagram showing a correspondence relationship between downlink logical channels and transport channels according to the embodiment.

[0045] As shown in Figure 6, the logical channels used for MBSFN transmission are MTCH (Multicast Traffic Channel) and MCCH (Multicast Control Channel), and the transport channel used for MBSFN transmission is MCH (Multicast Control Channel). MBSFN transmission is designed mainly for multi-cell transmission, and in an MBSFN area consisting of multiple cells, each cell synchronously transmits the same signal (same data) in the same MBSFN subframe.

[0046] The logical channels used for SC-PTM transmission are the Single Cell Multicast Traffic Channel (SC-MTCH) and the Single Cell Multicast Control Channel (SC-MCCH), and the transport channel used for SC-PTM transmission is the Downlink Shared Channel (DL-SCH). SC-PTM transmission is designed primarily for single-cell transmission, and transmits data by broadcast or multicast on a cell-by-cell basis. The physical channels used for SC-PTM transmission are the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH), which enable dynamic resource allocation.

[0047] In the following, an example in which an MBS is provided using the SC-PTM transmission method will be mainly described, but an MBS may also be provided using the MBSFN transmission method. Also, an example in which an MBS is provided by multicast will be mainly described. Therefore, MBS may be read as multicast. However, an MBS may also be provided by broadcast.

[0048] In the following, MBS data refers to data transmitted by the MBS, the MBS control channel refers to the MCCH or SC-MCCH, and the MBS traffic channel refers to the MTCH or SC-MTCH.

[0049] The network can provide different MBS services for each MBS session. An MBS session (MBS service) is identified by at least one of a Temporary Mobile Group Identity (TMGI) and a session identifier, and at least one of these identifiers is called an MBS service identifier. Such an MBS service identifier may be called an MBS session identifier or a multicast group identifier.

[0050] (First embodiment) Next, a communication control method according to the first embodiment will be described on the premise of the above-mentioned mobile communication system and MBS.

[0051] FIG. 7 is a diagram showing a communication control method according to the first embodiment.

[0052] As shown in Fig. 7, the communication control method according to the first embodiment is a method used in a mobile communication system that provides a multicast broadcast service (MBS) from a gNB 200 to a UE 100. The communication control method according to the first embodiment includes a step in which the gNB 200 that manages a cell C1 transmits, in the cell C1, a plurality of MBS control channels each associated with a different service quality requirement, and a step in which the UE 100 receives, from among the plurality of MBS control channels, an MBS control channel that corresponds to the service quality requirement requested by the UE 100.

[0053] In this manner, in the first embodiment, a plurality of MBS control channels are configured in one cell C1, and each MBS control channel is associated with a different service quality requirement (or service category). This makes it possible to configure an MBS control channel optimized according to the service quality requirement.

[0054] In the first embodiment, the multiple MBS control channels may include a first MBS control channel for a predetermined MBS service and a second MBS control channel for an MBS service that requires lower delay than the predetermined MBS service. In other words, the multiple MBS control channels are classified into an MBS control channel for a delay-sensitive service (a second MBS control channel) and an MBS control channel for other services (a first MBS control channel).

[0055] This enables a setting such that the time interval at which the gNB 200 transmits the second MBS control channel is shorter than the time interval at which the gNB 200 transmits the first MBS control channel, making it easier for the UE 100 to quickly receive the delay-sensitive service. Note that the UE 100 may receive the second MBS control channel if it wishes to receive the delay-sensitive service, and may not need to receive the second MBS control channel if it does not wish to receive the delay-sensitive service.

[0056] In the first embodiment, the multiple MBS control channels may be associated with different network slices. A network slice refers to a logical network obtained by virtually dividing a network. Each network slice can provide services with different service quality requirements. Each network slice is identified by a network slice identifier, for example, NSSAI (Network Slice Selection Assist Information). In this way, by associating each MBS control channel with a network slice, it becomes possible to configure an MBS control channel optimized for each network slice.

[0057] In the first embodiment, each of the multiple MBS control channels may transmit MBS control information including a network slice identifier that identifies a corresponding network slice. This makes it easier for the UE 100 to know which MBS control channel corresponds to which network slice.

[0058] In the first embodiment, the gNB 200 or the UE 100 may receive a network slice identifier associated with the MBS service identifier from a network node. The network node refers to a node consisting of one or more devices provided in a core network (5GC 20) or a higher-level network.

[0059] Fig. 8 is a diagram showing an example of the operation according to the first embodiment. The procedure of the operation shown in Fig. 8 can also be applied to each embodiment described later.

[0060] 8, in step S101, the network node 500 transmits user service information (USD: User Service Description) to the UE 100. The UE 100 receives the user service information.

[0061] The user service information is information of the application layer (service layer). The user service information includes, for each MBS service, at least one of an MBS service identifier (e.g., TMGI), a start time and an end time of an MBS session, a frequency, and an MBMS service area identifier. In the first embodiment, the user service information may include a network slice identifier for each MBS service. Based on the user service information, the UE 100 may request, from the network node 500, an access right to a network slice indicated by a network slice identifier corresponding to an MBS service that the UE 100 wishes to receive.

[0062] In step S102, the network node 500 transmits a notification including at least one set of an MBS service identifier and a network slice identifier to the gNB 200. The gNB 200 receives the notification. This notification may be a notification indicating that the provision of an MBS service (MBS session) indicated by the MBS service identifier is started.

[0063] In step S103, the gNB 200 transmits the MBS system information to the UE 100 via a broadcast control channel (BCCH). The MBS system information is transmitted by broadcast using a predetermined RNTI (Radio Network Temporary Identifier). The UE 100 receives the MBS system information. Note that the system information may be referred to as a SIB (System Information Block).

[0064] The MBS system information includes scheduling information required for receiving the MBS control channel. For example, the MBS system information includes at least one of information indicating a period during which the content of the MBS control channel (MBS control information) may be changed, information indicating a time interval for transmitting the MBS control channel in terms of the number of radio frames, information indicating an offset of a radio frame in which the MBS control channel is scheduled, and information indicating a subframe in which the MBS control channel is scheduled.

[0065] In the first embodiment, the MBS system information includes scheduling information for each of a plurality of MBS control channels used in the cell C1 of the gNB 200. For example, a scheduling setting is made such that the time interval for transmitting the second MBS control channel is shorter than the time interval for transmitting the first MBS control channel.

[0066] In the first embodiment, the MBS system information may include identifiers (names) of each of the multiple MBS control channels. Such MBS control channel identifiers may include a predetermined tag. For example, the second MBS control channel may be expressed as "SC-MCCH-delay-sensitive-services" and the second MBS control channel may be expressed as "SC-MCCH-other-services". Alternatively, abstracted MBS control channel identifiers such as "SC-MCCH-A" and "SC-MCCH-B" may be used. In this case, information on which MBS control channel is for low delay may be included in the MBS system information.

[0067] In the first embodiment, the MBS system information may include a network slice identifier for each MBS control channel. The MBS system information may include a set of a network slice identifier and an MBS service identifier for each MBS control channel. The MBS system information may include MBS control channel information (such as scheduling information) and / or an MBS service identifier for each network slice identifier. Alternatively, the MBS system information may include MBS control channel information and / or a network slice identifier for each MBS service identifier. The MBS control channel information, the MBS service identifier, and / or the network slice identifier may be linked to each other in each entry of the configuration list.

[0068] In step S104, the gNB 200 transmits multiple MBS control channels (multiple MBS control information) by scheduling according to the MBS system information transmitted in step S103. The MBS control information is transmitted by broadcast (or multicast) using a predetermined RNTI. The RNTI may be different for each MBS control channel.

[0069] Each MBS control channel includes a list of scheduling information of MBS traffic channels of each MBS service belonging to the corresponding service category. For example, the scheduling information of an MBS traffic channel includes an MBS service identifier (e.g., TMGI) and a group RNTI corresponding to the MBS traffic channel, and DRX (Discontinuous Reception) information (or scheduling information) for the MBS traffic channel. The group RNTI has a one-to-one mapping with the MBS service identifier.

[0070] Based on the MBS system information received in step S103, UE100 receives only an MBS control channel corresponding to the service quality requirement (service category) requested by itself among the multiple MBS control channels. For example, if UE100 is not interested in a low-latency service, UE100 does not receive an MBS control channel for low latency. This realizes standby with low power consumption. UE100 may receive only an MBS control channel corresponding to a network slice that UE100 can access (i.e., a network slice to which UE100 has access rights or is registered) or a network slice in which UE100 is interested. Based on the MBS system information received in step S103, UE100 may receive only an MBS control channel corresponding to a service quality requirement (service category) to which an identifier (e.g., TMGI) of an MBS service in which UE100 is interested belongs.

[0071] In step S105, the network node 500 transmits the MBS data to the gNB 200. The gNB 200 receives the MBS data.

[0072] In step S106, the gNB 200 transmits the MBS data received from the network node 500 via the MBS traffic channel. The MBS data is transmitted by multicast (or broadcast) using the group RNTI. The UE 100 receives only the MBS data corresponding to the service quality requirement (service category) requested by the UE 100 based on the MBS control information received in step S104. For example, if the UE 100 is not interested in a low-latency service, the UE 100 does not receive the MBS data of the low-latency service. The UE 100 may receive only the MBS data corresponding to a network slice that the UE 100 can access (i.e., a network slice to which the UE 100 has access rights or has been registered) or a network slice of the UE 100's interest. The UE 100 may receive only the MBS data corresponding to the service quality requirement (service category) to which the identifier (e.g., TMGI) of the MBS service of the UE 100's interest belongs.

[0073] Second embodiment Next, a second embodiment will be described, focusing mainly on the differences from the above-mentioned embodiment.

[0074] In the above embodiment, the UE 100 receives the MBS control channel to receive the MBS traffic channel, and receives the broadcast control channel to receive the MBS control channel. Since such a three-stage reception process is required, there is room for improvement for MBS services that do not allow access delay.

[0075] The MBS control channel can be updated more frequently than the broadcast control channel, so while the MBS control channel can allow for frequent updates of the MBS traffic channel, the MBS traffic channel may not require frequent updates.

[0076] Therefore, in the second embodiment, the scheduling information of the MBS traffic channel can be transmitted in the broadcast control channel (MBS system information).

[0077] The communication control method according to the second embodiment includes a step in which the gNB 200 transmits MBS system information via a broadcast control channel. The MBS system information includes first MBS system information indicating the scheduling of an MBS control channel that transmits the MBS control information, and second MBS system information indicating the scheduling of an MBS traffic channel that transmits the MBS data. Hereinafter, the first MBS system information may be referred to as SIBy, and the second MBS system information may be referred to as SIBx.

[0078] In this way, by transmitting not only SIBy indicating the scheduling of the MBS control channel but also SIBx indicating the scheduling of the MBS traffic channel, it becomes easier to suppress the occurrence of delays.

[0079] In the second embodiment, the UE 100 may transmit a transmission request for requesting transmission of MBS system information to the gNB 200. The transmission request includes information for identifying the MBS system information requested by the UE 100 among SIBy and SIBx. This allows the UE 100 to quickly obtain the MBS system information required by itself from the gNB 200.

[0080] Fig. 9 is a diagram showing the correspondence relationship of channels according to the second embodiment. Each channel shown in Fig. 9 is provided in one cell. Here, an example in which the second embodiment is used in combination with the first embodiment is shown, but the second embodiment does not necessarily have to be used in combination with the first embodiment.

[0081] 9 represents one channel, the description of "PDCCH" in each block means that the radio resource (PDSCH) of the channel in the physical layer is allocated by the PDCCH. That is, it is assumed that the broadcast control channel, the MBS control channel, and the MBS traffic channel are all mapped to the DL-SCH.

[0082] As shown in Fig. 9, the MBS system information transmitted on the broadcast control channel includes SIBy indicating the scheduling of the MBS control channel and SIBx indicating the scheduling of the MBS traffic channel. Note that the MBS system information may be transmitted at a period scheduled by a predetermined type of SIB (e.g., SIB type 1) or may be transmitted in response to a request from the UE 100 (i.e., on-demand).

[0083] The SIBx can directly point to the MBS traffic channel (MTCH#4) without going through the MBS control channel (i.e., direct pointing). The MTCH#4 is, for example, an MBS traffic channel that transmits MBS data for delay tolerant service.

[0084] SIBy indicates each of multiple MBS control channels ((SC-)MCCH#1 and (SC-)MCCH#2). As described in the first embodiment, different scheduling can be applied to each MBS control channel. Note that the MBS control channel may be transmitted at a period indicated by SIBy, or in response to a request from UE 100 (i.e., on-demand). The latter case will be described in the third embodiment.

[0085] In FIG. 9, an example is shown in which (SC-)MCCH#1 indicates one MBS traffic channel (MTCH#1) and (SC-)MCCH#2 indicates two MBS traffic channels (MTCH#2 and MTCH#3). MTCH#1 is an MBS traffic channel that transmits MBS data (Data for delay sensitive service) for a delay sensitive MBS service. MTCH#2 and MTCH#3 are MBS traffic channels that transmit MBS data (Data for typical service) for a general MBS service.

[0086] Fig. 10 is a diagram showing an example of the operation according to the second embodiment. In Fig. 10, non-essential steps are indicated by dashed lines.

[0087] 10, in step S201, the gNB 200 transmits system information (hereinafter referred to as SIBz) including mapping information of the MBS service identifiers mapped to SIBx and SIBy, respectively, via a broadcast control channel. That is, the mapping information indicates which SIB contains information for receiving the MBS control channel, and which SIB contains information for receiving the MBS traffic channel.

[0088] When the UE 100 receives the SIBz, the UE 100 identifies an SIB linked to an MBS service identifier of an MBS service that the UE 100 wishes to receive, based on the SIBz. In step S202, the UE 100 transmits a transmission request to the gNB 200 in a manner that allows the identified SIB (SIBx or SIBy) to be identified. For example, the UE 100 transmits an RRC message including an identifier of the identified SIB (SIBx or SIBy) to the gNB 200 as a transmission request. Alternatively, the UE 100 transmits a random access preamble to the gNB 200 as a transmission request, using a PRACH resource associated with the identified SIB (SIBx or SIBy).

[0089] In step S203, the gNB 200 transmits, via a broadcast control channel, the SIB (SIBx or SIBy) identified by the transmission request from the UE 100. Alternatively, the gNB 200 may transmit the SIBx or SIBy to the UE 100 by unicast instead of transmitting the SIBx or SIBy by broadcast. Such unicast transmission will be described in the fourth embodiment.

[0090] As mentioned above, the SIBx is for directly receiving the MBS traffic channel and includes, for example, at least one of the following information elements for each MBS service identifier: Scheduling information of MBS traffic channel: On duration timer, DRX inactivity timer, Scheduling period (transmission period), Start offset (transmission SFN offset value), Num repetition (number of repeated transmissions), BWP (transmission BWP information). Details of BWP (Bandwidth Part) will be described in the sixth embodiment, but the transmission BWP information includes at least one of Starting PRB and bandwidth (BWP setting), SCS (sub-carrier spacing setting), and CP length (cyclic prefix length setting). ·Group RNTI PDCCH setting PDSCH settings Neighboring cell information (frequency, cell ID)

[0091] On the other hand, SIBy is for receiving an MBS control channel and includes, for example, at least one of the following information elements for each MBS service identifier. MBS control channel scheduling information: Repetition period (repetition transmission period), Offset (offset value of SFN for scheduling), First subframe (scheduling start subframe), Duration (scheduling period from the first subframe), Modification period (modification period), On duration timer, DRX inactivity timer, Scheduling period (transmission period), Start offset (transmission SFN offset value), Num repetition (number of repeated transmissions), BWP (transmission BWP information). Details of the BWP will be described in the fifth embodiment, but the transmission BWP information includes at least one of Starting PRB and bandwidth (BWP setting), SCS (sub-carrier spacing setting), and CP length (cyclic prefix length setting). SC-RNTI (RNTI assigned to the MBS control channel. Assumes that it can have multiple values) SC-N-RNTI (RNTI assigned to change notification of MBS control channel. Assumes that it can have multiple values) PDCCH setting PDSCH settings Neighboring cell information (frequency, cell ID)

[0092] In step S203, the UE 100 receives an SIB including control information related to an MBS service identifier that the UE 100 wishes to receive, and receives an MBS traffic channel or an MBS control channel based on the received SIB.

[0093] In the second embodiment, on-demand transmission may also be applied to SIBz. Furthermore, gNB200 may always periodically broadcast one of SIBx and SIBy, and broadcast the other on-demand. SIBz may be pointed to by the SIB (e.g., SIBx) that is always periodically broadcast. The SIB (e.g., SIBx) that is always periodically broadcast may include mapping information in SIBz. If SIBy exists, SIBx and SIBy may be transmitted as the same system information. In this case, the transmission request of S202 is transmitted based on the mapping information by SIBz and the interest of the UE itself (e.g., including the TMGI that the UE wishes to receive). In S203, a SIB including MBS system information and / or MBS control information corresponding to a multicast service in which the UE is interested is provided.

[0094] Third embodiment Next, a third embodiment will be described, focusing mainly on the differences from the above-mentioned embodiments.

[0095] Although transmission opportunities are determined for the MBS control channel, if the MBS control channel is transmitted at every transmission opportunity, radio resources may be wasted. For example, there may be a case where no UE 100 desires to receive the MBS control channel.

[0096] Therefore, in the third embodiment, on-demand transmission can also be applied to the MBS control channel. The communication control method according to the third embodiment includes a step in which the UE 100 transmits a transmission request to the gNB 200 to request transmission of MBS control information via the MBS control channel, and a step in which the gNB 200 transmits (broadcasts) the MBS control information via the MBS control channel in response to receiving the transmission request.

[0097] FIG. 11 is a diagram illustrating an example of the operation according to the third embodiment.

[0098] As shown in Fig. 11, in step S301, the gNB 200 transmits MBS system information to the UE 100 via a broadcast control channel. The UE 100 receives the MBS system information. Here, in the case of on-demand, the UE 100 requests and then receives the MBS system information.

[0099] In the third embodiment, the MBS system information includes at least one of the following information elements:

[0100] (A) One MBS control channel: - MBS service identifier during multicast (MBS traffic channel transmission) or network slice identifier corresponding to the MBS service identifier Information indicating whether the MBS control channel is always broadcast periodically or is currently not broadcast (on-demand type) Scheduling information for MBS control channel, BWP information (transmission BWP information mentioned above), etc.

[0101] (B) Multiple MBS control channels: - MBS service identifier during multicast (MBS traffic channel transmission) or network slice identifier corresponding to the MBS service identifier Information indicating whether the MBS control channel is always broadcast periodically or is currently not broadcast (on-demand type) for each MBS service identifier For each MBS service identifier, MBS control channel scheduling information, BWP information (the above-mentioned transmission BWP information), SC-RNTI information, etc. Alternatively, for each MBS control channel identifier, an MBS service identifier, MBS control channel scheduling information, BWP information, and SC-RNTI information may be provided. (See Table 1) Alternatively, for each network slice identifier, an MBS service identifier, an MBS control channel identifier, MBS control channel scheduling information, BWP information, and SC-RNTI information may be provided. Note that SC-RNTI refers to the RNTI for the MBS control channel, but may be named otherwise.

[0102] [Table 1]

[0103] In step S302, the UE 100 transmits a broadcast request (transmission request) for the MBS control channel to the gNB 200 based on the MBS system information received in step S301. The broadcast request includes an MBS service identifier or an identifier of the MBS control channel when multiple MBS control channels are provided in the cell. The broadcast request may include identification information indicating whether or not early information is desired (whether or not a delay is acceptable).

[0104] The broadcast request may be an RRC message including these pieces of information. This RRC message may be an MBS Interest Indication message as specified in LTE. If the UE 100 is in an RRC idle state or an RRC connected state before the broadcast request, the UE 100 may complete the random access procedure and transition to the RRC connected state before transmitting the broadcast request (RRC message). The UE 100 may notify that the communication is for making a broadcast request in a transition request to the RRC connected state (RRC Setup Request or RRC Resume Request). The notification may be notified as a cause, which is one of the information elements in the transition request message.

[0105] The broadcast request may be a random access preamble transmitted using a PRACH resource for broadcast requests. If multiple MBS control channels are provided, they may be identified by dividing the PRACH resource by MBS service identifier.

[0106] In step S303, the gNB 200 broadcasts the MBS control channel at the transmission opportunity of the MBS control channel based on the broadcast request (transmission request) received from the UE 100 in step S302. The UE 100 receives the MBS control channel (MBS control information) and receives the MBS traffic channel that the UE 100 wants to receive based on this information. Note that an example of transmitting the MBS control channel (MBS control information) by unicast, i.e., UE-specific signaling (RRC message), will be described in the fourth embodiment.

[0107] (Fourth embodiment) Next, a fourth embodiment will be described, focusing mainly on the differences from the above-mentioned embodiments. The fourth embodiment may be used in combination with at least a part of the operation of the third embodiment.

[0108] The on-demand transmission described above may cause an unacceptable delay because it is necessary to wait for an opportunity to transmit MBS system information or an MBS control channel after receiving a transmission request from the UE 100. In particular, in the case of a delay-sensitive MBS service, there is a risk that the delay requirement cannot be met.

[0109] Therefore, in the fourth embodiment, on-demand MBS system information or an on-demand MBS control channel can be transmitted by unicast (UE-specific signaling). This eliminates the need to wait for a predetermined transmission opportunity, and can suppress delays.

[0110] Specifically, the communication control method of the fourth embodiment includes a step in which UE100 transmits a unicast transmission request to gNB200, specifying at least one of MBS system information transmitted via a broadcast control channel and MBS control information transmitted via an MBS control channel, and a step in which gNB200 transmits, in response to receiving the unicast transmission request, information specified in the unicast transmission request by unicast to UE100.

[0111] In the fourth embodiment, one cell may include multiple MBS control channels. The gNB 200 may transmit information for identifying an MBS control channel that can be specified in a unicast transmission request via a broadcast control channel. For example, the gNB 200 broadcasts an MBS service identifier or an MBS control channel identifier corresponding to a broadcast control channel provided on demand (i.e., a broadcast control channel whose broadcast has been stopped). This allows the UE 100 to appropriately determine the broadcast control channel that is the target of the unicast transmission request.

[0112] In the fourth embodiment, the UE 100 may transmit a unicast transmission request to the gNB 200 after transitioning from an RRC idle state or an RRC inactive state to an RRC connected state.

[0113] In the fourth embodiment, one cell may include multiple MBS control channels. The UE 100 may transmit a unicast transmission request specifying at least one MBS control channel to the gNB 200. Alternatively, the UE 100 may transmit a unicast transmission request specifying at least one MBS data (at least one MBS traffic channel) to the gNB 200. Here, "specify" refers to, for example, including an MBS service identifier (or an MBS control channel identifier) ​​in which the UE 100 is interested in the unicast transmission request. Alternatively, the UE 100 may transmit a random access preamble as a unicast transmission request using a PRACH resource associated with the MBS service identifier or MBS control channel identifier in which the UE 100 is interested. The gNB 200 transmits, by unicast, the MBS control information of the MBS control channel specified in such a unicast transmission request.

[0114] Fig. 12 is a diagram showing an example of the operation according to the fourth embodiment. In Fig. 12, non-essential steps are indicated by dashed lines.

[0115] 12, in step S401, when the gNB 200 supports multiple MBS control channels in one cell, the gNB 200 broadcasts on-demand provision information including an MBS service identifier and / or an MBS control channel identifier corresponding to an MBS control channel that provides on-demand (an MBS control channel that is not broadcast). This broadcast is performed by the broadcast control channel or the MBS control channel.

[0116] In step S402, the UE 100 transmits a unicast transmission request to the gNB 200. The UE 100 may transmit the unicast transmission request to the gNB 200 based on the on-demand provision information received in step S401. Specifically, the UE 100 may transmit the unicast transmission request to the gNB 200 for only the MBS control channel or only the MBS traffic channel (MBS data) provided on-demand.

[0117] For example, the UE 100 requests the provision of an MBS control channel (MBS control information). When multiple MBS control channels exist in one cell, the UE 100 may notify the gNB 200 of an MBS service identifier (or an MBS control channel identifier) ​​in which the UE 100 is interested.

[0118] The UE 100 may transmit, to the gNB 200, information indicating whether it wishes to be provided with MBS system information, or to be provided with an MBS control channel, or to be provided with both. The UE 100 may also transmit, to the gNB 200, information indicating whether it wishes to request on-demand transmission by broadcast or on-demand transmission by unicast. Furthermore, the UE 100 may notify the gNB 200 that it is accessing a delay-sensitive MBS service.

[0119] Step S402 may be performed by the UE 100 in the RRC connected state. The UE 100 may transmit the unicast transmission request to the gNB 200 by MBS Interest Indication or UE 100 Assistance Information, which are types of RRC messages. Alternatively, the UE 100 may transmit the unicast transmission request to the gNB 200 by Msg3 or Msg5 in the random access procedure.

[0120] Step S402 may be performed by the UE 100 in the RRC idle state. As described in the above third embodiment, the UE 100 may transmit a unicast transmission request to the gNB 200 using a dedicated PRACH resource. In this case, a different PRACH resource may be allocated for each classification of requests, such as an MBS service identifier (or an MBS control channel identifier), or an identification of a SIB and an MBS control channel. Such a dedicated PRACH resource may be broadcast in the SIB, or may be notified to the UE 100 by UE-specific signaling.

[0121] In step S403, the gNB200 transmits MBS system information and / or an MBS control channel (MBS control information) to the UE100 by UE-specific signaling (e.g., an RRC message) based on the unicast transmission request received in step S402. Note that the gNB200 may transmit only a part of the MBS control information. For example, when one (or multiple) MBS control channels have control information (such as scheduling information) for multiple MBS data, the gNB200 transmits only the control information of the MBS data corresponding to the TMGI based on the request from the UE received in step S402 (the TMGI of interest of the UE).

[0122] Here, gNB200 may pass to UE100 only the scheduling information of the MBS traffic channel corresponding to the MBS service identifier requested by UE100 among the MBS system information and / or MBS control channel (MBS control information).

[0123] The gNB200 may use UE-specific signaling only for delay-sensitive services and use broadcasting otherwise.

[0124] In addition, instead of step S403, gNB200 may hand over UE100 to an appropriate cell.

[0125] Fifth embodiment Next, the fifth embodiment will be described, focusing mainly on the differences from the above-mentioned embodiments.

[0126] The UE 100 must check the MBS control channel, which is transmitted frequently, every time to know whether the provision of the MBS service (MBS session) that the UE 100 wishes to receive has started. If the MBS traffic channel resource has not yet been assigned (i.e., MBS transmission has not yet started), the UE 100 will consume power unnecessarily.

[0127] Therefore, in the fifth embodiment, it is possible to notify the UE 100 of the MBS service for which MBS transmission has started. This eliminates the need for the UE 100 to check the MBS control channel that is transmitted frequently every time, and therefore the power consumption of the UE 100 can be reduced.

[0128] The communication control method according to the fifth embodiment includes a step in which, when gNB200 starts providing an MBS session, gNB200 transmits a session start notification including an MBS service identifier corresponding to the MBS session to UE100.

[0129] The communication control method according to the fifth embodiment may further include a step of transmitting an MBS service identifier designated by the UE 100 from the UE 100 to the gNB 200 before the MBS session is started, and a step of the gNB 200 storing the MBS service identifier from the UE 100. When starting a target MBS session corresponding to the stored MBS service identifier, the gNB 200 transmits a session start notification.

[0130] Fig. 13 is a diagram showing an example of the operation according to the fifth embodiment. In Fig. 13, non-essential steps are indicated by dashed lines.

[0131] As shown in Fig. 13, in step S501, the gNB 200 broadcasts a notice including an MBS service identifier of each MBS service (each MBS session) that is not currently being provided but will be provided in the near future. Based on this notice, the UE 100 can recognize the MBS service (MBS session) that the gNB 200 will provide in the near future. The UE 100 may recognize the MBS service (MBS session) that will be provided in the near future by USD provided from the network.

[0132] In step S502, the UE 100 transmits an MBS service identifier indicating an MBS service (MBS session) that the UE 100 wishes to receive to the gNB 200. The gNB 200 receives and stores this MBS service identifier.

[0133] Here, when UE100 is in the RRC connected state, UE100 may, for example, include the MBS service identifier in an MBS Interest Indication message, which is a type of RRC message, and transmit the MBS service identifier to gNB200. This MBS service identifier may be one that is not currently being transmitted (expected to be transmitted in the future). UE100 may notify gNB200 of only the MBS service identifier included in the advance notice received from gNB200 in step S501, or may notify gNB200 of the MBS service identifier regardless of the advance notice.

[0134] On the other hand, when UE100 is in an RRC idle state or an RRC inactive state, UE100 may, for example, notify gNB200 of the MBS service identifier using a PRACH (see the fourth embodiment), or transition to an RRC connected state and transmit the above-mentioned MBS Interest Indication.

[0135] In step S503, the gNB 200 transmits a session start notification (service start notification) including the MBS service identifier. The gNB 200 may transmit the session start notification including the MBS service identifier notified from the UE 100 in step S502.

[0136] As a specific notification timing, the gNB200 may transmit a session start notification at any of the following times. - The timing when the MBS session for the target MBS service identifier starts Timing when the MBS control channel control information of the target MBS service identifier is changed Timing of allocation of MBS traffic channel resources for the target MBS service identifier

[0137] As specific notification content, gNB200 may include at least one of the following information elements in the session start notification. Target MBS service identifier -Start timing of the target MBS service (H-SFN, SFN, subframe number, time, relative time, etc.)

[0138] As a specific notification method, gNB200 may send a session start notification in any of the following ways. RRC messages (UE-specific signaling or SIB) · Change notification for SIB or MBS control channel ·MAC CE (Control Element): In this case, for example, it may be multiplexed into a TB (Transport Block) that transmits a Paging message. UE 100 that is interested in receiving the MBS monitors the MAC CE that is (possibly) transmitted in the Paging Occasion. Paging message (Short Message): In this case, there may be a link between the Short Message or the notification in the Paging message and the MBS service identifier. The link between each bit of the Short Message and the MBS service identifier may be notified in advance by the gNB 200 using an SIB or the like. Also, the start timing may be notified in advance, or a value may be assigned to the bit of the Short Message. For example, when the UE 100 makes a request in step S502, the gNB 200 notifies the UE 100 of the corresponding identifier (bit position) and the like. For example, when the bit position is "00100000", the UE 100 is notified in advance that the third bit is the MBS service identifier. An individual UE 100 may be notified in the Paging message. For example, the notification may be made in association with the UE-ID to be called.

[0139] In step S504, the gNB 200 transmits MBS control information (MBS control channel). In step S505, the gNB 200 transmits MBS data (MBS traffic channel). The UE 100 receives the MBS control channel and attempts to receive the MBS traffic channel.

[0140] Here, the gNB 200 may broadcast only the MBS control channel in advance, and may start transmission of the MBS traffic channel after the start notification in step S503. This allows the UE 100 to promptly start receiving the MBS data of the MBS service that the UE 100 wishes to receive. Alternatively, the transmission of the MBS control channel may start after the start notification. In either case, the UE 100 can reduce the PDCCH monitoring operation during the period when the MBS data of the target MBS service is not yet transmitted, and therefore the power consumption of the UE 100 can be reduced.

[0141] In addition, when gNB200 hands over UE100 to the target gNB200, it may include the MBS service identifier received in step S502 in the handover request sent to the target gNB200.

[0142] Sixth embodiment Next, the sixth embodiment will be described, focusing mainly on the differences from the above-mentioned embodiments.

[0143] In NR, a bandwidth part (BWP) may be set to a cell. FIG. 14 is a diagram showing an example of a BWP. As shown in FIG. 14, a BWP is a frequency part of the entire band of a cell. FIG. 14 shows examples of a BWP1 having a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, a BWP2 having a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and a BWP3 having a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP is set to the UE 100 by the gNB 200, and switching from one BWP to another BWP is controlled by the gNB 200. For example, when multiple BWPs are set to the UE 100, and some BWPs are active and other BWPs are inactive, the gNB 200 can control the active BWP to be switched to another BWP. In addition, the subcarrier spacing and the cyclic prefix can be variably set for each BWP.

[0144] Under such a premise, the gNB 200 may set a BWP for MBS transmission. It is preferable that the UE 100 can grasp information on the BWP for MBS transmission (or information on the BWP in which the UE 100 receives MBS).

[0145] The communication control method according to the sixth embodiment includes a step in which a gNB 200 managing a cell transmits an MBS service identifier corresponding to an MBS session (MBS service) and BWP information associated with the MBS service identifier to a UE 100. This BWP information is information indicating a first BWP used to provide an MBS session in a cell. The contents of the BWP information (transmission BWP information) are the same as those of the above-mentioned embodiments.

[0146] The communication control method according to the sixth embodiment may further include a step in which the gNB200 assigns to the UE100 a second BWP used for unicast transmission to the UE100, and a step in which the UE100 prioritizes reception of the first BWP over reception of the second BWP when the first BWP and the second BWP overlap in time and the UE100 desires to receive an MBS session. This allows the UE100 to receive the MBS even when a collision occurs between the BWP for MBS (the first BWP) and the BWP for unicast (the second BWP). Alternatively, the gNB200 may determine which BWP to prioritize in reception operation when the BWP for unicast and the BWP for multicast overlap in time. In this case, the gNB200 may notify (set) the UE100 of the BWP to be prioritized. The UE100 may notify the gNB200 of which BWP to prioritize. Alternatively, UE100 may notify gNB200 that it can prioritize (i.e., can receive) the BWP for unicast.

[0147] FIG. 15 is a diagram illustrating an example of the operation according to the sixth embodiment.

[0148] As shown in FIG. 15, in step S601, the gNB 200 includes BWP information of the BWP that transmits the MBS control channel in the MBS system information to be transmitted to the UE 100. The UE 100 receives this MBS system information. When multiple MBS control channels exist in one cell, the gNB 200 may include BWP information for each MBS control channel in the MBS system information. The UE 100 performs reception processing of the MBS control information in the BWP that transmits the MBS control channel based on the BWP information included in the MBS system information.

[0149] In step S602, the gNB200 transmits BWP information of the BWP that transmits the MBS traffic channel for each MBS service identifier (or for each group RNTI, or for each network slice identifier) ​​in the MBS control channel (MBS control information). The UE100 receives this MBS control channel. The UE100 performs reception processing of the MBS control information in the BWP that transmits the MBS traffic channel based on the BWP information included in the MBS control channel (step S603). Note that when the scheduling information of the MBS traffic channel is transmitted in the broadcast control channel (MBS system information) (see the second embodiment), the gNB200 may transmit the BWP information of the BWP that transmits the MBS traffic channel in the broadcast control channel (MBS system information).

[0150] Here, the UE 100 in the RRC connected state may preferentially receive the BWP in which the MBS control channel and the MBS traffic channel are transmitted, regardless of the active BWP (BWP for unicast). If the active BWP (BWP for unicast) and the BWP in which the MBS control channel and the MBS traffic channel are transmitted overlap, the UE 100 may preferentially receive the BWP in which the MBS control channel and the MBS traffic channel are transmitted if the UE 100 is interested in receiving MBS.

[0151] In this case, the gNB 200 may be notified by MBS Interest Indication that MBS reception is prioritized. After notifying the MBS reception priority by MBS Interest Indication, the UE 100 may be able to prioritize the multicast BWP. When the UE 100 is no longer interested in MBS reception, the UE 100 may notify the MBS reception is not prioritized by MBS Interest Indication. After notifying the MBS reception non-priority by MBS Interest Indication, the UE 100 may release the priority control of the multicast BWP. As a result, reception by an active unicast BWP is prioritized, and the flexibility of unicast scheduling of the gNB 200 is increased.

[0152] The above-mentioned operation is based on the premise that each MBS control channel and each MBS traffic channel has its own BWP setting, but the gNB200 may broadcast multiple BWP settings together in the MBS system information (list format). Each of the multiple BWP settings may have an index value. For example, the gNB200 broadcasts the index value of the BWP setting for each MBS control channel in the MBS system information. The gNB200 broadcasts the index value of the BWP setting for each MBS traffic channel on the MBS control channel. Here, these index values ​​may be the entry numbers (indexes) of the above-mentioned lists.

[0153] (Other embodiments) In the above embodiment, an example has been described in which a plurality of MBS control channels are associated with different service quality requirements. As another example of such a form, the MBS control channels may be classified into SFN transmission (e.g., MBSFN transmission) and non-SFN transmission (SC-PTM transmission).

[0154] The above-described embodiments are not limited to being implemented separately and independently, but can be implemented in combination of two or more embodiments.

[0155] 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 in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in the computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

[0156] In addition, circuits that execute each process performed by UE100 or gNB200 may be integrated, and at least a part of UE100 or gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC).

[0157] 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, etc. are possible without departing from the spirit of the invention.

[0158] This application claims priority to U.S. Provisional Application No. 63 / 058713 (filed July 30, 2020), the entire contents of which are incorporated herein by reference.

[0159] (Additional Note) (introduction) A revised work item on NR Multicast and Broadcast Services (MBS) was approved. The objectives of the work item are to:

[0160] -Specifies basic RAN functions for broadcast / multicast for UEs in RRC connected state. - Defines a group scheduling mechanism that enables UEs to receive broadcast / multicast services. - This objective includes specifying the extensions necessary to allow simultaneous operation with unicast reception. - Specifies support for dynamic change of broadcast / multicast service delivery between multicast (PTM) and unicast (PTP) with default UE service continuity. - Provide for support of basic mobility with service continuity. - Specify the necessary changes to the RAN architecture and interfaces, taking into account the consequences of SA2 SI in broadcast / multicast, assuming the necessary coordination functions (such as those hosted by the MCE) are in the gNB-CU. - Specifying the changes required to improve the reliability of broadcast / multicast services, e.g. by UL feedback. The level of reliability should be based on the requirements of the application / service provided. Study support for dynamic control of broadcast / multicast transmission areas within one gNB-DU and specify what, if anything, is needed to enable it.

[0161] -Specifies basic RAN functions for broadcast / multicast for UEs in RRC idle / RRC inactive state. -Specifies the changes required to enable reception of Point to Multipoint transmissions by UEs in RRC Idle / RRC Inactive state with the aim of maintaining maximum commonality between the RRC Connected state and the RRC Idle / RRC Inactive state for PTM reception configuration.

[0162] In this appendix, we discuss initial considerations for NR MBS.

[0163] (Discussion) (General Design Considerations) LTE eMBMS had several transmission schemes to enable multicast / broadcast services, such as MBSFN from Rel-9 and SC-PTM from Rel-13. MBSFN transmission is mainly designed for multi-cell transmission, and simultaneous transmission is performed within an MBSFN area in (PMCH) MBSFN subframes. On the other hand, SC-PTM transmission focuses on single-cell transmission, and MBMS is transmitted over PDSCH. As shown in Figure 6, from a Layer 2 perspective, MBSFN related logical channels are mapped to MCH, while SC-PTM related logical channels are mapped to DL-SCH.

[0164] Observation 1: In LTE, the MCCH and MTCH are mapped to the MCH in the MBSFN transmission scheme, and the SC-MCCH and SC-MTCH are mapped to the DL-SCH in the SC-PTM transmission scheme.

[0165] The WID captures some limitations and assumptions that are useful to consider in what design is intended for this WI: For the physical layer, no new numerology or physical channels are expected to be introduced, as shown below. This means that NR MBS related logical channels are mapped to DL-SCH. Physical Layer: Limits the scope of this WI to the current Rel-15 numerology, physical channels (PDCCH / PDSCH), and signals.

[0166] Observation 2: The scope of this WI is limited within the existing numerology and physical channels (PDCCH / PDSCH), i.e., NR MBS related channels are assumed to be mapped to DL-SCH.

[0167] Even if MBSFN is not used, multi-cell transmission could be supported by DL-SCH in a future release, e.g., by combining CoMP transmission with simultaneous delivery of user plane packets. DL-SCH is therefore subject to the following restrictions and assumptions:

[0168] No design decisions made for this WI in Release 17 preclude the introduction of the following features in future releases: - Standardization support for SFN with multiple cells above gNB-DU level

[0169] Observation 3: The DL-SCH (PDSCH) may be extended for multi-cell transmission in future releases.

[0170] In view of the above observations, the SC-PTM specification, which is mature in LTE and covers not only transmission methods but also other mechanisms such as configuration and service continuity, could be a good baseline for NR MBS design considerations. Therefore, in this WI, RAN2 should reuse the existing SC-PTM specification as much as possible and consider what can be extended on top of SC-PTM to support new / various use cases of NR MBS.

[0171] Proposal 1: RAN2 should agree to adopt the existing LTE SC-PTM specifications as the baseline for NR MBS design, including group scheduling mechanisms, service continuity support (e.g., neighbor cell information), and UE interest indication.

[0172] Proposal 2: If Proposal 1 is agreed, RAN2 should consider what can be extended beyond the SC-PTM baseline to support new / various use cases envisioned for NR MBS.

[0173] In the following sections, we use the SC-PTM specification as a baseline for our descriptions, i.e. we assume that Proposal 1 will be agreed upon, but the descriptions can be reused even if mechanisms like MBSFN are introduced.

[0174] (Control Plane Enhancements Overview) In LTE SC-PTM, configuration is provided by two messages: SIB20 and SC-MCCH. SIB20 provides SC-MCCH scheduling information, and SC-MCCH provides SC-MTCH scheduling information including G-RNTI and TMGI, and neighbor cell information.

[0175] The advantage of the LTE two-stage configuration as shown in Figure 16 was that the SC-MCCH scheduling was independent from the SIB20 scheduling in terms of repetition period, duration, modification period, etc. The two-stage configuration facilitated frequent scheduling / updating of the SC-MCCH, especially for delay-sensitive services and / or UEs that join the session late. According to WID, this is also true for NR MBS, since one of the applications is group communication, etc.

[0176] Observation 4: In LTE, the two-stage configuration with SIB20 and SC-MCCH lends itself to different scheduling of these control channels, which also lends itself to NR MBS.

[0177] Proposal 3: RAN2 should agree on a two-stage configuration with different NR MBS messages, such as SIB20 in SC-PTM and SC-MCCH.

[0178] In addition to Proposal 3, NR MBS is envisioned to support various types of use cases as outlined in the WID. It may be noted that NR MBS should be appropriately designed for various requirements ranging from delay-sensitive applications such as mission-critical and V2X to delay-tolerant applications such as IoT, in addition to other aspects of requirements ranging from lossless applications such as software distribution to UDP type streaming such as IPTV.

[0179] Therefore, the design of the control channel should consider its flexibility and resource efficiency, otherwise, for example, when delay-tolerant and delay-sensitive services are configured together in one control channel, the control channel needs to be scheduled frequently to satisfy the delay requirements from the delay-sensitive services, which may cause more signaling overhead.

[0180] Objective A of the SA2 SI is about enabling general MBS services over 5GS and identified use cases that may benefit from this capability include (but are not limited to) public safety, mission critical, V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, over-the-air software distribution, group communications, and IoT applications.

[0181] Observation 5: The NR MBS control channel needs to be flexible and resource efficient for different types of use cases.

[0182] In these use cases, the configured channels may be separated. For example, one control channel may provide frequent delay-sensitive services, while another control channel may provide sparse delay-tolerant services. In LTE SC-PTM, a cell may have only one SC-MCCH. However, considering that more use cases than in LTE are expected, NR MBS should remove such restrictions. If multiple SC-MCCHs are allowed in a cell, each SC-MCCH may have different scheduling configurations, such as repetition period, that can be optimized for a particular service. How a UE identifies the SC-MCCH that provides the service it is interested in needs further study.

[0183] Proposal 4: RAN2 should discuss whether multiple control channels will be supported in cells in NR MBS, like multiple SC-MCCHs that were not present in LTE.

[0184] Furthermore, a new paradigm in NR is the support of on-demand SI transmission. This concept can be reused for the SC-MCCH of NR MBS, i.e., on-demand SC-MCCH. For example, the SC-MCCH for delay-tolerant services is provided on-demand, so that signaling resource consumption can be optimized. Of course, the network has other options to provide the SC-MCCH periodically, i.e., not on-demand, for delay-sensitive services, etc.

[0185] Proposal 5: RAN2 should discuss the option of a control channel being provided on an on-demand basis, such as the on-demand SC-MCCH that was not available in LTE.

[0186] Another possibility could be further considered to merge these messages, i.e. one-stage configuration. For example, as shown in Fig. 17, the SIB provides SC-MTCH scheduling information directly, i.e. without SC-MCCH. This would provide optimization for delay-tolerant services and / or power-sensitive UEs. For example, a UE may request a SIB (on-demand) and the gNB may start providing the SIB and corresponding services after requests from multiple UEs. These UEs do not need to monitor the repeatedly broadcasted SC-MCCH.

[0187] Proposal 6: RAN2 should discuss options such as the SIB providing traffic channel configuration directly if multicast reception without SC-MCCH (i.e., one-stage configuration) is supported.

[0188] (Overview of User Plane Extensions) In LTE eMBMS, regardless of MBSFN or SC-PTM, there is no PDCP layer in the Uu protocol stack, as shown in Figure 18. In addition, one transmission per logical channel is allowed, i.e., only UM mode is used in the RLC layer, and blind retransmission is not used in HARQ. In other words, retransmission of lost packets relied on higher layer mechanisms in LTE eMBMS.

[0189] Observation 6: In LTE eMBMS, no retransmission scheme is supported at the AS layer.

[0190] On the other hand, NR MBS appears to require a more reliable and flexible transmission scheme to be implemented as an AS function, as quoted from the WID below:

[0191] [···] It specifies support for dynamic change of broadcast / multicast service delivery between multicast (PTM) and unicast (PTP) with default UE service continuity. Provide support for basic mobility with service continuity. [···] For example, UL feedback specifies the changes required to improve the reliability of broadcast / multicast services. The level of reliability should be based on the requirements of the application / service provided. [···]

[0192] Observation 7: In NR MBS, some AS layer enhancements may be required to improve the reliability and flexibility of multicast transmission and reception.

[0193] Regarding groupcast retransmissions, it can be considered to be handled by MAC (HARQ), RLC (ARQ), and / or PDCP (status report). These mechanisms can be useful in particular for UE mobility, i.e., compensating for packets lost due to radio quality degradation and / or transport path switching, as well as Uu.

[0194] Multicast / groupcast HARQ feedback has not been introduced in LTE. Meanwhile, Rel-16 NR V2X supports sidelink groupcast HARQ feedback, i.e., ACK / NACK or NACK-only. This is one possibility to reuse and improve NR MBS performance. While it is ultimately up to RAN1 to decide the details, RAN2 may discuss the usefulness of HARQ feedback / retransmissions to improve multicast reception reliability for idle, inactive and connected UEs.

[0195] Proposal 7: RAN2 should discuss whether HARQ feedback / retransmission is useful for multicast of NR MBS for RRC idle, inactive and connected UEs.

[0196] In the case of unicast, a double feedback loop is supported for HARQ and ARQ to improve reception reliability. If the case of groupcast in NR MBS is similar, one possibility to introduce ARQ, i.e. RLC AM mode, should be discussed to improve reliability at least for connected UEs. However, it can usually be assumed that the paired uplink channel cannot be used for groupcast. Therefore, one potential challenge is how the UE sends feedback (STATUS PDU) to the gNB.

[0197] Proposal 8: RAN2 should discuss whether RLC AM mode is supported for NR MBS multicast, at least for RRC connected UEs.

[0198] Moreover, if the NR MBS needs to consider lossless delivery during handover, e.g., for software distribution use cases, PDCP will help to recover packets that are dropped as they are today. Figure 19 shows the enhancements for reliable reception and multicast / unicast switching. Another advantage of the PDCP layer support is that it is possible to configure multicast bearers with split bearers and / or duplication with unicast bearers. This is also one of the potential mechanisms for "dynamic change of broadcast / multicast service delivery between multicast (PTM) and unicast (PTP) with given UE service continuity" as described in the WID. It is necessary to further study whether various PDCP features such as header compression, encryption, etc. can be supported for multicast reception.

[0199] Proposal 9: RAN2 should discuss whether the PDCP layer is supported for at least groupcast of NR MBS for RRC connected UEs.

[0200] Finally, it should be considered whether SDAP is necessary in the NR MBS protocol stack. NR supports an SDAP layer to handle QoS flows in radio bearers. On the other hand, an SDAP layer was not present in traditional LTE and therefore not in eMBMS. It can be assumed that the SDAP layer does not harm the reception of multicast data, but the necessity of the SDAP layer may actually depend on the assumptions / requirements of higher layers. Therefore, RAN2 may need to wait for the progress of other WGs on whether it is necessary.

[0201] Observation 8: RAN2 may need to check with other WGs whether the SDAP layer is required in NR MBS.

Claims

1. A communication control method for use in a mobile communication system that provides a multicast and broadcast service (MBS) from a network node to a user device, comprising: The network node managing a cell transmits to the user equipment first MBS bandwidth portion information corresponding to a first MBS service and second MBS bandwidth portion information corresponding to a second MBS service, The first MBS bandwidth portion information is information indicating a first bandwidth portion used for providing the first MBS service in the cell, The second MBS bandwidth portion information is information indicating a second bandwidth portion used for providing the second MBS service in the cell. Communications control method.

2. A network node in a mobile communication system providing a multicast and broadcast service (MBS) to a user device, comprising: A control unit that manages the cells; a transmitter configured to transmit first MBS bandwidth partial information corresponding to a first MBS service and second MBS bandwidth partial information corresponding to a second MBS service to the user device; The first MBS bandwidth portion information is information indicating a first bandwidth portion used for providing the first MBS service in the cell, The second MBS bandwidth portion information is information indicating a second bandwidth portion used for providing the second MBS service in the cell. Network node.

3. A user equipment in a mobile communication system in which a network node provides a multicast and broadcast service (MBS), comprising: a receiving unit for receiving first MBS bandwidth partial information corresponding to a first MBS service and second MBS bandwidth partial information corresponding to a second MBS service from the network node managing a cell; The first MBS bandwidth portion information is information indicating a first bandwidth portion used for providing the first MBS service in the cell, The second MBS bandwidth portion information is information indicating a second bandwidth portion used for providing the second MBS service in the cell, The receiving unit performs at least one of a process of receiving the first MBS service based on the first MBS bandwidth partial information and a process of receiving the second MBS service based on the second MBS bandwidth partial information. User equipment.

4. A chipset for controlling a user equipment in a mobile communication system in which a network node provides a multicast broadcast service (MBS), comprising: receiving from the network node managing a cell first MBS bandwidth portion information corresponding to a first MBS service and second MBS bandwidth portion information corresponding to a second MBS service; The first MBS bandwidth portion information is information indicating a first bandwidth portion used for providing the first MBS service in the cell, The second MBS bandwidth portion information is information indicating a second bandwidth portion used for providing the second MBS service in the cell, The receiving process includes performing at least one of a process of receiving the first MBS service based on the first MBS bandwidth partial information and a process of receiving the second MBS service based on the second MBS bandwidth partial information. Chipset.

5. A user device in a mobile communication system in which a network node provides a multicast and broadcast service (MBS), receiving from said network node managing a cell first MBS bandwidth portion information corresponding to a first MBS service and second MBS bandwidth portion information corresponding to a second MBS service; The first MBS bandwidth portion information is information indicating a first bandwidth portion used for providing the first MBS service in the cell, The second MBS bandwidth portion information is information indicating a second bandwidth portion used for providing the second MBS service in the cell, The receiving process includes performing at least one of a process of receiving the first MBS service based on the first MBS bandwidth partial information and a process of receiving the second MBS service based on the second MBS bandwidth partial information. program.

6. A mobile communication system comprising a network node managing a cell, the network node providing a multicast / broadcast service (MBS) to a user device, the mobile communication system comprising: The network node transmits to the user equipment first MBS bandwidth portion information corresponding to a first MBS service and second MBS bandwidth portion information corresponding to a second MBS service; The first MBS bandwidth portion information is information indicating a first bandwidth portion used for providing the first MBS service in the cell, The second MBS bandwidth portion information is information indicating a second bandwidth portion used for providing the second MBS service in the cell. Mobile communication system.

Citation Information

Patent Citations

  • Method and device for terminal receiving service continuity indicator

    US20180242206A1

  • Increase of spectral capacity of embms-cell when deployed as a supplementary downlink carrier

    US20190090103A1

  • Mobile communication system

    WO2018062370A1

  • Multicast and broadcast services in 5g networks for IoT applications

    WO2019136128A1

  • KR20200073118A