Report transmission method, terminal, base station, device, and storage medium

Abstract

The embodiment of the application provides a report sending method, a terminal, a base station, an apparatus, and a storage medium, the method comprising: determining the identity of a second MRB configured by a source base station for a QoS Flow of a target MBS service according to the identity of a first MRB configured by a target base station for the QoS Flow of the target MBS service; and sending a PDCP status report for the QoS Flow of the target MBS service to the target base station through a packet data convergence protocol (PDCP) entity corresponding to the identity of the second MRB. The embodiment of the application uses the PDCP entity established for the first MRB of the source base station before handover, avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when switching to the target base station, guarantees lossless transmission based on the PDCP status report, and guarantees the reliability of data transmission.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a report transmission method, terminal, base station, device, and storage medium. Background Technology

[0002] PDCP (Packet Data Convergence Protocol) is an air interface protocol layer. When transmitting data, radio access network nodes and terminals establish a PDCP entity for each radio bearer to process the transmitted data.

[0003] However, the identifiers of the Multicast Broadcast System Radio Bearers (MRBs) established by different RAN nodes for the same Multicast Broadcast System (MBS) session are different. This means that in a handover scenario, the MRB IDs assigned by the source RAN node and the target RAN node for the same MBS session are different. Therefore, when the terminal switches to the target RAN node, it needs to trigger the release and establishment of the PDCP entity. If transmission is still based on the source PDCP status report, MBS service data will be lost. Summary of the Invention

[0004] This application provides a report sending method, terminal, base station, device, and storage medium to address the shortcomings of existing technologies where MBS service data is easily lost, thereby ensuring lossless transmission based on PDCP status reports and guaranteeing the reliability of data transmission.

[0005] In a first aspect, embodiments of this application provide a report sending method applied to a terminal device, the method comprising:

[0006] Based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0007] The Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB sends a PDCP status report for the QoS Flow of the target MBS service to the target base station.

[0008] Optionally, according to a report sending method of one embodiment of this application, the step of sending a PDCP status report of the QoS Flow for the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB includes:

[0009] The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB.

[0010] The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

[0011] Optionally, according to one embodiment of the report sending method of this application, the method further includes:

[0012] The mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station is received from the source base station;

[0013] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0014] Based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0015] Optionally, according to one embodiment of the report sending method of this application, the method further includes:

[0016] The system receives a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station.

[0017] Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined;

[0018] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0019] Based on the determined mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0020] Secondly, embodiments of this application also provide a report transmission method applied to a source base station, the method comprising:

[0021] Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0022] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0023] Optionally, according to a report transmission method of one embodiment of this application, the step of indicating to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service includes:

[0024] The target base station sends a mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0025] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is sent to the terminal.

[0026] Optionally, according to a report transmission method of one embodiment of this application, the step of indicating to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service includes:

[0027] Receive the second mapping relationship sent by the target base station;

[0028] Send the second mapping relationship and the first mapping relationship to the terminal;

[0029] The first mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB. The second mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB. The second mapping relationship and the first mapping relationship are used to indicate to the terminal the mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0030] Thirdly, embodiments of this application also provide a terminal device, including a memory, a transceiver, and a processor, wherein:

[0031] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0032] Based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0033] The Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB sends a PDCP status report for the QoS Flow of the target MBS service to the target base station.

[0034] Optionally, according to one embodiment of the terminal device of this application, the step of sending a PDCP status report of the QoS Flow for the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB includes:

[0035] The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB.

[0036] The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

[0037] Optionally, according to one embodiment of the terminal device of this application, the operation further includes:

[0038] The mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station is received from the source base station;

[0039] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0040] Based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0041] Optionally, according to one embodiment of the terminal device of this application, the operation further includes:

[0042] The system receives a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station.

[0043] Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined;

[0044] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0045] Based on the determined mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0046] Fourthly, embodiments of this application also provide a source base station, including a memory, a transceiver, and a processor, wherein:

[0047] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0048] Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0049] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0050] Optionally, according to one embodiment of the base station of this application, the step of indicating to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service includes:

[0051] The target base station sends a mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0052] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is sent to the terminal.

[0053] Optionally, according to one embodiment of the base station of this application, the step of indicating to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service includes:

[0054] Receive the second mapping relationship sent by the target base station;

[0055] Send the second mapping relationship and the first mapping relationship to the terminal;

[0056] The first mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB. The second mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB. The second mapping relationship and the first mapping relationship are used to indicate to the terminal the mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0057] Fifthly, embodiments of this application also provide a report sending device, the device comprising:

[0058] The determining module is used to determine the identifier of the second MRB configured by the source base station for the QoSFlow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoSFlow of the target MBS service.

[0059] The sending module is used to send a PDCP status report of the QoS Flow for the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB.

[0060] Sixthly, embodiments of this application also provide a report sending device, the device comprising:

[0061] The instruction module is used to indicate to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0062] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0063] In a seventh aspect, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to perform the steps of the report sending method described in the first aspect above, or to perform the steps of the report sending method described in the second aspect above.

[0064] The report sending method, terminal, base station, apparatus, and storage medium provided in this application determine the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the MBS service at the target base station. Then, using the PDCP entity corresponding to the identifier of the second MRB (i.e., the PDCP entity established for the first MRB of the source base station before handover), a PDCP status report for the QoS Flow of the target MBS service is sent to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handover to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission. Attached Figure Description

[0065] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0066] Figure 1 This is one of the flowcharts illustrating the report sending method provided in the embodiments of this application;

[0067] Figure 2 This is a second schematic flowchart of the report sending method provided in the embodiments of this application;

[0068] Figure 3 This is the third flowchart illustrating the report sending method provided in this application embodiment;

[0069] Figure 4 This is the fourth flowchart illustrating the report sending method provided in the embodiments of this application;

[0070] Figure 5 This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application;

[0071] Figure 6 This is a schematic diagram of the source base station structure provided in an embodiment of this application;

[0072] Figure 7 This is one of the structural schematic diagrams of the report sending device provided in the embodiments of this application;

[0073] Figure 8 This is a second schematic diagram of the structure of the report sending device provided in the embodiments of this application; Detailed Implementation

[0074] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0075] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0076] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0077] This application provides a report sending method and apparatus to ensure lossless transmission based on PDCP status reports and to guarantee the reliability of data transmission.

[0078] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0079] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0080] First, let's introduce the following:

[0081] (1) Identification of Multicast and Multicast Broadcast System Radio Bearer (MRB);

[0082] In wireless communication systems, there are scenarios where multiple user equipment (UEs) request the same downlink service data. To minimize radio resource consumption in such scenarios, the industry has proposed multicast and broadcast mechanisms, allowing the network to use specific radio resources to send a single set of downlink data, which multiple UEs can simultaneously receive. In contrast, the traditional downlink data mechanism, which can only be received by one UE, is called unicast. The portion of a wireless communication system that supports multicast and broadcast is called a Multicast Broadcast System (MBS).

[0083] In communication systems, different data have different Quality of Service (QoS) requirements. A UE may simultaneously receive data packets with different QoS requirements. Data packets with the same QoS requirements constitute a QoS Flow, identified by a QFI (QoS Flow ID). In air interface transmission, to differentiate scheduling, the Radio Access Network (RAN) can configure multiple radio bearers to carry these QoS flows. Each radio bearer has its own configuration information and is uniquely identified by its radio bearer identifier. The RAN node informs the UE of these radio bearer identifiers and corresponding configuration information via air interface signaling.

[0084] When a UE switches between two RAN nodes, the configuration of the radio bearer needs to be adapted due to the change in the channel environment. In this case, the target RAN node can use the radio bearer identifier to inform the UE which radio bearer configuration needs to be changed and what changes are required. Multicast mechanisms are no exception; their service data is transmitted through the Multicast Broadcast System Radio Bearer (MRB), and the RAN node will also inform the UE of the MRB identifier and corresponding configuration information via air interface signaling. The MRB identifier is called the MRB ID.

[0085] In multicast mechanisms, for management, maintenance, and data security reasons, when multiple UEs connect to the same RAN node and receive the same multicast service data stream, the RAN node must instruct all UEs to establish an MRB with identical identifier and configuration for this same service data stream. In other words, the MRB ID is global within the RAN node and valid for all UEs receiving the MBS service. However, according to current technology, the MRB ID is assigned autonomously by each RAN node; therefore, different RAN nodes may assign different MRB IDs for the same service data stream.

[0086] (2) PDCP status report after handover;

[0087] The Packet Data Convergence Protocol (PDCP) is an air interface protocol layer. During data transmission, the Radio Access Network (RAN) node and the UE establish a PDCP entity for each radio bearer to handle the transmitted data. After a handover, the UE must release the old DRB and establish a new one, which in turn causes the UE to release the old PDCP entity and establish a new one. At this time, PDCP status reports become unavailable, thus preventing lossless transmission of user data from being guaranteed using this method.

[0088] DRB is used only for a single UE. The target base station can simply assign the same DRB ID to the UE so that lossless transmission based on PDCP status reports can be achieved during handover.

[0089] MBS service transmission uses MRB. Unlike DRB, which is only used for a single UE, MBS service carried by MRB can be received by multiple UEs. Therefore, before a UE switches over, the corresponding MBS service may have been transmitted at the target base station for a period of time, and the MRB ID it uses may be different from the MRB ID used on the source base station. When this UE switches over to the target base station, it can only use the existing MRB (which has a different MRB ID from the source base station) to receive MBS service.

[0090] To overcome the defect that when different RAN nodes establish different MRB identifiers for the same QoS flow in an MBS session, the base station and UE will trigger the release and establishment of PDCP entities when switching to the target cell. This causes the lossless transmission mechanism based on PDCP status reports in existing unicast scenarios to fail, resulting in data loss. This application proposes a report sending method, apparatus, terminal device, base station, and storage medium, which can effectively ensure lossless transmission based on PDCP status reports and improve the reliability of data transmission.

[0091] Figure 1 This is one of the flowcharts illustrating the report sending method provided in the embodiments of this application, such as... Figure 1 As shown in the figure, this application provides a report sending method, the execution subject of which can be a terminal device, such as a mobile phone. The method includes:

[0092] Step 101: Based on the identifier of the first multicast broadcast system radio bearer (MRB) configured by the target base station for the QoS Flow of the target multicast broadcast system (MBS) service, determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service.

[0093] Specifically, in this embodiment, to overcome the defect that the terminal device must release the old DRB and establish a new DRB, which leads to data loss due to the terminal device needing to establish a new PDCP entity, after the terminal device determines the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, which is different from the identifier of the second MRB of the QoS Flow of the target MBS service at the source base station. After determining the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the terminal device can find the identifier of the second MRB corresponding to the identifier of the first MRB. The second MRB is the MRB configured by the source base station for the QoS Flow of the target MBS service. Therefore, the terminal device can continue to use the PDCP entity of the QoS Flow of the target MBS service for the second MRB on the source base station, that is, the PDCP entity corresponding to the identifier of the second MRB.

[0094] Step 102: Send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB.

[0095] Specifically, in the embodiments of this application, the terminal can determine the PDCP entity corresponding to the QoSFlow of the target MBS service that continues to use the source base station, ensuring that the lossless transmission mechanism based on PDCP status reports works normally and ensuring the reliability of data transmission.

[0096] Specifically, in this embodiment, the terminal can, based on the mapping relationship between the MRB ID (identifier of the second MRB) corresponding to the same MBS QoS Flow (QoS Flow of the target MBS service) in the source cell and the MRB ID (identifier of the first MRB) corresponding to the target cell, continue to use the PDCP entity configured by the source base station for the QoS Flow of the target MBS service for the first MRB corresponding to the target cell on the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the MRB involved when switching to the target cell, thereby enabling lossless transmission of multicast services.

[0097] Specifically, in this embodiment, for the QoS Flow of the target MBS service, the identifiers of the radio bearers used to carry the QoS Flow of the target MBS service before and after the terminal device handover are related. Therefore, during handover, the target base station can instruct the UE to continue using the PDCP entity before the handover, without releasing the old PDCP entity and establishing a new one. Furthermore, after the UE completes the handover, the PDCP entity on the UE side can report a PDCP status report to the target base station, informing the PDCP entity on the target base station side which downlink PDCP data packets were successfully received before the handover and which downlink PDCP data packets were not yet successfully received. The PDCP entity on the target base station side can then perform targeted PDCP retransmissions based on this status report, thereby ensuring lossless transmission of user data.

[0098] The report sending method provided in this application determines the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the QoS Flow of the target base station for the MBS service. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e. the PDCP entity established for the second MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0099] Optionally, in one embodiment, the step of sending a PDCP status report for the QoS Flow of the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB includes:

[0100] The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB.

[0101] The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

[0102] Specifically, before handover, while still connected to the source base station, the UE can receive the QoS Flow of the target MBS service through the PDCP entity corresponding to the identifier of the second MRB configured by the source base station. After handover, the UE can continue to use the PDCP entity from before handover to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. That is, the PDCP entity on the UE side can report a PDCP status report to the target base station, informing the target base station's PDCP entity which downlink PDCP data packets were successfully received before handover and which downlink PDCP data packets were not yet successfully received. The PDCP entity on the target base station side can perform targeted PDCP retransmissions based on this status report, thereby ensuring lossless transmission of user data. Optionally, in one embodiment, the method further includes:

[0103] The mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station is received from the source base station;

[0104] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0105] Based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0106] Optionally, when a handover occurs, the target base station configuration can indicate the correspondence between the MRB ID (identifier of the second MRB) of the same MBS QoSFlow (QoS Flow of the target MBS service) in the source cell and the corresponding MRB ID (identifier of the first MRB) in the target cell.

[0107] Specifically, before transmission, the terminal can receive in advance the mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station, which is forwarded by the source base station. Based on the mapping relationship, the terminal can determine the identifier of the second MRB corresponding to the identifier of the first MRB, and then determine the PDCP entity to be used.

[0108] Specifically, upon receiving the mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station, the terminal device can determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service.

[0109] Optionally, in one embodiment, the method further includes:

[0110] The system receives a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station.

[0111] Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined;

[0112] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0113] Based on the determined mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0114] Optionally, when a handover occurs, the UE can determine the correspondence between the MRB ID (identifier of the second MRB) of the same MBS QoS Flow (QoS Flow of the target MBS service) in the source cell and the corresponding MRB ID (identifier of the first MRB) in the target cell based on the received first mapping relationship (mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB) and the second mapping relationship (mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB).

[0115] Specifically, before transmission, the terminal can receive a first mapping relationship sent by the source base station, then access the source base station and receive MBS service data through the corresponding MRB on the source cell; after the terminal switches to the target base station, the source base station can receive a second mapping relationship sent by the target base station, and the terminal can receive the second mapping relationship forwarded by the source base station from the target base station; and determine the mapping relationship between the identifier of the first MRB and the identifier of the second MRB according to the first mapping relationship and the second mapping relationship, and determine the identifier of the second MRB corresponding to the identifier of the first MRB based on the mapping relationship, thereby determining the PDCP entity that can continue to be used.

[0116] Specifically, upon receiving the mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station, the terminal device can determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service. The report sending method provided in this application, by determining the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured by the target base station for the MBS service, and then using the PDCP entity corresponding to the identifier of the second MRB (i.e., the PDCP entity established for the first MRB of the source base station before handover), sends a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB during handover to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0117] Figure 2 This is a second flowchart illustrating the report sending method provided in this application embodiment, as shown below. Figure 2 As shown in the figure, this application embodiment provides a report sending method applied to a source base station, the method including:

[0118] Step 201: Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0119] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0120] Specifically, in this embodiment, to overcome the defect that the terminal device must release the old DRB and establish a new DRB due to the difference between the identifier of the first MRB established by the terminal for the QoS Flow of the target MBS service after switching to the target base station and the identifier of the second MRB of the QoS Flow of the target MBS service at the source base station, which in turn leads to the need for the terminal device to establish a new PDCP entity and cause data loss, the source base station can indicate the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This allows the terminal to find the identifier of the second MRB corresponding to the identifier of the first MRB after determining the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service. The second MRB is the MRB configured by the source base station for the QoS Flow of the target MBS service. Thus, the terminal device can continue to use the PDCP entity of the QoS Flow of the target MBS service for the second MRB on the source base station, that is, the PDCP entity corresponding to the identifier of the second MRB. In this embodiment, the terminal determines to continue to use the PDCP entity corresponding to the QoS Flow of the target MBS service by the source base station, ensuring the normal operation of the lossless transmission mechanism based on PDCP status reports and ensuring the reliability of data transmission.

[0121] Optionally, the source base station can send the above mapping relationship to the terminal so that the terminal can, based on the correspondence between the MRB ID (identifier of the second MRB) corresponding to the same MBS QoS Flow (QoS Flow of the target MBS service) in the source cell and the MRB ID (identifier of the first MRB) corresponding to the same MBS QoS Flow (QoS Flow of the target MBS service) in the target cell (target mapping relationship), continue to use the PDCP entity configured by the source base station for the QoS Flow of the target MBS service for the MRB corresponding to the target cell. This avoids triggering the release and establishment process of the PDCP entity corresponding to the MRB involved when switching to the target cell, thereby enabling lossless transmission of multicast services.

[0122] Specifically, in this embodiment, for the QoS Flow of the target MBS service, the identifiers of the radio bearers used to carry the QoS Flow of the target MBS service before and after the terminal device handover are related. Therefore, during handover, the target base station can instruct the UE to continue using the PDCP entity before the handover, without releasing the old PDCP entity and establishing a new one. Furthermore, after the UE completes the handover, the PDCP entity on the UE side can report a PDCP status report to the target base station, informing the PDCP entity on the target base station side which downlink PDCP data packets were successfully received before the handover and which downlink PDCP data packets were not yet successfully received. The PDCP entity on the target base station side can then perform targeted PDCP retransmissions based on this status report, thereby ensuring lossless transmission of user data.

[0123] The report sending method provided in this application embodiment indicates the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This enables the terminal to determine the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured for the MBS service by the target base station. Then, the terminal uses the PDCP entity corresponding to the identifier of the second MRB, i.e., the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0124] Optionally, in one embodiment, the step of indicating to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service includes:

[0125] The target base station sends a mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0126] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is sent to the terminal.

[0127] Specifically, the source base station can first receive the mapping relationship between the identifier of the first MRB and the identifier of the second MRB sent by the target base station through the Xn interface; after receiving the mapping relationship between the identifier of the first MRB and the identifier of the second MRB, the source base station can forward it to the terminal device.

[0128] Optionally, in one embodiment, the step of indicating to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service includes:

[0129] Receive the second mapping relationship sent by the target base station;

[0130] Send the second mapping relationship and the first mapping relationship to the terminal;

[0131] The first mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB. The second mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB. The second mapping relationship and the first mapping relationship are used to indicate to the terminal the mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0132] Optionally, the source base station can send the first mapping relationship and the second mapping relationship to the terminal, so that the terminal can determine the mapping relationship between the identifier of the first MRB and the identifier of the second MRB. Then, based on the mapping relationship between the MRB ID (identifier of the second MRB) corresponding to the same MBS QoS Flow (QoS Flow of the target MBS service) in the source cell and the MRB ID (identifier of the first MRB) corresponding to the target cell, the target base station continues to use the PDCP entity configured by the source base station for the QoS Flow of the target MBS service for the MRB corresponding to the target cell. This avoids triggering the release and establishment process of the PDCP entity corresponding to the MRB involved when switching to the target cell, thereby enabling lossless transmission of multicast services.

[0133] Specifically, the source base station first receives the second mapping relationship sent by the target base station through the Xn interface; after receiving the second mapping relationship, the source base station can forward it to the terminal device.

[0134] Specifically, the source base station can establish an MRB (identifier of the second MRB) for the QoS Flow of the target MBS service in the MBS session. Then, the source base station can use the MRB to send MBS service data through the air interface. Subsequently, the source base station can send the first mapping relationship to the terminal, and the terminal can access the source base station and receive MBS service data through the corresponding MRB on the source cell. After the terminal switches to the target base station, the source base station can receive the second mapping relationship sent by the target base station and forward it to the terminal. The terminal can then receive the second mapping relationship forwarded by the source base station from the target base station.

[0135] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined according to the first mapping relationship and the second mapping relationship. Based on the mapping relationship, the identifier of the second MRB corresponding to the identifier of the first MRB is determined, and then the PDCP entity that can continue to be used is determined.

[0136] The report sending method provided in this application embodiment indicates the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This enables the terminal to determine the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured for the MBS service by the target base station. Then, the terminal uses the PDCP entity corresponding to the identifier of the second MRB, i.e., the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0137] Optionally, Figure 3 This is the third flowchart illustrating the report sending method provided in this application embodiment, as shown below. Figure 3 As shown, this application embodiment provides a report sending method that can indicate the target mapping relationship between the identifier of the second MRB corresponding to the QoSFlow of the target MBS service on the source cell and the identifier of the first MRB corresponding to the target cell in the configuration of the target base station. The method includes:

[0138] Step 1: The core network instructs base station 1 (source base station) to establish an MBS session;

[0139] Step 2: Base station 1 establishes an MRB for the QoS Flow of a target MBS service in the MBS session, which can be identified by MRB ID 1 (the identifier of the second MRB). Then, base station 1 starts to use the MRB to send MBS service data through the air interface.

[0140] Step 3: Base station 1 configures the QoS Flow identifier of the target MBS service and the mapping relationship between MRB to the UE.

[0141] Step 4: The UE accesses base station 1 and receives MBS service data through the aforementioned MRB.

[0142] Step 5: At a certain moment, due to reasons such as UE movement, base station 1 decides to hand over the UE to base station 2, and therefore initiates a handover preparation process to base station 2. The target base station (base station 2) allocates an MRB and designates MRB ID 2 (the identifier of the first MRB) for the QoS Flow of the same target MBS service for the same service. The target base station (base station 2) sends the target mapping relationship between MRB ID 2 and MRB ID 1 corresponding to the QoS Flow of the target MBS service to the source base station (base station 1) through the Xn interface.

[0143] Step 6: Base station 1 transmits the target mapping relationship to the UE.

[0144] Step 7: As instructed by the network, the UE switches from base station 1 to base station 2. It is determined that the QoSFlow of the same target MBS service is mapped to MRB ID 2 on the target base station. Therefore, the PDCP entity for the aforementioned MRB ID 1 is used to receive data on the target base station.

[0145] Step 8: The UE performs a lossless handover transmission process based on the PDCP status report, and reports the PDCP data reception status on MRB ID 1 of the source base station as the status of MRB ID 2 to the target base station through the PDCP status report.

[0146] Optionally, Figure 4 This is the fourth flowchart illustrating the report sending method provided in this application embodiment, as shown below. Figure 4 As shown, this application embodiment provides a report transmission method, which allows a UE to determine the target mapping relationship between the identifier of the second MRB corresponding to the QoS Flow of the target MBS service on the source cell and the identifier of the first MRB corresponding to the target cell, based on a received first mapping relationship and a second mapping relationship. The method includes:

[0147] Step 1: The core network instructs base station 1 (source base station) to establish an MBS session;

[0148] Step 2: Base station 1 establishes an MRB for the QoS Flow of a target MBS service in the MBS session, which can be identified by MRB ID 1 (the identifier of the second MRB). Then, base station 1 starts to use the MRB to send MBS service data through the air interface.

[0149] Step 3: Base station 1 configures the QoS Flow identifier of the target MBS service and the first mapping relationship between MRB and the UE.

[0150] Step 4: The UE accesses base station 1 and receives MBS service data through the aforementioned MRB.

[0151] Step 5: At a certain moment, due to reasons such as UE movement, base station 1 decides to hand over the UE to base station 2, and thus initiates a handover preparation process to base station 2. The target base station (base station 2) allocates an MRB and designates MRB ID 2 (the identifier of the first MRB) for the QoS Flow of the same target MBS service of the same service. The target base station (base station 2) sends the second mapping relationship between the QoS Flow of the target MBS service and MRB ID 2 to the source base station (base station 1) through the Xn interface.

[0152] Step 6: As a relay, base station 1 sends the second mapping relationship between the MBS session on base station 2, the QoS Flow of the target MBS service, and MRB ID2 to the UE via an RRC message.

[0153] Step 7: The UE obtains the mapping relationship between MRB ID1 and MRB ID2 based on the configuration of base station 1 and base station 2.

[0154] Step 8: As instructed by the network, the UE switches from base station 1 to base station 2. It is determined that the QoSFlow of the same target MBS service is mapped to MRB ID 2 on the target base station. Therefore, the PDCP entity for the aforementioned MRB ID 1 is used to receive data on the target base station.

[0155] Step 9: The UE performs a lossless handover transmission process based on the PDCP status report, and reports the PDCP data reception status on MRB ID 1 of the source base station as the status of MRB ID 2 to the target base station through the PDCP status report.

[0156] The report sending method provided in this application determines the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the MBS service at the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e. the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0157] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0158] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0159] Figure 5 This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application, such as... Figure 5 As shown, the terminal device includes a memory, a transceiver, and a processor.

[0160] Transceiver 500 is used to receive and send data under the control of processor 510.

[0161] Among them, Figure 5In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 510 and memory represented by memory 520 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 500 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 530 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0162] Processor 510 is responsible for managing the bus architecture and general processing, while memory 520 can store data used by processor 500 when performing operations.

[0163] Optionally, the processor 510 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0164] The processor executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling a computer program stored in memory. The processor and memory may also be physically separated.

[0165] Specifically, the processor 510 is used to read the computer program in the memory and perform the following operations:

[0166] Based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0167] The Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB sends a PDCP status report for the QoS Flow of the target MBS service to the target base station.

[0168] The terminal device provided in this application determines the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the MBS service at the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e. the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0169] Optionally, the processor 510 is also used for:

[0170] The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB.

[0171] The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

[0172] Optionally, the processor 510 is also used for:

[0173] The mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station is received from the source base station;

[0174] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0175] Based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0176] Optionally, the processor 510 is also used for:

[0177] The system receives a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station.

[0178] Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined;

[0179] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0180] Based on the determined mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0181] The terminal device provided in this application determines the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the MBS service at the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e. the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0182] Figure 6 This is a schematic diagram of the source base station structure provided in the embodiments of this application, such as... Figure 6 As shown, the terminal device includes a memory, a transceiver, and a processor.

[0183] Transceiver 600 is used to receive and send data under the control of processor 610.

[0184] Among them, Figure 6In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 610) and memory (memory 620). The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 600 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 610 during operation.

[0185] The processor 610 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0186] Specifically, the processor 610 is used to read the computer program in the memory and perform the following operations:

[0187] Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0188] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0189] The source base station provided in this application indicates the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This enables the terminal to determine the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured by the target base station for the MBS service. Then, the terminal uses the PDCP entity corresponding to the identifier of the second MRB, i.e., the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0190] Specifically, the processor 610 is also used for:

[0191] The target base station sends a mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0192] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is sent to the terminal.

[0193] Specifically, the processor 610 is also used for:

[0194] Receive the second mapping relationship sent by the target base station;

[0195] Send the second mapping relationship and the first mapping relationship to the terminal;

[0196] The first mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB. The second mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB. The second mapping relationship and the first mapping relationship are used to indicate to the terminal the mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0197] The source base station provided in this application indicates the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This enables the terminal to determine the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured by the target base station for the MBS service. Then, the terminal uses the PDCP entity corresponding to the identifier of the second MRB, i.e., the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0198] It should be noted that the terminal device or source base station provided in the embodiments of the present invention can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0199] Figure 7 This is one of the structural schematic diagrams of the report sending device provided in the embodiments of this application, such as... Figure 7 As shown, the report sending device includes: a determining module 710 and a sending module 720;

[0200] The determining module 710 is used to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service.

[0201] The sending module 720 is used to send a PDCP status report of the QoS Flow for the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB.

[0202] The report sending apparatus provided in this application determines the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the MBS service at the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e. the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0203] Optionally, the sending module 720 is further configured to:

[0204] The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB.

[0205] The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

[0206] Optionally, the device further includes:

[0207] The first receiving module is used to receive the mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station, which is sent by the source base station.

[0208] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0209] Based on the mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0210] Optionally, the device further includes:

[0211] The second receiving module is configured to receive a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station.

[0212] Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined;

[0213] Based on the identifier of the first Multicast Broadcast System Radio Bearer (MRB) configured by the target base station for the Quality of Service (QoS) data flow of the target Multicast Broadcast System (MBS) service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined, including:

[0214] Based on the determined mapping relationship and the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0215] The report sending apparatus provided in this application determines the identifier of the second MRB configured for the same QoS Flow at the source base station based on the identifier of the first MRB configured for the MBS service at the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e. the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0216] The report sending device provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0217] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0218] Figure 8 This is a second schematic diagram of the structure of the report sending device provided in the embodiments of this application, as shown below. Figure 8 As shown, the report sending device includes: an indication module 810; wherein:

[0219] The instruction module 810 is used to indicate to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0220] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0221] The report sending apparatus provided in this application embodiment indicates the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This enables the terminal to determine the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured for the MBS service by the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e., the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0222] Optionally, the indicating module 810 is further configured to:

[0223] The target base station sends a mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0224] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is sent to the terminal.

[0225] Optionally, the indicating module 810 is further configured to:

[0226] Receive the second mapping relationship sent by the target base station;

[0227] Send the second mapping relationship and the first mapping relationship to the terminal;

[0228] The first mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB. The second mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB. The second mapping relationship and the first mapping relationship are used to indicate to the terminal the mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

[0229] The report sending apparatus provided in this application embodiment indicates the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal. This enables the terminal to determine the identifier of the second MRB configured by the source base station for the same QoS Flow based on the identifier of the first MRB configured for the MBS service by the target base station. Then, it uses the PDCP entity corresponding to the identifier of the second MRB, i.e., the PDCP entity established for the first MRB of the source base station before the handover, to send a PDCP status report for the QoS Flow of the target MBS service to the target base station. This avoids triggering the release and establishment process of the PDCP entity corresponding to the second MRB when handing over to the target base station, ensuring lossless transmission based on the PDCP status report and guaranteeing the reliability of data transmission.

[0230] The report sending device provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0231] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0232] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0233] It should be noted that the apparatus provided in this embodiment of the invention can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0234] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the methods provided in the above embodiments, including:

[0235] Based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service is determined.

[0236] The Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB sends a PDCP status report for the QoS Flow of the target MBS service to the target base station.

[0237] or,

[0238] Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service;

[0239] The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

[0240] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0241] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0242] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0243] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0244] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0245] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A report sending method, characterized in that, Applied to a terminal device, the method includes: The identifier of the second MRB is determined based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and the mapping relationship between the first MRB identifier and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service. The Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB sends a PDCP status report for the QoS Flow of the target MBS service to the target base station.

2. The report sending method according to claim 1, characterized in that, The step of sending a PDCP status report for the QoS Flow of the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB includes: The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB. The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

3. The report sending method according to claim 1 or 2, characterized in that, The method further includes: The mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station, which is received from the source base station.

4. The report sending method according to claim 1 or 2, characterized in that, The method further includes: The system receives a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station. Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined.

5. A report sending method, characterized in that, Applied to a source base station, the method includes: Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service; The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

6. The report sending method according to claim 5, characterized in that, The mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service, which indicates to the terminal device, includes: The target base station sends a mapping relationship between the identifier of the first MRB and the identifier of the second MRB. Send the mapping relationship between the identifier of the first MRB and the identifier of the second MRB to the terminal.

7. The report sending method according to claim 5, characterized in that, The mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service, which indicates to the terminal device, includes: Receive the second mapping relationship sent by the target base station; Send the second mapping relationship and the first mapping relationship to the terminal; The first mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB. The second mapping relationship includes the mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB. The second mapping relationship and the first mapping relationship are used to indicate to the terminal the mapping relationship between the identifier of the first MRB and the identifier of the second MRB.

8. A terminal device, comprising a memory, a transceiver, and a processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The identifier of the second MRB is determined based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and the mapping relationship between the first MRB identifier and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service. The Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB sends a PDCP status report for the QoS Flow of the target MBS service to the target base station.

9. The terminal device according to claim 8, characterized in that, The step of sending a PDCP status report for the QoS Flow of the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB includes: The QoS Flow of the target MBS service is received through the PDCP entity corresponding to the identifier of the second MRB. The PDCP status report generated by the PDCP entity corresponding to the identifier of the second MRB is sent to the target base station. The PDCP status report contains the QoS Flow transmission information of the target MBS service.

10. The terminal device according to claim 8 or 9, characterized in that, The operation also includes: The mapping relationship between the identifier of the first MRB configured by the target base station and the identifier of the second MRB configured by the source base station, which is received from the source base station.

11. The terminal device according to claim 8 or 9, characterized in that, The operation also includes: The system receives a first mapping relationship and a second mapping relationship sent by the source base station. The first mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station. The second mapping relationship includes a mapping relationship between the QoS Flow of the target MBS service and the identifier of the first MRB configured by the target base station. The second mapping relationship is sent by the target base station to the source base station. Based on the first mapping relationship and the second mapping relationship, the mapping relationship between the identifier of the first MRB and the identifier of the second MRB is determined.

12. A base station, comprising a memory, a transceiver, and a processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Instruct the terminal device on the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service; in, The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

13. A report sending device, characterized in that, The device includes: The determining module is used to determine the identifier of the second MRB based on the identifier of the first multicast broadcast system radio bearer (MRB) configured by the target base station for the QoSFlow of the target multicast broadcast system (MBS) service, and the mapping relationship between the first MRB identifier and the identifier of the second MRB configured by the source base station for the QoSFlow of the target MBS service. The sending module is used to send a PDCP status report of the QoS Flow for the target MBS service to the target base station through the Packet Data Convergence Protocol (PDCP) entity corresponding to the identifier of the second MRB.

14. A report sending device, characterized in that, The device includes: The instruction module is used to indicate to the terminal device the mapping relationship between the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service and the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service; The mapping relationship between the identifier of the first MRB and the identifier of the second MRB is used to instruct the terminal device to determine the identifier of the second MRB configured by the source base station for the QoS Flow of the target MBS service based on the identifier of the first MRB configured by the target base station for the QoS Flow of the target MBS service, and to send a PDCP status report for the QoS Flow of the target MBS service to the target base station through the PDCP entity corresponding to the identifier of the second MRB.

15. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to perform the method according to any one of claims 1 to 7.

Images