CN115804064A

CN115804064A - MBS (multicast broadcast multicast service) receiving method and device and terminal equipment

Info

Publication number: CN115804064A
Application number: CN202080102718.5A
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-10
Filing date: 2020-07-10
Publication date: 2023-03-14
Also published as: WO2022006888A1; CN116744240A

Abstract

The embodiment of the application provides a receiving method and a device of MBS service and terminal equipment, wherein the method comprises the following steps: the terminal equipment receives MBS service sent by a first cell according to a unicast mode and receives MBS service sent by the first cell according to a multicast mode; and the terminal equipment combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or repeatedly detects the MBS service on a packet data convergence protocol PDCP layer.

Description

MBS (multicast broadcast multicast service) service receiving method and device and terminal equipment

Technical Field

The embodiment of the present application relates to the technical field of mobile communications, and in particular, to a method and an apparatus for receiving a Multimedia multicast Service (MBS) Service, and a terminal device.

Background

In a cell, a base station can issue MBS service according to a multicast mode, and also can issue MBS service for a specific user according to a unicast mode. How to improve the reliability of receiving the MBS service in a cell by the terminal device needs to be solved.

Disclosure of Invention

The embodiment of the application provides a method and a device for receiving MBS service and terminal equipment.

The receiving method of the MBS service provided in the embodiment of the present application includes:

the terminal equipment receives MBS service sent by a first cell according to a unicast mode and receives MBS service sent by the first cell according to a multicast mode;

the terminal device merges the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode in a physical layer or repeatedly detects the MBS service in a Packet Data Convergence Protocol (PDCP) layer.

The receiving apparatus for MBS service provided in the embodiment of the present application includes:

a receiving unit, configured to receive an MBS service sent by a first cell in a unicast manner, and receive an MBS service sent by the first cell in a multicast manner;

and the processing unit is used for merging the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or carrying out repeated detection on a PDCP layer.

The terminal device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory to execute the MBS service receiving method.

The chip provided by the embodiment of the application is used for realizing the receiving method of the MBS service.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the MBS service receiving method.

The computer-readable storage medium provided in the embodiments of the present application is used for storing a computer program, and the computer program enables a computer to execute the MBS service receiving method described above.

The computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions enable a computer to execute the receiving method of the MBS service.

The computer program provided in the embodiment of the present application, when running on a computer, enables the computer to execute the receiving method of the MBS service.

By the technical scheme, the terminal equipment receives the MBS service in the unicast mode and the MBS service in the multicast mode at the same time in the first cell, and the receiving reliability of the MBS service can be improved by combining the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or repeatedly detecting the MBS service on a PDCP layer.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic diagram of an architecture of a communication system provided in an embodiment of the present application;

fig. 2 is a schematic diagram illustrating that MBS services provided in an embodiment of the present application are transmitted in a multicast manner and a unicast manner;

fig. 3 is a flowchart illustrating a method for receiving MBS services according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a protocol stack on a network device side according to an embodiment of the present application;

fig. 5 is a schematic diagram of cell handover provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of a receiving apparatus for MBS service provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a chip of an embodiment of the present application;

fig. 9 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a 5G communication system, a future communication system, or the like.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the Network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a mobile switching center, a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a future communication system, and the like.

The communication system 100 further comprises at least one terminal 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, a connection via a wireline, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., for a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal that is arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal can refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

Optionally, the terminals 120 may perform direct-to-Device (D2D) communication therebetween.

Alternatively, the 5G communication system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminals, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal 120 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above and are not described again here; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which are not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

With the pursuit of speed, delay, high-speed mobility, energy efficiency and the diversity and complexity of the services in future life, the third generation partnership project (3) ^rd Generation Partnership Project,3 GPP) the international organization for standardization began developing 5G. The main application scenarios of 5G are: enhanced Mobile Ultra wide band (eMBB), low-Latency high-reliability communication (URLLC), and massive Machine-Type communication (mMTC).

On the one hand, the eMBB still targets users for multimedia content, services and data, and its demand is growing very rapidly. On the other hand, because the eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., and the difference between the capabilities and the requirements is relatively large, it cannot be said that it must be analyzed in detail in conjunction with a specific deployment scenario. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety, and the like. Typical characteristics of mtc include: high connection density, small data volume, insensitive time delay service, low cost and long service life of the module, etc.

In early NR deployment, complete NR coverage is difficult to obtain, so typical network coverage is wide-area LTE coverage and isolated island coverage pattern of NR. Moreover, a large amount of LTE is deployed below 6GHz, and the spectrum below 6GHz available for 5G is rare. NR must therefore be studied for spectrum applications above 6GHz, with limited high band coverage and fast signal fading. Meanwhile, in order to protect the early-stage LTE investment of mobile operators, a tight coupling (light interworking) working mode between LTE and NR is provided.

RRC state

In order to reduce air interface signaling, quickly recover wireless connection, and quickly recover data service, 5G defines a new Radio Resource Control (RRC) state, that is, an RRC INACTIVE (RRC _ INACTIVE) state. This state is distinguished from the RRC IDLE (RRC IDLE) state and the RRC ACTIVE (RRC ACTIVE) state. Wherein the content of the first and second substances,

1) RRC _ IDLE state (IDLE state for short): the mobility is cell selection and reselection based on terminal equipment, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no terminal equipment context and no RRC connection.

2) RRC _ CONNECTED state (CONNECTED state for short): the RRC connection exists, and the base station side and the terminal device side have a terminal device context. The network side knows that the location of the terminal device is at a particular cell level. Mobility is network side controlled mobility. Unicast data may be transmitted between the terminal device and the base station.

3) RRC _ INACTIVE state (INACTIVE state for short): mobility is based on cell selection reselection of terminal equipment, connection between CN-NR exists, context of the terminal equipment exists on a certain base station, paging is triggered by RAN, a paging area based on the RAN is managed by the RAN, and the network side knows that the position of the terminal equipment is based on the paging area level of the RAN.

MBMS

MBMS is a technology for transmitting data from one data source to a plurality of UEs by sharing network resources, which enables broadcasting and multicasting of a multimedia service at a higher rate (e.g., 256 kbps) by effectively using network resources while providing the multimedia service.

Because the MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of the mobile tv type service. Therefore, in LTE, 3GPP explicitly proposes to enhance the support capability for downlink high-speed MBMS service, and determines the design requirements for the physical layer and air interface.

The 3GPP R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes a Single Frequency Network (SFN) concept, that is, a Multimedia Broadcast multicast service Single Frequency Network (MBSFN), where MBSFN employs a uniform Frequency to simultaneously transmit service data in all cells, but needs to ensure synchronization between the cells. The method can greatly improve the distribution of the overall signal-to-noise ratio of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocol.

In LTE or LTE-Advanced (LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode. In addition, the reception of the MBMS service is applicable to the idle-state or connected-state UE.

A Single Cell Point To multipoint (SC-PTM) concept is introduced into a 3GPP R13, and the SC-PTM is based on an MBMS network architecture.

MBMS introduces new logical channels including a Single Cell-Multicast Control Channel (SC-MCCH) and a Single Cell-Multicast Transport Channel (SC-MTCH). The SC-MCCH and SC-MTCH are mapped to a Downlink-Shared Channel (DL-SCH), and the DL-SCH is further mapped to a Physical Downlink Shared Channel (PDSCH), wherein the SC-MCCH and SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a Physical Channel. The SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

MBMS introduces a new System Information Block (SIB) type, SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and the scheduling of the wireless frame and the subframe of the SC-MCCH. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m =0, where SFN represents the system frame number of the boundary, and m is the modification period of the SC-MCCH (i.e. SC-MCCH-modification period) configured in the SIB20. 2) And scheduling the radio frame of the SC-MCCH to meet the following requirements: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents a system frame number of a radio frame, MCCH-repetition period represents a repetition period of the SC-MCCH, and MCCH-Offset represents an Offset of the SC-MCCH. 3) And the sub-frame for scheduling the SC-MCCH is indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), that is, a Single Cell RNTI (SC-RNTI) is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling an SC-MCCH, and optionally, the SC-RNTI is fixedly valued as FFFC. On the other hand, a new RNTI, namely a Single Cell Notification RNTI (SC-N-RNTI) is introduced to identify a PDCCH (e.g., notification PDCCH) for indicating a change Notification of the SC-MCCH, and optionally, the SC-N-RNTI is fixedly valued as FFFB; further, the change notification may be indicated by one bit of 8 bits (bits) of the DCI 1C. In LTE, the configuration information of SC-PTM is based on SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., SCPTMConfiguration) for configuring configuration information of the SC-PTM. The configuration information of SC-PTM includes: temporary Mobile Group Identity (TMGI), session Identity (session id), group RNTI (G-RNTI), discontinuous Reception (DRX) configuration information, SC-PTM service information of the neighbor cell, and the like. It should be noted that SC-PTM in R13 does not support Robust Header Compression (ROHC) function.

The downlink discontinuous reception of SC-PTMs is controlled by the following parameters: ondurationTimerSCPTM, drx-InactivetTimeSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

When [ (SFN x 10) + subframe number ] module (SC-MTCH-scheduling cycle) = SC-MTCH-scheduling offset is satisfied, a timer onDurationTimerSCPTM is started;

when receiving downlink PDCCH dispatching, starting a timer drx-InactivetyTimerSCPTM;

the downlink SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-inactivityttimerscptm is running.

SC-PTM service continuity adopts SIB 15-based MBMS service continuity concept, namely SIB15+ MBMSIntestrIndication mode. The traffic continuity of idle UEs is based on the concept of frequency priority.

In the technical solution of the embodiment of the present application, a new SIB (referred to as a first SIB) is defined, where the first SIB includes configuration information of a first MCCH, where the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used to configure configuration information of a control channel of an NR MBMS, and optionally, the control channel of the NR MBMS may also be referred to as an NR MCCH (i.e., the first MCCH).

Further, the first MCCH is used to carry a first signaling, and in this embodiment of the present application, the name of the first signaling is not limited, for example, the first signaling is signaling a, the first signaling includes configuration information of at least one first MTCH, where the first MTCH is a traffic channel (also referred to as a data channel or a transport channel) of an MBMS service, and the first MTCH is used to transmit MBMS service data (e.g., service data of NR MBMS). In other words, the first MCCH is used to configure configuration information of a traffic channel of the NR MBMS, which may also be called NR MTCH (i.e., the first MTCH) optionally.

Specifically, the first signaling is used to configure a service channel of the NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, for example, the identification information for identifying the service, such as the TMGI, the session id, and the like. The scheduling information corresponding to the traffic channel, for example, the RNTI used when the MBMS service data corresponding to the traffic channel is scheduled, such as G-RNTI, DRX configuration information, and the like.

It should be noted that the transmission of the first MCCH and the first MTCH is scheduled based on the PDCCH. Wherein, the RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, which is a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

It should be noted that, in the embodiments of the present application, nomenclature of the first SIB, the first MCCH, and the first MTCH is not limited. For convenience of description, the first SIB may also be referred to as SIB, the first MCCH may also be referred to as MCCH, and the first MTCH may also be referred to as MTCH, where PDCCH for scheduling MCCH (i.e. MCCH PDCCH) and notification PDCCH are configured through SIB, and PDSCH for transmitting MCCH (i.e. MCCH PDSCH) is scheduled through DCI carried by MCCH PDCCH. Further, M PDCCHs (namely MTCH 1 PDCCH, MTCH 2 PDCCH, 8230; MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, wherein DCI carried by the MTCH n PDCCH schedules PDSCH (namely MTCH n PDSCH) for transmitting MTCH n, and n is an integer which is more than or equal to 1 and less than or equal to M. The MCCH and MTCH are mapped to DL-SCH, which belongs to a logical channel, and further mapped to PDSCH, which belongs to a physical channel.

It should be noted that the MBMS service in the above scheme includes, but is not limited to, a multicast service and a multicast service. In the embodiment of the present application, MBS service is taken as an example for explanation, and the description of "MBS service" may also be replaced by "multicast service" or "MBMS service".

In the NR MBS service, besides that the same cell needs to send the MBS service in multicast transmission, it may also transmit the MBS service in unicast for a specific user, for example, when the channel of the user is poor, the MBS service needs to be transmitted in unicast for the user. In a cell, there may be several users receiving a certain MBS service at the same time, but the base station sends the MBS service to each user in a unicast manner, for example, the efficiency of service transmission can be effectively improved by sending the MBS service to each user in a unicast manner when there are fewer users receiving the MBS service in the cell.

Referring to fig. 2, for a Packet Data Unit (PDU) session of a certain MBS service, a Shared GTP tunnel (Shared GTP tunnel) may be used between a 5G Core network (5G Core network,5 gc) and a gNB to transmit the MBS service, that is, the GTP tunnel is Shared for both unicast service and MBS service. The gNB issues the MBS service to a multicast group (multicast group) in a multicast (multicast) manner, and issues the MBS service to a certain UE in a unicast (unicast) manner (fig. 2 takes UE3 as an example). Wherein, the multicast group includes one or more UEs (fig. 2 takes the example that the multicast group includes UE1 and UE 2). How to improve the reliability of receiving the MBS service in a cell by the terminal device needs to be solved. Therefore, the following technical scheme of the embodiment of the application is provided.

Fig. 3 is a schematic flowchart of a receiving method for MBS service provided in an embodiment of the present application, and as shown in fig. 3, the receiving method for MBS service includes the following steps:

step 301: the terminal equipment receives the MBS service sent by the first cell according to the unicast mode and receives the MBS service sent by the first cell according to the multicast mode.

In this embodiment of the present application, the first cell may refer to a current serving cell of the terminal device.

In the embodiment of the application, the terminal device receives the MBS service in the first cell in a unicast manner, and meanwhile, the terminal device may also receive the MBS service in a multicast manner, thereby improving the reliability of receiving the MBS service.

Step 302: and the terminal equipment merges the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or repeatedly detects on a PDCP layer.

In the embodiment of the present application, the terminal device merges the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode in a physical layer or performs repeated detection in a PDCP layer, which will be described below.

● The terminal equipment improves the receiving reliability gain in a physical layer combination mode. Specifically, the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer.

In an optional manner of this application, the terminal device receives first indication information sent by the first cell, where the first indication information is used to indicate that the terminal device receives MBS services corresponding to a unicast manner and MBS services corresponding to a multicast manner at the same time.

In an optional manner of this application, the terminal device receives third indication information sent by the first cell, where the third indication information is used to indicate that the terminal device merges, on a physical layer, the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode, or performs duplicate detection on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a PDCP layer.

Here, the terminal device receives a unicast mode transmission and a multicast mode transmission of a certain MBS service simultaneously according to the indication information (i.e., the first indication information) configured by the network device, for example, the network device may display that the terminal device is indicated by the first indication information to receive the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode simultaneously. Further, the network device further indicates, through the third indication information, whether the terminal device combines the MBS service in the unicast manner and the MBS service in the multicast manner received at the same time in the physical layer or repeatedly receives the MBS service in the multicast manner in the PDCP layer.

And the terminal equipment receives a certain MBS service in a unicast mode and simultaneously receives the MBS service in a multicast mode according to the first indication information. And the terminal equipment combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer according to the third indication information.

In an optional manner of this application, the network device further instructs the terminal device to reserve configuration information of a multicast bearer when establishing a unicast bearer. Specifically, when the network device instructs the terminal device to receive a certain MBS service in a unicast manner, if the terminal device receives the MBS service in a multicast manner before, the terminal device reserves configuration information of a multicast bearer while establishing a unicast bearer to receive the MBS service. In this way, the terminal device reserves the configuration information of the multicast bearer when establishing the unicast bearer based on the indication of the network device.

In the above solution, the network device may explicitly instruct the terminal device to reserve the configuration information of the multicast bearer when establishing the unicast bearer, or implicitly instruct the terminal device to reserve the configuration information of the multicast bearer when establishing the unicast bearer, which will be described below.

1) Explicit indication mode

The terminal device receives second indication information sent by the first cell, where the second indication information is used to indicate that the terminal device reserves configuration information of a multicast bearer when establishing a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.

2) Implicit indication mode

The implicit indication may refer to the first indication or the second indication in the foregoing scheme for indication, and in an optional manner, the first indication information indicates that configuration information of a multicast bearer is reserved when the terminal device establishes a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.

In the embodiment of the application, a Transport Block (Transport Block, TB) of an MBS service corresponding to a unicast mode is referred to as a unicast TB, a TB of an MBS service corresponding to a multicast mode is referred to as a multicast TB, and the precondition for combining the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode in a physical layer is that the unicast TB and the multicast TB are associated, that is, the multicast TB and the unicast TB belonging to the same TB are associated. The TB belonging to the same TB means that the TB contents are the same. Associating unicast TBs with multicast TBs may be accomplished in any of the following ways.

The first method is as follows:

the scheduling information of a unicast TB of the MBS service corresponding to the unicast mode is first scheduling information, the scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, and the first scheduling information comprises the second scheduling information; and the terminal equipment associates the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information, and combines the associated multicast TB and unicast TB at a physical layer.

Here, the scheduling information corresponding to the multicast TB is added to the scheduling information of the unicast TB. In this way, multicast TBs and unicast TBs can be associated, thereby enabling physical layer consolidation.

For example: the scheduling information of the unicast TB carries first scheduling information and second scheduling information, wherein the first scheduling information is used for scheduling the unicast TB, the second scheduling information is used for scheduling the multicast TB corresponding to the unicast TB, and the unicast TB and the corresponding multicast TB can be associated through the scheduling information.

The second method comprises the following steps:

the scheduling information of a unicast TB of the MBS service corresponding to the unicast mode is first scheduling information, the scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, the first scheduling information comprises first identification information, the second scheduling information comprises second identification information, and the first identification information and the second identification information have an association relation; and the terminal equipment associates the multicast TB and the unicast TB belonging to the same TB based on the first identification information and the second identification information, and combines the associated multicast TB and unicast TB in a physical layer.

Here, one piece of indication information is added to the scheduling information of the unicast TB, one piece of indication information is also added to the scheduling information of the multicast TB corresponding to the unicast TB, and the unicast TB and the multicast TB are associated with each other through the two pieces of indication information, so that the associated multicast TB and unicast TB are merged at the physical layer.

For example: the indication information in the scheduling information of the unicast TB and the multicast TB is a bit stream, or an integer value, or an information stamp, and if the indication information in the two schedules is the same, the TBs corresponding to the two schedules can be associated together and merged at a physical layer.

In this embodiment, in order to enable that a unicast TB and a multicast TB can be associated, it is first ensured that TB contents are the same (that is, the unicast TB and the multicast TB belong to the same TB). When the network device sends the unicast TB and the multicast TB, the protocol stack architecture shown in fig. 4 may be used to ensure that the unicast TB and the multicast TB have the same content (or the network device ensures that the unicast TB and the multicast TB are the same TB when the unicast packet and the multicast packet are both sent).

Referring to fig. 4, fig. 4 is a schematic diagram of a structure of a protocol stack on a network device side, and a description of an "entity" is omitted in fig. 4, for example, "SDAP" in fig. 4 indicates an "SDAP entity". The PDU session of the MBS service includes one or more Qos flows, and the one or more Qos flows of the PDU session may be mapped to one or more DRBs through the SDAP entity, where the mapping relationship between the Qos flows and the DRBs may be one-to-one or many-to-one. Each DRB corresponds to a logical channel, wherein different DRBs are transmitted through different PDCP entities and RLC entities, i.e. different logical channels correspond to different PDCP entities and RLC entities.

It should be noted that in fig. 4, there may be no PDCP entity or SDAP entity for each DRB. That is, for each DRB, there may be a PDCP entity, or a PDCP entity + SDAP entity, or a SDAP entity.

The MAC entity copies one part of each MAC PDU (namely one TB data) to the PHY2 entity, the original MAC PDU is sent to the PHY1 entity, the MBS service is sent through the PHY1 entity according to a multicast mode, and the MBS service is sent through the PHY2 entity according to a unicast mode.

The third method comprises the following steps:

the terminal equipment associates the unicast TB and the multicast TB belonging to the same TB according to the Serial Number (SN) associated with the unicast TB and the SN associated with the multicast TB.

For example: unicast TB1 associated SN1, unicast TB2 associated SN2, unicast TB3 associated SN3, multicast TB1 associated SN1, multicast TB2 associated SN2, multicast TB3 associated SN3. According to the SN, unicast TB1 and multicast TB1 may be associated, unicast TB2 and multicast TB2 may be associated, and unicast TB3 and multicast TB3 may be associated.

Further, the terminal device determines feedback information of a unicast mode based on the reception condition of the unicast TB and the multicast TB which are associated together. Specifically, if the terminal device successfully receives at least one of a unicast TB and a multicast TB, the terminal device replies a positive acknowledgement message for the unicast mode; the unicast TB refers to the TB of the MBS corresponding to the unicast mode, the multicast TB refers to the TB of the MBS corresponding to the multicast mode, and the unicast TB and the multicast TB are the same TB.

In the above scheme, the TB associates with a SN, and the SN is carried in at least one of the following: the scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located, and the MAC packet header of the MAC PDU where the TB is located.

In one example, when a TB is successfully received in a multicast manner but fails to be received in a unicast manner, the terminal device performs feedback according to an Acknowledgement (ACK) in HARQ feedback in the unicast manner.

In one example, when a certain TB is successfully received in the unicast mode but fails to be received in the multicast mode, the terminal device performs feedback according to a positive Acknowledgement (ACK) in HARQ feedback in the unicast mode.

In one example, when a TB is successfully received in a unicast manner and successfully received in a multicast manner, the terminal device performs feedback according to an Acknowledgement (ACK) in HARQ feedback in the unicast manner.

In one example, when a TB fails to be successfully received in the unicast mode and fails to be received in the multicast mode, the terminal device performs feedback according to a Negative Acknowledgement (NACK) in HARQ feedback in the unicast mode.

Through the scheme, if any one of the unicast TB and the multicast TB is successfully received, the terminal equipment feeds back the ACK; and if the unicast TB and the multicast TB are received unsuccessfully, the terminal equipment feeds back NACK. Therefore, unnecessary unicast retransmission can be avoided, namely, the probability of unicast retransmission is reduced, and the spectrum efficiency is improved.

According to the technical scheme of the embodiment of the application, the terminal equipment receives the MBS service in the unicast mode and the MBS service in the multicast mode at the same time in one cell, and the MBS service in the unicast mode and the MBS service in the multicast mode are combined in a physical layer, so that the receiving reliability of the MBS service is improved.

● The terminal device improves the receiving reliability by repeatedly receiving through the PDCP layer. Specifically, the terminal device performs repeated detection on MBS services corresponding to the unicast mode and MBS services corresponding to the multicast mode on the PDCP layer.

Here, the terminal device simultaneously receives unicast mode transmission and multicast mode transmission of a certain MBS service according to the indication information (i.e. the first indication information) configured by the network device, for example, the network device may indicate, through the first indication information, that the terminal device simultaneously receives MBS service corresponding to the unicast mode and MBS service corresponding to the multicast mode. Further, the network device further indicates, through the third indication information, whether the terminal device combines the MBS service in the unicast manner and the MBS service in the multicast manner received at the same time in the physical layer or repeatedly receives the MBS service in the multicast manner in the PDCP layer.

And the terminal equipment receives a certain MBS service in a unicast mode according to the first indication information, and simultaneously receives the MBS service in a multicast mode. And the terminal equipment combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode in a physical layer according to the third indication information.

In an optional manner of this application, the network device further instructs the terminal device to reserve configuration information of a multicast bearer when establishing a unicast bearer. Specifically, when the network device instructs the terminal device to receive a certain MBS service in a unicast manner, if the terminal device receives the MBS service in a multicast manner, the terminal device establishes a unicast bearer to receive the MBS service, and meanwhile, retains configuration information of the multicast bearer. In this way, the terminal device reserves the configuration information of the multicast bearer when establishing the unicast bearer based on the indication of the network device.

1) Explicit indication mode

2) Implicit indication mode

In the embodiment of the application, the terminal device performs repeated detection on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on the PDCP layer according to the SN associated with the MBS service data.

According to the technical scheme of the embodiment of the application, the terminal equipment receives the MBS service in the unicast mode and the MBS service in the multicast mode at the same time in one cell, and repeatedly detects the MBS service in the unicast mode and the MBS service in the multicast mode on the PDCP layer, so that the receiving reliability of the MBS service is improved.

In the embodiment of the present application, in consideration of the mobility of the terminal device, a scenario in which the terminal device switches from the first cell to the second cell may occur, and how the terminal device receives the MBS service in such a scenario is described below.

As shown in fig. 5, for maintaining continuous reception of MBS service during handover, there are four scenarios as follows:

TABLE 1

In an optional manner of this application, in a process of switching from the first cell to the second cell, the terminal device reserves the multicast configuration information of the MBS service on the first cell side.

Here, the terminal device maintains the multicast configuration information of the original side (i.e. the first cell side) on the MBS service during the handover procedure.

In an optional manner of the present application, during the process of switching from the first cell to the second cell and/or after switching to the second cell, the terminal device receives MBS services sent by the first cell in a multicast manner and MBS services sent by the second cell in a multicast manner and/or a unicast manner at the same time; and the terminal equipment performs repeated detection on the received MBS service according to the SN associated with the MBS service data.

Here, during or after the handover, the terminal device still receives the MBS service transmission in the target cell (i.e., the second cell) and the MBS service transmission on the original side (i.e., the first cell side) at the same time. And the terminal equipment performs repeated detection on the received MBS service according to the SN associated with the MBS service data.

In an optional manner of this application, when the terminal device determines that the target condition is satisfied, the multicast configuration information of the MBS service on the first cell side is released, and the terminal device stops receiving the MBS service sent by the first cell in a multicast manner. Further optionally, the target condition comprises at least one of: 1. the terminal equipment can successfully receive the MBS service of the second cell; 2. and the terminal equipment detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.

Here, the terminal device itself decides to release the multicast configuration information of the original side (i.e., the first cell side) regarding the MBS service and stops receiving the MBS service of the original side. For example: the terminal device can successfully receive the MBS service of the target cell (namely, the second cell), and releases the multicast configuration information of the original side (namely, the first cell side) about the MBS service and stops receiving the MBS service of the original side under the condition that the SN gap does not exist. For another example: when detecting that the signal quality of the original side (i.e. the first cell side) is lower than a certain threshold, the terminal device releases the multicast configuration information of the original side about the MBS service and stops receiving the MBS service of the original side.

In this embodiment of the present application, from the perspective of a network side, a network architecture of the first cell and the second cell may have the following implementation manners:

i) The first cell and the second cell have separate Distributed Units (DUs) and have the same Centralized Unit (CU).

Here, optionally, the protocol stack entity implemented by the DU is: an RLC entity, a MAC entity and a PHY entity.

Here, optionally, the protocol stack entities implemented by the CUs are: RRC entity and PDCP entity.

In the above manner, the first cell and the second cell implement intra-CU scenarios.

II) the first cell and the second cell belong to the same MBS zone, and the base station corresponding to the first cell and the base station corresponding to the second cell share one anchor point which is used for generating PDCP PDU of MBS service and forwarding to all base stations in the MBS zone.

According to the technical scheme of the embodiment of the application, the receiving reliability of the MBS service is improved while the terminal equipment receives the MBS service in the switching process, and the packet loss rate can be reduced to ensure the continuity of the MBS service.

Fig. 6 is a schematic structural diagram of a receiving apparatus of an MBS service provided in an embodiment of the present application, and is applied to a terminal device, as shown in fig. 6, the receiving apparatus of the MBS service includes:

a receiving unit 601, configured to receive an MBS service sent by a first cell in a unicast manner, and receive an MBS service sent by the first cell in a multicast manner;

a processing unit 602, configured to merge, in a physical layer, the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode, or perform repeated detection on a PDCP layer.

In an optional manner, the receiving unit 601 is further configured to receive first indication information sent by the first cell, where the first indication information is used to indicate that the terminal device receives MBS services corresponding to a unicast manner and MBS services corresponding to a multicast manner at the same time.

In an optional manner, the first indication information is further used to indicate that the terminal device reserves configuration information of a multicast bearer when establishing a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.

In an optional manner, the receiving unit 601 is further configured to receive second indication information sent by the first cell, where the second indication information is used to indicate that configuration information of a multicast bearer is reserved when the terminal device establishes a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.

In an optional manner, the receiving unit 601 is further configured to receive third indication information sent by the first cell, where the third indication information is used to indicate that the terminal device merges the MBS service corresponding to the unicast manner and the MBS service corresponding to the multicast manner on a physical layer, or performs duplicate detection on the MBS service corresponding to the unicast manner and the MBS service corresponding to the multicast manner on a PDCP layer.

In an optional mode, scheduling information of a unicast TB of an MBS service corresponding to the unicast mode is first scheduling information, scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, and the first scheduling information includes the second scheduling information;

the processing unit 602 is configured to associate a multicast TB and a unicast TB that belong to the same TB based on the first scheduling information, and merge the associated multicast TB and unicast TB in a physical layer.

In an optional mode, scheduling information of a unicast TB of an MBS service corresponding to the unicast mode is first scheduling information, scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, the first scheduling information includes first identification information, the second scheduling information includes second identification information, and the first identification information and the second identification information have an association relationship;

the processing unit 602 is configured to associate a multicast TB and a unicast TB that belong to the same TB based on the first identification information and the second identification information, and merge the associated multicast TB and unicast TB at a physical layer.

In an optional manner, the apparatus further comprises:

a sending unit (not shown in the figure), configured to reply a positive acknowledgement message for the unicast mode if the receiving unit successfully receives at least one of the unicast TB and the multicast TB; the unicast TB refers to the TB of the MBS service corresponding to the unicast mode, the multicast TB refers to the TB of the MBS service corresponding to the multicast mode, and the unicast TB and the multicast TB are the same TB.

In an optional manner, the TB is associated with a SN, and the SN is carried in at least one of the following: the scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located, and the MAC packet header of the MAC PDU where the TB is located.

In an optional manner, the processing unit 602 is further configured to associate a unicast TB and a multicast TB belonging to the same TB according to a SN associated with the unicast TB and a SN associated with the multicast TB, and determine feedback information of a unicast manner based on a reception situation of the associated unicast TB and multicast TB.

In an optional manner, the processing unit 602 is configured to perform repeated detection on the MBS service corresponding to the unicast manner and the MBS service corresponding to the multicast manner on the PDCP layer according to an SN associated with MBS service data.

In an optional manner, the processing unit 602 is further configured to reserve multicast configuration information of an MBS service on the first cell side in a process that a terminal device is handed over from the first cell to a second cell.

In an optional manner, the receiving unit 601 is configured to receive, during and/or after a terminal device is handed over from the first cell to a second cell, an MBS service sent by the first cell in a multicast manner and an MBS service sent by the second cell in a multicast manner and/or a unicast manner at the same time;

the processing unit 602 is configured to perform repeated detection on the received MBS service according to the SN associated with the MBS service data.

In an optional manner, the processing unit 602 is further configured to release the multicast configuration information of the MBS service on the first cell side if it is determined that the target condition is met;

the receiving unit 601 is further configured to stop receiving the MBS service sent by the first cell in a multicast manner.

In an alternative, the target condition includes at least one of:

the terminal equipment can successfully receive the MBS service of the second cell;

and the terminal equipment detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.

In an alternative, the first cell and the second cell have independent DUs and have the same CU.

In an optional manner, the first cell and the second cell belong to the same MBS zone, and the base station corresponding to the first cell and the base station corresponding to the second cell share an anchor point, where the anchor point is used to generate a PDCP PDU of an MBS service and forward the PDCP PDU to all base stations in the MBS zone.

Those skilled in the art should understand that the related description of the receiving apparatus of the MBS service in the embodiment of the present application can be understood by referring to the related description of the receiving method of the MBS service in the embodiment of the present application.

Fig. 7 is a schematic structural diagram of a communication device 700 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 700 shown in fig. 7 includes a processor 710, and the processor 710 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, the communication device 700 may also include a memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, as shown in fig. 7, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 730 may include a transmitter and a receiver, among others. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 700 may specifically be a network device in the embodiment of the present application, and the communication device 700 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 700 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 700 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.

Fig. 8 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 800 shown in fig. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 8, chip 800 may further include a memory 820. From the memory 820, the processor 810 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

Optionally, the chip 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 800 may further include an output interface 840. The processor 810 can control the output interface 840 to communicate with other devices or chips, and in particular, can output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 9, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, which is not described herein again.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting, for example, the memories in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A receiving method of multimedia multicast service MBS service, the method comprises:

the terminal equipment receives MBS service sent by a first cell according to a unicast mode and receives MBS service sent by the first cell according to a multicast mode;

and the terminal equipment combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or repeatedly detects the MBS service on a packet data convergence protocol PDCP layer.
The method of claim 1, wherein the method further comprises:

and the terminal equipment receives first indication information sent by the first cell, wherein the first indication information is used for indicating the terminal equipment to simultaneously receive MBS services corresponding to a unicast mode and MBS services corresponding to a multicast mode.
The method of claim 2, wherein the first indication information is further used to indicate configuration information of a multicast bearer to be reserved when the terminal device establishes a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.
The method according to claim 1 or 2, wherein the method further comprises:

the terminal device receives second indication information sent by the first cell, where the second indication information is used to indicate that the terminal device reserves configuration information of a multicast bearer when establishing a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.
The method of any of claims 1 to 4, wherein the method further comprises:

and the terminal equipment receives third indication information sent by the first cell, wherein the third indication information is used for indicating that the terminal equipment combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or repeatedly detects the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a PDCP layer.
The method according to any one of claims 1 to 5, wherein the scheduling information of a unicast Transport Block (TB) of the MBS service corresponding to the unicast mode is first scheduling information, the scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, and the first scheduling information includes the second scheduling information;

the said terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode in the physical layer, which includes:

and the terminal equipment associates the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information, and combines the associated multicast TB and unicast TB at a physical layer.
The method according to any one of claims 1 to 5, wherein the scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is first scheduling information, the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, the first scheduling information comprises first identification information, the second scheduling information comprises second identification information, and the first identification information and the second identification information have an association relationship;

the said terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode in the physical layer, which includes:

and the terminal equipment associates the multicast TB and the unicast TB belonging to the same TB based on the first identification information and the second identification information, and combines the associated multicast TB and unicast TB in a physical layer.
The method of any of claims 1-6, wherein the method further comprises:

if the terminal equipment successfully receives at least one of the unicast TB and the multicast TB, the terminal equipment replies a positive confirmation message aiming at the unicast mode; the unicast TB refers to the TB of the MBS corresponding to the unicast mode, the multicast TB refers to the TB of the MBS corresponding to the multicast mode, and the unicast TB and the multicast TB are the same TB.
The method of claim 8, wherein the TB is associated with a sequence number SN, the SN being carried in at least one of: the scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located, and the MAC packet header of the MAC PDU where the TB is located.
The method of claim 8, wherein the method further comprises:

and the terminal equipment associates the unicast TB and the multicast TB belonging to the same TB according to the SN associated with the unicast TB and the SN associated with the multicast TB, and determines the feedback information of the unicast mode based on the receiving conditions of the associated unicast TB and multicast TB.
The method according to any of claims 1 to 5, wherein the repeatedly detecting, by the terminal device, the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a PDCP layer comprises:

and the terminal equipment repeatedly detects the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a PDCP layer according to the SN associated with the MBS service data.
The method of any of claims 1 to 11, wherein the method further comprises:

and in the process of switching the terminal equipment from the first cell to the second cell, reserving the multicast configuration information of the MBS service at the side of the first cell.
The method of any of claims 1 to 12, wherein the method further comprises:

the terminal equipment simultaneously receives MBS services sent by the first cell in a multicast mode and MBS services sent by the second cell in a multicast mode and/or a unicast mode in the process of switching from the first cell to the second cell and/or after switching to the second cell;

and the terminal equipment performs repeated detection on the received MBS service according to the SN associated with the MBS service data.
The method of claim 13, wherein the method further comprises:

and the terminal equipment releases the multicast configuration information of the MBS service at the first cell side and stops receiving the MBS service sent by the first cell in a multicast mode under the condition of determining that the target condition is met.
The method of claim 14, wherein the target condition comprises at least one of:

the terminal equipment can successfully receive the MBS service of the second cell;

and the terminal equipment detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.
The method according to any of claims 12-15, wherein the first and second cells have separate distribution units, DU, and the same concentration unit, CU.
The method according to any of claims 12 to 15, wherein the first cell and the second cell belong to the same MBS zone, and the base station corresponding to the first cell and the base station corresponding to the second cell share one anchor point, and the anchor point is used for generating PDCP PDUs of MBS services and forwarding the PDCP PDUs to all base stations in the MBS zone.
A receiving apparatus of an MBS service, the apparatus comprising:

a receiving unit, configured to receive an MBS service sent by a first cell in a unicast manner, and receive an MBS service sent by the first cell in a multicast manner;

and the processing unit is used for merging the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode on a physical layer or repeatedly detecting the MBS services on a PDCP layer.
The apparatus of claim 18, wherein the receiving unit is further configured to receive first indication information sent by the first cell, where the first indication information is used to indicate the terminal device to simultaneously receive MBS service corresponding to a unicast mode and MBS service corresponding to a multicast mode.
The apparatus of claim 19, wherein the first indication information is further configured to indicate configuration information of a multicast bearer to be reserved when the terminal device establishes a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.
The apparatus according to claim 18 or 19, wherein the receiving unit is further configured to receive second indication information sent by the first cell, where the second indication information is used to indicate configuration information of a multicast bearer that is reserved when the terminal device establishes a unicast bearer, where the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.
The apparatus according to any one of claims 18 to 21, wherein the receiving unit is further configured to receive third indication information sent by the first cell, where the third indication information is used to indicate that the terminal device merges the MBS service corresponding to the unicast scheme and the MBS service corresponding to the multicast scheme on a physical layer, or performs repeated detection on the MBS service corresponding to the unicast scheme and the MBS service corresponding to the multicast scheme on a PDCP layer.
The apparatus according to any one of claims 18 to 22, wherein the scheduling information of a unicast TB of the MBS service corresponding to the unicast mode is first scheduling information, the scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, and the first scheduling information includes the second scheduling information;

and the processing unit is used for associating the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information, and combining the associated multicast TB and unicast TB in a physical layer.
The apparatus according to any one of claims 18 to 22, wherein the scheduling information of a unicast TB of the MBS service corresponding to the unicast mode is first scheduling information, the scheduling information of a multicast TB of the MBS service corresponding to the multicast mode is second scheduling information, the unicast TB and the multicast TB are the same TB, the first scheduling information includes first identification information, the second scheduling information includes second identification information, and the first identification information and the second identification information have an association relationship;

and the processing unit is configured to associate multicast TBs and unicast TBs that belong to the same TB based on the first identification information and the second identification information, and merge the associated multicast TBs and unicast TBs in a physical layer.
The apparatus of any one of claims 18 to 23, wherein the apparatus further comprises:

a sending unit, configured to reply a positive acknowledgement message for the unicast mode if the receiving unit successfully receives at least one of a unicast TB and a multicast TB; the unicast TB refers to the TB of the MBS service corresponding to the unicast mode, the multicast TB refers to the TB of the MBS service corresponding to the multicast mode, and the unicast TB and the multicast TB are the same TB.
The apparatus of claim 25, wherein the TB is associated with a SN that is carried in at least one of: the scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located and the MAC packet header of the MAC PDU where the TB is located.
The apparatus of claim 25, wherein the processing unit is further configured to associate a unicast TB and a multicast TB belonging to the same TB according to a SN associated with the unicast TB and a SN associated with the multicast TB, and determine the feedback information of the unicast mode based on reception conditions of the unicast TB and the multicast TB that are associated together.
The apparatus according to any of claims 18 to 22, wherein the processing unit is configured to perform repeated detection on the PDCP layer for MBS service corresponding to the unicast manner and MBS service corresponding to the multicast manner according to an SN associated with MBS service data.
The apparatus of any of claims 18 to 28, wherein the processing unit is further configured to reserve multicast configuration information of an MBS service on the first cell side in a process of a terminal device handing over from the first cell to a second cell.
The apparatus according to any of claims 18 to 29, wherein the receiving unit is configured to receive MBS service sent by the first cell in a multicast manner and MBS service sent by the second cell in a multicast manner and/or unicast manner simultaneously during and/or after a terminal device is handed over from the first cell to the second cell;

and the processing unit is used for carrying out repeated detection on the received MBS service according to the SN associated with the MBS service data.
The apparatus of claim 30, wherein,

the processing unit is further configured to release the multicast configuration information of the MBS service at the first cell side under the condition that it is determined that the target condition is satisfied;

the receiving unit is further configured to stop receiving the MBS service sent by the first cell in a multicast manner.
The apparatus of claim 31, wherein the target condition comprises at least one of:

the terminal equipment can successfully receive the MBS service of the second cell;

and the terminal equipment detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.
The apparatus of any of claims 29-32, wherein the first cell and the second cell have independent DUs and have the same CUs.
The apparatus of any of claims 29 to 32, wherein the first cell and the second cell belong to the same MBS zone, and a base station corresponding to the first cell and a base station corresponding to the second cell share one anchor point, where the anchor point is configured to generate PDCP PDUs of MBS services and forward the PDCP PDUs to all base stations in the MBS zone.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and execute the computer program stored in the memory, performing the method of any of claims 1 to 17.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 17.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 17.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 17.
A computer program for causing a computer to perform the method of any one of claims 1 to 17.