Time domain resource allocation for multicast broadcast services

Abstract

Embodiments of the present disclosure relate to time domain resource allocation for multicast broadcast services. A first device receives, from a second device, a DCI including a TDRA field, and determines a TDRA list from a configured set of TDRAs based on at least one of an identifier used to scramble the DCI, an RRC state of the first device, or a type of traffic configured for the first device. The first device then applies the TDRA field based on the TDRA list to receive traffic from the second device. In this way, the TDRA list to be used can be determined in an optimal manner, where all terminal devices receiving multicast and broadcast traffic determine a common value of time domain resources that will schedule data traffic.

Description

Technical Field

[0001] This disclosure generally relates to the telecommunications field, and more particularly to communication methods, apparatus, and computer-readable storage media for time-domain resource allocation (TDRA) for multicast broadcast services (MBS). Background Technology

[0002] With the development of New Radio (NR) multicast technology, the 3rd Generation Partnership Project (3GPP) is currently defining mechanisms to enable the delivery of multicast and / or broadcast services to multiple terminal devices. A key objective is to define a group scheduling mechanism that allows the use of common data channel resources to schedule multicast and / or broadcast services while maintaining maximum commonality with currently defined unicast scheduling and operation mechanisms.

[0003] The current consensus is that downlink control information (DCI) formats 1_0 and 1_1, used for scheduling unicast services, can be used as the baseline for scheduling physical downlink shared channel (PDSCH) resources for multicast services. The TDRA field in the DCI informs the terminal device which field from a predefined set of TDRA lists should be applied. For NR MBS, further research is needed on how to apply appropriate configuration to determine which TDRA list to utilize. Summary of the Invention

[0004] Generally, the exemplary embodiments of this disclosure provide a scheme for enabling a terminal device to select an applicable time-domain resource allocation table for MBS.

[0005] In a first aspect, a first device is provided. The first device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured, together with the at least one processor, to cause the first device to: receive downlink control information including a time-domain resource allocation field from a second device; determine a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier for scrambling the downlink control information, a radio resource control state of the first device, or a type of service configured for the first device; and apply the time-domain resource allocation field based on the time-domain resource allocation list to receive a service from the second device.

[0006] In a second aspect, a second device is provided. The second device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured, together with the at least one processor, to cause the second device to: transmit downlink control information including a time-domain resource allocation field to a first device; determine a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier for scrambling the downlink control information, a radio resource control state of the first device, or a type of service configured for the first device; and apply the time-domain resource allocation field based on the time-domain resource allocation list to transmit a service to the first device.

[0007] In a third aspect, a communication method is provided. The method includes: receiving downlink control information, including a time-domain resource allocation field, from a second device at a first device; determining a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier used to scramble the downlink control information, a radio resource control state of the first device, or a type of service configured for the first device; and applying the time-domain resource allocation field based on the time-domain resource allocation list to receive a service from the second device.

[0008] In a fourth aspect, a communication method is provided. The method includes: sending downlink control information, including a time-domain resource allocation field, from a second device to a first device; determining a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier used to scramble the downlink control information, a radio resource control state of the first device, or a type of service configured for the first device; and applying the time-domain resource allocation field based on the time-domain resource allocation list to send a service to the first device.

[0009] In a fifth aspect, a communication apparatus is provided. The communication apparatus includes: components for receiving downlink control information, including a time-domain resource allocation field, from a first device to a second device; components for determining a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier used to scramble the downlink control information, a radio resource control state of the first device, or a type of service configured for the first device; and components for applying the time-domain resource allocation field based on the time-domain resource allocation list to receive a service from the second device.

[0010] In a sixth aspect, a communication apparatus is provided. The apparatus includes: components for transmitting downlink control information, including a time-domain resource allocation field, from a second device to a first device; components for determining a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier used to scramble the downlink control information, a radio resource control state of the first device, or a type of service configured for the first device; and components for applying the time-domain resource allocation field to the time-domain resource allocation list to transmit a service to the first device.

[0011] In a seventh aspect, a non-transient computer-readable medium is provided. This non-transient computer-readable medium includes program instructions for causing a device to execute the method according to the third aspect.

[0012] In an eighth aspect, a non-transient computer-readable medium is provided. This non-transient computer-readable medium includes program instructions for causing a device to execute the method according to the fourth aspect.

[0013] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0014] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0015] Figure 1 An example communication network in which an example embodiment of this disclosure can be implemented is shown;

[0016] Figure 2 A diagram illustrating a communication process according to some embodiments of the present disclosure is shown;

[0017] Figure 3A A flowchart illustrating a method for determining a list of TDRAs according to an exemplary embodiment of this disclosure is shown;

[0018] Figure 3B A flowchart illustrating another method for determining a list of TDRAs according to an exemplary embodiment of this disclosure is shown;

[0019] Figure 3C A flowchart illustrating yet another method for determining a list of TDRAs according to an exemplary embodiment of this disclosure is shown;

[0020] Figure 4 A flowchart illustrating a communication method implemented at a first device according to an exemplary embodiment of the present disclosure is shown;

[0021] Figure 5A flowchart illustrating a communication method implemented at a second device according to an exemplary embodiment of the present disclosure is shown;

[0022] Figure 6 A simplified block diagram of an apparatus suitable for implementing exemplary embodiments of the present disclosure is shown; and

[0023] Figure 7 A block diagram of an example computer-readable medium according to an example embodiment of the present disclosure is shown.

[0024] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0025] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of the disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0026] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0027] In this disclosure, references to "an embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments (whether explicitly described or not) to affect such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0028] It should be understood that while the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0029] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “comprising,” “including,” “having,” “containing,” and / or “comprising” as used herein specify the presence of the stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0030] In this application, the term "circuit" may refer to one or more or all of the following:

[0031] (a) Hardware circuit implementation only (e.g., implemented only in analog and / or digital circuits) and

[0032] (b) A combination of hardware circuitry and software, such as (if applicable):

[0033] (i) A combination of analog and / or digital hardware circuitry with software / firmware, and

[0034] (ii) Any part of a hardware processor, software, and memory that has software (including a digital signal processor), which works together to enable a device (such as a mobile phone or server) to perform various functions, and

[0035] (c) Hardware circuitry and / or processors, such as microprocessors or a portion thereof, which require software (e.g. firmware) to operate, but the software may be absent when it is not required for operation.

[0036] The definition of "circuit" applies to all uses of the term in this application, including any claim. As a further example, as used in this application, the term "circuit" also includes implementations of hardware circuitry or processors (or processors) or a portion thereof and their accompanying software and / or firmware. The term "circuit" also covers (e.g., and if applicable to a particular claim element) baseband integrated circuits or processor integrated circuits in mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0037] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as fifth-generation (5G) systems, fifth-generation advanced (5G-Advanced) systems, Long Term Evolution (LTE), LTE-A, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), New Radio (NR) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communication, there are, of course, future types of communication technologies and systems that can be used to implement this disclosure. This should not be construed as limiting the scope of the invention to the systems described above.

[0038] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR next-generation Node B (gNB), remote radio unit (RRU), radio header (RH), remote radio header (RRH), relays, and low-power nodes such as femtoseconds and picoseconds. The RAN split architecture includes a gNB CU (centralized unit, carrying RRC, SDAP, and PDCP) that controls multiple gNB DUs (distributed units, carrying RLC, MAC, and PHY). Relay nodes can correspond to the DU portion of an IAB node.

[0039] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), mobile device, subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment", "communication equipment", "terminal", "user equipment" and "UE" are used interchangeably.

[0040] As used herein, the term "multicast service" means a service transmitted to a group of users interested in receiving the service, and also means data transmitted over the air and received by all users interested in receiving the service. In other words, the term "multicast service" as used herein can also encompass both multicast and broadcast services. In the following description, the terms "multicast service," "multicast service," "broadcast service," "broadcast service," and "multicast broadcast service (MBS)" are used interchangeably.

[0041] As is known, DCI formats 1_0, 1_1, and 1_2 are used by network devices to inform terminal devices about the PDSCH resources to which downlink data will be scheduled. These formats are currently defined for unicast services, meaning that network devices will utilize any of these DCI formats to inform terminal devices about upcoming downlink information scheduled on the PDSCH using the Physical Downlink Control Channel (PDCCH) dedicated to terminal devices. As mentioned above, it is agreed that DCI formats 1_0 and 1_1 can be used as a baseline for scheduling PDSCH resources for multicast services, where a common identifier (called the Group Public Radio Network Temporary Identifier (G-RNTI)) is used to scramble the control information. This allows a group of users to receive downlink control information.

[0042] In this scenario, network devices will use group common PDCCH resources to transmit DCI, which has Cyclic Redundancy Check (CRC) scrambled using group common RNTI values ​​that may be configured by higher layers. These PDCCH resources will be configured using a new type of search space set (dedicated to scheduling control information for multicast and / or broadcast traffic). This search space set is referred to as Type-X, Type-3A, or multicast or broadcast search space set.

[0043] The TDRA field in DCI informs the terminal device which field from a predefined set of TDRA lists should be applied. Based on certain priorities, different higher-level configurations, such as PDSCH Configuration (PDSCH-Config) or PDSCH Common Configuration (PDSCH-ConfigCommon), are applied to calculate which TDRA list the terminal device should use to interpret the TDRA field. For NR MBS, the higher-level configuration PDSCH Multicast Configuration (PDSCH-Config-Multicast) is expected to be applied.

[0044] However, PDSCH-Config-Multicast is a parameter configured using RRC once the terminal device establishes an RRC connection with the network device. For terminal devices in an idle or inactive state, such configuration is not currently provided because the terminal device does not have an active RRC connection with the network device. This leads to a problem with the Type-X Common Search Space (CSS) as shown in Table 1, where if the UE is simultaneously configured with multicast and broadcast services with two different G-RNTIs, the UE cannot select the TDRA table (also referred to herein as the TDRA list) applicable to the multicast and broadcast DCIs.

[0045] Table 1 lists the issues in the allocation of applicable PDSCH time-domain resources for DCI formats 1_0 and 1_1.

[0046]

[0047]

[0048] Currently, Type-X CSS is a new common search space defined for broadcast and multicast. For multicast, it is agreed that Type-X CSS is supported for the CSS of group common PDCCH in Point-to-Multipoint (PTM) scheme 1, where the group common PDCCH is used to schedule group common PDSCH for multicast in the RRC_CONNECTED state. The monitoring priority of Type-X CSS is determined based on the search space set index of the Type-X CSS set and the UE-specific search space (USS) set, regardless of which DCI format group common PDCCH is configured in the Type-X CSS.

[0049] As shown in Table 1 for Type-X CSS, the problem to be solved is: how to use G-RNTI to identify the appropriate TDRA list to be used for interpreting TDRA fields in DCI while simultaneously receiving multicast and broadcast services. Currently, the UE can use Scheme 1 or Scheme 2 shown in the table. Based on the currently proposed specification update, without configuring PDSCH-Config-Multicast, a terminal device in a connected state receiving multicast / unicast and broadcast services may utilize the TDRA list provided in PDSCH-Config, but a terminal device receiving only broadcast services will utilize the TDRA list provided in PDSCH-ConfigCommon, resulting in the use of two different TDRA tables, which in turn leads to incorrect interpretation of the TDRA fields received in DCI.

[0050] In view of this, embodiments of this disclosure provide an improved communication scheme. In this scheme, a TDRA list is determined from a TDRA configuration set based on the identifier used for scrambling DCI, the RRC status of the terminal device, and the service type configured for the terminal device. Then, the TDRA fields in the DCI within the TDRA list are applied to determine the time-domain resources used for service transmission or reception. This allows terminal devices in a connected state receiving multicast / unicast and broadcast services, as well as terminal devices receiving only broadcast services, to interpret the common TDRA list to be used. Therefore, significant flexibility in scheduling MBS can be provided with optimal time-domain resource allocation capabilities, and a significant reduction in complexity can be offered to the terminal devices.

[0051] The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings.

[0052] Examples of communication networks

[0053] Figure 1 An example communication network 100 in which embodiments of this disclosure can be implemented is shown. For example... Figure 1As shown, network 100 includes a first device 110 and a second device 120 serving the first device 110. It should be understood that... Figure 1 The number of first and second devices shown is for illustrative purposes only and does not imply any limitation. Network 100 may include any suitable number of first and second devices appropriate for implementing embodiments of this disclosure. In some embodiments, first device 110 may be a terminal device and second device 120 may be a network device.

[0054] For illustrative purposes only and without limiting the scope of this disclosure, some embodiments will be described in the context that the first device 110 is a terminal device and the second device 120 is a network device. It should be understood that in other embodiments, the first device 110 may be a network device, and the second device 120 may be a terminal device. In other words, the principles and spirit of this disclosure can be applied to both uplink and downlink transmissions.

[0055] like Figure 1 As shown, the first device 110 and the second device 120 can communicate with each other via a wireless communication channel. Communication within network 100 can conform to any suitable standard, including but not limited to LTE, LTE Evolution, LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM). Furthermore, communication can be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), or sixth-generation (6G) communication protocols.

[0056] In some scenarios, the second device 120 can send any of the following types of services to the first device 110: multicast, unicast, and broadcast. For example, the second device 120 can send both broadcast and multicast services to the first device 110. In some cases, the second device 120 can send a DCI (Digital Currency Information) to the first device 110 to schedule services. The DCI may include a TDRA (Time Domain Relationship) field. The first device 110 can interpret the TDRA field to determine time domain resources and receive services based on those resources.

[0057] This disclosure provides a mechanism for applying or interpreting TDRA fields in a suitable TDRA list, enabling terminal devices receiving different types of services to have a common understanding of TDRA fields. This mechanism of the present disclosure... Figure 2 The advanced flowchart shown is illustrated.

[0058] Example implementation of interpreting TDRA fields

[0059] Figure 2 A flowchart illustrating a communication process 200 according to some embodiments of the present disclosure is shown. For convenience, it will be combined with... Figure 1 Examples to describe Figure 2 .

[0060] like Figure 2 As shown, the second device 120 can send a configuration set 210 for TDRA to the first device 110. In some embodiments, this configuration set can be a set of higher-level configurations, such as an RRC configuration set. Of course, any other suitable form is also possible. In some embodiments, the configuration set may include at least one of the following: PDSCH-Config-Multicast configuration, PDSCH-ConfigCommon configuration, PDSCH-Config configuration, default A table, default B table, or default C table. It should be understood that any other suitable configuration, whether existing or developed in the future, is also possible.

[0061] Each configuration includes a predefined list of TDRAs. For example, the PDSCH-config-multicast configuration includes a PDSCH time domain allocation list (pdsch-TimeDomainAllocationList-Multicast) for multicast. The PDSCH-Config-Broadcast configuration includes a PDSCH time domain allocation list (pdsch-TimeDomainAllocationList-Broadcast) for broadcasting. The PDSCH-Config configuration includes a PDSCH time domain allocation list (pdsch-TimeDomainAllocationList). Of course, any other suitable form is also possible.

[0062] When a service is to be transmitted, the second device 120 sends a DCI including the TDRA field to the first device 110. It should be understood that the DCI may include any suitable additional fields, and this disclosure does not limit this aspect.

[0063] Upon receiving the DCI, the first device 110 determines a 230TDRA list from the configuration set for TDRA based on at least one of the following: the identifier used to scramble the DCI, the RRC status of the first device 110, or the service type configured for the first device. In this way, different devices configured to receive different types of services have a common understanding of the TDRA fields used for multicast and broadcast.

[0064] In some embodiments, the search space set type can be configured to send DCI along with the identifier used for scrambling DCI.

[0065] In some embodiments, the identifier used for scrambling DCI can be an identifier of the CRC used for scrambling DCI. For example, the identifier can be a Radio Network Temporary Identifier (RNTI), such as a Cell RNTI (C-RNTI), a Group RNTI (G-RNTI), a Group Common Configuration Scheduling RNTI (G-CS-RNTI), or a Single Cell RNTI (SC-RNTI). It should be understood that these are merely examples, and any other suitable identifier is also possible.

[0066] In some embodiments, the RRC state of the first device 110 may be a connected state, such as the RRC_CONNECTED state or mode. In some embodiments, the RRC state of the first device 110 may be an idle state, such as the RRC_IDLE state or mode. In some embodiments, the RRC state of the first device 110 may be an inactive state, such as the RRC_INACTIVE state or mode.

[0067] In some embodiments, the service type may be at least one of multicast service, broadcast service, or unicast service.

[0068] After determining the TDRA list, the first device 110 applies the 240TDRA field based on the TDRA list to determine the time-domain resources used for receiving services. The application of the TDRA field can be implemented in any suitable manner, and this disclosure is not limiting in this respect.

[0069] like Figure 2 As shown, after sending the DCI, the second device 120 further determines a 250TDRA list from the configuration set based on at least one of the following: the identifier used to scramble the DCI, the RRC status of the first device 110, or the service type configured for the first device 110. The operation of determining 250 is similar to the operation of determining 230.

[0070] After determining the TDRA list, the second device 120 also applies the TDRA field 260 based on the TDRA list to determine the time-domain resources used for service transmission. The application of 260 is similar to the application of 240. The application of the TDRA field can be implemented in any suitable manner, and this disclosure does not limit this aspect.

[0071] For the sake of illustration, some example embodiments for determining the TDRA list will be described in conjunction with Examples 1 to 3.

[0072] Example 1

[0073] In this embodiment, the TDRA list is determined based on the identifier used for scrambling DCI, the radio resource control status of the first device 110, or the service type configured for the first device 110. This will refer to... Figure 3ADescribe it.

[0074] Figure 3A A flowchart illustrating a method 300A for determining a list of TDRAs according to an exemplary embodiment of this disclosure is shown. Method 300A can be performed in... Figure 1 This is implemented at either the first device 110 or the second device 120 shown. For the purposes of discussion, it will be combined with... Figure 1 Method 300A is described using the first device 110. It should be understood that method 300A may also be implemented at the second device 120. It should also be understood that method 300A may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0075] like Figure 3A As shown, in block 301, the first device 110 can determine whether it is in a connected state. If the first device 110 is in a connected state, the process proceeds to block 302.

[0076] In block 302, the first device 110 may determine whether the service type is at least broadcast and multicast. For example, the first device 110 may determine whether it is configured to receive broadcast and multicast services. In another example, the first device 110 may determine whether it is configured to receive broadcast, multicast, and unicast services. If the service type is broadcast and multicast, or if the service type is broadcast, multicast, and unicast, then process 300A proceeds to block 303.

[0077] In box 303, the first device 110 can determine whether the PDSCH-Config-Multicast configuration (also referred to herein as the first configuration for convenience) is configured for the first device 110. If the PDSCH-Config-Multicast configuration is configured, process 300A proceeds to box 304.

[0078] In block 304, the first device 110 can determine whether the identifier is a predetermined identifier. In other words, the first device 110 can determine whether the DCI is scrambled by the predetermined identifier. For example, the first device 110 can determine whether the CRC of the DCI is scrambled by the predetermined identifier. In some embodiments, the predetermined identifier may be G-RNTI. In some embodiments, the predetermined identifier may be G-CS-RNTI. Of course, the predetermined identifier may take any other suitable form.

[0079] If the identifier is a predefined identifier, process 300A proceeds to block 305. In block 305, the first device 110 can determine the TDRA list from the PDSCH-Config-Multicast configuration. For example, the first device 110 can determine the TDRA list as such as the pdsch-TimeDomainAllocationList-Multicast provided in the PDSCH-Config-Multicast configuration.

[0080] Returning to box 303, if it is determined that the PDSCH-Config-Multicast configuration is not configured, process 300A proceeds to box 306. In box 306, the first device 110 can determine whether the PDSCH-Config-Common configuration (also referred to herein as the second configuration for convenience) is configured for the first device 110. If PDSCH-Config-Common is configured, process 300A proceeds to box 307.

[0081] In block 307, the first device 110 can determine whether the identifier is a predetermined identifier. In other words, the first device 110 can determine whether the DCI is scrambled by the predetermined identifier. For example, the first device 110 can determine whether the CRC of the DCI is scrambled by the predetermined identifier. In some embodiments, the predetermined identifier may be G-RNTI. In some embodiments, the predetermined identifier may be G-CS-RNTI. Of course, the predetermined identifier may take any other suitable form.

[0082] If the identifier is a predefined identifier, process 300A proceeds to box 308. At box 308, the first device 110 can determine the TDRA list from the PDSCH-Config-Common configuration.

[0083] Returning to box 306, if it is determined that the PDSCH-Config-Common configuration is not configured, process 300A proceeds to box 309. In box 309, the first device 110 can determine whether the identifier is a predetermined identifier. In other words, the first device 110 can determine whether the DCI is scrambled by a predetermined identifier. For example, the first device 110 can determine whether the CRC of the DCI is scrambled by a predetermined identifier. In some embodiments, the predetermined identifier may be G-RNTI. In some embodiments, the predetermined identifier may be G-CS-RNTI. Of course, the predetermined identifier can take any other suitable form.

[0084] If the identifier is a predetermined identifier, then process 300A proceeds to block 310. In block 310, the first device 110 can determine whether the predetermined identifier is associated with a multicast service or a broadcast service.

[0085] If the predefined identifier is associated with a multicast service, process 300A proceeds to box 311. In box 311, the first device 110 can determine the TDRA list from the default A table (also referred to herein as the third configuration for convenience).

[0086] If the predefined identifier is associated with a broadcast service, process 300A proceeds to block 312. In block 312, the first device 110 can determine the TDRA list from the set of default A, B, and C tables (also referred to herein as the fourth configuration for convenience) based on the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block and Control Resource Set (CORESET) multiplexing mode. For example, the first device 110 can determine the TDRA list from the default A, B, or C table based on the SS / PBCH block and CORESET multiplexing mode.

[0087] Example 2

[0088] This embodiment is a variation of Embodiment 1. This embodiment provides... Figure 3A Alternatives to boxes 306 to 312. In this embodiment, the first device 110 may receive an indication from the second device 120 indicating whether the PDSCH-Config-Common configuration (i.e., the second configuration) or the PDSCH-Config configuration (also referred to herein as the fifth configuration for convenience) is used for determining the TDRA list. This indication may be implemented in any suitable form.

[0089] Reference Figure 3B Details of this embodiment are described below. Figure 3B A flowchart illustrating another method 300B for determining a list of TDRAs according to an exemplary embodiment of this disclosure is shown. Method 300B can be performed in... Figure 1 This is implemented at either the first device 110 or the second device 120 shown. For the purposes of discussion, it will be combined with... Figure 1 Method 300B is described using the first device 110. It should be understood that method 300B may also be implemented at the second device 120. It should also be understood that method 300B may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0090] If in Figure 3A If it is determined at box 303 that PDSCH-Config-Multicast (i.e., the first configuration) is not configured, then process 300B can begin.

[0091] like Figure 3BAs shown, in block 320, the first device 110 can determine whether to use PDSCH-Config-Common configuration or PDSCH-Config configuration based on this instruction. If PDSCH-Config-Common configuration is used, process 300B proceeds to block 321.

[0092] In block 321, the first device 110 can determine whether the identifier is a predetermined identifier. In other words, the first device 110 can determine whether the DCI is scrambled by the predetermined identifier. For example, the first device 110 can determine whether the CRC of the DCI is scrambled by the predetermined identifier. In some embodiments, the predetermined identifier may be G-RNTI. In some embodiments, the predetermined identifier may be G-CS-RNTI. Of course, the predetermined identifier may take any other suitable form. In some embodiments, the predetermined identifier may be associated with a multicast service. In some embodiments, the predetermined identifier may be associated with a broadcast service.

[0093] If the identifier is a predefined identifier, then process 300B proceeds to block 322. In block 322, the first device 110 can determine the TDRA list from the PDSCH-Config-Common configuration. In other words, if the first device 110 is not configured with a PDSCH-Config-Multicast configuration, then the first device 110 can apply the TDRA list provided in the PDSCH-Config-Common configuration and apply it only to DCIs that have CRCs scrambled using G-RNTI or G-CS-RNTI for multicast and broadcast.

[0094] Returning to box 320, if it is determined that the PDSCH-Config configuration is used, process 300B proceeds to box 323. In box 323, the first device 110 can determine whether the identifier is a predetermined identifier. In other words, the first device 110 can determine whether the DCI is scrambled by a predetermined identifier. For example, the first device 110 can determine whether the CRC of the DCI is scrambled by a predetermined identifier. In some embodiments, the predetermined identifier may be G-RNTI. In some embodiments, the predetermined identifier may be G-CS-RNTI. Of course, the predetermined identifier can take any other suitable form.

[0095] If the identifier is a predetermined identifier, process 300B proceeds to block 324. In block 324, the first device 110 can determine the TDRA list from the PDSCH configuration. In other words, if the first device 110 is not configured with a PDSCH-Config-Multicast configuration, the first device 110 can apply the TDRA list provided in the PDSCH-Config configuration and only apply it to those DCIs that have CRCs scrambled using G-RNTI or G-CS-RNTI for multicast and broadcast. In some embodiments, the predetermined identifier may be associated with multicast services. In some embodiments, the predetermined identifier may be associated with broadcast services.

[0096] In this way, the list of TDRAs to be used can be determined in the best way, where all UEs receiving multicast and broadcast services determine common values ​​for the time-domain resources for which data services will be scheduled.

[0097] Example 3

[0098] This embodiment is another variation of Embodiment 1. This embodiment provides Figure 3A Alternative options for boxes 304 to 305. (Refer to...) Figure 3C Details of this embodiment are described below.

[0099] Figure 3C A flowchart illustrating yet another method 300C for determining a list of TDRAs according to an exemplary embodiment of this disclosure is shown. Method 300C can be... Figure 1 This is implemented at either the first device 110 or the second device 120 shown. For the purposes of discussion, it will be combined with... Figure 1 Method 300C is described using the first device 110. It should be understood that method 300C may also be implemented at the second device 120. It should also be understood that method 300C may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0100] If in Figure 3A Once it is confirmed at box 303 that the PDSCH-Config-Multicast configuration (i.e., the first configuration) is configured, process 300C can begin.

[0101] like Figure 3C As shown, in block 330, the first device 110 can determine whether the identifier is a predetermined identifier. In other words, the first device 110 can determine whether the DCI is scrambled by the predetermined identifier. For example, the first device 110 can determine whether the CRC of the DCI is scrambled by the predetermined identifier. In some embodiments, the predetermined identifier may be G-RNTI. In some embodiments, the predetermined identifier may be G-CS-RNTI. Of course, the predetermined identifier may take any other suitable form.

[0102] If the identifier is a predetermined identifier, process 300C proceeds to block 331. At block 331, the first device 110 can determine whether the predetermined identifier is associated with a multicast service or a broadcast service.

[0103] If the predefined identifier is associated with a multicast service, process 300C proceeds to box 332. In box 332, the first device 110 can determine the list of TDRAs from the PDSCH-Config-Multicast configuration.

[0104] Returning to box 331, if the predefined identifier is associated with a broadcast service, process 300C proceeds to box 333. In box 333, the first device 110 can determine whether the PDSCH-Config-Broadcast configuration (also referred to herein as the sixth configuration for convenience) is configured.

[0105] If the PDSCH-Config-Broadcast configuration is configured, process 300C proceeds to box 334. In box 334, the first device 110 can determine the TDRA list from the PDSCH-Config-Broadcast configuration.

[0106] Returning to block 333, if it is determined that the PDSCH-Config-Broadcast configuration is not configured, process 300C proceeds to block 335. In block 335, the first device 110 can determine whether the PDSCH-Config-Common configuration (i.e., the second configuration) is configured.

[0107] If the PDSCH-Config-Common configuration is configured, process 300C proceeds to box 336. In box 336, the first device 110 can determine the TDRA list from the PDSCH-Config-Common configuration.

[0108] If it is determined at box 335 that the PDSCH-Config-Common configuration is not configured, process 300C proceeds to box 337. At box 337, the first device 110 can determine the TDRA list from the set of default A, B, and C tables (i.e., the fourth configuration) based on the SS / PBCH block and CORESET multiplexing mode. For example, the first device 110 can determine the TDRA list from the default A, B, or C table based on the SS / PBCH block and CORESET multiplexing mode.

[0109] In this way, the list of TDRAs to be used can be determined in the best way, where all UEs receiving multicast and broadcast services determine common values ​​for the time-domain resources for which data services will be scheduled.

[0110] According to embodiments of this disclosure, Table 1 can be updated to Table 2 below.

[0111] Table 2 shows examples of applicable PDSCH time-domain resource allocations for DCI formats 1_0 and 1_1.

[0112]

[0113]

[0114]

[0115] Example implementation of the method

[0116] Corresponding to Figures 2 to 3C The above-described process is described in the present disclosure, which provides a communication method implemented at a first device and a second device. The following will refer to... Figures 4 to 5 These methods are described. However, those skilled in the art will readily understand that the detailed descriptions given herein with respect to these figures are for illustrative purposes, as this disclosure extends beyond these limited embodiments.

[0117] Figure 4 A flowchart is shown of a communication method 400 implemented at a first device according to an exemplary embodiment of the present disclosure. Method 400 can be implemented in... Figure 1 The first device 110 shown is implemented here. For the purposes of discussion, reference will be made to... Figure 1 Method 400 is described. It should be understood that method 400 may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0118] like Figure 4 As shown in box 410, the first device 110 receives a DCI including the TDRA field from the second device 120.

[0119] In box 420, the first device 110 determines a list of TDRAs from a set of configurations for TDRAs based on at least one of an identifier used for scrambling DCI, an RRC of the first device 110, or a service type configured for the first device 110.

[0120] In some embodiments, the RRC state of the first device 110 may be one of a connected state, an idle state, and an inactive state. In some embodiments, the service type is at least one of a broadcast service, a multicast service, or a unicast service.

[0121] In some embodiments, if the first device 110 is in a connected state and the service type is at least broadcast and multicast service, the first device 110 can determine whether a first configuration (e.g., PDSCH-Config-Multicast configuration) is configured for the first device 110. If the first configuration is configured for the first device 110, the first device 110 can determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the first device 110 can determine a list of TDRs from the first configuration.

[0122] In some embodiments, if the first configuration is not configured for the first device 110, the first device 110 may determine whether a second configuration (e.g., the PDSCH-Config-Common configuration) is configured for the first device 110. If the second configuration is configured for the first device 110, the first device 110 may determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the first device 110 may determine a list of TDRAs from the second configuration.

[0123] In some embodiments, if the second configuration is not configured for the first device 110, the first device 110 may determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the first device 110 may determine whether the predetermined identifier is associated with a multicast service or a broadcast service. If the predetermined identifier is associated with a multicast service, the first device 110 may determine the TDRA list from a third configuration (e.g., the default A table). If the predetermined identifier is associated with a broadcast service, the first device 110 may determine the TDRA list from a fourth configuration (e.g., a set of default A, B, and C tables) based on the SS / PBCH block and CORESET multiplexing mode.

[0124] In some embodiments, the first device 110 may receive an indication from the second device 120, the indication being used to indicate whether a second configuration (e.g., PDSCH-Config-Common configuration) or a fifth configuration (e.g., PDSCH-Config configuration) is used to determine the TDRA list.

[0125] In these embodiments, if the first configuration is not configured for the first device 110, the first device 110 can determine whether to use the second or fourth configuration based on the indication. If the second configuration is used, the first device 110 can determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the first device 110 can determine the TDRA list from the second configuration. In some embodiments, if the fifth configuration is used, the first device 110 can determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the first device 110 can determine the TDRA list from the fifth configuration.

[0126] In some embodiments, if the first device 110 is in a connected state and the service type is at least broadcast and multicast service, the first device 110 can determine that a first configuration (e.g., PDSCH-Config-Multicast configuration) is configured for the first device 110. If the first configuration is configured for the first device 110, the first device 110 can determine whether an identifier is a predetermined identifier. If the identifier is a predetermined identifier, the first device 110 can determine whether the predetermined identifier is associated with a multicast service or a broadcast service. If the predetermined identifier is associated with a multicast service, the first device 110 can determine a list of TDRs from the first configuration. If the predetermined identifier is associated with a broadcast service, the first device 110 can determine whether a sixth configuration (e.g., PDSCH-Config-Broadcast configuration) is configured for the first device 110. If the sixth configuration is configured for the first device 110, the first device 110 can determine a list of TDRs from the sixth configuration.

[0127] In some embodiments, if a sixth configuration is not configured for the first device 110, the first device 120 may determine whether a second configuration is configured for the first device 110. If the second configuration is configured for the first device 110, the first device 110 may determine a list of TDRAs from the second configuration. If the second configuration is not configured for the first device 110, the first device 110 may determine a list of TDRAs from a fourth configuration (e.g., a set of default A, B, and C tables) based on the SS / PBCH block and CORESET multiplexing mode.

[0128] After determining the TDRA list, in box 430, the first device 110 applies the TDRA field based on the TDRA list to receive services from the second device 120.

[0129] Using method 400, terminal devices in a connected state that receive multicast / unicast and broadcast services, as well as terminal devices that only receive broadcast services, can decode the public TDR list to be used. Therefore, a significant reduction in the complexity of the terminal devices can be provided.

[0130] Accordingly, this disclosure also provides a communication method implemented at a second device. Figure 5 A flowchart is shown of a communication method 500 implemented at a second device according to an exemplary embodiment of this disclosure. Method 500 can be implemented in... Figure 1 The second device shown is implemented at location 120. For the purposes of discussion, reference will be made to... Figure 1 Method 500 is described. It should be understood that method 500 may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0131] like Figure 5 As shown in box 510, the second device 120 sends a DCI including the TDRA field to the first device 110.

[0132] In box 520, the second device 120 determines a list of TDRAs from a set of TDRA configurations based on at least one of the identifier used for scrambling DCI, the RRC of the first device 110, or the service type configured for the first device 110.

[0133] In some embodiments, the RRC state of the first device 110 may be one of a connected state, an idle state, and an inactive state. In some embodiments, the service type is at least one of a broadcast service, a multicast service, or a unicast service.

[0134] In some embodiments, if the first device 110 is in a connected state and the service type is at least broadcast and multicast, the second device 120 can determine whether a first configuration (e.g., PDSCH-Config-Multicast configuration) is configured for the first device 110. If the first configuration is configured for the first device 110, the second device 120 can determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the second device 120 can determine a list of TDRAs from the first configuration.

[0135] In some embodiments, if the first configuration is not configured for the first device 110, the second device 120 may determine whether the second configuration (e.g., the PDSCH-Config-Common configuration) is not configured for the first device 110. If the second configuration is not configured for the first device 110, the second device 120 may determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the second device 120 may determine the TDRA list from the second configuration.

[0136] In some embodiments, if the second configuration is not configured for the first device 110, the second device 120 may determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the second device 120 may determine whether the predetermined identifier is associated with a multicast service or a broadcast service. If the predetermined identifier is associated with a multicast service, the second device 120 may determine the TDRA list from a third configuration (e.g., the default A table). If the predetermined identifier is associated with a broadcast service, the second device 120 may determine the TDRA list from a fourth configuration (e.g., a set of default A, B, and C tables) based on the SS / PBCH block and CORESET multiplexing mode.

[0137] In some embodiments, the second device 120 may send an indication to the first device 110, the indication being used to indicate whether a second configuration (e.g., PDSCH-Config-Common configuration) or a fifth configuration (e.g., PDSCH-Config configuration) is used to determine the TDRA list.

[0138] In these embodiments, if the first configuration is not configured for the first device 110, the second device 120 can determine whether to use the second or fourth configuration based on the indication. If the second configuration is used, the second device 120 can determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the second device 120 can determine the TDRA list from the second configuration. In some embodiments, if the fifth configuration is used, the second device 120 can determine whether the identifier is a predetermined identifier. If the identifier is a predetermined identifier, the second device 120 can determine the TDRA list from the fifth configuration.

[0139] In some embodiments, if the first device 110 is in a connected state and the service type is at least broadcast and multicast service, the second device 120 can determine whether a first configuration (e.g., PDSCH-Config-Multicast configuration) is configured for the first device 110. If the first configuration is configured for the first device 110, the second device 120 can determine whether an identifier is a predetermined identifier. If the identifier is a predetermined identifier, the second device 120 can determine whether the predetermined identifier is associated with a multicast service or a broadcast service. If the predetermined identifier is associated with a multicast service, the second device 120 can determine a list of TDRs from the first configuration. If the predetermined identifier is associated with a broadcast service, the second device 120 can determine whether a sixth configuration (e.g., PDSCH-Config-Broadcast configuration) is configured for the first device 110. If the sixth configuration is configured for the first device 110, the second device 120 can determine a list of TDRs from the sixth configuration.

[0140] In some embodiments, if the sixth configuration is not configured for the first device 110, the second device 120 may determine whether the second configuration is configured for the first device 110. If the second configuration is configured for the first device 110, the second device 120 may determine the TDRA list from the second configuration. If the second configuration is not configured for the first device 110, the second device 120 may determine the TDRA list from the fourth configuration (e.g., a set of default A, B, and C tables) based on the SS / PBCH block and CORESET multiplexing mode.

[0141] After determining the TDRA list, in box 530, the second device 120 applies the TDRA field based on the TDRA list to send services to the first device 110.

[0142] Using method 500, terminal devices in a connected state that receive multicast / unicast and broadcast services, as well as terminal devices that only receive broadcast services, can interpret the public TDRA list to be used. Therefore, significant flexibility in scheduling MBS can be provided.

[0143] Figure 4 and Figure 5 The operations in the method correspond to Figure 2 The process described in the text is omitted here for brevity; other details are omitted as they are not part of the main text.

[0144] Example implementations of devices and equipment

[0145] In some embodiments, the apparatus capable of performing method 400 (e.g., the first device 110) may include components for performing the various steps of method 400. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0146] In some embodiments, the apparatus may include: components for receiving downlink control information, including a time-domain resource allocation field, from a second device at a first device; components for determining a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier for scrambling the downlink control information, a radio resource control state of the first device, or a service type configured for the first device; and components for applying the time-domain resource allocation field based on the time-domain resource allocation list to receive a service from the second device.

[0147] In some embodiments, the radio resource control state of the first device is one of a connected state, an idle state, or an inactive state, and the service type is at least one of a broadcast service, a multicast service, or a unicast service.

[0148] In some embodiments, the components for determining the time-domain resource allocation list include components for: determining whether a first configuration is configured for the first device if the first device is in a connected state and the service type is at least broadcast and multicast services; determining whether the identifier is a predetermined identifier if the first configuration is configured for the first device; and determining the time-domain resource allocation list from the first configuration if the identifier is the predetermined identifier.

[0149] In some embodiments, the component for determining the time-domain resource allocation list further includes components for: determining whether a second configuration is not configured for the first device if the first configuration is not configured for the first device; determining whether the identifier is a predetermined identifier if the second configuration is configured for the first device; and determining the time-domain resource allocation list from the second configuration if the identifier is the predetermined identifier.

[0150] In some embodiments, the component for determining the time-domain resource allocation list further includes components for: determining whether the identifier is a predetermined identifier if the second configuration is not configured for the first device; determining whether the predetermined identifier is associated with a multicast service or a broadcast service if the identifier is the predetermined identifier; determining the time-domain resource allocation list from a third configuration if the predetermined identifier is associated with a multicast service; and determining the time-domain resource allocation list from a fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode if the predetermined identifier is associated with a broadcast service.

[0151] In some embodiments, the apparatus may further include components for receiving from the second device an indication of whether to use a second configuration or a fifth configuration to determine the time-domain resource allocation list.

[0152] In these embodiments, the component for determining the time-domain resource allocation list may further include components for: determining, based on the indication, whether to use the second configuration or the fourth configuration if the first configuration is not configured for the first device; determining whether the identifier is a predetermined identifier if the second configuration is used; and determining the time-domain resource allocation list from the second configuration if the identifier is the predetermined identifier.

[0153] In some embodiments, the component for determining the time-domain resource allocation list may further include components for: determining whether the identifier is a predetermined identifier if the fifth configuration is used; and determining the time-domain resource allocation list from the fifth configuration if the identifier is the predetermined identifier.

[0154] In some embodiments, the components for determining the time-domain resource allocation list may include components for: if the first device is in a connected state and the service type is at least broadcast and multicast service, determining whether a first configuration is configured for the first device; if the first configuration is configured for the first device, determining whether the identifier is a predetermined identifier; if the identifier is the predetermined identifier, determining whether the predetermined identifier is associated with a multicast service or a broadcast service; if the predetermined identifier is associated with a multicast service, determining the time-domain resource allocation list from the first configuration; if the predetermined identifier is associated with a broadcast service, determining whether a sixth configuration is configured for the first device; and if the sixth configuration is configured for the first device, determining the time-domain resource allocation list from the sixth configuration.

[0155] In some embodiments, the component for determining the time-domain resource allocation list may further include components for: determining whether the second configuration is configured for the first device if the sixth configuration is not configured for the first device; determining the time-domain resource allocation list from the second configuration if the second configuration is configured for the first device; and determining the time-domain resource allocation list from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode if the second configuration is not configured for the first device.

[0156] In some embodiments, the first device is a terminal device, and the second device is a network device. In some embodiments, the first configuration is a PDSCH-Config-Multicast configuration, the second configuration is a PDSCH-ConfigCommon configuration, the third configuration is a default A table, the fourth configuration is a set of default A, B, and C tables, the fifth configuration is a PDSCH-Config configuration, and the sixth configuration is a PDSCH-Config-Broadcast configuration.

[0157] In some embodiments, the apparatus capable of performing method 500 (e.g., the second device 120) may include components for performing the various steps of method 500. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0158] In some embodiments, the apparatus may include: components for transmitting downlink control information, including a time-domain resource allocation field, from a second device to a first device; components for determining a time-domain resource allocation list from a configuration set for time-domain resource allocation based on at least one of an identifier used to scramble the downlink control information, the radio resource control state of the first device, or a service type configured for the first device; and components for applying the time-domain resource allocation field to the time-domain resource allocation list to transmit a service to the first device.

[0159] In some embodiments, the radio resource control state of the first device is one of a connected state, an idle state, or an inactive state, and the service type is at least one of a broadcast service, a multicast service, or a unicast service.

[0160] In some embodiments, the components for determining the time-domain resource allocation list include components for: determining whether a first configuration is configured for the first device if the first device is in a connected state and the service type is at least broadcast and multicast services; determining whether the identifier is a predetermined identifier if the first configuration is configured for the first device; and determining the time-domain resource allocation list from the first configuration if the identifier is the predetermined identifier.

[0161] In some embodiments, the component for determining the time-domain resource allocation list further includes components for: determining whether a second configuration is not configured for the first device if the first configuration is not configured for the first device; determining whether the identifier is a predetermined identifier if the second configuration is configured for the first device; and determining the time-domain resource allocation list from the second configuration if the identifier is the predetermined identifier.

[0162] In some embodiments, the component for determining the time-domain resource allocation list further includes components for: determining whether the identifier is a predetermined identifier if the second configuration is not configured for the first device; determining whether the predetermined identifier is associated with a multicast service or a broadcast service if the identifier is the predetermined identifier; and determining the time-domain resource allocation list from a third configuration if the predetermined identifier is associated with a multicast service; or determining the time-domain resource allocation list from a fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode if the predetermined identifier is associated with a broadcast service.

[0163] In some embodiments, the apparatus may further include components for receiving from the second device an indication of whether to use a second configuration or a fifth configuration to determine the time-domain resource allocation list.

[0164] In these embodiments, the component for determining the time-domain resource allocation list may further include components for: determining, based on the indication, whether to use the second configuration or the fourth configuration if the first configuration is not configured for the first device; determining whether the identifier is a predetermined identifier if the second configuration is used; and determining the time-domain resource allocation list from the second configuration if the identifier is the predetermined identifier.

[0165] In some embodiments, the component for determining the time-domain resource allocation list may further include components for: determining whether the identifier is a predetermined identifier if the fifth configuration is used; and determining the time-domain resource allocation list from the fifth configuration if the identifier is the predetermined identifier.

[0166] In some embodiments, the components for determining the time-domain resource allocation list may include components for: if the first device is in a connected state and the service type is at least broadcast and multicast service, determining whether a first configuration is configured for the first device; if the first configuration is configured for the first device, determining whether the identifier is a predetermined identifier; and if the identifier is the predetermined identifier, determining whether the predetermined identifier is associated with a multicast service or a broadcast service; if the predetermined identifier is associated with a multicast service, determining the time-domain resource allocation list from the first configuration; if the predetermined identifier is associated with a broadcast service, determining whether a sixth configuration is configured for the first device; and if the sixth configuration is configured for the first device, determining the time-domain resource allocation list from the sixth configuration.

[0167] In some embodiments, the component for determining the time-domain resource allocation list may further include components for: determining whether a second configuration is configured for the first device if the sixth configuration is not configured for the first device; determining the time-domain resource allocation list from the second configuration if the second configuration is configured for the first device; and determining the time-domain resource allocation list from a fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode if the second configuration is not configured for the first device.

[0168] In some embodiments, the first device is a terminal device, and the second device is a network device. In some embodiments, the first configuration is a PDSCH-Config-Multicast configuration, the second configuration is a PDSCH-ConfigCommon configuration, the third configuration is a default A table, the fourth configuration is a set of default A, B, and C tables, the fifth configuration is a PDSCH-Config configuration, and the sixth configuration is a PDSCH-Config-Broadcast configuration.

[0169] Figure 6 This is a simplified block diagram suitable for implementing the device 600 of the embodiments of this disclosure. The device 600 can be provided to implement the first device or the second device, for example... Figure 1 The first device 110 or the second device 120 shown. As shown, device 600 includes one or more processors 610, one or more memories 620 coupled to processor 610, and one or more communication modules 640 (such as transmitters and / or receivers) coupled to processor 610.

[0170] Communication module 640 is used for bidirectional communication. Communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements.

[0171] Processor 610 can be any type suitable for a local technology network, and as a non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 600 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock that synchronizes with the main processor.

[0172] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to: read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist during power-off periods.

[0173] Computer program 630 includes computer-executable instructions that are executed by the associated processor 610. Program 630 may be stored in ROM 624. Processor 610 can perform any appropriate actions and processes by loading program 630 into RAM 622.

[0174] This embodiment of the disclosure can be implemented by means of program 630, enabling device 600 to execute as described in the reference. Figures 1 to 5 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.

[0175] In some embodiments, program 630 may be tangibly contained in a computer-readable medium, which may be contained in device 600 (e.g., memory 620) or other storage device accessible to device 600. Device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 7 An example of a computer-readable medium 700 in the form of a CD or DVD is shown. A program 630 is stored on the computer-readable medium.

[0176] Generally, various embodiments of the present invention can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present invention are shown and described as block diagrams, flowcharts, or using some other illustrations, it should be understood that the block diagrams, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or certain combinations thereof.

[0177] The present invention also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which execute in a device on a target real or virtual processor to perform the above-referenced... Figure 4 and Figure 5 Methods 400 and 500. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided as needed. The machine-executable instructions of the program module can be executed locally or on a distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0178] The program code used to perform the methods of the present invention can be written in any combination of one or more programming languages. This program code can be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device so that, when executed by the processor or controller, the program code results in the implementation of the functions / operations specified in the flowcharts and / or block diagrams. The program code can be executed entirely on the machine as a standalone software package, partially on the machine, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0179] In the context of this invention, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0180] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0181] Furthermore, while the operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order or sequence shown, or requiring that all illustrated operations be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of the invention, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0182] Although the invention has been described in language specific to structural features and / or methodological behavior, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A first device, comprising: At least one processor; as well as At least one memory including computer program code; The at least one memory and the computer program code are configured, together with the at least one processor, to cause the first device to: Receive downlink control information, including time-domain resource allocation fields, from the second device; Based on the identifier used to scramble the downlink control information, the radio resource control status of the first device, and the type of service configured for the first device, a time-domain resource allocation list is determined from the configuration set for time-domain resource allocation; as well as The time-domain resource allocation field is applied according to the time-domain resource allocation list to receive the service from the second device.

2. The first device according to claim 1, wherein the radio resource control state of the first device is one of a connected state, an idle state, or an inactive state. The type of service mentioned therein is at least one of broadcast service, multicast service, or unicast service.

3. The first device according to claim 1, wherein the first device is configured to determine the time-domain resource allocation list by: If the first device is in a connected state and the type of the service is at least broadcast and multicast service, then determine whether the first configuration is configured for the first device; If the first configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the first configuration.

4. The first device according to claim 3, wherein the first device is further configured to determine the time-domain resource allocation list by: If the first configuration is not configured for the first device, then determine whether the second configuration is not configured for the first device; If the second configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

5. The first device according to claim 4, wherein the first device is further configured to determine the time-domain resource allocation list by: If the second configuration is not configured for the first device, then determine whether the identifier is a predetermined identifier; If the identifier is the predetermined identifier, then determine whether the predetermined identifier is associated with a multicast service or a broadcast service; as well as If the predetermined identifier is associated with a multicast service, the time-domain resource allocation list is determined from the third configuration; or If the predetermined identifier is associated with a broadcast service, the time-domain resource allocation list is determined from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

6. The first device according to claim 3, wherein the first device is further configured such that: The device receives an instruction indicating whether to use a second configuration or a fifth configuration to determine the time-domain resource allocation list.

7. The first device of claim 6, wherein the first device is further configured to determine the time-domain resource allocation list by: If the first configuration is not configured for the first device, then it is determined whether to use the second configuration or the fifth configuration based on the indication; If the second configuration is used, determine whether the identifier is a predefined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

8. The first device of claim 7, wherein the first device is further configured to determine the time-domain resource allocation list by: If the fifth configuration is used, it is determined whether the identifier is a predetermined identifier; and If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the fifth configuration.

9. The first device of claim 1, wherein the first device is further configured to determine the time-domain resource allocation list by: If the identifier is a predefined identifier, the predefined identifier is associated with a multicast service, and the first configuration is configured for the first device, then the time-domain resource allocation list is determined from the first configuration; or If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, and the sixth configuration is configured for the first device, then the time-domain resource allocation list is determined from the sixth configuration.

10. The first device of claim 9, wherein the first device is configured to determine the time-domain resource allocation list by: If the identifier is a predefined identifier, the predefined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is configured for the first device, then the time-domain resource allocation list is determined from the second configuration; or If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is not configured for the first device, then the time-domain resource allocation list is determined from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

11. The first device according to claim 1, wherein the first device is a terminal device and the second device is a network device.

12. The first device according to claim 10, wherein the first configuration is a PDSCH multicast configuration, the second configuration is a PDSCH common configuration, the third configuration is a default A table, the fourth configuration is a set of default A tables, B tables and C tables, and the fifth configuration is a PDSCH configuration.

13. The first device according to claim 9, wherein the sixth configuration is a PDSCH broadcast configuration.

14. A second device, comprising: At least one processor; as well as At least one memory including computer program code; The at least one memory and the computer program code are configured, together with the at least one processor, to cause the second device to: Send downlink control information, including time-domain resource allocation fields, to the first device; Based on the identifier used to scramble the downlink control information, the radio resource control status of the first device, and the type of service configured for the first device, a time-domain resource allocation list is configured from the configuration set for time-domain resource allocation; as well as The time-domain resource allocation field is applied according to the time-domain resource allocation list to send the service to the first device.

15. The second device according to claim 14, wherein the radio resource control state of the first device is one of a connected state, an idle state, or an inactive state. The type of service mentioned therein is at least one of broadcast service, multicast service, or unicast service.

16. The second device of claim 14, wherein the second device is configured to determine the time-domain resource allocation list by: If the first device is in a connected state and the type of the service is at least broadcast and multicast service, then determine whether the first configuration is configured for the first device; If the first configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the first configuration.

17. The second device of claim 16, wherein the second device is further configured to determine the time-domain resource allocation list by: If the first configuration is not configured for the first device, then determine whether the second configuration is not configured for the first device; If the second configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

18. The second device of claim 17, wherein the second device is configured to determine the time-domain resource allocation list by: If the second configuration is not configured for the first device, then determine whether the identifier is a predetermined identifier; If the identifier is the predetermined identifier, then determine whether the predetermined identifier is associated with a multicast service or a broadcast service; as well as If the predetermined identifier is associated with a multicast service, the time-domain resource allocation list is determined from the third configuration; or If the predetermined identifier is associated with a broadcast service, the time-domain resource allocation list is determined from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

19. The second device according to claim 16, wherein the second device is further configured such that: Send an instruction to the first device, the instruction being used to indicate whether to use a second configuration or a fifth configuration to determine the time-domain resource allocation list.

20. The second device of claim 19, wherein the second device is further configured to determine the time-domain resource allocation list by: If the first configuration is not configured for the first device, then it is determined whether to use the second configuration or the fifth configuration based on the indication; If the second configuration is used, determine whether the identifier is a predefined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

21. The second device of claim 20, wherein the second device is configured to determine the time-domain resource allocation list by: If the fifth configuration is used, it is determined whether the identifier is a predetermined identifier; and If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the fifth configuration.

22. The second device of claim 14, wherein the second device is further configured to determine the time-domain resource allocation list by: If the identifier is a predefined identifier, the predefined identifier is associated with a multicast service, and the first configuration is configured for the first device, then the time-domain resource allocation list from the first configuration is applied; or If the identifier is a predefined identifier, the predefined identifier is associated with a broadcast service, and the sixth configuration is configured for the first device, then the time-domain resource allocation list from the sixth configuration is applied.

23. The second device of claim 22, wherein the second device is further configured to determine the time-domain resource allocation list by: If the identifier is a predefined identifier, the predefined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is configured for the first device, then the time-domain resource allocation list from the second configuration is applied; or If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is not configured for the first device, then the time-domain resource allocation list from the fourth configuration is applied based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

24. The second device according to claim 14, wherein the first device is a terminal device and the second device is a network device.

25. The second device according to claim 23, wherein the first configuration is a PDSCH multicast configuration, the second configuration is a PDSCH common configuration, the third configuration is a default A table, the fourth configuration is a set of default A tables, B tables and C tables, and the fifth configuration is a PDSCH configuration.

26. The second device according to claim 22, wherein the sixth configuration is a PDSCH broadcast configuration.

27. A communication method, comprising: The first device receives downlink control information, including a time-domain resource allocation field, from the second device. Based on the identifier used to scramble the downlink control information, the radio resource control status of the first device, and the type of service configured for the first device, a time-domain resource allocation list is determined from the configuration set for time-domain resource allocation; as well as The time-domain resource allocation field is applied according to the time-domain resource allocation list to receive the service from the second device.

28. The method of claim 27, wherein the radio resource control state of the first device is one of a connected state, an idle state, or an inactive state. The type of service mentioned therein is at least one of broadcast service, multicast service, or unicast service.

29. The method of claim 27, wherein determining the time-domain resource allocation list comprises: If the first device is in a connected state and the service type is at least broadcast and multicast service, then determine whether the first configuration is configured for the first device; If the first configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the first configuration.

30. The method of claim 29, wherein determining the time-domain resource allocation list further comprises: If the first configuration is not configured for the first device, then determine whether the second configuration is not configured for the first device; If the second configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

31. The method of claim 30, wherein determining the time-domain resource allocation list further comprises: If the second configuration is not configured for the first device, then determine whether the identifier is a predetermined identifier; If the identifier is the predetermined identifier, then determine whether the predetermined identifier is associated with a multicast service or a broadcast service; as well as If the predetermined identifier is associated with a multicast service, the time-domain resource allocation list is determined from the third configuration; or If the predetermined identifier is associated with a broadcast service, the time-domain resource allocation list is determined from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

32. The method of claim 29, further comprising: The device receives an instruction indicating whether to use a second configuration or a fifth configuration to determine the time-domain resource allocation list.

33. The method of claim 32, wherein determining the time-domain resource allocation list further comprises: If the first configuration is not configured for the first device, then it is determined whether to use the second configuration or the fifth configuration based on the indication; If the second configuration is used, determine whether the identifier is a predefined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

34. The method of claim 33, wherein determining the time-domain resource allocation list further comprises: If the fifth configuration is used, it is determined whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the fifth configuration.

35. The method of claim 27, wherein determining the time-domain resource allocation list comprises: If the identifier is a predefined identifier, the predefined identifier is associated with a multicast service, and the first configuration is configured for the first device, then the time-domain resource allocation list is determined from the first configuration; or If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, and the sixth configuration is configured for the first device, then the time-domain resource allocation list is determined from the sixth configuration.

36. The method of claim 35, wherein determining the time-domain resource allocation list further comprises: If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is configured for the first device, then the time-domain resource allocation list is determined from the second configuration; or If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is not configured for the first device, then the time-domain resource allocation list is determined from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

37. The method of claim 27, wherein the first device is a terminal device and the second device is a network device.

38. The method of claim 36, wherein the first configuration is a PDSCH multicast configuration, the second configuration is a PDSCH common configuration, the third configuration is a default A table, the fourth configuration is a set of default A tables, B tables and C tables, and the fifth configuration is a PDSCH configuration.

39. The method of claim 35, wherein the sixth configuration is a PDSCH broadcast configuration.

40. A communication method, comprising: The second device sends downlink control information, including a time-domain resource allocation field, to the first device. Based on the identifier used to scramble the downlink control information, the radio resource control status of the first device, and the type of service configured for the first device, a time-domain resource allocation list is configured from the configuration set for time-domain resource allocation; as well as The time-domain resource allocation list is applied according to the time-domain resource allocation field to send the service to the first device.

41. The method of claim 40, wherein the radio resource control state of the first device is one of a connected state, an idle state, or an inactive state. The type of service mentioned therein is at least one of broadcast service, multicast service, or unicast service.

42. The method of claim 40, wherein determining the time-domain resource allocation list comprises: If the first device is in a connected state and the type of the service is at least broadcast and multicast service, then determine whether the first configuration is configured for the first device; If the first configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the first configuration.

43. The method of claim 42, wherein determining the time-domain resource allocation list further comprises: If the first configuration is not configured for the first device, then determine whether the second configuration is not configured for the first device; If the second configuration is configured for the first device, then determine whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

44. The method of claim 43, wherein determining the time-domain resource allocation list further comprises: If the second configuration is not configured for the first device, then determine whether the identifier is a predetermined identifier; If the identifier is the predetermined identifier, then determine whether the predetermined identifier is associated with a multicast service or a broadcast service; as well as If the predetermined identifier is associated with a multicast service, the time-domain resource allocation list is determined from the third configuration; or If the predetermined identifier is associated with a broadcast service, the time-domain resource allocation list is determined from the fourth configuration based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

45. The method of claim 42, further comprising: The device receives an instruction indicating whether to use a second configuration or a fifth configuration to determine the time-domain resource allocation list.

46. ​​The method of claim 45, wherein determining the time-domain resource allocation list further comprises: If the first configuration is not configured for the first device, then it is determined whether to use the second configuration or the fifth configuration based on the indication; If the second configuration is used, determine whether the identifier is a predefined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the second configuration.

47. The method of claim 46, wherein determining the time-domain resource allocation list further comprises: If the fifth configuration is used, it is determined whether the identifier is a predetermined identifier; as well as If the identifier is the predetermined identifier, then the time-domain resource allocation list is determined from the fifth configuration.

48. The method of claim 40, wherein determining the time-domain resource allocation list comprises: If the identifier is a predefined identifier, the predefined identifier is associated with a multicast service, and the first configuration is configured for the first device, then the time-domain resource allocation list from the first configuration is applied; or If the identifier is a predefined identifier, the predefined identifier is associated with a broadcast service, and the sixth configuration is configured for the first device, then the time-domain resource allocation list from the sixth configuration is applied.

49. The method of claim 48, wherein determining the time-domain resource allocation list further comprises: If the identifier is a predefined identifier, the predefined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is configured for the first device, then the time-domain resource allocation list is applied from the second configuration; or If the identifier is a predetermined identifier, the predetermined identifier is associated with a broadcast service, the sixth configuration is not configured for the first device, and the second configuration is not configured for the first device, then the time-domain resource allocation list from the fourth configuration is applied based on the synchronization signal / physical broadcast channel block and control resource set multiplexing mode.

50. The method of claim 40, wherein, The first device is a terminal device, and the second device is a network device.

51. The method according to claim 49, wherein the first configuration is a PDSCH multicast configuration, the second configuration is a PDSCH common configuration, the third configuration is a default A table, the fourth configuration is a set of default A tables, B tables and C tables, and the fifth configuration is a PDSCH configuration.

52. The method of claim 48, wherein the sixth configuration is a PDSCH broadcast configuration.

Images