CN114143722B

CN114143722B - Method and device for receiving and sending multicast service, storage medium, terminal and base station

Info

Publication number: CN114143722B
Application number: CN202010814819.7A
Authority: CN
Inventors: 邓云; 顾祥新
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2020-08-13
Filing date: 2020-08-13
Publication date: 2023-04-28
Anticipated expiration: 2040-08-13
Also published as: WO2022033505A1; CN114143722A

Abstract

A receiving and sending method, device, storage medium, terminal, base station of multicast service, the receiving method includes: determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0; and adjusting the receiving bandwidth of the self to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service. The scheme of the invention can meet the low power consumption requirement of the UE and timely transmission of the multicast service.

Description

Method and device for receiving and sending multicast service, storage medium, terminal and base station

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a storage medium, a terminal, and a base station for receiving and transmitting a multicast service.

Background

According to the existing protocol, a User Equipment (UE) currently in idle or inactive state will reside in an Initial portion of the bandwidth (Initial Bandwidth Part, initial BWP) of the serving cell. And the downlink reception bandwidth (hereinafter simply referred to as reception bandwidth) of the UE is equal to the reception bandwidth of the control-resource set 0 (hereinafter simply referred to as CORESET 0).

After the introduction of the multimedia broadcast multicast service (Multimedia Broadcast Multicast Service, abbreviated MBMS, hereinafter abbreviated as multicast service), if the MBMS service is limited within the reception bandwidth of CORESET 0, the reception bandwidth of CORESET 0 may be wide to ensure the timely transmission of the MBMS service, which is disadvantageous for the power saving of UEs not receiving the MBMS service.

If the bandwidth of CORESET 0 is too narrow, the MBMS service may not be transmitted in time.

Therefore, there is a need for an efficient multicast service transmission manner that can satisfy low power consumption of a UE and ensure timely transmission of multicast service.

Disclosure of Invention

The technical problem solved by the invention is how to provide an efficient multicast service transmission mode so as to consider the low power consumption requirement of UE and the timely transmission of multicast service.

In order to solve the above technical problems, an embodiment of the present invention provides a method for receiving a multicast service, including: determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0; and adjusting the receiving bandwidth of the self to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service.

Optionally, the receiving method further includes: and receiving the system message and/or paging on the receiving bandwidth corresponding to the multicast service.

Optionally, the adjusting the self receiving bandwidth to the receiving bandwidth corresponding to the multicast service includes: and adjusting the self receiving bandwidth from the receiving bandwidth of CORESET 0 to the receiving bandwidth corresponding to the multicast service.

Optionally, the receiving method further includes: and when the data of the multicast service does not need to be received, recovering the self receiving bandwidth from the receiving bandwidth corresponding to the multicast service to the receiving bandwidth of the CORESET 0.

Optionally, the receiving method further includes: and receiving configuration information, wherein the configuration information comprises the association relation between at least one multicast service and the receiving bandwidth.

Optionally, the configuration information is carried through a system message or an SC-MCCH.

Optionally, when different multicast services multiplex the same search space, the configuration information indicates the number of physical resource blocks corresponding to the receiving bandwidths corresponding to the different multicast services by using the same bit number, where the number of physical resource blocks corresponding to the receiving bandwidths corresponding to the different multicast services is the same or different.

Optionally, when different multicast services adopt different search spaces, for each multicast service, the configuration information determines, according to the number of physical resource blocks corresponding to the receiving bandwidths corresponding to the multicast service, the number of bits indicating the number.

Optionally, when there are a plurality of multicast services to be received, the adjusting the self receiving bandwidth to the receiving bandwidth corresponding to the multicast service includes: and adjusting the receiving bandwidth of the self to the receiving bandwidth with the largest coverage bandwidth in the receiving bandwidths corresponding to the multicast services to be received, wherein the receiving bandwidth with the largest coverage bandwidth covers the rest of the receiving bandwidths in the receiving bandwidths corresponding to the multicast services to be received.

Optionally, the lowest physical resource block corresponding to the receiving bandwidth corresponding to the multicast service is aligned with the lowest physical resource block of CORESET 0.

Optionally, the lowest physical resource block corresponding to the receiving bandwidth corresponding to the multicast service is aligned with the lowest physical resource block of the initial BWP.

Optionally, the receiving bandwidth corresponding to the multicast service is equal to or greater than the initial BWP.

Optionally, the size of the receiving bandwidth corresponding to the multicast service is determined according to the service quality parameter of the multicast service.

In order to solve the above technical problem, an embodiment of the present invention further provides a receiving device for a multicast service, including: a determining module, configured to determine a receiving bandwidth corresponding to the multicast service, where different multicast services correspond to the same or different receiving bandwidths, and each receiving bandwidth corresponding to the multicast service at least covers a receiving bandwidth of CORESET 0; and the adjusting module is used for adjusting the receiving bandwidth of the self to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service.

In order to solve the above technical problem, the embodiment of the present invention further provides a method for sending a multicast service, including: determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0; and transmitting the data of the multicast service on the receiving bandwidth corresponding to the multicast service.

Optionally, the sending method further includes: and sending configuration information, wherein the configuration information comprises the association relation between at least one multicast service and the receiving bandwidth.

In order to solve the above technical problem, an embodiment of the present invention further provides a device for sending a multicast service, including: a determining module, configured to determine a receiving bandwidth corresponding to the multicast service, where different multicast services correspond to the same or different receiving bandwidths, and each receiving bandwidth corresponding to the multicast service at least covers a receiving bandwidth of CORESET 0; and the sending module is used for sending the data of the multicast service on the receiving bandwidth corresponding to the multicast service.

To solve the above technical problem, an embodiment of the present invention further provides a storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the above method.

In order to solve the technical problem, the embodiment of the invention also provides a terminal, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the steps of the method when running the computer program.

To solve the above technical problem, an embodiment of the present invention further provides a base station, including a memory and a processor, where the memory stores a computer program capable of running on the processor, and the processor executes steps of the above method when running the computer program.

Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:

for the UE side, the embodiment of the present invention provides a method for receiving a multicast service, including: determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0; and adjusting the receiving bandwidth of the self to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service.

The implementation method can meet the low power consumption requirement of the UE and timely transmission of the multicast service. Specifically, the variable multicast service receiving bandwidth mechanism adopted in this embodiment enables different multicast services to correspond to different receiving bandwidths, and the UE interested in a specific multicast service can adjust its receiving bandwidth based on the receiving bandwidth corresponding to the multicast service to receive data. Further, the receiving bandwidths corresponding to the multicast services all cover the receiving bandwidth of CORESET 0, so that the UE can receive system messages, paging and the like while receiving the multicast services without adjusting the receiving bandwidth.

For the base station side, the embodiment of the invention also provides a method for sending the multicast service, which comprises the following steps: determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0; and transmitting the data of the multicast service on the receiving bandwidth corresponding to the multicast service.

Therefore, under the condition of introducing the multicast service, the situation that the network needs to configure a larger CORESET 0 receiving bandwidth is avoided, and the power consumption of the UE which does not need to receive the multicast service is increased. Meanwhile, reasonable receiving bandwidths are set for different multicast services, so that the remarkable increase of power consumption of the UE can be avoided, and load balancing of the base station in the process of initial access of a large number of UEs can be considered.

Drawings

Fig. 1 is a flowchart of a method for receiving a multicast service according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a receiving bandwidth configuration of a first exemplary application scenario according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a receiving bandwidth configuration of a second exemplary application scenario according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a receiving device for multicast service according to an embodiment of the present invention;

fig. 5 is a flowchart of a method for transmitting multicast service according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a multicast service transmitting apparatus according to an embodiment of the present invention.

Detailed Description

As described in the background art, after the MBMS service is introduced, the existing data transmission method cannot meet the low power consumption requirement of the UE and the timely transmission requirement of the multicast service.

Specifically, an MBMS multimedia broadcast multicast function will be introduced in New Radio (NR for short). A single cell point-to-multipoint (Single Cell Point to Multipoint, SC-PTM for short) mechanism will be employed, i.e. each cell independently schedules the transmission of the multicast service.

The SC-PTM mechanism in long term evolution (Long Term Evolution, abbreviated LTE) provides a list of all MBMS services transmitted on a single cell multicast traffic channel (Single Cell Multicast Transport Channel, abbreviated SC-MTCH) for a single cell multicast control channel (Single Cell Multicast Control Channel, abbreviated SC-MCCH). Wherein, the list may include a temporary mobile group identifier (Temporary Mobile Group Identity, abbreviated as TMGI) of each MBMS service, a service (session) identifier, a group radio network temporary identifier (Group Radio Network Temporary Identity, abbreviated as G-RNTI) and scheduling information.

Further, the base station transmits the SC-MCCH in each SC-MCCH repetition period through radio resource control (Radio Resource Control, abbreviated as RRC). The SC-MCCH adopts a modification period and is transmitted for a plurality of times in one modification period.

The UE acquires the G-RNTI of the interested MBMS service through the SC-MCCH, and then detects DCI scrambled by the RNTI in the corresponding subframe according to the scheduling information, thereby acquiring the multicast data transmitted on the downlink shared channel.

In the NR system, the maximum channel bandwidth of each carrier is 400 megahertz (MHz), which is far more than the 20MHz bandwidth of the LTE system. In initial access, if the UE directly accesses the bandwidth of 400MHz, not only the hardware cost of the UE is high, but also larger power consumption is caused. Thus, the NR system introduces a partial Bandwidth Part (BWP) concept.

In an NR system, each cell may contain one or more BWP, each BWP occupying a limited bandwidth, at least one BWP allowing an idle state user equipment to camp on, through which an idle state UE receives a system message and a paging message, thereby establishing an RRC connection and a data radio bearer by an access network. This BWP is called initial BWP (initial BWP).

For the same UE, after the UE access network establishes an RRC connection, the base station may configure the UE with a plurality of BWP according to user equipment capability, service requirements, and the like. Each UE may have at least one active BWP. For example, for a UE in carrier aggregation, there may be one active BWP per serving cell on multiple active serving cells.

For each BWP, a series of configuration parameters, such as a location parameter of an occupied physical resource block, and a control resource set (Control Resource Set, abbreviated as CORESET) configuration parameter, a downlink physical shared channel (Physical Downlink Shared channel, abbreviated as PDSCH) configuration parameter, an uplink physical control channel (Physical Uplink Control Channel, abbreviated as PUCCH) configuration parameter, an uplink physical shared channel (Physical Uplink Shared channel, abbreviated as PUSCH) configuration parameter, a reference signal, a random access channel (Random Access Channel, abbreviated as RACH) configuration parameter, and the like, are corresponding. The user equipment can apply the BWP only after learning the configuration parameters corresponding to the BWP.

In protocol version 15 (Release 15, R15 for short), the base station may configure the UE with multiple BWP, e.g. up to 4 BWP, for one serving cell. But only one of them is an active BWP, i.e., the UE can only receive downlink control information (Downlink Control Information, DCI for short) of the base station through the BWP, receive data from the BWP, and transmit data to the base station through the BWP.

On activated BWP, the UE detects its own DCI at the configured CORESET or coreets. For each CORESET, there may be two search spaces: a common search space and a UE-specific search space. And the UE blindly detects the DCI in the search space according to a certain rule, detects the DCI belonging to the UE according to the RNTI of the UE, and then receives data or uploads the data according to the DCI. One UE may have one or more RNTIs.

The base station may switch the BWP in which the UE operates, i.e., switch the activation BWP (Active BWP) of the UE, according to the need of the UE to actually operate and the load status of the different BWP. The base station may switch the BWP of the UE through the DCI. The UE side may configure a BWP inactivity timer (BWP-inactivity timer) that when exceeded, the UE will actively switch BWP and will switch to default BWP (default BWP). Wherein the default BWP is configured by the base station.

For an idle or Inactive (Inactive) UE, when it camps on a serving cell, it typically camps on the initial BWP of the serving cell. The UE may normally receive the system message and the paging message in the initial BWP, and if there is a service requirement, the UE may initiate random access to establish RRC connection in the initial BWP, and further establish a data radio bearer to perform a service.

The initial BWP includes CORESET 0, and the network may generally configure the receiving bandwidth of the initial BWP to be equal to or greater than the receiving bandwidth of CORESET 0. The UE may detect DCI through the search space mapped on CORESET 0 and may receive a system information block (System Information Block, SIB for short), paging, and random access response. Wherein the DCI indicates a system information block, paging, and a physical resource block used for a random access response.

For idle or inactive UEs, when camping on the initial BWP, the reception bandwidth of the UE is the reception bandwidth of CORESET 0, and the network will ensure that the system messages, paging and random access response at the initial access are limited within the reception bandwidth of CORESET 0, so that the UE can save more power.

When the UE needs to access the network, the network may configure the BWP that the UE works with through a Message 4 (MSG 4 for short) in a random access procedure, for example, may be an initial BWP, or other BWP. The UE adjusts its own downlink reception bandwidth when receiving the MSG 4.

After the MBMS service is introduced, the MBMS service is likely to be deployed in the initial BWP from the resource efficiency point of view. The following problems will arise:

if the bandwidth of the initial BWP or CORESET 0 is too narrow, more MBMS services and initial access of the UE may not be carried, which affects the transmission timeliness of the multicast service.

If the initial BWP is too wide, the UE not receiving the MBMS service consumes much power when receiving according to the initial BWP.

Therefore, an efficient multicast service transmission mode is required to be capable of satisfying both the low power consumption requirement of the UE and the timely transmission of the multicast service.

In order to make the above objects, features and advantages of the present invention more comprehensible, embodiments accompanied with figures are described in detail below.

Fig. 1 is a flowchart of a method for receiving a multicast service according to an embodiment of the present invention.

Specifically, the multicast service may be an MBMS service.

The embodiment can be applied to an NR system and introduces an application scene of MBMS service. For example, for an NR cell supporting SC-PTM, the present embodiment may be used to transmit multicast services to UEs in different states within the cell. The different states include an RRC connected state, an idle state, and an inactive state.

The present embodiment may be performed by the user equipment side, such as by the UE at the user equipment side. For example, the present embodiment may be performed by a UE in an inactive state or an idle state.

More specifically, referring to fig. 1, the method for receiving a multicast service according to the present embodiment may include the following steps:

step S101, determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0;

here, the received bandwidths corresponding to the multicast service being broadcast or to be broadcast are determined for one NR cell, that is, the NR cell, and each of the different received bandwidths or the same received bandwidth corresponding to the multicast service at least covers the received bandwidth of CORESET 0 of the NR cell.

Step S102, self receiving bandwidth is adjusted to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service.

In one implementation, before the step S101, the receiving method of this embodiment may further include the steps of: and receiving configuration information, wherein the configuration information comprises the association relation between at least one multicast service and the receiving bandwidth.

In particular, the configuration information may be carried through a system message or an SC-MCCH.

For example, the network may configure a corresponding receiving bandwidth for an MBMS service that may be transmitted by the NR cell in advance, and indicate the corresponding receiving bandwidth to a UE accessing the NR cell through configuration information.

For example, configuration information may be included in DCI.

Further, for all MBMS services that may be transmitted by the NR cell, the all MBMS services may correspond to the same reception bandwidth. All MBMS services herein refer to an MBMS service being broadcast or an MBMS service to be broadcast. When all the MBMS services correspond to the same receiving bandwidth, the configuration information does not need to indicate the association relation between the multicast service and the receiving bandwidth, and only needs to configure one common receiving bandwidth.

Alternatively, a part of the MBMS service may correspond to the same reception bandwidth, and the remaining part of the MBMS service corresponds to another different reception bandwidth.

Or, each MBMS service is provided with a corresponding receiving bandwidth.

Further, if no corresponding receiving bandwidth is set in the configuration information, the MBMS service defaults to a receiving bandwidth of CORESET 0 or a downlink receiving bandwidth of initial BWP.

In one implementation, when different multicast services multiplex the same search space, the configuration information may indicate the number of physical resource blocks corresponding to the receiving bandwidths corresponding to the different multicast services by using the same number of bits, where the number of physical resource blocks corresponding to the receiving bandwidths corresponding to the different multicast services is the same or different.

Since the number of physical resource blocks (Physical Resource Block, abbreviated PRBs) corresponding to different reception bandwidths is different, if different MBMS services multiplex the same search space (search space), DCI needs to use PRB bits with the same length to indicate allocated resources. Specifically, the number of PRB bits indicating the PDSCH in DCI for scheduling the MBMS service may be uniformly set by a system message or MCCH.

For example, assuming that the number of PRBs corresponding to the reception bandwidth 1 corresponding to the MBMS service 1 is 30, 5 bits may represent the allocation of these PRBs (the number of bits required for different resource allocation schemes is different, and here, it is assumed that only an index representing each PRB is required). Assuming that the number of PRBs corresponding to the reception bandwidth 2 corresponding to the MBMS service 2 is 100, 7 bits are required to represent allocation of the PRBs. In order to avoid that the number of PRBs needs to represent the resource allocation by a different number of bits, in this embodiment, the number of PRB bits indicating PDSCH in DCI for scheduling MBMS service may be uniformly set by a system message or MCCH. If the number of PRBs can be indicated by 7 bits in the DCI in a unified manner, 7 bits can be added to the reception bandwidth 1 requiring only 5 bits by zero addition of the number of unused bits.

In one implementation, when different multicast services use different search spaces, for each multicast service, the configuration information may determine, according to the number of physical resource blocks corresponding to the reception bandwidth corresponding to the multicast service, the number of bits indicating the number.

If different MBMS services employ different search spaces, DCI may indicate allocated resources using respectively different numbers of bits. The number of bits specifically required may be determined by the reception bandwidth corresponding to the MBMS service.

For example, assuming that MBMS service 1 corresponds to search space 1, the UE knows that 5 bits indicate a physical resource block when it decodes DCI. The DCI may indicate resource allocation information of the PRB corresponding to the reception bandwidth 1 corresponding to the MBMS service 1 with 5 bits.

For another example, it is assumed that MBMS service 2 corresponds to search space 2, and the ue knows that 7 bits indicate a physical resource block when it decodes DCI. The DCI may indicate the resource allocation information of the PRB corresponding to the reception bandwidth 2 corresponding to the MBMS service 2 with 7 bits.

In one implementation, the lowest physical resource block corresponding to the received bandwidth corresponding to the multicast service may be aligned with the lowest physical resource block of CORESET 0.

Specifically, after taking the lowest physical resource block of CORESET0 as a reference, the bandwidth amount extended on the basis of CORESET0 can be determined according to the quality of service parameters of the corresponding MBMS service, the number of UEs accessing the cell (especially the number of UEs switching from the idle state to the connected state), the traffic amount of the accessing UEs, and other factors.

For example, if there are more UEs in the connection state from the idle state among the UEs in the access cell, the transmission resources in CORESET 0 may be occupied much, and a portion of the corresponding receiving bandwidth of the MBMS service exceeding the receiving bandwidth of CORESET 0 may be allocated a bit more appropriately.

In one implementation, the size of the receiving bandwidth corresponding to the multicast service may be determined according to a quality of service parameter of the multicast service.

Specifically, MBMS services of the same or similar quality of service parameters may correspond to the same reception bandwidth.

Further, the quality of service parameters may include an amount of transmission data, a transmission rate, and the like.

In one implementation, before/after/at the same time of performing the step S102, the receiving method of the present embodiment may further include the steps of: and receiving the system message and/or paging on the receiving bandwidth corresponding to the multicast service.

Because the receiving bandwidth corresponding to the multicast service covers the receiving bandwidth of CORESET 0, the UE can receive the data and the paging of the MBMS service, the random access response and the system message at the same time without adjusting the receiving bandwidth, and the timing of the base station for transmitting the data of the MBMS service and the timing of the paging, the system message and the random access response can be the same or different.

In one implementation, the step S102 may include the steps of: and adjusting the self receiving bandwidth from the receiving bandwidth of CORESET 0 to the receiving bandwidth corresponding to the multicast service.

In a typical application scenario, it is assumed that 3 MBMS services, referred to as service 1 (session 1), service 2 (session 2) and service 3 (session 3), respectively, need to be transmitted by the NR cell for a period of time.

The service characteristics of these three different MBMS services differ significantly. For example, service 1 needs a larger bandwidth each time to transmit more data, while service 2 and service 3 need less data to be transmitted each time, and can complete one data transmission without needing a large transmission resource.

For the application scenario, the base station may configure different receiving bandwidths for different MBMS services, for example, the receiving bandwidth of the configured service 1 is the largest, and the receiving bandwidths of the configured service 2 and the configured service 3 are all 30MHz. In this application scenario, assume that the reception bandwidth of CORESET 0 is 20MHz and the reception bandwidth of initial BWP is 50MHz.

Referring to fig. 2, fig. 2 illustrates a configuration of a receiving bandwidth 1 corresponding to a service 1 and a receiving bandwidth 2 corresponding to a service 2 and a service 3 in common in the present application scenario.

As can be seen from fig. 2, the reception bandwidth 1 and the reception bandwidth 2 each include CORESET 0, and are each based on the lowest physical resource block of CORESET 0. Wherein the receiving bandwidth 2 comprises 30MHz and the receiving bandwidth 1 comprises 40MHz.

That is, for the service 2 and the service 3, the base station ensures that scheduling of the two MBMS services is limited to 30MHz of the reception bandwidth 2 as shown in fig. 2, while the base station may indicate to the UE that the reception bandwidths 2 of the service 2 and the service 3 are 30MHz through a system message or MCCH.

Accordingly, after acquiring the receiving bandwidths 2 corresponding to the service 2 and the service 3, the UE interested in the service 2 and the service 3 (currently in an idle state or an inactive state) can adjust its receiving bandwidth from the original receiving bandwidth of receiving CORESET 0 to the receiving bandwidth of receiving 30MHz.

Since this 30MHz contains CORESET 0, the UE can also receive system messages and pages when receiving service 2 and/or service 3, without affecting the UE's camping procedure.

The base station will ensure that the resource allocation for service 2 and service 3 is limited to 30MHz as shown in fig. 2 to ensure that the UE can receive the MBMS service 2 and service 3 of interest without readjusting the reception bandwidth.

Similarly, when the UE interested in service 1 acquires that the receiving bandwidth 1 corresponding to service 1 is 40MHz, the UE may adjust its receiving bandwidth from the original receiving CORESET 0 to the receiving bandwidth of 40MHz.

In one implementation, after the step S102, the receiving method of this embodiment may further include the steps of: and when the data of the multicast service does not need to be received, recovering the self receiving bandwidth from the receiving bandwidth corresponding to the multicast service to the receiving bandwidth of the CORESET 0.

For example, when the UE is no longer interested in the MBMS service, it may camp on the initial BWP of the cell and recover the downlink reception bandwidth to the bandwidth of CORESET 0.

In one implementation, the lowest physical resource block corresponding to the reception bandwidth corresponding to the multicast service may be aligned with the lowest physical resource block of the initial BWP.

For example, referring to fig. 3, the reception bandwidth 1 corresponding to the multicast service 1 is based on the lowest physical resource block of the initial BWP and covers at least CORESET 0.

In one implementation, the reception bandwidth corresponding to the multicast service may be equal to or greater than the initial BWP.

For example, referring to fig. 3, the reception bandwidth 2 corresponding to the multicast service 2 is based on the lowest physical resource block of the initial BWP and is greater than the initial BWP.

In one implementation, when there are multiple multicast services to be received, in the step S101, the receiving bandwidths corresponding to the respective multicast services to be received may be determined one by one.

Further, the step S102 may include the steps of: and adjusting the receiving bandwidth of the self to the receiving bandwidth with the largest coverage bandwidth in the receiving bandwidths corresponding to the multicast services to be received, wherein the receiving bandwidth with the largest coverage bandwidth covers the rest of the receiving bandwidths in the receiving bandwidths corresponding to the multicast services to be received.

That is, if the UE is interested in a plurality of multicast services at the same time, the maximum value of the reception bandwidths corresponding to the plurality of multicast services is taken, that is, the reception bandwidth selected last completely covers the reception bandwidth corresponding to the plurality of multicast services.

Therefore, for the UE side, the embodiment can give consideration to the low power consumption requirement of the UE and the timely transmission of the multicast service. Specifically, the variable multicast service receiving bandwidth mechanism adopted in this embodiment enables different multicast services to correspond to different receiving bandwidths, and the UE interested in a specific multicast service can adjust its receiving bandwidth based on the receiving bandwidth corresponding to the multicast service to receive data. Further, the receiving bandwidth corresponding to each multicast service covers the receiving bandwidth of CORESET 0, so that the UE can always receive a system message, paging, etc. while receiving the multicast service.

Fig. 4 is a schematic structural diagram of a receiving device for multicast service according to an embodiment of the present invention. It will be appreciated by those skilled in the art that the receiving device 4 for multicast service according to the present embodiment may be used to implement the method technical solutions described in the embodiments described in fig. 1 to 3.

Specifically, referring to fig. 4, the receiving apparatus 4 for multicast service according to the present embodiment may include: a determining module 41, configured to determine a receiving bandwidth corresponding to the multicast service, where different multicast services correspond to the same or different receiving bandwidths, and each receiving bandwidth corresponding to the multicast service at least covers a receiving bandwidth of CORESET 0; and the adjusting module 42 is configured to adjust the receiving bandwidth to a receiving bandwidth corresponding to the multicast service, so as to receive the data of the multicast service.

For more details on the working principle and the working manner of the multicast service receiving device 4, reference may be made to the related descriptions in fig. 1 to 3, which are not repeated here.

Fig. 5 is a flowchart of a method for transmitting a multicast service according to an embodiment of the present invention.

The solution of this embodiment may be executed by the network side, for example, by the base station of the network side.

In particular, the base station may jurisdiction one or more NR cells, and the NR cells support an SC-PTM mechanism. The NR cell may transmit data of at least one multicast service to UEs within the cell. The UE may be in an idle state or, inactive state or connected state.

More specifically, referring to fig. 5, the method for sending a multicast service according to the present embodiment may include the following steps:

step S501, determining a receiving bandwidth corresponding to the multicast service, where different multicast services correspond to the same or different receiving bandwidths, and each receiving bandwidth corresponding to the multicast service at least covers a receiving bandwidth of CORESET 0;

step S502, data of the multicast service is sent on the receiving bandwidth corresponding to the multicast service.

That is, the base station may configure different reception bandwidths for different MBMS services, and may be configured through system information (System Information, abbreviated SI) or configured through MCCH.

Further, the base station ensures that scheduling of a particular MBMS service is limited to the reception bandwidth allocated to this MBMS service.

It will be appreciated by those skilled in the art that the steps S501 to S502 may be regarded as steps corresponding to the steps S101 to S102 described in the embodiment shown in fig. 1, and the two steps complement each other in terms of specific implementation principles and logic. Thus, the explanation of the nouns in this embodiment may refer to the related description of the embodiment shown in fig. 1, which is not repeated here.

In one implementation, before performing the step 501, the sending method according to this embodiment may further include the steps of: and sending configuration information, wherein the receiving configuration information comprises the association relation between at least one multicast service and the receiving bandwidth.

For example, for a UE in idle or inactive state, after the UE camps on a serving cell governed by the base station, the base station may send the configuration information to the UE through a system message or SC-MCCH. For the UE in the connected state, the configuration information may also be obtained through a system message or SC-MCCH, and the base station may also send the configuration information to the UE through dedicated signaling.

In this embodiment, when the network reasonably configures the receiving bandwidths corresponding to the MBMS service, that is, considers the data size of the MBMS service, and also considers the resource consumption required by the initial access of the UE, and also considers the power consumption problem that the receiving bandwidths of the UE are too large, so that the receiving bandwidths corresponding to different MBMS services are reasonably configured.

In a variation, when different multicast services use different search spaces, the configuration information may determine, for each multicast service, a number of bits indicating the number according to a number of physical resource blocks corresponding to a reception bandwidth corresponding to the multicast service.

In a variation, the lowest physical resource block corresponding to the received bandwidth corresponding to the multicast service may be aligned with the lowest physical resource block of the initial BWP.

Further, the reception bandwidth corresponding to the multicast service may be equal to or greater than the initial BWP.

In an implementation, the size of the receiving bandwidth corresponding to the multicast service may be determined according to a quality of service parameter of the multicast service, and indicated to the UE in advance by configuration information.

In one implementation, for a UE in a connected state, when the UE indicates an MBMS service of interest to the UE, the base station may reasonably configure the active BWP of the UE. For example, it may be ensured that the active BWP configured to the UE covers at least the reception bandwidth of the MBMS service of interest to the UE.

By the above, for the network side, under the condition of introducing the multicast service, the network is prevented from configuring a larger CORESET 0 receiving bandwidth, so that the power consumption of the UE which does not need to receive the multicast service is increased. Meanwhile, reasonable receiving bandwidths are set for different multicast services, so that the remarkable increase of power consumption of the UE can be avoided, and load balancing of the base station in the process of initial access of a large number of UEs can be considered.

Fig. 6 is a schematic structural diagram of a multicast service transmitting apparatus according to an embodiment of the present invention. Those skilled in the art will understand that the sending device 6 of the multicast service according to the present embodiment may be used to implement the method technical solution described in the embodiment of fig. 5.

Specifically, referring to fig. 6, the sending device 6 of the multicast service according to the present embodiment may include: a determining module 61, configured to determine a receiving bandwidth corresponding to the multicast service, where different multicast services correspond to the same or different receiving bandwidths, and each receiving bandwidth corresponding to the multicast service at least covers a receiving bandwidth of CORESET 0; and the sending module 62 is configured to send the data of the multicast service on the receiving bandwidth corresponding to the multicast service.

For more details of the working principle and the working manner of the multicast service transmitting device 6, reference may be made to the related description in fig. 5, which is not repeated here.

Further, the embodiment of the invention also discloses a storage medium, on which a computer program is stored, which when being executed by a processor, performs the technical solutions of the method described in the embodiments shown in fig. 1 to 3. Alternatively, the computer program is executed by the processor to perform the method technical solution described in the embodiment shown in fig. 5. Preferably, the storage medium may include a computer-readable storage medium such as a non-volatile (non-volatile) memory or a non-transitory (non-transitory) memory. The storage medium may include ROM, RAM, magnetic or optical disks, and the like.

Further, the embodiment of the invention also discloses a terminal, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the technical scheme of the method in the embodiment shown in the figures 1 to 3 when running the computer program. Specifically, the terminal may be a UE, such as a UE in an NB system.

Further, the embodiment of the invention also discloses a base station, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the technical scheme of the method in the embodiment shown in fig. 5 when running the computer program. In particular, the base station may be a base station in an NB system.

Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be made by one skilled in the art without departing from the spirit and scope of the invention, and the scope of the invention should be assessed accordingly to that of the appended claims.

Claims

1. A method for receiving multicast service, comprising:

determining the receiving bandwidths corresponding to the multicast service, wherein different multicast services correspond to the same or different receiving bandwidths, and the receiving bandwidth corresponding to each multicast service at least covers the receiving bandwidth of CORESET 0;

adjusting the self receiving bandwidth to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service;

further comprises: and receiving configuration information, wherein the configuration information comprises an association relation between at least one multicast service and a receiving bandwidth, and when different search spaces are adopted by different multicast services, for each multicast service, the configuration information determines the bit number indicating the number according to the number of physical resource blocks corresponding to the receiving bandwidth corresponding to the multicast service.

2. The receiving method according to claim 1, characterized by further comprising:

And receiving the system message and/or paging on the receiving bandwidth corresponding to the multicast service.

3. The receiving method according to claim 1, wherein the adjusting the self-receiving bandwidth to the receiving bandwidth corresponding to the multicast service includes:

and adjusting the self receiving bandwidth from the receiving bandwidth of CORESET 0 to the receiving bandwidth corresponding to the multicast service.

4. The receiving method according to claim 1, characterized by further comprising:

and when the data of the multicast service does not need to be received, recovering the self receiving bandwidth from the receiving bandwidth corresponding to the multicast service to the receiving bandwidth of the CORESET 0.

5. The receiving method according to claim 1, wherein the configuration information is carried through a system message or an SC-MCCH.

6. The receiving method according to claim 1, wherein the configuration information indicates the number of physical resource blocks corresponding to the reception bandwidths corresponding to the different multicast services using the same number of bits when the different multicast services multiplex the same search space, wherein the number of physical resource blocks corresponding to the reception bandwidths corresponding to the different multicast services is the same or different.

7. The receiving method according to claim 1, wherein when there are a plurality of multicast services to be received, said adjusting the own reception bandwidth to the reception bandwidth corresponding to the multicast service includes: and adjusting the receiving bandwidth of the self to the receiving bandwidth with the largest coverage bandwidth in the receiving bandwidths corresponding to the multicast services to be received, wherein the receiving bandwidth with the largest coverage bandwidth covers the rest of the receiving bandwidths in the receiving bandwidths corresponding to the multicast services to be received.

8. The receiving method according to any one of claims 1 to 7, characterized in that the lowest physical resource block corresponding to the receiving bandwidth corresponding to the multicast service is aligned with the lowest physical resource block of CORESET 0.

9. The receiving method according to any one of claims 1 to 7, wherein a lowest physical resource block corresponding to a receiving bandwidth corresponding to the multicast service is aligned with a lowest physical resource block of an initial BWP.

10. The receiving method according to claim 9, wherein the multicast service has a corresponding receiving bandwidth equal to or greater than the initial BWP.

11. The receiving method according to any one of claims 1 to 7, wherein the size of the receiving bandwidth corresponding to the multicast service is determined according to a quality of service parameter of the multicast service.

12. A receiving apparatus for multicast services, comprising:

a determining module, configured to determine a receiving bandwidth corresponding to the multicast service, where different multicast services correspond to the same or different receiving bandwidths, and each receiving bandwidth corresponding to the multicast service at least covers a receiving bandwidth of CORESET 0;

the adjustment module is used for adjusting the self receiving bandwidth to the receiving bandwidth corresponding to the multicast service so as to receive the data of the multicast service;

The receiving device further performs the steps of: and receiving configuration information, wherein the configuration information comprises an association relation between at least one multicast service and a receiving bandwidth, and when different search spaces are adopted by different multicast services, for each multicast service, the configuration information determines the bit number indicating the number according to the number of physical resource blocks corresponding to the receiving bandwidth corresponding to the multicast service.

13. A method for transmitting multicast service, comprising:

transmitting data of the multicast service on a receiving bandwidth corresponding to the multicast service;

further comprises: and sending configuration information, wherein the configuration information comprises the association relation between at least one multicast service and a receiving bandwidth, and when different search spaces are adopted by different multicast services, for each multicast service, the configuration information determines the bit number indicating the number according to the number of physical resource blocks corresponding to the receiving bandwidth corresponding to the multicast service.

14. The transmission method according to claim 13, wherein the configuration information is carried through a system message or an SC-MCCH.

15. The transmission method according to claim 13, wherein when different multicast services multiplex the same search space, the configuration information indicates the number of physical resource blocks corresponding to the reception bandwidths corresponding to the different multicast services with the same number of bits, and wherein the number of physical resource blocks corresponding to the reception bandwidths corresponding to the different multicast services is the same or different.

16. The transmission method according to any one of claims 13 to 15, wherein a lowest physical resource block corresponding to a reception bandwidth corresponding to the multicast service is aligned with a lowest physical resource block of CORESET 0.

17. The transmission method according to any one of claims 13 to 15, wherein a lowest physical resource block corresponding to a reception bandwidth corresponding to the multicast service is aligned with a lowest physical resource block of an initial BWP.

18. The transmission method of claim 17, wherein the multicast service has a corresponding reception bandwidth equal to or greater than the initial BWP.

19. The transmission method according to any one of claims 13 to 15, wherein the size of the reception bandwidth corresponding to the multicast service is determined according to a quality of service parameter of the multicast service.

20. A transmission apparatus for multicast service, comprising:

a sending module, configured to send data of the multicast service on a receiving bandwidth corresponding to the multicast service;

the transmitting apparatus further performs the steps of: and sending configuration information, wherein the configuration information comprises the association relation between at least one multicast service and a receiving bandwidth, and when different search spaces are adopted by different multicast services, for each multicast service, the configuration information determines the bit number indicating the number according to the number of physical resource blocks corresponding to the receiving bandwidth corresponding to the multicast service.

21. A storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the method of any of claims 1 to 11 or any of claims 13 to 19.

22. A terminal comprising a memory and a processor, the memory having stored thereon a computer program capable of being run on the processor, characterized in that the processor executes the steps of the method according to any of claims 1 to 11 when the computer program is run on the processor.

23. A base station comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, characterized in that the processor executes the steps of the method according to any of claims 13 to 19 when the computer program is executed by the processor.