Service Data Processing Method, Apparatus, and Device

Abstract

The present application discloses a service data processing method, an apparatus and a device, which belong to the technical field of communication. The service data processing method of the embodiment of the present application includes the steps of: a source node forwarding service data of a target multicast service to a target node through a data forwarding tunnel of a dedicated bearer of a terminal according to the MBS capability of the target node, where the terminal receives the target multicast service from the source node through a source multicast bearer.

Description

Technical Field

[0001] (Cross - reference to related applications) This application claims the priority of Chinese Patent Application No. 202110341235.7, filed in China on March 30, 2021, and all of its contents are incorporated herein by reference.

[0002] This application belongs to the technical field of communications, and specifically relates to a service data processing method, apparatus, and device.

Background Art

[0003] During the movement of a terminal, there may be a case where the terminal moves from a node that supports the Multi - cast Broadcast Service (MBS) to a node that does not support MBS. In this scenario, with the conventional mechanism, the multicast transmission tunnel resources related to MBS cannot be switched to a node that does not support MBS.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Embodiments of this application provide a service data processing method, apparatus, and device that can solve the problem that when a terminal moves from a base station that supports MBS to a node that does not support MBS, the multicast transmission tunnel resources related to MBS cannot be switched to a node that does not support MBS.

Means for Solving the Problems

[0005] In a first aspect, it includes the step of the source node transferring service data of a target multicast service to the target node through a data transfer tunnel of a dedicated bearer of the terminal according to the MBS capability of the target node. The terminal receives the target multicast service from the source node through a source multicast bearer, and provides a service data processing method.

[0006] In a second aspect, a step of resetting a dedicated bearer based on a reset message received by the terminal from the source node; a step of the terminal receiving service data of a target multicast service from a target node through the dedicated bearer, and includes: The terminal receives the target multicast service from the source node through a source multicast bearer, and provides a service data processing method.

[0007] In a third aspect, the source node is provided with a first transfer module for transferring service data of a target multicast service to the target node through a data transfer tunnel of a dedicated bearer of the terminal according to the MBS capability of the target node; The terminal receives the target multicast service from the source node through a source multicast bearer, and provides a service data processing apparatus.

[0008] In a fourth aspect, a second setting module for resetting a dedicated bearer based on a reset message received by the terminal from the source node; a first receiving module for the terminal to receive service data of a target multicast service from a target node through the dedicated bearer, and includes: The terminal provides a service data processing apparatus, characterized in that the terminal receives the target multicast service from the source node through a source multicast bearer.

[0009] In a fifth aspect, A source node is provided, which includes a processor, a memory, and a program or command stored in the memory and executable on the processor. When the program or command is executed by the processor, the steps of the method according to the first aspect are realized.

[0010] In the sixth aspect, A source node is provided, which includes a processor and a communication interface. The communication interface is for the source node to transfer service data of a target multicast service to a target node through a dedicated bearer data transfer tunnel of a terminal according to the MBS capability of the target node. The terminal receives the target multicast service from the source node through a source multicast bearer.

[0011] In the seventh aspect, A terminal is provided, which includes a processor, a memory, and a program or command stored in the memory and executable on the processor. When the program or command is executed by the processor, the steps of the method according to the second aspect are realized.

[0012] In the eighth aspect, A terminal is provided, which includes a processor and a communication interface. The processor is for the terminal to reconfigure a dedicated bearer based on a reset message received from a source node, and the communication interface is for the terminal to receive service data of a target multicast service from a target node through the dedicated bearer. The terminal receives the target multicast service from the source node through a source multicast bearer.

[0013] In the ninth aspect, a readable storage medium is provided, which stores a program or command that, when executed by a processor, realizes the steps of the method according to the first aspect or the steps of the method according to the second aspect.

[0014] In a tenth aspect, there is provided a chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or command to implement the steps of the method according to the first aspect or the steps of the method according to the second aspect.

[0015] In an eleventh aspect, there is provided a computer program / program product stored in a non - volatile storage medium and executed by at least one processor to implement the steps of the method according to the first aspect or the steps of the method according to the second aspect.

[0016] In a twelfth aspect, there is provided a communication device configured to execute the steps of the method according to the first aspect or the second aspect.

Advantages of the Invention

[0017] In an embodiment of the present application, the source node transmits service data of the target multicast service to the terminal via a dedicated bearer according to the MBS capability of the target node, thereby solving the problem that the interruption time of the multicast service data is too long when the terminal moves from a node supporting MBS to a node not supporting MBS.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying out the Invention

[0019] In the following, while referring to the drawings in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described. Naturally, the described embodiments are part of the embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art also belong to the protection scope of the present application.

[0020] The terms "first", "second", etc. in the specification and claims of the present application are not for explaining a specific order or sequence, but for distinguishing similar objects. It should be understood that such terms may be replaced with each other in appropriate cases so that the embodiments of the present application can be implemented in an order other than that illustrated or described here. Also, it should be understood that the objects distinguished by "first", "second", etc. are usually of one type, and the number of objects is not limited. For example, the first object may be one or a plurality. Also, in the specification and claims, "and / or" represents at least one of the connected objects, and the symbol " / " generally represents that the related objects before and after are in an "or" relationship.

[0021] It should be noted that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems. For example, it can also be used in other wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the technology described can be used in other systems and radio communication technologies in addition to the systems and radio communication technologies described above. In the following description, a New Radio (NR) system is described for illustrative purposes, and the NR term is used in many of the following descriptions. However, these technologies are also applicable to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0022] FIG. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 may also be called a terminal device or a user equipment (UE). The terminal 11 may be a mobile phone, a tablet personal computer, a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a personal handyphone system, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), a wearable device, or an in-vehicle device (VUE), a pedestrian terminal (PUE), etc. The wearable device includes a smartwatch, a wristband, earphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 may be a base station or a core network-side device. Among them, the base station may be called an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a Node B, an evolved Node B (eNB), a home Node B, a home evolved Node B, a wireless local area network (WLAN) access point, a wireless fidelity (WiFi) node, a transmitting and receiving point (TRP), or any other suitable term in the field. As long as the same technical effect can be achieved, the base station is not limited to a specific technical term. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0023] To better understand the solution means of the embodiments of this application, the following content will be described first.

[0024] 1. NR MBS mechanism Currently, to support MBS, the base station and core network equipment can establish a shared tunnel (which can be understood as a data tunnel shared by multiple terminals) for transmitting the service data of MBS. On the other hand, the Radio Access Network (RAN) side can provide multicast services through a multicast bearer. Specifically, the MBS service can be provided in two ways: point-to-point (PTP) and point-to-multipoint (PTM). Among them, PTM is a point-to-multipoint transmission method, which can be understood as a method in which the RAN uses the same radio resources to transmit multicast service data to multiple terminals. PTP is a point-to-point transmission method, which can be understood as a method in which the RAN uses dedicated radio resources for a specific terminal to transmit multicast service data to that terminal.

[0025] In addition to the above method in which the RAN receives multicast service data from the core network through a shared tunnel, the RAN can also receive multicast service data from the core network through a dedicated tunnel for the terminal (i.e., a unicast tunnel according to the conventional mechanism). The RAN side transmits the multicast service data to the terminal through the dedicated Data Radio Bearer (DRB) for that terminal. It can be understood that the data tunnels between the terminal and the RAN, and between the RAN and the core network in this method are all dedicated unicast data transmission tunnels for the terminal.

[0026] The service data processing method provided in the embodiments of this application will be described in detail below with reference to the drawings in several embodiments and their application scenarios.

[0027] Referring to FIG. 2, the embodiments of this application provide a service data processing method including the following step 201.

[0028] In step 201, according to the MBS capability of the target node, the source node transfers the service data of the target multicast service to the target node through the data transfer tunnel of the dedicated bearer of the terminal.

[0029] It should be noted that the MBS capability of the target node refers to whether the target node has the ability to provide multicast services through multicast communication. For example, when the target node supports the MBS capability (it may be understood as having the MBS capability), the core network and the multicast tunnel can be established, and the multicast service data can be received from the core network through the multicast tunnel, and the service data of the multicast service is provided to the terminal by the Multicast Radio Bearer (MRB). Conversely, when the target node does not support the MBS capability (it may be understood as not having the MBS capability), the target node cannot establish a multicast tunnel with the core network, and can only establish a unicast tunnel dedicated to the terminal, and receive the multicast service data from the core network through the unicast tunnel, and the service data of the multicast service is provided to the terminal by the dedicated bearer of the terminal (unicast bearer, which may also be understood as the data radio bearer DRB). Since such a data transmission method is the same as the unicast service data transmission method, furthermore, it may be understood that a base station that does not support the MBS capability can be a conventional base station.

[0030] In the embodiments of the present application, the source node supports MBS capabilities. The terminal receives the target multicast service from the source node through the source multicast bearer. The MBS capabilities of the above target node may specifically support MBS capabilities or not support MBS capabilities. The source node determines to send the service data of the target multicast service to the dedicated bearer of the terminal according to the MBS capabilities of the target node. For example, the terminal receives the service data of the target multicast service with the temporary mobile group identity (TMGI) of TMGI 1, that is, the multicast service identification information, through the multicast radio bearer, that is, the source multicast bearer MRB 1, at the source node, and the source node determines to switch the terminal to the target node. When the target node does not support MBS, since MRB1 cannot be switched to the target node, after the terminal is switched to the target node, the source node determines to transfer the data corresponding to MRB1 to the terminal through the dedicated bearer of the terminal, for example, DRB1, so that the source node can continue to receive the service data of the multicast service TMGI 1 from the target node.

[0031] In the embodiments of the present application, according to the MBS capabilities of the target node, the source node sends the service data of the target multicast service to the terminal through the dedicated bearer, so as to solve the problem that the interruption time of the multicast service data is too long when the terminal moves from a node that supports MBS to a node that does not support MBS.

[0032] In some embodiments, before the step of the source node transferring the service data of the target multicast service to the target node through the data transfer tunnel of the dedicated bearer of the terminal according to the MBS capability of the target node, the method further includes the step of the source node obtaining the MBS capability of the target node based on one or more pieces of information of the following Method 1 and Method 2. That is, the source node can obtain the support status of the target node for the MBS capability by the following Method 1 and Method 2, and further determine whether the target node is a conventional node (not supporting the MBS capability).

[0033] Method 1 Multicast setting information in the handover confirmation message

[0034] Specifically, the step of the source node obtaining the MBS capability of the target node based on the multicast setting information in the handover confirmation message includes (1) The step of the source node sending a handover request message to the target node, where the handover request message includes the multicast setting information at the source node of the terminal; (2) The step of the source node receiving a handover confirmation message from the target node; (3) The source node (3.1) When the handover confirmation message does not include the multicast setting information at the target node of the terminal, determining that the target node does not support the MBS capability; (3.2) When the handover confirmation message includes the multicast setting information at the target node of the terminal, determining that the target node supports the MBS capability, and including at least one of the steps of executing.

[0035] In the embodiments of this application, the source node includes multicast configuration information (for example, multicast bearer MRB configuration information) in the source node of the terminal in the switching request, receives a switching confirmation message from the target node, and if the multicast configuration information (for example, multicast bearer MRB configuration information) in the target node of the terminal is not included in the switching confirmation message of the target node, the source node determines that the target node is a conventional node. It can be understood that in such a method, the source node can determine for the first time that the target node is a conventional node in the process of reaching an agreement on the switch.

[0036] Method 2: Capability interaction information between the source node and the target node, for example, information on the interaction through the Xn interface between the source node and the target node

[0037] Specifically, the step in which the source node obtains the MBS capability of the target node based on the capability interaction information between the source node and the target node includes: (1) The step in which the source node sends a capability request message to the target node; (2) The step in which the source node receives a capability request response message from the target node, where the capability request response message includes the capability information supported and / or not supported by the target node; (3) Based on the capability information supported and / or not supported by the target node, the step of determining that the target node does not support the MBS capability or supports the MBS capability.

[0038] In an embodiment of the present application, the source node sends a capability requirement message to the target node, and the target node includes in the capability requirement response message the capability information that the target node supports and / or does not support. The capability information supported by the target node means all the capabilities supported by the target node. If there is no MBS capability among them, it can be determined that the target node does not support the MBS capability. Similarly, the capability information not supported by the target node means all the capabilities not supported by the target node. If the MBS capability is included among them, it can be determined that the target node does not support the MBS capability.

[0039] Specifically, the step in which the source node obtains the MBS capability of the target node based on the capability interaction information between the source node and the target node is as follows: (1) A step in which the source node sends a capability instruction message to the target node, and the capability instruction message includes the capability information supported and / or not supported by the source node; (2) A step in which the source node receives a capability instruction confirmation message from the target node, and the capability instruction confirmation message includes the capability information supported and / or not supported by the target node; (3) Based on the capability information supported and / or not supported by the target node, determining whether the target node does not support the MBS capability or supports the MBS capability.

[0040] In an embodiment of the present application, the source node sends a capability indication message to the target node, and the message includes the capabilities supported and / or not supported by the source node. For example, the source node can carry the capability information of whether the source node supports and / or does not support MBS in the XN SETUP REQUEST message. In this case, the target node can include the capability information supported and / or not supported by the target node in the capability indication confirmation message. Accordingly, the target node can carry the capability information of whether the target node supports and / or does not support MBS in the XN SETUP RESPONSE message.

[0041] It should be noted that through the Xn interaction process similar to the above, the source node can determine whether the target node is a node that does not support MBS before reaching an agreement on the handover. It should also be noted that when the source node determines that the target node is a conventional node before reaching an agreement on the handover, the handover request does not include multicast-related configuration information (for example, multicast bearer-related configuration information).

[0042] In some embodiments, the method for the source node to configure a dedicated bearer for the terminal may be either of the following configuration method 1 and configuration method 2.

[0043] Configuration method 1 The source node configures a dedicated bearer before deciding to switch the terminal to the target node.

[0044] In an embodiment of the present application, the dedicated bearer of the terminal is a dedicated bearer for service data transmission of the target multicast service, which is set before the source node determines to switch the terminal to the target node. For example, when the terminal is at the source node, the terminal receives the multicast service data of the multicast service TMGI1 through the multicast bearer MRB1. Further, the source node also sets a dedicated bearer DRB1 for the terminal, and the dedicated bearer DRB1 can be used to transmit the multicast service data of the multicast service TMGI1. When the terminal is at the source node, since the terminal can receive the multicast service data through the multicast bearer MRB1, the source node does not need to perform data transmission through the dedicated bearer DRB1. This setting method can be applied in a scenario where the target node is determined to be a conventional base station before or after the handover agreement by the source node.

[0045] Setting method 2 After determining to switch the terminal to the target node, the source node sets a dedicated bearer.

[0046] In the embodiments of the present application, the dedicated bearer of the terminal is a dedicated bearer for the service data transmission of the target multicast service that is set for the terminal in the switching preparation process after the source node determines to switch the terminal to the target node. For example, when the terminal is at the source node, it receives the multicast service data of the multicast service TMGI1 through the multicast bearer MRB1, and the source node determines to switch the terminal to the target node. Since the source node has previously obtained through the Xn interaction that the target node is a conventional base station, it temporarily establishes one dedicated bearer for the terminal and continues to transmit the multicast service data of the multicast service TMGI1 to the terminal through the dedicated bearer. Such a method of setting the dedicated bearer has the advantage that the dedicated bearer is set as needed, that is, it is only set when the terminal switches to a target node that does not support MBS. Since there is no need to set it when the switch has not been sent or when switching to a target node that supports MBS, the occupancy rate of the radio bearer resources can be reduced, and the radio bearer identification resources can be saved.

[0047] In some embodiments, the dedicated bearer is for bearing the service data of the target multicast service. It is understood that the dedicated bearer can be used to bear all the service data of the target multicast service, or the dedicated bearer can be used to bear a specific data flow of the target multicast service. As an example, the multicast service TMGI includes service data flows flow1 and flow2. The network side can set a dedicated bearer DRB1 for bearing all the data of the service data flows flow1 and flow2, or the network side can set a dedicated bearer DRB1 for bearing all the data of the service data flow flow1 and a dedicated bearer DRB2 for bearing all the data of flow2.

[0048] It should also be noted that when the mapping relationship between the dedicated bearer and the target multicast service is not set on the network side (the mapping relationship means that the dedicated bearer DRB1 is only used to bear the service data of the multicast service TMGI1, or the dedicated bearer DRB1 is only used to bear a specific data flow flow of the multicast service (here, different data flows can be distinguished by the data flow identification information QFI)), the network side can send the service data of multiple multicast services to the target node through the data transfer tunnel of the dedicated bearer. It can be understood that such a situation corresponds to the service data of multiple multicast services sharing the data transfer tunnel of one dedicated bearer DRB. Furthermore, the method of this patent can also be applied to a more complex scenario, that is, a scenario where the service data of one or more multicast services can share the data transfer tunnel of the unicast service and one dedicated bearer DRB.

[0049] In some embodiments, the method further includes a step in which the source node sends first indication information to the terminal, and the first indication information is for indicating that the dedicated bearer is for bearing the service data of the target multicast service.

[0050] After receiving the first instruction information, the terminal can determine that both the dedicated bearer and the source multicast bearer are capable of bearing the target multicast service data. In some scenarios, this helps to achieve submission according to the needs of the terminal. For example, the data transmitted by the source multicast bearer is later than the data transmitted by the dedicated bearer by the target node. Theoretically, the data transmitted by the terminal by the target node must be submitted to the upper layer later than the data received by the source multicast bearer. Therefore, when the terminal knows that the dedicated bearer and the source multicast bearer are associated with the same target multicast service, after all the data by the source multicast bearer is received or after waiting for a while, the terminal can submit the data received by the dedicated bearer to the upper layer of the terminal. In other scenarios, this also helps to achieve repeated detection of the terminal. For example, the network side may transmit the same data packet by both the source multicast bearer and the dedicated bearer of the target node to ensure service reliability. When the terminal knows that the dedicated bearer and the source multicast bearer are associated with the same target multicast service, the terminal can distinguish the repeatedly transmitted data based on the number of the data packet, and further avoid submitting the duplicate data packet to the upper layer of the terminal.

[0051] In some embodiments, the transfer method by which the source node transfers the service data of the target multicast service to the target node may be either of the following transfer method 1 and transfer method 2.

[0052] Transfer method 1 The source node determines a target number according to the number state of the dedicated bearer, and instructs the target number to the target node and transmits the target number. Here, the target number is for instructing the number assigned by the target node to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer.

[0053] Specifically, the step of the source node determining the target number according to the number state of the dedicated bearer includes the step of the source node determining the number to be assigned next to the dedicated bearer as the target number.

[0054] In the embodiment of the present application, the source node determines the number to be assigned to the data packet to which the next number transmitted by the dedicated bearer is not assigned according to the number state of the dedicated bearer of the terminal, and instructs the target node of the number. For example, the terminal receives the service data of the target multicast service TMGI1 by MRB1 at the source node, and the network side sets the dedicated bearer DRB1 for the terminal. Instead of transmitting the service data of the target multicast service to the terminal by the dedicated bearer DRB1, the network side transmits the service data of the target multicast service to the terminal by the multicast bearer MRB. Therefore, the number to be assigned to the next data packet transmitted by the dedicated bearer DRB1 is the initial value 0, that is, the number PDCP COUNT = 0. The terminal instructs the target node of the number 0 determined according to the number state of the dedicated bearer DRB1.

[0055] Transmission method 2 The source node determines the target number according to the number state in the source multicast bearer of the service data of the target multicast service, and instructs the target node of the target number. Here, the target number is for instructing the number assigned by the target node to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer.

[0056] Specifically, the step of the source node determining the target number according to the number state in the source multicast bearer of the service data of the target multicast service includes the step of the source node determining the number to be assigned next to the source multicast bearer as the target number.

[0057] In the embodiments of the present application, the source node determines the number to be assigned to the data packet for which the next number to be transmitted by the dedicated bearer is not assigned according to the number state in the source multicast bearer of the service data of the target multicast service, and instructs the target node of the number. For example, the terminal receives the service data of the target multicast service TMGI1 by MRB1 at the source node, and the network side sets the dedicated bearer DRB1 for the terminal. Instead of transmitting the service data of the target multicast service to the terminal by the dedicated bearer DRB1, the source node transmits the service data of the target multicast service to the terminal by the source multicast bearer MRB1. Therefore, the number state of the dedicated bearer DRB1 is the initial state, that is, no number is assigned. Currently, it is assumed that data packets with numbers 0, 1, 2, and 3 are assigned by the multicast bearer MRB1, and numbers are assigned to the data packets with numbers 4 and 5, but they are not transmitted by the source multicast bearer. Then, the next number to be assigned to the data packet transmitted by the multicast bearer is 6. In transfer method 2, the source node determines to transmit the service data of the target multicast service by the dedicated bearer, and sets the next number to be assigned to the multicast bearer as the number to be assigned to the data packet for which the next number to be transmitted by the dedicated bearer is not assigned. That is, the number to be assigned to the data packet for which the next number to be transmitted by the dedicated bearer is not assigned is 6. The terminal instructs the target node of the number 6 determined according to the number state of the source multicast bearer.

[0058] Furthermore, the method further includes a step in which the source node transfers first data to the target node through the data transfer tunnel of the dedicated bearer, and the first data includes the service data of the target multicast service that is not transmitted by the source multicast bearer of the source node.

[0059] In some embodiments, the first data is (1) Data that was sent by the source node via the source multicast bearer but not normally received by the terminal, and (2) Further includes either all data packets sent by the source node via the source multicast bearer from the first data packet that was not normally received by the terminal.

[0060] In some embodiments, the method Further includes the step of the source node determining, based on the reception status of the source multicast bearer reported by the terminal to the source node, that the data packets sent by the source multicast bearer were not normally received by the terminal.

[0061] Furthermore, before the step of the source node determining, based on the reception status of the source multicast bearer reported by the terminal to the source node, that the data packets sent by the source multicast bearer were not normally received by the terminal, the method Further includes the step of sending second indication information to the terminal, where the second indication information is for instructing the terminal to report the reception status of the source multicast bearer.

[0062] In some embodiments, the method Further includes the step of the source node using the number assigned in the source multicast bearer of the first data when transferring the first data to the target node via the data transfer tunnel of the dedicated bearer, or ignoring the number assigned in the source multicast bearer of the first data when the source node transfers the first data to the target node via the data transfer tunnel of the dedicated bearer.

[0063] It should be noted that when the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer, the step of using the number assigned in the source multicast bearer of the first data may be understood as that when the source node transfers data to the target node, it is necessary to specifically notify the target node of the number assigned in the source multicast bearer of the first data. When the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer, the step of ignoring the number assigned in the source multicast bearer of the first data may be understood as that when the source node transfers data to the target node, it is not necessary to notify the target node of the number assigned in the source multicast bearer of the first data. After the target node receives the data, if the data has no number, the target node re-assigns a number to the data. If the data has a number, the data corresponding to the number is transmitted to the terminal by the dedicated bearer using the number as it is.

[0064] Furthermore, it should be noted that in any of the above data transfer methods, the source node needs to transfer data packets to the target node in order (e.g., based on the numbers corresponding to the data packets and / or the order in which the data packets arrive at the source node) through the data transfer tunnel of the dedicated bearer. When transferring data packets, the source node transfers previously numbered data packets as needed based on the data packet numbers, and transfers data that has not been numbered based on the order in which the data packets arrive at the source node. As an example, assume that the source node sends data packets numbered 0, 1, 2, 3, 4, 5 through the source multicast bearer, and data packets numbered 6, 7, 8 are not sent through the source multicast bearer, and among them, the data packets numbered 2 and 5 are not normally received by the terminal. If the source node decides to transfer the data packets numbered 6, 7, 8 to the target node, it is necessary to transmit the data packets numbered 6, 7, 8 to the target node in ascending order of numbers. Regarding the case of ignoring the numbers assigned in the source multicast bearer of the data during data transfer, the source node still needs to transfer the data packets numbered 6, 7, 8 to the target node as needed in ascending order of numbers based on the numbers assigned in the source multicast bearer of the data.

[0065] The following will be described in association with specific examples. For example, assume that the source node transmits data packets numbered 0, 1, 2, 3, 4, 5 through the source multicast bearer, and data packets numbered 6, 7, 8 are not transmitted by the source multicast bearer. Among them, the data packets numbered 2 and 5 are not normally received by the terminal. Then, the data packets waiting to be transmitted by the dedicated bearer include the data packets numbered 6, 7, 8. Such a method corresponds to the source node transferring only the service data of the target multicast service that is not transmitted by the source multicast bearer to the target node through the data transfer tunnel of the dedicated bearer. For example, assume that the source node transmits data packets numbered 0, 1, 2, 3, 4, 5 through the source multicast bearer, and data packets numbered 6, 7, 8 are not transmitted by the source multicast bearer. Among them, the data packets numbered 2 and 5 are not normally received by the terminal.

[0066] The data packets waiting to be transmitted by the dedicated bearer may further include the data packets numbered 2 and 5 in addition to the data packets numbered 6, 7, 8. Such a method corresponds to transferring both the service data of the target multicast service that is not normally received by the terminal and the service data of the target multicast service that is not transmitted by the source multicast bearer to the target node through the data transfer tunnel of the dedicated bearer of the terminal. Of course, the data packets waiting to be transmitted by the dedicated bearer may further include the data packets numbered 2, 3, 4, 5. Such a method corresponds to transferring both all the data packets transmitted by the multicast bearer and the service data of the target multicast service that is not transmitted by the multicast bearer from the service data of the target multicast service that is not normally received by the first terminal to the target node through the data transfer tunnel of the dedicated bearer of the terminal.

[0067] Also, when the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer, if the number assigned in the source multicast bearer of the first data is ignored, regarding the service data of the target multicast service to be transferred as the new data of the dedicated bearer, it can be understood that for the data to which the number of the dedicated bearer of the terminal is not assigned, subsequently the target node re-numbers or continues to number based on the number state of the dedicated bearer instructed by the source node (that is, the target node assigns numbers to the received data without numbers according to the target number instructed by the source node). For example, the corresponding numbers in the source multicast bearer of the target multicast service to be transmitted are 2, 5, 6, 7, 8, and the dedicated bearer of the terminal has never transmitted data (in such a case, the target number instructed by the source node to the target node is 0). If the multicast service data to be transmitted is regarded as the new data of the dedicated bearer of the terminal, these data packets need to be re-numbered based on the number state of the dedicated bearer. That is, when the source node transfers these data to the target node, it is not necessary to provide the numbers assigned in the source multicast bearer of these data, and the numbers sequentially assigned by the target node to these data packets in the dedicated bearer are 0, 1, 2, 3, 4.

[0068] It should be noted that the above method can be applied in a scenario where the mapping relationship between the dedicated bearer and the target multicast service is a one-to-one relationship. For example, when a terminal receives service data of multiple multicast services at a source node, the network side may reserve one dedicated bearer for each terminal for each multicast bearer corresponding to each multicast service data. Each dedicated bearer for a terminal is for transferring the service data of each multicast service. The above method can also be applied in a scenario where the mapping relationship between the dedicated bearer and the target multicast service is a one-to-many relationship. For example, when a terminal receives service data of multiple multicast services at a source node, the network side may reserve only one dedicated bearer for each terminal for multiple multicast services.

[0069] When the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer and uses the number assigned in the source multicast bearer of the first data, the source node shall transfer, as the new data of the dedicated bearer, the service data of the target multicast service that is to be transmitted and for which no number is assigned, to the target node through the data transfer tunnel of the dedicated bearer. Specifically, for the service data of the target multicast service that is to be transmitted and for which a number is assigned, the source node shall retain the number assigned in its source multicast bearer and transfer these data to the target node through the data transfer tunnel of the dedicated bearer. For example, assume that the source node sends data packets numbered 0, 1, 2, 3, 4, 5 through the multicast bearer, and data packets numbered 6, 7, 8 are not sent by the source multicast bearer, and among them, the data packets numbered 2 and 5 are not normally received by the terminal. The source node may decide to send only the data of the dedicated bearer for the data not sent by the source multicast bearer to the target node through the transfer tunnel. In such a case, it is equivalent to transferring the data packets numbered 6, 7 and the data packets for which no number is assigned in the source multicast bearer to the target node through the data transfer tunnel of the dedicated bearer. At this time, for the data packets with numbers assigned in the source multicast bearer, the source node shall retain the original assigned numbers during transfer, that is, the target node does not need to reassign numbers. The source node may also send the data packets that are sent by the source multicast bearer but not normally received by the terminal to the target node through the data transfer tunnel of the dedicated bearer. It should be noted that the source node needs to retain the original assigned numbers of these data packets during transfer, that is, the target node does not need to reassign numbers.

[0070] Accordingly, for the target node, the target node receives the number indicated by the source node and assigns the number to the data packet that has not been assigned a number and is transmitted by the dedicated bearer. Specifically, for the data packet assigned a number and transferred by the source node, the target node holds the number and transmits this data to the terminal through the dedicated bearer.

[0071] In some embodiments, the method further includes a step in which the source node transmits first configuration information to the terminal, and the terminal configures a dedicated bearer according to the first configuration information.

[0072] Furthermore, the first configuration information includes bearer identification information configured by the dedicated bearer and does not include layer 2 configuration information of the dedicated bearer.

[0073] In the embodiments of the present application, the above method is suitable for a scenario where the dedicated bearer is pre-configured before the source node's handover decision. The dedicated bearer may be a virtual bearer, that is, the network side provides the terminal with the bearer identification information of the dedicated bearer, but does not provide the layer 2 configuration information of the dedicated bearer. That is, the network side does not provide the terminal with the layer 2 configuration information required for the bearer, such as PDCP configuration information, RLC configuration information, and logical channel configuration information. By associating the bearer identification information of the dedicated bearer with the layer 2 entity of the source multicast bearer, the terminal can continue to receive the service data of the target multicast service from the target node through the layer 2 entity of the source multicast bearer. When the terminal executes the association process, it is not necessary to process the layer 2 entity (that is, maintain the reception state of the current layer 2 entity (for example, the PDCP entity)) for rearranging and repeatedly detecting the data received from the source node and the data received by the target node.

[0074] Referring to FIG. 3, the embodiments of the present application provide a service data processing method including the following steps 301 and 302.

[0075] In step 301, the terminal reconfigures the dedicated bearer based on the reconfiguration message received from the source node.

[0076] In step 302, the terminal receives the service data of the target multicast service from the target node through the dedicated bearer.

[0077] In the embodiment of the present application, the source node supports the MBS capability, and the terminal receives the target multicast service from the source node through the source multicast bearer.

[0078] In some embodiments, the method further includes the step of the terminal setting the dedicated bearer before the source node decides to switch the terminal to the target node, or the terminal setting the dedicated bearer after the source node decides to switch the terminal to the target node.

[0079] In some embodiments, the terminal reconfigures the dedicated bearer based on the reconfiguration message, that is, the operation of the terminal reconfiguring the dedicated bearer based on the reconfiguration message received from the source node may be either of the following operation methods 1 and 2.

[0080] Operation method 1 The terminal associates the bearer identification information of the dedicated bearer with the layer 2 entity of the source multicast bearer.

[0081] In an embodiment of the present application, bearer identification information of a dedicated bearer is associated with a layer 2 entity of a source multicast bearer, and the layer 2 entity includes a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, and a Multiple Access Channel (MAC) entity. The method can be applied in a preset scenario before a dedicated bearer makes a handover decision of a source node, and can also be applied in a scenario temporarily set for a terminal after the source node makes a handover decision.

[0082] In some embodiments, the method further includes a step in which a terminal receives first configuration information from a source node, and a step in which the terminal configures a dedicated bearer based on the first configuration information.

[0083] Furthermore, the first configuration information includes bearer identification information set by the dedicated bearer, and does not include layer 2 configuration information of the dedicated bearer.

[0084] It should be noted that for a dedicated bearer in a preset scenario before the source node switching decision, the dedicated bearer may be a virtual bearer. That is, the network side provides the bearer identification information of the dedicated bearer to the terminal, but does not provide the layer 2 setting information of the dedicated bearer. That is, the network side does not provide the layer 2 entity setting information required for the bearer to the terminal, such as PDCP setting information, RLC setting information, and logical channel setting information. By associating the bearer identification information of the dedicated bearer with the layer 2 entity of the source multicast bearer, the terminal can continue to receive the service data of the target multicast service from the target node through the layer 2 entity of the source multicast bearer. When the terminal executes the association process, it is not necessary to process the layer 2 entity (i.e., maintain the reception state of the current layer 2 entity (e.g., PDCP entity)) for rearranging and repeatedly detecting the data received from the source node and the data received by the target node.

[0085] Operation method 2 The terminal obtains the reception state of the dedicated bearer based on the reception state of the source multicast bearer.

[0086] Furthermore, when the terminal determines that the target node does not support the MBS capability, the terminal obtains the reception state of the dedicated bearer based on the reception state of the source multicast bearer.

[0087] In some embodiments, before the step where the terminal obtains the reception state of the dedicated bearer based on the reception state of the source multicast bearer, the method further includes a step where the terminal receives first indication information from the source node, and the first indication information is for indicating that the dedicated bearer is for bearing the service data of the target multicast service.

[0088] By receiving the first indication information, the terminal can know which dedicated bearer and source multicast bearer are for receiving the service data of the same target multicast service. Knowing the association relationship between the dedicated bearer and the source multicast bearer, the terminal can obtain the reception state of the dedicated bearer based on the reception state of the source multicast bearer. The terminal can copy the reception state of the source multicast bearer to the dedicated bearer, and it may be understood that the dedicated bearer of the terminal can continue to receive the service data of the target multicast service transmitted by the target node. Such a method can be applied in a scenario where the source node continues to use the number assigned in the source multicast bearer of the data during data transfer. When the target node receives a data packet with a corresponding number and uses the number as it is to transmit the data to the terminal, if the terminal can copy the reception state of the source multicast bearer to the dedicated bearer, it can detect which data has not been received and which data has been received. Also, repeated detection and rearrangement operations can be performed.

[0089] The above step in which the terminal obtains that the target node does not support the MBS capability includes at least one of the following (1) and (2).

[0090] (1) Based on the PDCP status report indication information of the dedicated bearer, the terminal determines that the target node does not support the MBS capability.

[0091] For example, when the network side configures the terminal to report the reception status of the source multicast bearer, the terminal can determine that the target node is an extended node, i.e., a node with MBS capabilities. When the network side configures the terminal to report the reception status of the dedicated bearer, the terminal can determine that the target node is a conventional node. For example, if the terminal has never received data through the dedicated bearer, theoretically the network side will not configure the terminal to report the reception status of the dedicated bearer. However, when the network side configures the terminal to report the reception status of the dedicated bearer and the dedicated bearer and the source multicast bearer are associated (i.e., for carrying service data of the same target multicast service), the terminal may understand that the network side is attempting to have the terminal report the reception status of the source multicast bearer. Furthermore, the terminal can determine that the target node does not have MBS capabilities.

[0092] (2) If the reconfiguration message does not contain the multicast configuration information of the target multicast service, the terminal determines that the target node does not support MBS capabilities.

[0093] For example, when receiving a reconfiguration message containing a switching command, if the terminal identifies that the configuration message does not contain the multicast configuration information of the target multicast service, it determines that the target node is a conventional node. If the terminal identifies that the configuration message contains the multicast configuration information of the target multicast service, it determines that the target node is an extended node, i.e., a base station supporting MBS capabilities.

[0094] As an example of the terminal executing the above operation method 2, the network side has pre-configured a dedicated bearer DRB1 for the terminal. The dedicated bearer DRB1 is reserved for the target multicast service TMGI1 set by the network side. At the source node, the terminal receives the service data of the target multicast service TMGI1 through the multicast bearer MRB1 set by the network side. When receiving a re-configuration message containing a switching command, if the terminal identifies that the multicast configuration information of the target multicast service is not included in the configuration message, it determines that the target node is a conventional node. The terminal initializes the reception state of the dedicated bearer according to the reception state of the source multicast bearer. For example, it copies the reception state of the source multicast bearer to the dedicated bearer. Specifically, the terminal can also transfer the data in the source multicast bearer buffer to the buffer of the dedicated bearer. Such a method can be applied in a scenario where the source node always adopts the above transfer method 2 for the method of transferring data to the target node.

[0095] In some embodiments, the above operation method 2 may also be executed according to instruction information. That is, the step of the terminal obtaining the reception state of the dedicated bearer based on the reception state of the source multicast bearer includes the following (1) and (2).

[0096] (1) When the terminal receives the third instruction information from the source node, it synchronizes the reception state of the dedicated bearer according to the reception state of the source multicast bearer. The third instruction information is for instructing the source node to determine the target number according to the number state of the source multicast bearer of the service data of the target multicast service. Here, the target number is for instructing the number that the target node assigns to the target data packet. The target data packet is the next unnumbered data packet transmitted by the dedicated bearer. That is, the first instruction information instructs the source node to transfer the service data of the target multicast service to the target node through the data transfer tunnel of the dedicated bearer by transfer method 2.

[0097] In the embodiment of the present application, since the target data packet is numbered according to the number state of the source multicast bearer, considering that the reception state of the dedicated bearer (for example, the size of the data packet reception window, the corresponding receivable data packet number) and the number state of the source multicast bearer may not match, in order to ensure that the data packet on the source multicast bearer can be received by the dedicated bearer, it is necessary to synchronize the reception state of the dedicated bearer according to the reception state of the source multicast bearer.

[0098] (2) When the terminal receives the fourth instruction information from the source node, it maintains the current reception state of the dedicated bearer. The fourth instruction information is for instructing the source node to determine the target number according to the number state of the dedicated bearer. Here, the target number is for instructing the number that the target node assigns to the target data packet. The target data packet is the next unnumbered data packet transmitted by the dedicated bearer. That is, the second instruction information instructs the source node to transfer the service data of the target multicast service to the target node through the data transfer tunnel of the dedicated bearer by transfer method 1.

[0099] In the embodiments of the present application, when the source node does not transfer the service data of the target multicast service through a dedicated bearer, the reception state of the dedicated bearer is in an initial state, that is, the variables of the related reception states are initial values determined by the protocol. Since the target data packet is numbered according to the number state of the dedicated bearer, the terminal side only needs to maintain the current reception state of the dedicated bearer, and can ensure that the data packet on the source multicast bearer can be received through the dedicated bearer.

[0100] It should be particularly noted that the above third instruction information and fourth instruction information may be the same instruction parameter, for example, a 1-bit instruction parameter. When the value of the instruction parameter is "1", it means the above third instruction information, and when the value of the instruction parameter is "0", it means the above fourth instruction information. Of course, the third instruction information and the fourth instruction information may also be different instruction parameters, and the embodiments of the present application do not specifically limit this.

[0101] Regarding the above operation method 2, when the terminal receives a reset message including a switching command, if the reset message does not instruct the terminal to release the layer 2 entity (for example, PDCP entity, RLC entity) of the source multicast bearer, the terminal initializes the reception state of the dedicated bearer according to the reception state of the source multicast bearer, and transfers the data in the layer 2 entity buffer of the source multicast bearer to the layer 2 entity corresponding to the dedicated bearer. For example, the terminal transfers the data in the reception buffer of the PDCP entity of the source multicast bearer to the reception buffer of the PDCP entity of the dedicated bearer.

[0102] Specifically, when the terminal receives network status report instruction information (the status report instruction information is for instructing the terminal to report the reception state in which the terminal receives data through a dedicated bearer), the terminal reports the reception state of the source multicast bearer through the dedicated bearer.

[0103] In some embodiments, the method further includes a step in which the terminal receives second instruction information from the source node, and the second instruction information is for instructing the terminal to report the reception state of the source multicast bearer to the source node.

[0104] Furthermore, the method further includes a step in which the terminal reports the reception state of the source multicast bearer to the source node.

[0105] It should be noted that the service data processing method provided in the embodiments of this application may be that the execution entity is a service data processing device, or a control module for executing the service data processing method in the service data processing device. In the embodiments of this application, taking the service data processing device executing the service data processing method as an example, the service data processing device provided in the embodiments of this application will be described.

[0106] Referring to FIG. 4, the embodiments of this application include a first transfer module 401 for the source node to transfer service data of the target multicast service to the target node through the data transfer tunnel of the dedicated bearer of the terminal according to the MBS capability of the target node. The terminal receives the target multicast service from the source node through the source multicast bearer, and provides a service data processing device 400.

[0107] In some embodiments, the device the source node further includes a first acquisition module for acquiring the MBS capability of the target node based on one or more pieces of information including the multicast setting information in the handover confirmation message and the capability interaction information between the source node and the target node.

[0108] In some embodiments, the first acquisition module further The step in which the source node sends a switching request message to the target node, wherein the switching request message includes the multicast setting information at the source node of the terminal. The step in which the source node receives a switching confirmation message from the target node. The source node When the switching confirmation message does not include the multicast setting information at the target node of the terminal, determining that the target node does not support the MBS capability. When the switching confirmation message includes the multicast setting information at the target node of the terminal, determining that the target node supports the MBS capability. At least one of the steps is executed.

[0109] In some embodiments, the first acquisition module further The step in which the source node sends a capability request message to the target node. The step in which the source node receives a capability request response message from the target node, wherein the capability request response message includes the capability information supported and / or not supported by the target node. Based on the capability information supported and / or not supported by the target node, determining that the target node does not support or supports the MBS capability. Or The first acquisition module further The step in which the source node sends a capability indication message to the target node, wherein the capability indication message includes the capability information supported and / or not supported by the source node. The step in which the source node receives a capability indication confirmation message from the target node, where the capability indication confirmation message includes capability information supported by the target node and / or capability information not supported by the target node. It is used for determining, based on the capability information supported by the target node and / or the capability information not supported by the target node, whether the target node does not support the MBS capability or supports the MBS capability.

[0110] In some embodiments, the apparatus sets the dedicated bearer before the source node decides to switch the terminal to the target node, or or further includes a first setting module for setting the dedicated bearer after the source node decides to switch the terminal to the target node.

[0111] In some embodiments, the dedicated bearer is for bearing the service data of the target multicast service.

[0112] In some embodiments, the apparatus further includes a first transmission module for the source node to transmit first indication information to the terminal, where the first indication information is for indicating that the dedicated bearer is for bearing the service data of the target multicast service.

[0113] In some embodiments, the apparatus determines a target number according to the number state of the dedicated bearer by the source node and instructs the target node with the target number, or or the source node further includes a first determination module for determining a target number according to the number state in the source multicast bearer of the service data of the target multicast service and instructing the target node with the target number. Here, the target number is for indicating the number that the target node assigns to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer.

[0114] In some embodiments, in the apparatus, the first determination module further determines whether the source node determines the next number to be assigned by the dedicated bearer as the target number, or is for the source node to determine the next number to be assigned by the source multicast bearer as the target number.

[0115] In some embodiments, the apparatus further includes a second transfer module for the source node to transfer first data to the target node through the data transfer tunnel of the dedicated bearer, and the first data includes service data of the target multicast service that the source node does not transmit by the source multicast bearer.

[0116] In some embodiments, the first data further includes either data that the source node transmitted by the source multicast bearer but was not normally received by the terminal, or all data packets that the source node transmitted by the source multicast bearer from the first data packet that was not normally received by the terminal.

[0117] In some embodiments, the apparatus further includes a first acquisition module for the source node to determine that the data packets transmitted by the source multicast bearer were not normally received by the terminal based on the reception state of the source multicast bearer reported by the terminal to the source node.

[0118] In some embodiments, the apparatus Before the source node determines that the data packet transmitted by the source multicast bearer is not normally received by the terminal based on the reception state of the source multicast bearer reported by the terminal to the source node, the apparatus further includes a second transmission module for transmitting second indication information to the terminal, where the second indication information is for instructing the terminal to report the reception state of the source multicast bearer.

[0119] In some embodiments, the apparatus When the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer, whether to use the number assigned in the source multicast bearer of the first data, Or When the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer, the apparatus further includes a numbering module for ignoring the number assigned in the source multicast bearer of the first data.

[0120] In some embodiments, the apparatus The source node further includes a third transmission module for transmitting first setting information to the terminal, and the terminal sets the dedicated bearer based on the first setting information.

[0121] In some embodiments, the first setting information includes bearer identification information set by the dedicated bearer and does not include layer 2 setting information of the dedicated bearer.

[0122] Referring to FIG. 5, the embodiment of the present application A second setting module 501 for resetting the dedicated bearer based on the reset message received by the terminal from the source node, and A first receiving module 502 for the terminal to receive service data of a target multicast service from a target node by means of the dedicated bearer, The terminal provides a service data processing apparatus 500 that receives the target multicast service from the source node by means of a source multicast bearer.

[0123] In some embodiments, the apparatus either sets the dedicated bearer by the terminal before the source node determines to switch the terminal to the target node, or further comprises a third setting module for the terminal to set the dedicated bearer after the source node determines to switch the terminal to the target node.

[0124] In some embodiments, the second setting module further either associates the bearer identification information of the dedicated bearer with the layer 2 entity of the source multicast bearer by the terminal, or is for the terminal to obtain the reception state of the dedicated bearer based on the reception state of the source multicast bearer.

[0125] In some embodiments, the second setting module further is for the terminal to obtain the reception state of the dedicated bearer based on the reception state of the source multicast bearer when the terminal obtains that the target node does not support MBS capabilities.

[0126] In some embodiments, the apparatus further comprises a second receiving module for the terminal to receive first indication information from the source node before the step of the terminal obtaining the reception state of the dedicated bearer based on the reception state of the source multicast bearer, and the first indication information is for indicating that the dedicated bearer is for bearing service data of the target multicast service.

[0127] In some embodiments, the second setting module further is used for at least one of the following steps: when the terminal determines, based on the packet data convergence protocol (PDCP) status report indication information of the dedicated bearer, that the target node does not support the MBS capability; and when the terminal determines that the target node does not support the MBS capability if the reconfiguration message does not include the multicast setting information of the target multicast service. In some embodiments, the second setting module further

[0128] is used for synchronizing the reception state of the dedicated bearer according to the reception state of the source multicast bearer when the terminal receives third indication information from the source node. The third indication information is for instructing the source node to determine a target number according to the number state of the service data of the target multicast service in the source multicast bearer. The target number is for instructing the number that the target node assigns to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer. Or, In some embodiments, the second setting module further is used for maintaining the current reception state of the dedicated bearer when the terminal receives fourth indication information from the source node. The fourth indication information is for instructing the source node to determine a target number according to the number state of the dedicated bearer. The target number is for instructing the number that the target node assigns to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer. In some embodiments, the device

[0129] In some embodiments, the device The terminal further comprises a third receiving module for receiving second instruction information from the source node, where the second instruction information is for instructing the terminal to report the reception state of the source multicast bearer to the source node.

[0130] In some embodiments, the apparatus further comprises a reporting module for the terminal to report the reception state of the source multicast bearer to the source node.

[0131] In some embodiments, the apparatus further comprises a fourth receiving module for the terminal to receive first setting information from the source node, and a fourth setting module for the terminal to set the dedicated bearer based on the first setting information.

[0132] In some embodiments, the first setting information includes bearer identification information set by the dedicated bearer and does not include layer 2 setting information of the dedicated bearer.

[0133] In the embodiments of this application, the source node transmits service data of the target multicast service to the terminal through a dedicated bearer according to the MBS capability of the target node, so as to solve the problem that the interruption time of the multicast service data is too long when the terminal moves from a node supporting MBS to a node not supporting MBS.

[0134] The service data processing apparatus in the embodiments of this application may be a device, a device having an operating system, or an electronic device, or may be a member, an integrated circuit, or a chip in a terminal. The device or the electronic device may be a portable terminal or a non-portable terminal. By way of example, the portable terminal may include the types of terminal 11 listed above, but is not limited thereto, and the non-portable terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a cash dispenser, or a kiosk, etc., and the embodiments of this application are not specifically limited.

[0135] The service data processing apparatus provided in the embodiments of this application realizes each process realized in the method embodiments shown in FIGS. 2 to 3 and can achieve the same technical effects. For the sake of brevity, detailed descriptions are omitted here.

[0136] Optionally, as shown in FIG. 6, the embodiments of this application further provide a communication device 600 including a processor 601, a memory 602, and a program or command stored in the memory 602 and executable on the processor 601. For example, when the communication device 600 is a source node, when the program or command is executed by the processor 601, each process of the method embodiment of the service data processing method shown in FIG. 2 above is realized and the same technical effects can be achieved. When the communication device 600 is a terminal, when the program or command is executed by the processor 601, each process of the method embodiment of the service data processing method shown in FIG. 3 above is realized and the same technical effects can be achieved. For the sake of brevity, detailed descriptions are omitted here.

[0137] Embodiments of the present application further provide a source node, the source node comprising a processor and a communication interface, wherein the communication interface is for the source node to transfer service data of a target multicast service to a target node through a dedicated bearer data transfer tunnel of a terminal according to the MBS capability of the target node, and the terminal receives the target multicast service from the source node through a source multicast bearer. Embodiments of the source node correspond to the above source node method embodiments, and each implementation process and realization method of the above method embodiments can be applied in the source node embodiments and can achieve similar technical effects.

[0138] Specifically, embodiments of the present application further provide a source node. As shown in FIG. 7, the source node 700 includes an antenna 71, a radio frequency device 72, and a baseband device 73. The antenna 71 is connected to the radio frequency device 72. In the uplink direction, the radio frequency device 72 receives information via the antenna 71 and transmits the received information to the baseband device 73 for processing. In the uplink direction, the baseband device 73 processes the transmitted information and transmits it to the radio frequency device 72, and the radio frequency device 72 processes the received information and then transmits it via the antenna 71.

[0139] The above frequency band processing device may be in the baseband device 73. The method executed by the source node in the above embodiments can be realized by the baseband device 73, and the baseband device 73 includes a processor 74 and a memory 75.

[0140] The baseband device 73 may include, for example, at least one baseband board with a plurality of chips installed. As shown in FIG. 7, one of the chips is, for example, a processor 74 connected to the memory 75 to call a program in the memory 75 to execute the operations of the network device shown in the above method embodiments.

[0141] The baseband device 73 may further include a network interface 76 for communicating information with the high-frequency device 72, and the interface may be, for example, a common public radio interface (CPRI).

[0142] Specifically, the source node according to the embodiment of the present invention further includes commands or programs stored in the memory 75 and executable on the processor 74. The processor 74 calls the commands or programs in the memory 75 to execute the methods executed by each module shown in FIG. 4 and can achieve similar technical effects. For the sake of not repeating the description, the detailed description is omitted here.

[0143] The embodiment of the present application further provides a terminal, which includes a processor and a communication interface. Among them, the processor is for resetting a dedicated bearer based on a reset message received by the terminal from a source node, and the communication interface is for the terminal to receive service data of a target multicast service from a target node through the dedicated bearer. The terminal receives the target multicast service from the source node through a source multicast bearer. The terminal embodiment corresponds to the above terminal-side method embodiment, and each implementation process and realization method of the above method embodiment can be applied in the terminal embodiment and can achieve similar technical effects. Specifically, FIG. 8 is a schematic diagram of the hardware structure of the terminal for realizing the embodiment of the present application.

[0144] The terminal 800 includes at least some of the members such as a high-frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, and a processor 810, but is not limited thereto.

[0145] A person skilled in the art should understand that the terminal 800 may further include a power source (e.g., a battery) for supplying power to each component. The power source may be logically connected to the processor 810 by a power management system. In this way, the power management system realizes functions such as charge and discharge management and power consumption management. The structure of the terminal shown in FIG. 8 does not limit the terminal. It is understandable that the terminal may include more or fewer components than shown in the figure, or a combination of some components, or different component arrangements. Detailed description is omitted here.

[0146] In the embodiments of the present application, it should be understood that the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042 for processing still image or video image data acquired by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 807 includes a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. The other input devices 8072 may include a physical keyboard, function buttons (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, an operation lever, etc., but are not limited thereto, and the description is omitted here.

[0147] In the embodiments of the present application, after receiving downlink data from a network-side device, the high-frequency unit 801 processes it with the processor 810 and also transmits uplink data to the network-side device. Usually, the high-frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0148] Memory 809 can be used to store software programs and various data. Memory 809 may mainly include a program or command storage area and a data storage area capable of storing an operating system, an application or command (e.g., voice playback function, image playback function, etc.) required for at least one function. Further, Memory 809 may include a high-speed random access memory, and may also include a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices may be mentioned.

[0149] Processor 810 may include one or more processing units. Optionally, an application processor mainly processing an operating system, a user interface, an application, etc. and a modem processor mainly processing wireless communication such as a baseband processor can be integrated into Processor 810. It can be understood that the above modem processor may not be integrated into Processor 810.

[0150] Here, Processor 810 is for resetting a dedicated bearer based on a reset message received by the terminal from a source node.

[0151] The high-frequency unit 801 is for the terminal to receive service data of a target multicast service from a target node through the dedicated bearer. Here, the terminal receives the target multicast service from the source node through a source multicast bearer.

[0152] Optionally, the processor 810 further determines whether the terminal sets the dedicated bearer before the source node determines to switch the terminal to the target node, or is for the terminal to set the dedicated bearer after the source node determines to switch the terminal to the target node.

[0153] Optionally, the processor 810 further determines whether the terminal associates the bearer identification information of the dedicated bearer with the layer 2 entity of the source multicast bearer, or is for the terminal to obtain the reception state of the dedicated bearer based on the reception state of the source multicast bearer.

[0154] Optionally, the processor 810 further is for the terminal to obtain the reception state of the dedicated bearer based on the reception state of the source multicast bearer when the terminal obtains that the target node does not support the MBS capability.

[0155] Optionally, the high-frequency unit 801 is for the terminal to receive first indication information from the source node before the step of obtaining the reception state of the dedicated bearer based on the reception state of the source multicast bearer, and the first indication information is for indicating that the dedicated bearer is for bearing the service data of the target multicast service.

[0156] Optionally, the processor 810 further determines that the target node does not support the MBS capability based on the packet data convergence protocol PDCP status report indication information of the dedicated bearer by the terminal, and When the re - setting message does not include the multicast setting information of the target multicast service, it is used for at least one of the step in which the terminal determines that the target node does not support MBS capabilities.

[0157] Optionally, the processor 810 further When the terminal receives third instruction information from the source node, it is for synchronizing the reception state of the dedicated bearer according to the reception state of the source multicast bearer. The third instruction information is for instructing the source node to determine a target number according to the number state of the service data of the target multicast service in the source multicast bearer. The target number is for instructing the number that the target node assigns to the target data packet. The target data packet is the next unnumbered data packet transmitted by the dedicated bearer. Or The processor 810 further When the terminal receives fourth instruction information from the source node, it is for maintaining the current reception state of the dedicated bearer. The fourth instruction information is for instructing the source node to determine a target number according to the number state of the dedicated bearer. The target number is for instructing the number that the target node assigns to the target data packet. The target data packet is the next unnumbered data packet transmitted by the dedicated bearer.

[0158] Optionally, the high - frequency unit 801 Is for the terminal to receive second instruction information from the source node. The second instruction information is for instructing the terminal to report the reception state of the source multicast bearer to the source node.

[0159] Optionally, the high - frequency unit 801 The terminal is for reporting the reception state of the source multicast bearer to the source node.

[0160] Optionally, the high-frequency unit 801 is for the terminal to receive first setting information from a source node, and the processor 810 is for the terminal to set the dedicated bearer based on the first setting information.

[0161] Optionally, the first setting information includes bearer identification information set by the dedicated bearer and does not include layer 2 setting information of the dedicated bearer.

[0162] Embodiments of the present application further provide a readable storage medium, in which a program or command is stored. When the program or command is executed by a processor, each process of the service data processing method embodiment is realized, and the same technical effects can be achieved. For the sake of brevity, detailed descriptions are omitted here.

[0163] Here, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes, for example, computer-readable storage media such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0164] Embodiments of the present application further provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is for executing a program or command to realize each process of the service data processing method embodiment, and the same technical effects can be achieved. For the sake of brevity, detailed descriptions are omitted here.

[0165] It should be understood that the chip described in the embodiments of the present application may also be referred to as a system-level chip, a system-on-chip, a chip system, a system-on-a-chip, or the like.

[0166] The embodiments of the present application further provide a computer program product, which is stored in a non-volatile readable storage medium and executed by at least one processor to implement each process of the embodiments of the above service data processing method, and can achieve similar technical effects. For the sake of brevity, detailed descriptions are omitted here.

[0167] The embodiments of the present application further provide a communication device, which is configured to execute each process of the embodiments of the above service data processing method, and can achieve similar technical effects. For the sake of brevity, detailed descriptions are omitted here.

[0168] It should be noted that in this specification, the term "including", "consisting of" or any other variation is intended to include non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such a process, method, article or device. Unless otherwise specified, the elements limited by the phrase "including one..." do not exclude the further existence of the same other elements in the process, method, article or device including the element. It should also be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order illustrated or considered, and may also include performing functions substantially simultaneously or in reverse order according to such functions. For example, the described method may be executed in an order different from that described, and various steps may be added, omitted, or combined. Also, the features described with reference to any example may be combined in other examples.

[0169] From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be realized in the form of a combination of software and the necessary common hardware platform. Of course, it may also be realized by hardware, but in many cases, the former is a more preferred embodiment. Based on such an understanding, the technical solution of this application or the part that contributes to the prior art can be implemented in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of commands for causing a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the embodiments of this application.

[0170] As described above, the embodiments of this application have been described with reference to the drawings. However, this application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Based on the inspiration of this application, many forms that those skilled in the art can make without departing from the spirit and protection scope of the claims of this application all belong to the protection scope of this application.

Description of Reference Signs

[0171] 11 Terminal 12 Network-side Device 71 Antenna 72 High-frequency Device 73 Baseband Device 74 Processor 75 Memory 76 Network Interface 201 Step 301 Step 302 Step 400 Service Data Processing Device 401 First Transfer Module 500 Service Data Processing Device 501 Second Setting Module 502 First Reception Module 600 Communication Device 601 Processor 602 Memory 700 Source Node 800 Terminal 801 High-Frequency Unit 802 Network Module 803 Audio Output Unit 804 Input Unit 805 Sensor 806 Display Unit 807 User Input Unit 808 Interface Unit 809 Memory 810 Processor 8041 Graphics Processing Unit (GPU) 8042 Microphone 8061 Display Panel 8071 Touch Panel 8072 Input Device

Claims

When the target node does not support the MBS capability, the method includes the step of the source node transferring service data of the target multicast service to the target node through a data transfer tunnel of the dedicated bearer of the terminal, before the terminal switches to the target node, the terminal receives the target multicast service from the source node through a source multicast bearer, before the step of the source node transferring service data of the target multicast service to the target node through a data transfer tunnel of the dedicated bearer of the terminal, the method further includes the step of the source node obtaining the MBS capability of the target node based on multicast configuration information in a handover confirmation message, the step of the source node obtaining the MBS capability of the target node based on multicast configuration information in a handover confirmation message includes the step of the source node sending a handover request message to the target node, where the handover request message includes multicast configuration information of the terminal at the source node, the step of the source node receiving a handover confirmation message from the target node, the source node when the handover confirmation message does not include multicast configuration information of the terminal at the target node, determining that the target node does not support the MBS capability, when the handover confirmation message includes multicast configuration information of the terminal at the target node, determining that the target node supports the MBS capability, and performing at least one of the steps, a service data processing method.

2. before the step of the source node transferring service data of the target multicast service to the target node through a data transfer tunnel of the dedicated bearer of the terminal, the method according to claim 1, further including the step of the source node obtaining the MBS capability of the target node based on capability interaction information between the source node and the target node.

3. The step of the source node obtaining the MBS capability of the target node based on capability interaction information between the source node and the target node includes the step of the source node sending a capability request message to the target node, The step in which the source node receives a capability request response message from the target node, wherein the capability request response message includes the capability information supported by the target node and / or the capability information not supported by the target node; Based on the capability information supported by the target node and / or the capability information not supported by the target node, determining whether the target node does not support the MBS capability or supports the MBS capability, or Or, The step in which the source node transmits a capability indication message to the target node, wherein the capability indication message includes the capability information supported by the source node and / or the capability information not supported by the source node; The step in which the source node receives a capability indication confirmation message from the target node, wherein the capability indication confirmation message includes the capability information supported by the target node and / or the capability information not supported by the target node; Based on the capability information supported by the target node and / or the capability information not supported by the target node, determining whether the target node does not support the MBS capability or supports the MBS capability, the method according to claim 2.

4. The dedicated bearer is for bearing the service data of the target multicast service, The method according to claim 1, further including the step in which the source node transmits first indication information to the terminal, wherein the first indication information is for indicating that the dedicated bearer is for bearing the service data of the target multicast service.

5. The source node determines a target number according to the number state of the dedicated bearer and instructs the target node of the target number, or Or, The method further includes the step in which the source node determines a target number according to the number state in the source multicast bearer of the service data of the target multicast service and instructs the target node of the target number, The target number is for instructing the number that the target node assigns to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer. The step in which the source node determines a target number according to the number state of the dedicated bearer includes the step in which the source node determines the next number to be assigned to the dedicated bearer as the target number, or The step in which the source node determines a target number according to the number state in the source multicast bearer of the service data of the target multicast service, the method according to claim 1, includes the step in which the source node determines the next number to be assigned to the source multicast bearer as the target number.

6. The method according to claim 1 further includes the step in which the source node transfers first data to the target node through the data transfer tunnel of the dedicated bearer, and the first data includes service data of the target multicast service that the source node does not transmit through the source multicast bearer, The first data includes either data that the source node transmitted through the source multicast bearer but was not normally received by the terminal, or all data packets that the source node transmitted through the source multicast bearer starting from the first data packet that was not normally received by the terminal.

7. The method according to claim 6 further includes the step in which the source node determines, based on the reception state of the source multicast bearer reported by the terminal to the source node, that the data packet transmitted by the source multicast bearer was not normally received by the terminal. Before the step in which the source node determines, based on the reception state of the source multicast bearer reported by the terminal to the source node, that the data packet transmitted by the source multicast bearer was not normally received by the terminal, the method according to claim 6 further includes the step of transmitting second indication information to the terminal, and the second indication information is for instructing the terminal to report the reception state of the source multicast bearer.

8. When the source node transfers the first data to the target node through the data transfer tunnel of the dedicated bearer, whether to use the number assigned in the source multicast bearer of the first data, or The method according to claim 6, further comprising, when the source node transfers first data to the target node through the data transfer tunnel of the dedicated bearer, ignoring the number assigned in the source multicast bearer of the first data.

9. The method further comprises a step in which the source node transmits first setting information to the terminal, and the terminal sets the dedicated bearer according to the first setting information, wherein the first setting information includes bearer identification information set by the dedicated bearer and does not include layer 2 setting information of the dedicated bearer, according to the method of claim 1.

10. A step in which the terminal re-sets a dedicated bearer based on a re-setting message received from a source node; and a step in which the terminal receives service data of a target multicast service from a target node through the dedicated bearer, wherein the terminal receives the target multicast service from the source node through a source multicast bearer before switching to the target node, The method further comprises a step in which the source node obtains the MBS capability of the target node based on the multicast setting information in the switch confirmation message, The step in which the source node obtains the MBS capability of the target node based on the multicast setting information in the switch confirmation message is a step in which the source node transmits a switch request message to the target node, and the switch request message includes the multicast setting information of the terminal at the source node, a step in which the source node receives a switch confirmation message from the target node, The source node when the switch confirmation message does not include the multicast setting information of the terminal at the target node, determining that the target node does not support the MBS capability; and when the switch confirmation message includes the multicast setting information of the terminal at the target node, determining that the target node supports the MBS capability, and includes at least one of the steps of executing,

11. The step in which the terminal re-sets a dedicated bearer based on a re-setting message received from a source node is The terminal associates the bearer identification information of the dedicated bearer with the Layer 2 entity of the source multicast bearer, or or The method according to claim 10, further comprising the step of the terminal obtaining the reception state of the dedicated bearer according to the reception state of the source multicast bearer. **Claim 12** The step that the terminal obtains the reception state of the dedicated bearer according to the reception state of the source multicast bearer includes: When the terminal obtains that the target node does not support the MBS capability, the step of obtaining the reception state of the dedicated bearer according to the reception state of the source multicast bearer is included. The step that the terminal obtains that the target node does not support the MBS capability includes: The step that the terminal determines, based on the packet data convergence protocol (PDCP) status report indication information of the dedicated bearer, that the target node does not support the MBS capability, and When the multicast setting information of the target multicast service is not included in the reconfiguration message, the step that the terminal determines that the target node does not support the MBS capability, including at least one of the above. Before the step that the terminal obtains the reception state of the dedicated bearer according to the reception state of the source multicast bearer, The method according to claim 11, further comprising the step that the terminal receives first indication information from the source node, where the first indication information is for indicating that the dedicated bearer is for bearing the service data of the target multicast service. **Claim 13** The step that the terminal obtains the reception state of the dedicated bearer according to the reception state of the source multicast bearer includes: When the terminal receives third indication information from the source node, the step of synchronizing the reception state of the dedicated bearer according to the reception state of the source multicast bearer is included. The third indication information is for instructing the source node to determine a target number according to the number state of the service data of the target multicast service in the source multicast bearer. The target number is for instructing the number that the target node assigns to the target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer. or When the terminal receives fourth indication information from the source node, the method includes maintaining the current reception state of the dedicated bearer. The fourth indication information is for instructing the source node to determine a target number according to the number state of the dedicated bearer. The target number is for instructing the target node to assign a number to a target data packet, and the target data packet is the next unnumbered data packet transmitted by the dedicated bearer. The method according to claim 11.

14. The method further includes the step of the terminal receiving second indication information from the source node. The second indication information is for instructing the terminal to report the reception state of the source multicast bearer to the source node. The method according to claim 10 further includes the step of the terminal reporting the reception state of the source multicast bearer to the source node.

15. The method further includes the step of the terminal receiving first configuration information from the source node, and the step of the terminal configuring the dedicated bearer based on the first configuration information. The first configuration information includes bearer identification information set by the dedicated bearer and does not include layer 2 configuration information of the dedicated bearer. The method according to claim 10.

Images