Alignment of common frequency resource for multicast services
Patent Information
- Application Number
- PCT/CN2023/093909
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-21
Smart Images

Figure CN2023093909_21112024_PF_FP_ABST
Abstract
Description
ALIGNMENT OF COMMON FREQUENCY RESOURCE FOR MULTICAST SERVICES
[0001] FIELDS
[0002] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to apparatuses, methods, and computer readable storage medium for alignment of a common frequency resource (CFR) for multicast services.BACKGROUND
[0003] Multicast and broadcast services (MBSs) are supported in the third-generation partnership project (3GPP) Release 17 (Rel-17) for New Radio (NR) . A point to multi-point (PTM) transmission is expected to efficiently provision MBSs to multiple users by using the same radio framework as a unicast transmission. In Rel-17, the reception of a multicast service by user equipment (UEs) is enabled in a Radio Resource Control Connected (RRC_CONNECTED) state. Enhancements to a fifth-generation system (5GS) architecture are further identified and evaluated in Release 18 (Rel-18) to provide MBSs. A focus is to enable the reception of multicast services by the UEs in an RRC inactive (RRC_INACTIVE) state for scalability and power saving purposes. For support of multicast reception by UEs in an RRC_INACTIVE state, PTM configurations are needed for UEs receiving multicast services in an RRC_INACTIVE state.
[0004] A CFR can be used for a multicast control channel (MCCH) and a multicast traffic channel (MTCH) which may indicate where a UE expects multicast relevant control information and data. For example, the UE may use the CFR in computations of downlink control information (DCI) for scheduling multicast services. However, CFRs for UEs in RRC_CONNECTED and RRC_INACTIVE states may not be aligned, and therefore these UEs may not have the same DCI interpretation for the multicast services.SUMMARY
[0005] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, assistance information related to a first CFR, the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a MTCH; and receive, in an inactive state, the first scheduling information based on the assistance information.
[0006] In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: transmit, to a first apparatus, assistance information related to a first CFR, the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a MTCH; and transmit, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.
[0007] In a third aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a second apparatus, assistance information related to a first CFR, the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a MTCH; and receiving, in an inactive state, the first scheduling information based on the assistance information.
[0008] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first apparatus, assistance information related to a first CFR, the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a MTCH; and transmitting, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.
[0009] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, assistance information related to a first CFR, the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a MTCH; and means for receiving, in an inactive state, the first scheduling information based on the assistance information.
[0010] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, assistance information related to a first CFR, the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a MTCH; and means for transmitting, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.
[0011] In a seventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third or fourth aspect.
[0012] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0014] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0015] FIG. 2 illustrates an example scenario of scheduling multicast services with the same DCI;
[0016] FIG. 3 illustrates a signaling diagram for an example process for CFR alignment in accordance with some example embodiments of the present disclosure;
[0017] FIG. 4 illustrates a signaling diagram for an example process for multicast service provision in accordance with some example embodiments of the present disclosure;
[0018] FIG. 5 illustrates a flowchart of an example method for CFR alignment in accordance with some example embodiments of the present disclosure;
[0019] FIG. 6 illustrates a flowchart of an example method for CFR alignment in accordance with some other example embodiments of the present disclosure;
[0020] FIG. 7 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0021] FIG. 8 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0022] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0023] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0024] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0025] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0026] It shall be understood that although the terms “first, ” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For examp le, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0027] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0028] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0029] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0030] As used in this application, the term “circuitry” may refer to one or more or all of the following:
[0031] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and
[0032] (b) combinations of hardware circuits and software, such as (as applicable) :
[0033] (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and
[0034] (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[0035] (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0036] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0037] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the sixth generation (6G) communication protocols and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0038] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives se rvices therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0039] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0040] As used herein, the term “resource, ” or “transmission resource, ” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in a time domain, a resource in a frequency domain, a resource in a space domain, a resource in a code domain, or any other resources enabling a communication, and the like. In the following, unless explicitly stated, a resource in both the frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0041] As mentioned above, the reception of a multicast service by UEs in an RRC_CONNECTED state (also referred to as RRC_CONNECTED UEs) is enabled in Rel-17. In addition, broadcast reception in all RRC states is specified in Rel-17. For MBS enhancements, the reception of multicast services by UEs in an RRC_INACTIVE state (also referred to as RRC_INACTIVE UEs) is enabled in Rel-18. To support such enhancements, PTM configurations are needed for UEs receiving multicast services in an RRC_INACTIVE state. Moreover, an impact of mobility and state transition for these UEs is studied.
[0042] A UE in an RRC_INACTIVE state may apply a configuration of a multicast service in a cell to start or continue receiving a multicast service that the UE has joined. An approach, similar to Rel-17 broadcast, may be used to provide such a configuration to the UE. For example, a system information block (SIB) or a MCCH may be broadcast in a cell periodically, so that RRC_INACTIVE UEs can receive the related configuration and any updates to this configuration. Further, if a UE transits from an RRC_CONNECTED state to an RRC_INACTIVE state, such a configuration may be provided in the current cell in a RRC release message (also referred to as RRC release) with suspendConfig.
[0043] Furthermore, a UE in the RRC_INACTIVE state may be able to move to a neighbor cell in a radio access network (RAN) while receiving a multicast service without notifying the network and to be able to receive the same service in a reselected or newly camped cell, if the service is provided to the UEs in the RRC_INACTIVE state. For reception of the service in the newly camped cell, the UE may first read a SIB of the neighbor cell that provides a configuration for a MCCH, then wait for a periodic MCCH to be scheduled, and then learn how to receive a specific multicast service. It is possible that the UE would not find the service being provided to the UEs in the RRC_INACTIVE state after reading the MCCH and then reconnect to receive the service in an RRC_CONNECTED state. It is also possible that the service is not provided at all in the new cell, as there were no UEs that joined the multicast session in that cell before. In this case, the information about the multicast service may be obtained from the neighbor cell.
[0044] For multicast data scheduling in Rel-17, a CFR configured by an RRCReconfiguration message is defined for multicast scheduling as an “MBS frequency region” with a number of contiguous physical resource blocks (PRBs) confined within and with the same numerology as a downlink (DL) bandwidth part (BWP) . The multicast scheduling may have specific characteristics, including, for example, physical downlink control channel (PDCCH) , physical downlink shared channel (PDSCH) , and / or Semi-persistent Scheduling (SPS) configurations.
[0045] A CFR may indicate where the UE expects multicast relevant control information and data. It may be configured per active BWP. Same group of UEs interested in a specific multicast session has overlapping regions of CFRs, in order to be able to receive group common PDCCH and PDSCH transmissions. Different UEs interested in different multicast services may have non-overlapping CFRs. For example, such a CFR (for example, a size and a starting point in a frequency grid) may be used for scheduling the multicast data. The UE is expected to use the CFR for selected DCI related computations, for example, when calculating a size of a Frequency Domain Resource Allocation (FDRA) field of multicast DCI and when decoding a FDRA field of actually transmitted DCI.
[0046] Regarding multicast reception by the UEs in the RRC_INACTIVE state, the following may be taken as baseline. The same PDCCH and PDSCH resources (e.g., resources used for a MTCH) can be used for all UEs (including UEs in CONNECTED and INACTIVE states) for receiving the same multicast session. Different configuration and resources are not precluded as well. It is for further study what exactly can be common and what is not common, such as Hybrid Automatic Repeat Request (HARQ) , SPS and / or the like, and what is needed in addition (to legacy PTM configurations) .
[0047] For a MTCH, the same DCI format of Rel-17 multicast (e.g., DCI format 4-1 or 4-2) may be reused for dynamic scheduling of multicast in an RRC_INACTIVE state. For MCCH scheduling, DCI format 4-0 may be used. Control information (e.g., DCI) and data (e.g., PDSCH) for multicast may be transmitted over the air once, and UEs in both the RRC_INACTIVE and RRC_CONNECTED states may be able to receive such information. The UEs in the RRC_INACTIVE state may also use the same Rel-17 DCI formats 4_1 and 4_2 to receive the control information and data of a multicast service and use the same Rel-17 DCI format 4_0 to receive the MCCH information.
[0048] Furthermore, the same CFR may be used for the multicast MCCH and MTCH. For example, similar to Rel-17 broadcast, it is expected that the same CFR is used for multicast MCCH (where the UE learns what services are transmitted to UEs in the RRC_INACTIVE state along with PTM configurations for such services) and MTCH (e.g., the multicast data) .
[0049] However, in some scenarios, the same DCI format 4_1 or 4_2 scheduling the same PDSCH or MTCH data for a specific multicast service is problematic. In an example scenario, if a plurality of multicast services is provided to RRC_CONNECTED UEs in a cell, these services would be available to the UEs in the RRC_INACTIVE state as well. In this case, a CFR for the RRC_INACTIVE state needs to include CFRs for a plurality of multicast services. Thus, the sizes of the CFRs for UEs in the RRC_CONNECTED and RRC_INACTIVE states interested to receive the same service cannot be aligned. Due to such misalignment, the UEs in the RRC_CONNECTED and RRC_INACTIVE states would interpret the (field) size and content of the DCI differently, as such interpretation necessitates usage of the CFR in calculations. Further, RRC_CONNECTED and RRC_INACTIVE UEs that are interested to receive the same multicast service cannot have the same DCI understanding in terms of size of the DCI (fields) and actual interpretation of the DCI indication. As a result, current means are not enough to be able to schedule UEs in RRC_CONNECTED and RRC_INACTIVE states to receive the same multicast service using the same DCI.
[0050] Example embodiments of the present disclosure propose a CFR alignment scheme. With this scheme, assistance information related to a CFR, which is associated with scheduling information (such as DCI) for multicast data on a MTCH, is provided by a network to a device in an inactive state. Based on the assistance information, the device in the inactive state receives the scheduling information and further the multicast data which may be the same as those received by a device in a connected state. Thus, the multicast data scheduled by the same scheduling information may be received by devices in inactive and connected states.
[0051] In this way, devices in inactive and connected state can receive the multicast services using the same scheduling information, even in the case that a CFR for the inactive devices does not overlap with a CFR of the connected devices. The proposed scheme also allows the configuration where the CFR of the inactive devices overlaps with the CFR of the connected devices. As such, multicast services may be provided more flexibly and efficiently.
[0052] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented.
[0053] In the communication environment 100, a plurality of communication devices, comprising a first apparatus 110 and a second apparatus 120, can communicate with each other. In some example embodiments, the first apparatus 110 may operate as a terminal device, and the second apparatus 120 may operate as a network device serving the terminal device. The second apparatus 120 may provide a cell 122 as a serving area.
[0054] The communication environment 100 may further comprise a third apparatus 130 which may operate as another terminal device and can communicate with the first apparatus 110 and / or the second apparatus 120. In the communication environment 100, both the first apparatus 110 and the third apparatus 130 may camp in the cell 122.
[0055] It is to be understood that the number of devices and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implement example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 122, and one or more additional cells served by the second apparatus 120 or another device may be deployed in the communication environment 100.
[0056] In the following, for the purpose of illustration, some example embodiments are described with the first apparatus 110 and the third apparatus 130 operating as terminal devices and the second apparatus 120 operating as a network device. However, in some example embodiments, operations described with respect to a terminal device may be implemented at a network device or other devices, and operations described with respect to a network device may be implemented at a terminal device or other devices.
[0057] In some example embodiments, if the first apparatus 110 or the third apparatus is a terminal device and the second apparatus 120 is a network device, a link from the second apparatus 120 to the first apparatus 110 or the third apparatus 130 is referred to as a DL, while a link from the first apparatus 110 or the third apparatus 130 to the second apparatus 120 is referred to as an uplink (UL) . In DL, the second apparatus 120 is a transmitting (TX) device (or a transmitter) , and the first apparatus 110 or the third apparatus 130 is a receiving (RX) device (or a receiver) . In UL, the first apparatus 110 or the third apparatus 130 is a TX device (or a transmitter) , and the second apparatus 120 is a RX device (or a receiver) .
[0058] In the scenario where the first apparatus 110 and the third apparatus 130 operate as terminal devices that communicate with each other directly, a link between the first apparatus 110 and the third apparatus 130 is referred to as a sidelink (SL) . In SL, one of the first apparatus 110 and the third apparatus 130 is a TX device (or a transmitter) , and the other of the first apparatus 110 and the third apparatus 130 is a RX device (or a receiver) .
[0059] Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0060] In the communication environment 100, the first apparatus 110 and / or the third apparatus 130 can move across neighbor cells. These cells may be provided by the same device or different devices. In an example, the second apparatus 120 may provide more than one cell, and the first apparatus 110 and / or the third apparatus 130 may move across cells provided by the second apparatus 120. In another example, the first apparatus 110 and / or the third apparatus 130 may move between the cell 122 served by the second apparatus 120 and a cell served by another device (not shown) .
[0061] The first apparatus 110 and the third apparatus 130 can receive multicast services in the cell 122. One or more CFRs may be configured for the first apparatus 110 and the third apparatus 130, which indicate where multicast relevant control information and data are expected. Such CFRs may be used by the first apparatus 110 and the third apparatus 130 in the computations of scheduling information (such as DCIs) for the control information and data. As an example, DCI formats 4_1 and 4_2 may be used to schedule multicast data on a MTCH, and DCI format 4_0 may be used to receive the MCCH information.
[0062] In an example, for resource allocation in a frequency domain, two downlink resource allocation schemes, type 0 and type 1, are supported. A UE, which is an example implementation of the first apparatus 110 or the third apparatus 130, may assume that if a scheduling grant is received with DCI format 1_0, 4_0 or 4_1, then downlink resource allocation type 1 is used. If the scheduling DCI may be configured to indicate the downlink resource allocation type as part of the “Frequency domain resource assignment” field by setting a higher layer parameter resourceAllocation in PDSCH-Config to “dynamicSwitch” for DCI format 1_1 or setting a higher layer parameter resourceAllocationDCI-1-2 in PDSCH-Config to “dynamicSwitch” for DCI format 1_2 or setting a higher layer parameter resourceAllocation in pdsch-ConfigMulticast to “dynamicSwitch” for DCI format 4_2, then the UE may use downlink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise, the UE may use the downlink frequency resource allocation type as defined by the higher layer parameter resourceAllocation in PDSCH-Config for DCI format 1_1 or by the higher layer parameter resourceAllocationDCI-1-2 for DCI format 1_2 or by the higher layer parameter resourceAllocation in pdsch-ConfigMulticast for DCI format 4_2.
[0063] In downlink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks defined by the higher layer parameter rbg-Size configured by PDSCH-Config and the size of the bandwidth part is defined in Table 1.
[0064] Table 1
[0065] The total number of RBGs (NRBG) for a downlink bandwidth part i of size PRBs is given by where the size of the first RBG is the size of last RBG is if and P otherwise, and size of all other RBGs is P, and is the starting PRB of a downlink bandwidth part i.
[0066] In downlink resource allocation of type 0 scheduled using DCI with cyclic redundancy check (CRC) scrambled by a Group Radio Network Temporary Identifier (G-RNTI) for multicast or a Group Configured Scheduling RNTI (G-CS-RNTI) , the resource block assignment information bitmap is calculated based on the description above with the following changes: the parameter is the starting PRB of a CFR, is the size of the CFR and the value of the higher layer parameter rbg-Size is configured by pdsch-ConfigMulticast.
[0067] The bitmap is of size NRBG bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs may be indexed in the order of increasing frequency and starting at the lowest frequency of the bandwidth part. The order of RBG bitmap is such that RBG 0 to RBG NRBG-1 are mapped from a most significant bit (MSB) to a least significant bit (LSB) . The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, and the RBG is not allocated to the UE otherwise.
[0068] In downlink resource allocation of type 1 scheduled using DCI format 4_0 or DCI format 4_1 with CRC scrambled by G-RNTI, G-CS-RNTI or MCCH-RNTI, the resource block assignment information indicates to the scheduled UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks. A downlink type 1 resource block assignment field in the DCI format 4_0 or DCI format 4_1 comprises a resource indication value (RIV) corresponding to a starting resource block in reference to the lowest RB of the CFR, e.g., and a length in terms of virtually contiguously allocated resource blocks LRBs, where is given by the size of CORESET 0 if CORESET 0 is configured for the cell, or the size of an initial DL bandwidth part if CORESET 0 is not configured for the cell.
[0069] The RIV is defined by the following: if then
[0070] else
[0071] where L'RBs=LRBs / K, RB'start=RBstart / K and L'RBs does not exceed If K is the maximum value from set {1, 2, 4, 6, 8, 10, 12} which satisfies otherwise K = 1.
[0072] In downlink resource allocation of type 1 scheduled using DCI format 4_2 with CRC scrambled by G-RNTI for multicast or G-CS-RNTI, the description above with the following changes: RBstart corresponds to a starting resource block in reference to the lowest RB of the CFR and is the size of the CFR.
[0073] If DCI format 4_1 is used for scheduling of a PDSCH for multicast in a cell, the following information is transmitted by means of the DCI format 4_1 with CRC scrambled by G-RNTI configured by G-RNTI-Config or G-CS-RNTI: frequency domain resource bits. is equal to the size of CORESET 0 if CORESET 0 is configured for the cell or the size of an initial DL bandwidth part if CORESET 0 is not configured for the cell.
[0074] If DCI format 4_2 is used for the PDSCH scheduling, the following information is transmitted by means of the DCI format 4_2 with CRC scrambled by G-RNTI configured by G-RNTI-Config or G-CS-RNTI: frequency domain resource assignment –a number of bits determined by the following: NRBG bits if only resource allocation type 0 is configured, bits if only resource allocation type 1 is configured, or bits if resourceAllocation in PDSCH-Config-Multicast is configured as “dynamicSwitch” . is the size of the CFR as configured by higher layer parameter locationAndBandwidth-Multicast.
[0075] If resourceAllocation in PDSCH-Config-Multicast is configured as “dynamicSwitch” , a MSB is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. For resource allocation type 0, the NRBG LSBs provide the resource allocation. For example, for resource allocation type 1, the LSBs provide the resource allocation.
[0076] In the communication scenario 100, the first apparatus 110 and / or the third apparatus 130 may operate either in an inactive state (e.g., a RRC_INACTIVE state) or in a connected state (e.g., in a RRC_CONNECTED state) . In some example embodiments, the first apparatus 110 and the third apparatus 130 in connected and inactive states may be scheduled to receive the same multicast service using the same DCI.
[0077] FIG. 2 shows an example scenario 200 of scheduling multicast services with the same DCI. In the scenario 200, a UE (or “UE-1” ) is receiving multicast service 1 in an RRC_CONNECTED state. Similarly, another UE (or “UE-2” ) receives multicast service 2 in an RRC_CONNECTED state. UE-1 and / or UE-2 may be an example implementation of the third apparatus 130. The two services may be any suitable multicast services. In an example, one service such as multicast service 1 may be provided for public safety, and the other service such as multicast service 2 may be provided for vehicle to everything (V2X) .
[0078] As shown in FIG. 2, CFRs 205 and 210 configured for multicast service 1 and multicast service 2 are slightly overlapping, but mostly separated. As such, a gNB, which may be an example implementation of the second apparatus 120, may be able to schedule both the services in the same slot in a more flexible way. If there are some other UEs interested in both the two services in an RRC_CONNECTED state, the gNB would configure to those UEs a CFR 215 that is the union of the CFRs 205 and 210 for both UE-1 and UE-2. UE-1 and UE-2 may compute a size of a FDRA field of a multicast DCI using its own CFR configuration (for example, sizes and starting points of the CFRs 205 and 210) . In addition, when a DCI is received, UE-1 and UE-2 would interpret the fields of the DCI again using their own CFR configuration.
[0079] The same services would be available to a UE in an RRC_INACTIVE state. In this case, the gNB may configure the CFR 215 for UEs in the RRC_INACTIVE state, which includes both the CFRs 205 and 210 for service 1 and 2, as such field will contain both the services. Based on the information about the CFR 215, a UE in the RRC_INACTIVE state, which may be an example implementation of the first apparatus 110, may receive the multicast DCI for multicast service 1 and multicast service 2.
[0080] Some example implementations of the present disclosure will be described in detail below with reference to FIGS. 3 and 4.
[0081] FIG. 3 shows a signaling diagram for an example process 300 for CFR alignment according to some example embodiments of the present disclosure.
[0082] As shown in FIG. 3, the second apparatus 120 transmits (305) , to the first apparatus 110, assistance information related to a CRF (referred to as a first CFR) that is associated with scheduling information (referred to as first scheduling information) for data of a multicast service carried on a MTCH. Accordingly, the first apparatus 110 receives (310) this assistance information from the second apparatus 120. The first scheduling information may comprise a DCI or other types of scheduling information that can be used for scheduling multicast data on the MTCH.
[0083] In some example embodiments, the assistance information may comprise a configuration of the first CFR, for example, including a full configuration of the first CFR with PDSCH configurations and / or the like. In an example, the first CFR may comprise one or more CFRs that are configured for devices in a connected state. For example, in the scenario 200 as shown in FIG. 2, the first CFR provided to the first apparatus 110 may comprise the CFR 215 which includes both the CFRs 205 and 210 configured for UE-1 and UE-2 in an RRC_CONNECTED state. In this way, a configuration of the CFR 205 for multicast service 1 in an RRC_CONNECTED state may be indicated to the first apparatus 110, and a relevant configuration of the CFR 210 for multicast service 2 in an RRC_CONNECTED state may be provided to the first apparatus 110, as well.
[0084] In some example embodiments, the assistance information related to the first CFR may comprise at least one parameter of the configuration of the first CFR that can be used for determining at least one parameter of the first scheduling information. In an example, the at least one parameter of the configuration of the first CFR may comprise at least one of a size (e.g., the number of PRBs) or a starting point (e.g., a starting PRB) of the first CFR. Based on the knowledge of the size and / or starting point of the first CFR, the calculations of the parameters such as a size of a FDRA field of DCI may be performed. In this way, only the configurations needed for calculations of the first scheduling information such as a DCI is provided to the first apparatus 110. Thus, signaling overhead may be reduced, thereby improving resource efficiency and network capacity.
[0085] In some example embodiments, the assistance information may comprise at least one parameter of the first scheduling information that can be determined based on a configuration of the first CFR. For example, in the example embodiments where the first scheduling information comprises DCI, the at least one parameter of the first scheduling information may comprise a size of a field (such as a FDRA field) of DCI.
[0086] In this case, the needed parameters of the first scheduling information may be directly provided to the first apparatus 110. Accordingly, the first apparatus 110 may use those parameters directly, rather than deriving them using a CFR. As the parameters (such as a field size and / or the like) of the first scheduling information is directly configured, there is no need for the first apparatus 110 to calculate a field size or other parameters of the first scheduling information based on the CFR relevant configuration. Thus, computing and processing resources of the first apparatus 110 may be saved without requirements for calculations based on the CFR.
[0087] In some example embodiments, the assistance information related to the first CFR may be configured by the second apparatus 120 per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) . In an example, the TMGI, G-RNTI and / or G-CS-RNTI may be associated with a cell (e.g., the cell 122) which the first apparatus 110 currently camps in. In this way, the devices may use the same scheduling information to receive multicast services in a cell.
[0088] In some example embodiments, the TMGI, G-RNTI and / or G-CS-RNTI may be associated with a neighbor cell of the first apparatus 110. For example, in the scenario that the first apparatus 110 moves from a neighbor cell to the cell 122, it is possible that there is no multicast service provided in the cell 122 as there were no devices that joined a multicast session in the cell 122 before. In this case, the assistance information configured per TMGI, G-RNTI and / or G-CS-RNTI of the neighbor cell may be provided to the first apparatus 110 such that the first apparatus 110 may be able to receive the same service in the reselected or newly camped cell 122.
[0089] In the case that both the neighbor cell and the current cell are provided by the second apparatus 120, the second apparatus 120 may transmit the assistance information configured per TMGI, G-RNTI and / or G-CS-RNTI of the neighbor cell to the first apparatus 110. In the case that the neighbor cell is served by a neighbor device, the second apparatus 120 may receive from the neighbor device the assistance information of the neighbor cell and then transmit this information to the first apparatus 110.
[0090] In some example embodiments, the assistance information may be signaled to the first apparatus 110 in an inactive state on a MCCH and / or in a SIB. For example, the second apparatus 120 may include such information in a periodic MCCH (or SIB) .
[0091] In some example embodiments, the second apparatus 120 may provide the assistance information to the first apparatus 110 in a connection release message. For example, the second apparatus 120 may transmit this information in RRC release with suspendConfig when switching the first apparatus 110 from an RRC_CONNECTED state to an RRC_INACTIVE state.
[0092] Then, as shown in FIG. 3, the second apparatus 120 transmits (315) , to the first apparatus 110 in an inactive state, the first scheduling information based on the assistance information. Accordingly, the first apparatus 110 in the inactive state receives (320) the first scheduling information from the second apparatus 120 based on the assistance information.
[0093] In some example embodiments, the first apparatus 110 may further receive scheduling information (referred to as second scheduling information) for control information of the multicast service carried on a MCCH, by using a CFR (referred to as a second CFR) configured for the inactive state. The second scheduling information may comprise DCI or other scheduling information for the MCCH.
[0094] In this way, the first apparatus 110 in the inactive state may still use the second CFR configured for the MCCH in the calculations for reception of the MCCH. The assistance information related to the first CFR may be used only for reception of the first scheduling information for the MTCH, which may be scrambled via a G-RNTI or G-CS-RNTI, but not for reception of the second scheduling information for the MCCH which may be scrambled by a MCCH-RNTI. In this way, different CFR parameters may be used for the MCCH and MTCH, which is more flexible.
[0095] In some example embodiments, if the assistance information related to the first CFR is not received, the first apparatus 110 may by default use the second CFR configured for the inactive state to receive the first scheduling information for the multicast data in the inactive state. For example, if there is no signalling per TMGI or G (-CS) -RNTI for the assistance information, the first apparatus 110 may use the second CFR configured for the inactive state rather than the first CFR specific to the multicast service for calculating scheduling relevant parameters.
[0096] Thus, there may be two distinct CFRs of interest, including the first CRF and the second CFR. The first CFR may be a reference CFR of connected-mode UEs (or connected UEs) , whose scheduling DCI may be read by both the connected UEs and inactive-mode UEs (or inactive UEs) to acquire a main part of the scheduling for the MTCH. The second CFR may be a CFR shared by all the inactive UEs that may overlap or encompass the first CFR. With the supplying of the assistance information related to the first CFR to the inactive UEs, the inactive UEs may not misinterpret the first CFR given that some parameters of DCI for the connected UEs parameters are directly based on the first CFR. In some cases, the second CFR may be used instead of the first CFR for receiving the DCI for the MTCH.
[0097] FIG. 4 shows a signaling diagram for an example process 400 for multicast service provision according to some example embodiments of the present disclosure. In this example, a UE 405, labeled as UE1, is an example implementation of the first apparatus 110, a UE 410, labeled as UE2, is an example implementation of the third apparatus 130, and a gNB 415 serving a cell, labeled as Cell1, is an example implementation of the second apparatus 120.
[0098] As shown in FIG. 4, at 420, the UE 410 is in an RRC_CONNECTED state at Cell1. At 422, the UE 410 receives a multicast service, labeled as multicast service A. In Scenario 1, at 424, the UE 405 is in an RRC_INACTIVE state, moved from another cell to Cell1, e.g., reselected Cell1 to camp on from another cell that it was camping. At 426, the UE 405 reads MCCH information periodically transmitted on cell1 to receive the configurations needed for receiving multicast service A in RRC_INACTIVE state. Here, the MCCH information includes a configuration for assisting DCI calculations based on the first CFR for multicast service A (as an example implementation of the assistance information) . This configuration may comprise information per TMGI or G (-CS) -RNTI (identifying a multicast service) . This information may provide the UE 405 with the CFR relevant values to be used in DCI relevant calculations (and other calculations if needed) for MTCH receptions for that specific TMGI or G (-CS) -RNTI.
[0099] As shown in FIG. 4, in Option 1, the configuration may comprise a full configuration of a CFR (as an example implementation of the first CFR) used in an RRC_CONNECTED state. In Option 2, the configuration may be limited to a size and starting point of the CFR. As such, the configuration may contain only needed parameters for DCI calculations, i.e., only the size of the CFR and the starting point of the CFR. In Option 3, the configuration may comprise the parameters (e.g., the field size of DCI) normally calculated via the CFR, for example, based on the CFR relevant information.
[0100] In Scenario 2, at 428, the UE 405 is in an RRC_CONNECTED state, receiving multicast service A. In this scenario, the UE 405 is switched to an RRC_INACTIVE state while the UE 405 still receives multicast service A. As shown in FIG. 4, at 430, RRC release with suspendConfig is sent to the UE 405, which includes a configuration for assisting DCI calculations based on the first CFR for multicast service A. The implementations of the configuration are similar to those in Scenario 1, and details thereof will be omitted.
[0101] At 432, the UE 405 is in an RRC_INACTIVE state camping in Cell1. At 434, the UE 405 receives a periodic MCCH. At 436, the UE 405 still uses the CFR configured for the RRC_INACTIVE state when calculating the field size (s) and content of DCI scheduling the MCCH. The UE 405 does not use the newly received parameters for this purpose. At 438, the UE 405 receives DCI for multicast service A which is scrambled via G- (CS-) RNTI dedicated for the multicast service.
[0102] At 440, the UE 405 computes the field size (s) and content of the DCI that is scheduling the data of multicast service A, by using newly obtained configuration such as the parameters received in 426 or 430. The UE 405 does not use the common MCCH CFR when calculating these parameters. At 442, the UE 405 receives data for multicast service A. At 444, the UE 405 successfully receives the multicast service A, for example, via a PDSCH. In this way, both the UE 410 in the RRC_CONNECTED state and the UE 405 in the RRC_INACTIVE state can successfully receive multicast service A.
[0103] Example Methods
[0104] FIG. 5 shows a flowchart of an example method 500 in accordance with some example embodiments of the present disclosure. The method 500 can be implemented by the first apparatus 110 or the third apparatus 130 in FIG. 1. For the purpose of discussion, the method 500 will be described from the perspective of the first apparatus 110 with reference to FIG. 1.
[0105] At block 510, the first apparatus 110 receives, from the second apparatus 120, assistance information related to a first CFR. The first CFR is associated with first scheduling information for data of a multicast service, and the data of the multicast service is carried on a MTCH. In some example embodiments, the scheduling information comprises DCI. At block 520, the first apparatus 110 receives, in an inactive state, the first scheduling information based on the assistance information.
[0106] In some example embodiments, the assistance information may be received in the inactive state on a MCCH and / or in a SIB. In some example embodiments, the assistance information may be received in a connection release message. In some example embodiments, the assistance information is configured per at least one of a TMGI, a G-RNTI or a G-CS-RNTI.
[0107] In some example embodiments, the assistance information may comprise a configuration of the first CFR. In some example embodiments, the assistance information may comprise at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information. In some example embodiments, the at least one parameter of the configuration of the first CFR may comprise at least one of a size or a starting point of the first CFR.
[0108] In some example embodiments, the assistance information may comprise at least one parameter of the first scheduling information determined based on a configuration of the first CFR. In some example embodiments, the at least one parameter of the first scheduling information may comprise a size of a field of DCI. In some example embodiments, the field of DCI may comprise a FDRA field.
[0109] In some example embodiments, in response to no reception of the assistance information, the first apparatus 110 may receive, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service in the inactive state.
[0110] In some example embodiments, the first apparatus 110 may further receive, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service in the inactive state. The control information of the multicast service is carried on a MCCH.
[0111] FIG. 6 shows a flowchart of an example method 600 in accordance with some example embodiments of the present disclosure. The method 600 can be implemented by the second apparatus 120 in FIG. 1. For the purpose of discussion, the method 600 will be described from the perspective of the second apparatus 120 with reference to FIG. 1.
[0112] At block 610, the second apparatus 120 transmits, to the first apparatus 110, assistance information related to a first CFR. The first CFR is associated with first scheduling information for data of a multicast service, and the data of the multicast service is carried on a MTCH. At block 620, the second apparatus 120 transmits, to the first apparatus 10 in an inactive state, the first scheduling information based on the assistance information.
[0113] In some example embodiments, the assistance information may be transmitted to the first apparatus in the inactive state on a MCCH and / or in a SIB. In some example embodiments, the assistance information may be transmitted to the first apparatus in a connection release message.
[0114] In some example embodiments, the assistance information may comprise a configuration of the first CFR. In some example embodiments, the assistance information may comprise at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information. In some example embodiments, the at least one parameter of the configuration of the first CFR may comprise at least one of a size or a starting point of the first CFR.
[0115] In some example embodiments, the assistance information may comprise at least one parameter of the first scheduling information determined based on a configuration of the first CFR. In some example embodiments, the at least one parameter of the first scheduling information may comprise a size of a field of DCI. In some example embodiments, the field of DCI may comprise a FDRA field.
[0116] In some example embodiments, the assistance information may be configured per at least one of a TMGI, a G-RNTI or a G-CS-RNTI. In some example embodiments, the at least one of the TMFI, the G-RNTI, or the G-CS-RNTI may be associated with a neighbor cell of the first apparatus.
[0117] In some example embodiments, in response to no transmission of the assistance information, the second apparatus 120 may transmit, to the first apparatus 110 in the inactive state, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service.
[0118] In some example embodiments, the second apparatus 120 may further transmit, to the first apparatus 110 in the inactive state, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service, and the control information of the multicast service is carried on a MCCH.
[0119] All operations and features related to the first apparatus 110 and the second apparatus 120 as described above with reference to FIGS. 1 to 4 are likewise applicable to the methods 500 and 600 and have similar effects. For the purpose of simplification, the details will be omitted.
[0120] Example Apparatus, Device and Medium
[0121] In some example embodiments, a first apparatus capable of performing the method 500 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.
[0122] In some example embodiments, the first apparatus comprises means for receiving, from a second apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; and means for receiving, in an inactive state, the first scheduling information based on the assistance information.
[0123] In some example embodiments, the assistance information is received in the inactive state on a multicast control channel (MCCH) and / or in a system information block (SIB) .
[0124] In some example embodiments, the assistance information is received in a connection release message.
[0125] In some example embodiments, the assistance information comprises a configuration of the first CFR.
[0126] In some example embodiments, the assistance information comprises at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information.
[0127] In some example embodiments, the at least one parameter of the configuration of the first CFR comprises at least one of a size or a starting point of the first CFR.
[0128] In some example embodiments, the assistance information comprises at least one parameter of the first scheduling information determined based on a configuration of the first CFR.
[0129] In some example embodiments, the at least one parameter of the first scheduling information comprises a size of a field of downlink control information (DCI) .
[0130] In some example embodiments, the field of DCI comprises a frequency domain resource allocation (FDRA) field.
[0131] In some example embodiments, the assistance information is configured per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) .
[0132] In some example embodiments, the first apparatus further comprises: means for in response to no reception of the assistance information, receiving, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service in the inactive state.
[0133] In some example embodiments, the first apparatus further comprises: means for receiving, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service in the inactive state, wherein the control information of the multicast service is carried on a multicast control channel (MCCH) .
[0134] In some example embodiments, the scheduling information comprises downlink control information (DCI) .
[0135] In some example embodiments, the first apparatus further comprises means for performing other operations in some example embodiments of the method 500 or the first apparatus 110. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the first apparatus.
[0136] In some example embodiments, a second apparatus capable of performing the method 600 (for example, the second apparatus 120 in FIG. 1) may comprise means for performing the respective operations of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.
[0137] In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; and means for transmitting, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.
[0138] In some example embodiments, the assistance information is transmitted to the first apparatus in the inactive state on a multicast control channel (MCCH) and / or in a system information block (SIB) .
[0139] In some example embodiments, the assistance information is transmitted to the first apparatus in a connection release message.
[0140] In some example embodiments, the assistance information comprises a configuration of the first CFR.
[0141] In some example embodiments, the assistance information comprises at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information.
[0142] In some example embodiments, the at least one parameter of the configuration of the first CFR comprises at least one of a size or a starting point of the first CFR.
[0143] In some example embodiments, the assistance information comprises at least one parameter of the first scheduling information determined based on a configuration of the first CFR.
[0144] In some example embodiments, the at least one parameter of the first scheduling information comprises a size of a field of downlink control information (DCI) .
[0145] In some example embodiments, the field of DCI comprises a frequency domain resource allocation (FDRA) field.
[0146] In some example embodiments, the assistance information is configured per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) .
[0147] In some example embodiments, the at least one of the TMFI, the G-RNTI, or the G-CS-RNTI is associated with a neighbor cell of the first apparatus.
[0148] In some example embodiments, the second apparatus further comprises: means for in response to no transmission of the assistance information, transmitting, to the first apparatus in the inactive state, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service.
[0149] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus in the inactive state, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service, wherein the control information of the multicast service is carried on a multicast control channel (MCCH) .
[0150] In some example embodiments, the scheduling information comprises downlink control information (DCI) .
[0151] In some example embodiments, the second apparatus further comprises means for performing other operations in some example embodiments of the method 600 or the second apparatus 120. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the second apparatus.
[0152] FIG. 7 is a simplified block diagram of a device 700 that is suitable for implementing example embodiments of the present disclosure. The device 700 may be provided to implement a communication device, for example, the first apparatus 110 or the second apparatus 120 as shown in FIG. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.
[0153] The communication module 740 is for bidirectional communications. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.
[0154] The processor 710 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0155] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 724, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 722 and other volatile memories that will not last in the power-down duration.
[0156] A computer program 730 includes computer executable instructions that are executed by the associated processor 710. The instructions of the program 730 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 730 may be stored in the memory, e.g., the ROM 724. The processor 710 may perform any suitable actions and processing by loading the program 730 into the RAM 722.
[0157] The example embodiments of the present disclosure may be implemented by means of the program 730 so that the device 700 may perform any process of the disclosure as discussed with reference to FIG. 1 to FIG. 6. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0158] In some example embodiments, the program 730 may be tangibly contained in a computer readable medium which may be included in the device 700 (such as in the memory 720) or other storage devices that are accessible by the device 700. The device 700 may load the program 730 from the computer readable medium to the RAM 722 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0159] FIG. 8 shows an example of the computer readable medium 800 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 800 has the program 730 stored thereon.
[0160] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0161] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0162] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0163] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0164] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0165] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the sc ope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0166] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:receive, from a second apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; andreceive, in an inactive state, the first scheduling information based on the assistance information.2.The first apparatus of claim 1, wherein the assistance information is received in the inactive state on a multicast control channel (MCCH) and / or in a system information block (SIB) .3.The first apparatus of claim 1, wherein the assistance information is received in a connection release message.4.The first apparatus of any of claims 1-3, wherein the assistance information comprises a configuration of the first CFR.5.The first apparatus of any of claims 1-3, wherein the assistance information comprises at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information.6.The first apparatus of claim 5, wherein the at least one parameter of the configuration of the first CFR comprises at least one of a size or a starting point of the first CFR.7.The first apparatus of any of claims 1-3, wherein the assistance information comprises at least one parameter of the first scheduling information determined based on a configuration of the first CFR.8.The first apparatus of claim 7, wherein the at least one parameter of the first scheduling information comprises a size of a field of downlink control information (DCI) .9.The first apparatus of claim 8, wherein the field of DCI comprises a frequency domain resource allocation (FDRA) field.10.The first apparatus of any of claims 1-9, wherein the assistance information is configured per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) .11.The first apparatus of any of claims 1-10, wherein the at least one memory and the at least one processor further cause the first apparatus to:in response to no reception of the assistance information, receive, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service in the inactive state.12.The first apparatus of any of claims 1-11, wherein the at least one memory and the at least one processor further cause the first apparatus to:receive, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service in the inactive state, wherein the control information of the multicast service is carried on a multicast control channel (MCCH) .13.The first apparatus of any of claims 1-12, wherein the scheduling information comprises downlink control information (DCI) .14.A second apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to:transmit, to a first apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; andtransmit, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.15.The second apparatus of claim 14, wherein the assistance information is transmitted to the first apparatus in the inactive state on a multicast control channel (MCCH) and / or in a system information block (SIB) .16.The second apparatus of claim 14, wherein the assistance information is transmitted to the first apparatus in a connection release message.17.The second apparatus of any of claims 14-16, wherein the assistance information comprises a configuration of the first CFR.18.The second apparatus of any of claims 14-16, wherein the assistance information comprises at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information.19.The second apparatus of claim 18, wherein the at least one parameter of the configuration of the first CFR comprises at least one of a size or a starting point of the first CFR.20.The second apparatus of any of claims 14-16, wherein the assistance information comprises at least one parameter of the first scheduling information determined based on a configuration of the first CFR.21.The second apparatus of claim 20, wherein the at least one parameter of the first scheduling information comprises a size of a field of downlink control information (DCI) .22.The second apparatus of claim 21, wherein the field of DCI comprises a frequency domain resource allocation (FDRA) field.23.The second apparatus of any of claims 14-22, wherein the assistance information is configured per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) .24.The second apparatus of claim 23, wherein the at least one of the TMFI, the G-RNTI, or the G-CS-RNTI is associated with a neighbor cell of the first apparatus.25.The second apparatus of any of claims 14-24, wherein the at least one memory and the at least one processor further cause the second apparatus to:in response to no transmission of the assistance information, transmit, to the first apparatus in the inactive state, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service.26.The second apparatus of any of claims 14-25, wherein the at least one memory and the at least one processor further cause the second apparatus to:transmit, to the first apparatus in the inactive state, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service, wherein the control information of the multicast service is carried on a multicast control channel (MCCH) .27.The second apparatus of any of claims 14-26, wherein the scheduling information comprises downlink control information (DCI) .28.A method comprising:receiving, from a second apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; andreceiving, in an inactive state, the first scheduling information based on the assistance information.29.The method of claim 28, wherein the assistance information is received in the inactive state on a multicast control channel (MCCH) and / or in a system information block (SIB) .30.The method of claim 28, wherein the assistance information is received in a connection release message.31.The method of any of claims 28-30, wherein the assistance information comprises a configuration of the first CFR.32.The method of any of claims 28-30, wherein the assistance information comprises at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information.33.The method of claim 32, wherein the at least one parameter of the configuration of the first CFR comprises at least one of a size or a starting point of the first CFR.34.The method of any of claims 28-30, wherein the assistance information comprises at least one parameter of the first scheduling information determined based on a configuration of the first CFR.35.The method of claim 34, wherein the at least one parameter of the first scheduling information comprises a size of a field of downlink control information (DCI) .36.The method of claim 35, wherein the field of DCI comprises a frequency domain resource allocation (FDRA) field.37.The method of any of claims 28-36, wherein the assistance information is configured per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) .38.The method of any of claims 28-37, further comprising:in response to no reception of the assistance information, receiving, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service in the inactive state.39.The method of any of claims 28-38, further comprising:receiving, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service in the inactive state, wherein the control information of the multicast service is carried on a multicast control channel (MCCH) .40.The method of any of claims 28-39, wherein the scheduling information comprises downlink control information (DCI) .41.A method comprising:transmitting, to a first apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; andtransmitting, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.42.The method of claim 41, wherein the assistance information is transmitted to the first apparatus in the inactive state on a multicast control channel (MCCH) and / or in a system information block (SIB) .43.The method of claim 41, wherein the assistance information is transmitted to the first apparatus in a connection release message.44.The method of any of claims 41-43, wherein the assistance information comprises a configuration of the first CFR.45.The method of any of claims 41-43, wherein the assistance information comprises at least one parameter of the configuration of the first CFR used for determining at least one parameter of the first scheduling information.46.The method of claim 45, wherein the at least one parameter of the configuration of the first CFR comprises at least one of a size or a starting point of the first CFR.47.The method of any of claims 41-43, wherein the assistance information comprises at least one parameter of the first scheduling information determined based on a configuration of the first CFR.48.The method of claim 47, wherein the at least one parameter of the first scheduling information comprises a size of a field of downlink control information (DCI) .49.The method of claim 48, wherein the field of DCI comprises a frequency domain resource allocation (FDRA) field.50.The method of any of claims 41-49, wherein the assistance information is configured per at least one of a temporary mobile group identifier (TMGI) , a group radio network temporary identifier (G-RNTI) or a group configured scheduling RNTI (G-CS-RNTI) .51.The method of claim 50, wherein the at least one of the TMFI, the G-RNTI, or the G-CS-RNTI is associated with a neighbor cell of the first apparatus.52.The method of any of claims 41-51, further comprising:in response to no transmission of the assistance information, transmitting, to the first apparatus in the inactive state, based on a second CFR configured for the inactive state, the first scheduling information for the data of the multicast service.53.The method of any of claims 41-52, further comprising:transmitting, to the first apparatus in the inactive state, based on a second CFR configured for the inactive state, second scheduling information for control information of the multicast service, wherein the control information of the multicast service is carried on a multicast control channel (MCCH) .54.The method of any of claims 41-53, wherein the scheduling information comprises downlink control information (DCI) .55.A first apparatus comprising:means for receiving, from a second apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; andmeans for receiving, in an inactive state, the first scheduling information based on the assistance information.56.A second apparatus comprising:means for transmitting, to a first apparatus, assistance information related to a first common frequency resource (CFR) , the first CFR being associated with first scheduling information for data of a multicast service, wherein the data of the multicast service is carried on a multicast traffic channel (MTCH) ; andmeans for transmitting, to the first apparatus in an inactive state, the first scheduling information based on the assistance information.57.A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of any of claims 28-40 or the method of any of claims 41-54.
Citation Information
Patent Citations
Techniques for indicating downlink control information in multicast / broadcast wireless communications
CN115039371A
Downlink size estimation for multicast traffic
US20230060839A1
Frequency resource allocation for multicast and broadcast services
WO2022081996A1
Frequency domain resource allocation for multicast traffic
WO2022082661A1
Method and apparatus for resource allocation and operation in a wirless communication system supporting unicast and multicast / broadcast service
WO2022145908A1
