Method and device for improving MBS service reliability, terminal equipment, and network equipment

Abstract

An embodiment of the present application provides a method and apparatus, terminal equipment, and network equipment for improving the reliability of MBS services. The method includes: the terminal equipment determines a transmission mode of the MBS service; the terminal equipment determines whether a first transmission is a new transmission or a retransmission based on the transmission mode of the MBS service.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a method and apparatus, terminal equipment, and network equipment for improving the reliability of a multicast broadcast service (MBS). Background Art

[0002] In the New Radio (NR) system, multicast MBS services are supported. The terminal device receives multicast MBS services in the Radio Resource Control (RRC) connection state. Generally, the reliability requirements of multicast MBS services are relatively high, and how to ensure the high reliability of MBS services needs to be clarified. Summary of the invention

[0003] The embodiments of the present application provide a method and apparatus, a terminal device, and a network device for improving MBS service reliability.

[0004] The method for improving MBS service reliability provided by the embodiment of the present application includes:

[0005] The terminal device determines the transmission mode of the MBS service;

[0006] The terminal device determines whether the first transmission is a new transmission or a retransmission based on the transmission mode of the MBS service.

[0007] The method for improving MBS service reliability provided by the embodiment of the present application includes:

[0008] The network equipment determines the transmission mode of the MBS service as follows: new transmission is transmitted via PTM mode, and retransmission is transmitted via PTP mode;

[0009] The network device schedules transmission of the MBS service based on the transmission mode of the MBS service.

[0010] The device for improving MBS service reliability provided in the embodiment of the present application is applied to a terminal device, and the device includes:

[0011] A determination unit is used for determining a transmission mode of an MBS service; based on the transmission mode of the MBS service, determining whether the first transmission is a new transmission or a retransmission.

[0012] The device for improving MBS service reliability provided in the embodiment of the present application is applied to a network device, and the device includes:

[0013] A determination unit, used to determine the transmission mode of the MBS service: new transmission is transmitted by PTM mode, and retransmission is transmitted by PTP mode;

[0014] A scheduling unit is used to schedule the transmission of the MBS service based on the transmission mode of the MBS service.

[0015] 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 method for improving the reliability of MBS services.

[0016] The network 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 method for improving the reliability of MBS services.

[0017] The chip provided in the embodiment of the present application is used to implement the above-mentioned method for improving the reliability of MBS services.

[0018] 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 method for improving the reliability of MBS services.

[0019] The computer-readable storage medium provided in the embodiments 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 improving MBS service reliability.

[0020] The computer program product provided in the embodiments of the present application includes computer program instructions, which enable a computer to execute the above-mentioned method for improving MBS service reliability.

[0021] 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 improving MBS service reliability.

[0022] Through the above technical solution, the transmission mode of MBS service is clarified as follows: new transmission is transmitted through point-to-multipoint (PTM) mode, and retransmission is transmitted through point-to-point (PTP) mode. Network equipment schedules the transmission of MBS service based on the transmission mode of MBS service; terminal equipment clarifies whether the first transmission is a new transmission or a retransmission according to the transmission mode of MBS service, thereby ensuring the reliability of MBS service reception to the greatest extent. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] 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:

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

[0025] Figure 2 It is a schematic diagram of the transmission of the MBS service provided by the embodiment of the present application in the PTM mode and the PTP mode;

[0026] Figure 3 This is a flow chart of a method for improving MBS service reliability provided by an embodiment of the present application. Figure 1 ;

[0027] Figure 4 It is a schematic diagram of the first protocol stack architecture provided in an embodiment of the present application;

[0028] Figure 5 It is a schematic diagram of the second protocol stack architecture provided in an embodiment of the present application;

[0029] Figure 6 This is a flow chart of a method for improving MBS service reliability provided by an embodiment of the present application. Figure 2 ;

[0030] Figure 7 The structure of the device for improving the reliability of MBS services provided by the embodiment of the present application is shown in FIG. Figure 1 ;

[0031] Figure 8 The structure of the device for improving the reliability of MBS services provided by the embodiment of the present application is shown in FIG. Figure 2 ;

[0032] Fig. 9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0033] Fig.10 is a schematic structural diagram of a chip according to an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

[0046] 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).

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

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

[0049] RRC Status

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

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

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

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

[0054] Multimedia Broadcast Multicast Service (MBMS)

[0055] MBMS is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. While providing multimedia services, this technology can effectively utilize network resources and achieve broadcast and multicast of multimedia services at a higher rate (such as 256kbps).

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

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

[0058] 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 terminal devices in an idle state or a connected state.

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

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

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

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

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

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

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

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

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

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

[0069] It should be noted that although the above solution is described by taking the MBMS service as an example, the technical solution of the embodiment of the present application is not limited thereto. The embodiment of the present application is described by taking the MBS service as an example, and the description of "MBS service" can also be replaced by "multicast service" or "groupcast service" or "MBMS service".

[0070] In the NR system, many scenarios need to support multicast and broadcast service requirements, such as in the Internet of Vehicles and the Industrial Internet. Therefore, it is necessary to introduce multicast and broadcast MBS services in NR. It should be noted that multicast MBS services refer to MBS services transmitted by multicast. Broadcast MBS services refer to MBS services transmitted by broadcast.

[0071] In the NR system, for multicast MBS services, the MBS services are sent to all terminal devices in a group. The terminal device receives multicast MBS services in the RRC connection state, and the terminal device can receive multicast MBS service data through PTM or PTP. Among them, the MBS service data of the PTM mode is scrambled with the corresponding scheduling information through the G-RNTI configured on the network side, and the MBS service data of the PTP mode is scrambled with the corresponding scheduling information through the C-RNTI.

[0072] The reliability requirement of multicast MBS services is relatively high, and it is necessary to clarify how to ensure the high reliability of MBS services. To this end, the following technical solutions of the embodiments of the present application are proposed.

[0073] The technical solution of the embodiment of the present application proposes a transmission mode for MBS services, that is, new transmission is transmitted through PTM mode, and retransmission is transmitted through PTP mode. In other words, PTP transmission can be used as a retransmission of PTM transmission. How to support this transmission mode so that the terminal device can correctly soft-combine the new transmission and retransmission to achieve the maximum receiving gain needs to be clarified.

[0074] It should be noted that in the embodiments of the present application, the description of "new transmission" can also be replaced by "initial transmission", and the description of "retransmission" can also be replaced by "retransmission".

[0075] In the embodiment of the present application, the MSB service is transmitted via multicast. In other words, the MSB service is a multicast type MBS service. Specifically, after the base station receives the MBS service sent by the core network from the shared tunnel (tunnel), it can send the MSB service to all terminal devices in a group through the air interface. Here, the base station can send the MSB service to all terminal devices in a group via the PTP method and / or the PTM method. For example: a group includes terminal device 1, terminal device 2 and terminal device 3. The base station can send the MBS service to terminal device 1 via the PTP method, send the MBS service to terminal device 2 via the PTP method, and send the MBS service to terminal device 3 via the PTP method; or, the base station can send the MBS service to terminal device 1 via the PTP method, and send the MBS service to terminal device 2 and terminal device 3 via the PTM method; or, the base station can send the MBS service to terminal device 1, terminal device 2 and terminal device 3 via the PTM method. Reference Figure 2 A shared GTP tunnel is used between the core network and the base station to transmit MBS services, that is, both PTM and PTP MBS services share this GTP tunnel. The base station sends MBS service data to UE1 and UE2 in PTM mode, and sends MBS service data to UE3 in PTP mode.

[0076] Figure 3 This is a flow chart of a method for improving MBS service reliability provided by an embodiment of the present application. Figure 1 ,like Figure 3 As shown, the MBS service reliability method includes the following steps:

[0077] Step 301: The terminal device determines the transmission mode of the MBS service.

[0078] In the embodiment of the present application, the transmission mode of the MBS service is: new transmission is transmitted by PTM mode, and retransmission is transmitted by PTP mode. In other words, the transmission mode of the MBS service is: PTP transmission is used for retransmission of PTM transmission.

[0079] Here, the scheduling information of the transmission corresponding to the PTM mode is scrambled by the G-RNTI, and the scheduling information of the transmission corresponding to the PTP mode is scrambled by the C-RNTI.

[0080] In the embodiment of the present application, the terminal device may determine the transmission mode of the MBS service in the following manner:

[0081] The terminal device receives the configuration information of the MBS service sent by the network device, and determines the transmission mode of the MBS service based on the configuration information of the MBS service; wherein the configuration information of the MBS service includes first information, and the first information is used to indicate that the transmission mode of the MBS service is: new transmission is transmitted via PTM mode, and retransmission is transmitted via PTP mode.

[0082] In some optional embodiments of the present application, the configuration information of the MBS service is configured through RRC dedicated signaling.

[0083] In some optional implementations, the configuration information of the MBS service includes at least one of the following: identification information of the MBS service, channel configuration information of the MBS service. In this way, the terminal device can receive the MBS service data based on the configuration information of the MBS service.

[0084] In some optional embodiments of the present application, the identification information of the MBS service in the configuration information of the MBS service is used by the terminal device to determine which MBS service to receive. In some examples, the identification information of the MBS service may be TMGI, G-RNTI, etc.

[0085] In some optional embodiments of the present application, the channel configuration information of the MBS service in the configuration information of the MBS service is used by the terminal device to determine the channel information for receiving the MBS service. In some examples, the channel configuration information of the MBS service may include at least one of the following: configuration information of the control channel of the MBS service (such as configuration information of the MCCH), configuration information of the service channel (also called data channel or transport channel) of the MBS service (such as configuration information of the MTCH).

[0086] In some optional embodiments of the present application, the configuration information of the MBS service further includes second information, and the second information is used to indicate that the protocol stack architecture of the MBS service is the first protocol stack architecture or the second protocol stack architecture. In this way, the terminal device determines the protocol stack architecture of the MBS service based on the configuration information of the MBS service.

[0087] In some optional embodiments of the present application, if the network side has not configured the protocol stack architecture of the MBS service, the terminal device determines that the protocol stack architecture of the MBS service is a default protocol stack architecture based on predefined information; wherein the default protocol stack architecture is a first protocol stack architecture or a second protocol stack architecture.

[0088] The first protocol stack architecture and the second protocol stack architecture in the above solution are described below. It should be noted that the following protocol stack architecture is only an exemplary description, and any protocol stack architecture that can implement the PTM mode and the PTP mode can be applied to the embodiments of the present application.

[0089] First protocol stack architecture

[0090] In the first protocol stack architecture, the PTM mode and the PTP mode correspond to independent physical (PHY) entities; the PTM mode and the PTP mode correspond to shared packet data convergence protocol (Packet Data Convergence Protocol, PDCP) entity, radio link control (Radio Link Control, RLC) entity, and media access control (Media Access Control, MAC) entity.

[0091] Further, optionally, the PTM mode and the PTP mode correspond to a shared Service Data Adaptation Protocol (SDAP) entity.

[0092] In one example, referring to Figure 4 , Figure 4 is a schematic diagram of the first protocol stack architecture, Figure 4 The description of "entity" is omitted, for example Figure 4 The "PHY" in it means "PHY 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.

[0093] It should be noted that Figure 4For each DRB, there may be no SDAP entity. That is, for each DRB, there may be a PDCP entity or a PDCP entity + SDAP entity. The MAC entity sends the MAC PDU (i.e., one TB of data) to the PHY1 entity, which is sent by the PHY1 entity in a PTM manner; or, the MAC entity sends the MAC PDU to the PHY2 entity, which is sent by the PHY2 entity in a PTP manner.

[0094] Second protocol stack architecture

[0095] In the second protocol stack architecture, the PTM mode and the PTP mode correspond to independent PHY entities and RLC entities; the PTM mode and the PTP mode correspond to shared PDCP entities and MAC entities.

[0096] Further, optionally, the PTM mode and the PTP mode correspond to a shared SDAP entity.

[0097] Reference Figure 5 , Figure 5 is a schematic diagram of the second protocol stack architecture, Figure 4-3 The description of "entity" is omitted, for example Figure 4-3 The "PHY" in it means "PHY 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 5 For each DRB, there may be no PDCP entity. That is to say, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity. The PDCP entity sends the PDCP PDU to the RLC1 entity, the RLC1 entity transmits the corresponding RLC PDU to the MAC entity, the MAC entity transmits the corresponding MAC PDU to the PHY1 entity, and the PHY1 entity sends it in PTM mode; or, the PDCP entity sends the PDCP PDU to the RLC2 entity, the RLC2 entity transmits the corresponding RLC PDU to the MAC entity, the MAC entity transmits the corresponding MAC PDU to the PHY2 entity, and the PHY2 entity sends it in PTP mode.

[0099] It should be noted that Figure 5The RLC1 entity includes RLC11 entity, RLC12 entity, ..., RLC1n entity, wherein different RLC entities correspond to different DRBs (ie, to different logical channels). Figure 5 The RLC2 entity includes an RLC21 entity, an RLC22 entity, ..., an RLC2n entity, wherein different RLC entities correspond to different DRBs (ie, to different logical channels).

[0100] Step 302: The terminal device determines whether the first transmission is a new transmission or a retransmission based on the transmission mode of the MBS service.

[0101] In an embodiment of the present application, a terminal device receives MBS service data based on the service configuration of the MBS. Specifically, the terminal device receives first downlink scheduling information encrypted by a first RNTI, the first downlink scheduling information is used to schedule the first transmission, and the first downlink scheduling information carries a first new data indication (New Data Indication, NDI); wherein, when the transmission mode of the MBS service is that the new transmission is transmitted by PTM mode and the retransmission is transmitted by PTP mode, the terminal device determines whether the first transmission is a new transmission or a retransmission based on the first RNTI and / or the first NDI. The following describes how the first transmission is what type of transmission. It should be noted that in an embodiment of the present application, the description of "downlink scheduling information" can also be replaced by "DL grant".

[0102] Case 1: If the first RNTI is a G-RNTI, the terminal device determines that the first transmission is a new transmission.

[0103] Specifically, the terminal device receives the first downlink scheduling information encrypted by G-RNTI, wherein the first downlink scheduling information carries a first hybrid automatic repeat request (HARQ) process identifier and a first NDI. As an example, the first HARQ process identifier can be expressed as HARQ process id=k, that is, the value of the first HARQ process identifier is k. The terminal device receives the first transmission according to the first downlink scheduling information, where receiving the first transmission can also be understood as receiving MBS service data carried on the PDSCH. Since the first downlink scheduling information for scheduling the first transmission is encrypted by G-RNTI, the first transmission scheduled by the first downlink scheduling information is a new transmission. Here, regardless of whether the downlink scheduling information before the first downlink scheduling information is encrypted by C-RNTI or by G-RNTI, the first transmission scheduled by the first downlink scheduling information is considered to be a new transmission, that is, it is considered that an NDI flip has occurred.

[0104] For example, the description of downlink scheduling information can be equivalently replaced by DL Grant. In addition, the transmission scheduled by the downlink scheduling information can be equivalently replaced by the transport block (TB) scheduled by the DL Grant.

[0105] In an example, the network side sends DL Grant 1 encrypted with G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device receives DL Grant 1 encrypted with G-RNTI, receives TB1 based on DL Grant 1, successfully decodes TB1, and feeds back HARQ-ACK information; after receiving the HARQ-ACK information, the network side sends DL Grant 2 encrypted with G-RNTI, and sends TB2 scheduled by DL Grant 2; the terminal device receives DL Grant 2 encrypted with G-RNTI, receives a TB2 based on DL Grant 2, and considers TB2 to be a new transmission.

[0106] In an example, the network side sends DL Grant 1 scrambled by G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device receives DL Grant 1 scrambled by G-RNTI, receives TB1 based on DL Grant 1, fails to decode TB1, and feeds back HARQ-NACK information; after receiving the HARQ-NACK information, the network side switches the PTM mode to the PTP mode, sends DL Grant 2 scrambled by C-RNTI, and sends TB1 scheduled by DL Grant 2; the terminal device receives DL Grant 2 scrambled by C-RNTI, receives the retransmission of TB1 based on DL Grant 2, successfully decodes TB1, and feeds back HARQ-ACK information; after receiving the HARQ-ACK information, the network side sends DL Grant 3 scrambled by G-RNTI, and sends TB2 scheduled by DL Grant 3; the terminal device receives DL Grant 3 scrambled by G-RNTI, receives TB2 based on DL Grant 3, and considers TB2 to be a new transmission.

[0107] In an example, the network side sends DL Grant 1 encrypted with G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device does not receive DL Grant 1 and does not feed back any HARQ feedback information; the network side does not receive any HARQ feedback information within a certain period of time after sending DL Grant 1, switches the PTM mode to the PTP mode, sends DL Grant 2 encrypted with C-RNTI, and sends TB1 scheduled by DL Grant 2; the terminal device receives DL Grant 2 encrypted with C-RNTI, receives the retransmission of TB1 based on DL Grant 2, successfully decodes TB1, and feeds back HARQ-ACK information; after receiving the HARQ-ACK information, the network side sends DL Grant 3 encrypted with G-RNTI, and sends TB2 scheduled by DL Grant 3; the terminal device receives DL Grant 3 encrypted with G-RNTI, receives TB2 based on DL Grant 3, and considers TB2 as a new transmission.

[0108] In one example, the network side sends TB1 of unicast scheduling or semi-persistent scheduling (SPS), and then sends DL Grant 1 encrypted with G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device receives DL Grant 1 encrypted with G-RNTI, receives TB1 based on DL Grant 1, and considers TB1 as a new transmission.

[0109] It should be noted that for the transmission (including new transmission and retransmission) of the same TB (or the same MBS service data), the corresponding HARQ process identifier is the same, and the HARQ process identifier is carried in the DL Grant that schedules the TB.

[0110] It should be noted that if the DL Grant is scrambled by G-RNTI, the TB scheduled by the DL Grant is transmitted by PTM; if the DL Grant is scrambled by C-RNTI, the TB scheduled by the DL Grant is transmitted by PTP.

[0111] Case 2: If the first RNTI is C-RNTI, and the first NDI is different from the second NDI, the terminal device determines that the first transmission is a new transmission; wherein the second NDI is carried in the second downlink scheduling information, the second downlink scheduling information is the downlink scheduling information received by the terminal device before the first downlink scheduling information, the second downlink scheduling information is used to schedule the second transmission, and the second transmission and the first transmission both correspond to the first hybrid automatic repeat request HARQ process identifier.

[0112] Here, the second downlink scheduling information is scrambled by G-RNTI; or, the second downlink scheduling information is scrambled by C-RNTI.

[0113] Specifically, the terminal device receives the first downlink scheduling information encrypted by C-RNTI, wherein the first downlink scheduling information carries the first HARQ process identifier and the first NDI. As an example, the first HARQ process identifier can be expressed as HARQprocess id=k, that is, the value of the first HARQ process identifier is k. The terminal device receives the first transmission according to the first downlink scheduling information, where receiving the first transmission can also be understood as receiving the MBS service data carried on the PDSCH. Since the first downlink scheduling information for scheduling the first transmission is encrypted by C-RNTI, it is necessary to compare the first NDI carried in the first downlink scheduling information with the second NDI carried in the second downlink scheduling information previously received. If the first NDI is different from the second NDI, regardless of whether the second downlink scheduling information is encrypted by C-RNTI or G-RNTI, the first transmission scheduled by the first downlink scheduling information is considered to be a new transmission, that is, it is considered that an NDI flip occurs; if the first NDI is the same as the second NDI, the first transmission scheduled by the first downlink scheduling information is considered to be a retransmission, that is, it is considered that the NDI is not flipped.

[0114] For example, the description of downlink scheduling information can be equivalently replaced by DL Grant. In addition, the transmission scheduled by the downlink scheduling information can be equivalently replaced by the TB scheduled by the DL Grant.

[0115] In an example, the network side sends DL Grant 1 scrambled by G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device receives DL Grant 1 scrambled by G-RNTI, receives TB1 based on DL Grant 1, successfully decodes TB1, and feeds back HARQ-ACK information; after receiving the HARQ-ACK information, the network side sends DL Grant 2 scrambled by C-RNTI, and sends TB2 scheduled by DL Grant 2; the terminal device receives DL Grant 2 scrambled by C-RNTI, and receives a TB2 based on DL Grant 2. Since the NDI carried in DL Grant 2 is different from the NDI carried in DL Grant 1, TB2 is considered to be a new transmission.

[0116] In an example, the network side sends DL Grant 1 scrambled by G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device receives DL Grant 1 scrambled by G-RNTI, receives TB1 based on DL Grant 1, fails to decode TB1, and feeds back HARQ-NACK information; after receiving the HARQ-NACK information, the network side switches the PTM mode to the PTP mode, sends DL Grant 2 scrambled by C-RNTI, and sends TB1 scheduled by DL Grant 2; the terminal device receives DL Grant 2 scrambled by C-RNTI, receives the retransmission of TB1 based on DL Grant 2, successfully decodes TB1, and feeds back HARQ-ACK information; after receiving the HARQ-ACK information, the network side sends DL Grant 3 scrambled by C-RNTI, and sends TB2 scheduled by DL Grant 3; the terminal device receives DL Grant 3 scrambled by C-RNTI, and receives TB2 based on DL Grant 3. Since the NDI carried in DL Grant 3 is different from the NDI carried in DL Grant 2, TB2 is considered to be a new transmission.

[0117] In an example, the network side sends DL Grant 1 encrypted with G-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device does not receive DL Grant 1 and does not feed back any HARQ feedback information; the network side does not receive any HARQ feedback information within a certain period of time after sending DL Grant 1, switches the PTM mode to the PTP mode, sends DL Grant 2 encrypted with C-RNTI, and sends TB1 scheduled by DL Grant 2; the terminal device receives DL Grant 2 encrypted with C-RNTI, receives the retransmission of TB1 based on DL Grant 2, successfully decodes TB1, and feeds back HARQ-ACK information; after receiving the HARQ-ACK information, the network side sends DL Grant 3 encrypted with C-RNTI, and sends TB2 scheduled by DL Grant 3; the terminal device receives DL Grant 3 encrypted with C-RNTI, and receives TB2 based on DL Grant 3. Since the NDI carried in DL Grant 3 is different from the NDI carried in DL Grant 2, TB2 is considered to be a new transmission.

[0118] In one example, the network side sends TB1 of unicast scheduling or semi-persistent scheduling (SPS), and then sends DL Grant 1 encrypted with C-RNTI, and sends TB1 scheduled by DL Grant 1; the terminal device receives DL Grant 1 encrypted with C-RNTI, receives TB1 based on DL Grant 1, and considers TB1 as a new transmission.

[0119] Case three: If the first RNTI is C-RNTI and there is no second NDI associated with the first NDI, the terminal device determines that the first transmission is a new transmission; wherein, the association of the second NDI with the first NDI means that the HARQ process identifier corresponding to the second NDI is the same as the HARQ process identifier corresponding to the first NDI.

[0120] Specifically, the terminal device receives the first downlink scheduling information encrypted by C-RNTI, wherein the first downlink scheduling information carries the first HARQ process identifier and the first NDI. As an example, the first HARQ process identifier can be expressed as HARQprocess id=k, that is, the value of the first HARQ process identifier is k. The terminal device receives the first transmission according to the first downlink scheduling information, where receiving the first transmission can also be understood as receiving the MBS service data carried on the PDSCH. Since the first downlink scheduling information for scheduling the first transmission is encrypted by C-RNTI, it is necessary to compare the first NDI carried in the first downlink scheduling information with the second NDI carried in the second downlink scheduling information received previously. However, the downlink scheduling information associated with the same HARQ process identifier as the first downlink scheduling information has not been received previously, and there is no NDI that can be compared with the first NDI, so the first transmission scheduled by the first downlink scheduling information is considered to be a new transmission.

[0121] In some optional implementations, the technical solution of the embodiment of the present application also includes:

[0122] If the first transmission is a new transmission, the terminal device decodes the first transmission to obtain a decoding result;

[0123] If the decoding result is successful, the terminal device feeds back HARQ ACK information;

[0124] If the decoding result is a decoding failure, the terminal device feeds back HARQ NACK information and stores the data corresponding to the first transmission in a cache.

[0125] Here, decoding is implemented by the physical layer of the terminal device, and the terminal device feeds back HARQ NACK information or HARQ ACK information to the network side according to the decoding result of the physical layer. Further, if the terminal device feeds back HARQ NACK information, the terminal device stores the received data soft bits in a HARQ buffer.

[0126] For the network side, after the base station sends a TB via the PTM mode, if the base station receives HARQ NACK information for the TB fed back by a terminal device or does not receive any HARQ feedback information for the TB fed back by a terminal device, then the base station will switch the terminal device to the PTP mode and retransmit the TB to the terminal device via the PTP mode. In the retransmission scheduling of the PTP mode, the scheduling information of the TB is encrypted by C-RNTI. In addition, the HARQ process identifier carried in the scheduling information of the TB is the same as the HARQ process identifier carried in the scheduling information corresponding to the previous PTM mode. In addition, the value of the NDI carried in the scheduling information of the TB is also the same as the value of the NDI carried in the scheduling information corresponding to the previous PTM mode.

[0127] For the terminal device side, when the terminal device does not feed back HARQ ACK information, the terminal device receives the third downlink scheduling information encrypted by C-RNTI, and the third downlink scheduling information is used to schedule a third transmission, and the third transmission and the first transmission both correspond to a first HARQ process identifier; the terminal device soft-merges the data corresponding to the third transmission and the data corresponding to the first transmission in the cache and decodes them to obtain a decoding result; if the decoding result is a successful decoding, the terminal device feeds back HARQ ACK information; if the decoding result is a decoding failure, the terminal device feeds back HARQ NACK information and stores the data corresponding to the third transmission in the cache.

[0128] For example: the terminal device receives the third downlink scheduling information encrypted by C-RNTI, and the first HARQ process identifier is indicated in the third downlink scheduling information, and the HARQ process corresponding to the first HARQ process identifier has cached data, then the terminal device soft-merges the data scheduled by the received third downlink scheduling information and the cached data and then decodes them, and determines whether to feedback HARQ ACK information or HARQ NACK information based on the decoding result.

[0129] On the network side, for a TB, the HARQ feedback corresponding to the PTM mode and the HARQ feedback corresponding to the PTP mode are comprehensively considered. If the HARQ feedback of all terminal devices in the MBS group for the TB are HARQ ACK information, the base station executes a new transmission of the next TB according to the HARQ process identifier of the TB.

[0130] In an embodiment of the present application, when the decoding result in the above scheme is successful decoding, the terminal device obtains the first TB, and it can be understood that the first TB corresponds to the first HARQ process identifier; the terminal device obtains the first MAC SDU and the first LCID corresponding to the MAC SDU from the first TB; the terminal device determines the RLC entity to which the first MAC SDU is to be delivered based on the first LCID and the first HARQ process identifier.

[0131] Case 1

[0132] In one case, the first HARQ process identifier belongs to a first HARQ process identifier set, and the first LCID belongs to a first LCID set; the first HARQ process identifier set does not overlap with the second HARQ process identifier set, and the first LCID set at least partially overlaps with the second LCID set; wherein the first HARQ process identifier set and the first LCID set are used for MBS services, and the second HARQ process identifier set and the second LCID set are used for unicast services. Here, the unicast service is, for example, an eMBB unicast service.

[0133] In this case, the HARQ process identifier set used for the MBS service and the HARQ process identifier set used for the unicast service do not overlap, and the network side can configure the HARQ process identifier set dedicated to the MBS service for the terminal device through dedicated signaling.

[0134] As an example, the HARQ process identifiers in the HARQ process identifier set range from 0 to N, where N is a positive integer. HARQ process identifiers from 0 to k, where k is a positive integer greater than or equal to 0 and less than or equal to N, can be reserved for MBS services, while other HARQ process identifiers are used for unicast services.

[0135] The terminal device determines that the first HARQ process identifier is used for MBS service based on the fact that the first HARQ process identifier belongs to the first HARQ process identifier set; the terminal device determines the RLC entity corresponding to the first LCID from the RLC entities corresponding to the MBS service as the RLC entity to which the first MAC SDU is to be delivered.

[0136] For example: there are 4 RLC entities in total, among which RLC entity 1 and RLC entity 2 are RLC entities corresponding to MBS services, RLC entity 3 and RLC entity 4 are RLC entities corresponding to unicast services, RLC entity 1 corresponds to LCID1, RLC entity 2 corresponds to LCID2, RLC entity 3 corresponds to LCID1, and RLC entity 4 corresponds to LCID2. The terminal device decodes and obtains TB, obtains MAC SDU and the corresponding LCID1 from the TB, and determines that it belongs to the TB of MBS services according to the HARQ process identifier corresponding to the TB, determines from RLC entity 1 and RLC entity 2 that LCID1 corresponds to RLC entity 1, and delivers MAC SDU to RLC entity 1.

[0137] Case 2

[0138] In one case, the first HARQ process identifier belongs to a first HARQ process identifier set, and the first LCID belongs to a first LCID set; the first HARQ process identifier set at least partially overlaps with the second HARQ process identifier set, and the first LCID set does not overlap with the second LCID set; wherein the first HARQ process identifier set and the first LCID set are used for MBS services, and the second HARQ process identifier set and the second LCID set are used for unicast services.

[0139] In this case, the HARQ process identifier set for the MBS service and the HARQ process identifier set for the unicast service at least partially overlap, for example, completely overlap. However, the LCID set for the MBS service and the LCID set for the unicast service do not overlap, and the network side can configure the LCID set dedicated to the MBS service for the terminal device through dedicated signaling.

[0140] The terminal device determines the RLC entity corresponding to the first LCID from the RLC entities corresponding to the MBS service and the RLC entities corresponding to the unicast service as the RLC entity to which the first MAC SDU is to be delivered.

[0141] For example: there are 4 RLC entities in total, among which RLC entity 1 and RLC entity 2 are RLC entities corresponding to MBS services, RLC entity 3 and RLC entity 4 are RLC entities corresponding to unicast services, RLC entity 1 corresponds to LCID1, RLC entity 2 corresponds to LCID2, RLC entity 3 corresponds to LCID3, and RLC entity 4 corresponds to LCID4. The terminal device decodes and obtains TB, obtains MAC SDU and the corresponding LCID1 from the TB, and cannot determine which MBS service it belongs to based on the HARQ process identifier corresponding to the TB. It can directly determine that LCID1 corresponds to RLC entity 1 from all RLC entities based on LCID1, and deliver the MAC SDU to RLC entity 1.

[0142] Figure 6 This is a flow chart of a method for improving MBS service reliability provided by an embodiment of the present application. Figure 2 ,like Figure 6 As shown, the MBS service reliability method includes the following steps:

[0143] Step 601: The network device determines the transmission mode of the MBS service: new transmission is transmitted by PTM mode, and retransmission is transmitted by PTP mode.

[0144] Step 602: The network device schedules the transmission of the MBS service based on the transmission mode of the MBS service.

[0145] In an embodiment of the present application, the network device schedules new transmission of the first service data via a PTM method; and / or, the network device schedules retransmission of the first service data via a PTP method; wherein the first service data is service data of the MBS service.

[0146] In some optional implementations, the network device sends first downlink scheduling information encrypted with a G-RNTI, where the first downlink scheduling information is used to schedule new transmission of first service data, and the first downlink scheduling information carries a first HARQ process identifier.

[0147] In some optional implementations, the network device sends third downlink scheduling information encrypted with C-RNTI, the third downlink scheduling information is used to schedule retransmission of the first service data, and the third downlink scheduling information carries the first HARQ process identifier. Further, the NDI carried in the third downlink scheduling information is the same as the NDI carried in the first downlink scheduling information.

[0148] In the embodiment of the present application, for the MBS service, multiple terminal devices receiving the MBS service are called an MBS group. In the MBS group, some terminal devices need to retransmit, while some terminal devices do not need to retransmit. For the terminal devices that need to retransmit, the PTP mode is used for transmission. Specifically, the network device schedules the retransmission of the first service data to each terminal device in the at least one terminal device respectively through the PTP mode; wherein the at least one terminal device is at least one terminal device in the MBS group.

[0149] Here, the at least one terminal device includes: at least one terminal device that feeds back HARQ NACK information for the first service data; and / or at least one terminal device that does not feed back HARQ feedback information for the first service data.

[0150] As an example, the MBS group includes four UE1, UE2, UE3 and UE4. The base station sends TB1 to the MBS group through PTM. The base station receives HARQ ACK information for TB1 fed back by UE1 and UE4, receives HARQ NACK information for TB1 fed back by UE2, and does not receive any HARQ feedback information for TB1 fed back by UE3. The base station schedules the retransmission of TB1 to UE2 and UE3 respectively through PTP. Specifically, the base station sends C-RNTI-scrambled scheduling information to UE2 and UE3 respectively, and the scheduling information is used to schedule the retransmission of TB1.

[0151] In an embodiment of the present application, when the network device receives HARQACK information for the first service data fed back by all terminal devices in the MBS group, it schedules new transmission of the second service data through the PTM method, and the second service data is the next data to be transmitted of the first service data.

[0152] As an example, the MBS group includes four UE1, UE2, UE3 and UE4. The base station sends TB1 to the MBS group through PTM. The base station receives HARQ ACK information for TB1 fed back by UE1 and UE4, receives HARQ NACK information for TB1 fed back by UE2, and does not receive any HARQ feedback information for TB1 fed back by UE3. The base station schedules the retransmission of TB1 to UE2 and UE3 respectively through PTP, and then the base station receives HARQ ACK information for TB1 fed back by UE2 and UE3. So far, the base station has received HARQ ACK information for TB1 fed back by all UEs in the MBS group and performs a new transmission of the next TB2. Here, the HARQ identification of TB2 can be carried out by using the previous HARQ identification of TB1. The new transmission of TB2 can adopt the PTM method.

[0153] It should be noted that the above Figure 6 Related technical solutions can be Figure 3 The relevant technical solutions can be implemented by any combination.

[0154] Figure 7 The structure of the device for improving the reliability of MBS services provided by the embodiment of the present application is shown in FIG. Figure 1 , applied to terminal devices, such as Figure 7 As shown, the device for improving MBS service reliability includes:

[0155] The determining unit 701 is configured to determine the transmission mode of the MBS service and to determine whether the first transmission is a new transmission or a retransmission based on the transmission mode of the MBS service.

[0156] In some optional embodiments, the device further comprises:

[0157] The receiving unit 702 is configured to receive the configuration information of the MBS service sent by the network device; wherein the configuration information of the MBS service includes first information, and the first information is used to indicate that the transmission mode of the MBS service is: new transmission is transmitted by PTM mode, and retransmission is transmitted by PTP mode;

[0158] The determining unit 701 is configured to determine a transmission mode of the MBS service based on the configuration information of the MBS service.

[0159] In some optional implementations, the determining unit 701 is further configured to determine a protocol stack architecture of the MBS service based on the configuration information of the MBS service;

[0160] The configuration information of the MBS service also includes second information, and the second information is used to indicate that the protocol stack architecture of the MBS service is the first protocol stack architecture or the second protocol stack architecture.

[0161] In some optional implementations, the determining unit 701 is further configured to determine, based on predefined information, that the protocol stack architecture of the MBS service is a default protocol stack architecture;

[0162] The default protocol stack architecture is the first protocol stack architecture or the second protocol stack architecture.

[0163] In some optional implementations, in the first protocol stack architecture,

[0164] The PTM mode and PTP mode correspond to independent PHY entities;

[0165] The PTM mode and the PTP mode correspond to a shared PDCP entity, an RLC entity, and a MAC entity.

[0166] In some optional implementations, in the second protocol stack architecture,

[0167] The PTM mode and PTP mode correspond to independent PHY entities and RLC entities;

[0168] The PTM mode and the PTP mode correspond to a shared PDCP entity and a shared MAC entity.

[0169] In some optional embodiments, the device further comprises:

[0170] A receiving unit 702 is configured to receive first downlink scheduling information scrambled by a first RNTI, where the first downlink scheduling information is used to schedule the first transmission, and the first downlink scheduling information carries a first NDI;

[0171] The determining unit 701 is configured to determine whether the first transmission is a new transmission or a retransmission based on the first RNTI and / or the first NDI when the transmission mode of the MBS service is that the new transmission is transmitted in a PTM mode and the retransmission is transmitted in a PTP mode.

[0172] In some optional implementations, the determining unit 701 is configured to determine that the first transmission is a new transmission if the first RNTI is a group radio network temporary identifier G-RNTI.

[0173] In some optional implementations, the determining unit 701 is configured to determine that the first transmission is a new transmission if the first RNTI is a C-RNTI and the first NDI is different from the second NDI;

[0174] Among them, the second NDI is carried in the second downlink scheduling information, the second downlink scheduling information is the downlink scheduling information received by the terminal device before the first downlink scheduling information, the second downlink scheduling information is used to schedule the second transmission, and the second transmission and the first transmission both correspond to the first HARQ process identifier.

[0175] In some optional implementations, the second downlink scheduling information is scrambled by G-RNTI; or,

[0176] The second downlink scheduling information is scrambled by using the C-RNTI.

[0177] In some optional implementations, the determining unit 701 is configured to determine that the first transmission is a new transmission if the first RNTI is a C-RNTI and there is no second NDI associated with the first NDI;

[0178] The association between the second NDI and the first NDI means that the HARQ process identifier corresponding to the second NDI is the same as the HARQ process identifier corresponding to the first NDI.

[0179] In some optional embodiments, the device further comprises:

[0180] a decoding unit, configured to decode the first transmission to obtain a decoding result if the first transmission is a new transmission;

[0181] A feedback unit, configured to feedback HARQ ACK information if the decoding result is a decoding success; and feedback HARQ NACK information if the decoding result is a decoding failure;

[0182] A storage unit is used to store the data corresponding to the first transmission into a cache if the decoding result is a decoding failure.

[0183] In some optional implementations, the receiving unit 701 is further configured to receive third downlink scheduling information scrambled by the C-RNTI, where the third downlink scheduling information is used to schedule a third transmission, and both the third transmission and the first transmission correspond to a first HARQ process identifier;

[0184] The decoding unit is further used to perform soft merging and decoding on the data corresponding to the third transmission and the data corresponding to the first transmission in the cache to obtain a decoding result;

[0185] The feedback unit is further configured to, if the decoding result is a decoding success, cause the terminal device to feed back HARQ ACK information; if the decoding result is a decoding failure, cause the terminal device to feed back HARQ NACK information;

[0186] The storage unit is further configured to store the data corresponding to the third transmission in the cache if the decoding result is a decoding failure.

[0187] In some optional implementations, when the decoding result is successful decoding, the decoding unit obtains a first TB, and the first TB corresponds to a first HARQ process identifier;

[0188] The decoding unit is further configured to obtain a first MAC SDU and a first LCID corresponding to the MAC SDU from the first TB;

[0189] The determination unit 701 is further used to determine the RLC entity to which the first MAC SDU is to be delivered based on the first LCID and the first HARQ process identifier.

[0190] In some optional implementations, the first HARQ process identifier belongs to a first HARQ process identifier set, and the first LCID belongs to a first LCID set;

[0191] The first HARQ process identifier set does not overlap with the second HARQ process identifier set, and the first LCID set at least partially overlaps with the second LCID set;

[0192] The first HARQ process identifier set and the first LCID set are used for MBS services, and the second HARQ process identifier set and the second LCID set are used for unicast services.

[0193] In some optional embodiments, the determination unit 701 is used to determine that the first HARQ process identifier is used for MBS service based on the fact that the first HARQ process identifier belongs to the first HARQ process identifier set; and determine the RLC entity corresponding to the first LCID from the RLC entities corresponding to the MBS service as the RLC entity to which the first MAC SDU is to be delivered.

[0194] In some optional implementations, the first HARQ process identifier belongs to a first HARQ process identifier set, and the first LCID belongs to a first LCID set;

[0195] The first HARQ process identifier set at least partially overlaps with the second HARQ process identifier set, and the first LCID set does not overlap with the second LCID set;

[0196] The first HARQ process identifier set and the first LCID set are used for MBS services, and the second HARQ process identifier set and the second LCID set are used for unicast services.

[0197] In some optional implementations, the determination unit 701 is used to determine the RLC entity corresponding to the first LCID from the RLC entities corresponding to the MBS service and the RLC entities corresponding to the unicast service as the RLC entity to which the first MAC SDU is to be delivered.

[0198] Those skilled in the art should understand that the relevant description of the above-mentioned device for improving MBS service reliability in the embodiment of the present application can be understood with reference to the relevant description of the method for improving MBS service reliability in the embodiment of the present application.

[0199] Figure 8 The structure of the device for improving the reliability of MBS services provided by the embodiment of the present application is shown in FIG. Figure 2 , applied to network equipment, such as Figure 8As shown, the device for improving MBS service reliability includes:

[0200] The determining unit 801 is used to determine the transmission mode of the MBS service: the new transmission is transmitted by the PTM mode, and the retransmission is transmitted by the PTP mode;

[0201] The scheduling unit 802 is configured to schedule the transmission of the MBS service based on the transmission mode of the MBS service.

[0202] In some optional implementations, the scheduling unit 802 is used to schedule new transmission of the first service data in a PTM manner; and / or schedule retransmission of the first service data in a PTP manner;

[0203] The first service data is service data of the MBS service.

[0204] In some optional implementations, the scheduling unit 802 is used to send first downlink scheduling information encrypted with the G-RNTI, where the first downlink scheduling information is used to schedule new transmission of first service data, and the first downlink scheduling information carries a first HARQ process identifier.

[0205] In some optional implementations, the scheduling unit 802 is used to send third downlink scheduling information encrypted with C-RNTI, the third downlink scheduling information is used to schedule retransmission of the first service data, and the third downlink scheduling information carries the first HARQ process identifier.

[0206] In some optional implementations, the NDI carried in the third downlink scheduling information is the same as the NDI carried in the first downlink scheduling information.

[0207] In some optional implementations, the scheduling unit 802 is used to schedule the retransmission of the first service data to each terminal device in the at least one terminal device through the PTP method; wherein the at least one terminal device is at least one terminal device in the MBS group.

[0208] In some optional implementations, the at least one terminal device includes:

[0209] at least one terminal device that feeds back HARQ NACK information for the first service data; and / or,

[0210] At least one terminal device that does not feed back HARQ feedback information for the first service data.

[0211] In some optional embodiments, the scheduling unit 802 is further used to schedule new transmission of second service data through PTM when HARQ ACK information for the first service data is received from all terminal devices in the MBS group, and the second service data is the next data to be transmitted of the first service data.

[0212] Those skilled in the art should understand that the relevant description of the above-mentioned device for improving MBS service reliability in the embodiment of the present application can be understood with reference to the relevant description of the method for improving MBS service reliability in the embodiment of the present application.

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

[0214] Alternatively, if Fig. 9 As shown, the communication device 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0215] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0216] Alternatively, if Fig. 9 As shown, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

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

[0218] Optionally, the communication device 900 may specifically be a network device of an embodiment of the present application, and the communication device 900 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.

[0219] Optionally, the communication device 900 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 900 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 again for the sake of brevity.

[0220] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.10 The chip 1000 shown includes a processor 1010, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0221] Alternatively, if Fig.10 As shown, the chip 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0222] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0223] Optionally, the chip 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0224] Optionally, the chip 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

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

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

[0228] Fig.11 1 is a schematic block diagram of a communication system 1100 provided in an embodiment of the present application. Fig.11 As shown, the communication system 1100 includes a terminal device 1110 and a network device 1120 .

[0229] Among them, the terminal device 1110 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0248] 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 improving MBS service reliability, the method comprising: The network equipment determines the transmission mode of the MBS service as follows: new transmission is transmitted via PTM mode, and retransmission is transmitted via PTP mode; The network device schedules transmission of the MBS service based on the transmission mode of the MBS service; The network device scheduling the transmission of the MBS service based on the transmission mode of the MBS service includes: The network device schedules new transmission of the first service data by means of PTM; and / or, The network device schedules retransmission of the first service data in a PTP manner; Wherein, the first service data is service data of the MBS service; The network device scheduling new transmission of the first service data in a PTM manner includes: The network device sends first downlink scheduling information scrambled by the G-RNTI, where the first downlink scheduling information is used to schedule new transmission of first service data, and the first downlink scheduling information carries a first HARQ process identifier.

2. The method according to claim 1, wherein: The network device schedules retransmission of the first service data in a PTP manner, including: The network device sends third downlink scheduling information encrypted with the C-RNTI, where the third downlink scheduling information is used to schedule retransmission of the first service data, and the third downlink scheduling information carries the first HARQ process identifier.

3. The method according to claim 2, wherein: The NDI carried in the third downlink scheduling information is the same as the NDI carried in the first downlink scheduling information.

4. The method according to any one of claims 1 to 3, wherein: The network device schedules retransmission of the first service data in a PTP manner, including: The network device schedules the retransmission of the first service data to each terminal device in the at least one terminal device through the PTP method; wherein the at least one terminal device is at least one terminal device in the MBS group.

5. The method according to claim 4, wherein: The at least one terminal device comprises: at least one terminal device that feeds back HARQ NACK information for the first service data; and / or, At least one terminal device that does not feed back HARQ feedback information for the first service data.

6. The method according to any one of claims 1 to 3, wherein: The method further comprises: When the network device receives HARQ ACK information for the first service data fed back by all terminal devices in the MBS group, it schedules new transmission of second service data through PTM, where the second service data is the next data to be transmitted of the first service data.

7. A device for improving MBS service reliability, applied to a network device, the device comprising: A determination unit, used to determine the transmission mode of the MBS service: new transmission is transmitted by PTM mode, and retransmission is transmitted by PTP mode; a scheduling unit, configured to schedule transmission of the MBS service based on a transmission mode of the MBS service; The scheduling unit is specifically used to schedule new transmission of the first service data by PTM mode; and / or schedule retransmission of the first service data by PTP mode; wherein the first service data is service data of the MBS service; The scheduling unit is further specifically used to send first downlink scheduling information encrypted with the G-RNTI, where the first downlink scheduling information is used to schedule new transmission of first service data, and the first downlink scheduling information carries a first HARQ process identifier.

8. The device according to claim 7, wherein: The scheduling unit is further used to send third downlink scheduling information encrypted with the C-RNTI, where the third downlink scheduling information is used to schedule retransmission of the first service data, and the third downlink scheduling information carries the first HARQ process identifier.

9. The device according to claim 8, wherein: The NDI carried in the third downlink scheduling information is the same as the NDI carried in the first downlink scheduling information.

10. The device according to any one of claims 7 to 9, wherein: The scheduling unit is used to schedule the retransmission of the first service data to each terminal device in the at least one terminal device through the PTP method; wherein the at least one terminal device is at least one terminal device in the MBS group.

11. The device according to claim 10, wherein: The at least one terminal device comprises: at least one terminal device that feeds back HARQ NACK information for the first service data; and / or, At least one terminal device that does not feed back HARQ feedback information for the first service data.

12. The device according to any one of claims 7 to 9, wherein: The scheduling unit is also used to schedule new transmission of second service data through PTM when HARQ ACK information for the first service data is received from all terminal devices in the MBS group, and the second service data is the next data to be transmitted of the first service data.

13. A network 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 according to any one of claims 1 to 6.

14. 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 6.

15. 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 6.

16. A computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method according to any one of claims 1 to 6.

Images