MBS service receiving method, device and terminal equipment

Abstract

An embodiment of the present application provides a method and apparatus for receiving an MBS service, and a terminal device. The method includes: the terminal device receives an MBS service sent by a first cell in a unicast manner, and receives an MBS service sent by the first cell in a multicast manner; the terminal device merges the MBS service corresponding to the unicast manner and the MBS service corresponding to the multicast manner at the physical layer or performs duplicate detection at the packet data convergence protocol PDCP layer.

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2020 / 101433 with an application date of July 10, 2020, which has entered the Chinese national phase with Chinese patent application number 202080102718.5 and the invention name being “A method, device and terminal equipment for receiving MBS services”. Technical Field

[0002] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a method and apparatus for receiving a Multimedia Broadcast Service (MBS) service, and a terminal device. Background Art

[0003] In a cell, the base station can send MBS services in a multicast manner or in a unicast manner to a specific user. How to improve the reliability of terminal equipment receiving MBS services in a cell needs to be solved. Summary of the invention

[0004] The embodiments of the present application provide a method and apparatus for receiving an MBS service, and a terminal device.

[0005] The method for receiving MBS services provided in the embodiment of the present application includes:

[0006] The terminal device receives the MBS service sent by the first cell in a unicast manner, and receives the MBS service sent by the first cell in a multicast manner;

[0007] The terminal device merges the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or performs duplicate detection at the Packet Data Convergence Protocol (PDCP) layer.

[0008] The MBS service receiving device provided in the embodiment of the present application includes:

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

[0010] The processing unit is used to merge the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or perform duplication detection at the PDCP layer.

[0011] The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned MBS service receiving method.

[0012] The chip provided in the embodiment of the present application is used to implement the above-mentioned MBS service receiving method.

[0013] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned MBS service receiving method.

[0014] The computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned method for receiving MBS services.

[0015] The computer program product provided in the embodiment of the present application includes computer program instructions, and the computer program instructions enable a computer to execute the above-mentioned MBS service receiving method.

[0016] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for receiving MBS services.

[0017] Through the above technical solution, the terminal device receives unicast MBS services and multicast MBS services in the first cell at the same time. The reception reliability of the MBS services can be improved by merging the MBS services corresponding to the unicast mode and the MBS services corresponding to the multicast mode at the physical layer or performing repeated detection at the PDCP layer. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0020] Figure 2 It is a schematic diagram of the MBS service provided by the embodiment of the present application being transmitted in a multicast manner and a unicast manner;

[0021] Figure 3 It is a flowchart of a method for receiving an MBS service provided in an embodiment of the present application;

[0022] Figure 4 It is a schematic diagram of the structure of the protocol stack on the network device side provided in an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of cell switching provided in an embodiment of the present application;

[0024] Figure 6 It is a schematic diagram of the structure of a receiving device for MBS services provided in an embodiment of the present application;

[0025] Figure 7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0026] Figure 8 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0027] Fig. 9 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0029] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future communication system, etc.

[0030] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (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, etc.

[0031] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminal" includes but is not limited to connecting via a wired line, such as via a Public Switched Telephone Networks (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, such as, 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 another terminal configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal configured to communicate via 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 System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, 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 radiotelephone transceivers. A terminal may refer to an access terminal, User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with 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.

[0032] Optionally, the terminals 120 may perform device-to-device (D2D) communication with each other.

[0033] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0034] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.

[0035] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0036] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0037] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

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

[0039] With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of services in future life, the Third Generation Partnership Project (3GPP) rd The 3rd Generation Partnership Project (3GPP) international standard organization has begun to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0040] On the one hand, eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary greatly, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc.

[0041] In the early days of NR deployment, complete NR coverage was difficult to obtain, so the typical network coverage was wide-area LTE coverage and NR island coverage. In addition, a large number of LTEs are deployed below 6GHz, and there is little spectrum below 6GHz available for 5G. Therefore, NR must study spectrum applications above 6GHz, but high-frequency bands have limited coverage and fast signal fading. At the same time, in order to protect mobile operators' early investments in LTE, a tight interworking working mode between LTE and NR was proposed.

[0042] RRC Status

[0043] In order to reduce air interface signaling and quickly restore wireless connections and data services, 5G defines a new Radio Resource Control (RRC) state, namely the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state.

[0044] 1) RRC_IDLE state (abbreviated as idle state): Mobility is based on cell selection and reselection of terminal equipment, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no terminal equipment context on the base station side, and there is no RRC connection.

[0045] 2) RRC_CONNECTED state (referred to as connected state): There is an RRC connection, and there is a terminal device context on the base station side and the terminal device side. The network side knows the location of the terminal device at the specific cell level. The mobility is the mobility controlled by the network side. Unicast data can be transmitted between the terminal device and the base station.

[0046] 3) RRC_INACTIVE state (abbreviated as inactive state): Mobility is based on cell selection reselection of the terminal device, there is a connection between CN-NR, the terminal device context exists on a certain base station, paging is triggered by RAN, and the paging area based on RAN is managed by RAN. The network side knows the location of the terminal device based on the paging area level of RAN.

[0047] MBMS

[0048] MBMS is a technology that transmits data from one data source to multiple UEs by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and realize broadcast and multicast of multimedia services at a higher rate (such as 256kbps).

[0049] Since MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed to enhance the support capability for downlink high-speed MBMS services and determined the design requirements for the physical layer and air interface.

[0050] 3GPP R9 introduced evolved MBMS (eMBMS) into LTE. eMBMS proposed the concept of Single Frequency Network (SFN), namely Multimedia Broadcast multicast service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to send service data in all cells at the same time, but synchronization between cells must be guaranteed. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly. eMBMS implements broadcast and multicast of services based on the IP multicast protocol.

[0051] In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS has only a broadcast bearer mode, but no multicast bearer mode. In addition, the reception of MBMS services is applicable to UEs in an idle state or a connected state.

[0052] 3GPP R13 introduced the concept of Single Cell Point To Multipoint (SC-PTM), which is based on the MBMS network architecture.

[0053] MBMS introduces new logical channels, including Single Cell-Multicast Control Channel (SC-MCCH) and Single Cell-Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to Downlink Shared Channel (DL-SCH), and further, DL-SCH is mapped to Physical Downlink Shared Channel (PDSCH), where SC-MCCH and SC-MTCH are logical channels, DL-SCH is a transport channel, and PDSCH is a physical channel. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

[0054] MBMS introduces a new type of System Information Block (SIB), namely SIB20. Specifically, the configuration information of SC-MCCH is transmitted through SIB20, and there is only one SC-MCCH in a cell. The configuration information of SC-MCCH includes: the modification period of SC-MCCH, the repetition period of SC-MCCH, and the radio frame and subframe for scheduling SC-MCCH. Further, 1) The boundary of the modification period of SC-MCCH satisfies SFN mod m = 0, where SFN represents the system frame number of the boundary, and m is the modification period of SC-MCCH configured in SIB20 (i.e., sc-mcch-ModificationPeriod). 2) The radio frame for scheduling SC-MCCH satisfies: SFN mod mcch-RepetitionPeriod = mcch-Offset, where SFN represents the system frame number of the radio frame, mcch-RepetitionPeriod represents the repetition period of SC-MCCH, and mcch-Offset represents the offset of SC-MCCH. 3) The subframe for scheduling SC-MCCH is indicated by sc-mcch-Subframe.

[0055] SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH). On the one hand, a new Radio Network Temporary Identity (RNTI), namely the Single Cell RNTI (SC-RNTI), is introduced to identify the PDCCH (such as SC-MCCHPDCCH) used to schedule SC-MCCH. Optionally, the SC-RNTI is fixed to FFFC. On the other hand, a new RNTI, namely the Single Cell Notification RNTI (SC-N-RNTI), is introduced to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of SC-MCCH. Optionally, the SC-N-RNTI is fixed to FFFB; further, one of the 8 bits of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then the SC-MCCH configures the SC-MTCH, which is used to transmit service data.

[0056] Specifically, SC-MCCH only transmits one message (i.e., SCPTMConfiguration), which is used to configure the configuration information of SC-PTM. The configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session id, group RNTI (G-RNTI), discontinuous reception (DRX) configuration information, and SC-PTM service information of neighboring cells. It should be noted that SC-PTM in R13 does not support the robust header compression (ROHC) function.

[0057] The downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

[0058] When [(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset is satisfied, the timer onDurationTimerSCPTM is started;

[0059] When receiving downlink PDCCH scheduling, start the timer drx-InactivityTimerSCPTM;

[0060] Downlink SC-PTM services are received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

[0061] SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely "SIB15+MBMSInterestIndication". The service continuity of idle UE is based on the concept of frequency priority.

[0062] In the technical solution of the embodiment of the present application, a new SIB (called the first SIB) is defined. The first SIB includes configuration information of the first MCCH. Here, the first MCCH is the control channel of the MBMS service. In other words, the first SIB is used to configure the configuration information of the control channel of NRMBMS. Optionally, the control channel of NR MBMS can also be called NR MCCH (i.e., the first MCCH).

[0063] Further, the first MCCH is used to carry the first signaling. The embodiment of the present application does not limit the name of the first signaling. For example, the first signaling is signaling A. The first signaling includes configuration information of at least one first MTCH. Here, the first MTCH is a service channel (also called a data channel or a transmission channel) of the MBMS service. The first MTCH is used to transmit MBMS service data (such as service data of NR MBMS). In other words, the first MCCH is used to configure the configuration information of the service channel of NR MBMS. Optionally, the service channel of NR MBMS can also be called NR MTCH (i.e., the first MTCH).

[0064] Specifically, the first signaling is used to configure the service channel of NR MBMS, the service information corresponding to the service channel, and the scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, such as identification information of the service such as TMGI and session id. The scheduling information corresponding to the service channel, such as the RNTI used when the MBMS service data corresponding to the service channel is scheduled, such as G-RNTI, DRX configuration information, etc.

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

[0066] It should be noted that the embodiments of the present application do not limit the naming of the first SIB, the first MCCH and the first MTCH. For ease 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. The PDCCH for scheduling MCCH (i.e., MCCHPDCCH) and notifying PDCCH are configured through SIB, wherein the DCI carried by MCCH PDCCH is scheduled for transmitting the PDSCH (i.e., MCCH PDSCH) for MCCH. Further, M PDCCHs for scheduling MTCH (i.e., MTCH 1PDCCH, MTCH2PDCCH, ..., MTCH MPDCCH) are configured through MCCH, wherein the DCI carried by MTCH n PDCCH is scheduled for transmitting the PDSCH for MTCH n (i.e., MTCH n PDSCH), and n is an integer greater than or equal to 1 and less than or equal to M. MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH, wherein MCCH and MTCH belong to logical channels, DL-SCH belongs to a transport channel, and PDSCH belongs to a physical channel.

[0067] It should be noted that the MBMS service in the above solution includes but is not limited to multicast service and groupcast service. The embodiment of the present application takes the MBS service as an example for explanation, and the description of "MBS service" can also be replaced by "multicast service" or "groupcast service" or "MBMS service".

[0068] In the NR MBS service, in addition to sending the MBS service in multicast mode, the same cell may also transmit the MBS service to a specific user in unicast mode. For example, if the channel of the user is poor, the MBS service needs to be transmitted to the user in unicast mode. 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 unicast mode. For example, if there are few users receiving MBS services in the cell, sending MBS services to each user in unicast mode can effectively improve the service transmission efficiency.

[0069] Reference Figure 2For a packet data unit (PDU) session of a certain MBS service, a shared GTP tunnel may be used between the 5G Core network (5GC) and the gNB to transmit the MBS service, that is, both unicast services and MBS services share this GTP tunnel. The gNB sends the MBS service to the multicast group in a multicast manner, and sends the MBS service to a certain UE in a unicast manner. Figure 2 Take UE3 as an example). The multicast group includes one or more UEs ( Figure 2 Take the multicast group including UE1 and UE2 as an example). How to improve the reliability of terminal equipment receiving MBS services in a cell needs to be solved. To this end, the following technical solutions of the embodiments of the present application are proposed.

[0070] Figure 3 is a flow chart of a method for receiving MBS services provided in an embodiment of the present application, such as Figure 3 As shown, the method for receiving the MBS service includes the following steps:

[0071] Step 301: The terminal device receives an MBS service sent by a first cell in a unicast manner, and receives an MBS service sent by the first cell in a multicast manner.

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

[0073] In the embodiment of the present application, the terminal device receives the MBS service in a unicast manner in the first cell. At the same time, the terminal device may also receive the MBS service in a multicast manner, thereby improving the reliability of the MBS service reception.

[0074] Step 302: The terminal device merges the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or performs duplication detection at the PDCP layer.

[0075] 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 at the physical layer or performs duplicate detection at the PDCP layer, which are explained below respectively.

[0076] The terminal device improves the reception reliability gain by combining the physical layer. Specifically, the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer.

[0077] In an optional manner of the present application, the terminal device receives first indication information sent by the first cell, and the first indication information is used to instruct the terminal device to simultaneously receive the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode.

[0078] In an optional method of the present application, the terminal device receives third indication information sent by the first cell, and the third indication information is used to instruct the terminal device whether to merge the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer, or to perform repeated detection of the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the PDCP layer.

[0079] Here, the terminal device receives both the unicast and multicast transmissions 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 can display the first indication information to instruct the terminal device to simultaneously receive the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode. Furthermore, the network device also instructs the terminal device through the third indication information whether to merge the unicast MBS service and the multicast MBS service received simultaneously at the physical layer or to receive them repeatedly at the PDCP layer.

[0080] When the terminal device receives a certain MBS service in unicast mode according to the first indication information, it also receives the MBS service in multicast mode. According to the third indication information, the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer.

[0081] In an optional manner of the present application, the network device further instructs the terminal device to retain the configuration information of the 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 previously received the MBS service in a multicast manner, the terminal device retains the configuration information of the multicast bearer while establishing a unicast bearer to receive the MBS service. In this way, the terminal device retains the configuration information of the multicast bearer when establishing a unicast bearer based on the instruction of the network device.

[0082] In the above scheme, the network device can explicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, or can implicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, which are explained separately below.

[0083] 1) Explicit indication method

[0084] The terminal device receives second indication information sent by the first cell, and the second indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, wherein the unicast bearer is used by the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used by the terminal device to receive the MBS service in a multicast manner.

[0085] 2) Implicit indication method

[0086] The implicit indication can be indicated by referring to the first indication or the second indication in the aforementioned scheme. In an optional manner, the first indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, wherein 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.

[0087] In the embodiment of the present application, the transport block (TB) of the MBS service corresponding to the unicast mode is called a unicast TB, and the TB of the MBS service corresponding to the multicast mode is called a multicast TB. The premise for merging the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer is to associate the unicast TB with the multicast TB, that is, to associate the multicast TB and the unicast TB belonging to the same TB. It should be noted that belonging to the same TB means that the TB contents are the same. Associating the unicast TB with the multicast TB can be achieved in any of the following ways.

[0088] Method 1:

[0089] The scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information, and the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the 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 terminal device associates the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information, and merges the associated multicast TB and unicast TB at the physical layer.

[0090] Here, the scheduling information of the corresponding multicast TB is added to the scheduling information of the unicast TB. In this way, the multicast TB and the unicast TB can be associated, so that the physical layer can be merged.

[0091] For example, the scheduling information of a unicast TB carries first scheduling information and second scheduling information, wherein the first scheduling information is used to schedule the unicast TB, and the second scheduling information is used to schedule the multicast TB corresponding to the unicast TB. The unicast TB and the corresponding multicast TB can be associated through the scheduling information.

[0092] Method 2:

[0093] The scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information, and the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the 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 are associated with each other; based on the first identification information and the second identification information, the terminal device associates the multicast TB and the unicast TB belonging to the same TB, and merges the associated multicast TB and unicast TB at the physical layer.

[0094] Here, an indication information is added to the scheduling information of the unicast TB, and an indication information is also added to the scheduling information of the multicast TB corresponding to the unicast TB. The unicast TB and the multicast TB are associated through these two indication information, so that the associated multicast TB and unicast TB are merged at the physical layer.

[0095] 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. If the indication information in the two schedulings is the same, the TBs corresponding to the two scheduling information can be associated together and merged at the physical layer.

[0096] In the embodiment of the present application, in order to achieve the association between the unicast TB and the multicast TB, it is necessary to first ensure that the TB content is 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, it can use Figure 4 The protocol stack architecture shown is used to ensure that the contents of the unicast TB and the multicast TB are the same (or the network device ensures that the unicast group packet and the multicast group packet are for the same TB).

[0097] Reference Figure 4 , Figure 4 A structural diagram of the protocol stack on the network device side. Figure 4 The description of "entity" is omitted, for example Figure 4 The "SDAP" in it means "SDAP entity". The PDU session of the MBS service includes one or more QoS streams. One or more QoS streams of the PDU session can be mapped to one or more DRBs through the SDAP entity, where the mapping relationship between the QoS stream and the DRB can be one-to-one or many-to-one. Each DRB corresponds to a logical channel, where different DRBs are transmitted through different PDCP entities and RLC entities, that is, different logical channels correspond to different PDCP entities and RLC entities.

[0098] It should be noted that Figure 4 For each DRB, there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity, or there may be an SDAP entity.

[0099] The MAC entity copies each MAC PDU (ie, one TB of data) to the PHY2 entity, and the original MAC PDU to the PHY1 entity, and sends the MBS service in a multicast manner through the PHY1 entity and in a unicast manner through the PHY2 entity.

[0100] Method 3:

[0101] The terminal device associates the unicast TB and the multicast TB belonging to the same TB according to the serial number (Serial Number, SN) associated with the unicast TB and the SN associated with the multicast TB.

[0102] For example, unicast TB1 is associated with SN1, unicast TB2 is associated with SN2, unicast TB3 is associated with SN3, multicast TB1 is associated with SN1, multicast TB2 is associated with SN2, and multicast TB3 is associated with SN3. According to SN, unicast TB1 can be associated with multicast TB1, unicast TB2 can be associated with multicast TB2, and unicast TB3 can be associated with multicast TB3.

[0103] Further, the terminal device determines feedback information of the unicast mode based on the reception status of the associated unicast TB and multicast TB. Specifically, if the terminal device successfully receives at least one of the unicast TB and the multicast TB, the terminal device replies with a positive confirmation message for the unicast mode; wherein 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.

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

[0105] In one example, when a TB is successfully received via multicast but fails to be received via unicast, the terminal device provides feedback according to a positive acknowledgement (ACK) in the HARQ feedback of the unicast mode.

[0106] In one example, when a TB is successfully received via unicast but fails to be received via multicast, the terminal device provides feedback according to a positive acknowledgement (ACK) in the HARQ feedback in the unicast mode.

[0107] In one example, when a TB is successfully received via unicast and successfully received via multicast, the terminal device provides feedback according to positive acknowledgment (ACK) in the HARQ feedback in the unicast mode.

[0108] In one example, when a TB fails to be successfully received via unicast and fails to be received via multicast, the terminal device provides feedback in the form of negative acknowledgment (NACK) in the HARQ feedback in the unicast mode.

[0109] Through the above scheme, if either unicast TB or multicast TB is successfully received, the terminal device will feedback ACK; if both unicast TB and multicast TB are failed to be received, the terminal device will feedback NACK. In this way, unnecessary unicast retransmission can be avoided, that is, the probability of unicast retransmission is reduced, and the spectrum efficiency is improved.

[0110] According to the above technical solution of the embodiment of the present application, a terminal device receives unicast MBS services and multicast MBS services in a cell at the same time, and merges the unicast MBS services and multicast MBS services at the physical layer, thereby improving the reception reliability of the MBS services.

[0111] ● The terminal device improves reception reliability by repeated reception at the PDCP layer. Specifically, the terminal device performs repeated detection on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the PDCP layer.

[0112] In an optional manner of the present application, the terminal device receives first indication information sent by the first cell, and the first indication information is used to instruct the terminal device to simultaneously receive the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode.

[0113] In an optional method of the present application, the terminal device receives third indication information sent by the first cell, and the third indication information is used to instruct the terminal device whether to merge the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer, or to perform repeated detection of the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the PDCP layer.

[0114] Here, the terminal device receives both the unicast and multicast transmissions 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 can display the first indication information to instruct the terminal device to simultaneously receive the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode. Furthermore, the network device also instructs the terminal device through the third indication information whether to merge the unicast MBS service and the multicast MBS service received simultaneously at the physical layer or to receive them repeatedly at the PDCP layer.

[0115] When the terminal device receives a certain MBS service in unicast mode according to the first indication information, it also receives the MBS service in multicast mode. According to the third indication information, the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer.

[0116] In an optional manner of the present application, the network device further instructs the terminal device to retain the configuration information of the 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 previously received the MBS service in a multicast manner, the terminal device retains the configuration information of the multicast bearer while establishing a unicast bearer to receive the MBS service. In this way, the terminal device retains the configuration information of the multicast bearer when establishing a unicast bearer based on the instruction of the network device.

[0117] In the above scheme, the network device can explicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, or can implicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, which are explained separately below.

[0118] 1) Explicit indication method

[0119] The terminal device receives second indication information sent by the first cell, and the second indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, wherein the unicast bearer is used by the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used by the terminal device to receive the MBS service in a multicast manner.

[0120] 2) Implicit indication method

[0121] The implicit indication can be indicated by referring to the first indication or the second indication in the aforementioned scheme. In an optional manner, the first indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, wherein 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.

[0122] In the embodiment of the present 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 at the PDCP layer according to the SN associated with the MBS service data.

[0123] According to the above technical solution of the embodiment of the present application, the terminal device receives unicast MBS services and multicast MBS services in a cell at the same time, and repeatedly detects the unicast MBS services and multicast MBS services at the PDCP layer, thereby improving the reception reliability of the MBS services.

[0124] In the embodiment of the present application, considering the mobility of the terminal device, there may be a scenario in which the terminal device switches from the first cell to the second cell. The following describes how the terminal device receives the MBS service in this scenario.

[0125] like Figure 5 As shown, there are four scenarios for maintaining continuous reception of MBS services during the switching process:

[0126]

[0127] Table 1

[0128] In an optional manner of the present application, during the process of switching from the first cell to the second cell, the terminal device retains the multicast configuration information of the MBS service on the first cell side.

[0129] Here, during the switching process, the terminal device maintains the multicast configuration information about the MBS service on the original side (ie, the first cell side).

[0130] In an optional method 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 simultaneously receives the MBS service sent by the first cell in a multicast manner and the MBS service sent by the second cell in a multicast manner and / or in a unicast manner; the terminal device performs repeated detection on the received MBS service according to the SN associated with the MBS service data.

[0131] Here, during the switching process or for a period of time after the switching, the terminal device still receives the transmission of the MBS service in the target cell (i.e., the second cell) and the transmission of the MBS service on the original side (i.e., the first cell side) at the same time. The terminal device performs repeated detection on the received MBS service according to the SN associated with the MBS service data.

[0132] In an optional manner of the present application, when the terminal device determines that the target condition is met, the multicast configuration information of the MBS service on the first cell side is released, and the MBS service sent by the first cell in a multicast manner is stopped. Further, optionally, the target condition includes at least one of the following: 1. The terminal device can successfully receive the MBS service of the second cell; 2. The terminal device detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.

[0133] Here, the terminal device decides by itself to release the multicast configuration information about the MBS service on the original side (i.e., the first cell side), and stops receiving the MBS service on the original side. For example: when the terminal device can successfully receive the MBS service of the target cell (i.e., the second cell), and there is no SN gap, the multicast configuration information about the MBS service on the original side (i.e., the first cell side) is released, and the MBS service on the original side is stopped. For another example: when the terminal device detects that the signal quality on the original side (i.e., the first cell side) is lower than a certain threshold, the multicast configuration information about the MBS service on the original side is released, and the MBS service on the original side is stopped.

[0134] In the embodiment of the present application, from the perspective of the network side, the network architecture of the first cell and the second cell may be implemented as follows:

[0135] I) The first cell and the second cell have independent distributed units (DU) and the same centralized unit (CU).

[0136] Here, optionally, the protocol stack entities implemented by the DU include: RLC entity, MAC entity, MAC entity and PHY entity.

[0137] Here, optionally, the protocol stack entities implemented by the CU include: RRC entity and PDCP entity.

[0138] In the above manner, the first cell and the second cell implement an intra-CU scenario.

[0139] II) The first cell and the second cell belong to the same MBS area, and the base station corresponding to the first cell and the base station corresponding to the second cell share an anchor point, which is used to generate PDCP PDU of the MBS service and forward it to all base stations in the MBS area.

[0140] The above technical solution of the embodiment of the present application enables the terminal device to receive the MBS service during the switching process while improving the reception reliability of the MBS service, and can reduce the packet loss rate to ensure the continuity of the MBS service.

[0141] Figure 6 Schematic diagram of the structure of the receiving device of the MBS service provided in the embodiment of the present application, which is applied to the terminal device, such as Figure 6 As shown, the receiving device of the MBS service includes:

[0142] The receiving unit 601 is 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;

[0143] The processing unit 602 is configured to combine the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or perform duplication detection at the PDCP layer.

[0144] In an optional manner, the receiving unit 601 is further used to receive first indication information sent by the first cell, where the first indication information is used to instruct the terminal device to simultaneously receive the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode.

[0145] In an optional manner, the first indication information is also used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, wherein the unicast bearer is used by the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used by the terminal device to receive the MBS service in a multicast manner.

[0146] In an optional manner, the receiving unit 601 is further used to receive second indication information sent by the first cell, and the second indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing a unicast bearer, wherein the unicast bearer is used by the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used by the terminal device to receive the MBS service in a multicast manner.

[0147] In an optional manner, the receiving unit 601 is further used to receive third indication information sent by the first cell, and the third indication information is used to instruct the terminal device whether to merge the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer, or to perform repeated detection of the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the PDCP layer.

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

[0149] The processing unit 602 is configured to associate the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information, and merge the associated multicast TB and unicast TB at the physical layer.

[0150] In an optional manner, the scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information, the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the 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 associated relationship;

[0151] The processing unit 602 is used to associate the multicast TB and the unicast TB belonging 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 the physical layer.

[0152] In an optional manner, the device further includes:

[0153] A sending unit (not shown in the figure) is used to reply a positive confirmation message for the unicast mode if the receiving unit successfully receives at least one of the unicast TB and the multicast TB; wherein 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.

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

[0155] In an optional manner, the processing unit 602 is further used to associate 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 determine the feedback information of the unicast mode based on the reception status of the associated unicast TB and multicast TB.

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

[0157] In an optional manner, the processing unit 602 is further configured to retain the multicast configuration information of the MBS service on the first cell side during the process of the terminal device switching from the first cell to the second cell.

[0158] In an optional manner, the receiving unit 601 is configured to simultaneously receive the MBS service sent by the first cell in a multicast manner and the MBS service sent by the second cell in a multicast manner and / or in a unicast manner during the process of the terminal device switching from the first cell to the second cell and / or after switching to the second cell;

[0159] The processing unit 602 is configured to perform duplication detection on the received MBS service according to the SN associated with the MBS service data.

[0160] 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 when it is determined that the target condition is met;

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

[0162] In an optional manner, the target condition includes at least one of the following:

[0163] The terminal device can successfully receive the MBS service of the second cell;

[0164] The terminal device detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.

[0165] In an optional manner, the first cell and the second cell have independent DUs and the same CU.

[0166] In an optional manner, the first cell and the second cell belong to the same MBS area, and the base station corresponding to the first cell and the base station corresponding to the second cell share an anchor point, which is used to generate PDCP PDU of the MBS service and forward it to all base stations in the MBS area.

[0167] Those skilled in the art should understand that the relevant description of the above-mentioned MBS service receiving device in the embodiment of the present application can be understood by referring to the relevant description of the MBS service receiving method in the embodiment of the present application.

[0168] Figure 7 700 is a schematic structural diagram of a communication device 700 provided in an embodiment of the present application. The communication device may be a terminal device or a network device. Figure 7 The communication device 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0169] Alternatively, if Figure 7As shown, the communication device 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0170] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0171] Alternatively, if Figure 7 As shown, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

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

[0173] Optionally, the communication device 700 may specifically be a network device of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0174] Optionally, the communication device 700 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

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

[0176] Alternatively, if Figure 8 As shown, the chip 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0177] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0178] 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 sent by other devices or chips.

[0179] Optionally, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0180] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0181] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0182] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

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

[0184] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0185] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0186] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0187] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory 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 (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0188] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0189] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0190] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0191] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0192] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0193] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0194] The embodiment of the present application also provides a computer program.

[0195] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0196] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0197] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0198] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0199] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0200] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0201] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0202] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0203] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for receiving a multimedia multicast service (MBS) service, the method comprising: The terminal device receives the MBS service sent by the first cell in a unicast manner, and receives the MBS service sent by the first cell in a multicast manner; The terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or performs duplication detection at the packet data convergence protocol PDCP layer; The scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information, the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the second scheduling information, the unicast TB and the multicast TB are the same TB, the first scheduling information includes the first identification information, the second scheduling information includes the second identification information, and the first identification information and the second identification information have an associated relationship; The terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer, including: The terminal device 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 merges the associated multicast TB and unicast TB at the physical layer.

2. The method according to claim 1, wherein: The terminal device performs duplication detection on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the PDCP layer, including: The terminal device performs duplication detection on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the PDCP layer according to the SN associated with the MBS service data.

3. The method according to claim 1, wherein: The method further comprises: When the terminal device determines that the target condition is met, it releases the multicast configuration information of the MBS service on the first cell side, and stops receiving the MBS service sent by the first cell in a multicast manner.

4. The method according to claim 3, wherein: The target conditions include at least one of the following: The terminal device can successfully receive the MBS service of the second cell; The terminal device detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.

5. The method according to claim 4, wherein: The first cell and the second cell have independent distribution units DU and the same centralization unit CU; and / or, The first cell and the second cell belong to the same MBS area, and the base station corresponding to the first cell and the base station corresponding to the second cell share an anchor point, which is used to generate PDCP PDU of the MBS service and forward it to all base stations in the MBS area.

6. A device for receiving MBS services, the device comprising: A receiving unit, configured to receive an MBS service sent by the first cell in a unicast manner, and receive an MBS service sent by the first cell in a multicast manner; a processing unit, configured to merge the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or perform duplication detection at the PDCP layer; The scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information, the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the second scheduling information, the unicast TB and the multicast TB are the same TB, the first scheduling information includes the first identification information, the second scheduling information includes the second identification information, and the first identification information and the second identification information have an associated relationship; The processing unit is further configured to associate the multicast TB and the unicast TB belonging 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 the physical layer.

7. A terminal device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 5.

8. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 5.

9. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 5.

Images