Multicast and broadcast service method and apparatus

Abstract

Embodiments of the present disclosure relate to multicast and broadcast service (MBS) services. The method includes receiving configuration information from a network device, the configuration information related to a multicast and broadcast service (MBS) service provided in one or more serving cells. The method further includes receiving downlink control information from the one or more serving cells in which the MBS service is provided. The method further includes receiving the MBS service provided in the one or more serving cells based on the downlink control information.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more specifically to wireless communication systems, apparatus, methods, and computer-readable media for multicast and broadcast services (MBS). Background Technology

[0002] The “background” description provided herein is intended to provide a general overview of the context of this disclosure. The work of the inventors within the scope described in this background section, and all aspects of this specification that cannot be otherwise limited to prior art at the time of this application, are neither explicitly nor implicitly acknowledged as prior art to this invention.

[0003] With the development of communication technology, several solutions have been proposed to provide efficient and reliable communication. For example, Multipoint Multi-Speed ​​(MBS) has been proposed. As used in this paper, "MBS" refers to a point-to-multipoint communication scheme where data packets are simultaneously sent from a single source to multiple destinations. In the MBS scenario, efficient use of radio and network resources can be achieved, simultaneously sending audio and video content to a large number of end users. The term "broadcast" refers to the ability to provide content to all users. On the other hand, the term "multicast" refers to the distribution of content among a specific group of users subscribed to these services. Multicast and broadcast content are sent over geographical areas called zones. Summary of the Invention

[0004] Overall, the exemplary embodiments of this disclosure provide an MBS solution.

[0005] An exemplary embodiment of this disclosure provides a method performed by a terminal device. The method includes: receiving configuration information from a network device, the configuration information relating to MBS services provided in one or more serving cells. The method further includes receiving downlink control information from the one or more serving cells in which the MBS services are provided. The method also includes: receiving the MBS services provided in the one or more serving cells based on the downlink control information.

[0006] An exemplary embodiment of this disclosure provides a method performed by a network device. The method includes: determining configuration information related to MBS service for a terminal device. The method further includes sending the configuration information to the terminal device. The configuration information indicates one or more serving cells for providing MBS service.

[0007] An exemplary embodiment of this disclosure provides a terminal device. The first terminal device includes a processor; and a memory coupled to the processor and storing instructions that, when executed by the processor, cause the first terminal device to perform the method according to the first aspect.

[0008] An exemplary embodiment of this disclosure provides a network device. The second terminal device includes a processor; and a memory coupled to the processor and storing instructions that, when executed by the processor, cause the network device to perform the method according to the second aspect.

[0009] In a fifth aspect, a computer-readable medium having instructions stored thereon is provided, which, when executed on at least one processor, cause at least one processor to perform the method according to the first aspect.

[0010] In a sixth aspect, a computer-readable medium having instructions stored thereon is provided, which, when executed on at least one processor, cause at least one processor to perform the method according to the second aspect.

[0011] This "Summary" is provided to illustrate a selection of embodiments described herein in a simplified form, which will be further described in the "Detailed Description" section below along with other embodiments. This "Summary" is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to the limitations of addressing any or all of the shortcomings pointed out in any part of this disclosure.

[0012] The term “UE” in this specification may be used interchangeably with the broader term “electronic device” and vice versa. Attached Figure Description

[0013] The scope of this disclosure will be best understood from the following detailed description of exemplary embodiments, when read in conjunction with the accompanying drawings, in which:

[0014] Figure 1 A schematic diagram of MBS delivery according to conventional technology is shown;

[0015] Figure 2 A schematic diagram of a communication system according to an exemplary embodiment is shown;

[0016] Figure 3 A signaling diagram of an example process according to an exemplary embodiment is shown;

[0017] Figure 4 A schematic diagram of a carrier aggregation system according to an exemplary embodiment is shown;

[0018] Figure 5 A flowchart of an example method according to an exemplary embodiment is shown;

[0019] Figure 6 A flowchart of an example method according to an exemplary embodiment is shown; and

[0020] Figure 7A simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure is shown.

[0021] Other applicable areas of this disclosure will become clear from the detailed description provided below. It should be understood that the detailed description of exemplary embodiments is for illustrative purposes only and is therefore not intended to limit the scope of this disclosure. Detailed Implementation

[0022] The 3rd Generation Partnership Project (3GPP) developed technical standards for cellular telecommunications network technologies, including radio access, core transport networks and service capabilities, including codecs, security and quality of service.

[0023] abbreviation

[0024] 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 impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various other ways than those described below.

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

[0026] As used herein, the term "network device" refers to a device capable of providing or hosting a cell or coverage area in which terminal devices can communicate. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), NodeBs in new radio access (gNBs), remote radio units (RRUs), radio heads (RHs), remote radio heads (RRHs), low-power nodes (such as femtonodes, piconodes), satellite network devices, aircraft network devices, etc. For the purposes of discussion, some exemplary embodiments will be described below with reference to eNBs as examples of network devices.

[0027] As used herein, the term "terminal device" means any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices or evolved MTC (eMTC) devices, vehicle equipment for V2X communication (where X represents a pedestrian, vehicle, or infrastructure / network), or image capture devices (such as digital cameras), gaming devices, music storage and playback devices, or internet devices that enable wireless or wired internet access and browsing, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0028] The communications discussed herein can conform to any suitable wireless interface standard, including but not limited to New Radio Access (NR), Long Term Evolution (LTE), LTE Evolution, LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), cdma2000, and Global System for Mobile Communications (GSM). Furthermore, such communications can be implemented according to any currently known or future communication protocols. 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, and fifth-generation (5G) communication protocols. The techniques described herein can be used in the aforementioned wireless networks and radio technologies, as well as other wireless networks and radio technologies.

[0029] As used herein, unless the context explicitly indicates otherwise, the singular forms “a,” “an,” and “the” should also include the plural forms. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0030] In some examples, values, processes, or devices are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many functional alternatives used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0031] As mentioned above, MBS has been proposed. Some MBS services are only available to UEs within a specific area; these can be termed "local MBS services." The following principles can be applied to support local MBS services: It is possible to support MBS sessions when the content of the MBS service is not location-dependent but the distribution of the content is limited to a certain region, and when the content is location-dependent. - It is possible to locate the MBS CN function near the NG RAN node serving the location area. - In cases where multicast services are only available in a limited area, the UE should be able to obtain the service area information of the multicast service so that the UE can trigger the session joining process only within the location area. - The UE should be able to obtain the service area information of the local multicast service via NAS signaling or via MBS service announcement. - In cases where MB service content is location-dependent (meaning the same MB service delivered to different sub-regions has different content), the UE may not know each sub-region in the MB service availability information. - It should be able to hide the internal PLMN topology from the application function (AF). - The network should be able to implement regional restrictions for access to local MBS services. - If different location-related content is provided for MBS sessions, the network should be able to support multiple ingress points for MBS sessions. - To support different location-related content, an additional identifier (e.g., FlowID) should be assigned to each location region and used in conjunction with the multicast session ID / TMGI in the network internal signaling to identify the location-related part of the multicast session. Information about location-related multicast services can be provided by AF or can be configured.

[0032] Simultaneously, the UE can be configured with carrier aggregation (CA) and served by one primary cell and one or more secondary cells (SCells) in a primary or secondary cell group (SpCell). The term "carrier aggregation" as used in this document refers to a technique used in wireless communication to allocate multiple frequency blocks (called component carriers) to the same user to increase the data rate per user. Several issues exist when supporting (local) MBS service in a CA scenario:

[0033] MBS-related configurations include: When the gNB configures a primary cell group (MCG) or secondary cell group (SCG) for the UE, the gNB should also provide the UE with the ongoing or supported MBS service configuration in each serving cell. This allows the UE to know which Radio Network Temporary Identifier (RNTI) to monitor in each serving cell. As used herein, "RNTI" can refer to an identifier that can be included in the signal between the UE and network equipment. As used herein, "serving cell" can refer to a cell capable of providing services to the terminal equipment.

[0034] MBS service is provided by one cell but transmitted in other cells: To take advantage of carrier aggregation, the gNB can use the resources of the first cell to transmit MBS service data, therefore the UE may need to monitor Group RNTI (G-RNTI) across the entire cell group. Furthermore, for location-related content, the MBS service is targeted at the UE in the second cell. Therefore, the UE needs to understand that the content received from the first cell is actually for the second cell.

[0035] The same MBS service is provided in multiple cells: For a UE configured with multiple cells in a cell group, the same MBS service may be provided in multiple cells (e.g., multiple SpCells and / or multiple SCells). If the MBS service content is location-dependent, the UE needs to decide from one or more / all relevant cells to receive MBS service data.

[0036] According to conventional techniques, configuration for single-cell point-to-multipoint (SC-PTM) service can be provided in an SCPTM Configuration sent via the single-cell multicast control channel (SC-MCCH). The SCPTM Configuration message may contain control information applicable to MBMS service transmitted via the single-cell multimedia broadcast multicast service signal frequency network (SC-MBSFN) radio bearer (SC-MRB). Table 1 below shows an example of an SCPTM Configuration message. Table 2 below shows the field descriptions of the SCPTM Configuration message. Table 1 Table 2

[0037] Furthermore, MBS services need to be delivered from a single data source (e.g., an application service provider) to multiple UEs. Depending on many factors, various delivery methods can be used to deliver MBS services in 5G. The term "unicast delivery" refers to a mechanism that uses Protocol Data Unit (PDU) sessions within the 3GPP network and individual UE and application server addresses (e.g., IP addresses) between the 3GPP network and the application server to deliver application data and signaling between the UE and the application server.

[0038] From the perspective of 5G CN, MBS multicast service can be delivered in two ways:

[0039] (1) 5GC Individual MBS Service Delivery Method: The 5G CN receives a single copy of the MBS data packets and delivers these individual copies of the MBS data packets to the individual UE via each UE PDU session. Therefore, for each such UE, a PDU session needs to be associated with a multicast session. For example, as Figure 1 As shown, the 5G CN 120 can receive individual copies of MBS data packets and deliver these individual copies of MBS data packets individually to UE 110-3 and UE 110-4 via each PDU session.

[0040] (2) 5GC Shared MBS Service Delivery Method: The 5G CN receives a single copy of the MBS data packets and delivers these single copies to the RAN node, which then delivers them to one or more UEs. For example, as Figure 1 As shown, the 5G CN 120 can receive a single copy of the MBS data packets and deliver these single copies of the MBS packets to the 5G RAN node 130, which can then deliver them to one or more UEs, such as UE 110-1 and UE 110-2.

[0041] If the 5GC Individual MBS Service Delivery Method is supported, the same single copy of the MBS data packets received by the CN can be delivered to one (or some) UEs via the 5GC Individual MBS Service Delivery Method and to other UEs via the 5GC Shared MBS Service Delivery Method.

[0042] From the RAN's perspective, in a shared delivery scenario, there are two delivery methods available for transmitting MBS packet streams via radio. RAN nodes can use a combination of PTP / PTM to deliver MBS packets to the UE.

[0043] - Point-to-point (PTP) delivery method: The RAN node delivers a separate copy of the MBS data packet to the individual UE via radio. For example, 5G RAN node 130 can deliver a copy of the MBS data packet to UE 110-1 and another copy of the MBS data packet to UE 110-2.

[0044] - Point-to-multipoint (PTM) delivery method: The RAN node delivers a single copy of the MBS data packets to a group of UEs via radio. For example, 5G RAN node 130 can deliver a single copy of the MBS data packets to UE 110-1 and UE 110-2.

[0045] To improve the data rate per user, carrier aggregation (CA) was proposed. In CA, multiple frequency blocks (called component carriers (CCs)) can be allocated to the same user. The maximum possible data rate per user increases with the number of frequency blocks allocated to the user. A UE can simultaneously receive or transmit on one or more CCs depending on its capabilities.

[0046] - A UE with a single timing advance capability for CA can simultaneously receive or transmit on multiple CCs corresponding to multiple serving cells that share the same timing advance.

[0047] - A UE with multiple timing advance capabilities for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells with different timing advances;

[0048] - A UE without CA capability can receive and transmit on a single CC corresponding to only one serving cell.

[0049] CA is supported for both continuous and non-continuous CCs. When CA is deployed, frame timing and system frame number (SFN) are aligned between aggregated cells, or the UE can configure offsets in multiple slots between PCell / PCell and SCell. The maximum number of CCs configured for a UE is 16 for DL ​​and 16 for UL.

[0050] In the case of CA, the multi-carrier nature of the physical layer can only be exposed to the MAC layer. For the MAC layer, each serving cell may require a Hybrid Automatic Repeat Request (HARQ) entity, as shown below:

[0051] - In both the uplink and downlink, each serving cell has an independent hybrid ARQ entity, and in the absence of spatial multiplexing, one transport block is generated per allocation or authorized per serving cell. Each transport block and its potential HARQ retransmissions are mapped to a single serving cell.

[0052] When CA is configured, the UE has only one RRC connection with the network. During RRC connection establishment or re-establishment, one serving cell can provide NAS mobility information, and during RRC connection re-establishment or handover, one serving cell can provide security input. This cell is called the primary cell (PCell). Depending on the UE's capabilities, secondary cells (SCells) can be configured to form a serving cell set together with the PCell. Therefore, the serving cell set configured for a UE will always include one PCell and one or more SCells.

[0053] SCell reconfiguration, addition, and removal can be performed via RRC. During intra-NR handover and during connection recovery from RRC_INACTIVE, the network can also add, remove, retain, or reconfigure SCells for use with a target PCell. When a new SCell is added, dedicated RRC signaling is used to send all the necessary system information for the SCell; that is, when in connected mode, the UE does not need to directly obtain broadcast system information from the SCell.

[0054] Therefore, a new MBS solution is needed. According to embodiments of this disclosure, a terminal device distinguishes different content offered in different cells based on MBS configuration received from a network device. The terminal device monitors identifiers in one or more cells and receives one or more data packets for MBS services from those cells. In this way, MBS services can be more flexible, and data reliability is also improved. Example communication systems and networks

[0055] Figure 2 A schematic diagram of a communication system 200 in which embodiments of the present disclosure may be implemented is shown. The communication system 200, as part of a communication network, includes terminal devices 210-1, 210-2, ..., 210-N, which may be collectively referred to as "(a plurality of) terminal devices 210". The number N may be any suitable integer.

[0056] The communication system 200 also includes communication devices 220-1, 220-2, 220-3, ..., 220-M, which can be collectively referred to as "(a plurality of) communication devices 220". The number M can be any suitable integer. In some embodiments, the communication devices 220 can be network devices. The communication system also includes a core network device 230. By way of example only, the core network device 230 can be an Access and Mobility Management Function (AMF) entity. In the communication system 200, the communication devices 220 and the terminal device 210 can transmit data and control information to each other. Figure 2 The number of devices shown is given for illustrative purposes only, and no limitations are imposed.

[0057] Communication in communication system 200 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or to be developed in the future. Furthermore, the communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDMA), and / or any other currently known or to be developed in the future.

[0058] The embodiments of this disclosure can be applied to any suitable scenario. For example, embodiments of this disclosure can be implemented at NR devices with reduced capabilities. Alternatively, embodiments of this disclosure can be implemented in one of the following ways: NR multiple-input multiple-output (MIMO), NR sidechain enhancement, NR systems at frequencies above 52.6 GHz, extended NR operation up to 71 GHz, narrowband Internet of Things (NB-IoT) / enhanced machine-type communications (eMTC) over non-terrestrial networks (NTN), UE power saving enhancement, NR coverage enhancement, NB-IoT and LTE-MTC, integrated access and backhaul (IAB), NR multicast and broadcast services, or enhancements to multi-radio dual connectivity. Example process

[0059] Some example procedures according to embodiments of this disclosure will now be described in detail. (Refer to...) Figure 3 . Figure 3 A signaling diagram of an example process 300 according to some embodiments of the present disclosure is shown. For the purposes of discussion, reference will be made to... Figure 2 Describe process 300. For illustrative purposes only, process 300 may involve, for example, Figure 2 The terminal device 210-1 and network device 220-1 are shown. In some embodiments, the example process 300 can be applied to a CA (Certificate Authority) scenario. Alternatively, the example process 300 can also be applied to other communication scenarios.

[0060] In some embodiments, if a terminal device (e.g., terminal device 210-1) initially accesses the network, the identifier of the terminal device may be reported to CN device 230. Alternatively, if the terminal device subscribes to 5GC, the identifier of the terminal device may be reported to CN device 230. If the identifier of the terminal device is subscribed, CN device 230 may send the identifier of the terminal device to a network device (e.g., network device 220-1). The identifier of the terminal device may be sent in any suitable message. For example, the identifier of the terminal device may be included in a context establishment message sent from CN device 130 to network device 220-1. The context establishment message may also include an indication of the service. Furthermore, the context establishment message may include the range of the transport area for the MBS service. In other embodiments, a Temporary Mobile Group Identifier (TMGI) that may identify the MBS service may also be included in the context establishment message. Alternatively or additionally, the context establishment message may include a session identifier for the service. It should be noted that the context establishment message may include any suitable parameters. In this way, the communication device knows that the terminal device needs the MBS service in its vicinity, as well as the MBS service transport area range or service area for the MBS service.

[0061] In some embodiments, network device 220-1 may send a request (3005) to CN device 230 for configuration related to the MBS service. This request may be sent via appropriate signaling between network device 220-1 and CN device 230. For example, the MBS service may be a streaming media service. Alternatively, the MBS service may be a service related to vehicle networking. It should be noted that the MBS service can be any suitable type of service. CN device 230 may send a response (3010) to network device 220-1 to this request. This response may include the MBS service configuration, which will be described in detail later. In other embodiments, CN device 230 may send the MBS service configuration to network device 220-1 without receiving such a request from network device 220-1. The MBS configuration may be sent via any appropriate signaling between network device 220-1 and CN device 230.

[0062] Network device 220-1 determines configuration information related to MBS service 3015. The MBS service configuration information indicates one or more serving cells used to provide the MBS service. In some embodiments, the MBS service configuration information may indicate a set of serving cells. The size of the set of serving cells can be any suitable size. For example, the set of serving cells may include one serving cell. Alternatively, the set of serving cells may include more than one serving cell. This is merely an example. Figure 4As shown, the serving cell set may include cell 410-1. Alternatively, the serving cell set may include one or more of cells 410-1, 410-2, 410-3, 410-4, 410-5, and 410-6 that can provide MBS service. For example, in a CA scenario, as... Figure 4 As shown, terminal device 210-1 is located within the overlapping coverage area of ​​cells 410-1, 410-2, 410-3, and 410-5. In this case, terminal device 210-1 can receive MBS services from these cells 410-1, 410-2, 410-3, and 410-5. It should be noted that... Figure 4 The number of cells shown is just an example, not a limitation.

[0063] In some embodiments, the configuration information may include MBS session information. As used herein, the term "MBS session" refers to the duration for which data associated with the MBS service can be sent to an end device. For example, MBS session information may include the range of the MBS service's transmission area. By way of example only, MBS session information may include the Temporary Multicast Group Identifier (TMGI) of the MBS service, which may indicate the range of the MBS service's transmission area. Furthermore, MBS session information may include an identifier for the MBS session.

[0064] Alternatively or additionally, the configuration information for the MBS service may include an indication of whether the MBS service is location-dependent. In some embodiments, the content of the MBS service may vary depending on the location within the range of the MBS service's transmission area. In this case, the indication may indicate that the MBS service is location-dependent. Alternatively, if the content of the MBS service can be the same at different locations within the range of the MBS service's transmission area, the indication may indicate that the MBS service is not location-dependent. In this case, the configuration information may include one or more area identifiers associated with the MBS service. For example, if the MBS service is location-dependent, the area identifiers at different locations may be different.

[0065] In other embodiments, the configuration information for the MBS service may include indexes for distinguishing different content of the MBS service in different serving cells within a set of serving cells. For example, multiple serving cells may provide MBS services but send different content of the MBS service to terminal device 210-1. In this case, terminal device 210-1 may distinguish those different contents based on the indexes. In some embodiments, the indexes may be any suitable numbers. By way of example only, if cells 410-1, 410-2, and 410-3 provide MBS services, the configuration information may indicate that index "0" represents a portion of the MBS service content received in cell 410-1, index "1" represents a portion of the MBS service content received in cell 410-2, or index "2" represents a portion of the MBS service content received in cell 410-3.

[0066] Alternatively or additionally, the configuration information for the MBS service may include an identifier associated with the MBS service. As used herein, the term "identifier" refers to information that can be included in signals between the UE and the network device. In some embodiments, the identifier may be a physical layer identifier. For example, the identifier may be a G-RNTI. It should be noted that the identifier can be any suitable type of identifier.

[0067] In other embodiments, the configuration information may include a list of allowed serving cells for the MBS service. For example, cells in the list of allowed serving cells may send the same content for the MBS service.

[0068] In some embodiments, the configuration information may include an indication of whether the MBS service is transmitted on one or more serving cells in the serving cell set. For example, if the MBS service is transmitted only on cell 410-1, the configuration information may include an indication instructing the MBS service to be transmitted on cell 410-1. Alternatively, if the MBS service is transmitted on the serving cell set, the configuration information may include an indication instructing the MBS service to be transmitted on the entire serving cell set.

[0069] Alternatively or additionally, the configuration information may include Multimedia Broadcast Multicast Service (MBMS) Traffic Channel (MTCH) scheduling information. As used herein, the term "MTCH scheduling information" can refer to information used to schedule MBMS services on the MTCH channel. For example, the MTCH scheduling information may include Discontinuous Receive (DRX) configuration associated with MBS services for terminal device 210-1. By way of example only, the DRX configuration may indicate the duration of DRX on. Furthermore, the DRX configuration may indicate the duration of DRX off. Additionally, the DRX configuration may indicate the DRX period. As used herein, the term "DRX" refers to a technique that allows the UE to turn off its transceiver for a duration of a DRX period when there are no packets to receive. As used herein, the term "on duration" refers to a period of time during which the terminal device is able to monitor the downlink channel and receive data or control information on the downlink channel. As used herein, the term "off duration" refers to a period of time during which the terminal device does not monitor the downlink channel and does not receive data or control information on the downlink channel. As used in this document, the term "DRX period" includes the duration during which the terminal device should monitor the downlink channel and the DRX period during which the terminal device can skip receiving downlink channels.

[0070] Network device 220-1 sends configuration information 3020 to terminal device 210-1. In some embodiments, the configuration information for the MBS service can be sent via RRC signaling. Alternatively, the configuration information for the MBS service can be sent in a system information block. In some embodiments, if terminal device 210-1 is configured with a primary cell group or a secondary cell group, the configuration information for the MBS service can be sent using the same signaling used for the configuration of the primary cell group or the secondary cell group. As used herein, the term "primary cell group (MCG)" can refer to a group of serving cells associated with a primary node. As used herein, the term "secondary cell group (SCG)" can refer to a group of serving cells associated with a secondary node. In other embodiments, the configuration information for the MBS service can be sent separately from the configuration of the primary cell group or the secondary cell group.

[0071] As an example only, configuration information for the MBS service can be included in an RRCReconfiguration message. In some embodiments, the information element "MBS Configuration" can be included in the information elements "SpCellConfig" and "SCellConfig" within the RRCReconfiguration message. The term "information element" as used herein refers to a type-length-value item, comprising 1) a type (which corresponds to a label for a field), a length indicator, and a value, although any combination of one or more of these components is possible. Typically, a message may include one or more information elements. "SpCellConfig" as used herein refers to the configuration for the primary cell in a primary or secondary cell group. "SCellConfig" as used herein refers to the configuration for the secondary cell in a primary or secondary cell group. As an example only, an RRCReconfiguration message may include the following information elements: masterCellGroup / MRDC-SecondaryCellGroupConfig → SpCellConfig / SCellConfig → MBS Configuration.

[0072] In other embodiments, the information element "MBS Configuration" may be included in the information element "DRB-ToAddMod" of the RRCReconfiguration message. By way of example only, the RRCReconfiguration message may include the following information element: RadioBearerConfig → DRB-ToAddMod. As used herein, the information element "DRB-ToAddMod" refers to the configuration of the data radio bearer to be added or modified.

[0073] Alternatively or additionally, the information element "MBS Configuration" may be included within the information element "LogicalChannelConfig" in the RRCReconfiguration message. By way of example only, the RRCReconfiguration message may include the following information elements: CellGroupConfig → RLC-BearerConfig → LogicalChannelConfig. The term "LogicalChannelConfig" as used herein refers to the configuration of a logical channel.

[0074] Table 3 shows an example of MBS configuration, where MBS configuration can be included in SpCellConfig and SCellConfig. Table 3

[0075] Terminal device 210-1 determines the identifier associated with the MBS service 3025. For example, terminal device 210-1 can obtain the identifier from configuration information. In some embodiments, if the identifier associated with the MBS service can be the same in the serving cell set, terminal device 210-1 can obtain the identifier from the configuration information. Alternatively, if the identifier associated with the MBS service can be different in the serving cell set, terminal device 210-1 can obtain multiple identifiers from the configuration information.

[0076] Terminal device 210-1 can monitor downlink control information (DCI) associated with an identifier in at least one serving cell in the serving cell set. The term "downlink control information (DCI)" as used herein refers to information that provides the UE with necessary information such as physical layer resource allocation, power control commands, and HARQ information for both uplink and downlink. Various DCI formats exist, which are predefined formats in which downlink control information is packaged or formed and transmitted in the physical downlink control channel (PDCCH). In some embodiments, the DCI can be scrambled with an identifier. For example, the cyclic redundancy check (CRC) bits in the DCI can be scrambled with an identifier. The term "scrambling" as used herein refers to a digital coding technique that can be used to identify and distinguish cells.

[0077] In some embodiments, if configuration information is received from network device 220-1 in cell 410-1, terminal device 210-1 may monitor the DCI associated with the identifier only in cell 410-1. In other words, terminal device 210-1 may monitor the DCI associated with the identifier only in the cell providing the configuration information for MBS service. In this case, terminal device 210-1 may receive at least one data packet in that cell.

[0078] Alternatively, terminal device 210-1 can determine whether to monitor the current serving cell or multiple serving cells in a set of serving cells based on the configuration information of the MBS service. In some embodiments, the configuration information may include an indication of whether the MBS service is transmitted on a single cell. In this case, terminal device 210-1 can monitor the DCI associated with the identifier in that cell. For example, if the indication is "1", it indicates that the MBS service is transmitted on a single cell. If the indication is "0", it indicates that the MBS service is transmitted on more than one cell. It should be noted that the indication can be any suitable form. As an example only, if the configuration information of the MBS service indicates that cell 410-1 needs to be monitored, terminal device 210-1 can monitor the DCI associated with the identifier in cell 410-1. Alternatively, the configuration information may include an indication of multiple serving cells in one or more serving cells on which the MBS service is transmitted. In this case, terminal device 210-1 can monitor the DCI associated with the identifier in multiple serving cells. For example, if the configuration information of the MBS service indicates that cells 410-1 and 410-2 need to be monitored, then terminal device 210-1 can monitor the DCI associated with the identifier in cells 410-1 and 410-2. In other embodiments, if the configuration information of the MBS service indicates that all cells in the serving cell set need to be monitored, then terminal device 210-1 can monitor the DCI associated with the identifier in all cells of the serving cell set. In this case, terminal device 210-1 can receive at least one data packet in all cells of the serving cell set.

[0079] In other embodiments, the configuration information for the MBS service may indicate a list of allowed cells for the MBS service. In this case, terminal device 210-1 can understand that the MBS service can be provided by cells in the list of allowed cells, and that DCI associated with the identifier can be monitored in the cells of the list of allowed cells.

[0080] In some embodiments, to save power, network device 220-1 may instruct terminal device 210-1 to monitor the DCI associated with the identifier only in the target serving cell. For example, the configuration information for the MBS service may include a one-bit field indicating the target serving cell. In this case, terminal device 210-1 may monitor the DCI associated with the identifier in the target serving cell indicated in the configuration information. In this case, terminal device 210-1 may receive at least one data packet in the target serving cell. By way of example only, the configuration information may indicate cell 410-3. Terminal device 210-1 may determine to monitor the DCI associated with the identifier in cell 410-3.

[0081] In other embodiments, network device 220-1 may transmit a search space configuration. The term "search space configuration" as used herein refers to information indicating where to monitor scheduling allocation / granting information associated with a particular component carrier. In some embodiments, the search space configuration may also include a DCI format. A DCI associated with at least one identifier can be considered a type of DCI format. The term "DCI format" as used herein refers to a predefined format for packaging / forming downlink control information and transmitting it in the PDCCH. In this case, the search space configuration of the target serving cell may indicate a DCI format of this type in which the DCI is associated with at least one identifier. In this case, terminal device 210-1 may monitor the DCI associated with at least one identifier in the target serving cell. In this case, terminal device 210-1 may receive at least one data packet in the target serving cell.

[0082] In some embodiments, network device 220-1 may send a 3035 DCI associated with an identifier to terminal device 210-1. For example, network device 220-1 may send the DCI on the PDCCH. In some embodiments, the DCI may be sent in the current serving cell. Alternatively, the DCI may be sent in one or more cells from a set of serving cells that can provide MBS services. In other embodiments, network device 220-1 may send a 3040 MBS service to terminal device 210-1. For example, network device 220-1 may send one or more data packets associated with the MBS service.

[0083] In some embodiments, network device 220-1 may send additional information 3045 to terminal device 210-1. As used herein, additional information refers to information that can be used to distinguish different content of MBS services in different serving cells. In some embodiments, the additional information may be an index used to distinguish different content of MBS services. For example, the content of MBS services in cells with different indices is different. In some embodiments, the additional information may be determined by network device 220-1. Alternatively, the additional information may be determined by CN device 230. In some embodiments, terminal device 210-1 may associate at least one data packet with a target cell 3050 based on the additional information.

[0084] In other embodiments, if the MBS service is location-dependent, the additional information may include identifiers of areas in which certain content of the MBS service can be valid. For example, the additional information may indicate one or more valid areas of the MBS service. In this case, terminal device 210-1 can understand that the content of the MBS service is valid in one or more valid areas.

[0085] In some embodiments, additional information may be sent via physical layer signaling. For example, when network device 220-1 transmits data packets for MBS service in the downlink, additional information may be added to the associated DCI of the data packet to indicate the associated cell or region of the data packet. In this case, the additional information may be a region identifier associated with the data packet. The term "region identifier" as used herein refers to an identifier that can be used to identify a region. Alternatively, the additional information may include another identifier associated with the MBS service. Alternatively, the additional information may be a cell identifier associated with the data packet. The term "cell identifier" as used herein refers to an identifier that can be used to identify a cell. In other embodiments, the associated DCI for the data packet may be associated with a region identifier, and terminal device 210-1 may determine the corresponding region after decoding the associated DCI of the data packet. By way of example only, if the cell identifier in the additional information may be an identifier of cell 410-5, and at least one data packet is received in cell 410-1, then terminal device 210-1 may associate at least one data packet with cell 410-5.

[0086] In some embodiments, additional information may be sent via the MAC layer header. For example, the additional information may be provided in the MAC layer Logical Channel Identifier (LCID). In this case, in some embodiments, the LCID may be used to indicate the cell or area associated with at least one data packet. In other embodiments, the additional information may be included in the MAC Control Element (MAC CE). In this case, in some embodiments, the MAC CE may include information about the cell or area associated with at least one data packet. By way of example only, if the cell in the LCID or MAC CE is cell 410-5, and at least one data packet is received in cell 410-1, then terminal device 210-1 may associate at least one data packet with cell 410-5.

[0087] In other embodiments, the MBS service may be provided in multiple serving cells (e.g., cells 410-1, 410-2, and 410-3), and the MBS service may be associated with different identifiers in the multiple cells. If the configuration information of the MBS service indicates that the content of the MBS service provided in the multiple cells is different, then terminal device 210-1 may monitor the DCIs associated with all identifiers indicated in the configuration information of the MBS service in the multiple serving cells (e.g., in cells 410-1, 410-2, and 410-3). Alternatively, if the configuration information of the MBS service indicates that the content of the MBS service provided in the multiple serving cells is the same, then terminal device 210-1 may determine the target cell from the multiple serving cells. Terminal device 210-1 may determine the target identifier corresponding to the target cell based on the configuration information. In this case, terminal device 210-1 may monitor the DCI associated with the target identifier in the target serving cell and receive the MBS service in the target serving cell. For example, terminal device 210-1 may determine cell 410-3 as the target cell and determine the identifier based on cell 410-3. In this scenario, terminal 210-1 can monitor the DCI scrambled with such an identifier and receive MBS service in cell 410-3. In some embodiments, terminal device 210-1 can randomly select a target cell from a plurality of serving cells. Alternatively, terminal device 210-1 can select a target cell whose link quality exceeds a threshold quality. For example, terminal device 210-1 can measure the link quality of multiple cells and select a target cell based on the measurement results. In some embodiments, the link quality can be measured based on the power of the signal received in the multiple serving cells.

[0088] In other embodiments, terminal device 210-1 may further determine another target cell from a plurality of serving cells. In this case, terminal device 210-1 may determine another target identifier corresponding to the other target serving cell. In this case, terminal device 210-1 may monitor the DCI associated with the corresponding other target identifier in the other target serving cell and receive at least one data packet in the other target serving cell. In some embodiments, the target cell may be determined randomly. Alternatively, the target cell may be determined based on the link quality in the target cell. In some embodiments, terminal device 210-1 may randomly select another target cell from a plurality of serving cells. Alternatively, terminal device 210-1 may select another target cell whose link quality exceeds a threshold quality. For example, terminal device 210-1 may measure the link quality of a plurality of cells and select another target cell based on the measurement results. In some embodiments, the link quality may be measured based on the power of the signal received in the plurality of serving cells.

[0089] According to embodiments of this disclosure, a solution is proposed that facilitates MBS service transmission between different cells within the same cell group. It allows for more flexible configuration of MBS services. Furthermore, it can improve the data rate of MBS services. Example Method

[0090] Figure 5 A flowchart of an example method 500 according to some embodiments of the present disclosure is shown. Method 500 can be performed by, for example... Figure 2 The terminal device 210-1 shown performs this operation. It should be understood that method 500 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect. For ease of discussion, reference will be made to… Figure 2 Method 500 is described from the perspective of terminal device 210-1.

[0091] In box 510, terminal device 210-1 receives configuration information from network device 220-1. The configuration information relates to MBS services provided in one or more serving cells. The MBS service configuration information indicates the set of serving cells used to provide the MBS service. The size of the serving cell set can be any suitable size. For example, the serving cell set may include one serving cell. Alternatively, the serving cell set may include more than one serving cell.

[0092] In some embodiments, the configuration information may include MBS session information. As used herein, the term "MBS session" refers to the duration for which data associated with the MBS service can be sent to an end device. For example, MBS session information may include the range of the MBS service's transmission area. By way of example only, MBS session information may include the Temporary Multicast Group Identifier (TMGI) of the MBS service, which may indicate the range of the MBS service's transmission area. Furthermore, MBS session information may include an identifier for the MBS session.

[0093] Alternatively or additionally, the configuration information for the MBS service may include an indication of whether the MBS service is location-dependent. In some embodiments, the content of the MBS service may vary depending on the location within the range of the MBS service's transmission area. In this case, the indication may indicate that the MBS service is location-dependent. Alternatively, if the content of the MBS service can be the same at different locations within the range of the MBS service's transmission area, the indication may indicate that the MBS service is not location-dependent. In this case, the configuration information may include one or more area identifiers associated with the MBS service. For example, if the MBS service is location-dependent, the area identifiers at different locations may be different.

[0094] In other embodiments, the configuration information for the MBS service may include indexes for distinguishing different content of the MBS service in different serving cells within a set of serving cells. For example, multiple serving cells may provide MBS services but send different content of the MBS service to terminal device 210-1. In this case, terminal device 210-1 may distinguish those different contents based on the indexes. In some embodiments, the indexes may be any suitable numbers. By way of example only, if cells 410-1, 410-2, and 410-3 provide MBS services, the configuration information may indicate that index "0" represents a portion of the MBS service content received in cell 410-1, index "1" represents a portion of the MBS service content received in cell 410-2, or index "2" represents a portion of the MBS service content received in cell 410-3.

[0095] Alternatively or additionally, the configuration information for the MBS service may include an identifier associated with the MBS service. In some embodiments, the identifier may be a physical layer identifier. For example, the identifier may be a G-RNTI. It should be noted that the identifier can be any suitable type of identifier.

[0096] In other embodiments, the configuration information may include a list of allowed serving cells for the MBS service. For example, cells in the list of allowed serving cells may send the same content for the MBS service.

[0097] In some embodiments, the configuration information may include an indication of whether the MBS service is transmitted on one or more serving cells in the serving cell set. For example, if the MBS service is transmitted only on cell 410-1, the configuration information may include an indication instructing the MBS service to be transmitted on cell 410-1. Alternatively, if the MBS service is transmitted on the serving cell set, the configuration information may include an indication instructing the MBS service to be transmitted on the entire serving cell set.

[0098] Alternatively or additionally, the configuration information may include Multimedia Broadcast Multicast Service (MBMS) Traffic Channel (MTCH) scheduling information. As used herein, the term "MTCH scheduling information" can refer to information used to schedule MBMS services on the MTCH channel. For example, the MTCH scheduling information may include Discontinuous Receive (DRX) configuration associated with MBS services for terminal device 210-1. By way of example only, the DRX configuration may indicate the duration of DRX on. Furthermore, the DRX configuration may indicate the duration of DRX off. Additionally, the DRX configuration may indicate a DRX period. As used herein, the term "DRX" refers to a technique that allows the UE to turn off its transceiver for the duration of a DRX period when there are no packets to receive. As used herein, the term "on duration" refers to the period during which the terminal device is able to monitor the downlink channel and receive data or control information on the downlink channel. As used herein, the term "off duration" refers to the period during which the terminal device does not monitor the downlink channel and does not receive data or control information on the downlink channel. As used in this document, the term "DRX period" includes the duration during which the terminal device should monitor the downlink channel and the DRX period during which the terminal device can skip receiving downlink channels.

[0099] In some embodiments, the configuration information for the MBS service may be sent via RRC signaling. Alternatively, the configuration information for the MBS service may be sent in a system information block. In some embodiments, if the terminal device 210-1 is configured with a primary cell group or a secondary cell group, the configuration information for the MBS service may be sent using the same signaling used for the configuration of the primary cell group or the secondary cell group. As used herein, the term "primary cell group (MCG)" may refer to a group of serving cells associated with a primary node. As used herein, the term "secondary cell group (SCG)" may refer to a group of serving cells associated with a secondary node. In other embodiments, the configuration information for the MBS service may be sent separately from the configuration of the primary cell group or the secondary cell group.

[0100] As an example only, configuration information for the MBS service can be included in an RRCReconfiguration message. In some embodiments, the information element "MBS configuration" can be included in the information elements "SpCellConfig" and "SCellConfig" within the RRCReconfiguration message. The term "information element" as used herein refers to a type-length-value item, comprising 1) a type (which corresponds to a label for a field), a length indicator, and a value, although any combination of one or more of these components is possible. Typically, a message may include one or more information elements. "SpCellConfig" as used herein refers to the configuration for the primary cell in a primary or secondary cell group. "SCellConfig" as used herein refers to the configuration for the secondary cell in a primary or secondary cell group. As an example only, an RRCReconfiguration message may include the following information element: masterCellGroup / MRDC-SecondaryCellGroupConfig → SpCellConfig / SCellConfig → MBS configuration.

[0101] In other embodiments, the information element "MBS Configuration" may be included in the information element "DRB-ToAddMod" of the RRCReconfiguration message. By way of example only, the RRCReconfiguration message may include the following information element: RadioBearerConfig → DRB-ToAddMod. As used herein, the information element "DRB-ToAddMod" refers to the configuration of the data radio bearer to be added or modified.

[0102] Alternatively or additionally, the information element "MBS Configuration" may be included within the information element "LogicalChannelConfig" in the RRCReconfiguration message. By way of example only, the RRCReconfiguration message may include the following information elements: CellGroupConfig → RLC-BearerConfig → LogicalChannelConfig. The term "LogicalChannelConfig" as used herein refers to the configuration of a logical channel.

[0103] In some embodiments, terminal device 210-1 may determine an identifier associated with the MBS service. For example, terminal device 210-1 may obtain one or more identifiers from configuration information. In some embodiments, the identifier associated with the MBS service may be the same across the serving cell set. Alternatively, the identifier associated with the MBS service may be different across the serving cell set.

[0104] In block 530, terminal device 210-1 receives downlink control information from one or more serving cells in which MBS service is provided. In block 540, terminal device 210-1 receives MBS service from one or more serving cells based on the downlink control information. In some embodiments, terminal device 210-1 may monitor downlink control information (DCI) associated with an identifier in at least one serving cell in the set of serving cells.

[0105] In some embodiments, if configuration information is received from network device 220-1 in cell 410-1, terminal device 210-1 may monitor the DCI associated with the identifier only in cell 410-1. In other words, terminal device 210-1 may monitor the DCI associated with the identifier only in the cell where the configuration information for the MBS service is provided. In this case, terminal device 210-1 may receive at least one data packet in that cell.

[0106] Alternatively, terminal device 210-1 can determine whether to monitor the current serving cell or multiple serving cells in the serving cell set based on the configuration information of the MBS service. For example, if the configuration information of the MBS service indicates that cell 410-1 needs to be monitored, terminal device 210-1 can monitor the DCI associated with the identifier in cell 410-1. Alternatively, if the configuration information of the MBS service indicates that cells 410-1 and 410-2 need to be monitored, terminal device 210-1 can monitor the DCI associated with at least one identifier in cells 410-1 and 410-2. In other embodiments, if the configuration information of the MBS service indicates that all cells in the serving cell set need to be monitored, terminal device 210-1 can monitor the DCI associated with the identifier in all cells in the serving cell set. In this case, terminal device 210-1 can receive at least one data packet in all cells in the serving cell set.

[0107] In other embodiments, the configuration information for the MBS service may indicate a list of allowed cells for the MBS service. In this case, terminal device 210-1 can understand that the MBS service can be provided by cells in the list of allowed cells, and that DCI associated with the identifier can be monitored in the cells of the list of allowed cells.

[0108] In some embodiments, to save power, network device 220-1 may instruct terminal device 210-1 to monitor the DCI associated with the identifier only in the target serving cell. For example, the configuration information for the MBS service may include a one-bit field indicating the target serving cell. In this case, terminal device 210-1 may monitor the DCI associated with the identifier in the target serving cell indicated in the configuration information. In this case, terminal device 210-1 may receive at least one data packet in the target serving cell.

[0109] In other embodiments, network device 220-1 may transmit a search space configuration. As used herein, the term "search space configuration" refers to information indicating where to monitor scheduling allocation / granting associated with a particular component carrier. In some embodiments, the search space configuration may also include a DCI format. The DCI associated with an identifier can be considered a type of DCI format. In this case, the search space configuration of the target serving cell may indicate a DCI format of this type, in which the DCI is associated with the identifier. In this case, terminal device 210-1 may monitor the DCI associated with the identifier in the target serving cell. In this case, terminal device 210-1 may receive at least one data packet in the target serving cell.

[0110] In some embodiments, additional information may be sent to terminal device 210-1. As used herein, additional information refers to information that can be used to distinguish different content of MBS services in different serving cells. In some embodiments, the additional information may be an index used to distinguish different content of MBS services. For example, the content of MBS services in cells with different indices is different. In some embodiments, the additional information may be determined by network device 220-1. Alternatively, the additional information may be determined by CN device 230. In some embodiments, terminal device 210-1 may associate at least one data packet with a target cell based on the additional information.

[0111] In other embodiments, if the MBS service is location-dependent, the additional information may include identifiers of areas in which certain content of the MBS service can be valid. For example, the additional information may indicate one or more valid areas of the MBS service. In this case, terminal device 210-1 can understand that the content of the MBS service is valid in one or more valid areas.

[0112] In some embodiments, additional information may be sent via physical layer signaling. For example, when network device 220-1 transmits data packets for MBS service in the downlink, additional information may be added to the associated DCI of the data packet to indicate the associated cell or area of ​​the data packet. In this case, the additional information may be an area identifier associated with the data packet. The term "area identifier" as used herein refers to an identifier that can be used to identify an area. Alternatively, the additional information may include another identifier associated with the data packet. Alternatively, the additional information may be a cell identifier associated with the data packet. The term "cell identifier" as used herein refers to an identifier that can be used to identify a cell. In other embodiments, the associated DCI for the data packet may be associated with an area identifier, and terminal device 210-1 may determine the corresponding area after decoding the associated DCI of the data packet. By way of example only, if the cell identifier in the additional information may be an identifier of cell 410-5, and at least one data packet is received in cell 410-1, then terminal device 210-1 may associate at least one data packet with cell 410-5.

[0113] In some embodiments, additional information may be sent via MAC layer signaling. For example, the additional information may be provided in a MAC layer Logical Channel Identifier (LCID). In this case, in some embodiments, the LCID may be used to indicate the cell or area associated with at least one data packet. In other embodiments, the additional information may be included in a MAC Control Element (MAC CE). In this case, in some embodiments, the MAC CE may include information about the cell or area associated with at least one data packet. By way of example only, if the cell in the LCID or MAC CE is cell 410-5, and at least one data packet is received in cell 410-5, then terminal device 210-1 may associate at least one data packet with cell 410-5.

[0114] In other embodiments, the MBS service may be provided in multiple serving cells, and the MBS service may be associated with different identifiers in multiple cells. If the configuration information of the MBS service indicates that the content of the MBS service provided in multiple cells is different, then terminal device 210-1 may monitor the DCI associated with all identifiers indicated in the configuration information of the MBS service in multiple serving cells (e.g., in cells 410-1, 410-2, and 410-3). Alternatively, if the configuration information of the MBS service indicates that the content of the MBS service provided in multiple serving cells is the same, then terminal device 210-1 may determine a target cell from the multiple serving cells. In this case, terminal device 210-1 may monitor the DCI associated with a target identifier corresponding to the target serving cell and receive at least one data packet in the target serving cell. In other embodiments, terminal device 210-1 may also determine another target cell from the multiple serving cells. In this case, terminal device 210-1 may monitor the DCI associated with another target identifier corresponding to another target serving cell and receive at least one data packet in the other target serving cell. In some embodiments, the target cell may be determined randomly. Alternatively, the target cell can be determined based on the link quality within the target cell.

[0115] Figure 6 A flowchart of an example method 600 according to some embodiments of the present disclosure is shown. Method 600 can be... Figure 2 The network device 220-1 shown performs this operation. It should be understood that method 600 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect. For ease of discussion, reference will be made to… Figure 2 Method 600 is described from the perspective of network device 220-1.

[0116] In some embodiments, if a terminal device (e.g., terminal device 210-1) initially accesses the network, the identifier of the terminal device may be reported to CN device 230. Alternatively, if the terminal device subscribes to 5GC, the identifier of the terminal device may be reported to CN device 230. If the identifier of the terminal device is subscribed, CN device 230 may send the identifier of the terminal device to a network device (e.g., network device 220-1). The identifier of the terminal device may be sent in any suitable message. For example, the identifier of the terminal device may be included in a context establishment message sent from CN device 130 to network device 220-1. The context establishment message may also include an indication of the service. Furthermore, the context establishment message may include the range of the transport area of ​​the MBS service. In other embodiments, the Temporary Multicast Group Identifier (TMGI) of the service may also be included in the context establishment message. Alternatively or additionally, the context establishment message may include the session identifier of the service. It should be noted that the context establishment message may include any suitable parameters. In this way, the communication device knows that the terminal device needs the MBS service in its vicinity and the range of the transport area of ​​the MBS service.

[0117] In some embodiments, network device 220-1 may send a request to CN device 230 for configuration of the MBS service. This request may be sent via appropriate signaling between network device 220-1 and CN device 230. For example, the MBS service may be a streaming media service. Alternatively, the MBS service may be a vehicle-to-everything (V2X) related service. It should be noted that the MBS service can be any suitable type of service. Network device 220-1 may receive a response to this request from CN device 230. This response may include the MBS service configuration, which will be described in detail later. In other embodiments, CN device 230 may send the MBS service configuration to network device 220-1 without receiving such a request from network device 220-1. The MBS configuration may be sent via any appropriate signaling between network device 220-1 and CN device 230.

[0118] In box 610, network device 220-1 determines configuration information related to MBS service for terminal device 210-1. The MBS service configuration information indicates the set of serving cells used to provide the MBS service. The size of the serving cell set can be any suitable size. For example, the serving cell set may include one serving cell. Alternatively, the serving cell set may include more than one serving cell.

[0119] In some embodiments, the configuration information may include MBS session information. As used herein, the term "MBS session" refers to the duration for which data associated with the MBS service can be sent to an end device. For example, MBS session information may include the range of the MBS service's transmission area. By way of example only, MBS session information may include the Temporary Multicast Group Identifier (TMGI) of the MBS service, which may indicate the range of the MBS service's transmission area. Furthermore, MBS session information may include an identifier for the MBS session.

[0120] Alternatively or additionally, the configuration information for the MBS service may include an indication of whether the MBS service is location-dependent. In some embodiments, the content of the MBS service may vary depending on the location within the range of the MBS service's transmission area. In this case, the indication may indicate that the MBS service is location-dependent. Alternatively, if the content of the MBS service can be the same at different locations within the range of the MBS service's transmission area, the indication may indicate that the MBS service is not location-dependent. In this case, the configuration information may include one or more area identifiers associated with the MBS service. For example, if the MBS service is location-dependent, the area identifiers at different locations may be different.

[0121] In other embodiments, the configuration information for the MBS service may include an index for distinguishing different content of the MBS service in different serving cells within a set of serving cells. For example, multiple serving cells may provide MBS services but send different content of the MBS service to terminal device 210-1. In this case, terminal device 210-1 may distinguish those different contents based on the index. In some embodiments, the index may be any suitable number.

[0122] Alternatively or additionally, configuration information related to the MBS service may include an identifier associated with the MBS service. In some embodiments, the identifier may be a physical layer identifier. For example, the identifier may be a G-RNTI. It should be noted that the identifier can be any suitable type of identifier.

[0123] In other embodiments, the configuration information may include a list of allowed serving cells for the MBS service. For example, cells in the list of allowed serving cells may send the same content for the MBS service.

[0124] In some embodiments, the configuration information may include an indication of whether the MBS service is transmitted on one or more serving cells in the serving cell set. For example, if the MBS service is transmitted only on cell 410-1, the configuration information may include an indication instructing the MBS service to be transmitted on cell 410-1. Alternatively, if the MBS service is transmitted on the serving cell set, the configuration information may include an indication instructing the MBS service to be transmitted on the entire serving cell set.

[0125] Alternatively or additionally, the configuration information may include Multimedia Broadcast Multicast Service (MBMS) Traffic Channel (MTCH) scheduling information. As used herein, the term "MTCH scheduling information" can refer to information used to schedule MBMS services on the MTCH channel. For example, the MTCH scheduling information may include Discontinuous Receive (DRX) configuration associated with MBS services for terminal device 210-1. By way of example only, the DRX configuration may indicate the duration of DRX on. Furthermore, the DRX configuration may indicate the duration of DRX off. Additionally, the DRX configuration may indicate the DRX period. As used herein, the term "DRX" refers to a technique that allows the UE to turn off its transceiver for a duration of a DRX period when there are no packets to receive. As used herein, the term "on duration" refers to a period of time during which the terminal device is able to monitor the downlink channel and receive data or control information on the downlink channel. As used herein, the term "off duration" refers to a period of time during which the terminal device does not monitor the downlink channel and does not receive data or control information on the downlink channel. As used in this document, the term "DRX period" includes the duration during which the terminal device should monitor the downlink channel and the DRX period during which the terminal device can skip receiving downlink channels.

[0126] In block 620, network device 220-1 sends configuration information to terminal device 210-1. In some embodiments, the configuration information for the MBS service may be sent via RRC signaling. Alternatively, the configuration information for the MBS service may be sent in a system information block. In some embodiments, if terminal device 210-1 is configured with a primary cell group or a secondary cell group, the configuration information for the MBS service may be sent using the same signaling used for the configuration of the primary cell group or the secondary cell group. As used herein, the term "primary cell group (MCG)" may refer to a group of serving cells associated with a primary node. As used herein, the term "secondary cell group (SCG)" may refer to a group of serving cells associated with a secondary node. In other embodiments, the configuration of the MBS service configuration information may be sent separately from the configuration of the primary cell group or the secondary cell group.

[0127] As an example only, configuration information for the MBS service can be included in an RRCReconfiguration message. In some embodiments, the information element "MBS configuration" can be included in the information elements "SpCellConfig" and "SCellConfig" within the RRCReconfiguration message. The term "information element" as used herein refers to a type-length-value item, comprising 1) a type (which corresponds to a label for a field), a length indicator, and a value, although any combination of one or more of these components is possible. Typically, a message may include one or more information elements. "SpCellConfig" as used herein refers to the configuration for the primary cell in a primary or secondary cell group. "SCellConfig" as used herein refers to the configuration for the secondary cell in a primary or secondary cell group. As an example only, an RRCReconfiguration message may include the following information elements: masterCellGroup / MRDC-SecondaryCellGroupConfig → SpCellConfig / SCellConfig → MBS configuration.

[0128] In other embodiments, the information element "MBS Configuration" may be included in the information element "DRB-ToAddMod" of the RRCReconfiguration message. By way of example only, the RRCReconfiguration message may include the following information element: RadioBearerConfig → DRB-ToAddMod. As used herein, the information element "DRB-ToAddMod" refers to the configuration of the data radio bearer to be added or modified.

[0129] Alternatively or additionally, the information element "MBS configuration" may be included within the information element "LogicalChannelConfig" in the RRCReconfiguration message. By way of example only, the RRCReconfiguration message may include the following information elements: CellGroupConfig → RLC-BearerConfig → LogicalChannelConfig. The term "LogicalChannelConfig" as used herein refers to the configuration of a logical channel.

[0130] In some embodiments, network device 220-1 may send a DCI associated with an identifier to terminal device 210-1. In other embodiments, network device 220-1 may send at least one data packet associated with MBS service to terminal device 210-1.

[0131] In some embodiments, network device 220-1 may send additional information to terminal device 210-1. As used herein, additional information refers to information that can be used to distinguish different content of MBS services in different serving cells. In some embodiments, the additional information may be an index used to distinguish different content of MBS services. For example, the content of MBS services in cells with different indices is different. In some embodiments, the additional information may be determined by network device 220-1. Alternatively, the additional information may be determined by CN device 230.

[0132] In other embodiments, if the MBS service is location-dependent, the additional information may include identifiers of areas in which certain content of the MBS service is valid. For example, the additional information may indicate one or more valid areas of the MBS service.

[0133] In some embodiments, additional information may be sent via physical layer signaling. For example, when network device 220-1 transmits data packets for MBS service in the downlink, additional information may be added to the associated DCI of the data packet to indicate the associated cell or area of ​​the data packet. In this case, the additional information may be an area identifier associated with the data packet. The term "area identifier" as used herein refers to an identifier that can be used to identify an area. Alternatively, the additional information may include another identifier associated with the data packet. Alternatively, the additional information may be a cell identifier associated with the data packet. The term "cell identifier" as used herein refers to an identifier that can be used to identify a cell.

[0134] In some embodiments, additional information may be transmitted via MAC layer signaling. For example, the additional information may be included in a MAC layer Logical Channel Identifier (LCID). In this case, the LCID may be used to indicate the cell or area associated with at least one data packet. Alternatively, in another example, the additional information may be included in a MAC Control Element (MACCE). Example device

[0135] Figure 7 This is a simplified block diagram of an apparatus 700 suitable for implementing embodiments of the present disclosure. The apparatus 700 can be considered as follows: Figure 2 This is yet another example implementation of the terminal device 210 shown. Therefore, the device 700 can be implemented at or as at least a part of the terminal device 210.

[0136] As shown in the figure, device 700 includes a processor 710, a memory 720 coupled to the processor 710, and suitable transmitters (TX) and receivers (RX) 740 coupled to the processor 710. The memory 710 stores at least a portion of a program 730. The TX / RX 740 is used for bidirectional communication. The TX / RX 740 is coupled to at least one antenna to facilitate communication, although in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a Mobility Management Entity (MME) / Serving Gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a Relay Node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0137] Assuming program 730 includes program instructions that, when executed by the associated processor 710, enable device 700 to operate according to embodiments of this disclosure, as referenced herein. Figures 3-6 The embodiments described herein can be implemented by computer software executable by the processor 710 of device 700, or by hardware, or by a combination of software and hardware. The processor 710 can be configured to implement various embodiments of this disclosure. Furthermore, a combination of the processor 710 and the memory 710 can form a processing unit 750 suitable for implementing various embodiments of this disclosure.

[0138] Memory 710 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory, as non-limiting examples. Although only one memory 710 is shown in device 700, several physically different memory modules may exist within device 700. Processor 710 can be of any type suitable for a local technology network and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 700 may have multiple processors, such as application-specific integrated circuit chips that are time-obliged to a clock that synchronizes the main processor.

[0139] In one exemplary embodiment, a method performed by a terminal device includes: receiving configuration information from a network device, the configuration information relating to MBS services provided in one or more serving cells; receiving downlink control information from the one or more serving cells in which the MBS services are provided; and receiving the MBS services provided in the one or more serving cells based on the downlink control information.

[0140] In one exemplary embodiment, the configuration information is received in a Radio Resource Control (RRC) reconfiguration message.

[0141] In one exemplary embodiment, the identifier includes a Group Radio Network Temporary Identifier (G-RNTI).

[0142] In one exemplary embodiment, the configuration information includes at least one of the following: MBS session information of the MBS service, the MBS session information including at least one of a temporary mobile group identifier associated with the MBS service or a session identifier associated with the MBS service; an indication of whether the MBS service is location-dependent; if the MBS service is location-dependent, at least one area identifier associated with the MBS service; an index for distinguishing different content of the MBS service received from different serving cells in the serving cell set; an identifier associated with the MBS service; an indication of whether the MBS service is transmitted on one or more serving cells in the serving cell set; or Multimedia Broadcast Multicast Service (MBMS) Traffic Channel (MTCH) scheduling information.

[0143] In one exemplary embodiment, receiving the configuration information includes receiving the configuration information via a message carrying one of the following: the configuration of the one or more serving cells, the configuration of the data radio bearers associated with the one or more serving cells, and the configuration of the logical channels associated with the one or more serving cells.

[0144] In one exemplary embodiment, receiving the configuration information includes receiving the configuration information via either radio resource control signaling or a system information block.

[0145] In one exemplary embodiment, the method further includes obtaining an identifier from the configuration information; and wherein receiving the downlink control information includes: determining that the configuration information is received from the network device in a serving cell among the one or more serving cells, and receiving the at least one downlink control information associated with the identifier in the serving cell.

[0146] In one exemplary embodiment, receiving the downlink control information associated with the identifier includes: receiving the downlink control information associated with the identifier in one or more serving cells.

[0147] In one exemplary embodiment, receiving the downlink control information includes: obtaining a first indication from the configuration information regarding whether the MBS service is transmitted on a serving cell; and, based on the determination that the MBS service is transmitted on a serving cell, receiving the downlink control information in the serving cell on which the MBS is transmitted, based on the first indication.

[0148] In one exemplary embodiment, the method further includes: obtaining an identifier from the configuration information; and wherein receiving the downlink control information includes: obtaining a second indication from the configuration information, the second indication indicating a plurality of serving cells on which the MBS service is transmitted in the one or more serving cells; and receiving the at least one downlink control information associated with the identifier in the plurality of serving cells based on the second indication.

[0149] In one exemplary embodiment, the method further includes: receiving a search space configuration of a serving cell among the one or more serving cells from the network device; and receiving the downlink control information associated with the identifier includes: determining that the search space configuration indicates that the downlink control information of the serving cell is associated with the identifier, and receiving the downlink control information in the serving cell.

[0150] In one exemplary embodiment, the method further includes: receiving additional information from the network device via physical layer signaling, the additional information indicating one of the following: an area identifier associated with a data packet of the MBS service, a cell identifier associated with the data packet, and another identifier associated with the data packet; and associating the data packet with a target serving cell among the one or more serving cells based on the additional information.

[0151] In one exemplary embodiment, the method further includes: receiving additional information from the network device via media access control layer signaling, the additional information indicating one of the following: an area identifier associated with a data packet of the MBS service, or a cell identifier associated with the data packet; and associating the data packet with a target serving cell among the one or more serving cells based on the additional information.

[0152] In one exemplary embodiment, determining the identifier associated with the MBS service includes: obtaining multiple identifiers corresponding to multiple serving cells among the one or more serving cells based on the configuration information; receiving the downlink control information includes: receiving multiple downlink control information associated with the multiple identifiers in the multiple serving cells based on determining that the configuration information indicates that the MBS service is location-dependent or that the content of the MBS service from the multiple serving cells is different.

[0153] In one exemplary embodiment, receiving the MBS service includes: receiving multiple data packets associated with the MBS service in the plurality of serving cells.

[0154] In one exemplary embodiment, receiving the downlink control information includes: determining a target serving cell from the plurality of serving cells based on determining that the configuration information indicates that the content of the MBS service from the plurality of serving cells is the same; determining a target identifier corresponding to the target serving cell based on the configuration information; and receiving the downlink control information associated with the target identifier corresponding to the target serving cell.

[0155] In one exemplary embodiment, receiving the MBS service includes: receiving the at least one data packet associated with the MBS service from the target serving cell.

[0156] In one exemplary embodiment, the method further includes: determining another target serving cell from the plurality of serving cells; receiving the downlink control information associated with another target identifier corresponding to the other target serving cell; and wherein receiving the MBS service includes: receiving at least one data packet associated with the MBS service from the target serving cell and the other target serving cell.

[0157] In one exemplary embodiment, a method performed by a network device includes: determining configuration information related to MBS service for a terminal device; and sending the configuration information to the terminal device, wherein the configuration information indicates one or more serving cells for providing the MBS service.

[0158] In one exemplary embodiment, the configuration information is sent in a Radio Resource Control (RRC) reconfiguration message.

[0159] In one exemplary embodiment, the identifier includes a Group Radio Network Temporary Identifier (G-RNTI).

[0160] In one exemplary embodiment, the configuration information includes at least one of the following: MBS session information of the MBS service, the MBS session information including at least one of a temporary mobile group identifier associated with the MBS service or a session identifier associated with the MBS service; an indication of whether the MBS service is location-dependent; if the MBS service is location-dependent, at least one area identifier associated with the MBS service; an index for distinguishing different content of the MBS service received from different serving cells in the serving cell set; an identifier associated with the MBS service; an indication of whether the MBS service is transmitted on one or more serving cells in the serving cell set; or Multimedia Broadcast Multicast Service (MBMS) Traffic Channel (MTCH) scheduling information.

[0161] In one exemplary embodiment, sending the configuration information includes sending the configuration information via a message carrying one of the following: the configuration of the one or more serving cells, the configuration of the data radio bearers associated with the one or more serving cells, and the configuration of the logical channels associated with the one or more serving cells.

[0162] In one exemplary embodiment, sending the configuration information includes sending the configuration information via either radio resource control signaling or a system information block.

[0163] In one exemplary embodiment, the method further includes sending a search space configuration of serving cells in the serving cell set to the terminal device, the search space configuration indicating that downlink control information of the serving cell is associated with an identifier related to the MBS service.

[0164] In one exemplary embodiment, the method further includes sending downlink control information associated with an identifier associated with the MBS service to the terminal device; and sending at least one data packet associated with the MBS service to the terminal device.

[0165] In one exemplary embodiment, the method further includes sending additional information to the terminal device via physical layer signaling, the additional information indicating one of an area identifier associated with the at least one data packet, a cell identifier associated with the at least one data packet, and another identifier associated with the at least one data packet.

[0166] In one exemplary embodiment, the method further includes sending additional information to the terminal device via media access control layer signaling, the mapping information indicating one of an area identifier associated with the at least one data packet or a cell identifier associated with the at least one data packet.

[0167] Generally, the various embodiments of this disclosure 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. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other illustrations, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0168] This disclosure 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 a program module, which execute in a device on a target real or virtual processor to perform the functions described above. Figures 3-6 The process or method described herein. 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 a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can be executed locally or on a distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0169] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote computer or server.

[0170] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will 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 fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0171] Furthermore, although the operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or sequentially, or requiring all shown operations to be performed to obtain the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of individual embodiments 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 individually or in any suitable sub-combination in multiple embodiments.

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

[0173] Unless otherwise expressly stated, references to elements in the singular do not indicate "one and only one," but rather "one or more." If phrases such as "any combination of A, B, and C" are used herein, they should be interpreted as meaning that A can exist alone in an embodiment, B can exist alone in an embodiment, C can exist alone in an embodiment, and any combination of elements A, B, and C can exist in a single embodiment. For example, any combination of elements A, B, and C includes the following combinations: A and B, A and C, B and C, and A and B and C, each of which can exist in an embodiment.

[0174] When elements (such as A and B) are described as “A / B” or using “ / ”, the description is intended to cover all the following combinations: A alone, B alone, or A and B together.

Claims

1. A method executed by a terminal device, the method comprising: Receive configuration information from network devices, the configuration information being related to multicast and broadcast (MBS) services provided in one or more serving cells; Receive the search space configuration of the serving cell from the one or more serving cells from the network device; The downlink control information of the serving cell is associated with an identifier associated with the MBS service, as determined by the search space configuration. The downlink control information is received from the serving cell of the one or more serving cells in which the MBS service is provided. as well as Based on the downlink control information, the MBS service provided in the one or more serving cells is received.

2. The method of claim 1, wherein the configuration information is received in at least one of the following ways: Radio Resource Control (RRC) reconfiguration message, Radio resource control signaling, or System information block.

3. The method according to claim 1, wherein the configuration information includes at least one of the following: The MBS session information of the MBS service includes at least one of the following: a temporary mobile group identifier associated with the MBS service, or a session identifier associated with the MBS service. Regarding whether the MBS service is location-related. If the MBS service is location-dependent, then at least one area identifier associated with the MBS service, An index used to distinguish the different content of the MBS service received from different serving cells in the serving cell set. Identifiers associated with the MBS service, An indication regarding whether the MBS service is sent on one or more serving cells in the set of serving cells, or Multimedia Broadcast Multicast Service (MBMS) Service Channel (MTCH) scheduling information.

4. The method according to claim 1, wherein receiving the configuration information includes: The configuration information is received via a message carrying one of the following: The configuration of the one or more serving cells, The configuration of the data radio bearers associated with the one or more serving cells, Configuration of logical channels associated with the one or more serving cells.

5. The method according to claim 1, further comprising: Obtain the identifier associated with the MBS service from the configuration information; And receiving the downlink control information includes: The configuration information is received from the network device in one or more serving cells, and the downlink control information associated with the identifier is received in the serving cell.

6. The method of claim 1, wherein receiving the downlink control information comprises: Obtain a first indication from the configuration information regarding whether the MBS service is being sent on a serving cell; as well as Based on the determination that the MBS service is transmitted on a serving cell, and based on the first indication, the downlink control information is received in the serving cell on which the MBS is transmitted.

7. The method according to claim 1, further comprising: Obtain the identifier associated with the MBS service from the configuration information; and The receipt of the downlink control information includes: Obtain a second indication from the configuration information, the second indication specifying multiple serving cells among the one or more serving cells on which the MBS service is transmitted; and Based on the second instruction, the downlink control information is received in the plurality of serving cells.

8. The method according to claim 1, further comprising: Additional information is received from the network device via physical layer signaling or via media access control layer signaling, the additional information indicating one of the following: The region identifier associated with the data packets of the MBS service, The cell identifier associated with the data packet, Another identifier associated with said one data packet; and Based on the additional information, the data packets are associated with a target serving cell among the one or more serving cells.

9. The method according to claim 1, further comprising: Based on the configuration information, obtain multiple identifiers corresponding to multiple serving cells in the one or more serving cells; The receipt of the downlink control information includes: Based on the determination that the configuration information indicates the MBS service is location-dependent or that the content of the MBS services from the multiple serving cells is different, multiple downlink control information associated with the multiple identifiers is received in the multiple serving cells; and wherein receiving the MBS service includes: Receive multiple data packets associated with the MBS service in the plurality of serving cells.

10. The method according to claim 1, further comprising: Based on the configuration information, obtain multiple identifiers corresponding to multiple serving cells in the one or more serving cells; The receipt of the downlink control information includes: Based on the determination that the configuration information indicates that the content of the MBS service from the plurality of serving cells is the same, a target serving cell is determined from the plurality of serving cells; Based on the configuration information, a target identifier corresponding to the target serving cell is determined; and Receiving the downlink control information associated with the target identifier in the target serving cell; and wherein receiving the MBS service includes: Receive at least one data packet associated with the MBS service from the target serving cell.

11. The method of claim 10, further comprising: Determine another target serving cell from the plurality of serving cells; Receive the downlink control information associated with another target identifier corresponding to the other target serving cell; and Receiving the MBS service includes: Receive at least one data packet associated with the MBS service from the target serving cell and the other target serving cell.

12. A terminal device, comprising: processor; as well as A transceiver coupled to the processor, and the processor is configured to: Receive configuration information from network devices, the configuration information being related to multicast and broadcast (MBS) services provided in one or more serving cells; Receive the search space configuration of the serving cell from the one or more serving cells from the network device; The downlink control information of the serving cell is associated with an identifier associated with the MBS service, as determined by the search space configuration. The downlink control information is received from the serving cell of the one or more serving cells in which the MBS service is provided. as well as Based on the downlink control information, the MBS service provided in the one or more serving cells is received.

13. The terminal device according to claim 12, wherein the configuration information is received in at least one of the following ways: Radio Resource Control (RRC) reconfiguration message, Radio resource control signaling, or System information block.

14. The terminal device according to claim 12, wherein the configuration information includes at least one of the following: The MBS session information of the MBS service includes at least one of the following: a temporary mobile group identifier associated with the MBS service, or a session identifier associated with the MBS service. Regarding whether the MBS service is location-related. If the MBS service is location-dependent, then at least one area identifier associated with the MBS service, An index used to distinguish the different content of the MBS service received from different serving cells in the serving cell set. Identifiers associated with the MBS service, An indication regarding whether the MBS service is sent on one or more serving cells in the set of serving cells, or Multimedia Broadcast Multicast Service (MBMS) Service Channel (MTCH) scheduling information.

15. The terminal device of claim 12, wherein the processor is configured to receive the configuration information by: The configuration information is received via a message carrying one of the following: The configuration of the one or more serving cells, The configuration of the data radio bearers associated with the one or more serving cells, Configuration of logical channels associated with the one or more serving cells.

16. The terminal device according to claim 12, wherein the processor is further configured to: The processor is further configured to receive the downlink control information by: obtaining an identifier associated with the MBS service from the configuration information; and wherein the processor is also configured to receive the downlink control information by: The configuration information is received from the network device in one or more serving cells, and the downlink control information associated with the identifier is received in the serving cell.

17. The terminal device of claim 12, wherein the processor is further configured to receive the downlink control information by: Obtain a first indication from the configuration information regarding whether the MBS service is being sent on a serving cell; and Based on the determination that the MBS service is transmitted on a serving cell, and based on the first indication, the downlink control information is received in the serving cell on which the MBS is transmitted.

18. The terminal device according to claim 12, wherein the processor is further configured to: Obtain the identifier associated with the MBS service from the configuration information; and The processor is also configured to receive the downlink control information by: Obtain a second indication from the configuration information, the second indication specifying multiple serving cells among the one or more serving cells on which the MBS service is transmitted; and Based on the second instruction, the downlink control information is received in the plurality of serving cells.

19. The terminal device according to claim 12, wherein the processor is further configured to: Additional information is received from the network device via physical layer signaling or via media access control layer signaling, the additional information indicating one of the following: The region identifier associated with the data packets of the MBS service, The cell identifier associated with the data packet, Another identifier associated with said one data packet; and Based on the additional information, the data packets are associated with a target serving cell among the one or more serving cells.

20. The terminal device according to claim 12, wherein the processor is further configured to: Based on the configuration information, obtain multiple identifiers corresponding to multiple serving cells in the one or more serving cells; The processor is also configured to receive the downlink control information by: Based on the determination that the configuration information indicates the MBS service is location-dependent or that the content of the MBS services from the plurality of serving cells is different, multiple downlink control information associated with the plurality of identifiers is received in the plurality of serving cells; and wherein the processor is further configured to receive the MBS service by: Receive multiple data packets associated with the MBS service in the plurality of serving cells.

21. The terminal device according to claim 12, wherein the processor is further configured to: Based on the configuration information, obtain multiple identifiers corresponding to multiple serving cells in the one or more serving cells; The processor is also configured to receive the downlink control information by: Based on the determination that the configuration information indicates that the content of the MBS service from the plurality of serving cells is the same, a target serving cell is determined from the plurality of serving cells; Based on the configuration information, a target identifier corresponding to the target serving cell is determined; as well as The processor receives the downlink control information associated with the target identifier in the target serving cell; and the processor is further configured to receive the MBS service by: Receive at least one data packet associated with the MBS service from the target serving cell.

22. The terminal device according to claim 21, wherein the processor is further configured to: Determine another target serving cell from the plurality of serving cells; Receive the downlink control information associated with another target identifier corresponding to the other target serving cell; and wherein the processor is further configured to receive the MBS service by: Receive at least one data packet associated with the MBS service from the target serving cell and the other target serving cell.

23. A processor for wireless communication, comprising: At least one memory; as well as A controller, coupled to the at least one memory, and configured to cause the processor to: Receive configuration information from network devices, the configuration information being related to multicast and broadcast (MBS) services provided in one or more serving cells; Receive the search space configuration of the serving cell from the one or more serving cells from the network device; The downlink control information of the serving cell is associated with an identifier associated with the MBS service, as determined by the search space configuration. The downlink control information is received from the serving cell of the one or more serving cells in which the MBS service is provided. as well as Based on the downlink control information, the MBS service provided in the one or more serving cells is received.

24. The processor of claim 23, wherein the configuration information is received in at least one of the following ways: Radio Resource Control (RRC) reconfiguration message, Radio resource control signaling, or System information block.

25. The processor of claim 23, wherein the configuration information includes at least one of the following: The MBS session information of the MBS service includes at least one of the following: a temporary mobile group identifier associated with the MBS service, or a session identifier associated with the MBS service. Regarding whether the MBS service is location-related. If the MBS service is location-dependent, then at least one area identifier associated with the MBS service, An index used to distinguish the different content of the MBS service received from different serving cells in the serving cell set. Identifiers associated with the MBS service, An indication regarding whether the MBS service is sent on one or more serving cells in the set of serving cells, or Multimedia Broadcast Multicast Service (MBMS) Service Channel (MTCH) scheduling information.

26. The processor of claim 23, wherein the controller is configured to cause the processor to receive the configuration information by: The configuration information is received via a message carrying one of the following: The configuration of the one or more serving cells, The configuration of the data radio bearers associated with the one or more serving cells, Configuration of logical channels associated with the one or more serving cells.

27. The processor of claim 23, wherein the controller is further configured to cause the processor to: The identifier associated with the MBS service is obtained from the configuration information; and wherein the controller is configured to cause the processor to receive the downlink control information by: The configuration information is received from the network device in one or more serving cells, and the downlink control information associated with the identifier is received in the serving cell.

28. The processor of claim 23, wherein the controller is further configured to cause the processor to receive the downlink control information by: Obtain a first indication from the configuration information regarding whether the MBS service is being sent on a serving cell; and Based on the determination that the MBS service is transmitted on a serving cell, and based on the first indication, the downlink control information is received in the serving cell on which the MBS is transmitted.

29. The processor of claim 23, wherein the controller is further configured to cause the processor to: Obtain the identifier associated with the MBS service from the configuration information; and The controller is further configured to enable the processor to receive the downlink control information by: Obtain a second indication from the configuration information, the second indication specifying multiple serving cells among the one or more serving cells on which the MBS service is transmitted; and Based on the second instruction, the downlink control information is received in the plurality of serving cells.

30. The processor of claim 23, wherein the controller is further configured to cause the processor to: Additional information is received from the network device via physical layer signaling or via media access control layer signaling, the additional information indicating one of the following: The region identifier associated with the data packets of the MBS service, The cell identifier associated with the data packet, Another identifier associated with said one data packet; and Based on the additional information, the data packets are associated with a target serving cell among the one or more serving cells.

31. The processor of claim 23, wherein the controller is further configured to cause the processor to: Based on the configuration information, obtain multiple identifiers corresponding to multiple serving cells in the one or more serving cells; The controller is further configured to enable the processor to receive the downlink control information by: Based on the determination that the configuration information indicates the MBS service is location-dependent or that the content of the MBS services from the plurality of serving cells is different, multiple downlink control information associated with the plurality of identifiers is received in the plurality of serving cells; and wherein the controller is further configured to cause the processor to receive the MBS service by: Receive multiple data packets associated with the MBS service in the plurality of serving cells.

32. A computer-readable storage medium having program code stored thereon, the program code being configured to cause a device to perform the method according to any one of claims 1 to 11 when executed.

Images